Meta has lifted the ADB support for its long‑abandoned Portal line, allowing developers to debug and deploy apps on the legacy hardware. The move signals a shift toward keeping older VR platforms viable for third‑party content. Developers who have built experiences for Portal can now use standard Android tooling.

Portal devices first launched in 2019, but their software stack has since been phased out. By re‑enabling ADB, Meta equips engineers with a familiar interface to push updates, capture logs, and profile performance on the headset’s Snapdragon XR2 chip. The change reduces friction for sustaining legacy titles in a market that favors newer hardware for developers and users today.

The announcement follows a surge in demand for cross‑platform toolchains that let creators target both current Meta Quest models and older Portal units. Developers can now leverage Unity, Unreal, or native Android SDKs to build experiences that run on the same device under a unified debugging workflow for creative teams worldwide.

By restoring ADB, Meta signals a commitment to backward compatibility and eases maintenance for studios that invested in Portal. The change may prompt developers to revisit older projects, keeping Portal content alive on a single hardware platform. This decision helps maintain a steady user base for Meta’s legacy hardware and preserves investment for third‑party developers, potentially extending the life cycle of older VR titles.