After daily driving a xperia 10 V for a year, in disappointment of the progress I just bought a Oneplus Nord N10 5G and installed ubuntu touch. AppSupport is of course way better than waydroid in every aspect, but when it comes to native Linux support, ubports appears better in every way.
I used to believe the reason that Sailfish choose Sony device is that they release blobs which is beneficial, but from what I have learnt, Xperia 10 III, which is overall the best supported device ATM, only has one long range camera working and takes a long time to focus. On the other hand, ubports get a device released at same time with 10V with full support from NFC to fingerprint to all cameras. With libertine I am now running full desktop firefox (they have a build in openstore which customized the UI to be usable on phone) and frankly speaking it is smoother than fennec on Xperia 10V.
My knowledge is limited on porting devices, but this contrast surprises me. It is kind of sad because I was a long time Sony phone fan before I started using Linux mobile systems. I really like their hardware design philosophy (however Oneplus N10 5G also have headphone jack, duo sim, sd card support, but not water resistant).
Somebody can correct me if I’ve gotten this wrong…but how I understood it, is that Sony cannot release their official blobs from stock-Android because Google doesnt allow it (stipulated in Android license).
So AOSP program builds new blobs out of scratch and it is done half-heartedly (?) by…hmm..well who actually (?), not Sony (?) - the result is atleast obvious, an avalanche of bugs.
Leads me to the question, how does LineageOS deal with this? Yesterday i took one of my 6 years old Xperia 10’s and flashed LineageOS onto it. Result is, this good old phone now supports VoLTE, VoWIFI, Fennec browser works at triple speed without any tweak of the about:config, much less battery drain, and more.
I would really like to see some sources for these claims because to me, these sound like they have a very high potential to be bullshit inaccurate, and speculations based on them therefore also.
I have no sony device nor do I care much about them. I only read in the forum that the sony devices use blobs from aosp image for whatever reason and not the ones from the stock firmware (like e.g. lineage does), why this is the case I dont know and again I dont care
SONY grants You non-exclusive, non-transferable end-user copyright rights to download the Software on the local hard disk(s) or other permanent storage media of one computer and install the Software, by using the Fastboot Protocol, on a single SONY device with an unlocked boot loader at a time. Except as provided by any Open Source License Terms, You may use the Software only for the sole purpose of testing and validating Your own applications and/or content (“Purpose”).
Me too. But it’s something I read some years ago already (…or maybe I just did dream of this while sleeping )
I think I thought I read it in together.jolla.com, but that site is no more for verification.
Eventhough the site still existed, it could have been unverifiable source there too, so the site maybe wouldn’t help anyway.
I did state in the beginning that someone might need to correct me
However, thinking it rationally. We can establish that the device drivers are sub-standard if compared to stock-Android device drivers - can we not? I think any X10IV and X10V owner might have an opinion on this one…(?)
→ which means that they are not the same what Sony uses on the official Android versions …or..?
→ which leads to the question why would Sony not release their perfectly working blobs/drivers to the AOSP-version? Why develop the wheel again?
Sorry for opening a Pandora’s box, speculations might not help anybody on this one
This was asked in community meeting once at least in autumn. Don’t remember exactly but Sony can’t use those blobs they use in their normal android versions in their open device program. And that in open device program they have different employees with probably very little co-operation with other team. My guess is some licensing thing but don’t have any sources and currently no time to find from matrix chat
Jolla is years behind of what is happing now. They should see this coming and go with linegae images a long time ago as those seems to have all the problems (That jolla cannot fix with sony blobs) figured out.
For me it seems that they can’t go with lineage images. There has been talks if they would support community ports officially, which could do this. But for me it has seen more that they themselves can’t officially go down the lineage road.
)
