Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

So I tried to follow those instructions. I wasn't sure the Pebble was paired properly because of the output of hcitool, so I re-paired it. But I couldn't stop the rockpool service because you can't access the settings menu if there are no Pebbles. I kill -9'd the rockpool process, but it started right back up. I went back to rockpool, and suddenly it's working! Didn't get as far as removing the saved configurations, and I'm not entirely sure what fixed it, but it seems to be working now.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

ok, perhaps rockpoold service starts (or may start) prior to bluetoothd on this phone which somehow afects ability of the bt stack to initialize properly. Although service definition explicitly sets dependency on bluetooth service and orders start sequence post it. It could be though when bluetoothd service starts adapter is not yet visible (not initialized by adaptation layer).
If the assumption is correct that means that after reboot you could stumble again upon the same problem and would need to restart the service once the phone is properly booted.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Someone has this problem with a Nexus 5 already. The problem is that the BT is not enabled on boot, and on Sailfish this means the adaptor is not present so Rockpool cannot listen for it to be enabled. It can be replicated on the Jolla1 by rebooting with BT switched off. I added a 'Restart Service' to that first screen as a temp measure, but that was after 0.11-1 release.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Yep, I can replicate that on OnePlus X too.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Hi guys,

This is quite serious problem, since it makes Rockpool unusable with Jolla C. In Jolla 1 it wasn't that bad, because the symptom was, that end of call made Pebble (kind of) boot itself, whereas Jolla C gets stuck.

Is there a fix planned/on it's way ? Is it worth to install Rockpool beta ?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Actually yes - the Pebble freeze/reboot problem has been fixed in latest betas, but I'm not sure this is the same problem as the one on Jolla C.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

So far the only difference i see on new release is that phone wakes up (and lights up the display) each time wifi reconnects. Don't think it would have positive impact on battery life.
Calls are going in and out same way as before.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Apparently it is worth to install, even if for the sake of the test. Because we're getting mixed results which is - we're unable to reproduce the mentioned issue, even though we're getting quite consistent number of reports which means it cannot be mere coincidence and/or instance-specific issue.
Also similarly we're getting reports for both - mainline and beta releases, so it seems to be unrelated to latest fix for the daemon crash+pebble reboot.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I think I've found another thing that was causing my Pebble to have trouble. I have my Nexus 5 set up with MultiROM, and if I boot into Android it seems to overwrite the phone's pairing, and after rebooting into Sailfish the only fix seems to be to unpair and repair it a few times. (I suppose because the phone has the same Bluetooth address across OSes or something?)

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

How do I setup the CloudPebble connection? Simply enabling it doesn't do the trick. I reckon I need to link the pebble to my account somehow, or make my account details known to rockpool. But how?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Now I have installed Rockpool beta, and even received one incoming call ! :) Actually, it went well, the watch didn't boot, nor did the phone freeze.

But the bluetooth connectivity issue is still there: I tend to turn bluetooth off from the phone for night time. In the morning I turn it on again, and the phone and the watch find each other perfectly every time, but Rockpoold does not notice the connection until I restart it.

EDIT: Another succesful call !! \o/ :) :)

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

It's not implemented at the moment, I have no clue what should I do to register the phone at cloudpebble. I didn't find any description for the api or reference implementation. Would need to reverse-engineer the communication (because it's websockets so would be binary protocol, not text)
So that checkbox currently does nothing except sending a log message.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Thanks for the test! So do I understand you correct that with mainline/older version you have a freeze/crash but with latest it works properly? I.e. on jolla 1 mainline rockpool crashes on the call end, but on jolla c the whole phone freezes, while latest beta works ok on both?

There's still occasional service crash on reconnect attempt. Is that behaviour consistent? What may happen is after you disable BT rockpool may (for some unknown reason, it should not actually) try to reconnect and crash, it will then be restarted by systemd and see no BT connection, hence would not be able to reconnect once BT is enabled back. But this should be intermittent, because i cannot reproduce crash on reconnect, even though I saw it happened several times.
To prove if that's not the case you may check before restarting the service it's status (systemctl --user status rockpoold) and see when it was started last time.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Yes, this is correct. But of course the sample is quite small so far (2 calls).

I'll try to remember to check this next time.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Please give a link to said beta to be sure i test the correct one.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Here would be the latest released: https://openrepos.net/content/ruff/rockpool-beta

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Ok, I turned bt off from the phone an hour ago, and again on a moment ago. Devices are now connected, but Rockpool(d) does not realize it.

The status states, that the daemon was started this morning at 6:30, which was the time, when I restarted it manually.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

1.0 released! Thanks to ruff for getting an incredible amount of stuff implemented these last couple of months, and everyone else who's helped with testing, translations and support. Much love to Katharine, mzanetti and the other RockWork guys.

This is a pretty much feature complete Pebble app now. If anyone around here does any youtubing, it'd be great to see how you find it.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

uhm, i thought we'd go with beta1, and I'll squeeze my weatherapp and sendtextapp implementation before release. Although 1.0, 1.1 - who cares :)

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Are you saying you've got even more to add??? :)

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Can you fetch the log for the time when you enabled bt (eg. devel-su + journalctl -bl)?
Also to confirm - it's about jolla1 device on latest (2.0.2.48) release? To know whether I can try to reproduce it

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Yes, I told you I'm working on it %P It just takes a bit longer than I expected, hard to plan personal time with small kid.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Thank you so much for all the hard work guys, apps like this make Sailfish a pleasure to use. Like the visibility & openness of the development too, it's really interesting.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Ehm ... I have used Terminal a bit, but I'm not too familiar with Linux. Do I have to be in a certain folder, when I do that journalctl ?

I have Jolla C nowadays, with the latest SFOS 2.0.2.48.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

No any folder will do, just make sure you're root by entering 'devel-su' then your password. You can only access the right logs as root.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Just spotted one unexpected result of notification cutoff.
EMail delivery is not realtime and mail may be held on MTAs for some time. When it arrives to mailbox and syncs back to phone there's certain delay. Notification timestamp though is original time of the mail - i.e. sent time (not received or delivered time). So if the delay when message is delivered to phone is more than one hour - notification is suppressed as outdated.
Need to look at notification internals whether it has any other reliable timestamp. So far this is how it works. Just for you to know and not to be surprised.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Reporting the first crash bug:

Rockpool crashes (and makes the Jolla C unresponsive) when saving the settings from EuroFootball

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Any logs you could fetch during the crash?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

How can I check out the log?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I guess ssh in, devel-su, then run

journalctl -fl

then cause the crash.

Congratulations, and thanks for the 1.0 (even if disputed ;) ) release - great work all round!

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

The update to the latest version just made rockpool useless for some reason. All notifications are just empty.
https://github.com/abranson/rockpool/issues/44

//Edit: Fixed

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

What happened? How did you fix it?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

After the upgrade, I only got empty notifications and changes for the Timeline interface did not get set.

After a second manual restart of the rockpool daemon it worked. But I had to redo all settings.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Another issue on Nexus 5 (not sure whether this is something you can fix): the Pebble connection stops working after the phone goes to sleep and wake up again. The Pebble thinks it is connected, and Rockpool shows it as connected, but it no longer receives notifications, is no longer able to control media, and things like watch faces can no longer be uploaded.

If this happens while something is uploading to the watch, the upload hangs for half a minute and then it says "Failed" (on the watch).

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

If I remember correctly, Nexus 5 had severe BT problems when I tested it. That was CM11 though. Are you on the newest port?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I installed using CM11, and SFOS 1.1.9 - is there a newer one?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Yeah, though it has other tradeoffs.

http://talk.maemo.org/showthread.php?t=96932

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I think I spotted it this morning - although on a different occasion.

Tonight I left my phone at 15% bat - so it was whining all the night with low battery beeps. This morning I put it on a charger with 5% but noticed that pebble is disconnected. On the way to the office I've turned on my BT headset and realized it cannot connect to the phone. I've checked BT - it was on, however showing only devices which were on nearby - pebble, headset and my BT speaker. In fact I have smth like 10 devices paired - they just disappeared from BT settings screen (I've seen such behaviour before though).

Any attempt to connect the phone from headset failed. When I initiated connection from the phone - it connected.

Attempting to reset BT (off/on) does nothing - pebble is still disconnected, headset still cannot initiate connection.

Looking into syslog I see kernel reporting l2cap_sock_connect: failed -115 and followed by standard rockpool's QBluetoothSocket::UnknownSocketError.

So it seems there's still a problem in the BT stack implementation on jolla, where when BT adapter goes into deep sleep - it cannot be recovered back into proper state.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Not sure if that is the same case. I turn BT explicitely off from the phone in the evening, and on again in the morning. The devices get connected quickly (Pebble vibrates and BT marker disappears), only Rockpoold does not notice the connection. So, the connection is fine just by restarting the Rockpoold, no further actions to BT needed. And the phone connects e.g. to my car's hands-free every time.