Related
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¢.
hey all, couldnt search forums since its disabled. so like my title says, my phone turns off whenever. the samsung logo comes up and turns off. it happens every so often but nothing annoying. to get it back on is either take battery out or plug to charger and turn it on. when i did this, it gave me the searching for battery thing. this leads me to believe it could be battery? it happens whether the battery is 90% or 20%. anybody have this problem? my phone is rooted using juggs 5.0. phone is just over a month old so wonder if i can get a replacement battery to ruled that one? thanks for the help..
Mines does the same thing except it only reboot when its on charge, and all my contacts dissapear
@OP: Try flashing a different ROM.
Juggernaut has pretty aggressive UVing that not all phones might like.
It happened to me just today. I tried opening Facebook and for whatever reason it FCed. So I reopened it and my phone just turned off. I had to hold the power button for 15 seconds before I felt a vibration and it was alive again. Not sure what the issue is but it's safe to say you're not the only one experiencing this
NJ_RAMS_FAN said:
hey all, couldnt search forums since its disabled. so like my title says, my phone turns off whenever. the samsung logo comes up and turns off. it happens every so often but nothing annoying. to get it back on is either take battery out or plug to charger and turn it on. when i did this, it gave me the searching for battery thing. this leads me to believe it could be battery? it happens whether the battery is 90% or 20%. anybody have this problem? my phone is rooted using juggs 5.0. phone is just over a month old so wonder if i can get a replacement battery to ruled that one? thanks for the help..
Click to expand...
Click to collapse
Random reboots are usually a sign of too aggressive of undervolting. If it's not happening under heavy CPU load and is just happening during standby/sleep phases, then you're just barely on the edge of too much undervolting. Download system tuner from the market and go to voltages in the main menu then knock up the voltage one step (+12.5mV). You should be fine then.
For reference, you can compare your voltages to this list of stock voltages to see what Jugs' global undervolt is. I'm not too familiar with Jugs v5.0:
http://forum.xda-developers.com/showthread.php?t=1523064
yoft1 said:
Random reboots are usually a sign of too aggressive of undervolting. If it's not happening under heavy CPU load and is just happening during standby/sleep phases, then you're just barely on the edge of too much undervolting. Download system tuner from the market and go to voltages in the main menu then knock up the voltage one step (+12.5mV). You should be fine then.
For reference, you can compare your voltages to this list of stock voltages to see what Jugs' global undervolt is. I'm not too familiar with Jugs v5.0:
http://forum.xda-developers.com/showthread.php?t=1523064
Click to expand...
Click to collapse
cool. I give this a try. The last time it turned off was right after I used gps. yesterday I was just browsing. thanks again.
Are you overclocking? If so what freqs/governor? Mine would do this when I would clock it too high for too long. May be an undervolting problem as well.
AaronPauley said:
Are you overclocking? If so what freqs/governor? Mine would do this when I would clock it too high for too long. May be an undervolting problem as well.
Click to expand...
Click to collapse
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
yoft1 said:
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
Click to expand...
Click to collapse
Thanks for the clarification. I've not really dabbled in undervolting much, and haven't been too concerned with overclocking since the ol' mt3g days. I'm definitely going to read more about it. I've found that for my s2, stock kernel w/ stock frequency set and governor have worked best. Every device is different they say. Thanks your way for the knowledge. Always appreciated.
yoft1 said:
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
Click to expand...
Click to collapse
Thanks for the clarification. I've not really dabbled in undervolting much, and haven't been too concerned with overclocking since the ol' mt3g days. I'm definitely going to read more about it. I've found that for my s2, stock kernel w/ stock frequency set and governor have worked best. Every device is different they say. Thanks your way for the knowledge. Always appreciated.
I am currently trying to set up profiles for SetCPU and I prefer to run my CPU as fast as possible so everything is buttery smooth (charging my phone is not a problem right now, so I am not worried about battery life). However, I am wary of placing too much stress on my CPU, so I was wondering if anyone knows how hot our ARMv7 processor can get before it becomes too much. If I know this temperature I can simply set up another profile that will limit the CPU's speeds to prevent any permanent damage from running it too much or too hot. Thanks!
The s4 chip set won't let it over heat. It goes to 1ghz when it gets too hot.
Sent from my SGH-T999 using Tapatalk 2
Thanks for the info! This is what I was hoping for
someone said in another thread i saw, the phone is fine up to 140F. if thats true, i couldnt say for sure, but just throwing it out there
Gello guys,
(I'm on MooDed ICS 1.0.2)
I wanted to know what kernel(s) is (are) the best to overclock the Arc and to what frequency can I go with the phone stable? I'm actually on InFamous Kernel ( http://forum.xda-developers.com/showthread.php?t=1843532 ) But I'm not overclock. I was before on DooM Kernel and overclock to 1.2 gh/z.
Thanks a lot! (And sorry for my bad English, I do my best)
It all depends on your phone. Even though there all made the same, some of the processors can not handle the same amount of OC as other do. The way to test which runs most stable is to slowly up the frequency every hour or so, and test it to see if it's stable.
If your phone starts to random reboot, then it's probably best that you choose the lower frequency to what you are using when it reboots.
I'm using inFamous Kernel too, its overclocked to 1.5.
1.4 should be theoretically safe as that the speed that the Arc S runs at with the same processor
EDIT: I don't recommend passing 1.5 on the Arc as it will very quickly burn out the processor. (Even at 1.5, it's running 50% more than what it was originally designed for).
Overclocking will also reduce your battery life. So it's swings and roundabouts depending on if you want performance or battery life.
Hope I helped
Over cloking is realy affect to battery life and all so the head will get increase,
am always usting 1.2Hz.i think it is enough to have a smoooth run for a xperia smart phone while saving the battery and reducing the risk
Ok thanks guys! I'll try all I can. I'm now overclocked to 1.2 ghz and battery life is good for me, because I recharge it all night. At 1.4 ghz, it's stable normally but the CPU is hot (very hot) and I don't want to burn it. But is it normal? Because Arc S is on this frequency and isn't normally so hot
So Thanks one more time!
Yeah, don't worry about it getting warm. If it gets really hot, then I'd recommend to stop using it for a while. Simply to let it cool down.
Mine can get to the point when it feels it's going to melt the plastic on the back yet it still works perfectly, so yeah i'd say its normal. There's also a ton of older threads about how much peoples arc's heat up when it's being used.
The reason why the processor gets so hot is because there is very little heat sink because of how thin the arc is.
Obviously the more you overclock the hotter the processor will get. The hotter the processor gets, the more quickly the CPU will burn out. If you don't like to replace your phone every few years, don't overclock it to the limit.
You should OC stable at 1.2 - 1.4 GHZ
Ah ok thanks.. I like to change it every year / 2 years. And now I'll try Puissant phone like GS3 and others.
I've overclocked it to 1.6 and it's stable (fast..) and hot. But I'll follow your advices. Thanks a lot!
dont overclock over 1.4Ghz if you have arc and you can always undervolt to save some battery juice
arpith.fbi said:
dont overclock over 1.4Ghz if you have arc and you can always undervolt to save some battery juice
Click to expand...
Click to collapse
Ok, but I didn't find thé option to undervolt where is it?
Thanks
U need apps for undervolting such as setxperia, voltage control, etc.. Reduce the voltage and test it for few mins then again lower the value until ur phone auto restarts. Tats the threshold value
Sent from SE Xperia arc s using tapatalk 2
Is it possible to undervolt it if it's overclocked?
Thanks
TheJurassien said:
Is it possible to undervolt it if it's overclocked?
Thanks
Click to expand...
Click to collapse
yea obv..undervolting means supplying less voltage to the cpu at specific frequency. it doesnt matter at wat frequency the phone is running
It might work fine well above 1.4 depending on the quality of the CPU you have in your device. I am fortunate enough to be able to overclock an xperia arc to 1.8 GHz and have been running at this clock for 6 months. Even gaming at lengthy time with charger plugged in works fine.
I do not game every day and just listening to music, talking on the phone, texting, reading a webpage or watching a video will not run the CPU at full speed all the time. Battery live if also fine for my usage 1-3 days. I prefer a snappy and responsive phone.
Running at very high clock speeds is at your own risc, the cpu chip design should be able to handle the high temperatures. I have allways overclocked my phones and have not yet been able to kill any of them, maybe I have just been lucky. There could be a poor soldering that breaks when it heats up, only push it to the limits if you can afford paying for a new phone
1,6 GHz on XArc by Sirkay = epic speed.
Sent from my CM9'd Galaxy Tab 2 10.1
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