11–20 of 115 posts
On the one hand I'm happy they added this, so we don't have to do it programmatically.
On the other hand it took them what, 9 years? It's bizarre that it shipped without the ability to do that in layout.
Wi-Fi Aware looks cool. Something like this has been sorely needed for things like Chromecast setup and local multiplayer games. Has anyone out there used it, or are there no supported devices yet?
How is it different to WiFi Direct? Aren't there quite a lot of these wifi-without-base-station standards, but they never seem to work or take off?
If they start allowing YouTube to work with the PiP feature on iPads (which it always could with third-party workarounds, but not in the official app [1]) after this, then it'll be confirmed that they purposely disabled the feature on iOS only to retain artificial parity with Android, which would be a very scummy behavior.
[1] https://www.reddit.com/r/apple/comments/5lxm6c/why_is_google...
Any dibs on what it's going to be named? An obvious one is "Oreo", but that's trademarked. "Oatmeal cookie" is the only O dessert I can think of that isn't.
Any dibs on what it's going to be named? An obvious one is "Oreo", but that's trademarked. "Oatmeal cookie" is the only O dessert I can think of that isn't.
https://gherkinstomatoes.com/2010/12/13/oreillettes-a-part-o...
Any dibs on what it's going to be named? An obvious one is "Oreo", but that's trademarked. "Oatmeal cookie" is the only O dessert I can think of that isn't.
There's Oreillettes at least, a yummy donut from south of France. Also, Kitkat is trademarked and there was an Android Kitkat. https://gherkinstomatoes.com/2010/12/13/oreillettes-a-part-o...
Too bad the OEMs don't keep up. Only 2% of devices have Android 7 (N). http://www.digitaltrends.com/mobile/android-distribution-new...
I look at these previews as an example of things to come 3 years from now. I keep hoping that Google will figure out a solution to that (restrict access to Play Services, say). Until then, I guess I'll continue targeting API 16.
The basic problem is that updates are an expense once the SKU starts shipping, while spending the same money on a new SKU is an investment.
Apple get around this because they own the whole stack. Thus keeping a device going longer means more exposure to their stores.
Never mind that even though they release a new iOS in name, major new features are left out for the version pushed to the older devices.
Never mind that on Android APIs can be supplied by APKs, and thus we have Play Services.
Frankly the only thing Google can do is adopt something akin to what they have on ChromeOS.
Split the Android VM layer from the Linux layer, so that they can update the VM layer independently of the kernel and userland layer.
Another issue is unless you are looking at white box rebrands, each OEM tailor the Android UI/UX.
Unless Google makes it possible to isolate this tailoring from the core Android code, there will still be lag time between Google releasing a new version, and it hitting devices. And that is reliant on the tailored variant fits inside the storage space of the device.