934372 - [flatfish][Bluetooth][JB only]AVRCP is not working due to uinput event was not been generated

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Bluetooth, defect)

Description

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

We found uninput was not been generated. So shell.js cannot receive any of AVRCP media button key event.

Comment 1

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

This bug looks like related to JB + BlueZ.

Comment 2

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

I have helped to check bluez part.
I found this is caused by /dev/uinput permission incorrect which cause bluez bluetoothd cannot open uinput device node. Again, Sam will help on submit patch to system/core/rootdir/ueventd.rc.
Close this bug.

Comment 3

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

Note: /dev/uinput change to net_bt_stack

Comment 4

[Shawn Huang [:shawnjohnjr][:shuang] (as a happy gecko contributor)]

(In reply to Shawn Huang from comment #3)
> Note: /dev/uinput change to net_bt_stack 
In this way we give the bluetooth file access to Bluetooth api of all.
In JB,  framework/base/data/etc/platform.xml defines
   <permission name="android.permission.BLUETOOTH_STACK" >
        <group gid="net_bt_stack" />
    </permission>
/dev/uinput group permission changes from bluetooth to net_bt_stack, because packages/apps/Bluetooth uses bluedroid library and it uses android.permission.BLUETOOTH_STACK
So this is why JB changes permission.