Closed
Bug 989709
Opened 10 years ago
Closed 10 years ago
[tarako] unable to recieve bluetooth pair request during phone call
Categories
(Firefox OS Graveyard :: Bluetooth, defect)
Tracking
(blocking-b2g:-, b2g-v1.3 unaffected, b2g-v1.3T affected, b2g-v2.0 unaffected)
RESOLVED
DUPLICATE
of bug 915611
blocking-b2g | - |
Tracking | Status | |
---|---|---|
b2g-v1.3 | --- | unaffected |
b2g-v1.3T | --- | affected |
b2g-v2.0 | --- | unaffected |
People
(Reporter: angelc04, Assigned: echou)
Details
(Whiteboard: OOM)
Attachments
(1 file)
72.70 KB,
text/plain
|
Details |
Steps to reproduce ---------------------------------------------------------------------- 1. Go to Settings and enable Bluetooth and "Visible to All" 2. Make a phone call 3. Use another device to send a bluetooth pair request to test device --> No Pair request displayed on test device. [expected] bluetooth pair dialog should pop up when there is a pair request coming during a phone call. Test Build -------------------------------------------------------------------------- Gaia 14ef4fcdf9199f04f7678755c917dc77f51e13ba Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/b574a7967338 BuildID 20140329004002 Version 28.1 ro.build.version.incremental=70 ro.build.date=Fri Mar 28 06:17:40 CST 2014
Comment 1•10 years ago
|
||
It worked as expected on hamachi using m-c and 1.3. m-c --------------------------------------- Gaia 4cf7ec04b82320a1ff1f825220204f454f951a87 Gecko https://hg.mozilla.org/mozilla-central/rev/1c23863d8dda BuildID 20140330160201 Version 31.0a1 ro.build.version.incremental=324 ro.build.date=Thu Dec 19 14:04:55 CST 2013 1.3 ---------------------------------------- Gaia 0d54a796bdaeb96ca7fb63da2166a46b4f8859f2 Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/ad91817a1967 BuildID 20140330164002 Version 28.0 ro.build.version.incremental=324 ro.build.date=Thu Dec 19 14:04:55 CST 2013
HCI aleady receive Connect Request I/GeckoBluetooth( 83): AgentEventFilter: AgentEventFilter: /B2G/bluetooth/agent, RequestConfirmation I/GeckoBluetooth( 83): Notify: [S] Notify: RequestConfirmation
Doing the pairing caused my phone connection to hang up. Since this is a telephone, I think this should block as the telephone call shouldn't be the one getting killed. Gaia acd18bbd94ebfa534e252a24a75a0617e4b5d5ae Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/91a1b54da4a6 BuildID 20140404004001 Version 28.1 ro.build.version.incremental=eng.cltbld.20140404.044841 ro.build.date=Fri Apr 4 04:48:48 EDT 2014 Tarako
Updated•10 years ago
|
blocking-b2g: --- → 1.3T?
status-b2g-v1.3:
--- → unaffected
status-b2g-v1.3T:
--- → affected
status-b2g-v2.0:
--- → unaffected
Whiteboard: OOM
Comment 4•10 years ago
|
||
Ni? etienne/Eric for further input is there anything that can be done to quickly fix this? thanks
Flags: needinfo?(etienne)
Flags: needinfo?(echou)
Comment 5•10 years ago
|
||
Users will be impacted when he/she get into the car with car kit during the call.
Whiteboard: OOM → OOM [MP_Blocker]
Comment 6•10 years ago
|
||
Hi! Eric, Need your team to help on this case. Thanks -- Keven
Assignee: nobody → echou
Comment 7•10 years ago
|
||
triage: 1.3T+ partner blocker
blocking-b2g: 1.3T? → 1.3T+
Whiteboard: OOM [MP_Blocker] → OOM [priority]
Comment 8•10 years ago
|
||
clearing needinfo until we get feedback from the BT team.
Flags: needinfo?(etienne)
Comment 9•10 years ago
|
||
(In reply to Steven Yang [:styang] from comment #5) > Users will be impacted when he/she get into the car with car kit during the > call. I'm misunderstood here, it's the pairing case, not the connected case. minus for 1.3T.
blocking-b2g: 1.3T+ → -
Updated•10 years ago
|
Whiteboard: OOM [priority] → OOM
Assignee | ||
Comment 10•10 years ago
|
||
I can reproduce this easily with the following steps: 1. Go to Settings and enable Bluetooth and "Visible to All" 2. Make a phone call 3. Press Home key to go back to Homescreen while in-call. 4. Use another device to send a bluetooth pair request to test device (1), (2) and (4) are the same as comment 0. I added step (3) and it seems to be more easily to occur. After investigation, I believe this is not a Gecko Bluetooth issue. When Gecko Bluetooth receives a pairing request event sent from bluetooth stack, it would broadcast a system message to notice Gaia. Once the system message is sent, the job of Gecko Bluetooth completes. So I turned on the log in System Message module and found that Settings app was not launched even the system message was sent correctly: I/Gecko ( 1220): ###################################### forms.js loaded I/Gecko ( 1220): ############################### browserElementPanning.js loaded I/Gecko ( 1220): ######################## BrowserElementChildPreload.js loaded I/GeckoBluetooth( 84): Notify: [S] Notify: RequestConfirmation I/Gecko ( 84): -- SystemMessageInternal 1410371704945 : Broadcasting bluetooth-pairing-request {"address":"28:9A:FA:B5:21:50","method":"confirmation","passkey":982352,"name":"flame-eric"}; extra = undefined I/Gecko ( 84): -- SystemMessageInternal 1410371705067 : Acquiring a CPU wake lock for page key = N1mFHp75Jx2zqEIlQ8WqGIamK7k= I/Gecko ( 84): -- SystemMessageInternal 1410371705069 : Returned status of sending message: 2 I/Gecko ( 84): -- SystemMessageInternal 1410371705071 : _getMessageConfigurator for type: bluetooth-pairing-request I/Gecko ( 84): -- SystemMessageInternal 1410371705073 : Asking to open {"pageURL":"app://settings.gaiamobile.org/index.html#root","manifestURL":"app://settings.gaiamobile.org/manifest.webapp","type":"bluetooth-pairing-request","onlyShowApp":false,"showApp":false} I/Gecko ( 1220): -- SystemMessageManager 1410371707922 : init I/Gecko ( 1220): -- SystemMessageManager 1410371707962 : done I/Gecko ( 84): -- SystemMessageInternal 1410371707964 : Got Register from app://settings.gaiamobile.org/index.html#root @ app://settings.gaiamobile.org/manifest.webapp I/Gecko ( 84): -- SystemMessageInternal 1410371707965 : listeners for app://settings.gaiamobile.org/manifest.webapp innerWinID 4 I/Gecko ( 1220): -- SystemMessageManager 1410371707967 : set message handler for [activity] [xpconnect wrapped nsIDOMSystemMessageCallback] I/Gecko ( 84): -- SystemMessageInternal 1410371707975 : received SystemMessageManager:GetPendingMessages activity for app://settings.gaiamobile.org/index.html#root @ app://settings.gaiamobile.org/manifest.webapp I/Gecko ( 1220): -- SystemMessageManager 1410371708155 : receiveMessage SystemMessageManager:GetPendingMessages:Return for [activity] with manifest URL = app://settings.gaiamobile.org/manifest.webapp and page URL = app://settings.gaiamobile.org/index.html#root I/Gecko ( 84): I/Gecko ( 84): ###!!! [Parent][MessageChannel] Error: Channel error: cannot send/recv I/Gecko ( 84): I/Gecko ( 84): -- SystemMessageInternal 1410371711688 : Got child-process-shutdown from [object ChromeMessageSender] I/Gecko ( 84): -- SystemMessageInternal 1410371711689 : remove the listener for app://settings.gaiamobile.org/manifest.webapp This is a known issue which not only occurs on Tarako but other devices. Please see bug 915611 for more information. Close as a dup of 915611.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(echou)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•