Google Pixels are no longer the AOSP reference device

Re:Google Pixels are no longer the AOSP reference device by nrclark on Thursday June 12, 2025 @01:26PM (#44260302)

A question for any Android folks in the thread: how performant is Cuttlefish? Would I get good performance if I ran it in KVM on something like a Raspberry Pi 5? I've been thinking about a design that runs some robotic services natively, with a user-facing Android inside of a resource-constrained VM.

[ Parent | on HN ]

Re:Google Pixels are no longer the AOSP reference device by moonshot5 on Thursday June 12, 2025 @01:36PM (#44260411)

Android can run natively on x86_64. The ART folks spent quite a bit of time getting this to work.

A lot of our CI targets run android in this configuration.

[ Parent | on HN ]

Re:Google Pixels are no longer the AOSP reference device by nrclark on Thursday June 12, 2025 @01:43PM (#44260493)

Understood. I'm actually thinking about a product design for an aarch64-based industrial controller.

I'd want to run all of the machine interfaces directly on Linux, but am interested in using Android for everything user-facing. Could I get away with running Cuttlefish in KVM (on an aarch64 SOC) and get OK performance? I'm thinking that it could be a good way to keep the important stuff isolated.

[ Parent | on HN ]

Re:Google Pixels are no longer the AOSP reference device by moonshot5 on Thursday June 12, 2025 @02:08PM (#44260768)

Only one way to find out. :)

[ Parent | on HN ]

Re:Google Pixels are no longer the AOSP reference device by yjftsjthsd-h on Thursday June 12, 2025 @04:58PM (#44263127)

You might also consider waydroid for that

[ Parent | on HN ]