#33114 closed defect (fixed)

Crash after update to 16.1.4-BETA-1-tor- (from f-droid)

Reported by: user45738 Owned by: n8fr8
Priority: Very High Milestone:
Component: Applications/Orbot Version: Tor:
Severity: Major Keywords: orbot, crash, android, update
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Updated my orbot this morning, because I saw an update in the F-Droid store, to 16.1.4-BETA-1-tor-

1) I open orbot, the "start screen" loads fine. It shows the unconnected start-state. The background makes this nice pulsing animation
2) I want to start the service, tap "start"/logo.
3) App crashes. It just disappears the second I click start.
4) I then reopen the app, still it is unconnected of course. I enable the VPN slider. The app instantly crashes (again). Even worse, when I now start it again, it crashes (does not show the start screen anymore, either).

I am on android 9. Lineageos 16.0-20191229-NIGHTLY-beryllium. Kernel 4.9.200-perf-g44bd5bc. I use a pocophone f1.
Cannot use the app now.

Child Tickets

Change History (10)

comment:1 Changed 10 months ago by n8fr8

Please downgrade so you can use the previous version.

Lineage 16.0 has known issues with Tor and VPN mode that we are actively debugging.

comment:2 Changed 10 months ago by user45738

Thanks n8fr8. Is there a bug report/issue I can follow?

Downgrading (at least from F-Droid) leads to install-errors for me unfortunately.

comment:3 Changed 10 months ago by n8fr8

You can uninstall, and then from F-Droid, you have access to older versions. You can always grab older releases from here as well: https://github.com/guardianproject/orbot/releases

Likely the "universal" or "armeabi-v7a" releases will be best.

We are working on Lineage fixes now.

comment:4 Changed 10 months ago by n8fr8

We've pushed a BETA 2 here to try, testing on Lineage 16 on a OnePlus 5t:


You can grab the approprite ARM build if you know if you are 32 bit or 64 bit, or just the "universal" one.

comment:5 Changed 10 months ago by user45738

I just tested 16.1.4-BETA-2-tor- on LineageOS16 on Poco F1 and it gave the same problem.

The link was useful, I was able to use it to download an old release for now :)

comment:6 Changed 10 months ago by user45738

Also thanks for providing real replies and feedback. Very useful. I am happy I am at least doing all over TOR now again. Will keep watching releases. The tested armeabi did not work, as said ;)

comment:7 Changed 10 months ago by n8fr8

More question: With Poco F1, did you use armeabi, arm64 or universal build?

Instant crashing is still happening when you tap start?

Is there any way you can capture log output, like using the "adb" tool?


From there, you can likely see what/where the crash is

comment:8 Changed 10 months ago by user45738


Wait a minute.

I allowed USB debugging, opened logcat, wanted to try "Orbot 16.1.4-BETA-2-tor-" again to give output.

It now works! Maybe I had the wrong binary before ?.

comment:9 Changed 10 months ago by n8fr8

sometimes when you upgrade, the old code is still in memory. you have to force stop the app, or wait until Android can replace the running code in memory, before you truly upgrade.

Glad to hear it works!

comment:10 Changed 10 months ago by n8fr8

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.