Develop Bugs

Android battery calibration, what are other people experiencing except me?

Well members,
I really want to know who has their battery percentage the same as in winmo. I know it has a issue with the battery driver, but still i am curious.
My battery.capacity=4462 Units.
Current percentage in Android 41% at the moment
Current Units in Dmesg 2988Units
After restart in Winmo it says 53%
If I calculate this, (2988/4462)*100= almost 67%
Someone knows what i am doing wrong?
PHP:
I will charge my battery again tonight, plug usb out, read units, change Units again in default.txt. Then I will keep for myself updates trough the day of the current data. Will post again tomorrow with updates.
Hope to hear what other people are experencing
Don't blame my poor english, Firefox English dictionary isn't downloaded/installed yet

battery
Yeah is really not understandable of how to calibrate the battery, iv been trying it for the past 2 weeks...and i still have not get it right! well..i got 4320

My battery reports completely wrong in android, to the point where it's 30-50% left then dies as it's really flat!

Hmm,
Code:
Try to use this line in default.txt if you don't got it yet
board-kaiser-battery.battery_capacity= ****
**** stands for the unit you get in with Dmesg in terminal of android after a full charge.
I can say that doesn't even is correct for me.
But I Tried another value. I read (translated) on japanese forum dat you have to put the mAh instead of units.
So I tried with 1350 (Of my Kaiser160).
Now my android shuts of when it's 15% instead of 59%. He also said something like, try to double the value. I am testing now with the value 2700
You guys should try :O
I've to say, after changed to 1350, i had a more realised idea how android does with the battery. I can say that android sucks more battery than winmo.

battery
assangflexx said:
Hmm,
Code:
Try to use this line in default.txt if you don't got it yet
board-kaiser-battery.battery_capacity= ****
**** stands for the unit you get in with Dmesg in terminal of android after a full charge.
I can say that doesn't even is correct for me.
But I Tried another value. I read (translated) on japanese forum dat you have to put the mAh instead of units.
So I tried with 1350 (Of my Kaiser160).
Now my android shuts of when it's 15% instead of 59%. He also said something like, try to double the value. I am testing now with the value 2700
You guys should try :O
I've to say, after changed to 1350, i had a more realised idea how android does with the battery. I can say that android sucks more battery than winmo.
Click to expand...
Click to collapse
Hi there, well iv tried the above instructions, but i found out something is strange, i deleted the batterystats.bin and then make sure that the board-kaiser-battery.battery_capacity= 1400 (my battery is 1400) i adb pushed it to my device....but strangely when i reboot....it changes back to 2700 automatically....i think this is the reason why we still cannot calibrate our battery for now...since as soon as my battery reaches down to 20% and suddenly 4% then shuts off...
Perhaps do you guys think that to keep our kaiser's stanbby time longer rather buy an external battery charger and make sure that battery is charged up fully.so that we can utilize the battery fully.

i think for now we should just try an carry our chargers with us say to work or school..and charge it over night....
Usually i wouldnt charge my phone for bout 2 days but it will last..but now i realieze its a must if ima use android..
Cheers

i never trust the battery status when charging.
if I am looking for a full charge I wait until dmesg reports a charge of less than approx 30mA. if it shows charge at 100/100 and it still is showing over 100mA then it is not done charging.
also if it is showing less than 30mA and a charge of less than 100/100 it really is done charging. don't wait for 100/100 if it is done charging.
as far as battery usage is concerned, one thing to not as far as a difference between winmo and android:
winmo shuts down many services when sleeping.
such as in winmo if you are playing music and it goes to sleep, music shuts off.
and same for wifi.
android doesn't seem to shut of anything except the screen.
maybe there is settings for what is to be run while sleeping.
I had a program in winmo that allowed you to turn on or of services during sleep.

mnjm9b said:
i never trust the battery status when charging.
if I am looking for a full charge I wait until dmesg reports a charge of less than approx 30mA. if it shows charge at 100/100 and it still is showing over 100mA then it is not done charging.
also if it is showing less than 30mA and a charge of less than 100/100 it really is done charging. don't wait for 100/100 if it is done charging.
as far as battery usage is concerned, one thing to not as far as a difference between winmo and android:
winmo shuts down many services when sleeping.
such as in winmo if you are playing music and it goes to sleep, music shuts off.
and same for wifi.
android doesn't seem to shut of anything except the screen.
maybe there is settings for what is to be run while sleeping.
I had a program in winmo that allowed you to turn on or of services during sleep.
Click to expand...
Click to collapse
yep...you are right....maybe we should just focus on dmesg for now...by the way, do you guys have the same problem as i have...20% then suddenly drops to 4% then shuts off?

twinklesam123 said:
yep...you are right....maybe we should just focus on dmesg for now...by the way, do you guys have the same problem as i have...20% then suddenly drops to 4% then shuts off?
Click to expand...
Click to collapse
i dont have that problem..however today, i charged to 100 percent and talk to my gf on the phone for about an hour..it went down to about 40 percent..i set it down and didnt touch it for about 20 minutes..and it went up to about 70 percent..very weird

Yes, i can tell you, in the settings under connection (i think, i have dutch android language) you can define a setting that wifi goes to sleep after your screen sleeps.
Code:
Also,best way to use android is that you have to
1. fully charge your phone in android and keep the powercable on it,
2. look in dmesg for the units. when te units aren't getting bigger, than that's the last one that is charged.
3. write down or do something with your mind :D
4. restart to winmo, KEEP POWERCABLE ON
5. change and/or put a line to your default.txt "board-kaiser-battery.battery_capacity= ****"
change **** to your units you have written down
6. after you changed units, start to android.
But still it doesn't is good yet. I experienced that 1350 value is the most effective one. When android said 15%, i tought lets restart and look what winmo says. winmo was at 1%.
Also, i was a little cocky and without 100% battery i started android. I can say, it took ages that 100% was changed to 99%. Also you never know when battery is going to die
Maybe someone can do something with this.

Battery
i think for now...we should just look at the charge in dmesg....which is the most accurate telling for now...

twinklesam123 said:
Hi there, well iv tried the above instructions, but i found out something is strange, i deleted the batterystats.bin and then make sure that the board-kaiser-battery.battery_capacity= 1400 (my battery is 1400) i adb pushed it to my device....but strangely when i reboot....it changes back to 2700 automatically....i think this is the reason why we still cannot calibrate our battery for now...since as soon as my battery reaches down to 20% and suddenly 4% then shuts off...
Perhaps do you guys think that to keep our kaiser's stanbby time longer rather buy an external battery charger and make sure that battery is charged up fully.so that we can utilize the battery fully.
Click to expand...
Click to collapse
try to put these lines in sysinit.rc:
#battery patch
chmod 777 /sys/module/board_kaiser_battery/parameters/battery_capacity
write /sys/module/board_kaiser_battery/parameters/battery_capacity 1400

I'v changed it to 1350. It was charged properly and drop to 4% from ~10%, so nearly ok. But when connected charger it's full in about 10 minutes????
Edit: After dischargine (5 minutes), it charges probably normally.

working...
tiagoclc said:
try to put these lines in sysinit.rc:
#battery patch
chmod 777 /sys/module/board_kaiser_battery/parameters/battery_capacity
write /sys/module/board_kaiser_battery/parameters/battery_capacity 1400
Click to expand...
Click to collapse
Thanks! i think it worked now!my battery now runs down normally...

How long everybody using your Kaiser battery? I can use 3 days in Winmo but it could not exceed 1,5 day in Android (NAND) :-(

I have the same as you.
But i stopped using Android on ma phone. I'am out with Winmo, don't want to use it anymore. And android dies just quickly.
Am using now en Nec N343i
Will try android again when new updates or new kernel arrives

yo ppl...now most of the time i can figure this type of stuff out....but this time im kinda lost....i edited the sysinit.rc file....also the battery_capacity file.....im running poly 2.1g on NAND but after i reboot the phone....does nothing.....any tips or site with a little more info...?? thanks in advanced for any help

Battery problems on polymod 2.1 gamma
tiagoclc said:
try to put these lines in sysinit.rc:
#battery patch
chmod 777 /sys/module/board_kaiser_battery/parameters/battery_capacity
write /sys/module/board_kaiser_battery/parameters/battery_capacity 1400
Click to expand...
Click to collapse
Hi,
I have polymod 2.1 gamma with all updates (UPDATE 15 Mar 2010, UPDATE 18 Mar 2010, UPDATE 23 Mar 2010) and the kernel from "ponack.net/poly/BT_Update/" installed on NAND (Tytn II). It runs really smooth, but I have a problem with my battery.
I have written the battery patch from tiagoclc in the sysinit.rc before I installed on Nand (but with value 1350 from my battery). But is this enough or do I have to delete a *.bin file from battery? I hope someone can help me with a description.
I have seen a fix for "Myn's Warm Donat" here:
forum.xda-developers.com/showpost.php?p=6243182&postcount=306
Is there also a fix for Eclair 2.1 available? Or does someone have a "complete" description for this battery problem? My Batterie is a few hours on 100% with this battery patch and I can not charge it. But this could not be true.
I hope someone can help me.
MT

Maybe kernel problem.
I'm experiencing the same problem as everyone.
Lately my battery suddenly drops from 100% to 4%.
When I put to charge, it reaches 100% very fast. Should reach only 5%
I think it can be a problem in the kernel.
Now, i'm trying to solve it. If I find something I'll share with you
I can not determine which kernel brought the problem...
23/04 - 16:16 (GMT-3 - Rio de Janeiro) - Trying an old kernel
23/04 - 17:00 - Nothing. But came to the conclusion that the problem is with the battery.
Battery really "thinks" its 100% charged, since it accepts flash a nbh without the need of the phone is charging. And this only happens when the battery is at least 50% charged...
(sorry about my english. I'm brazilian and still learning english)
Some threads and posts about battery:
http://forum.xda-developers.com/showthread.php?t=661588
http://forum.xda-developers.com/showthread.php?t=644453
http://forum.xda-developers.com/showpost.php?p=5599516&postcount=33
We must concentrate everything in one thread!!!
We have to use search

I have set 1350 in sysinit.rc and it seems to be ok, but before every charge I have to reboot to charge it fully. then it discharges nearly fine - there are some fluctuations beetween 2-3-4 percent.

[Q] My desire drains battery 3x faster than other desires, why?

Hi, I had my desire serviced for battery unrelated problems. When it came back with a new MB (or so they state) my battery woes began. My desire eats the battery 3-4x faster that before. Even if I swap batteries with my friends, who also has a Desire, the one in my phone lasts only 12hour on Stand-by in airplane-mode with display Off!
I've tried running battery benchmark and get around 7000 sec (with my and friends battery), while my friend gets 20000+ with both batteries.
So obviously the problem is my phone. After the battery problem the service changed my MB again (the phone went dead) and the new MB eats the battery again!
What could be the cause? What is inside the phone besides the MB, battery and display?

are you using a custom rom? some of them are very heavy on battery life and drain it quickly

default HTC android 2.2

I got the exact some problem =/ it's a hardware bug, even on different ROMS my battery goes from 90% 10% in just 5 hours, without even touching the device...

Check battery health:
Open dialer, type *#*#4636#*#* > Battery information.

maybe your calibration is messed up, try using BatteryCalibration app

Please use the Q&A Forum for questions Thanks
Moving to Q&A

[Q] Strange battery drain when screen on.

Hi everyone,
sometime ago I started having strange battery drain on my DHD. It only happens when the screen is on.
When screen is off the average battery drain is only around 2-4mA and I lose around 5-7% of battery in 8 hours.
However when I turn the screen on battery fully drains in around 3-4 hours and usage is around 150-450 mA.
Is is normal behaviour?
When I was using stock Sense when I first got the phone I did not have that problem. I wanted something faster and I have installed CM7. Then I wanted to get back to Sense and I have installed Android Revolution HD (Full wipe between each install). At that time battery was still great. Then I wanted new Sense and I have installed CoreDroid 9.3 and the drain I have described started at that point. I thought maybe I had a bad install and I have reinstalled CoreDroid. The problem was still there. So I decided to go back to CM7 which I knew was working fine before but the drain is still here and only when screen is on. I have tried different radios and kernels, working with and without SD card, different brightness settings, wifi on and off, 3g on and off and nothing makes any difference, the drain is still there even in airplane mode. I have tried couple of different batteries but even that did not help, the phone is still draining when screen is on.
Does anyone have the same problem? Is it hardware at fault?
I have tried finding the solution but no one else seems to be suffering from described problem. Also the phone switches itself off at 3600mV. I have read that most of the androids switch itself off at 3200 mV. Is it nomal for DHD? I have recalibrated battery and tried all the possible solutions available on the web.
Does anyone know what is going on with my phone?
My current setup:
Android version: 2.3.7
Baseband version: 12.54.60.25U_26.09.04.11_M2
Kernel Version: [email protected]
Mod version: CyanogenMod-7.2.0-RC1-ace
I will be really grateful for any help.
Thanks,
Greg

I can't help you, but can say that If I take my phone off charge at 100%, I can go out the front garden, to have a cigarette for literally 3-5 mins.....and my battery has gone from 100% down to 88-90% ! !
That's with screen dim as low as it will go, WiFi Off, Data OFF, Gps OFF, Auto Sync OFF...just literally 3-5 mins browsing through folders using ES File Explorer...not playing any videos or anything.
I think it's a general smart phone thing, the bigger the screen, the more power the processor etc etc, the more power it's gonna suck.
As Technology moving as fast as it is, give it a year or 2 and I reckon there will be some crazy battery invention that gives you days and days of battery use and still have loads left.
Matt

Hi Matt,
thanks for the reply. I guess I will have to live with that until my next upgrade.
At least most of the time I am somewhere near wall socket so somehow I manage, but it is annoying to see 50% off battery drained in an hour whenever I play any game on it.

Random reboot problem.

Hello, I've just recently revisited my old android and discovered it rebooting randomly. A further look into this more into the hardware level, would need some statistics from users. I've installed Current Widget, and I've noticed the resets happen when my battery is quite low (20% (3.6v)). So i'm wondering if the problem is with either a bad battery (non linear voltage drops), or more into the battery circuitry myself. I've included the battery voltage I had at the time of the occurrence, because I'm in the middle of a battery calibration, but i do know that it still had plenty of 'juice' left in it because i used it for anther 20 minutes before plugging it in after the random reboot happened. It has done this in the past but this is the first time I've decided to log the reboot.
If anyone suffers from this (not the reboot loop), if you could, could you check your battery voltage level and possible mA amount before and after the reboots happen. (just mark the time down and refer to the logs later. Thanks!

It sounds like a battery issue to me. A new battery is £9 or around $15 max
Did I help you? Hit THANKS!
Galaxy S3 (BEAST, stock)
Desire HD (Retired, REVOlution)
Galaxy Note 10.1 (Big Bad Wolf, stock)

Dark-Show said:
Hello, I've just recently revisited my old android and discovered it rebooting randomly. A further look into this more into the hardware level, would need some statistics from users. I've installed Current Widget, and I've noticed the resets happen when my battery is quite low (20% (3.6v)). So i'm wondering if the problem is with either a bad battery (non linear voltage drops), or more into the battery circuitry myself. I've included the battery voltage I had at the time of the occurrence, because I'm in the middle of a battery calibration, but i do know that it still had plenty of 'juice' left in it because i used it for anther 20 minutes before plugging it in after the random reboot happened. It has done this in the past but this is the first time I've decided to log the reboot.
If anyone suffers from this (not the reboot loop), if you could, could you check your battery voltage level and possible mA amount before and after the reboots happen. (just mark the time down and refer to the logs later. Thanks!
Click to expand...
Click to collapse
You can goto Recovery then wipe davik cache or/and wipe cache +davik cache and reboot to check if it works

Horrible battery life on newish S4 Mini ("best" performance <3h)

Hey guys,
after dropping my beloved Nexus 4 to the concrete floor in May, I bought a new S4 mini in the electronic market because of it's decent size and all the fuzz about having a very good price-performance-ratio.
After a few weeks I already was fairly disappointed.
On an average work day (without WiFi) and little use (~30min OSD) the battery wouldn't last a full day. I tried the usual things like turning off GPS, bluetooth and using Wifi whenever possible (turning it off, when not in range), etc. I also used the App greenify which boosted my deepsleep in Wakelock Detector to stable 85+%.
When using GMaps/navigation my phone is getting hot (~50°C) and battery is drained within minutes. When trying to navigate out of the city (<15min navigation) one day my phone was discharged within 3 hours after a full charge. I got Wakelock Detector, Better Battery Stats and Battery Monitor Widget installed.
The only thing I found out, that when I am connected to Wifi the drain is a lot lower 1-2%/hour compared to when I am using 3G/H+ which results in 7-15%/hour (both when not using the phone), although there is no problem with signal quality. Recently my phone started to bottoming out rly hard when hitting the 20% mark. From there I can watch the battery dropping to 0% within a few minutes.
Things I tried so far:
- turning off features that are not in use (GPS, bluetooth, Wifi when not in range)
- make sure phone gets into deep sleep/greenify apps
- recalibrate akku
- reduce brightness & disable auto-brightness
Setup:
GT-I9195 bought in May 2015 from electronic market chain
CM 12.1 (Android 5.1.1, serranoltexx)
Standard CM Kernel
Baseband I9195XXUBML4
I can provide Screenshots from BMW, WD and BBS. Any ideas how to solve this or what else I could do?

Probably you should use something like better battery stats, to check
- if a service is going mad, then turn it off with disable service to test (most times happens with unclean flash)
- if you have an app with wakelocks
If you can't find anything that way, might be a hardware fault.

Personally if I came across this problem I would return the phone to stock Android and do some tests, see if the same happens again. CM12.1 can have issues across different same model phones. Try the Samsung Phone Info app to see how old your phone is. I'm guessing it was second hand? Some older revisions of the Mini had battery problems. Maybe a new battery is needed? Maybe.. As for the battery draining 20%-0% in minutes I have also suffered this on a brand new March 2015 device. Not all the time though it only happens with randomly once a week. But I put that down to the battery not been fully calibrated and then drained and recharged over the next 3 4 days, as I use a spare battery and swap out the batteries regularly which means my battery is very rarely calibrated.
All that said though I can easily get through an entire day if not 2. And using stock I'm able to get 4 and a half hours on average every time, maybe 4 hours of screen on time when using 3G a lot and GPS etc.

NNNexX said:
Hey guys,
When using GMaps/navigation my phone is getting hot (~50°C) and battery is drained within minutes. When trying to navigate out of the city (<15min navigation) one day my phone was discharged within 3 hours after a full charge. I got Wakelock Detector, Better Battery Stats and Battery Monitor Widget installed.
The only thing I found out, that when I am connected to Wifi the drain is a lot lower 1-2%/hour compared to when I am using 3G/H+ which results in 7-15%/hour (both when not using the phone), although there is no problem with signal quality. Recently my phone started to bottoming out rly hard when hitting the 20% mark. From there I can watch the battery dropping to 0% within a few minutes.
Click to expand...
Click to collapse
I have had the same problem as you.
I return twice my phone to vendor. But they could do anything.
I solved it with undervolting and underclocking my phone (only the low frequency).
I read from someone, you can undervolting 150 millivolt.
My experience, is undervolting 125 milivolt. and underclocking the low frequency at the minimum.
You didn't feel any difference, behalves that the phone is cooler and battery live is better.
My WiFi and Bluetooth are always on. I don't have to recharge my phone during the day.
It is so effective en transparent that I don't understand why Samsung didn't do it natively.

Hey,
I tried to apply some of your advice and flashed the newest stock rom for S4 Mini (Kitkat ...COE4).
In that process I recognized that the Baseband is not updated by CM and that the one that was installed when I bought it was fairly old (from 2013). Do you think that this might be part of the problem? (I sort of hate the Samsung Rom)
This week when working and not having Wifi all day, I managed to get 2h of SOT and still had around 25% left which I couldnt have gotten before imo. I only lose 1-4% per hour when the phone is not used. But still thats not pretty good, when ur saying you can get 4h with GPS and everything. I also didnt use GPS. And today when I restarted my phone it just went from 40-ish % to 15% without any reason. Any more ideas?
I installed BetterBatteryStats today and will try to give some more insight the next days. Wakelock detector said that I had 85% deep sleep (timeframe 1 day 2 hours).
Try the Samsung Phone Info app to see how old your phone is. I'm guessing it was second hand? Some older revisions of the Mini had battery problems. Maybe a new battery is needed?
Click to expand...
Click to collapse
No I bought it new from a electronic store (Media Markt). The app says that is was made on Oct 19th 2014 in Vietnam and that it is original/not refurbished.
How much do you gain by undervolting (SOT or % per hour when idle)?
How do you do it?

maybe the best way is to downgrade by flashing CM11 for example ...
(another way with stock + Alexax kernel + own debloat&freeze ... )
I have the same consumption problem with Resurection Remix LP too ..... very strange !
Lollipop is supposed to be less angry than Android 4.X.X ... but it seem have problem somewhere for our S4-mini sources maybe ,i don't know ...

This night I did some BBS tests:
Setup:
Stock Rom I previously installed (see posts above)
charged phone during evening
set up custom timepoint before I went to sleep
WLAN disabled
all apps greenyfied except those I deemed significant that they keep running (Whatsapp, calendar, Swiftkey, BBS, BMW, etc). Forgot newly installed app hoomn.
I had to upload the logfile to pastebin because it was too long for the xda forum: pastebin.ca/3256568 (I am not allowed to post URLs, sorry)
I lost 14% of battery during 9hrs (-1,6%/h). That's probably not too bad?
93% deep sleep, 33min awake time
Weird things I discovered/things I did not understand:
- negative Voltage loss?
- Wifi runtime 100% although I disabled it
- dominant wakelocks (count > 100, all of them < 30s): Alarm Manager, RILJ1, *net_scheduler*, GCM_CONN, ContextManagerWakeLock, Event Log Service, AlarmManager (com.sec.spp.push.Samsung Push Service), SyncLoopWakeLock, GCM_HB_ALARM
- dominant KWLs (count > 100): ril-fd (25min), bam_dmux_wakelock (13min), radio-interface (7min), PowerManagerService.WakeLocks (3min), mmc1_detect (1min), alarm_rtc, alarm, sec-charger-monitor, smdcntl0, pm8921_soc_lock, power-supply, KeyEvents, smsm_snapshot, qmuxd_port_wl_0, qmuxd_port_wl_1, smdcntl1, mmc0_detect
- Alarms (>20): ccc71.bmw (Battery Monitor Widget), android, com.google.android.gms, com.sec.spp.push
any ideas/assessments?