Bug #3138

Orbot not starting on Note 3

Added by Anonymous almost 4 years ago. Updated over 3 years ago.

Status:NewStart date:03/26/2014
Priority:NormalDue date:
Assignee:Anonymous% Done:

0%

Category:-Spent time:-
Target version:v14 - April Anons
Component:

Description

I have looked at issues 2197 and 2244... my new Note 3 will not connect to TOR network. I upgraded from an S4 Active which ran Orbot wonderfully. Orbot was the first app I installed after getting my new device and it would not run then. Have since installed the rest of my "stuff" but still can't get Orbot working.

Running Orbot v13.0.4a - latest in Play Store
on SM-N900A Android 4.3, kernel 3.4.0.1625098
SELinux status is Enforcing
  • Not rooted or otherwise modified from stock

Same message as described by others;
Orbot is starting (for about 30 seconds)
Orbot is deactivated

(I open the log to this)
Orbot is starting…
Tor binary exists: /mnt/asec/org.torproject.android-1/lib/libtor.so
Privoxy binary exists: /mnt/asec/org.torproject.android-1/lib/libprivoxy.so
Obfsproxy binary exists: /mnt/asec/org.torproject.android-1/lib/libobfsproxy.so
Xtables binary exists: /mnt/asec/org.torproject.android-1/lib/libxtables.so
app installed on external storage - copying binaries to internal
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
privoxy: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/privoxy
privoxy: POST: Is binary exec? true
obfsproxy: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/obfsproxy
obfsproxy: POST: Is binary exec? true
xtables: PRE: Is binary exec? true
(re)Setting permission on binary: /data/data/org.torproject.android/app_bin/xtables
xtables: POST: Is binary exec? true
Orbot is starting…
Orbot is starting…

History

#1 Updated by n8fr8 over 3 years ago

  • Target version set to v14 - April Anons

Also available in: Atom PDF