short battery life on OPO (Bacon) with OTA12

truscellino

Hi everyone,
Like most of you in this thread, I have noticed a drop in battery life since OTA12 with very light usage of the phone. Nothing looking awful when taking a look at processes with "top" in the phone terminal, Unity8 with ~2-5% of CPU... which means that hardware is working too much when most things should be idle.
I will try:

disabling wifi (except when I use it)
try and disable IPv6

Will report back here...
thanks

flohack

@Moem Sory I would need the dmesg right after startup. You sent me one thats already after some time of operation. So reboot, and then try to capture it. Also /var/log/syslog could be useful..

flohack

@truscellino You cannot use top to measure activity of the CPU, since top will keep your phone out of deep sleep, and, worse, if you try it with the terminal-app you will also see a lot of CPU going into rendering the display. Also, if you connect a cable and the phone gets charged from that, the whole battery management will switch to different modes.

So currently there is no reliable way to capture activity of the phone while you are on the go, someone needs to research kernel measurement facilities for that.

Moem

@Flohack said in short battery life on OPO (Bacon) with OTA12:

Sory I would need the dmesg right after startup.

Right. That's not the kind of thing a beginner would 'just know'. But no problem, I'll get to it.

Moem

@Flohack said in short battery life on OPO (Bacon) with OTA12:

Also /var/log/syslog could be useful..

Right, I know how to browse to it in the file manager, but I have no idea how to open it or copy it. If I tap on it I get asked whether I want to open it in 'another app' (other than what?) and if I click that I get offered the option to open it in OpenStore.............
I did install a text editor earlier, but the system doesn't seem to be aware.

...okay, someone else is helping me. But surely these things could be easier? I want to help but I feel so lost

New dmesg output (I hope) is here https://pastebin.com/Uh3Qsivu
Syslog is 14 MB and Pastebin does not accept that.

joolz

@Flohack said in short battery life on OPO (Bacon) with OTA12:

IPv6

Thanks for the tip! After following the instructions and a reboot, I get

phablet@ubuntu-phablet:~$ cat /etc/sysctl.d/30-ubports-disable-ipv6.conf

net.ipv6.conf.all.disable_ipv6=1

phablet@ubuntu-phablet:~$ ifconfig wlan0

wlan0     Link encap:Ethernet  HWaddr c0:ee:fb:9c:b8:e8  
          inet addr:192.168.178.29  Bcast:192.168.178.255  Mask:255.255.255.0
          inet6 addr: fe80::c2ee:fbff:fe9c:b8e8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:406 errors:0 dropped:1 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:69205 (69.2 KB)  TX bytes:15370 (15.3 KB)

phablet@ubuntu-phablet:~$ dmesg | grep -i ip6

[    2.586628] ip6_tables: (C) 2000-2006 Netfilter Core Team

phablet@ubuntu-phablet:~$ dmesg | grep -i ipv6

[    2.586565] Mobile IPv6
[    2.586844] IPv6 over IPv4 tunneling driver
[   17.546583] wlan: [860:E :HDD] hdd_wlan_startup: 9414: Registered IPv6 notifier

This probably means ip6 is still on, is that correct? I have no time to check the traffic now, but will keep an eye on power consumption.

flohack

@Moem ok you can zip syslog and put it to some download service maybe

Moem

@Flohack Sure, no problem, here it is:
https://workupload.com/file/2Tw2MZSNtqk

joolz

@joolz said in short battery life on OPO (Bacon) with OTA12:

@Flohack said in short battery life on OPO (Bacon) with OTA12:

IPv6

Thanks for the tip! After following the instructions and a reboot, I get

phablet@ubuntu-phablet:~$ cat /etc/sysctl.d/30-ubports-disable-ipv6.conf

net.ipv6.conf.all.disable_ipv6=1

phablet@ubuntu-phablet:~$ ifconfig wlan0

wlan0     Link encap:Ethernet  HWaddr c0:ee:fb:9c:b8:e8  
          inet addr:192.168.178.29  Bcast:192.168.178.255  Mask:255.255.255.0
          inet6 addr: fe80::c2ee:fbff:fe9c:b8e8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:406 errors:0 dropped:1 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:69205 (69.2 KB)  TX bytes:15370 (15.3 KB)

phablet@ubuntu-phablet:~$ dmesg | grep -i ip6

[    2.586628] ip6_tables: (C) 2000-2006 Netfilter Core Team

phablet@ubuntu-phablet:~$ dmesg | grep -i ipv6

[    2.586565] Mobile IPv6
[    2.586844] IPv6 over IPv4 tunneling driver
[   17.546583] wlan: [860:E :HDD] hdd_wlan_startup: 9414: Registered IPv6 notifier

This probably means ip6 is still on, is that correct? I have no time to check the traffic now, but will keep an eye on power consumption.

@Flohack that was it! After disabling ip6 and normal usage (about an hour on wifi, few calls, the rest of the time idling) and no charging, it went from 100% to 60% battery in a bit less than 24 hours which looks like what it did before OTA12.

Solved, thank you!

truscellino

The last two days I have been leaving the phone with wifi switched off (and manually back on, as and when needed only). Battery life has come back to "normal", so clearly there is something going on with wifi while phone is left idle.
I will now try the IPv6 trick. Thanks.

Aristid

Just tried to deactivate IPv6 on my OPO : battery still drained like crazy even when wifi is off.

Weird thing is sometimes when i reboot battery life is back to normal, and then out of nowhere it discharges super fast...

Edit : i just upgraded to OTA14, will see if it changes anything.

Aristid

@Aristid said in short battery life on OPO (Bacon) with OTA12:

will see if it changes anything

And it does not : battery still lasts a few hours... OPO spent the night in airplane mode, did not lose a single battery % but as soon as airplane mode is off battery melts.

Lakotaubp

@Aristid If your still getting issues with your OPO and everything is fully up to date and you are sure it's not the battery if you are on stable try RC and if on RC try Development and see if that fixes it.
If it doesn't you are best starting a new thread as this one is about OTA-12 and we are now on OTA-14 it will avoid confusing the issue. I will lock this topic now. Thanks for your understanding.