Create service property functions for desktop linux bluetooth

RESOLVED INVALID

Status

()

RESOLVED INVALID
6 years ago
2 years ago

People

(Reporter: qdot, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
x86_64
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Android devs wrote their own dbus calls so they don't get back XML blocks for Service functions like on desktop. However, since we'd like to support desktop at some point (and a least for testing), we need equivilents that can make the desktop functions act like the android functions.
Blocks: 674737
Summary: [b2g-bluetooth] Create service property functions for desktop B2G → Create service property functions for desktop linux bluetooth
Created attachment 715134 [details] [diff] [review]
Remove usage of GetDeviceAttributeValue

For m-i builds, recently the message

> I/Gonk    (  109): dbus_func_args_timeout_valist: D-Bus error in GetServiceAttributeValue: org.bluez.Error.Failed (GetServiceAttribute Failed)

started to show up in logcat when trying to connect to a device. It seems like Android stopped supporting this interface, and I couldn't find a related string in external/bluetooth/ or external/dbus/. Since I had problems with connecting the phone to my headset, I removed the respective DBus call from the Bluetooth system. Seems to fix this issue at least.
Attachment #715134 - Flags: feedback?(kyle)
Comment on attachment 715134 [details] [diff] [review]
Remove usage of GetDeviceAttributeValue

Review of attachment 715134 [details] [diff] [review]:
-----------------------------------------------------------------

I hate android's bluez implementation. I hate it so much. ;.;
Attachment #715134 - Flags: feedback?(kyle) → feedback+
> I hate android's bluez implementation. I hate it so much. ;.;

Well, at least this comment made me laugh. :D

Last time I tried, I still had connecting problems with m-i, even though the patch was installed. The phone wants to pair with the headset, but then tells me to check if the device is still in range. I didn't have time to further check what's going on.
We really don't want to do the XML parsing in C++. Making this depend on dbus being in js.
Depends on: 859488
Linux bluetooth implementation was ripped out years ago.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.