so...my note is rooted with OC and on CWM beta 3. i even have flashed a battery percentage status bar mod (after many tries and lots of FC's issues) i finally got everything stable on a stock rom oc'd at 1.8 and this thing was sick dude...i mean so fast and big and bright and perfect...no problems except for 1...was getting random reboots...3 a couple days ago while using boat browser every mtime so uninstalled and started using dolphin. worked great until 1 rando reboot today while on dolphin browser...i figure no big deal it happens when you tweak your phone...but then all of a sudden it did something different just now it did...it just randomly rebooted while toggling wifi on except after it booted back up i couldn't unlock the screen or get into the launcher and the screen went black and unresposive. power button did nothing even holding it down...i pulled the battery out and then back in and restart and phoone booted up normally. clear as a bell and lightning fast...
so i just dialed down the oc to 1700...hope it's all good though...can't think why it would do this...
thanks?
Your phone can't handle the 1.8 ghz overclock.
When overclocking, no 2 chipsets will perform the same. Some will be able to overclock to 1.8 and some will not.
zer0nine said:
Your phone can't handle the 1.8 ghz overclock.
When overclocking, no 2 chipsets will perform the same. Some will be able to overclock to 1.8 and some will not.
Click to expand...
Click to collapse
So then is this OK?
Well anyway I guess I'll post back with the results. Cuz I'm running that way now. Hope I don't brick this beauty.
All opinions welcome.
Sent from my SAMSUNG-SGH-I717 using xda premium
You won't brick by overclocking. If you run it at an unstable clockspeed for your phone, you'll just be getting constant reboots.
1782 mhz should be fine. Try benchmarking your phone using Quadrant and Antutu from the market to stress test your phone at that new CPU speed.
zer0nine said:
You won't brick by overclocking. If you run it at an unstable clockspeed for your phone, you'll just be getting constant reboots.
1782 mhz should be fine. Try benchmarking your phone using Quadrant and Antutu from the market to stress test your phone at that new CPU speed.
Click to expand...
Click to collapse
Thanks. I'm at 3723.....phone feels good.
Sent from my SAMSUNG-SGH-I717 using xda premium
yup, sounds like classic too-overclocked symptoms to me. Back it down a notch like you have already done and try again...
Related
hi there
i am a noob i just brought vibrant previously using htc hero...
i tried to flash bionix and bionix fusion with the new 1.2 ghz oc...
phone works well except when i play games like asphalt, neocore my phone freezes then i have to remove the battery and insert again...
what could be the problem
i am using J12 RADIO....
PLEASE HELP ....
VIBRANT IS 100% AN IPHONE KILLER ... LOVE IT....
mine does the same thing not really sure why yet but if your using setcpu just put the speed at 1000 on both the proformance is unnoticable
Thegreat520 said:
mine does the same thing not really sure why yet but if your using setcpu just put the speed at 1000 on both the proformance is unnoticable
Click to expand...
Click to collapse
i had kept setcpu max 1000 and min 200 still it freezes when running heavy graphics games
Your phone might not play nice with that kernel. Try flashing core 1.0 instead and see if that helps.
Yes, not all phones are stable when overclocked. Use the stock kernel and you should be fine.
Chalup said:
Yes, not all phones are stable when overclocked. Use the stock kernel and you should be fine.
Click to expand...
Click to collapse
^^^ this, but I'm sure you knew that since it says so every where.
My phone runs great at 1.2Ghz with JAC's XMOD Voodoo kernel, but locks up constantly with Core, OCed or not. Try swapping kernels, but don't give up on the OC yet.
I'm having the same exact issue, mine will just lock up for no reason sometimes as well. I'm not sure what it is, I kind of feel like it's the rom. I had problems originally with fusion to begin with. Maybe I'm not doing a proper procedure to install it?
Is it because I'm wiping and going straight to fusion? Please anyone else are you having this issue, I'm getting frustrated and feel my phone is slightly useless like this. I HATE stock.
Edit: Setcpu doesn't let me set to 1000 with Core 1.2Ghz, I can only get 1000 if I use Core 1.0Ghz (obviously). Again though, same issue regardless.
Core is still in beta status and not all the bugs have been worked out yet. The issue the OP is having has been mentioned before in the Core thread in the Dev section and on the TeamWhiskey.com forums as well.
OP: To alleviate the freezing issue you're having, flash the 1.0GHz CoreV1 instead of the 1.2GHz CoreV1
~SB
Im running Cm7 withh Imoseyon's kernal. Every time i oc to 1.9 phone will freeze almost instantly any suggestions to fix this
Sent from my ADR6400L using Tapatalk
Yep, slow the overclock to 1.5 your phone can't handle it, neither can mine. Some can and some can't but other than running a nice CPU test to show off to your buddies you don't want to push your TB like that on a daily basis. I have mine set to 368/1.02 and happy as can be with the extra battery life I get from my phone.
If I helped you in any way please use the thank you button
Alrighty i have mine set to 1.4 extremely undervolted and i get 9-10 hours battery life with heavy use thank you
Sent from my ADR6400L using Tapatalk
Hello,
I have a few issues with IMO's lean kernel that someone might can help with. 1) Extreme settings 2 and 4 cause instant phone freeze and reboot. 2) Option 3 works for the first minute or two after boot but then freezes (CPU spy shows 1.92 GHz runs smooth through boot). I believe it to be caused by the ramp up/down of the governor or possibly a script/setting messing with my system.
I am able to run very stably and smooth with a top CPU speed of 1.6 GHZ( 1.593 GHz on A05P). Any ideas on what I can do to increase the CPU speed so that the system stays stable? Your input is much appreciated. Thank you again for helping this poor noob.
Veltar said:
Hello,
I have a few issues with IMO's lean kernel that someone might can help with. 1) Extreme settings 2 and 4 cause instant phone freeze and reboot. 2) Option 3 works for the first minute or two after boot but then freezes (CPU spy shows 1.92 GHz runs smooth through boot). I believe it to be caused by the ramp up/down of the governor or possibly a script/setting messing with my system.
I am able to run very stably and smooth with a top CPU speed of 1.6 GHZ( 1.593 GHz on A05P). Any ideas on what I can do to increase the CPU speed so that the system stays stable? Your input is much appreciated. Thank you again for helping this poor noob.
Click to expand...
Click to collapse
Don't OC that high, simple as that. There is no need to run the phone constantly at 1.9ghz.
Running stock 2.3.6 rooted, I'll be playing Galcon, Froad, Fruit Ninja, etc. it will randomly freeze for 4-7 seconds, sometimes even boot me back to the title menu.. Is anyone else experiencing this & is there a fix?
Sent from my DROID RAZR using Tapatalk
I know EXACTLY what you're experiencing. I HATED when that used to happen to me...
A fix that I tried and currently still use, is to use CPU Master (or I guess any other app that let's you set your CPU speed and over/under clock)
I usually set it to min. 1000mhz and max. 1200mhz, and voila, problem solved
Tell me if it works for you!
Icannotthinkofagoodname said:
I know EXACTLY what you're experiencing. I HATED when that used to happen to me...
A fix that I tried and currently still use, is to use CPU Master (or I guess any other app that let's you set your CPU speed and over/under clock)
I usually set it to min. 1000mhz and max. 1200mhz, and voila, problem solved
Tell me if it works for you!
Click to expand...
Click to collapse
that's still some pretty massive overclocking, running your CPU so high all the time will eventually eat up a lot of battery.
I think it's a problem with the phone's kernel not being very well optimized. Or.. maybe it's the developers who haven't optimized their games for dual cores, idk
POQbum said:
that's still some pretty massive overclocking, running your CPU so high all the time will eventually eat up a lot of battery.
I think it's a problem with the phone's kernel not being very well optimized. Or.. maybe it's the developers who haven't optimized their games for dual cores, idk
Click to expand...
Click to collapse
LOL I'm aware that is really high. But don't worry, I almost always set it to min. 300mhz to a max of 800 mhz for average use. I only overclock for the rare occasion of games, which I have gotten a little tired of xD
Haloman800 said:
Running stock 2.3.6 rooted, I'll be playing Galcon, Froad, Fruit Ninja, etc. it will randomly freeze for 4-7 seconds, sometimes even boot me back to the title menu.. Is anyone else experiencing this & is there a fix?
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
had the same problem. for me i just thought about, why they are freezing. then i recognized that every time the razr's cpu changed it's speed, there's some freezing... freezing time ssems to be long or short, don't know exactly why this happens...
fruit ninja should be playable unfreezed with speeds like 800MHz or even 600MHz... tested only with 800...
greetings
Odd.. Fruit ninja used irritate the **** out of me for freezing on 2.3.5.. But no longer freezes on 2.3.6
Sent from my XT910
POQbum said:
that's still some pretty massive overclocking, running your CPU so high all the time will eventually eat up a lot of battery.
I think it's a problem with the phone's kernel not being very well optimized. Or.. maybe it's the developers who haven't optimized their games for dual cores, idk
Click to expand...
Click to collapse
I am running my RAZR at 1325 mhz and no problems with battery drain...
Some of the games i try, still freeze
vash_h said:
Odd.. Fruit ninja used irritate the **** out of me for freezing on 2.3.5.. But no longer freezes on 2.3.6
Sent from my XT910
Click to expand...
Click to collapse
same case with me.. after i update to 2.3.6 asia retail version fruit ninja is now as smooth as butter..
Icannotthinkofagoodname said:
I know EXACTLY what you're experiencing. I HATED when that used to happen to me...
A fix that I tried and currently still use, is to use CPU Master (or I guess any other app that let's you set your CPU speed and over/under clock)
I usually set it to min. 1000mhz and max. 1200mhz, and voila, problem solved
Tell me if it works for you!
Click to expand...
Click to collapse
This fixed the freezing in Fruit Ninja for me on Axiom AOKP b15 ICS Rom. Except I set MIN to 800 mhz.
I'm having some serious lag when using data-related apps such as TuneIn, Google Now and Dolphin Browser. Also happens when downloading. Other times it works completely fine then once I open any of these apps, it lags like there's no tomorrow..
On stock LIB rom with Siyah 1.6 rc3, CPU/GPU overclocked 1600MHz and undervolted (25-50mV).
OCUV doesn't seem to be the problem as stress tests and graphic benchmarks are completely fine with no errors, and since this has been happening even before I did anything, albeit to a less serious level.
Anyone else experiencing the same issue? Can't even undervolt too much because of this..
why don't you try using stock Rom for a while with out any undervolting or over cloaking and check the performance of your phone?
I guess that would be the only option for now?
will try that.
Sent from my GT-I9300 using xda premium
same problem with i thought it from undervolting or kernel problem I've tried it with stock kernel same issue exist i think it's jellybean problem.:crying:
redownloaded stock, flashed, undervolted 25-150mV, all seem okay now.
will wait to wait and see a few days but so far so good. I'm not gonna undervolt too much on the higher clocks as I'm only expecting battery extension on lower clocks, ie when in sleep or screen off.
Sent from my GT-I9300 using xda premium
I cleared my cache and dalvik cash and when I rebooted the phone the screen had a sorta checkerboard pattern on it...it straightened up when I rebooted again What would cause that?
Have you been overclocking your GPU?
If so reset it to 533mhz and never OC it again. Sounds like textbook GPU overclock failure.
DaRkL3AD3R said:
Have you been overclocking your GPU?
If so reset it to 533mhz and never OC it again. Sounds like textbook GPU overclock failure.
Click to expand...
Click to collapse
Why would it just now do it? Is it bad for it?
blackbass595 said:
Why would it just now do it? Is it bad for it?
Click to expand...
Click to collapse
Generally speaking any artifacts that arise shouldn't be permanent. However damage from overvolting can occur. I didn't play around with the GPU clock settings in the custom kernel so I don't know how much they overvolt it, but that is sure to cause problems if it does, in time.
Artifacts caused by overclocking the GPU, like that checkerboard pattern you saw, are usually temporary. But if you see artifacts like that then it's a sure sign that your OC is failing and you should fall back a notch, or just go back to default clock speed period.
I have years experiencing overclocking graphics cards and processors alike on my PC. Pretty obvious what happened here.
Right on man thanks...I have run antutu so many times that I know what the graphics score is and I can tell ANYONE reading this that over clocking the GPU does not speed the phone up. I'm back at 533 and still hit this on pegasus governor. This is what i hit with the gpu set at 620 (or whatever the next step is) That was the only thing I had changed in GPU. So take dark leaders advice and slow it back down...
Thanks for sharing this guys, I was getting this when playing some games, especially with modern combat 4. Just flashed the 29.1 (from 28/5g) and am going to leave everything at default for now to see how it runs.
Edit: Would ya look at that.... played again on stock settings with Perseus 29.1 and it runs like a dream! Not a single glitch, lag, or even the slightest artifact! Sometimes less is more!
Sent from my unlocked & underclocked Galaxy Note 2
Yep no problem guys.
CPU overclocking can have tangible gains for phone use. But GPU is pretty tight setup from stock, and pushing it harder won't really improve much of anything. In fact I only recommend overclocking desktop grade GPU's for benchmarking only, as it's impact on real world performance is so minimal that it isn't worth the extra needed voltage and the possibility of artifacting that you get with it.
So yeah definitely enjoy the phone at 1.8Ghz CPU and leave the GPU alone
Yes this is info that needs to be out there ...steve's post is yet more proof of concept here. ... Just linked a guy on kernel page here cause he's oc-ing GPU to 800...wow.
This is very good info indeed. I am currently at one level higher in gpu and after reading this thread its going back to 533. Planning on keeping this phone for the long haul.
Sent from my SCH-I605 using xda app-developers app
DaRkL3AD3R said:
Have you been overclocking your GPU?
If so reset it to 533mhz and never OC it again. Sounds like textbook GPU overclock failure.
Click to expand...
Click to collapse
blackbass595 said:
I cleared my cache and dalvik cash and when I rebooted the phone the screen had a sorta checkerboard pattern on it...it straightened up when I rebooted again What would cause that?
Click to expand...
Click to collapse
I know exactly what you're talking about and it is not limited to your model Samsung. It happened on my Galaxy Tab as well.
Actually, this is normal, even if not overclocked. It happened to me after clearing the caches like you did and I thought it was locked up, cause it sat there for a while and I kept trying reboots, thinking I was hosed. But this is a natural phenomenon!
When this happens, do not reboot! Instead, just put it down, go make a sandwich and come back. It will be booted! (screen may have turned off by then, as it normally would after a while after booting)!
Then reboot again and it should come up normally!
DaRkL3AD3R said:
Yep no problem guys.
CPU overclocking can have tangible gains for phone use. But GPU is pretty tight setup from stock, and pushing it harder won't really improve much of anything. In fact I only recommend overclocking desktop grade GPU's for benchmarking only, as it's impact on real world performance is so minimal that it isn't worth the extra needed voltage and the possibility of artifacting that you get with it.
So yeah definitely enjoy the phone at 1.8Ghz CPU and leave the GPU alone
Click to expand...
Click to collapse
My dual GTX570 cards that have been over volted and overclocked beg to differ. Noticeable gains in many games after doing so. Not just in the benchmarks. That is com pairing areas of very noticeable frame drops to where the from drops were less severe and kept from stuttering.
I do agree that the GPU on our phone does not need to be overclocked.
Sent from my SCH-I605 using xda app-developers app
I use to mess with gpu overclocking on my GNex and it would always get that glitchy stuff on the screen when I played games. I just never touch it now.
I OC'd both on the GNex and now the beast and have had no trouble at all. Speed freak! :laugh:
nosympathy said:
My dual GTX570 cards that have been over volted and overclocked beg to differ. Noticeable gains in many games after doing so. Not just in the benchmarks. That is com pairing areas of very noticeable frame drops to where the from drops were less severe and kept from stuttering.
I do agree that the GPU on our phone does not need to be overclocked.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I agree that the GPU doesn't need to be overclocked, although I did overclock mine from 533 MHz to 800 MHz.
My comment about the "Colored checkerboard screen after clearing the Dalv chache", when it's botting up again immediately after doing that, was only in reference to the fact that that happens on some Samsung devices immediately after clearing that cache and it starts to boot up, regardless of whether the CPU, or GPU has been overclocked or not and it just sits there for a while and will seem like it has locked up.
In reality, if you just let it do its thing; just put it down and walk away, eventually, it will finish booting and it will be fine. Then, once your Home Screen has finally come up again, you just reboot it one more time and it will boot as it normally boots, without the funky looking screen.
I guess this screen glitch is just what happens when it's rebuilding that cache, which I would assume it does when it boots again and I assume that's probably why the boot takes so long after clearing that cache.
In other words, my point was simply that all is well and there is no need for any concern. It just looks like there is.
But hang in tight and about 3-5 minutes later, you will have your device back again!