Battery life

[adfh]

Hey all,

Got my Cosmo late last year, and of late have noticed it draining through the battery a LOT faster than previously.

I use my Cosmo a LOT. Dual screening infront of the TV, car sat nav (the Planet car kit is the most solid car cradle I've ever used), Tidal streaming etc. etc. I don't leave it connected to the charger, and generally charge to 80%. Up until about a month ago, I could easily get a day plus before needing to charge. I have normally used the supplied Cosmo charger to charge it, but also have a USB C car charger (Belkin), a Huawei charger (also USB C, from my old Nexus 6P), and a Lenovo charger (USB A).

Now.. it's draining a LOT faster.

AccuBattery suggests that Firefox, phone calls etc. are all taking a lot more power.. though given that the native battery app doesn't report on individual app usage, I'm going to guess that AccuBattery guesses based upon active process + BMS overall drain reported, and perhaps it's something else sucking the battery dry faster.

I'm running v22 of the firmware, and run with CODI and keyboard backlight off most of the time (unless I want to use NFC or the second USB port, it stays off). Upgrading CODI was the usual hell (Airplane mode, NFC off, BT off, WiFi off, DnD on) and it's still telling me to update the firmware even though I'm apparently running the latest version.

Have I just hit the cycle limit on the battery - or is something else afoot?

Edit: It seems, besides the fact that there's never been proper per-app power utilisation built into the Cosmo, that its battery estimation calibration relies on it more frequently being charged to 100%. After I charged it using a slightly slower charger to 100%, and I unplugged it, it sat at 100% for around 30 minutes of active use before I stopped using it and went to bed. When I woke up, the rate of charge decline was also significantly slower. This suggests the battery management system is cutting some corners and can lose track of where non-extreme charge states are.

[akrus]

Hey all,

Got my Cosmo late last year, and of late have noticed it draining through the battery a LOT faster than previously.

I use my Cosmo a LOT. Dual screening infront of the TV, car sat nav (the Planet car kit is the most solid car cradle I've ever used), Tidal streaming etc. etc. I don't leave it connected to the charger, and generally charge to 80%. Up until about a month ago, I could easily get a day plus before needing to charge. I have normally used the supplied Cosmo charger to charge it, but also have a USB C car charger (Belkin), a Huawei charger (also USB C, from my old Nexus 6P), and a Lenovo charger (USB A).

Now.. it's draining a LOT faster.

AccuBattery suggests that Firefox, phone calls etc. are all taking a lot more power.. though given that the native battery app doesn't report on individual app usage, I'm going to guess that AccuBattery guesses based upon active process + BMS overall drain reported, and perhaps it's something else sucking the battery dry faster.

I'm running v22 of the firmware, and run with CODI and keyboard backlight off most of the time (unless I want to use NFC or the second USB port, it stays off). Upgrading CODI was the usual hell (Airplane mode, NFC off, BT off, WiFi off, DnD on) and it's still telling me to update the firmware even though I'm apparently running the latest version.

Have I just hit the cycle limit on the battery - or is something else afoot?

Edit: It seems, besides the fact that there's never been proper per-app power utilisation built into the Cosmo, that its battery estimation calibration relies on it more frequently being charged to 100%. After I charged it using a slightly slower charger to 100%, and I unplugged it, it sat at 100% for around 30 minutes of active use before I stopped using it and went to bed. When I woke up, the rate of charge decline was also significantly slower. This suggests the battery management system is cutting some corners and can lose track of where non-extreme charge states are.

I have the same, now charging it during the day as it reaches 15% by 4pm. Also recently it rebooted and after the reboot was showing 1% battery left (although it was ~50% before), so maybe it's just inaccuracy in reporting?

[cam1965]

Hey all,

Got my Cosmo late last year, and of late have noticed it draining through the battery a LOT faster than previously.

I use my Cosmo a LOT. Dual screening infront of the TV, car sat nav (the Planet car kit is the most solid car cradle I've ever used), Tidal streaming etc. etc. I don't leave it connected to the charger, and generally charge to 80%. Up until about a month ago, I could easily get a day plus before needing to charge. I have normally used the supplied Cosmo charger to charge it, but also have a USB C car charger (Belkin), a Huawei charger (also USB C, from my old Nexus 6P), and a Lenovo charger (USB A).

Now.. it's draining a LOT faster.

AccuBattery suggests that Firefox, phone calls etc. are all taking a lot more power.. though given that the native battery app doesn't report on individual app usage, I'm going to guess that AccuBattery guesses based upon active process + BMS overall drain reported, and perhaps it's something else sucking the battery dry faster.

I'm running v22 of the firmware, and run with CODI and keyboard backlight off most of the time (unless I want to use NFC or the second USB port, it stays off). Upgrading CODI was the usual hell (Airplane mode, NFC off, BT off, WiFi off, DnD on) and it's still telling me to update the firmware even though I'm apparently running the latest version.

Have I just hit the cycle limit on the battery - or is something else afoot?

Edit: It seems, besides the fact that there's never been proper per-app power utilisation built into the Cosmo, that its battery estimation calibration relies on it more frequently being charged to 100%. After I charged it using a slightly slower charger to 100%, and I unplugged it, it sat at 100% for around 30 minutes of active use before I stopped using it and went to bed. When I woke up, the rate of charge decline was also significantly slower. This suggests the battery management system is cutting some corners and can lose track of where non-extreme charge states are.

I have the same, now charging it during the day as it reaches 15% by 4pm. Also recently it rebooted and after the reboot was showing 1% battery left (although it was ~50% before), so maybe it's just inaccuracy in reporting?

Me too. V23. If using wifi , battery drains fast. In airplane mode battery life is good.

[Daniel W]

To the best of my knowledge, there is no easy way to directly measure the charge level of a Li-ion battery. Its voltage only gives a very rough idea, which might explain why the battery display on a newly restarted Cosmo can be so far off from reality. I would guess more expensive phones has a bit of hardware in the battery, keeping track of this across restarts, while the Cosmo might use some cheaper software solution, maybe?

Knowing the nominal battery capacity (which decreases semi-predicatably as the battery ages, further complicating things) and tracking the energy flowing out of and into it when used and charged, one can indirectly keep track of the approximate charge level. But small errors adds up over time, making the approximations ever less reliable. Since it is posssible to mesure when a Li-ion battery is full, the meter can use that to reset itself to 100%, which may suggest it might be a good idea to charge to 100%, and leave it on the charger a bit longer, just to make sure, maybe once a month or so. I tend to do this once in a while, simply by forgetting I've put my Cosmo on the charger...

To me, it seems, the battery draw always goes up a bit for a while after an OS update. This makes me think Android might be doing some auto-optimization, where the OS learns the habits of the user, to better figure out which commonly used processes to keep in RAM, rather than keep reloading them. If this is done from scratch after an OS update, it may also party explain why it seems to take a while for my battery draw to settle down after each update.

[dmontes]

Hi, my Cosmo also had too high battery consumption, so I tried to isolate the cause as the statistics of battery consumtion are not available.
  First is of course codi, it takes a lot of battery, turned it off to see the improvements but still too little battery.
  I turned off almost all the software, all planet and google software that you are allowed to disable without root, did not make such a huge difference (+15% approx).
  To continue trying system app disable capabilities are needed, if your cosmo is rooted you can disable system apps but when restarting they are back, the way I used was through TWRP (unofficial), installed it on the second boot (renaming to twrp.img and using cosmo installer), when booting to twrp it has system privileges, so in twrp mount system and rename system apps (in priv-app folder) from *.apk to *.bak. I started with the google core services (GmsCore) another (+10%) the codi updater (STFlash) almost no difference with this one but it is a little annoying. Finally Baidu_Location and this is the one that gets the big price (+40%).
  So right now my cosmo has disable all no major google software, all planet software, baidu_location and stflash and it goes up to 5 days of normal phone use, 3-4 phone calls a day, 5-6 emails, some random web browse and 10-15 min of video a day.

  The question I have in mind is what could happen with a clean android like AOSP?

[Daniel W]

Um... excuse a perhaps ignorant question, but what, precisely, IS "Baidu_Location" and what particular benefits is it supposed to provide Cosmo users with? I know the onboard GPS is compatible with the satellite navigation system BeiDou, but Baidu is, as far as I know, a search engine, and related services, mainly serving east Asia. What important benefit would a user in, say, Europe get in return for such a hefty amount of battery power? Is it a part of the Planet Android build? Is there some less invasive means to see if is running and, if so, disable it?

[Zarhan]

It seems you can issue "killall com.baidu.map.location" in rooted termux. The process will not come back if you don't activate location service.

[cam1965]

Hi, my Cosmo also had too high battery consumption, so I tried to isolate the cause as the statistics of battery consumtion are not available.
  First is of course codi, it takes a lot of battery, turned it off to see the improvements but still too little battery.
  I turned off almost all the software, all planet and google software that you are allowed to disable without root, did not make such a huge difference (+15% approx).
  To continue trying system app disable capabilities are needed, if your cosmo is rooted you can disable system apps but when restarting they are back, the way I used was through TWRP (unofficial), installed it on the second boot (renaming to twrp.img and using cosmo installer), when booting to twrp it has system privileges, so in twrp mount system and rename system apps (in priv-app folder) from *.apk to *.bak. I started with the google core services (GmsCore) another (+10%) the codi updater (STFlash) almost no difference with this one but it is a little annoying. Finally Baidu_Location and this is the one that gets the big price (+40%).
  So right now my cosmo has disable all no major google software, all planet software, baidu_location and stflash and it goes up to 5 days of normal phone use, 3-4 phone calls a day, 5-6 emails, some random web browse and 10-15 min of video a day.

  The question I have in mind is what could happen with a clean android like AOSP?

Please, what version of twrp you are using ? Mine from Ninji asks for a password with v23 firmware. With v19 it was OK. Thank you.

[dmontes]

I used Ninji twrp, and it does ask for a password when trying to mount Data partition, but for System partition no problem mounting, also of course there are other methods, but this one does not require root as twrp has the correct rights to modify System.
What is Baidu_location doing in our machines is unknown to me, first time I was aware of this software was after changing the sim, a message came out asking for permission for the software, but to my understading this software is not needed at all.

[cam1965]

Thank you so much !

[cam1965]

Even if I delete the Baidu_location.apk file  from /system/priv-app, the system restores it if booted in non rooted android. ( I have checked it in the mentioned directory and the file is there ).  But if you boot in rooted android the baidu_location apk is not in the folder /system/priv-app. I did the same in magisk with debloat with airmail and Digital  Wellbeing and the apks is only removed in rooted android. In the non rooted android the apk file is there . So, something restores the apk if booted in non rooted android. Is there a way to get rid of this apk in non rooted android ? Thank you.

A workaround  that I did to not run some apps. ( uninstall digital well being , airmail and baidu location ).
Needs a computer and adb installed.

adb shell pm uninstall -k --user 0 com.google.android.apps.wellbeing
adb shell pm uninstall -k --user 0 com.gemini.airmail 
adb shell pm uninstall -k --user 0 com.baidu.map.location

[dmontes]

It seems that it is using a dual partition system, when rebooting restores the daily partition with the backup. I did not really research how exactly it works but as an example if you delete a system apk file on a rooted android when rebooting the apk is restored.

[vldmr]

On my unrooted device I just disabled "Air mail" in application settings and it does not show up in my laucnher (tui) any more. I also disabled "Digital wellbeing" - this did not show in launcher before, but after disabligng the related setiing section is inactive.

[Ralph B]

Non-rooted Android here. Battery now lasting about 4hrs max. Cover display noticeably warm to the touch, almost hot, although turned off. What can be done?

[cam1965]

@ Ralph B : If you have linux installed , you can check how long  is the battery life in linux. If not, maybe  a fresh android reinstall can help. Please install an antivirus like norton. Maybe a malware is running in background. Good luck.