Scope: Community-documented methods to access developer/engineering options on MG4 Electric infotainment (Android Automotive OS 9, MT2712), enable installation from unknown sources, sideload apps (notably Nova Launcher), and work around SAIC’s default launcher behavior. Differences between SE/basic and Trophy/XPower/higher-end trims are noted where known. Safety & Warranty: Proceed at your own risk. Do not interact with the infotainment while driving. Some functions may be disabled by updates, vary by region/trim/firmware, or affect warranty. Primary discovery threads: XDA starter post and MGEVs forum posts describing the keyboard-trigger trick and trim/version notes.
- Getting Into Hidden Settings
- Open Bluetooth → Device name (or any text field that brings up the on-screen keyboard).
- Long-press the comma ( , ); if that doesn’t work on your build, long-press the “@” (e.g., in an Amazon login field).
- Choose Android Keyboard Settings.
- Go Languages → use the search bar to find About (for Developer options) or Wi-Fi (to bring up network toggles).
- Enable Developer options from About (tap build/version repeatedly if shown), and/or turn on Wi-Fi for downloads. Reported working on SE, expected to work on Trophy; “@” key method confirmed on an R59 keyboard layout. https://www.mgevs.com/threads/diagnostic-vdi-vnci-mdi-with-mg4.17679/page-7
From the car’s Phone tile, open the dial keypad and enter ##4479#* to pop the engineering screen. Variants/passwords may exist by model year/trim; community notes mention a 5-tap version route and different passwords on some models/years. Use as a working theory if your build differs. - MGEVs “Secret Menu” posts (SE code, 5x tap context, Trophy password line) https://www.mgevs.com/threads/mg4-secret-menu-mode.8529/page-6 https://www.mgevs.com/threads/engineering-menu.19042/ Some posts reference: Settings → tap the Infotainment “Version” 5 times → enter password → Engineering/Developer menus, with toggles such as ADB. Treat passwords/paths as firmware-specific. Once in Android/Developer areas: #
Enable Developer options (if not already). #
Find Install unknown apps / Allow from this source (may be under Apps → Special access). On Android 8+ this is per-app (e.g., enable for Files or Browser you’ll use to install APKs). https://xdaforums.com/t/mg4-electric-aaos-9-playing-and-possibly-other-mg-models.4697712/page-7 Pick the path your unit supports.
- On a PC/Mac, download the APK(s) to a FAT32 USB drive.
- Plug into the MG4’s USB.
- Open the car’s Files / Downloads area and install the APK(s).
- If prompted, Allow from this source for the Files app.
- Community posts in other AAOS cars (Renault OpenR) confirm USB + Files flow; MG4 owners on XDA mention returning to the “files area” between installs—suggesting an analogous flow. https://xdaforums.com/t/sideload-apps-on-renault-openr-aaos.4661050/
If your build exposes a browser, navigate to a trusted source and download the APK; then open from notification or Files/Downloads and install. Enable per-app “install unknown apps” for the browser. #
Trusted sources for Nova: https://www.apkmirror.com/apk/teslacoil-software/nova-launcher/ https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher
- Enable ADB in engineering/developer menus.
- Connect over USB (if enumerates) or switch to Wi-Fi ADB: adb tcpip 5555
(over USB), thenadb connect <car_ip>:5555
- Install:
adb install Nova.apk
- Generic ADB over TCPIP instructions and examples: https://stackoverflow.com/questions/2604727/how-can-i-connect-to-android-with-adb-over-tcp Trim caveat: Some SE/basic units reportedly don’t enumerate for ADB over USB as easily as higher-spec units; progress has been mixed. Try Wi-Fi ADB if USB fails. The XDA thread shows users installing Nova first, accepting all prompts, then returning to Files to install companion utilities.
- Obtain Nova Launcher APK (stable or beta) from a trusted source (above). Copy to USB or download in-car.
- On the MG4, open Files/Downloads and tap the Nova APK.
- If warned, Allow from this source (Files or Browser).
- Complete the installer and tap Done (not always Open yet).
- Optional but recommended: install Key Mapper to map a reliable gesture/hardware route into Nova (details §5). https://www.apkmirror.com/apk/teslacoil-software/nova-launcher/
- If Settings → Apps → Default apps → Home app is visible, set Nova as Home.
- Some SAIC builds revert to the stock launcher on Home presses. Expect this to be flaky. ADB fallback to force Home: adb shell cmd package set-home-activity com.teslacoilsw.launcher/com.teslacoilsw.launcher.NovaLauncher Community tip for stubborn devices; may or may not stick on AAOS builds. https://www.reddit.com/r/NovaLauncher/comments/jmmfop/nova_launcher_as_default/
Install Key Mapper, open it once to establish permissions. #
Map a bottom-right swipe-up (not the bottom-left, which acts as Back) to Launch Nova. Owners report: two different swipe zones live at the bottom—right launches the mapped app; left behaves like Back. Physical Home always returns to SAIC UI if lost. https://github.com/keymapperorg/KeyMapper https://www.mgevs.com/threads/mg4-software-update-thread.7699/page-258
- Community members have been building floating buttons to bypass SAIC launcher reassertion; watch XDA/MGEVs for released APKs. Treat as in development.
- Expect SAIC apps to use a different DPI than standard Android apps. Owners report stock apps look large, while sideloaded apps look tiny. Nova’s own icon/label scaling helps, but system-wide DPI (“Smallest width”) may be restricted on AAOS builds. Consider this a known limitation unless your Developer options expose display size overrides.
If your unit lacks obvious Wi-Fi toggles, use the keyboard search inside Android Keyboard Settings → Languages → Search to surface Wi-Fi settings. #
ADB over USB vs Wi-Fi: higher-spec trims have reported easier ADB activation; SE/basic sometimes fail to enumerate over USB. Try Wi-Fi ADB ( adb tcpip 5555 thenadb connect <ip>:5555 ) if USB fails. https://stackoverflow.com/questions/2604727/how-can-i-connect-to-android-with-adb-over-tcp
- No “Install unknown apps” toggle? On Android 8+ it’s per-app under Special access; grant it for the Files app or Browser you use to install.
- Nova doesn’t appear on Home: try launching Nova once from Key Mapper mapping; if a Default Home picker appears, choose Nova. If the picker never appears, use the ADB set-home-activity command (may still get overridden by SAIC on Home presses).
- R59 keyboard long-press fails: use the “@” key long-press in an app sign-in field (like Amazon) to open keyboard settings.
- USB ADB not detected: confirm ADB enabled in Engineering/Developer menus; try alternative USB port/cable, or switch to Wi-Fi ADB.
- Uninstall Nova from Apps, remove Key Mapper mappings, and the SAIC launcher regains control.
- If you forced Home via ADB, restore SAIC’s launcher by clearing defaults or factory-resetting the head unit (as a last resort).
- Physical Home remains a quick escape hatch to SAIC UI if a sideloaded app misbehaves.
- XDA thread (MG4 AAOS 9 exploration):
https://xdaforums.com/t/mg4-electric-aaos-9-playing-and-possibly-other-mg-models.4697712/
https://xdaforums.com/t/mg4-electric-aaos-9-playing-and-possibly-other-mg-models.4697712/page-2
https://xdaforums.com/t/mg4-electric-aaos-9-playing-and-possibly-other-mg-models.4697712/page-7
- MGEVs posts (keyboard trick, R59 “@”, swipe mapping, trim notes):
https://www.mgevs.com/threads/diagnostic-vdi-vnci-mdi-with-mg4.17679/page-7
https://www.mgevs.com/threads/mg4-software-update-thread.7699/page-258
https://www.mgevs.com/threads/mg4-secret-menu-mode.8529/page-6
- Nova Launcher (official + trusted APK):
https://www.apkmirror.com/apk/teslacoil-software/nova-launcher/
- Key Mapper (for gesture → Nova): https://github.com/keymapperorg/KeyMapper
- Side mechanics / ADB over TCPIP (generic but applicable):
https://stackoverflow.com/questions/2604727/how-can-i-connect-to-android-with-adb-over-tcp
https://xdaforums.com/t/sideload-apps-on-renault-openr-aaos.4661050/