The quality of the images seems to be similar, although the autofocus appears to be a bit more finicky in Sailfish. As @Setok wrote, only the main cameras (front and back) are supported for now.
Hmm… I have one question.
Manual says than it will be better, if I upgrade my phone to android 11, but later manual propose to use binaries from Android 10.0:
DECEMBER 18, 2020, SW_BINARIES_FOR_XPERIA_ANDROID_10.0.7.1_R1_V12B_SEINE.ZIP
But Sony’s website offer updated images for android 11, with fixed issues and vulnerabilities:
MARCH 16, 2021
SW_BINARIES_FOR_XPERIA_ANDROID_11_4.14_V4B_SEINE.ZIP
So, my question is: is it safe to use this outdated firmware drivers, and when new updated binaries will supported by SailfishOS? Thank you.
As I have already reported, my battery discharges quickly. The night lost 20%. Only wifi on. I want to do it again using a factory reset. But I can’t find this option anymore? Any advice?
I tested this on my Xperia 10 II using the Android_11_4.14_v4b_seine binaries. Even the flashing tool warns you if you try to install it directly with those binaries. However, it seems that network like wifi, sim cards or even camera are not working. Not to mention that the fingerprint didn’t work as well. Strangely, the UI / UX seemed to be smoother .
I’m trying to reflash the system. Unfortunately it does not work. I suspect it’s the security code. Can you do a factory reset from the device? How can I deactivate the code? thanks
Update to Android 11 is probably to ensure that all binary blobs dealing with the modem and some other parts are updated. This is done while you boot into Stock (NOT AOSP) Android as distributed by Sony. So, update to Android 11, boot into it. There is no need to register with Google, as far as I know. But you probably should get into the OS fully booted.
When you use AOSP10 based SFOS, the binaries have to be for AOSP10. Do not mix with AOSP11 blobs. The flash script warns for reason as it is the combination that works.
i have my 10ii doing update for the entire night and it still havent finished, is this normal? its in 3\3 installing stage
never mind less than 1 second after i posted this it literally finished…
If I were an italian, I would say ce l’ho fatta.
I’ve checked my phone and it’s on Android 10. I went to update it, but it says that it’s up to date. Do I have to do something special to update it to Android 11?
Did you already unlock it? In that case you need to lock it before the updates become available.
Ah okay! So I need to lock it, update it, and then unlock it again?
Yes. See here for how:
Thank you for the help! Might do so once Exchange support is available, in order to flash SFOS again
Can someone already write a little conclusion on how they find the Xperia 10 II with SFOS?
I’ve decided to split off the discussion about bugs and other problems with Sailfish on the Xperia 10 II to a new thread:
Here goes my end of the week experience summarized. Mostly it works. Phone calls, text messages and email all go through. Setting up workplace email, which was semi-automatic in Android, was still impossible. To be fair it fails everywhere else but Gmail, so it is more of an organizational problem. The harbour store seemed quite empty, installing Storeman from openrepos.net was easy though. Took me a while to realize that only the newest applications are for aarch64 and can not be installed. Installed a black & white ambiance to safe battery on OLED. Also BatteryBuddy to keep it from charging over 70%, mine has newer gone below 40%.
The browser engine is still too old for most modern websites but for many things that I do it is passable. Most streaming services will fail, but our national broadcasters services work. Maybe it is a good while to reconsider those subscription services. The speakers sound different and not in good way, but I can live with that. 21:9 aspect ratio isn’t as widely used as it is on Android but who cares. Display burn in is something that I wonder about, like running DisplayTime program nightly would be cool, but likely a bad idea.
Nothing I’ve encountered seems to be a problem specific to this model. What works:
- Everything except
- NFC is something that I did not get to pass on the Android side hardware testing and have not tried it here either, Matkakortti is not aarch64 yet. Payments wouldn’t work anyway.
Having this time without online service providers apps has me pondering that is running Android something that I want to add to this? It be quite happy with just flatpak support. But I’m likely going to get a license anyway and if it is not my cup of tea give it forward. Well if it’ll get GCam working then its a must have.
Community member @leszek has uploaded a video with tests of the device’s main camera under Sailfish OS:
https://www.youtube.com/watch?v=-rpTxJtWJtc
All 4 cameras seem to work ok under SFOS.
But I had to install piggz-o-vision and set the camera ID in /usr/share/harbour-advanced-camera/qml/pages/CameraUI.qml
settings.global.cameraId = 1
(for bottom camera)
etc.
Nice! Beeing unfamiliar with this app: is it a permanent configuration, or do you have to adjust the config whenever you want to use a different camera?