Closed Bug 1118064 Opened 10 years ago Closed 7 years ago

[Data Connection] After an OTA update to the latest build on Base v18D, Data Connection is broken and doesn't provide Internet

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-, b2g-v2.1 unaffected, b2g-v2.2 affected)

RESOLVED WONTFIX
blocking-b2g -
Tracking Status
b2g-v2.1 --- unaffected
b2g-v2.2 --- affected

People

(Reporter: onelson, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [2.2-Daily-Testing])

Attachments

(1 file)

Description: While on Base Image v18D, when a user updates their phone via the OTA update process to the latest build, data connection will break and not provide internet access to any application. OTA performed from: 20141231010205 from nightly PreReq: * Starting build to OTA from must contain bug 1114955 Repro Steps: 0) Flash a Flame device to a BuildID prior to 20150105010205 1) Download the OTA update to BuildID: 20150105010205 2) Once updated, establish Data Connection and disable Wi-Fi 3) Perform Internet-Oriented Tasks [MMS, Email, Browser, Hotspot]. 4) Observe results. Actual: Phone behaves as if no Internet connection is enabled. Expected: Phone has usable Internet Connection with Data enabled. Environmental Variables: ---------------------------------------------- Device: Flame 2.2 BuildID: 20150105010205 Gaia: c2bf20d23851d5fda9f8f0ef0267db5f49152376 Gecko: 636498d041b5 Gonk: 48835395daa6a49b281db62c50805bd6ca24077e Version: 37.0a1 (2.2) Firmware: V18D & v188-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 ---------------------------------------------- Repro frequency: 5/5 See attached: video- http://youtu.be/lhZfO4bT4lk log
This issue DOES NOT REPRO on flame 2.1 devices: Results: Phone has usable Internet Connection with Data enabled. Environmental Variables: ---------------------------------------------- Device: Flame 2.1 BuildID: 20150105001204 Gaia: 73be51f998031f06db0cd660c0e388fa621c9f4c Gecko: 05dd053f1d90 Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76 Version: 34.0 (2.1) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 ----------------------------------------------
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Keywords: regression
Whiteboard: [2.2-Daily-Testing]
blocking-b2g: --- → 2.2?
Component: Gaia::System → RIL
Shouldn't this be a smoketest blocker?
You have to start with a build that reproduces bug 1114955. If you OTA to a build that has the commit for bug 1114955 you reproduce this issue, if you full flash to that build instead, you do not reproduce this issue. It's a bug of a bug, but I think it reveals another potential issue with OTA.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
When you start a build that reproduces bug 1114955, the APN doesn't be initialized in database correctly during first boot up. Then you OTA to a build that contains the fix, but the apn initialization process won't run again after OTA unless you swap a different sim card. So the apn in database is still incorrect after OTA. I think that is why you still are unable to establish data connection after OTA, but full flash doesn't have issue.
triage: this is rather a non-common case to end users, since we're not expecting many to get the build w/o bug 1114955.
blocking-b2g: 2.2? → -
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.

Attachment

General

Created:
Updated:
Size: