-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
[Verizon] What is a safe overclock? LTE
- Thread starter veccster
- Start date
-
- Tags
- galaxy nexus
pool_shark
Android Expert
It is safe, but each device is different as to how far they can go before becoming unstable.
I would also say that if you're experiencing a lag at 1.2, your problem probably isn't clock speed.
I would also say that if you're experiencing a lag at 1.2, your problem probably isn't clock speed.
veccster
Android Enthusiast
Thanks Pool. What is an UNSAFE overclock? I mean...what happens when you overclock a phone too much? Does it heat up? Will it fry the internals?
Anyway, I agree that 1.2 should be enough for my purposes. My lag was in opening apps, clicking on icons, opening the keyboard (and tons of keyboard lag with swype or swiftkey), opening the notification bar, scrolling through apps in drawer, etc. Very frustrating!
Last night I pulled the min CPU up to 729 and upped the max to 1305.
The phone seems much snappier. BUT....
...I made one other change that I think did the trick - I went from LeanKernal to FrancoKernal. I should also point out that I'm on AOKP Build 4. Maybe Franco is better suited.
Thanks Pool. What is an UNSAFE overclock? I mean...what happens when you overclock a phone too much? Does it heat up? Will it fry the internals?
Anyway, I agree that 1.2 should be enough for my purposes. My lag was in opening apps, clicking on icons, opening the keyboard (and tons of keyboard lag with swype or swiftkey), opening the notification bar, scrolling through apps in drawer, etc. Very frustrating!
Last night I pulled the min CPU up to 729 and upped the max to 1305.
The phone seems much snappier. BUT....
I should also point out that I'm on AOKP Build 4. Maybe Franco is better suited.
The faster you overclock your phone, the hotter it will become. The danger is that if you overclock too much it will fry the processor/memory. This is also something that voids the warranty/insurance, so if you fry it you will need to purchase a new phone.
pool_shark
Android Expert
People were over clocking their devices and getting up to 120 degrees with no issues.
What I was referring to when I said they can become unstable was some would freeze, or reboot where others were just fine. That's why I said each device was different.
I could over clock my droid X to 1.35 but if I went higher it would freeze and I had to do a battery pull, others went over 1.35 with no issues, but voltages also played a role.
What I was referring to when I said they can become unstable was some would freeze, or reboot where others were just fine. That's why I said each device was different.
I could over clock my droid X to 1.35 but if I went higher it would freeze and I had to do a battery pull, others went over 1.35 with no issues, but voltages also played a role.
Guys,
I've moved your thread over to the all-things-root sub-forum for ya.
Cheers!
I've moved your thread over to the all-things-root sub-forum for ya.
Cheers!
The advantage of a governor though, is that it UNDERCLOCKS the phone when demand is low. Phone cools, battery lives longer.
As stated, every single device responds differently to the same kernels and clock speeds.
Never set a frequency on boot until you are SURE your phone can handle it. Try a step up from 1.2 GHz and if your phone works well, step it up again and again until things start getting squirrelly. Then step it down again and that's your top speed.
As stated, every single device responds differently to the same kernels and clock speeds.
Never set a frequency on boot until you are SURE your phone can handle it. Try a step up from 1.2 GHz and if your phone works well, step it up again and again until things start getting squirrelly. Then step it down again and that's your top speed.
colchiro
Extreme Android User
You guys are chasing symptoms and ignoring the cause. 
I don't have lag on my GNex. Don't recall ever having it. I suspect battery life sucks too. See what's using your battery and you may find the lag.
O/w what rom are you running? What launcher? Where do you see the lag, everywhere or just certain apps? When did it start? What have you tried?
The GLaDOS kernel is pretty responsive. You might try that.
I don't have lag on my GNex. Don't recall ever having it. I suspect battery life sucks too. See what's using your battery and you may find the lag.
O/w what rom are you running? What launcher? Where do you see the lag, everywhere or just certain apps? When did it start? What have you tried?
The GLaDOS kernel is pretty responsive. You might try that.
veccster
Android Enthusiast
You guys are chasing symptoms and ignoring the cause.
I don't have lag on my GNex. Don't recall ever having it. I suspect battery life sucks too. See what's using your battery and you may find the lag.
O/w what rom are you running? What launcher? Where do you see the lag, everywhere or just certain apps? When did it start? What have you tried?
The GLaDOS kernel is pretty responsive. You might try that.
Thanks for the info. I am using AOKP Build 4 with the included Nova Launcher.
I switched to Franco Kernel overclocked to 1350 and it ran very smooth. Was killing my battery and I really needed my phone yesterday so I switched back to Leankernel. Big difference in battery life but i'm also not getting the lag I had before. Not sure what changed but it seems stable for now.
I was getting lag when scrolling through homescreens, scrolling through the app drawer, opening some apps, closing some apps. It just wasn't being very responsive.
I do watch CPU Spy and Better Battery and nothing seems to be hogging it.
colchiro
Extreme Android User
You may have some settings in Nova to keep the launcher in memory or other Nova settings under "Advanced", that may improve your experience. I use Apex launcher and leave "keep in memory" checked.
I mentioned the GLaDOS kernel, which I use, because it's a nice kernel for people that actually use their phone. (I don't match that demographic tho. My phone is idle most of the day.)
GLaDOS can be compared to having two speeds on your car, wide open or idle. The idea is that things complete quickly so you aren't at WOT for long and it doesn't get hot and gets pretty good battery. You need to use the wheatley governor that comes default with the kernel tho. I use GLaDOS because it has nice features I like like wake on screen touch (if within 300 seconds of screen off).
I mentioned the GLaDOS kernel, which I use, because it's a nice kernel for people that actually use their phone. (I don't match that demographic tho. My phone is idle most of the day.)
GLaDOS can be compared to having two speeds on your car, wide open or idle. The idea is that things complete quickly so you aren't at WOT for long and it doesn't get hot and gets pretty good battery. You need to use the wheatley governor that comes default with the kernel tho. I use GLaDOS because it has nice features I like like wake on screen touch (if within 300 seconds of screen off).
Thanks Pool. What is an UNSAFE overclock? I mean...what happens when you overclock a phone too much? Does it heat up? Will it fry the internals?
Anyway, I agree that 1.2 should be enough for my purposes. My lag was in opening apps, clicking on icons, opening the keyboard (and tons of keyboard lag with swype or swiftkey), opening the notification bar, scrolling through apps in drawer, etc. Very frustrating!
Last night I pulled the min CPU up to 729 and upped the max to 1305.
The phone seems much snappier. BUT....
I should also point out that I'm on AOKP Build 4. Maybe Franco is better suited.
I had lag on Franco kernel after a day of use. Switched to Lean and the problem went away. Use the interactive governor too. Don't both with the others. Jelly Bean is optimized for that governor.