Describe the Bug
on a armv7 / android 9 device,
past several releases, including the latest release on google play store (17.9.2-RC-1-tor-0.4.9.5.1-1-g5efd657a1) and github release (17.9.4-BETA-2-tor-0.4.9.8), if i select any connection method except Direct connection, as soon as i click connect, android os prompts "Orbot has stopped (app info) (close app)", but choosing 'close app' doesn't close Orbot gui. (as if some background process has died)
i assume that in the past several releases, the connection daemon responsible for snowflake/obfs4 (Lyrebird ?)
has some build issues that cause it to terminally fail on a armv7 / android 9 device.
(i also have armv8 + android 16 device that orbot build from google play store works just fine)
also, logs are empty, orbot android device VPN fails to connect.
no amount of clearing cache/clearing data can resolve this issue.
also, as for reference, the time estimate of this issue NOT happening is google play store release from slightly more than 3 months ago (whatever version that was available at that time)
Expected Behavior
a crash of some background process doesn't happen, Orbot starts the daemon process responsible for Snowflake [AMP]/obfs4 and connects.
What Custom Configuration Do You Use?
none, default installation setting.
Smartphone (please complete the following information):
- Device: Samsung j7 2017 (SM-J730F)
- OS: Android 9
- Version: various, including 17.9.2-RC-1-tor-0.4.9.5.1-1-g5efd657a1, 17.9.4-BETA-2-tor-0.4.9.8
Additional Context
tor network is limited on this network, but it used to work on past versions anyway.
Describe the Bug
on a armv7 / android 9 device,
past several releases, including the latest release on google play store (17.9.2-RC-1-tor-0.4.9.5.1-1-g5efd657a1) and github release (17.9.4-BETA-2-tor-0.4.9.8), if i select any connection method except Direct connection, as soon as i click connect, android os prompts "Orbot has stopped (app info) (close app)", but choosing 'close app' doesn't close Orbot gui. (as if some background process has died)
i assume that in the past several releases, the connection daemon responsible for snowflake/obfs4 (Lyrebird ?)
has some build issues that cause it to terminally fail on a armv7 / android 9 device.
(i also have armv8 + android 16 device that orbot build from google play store works just fine)
also, logs are empty, orbot android device VPN fails to connect.
no amount of clearing cache/clearing data can resolve this issue.
also, as for reference, the time estimate of this issue NOT happening is google play store release from slightly more than 3 months ago (whatever version that was available at that time)
Expected Behavior
a crash of some background process doesn't happen, Orbot starts the daemon process responsible for Snowflake [AMP]/obfs4 and connects.
What Custom Configuration Do You Use?
none, default installation setting.
Smartphone (please complete the following information):
Additional Context
tor network is limited on this network, but it used to work on past versions anyway.