Ask / Submit

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-04-30 21:40:40 +0300

I got my Jolla phone yesterday and only now started to investigate the OS, but here's what I found about this: You can read keypresses from /dev/input/event5 or it's symlink /dev/input/by-path/platform-soc-audio.0-event-headset-button . So hardware and kernel support is here ( at least with the current version ), and this functionality could be implemented a userspace application.

I got my Jolla phone yesterday and only now started to investigate the OS, but here's what I found about this: this:

You can read keypresses from /dev/input/event5 or it's symlink /dev/input/by-path/platform-soc-audio.0-event-headset-button . .

So hardware and kernel support is here ( at least with the current version ), and this functionality could be implemented a userspace application.

I got my Jolla phone yesterday and only now started to investigate the OS, but here's what I found about this:

  1. button support :
    You can read keypresses from /dev/input/event5 or it's symlink /dev/input/by-path/platform-soc-audio.0-event-headset-button .

    .

    So hardware and kernel support is here ( at least with the current version ), and this functionality could be implemented a userspace application.

  2. media player control:
    The stock media player ( in 1.0.5.19 ) can not be controlled by another application, since it is missing a dbus interface. To fix this oversight you would need to apply this patch https://github.com/ruedigergad/SkippingStones/blob/master/audioplayer_dbus.patch , or just install the SkippingStones application.