Database Users

battery life drains from 100 to 90 to 80 to 70%....why

hi guys this may be a noob question but why does my x1's battery life drain in increments of ten like from 100% to 90% to 80% and so on....it doesn't really give me an accurate detail of how much battery life i have. Any ideas?
I'm using SPB shell 2, ROM version 1.03.931.8, software version R2AA008, generic UK
thanks for any input people!!!!!!!

It is the way, the phone (and/or its software) is build. It is as simple as that.

Please do a search. There are many threads about this issue already.

needs to fix battery.dll
offset near B880h

needs to fix battery.dll
offset near B880h
what does that mean? im not sure what the term means sorry kind of a noob to this

defconsc said:
needs to fix battery.dll
offset near B880h
what does that mean? im not sure what the term means sorry kind of a noob to this
Click to expand...
Click to collapse
yeah - i'd like to know more about this too

i saw fixed dll's from HTC thru WinHEX
so i notice that assembler's code in that place is different than X1's dll
but i very very bad in assembler
so i can't just cut asm code from one dll and paste in other, because after that needs to have some tuning up of the part of code...
but i know it very easy for specialist

Wait...I thought this was a hardware issue on the X1s...

hey so am i not the only one that has this problem...please let me know if you guys have the same problem and what are the steps to take to resolve the issue. I just want to have my battery percentage drain normal like 94% to 88% and so on. thanks

Here guys...read all about it
http://forum.xda-developers.com/showthread.php?t=475610
These guys have been trying a long time to get the 1% increments working...and haven't managed to do so yet...

stormlv> Thanks for the link.....so for now my questions are answered. Hope some one can fix this problem cause i hate that it drops in 10% increments. Keeping my fingers crossed that a solution will arise very soon!!!!

what difference does it make? lol. you only need to know when its at 100% or about 20% so you know when to charge it. whats in between is irrelevant. they probably set it to decrease 10% at a time because the x1 eats through battery power so quick. if it was set to 1% increments then it would be ticking down almost in real time lol

I'm actually quite happy about the battery life on the X1. I have no problems getting through the day, and I use my phone a lot, day and night. I don't even have to charge it everyday. Compared to other smartphones I've owned, including the Omnia, the X1 has pretty good battery life.

rogatsby said:
I'm actually quite happy about the battery life on the X1. I have no problems getting through the day, and I use my phone a lot, day and night. I don't even have to charge it everyday. Compared to other smartphones I've owned, including the Omnia, the X1 has pretty good battery life.
Click to expand...
Click to collapse
I second this. I don't have to charge my X1 daily and I use it for calls, texts, Twitter, web browsing, and music.

driver calculates percentage by some formula and give us result of CASE :
if current mAh / base mAh > 4070 then a:= 100 %
if current mAh / base mAh < 4070 and current mAh / base mAh > 3900 then a:= 90 %
etc.
in modified dll's that formula changed t a: = ( current mAh / base mAh ) * y
well, something about.
so IT IS NOT HW problem

anothadave said:
what difference does it make? lol. you only need to know when its at 100% or about 20% so you know when to charge it. whats in between is irrelevant. they probably set it to decrease 10% at a time because the x1 eats through battery power so quick. if it was set to 1% increments then it would be ticking down almost in real time lol
Click to expand...
Click to collapse
Lol...true...but when it drops below 20% id still want to have it in 1% increments. That came in quite handy on the P1i.
@ Ethermind
"so IT IS NOT HW problem"
Could we have the corrected driver then? I still don't get why someone would bother write cases when writing the pure percentage is so much easier. I'm a programmer...and programmers are lazy...they want to write the least amount of code. It beats me why theyd write 10 lines instead of 1...
Ethermind...do you have something to back up your claim?

stormlv said:
Could we have the corrected driver then?
Click to expand...
Click to collapse
In that topic:
http://etenclub.ru/board/otobrazhenie-zaryada-batarei-s-tochnostju-do-1-t15473-p-350.html
DeadMan have corrected dll of Eten for 1% percentage.
He explains code :
case CurrentVoltage
4070: percent=100%
4040: percent=95%
4010: percent=90%
Click to expand...
Click to collapse
I have downloaded dll from Eten - it almost the same as x1, but some parts of code and size.
so two strings
case CurrentVoltage
4070: percent=100%
4040: percent=95%
Click to expand...
Click to collapse
become 6 strings in corrected dll
case CurrentVoltage
4070: percent=100%
4065: percent=99%
4050: percent=98%
4055: percent=97%
4050: percent=96%
4040: percent=95%
Click to expand...
Click to collapse

Right...
It amazes me that someone would go to this much trouble to write cases...anyway...
I'll have a look at battery.dll and batdrv.dll and see if i can come up with anything...

stormlv said:
Right...
It amazes me that someone would go to this much trouble to write cases...anyway...
I'll have a look at battery.dll and batdrv.dll and see if i can come up with anything...
Click to expand...
Click to collapse
I ask DeadMan for code, so we must change our case on next:
Code:
start mov r0,#0x0F00;set maximum voltage to 4090mV
orr r0,r0,#0xFA
cmp r2,r0
movcs r3,#100
bcs exit
cmp r2,r1
strls r2,[r8,#20]
movls r3,#0
bls exit
sub r4,r2,r1
mov LR,#100
mul r3,r4,LR
sub r4,r0,r1
mov r0,r3
mov r1,r4
bl exit
mov r3,r0
exit nop
let's learn ARM assembler

i had a p1i too and one of the first things i noticed was the 10% increments. it did bug me at first but the battery doesnt last quite as long on the x1 as it did on the p1i so i know 20% isnt going to last more than a few hours. i can go about 2-3 days on average use between charges so i just charge it up and forget about it until it hits 20/30% and then i know that i have to charge it sometime that day. when it hits 10% i plug it in. no point waiting for 7% or 6% lol. seems that some people have put the 1% increments on a pedestal and its becoming a big deal. saying that, i wouldnt say no if some clever person figures it out i notice that sktools can give an exact voltage reading. surely someone can translate that information into a percentage?? similar to what deadman and ethermind are talking about.

HTC response on short Battery Life: Expect it!

I wrote to HTC to ask how they measured their "up to 490 hours on Standby" and "up to 380 mins talk time" referred to in their HD2 website specification especially as people like myself were experiencing the battery going flat in <24 hours with almost zero usage of the phone.
Here's their official reply.
Thank you for your email. The specifications that you have referenced are laboratory test conditions, and are not indicative of real-world performance, nor do they take into account the considerable drain incurred by the myriad services and programs that run as a matter of course on Windows Mobile 6.5, as well as any other background applications that may be running, which may not be readily apparent. Please be advised that these laboratory test figures are in line with EU regulations concerning the testing of mobile device batteries, and the real-world battery time that you have quoted of 20-24 hours is well within what we would expect of this device. We have recently released a large capacity battery for use with the HD2, and this can be purchased from the following link :- http://www.htcaccessorystore.com/uk/p_htc_item.aspx?i=195058
So in simple terms, we mislead you in our advertising and you'll be lucky to get the battery to last 24 hours. We can't fix it so buy a bigger battery!
What's the point in publishing performance data that has no relationship to "real-world" conditions. Most customers won't be using the phone in a laboratory.
Perhaps we should start a new campaign to get HTC to be more honest about "real-world" expectations.

Bobins24 said:
What's the point in publishing performance data that has no relationship to "real-world" conditions. Most customers won't be using the phone in a laboratory.
Click to expand...
Click to collapse
Because as they said that measurement procedure is a standard that everybody follows, so it would be stupid to do it differently, why "not lie" when everybody does so (and they actually probably wouldn't be allowed to do it differently).

Bobins24 said:
I wrote to HTC to ask how they measured their "up to 490 hours on Standby" and "up to 380 mins talk time" referred to in their HD2 website specification especially as people like myself were experiencing the battery going flat in <24 hours with almost zero usage of the phone.
Here's their official reply.
Thank you for your email. The specifications that you have referenced are laboratory test conditions, and are not indicative of real-world performance, nor do they take into account the considerable drain incurred by the myriad services and programs that run as a matter of course on Windows Mobile 6.5, as well as any other background applications that may be running, which may not be readily apparent. Please be advised that these laboratory test figures are in line with EU regulations concerning the testing of mobile device batteries, and the real-world battery time that you have quoted of 20-24 hours is well within what we would expect of this device. We have recently released a large capacity battery for use with the HD2, and this can be purchased from the following link :- http://www.htcaccessorystore.com/uk/p_htc_item.aspx?i=195058
So in simple terms, we mislead you in our advertising and you'll be lucky to get the battery to last 24 hours. We can't fix it so buy a bigger battery!
What's the point in publishing performance data that has no relationship to "real-world" conditions. Most customers won't be using the phone in a laboratory.
Perhaps we should start a new campaign to get HTC to be more honest about "real-world" expectations.
Click to expand...
Click to collapse
What can i say........except that HTC should look in to the real world more often!

I use many phones, from htc, and from other company , my last two nokia phones was "business versions" with "everlasting" battery - first e65 least 40h , second - better version - only 22h ( e66) - it's normal - in this world

If HTC say it's a standard EU process, then perhaps we should campaign to get the EU standard changed as the current published figures give no indication of the phones real performance.
Don't get me wrong, I love the phone but I've never seen one like this go flat in such a short time when on standby.

i love how they say it lasts up to 490 hours on standby, but 24 hours is what they would expect
it's actually ridiculous how deceitful these companies are, we deserve better than this
it's not right that they lie right to our faces to what we are getting and how we have no rights
just not right.

I think we need a bit of a reality check here. I'm not especially inclined to defend HTC but they have a point about the stuff that may be running on the phone. Anyone who has tried some new toys must have encountered one that sucks the life out of the battery for no obvious reason - scale that down and extrapolate across a raft of apps that most of us here will have on our phones and you will get a host of variations in terms of battery life...which is exactly what we do get.
Secondly, as kilrah said, that's the way battery life is measured. Instead of whining about it we should treat it as a relative indicator against other phones because that's about all it is good for. I suspect most say 'up to...' in small letters in front of their stand by and talk times anyway.
If I were to buy a car because the specs say that it does 40 miles to the gallon I'd be a mug to expect it to do that when I'm thrashing down the motorway towing a trailer with the windows and sun roof open. But I might well buy it in preference to a car that claims 30 mpg because in the long run it will probably cost me less in running costs.
You pays your money and you takes your choice...I don't personally see any significant misrepresentation in this, but there may be a little end user misunderstanding?

Bobins24 said:
...
Click to expand...
Click to collapse
No surprise here. I observed the same discrepancy on all my phones till now - Motorola, Nokia, Samsung, Siemens, Ericsson, Sony Ericsson, HTC.
Actually I use my phone a lot and I'm more than happy with its performance so far - huge and bright screen, powerful CPU... What are your expectations? 48 hours? A week?
If you think, this is something impressive, go and buy yourself a new monitor and then just measure the advertised contrast ratio - 10000:1 ? Seriously? In fact it is only 700:1. Nothing more to say.
Watch Out: Crazy Contrast Ratios

Exact. And especially on smartphones it's absolutely impossible for the manufacturer or a standards organisation to imagine how you will use your device.
If they can quote anything, it's stock configuration, open the box, put sim card in, press power on, enter your pin, put phone in standby, leave it there, note how long it lasts. That's all.
Knowing that you can do so many things on it, install so many programs that can do what they want to the phone, and that depending on usage the battery life can vary anywhere between 2 hours and 4 days it's totally impossible, by whatever means, to quote something realistic.

When you buy a WM device (or any other Lith-Ion device for that matter) you should know what to expect with regards to battery life, it's not rocket science.
Lithium-Ion batteries are poor, until battery technology is improved it's what we should have come to expect.

That's a bit simplistic, knowing that firstly there's nothing better yet, and secondly the good old phones we had that were lasting a whole week were also using the same batteries or even worse NiMH ones.
It's a combination of a lot of things.

battery life
I turned htc sense off on my phone and now the battery lasts 2-2.5 days with what i would deem reasonable use ie using the internet checking emails texting and 4 or 5 calls a day , if i turn sense back on the battery life drops to about 15 hours so i can live without sense !!! Im far more concerned about the speaker problems and pink photos than the battery )

kilrah said:
That's a bit simplistic, knowing that firstly there's nothing better yet, and secondly the good old phones we had that were lasting a whole week were also using the same batteries or even worse NiMH ones.
It's a combination of a lot of things.
Click to expand...
Click to collapse
I assume you are replying to me?
After having 4 HTC devices, I didn't expect anything more from the HD2 than I got from the Wizard or my Kaiser or my Diamond, if anything it was obviously going to be poorer due to the huge screen, hardware and all the software I knew I would be using.

I think your best chance of getting their claimed hours would be by:
1. Completely charging the battery;
2. Use a bare-bone ROM with absolutely nothing installed
3. Switching off all radio signals.. (that is, put the phone in flight mode so that the phone is not transmitting like wireless, bluetooth or anything else at all...)
4. leaving the phone on standby with the screen off.
Of course, noone uses their phone like that, but HTC have used the term "up to" to protect themselves...
HTC would be stupid to change the way they rate their times since every other company is using the same method. I doubt anyone would want to buy a phone that says "Standby Up to 24hours" when every other phone has "Standby Up to 500hours" At best, the rated hours could be used as a comparison/indicator against other phones.

I'm celebrating two weeks into life with my HD2, and after suffering water damage with my HD which had no effect except to bring battery life down to 8 hours a day, I'm really pleased with my 24-28 hours of battery life.
On days I'm using it a lot, I expect 15 hours. However the other day I barely touched the phone (no calls, no music, no random turning on the screen) and I was on 65% after 24 hours, which I felt was good.
I agree with the OP, their quotes are a joke, but I don't look at specs, I look at reviewers to tell me "I expect a day's life from this phone" etc. when I choose a phone. With a screen this size I don't expect miracles, but again, it does feel like a blatant lie when they suggest the phone can sit for weeks without dying, and i give manufacturers (including HTC) no credit for being economical with the truth to their customers.

My SEX1 used to last a few hours more, having a smaller screen, larger battery, and less than half the processor. They specced same timings, as I said I got a few hours more. I doubt Iphone or any other manufacturer, will spec their device like, Standby time 24hrs, talk time 4 hrs. Who would buy such a device?
Anyway I didn't expect it to last any longer. Good thing is I'm in front of my pc for long hours, no harm in letting the phone plugged in.

Isn't draining the Li-Ion actually shortens the battery life?
I'm told that letting the battery get lower than 2.3v isn't a good thing.
Let the battery get low, but not low enough for auto-shutdown

It's called Business Opportunity
All companies all over the world is like HTC.
Whenever there is a problem, they will direct you to purchase something to "solve" the problem.
HD2 problem that we are facing is poor battery performance (if you enable non-Sense). "Solution" is to buy bigger capacity battery.
Problem : screen easily crack
HTC "solution" : tampered glass screen (if HTC would advertise...)
Problem : Screen too sensitive
HTC "solution" : special screen protector (if HTC would advertise...)
Problem : this, that, this , that,
HTC "solution" : you pay, we gain profit!
That's the real world scenario....
Conclusion : HTC = poor quality product(s) at expensive price.

rickyoon.vegas said:
I'm told that letting the battery get lower than 2.3v isn't a good thing.
Let the battery get low, but not low enough for auto-shutdown
Click to expand...
Click to collapse
Auto forced shutdown is at 3.6V, which has a lot of margin not to cause damage.
HD2 problem that we are facing is poor battery performance (if you enable non-Sense). "Solution" is to buy bigger capacity battery.
Click to expand...
Click to collapse
Sensible solution: if you want battery life of more than 1-2 days, do not get a smartphone, especially not one that has the fastest processor on the market and a 4.3" screen. And read reviews that will tell you "you'll get 1-2 days" and "it lasts just a bit more than an iphone". I.e. Educate yourself.
Problem : screen easily crack
HTC "solution" : tampered glass screen (if HTC would advertise...)
Click to expand...
Click to collapse
Sensible solution: Realise you have a large piece of GLASS in front of you, and take care of it as such. Don't drop it, don't sit on it,...
We know how the HD2 behaves. If you read a couple of reviews, you know too. If you now buy it and still complain, there's not much we, or HTC, can do for you.

1% battery widget

Hey DG, here you go:
https://market.android.com/details?...oid.CircleBatteryWidget&feature=search_result
1% battery widget.

Great find.....THANKS

It does display in 1% increments but now I'm wondering how the stock 10% increment system works. My other widget shows 40% when I'm at 39% on this circular widget. If the circular widget is correct, then that brings up the question of when the 10% increments actually change.

my guess is that the widget is cheating and just estimating it until it actually receives the 10% drop. still useful

Just made the "sacrifice" of wasting battery to figure it out. The 10% increment changed from 40 to 30 when the circular widget changed from 35 to 34. Still leaves the option that the circular widget is just estimating, but it could be accurate...
Edit: It's consistent... 25 to 24 was the change from 30 to 20.

Doesn't display in 1% increments on my phone for some reason.

That's weird... can't imagine why it wouldn't work for you as well. Have you tried rebooting?
Off topic: Do you own a B5 S4, EvilEvo?
Back on topic: I've been watching as my battery lowers and it at least appears to be accurate. I'd definitely like to see confirmation on whether or not the hardware is limited to 10% increments.

CC Lemon said:
That's weird... can't imagine why it wouldn't work for you as well. Have you tried rebooting?
Off topic: Do you own a B5 S4, EvilEvo?
Back on topic: I've been watching as my battery lowers and it at least appears to be accurate. I'd definitely like to see confirmation on whether or not the hardware is limited to 10% increments.
Click to expand...
Click to collapse
from what designgears said, it is indeed a hardware limitation. that's why i said the program must be "cheating" and estimating the battery drop depending on use, since it cannot get a proper hardware read.

i use the fancy widget to display the clock and weather but in the setting i also enable it to show battery life as well and it shows by 1% increment.

its a cheater app.. sorta like the abttery calibration that we used to do on the epic...
you charge to full wipe stats let it fully drain then fully charge
then the app knows the rough approximation of the time and keeps track itself instead of relying on the phone/battery to tell it.
thers a few battery apps that behave this way

franciscojavierleon said:
from what designgears said, it is indeed a hardware limitation. that's why i said the program must be "cheating" and estimating the battery drop depending on use, since it cannot get a proper hardware read.
Click to expand...
Click to collapse
If you let your battery get below 20%, it starts reading in 5% intervals. Not sure why it would do that and not be able to do that elsewhere.
CC Lemon said:
That's weird... can't imagine why it wouldn't work for you as well. Have you tried rebooting? Off topic: Do you own a B5 S4, EvilEvo? Back on topic: I've been watching as my battery lowers and it at least appears to be accurate. I'd definitely like to see confirmation on whether or not the hardware is limited to 10% increments.
Click to expand...
Click to collapse
NVM, it didn't work at work at first, i guess the battery might have legit been at 50% haha. And yes I do, and use the same name on AZ and Vortex.

EvilEvo said:
If you let your battery get below 20%, it starts reading in 5% intervals. Not sure why it would do that and not be able to do that elsewhere. NVM, it didn't work at work at first, i guess the battery might have legit been at 50% haha. And yes I do, and use the same name on AZ and Vortex.
Click to expand...
Click to collapse
Because its probably not a hardware limitation lol. Im guessing its the driver.

EvilEvo said:
And yes I do, and use the same name on AZ and Vortex.
Click to expand...
Click to collapse
Recognized you from AZ lol.
EvilEvo said:
If you let your battery get below 20%, it starts reading in 5% intervals. Not sure why it would do that and not be able to do that elsewhere. NVM, it didn't work at work at first, i guess the battery might have legit been at 50% haha.
Click to expand...
Click to collapse
jug6ernaut said:
Because its probably not a hardware limitation lol. Im guessing its the driver.
Click to expand...
Click to collapse
That's what I'm thinking, or at least wondering about. It seems odd that they would design the hardware to measure in 10% intervals until the last 20%. I can't imagine the ability to do 5% intervals the whole time would be much more complicated or expensive to work into the design.

CC Lemon said:
Recognized you from AZ lol.
That's what I'm thinking, or at least wondering about. It seems odd that they would design the hardware to measure in 10% intervals until the last 20%. I can't imagine the ability to do 5% intervals the whole time would be much more complicated or expensive to work into the design.
Click to expand...
Click to collapse
Haha, ya. I recognized your name too.
I think it can be figured out. I'm not knowledgable enough in it, but I would look into however it displays or calculates the battery below 20%.

Is ZTE lying about Axon's 7 battery capacity?

I have installed many apps to find out the capacity of the battery all say 3100mAh. I installed and updated several versions of the O.S. from Marshmallow to Nougat thinking that maybe the OS were not showing the accurate battery size. But nothing...
As I've seen some videos tearing the phone apart and shows that indeed it has a 3100mAh only INSTEAD OF THE 3250mAh that ZTE claims it to have.
I am using the A2017G version bought from Amazon Germany. And it bugs and find it irritating that ZTE might be lying to us Axon users. Perhaps I'm wrong but.... I had to check with them.
After several emails and communication with ZTE they sent me this reply, which still DOESN'T ANSWER MY CONCERNS and their reply MAKES NO SENSE to me and I am an electronic engineer. I would like to hear from anyone who might have the same issue and/or just want to add some info. Thanks guys. Here's the reply from ZTE:
"Dear Valued ZTE Customer,
Thanks for contacting ZTE.
We are really sorry for the delay in response.
This email is with regards to the issue you had forwarded us about the wrong capacity battery that you have received.
We would like to inform you that, perhaps our concerned team has already informed you about the results they found from the test they performed.
However incase they haven't then, this is what they had to say about the battery issue.
The battery has two nominal values, one is the nominal value and the typical value. The A7 battery has a nominal value of 3250 mHA and a typical value of 3140 mHa.
As you mentioned by applying the check to the battery is 3100mhA, the possible reason:
1. Battery inspection application of the inspection program related to the application of detection methods affect the detection accuracy, the most accurate battery test is through a professional battery capacity test equipment to check, A7 battery capacity. The amount is measured by the battery capacity test equipment capacity, capacity is no problem.
2, The battery capacity itself will increase with the use of time, the battery capacity will drop, according to the standard battery cycle 500 times, the battery capacity reduced to 80% of the original qualified.
Should you require any further assistance, please do not hesitate to contact us."

Monk09 said:
I have installed many apps to find out the capacity of the battery all say 3100mAh. I installed and updated several versions of the O.S. from Marshmallow to Nougat thinking that maybe the OS were not showing the accurate battery size. But nothing...
As I've seen some videos tearing the phone apart and shows that indeed it has a 3100mAh only INSTEAD OF THE 3250mAh that ZTE claims it to have.
I am using the A2017G version bought from Amazon Germany. And it bugs and find it irritating that ZTE might be lying to us Axon users. Perhaps I'm wrong but.... I had to check with them.
After several emails and communication with ZTE they sent me this reply, which still DOESN'T ANSWER MY CONCERNS and their reply MAKES NO SENSE to me and I am an electronic engineer. I would like to hear from anyone who might have the same issue and/or just want to add some info. Thanks guys. Here's the reply from ZTE:
"Dear Valued ZTE Customer,
Thanks for contacting ZTE.
We are really sorry for the delay in response.
This email is with regards to the issue you had forwarded us about the wrong capacity battery that you have received.
We would like to inform you that, perhaps our concerned team has already informed you about the results they found from the test they performed.
However incase they haven't then, this is what they had to say about the battery issue.
The battery has two nominal values, one is the nominal value and the typical value. The A7 battery has a nominal value of 3250 mHA and a typical value of 3140 mHa.
As you mentioned by applying the check to the battery is 3100mhA, the possible reason:
1. Battery inspection application of the inspection program related to the application of detection methods affect the detection accuracy, the most accurate battery test is through a professional battery capacity test equipment to check, A7 battery capacity. The amount is measured by the battery capacity test equipment capacity, capacity is no problem.
2, The battery capacity itself will increase with the use of time, the battery capacity will drop, according to the standard battery cycle 500 times, the battery capacity reduced to 80% of the original qualified.
Should you require any further assistance, please do not hesitate to contact us."
Click to expand...
Click to collapse
Oh my dear God you get 150 mAh less! What is this madness?
Okay jokes aside, the battery capacity is actually 3140 mAh. I've seen this number before buying the phone, on reviews and one of the official pages, and when I bricked it, I took it apart and the battery says 3140.
Now a couple of things. assuming that the battery is actually 3140, they are saying that the battery has 110 mAh more. They are stating that the battery is 3.5% bigger than it is in reality. Is it worth spending all that time and effort writing the OP, asking ZTE for explanations, even watching disassembly videos, because the battery is 3.5% smaller?
And what do you plan to do, turn it back because you'll have 12.6 minutes less SOT?

Reply to "Choose a username"
Yes, your jokes are hilarious indeed. I'm talking about the principles here man. They're claiming something it isn't true. False advertising.
When you go to a McDonald's and they give you a half empty box of fries (which sometimes happens) do you just take it? At then end of the day, you, me and the buyers in general pay for the price that a company asks for. I don't know about you but when I buy something I expect it to be in good condition and fit for purpose. Or at least with the same specs as they advertise...
Whether it has 3.5% less capacity or not - that is NOT THE POINT. Point is they are advertising it incorrectly. And I HAVE TIME TO WRITE AND ADDRESS THE ISSUE TO THEM.
Yes, usually what I would do is return it, I have no problem returning stuff if they don't meet my expectations and Amazon is usually good regarding refunds. But I would not return it in this case, because as you correctly said, 110mAh less won't make a huge difference. But again, it's the principles man.
One other thing is if you read ZTE's reply, it doesn't make a lot of sense. It all sounds a bunch of excuses to me. Oh! Sorry, unlike me, you probably won't have time to read it.

Monk09 said:
Reply to "Choose a username"
Yes, your jokes are hilarious indeed. I'm talking about the principles here man. They're claiming something it isn't true. False advertising.
When you go to a McDonald's and they give you a half empty box of fries (which sometimes happens) do you just take it? At then end of the day, you, me and the buyers in general pay for the price that a company asks for. I don't know about you but when I buy something I expect it to be in good condition and fit for purpose. Or at least with the same specs as they advertise...
Whether it has 3.5% less capacity or not - that is NOT THE POINT. Point is they are advertising it incorrectly. And I HAVE TIME TO WRITE AND ADDRESS THE ISSUE TO THEM.
Yes, usually what I would do is return it, I have no problem returning stuff if they don't meet my expectations and Amazon is usually good regarding refunds. But I would not return it in this case, because as you correctly said, 110mAh less won't make a huge difference. But again, it's the principles man.
One other thing is if you read ZTE's reply, it doesn't make a lot of sense. It all sounds a bunch of excuses to me. Oh! Sorry, unlike me, you probably won't have time to read it.
Click to expand...
Click to collapse
Hell they're not giving you half the capacity advertised - just 3.5% less, that's my point. You wouldn't bother if they gave you 3.5% less fries would you. i guess that this would be relevant if they actually shipped with 3000 mAh. False advertisement would be more like what has been going down with the OnePlus 3 and 5. They make their phones go full throttle to get the best results on benchmark apps, and they appear at the top of the list because most new phones have the same 835 anyways. Or with the Huawei P10s where they claimed UFS 2.1 and changed that on the last week, and you could even get eMMC storage

Monk09 said:
Reply to "Choose a username"
Yes, your jokes are hilarious indeed. I'm talking about the principles here man. They're claiming something it isn't true. False advertising.
When you go to a McDonald's and they give you a half empty box of fries (which sometimes happens) do you just take it? At then end of the day, you, me and the buyers in general pay for the price that a company asks for. I don't know about you but when I buy something I expect it to be in good condition and fit for purpose. Or at least with the same specs as they advertise...
Whether it has 3.5% less capacity or not - that is NOT THE POINT. Point is they are advertising it incorrectly. And I HAVE TIME TO WRITE AND ADDRESS THE ISSUE TO THEM.
Yes, usually what I would do is return it, I have no problem returning stuff if they don't meet my expectations and Amazon is usually good regarding refunds. But I would not return it in this case, because as you correctly said, 110mAh less won't make a huge difference. But again, it's the principles man.
One other thing is if you read ZTE's reply, it doesn't make a lot of sense. It all sounds a bunch of excuses to me. Oh! Sorry, unlike me, you probably won't have time to read it.
Click to expand...
Click to collapse
Both capacities are correct. If you fill it up with, say, QC3 or a 2A charger, it will go closer to the 3140 mark, but if you charge it with a 1A charger, it will go closer to the 3250 mark. All modern lithium-ion batteries do this. Using you analogy, it would be like filling the fry container (? whatever it's called) with the fry container filler (? I know this is wrong) really fast and getting, say, 100 fries, versus taking 10 seconds and getting 104.

I feel like as this device gets older, the expectations in general get unrealistically higher and higher... Especially for a device that's less than $300 with a 2K super amoled display and periodic fw updates... ?

awsomjgp said:
Using you analogy, it would be like filling the fry container (? whatever it's called) with the fry container filler (? I know this is wrong) really fast and getting, say, 100 fries, versus taking 10 seconds and getting 104.
Click to expand...
Click to collapse
Whoa that was a deep analogy

Batteries typically have two capacities listed: a minimum (min) and a typical (typ). All companies tend to advertise the typical capacity, even if the battery you have is closer to the minimum.
For example, the LG G3 is advertised everywhere as having a 3000mAh battery (the typ size), while the battery itself has a min of 2940mAh printed on it.
Another example is the Moto G4 Play, which has a typ size of 2800mAh (which is what gets advertised), but has a 2685mAh min printed on the battery itself.
ZTE seems to have only listed the minimum capacity on the battery itself, not the typical capacity.

[Q] Strange battery behavior following software update

I recently pulled the trigger on the MPHS25.200-23 official Android N software update for the Moto X Pure Edition. Aside from the concerns I listed among the release notes in the rollout discussion thread, I have been reasonably satisfied with the update. However, battery life absolutely plummeted after installing it. A hard reset was executed before (and after) the update and a cache/dalvik/art wipe was completed a couple days after getting everything set up.
Battery percentage drops at record speeds while the screen is on (although standby time is still okay). Using a Nexus 6 for reference, I compared results using Ampere and didn't notice any significant difference in power use (at least while idling with the screen on). Using the CPU usage monitor tool found under the debugging panel, nothing seems out of the ordinary here either (idling and light use shows a figure in the 9s, typically).
At this point, I figured misbehaving software could be ruled out, so I turned my attention to the battery. On my laptops, I can use either the OEM's power manager application or a Windows commandline tool (in Windows 8 and newer) to generate a battery health report, showing the "design capacity" and the actual "full charge capacity" in mah, which is a very good indicator of a battery's health. I struggled to find an equivalent to this on Android, but, after some digging, did find some promising leads
The trouble is that the results aren't consistent. On the Nexus 6, running "dumpsys batterystats | grep "Capacity"" shows a "Capacity" of 3220, which just happens to match the design capacity of the Nexus 6's internal battery. Running "dumpsys batteryproperties" shows "2910000" at the bottom next to "Full charge." Since the Nexus 6 is close to 3 years old now, it would make sense that the battery is only good for 2900 mah. Everything makes sense so far...
On the Moto X Pure Edition, however, "dumpsys batterystats | grep "Capacity"" yields a puzzling "Capacity: 1948." "dumpsys batteryproperties" yields "Full charge: 1948000". This makes no sense. If "Full charge" represents the design capacity, (not taking usage into account) why would it show as only 1948 on the Moto X?
Now, I'm opening this up to the community. What do you see when you run the first command?
Code:
dumpsys batterystats | grep "Capacity"
Do you see the expected design capacity of 3000 or do you also get a small (or smaller) number like I did?
Either way, I'd like to see people's results for the second command as well:
Code:
dumpsys batteryproperties
How close is the resulting "Full charge" value to the rated 3000?

The battery never was a 3000mah. That was a lie.
Have you done a factory reset since the update?

I get:
estimated battery capacity : 2996 mAh
and :
ac: 0 usb: 1 wireless: 0 current_max: 0 voltage_max: 0
status: 2 health: 2 present: 1
level: 96 voltage: 4411 temp: 267
current now: -182951
charge counter: 2905046
current now: -185
cycle count: 2
Full charge: 2730600
although my battery misbehaves big time ! from full charge to 80 in less than 10 minutes.

Thank you for the input
autosurgeon said:
The battery never was a 3000mah. That was a lie.
Have you done a factory reset since the update?
Click to expand...
Click to collapse
I figured as much, but not a value nearly half that! Definitely performed a hard reset, both before and after the update.
roozbeh101 said:
I get:
estimated battery capacity : 2996 mAh
and :
ac: 0 usb: 1 wireless: 0 current_max: 0 voltage_max: 0
status: 2 health: 2 present: 1
level: 96 voltage: 4411 temp: 267
current now: -182951
charge counter: 2905046
current now: -185
cycle count: 2
Full charge: 2730600
although my battery misbehaves big time ! from full charge to 80 in less than 10 minutes.
Click to expand...
Click to collapse
Interesting. This is more in line with what I was expecting to see on my own system, although it's surprising to hear that your phone still misbehaves as it does.

Bill720 said:
Interesting.
Click to expand...
Click to collapse
Bought February this year:

Going to try battery replacement
At this point, I'm going to chalk the issues up to a failing battery and simply consider this a coincidence. Does anybody who has done a battery replacement recently recommend any good brands or vendors who sell a decent battery that I won't have to bend to make fit? One eBay seller who I have contacted says that he normally sells the flat ones, but will provide a curved battery in its place if the customer specifically asks for it at checkout.

It may not be a bad battery, as I had the same issues and I recently replaced my battery with a battery the seller swears is brand new, and again it is behaving exactly like the old battery.
So I am at a loss as to what to try. How do you fool the system into thinking the battery is brand new?
I just decided to check the dumpsys batterystats and it shows absolutely nothing
dumpsys does not give me any information at all, is this a permission problem?

The plot thickens...
roadrun777 said:
It may not be a bad battery, as I had the same issues and I recently replaced my battery with a battery the seller swears is brand new, and again it is behaving exactly like the old battery.
Click to expand...
Click to collapse
Interesting. What time of runtime (screen-on time) are you seeing? Do you remember what seller/store you got the replacement from? Was the replacement flat or curved, like the original battery?
roadrun777 said:
I just decided to check the dumpsys batterystats and it shows absolutely nothing
dumpsys does not give me any information at all, is this a permission problem?
Click to expand...
Click to collapse
Don't try "dumpsys batterystats" without the "grep "Capacity"," else you'll get so much output that the device might freeze and then reboot.
The fact that you're getting no output with either command seems unusual though. I don't know if it'd make a difference for sure, but, out of curiosity, do you have busybox installed?

Yes I have busybox installed, let me go check version.
busybox 1.27.2
I thought maybe it was because I was plugged in but I installed a terminal app get root and check it internally without it being plugged in and nothing, there is absolutely no data.
So I am at a loss as how to fix this. Something is either hijacked the system and is hiding the data or there is no data and the processes that create it have not run correctly, which then means I will have to hunt down exactly what processes create the info.
Any help would be appreciated as I've been doing stuff like this without help for decades and it gets very time consuming to track down bugs for developers that are too busy driving around in their humvee's and flying to Europe to care.

Strange output; are you running the stock rom?
roadrun777 said:
Yes I have busybox installed, let me go check version.
busybox 1.27.2
I thought maybe it was because I was plugged in but I installed a terminal app get root and check it internally without it being plugged in and nothing, there is absolutely no data.
So I am at a loss as how to fix this. Something is either hijacked the system and is hiding the data or there is no data and the processes that create it have not run correctly, which then means I will have to hunt down exactly what processes create the info.
Any help would be appreciated as I've been doing stuff like this without help for decades and it gets very time consuming to track down bugs for developers that are too busy driving around in their humvee's and flying to Europe to care.
Click to expand...
Click to collapse
That's really weird that the command takes, but displays no output. My Samsung Epic (with a CyanogenMod build of Ice Cream Sandwich) simply scolds me when trying to put the commands in. The only time when I can achieve no output (on the Pure Edition or Nexus 6) is if I forget to go root before typing the commands. Are you on the stock rom?

No good, it seems
Well, I received the replacement battery today and installed it. To my surprise, however, there was almost no measurable change in runtime; I charged it up and burned down half a tank with only about 45 minutes of screen-on use! I ran those commands again, and this time, both values indicate a touch over 3000. I'll give it a few cycles to see if things return to normal, but if not, then I'm at a loss. Are there any negative consequences to "downgrading" to Marshmallow?

Unusually high power draw spotted, as reported by Ampere
Quick addendum: I tested again using a program called Ampere, and found that current draw is actually a bit on the high side. Comparing alongside the (nearly identically-configured) Nexus 6, using multi-window, I found that current draw is actually often doubled, and sometimes even tripled.
For example, when playing an HD YouTube video, the Nexus 6 maintained a draw of around 330, give or take a few dozen (fluctuating between around 300 and 430). However, the Pure Edition was between 800 and 1400, typically settling at around 1100 to 1300. Thinking that there may be some kind of software issue after all, I rebooted into "Safe Mode" and tried using the device that way, but saw no perceptible change (at least as best as I could tell without being able to run Ampere).
With that in mind, I'd like to pivot more to a discussion of what kind of power draw everybody is seeing in Ampere under light usage and video watching, regardless of what Rom or kernel you're running. Is anyone else seeing high power draw while doing relatively little?

200-22 was the ticket!
Well, this will be the second time that a weird, untraceable issue wound up being solved by flashing back to stock and upgrading. I installed that 200-22 factory image, took the new update, (October security level) and everything appears to be fine and dandy once again. Runtimes are much better and Ampere reports much lower power consumption (idling below 250ma and light use in the mid-to-low hundreds; which is much less than half of what I was seeing before).
Idle power draw (prior to restoring most of my apps) was holding steady at around 1.4% per hour, averaged over about 24 hours of non-use. And that's without any of the Amplify or Greenify tweaks.
I'll have to withhold final judgement until all of my data and software is restored, but things are looking really good so far. That "Sprint" factory image appears to have saved this Verizon-network-user's bacon.

Update...
Maybe that wasn't it after all. Battery life started tanking again within a couple of weeks after the operation, so there must be some software I'm installing that isn't playing nice somehow (even though Wakelock Detector shows no noteworthy periods of unrest). It's odd because I have almost the exact same software load on my backup phone (the Nexus 6) and can leave that thing in the backpack for days on end without it losing much charge at all, while the Pure Edition is managing to run down at a rate of about 4 percent per hour, screen-off and unused.
While the device is awake and running, Ampere shows an idle power draw of between 450 and 1000 mah, which, while (probably) not as bad as before, is still consistently higher than it should be.
The silver lining to this whole thing is that I now have so little time in the day to actually use the phone that it usually doesn't matter. If I get the chance again, I might switch back to the Nexus 6 temporarily again to troubleshoot the Pure Edition more carefully. There has to be something that I'm missing.

same issue here after updating to NPHS25.200-15-3, i have to charge the phone almost twice as before. looking at apps usage shows nothing unusual. i'm checking battery performance using accubattery

Power use figure?
hagi_mostafa said:
same issue here after updating to NPHS25.200-15-3, i have to charge the phone almost twice as before. looking at apps usage shows nothing unusual. i'm checking battery performance using accubattery
Click to expand...
Click to collapse
What's your idle power draw as measured by Ampere?

Bill720 said:
What's your idle power draw as measured by Ampere?
Click to expand...
Click to collapse
Check these two shots

Going to have to find the answer the hard way
hagi_mostafa said:
Check these two shots
Click to expand...
Click to collapse
Are you running stock rooted? At this point, I'm beginning to wonder if I got a bum replacement battery, since the whole thing just shut down spontaneously on me one day at around 20%. I'll try switching back to the Nexus 6 and start over with the Pure Edition again, this time installing things one-at-a-time (or in waves while making liberal use of backup images) to see what (if anything) is not sitting right with it. The most perplexing thing of all is that I have the Pure Edition configured almost identically to the Nexus 6 in terms of tweaks and software, and yet the Nexus lasts 2-4 times longer.
Even right now, I'm sitting at 4% with about 32 minutes of screen-on time and 36 minutes of background audio playback over about 12 hours. In contrast, the Nexus 6 is at 74% with just over 1 hour of screen-on time and 52 minutes of screen-off audio playback (and yes, I do have an active Sim card installed in it too, albeit on a different carrier). In essence, the Nexus managed to do twice as much with one quarter the power draw, so I know for a fact that something is wrong, either in hardware or in software, and my experiments over the course of the coming weeks will confirm, one way or another, which is the case.
This whole experience really has soured my whole opinion of this phone. I still believe that it's one of the best smartphones ever made, but there's no doubt that it has a serious problem, and I'm disappointed by both possible outcomes. If it ends up being software, then it'll be plain that Lenovo screwed up in a big way to make it so that I could duplicate the same weird bug twice in a row with a fairly common/minimal setup that should not cause any problems. On the other hand, if it ends up being hardware, then that'll be the end of the line for this phone, plain and simple, seeing as few of the available battery replacements don't completely suck. Honestly, I'd have replaced this phone sooner, given how much time it's cost me, but there's just nothing affordable I could go to that wouldn't be a compromise. I guess the dream of "decent smartphone" just wasn't meant to be for any longer than that first year .

Bill720 said:
Are you running stock rooted? At this point, I'm beginning to wonder if I got a bum replacement battery, since the whole thing just shut down spontaneously on me one day at around 20%. I'll try switching back to the Nexus 6 and start over with the Pure Edition again, this time installing things one-at-a-time (or in waves while making liberal use of backup images) to see what (if anything) is not sitting right with it. The most perplexing thing of all is that I have the Pure Edition configured almost identically to the Nexus 6 in terms of tweaks and software, and yet the Nexus lasts 2-4 times longer.
Even right now, I'm sitting at 4% with about 32 minutes of screen-on time and 36 minutes of background audio playback over about 12 hours. In contrast, the Nexus 6 is at 74% with just over 1 hour of screen-on time and 52 minutes of screen-off audio playback (and yes, I do have an active Sim card installed in it too, albeit on a different carrier). In essence, the Nexus managed to do twice as much with one quarter the power draw, so I know for a fact that something is wrong, either in hardware or in software, and my experiments over the course of the coming weeks will confirm, one way or another, which is the case.
This whole experience really has soured my whole opinion of this phone. I still believe that it's one of the best smartphones ever made, but there's no doubt that it has a serious problem, and I'm disappointed by both possible outcomes. If it ends up being software, then it'll be plain that Lenovo screwed up in a big way to make it so that I could duplicate the same weird bug twice in a row with a fairly common/minimal setup that should not cause any problems. On the other hand, if it ends up being hardware, then that'll be the end of the line for this phone, plain and simple, seeing as few of the available battery replacements don't completely suck. Honestly, I'd have replaced this phone sooner, given how much time it's cost me, but there's just nothing affordable I could go to that wouldn't be a compromise. I guess the dream of "decent smartphone" just wasn't meant to be for any longer than that first year .
Click to expand...
Click to collapse
after several cycles accubattery shows that a full battery just works no more than 3 hours. in some cases it even lasted for just one hour or less!
so of course there's something wrong here.
the issue has appeared exactly since i upgraded from 6.0.1 to version 7, both official xt1572 asia ds. just flashing boot and system files. no root custom recov or else.
so i really doubt that this could be of a hardware failure. also i'm using the same collection of apps as in rom 6.0.1 so this is not an app issue.
as accubattery shows battery health and power usage, battery health is 80% at 2580mah and power usage is high, something between 500 up to 700 mah.
the only possible cause resides in rom or flashing. i'm gonna try flashing us rom and if the problem continued, i'm gonna flashing latin ds with boot system and modems.

Gratitude for the information
hagi_mostafa said:
the issue has appeared exactly since i upgraded from 6.0.1 to version 7, both official xt1572 asia ds. just flashing boot and system files. no root custom recov or else.
Click to expand...
Click to collapse
Good to know. Mine is the North American XT1575 variant, but I'm in the same boat otherwise. The trouble seemed to start almost immediately after installing the new 7.0-based update, so there's a good chance that it's related to this in some way. Mine is rooted, (stock rom/kernel, however) but it's good to know that somebody running stock is seeing the same thing.
hagi_mostafa said:
so i really doubt that this could be of a hardware failure. also i'm using the same collection of apps as in rom 6.0.1 so this is not an app issue.
as accubattery shows battery health and power usage, battery health is 80% at 2580mah and power usage is high, something between 500 up to 700 mah.
the only possible cause resides in rom or flashing. i'm gonna try flashing us rom and if the problem continued, i'm gonna flashing latin ds with boot system and modems.
Click to expand...
Click to collapse
I don't think that it has anything to do with the software region. I'm on the standard North American build with the same problem, so the issue (if in software) must be a broader one. I'm going to try to switch back to the Nexus 6 today so that I can start the long process of starting over on the Pure Edition and getting to the bottom of just what causes things to crash & burn.