I’ll keep that adb root note for now, we can drop it later.
Please after install perform OTA:
ssu release 5.0.0.68
devel-su zypper clean -a
devel-su zypper ref -f
devel-su version --dup
# if above fails, try again
# devel-su version --dup
I am currently on this release and let’s make sure we all test against the same version. Thinking of it, I should have generated images immediately for the latest version. The packaged version was based on the version I had in my SFOS HADK.
Seems to upgrade nicely without faults.
One issue reported, please keep an eye on this: Xperia 1 IV Doubled-input Tochscreen · Issue #60 · sailfishos-sony-nagara/main · GitHub
I wonder if it is due to older SFOS or something else. So, would be good to watch out for it.
And thanks to the one who opened the issue at Github! Let’s keep issues there as it is a bit more organized and we can refer to them from here as a part of general discussion.
I had some non-responsiveness after the first restart - the phone was still attached to the cable to the PC. After that, I disconnected it, slept it, woke it and it hadn’t any more problems, even on cable. I mean - it might happen if you boot, while charging.
Something very strange - I was installing some packages from Storeman and suddenly the vibrator stuck on vibrating and had to restart. No idea how that happened.
Hmm, seems to happen every time it charges.
Might have something to do with my broken reader.
It is rather strange.
To track it, I have the same questions as for the other issue
Please enable logs (Getting logs on Sailfish · sailfishos-sony-nagara/main Wiki · GitHub) and grab them. Maybe we can see something there. But testing on LOS would also help to narrow it down.
Ah, sorry, wrote about two issues in one post - the vibrator was one time issue. the other things below are for something else, which I guess I missed to explain - after locking the phone with the power button, when you press it again to unlock it, sometimes it waits several seconds before doing it. That’s why I think it is connected to the broken reader Also turned out to not be connected to charging. Both things didn’t happen in Lineage. Stock was updated to last.
Do you happen to remember if the vibrator was before SFOS OTA or after?
It would make sense to enable logs and when some issue happens grab them. maybe you could see something odd around the time of event.
I will probably reflash my phone to be on the same version as you are. Haven’t done it for a while and it makes sense to sync it. Maybe there are some issues caused by newer blobs and LOS version.
All reflashed on my device, so I am on the same page as you are.
Now, I have also uploaded bit updated images for LOS and SFOS. SFOS is already on .68 - simplifies the use. Probably new release will come a touch later for SFOS, so no rush in reflashing unless you want to get to the same base.
I observed the delay between pressing power and display turning on after new install. Now, I am using it with double tap 2 wake and such delay disappeared when I enabled it. See Tips in Wiki on how to enable it and try then. I wonder if it is due to luck or it is like that.
would it be possible to install Appsupport binaries from Xperia 10mk5?
No idea. Probably it requires the same Android base and some extras. This port is based on Android 14
I’m not sure the Android base is of big significance, but who knows. I plan to test that in the following days (and buy another license to be fair).
My Xperia 5 IV arrived today. will it now test for a week or so until I will have a look, if I’m able to compile LOS with the documents.
Congratulations! We are now moving already to binary releases. For 1IV CT54 variant builds can be downloaded. I hope that we can push 5IV builds out as well somewhere next week. So, focus on testing and updating to the latest stock 
. timing should match well in this respect.
If it takes a bit longer that’s no problem. My Quintus is running at the moment quite well aside from the already mentioned problems. On the long run I anyway plan to use both phones in parallel.
5.0.0.71 available for 1 IV. We expect that 5 IV will be released during the next week.
The releases are under Releases · sailfishos-sony-nagara/main · GitHub and include a dedicated release for Lineage OS images as well as the first test release for SFOS.
Those who installed earlier builds, please flash this testing release. I couldn’t test it myself as I need to stay on developer builds. The published testing release image should point you to the dedicated end-user release channel at OBS. After flashing and configuring the build, it would be great to see your ssu lr output. Then I can check if all settings are working as they should.
Currently we are targeting a release model that will allow you to easily OTA update in the future, such as moving to 5.1 releases. Hopefully your tests will pass with ssu and the phone works as expected.
Note that the main repository README has been updated and lists the models and phones that we expect to be able to support with this port.
Do I understand that correct. When the image for the 5 IV is released I don’t have to build LOS on my own anymore?
You guys rock! This is incredible speed.
When my device is greeting me with Sailfish OS for the first time, I would like to say thank you. I know how to donate to @rinigus, but this ports are team work if I understood you right. So is there a donation possibility for @vlagged as well.
Yes, you will not have to build images yourself. It took some time to figure out the distribution model, but I hope it will work well.
What a great achievement! Great work, perhaps I one day stumble upon one of these phones 
Great news! now “all that’s left” is to do the same for 10IV and 10V and Jolla can release AAS as a licensed add-on and we can move on without buggy blobs 