Sorry, I did not verified this aspect. My Xperia 10 II arrived on May 26th in the morning and in the meantime I had to move from Germany to Italy dealing with the landlord goodbay, a travel full of luggages, all the burocracy of changing the residence and made my appartment in Italy living again.
Moreover, I never played with a smartphone before and never developed an Android app but just used them. Despite this, I have been able to overcome the annoying and absurd USB3 problem about fastboot protocol. In my case, I suspect it was coupled with sleeping USB ill-mode because after the first fastboot command was executed the connection interrupted and phone rebooted, regularly.
For sake of completeness, an Ubuntu LTS pro is running on a refurbished ThinkPad. Thus, I was quite surprised about seeing hardware glitches with fastboot protocol because in the last 15 years no one of my ThinkPad laptop dent my trust in them. Despite my experience in this brand, the last two X-series ThinkPads were behaving strangerly like they were affected by a CPU cache injection bug. Probably, just a unlucky choice twice.
Then, I discovered that my smartphone arrived with Android 12 instead of 11 and in the documentation there is writing that 11 is more suitable than 10 but nobody wrote about about 12+ is wrong. Therefore, I got stuck into GPS fail-over which forced me to use ADB for my first time in life and introduced me in a world in which sudo
has another name because the entire architecure is completely different at such a point for which the OEM-installed Android version can make some kind of difference in how the current linux-based SFOS works because the hardware is initialised using Android configurations and also microG affects the native apps behaviour while they are using GPS. In fact, microG preview release solve a bug on Xperia 10 II when GPS is used by native apps.
Just for sake of clarity, I rephrase this concept: the native apps behaviour running on the SFOS depends by the Android image and by the higher software stack that communicate with it. This is not a smartphone, because considering its architecture it more similar to a triple cheesburger in an Esher painting!
Finally - after this incredible hacking trip - I realised that a “Quick Start Guide” was missing and I wrote it.
Now, you pop-up revealing me that the relative huge pile of filesystems which I saw are not based on an read-only image. So, all the other stuff is not written on top of that (or mounted in several folders) in such a way that if I press a specific combination of hardware keys the smartphone is reset to the default factory installation and all the user data deleted.
Moreover, you are claiming that pre-installed app can also be deleted at installation time.
I have the sensation that we got stuck in a misunderstaning here, with “pre-installed app” definition, I hope…