Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T04:05:15Zhttps://gitlab.torproject.org/legacy/trac/-/issues/15444Cannot install on Android 5.12020-06-13T04:05:15ZTracCannot install on Android 5.1Android 5.1 has started rolling out on many devices. Current version of Orbot on Google Play store doesn't support Android 5.1 yet.
I don't think there are many changes in 5.1 from 5.0, so only change required might be to just bump the ...Android 5.1 has started rolling out on many devices. Current version of Orbot on Google Play store doesn't support Android 5.1 yet.
I don't think there are many changes in 5.1 from 5.0, so only change required might be to just bump the maxSdkVersion to 22.
Keep up the good work & Thanks
**Trac**:
**Username**: abdulmoeedNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/15099Hidden/onion service port forwarding2020-06-13T04:01:23ZFederico Cerattofederico.ceratto@gmail.comHidden/onion service port forwardingOrbot should be able to forward local ports to an onion service.
Once the user configures <onion-address>:<port|portrange> on Orbot, any non-tor-capable application can connect to localhost:<port> and the connection will be forwarded to...Orbot should be able to forward local ports to an onion service.
Once the user configures <onion-address>:<port|portrange> on Orbot, any non-tor-capable application can connect to localhost:<port> and the connection will be forwarded to the (remote) onion service.
Rationale:
- an onion service is used to provide a set of services on different ports (e.g. from a FreedomBox, an ownCloud instance)
- the phone is not rooted
- many applications do not support Tor, or socks proxies, or the configuration is more cumbersome for the average user than just connecting to localhost:<port>
Service authentication could be supported.
Maybe this feature could be instead implemented externally from Orbot with a small, dedicated add.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/15035URI format for bridges2022-03-15T17:14:23ZeighthaveURI format for bridgesRight now, according to @n8fr8, this is the URI format for the bridge URIs:
bridge://obfs3+99.999.99.999%3A10223+c6fa110ebcd8979b0a57617bf2d6e82bbecd287d+%0A
There is a problem with this format because it doesn't follow the URI RFC so ...Right now, according to @n8fr8, this is the URI format for the bridge URIs:
bridge://obfs3+99.999.99.999%3A10223+c6fa110ebcd8979b0a57617bf2d6e82bbecd287d+%0A
There is a problem with this format because it doesn't follow the URI RFC so that standard URI parsers won't parse it very well. Adding the `//` after `bridge:` makes it a "hierarchical" URI, which means that it has the standard sections of authority, user info, host, port, path, query, and fragment. But the above URI will just stick all of the text in the "authority" part, but that section can't be broken down into the standard parts of the "authority", i.e. user info, host, and port.
To keep the same data format, then this URI should be an "opaque" URI. That just means removing the `//`. So that makes it like a `mailto:` URI.
Otherwise, the data could be refactored to fit into the standard parts for a hierarchical URI, then standard URI parsing classes will be able to parse it. For example, android.net.Uri, java.net.URL, etc. That would make the URI look something like this:
`obfs4://xx.xx.xxx.xxx:18965/asdasdasldkasjlasjkdd4?cert=3wYasdasdasdasBmsIat+RMmMDV5BV4jDvXuzasdasdasdas8Dz8J1MUvLKHKaQ&iat-mode=0`
* `getScheme()` would be bridge type
* `getAuthority()` would be IP and port number
* `getHost()` would be IP
* `getPort()` would be port number
* `getPath()` would be this thing: `95151988dc29fccb4f610a1c700a1ddf7d5ffbd4`
* then `cert=`, `iat-mode=`, etc. would be in the query string
The downside of this approach is that there could only be a single bridge per URI, but maybe that's not so bad.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/15028Orbot will not start on Verizon Galaxy S5 Lollipop2015-02-25T19:13:18ZTracOrbot will not start on Verizon Galaxy S5 LollipopI just installed lollipop on my VZ S5, and followed it up with the Orbot 5.0 update. When I press orbot, he goes yellow, tries to connect, then shuts down to grey. I receive the following error notification: Unable to start Tor: java.lan...I just installed lollipop on my VZ S5, and followed it up with the Orbot 5.0 update. When I press orbot, he goes yellow, tries to connect, then shuts down to grey. I receive the following error notification: Unable to start Tor: java.lang.Exception: Torrc config did not verify.
Here is also a copy of the log:
"Orbot is starting…
Orbot is starting…
Waiting for control port...
Connecting to control port: 43646
Connecting to control port: 43646
Connecting to control port: 43646
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…
Orbot is starting…
updating torrc custom configuration...
success.
Orbot is starting…
Tor (1): error: only position independent executables (PIE) are supported.
Unable to start Tor: java.lang.Exception: Torrc config did not verify"
I saw a ticket with a similar problem, but there was no response, at least in the public comments.
**Trac**:
**Username**: corsapernikNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/14946NullPointerException when Requesting Hidden Service2020-06-13T03:58:49ZTracNullPointerException when Requesting Hidden ServiceCurrently, a NullpointerException is raised when requesting a hidden service form another app through an intent.
The attached patch should fix this.
**Trac**:
**Username**: JesusMcCloudCurrently, a NullpointerException is raised when requesting a hidden service form another app through an intent.
The attached patch should fix this.
**Trac**:
**Username**: JesusMcCloudNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/14913Orbot error when using obfs4 bridges2015-02-17T07:03:49ZTracOrbot error when using obfs4 bridgesOrbot is starting…
Orbot is starting…
Waiting for control port...
Connecting to control port: 38088
Connecting to control port: 38088
Connecting to control port: 38088
tor: PRE: Is binary exec? true
polipo: PRE: Is binary exec? true
obfs...Orbot is starting…
Orbot is starting…
Waiting for control port...
Connecting to control port: 38088
Connecting to control port: 38088
Connecting to control port: 38088
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…
Orbot is starting…
updating torrc custom configuration...
success.
Orbot is starting…
Waiting for control port...
Connecting to control port: 34458
SUCCESS connected to Tor control port.
SUCCESS - authenticated to control port.
Starting Tor client… complete.
adding control port event handler
SUCCESS added control port event handler
NOTICE: Opening Socks listener on 127.0.0.1:9050
Local SOCKS port: 9050
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:59904
NOTICE: Closing old Transparent pf/netfilter listener on 127.0.0.1:59904
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:55750
NOTICE: Closing old DNS listener on 127.0.0.1:55750
Local DNSPort port: 9040
Tor started; process id=7660
updating settings in Tor service
Set background service to FOREGROUND
Starting polipo process
WARN: We were supposed to connect to bridge 'Address' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
NOTICE: Delaying directory fetches: No running bridges
Polipo is running on port:8118
Polipo process id=7680
**Trac**:
**Username**: ProGamerGuyNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/14883Orbot handshake fails on networks with Blue Coat Systems' technology2020-06-13T03:58:08ZTracOrbot handshake fails on networks with Blue Coat Systems' technologyBootstrapping fails at 85%.
**Trac**:
**Username**: ProGamerGovBootstrapping fails at 85%.
**Trac**:
**Username**: ProGamerGovNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/14801"EXCLUDE Nodes" is not respected in Orbot2020-06-13T03:56:24ZTrac"EXCLUDE Nodes" is not respected in OrbotI've entered FiveEyes in Exlude Nodes and yet it still connects me to them. At first I thought it's just relay nodes. But just now, I was connected to a path with an Exit Node in one of them!
I input countries as:
US, UK, NZ, CA, AU,
A...I've entered FiveEyes in Exlude Nodes and yet it still connects me to them. At first I thought it's just relay nodes. But just now, I was connected to a path with an Exit Node in one of them!
I input countries as:
US, UK, NZ, CA, AU,
And I also tried with and without "Strict Nodes" option.
Orbot: 14.1.4-noPIE (Tor: 0.2.5.10)
Android: 4.4.4
Nexus 5, stock rooted
Downloaded Orbot from F-Droid
**Trac**:
**Username**: BugerNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/14767Orbot doesn't use specified exit node2016-04-07T11:15:37ZTracOrbot doesn't use specified exit nodeI have specified an exit node in Orbot but it doesn't use it.
I run the specified exit node and it is using the default exit policy which I think should allow it to be used as an exit node.
Orbot 14.1.4-noPI on an HTC One M8 (not roote...I have specified an exit node in Orbot but it doesn't use it.
I run the specified exit node and it is using the default exit policy which I think should allow it to be used as an exit node.
Orbot 14.1.4-noPI on an HTC One M8 (not rooted)
Firefox with Proxy Mobile addon
**Trac**:
**Username**: 2bdkidNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/14425Orbot not working after upgrade to Lollipop2020-06-13T03:53:29ZTracOrbot not working after upgrade to LollipopI was using Orbot on my HTC One (M7) running a custom ROM,Android KitKat,fully rooted and had no issues. I've recently upgraded the same ROM to its newest version which is Lollipop. Orbot now will not start. I have the latest Play Store ...I was using Orbot on my HTC One (M7) running a custom ROM,Android KitKat,fully rooted and had no issues. I've recently upgraded the same ROM to its newest version which is Lollipop. Orbot now will not start. I have the latest Play Store version of the App. I copied the log details:
Orbot is starting…
Orbot is starting…
Waiting for control port...
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…
Orbot is starting…
updating torrc custom configuration...
success.
Orbot is starting…
Tor (1): error: only position independent executables (PIE) are supported.
Unable to start Tor: java.lang.Exception: Torrc config did not verify
**Trac**:
**Username**: rantekinazNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/13957Orbot not starting on lollipop (Nexus 4)2020-06-13T03:47:18ZTracOrbot not starting on lollipop (Nexus 4)Every time I try starting Orbot, I see the following error:
Tor(1):error: only position independent executables (PIE) are supported
Unable to start Tor:java.lan.Exception: Torrc config did not verify.
I tried the advise given in
http...Every time I try starting Orbot, I see the following error:
Tor(1):error: only position independent executables (PIE) are supported
Unable to start Tor:java.lan.Exception: Torrc config did not verify.
I tried the advise given in
https://trac.torproject.org/projects/tor/ticket/13764
But that didn't help either.
Is there anything else I can do?
Thanks,
**Trac**:
**Username**: atthedoghouseNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/13954Android fonepad2020-06-13T03:47:16ZTracAndroid fonepadDownloaded both apps from Google play store and did the regular install to internal hard drive
Orbo keeps giving me a startup error so I deleted both apps and reinstalled them with same results
How can I manually repair install
Phone= A...Downloaded both apps from Google play store and did the regular install to internal hard drive
Orbo keeps giving me a startup error so I deleted both apps and reinstalled them with same results
How can I manually repair install
Phone= Asus FonePad 7 K012 rooted running 4.3 jellybean
Running android Orbit 14.1.4 (Tor 0.2.5.10)
Orbot is starting…
Orbot is starting…
Waiting for control port...
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…
Orbot is starting…
updating torrc custom configuration...
success.
Orbot is starting…
Tor (1): sh: <stdin>[2]: /data/data/org.torproject.android/app_bin/tor: No such file or directory
Unable to start Tor: java.lang.Exception: Torrc config did not verify
**Trac**:
**Username**: stockmanNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/13841Orbot dropping connections when opening Orweb2016-04-07T11:19:26ZTracOrbot dropping connections when opening OrwebLatest version of Orbot on android lollipop drops all connections as soon as Orweb is opened. Output :
Orbot is starting…
checking binary version: 0.2.5.10-openssl1.0.1i-nonPIE-polipofix
updating torrc custom configuration...
success.
O...Latest version of Orbot on android lollipop drops all connections as soon as Orweb is opened. Output :
Orbot is starting…
checking binary version: 0.2.5.10-openssl1.0.1i-nonPIE-polipofix
updating torrc custom configuration...
success.
Orbot is starting…
Waiting for control port...
Waiting for control port...
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…
Orbot is starting…
updating torrc custom configuration...
success.
Orbot is starting…
Waiting for control port...
Connecting to control port: 56220
SUCCESS connected to Tor control port.
SUCCESS - authenticated to control port.
Starting Tor client… complete.
adding control port event handler
SUCCESS added control port event handler
NOTICE: Opening Socks listener on 127.0.0.1:9050
Local SOCKS port: 9050
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:35922
NOTICE: Closing old Transparent pf/netfilter listener on 127.0.0.1:35922
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:50507
NOTICE: Closing old DNS listener on 127.0.0.1:50507
Local DNSPort port: 9040
Tor started; process id=8389
updating settings in Tor service
Starting polipo process
NOTICE: Delaying directory fetches: No running bridges
NOTICE: Learned fingerprint 4F3DC1C3FB05721E0C88C67E161C026657EF6293 for bridge 192.168.10.220:9005.
Circuit (4) BUILT: 0000000000000000000000000000000000000000
NOTICE: new bridge descriptor 'PhilsTorBridge' (fresh): $4F3DC1C3FB05721E0C88C67E161C026657EF6293~PhilsTorBridge at 192.168.10.220
NOTICE: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 3861/6786, and can only build 19% of likely paths. (We have 55% of guards bw, 56% of midpoint bw, and 61% of exit bw.)
Polipo is running on port:8118
Polipo process id=8429
Circuit (5) BUILT: PhilsTorBridge
NOTICE: Bootstrapped 59%: Loading relay descriptors
NOTICE: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 3861/6786, and can only build 19% of likely paths. (We have 55% of guards bw, 56% of midpoint bw, and 61% of exit bw.)
NOTICE: Bootstrapped 64%: Loading relay descriptors
NOTICE: Bootstrapped 69%: Loading relay descriptors
NOTICE: Bootstrapped 74%: Loading relay descriptors
NOTICE: We now have enough directory information to build circuits.
NOTICE: Bootstrapped 80%: Connecting to the Tor network
NOTICE: Bootstrapped 90%: Establishing a Tor circuit
Circuit (6) BUILT: PhilsTorBridge > roxxyCZ > kramse
NOTICE: Tor has successfully opened a circuit. Looks like client functionality is working.
NOTICE: Bootstrapped 100%: Done
Circuit (8) BUILT: PhilsTorBridge > Unnamed > toxiroxiUA2
Circuit (9) BUILT: PhilsTorBridge > YouOhKay > VERITAS
At this point I click on Check Browser to open Orweb which says 'Web page not available ' net: ERR_TUNNEL_CONNECTION_FAILED
Back to the log shows the following
Circuit (5) CLOSED: PhilsTorBridge
Circuit (6) CLOSED: PhilsTorBridge > roxxyCZ > kramse
Circuit (4) CLOSED: 0000000000000000000000000000000000000000
Circuit (8) CLOSED: PhilsTorBridge > Unnamed > toxiroxiUA2
Circuit (9) CLOSED: PhilsTorBridge > YouOhKay > VERITAS
NOTICE: Delaying directory fetches: No running bridges
Will not connect again.
Never had any problems before upgrading to lollipop...
**Trac**:
**Username**: tescophilNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/13768clean orbot build from git clone https://git.torproject.org/orbot.git2020-06-13T03:43:24ZTracclean orbot build from git clone https://git.torproject.org/orbot.gitTrying to make clean build from
git clone https://git.torproject.org/orbot.git
It seems that makefile is not sync with latest external folders. iptables, libevent missing.
How are official builds made? It looks that not from clean sta...Trying to make clean build from
git clone https://git.torproject.org/orbot.git
It seems that makefile is not sync with latest external folders. iptables, libevent missing.
How are official builds made? It looks that not from clean start. Messy stuff.
As security app as is should be more proper maintained.
-----
make[3]: Leaving directory `/media/verbatim/git/orbot_main/orbot/external/openssl/engines/ccgost'
make[2]: Leaving directory `/media/verbatim/git/orbot_main/orbot/external/openssl/engines'
make[1]: Leaving directory `/media/verbatim/git/orbot_main/orbot/external/openssl'
touch openssl-build-stamp
test -d lib || mkdir lib
test -d include || mkdir include
test -d include/openssl || mkdir include/openssl
cp openssl/libcrypto.a lib/libcrypto.a
cp openssl/libssl.a lib/libssl.a
cp openssl/include/openssl/* include/openssl
sed -i 's@\(SUBDIRS = . include\) sample test@\1@' libevent/Makefile.am
sed: can't read libevent/Makefile.am: No such file or directory
make: [libevent/Makefile] Error 2
make: Leaving directory `/media/verbatim/git/orbot_main/orbot/external'
**Trac**:
**Username**: throwaway1Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/13764Orbot not starting on Lollipop (Nexus 5)2015-10-27T22:40:35ZTracOrbot not starting on Lollipop (Nexus 5)When pressing the start button, the yellow color flashes for a second before it gets grey again and the log says:
Orbot is starting...
That's it.
Anything I can do?
**Trac**:
**Username**: mk9900When pressing the start button, the yellow color flashes for a second before it gets grey again and the log says:
Orbot is starting...
That's it.
Anything I can do?
**Trac**:
**Username**: mk9900Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/13455all orbot download links in f-droid app are broken2016-04-07T11:38:22ZTracall orbot download links in f-droid app are brokenTried entering the links in a browser as well and they go to a 404 not found page.
Links:
Version 14.0.4.3: https://f-droid.org/repo/org.torproject.android_109.apk
Version 14.0.4.1: https://f-droid.org/repo/org.torproject.android_107....Tried entering the links in a browser as well and they go to a 404 not found page.
Links:
Version 14.0.4.3: https://f-droid.org/repo/org.torproject.android_109.apk
Version 14.0.4.1: https://f-droid.org/repo/org.torproject.android_107.apk
Version 14.0.4: https://f-droid.org/repo/org.torproject.android_106.apk
**Trac**:
**Username**: vvnNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/13453circular link, outdated info on orbot info page2020-06-13T03:37:22ZTraccircular link, outdated info on orbot info pagepage I'm referencing is: https://guardianproject.info/apps/orbot/
fixes should be made in the 4th paragraph, the section outlining features after the screenshot:
> ★ PRIVATE CHAT MESSAGING: Use Gibberbot with Orbot to chat confidentia...page I'm referencing is: https://guardianproject.info/apps/orbot/
fixes should be made in the 4th paragraph, the section outlining features after the screenshot:
> ★ PRIVATE CHAT MESSAGING: Use Gibberbot with Orbot to chat confidentially with anyone, anywhere for free. Get Gibberbot:
> !https://goo.gl/O3FfS!
__'been awhile since it was called gibberbot, hasn't it? should probably change that to chatsecure
__'
> ★ PRIVACY FOR APPS: Any installed app can use Tor if it has a proxy feature, using the settings found here:
> https://goo.gl/2OA1y
**_The short url unmasks to the exact page it's on. Seeing as there are multiple possibilities (localhost: 9050, localhost 9040, localhost 8118, and http/https/socks4/socks4a/socks5) and no real explanation of the proper proxy configuration, there should be at least a section with that info and how they are connected to each other, because sending everything through tor doesn't work, and there is a bug in the individual apps selection I will detsail in a separate ticket if it hasn't yet been reported that makes the option virtually unusable.**_
**Trac**:
**Username**: vvnNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/13333Android users visiting sites using Tor leave all kinds of incriminating evide...2020-06-13T03:34:46ZcypherpunksAndroid users visiting sites using Tor leave all kinds of incriminating evidence in the logsPeople using Tor on Android use User-Agents with all kinds of incriminating evidence such as:
"Mozilla/5.0 (Linux; Android 4.1; Nexus 7 Build/JRN84D)
AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.166
Safari/535.19"
"Mozill...People using Tor on Android use User-Agents with all kinds of incriminating evidence such as:
"Mozilla/5.0 (Linux; Android 4.1; Nexus 7 Build/JRN84D)
AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.166
Safari/535.19"
"Mozilla/5.0 (Linux; U; Android 4.2.2; es-us; HUAWEI Y320-U151
Build/HUAWEIY320-U151) AppleWebKit/534.30 (KHTML, like Gecko)
Version/4.0 Mobile Safari/534.30"
"Mozilla/5.0 (Linux; U; Android 2.3; en-us; GT-I9100 Build/GRH78)
AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1"
These are examples with the least personal information in them and they may or may not be from a popular hidden service.
I am not sure who's software or project is responsible for this but it does not exactly make these people "blend in"Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/13185Orbot still accesses the public Tor network with bridges configured2020-06-13T03:31:47ZMike PerryOrbot still accesses the public Tor network with bridges configuredI configured Orbot 14.0.8.1 to use bridges, and then set up my upstream firewall to block all connection attempts except to that bridge, yet Orbot still seems to try to connect to many other nodes in the public directory.
Note I have th...I configured Orbot 14.0.8.1 to use bridges, and then set up my upstream firewall to block all connection attempts except to that bridge, yet Orbot still seems to try to connect to many other nodes in the public directory.
Note I have the same configuration on my laptop, and tor does not do this. If bridges are configured, Tor only connects to those IPs.
It should also be possible to observe by inspecting Orbot's connections on your Android device in OS Monitor app's "Connections" tab:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
https://f-droid.org/repository/browse/?fdid=com.eolwral.osmonitorNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/13121App Conflict2020-06-13T03:30:27ZTracApp ConflictPlease disable this app in Android: -> settings-> Apps if you are having problems with Orbot: com.sec.msc.nts.android.proxy
**Trac**:
**Username**: dlmrPlease disable this app in Android: -> settings-> Apps if you are having problems with Orbot: com.sec.msc.nts.android.proxy
**Trac**:
**Username**: dlmrNathan FreitasNathan Freitas