1160329 - [Homescreen][OTA] Broken Icons will remain broken after an OTA.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Homescreen, defect)

Description

[Martin Shuman [:Marty]]

Attachment: logcat-OTA-Icon.txt

Description:
If the user has a broken homescreen icon due to an issue in the build, when they OTA to a later build without that issue, the broken rocketship icon will persist.

For example, the broken rocketship icons for Marketplace and Packaged apps from bug 1159299 will remain broken after running an OTA, despite the fact that the issue no longer occurs on later builds.  The user must perform a system factory reset in order to fix the issue.

Repro Steps:
1) Update a Flame to 20150429010205. Note the broken Marketplace icon on the homescreen.
2) Connect to a WiFi or Data network
3) Wait for an OTA to become available.
4) Download and install the OTA

Actual:
The Marketplace icon remains broken after performing the OTA.

Expected:
Broken icons do not remain broken after performing an OTA.

Environmental Variables:
Device: Flame 3.0
Build ID: 20150430010201
Gaia: db8ea705c0fd1b1684807f5a8e837bb9a36a6f96
Gecko: 4b9b12c248dc
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 40.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0

Repro frequency: 5/5
See attached: logcat

Comment 1

[Peter Bylenga [:PBylenga]]

We're handling this type of error in such a way that OTA can't recover from without a factory reset.

Use Case:
1. User OTA's to a build with a bug where packaged icons display as rocketships and downloads a few packaged apps.
2. User OTA's to a build without the bug but all icons remain as rocketships even though additional downloads display correctly.  Reboot of phone doesn't recover.

Perhaps doing an icon refresh at boot if the asset we have to display is the rocketship?

NI Component owner for nomination decision and assignment.

Comment 2

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I'm not sure we can do anything about the situation either codewise if they started off on a bad build; the basic situation is, we don't want them on that bad build in the first place.

So, I am partial to say that this is either a won't fix/invalid...

dhylands, can we get your input please?

Comment 3

[Dave Hylands [:dhylands]]

Not sure what you're asking for.

I looked at the log. It shows that no update occurred because the network was unavailable.

OTA, in and of itself, can't "fix" anything. It's just a file transfer mechanism, for updating gecko.

If the homescreen is screwed up because of a database setting, then by and large, OTA isn't going to fix anything. OTA doesn't touch the database, or user profile, or anything in /data.

Comment 4

[Kevin Grandon :kgrandon]

Mass update: Resolve wontfix all issues with legacy homescreens.

As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.