Lately my battery stats behaves a bit strange like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what could i do? :s I have tried different roms and kernels, now i'm on purity rom + m-kernel. Maybe a battery problem? I calibrated it with an app but unluckily it hasn't worked... Thanks in advance
Enviado desde mi Nexus 7 mediante Tapatalk
Battery calibration does not affect the actual amount of current drawn by the device - any device.
At best all it can do is make a slightly improved prediction about how much charge remains.
But on the N7 I don't believe it even does that. In any event, it will not change in the slightest little bit *when* your battery runs out of charge, nor will it perform some kind of voodoo magic where your tablet will use less current, either.
in the N7, there is a "fuel gauge" chip (TI BQ2745 ?) that monitors battery voltage and current in & out of the battery, from which it produces a "% charge" value directly from the firmware embedded in that chip ( and read by the kernel across an I^2C bus). There is no OS-level software which alters this.
The upward movement in apparent charge level is a little bit unusual, but it is not unusual for rechargeable batteries to show a "voltage rebound" when they have been operating with high current draw and then operated in a very low current mode (e.g. tablet sleeping). Perhaps that TI chip just isn't all that great at dealing with that "rebound" behavior.
The rest of your graph shows the battery draining about 42% of the time ( = 0.42*7.75 = 3.26 hrs).
During that time your battery graph says you lost about 40% of your charge.
The way I do math that works out to a full-scale "100% discharge time" of 3.26/0.40 = 8.1 hours.
That doesn't seem to be much to be worrying about.
Related
My note 3 battery is horrible I downloaded wake lock
Here are 2 pics
Any advice?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is another
My phone has been in my pocket all day not being used until just now when I made this post
I should also mention it is fully stock
looks pretty standard for stock to me. 5 hours for 23% of the battery? That means about 20 hours a cycle? seems very standard for stock.
If you want more then you gotta go custom ROMS and Kernels.
If your rooted use SET CPU to make phone clock speed 322-400 mhz when the screen is turned of.
But why is it awake so much?
Search for "AndroidOS Bug" and you'll get the answer.
Gesendet von meinem SM-N9005 mit Tapatalk
This bug really makes it hard to enjoy the note 3 as a whole. I was plagued by this pretty badly until recently I sort of found a workaround.
Some time ago I found out, that in offline mode the bug is not present. I came across it, when i was in our datacenter where the cell signal is a nightmare. I turned on offline mode and switched WiFi back on (thankfully we have a WiFi active there) and the battery drain was very low with active WiFi and bluetooth (headset connected) over a period of several hours.
I did still encounter the Android OS bug afterwards, but then once after my phone was fully charged, I put it into offline mode for some time (30 secs or one minute) and then switched back to normal and that day I had exceptional battery life (whole day = ~12h with some time checking, messaging and checking mail, with ~70% battery left) which i assume must be the actual battery life that the phone is capable of without bugs.
So long story short:
possible workaround for the Android OS bug: put phone in offline mode for ~1 minute, then back into normal mode
I would love to read if somebody tried this and gave some feedback.
Ok so I'm slightly panicking... I forgot to charge my phone 2 nights ago, so I went the next day from like 50% down to 4% maybe (awesome battery life coming from my Gnex!). Plugged it in to charge. Woke up 8 hours later and the phone was pretty warm, but fully charged. Well, I got in the car to go to work and the screen just went black when I tried to play some music and BT, then the phone rebooted. It was still kinda warm so I just turned it off for a half hour on the way to work. Left it sit on my desk all day (busy day) and start using it this evening. So far the phone has rebooted itself twice now on its own. I cleared cache and dalvik thinking it'd help after the first reboot. Is it possible somehow the full charge up and heat maybe broke something? My verizon dev edition is only a few weeks old!
My phone has never gotten more then a gentle warmth to it while charging - are you using the stock power adapter? If it got hot enough to damage it from charging then you should have it replaced.
It also might just need a full reset, but that will erase all data.
All smartphones have PMIC(Power Management Integrated Circuit) on their boards to prevent the battery from being overcharged and having too much current running through such that the battery would feel anything more than mild under the most stressful loads. If a phone(our Moto X) has Qualcomm's Quick Charge 1.0 and is pulling the full 1.1A from a battery at 20%, then the battery is going to feel warm as the current-draw is at its highest from 20% to 80%. Here's a line-graph comparing charge times to illustrate the point where Quick Charge 2.0 was being graphed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source
With regard to the OP's situation: I have no idea without a logcat file to say for sure.
Hello,
I've experienced a sudden change in battery performance.
What used to take around 50% of battery now takes around 85%.
It happened recently, around the same time I started working at a new workplace. The reception is horrible there, maybe that's the issue. However during the weekends, it is around the same.
I was on 4.4.2 stock when it happened and since then I've flashed it again once. I've also tried a couple of different radios (and enabled LTE) and I've always had franco kernel.
Brightness was always on Auto (which I shall turn off to experiment battery life) and wifi is selected to be off when the phone is off.
I have still a few more experiments to do, but I'm considering using warranty services. What do you guys think? It's clearly not as bad as some of the other battery issues I've seen on this forum, but it's quite the change for me. I bought this phone in July 2013.
Here is an example battery usage graph. Charging finished around 1 AM and left it unplugged over night. In the morning (~7 hours) the percentage was at 75%. (5% / hr) Throughout the day, I have used it for text messaging only and by 6 pm, it's at around 13%.
Thanks for taking the time to read my long post.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can check what drains battery with BetterBatteryStats. Google it and you'll find.
Thanks for replying.
I have tried that before an OS reset although I couldn't make much out of it. One main thing I noticed was a certain kernel wakelock which, after I googled, was responsible for LTE connectivity. Although this makes sense, I had good battery life even with the LTE chip being used (& auto brightness / wifi always on) prior to this battery incident. By good battery life, I mean 50-60% used by the end of the day
I just found a pretty interesting bug that causes my G935FD phone to be constantly awake after a full charge, but will happily go into deep sleep after I restart the phone after the full charge. It reflects in the GSam Battery monitor as well as the battery life.
Maybe someone who has issue with the phone constantly awake (or very high Android System battery usage) can try this trick out. My software version is:
Baseband: APD1
Build: APDQ
My phone is rooted if it makes any difference.
Here are some examples:
After 10 mins charging and before reboot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And after a quick reboot:
may b this is the cause
may be this is the cause of pathetic battery life on my phone. do u suggest a restart while still plugged in or after unplugging? Know any permanent fix for this?
drmrahul said:
may be this is the cause of pathetic battery life on my phone. do u suggest a restart while still plugged in or after unplugging? Know any permanent fix for this?
Click to expand...
Click to collapse
I reboot them after unplugging.
I've just found this work around recently (as you can see my pathetic average doze time per charge).
Will try this for a few days to see if it helps.
Have you tried to wipe cache ? cause i've had the exact same problem over and over again and in my case it only happened with wireless charger. After I wiped cache partition it never happened again.
It is google backup bug. Turn off google backup and it should be gone.
Or restart your phone after each full charge.
Edit: it affects other phones too
http://forum.xda-developers.com/nexus-6p/help/partial-wakelock-android-backup-t3363390
wollyka said:
It is google backup bug. Turn off google backup and it should be gone.
Or restart your phone after each full charge.
Edit: it affects other phones too
http://forum.xda-developers.com/nexus-6p/help/partial-wakelock-android-backup-t3363390
Click to expand...
Click to collapse
Wow this is a colossal bug.
Yeah, it affects two of my phones, S6 and S7 edge!
Note: this is a hardware fix by soldering a 1 kΩ 1% 0201 inch (0603 metic) into the main board; you'll need a bunch of tools, soldering skills andyour own responsibility if anything goes wrong.
Let me know if need any more info.
The symptom:
If you read the CPU or battery's temperature (any app) it will show 2 to 3 times the real temperature. On my case, it should be reading around 25 ºC (I had a similar working Pixel nearby) while it was showing around 60 ºC. The main problem with this is that the phone will be throttling all the time while perfectly cold. I did not measure any CPU performance, but the battery wouldn't charge more than 10-20 mA per hour while switched off.
The problem:
I guess that while disconnecting the battery I forced a resistor which is (AFAIK) related to the CPU & battery temperature measuring circuit. I had a faulty main board around so I could compare them. Fortunately I found a missing resistor and I could measure it on the faulty MB. The part you will need is a 1.00 kΩ 1% 0201 inch (0603 metic) thik film resistor. I've use a Vishay CRCW02011K00FKTDBC.
The solution:
Just solder another one.
I'm not going to give you much soldering details as I think this out of scope and you'll notice right away if you feel you can do it once you look how tiny these resistor are.
I've used:
- very small tweezers:
- very small 0.2mm soldering tip:
- head mounted magnifying
- etc.
Here is, red highlighted, the resistor that was missing and now soldered. It's on top of battery's socket:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you so much. I can't believe that I can eventually find the reason of this.
I have a google pixel also got this problem after battery replacement in 2017-2018.
I just took a look, the same resistor is missing on my main board.
Sadly, it is really really very very small, I don't have the skill to replace it.