Closed
Bug 864515
Opened 11 years ago
Closed 11 years ago
[Dialer] Invalid message shown when coverage is absent
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect, P2)
Firefox OS Graveyard
Gaia::Dialer
Tracking
(blocking-b2g:leo+, b2g18+ fixed, b2g18-v1.0.1 wontfix)
People
(Reporter: jhammink, Assigned: arthurcc)
Details
(Whiteboard: IOT, Spain, Ikura, Chile, khepera_43875,)
Attachments
(2 files)
Build info: Gaia 080ef2e2041178f7e4d669c7ee5c30f6a7263896 BuildID 20130328103121 Version 18.0 Preconditions: Carry the phone to any place where the Movistar's signal is not present. There, the phone must allow only emergency calls. Steps to Reproduce: Enter a valid mobile number and press the send key. Actual Result: The phone informs the user that the dialed number is invalid; but the real reason that that call cannot go through is that there is no coverage. The message is: "Número de teléfono no válido El número de teléfono al que está llamando no es válido." Expected Result: The correct message should inform the user about absence of <carrier's> coverage. In the case of certification, this means Movistar.
Reporter | ||
Comment 1•11 years ago
|
||
Comment 2•11 years ago
|
||
Hi, This is not a certification blocker, I'd suggest to move this issue to tef-. Thanks David
Updated•11 years ago
|
Whiteboard: IOT, Spain, Ikura, Chile, khepera_43875 → IOT, Spain, Ikura, Chile, khepera_43875, [tef-triage]
Comment 3•11 years ago
|
||
Sounds like we should track this for getting a better user experience, but not block.
blocking-b2g: tef? → -
status-b2g18:
--- → affected
tracking-b2g18:
--- → +
Whiteboard: IOT, Spain, Ikura, Chile, khepera_43875, [tef-triage] → IOT, Spain, Ikura, Chile, khepera_43875,
Comment 4•11 years ago
|
||
Etienne do you know if this is because RIL gives us a wrong error message or is it because we handle a error message in a too generic way in the dialer app?
Flags: needinfo?(etienne)
Comment 5•11 years ago
|
||
Looks like we expect a BadNumber error a try to do the right thing [1]. But for this to work we may need to refine our detection of when only emergency calls are available [2]. Can somebody log the |window.navigator.mozMobileConnection.cardState| we have during the STR? [1] https://github.com/mozilla-b2g/gaia/blob/master/apps/communications/dialer/js/telephony_helper.js#L54-58 [2] https://github.com/mozilla-b2g/gaia/blob/master/apps/communications/dialer/js/telephony_helper.js#L25-28
Flags: needinfo?(etienne) → needinfo?(jhammink)
Comment 6•11 years ago
|
||
I think emergencyCalls is detected with : "window.navigator.mozMobileConnection.voice.emergencyCallsOnly === true" see eg https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/statusbar.js#L541
Comment 7•11 years ago
|
||
(In reply to Julien Wajsberg [:julienw] (PTO until Monday 13th May) from comment #6) > I think emergencyCalls is detected with : > > "window.navigator.mozMobileConnection.voice.emergencyCallsOnly === true" Cool! Thanks Julien! Should be pretty straightforward then, we need to change the telephony helper to use this property in order to detect if we're in a emergency calls only mode.
Flags: needinfo?(jhammink)
Reporter | ||
Comment 8•11 years ago
|
||
FWIW, problem does not appear on B02 build (4/26) in Chile certification, nor on 5/13 build.
Reporter | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Comment 9•11 years ago
|
||
Hi I have just tried with the official version delivered to certif. lab for the final IOT round, and I still see this issue. QC RIL version: "ro.build.firmware_revision=V1.01.00.01.019.120" gaia commit: 50abeb2 Merge pull request #10032 from alivedise/bugzilla/872912_v1.0.1b gecko commit: a6a5487 Bug 875483 - YouTube HTML5 Playback hangs Firefox. r=derf,a=tef+ For sure this not a blocking issue, but I suggest to fix it for leo, as it improves the UX. nominating it to leo?
Status: RESOLVED → REOPENED
blocking-b2g: - → leo?
Resolution: WORKSFORME → ---
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → arthur.chen
Assignee | ||
Comment 10•11 years ago
|
||
Etienne, the change is based on comment 6. Please help review it, thanks!
Attachment #758431 -
Flags: review?(etienne)
Comment 11•11 years ago
|
||
Comment on attachment 758431 [details] Link to https://github.com/mozilla-b2g/gaia/pull/10206 Commented on github, should be a quick fix :)
Attachment #758431 -
Flags: review?(etienne)
Assignee | ||
Comment 12•11 years ago
|
||
Comment on attachment 758431 [details] Link to https://github.com/mozilla-b2g/gaia/pull/10206 Thanks for reviewing! Please check my reply in github.
Attachment #758431 -
Flags: review?(etienne)
Comment 13•11 years ago
|
||
Comment on attachment 758431 [details] Link to https://github.com/mozilla-b2g/gaia/pull/10206 r=me (17f026ac9f75bdfae81d379d021a9e9a85bae09b) Thanks!
Attachment #758431 -
Flags: review?(etienne) → review+
Assignee | ||
Comment 14•11 years ago
|
||
master: https://github.com/mozilla-b2g/gaia/commit/a1f8ab56c638bbbbb9d3b47c56f2c6a344dfdb42
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 15•11 years ago
|
||
Uplifted a1f8ab56c638bbbbb9d3b47c56f2c6a344dfdb42 to: v1-train: f1b765fd98ae40865862e0b89fc66f77be5a6e02
You need to log in
before you can comment on or make changes to this bug.
Description
•