![]() |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Can you replicate that? Everyone seems to be getting a 0 there, including me, but stupidly I didn't notice before because I'd repaired my watch and so had a fresh file. I assumed that converting it directly to an int would return 0 for any string that wouldn't parse as an int, for the sake of the children. I've added a bit of a dirty hack to skip the parsing and return Enabled when the value is "true", but I'd remove it if I could. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Ok, I'll leave that in then. It won't do any hard. The icon thing is bugging me so I'm trying to store the notif icons as they come in. Just putting off solving the phone call end segfault...
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
It seems there's no way to disable an "ongoing" Android system notification? Like, when the Play store is updating apps, it puts up a notification saying "Updating gmail" or whatever, and if I close that on the Pebble it re-opens in ten seconds or so.This effectively makes the rest of the Pebble useless until apps are done updating.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Is there a way to receive notifications after getting the first one?
Because it stops receiving notifications after the first one, untill I open the app (Skype for example) I wish there was an option to receive all messages without this limitation Edit: The problem is: It shows the messages on the notifications of the phone, but not as a NEW notification. It replaces the old one, which is probably the problem why Rockpool does not detect it :( |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
I'm rejigging the notification part a lot right now to support replacesId, and I don't think we're doing anything if the notification already exists so it doesn't get sent. I'd wondered when that would be the case, but you've just told me. Skype messages?
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
While you're at it - can you also extend struct which is sent for notification filters to the client as well as the string used for id? The way it works now is a bit cumbersome - normalized name to be presented as a source_id (which it isn't actually) and then this stupid attempt to guess who the hell was that in the client.
I.e. I have now almost all filters set to some localized string (eg. Nachrichten) so if i switch locale all my filters become obsolete. Also the icon for the mail notification is now assigned if id contains @ - which would not be true for let say jabber. While original messages contain proper info we need: Code:
method call sender=:1.35 -> dest=org.freedesktop.Notifications serial=2004 path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; member=Notify |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Did you pull my latest master? I'm already storing the icon from the notification. Source id from x-nemo-owner would make more sense though. I'll have a look at storing that alongside a separate friendly/locale specific name.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Not yet, still enchanting websockets to cast them to devconnection. let me rebase...
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
I've also noticed that some other apps, just stops receiving ANY notification at all once it has received 1 notification of that app... (Like "KakaoTalk" also for Android) |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
After a week or so of use, some comments of what seems not to work:
- timeline: I am not sure how it works. I have the option enabled in the parameters and it did sync at first but now I am arriving at Friday and I have a 'end' after appointments of today while I still have entries for tomorrow and next week in the phone? - misfit: i have regular error messages of 'sync failed'... - during the night i usually put my phone and watch in flight mode. Sometimes it does not reconnect in the morning and I have to use the 'disable service' in the developer tools... no big problems anyway thanks again |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Why not use quiet time instead of flight mode?
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Thanks for these. Very helpful.
Quote:
Quote:
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
1 Attachment(s)
Thanks for the reply.
Regarding the timeline, do you mean the logs available in 'developer tools' ? I have opened it but is not meaningful to me ;). Anyway I have attached a shorter version (because tmo is restricting the size) so I have kept only what has happened today and the last line of other 'generation'... let me know if you need something else. Regarding Misfit, I have tried to uninstall it and reinstall it (to make sure I have latest version because i am not sure how to check the version of the app I have) but it is still failing at sync, it reports 'Sync initiated - Wifi required' and then 2s later 'Sync failed - network error'. If I go to settings of the app, I can see that 'your pebble is connected to Misfit account successfully [...]' and all i can do is close or switch account. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Using latest version of everything I think:
rockpool 0.9-4 firmware v3.11.1 |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Hmm ok. Maybe I should reset my Misfit to see if I'd left any changes in. It's quite nice seeing the graphs of your activity on their website once the upload works.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
So currently in rockpool you can only send pebble logs. That means to extract phone logs you need to ssh to phone and start /usr/bin/rockpoold manually (disable service prior to this in the app) and collect the output. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
I guess you need devel-su for it? It logs to system journal, even for user session.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Code:
qDebug() << "Attempting to reconnect in 15 minutes"; How costly, in terms of energy, is it to try to reconnect more often? I.e. what impact would it have to try to reconnect every 15 seconds, instead of every 15 minutes? Also, I wonder if this is the only or best strategy. When the watch' bluetooth connection becomes active, it seems it merely makes itself discoverable. I'd assume it would try to reconnect itself at least once. What strategy does the android app use? |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
15 mins is too long I agree. But we could also detect when the bluetooth adaptor is re-enabled and try to connect immediately.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Ok, this is a start (not related to conversation above, just a dev connection)
Code:
$ pebble ping --phone jolla -vvv |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Fantastic!
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Code:
case QBluetoothLocalDevice::HostConnectable: |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Now almost usable:
Code:
$ pebble install --phone jolla -vvv |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Edit: yes it is reset. I'll investigate properly when I get chance then. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
I've noticed that the Timeline does not work anymore since a couple fw's ago :(
Anyone else noticed as well? |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
DeveloperConnection RPM went to beta. Don't forget to add websockets.
It also means it went with WebSockets API enabled in the JSkit - another thing to test. CloudConnection proxy not implemented - only direct (lan) connectivity (--phone target). PhoneAppLog is not yet implemented, watch log should work (as it uses relay feature). In general since DevCon does not use any auth - it's actually quite a dangerous backdoor. hence current behaviour is that it never starts automatically, should be enabled explicitly in the GUI. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
That's great news, will definitely try it out.
Any suggestions on how we could manage this QtWebSockets dependency in the main app? At the moment they'd have to explictly enable Coderus' repo, and upgraders won't catch that. Should I mirror it? |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Well, yes, probably would make sense to prepare two rpms, with WS linked as a subproject, and _light_ rpm relying on external dependency. We could even slim static version down by removing declarative (qml) part.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Why are libs statically linked anyway? Compatibility? Using shared libraries could save a few precious kilobytes.
|
All times are GMT. The time now is 15:51. |
vBulletin® Version 3.8.8