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.

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.

Miscellaneous battery drain

Just upgraded my Nexus 5 to CM12, now i'm getting huge battery drain by a process called "Miscellaneous" and it's becoming very annoying... What is this process?? What information do we have here on XDA??? Anyone else is having this issue????

Enri1196 said:
Just upgraded my Nexus 5 to CM12, now i'm getting huge battery drain by a process called "Miscellaneous" and it's becoming very annoying... What is this process?? What information do we have here on XDA??? Anyone else is having this issue????
Click to expand...
Click to collapse
Working as intended. There has been much discussion on this but someone correct me if I'm wrong it's Lollipop estimating what your battery usage is going to be for X then it ends up being Y so X+/-Y = Miscellaneous..

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:
*<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
{
"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.

But what do you do to get decent battery life?? maybe my battery is broken??? i don't know what to think

Enri1196 said:
But what do you do to get decent battery life?? maybe my battery is broken??? i don't know what to think
Click to expand...
Click to collapse
the miscelanius aint the problem, something else is. if you use an app or something to change your build prop and edit the ro.build.type to user (ro.build.type=user) the miscelanius will go away. use some app to indentify if you dont have wakelocks or something like that

although long time since anybody have been here, might as well ask right...
I ahve huge problem with my battery life --- I loose about 60% over night with no use.
I bought new battery and tried few different roms and kernels including stock with no luck of improvement.
I have tried to turn the wifi off and battery saver on ... Tried with no apps installed or in safe mode .... still same battery drain ...
Getting kinda desperate here.
Nexus 5 Hammerhead, Euclidean OS, ElemantalX kernel.
https://plus.google.com/photos/1097...738&ssid=41667ddc-02c5-4271-a7a3-e9b0fe1dda58
https://plus.google.com/photos/1097...738&ssid=41667ddc-02c5-4271-a7a3-e9b0fe1dda58

erik.paliza said:
although long time since anybody have been here, might as well ask right...
I ahve huge problem with my battery life --- I loose about 60% over night with no use.
I bought new battery and tried few different roms and kernels including stock with no luck of improvement.
I have tried to turn the wifi off and battery saver on ... Tried with no apps installed or in safe mode .... still same battery drain ...
Getting kinda desperate here.
Nexus 5 Hammerhead, Euclidean OS, ElemantalX kernel.
https://plus.google.com/photos/1097...738&ssid=41667ddc-02c5-4271-a7a3-e9b0fe1dda58
https://plus.google.com/photos/1097...738&ssid=41667ddc-02c5-4271-a7a3-e9b0fe1dda58
Click to expand...
Click to collapse
Just try this and let us know
https://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884

AlbertoDR said:
Just try this and let us know
https://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884
Click to expand...
Click to collapse
I have been led to belive I can not use xposed because I am on android 7.1., at least I have not found proper zip file to flash. So no use for me. But now i have found out it does not have to do anything with my apps.
In safe mode the battery drain is fine ... over night about 5%, wich is fine.
Lastly, i have flashed the latest euclidean os from 10.1.2017 or so ... Kept the phone as it was, no further apps ... still huge battery drain. Instaled betterbatterystats and now I know it is due to wakelocks.
i have been monitoring just a while now but for now most wakes are:
AudioMix
EntriesRefresh_wakelock
ULR-BarometerReading_wakelock
NIpCollectorWakelock
And BBS_Wakelock
I will google those later ... But mi biggest issue is the fact that the phone worked fine, but now it is terrible, with no new apps or anything ... Even without anything installed from my part the batery drain is enormous. I am constantly chargign the phone.
Thanks for your reply, though. I will when i am able to download xposed.
---------- Post added at 02:20 PM ---------- Previous post was at 01:42 PM ----------
Enri1196 said:
But what do you do to get decent battery life?? maybe my battery is broken??? i don't know what to think
Click to expand...
Click to collapse
Did you ever figure it out?

Same issue on Nexus 5 with AOSP 7.1.1 from Santhosh M.
110% battery consumed by Miscellaneous for last day

Some battery test results

Today did some basic tests to see how the batter compared to a Sony Z Ultra.
Be advised this is not a fair test, the ZU is 2 years old. While the device has been properly maintained and not stressed a lot, its still with a two year old battery.
Screen on ( ZU: 45%, X2: 50% ( brighter then ZU to compensate the battery somewhat )), no activity.
ZU: Lost about 11% in 75 minutes.
X2: Lost about 4% in 75 minutes.
At that rate the devices will last:
ZU: 11h15 minutes
X2: 31h10 minutes
Now this matches up with a review i read where they state that the X2 will last 35 hours with screen on.
The double to triple battery life seems to match up with the reviews i read before. Its powering a bigger screen, higher resolution, has more memory ( 3GB vs 2GB ), and still triple the ( 2 year old ) ZU, despite given a extra handicap with a high screen usage.
Some benches:
AnTuTu:
ZU: 39.900
X2: 49.200
About 25% better benchmark performance. Memory had clearly more bandwidth, faster internal flash, CPU score was a bit of a head breaker. Faster on multithread and float ( probably because of the 64 bit ) but slower in the single core ( pure ) integer performance.
Screens:
If both devices are put next to each other, the ZU its color looks more washed ( grayish ) out compared to the X2. The X2's color are more stronger.
So far its a great ZU replacement.
Things i do not like: The screen has a higher output for everything ( everything looks bigger on the screen ) compared to the ZU where they reduced the rendering size for the font/etc, giving more content on the screen.
This needs a fix somehow ( do not know if this can be changed with a setting or needs a custom rom ).
That is it. Not a lot of time right now.

change dpi in build.prop if you are rooted.
If you are not rooted. run following command inside any terminal app :
- wm density xxx
- reboot device
where xxx is 170 to 400. keep changing it until you find are happy with resolution.

What is the standard DPI on the X2?

400
Flavio said:
What is the standard DPI on the X2?
Click to expand...
Click to collapse

bark1234 said:
change dpi in build.prop if you are rooted.
If you are not rooted. run following command inside any terminal app :
- wm density xxx
- reboot device
where xxx is 170 to 400. keep changing it until you find are happy with resolution.
Click to expand...
Click to collapse
Good advice, thanks.
Will changing the DPI affect all parts of the UI? For example, will the web browser show more content because the viewport will have been lengthened due to the smaller dot pitch?
I ask because I have installed third party launchers on my device that "simulate" a lower DPI by shrinking the size of text and icons on the home screen, but the magnification of all other apps is left unchanged.

Yes
aniym said:
Good advice, thanks.
Will changing the DPI affect all parts of the UI? For example, will the web browser show more content because the viewport will have been widened due to the smaller dot pitch?
Click to expand...
Click to collapse

bark1234 said:
change dpi in build.prop if you are rooted.
If you are not rooted. run following command inside any terminal app :
- wm density xxx
- reboot device
where xxx is 170 to 400. keep changing it until you find are happy with resolution.
Click to expand...
Click to collapse
Thanks for the tip Bark...
It did involve a bit more work then what was written above... You need to do a bunch of steps to conclude things to a good end. I made a little mini-guide to help people along:
http://forum.xda-developers.com/mediapad-x2/general/mini-guide-adb-installation-usage-t3183906
Hope it helps. Btw: 280 rocks for this device... makes a lot of websites run into desktop made, and Chrome shows tabs. Turns it into more of a mini-pc... and with the big screen its still very readable!

Can you tell us which standard apps are incompatible with the 280DPI setting?
Do the dialer and contacts work? And settings?

Flavio said:
Can you tell us which standard apps are incompatible with the 280DPI setting?
Do the dialer and contacts work? And settings?
Click to expand...
Click to collapse
So far there seems to be a bug with the navigation bar and landscape. In the sense that the navigation bar shows up but none of the icons show up ( and nothing reacts on the bar ). Not sure if its related to the 280dpi or not.
Some more battery numbers:
3h36min playing Fallout Shelter ( big battery eating game )
4.20min total screen time.
Battery loss: 44%

[/COLOR]
Benjiro said:
So far there seems to be a bug with the navigation bar and landscape. In the sense that the navigation bar shows up but none of the icons show up ( and nothing reacts on the bar ). Not sure if its related to the 280dpi or not.
Some more battery numbers:
3h36min playing Fallout Shelter ( big battery eating game )
4.20min total screen time.
Battery loss: 44%
Click to expand...
Click to collapse
Great info thanks. Would you be able to post some screenshots of the UI and web browser so we can see the difference 280 DPI makes in terms of screen real estate? Thanks!

Flavio said:
Can you tell us which standard apps are incompatible with the 280DPI setting?
Do the dialer and contacts work? And settings?
Click to expand...
Click to collapse
I have no problems at all with anything running the density at 280

aniym said:
[/COLOR]
Great info thanks. Would you be able to post some screenshots of the UI and web browser so we can see the difference 280 DPI makes in terms of screen real estate? Thanks!
Click to expand...
Click to collapse
Here are some apps running at 280 DPI.

bark1234 said:
If you are not rooted. run following command inside any terminal app :
- wm density xxx
- reboot device
where xxx is 170 to 400. keep changing it until you find are happy with resolution.
Click to expand...
Click to collapse
Seems to ask for writting permission:
{
"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"
}
http://www.hostingpics.net/viewer.php?id=566688Screenshot20150822213331.png
So to be rooted, isn't it?

Try to run from adb shell.
Djiban said:
Seems to ask for writting permission:
http://www.hostingpics.net/viewer.php?id=566688Screenshot20150822213331.png
So to be rooted, isn't it?
Click to expand...
Click to collapse

Djiban said:
Seems to ask for writting permission:
http://www.hostingpics.net/viewer.php?id=566688Screenshot20150822213331.png
So to be rooted, isn't it?
Click to expand...
Click to collapse
Do this:
http://forum.xda-developers.com/mediapad-x2/general/mini-guide-adb-installation-usage-t3183906
Works perfect. Took me a hour to figure out those steps ( especially the missing driver! ). *lol*

Today finally did a full charge ( up to 90% ), with still 13% left. So in total been using the X2 from last week Thursday ( full charge to 97% on Thursday night at 20.30, with a small 10% extra charge-up on Saturday when it was connected to my USB for configuring ).
Did some navigation tests:
GPS: Fast lock-on even without A-GPS. Inside 3 meters from the window it found 4 sat's but no lock-on. Closer to the window got 12 sats with 10 in usage.
Cold start outside was done within several seconds, where it took my old HTC HD2 at times 3 or 4 minutes ( Hamburg = big building everywhere blocking the signal too much for my old HD2 its cold start )...
28 min driving with Sygic navigation, with 4G/Phone/GPS on had a battery drop of about 4% ( from 18 to 14% ).
Inside at my work, had GPS + 4G + Phone active during "sleep", drains the battery about 1 a 2% per hour. Probably the GPS trying to get the location while inside, what was draining the battery faster.
Biggest battery eater: Fallout Shelter... this eats battery like candy. I estimate that playing the game for 8 hours will drain the battery from 95% to 5% ... So that is good survivability. If all you do is comic book readying, i estimate that you can easily get 20h+ out of it.

Here are some power usage number over the last 6 days and half.
25/08 21.30: 100%
- Installing some software
- Wifi + Cell on all night
26/08 9.50: 93%
- Call 15 min
- Daily WeChat checks & talks
- Wifi ( useless, no connection ) + 2G + Cell on all day
26/08 17.44: 88%
- Some playing around
- Wifi + Cell on all night
27/08 9.22: 83%
- Call 15 min
- Lots of WeChat chatting
- Wifi ( useless, no connection ) + 2G + Cell on all day
27/08 17.23: 74%
- Wifi or 2G + Cell on all day, forgot to write down. Based upon the drop, i probably had 2G and no Wifi on.
28/08 9.22: 71%
- Some WeChat chatting & checking but low activity day
- 2G + Cell on all day
28/08 17.50: 69% << no joke .. only 2% that day??
... big gap, weekend. Forgot to write down numbers.
- Some software installing, playing round, internet usage, ... a bunch of things
- Wifi + Cell on all the time.
31/08: 08:00 ( Forgot to write down but it was in the 40% somewhere )
- GPS navigation for about 30 minutes in the car
- Wifi + 2G + Cell
31/08: 11.47 36%
- Chatting, etc ... you know the routine by now *lol*
- 2G + Cell all day
31/08 18.19: 31%
- 2G + Cell all night
01/08 9.50: 28%
...
In total my screen was on for about 5 hours according to the battery app but i have my doubts about the reporting. Sygic ( car navigation ) had run for a pure minimum of 30 minutes ( longer because i tested some things at home ), and this usage is not reported at all. And Sygic + GPS are medium/high power drainers.
My 4G/2G + Cell account for 24% of the power usage. Wifi accounts for 4%. My 5 hour screen time supposedly account for 4%...
Its not easy to get a perfect power profile because activities switch, or i forget to turn off the Wifi at work ( so its constantly wasting energy looking for a connection ), with then 4G/2G also active. Or forgetting to turn of the GPS after using the navigation.
In comparrison, my 2 year old Sony Z Ultra, this same type of activity ( minus any GPS usage because i tried to save the Sony Z Ultra from heavy work to extend its life ), resulted in about 2 days of work, before the battery started hitting close to 30 a 40% mark. At that moment i always charged up because it made me unconfortable.
On new battery, the Sony Z Ultra's life was closer to 2.5 days of activity. What is really not bad for a phone that big. Especially if we compare the battery life of most other smaller smartphone's from that time / era.
But the X2 so far is really trumping it massivly. If this was my ZU, showing 27% ( now ), i will have been like "o god, o god, need to charge it up" because its going to drain ( even doing nothing ). I do not have the same feeling with the X2.
And to be honest, i wasted a bunch of power because of the missing ability to automatically turn Wifi off, when your not near your home Wifi connection. So you end up with Wifi + xG active all the time outside. Love to install Trigger or any of the Xposed modules the moment it becomes available.
My estimate for tonight, when i officially hit day 7 ( 168 hours ), is that the phone will have 20% left. Hell, i can probably do another day and half with that. But i think that 20% is a good charge mark. Lower then that will damage the battery more easily ( if you keep low charging over time ).

Benjiro said:
Here are some power usage number over the last 6 days and half.
25/08 21.30: 100%
- Installing some software
- Wifi + Cell on all night
26/08 9.50: 93%
- Call 15 min
- Daily WeChat checks & talks
- Wifi ( useless, no connection ) + 2G + Cell on all day
26/08 17.44: 88%
- Some playing around
- Wifi + Cell on all night
27/08 9.22: 83%
- Call 15 min
- Lots of WeChat chatting
- Wifi ( useless, no connection ) + 2G + Cell on all day
27/08 17.23: 74%
- Wifi or 2G + Cell on all day, forgot to write down. Based upon the drop, i probably had 2G and no Wifi on.
28/08 9.22: 71%
- Some WeChat chatting & checking but low activity day
- 2G + Cell on all day
28/08 17.50: 69% << no joke .. only 2% that day??
... big gap, weekend. Forgot to write down numbers.
- Some software installing, playing round, internet usage, ... a bunch of things
- Wifi + Cell on all the time.
31/08: 08:00 ( Forgot to write down but it was in the 40% somewhere )
- GPS navigation for about 30 minutes in the car
- Wifi + 2G + Cell
31/08: 11.47 36%
- Chatting, etc ... you know the routine by now *lol*
- 2G + Cell all day
31/08 18.19: 31%
- 2G + Cell all night
01/08 9.50: 28%
...
In total my screen was on for about 5 hours according to the battery app but i have my doubts about the reporting. Sygic ( car navigation ) had run for a pure minimum of 30 minutes ( longer because i tested some things at home ), and this usage is not reported at all. And Sygic + GPS are medium/high power drainers.
My 4G/2G + Cell account for 24% of the power usage. Wifi accounts for 4%. My 5 hour screen time supposedly account for 4%...
Its not easy to get a perfect power profile because activities switch, or i forget to turn off the Wifi at work ( so its constantly wasting energy looking for a connection ), with then 4G/2G also active. Or forgetting to turn of the GPS after using the navigation.
In comparrison, my 2 year old Sony Z Ultra, this same type of activity ( minus any GPS usage because i tried to save the Sony Z Ultra from heavy work to extend its life ), resulted in about 2 days of work, before the battery started hitting close to 30 a 40% mark. At that moment i always charged up because it made me unconfortable.
On new battery, the Sony Z Ultra's life was closer to 2.5 days of activity. What is really not bad for a phone that big. Especially if we compare the battery life of most other smaller smartphone's from that time / era.
But the X2 so far is really trumping it massivly. If this was my ZU, showing 27% ( now ), i will have been like "o god, o god, need to charge it up" because its going to drain ( even doing nothing ). I do not have the same feeling with the X2.
And to be honest, i wasted a bunch of power because of the missing ability to automatically turn Wifi off, when your not near your home Wifi connection. So you end up with Wifi + xG active all the time outside. Love to install Trigger or any of the Xposed modules the moment it becomes available.
My estimate for tonight, when i officially hit day 7 ( 168 hours ), is that the phone will have 20% left. Hell, i can probably do another day and half with that. But i think that 20% is a good charge mark. Lower then that will damage the battery more easily ( if you keep low charging over time ).
Click to expand...
Click to collapse
That's awesome! I'm the opposite of you. I leave the screen brightness all the way up all day, use an hour or more of Navi, do about an hour of phone calls and Facebook, an hour or Web browsing, a half hour of Teamviewer, a half hour of texting, and maybe sneak in a game of Spades. The battery still lasts almost two days. This is amazing in a phone this size. No other phone I've had went this long on one charge with everything turned up. So far I really love this phone and plan on buying another soon.

ajsmsg78 said:
That's awesome! I'm the opposite of you. I leave the screen brightness all the way up all day, use an hour or more of Navi, do about an hour of phone calls and Facebook, an hour or Web browsing, a half hour of Teamviewer, a half hour of texting, and maybe sneak in a game of Spades. The battery still lasts almost two days. This is amazing in a phone this size. No other phone I've had went this long on one charge with everything turned up. So far I really love this phone and plan on buying another soon.
Click to expand...
Click to collapse
I know the feeling. Its one of those devices where you do not feel like your limited to x time on it, before you need to run to the charger.
Yesterday did about 30 min car ( 2 * 15 min ) navi with the car usb charger connected. The battery was at 62% before ( did some charging at work using the pc's usb port ) and it was 71% after i arrived home. The problem i have is, was it connected to the 2Amp port or the 1Amp ( its one of those Chinese dual usb ports mini chargers with no description: "what is what" *lol* ).
So still need to figure out if it was charging up on 1 Amps or 2 Amps ( to give me a idea of the power consumption while navigating ). The fact that it charged up while navigating is always a plus.
My old HTC HD2 had the habit of slowly draining while driving with the usb charger connected. Do not remember what my ZU did ( did not used it much for nav, mostly because of the limited battery life ).
So, my X2 is going to retire my ZU & HTC HD2 at the same time.

Benjiro said:
I know the feeling. Its one of those devices where you do not feel like your limited to x time on it, before you need to run to the charger.
Yesterday did about 30 min car ( 2 * 15 min ) navi with the car usb charger connected. The battery was at 62% before ( did some charging at work using the pc's usb port ) and it was 71% after i arrived home. The problem i have is, was it connected to the 2Amp port or the 1Amp ( its one of those Chinese dual usb ports mini chargers with no description: "what is what" *lol* ).
So still need to figure out if it was charging up on 1 Amps or 2 Amps ( to give me a idea of the power consumption while navigating ). The fact that it charged up while navigating is always a plus.
My old HTC HD2 had the habit of slowly draining while driving with the usb charger connected. Do not remember what my ZU did ( did not used it much for nav, mostly because of the limited battery life ).
So, my X2 is going to retire my ZU & HTC HD2 at the same time.
Click to expand...
Click to collapse
My X2 retired every phone I had including the Note 4 and Nexus 6. A seller on ebay is selling our Gold 32gb X2 for $409.99. I may pick up another one to have an extra.