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.
Related
I'm having a problem that has me stumped.
YouTube
Earlier in the week, I noticed that I was unable to stream YouTube videos over mobile data. I could launch YouTube and it would bring up the top videos. I could search and it would get me results. I could not however get anything to actually play, when I choose a video it will just sit at the loading screen, and my bars will turn grey. I will not get a mobile data connection back until I back out of Youtube. I confirmed this issue with several different videos while in different parts of the state, so it isn't limited to a certain video or tower.
Google Talk
If I am at the main screen that shows who is online/offline, usually this will display properly. However as soon as I pick a name and go to send a message, my bars will turn grey and I will lose my data connection. It will not come back until I back out of Talk. Sometimes after this happens I can reopen talk and it will sit at the main screen for a while, get mobile data back, and display who is online and who is not. Most of the time, Talk will not work again until I force close it.
Edit: Talk will not disconnect until I actually send a message. The message makes it through most of the time, but then I lose mobile data. This results in Talk saying "Lost connection to Server. Messages will be sent when online."
I am on CM7 Nightly 20 with the stock CM7 kernel since the day Nightly 20 was released. Just to be safe, I did a full wipe in Fastboot erasing the following partitions before re-flashing: userdata, cache, webtop, system, boot.
I am unsure when this problem started. I know that YouTube worked last weeks, but when I think back, I can't remember the last time Google Talk worked while I was on mobile data. Note though, that while on Wifi everything works just fine.
I'm at wit's end here. I'm going to wipe the phone again and install stable Ba2tF and just Google Apps, and see what happens (after I flashed Nightly 20 earlier today I had the Market start spam reinstalling my apps before testing Google Talk - though I did get to test it and have it lose data after just a few apps were installed).
I'm on 30P for the radio, AT&T, Western Massachusetts, any help would be greatly appreciated!!!
I was going to post the same exact problem. The problem only appears over cellular. Over WiFi, everything works fine. Also, I just reflashed stock and it works. So it would seem to be a problem with CM7 and/or AT&T.
I'm going to get a good logcat of what's going on after I narrow it down a bit more... my current log is 1MB, which as about 2 minutes of info. I'm going to try to narrow it down to just the few seconds from when I hit "send" to when I get disconnected.
Hopefully at that point someone smarter than I can figure out what's going on.
DK
DeathKoil said:
I'm going to get a good logcat of what's going on after I narrow it down a bit more... my current log is 1MB, which as about 2 minutes of info. I'm going to try to narrow it down to just the few seconds from when I hit "send" to when I get disconnected.
Hopefully at that point someone smarter than I can figure out what's going on.
DK
Click to expand...
Click to collapse
Just thought I'd chime in and give some feedback. Tested this out on Weekly #2 both with wi-fi and regular data and everything was working as it should. I've been through a few different versions of CM7 and have not run into this.
Have you been using the same gtalk .zip each time? Maybe try re-downloading it along with your fresh install? Also, have you re-flashed your radio?
And here is a logcat capture. I force closed Talk, started the capture, launched talk, connected, pressed on my roommate's name, and lost my connection. The part that says "<SNIP>" is where my email address was.
I'm going to upload it here, then start to go over it myself.
DK
ghost_og said:
Have you been using the same gtalk .zip each time? Maybe try re-downloading it along with your fresh install? Also, have you re-flashed your radio?
Click to expand...
Click to collapse
Yeah, the GAPPS package ROM Manager lists as newest is still 20110828, which is also listed as newest on the Cyanogen Wiki. I never re-downloaded it, I've always used the same .zip everytime I've needed it... which is since Pre-Beta1.
I didn't flash my radio up to 36P when it came out since some people reported issues with it, and 30P had been working fine for me since June/July.
I am going to try to re-flash Google Apps now, this time without using the new version of talk that supports the front facing camera... since I never used the functionality anyway. I will report back in a few minutes.
DK
I tried reflashing both AT&T radios and both versions of Talk (w/ and w/o video chat).
For me, I get disconnected as soon as I open Talk. Happens every time. I froze Talk and I was disconnected when I got a Gmail notification. Maybe it was a coincidence but either way I was disconnected so the problem isn't limited to Talk. Maybe it's a problem with the Google Services Framework.
Here is what I think is a better logcat of what happens. This time, I setup CM7 to have long press back kill the currently active process, so that I could kill Talk right away.
I started the logcat from killing Talk and hitting the home button while it was restarted. I sent one message that said "Son" to my roommate, and lost my data connection. I then waited 20-30 seconds, killed Talk, it restarted, I got data back, I sent another message to my roommate that said "disconnect", and I lost my data again.
NOTE: This is with the Talk from the newest GAPPS (fresh download with ROM Manager), but not the one with the camera support (camera crap was cluttering the logcat anyway).
Anyone who is smarter than I able to see what's going on here?
DK
Same problem with CM7 Beta so I'm guessing there's some problem between CM7 and AT&T. I'm on AT&T in NYC.
I have a list of ROMs this does NOT happen on. I went back and restored to several points trying to figure out exactly where the problem started, and while I didn't find that, I do have a list that it does and does not happen to.
Talk Works on:
Prebeta2
Prebeta3
Prebeta4
Stopgap
Ba2tF
Weekly1
Nightly8 (likely it works on Nightlies 1-8, I just never made a backup after that and went right to 20 so I dont know exactly where the issue started with nightlies)
Talk does NOT work in:
Weekly3
Nightly20
So at some point between Nightly9 and Nightly20 (which includes the commits for Weekly3), something happened with Talk that is causing it to drop your data connection when you send message or refresh the friend list.
If any Dev happen to stumble upon this thread, I did take a logcat dump and linked it above as a txt file called "betterlog.txt" which clearly shows two disconnects while using Talk without having a lot of other "noise" in the logs from other things happening on the phone.
DK
Same problem, only I have this in Ba2tF. Odd thing is, I was running Ba2tf for some time, then all of a sudden this issue just appeared. I couldn't get it to clear, even after wiping data, caches, re-flashing etc...
Looks like this is nothing new. Check out CyanogenMod issue 3557.
---------- Post added at 02:52 AM ---------- Previous post was at 02:38 AM ----------
Same problem in Ba2tF. I was running Ba2tF for several weeks, then this problem just popped up. Couldn't get it to clear.
Looks like an old CyanogenMod issue. Issue #3557.
I don't know if it's AT&T that changed or CM7 but the problem's gone since I started using weekly #4.
I've been having this problem for quite a while now. Halfway through a call, it disconnects, and I can't end the call, I'll hit the home button, and have to roll down notification screen, and end it from there. After that if I try to make a call, it just gives the error "call not sent". And I can't receive calls too. Only way to get it to work again, is by rebooting.
I've tried diff roms, flash to stock, wipe, etc problem still there.
I'm now on superatmos 3.0 with galaxy RC4.1.
Its a long shot but try taking out sim card or try a different sim.
Sent from my GT-I9100 using xda premium
if you on i9100 first using cwm wipe everything including system partition also boot if you have that option.
than flash stock ROM via Odin
http://forum.xda-developers.com/showthread.php?t=1075278
flash latest 2.3.6, i say go for la2. it will update your modem aswell. now see if you have same issues.
atifsh said:
if you on i9100 first using cwm wipe everything including system partition also boot if you have that option.
than flash stock ROM via Odin
http://forum.xda-developers.com/showthread.php?t=1075278
flash latest 2.3.6, i say go for la2. it will update your modem aswell. now see if you have same issues.
Click to expand...
Click to collapse
I have done this already problem still persist.
fida khan said:
Its a long shot but try taking out sim card or try a different sim.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I'm using an iPhone sim with an adaptor in my s2, could this be the cause?
ad_ek said:
I'm using an iPhone sim with an adaptor in my s2, could this be the cause?
Click to expand...
Click to collapse
I'd try the sim change definitely. it's worth trying if only because sometimes its the obvious things that are the problem. Let us know how you get on
Sent from my GT-I9100 using xda premium
But why does it happen only sometimes when on a call? Data network never has issues.
Same trouble with my Samsung Galaxy R
ad_ek said:
I've been having this problem for quite a while now. Halfway through a call, it disconnects, and I can't end the call, I'll hit the home button, and have to roll down notification screen, and end it from there. After that if I try to make a call, it just gives the error "call not sent". And I can't receive calls too. Only way to get it to work again, is by rebooting.
I've tried diff roms, flash to stock, wipe, etc problem still there.
I'm now on superatmos 3.0 with galaxy RC4.1.
Click to expand...
Click to collapse
Hi ad_ek,
I am experiencing identical problems in my Samsung Galaxy R (GT I9103) which I bought 15 months ago.
I am experiencing this problem since last couple of weeks.
Please do update me if you get a fix on this.
Regards,
Pawas
[email protected]
Same issue in Sgs2GT9100G 4.1.2
I also face this issue of "call not sent" in my stock SGS2 Gt9100G 4.1.2, this happens infrequently, have changed SIMS, cleared cache, cleared all data before flashing but not luck, is is got to do something with memory full?
I have a similar issue for about 2 months on the SGS2. This is how it goes:
I first had CyanogenMod 10.1 with no problems at all until i installed total recall for the s2 (for legal purposes). Bad luck with that because after i installed it the phone didn't have any sound at all (music, calls, microphone, headset). I didn't have a backup so i had to reflash CM 10.1. Ok, for a while until i got reports that i don't receive phone calls, i was told that my phone was closed (even though it wasn't). Luckily i have a second phone. So, i restarted the phone, and it got back to normal. Next day, similar issue, and so on for a week until i decided to change the baseband. Did that, worked like a charm for a week and then it got back to not receiving phone calls. Decided to change to AOKP (06.15 - i later updated to 06.30 but had to downgrade to 06.15 again because android keyboard kept giving errors). No problems for a week, but finally the problem came back and persisted. Changed about 3 or 4 basebands with no luck. I sometimes check if i can send or receive calls with my other phone, and if i don't, i restart the phone and comes back to normal for a few hours or a day or two. Signal bars are full even when it doesn't work.
I got in huge trouble with this problem and i would really like a suggestion. Please help...
801
ad_ek said:
I've been having this problem for quite a while now. Halfway through a call, it disconnects, and I can't end the call, I'll hit the home button, and have to roll down notification screen, and end it from there. After that if I try to make a call, it just gives the error "call not sent". And I can't receive calls too. Only way to get it to work again, is by rebooting.
I've tried diff roms, flash to stock, wipe, etc problem still there.
I'm now on superatmos 3.0 with galaxy RC4.1.
Click to expand...
Click to collapse
ok.go to keypad,then call settings,then internet call settings.then select use internet calling,then selectonly for internet calls
Same issue here. Gotta change my SII, not buying a SAMSUNG phone any more.
Tried EVERYTHING and nothing works. I am pissed off. Camera also gives me problems...
EDIT: FINALLY WORKING, YAY!
After having wiped, rewiped, changed ROM, changed modem... Another ROM switch+EFS restore (altough my IMEI was correct) calls are working again.
razinoushu said:
ok.go to keypad,then call settings,then internet call settings.then select use internet calling,then selectonly for internet calls
Click to expand...
Click to collapse
This fixed the issue for me.
Thanks very much!
I'm having a similar issue. Each time I go to make a phone call, It gives me the CALL NOT SENT error on the first try. Then I try a second time and it goes through just fine. I've contacted TMO support and here is what they said after troubleshooting: "Alright. Upon checking here, I can see that we already exhausted all our basic troubleshooting on your phone, and I do apologize for the inconvenience. Please do contact out Technical Care at 1-800-937-8997 or 611 on your phone."
I'm wondering if any of you have a suggestion other than new sim card or factory reset. I'm going to definitely stop by a TMO store to ask them about the issue, but I figured I'd try here before going out there.
Here's a video to show you what happens: go to my youtube channel to view the call not sent error. My User account is DeSaaD37. This forum wont allow me to post the link to the video since I haven't posted ten posts yet. So stupid!
Solution
What seems to be happening is the WiFi calling bake in is struggling to activate properly against the chipset structure of Samsung. I watched error codes pop up when the phone first wakes up. Calling is not available right away. When Wifi calling is turned off completely this issue goes away. Not sure what needs to be done to fix the problem so you can leave this on.
-- I have done this now on several samsung phones and has worked on each one (all tmobile)
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
Alright.... I dont have enough posts to put this in the development thread. I took the omni rom ota update and like a few people my phone rebooted to the invalid software please take this phone to a verizon store..... I odined back to stock and eventually got things back to normal or so I thought. Now it seems that anytime I am on an aosp based rom my signal is borked. When I am on a touchwiz rom everything seems fine. It does seem to want to go to global under mobile networks and my singal strength seems way lower than normal also the connection seems much slower. So i odined back to stock again and backed up the apns went back to liquid and restored apns. That didn't work. I can receive and make calls no problem. I can receive sms and mms. If i go into mobile settings and change it from global to LTE then turn on and airplane mode it will send messages for maybe a minute then it cuts back out. I am assuming my next step is to get a new sim card. If anyone has any ideas I would appreciate some input. I have been searching this and other sites since the 24th when I took the ota and have had no luck. I have been on this site and fiddling with my androids since the original droid. I didn't think I was a total noob but this has me stumped.
I am on MDK and my IMEI seems fine I actually Just noticed my IMEISV says "00". So help please!
You're having problems with SMS?
Try going from TW to the GPE rom and see if if keeps working on that, then if it does go from that to whatever rom you want.
Oishikatta said:
You're having problems with SMS?
Try going from TW to the GPE rom and see if if keeps working on that, then if it does go from that to whatever rom you want.
Click to expand...
Click to collapse
never thought of the gpe rom. seems to have worked. thank you very much for the help.
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.