3 ms·
> but that has no consequences for other apps. No functionality of AOSP is being absorbed into Play Services at all. That's technically correct. But apps that
by Zigurd 12y ago
> but that has no consequences for other apps. No functionality of AOSP is being absorbed into Play Services at all.
That's technically correct. But apps that are in AOSP can be supplanted by Google proprietary apps and turn into abandonware.
Goggle has never outright misbehaved w.r.t. AOSP, and in some cases put things like ART into AOSP very early, ahead of commercialization by Google's OEM partners. BUT that doesn't mean that Google Play Services isn't effectively shrinking AOSP's share of the standard complement of apps.
- mattl 12y agoAndroid 3.0 wasn't released by AOSP until Android 4.0 came out. That was certainly a strange time.
- jayd16 12y agoGo back and use a 3.0 device. It was a mess.
- Zigurd 12y agoIt wasn't a mess. There was never a good reason to withhold the source code. It was eventually released, and there was nothing terrible in it.
- yareally 12y agoMy guess for withholding Android 3.x was to prevent Amazon from using Android 3.x on the original Kindle Fire. Instead, the original Fire was stuck using a modded Phone OS (Android 2.3) while Android 3.x remained exclusive to tablets licensed by Google.