Possible ‘Nexus Player’ successor shows up in AOSP running Android Q

by kawshik201
rawd_unda

Everyone still using their NP(s) daily, and have not bought into either a MiBox or Shield raise their hand.

513

I know I already wrote that at r/android, but I think elfin is just a code name for a Broadcom SoC or a device running their SoC, like the latest Dual-Core BCM72604 that's not yet available on any Android TV Set-top box (but will soon be).

Check Geekbench, you can find a lot of 'broadcom elfin' (dual-core) results.

With 7.1 https://browser.geekbench.com/geekbench3/8415671 (result date: Jul 28, 2017)

And 8.0 https://browser.geekbench.com/geekbench3/8558412

Lots of different Broadcom code names by the way, like elfin, cypress, prjo, pearlb (this one is a Technicolor STB), avko (BCM 7251/2S), etc.

blusky75

If it's anything like the rest of the pixel hardware lineup, I would expect a device priced like a shield TV but with a fraction of the features

ProfitOfRegret

Maybe they could call it the Nexus Player Q, or something like that.

mikeydangerous

Android Q? That implies 1) Google is already working on Q before finishing P, and 2) that the next Player (likely a Pixel Player, not a Nexus) won’t be out til late 2019 at the earliest. Not cool.

TheCrystalSteven

Honestly, I think when it says "Second attempt for Q", it's supposed to refer to the Nexus Q, as that was their 1st attempt. So I think it has nothing to do with Android Q, but just referring to a past failed product. Just my opinion.

amionreddityet

I can't figure out what delicious treats might start with a Q.

OttoNormalRedditor

So the only hint that this could be an Android TV device is a commit fixing a bug in the Nexus Player and this new device?