Closed Bug 792819 Opened 7 years ago Closed 7 years ago

[b2g-bluetooth] BluetoothService::Notify() won't be called after receiving agent events

Categories

(Core :: DOM: Device Interfaces, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

()

RESOLVED FIXED
mozilla18
blocking-basecamp +

People

(Reporter: echou, Assigned: gyeh)

References

Details

Attachments

(1 file, 1 obsolete file)

I used latest code to pair with my HTC device but failed. I found that we did receive RequestConfirmation event in AgentEventFilter, in that case BluetoothService::Notify should be called because it registered for LOCAL_AGENT_PATH & REMOTE_AGENT_PATH in Init(). However, if Bluetooth was ever switched off, mBluetoothSignalObserverTable would be clear, and we won't register again.
blocking-basecamp: --- → ?
blocking-basecamp: ? → +
Assignee: nobody → echou
Attached patch v1 patch (obsolete) — Splinter Review
Since mBluetoothSignalObserverTable (in BluetoothService) is cleared when we stop bluetooth, the entry of LOCAL_AGENT_PATH, REMOTE_AGENT_PATH, and BluetoothManager(/) which should be kept in the table are also removed. 

In this patch, we re-add these entries when bluetooth is started.
Assignee: echou → gyeh
Attachment #664451 - Flags: review?(kyle)
Attachment #664451 - Flags: review?(kyle) → review+
Attachment #664451 - Attachment is obsolete: true
Duplicate of this bug: 789434
https://hg.mozilla.org/mozilla-central/rev/f85da9a728de
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla18
You need to log in before you can comment on or make changes to this bug.