Skip to content
This repository has been archived by the owner on Feb 12, 2019. It is now read-only.

No notifications when more then one email arrives at a time #16

Closed
awlx opened this issue Aug 10, 2014 · 22 comments
Closed

No notifications when more then one email arrives at a time #16

awlx opened this issue Aug 10, 2014 · 22 comments

Comments

@awlx
Copy link

awlx commented Aug 10, 2014

Hi,

today I noticed that I get no new email notifications when more then one mail is received at a time. Only the phone vibrates and says "2 new messages" but pebble does nothing.

Cheers.

@smurfy
Copy link
Contributor

smurfy commented Aug 10, 2014

noticed that too today. i'm looking in to it.

@locusf
Copy link
Contributor

locusf commented Aug 10, 2014

I guess this is due to how lipstick handles notifications of emails (or rather Jolla notification model) as it updates the same notification for email if there is one unread.

@awlx
Copy link
Author

awlx commented Aug 10, 2014

But it even occurs when it receives two emails at a time. And not only when there is already one notification. I expected to get at least the first notification when two mails arrive at a time.

@smurfy
Copy link
Contributor

smurfy commented Aug 11, 2014

Ok i think i found the problem.

Email notifications gets only sent if both "data" and "subject" is present in the dbus message.
With the combining feature of the notifications in sailfish only on of the fields are filled "2 new emails" (author is empty). so the code does not display the message.

I will fix that, tonight.

Also its planned but i did not do the research for it, to automatically mark the notification read on the phone if successfully sent to the pebble (clear the specific notifications)

@awlx
Copy link
Author

awlx commented Aug 11, 2014

Also its planned but i did not do the research for it, to automatically mark the notification read on the phone if successfully sent to the pebble (clear the specific notifications).

That sounds great :). And cool that you found the issue. 👍

@smurfy
Copy link
Contributor

smurfy commented Aug 11, 2014

Problem is, that as before, you only get the notification "2 new emails" no details about the email.
I hope the autoclear option will help with that once implemented.

@awlx
Copy link
Author

awlx commented Aug 11, 2014

But it's better to get only "2 new emails" instead of nothing :).

@awlx
Copy link
Author

awlx commented Aug 11, 2014

org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.CloseNotification(uid)

should close the notification when triggered I am going to test it.

@smurfy
Copy link
Contributor

smurfy commented Aug 11, 2014

If you implement it, please make sure its an optional feature.

@awlx
Copy link
Author

awlx commented Aug 11, 2014

Ok, it does not make much sense to just dismiss the notifications after being sent to pebble because the email client still does only send "1 new email" if it has an unread mail. Maybe there is a way to reset this count but I don't think this is a good idea.

@smokku
Copy link
Owner

smokku commented Aug 11, 2014

mark the notification read on the phone if successfully sent to the pebble

emphasis :-)

@smokku
Copy link
Owner

smokku commented Aug 11, 2014

Also, we may revisit the idea to treat notifications as a trigger only, not as a data-source and use dedicated interfaces for messages and emails to pull data from.

@awlx
Copy link
Author

awlx commented Aug 11, 2014

Sounds better because at the moment the notifications interface is not that reliable.

mark the notification read on the phone if successfully sent to the pebble
emphasis :-)

Sure but I do not find a way to mark the mail read and not only to dismiss the notification after sending it to pebble.

@smurfy
Copy link
Contributor

smurfy commented Aug 11, 2014

hmpf. latest log4qt changes and i can't compile it anymore? how to install log4qt to the mer build vm?

@smokku
Copy link
Owner

smokku commented Aug 11, 2014

@smurfy
Copy link
Contributor

smurfy commented Aug 11, 2014

I guess i'm to stupid for it :)

I added the chum repo in my mer build vm but i cant install log4qt (it does not find it) also i can't install the rpms manually.

i guess thats because they are for armv7h1 instead of i486 (of which the system in the vm runs).

Can you please describe how to install log4qt in the build vm? (the target)

@smokku
Copy link
Owner

smokku commented Aug 11, 2014

smoku@wing:~$ ssh -p 2222 -i ~/SailfishSDK/vmshare/ssh/private_keys/engine/mersdk mersdk@localhost
[mersdk@SailfishSDK ~]$ sb2 -t SailfishOS-armv7hl -m sdk-install -R zypper ar http://repo.merproject.org/obs/sailfishos:/chum:/1.0.8.19:/testing/1.0.8.19_armv7hl/sailfishos:chum:1.0.8.19:testing.repo

Then set gpgcheck=0 in /etc/zypp/repos.d/sailfishos:chum:1.0.8.19:testing.repo, go to Qt Creator, Sailfish tab, refresh SailfishOS-armv7hl packages and install log4qt-devel.

@smurfy
Copy link
Contributor

smurfy commented Aug 11, 2014

thanks, there was no /etc/zypp... file but providing the -G param

sb2 -t SailfishOS-armv7hl -m sdk-install -R zypper ar -G http://repo.merproject.org/obs/sailfishos:/chum:/1.0.8.19:/testing/1.0.8.19_armv7hl/sailfishos:chum:1.0.8.19:testing.repo

worked too.

Also it still did not compile because it seams there is another dependency on "libicu-devel" too.

I will test my fix over the next 16 hours or so and do a pull request tomorrow.

@smokku
Copy link
Owner

smokku commented Aug 12, 2014

ICU is provided by default in standard repos.

@eras
Copy link

eras commented Feb 13, 2015

Has this issue been really resolved (bug closed)? I'm still receiving 'x new mails' notifications on my Pebble unless I clear them from Jolla's notification view. I have pebble-0.15-1.armv7hl. Or did the latest Jolla firmware update break this..

@smokku
Copy link
Owner

smokku commented Feb 13, 2015

@eras This issue is about not getting notifications about new mail at all on the watch, not about the content.
If you want to talk about getting the content of new messages instead of "2 new messages", you can open another issue, as it is not as straightforward as it seems and may need additional discussion.

@smokku
Copy link
Owner

smokku commented Feb 26, 2015

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants