Core Apps » Orbot

Log pasted below. Info: Rooted Samsung galaxy 3 (sch-i535), running kitkat 4.4.2... phone got really hot and needed battery pull (touch screen went unresponsive, no luck rebooting into safe mode or using power buttons. Eep.)

the notoriously problematic galaxy proxy process is disabled fwiw.

////////thanks for your tireless work! I wish i knew how to level up from newbie to debugger. Srsly! /////////

starting Tor background service...
Tor background service connected.
checking binary version: 0.2.5.7-openssl1.0.1i
updating torrc custom configuration...
success.
checking binary version: 0.2.5.7-openssl1.0.1i
updating torrc custom configuration...
success.
Reading control port config file: /data/data/org.torproject.android/app_bin/control.txt
Connecting to control port: 55676
Error connecting to Tor local control port: failed to connect to /127.0.0.1 (port 55676): connect failed: ECONNREFUSED (Connection refused)
waiting...
Connecting to control port: 55676
Error connecting to Tor local control port: failed to connect to /127.0.0.1 (port 55676): connect failed: ECONNREFUSED (Connection refused)
waiting...
tor: PRE: Is binary exec? true
polipo: PRE: Is binary exec? true
obfsclient: PRE: Is binary exec? true
xtables: PRE: Is binary exec? true
Orbot is starting…
updating torrc custom configuration...
success.
Network connectivity is good. Waking Tor up...
Reading control port config file: /data/data/org.torproject.android/app_bin/control.txt
Connecting to control port: 53175
SUCCESS connected to Tor control port.
checking binary version: 0.2.5.7-openssl1.0.1i
updating torrc custom configuration...
success.
SUCCESS connected to Tor control port.
Background service is bound. Status=2
Orbot is starting…
SUCCESS - authenticated to control port.
adding control port event handler
SUCCESS added control port event handler
SUCCESS - authenticated to control port.
adding control port event handler
SUCCESS - authenticated to control port.
adding control port event handler
SUCCESS - authenticated to control port.
adding control port event handler
SUCCESS added control port event handler
found existing Tor process…
NOTICE: Opening Socks listener on 127.0.0.1:9050
Local SOCKS port: 9050
SUCCESS added control port event handler
NOTICE: Opening Transparent pf/netfilter listener on 127.0.0.1:9040
NOTICE: Closing no-longer-configured Transparent pf/netfilter listener on 127.0.0.1:47304
NOTICE: Closing old Transparent pf/netfilter listener on 127.0.0.1:47304
Local TransProxy port: 9040
NOTICE: Opening DNS listener on 127.0.0.1:5400
NOTICE: Closing no-longer-configured DNS listener on 127.0.0.1:42017
NOTICE: Closing old DNS listener on 127.0.0.1:42017
Local DNSPort port: 9040
Tor started; process id=2971
updating settings in Tor service
found existing Tor process…
Starting polipo process
Starting Tor client… complete.
NOTICE: Bootstrapped 5%: Connecting to directory server
NOTICE: Bootstrapped 10%: Finishing handshake with directory server
Polipo is running on port:8118
Polipo process id=4662
NOTICE: Bootstrapped 15%: Establishing an encrypted directory connection
NOTICE: Bootstrapped 20%: Asking for networkstatus consensus
Circuit (1) BUILT: CoinTossHead
NOTICE: Bootstrapped 25%: Loading networkstatus consensus
WARN: Our clock is 106 days, 23 hours, 16 minutes behind the time published in the consensus network status document (2014-09-22 03:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
NOTICE: I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
NOTICE: Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
Circuit (10) BUILT: Samo2
NOTICE: Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
WARN: Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (DONE; DONE; count 10; recommendation warn)
WARN: 10 connections have failed:
WARN: 10 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
NOTICE: Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
WARN: Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (DONE; DONE; count 11; recommendation warn)
WARN: 11 connections have failed:
WARN: 11 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
NOTICE: Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
WARN: Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (DONE; DONE; count 12; recommendation warn)
WARN: 12 connections have failed:
WARN: 12 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
Circuit (15) BUILT: TorSupporter
NOTICE: Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.