Related
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.
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
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
I do not experience this issue. When you flashed the rom, did you do a clean install? Have you formatting the device?
Yup.. I format everything.. I use the touch recovery and just use every option that it provides and wipe everything.. It even does it when there is nothing installed. I usually delete almost all the useless system apps that I don't use like the google music app and all of the ones civato provides... I even change the animation settings to .5 in the developer section.. should I turn them off all together?
Crimson Ghoul said:
Yup.. I format everything.. I use the touch recovery and just use every option that it provides and wipe everything.. It even does it when there is nothing installed. I usually delete almost all the useless system apps that I don't use like the google music app and all of the ones civato provides... I even change the animation settings to .5 in the developer section.. should I turn them off all together?
Click to expand...
Click to collapse
The animations should not have anything to do with it. Does this only occur on that rom? Have you tried other roms and experienced that issue?
not many other roms out there.. I have used stock and his.. had the same issue on both.. Also happens on my brother's a500.. it usually happens when unlocking and going into any app.. it sits there for a few seconds and then opens whatever it is i opened
Crimson Ghoul said:
not many other roms out there.. I have used stock and his.. had the same issue on both.. Also happens on my brother's a500.. it usually happens when unlocking and going into any app.. it sits there for a few seconds and then opens whatever it is i opened
Click to expand...
Click to collapse
This is starting to sound like a hardware issue. Before that is concluded, you could:
- Make sure the governor is not set to "conservative"
- Try a clean install of CM9
If the problem still arises, its most likely a hardware issue.
I'm using the OC kernel and have it to 1500.. I also always leave it on performance.. I figure it would kill my battery life but I don't use it much.. and i tried cm9 also.. too many issues as of right now
Crimson Ghoul said:
I'm using the OC kernel and have it to 1500.. I also always leave it on performance.. I figure it would kill my battery life but I don't use it much.. and i tried cm9 also.. too many issues as of right now
Click to expand...
Click to collapse
It doesn't seem it can be anything else but a hardware issue in that case.
NB. Overclocking to a high frequency can cause instability and bring about that issue (but since you experienced it on the stock rom, its quite likely not to be that).
the overclocking helps to speed it up a tad bit.. for the most part it just lags.. i did a clean install just now
Thought I would jump in. Stock ics would slow down and lag on me, jittery transitions poor performance in games or movies, but it took an hour not a few minutes. However testing the T20 kernel before the release kernel had that exact issue, bogging and lagging within minutes.
His release kernel doesnt do it, and flex extreme as well as my cm9 builds don't, even with T20 kernel. Consider flashing that kernel to see what happens.
Side note...what issues did you have with cm9? And what release? My build 1 has been running for 3 days no reboots stable as can be undervolted and OC when needed. Something to maybe think to try to see if it persists. T20 kernel works fine with it too.
Tapatalked from my Galaxy S II.
Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
Yup, EVERYTIME I turned on my screen then unlocked it to laggggggg for a lil while. I'm now using CM9 n that issues gone. Try CM9
forum.xda-developers.com/showthread.php?t=1705554
A100 Running CM9 Nightly ROM n ezT20 OC Kernel :-D
To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.
eww245 said:
To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.
Click to expand...
Click to collapse
That reminds me...setting a screen off profile with the same min/Max speed can cause issues with that, give Max a notch or two higher. And don't have it change the governor leave it the same. So like interactive screen on Myst nit be conservative screen off, doesn't work that way.
Tapatalked from my Galaxy S II.
I had the same issue on stock. I noticed there are 2 weather applications installed (version 1 and version 2) immediately after I disabled the old weather application (version 1) this stopped happening. I used the ICS GUI to do the disable.
This might not be the case in custom rom, but is true for stock. Post reply and let me know if this fixed it for you also.
Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
Do you have a micro SD card plugged in? Try reformatting the card with a computer. Worked for me.
Sent from my A100 using XDA
I felt the need to add my two cents in this....this has been happening to me for the longest with the flex reaper rom ONLY. I've used stock and ZN's rom and those did not lag after unlock...only flex reaper. I'm currently using flex reaper and still experience it from time to time but doesn't destroy my day at all...
Give the CM9 nightly ROM's a go. No Bluetooth n no HDMI audio, but everything else is fine n damn smooth. Those issues will be fixed though
A100 Running CM9 Nightly ROM n ezT20 OC Kernel :-D
eww245 said:
To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.
Click to expand...
Click to collapse
I installed Flex 100 Reaper with stock and it it seemed to run smooth enough. Then I installed the OC kernal, and started to get lag. I was looking around to find the OC settings, but can't see it anywhere in settings..
Can anyone direct me to where can I adjust the governor/max/min CPU settings?
Sorry for the noob question.
htc_softbank said:
I installed Flex 100 Reaper with the OC kernal, and started to get lag. I was looking around to find the OC settings, but can't see it anywhere in settings..
Can anyone direct me to where can I adjust the governor/max/min CPU settings?
Sorry for the noob question.
Click to expand...
Click to collapse
Setcpu from the play store.
The overclock settings are not integrated like CM.
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.
Alright so I am using KT747 Kernel with Ktoonservative/Noop, 1512-384mhz, screen off 486mhz. I was given an option to Lock frequencies which disallows apps to modify the speed. However I noticed after I checked this some of my apps started crashing. I want good battery life (forget to mention I undervolted) and want to know if locking frequencies is what is making the apps crash. Any help would be great, and feel free to post some good settings for the kernel for optimal battery life with pretty decent clock speeds as well. Thanks again.
If your apps crash it is more likely to be caused by your undervolting.
And for the setting go there:
http://forum.xda-developers.com/showthread.php?p=31539830
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
If your apps crash it is more likely to be caused by your undervolting.
And for the setting go there:
http://forum.xda-developers.com/showthread.php?p=31539830
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah I read your post earlier in that thread and was using your settings. I've come across a newer problem, my phone randomly reboots. I don't know what was causing this so I restored default settings.
When you change kernel or kernel setting it is usual that your phone may need a few reboots before stabilizing
Sent from my SGH-I747 using xda app-developers app
Unlock the frequencies and run the app that causes the reboot. If it doesn't reboot that was the problem. More likely its too much under volt. The table in the link is some pretty severe undervolting. 740 is a long way down from the stock 925. That's great if your phone can handle it, but can cause problems if it can't. Piece of advice, never use any set on boot settings if your not sure it will. You may find yourself in a bootloop and have to reflash the kernel to get out of it.
DarthDerron said:
Alright so I am using KT747 Kernel with Ktoonservative/Noop, 1512-384mhz, screen off 486mhz. I was given an option to Lock frequencies which disallows apps to modify the speed. However I noticed after I checked this some of my apps started crashing. I want good battery life (forget to mention I undervolted) and want to know if locking frequencies is what is making the apps crash. Any help would be great, and feel free to post some good settings for the kernel for optimal battery life with pretty decent clock speeds as well. Thanks again.
Click to expand...
Click to collapse
I doubt locking the frequencies has anything to do with your reboot problems, this simply dissallows any apps that are capable to override the voltage settings for any particular frequency step. In fact, unchecking this may actually give you a false positive of it 'fixing' the problem when it is actually just using the default (or higher) voltages, burning up more battery in the process. As mentioned by jethro and liltitiz its more likely your UV settings, keep playing with them until you find the happy spot (works on other things too....:silly.
jethro650 said:
Unlock the frequencies and run the app that causes the reboot. If it doesn't reboot that was the problem. More likely its too much under volt. The table in the link is some pretty severe undervolting. 740 is a long way down from the stock 925. That's great if your phone can handle it, but can cause problems if it can't. Piece of advice, never use any set on boot settings if your not sure it will. You may find yourself in a bootloop and have to reflash the kernel to get out of it.
Click to expand...
Click to collapse
Or just move the ktweaker apk from the /system/app directory from a recovery based file manager. This will keep it from launching on startup and then can either be moved back or ran to reinstall. This way you dont have to cleark the dalvik cache, which should be done any time a kernel is installed, eliminating the extra long boot time when this is done. Either the built in TWRP explorer or the Aroma File Manager which can be 'flashed' in recovery. It doesn't actually flash anything, just unpacks, runs, and then is dumped from memory on reboot...very handy if you dont have TWRP or can't get into android.
liltitiz said:
When you change kernel or kernel setting it is usual that your phone may need a few reboots before stabilizing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I was wondering what was going on. I restored stock Voltage and realized that it was the problem.