Closed
Bug 816002
Opened 13 years ago
Closed 13 years ago
[Bluetooth] No updating progress and always transfer failed during Bluetooth file transferring
Categories
(Firefox OS Graveyard :: Gaia::Bluetooth, defect, P2)
Tracking
(blocking-basecamp:+)
People
(Reporter: iliu, Assigned: iliu)
References
Details
(Keywords: regression)
Attachments
(1 file)
*How to reproduce:
1. Turn on bluetooth
2. Pair with a device
3. Send/Receive a file from other device
*Expected Result:
There should be updating progress. Then, show the transfer successfully when the transferring task is finished.
*Actual Result:
No updating progress and always transfer failed.
Updated•13 years ago
|
Component: General → Gaia::System
| Assignee | ||
Comment 1•13 years ago
|
||
Pointer to Github pull-request
| Assignee | ||
Comment 2•13 years ago
|
||
Comment on attachment 686034 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/6675
Since we changed to bind the system message of "bluetooth-opp-transfer-start", "bluetooth-opp-transfer-complete" in bluetooth.js, it missed the transferring information which are needed to pass in the CustomEvent.
Attachment #686034 -
Flags: review?(ehung)
Updated•13 years ago
|
blocking-basecamp: ? → +
Keywords: regression
Priority: -- → P2
Target Milestone: --- → B2G C2 (20nov-10dec)
Updated•13 years ago
|
Component: Gaia::System → Gaia::Bluetooth File Transfer
QA Contact: wachen
Comment 3•13 years ago
|
||
Comment on attachment 686034 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/6675
r=me, thanks for patch my bad miss!
Attachment #686034 -
Flags: review?(ehung) → review+
| Assignee | ||
Comment 4•13 years ago
|
||
Merged https://github.com/mozilla-b2g/gaia/pull/6675
We can close the issue now.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 5•13 years ago
|
||
Verified that this is fixed in 20121212 build from https://releases.mozilla.com/b2g/
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•