@pali, thank for the update, however I was wondering why my CallNotify.py changes were used in your update without mentioning this anyhwere in latest version 0.3.0-1. I think my changes in the file (for which I used a lot of time and energy to make it work) are huge compared with original file from 0.2.0-2.
The way you were doing this update makes people believe (those that didn't read my post: http://talk.maemo.org/showpost.php?p...&postcount=465) that you are the single author fixing this application, and I think this is not nice.
I tested it and sound & vibra events stopped after I read missed call. Try to reboot device. There is problem that if you change settings in control pannel it take effect after reboot...
I've not changed those settings for a looong time, and I have the notifier stuck in my status area telling me I have a sms because I read the sms before the phone notified me it had arrived (may have had the conversation window open - don't recall).
Had the same issue few days ago, but then set all notifications off rebooted and set them back on and rebooted (not intentionally ). And now it seems better.
this works only for "official" silent bulit-in profile ?! Many of Us have profilesx package and using more profiles, I Have profile called "night" and want if it can work on this profile. Is it somewhere changeable at least ?!
call notify ask profiled daemon about current profile settings. if current profile has flag silent then sound events are disabled. if current profile has flag disabled vibrations, then vibra is disabled. if current profile has flag sms sound muted, then call notify do not play sound for new sms (same for calls and im).
so if your profile app create new profile in profiled daemon (yes this is really possible) and set all those flags, then it will work. just try it and write! call notify does not check profile name, so you can rename it as you want...
the correct setting would be :
ringing.alert.type=silent
profilesx does not let you set this setting for custom
profiles. I had this option in a previous developer
version, but it does not do what you would expect.
Most parts of the system (hildon-home/desktop) just
ignores this setting and handles the one silent profile
as a "silent" profile just because of its name/id.
Or in other words, the way the system (maemo) handles
the profiles you can not create another profile that acts
like the one "silent" profile.