Database Info

[i9003]xxkb3 battery icon is misleading not updating the status.

Well after 2 days of testing the xxkb3 battery usage which I have been talking about as great is a false perception, whats happening is that the battery indicator is not actually updating the real status thus showing good battery life.
I reported earlier that in ideal mode 12hrs night time its only consuming 2% that's not true, whats happening is that the moment i start using the handset in morning just after few mins I noticed a sharp drop in battery status I got confused the 1st day of test so did it another day & noticed the same behavior, hence installed battery Notifier (big text) which shows directly in the status bar & that showed a mismatch since this morning.
Here are few screenshot at 80% actual battery the icon is still showing me full charge to make me believe that its a good battery......now is it a bug in xxkb3 which should be reported or any way to correct it? DDKB1 which i was using earlier never had this problem.
The Green text at left is the battery notifier.

Dude i dont think its a problem.
The indicator changes according to the % of battery remaining. The default status indicator will have only a total of 4 to 5 stages of indication.
above 80 - state 1
above 60 - state 2
above 40 - state 3
above 20 - state 4
less than 10 - state 5.
For example
if % is above 80 , then the indicator will show full.
if it is in between 60 to 79 then it will show some changes.
Im using battery status widget to monitor battery as it gives more info on the battery status.

if % is above 80 , then the indicator will show full.
if it is in between 60 to 79 then it will show some changes.
Click to expand...
Click to collapse
yes that is what happening so you confirm that its normal. I will test it for few more days, do we have any app which can graphically plot the battery stats?

Yes, this is normal, you can check this battery indicator out it's pretty detailed - http://forum.xda-developers.com/showthread.php?p=8639993
Or, you can replace the default indicator - http://forum.xda-developers.com/showthread.php?t=724778

Thanks a lot
I have been hunting for that app in the market but could not find any such app there.

sgsI9003 said:
yes that is what happening so you confirm that its normal. I will test it for few more days, do we have any app which can graphically plot the battery stats?
Click to expand...
Click to collapse
Try JuicePlotter from the market!

btw, dont these battery indicator apps themselves drain battery quite too much?

bala_gamer said:
Dude i dont think its a problem.
The indicator changes according to the % of battery remaining. The default status indicator will have only a total of 4 to 5 stages of indication.
above 80 - state 1
above 60 - state 2
above 40 - state 3
above 20 - state 4
less than 10 - state 5.
For example
if % is above 80 , then the indicator will show full.
if it is in between 60 to 79 then it will show some changes.
Im using battery status widget to monitor battery as it gives more info on the battery status.
Click to expand...
Click to collapse
......and it is the same in KB1 as well. It is the normal behavior. @sgsI9003 Now the point is why the battery indicator (the stock blue one) suddenly drops when u start using it.

needachange said:
......and it is the same in KB1 as well. It is the normal behavior. @sgsI9003 Now the point is why the battery indicator (the stock blue one) suddenly drops when u start using it.
Click to expand...
Click to collapse
My guess is that at till 80 it wont show any drain & & then when I use for 30 mins assume it consumed another 10% so suddenly I see a drop of 30% bcoz the 1st 20% was not even showing at that time & I use to wonder how come 30 mins using consumes so much battery?
Now all is sorted out with these numerical indicators. After 3 days of testing I can say that xxkb3 has better battery life on ideal /standby if you use the phone just for calling it can last easily 48+ hrs, with web surfing, mail access & other multimedia usage it would last 12-24hours only depending upon how much its being used.
Another testing now reveled that each night I have different amount of drain which I assume that its due to radio signal interaction. Best practice is to switch off or put to airplane mode to conserve battery or have an app which can follow a time schedule to do this automatically.

Dude! why don't u try battery solo widget (free version from the market). It looks awesome & consumes around 2.9mb of ram with negligible cpu. so hardly any effect on the battery life.

For battery solo widget I have always had to go back to home screen to look the status but with battery Notifier (big text) I can see it always in real time on the notification bar.

[Battery Drain] [Lollipop] [LRX21O] - UPDATED 19-NOV-2014

Star & Report this issue to Google here: http://tinyurl.com/pgcmfma​********** UPDATE 19-NOV-2014 **********
Test 3: Battery Consumption Lollipop 5.0 [LRX21O] vs KitKat 4.4.4 [KTU84Q] (4h 30m)
[LINK TO POST IN THREAD HERE]​Scenario:
STOCK + ROOT + SELinux Mode (Permissive) + GSAM Battery Monitor (Root) + Whatsapp + Viber + Stock Apps Only
WiFi: ON
WiFi Notification: OFF
WiFi Scanning: OFF
Cellular Network Mode: 3G
NFC: OFF
Google Now: OFF
Brightness: AUTO/ADAPTIVE
OK Google: ON (Default)
Location Mode: High Accuracy
Location History: ON
Location Reporting: ON
Alarms: NO
Observations after 4h 30m:
Initial Charge: 100% (BOTH)
Remaining Charge: KitKat - 74% | Lollipop 67%
Power Consumption Per Hour: KitKat - 5.7% | Lollipop - 7.6% (~2%/hr MORE)
{
"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"
}
Total Battery Consumption: LOLLIPOP CONSUMES 7% MORE
[Note: In KitKat Phone & WiFi were significantly more used]
Application/Service Specific Battery Consumption: LOLLIPOP CONSUMES 8% MORE (APPROX)
[NOTE: KitKat Phone Call - 1h 45m while Lollipop Phone Call - 45m]
Screen Consumption: LOLLIPOP CONSUMES 11% MORE
Phone Radio: KitKat = LOLLIPOP
WiFi: LOLLIPOP CONSUMES 1.7% MORE (MATHEMATICALLY PROJECTED)
Conclusion:
Overall Battery Consumption of Lollipop is significantly higher than that of KitKat.
The default Battery Stats are inaccurate in Lollipop. It's accurate in KitKat.
WiFi shows as 'Always ON' in Lollipop's default battery stats but it is actually OFF and consumes no extra power. (Thanks to GSAM).
No 3rd Party Applications are causing drain in Lollipop. Neither is WiFi (Scanning always available or Network Notification or Whatever....)
Cast Services in Lollipop are not draining battery.
Project Volta & App Optimizations - Google Apps are expected to be optimized to consume less power. But it seems exactly the opposite.
Android System, Kernel (Android OS) & Google Play Services in Lollipop 5.0 consume 2.5 times more power to run than in KitKat 4.4.4 (6.1% vs 15.3%)
Extremely disappointed with Google. Lollipop 5.0 LRX21O has rendered the Nexus 5 unusable.
The Rest is for you to judge my friends.
Thanking everyone for their continued support. Keep Testing. Keep Reporting.
kyinx
********** END OF 19-NOV-2014 **********​
********** UPDATE 16-NOV-2014 **********
Test 2: Overnight Battery Drain [WiFi OFF] (8h 0m)
[LINK TO THIS POST HERE]
[SCREENSHOTS IN CONTENT BELOW]
Scenario:
Cleared Cache: YES
Initial Charge: 100%
WiFi: 0FF ***** Notice how the WiFi still remains ON in the Battery Stats - Screenshot 1 of Test 2.
Cellular Network Mode: 3G
NFC: OFF
Google Now: OFF
Location Mode: High Accuracy
Location History: ON
Location Reporting: ON
Alarms: NO
Observation:
Initial Charge: 100%
Remaining Charge: 85% (86% when the screenshot was taken, but dropped immediately)
Total Battery Use: 15%
Unreported Use (Hidden/Masked): 8%
Reported Battery Use: 7% (Summation of individual usage as per battery stats)
Note: 15% of battery consumption in 8h 0m results to 17.81% (18%) in 9h 32m (Mathematically). This is exactly same as Test 1's battery consumption i.e. with WiFi ON.
Whatsapp - 2%
Google Services - 1%
Phone Idle - 1%
Viber - 1%
Cell Standby - 1%
Android OS - 1%
[LINK TO THIS POST HERE]
Conclusion:
The [WiFi ON] battery drain has been consistent with [WiFi OFF] battery drain. [Test 1 = Test 2]
The WiFi service is somehow always ON whether we disable the WiFi or simple put the device in Airplane mode. This is a definite flaw with the OS.
An idle phone with WiFi ON has never ever consumed this much of battery - 16% overnight (as per Test 1). Today's test (Test 2) proves that there definitely is a WiFi Battery Drain Bug in the final version of Lollipop LRX21O.
Such high overnight battery consumption with either WiFi ON or OFF cannot be contributed only to the WiFi Bug. There are definitely other hidden battery drain issues other than this which Google knows but we do not.
50% of battery usage is still unaccounted/masked/hidden. The Developer Preview version of Lollipop shows that the Battery Stats are not incorrect. Hence I believe that Google does/did not want the users to know about the drain by MANIPULATING the stats.
It is now upto Google to come up, acknowledge this issue and fix it. They have already made a fool of themselves by releasing the Developer preview about 6 months back and still not being able to rectify the bug in the final release. I wonder if they actually are listening to us!
I thank all readers and participants of this thread for their support. Kindly continue tracking the battery usage and report observations and fixes if any..
[LINK TO THIS POST HERE]
kyinx
********** END OF 16-NOV-2014 **********​
********** UPDATE 15-NOV-2014 **********
Test 1: Overnight Battery Drain [WiFi ON] (9h 27m)
[LINK TO THIS POST HERE]
[SCREENSHOTS IN CONTENT BELOW]
Scenario:
Initial Charge: 100%
WiFi: 0N
Cellular Network Mode: 3G
NFC: OFF
Google Now: OFF
Location Mode: High Accuracy
Location History: ON
Location Reporting: ON
Alarms: NO
Observation:
Initial Charge: 100%
Remaining Charge: 82%
Total Battery Use: 18%
Unreported Use (Hidden/Masked): 14%
Reported Battery Use: 4% (Summation of individual usage as per battery stats)
WiFi - 1%
Phone Idle - 1%
Google Services - 1%
Android System - 1%
[LINK TO THIS POST HERE]
Conclusion:
There is something seriously wrong somewhere. 14% of Battery Drain overnight with screen off is ridiculous.
In KitKat the overnight battery consumption used to be 5% (Average) and 8% (Max). This used to be reported in Battery stats and this was not a drain.
Google is surely hiding the battery drain in Lollipop. It is a half baked cake and Google knows it.
I request all users (not only Nexus) to track their battery usage on Lollipop and report their observations. A comparison report with KitKat would be Excellent.
[LINK TO THIS POST HERE]
kyinx
********** END OF 15-NOV-2014 **********​
********** ORIGINAL POST 14-NOV-2014 **********
My Device: Nexus 5 LG-D821 (India). Not an OTA update. Flashed LRX21O Factory Image. Did not use Google or any other Backup & Restore utility. No Root.
Flashback: Lollipop 5.0 Developer Preview LPV79, LPV81C & LPX13D had serious battery drain issues. Detailed as "Miscellaneous" it was the WiFi Battery Drain bug which bothered all Lollipop users.
Report: After using my Nexus 5 for two complete charge cycles, I have observed that the WiFi battery drain bug persists and the details are very cleverly hidden by Google. I am framing my observations and conclusion below.
[SCREENSHOTS IN ATTACHMENT BELOW]
Initial charge: 100%
Used: 45% (Summation of individual usage as per battery stats)
Remaining: 10%
Unreported Use (Hidden/Masked): 45%
Wifi was ON the whole time (11h 5m). Consumption: 2% [SUSPICIOUSLY LOW]
uTorrent was downloading over WiFi (3h 14m). Consumption: 5% [LOOKS GOOD]
Phone idle (9h 52m). Consumption: 1% [SUSPICIOUSLY LOW]
Voice Calls (1h 20m). Consumption: 11% [LOOKS NORMAL]
Screen ON (2h 6m). Consumption: 12% [SUSPICIOUSLY LOW]
Conclusion:
There is about 50% masked battery drain in the final release of Lollipop LRX21O which Google does not want it's users to know.
Google has termed the "Miscellaneous Wifi Battery Bug" as SOLVED by just MANIPULATING the Battery Stats.
At first anyone would be very happy to see that "Miscellaneous" does not appears in the Battery stats and each service uses battery economically. But by observing carefully and refering to the Kitkat 4.4.x battery consumption stats one can easily makeout that the Lollipop battery stats are incorrect. Services are using far less amount of battery than they should (logically) and the device is still draining battery over WiFi.
Google did a hasty job with their final release of Lollipop. They are trying to hide the unresolved bugs.
Project Volta is supposed to give us 30% battery gain and not 50% battery drain.
I request Nexus users to track their battery usage on Lollipop and report their observations.
kyinx

Maybe reflash again?
Sent from my Nexus 5 using XDA Premium 4 mobile app

I was wondering the same....
Let me first talk about my old Nexus7 (2012-WiFi-32GB)...
I jumped onto the AOSP build as we got one after Google released AOSP sources publicly...
I was happy on having it running on my 2 year old device...
Performance was improved and acceptable.. Antutu scores were nearing about 22k mark with Faux kernel...... Some apps ran smoother... some took much more time to start... All credits to NAND dependency of Lollipop...
However, when I used device actively on wifi...Wi-Fi battery drainage was quite high... When I switched off Wi-Fi it went fine...
There was miscellaneous in battery usage...which accounted 30% of battery on AOSP Nexus 7 buikd...
I was unhappy and came back to Kitkat stock build...
Later on I came across the Official Build Image by Google on its servers... I downloaded and flashed on my Nexus 7... It was up and running...
Initially I was happy... Miscellaneous bug was not present(rather visible in stats)....
I used it for day...same battery drainage was there...
I felt Google did not solve anything they have just hidden the miscellaneous battery issue....just to release the lollipop as scheduled..
I get much lesser SOT (3-4 hours) compared to 5+ hours on KK... and while using with WiFi battery decays exponentially... While Wi-Fi not being used... it acts normal....
Another thing, WiFi was on for 12 hours almost and accounts to only 1% battery? I don't agree.... Google(battery stats) is faking this time I feel....
-via Nexus 7

dec1153 said:
Maybe reflash again?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashed twice. Not a problem with flashing.
Does your battery usage stats sum up to about 100% ??

kyinx said:
uTorrent was downloading over WiFi (3h 14m)
Click to expand...
Click to collapse
Rerun the test without downloading anything in the background, this is a huge wakelock. You can see when your phone was awake and when you had the steepest drain.
Leave your phone with WiFi connected and idle, screen off for several hours.
Then work out the average % / hr drain. And to anyone else who sees drain, I'm not saying there's no issue, but please at least verify that it is actually drain by logical testing. Fresh install, no additional apps other than those bundled. 'Seems' worse is not a measurement.

I went to sleep with 53% battery and woke up with 10%... Wifi on ofcourse.
I've also noticed my screen turns on when I receive messages. Not always, but sometimes it does it which is weird...
I can wait for the next update for L...

eddiehk6 said:
Rerun the test without downloading anything in the background, this is a huge wakelock. You can see when your phone was awake and when you had the steepest drain.
Leave your phone with WiFi connected and idle, screen off for several hours.
Then work out the average % / hr drain. And to anyone else who sees drain, I'm not saying there's no issue, but please at least verify that it is actually drain by logical testing. Fresh install, no additional apps other than those bundled. 'Seems' worse is not a measurement.
Click to expand...
Click to collapse
I agree that it is a huge wake lock. The battery drop curve is definitely steep. But the curve does not improve even when the download is complete and the device sleeps. The steep curve continues.
If uTorrent/WiFi/Wake Lock consumes so much battery, then why is it not reported in the stats under any category?
Kitkat used to report this usage. Lollipop is not. There is definitely something which we do not know. Google had not released the bug fixed binaries yet.
Right now my device is on charge and I would do the idle on WiFi test and no WiFi test and report my observations in the next couple of days.

experienced the same. but i think in my case my battery has had its time (1 year now, intensivly used). I ordered a new battery, should arrive tomorrow. I am curious if it will improve, because when i bought my n5, i could easily get 5h screen on. now its just 2-3h (even with kitkat)

I can confirm I'm seeing the exact same battery life (drain) as with the last Dev. Preview. They are definitely hiding the drain now... This needs to be addressed. Before, I could get 5+ hours of SOT on 4.4.4.. Ever since the last Dev. Preview until now on the official factory image flash 100% stock it's roughly 3 hours SOT..

02busa said:
I can confirm I'm seeing the exact same battery life (drain) as with the last Dev. Preview. They are definitely hiding the drain now... This needs to be addressed. Before, I could get 5+ hours of SOT on 4.4.4.. Ever since the last Dev. Preview until now on the official factory image flash 100% stock it's roughly 3 hours SOT..
Click to expand...
Click to collapse
What do you mean by "hiding the drain now"?

tfouto said:
What do you mean by "hiding the drain now"?
Click to expand...
Click to collapse
They're not listing it as miscellaneous in the battery stats menu anymore, but the drain is definitely still there. Also, they marked the issue as fixed in the issue tracker.. It's not fixed, just being covered up.

02busa said:
They're not listing it as miscellaneous in the battery stats menu anymore, but the drain is definitely still there. Also, they marked the issue as fixed in the issue tracker.. It's not fixed, just being covered up.
Click to expand...
Click to collapse
Isn't this open source code? Cant it be checked?
---------- Post added at 10:56 AM ---------- Previous post was at 10:49 AM ----------
bhargav143 said:
I was wondering the same....
I felt Google did not solve anything they have just hidden the miscellaneous battery issue....just to release the lollipop as scheduled..
-via Nexus 7
Click to expand...
Click to collapse
Do they hide their bug, or is something that they hid on purpose? Like scanning wi-fi and sending data even tough people think it's isn't happening?

tfouto said:
Isn't this open source code? Cant it be checked?
---------- Post added at 10:56 AM ---------- Previous post was at 10:49 AM ----------
Do they hide their bug, or is something that they hid on purpose? Like scanning wi-fi and sending data even tough people think it's isn't happening?
Click to expand...
Click to collapse
Yes it should be open sourced...however after the so called fix by Google... the sources are not updated...they are still in R6 branch.... No new addition/manipulation to code....
The reasoning is...they wanted the rollout take place as scheduled... And WiFi is functional... Its not that its not working at all... So they have hidden as of now... And we might see some bug fixes in coming weeks...
-via Nexus 7

tfouto said:
Isn't this open source code? Cant it be checked?
---------- Post added at 10:56 AM ---------- Previous post was at 10:49 AM ----------
Do they hide their bug, or is something that they hid on purpose? Like scanning wi-fi and sending data even tough people think it's isn't happening?
Click to expand...
Click to collapse
It MAY be fixed in AOSP, but they pushed out the factory image with the battery stats changed after the issue was marked fixed and acknowledged as fixed by a team member. The drain is still there though. I guess they're thinking that by not showing the "miscellaneous" drain in battery stats it will have some mental placebo effect on the end user... Yet any dumbass can see their actual battery life over their average daily use. Also, the items listed in battery stats DON'T add up to 100%, there's a huge percentage not showing up in the list.
For instance right now as I type this from my N5 my percentages are as follows.
Exactly 20% Battery life left.
Exactly 40% showing in battery stats among everything added up.
Thus leaving exactly 40% unaccounted for in the list..
Like I stated before, they considered this "fixed" last week, well before the factory images were pushed out this week. Yet, our LRX21O build for the Nexus 5 is dated at approximately October 21, 2014 before the issue was "fixed".
Follow me now?

coming from android 4.4.3
and flashing the OTA with this method
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
i haven't observed any battery drain at all
slept last night with wifi ON at 75%
work up and it was a respectable 60%
pretty good !

qwerty warrior said:
coming from android 4.4.3
and flashing the OTA with this method
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
i haven't observed any battery drain at all
slept last night with wifi ON at 75%
work up and it was a respectable 60%
pretty good !
Click to expand...
Click to collapse
I suggest you watch your battery life a little closer.. That's not that good. A lot of people aren't familiar with the drain, having not run the Dev. Preview for any extended amount out time.

I suspect Google for hiding Miscellaneous in battery stats.
For example, on top list of batt stats is obviously display (for example) but the "screen" only show ¼ bar graphic, not full graphic. (Just like the third picture in the OP)
So, what is on the top list above display actually?? ?

I agree. The stats no longer add up..
FYI. Miscellaneous wasn't just related to WiFi drain. If you open miscellaneous in battery stats, it said it accounted for the difference between the guesses made in battery screen (they've always been very approximate calculations and always been very inaccurate) and what the battery management chip reports as reality.
Having miscellaneous in principal was a good thing as we could see how inaccurate the battery stats really were. Its just unfortunate that there was also a WiFi bug that reported in miscellaneous too.

rootSU said:
I agree. The stats no longer add up..
FYI. Miscellaneous wasn't just related to WiFi drain. If you open miscellaneous in battery stats, it said it accounted for the difference between the guesses made in battery screen (they've always been very approximate calculations and always been very inaccurate) and what the battery management chip reports as reality.
Having miscellaneous in principal was a good thing as we could see how inaccurate the battery stats really were. Its just unfortunate that there was also a WiFi bug that reported in miscellaneous too.
Click to expand...
Click to collapse
Yeah. They should know being a developer device, that this would still be noticed by many people.

02busa said:
Yeah. They should know being a developer device, that this would still be noticed by many people.
Click to expand...
Click to collapse
Honestly not sure what's going on. Also better battery stats is about as much use as a chocolate tea pot
That said, they've managed to make a chocolate tea pot now so...

Lollipop ROMs

What is causing all of the misc battery drain on these ROMs? I have tried about 6 different ones and all have been giving me drain. Can anyone suggest a ROM that doesn't suffer the drain?
Sent from my Nexus 5 using Tapatalk

brandon5132 said:
What is causing all of the misc battery drain on these ROMs? I have tried about 6 different ones and all have been giving me drain. Can anyone suggest a ROM that doesn't suffer the drain?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Tap on Misc. and read what it actually is.

It doesn't really tell me

brandon5132 said:
It doesn't really tell me
Click to expand...
Click to collapse
Yes it does.

The only thing it tells you is that battery drain is greater than would typically be expected based on calculated usage. A few thoughts, have you tried the stock ROM, as most ROMs for lolly pop are at an early development stage, with quite a few issues. Are you testing on a fresh install without any additional apps installed. Could be a specific app that does not play well with lollipop. I know a lot of people have reported battery problems with cyanogenMod and asop ROMs

Its really simple and basic and is in no way "drain". If the big wall of text in the screenshot doesn't clarify what it is, then I will elaborate further.
All your battery stats are guessed calculations. They're never accurate. Never have been and never will be.
Here's how battery stats work.
In android, there is a file. It lists "power consumption" for certain things.
For example (and these numbers are made up because i can't be bothered to look in the code)
WiFi disconnected = 4mA
WiFi connected = 10mA
So if your phone has been connected to WiFi for 10 hours, it calculates that 10 hours @10ma = x% of battery used.
However, what if you're in your bedroom for 10 hours? The router is in your living room. Actually your WiFi is using 20mA because of the weal signal. Well, this magic file cannot account for that. There is no "WiFi connected but user is in bedroom = 20mA" entry in the file.
Battery stats actually have no link to actual battery usage. Its just a guess. Battery stats knows how much battery has been used and using its magic file, makes an educated guess at how much % battery has been used by each thing.
So your battery has depleted by 50%. 25% is WiFi connected at 10mA. But your WiFi was actually using 20mA because of distance. Battery stats cannot know this. So you actually have 25% missing in battery stats. That's what miscellaneous was created for. To show that there was a difference between battery stats guess and actual battery use from the battery.
Its the same for screen brightness, cell signal, CPU usage etc. The file knows very little. Battery stats is very inaccurate
Google actually removed miscellaneous from stock ROMs due to people who don't understand, calling it a WiFi bug. However it still exists in aosp.
I hope think clarifies for people

Thank you that cleared up a lot for me.
Sent from my Nexus 5 using Tapatalk

brandon5132 said:
Thank you that cleared up a lot for me.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No probs.

This still happens? I've not seen this since the official release?

Ben36 said:
This still happens? I've not seen this since the official release?
Click to expand...
Click to collapse
As per my post, it's been removed from Stock releases. It still exists (and rightly so IMHO) on AOSP roms. Shouldn't have been taken from stock, but they had to shut up all the complainers some how.

rootSU said:
Its really simple and basic and is in no way "drain". If the big wall of text in the screenshot doesn't clarify what it is, then I will elaborate further.
All your battery stats are guessed calculations. They're never accurate. Never have been and never will be.
Here's how battery stats work.
In android, there is a file. It lists "power consumption" for certain things.
For example (and these numbers are made up because i can't be bothered to look in the code)
WiFi disconnected = 4mA
WiFi connected = 10mA
So if your phone has been connected to WiFi for 10 hours, it calculates that 10 hours @10ma = x% of battery used.
However, what if you're in your bedroom for 10 hours? The router is in your living room. Actually your WiFi is using 20mA because of the weal signal. Well, this magic file cannot account for that. There is no "WiFi connected but user is in bedroom = 20mA" entry in the file.
Battery stats actually have no link to actual battery usage. Its just a guess. Battery stats knows how much battery has been used and using its magic file, makes an educated guess at how much % battery has been used by each thing.
So your battery has depleted by 50%. 25% is WiFi connected at 10mA. But your WiFi was actually using 20mA because of distance. Battery stats cannot know this. So you actually have 25% missing in battery stats. That's what miscellaneous was created for. To show that there was a difference between battery stats guess and actual battery use from the battery.
Its the same for screen brightness, cell signal, CPU usage etc. The file knows very little. Battery stats is very inaccurate
Google actually removed miscellaneous from stock ROMs due to people who don't understand, calling it a WiFi bug. However it still exists in aosp.
I hope think clarifies for people
Click to expand...
Click to collapse
@rootSU,
I am going to steal this, while still giving you credit, to assist while trying to explain to new users why android does what it does.
You have the best explanation I've ever read. Thank you.

ghostryder12 said:
@rootSU,
I am going to steal this, while still giving you credit, to assist while trying to explain to new users why android does what it does.
You have the best explanation I've ever read. Thank you.
Click to expand...
Click to collapse
Delete
Sent from my Nexus 9 using XDA Free mobile app

ghostryder12 said:
@rootSU,
I am going to steal this, while still giving you credit, to assist while trying to explain to new users why android does what it does.
You have the best explanation I've ever read. Thank you.
Click to expand...
Click to collapse
Please feel free. However, that's an old revision. Below is what I'll be posting from now on. Feel free to.use either
There is no "Misc bug" or "WiFi Bug" related to misc
Its really simple and basic and is in no way "drain".* All your battery stats are guessed calculations. They're never accurate. They never have been and never will be.
How battery stats work
The Battery stats UI shows the percentage of battery that device elements are responsible for using, which is based on a couple of things.
1./data/system/batterystats.bin
2./system/frameworks/frameworks-res.apk/res/xml/power_profile.xml
These things contribute in the following way:
1.From the moment Android detects that a close-to-full charge has completed, batterystats.bin records how long the device elements are running
2.This xml file is where the information about how much power, each device element “uses”
The battery stats UI looks at batterystats.bin to see how long each element has been running (and in what state) since the last charge, applies the value (in mV) for each element stored in power_profiles.xml and comes up with a calculation of the % of battery each element is using.
It simply knows the total mV used by adding up all the element values and the time in state to work out the percentages.
Here is a really basic example…
power_profile.xml from the SNexus 5
Code:
<item name="none">0</item>
<item name="screen.on">82.75</item>
<item name="screen.full">201.16</item>
<item name="bluetooth.active">51.55</item>
<item name="bluetooth.on">0.79</item>
<item name="wifi.on">3.5</item>
<item name="wifi.active">73.24</item>
<item name="wifi.scan">75.48</item>
<item name="dsp.audio">0.1</item>
<item name="dsp.video">0.1</item>
<item name="gps.on">76.23</item>
<item name="radio.active">185.19</item>
<item name="radio.scanning">99.2</item>
batterystats.bin
Code:
*** screen.on = 2 h
*** bluetooth.active = 3 h
*** bluetooth.on = 7 h
*** wifi.on = 6 h
*** wifi.active = 4 h
So, if….
Code:
*** screen.on = 165.5
*** bluetooth.active = 154.65
*** bluetooth.on = 5.53
*** wifi.on = 21
*** wifi.active = 292.96
*** Total = 639.64
Then…*
Code:
*** screen.on = 26%
*** bluetooth.active = 24%
*** bluetooth.on = 1%
*** wifi.on = 3%
*** wifi.active = 46%
*** Total = 100%
That was a basic example of how the Battery Stats UI makes it’s calculations.* Notice how the total is 100%? Well in KK and earlier this was the case.* The Battery Stats UI calculated to 100%.* So even if you had only used 50% of your battery, it would show that device elements had used 100% of your 50% used battery.
This meant that as it always had to add up to 100%, it didn't have to be particularly accurate.* It takes the values and calculations it knows about and works the portion of that 100% each known value has taken.* It knows that 639.64 is 100% therefore wifi at 292.96 must be 46%....
Since Lollipop, it has changed and makes it more difficult for battery stats UI to be so blase about its accuracy.* Now it attempts to show you what "actual" percentage of battery has been used.* For example, if 50% of your battery has been used, the total of percentage used by device elements will also show as 50%.* However, now that the total % of elements might not match the total % of battery used, it is much harder to hide how inaccurate battery stats actually are.
So to elaborate on that further, lets say that your Nexus 5 battery is 4720 mV in capacity.* The actual battery % in status bar is calculated by reading the actual current battery reading from the battery itself and working out the %, so in the example above, 14% battery has been used (639.64 is 14% of 4720 - or more accurately 13.55%)
So...*
Code:
*** screen.on = 3.6%
*** bluetooth.active = 3.4%
*** bluetooth.on = 0.05%
*** wifi.on = 0.5%
*** wifi.active = 6%
*** Total = 13.55%
Why are they never accurate?
So battery % in status* bar takes a reading from the actual battery, but battery stats just add up what they recorded multiplied by the Power_profile.xml values.
Looking at the power_profile.xml file, you'll see for example, wifi - there is an "on" value and an "active" value.* There are just 2 states.* However, what if your router is in your living room and you are in the bedroom?* WiFi Active may not be 76.23 at all.* Due to weak signal, it may be 150....* But battery stats is not aware that it may be using 150....* So it calculates using 76.23
This is where it gets a little more complicated.* Lets go back to these calculations, but factor in the new 150 value for bedroom wifi active
batterystats.bin
Code:
*** screen.on = 2 h
*** bluetooth.active = 3 h
*** bluetooth.on = 7 h
*** wifi.on = 6 h
*** wifi.active = 2 h
wifi.active.InBedroom = 2 h
So, if….
Code:
*** screen.on = 165.5
*** bluetooth.active = 154.65
*** bluetooth.on = 5.53
*** wifi.on = 21
*** wifi.active = 152.46
wifi.active.InBedroom = 300
*** Total = 799.14
So that is what ACTUALLY happened.* But Battery Stats doesn't know.. because the power_profile.xml does not really have the InBedroom entry at all.* So battery stats shows that a total 639.64 of battery has been used, however the physical battery reports that 799.14 has been used.* So the battery % in the status bar is 100% - 17%, = 83%....* 17% has been used but our earlier stats (that don't show the fake inbedroom value) show the total used is only 13.55% - there is a discrepancy here...
Well, since lollipop, that discrepancy has to be accounted for to make the battery stats appear more accurate, so the 159.50 difference that is unaccounted for (The Wifi InBedroom), now will appear as "Miscellaneous".* This makes battery stats show that 17% total battery has been used, to match the status bar and not 13.55% as per the total added up from Power_profile.xml...*
THis is not just the case with WiFI, but with everything from Screen brightness, to bluetooth to cell reception.
Why does misc show on some roms and not others
You may remember a while back that people were reporting the WiFi bug to google..* Well, simply - they probably got fed up and hid misc in Stock ROMS.* No stock roms on the Nexus 5 show misc anymore.* They just have calculations that no longer add up in total to the amount of % used of your battery
Some people have accused google of "hiding" the bug.* What we're saying is that there is NO BUG and they hid misc, which is what caused people to think there was a bug in the first place.
The Misc battery report is still in AOSP code, however some roms have also decided to hide it, such as SlimRoms for example.
You can see their changes here:
From Google: https://github.com/SlimRoms/packages_apps_Settings/commit/e6793771cedb47aed72f1c64f870b70357746938
Custom ROM feature: https://github.com/SimpleAOSP-Lolli...mmit/d025994f90722139dfcf236f275e05236ec47491
Here is an example on SlimLP with the option turned on and off
Summary
There is no such thing as a "misc bug" or "WiFi bug".* Android tries to calculate the amount of battery used by each device element, based on a very finite list of values.* Since the values are pre-determined in a file, it is not an accurate refelection of reality.* When these values in reality are higher than the file, it makes the Battery Stats show a lower % than reality being used by the elements (most easily seen in wifi).* To make the elements total match the actual % used from the battery, Misc was created to fill in that discrepancy - However, since people thought it was a bug due to lack of understanding, it has since been hidden.* But it is not a bug.

rootSU said:
Please feel free. However, that's an old revision. Below is what I'll be posting from now on. Feel free to.use either
There is no "Misc bug" or "WiFi Bug" related to misc
Its really simple and basic and is in no way "drain".* All your battery stats are guessed calculations. They're never accurate. They never have been and never will be.
How battery stats work
The Battery stats UI shows the percentage of battery that device elements are responsible for using, which is based on a couple of things.
1./data/system/batterystats.bin
2./system/frameworks/frameworks-res.apk/res/xml/power_profile.xml
These things contribute in the following way:
1.From the moment Android detects that a close-to-full charge has completed, batterystats.bin records how long the device elements are running
3.This xml file is where the information about how much power, each device element “uses”
The battery stats UI looks at batterystats.bin to see how long each element has been running (and in what state) since the last charge, applies the value (in mV) for each element stored in power_profiles.xml and comes up with a calculation of the % of battery each element is using.
It simply knows the total mV used by adding up all the element values and the time in state to work out the percentages.
Here is a really basic example…
power_profile.xml from the SNexus 5
Code:
*** 0
*** 82.75
*** 201.16
*** 51.55z
*** 0.79
*** 3.5
*** 73.24
*** 75.48
*** 0.1
*** 0.1
*** 76.23
*** 185.19
*** 99.2
batterystats.bin
Code:
*** screen.on = 2 h
*** bluetooth.active = 3 h
*** bluetooth.on = 7 h
*** wifi.on = 6 h
*** wifi.active = 4 h
So, if….
Code:
*** screen.on = 165.5
*** bluetooth.active = 154.65
*** bluetooth.on = 5.53
*** wifi.on = 21
*** wifi.active = 292.96
*** Total = 639.64
Then…*
Code:
*** screen.on = 26%
*** bluetooth.active = 24%
*** bluetooth.on = 1%
*** wifi.on = 3%
*** wifi.active = 46%
*** Total = 100%
That was a basic example of how the Battery Stats UI makes it’s calculations.* Notice how the total is 100%? Well in KK and earlier this was the case.* The Battery Stats UI calculated to 100%.* So even if you had only used 50% of your battery, it would show that device elements had used 100% of your 50% used battery.
This meant that as it always had to add up to 100%, it didn't have to be particularly accurate.* It takes the values and calculations it knows about and works the portion of that 100% each known value has taken.* It knows that 639.64 is 100% therefore wifi at 292.96 must be 46%....
Since Lollipop, it has changed and makes it more difficult for battery stats UI to be so blase about its accuracy.* Now it attempts to show you what "actual" percentage of battery has been used.* For example, if 50% of your battery has been used, the total of percentage used by device elements will also show as 50%.* However, now that the total % of elements might not match the total % of battery used, it is much harder to hide how inaccurate battery stats actually are.
So to elaborate on that further, lets say that your Nexus 5 battery is 4720 mV in capacity.* The actual battery % in status bar is calculated by reading the actual current battery reading from the battery itself and working out the %, so in the example above, 14% battery has been used (639.64 is 14% of 4720 - or more accurately 13.55%)
So...*
Code:
*** screen.on = 3.6%
*** bluetooth.active = 3.4%
*** bluetooth.on = 0.05%
*** wifi.on = 0.5%
*** wifi.active = 6%
*** Total = 13.55%
Why are they never accurate?
So battery % in status* bar takes a reading from the actual battery, but battery stats just add up what they recorded multiplied by the Power_profile.xml values.
Looking at the power_profile.xml file, you'll see for example, wifi - there is an "on" value and an "active" value.* There are just 2 states.* However, what if your router is in your living room and you are in the bedroom?* WiFi Active may not be 76.23 at all.* Due to weak signal, it may be 150....* But battery stats is not aware that it may be using 150....* So it calculates using 76.23
This is where it gets a little more complicated.* Lets go back to these calculations, but factor in the new 150 value for bedroom wifi active
batterystats.bin
Code:
*** screen.on = 2 h
*** bluetooth.active = 3 h
*** bluetooth.on = 7 h
*** wifi.on = 6 h
*** wifi.active = 2 h
wifi.active.InBedroom = 2 h
So, if….
Code:
*** screen.on = 165.5
*** bluetooth.active = 154.65
*** bluetooth.on = 5.53
*** wifi.on = 21
*** wifi.active = 152.46
wifi.active.InBedroom = 300
*** Total = 799.14
So that is what ACTUALLY happened.* But Battery Stats doesn't know.. because the power_profile.xml does not really have the InBedroom entry at all.* So battery stats shows that a total 639.64 of battery has been used, however the physical battery reports that 799.14 has been used.* So the battery % in the status bar is 100% - 17%, = 83%....* 17% has been used but our earlier stats (that don't show the fake inbedroom value) show the total used is only 13.55% - there is a discrepancy here...
Well, since lollipop, that discrepancy has to be accounted for to make the battery stats appear more accurate, so the 159.50 difference that is unaccounted for (The Wifi InBedroom), now will appear as "Miscellaneous".* This makes battery stats show that 17% total battery has been used, to match the status bar and not 13.55% as per the total added up from Power_profile.xml...*
THis is not just the case with WiFI, but with everything from Screen brightness, to bluetooth to cell reception.
Why does misc show on some roms and not others
You may remember a while back that people were reporting the WiFi bug to google..* Well, simply - they probably got fed up and hid misc in Stock ROMS.* No stock roms on the Nexus 5 show misc anymore.* They just have calculations that no longer add up in total to the amount of % used of your battery
Some people have accused google of "hiding" the bug.* What we're saying is that there is NO BUG and they hid misc, which is what caused people to think there was a bug in the first place.
The Misc battery report is still in AOSP code, however some roms have also decided to hide it, such as SlimRoms for example.
You can see their changes here:
From Google: https://github.com/SlimRoms/packages_apps_Settings/commit/e6793771cedb47aed72f1c64f870b70357746938
Custom ROM feature: https://github.com/SimpleAOSP-Lolli...mmit/d025994f90722139dfcf236f275e05236ec47491
Here is an example on SlimLP with the option turned on and off
Summary
There is no such thing as a "misc bug" or "WiFi bug".* Android tries to calculate the amount of battery used by each device element, based on a very finite list of values.* Since the values are pre-determined in a file, it is not an accurate refelection of reality.* When these values in reality are higher than the file, it makes the Battery Stats show a lower % than reality being used by the elements (most easily seen in wifi).* To make the elements total match the actual % used from the battery, Misc was created to fill in that discrepancy - However, since people thought it was a bug due to lack of understanding, it has since been hidden.* But it is not a bug.
Click to expand...
Click to collapse
Yeah, I just finished reading it. For me, the first one is great for rooted newbes Cuz it's easily understandable with no experience.
Not this second one is great for those of us that are starting to understand just how android works.
I'll be using them both, thanks.

Is there any rom without miscellaneous bug?

I try few roms and always have miscellaneous bug and wifi constantly on..
This is with unofficial cm 12 still on the phone.

Most if not all aosp 5.0.1 ROMs should not have a miscellaneous bug... I have never had an issue with WiFi always on. In currently running the latest optipop by @Cl3Kener

I know that is why i am not sure why i have it i flash this rom this afternoon so it is 5.0.1 but bug is here.

any rom using 5.0/0.1 binaries shouldnt have that. such as rastapop, slim lp, ls lp and so on

Will try rastapop now and see what will happen.

There is no such thing as a miscellaneous bug. Miscellaneous is not a bug.
The difference is that miscellaneous is either hidden or is not hidden. Battery use is the same. That's it. There is no bug.
From http://forum.xda-developers.com/showthread.php?t=2973480
rootSU said:
Its really simple and basic and is in no way "drain". If the big wall of text in the screenshot doesn't clarify what it is, then I will elaborate further.
All your battery stats are guessed calculations. They're never accurate. Never have been and never will be.
Here's how battery stats work.
In android, there is a file. It lists "power consumption" for certain things.
For example (and these numbers are made up because i can't be bothered to look in the code)
WiFi disconnected = 4mA
WiFi connected = 10mA
So if your phone has been connected to WiFi for 10 hours, it calculates that 10 hours @10ma = x% of battery used.
However, what if you're in your bedroom for 10 hours? The router is in your living room. Actually your WiFi is using 20mA because of the weal signal. Well, this magic file cannot account for that. There is no "WiFi connected but user is in bedroom = 20mA" entry in the file.
Battery stats actually have no link to actual battery usage. Its just a guess. Battery stats knows how much battery has been used and using its magic file, makes an educated guess at how much % battery has been used by each thing.
So your battery has depleted by 50%. 25% is WiFi connected at 10mA. But your WiFi was actually using 20mA because of distance. Battery stats cannot know this. So you actually have 25% missing in battery stats. That's what miscellaneous was created for. To show that there was a difference between battery stats guess and actual battery use from the battery.
Its the same for screen brightness, cell signal, CPU usage etc. The file knows very little. Battery stats is very inaccurate
Google actually removed miscellaneous from stock ROMs due to people who don't understand, calling it a WiFi bug. However it still exists in aosp.
I hope think clarifies for people
Click to expand...
Click to collapse

rootSU said:
There is no such thing as a miscellaneous bug. Miscellaneous is not a bug.
The difference is that miscellaneous is either hidden or is not hidden. Battery use is the same. That's it. There is no bug.
From http://forum.xda-developers.com/showthread.php?t=2973480
Click to expand...
Click to collapse
You may as well add these two Github links to your text file:
From Google: Skip Misc/Overcounted battery stats in release builds.
Custom ROM feature: Settings: make unaccounted and over-counted battery usage configurable

Lethargy said:
You may as well add these two Github links to your text file:
From Google: Skip Misc/Overcounted battery stats in release builds.
Custom ROM feature: Settings: make unaccounted and over-counted battery usage configurable
Click to expand...
Click to collapse
Thanks. Will do. I haven't actually committed this to ever note yet but will soon. I'm waiting for some screen shots (I have this feature in slim lap to hide misc) before I do...

So this mean that maybe is time to change my battery.

kojoti2 said:
So this mean that maybe is time to change my battery.
Click to expand...
Click to collapse
No. It means nothing. Just that there is no bug. Your battery will last the same amount of time on a rom that shows misc as a rom that does not show misc.

I have free fall on battery that is not happen before and my phone is one year i will let rom settle few days yo see if something change if not will order new battery from amazon. I never have this problem with kitkat.

kojoti2 said:
I have free fall on battery that is not happen before and my phone is one year i will let rom settle few days yo see if something change if not will order new battery from amazon. I never have this problem with kitkat.
Click to expand...
Click to collapse
Because Misc. wasn't a thing in KK? lol

Because battery i believe is bad.

@Lethargy, thinking of commiting this to my evernote to reuse. Mind proof reading it for me please?
THere is no "Misc bug" or "WiFi Bug" related to misc
Its really simple and basic and is in no way "drain". All your battery stats are guessed calculations. They're never accurate. They never have been and never will be.
How battery stats work
The Battery stats UI shows the percentage of battery that device elements are responsible for using, which is based on a couple of things.
1./data/system/batterystats.bin
2./system/frameworks/frameworks-res.apk/res/xml/power_profile.xml
These things contribute in the following way:
1.From the moment Android detects that a close-to-full charge has completed, batterystats.bin records how long the device elements are running
3.This xml file is where the information about how much power, each device element “uses”
The battery stats UI looks at batterystats.bin to see how long each element has been running (and in what state) since the last charge, applies the value (in mV) for each element stored in power_profiles.xml and comes up with a calculation of the % of battery each element is using.
It simply knows the total mV used by adding up all the element values and the time in state to work out the percentages.
Here is a really basic example…
power_profile.xml from the SNexus 5
Code:
0
82.75
201.16
51.55z
0.79
3.5
73.24
75.48
0.1
0.1
76.23
185.19
99.2
batterystats.bin
Code:
screen.on = 2 h
bluetooth.active = 3 h
bluetooth.on = 7 h
wifi.on = 6 h
wifi.active = 4 h
So, if….
Code:
screen.on = 165.5
bluetooth.active = 154.65
bluetooth.on = 5.53
wifi.on = 21
wifi.active = 292.96
Total = 639.64
Then…
Code:
screen.on = 26%
bluetooth.active = 24%
bluetooth.on = 1%
wifi.on = 3%
wifi.active = 46%
Total = 100%
That was a basic example of how the Battery Stats UI makes it’s calculations. Notice how the total is 100%? Well in KK and earlier this was the case. The Battery Stats UI calculated to 100%. So even if you had only used 50% of your battery, it would show that device elements had used 100% of your 50% used battery.
This meant that as it always had to add up to 100%, it didn't have to be particularly accurate. It takes the values and calculations it knows about and works the portion of that 100% each known value has taken. It knows that 639.64 is 100% therefore wifi at 292.96 must be 46%....
Since Lollipop, it has changed and makes it more difficult for battery stats UI to be so blase about its accuracy. Now it attempts to show you what "actual" percentage of battery has been used. For example, if 50% of your battery has been used, the total of percentage used by device elements will also show as 50%. However, now that the total % of elements might not match the total % of battery used, it is much harder to hide how inaccurate battery stats actually are.
So to elaborate on that further, lets say that your Nexus 5 battery is 4720 mV in capacity. The actual battery % in status bar is calculated by reading the actual current battery reading from the battery itself and working out the %, so in the example above, 14% battery has been used (639.64 is 14% of 4720 - or more accurately 13.55%)
So...
Code:
screen.on = 3.6%
bluetooth.active = 3.4%
bluetooth.on = 0.05%
wifi.on = 0.5%
wifi.active = 6%
Total = 13.55%
Why are they never accurate?
So battery % in status bar takes a reading from the actual battery, but battery stats just add up what they recorded multiplied by the Power_profile.xml values.
Looking at the power_profile.xml file, you'll see for example, wifi - there is an "on" value and an "active" value. There are just 2 states. However, what if your router is in your living room and you are in the bedroom? WiFi Active may not be 76.23 at all. Due to weak signal, it may be 150.... But battery stats is not aware that it may be using 150.... So it calculates using 76.23
This is where it gets a little more complicated. Lets go back to these calculations, but factor in the new 150 value for bedroom wifi active
batterystats.bin
Code:
screen.on = 2 h
bluetooth.active = 3 h
bluetooth.on = 7 h
wifi.on = 6 h
wifi.active = 2 h
wifi.active.InBedroom = 2 h
So, if….
Code:
screen.on = 165.5
bluetooth.active = 154.65
bluetooth.on = 5.53
wifi.on = 21
wifi.active = 152.46
wifi.active.InBedroom = 300
Total = 799.14
So that is what ACTUALLY happened. But Battery Stats doesn't know.. because the power_profile.xml does not really have the InBedroom entry at all. So battery stats shows that a total 639.64 of battery has been used, however the physical battery reports that 799.14 has been used. So the battery % in the status bar is 100% - 17%, = 83%.... 17% has been used but our earlier stats (that don't show the fake inbedroom value) show the total used is only 13.55% - there is a discrepancy here...
Well, since lollipop, that discrepancy has to be accounted for to make the battery stats appear more accurate, so the 159.50 difference that is unaccounted for (The Wifi InBedroom), now will appear as "Miscellaneous". This makes battery stats show that 17% total battery has been used, to match the status bar and not 13.55% as per the total added up from Power_profile.xml...
THis is not just the case with WiFI, but with everything from Screen brightness, to bluetooth to cell reception.
Why does misc show on some roms and not others
You may remember a while back that people were reporting the WiFi bug to google.. Well, simply - they probably got fed up and hid misc in Stock ROMS. No stock roms on the Nexus 5 show misc anymore. They just have calculations that no longer add up in total to the amount of % used of your battery
Some people have accused google of "hiding" the bug. What we're saying is that there is NO BUG and they hid misc, which is what caused people to think there was a bug in the first place.
The Misc battery report is still in AOSP code, however some roms have also decided to hide it, such as SlimRoms for example.
You can see their changes here:
From Google: https://github.com/SlimRoms/packages_apps_Settings/commit/e6793771cedb47aed72f1c64f870b70357746938
Custom ROM feature: https://github.com/SimpleAOSP-Lolli...mmit/d025994f90722139dfcf236f275e05236ec47491
Here is an example on SlimLP with the option turned on and off
Summary
There is no such thing as a "misc bug" or "WiFi bug". Android tries to calculate the amount of battery used by each device element, based on a very finite list of values. Since the values are pre-determined in a file, it is not an accurate refelection of reality. When these values in reality are higher than the file, it makes the Battery Stats show a lower % than reality being used by the elements (most easily seen in wifi). To make the elements total match the actual % used from the battery, Misc was created to fill in that discrepancy - However, since people thought it was a bug due to lack of understanding, it has since been hidden. But it is not a bug.

rootSU said:
@Lethargy, thinking of commiting this to my evernote to reuse. Mind proof reading it for me please?
Click to expand...
Click to collapse
Here we go: http://pastebin.com/htnd4hhq
Quite long so maybe make this a thread, then have a much shorter, basic summary with a link to the full post?

Lethargy said:
Here we go: http://pastebin.com/htnd4hhq
Quite long so maybe make this a thread, then have a much shorter, basic summary with a link to the full post?
Click to expand...
Click to collapse
I just rewrote it slightly...
I don't want to make it a thread really. Whenever I make a thread, I seem to get challenged by some members about it's accuracy and to be honest, it's getting a bit boring. Not that I mind being challenged. I write my threads in such a way that they make sense by over simplifying stuff which sometimes makes them technically inaccurate to an extent to make it understandable. However, every time I create a thread, I end up spending half my time explaining why I wrote what I wrote in the way that I did, so i'm just gonna do what I do with some other responses and make them an Ever note pastable answer.
But the answer is acceptable to you?

rootSU said:
I just rewrote it slightly...
I don't want to make it a thread really. Whenever I make a thread, I seem to get challenged by some members about it's accuracy and to be honest, it's getting a bit boring. Not that I mind being challenged. I write my threads in such a way that they make sense by over simplifying stuff which sometimes makes them technically inaccurate to an extent to make it understandable. However, every time I create a thread, I end up spending half my time explaining why I wrote what I wrote in the way that I did, so i'm just gonna do what I do with some other responses and make them an Ever note pastable answer.
Click to expand...
Click to collapse
Haha, yeah.
rootSU said:
But the answer is acceptable to you?
Click to expand...
Click to collapse
Yup

Lethargy said:
Haha, yeah.
Yup
Click to expand...
Click to collapse
Cool, thanks for your time and input. As always, much appreciated.

Nice explanation i have one more question according to miscellaneous report power that battery produce is way smaller than power use and my battery charge time is always 40-50 minutes from 10% battery lvl.
I have same application as on kitkat all up to date. That is why i'm suspicious that my battery need to be replaced.

kojoti2 said:
Nice explanation i have one more question according to miscellaneous report power that battery produce is way smaller than power use and my battery charge time is always 40-50 minutes from 10% battery lvl.
I have same application as on kitkat all up to date. That is why i'm suspicious that my battery need to be replaced.
Click to expand...
Click to collapse
My advice to you is forget about miscellaneous all together. Your graph looks like you have a problem but I have no idea what the cause is. Misc is only showing because android doesn't know what it is.
I would consider doing a full factory reset and running it "blank" for few days, running apps like gsam or bbs to see what is going on - probably on stock rom.... It could be that your battery is indeed problematic, but I think its best to disassociate that with misc etc and look at it objectively.

Ugh

Not sure if this is the right place for a rant but here i go none the less.
If this isn't the place for a rant then please move or delete.
My cant there be a ROM out there that has everything lol
I've been going from ROM to ROM for sometime now.
I find one that has all the features but has crap battery life. Which makes no sense to me as they are all from aosp or source. How can some ROMs have the misc battery issues but others don't. This is extremely frustrating.
Then I will find a ROM that has amazing battery life but has nothing for features or is all blacked out.
I know Devs make ROMs on their free time and all and don't make money. But I'm one of the few who when they find a ROM, donate. I do it for apps. Kernels. ROMs.
All I want essentially is rastapop ROM as it had the best battery life I had ever seen. It has most of the features I want except one. Led notifications. I want it built in. Not a separate app like liteflow. I find liteflow barely works. Without having a stupid constant notification.
Anyways. Why Oh why can I not find a ROM that has everything. Ugh...
/rant

1. There is no place for rants
2. There is no "Misc bug" or "WiFi Bug" related to misc
Its really simple and basic and is in no way "drain".* All your battery stats are guessed calculations. They're never accurate. They never have been and never will be.
Basic version
Here's how battery stats work.*
In android, there is a file. It lists "power consumption" for certain things.*
For example (and these numbers are made up for simplicity)
WiFi disconnected = 4mA
WiFi connected = 10mA
So if your phone has been connected to WiFi for 10 hours, it calculates that 10 hours @ 10mA = x% of battery used.*
However, what if you're in your bedroom for 10 hours? The router is in your living room. Actually your WiFi is using 20mA because of the weal signal. Well, this magic file cannot account for that. There is no "WiFi connected but user is in bedroom = 20mA" entry in the file.*
Battery stats actually have no link to actual battery usage. Its just a guess. Battery stats knows how much battery has been used and using its magic file, makes an educated guess at how much % battery has been used by each thing.*
So your battery has depleted by 50%. 25% is WiFi connected at 10mA. But your WiFi was actually using 20mA because of distance. Battery stats cannot know this. So you actually have 25% missing in battery stats. That's what miscellaneous was created for. To show that there was a difference between battery stats guess and actual battery use from the battery.*
Its the same for screen brightness, cell signal, CPU usage etc. The file knows very little. Battery stats is very inaccurate
Google actually removed miscellaneous from stock ROMs due to people who don't understand, calling it a WiFi bug. However it still exists in aosp.*
Advanced version
How battery stats work
The Battery stats UI shows the percentage of battery that device elements are responsible for using, which is based on a couple of things.
1./data/system/batterystats.bin
2./system/frameworks/frameworks-res.apk/res/xml/power_profile.xml
These things contribute in the following way:
1.From the moment Android detects that a close-to-full charge has completed, batterystats.bin records how long the device elements are running
3.This xml file is where the information about how much power, each device element “uses”
The battery stats UI looks at batterystats.bin to see how long each element has been running (and in what state) since the last charge, applies the value (in mV) for each element stored in power_profiles.xml and comes up with a calculation of the % of battery each element is using.
It simply knows the total mV used by adding up all the element values and the time in state to work out the percentages.
Here is a really basic example…
power_profile.xml from the SNexus 5
Code:
*0 82.75 201.16 51.55 0.79 3.5 73.24 75.48 0.1 0.1 76.23 185.19 99.2
batterystats.bin
Code:
*** screen.on = 2 h
*** bluetooth.active = 3 h
*** bluetooth.on = 7 h
*** wifi.on = 6 h
*** wifi.active = 4 h
So, if….
Code:
*** screen.on = 165.5
*** bluetooth.active = 154.65
*** bluetooth.on = 5.53
*** wifi.on = 21
*** wifi.active = 292.96
*** Total = 639.64
Then…*
Code:
*** screen.on = 26%
*** bluetooth.active = 24%
*** bluetooth.on = 1%
*** wifi.on = 3%
*** wifi.active = 46%
*** Total = 100%
That was a basic example of how the Battery Stats UI makes it’s calculations.* Notice how the total is 100%? Well in KK and earlier this was the case.* The Battery Stats UI calculated to 100%.* So even if you had only used 50% of your battery, it would show that device elements had used 100% of your 50% used battery.
This meant that as it always had to add up to 100%, it didn't have to be particularly accurate.* It takes the values and calculations it knows about and works the portion of that 100% each known value has taken.* It knows that 639.64 is 100% therefore wifi at 292.96 must be 46%....
Since Lollipop, it has changed and makes it more difficult for battery stats UI to be so blase about its accuracy.* Now it attempts to show you what "actual" percentage of battery has been used.* For example, if 50% of your battery has been used, the total of percentage used by device elements will also show as 50%.* However, now that the total % of elements might not match the total % of battery used, it is much harder to hide how inaccurate battery stats actually are.
So to elaborate on that further, lets say that your Nexus 5 battery is 4720 mV in capacity.* The actual battery % in status bar is calculated by reading the actual current battery reading from the battery itself and working out the %, so in the example above, 14% battery has been used (639.64 is 14% of 4720 - or more accurately 13.55%)
So...*
Code:
*** screen.on = 3.6%
*** bluetooth.active = 3.4%
*** bluetooth.on = 0.05%
*** wifi.on = 0.5%
*** wifi.active = 6%
*** Total = 13.55%
Why are they never accurate?
So battery % in status* bar takes a reading from the actual battery, but battery stats just add up what they recorded multiplied by the Power_profile.xml values.
Looking at the power_profile.xml file, you'll see for example, wifi - there is an "on" value and an "active" value.* There are just 2 states.* However, what if your router is in your living room and you are in the bedroom?* WiFi Active may not be 76.23 at all.* Due to weak signal, it may be 150....* But battery stats is not aware that it may be using 150....* So it calculates using 76.23
This is where it gets a little more complicated.* Lets go back to these calculations, but factor in the new 150 value for bedroom wifi active
batterystats.bin
Code:
*** screen.on = 2 h
*** bluetooth.active = 3 h
*** bluetooth.on = 7 h
*** wifi.on = 6 h
*** wifi.active = 2 h
wifi.active.InBedroom = 2 h
So, if….
Code:
*** screen.on = 165.5
*** bluetooth.active = 154.65
*** bluetooth.on = 5.53
*** wifi.on = 21
*** wifi.active = 152.46
wifi.active.InBedroom = 300
*** Total = 799.14
So that is what ACTUALLY happened.* But Battery Stats doesn't know.. because the power_profile.xml does not really have the InBedroom entry at all.* So battery stats shows that a total 639.64 of battery has been used, however the physical battery reports that 799.14 has been used.* So the battery % in the status bar is 100% - 17%, = 83%....* 17% has been used but our earlier stats (that don't show the fake inbedroom value) show the total used is only 13.55% - there is a discrepancy here...
Well, since lollipop, that discrepancy has to be accounted for to make the battery stats appear more accurate, so the 159.50 difference that is unaccounted for (The Wifi InBedroom), now will appear as "Miscellaneous".* This makes battery stats show that 17% total battery has been used, to match the status bar and not 13.55% as per the total added up from Power_profile.xml...*
THis is not just the case with WiFI, but with everything from Screen brightness, to bluetooth to cell reception.
Why does misc show on some roms and not others
You may remember a while back that people were reporting the WiFi bug to google..* Well, simply - they probably got fed up and hid misc in Stock ROMS.* No stock roms on the Nexus 5 show misc anymore.* They just have calculations that no longer add up in total to the amount of % used of your battery
Some people have accused google of "hiding" the bug.* What we're saying is that there is NO BUG and they hid misc, which is what caused people to think there was a bug in the first place.
The Misc battery report is still in AOSP code, however some roms have also decided to hide it, such as SlimRoms for example.
You can see their changes here:
From Google: https://github.com/SlimRoms/packages_apps_Settings/commit/e6793771cedb47aed72f1c64f870b70357746938
Custom ROM feature: https://github.com/SimpleAOSP-Lolli...mmit/d025994f90722139dfcf236f275e05236ec47491
Here is an example on SlimLP with the option turned on and off
{
"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"
}
Summary
There is no such thing as a "misc bug" or "WiFi bug".* Android tries to calculate the amount of battery used by each device element, based on a very finite list of values.* Since the values are pre-determined in a file, it is not an accurate refelection of reality.* When these values in reality are higher than the file, it makes the Battery Stats show a lower % than reality being used by the elements (most easily seen in wifi).* To make the elements total match the actual % used from the battery, Misc was created to fill in that discrepancy - However, since people thought it was a bug due to lack of understanding, it has since been hidden.* But it is not a bug.

Makes sense. Thank you. I read some thing about the misc drain. But never truly understood it. That actually helped and made me understand it.
But why does it seem like my battery is worse when I am on ROMs with the misc drain. Then on ROMs that don't list it.
Example. My drain is worse when on cm12 but is better on rastapop.
Anyways. I guess someone can delete this thread before it becomes a bashing heaven lol or a flame war in here.
Thank you again for the clarification on that misc battery thing. Appreciated very much.

No problem. As for why some see to drain quicker, I can only guess its to do with the out-of-the-box kernel settings, or its pyschologogical

rootSU said:
No problem. As for why some see to drain quicker, I can only guess its to do with the out-of-the-box kernel settings, or its pyschologogical
Click to expand...
Click to collapse
Can't be psychological...
Here's a good comparison.
My work is 30 mins away driving. Every day is the same. Same route. Same time. Etc
Some ROMs by the time I get to work I'm at 95%
Some ROMs I'll be at 99% .
That's usually my comparison
I would have all the same stuff running. I normally don't touch my phone other then turning off wifi and turning on bt.
My phone auto reboots every morning at 5am.
Anyways lol enough of all that.
Thank you again for the details

c_86 said:
Can't be psychological...
Here's a good comparison.
My work is 30 mins away driving. Every day is the same. Same route. Same time. Etc
Some ROMs by the time I get to work I'm at 95%
Some ROMs I'll be at 99% .
That's usually my comparison
I would have all the same stuff running. I normally don't touch my phone other then turning off wifi and turning on bt.
My phone auto reboots every morning at 5am.
Anyways lol enough of all that.
Thank you again for the details
Click to expand...
Click to collapse
Hmm. I think it may be because it guesses what usage will be then realizes the battery is only at x when it calculates y.
Sent from my Nexus 5 using XDA Free mobile app

Learn to compile yourself. Issues solved.

Tweaked. Believe me. I have tried. For some reason it's just above my head and I get confused. I'm normally decent at coding but for some reason I cannot wrap my head around compiling for Android.