Editorial: Nexus PDK and various enough to piece together the puzzle of fragmentation?


The title is most likely emblematic of what was asked during the presentation of the new Major Release of Google and is even more likely a question that no one can answer yet. It seems that even the manufacturers are so eager to enlighten us.

The colleagues at The Verge are in fact able to ask some information about the different companies for updates , but the responses were very uncertain: Acer , ASUS and HTC have responded with a gray "no comment" , LG has instead revealed that in his office is considering the option update on the terminals on the market (hoping not to run into problems and delays at the Gingerbread and Ice Cream Sandwich ), while Motorola is formally absent (Google had said it would not be favored , in the end) . The only house to unbutton a bit 'was (predictably) Samsung: The Korean company will update some devices Jelly Bean, recalling that it was she who produce the Nexus S and Galaxy Nexus, which will be omitting the criteria of choice (we can only hope that they are not like those used for the ' upgrade to Ice Cream Sandwich, would be exceedingly grotesque to see Android 4.1 running smoothly on a single core and not have it on a Galaxy S II).

Thinking about it, one of the surprises is without doubt the silence of ASUS: the Nexus 7 is right in this work and the majority of its products this year are sold with a very similar hardware, but we'll see.

On the CyanogenMod, everything remains silent: the page of Google + we learn that the team expects the source (and have repeated a concept already dealt with in the past), without specifying whether the new version will be marked by a 9.1 or a 10 round.

The premises are very uncertain and no one seems to want to say too: without a doubt, Google is going all out there to speed up the process of porting Android for different devices, just think of the PDK and the Nexus many of which are rumored, but a couple of months will be sufficient for producers to go and put his hand in the most hidden recesses of Android (and its kernel) and integrate their own interfaces as well? (Tell it to Samsung.) Or, as the little devil on my shoulder suggests, one of Mountain View is a move to get out of trouble for late updates?

These questions lead us to consider a matter not so rosy in the matter: if Google is able to recompile the operating system for Nexus S (that's what it is, complete with different drivers), and very quickly without going to touching the interface, the problem will not stand right there? We do not doubt that in Mountain View may have been working simultaneously on multiple terminals, but it is unlikely that the port is not started with a product that is already largely in place (and the PDK -up to companies to be tested, however, what better?) if only for the use of resources (even Google has infinite), then the finger pointing goes on forever and inexorably toward the major changes that manufacturers make to our love green robot.

So let's add to the questions that we have left open a question that we have already dealt with but, unfortunately, have not yet gone out of fashion: truly serve these customizations? Or maybe Google should put a dot on me and decide what needs to be Android Android and not xyzUI?

Post a Comment

Previous Post Next Post