Yup saw the latest on merproject but didn’t change that one. I thought it was jolla store that asked for user/password but I may have looked wrong.
Anyway upgraded now to latest_armv7hl repo. Thanks for clarify.
Btw. I have found some issues with BT on FP2 SFOS (all versions). If headset is disconnecting (when go out of range) I sometimes have to re-pair headset? Anyone seen similar issues?
I want to update to the latest_armv7hl but there is a problem with the repositories.
The adaption0 and extra repositories are correct, but there is a problem with the apps, hotfix and jolla repository.
What I can see is that with the adaptation0 you are in the testing repo; for latest versions you need to change to the devel repo.
See mal’s post, 2 posts above yours.
I just switched back to Open OS yesterday, so I can’t check, but I am pretty sure that I had these in the releases.jolla repos as well and no problems to update. Latest version I had installed was 2.0.4.13.
I only changed the adaption0 & extra.
Did you update the repos after the change (ssu ur) before initiating the update (version --dup)?
I’m sorry, but if the update to 2.0.2.48 worked great, I can’t do the update to the 2.0.4.14 version because they ask me my password. I read all your posts above but I don’t really understand…
I tried to change adaptation0 to http://repo.merproject.org/obs/nemo:/devel/hw:/fairphone:/fp2-sibon/sailfish_latest_armv7hl/, but it didn’t happen (with ssu ar adapation0 http://repo.merproject.org/obs/nemo:/devel/hw:/fairphone:/fp2-sibon/sailfish_latest_armv7hl/ wich I believe is the command to do so, but there’s no man pages). The same for the extra repo (with …/common/sailfish_latest_armv7hl/).
you need to run the sed-command after each software-update, because it will always resetted back to the Jolla-Settings (Jolla adaptation0) repository which we can’t use on FP2. Until we get official Sailfish OS Support.
is it me or is the orientation sensor is completely broken in 2.0.4 release? Phone is not switching to landscape mode and flip-to-silent feature is not working either =(
A quick question: How much time does it take to install the outdated and required Fairphone-Open-version to get the possibilty for installing Sailfish OS subsequent?
fastboot devices (checking if the phone is in fastboot-mode)
fastboot -w (erasing the cache and userdata-files)
fastboot flash userdata files/userdata.img (flashing userdata.img)
fastboot flash boot files/boot.img (flashing boot.img)
Everything worked fine until now, but the next step seems to cause some problems:
fastboot reboot
Since the reboot-command, I’m already waiting around 5 minutes for a change of the display-signal. Unfortunately, the bootup-screen with “Fairphone - powered by android” is still shown without any operating-system-information…
Is it usual to wait such a long time? I thought that first bootup into Fairphone-Open should be more quick? I’m asking, because I still want to install Sailfish OS afterwards…
If you are trying change the Android version you also need to flash the system.img from the android fastboot zip. Actually that system.img is the only thing needed before installing Sailfish. If you are planning on updating to latest Sailfish right after that you can just install the latest Open Source version of Fairphone Android and then install Sailfish and update it via the instructions earlier in this thread. In case you use the latest Android version I suggest you install also the recovery.img included in the Android zip after which you can install Sailfish OTA zip from the recovery instead of using fastboot