by Lucian Armasu, 1 year ago
Verizon has never been too fond of the Nexus phones. I remember when Google launched the Nexus One, a Verizon exec was right there with Google, and saying they’ll have the Nexus One in spring…
[ Update 2011-09-07 22:23 -- We've received a tip that the User Agent Profile (UAProf) of the Google Nexus S (which Samsung manufactured) is actually similar to the UAProf of the Nexus Prime. In fact, the two XML files are exactly alike, save for one difference: the handset model numbers. We've added screenshots of the
diff for the UAProfs for both Nexus S and Nexus Prime. We've also updated parts of the original post a bit to reflect the information we have received. For good measure, we've also included screenshots of the
diff between the recent XML for the Nexus Prime and the first Google phone, the Nexus One, made by HTC who reportedly omits a lot of device-identifying information in pre-release User Agent Profiles. ]
A recently updated User Agent Profile (UAProf) on Samsung Mobile’s site reveals several interesting bits about the Nexus Prime.
First is that the UAProf, in XML format, is named “nexusprime.xml,” which adds more credence to the yet-unconfirmed rumor that Samsung may be the anointed one for the Nexus Prime.
Second, the handset model known as the Samsung GT-I9250 is specified in the XML file as the device model to use the file. We got wind of the GT-I9250 from a leaked roadmap purported to be Samsung’s.
The said model was listed on the roadmap as the only upcoming handset bearing Android 2.4/4.0 Ice Cream Sandwich, a fact causing a whirlwind of rumors to ensue about its being the upcoming Nexus Prime.
We almost got fooled into thinking that the GT-I9220, a 5.3-inch handset–although listed only as having Android 2.3 Gingerbread–was the Nexus Prime. It turned out to be the Samsung Galaxy Note recently debuted at the Internationale Funkausstellung (IFA 2011) in Berlin.
Third, the UAProf specifies a screen resolution of 800×480 (WVGA), which we find to be heartbreaking–if true (and we hope it isn’t). Rumors currently circulating have been saying that the upcoming Nexus Prime will have 720p resolution. The leaked roadmap, which has been nothing less than prophetic so far, also specifies 1280×720 as the resolution of the GT-I9250. This leads us and others to question the accuracy of the details in the XML file. It is possible that Samsung’s chest is no longer able to contain its emotions and just wants to scream, “WE ARE MAKING THE NEXUS PRIME!!!!!” without divulging further details that might allow competitors to preempt its moves.
Fourth, the XML file mentions ARM11 as the processor for the Nexus Prime. We were hoping to find OMAP4470 or OMAP4460 there, since Texas Instruments, which manufactures the OMAP processors, have been reportedly getting chummy with Google as concerns the Nexus Prime.
Fifth, the MMS Max Image Resolution value is only 1200×1600–or 2 megapixels. The MMS Max Image Resolution (mms:MMsMaxImageResolution) attribute specifies the maximum resolution of an image that the device can send through MMS. Here’s the catch–that same attribute is almost usually equal to the resolution of the device’s primary camera. Does it not break your heart for the Nexus Prime to shoot only 2-megapixel photos with its primary camera?
As to which of those details are true, we really have no idea. But, we do get the gut feeling that Samsung is not entirely truthful here–and for a presumably good cause.
Interestingly, the UAProf for both the Nexus Prime and the earlier Google phone, the Nexus S (also from Samsung) had similar content, except for only one change: the Nexus Prime’s model number. Everything else in the XML files for the two devices is practically the same, as can be seen in this
In light of that, it seems that the XML file for the Nexus Prime was based on the XML file for the Nexus S as template–and only the handset model number was changed. This leads us to presume that the other details in the Nexus Prime UAProf will still undergo updating soon.
For completeness of comparison, we’ve also included the
diff for the UAProfs of both the HTC-made Nexus One and the Nexus Prime:
Now, who’s with me in saying that Samsung is fudging the details of the Nexus Prime User Agent Profile? As to why, you’re free to speculate with us. Perhaps, to spread confusion among the public in order to exasperate it with a wild-goose chase and get its attention back to the Samsung Galaxy S II and the other Samsung devices recently debuted at IFA 2011?