Should I reflash the persist partition, if I decide to go stock way? And which spc code is ours?
If the issue was with stock already then no extra testing is needed.
I will try to push SFOS release out within 1-2 days for 1iv and then we can start testing flashing it. Some docs maybe have to be updated as well.
SPC code?
3 Likes
The code of the model in XperiFirm.
Wait, I just learned that both 1IV and 5IV has 120Hz screen. I have thought that SailfishOS doesnât currently support anything other than 60Hz (Animations are faster on 120/144Hz screen ¡ Issue #9 ¡ sailfishos/issue-tracker ¡ GitHub)!? But apparently it works normally?
I can confirm fingerprint works on Lineage for me (I just compiled and flashed it)
4 Likes
@rinigus now when there is a port of Lineage for Nagara, does it mean that we can update the Android version in the future and get new security patches / features and an updated kernel version?
Yeah, contacted the seller and he confirmed mine was broken before, he just forgot to mention it. 
Thatâs a code that is probably in your About or System box. Something like pdx223 and XQ-CT54 (thatâs for me).
On this device it is set to 60hz by default and can be bumped higher. I havenât looked into when and how to bump. 60hz is fine for me.
Maybe. Iâll try Github first - makes more sense than to register there. But it seems like a good option too, thanks!
kernel updates are not an issue at all. android version, no - as this is basically a new (or updated) port. in general, it is rare when SFOS port updates its base. exception was Sony Tama as we had better HW support on newer base. as hardware is working fine with LOS21, I donât see a reason why we should jump from it.
re security patches: we mainly live on SFOS side of the things, so that is not a major issue. if we find that those smaller bits of android that we use are with some security issues that can be patched, we can get back to that.
4 Likes
There are four XQ-CT54 models there. 
Anyway, my guess is Customized EU/UK version, as one other was EE/UK and the rest were operator locked.
yes, choose that one. thatâs ROM versions, device is probably the same. but note that when I get ready with SFOS release files, you will have to flash them on top of lineage, not stock.
1 Like
Yeah, I know that. Just wanted to make sure I have one rom ready if XperiFirm goes south again.
Great idea!
I am working now on release scripts, may take a bit of time. Had to update configs to be able to make clean builds.
4 Likes
Got it all built and working yesterday evening, thanks for all your work on this port @rinigus! Iâve been using it for the past day and so far everything has been working great!
6 Likes
Status update: scripts and docs are ready. I just have to proofread all and then upload archives to github release. 1IV will be uploaded first and I hope @vlagged will soon follow with 5iv. This will be developer build for testing. Next we will have to setup repositories for proper releases at OBS and make a release using that.
18 Likes
The first images are uploaded under Release Testing release ¡ sailfishos-sony-nagara/main ¡ GitHub
Please follow the installation guide in our Wiki pages.
I will rebuild Lineage OS again for Xperia 1IV and, if needed, for Xperia 5IV.
Right now, images were uploaded for Xperia 1IV, PDX223, model XQ-CT54. It may work with XQ-CT72 as well, possibly with single SIM.
Please consider the current state as opened for testing. It would be good if the images and associated documentation are tested. Let me know, regardless
9 Likes
According to the wiki, I should change to adb root after restarting to recovery. However I can only do it before that. In recovery it goes like this:
Okay, there is âEnable adbâ option in Advanced that enables adb root directly.
1 Like
Other than that, seems to install and works! Thanks a ton!
3 Likes
Thank you very much for going through it! I have added it to the wiki.
3 Likes
Not sure about the adb root step after enabling it in Advanced - it maybe is needed it if you didnât run adb root in Android before restarting to recovery, but if you did - it shouldnât be (probably, at least it wasnât for me). Probably because the adb root is a flag of adb that switches the PC server in that mode and if you restart the device, it still stays in that mode.