Bug #5521
Orbot wont start on Samsung Galaxy S6. 15.0.1-RC3-PIE
Status: | New | Start date: | 07/18/2015 | |
---|---|---|---|---|
Priority: | Urgent | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | Spent time: | - | |
Target version: | - | |||
Component: |
Description
checking binary version: null
upgrading binaries to latest version: 0.2.6.10
There was an error installing Orbot binaries
Orbot is starting…
Orbot is starting…
checking binary version: null
upgrading binaries to latest version: 0.2.6.10
Unable to start Tor: java.io.FileNotFoundException: armeabi/tor.mp3
Set background service to FOREGROUND
TorService is shutting down
Orbot is deactivated
Orbot is starting…
Orbot is starting…
checking binary version: null
upgrading binaries to latest version: 0.2.6.10
Unable to start Tor: java.io.FileNotFoundException: armeabi/tor.mp3
Set background service to FOREGROUND
TorService is shutting down
Orbot is deactivated
Related issues
History
#1 Updated by reg over 2 years ago
Hi there!
I have the same phone, same version, same issue.
One thing I noticed, though, is that this only happens when Orbot was downloaded from F-Droid. Orbot from Google Play, with the same version number, works just fine.
#2 Updated by teeks99 about 2 years ago
I'm having the same issue on my Nexus 6P.
#3 Updated by penguin77 about 2 years ago
I too have the same issue except on OnePlus 2. Also downloaded from F-droid, the version I had previously installed from play store worked fine
#4 Updated by penguin77 about 2 years ago
I found a solution to this. There seems to be 3 builds of the current version on 3 different dates. If you install the one which is not labelled PIE then it works. It won't upgrade as the signature is different
#5 Updated by teeks99 about 2 years ago
I also got it working with a different build. Here are the options I see in F-Droid (in the following order):
1. Version 15.0.1-RC-3-PIE - 7/16/15 - 4.4MB
2. Version 15.0.1-RC-3-PIE - 7/18/15 - 8.0MB
3. Version 15.0.1-RC-3 - 7/1/15 - 10.2MB
No. 1 was installed by default. Manually uninstalling orbot and re-installing No. 2 seemed to fix everything.
Could anyone describe why I'm seeing these different versions, and what they mean? Is this some kind of config error where I was installing a version that wasn't compatible with my hardware? Is this something that can be rectified in the packaging?
#6 Updated by InflatableSoulmate about 2 years ago
Same issue with a Verizon LG V10 (VS990, rev 1.0), Android 5.1.1, kernel 3.10.49-gdc160a8-00005-g2eb8497. I used the FDroid app to download Orbot, since the website doesn't appear to point to a file index.