In the past week have just rooted my inc2, flashed OMGB rom and Tiamat 1.1.0 kernel. I also loaded SetCPU from the market. I can't go over 1.036ghz without the phone locking up and having to do a battery pull. When the phone is back on I only have a few seconds to open SetCPU and lower the OC rate or the phone will lock again. I wiped cache/davlik cache before flashing kernel. What am I doing wrong? I have seen in the Tiamat thread in the development forum that people are going as high as 1.9ghz with out a problem. I would only like to get 1.2ghz to 1.3ghz because I read that this is a safe range. I do have have the governor set at Smartass. Thank you for your input.
scott7044 said:
In the past week have just rooted my inc2, flashed OMGB rom and Tiamat 1.1.0 kernel. I also loaded SetCPU from the market. I can't go over 1.036ghz without the phone locking up and having to do a battery pull. When the phone is back on I only have a few seconds to open SetCPU and lower the OC rate or the phone will lock again. I wiped cache/davlik cache before flashing kernel. What am I doing wrong? I have seen in the Tiamat thread in the development forum that people are going as high as 1.9ghz with out a problem. I would only like to get 1.2ghz to 1.3ghz because I read that this is a safe range. I do have have the governor set at Smartass. Thank you for your input.
Click to expand...
Click to collapse
Go back to the kernel thread look for the voltage table. The voltage levels are too low at the overclock levels, that what's causing your freeze ups. Use incredicontrol app from the market to adjust the voltage levels. You want to mirror the settings to match those of the previous version of the kernel
Sent from my Incredible 2 using Tapatalk
Thanks tnez, I found chads post about incredicontrol and sounded like it only worked on ver 1.0.4, will it work on ver 1.1.0 also.
How bad is this freezing for the phone? If I ever get really stuck will booting into recovery and reflashing omgb fix it or using the nandroid backup I created before flashing the kernel? Still new to all the rooting and custom roms and kernels, lots of fun but still have the fear of bricking the phone.
I'm fairly new myself but have been using SetCPU for a while. Make sure the "Set on Boot" option is unchecked until you find a setting that will work for your phone. As far as the nandroid, restore is your friend!! lol I've made many mistakes in the past that have totally locked up my phone and the restore option from recovery has saved me every time. There is always a chance that you can damage your phone but as time has gone by the devs have really made that possibility minimal
scott7044 said:
Thanks tnez, I found chads post about incredicontrol and sounded like it only worked on ver 1.0.4, will it work on ver 1.1.0 also.
How bad is this freezing for the phone? If I ever get really stuck will booting into recovery and reflashing omgb fix it or using the nandroid backup I created before flashing the kernel? Still new to all the rooting and custom roms and kernels, lots of fun but still have the fear of bricking the phone.
Click to expand...
Click to collapse
The app works on any kernel that supports adjustable voltages.
Both methods will work to undo things. Either restore or re flash the rom. But like stated above don't select the set on boot option until you find settings that work good on your phone.
Sent from my Incredible 2 using Tapatalk
Thanks again tnez, I installed incredicontrol and made the changes to the voltages so far so good. I have gone to 1.19ghz with no problems after the voltage changes. Is there app that can be used to test for stability or is just using the phone the way to test for stability.
scott7044 said:
Thanks again tnez, I installed incredicontrol and made the changes to the voltages so far so good. I have gone to 1.19ghz with no problems after the voltage changes. Is there app that can be used to test for stability or is just using the phone the way to test for stability.
Click to expand...
Click to collapse
You can do it by use....open up different apps very quick and switch between them...basically trying to over load the phone by making it multi task at a high level. set cpu also has a built in stress test under the info tab, run that for a few mins. I usually do the stress test for 3-5 mins followed by a quadrant test.
Sent from my Incredible 2 using Tapatalk
In regards to Tiamat, there have been a ton of people say that downgrading back to 1.0.4 Tiamat fixed the issue of the phone locking up when overclocked. If all else fails from what you have been recommended, try that!
TheMavic said:
In regards to Tiamat, there have been a ton of people say that downgrading back to 1.0.4 Tiamat fixed the issue of the phone locking up when overclocked. If all else fails from what you have been recommended, try that!
Click to expand...
Click to collapse
voltages just need to be changed and made to match 1.0.4 for the kernel to run like a champ
Sent from my Incredible 2 using Tapatalk
Related
I guess I'm under 10 posts so I could not post in his thread.
But I installed the rom and everything is awesome btw,
Now under his alternative kernels it has the Netarchy's agressive v7 kernel, I installed it, and if I put setcpu at 1.267 ghz my phone shuts off and reboots?
IS there a reason why?
Also it just went to its first reboot and it went into a bootloop?
K now it's not bootlooping but it starts up and after about 15 seconds it reboots.
EDIT: I flashed the stock kernel and its fine now, but I want to OC it just a little why is it doing that?
you cant overclock it above 1.1 as far as i know thats all the cpu is really capable of
r916 said:
K now it's not bootlooping but it starts up and after about 15 seconds it reboots.
EDIT: I flashed the stock kernel and its fine now, but I want to OC it just a little why is it doing that?
Click to expand...
Click to collapse
4g evo said:
you cant overclock it above 1.1 as far as i know thats all the cpu is really capable of
Click to expand...
Click to collapse
On this rom?
When I had the Evio 2 rom and stock kernel it would go to 1.228.
And on this one, 1.267 makes it reboot.
any kernels or Roms that i have had it would always loop above 1.1 your lucky that u got it to go that high how was it at that speed lol.
r916 said:
On this rom?
When I had the Evio 2 rom and stock kernel it would go to 1.228.
And on this one, 1.267 makes it reboot.
Click to expand...
Click to collapse
i was told that if you OC and start having bootloop scale back the OC until it gets stable again.
I got netarchy's 4.3.2 kernel and it's clocked to 1.228, wont go any higher since the incident.
From my understanding, no two phones are exactly alike and one phone will allow you to OC more than another. The most I ever OC to is 1.19 but I usually keep it at 1.15 and it is very stable. I've gone up to 1.267 and it still worked, but I only left it at that number for a few seconds and I never tried to go higher.
It's a crap shoot with overclocking. With different ROMs, Kernels and hardware in play, the results can be very different from one version to the next. This is the nature of overclocking. As mentioned in a previous post, you need to keep notching it back until it gets stable again.
Sent from my PC36100 using XDA App
cloak.n.dagger said:
It's a crap shoot with overclocking. With different ROMs, Kernels and hardware in play, the results can be very different from one version to the next. This is the nature of overclocking. As mentioned in a previous post, you need to keep notching it back until it gets stable again.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well it was hard to notch it back since I had set at boot checked and it was at 1.267, so I had to re flash the stock #15 htc kernel, and set it at 998 and then flash the new kernel and now it's at 1.228 and stable, and not to mention my battery is amazing.
I keep mine at 1.19 as well, I had it higher at one time, but there's not that much
improvement in performance for me to risk my phone boot looping while i'm asleep at
night.
BTW, Myn's ROM is really good but i've always use KK #9 BFS for it overclocker at 1.19
with no issues, no reboots, only secks.
This is stock ROM.
Every time I flash bacon bits to overclock my phone I always noticed that my screen flickers when I turn off the phone's screen or press the button to wake up.
Sometimes it just gets stuck and it stats flickering like crazy and I can't unlock my phone because of it.
This only happens when I OC my phone. When I wipe the phone it works fine but no OC which is what I want.
Any way to fix this issue?
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
dustrho said:
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
Click to expand...
Click to collapse
Actually I OC my phone, but it's still set on 806MHz so even at lower clockspeed it still flickers. It's bugging the hell out of me.
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
captainreynolds said:
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
Click to expand...
Click to collapse
Yeah, I have flashed all the kernels even pershoot's and it still flickers. I'm using the original ROM that came with the phone not the original one posted on the forums. Maybe if I use the one posted on the forums that will work?
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
captainreynolds said:
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
Well you know what I flashed an older version of pershoot mayeb I should try the newer one. I'll let you know what happens...
I had trouble flashing it with ROM Manager. Clockworkmod it. Here's the link to pershoots blog with the latest update links: http://droidbasement.com/db-blog/
Good luck!
Sent from my T-Mobile G2 using XDA Premium App
Just tried it and nope... it's still doing it maybe it's just my phone.
Bring it up in this thread:
http://forum.xda-developers.com/showthread.php?t=847672&page=103
Pershoot is always monitoring it along with a bunch of other smart devs. Maybe they'll have a better idea - don't give up hope!
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
pmcqueen said:
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
Click to expand...
Click to collapse
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
jjuice525 said:
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
Click to expand...
Click to collapse
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
pmcqueen said:
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
Click to expand...
Click to collapse
Actually, after installing Pershoot's most recent kernel, I have no problems. Maybe I just got lucky here.
I'm using the virus rom airborne rc6 and the netarchy 4.3.4 kernel. I went to the app market and downloaded the overclock widget since I had used it on another evo. Whenever I set it up or go to set it up I should say the phone locks up and requires a battery pull. Start the phone back up and it freezes again on the lock screen not allowing you to use it. A restore or wipe is required. I was thinking it was the Rom or kernel so I downloaded valpeak Rom and a kernel and it did the same thing on it. Just wondering if anyone had heard seen or experienced something like this before ? Is there another over clock program that's good and stable ?
Thanks in advance
Virus Rom airborne rc6
Netarchy toastmod kernel
jshaddix865 said:
I'm using the virus rom airborne rc6 and the netarchy 4.3.4 kernel. I went to the app market and downloaded the overclock widget since I had used it on another evo. Whenever I set it up or go to set it up I should say the phone locks up and requires a battery pull. Start the phone back up and it freezes again on the lock screen not allowing you to use it. A restore or wipe is required. I was thinking it was the Rom or kernel so I downloaded valpeak Rom and a kernel and it did the same thing on it. Just wondering if anyone had heard seen or experienced something like this before ? Is there another over clock program that's good and stable ?
Thanks in advance
Virus Rom airborne rc6
Netarchy toastmod kernel
Click to expand...
Click to collapse
You need to clock it at a lower maximum speed. Some chips can't handle overclocking as well as other chips can. My phone can only be overclocked to like 1.1, and anything over that, I have the same issues you are explaining. Set the maximum speed a little lower and see if that helps.
That's just it when I try to set it up it freezes. I contacted the developer of the app and they said its on my end. I used the valpak before and could clock to 1.2 I'm wondering if there isnt something wrong with the kernels lime maybe they did a software update on the app and it doesn't agree with Rom or kernel. I've heard good things about set cpu I may try it. Thanks for your help
jshaddix865 said:
That's just it when I try to set it up it freezes. I contacted the developer of the app and they said its on my end. I used the valpak before and could clock to 1.2 I'm wondering if there isnt something wrong with the kernels lime maybe they did a software update on the app and it doesn't agree with Rom or kernel. I've heard good things about set cpu I may try it. Thanks for your help
Click to expand...
Click to collapse
Yeah I know what you mean, you just gotta hurry and get into the app and lower the max speed before the app gets superuser permission and freezes again. Or if you have the SDK on your pc and know how to use adb, you could remove the app from the phone while connected to a pc in recovery. Also, I use setCPU, and I've had nothing but good experiences with it. I've never used Overclock widget so I can say anything about it.
try flashing a different kernel its happened to me before and thats what i had to do then i changed the max and flashed back to the other kernel
re
Leukay said:
Yeah I know what you mean, you just gotta hurry and get into the app and lower the max speed before the app gets superuser permission and freezes again. Or if you have the SDK on your pc and know how to use adb, you could remove the app from the phone while connected to a pc in recovery. Also, I use setCPU, and I've had nothing but good experiences with it. I've never used Overclock widget so I can say anything about it.
Click to expand...
Click to collapse
Thats how i fixed it. I ended up using the computer to remove the app and used setcpu. I normally dont care about the over clocking ability but the battery life sucks on the virus Rom. The roms great just crappy battery life. Thankfully that worked we will see if by underclocking it helps if not ill have to look for a different Rom. Thanks for your help man.
Hi guys,
I'm a bit of a noob so please bear with me. I recently rooted my phone (SGH-I747M Telus), I have CWM recovery installed. I was interested in overclocking so I installed this kernel on my stock rooted rom (I installed the "sammy" one). I also cleared the delvik cache, cache, and fixed permissions before rebooting. Now I'm having a weird problem with video playback. I get these bleep like sounds, like you might hear on a spaceship, lol. The normal audio plays in addition to these sounds. Yet, regular audio plays fine (mp3s), same with youtube. So, my question is, why? Is there any way of fixing this? I'd rather not play around the stock ROM. I made a backup before doing anything and recently tried to restore the boot, but I got an invalid md5 check.
-JC
Okay, I was able to fix my problem by flashing the stock at&t kernel... but I would still like to be able to overclock... is there another kernel that I can try or a way to fix the problem with the kernel I already tried? Thanks.
If you still want to try previous kernel your problem might be because of heavy undervolting , kernel creator posted this voltage chart.
You can experiment by increasing voltage and see if that helps.
Or you can just try this faux kernel , its pretty good also, we don't have many kernel choices for Samsung based roms at this early development cycle.
ghost77 said:
If you still want to try previous kernel your problem might be because of heavy undervolting , kernel creator posted this voltage chart.
You can experiment by increasing voltage and see if that helps.
Or you can just try this faux kernel , its pretty good also, we don't have many kernel choices for Samsung based roms at this early development cycle.
Click to expand...
Click to collapse
Thanks for the reply... but I was able to fix the problem. It was something wrong with the settings of SetCPU which I installed earlier. I changed it from on demand to performance and now all is well. Now I have a question about battery life. Will overclocking drain battery a lot faster? I imagine it would only make a difference if I was doing CPU intensive things.
JustChillin1414 said:
Thanks for the reply... but I was able to fix the problem. It was something wrong with the settings of SetCPU which I installed earlier. I changed it from on demand to performance and now all is well. Now I have a question about battery life. Will overclocking drain battery a lot faster? I imagine it would only make a difference if I was doing CPU intensive things.
Click to expand...
Click to collapse
Well.. performance setting makes it so that your CPU runs 100% all the time. I don't think that will be battery friendly . Overclock generally uses more power and battery longevity will depend on your usage.
You can try messing with setcpu settings. Try Conservative, then limit minimum speed to 384 and max to your preference. Try your movie again.
Current kernels and setcpu are a bit quirky.
I had the same issues on ktoonsez Sammy. Ended up back at stock AT&T. I've heard it's an issue with many of the kernels but a fix is on the way. Couldn't find a way to get rid of it, but that's not to say it can't be done. Don't have much time to tinker right now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Its a known issue on ktoonsez kernel. Flash faux's kernel, it has the same features (as well as GPU OC) and doesn't have the audio issue.
Hi all,
Today I installed CWM and flashed franco's kernel for JB (the newest one). At first it seemed pretty fast so I was happy. I decided to install setcpu and set it to max 1,8 ghz with set on boot enabled (I know it was stupid, but I did not realize it at the time). After rebooting the phone froze and a purple layer appeared on top of my screen. Seconds later my phone rebooted. I set setcpu on 1,2 ghz max and let it stresstest for a couple of minutes. No errors were found. But now my phone lags sometimes, like if project butter just had disappeared and the normal android sluggishness has reappeared. Is this a kernelissue or did I damage my cpu with this stupid overclock? Btw, apart from the sluggishness in the animations I can run everything just fine.
I'm on Franco and have no problems. Why don't you try another kernel and let us know how it goes?
tobitronics said:
Hi all,
Today I installed CWM and flashed franco's kernel for JB (the newest one). At first it seemed pretty fast so I was happy. I decided to install setcpu and set it to max 1,8 ghz with set on boot enabled (I know it was stupid, but I did not realize it at the time). After rebooting the phone froze and a purple layer appeared on top of my screen. Seconds later my phone rebooted. I set setcpu on 1,2 ghz max and let it stresstest for a couple of minutes. No errors were found. But now my phone lags sometimes, like if project butter just had disappeared and the normal android sluggishness has reappeared. Is this a kernelissue or did I damage my cpu with this stupid overclock? Btw, apart from the sluggishness in the animations I can run everything just fine.
Click to expand...
Click to collapse
I understand people want to ask questions first, did you try to wipe and reflash?
At most I can probably assure you, you didn't damage your CPU.. there would probably be more dire issues if it was.
Did you flash a new kernel yet?
Sent from my Galaxy Nexus using Tapatalk 2
Not yet. Should I reflash franco or try another? Can I flash a new kernel over another kernel without wiping my whole device?
tobitronics said:
Not yet. Should I reflash franco or try another? Can I flash a new kernel over another kernel without wiping my whole device?
Click to expand...
Click to collapse
Wipe dalvik cache and install trinity.
Sent from my Galaxy Nexus using Tapatalk 2
tobitronics said:
Not yet. Should I reflash franco or try another? Can I flash a new kernel over another kernel without wiping my whole device?
Click to expand...
Click to collapse
Yes, I've flashed 3-4 kernels on one ROM. You can dirty flash your ROM too or completely wipe and flash.
Either way its fine. I do suggest wiping and flashing though..
Sent from my Galaxy Nexus using Tapatalk 2
And should I uninstall SetCPU in order to get stock CPU speeds? And what issues would I have if I would have fried my SoC?
tobitronics said:
And should I uninstall SetCPU in order to get stock CPU speeds? And what issues would I have if I would have fried my SoC?
Click to expand...
Click to collapse
Setcpu is fine. In order to get stock, either use a new kernel or dirty flash.
Assuming.. if it was I'd guess the phone probably wouldn't be running?
Sent from my Galaxy Nexus using Tapatalk 2
You need to learn about what you're doing before you do it!
I flashed the trinity 1420-537 JB stable kernel, and everything works as smooth as it has to be. The strange thing is that it was a bit sluggish until I changed my wallpaper from a live to a normal one. Now I switched back and everything is still smooth :? . Anyway, does this kernel overclock the cpu itself or are the speeds in the name just the available range?
z06mike said:
You need to learn about what you're doing before you do it!
Click to expand...
Click to collapse
:good: :good:
tobitronics said:
I flashed the trinity 1420-537 JB stable kernel, and everything works as smooth as it has to be. The strange thing is that it was a bit sluggish until I changed my wallpaper from a live to a normal one. Now I switched back and everything is still smooth :? . Anyway, does this kernel overclock the cpu itself or are the speeds in the name just the available range?
Click to expand...
Click to collapse
if I have such issues I will never flash an oc kernel to look if everthing is working. Install stock rom kernel back and try. If everything is fine......you can try an oc one.
On Trinity; first number is MAX CPU clock range you can chose and second number is fix GPU clock.....or just reading FAQ, Changelog etc. will answer your questions really quick
regards,
Lars
from what I've heard, some gnexs are really picky with roms and kernels. I guess your phone is one of them. I personally had problems with Trinity Kernel, since when I reboot, it sometimes bootloops for 5minutes and such. I personally had no problems with Franco though. In fact, I use Franco as my daily driver
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Franco's app let's you easily tweak the settings (overclock, change governors, etc.) which may help the sluggishness. I almost exclusively run Franco and his M5 is amazing!
Sent from my Galaxy Nexus using Tapatalk 2
A reflash might be the best option ... either the ROM or Kernel or Both lol thats my inner crack flasher talkin'
Never had problems with franco. It's trinity's kernel that made problems for me.
I run Franco's kernel myself. Just have to be careful with flashing the nightlies, it can be hit or miss. They are experimental.
Sent from my Galaxy Nexus using Tapatalk 2
CHANGE YOUR GOVERNOR HURR DURR.
Sent from my Galaxy Nexus using xda app-developers app
Today I reflashed franco and I must say that trinity is way better, at least for me. Franco keeps being sluggish, trinity works smooth.
trinity is better than Franco's in every way possible...
especially battery life