Closed
Bug 830597
Opened 11 years ago
Closed 11 years ago
Update notification for an app (e.g. Maps, in my case) over cell connection warns me that it "will block incoming calls" -- pretty sure that's incorrect...?
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: dholbert, Unassigned)
Details
(Keywords: b2g-testdriver, unagi)
STR: 1. Be running an outdated version of some app, so that you've got an app update available. (not sure how to get in that state, but I'm in it right now) 2. Ensure WiFi is disabled, and you've got a SIM with a data plan. 3. Pull down status menu, and tap the "1 update available" ACTUAL RESULTS: An app-update notification appears, saying > 1 Update Available > Maps [x] (or whatever app you've got updates for) > > Wi-Fi unavailable. Updating over current > connection will block incoming calls, > and may incur additional charges. I'm pretty sure that statement about "will block incoming calls" is incorrect, right? Do updates to individual apps really block incoming calls? Please tell me they don't. :)
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
No longer blocks: b2g-app-updates
Component: Gaia::System → Gaia
Summary: Update notification for an app (Maps) over cell connection tells me that it will "block incoming calls" → Update notification for an app (e.g. Maps, in my case) over cell connection warns me that it "will block incoming calls" -- pretty sure that's incorrect...?
(In reply to Daniel Holbert [:dholbert] from comment #0) > I'm pretty sure that statement about "will block incoming calls" is > incorrect, right? Do updates to individual apps really block incoming > calls? Please tell me they don't. :) This is the case for many EDGE networks, especially in v1 target markets. It may not be the case for your US carrier.
Flags: needinfo?(jcarpenter)
Updated•11 years ago
|
Blocks: b2g-app-updates
Component: Gaia → Gaia::System
Reporter | ||
Comment 3•11 years ago
|
||
Perhaps we should change "will block" to "may block" then?
Updated•11 years ago
|
No longer blocks: b2g-app-updates
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Comment 5•11 years ago
|
||
Current r+ patch for bug 830286 does not change this text. It adds a new text and add some logic. This but is another bug so let's keep it opened please. Daniel> I think that while in 2G (GPRS/Edge) the calls are blocked; in 3G (UMTS/HSDPA/etc) they are not. We can know this with |navigator.mozMobileConnection.data.type| [1] so we may change the text depending on the connection type. Yet for v1 a small text change ("may" instead of "will") might be enough. [1] https://mxr.mozilla.org/mozilla-central/source/dom/network/interfaces/nsIDOMMobileConnection.idl#349
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Updated•11 years ago
|
Blocks: b2g-app-updates
Comment 6•11 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #5) > We can know this with |navigator.mozMobileConnection.data.type| [1] so we > may change the text depending on the connection type. We do.
Comment 7•11 years ago
|
||
ok so it's worksforme then. I've just checked that when I'm on 3G I don't have the same text, as etienne's saying.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → WORKSFORME
Updated•11 years ago
|
No longer blocks: b2g-app-updates
You need to log in
before you can comment on or make changes to this bug.
Description
•