Set the signage player as the Android home app to bring the show up full screen at power-on. Treat automatic startup, access restrictions, local content, and recovery as separate requirements, then check each on the intended installation.
Set the signage player as the Android home app so the display opens the approved signage application at power-on instead of presenting a general launcher. Treat that as a startup setting, not proof that every route to other applications is blocked. For a single-purpose display, you also need local content, the correct screen settings, a documented maintenance route, and separate checks for startup and recovery.
Make the player the home app
The home app is the application Android uses for its home screen. Assigning that role is different from opening an application manually or making its window full screen.
The signage player supports being set as the home app. In that configuration, it brings the show up full screen at power-on, without a launcher or keyboard. Use the documented home-app selection procedure for the installed Android version. Settings labels can differ, so do not assume that a menu path from another device applies.
Before selecting the home app, load the approved content and check the player's settings. Otherwise, an application can start correctly without having the intended show ready to display.
Keep the startup arrangement simple. If a different application must be the approved signage app, confirm that application's documented startup method and compatibility with the device. Do not assume that every Android application can take the home-app role.
Separate full screen from access control
Three different requirements are often grouped under the word kiosk:
- Automatic startup: the intended application opens when the display starts.
- Full-screen presentation: the show occupies the screen rather than appearing inside a general desktop interface.
- Restricted access: ordinary interaction cannot open unapproved applications or settings.
Meeting the first two does not establish the third. A home-app assignment alone is not evidence that system navigation, notifications, connected input devices, or other applications are restricted.
The player has a hidden, PIN-protected maintenance menu. That protects access to the player's menu; it should not be treated as a claim that the entire Android device is locked down.
If you need enforced application restrictions, use a documented device-management or kiosk-management arrangement that supports the chosen hardware and Android version. Confirm its capabilities before deployment. Do not disable system protections or remove essential system components to imitate a managed-device configuration.
Prepare content before relying on startup
An application opening automatically is only useful if it has something suitable to play. Load a small, known content set first, then check the final playlist before installation.
The player accepts images and video from microSD or USB and keeps a copy in internal memory. It can play without a network connection. For video, H.264 MP4 is the recommended format. JPG, PNG and WebP are supported image formats; a presentation file or PDF is not a playable substitute.
Keep these two questions separate:
- Does Android open the correct application?
- Does that application have the approved content available locally?
Optional HTTPS sync adds a content-update path, not a requirement for local playback. Establish local playback before adding scheduled downloads. The offline or cloud signage guide covers the broader choice between local content and a network-managed workflow.
Record the playlist revision used for acceptance checks. A startup check with temporary content does not establish that the final media files display correctly.
Understand an apparently blank screen
The player can be open even when no image is visible. Its daily on and off settings affect what you see after startup.
Outside the configured hours, the player shows black at minimum brightness. The application cannot switch the backlight off. That state is therefore different from removing power from the display. Check the configured hours and the device clock before treating a dark presentation as a startup fault.
Other presentation settings also matter:
- Set portrait or landscape rotation to match the physical installation.
- Check the first slide for readable text and correct orientation.
- Remember that videos play muted unless sound is enabled in settings.
- Check that the intended opening content is not itself a black frame or a long blank introduction.
Use screen behavior, not sound alone, to judge whether the show has started. A silent video may be operating exactly as configured.
Check startup and recovery separately
A normal power-on check and an application-recovery check answer different questions. Neither should be inferred from the other.
For normal startup, observe the installed display after a normal shutdown and power-on. Record whether the signage app opens without manual selection, whether the intended content appears, and whether rotation and scheduled screen behavior match the configuration. Do not count a manually opened application as an automatic-startup result.
For local playback, make the network unavailable through an approved maintenance procedure, then observe playback using content already copied to internal memory. This checks whether the installation depends on an online page or service that was not part of the intended local workflow.
For application-crash recovery, the player is designed to relaunch itself and return to playback. That is a separate behavior from being selected as the home app. Only exercise an application-failure check through a documented, authorized method. Do not change system protections or use undocumented commands to manufacture a result.
What this page describes is how the software is designed to behave. It has been tested on the Android 12 emulator, and testing on a real unit is pending.
Keep an acceptance record for the actual installation:
- The selected home application and software version.
- The content revision and loading method.
- The observed normal power-on behavior.
- The configured display hours, clock and rotation.
- Any recovery checks performed and their observed results.
- Any checks that remain outstanding.
If the display repeatedly loses power, investigate the supply and wiring rather than changing application settings. The DC power wiring guide covers that separate installation task. Do not interrupt a software update or a content-copy operation as a startup test.
Preserve an authorized maintenance route
A single-purpose screen still needs an approved way to change content and inspect settings. Establish that route before restricting access.
Use the player's PIN-protected menu for its documented maintenance functions, including reloading content and checking the screen. Store the chosen PIN through your normal credential-management process. Do not put it on a label visible beside the display or include it in a publicly accessible installation record.
If access is lost, follow the documented reset or recovery process for the affected software or device. Do not rely on guessed credentials, undocumented passwords, or changes intended to bypass protection.
Record how to return the display to its intended startup configuration after maintenance. A screen left in settings may be powered and responsive but still unsuitable for its signage job.
Know when this startup method is not enough
A home-app configuration suits a display whose job is to open a local signage show without routine interaction. It does not, by itself, establish a security boundary for an unattended interactive terminal.
Choose a different arrangement when you need enforced restrictions on applications, centrally administered access policies, or documented control over every available navigation route. Confirm those requirements against the management system and device documentation, rather than assuming that full-screen playback provides them.
A signage application is also not a machine safety function. Do not make safe machine operation depend on whether a sign starts, remains visible, or accepts input.
For the wider hardware and software selection, use the digital signage player guide. For this narrower startup decision, the acceptance question is straightforward: does the approved application open as intended, show the right local content, and leave a documented route for authorized maintenance?
Questions
Does setting a signage app as the home app lock down Android?
No. Selecting the home app determines the application used for the home screen and supports the intended startup experience. It does not, by itself, establish restrictions on every system setting, navigation route, or other application. Enforced restrictions require a compatible, documented management arrangement.
Can the signage show start without a network connection?
Yes. The player can play locally loaded images and video without a network connection and keeps a content copy in internal memory. Load and check the intended playlist before assessing startup. Optional HTTPS sync is a separate update method, not a requirement for local playback.
Why might the player be open but the screen look blank?
Check the configured daily on and off hours, the device clock, and the opening content. Outside the configured hours, the player shows black at minimum brightness because the app cannot switch the backlight off. A black presentation is therefore not enough to identify a startup fault.
Is automatic startup the same as recovery after an app crash?
No. Normal startup checks whether Android opens the selected application. Crash recovery checks a separate failure path: the player is designed to relaunch itself and return to playback after an application crash. Record those checks separately and use only documented, authorized methods.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.