guardianproject
[BUG] User reporting Orbot 100% max battery usage
Describe the Bug "Orbot is draining the battery big time since latest obfuscation update I recommended. (v17.5)"
To Reproduce Unsure
Expected Behavior It doesn't drain the battery so much!
What Custom Configuration Do You Use? TBD
Screenshots None
Smartphone (please complete the following information): TBD
Crash Logs (Advanced)
NOTICE: Bootstrapped 14% (handshake): Handshaking with a relay NOTICE: Bootstrapped 15% (handshake_done): Handshake with a relay done NOTICE: Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection NOTICE: Bootstrapped 25% (requesting_status): Asking for networkstatus consensus NOTICE: Bootstrapped 30% (loading_status): Loading networkstatus consensus NOTICE: I learned some more directory information, but not enough to build a circuit: We have no usable consensus. NOTICE: Bootstrapped 40% (loading_keys): Loading authority key certs NOTICE: The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services. NOTICE: Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors NOTICE: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/8779, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.) NOTICE: Bootstrapped 50% (loading_descriptors): Loading relay descriptors NOTICE: The current consensus contains exit nodes. Tor can build exit and internal paths. NOTICE: Bootstrapped 56% (loading_descriptors): Loading relay descriptors NOTICE: Bootstrapped 63% (loading_descriptors): Loading relay descriptors NOTICE: Bootstrapped 72% (loading_descriptors): Loading relay descriptors NOTICE: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits NOTICE: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits NOTICE: Bootstrapped 95% (circuit_create): Establishing a Tor circuit NOTICE: Bootstrapped 100% (done): Done NOTICE: We tried for 15 seconds to connect to '[scrubbed]' using exit $C7EC5E64B545E403C0322A26C18CDBBC30EE3E37~cozybeardev [L/ke7IU2PZE7qbJPHXvRH7/h9eEq6UZJMF33QpZc55w] at 45.90.185.112. Retrying on a new circuit. WARN: tor_bug_occurred_: Bug: ./src/core/or/conflux_util.h:31: CIRCUIT_IS_CONFLUX: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed. (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: Bug: Tor 0.4.8.16 (git-dbc1c4b42069399f): Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed in CIRCUIT_IS_CONFLUX at ./src/core/or/conflux_util.h:31. (Stack trace not available) (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: tor_bug_occurred_: Bug: ./src/core/or/conflux_util.h:31: CIRCUIT_IS_CONFLUX: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed. (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: Bug: Tor 0.4.8.16 (git-dbc1c4b42069399f): Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed in CIRCUIT_IS_CONFLUX at ./src/core/or/conflux_util.h:31. (Stack trace not available) (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: tor_bug_occurred_: Bug: ./src/core/or/conflux_util.h:31: CIRCUIT_IS_CONFLUX: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed. (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: Bug: Tor 0.4.8.16 (git-dbc1c4b42069399f): Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed in CIRCUIT_IS_CONFLUX at ./src/core/or/conflux_util.h:31. (Stack trace not available) (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: tor_bug_occurred_: Bug: ./src/core/or/conflux_util.h:31: CIRCUIT_IS_CONFLUX: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed. (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: Bug: Tor 0.4.8.16 (git-dbc1c4b42069399f): Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed in CIRCUIT_IS_CONFLUX at ./src/core/or/conflux_util.h:31. (Stack trace not available) (on Tor 0.4.8.16 dbc1c4b42069399f) NOTICE: We tried for 15 seconds to connect to '[scrubbed]' using exit $A9044B9AE03BCA32DEECB70A973E34C02F72CFC8~Quetzalcoatl [OOR1OLEwwBB/r1e1dvp++Iy19P9UwdUnp4w0msCkWVI] at 107.189.5.7. Retrying on a new circuit. NOTICE: Tor has not observed any network activity for the past 61 seconds. Disabling circuit build timeout recording. NOTICE: We tried for 15 seconds to connect to '[scrubbed]' using exit $1BAA33FE4AFA3A307797043FCD59665D3C2CE552~NTH39R1 [mH5Y6wvqACXxeBsdMy7nDhVGeCPOz6mZfAotQjWoCjQ] at 192.42.116.202. Retrying on a new circuit. WARN: tor_bug_occurred_: Bug: ./src/core/or/conflux_util.h:31: CIRCUIT_IS_CONFLUX: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed. (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: Bug: Tor 0.4.8.16 (git-dbc1c4b42069399f): Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed in CIRCUIT_IS_CONFLUX at ./src/core/or/conflux_util.h:31. (Stack trace not available) (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: tor_bug_occurred_: Bug: ./src/core/or/conflux_util.h:31: CIRCUIT_IS_CONFLUX: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed. (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: Bug: Tor 0.4.8.16 (git-dbc1c4b42069399f): Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_LINKED failed in CIRCUIT_IS_CONFLUX at ./src/core/or/conflux_util.h:31. (Stack trace not available) (on Tor 0.4.8.16 dbc1c4b42069399f) NOTICE: Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 77 seconds during 25 circuit attempts. WARN: tor_bug_occurred_: Bug: ./src/core/or/conflux_util.h:32: CIRCUIT_IS_CONFLUX: Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_UNLINKED failed. (on Tor 0.4.8.16 dbc1c4b42069399f) WARN: Bug: Tor 0.4.8.16 (git-dbc1c4b42069399f): Non-fatal assertion circ->purpose != CIRCUIT_PURPOSE_CONFLUX_UNLINKED failed in CIRCUIT_IS_CONFLUX at ./src/core/or/conflux_util.h:32. (Stack trace not available) (on Tor 0.4.8.16 dbc1c4b42069399f)
There are a lot of non-fatal asserts in the log which are fixed by https://gitlab.torproject.org/tpo/core/tor/-/commit/46161b194f7a0ca7a2c83c36d1eb01f8110d80a1
Also, Orbot is currently using Openssl 3.5 but without the commits added to Tor for Openssl 3.5.
Maybe this battery drain issue would be fixed by using latest commits on Tor's release-0.4.8 branch.
More details: OnePlus 8, Android 13, OxygenOS (native), and using "power user mode" w/o VPN
@uniqx if you have availability, we may need a new tor-android build - see @syphyr comment above
I don't think we should be using any unofficial release of tor. We were talking off this thread, but I think if you go with
tor 0.4.8.16 we should be using openssl 3.0.16 it seems that in tor browser they don't use openssl 3.5.0 until tor 0.4.9.2-alpha
We can switch to 3.5.0 once a stable 0.4.9.x release of tor comes out.
So unfortunately @uniqx I don't think this is needed right now, but will soon once there's a stable 0.4.9series release
I'm fine with rolling back to openssl 3.0.16, but as I also said off thread I doubt that openssl 3.5.0 was the culprit for this battery consumption. Currently interested in snowflake proxy misbehaving
Tor 0.4.8.17 is going to fully support openssl 3.5. I'm sure that Tor 0.4.8.17 will be released before Tor 0.4.9.x is stable. It should be OK to stay with openssl 3.5.