An unofficial home screen for the BYD Sealion 7 that replaces the stock launcher — and takes the instrument cluster with it. It shows you what the car already knows, in the places the car never showed you.
Everything below is photographed on a real car. Only what works gets a picture.
Regions — navigation and the speed-camera warnings run on Korean data (Kakao Mobility, public camera data). Weather, media, the cluster and the vehicle controls work anywhere.
This panel reads the release server directly. The moment a new build is published, everything below changes with it.
https://beetle-launcher.com/BeetleLauncher-1.48-4117dca-release.apk
Once installed, the launcher checks for new releases on its own and offers them to you. You won't need to come back here.
Four steps, once.
Turn on wireless ADB from the head unit's engineer menu, then connect from a computer on the same network.
adb connect <car-ip>:5555
It is built into the launcher now, and the two will fight each other.
adb uninstall com.beetle.adbkick
adb install -r BeetleLauncher-1.48-4117dca-release.apk
Without it the launcher cannot switch wireless ADB back on for you after the next start.
adb shell pm grant com.beetle.launcher \ android.permission.WRITE_SECURE_SETTINGS
Reports go to one shared sheet. Add a row and it gets read and fixed from there.
Row 1 is a worked example. Add yours on a new row below it.
With these, the cause can usually be found without the car in front of us. Leave blank whatever you don't have.
Dashboard, cluster, navigation, vehicle controls, or settings.
Some faults only appear once the car is moving.
The last action is enough — a button, a switch, a swipe.
And what you expected instead. The gap between the two is the bug.
Once, always, or sometimes. This narrows the cause more than anything else here.
The version is under Settings › About. One photo of the screen beats ten lines of description.