Meta published developer guidance showing that its new Quest and Horizon OS tooling also works on discontinued Portal devices, and users can now enable Android Debug Bridge through settings to sideload software. Portal was a line of video-calling smart displays launched in 2018. People described them as unusually good hardware for family calling, especially for older relatives and pandemic-era home use, but said the product slowly lost features after Meta killed it and pushed its attention into VR and Horizon. That set the tone here. People were glad ADB is finally available because it gives these devices a second life as home dashboards, kiosks, speakers, and custom family tools. One commenter had already turned old Portals into Home Assistant dashboards, and another shared a kids routine board app running on the hardware.
The sharper signal was that nobody saw this as a principled embrace of repairability. Multiple former employees said people inside Meta had been asking for years to open deprecated devices, both to avoid e-waste and to let the community adopt the hardware. They say those requests were blocked, reportedly because unlocking the platform risked exposing device keys, and because Portal became collateral damage once the company reorganized around AR and VR. Former employees painted Portal as a genuinely liked product that got trapped inside Meta politics. It was overbuilt, sold at a loss, hit the market just as Cambridge Analytica cratered trust in Facebook-branded in-home cameras, and then got folded under leaders who cared more about Horizon and headset strategy than about making Portal a durable standalone platform.
That led to a broader conclusion about Meta’s product machine. The company came off as highly centralized around executive whims while still being chaotic below that level. Several former employees described a flat org where projects not blessed from the top drift, while pet projects get distorted by leadership priorities. In that framing, the ADB change is good news for owners but also an indictment. A feature that could have extended the useful life of solid hardware for years only appeared once it became amusing and strategically adjacent to Meta’s current AI tooling push. The dominant read was simple: great for hackers, bad as policy, and a case study in how capable devices become waste when no one in charge values stewardship.
If you own deprecated Android-based hardware, this is a reminder to check whether a vendor has quietly exposed enough access to turn it into a kiosk, dashboard, or dedicated appliance. For product leaders, the stronger lesson is that abandoned but still-capable devices create goodwill and secondary ecosystems when you open them before users have already written them off.
Mostly positive about getting ADB access and being able to reuse good hardware, but frustrated that it took this long and seems driven by internal whim and AI marketing rather than any real commitment to openness, repairability, or long-term product support.
Key insights
01
Security keys were a real blocker, not a fake excuse
The claim about embedded keys changes the story from "Meta just flipped a switch" to "Meta had to decide the residual security risk was finally acceptable." People pointed out that many Android vendors handle this by wiping secrets during bootloader unlock, and others noted that shipped devices do not automatically leak private keys because hardware protection and asymmetric cryptography can still keep them hard to extract. That makes the missed opportunity look more like lack of will to engineer a proper decommissioning path than pure technical impossibility.
If you ship locked hardware, design an end-of-life unlock path from the start. Wiping device secrets and documenting what trust guarantees are lost is far better than treating deprecation as a permanent lock-in state.
Portal was not just oddball hardware looking for a purpose. People who used it for elderly relatives, grandparents, and pandemic family calling described it as one of the best consumer video communication devices they had owned. Former employees added that there was also a credible workplace conferencing path, including work on mobile device management support tied to Workplace. That makes Portal look less like a product nobody wanted and more like a product Meta stopped believing in before it had built the surrounding platform and distribution to sustain it.
When a device wins hard in one concrete workflow, preserve that lane even if the broader strategy changes. Niche but loved products can justify a long tail if you keep the core path stable and stop stripping features.
Meta looked centralized at the top and leaderless below
Former employees described a company where Zuckerberg's interests could instantly reshape priorities, but anything outside those focal areas ran with weak executive ownership. That is a bad combination. It leaves teams exposed to sudden top-down pivots without giving them a stable operating mandate the rest of the time. The result, as described here, was constant initiative churn, poor product continuity, and engineers discovering major decisions from leaks while leadership obsessed over cosmetic details on pet projects.
For founders and executives, this is a warning that "flat" can become organizational drift if only the CEO provides real coordination. A stable mission, product ownership, and explicit end-of-life policy matter more than bursts of top-level enthusiasm.
The immediate value is not waiting for a full bootloader unlock. People are already sideloading Home Assistant and building purpose-built household apps on stock Portal hardware. For a cheap secondhand device with a decent screen, speakers, and stand, that is enough to turn abandoned consumer electronics into a kiosk, dashboard, or family display. The new opening is useful now, even if root and custom Linux images never arrive.
Do not wait for perfect openness before testing reuse ideas on deprecated devices. Sideloading alone may be enough to validate internal tools, wall dashboards, or dedicated single-app appliances at very low cost.
Turning Portal into a kids routine board got praise, but the pushback was practical. A paper chart with magnets can already handle much of that workflow. The software only earns its keep once it tracks points over time, rankings, and rewards. That is a useful check on the wider excitement around repurposing. Not every rescued device becomes meaningfully better than a simpler object.
Before you invest time repurposing old hardware, define the feature that truly requires a screen and software. If the digital version does not create tracking, automation, or remote management, the hack may be more novelty than value.
Warnings about an end-of-life Android build drew a more technical correction. The claim was that old Android versions are not automatically wide-open from the network side because the external attack surface is fairly small and SELinux still makes post-compromise escalation painful. The bigger risk is local app and sandbox escape bugs, plus the baseline trust problem of Meta's stock firmware on a camera device. That narrows the threat model. These devices are not harmless, but they are also not instant liabilities just because the version number is old.
Treat deprecated Android hardware with a specific threat model, not generic panic. Network isolation and careful app choices may be enough for kiosk use, but stock firmware from an untrusted vendor is still the bigger strategic risk.
Open bootloaders alone will not create second lives
Calls for governments to require unlocks met a reality check from people who have tried to keep old Android devices alive. Even with open bootloaders and source code, device fragmentation, region-specific variants, and stale driver stacks make long-term support brutally hard. Samsung was cited as a worst-case example because each model splinters into multiple SoCs and market-specific builds. So mandatory unlocking helps, but it does not magically produce a thriving aftermarket software ecosystem.
If you want regulation to reduce device waste, do not stop at bootloader access. Driver release, variant simplification, and upstream support windows matter just as much as the legal right to unlock.