To my knowledge the wiki is current, i.e. you should do as it says. In that case: " Requires Fairphone Opensource OS 18.04 (or Fairphone OS 18.04), not tested on other releases."
But does that mean that it doesn’t work with other releases or does that mean it should/could work with other releases but it’s not tested yet.
Just try it out and report back here.
What could go wrong?
Worst case you flash Fairphone Opensource OS 18.04 afterwards and start over.
It might work with other quite recent Android 6 based FP Open OS releases. It certainly won’t work with Android 7 based releases like 19.02. Instructions tell how to get back to Android 6 base.
I think 18.04 was the last Android 6 release. So I’d say just use that exact version
Yes, 18.04 was the last Android 6 release and that is the reason why it’s still used as base for Sailfish OS.
…and it worked for me, I am now on the FP2 running on Sailfish OS, thank you, mal! I will hand it over tomorrow.
I’m currently running Ubuntu Touch 16.04 OTA-8 on the Fairphone and it works surprisingly well. So I’ll postpone my Sailfish OS installation a bit. As far as I know, the Sailfish source code still isn’t available, right?
Which source code? Sailfish is mostly open source, but partly closed source, just like Nokia’s Maemo and successors have always been. What you’re using is a community edition. It lacks features, most notably Alien Dalvik (the Android emulation layer). Without that, it is IMO difficult to use the device as your sole, primary smartphone device but YMMV.
See also e.g. https://en.wikipedia.org/wiki/Sailfish_OS#Community_enthusiasts’_ports_to_devices_from_other_vendors
The interface source code is closed right? Or where can I find it?
I used Firefox OS for years as my primary device, and I’m now running Ubuntu Touch. I’m totally fine with the fact that I can’t run APKs. The web is the platform anyway
Anyone using devel repos can now test the 18.04 modem partition on their device after updating to latest versions of packages from devel repos. I have enabled on-demand use of proximity sensor in devel and based on my testing for more than a week the battery life seems good now and we can stop using the old firmware. I’ll include the change to next Sailfish OS release for FP2 (3.0.2.x) when that is ready.
Testing of Sailfish OS 188.8.131.52 for FP2 has gone as planned without any regressions found so far. If no issues are found then I will make the release later this week. The release will still be based on FP Open OS 18.04 as before due to the lack of Android 7 sources but at least the proximity sensor issue is fixed and everyone can update to 18.04 modem partition after updating to Sailfish OS 184.108.40.206 release for FP2. I will give detailed instructions how to do that in update instructions.
I did some preliminary testing of Sailfish OS 220.127.116.11 on FP2 and so far everything is working the same as before. Before releasing the new version I’ll try to fix the randomly occurring camera issue when updating or installing Sailfish OS. Also I’m thinking about making a proximity sensor calibration tool for Sailfish OS but not sure if I will make it before this release yet.
first I have to say thank you a lot four your Sailfish OS (SFOS) port for our FP2! I was using UT since September on my FP2 and I really like UT but in daily usage I finally got too annoyed by the instability from UT on our FP2 (frequent crashes of Unity 8/GUI during typing of messages etc, slow or not existing hardware support (camera, LED light, FM radio).
As more I was really positively suprised by the technical quality of your SFOS port on the phone! It is really smooth and stable, not worse than the official Android ROMs and fully working hardware support.
I like SFOS as a system as well, however it is a bit sad that SFOS and UT don’t work together more in the apps. There are some really good SFOS apps (I like for example gpodder) but many are very old and unsupported. On the FP2 we don’t have AlienDalvik and cannot move to Android apps as alternative. Especially the browser is much weaker (slower, lagging and sometimes freezing) than the UT browser. I really miss a Signal app now (the only one existing is abandonded and cannot be installed anymore in Storeman). Finding an Youtube App was also kind of difficult among all the abandonded and forked and forked and abbandonded old YT apps on SFOS, until I got the hint of using ‘LLs vPlayer’ in the UT Telegram group.
I will have a look on SFOS a bit more but I consider maybe just going back to an Android Open Source Project based ROM (Fairphone Open). There I can use the Android apps without an emulation layer and don’t bother with Google.