Closed
Bug 825851
Opened 12 years ago
Closed 12 years ago
[Bluetooth][Hfp] Handle AT command: AT+VGM
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
People
(Reporter: echou, Assigned: gyeh)
References
Details
Attachments
(2 files, 3 obsolete files)
1.67 KB,
patch
|
Details | Diff | Splinter Review | |
1.56 KB,
patch
|
Details | Diff | Splinter Review |
To support feature "Remote audio volume control", we need to handle AT command AT+VGM.
Please see 4.28 "Remote Audio Volume Control" of HFP 1.5 for more detail.
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → gyeh
Assignee | ||
Comment 1•12 years ago
|
||
Cache the value of vgm in BluetoothHfpManager and reply OK.
Attachment #697318 -
Flags: review?(echou)
Reporter | ||
Comment 2•12 years ago
|
||
Comment on attachment 697318 [details] [diff] [review]
Patch 1(v1): Handle AT command: AT+VGM
Review of attachment 697318 [details] [diff] [review]:
-----------------------------------------------------------------
r=me with nit picked
::: dom/bluetooth/BluetoothHfpManager.cpp
@@ +630,5 @@
> + NS_WARNING("Failed to extract microphone volume from bluetooth headset!");
> + goto respond_with_ok;
> + }
> +
> +#ifdef DEBUG
We don't need to do this ourselves. NS_ASSERTION won't do anything if DEBUG is not defined.
Attachment #697318 -
Flags: review?(echou) → review+
Assignee | ||
Comment 4•12 years ago
|
||
Assignee | ||
Comment 5•12 years ago
|
||
Comment 6•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
Assignee | ||
Updated•12 years ago
|
Blocks: b2g-bluetooth-hfp
Reporter | ||
Updated•12 years ago
|
tracking-b2g18:
--- → ?
Updated•12 years ago
|
Updated•12 years ago
|
status-b2g18:
--- → affected
Comment 7•12 years ago
|
||
Assignee | ||
Comment 8•12 years ago
|
||
This bug(and other 12 bugs) block Bluetooth certification. So, these bugs need to be marked as tef+ and landed to v1.0.1 in order to pass Bluetooth certification:
bug 827255
bug 827212
bug 827266
bug 828175
bug 823346
bug 827230
bug 828798
bug 835740
bug 846647
bug 828160
bug 827204
bug 825861
bug 825851
So, mark these bugs as tef?. These fixes have some dependency and it would be better to have them landed in a specific order. I'll provide the order later.
blocking-b2g: --- → tef?
Assignee | ||
Comment 9•12 years ago
|
||
I recommend to land these patches in the following order:
01. bug827204
02. bug827255
03. bug823346
04. bug827230
05. bug828798
06. bug827212, patch 1
06. bug827212, patch 2
07. bug827266
08. bug828175
09. bug846647
10. bug825861
11. bug825851
12. bug835740
I'm going to attach patches for b2g18_v1_0_1 for each bug. Please land them in the above order. There should be no conflict and feel free to let me know if I can be any help.
Assignee | ||
Comment 10•12 years ago
|
||
Assignee | ||
Comment 11•12 years ago
|
||
Attachment #738776 -
Attachment is obsolete: true
Comment 12•12 years ago
|
||
tef- for now until tef release partner confirms this is blocking BT cert.
blocking-b2g: tef? → -
Comment 13•12 years ago
|
||
Seems it is confirmed it blocks BT cer as per bug 868347
blocking-b2g: - → tef+
Assignee | ||
Comment 14•12 years ago
|
||
v1.0.1 patch updated.
Attachment #738924 -
Attachment is obsolete: true
Assignee | ||
Comment 15•12 years ago
|
||
Ryan, I've updated all patches. Please land them in the following order, thanks.
01. bug827204
02. bug827255
(03. bug823346 has been landed on v1.0.1)
04. bug827230
05. bug828798
06. bug827212, patch 1
06. bug827212, patch 2
07. bug827266
08. bug828175
09. bug846647
10. bug825861
11. bug825851
12. bug835740
Comment 16•12 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•