Possible fix for missed text/Group messages after update

If you are missing messages or your group message are not functioning like they were BEFORE the update here’ are some fixes to try:

When the Mudita Kompakt installs an OS update and reboots, it often forces a carrier network settings refresh. This means that if a user previously went in and manually fixed their APN settings to get group texts working, the 1.5.0 update likely wiped out their manual fixes and restored the carrier’s default profile.

Major carriers (like T-Mobile, AT&T, and their MVNOs) include advanced messaging tags like rcs or xcap in their default APN profiles. Because the Kompakt does not support these protocols, having those tags instantly breaks MMS (group texts).

You can absolutely tell them to contact support, but providing them with a quick checklist on the forum first will likely solve the problem for most users and save our support team from a flood of tickets.

1. Check for the APN Update Glitch
This is the most likely culprit after an OS update. Users need to verify that the update didn’t inject incompatible tags back into their network profile.

  • Go to Settings → Network & Internet → Mobile network → Advanced → Access Point Names.
  • Tap the active carrier profile.
  • Scroll down to APN Type.
  • Ensure the text strictly says: default,mms,supl
  • If tags like rcs or xcap have reappeared, users must delete them, tap the three dots in the top right corner, and press Save.

2. Verify Mobile Data & MMS App Settings
Group texts (MMS) are small file downloads and cannot be processed over Wi-Fi alone; they strictly require an active cellular data connection.

  • Mobile Data: Go to Settings → Network & Internet → Mobile network and ensure Mobile data is toggled ON.
  • App Settings: Open the Messages app, tap the three dots in the top right, go to Settings → SIM 1 (or whichever SIM is active), and ensure Download MMS content is toggled ON.

3. The Physical Modem Reset (SIM Pull)
If the APN is correct, the internal modem might just be “stuck” trying to re-establish a handshake with the cell tower after the 1.5.0 reboot. A physical reset forces a clean connection:

  1. Turn Airplane Mode ON.
  2. Power the phone completely off.
  3. Remove the SIM card from the tray.
  4. Power the phone back on without the SIM card inside.
  5. Turn Airplane Mode OFF.
  6. Reinsert the SIM card and let it establish a brand-new connection to the network.
1 Like

For making sure the APN type is right, my list is as follows: default, supl, mms, ia

Is the “ia” ok in that list? No idea what it is.

Edit: I’m using Mint Mobile

1 Like

1 Like

As for the correct APN settings, each network provider has their own, so it’s best to check with them.

Can confirm, I had made a custom APN a year ago, and after the updates since then, it did not exist anymore. My T-Mobile US default APN had rcs listed under APN Type, but I haven’t had any issues receiving MMS or group messages for most of the year (I possibly had some issues due to having used ADB to change DNS settings).

That being said, I went ahead and made a custom APN using the settings listed at T-Mobile (https://www.t-mobile.com/support/devices/not-sold-by-t-mobile/byod-t-mobile-data-and-apn-settings?msockid=0023037bd70064ef386015cbd67e6563) slightly edited below to match the Kompakt’s settings.

Name: T-Mobile

APN: fast.t-mobile.com

Proxy: Not set

Port: Not set

Username: Not set

Password: Not set

Server: Not set

MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc

MMS proxy: Not set

MMS port: Not set

MCC: 310

MNC: 260

Authentication Type: Not set

APN Type: default,supl,mms

APN Protocol: IPv4/IPv6

APN roaming protocol: IPv4/IPv6

APN enable/disable: [Leave switch on to enable]

Bearer: Unspecified

MVNO type: None [setting not specified by T-Mobile US]

MVNO value: Not set [setting not specified by T-Mobile US]

1 Like