Unfortunately, that page has been started to be backup-ed by Internet Way Machine since 8th Nov 2022 only and here the first screenshot available
Technically speaking s/10/11/
or s/10/12/
in my original claim for some devices but just 9 for others.
However, why the same SFOS cannot work with the same Sony AOSP version independently of the device?
The last one is 13 for Seine hardware platform. Explain me, after all you are the expert…
When you will answer my question, above, you will find the proof of my other statement you asked to me.
spoiler: because SFOS cannot correctly initialize the hardware otherwise. Discover why!
spoiler 2: the day in which Sony will adopt the architectural design suggested in my SFSCON slides, they will be able to provide a single ASOP image for all their devices and a boot/rescue image tailored for each specific device or a set of three - I think - three images but because Android expects to find some stuff in some separate partitions - however - because the stuff can be mounted with bind
option, there is not a reason to keep it separate - however - it would be not nice to clog the device memory with about 128 MB of stuff when 2/3 of it can stay saved on a partition or two which is also better for OTA updates. That day SFOS will stop to work, unless redesigned.
none about the root filesystem and just one about the kernel as far as it means a porting for another well-documented and largerly more limited than a smartphone piece hardware.
That blobs are the firmware and you do not need either to use as-is. I don’t in fact. If you expect that Sony does a work for you, you can wait until the end-of-time. Then, why do I cultivate some hopes that Sony will adopt my design? Because they have the skills to do that and an advantage to do that. That’s why.