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...
Had it at about 70% battery (around) last night, after 12 hours or so today, it refused to turn on.
I got it to turn on finally with a soft reset, and the battery showed 28%!!
I have no idea how it could have run down so fast, though it could have been something I left on (maybe wifi?).
I'm still surprised it would refuse to turn on at 28% though...
My Dopod 818 Pro is having this problem ever since I bought it. If I turn off the screen using the power switch or let it go to standby automatically, most of this time I can't turn it on again and have to do a soft reset.
I do not see a lot of Dopod users complaining about this problem so I am wondering if I have a faulty set. Other than this problem, everything else works fine.
i'm having the same problem. Do you think there will be a rom fix?
I just found an interesting observation regarding this sleep-to-death (STD) issue. If I left my Dopod overnight and got the STD problem the next day, the battery had drained considerably. It was fully charged the night before, but after 8 hours, the battery is only at 40 percent.
But since more than one person is having this issue, is it still a hardware problem?
This is not a hardware issue, its more like an unoptimised ROM issue. I suppose it will be fixed with an update in the future.
Leaving WiFi on does not matter because your device automatically goes into standby mode after a pre-defined time (3 minutes by default). In that case, even if you leave 10 apps running in the background, it won't make a difference for the aforementioned reason.
With the HTC Universal, what happened was that people would leave apps running in the background and once they are done using the device, they would just close the device thinking that it would shut off, but it wouldn't because the standy-mode was disabled by most people to get a snappier device. In such a situation, battery would drain rapidly overnight as the device hasn't gone into standby mode.
This situation will occur on the JAMin too IF there is no default standy-by mode set.
I have an HTC Universal (O2 XDA EXEC) and had the same thing happen to me two nights in a row. The battery was at 100% when i went to bed and i woke up and realized i was late as the alarm i had set didnt wake me up.
I had to soft reset the phone and the battery was down to 24% and then the alarm starting going off, a bit late though. I have had this phone for three days, and im not happy about this failing twice on me.
The only thing i have changed is running a coporate install (0506) so that o2 active wasnt on the phone.
Is there any fix for this??
Rom version: 1.13.82 WWE
Radio version: 1.04.02
Protocol version: 42.37.P8
ExtROM version 1.13.188 WWE
Go to Settings>System>Power and check the "switch off device after x minutes" option. By default it is 3 minutes, but i have set it to one minute as that serves my purpose. You will notice the drastic difference immediately .
It kind of sounds like an issue I've seen on my m600. It's a wm5 bug where activesync will try to connect all the time, randomly, even if your device is off. It can cause STD (sleep to death) and will. It's a simple fix. Just install the autosyncschedule.cpf and run it. It's a simple little .cab that will change some settings. Hope it helps
http://us.f1.yahoofs.com/bc/59d707c...amin/DisableSyncSchedule.cpf?bftVi9DBC7gsZI7r
If that link to my yahoo briefcase doesn't work, you can get this file at eten-users.net in the download section under /utilities/wm5. It solved all STD's with the eten and so far with my jamin. 8)
You can also fix the Active Sync bug manually.
To do so open ActiveSync on your WM5 device and tap on Menu>Add Server Source. Add any info to create a fake server sync. After that is complete go to Menu>Schedule and change the two dropdowns to "Manual" and tap "ok" at the top right.
Slept to death- I've sussed out why my device was doing this
I had an SD card from my i-mate Jam inserted, and after taking this out, the situation stopped happening. So if you've got an SD card in try running the device without for a while to see if that helps...
I have started this thread so that we can begin development of a program or a solution which will make the alarm system on our Wizards totally reliable.
As we know, a number of us have a problem whereby our devices fail to wake up when an alarm is due to go off, causing us to sleep in, and be late for work. This is an unacceptable situation. It is my intent to develop a program which will replace or augment the alarm system in WM5 so that we never again have to worry that our PPCs won't wake us up in the morning.
So far, we know there are a number of problems which might be contributing to the failed alarms:
1. Duplicate alarm/calendar notifications being entered into the notification database (same alarm shows repeatedly in the database)
- This can be resolved with CheckNotifications (http://www.scarybearsoftware.com/ppc_cn_overview.html) which will remove duplicate entries. It does not prevent the duplicates from being entered in the first place.
2. Alarm settings not saved to registry. It seems there may be a problem whereby registry changes are not being copied from RAM to Flash immediately, so if you Standby the device shortly after setting/changing the alarm, the alarm is not saved.
- This can be resolved by leaving the PPC for a minute or so before putting it in Standby after changing an alarm.
3. The big one. An alarm notification not turning the device on from standby. Why this affects some people and not others, we don't know. Some users report than when an alarm is due to go off, the device doesn't wake up. When the device is turned on manually, the alarm then sounds. This seems to happen randomly (with some alarms working OK, and others not) but doesn't affect everyone.
As yet, there is no known solution to this problem. This thread is intended to develop that solution.
My idea so far is to develop an application to replace the standard alarm on WM5. Our main objective is to create an event which will, reliably, and without fail, wake the device from standby. Once we have developed this program, a new alarm system can be tacked on to it, or the source code can be made available for developers of current alarm systems to integrate into their programs.
My PPC programming knowledge is limited, so the intention is for this project to be a joint effort, and I would urge anyone who has any useful input to contribute it on this thread.
I have noticed a few people mention that a program called Pocket WakeUp is a reliable alarm system, and doesn't suffer from the known bugs in the WM5 one.
http://www.pocketpcfreewares.com/en/index.php?soft=1299 (French version - see below for translated English version)
Unfortunately, there doesn't seem to have been an update of the program for quite a while, and also, the program is in French, so there aren't many people using it to see exactly how reliable it is.
I have done a quick-n-dirty translation of the program into English (I hope the author doesn't mind - no other changes were made), and attached it to this post. The interface isn't great, and it can be quite convoluted to use, but perhaps with an English version, more people can give it a try and see if it actually is reliable.
From what I can gather, Pocket WakeUp adds a notification when an alarm is due, which loads with WakeUpStart.exe program, which then loads the main program and sounds the alarm.
If this program is actually reliable, then I expect the author has found a way to make the device wake up from standby without fail, and the WakeUpStart.exe is the important part.
Please let me know if you use Pocket WakeUp and it works reliably, or randomly fails. Also, if the author of this program reads this board (or someone knows how to get in contact with him in English) I'd be interested to hear your views.
Good effort, I'll try the cab and report back over the next week.
Excellent endeavor! I have been using PPC devices for sevearl years and this has always been my biggest problem. Its hard to believe that MS has issued 3 new versions of their WM platform, all with this issue. This should be one on the first things you need to get right in these devices.
On the WM2002 and WM2003 platform I have good success with both PhoneAlam with AlarmToday for Pocketmax and also SuperAlert. But since moving on to the KJAM, the current versions of these programs just don't work.
I am not a developer, but will certainly help with testing etc. I'll try the FR prog now and will also post results.
Regards
Chris
The alarm not waking up on standby bug was fixed in the leaked 9100 test rom.. so whats the point in fixing a problem thats already been fixed
MilanoRex said:
The alarm not waking up on standby bug was fixed in the leaked 9100 test rom.. so whats the point in fixing a problem thats already been fixed
Click to expand...
Click to collapse
Says who? I'm using the latest i-mate ROM and the problem still persists.
I've been using Pocket WakeUp to check - *zap* - and so far it seems to work fine. Problem is, that's what I thought of the standard alarms until they failed a couple of times on me. Unfortunately, it also seems that my battery is draining faster now - but I would have to confirm that absolutely with a full copy of pocketbatteryanalyzer. I'm using my old phone in the mean time to make sure I do wake up.
For me, just not switching the device to standby is still the best bet. This also negates any issues related to point 2. Point 1 remains, and is actually a cause for old alarms going off when they shouldn't - and the cleanup thing is something I still do.
One thing that I think I should point out, though, is that the problem isn't just with a wake-up alarm. Pocket WakeUp may very well be a perfectly fine solution to that (no way to be 100% certain, I guess). The problem is that on at least one occasion, the device failed to wake up for a meeting event. Thankfully I was keeping an eye on the clock and I was leaving only 5 minutes late - and with a little speeding got there in time just fine. Point is, a wake-up alarm won't fix -those- :\
ZeBoxx, as far as I can see, Pocket WakeUp does use the notification system. Set an alarm with it, and check the notification queue. Delete the item from the notification queue and the alarm never sounds.
If we can work out how Pocket WakeUp reliably brings the device out of standby, then there's the possibility of writing a program to tack a wake up event in front of every calendar entry.
gah.. WakeUpStart? totally missed that.. I'll stfu now
ZeBoxx said:
gah.. WakeUpStart? totally missed that.. I'll stfu now
Click to expand...
Click to collapse
Yep! Thing is, if WakeUpStart can wake up the device without fail, then it will be simple enough to tack a similar wake up event a few secs before each alarm or appointment. Just need more people to test Pocket WakeUp to see if it's reliable - and hopefully we can get a hold of the author so he can tell us how he did it!
I upgrade to the new KJAM rom and now my alarm works.
texasez said:
I upgrade to the new KJAM rom and now my alarm works.
Click to expand...
Click to collapse
Yep, the whole problem with this bug is that it affects people randomly. Some people have the bug, some don't. Some people just get it one day for no apparent reason. There is no one solution to everyone's problems. Upgrading worked for you - good for you - doesn't mean it will work for everyone, and there's always the possibility that you never had the bug, and then you upgrade to the latest ROM and you start getting the bug!
thanks alot elyl !!
the translation of this program is the best news in months! I have been using this prog for 3 months without any problems. It seems very reliable to me. I dont understand French thoug, so it has been a little bit hard to use.
Before I started using the program, I had alot of problems with the alarm...
I tried Pocket wake up yesterday with mixed results. My KJaM seemed to be waking up for each event, but I was expecting it to continue to repeat the alarm beyond the few repeats that you get with the built in reminder. That did not happen though... I have set Pocket alarm wake up call take is set go in a few minutes, so will see if that works (guess that I am already awake though, so it won't be a big deal if it doesn't go off )
cbrow51 said:
I tried Pocket wake up yesterday with mixed results. My KJaM seemed to be waking up for each event, but I was expecting it to continue to repeat the alarm beyond the few repeats that you get with the built in reminder. That did not happen though... I have set Pocket alarm wake up call take is set go in a few minutes, so will see if that works (guess that I am already awake though, so it won't be a big deal if it doesn't go off )
Click to expand...
Click to collapse
Did you try setting a snooze time for about 5 mins? It will repeat then if you don't cancel it. Also, if you are using a short audio file for the alarm, make sure you increase the Minimum time of alarm to be X number of seconds - then it will repeat your alarm sound for however many seconds.
Hi Elyl
Yes, stumbled into that in the end. My French is very poor, so I had to guess at the options. Still, that seemed to work. I did notice that if you change the settings and then let the device go into standby, the alarm did not repeat...:-( I had to reset a new time, then it worked. I will now set a reoccuring alarm and not touch the settings and see how that goes... Will post back at end of day today..
Regards
chris
to be thorough...
In an effort to be thorough, I'll add my experience so that maybe a developer can read a solution. I use my kjam as a daily alarm. It has almost always worked when I leave the device plugged in and though the backlight is off but the actual system never goes into standby (everyday except one in six months). I have also experimented with using the alarm from a battery power source, but again, making sure that the device never goes into standby (this is a real battery drain).
I have used SPB time, Ptravel Alarm, and the built in alarm. SPB time is completely unreliable and has never worked (not even when set immediately after a more reliable alarm). Ptravel alarm has worked over the past week when I have tried it in both power/active and non-powerd/active, but I haven't tried it when the system was in standby. The Ptravel Alarm developer (Burroak Software) is a very very active developer and seems to really care about making his products work. The only flaw I have is the interface (i.e. stop button) is somewhat small to press first thing in the morning.
The built-in alarm is the one I have used most and seems to work well from a power source. Again, it does not work from standby reliably.
I know this is re-hashing the obvious for all of you, but thought it might give some more background. There simply must be something that is develop-able, which wakes up the device from standby (a turned off state) in time for the system to register and activate an alarm program or a few seconds before.
Could there be a way to extrapolate the program which activates the device or part of it to remotely activesync on a time schedule?
I will use the WakeUp program and report back.
wakealarm
just to stress the point, i will also use wakealarm and report at the first failures. If 100 users would do the same, we can improve our evaluation time by 100X. If even to a single user it will not work, i cannot fully trust the program for professional reasons or travelling.
Today, I have the test rom, SPB pocketplus, and yes ONCE the standard wm5 alarm didn't work on this configuration (over about 20 alarms and 200 calendar reminders that worked successfully). i use once in a while checknotifications and sktools to keep the notify queue clean - should i do it or not? sometimes, i am afraid that the alarm i loose are those that these two programs remove by believing they are unnecessary duplications....
i noticed that - in the infamous occasion of a missed alarm in the morning - i forgot the wifi connection on while the system was recharging beside my bed, and in the morning i had a pop-up message it complaining about the absence of network (instead of waking me up...).
Did i understand it correctly that - at midnight - the wizard does some internal procedures and wakes up? do i guess that - after waking up - it had to deal with the wifi network search instead of some alarm critical procedure? if it would be so, i would be happy - for example - to do the alarm critical procedures every few hours, so to be sure not to miss any.
Few hours later, finally at work, i saw the wizard rebooting by itself (second time ever, the first one was with the 1.6 ROM!) and, at reboot, started sending a list of alarms that i could not easily dismiss (since the system was in an early phase of reboot, no today screen available yet). i had to softreset a couple of times, after dismissal of the pending alarms it started to work correctly again.
I am reporting this in order to increase empirical understanding of the reasons why the standard alarm fails.
cbrow51 said:
Hi Elyl
Yes, stumbled into that in the end. My French is very poor
Click to expand...
Click to collapse
That's why I translated it! See the attachment.
Maybe its just me but I cannot see any link to a translation?
I can see the link to the cab file and I can see the link to the web site but no document?
Robin
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
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.