Related
This is my third time typing this... (This website should really have an auto-save draft feature)
I recently installed the application "CPU Tuner" because I've always wanted to utilize my newly rooted phone. The phone is running Cyanogenmod 7.2 Stable, and currently overclocked at 1.5GHz. My main concern is overclocking my phone that high. Now, I didn't really choose that option, SetCPU automatically set it to that when it loaded a configuration. I'm a beginner to overclocking, and this is my first time doing it for anything. I've heard rumors of people melting their processors from overclocking it, so I want to know if it's okay if its overclocked to roughly twice the stock frequency of 800MHz. If it IS safe, then why isn't the phone automatically set to 1GHz to compare to it's twin, the Evo 4G? Or perhaps even 1.2GHz to surpass it? I would definitely be satisfied with 1.2GHz, but I wouldn't mind having 1.5GHz if it was stable and didn't drain the battery. On to the next question, would an OC this high cause instability and/or would it drain my battery? I only overclocked an hour ago, so I haven't experienced any problems whatsoever... yet. On to the profiles... I'd like some suggestions for improving my triggers. Right now, it set everything up to the highest frequency, but looking at the help, it said to not touch the frequency, but experiment with thresholds. In the Help, it doesn't tell you what the thresholds are, and what they do, and more importantly, how they work. It just shows that the highest is the most battery saving. I would have thought the lower the better, but... Anyway, if you could tell me, I'd be highly appreciated it. Finally, the battery temperature... It has an option to enable a setting to change profiles if the battery gets a certain temperature, but I'd like to know what would be considered "Overheating". I get paranoid when the battery temperature gets a little warm at around 36 Celsius... but the profile it switches to is supposed to really slow down the CPU to preserve battery, so I'd really rather not use it unless it's necessary. So, would 45 - 50 Celsius do, or should I set it a bit lower? My battery is 4000+ mV, if that'd help at all. If you know any sources that you can direct me to that would answer my questions, it'd be highly appreciated.
Wow ok . Well first off check out THIS thread. It will explain a lot about Governors, I/O Schedulers, and a bunch of the questions you have. As for people melting CPUs, I've never actually seen it happen, or know anyone who has had it happen on the Shift. That's not to say it's not possible. It may be, just not probable. The Shift processor compared to the OG EVO's is much better. The Shift even at the stock 800mHz out performs the EVO's processor at 1000mHz. That is in part because it is a 2nd Gen processor vs the EVO's 1st Gen Unit. The Battery Temp should try and always be kept below 115-120 Degrees Fahrenheit. I use SetCPU, and have a Profile that kicks in to lower the OC to around Stock should the Battery Temp every reach 110 Degrees Fahrenheit. My setting are 61mHz Min 1516mHz Max, Smartass V2 Governor, and SIO Scheduler. But every device is different, so your going to have to do a bit of experimenting till you find what works for you. If you get a lot of Random Reboots, lower your Max OC setting, or try a different Governor. BTW where did you get a 4000mAh Battery?
prboy1969 said:
Wow ok . Well first off check out THIS thread. It will explain a lot about Governors, I/O Schedulers, and a bunch of the questions you have. As for people melting CPUs, I've never actually seen it happen, or know anyone who has had it happen on the Shift. That's not to say it's not possible. It may be, just not probable. The Shift processor compared to the OG EVO's is much better. The Shift even at the stock 800mHz out performs the EVO's processor at 1000mHz. That is in part because it is a 2nd Gen processor vs the EVO's 1st Gen Unit. The Battery Temp should try and always be kept below 115-120 Degrees Fahrenheit. I use SetCPU, and have a Profile that kicks in to lower the OC to around Stock should the Battery Temp every reach 110 Degrees Fahrenheit. My setting are 61mHz Min 1516mHz Max, Smartass V2 Governor, and SIO Scheduler. But every device is different, so your going to have to do a bit of experimenting till you find what works for you. If you get a lot of Random Reboots, lower your Max OC setting, or try a different Governor. BTW where did you get a 4000mAh Battery?
Click to expand...
Click to collapse
Thanks for the response. It's pretty late, so I've bookmarked the link to read tomorrow. Alright, so 45 degrees Celsius should the maximum then. I've been thinking of switching over to SetCPU, since there are more comprehensive guides than for CPU Tuner (In which no one seems to have heard about), and it doesn't seem that the settings it set will be ideal for the long run. Although, before I switch over to SetCPU, I want to at least give it a shot. I'll change my settings so that the frequency decreases depending on battery level. Also, I don't have much but the basic governors and configurations on CPU Tuner, so I've never heard of Smartass V2 (Prior to skimming through the link you posted). Also, the battery came with it, I knew it seemed a bit different from most other batteries (From what I've seen in searches, most of them had around 2000), but I didn't know it meant that much.
The Governor settings available will depend on the Kernel, not on the CPU Controller. I've always been partial to SetCPU, but that's just me. I would again suggest doing a bit of reading, and experimentation to find your best settings. But defiantly the closer to normal the Battery temperature is the better. When the Battery heats up to much it will in most cases also drain faster. If you can post a Pic of the Battery I would really like to see it. I've never come across a 400mAh Battery for the Shift.
When I first rooted my shift 2 years ago I was very concerned of over-heating. I constantly checked the temperature. After a while I realized it is quite hard to over heat and cause damage, especially with the newest kernels the devs have put out. Just experiment with different settings and see what works best for your phone
Sent from my PG06100 using xda app-developers app
So recently I've become too lazy to constantly charge my Captivate and began to experiment with undervolting/underclocking it. Has anyone found optimal voltage for battery life? I've currently got every step of 200mhz down 100 volts and underclocked to a max of 800mhz. I'm on Semaphore kernel 2.9.5sc.
freshlimes said:
So recently I've become too lazy to constantly charge my Captivate and began to experiment with undervolting/underclocking it. Has anyone found optimal voltage for battery life? I've currently got every step of 200mhz down 100 volts and underclocked to a max of 800mhz. I'm on Semaphore kernel 2.9.5sc.
Click to expand...
Click to collapse
There isn't a optimal setting as all phones act different. Testing is the best you can do.
which cpu governor are you running? that may have more effect than underclocking/undervolting on battery life.
user Stempox has a nice post on cpu governors here
http://forum.xda-developers.com/showthread.php?p=28647926
the screen on time and data/gps traffic, and apps that keep the phone awake, do more to effect power drain than other factors. so, if you manage those, and choose the governor that suits you preferences, then undervolting and underclocking aren't needed, IMHO.
you can tweak the governor settings with Semaphore manager, if you really want to do that too.
the thing is, you may end up keeping the screen on longer than you would at higher cpu speeds, which would counter any battery savings. also, undervolting can increase the error rate, which means further delays while phone is awake.
hope this is helpful in your pursuit of fewer charging cycles.
Sent from my SGH-I897
Hello guys
I'm not a new user in kernels or ROMs .
I have a low-decent battery life ,and I'm sure there's a way to get a better battery life with undervolting .
I want to know
what is "undervolting" ?
What is the biggest damage it can cause?
What is PVS?
How do I know ,how much I can UV?
What are the steps to undervolt?
What I gain from UV (despite battery life)?
For your info ,I'm using AOSPAL ROM +FAUX's latest 16u kernel .
Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2537000
Sent from my Nexus 5 using Tapatalk
Hi,
Most of your questions have a reply:
About undervolting: http://forum.xda-developers.com/google-nexus-5/general/nexus-5-undervolting-thread-t2537000.
CPU binning: http://forum.xda-developers.com/google-nexus-5/general/cpu-binning-nexus-5-t2515593.
The "risks" are instability like hard reboot, SOD, etc.... To find a "safe" value you will need to test by yourself to find what undervolting your CPU can handle, not all CPU's are equals.
Undervolt by steps like - 25mV, don't set your new values at boot unless your are sure it's stable (or you could encounter bootloop), test for a few days under different conditions (as your use).
The gain apart battery life (but you will not gain that much as people tend to think) is a little less heat, but again nothing huge..., better is to test by yourself and see what you will gain... or not.
Battery life depends mainly of your use, apps, signal quality and settings like, screen brightness, synchro, CPU governor, etc... In my opinion check first what could be the cause of your low battery life (and what is low battery life for you???) before play with undervolting.
As said above, undervolting will get you very minor battery life increases.
More than likely you have an issue, or its just your setup and usage giving you the battery life you are seeing.
Undervolting will not change any of this.... You'll gain only minutes of battery time.
Try some troubleshooting in the below thread to see if you have an issue, or how to setup for better battery life. Read through it a bit, from the last page and work back a bit. You can post meaningful screenshots there too. From gsam or BBS.... not the stock battery screen, it has no real useful info for finding issues. Good luck!!
http://forum.xda-developers.com/showthread.php?t=2509132
Nexus 5 Battery Results
I've been undervolting many systems for many years, primarily Linux desktops and some servers, and the primary benefit is that you get less heat output which means when running cpu-intensive tasks the temperature climbs slower so the throttling of the clockspeed kicks in later, so your phone will be faster in certain situations. If you take a phone which has been idle for a while and run a benchmark, and then immediately run that benchmark again, the 2nd time gets a lower result as the phone is still hot from the 1st. This makes drawing conclusions about settings really dificult but it illustrate that throttling from heat is affecting speed.
For most users their perception will be the phone runs cooler.
You do undervolt at each step in the processor's frequency, and each step is a trial+error activity, the throttling I mention means finding a stable under-volt at the higher frequency which is labour-intensive,i.e take the max clock, and undervolt it a little, run a benchmark which forces it to run at high clockspeed, and if it passes that test then run it again at the next step down in frequency. Once you've got the most stable top clockspeed, then do it progressively for all the other voltages on the way down.
In some platforms in Linux and Windoze, we wrote scripts which save the stable voltages and then undervolts a little and runs a stress-testing benchmark and if the system hung it wouldn't save the current voltages so the previous higher voltages were safer, stick that script in a startup script area and leave the compute to do many self resets, and you've calculated your device's voltage range. I wonder if someone has that done for Android??? For a laptop the FAN would run slower saving battery time and for laptops that would lead to say 20% better battery life but on a phone it won't make much saving as no fan.
Your phone will run most of its time (like 95%) at its lowest frequency, so for effort/benefit just focusing on dropping its voltage will gain the most in the phone running cooler.
Battery life improvement is marginal, if you look at your battery stats its down to your application settings and screen brightness, i.e. how you use and what you do with your phone. So if your battery life is bad, use your phone less!
I carry a slim USB battery, it is the $/effort/benefit the best thing you can do, $20 doubles your battery life, if you get one with a 1.5A-2A output in just a few minutes when the phone doesn't mind a battery attached, will dwarth every possible tweak and hack anyone can form in benefit.
Starting a month and half ago my LG Nexus 5 would get hot near the camera (Where the CPU is) and drain the battery unusually fast, even without an active app opened, now I can not keep it on outside because of the drain and even if it stays connected to a charger, it slowly builds a charge because of the drain.
I recently changed the battery and the problem continues to persist.
This started happening around when I went over all the settings in the phone and apps, I fear I might of turned on something that is causing it in the background but I can not figure out the exact problem.
Please help.
minun said:
Starting a month and half ago my LG Nexus 5 would get hot near the camera (Where the CPU is) and drain the battery unusually fast, even without an active app opened, now I can not keep it on outside because of the drain and even if it stays connected to a charger, it slowly builds a charge because of the drain.
I recently changed the battery and the problem continues to persist.
This started happening around when I went over all the settings in the phone and apps, I fear I might of turned on something that is causing it in the background but I can not figure out the exact problem.
Please help.
Click to expand...
Click to collapse
Check the frequencies of the cpu, sometimes the minimum value gets stuck to a higher than needed frequency.
You can do so by using Kernel Auditor (root) or CPU-Z. Obviously if they're higher you'll need to set them lower, 300 MHz is the normal minimum freq. If that is not the case then install Gsam Battery Monitor and enable extra stats, you should be able to figure something out with that one app.
CriGiu said:
Check the frequencies of the cpu, sometimes the minimum value gets stuck to a higher than needed frequency.
You can do so by using Kernel Auditor (root) or CPU-Z. Obviously if they're higher you'll need to set them lower, 300 MHz is the normal minimum freq. If that is not the case then install Gsam Battery Monitor and enable extra stats, you should be able to figure something out with that one app.
Click to expand...
Click to collapse
thank you, it was the outlook app going rouge
Hello to all of xda-dev users. I got problem with my Galaxy s6 Active smartphone. One day it's just start overheating and draining batery very fast, just about 1% per minute or two. I have search many threads over many forums for solution and didn:t find it so i ask here, maybe someone will help me.
What i have noticed that overheating is caused by processor (sensor exynos-therm) while battery stay cool. I have did a factory reset few tmes but it didn't help. I have flash a new rom from this forum, upgrading from android 6.0 to 7.0 but it also didn't resolve the problem. I have no ideas what to do and where to search to find reason of overheating. While device is running, all monitoring software shows minimal activity and processor usage, anyway the processor seems to overheat up to 80C (almost 180F). Please don't say it is normal cause it didn't work that way before that malfunction. I hope someone will help, thanks!
To start...
Run the monitoring software as root? Reading the CPU usage of processes might be restricted without it?
CPU clock is lower with thermal throttling and doesn't look like heavy usage?
GPU?
Persists with wifi off?
Check for wakelocks/CPU background time, and it's the process at the top?
*#0011# > select SIM > Tx power/TX, when the signal strength or quality is low, the decoding/transmitting could be expensive, the tx power isn't everything but it should ramp similarly, is this high?