Bug #3853
NOT RESOLVED! orbot 14.0.x conflicts with com.android.systemui & now conpletely HANGS OS&WiFi on Sprint-Samsung GS4 Android 4.4.2
| Status: | New | Start date: | 06/20/2014 | |
|---|---|---|---|---|
| Priority: | Immediate | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| Component: |
Description
orbot v13.0.x & v14.0.x releases mutually hang orbot & Android WiFi whenever WiFi is enabled.
orbot also hangs Android Settings whenever WiFi is enabled and battery drain goes crazy.
Rebooting Sprint-Samsung Android 4.4.2, with WiFi & orbot enabled hangs WiFi, hangs orbot & hangs com.android.systemui - requniring a battery pull or long powerbutton hold to reboot again. Then, you have to rush into Android Settings, disable WiFi and reboot again, before orbot screws everything up, again, just to revert 3G/LTE connectivity.
This is NOT the ALLEGED conflict with com.sec.msc.nts.android.proxy & Samsung AllShare/Samsung Link, which are BOTH disabled on this GS4.
Whoever closed out Bug #3576 was COMPLETLY WRONG in doing so.
IT IS TIME FOR THE DEVS TO ASK/BEG GOOGLE FOR HELP FIXING THESE PROBLEMS.