Sailfish OS for Sony Xperia 1 II and 5 II

Sailfish OS 4.5.0.24 for Sony Xperia 1 II and 5 II

These release notes cover Sailfish OS 4.5.0.24 for the following devices:

  • Sony Xperia 1 II (XQ-AT51, XQ-AT52)
  • Sony Xperia 5 II (XQ-AS52)

Intro

This is the first public release of this port. The port existed before it’s public release for quite long, it was developed along the Xperia 10 III port.
I’m using it ever since then. However the testing, polishing and subsequent release took quite some time because of my personal situation and the work on other items such as the the update discovery service Cosu.

The highlights of this release are:

  • No notable highlights here exceptthat the device works fully except the known issues
    noted below and the issues where community ports don’t have
    the access VoLTE packages used by Jolla’s Sony adaptations.

Functionality

The devices have the same functionality level as the Xperia 10 III port made by Jolla, except in areas such as VoLTE where public packages are missing or in relation to Sailfish X features which are (currently) unavailable.
Some features such as camera support might be different as for the nature of the difference in platform between the basis of
the two ports (also called boards).

Known issues

  • sonyxperiadev/bug_tracker#756
    When trying to record a video the the camera app freezes and has to be forcefully closed.
    The bug is caused by an issue inside the camera server used by the port or the adaptation camera configuration.
    No workarounds for this issue except to avoid recording videos :confused:.

  • sonyxperiadev/bug_tracker#771
    The recording quality when not using the speakerphone or when calling with the phone to the ear is
    bad that it is hard to hear the user of the device.
    When using the speakerphone the quality of the microphone is slightly better but can
    cause echos.
    A workaround is a wired or wireless headset.

Project

The Github project that contains this port and all other ports from this project can be found here:

Project Updates

As explained above there’s now a separate changelog for project wide updates which can be found down below:

The changelog file about the project updates can be found down below:

About

The goal of this project is to port additional Sony devices on top of Jolla’s existing adaptations while staying as close as possible to the existing ports and contributing back to the upstream where possible.

Most of the changes from Jolla ports are adopted in both directions since the issues that one port has usually apply to the sister device of the same generation (e.g. Xperia 10 III → Xperia 1/5 II).
This is the reason why changes from Jolla’s port end up in the changelog for these port,
in many cases because they also affect the specific port but not always.

Where possible changes that were done for this port go back to the Mer-Hybris repositories such as the kernel or droid repositories.

The project is open for anyone that wishes to port additional Sony devices to Sailfish OS. Feel free to suggest new features, provide bug reports or to contribute.

Report bugs

Bugs can be opened in the bug repository linked below:

Download

Flashing

To install Sailfish OS on your device please follow the install instructs in the flashing-readme.txt file included in the archive or read the offical flashing instructions for either the Xperia 10 II or Xperia 10 III:

Just make sure to download the software binaries for your device instead of the ones mentioned in the instructions:

Updating your device

To update your device please follow the update instructions in INSTALL.org:
INSTALL.org/Updating your device

Changelog

Release notes of previous releases:

The release notes of previous releases can be found in this folder:

24 Likes

Hey there. I just came across a Xperia 1 II, which my son used for some time with /e/OS. Since he got a new phone and my XA2 has a cracked screen glass which only holds together by transparent tape, I thought I give it a try with SailfishOS. Always wanted to have a device to experiment with a community build.

At first I mixed up the model, because recovery of /e/OS told me it was AT52 - must be a bug there. Well, I didn’t get passed the Sailfish Logo because of that and had to start over getting everything for AT51.

I was too lazy to get an Android 11 image so I went with A 12. I had some issues when using the flashing script, it got stuck while flashing oem. But starting over and typing the flashing commands one by one myself it finally booted up fine. I recall that somewhere in the process I had it running but without WLAN. Maybe that was, when I used AOSP 11 as in the instructions while being based on A12. But in the end having oem on AOSP 12 everything seems to work. Well almost: The mentioned but with video recoring is still present. And sometimes the login after starting up the phone after decryption doesn’t show and I have to press the button once or twice.

So now I have to thing to find out:

First, maybe since I am into experimenting already, I could make myself familiar with updating SailfishOS. The image I flashed is 4.5.0.24 What is needed to create a newer version? What can I do to make it happen? Is there some upstream fix for the video recording?

Second, I have never used waydroid as I always had an official licence. I am somewhat stuck because ‘waydroid init’ can’t find /dev/binder. I confirmed it is there. I changed the conf file for the other binder ressources as they are in /dev/binderfs. Maybe I need to create symlinks?

Would appreciate any help on both questions.