Xperia 10 II + SFOS

Sony ships aosp as well, so that would be covered too:
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions
I guess that means then that:

  • patches for the kernel might be necessary for hybris
  • patches for AOSP might be necessary for hybris/Android support?
    Come to think of it, n00b question:
    does MER require AOSP ? If hybris (as I understood) is managing the compatibility between glib & android drivers in the kernel; theoretically, the AOSP is necessary “only” for the android support?
1 Like

I was looking at what Vknecht posted on:
http://merproject.org/logs/%23sailfi…05-02.log.html
respectively:

https://build.merproject.org/project…qualcomm:f5121

also a pie based port which works better, but only boots correctly sometimes:
https://build.merproject.org/project…:hw:sony:loire

because of:
https://github.com/sonyxperiadev/dev…6c494ecad6875e

I would like to try any of these ports but I need some guidance like step by step sequence of actions.

3 Likes

No. By tthe way there had been a “Community initiative” already, which got abandoned.

2 Likes

how is the backport for audio to be applied ?

Oh, so someone already got it to work with an even more recent kernel version, that’s interesting. It’s a shame that person seems to have stopped working on it. @vknecht, if by any chance you read this, do you intend to continue your project?

1 Like

Thanks for the interest in Oreo/Pie based ports for Loire, and I understand how important it looks to SFOS on Loire users/fans. Sadly, it seems to be a dead end since Jolla :

  • never really acknowledged this work (like for all community devices/ports)
  • never agreed to provide/allow AlienDalvik for community devices/ports

so there’s no real benefit to it except maybe more recent kernel (and new problems/incompatibilities to solve), but even Sony’s 4.9 kernel branch (LE.UM.2.3.2.r1.4) is almost dead now and not update-able anymore.

Future is in getting Loire devices mainlined, that is, integrated in Linus Torvald’s Linux tree.
And thankfully there is a team working on it which already mainlined Nile/XA2 : https://www.somainline.org/
That way, no need for binary blobs anymore, and it opens gates to newer and native Android or SFOS ports.
Also, Anbox seems to be better supported on mainlined OS/devices.

14 Likes

Thank you for replying so quickly! Mainline kernel support for mobile phones sounds incredible, but I guess a lot of work will still be needed to make sure those phones can function like a proper phone, with decent battery life and functional sensors.

Indeed, Jolla does not support community ports more than on the tech side.
Premium aspects (Alien Dalvik, predictive text etc) are not available.
Which is why I was wondering if updating the kernel would yield at least a better AOSP.
But perhaps that’s not enough.

I am not looking for (yet) another open source project aimed at saving the mobile world (Jolla gracefully demonstrated this to be not a feasible solution already); I just want a sustainable (from user perspective) phone with SFOS :). The XPeria X is an excellent HW, and actually quite reliable.
If there’s not a better alternative available by the EOL of it, there might be better options around. Will see!

1 Like

One step further. readme

13 Likes

Did you try it? :grimacing: But we would need a “ready made” Image to flash, right?

1 Like

Thanks for the reply. I’ve checked the IRC meetup logs and thanks for the clarifications there too. I’ll wait hopefully for an official release for Xperia 10 II if that happens.
Slightly sad that the shift is towards B2B customers, but hopefully one day the momentum will be back again for providing phones/OS for end-users as first-party too (not just developers and testers).
For the moment, the only real alternatives for Android/iOS are you guys at Sailfish and the other Linux phones. Sailfish being the most mature and stable of the Linux ones.

10 Likes

Would this work right now? Amazing news!

1 Like

I just noticed the repository for this now has a branch for ‘upgrade-4.1’. So maybe SF 4.1 will arrive at the same time as this :slight_smile:

In any case I picked up a phone the other day. Now sitting unopened on the shelf in the hope it will be able to enjoy some Sailfish love soon.

3 Likes

Test it on Android. If you find some fault you can have it repaired or exchanged under warranty.

6 Likes

The warranty is still there for some time, so I’m in no rush to open the box. If I have to resell the box it will be more valuable unopened. Once SF (hopefully) comes out for it, I’ll naturally play around with Android first to see it’s working (and also out of curiosity to see how Sony’s Android flavour functions).

There’s always hazzle and confusion with this warranty case. In general, in EU (might be somewhere else as well) there is this thing called vendor liability. If you buy something and it breaks they need to be able to show that you caused that damage. Usually this vendor liability is also 2 years as the warranty. And even if let’s hypothetically say your Sony warranty is 1 year, there is still this vendor liability. You can always check your local consumer laws and get help for bad situations. For instance, in Finland we have The Consumer Disputes Board which solves these situations between consumers and vendors, and usually the outcome is on consumers side.

I had this very irritating case with my Xperia X and they tried to repair it 4 times after finally it got stuck in a bootloop and I got my money back… However, the phone had SailfishOS and the stock Sony Android etc. were flashed and installed on the service, with no charge.

Also, waiting here eagerly with my Xperia 10 II to have any information about official Sailfish on it.

With the readme instructions posted yesterday, would it possible to already flash Sailfish OS or it won’t work until it’s released? Can’t wait! :smiley:

4 Likes

Do mind, there is no Android support however.

Give a link to the firmware. Thanks.

Found https://sailfishos.org/wiki/Sailfish_X_Xperia_Android_10_Build_and_Flash
and https://github.com/mer-hybris/droid-config-sony-seine/commit/cf94d86f6be3714e1461f4717bb3ba497e26f0c4
Or are there more links?

I will clarify the question. Is there a ready-made firmware, or do you need to assemble it yourself according to the instructions above?

It will come. No need to rush. And it will be a better experience than going through git etc. So be patient.

8 Likes