A home screen that opens up something new
An unofficial home screen that replaces the stock launcher on your car — and takes the instrument cluster with it. It shows you what the car already knows, in the places the car never showed you.
Key features
Everything below is photographed on a real car. Only what works gets a picture. Broadcast pictures and station logos are blurred out.
Cluster
The car
Cameras
Map and broadcast
Regions — navigation, the speed-camera warnings, radio and TV run on Korean data and Korean broadcasters (Kakao Mobility, public camera data). Weather, music, the cluster, the vehicle controls, the turn-signal camera and the dashcam work anywhere.
Manual
What each screen holds, and what every item in Settings does. The app itself carries no explanations — Settings is for operating, not reading — so the explanations live here.
Open source we learned from
The Sealion 7 and ATTO 3 launchers were built with help from the public research below. No code was taken — the implementation is written from scratch. What these taught us is what the BYD framework calls things and in what order. Without them this would have taken weeks longer.
- byd-turnsignal-cameraview sunlixWhyNotAvailable AGPL-3.0 How the car's camera is opened, and how a helper is started with shell privileges.
- BYDMate AndyShaman That the car's services can be reached without root — and where the research above lives.
- byd-apps wheregoes Walking the SDK surface by reflection — confirmation that we were on the same path.
Typefaces: Saira Condensed, IBM Plex Sans and IBM Plex Mono (SIL Open Font License).
Latest release
This panel reads the release server directly. The moment a new build is published, everything below changes with it.
Once installed, the launcher checks for new releases on its own and offers them to you. You won't need to come back here.
The debug build is for testing. Use it only when you're helping chase a problem that's being fixed. It sends logs to a server and can contain half-finished work. Automatic updates follow the stable line only. It is signed with the same key as the release, so the two install over each other.
No key? Ask through the contact on the “Report a bug” tab. The release build above needs none — take it as it is.
ATTO 3 — in testing
The ATTO 3 build is still being made, so it isn't open to everyone. People helping to test it are given a download key.
This is not a release. It can contain half-finished work, and things that used to work may not. The Sealion 7 release above needs no key — take it as it is.
No key? Ask through the contact on the “Report a bug” tab.
Standalone apps
These run on their own, separately from the launcher. If you use the launcher you mostly won't need them — they're for using that one piece without it.
Switches wireless ADB back on at every start. It is built into the launcher, so you don't need this one if you use the launcher.
Get AdbKick Get the stable releasePuts the instrument-cluster screen up on its own. When the launcher is this car's home app it stands aside and says on screen why.
Putting it on the car
You can do this from a computer, or from a phone alone. Once.
Easier from a phone
Put your phone on the same Wi-Fi as the car, connect over wireless ADB with one of these, and install the APK straight from the phone. No computer, no cable.
Bugjaeger is Android-only. On iPhone, use atvTools.
From a computer
-
Connect over wireless ADB
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
-
Install it
adb install -r BeetleLauncher-1.48-4117dca-release.apk
-
Grant one permission
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
AdbKick — the piece that switches wireless ADB back on — is built into the launcher. You don't need to install it separately, and if you still have the standalone one, the launcher does not call it.
Before you install
- This is unofficial. It is not affiliated with, endorsed by, or connected to BYD in any way. “BYD”, “Sealion” and “DiLink” are the trademarks of their respective owners.
- It does not modify vehicle firmware. It replaces the home screen, and it drives the car through the same published SDK the factory app uses.
- Install at your own risk. No warranty of any kind is given. Do not operate it while driving.
- Built for the Sealion 7 on DiLink 5.0, Android 11. Other BYD models are untested.
Tell us what broke
Fill the boxes and send. You can attach photos and a short video with it.
You'll get a reference number back. When it is fixed, it will be listed against that number.
Six things are enough
These six are what the report page asks for. With them, the cause can usually be found without the car in front of us. Leave blank whatever you don't have.
-
Which screen
Dashboard, cluster, navigation, vehicle controls, or settings.
-
Parked or driving
Some faults only appear once the car is moving.
-
What you did
The last action is enough — a button, a switch, a swipe.
-
What happened
And what you expected instead. The gap between the two is the bug.
-
Every time?
Once, always, or sometimes. This narrows the cause more than anything else here.
-
Version, and a photo
The version is under Settings › About. One photo of the screen beats ten lines of description.