Substantial leaks for the third-generation Made by Google devices emerged later than usual this year, with concrete rumors first surfacing at the end of May. In the coming months, there will be more and more rumors with one good source of news coming directly from Google’s Android Open Source Project.
9to5Google is compiling an updating list of when Google developers inadvertently slip up during the development process for these devices and the next version of Android. At the moment, we are aware of three codenames pegged with the Pixel 3 and Pixel 3 XL.
Last April, our Stephen Hall revealed a list of codenames for current Google projects. It included “sailfish” and “marlin” for the first-generation Pixel devices, as well as “walleye” and “taimen,” which are the Pixel 2 and Pixel 2 XL, respectively. “Muskie,” the shelved Pixel 2 XL from HTC, was also present.
Meanwhile, in October, a report suggested that “crosshatch” — now confirmed to be the larger XL device — and “blueline” from our list were like codenames for the Pixel 3. At the time, “albacore” was also offered as a possible codename for a third device.
Our full (reverse chronological) list of codenames referenced in AOSP will also provide some context to the nature of the entry:
blueline, crosshatch: June 19, 2018
A new commit related to Neural Networks.
blueline, crosshatch: June 14, 2018
blueline, crosshatch: June 12, 2018
blueline, crosshatch: June 8, 2018
This is the first commit where both blueline and crosshatch appear together. Given that the Pixel 3 XL is highly likely codenamed “crosshatch,” “blueline” is possibly the smaller Pixel 3 given the other mention a week earlier.
blueline: June 1, 2018
The first commit for blueline is in reference to testing done on that device of a “new spam API” for the phone dialer app that “can query additional data.”
crosshatch: January 11, 2018
Another entry related to development, crosshatch is referenced in regards to a Googler asking about the state of “
crosshatch: November 22, 2017
This commit wants to revert the earlier deletion of “toolbox/r.c” as “this utility is always useful during device bringup, so let’s bring it back for debug builds.”
Device bringup is a part of the development process where a system is repeatedly tested, validated, and debugged until it is ready for manufacturing.
In this case, one Googler notes that the tool is used “a lot” as part of crosshatch development.
crosshatch: October 26, 2017
The first reference for crosshatch in AOSP is in regards to an “audio subsystem” related to the “Pixel and Qualcomm.”