I thought I'd put this together given the amount of questions and apparent lack of knowledge on what you're getting yourself into with overclocking. While it's a one-click-wonder with SetCPU and JuiceDefender, it's not that simple when it comes to what it's actually doing to the phone.
The first thing you need to know is this:
All devices are not created equal!
Even when they come off the production line together they may not be capable of even getting close to each other with an overclock. This is down to numerous variables, the most important of which is the processor itself. Processors are manufactured in batches from something called a wafer (basically a big chunk of silicon), that batch is then tested to a maximum stable speed and then marketed at a slightly lower speed for the sake of rock solid stability. Dual/multicore processors may have a faulty core disabled and be marketed as something else (hence AMD's Tri-Core processors). This is the reason overclocking works, and the long and the short of it is just because Person A can get 1.3Ghz running stable, doesn't mean Person B can.
So, now we know that whingeing that my Desire can get 1300Mhz but yours crashes every time you go above 1100Mhz is irrelevant, we can move on to the risks. Overclocking is dangerous. That's not an exaggeration, so let me reiterate...
Overclocking is dangerous, You can potentially kill your phone stone dead.
But yet again it's not that simple. Yes, in very rare cases a processor will just go bang and give up, but most of the time other things will happen, behind the scenes, that you won't know about until it's too late.
The basic premise of overclocking is to get a faster processor clock speed. A small jump can probably be attained just by upping the speed itself and be perfectly stable. Going higher is where the problems start. If you start getting crashes/freezes/reboots then the next step is to increase the voltage to the processor to make it more stable, but more voltage means more heat, and excess heat is bad. This can either cook the processor as a whole or a group of transistors. This is more of a problem on a device like the Desire as where do you put the extra cooling?
Another problem is that more voltage can fry an IC track, and/or arc across to a track it shouldn't be on. This could do nothing, but it could also kill a single transistor on the processor or other chips in the device, or maybe multiple transistors and it can also lock them open or closed. This takes us back to random reboots, freezes, and crashes - but this time it can't be fixed.
Then theres a twist. Undervolting can also break things. A transistor is either on or off, and if it doesn't get enough power one of three things can happen - it can work fine, it can not work at all, or it can continually switch until it breaks (what an example? go and flick a light switch on and off until it stops - and it might not be the bulb that goes). If it decides not to work when other parts think it should, guess what happens.
So, bear this in mind when overclocking. If you start getting ANY issues test at stock speed. If you still have issues and/or you kill your phone, it's your own fault.
Mods - I've put this here as it's the place most people seem to ask about OCing, please move it if i'm wrong...
Nicely written and informative. Users must always take their own responsibility when trying to do something "out-of-spec" with their device. I didn't know undervolting could break things though.
It's far far less common and it's not the actual undervolting that causes the issue - it's the power requirements of the device. If you're unfortunate enough to have something keep tripping - it's kind of like when a PSU goes and keeps clicking, there's not quite enough power to flick to On permanently so it just ticks at you till you turn it off or it gives up completely. 9 times out of 10 you'd be fine, but theres always that chance.
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
My phone freezed several times a day with defrost. But no freez with MIUI/OpenDesire. I dont know why but Defrost §$%#s my phone
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
It can be that it is your ext3 partition if you have one...i had a user with freezes...and i did not know what it was...i say him...make all new...he flasht a original rom...root again with unrevoked...flasht my rom again and it was the same...freezes...so he formated the card...and maked a new ext3 and now he have no more problems with freezes
with kind regards..Alex
Good write up. Hopefully people will actually read this and understand the risks before they start pushing zip files with overclocked/undervolted kernels. Personally I've never overclocked any mobile device since I'm not comfortable with the risks that may lead to long term damages.
great job! thumbs up! vote for sticky or linking this in one of the stickys
i'm familiar with overclocking since i've been doing it to my PCs for years. i'm wondering if aosp roms push the phone harder or something than sense based ones?
reason i ask is i've tried a few aosp roms (open desire, defrost etc) and all the various kernels i've tried cause a reboot after a while - 30 mins, upto a few hours. now, i tried richard trips sense kernel and OCd with that no problems at all. very weird
p,s all Ocing was on the relatively small 1113mhz.
Related
CM6 is definitely great, I think without question it is a vast improvement.
The only issue I have is my battery life is ABSOLUTELY HORRIBLE. Could be the worst battery life I've had with any phone. But maybe that's just the EVO, with it's big screen and speedy processor. I underclock to 384 mhz sometimes but then the thing slows down and even freezes. I have 3 different batteries and they all perform about the same (not good.) Before I had a partial wake issue but that's gone, and battery life still stinks. I've also tried calibrating but nothing really seems to make it better.
I hear the snap thing is good for battery life but I everytime I open that thread I get a headache. I love this phone and am obsessed wtih it but that thread is a bit much even for me!
Can anyone give me a quick and dirty explaination of what snap is / how to use snap? Which kernel to flash? Some day I hope to digest that mammoth of a thread, but right now I'm too busy reading texts for college and Just want better battery life.
Thanks!
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
nyc_zx10 said:
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
Click to expand...
Click to collapse
Yeah, I tried System Panel but the things eating my battery were mostly system things, like Browser. I guess I could give it another go.
Why are Juice Defender reviews so bad? I've considered it before also, maybe will try playing with it again
snap 8.2 is the current release. you can try any of the kernels, but i would avoid the 7.0/7.1 SD Card implementations since that technology has been put on the back burner for a bit.
Snap allows you to you Overclock and Undervolt (aka: UV).
Overclocking of course is for speed and Undervolting may save battery.
all EVOs are not created equal. some like undervolting some do not. so snap is available in multiple flavors. each with a different UV floor. the lower the floor the more potential battery saving..but also the more chance for a random reboot or wifi/gps acting funny. remember UV retards the amount of power so things can act goofy. the different UV floors are 800mv - 925mv. for example...i use the 8.2_900 because it works well with my EVO. the 8.2_800 booted great but after a while started rebooting itself. 8.2_850 just hung at bootup. the 8.1 kernels didn't work for me at all. 7.3b1 was great.
HAVs is adaptive..so don't get stressed if your device fails to boot properly the first time. wipe the cache/dalvik and try again.
so download a few of the 8.2 kernels.
make your nandroid
begin trial and error (I'd suggest starting at 800, 850 then 900 to get a feel)
don't be afraid to wipe the Cache and Dalvik multiple times.
don't worry about the whole thread. just grab the last few pages and read the OP. then feel free to ask.
i also recommend setCPU. you can find some threads for SetCPU configurations to help. BUT....make sure SetCPU is disabled when flashing the new kernel. once you get a working kernel you can enable SetCPU...but during testing phase it will give you gray hair.
jmxp69 said:
Just a few quick thoughts on voltages/freqs after seeing a handful of discussion in the thread:
1) Every 8.2 kernel has voltages lower than stock. The default stock voltage @ 245 is something around 1050.
2) No real effort is made to UV at the top end. It's a little lower, but the objective at the highest CPU frequency is not to UV. Most of the benefit of UV comes at the low end of the scale when your phone is idle (most of the time). Less voltage = less draw.
3) nHAVS scales voltage at each step. There is a min.max voltage at every cpu frequency. This range is fairly small--50-75mv, but it enables HAVS to decide based on feedback from the CPU which one to apply. And the max at each step is lower than stock. So no matter how you slice it, even if you're running 925, you are undervolted. This becomes a question of how undervolted.
4) OC is not about undervolting, it's about overclocking. The differences is voltage vs. frequency. OC means we're increasing the CPU frequency beyond stock which is 998mhz in the case of Evo. If you move your SetCPU slider beyond 998mhz, you're overclocking.
The objective of overclocking is speed. The objective of undervolting is battery savings. Snap gives you both. We overclock when we increase the fequency with SetCPU. We undervolt automatically via nHAVS. As of this writing, UV is handled in the kernel, it happens most at the bottom end of the frequency scale.
I hope this helps clear up some of the questions. Great conversation by the way.
Click to expand...
Click to collapse
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Thank you Dragin!!!
That helps a lot! So once you have Snap setup at what you feel is "good" does your phone seem to perform as well as before you had it undervolted? Man, sounds like a pretty involved process - maybe I better wait until I can really sit down and play with it.
goodelyfe said:
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Click to expand...
Click to collapse
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
foueddyf said:
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I think he's talking about when ur figuring out the best setup
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
I had the same issue, left to stock with kingx.
Sent from my PC36100 using XDA App
nyc_zx10 said:
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do you know what in particular Juice is doing to give you better battery life? like what does Turn off certain things based on conditions or?
That is some good battery life.
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
nyc_zx10 said:
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Meh... see I really don't want to do those things. I can turn off data sync myself and just have gmail forward me a text message when I have an email. I just was hoping there was a way to get decent battery life without going back to the days of Winmo
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
berardi said:
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
Click to expand...
Click to collapse
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
DraginMagik said:
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
Click to expand...
Click to collapse
Thanks man, appreciate the breakdown.
You have inspired me, I'm going to bite the bullet and try this snap7.5_925 kernel. I'll report back my luck
I do enjoy this stuff, really - just right now it would be irresponsible for me to spend too much time on it. School comes first right now.
DraginMagik said:
... after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
Click to expand...
Click to collapse
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
loupy said:
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
Click to expand...
Click to collapse
Yeah dragin, don't hog those sweet settings! I'm enjoying Snap 7.6 and it seems to be helping out my battery life a bit, but I'd love to see your SetCPU details.
I've found that the issue for me is bluetooth. If I have it on constantly my battery will drain 10-15% per hour. With bluetooth off it's only draining 1%-2% per hour.
Seems like the bluetooth needs work on CM6 in order to have the efficiency that the other ROMs i've tried (Fresh and EViO) have. Nonetheless, I'm sticking with CM6 and just use the bluetooth when necessary.
I have the same issue with bluetooth on CM 6.0.0. I am running the stock kernel that comes with cyanogenmod, so this is definitely not a snap issue. There was a bug submitted about a month ago:
code.google.com/p/cyanogenmod/issues/detail?id=2136
I *really* hope this can get fixed for the 6.1 release, but it is currently listed with a low priority. I really love CM6, but basically making bluetooth unusable for more than a few hours really makes me struggle with the using this rom.
Why not the 7.6 with turbo...just wonderin
With all these tweaks, ROMS, and kernels out there to completely customize your Evo or whatever phone you have. My question is, how to make sure to you don't over do it.
I know that I will look at signatures and see what posters have done to their evos...and try some of those things myself. You can see my signature to see what I've done too.
I am a noob, but I have almost graduated to the next level (whatever that may be). There might be several people like myself who sees all these tweaks and tweaks out themselves in excitement over what you can do to your new toy.
I get the feeling that some tweaks (kernels, CPU governors, ROMS) can often have functions that can overlap and actually worsen performance rather then improve.
As a request to all those who have conquered the realm of the Evo and aid us lowly lifeforms in modding our phones, can you help us figure out what is just right, not enough, or too much? Besides, too much of a good thing can be bad...
We can start off with my Evo. Been using Linpack as a reference for performance, and have averaged 36.5 MFLOPS on single thread. How does this stack up?
Interesting, and i am by no means an expert, but here some things I have found out.
Don't use Collins ph battery tweak and Setcpu together. Your CPU will peg and kill your battery life.
Setcpu with a Screenoff profile is unnecessary if you have the kernel governor set to smartass. Smartass sets the cpu to 384 with the screenoff anyway.
Don't let your daughter take your EVO in the tub. That limits performance as well.
Add in that benchmark apps, like Linpack, are worthless.
You couldn't hit "too much". Believe me, there are people who flash things daily. Some several times a day. And think about how many mod flashes a dev does to his phone?
I meant running at once...
HipKat said:
Add in that benchmark apps, like Linpack, are worthless.
You couldn't hit "too much". Believe me, there are people who flash things daily. Some several times a day. And think about how many mod flashes a dev does to his phone?
Click to expand...
Click to collapse
Too many things running at once. I figure these phones can handle a lot given the roms people float between...
And you have to remember that all phones are different and that just because I can do something that works great on my phone doesn't mean it will do anything for yours. Or make it worse... Just sayin'
Sent from my PC36100 using xda premium
This question is also hard to answer because peoples taste varies so much.
A good example is myself, I like Sense, but I could care less if it is version 1, 2, or 3, I just want it to work good with no problems. I have never seen a theme that I liked better than stock with just a nice photo as a background. In fact, I could really care less what it looks like as long as everything works well when I want to use it. On the other hand, I have almost no use for any of the bloat apps that came with the phone. I remove almost all of them, Including Facebook, the stock browser, the calender and all Sprint specific apps. But I do have a lot of apps on my phone, about 141 user apps, last time I checked for a total of 264 total apps, including the system apps I have left.
I run Fresh 4.2 rom, that I have modified by removing the aforementioned Sprint bloat and built in apps that I don't want or need. I like Flipz rom's the best because they are stable, reliable, and not updated every day, because no update is needed. Plus he removes the CIQ, which runs all the time in the background. I run a kernel that gives me the best performance and responsiveness, with no-sbc and features like HDMI mirroring and 5-point multi-touch, but other than that pretty much stock (trying out various kernels now so can't say which one I will end up going with). The only other mods I have done is I have changed the splash screen, because the white one would wake up my wife when I would boot my phone in bed at night. I also made a battery indicator mod that reads percentage and is easier to see. And I am running the V6 script to eliminate the Sense reloads when exiting apps.
Works for me, but I am sure a lot of guys/girls wouldn't like it at all. So, in the end, it really doesn't matter what I am running, unless someone else has the same tastes as me. And isn't that really the point?
I think I do a lot for my phone. But not too much. Everything in my sig + setcpu, chainfire 3d, juice defender etc
Deck's + SZ + SuperCharger script + ViperMod script.
Journeyman83 said:
As a request to all those who have conquered the realm of the Evo and aid us lowly lifeforms in modding our phones, can you help us figure out what is just right, not enough, or too much? Besides, too much of a good thing can be bad...
Click to expand...
Click to collapse
How much becomes too much the day you bork your phone when you tweaked something you shouldn't have tweaked, and then turn to the forums for help, only to get an attitude at the people who are trying to help you fix your own f'up. That is when it becomes too much.
wfrandy said:
I run a kernel that gives me the best performance and responsiveness, with no-sbc and features like HDMI mirroring and 5-point multi-touch, but other than that pretty much stock ...
Click to expand...
Click to collapse
Just curious about which kernel you're referring to here ... thanks.
Nothing is to much as long as you are comfortable with the mods. Nand restore if you mess something up. If you need any help pm me ill help ya.
Sent from my PC36100 using XDA App
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Deshabilitado said:
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Click to expand...
Click to collapse
I cover this in the guide I wrote in general (which has been pushed down quite a ways) but anyways here goes another version.
Overclocking varies from device to device, even of the same model. Variances in tolerance is on a per chip basis, as long as they pass within a certain range they are sent out for production in devices. Overclocking in general is within means of the chip's abilities, if it isn't, you'll know it. Generally speaking, 1.4 GHz is perfectly fine on our devices. 1.5 GHz is also usually ok, but is the upper end of what the Tegra2 can usually tolerate. Few an go past 1.58 GHz, my old G2x's tegra2 could hit 1.7 GHz,but that's well beyond "normal" range.
Overclocking a device is the same as overclocking a PC, you need to be careful with it. Don't just ramp it to 65% overclock and expect it to run fine. Every chip is different. Do it in steps, and test each step before moving on. Test it in normal usage, test it in heavy usage, gaming, etc.
An overclocked device will certainly run hotter then normal, it's running faster, drawing more power, and that creates a hotter running core, no way around it. Keeping in mind there is no airflow in these things, that makes the biggest enemy to CPUs even more dangerous.Does it run so hot that it can shorten component life? Sure it can. Will you still have the device when it happens? I doubt it. Likely, we'll be on Tegra5 before it even begins to show signs of stress.
One of the nice things, though, is our CPUs range so much in speed according to load that just because your Max is 1.5 GHz, it doesn't always run there. Most times, it won't even be in the overclocked speeds. Does it run faster? Sure does. Benchmarks will raise nicely, and games that maybe got choppy before will smooth out, movies that couldn't play well will be fluid, the heavens will align, mankind will discover world peace and I'll win the lottery.
All that being said, I don't usually overclock, in fact I tend to underclock a little to 800MHz. Its usually sufficient to do normal tablet stuff, and I adjust the speed according to what I require. If my movie is lagging, I'll bump it up until it smooths out. Same for a game if it needs it.
In the end, its all personal choice, really. Just because you CAN overclock, doesn't mean you NEED to. IMO a well tuned governor will give as good a result as overclocking in normal usage, and a good I/O Scheduler will also help alot, without adding anymore heat or stress to your device.
TL;DNR:
Overclocking is fun. It causes more heat. It likely won't explode within the time you own it. Or your children. Your battery will suck.
thanks pio for the answer, thats what i needed to read, cuz usually when u talk about OC its like "yeah dude, OC its "tha greeeeeat doi it dude" or something like "dont do it!!! u will decrease your tablet life" and yes, i know that devices are way to diferent even if they are the same model, and also im agree with u, governors and I/O works better than OC but we dont have many for our device, i miss the smartass v2 governor,or the brazzilianwax too, but well, hope someone can port it for us someday.
I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks
jpzsports said:
I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks
Click to expand...
Click to collapse
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.
cmlusco said:
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.
Click to expand...
Click to collapse
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?
It's hard to even guess unless you can get a log. If you give one of the stock based ROMs another trial for a few days, and the phone does not reboot, then it is safe to say it is not hardware. I'd start by at least ruling out the hardware possibility.
Do not use Titanium or some other app to restore any sort of data from one ROM to another. That often seems to cause a lot of people problems.
If your phone isn't that hot, I agree that heat isn't likely the problem. Mine absolutely roasts while navigating (while charging, screen on, gps and 3g antennas on, music playing, overclocked, weak original stock battery, otterbox case so it can't breathe, etc.) and it doesn't ever reboot from heat.
Everyone uses their phones differently. So what may be stable for one person might not be for others. I've come to the conclusion that there is only one person who can determine if a ROM is stable... that is the one person who uses it everyday. Just because some other people are using a ROM and getting good results, it doesn't mean that you ever will (even with you wiping/flashing/installing apps by the book).
CM9, CM10, or any and all ICS and JB roms are going to have things that aren't working right for some time still. It's just the nature of the beast. App compatibility, especially, is just one of those things. It's a testament to how good those awesome devs are that anything works on our Dinc running JB and ICS.
I never ran the ICS and JB ports for long (in fact only very short periods of time) because my problems far outweighed the benefits. There is no shame in GB working better for you. I run a variant of CM7 (which is gingerbread)... it is definitely different than stock-sense. Then I use alternate launchers (Go launcher is my favorite) to change it up even more. You can do so much customization that isn't dependent on the ROM. Then I can use something like ROM TOOLBOX PRO for even more customization.
Software is not fashion. What actually works never goes out of style (despite what the hipster kids on xda might be saying ...get off my lawn... grumble...)
jpzsports said:
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
Click to expand...
Click to collapse
I would use incredicontrol and raise all max voltages by 25 or one push of the plus button. Sometimes as phones get older the processors get worn , and have issues with not enough power or even with the stock max frequencie of 998mhz. If raising the max voltage dosent help, i would underclock down from max 998.
Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.
jpzsports said:
Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.
Click to expand...
Click to collapse
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...
musical_chairs said:
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...
Click to expand...
Click to collapse
That is true, if i go down to 128 i have screen on freezing issues, and random reboots.
EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?
Click to expand...
Click to collapse
This is certainly a clue... but I don't know what it means...
I would not think the the extended battery would produce more heat. Since both batteries should be discharging at the same rates the heat output should be the same (just that the bigger one would take longer since it has more reserve). I've ran across stories of people who had phones that went completely wonky when they tried swapping batteries or getting a new one. I really don't know anything about it, I'm still on my stock battery.
It certainly couldn't hurt to try wiping your battery stats in clockwork. There is apparently some magic methodology to do it "correctly". I don't know about that either... here is a thread.
http://forum.xda-developers.com/showthread.php?t=1359395
Well just as an update, I tried the overvolting and clearing the battery stats but still got the reboots. I installed one of the Stock Sense ROMs and it's been running great with no reboots. Apparently my phone just doesn't like non-Sense ROMs for some reason. Oh well. At least I have a working phone. Pretty amazing how fast the stock rom runs!
Well, I guess it's good to hear the hardware is ok.
You still could try out the CM10s (or other JB roms) by starting off without installing your apps (if you can live without them). App compatibility might be your problem. Let it run for a while with no additional apps added. Then, add them back slowly (one or two a day or every couple of days) from the market only. If the reboots start up later on... you will probably recognize the one that is the source of trouble.
Of course you still have plenty of options in the gingerbread family to choose from. If you've never tried out some GB AOSP/CM roms, that would be worth a try. You've got stock roms, stock roms with sense removed, and the whole variety of AOSP/CM7 (official and unofficial) to choose from. Launchers...themes... mods... etc... all kinds of ways to change from whatever you start with. The only GB roms that I ever had problems with were the official "stable" CM7.0 and CM7.1 ROMs. I've been running one unofficial CM7 build (about 99.99% of the time...except to test drive newer stuff) for almost a year. Its been the best thing that's ever happened to my phone.
Dear ppl of this fourm you kick butt. I was able to unlock and root my g power 2022. I'm a little nervous I can't get twrp back up working, I know it's out there I just want it more main stream.
Here's my question. Over clocking is it possible on this phone. The battery is great and at the end of a long day I'm well over 60% I'd love to turn the clock up on this phone. All the apps you see on ps don't do anything, they also say 2301 is the max mhz. Is it a locked CPU????
Thanks for your time guys and girls
Overclocking a phone is not advisable, because of the extremely limited cooling capacity.
Also, don't use profanity on XDA. Post edited.
I'm very sorry about that. Thanks for fixing it.
I did some bench marks of my phone and the temp bearly moved. I understand the heat that builds up during over clocking and also that mounting a water cooling solution is not possible. I just wondered if it was possible to move the cpu clock ???
Any other ideas on speeding it up??? I'm sure there is a ton I don't know about.
So I did find an app root booster. It's free for the basic over clocking and you can go extreme for a one time but. I am using the free version. And I picked up 6 points on 3d mark. The phone has been very stable all day. It's all preset stuff. Witch is probably better than trial and error.