[guardian-dev] hidden services, doze, battery life
arrase at gmail.com
Wed Dec 7 16:46:07 EST 2016
I knew the problem but I did not address it in depth because until now it
was not an intensive use of hidden services in Orbot.
Now that I have finished my changes it is time to study the problem but I
need to write some code before deciding a solution.
I will keep you informed of my progress.
I have read your comments on the link you attach and I want to thank you
for the information gathering work you have done.
I think at the technical level you have exposed all the arguments.
2016-12-07 1:10 GMT+01:00 Greg Troxel <gdt at lexort.com>:
> I tried to use briar, which uses a HS on every user's device to get
> metadata protection for messaging:
> and noticed that it kept my phone always awake. After some very helpful
> discussions, I understand that the basic issue (vast
> oversimplification!) is that tor's state machine expects to be called
> once/second, and essentially this isn't compatible with android/doze.
> So I wonder what you are doing about hidden services in orbot? Are you
> taking a wake lock? Being a good doze citizen? Does this really work
> (meaning you can keep a HS registered in doze, and the app will notice
> arriving traffic in 10 minutes when it hits maintenance window)? With
> or without whitelisting? Or do you think I'm confused (that would be
> great, in this situation)?
> (It's on my todo list to change the code to not object to being called
> up to about 900s late, and to remove the wake lock from briar, and see
> what happens.)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the guardian-dev