With the very strong caution that I am not at all an ADB expert and did this with every possibility it would brick my phone (Make a backup with Mudita Center First!!), this is what I did:
Enable USB debugging on your MK by going to Settings>About and tapping the build number a bunch of times until it asks if you want to turn on USB debugging.
I’m experiencing this exactly. I use mint mobile. It is really, really crucial that I am able to receive SMS messages. Is there a simpler solution that doesn’t involve ADB?
@celebratetheday Thank you for giving us this feedback & welcome to the Mudita Forum! We’re glad that you’re here. Our team is currently into this issue. We appreciate your patience while we try to figure this out.
Thanks for your reply! I just submitted a ticket with more details as well. Is there an ETA into when this will be resolved? I really, really want the Kompakt to work for me, but I’m feeling lost after learning that I’m missing so many SMS messages (even after disabling iMessage, removing myself from RCS, etc.).
A timeline update would be really helpful, or any other guidance for troubleshooting! Thank you!
Not sure if this does anything, but if its an IMS issue, and we suspect the Battery Optimzer or Duraspeed: adb shell settings put global duraspeed_whitelist com.mediatek.ims adb shell dumpsys deviceidle whitelist +com.mediatek.ims
Just chiming in to say that I am also having issues receiving texts. I have at least one person (iPhone user) whose texts I am only getting maybe 50% of the time. It seemed like the issue had been fixed with the 1.4 update and playing with some settings, but apparently it’s still happening. I know I’ve missed a couple texts from other people, but the issue has been the most consistent with this particular friend. I had to move my SIM back into my old smartphone this week, because I can’t keep missing messages. I might try flashing my Kompakt with LineageOS, because I really love the device, but it’s currently failing at one of the most essential functions of a phone.
I’m on Mint Mobile (which uses T-Mobile’s network), and I’ve made absolutely sure RCS is deactivated for my number. It doesn’t seem to be a specific type of message (text-only, pictures-only, group vs single) that I’m missing, either. It makes me very concerned about what other messages I might be missing. Recently there was a closure alert from my work that I should have received an automated text about and didn’t – I thought it was a problem with their system, but now I think it was my phone. Luckily I wasn’t scheduled to work that day, but that was an absolutely essential message that I missed, and I can’t risk missing another one.
You’ve described my exact experience. I am also on Mint Mobile. I have tried to troubleshoot, but the troubleshooting advice I was given to turn off Wifi calling and change my APN settings from support didn’t work. I am still missing a significant number of text messages.
Since IMS doesn’t appear as an actual app on the phone, it won’t appear in Duraspeed or Battery Optimizer settings. Duraspeed is a built-in Mediatek (the phone processor) app which kills apps in the background when the phone is experiencing slow-downs. Battery Optimizer is a remant of the original Android operating system that kills apps in the background to prevent them from using battery power. From the experiences above, I guess it’s possible that the custom ROM is allowing IMS (which is required to receive messages) to be stopped in the background. Looking through logs from my phone, I found no evidence that IMS had been stopped in the background, but it’s possible.
This first command can possibly force IMS into the whitelist of Duraspeed. You can access Duraspeed settings on the phone, but IMS doesn’t appear in the list of apps, so this command just overrides the list and allows you to whitelist it along with your other allowed apps.
Similarly, IMS doesn’t appear in the list of apps you can allow in the Battery Optimizer settings. This command possibly will force the Battery Optimizer to allow IMS.
I continue to say possibly only because I have zero evidence from my phone logs that IMS was being force closed. I ran these commands on my phone anyway, just to be safe. I can’t prove they worked because I have no evidence to the contrary. However, I see no reason of danger, since IMS is something you want your phone to allow in the background anyway.
I just wanted to pop on here & share a post I saw on REDDIT yesterday about this problem.
I’m not sure how well it can work, but I felt lit’s worth sharing.
I continue to have issues as well with missing texts, intermitttent data connection, (won’t connect to Lte, gets stuck on 2G I think and shows an ‘E"‘), and an intermittent cellular connection as well. On Mint Mobile, made sure APN settings are correct, etc. On latest 1.4.0. Happens every few days. The only way to get my signal to come back and work is to download a new eSim from Mint. (I think I’ve don’t this 3x now over the last month for context) Would love if we could get this fixed because I love this phone and want to keep, but this is very concerning
I’m also on T-Mobile using 1.4.0 and continue to miss texts. So far, I have only identified that I am definitely missing group texts, both new messages in previously existing threads from before I got my Mudita and newly created groups as well. The latter is much more important. I am two weeks out from deregistering my number from iMessage and RCS. I have the MMS group messaging feature turned on on the Kompakt.
Old iMessage threads converted to RCS for some reason, and I stopped getting those messages though others in the group continued to. This is actually fine for me and I solved the problem. I’m keeping my old iPhone and after adding myself to the thread again with my email address it re-converted to iMessage. I am participating successfully in these threads again. These are important groups and worth checking my iPhone 1-2 times a day for.
However, the real issue is that I often do not receive messages in groups that were newly created after I deregistered and transferred the SIM to the Mudita. Already, I have missed two critically important threads. One that was started by my boss, causing me to look bad at work, and one that was organizing a surprise party for a friend which I ended up missing. This completely defeats the purpose of the Kompakt. While everything else about it is great, I am becoming more limited in the most important aspects of life. I really love the Mudita and want to make it work, as getting almost totally off my iPhone has been huge for me. But I’m frustrated with the lack of clarity around what causes this issue, let alone the lack of a definite solution. I’ve probably poured more hours into figuring this out than I would have wasted on my iphone the last few weeks, which is a lot.
I am hoping the magical “30 days” after deregistering does something, but almost everything I’ve read has said that the deregistration process should take hold in no more than a few days. The group texts I have definitely missed have come from both iPhone and Android (RCS) users, and I think the problem has something to do with both still identifying my number as RCS-capable for some reason. After I sent an individual message to the Android user from my Kompakt, a subsequent group they created worked. But the same did not work with the iPhone user.
On a separate note, is it true that SMS works over wifi but MMS does not?
Some clarity on what is happening and why, steps I could take personally to fix this, and assurances that the Mudita team does have a solid plan to address this on a specific timeline would go a long way in helping to reassure me. I realize this has been talked about in different threads on the forum but the info should really be consolidated somewhere on the website as opposed to a hodgepodge of theories scattered around the forums. To be totally frank, it’s the core function of the phone, and it doesn’t work. I really want to keep the Kompakt because it could make a huge difference in my life, but it’s becoming hard to justify keeping. I also think it’s unfair that it takes potentially up to 30 days for messaging to maybe start working properly, but the return window is only two weeks.
