Rockpool

Rating: 
5
Your rating: None Average: 5 (22 votes)

Release 1.3-2 is a recompilation for Sailfish OS 2.0.5. It won't install on 2.0.4. When you update your phone, the Rockpool UI won't start until you upgrade to 1.3-2.

Unofficial Pebble smartwatch support for Sailfish.

Rockpool is a port of the Ubuntu Touch application RockWork, which is a port of the Sailfish application Pebbled, which can trace its history back to the original python libpebble written by Pebble developers for exactly this sort of thing. It supports the v3 version of the Pebble firmware, which was released with the Pebble Time and is now available for earlier models. You can update your v2 Pebble classic to the new firmware with Rockpool.

NOTE: Versions 0.10-1+ include WebSocket support, and declare a dependency to Qt5WebSockets, which is also in this repo. Note that you'll only be able to automatically install this dependency if you have added my repository (e.g. through Warehouse), otherwise you'll have to install manually it from here or else installation will fail.

Features

  • Forwards notifications to the watch, they can be opened or dismissed from there. New notification types in the pebble v3 are used: Hangouts for Hangish, Telegram for Sailorgram and the android client, Whatsapp for the android client. Different notification types can be silenced either completely or only when the phone is unlocked. SMS and IM messages can be replied to from the watch using user-defined 'canned messages'
  • Calendar entries are added to the timeline on the watch, automatically refreshed when the phone's calendar is updated. If you have a reminder set on the entry before the event starts, you'll get one on your watch too. If you log into Pebble, then your watch will be able to subscribe to custom notifications from watchapps too.
  • Send music info to the watch, including track duration and progress so you get the progress bar. You can pause, play, skip tracks and change the volume from your pebble.
  • Show incoming call notifications, rejecting, accepting and ending calls.
  • You can manage watch apps, and browse the pebble store for new ones. If you previously added apps manually, you should remove them and add them from the store so you get the nice icon. Your installed apps and watch faces can be synced with Pebble.
  • Lots more: Profile switching when the watch is connected (e.g. silent). Take, manage and share watch screenshots. Update the time on your watch whenever the time or timezone changes on your phone.
  • Language file support for alternative character sets.

To do list

The following features are not yet implemented:

  • Companion apps. These are usually for iOS or Android only, and we haven't implemented a Sailfish API for them yet. Not sure we will
  • Support for Pebble 2 watches. The new models only support Bluetooth Low Energy, which is not currently implemented in Sailfish OS.

Please feel welcome to contribute on GitHub, either by filing issues or chipping in. New translations are always welcome on https://hosted.weblate.org/projects/rockpool/translations/!

Screenshots: 
Application versions: 
AttachmentSizeDate
rockpool-1.3-1.armv7hl.rpm1.05 MB06/11/2016 - 00:55
rockpool-1.3-1.i486.rpm1.14 MB06/11/2016 - 01:33
rockpool-1.3-2.armv7hl.rpm7.35 MB08/11/2016 - 01:21
Changelog: 

- Rebuild for 2.0.5 ABI

Comments

anasyntes's picture

Hello Andrew. I love your Rockpool app. Do you accept donations?

Thanks a lot for your work!

loki_ast's picture

It will be great if you add support for Pebble 2 watches))))

alanmorford's picture

I'm running 2.0.5.6 on a Nexus 4. Rockpool does not seem to work properly under this build despite working perfectly in the previous build. With an original Pebble on the latest fw 3.12.3 and the latest Rockpool version from Warehouse, notifications on the watch are blank.  Also, I can't login via the app. Tapping on the username block brings up the keyboard but the screen goes black. :( Is rockpool still in development?

abranson's picture

Hi,

The app is slightly in limbo at the moment as it's using the browser's webview and that's quite broken in the latest couple of versions of Sailfish. I'll probably build it for 2.1.0 with some small fixes, but it's waiting for a breakthrough. I haven't seen blank notifications before though. Do you even get an icon, or is it just the default bell?

jcoder's picture

Will there be a version for 2.1.0, too?

Installation stops with error on my Jolla 1 (2.1.0.10) and Jolla C (2.1.0.9) with status "repo not available". File not found:  './qt/armv7hl/qt5-qtconnectivity/qtbluetooth-5.2.0+git0-1.3.61-.armv7hl.rpm' on medium 'https://releases.jolla.com/releases/2.1.0.10/jolla/armv7hl'

jdrescher's picture

I was able to install it on my Jolla 1 after doing pkcon refresh in the terminal.

jcoder's picture

Thank you! That made it for me, too.

abranson's picture

Yes I'll do a 2.1.0 version when it's released.

pbh's picture

Unfortunately Rockpool doesn't work on my Jolla tablet any more (Sailfish OS 2.0.5.6). I assume this is because there isn't a rockpool-1.3-2 version for i486? Any chance to get Rockpool working on a Jolla tablet again?

abranson's picture

Sorry, I didn't do an x86 build last time because I didn't know anyone was using it! I'm away this week, but I'll try to get one done when I get back.

Sanpo's picture

Hope there is Pebble 2 support coming soon ;)

abranson's picture

It's not planned by me yet sorry.

cemoi71's picture

Hello, i find that's great app. huge job is done. respect.

Is there a known issue that make the watch unable to change its language?

By submitting the french or german language, it appends nothing and its stay on the eng-us one...

Have good continuation.

penzin's picture

It will be great if you add support for Pebble 2 watches =)

btux's picture

Since about 12 hours I am not able to see any settings pages of apps anymore. Every app is affected.
The settings pages just do not open, I see a spinner and nothing afterwards. Anyone else having this?

I already resinstalled rockpool and resetted ~/.local/share/rockpoold . Did not help.

By the way, after starting from deleted rockpoold dir all my apps and configuration got lost from the pebble. I still have a backup of my latest rockpoold dir and moved it back in place - but how to synchronize its apps to the pebble again? It does not do automatically.

UPDATE Got the apps resynced by deleting blobdb/appsyncstate.conf

ct_berlin's picture

Thanks for the tremendous work done with rockpool. I'm following the progress here as well as in the TMO-Thread. I love the app. 

Somehow my timeline is broken since yesterday. When I use the up and down button my pebble steel resets itself (displaying "pebble" and returing to the menu). I have been factory resetting the watch and reinstalled the app, nothings has helped this far. I've also tried the rockpool beta, which doesn't reset the pebble but is not syncing anything to the timeline either. Notifications and watch-apps work flawlessly. Do you have any hints on what to do?

 

abranson's picture

Wow that sounds intense. It could be that your rockpool data directory has some weird things in it. If you have a file manager on your phone, or you can use a terminal, uninstall Rockpool and delete /home/nemo/.local/share/rockpoold

Failing that, we'll have to get some logs out of you.

ct_berlin's picture

We have to do that then ;-) I've removed the data directory, the problem persists. How can I generate some logs?

abranson's picture

Open a terminal (though an ssh session would be easier to paste from), switch to root with 'devel-su' and your password, then type 'journalctl -fla' to follow the log. Disconnect and reconnect your watch to see the timeline stuff load. I think you might have something in one of your events that is breaking things.

ct_berlin's picture

OK, thanks. The timeline is functional again after fiddling around activating and deactivating my calenders. Haven't found the faulty entry though. Thanks for the effort. I'm looking forward for further releases ;-)

abranson's picture

Did you have to leave a calendar deactivated? If so, is there an odd event coming up in the next few days?

ct_berlin's picture

No, I deactivated all calenders and reactivated them one after another. Now all previously deactivated calendars are all up again. Nothing in particular that seems odd. It might have been the event from this morning, but I didn't see anything about it in the log. 

But I'll look out for it and do some debugging with the log, when the problem occurs again. 

abranson's picture

Thanks!

ct_berlin's picture

Short update: I identified the entries. Seem to be an issue with syncing from CalDav to IBM Notes to Jolla. So it is quite uncommon and probably the fault of IBM Notes (which it is in most cases ;-)).

ruff's picture

Can you re-try this lotus stuff with the latest beta? There was a release with broken calendar so that might be the one which was not syncing. I wonder how would it behave now on new timeline engine.

ct_berlin's picture

Thanks, I've installed the beta and added the calendar again. It's not crashing anymore. However I only have one event in the next days. I'll observe the behavior with more events coming up and give you feedback, when the error occurs again.

ct_berlin's picture

Working alright even with multiple entries. Problem is solved in beta. Thanks for the great work!

alanmorford's picture

You'll have to forgive me but for the life of me I can't get my pebble steel with latest firmware to stay connected to my N4 with the latest Sailfish port. It sees the watch and both confirm the connection but it won't stay connected and rockpool can't see it. I'd appreciate any tips. Thanks.

abranson's picture

You might be able to see what's going on with the daemon output. If you have developer mode enabled, stop the Rockpool service from the 'Developer Tools' page, then launch it manually from Terminal or over an ssh connection by typing 'rockpoold'. You should see what the problem is in there.

alanmorford's picture

So this is weird but all I did was ps aux | grep roockpoold to get the PID. Then issued the 'kill pid#' command with it's PID and the watch autoconnected immediately. *shrug*

Pages