Closed
Bug 1047972
Opened 12 years ago
Closed 12 years ago
On 2.0, still using the old home screen?
Categories
(Firefox OS Graveyard :: Gaia::Homescreen, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: freddy, Unassigned)
Details
I updated my Flame to 2.0 (base image v123) and restored a previous profile (both manually).
I still get the "classical" pre 2.0 homescreen that scrolls to the right.
I couldn't find a setting that allows me to switch to the new homescreen, that scrolls vertically.
Comment 1•12 years ago
|
||
Hey Fredrik -
Which scripts did you use to backup/restore your profile? This is not an upgrade path that we tested, we normally only check on OTA/FOTA updates. My guess is that the scripts you're using have some setting for the homescreen that's overriding the default.
| Reporter | ||
Comment 2•12 years ago
|
||
Yes, this is quite possible. I'm using the backup/restore scripts from TWQA: https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/backup_restore_profile.sh
| Reporter | ||
Comment 3•12 years ago
|
||
Kevin, can you suggest a hack to get the homescreen reset without having to reset my whole profile?
Comment 4•12 years ago
|
||
(In reply to Frederik Braun [:freddyb] from comment #3)
> Kevin, can you suggest a hack to get the homescreen reset without having to
> reset my whole profile?
Hey Freddy - I guess what's happening is that you have the old homescreen setting sitting around. We either need to spin some code to upgrade setting databases after a profile restore, or you should allow an OTA update to a new version without a restore after perhaps. The OTA update is what actually triggers the settings update, and I guess restoring the profile currently prevents that. I would strongly suggest that we have some way to trigger settings upgrades after a profile restore, but that just needs to get prioritized and worked on. I'm also adding :dbaron here as I believe he was running into the same problem.
To fix it, we'll need to update a setting, specifically the homescreen.manifestURL setting. You'll want to set this to: app://verticalhome.gaiamobile.org/manifest.webapp
TBH I'm not sure what the easiest way to update settings is. If you have access to install the system app, or inspect it with the app manager, we can run a simple javascript snippet which will set the setting:
navigator.mozSettings.createLock().set({
'homescreen.manifestURL': 'app://verticalhome.gaiamobile.org/manifest.webapp'
});
| Reporter | ||
Comment 5•12 years ago
|
||
Yeah, this did the trick!
Detailed steps:
1) Enable debugging in the Developer settings ("ADB and developer tools")
2) Allow debugging system apps (danger mode :))
> adb shell "cd /data/b2g/mozilla/*.default && echo 'user_pref(\"devtools.debugger.forbid-certified-apps\", false);' >> prefs.js"
3) Restart b2g
> adb shell stop b2g && adb shell start b2g
4) Connect App Manager to the phone and debug the system app. Use the code snippet from comment 4 to change the homescreen setting
5) Disable debugging system apps
> adb shell "cd /data/b2g/mozilla/*.default && echo 'user_pref(\"devtools.debugger.forbid-certified-apps\", true);' >> prefs.js"
6) Restart again
> adb shell stop b2g && adb shell start b2g
7) Disable debugging in the Developer settings
Kevin, what do you suggest for this bug? Resolved/Worksforme?
Comment 6•12 years ago
|
||
(In reply to Frederik Braun [:freddyb] from comment #5)
> Kevin, what do you suggest for this bug? Resolved/Worksforme?
Sounds good to me. I think there is a larger problem of currently not being able to migrate settings after a profile restore, but I feel that's outside the scope of this bug. Perhaps it would make a good dev-b2g or dev-gaia discussion.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•