maemo.org - Talk - [SailfishOS] [Announce] Rockpool

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - [SFOS] [Announce] Rockpool - Pebble daemon for Sailfish (https://talk.maemo.org/showthread.php?t=96490)

Re: [Announce] Rockpool - Pebble daemon for Sailfish

I thought they were already hidden - they're called transient notifications. I'll have to attach my tohkbd again and test it.

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by taixzo (Post 1504120)

Is there a way to disable "ephemeral" notifications (or at least have them go away from the watch)? Like, when you connect or disconnect a TOHKBD it creates one of the drop-down notifications at the top of the screen - it doesn't ever show up in SFOS's notifications window, but it sits there on the pebble (and can only be dismissed by the back button, because when you try to "dismiss" it says "Failed", probably as a result of the notification not being on the phone.)

I've just tried on my tohkbd, and they get discarded before they get to the filters. Can you check if you have the file /usr/share/lipstick/notificationcategories/x-harbour.tohkbd2.conf? It should contain the line 'transient=true'. If it does, then the output of 'journalctl -laf' as root while connecting the keyboard should tell us more.

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by abranson (Post 1504137)

I do not have that file.

Re: [Announce] Rockpool - Pebble daemon for Sailfish

btw I had some time to run the logs for the problems of Caldav appointments not being sent to the watch.
I can see that the gmail calendar events are indeed being sync , and I do not see problems except maybe at the beginning of the logs even though it is not clear to me which of the error and success wins :) :

Code:

[W] mKCal::ExtendedCalendar::defaultStorage:2057 - Unable to create calendar database directory: "/home/nemo/.local/share/system/privileged/Calendar/mkcal" 

[C] {anonymous}::semaphoreError:57 - semaphore_p.cpp: 57 - Unable to get semaphore /home/nemo/.local/share/system/privileged/Calendar/mkcal/db: Invalid argument (22) 

[C] ProcessMutex::ProcessMutex:214 - semaphore_p.cpp: 214 - Unable to create semaphore array! 

[C] {anonymous}::semaphoreError:57 - semaphore_p.cpp: 57 - Unable to decrement semaphore /home/nemo/.local/share/system/privileged/Calendar/mkcal/db: Success (0) 

[C] mKCal::SqliteStorage::open:180 - sqlitestorage.cpp: 180 - cannot lock "/home/nemo/.local/share/system/privileged/Calendar/mkcal/db" error "Success" 

[W] OrganizerAdapter::OrganizerAdapter:25 - Cannot open calendar database

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by P@t (Post 1504262)

Code:

[W] mKCal::ExtendedCalendar::defaultStorage:2057 - Unable to create calendar database directory: "/home/nemo/.local/share/system/privileged/Calendar/mkcal" 

[C] {anonymous}::semaphoreError:57 - semaphore_p.cpp: 57 - Unable to get semaphore /home/nemo/.local/share/system/privileged/Calendar/mkcal/db: Invalid argument (22) 

[C] ProcessMutex::ProcessMutex:214 - semaphore_p.cpp: 214 - Unable to create semaphore array! 

[C] {anonymous}::semaphoreError:57 - semaphore_p.cpp: 57 - Unable to decrement semaphore /home/nemo/.local/share/system/privileged/Calendar/mkcal/db: Success (0) 

[C] mKCal::SqliteStorage::open:180 - sqlitestorage.cpp: 180 - cannot lock "/home/nemo/.local/share/system/privileged/Calendar/mkcal/db" error "Success" 

[W] OrganizerAdapter::OrganizerAdapter:25 - Cannot open calendar database

This output is what you get if the daemon is running without permission to access the calendar database. This can happen either because it was run manually through qtcreator or from the console, or if it hasn't had its permissions added property to the mapplauncherd permissions config.

The best way to get calendar logs out if to relaunch the service with the GUI, while watching the output of 'journalctl -laf' on an ssh session. This will make sure that the service is launched with the proper permissions.

I can see it removing the calendar entries that had been loaded when the service was running though - those 'removing stale entries' lines - but that doesn't say where they were from, or why others were skipped.

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by abranson (Post 1504100)

Pebbled stored the pbws by UUID, so I'm not sure why he changed it.

Seems I've figured why. AppStore accepts only StoreID - it has no knowledge of the UUID (or at least doesn't expose it to API). However StoreID is not part of apps's metadata.
It means it's not stored anywhere. So appdir name was a way to store the StoreID. If we move to uuid - we then need to store it separately. which by itself is not a big deal.
However since I've already added logic to handle existing apps - the easiest and most consistent way would be then to use following logic:
* For app fetched from the app-store - check if app exists, if yes check current appdir matches StoreID, if not rename it to StoreID.
* For sideloaded app - check if app exists, if yes - install to existing appdir, otherwise install under uuid.
That should allow overriding appstore-installed app by sideloading and other way around.

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Thanks @abranson
I am far from being a developer so I may do stupid mistakes :p

See below a link with logs from the journal this time. I do not find any obvious error so my guess is that Caldav entries are just stored in another place which is not read?
http://pastebin.com/7DujHMNz

I have also tried to see what happens when I try (and fail) to sync misfit:
http://pastebin.com/LkxY17Jv

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Yeah all I can see in the first one are successful entries, there's no mention of anything skipped or missed. You could try disabling one of the caldav calendars in the calendar app and seeing if it's mentioned in the log. There is no other place for them to be stored afaik.

I'll have to reinstall my misfit to check that. It seems to be the problem I thought I'd fixed.

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Thanks for your work with this great app!

One idea: is there possibility to make phone change profile when silent mode will be enabled from Pebble?

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by junnuvi (Post 1504306)

Thanks for your work with this great app!

One idea: is there possibility to make phone change profile when silent mode will be enabled from Pebble?

I think that might require a watch app - I don't think Rockpool can tell if the watch is in quiet mode or not. If it could, then that's another justification for the JS DBus API to be implemented ;)