The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Talk:Adaptations/libhybris/Install SailfishOS for fp2
(Created page with "== Bug tracking == The current text about reporting bugs related to hardware (which I assume is everything FP2 specific) is "Problems which depend on hardware: at the Nemo Mo...") |
(→Upgrading alpha1 → alpha2: new section) |
||
| Line 5: | Line 5: | ||
The links lead to the Bugzilla at https://bugs.nemomobile.org, where 45 porting bugs currently seem to be reported, but nothing related to FP2. In the page header is a message: "ANNOUNCEMENT: Nemo Middleware is moving to Mer. File all MW bugs under [https://bugs.merproject.org/describecomponents.cgi?product=Mer%20Core http://bugs.merproject.org - Mer Core]", but I can't find anything FP2 related on that Bugzilla either. Where should they be reported? I have a list of things to report, but would prefer to see some other FP2 bugs reported first to get it confirmed that I add them at the right place. The closest I have found so far is the list in this wiki page. --[[User:Luen|Luen]] ([[User talk:Luen|talk]]) 07:21, 14 June 2016 (UTC) | The links lead to the Bugzilla at https://bugs.nemomobile.org, where 45 porting bugs currently seem to be reported, but nothing related to FP2. In the page header is a message: "ANNOUNCEMENT: Nemo Middleware is moving to Mer. File all MW bugs under [https://bugs.merproject.org/describecomponents.cgi?product=Mer%20Core http://bugs.merproject.org - Mer Core]", but I can't find anything FP2 related on that Bugzilla either. Where should they be reported? I have a list of things to report, but would prefer to see some other FP2 bugs reported first to get it confirmed that I add them at the right place. The closest I have found so far is the list in this wiki page. --[[User:Luen|Luen]] ([[User talk:Luen|talk]]) 07:21, 14 June 2016 (UTC) | ||
| + | |||
| + | == Upgrading alpha1 → alpha2 == | ||
| + | |||
| + | I first tried the OTA upgrade, but after flashing system.img and rebooting, I couldn't unlock the phone. It didn't accept my lock code, so it got permanently locked. Fortunately I had taken backup of the most important stuff before, so I flashed the rest of the images as well. Feels at least good to have a fresh install. The only thing I can think of that not was according to the instructions was that I did't use fastboot to reboot the first time (I instead shut down by holding the power button). Conclusion: as a precaution, disable the lock code before trying the OTA upgrade. --[[User:Luen|Luen]] ([[User talk:Luen|talk]]) 23:26, 9 August 2016 (UTC) | ||
Latest revision as of 23:26, 9 August 2016
[edit] Bug tracking
The current text about reporting bugs related to hardware (which I assume is everything FP2 specific) is
"Problems which depend on hardware: at the Nemo Mobile Project: search existing http://bit.ly/port-bugs; add new http://bit.ly/port-new-bug."
The links lead to the Bugzilla at https://bugs.nemomobile.org, where 45 porting bugs currently seem to be reported, but nothing related to FP2. In the page header is a message: "ANNOUNCEMENT: Nemo Middleware is moving to Mer. File all MW bugs under http://bugs.merproject.org - Mer Core", but I can't find anything FP2 related on that Bugzilla either. Where should they be reported? I have a list of things to report, but would prefer to see some other FP2 bugs reported first to get it confirmed that I add them at the right place. The closest I have found so far is the list in this wiki page. --Luen (talk) 07:21, 14 June 2016 (UTC)
[edit] Upgrading alpha1 → alpha2
I first tried the OTA upgrade, but after flashing system.img and rebooting, I couldn't unlock the phone. It didn't accept my lock code, so it got permanently locked. Fortunately I had taken backup of the most important stuff before, so I flashed the rest of the images as well. Feels at least good to have a fresh install. The only thing I can think of that not was according to the instructions was that I did't use fastboot to reboot the first time (I instead shut down by holding the power button). Conclusion: as a precaution, disable the lock code before trying the OTA upgrade. --Luen (talk) 23:26, 9 August 2016 (UTC)
