maemo.org - Talk - [SailfishOS] [Announce] Rockpool

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - [SFOS] [Announce] Rockpool - Pebble daemon for Sailfish (https://talk.maemo.org/showthread.php?t=96490)

Re: [Announce] Rockpool - Pebble daemon for Sailfish

while playing with this response action realized we don't have any voice support whatsoever, implementation for endpoint 0x2af8 is completely missing

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by ruff (Post 1506015)

stockpiled quite a big bunch of commits, probably a good time to merge. Posted a beta rpm.
Atm - no (visible) new functionality - except everything timeline related is moved to timeline engine - notifications and calendar.
As a side effect - some colors are changed, some new actions are added, devcon supports pin-insert, there's dbus call to insert the timeline pin, notifications are pooled and re-delivered on connection...
Don't be confused by Canned Response action - it's part of notifcation now however platform part is not yet implemented, so it does nothing except notifying platform part to do the reply.
Next steps - platform part and websync.

That's looking really nice, huge drop in code complexity here. A merge as soon as you're ready would be good - I don't think we should release it until the websync is there as users won't see any benefit (though beta is essential). I'd like to help with the plumbing though. I reckon this will be a good time to drop 1.0.

It'll need pebble.com login too for the websync, right?

Quote:

Originally Posted by ruff (Post 1506030)

while playing with this response action realized we don't have any voice support whatsoever, implementation for endpoint 0x2af8 is completely missing

One thing at a time! :P

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by abranson (Post 1506032)

I don't think we should release it until the websync is there as users won't see any benefit (though beta is essential). I'd like to help with the plumbing though. I reckon this will be a good time to drop 1.0.

It'll need pebble.com login too for the websync, right?

Sure, it's just to reduce review volume later on one side, and get rid of an urge to fix something backdate on the other. While nothing wrong with that per se, it also affects reviewability of the change set.

Yes, it would need oauth token from pebble.com.

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by abranson (Post 1506032)

One thing at a time! :P

Absolutely, just to mark it somewhere till i remember that. Realized then there's better place to leave such reminders - issues board :)

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by Bundyo (Post 1506014)

Here we go again :)

https://www.kickstarter.com/projects...y-new-3g-ultra

crap, attempted to pledge for core - refuses my card. to hell with it.

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Is there any way I can hook Saera into the voice things?

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by taixzo (Post 1506040)

Is there any way I can hook Saera into the voice things?

I don't yet understand fully how it works, but since there's word AudioCodec (speex) I assume that certain phone app should do actual recognition and submit results. And I don't think we have a big offer of speech recognition services on jolla :)
Voice session setup request looks like this:

Code:

VoiceControlCommand

CMD: 01

 SessionSetup

FLG: 00000000

data

 SessionSetupCommand

  Type: 01

   Dictation

  SesID: 0800

  attributes

   CNT: 01

   dict

    Attr

     AID: 01

     LEN: 1d00

      29 (LE)

     Attribute

      SpeexEncoderInfo

       VerStrn: 312e327263310000000000000000000000000000

        "1.2rc1"

       SmplRte: 803e0000

        16000 (LE)

       BitRate: 0032

        12800 (LE)

       BtStrVr: 04

       FrmSize: 4001

        320 (LE)

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Saera is about the only option we have, because I think we can agree that Sailfish and cloud-based speech recognition are not morally compatible. Maybe I should pledge for a Pebble 2 so I can at least test it :)

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by abranson (Post 1505572)

Ofono was the only way I could find to send SMSes. I hadn't found any way of sending IMs yet.

Another way would be using telepathy.
This is the one I've been trying to explore and think should be more appropriate as it allows:

a) step up one abstraction above phone implementation
b) use common interface for SMS and IM messages
c) it automatically adds messages to the comhistoryd - visible in messaging centre.

There was an issue though that only one consumer could be attached to Tp::account as it uses static member internally. However it seems (partially) this was fixed.
nemo-qml-plugin-messages is an example how it works.
Here's an example - https://talk.maemo.org/showthread.php?t=95876
You can get directly to the channel for the phone as it is hardcoded mostly (ring/tel/ring), but IM accounts should be properly discovered based on notification data (from that base64 encoded VariantMap in the x-nemo-remote-action-default) using appropriate telepathy management interface.

Re: [Announce] Rockpool - Pebble daemon for Sailfish

Quote:

Originally Posted by abranson (Post 1506049)

Saera is about the only option we have, because I think we can agree that Sailfish and cloud-based speech recognition are not morally compatible.

That was the essence of my previous message :)

So taixzo - while we're all here - can you briefly introduce us into interaction with your product? DBus calls? API?
I.e. can we just dump raw speex to /tmp/blah and signal Saera to perform recognition of the dump, then catch another signal in return and forward results to pebble?