What is the best overclock app for a rooted Eris running Froyo 2.2?
What is the best min/max setting too for performance?
I use SetCPU. It really depends on what you want.
I want the best performance possible, without overheating my phone
No matter what you're going to heat up when overclocking. If you use setcpu don't use the widget.
What's the safest maximum performance setting then?
What about overclock widget app (free)? I'm using that now. It seems ok, not sure though compared to setcpu.
ChadZ said:
What's the safest maximum performance setting then?
What about overclock widget app (free)? I'm using that now. It seems ok, not sure though compared to setcpu.
Click to expand...
Click to collapse
that widget app sucks. it's nothing compared to setcpu. I run 768max 19 min, and I have a full day of battery life, using it fairly regularly every day. I rarely have lag, and it's fast too.
using kayosfroyo btw.
Every processor is different. Some people get get to 844mhz, some people can't push past 710mhz. You need to find what's right for you.
I personally get up to 787mhz.
I run 806 all day no problem. But faster is a reboot. All phones seem to be different on their safe max w/o crash. I use setcpu myself. It's free on this fourm for members.
Sent from my Cyno Tazz 3.0 using XDA App
Yes, SetCPU is best. I can clock mine to about 806 and I get about 48 hours of battery... every phone is not the same, remember that!
using setcpu here as well. 825mhz no issues
Im using set cpu as well at 768 max and 245 min. Make sure u dont have set on boot if ur going to test the limit of ur phone, I did and was able to go 806 and past rat my phone locks up and on every reboot the same so I had to uninstall in using command prmpt from pc
Sent from my FroyoEris using XDA App
SicNside, were did you find the info for OCing? I don't quite get the whole "minute" thing. Can you point me in the right direction, as in a guide with explanations and recommended settings? Every post I find about OCing the Eris is old, and says "hasn't been done"
Sent from my FroyoEris using XDA App
Yeah ill type out what my settings r to give u an idea, later when I get home to access a computer.. what I meant for min= minimum
Sent from my FroyoEris using XDA App
Read this page http://forum.xda-developers.com/showthread.php?t=761940 and it will give you a little understanding on setting up for performence and setting up for performence With Higher battery life. This is the place i liked the best only because i needed increse speed with out loosing to much battery power due to not being in a place to set phone on the charger like i work 9 hours a day and i like to listen to music and fiddle on my phone on breaks.. Plus honestly my phone does not seem to be performing any slower than it was with a high performence setup i used to be 480 min with a 787 max, and somtimes higher but 245 min with 748 or 19 min with 748 i still have not noticed anything being slower than when i had it set at 480 min 787 max..
But i cant stress enough that dont have it set on boot when u are trying to find ur phones limits because if u do have it set and find ur phones limits u will have to adb that crap to uninstall it. find the settings u want for your phone before you set on boot
Edit: And i have also been seing people post that after testing they have not found there Eris being any faster than 710 just that higher decreses there battery life. Which is Maybe why kaosfroyo has it alrdy clocked at 710 but i dont know, you cant quote me on that.. I hope i was of some help
Related
I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Notxok said:
I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Click to expand...
Click to collapse
If your phone is running ok and getting too hot then 768 should be fine, many of us run 806 without a problem. I think stock CPU is set at 528 (maybe lower, I don't remember)
BTW this should probably be in Q&A board
Sent from my nonsensikal froyo
I run 768 with no problems.
SikYou said:
If your phone is running ok and getting too hot then 768 should be fine, many of us run 806 without a problem. I think stock CPU is set at 528 (maybe lower, I don't remember)
BTW this should probably be in Q&A board
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
806 are you ****ting me?... is it set to performance?
Notxok said:
806 are you ****ting me?... is it set to performance?
Click to expand...
Click to collapse
Interactive
Sent from my nonsensikal froyo
Hmmm. I'm trying 806 now.
SikYou said:
Interactive
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
806 in interactive rebooted for me.. I might have to reflash a ROM now LOL... lucky I wish I could run 806 efficiently
You should never try clock speeds without disabling "Start on boot" or you can really screw yourself over....
Anyway, 768 is a very common speed for people to be able to hit. I personally become unstable at 806 (especially with JIT on) and I stick to 787.
Hungry Man said:
You should never try clock speeds without disabling "Start on boot" or you can really screw yourself over....
Anyway, 768 is a very common speed for people to be able to hit. I personally become unstable at 806 (especially with JIT on) and I stick to 787.
Click to expand...
Click to collapse
Your 486 Makes me Envious.. Would you mind PMing m your set-up ( ROM Set CPU info and current task killer? )
My 486 was a while ago and doesn't really reflect the overall performance of my phone; as in my phone is currently faster but I get lower quadrant scores (440-450)
I was on Tazz V6 I believe, clocked to 768mhz performance, with BFS V2 or V3. After rebooting and flashing the kernel I was getting high 470's and mid 480's so I took a picture with my girlfriend's Incredible.
JIT was at 16m and I'd just switched from 24 to 16 and wiped dalvik. This is significant because anytime you switch your dalvik heapsize and reboot your quadrant scores will be at their highest, not sure why, probably has to do with RAM allocation.
Hungry Man said:
My 486 was a while ago and doesn't really reflect the overall performance of my phone; as in my phone is currently faster but I get lower quadrant scores (440-450)
I was on Tazz V6 I believe, clocked to 768mhz performance, with BFS V2 or V3. After rebooting and flashing the kernel I was getting high 470's and mid 480's so I took a picture with my girlfriend's Incredible.
JIT was at 16m and I'd just switched from 24 to 16 and wiped dalvik. This is significant because anytime you switch your dalvik heapsize and reboot your quadrant scores will be at their highest, not sure why, probably has to do with RAM allocation.
Click to expand...
Click to collapse
I don't get above a 415-420 really.. any suggestions or help?
Notxok said:
806 in interactive rebooted for me.. I might have to reflash a ROM now LOL... lucky I wish I could run 806 efficiently
Click to expand...
Click to collapse
806 seems to be running a fraction faster but to me it is hardly noticeable coming from 768.
Notxok said:
I don't get above a 415-420 really.. any suggestions or help?
Click to expand...
Click to collapse
Don't read too much in the benchmarks . I usually run happily around 430.
I use SetCPU (interactive 768 / 245)
I don't run any task killers, in my experience they are more trouble than they are worth.
The other thing IMHO if you don't use an app, get rid of it.
Task killers are in fact more trouble than they're worth, especially automatic ones. I use advanced task killer and I only ever kill tasks right after my phone has started up/ when my phone is plugged in. Task killers hurt battery life and performance.
Hungry Man said:
Task killers are in fact more trouble than they're worth, especially automatic ones. I use advanced task killer and I only ever kill tasks right after my phone has started up/ when my phone is plugged in. Task killers hurt battery life and performance.
Click to expand...
Click to collapse
Thanks Guys... Ill keep that in mind.. I was using auto memory killer
Notxok said:
I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Click to expand...
Click to collapse
In my personal experience, I would disable set on boot in SetCPU and start gradually bumping the speed up. Usually at 787 my phone runs best (fastest and most stable). Then, I'd go back and bump it to 806. It WOULD run but after about 5 minutes of playing with my phone it typically causes it to lock. 825 Causes an immediate lock. So I typically leave it at 787 and all Froyo roms seem to run fine at that for me. I don't even test anymore...just restore SetCPU app and data with Titanium on initial boot of a new rom. So far, no problems.
Sent from my ERIS using XDA App
What's the best setting? Ondemand? Interactive? Prefermance..etc
Sent from my VANILLA TAZZ using XDA App
806 no problem using the Collins script.
Anything higher than 710 on my phone locks it up.
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Franzie3 said:
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Click to expand...
Click to collapse
i think you have to wait for the source code for the kernal to be released and tinkered with to get anything useful from all that...but who knows
Yup. About all you can use it for right now is throttling (which isn't bad... the CPU is plenty fast already). It'll help save battery, at least.
Odinist said:
Yup. About all you can use it for right now is throttling (which isn't bad... the CPU is plenty fast already). It'll help save battery, at least.
Click to expand...
Click to collapse
Agreed. That's all I use it for now.
I have it set to the following:
Screen off = 245 max
Charging = 1024 max
Battery < 10% = 245 max
Battery less than 25% = 768 max
All other istances = 1024 max
It will do for now until we get custom kernels.
SuperFly03 said:
Agreed. That's all I use it for now.
I have it set to the following:
Screen off = 245 max
Charging = 1024 max
Battery < 10% = 245 max
Battery less than 25% = 768 max
All other istances = 1024 max
It will do for now until we get custom kernels.
Click to expand...
Click to collapse
pretty much what I did, minus everything but the screen off
I always set the screen off on my evo 4g to 245 max, and will probably do the same here. Kinda waiting for kernal source code to be released so I can use the smartass governor. I always liked that one.
Franzie3 said:
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Click to expand...
Click to collapse
I downloaded Quadrant immediately after rooting w/o installing SetCPU & first run pulled off a 1926...second run a 2000 flat! So I installed SetCPU & set it to performance & the most I got was mid 1800's which is what I was pulling off before I rooted.
I remember on my droid playing around with the up threshold & it would speed things up & so I did but still stayed at consistent 1800's. Uninstalled & I'm running 1900's consistent, only hit 2000 once lol.
I cannot wait to tinker once HTC releases the kernel source!
mthorn79 said:
I downloaded Quadrant immediately after rooting w/o installing SetCPU & first run pulled off a 1926...second run a 2000 flat! So I installed SetCPU & set it to performance & the most I got was mid 1800's which is what I was pulling off before I rooted.
I remember on my droid playing around with the up threshold & it would speed things up & so I did but still stayed at consistent 1800's. Uninstalled & I'm running 1900's consistent, only hit 2000 once lol.
Click to expand...
Click to collapse
quadrant scores don't mean everything. If you installed SetCPU and noticed a speed decrease then there would be a reason to not want it, but just because you get a lower score in quadrant?
*EDIT* just thought I'd say, I just ran Quadrant with SetCPU on performance, and got a 1978 score. So I DK what you are talking about.
HTC really needs to release the source code. To my understanding it should be out sooner than later? I sure hope so...
nosympathy said:
quadrant scores don't mean everything. If you installed SetCPU and noticed a speed decrease then there would be a reason to not want it, but just because you get a lower score in quadrant?
*EDIT* just thought I'd say, I just ran Quadrant with SetCPU on performance, and got a 1978 score. So I DK what you are talking about.
Click to expand...
Click to collapse
Ok I'm not an idiot, I know quadrant scores don't mean anything but some people use it as a gauge to get an idea on how their phone is. (If u feel it does nothing for you then don't use it if u don't want to no one asked you to)
If you know anything about phones you know certain people's will vary in speeds, I'm just posting my experience...this IS afterall a "Post Your SetCPU Settings' thread, so don't be getting all uppity.
Sent from my ADR6400L using Tapatalk
Jimmy058910 said:
HTC really needs to release the source code. To my understanding it should be out sooner than later? I sure hope so...
Click to expand...
Click to collapse
Yes. I think they releases it within 45 days or something like that. It will most certainly be here soon.
Sent from my ADR6400L using Tapatalk
Any incoming call issues with Screen Off set at 245?
Steeler86 said:
Any incoming call issues with Screen Off set at 245?
Click to expand...
Click to collapse
no and their shouldn't be, unless you down the road, since you couldn't do it now, use one of the governors like Conservative which tend to really slow the phone down. On my Evo 4G it used to take a good 30 seconds to unlock the screen is I used that with screen off at 245Mhz.
1570 for me on stock rom.
I got 2000+ quadrants on stock ROM. SA for setCPU, I can't get my CPU to clock down by force with any app. I think the kernel source is going to be needed. Probably have perflock on like they did on my inc. Let me know if setCPU works please.
SetCPU works, you just have to hit the menu button and click "disable perflock"
1376 on VirusRom but it is soooo snapppy
Seems to be working for me. 39% battery after 12+ hours. Just with the "screen off: max245" setting.
Sent from my ADR6400L using XDA App
We finally got the source code!
Do I need to flash this to overclock
http://forum.xda-developers.com/showthread.php?t=1016916
or can I wait for SetCPU to update?
Hei guys, I'm really, really new to this.
I've just flash andy's port of CM7 based on 2.3.4. I'm having a really though time with the battery, it goes down 50% faster than on my previous 2.2.2 official Froyo from LG.
Anyway, this question is about overclocking.
So, inside CM7 settings there's this "Performance" menu, in which you can go to "CPU", I've set there smartass governor, minimum 122 and maximum 768.
What does that mean? Does that mean I'm overclocking my CPU? Does it mean that smartass will allow or push the CPU to 768 when it's needed? Do I need to do something else in order to achieve that? (i.e - use get the CPU at 122 while screen off and increase it according to demand up to 768). - that's what I'm after.
Any response on the topic(s) much appreciated.
Thanks.
Regarding battery - calibrate it with the app from the market
Regarding OC - yes, when you'll use the phone your cpu will run at 768 mhz (note that you might get kernel panics). Your minimum speed is pretty low and it will take a little longer to get to 768... you will see some skips or lags.
Oh, and yes! You're overclocking and smartass will do what you're looking for (idle-122/in-use-768).
Sent from my LG-P500 using XDA Premium App
I would kick the min up to 480. That usually gives you a good balance.
Sent from my LG-P500 using XDA App
Thanks for the fast response.
As for the battery, I tried calibrating it and still the same.
I'm reporting 10% (exactly) each 2 hours, in idle, screen off, everything turned off except mobile data on EDGE.
At this rate, the phone goes dry in exactly 20 hours with minimal to no use. This isn't normal.
It heats up when charging (more than usual).
In battery stats I have all the four ones (android system, cell, etc.) at 25%.
No apps installed.
Just a few hours ago I tried replacing the stock kernel of andy's with the latest from franco (16) and zram.
Exactly the same.
I don't know what else to do, I already reflashed it twice. Same results. I can't post to the development forum just yet (not enough posts).
I guess I'll just go ahead and try mik's port... although I wouldn't want to, I love this one, everything works perfectly except the battery thing.
Did you use google maps?
"Known bugs
[...]
- Google Maps is eating your battery, kill this app after using in Setting->applications
[...]"
i think smartass does automatically change your cpu's frequency when you need it..but your minimum frequency is too low..change it to 320 Mhz....and are you using 3g all time..??
Yes, used google maps but killed it. Second reflash didn't even install it and still the same problem.
No, I didn't use 3g at all.
I only kept mobile data active on EDGE. and as I said, it was in idle. it's like the phone was used 24/7 even in idle.
and why is my cpu to low? the phone works like a charm with that frequency.
Check the 2 g networks only box in settings-networks- mobile networks....that may be the reason
Sent from my LG-P500 using XDA App
It's checked alright. Like I said, I used it on the EDGE (2G) networks.
Anyway this doesn't matter anymore since I've switched to mik's rom.
you can give void# forever a try too...gives me two days battery life on moderate use...
Okay, I will.
Undervolting and profiles.
I have tried a crap ton of different undervolting setting, but none work
Also the profiles in set cpu don't seem to work for me. I have a few of them set and it always sits on the top one I need some guidence with both please!
Another thing my xda premium app isn't pushing my notafications yes its set
Sent from my MB860 using xda premium
Undervolting is a delicate process. It takes time to find the max undervolt that is stable. With that being said, try undervolting everything by the lowest amount which is -25mv. Check to see if that is stable. If so proceed to go further. Remember lower freq will typically undervolt farther than higher frequencies.
As far as profiles go your probably not using the priority values right. The higher priority is what determines which profile setcpu uses. So for instance if you want a safeguard against overheating, you could set the profile for when the cpu goes above 55C to throttle the processor way down. If you set this profile to 100(max) it will overide all other profiles at 98, 99, 75, 50...etc. Also this may be obvious to some but be sure to tick(enable) the profiles button. If thats not ticked then it doesnt matter how many profiles you have set up. It simply wont use them.
jack_slapped said:
Undervolting is a delicate process. It takes time to find the max undervolt that is stable. With that being said, try undervolting everything by the lowest amount which is -25mv. Check to see if that is stable. If so proceed to go further. Remember lower freq will typically undervolt farther than higher frequencies.
As far as profiles go your probably not using the priority values right. The higher priority is what determines which profile setcpu uses. So for instance if you want a safeguard against overheating, you could set the profile for when the cpu goes above 55C to throttle the processor way down. If you set this profile to 100(max) it will overide all other profiles at 98, 99, 75, 50...etc. Also this may be obvious to some but be sure to tick(enable) the profiles button. If thats not ticked then it doesnt matter how many profiles you have set up. It simply wont use them.
Click to expand...
Click to collapse
When I was on alien rom, I tried 25 on all and it restarted after like a minute. What worked for me was 25 25,50,50,75,75,100 fromm bottom to top. I tried it with cm7 and total no go lol
Lemme tryi 25 on all and see what I get and I didn't know that. They all werent working, so I set them all to 100 lmao, I understand that now
Sent from my MB860 using xda premium
Aparently its been running 125,125,50,75,75,75,75bottom to top cm7 with 1.3 kernel.
It did restart a couple min ago randomly. Will keep posted
Sent from my MB860 using xda premium
Glad your getting some results. If it restarts even once it means at least one of your undervolted freq isn't stable. With your settings I would wager its in the uper freq considering your undervolt in the lower freq isn't too extreme. You might try decreasing the undervolt for your upper freq to -50 -50 -50 starting at the top. Might help to stabilize bc higher freq just require more voltage. If that proves to be stable continue trying to reduce the lower freq as much as possible. Mainly bc if you set your profiles right(screen off is the most important really) your phone will spend the majority of its time on the 200mhz freq. Thus the more undervolt on that freq should theoretically give the most benefit from undervolting. This is just all from personal experience. I'm no guru. Just spent way too much time adjusting voltages on phones . And of course having the upper freq undervolted as much as possible cant hurt either.
jack_slapped said:
Glad your getting some results. If it restarts even once it means at least one of your undervolted freq isn't stable. With your settings I would wager its in the uper freq considering your undervolt in the lower freq isn't too extreme. You might try decreasing the undervolt for your upper freq to -50 -50 -50 starting at the top. Might help to stabilize bc higher freq just require more voltage. If that proves to be stable continue trying to reduce the lower freq as much as possible. Mainly bc if you set your profiles right(screen off is the most important really) your phone will spend the majority of its time on the 200mhz freq. Thus the more undervolt on that freq should theoretically give the most benefit from undervolting. This is just all from personal experience. I'm no guru. Just spent way too much time adjusting voltages on phones . And of course having the upper freq undervolted as much as possible cant hurt either.
Click to expand...
Click to collapse
25,50,50,50,50,75,75
Still getting a reboot:'(
Only good thing about the reboot is it turns on instantly
PROFILES CONFIRMED WORKING trying to indwrvolt this thing
I think I'm gonna order another battery too bc this one isn't getting the 16 hours it was, I cant say much bc I'm screwing with the settings hardcore xD I will show.all settings in a sec
Sent from my MB860 using xda premium
Sent from my MB860 using xda premium
Blahhh
Put blah there so it would post lol. Also going to download a stress test or quadrent thing to test the stress and find maximum uv
Sent from my MB860 using xda premium
Undervolting COMPLETE=D
QUAD SCORE! OCED 1.3 CM7
Right now I'm thinking my battery life is going to be amazig and if I turned the data off when not using it... omg I would last like 2 straight days prolly=D
So pumped to test everything morrow!!
Side note:800mhz or above wont go past 75 >:/
Had really important question to ask you but forgot
Also tried putting 215 to 275 that was a no go lol. My question was is there a battery manager and info like the stock one for cm7?!!!
Sent from my MB860 using xda premium
Smittyzz said:
Undervolting COMPLETE=D
QUAD SCORE! OCED 1.3 CM7
Right now I'm thinking my battery life is going to be amazig and if I turned the data off when not using it... omg I would last like 2 straight days prolly=D
So pumped to test everything morrow!!
Side note:800mhz or above wont go past 75 >:/
Had really important question to ask you but forgot
Also tried putting 215 to 275 that was a no go lol. My question was is there a battery manager and info like the stock one for cm7?!!!
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
well my battery was draining mad quick so I am not overclocking It anymore unless I want to show off or play games lol, lost 20% in one hour. Now its stable and undervolted
Sent from my MB860 using xda premium
First off, regarding SetCpu and over / undercloking, dev has said it'll only underclock/overclock ONE core at a time. It's a bug and he's working on it from what I understand. If both cores are needed to be in use at the same time, no over / underclocking will be applied. Secondly, profiles work as they should in SetCpu, so that's a problem on your end. Third, the undervolting can't be more than 100mv differnce between jumps. See screen shot.
http://www.multiupload.com/YUK0KPXZLJ
Phalanx7621 said:
First off, regarding SetCpu and over / undercloking, dev has said it'll only underclock/overclock ONE core at a time. It's a bug and he's working on it from what I understand. If both cores are needed to be in use at the same time, no over / underclocking will be applied. Secondly, profiles work as they should in SetCpu, so that's a problem on your end. Third, the undervolting can't be more than 100mv differnce between jumps. See screen shot.
http://www.multiupload.com/YUK0KPXZLJ
Click to expand...
Click to collapse
I understand the 100 thing and I got the undervolting and profiles done. I hope he gets both cores supported soon and thank you dmfor the reply
Sent from my MB860 using xda premium
Yea Im skeptical about not setcpu not having support for dual cores... Did some searching on the net and couldnt find anything to support that. As far as not the tegra 2 not being able to do over 100mv jumps. That's not true. My lowest frequency is 600mv (-150) and my next frequency is at 750mv. That's a 150mv difference right there... And I'm completely stable. Its entirely dependent on your processor. They are all different and respond differently to undervolting. You just have to find what works for you. Generally though the lesser the jumps in voltage will give you more stability.
a good kernal helps too im useing faux123 v2.0 0C1.3 its undervolts quite well
us/alienv4UL/OC1.3{webtop2sd{fixed}
Hey guys I know this was already asked but still i didn't found an answer . Is there anyway to incrase your CPU limit . Mine it's at 729 . If i set it to 747+ it will block and reboot . So is there a way to incrase it ?
I'm using Kernel roq XIII+ .
The cpu in this phone is what I believe to be an Arm v6 Adreno GPU. The max overclock we can get on the phone (whilst stable 100% of the time) is around 748mHz. I've seen people with 806mHz at certain times using Rom and kernal mixups, like once when I used PerfectPeso and Francos Kernal. Weird occasions...
I'd say max for speed and so on, go 100mHz or around that for lowest, and 728mHz for highest clocks.
Sent via Tapatalk for Android (T-Mobile HTC MyTouch 3G Slide running HTC Update #5)
CJJames said:
The cpu in this phone is what I believe to be an Arm v6 Adreno GPU. The max overclock we can get on the phone (whilst stable 100% of the time) is around 748mHz. I've seen people with 806mHz at certain times using Rom and kernal mixups, like once when I used PerfectPeso and Francos Kernal. Weird occasions...
I'd say max for speed and so on, go 100mHz or around that for lowest, and 728mHz for highest clocks.
Sent via Tapatalk for Android (T-Mobile HTC MyTouch 3G Slide running HTC Update #5)
Click to expand...
Click to collapse
Dont underclock below 448MHz. All frequencies below that have the same voltage so its pointless as power consumption will be same. If you clock too low, it'll take more time to come out of sleep. And don't overclock above 748Mhz. If you consistently clock above 748, there is a high chance for kernel panics. I know a guy who did so and now even 748 isn't very stable for him.
That is not totally correct. 122 MHz uses a lower voltage than 245-480.
Sent from my LG-P500 using XDA
NeuDLi said:
That is not totally correct. 122 MHz uses a lower voltage than 245-480.
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
However it's slow and there is a reason why LG chose not to you it by default
Sent from my LG-P500 using XDA
So no one know if it's posible to incrase that limit ..?
Cresqo said:
However it's slow and there is a reason why LG chose not to you it by default
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
You mean in the same manner LG chose to use crappy default kernels with defective touchscreen driver, or a crappy GB firmware, yes? Sorry but what LG does or not does is simply irrelevant.
And I did not tell anyone to use 122 MHz, but it is possible and at least with screen off can't hurt. If you don't like it don't use it! But don't act like you knew better.
Sent from my LG-P500 using XDA
I use 480-748 with no problems on my current rom (Lupo's CM9 test), if your phone is unstable or simply reboots then you may wanna try another rom/kernel
With popdog's Oxygen rom (version 2.5 at least) I also had no problems with the same range.
See what CPU we have it's one 600 very stable. if you are clocking it more it will heat up that's why it reboots and some time it freezes. I would suggest you you to use it at 600 or you can go little upper side. But if you really want to over clock it high then it has some issues. There are extreme heat. battery drain. reboots. hang. it can break you sound and VGA chip...so do it wisely. in 600 LG P500 is very good.
Every combination will be different. Some CPU will handle higher clock speeds than others. The manufacturer only lets it pass inspection if it exceeds their minimum specs. That means there will be some that can handle more.
You will find out with use.
Your kernel and governor will also make a difference. So will the rom depending on the tweaks used.
Do you really need to clock it faster than that? The faster you go, the hotter you go, which shortens the life of the chip. Heat is the enemy.
Sent from my LG-P500 using XDA