Did any of you used to be able to OC and/or UV with no problems, even at 1500MHz, but now are unable to get the same performance out of your g2x?
Mine did. When I first started flashing on this phone, I was able to run oc/uv kernals at 1500MHz, and even uv the lower end an additional -50 beyond what the kernal is already undervolted at...and run back to back smartbenches with no problems...but now, any attempt to uv leads me to forced reboots, and any attempt to clock higher than 1200 does the same. I've tried every rom and kernal on this site. I wonder if I damaged my phone with the high oc early on.
Related
If I've found a combination of rom/kernal/voltage that's stable for me to run at 1500MHz, is it safe to run that way full-time? I mean, I would still use profiles in setcpu for in-call and screen-off...but would this damage my phone? I do keep the phone in a case, if that has any bearings. I can feel it considerably warmer when I oc it than when I leave it at 1GHz.
what kernel do you use? the new trinity kernel doesnt scale and stays up at 1500 100% of the time, i havent had any problems with heat using 1500 on other kernels, i have a profile to underclcok if over 40C but never kicks in while running faux's kernel and screen off underclock, long term a constant temperature of 40C plus would damage the phone as heat damages any electronics.
I'm running faux's froyo kernal. I have setcpu profiles setup for:
in-call 500/400
screen-off 500/400
and now I just added temp>40c (following your lead) 1000/400
I have 1300mV set for 1500MHz and 950mV set for 1000Mhz...and I believe it's 770 for 400MHz. If I understood Faux correctly, that's already -50 undervolted.
Is there a recommended app for monitoring cpu temp?
just set set cpu notification for your temp profile itll beeep if you go over 40, you could test if you can go an extra -25 it worked on my device any higher it reboots, in my case -25 extra is perfectly stable. i think also , setcpu has a widget you can place on your screen that shows temperature and cpu frequency
if you try to see if your proc can handle an extra -25 i would recomend you take the set at boot option off or you could get stuck in a reboot loop till you restore from clockwork.
Is there any particular reason the second core always drops down to 216mhz? This happens with any custom kernel I run, currently running moray with electra kernel at 1.5Ghz using pimp my cpy to OC.
ggrammer said:
Is there any particular reason the second core always drops down to 216mhz? This happens with any custom kernel I run, currently running moray with electra kernel at 1.5Ghz using pimp my cpy to OC.
Click to expand...
Click to collapse
when it's needed, it goes to the required frequency...
sounds reasonable but I will notice some lag and stuttering while I am using the xoom, i will open os monitor and the second core is sitting at 216, i move it manually to 1.5Ghz and the tablet is more responsive...
Edit
Sorry I should have been more specific about the situation. When I say the 2nd core drops to 216 I mean the max frequency drops to 216 so the 2nd core does not clock up any higher unless I manually intervene.
same on my xoom with tiamat 2.2.2 and setcpu. i have two profles , screen off with 216-456mhz and other with 216-1200mhz. only the first score is over clocked after switched on, the second stucks at 216-456mhz. i contacted the developer of setcpu someting around 2 weeks a go, but no solution till now.
okay i see wat u mean...i just checked and i'm getting the same results... it sits on the min freq, all laggy, then when i manually set the frequency, it's super responsive like it shud.... i'm over-clocking to 1.6 btw
burgi400 said:
same on my xoom with tiamat 2.2.2 and setcpu. i have two profles , screen off with 216-456mhz and other with 216-1200mhz. only the first score is over clocked after switched on, the second stucks at 216-456mhz. i contacted the developer of setcpu someting around 2 weeks a go, but no solution till now.
Click to expand...
Click to collapse
I don't think that it strictly a SetCPU problem. I also have an Advent Vega and have used SetCPU to overclock it. Had almost the same problem, except both cores were stuck at 216Mhz.
Tried multiple overclocking apps and have had the same problem with all of them. Device fine until it goes into sleep mode, CPU stuck at 216Mhz when brought out of sleep. Even setting the minimum setting to 456Mhz still resulted in the CPU being stuck at 216Mhz on wakeup.
so i guess the big question is whether it is the kernels (I've tried a few) or in the way these apps OC a dualcore processor...It makes me wonder about the OC apps though, they were all built for single core originally and in each of them you only set 1 max and 1 min speed. OS monitor is the only app that displays both cores, at least that I have used, but it doesn't set an OC value at boot. Maybe if one of the smart devs on here could comment maybe even just to shed some light on this
Is there no solution to this issue yet?
Is it a tegra fault/problem?
Is it a Kernel issue?
Would flashing back to a stock kernel fix it? (if that is even possible...)
So overclocking cm7 to 1600 doesnt work and causes boot loops, i have been trying to get a kernel that would do it and i cant find one.
anyone know any kernels that work?
Only kernal for cm7 is the one that is with it no other kernals are compatible as for 1600 some phones run fine at 1600 others don't just depends on your CPU in your phone
Sent from my SGH-I997 using xda premium
^^^ what he said ^^^
my cappy was maginally stable @ 1300 within a very narrow voltage range. my infuse runs 100% @ 1664 with a ton of uv untill i turn on gps and everything starts to get warm. every cpu is different.
most infuses seem to be a higher test cpu than galaxy s phones though. you may be able to run at 1500 or better if you take a lot of time and figure out what the cpu likes and doesnt like. remember heat, uv and rapid voltage change can all cause instability so too much uv can cause problems as well as too little! to get maximum speed you may want keep the top few freq's at the same voltage (not the same uv but the same actual voltage) and have zero uv on the low freq's. it can be a pain to figure it all out but when you see the benchmarks you may think it was worth it.
ok well i kinda messed around with the overclocking built in and was messing with the type of governors and userspace seems to support over clocking on 1600.
really weird but my phone hasnt done the boot loop yet.
but thanks for your guy's help.
I set mine at 1600 last night via SetCPU. After 5 min it got hot and started boot looping. Its running good at 1200 now. I'm gonna bump it up little by little.
Good info, nice to know its "normal".
Honestly, the performance of CM7 outperforms all the other ROMS even running at 1.2GHz (IMO). I really don't see much of a performance increase by stepping up the clock speed, just a decrease in battery life, so it's not worth it to me.
ive talked to many people about this and most can only run at 1.4ghz even though 1.6ghz was stable in froyo. alot of people repeat "it depends on your specific chipset" but i dont buy that cop out. i think theres something wrong with the 1.6ghz setting in cm7.
Does anyone have any advice for OC and UV settings for the NS4G?
I would recommend Stock Voltage -25.
Claude
Uncheck the set at boot option before you mess with voltages, some phones don't like being undervolted so you may get a boot loop so with the set at boot option unchecked you will revert to stock volts if the phone freezes.
You can undervolt as much as you want as long as you get stability.
If you wanna over clock or live oc then you need to raise voltages.
Not all phones are the same
You have to understand that the phones response to undervolting is different for each handset. It depends on the production batch of the chips, the assembly and such things.
I installed the newest faux kernel, along with a stock ROM and the new UCLA radio. Seems to run fine. My main reason for putting on the FAUX kernel was battery life, as it's a scalable kernel.
So I downloaded SetCPU so I can take advantage of the under-clocking without using scripts. I chose on-demand, and it sets the high to 1728 and low to 192. My understanding is that a stock Skyrocket is runs at about 1.5. It runs nice and fast stock, so I tried to put the slider down to 1516, but it jumps back up to 1728.
Why will it not let me take advantage of maximum underclocking?
Bump.......