Write a design document for the control interface for enhanced battery awareness on Android devices

We should begin writing a design document for the control interface for enhanced control of battery utilisation.

We should investigate how Tor and Orbot currently interacts with the platform and how this could be improved. Ideally in a manner that potentially could become useful for other mobile platforms such as iOS as well.

Android documents that might be worth reading for better knowledge of platform features when it comes to standby:

• https://developer.android.com/training/monitoring-device-state/doze-standby.html

changed milestone to %Tor: unspecified

added 034-deferred-20180602 034-included-20180405 034-roadmap-subticket 034-triage-20180328 035-removed-20180711 TorCoreTeam201711.1 component::core tor/tor milestone::Tor: unspecified owner::ahf parent::25499 priority::medium resolution::implemented severity::normal status::closed type::defect labels

Assigning to Nick.

Trac:
Owner: N/A to nickm
Status: new to assigned

Trac:
Keywords: s8-201711 deleted, s8-201711 TorCoreTeam201711.1 added

Attaching a draft for initial comment. I'll send it to tor-dev next week.

Trac:
xxx-hibernation-api.txt

Trac:
Cc: N/A to ahf, hellais, darkk, brade, mcs, sbs, mike@tig.as

Trac:
Cc: ahf, hellais, darkk, brade, mcs, sbs, mike@tig.as to ahf, hellais, darkk, brade, mcs, sbs, mtigas

This looks great to me. Don't know the specifics of Android, but what you've got would be super useful for the limited callbacks we get on iOS: https://developer.apple.com/library/content/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/TheAppLifeCycle/TheAppLifeCycle.html#//apple_ref/doc/uid/TP40007072-CH2-SW3

The app's applicationWillResignActive: or applicationDidEnterBackground : are where I'd likely call SIGNAL SLEEP, and likewise with applicationDidBecomeActive: and SIGNAL WAKEUP. (Right now I think I only call SIGNAL HUP at applicationDidBecomeActive: time, which doesn't always gracefully recover from the iOS background state. So think this will be very useful.)

But yeah, LGTM (from the iOS point of view).

I've added the proposal above as proposal 286.

Trac:
Keywords: s8-201711 TorCoreTeam201711.1 deleted, s8-201711, TorCoreTeam201711.1, 034-triage-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

Trac:
Keywords: 034-removed-20180328 deleted, 034-roadmap-subticket 034-included-20180405 added
Parent: N/A to #25499 (moved)

Trac:
Owner: nickm to ahf

Deferring non-must tickets to 0.3.5

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: 0.3.5.x-final
Keywords: 034-roadmap-subticket 034-included-20180405 deleted, 034-included-20180405, 034-roadmap-subticket, 034-deferred-20180602 added

These tickets are being triaged out of 0.3.5. The ones marked "035-roadmap-proposed" may return.

Trac:
Milestone: Tor: 0.3.5.x-final to Tor: unspecified
Keywords: N/A deleted, 035-removed-20180711 added

Trac:
Keywords: s8-battery, s8-control, s8-201711 deleted, N/A added
Sponsor: Sponsor8 to N/A

Subsumed in Dormant* options.

Trac:
Resolution: N/A to implemented
Status: assigned to closed

closed

mentioned in issue #24108 (moved)

mentioned in issue #24204 (moved)

moved to tpo/core/tor#24107 (closed)