Closed
Bug 966921
Opened 11 years ago
Closed 11 years ago
Turn bluetooth off after NFC handover if user deactivated it in the settings
Categories
(Firefox OS Graveyard :: NFC, defect)
Tracking
(blocking-b2g:-)
RESOLVED
FIXED
blocking-b2g | - |
People
(Reporter: arroway, Assigned: arno)
References
Details
(Keywords: sec-low)
Attachments
(1 file, 1 obsolete file)
Bluetooth is automatically turned on to share data via NFC (Bluetooth handover). When the communication is finished, bluetooth should be turned off if the user chose to deactivate it in the settings before.
Updated•11 years ago
|
Blocks: b2g-NFC-2.0
Updated•11 years ago
|
Updated•11 years ago
|
blocking-b2g: --- → backlog
Attachment #8406486 -
Flags: review?(ehung)
Updated•11 years ago
|
Target Milestone: --- → 1.4 S6 (25apr)
Comment 2•11 years ago
|
||
I do not see this spec on UX doc, does UX designer have been informed this behavior?
Flags: needinfo?(jhuang)
Comment 3•11 years ago
|
||
I remember when we were in the meeting last time, our agreement was to keep the bluetooth on due to technical constraint so that's why I implemented the spec like that.
Yet I'm also happy to see if we can turn the bluetooth off automatically when people choose to turn it off before. It also sounds more reasonable to this use case.
Let me know if dev are ok with this bug, then I'll change the spec shortly.
Flags: needinfo?(jhuang)
I concur with Juwei. It is reasonable to restore the state that was in effect prior to the file transfer. I don't see why BT should be left enabled for a temporary operation. Just to mention it: this is also the behavior of Android.
Updated•11 years ago
|
Attachment #8406486 -
Flags: review?(ehung) → review+
Rebased to current b2g/master hoping to make Travis happy
Attachment #8406486 -
Attachment is obsolete: true
Keywords: checkin-needed
You need to log in
before you can comment on or make changes to this bug.
Description
•