Hello all,
I have a brand new A500 which I've rooted and installed HoneyVillian 1.1 on (Honeycomb 3.2). While I can overclock it to 1.2ghz and run basically any apps all day long, as soon as I try to push it to 1.5ghz (which is readily attainable by most) the device panics and reboots continuously.
Having had an Android smartphone for a couple years, I know the panic and reboot condition is most likely caused by too low voltage for the desired clockspeed. In this case, I noticed that in the HoneyVillian screen caps, the voltage for 1500mhz is 1325mV, however, when I go into SetCPU I see that my setting for 1500mhz is just 1250mV.
Can others please confirm whether or not they are running 1500mhz at 1325mV or at the 1250mV my ROM came stock with?
What are your experiences with 1.5ghz and what is your voltage setting?
Thanks a lot!
Hi, wrong section. Should be in the General or Q&A section as this post has nothing to do with development.
I have mine running at 1.5GHz with no problems on stock 1250mV. Never got into UVing yet and still need to learn of its benefits. Running Taboonay 2.0 with the Taboonay Kernel at 1.5GHz max and 216MHz min with the Ondemand governor.
Moved to Q&A
odd
Guess I am lucky - can run @ 1646 MHz *mostly* stable, occasional fc. Run 1504 normally - solid as a rock.
both running Taboonay?
autom8r said:
both running Taboonay?
Click to expand...
Click to collapse
Stock 3.1, Taboonay kernel. Usually stick at 1.4 for battery life/stability/speed 1.4 ghz = 1225 mv via set CPU on my stock setup. Hope that helps. 1.64 tops out at 1400 mv
Im running honeyvillain 1.1 rom with cwm recovery installed and all the kernel and normal addons that come with honeyvillain. I run with setcpu at 1.65 all the time and never had an issue.
One thing that you may want to do is make sure your recovery image is proper. I know this may sound odd, but mine gave me so many troubles until I setup a new one.
Related
Ok after bricking one phone, i got a new one and loaded voodoo and dirkks SV1200 kernal. also oc'd to 1200. everything has been perfect and had scores in the 18 or 1900s. this morning i was using my phone and noticed it was very laggy. i checked quadrant scores again and it scored in the 14's. as i ran the benchmark, i noticed it hangs on the I/O 3of4 for longer then usual. i have restarted the phone, no luck. even reflashed the kernal, no luck. I cant think of any new programs or changes to the phone. any ideas?
Jeff5886 said:
Ok after bricking one phone, i got a new one and loaded voodoo and dirkks SV1200 kernal. also oc'd to 1200. everything has been perfect and had scores in the 18 or 1900s. this morning i was using my phone and noticed it was very laggy. i checked quadrant scores again and it scored in the 14's. as i ran the benchmark, i noticed it hangs on the I/O 3of4 for longer then usual. i have restarted the phone, no luck. even reflashed the kernal, no luck. I cant think of any new programs or changes to the phone. any ideas?
Click to expand...
Click to collapse
Well the 3rd I/O test does take the longest to complete. If you are having I/O issues this certainly would give you a fluctuating Quadrant score since so much is I/O affected especially on a voodoo'd SF. Have your other benchmarks taken a dip as well? Does the phone lag in regular use? If its just a Quadrant issue I would not overly panic. Cross check with other benches
My phone did that with voodoo too, I installed dirrks lv 1200, and when I upgraded it started acting up. I did remove the fix before I updated, did everything right, but it still lagged so I just glassed back to stock and did all the steps for remove lagfix. Still on stock kernel now but will install birdman optimized tonight.
Adrynalyne is the man BTW. Ok, as to the OP, have you reset the CPU in SetCPU after you restart your phone? If I don't, I get a score of 1400 ish too.
that would make sense as I believe it resets to 800 instead of 1200
thestigwins said:
that would make sense as I believe it resets to 800 instead of 1200
Click to expand...
Click to collapse
Yes, it resets to 800. 1.2 ghz is nice, I would like to see 1.6. G2 OC'ed at 1450 I believe... Ugh, one day, one day.
No luck with OC kernels
I have tried a few, everytime I get issues. Seems like setcpu just does not play well with this phone. I get 1800 on stock voodoo .2. Don't see a need for the extra conservative 200mhz that an OC can provide. Good luck with the kernels though.
Anyways, as stated, make sure set CPU is set to 1.2 GHz and not 800 MHz which is where it defaults. I use the widgit and crank up the speed any time I'm using the phone, else, I leave it at 800 when charging / idle etc.
Also, go into System Panel (best app killer around) and do an END ALL - it will kill everything... THAN run quadrant. If your scores skyrocket, don't be alarmed. Quadrant likes to have a very clean system to run on, if you have a lot of cached or running applications, Quadrant seems to suffer, I'm assuming due to the delay between it requesting more RAM from Android and the time it takes for it to release it. Seems to make sense as to why it would slow down to me at least based on what I know about how Android handles RAM.
Just make sure to reboot your phone after to restore your normal app library of running apps.
With a 1.2 GHz overclock on jt's voodoo kernel most of us are/were getting about 1925 . I've not ran dirrk's LV kernel, the undervolting is very minimal and I'd rather error on the side of stability, YMMV.
Accused: Everyone flaming & veering off-topic (You know who you are)
Charge: Violation of XDA Anti Spamming, Trolling & Flaming Rules
Verdict: GUILTY
Resolution: All violating posts have been deleted
Warning: Further transgressions might result in a BAN!
COURT'S ADJOURNED!
Helloooooo community!
I have a question...
I'm using HD2 with nand android and the rom
MDJ's CyanogenMod 7 v. 2.6
I installed the SetCPU and I managed to OC my device @ 1536MHz
I stess tested and it is stable, plus I'm using it for 2 days now!
stock temps after stress test: 33c
OC temps after stress test: 35-37c
My question is, is it safe to leave it as it is?
Cause according to temps, I don't think I have problem...
Also my profile is "On Demand"
Max: 1536MHz
Min: 245MHz
Thanks!
Hi,
From what I understand, on demand will not OC your CPU to 1.5 ghz, but use the CPU according to the performance it requires. If you use really intensive apps, CPU *might* go to 1.5 ghz, but it really just raises about as high as what's being used. I wouldn't recommend 1.5 ghz OC on your phone for a long term use. You never know what might happen.
Alot of people do it though, but my phone isn't stable at 1.2ghz so I'm not one of them.
I dont have enough posts, and im not going to post a bunch of useless replies to threads im not interested in to inflate my post count to 10 posts. However, since ive encountered a fairly bad bug with this kernel, I figured id mention it here and see if an "expert" user might be able to guide/teach me what im missing, OR post in the Samurai kernel thread so the devs know its a problem.
Running the samurai kernel included with ACS ICS 5.5 (Samurai 3.0.1), i setup Voltage Control to use the Noop scheduler and Conservative governor. I disabled everything beyond 1000Mhz (for max battery life), and it worked as expected (100-1000mhz depending on what im doing). After flashing 3.0.4, it would no longer go above 800mhz. I ensured the max frequency was set to 1000mhz, applied changes, saved as boot settings, etc, and upon reboot the phone INITIALLY goes up to 1000mhz, but then stops at 800mhz. I noticed in voltage control I couldnt undervolt anything above 800 (all other frequencies disabled). Flashing back to 3.0.1, everything worked as advertised with all frequencies working well. BTW, to test, I changed schedulers and even set the governor to Performance, which maxed the frequency at 800mhz still.
Just thought id let some people in here know- I LOVED how well the ram optimization worked in 3.0.4- it reliably kept my RAM at about 170mb, whereas my RAM would eventually end up in the 70s with other choices.
Love the ROMS, kernels, and all the hacks you guys do; just wanted to let everyone know I noticed this.
GSF1200S said:
I dont have enough posts, and im not going to post a bunch of useless replies to threads im not interested in to inflate my post count to 10 posts. However, since ive encountered a fairly bad bug with this kernel, I figured id mention it here and see if an "expert" user might be able to guide/teach me what im missing, OR post in the Samurai kernel thread so the devs know its a problem.
Running the samurai kernel included with ACS ICS 5.5 (Samurai 3.0.1), i setup Voltage Control to use the Noop scheduler and Conservative governor. I disabled everything beyond 1000Mhz (for max battery life), and it worked as expected (100-1000mhz depending on what im doing). After flashing 3.0.4, it would no longer go above 800mhz. I ensured the max frequency was set to 1000mhz, applied changes, saved as boot settings, etc, and upon reboot the phone INITIALLY goes up to 1000mhz, but then stops at 800mhz. I noticed in voltage control I couldnt undervolt anything above 800 (all other frequencies disabled). Flashing back to 3.0.1, everything worked as advertised with all frequencies working well. BTW, to test, I changed schedulers and even set the governor to Performance, which maxed the frequency at 800mhz still.
Just thought id let some people in here know- I LOVED how well the ram optimization worked in 3.0.4- it reliably kept my RAM at about 170mb, whereas my RAM would eventually end up in the 70s with other choices.
Love the ROMS, kernels, and all the hacks you guys do; just wanted to let everyone know I noticed this.
Click to expand...
Click to collapse
Did you try reflashing fresh? I'm currently runnin CK23's Urban Precision 1.1 with Samurai 3.0.4 and I'm OC'd to 1400/200. I honestly don't kno why its not working for you, I'll be sure ta mention it in the thread tho.
Sent from a Epic like no other usin XDA Premium....
Did you reflash your ROM fresh and put on the kernel immediately like Earthbound recommended?
kennyglass123 said:
Did you reflash your ROM fresh and put on the kernel immediately like Earthbound recommended?
Click to expand...
Click to collapse
Yes, Ive done it a third time just to make sure; 100% reproducible with 3.0.4. The first 2 times I booted ACS ICS 5.5 FIRST, then booted back into CWM to flash the kernel. This last time, I flashed the ROM, then flashed the kernel immediately after. Same result. I guess its just my device? Ive never had issues with this before, so..
Did you clear data in Voltage Control? Perhaps it's your governor.
What CPU speed and voltage suits you the best?
-100mv on all clocks, 1.2ghz max. No lag.
See sig.
I am currently tsvz111 der Kernel Trinity at 1400 and I am not very undervolted. I highly recommend Trinity - if you want more power get a96 which is 1600 max i believe. a96 and other builds might max at 1700 I forget which. Also the inexpensive Trinity Tool kit app.
I was coming to ask what stock voltages are because I have reboots when too under voltage.
MrSchroeder said:
I am currently tsvz111 der Kernel Trinity at 1400 and I am not very undervolted. I highly recommend Trinity - if you want more power get a96 which is 1600 max i believe. a96 and other builds might max at 1700 I forget which. Also the inexpensive Trinity Tool kit app.
I was coming to ask what stock voltages are because I have reboots when too under voltage.
Click to expand...
Click to collapse
Refer to the system tuner app for recommended voltages
here's a question. I am running trinity a96 i believe; and I'm trying to keep my device running at minimum 500mhz up to 1.5ghz. However, everytime I turn the device off and back on, it goes back to stock clock speeds. Anyone know how to fix this?
MRsf27 said:
here's a question. I am running trinity a96 i believe; and I'm trying to keep my device running at minimum 500mhz up to 1.5ghz. However, everytime I turn the device off and back on, it goes back to stock clock speeds. Anyone know how to fix this?
Click to expand...
Click to collapse
Sometimes the tegra 3 has a mind of its own. I had that problem with every kernel I tried before giving up. What you can do is set an init.d script to set the clock speeds
But I have Faux's 009es kernel, which comes at 1.2GHz and I have just left it. Tegra 3 does a good enough job at handling performance by itself imo
Hi there,
I want to get the most performance out of my old galaxy s but i have a slight problem with 4.4.
I came from Slimbean android 4.3 on 1.2ghz because it worked really slow and gave me alot of problems.
I first flashed (After full wipe) to Mackay 4.4 rom but whatever govenor or sheduler i am using it crashes everytime after a minute or so doing some simple tasks from the slightest overclock (1.1 ghz).
So i flashed to CyanAOSP (full wipe) to see if it would fix the problem but the problem still exist on this rom :c
Is there something wrong with my device?
Greetings,
- Merlin
Taking the phone to pieces and applying thermal compound to the chips gave me another 100Mhz. (rock solid at 1200Mhz when 3D gaming etc). There are 2 chips underneath the motherboard, and if you remove the sim tray from the board there are another few under there. I did them all. Be very careful if you're using Arctic Silver. I would have preferred to use the cheap white stuff but I didn't have any. There is a thread if you search for it with instructions on how to do this if you need it.
And with overclocking there's an element of luck. There are variations in the manufacturing of the chips themselves which can make your particular phone good (or useless) for overclocking.
Sent from my GT-I9000 using Tapatalk
knuckles1978 said:
Taking the phone to pieces and applying thermal compound to the chips gave me another 100Mhz. (rock solid at 1200Mhz when 3D gaming etc). There are 2 chips underneath the motherboard, and if you remove the sim tray from the board there are another few under there. I did them all. Be very careful if you're using Arctic Silver. I would have preferred to use the cheap white stuff but I didn't have any. There is a thread if you search for it with instructions on how to do this if you need it.
And with overclocking there's an element of luck. There are variations in the manufacturing of the chips themselves which can make your particular phone good (or useless) for overclocking.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
But why could it do 1.3 ghz on android 4.3 easily? I think it has nothing to do with heat atm.
Because sometimes i can run antutu for 2 times in a row before it crashes. But sometimes it crashes instantly when i press the start button.
MerlijnD said:
But why could it do 1.3 ghz on android 4.3 easily? I think it has nothing to do with heat atm.
Because sometimes i can run antutu for 2 times in a row before it crashes. But sometimes it crashes instantly when i press the start button.
Click to expand...
Click to collapse
It's kernel related issues. I managed to clock in at 1.6Ghz rock stable on CM 10.2 but likewise, a 1.2Ghz overclock on 4.4 is giving me very rear soft reboots
MrAndroid12 said:
It's kernel related issues. I managed to clock in at 1.6Ghz rock stable on CM 10.2 but likewise, a 1.2Ghz overclock on 4.4 is giving me very rear soft reboots
Click to expand...
Click to collapse
Ah ok now that i know that, its probably going to get fixed sooner or later
Interesting. Mine is stable at 1.2Ghz on 4.4, so I'll be trying to push it a bit more when I get new kernels. I put Arctic Silver on all the chips the other day, even the ones under the sim card tray so hopefully that will help it. It has defo done something because my phone was unstable at 1.2Ghz before I did it.
Sent from my GT-I9000 using Tapatalk
knuckles1978 said:
Interesting. Mine is stable at 1.2Ghz on 4.4, so I'll be trying to push it a bit more when I get new kernels. I put Arctic Silver on all the chips the other day, even the ones under the sim card tray so hopefully that will help it. It has defo done something because my phone was unstable at 1.2Ghz before I did it.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I just flashed to semaphore kernel on mackay rom and it is fully stable on 1.3 ghz atm.
Is there a 4.4 semaphore kernel?
Sent from my GT-I9000 using Tapatalk
Guys , every kernel has its own custom voltages for over clocking . just use an app that controls the voltage (you can find one in play store ) and increase the voltage step by step until your phone is stable. For example : on Mackay I can't over clock not even to 1100 MHz with stock voltages without the phone rebooting after a few seconds but on Semaphore I can oc with stock voltages up to 1200MHz and its stable . on Mackay I messed around with higher voltages until I found the ones that my phone is happy with and I could oc up to 1300 MHz stable after that.
knuckles1978 said:
Is there a 4.4 semaphore kernel?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Yes there is , check the Semaphore thread for 3.4.0
Sent from my GT-I9000 using Tapatalk
I didn't realise that voltages were set in a kernel. Thanks
Do you know what voltages I should be using for a 1300 or 1400 overclock? I'm sitting stable at 1200 at the moment, how much do you think I should raise the voltage to keep it stable with another 100 or 200 MHz increase?
Edit: I'll try the 4.4 semaphore kernel
Sent from my GT-I9000 using Tapatalk
I personally use these settings:
Frequency - CPU - Int
1000MHz - 1225 - 1100
1200MHz - 1300 - 1100
1300MHz - 1350 - 1100
1400MHz - I've never got stable 1400MHz OC :/ (I think 1400 1150 should be right for most devices)
Optional:
1100MHz - 1250 - 1100 (some kernels have this step)
Thanks again, that's me running rock stable even under gaming at 1.3Ghz. Not tried 1.4.......yet lol
Why is there two voltage values you gave for each clock speed though?
I used setcpu, and set the first value. I'm not sure what the other value you gave is? GPU voltage?? Thx
knuckles1978 said:
Thanks again, that's me running rock stable even under gaming at 1.3Ghz. Not tried 1.4.......yet lol
Why is there two voltage values you gave for each clock speed though?
I used setcpu, and set the first value. I'm not sure what the other value you gave is? GPU voltage?? Thx
Click to expand...
Click to collapse
Second value is internal voltage (mostly used with LiveOC to stabilize as it gives voltage to GPU and RAM). With normal OC it should be at stock (1100mV). Some apps, like NSTools gives you opportunity to change those.
Normal OC affects CPU, and liveOC CPU, GPU, RAM, so it's more likely to be unstable. I can't reach 1100 on LiveOC, but on normal I have 1300 easily.
midnight911 said:
Second value is internal voltage (mostly used with LiveOC to stabilize as it gives voltage to GPU and RAM). With normal OC it should be at stock (1100mV). Some apps, like NSTools gives you opportunity to change those.
Normal OC affects CPU, and liveOC CPU, GPU, RAM, so it's more likely to be unstable. I can't reach 1100 on LiveOC, but on normal I have 1300 easily.
Click to expand...
Click to collapse
Ah well i am using stock voltages from semaphore kernel and 130% live oc. It is fully stable atm.
MerlijnD said:
Ah well i am using stock voltages from semaphore kernel and 130% live oc. It is fully stable atm.
Click to expand...
Click to collapse
Heh there are no two same devices. One overclocks better and one at all. There are devices which can't be overclocked. It's just luck you have with your hardware.