How come you did not mention the
"Scoped Storage" which is destroying the core Android functionality of file management into the stupid iOS type sandboxed castrated trash. This doesn't qualify for a deep dive, because that change is HUGE vs these stupid Chat heads or that big blocking volume panels.
Look at the
Potato Custom ROM1 and think about how worse google did just because to satisfy kids.
The Scoped Storage kills the whole file management as we know on Android to iOS sandboxing, they depreciated the Read and Write external storage permissions to the Mediastore usage of the Photos, Videos and Audio collections only. That means no app can access other apps files there's simply no permissions. Except for SAF, SAF is a slow one and heavily downgraded, recall the photo/file picker when you send anything over WhatsApp, that's one of the main feature of SAF since it treats all storage spaces from Cloud and Local as well.
You cannot write to those files unless you use Mediastore again only stupid predefined 3 types of files. Document viewer, Text editor, zip extractor that I use with
FX Explorer app (Strongly recommend to use it, very powerful) all are dead once they target Q (They must because of the enforcing of Google, else delisted, more in below links)
Check the commons blog from Murphy to understand more (link in the end) this is to cripple Android Filesystem access in the name of Security (No reason why there are no granular permission gating). This is another wrath of Google's Draconian grip on Android which is user hostile and fundamentally against the principle of Android.
They killed a lot of things and this one is massive, Read over at this
Issue tracker and Star it. See the transgressions of this bull***t change.
Another powerful feature of Android gets booted because kids or iOS mimic.
List of downgrades that Google did so far in ruining Android (
old comment)
Removal of undocumented APIs in
Pie and
Q
Draw over other apps,
Killing notifications for notch,
Clock icons to accommodate Notch no resolution still even after 300+ stars,
Killing clipboard access permanently without permission gating,
Killing the expandable toggles,
Putting every icon into dinner plates to force the uniform icons look vs the material design and unique shapes, and now
forcing them with PlayStore, to mimic iOS.
Killing the SMS and call log access, again no permission gating.
Proprietary inclusions into android heavily (more reliability on Google Apps/Play services) and undermining the AOSP.
Accessibility death,
Rootless substratum block 5000 stars no effect.
Play Store restrictions clamps for latest API,
Cloning iOS multitasker and killing a more sensible vertical scroll system (phones have vertical screens), forcing the looks of the play store icons to mimic s singular shape like iOS.
It's a shame to Android community I remember how
Chevron Unlock died on WinPhone OS due to that Satya Nadella sending lawyers to their home to block the .reg edit and allowing that OS to take off like a Win7 successor on mobiles.
Same thing in a different skin, Abusing their power to draconian levels and duopoly ******** 5000+ stars in the issue tracker, nothing zero effect as if people are fools to use that ?
I strongly suggest Tech press to mention this because all these corporations move ONLY with the bad PR, look at the Apple Keyboard flaws but since all is mainstream no one cares to bother..sadly.
Last note, read this fantastic blog, he not only covered the Scoped Storage extensively but also a great insight of direction from Google's death grip POV of Android and their plans to put more clamps on the OS crippling it to satisfy their stupidity of Ecosystem anti liberty lockdown.
Massive change of file system essentially turning it into a full fledged iOS cheap clone but with AOSP and Linux GNU GPL they cannot, and somehow fail to realize it as well. But they are working on it as well the MIT based Fuchsia OS which doesn't enforce any changes to the OSS code. And ChromeOS, how locked down it is vs Android.
Thankfully Root is achieved on Q (
Magisk Dev Twitter) it had
problems initially but for now we are good.
Problems? See this thread at archive.org.
![[IMG]](images/storyImages/41-800x444.jpg)
