Database Develop

DX/D2 Overclocker

Sorry for not posting this sooner everyone. But if you want to check out the first DX/D2 Overclocker to hit the market here are a few screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One of the key features this one carries is you can have as many presets as you want and as an integrated stress test feature to see if your settings are happy or not. There are also some new safety features coming today and something big I can't speak about tomorrow or Wednesday.
If you have any comments or ideas, let me know. I always want to improve things!
Thanks.

I can vouch for this product. Very nice layout and the settings work as advertised. I can't wait to see what you have up your sleeve!

Nice app! I like the presets. Gives you a good place to start from.

Nice app OP!

working for me so far, nice work. i was hoping i wouldnt have to go through the files like in the tutorials...
quadrant was like 1375 or so, now i hit 1485. not bad i think!

How can I test the overclock? I see always this bar graph on the forum but don't know what it is.
I have a blur X and was wondering if I could make it quicker without loading a custom ROM
Thanks
Ohh in the market in the app description make it in bold that it is only for the DX and D2 I think people are using it on other phones and that is why you are getting negative reviews. I'm thinking on getting it this week

Venc said:
How can I test the overclock? I see always this bar graph on the forum but don't know what it is.
I have a blur X and was wondering if I could make it quicker without loading a custom ROM
Thanks
Ohh in the market in the app description make it in bold that it is only for the DX and D2 I think people are using it on other phones and that is why you are getting negative reviews. I'm thinking on getting it this week
Click to expand...
Click to collapse
That bar graph you are most often seeing is people running the benchmark "Qaudrant". Go download it from the Market, it is free.

Real time CPU scaling and current speed are in 1.3.2 that just hit the Market. Enjoy.

I was wondering how the stress test works, everytime I use an OC setting and use the stress test and try to send a text it locks ups, no matter what speed im using. 1.45GHZ works but locks up after use without stress testing, and 1.40GHZ works fine until put under a lot of stress, but drains battery fast so ive been messing around wit the settings. Whats a great way to test my settings?

The Stress Test litterally just goes to town on your poor phone. It calculates PI to 800 decimal places over and over and over again until you tell it to stop. I don't recommend trying to do anything else while it is going. Just let it run and see if it craps out. Then be sure to stop it

gweedo767 said:
The Stress Test litterally just goes to town on your poor phone. It calculates PI to 800 decimal places over and over and over again until you tell it to stop. I don't recommend trying to do anything else while it is going. Just let it run and see if it craps out. Then be sure to stop it
Click to expand...
Click to collapse
Alright thanks, how long should I let it run?

AsaSpades said:
Alright thanks, how long should I let it run?
Click to expand...
Click to collapse
How long you let it run is up to you.
I typically start it then set it on my desk while I cook dinner/take a shower/do chores etc..
When I am done I check it out and see if it crapped out or not.
Also, I have tried all 3 methods currently available for OC'ing our X's and (in my opinion) this is the best out of them.
Nice user interface, some good starting points for OC'ing and with the latest build you get current/max/min clocks and battery temp.
Now, he just needs to add current voltage so I know what speed and voltage my X is pulling at that time.
OH, and some kind of log would be tits as well.
(Just thinking out loud)
D.

I keep getting the "oc in 90 seconds" pop up randomly even though I turned it off and applied settings...seems to be on anyway .. Many reboots and still getting the message

adammsu said:
I keep getting the "oc in 90 seconds" pop up randomly even though I turned it off and applied settings...seems to be on anyway .. Many reboots and still getting the message
Click to expand...
Click to collapse
Yep, I have noticed that as well.
I thought it might be memfree I was running, so I uninstalled it this morning and will see if that makes it go away.
If not, it is only a minor annoyance.
D.

debaucher said:
Yep, I have noticed that as well.
I thought it might be memfree I was running, so I uninstalled it this morning and will see if that makes it go away.
If not, it is only a minor annoyance.
D.
Click to expand...
Click to collapse
i agree, only minor, IF IN FACT that it really has been overclocked the whole time., and isn't dropping up and down all day.

I also have been having the same issues but I thought it was just me.
Sent from my DROIDX using XDA App

AsaSpades said:
I was wondering how the stress test works, everytime I use an OC setting and use the stress test and try to send a text it locks ups, no matter what speed im using. 1.45GHZ works but locks up after use without stress testing, and 1.40GHZ works fine until put under a lot of stress, but drains battery fast so ive been messing around wit the settings. Whats a great way to test my settings?
Click to expand...
Click to collapse
I think the problem here is the 1.45 ghz. To increase the Frequency that drastically, you also need to increase voltage. With a voltage setting too low you will lock your phone. The closer you get to a stable VSEL value the more you will be able to do before it locks up. That is why the stress test is so powerful a test to determine if the voltage is appropriate. When at 1.40 ghz your voltage must be close to stable if you can use under lite usage, but if you can only use it lightly, why OC so drastically?
Another App in the market, Droid x/2 Overclock, gives an advised list of frequencies and the VSEL value, and for 1.45 ghz, it advises 82 VSEL as the starting point. which is about 33% more power than it uses at stock frequency (62 VSEL). This is why you said you are tearing through your battery much quicker.
To alleviate the added draw, what I do, is run 2 settings, I leave it undervolted and clocked down to 750 mhz for every day use (barely notice a difference from stock performance) which increases my battery life to 35 hrs + and have a second setting for things like Emulators clocked up to 1.45 ghz running 78 VSEL very stable, never locks up. The added step is worthwhile to me since it both saves the added strain on the processor, Less Heat, and drastically Increases Battery Life.
If you insist on leaving it full blazing 1.45 ghz, get SetCPU (also in the market) and set profiles that can down control power, ie when my screen is off, the CPU is capped at 300 mhz. For the most part the Android OS already controls this pretty decent, but I like to be able to manually control it myself.

I would really like to see the application stop the service after it does it sets the clock after 90seconds.
As it stands now, I force stop it every boot.

[Q] battery optimized ROM

I have seen pretty many ROMs here, but am unable to make out which ROM is best optimized keeping battery life in mind. Could anyone please help suggest me a ROM or two that give the most of the battery life. Please.

You could take any ROM that will work with a kernel supporting OC/UV (like Setiron's) and use Xan's voltage app to limit the top speed of the CPU to something less than stock (1ghz is stock, your choices would be 800, 400, 200, 100)
Then apply an undervolt as low as you can go while still being stable.
This will of course result in a slower device, but that's the tradeoff. Less speed for more battery life.
Do note that the screen is the largest user of power by far and thus you can make the most difference by keeping the backlight as low as tolerable and shut it off whenever you aren't actively using it.

Da_G said:
You could take any ROM that will work with a kernel supporting OC/UV (like Setiron's) and use Xan's voltage app to limit the top speed of the CPU to something less than stock (1ghz is stock, your choices would be 800, 400, 200, 100)
Then apply an undervolt as low as you can go while still being stable.
This will of course result in a slower device, but that's the tradeoff. Less speed for more battery life.
Do note that the screen is the largest user of power by far and thus you can make the most difference by keeping the backlight as low as tolerable and shut it off whenever you aren't actively using it.
Click to expand...
Click to collapse
Thanks Da_G. I did use SetCPU, and set the speed to 800, but for some reason it is giving me lower battery life compared to without SetCPU. So took it out.
Also, I have my screen brightness turned all the way down with auto set to off.
I meant to ask for a ROM that has all the battery hogging stuff in it removed/optimized.
I am currently like 45% left after about 8 hours with moderate usage. Trying to see if I can stretch more than this.
My today's usage statistics:
1. 11 hours 25 min 4 secs since unplugged
2. Battery remaining: 63%
3. Voice calls: 1h 10m 15s
4. Display: 1h 15m 42s
5. 2 gmail accounts with push turned on with about 10 mails delivered today
6. google voice with push all time with about 100-120 messages delivered using push
a. I do not have SetCPU.
b. I have my brightness set to 0, with auto-brightness turned off.
c. I used SamServMode to turn on EDGE, and 3G turned off since the phone was off charging hook. In short, on EDGE all the time.
d. Static but nice, colored wall paper.
Could anyone suggest me if this is good enough. And any ROM that could get me battery atleast on par with what I am getting.

A few of my ideas:
1. Use a dark colored theme. Our nice SUPER AMOLED screens don't use up much power to draw black - so the more black - the merrier.
2. Be careful of what extra apps running. Things like widget locker are one more app to run. Go slender. Theme's are okay if they replace files like frameworkres.apk but if they run in background (see it under processes) then that's bad.
3. Be extra careful of making sure you are fully charged when you flash. This means, charge, turn off, charge, turn on, charge, flash. I get a little more charge when I go back to eclair stock .
also note that 95% of battery is the screen
Everything else that was said before me was spot on so try that too.

fatttire said:
A few of my ideas:
1. Use a dark colored theme. Our nice SUPER AMOLED screens don't use up much power to draw black - so the more black - the merrier.
2. Be careful of what extra apps running. Things like widget locker are one more app to run. Go slender. Theme's are okay if they replace files like frameworkres.apk but if they run in background (see it under processes) then that's bad.
3. Be extra careful of making sure you are fully charged when you flash. This means, charge, turn off, charge, turn on, charge, flash. I get a little more charge when I go back to eclair stock .
also note that 95% of battery is the screen
Everything else that was said before me was spot on so try that too.
Click to expand...
Click to collapse
Thank you kind sir. I shall do this. But I am not flashing anymore.
I loaded the AOSP ROM from Spaceman here
Code:
http://forum.xda-developers.com/showthread.php?t=827153&page=36
and am getting pretty much the battery backup I was getting with stock.
Thanks a bunch everyone who helped me on this.

[Q] Phone not sleeping

Hey all, recently rooted my Hero to CM7 RC4 and I've noticed that it doesn't actually sleep, even when the screen is off. If I turn the screen off (to "sleep" it) for a minute, the up-time (in Status) also goes up by a minute. My battery life is also very poor and is likely a result of the phone never spooling down. Poking around the web, some people thought this was from the default SMS app, but this happened before I had ever sent a text (only received one.) I even installed handcent and used it for a bit, but the phone still doesn't sleep properly. Any ideas?

Have you gone into Spare Parts and checked Partial Wake?

stayclean said:
Have you gone into Spare Parts and checked Partial Wake?
Click to expand...
Click to collapse
I did, but it said the only appreciable lock was 3m 25s for Android System (all time.) Dialer was 4s all time. There are no stats for 'time since last boot' or 'time since last unplugged'; I recently rebooted and have the phone currently plugged in.

Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.

gaan kak said:
Hey all, recently rooted my Hero to CM7 RC4 and I've noticed that it doesn't actually sleep, even when the screen is off. If I turn the screen off (to "sleep" it) for a minute, the up-time (in Status) also goes up by a minute. My battery life is also very poor and is likely a result of the phone never spooling down. Poking around the web, some people thought this was from the default SMS app, but this happened before I had ever sent a text (only received one.) I even installed handcent and used it for a bit, but the phone still doesn't sleep properly. Any ideas?
Click to expand...
Click to collapse
You do have the End button Behaviour to sleep right?
its in sparepatrss?

stayclean said:
Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.
Click to expand...
Click to collapse
Right now I have wi-fi off, with generally average phone service on 3G. Sometimes it dips down to 1 bar or reaches 4, but is usually 2-3.
I have the governor set to 'ondemand', with a min of ~176 and a max of ~714. The brightness is set to auto. I don't know if I have much stuff auto-syncing, is there a way to check if I do? I don't have very many apps installed - I just rooted this afternoon, and this is my first android phone so I'm trying to take it slow.

davidevan said:
You do have the End button Behaviour to sleep right?
its in sparepatrss?
Click to expand...
Click to collapse
Pretty sure in Android, the end button defaults to sleep anyway, so I don't think that really accomplishes much. Maybe try turning off 3G when not using the phone actively? That will drain the battery a bit.

stayclean said:
Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.
Click to expand...
Click to collapse
Yeah, you're right...uptime has nothing to do with sleeping.
To the OP...reboot the phone then let the phone run for about 1.5 - 2 hours or so without using it. Then go to Menu - Settings - About phone - Battery use. Then tap the graph at the top where it shows your time and compare your Awake time bar to your screen on time bar. They should be similar, with a bit more in the awake time depending on wat is set to sync.

To be honest, there is no fix to be honest. I've had this problem on many occasions and it fixes itself automatically whenever it wants to.
Sent from my HERO200 using Tapatalk

What radio are you using??? What kernel are you using??? Also try unckecking auto brightness. Also I think I read the ondemad governor has no sleep frequency,so if your clocked at 748 then your still at 748 when you hit the end button to sleep. Also there's no need to have the end button set to sleep in spare parts the rom should sleep on its on. lm not sure but I don't think the phone will sleep being on that governor. Try smartass or conservative and see if it sleeps then. Also make sure you have compatibility unchecked in spare parts. Also in settings under accounts&sync uncheck mobile data. That will need to be rechecked again to use your data services. Having it on all the time drains big time. Hope some of this helps. If not just post here or pm me and if I can help I will good luck
Yea it's Me Again With the
Modified Hero

laie1472 said:
What radio are you using??? What kernel are you using??? Also try unckecking auto brightness. Also I think I read the ondemad governor has no sleep frequency,so if your clocked at 748 then your still at 748 when you hit the end button to sleep. Also there's no need to have the end button set to sleep in spare parts the rom should sleep on its on. lm not sure but I don't think the phone will sleep being on that governor. Try smartass or conservative and see if it sleeps then. Also make sure you have compatibility unchecked in spare parts. Also in settings under accounts&sync uncheck mobile data. That will need to be rechecked again to use your data services. Having it on all the time drains big time. Hope some of this helps. If not just post here or pm me and if I can help I will good luck
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I am merely speaking from experience with no programming or dev experience, but I think ondemand actually does sleep. I use it at 176/729 and my awake and screen on is always similar. See the screenie below and look at the broken blue line below the battery up time. If it wasn't sleeping that line would be solid. Again, this is just my personal experience using ondemand.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

make it sleep=
just give it some nice warm hot cocoa with a dab of whisky, works like a charm

ranger61878 said:
I am merely speaking from experience with no programming or dev experience, but I think ondemand actually does sleep. I use it at 176/729 and my awake and screen on is always similar. See the screenie below and look at the broken blue line below the battery up time. If it wasn't sleeping that line would be solid. Again, this is just my personal experience using ondemand.
Click to expand...
Click to collapse
I mean you could be right, I'm no dev by far myself but
I'm using jm's kernel 806. Its based off of the same kernel as the aosp gb builds. If you check his kernel thread I asked this question and was given a different answer. Maybe I misunderstood him or didn't ask the question correctly. I'll send him a pm and see if he's in the mood to share some knowledge. I read that link you posted on aosp's thread, very helpful in understanding the kernels operations a bit better. But it didn't mention what those selected governors default to while sleeping. I mean how can I really know what frequency the kernel is currently at while its sleeping??? The min/max can be set with the default oc app. But not the off screen settings. Unless I'm missing something?? And that could be the case??
Yea it's Me Again With the
Modified Hero

I too am noticing lots of awake time on my battery graph with CM7 RC4. I rebooted about an hour ago, and haven't touched my phone until taking these screenshots. (Sorry for hosting them offsite, the network here blocks the xda uploader.)
http://img828.imageshack.us/slideshow/webplayer.php?id=sparepartspartialwakesil.png
One thing I found very interesting is that even though my phone shows nearly 50 minutes of 'awake' time, my battery still reads 100% even though it's been unplugged the entire time.
sleepy

laie1472 said:
I mean you could be right, I'm no dev by far myself but
I'm using jm's kernel 806. Its based off of the same kernel as the aosp gb builds. If you check his kernel thread I asked this question and was given a different answer. Maybe I misunderstood him or didn't ask the question correctly. I'll send him a pm and see if he's in the mood to share some knowledge. I read that link you posted on aosp's thread, very helpful in understanding the kernels operations a bit better. But it didn't mention what those selected governors default to while sleeping. I mean how can I really know what frequency the kernel is currently at while its sleeping??? The min/max can be set with the default oc app. But not the off screen settings. Unless I'm missing something?? And that could be the case??
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I haven't a clue...maybe JM can shed some light for us

the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.

il Duce said:
the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.
Click to expand...
Click to collapse
I have always used 176/729 ondemand and had no issues with music and get great battery life (and my phone sleeps ).

il Duce said:
the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.
Click to expand...
Click to collapse
But is there any way to accurately check or confirm the actual frequency??? Or follow the governor design???
Yea it's Me Again With the
Modified Hero

laie1472 said:
But is there any way to accurately check or confirm the actual frequency??? Or follow the governor design???
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I don't know that I understand you... The whole point is that they scale based on conditions, so the actual freq would be changing constantly (but only to your min setting). The smartass gov is the only one with screen off/on specific freq - it caps to 352 screen off, and min is 528 screen on... I suppose there's a way you could monitor it using adb, maybe ddms, but it would be changing based on your current load or input, so you wouldn't really get much from it. Does that help?

il Duce said:
I don't know that I understand you... The whole point is that they scale based on conditions, so the actual freq would be changing constantly (but only to your min setting). The smartass gov is the only one with screen off/on specific freq - it caps to 352 screen off, and min is 528 screen on... I suppose there's a way you could monitor it using adb, maybe ddms, but it would be changing based on your current load or input, so you wouldn't really get much from it. Does that help?
Click to expand...
Click to collapse
Here's what I'm getting at. If the frequency constantly changes due to the users demand or cpu load and maxes out at the selected frequency but doesn't go below the selected frequency either. Then lets say its in the middle of scaling up or down and the user hits the end button, then what frequency would the cpu be at??? Being that it's no way of telling if it hit the min or the max user defined choice. So if the user has a min of 352 and a max of 768 and this were to happen. Couldn't the kernel then be put to sleep at a frequency of 768 ??? After all its still in line with the user defined settings. With apps like over clock widget and set/cpu you could select the off screen clock settings but being as those apps conflict with the native app how can the user be sure of what the off screen frequency is set to if this were the case???
Yea it's Me Again With the
Modified Hero

[Q] Awful Battery Life - 5 Hours and 5% left. OG Droid.

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.

Did I just screwed my lineageOS 15.1 installing elementalX using their official app?

I was struggling with my Nexus 6 performance very badly. It was almost unusable. First, its battery used to drain fast. I felt the low performance was due to battery. So I replaced the battery. I also factory reset the phone. After factory resetting the phone was at least smooth. But as soon as I install some apps (not a lot of them), it started to slow down. I used to run 200+ apps without any lag on my Nexus 6. But now it was struggling with 50+ apps. So I felt it must be stock Naugat. So I went to flash lineageOS 15.1 (my first successful experience with MODing android, earlier I bricked one phone and after that never thought of trying it out again). The performance is a bit improved. But its definitely not smooth. Also this is the case with no extra apps installed. Only basic gapps are their. So I am getting fishy about whats going on. So I googled and found this thread.
Someone their said that its working on only two cores!!! And something immediately clicked to me what I have seen but never observed well. Recently I bought poco f1. Just to do performance comparison, I installed antutu on both Nexus 6 and poco. Also whenever I opened Antutu CPU monitor, it always showed two cores are sleeping. That was not the case with poco. All cores are always working. For example, I just charged my Nexus 6 battery to 100%. Also its not in battery saver. Still it says two cores sleeping and only two cores active:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
People at reddit said installing custom kernel fixes this issue. There are some recommendations on reddit page: Franco, b14ckb1rd and elementalX. I googled and found that there is elementalX app in play store which says to automate whole process. I bought it for ₹250 and installed, backed up current kernel and installed elmentalX. It went into TWRP and installed elementalX successfully. But now my lineageOS is not booting up. It is animating its icon for last 15 minutes? Is it bootloop. I didnt read much earlier about kernels. I felt as offical app installs it, it must be working one. But now reading this thread, it seems that my lineageOS got screwed again. So I have some questions:
1. Is my lineageOS screwed now?
2. If yes what should I do? Flash backed up kernel through TWRP. If yes, how? I never done. Is the procedure same as installing custom ROM? Putting kernel zip in phone and then installing ZIP from TWRP?
3. Is their any custom kernel out their compatible with lineageOS 15.1 which can enable my CPUs two sleeping cores?

Just installed backed up kernel from TWRP. Got my NExus 6 alive. Now point is which custom kernel is compatible with lineageOS 15.1 that will awake my two sleeping cores. My Nexus 6;s two core's are still inactive at 80% battery . Overall performance not smooth.

After watching some videos and some googling, I realized that its not about the kernel actually which turns off cores but its hotplug mpdecision. I installed kernel audiutor,
hotplug mpdecision, I enabled all cores of my Nexus 6. Also I realized that max frequency of my active cores were something 1958 MHz. I just increase it to max 2649 MHz and rebooted. My Nexus 6 is going super smooth now. Also ran geekbench4 benchmarks.
These are the benchmarks.
Before changing CPU stuff
================================================
Benchmarks 1
-----------------------------------------------------------------------------------------------
Single core: 593
Multicore: 997
After changing CPU stuff
================================================
Benchmarks 2
-----------------------------------------------------------------------------------------------
Single core: 818
Multicore: 1009
Benchmarks 3
-----------------------------------------------------------------------------------------------
Single core: 1069
Multicore: 3029
I feel that two cores were still offline during benchmark 2. When I checked after benchmark 2, they were off in kernel adiutor CPU monitor. I re-enabled them and I reran the geekbench. I ended up getting benchmark-3 which are quite good and in fact above average for Nexus 6. For 5-10 minutes now, all cores are active.
I then googled and realized that mpdecision restarts after every reboot. So I have to disable mpdecision on every reboot to enable all cores. Initially I was not getting meaning of two ON/OFF switches on kernel adiutor's interface. They were "Apply on boot" and "mpdecision". Now I have "Apply on boot" switched ON and "mpdecision" switched off. That means on every reboot, all my cores will be up at full frequency right?
Also that means more power consumption. So I have done certain things to compensate. Enabled dark mode so that Nexus's quad HD AMOLED will consume less power. Also installed Franco kernel's Servicely app which allows app and services to put on sleep when screen is off. I am also planning to use Nexis 6's always in battery saver mode. I am ok as long as it performs fast (with two core off, battery saver mode was useless, now it seems like very normal). Its just that only top and bottom orange bars/strips in battery saver mode annoys me.
One more thing I will love to have to save battery. In MIUI, there is per app setting for what to allow when app is in background as can be seen here: http://nine-faq.9folders.com/articl...-background-restriction-on-the-xiaomi-devices On my poco f1, I keep almost all apps "No background activity mode". Only handful have "No restriction". This is letting me extend battery to days straight. Is similar possible on lineageOS say through some apps or setting.
Also can all feel my config all fine? Latest lineageOS + All cores running at full speed + Power saving settings explained above? Is this perfect for performance and battery life?
(Will be testing battery life soon for few days.)

Mahesha999 said:
One more thing I will love to have to save battery. In MIUI, there is per app setting for what to allow when app is in background as can be seen here: http://nine-faq.9folders.com/articl...-background-restriction-on-the-xiaomi-devices On my poco f1, I keep almost all apps "No background activity mode". Only handful have "No restriction". This is letting me extend battery to days straight. Is similar possible on lineageOS say through some apps or setting.)
Click to expand...
Click to collapse
I don't know much about LOS and how close it is to AOSP but in ABC ROM you can go to Settings --> Battery --> click three dots in upper right corner --> select Battery Optimization to set what apps run in the background.

Mahesha999 said:
Just installed backed up kernel from TWRP. Got my NExus 6 alive. Now point is which custom kernel is compatible with lineageOS 15.1 that will awake my two sleeping cores. My Nexus 6;s two core's are still inactive at 80% battery . Overall performance not smooth.
Click to expand...
Click to collapse
- Install the latest LOS nightly 20180926
- in battery management, set the performance profile to fast
- with a kernel manager, disable mpdecision
if that still isn't fast enough, install this custom kernel:
https://forum.xda-developers.com/nexus-6/development/testers-oreo-8-1-custom-kernel-t3798205
- in battery management, set the performance profile to fast
- with a kernel manager, disable mpdecision and CPU hot plugging