Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Actually when I was on the second ics leak, and setcpu worked fine. I know this because I benchmarked before and after setting frequencies
Sent from my ADR6425LVW using XDA
benchmarking doesn't mean it wasn't running at full tilt when you didn't need it to. unless your kernel magically doesn't include perflock, it was.
also, there are some combinations of setcpu and monitoring that will work. at one point if i used setcpu, cpu monitor, and one other which i forget now, it would work, kind of. definitely not recommended.
Thats why I deaded mine. Phone was constantly overheating
Sent from my ADR6425LVW using xda premium
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
tspderek said:
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
Click to expand...
Click to collapse
Agreed. I had set CPU try to disable perflock and limit to 1200mhz on conservative and it ended up being worse battery and slower overall.
You're exactly right I advise everyone I discuss the topic with to make sure and avoid trying to over ride perflock with a CPU management app. It causes a conflict in my opinion which is a huge battery drain and also causes excessive heat due to the process of fighting for its life.
Sent from my ADR6425LVW using xda premium
I've been saying this I even started a thread to smash this rumor of ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels.
THERE WAS NEVER ANYTHING WRONG WITH ANY ICS LEAKS. JUST USER FAULT
Sent from my ADR6425LVW using XDA
richii0207 said:
I've been saying this I even started a thread to smash this rumor if ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
con247 said:
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
Click to expand...
Click to collapse
My favorite part is when they try to sound like a dev, I guess everyone's a dev on here ;-P. At least I only say something I know from EXPERIENCE and not what I read ;-)
Sent from my ADR6425LVW using XDA
jayochs said:
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
Click to expand...
Click to collapse
the widget i posted is what you want. it should be scaling up and down, and settling eventually when nothing is really going on. the system panel that you tried clearly affected the perflock in some way. from what i understand, some apps/widgets look at the cpu itself, while others hit up the kernel for status. the ones that hit up the kernel are the issue. i'm not 100% on this, that's just what i've been told. all i know is my experience seems to match this.
tspderek said:
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Click to expand...
Click to collapse
Hmm, that's weird, cause I've been using setCPU with ICS on the Rezound for months and it works great! My CPU scales fine and hits all the frequencies its supposed to. The min and max frequencies do change around seemingly randomly, but anyone can see by watching the current frequency display that it is always somewhere in between the range I selected, and always appropriate for the system load.
I've always had CPU Master installed. I just removed it, we'll see how it goes.
Related
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
just experiment, start with small increments (don't save your settings!!!) see if it reboots, if its stable for a day or two, increase it, when it starts crashing dial it back a notch.
Just like overclocking except in reverse and with voltage basically.
note I'm not sure re: kernel requirements, I haven't tried it yet with my atrix, and my current ROM runs stock kernel I think.
its hit and miss, for example on my SGTab I can't undervolt at all or else it crashes all the time, others get away with -100mAh across the board (bastards), but mine is happy on 1.1OC.
WTFsandwich said:
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you like cars it seem this will be the best way to explain it
http://forum.xda-developers.com/showpost.php?p=15947019&postcount=643
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Yes, start conservative.
Another way to use setcpu to improve your battery life is to set a screen off profile to restrict the CPU speed to minimum when the screen is off.
I tried that one, but it kept stalling my phone when turning the screen back on when it was at the bare minimum.
EDIT: For anyone wondering, -75 seems to cause frequent freezes.
Sent from my MB860 using XDA App
mramirezusa said:
If you like phones it seem this will be the best way to explain it
Think of it as tweaking the CPU of a phone to use just enough power to prevent it from failing in order to conserve battery life without affecting it's normal operation.
Click to expand...
Click to collapse
Fixed that for ya!
WTFsandwich said:
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Any overclocking or underclocking is always trial and error. Rule of thumb is to only ever change one thing at a time in small increments, then test before adjusting again. Your approach should be methodical and not haphazard, i.e. in a PC change cpu clock speed in small increments until you fail to boot or BSOD, then change voltage in small increments until you boot and are stable again. Monitor temperatures all the time, and add cooling if necessary. If you take a methodical approach, and don't rush things, you can achieve surprising results with hardware/software tweaking.
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
A good test is to just use it as you normally would. If the phone doesn't reboot, you're good to go.
Sent from my MB860 using XDA App
edit: pls delete
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
WTFsandwich said:
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Do something CPU intensive also to see if it crashes, like play a game. You want to stretch the phone to the limits to test it at the most extreme condition you will use it under.
WTFsandwich said:
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
Click to expand...
Click to collapse
Maybe a factory/data wipe?
Other than that I can't think of anything myself.
ddddddddddddd
you may try to use default stock kernel, on wich overcloking do not work.
re: setcpu, sorry I think you have to reflash... thats why you don't save the settings until you're sure
there is no shortcut way.... you may be fine for a day but next day it keeps crashing. Happened to me on my SG tab when I went to 1.2 for example, I thought it was hunky dory then a few days later crashing galore.
the longer you leave it for the better you are, its really your call to make. Some people prefer the extra speed and will live with a crash or two a week (not me, its my phone not gaming pc lol).
not sure how much stress testing you can/should do. Back when I was OCing PCs I would leave stress tests running overnight, but probably not a good idea to 100% CPU a phone overnight lol
Well I just got my phone and flashed it to Unnamed rom. Now there's a slight delay when waking up the phone, around 1-2 seconds. Is that normal? I didn't get to test it on stock so I'm not sure if other people have that slight delay. Is a bit annoying at times cause I would double press and it would sleep it again. Just wondering if its normal. Thanks.
It's the default Conservative CPU governor used in Entropy's Daily Driver kernel included with the ROM. As a battery saving measure the conservative governor scales up more slowly. Entropy has a zip in his kernel thread to restore the On Demand governor of you prefer. It scales up a little more quickly but uses a little more battery since out uses more of the upper CPU states.
Sent from my SAMSUNG-SGH-I777 using XDA App
Hmm, would you say is worth it?
deathsycthehe11 said:
Hmm, would you say is worth it?
Click to expand...
Click to collapse
According to your preference really. I'm using the Conservative since it was included with the kernel and getting mostly good snappiness, but I might switch back to OnDemand since I was getting pretty good battery life on the stock kernel with OnDemand anyway.
Hmm, alright. How exactly would I do this? I don't need a full step on step guide. Just a short sentence. I'm a android newb but can understand stuff easy. Do I use odin and just flash the ondemand zip? Do I need to do anything before that if thats the case?
deathsycthehe11 said:
Hmm, alright. How exactly would I do this? I don't need a full step on step guide. Just a short sentence. I'm a android newb but can understand stuff easy.
Click to expand...
Click to collapse
Go to Entropy's thread, download the Ondemand zip, flash it, done.
Rrryan2 said:
It's the default Conservative CPU governor used in Entropy's Daily Driver kernel included with the ROM. As a battery saving measure the conservative governor scales up more slowly. Entropy has a zip in his kernel thread to restore the On Demand governor of you prefer. It scales up a little more quickly but uses a little more battery since out uses more of the upper CPU states.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
No, it's the fact that our device fundamentally takes at LEAST 650 milliseconds to resume from suspend. It does not matter what kernel - I have NEVER seen this numer lower except for some I9100 users, and the best they can do is intermittently get resume down to 500-550 msec.
Entropy512 said:
No, it's the fact that our device fundamentally takes at LEAST 650 milliseconds to resume from suspend. It does not matter what kernel - I have NEVER seen this numer lower except for some I9100 users, and the best they can do is intermittently get resume down to 500-550 msec.
Click to expand...
Click to collapse
Interesting, learn something every day. Thanks!
THat small pause doesn't bother me, conservative is what I use as well. It's like getting smacked to wake up and roll outta bed, it's gonna take a sec ya know?
So far I've just been using SetCPU for over/underclocking but have never messed with undervolting. I was wondering what most people use if your main priority is undervolting for better battery life. I'm running Siyah 2.6.7 with SHOstock ROM. Any help/feedback is appreciated.
mpkothari said:
So far I've just been using SetCPU for over/underclocking but have never messed with undervolting. I was wondering what most people use if your main priority is undervolting for better battery life. I'm running Siyah 2.6.7 with SHOstock ROM. Any help/feedback is appreciated.
Click to expand...
Click to collapse
Well, undervolting is very tricky. Each CPU differs in its ability to undervolt, so settings that work for one may not work for others. You'd have to do some testing. I recommend either a.) undervolting one tick and run AnTuTu benchmark multiple times as well as a demanding game/app (Run them for a long time), or b.) undervolting one tick and using your phone normally as per your current usage and if by the next morning it's still running as normal, repeat one tick.
Do NOT set "Set on Boot" to on until you've run these tests and have had no issues.
Hope this helps a little.
Do not worry about 1400,1600 mhz till later since that's when your overclocking.
Bump everything else down by 25mv, run the stress test and a few intensive programs like benchmarks/games.
Keep doing that till you start to notice problems and then revert to the best setting you had. (make sure to backup or not set on boot)
Once you go through all that then you can do it for individual mhz and see which can still be lowered.
This should keep you busy for a hour or so.
I'll share what I posted in another thread. Doing stress tests are fine, but if you test throughout the course of a day or more, you have the opportunity to come across situations you might not think of during testing.
Simba501 said:
Ouch....I think the best way to experiment with undervolting is to use Voltage Control. Save the stock settings as your boot settings (it saves everything - governor, frequencies, etc; so, make sure those are what you want them to be as well), then undervolt (at the beginning of the day). If you make it to the end of the day with typical usage, you can save those as your new boot settings. Undervolt further at the beginning of another day, etc. Once you make it to the point where you get locked up, voltage control will set the previous values at boot and you'll know that those are your limits.
EDIT: If you want to play it extra safe, run values for more than one day.
Click to expand...
Click to collapse
I'm at work right now trying not to get easily distracted by xda since I keep checking whether or not an ICS leak has been ported or something. Thanks guys for your much appreciated input. I've been running with all voltage values knocked down by 50mV with the exception of 1.4 and 1.6 GHz. Those I kept stock since I'm not overclocking. So far so good actually with sio/ondemand and Max 500 Mhz. It's surprisingly smooth and battery of course is doing exceptionally well at these settings. Switched over to voltage control for now.
Sent from my SAMSUNG-SGH-I777 using xda premium
I personally have become very fond of voltage control where as I'd previously been using set-cpu for nearly ever since the H1 and mytouch days. Voltage controls just allows more freedom and tweakability.
Alucardis666 said:
I personally have become very fond of voltage control where as I'd previously been using set-cpu for nearly ever since the H1 and mytouch days. Voltage controls just allows more freedom and tweakability.
Click to expand...
Click to collapse
Right there with you. just "converted" to Voltage Control. (thanks Simba!)
K Rich said:
Right there with you. just "converted" to Voltage Control. (thanks Simba!)
Click to expand...
Click to collapse
Heh, glad I'm not the only defector
Simba501 said:
I'll share what I posted in another thread. Doing stress tests are fine, but if you test throughout the course of a day or more, you have the opportunity to come across situations you might not think of during testing.
Click to expand...
Click to collapse
That's the post I was thinking of, I just honestly couldn't figure out where I saw it or who wrote it.
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Just try clearing app data rebooting and reinstalling the app. That problem has happened to me every once in a blue moon and that fixed it for me.
Sent from my SGH-I777 using Tapatalk 2
Thanks, I'll try reinstalling the kernel.
Which app are you referring to? because I had this problem no matter which app I used to change the governor (Extweaks, voltage control, setcpu).
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
bacon_n_icecream said:
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
Click to expand...
Click to collapse
It's the lulzkernel for some-reason :|
I have problem goto smartassv2 it's ok just steps heavy
Thanks for your suggestion. I just moved over to ondemand and its been ok for me. Too early to make any judgments but I'll try smartassv2 next.
Not that I'm glad to that you're having problems, but I'm glad I'm not the only one with this issue. Thanks for the response
Winklie said:
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Click to expand...
Click to collapse
DONT use kernel cleaning scripts. They cause more problems than good.
Sent from my AT&T I777 running AOKP build 3X
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
bacon_n_icecream said:
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
Click to expand...
Click to collapse
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
thanks, I generally do that any way along with the script cleaner
K Rich said:
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
CPU related as well...
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
kbulut said:
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
Click to expand...
Click to collapse
Lots of questions there. Phone overclocking is the same and at the same time different than PC overclocking. I too bought SetCPU and due to bugs and problems have completely abandoned it. Honestly with the exception of running an epeen benchmark there is little incentive to overclock. Find a newer Kernel (I use NEAK which has no overclocking ability) and install it, performance is stellar. You really have to ask yourself, is my phone slow enough that I need more CPU power to make it faster?
To see what time your CPU is spending at a given clock speed, download CPUSpyhttps://play.google.com/store/apps/details?id=com.bvalosek.cpuspy&feature=nav_result#?t=W251bGwsMSwyLDNd, you will be surprised to see your phone spend very little time at it's max clockspeed.
Due to the immaturity of the fab process for our CPU's (well SoC), what is a stable overclock for one person might not even load for another. These CPU's are not like an Intel Sandy Bridge, with 1Ghz of free overclocking, nearly guaranteed. You can certainly play with voltages to try and attain a higher overclock, but at the expense of CPU lifetime, as well as battery.
Additionally, it takes a new Kernel 3 or so full charge, discharge cycles on a phone to really 'settle in' and 'learn' a particular phones battery, while yours got hot, which to me indicates an endless loop of some kind running in the background.
My advice would be as follows: Choose a ROM you like, feel free to play with different Kernels, again, I use NEAK, which does not work for some folks, or crashes or whatever. Give it several days to 'settle in' and if your still not happy with performance or have stability problems, try a different governor/scheduler. You really need to establish a good, solid baseline of your phones performance and make small changes and give them long enough to establish any changes to your phones overall stability. Basically running cowboy through your phone and making changes will have a negative overall outcome. Make small, documented changes, test and see what overall effect this has to your phone's stability and battery life, and make another change.
bacon_n_icecream said:
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Click to expand...
Click to collapse
Lulz has known problem in 3.2b2-1
Gokhan has fixed it in 3.2b2 - 2
Wait for ktoonsez to update it for us
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Thank you so much for the information. Could I simply uninstall the setcpu and go back to normal? Simply reflash the rom and/or kernel? I really like shostock2 with the cherry picker kernel for now. I want to give them a week of try to make my mind. Before the setcpu I think.I was better off
Thanks for the help by the way. I appreciate it.
Thanks for the update about the new siyah kernel. Glad it wasn't just me with the issue. I was going to post this question in the siyah thread but am new to the site so didn't have permission so thanks for finding me all the way over here
Phalanx7621 said:
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going off what I've seen in the Siyah/NEAK threads. Most of the lock-ups/random reboots I've heard people having had used the cleaning script. Either that or its just coincidence.
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
bacon_n_icecream said:
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
Click to expand...
Click to collapse
Hmm, well I've just manually wiped cache and dalvik and have never had problems between roms/kernels.
Sent from my SGH-I777 using Tapatalk 2
Hello
I'm using the Ultima rom and I need help undervolting. In Stweaks there are only sliders per frequency but on stock with Siyah kernel, there was a drop down list with -25 and -50 on it.
I don't know how to edit using the sliders. How can I get the drop down list back?
SuperAce609 said:
Hello
I'm using the Ultima rom and I need help undervolting. In Stweaks there are only sliders per frequency but on stock with Siyah kernel, there was a drop down list with -25 and -50 on it.
I don't know how to edit using the sliders. How can I get the drop down list back?
Click to expand...
Click to collapse
check for boeffla kernel it has drop down list but make sure it works for ur Rom or ull screw it up
No offense but if you can't figure out a slider, perhaps you shouldn't be undervolting.
Besides, most devs don't believe it saves battery anyway. After stopping undervolting recently myself, I'm inclined to agree
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
No offense but if you can't figure out a slider, perhaps you shouldn't be undervolting.
Besides, most devs don't believe it saves battery anyway. After stopping undervolting recently myself, I'm inclined to agree
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Nah, I finally learned how to do it using System Tuner. I was confused because when I moved the slider a bit, all the numbers changed and I couldn't figure out where the -25 was gonna be at. But I got it now.
Are you sure it doesn't attribute to battery life? I went a whole -100mV in general and for me it seems to have improved a bit. Not by much but it is noticeable.
Anything else you recommend? I'm completely new to the device, but I familiarize with tweaking very quickly.
SuperAce609 said:
Nah, I finally learned how to do it using System Tuner. I was confused because when I moved the slider a bit, all the numbers changed and I couldn't figure out where the -25 was gonna be at. But I got it now.
Are you sure it doesn't attribute to battery life? I went a whole -100mV in general and for me it seems to have improved a bit. Not by much but it is noticeable.
Anything else you recommend? I'm completely new to the device, but I familiarize with tweaking very quickly.
Click to expand...
Click to collapse
I've been undervolting for about 3 years but I have noticed no effects by ceasing this activity. I have noticed improved stability though. I actually notice more effects by tweaking things like CPU sample times etc
I use SetCPU
rootSU said:
I've been undervolting for about 3 years but I have noticed no effects by ceasing this activity. I have noticed improved stability though. I actually notice more effects by tweaking things like CPU sample times etc
I use SetCPU
Click to expand...
Click to collapse
You mean better stability after or during the undervolting? And what's your stand on OC? Do you also think UC saves battery as well?
Lol sorry, I just like asking people that know about these things before I try messing with them.
Yeah its more stable at stock voltages.
I recently stopped overclocking. I don't have any particular reason not to overclock. I was troubleshooting an issue and overclocking and undervolting should be the first to go when doing this. Just didn't have a need to re-overclock.
One thing I would say though... if you're overclocking, don't add more voltage than 1400 MHz is set as stock... that adds heat. Heat + clock = damage
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Yeah its more stable at stock voltages.
I recently stopped overclocking. I don't have any particular reason not to overclock. I was troubleshooting an issue and overclocking and undervolting should be the first to go when doing this. Just didn't have a need to re-overclock.
One thing I would say though... if you're overclocking, don't add more voltage than 1400 MHz is set as stock... that adds heat. Heat + clock = damage
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I see. Thank you very much for all this.
But I ran into a problem. Screen flickering. When the screen is off and I press the home button, a bright flash appears then the lock screen turns on. That's the only problem I've been having and it's scaring me like crazy. I've seen some flickering issues but none like this one. Do you think it has to do with the volting? I've restored normal voltages and hasn't happened so far. It's happened twice since last night and today. Both after undervoltage. I hope that was the cause.
SuperAce609 said:
I see. Thank you very much for all this.
But I ran into a problem. Screen flickering. When the screen is off and I press the home button, a bright flash appears then the lock screen turns on. That's the only problem I've been having and it's scaring me like crazy. I've seen some flickering issues but none like this one. Do you think it has to do with the volting? I've restored normal voltages and hasn't happened so far. It's happened twice since last night and today. Both after undervoltage. I hope that was the cause.
Click to expand...
Click to collapse
I dont know tbh...
rootSU said:
I dont know tbh...
Click to expand...
Click to collapse
No, it doesn't have anything to do with undervolting. It just happened again. I really can't tell what it is.