Some commercial signage hardware ships as a sealed Android media player running a locked-down build. It usually does have a handful of apps you can open — typically a browser, a file manager, and a camera — but no Google Play Store and no built-in way to install new apps (no sideload/APK-install function exposed in Settings). A common example: a customer installs a Keyser all-weather display in their drive-thru, then asks us to supply Menuboard Manager as the CMS behind it — including using one of the drive-thru screens (in full or in part) as a customer-facing order confirmation display tied to Toast. When you go to install the Menuboard Manager Player App the normal way, the Play Store does nothing.

Real-world example. The Keyser drive-thru units run a Quber media player (model QUBER_QR1G_M110S, Android 9). Settings exposes the usual Android sections plus a Quber entry (Product Version, ADB, Display Rotation), and the device ships with about 7 apps — including Lightning (the default browser), Files, Explorer, and a camera. Bluetooth is available under Connected devices. There is no Play Store and no in-Settings way to install an APK, which is what makes the methods below necessary.

This guide explains why that happens and walks through the two ways to get Menuboard Manager onto that kind of device:

The short version: Many low-cost commercial signage sticks and media boxes run uncertified Android without Google Mobile Services (GMS), so the Google Play Store can't install apps on them — and any advice to "install it from the Play Store in the browser" will fail. Because Menuboard Manager is our own app, you don't need the Play Store at all — sideload the signed APK and it runs regardless of GMS certification. Easiest is to download the APK straight from a hosted URL in the device browser (or from a USB stick); ADB is the fallback for fully locked-down units. If ADB-over-network refuses the connection, flip the device to network mode once over USB with adb tcpip 5555.

The Play Store isn't a single standalone app — it depends on several Google Mobile Services (GMS) components (Google Play Services, Google Services Framework, and the Play Store client) working together, installed and licensed via Google's device certification.

Low-cost commercial signage players and generic Android "media boxes" often ship with an uncertified AOSP (Android Open Source Project) build to avoid Google's licensing costs. On those devices:

If you open the Play Store in the device's web browser (play.google.com), sign in, and click Install — or see the button change to "Install on additional devices" — and nothing happens, that's the tell.

The web Play Store doesn't download and install apps itself. It sends an install request to a registered, GMS-certified Play Store app running on the device, which then performs the install. If the signage player has no such on-device Play Store, there's nowhere for the request to land, so the button silently does nothing. This is not a permissions problem — there's simply no receiver.

Takeaway: Stop fighting the Play Store on a device that was never certified to run it. Sideload instead.

Because Menuboard Manager is our own application, our support team can provide a signed release APK. Sideloading it bypasses the Play Store and GMS entirely, so it works even on uncertified hardware.

Need the APK? Contact support if your device doesn't have access to the Google Play Store, the Amazon Fire TV app store, or the Amazon Signage store and you need to side-load the APK. The Menuboard Manager Support Team can provide the APK for download. Include the device make/model and Android version so we send a build compatible with it.

Setup tip: A cheap wireless USB mini keyboard/trackpad (~$12) makes navigating the device's Settings, browser, and file manager far easier than fighting the screen's remote as a mouse. Two catches on signage players: the Android player often has only one usable USB port (the other USB ports belong to the display itself), and a wireless keyboard's USB receiver dongle occupies that one port — so you can't have the keyboard and a USB thumb drive plugged in at once. A Bluetooth keyboard/trackpad sidesteps that conflict if the device supports it.

There are three ways to get the APK onto the device. Path A (browser download) is the recommended procedure for the Keyser/Quber units — it needs no computer and, crucially, no free USB port. Paths B and C are fallbacks.

Field note — sideloading can fail entirely on sealed units. On at least one real install, none of the three paths below worked: the Android player had only one usable USB port, which was occupied by the wireless keyboard needed to control the screen (so no USB drive could be attached at the same time); when a USB drive was tried, the player didn't detect the drive or the APK on it; and the network/ADB pivot was blocked, apparently by closed ports. If you hit the same wall, don't burn hours on it — go to the browser / PWA fallback, which is often the only thing that will get a screen live on hardware this locked down.

Once support has sent you a download link for the APK, you can install without a computer at all. This is the expected method for the customer to run on the Keyser/Quber units.

The exact wording varies slightly by device and Android version, but this flow is universal for sideloading:

Prefer Path A instead. On the Keyser/Quber players there is only one usable USB port, and it's occupied by the wireless keyboard/trackpad's USB adapter you need to control the screen. To use a flash drive you'd have to unplug that adapter — leaving you driving the entire install with the remote control as a mouse, which is extremely slow and painful. Since Path A (browser download) needs no USB port at all, use it whenever the device can reach the download link support sent you. Only fall back to USB if the browser download is impossible (e.g., no network) and you have a Bluetooth keyboard so the USB port is free.

If you must use USB anyway:

Watch for two failure modes. (1) If the player's single USB port is taken by your keyboard dongle, you can't attach the drive at the same time — see the setup tip above (use Bluetooth, or the remote as a mouse). (2) Some locked-down players won't detect the USB drive at all (the File Manager shows nothing when you plug it in). Try re-formatting the drive as FAT32, a different/smaller drive, or a different port. If the player simply never mounts USB storage, skip to Path C or Method 2.

Use this when you can't get an APK onto the device directly and you have a computer available.

Heads-up: on some sealed units this path is a dead end too — the ADB TCP port (5555) is firewalled/blocked, or the on-screen toggle never opens a network listener even after the USB tcpip step. If you exhaust the steps below without a connection, it's not worth grinding on — use Method 2.

On a Mac, the easiest route is Homebrew:

That gives you the adb command without installing all of Android Studio.

On the signage player (a wireless keyboard/trackpad helps here):

While you're here, note the exact chipset and Android version — some of these boxes report a userdebug build, which is generally more permissive about sideloading, and knowing the Android version tells us which APK build to send you.

Look in the device's Network / Ethernet or Device Info screen for its IPv4 address (something like 10.10.10.105). Wired Ethernet is more reliable than Wi-Fi for this.

Sanity-check the network config while you're here. On one install the device's IP was 10.10.10.105/24 (subnet 10.10.10.0) but the gateway read 10.1.10.1 — a different subnet the device can't actually route to. A mismatched IP/gateway pair like that will break internet access and ADB reachability, so confirm the gateway is on the same subnet as the device's IP.

If you see the device listed as device, skip to Step 6.

Connection refused (not a timeout) is actually good news: your computer is reaching the device, but nothing is listening on port 5555. You can confirm exactly that:

The cause: on many of these OEM signage builds, the on-screen "ADB" toggle only enables USB debugging — it does not start a TCP listener. Rebooting won't help, because the network daemon was never turned on. You have to flip it to network mode once over USB:

No accessible USB port? Fully sealed installs sometimes expose USB debugging in settings but give you no port to use it. In that case, ask support whether the device vendor offers a provisioning / MDM tool to push the APK remotely.

A Success message means it's installed. Common failures:

Even though the device has other apps you can open, a locked-down launcher may not surface a newly sideloaded app in its app list. If it doesn't show up, launch it from your computer instead:

Once it opens the first time, Menuboard Manager displays "Installation Complete. Unit Activation Required!" with an activation code. Provide that code to support to activate the unit — same as any other Android install (see Android — Device Setup, Provisioning & Troubleshooting).

If the customer can't complete the sideload on their own, Menuboard Manager Support can remote in and install the APK for them. The lightweight tool for this is TeamViewer QuickSupport (no install/admin rights needed on the far end — it just runs and shows a session ID).

Screen sharing/remote control on Android often needs an add-on for the device brand (e.g., a "TeamViewer Add-On:

" from the same source) before full remote control works — install that too if QuickSupport prompts for it.

When sideloading fails — and on the most locked-down units it does (see the field note above) — you can point the device's built-in browser at a hosted menu page and run it full screen. This is what actually got a screen live in the field example where every sideload path was blocked, so treat it as a real option, not just a placeholder.

Understand the trade-off: this shows a hosted page, so you don't get the full Player App's remote management, unit activation, on-screen alerts, or live POS-driven updates. It's ideal as an immediate stopgap, and it's an acceptable longer-term answer when the hardware genuinely can't run the app — but move to the sideloaded Player App (Method 1) whenever the device allows it.

The single biggest gotcha here: Immersive Mode only hides Android's own system bars — it does not hide the browser's address bar. Getting rid of the address bar is up to the browser.

Many signage players ship a lightweight built-in browser rather than Chrome — for example Lightning (a minimal open-source Android browser). In the field, the built-in Lightning browser displayed the hosted menu image fine, but could not hide its address bar: Immersive Mode removed the bottom navigation bar, yet the browser's URL bar stayed on screen. Lightning does not support Chrome's installable-web-app flow, so the manifest trick below won't help it.

Your options, best first:

This section applies once you have Chrome on the device. A plain "Add to Home Screen" shortcut still shows the address bar, because the page isn't an installable web app. To get a truly clean full screen, the hosted page needs a web app manifest that requests fullscreen display.

Note: a bare image URL (like taco1.jpg) has no <head> to attach a manifest to. Wrap the image in a minimal HTML page first — e.g., a page whose body is just <img src="taco1.jpg" style="width:100%;height:100%;object-fit:contain"> — then point the device at that page and add the manifest to it.

Add to the page's <head>:

And create manifest.json alongside it:

The key field is "display": "fullscreen" — that's what tells Chrome to drop the address bar when the page is launched from the home screen. After adding it:

Remember the trade-off: the browser fallback shows a hosted page with no connection to Menuboard Manager's management, playlists, alerts, or live Toast pricing. Move to the sideloaded Player App (Method 1) whenever the device allows it.

In drive-thru setups, customers often want one of the screens to double as a customer-facing order confirmation display — showing the guest their itemized order and running total as it's rung in. That's a separate, POS-driven feed from the Menuboard Manager CMS content:

We're a Toast Development partner. Menuboard Manager has integrated directly with Toast for years, so the CMS content and the POS-driven order confirmation feed are designed to live side by side in the same install.

The screen used for order confirmation can also have Menuboard Manager installed on it, so the customer can show CMS content on it instead of order confirmation whenever they want. In that arrangement:

⚠️ WARNING: NEVER connect HDBaseT devices to a network switch. The Cat6 run between the HDBaseT sender and receiver is point-to-point only — it carries HDMI-over-Cat6, not Ethernet. Plugging either end into a network switch can damage the equipment and will not work.

Plan which physical screen carries which feed before final install, especially outdoors where sunlight readability and weatherproofing matter.

Menuboard Manager runs on a wide range of Android media players and smart displays, but not all Android devices are fully supported. Low-cost, non-commercial, or uncertified signage boxes may show app freezing/crashing, unreliable connectivity, or kiosk/auto-start incompatibilities. Your device must run Android 8.0 or later. For a guaranteed-supported setup, use qualified commercial hardware — see Supported Hardware and the Android — Supported Devices Disclaimer.