Related
So, after diggin' for long time in registry on Pocket PC 2002 ROMs I've found nice feature - HKLM\System\CurrentControlSet\Control\Power\
(may vary cause this is from 2003 ROM, for now I have but was like this and works on 2002), has value WakeUpPowerOff = 180 (by default).
This value (in seconds) determines, how long device will be on after:
1. power on by "power" button (and no other activity - no taps, no any hardware buttons pressing) - it userful for example to see "what's on
today", time, etc...
2. power on by incoming event like SMS or calendar one.
And after you touch screen\ other button - then as I found starts another, "original" timer, defined in Start->Settings->System->Power.
I've set above WakeUp parameter to WakeUpPowerOff = 12 (smallest that works really at mine device) and what I got? This:
When I need to look into today's or time or missed calls etc - I just press power look at screen and devices turns iself off byself. Not great effort but - heh - longer live for power button
But this is more important: When incomes SMS (I have gate from internet inbox to sms so have a lot of smses) - devices comes on only for 12 secs - for day it increases significantly battery life. (aha - 180sec and 12sec - differs!) (etc...). So we can set auto Off timer for 1 minute and work in normal mode (when we tap or read something, smaller is not so much siutable), but with this WakeUp timer also when we don't use device we get very small time to byself on\off-ing and longer battery life.
But after appearing 2003 in my wallaby and then after bying himalaya I have changed this parameter with no effect.
Now I find solution!
We need to change one more parameter in that registry subdirectory named:
DisableGwesPowerOff=1 by defalut. Simpy set it to 0.
And now on my XDA II (and on XDA I with 2003) this hacks works.
I think this will be userful for our XDA community. Thanks for paying attention for this text.
Hey, that is a very, very cool hack! I have always been annoyed when my XDA2 is in my pocket and I receive an SMS when I can't reply. During the 2 minutes before it switches itself off I find that the screen gets pressed a lot in my pocket with sometimes disastrous results.
This hack seems to have no side-effects at all. The XDA2 stays switched on in the cradle and changing the Power-off-on-battery setting doesn't reset this auto-off timer.
I dare to suggest even that it is perfect! Thank you very much nugged.
Thank you realy love this one :idea:
Works fine with 5sec off on XDAII.
goodluck
2 SiliconS: That's some kind of pleasure to share with info and to help.
2 eme: 5 sec? hmm... Ah! I think I have bigger lag cause I have setted up password protection and maybe it needs some time to initialize after on/before off... You haven't password protection on?
Anyway - it's works.
I've just had a thought: does this hack affect the alarms and appointment notifications? Does the machine turn itself off after 12 seconds and stop the alarm working? That might be a problem for some people if so. I can't test at the moment - my wife is asleep
Edit:
Just tested, quietly . It does affect the alarm. I set a repeating alarm. The machine turned on, sounded the alarm once and then switched off. When I turned it on again a few seconds later it sounded a repeat.
I think this hack is excellent if you don't use your XDA2 for alarms or notifications. Otherwise it might cause problems. :?
@nugged:
every PocketPC turns itself automatically on at midnight, to perform some magic regarding alarms etc. It is a known problem that sometimes it turns off too soon again, before having finished its work. There are even programs to make this time-out longer. Question: does you hack also affect this time-out, or is it something completely unrelated?
Cheers
Daniel
2 tadzio: Mine never do this. What "reorganization"? Mine works fine, don't miss any appointments and haven't midnight magic power-ons ...
2 SiliconS: Yes, so that's maybe who need to have long alarms install additional soft and\or set up time longer, smth like 15 seconds.
As for me - yes, I use mine device lot of time so it often in mine hands and at my eyes so I don't need long alarms.
Lets explore info above (at 1st post) here more deeply maybe someone find solution for short WakeUpPowerOff time and working long alarms if needed.
Put down the pipe!!
What are you guys on, hacking the on time? I must be really confused... what about just using the power settings to turn of backlight after 10 seconds and power off if not used for 1 minute?
That's all I ever do and mine lasts easily through a weekend with a few hours of talk time and checking my e-mail at least 20 times.
2 wayandrs: That's your decision If you satisfied with that standard system - good . Anyway - it's not an order - it's just advice
Look - when you setup to run your backlight off after 10 seconds - try to work normally then .
nugged said:
2 tadzio: Mine never do this.
Click to expand...
Click to collapse
Yes, it does. You just don't see it because it's only a partial power-up: the display does not get switched on.
The OS needs to clean up appointments, and set alarms for the new day. Most of the time it succeeds, but sometimes the device powers off automatically before the OS could finish, resulting in alarms not going off. This is what tools like "Wakeup Tweak" are for - they just extend the time-out until the device powers down again.
Also, zendrui (the PocketZenPhone author) had a lot of... umm... fun with this feature when users configured PocketZenPhone to automatically switch modes at midnight. Ask him, I think he knows a lot more about this than he ever wanted to know.
Cheers
Daniel
I miss the old 2003 future and wish SMS dose not turn IMATE-II on..
hope some body listen there and give a soltion. it was built in before some bodies complain about it.
2 eme: 5 sec? hmm... Ah! I think I have bigger lag cause I have setted up password protection and maybe it needs some time to initialize after on/before off... You haven't password protection on?
Yes, no password protection.
Btw I managed to connect over BT to Linux machine and have acces to local net and web. That 's nothing ok. But managed also to use device cca
100m+ away form my BT acces point. Just put USB dongle on extended
cable and if possible outside of your room. My is on the attic.
Think, PC makes som interference to BT rx for sure. If anybody interesting
on this can write som more..
goodluck
2 eme: after setting this hack do you have some troubles with 'midnight self turning-ONs of device with turned off display and some reogranization' as tadzio has?
2 tadzio: so, device turning itself on withot turning on display? Sounds very interesting. Anyway - we can say so our devices stays on every time even turned off by the key, they only slowing down processor and turning off display and some hardware, cause they need to refresh SDRAM memory, to track and remember appointments to wake up at needed time, etc.
And, anyway, if this 'midnight ONs' are have place, if they are not turning on display - ppc works in another mode and I think this registry value is not related to them. But this - for me - is very strange information.
Please, Daniel, give detailed info/links, if you know this question good or don't bewilder other peoples, who read this topic.
nugged said:
2 eme: after setting this hack do you have some troubles with 'midnight self turning-ONs of device with turned off display and some reogranization' as tadzio has?
I do not have any appointments stored in my device.
Cant wait for Linux to run on it with graphical enviromet.
Than we can all forget this misterious M$ hacks.
Click to expand...
Click to collapse
eme said:
nugged said:
2 eme: after setting this hack do you have some troubles with 'midnight self turning-ONs of device with turned off display and some reogranization' as tadzio has?
Click to expand...
Click to collapse
Oh, I didn't mean to say that I have any problems. In fact, before I apply this hack I wanted to make sure that it will likely not cause any problems, that's why I asked if the author knows about any possible interaction between the midnight wakeup and his hack. I would suspect there is none, but I am not sure.
Cheers
Daniel
Click to expand...
Click to collapse
nugged said:
Please, Daniel, give detailed info/links, if you know this question good or don't bewilder other peoples, who read this topic.
Click to expand...
Click to collapse
Here is more information about this: http://www.mtekk.com.au/browse/page826.html
Cheers
Daniel
problem need help
Alrite i tried with a 12. It works well. As expected, but things happen when my phone rings, with a long rintone i have, it got cut off and then it went back to standby mode, making the call still ringing behind the background, after a while it was turn on again. It annoying when i cannot hear the first part of the ring. I end up not picking up importants calls... Anyway to help this desperado? ow i want to change back but its like the same...
First of all sorry for opening a new thread.....did search but didn´t find anything.....and I usually get annoyed myself by people asking question that have already been answered....
Problem: once in a while - and in no understandable pattern - my HD does not switch to standby after the set timeout (60s for me). Soft-reset does not solve the issue, but it disappears after a while (several times turning the display on/off). Have not changed/installed anything recently. First blamed it on S2U2.....uninstalled and problem seemed to be solved, but only until today - now it´s back in all its glory....
Already compared the - what I think - relevant registry values to my Diamond registry....no suspects there.
And no, there is no video-, audio-, or navigation program running in the background, as the problem manifests itself right after a restart/soft-reset....
Any ideas?
Thanks!!
mine does the same...I've just gotten used to it.
twisted-pixel said:
mine does the same...I've just gotten used to it.
Click to expand...
Click to collapse
Hmmm....I don´t want to get used to it, because whenever the device wakes up (missed call, reminder, alert etc.) the display stays on (altough dimmed) using up battery power....
Same problem here with my Diamond.
Any news or ideas on this?
Same for me, and it's a very big problem!
I've read in some of the other posts that it may have to do with the activation of auto-screen lock that is included in the ROM, but this isn't turnd on in my case!
I use my Blackstone professionally, which means I need as much battery power as possible on one charge! At the moment this problem makes the device last for about half a day during work!
If anyone has a fix, I would appreciate hearing about it
Getting a bit tired of this now so I'm tempted to try doing something about it, but I'm not sure what.
Non of the auto updates on my phone appear to work correctly and every time I want new data I have to manually tell each program to refresh/update etc. The manual procedures work no problem.
It's really annoying and wastes time having to do that when you should be able to open an app and have everything up to date.
Examples of what I mean are RSS feeds, Weather programs etc. . It puts me off using certain apps.
Is there any common reason for things that might cause this? I'm using an "Energy rom WWE" and am wondering if this might be rom related, although I have a vague recollection that this was also the case on the standard rom as I can remember having to manually update TF3 weather every time I used it, despite setting it to auto.
The phone always has a good GPRS/EDGE connection (my provider has no 3G ), although what I noticed a while ago was that my data connection would sometimes not work so I now have a scheduled automatic reboot every night.
I don't think the problem is related and I've not had connection problems since then, but regardless of this the auto updates never seem to work.
I'd LOVE all this stuff to be updating automatically as it is all set to do, but no idea why it doesn't do this.
Any ideas? Thanks!
Jim
Jim...1)does your data connection stay active in standby? Also 2) Check this registry setting HKLM\Software\HTC\HTCMSgEnhancement\Overlay Transition and see if the dword is 0 or 1. If 0 change to 1. It's a long shot that may not make much sense, but worth a try.
Thanks for the suggestion Sean - will check it out.
What exactly is that registry setting for?
And silly question maybe - but how can I tell if it's keeping the connection active if it's in standby?
Hmmm, been in the registry and I'm uncertain about this.
I don't actually seem to have this registry path:
HKLM\Software\HTC\HTCMSgEnhancement\Overlay Transition
Instead it has:
HKLM\Software\HTC\HTCMSgEnhance\
And none of the folders inside it seem to correspond with the overlay transition setting.
On the other hand there is a folder for:
HKLM\Software\HTC\Overlay Transition
This has three REG_DWORD settings (Interval/TotalFrame/WaitTime), and a default that has not been set to anything.
Hope that makes sense?
The registry setting is actually what controls how email fades in and out when you're swiping left or right between emails. Some chefs turn the overlay off which turns the fade transition off and makes swiping between emails almost instant. I use to turn it off, but each time I messed with that reg setting, my data connection would freeze up after or during an auto update. The only way to fix it was a softreset. When I would turn the transition back on, the problem would go away. Why? Not sure. That's why I said checking that reg may make zero sense, but it might be a factor.
To check if your data stays on in standby: establish a data connection and put your phone in standby (screenoff). After a bit, turn the screen back on and see if you still have a small "E" over the signal bars. You can also check the notification manager by pressing the top bar. See if a timer is going and how many hours, minutes and seconds it's been going. Or, and this may be better for testing purposes, go into sounds and notifications, set a sound for data connection established and a sound for data disconnected. Then start a data connection and you should hear the connected sound. Then put the phone in standby you will either hear the data disonnect sound or nothing at all. If you hear nothing at all, then your data is staying alive in stanby.
Edit: oops I didn't see your post above this one. See my response below.
Which Energy Rom version are you using? The second reg settting is what controls the speed of the fade in and out email transition. If you don't have the other setting then my second suggestion is not the problem. So see if your data stays active in stanby. If it disconnects then that would certainly be one good explanation for your apps not updating.
Thanks for such an informative reply - very helpful.
Yes, checked the data connection and it still shows edge there (ove 8 hours worth) so I guess that's not the issue.
The odd thing was that after posting this thread my RSS feeds actually did auto update today! BUT, my weather apps haven't, so it's a fluke I think.
Rom name is Energy ROM WWE 29/07/2009, Protocol 52.64.25.34U, Radio 1.14.25.24
i'm new of HTC TD2. my clock time changes all the time when it goes sleep mode and i press the power button and want to make a phone call, i need to adjust the time back. this is really annoying me coz it means i can't use this mobile as my alarm at all.
can anyone help me? I've already read the thread in the forum. but still can't find the solution. Thanks heaps.
Same thing is happening for me. This is the second Pure that I have owned and it seems like the time doesn't "keep up". Sometimes it will be only a few minutes behind; other times, hours. It has caused me to be late for work and I now have to set 2 alarms (I hate using standard alarm clocks and their annoying beeps and prefer to wake up to music that I have set on my phone, but I need a reliable back up). I really like the phone and hate to have to send it back for the second time for the same thing, but HTC seems to think that it is AT&T's network issues (funny how no one else or any other phones in my house have this problem). I'd be interested to know how many other people are experiencing the same problem.
Play with your sync time with network setting and see if that helps.
Thanks for the reply.
i think i've solved the problem. just unticked the automatically time zone changed. and it's running fine now.
Hello,
I recently noticed an issue with my wifi (stock 2.3.3), where an app that needs to update regularly didn't seem to be doing it when the screen was off. As the phone always sits on its dock when I'm at home, I "solved" the issue by making the screen never turn off.
However, today I decided to give SIPdroid another go, as I tested it when I first got my phone and it wasn't working properly. I found out why, the second I put the phone to my ear, the screen turns off and the sound cuts. If I take the phone away, I suddenly get all the audio high speed as it catches back up.
A bit of googling showed this to be a known issue, the wifi goes into power saving mode when the screen turns off - on SIPdroid there's an option to keep the screen off and it seems to work well, it just dims the screen instead. But that's still an unnecessary battery drain.
I had trouble finding any recent info on the issue (within the past 6 months), maybe I was just using the wrong keywords. So I thought I'd ask here. Does anyone know anything about this issue? Is it likely to be fixed in the next version of android if it ever comes to the desire HD? Maybe there's a fix out there already (preferably without rooting and/or installing custom rom, my phone is just right as it is now...).
Settings>Wireless & Networks>Wifi settings>Hit 'Menu'>Advanced>Wifi sleep policy>Never
That'll prevent the wifi turning off when the screen turns off.
Sent from my Desire HD using xda premium
I tried that before posting, it makes no difference whatsoever (besides, the sleep policy is either never or 15 minutes, this problem occurs the second the screen goes off).
If u re root: change radio... try anyone.
stock: mmm default reset to try. (i think)
No:
http://code.google.com/p/sipdroid/issues/detail?id=268
http://code.google.com/p/sipdroid/i...Status Priority Milestone Owner Summary Stars
Reading through the comments, it seems a more general android problem. A reset wouldn't fix it.
Also:
http://code.google.com/p/android/issues/detail?id=9781