![]() |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
As for logs - try starting rockpool directly instead through the daemon - it does print all the logs you need.
P.S. And more :) |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Looking at https://rpmfind.net/linux/RPM/opensu...1.armv7hl.html I'd say Jolla/Sailfish has a little to do with it, it's rather up-up-up-stream problem. Could be fixed by re-packaging with all the necessary data but it's not core package so why care (from the vendor perspective). |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
I bit the bullet, moved from pebbled to rockpool. I'm using a Pebble Steel, which was still on firmware v2.9. Updating using rockpool seemed to go smoothly, but at some point the watch booted to recovery mode (v3.8-prf9), and rockpool couldn't make a connection anymore. (Didn't record the log, sorry)
It took me a few hours to realize the normal Android Pebble app won't work, you'd need the Pebble [b]Time[/]b app, to update to v3.10.1. Thanks Pebble :rolleyes:. (Also, I don't have an Android device, which makes it even harder) My PS now sports v3.10.1, but unfortunately Rockpool v0.4 won't connect, even though the Pebble is paired to Jolla. Log: Code:
Mar 17 22:53:14 Jolla [9201]: [D] Pebble::connect:139 - Connecting to Pebble: "Pebble 0A47" "00:17:E9:AD:0A:47" [edit] Uggh, I have a clue: pebbled was mysteriously running again, and happy to (try) to connect. Also, Jolla forgot about the pairing. Code:
[nemo@Jolla ~]$ /usr/lib/qt5/bin/qdbus org.rockwork /org/rockwork/00_17_E9_AD_0A_47 org.rockwork.Pebble.IsConnected |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
I've had problems with pebbled starting again too, and had to remove it. If anyone else has connection problems like this, always check whether the watch thinks it's connected or not to rule out pebbled or another instance of rockpoold running. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Edit: you know what, I think that the appstore would probably filter out those apps that your model/firmware doesn't support before you get to this point. There might be alternative versions of apps for different cases. And also, here's something we haven't seen on Sailfish before. Music track progress! Working but messy, will clean up and release. http://i.imgur.com/tk3cEgK.jpg |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Another request for the music player: can you add the "next track title" showing at the bottom instead of the casette? It can be shown in a small font (I remember that this was possible with SkippingStones) |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
How can I do an upgrade with Rockpool ? |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
https://github.com/pebble/libpebble2...tocol/music.py Maybe it was a thing in an earlier firmware? The only music protocol bits missing now involve telling the watch when the volume or player change, and I don't think that actually does anything on the watch so I didn't bother yet. I'm not sure if the MPRIS interface supports fetching the next track name either. Quote:
|
All times are GMT. The time now is 11:11. |
vBulletin® Version 3.8.8