HecticHector
I'd like to see that very much. But as i see it, questions regarding detailed specs are far away from a reliable answer.
In addition to that, my hopes to get a GrapheneOS Laptop in the foreseeable future, are declining even more. This is particularly in light of recent actions by Google, which became particularly visible with the publication (or "non-publication") of certain software components of Android 16. Those let my doubt their future investment in FOSS projects like the Android Open Source Project (AOSP) itself.
Back to the hypothetical GOS laptop:
- I remember some several months-old (prior AOSP 16) statement as well. However, IIRC, it was more about the GOS Project loudly thinking about that if (!) an android laptop supported by google appeared it was likely that the project would eventually support it. I presume that, at that time, there also was a very plausible assumption that such a device would mostly be based on AOSP as we've known then.
- In addition to that, there have been late 2024 rumors that there has been an active project at Google, called "Snowy", aimed at developing a new, pixel laptop. (Compare https://www.androidcentral.com/chromebooks-laptops/alleged-google-pixel-laptop-early-report )
- I think we can take already existing improvements regarding desktop mode and development "under the hood" to create an environment able to run native linux apps to be somewhat consistent with a planned, future Android version then will be compatible to select desktop/laptop hardware and provide the desired desktop experience. (Compare https://issuetracker.google.com/issues/392521081#comment3 , as cited by https://www.androidauthority.com/android-linux-terminal-purpose-3535765/)
Now comes the big "but" - and this is why my hope is declining: The recent publication scheme of Android 16 (as of 2025-07) and prior tendencies of Google to do more development Closed Source, lets me seriously doubt Googles FOSS development policy and engagement as a whole. Frankly -- NOTE: this is entirely speculation atm -- I wouldn't be surprised, if Google forked the decisive part of future Android development to a proprietary, closed source "Pixel-Android" and left the AOSP remain to whoever is left to develop.
BTW: I'd consider such, speculative, future move an extremely bad move -- since, to me, an immense part of the Android ecosystem and its quality has originated from its free and open nature (up till now). A nature which let everyone improve not just their own products, but to some extend also those of the whole ecosystem as well. And that resulted in immense benefit for Google as well. However, if a few key decision makers see it differently and want to make a decision away from the contemporary open environment, I can't and won't stop them from hurting themselves.
What this means for a possible "Project Snowy" laptop is unclear for me, yet. It's just my fear, that such assumed device might be degraded to the same sort of lame, closed source device we can obtain from competitors (wink Apple) -- and not be qualified as a potential GrapheneOS device any more.
For a real FOSS, GrapheneOS laptop I'd probably shout "take my money".
For an apple-style, closed "Pixel-Android Laptop" under the thumb of an enterprise betraying its original ideals -- definitely not.