com.android.fmradio Copy

The AOSP "FM Radio" app. It is a stock Android application, kept in the AOSP tree at packages/apps/FMRadio, whose manifest declares the package name com.android.fmradio and version 2.0. It tunes and plays broadcast FM through the device's FM receiver: the manifest requests ACCESS_FM_RADIO, MODIFY_AUDIO_ROUTING, RECORD_AUDIO and related audio permissions, and the project ships a jni/fmr native directory through which the app reaches the tuner. On most devices wired headphones act as the aerial: FmService treats the headset lead as a "long antenna", checks antenna availability by asking the audio manager whether a wired headset is connected, and switches antenna type when the headset is plugged or unplugged. The same code also allows for a "short antenna" built into the phone, so headphones are the usual requirement rather than a universal one, and the native call can report that a device does not support the switch at all. It is a plain media app with no platform role, and it is not a Google app. Our signer data covers only a minority of the devices we have recorded it on, but on those it is signed by the device maker's own framework-signing key rather than by Google, which is what you would expect of a ROM-resident app. The devices carrying it are mostly budget and rugged handsets from makers such as Blackview, DOOGEE, OUKITEL, Ulefone, Unihertz, itel, Lenovo, Motorola, realme and OPPO. It appears in the launcher on some of those devices. Version note: the upstream AOSP project is effectively frozen. Its manifest carries a 2014 copyright and targets SDK 21, and the newest commit on the main branch is from May 2016. What ships today is therefore a vendor-maintained fork rather than a current AOSP build: copies in our sample still report version 2.0 but have been rebuilt against target SDKs from 27 to 34, and are recorded on devices from API 27 through API 35 (Android 8.1 to Android 15). We could not source any newer upstream successor, so treat behaviour as vendor-specific rather than standard across devices. For Android Enterprise, EMM and kiosk use no enrolment, policy or connectivity role was identified for it: it is a self-contained media app. On a work device it is a consumer distraction that can also record audio, so disabling or hiding it is a sensible default unless FM reception is genuinely part of the use case, which does happen on some rugged and field devices. Because what ships is a vendor fork rather than the upstream build, test on the exact model before rolling a disable out widely.

• FMRadio AndroidManifest.xml - Android (platform/packages/apps/FMRadio) →
• FmService.java (antenna and headset handling) - Android (platform/packages/apps/FMRadio) →
• FMRadio jni directory - Android (platform/packages/apps/FMRadio) →
• FMRadio commit log, main branch - Android (platform/packages/apps/FMRadio) →
• Package provenance for com.android.fmradio - Android System App Database →

• Signed by the device maker's own signing key (OUKITEL), so it is an OEM preinstall, but 2 different certificates appear across the fleet, so OEMs ship their own builds of it. It also signs the Android framework, so it is a platform-level key on its device(s). Inferred from the certificate appearing only on OUKITEL devices (85 packages, 85 observations).
• Its largest observed manifest declares 24 permissions: 4 runtime (user-granted), 12 signature or system-level, 6 install-time and 2 vendor or uncatalogued. The signature/system share marks it as a privileged component, not an ordinary app.