Related
Hey everyone, there is an overclocking app in the market, anyone care to give it a try?
Edit: So I downloaded it lol. Here are some screenshots. BTW, is there anyway I can verify that the cpu freq is actually being adjusted?
*Just for fun I ran neocore to see if it would raise my FPS. lol.
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
For example, atrackdog would take me at least 20-30 seconds to load my full app list (184 apps)
After installing overclock, it loaded in under 5 seconds.
i'll run other programs, and post my results.
I ran droidgear (game gear emulator) before and after, and I can honestly say it was faster (not a placebo affect).
-Before: droidgear would take over 4 minutes just to get to the menu screen
-After: i was actually able to load a game in under 1 and a half minutes, I even let it sit to run the demo, and it is the fastest ive ever seen an emulator run on this device (compared to NesEmu, and GB emu)
It would probably actually be playable if tweaks were made to the application codebase, and android Open GL stack.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
well, i was too, and then i downloaded it and said "aahh, what the hell, if i break mine, ill just take my wifes haha..." probably not the best of plans but i installed it anyway
sooo i havnt burnt up my phone yet, but here is my issue with the app, does the app only work untill you reboot your phone?
because when i reboot my phone, it goes back to the default speed according to the app
also, my phone tends to hang up (stuck on the apps screen, no buttons work, screen wont rotate, power button wont shut screen off) when using the 528MHz
so far, i havnt found a reason to pay a dollar for it, but ill keep testing
[UPDATE]
resolution for all below tests is 320 x 480
i tried neocore like posted above, using the mid level setting, and i actually did raise my fps from
DEFAULT CPU (248 MHz): 20.5 (with sound off)
384 MHz: 25.0! (with sound off)
DEFAULT CPU (248 MHz): 14.5 (with sound on)
384 MHz: 20.8 (with sound on)
still havnt gotten the fast speed to work yet, but im still trying to figure that out, on another note, sweeter home does seem to load a little faster
[UPDATE]
Incase you didnt see my sig, im not running on a ADP1 phone, so that might by why the fastest setting doesnt work for me, but so far 384MHz is making a noticeable difference with NEOCORE and SWEETER HOME
andonnguyen said:
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
Click to expand...
Click to collapse
i use snap photo, which used to take FOREVER to load up on my g1 using the camera button, its significantly faster using the 384MHz setting, good observation
Ok, so so far here is a list of things ive noticed (using 384MHz vs 248MHz):
-FPS in NEOCORE increased on adverage 5 to 6 fps
-Sweeter Home doesnt lag NEARLY as much as it used to (ALOT less force closes)
-Snap Photo doesnt take a month to load using the camera button
-G1 Wakes up properly which was a issue my g1 (and others on this forum) had
-Even though the app says it will "kill" the battery, using 384MHz during normal use of the phone isnt "killing" my battery, however, doom (while runs better (even with sound on)) seems to be dropping my battery level faster, but the game is running faster, which is the trade off id expect when running these apps together
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
speoples20 said:
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
Click to expand...
Click to collapse
all of our battery life sucks unless you have the extended battery, im not getting THAT big of a battery drain according to the system monitor app, and it DOES make a difference on g1's that have lag issues (running tons of apps like i do)
in other threads, people have complained about the g1 not waking up quickly sometimes, ive yet to have that issue since ive clocked mine up to the 384MHz setting
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
The program installs a script on your sd card called ocx_tmp.sh and adjusts it that way, it'll write to /system as -rw (from what I've discussed with someone) would probably cause instability.
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Try it before and after setting the cpu freq in overclock and you'll see what I mean =)
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
andonnguyen said:
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
Click to expand...
Click to collapse
im not as familiar with clocking/overclocking so i wasnt sure if i was clocking it to 384, overclocking it to 384, or what, so what would be the proper thing to put in my sig? lol because according to my first quote, true overclocking wouldnt be untill i went beyond 528, so from the view of my first quote, im not OVERclocking, im clocking, wheras your saying im overclocked
andonnguyen said:
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Click to expand...
Click to collapse
so is it infact the program thats changing the cpu freq or is it the phone? if its the program, is this to avoid overworking the cpu without the demand?
andonnguyen said:
.
The program will reset the cpu freq back down to 384mHz after the phone sleeps.
Click to expand...
Click to collapse
by sleep do you mean turning the screen off using the power button? because i saw no change in my cpu freq when doing so using your commands
ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
dont know, but i found this over at the android community:
Technical Features
Supports WCDMA/HSUPA and EGPRS networks
Multimedia Broadcasting Multicast Service (MBMS)
Integrated ARM11™ applications processor and ARM9™ modem
QDSP4000™ and QDSP5000™ high-performance digital signal processors (DSP)
528 MHz ARM11 Jazelle™ Java® hardware acceleration
Support for BREW® and Java applications
Qcamera™: Up to 6.0 megapixel digital images
Qtv™: Playback up to 30 fps VGA
Qcamcorder™: Record up to 24 fps QVGA
Up to 4 million triangles per second, and 133 million depth-tested, textured 3D pixels per second fill rate
gpsOne® position-location assisted-GPS (A-GPS) solution
Support for third-party operating systems
Digital audio support for MP3, aacPlus™ and Enhanced aacPlus
Integrated Mobile Digital Display Interface (MDDI), Bluetooth® 1.2 baseband processor and Wi-Fi® support
maybe that info will help? if not sorry
I remember reading somewhere by someone that it runs at 384 by default, and I think the post above confirms that...
ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
gui fluidity is definitely increased, and sluggishness between app switches and when the translucent app drawer opens up is gone. i like it, but to the average person there probably is no need to do it.
keep in mind this is also not overclocking the cpu, it's clocking it to its default spec. as it is an embedded arm, it is designed to run hot, so i guarantee you are in no danger of hurting your phone.
also, do not listen to people that claim there could be no gain from overclocking, just because the bus speed is slower than the cpu speed does NOT mean there will be no improvement in system performance. if that were the case, there'd be no use for 4ghz desktop processors.
cache still runs full speed, and common execution paths stay in cache meaning no prefetch from system memory, meaning BIG improvement in many cases. (that's why cache exists.)
damnoregonian said:
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
gui fluidity and responsiveness is greatly improved. sluggishness if app switching and the translucent app drawer are completely gone.
for many i imagine this means there isn't really any reason to clock the cpu up to its stock speed, but to each their own.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
Click to expand...
Click to collapse
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Holy crap. Used this @528MHz with Haykuro's version 4.5 apps to sd ROM and the osk works SO MUCH BETTER!!!! Also I got 25.6 fps on neocore... very smooth
wootroot said:
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Click to expand...
Click to collapse
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
A modded version of JF's ROM would ROM.
I DO notice the sluggishness and it bugs the heck out of me. (I switched from a WING with a 200MHz CPU, and although it IS faster than the wing, it doesn't seem significantly faster and seems to much slower when I open up the camera...
damnoregonian said:
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
Click to expand...
Click to collapse
that involved eh?
thanks for this post though, now i understand more about the idle loop and why the cpu freq resets with each reboot
maybe someone can take this stuff further like he said, that kind of stuff would be worth the dollar, imo more than a dollar
well... i don't mind providing basic procedure and source, i just don't want to get dragged into level 1 support of the procedure.
i'll go ahead and package up some source, prebuilt boot images based on JF's RC33 (which is what i run) and a basic procedure.
Subject says it all, 200MHZ sometimes doesn't cut in, if we need the speed, what is the best app out there ?
Thanks in advance
Found the solution...
Thanks for looking at the thread ... It was shinny isn't it.
Don't waste your time, PPC CPU can't be overclocked
No?!?! look this!
xhtc said:
Don't waste your time, PPC CPU can't be overclocked
Click to expand...
Click to collapse
You really need to do some research my friend.
Alright, let me save your time. Just search for Omapclockkeep, you'll clear your old taboo.
Just for the information, i have happily cruised my VIVA's CPU at 250MHZ, battery life is ok, not much affected.
Battery lasts 2 days with occasional WIFI plus Bluetooth.
3 apps
I've seen 3 apps so far that promisses the posibility to OC ppc...
Omapclockkeep
(posted in this thread)
Speed Booster
_www .teksoftco. com/index.php?section=speedbooster_
Pocket Hack Master
_www .wizcode. com/products/view/pocket_hack_master_
and pocket hack master even says it can prolong battery life (they also have another app called Pocket Battery Analyzer that seems good)
Anyone tried the apps? do they really work?
su8044 said:
I've seen 3 apps so far that promisses the posibility to OC ppc...
Omapclockkeep
(posted in this thread)
Speed Booster
_www .teksoftco. com/index.php?section=speedbooster_
Pocket Hack Master
_www .wizcode. com/products/view/pocket_hack_master_
and pocket hack master even says it can prolong battery life (they also have another app called Pocket Battery Analyzer that seems good)
Anyone tried the apps? do they really work?
Click to expand...
Click to collapse
I am using Omap keep cause you can keep the default speed at ideal and as soon as you start using it, you can set the speed like 250 and gain the extra performance through overclocking...
I'm using Homescreen++, which has a great overclock utility called CPU Scaler. It dynamically overclocks the CPU when the phone actually requires it, therefore saving lots of battery life. It also reduces the speed when it's idle to save even more. You just give it a min, max and boost value(when apps are really demanding) and it does the rest. It also monitors power consumption(maH, mW) and CPU temp. Good stuff.
zuperxtreme said:
I'm using Homescreen++, which has a great overclock utility called CPU Scaler. It dynamically overclocks the CPU when the phone actually requires it, therefore saving lots of battery life. It also reduces the speed when it's idle to save even more. You just give it a min, max and boost value(when apps are really demanding) and it does the rest. It also monitors power consumption(maH, mW) and CPU temp. Good stuff.
Click to expand...
Click to collapse
I have used it and my personal experience of using PPC for last 5 years says anything that monitors eat battery...
haha, yeah obviously, but every bit counts, no?
Hello, anyone know how to configure setcpu to save the battery while maintaining a smooth flow of the phone?
I saw that we could create "rules": those who did, can you post your configuration.
Thank you
Yes, i've good settings!
Profile: Auto-detect
Max 998400
Min 245000
CPU Governor On demand
Set on boot checked
Profiles on
Sleep/standby enabled
Max 245
Min 245
Battery profiles
Power <30%
768 Max
245 Min
These are same settings as teknologist have. This is the man who did the kernel for MCR ROMs. In my eyes he is a god in this things. So I belive him full!
see this and I think should be added here. http://www.pokedev.com/setcpu/
Formel-LMS said:
Yes, i've good settings!
Profile: Auto-detect
Max 998400
Min 245000
CPU Governor On demand
Set on boot checked
Profiles on
Sleep/standby enabled
Max 245
Min 245
Battery profiles
Power <30%
768 Max
245 Min
These are same settings as teknologist have. This is the man who did the kernel for MCR ROMs. In my eyes he is a god in this things. So I belive him full!
Click to expand...
Click to collapse
With this configuration, you save the battery?
If yu wanna have the longest battery time, just use all 245/245 Mhz.
But this makes no sense.
I think you wanna have it between battery/speed, isn't it?
Formel-LMS said:
If yu wanna have the longest battery time, just use all 245/245 Mhz.
But this makes no sense.
I think you wanna have it between battery/speed, isn't it?
Click to expand...
Click to collapse
obviously! I want my battery will hold at least two days! I will try your setup throughout the weekend and I'll make a return Monday.
thx
tcastel said:
obviously! I want my battery will hold at least two days! I will try your setup throughout the weekend and I'll make a return Monday.
thx
Click to expand...
Click to collapse
Don't hold your breath. Im being serious here. It wont last unless it sits in standby most of the time and then you're still pushing it.
Spend the 25$ extra and get a second battery.
2 DAYS?! Let me know if you are able to accomplish that somehow! I've tried everything; ROMS, Kernels, Juice Defender, SetCPU, anything you can think of and about the best I can get is 15-16 hours with moderate to heavy usage. I think I am actually going to buy a spare battery today.
.. that's not hard to do, 2days... even more.
Just stop all apps to update, stop auto sync, stop background sync...
you will be surprised*
I knocked down my cpu to 500 or so in all conditions, phone still feels responsive.
If you want two days, turn off 3g, turn off sync, turn off brightness. You'll not only get great battery life but a $600 dumbphone to boot!
this is what you need to do...
sleep/standby 245min 245 max cpu governer: powersave
charging 245min 883 max cpu governer: on demand
'normal': 460min 998max cpu governer: conservative
if u find that with normal use the phone isnt as snappy as it used to be, and this bothers u, then change the cpu governer back to on demand for the normal profile.
i've had amazing battery life since i tried these settings.
Also....some apps prevent the phone from sleeping so keep an eye out if ur battery is just literally disappearing!
Setting the max too low on any profile is not a good idea. This can cause tasks to take too long to complete and queues and memory to fill. This can make your phone unstable and arguably increase battery usage due to increased management overheads.
Some overhead above minimum is always preferable. I would consider anything less than 245/576 quite extreme and normally undesirable.
djmcnz said:
Setting the max too low on any profile is not a good idea. This can cause tasks to take too long to complete and queues and memory to fill. This can make your phone unstable and arguably increase battery usage due to increased management overheads.
Some overhead above minimum is always preferable. I would consider anything less than 245/576 quite extreme and normally undesirable.
Click to expand...
Click to collapse
yeah i heard about this but i have never encountered any problems. obviously its different for everyone but i would say try 245/245...if your getting too much drain with the phone on standby then use 245/576 with on demand governor.
Formel-LMS said:
Yes, i've good settings!
Profile: Auto-detect
Max 998400
Min 245000
CPU Governor On demand
Set on boot checked
Profiles on
Sleep/standby enabled
Max 245
Min 245
Battery profiles
Power <30%
768 Max
245 Min
These are same settings as teknologist have. This is the man who did the kernel for MCR ROMs. In my eyes he is a god in this things. So I belive him full!
Click to expand...
Click to collapse
I do not see much difference!!
tcastel said:
I do not see much difference!!
Click to expand...
Click to collapse
To be honest everyone "thinks" you can see a night and say difference just by tweaking the clock's and installing more efficient kernels. You can't and wont.
Those things may save you 5-10% over the course of a day but don't expect miracles. If you look at your battery history information you'll see that the system and any CPU related item can become relatively low doing all the efficiency modifications yet the battery still poops too soon.
Now look at the display. Thats where it's all going and as far as I know there is nothing anyone can do about that on our side. I run with the display back lighting 100% OFF and it still shows at a HUGE portion of my energy use. ~50% and sometimes more.
The day we get more efficient screen technology is the day we will be able to possibly use these things for 2 days on one charge... Either that or more powerful battery technology.
You know guys, I only have 3 scales on the application. Userspace, ondemand, and performance. I also have no idea what Priority means and how high or low to put them for a good profile! What do I do?
ma1993 said:
You know guys, I only have 3 scales on the application. Userspace, ondemand, and performance. I also have no idea what Priority means and how high or low to put them for a good profile! What do I do?
Click to expand...
Click to collapse
Set a default scaling type that suits you, typically On Demand or Uberspace and then set up your profiles. All of your profiles can use the same scaling (mine do).
The set your profile priorities in the order you want them to apply, 100 is the highest priority. For example, you might want the phone to run with less overclock when the battery is low and you want this condition to apply all of the time then you would give it a higher priority than other rules so it always executes. A better example might be a temperature profile. If the phone is hot you want to clock it down and want this to NEVER be overridden by another profile then you would set this to very high (say 99) so it could NOT be substituted by another rule.
OK...so MUCH THANKS to Mr. Carlisle for gettin me all squared away with rooting my Hero and upgrading to Froyo 2.2. All back ups complete, apps downloaded and only major bug thus far is the camera...SO....why is my battery running at 105 degrees on average? What should the normal range be? I turn it on @ 6 am after charging to 100% and wiping battery stats and ten hours later recharge it to 100% (Currently @ 50%) and all day the temp has been between 103 and 105. whycome? HELP!
Pauper7 said:
OK...so MUCH THANKS to Mr. Carlisle for gettin me all squared away with rooting my Hero and upgrading to Froyo 2.2. All back ups complete, apps downloaded and only major bug thus far is the camera...SO....why is my battery running at 105 degrees on average? What should the normal range be? I turn it on @ 6 am after charging to 100% and wiping battery stats and ten hours later recharge it to 100% (Currently @ 50%) and all day the temp has been between 103 and 105. whycome? HELP!
Click to expand...
Click to collapse
Because on FRF91 on Cyanogen mod (which i assume you are using) is overclocked to 710 mhz, where the hero's processor runs at 528 normally. My suggestion is to download an app called overclock widget from the market, (Obviously, it's a widget and you'll have to add it to your homescreen) and set the minimum and maximum clock (processor) speed to 240mhz(min) and 518mhz [or 534, if you want to, but it won't make much difference] (max).
You can set the max (or minimum) clock speed to be more or less. Lower clock(processor) speed=More lag but better battery life, and potential to freeze your hero because the processor can't operate the system fast enough. Higher clock(processor) speed= Faster and less lag but less battery life and can damage your touch screen (It's happened to me). if you leave it at too high a clock speed for too long, and can also freeze your phone because your processor can't operate at that speed and crashes your phone.
It's up to you if you want to overclock or not, but you should keep it resonable, and if you have heavy phone usage, don't go much further than 613 mhz for your max. There is also another program called set cpu that is avalible for free for xda members, but is a paid app on the market. Using that, you can set your frequencies to the default hero processor, or of other phones. But overclocking over 710mhz could do some harm to your phone, so be careful.
If you say, "I wonder if this will damage my phone," then don't take the chance without asking around first.
If you have any more questions about overclock, pm me, and I can help you out.
That temperature range, ~40C is completely normal when charging and using at the same time (with me, anyway). I'm OC'ed to 710 and using undervolt, too. The highest I've ever seen mine go is 43C, or about 109F. I don't really know where the "danger zone" is, but if I had to guess it would be around 48C or higher.
Edit: I reread your post, and do you mean it's at 40C always, even when it's sitting doing nothing? If that's the case then follow Ryoma Echizen's advice and fine-tune your CPU speed.
748/245
Temp < 50C 245/245 100
Screen Off 245/245 90
Charging/Full 719/245 80
Battery <40% 604/245 70
All ondemand
Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery <100% 768/245
that's listed by priority
Hungry Man said:
Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery
Click to expand...
Click to collapse
Screen Off: 245-480
**Stock is 245-245. 160 as a minimum seems to produce a LOT of wait time from when the call is coming in to when the phone lights up. More than 245 seems to whack the battery.
Keep in mind, when you wake up your phone, this Screen Off SetCPU Profile is active for at least a SECOND or two. The problem is that if you have your maximum at 245, you experience BAD lag trying to pull the lock bar down. At 245-480, the maximum is high enough that a) the lock bar pulls down as smoothly as a stock Eris, and b) even if SetCPU takes a couple of seconds to change the profile, at least you're at 480mhz for the first scrolling of the screen left/right (so you don't embarass yourself in front of iphone users). Anything higher than 480mhz is a different voltage. Almost the whole time your phone is 'Screen Off', it will be operating at 245 anyway. So 480 is a good setup for it to jump up when a call comes in (to play the ringtone and show the picture a little faster, and for the lock screen bar to pull down smoothly, and the first second of SenseUI to be smooth enough, until your phone changes the profile to your <100% profile.
Battery <100% 245-806
** Zanfur's take on how this processor clocks up/down its speeds will lend itself to a general wisdom that 768mhz isn't really slower than 806mhz, and that in instances of high variability of clock speed (aka you have some Power Save bias in SetCPU keeping it lower/higher at random, or you're doing very intermittent tasks), the processor rests at 768mhz more quickly, and wastes less time/'effort' changing speeds. Changing to 806 is another 'step' altogether, where 245 to 528 is one 'step', and that to 768 is another 'step'. Going to 806 is absolutely another step yet after that (which means your phone responds a LITTLE slower because it has one more step to 'throttle' up to). BUT, if you're doing a dedicated task, such as running a Linpack benchmark (which is a terrible benchmark anyway) your phone will move faster at 806, or if you're playing a game, or playing a video... generally the processor will stick at one speed (and not have to 'step' up or down), so 806 is faster. I clock friends' phones at 768 to avoid problems, keep it clean, etc etc. Some people put the minimum here at 160mhz, but I feel that this is too low (and another 'step', just like 806 is over 768, 160 is another step down from 245).
Charing (any) 480-806
** I keep the minimum here HIGHER than when the phone is on battery, because I'm less concerned about how much energy it's consuming, and having a minimum of 480 makes the phone very snappy no matter what, from the second you touch it
Overheating > 48C 122-528
** Clock speed here matters a LOT less than just getting your phone out of the heat. This phone doesn't overheat because it's overclocked, it overheats because you run it at an overclocked speed for a long time. MOST overheating instances are from wireless tethering and from broken charging systems (that keep trying to charge the battery and generate a lot of heat). The 'Failsafe' profile here provides a 'notification' option which I HIGHLY recommend.
My ex-gf's Eris actually CAUGHT FIRE, as in it looked like it was a zippo, right above the volume buttons. It used to overheat EVERY NIGHT that it was on the charger, excessively, so hot that you couldn't touch it. For a month or two it did this, actually, and caused no real damage to the phone. Since the night of the Flame (you can actually see the melted plastic and even on the outer case - she has a blue snap shell case on it that is melted as well), the phone has NOT overheated even one time on the charger. (Sorry for the story, it was a waste of time).
The point is that, the first time it happened, her phone System sound was on Silent, and she DIDN'T hear the notification that her phone was overheating. Apparently it doesn't matter (or she's very lucky her phone isn't damaged in terms of its operation!) how much it overheats for some people, but I like to have it warn me it's getting close to 50C. The notification's the important part there (so u can cool your eris), not the clock speed.
@pkopalek I like your settings you posted with a full description of each. I changed my settings to yours and give it a day or so and will report a status update as to performance quality
I've never lagged at 160mhz =p but that could just be my phones/ roms.
Hungry Man said:
I've never lagged at 160mhz =p but that could just be my phones/ roms.
Click to expand...
Click to collapse
my audio skips and it won't wake up when in a call at 160mhz. I keep mine at 245mhz minimum to keep phone working smoothly.
What does the different prioritys mean? Is that like what one its.focused on more?
Sent from my FroShedYo.V5 using XDA App
How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo
sgbenton said:
How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo
Click to expand...
Click to collapse
When a processor is made at the factory, it will always have flaws in it. The chip is tested to see what frequency it is stable at. So that is the speed that is stamped on the chip and the frequency that it is set at to operate for the consumer and not have any problems. When you overclock a processor, you are bypassing the frequency that the chip as been deemed to be stable at. After that, there is no set speed that your processor can handle, because each one is different according to the flaws it might have.
So in short (what I'm trying to say), the processor in your phone just can't handle those without causing problems. That's why when you overclock it, it's kind of a trial-and-error process to see what speed you can get out of it, but be careful, because too high can cause permanent damage.
Using Interactive governor
Main: 787/710
Temp > 42.1 C: 480/245 Priority: 100
Screen Off: 480/245 Priority: 95
Charging/Full: 480/245 Priority: 90