![]() |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
It's available through pebble SDK (hence protocol part should be in the libpebble2 i presume), however phone app should support it, acting as a proxy for either direct push or pebblecloud. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Looks like a phone app service rather than something that the watch supports? I can't see anything specific in libpebble2. Maybe it's equivalent to the DBus connection/sideloading...
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
yes, now looking at the api I think from watch perspective it is combination of the SideLoad + DumpLogs loop, phone service is acting as service to communicate then to sdk or cloudpebble.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Thanks, now the clock is working!!!
Ronny |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Really impressive how far this has come this quickly, well done!
One idea for a feature request I've been mulling over: do you think it would make sense to be able to suppress notifications on the watch when the phone screen has been unlocked for a certain amount of time? Sometimes I'll sit there reading my phone for a while, and it always strikes me as a bit pointless (...distracting, wasteful of battery) that my watch still buzzes. It'd have to be optional, obviously. edit - One way you could do this would be in the 'Manage notifications' settings page have three options for each notification - Always / Locked only / Off. That would allow people to prioritise important notifications. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Guys, you ROCK!
I prepared for several walls to run into from reading this thread but it worked on first try with no problems! Even the userdata from apps in 2.9.1 was still there after updating my Steel to 3.10 and reinstalling apps. Gonna report if i hit problems. Everything works perfectly for my usecase. I am super impressed :) |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Code:
signal sender=:1.1 -> dest=(null destination) serial=3592 path=/com/nokia/mce/signal; interface=com.nokia.mce.signal; member=tklock_mode_ind Code:
signal sender=:1.1 -> dest=(null destination) serial=3628 path=/com/nokia/mce/signal; interface=com.nokia.mce.signal; member=display_status_ind |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
So with Coderus' Qt5Websockets packages from Openrepos, it's possible to build Rockpool with the JS websockets stuff turned back on. I've got it running on my phone - the code is in a new branch on github. I don't know of an app to test it with though.
If it works without problems, maybe we could ask for it to be added to the Sailfish repos. It kind of qualifies as a backport... |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Hi,
I was about to take a screenshot of my Rockpool showing my Pebble Time Steel, but I noticed, that the watch image in the app actually shows a screenshot of my watch in a real situation (bluetooth settings showing my devices) !? When did that happen, and how could that be changed ? Another thing: the order of watchfaces can be modified, but the "save" button doesn't seem to do anything ? The order remains the same in the watch as it was before. But once again: thanks for the app, this is brilliant ! :) |
All times are GMT. The time now is 15:02. |
vBulletin® Version 3.8.8