Hey guys, anyone have a good idea of what some safe undervolting values would be? I was just going to play around with them and not set it on reboot so I could just pull the battery, but I am unsure of how irreversible the damage could possibly be, if any.
I am running: Senseless 1.0
dsb's kernel
I actually have it underclocked slightly because I don't play games, and when I do they are something like Angry Birds, or Words when I am bored.
Bump, out of all of you who have undervolted none of you know any good values?
AtLemacks said:
Bump, out of all of you who have undervolted none of you know any good values?
Click to expand...
Click to collapse
Well, since no one will answer, I will
I generally only keep it undervolted -50mV across the board. That's just my usual set up to get a tiny bit more from the battery. The furthest I've gone is -200mV at the top. I didn't keep it like that for long, but everything seemed to run smoothly still. I'm sure I could go much lower, but I'm kind of afraid to until I know more about it.
I'm just starting to work on undervolting today since I found a kernel that works really well. I'll let you know what my phone is stable at.
WasabiWa83 said:
Well, since no one will answer, I will
I generally only keep it undervolted -50mV across the board. That's just my usual set up to get a tiny bit more from the battery. The furthest I've gone is -200mV at the top. I didn't keep it like that for long, but everything seemed to run smoothly still. I'm sure I could go much lower, but I'm kind of afraid to until I know more about it.
Click to expand...
Click to collapse
Cool, I didn't know what was "too much". How much better battery life did you see from -50?
Evo4gLI said:
I'm just starting to work on undervolting today since I found a kernel that works really well. I'll let you know what my phone is stable at.
Click to expand...
Click to collapse
Which Kernel are you running?
At -50mV across all frequencies, it reeeally varies. I never have a "normal" day with this phone. But, the shortest I've had using Ziggy's kernel from 192-1836gHz with on demand governor is around 7 hours. That was pretty heavy usage for me. Some games like Dead Space and Captain America, tons of internet, Pulse, texting, a few phone calls, music, and a little Netflix at night. The longest I've had has been 20+ hours. That's with very little gaming, a little internet, and mostly just texting. Stock battery, bump charged.
I'm really afraid to go too low, though. One time I was just seeing what would happen if I kept lowering it across all of the frequencies and it froze, then crashed. Had to battery pull to get it to work again.
I run DSB Kernel with SmartAssV2 underclocked to 1296, and before undervolting on my OEM battery I got 13 hours with a little over normal usage. Screen was on for about 2 hours total. On my extended battery I got like 27 1/2 hours, but obviously some of that time was overnight.
2 hours later I am still above 90% this is what I like to see! If I can get 15 hours on OEM battery, my extended battery will stay in my truck as my backup!
AtLemacks said:
2 hours later I am still above 90% this is what I like to see! If I can get 15 hours on OEM battery, my extended battery will stay in my truck as my backup!
Click to expand...
Click to collapse
Might mess with this, I am running same kernel same governor. How much did you undervolt in the end? I was gonna push-100 on each and see how it goes...
Sent from my ADR6425LVW using XDA App
I went -50 across the board, using dsb kernel, underclocked to 1028, and everything is stable.
Sent from my HTC Rezound via Tapatalk
nosympathy said:
Might mess with this, I am running same kernel same governor. How much did you undervolt in the end? I was gonna push-100 on each and see how it goes...
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Just -50, but I updated the kernel and forgot to remove the PH98IMG prior so I set the phone into bootloops. Had to factory reset(after trying everything else) and start over from backups.
Evo4gLI said:
I went -50 across the board, using dsb kernel, underclocked to 1028, and everything is stable.
Sent from my HTC Rezound via Tapatalk
Click to expand...
Click to collapse
See, I don't get the overclocking hype. It isn't hard to overclock when needed, so I feel underclocking is the better choice for battery life. The phone is fast as hell no matter what.
I may try to do some undervolting...but I am running clean rom 1.3 and dsb's smartass kernel, and I have been getting good battery life for what I use my phone for. I do have it overclocked though (on demand).
You won't damage the phone with undervolting. I mean a lockup might be a pain, but it won't damage the phone. Overvolting on the other hand could ruin the phone.
I will probably just stick with -50 across the board for now, I am tempted to pay for the full version just so I can save profiles and not have to set on boot.
Late reply but running AOKP w/ frAnco I UV -100 with no issues at all.
Running -75 on everything with incredikernel
bendirkss said:
Late reply but running AOKP w/ frAnco I UV -100 with no issues at all.
Click to expand...
Click to collapse
You sir must be using a Gnex. LOL
Related
I tested it once and I'm losing 4% per hour. Its 800-200 on demand as main, screen off at 500-200 and less than 50% battery also at 500-200.
I haven't toyed around with different kernels, I'm using the kernal that came with Zedomax's root instructions. Also, 200, 500, 800, 1000 and 1200 are my only options, this is because of the kernel that I'm using correct?
In your experience is -4%/hour average or does it seem like SetCPU is working? 500-200 is the lowest I can go otherwise it would be 200-200.
Thanks
Sent from my SAMSUNG-SGH-I777 using xda premium
Sounds like you have some apps or widgets draining your battery. I've overclocked mine to 1.6 and get less than 1%/hr drain on idle.
First off, what rom are you running. Try unnamed or serendipity. Don't do the 50% or less at 500-200 its gonna slow you down. Also switching to entropys daily driver should net you an improvement. Also try out the conservative governor. Its just as good as ondemand but with better battery.
Sent from my SAMSUNG-SGH-I777 using XDA App
I am running stock ROM. Should I bump the 50% up to 800-200? I don't have many options with this kernel/rom.
Im still new to this process as well
CollegeProfesor said:
I am running stock ROM. Should I bump the 50% up to 800-200? I don't have many options with this kernel/rom.
Im still new to this process as well
Click to expand...
Click to collapse
800 should be fine for most things, only adds a tiny bit of lag to paging around the apps and home screens. I just benchmarked mine at 800 and got a 2721 on Quadrant, which is only ~500 less than what I got at 1200mhz on stock.
Also, I was wondering, is the issue with screen-off speeds below 500mhz still around? I have mine at 200-1600 conservative and I haven't had any issues yet.
Thanks. I flashed UnNamed and now I can finally overclock, but SetCPU won't allow me to set my main to conservative. Ive tried it multiple times and re-booted as well.
I also want to undervolt, I've reduced each one by 50, thoughts? Is this too little?
Thanks again, im trying to get the hang of this
CollegeProfesor said:
Thanks. I flashed UnNamed and now I can finally overclock, but SetCPU won't allow me to set my main to conservative. Ive tried it multiple times and re-booted as well.
I also want to undervolt, I've reduced each one by 50, thoughts?
Click to expand...
Click to collapse
Is it giving a error could be the new kernel didn't flash. Go to entropy's thread download the newest version and flash via CWM. See what it does then.
nh5 said:
Is it giving a error could be the new kernel didn't flash. Go to entropy's thread download the newest version and flash via CWM. See what it does then.
Click to expand...
Click to collapse
Nevermind, it worked. SetCPU was just using a different governor for a profile that I set.
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
What I'm running:
Latest NEAK kernel + AOKP build 36.
Issue also occurred in Phonebricker + NEAK (sammy version).
My issue:
Occasionally the OS will get extremely slow, like you would expect if the phone were running at 100mhz or something. Everything continues to work, just reeaaallly slow. For instance, music playback gets very electronic-y as sounds are stretched out, tapping one of the capacitive buttons takes 5-10 seconds before vibration/feedback, and another 5-10 seconds before a menu pops up. I managed to get the NEAK configurator open and scrolled to the CPU tab, and it claimed I was at 1200mhz - though the phone didn't even get warm so I'm skeptical.
I'm guessing since I've done a full wipe between phone bricker + NEAK and AOKP + NEAK, the only thing in common are my apps and the NEAK kernel, so it stands to reason it would be one or the other causing this. My wife's GS2 is running AOKP + NEAK as well though and we haven't experienced this problem on it yet (but it's intermittent so it might be there, just hasn't happened yet). I'm currently running conservative governor + SIO, but it has also happened on conservative + NOOP.
While I could just change a bunch of sh!t and hope it goes away, I'm more interested in figuring out what's causing it, and fixing it properly. How can I figure out what's going on? What will log this kind of thing? What do you guys recommend?
Thanks!
this is really easy/simple. flash a different kernel. all devices are not created equally so you need to just try everything that we have and see which best fits your device.
if you had this issue on 2 different roms with the same kernel then you've answered this question in your post for yourself. it wasnt even necessary to post this dude. change kernels. done.
some phone like neak kernel, some phones dont. some phones like siyah, some phones dont. you cant "fix" that unless you get a different phone and try neak again. but even then it my not "fix" this issue because nothing is broken.
Well, what if it's something as simple as the governor I'm using or an undervolt setting? I'll probably flash back to your kernel though, but again it'd be nice if I could figure out exactly what the phone is doing when it's "super-lagging".
Eckyx said:
Well, what if it's something as simple as the governor I'm using or an undervolt setting? I'll probably flash back to your kernel though, but again it'd be nice if I could figure out exactly what the phone is doing when it's "super-lagging".
Click to expand...
Click to collapse
If you're undervolting when this issue is happening, change it back to regular voltage.
I can attest to the slow downs and the screen lock ups. I have been using Tasks kernel for the past week and a half. Going back to try NEAK one last time. If it gives the same results I'll have to give up on it. I don't under volt hardly at all by the way. Like maybe -25 per step so it isn't that, and when I first experienced the issue I tried Evey possible io scheduler / governor combo under the sun. All yielded same darn results.
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
I can attest to the slow downs and the screen lock ups. I have been using Tasks kernel for the past week and a half. Going back to try NEAK one last time. If it gives the same results I'll have to give up on it. I don't under volt hardly at all by the way. Like maybe -25 per step so it isn't that, and when I first experienced the issue I tried Evey possible io scheduler / governor combo under the sun. All yielded same darn results.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
+1, my problem was with typing as well. Stock voltages, several kernels.
Sent from my Galaxy S2
Simba501 said:
+1, my problem was with typing as well. Stock voltages, several kernels.
Sent from my Galaxy S2
Click to expand...
Click to collapse
I've only used Task's (CM9) kernel and NEAK, and I haven't yet experienced any slowdowns with Task's, but I really have no idea what kind of optimizations his has, haven't found any information on it published so I can't say what's different between his and the NEAK kernel.
What kernels have you had problems on?
Eckyx said:
I've only used Task's (CM9) kernel and NEAK, and I haven't yet experienced any slowdowns with Task's, but I really have no idea what kind of optimizations his has, haven't found any information on it published so I can't say what's different between his and the NEAK kernel.
What kernels have you had problems on?
Click to expand...
Click to collapse
Stock & Siyah. My issue with it wasn't major; it just isn't as polished as GB. The difference is noticeable.
Sent from my Galaxy S2
When mine gets laggy, I usually pull out the battery and put it back after 10 min or so. If you are leaving the phone on more than 2-3 days at a time, that could really hurt the memory and phone performance. The phone usually runs on 300 mb but it will run about 700mb ram after 3 days (even force closing everything).
It is not mentioned so I just wanted to cover all bases
After posting about giving NEAK another try, I did. And within 10 minutes got an extreme lag slow down while typing. Didn't touch any settings kernel side. So I flashed siyah kernel and so far no problems. Sux too. I liked NEAK.
Sent from my SGH-I777 using xda premium
I have been running Siyah with Task's AOKP and have had zero lag and great battery. No UV or OC.
Sent from my SGH-I777 using xda premium
Posted this in NEAK thread but also posting it here:
I just installed the new AOKP, used kernel clean script and installed NEAK 2.0.5x, then went into the NEAK Pro config and changed my governor to Conservative and sched to SIO. Rebooted, opened Scramble with Friends and immediately got superlag.
Turning off the screen and waiting 20-30 seconds fixes it (long enough for the phone to go to sleep), but nothing else short of a reboot will help. I can leave it like that for an hour (if I don't let it sleep) and it'll still be uberslow.
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.