Database Users

Power Management for Hermes!

Hi Guys,
I saw this on a foreign website. Not sure if this has been posted already.
[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
[HKEY_LOCAL_MACHINE\Comm\Irsir1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
[HKEY_LOCAL_MACHINE\Comm\PPTP1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
[HKEY_LOCAL_MACHINE\Comm\L2TP1\Parms]
"DisablePowerManagement"=dword:1
Change to
"DisablePowerManagement"=dword:0
This will turn on power management for the above protocols. Logically, it should save us some power. The orginal poster claims that there is a significant increment in his battery life .
I've applied this tweak to my SPV M3100, Hopefully this will save me more battery life.
N.B. please do a backup before applying this reg tweak just to be on the safe side.
Update: been using it for the few days and I must say I've noticed some improvement in Battery life. no other issues at the moment so far so good

What exactly are the above protocols? L2tp1, pptp1... what are those for? its not like that nokia tweak where it gives less power to the antenna?
Basicly is this tweak gonna cripple my device in any way?

fone_fanatic said:
What exactly are the above protocols? L2tp1, pptp1... what are those for? its not like that nokia tweak where it gives less power to the antenna?
Basicly is this tweak gonna cripple my device in any way?
Click to expand...
Click to collapse
The above mentioned protocols are used for VPN (Virtual Prvate Network).

fone_fanatic said:
Basicly is this tweak gonna cripple my device in any way?
Click to expand...
Click to collapse
I've made those registry changes to my TyTn. So far, I can find no bad side-effects.

software_samurai said:
I've made those registry changes to my TyTn. So far, I can find no bad side-effects.
Click to expand...
Click to collapse
no bad side-effects... but what about good?

shogunmark said:
no bad side-effects... but what about good?
Click to expand...
Click to collapse
Hmmm... Well, so far I think the battery life is a little better. But I need more time to really test it.
(Now that I've installed the Battery Status plugin, I can see the power usage, so I'll fiddle with these settings and see what happens to the numbers.)

gfreek said:
This will turn on power management for the above protocols. Logically, it should save us some power. The orginal poster claims that there is a significant increment in his battery life .
Click to expand...
Click to collapse
Thanks for posting.. but Like most random registry tweaks, I'd suggest not touching them for the following reasons:
They are not in the associated MSDN documentation for the reg keys. This is usually MS's way of saying 'this doesn't work right so we don't talk about it so no one thinks we support it'.
Second, the protocols it refers to are all network protocols that aren't generally in use by most people anyway and those that do wouldn't have vpn's running 24/7 therefore any power savings would be minimal.
Thirdly, they were purposely disabled for some reason. I assume because there is a problem with them. And my device is unstable enough
Just my 0.02c

FYI: My test results
In my admittedly objected tests (I changed those settings, soft-rebooted, and then watched the batter drain number for a few minutes), it looked as though enabling the power management for those 4 settings brought the batter drain down a little faster then with them disabled. When they were disabled, it took several minutes for the battery drain to drop down to about 90mA. When they were enabled, the batter drain dropped down to 90mA within about 2 minutes. However, in both cases, the battery drain seemed to bottom out at about 88mA after a while (actually, right after the backlight went into power-saving mode). So I can't say these settings would save a "significant" about of power. YMMV.

icemantwilight said:
Thanks for posting.. but Like most random registry tweaks, I'd suggest not touching them for the following reasons:
They are not in the associated MSDN documentation for the reg keys. This is usually MS's way of saying 'this doesn't work right so we don't talk about it so no one thinks we support it'.
Second, the protocols it refers to are all network protocols that aren't generally in use by most people anyway and those that do wouldn't have vpn's running 24/7 therefore any power savings would be minimal.
Thirdly, they were purposely disabled for some reason. I assume because there is a problem with them. And my device is unstable enough
Just my 0.02c
Click to expand...
Click to collapse
If it's not supported, I can understand it. But, I've found with my Wizard, and now my Hermes, that just because it's disabled, doesn't mean it isn't useable. I've found a variety of registry keys that I love tinkering with. That isn't one of them thankfully, but some of the things that they disable there aren't any problems that I've seen, so therefore I add them back in.
A good example is that "Wireless" today plug in. Sure, it really doesn't server a whole lot of purpose, but I like it, so I put it back in.
Much of it is in the eye of the beholder. N00bs probably shouldn't do some of this stuff. Then again, if it weren't for our curiousity, we'd never make any progress hacking these devices...

icemantwilight said:
Thanks for posting.. but Like most random registry tweaks, I'd suggest not touching them for the following reasons:
They are not in the associated MSDN documentation for the reg keys. This is usually MS's way of saying 'this doesn't work right so we don't talk about it so no one thinks we support it'.
Second, the protocols it refers to are all network protocols that aren't generally in use by most people anyway and those that do wouldn't have vpn's running 24/7 therefore any power savings would be minimal.
Thirdly, they were purposely disabled for some reason. I assume because there is a problem with them. And my device is unstable enough
Just my 0.02c
Click to expand...
Click to collapse
This wouldnt be the right forum if noone would investigate any kind of improvement (or at least finding out if it does anything, positive or negative)
I we would go for what MS suggests or covers in their docs, we wouldnt flash roms, apply MUIs or anything in that regard.
After all this site is called XDA-Developers and playing around with tools, tweaks and sharing knowledge is what this is about.
So far i cannot see any change in battery life. I will give it a few more test.

if there is a way that we could scale the processor based on the processing requirements, then we will always consume optimal power... something similar to speed-step intel has on PC's.
from what I know for this to be possible, the CPU has to have dynamic voltage scaling, meaning that when the processing load is reduced, the core voltage of the cpu reduces yielding reduced clock frequency. when more isntructions need be executed, the voltage supply to the CPU core will increase, hence increasing clock frequency.
has anyone read the documentation in regards to the architecture of the samsung CPU? if it supports dynamic voltages scaling, and if it is wired up to a dynamic voltage source, then there could be some tweak to enable such a feature.

I've had the pleasure of reading the Samsung CPU manual. You should too!
It doesn't support much clock speed scaling - ie you can't easily overclock (and even then, not by anything of signficance). Voltage scaling is possible. Look into Pocket Hack Master.
V

vijay555 said:
I've had the pleasure of reading the Samsung CPU manual. You should too!
It doesn't support much clock speed scaling - ie you can't easily overclock (and even then, not by anything of signficance). Voltage scaling is possible. Look into Pocket Hack Master.
V
Click to expand...
Click to collapse
if the core CPU voltage can be scaled, then we instantly have a scaled clock frequency. there is a direct relationship between power dissipation in CMOS semiconductors, clock frequency, supply voltage, capacitance and probability if switching (ie dynamic clocking).
Here is an interesting read for you softeare hackers out there. it is a project ot implement dynamic voltage scaling on pda's for those that have CPU with fine grian dynamic voltage scaling. the work is on linux os on a pda, but the methodology should be the same.
http://www.eecg.toronto.edu/~tamda/csc2228/
Dynamic voltage scaling doesnt imply that we can overclock the device, but instead keep the CPU running at a speed that is ample for the processing that it is doing, ie, dynamic. so if there are no apps runing besides an idle today screen, why keep the CPU at 400MHZ running at its full voltage supply. lets reduce it to an amount that it enought to handle the performance requirements of having an idle today screen BY reducing the supply voltage.
Dynamic voltage scaling is basically an algorith (if the hardwre is there) that can be implemented at the CPU level or OS level to monitor instructions required per second etc, then adjusts the CPU core suply voltage accordingly. So in effect, we can get our devices running from 10MHz (doing nothing and consuming little power - I am sure this is the case 70% of the time) to 400MHZ (running apps, GPS, video streaming etc - and consume more power)
I have a PhD student doing his thesis on dynamic voltage scaling for mobile medical devices and the philosophy is "do (process) only what you have to do (process)"
EDIT: Just looked into pocket hack master, it does some kind of clock scaling, well, I learn new things everyday, this is my first PPC and its overwhelming.

vijay,
what is the model number of the samsung CPU in the hermes? i cant seem ti find it?
EDIT: I found it, Samsung K5D5657ACA-D090, it seems voltage scaling is not supported by pocket hack master, that app supports the samsung ric micr S3C24XX series in which the S3C24A0 has a max clock of 200MHz running of a 1.2V supply

also you may want to be careful with Pocket Hack Master.. some people have reported it completely bricking their device. I had it installed it hours before my phone died, but i dont know if it was the cause due to a high amount of irregular bad blocks that werent there when i got the phone.

shogunmark said:
also you may want to be careful with Pocket Hack Master.. some people have reported it completely bricking their device. I had it installed it hours before my phone died, but i dont know if it was the cause due to a high amount of irregular bad blocks that werent there when i got the phone.
Click to expand...
Click to collapse
I dont trust it, it doesnt support our samsung CPU in terms of voltage scaling and by simply scaling the processor frequency isnt really going to accomplish much of an energy saving in terms of the big picture. by big picture i mean with respect to LCD screen energy consumption, GSM radio and UMTS radios (all of which use separate LNA's for each of the Centre Frequency bands) BT etc....

This trick, run on wm 6.5 ?

We can now overclock our phones!

Couldn't really see any discussion on this yet, and personally it's in a location on the forum that I rarely visit but I've found an overclock tool that is slowly becoming very good indeed for our processors. Link to thread is here. I'm soo far up from 528Mhz to 748Mhz (been stable for the past 6 hours no problem). Just make sure to follow the thread (instructions are linked to ensure overclock remains applied through scripts and 3rd party apps). Should take no longer than 30mins for a well versed user to set up. Please don't try this if you haven't got a clue what you are doing as there is soo much scope for error and dead phones! You may also need to customise any scripts to your specific phone/software build. CDMA phones as usual are different from what I've heard. But anyway good luck, I'm gonna keep trying to push the Mhz up (aiming for 850Mhz ).

Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.

It's actually remained pretty cool, and when it's in my pocket it's only running at stock clocks anyway. Only when I'm using it does it get to the full 748Mhz. Running wifi router and charger and temps are not noticeably hotter than usual...

um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
recommendations: Download v1, not v2. ESP if you dont know what you're doing. Then download the zip im attaching, there's 2 mortscripts in there and a registry addition, THESE MUST BE IN THE STORAGE CARD ROOT. use the regisitry addition FIRST (just associate w/e regedit software you use, then run the .reg file in total commander), then go back to total commander, edit the .mscr "Toggle_boost" and adjust the value boost = "x" to whatever value you want the phone to OC at, eg boost = 41 is 787mhz which is stable for me, test yours out.
THEN, open and install rhodiumkbdcontrol (attached), reboot, go to settings>system>keyboard config> add key
1st pick which key you want to be the OC boost swtich, I have it mapped to my PTT button. click the plus sign, drop down menu, run program, then highlight "run program" in the list then click "..." then type in
Program: \windows\mortscript.exe
Arguments: "\storage card\toggle_boost.mscr"
This time you wanna use the power key.
same general instructions except
Program: \windows\mortscript.exe
Arguments: "\storage card\boost_off.mscr"
then plus sign again, drop down menu, default key action, and click extended emulation. THEN hit update config. should work like a charm, also autoover clocks to 610, the boost button with send you up the w/e the boost = "x" is set to, and then back again, most find 710mhz to be the stable point, and feel free to ask questions

sorry, heres the zips

wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs

I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!

miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Edit:
I just read threw the above links and guides and was wondering if there is a more automated way of setting this up rather than having to link it to a button press. I'm guessing this has not been figured out yet (or the guides would have mention of it ). Just curious.

dantegl36 said:
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Click to expand...
Click to collapse
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627

Check it!
Outlaw78a said:
Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.
Click to expand...
Click to collapse
I have used this, NRG also does. I have NEVER had any problems and mine is as high as 787 as long as I'm running it which is constantly.
XITruthiX said:
um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
Click to expand...
Click to collapse
100% agreed. Been running at the highest speeds with NO problems, no batt drain, no heat probs, nothing.
XERO_Racer said:
wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs
Click to expand...
Click to collapse
Not unless you are having excessive heat problems. Since there are basically no people reporting these problems, I wouldn't worry.
miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Once again as stated earlier, 100% agreed.

Do I have to keep plugged in?

miked79928 said:
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627
Click to expand...
Click to collapse
I thank you for this, but I'm not sure how to implement it. I have installed Mortscript, I've copied the code into a file I called overclock.mscr and modified the code reflect the reg values on my Tilt 2. and I've placed the script on the root on my SD card. I've installed MSM7kCpuSpeed on to my SD card. How do I make the script run automatically?
Thank you!

I take no responsibility for w/e happens to your phone with this advice.
Try putting a pointer in your start up to the over clocking script. Its highly unstable and could brick your phone or require a hard reset... thats why I do it with a toggle switch, i dont mind manually applying the OC with a hard key knowing its safe, esp because the situations where I actually NEED 787mhz are less common than needing to just wake the phone to answer a call or make a txt message.

I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution

dirtypiratehooker said:
I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution
Click to expand...
Click to collapse
Just a note, I'm not sure the insurance would cover burning a custom ROM into the phone, or overclocking the CPU. And if the chip is fried you can't burn the stock ROM back in. But then, they probably couldn't figure out it was updated without in stalling a new CPU. Umm, it would probably work.

Would a .cab for this ever be conceivable?

At this point, we have finally got a script that will work for most Rhodiums, Topaz (Diamond 2), and a few guys with other phones seem to be having good luck.
The device has to have Mortscript installed, and nettrip's MSM7 v2.
It is a single script solution that requires no pre checks in the registry, no key/button assignment, and you can change the speed settings from the script instead of the registry.
It throttles the OC up and down for calls, lock, and sleep, to avoid freezing on wake up and in a call. Some problems that still need to worked out by nettrip in the script. I don't envy him the work as the script(s) were bad enough. Four of us have hit that original script (by jpc) from about page 13.
You copy the script to the SD or the device root, create a shortcut to the file, copy the shortcut to Windows\Startup directory, reset/reboot the device and you are off.
You can use the MSM7 app to read the OC, but you should make sure to exit the app before sleep, lock, or power off, as it will error on reboot if left open.
To be honest, you never have to open the MSM7 app, as the script controls it in the background.
I believe the script is set for a low over clock. 691. My experience has been a 710 average, but a lot get a stable OC at 750+. I am running 748 and I think I will stop there. A 200MHz overclock will just have to do.The phone does not get hot, though with intense use, it does get warmer. Never warmer than when the battery is charging, tho.
I am running the nrg Sense Reference ROM, 23xxx based on Sense 2.5. I added the CHT 1.8x and the editor to save a few MHz, no biggy.
The overclock allows the Sense to work MUCH smoother, actually noticeable as even the weather animation is smooth.
And all the vid players seem to work better.
I have noticed NO extra battery drain than usual.
The script is only a stop gap measure until nettrip finishes his app, but it does work well with little effort. WAAAAY better now than even last week.
However, use the script at your own risk, as you can get too Medieval on the OC. Some guys are running 800+, more nerve than I have.
Anyway, if interested in the script or want to read some more about the app, you can start here
http://forum.xda-developers.com/showthread.php?t=725290&page=89
post #882 has the script.
Plenty of instructions on how to use (and make changes to the settings) in the last 30-40 pages.

Sorry if this is already explained, but can someone tell me in simple details how to keep my overclock at 729mhz even after screen lock or sleep mode? I've tried to follow previous posts but it keeps reverting back to 528mhz after locking and sleep.

Ok so this seems legitamite,everyones checking in with no problems.
other than the increased risk factor that always accompanys speed,
it seems our ppc's cpu was underclocked beforehand ?
i will try this and see if i get a gpu boost as well.
but ivr already experienced my phone overheating to the point
of shutting itself down,and the god-damned orange light is permenantly on...

Underclock in Froyo

The main thing I'm concerned about here is the time it takes to charge the phone.
What it seems like is happening is that the phone won't underclock like it did before froyo and it stays up above 500-600 mhz instead of much, much lower in the 200-300 range.
Can anyone tell me if I'm way off on this?
If I'm not, is there a way to test and see at which speed the processor is running, especially in standby?
Then, is there anything that can be done about this, or do we have to wait for the source code to be released and then for custom kernels to be developed that can help the phone be more energy efficient when charging.
Thanks

You could use Set CPU to limit the processor speed while the screen is off or charging.

My only concern with doing that is that when a task needs to be performed it would take alot longer to do it, and erase any positive effect of underclocking that way.
Does anyone know if this is a valid or known issue? Is anyone else seeing the same issue or know why its happening? Just looking for more info on this.

Kind of off topic, but does setCPU work with the latest leak of Froyo?
Sent from my ADR6300 using XDA App

I just have a setCPU profile set to 245/245 while screen off. Doesn't seem to affect anything in a negative way. SetCPU should work as long as your phone is rooted. Select "Autodetect" in device selection. Moving this to General with a redirect expiring in one month.

Keep in mind that underclocking will not work unless you disable the perflock. In setcpu, hit menu to do so. Its only per boot.

adrynalyne said:
Keep in mind that underclocking will not work unless you disable the perflock. In setcpu, hit menu to do so. Its only per boot.
Click to expand...
Click to collapse
thanks for the tip.. so I guess I'll have to disable perflock every time I reboot.. sigh..
Also, what does the "set to boot" check/uncheck option do?

You can set your default speeds with that option on boot. However, it will only work on perflock disabled kernels, and I haven't found a way to disable it in the stock kernel. Easy enough from source, but once its compiled, its a lot tougher, if not impossible.

I guess I don't want to deprive the device of it's full potential by underclocking it especially when I am using it... the processor speed being one of the main reasons why this phone stood out for me back then..
However, I do have the processor speed dip down to 245max/min when screen is off.. I think that should help with battery quite a bit yea? Also with the 245 max/min profile when screen is off.. I guess there is no need for an app killer anymore.

Thats what I am doing as well and the results have been promising. Just wish the perflock disable was permanent
I requested it as a feature in the dev thread, but I don't know if he will add it.
Seems to me he just needs to insmod the module that disables the perflock at the same time speeds are set with the at boot time option.
Not that I know anything about programming.

Ahh yes...forgot about the perflock on your Sense devices.

My understanding was having to do the perflock each time was intentional. Since it has a chance of crashing your phone, if it was permanent it would cause a permanent unrecoverable loop or something to that effect.
But I know nothing about programming either (WAY less than adrynalyne that's for sure), just remember reading that somewhere on the forums.

Didn't really intend for this thread to become a setCPU discussion, but got some good info out of it.
Was mainly trying to figure out WHY group doesn't seem to undertook natively and id there is a possible fix out there or at least looming.
That said. I'll be getting to a charger in a few minutes and anxious to see if this helps me with the charging issue as is seems to have with others.

s197 said:
My understanding was having to do the perflock each time was intentional. Since it has a chance of crashing your phone, if it was permanent it would cause a permanent unrecoverable loop or something to that effect.
But I know nothing about programming either (WAY less than adrynalyne that's for sure), just remember reading that somewhere on the forums.
Click to expand...
Click to collapse
Its true thats why it has been set up that way, and Im sure the dev did that for support reasons too.
Anything is recoverable though
Maybe the dev could add a secret geek code to unlock it for those of us who are stupid and wreckless

No seriously, battery life problem solved once and for all

No seriously, im not BSing! the battery life problem of xperia (and potentially any android phone, haven't tested on anything yet) is solved!!!
It does not require you to turn off any cellphone function!!!
I discovered this trick by pure luck the day before yesterday.
I used setcpu (i think any overclock will work but lets be specific for now) to set my phone's cpu to "performance" (by default i think it is kept on "ondemand") just to give a speed boost as im doing stuff. The phone was charging so i didnt have to worry to much about battery life anyway
after that i FORGOT TO TURN PERFORMANCE OFF, went to school with that setting.
I checked my phone at around 14:00, when my battery is usually down to 65% (horrible i know, i like to keep everything running 3G wifi bluetooth gps lots of widgets tasks in the background) to my surprise, my battery is at 86%
i used the same setting yesterday just to make sure that performance really saves battery and sure enough, it is just shockingly good
So basically, to save battery all you have to do is:
1. get an overclock app
2. do two settings
default=performance
when screen off=powersave
3. let it make you cry!
It should drain very little battery while idling and use a bit more power than usual when youre using the phone since you get the neat performance boost
So everybody do what i said and report back!
if it really works a charm for everybody, i believe that this method deserves to shine in the android development section.
lol please keep this post at the top! i feel guilty for keeping something this good to myself...

thanks for that, ive set my phone to when screen off powersave and ive made a simular profile for when the battery is at 25%, its already running juice-defender so hopefully they wont conflict.

People, this really will work! Please just try it and you will know what I mean

Did you mean overclock widget? Should i search in other resource than the market?
Sent from my X10i using XDA App

The difference between performance and ondemand is marginal; Performance would keep your CPU @ 998 MHz (or whatever you set the Max to). OnDemand jumps between the Max in the Min (usually 245 MHz). But you already can tell that it's on the max 99% of the time since if the phone was at 245 MHz, it would lag like hell. I don't see how this works, but ok, I'll try it.

If only there are solutions for people like me who won't condone to hacking our beloved phones =/

Um I used juice defender and upstart killer (only for software) and lost only ten % in 9 hours with at least 40 texts and a short phonecall and refreshed my weather twice. At this rate my phone would last more than 2 days even 3
I meant autostart killer sorry.... dam HTC keyboard
Sent from my X10a using XDA App

loneLEE said:
If only there are solutions for people like me who won't condone to hacking our beloved phones =/
Click to expand...
Click to collapse
I don't mean this in an insulting tone, but then why are you here?

loneLEE said:
If only there are solutions for people like me who won't condone to hacking our beloved phones =/
Click to expand...
Click to collapse
i just gave a solution. im not hacked either lol

my phone actually lasted a full 24hours and it seems like it could've lasted another 12 hours really. Thanks!

Oke i give it an try, i let you know if its realy works,
AlexPranee

so if i text a lot under these settings, does that mean my battery will die even faster within the, for ex., 10 min of texting time?

Apologies for stupid question, but where do I set powersave on screen=off? there is no such setting in setcpu.

vlissine said:
Apologies for stupid question, but where do I set powersave on screen=off? there is no such setting in setcpu.
Click to expand...
Click to collapse
Go to the Profiles tab > Add Profile > Condition: Screen Off | Scaling: powersave >Save

and use advance task killer then change kill frequency to (when screen off) . and kill level (aggressive ) .

dogwoofer said:
Go to the Profiles tab > Add Profile > Condition: Screen Off | Scaling: powersave >Save
Click to expand...
Click to collapse
Thank you. Should I also lower the max frequency in this profile?

mrljlamon said:
i just gave a solution. im not hacked either lol
Click to expand...
Click to collapse
I used juice defender (free) before, but in the end after hearing bad reviews, I uninstalled it. As for task killers, it's been debated that it does more harm than good. =/

hemo1001 said:
and use advance task killer then change kill frequency to (when screen off) . and kill level (aggressive ) .
Click to expand...
Click to collapse
Task killers are bad man, especially if you're on 2.2. That will actually kill your battery faster. Turn off auto kill. Only use a task killer to end a task that is stuck. The reason they are bad is because when you kill a task, it ends, but then starts right back up again. Keep doing this over and over, and your battery gets drained. If you need to end a task, don't be lazy, use Force Close in the Application section of Settings.

Product F(RED) said:
Task killers are bad man, especially if you're on 2.2. That will actually kill your battery faster. Turn off auto kill. Only use a task killer to end a task that is stuck. The reason they are bad is because when you kill a task, it ends, but then starts right back up again. Keep doing this over and over, and your battery gets drained. If you need to end a task, don't be lazy, use Force Close in the Application section of Settings.
Click to expand...
Click to collapse
thanks for the useful info i didn't notice that before . anyway you can disable the auto killing and that will make it easier to FC apps . and i removed every app that keep auto lunching it self and the battry stays around 2 or 2.5 days now .

This really does seem to work - The battery only went down 1% in the 8 hours I was asleep with this setting on

Watchdog detects Base System @ 60% frequently?!

Heyo bros so I'm experiencing what I'm afraid might be a problem:
I've been getting watchdog alerts regarding the "Base System" process. It notifies me that the CPU % at the time of the captures range from 40% to 60+%. Coincidence or not, it usually happens when I wake my phone from sleep- not when I unlock it, just when I press the power button. The moment the lock screen pops up, the phone's already vibrating and the watchdog notification is up in the status bar.
Battery life so far is:
9h 22m @ 74%; Phone Idle- 56% | Cell Standby- 22% | Display 17% (40m) | Android OS 3% | Voice calls- 3%
Who knows, maybe this^ looks normal. I just want to be sure.
I've heard talk of 'wakelocks' but I don't know exactly what they are, what might cause them, and how I can track them.
I'm currently running:
Atrix 4G (not 2, just for clarification)
CM7 xB^xN
Baseband reads: N_01.77.30P
Kernel version reads: 2.6.32.39-MB860-GB-Faux123-v0.2.1 [email protected] #14
Build number: GWK74
Totally honest, I don't know if that might be able to help diagnose the problem, but for what it's worth, I want to check two things:
1) I flashed Faux's enhanced stock CM7 kernel, and am pretty sure it took, but does that look to be the proper kernel version? I just want to be sure.
2) While I also flashed the "latest radio" in the CM7 xB^xN thread, I was certain there was an xx.97 radio (vs the x.77 radio that mine appears to currently have). Am I indeed on the latest radio version?
Would it hurt to reflash these two? Could either one, or maybe both, be the cause of this?
It also occurs to me: I've been using SetCPU and have ONE profile set up that forces my CPU to min/max 216/216 when the screen is off. Could that be causing it?
Thanks so much for any and all insight bros. Also, please let me know if there's any more info you might want to help diagnose what the dealio is.

Heyo guys,
I hate to bump this kinda soon, but this is definitely a problem.
It's getting to be that I don't even have to wake the phone up for the Base System to spike. I was woken up a couple times in the middle of the night by notifications saying it was really high.
You guys have any thoughts? I'd really like to get this resolved as CM7 is AWESOME.
Yes, you guessed it- I'm not anal about the fingerprint scanner or webtop. Just a stable and fully functional release.
Thanks for any help bros I really appreciate it.

Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!

AX-MA said:
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
Click to expand...
Click to collapse
Thanks for the insight bro. For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Looks like a couple of us are having problems then, though. We'd both really appreciate any info, advice, or help.

Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.

xyrovice said:
For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Click to expand...
Click to collapse
AX-MA said:
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
Click to expand...
Click to collapse
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".

WiredPirate said:
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
Click to expand...
Click to collapse
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.

xyrovice said:
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
Click to expand...
Click to collapse
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.

WiredPirate said:
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
Click to expand...
Click to collapse
Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
Also, is there any reason CM7 would have the minfree set to a default that causes this?
Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Thanks so much for saying this bro. Who knows, this might be the problem.
PS: I just tried this and am going to see if it works. Post #13 is the one that would really sum up my reaction of successful.
Hopefully maybe this helps my other bros.

xyrovice said:
1Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
2Also, is there any reason CM7 would have the minfree set to a default that causes this?
3Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Click to expand...
Click to collapse
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137

possible solutionary steps I've taken:
So Update:
I actually ended up checking out my (partial) Wakelocks with betterbatterystats, and I think I may have found a problem (diagnosed with alarmdump.txt from the Alarm Manager):
1) When I first flashed CM7 I thought, "Oh well why not really get comprehensive about keeping apps up to date" and I actually, for every single app, checked the "Automatically update" box in each one's market page. This led to a CATACLYSMIC wakelock that I'm now pretty sure could be the problem.
2)Google talk also seemed to be a little active with the screen off so I unticked the "sign me in auto..." box and made sure I signed out.
Lastly (not related to wakelocks), I checked on my TTS settings (see my last post about that).
Oh also LASTLY lastly I froze the modem fastdormancy manager in TiBU (kinda just for ****s and giggles). That said though, is the consensus on this that it's pretty harmless?
So, other bro who was having a problem, check and see if this might help you at all AYY
WiredPirate said:
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
Click to expand...
Click to collapse
Thanks for posting this. I checked ROM toolbox and it does indeed have the capability. That said, if my aforementioned possible solutions don't work, I'm turning here. Thanks for the info bro.

Watchdog is flagging the "base process" app because IT IS using over 60% of your CPU BUT it is using 60% of your CPU that is running at 216MHZ.
It's your screen off setcpu profile of 216/216, if you bump up the max to 456 the alert will go away. When you have it set as 216/216 Watchdog (I believe) thinks that is the actual max cpu speed and bases its percentages off of that. I got that warning before and after a bit of troubleshooting (actually tried several different things) found that was the problem.
I am not sure but if you "whitelist" a app in watchdog it might ignore it as well. However my alert level was set at 80% and it would still set it off, so I think the higher speed might just be better.