proomt

Search

Search posts, papers, and topics

All posts

Android4 min readtutorialintermediate

Bring your Android game to the car screen today

Read on googleblog.com

Summary

A step‑by‑step guide for Android game developers to make their apps runnable on Android Auto and Android Automotive OS, covering manifest changes (appCategory, CAR_LAUNCHER, automotive hardware feature), parked‑state handling, controller support, screen‑size adaptation, testing tools (Desktop Head Unit, AAOS emulator), and Play Console publishing requirements.

  • Add `android:appCategory="game"` to the `<application>` tag to appear in the games category.
  • Declare `android.intent.category.CAR_LAUNCHER` in an activity’s intent filter to signal Android Auto support (Android 15+).
  • Include `<uses-feature android:name="android.hardware.type.automotive" android:required="false"/>` for Android Automotive OS; set `required` based on the distribution track.
  • Do not use `distractionOptimized` metadata; stop audio when the vehicle starts moving and prevent unpausing while driving.

Enabling games on car screens opens a new, low‑distraction usage window (e.g., while parked) and expands distribution channels. Following the required manifest flags and UX restrictions ensures compliance with driver‑safety policies and avoids rejection during Play Store review.

6/10
androidgamespublishingandroid autoandroid automotive osmanifest

Related reading

  1. Android 17 Without the Last-Minute Scramble

    CodeName One prepared for Android 17 (API 37) by addressing platform changes proactively, including fixing version number parsing and implementing the new system-rendered location button. They also added robust PEM key parsing and explicit task removal to simplify common security operations for app developers.

    CodeName Onecodenameone.com8 min

  2. Android Bench 2.0: Pushing the frontier with challenging long-horizon tasks

    Android Bench 2.0 adds a set of long‑horizon tasks (multi‑day Android development problems) and introduces agent‑based evaluation. Scoring is now continuous, with the best model achieving a 28 % pass rate on these tasks, far lower than the ~91 % on earlier short tasks. The post lists new models on the leaderboard and points to updated methodology and GitHub repo.

    Androidgoogleblog.com4 minHN2

  4. Tapjacking Protection: Rejecting Android Touches Behind an Overlay

    Codename One adds tapjacking protection to its Android runtime. It detects fully or partially obscured MotionEvents, offers four policies (OFF, REPORT, BLOCK, STRICT), can block the entire gesture, and on Android 12+ can request the system hide overlay windows. The API is exposed via `DeviceIntegrity.setTapjackingProtection` and a listener for state changes. iOS has no overlay threat, so the feat…

    CodeName Onecodenameone.com3 min

  5. Reflect, Revise, Reuse: Training-Free Skill Evolution for GUI Agents

    EvoSkill‑GUI lets GUI agents revise their procedural skills on‑the‑fly without extra training by using a reflect‑revise‑reuse loop that edits skill packages during execution. The approach yields up to +16.2% improvement on MobileWorld and similar gains on AndroidWorld and OSWorld, and the evolved skills transfer to related tasks.

    Hugging Face Daily Papersarxiv.org1 minpaper

  6. Put App Documents in the System File Browser

    Codename One adds a read‑only DocumentProvider API that lets apps publish a virtual file tree to iOS Files and Android’s storage picker. The tree is defined with `DocumentNode` objects, can include remote‑only entries, and is shared via an App Group container. The iOS extension runs in a separate process, so the model is serialized and read independently; Android uses the same model inside the ap…

    CodeName Onecodenameone.com4 min