com.samsung.android.aremoji Copy

Galaxy Avatar, the Samsung feature previously called AR Emoji. Samsung describes it as a feature "available on select models running Android 9.0 or later", with which you create a personalised emoji from a selfie, and documents two routes to it: Settings, then Advanced features, then Galaxy Avatar, and the Camera app under MORE, then AR Zone, where AR Emoji Camera and AR Emoji Studio live. It is Samsung's own software, signed by the Samsung OEM key that also signs the framework, and is seen here only on Samsung hardware. It is entered from Settings and from the camera rather than from the home screen, and the field data reflects that: only 2 of the 58 observations recorded here show a launcher entry. The companion editor, com.samsung.android.aremojieditor, is covered in the entry below and does carry one. Version note, sourced from Samsung directly. "AR Emoji features have been officially renamed to Galaxy Avatar, beginning with the release of the Galaxy S25 series and other compatible Galaxy phones and tablets running Android 15 and One UI 7.0." The package name did not change, and both names are still visible in the field: this site's label data carries AR Emoji and Galaxy Avatar side by side, in several languages. Samsung's Common Criteria application lists put earlier numbers to the same package, recording AR Emoji at 1.0.02.48 on the Android 9 Galaxy S10+ (G975F) list and at 5.0.00.22 on the Android 11 Galaxy S20 FE (G781B) and Galaxy S20 (G981U) lists. Devices here carry 6.1.02.2 through 11.0.00.11, observed from API 31 to API 37. Whether the One UI 7 rename came with any change in what the feature does, beyond the name and its new home in Advanced features, could not be sourced. Two things are worth an administrator's attention. The first is size: this package is between roughly 69 MB and 76 MB in our sample, which is real storage on a fleet that has no use for it. The second is the permission list, which runs to 62 declared permissions and is wider than a selfie avatar suggests. Alongside the expected CAMERA, RECORD_AUDIO, READ_MEDIA_IMAGES and INTERNET, it declares ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION, QUERY_ALL_PACKAGES, SYSTEM_ALERT_WINDOW, INTERACT_ACROSS_USERS_FULL, MANAGE_USERS, READ_PRIVILEGED_PHONE_STATE and CAPTURE_AUDIO_HOTWORD. This site records declared rather than granted permissions, and declaring one is not evidence it is used, but nothing consulted explains why an avatar feature declares location or cross-user access, and on a privacy-sensitive fleet that is a reason to remove the package rather than reason to assume the worst. For Android Enterprise, EMM and kiosk use it has no role in enrolment or policy and no corporate purpose. The Android Management API can block it through an applications entry with installType BLOCKED, documented as "The app is blocked and can't be installed. If the app was installed under a previous policy, it will be uninstalled", and on a Samsung fleet Knox Manage documents enabling or disabling a named preinstalled system app through its application policies. The rating is caution rather than safe for one reason: Samsung documents the feature as reachable from inside the Camera app's AR Zone, and no source consulted says what the camera does when the package behind those modes is gone. Test on one device whether the Galaxy Avatar entries disappear and whether any camera functionality is affected before rolling it out.

• Turn yourself into an emoji on your Galaxy phone or tablet - Samsung US Support →
• Galaxy S10+ LTE (G975F) application list - Samsung Knox CC Mode documentation →
• Galaxy S20 FE 5G (G781B) application list - Samsung Knox CC Mode documentation →
• Galaxy S20 5G (G981U) application list - Samsung Knox CC Mode documentation →
• Policy resource reference (applications installType BLOCKED) - Android Management API →
• Enable or disable a specific system app - Knox Manage - Samsung Knox Documentation →
• Package provenance for com.samsung.android.aremoji - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, and that single certificate is consistent across all 20 device profiles. It also signs the Android framework, so it is a platform-level key on its device(s). Inferred from the certificate appearing only on Samsung devices (508 packages, 10196 observations).
• Its largest observed manifest declares 62 permissions: 7 runtime (user-granted), 11 signature or system-level, 11 install-time and 33 vendor or uncatalogued.
• Reported as an updated system app on 3 of 20 profiles - a newer build is installed over the one in the system image there.