![]() |
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
Mb more polite would be to add a clutch to servicecontrol to check pebbled status and stop it if alive?
Or to add conflict statement to the service unit |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
From systemd's manpage: "If a unit has a Conflicts= setting on another unit, starting the former will stop the latter and vice versa". This sounds much like the current situation: either pebbled is running, or rockpool, but you don't know which one. I don't know if this kind of conflict resolution can be resolved using a systemd unit configuration. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Ok, so here is the logs when I start rockpoold from the command line : pastebin.com/p4brZPED .
If we take a look at the end, we can read that the new version is detected, but the internal status about available update is set to false. And with the calls from qdbus, I have the same results than before. Maybe because my version number has an unexpected format rockpool can't define if my version is the latest or not ? Edit : I did this with the 0.5-1 version |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Edit: version 0.5-2 should be able to cope with you now. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Code:
nemo ~ $ qdbus org.rockwork /org/rockwork/B0_B4_48_C6_10_B1 org.rockwork.Pebble.PerformFirmwareUpgrade |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Conflict statement allows isolation of the services to avoid "strange unpredictable" behaviour. Pebbled app allows start/stopping the service and see its status. rockpoold is autostarted by app, moreover app locks down when daemon is not running (falls to waiting for service page). This basically grants certain predictability, not providing ultimate solution. Bcz ultimate solution should be a user's choice, nor programmer's. To be completely on the safe side we might implement checks for the stray pebbled processes (eg service is down but process is running) but that's too much overhead and unless reported with certain persistence by users - should be avoided. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Tbh I'm coming round to the idea of declaring a conflict with pebbled in the RPM. I don't think smokku would mind really. Btw I added a gitter chatroom. I thought it might be a good place to discuss finer implementation details in realer time. https://gitter.im/abranson/rockpool |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Service conflict should fine. We may probably also add simple org.pebbled introspection to give a warning when target is published. A fairly simple call to implement in servicecontrol. May even do it right in QML - nemomobile dbus plugin by default is on board. Chat is a good idea, will most probably need it while merging. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
I have a feature to suggest, if you have enough time. Do you think it will be possible to use the PT microphone during a phone call, and to have the call sound from the phone speaker ? It could be usefull when driving for example. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
I know there's an microphone elements to the API, but I thought it was for voice commands instead of Blake's 7 style communications. I don't have a Pebble Time though, so I have no idea. I should think the Voice stuff will be on our shared roadmap with RockWork, but that's a way off yet I should think. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Ok, so with latest commit interface is somewhat usable.
I didn't touch yet DeveloperPage part (includes screenshot page), firmware update and side-load (import page). The rest is more or less usable. (Finally I've set my fav. apps from jolla :) ) I've noticed that rockpoold segfaults occasionally on reconnection (need to enable coredumps to debug) Code:
[D] Pebble::onPebbleDisconnected:494 - Pebble disconnected: "Pebble Time C229" |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Quote:
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
What version are we looking out for for preliminary UI?
edit - and also, where should we report bugs? abranson's github page? Thanks - looking forward to this! |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Do you think you're ready for a PR? People are itching for a UI, and there's more than enough to be going on with. Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
I would really like to be able to get the microphone working with Saera for voice recognition. I have a Pebble Time now so if microphone is added I'd be able to test it.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
0.6-1 released with ruff's UI!
I had to make a couple of changes. It wouldn't build unless I uncommented some of the includes in main.cpp. I also fixed the URLs in the pebblemodels image list to include a 'qrc:///' because they were originally relative in RockWork because they include the qml in the binary with the artwork. The pebble page looks really nice with the latest screenshot overlaid on a picture of your watch model. I'd forgotten that I'd set the cover action to take a screenshot! That needs another icon. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Yes, there's no suitable cover icons for that, the only one which comes to my mind is https://sailfishos.org/develop/docs/...e-download.svg - which somehow reflects the fact you're requesting something from the device.
Re includes - also stumbled on it in the morning while attempting to package the rpm. I think I need to cleanup main.cpp even more, just need to make sure standard silica initialisation is suitable (which I'm sure is the case). Edit: I mean suitable icons from the standard themed resources - i.e. ambient. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Yay, we have Settings! :)
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Nice work ! Thank you very much !!
Everything work fine but one thing : the parameters of "Studio Clock". The menu (language, date format, and color selection) are not well displayed. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
It's a really great start - I like the feel of it the UI, and notifications and everything seem to work nicely. But unfortunately the search feature for Watchapps / Watchfaces doesn't seem to do anything for me at the moment (always returning the same results), meaning I can't get very far testing it.
Is everyone else seeing the same? Using 0.6-1 (according to Warehouse - the app's own 'About' page still says 0.5-2 :), Pebble Time 3.9.1, Sailfish 2.0.1.7. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Yep, the search isn't working for me either. Also, some of the configuration screens just come up blank e.g. Misfit, and those that work won't let me change dropdown list values. If I tap them they get selection but don't present a choice of values.
Seeing the app store as a silica list instead of a web page is really something though. And the installation sequence is really solid. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Ok so it seems there's certain problem in how webkit works in silica, it tries to intercept elements like popups and lists mapping them to silica-based components, and hence would require separate handling for that to work properly. Trying to figure that out but on each line WebKit scream on me it's highly experimental and I shouldn't use internals :) Another possible solution would to attempt using browserWindow instead of WebView - the critical part though is an ability to intercept link clicks (to catch pebblejs://close call).
Will check the search, didn't try it yet actually. Edit: well, the search works to me, but works a bit odd. I.e. I enter apps page, type snowy in the bottom docker, hit search - and it returns me plethora of weather and health apps, but of course not snowy. Also for the search some host with strange name (algloia.io) and hardcoded api key is used. which hints me it's some third-party search engine. Edit2: oops, sorry, fixed :) one of those stupid mistakes. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
The store UI is really slick! Thank you for all your hard work on this.
Exploring watch apps and faces for the first time on my PTS, really enjoying it :) |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Ok, so after long night I realised what I ended up with is basically resembling smoku's (or javispedro's) AppConfigPage, so would probably just copy that page and underlying components from his repo.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
I'm still contemplating on it, don't like the idea of having whole dialog for simple selection, trying to get simple floating listview instead. can PR those two though if you think they worth mainlining without delay.
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
yes, I've intentionally dropped that header thinking it's just useless screen-space consuming rudiment, usually one knows what is he configuring, and sometimes config screens are already full of various headers banners etc. so for actual controls need to scroll down.
Atm making offline cleanup of the developer page, trying to squeeze max from it. Conceptual problem there is ContentPicker which doesn't exist in public api, either need to grab it from internals or make own. Will nail down settings in the evening once back to the sdk - either own or pebbled version. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Hello,
how do I finish the recovery mode of the Pebble Time Round? The firmware-check of rockpoold announces the following: Code:
FirmwareDownloader::checkForNewFirmware:169 - fetching firmware info: "https://pebblefw.s3.amazonaws.com/pebble/spalding/release-v3.8/latest.json" |
All times are GMT. The time now is 04:57. |
vBulletin® Version 3.8.8