Closed Bug 856631 Opened 11 years ago Closed 11 years ago

Audio path shall not route to a2dp while phone call state in Ringing mode

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: shawnjohnjr, Assigned: brsun)

References

Details

STR:
1. Turn on Bluetooth
2. Make an incoming phone call
3. Ringtone gets jitter due to audio routes to both speaker and a2dp hw device node
This bug had been resolved by current setting SetConnectionState in audio part. It had been resolved in Bug 872907 Patch 5.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reopen since we can still hit this bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Hey Bruce,
Can you help this bug??
Flags: needinfo?(brsun)
Assignee: nobody → brsun
Flags: needinfo?(brsun)
I just did dumpsys while receiving incoming calls with connected headsets using Galaxy Nexus (ICS 4.0.4) ROM
Output devices is 000000a3, so hfp/a2dp connection state
=========================================================
PolicyManager Interface: 0x284f08

AudioPolicyManager Dump: 0x284f98
 Hardware Output: 1
 A2DP Output: 8
 Duplicated Output: 9
 A2DP device address: 00:21:3C:86:0E:CE
 SCO device address: 00:21:3C:86:0E:CE
 Output devices: 000000a3
 Input devices: 000c0000
 Phone state: 1
 Ringer mode: 0
 Force use for communications 0
 Force use for media 0
 Force use for record 0
 Force use for dock 0
Interesting, hamachi works fine, but unagi does not.
Close this bug since it looks like audio HAL dependent.
Hi Shawn,

Are we going to close this bug?
Flags: needinfo?(shuang)
We found this can be only found in unagi and ZTE Open is fine. It looks like audio hal problem anyway. I don't see problem on ZTE open. Since they are shall be similar chipset.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Flags: needinfo?(shuang)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.