Folks, the Universal is desperately in need of a notification queue manager - one that AUTOMATICALLY deletes duplicates, and \\.\Notifications\NamedEvents\SCRIPT... entries.
PocketMechanic identifies duplicates, but does not clean up automatically every night. Scarybear cleanup apps only target common XDA duplicates - not the Universal's sddeamon dup.
It's a big ask, but would someone be prepared to whip sopmething up quickly. I'd undertake to promote it savagely in the xda-forums, along with encouragement to contribute to xda-developers in lieue of a shareware fee.
Features should include:
- Autorun every night
- Find duplicates and delete
- Find matches to user input and delete
- A text kill-file of matches, so that we (on this forum) can add entires and upload new kill files (presently sddeamon and the above script notifications are proliferating on an almost-clean JasJar after a hard reset)
bump
Anyone know if there may be something in the works somewhere?
Use Pocket Mechanic...it does it all :lol:
It's almost like we either need an automisation of the pocket mechanic function, or a butchered antivirus type app where we replace the virus definitions with a list of notifications we want to get rid of.
What are those NamedEvents notifications?
Are they safe to delete?
I found this elsewhere
Some of you may have noticed these "\\.\Notification\NamedEvents\Script..." entries in the notification queue database that seem to build up for unknown reasons. Well, I just realized that these entries are created for each event where the "Flash Light for" option is enabled.
To prevent these entries from building up, disable the "Flash Light for" option using the "Sounds & Notifications" settings for specific events, i.e. "Messaging: new text messages".
But if you prefer to have this LED alert enabled, avoid selecting "No Limit" as this results in corresponding notification q database entries to expire only approx 42 days later. They do not get cleaned up sooner thus, the build-up.
I've been trying to get Pocket Outlook (8125/Wizard) to provide mail notifications when new (IMAP) messages are received.
Automatic polling is working fine -- the headers and/or messages are retrieved appropriately at the indicated intervals. I'm aware that Messaging cannot be in the foreground if notifications are to be received -- so I've tested with messaging completely closed or minimized.
I also specifically enabled (in sounds/notifications) sound notification for "new e-mail message" and made sure the sound was playable.
It's all to no end. New messages (headers and/or complete text) do come in from IMAP, but there's no notification of any kind. Nothing visually appears. No message text appears (despite the configuration setting that says it should). No audio notification occurs.
I have changed the Messaging paths to use the storage card rather the internal memory -- this unfortunately required me (apparently) to disable the Today messaging line (to avoid the Storage Card2 problem -- I'd love to find an alternative way of getting something back on the Today screen in this regard). However, even before I made this change I wasn't receiving any mail notifications of any kind.
Any suggestions appreciated! Thanks.
calendar notifications
I have the same issue with calendar notifications. everything is enabled, just it does not notify me. It just happened suddenly.
Anyone knows what ther problem might be? I am using Calendar+.
Thanks
Does anyone have a way to turn off the beeps that result from clicking on the start menu or closing an application while still allowing other general notification sounds (like new text message, new email, etc) ?
Yes
Settings/Personal/Sounds & Notifications
uncheck system events.
The clock of WM stop ring after 1 or 2 ring... can I set it continue to ring until I stop it please?
Up,
Is there a hack in the registry to change the repeate of the reminder/alarm please? The alarm default of WM is too poor, it ring 1 or 2 times and stop (the distance between 2 ring is also very long), it's impossible to wake up with that.
I don't understand why, to this version WM6, crosoft do not fix this problem and let WM user look for always an alternative software solution
Ya I don't know why WM has such a crappy alarm interface.
I'm finiding the ringer to lack mp3 support and also repeating the alarm.
I know about 3rd party programs SPBtime/Chronos, but I'm afraid its going to kill battery for something that WM should already have been doing.
ChiGGz said:
Ya I don't know why WM has such a crappy alarm interface.
I'm finiding the ringer to lack mp3 support and also repeating the alarm.
I know about 3rd party programs SPBtime/Chronos, but I'm afraid its going to kill battery for something that WM should already have been doing.
Click to expand...
Click to collapse
Me too, spb kill my battery... Hop MS fixe it in next version WM
How to Enable Repeat Play Audio Sound Notifications in Windows Mobile
How to Enable Repeat Play Audio Sound Notifications in Windows Mobile
=====================================================
In Windows Mobile Pocket PC smartphone device, user can configure and set sounds and notifications alert for various events and activities that happening on the device. The notification alerts can be playing a custom selected sound, ring tone or tune, display message on screen, flash keypad light, or vibrate.
And user can customize their favorite alert music audio and notification method for events such as incoming new e-mail messages, MMS messages, SMS text messages, missed call and voice mail the phone received. However, the notification alert for each event happens just once for one time. Supposedly, it’s possible to set the notification such as beeping and playing audio sound recurringly and repetitively until user acknowledge the e-mail, MMS, SMS or other events.
There is an option of “Repeat” for “Playing sound” in “Sounds & Notifications” control panel of Windows Mobile. However, the “Repeat” check box is always grayed out and disabled for most events, except few events such as Reminder. So user cannot select “Repeat” option in order to make notification alert recurring and repeat.
There is registry hack that able to enable the “Repeat” check box in “Sounds & Notifications” control panel. To perform the change on Windows Mobile registry, a registry editor such as PHM Registry Editor, Mobile Registry Editor or CeRegEditor is required.
In Registry Editor, navigate to the following registry key branch:
HKEY_CURRENT_USER\ControlPanel\Notifications
There is a lot of registry sub-key inside the Notifications folder. Search through one by one to find and locate a registry entry that has its Default (REG_SZ) value as the name of the event. For example, Messaging: New e-mail message, Messaging: New text message, Messaging: New MMS message, Phone: Missed call and etc.
Once found the correct registry sub-key that represents the event that you want to enable the “Repeat” option, edit the value data for Options value name. Change the value to 1073741835 (in Decimal base) or 4000000B (in Hexadecimal HEX base format). Save and exit from registry editor.
Now the Repeat check box is enabled, and user should be able to set repetitive and recurring event notifications.
The alerts appear to completely stop at 10 minutes.
For example a text message comes in, you get an alert
You get an alert every 30 seconds for 3 minutes
You get one alert at 5 minutes
You get one final alert at 10 minutes
Tweak and Configure How Notifications Work in Windows Mobile Notifications
Tweak and Configure How Notifications Work in Windows Mobile Notifications
=========================================================
Windows Mobile powered device (including WM5, WM6 and WM6.1) has a registry key that allows user to tweak, control, configure and customize how notifications work in the mobile Pocket PC (PPC) device. For example, whether a notification should shows or hides the icon in taskbar, play notification sound, pop up notification bubble for user to dismiss or vibrate.
One notification that can be configured via the said registry key is SMS sent notification, other than the SMSNoSentMsg registry key. Then Options registry entry, under HKEY_CURRENT_USER\ControlPanel\Notifications\Default registry branch, when changed to reflect user own preference, may affect other notification in Windows Mobile device too, especially those unable to configure via Sounds and Notifications control panel GUI.
To perform the registry hack to configure different settings for notifications in Windows Mobile, run any registry editor on Windows Mobile device (such as PHM Registry Editor) or remotely access mobile device registry with CeRegEditor from desktop PC, and then navigate to the following registry key:
HKEY_CURRENT_USER\ControlPanel\Notifications\Default\Options
Then, change the DWORD value to any of the following value, which also shows its corresponding results on notification respond, depending on user’s preference:
• 0 - Show icon
• 1 - Show icon and play notification sound
• 2 - Show icon and vibration
• 3 - Show icon and vibration and play notification sound
• 4 - Same as 0
• 5 - Same as 1
• 6 - Same as 3
• 7 - Same as 3
• 8 - Show icon and notification bubble
• 9 - Show icon and play notification sound and show notification bubble
• 10 - Show icon and notification bubble and vibration
• 11 - Show icon and play notification sound and show notification bubble and vibration
• 13 - Same as 1
The change takes effect effectively.
I wanted my sms application to be always running in the background so that I can access/send sms quickly.
I put a link of the sms application into the \Windows\Startup\ folder so that it is called up even after a soft reset. The "problem" is that the sms application will be displayed after a soft reset instead of the home screen. Is it possible to set it such that sms application is called up after every soft reset but is running in the background so that the home screen shows up everytime?
Friend, once you start SMS, the SMS application is a always running in the background till the time that you run ouf of memory and the system needs to shut down an application that is not actively bieng used.
True, but why the messaging client have to reload all SMS when opening it ?