Hi there,
I've been racking my brain on this but I can't seem to figure it out. I have been on both Carbon 4.2.2 and XenonHD for my XT926 but I can't for the life of me get MMS to send or receive. SMS work just fine but when I try to send a picture it just says sending... for infinity. When I flash back to stock 4.1.2, I can easily send MMS again. I've been searching for a while now for the answer but it seems to be working fine for most people. I've tried Go SMS apn settings, rebooting while sending, flashing back to stock then to rom, etc. Any ideas out there?
Thanks in advance.
Edit: Fixed it... somehow. I tinkered with APN backup and restore and Go Sms all to no avail. But then I dirty flashed the ROM over itself and for some reason that solved half the problem. I was able to do a fresh install after that and the MMS sending was still working.
Edit 2: Nevermind. It doesn't work again. It was fixed for about an hour and now just doesn't work again.
Edit 3: My second flash back to 4.1.2 Stock System, Kernel, and Radio and then clean install of XenonHD did the trick. Glad to have that over with. Fingers crossed. You can delete this thread.
Related
i just flashed back to stock ROM and not i can not recieve text or calls BUT i can send texts and make calls. also my market isnt downloading or updating apps. i believe everything on my phone is back to stock, but i am still rooted with CWM. i would very appreciate your help!
Go into CWM and do a factory reset then fix permissions. Look for them in the CWM menus.
well this fix the problem. i just flashed a rom. do i reflash it and then do a fix permission?
nativesmiley said:
well this fix the problem. i just flashed a rom. do i reflash it and then do a fix permission?
Click to expand...
Click to collapse
No no need to reflash, just try the fix permissions and factory reset first.
Greetings, all. Long time reader, first time posting.
I had recently flashed the HFS and EB ICS roms, and both were running without issue. Then, out of the blue, I stopped receiving SMS. I could still send, but could not receive. I had read on the HFS thread that a few others had experienced this issue. After searching various threads and forums, I couldn't find a solution. After a re-flash of both HFS and EB didn’t fix the problem on either, I flashed a couple of GB roms, and was still unable to receive SMS. Finally, I restored back to Stock GB and SMS worked fine.
I am sometimes able to receive SMS on ICS when WIFI Calling is active, but it is inconsistent.
I’ve tried the following to remedy this issue, with no success:
CWM>Wipe Data, Cache, and Dalvik, Flash rom and Gapps.
CWM>Wipe Data, Cache, and Dalvik, Format Data, System, and Cache, Flash rom and Gapps.
Same steps as above, but with G2x Scrubber (sometimes scrubbing twice) thrown into the mix.
Re-downloading roms, in case of file corruption.
Fixing permissions before and after first boot.
Master reset before and after first boot.
GetRIL.
SMSC Update.
APN delete, restore, manually enter, etc.
Tried multiple SMS apps (Stock, GO, Handcent).
Flashing Gapps after first boot.
Skipping Google account setup on first boot.
I followed all rom installation instructions, including waiting ten minutes before touching the phone after first boot.
I suppose the only thing I haven’t tried is flashing a different Kernel after flashing the rom. My only other thought is to flash the Stock recovery, then re-flash CWM and try it all again.
If anyone has any suggestions, your assistance would be greatly appreciated.
Battery pull?
iArtisan said:
Battery pull?
Click to expand...
Click to collapse
If only it were that simple; but, no, I tried that as well.
Unfortunately I don't have anything to add other than I'm having the same issue with ICS and CM7 roms. I can receive SMS on MIUI and Bionix and have gone through the same troubleshooting steps. I'll add that I've tried a different SIM as well...no dice.
I saw someone post on another thread that they resolved this issue through T-mobile customer support, but I'm skeptical.
EDIT: Maybe I'll at least save you some time...I also tried going all the way back to stock recovery like you mentioned with no luck.
akelty said:
Maybe I'll at least save you some time...I also tried going all the way back to stock recovery like you mentioned with no luck.
Click to expand...
Click to collapse
Thanks. After reading that, I didn't bother trying. I'm happy to say I did a warranty excahnge and ICS is running beautifully on my new G2x, though I still wish I could've figured out what the issue was with the last one. Thanks again for your response and trying out that fix.
If anybody's still following this thread I found a solution for GB roms that cannot receive SMS. I had trouble with EaglesBlood and tried flashing the Trinity kernel...viola! Getting all my texts now.
So I decided to take the leap and flash 10.1. Flashed the most recent nightlies build. Everything seemed to work fine. I have full 4G data without a problem, I can receive messages, but I am unable to send them.
Any suggestions would be greatly appreciated. I don't want to ODIN back to stock...
Thanks in advance.
Recently lost the ability to send MMS messages on any custom ROM on my XT1031(cdma) The only modification I've done lately is try out a CM12 build,wiped everything and then restored a backup of Liquid Smooth KK. I noticed MMS wasn't working, downloaded a SlimKat ROM and also can't send MMS with it. I've tried flashing MMS fix zips with no luck.
I doubt that flashing CM12 has anything to do with MMS messing up, but I have made no other changes, flashed nothing, no mods etc before or after. Any ideas how I can get back MMS capabilities?
lost
At this point I've tried every "MMS fix" zip I could find for Boost. All APN settings seem to be fine. I haven't a clue where to go from here. Maybe I'll try going back to stock and see what happens.
I've got a bit of an issue here. Out of nowhere (I've had the latest OTAs for about 2 weeks now) I am unable to receive SMS. When one tries to come through I got a "com.android.phone has stopped". I was bone stock, no unlocked bootloader or anything. Since then, I have tried a couple different ROMs but still seem to be unable to get SMS. MMS come through fine and I can send outgoing messages, but SMS do not work. Data also seems to work fine.
Any ideas would be incredibly helpful.
Thank you!
ETA : On the first boot of a stock + root install, I was able ot send one before getting the error. I don't understand. After the error pops up once, I can not get any more SMS.
ETA 2 : I have flashed the factory CM11 image and still get the issue on CM11. I am at a loss and have no idea what else to do. It seems to be a hardware problem.
ETA 3 : Here is my exact crash report.
java.lang.NullPointerException: Attempt to invoke virtual method 'long com.android.internal.telephony.SmsMessageBase.getTimestampMillis()' on a null object reference
at android.telephony.SmsMessage.getTimestampMillis(SmsMessage.java:625)
at com.android.internal.telephony.InboundSmsHandler.notifyAndAcknowledgeLastIncomingSms(InboundSmsHandler.java:621)
at com.android.internal.telephony.InboundSmsHandler.handleNewSms(InboundSmsHandler.java:510)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:397)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
I had the exact same problem on my wife's OPO, rooted, stock ROM, though it turned out slightly differently. The update gave the never-ending com.android.phone error. You can go into Airplane Mode to stop the crash. I read through the crash logs, and figured it was something to do with the APN. I deleted the APN, turned off Airplane Mode, and the crash stopped.
Phone and SMS work fine, as does wi-fi. However, I couldn't get any data at all. Not a great solution. I couldn't manually set the APN either, since I got a "APN Settings not allowed for this user" message, and removing the SIM, rebooting without it, then inserting it again, didn't help.
Also, root was removed. I installed TWRP and re-flashed the SuperSU zip file (make sure you go directly into recovery after the fastboot reboot or it'll flash Cyanogen Recover on top of TWRP and you have to start over!).
I did a full Titanium Backup as well as a Nandroid backup to a USB-OTG drive. Next step is to do a factory reset in TWRP and see if that fixes the APN issue.
Synyster06Gates said:
I've got a bit of an issue here. Out of nowhere (I've had the latest OTAs for about 2 weeks now) I am unable to receive SMS. When one tries to come through I got a "com.android.phone has stopped". I was bone stock, no unlocked bootloader or anything. Since then, I have tried a couple different ROMs but still seem to be unable to get SMS. MMS come through fine and I can send outgoing messages, but SMS do not work. Data also seems to work fine.
Any ideas would be incredibly helpful.
Thank you!
ETA : On the first boot of a stock + root install, I was able ot send one before getting the error. I don't understand. After the error pops up once, I can not get any more SMS.
ETA 2 : I have flashed the factory CM11 image and still get the issue on CM11. I am at a loss and have no idea what else to do. It seems to be a hardware problem.
ETA 3 : Here is my exact crash report.
java.lang.NullPointerException: Attempt to invoke virtual method 'long com.android.internal.telephony.SmsMessageBase.getTimestampMillis()' on a null object reference
at android.telephony.SmsMessage.getTimestampMillis(SmsMessage.java:625)
at com.android.internal.telephony.InboundSmsHandler.notifyAndAcknowledgeLastIncomingSms(InboundSmsHandler.java:621)
at com.android.internal.telephony.InboundSmsHandler.handleNewSms(InboundSmsHandler.java:510)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:397)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
Click to expand...
Click to collapse
Raketemensch23 said:
I had the exact same problem on my wife's OPO, rooted, stock ROM, though it turned out slightly differently. The update gave the never-ending com.android.phone error. You can go into Airplane Mode to stop the crash. I read through the crash logs, and figured it was something to do with the APN. I deleted the APN, turned off Airplane Mode, and the crash stopped.
Phone and SMS work fine, as does wi-fi. However, I couldn't get any data at all. Not a great solution. I couldn't manually set the APN either, since I got a "APN Settings not allowed for this user" message, and removing the SIM, rebooting without it, then inserting it again, didn't help.
Also, root was removed. I installed TWRP and re-flashed the SuperSU zip file (make sure you go directly into recovery after the fastboot reboot or it'll flash Cyanogen Recover on top of TWRP and you have to start over!).
I did a full Titanium Backup as well as a Nandroid backup to a USB-OTG drive. Next step is to do a factory reset in TWRP and see if that fixes the APN issue.
Click to expand...
Click to collapse
Unfortunately nothing has worked. I have fully wiped the phone MANY times. I installed 4 different 5.0.2 ROMs, rolled back to factory 4.4.4 ROM via fastboot, and even tried a 5.1.1 ROM this morning. The only time it crashes is when I receive a text.
Synyster06Gates said:
Unfortunately nothing has worked. I have fully wiped the phone MANY times. I installed 4 different 5.0.2 ROMs, rolled back to factory 4.4.4 ROM via fastboot, and even tried a 5.1.1 ROM this morning. The only time it crashes is when I receive a text.
Click to expand...
Click to collapse
Have you tried flashing a new modem at all? It seems the only thing that would be the same still after flashing all of those various ROMs would be the modem. Seeing as you have issues with the communication, I'd say modem would be a good thing to try..
Try flashing your rom, then the appropriate modem, then boot.
You can get your modem from either here (for OxygenOS) which should work for CM12, 12.1, etc. or here (for CM11/CM11s)
The_Symbiote said:
Have you tried flashing a new modem at all? It seems the only thing that would be the same still after flashing all of those various ROMs would be the modem. Seeing as you have issues with the communication, I'd say modem would be a good thing to try..
Try flashing your rom, then the appropriate modem, then boot.
You can get your modem from either here (for OxygenOS) which should work for CM12, 12.1, etc. or here (for CM11/CM11s)
Click to expand...
Click to collapse
I'm beginning to think T-Mobile had an issue with the OPO devices or something. I was speaking with someone across the country (eliminating a tower problem) that was running Oxygen OS and I had restored to COS12 at the time. Both of our devices suddenly got all the texts that had previously not come in and they started working correctly at the same time. As of right now it seems I'm good to go.