I believe this is the issue: Animations are faster on 120/144Hz screen · Issue #9 · sailfishos/issue-tracker · GitHub
1 Like
Another report - SMS sending through VoLTE on Yettel Bulgaria is not working, but not really an issue, since it didn’t work on Xperia 10 III too. 
1 Like
VoLTE implementation in this port is different from the other ports (official or unofficial). You can try to record journal as described in our port WIKI while sending SMS.
In addition, do you happen to know whether the same phone can send SMS in this network
1 Like
I’ll try tonight.
It can send SMS normally if I disable VoLTE (in Sailfish), didn’t test in Android.
Just received an SOG09, returning it 
Would appreciate a EU seller for the XQ-CQ54 / XQ-CQ72 in PM as well if possible, thanks!
SOG09 seems to be spreading just like the pestilence. As I’m unsure if it is forum spirit to link shops. I will do per PM.
1 Like
OK guys had some time today. After I tested everything on the device with stock android, I flashed Lineage OS. Instructions are good and don’t leave any questions open. Lineage is running. Do I have to test everything again, before flashing Sailfish, or is it enough, that I tested hardware on stock Android?
2 Likes
Test a bit. It should be fine, but makes sense to check if VoLTE is working, BT, GPS, camera. But as 5IV will still have to be recompiled, images updated, there is probably no need for testing extensively
2 Likes
Thought I give it a try, but I’m stuck at step 10:
10. Flash Sailfish OS Images
Flash the Sailfish OS boot images in fastbootD mode:
fastboot flash vendor_boot vendor_boot.img
Which vendor_boot.img? In the Sailfish download there is none. There is hybris-boot.img and the packed SF filesystem, but I don’t see a vendor_boot.img.
I downloaded from here:
this file
sailfishos-Xperia-5-IV-XQCQ54-5.0.0.71-testing.zip
Then that image was forgotten by @vlagged when 5IV was packaged. I can try to pack it myself this weekend. Sorry, before that it would be a bit complicated to do.
4 Likes
Ok, then I just shut down my phone and wait until the image is available?
Thank you @rinigus for your lightning fast answer and your support!
3 Likes
best if could flash back lineage boot and vendor_boot. after that you can decide, either make factory reset in recovery and go back to lineage or shutdown.
otherwise you would be stuck with a state where recovery is not available until you flash boot and vendor_boot from lineage.
2 Likes
Sorry, I don’t know how that happened - I will upload it now, will give a slight different name to the zip
L.E. Done, image has testing-2 suffix
2 Likes
That was quick, guys you rock. I have just sent some beers to rinigus. Is there a donation possibility for you as well?
3 Likes
I am not currently accepting donations (maybe that will change in the future).
But first let’s see if the build works on your device 
3 Likes
Sailfish is up and running. Now will make some tests.
I got you right, that it makes no sense to setup the hole device, because I have to flash it again, when the build has ripened a bit?
Regarding the instructions, I would change point six a bit:
It is:
6. Extract Sailfish OS
Open an ADB shell and extract the Sailfish OS files:
adb shell
and extract the Sailfish OS files
Then To do so, run these commands on the device:
mkdir -p /data/.stowaways/sailfishos tar --numeric-owner -xvzf /data/sailfishos-xqct54-release-5.0.0.68.tar.gz -C /data/.stowaways/sailfishos
3 Likes
Congrats! And thanks for testing. (I have applied your docs suggestion too).
That would be a partial re-flash of the lineage partitions and maybe kernel/boot bits. Consider it equivalent to a security update. No need to lose the userdata partition, so you can setup the device, if it passes your tests.
I know, I still have this tech debt for 5 IV (that rinigus has already done for 1 IV) but also have too few free time.
3 Likes
A more detailed report will follow. Anyway, here are my first observations - take them with a bit of salt, I haven’t had that much time for intensive testing.
The port is quite feature complete. Yes there are still some things missing, but NO showstopper for me. I even haven’t tested everything.
Battery Life is outstanding. Especially regarding standby time. I never had a Sailfish device before which had such a brilliant battery time. 
Camera is performing just like expected, much worse than on Android. Anyway for a device running SF it’s quite good - hopes are high that at one point Camera2 API will bring us more possibilities.
Screen is bright and nice, even though I’m now somehow adjusted a bit on the large Volla Quintus display.
The downsides:
I had one freeze and two unexpected reboots so far. I have to have an eye on that - Today it was stable.
Switching on the device takes a bit. I don’t mean booting, but just waking it up usually takes around three seconds. Maybe the reason is that it is sleeping that deep and therefore has this great battery time. If so, please leave it like that. It’s a bit irritating, but I prefer to have a great battery life.
7 Likes
For switching on: try to enable fingerprint and double tap.
Re camera: great that you made such comparison. In part, it maybe related to issue32, but there is no proof.
Fingerprint is enabled and works VERY reliable. But doubletap doesn’t change much. I double tap and then I need a bit of patience. I’m always thinking my taps were not recognized and at that moment when I decide to tap again the display decides to show it’s beauty.
I had another freeze in between. It’s not a proper freeze, the touchscreen simply accepts no input. It happened at the same time as the last time. directly after unlocking the device. So maybe it has to do with the delayed switching on of the device.
Regarding the camera I can’t say much. At the moment I’m not overwhelmed from it, but definitely not unhappy.
1 Like