Hi
First: thanks for all your efforts for the selfdefence from "datatheft"!
I use the eBlocker for about a month now and am very happy with it. But i have a problem. Since I use the eBlocker the batteries of my smartphones are draining unusually fast. If I use the phones normaly, with eBlocker on, the battery is empty in 1/3 or 1/2 of the usual time.
Smartphone 1: Android Nougat, connected via WiFI, without https.
Smartphone 2: Android Pi, connected via WIFI, https included.
Smartphone 3: Android Pi, connected via mobile Network, https included, via eBlocker Mobile. (if i use piHole instead of eBlocker, the battery is empty after about 2 days instead of 1/2 day).
eBlockerOS: installed and updated to the newest Version on January 13th, 2020, on a raspberry-pi 3.
Is this a known issue? What can I do to resolve it?
Thank you very much in advance, kind Regards, Frager
Hi @Frager,
this is an Android issue, because when the smartphone tries to reach google/app sites and doesn't reach them, the frequency of trying to reach is raising, which causes the speed up battery drain.
As far as I know, there should be the possibility that the response for blocked sites can be changed / different
DNS answer for google.de
0.0.0.0 or
127.0.0.1 or
not found
@benne @random
Do you know how eBlocker answers?
And the different answers are the reason for speed up battery drain.
More info also found with pihole
https://www.reddit.com/r/pihole/comments/b8vhh9/pihole_causes_android_battery_drain/
https://discourse.pi-hole.net/t/find-which-android-app-is-causing-so-many-dns-requests/4448
best regards
Sven
@bpr can you help here?
I don't have the answer at the moment without testing / looking at the code. Btw: much is online already github.com/eblocker
eBlocker's DNS returns the local IP 169.254.93.109 for blocked domains. It runs a server on that address that returns an HTTP/S redirect to its blocking page.
@Frager: I am not an Android expert. Is there maybe a setting that shows which apps use most energy?
You could also try if reducing eBlocker's device scanning interval at Settings / Devices / Device Discovery has any effect. Maybe the outgoing ARP packets keep some Android devices from going into sleep mode? But these packets are not routed, so they should not have any effect on devices that are remotely connected via eBlocker Mobile.