Closed
Bug 1234694
Opened 9 years ago
Closed 7 years ago
Sound settings reset to default after OTA update
Categories
(Firefox OS Graveyard :: AudioChannel, defect)
Tracking
(blocking-b2g:2.6?, b2g-v2.2 unaffected, b2g-v2.5 affected, b2g-master affected)
RESOLVED
WONTFIX
blocking-b2g | 2.6? |
Tracking | Status | |
---|---|---|
b2g-v2.2 | --- | unaffected |
b2g-v2.5 | --- | affected |
b2g-master | --- | affected |
People
(Reporter: MaxIvanov, Unassigned)
References
Details
(Whiteboard: [2.6-Daily-Testing][Spark])
After applying OTA update sound settings reset to the default
Repro Steps:
1) Downgrade a Aries to RC4
2) Make any changes in sound settings
3) Apply OTA update
4) Verify sound settings
Actual:
Sound settings reset to default
Expected:
Sound settings shouldn't be changed after applying OTA update
Environmental Variables:
Device: Aries 2.6
Build ID: 20151222115357
Gaia: f3cf488a97ecaec43369f3e3d8a7dda52be019f9
Gecko: ad16863d1d45bd3fd7906c76fa1ac1e12d24a133
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 46.0a1 (2.6)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0
Repro frequency: (100%)
Reporter | ||
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-master:
--- → affected
Flags: needinfo?(ktucker)
Whiteboard: [2.6-Daily-Testing][Spark]
Comment 1•9 years ago
|
||
Adding qawanted for branch checks.
blocking-b2g: --- → 2.6?
QA Whiteboard: [QAnalyst-Triage?] → [severe]
Flags: needinfo?(ktucker)
Keywords: qawanted
Comment 2•9 years ago
|
||
This issue DOES occur on Flame 2.6 and 2.5 builds.
Sound settings are reset to default after the OTA.
Note: 20151109004552 latest 2.5 build on the nightly-b2g44-latest channel, and this DOES reproduce the issue.
Environmental Variables:
Device: Flame 2.6
BuildID: 20160115055328
Gaia: 44cc5dfeda9251188c6547f2d5903ee980a5361e
Gecko: 02398f2be72b9bbf5ee79348b73ef122c915aae0
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 46.0a1 (2.6)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0
Environmental Variables:
Device: Flame 2.5
BuildID: 20151109004552
Gaia: cf646c52bb947af28329b0a100df91d1b1f2a907
Gecko: 4eafef5b80f8985c94c4a067f130d37513e1a581
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 44.0a2 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
***********************************************
This issue does NOT occur on Flame 2.2 builds.
Sound settings are not changed, and are still at user defined levels after the OTA.
Environmental Variables:
Device: Flame 2.2
BuildID: 20160112032503
Gaia: 885647d92208fb67574ced44004ab2f29d23cb45
Gecko: d8847129d134
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [severe] → [QAnalyst-Triage?][severe]
status-b2g-v2.2:
--- → unaffected
status-b2g-v2.5:
--- → affected
Flags: needinfo?(ktucker)
Keywords: qawanted
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?][severe] → [QAnalyst-Triage+][severe]
Flags: needinfo?(ktucker)
Comment 3•9 years ago
|
||
Hi, Sotaro,
Could you help me take a look to this issue?
Maybe you can quickly know where is the problem because you did lots works of AudioManager refactoring.
Very appreciate!
Flags: needinfo?(sotaro.ikeda.g)
Comment 4•9 years ago
|
||
It seems like an effect of changing of how to use setting DB. The AudioManager refactoring change the names of storage from profile name to device name.
Therefore, if we use the base ROM that is already have Bug 1218629, the audio volume seems not reset to default.
Flags: needinfo?(sotaro.ikeda.g)
Comment 6•9 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #5)
> If comment 4 is correct, I prefer to close a bug as WONTFIX.
Because, previous way does not scale to multiple audio out devices support. And the problem happens only once FOTA and it cause reset to default volume setting.
Comment 7•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•