3 ms·

Both of you are missing the point. The context of this thread is Google Play Services, and any apps dependent on them, won't be available on the Chinese AOSP fo

Both of you are missing the point. The context of this thread is Google Play Services, and any apps dependent on them, won't be available on the Chinese AOSP fork. Also, compiling without breaking, and running without breaking for two different things. If the binary compatibility alone was the main problem, there'd be no issues with Android fragmentation and testing. If you go to Google Play, pick "Top Apps" and read the reviews of any top apps, you'll see plenty of "It's not working", "won't launch", "freezes my phone" type comments.

fidotron 13y ago
You're spouting nonsense that you've heard and not reality. The errors people run into are largely just bugs in the apps not being written to deal with the different cases that exist, because developers are lazy and tend to write just for whatever device they have in front of them. Cases with RAM usage, storage assumptions, and so on. That and GL driver issues used to be a headache (less so these days), but Chrome OS is hardly going to help there. Since Android 4.0.3 the stability of the framework itself has been exemplary with very few exceptions. You happen to be missing our rather epic point that apps which are 100% dependent on GPS and cannot be moved from them are in practice rather thin on the ground.