Closed Bug 821181 Opened 12 years ago Closed 12 years ago

Setting call waiting status only when user manually sets the value

Categories

(Core :: DOM: Device Interfaces, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED FIXED
B2G C3 (12dec-1jan)
blocking-basecamp +
Tracking Status
firefox19 --- fixed
firefox20 --- fixed
b2g18 --- fixed

People

(Reporter: hsinyi, Assigned: hsinyi)

Details

Attachments

(1 file, 1 obsolete file)

See Bug 796824 comment 30: setting call waiting on bootup is failing a GCF test case. We shall rather let user manually set the call waiting status, instead of doing that automatically on bootup.
Attached patch Patch (obsolete) — Splinter Review
Don't set call waiting on bootup, wait for user manually setting.
(In reply to Hsin-Yi Tsai [:hsinyi] from comment #1) > Created attachment 691712 [details] [diff] [review] > Patch > > Don't set call waiting on bootup, wait for user manually setting. Hi Arthur, This patch 1) removes setting call waiting on bootup 2) sets the value in settings DB back to the current one (null if we don't know) when setting fails. Is this what you are expecting from the gaia side? Thanks :)
Flags: needinfo?(arthur.chen)
bb? because the issue fails a GCF test case. See comment 0.
blocking-basecamp: --- → ?
(In reply to Hsin-Yi Tsai [:hsinyi] from comment #2) > (In reply to Hsin-Yi Tsai [:hsinyi] from comment #1) > > Created attachment 691712 [details] [diff] [review] > > Patch > > > > Don't set call waiting on bootup, wait for user manually setting. > > Hi Arthur, > This patch 1) removes setting call waiting on bootup 2) sets the value in > settings DB back to the current one (null if we don't know) when setting > fails. > Is this what you are expecting from the gaia side? Thanks :) Thanks for Arthur's feedback. Per our discussion, I'll provide another patch that sets the value to null whenever the network notifies us a request error.
Flags: needinfo?(arthur.chen)
Attached patch Patch v2Splinter Review
Don't automatically set 'call waiting' on bootup.
Attachment #691712 - Attachment is obsolete: true
Attachment #692809 - Flags: review?(allstars.chh)
Attachment #692809 - Flags: review?(allstars.chh) → review+
Certification failures are blockers. If GCF isn't related to certification, please let us know and put the blocking flag back to ?. Thanks.
blocking-basecamp: ? → +
Target Milestone: --- → B2G C3 (12dec-1jan)
Hi Anshul, This patch 'removing setting call waiting automatically on bootup' has been passed review. Could you please help verify if it revolves the GCF failure before I push it to m-c? Thank you :)
Flags: needinfo?(anshulj)
Hsin-Yi, yes I tested that this change fixes the GCF test case faiure.
Flags: needinfo?(anshulj)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: