Re: [Announce] Pebble Watch Connector daemon 0.5
 

Hi,

thank you for this application!

I just read through this conversation and I am still not sure whether Pebbled supports email notifications or not? At least I couldn't get any notifications on my Pebble. Do you have plans to implement it?

Thank you for your answer.

Re: [Announce] Pebble Watch Connector daemon 0.5
 

According to the feature list at Github there are no Email notifications.
https://github.com/smokku/pebble

Re: [Announce] Pebble Watch Connector daemon 0.5
 

Email notification is in the works, but at the moment very spammy :)
(because its not just email notifications)

Re: [Announce] Pebble Watch Connector daemon 0.5
 

Thanks for the reply!

Re: [Announce] Pebble Watch Connector daemon 0.5
 

E-Mail notifications is waiting for a real deamon configuration interface, as I for once, do not want e-mail notifications, so it needs to be switchable first.

I was thinking about just writing a config file from management app and poking the daemon to reload. But I'm not sure now. I can envision some other apps wanting to switch daemon options.
Now I lean to exposing some settable properties on DBus and managing the config file by daemon only.

Re: [Announce] Pebble Watch Connector daemon 0.5
 

Smoku, Have you already been able to get Music control to work? And how about the "Pebble Dialer"? :)

Re: [Announce] Pebble Watch Connector daemon 0.5
 

Music player support has been added with some commits after 0.5.
The stock music player is not supported, but it could work (i did not test it yet) with the latest skippingstones musicplayer patch.
The support is based on the MPRIS dbus "standard"

I also would like support for pebble dialer :) is there the sourcecode available or other infos to extract the app-messages ?

I primary worked on the notfications and continue working on them until they are less spammy and can be filtered with settings.

Re: [Announce] Pebble Watch Connector daemon 0.5
 

I've patched the music player, but it didn't work though :(
one of my main uses of the Pebble is to control my music :(

sure, check out this post for the sources:
http://talk.maemo.org/showpost.php?p...08&postcount=5

Re: [Announce] Pebble Watch Connector daemon 0.5
 

Nice, i really would like that :).
My next internal todo was to contribute to support appmessages.
Not sure what the current prios for Smoku are but i guess adding an appmanager with support for different apphandler (pebbledialer, smartstatus, pebble 2.0 js sdk handler) would be good todos :) i think

Re: [Announce] Pebble Watch Connector daemon 0.5
 

I am currently working on Music Control, as it is a concrete application of bi-directional communication. It already nicely refactored some code.
As for features my Pebble is already displaying what I am listening to. Next is song switching and volume control.

Then I plan to work on settings interface and support for "mute when connected". I will probably add internal interface exposing the proximity of the Pebble too, as HCI is so nice to provide this data. :)

Re: [Announce] Pebble Watch Connector daemon 0.5
 

It's not a "standard".
It is both de-jure and de-facto standard. See http://incise.org/mpris-speaking-programs.html

Re: [Announce] Pebble Watch Connector daemon 0.5
 

I know, thats why i put standard in quotes :)

On the page you linked, the first phrase "MPRIS is a standard for communication between media players and programs that interact with them." :D

Re: [Announce] Pebble Watch Connector daemon 0.5
 

In my culture putting a phrase in quotation marks means you disagree with its use - thus you quote it, not use it.

Re: [Announce] Pebble Watch Connector daemon 0.5
 

Oh, no i really like you choose a standard and not reinventing the wheel by creating your own.

Not sure if there are other ones for this use-case but as long they support our needs they could be added as-well in the future.

Re: [Announce] Pebble Watch Connector daemon 0.5
 

Maybe up voting this TJC Thread brings MPRIS support to Jolla.
https://together.jolla.com/question/...-media-player/

Re: [Announce] Pebble Watch Connector daemon 0.5
 

BTW, does anyone know what is the recommended way of storing application settings in SailfishOS?

Re: [Announce] Pebble Watch Connector daemon 0.6
 

Released 0.6 with Music Control.

This release covers basic feature set of Pebble without any additional app.
So, now it's time to finally tackle App management.

Re: [Announce] Pebble Watch Connector daemon 0.6
 

Which music app uses MPRIS?
The only one that partially worked for me was QuasarMX.
I could see what song was playing, but I couldn't control it.

Also, seems like you've forget something that at the music control watchapp. When you hold down the Play/Pause button, the Next/Previous track buttons will change to Volumpe Up/Down control.
Will you also add this to your support? :)
By the way, My Pebble fw is on 2.3

(Note: I've already re-added my Pebble within the QuasarMX app, but still doesn't work :( )

Re: [Announce] Pebble Watch Connector daemon 0.6
 

Same here, it shows what song is playing within QuasarMX, but controls are not working. Same with native Media app.

Still great to see general development!

Re: [Announce] Pebble Watch Connector daemon 0.6
 

This is the one I use [for testing].


SOA#1 - I've been using it today constantly and it just works. No issues.

Did you check pebbled.log for errors?

It is already supported.
It's just that, QuasarMX does support volume control.
Maybe whan you enable the locked pages, there is some volume control there..


Mine is 2.2.

You don't have to do anything in the player. Normal pairing is enough.

Re: [Announce] Pebble Watch Connector daemon 0.6
 

You can do it using Management App since 0.3. Don't have to use terminal anymore.

Re: [Announce] Pebble Watch Connector daemon 0.6
 

Ok, it's working there :).

Which patch did you use to get Mediaplayer support?

Re: [Announce] Pebble Watch Connector daemon 0.6
 

Reinstalled, controls still not working. Pebble version 2.02

Also, are you receiving Mitakuuluu notifications to Pebble? That is not working either for me

Re: [Announce] Pebble Watch Connector daemon 0.6
 

None.
I use QuasarMX which already supports MPRIS.

Re: [Announce] Pebble Watch Connector daemon 0.6
 

This is supported in smurfy's notifications branch only.

Also, I am very reluctant to adding specific app notifications. We can't possibly add support for every single application out there.

Also this is against SailfishOS design. We have Conversations interface, which integrates all communications channels - no matter whether it is XMPP, SMS, GTalk, Skype etc. And this conversations interface is already supported by pebbled.
I have no idea why some developers chose to not to integrate with this design, instead rolling own solution, that needs to be handled specially.

Re: [Announce] Pebble Watch Connector daemon 0.6
 

There could be some workaround for this problem.
You could add a switch within the pebble manager that says "Push all notifications".
This way, all notifications WILL be pushed to the Pebble (even android notifications)

Edit:
I think the music control buttons don't work when using firmware 2.3 :(

Re: [Announce] Pebble Watch Connector daemon 0.6
 

Been there for one day.
Extremely annoying. Especially Android download notifications, pushing 100+ notifications with every single % downloaded.
0% downloaded...
1% downloaded...
2% downloaded...
...

Re: [Announce] Pebble Watch Connector daemon 0.6
 

I know :D hehhe
But, hey.. it's better then having no option at all :p
(maybe adding a little warning message below the switch, telling that this mode can be very annoying, would be good)

Re: [Announce] Pebble Watch Connector daemon 0.6
 

I have an idea how to solve this.
Track all applications sending notifications and dynamically add them to Manager list allowing user to disable pushing from specific (already seen) application. This way it does not need constant updates to the app code adding new notification sources and gives total control to the user.

But this needs coding it up.
And I have some other tasks with higher priority.

But smurfy is working on something like this, so he's the one to bug for. ;)

Re: [Announce] Pebble Watch Connector daemon 0.6
 

Is there a prebuilt RPM with the notifications enabled?

Re: [Announce] Pebble Watch Connector daemon 0.6
 

I second this question!

Re: [Announce] Pebble Watch Connector daemon 0.6
 

Is it normal that every vibration turned off when I installed pebbled on the phone? And I am not able to activate it anymore.

Re: [Announce] Pebble Watch Connector daemon 0.6
 

I have no problems over here. Are you sure it's Pebbled that causes this problem?

Re: [Announce] Pebble Watch Connector daemon 0.6
 

I don't know but it's the only application I installed in the last days.

Re: [Announce] Pebble Watch Connector daemon 0.6
 

Ok, it was not the pebbled it was the common problem that the vibrator becomes stuck and must be shook hard to work again (sounds somewhat like a sex game ;)).

Re: [Announce] Pebble Watch Connector daemon 0.7
 

Just released 0.7

Re: [Announce] Pebble Watch Connector daemon 0.6
 

Just got it.

Please try this:
- start QuasarMX
- restart daemon (in control app: deactivate + activate)
- try again media control buttons on the watch

Re: [Announce] Pebble Watch Connector daemon 0.6
 

yes, that works! any idea why this is happening?

Re: [Announce] Pebble Watch Connector daemon 0.7
 

Just installed the openrepos 0.7-1.
Works great
below are some comments:
- I had to reboot to have it working properly. It kept saying disconnected while it obviously was seeing the pebble. Maybe could be better to indicate that the reboot is needed in the description of the app?

- SMS forwarding is working well but not voice call notification. When the phone receives a call, there is absolutely no indication on the watch.

- about SMS forwarding, when it is sent from a number not in the contacts, then it is displayed 'Unknown', I would prefer to have the number used?

- while skipping stones sometimes sends too many notifications, with pebbled, i would say I miss some. I would appreciate a settings to activate/deactivate what you want to receive?

- as pointed by others, QuasarMX control works well but you need the trick explained above (could be nice to have it fixed :)).

- the 'silent when connected' is a cool idea. Could be nice to have it removed when pebble is disconnected? So that sounds are back when the watch is not connected anymore to the phone?

- when the phone is out of reach of the watch, it obviously disconnects. Could be nice to control how long to wait to try re-connect (as in Skipping stones). For the moment, I am not sure how it works?

I have just donated a small amount to your Paypal. Hope it helps while the store is not opened for paid apps!

Re: [Announce] Pebble Watch Connector daemon 0.7
 

It's a known issue (described in the first post). You don't have to reboot - just close/reopen management app to notice.
I lost to much time working around this, and moved on as it is of lesser annoyance and there are more important things.

Could you check ~/.cache/pebbled/pebble.log to see whether are there any errors logged?

This is exactly how it works. When Pebble gets disconnected, daemon restores the profile that was set before putting it to 'silent'.

What do you propose? How it should work exactly?

Currently it waits 1s, if no watch, then 2s, then 3s and so on, extending the wait period 1s a time.
You can always force the connection on the cover page of the app.


Thanks for the donation.
You were The First One. :-)