Re: [Announce] Call Notify
 

How can I check if application is correctly installed?
Another idea - I can create CallNotify directory with all needed files there if you send them to me.

Re: [Announce] Call Notify
 

yes, of course you can add all files manually, but that doesn't solve the problem rather than creating new one - if the app wasn't installed correctly then it won't update correctly either and we get more problems in the future...

first let's cover the installation - go to the app manager -> uninstall. do you see CallNotify there? what version? try to remove and reinstall.
check if you have /home/user/.config/CallNotify directory.
check for /usr/share/CallNotify directory and see if it has any files (should contain all the PNG and a WAV file).

Re: [Announce] Call Notify
 

Have now installed latest version 0.0.5.-2 (installed fine with no probs) and it seems to have solved some issues and created others!

This bug on the sending of SMS is now solved for me - thanks

BUT I know get no notification on recieving an SMS

I get notification on missed phone calls, and notification of the number of missed calls..

BUT If I get an SMS it clears the missed calls notification but doesn't leave one of it's own


Hmm, i think it should, but I guess that's a personal preference... My reasoning is to use least number of screen presses - what do you really need to do in that menu after pressing save?

Thanks for the rapid update again and quick replies in this thread :)

Re: [Announce] Call Notify
 

@omerico9
Yes, I see CallNotify 0.0.5-2 when go to Uninstall. Uninstalled. Reinstalled. Still no GUI ot CallNotify directory in .config. Done this drill 3 times already.
Yes, I have /usr/share/CallNotify folder with eight .PNG files and a . WAV file.

Re: [Announce] Call Notify
 

Hmm... ok, lets do it as you've suggested. Sorry for your inconvenience.

Please do the following as root:

mkdir /home/user/.config/CallNotify

create the file conf.txt with the following content:
y;y;y;5.0

Also, make sure you have the file:
/usr/share/applications/hildon-status-menu/CallNotify.desktop

if not, create it:

[Desktop Entry]
Name=CallNotify
Type=python
X-Path=CallNotify

now do both killall commands as mentioned in the previous pages, or restart.

Please let me know how it worked out.

BTW: If it's still not working after that, it must be some unmet dependency issue.

Re: [Announce] Call Notify
 

Does the built-in conversation app is open while is happens? If it does, that's the reason. Also, sending SMS to yourself will not cause the notification.

Re: [Announce] Call Notify
 

In my CallNotify.py line 50:
dbg('constructor end')
should be
self.dbg('constructor end')

I use CallNotify 0.0.5-2

nicolai

Re: [Announce] Call Notify
 

Thank you very much!!!
I'll upload a fixed version ASAP.
Way to go for finding it!

Re: [Announce] Call Notify
 

Anyway, no statusmenu :-(
This are the last lines from the log.txt:

2010-04-01 01:09:41.901613: constructor
2010-04-01 01:09:41.902406: loadImages started
2010-04-01 01:09:42.066255: addGUI end
2010-04-01 01:09:42.067110: constructor end
2010-04-01 01:09:42.560823: startDbusListeners started
2010-04-01 01:09:47.061952: handleMissedCall started
2010-04-01 01:09:47.063417: getMissedCallsCount started. agrs: False
2010-04-01 01:09:52.067415: handleMissedCall started
2010-04-01 01:09:52.080690: getMissedCallsCount started. agrs: False
2010-04-01 01:09:57.069734: handleMissedCall started
2010-04-01 01:09:57.071229: getMissedCallsCount started. agrs: False

I installed CallNotify in my X86 scratchbox environment and it works!
Statusmenu is there, but not on my device.
One additional note, the postinstallscript in scratchbox complains "/var/lib/dpkg/info/callnotify.postinst: line 2: killall: command not found"
Dont know how important this is, because finally it works in scratchbox.

nicolai

Re: [Announce] Call Notify
 

Well, it looks like the code fails on your device in lines 296-300. Apperantly it does not perform 300 otherwise the debug log would have shown it.
That doesn't make sense because all I do in these lines is comparing and assigning some string variables, as you can see. The fact that it works on scratchbox means that perhaps something is different on your device, maybe you've played with it during your development?

I'm pretty lost here. Please feel free to keep playing with the code and let me know if there's anything new.