Bug #2971
Orbot will not connect on Rooted Verizon Note 3
Status: | New | Start date: | 02/18/2014 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | Spent time: | - | |
Target version: | v14 - April Anons | |||
Component: |
Description
This is the log I see. Continues waiting until it just stops. Using latest orbot from Play Store
Orbot is starting…
Orbot is starting…
Tor binary exists: /data/app-lib/org.torproject.android-1/libtor.so
Privoxy binary exists: /data/app-lib/org.torproject.android-1/libprivoxy.so
Obfsproxy binary exists: /data/app-lib/org.torproject.android-1/libobfsproxy.so
Xtables binary exists: /data/app-lib/org.torproject.android-1/libxtables.so
link RM err=0 out:
link LN err=0 out:
libtor.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-1/libtor.so
libtor.so: POST: Is binary exec? true
tor: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/tor
tor: POST: Is binary exec? true
libprivoxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-1/libprivoxy.so
libprivoxy.so: POST: Is binary exec? true
libobfsproxy.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-1/libobfsproxy.so
libobfsproxy.so: POST: Is binary exec? true
libxtables.so: PRE: Is binary exec? true
(re)Setting permission on binary: /data/app-lib/org.torproject.android-1/libxtables.so
libxtables.so: POST: Is binary exec? true
Orbot is starting…
Connecting to control port: 9051
waiting.
Connecting to control port: 9051
waiting.
Connecting to control port: 9051
waiting.
Orbot is starting…
Connecting to control port: 9051
waiting.
History
#1 Updated by n8fr8 over 3 years ago
- Target version set to v14 - April Anons