Related
Not sure if you guys want this here...just thought I'd post here...move if needed...
Ok, problem I've had for awhile now..
I was using Tazz 10 and Nonsensikal 7.0. They were both working perfectly then all of a sudden, I started to not receive txt messages. I can send, but not receive. So I wiped, re-flashed each ROM seperately, nothing. Wiped and nandroid to a ROM that was working, nothing.
I am now doing the Flashback 1.5 to get to Stock ROM. If still not working, gotta take to Verizon. But once it works...gonna Root again and put Tazz 12 and Nonsensikal 8.8. and see if the issue returns.
That's all, just wanted to post if any one else experiences this issue.
OK....flashed the Stock ROM...I am now recieving Txt messages...
Next...re-root and flash Nonsensikal, and see if I am still able to recieve Txts.
After flashing a stock ROM, you should back up your APN files. One way to do this is with a free app on the market called APN backup and restore. It will back up to an XML file on your SD card. After flashing another ROM, use that app to restore the APN files.
What are the APN files for? I am stuck at boot screen since updating OTA. Haven't had a chance to root yet. So I can still do it.
BlazinDANDAMAN said:
What are the APN files for? I am stuck at boot screen since updating OTA. Haven't had a chance to root yet. So I can still do it.
Click to expand...
Click to collapse
I believe they tell your phone which towers to connect to. So if you don't have the correct APN files, your phone has issues receiving messages. Some of the ROMS that are based on ROMs from other carriers may not have the right APNs.
synesthete said:
I believe they tell your phone which towers to connect to. So if you don't have the correct APN files, your phone has issues receiving messages. Some of the ROMS that are based on ROMs from other carriers may not have the right APNs.
Click to expand...
Click to collapse
Shouldnt a *228, option 2, update the PRL to current for Verizon?
Well, I went through everything and now I am NOT receiving messages again. I re-rooted and flashed Tazz 12 and now not receiving Txt messages again. Damn! I have to have an unrooted phone now? This sux. I can't be with out Txt messaging.
FYI...I restored APN's and did *228
Is it with your stock txt app or did you download one? I had problems similar to yours with ChompSMS on NonSensikal. Wiped and reinstalled rom but stuck with Stock messenger and the problem never returned. If you are on stock try a different txt app. Good luck!
It was with both apps...neither were recieving. I have since restarted and it seems to be working at the moment...
Could it be that your not popular?
jk, have you turned the Wi-Fi off, cause that has seemed to work for me
BlazinDANDAMAN said:
It was with both apps...neither were recieving. I have since restarted and it seems to be working at the moment...
Click to expand...
Click to collapse
I would have the problem with both apps as well but when I reinstall the rom it would work and then a little while after installing Chomp it would stop again. Finally did a reinstall and didn't install ChompSMS and everything worked and stayed working. Good Luck!
One of my friends was having this issue too and it was due to which radio version she was using. The radio included in Tazz, KaosFroyo, and Nonsensikal were all giving her issues. She switched to xtrSense and the radio with that played nicer with her phone and all was well. Check out which version each rom runs and then you can flash the other radio over whichever rom you'd want. With that being said, I should also point out that there is a small chance, were something to go wrong with the radio flash, of damaging your phone. Now I have flashed two or three different ones, and had another friend purposely try to brick his phone by flashing radios from different phones even as well as pulling the battery while flashing a radio, and did not brick his phone. Just like rooting your phone, there's always a chance something can go wrong, but at that stage it's all about weighing the pros and cons and if you have a back up plan. Hope this helps.
I'm having the same problem. I was running KaosFroyo then Nonsensikal with no issues. I switched to Tazz Froyo today and now I can't receive texts, only send them. I flashed back to Nonsensikal and it didn't remedy the problem. The radio is the same on Tazz and Kaos (didn't check Nonsensikal) so I don't think that's the issue.
I would like to point out that kaosfroyo doesn't include a radio it uses whatever you have
Sent from my FroyoEris using XDA App
Problem Solved
I found the solution here: http://forum.xda-developers.com/showthread.php?t=770879
Hopefully it works for you as well.
Interesting problem that I suddenly have after installing rom. First I have been installing just about every rom has come for the last 6 months. Today I installed latest Carbon ROM from here http://forum.xda-developers.com/showthread.php?t=2310695 today and it installed ok, but upon booting for the first time, it got stuck the setup right at the beginning where I press the language (English). It just sat there and didn't do anything. I tried reinstalled the rom, and it did the same thing.
So I assumed a had a bad download, so I went to restore my daily driver backup rom (Zone sense 4 rom from here http://forum.xda-developers.com/showthread.php?t=2116509). But now I have no mobile data or mobile connection at all. I get a triangle next to the bars and whenever I restart phone I get this message "Global data roman access is allowed. Significantly higher charges may apply". I have never seen that before.
I have tried removing sim, toggling all mobile network options (CDMA, global, roaming, etc.) and I still get no connection at all. Any ideas here? I am on Verizon.
smacklayer said:
Interesting problem that I suddenly have after installing rom. First I have been installing just about every rom has come for the last 6 months. Today I installed latest Carbon ROM from here http://forum.xda-developers.com/showthread.php?t=2310695 today and it installed ok, but upon booting for the first time, it got stuck the setup right at the beginning where I press the language (English). It just sat there and didn't do anything. I tried reinstalled the rom, and it did the same thing.
So I assumed a had a bad download, so I went to restore my daily driver backup rom (Zone sense 4 rom from here http://forum.xda-developers.com/showthread.php?t=2116509). But now I have no mobile data or mobile connection at all. I get a triangle next to the bars and whenever I restart phone I get this message "Global data roman access is allowed. Significantly higher charges may apply". I have never seen that before.
I have tried removing sim, toggling all mobile network options (CDMA, global, roaming, etc.) and I still get no connection at all. Any ideas here? I am on Verizon.
Click to expand...
Click to collapse
Need to RUU it and go again, its known to happen on aosp roms for some reason.
pio_masaki said:
Need to RUU it and go again, its known to happen on aosp roms for some reason.
Click to expand...
Click to collapse
Thanks. I did that and it worked. Any thoughts on how to avoid that in future aosp roms? Did I do something wrong or is it totally random?
smacklayer said:
Thanks. I did that and it worked. Any thoughts on how to avoid that in future aosp roms? Did I do something wrong or is it totally random?
Click to expand...
Click to collapse
Its apparently random. I've had it happen twice, once back non CM10 when it just got RIL going, and a build ago on Carbon.
I'm going through this right now. I rru'd and can connect to 3g and use the data but no texts and when I try to make a call I end up with a Verizon message saying my number is inactive. Everything works fine on my backup phone. So its not a problem with Verizon
Edit... I'm going to ruu again and factory reset before booting because I think I remember seeing that posted at some point
Sent from my RM-845_nam_vzw_100 using Tapatalk
I'm going through this right now. I rru'd and can connect to 3g and use the data but no texts and when I try to make a call I end up with a Verizon message saying my number is inactive. Everything works fine on my backup phone. So its not a problem with Verizon
Edit... I'm going to ruu again and factory reset before booting because I think I remember seeing that posted at some point
EDIT 2.... re rru'd still having problems it will not make calls and will get 3g data when set to roaming which it seems to be on with the triangle above the signal.
anyone know the Verizon apn's i only have verizon internet in my apn list.
Edit 3 All fixed. i was factory resetting in stock recovery to no avail but a factory reset in sense itself worked
So, I suddenly started having an issue with SMS a day and a half ago with my Galaxy S4 on CM 11.0. Receiving texts works with no issues, but sending texts is hit or miss.
- Off a fresh reboot, the first text I send to someone always works.
- If I immediately text them again, it fails to send 100% of the time.
- Retrying doesn't work.
- If I reboot and try to resend that failed message, it works. If I send another message immediately after that, it fails.
- Sometimes, if I don't reboot but try to resend the failed message hours later, it suddenly works.
I tried a clean flash (with data/cache/dalvik wipe) of the latest nightly, but it didn't fix the problem.
I also tried reseating my SIM card.
I thought maybe this was a tower issue, but I travel a lot for my work and this is everywhere, strong or weak signals.
Research has told me that my APN settings may be screwed up, but when I go to check them the option is grayed out under Settings -> Mobile Networks. I tried using APNManager to check, but it force closes (Unfortunately, APNManager has stopped).
Just in case it helps, I'm attaching a ZIP containing syslog files. These were pulled after a fresh reboot and two texts sent (one succeeded, one failed).
Small update: I've determined that forcing airplane mode on/off will also let me send another text message.
At this point I'm going to try flashing a different modem and hope that fixes the issue. Will report back.
Unfortunately a new modem did not help. I'm still having the same texting issues. Any suggestions at this point are appreciated, I am once again out of ideas.
Do you have Google voice installed? If so make sure that the sms feature is disabled. Or just remove google voice. For more help visit the source.
(Source: http://forum.xda-developers.com/showthread.php?t=2561308 )
Sent from my SCH-I545 using xda app-developers app
nolethemole said:
Do you have Google voice installed? If so make sure that the sms feature is disabled. Or just remove google voice. For more help visit the source.
(Source: http://forum.xda-developers.com/showthread.php?t=2561308 )
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I don't, but I think I may have found out what the problem is anyway.
If I go in and check my SMSC, it comes up as +19037029920. The wiki tells me it should be +316540951000. I tried changing it, but the changes don't stick, something keeps changing it back to +19037029920.
TxdoHawk said:
I don't, but I think I may have found out what the problem is anyway.
If I go in and check my SMSC, it comes up as +19037029920. The wiki tells me it should be +316540951000. I tried changing it, but the changes don't stick, something keeps changing it back to +19037029920.
Click to expand...
Click to collapse
So you did the *#*#4636#*#* method?
nolethemole said:
So you did the *#*#4636#*#* method?
Click to expand...
Click to collapse
Correct.
I'm having the exact same problem. It started at the same time and has the same symptoms. I can receive texts, but not send texts. If I toggle airplane mode, I can send a single text. I've also tried a factory reset. I attempted to change the SMSC, but it reverted on me also. I was running KitKang (Fitsnugly's) nightly from Jan 24, 2014 when the issue happened. I upgraded to the Feb 19, 2014 nightly, which didn't help.
I've been working with VZW support and they want to replace the device and SIM (though I'm obviously going to try just the SIM before handing back an MDK device). I was hoping someone here would find a fix before the replacement arrives on Monday.
That was going to be my next suggestion is to get a new SIM card
Sent from my SCH-I545 using xda app-developers app
The SIM card replacement made sense when I thought I was alone in the issue. Now, when there are at least two of us who had the problem starting around the same time......
For what it's worth, Googling that SMSC gives me Github results for a piece of code that seems to change the SMSC of a device to that code as a test of some sort. Perhaps something like this unintentionally snuck into codebases?
Except it wouldn't explain why on Feb 19th, my Jan 24th build randomly did this. It had been working fine since then. I'm holding out hope that it's just a fried SIM card, but our timing is rather suspicious.
Cilraaz said:
Except it wouldn't explain why on Feb 19th, my Jan 24th build randomly did this. It had been working fine since then. I'm holding out hope that it's just a fried SIM card, but our timing is rather suspicious.
Click to expand...
Click to collapse
Similarly I find this strange. I hadn't changed or flashed a build in awhile and then poof, I suddenly started having this issue.
Now that I have ten posts, I posted in the CM KitKat nightly thread with a link here, hopefully a dev will figure this out.
I convinced my wife to let me try her SIM card in my phone, so hopefully it doesn't blow hers up and makes mine work. I'll come back when I'm done testing with the results.
Edit: Texting did not work using her SIM card. I guess it's time to try backing up and reverting to stock.
Edit2: Reverting to bone stock MDK worked. My texts flow freely now. I guess I'll try reloading CM.
Edit3: Flashed back to KitKang 2/19 nightly and the issue came back.
Edit4: Flashed back to KitKang 1/24 (which was working for me until 2/19) and the issue still exists. I'm at a loss.
Cilraaz said:
I convinced my wife to let me try her SIM card in my phone, so hopefully it doesn't blow hers up and makes mine work. I'll come back when I'm done testing with the results.
Edit: Texting did not work using her SIM card. I guess it's time to try backing up and reverting to stock.
Edit2: Reverting to bone stock MDK worked. My texts flow freely now. I guess I'll try reloading CM.
Edit3: Flashed back to KitKang 2/19 nightly and the issue came back.
Edit4: Flashed back to KitKang 1/24 (which was working for me until 2/19) and the issue still exists. I'm at a loss.
Click to expand...
Click to collapse
Thank you for testing. At least we know now that this is definitely code and not some weird SIM card thing.
TxdoHawk said:
Thank you for testing. At least we know now that this is definitely code and not some weird SIM card thing.
Click to expand...
Click to collapse
I just don't understand why my 1/24 nightly worked for 3 and a half weeks and suddenly stopped working.
I tried today's nightly of the official CM branch. It still had problems.
I've noticed some issues popping up since the builds have been unified.
Sent From My Verizon S4
I'm going to try clean flashing my old 1/24 build. When I tried it earlier, I flashed the 1/24 build over the 2/19 build, so maybe something was left behind? I'm grasping at straws, but I really want to be back on CM. I almost forgot how much I hate stock TouchWiz.
Edit: As expected, no dice.
And after all of 12 hours using stock MDK, I'm going back to the SMS-broken CM11 builds. Routing SMS via Voice+ and Hangouts is less of a pain than using a stock TouchWiz ROM.
So I recently flashed OctOS on my LG-LS990 and I am having this very annoying thing happening where I keep getting notifications that I have 1 voice mail when there aren't any. I've gone into the phone app and cleared cache, which makes the notification go away but then it comes back within a few minutes. This seems to happen quite frequently when I am at work and the signal is spotty. I've also called myself from a different number, left a vm, and then checked it from my G3 and deleted it and the icon doesn't clear. Also rebooted the phone numerous times, but it still comes back.
I was using youmail after I flashed the ROM, but have deleted it hoping it would resolve this issue. Which it has not.....
I was using Resurrection Remix ROM prior to this and initially had the same issue, but it cleared up when I did what I listed above. Anyone out there have any other ideas for how to fix this problem?
I have had the same issue and have asked but no answers yes. It is not a huge issue but really annoying. I have flashed Resurrection and OctOS and never could get it to stop showing up. I would get the VM notification EVERY time I got off of a phone call.
79 views and still no solutions
Go back to stock. Fix it. Then you might need to reflash CM instead of restore.
That's probably your best option
I have gone back to Stock several times using the Flash tool. When I do I have no more Phantom VM's. Root and flash a stockish ROM and still no phantom VM. But Everytime I flash any CM based ROM and get off of a phone call it comes back. after EVERY call. Aggravating more than anything.
engine95 said:
Go back to stock. Fix it. Then you might need to reflash CM instead of restore.
That's probably your best option
Click to expand...
Click to collapse
reedsammy7 said:
I have gone back to Stock several times using the Flash tool. When I do I have no more Phantom VM's. Root and flash a stockish ROM and still no phantom VM. But Everytime I flash any CM based ROM and get off of a phone call it comes back. after EVERY call. Aggravating more than anything.
Click to expand...
Click to collapse
Same here. May look at trying a different ROM. Such an annoying issue.....
Maybe try to just hide the notification. That is what I did. This is an old issue with sprint. If you really want to get rid of it, you have to find an old flip phone or something before android. Activate it and then go and clean out old voicemail's. I have been dealing with it since HTC EVO days. I have never gone back and done the real fix. If you really searched google there is info on this annoying issue.
Hey folks. So I finally took the leap to root and flash a custom rom (Lineage 16.0). I started on VS996 and had to cross-flash to US998 with the Frankenstein method. From there, I installed TWRP and rooted. Upgraded to US99820h before jumping to Lineage and even ran with it for a bit. Everything was going very well. I got through the set up, logged in to Google and started getting things synced, but soon discovered that my cellular abilities are dead. I have no ability to send or receive calls or texts from within the rom, but have a signal and curiously even internet over mobile data. The real problem is that it's not just limited to Lineage.
I reflashed the stock image and tried a new version of Lineage first. Same issue. Then I tried AOSiP. No luck. Here, the research I was doing was getting me worried that maybe my SIM died somewhere in this process. I tried out an old AT&T prepaid one, but it gave me no service whatsoever, not even the normal bars I had with the other SIM. I decided to go back to US99820h to see if I could still get texts on stock firmware. I could! It was good to feel connected and catch up on my texts from the past day. But this is far from over.
I did more research online, looking into ways to check on my APN settings. Compared to various sources online, they all seem good. I tried to add another APN, but have had no luck with that. I tried Havok out too. I really don't know what else I can do. Am I just doomed to live in the stone ages of Android 8? I can't really afford to give up telephony. I know there are other people here that came from VS996 too and seem to be running well. Or at least I think so. Is there something else that I can try? Any fixes or convoluted steps that I can take to get past this?
Any help, ideas, support, encouragement, or points in a good direction would be deeply appreciated.
This is a common issue. There is currently a small group trying to figure out how to get Sprint/Verizon services to work without any issue on AOSP/custom ROMs. I'm anticipating a release sometime as well, but it's been quite a while.
Until then, if you have a copy of Tasker installed, you can run a custom script to make a phone call to voicemail upon boot to "activate" service, then end the task 7-8 seconds in. However if your phone dozes then you may lose push notifications until you open your phone or messaging apps again.
TheCoryGuy said:
This is a common issue. There is currently a small group trying to figure out how to get Sprint/Verizon services to work without any issue on AOSP/custom ROMs. I'm anticipating a release sometime as well, but it's been quite a while.
Until then, if you have a copy of Tasker installed, you can run a custom script to make a phone call to voicemail upon boot to "activate" service, then end the task 7-8 seconds in. However if your phone dozes then you may lose push notifications until you open your phone or messaging apps again.
Click to expand...
Click to collapse
Hey, thanks for the idea! I've not had time to try that until this weekend, but it seems that it's not going to be an option. Unfortunately every time I try to make a call, my phone freezes and I have to reboot. I don't know what to do from here.
UPDATE: Flashed the newest version of Lineage (the 06/10 build) and the voicemail thing works! We're up and running for now.