Database Info

SPB time and alarms

Hello:
I have SPB time and recently the alarms seem to have stopped working.
They work if I place a test alarm in the afternoon for example, but the ones in the morning to wake me up for work never go off.
I have tried, wakeupteak, and scarybears check notify, to no avail, I have re-installed SPB time and the alarms. I have rebuilt my unit from the ground up. Still the same problem!!
SPB time are out of ideas themselves.
Any ideas on what the problem may be, or can someone suggest an alternative clock/alarm program for the PPC for me to try.
Thanks.

Aame problem here. AlarmX from MTUX seems to work but it's not as pretty.

There are posts on the forum somewhere telling why this is. It's something like the device goes in to sleep mode (excuse the pun). The built in alarm works Ok (for me) and so does the alarm in Stop Time.

I've had problems with alarms for almost two years - I've found only two solutions:
Try SuperAlert from WhittakerMoore - it cured my alarm problems except when I had stuff which clashed with it, however it is commercial.
A more recent and radical approach which has also worked for me is as follows (you will need software which can modify the Notifications database, such as Anton Tomov's Pocket Mechanic).
The root of the problem is the CALNOT process which runs at midnight - it performs housekeeping and if it doesn't complete correctly, it fails to trigger the first alarm of the day (and therefore any subsequent ones until you turn the device on).
Use your product of choice to simply delete the midnight notification entry which runs CALNOT.exe - this means that the housekeeping isn't done every night but the alarms will be reliable, since it now cannot fail to complete(!). To make sure the cleanup does occur now and again, put a shortcut to CALNOT.exe in the startup folder. Yes, it makes startup after a soft reset a little slower but it's worth it I feel for reliable alarms. Alternatively you could run CALNOT manually. You must remember to remove the CALNOT notification after each time it runs (including timezone changes) as it reinstates its midnight entry each time.
Although I have over 350 entries in my calendar, I haven't noticed any degradation without the regular housekeeping but I have noticed the alarms working - it now wakes me every morning except when I forget to delete the damned entry after a soft reset.
Let me know how you get on.
Note: If anyone out there wants to knock together a tiny app. which runs CALNOT then removes the notification, I for one would be very grateful - I haven't had the time to do any WM coding yet.

I almost missed a plane because the alarm didn't ring so it's important to fix it. However:
simply delete the midnight notification entry which runs CALNOT.exe
Click to expand...
Click to collapse
how to find this program?
I searched at "calnot.exe" in the registry: nopes, searched in windows/startup: nopes. So how to find the program that calls calnot.exe to delete it? Or just delete the file calnot.exe?
Please help

henk-jan said:
how to find this program?
I searched at "calnot.exe" in the registry: nopes, searched in windows/startup: nopes. So how to find the program that calls calnot.exe to delete it? Or just delete the file calnot.exe?
Click to expand...
Click to collapse
mtbsoft said:
(you will need software which can modify the Notifications database, such as Anton Tomov's Pocket Mechanic).
...
Use your product of choice to simply delete the midnight notification entry which runs CALNOT.exe
Click to expand...
Click to collapse
Do NOT delete the program calnot.exe! Re-read what I wrote, in particular the need for software to edit the notifications database - THAT is where the entry is which needs to be deleted.
Do not quickly skim across the post details, getting half the picture then blindly blundering around in your device - that is the fast way to a hard reset!

Thanks for the quick reply. I didn't read it well, indeed, sorry.
So I deleted calnot from the notication queue and now it has to be fixed, apart from running calnot now and then? Do you (after a run) have to delete calnot again from the queue?

No worries, I just didn't want to be the cause of a hard reset.
Generally running calnot doesn't seem to restore the notification entry, there is a special system notification entry (which I don't recommend you delete) which restores it at each soft reset.
Good luck and let us know how you get on.

@mtbsoft. Thanks for you're warning. But now I have some troubble with calnot.exe : can't copy/shortcut it to startmenu as you mentioned, can't even rename the read only status and can't run it (i.e. after double clicking I don't see it in the notification database appear). Any sugestions?

Tapping on it will run it - it doesn't have a user interface so won't be visible. I think you've misunderstood about the notification - running calnot.exe manually WON'T put the notification back, that only occurs when you soft-reset.
I assume you are using the in-built File Explorer, you should be able to navigate to calnot.exe then tap and hold to select Copy. Now go to the \windows\startup folder and use the Edit menu at the bottom left to select Paste as Shortcut. calnot.exe is actually in ROM so you can't rename or delete it (easily).

It worked! I tried it several times like you described, but got the message it was in use, or something like that. But now it's ok. Thanks a lot, the alarms seems to work properly.

@mtbsoft: I found a program/tweak that may solve the problem. It's free.
Look at http://www.pocketpcfreewares.com/en/index.php for wakeup tweak

All wakeup tweak does (to my recollection) is adjusts the Power up timeout that so many others also do - the results are variable and it doesn't work for me. I actually found a better solution in the shape of SuperAlert from www.whittakermoore.com - finally 100% reliable.

I didn't no, learnt again something. I'll give it a try. Thanks

WM6 goes to sleep and won't wake unless soft reset

Does anyone know of a resolution to the device going to sleep after a specified time and not re-waking? I tried the Backlight setting and Power setting, but the device seems to go to sleep and not wake up. I have to soft-reset it get it to respond and even phone calls go straight to voice mail.
any help is much appreciated

I had the same problem. It's so random that it's hard to find out a reason

feareddevil said:
Does anyone know of a resolution to the device going to sleep after a specified time and not re-waking? I tried the Backlight setting and Power setting, but the device seems to go to sleep and not wake up. I have to soft-reset it get it to respond and even phone calls go straight to voice mail.
Click to expand...
Click to collapse
What ROM are you running? What radio and ipl/spl do you have? I have to say I've never seen this on any of the WM6 roms I've been on (MBE, mUn, nottoosmart, faria, xplore). I wonder if its some 3rd party app thats misbehaving / conflicting with WM6? Are you running any Spb programs (a couple of those seem to have issues with WM6 in other ways).
Not sure how often it happens, but if possible you should go back to a clean flash of the rom and try using it just that way to see if the problem still happens.

3DES.2 ROM
SoftBank X01HT
Cingular Network
ROM: 3.23.0.2
Radio:1.38.30.10
OS:5.2.968 (B 17736.0.2.0)
Protocol:32.71.7020.12H
HERM200
I am concerned about reflashing, since I already bricked a device trying to roll back to an original rom (and I did read wiki) Any help is greatly appreciated. I boot fresh and do nothing but press the power button to turn off the screen and it happens everytime, the greenlight still blinks but nothing happens.

feareddevil said:
HERM200
Click to expand...
Click to collapse
Well, keep reading this forum and you will probably brick it again! You do realize you are reading the Wizard forum and not the Hermes forum???

If I set the minimum cpu speed to 130mhz or below I get the exact same problem, Are you using battery status or some other omap scalar program?

uugg-- sorry guys, I read the Hermes forum, but clicked the wrong link when I was mobile and posted the first message.
I am not sure if I am running a slower mhz. Is that default on 3DES.2? I will research how to change but if you can tell me quickluy - I will gladely take instructions to test.

The only way to change the speed is if you are running something like BatteryStatus or OMAPCLOCKplus or XCPUSCALER. Those will allow you to set a "min" on your phone and will drop your CPU down to the min when you aren't doing anything. So if the min is set to low, you phone can lock up similar to what you are describing.
You'll have to find out from other Hermes users what a good min is for your device. Personally on my Wizard I set the Min to 143 or 147Mhz. It can go lower, but I don't think it makes that much difference and don't care to find the bottom that works before I have problems. Just like I run a max of 260Mhz. I know I can run 273, but I don't see much difference, and really don't want to have issues by running faster when I can't see a performance gain (but thats just me).
Good luck!

Thank you everyone. I have narrowed it down to the powersave.dll. When I disable this - it no longer causes the lockup issues. I did not try adjusting the min value but it does appear to be the issue as I will assume - that powersave option does exactly as you outlined above.
regards and thanks again.

This is a common problem if you have installed a "Today" application on a storage card (the microSD card). If you did this, reinstall to the main memroy any Today application or any application that is in the "'windows\startup" folder.

Backlight reverting to 10 seconds

I am posting this because 1) I don't think this issue is specific to one cooked ROM, and 2) despite searching, I can't find a solution.
The issue is that with all of the ROMs I tried that are based on recent AT&T or HTC 6.1 ROMs, the backlight reverts back to 10 seconds. I can change it through Backlight settings to something else, and go back to the control panel a minute later and see it's back to 10 seconds. Very annoying.
I've seen this with a couple of L26 ROMs, the stock AT&T 6.1 ROM, and the HyperDragon III Pro ROM which I am currently using. I see this whether I have S2U2 or not (I am on 1.22b now). My current set-up: HardSPL 3.56, HyperDragon III Pro Sept-17, S2U2 1.22b... but like I said, I don't think it's ROM-specific.
Calling all experts: is there a fix for this? (If you are planning on posting something like "I don't have this problem" or "Change your backlight setting through the control panel", please don't clutter the thread with your post).
Thanks!

I spent a fair bit of time searching this and testing various suggestions that seemed to work for other people, however I was constantly getting the 10-second reversion, plus the even more annoying dimming backlight when locked.
Anyway I posted this:
http://forum.xda-developers.com/showthread.php?t=425361
And now after removing the registry 'BatteryTimeout' my backlight is working exactly as I want it - i.e. backlight dims afer 30-seconds regardless of whether it is locked or not, plus when locked the backlight comes on when the screen is tapped.
Now wait for the various replies saying 'use the search'.....
Andy

FWIW, I too had this annoying issue, but found that using ROMeOS roms (last version is 4.6) I don't get this issue. Not sure why or what the chef did to fix it.
The chef has now moved onto the Raphael...so he is not working on his Kaiser roms anymore

ADB100 said:
I spent a fair bit of time searching this and testing various suggestions that seemed to work for other people, however I was constantly getting the 10-second reversion, plus the even more annoying dimming backlight when locked.
Anyway I posted this:
http://forum.xda-developers.com/showthread.php?t=425361
And now after removing the registry 'BatteryTimeout' my backlight is working exactly as I want it - i.e. backlight dims afer 30-seconds regardless of whether it is locked or not, plus when locked the backlight comes on when the screen is tapped.
Now wait for the various replies saying 'use the search'.....
Andy
Click to expand...
Click to collapse
Thanks, let's see if it sticks. I've tried quite a few methods I found during my search and those didn't work....

It happened to me also with akadonny's 3.29.DK.10 / SPL 3.56.Hard
I changed SPL in the meantime for a different reason, and I had no backlight issues afterwards, but still I would not link that strictly to SPL cause I changed many other things.
Anyway, I found a power setup that works for me very well:
- for "on battery power" I only use turn off device (uncheck turn off backlight)
- for "on external power" I only use turn off backlight (uncheck turn off device)
P.S. This never happened to me with earlier builds, only with 20748.1.4.0.

Well, the first approach didn't work. I have a setup similar to the previous post, but that hasn't helped. I am on SPL 3.56 Hard. Which SPL did you go back to?

Second approach didn't work either. I see a lot of posts with people reporting the same problem... Has there been a definitive solution?

Im using HyperDragon_III_Omnia_20080818. With this ROM I dont have the issue of the 10 sec backlight. I use Hard SPL 3.29.
Chau Juan

I also have this problem and it is making me sick, at night while in bed I am trying to read an ebook but I have to tap on screen every 10 seconds!!
I am HyperDragon_III_Omnia ROM and I have tried many tweaks no luck.
Edit...
Ok I think the problem is now sorted.
Here's what I did... changed the following registry - HKCU\ControlPanel\BackLight\ACTimeout set the DWORD to 0 and reset the device.
So far it seems to be fine.

Invisible Sense said:
I also have this problem and it is making me sick, at night while in bed I am trying to read an ebook but I have to tap on screen every 10 seconds!!
I am HyperDragon_III_Omnia ROM and I have tried many tweaks no luck.
Edit...
Ok I think the problem is now sorted.
Here's what I did... changed the following registry - HKCU\ControlPanel\BackLight\ACTimeout set the DWORD to 0 and reset the device.
So far it seems to be fine.
Click to expand...
Click to collapse
Hmmm, I'll try this, thanks. This should be for backlight while connected... but worth a shot. I wonder if HardSPL version makes a difference... I'm on 3.56.

Trouble accepting calls

Ever since i installed wm6.5 (and I tried a few) I am have trouble accepting incoming calls. This is different from the lock screen issue. Whenever I get an incoming call i see it and either hit the hard key or slide left on-screen to accept but it doesn't answer but continues to ring. if I slide then the slider gets stuck all the way to the left until it stops ringing.
Any ideas as to what could cause this, I have this on different wm6.5 roms, and my friend who has the same wm6.5 rom has no problems.
Please help

well turns out it does answer but takes like a few secs to engage so if i click to answer late in the ring it doesnt have time to answr b4 the person goes to voicemail. i did use trapcall b4, and have now cacelled, maybe it is causing my problems?
any info of how I can reset att to default settings like voicemail and get 100% rid of trapcall.

I got this from a different thread and saved it to my computer just in case I bumped into this problem. I don't know if it'll work on 6.5, but you might want to give it a try:
I had the same problem as many others: When data is on (active or dormant, EVDO or 1xRTT (dormant), it takes many seconds for the calls to be answered, the phone keeps ringing even though I pressed the answer key.
It does appear that one of the tweak applications created the problem, at least for some. After much research, this may be it...
Take a look at your HKLM/Comm/ConnMgr/Planner/Settings/SuspendResume
It is a multi-sz value and should be #777. If it shows anything like ~GPRS or something containing GPRS, change it back to #777 and soft reset.
When I used PHM Regedit to correct this, it seemed to crash (the reg editor never crashed before now). I had to use SKTool's regedit. I will create an export if this will help you.
Once I changed it back to #777, I can answer the call immediately when data is on, time and time again. Prior to this, there was a significant delay.

Dude, thank you so much, I cant believe it was so simple. But I'm confused how it happened in the first place. Anyways yeah, changing SuspendResume to #777 works wonders.

I've got a slightly different Slide To Answer issue.
I just updated to the newest HTC stock rom for my Touch Pro.
I noticed on the first call that Slide to Answer was part of this rom.
It seemed to work well but suddenly I lost the slide button. The green bar for answer and red for reject are still there but the slider itself has disappeared. The only other thing I have changed since the rom upgrade is to add a cab file (from an XDA thread) that restored my Chinese fonts. Could something in that have disabled the button graphic?
What else could it be? How do I get this button back?
Also, is there a way to customize the Slide to Answer screen?
Rom: 5.07.707.2 WWE
Radio: 1.11.25.01

The Slide-to-Answer, for whatever reason, never worked right on my Fuze, so I just disable it.

Clock problem

Hi!
I have htc touch pro (AT&T version) with the latest stock rom.
For months already I am having problems with my clock. Altho its set to +2 Sofia time, it keeps on changing either to +1 time zone either it keeps the time zone but it changes 1 hour ahead or back. Doesn't sound that horrible, i know, but it's practicly unusable as an alarm clock and when i had forgotten my wristwatch home, i never know if i can trust my phone
Please tell me any ideas u might have for this.
Thanks in advance

could it be a regional settings or daylight saving issue?

They are set correctly but it just changes time zones as it wants

Hey,this looks strange,but did you use Weather Master for TouchFlo? I had similar problem and I found a fix,that I have done manually with some kind of database editor(or what was it). The problem was,that in some manila file there was bad timezone hardwritten,so I just rewrited it to +1 in my case and after that it was correct.

no I haven't, and I didn't use manila either. It's weird, since i installed Throttle Lock looks like i don't have the problem anymore, at least for a week now. Just yesterday it was showing correct time but in throttle lock was showing one hour ahead. so i looked at the clock and it was actually time zone +1 (incorrect) but with time of +2, so it was showing correct on the today screen. i changed it to +2 with the time it should be and it was showing correct on the both screens. It's really weird.

(A)
i had this exact prob. i used advance config and disabled the daylight savings c**p. here in oz out dls was extended for an extra week...what a pain. just set it manually. i had the same prob with my original touch.
PiratePete

hmm that's a good idea, thanks, i haven't thought about it. but it's already set there. anyway, it's still working without probs for a week already so i am optimistic about it i really have some feeling the throttle lock fixed it somehow, it's weird but it looks so