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.
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
So just inherited my dads OG Droid. Currently rooted and runs Steel Droid (Mod Version 9000) and 2.6.32.9_RZ Kernel.
Phone is overclocked to 1GHz (125/1000 ONDEMAND).
Like the title says, the phone gets about 5 hours and then hit's 5% and keeps asking me to charge. If I charge it overnight and unplug it when it's 100%, it'll hit 90% idling (while I sleep) about 3 hours later.
Running Programs:
DSPManager
Words Free
Facebook
3D Digital Weather Cloc
News & Weather
3G Watchdog
Videos
SoundHound
Pandora
Temp+CPU V2
Now out of all the running apps, Pandora, Soundhound, News & Weather, 3G Watchdog, Temp+CPU, 3D Digital Clock are all widgets. Temp+CPU and 3D Digital clock are the only ones that actually run, the rest are just there in case I want to use them.
These stats today are from using Pandora for about an hour over Wifi.
Any ideas? Phone runs fine most of the time but I have seen the occasional lag where you have to click something 10 times before it opens.
I used to have a pretty big problem with battery life too, but even though I think they are somewhat silly and annoying the Easy Battery Saver app helped me quite a bit.
Wifi and using the speakers are heavy on battery life. Not sure how much difference it will make but try consolidating your widgets and app shortcuts to as few screens as possible.
Also your CPU governor might be set to something that lets the phone hog through anything at the sacrifice of battery. When i set my CPU to Performance my phone runs like a boss, while setting it to battery saver I get a little more lag but more battery, obviously. Not sure how/if your ROM will let you change that but it's something to look into.
I got it set to On Demand which might be the issue. The kernel is a low voltage kernel. How do ultra low voltage kernels run?
I did a battery calibration, downloaded Advanced Task Killer (Battery saver didn't work well, I'd always have an issue with 3G not activating) and got rid of all my widgets. Currently charging it up completely, I'll check it out tomorrow.
So the title is incorrect, it says 5 hours and 5% left. I checked the battery info at 5%. It said 4hr 4x min. About 10 minutes later it shut off so I didn't even get 5 hours to a full charge.
I don't have high expectations but coming from an Alias 2 that had the extended battery (I'd get a week of battery with my use), this is pretty disappointing.
Well I can tell you now, ondemand is NOT good for battery, what that governor does is make it so the CPU will go from MIN to MAX speed slots depending on what the phone needs, AFAIK it doesn't scale with need, it just goes to max. So your phones CPU was running at max most the time which kills battery.
Can't say anything about your ROM, but I use simply stunning 5.6 http://www.droidforums.net/forum/chevyno1/177728-ss-5-6-2-3-7-incl-1-battery-other-goodies.html Which, with his low voltage 1ghz kernel set to the smartass governor, I get anywhere from 8-14 hours of battery life depending on use. Using ultra low voltage kernels depend on your phone, some phones have trouble overclocking to 800mhz mid-voltage (mid-voltage is considered to be the most stable, but use the most battery), others can overclock to 1.25ghz ultra-low voltage, which is very rare. I would say try out all the different voltage kernels and see which one works best with your phone.
Also task killer = MAJOR MAJOR No no! The task killer will kill the apps, and the android OS will restart them, using more CPU time and making the battery actually not last as long, I would recommend learning how to use the supercharger script http://forum.xda-developers.com/showthread.php?t=991276
Can't say much about the majority of programs you have running, but I've found facebook does not like to play nice with the Droid, also, why use the 3D clock when the Droid comes with a built in-clock app? Pandora uses a lot of battery, so running it w/ the ondemand governor is probably what hurt your battery there.
Not many Droid users left out there, but I was and still am an extremely avid Droid user, so if you have any more questions just shoot me a PM and I'll help as much as I can.
Thanks! I got rid of all my widgets and installed Chevy's ultra low voltage 1.1GHz kernel on smartass. I lost 20% battery pretty fast but let's see how long it runs. I've had no force close issues so far. I'm a bit tempted to go to 1.2GHz ulv.
How much does the ROM have to do with battery life? I really love this ROM and it's interface. I thought the battery life really only had to do with kernels.
I also got rid of the clock widget and put a default clock widget. What's the built in Android one? Is that the "Analog Clock"?
Sorry for all these questions, I'm pretty new to Android. Only had this for 2 days (~8-10 recharges...)
Its fine, better to question and learn then to just get mad and over it, and Roms have everything to do with battery, they are just like kernels, some work AMAZING on some phones, while others can destroy battery life.
Like my rom, I found the perfect one for my phone, I get 8- (been thinking about it more) 20 hours of battery life on mine and it has pretty amazing performance too with the occasional hiccup.
And I thought you had the clock app installed for an alarm, not for a widget, my bad. I don't use a clock widget so I wouldn't know.. Also, I've found its not very good to run many widgets on the Droid, as it has limited memory and can only handle so much.
Well I got sick of it and reflashed the entire ROM. CPU governer is set to ONDEMAND 125/1000. Only*widgets I have are a simple clock (like the iPhone lock screen) and power control. Gonna see how it goes. So far so good but I'm saying that because I didn't loose 20% overnight. If I can clear the day, I'm good.
googlelover, what CPU Governer did you find to work the best with your phone?
I have been an Android owner for a while now, with the Droid being my first. Until recently battery life had always been an issue for me. Undervolting has never had an effect over a 20% improvement. And this is only when it's in deep sleep. Otherwise, in very general terms, undervolting can require a higher current aka worse battery life if you use your phone a lot. With undervolting comes the risk of data corruption in your phones memory and SD Card. What really kills your phone is screen on time, wakelocks, CPU overclock, and signal quality.
The last you have no control of. But if you're overclocking 1GHz or higher you have to realize that's almost twice the manufactured clock speed. As far as wakelocks, this is when something keeps your phone from going into a low power state. This can happen because of a rogue app, a buggy ROM, or having too many widgets. I ran into a ROM a while ago on my Fascinate that would stay awake if you had GPS enabled. The best you can do with your display power usage is to keep your brightness down. Hope this explains a few things
have the same issue
core2kid said:
Well I got sick of it and reflashed the entire ROM. CPU governer is set to ONDEMAND 125/1000. Only*widgets I have are a simple clock (like the iPhone lock screen) and power control. Gonna see how it goes. So far so good but I'm saying that because I didn't loose 20% overnight. If I can clear the day, I'm good.
googlelover, what CPU Governer did you find to work the best with your phone?
Click to expand...
Click to collapse
I already told you, the smartass governor, and like I said before, ondemand is not a good governor in my opinion. There are way to many factors in battery life to have anyone else be able to truly help you with it, all our phones are different and it really just takes time switching kernels, switching ROMs, etc to find what works with your phone
Sorry googlelover, I forgot you already said that.
So update guys. I've been going a day (so like 18 hours) of use after which it finally hits the 15% warning.
What I did:
Basically I reflashed the ROM and started from scratch. Before reflashing, I wiped the user data/cache/davick cache etc at least twice just to make sure it was really wiped.
I reflashed SteelDroid 9.0 with the default chevyno1 lv 1ghz kernel and gave it a go with just a simple clock widget. Worked well. One by one, I'm starting to install applications until I can figure out what was draining the battery fast. So far, so good. If I can get 18 hours on a 2 year old battery, I'm going to be doing fine with my extended battery.
One thing I did notice was that the phone back by the camera (where CPU is) isn't getting as hot as it used to. Makes me think that the phone was at a high clock speed in sleep. Another issue may have been my CPU temp/speed monitor. It was probably poling the CPU stats every second which made the phone increase the CPU speed because it sensed activity.
Try out the ROM I'm using. I absolutely love it. The interface is phenomenal and it runs very well.
htp://w w w . d r o i d f o r u m s . n e t /forum/steel-droid/148060-release-steel-droid-9-0-gingerbread-11-17-2011-a.html
(remove the spaces to see it, I wasn't able to post links normally because I don't have enough overall posts).
There's probably other ROMS that run better like the one googlelover is using, but I can't use the default Android interface anymore after using this.
core2kid said:
Sorry googlelover, I forgot you already said that.
So update guys. I've been going a day (so like 18 hours) of use after which it finally hits the 15% warning.
What I did:
Basically I reflashed the ROM and started from scratch. Before reflashing, I wiped the user data/cache/davick cache etc at least twice just to make sure it was really wiped.
I reflashed SteelDroid 9.0 with the default chevyno1 lv 1ghz kernel and gave it a go with just a simple clock widget. Worked well. One by one, I'm starting to install applications until I can figure out what was draining the battery fast. So far, so good. If I can get 18 hours on a 2 year old battery, I'm going to be doing fine with my extended battery.
One thing I did notice was that the phone back by the camera (where CPU is) isn't getting as hot as it used to. Makes me think that the phone was at a high clock speed in sleep. Another issue may have been my CPU temp/speed monitor. It was probably poling the CPU stats every second which made the phone increase the CPU speed because it sensed activity.
Try out the ROM I'm using. I absolutely love it. The interface is phenomenal and it runs very well.
htp://w w w . d r o i d f o r u m s . n e t /forum/steel-droid/148060-release-steel-droid-9-0-gingerbread-11-17-2011-a.html
(remove the spaces to see it, I wasn't able to post links normally because I don't have enough overall posts).
There's probably other ROMS that run better like the one googlelover is using, but I can't use the default Android interface anymore after using this.
Click to expand...
Click to collapse
Don't forget not many roms have the default android interface, many have themes to completely change the look, if your happy where your phone is, great! But if you ever feel like your phone is slowing down again, I'd still recommend looking around and flashing some different roms.
Thanks, I'll keep that in mind. I'm only using this phone for another couple months. I'll be getting the Droid 4 when it comes out. Looks like a really nice phone.
Ever since I flashed the 213 leak, battery life has been a bit disappointing. To help things along, I downloaded SetCPU (haven't used it since my good ole OG Droid) and let it autodetect settings. To my surprise the governor was set to 'interactive' instead of hotplug like it was on stock GB.
My understanding is that hotplug allows the phone to disable unneeded cores during periods of low utilization, while interactive does not (although both cores can be disabled when the phone is sleeping). Do you think switching to hotplug from interactive will improve battery life?
My battery life is much better since switching, but I also disabled 4G (on WiFi most of the time) and added screen off and low battery profiles (600mhz and 800mhz max respectively) which muddy the waters a bit. I thought I would mention it on here for those of you who feel the same, it might be an easy way to improve battery life on the leak.
That's interesting. I've been using the .213 leak and my battery life has been quite good. I haven't noticed any particular drop in battery life, and I keep 4G on all the time. If I don't use my phone much, it's not uncommon for me to have 60% left at the end of the day.
Do you use anything like SetCPU? I am wondering whether I can confirm that the default governor of the leak does not shut off one of the CPUs when it is idle. If nobody can confirm I'll get around to checking it myself this weekend :laugh:
Sorry, I haven't messed with my cpu settings.
Hey, was just wondering what settings you all have under Kernel Auditor in order to ensure 5 hours+ SOT. I personally have a dual core setup and have the other two cores kick in when the load gets to 90%, but this seems sort of sluggish now and I only get about 3.5-4 hours SOT and I don't play any games; just simple browsing and productivity. Others manage to get up to 5-6 hours SOT and I wonder how, I have NEVER been able to get this much. Standby is great though, 10 hours overnight and I lose only 3% battery. I am running on Pure Nexus Project ROM and latest Hells Core Kernel.
thats about the regular time I get outa mine. If I had to guess a lot of these 5+ hours are from watching videos or something that doesn't involve touching the screen. I've been using HC kernel with just zen decision on max performance settings and gpu on performance governor (since it idles 27mhz anyway might as well ramp up to full 600mhz for touches) for smoothness.
I have it setup that all my cores are on all the time, no hotplugging. ondemand/deadline, mpdecision disabled, fsync disabled. and I get 5+ hours sot every single day. no, I do not watch videos. but I do keep my brightness all the way down.
Hey, where do you go to disable fsync
aroy97 said:
Hey, where do you go to disable fsync
Click to expand...
Click to collapse
it has to be an option in the kernel that youre using, at least the kernel has to expose it so that you can disable it. if its not xposed in general, then you cant disable it. im using despair kernel.
Try undervolting. Unless you severely under clock your cores you won't really see battery life improvement.
I keep my max CPU speed at 2803mhz. You might think "oh well if you're running higher frequencies then more battery drain". Not exactly. The difference between 2649mhz and 2803mhz will be negligible in terms of battery life so I'm seeing a slight performance increase with no significant battery loss. For example, on 2649mhz after a full day of normal usage I'd have about 49% battery life. On 2803mhz I'd have about 43%. I got a good performance increase and a more snappier device in terms of loading web pages, apps, opening documents etc so that extra 6% I lost doesn't matter to me, because its not significantly impacting me, I barely notice most of the time.
So yeah, the same goes for lowering CPU speeds to unless you significantly lower them. Putting max CPU speed to something like 2572mhz, you wouldn't even notice e the difference in battery. Now lowering it to like 1958mhz, or 2188mhz and you'll see a difference because at that point your severely under clocking.
You could also be draining your battery by hotplugging. That's why some people like Zen and MP Decision to keep all cores online when screen is on. If you use your device often, its better to have all cores running. If you don't and its kept in your pocket for hours at a time, hotplugging is the way to go.
Try under volting too. I do. Global Under Volt of -60.
TransportedMan said:
Try undervolting. Unless you severely under clock your cores you won't really see battery life improvement.
I keep my max CPU speed at 2803mhz. You might think "oh well if you're running higher frequencies then more battery drain". Not exactly. The difference between 2649mhz and 2803mhz will be negligible in terms of battery life so I'm seeing a slight performance increase with no significant battery loss. For example, on 2649mhz after a full day of normal usage I'd have about 49% battery life. On 2803mhz I'd have about 43%. I got a good performance increase and a more snappier device in terms of loading web pages, apps, opening documents etc so that extra 6% I lost doesn't matter to me, because its not significantly impacting me, I barely notice most of the time.
So yeah, the same goes for lowering CPU speeds to unless you significantly lower them. Putting max CPU speed to something like 2572mhz, you wouldn't even notice e the difference in battery. Now lowering it to like 1958mhz, or 2188mhz and you'll see a difference because at that point your severely under clocking.
You could also be draining your battery by hotplugging. That's why some people like Zen and MP Decision to keep all cores online when screen is on. If you use your device often, its better to have all cores running. If you don't and its kept in your pocket for hours at a time, hotplugging is the way to go.
Try under volting too. I do. Global Under Volt of -60.
Click to expand...
Click to collapse
undervolting doesnt really save you battery, but it does reduce heat. and hotplugging or having all your cores on doesnt really factor in when you dont use your device that much. as, if you have all your cores on or hotplugging, your phone should be in deep sleep anyways. it does make a difference when your phone is awake. i get much better battery life when all my cores are on all the time.
Should there be a sticky of suggested settings of differing requirements of speed, battery life, etc?
ronaldheld said:
Should there be a sticky of suggested settings of differing requirements of speed, battery life, etc?
Click to expand...
Click to collapse
honestly, I don't think so. as the settings/setup used is always dependent on how you actually use the device. and many people have different opinions on how it should be set up.