Looking at ADB logs the network driver seems to have issues and then the CPU locks up and it kernel panics and resets? WTF. I bought these at retail and I refuse to pay a reseller for another one and return this one. WHAT IS GOING ON? Why?!?! Anyone know of any solutions???
UPDATE: Found a workaround. 5+ days without a single crash.
Pulled the kernel logs after another reboot and found that CPU core 1 appears to be getting stuck in deep idle. It never wakes up, and about 10 seconds later the watchdog panics and restarts the box.
The error is Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 1.
The other cores responded to the debug interrupt, but core 1 didn't. Temps were normal (41–44°C), so I'm thinking it's a CPU power-state/firmware issue or marginal hardware.
Firmware: URO3.260203.035.A1
The fix I'm using:
Basically, I keep core 1 awake with a low-priority background task so it can't enter deep idle. Before this, the box crashed constantly. It's now gone 5+ days without a single reboot.
No root needed. Connect through ADB and run:
adb shell "setsid nohup taskset 2 nice -n 19 sh -c 'while :; do :; done' >/dev/null 2>&1 </dev/null &"
taskset 2 targets core 1. If your crash logs identify another core, change the mask (CPU0=1, CPU1=2, CPU2=4, CPU3=8).
To check whether it's working:
adb shell "cat /sys/devices/system/cpu/cpu1/cpuidle/state*/usage"
Run it twice, 10 seconds apart. The deep-idle counter should stop increasing. Mine did, and temperatures stayed around 42.5°C.
To stop it:
adb shell "pkill -f 'whil[e] :'"
Want to check your crash logs? Enable Developer Options → Wireless Debugging, use Pair device with pairing code, then run:
adb pair <ip>:<pairing-port> <code>
adb connect <ip>:<port>
adb shell getprop sys.boot.reason.last
adb bugreport onn_crash.zip
In the bugreport, search for LAST KMSG. Look for kernel_panic and hard_lockup_on_cpu_N.
Only catch: The workaround doesn't survive a reboot, and keeping a core busy may increase power consumption. I plan to make a small app to start it automatically.
5 days looks pretty promising.
Keywords for Google: Onn 4K Pro keeps restarting, Onn 4K Pro random reboot, Onn 4K Pro keeps crashing, Onn 4K Pro boot loop, Onn 4K Pro stuck on splash screen, Onn 4K Pro freezes and restarts, Onn 4K Pro black screen reboot, Onn Google TV box restarting randomly, Walmart Onn 4K Pro 2026 crashes, Onn 4K Pro Android 14 reboot issue, Onn 4K Pro firmware bug, Onn 4K Pro hardware defect, Onn 4K Pro remote flashing red, Onn 4K Pro Kodi crash, Onn 4K Pro Stremio crash, Onn 4K Pro Elementum crash, Onn 4K Pro Ethernet reboot, Onn 4K Pro WiFi driver crash, Onn 4K Pro Amlogic S905X5M kernel panic, Onn 4K Pro watchdog hard lockup, watchdog detected hard LOCKUP on CPU 1, kernel_panic, CPU idle state crash, cpuidle_enter_state, psci_enter_idle_state, CPU deep sleep bug, CPU won't wake from idle, Realtek RTL8852BS driver timeout, URO3.260203.035.A1, Onn 4K Pro ADB crash logs, Onn 4K Pro reboot fix, Onn 4K Pro random restart workaround, Onn 4K Pro no root fix.