Android 8.0's 'Streaming OS Updates' Will Work Even If Your Phone Is Full (arstechnica.com)
Regardless of whether or not your phone is full of pictures, or videos, or apps, you will still be able to download and install an OS update with Android 8.0. According to the latest source.android.com documentation, Google has cooked up a scheme to make sure that an "insufficient space" error will never stop an update again. Ars Technica reports: Where the heck can Google store the update if your phone is full, though? If you remember in Android 7.0, Google introduced a new feature called "Seamless Updates." This setup introduced a dual system partition scheme -- a "System A" and "System B" partition. The idea is that, when it comes time to install an update, you can normally use your phone on the online "System A" partition while an update is being applied to the offline "System B" partition in the background. Rather than the many minutes of downtime that would normally occur from an update, all that was needed to apply the update was a quick reboot. At that point, the device would just switch from partition A to the newly updated partition B. When you get that "out of space" error message during an update, you're only "out of space" on the user storage partition, which is just being used as a temporary download spot before the update is applied to the system partition. Starting with Android 8.0, the A/B system partition setup is being upgraded with a "streaming updates" feature. Update data will arrive from the Internet directly to the offline system partition, written block by block, in a ready-to-boot state. Instead of needing ~1GB of free space, Google will be bypassing user storage almost entirely, needing only ~100KB worth of free space for some metadata. Ars Technica goes on to note that the feature will be backported to Google Play Services, and will be enabled on "Android 7.0 and later" devices with a dual system partition setup.
Users get the latest apps, streamlined to remove any useful features, and also make it even easier for Google to plumb your juicy data and strengthen their behavior modification algorithms!
A win for everyone!
If Google would update or even cross date our phones with Google Android, I would pay for it. Instead we get Google Android plus phone maker driver layer, plus phone maker crapware, plus carrier crapware.
If I could just go back to 2015 Cyanogen...
Will we be able to kill this whole partition and reclaim the space?
I like to use community ROMs and wouldn't want to do an OTA.
Do not meddle in the affairs of geeks for they are subtle and quick to anger
Google is reserving additional space and making it unusable by the user to ensure updates can be run.
For the 9 months that the device still receives security updates this will be a killer feature! After that just throw it in the trash and buy some more Chinese junk!
Google blocks you from using your SD card as you wish but they will make sure that enough free space is reserved for their updates that you probably don't want.... thanks Google!
... for something that never happens; OS updates on an Android phone.
On a long enough timeline, the survival rate for everyone drops to zero.
But it's not going to be empty, it's going to contain an older version of your OS which the system keeps around so it can update itself and boot from it in case the update fails.
That's in *google*'s update scheme (the one mentionned in the summary).
This thread's top poster is not interested in OTA update from Google.
He's interested in installed community firmware such as LineageOS (formely CyanogenMod).
He has no use of the "one partition currently running (with old OS) one partition currently downloading (the next OS)", 1 partition is enough, and wondered if spaces can be claimed from this partition.
In this conditions it's actually relevant to point that the firmware running inside the flash chip will actually claim that unused space as more reserve for wear-leveling.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
It's not like android devs are known for being able to.
So in order to get the update that works even if your phone is full the only thing you need is a update to your phone that is already full?
Right....
So even if my phone has no more space for kitten pictures the vendor can cram an battery-killing app update in the middle of the day?
I'm not worried about a real update on an unlocked phone. I'm worried about how a shady carrier will use this feature.
Based on the usual competence of carriers this could leave me stuck somewhere with a dead phone that won't charge as long as it can reach the carrier's update servers.
So, let's see, since streaming ain't new, why have devices been downloading update packages in-advance of executing them forever? Oh yeah, because anything can happen and stability matters.
So, I see this resolves the stability issues, but having SystemB separate from SystemA. Wonderful.
So where does SystemB sit? Oh yeah, a whole 'nother partition . . . that takes up zero space?
Not quite, I'll bet.
So, let's create a big huge partition, hide it from the user, and then say that our updates require zero space.
Welcome to dedicated resources; nothing new.
Or, and here's a thought, you could give the user the benefits of that extra space, for the 90% of the time that they aren't updating anything.
Look! we've done the impossible! We don't need any of your space! Because we stole half of your space from the very beginning!
Moohaha!