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...
Related
Ok, I guess quite a few of us are now usig the MDA/XDA II and have made our experiences.
I think it is time to start collecting the different bugs and "features", so that maybe the guys here can start fixing them. Maybe even O2/T-Mobile or HTC might startt doing something.
I'll start with my contributions:
1) SMS: The SMS-Application doesn't copy the "+" from the phone number when you select through the contacts application. See also: http://xda-developers.com/phpBB/viewtopic.php?t=3198
2) Bluetooth: Right now, this seems to work mostly as a marketing gag, considering the very limited profiles supported. The list of missing profiles keeps getting longer, including HFREE, PAN and others. In fact, it might make sense to collect the experiences of successful bonds in a dedicated thread.
3) BT-Headset: Even when it does work, the performance is shaky s you can see here: http://xda-developers.com/phpBB/viewtopic.php?t=3548
4) Phone On/Off: Turning the phone on/off seems to have gotten less user friendly than on the old MDA. Now you always need to get out your stylus, which can be quite a hassle when you are standing at the gate getting on a plane - with your suitcase in the other hand. See also: http://xda-developers.com/phpBB/viewtopic.php?t=3553
5) Google: Ok, this seems to be a problem on almost all WM2003 devices when I look at all the suff on the web about this issue. Still, it would be nice if it would work :wink:
6) Wireless Modem: Well, you would expect that they include the driver on the CD wouldn't you.
7. The MDA II closes open programms as soon as you open another large programm. Like a device with no memory. You cannot keep large programms open at the same time (e.g. Pocket Informant, PIE, Total Commander, aso.) , so they would be accessible more quickly if you choose them over an taskmanager.
Have a look at this, it would tell you something about this "closingbug":
http://xda-developers.com/forum/viewtopic.php?t=3477
Xda USB Modem driver
The USB modem driver *is* on the disk. There are no drivers for Serial, Bluetooth on Infrared.
ANyway, the infrared requires a public domain add-on to work...
Hi
It seems that my XDA II turns on spurious ( not often, but sometimes), which is not nice when having it in my pocket.
Does anyone has the same experince ?
Not sure if this could be considered a bug, but I have yet to be able to receive a video MMS sent by either a P800 or a Nokia 7650. Have successfully sent one to a 7650 though. On the UK O2 network.
sorry could not post a link !
but here is a hummdinger !
try the following hit the "Wireless" icon and note how long it takes for the dialogue box to pop up then hit the "Turn the radio off" hotspot.. You will notice much longer delays before it performs the task, the same happens when you have switched it off and then attempt to "Switch the radio on". A further prob is with the Volume control....do the following...call your voicemail "long" press the green phone key, now when the speakerphone is on , reduce the volume with the side "Slider" when it is at minimum try to increase it...it don’t work you can only use the stylus on the screen, if you allow, after reducing the volume, the dialog to disappear then try to increase the volume with the slider it works again, then if with the dialogue displayed you then end the call the dialogue will appear to be stuck on screen, and only disappear after about 10 secs...
Xant said:
Hi
It seems that my XDA II turns on spurious ( not often, but sometimes), which is not nice when having it in my pocket.
Does anyone has the same experince ?
Click to expand...
Click to collapse
same here. happens all the time and that´s not funny. Called O2 Tech Support and they said (of course) that i´m the first to report that problem. can´t really believe that.
it´s very annoying
Xant said:
It seems that my XDA II turns on spurious ( not often, but sometimes), which is not nice when having it in my pocket.
Click to expand...
Click to collapse
Have you turned on the homezone indicator? Everytime your mobile phone changes the cell, the homezone indicator updates itself, causing the XDA to turn on.
Christian
I also have the problem of not being able to recieve a video MMS from a 7650, I phoned o2 support on Tuesday and they said they would look into it and call me back on Wednesday, Well its now Saterday and i have not had a call back from them. Its good to see they sill use the same calender where next day means we dont have a answer so we wont bother to call you back
John
Buffer full / crash on transcriber/Notepad
8.) Buffer full / crash on transcriber/Notepad
Waring: Maybe you should do a backup before you try this....
How to cause:
- Go to Notpad
- Change to "Transcriber"-recognition
- Start to enter by writing normal letter/words: >> ok, works
- Try to "fill/paint the whole Screen" without (!) removing the pen from screen: After some seconds the Buffer will be full, constant Signal will apear if you touch the screen again
- Regognition won't work anymore
How to resolve the "full buffer" (seems to be the reason for me):
- Soft reset, okay
BUT:
- Xda2 behaves unstable afterwards.
You might get messages like this:
"camera.exe is not a valid apllication"
"media player is not a valid apllication"
So you need a "hard reset" with all the data gone.
(Maybe a sync is still possible - I didn't try this yet)
Okay, maybe not a Killer-Bug.
But now it's impossible to hand over the xda2 to my friends cause' they know how to "kill" my pda
Don't know is it's a xda2-specific bug or caused by OS.
Justaname
3 bugs?: text colour, letter recogniser, transciber
Great PDA - I've had an XDA for a few days and have been using it extenisvely (having had an iPAQH3850 for 2 years). The power of having a combined PDA, phone & camera/video is great. However, I've got a couple of problems. Anyone else had them or know how to fix them? (soft reset doesn't help- I haven't tried a hard reset yet):
1) Funny coloured text: some of the letters on the screen are brown rather than black. In particular the following letter combinations: 'in' and 'll'
2) 'Ghost' characters in 'Letter recogniser' mode. I write quickly using 'Letter recogniser' mode. Sometimes a grey outline of the character I've drawn stays for a fraction longer than I'd expect so that I end up writing the next character over the previous character. More noticeable in the 'numbers/special charcters' section on the right of the letter recogniser window.
3) Change of font/script when correcting words in 'Transciber' mode. The transciber mode is not bad at recognising my handwriting scrawl. However, if a word is interpreted incorrectly and I highlight the word and then rewrite the word, the new interprtation appears lowerdown on the line than the rest of the text (like MS Word's 'subscript')
chrissi75 said:
Xant said:
It seems that my XDA II turns on spurious ( not often, but sometimes), which is not nice when having it in my pocket.
Click to expand...
Click to collapse
Have you turned on the homezone indicator? Everytime your mobile phone changes the cell, the homezone indicator updates itself, causing the XDA to turn on.
Christian
Click to expand...
Click to collapse
yay, that was it. thx a lot
Andy said:
chrissi75 said:
Xant said:
It seems that my XDA II turns on spurious ( not often, but sometimes), which is not nice when having it in my pocket.
Click to expand...
Click to collapse
Have you turned on the homezone indicator? Everytime your mobile phone changes the cell, the homezone indicator updates itself, causing the XDA to turn on.
Christian
Click to expand...
Click to collapse
yay, that was it. thx a lot
Click to expand...
Click to collapse
But it is still a bug and I hope they intend to fix it, as it is rather interessting to know if I have contact to my homezone or not.
Hi
Got an other one. The alarm function seems not to work reliable. First I thought I missed the alarm due to much drinks the evening before but this morning I woke up before, but no alarm from my XDA. Instead when I turn the XDA on manually, it notified me about the alarm.
I also noticed it with a meeting.
I don't need an alarm clock I have to turn on manually...
btw... Is there some action to fix the reported bugs... either O2 or M$
new annoying bug
OK I just had a new REALLY annoying bug happen last night.
First i found that GPRS kept dialing up every time i diconnected it - i thought it must have been because ie was open in the background so i went and closed all runing programs but it still kept dialling up GPRS whenever i disconnected.
Then I received an sms but when i viewed it in Inbox, the parts of the stripy background that are usually white where really dark grey making it almost impossible to read anything on the screen... so i decided it was time for a soft reset.
but instead of soft resetting it did a hard reset so I've now got to re-install everything!!!!! :x
Pope,
The GPRS dial up could be to do with your network settings. In fact an awful lot of issues where the PDA switches on for no reason are probably that.
I've always found 'interesting' problems with ActiveSync where it switches on the PDA periodically (it's nothing specific to the XDA II as it also happened with the Fujitsu Loox and the Viewsonic V37). I always 'close' activesync (using vBar) when I'm not using it for this reason!
I recently spent ages with the XDA II trying to get it not to switch on after I'd set up a blue tooth link with my laptop. Had to change some of the network settings to stop it (but can't remember what) ... even 'resetting' the PDA hadn't fixed the problem.
re
Pope, I too have had a Hard Reset occur without knowingly doing it.
As far as I am aware I did not press the power on off button, when I soft reset, and it just did a hard reset.
I was having problems with an app that froze though, and just figured it was that.
Anyone else expereienced this ?
Cheers, Shire
I installed the upgrade at www.clubimate.com
Some noticeable changes after the upgrade:-
Fast switchoff of the phone, though u still have to use the stylus
The missed call red blink of the LED stays red (at least for the few minutes I checked) instead of turning back to green after a minute as in the past
The + in SMS is added when chosing from the contacts menu. I think this was a problem in the past
I had difficulty in installing SanDisk Wi-Fi software in the previous version. Went smoothly on the upgraded one.
membership??
I tried to sign up but I don't have the EMI whatever # ... any chance you can e-mail me this fix software?
[email protected]
My MDA Compact works beautifully with a BT GPS and TomTom 3....... except I have to keep touching the screen to keep it lit
Is there a way to stop this happening - actually is this normal or is mine broke !!??
You need to ensure the back light is not set to switch off after a certain amount of inactivity (yes, although tomtom is 'on' your pocket pc will not agree and will turn the back light off to save battery).
The solution really is to ensure your pocket pc is getting power.......
It's normal. I use Mbipocket (ebook reader), and even having the text scrolling up the screen won't stop the backlight turning off.
Dang !
How do you read your ebooks - by pressing the screen every few minutes ?
Something this obvious and they haven't fixed it !!
A simple tick box in the options menu isn't asking too much ??
So I guess the only way around it is to go into the backlight options and set it too stay on for 1 hour before turning off ...... wait, the maximum is only 5 minutes ..... I love Microsoft
????
very simple, watch under backlight, there you can adjust your settings...
the best is to buy a chargecable..and plug it in..
you mda will now charge , and navigate at the same time...
8)
have fun
Aitch said:
Dang !
How do you read your ebooks - by pressing the screen every few minutes ?
Something this obvious and they haven't fixed it !!
A simple tick box in the options menu isn't asking too much ??
So I guess the only way around it is to go into the backlight options and set it too stay on for 1 hour before turning off ...... wait, the maximum is only 5 minutes ..... I love Microsoft
Click to expand...
Click to collapse
By tapping the screen every few minutes. Which as most of my ebook reading in dduring a 30 minute train journey to and from work, isn't much of a problem. And I've just realised that unticking the "turn off backlight" box means that it doesn't get turned off.
use TomTom4, the screen doesn't go off with that version
also BT is automaticly activated when starting TT4 when it was disabled in the systemtray.
TT4 r0x0r
Sweet !
TomTom 5 will be released in May - hopefully it will have those features included
tCC said:
use TomTom4, the screen doesn't go off with that version
also BT is automaticly activated when starting TT4 when it was disabled in the systemtray.
TT4 r0x0r
Click to expand...
Click to collapse
Strange, TomTom upgrades from TT3 to TT5 (in may) and skipped 4...
You are really sure you have a TT4 ???
Did i miss something?
Thomas
Hell Yeah !!
TT 5 is coming for sure !
Checkout it out - http://www.pocketgps.co.uk/modules.php?name=Forums&file=viewtopic&t=17753
Hi all,
I'm having my Universal for the last month, I suffered alot from the low speed of it, I read many threads in the forums, and tried many settings by myself and ended up with the following settings to be made to make your Universal works fast:
1) Un-install the anti virus program.
2) Diactivate the error reporting.
3) Set the power settings as follows: "Start / Settings / System / Power / Advance / Un-check turn off device if not used for ".
4) To avoid ending up with a flat battery do the following settings: " Start / Settings / System / Power / Tap backlight at the bottom of the screen / Check "Turn off backlight if device is not used for 30 seconds."
5)In the same menu "backlight" tap brightness and adjust the brightness to the minimum level .
6) If your device is I-mate tap Settings / Today / use any other theme other than I-mate grass , and I-mate swoosh because their size is too big, if you use any other theme you will save more than 1 MB of memory.
Please note that the change No. (3) is the only way to avoid the freeze happens to the universal in each time you press the light button to turn on your device, if you keep your device always on you will not only avoid this freezing, but also you will allow the voice dial to work properly even if your device is closed and the screen is inside because the device will never be turned off.
In addition to the above changes, you have to get a software which really close the applications such as spb pocket plus 3.0.4 which is compatible with WM 5 , or GSPMagic., or MagicButton , then you can try your device to see the difference.
Please note that if you use spb pocket plus do not include any SD card on your today screen otherwize it will slow down your device again.., and it's much better to reduce your program shortcuts to the minimum, there is no need either for the battery indicatior on the today screen since we have a battery indicator by default on the bottom right side of the screen, and battery line "spb" on the top of the screen.
I made the above changes and my device works fine.
Try it, I hope you all will find a lot of improvement.
Need feedback on this issue please.
Regards,
Hello all,
Will you please give me a feed back after making the suggested changes?
Regards,
Hey,,
Good advice. I've just made the power and screen changes and will see how it goes. I'm hoping that the battery life won't be worse and that I don't get to anoyed having to tap a key to swith the screen back on...
The important thing is that the bluetooth headset carries on working..It's a real bugger when it rings and I can't pick it up on the headset.. Do you think they tested this thing with headsets?
I also assume that when you switch the device off using the button, it never really switches off, just pretends to... I was thinking that there are times, on a long flight, where you'd like it to be really switched off to reserve battery. What think you?
Don't worry about the battery, battery life will not be worse, but as my experience with PDAs, "More than one year experience now" I can tell you that you have to charge your PDA at least once a day "every night".
Regarding the Blue tooth Headset issue, I'm using Jabra BT 800 and it's working like a charm even with voice dial, it never misses a voice tag.
Regarding the Turn off issue, PDAs are not designed to be completely switched off, you can only swich the power off "Pretending to be completely switched off" because if you turn it completely off by removing the battery for example you will lose all data on your PDA.
Still waiting for feedback.
Regards,
I have already turned off error reporting and turned off receive all incoming beams. I am a bit confuesd by Point 3 as my XDA Exec does not freeze at all when i press the backlight button- maybe it is a jasjar issue, like the antivirus? Have you noticedf any difference in battery life by just swtiching the screen off instead of putting the phone into standby?
Fin
Fin,
If you have no freezing issue when you press the light button to turn the phone on, and you don't have any problem in voice dialing while the phone is on standby mode there is no need to set the phone to never switch off.
I'm using Jasjar and I'm facing the above two problems, and I can't avoid them without making these settings.
Regarding the battery issue, there is no much difference between the two modes.
Regards,
carefuly folks, this is not entirely accurate:
- what freeze? Not heard many complaints on this matter
- what voice command issue; mine works perfectly WITH the BT headset fix of course
- battery life WILL & does reduce significantly with "always on"
- spb PP 3.0.4 is latest version, and there are a few alternatives that are just as good. Principle of task closing is right tho.
- There are several other truly useful hacks that would add a lot more value to this issue, incl GPRS always on, Buzz's BT headset fix, selecting working plugins only, etc etc - browse this forum from the start if u r just starting out
Correction
Not to play the devil :twisted: but WM5 devices do NOT hard-reset if (when?!) they run out of power, since internally all programs and data are now stored in Flash memory instead of DRAM.
As a side effect, you should also experience some improvement in battery life, since the smaller amount of DRAM on a WM5 device leads to a significant reduction in power consumption when the device is "doing nothing" - i.e. using very little CPU/Network, but standing by for incoming calls or user input.
craigiecraigie4,
- Regarding the freeze issue, I'm using Jasjar and it does freezes for 6-7 seconds whenever the power button or light button is pressed to switch the power on.
Also whenever I'm using the voice dial, this freezing causes the voice dial to delay and sometimes not responding.
But after setting the device to always on, I'm not experiencing any of those two problems.
- Battery life is not significantly reduced as you think, I tried both settings and any how I have to charge my phone once every day in both cases.
- spb pocket plus 3.0.4 is the latest version, and I did a typing mistake by saying it's 3.1.4..... sorry for that.
-Regarding the BT fix can you please post it here so that I can download it if possible... and can you please let me know what exactly does it fix?
Regards,
Khaled.
Re: Correction
dojohansen said:
Not to play the devil :twisted: but WM5 devices do NOT hard-reset if (when?!) they run out of power, since internally all programs and data are now stored in Flash memory instead of DRAM.
As a side effect, you should also experience some improvement in battery life, since the smaller amount of DRAM on a WM5 device leads to a significant reduction in power consumption when the device is "doing nothing" - i.e. using very little CPU/Network, but standing by for incoming calls or user input.
Click to expand...
Click to collapse
dojohansen,
Thanks for the valuble information, I thought it's the same like PDA2K which I was using till the last month.
I'm so happy to know this information.
Regards,
khaledelfeki said:
Still waiting for feedback.
Regards,
Click to expand...
Click to collapse
I hardly have problems with memory or speed.
I installed Listpro, Ewallet, some GPS software and NR de Luxe .
I use Excel, Word, and IE explorer frequently.
I use Agile in stead of MSN, but I never have problems with performance.
I do not often fully close ( settings/system/memory) programs used.
Can you give an example on which moments your really run into speed/memory problems?
Huib
herpi said:
khaledelfeki said:
Still waiting for feedback.
Regards,
Click to expand...
Click to collapse
I hardly have problems with memory or speed.
I installed Listpro, Ewallet, some GPS software and NR de Luxe .
I use Excel, Word, and IE explorer frequently.
I use Agile in stead of MSN, but I never have problems with performance.
I do not often fully close ( settings/system/memory) programs used.
Can you give an example on which moments your really run into speed/memory problems?
Huib
Click to expand...
Click to collapse
Huib,
I'm using Jasjar, I don't know the differences between Jasjar and the other universal devices, and I'm having problem always when I open the device cover and pressing the power "light" button to turn the device on, it freezes for 6-7 seconds before I can use it for any purpose.
This also affects the voice dialling when the device is on standby mode as it freezes for long time until it recognizes that there is a voice dial and them gives me the beep to start voice dialling and sometimes it does not even gives me the beep.
May be there are some differences between Jasjar and the other Universal devices but these are the problems which I'm facing and this is how I resolved it.
Regards,
khaledelfeki said:
Huib,
I'm using Jasjar, I don't know the differences between Jasjar and the other universal devices, and I'm having problem always when I open the device cover and pressing the power "light" button to turn the device on, it freezes for 6-7 seconds before I can use it for any purpose.
This also affects the voice dialling when the device is on standby mode as it freezes for long time until it recognizes that there is a voice dial and them gives me the beep to start voice dialling and sometimes it does not even gives me the beep.
May be there are some differences between Jasjar and the other Universal devices but these are the problems which I'm facing and this is how I resolved it.
Regards,
Click to expand...
Click to collapse
I have a Jasjar too. ( don't know how to get it into my profile, other then a comment)
You seem much further in know how than where I have arrived till now.
I can't say the machine is without bugs, but speed and memory never have been a problem so far.
Maybe a list of you software would give us a clue?
How big are your Outlook files?
Huib
spb pocket plus
spb diary
Resco Picture Viewer
That's all.
Regards,
khaledelfeki said:
spb pocket plus
spb diary
Resco Picture Viewer
That's all.
Regards,
Click to expand...
Click to collapse
That's not much. Spb pocket plus is suspect?
Huib
khaledelfeki said:
craigiecraigie4,
- Regarding the freeze issue, I'm using Jasjar and it does freezes for 6-7 seconds whenever the power button or light button is pressed to switch the power on.
Also whenever I'm using the voice dial, this freezing causes the voice dial to delay and sometimes not responding.
But after setting the device to always on, I'm not experiencing any of those two problems.
- Battery life is not significantly reduced as you think, I tried both settings and any how I have to charge my phone once every day in both cases.
- spb pocket plus 3.0.4 is the latest version, and I did a typing mistake by saying it's 3.1.4..... sorry for that.
-Regarding the BT fix can you please post it here so that I can download it if possible... and can you please let me know what exactly does it fix?
Regards,
Khaled.
Click to expand...
Click to collapse
Dude, your JJ is F***ed! It should NEVER do this! I've not heard of anyone else complain of such a totally unacceptable delay, and I've not experienced anything like it myself, despite setting my device up from scratch about 10 times now to test various configurations. I stroingly suggest a hard reset, install spbPP (or whatever you prefer), and use for a bit to get used to it. Apply the "BT headset fix" (search for it here, it prevents BT from turning off over night), and "Always on GPRS" if u like that which most of us do, and pocket mechanic (search for "notification queue") to maintain your notifications as per another post I wrote yesterday. You should NOT have this issue at all. 7s would make me throw the JJ away right away! If this does not work for you - take it back. Good luck!
I have the exact same problem of a delay on opening when it has been turned off for a while. Also, a friend of mine has the same problem. Your above mentioned fix of keeping it on appears to have saved the day for us, thanx.
apap,
Thanks for your feedback, It seems it's only me and you who are having this problem, and it's very strange too that I had never faced any problem with blue tooth and I don't need any fix for it.
It seems that not all devices are similar.
Any how, I'm so happy with my device now after making the changes which I suggested on the top of this post, and I'm so happy too that it had solved your problem as well.
All the best.
Regards,
Me too, same problen with freeze, but I newer waited for 6 7 secs, just done a soft reset, and this happends all the time.
Just changed to power of thing, will report back..
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