We’ve all got that drawer. You know the one—the tech graveyard filled with old smartphones, tablets, and abandoned smart home devices that the manufacturer decided to stop supporting. Usually, when a company deprecates a hardware line, those devices become expensive paperweights. But every now and then, the tech gods (or rather, a team of engineers under pressure from the open-source community) throw us a bone.
Recently, Meta quietly released a software update for its deprecated Portal smart displays that enables Android Debug Bridge (ADB) access. Yes, you read that right. The highly capable, camera-equipped, touchscreen-laden smart screen sitting in your closet can now be unlocked, poked, prodded, and repurposed into a dedicated developer tool, a local smart home dashboard, or a custom Linux terminal.
For developers, this isn't just about saving $100 worth of hardware from the landfill. It’s a masterclass in how we can salvage proprietary consumer hardware and bend it to our will. In this post, we're going to dive into what this update means, how to unlock your Meta Portal, and how to write and deploy a custom lightweight web app to turn this abandoned screen into a real-time DevOps dashboard.
The Hardware: What Are We Working With?
Before we plug things in, let's look at what is actually under the hood of a typical Meta Portal (specifically the Portal Mini or Portal TV). These devices aren't just cheap IoT gadgets; they actually pack some decent punch:
- Processor: Realtek RTD1295 or MediaTek MT8183 (octa-core ARM processors)
- OS: Portal OS (a heavily customized fork of Android/AOSP)
- Display: Decent IPS panels (ranging from 8 inches to 15 inches)
- Peripherals: High-quality far-field microphone arrays, wide-angle cameras with built-in pan/tilt logic, and surprisingly good speakers.
For years, this hardware was locked behind Meta’s proprietary launcher. With ADB now officially enabled by Meta for end-of-life devices, we have a direct bridge to the underlying Android system. We can install custom APKs, bypass the default setup screens, disable tracking telemetry, and utilize the screen for our own developer payloads.
Step 1: Enabling ADB and Connecting to the Portal
First things first, you need to make sure your Portal is updated to the latest available firmware release. Meta pushed the final update containing the ADB toggle to devices automatically, but if yours has been sitting offline, boot it up, connect it to Wi-Fi, and let it pull the latest OTA (Over-The-Air) update.
Finding the Golden Toggle
Once updated, navigate to the device settings. The path may vary slightly depending on your specific model, but generally, you will follow these steps:
- Go to Settings > About.
- Find the Build Number and tap it repeatedly (usually 7 times) until a toast notification pops up saying, "You are now a developer!"
- Go back to the main Settings menu, where you will now see Developer Options.
- Toggle on USB Debugging (ADB).
Connecting via your Terminal
Grab a USB-C cable, hook the Portal up to your development machine, open your favorite terminal, and make sure you have the Android SDK Platform Tools installed. Let's see if the device is listening:
$ adb devices
List of devices attached
192.168.1.150:5555 device
3948ACBD92010A deviceIf you prefer a wireless connection (highly recommended for smart displays sitting on your desk), you can connect over your local Wi-Fi network. Find your Portal's IP address from your router or the device's Wi-Fi settings, and run:
$ adb tcpip 5555
$ adb connect [YOUR_PORTAL_IP]:5555
connected to 192.168.1.150:5555Boom. You are in. You now have root-adjacent shell access to a highly optimized ARM-based smart display.
Step 2: Cleaning the Slate (Debloating)
Portal OS is filled with Meta services, Facebook login prompts, and video-calling frameworks that we no longer need. Let's clear some headspace on this device. We can use the ADB shell to disable package managers we don't want running in the background consuming CPU cycles.
Run the following commands to see what's running and disable the default launcher and system bloat:
# Access the shell
$ adb shell
# List all installed Meta/Facebook packages
pm list packages | grep 'facebook'
# Disable the proprietary launcher and system apps safely
pm disable-user --user 0 com.facebook.portal
pm disable-user --user 0 com.facebook.workplace.portal
pm disable-user --user 0 com.facebook.weaverNote: Be careful not to disable core system packages like com.android.systemui unless you plan on installing a complete custom ROM alternative.
Step 3: Deploying a Custom DevOps Dashboard
Now that we have a clean slate, what should we build? Let's turn this screen into a dedicated "DevOps Command Center." We'll write a simple, lightweight Android App wrapper that boots directly into a fullscreen WebView pointing to a local Grafana dashboard, Home Assistant, or a custom React-based build pipeline monitor.
The Android Wrapper (Java/AOSP)
Instead of writing a massive Android app, we can use a lightweight single-activity application containing a Fullscreen WebView. Here is the minimal, performant Java code for your MainActivity.java:
package com.sysseder.devdashboard;
import android.app.Activity;
import android.os.Bundle;
import android.view.View;
import android.webkit.WebSettings;
import android.webkit.WebView;
import android.webkit.WebViewClient;
public class MainActivity extends Activity {
private WebView myWebView;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
// Hide the status bar and navigation buttons for a kiosk look
getWindow().getDecorView().setSystemUiVisibility(
View.SYSTEM_UI_FLAG_FULLSCREEN |
View.SYSTEM_UI_FLAG_HIDE_NAVIGATION |
View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY
);
myWebView = (WebView) findViewById(final_webview);
WebSettings webSettings = myWebView.getSettings();
webSettings.setJavaScriptEnabled(true);
webSettings.setDomStorageEnabled(true);
// Point this to your local Grafana, Prometheus, or Custom UI dashboard
myWebView.setWebViewClient(new WebViewClient());
myWebView.loadUrl("http://192.168.1.50:3000/d/devops-metrics");
}
}Deploying the Build to the Portal
Compile your project into an APK (let's call it devops-dashboard.apk). To install it directly onto the Portal over the air, simply run:
$ adb install devops-dashboard.apk
SuccessTo launch your new application immediately via the terminal, trigger the Android Activity Manager (am):
$ adb shell am start -n com.sysseder.devdashboard/.MainActivityYour Portal screen will instantly refresh, bypassing the Meta environment entirely, and display your real-time developer metrics dashboard!
Step 4: Automating Boot and Power Management
Since this is a desktop utility, we want it to behave like a piece of infrastructure. That means two things: booting our app automatically when the device receives power, and managing the screen timeout so it doesn't burn out or stay bright red at 3 AM.
Setting our App as the Default Launcher
We can tell the Android operating system to treat our custom WebView app as the default home screen. Run this ADB command:
$ adb shell cmd package set-home-activity "com.sysseder.devdashboard/.MainActivity"Now, if the device reboots due to a power outage, it will bypass the setup screen and boot straight into your dashboard.
Controlling Screen State programmatically
Want to turn the screen off when you leave your desk? You can integrate your Portal into your CI/CD pipelines or cron jobs. Send a keyevent to simulate the power button over SSH/ADB:
# Turn screen off / toggle sleep state
$ adb shell input keyevent 26Or write a quick bash script on your local server to wake the Portal up only when a build fails:
#!/bin/bash
# wake_portal.sh
# Check if screen is off, if so, turn on and show red alert page
SCREEN_STATE=$(adb shell dumpsys power | grep "mWakefulness=")
if [[ "$SCREEN_STATE" == *"Asleep"* ]]; then
echo "Build failed! Waking up Portal..."
adb shell input keyevent 26
adb shell am start -a android.intent.action.VIEW -d "http://192.168.1.50:3000/build-fail-alert"
fiWhy This Matters to the Developer Community
The Meta Portal ADB update is a win for the Right to Repair and hardware preservation movement. Millions of these devices were manufactured, featuring incredible microphones, speakers, and cameras. Unlocking them via ADB allows developers to build local voice assistants (like Rhasspy or Mycroft), privacy-focused smart home hubs, or dedicated hardware status monitors without relying on any external cloud infrastructure.
It teaches us a valuable lesson: the line between "consumer appliance" and "general-purpose computer" is purely software. With a shell, some creative code, and a USB cable, we can extend the lifecycle of silicon, reduce e-waste, and get some awesome, free hardware on our desks in the process.
Conclusion: What Will You Build?
Do you have an old Meta Portal gathering dust in a closet or under your desk? Now is the time to fish it out, plug it into your development machine, and run adb devices. Whether you turn it into a dedicated Spotify player, a Git commit tracker, a Home Assistant monitor, or a camera feed for your 3D printer, the hardware is officially yours again.
What are you planning to run on your unlocked Portal? Have you run into any issues bypassing the Meta setup wizard? Let’s talk about it in the comments below!