Closed
Bug 812411
Opened 12 years ago
Closed 12 years ago
[SETTINGS][BLUETOOTH] Can't search/rename after a chained of actions
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-basecamp:-)
RESOLVED
WORKSFORME
blocking-basecamp | - |
People
(Reporter: wachen, Unassigned)
Details
*Environment:
Phone - Unagi
gaia master(git): 487a7c18c8ff08db7d2e76239e85e3e5eefcc8b7
gecko aurora(hg): 0d76df6f808d
*How to reproduce:
1. Go to Settings > Bluetooth
2. Enable Bluetooth, and waiting for searching on different devices
3. Connect to all the devices ( more than or equal to 2)
4. Quickly turn off bluetooth
5. wait for a second or 2 and turn on the bluetooth
*Expected Result:
Nothing happened, and the phone started to search for new devices.
*Actual Result:
It sometimes shows the warning that you cannot connect to certain devices. And, "Rename My Device" and "Search for Devices" buttons grey out. There is no devices can be found now. ( < 10% chance it recovered, but usually the bluetooth hangs there and keep searching for devices )
Reporter | ||
Comment 1•12 years ago
|
||
Modified title, cc Gina Yeh and Eric Chou. Also, Jason Smith is added so that he doesn't have to add this manually.
blocking-basecamp: --- → ?
Summary: [BLUETOOTH] Can't search/rename after a chained of actions → [SETTINGS][BLUETOOTH] Can't search/rename after a chained of actions
Updated•12 years ago
|
Component: General → Gaia::Settings
Comment 2•12 years ago
|
||
Do we have to support connection to more than one device at a time ?
blocking-basecamp: ? → -
Reporter | ||
Comment 3•12 years ago
|
||
I don't think any devie would support connecting into more than one devices at a time. But, if there is no warning message or other handle for user to understand it, people might do so. And, after all, it crashed your phone sometimes.
Reporter | ||
Comment 4•12 years ago
|
||
Doesn't reproduce anymore.
Close this
Status: NEW → RESOLVED
Closed: 12 years ago
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•