Orbot is starting…
Orbot is starting…
link command output:
Orbot is starting…
got tor proc id: 27262
Tor process id=27262
Connecting to control port: 9051
SUCCESS connected to control port
SUCCESS authenticated to control port
Starting Tor client… complete.
adding control port event handler
SUCCESS added control port event handler
updating settings in Tor service
WARN: You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You specified a public address '0.0.0.0:5400' for DNSPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You specified a public address '0.0.0.0:9040' for TransPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You have a ControlPort set to accept connections from a non-local address.  This means that programs not running on your computer can reconfigure your Tor.  That's pretty bad, since the controller protocol isn't encrypted!  Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
WARN: You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You specified a public address '0.0.0.0:5400' for DNSPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You specified a public address '0.0.0.0:9040' for TransPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You have a ControlPort set to accept connections from a non-local address.  This means that programs not running on your computer can reconfigure your Tor.  That's pretty bad, since the controller protocol isn't encrypted!  Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
WARN: Option 'StrictNodes' used more than once; all but the last value will be ignored.
WARN: Option 'UseBridges' used more than once; all but the last value will be ignored.
WARN: You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You specified a public address '0.0.0.0:5400' for DNSPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You specified a public address '0.0.0.0:9040' for TransPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You have a ControlPort set to accept connections from a non-local address.  This means that programs not running on your computer can reconfigure your Tor.  That's pretty bad, since the controller protocol isn't encrypted!  Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
WARN: You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You specified a public address '0.0.0.0:5400' for DNSPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You specified a public address '0.0.0.0:9040' for TransPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
WARN: You have a ControlPort set to accept connections from a non-local address.  This means that programs not running on your computer can reconfigure your Tor.  That's pretty bad, since the controller protocol isn't encrypted!  Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
Starting privoxy process
/data/app-lib/org.torproject.android-1/libprivoxy.so /data/data/org.torproject.android/app_bin/privoxy.config &

orConnStatus (absVpsTorRelayLUX): LAUNCHED
orConnStatus (afo2): LAUNCHED
NOTICE: Bootstrapped 85%: Finishing handshake with first hop.
orConnStatus (absVpsTorRelayLUX): CONNECTED
NOTICE: Bootstrapped 90%: Establishing a Tor circuit.
orConnStatus (afo2): CONNECTED
Circuit (1) BUILT: absVpsTorRelayLUX
Privoxy is running on port:8118
Privoxy process id=27277

Circuit (2) BUILT: afo2 > askatasuna65 > MichaelsTorExit
NOTICE: Tor has successfully opened a circuit. Looks like client functionality is working.
NOTICE: Bootstrapped 100%: Done.
orConnStatus (Unnamed): LAUNCHED
NOTICE: Our directory information is no longer up-to-date enough to build circuits: We need more microdescriptors: we have 3752/4713, and can only build 50% of likely paths. (We have 81% of guards bw, 78% of midpoint bw, and 79% of exit bw.)
NOTICE: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 3752/4713, and can only build 50% of likely paths. (We have 81% of guards bw, 78% of midpoint bw, and 79% of exit bw.)
Circuit (3) BUILT: afo2 > Unnamed > AccessNow
NOTICE: Tor has successfully opened a circuit. Looks like client functionality is working.
Circuit (5) BUILT: afo2
NOTICE: We now have enough directory information to build circuits.
Circuit (6) BUILT: afo2 > BostonUCompSci > manning1
orConnStatus (Unnamed): CONNECTED
Circuit (4) BUILT: Unnamed
Circuit (7) BUILT: afo2 > RainbowGate > ndnr1
Circuit (8) BUILT: afo2 > torpidsUKuk2 > remoc