Database Users

Evo getting extremely hot!

Ever since I picked up the Evo, I have noticed that it is getting extremely hot after using it for a while. Usually happens during Wifi browsing or playing a game. Roughly 10-15 minutes. The kickstand gets so hot that it is almost untouchable.
Using battery monitor widget I can see that the phone temperature gets anywhere from 107 degrees Fahrenheit to 111 degrees Fahrenheit.
I have used several kernals from CFS, BFS, HAVS, NOHAVS, SBC, NONSBC and I am experiencing the same issue. Same thing with different ROMs.
It happens whether the phone is charging or not. I have noticed that it happens more quickly when charging.
Anybody know what temperature threshold the battery has before it begins to get damaged? Anybody have ideas to resolve this?
Sent from my PC36100 using Tapatalk

Ayryyn said:
Ever since I picked up the Evo, I have noticed that it is getting extremely hot after using it for a while. Usually happens during Wifi browsing or playing a game. Roughly 10-15 minutes. The kickstand gets so hot that it is almost untouchable.
Using battery monitor widget I can see that the phone temperature gets anywhere from 107 degrees Fahrenheit to 111 degrees Fahrenheit.
I have used several kernals from CFS, BFS, HAVS, NOHAVS, SBC, NONSBC and I am experiencing the same issue. Same thing with different ROMs.
It happens whether the phone is charging or not. I have noticed that it happens more quickly when charging.
Anybody know what temperature threshold the battery has before it begins to get damaged? Anybody have ideas to resolve this?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
How is your battery life when the phone gets hot like that? bad, I would assume? Perhaps there is an app that is throttling your CPU 100%, causing the phone to overheat. Does this happen after a completely fresh install, after a full wipe? Have you tried a fresh install without adding any apps back, just to test and see if you get the same results? I'm not sure what the actual temperature is, but the phone has overheat protection. Once it gets to a certain temp, the led starts flashing orange and green. I've had my phone get in excess of 114 F, but that's while under heavy use. 4g tethering, streaming music at the same time, while charging. Under normal use, i'm usually around 80-98 degrees, somewhere in that range, depending on what I'm doing. It only goes over a hundred for me when I tether or play a game or something. What PRI are you on currently? Some phones don't like the newest 1.90 PRI, and dont run well with it (my phone being one of them). Using the 1.77pri works much better on my device.
I would try using Spare Parts, or OS Monitor, or maybe Watchdog, to try to see if anything is running away with your CPU.

Anything over 120 degrees is too hot, under that and you *should* be ok. A friend of mine has a new white one that is doing the same thing and the people at the sprint store told him the wifi and having the radios on will cause it.

hot HTC Evo
Mine seems to pick up a lot heat from receiving emails. Started about 6 months into the use of my new phone. Battery starting acted up as well. It does heat up when playing Pandora & Sirius, but it will heat up without radio use. Mostly just from updates and large emails. Very, very disappointing.

Maybe an defective motherboard ?
Sent from my X10i using XDA Premium App

Yeah, as someone said a while ago, check to see if there is an app keeping your CPU at 100. There was a gps driver for aosp roms a while ago that caused CPU spiking. Happened to me and while it was spiked my phone was dangerously hot. Flashed a different driver and was back to norm temps. Good luck.

Dungeon Defenders battery drain

Hi
I just wanted to let you know that Dungeon Defenders: First Wave eats your Battery for breakfast. It drains the Battery even if you are charging at the same time! Plus it gets VERY hot
Is this normal?

punshkin said:
Hi
I just wanted to let you know that Dungeon Defenders: First Wave eats your Battery for breakfast. It drains the Battery even if you are charging at the same time! Plus it gets VERY hot
Is this normal?
Click to expand...
Click to collapse
i've heard other people complaining about this. its probably the game just not being optimized well enough for the SGS2.
you can fix the charging and overheating issue by underclocking/undervolting your phone using SetCPU or Tegrak, although i wouldn't recommend messing around with these if you have no experience doing so.

yeah i think underclocking is a good idea as long as it is not fixed. Other phones can run it (like the G2) with 700MHz singlecore so i think 700MHz Dualcore should do it...
i need root now. I thought i`d better wait a month or so to see if there are Hardware defects so i can still return it but warranty sucks anyways^^
maybe someone who is on an AOSP / Cyanogen Rom can tell me, if the drain is that high on those ROMs?

punshkin said:
yeah i think underclocking is a good idea as long as it is not fixed. Other phones can run it (like the G2) with 700MHz singlecore so i think 700MHz Dualcore should do it...
i need root now. I thought i`d better wait a month or so to see if there are Hardware defects so i can still return it but warranty sucks anyways^^
maybe someone who is on an AOSP / Cyanogen Rom can tell me, if the drain is that high on those ROMs?
Click to expand...
Click to collapse
Dungeon Defenders and other games alike do have serious problems running on galaxy s2 and that includes the average fps and the overheating issue.

poofish said:
i've heard other people complaining about this. its probably the game just not being optimized well enough for the SGS2.
you can fix the charging and overheating issue by underclocking/undervolting your phone using SetCPU or Tegrak, although i wouldn't recommend messing around with these if you have no experience doing so.
Click to expand...
Click to collapse
We shouldn't need to under clock just to play a game. My battery was on ~55% today and I played words with Friends for about 35 - 40 minutes, this shouldn't be a CPU intensive game, yet it drained my battery from 55% to about 8% and the phone got very hot. I love the SG2 but I think this is a massive problem. Does everyone else get this rate of battery drain?

gruff83 said:
We shouldn't need to under clock just to play a game. My battery was on ~55% today and I played words with Friends for about 35 - 40 minutes, this shouldn't be a CPU intensive game, yet it drained my battery from 55% to about 8% and the phone got very hot. I love the SG2 but I think this is a massive problem. Does everyone else get this rate of battery drain?
Click to expand...
Click to collapse
I have tested 3 of them and all 3 have the same problem regarding the phone getting extremely hot in certain apps.

Deadly Issue ;( !! (UPDATE: occurs with the stock kernel)

Hello everyone...
I have 2 issues with my Transformer
the first one is that whenever i leave my Transformer for couple hours it shuts down !! doesn't occur when charging but it does when it's not.. even when the battery is around 80% !! i had this problem with ALL kernels except the stock kernel which i don't wanna use !! also had this problem for around 2 months...
the second one happened today when i left my Transformer "Charged" at 100%.. and after couple of hours i found it shut down but when i powered it on again i found the battery 27% !!
i went to the battery stats and found that battery was decreasing slowly and there was a gap (which means that it turned off) and after the gap it shows the battery low !! it happened within 6 hours !!
Please help me if you can... !! I'm using Revolver ROM 3.9.5 and "Blades Kernel 3" that comes in the Revolver Parts...
UPDATE : The problem occurs with the stock kernel !!

This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?

The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.

Cernunnoz said:
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
Click to expand...
Click to collapse
I never heard of this app... Just like i said it doesn't happen with the stock kernel !!
But the reason I'm using other kernels is because i wanna Overclock !!

a.mcdear said:
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Click to expand...
Click to collapse
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !

sounds like a silly question but i have seen it alot. Are you charging through a computer(USB) or wall?

It could be related to setCPU and the according profiles. Just recently I saw that my profiles were messed up after updating ROM and kernel. Might be worth a shot.

Reinstall stock kernel Issue #1 fixed.
Issue 2 sounds like charger shut off and left TF on not charging.

You've pretty much explained to yourself why the thing is shutting down.. It works fine on the stock kernel but not one that is letting you overclock.. Sounds to me like you are either overclocking more than it can handle or undervolting to much or both.
I can almost bet that its not shutting down completely and its just going into a state that the screen is off but the OS is hung up, so its not responding to you turning the screen on.. This would explain why the battery seems to be dieing when its sitting idle.
Not sure about it dieing while its plugged in other than maybe a fluke.

I don't wanna use the stock kernel.. it's really slow !!
and i over clock to 1.4 ghz only since i can't overclock more than that because it restarts itself endlessly if i overclocked more than 1.4 ghz !! i undervolted about -25 or -50.. not much !!
Yes i charge it on a wall or anything but NOT on my computer...
How can i change profiles in setcpu ??

xMini said:
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
Click to expand...
Click to collapse
No no you misunderstood! DONT let the battery hit 0.

First, you need to use more exclamation points !!!!
sounds like you are suffering from deep sleep issues. What rom are you running? also, have you tried running a custom kernel and not overclock it? You have several variables that can be influencing your issues, start isolating what may be causing your problems. the kernel seems the must likely of culprits, I would clear the overclock and install setcpu and run it for a but and see if you can replicate your issue.
Sent from my GT-I9000 using XDA App

Just try the non stock kernel, oc it but dont uv it, not all devices can handle uv, even if it is only a little bit. Even take it back too 1000mhz and try to increase the uv and oc by little bits at a time to see exactly what your transformer can handle. I think its the uv thats causing the problems. Experiment a bit and youll find the sweet spot.

I'm using Revolver ROM and i mentioned that...
I've never undervolted till yestersay.. maybe it caused the second problem
I set the clock speed at 1ghz and i'm waiting to see if anything changes..

Yeah... the problem still occurs even after setting the clock speed at 1ghz and default voltage !! using clemsyn kernel ver 22...

Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk

colonel187 said:
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I'm guessing my device is bad and it's Asus' problem ! i tried setting the clock speed at normal 1Ghz but the problem still occurs !! the reason i overclock is that because with the stock kernel i get slower web browsing and slower flash playback and slower overall performance!! however I'm back on the stock kernel to check out if the problem is gone or not...
I doubted my device couple months ago... because I've seen everyone overclock their devices at 1.6 GHz Without any issues !! but when i try to overclock a little bit more than 1.4 GHz it restarts itself endlessly !!

Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App

ropaisoft said:
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What do you exactly mean by "for now" ??
and how can i even send it to ASUS ??! i don't live in the USA

xMini said:
I'm guessing my device is bad and it's Asus' problem !!!
Click to expand...
Click to collapse
You stated in an earlier post that the problem does not show up in the stock ASUS setup, but only with a custom ROM and Kernel. How does that make it ASUS' problem. If you buy a car that says it runs on 87 octane fuel and you put 100% nitro methane in the tank and it blows up it is not the manufacturers fault.

[Q] Freezing issues

Hi i have flashed many nand roms to my hd2 the end result is always the same. phone works fine until i try to play games anywhere between 30s to 10 min and the phone freezes up and is unresponsive. only way to fix is to remove battery. any ideas on what this is why it happens and how to fix it.

what is your ROM? what's your magldr version? what is your HTC HD2 type EU or TMOUS? What is the name of your games? i need more information sir..

psypix said:
Hi i have flashed many nand roms to my hd2 the end result is always the same. phone works fine until i try to play games anywhere between 30s to 10 min and the phone freezes up and is unresponsive. only way to fix is to remove battery. any ideas on what this is why it happens and how to fix it.
Click to expand...
Click to collapse
I'd hazard a guess at it being an overheating problem. Do you overclock on the ROMs you use? Does the phone get extremely hot? If yes to these, try not overclocking and see if it works.

magldr version is 1.13 and it a tmous hd2 running nexus h2 ics 4.0.4 cm9 hwa v1.2 by tytung. not overclocking running at the standard max of 998Mhz min somewhere around 200. the only option i have used is in the performance settings under memory management i ticked the kenel samepage merging which seems to have reduced the amout of freezing i am experiencing. tried playing the game called drag racing think is by creative mobile. phone on its own works great but even playing angry birds anywhere between 5 to 15min it freezes. noticed yesterday my battery was low so the charge light was flashing and when the screen frooze the light still continued to blink but the phone was totally unresponsive. Any ideas

Nigeldg said:
I'd hazard a guess at it being an overheating problem. Do you overclock on the ROMs you use? Does the phone get extremely hot? If yes to these, try not overclocking and see if it works.
Click to expand...
Click to collapse
not overclocking running at the standard max of 998Mhz min somewhere around 200
Click to expand...
Click to collapse
I have similar problem. But not so often. He is not overclocking, neither do I.
I also use zRam 26%.
This often happens when the phone is under load, so I think that maybe this is due to lack of memory. The phone heats up when the screen freezes.
Any tips?

OK, this might sound stupid but try putting the phone in the fridge for a while to cool it down, then play. Obviously don't do it for too long, it is after all a phone, but I read somewhere that this had helped someone with overheating. I doubt it is a RAM issue cos that wouldn't cause a freeze, it would probably result in the launcher being killed to free up RAM.
Sent from my NexusHD2 using XDA

not sure putting it in the fridge every time want to play will be quite the fix i am looking for. Might prove the theory that the phone is overheating but then there must be a setting somewhere that can be envoked to get this to stop happening

psypix said:
not sure putting it in the fridge every time want to play will be quite the fix i am looking for. Might prove the theory that the phone is overheating but then there must be a setting somewhere that can be envoked to get this to stop happening
Click to expand...
Click to collapse
Yeah I know it isn't a practical solution, I just meant it to test my overheating theory. Perhaps there is a fix, but to be honest if you aren't OCing then I really don't know why it should be heating up so much. Sure, mine gets warm but even when I've played for around an hour on Contract Killer: Zombies (fairly graphically intense and a very fun game) it doesn't shut down or anything. There IS a hardware fix but it's quite dangerous and requires a lot of expertise and the right equipment, neither of which I have Should you wish to try it, just make sure you're very careful

Reason for bad Battery life, sticky 1026MHz?!

So since I had my nexus 4, I had to complain about its terrible battery life.
I would never get more than 3h of screen on time, despite my best efforts in conserving battery. Even with the phone in flight mode and on Wifi, I could not cross 3h give or take a few minutes. I even tried disabling location, google now, sync and everything else.
It was deep-sleeping nice, while the screen was off, standby time was awesome for me. If I turned it on though, it started to burn through battery insanely quick. So I started monitoring the frequency states with battery spy, and noticed that as if there was a little load, it spiked to 1026MHz and then stayed there for about three seconds every time before falling back to 386 MHz. So I tried setting the max cpufreq to 916Mhz with CPU tuner, and was astonished to find out, that immediately after the load was done, it went back to the lowest frequency. Like it should be, not hanging for multiple seconds on the high step.
Also, If I start CPU tuner, the min freq is always shown as 1026MHz. So I changed min to 386 and max to 916. Afterwards, this stays until I swipe cpu tuner away from the recent apps list. If I start it again, the settings revert. Strange...
With my cpu limited to 916MHz, I get about 5h and 50 min of screen on time without any other measures. Location on, Wifi on, Google now and sync all active. If I just go one step higher and set my max frequency to 1026, the old behavior starts again, and screen time drops to 3h because it seems to be stuck on that freq. Therefore I would like everybody who also has bad screen time to try that out and report back.
I don't really understand why it would take so long to drop back from the 1GHz step, and drop back immediately from the 0,9GHz step?
Of course, this is with normal surfing via chrome, or using normal apps that are not that much CPU intensive. Also, you hardly notice the performance limitation without playing games. There probably is an easy way to fix this?
Feedback would be appreciated. Maybe I see this wrong...
Thanks
tl;dr : if screen on, for me only 1026mhz is used, if max freq is set to anything lower, the phone spends most of the time at the lowest step 386mhz, greatly increasing screen time for me.

Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app

NoLunchBox_ said:
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Maybe, but I really first wanted to examine out of the box behavior

This is caused by qualcoms Mpdecision which ramps up the cpu to 1ghz on screen on and touches. All in the name of speed. It's basically a hot plugging technique such that smoothness is guaranteed under loaded gui transitions and scrolling. Before this you would have to wait for the cpu to be loaded for it to ramp up speed. Now the OS can demand speed.
You can see in Franco kernel he replaced Mpdecision with an open source alternative and swapped the lowest cpu speed to 368mhz. Then added a load step of 768mhz (for 60% loads). This actually added a bit of lag but should be better in the battery department. Some more tweaking to be done though.
Qualcoms thermald is what is causing thermal throttling.
Edit: this could be wrong. But I think I'm in the general area of what's going on...
Sent from my Nexus 4 using xda premium

This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,

ArRaY92 said:
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
Click to expand...
Click to collapse
You don't have to buy an app, everything can be set through scripts. The app just automates the process, allows you to back up kernels, download the latest nightly and milestone (when one becomes available). It's really worth the investment, plus you're helping out a great Dev who has shared his awesome work with us for a long time.
Sent from my Nexus 4 using Tapatalk 2

I like my phone to sleep. I bumped it down to 384!
No need to keep it @ the 1.026, it will pretty much kill battery! Makes no sense to me.
Sent from my Nexus 4 using Tapatalk 2

You can set the max to 384 mhz.. and still everything is smooth

Can I use SetCPU or is that app defunt now? And to change my CPU speeds can that be done on a phone that's simply rooted or do I need a custom kernel?
EDIT: I downloaded CPU tuner, but I'm not sure if it's working or not. Does it work w/ stock kernel or no?

Faux's Intellidemand fixes pretty much what you're describing. Since mpdecision is not used instead of fauxs alternative.
Sent from my Nexus 4

What is max frequency by default?

Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.

biffsmash said:
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
Click to expand...
Click to collapse
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.

ksc6000 said:
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
Click to expand...
Click to collapse
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.

[hfm] said:
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
Click to expand...
Click to collapse
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.

ArRaY92 said:
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
Click to expand...
Click to collapse
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.

[hfm] said:
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
Click to expand...
Click to collapse
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.

My min CPU speed is 1 GHz and in still getting 4 hours on screen time though. I don't think setting my min at 384 MHz even made much difference in my battery, will try it again soon.
Sent from my Nexus 4 using xda premium

droyd4life said:
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
Click to expand...
Click to collapse
Stock never rooted bootloader still locked.

If you are getting bad battery... simply flash a custom kernel. You get to keep your stock ROM or whatever but you will get substantial benefits. I prefer Trinity Kernel. Only the second or third update on this kernel and now the phone has made huge gains in battery life. Like hfm, I good on screen time... usually 5-5.5. I have auto brightness on, mobile on 100% of the time, and all Google services synced including books, gmail, currents, google now, etc etc. I have locations on, gps on... everything. Sometimes I turn off NFC because I rarely am somewhere where I can use those cool RFID card scanners. What sucks battery is probably a problem in Android 4.2. The phone does not sleep as much as it should. Go ahead and turn all your sync stuff off and keep the screen on static and let the battery die at stock clock speeds. Probably will get at least 5 hours with auto-brightness on. My phone probably sleeps 60% of the time now according to CPU spy when it sits idle in my car for my 8-10 hour work day. I usually get to the car with a bunch of emails, a text or two waiting for me, and the phone has only been asleep the aforementioned 60% and around 90-91% battery life. On a new phone, starting from full charge, this should be at least 95%. My N10 that doesn't have mobile data, only loses about 1% overnight. Apples to oranges but still. I'm convinced that stock voltages on this device are too high, and that Qualcomm did not give Google the latest drivers... maybe because it's not releasable to AOSP as of yet. I really don't know, but it's gotta be something buggy. This SoC is capable of doing better... and it does in the Optimus G and even with sense, 1080p screen, and a 100mah smaller battery the HTC Droid DNA/Butterfly gets 3.5-4 hours stock screen time. None of the other phones using the S4 Pro are running 4.2. I'm hoping either Qualcomm pulls a Samsung and releases some updated drivers/firmware that Google can incorporate or that Google fixes whatever bugs they may have not worked out. In the next calendar year other phones will be out that use the S4 Pro and 4.2 and I doubt Qualcomm wants to lose the luster it earned with the regular S4 Kraits performance/efficiency. When 4.2 comes to other devices we will probably know whether or not Google is to blame for this or that the Nexus 4 is just a poor performer.