Who is the maintainer – mikeioannina (as mentioned in Info about FP4 | LineageOS Wiki)? Would I be able to contact him to sort this out (and how)?
If 4–5 releases means they’re anticipating a release of lineage-20 in 4–5 weeks, I can put the FP4 in a drawer and hope the OnePlus One survives until then, and that the data migration from LOS 18 to LOS 20 (skipping LOS 19) will be smooth. But if it takes longer, I would appreciate a LOS 19 build for the FP4 that is signed with official keys, even if it still has some minor glitches – I can live with that for a month or two.
Because all maintainers are volunteers doing this in their free time, and someone happened to love this device enough to bring it up and properly support it.
Releasing 19.1 would mean that Michael “has” to provide support too. It would also mean that he regularly has to switch between both of the versions for testing, assuming he doesn’t own two FP4. That’s probably something he wants to avoid for a couple of weeks.
Funny thing, I’m in the exact same situation here. My OnePlus One faithfully served me for 7-8 years but ultimately I replaced it with a Fairphone 4, and I’d be great to have an official LineageOS build for it.
So, I got my FP4 today and got mmustermann’s LOS build to run on it.
First step is to unlock the bootloader as per the official instructions. You will need the serial number of your device (as reported e.g. by adb devices), as well as the IMEI (more precisely, the IMEI1, as the FP4 is a dual-SIM device).
Steps on the computer are described in a lot of detail there, though only for Windows and MacOS. In fact, it will work on any system which has adb and fastboot set up and working:
Boot the FP4 into the boot loader, while connected to your computer.
Run fastboot flashing unlock.
Follow the instructions on the screen – this will wipe all your data.
When the device reboots, boot into the boot loader again.
Run fastboot flashing unlock_critical.
You can now boot into recovery and install the OS of your choice.
Since LOS18+ no longer includes root functionality, not even as an add-on, you will need to install Magisk for that. The only way this worked for me was via the (deprecated) Custom Recovery install method: download the APK, rename it to .zip and install it as an update using Recovery.
I haven’t gotten around to moving user data yet. Simply restoring a backup, as I did when moving from the Nexus S to the OnePlus One, does not work as TWRP is not yet officially supported on the FP4 (and anyways the FP4 enforces data encryption, which TWRP does not support yet). LineageOS recovery is supported but does not provide data backup/restore functionality. So moving the /data partition over by means of recovery backup/restore is not an option here, I’ll have to figure out something else.
It’s relatively easy. There are even Docker containers, though I never tried those.
It just takes some hours and you need about 250 GB free disk space.
repo sync has finished successfully.
icterid$ source build/envsetup.sh
icterid$ breakfast FP4
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "lineage_FP4".
21:50:03 dumpvars failed with: exit status 1
/usr/bin/env: 'python': No such file or directory
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "lineage_FP4".
21:50:04 dumpvars failed with: exit status 1
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "lineage_FP4".
21:50:04 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_FP4'
** Do you have the right repo manifest?
Hey, I built myself a LineageOS + microg image (used GitHub - lineageos4microg/docker-lineage-cicd: Docker microservice for LineageOS Continuous Integration and Continous Deployment & thanks to max_o I know what manifest to use for the correct proprietary files).
Now I’m unsure if I can flash it without risk due to I currently have /e/ OS with Android Security Patches up to 2022-07-05 installed and don’t want a bricked phone due to the anti rollback mechanism. (I don’t care about losing data.) Does anyone know how I can lookup which security patches my LineageOS build includes (without flashing it)? Or does anyone know if it save to just try it?
(If my build runs fine for me, I can upload it to my server and even provide OTA updates until official builds are available.)
This is great news for me, I’m would also like to use a linageos+microg build, but so far didn’t tried to build it myself (As a consequence, my FP4 is still unused at the moment). It would be really awesome if you could share your build until there are official ones!
Thanks for the pointer to NeoBackup. I have used its predecessor oandbackup so far, but the ability to do batch backups was a good reason to switch over.
As for rooting, well, with an unofficial LOS build I am already messing with stuff that could set my house on fire, get my cat pregnant and whatnot. Magisk is one of my lesser worries; at least it has worked well on my OnePlus One with official LOS18. (The post you linked seems to focus primarily on the stock OS.)
I switched to the FP4 today. NeoBackup did a lot of the heavy lifting for me, but some things need to be done manually:
NeoBackup has issues restoring apps which were first installed on ~Android 5 and before, as the APK path differs. (This will be fixed in the upcoming version, thanks to the NeoBackup team, who were really quick to respond to my bug report.) As a workaround, restore the missing APKs from the backup dir, then restore data with NeoBackup in the usual way. You may need to reconfigure permissions for these apps.
Since I also migrated to a new Android version (11 to 12), migrating data for system apps did not work for all apps. For some it did, for the others I had no choice but set everything manually.
In particular, text messages and call history did not get migrated. SMS Backup/Restore (available on F-Droid) did the trick for me. (Contacts might be the same, if you store them locally.)
Some user apps need extra steps to migrate data:
DAVx⁵: accounts need to be set up from scratch, then recreated.
OpenVPN: profile needs to be set up (or re-imported) from scratch
Signal: delete app data, then transfer the account from the old device
Syncthing will identify itself as the old device. If you want to use both devices in parallel, you will need to delete app data, then set up sync from scratch
The Terminal app, which could be enabled from Developer Settings in LOS18, is no longer available in LOS19. Terminal Emulator for Android (available on F-Droid) is a suitable replacement. UX is so similar you will hardly feel a difference.
Didnt point you to the rooting thread to highlight the risks, but to make you aware about the “how to” as you used the deprecated .zip way…and even if the thread was initially created before any Custom ROM existed and therefore mainly is about FPOS, the “how to” does not change…
I might have found one thing that does not work the way it should: I got a third-party USB-C audio adapter and plugged it in, but the phone still happily plays audio over its speakers, ignoring the external headphones altogether.
As far as Wikipedia is concerned, such devices use a special USB-C mode where analog audio is transferred over the USB data pins. Somehow this does not work for my phone+OS+adapter combination. Either the there is something wrong with the adapter, or the OS fails to detect it and switch over to Audio Adapter Accessory mode.
Has anyone else tried using an analog audio adapter with the FP4 running LOS? Does it work for you?
The description does not mention whether it is a direct analog adapter or has a DAC. However, a USB device monitor on the device does not find any devices, nor does lsusb when I plug the device into my laptop. (Whereas I suspect a device with a built-in DAC would be a regular USB device, correct?)
