GInputBridge

Geely Steering Wheel Button Controller

GInputBridge (Git repository gbinder, application id com.salat.gbinder) is an Android app for automotive head units. It combines a custom launcher (grid of apps, recents, theming), hardware key and media bridging, system overlays (drive mode, task manager, and related UI), and vendor integration (Geely / EcarX stacks) behind a single product.

What’s in the app Launcher

A dedicated launcher surface: LauncherOverlayService draws a full-screen Compose overlay (TYPE_APPLICATION_OVERLAY) with “My apps”, All apps, optional recents, launcher settings, and theme options (including light/dark scheduling). LauncherEntryActivity (with an AppLauncher activity-alias) exposes a second entry point so the app can act as a home-style launcher alongside MainActivity, which remains the main settings / configuration entry (MAIN/LAUNCHER). Launcher data (tiles, layout, favorites) is backed by DataStore (LauncherPrefs, LauncherStorageRepository) and Coil for icons; utilities cover icon backup, file URIs, and time-based behavior. Input, media, and system glue

Central logic in App wires key state, media sessions, and global flows (GlobalState, StateKeeper). MediaNotificationListenerService and media helpers integrate with playback and notifications; key binding UIs and entities (KeyBindConfig, KeyState, etc.) map physical controls to actions. Overlays and auxiliary UI

Foreground services such as DriveModeOverlayService, TaskManagerOverlayService, LampModeOverlayService, plus dialogs like DashboardDialog — task switching, drive UI, and lamp-style overlays as needed on the HU. Configuration and tooling

MainActivity hosts the primary Compose UI for deep settings: key bindings, launcher-related options, import flows (e.g. .gibb file association on MainActivity), and feature toggles. features/configurator (RenderConfigurator and related) drives advanced configuration screens. adb integration (e.g. AdbRepository, adb-shell dependency) supports device-side automation and debugging workflows. Startup and platform hooks

BootAccessibilityService, BootContentProvider, BackgroundTaskReceiver, and related components align with boot and background execution on the target system. Other entry points

PhoneCallActivity and related flows for call-oriented UI when required on the platform. Data and services

AndroidX DataStore for preferences; Firebase (Analytics, Crashlytics, Firestore) as wired in build.gradle.kts. core:remoteConfig, core:stateKeeper, core:filedownloader, core:car for shared behavior across the app and head-unit context.