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 ?
Related
Has anyone noticed any long term disadvantages to overclocking the Wizard? Does the battery life permanently decrease? What speeds are you running yours at, and how long have you been doing it? Have you noticed anything at all which indicates it's not good for the hardware?
Cheers
reply
i believe that it's safe to overclock the mda...just set it at an acceptable rate (264mhz for me) and make sure not to run the battery all the way down...if you overclock the settings too high the device will freeze and reset (this is a fail safe procedure it goes through), so there is no need to worry...also don't overclock the settings too low as the phone becomes disfunctional when too low (about less than 132mhz for me)...the screen flickers because it's not being refreshed quick enough (my guess)...hope this helps...
I would set it to 240. I have done before, i'm just wondering if it's a bad idea leaving it permanently set to that level?
Cheers
yea you should be fine at that speed, but if you want you can overclock it higher if it will let you...just make sure that the phone is stable when using it...like i said in my earlier post my device is oc at 264mhz
Cool, thanks for your replies. How long have you had yours overclocked for? Do you use Smartskey?
Cheers
My self i ownly use it when need the extra speed, only with some games and wmv video files. I think it definitely lowers battery life and i would have worries about overclocking all the time and the long term effect it has on the processor (not so important if you only keep your wizard for a year and then change with a new contract - what i do new device once a year!) I found good speed gains with the registry wizard - http://forum.xda-developers.com/viewtopic.php?t=39725
have not found overclocking produces that much extra speed.
My self i only use it when need the extra speed, only with some games and wmv video files. I think it definitely lowers battery life and i would have worries about overclocking all the time and the long term effect it has on the processor (not so important if you only keep your wizard for a year and then change with a new contract - what i do new device once a year!) I found good speed gains with the registry wizard - http://forum.xda-developers.com/viewtopic.php?t=39725
have not found overclocking produces that much extra speed.
Mine is also set at 264 24/7. Battery still lasts me all day. Been doing it since the oc program was found which I guess has been a couple of months.
Don't forget, you're wizard is only overclocked when it is active (i.e. not in standby mode). When your wizard goes into standby, it automatically goes back to the default 180mhz. Only when you bring it out of standby does it overclock again (assuming you're running it with smartskey with the option of overclocking on wakeup)
i'm using smartkey to constantly run at 264mhz...i have been doing this for a month now...like i said there is not really any problems with the batt unless you run it down totally...there was a post about this in the overclocking thread...the process is set low so that the phone will have a longer batt life...this was also stated in the overclocking thread...theoretically there is more wear if you overclock it since you are making the processor work harder, so use it at your own risk! if you want to be on the safe side then use smartkey and the overclocking prog in the same directory...then use total commander's note pad (while the ini file is highlighted) and change the value lower when you don't want it to constantly run at 264mhz or whatever speed you want to overclock or underclock at...just use it when needed, but i overclock mine constant 264mhz with great results combined with tweaks2k2, registry wizard, and of course the tmobile custom rom ...internet is a blast...just wish i could get it to run like the IE in a pc
anyways hope this helps out a bit further...
activesync
your activesync will hang allot if you overclock, I have noticed this.
DOnt know why.
For some reason i stumbled onto something, im sure its been mentioned b4 but when running Wisbar advance with a Windows vista skin done by xcillion, i am able to overclock my cingular 8125 to 288mhz at a stable rate with no problems at all, can run warcraft 2 full speed with over 50 units battling it out on screen, almost doubles browsing speed and i can run all the emulators including SNES at full speed with sound. when i dont have wisbar advance running i cant go past 240mhz clocking speed. I wonder has anyone else noticed this or gone higher than 288 without a freeze. Also, my battery life runs steady for a full day of browsing the internet talking on mobile messanger and listening to music at half volume for a full day.
Re: DOnt know why.
xSoNiCcRaCkErSx said:
For some reason i stumbled onto something, im sure its been mentioned b4 but when running Wisbar advance with a Windows vista skin done by xcillion, i am able to overclock my cingular 8125 to 288mhz at a stable rate with no problems at all, can run warcraft 2 full speed with over 50 units battling it out on screen, almost doubles browsing speed and i can run all the emulators including SNES at full speed with sound. when i dont have wisbar advance running i cant go past 240mhz clocking speed. I wonder has anyone else noticed this or gone higher than 288 without a freeze. Also, my battery life runs steady for a full day of browsing the internet talking on mobile messanger and listening to music at half volume for a full day.
Click to expand...
Click to collapse
hey sonic, where did you get your copy of warcraft 2 for windows mobile ?
I've never heard of warcraft for Windows mobile, how does it run on a 240 MHz overclock?
I got it from the Wargus engine. i can email you the files if need be, i dont want to jeprodize this sites reputation. The game last time i checked was free though...
Actually I'm not sure if it's the overclocking issue or not but ...
For couple of weeks now my Wizard's red led is on all the time, not like it is when your battery is very low but about half of this brightness. I'm not really worried about that, it doesn't change much but it may be connected with overclocking (it was 240 for about a month).
Another thing - once I had sth like 110% speed of every tone played, either a phone call or an incoming message.
It doesn't really matter to me since it's still working fine but it may mean that overclocking isn't that safe as we might think.
TroLoo
PocketHack Master V4 is now out with Tytn support. Be warned that at it's highest setting of 440mhz i had to HARD reset my device.... Must start at a lower speed next time and work my way up!
I'm still in the middle of restoring!!
johnk1973 said:
PocketHack Master V4 is now out with Tytn support. Be warned that at it's highest setting of 440mhz i had to HARD reset my device.... Must start at a lower speed next time and work my way up!
I'm still in the middle of restoring!!
Click to expand...
Click to collapse
have you found a need to overclock the device then...., might works fine for what I use it for
Thanks for pointing this out... I updated the FAQs on the wiki.
It automatically scales the processor voltage onSamsung S3C2440 processors
so does this clock it over 440mhz, because an extra 40mhz doesnt really sound worthy of paying for software, especially when the TyTN is pretty snappy?
So... do you need to stick it in a fridge or anything afterwards?
I think the main idea of using the program is to allow a "super battery saving" mode, by underclocking the device it will use less power....obviously impacting performance-wise but still!
The main reason I wanted PHM was to help render web pages faster. My tytn downloads quicker than the works PC on normal broadband but the pages take longer to 'finalize' the page (i.e.. you can scroll down a page and it's still inserting images). This is a CPU speed issue.
I have finally got to play with PHM and it still needs more work! Just doing a test at tytn's default 400Mhz crashes my phone, never mind higher! I never got much higher than 300Mhz, how strange!!
Hack Master V4 not ready for primetime!
As others have noted, don't waste your time on Hack Master v4. I played with it, only to find it causes crashes, no matter what you do. Also, I found that it caused an incomplete Hard Reset. So, I had to do the manual hard reset twice, to get TYTN working again correctly.
Also, the Wiki should be updated to show there are still problems for anyone wanting to OC the TYTN.
I stupidly tried PHM too, and have just suffered a partial hard reset. Here goes the long and frustrating reinstall...
grayhaze said:
I stupidly tried PHM too, and have just suffered a partial hard reset. Here goes the long and frustrating reinstall...
Click to expand...
Click to collapse
aren't we allowed to take these people to court? False advertising and damaging my equipment? They must have had enough emails by now and yet the same program is still there advertising the same things, very poor...
We should probably change the title of this thread to say "OVERCLOCKING: DON'T EVEN THINK ABOUT IT..." :idea:
johnk1973 said:
aren't we allowed to take these people to court? False advertising and damaging my equipment? They must have had enough emails by now and yet the same program is still there advertising the same things, very poor...
Click to expand...
Click to collapse
They can get away with it through the fact that they tell you to backup your device before you use the program. Coming from an XDAII where PHM worked perfectly though, I stupidly assumed that the quality of the product would be at least the same or even better after numerous updates.
I'm pretty much set up again now, but I'll certainly be looking at purchasing a backup solution before I put my trust in something like that again.
Don't think about it, even with a backup... While trying to overclock my TyTN smoothly, it's now on the way to service (no more booting at all...)
Gx
Oops ... you should have read this thread before even trying overcloking ...
sorry for ya mate !!!
I find my Jasjam (Hermes) runs very fast and I don't see the point in over clocking it when it runs fast enough normally.
Have XCPU Scaler, in autoscale mode working up to 500mhz, on a cingular 8525 (HERM100), no resets, no problem.
>Edit
Also scaled down to 200mhz on the low side for super battery saver.
?Glitch
?Glitch that is amazing not just the speed but the fact that their is no problems!!!!!!!!
?Glitch said:
Have XCPU Scaler, in autoscale mode working up to 500mhz, on a cingular 8525 (HERM100), no resets, no problem.
>Edit
Also scaled down to 200mhz on the low side for super battery saver.
?Glitch
Click to expand...
Click to collapse
you'll be needing one of those new spangly batteries with extra life to cope with a processor increase like that.
@?Glitch: Can you post some screenshots?
That's awesome .. Has anyone else tried this program out? How's it working for you?
I'm using the XCPUScalar with its CPU load based setting.
Normally I set the speed to only 200MHz while on heavy load it speed-up back to 400MHz and 500NHz on very high load.
On day-to-day use it looks like extending the battery life (working on lower clock rate) whiles much quicker route calculation when using the navigation program.
Currently I faced now problem.
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...
I'm getting about 1-2 days battery life after rooting.
I've removed Phone.apk and the other one (can't remember what it's called).
I think the short battery life is because certain apps are trying to download in the background, even when WiFi is disconnected, I can't see what else it could be:
- market
- various rss readers
- widgets
- more?
I think this is happening even when these programs are not shown in a basic task manager (the task manager resulting from the n button long press rework).
I should add, how much battery life do you get after rooting?
About 1 month but I charged it only twice
I read that some had battery drain after a month I'm still waiting to figure it out :-$
NookTouch 1.0 rooted with touchnooter 1.6. 24
Sent from my GT-P1010
What do you have in Nook Color Tools > Settings > Battery use ?
thanks mdall,
it's 48% wifi (not worried about that)
43% phone idle
& 8% display, system 2%
I have 85% for Cell standby, is this normal?
why do I have something like that on a non-phone device?
MOD: I've found a thread about it: http://forum.xda-developers.com/showthread.php?t=1189047
glezmen said:
I have 85% for Cell standby, is this normal?
Click to expand...
Click to collapse
If you keep the NST on for long periods of time without reading, then the answer is yes. Otherwise, I couldn't tell you.
glezmen said:
why do I have something like that on a non-phone device?
Click to expand...
Click to collapse
Well, there might development considerations for not excluding the culprit files (mainly: Phone.apk and TelephonyProvider.apk) but, then again, after rooting they can be removed with no apparent damage to the device so...
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
Just a note, those files don't actually affect battery life, they only affect the way battery life is displayed in battery statistics.
Disabling phone apps for good: How?
GabrialDestruir said:
Just a note, those files don't actually affect battery life, they only affect the way battery life is displayed in battery statistics.
Click to expand...
Click to collapse
Sweet...
So, how we disable those apps for good, so they wont't suck the battery dry??
Awaiting your kind reply,
Sebástian,
If I understood right what Gabrial said, and it was commented before in nook str forum, those apps won't suck your battery, because there is no phone to get in touch with, and it won't add to wifi download - even though I notice that wifi traffic is heavier that from my phone, but I have much experience with android, so I can't really tell.
Disabling phone apps for good: How?
apeine said:
If I understood right what Gabrial said, and it was commented before in nook str forum, those apps won't suck your battery, because there is no phone to get in touch with
Click to expand...
Click to collapse
My point is, dear sir: if it's running, it's using CPU and/or memory... and certainly battery.
sarmasm said:
My point is, dear sir: if it's running, it's using CPU and/or memory... and certainly battery.
Click to expand...
Click to collapse
And if it isn't there, other parts of the system are wasting CPU cycles trying to find and start it. Been there before, done that, learned that removing things without having good reasons to do it can lead to wasting a lot of time.
Looking at how much the Nook stays on each cpu state, I have found some strange issues.
It seems, that without modifying anything, it stays a whole +1 minute at 800mhz after the last touch to the screen, and then comes back to 300mhz and stays there, this is not desirable at all, even for just reading.
Can someone install any program as cpuspy to check if it is a common issue?
Here is a link to the market, its free:
https://market.android.com/details?id=com.bvalosek.cpuspy&hl=es
Do something, open an app, close it, and w8 3 minutes, if the cpuspy reports +1 or more minutes of 800mhz state, then the issue is there.
If installing Setcpu, and looking into the gobernors, they are not found, all the options are -1.
When I change the max cpu state to 300mhz (so max = min) the cpu comes down to 300mhz but dosnt stay there, it jumps back to 800mhz but inmediatly comes back to 800mhz when not in use.
I need someone to check what I'm saying to look further into this issue.
Setcpu is free for xda members, http://forum.xda-developers.com/showthread.php?t=505419
Allthough if you can buy it, its a grate app, and devs need donations.
eded333 said:
If installing Setcpu, and looking into the gobernors, they are not found, all the options are -1.
When I change the max cpu state to 300mhz (so max = min) the cpu comes down to 300mhz but dosnt stay there, it jumps back to 800mhz but inmediatly comes back to 800mhz when not in use.
Click to expand...
Click to collapse
The NST has its own power management service, so tools like that would most likely not work as expected and could in fact be dangerous to your NST. (overheating)
ros87 said:
The NST has its own power management service, so tools like that would most likely not work as expected and could in fact be dangerous to your NST. (overheating)
Click to expand...
Click to collapse
That makes sense, and is what I thought about the gobernors.
The problem still resides on the time the cpu stays at max state after it has stopped being used.
I'm taking a look at sys/devices/system/cpu/cpu0/cpufreq/ at the moment, strangely under cpuidle I found a folder named conservative..... could that have been introduced by SetCpu, or am I talking bull**** ?
It seems the kernel supports the tipical gobernors: conservative, ondemand, userspace, performance, can't find any trace of the one the extra one that uses the Nook Touch, so it must be somewhere else.....
---------- Post added at 07:13 PM ---------- Previous post was at 06:44 PM ----------
ros87 could you please, if you know, show me where to look for this service, I found strange things under sys/devices/system/cpu/cpu0/ on idle, for example 8 states and a conservative folder, which totally shouldnt be there, and on frequency I found the normall gobernors.
I'd really like to know how the Nook touch administrates its power states .
eded333 said:
ros87 could you please, if you know, show me where to look for this service, I found strange things under sys/devices/system/cpu/cpu0/ on idle, for example 8 states and a conservative folder, which totally shouldnt be there, and on frequency I found the normall gobernors.
I'd really like to know how the Nook touch administrates its power states .
Click to expand...
Click to collapse
Sorry, I don't have any in-depth knowledge about this.
And maybe I misused the term "service", I wasn't really referring to a daemon.
There are some hints in init.rc
Code:
# Enabling sleep in idle path
write /sys/power/sleep_while_idle 1
# Enabling OFF mode
write /sys/power/enable_off_mode 1
# Enabling Voltage OFF in idle path
write /sys/power/voltage_off_while_idle 1
# Enablig DVFS with conservative governor
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor conservative
# Enabling SmartReflex for Zoom3 OMAP3630
write /sys/power/sr_vdd1_autocomp 0
write /sys/power/sr_vdd2_autocomp 0
I guess you have to grep your way trough the sources to find out what B&N modified for this particular platform.
Here's some platform documentation from TI (Gingerbread related, but still)
http://processors.wiki.ti.com/index...t-2.1_PortingGuides#DVFS_-_CPU_Freq_framework
Thanks ros87, I'll look into it.
Thanks - the link to the processor wiki is very helpful for a newbie like me to learn how these things work. I never understood that the userspace governor had to be set before the cpu frequency could be set.
Uhh, I cannot post this in development as I am still a newby :-(
However:
Hello,
I came from Symbian (Nokia C7-00) and liked the phone very much. Everything worked the way it should. (I was especially interested in office functionality.)
Now I bought a Galaxy Note and I really love the hardware.
But I discovered that it uses much energy and it doesn't like to sleep as often as it could. (I already returned to Android GB, which gives a better experience, but there still is room for improvement.)
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
corcovo said:
Uhh, I cannot post this in development as I am still a newby :-(
However:
Click to expand...
Click to collapse
Which is handy, because this thread has nothing to do with development and thus saved you from some abuse!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
But I already know how to click the "thanks" button
corcovo said:
But I already know how to click the "thanks" button
Click to expand...
Click to collapse
Doesn't matter.
Development, if you did not create IT, then it does not belong in development. Remember that. Otherwise you will get flamed.
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones. Android acts like a computer and, if you keep a computer running Crysis 2 for example, it would burn more power than a computer just playing some music off of iTunes.
In terms of improving your battery, check your brightness. You can download widgets to adjust the brightness right from the home screens. I use these to set my brightness to its lowest whilst at home (perfectly adequate for night and indoor use away from sunlight) and turn it onto automatic when I go outside. This has saved my a bunch of battery.
If you are running a stock Samsung ROM, turn on power saving mode. I always leave it on and, frankly, I have no idea as to what it actually does. I haven't noticed a performance drop in the slightest, but if it saves a bit of battery it is worth it. Also, you could try Juice Defender or some other battery saving apps which work for some people - others not.
Finally, ensure you haven't left GPS, Bluetooth or WiFi on when not needed. Try downloading CPU Spy to check your phone deep sleeps, yet mine even without it ever deep sleeping gets around 16 hours of battery life which is still the best I have ever gotten on a smart phone. Bettery Battery Stats can show you wake-locks (apps that are keeping your phone active) also.
Brad387 said:
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones.
Click to expand...
Click to collapse
I see. Well it might be a nice feature if one could add an "now be a cell phone"-option for energy enhancement, which means: if screen if off, sleep.
c.
corcovo said:
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
Click to expand...
Click to collapse
There are some legitimate needs for keeping the CPU from sleeping for a short period of time - such as finishing a sync operation (otherwise, the radio power spent beginning the sync is wasted). Unfortunately, some poorly written applications (Facebook for example) abuse the wakelock mechanisms and hold wakelocks when it is not justified.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
Click to expand...
Click to collapse
This is not something I have ever encountered myself. "push" relies on the server to trigger something - in airplane mode, this trigger can't happen.
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
Click to expand...
Click to collapse
Android is well optimized for cell phones - However, it assumes that third-party applications follow Google's recommendations for power management. Unfortunately, many of them do not. The number of IM applications which choose to use their own proprietary and poorly optimized network protocols (such as Skype, it's atrocious) as opposed to Google C2DM (optimized and efficient) is astonishing.
An interesting note was that I believe much of the focus at Google I/O was on reminding app developers that they need to play nice with the system and other apps.
There are some cases where there are device-specific nonoptimalities. Compared to most Nexus devices, Exynos devices have an absurdly long time to resume from wake (1000 milliseconds), and during that resume cycle CPU frequency is locked to 800 MHz and cpuidle is disabled. This is one of the #1 causes of power drain on our device. This is also exclusively a Samsung kernel/hardware architecture problem that does not affect the Nexus S (similar CPU, but completely different modem interface) or the Galaxy Nexus (different CPU/modem interface).
In the case of our device, the modem is hung off of the CPU on a USB bus - this makes for very long resume times.
Here are obvious reasons the CPU should occasionally turn on when the screen is off:
1) MP3 playback in the background
2) Handling of background syncs - e.g. when an email or Google Talk IM comes in, wake the CPU, handle it, and pop a notification sound, then go back to sleep. Normally, this means the CPU sleeps while waiting for an interrupt from the WLAN chipset or the cellular radio. Unfortunately, some apps drive incoming data to the device far too frequently. (See my above rant about Skype's network protocols being crap compared to Google's C2DM protocol.)
3) Handling of scheduled wakeups (alarms, calendar events, etc) - these are rare and almost never consume power
Most power drain is from item 2, with third-party apps frequently behaving extremely poorly compared to Google's own application suite and sync protocols.
Now this an extensive answer which is very informative and helpful for me since insights are always soothing. Love it. Thanks!
not much to add after Entropy, but if you feel the need to get some control over battery usage you could try betterbatterystats app (and the thread) to identify battery eaters, besides that, there are few apps to check what is going on with your system when it sleeps:
- CPU Spy to show cpu states time
- Autorun Manager or Autostarts to disable triggers causing apps like FB to run without reason (those which you will find with betterbatterystats)
- Battery Monitor Widget, to check battery current consumption (mA) - this app is generally not recommended, because Note's hardware does not report the actual current, so the readings are highly estimated and because when poorly configured it can drain your battery faster, BUT otoh with refresh rate set at 5 minutes or more, it can give you some approximate orientation on how much battery you lose (better than counting %/hour by yourself) at negligible battery usage
- also, if you feel the need to disable net and sync during night, you could automate it using "lama", which is free, and in my experience does not eat much battery by itself
- and last but not least, avoid taskillers, those apps may have adverse effect, i.e. self restarting apps (by the triggers mentioned above), will get killed then restarted and so on and so on, leading to much higher battery drain