I just charged yesterday, havent used the device today at all (device is set to always standby, never power down) - and battery usage tells me 20 days of charge left. Questions?
Make sure this is enabled in advanced Wifi Settings (Android Settings).
Make sure bluetooth is disabled. Use this for quick access:
https://apkpure.com/bluetooth-settin...edia.bluetooth
As the Likebook kills all your apps running in the background anyhow - it isnt your apps.
Only other possibility - the Likebook is indexing all your ebooks without you noticing, in which case remove them and put them back on in groups of less than several thousands.
You can also use the
adb top -m 10
command to see what processes are are active (developer options/usb debugging/enabled, pc with adb installed connected via usb) - in my case thats a hot 0% active for all processes while the device is idle:
Code:
User 0%, System 2%, IOW 0%, IRQ 0%
User 7 + Nice 1 + Sys 59 + Idle 2396 + IOW 0 + IRQ 0 + SIRQ 0 = 2463
PID PR CPU% S #THR VSS RSS PCY UID Name
97 5 0% S 1 0K 0K fg root taskup
96 4 0% S 1 0K 0K fg root epd_task
99 7 0% S 1 0K 0K fg root taskup_three
98 6 0% S 1 0K 0K fg root taskup_two
29672 6 0% R 1 3612K 1076K fg shell top
543 2 0% S 90 2101352K 118772K fg system system_server
100 0 0% S 1 0K 0K fg root epd thread
638 1 0% S 35 1488036K 88696K fg u0_a15 com.android.systemui
205 2 0% S 19 143764K 21184K fg system /system/bin/surfaceflinger
27640 0 0% S 1 0K 0K fg root kworker/0:0
User 0%, System 0%, IOW 0%, IRQ 0%
User 9 + Nice 0 + Sys 11 + Idle 2444 + IOW 1 + IRQ 0 + SIRQ 0 = 2465
PID PR CPU% S #THR VSS RSS PCY UID Name
29672 6 0% R 1 3612K 1076K fg shell top
543 2 0% S 90 2101352K 118772K fg system system_server
205 2 0% S 19 143764K 21184K fg system /system/bin/surfaceflinger
5 0 0% S 1 0K 0K fg root kworker/0:0H
186 3 0% S 1 0K 0K fg root dhd_dpc
1156 1 0% S 5 4908K 332K fg shell /sbin/adbd
243 1 0% S 10 16128K 2164K fg root /system/bin/netd
1455 1 0% S 11 1442824K 45560K fg u0_a38 info.kfsoft.force.rotation
12 1 0% S 1 0K 0K fg root watchdog/1
13 1 0% S 1 0K 0K fg root migration/1
User 0%, System 0%, IOW 0%, IRQ 0%
User 6 + Nice 0 + Sys 13 + Idle 2445 + IOW 0 + IRQ 0 + SIRQ 0 = 2464
PID PR CPU% S #THR VSS RSS PCY UID Name
29672 6 0% R 1 3612K 1076K fg shell top
543 1 0% S 90 2101352K 118772K fg system system_server
638 1 0% S 35 1488036K 88696K fg u0_a15 com.android.systemui
5 0 0% S 1 0K 0K fg root kworker/0:0H
27640 0 0% S 1 0K 0K fg root kworker/0:0
205 2 0% S 19 143764K 21184K fg system /system/bin/surfaceflinger
28476 1 0% S 21 925684K 45212K bg u0_a12 com.android.vending:instant_app_installer
950 0 0% S 1 8652K 3268K fg wifi /system/bin/wpa_supplicant
12 1 0% S 1 0K 0K fg root watchdog/1
13 1 0% S 1 0K 0K fg root migration/1
Telling people that their android devices use battery when they are active, is only so much fun. Becaue they then all are like "but why" and "how can I make them not use battery", and why should I uninstall facebook.
One more thing - your last active app still could be preventing your likebook to go into hybernating states as well. If you cant make out the culprit, start deinstalling all your apps, and see if it helped.
Sadly this doesnt always show up on the battery usage screen (as you've noticed quite a few processes are grouped as "android") - in that case, use GSAM (
https://play.google.com/store/apps/d...m.gsamlabs.bbm) (app has to be "always running in the background") to check wakelocks after a few hours.
Wakelocks are apps preventing the system from hybernating, and are usually caused by apps becoming active ("is there a new message from someone for me?!"), and android then preventing the device from going into hyberntion for a short while ("app probably still is communicating, I better not sleep"). If you have one app that spams the system with "active" states ("really no new massage for me?") battery drain can be caused by that as well.
On the likebook this is less likely since they are killing all apps in the background anyhow (usually - except for those you define in power options as "allowed"), but the last active app isnt killed and could still trigger it.
So I have to troubleshoot this? Yes - be my guest.
Start by disabling Bluetooth and Setting Wifi to the setting above. If that doesnt immensely increase your standby time, try to use GSAM to find out whats the culprit (you have to allow this app to run in the backgrount in the likebooks power management), if that doesnt help start by removing books from the device (the likebook is probably indexing them) and only adding them in small groups.
Try to not be the guy that tells the internet "i've have installed 5 apps you never heard of, and now my battery life is bad - what should I do". Try to prevent it at all cost. Something about the law of probability and you finding another human being that has the same five apps installed on the same device as you have. Still, people try to get their problems fixed this way by the thousands.
I'm on the latest firmware, btw.