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.
The first install is done this way — see the “Install” tab above. After that the launcher checks for new releases on its own.
The instrument cluster is the Sealion 7 only. On these cars the launcher stays on the centre screen; the screen beyond the steering wheel is left as the car made it.
The debug build is for testing. Use it only when you're helping chase a problem that's being fixed. It can contain half-finished work. 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 above needs none.
At ignition it checks wireless ADB, restores Wi-Fi, launches your apps, then closes. For the Sealion 7 head unit.
Install from a phone, not a file manager. Put the phone on the same Wi-Fi as the car, then install the APK with atvTools (iPhone) or Bugjaeger (Android) over wireless ADB. First time: Status tab → Connect / authorize → Always allow on the car.
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 release ManualPuts 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.
The dashcam on its own — front, rear, left and right on one screen, recorded as you drive. The launcher already carries the same thing, so you do not need this one if you use the launcher.
Not handed out yet. When it is ready, its download appears here.
You can do this from a computer, or from a phone alone. Once.
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.
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
adb install -r BeetleLauncher-1.48-4117dca-release.apk
On the ATTO 3 it is this file:
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.