Meta has unexpectedly enabled Android Debug Bridge (ADB) access on its discontinued Portal line of smart display devices. This development, announced by Andrew Bosworth (Boz) on Facebook, opens up possibilities for developers and hobbyists to explore and potentially repurpose the hardware.
What Happened
Andrew Bosworth announced the change on Facebook, stating that the developer tools recently released for Meta Quest devices now also function on Portal devices. He showcased a custom “home hub” application he built using these tools, encouraging others to experiment. The announcement was accompanied by a video demonstration of the functionality. The Portal devices in question are those that Meta has already deprecated, meaning they are no longer receiving official software updates.
Why It Matters
Enabling ADB access is significant for several reasons. First, it breathes new life into hardware that was previously becoming obsolete. While Meta has stopped actively supporting Portal, this move allows the community to potentially extend its lifespan through custom software. Second, it demonstrates a potential shift in Meta’s approach to its hardware ecosystem. Historically, Meta (and Facebook before it) has maintained tight control over its devices’ software environments. Opening up ADB access, even on deprecated devices, suggests a willingness to embrace a more open and developer-friendly approach.
For developers, this provides a new platform for experimentation. Portal devices have unique hardware configurations – cameras, displays, and speakers – that could be leveraged for various projects. It’s currently uncertain what level of access ADB provides beyond basic debugging and shell access, and whether deeper system-level modifications will be possible. The shared toolset with Quest suggests some level of compatibility and potentially porting of applications, though significant adaptation may be required. It is also unclear if this change will be extended to currently supported devices.
What To Watch
It remains to be seen how the developer community will respond to this change. The primary area to watch is the emergence of custom software and projects built specifically for Portal devices. The extent of ADB access and the feasibility of porting Quest applications will be key factors. Furthermore, it will be interesting to observe whether Meta expands this approach to other deprecated or current hardware. Finally, it’s worth monitoring if Meta provides any official documentation or support for developers utilizing ADB on Portal devices.