kimmoli | at least some pipes work in windows too; mosquitto_sub -h devaamo.fi -t sailfish/kimmoli/# -u kimmoli_read -P x | ..\eSpeak\command_line\espeak -v fi | 05:45 |
---|---|---|
kimmoli | OT: espeak builds on phone, but does not directly provide audio out. ./espeak --stdout kissa | gst-launch-0.10 -v fdsrc ! wavparse ! audioconvert ! alsasink | 05:50 |
tbr | that's probably due to audio policy | 05:57 |
tbr | the same hack as for SIP audio should work | 05:59 |
tbr | that would btw also work to make a caller name announcer | 06:01 |
tbr | you'd need to look up the number in the addressbook though as it's not sent over dbus | 06:02 |
tbr | caller name | 06:02 |
tbr | the number is | 06:02 |
* tbr plays with QoS | 06:02 | |
coderus | tbr: what hack btw? | 06:12 |
tbr | coderus: you can add an application to the pulseaudio config, but only works for the speaker | 06:13 |
tbr | the proper way is to use audio policy etc | 06:13 |
tbr | quoting as I can't copy a link to the comment: | 06:15 |
tbr | FYI if someone wants to test/work with the calling, DISCLAIMER following might break things and even though the workaround described enables incoming audio the underlying routing implementation is for the SIP part utterly broken and incomplete (means for example you wont get audio from earpiece) | 06:15 |
tbr | Append following to /etc/pulse/xpolicy.conf | 06:15 |
tbr | [stream] | 06:15 |
tbr | exe = voicecall-manager | 06:15 |
tbr | group = call | 06:15 |
tbr | Then either restart phone or restart pulseaudio.service and you'll get incoming audio with SIP call. | 06:15 |
kimmoli | speak dat notfications :) http://pastebin.com/CXUM7sD1 | 06:20 |
tbr | :) | 06:25 |
coderus | kimmoli: use dbus-monitor with interface=something set | 06:48 |
kimmoli | i use what i get first working... | 06:49 |
kimmoli | optimisations are overrated | 06:49 |
coderus | :D | 06:49 |
kimmoli | piping mosquitto to espeak was actually nice. now i can "say things" with my desktop-pc by typing them on mqtt-test-app on phone. Only ÄÖ seems to say something like aa-tilde | 07:01 |
tbr | utf8 problem | 07:16 |
kimmoli | yep | 07:18 |
kimmoli | chaging app to sen in Latin1 seems to with espeak, although printout in command prompt is broken still | 07:53 |
kimmoli | meant to say, changing app to send in Latin1 seems to work with espeak, although printout in command prompt is still broken | 07:54 |
tbr | hmm, losing subscriptions on reconnect, this bad. need to fix that | 08:14 |
*** tbr has quit IRC | 11:20 | |
*** tbr has joined #sailfishos-push | 11:22 | |
*** Stskeepz is now known as Stskeeps | 11:55 | |
*** Stskeeps has joined #sailfishos-push | 11:56 | |
*** Stskeeps has joined #sailfishos-push | 11:56 | |
tbr | just pushed some changes | 15:19 |
tbr | now it has a custom notification category which gets an proper icon and working led, sound and vibra feedback! \o/ | 15:20 |
Stskeeps | wp | 15:21 |
Stskeeps | woop | 15:21 |
tbr | I'm not happy with the reliability yet. Despite setting QoS 2 it seems to lose things. Not sure why | 15:21 |
tbr | need to look into that and this illusive "keepalive" thing | 15:23 |
tbr | I'd then want to move on to working on making this more of an generic service though. | 15:25 |
tbr | I want to enable TLS, that will mean installing certificates and moving to port 8883. | 15:25 |
tbr | Then I'd like to add some sort of app specific encryption. Maybe simply a pre-shared key. I'm very much open to hear about best practices and ideas here. Getting privacy right is important from the start. | 15:27 |
tbr | that encryption though might better be realized as "library" or "plugin", that way the push service itself is completely encryption agnostic and just provides a reasonably secure TLS layer in both directions (or a HTTPS API) | 15:32 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!