Battery Life Help - EVO 4G Q&A, Help & Troubleshooting

I really don't understand what is going on with my batter life. I can't get it anywhere near what people are reporting with the same configurations. I just changed roms and kernels again to Fresh and ffolkes undervolted kernel. I hope this fixes my problems because im starting to get fed up with sending 5 text messages and losing 20% in 3 hours. My setcpu has only one profile which is screen off 128 min and 245 max. Someone please help me I really can't put up with the horrible battery life I am getting.

Search around for info on powertop. If you're only running the default apps and aren't syncing a lot of stuff then it could be your battery itself. This isn't something that anybody can remotely troubleshoot for you without a lot of hassle.
Also depending, you may want the max higher on screen off. To put it simply, there is overhead with the cpu not being asleep in addition to crunching numbers. Slower processing for simple tasks may cost you more due to the CPU being on longer. Lots of variables.
Sent from my PC36100 using XDA App

Related

[Q] Paradox with underclock & battery savings, does it actually hurt? SetCPU, etc.

[Q] Paradox with underclock & battery savings, does it actually hurt? SetCPU, etc.
In theory, using SetCPU or other underclocking app to reduce CPU clock should reduce the power draw from the CPU, therefore reducing battery consumption.
However, underclocking does not reduce the amount of work that needs to be done. That is to say, whatever app or kernel processing that needs to be done will still be done. When UC'ed, they will be done at a slower pace, therefore taking longer time. In some cases, the UI becomes sluggish, requiring more user interaction time as well.
If, at 1Ghz, a process takes 10 seconds to complete and requires 10mA per second. This task should consume 100mA. By underclocking to 500mHz, perhaps the CPU takes only 6mA, but the task will require 20 seconds to complete. Now the task actually takes 120mA (plus the longer screen on time).
Is my theory sound?
Also, does the constant scaling itself consume power?
As far as I know, Froyo is supposed to scale the CPU anyway. So why underclock? Does it actually work or does it hurt the battery life?
Input please!
Thanks.
Edit: I know the function of CPU speed vs. efficiency vs. battery drain is never linear, and each situation has a different break-even point, but I'm curious the general application of underclocking within the Android environement and its effect on battery life, and more specifically, the Evo.
i'm a regular dude with a phone, but im educated...that being said im sure your aware of the diminishing marginal utitlity law. For example if me and you can mow a lawn in 2 hours, and we got one more guy, we can do it in in less than two...Bu you eventually reach a breakoff point where it is hurting you and those extra guy(s) are not needed and acutally slow down the process or are just a waste. Same thing here, although i am not sure of the numbers, im positive there is a sweet spot for underclock and if you go too low it actually is a waste or hurts battery life. It also could be in the middle meaning, im going to make up numbers. 1ghz uses 100 Mah in 10 seconds. 800 mhz used 50 mah. 900 uses 60 mah. Now, the difference ratio of battery usuage and spees would lean you towards using 900 because if you relate this to sales on products or even anything, for lack of better words this setting is the best abng for your buck...my 2 cents
http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNFlNlZCm-gnvD1PzEsDezCIPeA8jQ
Sent from my PC36100 using Tapatalk
Interesting stuff... Take a look at this thread:
[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock
The data seem to suggest that underclocking an Evo at idle yields real results. I would think that this can only work if there is not a lot of background/idle tasks going on?
snovvman said:
Interesting stuff... Take a look at this thread:
[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock
The data seem to suggest that underclocking an Evo at idle yields real results. I would think that this can only work if there is not a lot of background/idle tasks going on?
Click to expand...
Click to collapse
both pics depicts very different device usages. not a fair comparison imo.
quocamole said:
both pics depicts very different device usages. not a fair comparison imo.
Click to expand...
Click to collapse
Yea I went through and read the whole thread. I'm now even less convinced that SetCPU provides any tangible battery benefits at all.
snovvman said:
Yea I went through and read the whole thread. I'm now even less convinced that SetCPU provides any tangible battery benefits at all.
Click to expand...
Click to collapse
Do you think i am right on any part of which i said or am i talking out of my arse lol
A microprocessor does not live by its clock alone. lol
It can cycle through a huge math operation, which is loaded into its registers lickity split with a fast clock. It will have to wait while the memory/code of the programs it runs are loaded either into its cache memory or into execution space. So in calculating theoretical energy use, you got to figure the bus speed, as well as the type of operations the processor is doing.
Golly, ( pronounced like a resident of Mayberry) the bus is key on loading programs to be run. What's the bus clock triggered off? That's the key. You don't want the bus to slow while slowing the cpu. If you can cycle the processor while it prefetches then you've got optimal use, providing it isn't thrashing.
Google cpu wait states for bus synchronization
This is basically the reason HAVS is supposed to be better than static scaling and underclocking. With HAVS, voltage is based on workload as well as clock speed, so you should get the benefits of running fast/idling more often combined with the benefits of using as low of a voltage as possible. As long as you don't have something pegging the CPU at 100% all the time in the background, it should, in theory, work better.
In practice, I haven't seen all that much of a difference.
iitreatedii said:
i'm a regular dude with a phone, but im educated...that being said im sure your aware of the diminishing marginal utitlity law. For example if me and you can mow a lawn in 2 hours, and we got one more guy, we can do it in in less than two...Bu you eventually reach a breakoff point where it is hurting you and those extra guy(s) are not needed and acutally slow down the process or are just a waste. Same thing here, although i am not sure of the numbers, im positive there is a sweet spot for underclock and if you go too low it actually is a waste or hurts battery life. It also could be in the middle meaning, im going to make up numbers. 1ghz uses 100 Mah in 10 seconds. 800 mhz used 50 mah. 900 uses 60 mah. Now, the difference ratio of battery usuage and spees would lean you towards using 900 because if you relate this to sales on products or even anything, for lack of better words this setting is the best abng for your buck...my 2 cents
Click to expand...
Click to collapse
iitreatedii said:
Do you think i am right on any part of which i said or am i talking out of my arse lol
Click to expand...
Click to collapse
What you wrote makes sense and the concept is sound. I just wish we knew what that sweet spot is, although I think it changes constantly based on load, code, and operational requirements.
With the two posts above, it would seem like phone manufactures would do everything they can to optimize efficiency. Having SetCPU loaded for 24 hours, I too, can say that I have not seen a huge difference...
Noxious Ninja said:
This is basically the reason HAVS is supposed to be better than static scaling and underclocking. With HAVS, voltage is based on workload as well as clock speed, so you should get the benefits of running fast/idling more often combined with the benefits of using as low of a voltage as possible. As long as you don't have something pegging the CPU at 100% all the time in the background, it should, in theory, work better.
Click to expand...
Click to collapse
Does the stock HTC kernel, 2.6.32 "#11" have/use HAVS?

[Q] setvsel cpu damage

hey guys, just wondering will using a lower vsel damage my cpu and/or battery?
i have previously beein using milestone overclock on 1ghz and 60 vsel and am adding setvsel into the mix, also any ideas on starter settings? thanks
also could someone just give me a heads up on what vsel actually IS
I don't believe there are any studies that show effects of long term use of lowering the voltage, which is what you are doing with vsel in order to save battery juice...or you could increase the voltage but that defeats the purpose and also heats up the battery which leads to shorter life span. Many use it without reporting any damage to battery or cpu, I believe it's safe (however, if you are overheating you might fry the battery or cpu, so you'll need to moniter and play with settings to get the desired effect without any overheating issues).
With regards to setvsel, there are reported issues from users with different roms...from what I've read (and you can do your own research to see if this is what you are seeing...this is the conclusion that I've come to by reading a lot of threads), it is better to use milestone to overclock and setcpu to lower the vsel.
With that being said, I've used them all and like setvsel so keep going back to it...but I've been having some issues lately so I've removed setvsel to see if that is what is causing some problems (too early to tell).
Oh, and as for settings...pop on the overclocking/undervolting thread in the development section to see a lot of different settings and remember that what works for one user might not work for you...you'll have to experiment a bit to find your ideal setting.
oh okay i think i might go back to my old settings with milestone overclock and setcpu and just lower the vsel! i was under the impression for some reason that lowering the vsel would heat the battery. Thanks!
I'm no expert to be honest, I'm more of a research kinda person. From what I've researched, undervolting can help keep temps down, and may particularly help when you overclock (as overclocking is stressing the cpu to go beyond it's normal operating design hence it may heat up...supplying it with less power, or voltage, is what helps keep the temps down.
Of course, this is given you find the optimal setting for your phone, and as it seems from reading through these forums, many users have experienced completely different results using the same settings (i.e., one user will have a stable setting without any problems while another user on the same rom using the same settings will have crashes and/or issues like overheating). Doesn't seem right, but it is what it is
yeah ive read through most of that stuff too, i went down to 1ghz at 51 vsel, seeming stable, but i decided to go with 54 anyway
1.1 GHz @ Stock vsel for over a month without any issues...I hope it lasts.
Sent from my MB525 using XDA App
Hi,
I've also read a lot regarding the underclocking 'dangers' but couldn't find anything to prove that there is such an issue. I think that it is an urban myth spread everywhere by people asking if there is a danger with low vsel [but that are never getting a positive answer on it].
The only thing I found using setvSel is that I had to first install Milestone Overclock and load its module prior to start setvsel. There is a way around it, but requires you to copy files in the system folders and change their permissions. I find that my way is much easier.
As far as over-heating goes, it's an overclocking thing; not underclocking.
My Defy is set at 900Mhz and really, I don't see the point of going much higher: everything runs smooth and lag free already.
vsel: 21/300; 32/600; 43/900 - 90% up_threshold
Been like that for about a month now and never experienced any problem at all.
The underclocking is great for saving battery; no exact numbers to give here but it feels like my battery now last 2 times longer. I can easily get 4 days between charges with low/moderate usage and would get to 6+ days "IF" I could stay away from games and having the screen ON for long sessions of browsing/video watching.
I tried SetCpu before but I didn't like the interface; the simplicity of SetvSel is really nice.
i use setcpu for scaling and profiles, and run 18/300, 36/600, 50/1000 stable and smooth as
Undervolting is not a bad thing at all. It means less Watts consumed for running (Watts = Voltage x Amperage), less of your battery consumed.
Ussually companies test a large batch of components and how they react on different voltages and freqvencies, and then they decide for a voltage that works with all components and that is safe for all cases. Eg. when they have different CPU speeds and thus different options for CPU's this is one way to decide which one work at 3GHz and which one at 2.7 GHz (the other one is demand for components).
Phisically you will not have any problems and you can't damage your phone by undervolting, so no problem here, only possible software problems if you go too low.
Advantages :
+ Lower processor temperature
+ Lower phone temperature
+ Longer battery time
+ Longer components life
Disadvantages
- Stability issues (freeze, artefacts, slowness)
maxi2mc said:
Disadvantages
- Stability issues (freeze, artefacts, slowness)
Click to expand...
Click to collapse
You know, I was recording a video and when playing back noticed that there were squiggly lines that went through the video a couple of times (in a two minute clip). This was the first time I saw this...and have recently lowered vsel by 2 on vsel3...could that be the artifacts that you are mentioning?
I just figured it perhaps I was too bouncy with the phone while recording making it glitch...but now that I see this post I'm thinking maybe I undervolted too much...what do you think?
My settings: 54/1000 44/700 28/300
I know what people mean by same settings don't work for every phone even if it's the exact same model. My Defy won't underclock as much as others. I'm using SetVesel, and I've been able to drop 5 points from each, and that's about it before it reboots itself. I only tested undervolting, but I mainly overclock to get as much speed as I can, and give it enough juice to run super fast. I'm current running [email protected], [email protected], [email protected] Threshold at 75%. The highest the temp ever got was 112F, and that was after playing a game for about an hour. Usually it stays below 90F for normal use. I get around 17-20 hours out of it with screen on time at about 3 hours @ 50% brightness. I've been running these settings about a month, and have not had any issues.
If you put something like 100vsel will the phone accept and then burn? Is there any protection? Does anyone know what's the highest acceptable vsel?
Just for curiosity...
im pretty sure 80 is the highest you should EVER use and that'll significantly increase the chances of your phone burning out. @bobbyphoenix you should be able to lower your vsels a fair bit or your really unlucky! i run a lower vsel for 1ghz than u do for 700mhz smooth and stable
stewi21 said:
im pretty sure 80 is the highest you should EVER use and that'll significantly increase the chances of your phone burning out. @bobbyphoenix you should be able to lower your vsels a fair bit or your really unlucky! i run a lower vsel for 1ghz than u do for 700mhz smooth and stable
Click to expand...
Click to collapse
CM7, rather non-technical person here. I seem to have a very happy phone at setvsel settings of [email protected], [email protected], [email protected], 86%. Been running this for the month or so since I rooted and the phone feels like it was made for this config. I've never seen the temp above ~32c. My 2¢.

setcpu uv settings

i was hoping somebody had optimal setcpu uv settings. i'm trying to squeeze every last drop from my battery but i really don't know how to set it up. any help would be great.
Read this.
I'm using these settings and my phone lasts for 5 days (no gaming ofc. )
thanks. trying those settings now
Theres no such thing as optimal settings...everyones phone has different tolerances...
Go down in steps of 25 and stress test is the best way...Trail and error.
This belongs in Q&A ...not here
Sent from my GT-I9100 using XDA App
yea i used the settings in the link as a starting point and managed to lower them a little. is it just me or does that 4 days on a charge seem a little too good to be true? the best i can get seems to be around 1.5% of a 1650mah battery per hour in standby. about as good as my hd2 running gbx 12 got. the phone does go into deep sleep (76% since reboot) but i don't get anywhere near the tiny battery drain some do. the setcpu uc and uv adjustments did help some but not as much as i had hoped for, guess i'm just gonna have to get a bigger battery.
i put it here 'cause it was a setcpu question. i know its turning into something else. sorry 'bout that.
Thats because you have wakelocks. In deep sleep, I get a maximum of 5% battery usage over a 10-12h period. Check if some apps are keeping your phone from going into deep sleep.
yea i have quite a few wakelocks but they only are "active?" for a few seconds. k-9 was the biggest culprit but a bunch were system processes. i set k-9 now to not poll but i don't know what do do for the rest.
how do you know if the wakelock is a partial or is locked? do the partial ones keep the phone from sleeping all the time or only when the app/service is active? is there any way to suspend/overide partial wakelocks on a per case basis so email and such can update but still blocking some? i've done a little reading but this seems more complicated than it should be.

[Q] UV, UC, other Kernel options.

Android 4.2.1
CyanogenMod 10.1 Snapshot M1 (21/1/13)
Franco Kernel R364
I'm trying to maximize my battery time.
(Power mode BeastlyBattery 192MHz~1036MHz, Governor: Lazy, IO Scheduler: deadline, Screen of Max Frew: 384MHz)
I want to UV my CPU (and maybe IVA and GPU also, does it helps too?) to save some battery.
Should I just decrease the voltage a bit, use stability test app and keep going till there will be errors,
or I can just decrease like someone else on the web and then keep going..?
Can it do something to the device? (because Its just undervoltage..)
For how long I need to run the stability test?
I saw this topic:
http://forum.xda-developers.com/showthread.php?t=1599025
and he says:
"1. It has been tested that the 700Mhz frequency is prefereable over the 300Mhz one, due to the drops on frequency signal of the phone."
Anyone tested this?
Does UV degrades preformance?
What is SmartFlex?
Anything else I need to know about that?
Im gonna make this one quick, so my apologies if I don't address your questions directly.
Prior to my Galaxy Nexus, I had a T-Mobile SGSII. I too had the belief that undervolting/clocking would improve my battery life substantially. It seemed to work but then I was only getting the results that I wanted to get, and thats because I went to extremes to lowering my screen brightness to minimum and using my phone a fraction of what I used to.
With the help of others and trial and error, my major conclusion is that undervolting/clocking, though normal headset use will not improve your battery life by a landslide. Android is so well optimized to save you as much battery as it can. Sure there are things here in there that interrupt that optimization such as bugs or kernel issues but that something even undervolting/clocking will not be able to solve.
If you do go into undervolting/clocking your device, please keep in mind that the most you will probably get out of it is maybe 45 minutes to 1hr extension, but thats not display time.
What you can do to improve your battery life is turn off whatever sync services you don't use, lower your screen brightness ( the display is the major battery hog in the GN and SAMOLED devices), use dark wallpapers and dark themes if apps support it, use wifi, disable 3G when not in use. The radio you use can also potentially affect your battery life and signal quality.
Those are just a few suggestions, the rest is up to you.
Good luck!
P.S. Kernels also add variation to the longevity of your battery life. It's been a very long time since I touched CM10 so I'm not gonna go and defame that ROM but do try something else that possibly offers better battery life. If MODs are a MUST for you, then you will be faced with a lower battery life compared to stock based ROM's. It won't be an extreme difference but the difference will be there. If I may suggest a ROM, try this one. I can honestly say I can get up to 3-4 hours of display time on it with about a 12 hour standby.
I read a lot on the web that it does help to battery time.. :S
anyone?
You're not going to see much difference. Running the cpu at a lower clock speed just means it will take longer to complete the same operation so you'll use just as much battery.
063_XOBX said:
You're not going to see much difference. Running the cpu at a lower clock speed just means it will take longer to complete the same operation so you'll use just as much battery.
Click to expand...
Click to collapse
And undervoltage?
Different overnor?
Undervolting will have minimal effect during actual use and a governor is based on specific user needs. One might save me battery while another works better for your usage. You need to actually mess with setting instead of just asking others what they use.

Solution to reduce thermal throttling on Nexus 5X?

Is there a way to reduce it? My phone slows to the pace of a sloth far too frequently and it seems correlated with temp.
I'm assuming that's the cause because when I look at the CPUs in CPUz the last two go down to 633MHz when things are getting slow. Also seems worse with a case but could be my confirmation bias. This is particularly apparent with the camera, Maps, and when coming out of doze.
Is there a more conclusive way to figure out what is causing my Nexus 5X's occasionally brutal performance?
Sent from my Nexus 5X using Tapatalk
Well, what exactly are you doing with your phone that's causing it to throttle itself? I think with a stock kernel the phone begins to throttle and eventually shut off the Big cluster at 36 or 37 degrees Celsius (someone correct me if I'm wrong). If you flashed a custom kernel, most here have had that limit raised to 46C.
Last weekend I used my phone quite a bit for strenuous tasks including Navigation, Google Maps, lots and lots of pictures and 1080P video. The phone got noticeably warmer, but when I checked my kernel management app, the CPU temperature wasn't even close to the throttle temperature. Unless you're gaming or constantly benchmarking your phone this really shouldn't be a problem. Especially when coming out of Doze. The phone doesn't immediately enter Doze, it waits a while and there are factors that play into its decision to even enter doze in the first place (like laying on a flat surface for X amount of time). So when a phone is exiting Doze because of your input (turning the screen on) the CPU should be quite cool (maybe 22+ degrees). There's no thermal throttling there. The Big cluster shuts off when the screen is off for the sake of battery life, so maybe the lag that you're experiencing stems from the lack of the Big cluster being on for the first second or so when waking the phone back up.
I'll agree that the SD808 isn't a stellar chip; maybe even embarrassing. It's not blisteringly fast, but it certainly isn't slow. There are ways to speed up performance and improve battery life at the same time, which I'm sure you'd appreciate. Unfortunately you have not specified if you're running a custom ROM or kernel, so that's pretty much all the advice and information I can give you right now. But, if you're currently running stock, I'd highly recommend you unlock your bootloader and try out some of the custom (and more lightweight) ROMs that this community has to offer as well as some great kernels. That should make a noticeable difference right off the bat. Then you can dive into the nitty gritty details of tweaking and whatnot if you desire. Check out the links in my signature as a starting point. If you're looking for optimization and speed (like I do) then you'll be impressed.
Thanks for your reply.
I switched to ElementalX about a week ago and it may be a bit better now but it's hard to tell. I've also been using a spigen slim case, maybe that is causing heat to accumulate too.
I don't game. My usage is Maps, Facebook, Snapchat, camera, chrome, hangouts, Spotify, and textra.
I use greenify and amplify as well on xposed. Disabling xposed doesn't seem to make a difference.
Can you confirm that ElementalX throttles at 46C and stock at 36C?
I'm interested in your recommendations. When running geekbench it takes about 9 minutes for things to really slow down.
Sent from my Nexus 5X using Tapatalk
If you search the ElementalX thread you can see that the developer, Flar2, was getting very frustrated with the thermal throttling on this device (others were too, as well). You can read through the progression and, eventually, the decision to apply a "thermal fix" or raise the thermal throttling limit. The threshold is 46C now. Confirmed. The stock thermal throttle threshold is 10 degrees less than that from what I've read. I also remember reading that Franco did a fair amount of research into the throttling issue and found that the CPU was capable of going over 50C with no issues (but aren't recommended), so the limit in place now by the ElementalX kernel is a safe one that shouldn't be exceeded. He probably didn't make it any higher so he wouldn't be found liable by any users if they overheat or damage their phones.
I have no experience with xposed and everytime there's a compatibility issue, hard reboots, etc. it's always because of Xposed. So.. Yeah.
I also do not use any tweaking apps that supposedly save battery or whatever. I let the operating system take care of that. I do use the L-Speed app (again, in my signature) to disable certain things like debug logs and what not to speed things up slightly. Again, I highly recommend trying Ubermallow and Phasma Kernel as those have been my choice, after trying many others, for some time now. Also, I'd look into the interactive governor tweaks after you've settled on a ROM and kernel combination that you like. That's where you can fine tune the way the CPU governor on the phone behaves and can really make a difference in battery life and fluidity of the device.
Lastly, a case can make a difference with cooling but I've never really found it to be an issue. Maybe I'm just not hard on my phone enough.
ryanwalexander said:
Is there a way to reduce it? My phone slows to the pace of a sloth far too frequently and it seems correlated with temp.
I'm assuming that's the cause because when I look at the CPUs in CPUz the last two go down to 633MHz when things are getting slow. Also seems worse with a case but could be my confirmation bias. This is particularly apparent with the camera, Maps, and when coming out of doze.
Is there a more conclusive way to figure out what is causing my Nexus 5X's occasionally brutal performance?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
A member on the 6p forum came up with a hard mod that does this with a special thermal paste better then stock . Requires tearing apart the device though ...so its risky but his results looked promising
Sent from my Nexus 6P using XDA Free mobile app
Google just agreed to take back my device so I only have a few days to try things and make my decision on whether to keep the phone or not.
Thank you for your thoughtful responses and suggestions.
Since I started using the phone outside of the case it actually seems much better.
Regarding the extreme slowness coming out of doze, it only occurs when in doze for a long time. Presumably because the phone tries to catch up on all the sync activity that's been paused for the last 12h or so.
Sent from my Nexus 5X using Tapatalk
I think I'll try your suggestions and remove greenify, amplify, and xposed to see if things improve. I do agree that the system should be managing those things.
Sent from my Nexus 5X using Tapatalk
Yeah, give it a few days. There are many ways to combat the throttling. Got my phone to 41C today while using it out in the sun. The Big cluster is limited to 633MHz at 36C and shut off at 41CC. The 46C built into the kernel is most likely for the LITTLE cluster to start getting throttled. Check the attached pics below.
Thanks. Btw what ROM and app is that?
Sent from my Nexus 5X using Tapatalk
ryanwalexander said:
Thanks. Btw what ROM and app is that?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
ROM and Kernel are in my signature. The app for managing the kernel is Elementalx Kernel Manager and the app to add CPU usage overlays and stuff is called Trepn Profiler.
Sounds like the opposite to me, the phone might be slow because of software on the device not playing nice which causes the SoC to work over time (normal computing + rogue app computing) and can cause the device to over heat and throttle.
There's no reason the device should be slow after a period of doze. That tells me the device is having software caused slowdowns that are not related to thermal throttling.
It takes roughly 12 minutes of 100% sustained load (only synthetic benchmarks) to throttle the 2x A57 cluster, and I've never seen the 4x A53 cluster throttle under any conditions including hours of heavy gaming they stay at 1.4Ghz at all times.
bblzd said:
Sounds like the opposite to me, the phone might be slow because of software on the device not playing nice which causes the SoC to work over time (normal computing + rogue app computing) and can cause the device to over heat and throttle.
There's no reason the device should be slow after a period of doze. That tells me the device is having software caused slowdowns that are not related to thermal throttling.
It takes roughly 12 minutes of 100% sustained load (only synthetic benchmarks) to throttle the 2x A57 cluster, and I've never seen the 4x A53 cluster throttle under any conditions including hours of heavy gaming they stay at 1.4Ghz at all times.
Click to expand...
Click to collapse
Yesterday I was using GPS to drive and Spotify was streaming. The phone got really hot and unresponsive and Spotify began to stutter. Was unable to even launch textra to text someone.
This of course only started maybe 10m into the drive. The phone is fine while cold.
Maybe I have a defective device but my benchmark stress tests give similar results to other people.
Sent from my Nexus 5X using Tapatalk
ryanwalexander said:
Yesterday I was using GPS to drive and Spotify was streaming. The phone got really hot and unresponsive and Spotify began to stutter. Was unable to even launch textra to text someone.
This of course only started maybe 10m into the drive. The phone is fine while cold.
Maybe I have a defective device but my benchmark stress tests give similar results to other people.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
this is consistent with my experience. GPS and spotify (actually almost any app used concurrently with spotify) will cause the phone to have horrible lag.
also, don't text and drive
Interestingly, today when the phone was on battery saver it seemed much faster. Maybe more throttling could help things more than less?
Of course not exactly faster, but more consistent and no unbearable lagging.
Yesterday I flashed the stock firmware files other than user data. Unfortunately I lost root and it seems like I now need to reformat data to get TWRP going again but until then I'm fully stock. Does anyone know a way around that?
I haven't done enough testing to be sure but things seem to be running more smoothly for now than they did with root and ElementalX 1.06. However just writing this i can feel the phone heating up and becoming less responsive. The bottom 2 cores are offline with SoC at 36C and CPU at 56C when I switch to devcheck to check. Other 4 cores at 1440MHz.
ideaman924 said:
I've been having issues with thermal as well. Installed ElementalX along with the governer tweaks GhostPepper profile. When charging (this makes the device really hot) music begins to stutter, coming out of Viper4Android.
When not charging, slow accumulation of heat makes music stutter, same software used. Go figure. Maybe V4A is too demanding on the 808 chip, but I fear if this doesn't cut it, then I'll have to switch phones the next chance I get.
Oddly, this happens when screen is off - the music stutterings. I've thought about Doze and battery saving apps, and have disabled Doze for V4A through the battery optimize pane.
The phone constantly loses battery, around 2~5% an hour, I know thats not too much but my previous phone lost about 1% every three hours. This was a Note 3 Neo by the way. Installing Xposed and Amplify, Greenify and PowerNap should help, but I've had stability issues when using xposed. Maybe later.
Oh, and one last thing. My phone's thermal limit is set to 55 degrees Celsius, but it still feels like it throttles at around 39 or so. Maybe EX Kernel Manager isn't saving the changes, but either way... It throttles too much!
Click to expand...
Click to collapse
That could be because of the custom software and CPU tweaks or your V4A installation. Using those settings always has the potential to cause issues and I would troubleshoot there first.
Minimum CPU performance with stock settings is 4x A53 cores at 1.44Ghz which is still fast. If you've ever use one of the more recent Moto G devices you'd know it doesn't stutter playing music when it's cold and neither does this device when it's hot.
Sent from my Nexus 5X using XDA-Developers mobile app
Setting the throttling temp limit to high will decrease performance, see here for details:
http://forum.xda-developers.com/nexus-5x/general/thermal-throttling-temp-performance-test-t3388559
Alcolawl said:
Yeah, give it a few days. There are many ways to combat the throttling. Got my phone to 41C today while using it out in the sun. The Big cluster is limited to 633MHz at 36C and shut off at 41CC. The 46C built into the kernel is most likely for the LITTLE cluster to start getting throttled. Check the attached pics below.
Click to expand...
Click to collapse
Is this based on battery temperature or cpu temperature?
leo.best1398 said:
Is this based on battery temperature or cpu temperature?
Click to expand...
Click to collapse
CPU temperature but I beleive the phone also has ways of combating high battery temps as well.
Alcolawl said:
CPU temperature but I beleive the phone also has ways of combating high battery temps as well.
Click to expand...
Click to collapse
If its cpu temp then no wonder it's always throttling the cpu is nearly always above 40°c.
What do you mean ''combating''?
Sent from my Nexus 5X using Tapatalk

Categories

Resources