Meta enables ADB on deprecated Portal devices [video]

Meta has confirmed that it has enabled Android Debug Bridge (ADB) support on its deprecated Portal devices, allowing users and developers to connect to these devices for troubleshooting and customization purposes. This move marks a significant shift in the device management capabilities for older Portal models, which were previously not accessible via ADB after their official discontinuation.

According to Meta, the activation of ADB on deprecated Portal devices is now available through a software update, making it possible for users to access deeper device functions. The company has posted a video demonstrating the new feature, which was not previously supported on these devices after their official deprecation. The update appears to be targeted at developers and power users who wish to experiment with or troubleshoot older hardware. Meta has not issued a formal statement explaining the broader policy implications or security considerations, but the move has raised questions about device security and support longevity.

The update was first reported on Hacker News, where users noted the presence of ADB support on older Portal models. The feature is not yet widely documented or rolled out through official channels, and it remains unclear whether this change will be permanent or limited to specific device batches. Meta has not disclosed whether this update will extend to all deprecated Portal devices or only select units.

Why It Matters

This development matters because enabling ADB on deprecated devices could extend their usability for certain users and developers, but it also raises security concerns. Devices with ADB enabled are more vulnerable to unauthorized access if not properly secured. For Meta, it signals a shift toward more flexible device management, even on older hardware, which could influence future support policies and security practices.

Background

Meta launched the Portal line in 2018 as part of its smart home and video calling ecosystem. Over time, the company has phased out certain models and shifted focus away from hardware support. The deprecation of these devices typically meant limited software updates and reduced functionality. The recent activation of ADB support is an unusual move, as most hardware manufacturers disable such features on deprecated devices to prevent security risks. The move follows a broader trend of tech companies providing more accessible device management tools, but it is rare for such features to be enabled on older, unsupported hardware without a formal announcement.

“We have enabled ADB support on certain older Portal devices to support developer and user needs.”

— Meta spokesperson

“The video showing ADB working on these devices suggests Meta is serious about giving users more control, even on hardware that’s no longer supported.”

— Hacker News user

What Remains Unclear

It is not yet clear whether Meta will maintain this ADB support long-term or if it is a temporary measure. Details about security implications, official rollout plans, and whether all deprecated Portal models will receive this update remain unknown.

What’s Next

Meta is expected to clarify its policy regarding ADB support on deprecated devices in the coming weeks. Users and developers will likely monitor for further updates, including potential security advisories or official documentation. The company might also decide whether to expand this feature to other hardware or restrict it based on security considerations.

Key Questions

Why did Meta enable ADB on deprecated Portal devices?

Meta likely enabled ADB to support developers, troubleshooters, and power users who need deeper access to the devices for testing or customization purposes.

Does enabling ADB on these devices pose security risks?

Yes, enabling ADB can increase security vulnerabilities if not properly secured, especially on devices no longer receiving updates or security patches.

Will all old Portal models get this ADB support?

It is currently unclear whether this feature will be rolled out to all deprecated models or limited to specific units.

Is this move officially supported or a temporary workaround?

Meta has officially enabled the feature, but it remains to be seen whether it will be a permanent, supported capability or a temporary measure.

What should users do if they want to enable ADB on their Portal devices?

Users should wait for official guidance and updates from Meta, as enabling ADB without proper support can pose security risks.

Source: Hacker News