Im running liquid gingerbread v3.0 and no matter what I do if I change the processed speed while it boots up over 1.42 it locks completely up and I have to do a battery pull and sometimes if I boot up above 1.42 it locks up randomly anyways I've tried a wipe and I tried a different kernal imoseyen 6.2.1 I believe im gonna try one more kernal and will update the results but I don't have much hope
Sent from my HTC ThunderBolt using XDA App
hunterjackson92 said:
Im running liquid gingerbread v3.0 and no matter what I do if I change the processed speed while it boots up over 1.42 it locks completely up and I have to do a battery pull and sometimes if I boot up above 1.42 it locks up randomly anyways I've tried a wipe and I tried a different kernal imoseyen 6.2.1 I believe im gonna try one more kernal and will update the results but I don't have much hope
Sent from my HTC ThunderBolt using XDA App
Click to expand...
Click to collapse
Some phones can't handle OC'ing. Yours may be one of those.
madzozs said:
Some phones can't handle OC'ing. Yours may be one of those.
Click to expand...
Click to collapse
this is correct... i can clock mine up to ~1700 no problems, untill the screen goes to sleep and then all goes south if i keep it under 1400 its all good. but honestly there is no point to going over 12-1300 benchmark results are neglegably improved and you are killing your battery and running the risk of burning up your equipment.
Each ThunderBolt handles overclocking differently as mentioned above. The expansion and contraction of the metal and other materials when heating and cooling vary from device to device, so one thunderbolt might be able to get up to 1.7GHz, and another might not be able to handle 1.2GHz.
Also, as mentioned above, clocking over 1.2GHz is really pointless. I honestly never overclock my phone. No need in my opinion.
Like mentioned above I really see no need to go above 1.4, but if you wanted you could always raise the voltage on those higher frequencies so it wouldnt lock up.
Thank you guys it isn't really that I want or need to go over 1.4 and I rarely ever do it is more me being a perfectionist. But its strange Ive had liquid before on here and it always ran five and I usually left it at 1.5 and it never really started acting weird till about 1.8 and it was the same version v3.0.
*Edit* just out of curiousity I booted up and older recovery of liquid 3.0 with the stock kernal and it ran up 1.8 fine?
Sent from my HTC ThunderBolt using XDA App
Different roms run different kernels/versions of kernels, which in turn use different voltages. If a kernel was undervolted, its less likely to handle higher speeds.
Sent from my HTC Thunderbolt powered by KillaSense 3.5.0
Are you clocking that high just to do it?? In reality I just use smartass v2 and clock at 1222 and it stays snappy and doesn't demolish my battery...
Sent from Shift Ao5p ic3 overclocked unlocked and ready to rock.
I must be a lucky one. I overclock to 1.7 and my phone runs super stable.
Sent from my ADR6400L using XDA App
That's the thing though it's the exact same rom liquid gingerbread v3.0 with the stock kernal I can go up to 1.8 before it gives me any problems and even then it just acts weird
Sent from my HTC ThunderBolt using XDA App
Related
I have to say, the random reboots sucks. I am running Bamf 1.6 remix. I wiped two times, and keep getting reboots every so often. I wish someone could figure out what the heck is going on
Nobody is going to figure out what the heck is going on without any information. What are you doing when it reboots? Overclocked? If it rebooted when u are using the browser make sure you have flash installed.
dirtyfingers said:
Nobody is going to figure out what the heck is going on without any information. What are you doing when it reboots? Overclocked? If it rebooted when u are using the browser make sure you have flash installed.
Click to expand...
Click to collapse
I did over clock . Over clocking can cause that huh? I did put it back down to 1ghz and have not have any more reboots
Mine runs steady at 1.5ghz. Any higher and I get random reboot.
Sent from my rooted Bolt running VirusROM + leankernel extreme 1.92
Each phone is different. Some can handle 1.9ghz oc and others can't handle any. Also undervolting makes a processor less stable as you are running higher speeds with less power.
No, thats not a storm. Its just my Thunderbolt layin down this post.
Are you on the newest Radio? Some people are reporting that the Leaked Radio is causing the problems. I did notice that after I flashed the leaked radio. I started having random reboots.
Leaked Radio.
I for one can second that comment about the leaked radio. I've noticed a lot more reboots since flashing the new radio... especially after the 4G outage last week and changing my phone over to Rev.A. I just turned Rev.A off after the third reboot of the morning... Hopefully that will get rid of some of them. If not, I'll have to flash back. I like the better GPS locks, but they don't do much good when my phone is rebooting itself sitting on my desk.
EDIT: Didn't help. Just rebooted again. Guess I'm going back to the old radio.
herbiehusker2608 said:
I did over clock . Over clocking can cause that huh? I did put it back down to 1ghz and have not have any more reboots
Click to expand...
Click to collapse
Yes it definitely can, hopefully that fixed your problem and bamf 1.6 is a sweet ROM you should really like it.
I have had the new radio since it was released and never had a single reboot so that must not be affecting everybody. Maybe it is another factor causing reboots?
please check out my post http://forum.xda-developers.com/showthread.php?t=1094355
CM7 on the atrix appears to heat up rather quickly. Is this due to the Kernel but faux123 has mentioned (slave processor not able to be under clocked yet)? Has anyone else solved the heating issues? I've seen a bunch of posts on this, but i could never find a straight answer. Sorry if i missed it.
Undervolting seemed to fix that problem for me. I I also run at 1000 mhz rather than 1100.
sent from my Atrix via XDA premium
I actually felt less heat with CM7. Just make sure you have the kernel that came with CM7 not faux's 1.3 GHz one. Also, if you still feel it gets warm, try setting profiles in SetCPU. And if that doesn't work, read about undervolting and then try it if you're up for it.
plus one for the less heat, at first i had more but that was when i just flashed it and was charging + putting everything back on.
cm7 after boot up with same apps gives me 560mb ram, Alien #4 like 360. Blur takes alot out of the phone, also they have the fingure print scanner working and will hopefully be out next update of cm7
this phone on cm7 not being overclocked is like alien on steroids. mine boots up in like 5 seconds TOP i cant say much about the battery as Atnt in my town the last 2 days have been screwed up. cant get service for the life of me 3g dropped calls instantly. i just found out forcing it to egde everything works, but i think they finally fixed it tho.
Undervolting helps with the heat.
Sent from my CM860
Is it worth the hassle of flashing the new ics leak and roms? ive been running clean rom 1.7 ics and its been fine does the new leak and roms based off of it have a performace boost worthy of the hassle of relocking and unlocking again?
I was very hesitant at first weather or not to do it. Now that I've done it and am running cleanrom 4.0 its performance is better and i, myself, am getting way better battery life. Go ahead and do it! Look for Scotts tut on how to do it. Follow it and its really easy.
Its def worth it and its rather easy if u just follow the directions.
Is there anyway to go back to GB after if you find it is not best for you?
mc_365 said:
Is there anyway to go back to GB after if you find it is not best for you?
Click to expand...
Click to collapse
yes very easily.
just load up GB kernel, and flash GB ROM..
Thanks Andy bones
Sent from my ADR6425LVW using Tapatalk
It's got some nice things in it that I like, but I have to mention this -- my phone's running a lot hotter. And it doesn't seem like any of the usual tricks (airplane mode, CDMA, etc.) are taking any of the load off the battery. Power settings say the juice is all going to the display, but I seriously doubt that -- it's staying plenty hot even when I keep the screen off.
Also, I've never liked the fact that this phone discharges while on even when connected to a power source. They really need to keep consumption inside USB's ability to charge. If you leave it on all day even while plugged in to power you'll have a low batt after a few hours. That's ridiculous.
Did you change your CPU governor to conservative? That is one of the things on my check list to do when flashing. It really keeps it alot cooler.
Also know that if you flash back to a gb Rom you probably won't have access to external memory
Sent from my ADR6425LVW using xda premium
EmerikL said:
Did you change your CPU governor to conservative? That is one of the things on my check list to do when flashing. It really keeps it alot cooler.
Click to expand...
Click to collapse
How is this done? I never had to do this before on a previous build/device.
I use ROM Toolbox.
Its under the Performance tab, CPU controls. 1512 max 384 min governor set to conservative.
jumpoff609 said:
Also know that if you flash back to a gb Rom you probably won't have access to external memory
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Scott has a fix for that
http://forum.xda-developers.com/showthread.php?t=1453324&page=431
download from post #4303
You should stop what you are doing and flash right now... If you follow the steps, you can be done in an hour. ICS is worth it.
Sent from my highly modified ICS Rezound.
Ok, so i was super excited to hear that we are finally able to overclock, been waiting to do this since i picked up this phone and put down my OG Evo.. anyways, i tried Dread 7us's app Overclock v1.0, and installed it, pulled up Setcpu and i can see but it doesnt stick.. i pull up quadrant and look at system information. the max freq is set at my desired freq (1809MHz) but the actual never goes above 1512MHz. i go back into Setcpu and it says the same thing, max is 1809 but it doesnt go over 1512.
so i thought it could be the rom, i was on Rejuv 1.5, so i switched to OMJ 1.1 and same thing. Then Overclock v1.1 came out and i tried that with no luck, doesnt stick.
Then MeanRom 1.0 came out, and my phone hasnt really liked this rom but i wanted to see how it would do with the OC built into the rom at 1.72GHz. I get it all set up and go into quadrant and check my settings and the same thing, it shows max at 1.7GHz but my actual never goes higher than 1.5, even my quadrant scores do not change
i dont think im the only one having issues, i have heard of a few others having issues with it sticking, and the ones who think it is and post up quadrant scores of 5000-5200, my phone is doing that without being OC'd..
i have rooted many phones and flashed 100's of times, but havent ran into this before. Anybody got any idea's as to why this may be happening or any ideas i can try to see if it will stick
thanks for the help guys
Just wondering where your checking the frequencies.
Sent from my EVO using xda app-developers app
Like I stated in the OP, I used Setcpu and quadrant
Sent from my Supercharged ELiTE
harvickgm said:
Ok, so i was super excited to hear that we are finally able to overclock, been waiting to do this since i picked up this phone and put down my OG Evo.. anyways, i tried Dread 7us's app Overclock v1.0, and installed it, pulled up Setcpu and i can see but it doesnt stick.. i pull up quadrant and look at system information. the max freq is set at my desired freq (1809MHz) but the actual never goes above 1512MHz. i go back into Setcpu and it says the same thing, max is 1809 but it doesnt go over 1512.
so i thought it could be the rom, i was on Rejuv 1.5, so i switched to OMJ 1.1 and same thing. Then Overclock v1.1 came out and i tried that with no luck, doesnt stick.
Then MeanRom 1.0 came out, and my phone hasnt really liked this rom but i wanted to see how it would do with the OC built into the rom at 1.72GHz. I get it all set up and go into quadrant and check my settings and the same thing, it shows max at 1.7GHz but my actual never goes higher than 1.5, even my quadrant scores do not change
i dont think im the only one having issues, i have heard of a few others having issues with it sticking, and the ones who think it is and post up quadrant scores of 5000-5200, my phone is doing that without being OC'd..
i have rooted many phones and flashed 100's of times, but havent ran into this before. Anybody got any idea's as to why this may be happening or any ideas i can try to see if it will stick
thanks for the help guys
Click to expand...
Click to collapse
You stated that setcpu was used for verification. You have to use setcpu to set clock speed also. Dread7us' apk is kind of like setting the threshold max, so you can use a 3rd party app (setcpu) to OC. Hth.
Yes I know that.. and that's what I have done, but it does not stay. The max freq will say 1809 but the ACTUAL FREQ will never go above 1512 which is stock. This is what I'm trying to figure out and why
Sent from my Supercharged ELiTE
Here is a screenshot of what I saw when I opened Setcpu back up.
Sent from my Supercharged ELiTE
I had the same issue when I tried the OC... I checked in SetCPU, Quadrant, and System Monitor with the governor set to performance. Clock speed stayed at 1500MHz no matter what.
I uninstalled the OC APK and am just sticking with stock until we can get some proper kernels out. The stock speed is fast enough for everything I want to do realistically.
I had the same exact problem and run fresh rom. It would stick for normal use but as soon as I ran a benchmark it dropped to 1.5 again.
i had to install mine to internal memory. by default it went to phone. set it to internal you should be fine.
kaos420 said:
i had to install mine to internal memory. by default it went to phone. set it to internal you should be fine.
Click to expand...
Click to collapse
What did you install in internal memory?? Please explain what exactly it is what you did.
Maybe u can help us all figure this out
Thanks a lot man
Sent from my Supercharged ELiTE
harvickgm said:
What did you install in internal memory?? Please explain what exactly it is what you did.
Maybe u can help us all figure this out
Thanks a lot man
Sent from my Supercharged ELiTE
Click to expand...
Click to collapse
The oc program script. Wouldnt work till i installed to internal. Same for. Setcpu
Sent from my ice cream powered Evo Lte!
kaos420 said:
The oc program script. Wouldnt work till i installed to internal. Same for. Setcpu
Sent from my ice cream powered Evo Lte!
Click to expand...
Click to collapse
you mean installing the apps themselves on the internal memory and not the SD card. right? well i never install my apps on my SD card, so thats not the issue
It is when . They auto default to phone storage. Move them to internal like i said.
Sent from my ice cream powered Evo Lte!
I used the OC app in the original overclock mod post, installed setcpu, and then turned it up from there. I am using MeanRom. Not sure if anyone else has stated but you have to remember to set up in the OC app
Sent from my EVO 4G LTE using XDA-Developer App
Sent from my EVO 4G LTE using XDA-Developer App
EVOMIKE025 said:
Sent from my EVO 4G LTE using XDA-Developer App
Click to expand...
Click to collapse
ok, open quadrant and look at ur freq under system information. and look and see what ur actual freq stays at?
I Have the MeanBean and when I overclock and undervolt it works ok for a wile but after about 2 or 3 hours it will reboot untill I have rebooted it myself then its ok for a wile. I have tried to run as normal volt with overclock and same thing happens but if I overvolt and overclock to the 1.7 it runs ok. When I was on meanbean 2.8 the overclock was built into the rom. can someone tell me why this is and what I can do to get it stable and how far I can go with the overclock and voltage.
It's actually varies, some phones can't oc at all, some can only to 1.8 and some can go all the way to 2.1. Same goes for voltage. It's best to see how your phone reacts to each. So if 1.7 works for you then that might be your phones limit.
Sent from my EVO using Tapatalk 2
jdmohn12 said:
I Have the MeanBean and when I overclock and undervolt it works ok for a wile but after about 2 or 3 hours it will reboot untill I have rebooted it myself then its ok for a wile. I have tried to run as normal volt with overclock and same thing happens but if I overvolt and overclock to the 1.7 it runs ok. When I was on meanbean 2.8 the overclock was built into the rom. can someone tell me why this is and what I can do to get it stable and how far I can go with the overclock and voltage.
Click to expand...
Click to collapse
Each phone is different. Some phones handle overclocking/underclocking and over/undervolting better than others. What works for one may not work for the other. Find the setup that best suits your needs and stick with it.
The advice is free....the bandwidth, not so much
will this all change with the rom that I am using or is this all just in the phone? when I was on meanROM it was overclocked to 1.890 and it ran great, now I am not sure if I can get back to that or not. not tried it yet, going to see what happens after a day or two then try going up from there.
jdmohn12 said:
will this all change with the rom that I am using or is this all just in the phone? when I was on meanROM it was overclocked to 1.890 and it ran great, now I am not sure if I can get back to that or not. not tried it yet, going to see what happens after a day or two then try going up from there.
Click to expand...
Click to collapse
Well it could be the kernel used for now. Since htc has not released source, mean bean is using a hacked stock kernel. When you were on mean rom the oc and and voltage tables where written into the actual kernel source. Until htc releases the source that can not be done.
Sent from my EVO using Tapatalk 2
I think some of the variables affecting how the phone runs has to do not only with the phone itself but the ROM, also. When I was on ICS I ran Viper4G with a custom kernel OC'd to 1.9 and my phone ran without a hitch. I haven't been able to do the same since I've been on JB. Having said that, keep in mind that the kernel source for JB hasn't been released yet (as stated above). Once the source drops you'll see improvements in the kernels and how the phone runs overall
The advice is free....the bandwidth, not so much
and as we all know there is no telling when they will release that code. Thank you for the quick answers. I will see what happens in the next day or two.