I am having a strange problem with CM11 or any CM11 based ROM. When I first install the ROM, voice mail works fine from the phone app (by dialing my number and entering password), and also with the AT&T messages app. After a short time (within the same day), the voice mail password from the phone keypad stops working, but the messages app still functions. The voicemail responds that it is an incorrect password. This only happens on the CM11 roms, and I have no issues with other ROMs. Has anyone else experienced this, or have any ideas how to troubleshoot this? I have tried a variety of things, such as varying the amount of my customizations, apps installed, etc, but the problem always comes back.
bnewport said:
I am having a strange problem with CM11 or any CM11 based ROM. When I first install the ROM, voice mail works fine from the phone app (by dialing my number and entering password), and also with the AT&T messages app. After a short time (within the same day), the voice mail password from the phone keypad stops working, but the messages app still functions. The voicemail responds that it is an incorrect password. This only happens on the CM11 roms, and I have no issues with other ROMs. Has anyone else experienced this, or have any ideas how to troubleshoot this? I have tried a variety of things, such as varying the amount of my customizations, apps installed, etc, but the problem always comes back.
Click to expand...
Click to collapse
i think some people had this issue, and they simply turned off dial pad tones...
Related
Hi,
I've developed the app Group to Voicemail for Android and have come across an interesting issue that only occurs on HTC phones:
When I programatically send a Contact to voicemail (using the SEND_TO_VOICEMAIL field for ContactsContract.Contacts), it works as expected. However, when I set that field back to '0' (to not send that Contact to voicemail anymore) the check box is unchecked for that Contact in the UI, but calls that come in still go to voicemail. The only way to actually put the change into effect is to reboot the phone (obviously not an acceptable solution for users)
Anyway, I've only seen this happen, and had reports from users that have HTC phones (Incredible and Evo). It works fine on the Motorola Droid as far as I can tell.
Based on some other tests, it seems to be directly related to SenseUI, and not the hardware itself.
Any ideas?
Thanks,
Matt
I've been using your app for a while and have had the issue you are talking about. Once I rooted my phone and used a vanilla ROM the app seems to work properly, both enabling and disabling groups to voicemail. This also leads me to think this is a Sense UI problem...
I installed Virtuous Unity today (latest release) on my Dinc2 and like it. Noticed one thing that I have not seen before and can't seem to find anyone else referencing this "bug". I use Google Voice for my voicemail. I also use Google Voice for my business number and the default cell number as personal, thus allowing me to use two phone numbers on the same phone...
Anyway, if I get a message, it shows in Google Voice as it should. If from GV I select the number and dial out using Google Voice, it works fine. However, if I choose to dial from my actual cell number, I get "The network is busy. Please try again later."
I can duplicate this behavior 100% of the time. If i direct dial the same number it works fine, seems to only affect returning calls from Google Voice.
Any ideas? I need this to work as it does in stock and other ROMs. Unsure if it is passing something unusual through the dialer or what, but I have never seen this before.
Thanks,
-myk
Looks like the issue may be with a +1 appended to the phone number. However the stock ROM doesn't fail with the +1 which leads me to believe there may be some sort of bug in the dialer app. I have noted one other user on the forum that has noted the same problem but haven't found any resolution yet. Would be glad to accept any input on the subject.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Some people reported google voice issues similar to this that was resolved by disabling 3rd party access under settings>call settings> 3rd party access. Worth a shot.
This option doesn't seem to exist. I notice that with this ROM, Google Voice produces and error in the phase where you set up the voicemail, I wonder if that has something to do with it..
-myk
I have exact same problem w/Virtuous Unity. I'm on version 2.39 but even the previous version had the same problem. I so much want them to fix this, because otherwise I may go to a different ROM.
My temporary fix is to use Google Voice to be able to dial +1 numbers from my phone list, but this is so inconvenient to me....Please please please developers fix +1 dialing problem
First, I have a d2tmo so I'm unfamiliar with the d2spr builds. I'm actually writing about my brother's and I haven't seen this issue mentioned in other threads. Basically the problem is twofold:
(1) He can access his phone's internal voice mail just fine and it registers his key presses perfectly. But when he tries to access his work voice mail, it seems as if it does not register his key presses at all (i.e. when he tries to press a key to delete or do anything, it just continues as if nothing had been pressed). This so far seems to only affect accessing his work voicemail remotely. I confirmed it is working on my d2tmo. Have there been key press issues with the dialer?
(2) Whenever he gets voice mails, two things happen. First, he gets an SMS saying "[Person] has sent you a voice SMS message, please dial [CA phone number] to listen." When he dials it, it gives him a busy signal. He also gets random texts from #9016 saying he's received a voice mail as well. From what I've read this sometimes is caused by visual voice mail issues on different phone models, but he has no visual voice mail installed. Is this a common issue with the GSIII?
Other than these two issues, he loves CM 10.1, so I'd like to help him out and solve them.
Any help is appreciated; thanks.
fingolfin14 said:
First, I have a d2tmo so I'm unfamiliar with the d2spr builds. I'm actually writing about my brother's and I haven't seen this issue mentioned in other threads. Basically the problem is twofold:
(1) He can access his phone's internal voice mail just fine and it registers his key presses perfectly. But when he tries to access his work voice mail, it seems as if it does not register his key presses at all (i.e. when he tries to press a key to delete or do anything, it just continues as if nothing had been pressed). This so far seems to only affect accessing his work voicemail remotely. I confirmed it is working on my d2tmo. Have there been key press issues with the dialer?
(2) Whenever he gets voice mails, two things happen. First, he gets an SMS saying "[Person] has sent you a voice SMS message, please dial [CA phone number] to listen." When he dials it, it gives him a busy signal. He also gets random texts from #9016 saying he's received a voice mail as well. From what I've read this sometimes is caused by visual voice mail issues on different phone models, but he has no visual voice mail installed. Is this a common issue with the GSIII?
Other than these two issues, he loves CM 10.1, so I'd like to help him out and solve them.
Any help is appreciated; thanks.
Click to expand...
Click to collapse
Well known problem.... It's how Sprint notifies the visual voicemail app to download the message.
You can download root call blocker and permanently block them, but you will never get another notification as to you having a message.
Option 2 is what I did. I installed Sprint Visual Voicemail, downloaded Red List from the marketplace. Turned off stock message notifications to hide the text, in the redlist app I blacklisted 9016 and turned on the notifications in it. This causes the notification to come from redlist, not the message app and redlist deletes the text messages so you don't have to deal with them. They pop through with just enough time for the VVM app to know to download it so you get your messages as well.
Theres a fix for the text from 9016, try googling "disabling texts from 9016 cm10" because it was an issue starting wih jellybean for most phones
Sent from my PG06100
VVM Download?
jdogg836 said:
Well known problem.... It's how Sprint notifies the visual voicemail app to download the message.
You can download root call blocker and permanently block them, but you will never get another notification as to you having a message.
Option 2 is what I did. I installed Sprint Visual Voicemail, downloaded Red List from the marketplace. Turned off stock message notifications to hide the text, in the redlist app I blacklisted 9016 and turned on the notifications in it. This causes the notification to come from redlist, not the message app and redlist deletes the text messages so you don't have to deal with them. They pop through with just enough time for the VVM app to know to download it so you get your messages as well.
Click to expand...
Click to collapse
Would anyone happen to have a link to a version of Sprint VVM that will run on a CM10.1 ROM? (CarbonRom at the moment.)
Spuddlethud said:
Would anyone happen to have a link to a version of Sprint VVM that will run on a CM10.1 ROM? (CarbonRom at the moment.)
Click to expand...
Click to collapse
Did you ever find the app?
rock99rock said:
Did you ever find the app?
Click to expand...
Click to collapse
If you google "Visual voicemail for CM10 xda" you'll find one that should work on CM10.1 as well (its posted somewhere here on xda)
CNexus said:
If you google "Visual voicemail for CM10 xda" you'll find one that should work on CM10.1 as well (its posted somewhere here on xda)
Click to expand...
Click to collapse
Yep, I think I got mine from the epic 4g touch thread or something, its just a voicemail apk.
Sent from my Nexus 7 using Tapatalk 2
I'm running the 10/1 nightly build of Cyanogenmod 10.2 on my Epic 4g touch without too many issues except I cannot get my voicemail to work no matter what I do.
I have new voicemails in my inbox but get nothing in my Sprint visual voicemail app and even no text from them. The only way I can know I have a voicemail is to call my own number - found this out the hard way that I had been missing a bunch of things.
I tried to install Google Voice because I heard this works well with cyanogenmod but even this doesn't work. During the install, when it asks to call that long number that starts with *2.... it calls for 3 seconds and then hangs up. The install continues without error after that, but again, new voicemails aren't sent to the app, so I have no way of knowing when I get them
I could really use the help here, thanks so much.
I looked through the forums and could not find anything on this that is recent. If I missed something I apologize for the re-post.
What I am experiencing is rather annoying. I start most of my phone calls in one of 3 ways. 1) from the contact/missed/recent screens in the dialer app, 2) from the contact info screen, as access by Textra (my preferred texting app), or 3) voice command.
Regardless of how I start the call, more times than not I am greeted with the call about to start (in other words the dialer opens and the number is present along with the contact info) then the dialer will close. Then I try again by either swiping from the contact list, or sending the voice command again and the call dials.
I am not rooted, on the latest 5.0.1.
Any ideas?
Me too, same problem on 5.0.1. Annoying~
I have the Note 4 Dev and it is rooted with MOROM 6.5 installed, and I sometimes have this happen as well.
I have been experiencing the same issues. I'm also on 5.0.1 not rooted. Running Nova Launcher.
Sent from my BN NookHD+ using Tapatalk
ssb13 said:
I looked through the forums and could not find anything on this that is recent. If I missed something I apologize for the re-post.
What I am experiencing is rather annoying. I start most of my phone calls in one of 3 ways. 1) from the contact/missed/recent screens in the dialer app, 2) from the contact info screen, as access by Textra (my preferred texting app), or 3) voice command.
Regardless of how I start the call, more times than not I am greeted with the call about to start (in other words the dialer opens and the number is present along with the contact info) then the dialer will close. Then I try again by either swiping from the contact list, or sending the voice command again and the call dials.
I am not rooted, on the latest 5.0.1.
Any ideas?
Click to expand...
Click to collapse
I have noticed this issue on MoROM custom ROM and a person did mention it on that thread so it seems like this is a lollipop bug for some or all :/