[guardian-dev] hidden services, doze, battery life

arrase arrase at gmail.com
Wed Dec 7 20:13:08 EST 2016

When a user wants to have a hidden service active in sleep mode has to pay
the toll imposed by Android and we can not do anything about it without
patching Tor.

So I think our best approach is to ask the user to include Orbot in the
white list of Doze when there is some hidden service active and remind him
to delete Orbot from the list when all the services are paused.

I have written the code that manages the permission with the minimum
impact, but I would like to know what Nathan thinks before adding it to my

2016-12-07 22:46 GMT+01:00 arrase <arrase at gmail.com>:

> 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:
>>   https://briarproject.org/
>> 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)?
>> https://code.briarproject.org/akwizgran/briar/issues/769
>> https://lists.torproject.org/pipermail/tor-dev/2016-December/011708.html
>> https://lists.torproject.org/pipermail/tor-dev/2016-December/011713.html
>> (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.)
>> Thanks,
>> Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/guardian-dev/attachments/20161208/c88ffa39/attachment.html>

More information about the guardian-dev mailing list