I am using an I337M S4 on an Alaskan carrier and I am running into the same issue with all Cm12 builds. After sending an MMS, I lose my data until I delete the MMS message. It happens whenever someone tries to send one to me as well. I am on NC1 baseband, using latest Philz, doing a complete wipe before every flash. I have googled this, as well as searched the forums, but I have found no good answer. Has anyone run into this and managed to fix it?
*update* MMS works on stock and GPE lollipop. It will not work on any CM based rom, not even unified 4.4.4 (even though it used to). I have Odin flashed the stock firmware to see if it fixed anything, alas, nothing. Does not seem to work on SlimLP as well. Any suggestions would be appreciated. I do enjoy stock and GPE, but would like some of the customization of CM.
Bump, because I need a little love on this.
I was having the same issue, different network though (ATT). I just tested to make sure this worked before I posted:
1. Make sure your APN settings are correct, and you've selected the correct APN from the list
2. Delete all unused APNs. I actually deleted all but the one I'm using.
After that, I was able to send/receive MMS without losing my data every time. Hope this helps.
Related
Hey, I normally wouldnt make a help thread. But Im at a total loss of ideas on how to fix this. My Nexus 4 has been running on AOKP 4.3 nightlies for a week or so perfectly fine. Today out of the blue I lost signal all together, so I went through the normal steps of checking if everything is in order. I tried to go into my apn settings to check those, but I just got a force close upon opening my mobile networks settings. I tried using the *#*#INFO#*#* menu to check my phone settings in there, but that force closed as well.
So I flashed a clean ROM and tried to check my APN settings. I was able to get into the APN menu this time, but when I would try to save an APN and it would just exit the setup screen without saving an APN. When I try and change the setting to anything (for example, GSM, WCDMA, etc) in the *#*#INFO#*#* menu it instantly resets to "UNKNOWN" I have tried flashing multiple new radios, and new kernels and nothing has worked. I'm totally lost.
Any help would be enormously appreciated. All of my previous phones were CDMA phones so I cant really just swap my sim into an old phone to use.
EDIT: Problem was resolved. If you find this thread because you have a similar problem, download the factory image from Google's site and flash that. That fixed it for me.
calebloop said:
Hey, I normally wouldnt make a help thread. But Im at a total loss of ideas on how to fix this. My Nexus 4 has been running on AOKP 4.3 nightlies for a week or so perfectly fine. Today out of the blue I lost signal all together, so I went through the normal steps of checking if everything is in order. I tried to go into my apn settings to check those, but I just got a force close upon opening my mobile networks settings. I tried using the *#*#INFO#*#* menu to check my phone settings in there, but that force closed as well.
So I flashed a clean ROM and tried to check my APN settings. I was able to get into the APN menu this time, but when I would try to save an APN and it would just exit the setup screen without saving an APN. When I try and change the setting to anything (for example, GSM, WCDMA, etc) in the *#*#INFO#*#* menu it instantly resets to "UNKNOWN" I have tried flashing multiple new radios, and new kernels and nothing has worked. I'm totally lost.
Any help would be enormously appreciated. All of my previous phones were CDMA phones so I cant really just swap my sim into an old phone to use.
Click to expand...
Click to collapse
Try have a look at this http://forum.xda-developers.com/showthread.php?t=2087227
arifhazwan said:
Try have a look at this http://forum.xda-developers.com/showthread.php?t=2087227
Click to expand...
Click to collapse
I've tried flashing a few of the radios from that thread with the same result every time, unfortunately.
Currently what ROM you're using? If you're on nightlies you should be aware that it isn't stable. I suggest you restore your nand backup if you have one.
arifhazwan said:
Currently what ROM you're using? If you're on nightlies you should be aware that it isn't stable. I suggest you restore your nand backup if you have one.
Click to expand...
Click to collapse
Im currently on an AOKP nightly. Im trying to flash back to stock but Im having trouble getting it to do that for some reason too. Its acting like its been flashed, but it always boots up into AOKP again. Trying my hand at another toolkit before I start attempting to do it manually.
arifhazwan said:
Currently what ROM you're using? If you're on nightlies you should be aware that it isn't stable. I suggest you restore your nand backup if you have one.
Click to expand...
Click to collapse
Flashing back to a factory image fixed the issue. Thank you!
Don't forget to make a backup. By the way I just got my 4.3 with CM 10.2 working with franco kernel.
I finally got superuser working by flashing Echoe Illusion, the full touch-wiz version with Android 4.3. At first it seemed like I had everything working but the next day when I left the house (no longer connected to home wifi) I quickly realized it was refusing to connect to mobile data. I also cannot send text messages, and likewise I can assume I can't get them either. I have tried flashing the nightly CM11 build and 3G connected although LTE did not. I wasn't in an area where I expected reliable LTE anyway so that's not even an issue at this point because I'd very much like to use this Echoe Illusion rom, or another Touch-wiz based one. I just can't go downloading a bunch of them because I have a severe restriction on data usage and have already downloaded Echoe Illusion AND multiple other things. If it matters, my baseband ends in MJA.
I have also attempted to flash different modems with Odin, although all of them failed completely to flash at all and at this point I have to honestly admit I don't know what I'm doing. This is most definitely not my first time rooting...I'm just used to HTC phones, the Evos in particular. Thanks in advance if anyone can help or provide useful tips!
oh and P.S. I can't go back to the stock firmware because I must have flashed an incorrect kernel, and it borked the phone. I only got it working again by flashing a separate rom (Echoe Illusion) and have since flashed other kernels with no ill effect. I had a nandroid backup of the stock rom before I borked it, but every time I try restoring it, it stops at the yellow Sprint screen and won't boot.
To preface the current issue with my phone, I guess I should probably give some history of what I've done to it. I got my S4 around November last year, where I kept TouchWiz for about a good 3 months. At the end of those 3 months, I downloaded and installed CM KitKat using their easy installer and it worked! However, when Lollipop came around, I got a little impatient and decided to get CM12 using Antares version. Initially, I noticed there were a few bugs/glitches, but ignored them for the time being. As time went on, it became increasingly aggravating and so a few dayus ago I tried to switch back to stock TouchWiz. When I was setting up the phone, I noticed that the wi-fi would just not turn it. It would stay at "turning on" for a very long time with no sucess. Thus, I decided to switch back to Antares version of CM, but now there were a few issues: service was VERY spotty and the piece de resistance: no sound at ALL, and youtube would never play videos. I searched around and saw that using the Sound Recorder would give me an error: "Internal Application Error. Microphone may be in use." Now I'm not the most techy person around and probably should not have been messing around with my phone, but now all I want is a properly working phone, doesn't matter if its kitkat or lollipop. Your help is greatly appreciated. (If you need to know more info, go ahead and ask, because I'm very new to all this) Thanks!
If you want the stock ROM back, flash it twice using Odin. General consensus here is that you need to flash the modem twice in order for WiFi and cellular radios to work properly. Flashing the ROM twice will do that without having to track down just the modem file and trying to flash that.
Strephon Alkhalikoi said:
If you want the stock ROM back, flash it twice using Odin. General consensus here is that you need to flash the modem twice in order for WiFi and cellular radios to work properly. Flashing the ROM twice will do that without having to track down just the modem file and trying to flash that.
Click to expand...
Click to collapse
Unfortunately, it doesn't seem to be working :/ When setting up my S4, it's still stuck at turning on the wifi
I switched back to Antares CM, and everything works fine except for sound/microphone (to my knowledge). Would there be any way to fix this?
I've seen this mentioned in other places before, other threads and in the r/motox subreddit, about how the open GAPPS package apparently flashes the Google Dialer over the stock one, and it doesn't work with the Pure? Which is what causes the reboots whenever I try to make a call or, presumably, get a call, which until now I chalked up to random reboots in CM13.
So I've seen a bunch of posts about it, but none that explain how to actually fix it? Am I doing something wrong from the start?
Bonus question, I've been having radio problems on almost every AOSP rom I flash, either Wifi doesn't work upon booting and it persists in other ROMS or cell service is out (even though LTE data works fine). Is the radio (which I assume is the same as the "modem") included in each ROM package and is replaced every time you flash a new one, or does it persist in some system directory cross-firmware?
There are so many posts on how to fix I'm not sure how you could miss them. Set as default or uninstall.
lafester said:
There are so many posts on how to fix I'm not sure how you could miss them. Set as default or uninstall.
Click to expand...
Click to collapse
Set what as default? Or uninstall what? When I look in the apps list all I see is "phone". Nothing under the name google dialer or anything. It's just confusing, I didn't have this problem on other phones.
Sorry for the double post but I figured instead of making another thread I'll continue asking here, I'm STILL having cell issues, no matter what ROM I flash, stock or AOSP, or any of the radios I can find around the forums, whether it be with the February security update or not, I'm still not getting a connection. In fact once I flashed a new modem, I went from not being able to send texts etc. but able to get LTE data, to getting no connection at all. I'm totally lost, this is the second time it's happened I have no idea what to do. Happens in every single rom.
Last time it was fixed once I flashed from stock (which I had in turn flashed to try to get rid of the problem) to CM13 I think. But it was totally random, I have a feeling it didn't even have anything to do with the ROM itself...
Google searching: "Google Dialer reboots when making a call" >
http://android.stackexchange.com/qu...s-when-making-or-receiving-a-call-nexus-6cm13
https://www.reddit.com/r/cyanogenmo...cm_13_nexus_5_soft_reboots_when_a_phone_call/
Even from Open GApps own FAQ page:
https://github.com/opengapps/openga...boots-when-i-receive-or-make-a-phone-call-why
Thanks, I honestly dunno why I couldn't find that before. At first I wasn't even aware it was actually called the "google dialer" so I was just googling "phone app reboots after flash/root/etc" and obviously it wasn't turning up many results. But the stock rom rooted debloated thread had the instructions at the bottom, now I know. Whoops. Like I said, just really confusing coming from other phones where everything mostly just worked....
The baseband is still perplexing me though, in the bootloader under baseband it says <not found>. I'm keeping on trying to flash different stock roms to see if I get lucky.
EDIT: so I think flashing the modem at the SAME TIME as a new ROM might be the key? I think I saw something about that on some random obscure post and tried it out and bam, it worked like a charm. Anyway hopefully that works again when I flash to something new
Hello all,
I am running the XT1768 variant, Qualcomm version, rooted with Resurrection Remix version 5.8.5 unofficial. I have twrp as my recovery.
Everything was going smoothly until mms blew up. I can't send or receive pictures/files at all.
Here's what I've done so far:
I've checked the apn settings at least a dozen times and they are correct as per my carrier's website.
Tried different messaging apps and the problem persists through all of them.
I've reached out to my carrier and my favorite texting app developers and they have no clue.
I got a momentary reprieve when I force stopped the messaging service and rebooted the phone, but that trick is no longer working somehow. I tried it three times before coming here.
Everything else is working perfectly, including humongous texts. I am so confused right now.
SashaNT86 said:
Hello all,
I am running the XT1768 variant, Qualcomm version, rooted with Resurrection Remix version 5.8.5 unofficial. I have twrp as my recovery.
Everything was going smoothly until mms blew up. I can't send or receive pictures/files at all.
Here's what I've done so far:
I've checked the apn settings at least a dozen times and they are correct as per my carrier's website.
Tried different messaging apps and the problem persists through all of them.
I've reached out to my carrier and my favorite texting app developers and they have no clue.
I got a momentary reprieve when I force stopped the messaging service and rebooted the phone, but that trick is no longer working somehow. I tried it three times before coming here.
Everything else is working perfectly, including humongous texts. I am so confused right now.
Click to expand...
Click to collapse
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
madbat99 said:
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
Click to expand...
Click to collapse
If that fails try returning to stock to see if the problem persists. Occationally mms dysfunction can be upstream and require carrier involvement.
madbat99 said:
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
Click to expand...
Click to collapse
A dirty flash seems to have done the trick,though I will say I used a different download for the flash. Loving it so far.
Thank you for the help!
Davey216, I will keep that in mind if it comes back. Stock is kinda icky but I need my mms. Thank you for the reply!