Closed Bug 794054 Opened 12 years ago Closed 12 years ago

[b2g-bluetooth] Received "NoSuchAdapter" error after enabling Bluetooth

Categories

(Core :: DOM: Device Interfaces, defect)

Product:
Core
Component:
DOM: Device Interfaces
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Project Flags:
blocking-basecamp +

People

(Reporter: echou, Assigned: mwu)

References

Details

I tried to enable Bluetooth with the latest codebase, however after few seconds, we would receive an error message "NoSuchAdapter". The bug has been filed on GitHub as well. (https://github.com/mozilla-b2g/gaia/issues/5124)

Actually, the problem is not caused by us. When I rollback BlueZ to a previous commit 76326eda9665254e85c32a5dfeb3c626cac91e5c (on Aug 14), this issue does not exist anymore. After bisect, I finally found the commit "bluetooth: Add support for LE conn whitelist" patch, which is b8bdbaf3b3a97de1a098a62401b2dcd8c834ee3f merged on Sep 14, caused this bug.

Still need to figure out the exact reason why it happened. Maybe we need a more stable version of BlueZ for early stage Bluetooth developing.
Blocks: b2g-bluetooth
blocking-basecamp: --- → ?
Who checked in that patch?
Planning on having mwu roll this back tomorrow. We're just going to stay on the frozen otoro version.
Urph, was planning to roll it back today but I got interrupted and forgot. Taking this so I don't forget.
Assignee: nobody → mwu
blocking-basecamp: ? → +
We're on ics_chocolate_rb4.2 now.

https://github.com/mozilla-b2g/b2g-manifest/commit/b25c5e544e40e6488d00e505490876b96529b41d
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.