I had four 8-inch tablets lying in a drawer. No-name hardware, the kind you buy because it is cheap and then forget about. At the same time, the tablets I already use as Home Assistant wall panels were driving me mad: the kiosk browser would sometimes simply not be in the foreground anymore, even though it was configured to stay there, and the one in the hallway regularly ended up showing a blank white page until I rebooted it.
So the question was: can I turn these drawer tablets into wall panels that are boringly reliable? Slim system, screen always on, Home Assistant as the only thing that ever runs, brightness controlled from Home Assistant. And if I bricked one along the way — fine, they were destined for the bin anyway.
Spoiler: it worked, all four are on the wall, and the result is a public repository with a single script that converts a stock tablet in about a quarter of an hour. Here is how I got there, including every wall I ran into.
Meet the tablet
The device is a Weelikeit F83W. The box and settings screen promise little; adb shell getprop tells the real story:
-
SoC: Allwinner A133 (
sun50iw10p1), four Cortex-A53 cores, 3 GB RAM - OS: Android 13 — but with a 32-bit userspace on a 64-bit kernel (5.15)
- Partitions: A/B slots, dynamic partitions, Project Treble enabled (VNDK 33)
- Display: an 800×1280 panel that is natively portrait, mounted in a landscape tablet
Treble support was the good news: in theory, any Generic System Image (GSI) should boot on it. The 32-bit userspace was the first catch: it rules out the common arm64 GSIs and leaves only the rarer a64 builds (arm32 userspace with 64-bit binder).
Step 1: Unlocking the bootloader
Enabling OEM unlocking in the developer options worked as expected. Then it got interesting, because this tablet has two different fastboot modes:
-
fastbootd (
adb reboot fastboot) runs in userspace. It can flash logical partitions, but it refuses to unlock anything. -
The bootloader fastboot (
adb reboot bootloader, a green Android robot without any text) is Allwinner's U-Boot. It acceptsfastboot oem unlock— notflashing unlock.
The catch: on my Mac, fastboot devices never saw the bootloader. The device enumerates as USB ID 1F3A:1010 with a perfectly valid fastboot interface (class FF/42/03), but macOS doesn't activate a USB configuration for it, so the stock fastboot tool can't find it. My first tablet was unlocked from a Windows PC with Google's USB driver forced onto the device.
For the other three, I wrote a tiny fastboot client in Python on top of pyusb/libusb. It selects the configuration itself, claims the interface and speaks the fastboot protocol directly. It turned out to work every single time:
macOS-fastboot doesn't see the Allwinner bootloader – trying direct USB access (libusb) ...
Unlock device successfully!
One more thing worth knowing: there is no stock firmware download for this device. Once you replace the system partition, there is no easy way back. With four identical tablets, I kept one untouched until the first one worked.
Step 2: Finding a GSI that actually boots
My first attempt was a LineageOS 23.2 (Android 16) a64 build. It flashed fine and then sat at a black screen until Android's rescue party dropped me into the stock recovery with “Can't load Android system”.
The lesson: match the Android version of the vendor partition. The vendor blobs here are Android 13, so I switched to AndyYan's LineageOS 20 GSI in the a64_bvS flavour (A/B, vanilla, with superuser). That one showed the LineageOS boot animation — and stayed there forever.
The flashing itself is straightforward in fastbootd. The only extras are a blank vbmeta with verification disabled and deleting the vendor's product partition to make room in super:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_disabled.img
fastboot delete-logical-partition product_a
fastboot erase system_a
fastboot flash system_a lineage-20-a64_bvS.img
fastboot -w
fastboot reboot
Step 3: The boot loop nobody warns you about
Luckily, the LineageOS userdebug build has ADB enabled during boot, so I could pull a logcat while the animation was spinning. system_server had been restarted 90 times, and the reason was right there:
Signature mismatch on system package com.yhk.qeota for shared user android.uid.system
The manufacturer ships two apps in /vendor/app — an OTA updater and a video player — that run as the system user and are signed with the manufacturer's platform key. The GSI is signed with a different key, so Android's package manager refuses to start. The stock firmware works only because both sides share the same key.
The fix is to hide /vendor/app by bind-mounting an empty directory over it before the package manager scans it. My first attempt used an init .rc file — and failed, because SELinux doesn't allow init to mount over vendor_app_file. What did work: the TrebleDroid base of the GSI ships a boot script, rw-system.sh, that runs early in a permissive SELinux domain and already bind-mounts fixes over vendor files. One extra line there:
mount -o bind /system/etc/hide-vendor-app /vendor/app
Next boot: the LineageOS setup wizard.
Step 4: Portrait panel, landscape tablet, confused sensor
The system came up in portrait, while the touchscreen behaved as if it were landscape. The vendor's build.prop explained it: ro.vendor.sf.rotation=90. That's an Allwinner-specific property their patched framework uses to rotate the output — the GSI knows nothing about it. The AOSP equivalent is:
ro.surface_flinger.primary_display_orientation=ORIENTATION_90
That fixed display and touch at once. Auto-rotation was still wrong, though. The accelerometer reports its axes relative to the portrait panel, and Android doesn't compensate sensors for the display's install orientation.
Disassembling the vendor's sensor HAL showed that it computes an axis correction from several properties and from a config file, /vendor/etc/gsensor.cfg. The properties turned out to have no effect in practice, so I measured instead: holding the tablet upright in landscape, Android expects roughly x=0, y=+9.8. The sensor reported x=−9.7, y=0.3. From two measurements, the required mapping was obvious — and changing three flags for the msa sensor in gsensor.cfg, again bind-mounted from rw-system.sh, made auto-rotation work in all four directions.
Step 5: Making it a kiosk
Now the actual goal. Instead of a kiosk browser, I went with the official Home Assistant Companion app in its minimal flavour (no Google Play Services — there are none on this system). It can act as the device's home screen, so Android itself brings it back after every crash or reboot.
Everything is baked into the system image:
- Debloated: around 30 apps removed — camera, browser, dialer, gallery, music, and so on. WebView, keyboard and settings stay.
- Home Assistant as a system app, with its native libraries pre-extracted (system apps don't get their compressed libraries unpacked automatically).
- A first-boot script that sets the defaults: screen stays on while powered, no screen saver, no lock screen, no animations — and, once the setup wizard is done, grants the app all permissions, exempts it from battery optimisation and sets it as the home app.
-
No navigation bar:
setprop qemu.hw.mainkeys 1early inrw-system.sh. Setting it inbuild.propdid not stick on this build. - A watchdog that brings Home Assistant back to the foreground if anything else stays there for more than ten minutes, and restarts the app every night at 4 a.m. — my answer to the white-screen problem.
Two app settings needed special care. Without Google services, commands from Home Assistant only reach the device through the app's persistent connection. And the app wants a home Wi-Fi defined before it accepts a plain http:// internal URL. Both live in the app's Room database and only exist after you log in. So the watchdog waits for the login, writes the currently connected SSID into servers.internal_ssids and restarts the app once. After that, brightness commands work immediately.
I made one mistake worth sharing: in an early version, the watchdog grabbed the foreground before the LineageOS setup wizard had finished. The result was a tablet with no Wi-Fi, an English UI and a locked status bar. Everything Home Assistant-related now waits for user_setup_complete=1.
Patching a system image without root or loop mounts
All of this happens on the image file, not on the device. The GSI's ext4 image uses shared_blocks (deduplication), which makes it read-only for most tools. The recipe:
truncate -s +200M system.img
resize2fs system.img
e2fsck -fy -E unshare_blocks system.img
debugfs -w -f commands.txt system.img # write files, set modes and owners
resize2fs -M system.img
The part that's easy to forget: SELinux labels. Every file needs the right security.selinux extended attribute, which debugfs can set with ea_set. Scripts that should run in the permissive domain get u:object_r:phhsu_exec:s0, the sensor config vendor_configs_file, everything else system_file.
One script to flash them all
With a working image, I wanted the remaining three tablets to be boring. flash.sh runs on macOS and walks through seven steps:
- Checks and installs prerequisites via Homebrew, reassembles the image and verifies checksums
- Waits for the tablet (USB debugging), checks model, hardware and firmware build
- Unlocks the bootloader (via libusb when macOS fastboot can't see it)
- Flashes vbmeta and the system image in fastbootd
- Waits for the first boot
- Waits for you to finish the setup wizard
- Waits for the Home Assistant login and confirms that the watchdog did its job
Every waiting state is polled automatically, completed steps are detected, and the script can be restarted at any point. The three remaining tablets went through it in 15 to 30 minutes each — most of that was the script waiting for me to tap through the setup wizard.
Controlling the panel from Home Assistant
The Companion app exposes sensors and accepts notification commands. Brightness is a one-liner:
action: notify.mobile_app_wall_panel
data:
message: command_screen_brightness_level
data:
command: 120 # 0..255
Wrapped in a template number entity, it becomes a regular slider on the dashboard. The app has command_screen_on, but no screen-off command — if you need that, ADB over the network with Home Assistant's Android Debug Bridge integration and input keyevent KEYCODE_SLEEP does the job.
What I learned
- Treble is not magic. Match the Android version of the vendor partition, and check the userspace bitness before downloading anything.
- Read the logcat, not the forums. The boot loop had nothing to do with the GSI and everything to do with two vendor apps.
-
Vendor quirks hide in properties and config files.
ro.vendor.sf.rotationandgsensor.cfgwere the keys to display and sensor. - Own the OS, own the kiosk. Once the system is yours, the kiosk app doesn't have to fight Android — the system keeps it in front.
Everything — the flash script, the patches, the watchdog and a ready-to-flash image — is on GitHub: DasRed/weelike-f83w-homeassistant-kiosk. It is built for exactly this tablet and firmware, but the techniques apply to many cheap Allwinner devices.
Credits: LineageOS, AndyYan for the a64 GSI builds, TrebleDroid/phhusson for the GSI base, and the Home Assistant Companion for Android team. As always: unlocking a bootloader wipes your data and may void your warranty — do this at your own risk.
Originally published on Medium.
Top comments (0)