XT1033 Falcon CM12 (31/01) - Cannot send/receive sms - 3G, MMS, in/out calls fine! - Moto G Q&A, Help & Troubleshooting

Hey all. I really hoped I would have sorted this just by searching but... still stuck.
I have an XT1033, which I updated from cm11 > cm12 falcon (31/01 nightly) using TWRP 2.8.1. Gapps mini modular package from PA link. From my forum searching etc I thought the XT1033 dual sim was now all good to go on the falcon nightlies but since the update I havent been able to send or recieve any sms although 3g data, incoming and outgoing calls and MMS are all fine. Below are some things I have tried.
Sim card has been tested to send and receive fine in another phone.
MMS is working fine and all APN settings have been double checked.
I've tried using the *#*#4635#*#* menu to see if the SMSC number was the problem. Confirmed it was correct.
I tried flashing again using CWM as well with the same result. Also tried again with TWRP, this time formatting (almost) everything, data, system, data/media, dalvik, regular cache etc. Tried flashing a falcon nightly from 27/01 as well to see if it worked.
It looks like this problem has occurred for a couple of XT1033 owners upgrading recently to CM12 but I'm not sure if anybody has worked out where the issue is?? If anyone has any troubleshooting ideas, suggestions etc... Thanks in advance.
:good: and thanks to the CM devs, contributors etc. (And google I suppose). Im really loving Lollipop, the material ui and all the usual CM tweaks, the rom is friggin sweet otherwise. From a long time lurker/searcher of xde who usually finds my q already answered.

Sms not working
3down2togo said:
hey all. I really hoped i would have sorted this just by searching but... Still stuck.
I have an xt1033, which i updated from cm11 > cm12 falcon (31/01 nightly) using twrp 2.8.1. Gapps mini modular package from pa link. From my forum searching etc i thought the xt1033 dual sim was now all good to go on the falcon nightlies but since the update i havent been able to send or recieve any sms although 3g data, incoming and outgoing calls and mms are all fine. Below are some things i have tried.
Sim card has been tested to send and receive fine in another phone.
Mms is working fine and all apn settings have been double checked.
I've tried using the *#*#4635#*#* menu to see if the smsc number was the problem. Confirmed it was correct.
I tried flashing again using cwm as well with the same result. Also tried again with twrp, this time formatting (almost) everything, data, system, data/media, dalvik, regular cache etc. Tried flashing a falcon nightly from 27/01 as well to see if it worked.
It looks like this problem has occurred for a couple of xt1033 owners upgrading recently to cm12 but i'm not sure if anybody has worked out where the issue is?? If anyone has any troubleshooting ideas, suggestions etc... Thanks in advance.
:good: And thanks to the cm devs, contributors etc. (and google i suppose). Im really loving lollipop, the material ui and all the usual cm tweaks, the rom is friggin sweet otherwise. From a long time lurker/searcher of xde who usually finds my q already answered.
Click to expand...
Click to collapse
same issue for me... Sms not working on any custom roms... Pls help

Not the answer you are probably wanting to hear but I have a similar problem just a different model phone. Use a 3rd party app that lets you manually set the apn. EvolveSMS or Smitten both let you do just that and are pretty nice apps as well.

Thanks for the reply
n0ts0smart said:
Not the answer you are probably wanting to hear but I have a similar problem just a different model phone. Use a 3rd party app that lets you manually set the apn. EvolveSMS or Smitten both let you do just that and are pretty nice apps as well.
Click to expand...
Click to collapse
THANKS FOR THE REPLY DEAR FRIEND.. BUT I INSTALLED SO MANY 3RD PARTY APPS LIKE TEXTRA SMS, GOSMS ETC. BUT IT DIDN'T FIX MY PROBLEM... :crying:

Related

[Q] Unable to send/receive MMS

I have been unable to send or receive MMS messages to/from anyone. Outgoing messages just get stuck at "sending" and I've had multiple people try to send me an MMS. I believe my APN settings are correct based on other threads here. Has anyone else seen/dealt with/have a solution for this bug?
I'm currently running CM10.1 April 8 Nightly off of a clean complete wipe flash, but I believe the problem has occurred with prior versions as well.
dcvito said:
I have been unable to send or receive MMS messages to/from anyone. Outgoing messages just get stuck at "sending" and I've had multiple people try to send me an MMS. I believe my APN settings are correct based on other threads here. Has anyone else seen/dealt with/have a solution for this bug?
I'm currently running CM10.1 April 8 Nightly off of a clean complete wipe flash, but I believe the problem has occurred with prior versions as well.
Click to expand...
Click to collapse
I saw some commits related to unicode encoding with the MMS app. It's possible (Disclaimer: I am not a dev, these are just theories) that these have something to do with the MMS issue. You could extract the MMS.apk from a prior build (where your MMS was still functional) and push it to /system/apps, rename your current MMS.apk to MMS.bak (just in case), set permissions to R-W, R, R, then reboot. If that works then we know there's an issue with the CM commits to the MMS.apk.
Had the same problem this morning. Turns out I had mobile data turned off.
Sent from my SAMSUNG-SGH-I727 using xda premium
Nope, mobile data is on and I have no idea when the last time it was working.
I can't be the only one dealing with this... Anyone? Now running CM 10.1 4/22 Nightly.
dcvito said:
I can't be the only one dealing with this... Anyone? Now running CM 10.1 4/22 Nightly.
Click to expand...
Click to collapse
I've been having the same issue since sometime in march. Also running CM nightlines. I've read it may be something to do with the Access Point Names but no solution is given
briguy42 said:
I've been having the same issue since sometime in march. Also running CM nightlines. I've read it may be something to do with the Access Point Names but no solution is given
Click to expand...
Click to collapse
What that means is that your APN's might not be configured properly. Compare them to the ones listed here. If that doesn't fix the MMS issue then we'll have to investigate further.
mrfeuss said:
What that means is that your APN's might not be configured properly. Compare them to the ones listed here. If that doesn't fix the MMS issue then we'll have to investigate further.
Click to expand...
Click to collapse
I've checked out and even rebuild my APN's multiple times to troubleshoot to no avail.... Let's see what ideas we can come up with... Thanks for the help so far.
dcvito said:
I've checked out and even rebuild my APN's multiple times to troubleshoot to no avail.... Let's see what ideas we can come up with... Thanks for the help so far.
Click to expand...
Click to collapse
Hmm. Interesting. And you're using the stock MMS app in the CM Nightlies? Have you tried updating to a newer version?
mrfeuss said:
Hmm. Interesting. And you're using the stock MMS app in the CM Nightlies? Have you tried updating to a newer version?
Click to expand...
Click to collapse
Yes, stock messaging app included with the CM nightlies. What are you recommending that I update?
mrfeuss said:
What that means is that your APN's might not be configured properly. Compare them to the ones listed here. If that doesn't fix the MMS issue then we'll have to investigate further.
Click to expand...
Click to collapse
Tried using this APN config too and it still didn't work, thanks for the suggestion though.
I have this issue on rooted stock jelly bean I had to set sms to convert the images to smaller resolution to get it to send. Been working for now but would like to be able to send hi res pics
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I had that issue at one time on my stock rooted unit. Turns out that AT&T had changed something on the network side and my account didn't get changed. You might call them and check the settings.
Sent from my GT-N8013 using xda app-developers app
bryanclane said:
I had that issue at one time on my stock rooted unit. Turns out that AT&T had changed something on the network side and my account didn't get changed. You might call them and check the settings.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
I've put in a trouble call with AT&T hopefully they find something....
So according to AT&T there are no network problems but my phone is not responding to push notifications from them. They want me to bring it into a "core" store to have it checked out (not going to happen on behalf of the rooting/custom ROM). I'm wondering if my Android ID#/device hostname may have changed when I did a full wipe? Although I'm not even sure that would have any effect on my problem. I'm just tossing out ideas.
dcvito said:
So according to AT&T there are no network problems but my phone is not responding to push notifications from them. They want me to bring it into a "core" store to have it checked out (not going to happen on behalf of the rooting/custom ROM). I'm wondering if my Android ID#/device hostname may have changed when I did a full wipe? Although I'm not even sure that would have any effect on my problem. I'm just tossing out ideas.
Click to expand...
Click to collapse
If I were you I'd just make a nandroid backup of my current setup, transfer that (and any other important data) to either my external or PC, ODIN back to stock and head over to an AT&T store. Just my two cents. You can always re-root and flash a custom ROM again. If you'd corrupted something through flashing (not saying you did, just a thought) getting AT&T to straighten it out and then going custom from there might be your best option.
dcvito said:
So according to AT&T there are no network problems but my phone is not responding to push notifications from them. They want me to bring it into a "core" store to have it checked out (not going to happen on behalf of the rooting/custom ROM). I'm wondering if my Android ID#/device hostname may have changed when I did a full wipe? Although I'm not even sure that would have any effect on my problem. I'm just tossing out ideas.
Click to expand...
Click to collapse
Sinnce AT&T uses the IMEI number as the ID for the device, that wouldn't be the issue you aren't receiving push messages. I agree with mrfeuss, back up the phone, flash the stock rom, and go have AT&T fix it on their end. Then you can re-root and install your custom ROM again. Better to have them look at it than live without MMS.
bryanclane said:
Sinnce AT&T uses the IMEI number as the ID for the device, that wouldn't be the issue you aren't receiving push messages. I agree with mrfeuss, back up the phone, flash the stock rom, and go have AT&T fix it on their end. Then you can re-root and install your custom ROM again. Better to have them look at it than live without MMS.
Click to expand...
Click to collapse
Check mms after returning to stock as that may solve your problem.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I was afraid that was going to be the suggestion.... Guess I'll start my Firmware DL and backup now... here we go lol
mrfeuss said:
If I were you I'd just make a nandroid backup of my current setup, transfer that (and any other important data) to either my external or PC, ODIN back to stock and head over to an AT&T store. Just my two cents. You can always re-root and flash a custom ROM again. If you'd corrupted something through flashing (not saying you did, just a thought) getting AT&T to straighten it out and then going custom from there might be your best option.
Click to expand...
Click to collapse
Just used Odin to flash back to stock. After the Odin reboot how long should it take for the phone to start up? I've been sitting on the ATT logo screen for a few minutes now.... please don't tell me I bricked....
Never mind, figured out my own mistake..... Always factory reset/clear data before flashing!

Synergy ROM aosp MMS not working properly

Ok so I installed synergy ROM and the aosp group messaging isn't working right. Some of my friends texts will appear in the convo while others won't and its very annoying. I rebooted, reinstalled, wiped data, everything and it still won't work. Idk what to do. Any help is appreciated, thanks
tips14 said:
Ok so I installed synergy ROM and the aosp group messaging isn't working right. Some of my friends texts will appear in the convo while others won't and its very annoying. I rebooted, reinstalled, wiped data, everything and it still won't work. Idk what to do. Any help is appreciated, thanks
Click to expand...
Click to collapse
Same issue here. Tried HyperDrive, Synergy, and now BoneStock ROM... pretty annoying.
Any updates on this? You get it fixed? I'm having same problem

[Q] SMS not working after flashing CM11 20131214

Can anyone help me figure this out? I successfully flashed CM11: cm-11-20131214-NIGHTLY-d2vzw.zip
Problem is that i can't get SMS to work at all. Native messenger just force closes. Hangouts forcecloses, Handscent, same, GoSMS pro same...
Any fixes?
Did you clean flash (wipe all partitions)?
Sent from my SCH-I535 using Tapatalk
I have the same problem on my SGS2 i9100, I've done clean flash, still isn't working.
As for the OP question, gapps version did you flash? I've found the "mini modular package" works the best and causes the least FCs.
I've heard/seen nothing but problems with those CM11 nightlies. You guys might want to consider one of the AOSP roms til CM gets their s**t together. I'm on Gummy and have zero issues.
CM11 Sending SMS Problem solved!
I was also have the same problem, not able to send SMS after replacing the stock rom with cm11. After lot of googling also I was not able to correct the problem. Attempt Changing SMSC from 00 also failed. Then I found the root cause, that is while flashing cm11 I wiped everything including internal memory that only created the problem. Hence again I flashed stock rom and changed the SMS message center number and again I flashed CM11 this time without wiping internal memory. Now SMS is working!!!

No WhatsApp Connection with Mobile Data.

Hello, Today i Updated my opo to the latest cm 13. Everything Works Great, except WhatsApp with Mobile Data. Its working Great with WiFi but its Not connecting while using cellular Internet. Somebody had the Same issue? My APN is configured correctly. And stuff like Chrome and Snapchat is working finde too.
€: noticed, that i get Snapchat notifications only with WiFi
I have the same issue with my OPO since the last COS13.1 update.
But I am not really sure if it is the COS13.1 update, because in parallel I have updated WhatsApp.
Now I have the following versions:
COS 13.1.2-ZNH2KKAS3PO
WhatsApp 2.16.259
Fixed it, had to do a wipe and reinstall cm12.1. Than i updated OTA and now its working fine on 13.1.
A wipe is the hard way. I hope there will be a less painfull solution.
Just a wipe on cm13 didnt work for me either, tried flashing and wiping with TWRP and fastboot, both didnt change anything. I really had to go back to cm12 to get Whatsapp working with mobile data. Curiously everything is working great on CM13 too since i did the OTA updates.
So you are using CM13 and not COS13?
My OnePlus One is on Stock software (COS) since the first day.
I have only updated via OTA and I have never installed/used TWRP
or similar software on my phone.
Fixed it! Found a hint in the OnePlus One forum.
I have deleted all APN and kept only the one which is correct for
the network I am using (web.vodafon.de)
Now it works perfectly.
Thanks a lot. I also did the same and it worked for me. I deleted all other APNs except web.vodafone.de and it worked for me too..
Deleting all the other APNs also did the trick for me.
Thanks a lot!

Moto G3 Soft Reboot everytime on nougat.

My Moto G3 XT1550 2GB always randomly reboots everytime when I install any Nougat OS.:crying:
I need help.
Anyone please!?!?
maheshfuture said:
My Moto G3 XT1550 2GB always randomly reboots everytime when I install any Nougat OS.:crying:
I need help.
Anyone please!?!?
Click to expand...
Click to collapse
Clean flash... wipe system, data, and caches, then flash only the ROM without Gapps and verify boot. If it still fails you will need to give us more information of what you were on before, especially any custom kernels you may have tried.
I tried.
acejavelin said:
Clean flash... wipe system, data, and caches, then flash only the ROM without Gapps and verify boot. If it still fails you will need to give us more information of what you were on before, especially any custom kernels you may have tried.
Click to expand...
Click to collapse
I installed AOSP, Lineage OS and Ressurection Remix WITHOUT no other custom Kernels with and without installing Gapps. But when I run Chrome ,Maps or Mx Player, it soft reboots itself. And also the internet connnection and calls gets cutoff while downloading files. All Nougat roms that I installed has the same problem. So now I'm running stock rom 6.0.1 rooted and it has not shown any of the above problems. And also the phone lags from time to time on 7.x.x. I am completely hopeless now now. I love nougat. And I'm a big fan of Custom ROMs. Please can you find some other way.
maheshfuture said:
I installed AOSP, Lineage OS and Ressurection Remix WITHOUT no other custom Kernels with and without installing Gapps. But when I run Chrome ,Maps or Mx Player, it soft reboots itself. And also the internet connnection and calls gets cutoff while downloading files. All Nougat roms that I installed has the same problem. So now I'm running stock rom 6.0.1 rooted and it has not shown any of the above problems. And also the phone lags from time to time on 7.x.x. I am completely hopeless now now. I love nougat. And I'm a big fan of Custom ROMs. Please can you find some other way.
Click to expand...
Click to collapse
Sounds like it's time to revert to stock via fastboot and start clean... Also be aware there is a known issue with LineageOS and others based on it that supplementl GPS data is broken, the fix is delete your APN and re-enter it manually without the "supl" APN type.
Done it.
acejavelin said:
Sounds like it's time to revert to stock via fastboot and start clean... Also be aware there is a known issue with LineageOS and others based on it that supplementl GPS data is broken, the fix is delete your APN and re-enter it manually without the "supl" APN type.
Click to expand...
Click to collapse
Already done fastbooting to stock rom. And then tried installing custom roms but that didn't fix the problems.
acejavelin said:
Sounds like it's time to revert to stock via fastboot and start clean... Also be aware there is a known issue with LineageOS and others based on it that supplementl GPS data is broken, the fix is delete your APN and re-enter it manually without the "supl" APN type.
Click to expand...
Click to collapse
What do you mean by GPS data is broken? What does the APN have to do with GPS. Do phone calls go through?
Thanks, just trying to understand cause I just flashed ViperOS, based on linageOS
melp57 said:
What do you mean by GPS data is broken? What does the APN have to do with GPS. Do phone calls go through?
Thanks, just trying to understand cause I just flashed ViperOS, based on linageOS
Click to expand...
Click to collapse
There is a known issue with how LineageOS handles the APN entries in some cases (not everyone has this problem), specifically regarding APN type "supl" which is short for "Secure User Plane Location" which is location information from your carrier and it's towers which is used by location services (and GPS indirectly). I can't find the raised bug entry, but the fix is to delete your apn and rebuilt it manually, skipping "supl" in the APN Type field, but you still get SUPL data, it comes from "default". Remember that APN Type is used to tell your phone what type of data uses what APN, if a type isn't specified then it uses default (with the notable exception of mms which must be implicitly configured).
But I didn't really intend to make this a crash course in APN's and how they work, just suffice it to say that there is a GPS/Location problem with how LineageOS handles SUPL being configured in an APN... This is temporary and is either fixed or will soon be fixed in LineageOS and will trickle down to other ROM's based on it.
For reference; https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-248
I have this problem too and it was very frustrating.
Goodluck!
grantdb said:
For reference; https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-248
I have this problem too and it was very frustrating.
Goodluck!
Click to expand...
Click to collapse
Wow this is great, I think it might fix it. The only thing is - I can't delete the APN for some reason. Rooted with magisk.
NSD said:
Wow this is great, I think it might fix it. The only thing is - I can't delete the APN for some reason. Rooted with magisk.
Click to expand...
Click to collapse
Try making a new entry for APN first. And you have to save the original APN and then you can discard I think.
grantdb said:
Try making a new entry for APN first. And you have to save the original APN and then you can discard I think.
Click to expand...
Click to collapse
You are the best. That's exactly what I did and it worked, thanks a bunch!
NSD said:
You are the best. That's exactly what I did and it worked, thanks a bunch!
Click to expand...
Click to collapse
No problem it drove me nuts trying to figure this out!
I am also facing the same issue but in my case it happens while using all the roms I hv tried many custom roms but faced frequent reboots, most disappointing thing is that it was happening when I was using the stock rom as well.... Can anyone help me on this ... Thanks in advance
sunnyMehra22 said:
I am also facing the same issue but in my case it happens while using all the roms I hv tried many custom roms but faced frequent reboots, most disappointing thing is that it was happening when I was using the stock rom as well.... Can anyone help me on this ... Thanks in advance
Click to expand...
Click to collapse
Not good sign if it happened on stock. The only thing I can think of is do a compete wipe and try start again with original firmware. Maybe there was somthing wrong from the factory. Look here https://forum.xda-developers.com/showthread.php?t=3187750
Ya never know...

Categories

Resources