[SailfishOS] [Announce] Rockpool - Pebble daemon for Sailfish - Page 4 - maemo.org

Active Topics

Maemo repository (8)
to Community by Maemish - 1 day, 3 hrs ago
Porting apps to Leste (44)
to Maemo 7 / Leste by norayr - 1 day, 7 hrs ago
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 4 days, 5 hrs ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 5 days, 3 hrs ago
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 5 days, 3 hrs ago
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 5 days, 8 hrs ago
more...

Page 4 of 72

Thread Tools

	Bundyo	2016-03-17 , 19:58
	Posts: 4,708 \| Thanked: 4,649 times \| Joined on Oct 2007 @ Bulgaria	#31

Originally Posted by Astaoth

Hi,

I've tried to install some apps and most of them didn't work. Here is the full list :
- Stopwatch - works
- Timer - doesn't work
- Timer+ - doesn't work
- Steps - doesn't work
- Misfit - doesn't work
- Cards - works but can't load data
- Love Weather (watchface) - doesn't work
I can't find why the timers don't work, they are simple apps :s.
And this lead me to this question : is it currently possible to remove an app on the PT with only a Jolla phone ?

I also noticed than after extracting apps to the right folders, they are available on the PT only after restarting rockpoold.

This is interesting, as Real Weather and Weather Land from the same developer work fine for me. I also modified some watchface's JavaScript to change their defaults and avoid having to configure them

__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.

Quote & Reply |

The Following 3 Users Say Thank You to Bundyo For This Useful Post:
Amboss, Feathers McGraw, tangent

	Bundyo	2016-03-17 , 19:59
	Posts: 4,708 \| Thanked: 4,649 times \| Joined on Oct 2007 @ Bulgaria	#32

As for logs - try starting rockpool directly instead through the daemon - it does print all the logs you need.

P.S. And more

__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.

Quote & Reply |

The Following 4 Users Say Thank You to Bundyo For This Useful Post:
abranson, Feathers McGraw, mrsellout, tangent

ruff	2016-03-17 , 20:06
Posts: 207 \| Thanked: 482 times \| Joined on Mar 2016	#33

Originally Posted by abranson

Thanks, I don't really have a clue how pkg-config works. I'll mention it in the README. Is this a bug in the sailfish packaging that needs reporting? I'm pretty sure it doesn't affect end users anyway.

pkg-config is the way devel libs are telling to the devel environment how to use them - which -I, -l & -L and other compiler and linker options to use, etc. Without that - options should be provided explicitly.
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).

Quote & Reply |

The Following 3 Users Say Thank You to ruff For This Useful Post:
abranson, Feathers McGraw, tangent

Fuzzillogic	2016-03-17 , 22:01
Posts: 479 \| Thanked: 1,284 times \| Joined on Jan 2012 @ Enschede, The Netherlands	#34

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

. (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" 
Mar 17 22:53:14 Jolla [9201]: [D] WatchConnection::socketError:154 - SocketError QBluetoothSocket::UnknownSocketError 
Mar 17 22:53:14 Jolla [9201]: [D] WatchConnection::pebbleDisconnected:143 - Disconnected 
Mar 17 22:53:14 Jolla [9201]: [D] Pebble::onPebbleDisconnected:493 - Pebble disconnected: "Pebble 0A47"

Any clues?

[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
true

Last edited by Fuzzillogic; 2016-03-17 at 22:15.

Quote & Reply |

The Following 4 Users Say Thank You to Fuzzillogic For This Useful Post:
abranson, Amboss, Feathers McGraw, tangent

abranson	2016-03-17 , 22:38
Posts: 287 \| Thanked: 862 times \| Joined on Dec 2015	#35

Originally Posted by Fuzzillogic

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 . (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" 
Mar 17 22:53:14 Jolla [9201]: [D] WatchConnection::socketError:154 - SocketError QBluetoothSocket::UnknownSocketError 
Mar 17 22:53:14 Jolla [9201]: [D] WatchConnection::pebbleDisconnected:143 - Disconnected 
Mar 17 22:53:14 Jolla [9201]: [D] Pebble::onPebbleDisconnected:493 - Pebble disconnected: "Pebble 0A47"
Any clues?

[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
true

Glad your pebble is ok. I know the migration to 3.x is a two step process involving flashing the recovery firmware first. Hopefully it was pebbled blocking your reconnection the first time - I migrated mine with a tweaked pebbled, but the upgrading in RockPool is unchanged from RockWork so I would think it should be fine. If any other sailfish spartan wants to throw their pebble at it ...

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.

Quote & Reply |

The Following 3 Users Say Thank You to abranson For This Useful Post:
Feathers McGraw, Fuzzillogic, tangent

Astaoth	2016-03-17 , 22:56
Posts: 134 \| Thanked: 370 times \| Joined on Oct 2012 @ France	#36

Originally Posted by abranson

Could you remove those broken apps and try the 'SideloadApp' method in DBus which will use the same code as RockWork uses for installation. Download the pbw and do:

qdbus org.rockwork /org/rockwork/B0_B4_48_80_B9_87 org.rockwork.Pebble.SideloadApp /full/path/to/file.pbw

And see if the daemon does anything extra that might make it work.

Same problem with this method.

Quote & Reply |

The Following 4 Users Say Thank You to Astaoth For This Useful Post:
abranson, Amboss, Feathers McGraw, tangent

abranson	2016-03-17 , 23:35
Posts: 287 \| Thanked: 862 times \| Joined on Dec 2015	#37

Originally Posted by Astaoth

Same problem with this method.

Fishing a bit here, but did you say you were on v3.4 firmware? The latest is v3.10.1, so it's possible those newer apps might be incompatible?

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.

Last edited by abranson; 2016-03-18 at 11:42.

Quote & Reply |

The Following 7 Users Say Thank You to abranson For This Useful Post:
Amboss, Feathers McGraw, HtheB, imaginaryenemy, mrsellout, ruff, tangent

	HtheB	2016-03-18 , 12:59
	Moderator \| Posts: 3,718 \| Thanked: 7,420 times \| Joined on Dec 2009 @ Bize Her Yer Trabzon	#38

Originally Posted by abranson

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

Awesome!
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)

__________________
www.HtheB.com
Please donate if you think I'm doing a good job.

Quote & Reply |

The Following 4 Users Say Thank You to HtheB For This Useful Post:
abranson, Amboss, Feathers McGraw, tangent

Astaoth	2016-03-18 , 13:36
Posts: 134 \| Thanked: 370 times \| Joined on Oct 2012 @ France	#39

Originally Posted by abranson

Fishing a bit here, but did you say you were on v3.4 firmware? The latest is v3.10.1, so it's possible those newer apps might be incompatible?

With qdbus and Rockpool, org.rockwork.Pebble.PerformFirwmwareUpgrade does nothing, org.rockwork.Pebble.FirmwareUpgradeAvailable tell me I'm using the latest firmware available :s. However org.rockwork.Pebble.SoftwareVersion show me that I'm using th 3.4 version.
How can I do an upgrade with Rockpool ?

Quote & Reply |

The Following 2 Users Say Thank You to Astaoth For This Useful Post:
Feathers McGraw, tangent

abranson	2016-03-18 , 14:10
Posts: 287 \| Thanked: 862 times \| Joined on Dec 2015	#40

Originally Posted by HtheB

Awesome!
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)

I'm not sure that's possible without a new Music app - I've implemented most of the protocol described in libpebble2:

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.

Originally Posted by Astaoth

With qdbus and Rockpool, org.rockwork.Pebble.PerformFirwmwareUpgrade does nothing, org.rockwork.Pebble.FirmwareUpgradeAvailable tell me I'm using the latest firmware available :s. However org.rockwork.Pebble.SoftwareVersion show me that I'm using th 3.4 version.
How can I do an upgrade with Rockpool ?

That's the correct method, but not having a newer model Pebble I can't say for sure what your latest version should be. I think at this point it might be best to wait for the appstore UI and see if that makes a difference to the apps you're offered. ruff is steaming away at it on github!