A couple weeks ago, I flashed the stock 2.3.6 rom using Mobile Odin Pro to retain root. Immediately afterward, I used CWM to flash Entropy's DD kernel. Then I did some undervolting with SetCPU. These are the voltages I have set right now:
1200 - 1175mv
1000 - 1100mv
800 - 1050mv
500 - 950mv
200 - 850mv
They're well within the suggested minimums from several threads.
Anyway, my phone has been freezing about once a day since then. It always happens the same way: the screen and capacitive buttons become unresponsive, and after a few seconds the phone reboots. Could the undervolting be causing it? Is there something else you guys can think of that might be causing it?
EDIT: Also, every time this happens, I lose quite a bit of battery charge. Like, if my battery was at 50% before the reboot, it'll be somewhere around 10% afterwards. Is that normal? I've attached a screenshot.
raptor102888 said:
A couple weeks ago, I flashed the stock 2.3.6 rom using Mobile Odin Pro to retain root. Immediately afterward, I used CWM to flash Entropy's DD kernel. Then I did some undervolting with SetCPU. These are the voltages I have set right now:
1200 - 1175mv
1000 - 1100mv
800 - 1050mv
500 - 950mv
200 - 850
They're well within the suggested minimums from several threads.
Anyway, my phone has been freezing about once a day since then. It always happens the same way: the screen and capacitive buttons become unresponsive, and after a few seconds the phone reboots. Could the undervolting be causing it? Is there something else you guys can think of that might be causing it?
Click to expand...
Click to collapse
Have you set the voltages back to stock for a few days and seen if the freezing stops? That would be the first thing I would try Not all chips can handle the oc/uv
yoderk said:
Have you set the voltages back to stock for a few days and seen if the freezing stops? That would be the first thing I would try Not all chips can handle the oc/uv
Click to expand...
Click to collapse
What do you mean about not all chips being able to handle it? Do you mean there is variation among different i777 devices? Or variation among different types of phones? Because the latter is obvious...
raptor102888 said:
What do you mean about not all chips being able to handle it? Do you mean there is variation among different i777 devices? Or variation among different types of phones? Because the latter is obvious...
Click to expand...
Click to collapse
WHY DO YOU THINK THE DEVICE WASN'T SOLD WITH THESE VOLTAGES? What part of "every device is different" didn't you understand? What part of:
USE AT YOUR OWN RISK. DO NOT REPORT BUGS OR PROBLEMS IF YOU ARE OVERCLOCKING OR UNDERVOLTING. IF YOU EXPERIENCE ANY STABILITY PROBLEMS, DISABLE ALL OC/UV in BIG GIANT RED LETTERS in one of the first four posts of my kernel thread didn't you understand?
I have ZERO tolerance for someone who flashes **** and clearly didn't even bother reading ANY part of the thread.
raptor102888 said:
What do you mean about not all chips being able to handle it? Do you mean there is variation among different i777 devices? Or variation among different types of phones? Because the latter is obvious...
Click to expand...
Click to collapse
Well if you would read a little (as entropy clearly stated) not all chips are the same, some can handle oc/uv and some can't. Seems like you are one of the ones that can't.
Sent from my SAMSUNG-SGH-I777 using xda premium
Wow, ok. I understood the risks to undervolting, and I realize I'll probably have to stop doing it. I was just hoping that this problem could be from some other cause so I wouldn't have to.
By the way, I read your entire thread, all 109 pages of it, before I flashed.
Sorry for being a noob guys. Go ahead and close this thread I guess.
Sent from my SAMSUNG-SGH-I777 using xda premium
You know, its posts like this that make Entropy rage and not want to help members or post his awesome kernels.
I think we should make some stipulations that users cant download attachments until they hit 25 posts, that way they have been around long enough to know how to read and search.
Related
Im using voltage control on ICS 4.0.3 Im not overclocked, anyone done any experimentation with the UV settings? Im wondering how low i can go without causing a reboot. Let me know what settings you are all using. If it helps Im using Nelsons new kernal. Thanks everyone!
I guess you could try the chart on glitch kernels thread.
Though it might be completely different since diff kernel but you can use it as a guideline
remember to check off set on boot when messing with voltages and only set on boot after you test for like a day without issue
trailblazerz11 said:
I guess you could try the chart on glitch kernels thread.
Though it might be completely different since diff kernel but you can use it as a guideline
remember to check off set on boot when messing with voltages and only set on boot after you test for like a day without issue
Click to expand...
Click to collapse
Thanks will do!
Sent from my SGH-T959 using XDA App
Each vibrant cpu is different. Thats why some can overclock to 1.7 and others cant OC at all.
Back it off a bit and run it while a while - if its good try a little more.
As mentioned above, all vibrant are different so there is no copy/paste answer to this.
However, I will tell you what my settings are, and maybe they can serve as a starting point for your own experimentation.
1000 -50 (sometimes 25 depending on the rom/kernel)
800 -75
400 -125
200 -150
100 -175
Try different settings out, a day at a time...if you make it through a day with no freezes/ reboots....maybe try 25 lower. if you experience a freeze, try locating the problem setting and increasing it. Good luck
Xenoism said:
As mentioned above, all vibrant are different so there is no copy/paste answer to this.
However, I will tell you what my settings are, and maybe they can serve as a starting point for your own experimentation.
1000 -50 (sometimes 25 depending on the rom/kernel)
800 -75
400 -125
200 -150
100 -175
Try different settings out, a day at a time...if you make it through a day with no freezes/ reboots....maybe try 25 lower. if you experience a freeze, try locating the problem setting and increasing it. Good luck
Click to expand...
Click to collapse
Thank you, a starting point is exactly what I was looking for. My phone does overclock to 1.4 without issue, but I never run it that high.
Sent from my SGH-T959 using XDA App
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
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.
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Lootzifer said:
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Click to expand...
Click to collapse
You need a kernel that is capable of overclocking. If you look through the Development thread, you can find one to do so.
Lootzifer said:
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Click to expand...
Click to collapse
youll wanna find the devil kernel in development
Lootzifer said:
Im running a fascinate with cm10 nightly, stock kernel. I was hoping to overclock cpu to 1200 mhz, and I can't figure out a way to do it. I tried changing the gorverner, but they're all capped at 1000 mhz. What can I do?
Click to expand...
Click to collapse
download devil 1.6.1 for fascinate
Newest is 1.7.4 actually, get it from http://rootaxbox.no-ip.org/derteufel/Helly_Bean/kernel/
Crawshayi said:
Newest is 1.7.4 actually, get it from http://rootaxbox.no-ip.org/derteufel/Helly_Bean/kernel/
Click to expand...
Click to collapse
Yeah, but at the time I didn't realize he made a new folder for 1.7., so I looked but all I found was 1.6.1.. but at least, 1.6.1 won't screw your Rom if you have an old partition (current being nightly cm10)--I learned that the hard way.
Sent from my Nexus 7 using xda app-developers app
Actually 1.6.1 was for the newer partition layout I think the last one he made for the old one was 1.5.4 or something. Anyway, he just released 1.7.5 last night, grab it from http://rootaxbox.no-ip.org/derteufel/jellybean/175/ :good::good:
im using the 1.7.5 release on LagFree
i dont want to overclock it tho because idk if it would mess up my phone .
Crawshayi said:
Actually 1.6.1 was for the newer partition layout I think the last one he made for the old one was 1.5.4 or something. Anyway, he just released 1.7.5 last night, grab it from http://rootaxbox.no-ip.org/derteufel/jellybean/175/ :good::good:
Click to expand...
Click to collapse
[er, I kinda meant to say "if you have the new partition layout," not old..]
but well...... :S I was right and wrong, because the old partition layout [with /datadata] is technically the "old" layout [the one that everybody always had], until for some reason they decided to move it around, so that you only had 400MB for apps, which I quickly ran out of after restoring my TiBu apps...and then they finally came around and put /datdata back, so theoretically it's the "new" layout, but..well yeah, hopefully you know what I mean.
mvmacd said:
[er, I kinda meant to say "if you have the new partition layout," not old..]
but well...... :S I was right and wrong, because the old partition layout [with /datadata] is technically the "old" layout [the one that everybody always had], until for some reason they decided to move it around, so that you only had 400MB for apps, which I quickly ran out of after restoring my TiBu apps...and then they finally came around and put /datdata back, so theoretically it's the "new" layout, but..well yeah, hopefully you know what I mean.
Click to expand...
Click to collapse
The reason it was moved around and suddenly you only had around 400MB was because the Fassy has 2 chips, 1 is fast as hell and the other is slow. Problem was, the fast chip only had so much storage space, so that was the trade off, good performance but poor storage space. For the newest layout, Jt didn't simply just 'put back' /datadata, the new layout actually is a completely new arrangement that gives us the fast speed AND storage space. If you want to read about it go over to the CM10 thread on Rootzwiki, Jt explained what he did. What this means in practical terms is that we now have a device with good speed and storage space that can handle the newer Android OSes :good:
whats the worst that can happen if you overclock ?
AndroidGee209 said:
whats the worst that can happen if you overclock ?
Click to expand...
Click to collapse
Short term: Glitchy behavior (freezing/crashing/etc) and random reboots (this is more likely if you're doing Live OC versus just bumping up your CPU MHz)
Long term: Shortened device lifetime due to component stress; in other words if you plan to use your phone for a very long time don't overclock
Not all phones react the same way to overclocking, you might not get the same results as others are. For example, a lot of people seem to have good luck with 110% Live OC, however I can only get 105% on my phone before it becomes unstable.
Crawshayi said:
The reason it was moved around and suddenly you only had around 400MB was because the Fassy has 2 chips, 1 is fast as hell and the other is slow. Problem was, the fast chip only had so much storage space, so that was the trade off, good performance but poor storage space. For the newest layout, Jt didn't simply just 'put back' /datadata, the new layout actually is a completely new arrangement that gives us the fast speed AND storage space. If you want to read about it go over to the CM10 thread on Rootzwiki, Jt explained what he did. What this means in practical terms is that we now have a device with good speed and storage space that can handle the newer Android OSes :good:
Click to expand...
Click to collapse
Exactly
AndroidGee209 said:
whats the worst that can happen if you overclock ?
Click to expand...
Click to collapse
You remember that Mayan end of the World thing...
Crawshayi said:
Short term: Glitchy behavior (freezing/crashing/etc) and random reboots (this is more likely if you're doing Live OC versus just bumping up your CPU MHz)
Long term: Shortened device lifetime due to component stress; in other words if you plan to use your phone for a very long time don't overclock
Not all phones react the same way to overclocking, you might not get the same results as others are. For example, a lot of people seem to have good luck with 110% Live OC, however I can only get 105% on my phone before it becomes unstable.
Click to expand...
Click to collapse
Again, exactly...
Yep I accidently at my OC too high once and I got an immediate reboot, setting itself back to std
Sent from my swagger
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.