BluetoothHidDevice profile not exposed on Fairphone 6

Hi Fairphone team, I am developing an Android app that uses the Android Bluetooth HID Device API (“BluetoothHidDevice”).

On my new fp6, it appears that the HID Device profile is not exposed or enabled.

Observations:

- The app works correctly on a Samsung Galaxy S21 using the same Android API.

- On Fairphone 6, registration as a HID device fails.

- Running:

adb shell dumpsys package com.android.bluetooth | grep -i HidDevice

returns no result, which suggests the HID Device service may not be registered in the Bluetooth stack.

Since Fairphone publishes much of its Android source and uses a relatively open software model, I wanted to ask:

- Is Bluetooth HID Device (“BluetoothHidDevice”) intentionally disabled on Fairphone 6?

- Could it be enabled in a future software update?

This would be valuable for accessibility use cases and peripheral-control apps.

Thank you for your time.

Hi @jusjusjus you cant reach FP teams here, you would have to use official ways through support.

Hi, welcome to the forum. This is a user forum and Fairphone employees rarely read what’s happening here. Your best bet is to message support through their email to let them now this is an issue and get any feedback from them on why it might be the case.

Hi Justus,

I noticed the same thing on the official build of e/OS/ for the Fairphone 6, since its version 4.0.

At least in /e/OS case disabling the HID profiles was intentional: there was a specific commit in June FP6: Bluetooth: Disable HID Device Profile

Unfortunately the page returns error 429, so I can’t see what’s inside, but I guess it is about security, as the HID profile works smoothly after enabling it with a Magisk module. I’ve tested the phone as a controller for an old Doogee P1 projector running Android 4.4 and for a newer Rockchip RK3318 tv box running Android 11 (the app I used is BT Remote, com.atharok.btremote).

Edit: I looked more into the issue, and the disabling of the HID device profile has been submitted in April by a Qualcomm engineer for LineageOS, but I couldn’t find any explaination at all about the reasons.