Related
I've read in a bunch of other threads that people are getting awesome battery life out of their Z or G2. Mine is okay-ish. I had a hero before which seemed a bit better. there are a couple of odd things I thought I'd check tho...
First, the keyboard backlight turns on and off at seemingly random intervals while open. Anyone else got this?
Also I've seen screenshots of the battery use screen showing how much power is used by each system. The screen always is at least 75% on mine, even when its been sat in a pouch most of the time with just a couple of messages or a phone call- this seems quite different to other peoples experience.
Is there any reliable way of benchmarking the battery to check? If not, does anyone fancy helping me test?
im actually suffering from the same problem,
i thaught it was because the first week i was using it lots thats why the battery wasnt lasting long, but on monday morning with a full charge ,
only with a few calls , texts and checking train times on TFL , by the time i got to sleep that night the battery was on 30%
I was shocked , checked the battery useage meter , everything was below 5% except the screen which was was on a shocking 80%
I Then formatted the phone , restored to default , removed everything ,
set the brightness to lowest useable which was just above the 'o' on 'ok' in the brightness screen let it charge to 100% for use on tuesday.
Tuesday - Morn before i left for work it was on 100% , the only thing i had setup on it was email, brightness on low - but useable .
Screen must have been on onliy for 20 mins throughout the day
Got home , battery was on 45%
battery useage - again display was taking over 70% of it when it was hardly on .
I am RMA'ing this one tommorow
I think its an issue internally with something shorting on the display, battery shoudlnt be draining that much if its not on
Out of interest was yours a UK Desire Z ?
Yep. This sounds exactly like my situation in every detail. I couldn't believe reports from other people saying their batteries were at 92% after 12 hours- even without using mine at all this wouldn't happen.
Mine is a UK desire z, from play.com. I think its over 14 days so RMA might be tricky, although I know I have lots of rights thanks to distance selling regulations. Hope I can exchange without too much fuss.
Ooh, just thought of something. When I set the brightness really low on mine (below 20% or so) the screen flickers slightly. It's most visible on a totally white page. Does yours do the same? Faulty backlight maybe?
pizza65 said:
When I set the brightness really low on mine (below 20% or so) the screen flickers slightly. It's most visible on a totally white page. Does yours do the same? Faulty backlight maybe?
Click to expand...
Click to collapse
Just tested mine, definitely no flicker.
Now my experience with the battery....
I play about half hour - an hour of games every day, plus about up to an hour wifi, using the xda app throughout the day using data, 10 - 15 txts and a few 1 - 2 min calls... Not too heavy usage.
I'm getting 30-36 hours, I'm happy....
BUT..... I have not plugged in through mains once yet. I read that charging through USB gives better performance... so far that is looking true.
I got the same kind of time out of my Hero using mains but that was with zero game time.
yes! pizza65 , i noticed the flickering too! , i thaught it was just my eye being twitchy ! Noticeable on internet browsing on low brightness! .
Mine was from handtec .. (amazon delayed too much) so changed last min,
it comes with a 2 year manufacturer waranty i think so even if you take it up with HTC direct they should be able to help if play dont.
I tried a diff radio and rom , but it made no difference.
Maybe the UK batch is still faulty , wasnt that the reason why it failed google testing and got delayed for release here?
Whats your hinge like ?
ddot what network are you on ?
same to you pizza65?
im on 02 , i dont think it is a network radio issue with switching of hspda/3g to 2g signals as it does say cell standby battery useage is around only 6% , but then again the phone could be false reporting
pizza65 said:
Is there any reliable way of benchmarking the battery to check? If not, does anyone fancy helping me test?
Click to expand...
Click to collapse
Not really if you want realistic real-world results with data connectivity etc. It varies too much since everything counts like signal strength.
You can always just turn off everything and burn the battery with a movie but first thing you should do is a few dozen full discharges before you do anything. I've noticed that HTC (and other manufacturers too) pre-use their batteries ie. charge and recharge them until they're optimal for consumers, hence the whine about bad batteries when people buy new phones (and in reviews as well).
I'm on Orange, I don't think its network because, as you confirmed, the "battery use" screen says that the screen is draining all the power. If nobody else gets a flicker on low brightness (it can take a few seconds to see it, but once you notice it...) then it looks like our screens are the culprit. Maybe.
I've deleted batterystats.bin and fully charged, so ill give that another chance before talking to play.
Ddot, what percentage of the drain is from the screen on your z? Also, if you press 'display' in that menu it will say how long the screen has been on, what does it say?
I have the same issue with battery performace. I've moved to Desire Z from my old Desire which had AMOLED display. On my old one, the display taked 5-8% of battery. On Desire Z I have minimum 50%, but ussually ~70%.
After reading that some people can use their DZs like "for two days of heavy use (gaming, browsing)" or "5% for 6 hours" I can't understand how?
Comparing to old Desire my DZ have poor battery performance. But the specs tells it must be much better.
I'll publish my battery usage stats after some days. Maybe it'll be useful.
Sent from my HTC Vision using XDA App
In additional.
I have stock Sense ROM with root and S-Off. No overclocking kernel. My SetCPU profile is set for 245 MHz when screen is off.
Sent from my HTC Vision using XDA App
Interesting read...desire users, amoled etc. cynogen mod, 2.2 android:
http://code.google.com/p/cyanogenmod/issues/detail?id=2012
Another snippet:
http://www.goodandevo.net/2010/08/h...ry-and-possibly-double-your-battery-life.html
a variation:
http://forum.xda-developers.com/showpost.php?p=6796078&postcount=1
i'm in similar shoes like you guys. i'll try these.
I'm using SetCPU 245MHz idle, stock Z rom.
tbalden said:
Interesting read...desire users, amoled etc. cynogen mod, 2.2 android:
http://code.google.com/p/cyanogenmod/issues/detail?id=2012
Another snippet:
http://www.goodandevo.net/2010/08/h...ry-and-possibly-double-your-battery-life.html
a variation:
http://forum.xda-developers.com/showpost.php?p=6796078&postcount=1
i'm in similar shoes like you guys. i'll try these.
I'm using SetCPU 245MHz idle, stock Z rom.
Click to expand...
Click to collapse
Very interesting, thanks for sharing
And a really "geek" method here quoted from cyanogenmod issue:
Comment 27 by david.j.erickson, Aug 19, 2010
Now, I was still having abnormal drain on my battery. As suggested in the Wiki and also confirmed in another cyanogenmod post, clearing the battery stats can help. I followed this procedure:
Fully charge the battery, says Full and 100% under Settings - About phone - Status.
Reboot into recovery, wiped battery stats. Phone still plugged in at this point.
Reboot into rom, checked to make sure battery was still Full and 100%.
Unplugged phone.
Killed it, used Maps on Wifi and messing around. Killed it in about 3 hours or so.
Tried turning it on a couple times to make sure it was *dead* dead. It still tried to boot, but couldn't complete without shutting off.
Plugged phone in, booted it up. It may be better to not turn it on until it is fully charged, but this is just what I did.
Let it charge overnight, next morning took it off charger since it was full.
I have noticed pretty good battery life since doing this. This morning on my bus ride in I pretty much constantly played some Storm8 games and used Listen with Bluetooth, was only down to about 82 or 84%, can't remember. This is on par with previous CM release for me.
Not sure why this rom in particular had so much worse battery drain out of the gate, and not just for me. Fortunately it seems correctable. Maybe if a few of you could give this a try and see if it improves your battery performance we could conclusively say battery calibration is the solution.
Click to expand...
Click to collapse
What about the flicker? Can anyone confirm that?
I have a UK (read: QWERTY) Desire Z, first batch.
I tried reprodocuing the flicker by lowering the brightness completely and looking at a blank white page in the internet browser. Couldn't see it. Maybe I wasn't looking hard enough.
That said, I'm not getting the great battery life that most seem to be getting, and the stats always show the Display as being the number one drain. HOWEVER, it doesn't seem quite as bad as you guys are saying.
Right now, it looks like this:
Unplugged for 18 hours and 16 minutes, battery at 36%
Display accounts for 41% of the drain
It has been on for 50 minutes.
(stock ROM, running an IM client 24/7, synced to three email addresses... Typoclock seems to use 2% of the battery every time as well, which seems relatively high for such an innocuous little widget)
Yeah. I have some slight flickering too, slight when low light set.
Uk stock.
I dont think high display percent is an issue too much reading cyanogen issue comments.if you use nothing but low cpu burden apps, display should eat most.
Also if i have it off, power is eaten by cell standby.
Im still hoping for a settled battery log mentioned in forums.
My 2 cents:
If I "use" the phone, I have to plugin it every night.
If I do not "use" it (nobody calls that day, no browsing or GPS (Just work!)), I plugin it every two day (ex. mon - wed - fri).
The display is always 65-80 % of the "drain problem".
Today the stats are:
7.30 am: full chargerd 100%
7.30 pm: display drains: 70% in 1h : 21m - battery at 20%
I leave automatic background gmail sync on (only daylight, I use the "Flight mode" overnight)
No bluetooth, no wifi, no gps, brightness 35-40%
lordevol said:
I leave automatic background gmail sync on (only daylight, I use the "Flight mode" overnight)
No bluetooth, no wifi, no gps, brightness 35-40%
Click to expand...
Click to collapse
No phone either.
I'm on a North American Desire Z and I see the display using 70%-80% of the battery when I have the display on for approximately two hours out of the day. I keep my display quite dim too, at 20% brightness.
I'm also running everything stock. No root, no custom ROMs, no anything.
Isnt display percentage actually the display driver cpu time eaten?its just a theoretical value isnt it, not watts gone? It seems obvious that its eating a lot as it refreshes all the time regardless of display light level.
My screen on is only 33% today, im sure its usually higher though. Maybe its due to me flashing stuff all day. Ill do a full charge tonight and report back Sunday.
...bought from e2save, a part of carphone warehouse.
Sent from my HTC Vision using XDA App
Hello all,
I've been suspicious of the power draw of the screen on the GNex, and so decided to figure out how much a difference brightness made.
This is to test the difference extreme brightness settings make to battery run times. Including text, browsing or having radios on will dilute the results. I'm only interested in the efficiency of the screen and its supporting infrastructure people!
Here's my testing method.
1. Charge phone to 100% using a PCs USB charging (should give a more full charge than the wall adapters quick charge, I think, otherwise no harm done). Leave attached to USB cable
2. Switch the phone into Airplane mode.
3. Switch off Auto Brightness and turn brightness to Max
4. Restart Phone. Leave it to settle for a few mins
5. Fire up "Just Pictures" and the image "TotalWhite.jpg" (attached). No other photos in the folder where it sits.
6. Disconnect USB charging
7. Start Slide show. Record the start time.
8. Every now and then (about 45 mins to an hour and bit) I quickly pop into settings and take a sneak look at charge level - don't want to get caught out!
9. Resume Slide Show.
10. Wait until the phone switches off, which is less than 2% charge
Now, it's not a quick process as I'm going from 100% Batt until auto shut off. So I'll be updating this post in installments. Today is the Max Daddy Full Brightness White image!
Full Brightness, White Image:
100% 00h00m
85% 00h39m
60% 01h53m
35% 03h08m
0% 05h00m
Pretty good I think!
Battery status stated that Screen was 91% and Android System was 9%. Screen on time was the same as the run time. It never went off.
There's a heavy set of disclaimers to go with this though: The White Image isn't quite the right aspect for it to display across the full amount. Check out the image "White Full The Phone.jpg" - it's pretty close though. Just Pictures isn't so full screen that it takes over the Android buttons - Anyone know a 100% full screen picture view BTW? Between the point where it comes up with "Please connect your charger" (15%) and 6% it said that message over the White image and partly dimmed the screen - I'm at work and was in the middle of something when it happened.
Minimum Brightness, Black Image:
100% 00h00m
85% 01h26m
82% 02h05m
18% 08h54m
0% 10h47m
Battery status stated that Screen was 85% and Android System was 16%. Yes, that's 101%, but there you go... Screen on time was within a minute of the run time.
Again, some notes on the testing: From the "connect your charger" point (i think 15%) to 8 % it had the message on the screen. Just before the end I accidently touched the screen and ended the slide show for up to 15 minutes and the screen went off. Switched it back on and it was at 2%. It then lasted something like 30 mins before auto shutdown. Black isn't Black! check out my the photo "Black Dim The Phone.jpg" - ignore the strange black specs, it was 1 seconds exposure at F1.4, with the camera facing down - think there's some crap in my camera body/lens.
Minimum Brightness, White Image:
100% 00h00m
0% 10h20m
Again, Battery status stated that Screen was 85% and Android System was 16%. That's the same as when I ran it on Min Brightness, Black Image...
Maximum Brightness, Black Image:
100% 00h00m
0% 10h52m
Battery status stated that Screen was 90% and Android System was 11% (again 101% also probably due to some rounding going on). Screen was on 100% of the time, Android OS was awake for 100% of the time, CPU time 23 Seconds
Overview:
Maximum Brightness White Image: 5h00m
Maximum Brightness Black Image: 10h52m
Minimum Brightness White Image: 10h20m
Minimum Brightness Black Image: 10h47m
Well, well, what's happened here? Maximum brightness with a black image scored the longest run time - unbelievable, right? Yeah pretty much: On the minimum brightness black run I did check the battery stats a few times. The black image run had a greater Android OS drain (11% vs 9%) compared to the white image. As I switch the phone off in preparation for the test it's possible I inadvertantly bump charged the phone. In addition to this, I was trusting the phone a lot more in this, the final test and didn't check the battery status near the end, so perhaps drawing a lower current happily sitting there doing nothing other than displaying a blank image the phone managed to syphon off the last dregs of power, as opposed to spending CPU time with me rummaging through the settings screens for battery stats. Let's put it all down to being in the margin of error and consider the Black images to have the same run times, despite the Android buttons blazing away on Bright (but they aren't many pixels).
Conclusion:
Back to my original concern, that the screen was abusing the battery more than necessary. I'm mostly happy with the outcome - Black bright and dim screens draw substantially less than a very bright white screen on this phone, as it should. It's surprising to see that on dimmest setting the white screen got so close to the run time of the black screens. It's producing a lot more light than either black screen. It's drawing c5% more power than the black screens, but I would expect a lot more. I'm guessing that the circuitry to run the Screen and the small amount of power used to make the "Black" OLEDs glow dark dark grey draws only a little less than the white screen.
And that's a shame. I wanted to run an app such as "Off-Clock" to have a clock on the screen like the Nokia N8 used to do, but i'm thinking this will eat the battery in 10 hours 20 minutes. Only one way to know for sure....
My initial annoyance that Black never is actually Black whilst the screen has faded. Many of you good folks have pointed out (and after more Googling) that all OLED screens have this, although the reason for it isn't clear. It's either to ease the transition from black to lit by having the LED at the threshold already, power seeping into the circuit somewhere or something else. Who knows, maybe we'd get better run times if the screen was on full brightness but used PWM or a fast strobe to show a dimmer image!
That's all folks, discuss, and remember - continue testing...
I love you for doing this. Please don't stop.
Some tidbits: The whole phone was warm, front and back. Not scary hot, but like a nice hand warmer. The screen shots were actually done after I connected the charger and restarted the phone. You'll see the graph shows it starting to charge, but all the stats are for when it was last on the battery - in the test.
Thanks for testing this.
How do you define min brightness?
The black color, do you mean #000000 hex color code?
That will last days!
Sent from my Nexus S using XDA App
excellent thread that's it's about screen time on no idle time
gogol said:
Thanks for testing this.
How do you define min brightness?
The black color, do you mean #000000 hex color code?
Click to expand...
Click to collapse
Not too scientifically - I made it black in MS Paint. It's a JPG. I tried it out in portrait and landscape on full brightness and I can't see the edges of anything on the screen, so it's as black as the rest of the black in Gallery. If you have a better way, then I'd gladly take a 16x10 black image if you think it is more black.
Min brightness will be using the brightness slider in settings. I haven't rooted the phone so don't see any way to get it lower. I tried the app "Dimmer" but it's the same brightness as far as I can tell as min setting. Also I figured the min setting was relevant to more users than something they can't easily get to (or probably see on screen!).
Do you have any suggestions? I want to root, but my home PC can't see my GNex. It's being a pig about it and I haven't got Broadband ATM... Hope to root as soon as I can.
Just a quick input. If you just show a picture for 5h how does the cpu perfom in this time? Isn't it really bored?
In addition if you switch it to air plane mode it doesn't use any power for transmitting a signal. I know this point is really tricky due to the fact that not everybody receives the same signal strength.
Isn't there a more realistic way to test it? Like a combination of stability test and the white picture?
Or a slide show with specific pictures, for example a picture with lots of green, one with a lot of red, one with blue, one with white and one with black?
I really like the idea but if we could create something like a standard which tries to simulate real usage that would be great for future testings.
So that we could say something like:
Galaxy Nexus with Vanilla Android -> 5h with XDA battery benchmark
Galaxy Nexus with CyanogenMod 9 -> 5.3h with XDA battery benchmark
We could compare different settings and see how good they perform based on a "standardized" procedure.
Hmm is this probably a bit too much?
I like the idea of a standardized battery procedure for XDA.
Only thing is, i feel like just web browsing would give a better idea, mostly white website sites and it uses data and CPU/GPU still to give real world usage results.
Nebucatnetzer said:
Isn't there a more realistic way to test it? Like a combination of stability test and the white picture?
Or a slide show with specific pictures, for example a picture with lots of green, one with a lot of red, one with blue, one with white and one with black?
I really like the idea but if we could create something like a standard which tries to simulate real usage that would be great for future testings.
Click to expand...
Click to collapse
Hi Nebucatnetzer, I get what you're going for and think it would be a great test. My original goal was just to see how much of a drain the screen was. I used it on Airplane mode as I do not want to have any other drains diluting the result. As you say, signal strength changes, and so this becomes an uncontrollable variable. I'm only showing a white image as it's the most uniform full power test of the screen I can think of. As the display is RGBG, maybe a greenish white would draw more, but I can live without that - web pages are predominantly Plain White and Text in ICS is white.
I actually think that 9%/10% drain for Android OS may be a bit high for 5 hours. I think Just Pictures may be the cause for it as it does every minute change the image in a slide show... to itself...
pewpewbangbang said:
I like the idea of a standardized battery procedure for XDA.
Only thing is, i feel like just web browsing would give a better idea, mostly white website sites and it uses data and CPU/GPU still to give real world usage results.
Click to expand...
Click to collapse
It was one of the things which annoyed me the most here. Everyone says he has the ultimate tweak to save juice but you never really could measure it.
We probably have to skip the data part due to asimilar signal strengths.
And it would be really cool if we could find something which works for every phone.
pewpewbangbang said:
i feel like just web browsing would give a better idea, mostly white website sites and it uses data and CPU/GPU still to give real world usage results.
Click to expand...
Click to collapse
Hi! I'm not trying to do a real world test as such. I'm trying to find out how much of an impact a white screen has compared to a black screen. I have a suspicion that the Black screen will draw more than it should do. I've been using my phone on Auto Brightness and at night, min brightness and have found the screen is caning the battery. There's more to the screen than the AMOLED - there's also a MIPI Framebuffer controller, plus whatever interfaces that has to the rest of the phone.
I'm aware that ICS and the other internals of this phone seem quite efficient, so any savings I can make on the screen (which really does suck the juice) should translate into big run time gains... Surely...Right?
If it turns out that there's very little different in battery life between a Black screen and a white screen, then I'll crank up the brightness to revel in its retina destroying beauty. If there is a difference, then i'll stick with my black homescreen background....
The black screen shouldn't draw any power virtually as long as its truly black. SAMOLED functions where black doesn't turn the pixel on so no energy is used. I think the black test has been done by someone, you can probably google it.
We we aren't criticizing you specific we just hijacked the thread a bit sorry for that .
Nebucatnetzer said:
We probably have to skip the data part due to asimilar signal strengths.
And it would be really cool if we could find something which works for every phone.
Click to expand...
Click to collapse
would be good if someone could make a benchmarking program which pumps out signals in a set pattern on all devices at set frequencies and at a few different power levels. It would't need to wait for a response from any cells or WiFi routers, just talk to itself and only itself. Maybe this would need too low level access to work, below root.
Then you'd have your predictable Radio part of the test. If it's even possible.
pewpewbangbang said:
The black screen shouldn't draw any power virtually as long as its truly black. SAMOLED functions where black doesn't turn the pixel on so no energy is used. I think the black test has been done by someone, you can probably google it.
Click to expand...
Click to collapse
Well, I hope a black screen will draw considerably less. We shall see. Or it will be a revelation... Or everyone will get to witness me finding out that my phone is defective. Hahaha... oh...god I hope not...
I may run the black test overnight. It should last the night. If it doesn't I can always hook it up and check the last "On Battery" status as I did earlier. Then I can run two tests tomorrow!
Davidsmonkeyroost said:
would be good if someone could make a benchmarking program which pumps out signals in a set pattern on all devices at set frequencies and at a few different power levels. It would't need to wait for a response from any cells or WiFi routers, just talk to itself and only itself. Maybe this would need too low level access to work, below route.
Then you'd have your predictable Radio part of the test. If it's even possible.
Click to expand...
Click to collapse
This sounds more than difficult. Not a clue how one could do this.
As soon as I have my device I'll probably start a thread where we can think about a standardized (what a stupid word) battery test.
Curios how your second test goes.
Instead of the black screen test, amoled screen, you could do a white background with black text. This would give better overall real world stats.
Text generator http://www.lipsum.com/feed/html
Second test - black on lowest brightness - is underway.
Some bad news, which you may already know about: Black isn't black. It's very dark, but the phone isnt switching all the pixels off. I took a photo with my SLR in the dark but can't upload at the moment, will upload tomorrow.
Just took a sneaky look at the stats.
85% 01h26
The draw is 85% screen and 16% Android OS. Yeah, I know they don't add up, but that's what it says.
So far, the draw is higher than I expected for lowest settings with a black image. Odd. The phone isn't warm though, like when the screen was showing a white, max brightness image. It's cold.
Sure hope it doesn't start moaning about running flat whilst i'm asleep...
Last check before I go to sleep: 82% 02h05
Same split of 85% screen and 16% Android OS. Who says percentages have to add up to 100?
Davidsmonkeyroost said:
Last check before I go to sleep: 82% 02h05
Same split of 85% screen and 16% Android OS. Who says percentages have to add up to 100?
Click to expand...
Click to collapse
Most likely rounding bug.
I'm coming from a thunderbolt with an extended battery. I'm used to crappy battery life, and indeed I lose about a percent an hour playing music on my galaxy nexus with is way better than my thunderbolt.
The issue comes that when I have the screen on I lose about 1-2% a minute, even if I'm just reading an ebook. Calling is fine, DOWNLOADING/STREAMING is fine, but the screen on just kills the battery.
It also gets very, very hot on the upper portion of the screen, but doesn't if I'm downloading something with the screen off.
My question is, is this normal?
As well, the screen has a yellowish tint when looking at it directly, but takes a blue tint at a very slight angle (annoying) is THIS normal?
I want to know how much arguing and yelling I'm going to have to do when I try to exchange this phone.
Writing this took me from 22% to 13% D=
I'm new to Galaxy Nexus phones, but i've been here long enough to know that the yellow tint and blue side view tint is a manufacturer defect.
My battery drain, too, is really bad.
currently, it's 57% of my battery drain, but its been as high as high-60's before.
Facebook comes in 2nd, killing 10%. Almost makes me want to uninstall it.
Today, I noticed it was hot when it was idle in my pocket throughout the day.
It could be bad heat dispersion because of the slim design or cpu usage.
I feel your pain though. My battery went from 100% to 56% in 5H 20M of idle time and 40M of texting / light surfing usage.
Mobile data was off for the 5 hours and 20 minutes, too. >.>
My phone does all that too. Including the upper part getting hot. I would like to know more about this too.
What's your brightness set at?
Sent from my Galaxy Nexus using Tapatalk 2
Mines about 60%
The CPU is in the top right hand corner, mine has hit 60°C before, still fine.
Having your screen on and at a high brightness will absolutely murder your battery and will help raise the temperature.
Screen will always be the highest drain as it is big.
Lower brightness to save battery and delete that damn Facebook app, it stops your phone going into deep sleep which drains your battery.
As for the yellow tint, flash a custom kernel and modify the colours.
My whites are perfect, not a sign of yellow.
My brightness was set to auto, but I predominately work/play in dark rooms, when I wrote the post yesterday over a period of a couple minutes it was in a completely black room.
This is all in relation to the Thunderbolt, though. The screen uses more battery, but I thought AMOLEDs are very efficient (black wallpaper, yay minimalism!). I'm getting about the battery life as my Thunderbolt did with its stock battery, but considering it was the first LTE phone in the US I would think it would be a more inefficient and cumbersome radio chip. It doesn't get nearly as hot as the Galaxy Nexus did, which is why I am so alarmed.
I don't want to have a phone that I can only use the screen for an hour and some change, and while I don't expect to use it solidly for eight hours, I did expect it to last at least as long as the Thunderbolt did. Is there a larger extended battery than the one sold by Verizon that adds very little bulk? I may try investing in one.
afinita said:
My brightness was set to auto, but I predominately work/play in dark rooms, when I wrote the post yesterday over a period of a couple minutes it was in a completely black room.
This is all in relation to the Thunderbolt, though. The screen uses more battery, but I thought AMOLEDs are very efficient (black wallpaper, yay minimalism!). I'm getting about the battery life as my Thunderbolt did with its stock battery, but considering it was the first LTE phone in the US I would think it would be a more inefficient and cumbersome radio chip. It doesn't get nearly as hot as the Galaxy Nexus did, which is why I am so alarmed.
I don't want to have a phone that I can only use the screen for an hour and some change, and while I don't expect to use it solidly for eight hours, I did expect it to last at least as long as the Thunderbolt did. Is there a larger extended battery than the one sold by Verizon that adds very little bulk? I may try investing in one.
Click to expand...
Click to collapse
This. I also had a thunderbolt. I expected this Nexus to out perform it in the battery field but no way. My thunderbolt with stock battery would last from 6am to 6pm which was fine for me. Id just start charging when I got home at 3. This thing when I get home its at like 3% and these past 3 days Iv had the nexus off half the day to save battery while I took AP Tests.
This phone is perfect, except for the battery. As for brightness anything under 60% gives me that yellow tint. Im using the Apex rom right now. I dont see any custom color settings. What rom do you guys use?
afinita said:
I'm coming from a thunderbolt with an extended battery. I'm used to crappy battery life, and indeed I lose about a percent an hour playing music on my galaxy nexus with is way better than my thunderbolt.
The issue comes that when I have the screen on I lose about 1-2% a minute, even if I'm just reading an ebook. Calling is fine, DOWNLOADING/STREAMING is fine, but the screen on just kills the battery.
It also gets very, very hot on the upper portion of the screen, but doesn't if I'm downloading something with the screen off.
My question is, is this normal?
As well, the screen has a yellowish tint when looking at it directly, but takes a blue tint at a very slight angle (annoying) is THIS normal?
I want to know how much arguing and yelling I'm going to have to do when I try to exchange this phone.
Writing this took me from 22% to 13% D=
Click to expand...
Click to collapse
Download from toolbox lite and use it to disable some apps from loading at startup that you know you don't need. This got rid of the issue for me. Installing Franco kernel further helped my battery. I am on stock rom.
Sent from my Galaxy Nexus using Tapatalk 2
Hi Guys,
I have been playing Samurai Vs Zombies for some days now and I notice that when I play the game without the charger connected, the phone does get warm but not super hot.
When I connect my charger to charge while playing, for sometime there is no issue and then phones back becomes super hot and the battery indicator ,which is supposed to just give out red indicating charging, will start blinking red greed red green in that order repeatedly...
Does anyone else experience this and why is this?? What does the lights blinking mean???
Does it mean that the phone is overheated???
It means the battery has overheated and it will not charge until it cools down. This has been my top complaint, as it makes HOX unusable for car navigation, car recording or longer gaming (it will just discharge and then die)
WTF!!!!
Then how the hell will we use it for anything while charging.... You open maps and turn on GPS that will also create a lot of heat... Car navigation is screwed up big time...
I think if this is the case the new base 2.05 will serve much better as people have reported that the phone is relatively cooler when compared to the current build..
aLcHy09 said:
WTF!!!!
Then how the hell will we use it for anything while charging.... You open maps and turn on GPS that will also create a lot of heat... Car navigation is screwed up big time...
I think if this is the case the new base 2.05 will serve much better as people have reported that the phone is relatively cooler when compared to the current build..
Click to expand...
Click to collapse
actually there is a precoution for this by HTC. when your battery is below %20 the CPU clock will be limited to 1000Mhz. the heat comparison between the 1Ghz and 1.5Ghz is 72C and 85C (these are the values i found out after stressing the device in a really hot enviroment for half an hour).. so when the CPU heat is lower basicly the overall heat is also lower and the device will charge itself again..
the good news is you will never run out of battery, the bad news is it will not charge above %20 and something and mosty you will be using your device at 1Ghz CPU speed.. but hopefully this can be solved with a software update (maybe limiting the current or the CPU clocks while charging)
i think the battery choice by HTC was a complete mistake (the one and only mistake the One X has).. it is not producing 5A but or anything, just an average battery but gets hot very very easily without any valid reason.. besides the unibody design is keeping the heat inside of the device.. i wish one day we will be able to replace it with an bigger capacity and more heating-proof one..
Do you keep 'Always-on screen' in the settings toggled on or off?
Turning it off doubles the wake up time and makes it a lot slower to wake up than my Moto 360. On the other hand it would save some battery. So what do you guys do?
Cheers!
I've mine since Thursday. Yesterday I tested always on, and today toggle off. We'll see. But when toggled of it's sometimes really slow.
Gesendet von meinem Nexus 5 mit Tapatalk
The purpose of the transflective display is so that the screen can keep visibility without the back light. From my experience, waking from non-ambient is slower.
Didn't even try to turn off the screen from day 1. One of my items on list for 'next smartwatch' was to be able to read time at any moment. A full black screen and make an action (button or motion) was not an option in that sense ...
Coming from the smartwatch 1 , this is a real gain to my experience. Also a good watch face in dimmed mode does help a lot. Get the promised 48 hours of battery too, probably because i dont need the backlight which definitely consumes more ....
What apb said. The selling point of this tech is the low power daylight visible ambient mode.
And about backlight- with my hacking bootloop I had to wait from 9am till 5pm to discharge with noticeable heat (most likely high CPU) and backlight at max, so, great indicator of the good battery life
I use Always on screen On and if I switch off the watch during the night I get 2 days on battery which is very good.
The transflective display is awesome and does not need backlight to be readable.
In the next AndroidWear version, we should be able to disable the automatic backlight when we move the wrist, which would enhance the autonomy a little bit more.
I leave mine on all day and by the end of the days after more than 15 hours I still hover around 50-60 percent. So the battery life is definitely good!