A few days ago we showed you further evidence that supports the Chromebook Pixel / Link laptop, a device previously spotted in a leaked video and supposed to be Google’s own upcoming Chrome OS-running notebook.
The Chrome OS device is said to feature a 2560 x 1700 resolution display with touch support, a backlit keyboard but also LTE connectivity in addition to Wi-Fi and support for Intel’s Ivy Bridge generation of processors.
Myce’s Jan Willem Aldershoff has further explored Google code and found evidence pointing to a “Google Link” device, most likely the internal codename of the Pixel. Code names have been used in the past for other Chrome OS laptops including, in chronological order, Mario (Google Cr-48,) Alex (Samsung Series 5,) ZGB (Acer AC700,) Stumpy (Samsung Series 3,) Lumpy (Samsung Series 5 550,) Snow/Daisy (Samsung ARM Chromebook,) Parrot (Acer C7 Chromebook,) Stout (Lenovo Thinkpad X131e,) and Butterfly (HP Pavilion 14). But there doesn’t appear to be a pattern here when it comes to project code names that would confirm that Link is also a Chrome OS device.
However, a discussion about HighDPI support between Chrome OS developers titled “Remove high-DPI resource paks from all boards other than link” suggests that the feature should be enabled on Google Link only. One of the entries reads:
Ok. We had been relying on having high-DPI assets on all devices (for testing high-DPI, supporting plugging in external high-dpi displays, etc.). But now with availability of Macbook retina and more Arrows, this seems less necessary. If the space is that important then we should keep them only on link boards.
Another look at the code reveals that the Google Link could support Intel’s Ivy Bridge processors, although it’s not known at this time what processor model we’d be talking about.
Finally, backlit support and 4G LTE support have also been spotted in code, and the latter is definitely one feature Chromebook users will appreciate on a device that’s supposed to be mostly connected to the Internet to offer a proper computing experience.
However, the Chromebook Pixel (Google Link) is not a confirmed product and it may take some time to see it unveiled. Some of the code that Myce is pointing to dates back to April 2012, which means that if indeed the project is real then Google spent a lot of time working on it, and we have no idea whether the product is ready for prime time.
With all that in mind, the same source points us to a Sergey Brin Google Plus post dated January 14 that shows a picture of some jellyfish (top image) which seems to indirectly confirm the existence of the Pixel / Link. But is that actual proof or just a happy coincidence in light of the video that has recently surfaced?
We’ll be back with more details about this yet-to-be-announced product as soon as we have them.