com.samsung.android.messaging Copy

Samsung Messages, the SMS, MMS and RCS client Samsung has shipped as the default messaging app on Galaxy phones and tablets for years. It carries the label "Messages" on the device. In our sample it is preinstalled on Samsung devices only and is signed by Samsung keys that also sign the Android framework. Google's own Messages app, documented separately on this site under com.google.android.apps.messaging, is the other messaging client Galaxy devices commonly carry, and on many recent models both are present. Version note, and the important one for anyone planning a fleet: Samsung has ended this app. Samsung's own product page states plainly that "the Samsung Messages application has been discontinued" and that "users on an older Android OS (Android 11 or lower) are not affected by this End of Service". Note the scope: the same page carries the line "applicable to the US market only", and what Samsung intends for other markets is not established by the sources reviewed here, so treat the timing below as a US announcement rather than a global one. On that announcement, the app becomes user-removable from autumn 2026 on devices running One UI 9.0 or higher; owners of the Galaxy S26 and newer cannot download it from the Galaxy Store at all, and other devices lose that ability once the app is discontinued in July 2026. Samsung says that afterwards "sending messages via Samsung Messages on your phone will no longer be possible, except for emergency service numbers or emergency contacts defined in your device", and that Message Continuity for "Call & Text on Other Devices" is disrupted. Samsung directs users to Google Messages instead, and says conversations transfer automatically, taking up to around 24 hours. In this site's sample the package is recorded on builds from Android 9 through Android 16; we have too few Android 17 observations to read anything into its absence there. For Android Enterprise, EMM and kiosk use, the practical consequence is that any policy, allow list, default-app assumption or user documentation naming com.samsung.android.messaging should be reviewed on Galaxy fleets in the affected market, with Google Messages as the replacement Samsung points to. Disabling it is normally harmless on a device where it is not the default SMS handler, but disabling the app that currently holds that role will break messaging for the user, so check the default before acting. On a kiosk or single-purpose device with no messaging requirement it is a reasonable candidate for removal, subject to the usual caveat that emergency messaging paths should not be broken on a device a person carries.

• Samsung Messages Discontinued - Switch to Google Messages - Samsung US →
• Use the Samsung Messages app on your Galaxy phone or tablet - Samsung US →
• Package provenance for com.samsung.android.messaging - Android System App Database →

• Signed by the device maker's own signing key (Samsung), 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 Samsung devices (508 packages, 10196 observations).
• Its largest observed manifest declares 230 permissions: 24 runtime (user-granted), 24 signature or system-level, 21 install-time and 161 vendor or uncatalogued.
• APK size ranges from 31.0 MB to 74.9 MB across the reporting device profiles, so the build differs substantially between them.
• Reported as an updated system app on 1 of 15 profiles - a newer build is installed over the one in the system image there.