I have two U11 (I'm going to return one, or both) and I noticed significant differences in terms of battery life between them.
Running PCMark battery life test, auto-brightness OFF, brightness MAX, one phone consistently gets 4h53 of screen on time, and the other one 5h08 (from 100% to 20% battery). That's a 5% difference and it's not negligible. Phones are the same otherwise in terms of apps installed. Problem is, the phone that has the worst battery life starts apps a TINY bit faster...
So the bottom line is, phones have significant manufacturing differences.... and I don't know which one to return.
They have same firmware and all identical? are you sure? maybe some app is configurated different or something.. or one battery its more degraded
5% is close negligible. I've got two U11 and they don't perform any differently. You aren't going to get identical numbers on two different handsets running benchmarks.
Hardware parts may be more or less efficient than each other. Radios on one device may be a few percent better. Honestly just send one back and get it done with. You also forget about coy CPU variances (no two chips are the same).
Different bin could be the reason there is a slight difference.
Ivancp said:
They have same firmware and all identical? are you sure? maybe some app is configurated different or something.. or one battery its more degraded
Click to expand...
Click to collapse
Hardware/ firmware / software is identical.
Galactus said:
5% is close negligible. I've got two U11 and they don't perform any differently. You aren't going to get identical numbers on two different handsets running benchmarks.
Hardware parts may be more or less efficient than each other. Radios on one device may be a few percent better. Honestly just send one back and get it done with. You also forget about coy CPU variances (no two chips are the same).
Different bin could be the reason there is a slight difference.
Click to expand...
Click to collapse
Well the geekbench and 3D mark are exactly the same (like give or take 0.1%).
ppaasseeii said:
Well the geekbench and 3D mark are exactly the same (like give or take 0.1%).
Click to expand...
Click to collapse
Doesn't mean a battery benchmark is going to be within 0.1% the same as when you look at Youtubers who benchmark multiple of the same device and get somewhat different Antutu benchmark results.
5% is nothing to fuss over
Galactus said:
Doesn't mean a battery benchmark is going to be within 0.1% the same as when you look at Youtubers who benchmark multiple of the same device and get somewhat different Antutu benchmark results.
5% is nothing to fuss over
Click to expand...
Click to collapse
It's like starting with a battery at 100% vs starting at a battery at 95%. For the rest of the life of the phone. Kind of a big deal.
Anyways, I'm running another test now with a low screen brightness, in case one screen was brighter than the other one (at max brightness) and drained more battery, I'll keep y'all posted.
Try with all radios (wi-fi, gsm, bluetooth, nfc, gps) off, even in location settings (disable scanning nearby devices for improved accuracy), and force stop all installed apps before the test. That gives me about 10 to 15 % increase on AnTuTu score. Maybe log cpu load and speed while testing as well.
I agree 5% is not a big deal, but would definitely keep the longer standing
Edit: force stopping because you may have installed the same apps, but most background processes won't load until you first time run their app, so one of the two "identical" devices may actually be running less apps in background. Best for testing would be to factory reset both devices and not load anything into them nor change any settings except the backlight for test.
How do you use both phones in the same manner to expect same result? You text same person with both phones making sure time taken to perform the task is same for both? And different phones have different usage pattern hence the 5% difference..??
Besides....that's 15mins. I definitely consider that as negligible. A 20% difference would be something to concern yourself about.
Related
I am a bit concerned about the battery life of the upcoming htc. The first reviews I have read about it on german blogs speak from 12 to 15 hours battery life under medium to heavy usage. Even though, one needs to remain cautious with these numbers as the software is not finalized, I wouldn't expect these to double when final.
The Incredible S has a quite satisfying battery life according to users experience. But the Sensation has a bigger screen, higher resolution, a full load of 3D effects and almost the same battery. I fear the battery life will be insufficient in that case, even though dual core is supposed to consume a little less.
Samsung has built a slightly bigger battery on his GSII and people seem to experience a very good battery life. But Amoled doesn't drain the battery when black is displayed and the whole UI has been designed in black for this purpose. So the Sensation will probably not be able to achieve such an autonomy.
Hopefully it will still go through the day under heavy usage. Otherwise I might gonna settle for incredible s instead.
Has anyone read other numbers somewhere?
eadred said:
I am a bit concerned about the battery life of the upcoming htc. The first reviews I have read about it on german blogs speak from 12 to 15 battery life under medium to heavy usage. Even though, one needs to remain cautious with these numbers as the software is not finalized, I wouldn't expect these to double when final.
The Incredible S has a quite satisfying battery life according to users experience. But the Sensation has a bigger screen, higher resolution, a full load of 3D effects and almost the same battery. I fear the battery life will be insufficient in that case, even though dual core is supposed to consume a little less.
Samsung has built a slightly bigger battery on his GSII and people seem to experience a very good battery life. But Amoled doesn't drain the battery when black is displayed and the whole UI has been designed in black for this purpose. So the Sensation will probably not be able to achieve such an autonomy.
Hopefully it will still go through the day under heavy usage. Otherwise I might gonna settle for incredible s instead.
Has anyone read other numbers somewhere?
Click to expand...
Click to collapse
This is how I see it. Multi-core cpu's theoretically are more power efficient. You spread work over both cores, if software is optimized, to allow for less "strain" on the cpu. From what I can tell they are "optimizing" their Sense UI to run on both cores which efficiently manages the amount of power is being used. This now gives you less power draw hence power is saved. The battery isn't as big as some devices, but in my honest opinion I believe you will get a little more than 12-15 but probably won't get up to double that. This is all based off of my own conclusions after reading several articles. I may be wrong and if you need to correct me feel free. =) All I will say is you probably won't have to worry about battery issues.
Wondering if there's a difference in speed when using Bubby's root method versus the ACE hack kit. I rooted my phone about a year ago, my GF just did hers a couple weeks ago, and I could swear there's a difference between the two handsets, though they're both Inspire 4G's. Just curious to know if there's anything to my observation, or if it's a case of things always taking longer when you're waiting for them, rather than when you're the observer.
What specifically takes longer on one than the other.
Tx Redneck said:
What specifically takes longer on one than the other.
Click to expand...
Click to collapse
Oh, say for example things like opening and closing the app drawer, switching between apps, and general interface operations. I also find that my Favorites dialer widget tends to refresh a lot, particularly after a call - the icons will reload. That might be a different issue, but figured I'd mention it.
Sent from my Inspire 4G using Tapatalk
Probably speed difference due to what's installed on the phones. Number of apps. Type of SD card (maybe) things like that. It seems that the more I flash and change stuf on my pho.e the slower it gets. So I've started doing Full Wipes every few weeks. Even to my SD card taking everything off and only putting back what I actually use. It realmseems to help a lot. Also I've noticed that when a dev makes a full wipe zip for the Rom, that it works better when doing that along with the full wipe option you get with 4ext
Hope I helped
BillTheCat said:
Oh, say for example things like opening and closing the app drawer, switching between apps, and general interface operations. I also find that my Favorites dialer widget tends to refresh a lot, particularly after a call - the icons will reload. That might be a different issue, but figured I'd mention it.
Sent from my Inspire 4G using Tapatalk
Click to expand...
Click to collapse
That different issue may be associated, as it sounds like you may be suffering from a bit of lag. Have you tried running quadrant tests for comparison purposes? Not all Inspires will perform exactly the same. My wife's Inspire has always gotten a slightly better signal than mine, while my GPS has always performed better than hers. There will be variances with processor as well, although it should be minor.
Sent from my HTC Inspire 4G using Tapatalk
Let's not forget about ROMs. They all perform differently, too.
If you config them IDENTICALLY and yours is slower, then the proc/emmc may be inferior to what's in your wife's device. It's not unlike pc parts, you could have two kits of matching ram and one won't oc as well as the other. Same for processors too. Q6600 G0 SLACR will generally oc better than most other Q6600's.
Well, they're the same machine - Inspire 4G's, though I bought mine in March of last year from AT&T, she got hers in red from Target just about three months ago. The idea of variances between CPUs makes sense, though. Just figured I'd ask, since I hacked using Bubby's method and she used ACE, so I thought that might have made a difference.
BillTheCat said:
Well, they're the same machine - Inspire 4G's, though I bought mine in March of last year from AT&T, she got hers in red from Target just about three months ago. The idea of variances between CPUs makes sense, though. Just figured I'd ask, since I hacked using Bubby's method and she used ACE, so I thought that might have made a difference.
Click to expand...
Click to collapse
Also manufacturers make plenty of changes throughout a product's life. Small revision changes that may reduce cost, increase stability, boost performance, sometimes lower performance. As long as it is not running 'poorly' then small differences are expected just with the enormous list of variables. Just take the faster phone and give her the slower one!
BillTheCat said:
Oh, say for example things like opening and closing the app drawer, switching between apps, and general interface operations. I also find that my Favorites dialer widget tends to refresh a lot, particularly after a call - the icons will reload. That might be a different issue, but figured I'd mention it.
Sent from my Inspire 4G using Tapatalk
Click to expand...
Click to collapse
It could always be the rom. To compare better, you both need the same rom and version. With the app drawer, maybe you have the app drawer able to cache, and she doesn't? Just a guess.
Could be updated parts on her phone. I remember when I had my HTC Tilt when it came out then my sister had hers replaced a little bit before it was removed from the market and it was significantly faster than mine flashed with a ligh rom designed for speed.
Not exactly sure about this, but one would have to assume that battery charge levels could have an effect on the speed of the device and it's process speeds. the battery stays at nearly the same voltage during the charge cycle, but does begin to roll off as the battery power declines.
It could be said that decreased battery power would have a forced undervolt effect depending on it's level of charge, thus slowing down the device as it discharges.
Or....It's quite possible I'm full of crap, and have no Idea.
If you agree with the last sentence, please hit the thanks button out of pity....g
gregsarg said:
Not exactly sure about this, but one would have to assume that battery charge levels could have an effect on the speed of the device and it's process speeds. the battery stays at nearly the same voltage during the charge cycle, but does begin to roll off as the battery power declines.
It could be said that decreased battery power would have a forced undervolt effect depending on it's level of charge, thus slowing down the device as it discharges.
Or....It's quite possible I'm full of crap, and have no Idea.
If you agree with the last sentence, please hit the thanks button out of pity....g
Click to expand...
Click to collapse
There's a voltage regulator in there maintaining the supply to the phone. The voltage you read in any battery monitor app is the voltage of the battery. The regulator should be feeding about 3.3-3.5v from that source, so once the battery drops below those levels, things die off. You are right, as supply voltages drop the phone wouldnt function at it's full potential, there is just circuitry providing the proper levels regardless of the battery's voltage.
Just wanna ask around to check if I'm the only one who feels my phone is a tad bit too hot?
Usually when not charging , the batt temps are around 34-38°C, with the CPU in the range of 38-45°C
When charging the batt goes up to 38°C - 44.7°C or even overheating in the 45-50°C range( ok this would be my fault in using heavier apps)
And the CPU would stay in the range of 40°C - 55°C even without use sometimes
Those temperatures aren't out of the ordinary for this device, that's pretty normal actually. I've had my battery temperature go between 50-55°C fairly regularly, and even as high as 66°C without the phone shutting down (I did cool it down very quickly upon seeing how hot it was though).
Sent from my Evita
timmaaa said:
Those temperatures aren't out of the ordinary for this device, that's pretty normal actually. I've had my battery temperature go between 50-55°C fairly regularly, and even as high as 66°C without the phone shutting down (I did cool it down very quickly upon seeing how hot it was though).
Sent from my Evita
Click to expand...
Click to collapse
Thanks timmaaa, for a moment I thought I was the only one.
I use Battery Mix to record my temperature vs. Battery % over time (use the JB feature to disable its persistent notification): https://play.google.com/store/apps/details?id=jp.smapho.battery_mix&hl=en
One thing I've noticed is that when it hits 40C+, the space below the camera becomes extraordinarily hot! This happens at least once during a work day, especially happens when I don't touch the device.
When this happens, the drain rate just plummets (when I refer to the battery level slope vs. the phone temperature). However, a reboot fixes the heat (and as a result, the drain rate) over a lengthy amount of time.
I've heard of this, but haven't gotten around to trying it successfully:
http://forums.androidcentral.com/ht...g-red-while-charging-rapid-battery-drain.html
That shouldn't happen while you're not using the phone. Have you used an app like BetterBatteryStats to identify what's draining your battery?
Sent from my Evita
well this was previously answered by timmaa i had a similar concern cause none of my earlier phone actually felt that warm...
but when i got a green signal that these are normal temperatures, i tried gaming for almost an hour turns out the phone was hot indeed the battery was around 50+ but still the phone dint shut down itself or showed any inconsistency in its functions!
moral of the story.. it happens with everyone.. my friend has a endeavor it also suffers from heating... its so normal that if u search it in google that "why does ht one x get..... "it automatically completes it in with " get hot"(also for the new One).
if you want to cool it down get SET CPU and create a profile in which select battery temperature/cpu temperature at a certain temperature you don't want your phone to exceed and then set the cpu to a lower speed typically till 1026 or 1134...
but again if u feel its necessary cause doing so will obliviously slow down the device.:angel:
Sonone said:
moral of the story.. it happens with everyone.. my friend has a endeavor it also suffers from heating... its so normal
Click to expand...
Click to collapse
Of course its normal. All computers generate heat as power is discharged. Manufacturers are also packing more and more computing power into these small devices, and in general that means more heat (although there are other variables). And every smartphone is designed to deal with the heat differently, so those might be some reasons why your previous phones did not feel as warm.
redpoint73 said:
Of course its normal. All computers generate heat as power is discharged. Manufacturers are also packing more and more computing power into these small devices, and in general that means more heat (although there are other variables). And every smartphone is designed to deal with the heat differently, so those might be some reasons why your previous phones did not feel as warm.
Click to expand...
Click to collapse
true that!!
even i was actually worried before hearing about it being normal from u and timma as well!
its probably htc one x is build that way.
BTW sorry a little off topic since this issue has already been resolved has anyone heard a little rattling sound near the camera region only when the phone is sharked up and down (from screen to back)
this also is a build issue!
Sonone said:
BTW sorry a little off topic since this issue has already been resolved has anyone heard a little rattling sound near the camera region only when the phone is sharked up and down (from screen to back)
this also is a build issue!
Click to expand...
Click to collapse
Totally normal. Just a moving part in the camera module. Likely related to autofocus as you can sometimes hear a sound when focusing the image.
Sent from my HTC One XL using xda app-developers app
Hello.
I brought a nexus 5 in the first week of release, and the battery has never been great but as its not often im a heavy user i get by. But i am curious why it seems a fast majority of people achieve far greater battery life/SOT, as like i say i dont have many apps installed and not a heavy user.
Is there any difference in the hardware from the original ones co!pared to the versions you can buy currently?
I have tried root, greenify, standard you name it and always seem to reach same level.
andy46 said:
Hello.
I brought a nexus 5 in the first week of release, and the battery has never been great but as its not often im a heavy user i get by. But i am curious why it seems a fast majority of people achieve far greater battery life/SOT, as like i say i dont have many apps installed and not a heavy user.
Is there any difference in the hardware from the original ones co!pared to the versions you can buy currently?
I have tried root, greenify, standard you name it and always seem to reach same level.
Click to expand...
Click to collapse
There's no difference, no.
4
There's a battery life sticky thread in this very forum, have a read of that. Battery life is affected by many variables, especially environmental ones.
andy46 said:
Hello.
I brought a nexus 5 in the first week of release, and the battery has never been great but as its not often im a heavy user i get by. But i am curious why it seems a fast majority of people achieve far greater battery life/SOT, as like i say i dont have many apps installed and not a heavy user.
Is there any difference in the hardware from the original ones co!pared to the versions you can buy currently?
I have tried root, greenify, standard you name it and always seem to reach same level.
Click to expand...
Click to collapse
I believe the released a slightly modified second version with slightly bigger speaker / microphone holes. That's it, nothing that would affect the battery performance so you need to change your thinking.
Use the dedicated battery troubleshooting thread in general. Root by itself won't do anything, and greenify only does so much.
You need to diagnose exactly what is using your battery. SOT is only one crude measurement. It all depends on how you use the device, not just the apps. Keep an eye on wakelocks, and things like screen brightness and signal strength.
eddiehk6 said:
I believe the released a slightly modified second version with slightly bigger speaker / microphone holes.
Click to expand...
Click to collapse
They actually didnt. It was simply manufacturing tolerances that made people think that. Even today, a newly manufactured device could have bigger or smaller holes.
I am currently on stock Android 12. I flashed the unlocked stock image (non-verizon) a few weeks back. With Android 11, Android 12, LineageOS, etc. every browser I have tried including Chrome, Brave, Via, etc. all drain the battery way faster than browsers did on my previous Moto G5 plus. i would say when I am surfing the net on my browser (usually just reading forums, no video), the battery drains about 1% every 5 minutes or less. I have tried 2.4Ghz wifi, LTE, etc. and data connection type doesn't seem to impact anything.
Is this normal for this phone? anything to do to reduce browser battery drain?
If you go into battery usage graph, is the browser the only app listed as using up the battery (and not the screen brightness, or another app that may be contributing to the heavy usage)
JohnC said:
If you go into battery usage graph, is the browser the only app listed as using up the battery (and not the screen brightness, or another app that may be contributing to the heavy usage)
Click to expand...
Click to collapse
correct. if I am using other apps the battery drain isn't near as severe. I keep the display setting "extra dim" enabled all the time and I keep it down as low as I can tolerate. I use a pitch black wallpaper use dark mode in browsers so they have mostly black background with white text.
Phone idle is the only other thing that seems to use a sizeable amount of battery according to the battery usage data in settings.
Sounds about right. Came from a Moto G7 Play (15 months back) and saw similar drain rates. All three devices have similar battery specs which plays into the units being used to assess drain. Is what it is.
FWIW - Opera
DB126 said:
Sounds about right. Came from a Moto G7 Play (15 months back) and saw similar drain rates. All three devices have similar battery specs which plays into the units being used to assess drain. Is what it is.
FWIW - Opera
Click to expand...
Click to collapse
Not gonna lie, it makes me want to go back to Motorola when this Pixel bites the dust.
badtlc said:
Not gonna lie, it makes me want to go back to Motorola when this Pixel bites the dust.
Click to expand...
Click to collapse
Many Moto's bring a nice package with unique tricks. Gotta do your homework on what features are most important when the time comes.
DB126 said:
Many Moto's bring a nice package with unique tricks. Gotta do your homework on what features are most important when the time comes.
Click to expand...
Click to collapse
I definitely did that. I only got the 4a because it was the perfect size and had a headphone jack. I assumed with a newer hardware set and similar sized battery compared to my old phone batter life "should" be better. Nope.
Na, it's more complicated. 4a sports more sensors, brighter/denser display, faster processors, etc. System and personal apps clearly play a role in longevity (behind screen brightness); you'd need to do a detail study to understand what's drawing when and why.
I use to fuss over such matters but find the device lasts a full day for my use case which is all that really matters. Charges up quick from a modest size battery pack when camping/traveling. Just like past Motos.
Not sure who I'll partner with in the next dance. Love Pixel cameras (especially in challenging conditions) and routine updates. Miss some of Moto's innovations, like active display and actions. Needs to be close to AOSP; no Samsung UX butchery. In the end form factor will likely be the deciding factor once non-contenders are ruled out.
badtlc said:
I assumed with a newer hardware set and similar sized battery compared to my old phone batter life "should" be better.
Click to expand...
Click to collapse
I don't know what CPU you came from, but if the Moto only had "small" cores then of course it used less battery. "Big" cores use more power. They go faster too, but if you have a constant load, then they'll eat battery faster.
I don't know if there's a non-root way to disable the big cores, but I suspect you can do it with root (but don't know for sure).
Otherwise, you gotta get your browser to stop running JavaScript. If you're watching video you need to make sure the browser is offloading all the decoding to the hardware codecs rather than doing it on the CPU.
And if the screen is on, it might help to try and get it "more black" (eg. Use night mode) or turn down the brightness. The screen is often the primary user of power when a device is being used.
a1291762 said:
I don't know what CPU you came from, but if the Moto only had "small" cores then of course it used less battery. "Big" cores use more power. They go faster too, but if you have a constant load, then they'll eat battery faster.
I don't know if there's a non-root way to disable the big cores, but I suspect you can do it with root (but don't know for sure).
Otherwise, you gotta get your browser to stop running JavaScript. If you're watching video you need to make sure the browser is offloading all the decoding to the hardware codecs rather than doing it on the CPU.
And if the screen is on, it might help to try and get it "more black" (eg. Use night mode) or turn down the brightness. The screen is often the primary user of power when a device is being used.
Click to expand...
Click to collapse
Thanks for the suggestions. My power complaints are just limited to the browser so I dont think it is just the larger CPUs. I think my standby consumption issues are related to Stock Android as I am now running GrapheneOS and my standby power consumption now matches my old Moto G5 Plus.
As for browser usage consumption, I have tried everything but disabling Javascript. I will try that and see if it breaks anything I use regularly. Thanks for the idea.
tangent back to general power consumption, I typically disable just about everything behind the scenes as I can. I keep the theme on pitch black. I use the extra dim setting to keep screen brightness as low as I can tolerate. I use night mode in browser to keep as much black background as possible. I disable all tap-to-wake or sensor based features. When I was trying to run Android 12, I disabled all the smart services and removed all the google apps I could. I removed all permissions I could. I restricted all apps I could. I disabled adaptive settings, etc. There is a bunch of stuff running in the background on Android 12 and I just could not
Welcome to the future. Older phones had better battery life
Locklear308 said:
Welcome to the future. Older phones had better battery life
Click to expand...
Click to collapse
I dont think it is all the phone. GrapheneOS has 40% better standby battery usage than stock android 12. On graphene, it matches my old Moto G5 Plus. It is either lazy programmers with inefficient coding these days or it is google having the stock OS do waaaay too much by default with no way to disable it.
I'm trying to figure that out now.
badtlc said:
I dont think it is all the phone. GrapheneOS has 40% better standby battery usage than stock android 12. On graphene, it matches my old Moto G5 Plus. It is either lazy programmers with inefficient coding these days or it is google having the stock OS do waaaay too much by default with no way to disable it.
I'm trying to figure that out now.
Click to expand...
Click to collapse
I totally agree on the lazy thing. So many devs now days are so lazy. I develope QuickBase databases and constantly run into extremely poorly setup realms/apps. Just basic stuff. Lol