Huh? In what way does Google tell the companies which make their own Android smartphones, how they have to make them? I *really* doubt Sony did ask Google if it is ok/a good idea to put a 4K (simulating?) display in their Z5 Premium.
Yeah, I generally don't like Samsung phones at all.
I feel like they're being pretty apologetic in that comparison. I don't think it's terrible. It's wayyyy better than past moto phones but it still goes to show that they have a lot of room for improvement.
There is a difference between Apple dictating Hardware, Software and Features and Google trying to coordinate the needs, plans and wishes of n OEMs.
Considering it's such a huge improvement over previous years it's alright to be a bit apologetic I think. They probably just need to get their software in order. Who knows if they will but it is what it is.
problem solved
It'll be out by then anyways.
Both phones should come out next month in here, though. There should be plenty of reviews already.I'm sure google knows beforehand that Huawei was going to come out with force fouch or Samsung with an edge screen or Sony with a 4k screen, therefore why not introduce that even as an incremental build and make OEMs stick to that API and eventually evolve it as necessary? Or at least let OEMs contribute that API to AOSP?
Yes but next year every new Android flagship will probably have force touch (because Apple and the perception of better specs) and yet it will at best take another year for a system-wide force touch because 1) google will only support it with the next version of Android and 2) it takes forever for devices to be updated to that version. So while google's "coordination" allows for technical freedom it is also a drag on OEMs and users because new features have to wait for google to catch up.
And i'm pretty sure that Google has little to no insight on what OEMs are doing on the hardware front, and i'm even sure they have no insight on the alterations the OEMs are doing on their Android branches, as long as the Play Services rules are not violated.
The only drag on users are the OEMs with their slow ass updates. Maybe less bloat on their branches would result in faster updates ... you know like Morotola does it.
It's not about telling them what to do, it's more about "hey any new functionality in your upcoming device? Maybe we should design an API together".
Yes there's an API for fingerprint scanners in Android M, but the cynic in me says google implemented it simply because of Android Pay.
That's a bit harsh, while OEMs do drag a bit on updates carriers and chipset manufacturers taking their time on certifying the release/ updating their codebase (if they even bother to update).
just buy the new Vertu and be done with it
Nexus 5X benchmark seems to confirm 2GB of RAM, Snapdragon 808, and not much of a performance increase over the Nexus 5 (although with pre-release software, that may change).
Source
Nexus 5X benchmark seems to confirm 2GB of RAM, Snapdragon 808, and not much of a performance increase over the Nexus 5 (although with pre-release software, that may change).
Source
Quick googling raised one question ... is that 808 somehow underclocked? Shouldn't it be about 1.8 Ghz?Nexus 5X benchmark seems to confirm 2GB of RAM, Snapdragon 808, and not much of a performance increase over the Nexus 5 (although with pre-release software, that may change).
Source