Moving all my photos and ebook .pdfs off did alleviate the burden somewhat, but hasn't completely solved it.
My current workaround for very large apps is to uninstall, redownload, install. Apparently, holding both the update and the installed app uses much more space than doing a fresh install.
Or just leave them all on the internal system, until a system utility wakes up to the fact that there is not enough space, and suggest moving apps to the sdcard. After few rounds of updates, rinse and repeat.
Then apply that to a local copy of the previous APK.
If that goes well, it attempts to install the new APK alongside the old install.
And if that works out, the user data is switched over and the old install and APK removed.
So at certain points during the install you need to have enough space for two full installs of the app, and the APKs they came in.
Microsoft needs to deliver updates in tiers in order to regain trust. Simply dividing it up into mandatory security updates, optional bug fixes, and optional feature upgrades would go a long way to addressing that even if the default is for all three tiers.
Except that there were demonstrated cases of MS inserting the "brainwashing drugs" on the updates. Many people had legitimate copies of Win XP bricked by XPA, MS alti-malware broke install a couple of times in Win7 (and off-line machines were bricked by DRM more than once), and, finally with Win10 we've officially got the spyware and adware coming through updates like people were long expecting.
And when you do get one, you don't lose sight.
(My favourite complaint is Windows replacing GPU drivers with MS approved broken ones on major updates.)
What to do? Upgrade the hardware. It's not supported anyway. Modern Android devices which have updates published do not have this problem anymore.
Apps take up 6.32 GB of storage on my phone. The remaining space is taken up by the app cache. This isn't useless information like you'd expect, but it turns out it is data that is vital to the operation of my apps. I clear it fairly often, but it fills right back up again within a day.
Luckily I have an SD card slot, so I have space on my phone, but Google does not like expandable storage. Probably because they are a cloud organization or something.
I personally like to stay on a fairly new phone, but I think it is stupid that your phone can become obsolete within a few years. If the radios are still compatible with the cell towers, manufacturers should be obligated to support them. If you can't support your phones, don't churn out so many crappy phones.
I know times are different, but I used a Motorola Razr V3 from 2004 to 2011. It worked just fine for the entire time. Obviously internet sucked, but I was going to school in a place where the internet barely worked anyways.
If you just want a phone for texting, calling, and maybe as a GPS here and there, there is no good reason to buy a new phone other than planned obsolescence.
I suspect this is an artifact of using the Linux kernel. As said kernel puts a focus on IO ops, and the EXT file systems spend a whole lot of time looking for contiguous free space before committing a write.
Thus if your app do a bunch of writing (say syncing local data with the cloud) at start, it will start quite slowly on a near full Android device.
Outside of the app binaries and such you have their core data, stuff that gets generated or downloaded on first run.
Besides that you have a cache directory pr app that is housed outside of the tree location of the binaries and main data.
More recent Android versions have introduced yet more complications on this via the storage access framework, by providing APIs that give apps limited RW access to "external" storage areas without having to request the related permission.
And that's without going into the whole history of just what "external" means when dealing with Android file storage.
A Moto G 2015 has only 8GB storage.
Even mid-range devices sold today only come with 8GB storage, of which 6GB are used by the OS.
The Moto G 2013/2014/2015
https://www.amazon.com/Motorola-Moto-3rd-Generation-Unlocked...
> And what price range are you using to define mid-range?
$200-$250
> Is there even a low-range (lower than 8 GB) if 8 GB seems to be the absolute minimum, since the OS won't even fit on something smaller?
See above.
The only Moto G model that doesn’t offer 8GB anymore is the 2017 edition.
This is a good analogy, but does it work in different circumstances? (Apologies for the derail)
Over on Android, the apps have got so big (and the storage was until recently so small) that automatic updates _cannot_ be installed - the new apps are too big, the phone is full. What do we do then?