Database Develop

[Q] Problems with voicemail on Cyanogenmod

Voicemail problem is fixed, so please if you could, just skip to where it says "EDIT"
Ok so whenever I get a voicemail, it appears in the notifications bar, but when I click it, it dials the number to get voicemail service and then tells me my inbox is empty. This entire system is pretty damn stupid. Wouldn't it be easier, the way you'd normally do it on the phone, you just go to the voicemail app, and then proceed to listen to whatever voicemail you want to listen to? And for the past like 2 weeks, I've only had the same amount of voicemails (9) and it keeps bringing up the damn notification every few minutes. Can't change the settings on it to make it stop, and at the same time, I can't listen to the fcking messages it's telling me that I have received. Please can someone help me?
EDIT: I should also add that all day today, ADW Luncher and something called "ascore" keep force closing. Pretty annoying and I really can't do anyhting at all because when one isn't force closing, the other is. Wtf. And I've tried rebooting 3 times.

You can get the original Sprint Visual Voicemail app from this thread
http://forum.xda-developers.com/showthread.php?t=774172
Although I don't know why even when it dials your voicemail inbox, you don't hear your voicemails... that's very odd.
Also, if ADW Launcher is giving you problems you could try LauncherPro instead, which is quite similar and perfectly stable in my experience.

c00ller said:
You can get the original Sprint Visual Voicemail app from this thread
http://forum.xda-developers.com/showthread.php?t=774172
Although I don't know why even when it dials your voicemail inbox, you don't hear your voicemails... that's very odd.
Also, if ADW Launcher is giving you problems you could try LauncherPro instead, which is quite similar and perfectly stable in my experience.
Click to expand...
Click to collapse
Well thank you for the voicemail link, but I can't try that out until I fix the ADW Launcher problem. And when I said I can't do anything, I meant I literally cant do anything. Like, my screen is practically frozen. I was going to try downloading a new home launcher, but I can't do anyyythingg. Ahhh this is so frustrating..

I am having issues with voicemail too in cm6. Sprint app didn't work for me. Adw may be fixed by dalvik wipe and apk uid mismatch fix in recovery always fixed my fc issues.
Sent from my HERO200 using XDA App

skylinetun3r said:
I am having issues with voicemail too in cm6. Sprint app didn't work for me. Adw may be fixed by dalvik wipe and apk uid mismatch fix in recovery always fixed my fc issues.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
LOL English please sir

silverballer95 said:
LOL English please sir
Click to expand...
Click to collapse
in recovery under the "Advanced" option in the menu select "Wipe Davlik cache"
hit "yes, blah blah.."

sandix said:
in recovery under the "Advanced" option in the menu select "Wipe Davlik cache"
hit "yes, blah blah.."
Click to expand...
Click to collapse
Will I have to re-install all my apps again?

You will not have to reinstall with just a dalvik wipe. The 9016 message I found out is a provisioning error on sprints end. I had to call in to get it corrected.
Sent from my HERO200 using XDA App

You all are talking about different things here!
Sprint uses a SMS voicemail system. The stock HTC rom would receive the SMS message in the background and filter it from the messaging apps, download the voicemail message into visual voicemail and then notify you when the voicemail was in your inbox.
If you change to ANY asop ROM (not just CM6) your phone will not filter the SMS from Sprint which comes from number 9016. If you have installed Sprint VVM the best way to deal with this is to use Handecent and blacklist 9016 then you won't be bothered by it.
If you are not receiving your voicemail you are not properly provisioned and all you need to do is dial *38.
The worst problem is if you are cursed with the voicemail notification "New Voicemail Message Dial..." There is no fix for this. Sense based ROMs filter this, asop ROMS don't and there is no clear way to get rid of it.

Ok well I tried the dalvik wipe...4 times...none of them worked, at all. And I figured out that even other home launchers are force closing on my phone. I tried to use BetterHome and it started force closing repeatedly too. Please, someone has to know what to do, I'm really f*cking sick of not being able to use my phone. Nothing but problems with this PoS phone, ever since I got it...
Edit: Well, I decided to just wipe my phone and install CM6 AGAIN....hopefully it doesn't act up this time. I don't even know why it happened, I've had it for like a month now and it was working perfectly..

SMS Issue

I can send and receive texts from everyone but my wife.
Both of us have RUU'd to updated Sprint HK version.
However, I couldn't send our receive SMS from her before this.
We can't use Hangouts SMS, Sense SMS, or any other messaging app.
The conversations DO show up in Google Voice, but we never get notifications from any selected messaging app we choose.
The weird thing is, I can send her MMS fine on any messaging app.
Any ideas?

Disable the number through Google voice or try the ##72786#?

tjeeeeee said:
Disable the number through Google voice or try the ##72786#?
Click to expand...
Click to collapse
Thanks. What do I do with ##72786#? We use Voice for voicemail.

mcwups1 said:
Thanks. What do I do with ##72786#? We use Voice for voicemail.
Click to expand...
Click to collapse
Well as long as your on sense ##72786# does a reset to the profile and prl portions it's solved issues in the past for me and was just trying to explore all options
Of course you click reset after entering the code

tjeeeeee said:
Well as long as your on sense ##72786# does a reset to the profile and prl portions it's solved issues in the past for me and was just trying to explore all options
Of course you click reset after entering the code
Click to expand...
Click to collapse
You can do the same thing through "Activate this device" in the settings. I tried that with both phones.
MMS is working fine through Sense messaging app, but SMS doesn't work at all.

Alright.
I guess since I used Google Voice for Voicemail, it disabled the Voicemail app that comes with Sense.
Deleted Voice from account, and now Voicemail app and messaging work.
Thank you for the help. Not the first time Google Voice screwed something up for my phone.
But, if I switch to AOSP, I'll have to use Voice again, so will it screw up again?

Only one way to find out lol

tjeeeeee said:
Only one way to find out lol
Click to expand...
Click to collapse
Thanks again. I would have bashed my head against the wall sooner or later over this. No SMS app was working.

mcwups1 said:
Alright.
I guess since I used Google Voice for Voicemail, it disabled the Voicemail app that comes with Sense.
Deleted Voice from account, and now Voicemail app and messaging work.
Thank you for the help. Not the first time Google Voice screwed something up for my phone.
But, if I switch to AOSP, I'll have to use Voice again, so will it screw up again?
Click to expand...
Click to collapse
It's possible it messes up again, but don't think it will, but you will never know unless you try it

[Q] Voice Mail Notifications

I have not been receiving voicemail notifications on my Turbo. I don't want to have to use Visual Voice Mail. Does anyone have any ideas? Please help, thanks

Did you set it up? This was the first phone I've had in a while that I had to set everything up again and until I did, I wasn't getting them either obviously. Also, make sure that the box to receive notifications is turned on for the app under setting-apps-vm.

I'm having the same problem. Google Voice wasn't picking up for some reason so I switched to VZW VVM and I just flat out don't get a notification even with them enabled. I have to go in and check to see if I have any VMs after I miss a call.

Superman36NYY said:
I have not been receiving voicemail notifications on my Turbo. I don't want to have to use Visual Voice Mail. Does anyone have any ideas? Please help, thanks
Click to expand...
Click to collapse
I had the same problem. I added you mail app and have been using it.

6Binford said:
I had the same problem. I added you mail app and have been using it.
Click to expand...
Click to collapse
Thanks for the help, I've decided to give Google Voice a try. I get text displays of the messages as well as the audio files to my email

You need to log onto your verizon account on your computer and then switch the voicemail. Go to the free one and not the visual voicemail. Something like that. I just looked and the interface changed and I can't find where to do it now. It is a plan feature.

Can't make calls, phone app crashes

Already tried clearing cache and force stopping. Every time I try to open the app, it just closes right away. Any thoughts on the issue?

GiSS88 said:
Already tried clearing cache and force stopping. Every time I try to open the app, it just closes right away. Any thoughts on the issue?
Click to expand...
Click to collapse
Try going to Settings /apps press the settings icon and check to see if you have the phone app set as default

apascual89 said:
Try going to Settings /apps press the settings icon and check to see if you have the phone app set as default
Click to expand...
Click to collapse
It was. Weird thing happened, I apparently had a voicemail--once I listened to and deleted that, the app started opening again. Really strange.

Is it stock? If you flashed something, like a ROM or an app, it is probably that and you need to (clean?) re-flash the ROM. Happened to me before on another phone when I flashed, and a re-flash fixed it. NVM, seems you have it working now.

GiSS88 said:
It was. Weird thing happened, I apparently had a voicemail--once I listened to and deleted that, the app started opening again. Really strange.
Click to expand...
Click to collapse
I had the same issue seems like the phone app can't handle voicemail. I turned off visual voicemail to see if I can isolate the issue. Let's see what happens. BTW does anyone know if the source code of phone app is opensource or not?
EDIT: I think I know what the issue is, the voicemail I received was from a private number (VOIP). Looks like visual voicemail was unable to determine the caller number and died (I did not look into the logs but I am fairly certain about it).

installing tmobile visual voicemail and deleting my voicemails fixed my issue. hope this helps someone.
bond_ said:
I had the same issue seems like the phone app can't handle voicemail. I turned off visual voicemail to see if I can isolate the issue. Let's see what happens. BTW does anyone know if the source code of phone app is opensource or not?
EDIT: I think I know what the issue is, the voicemail I received was from a private number (VOIP). Looks like visual voicemail was unable to determine the caller number and died (I did not look into the logs but I am fairly certain about it).
Click to expand...
Click to collapse

nathanielwilliam said:
installing tmobile visual voicemail and deleting my voicemails fixed my issue. hope this helps someone.
Click to expand...
Click to collapse
Thanks I did a similar thing. I dialed my Voicemail from Truecaller and deleted them. So from what I have tested the default dialer app was not able to handle visual voicemail from Private/Unknown number. Looks like someone overlooked a null pointer error.

null/segv kind crash
bond_ said:
Thanks I did a similar thing. I dialed my Voicemail from Truecaller and deleted them. So from what I have tested the default dialer app was not able to handle visual voicemail from Private/Unknown number. Looks like someone overlooked a null pointer error.
Click to expand...
Click to collapse
I had the same issue. It turns out that I had a voicemail that was not deleted from an "unknown" number (t-mobile usa). The phone app was not able to handle it and crashed. I am assuming the phone number field was empty and whatever data that was there in its place from next field simply corrupted its memory or caused it to segv. I think this is just a bug in their phone app. In order to replicate the issue, just have someone block and send the voicemail to them and try opening the app, it crashes without any incident. Is there a way to see any exception thrown? or is that not on the consumer build?

ykandel1 said:
I had the same issue. It turns out that I had a voicemail that was not deleted from an "unknown" number (t-mobile usa). The phone app was not able to handle it and crashed. I am assuming the phone number field was empty and whatever data that was there in its place from next field simply corrupted its memory or caused it to segv. I think this is just a bug in their phone app. In order to replicate the issue, just have someone block and send the voicemail to them and try opening the app, it crashes without any incident. Is there a way to see any exception thrown? or is that not on the consumer build?
Click to expand...
Click to collapse
You can use the user feedback app installed on the latest stock rom
Open it and recreate your crash and submit report to oneplus
If possible they will rectify in the next update

text notification issues

All of a sudden I have 1 number in my phone that I do not get notifications from when they text me. My phone for not ring, vibrate, light up, nothing. This only happens with this one number, all other contacts work fine. I'm using the default messaging app and on the latest Google update. Has anyone has this issue. Is there something that maybe I clicked on that could have caused this.

FilthyFord said:
All of a sudden I have 1 number in my phone that I do not get notifications from when they text me. My phone for not ring, vibrate, light up, nothing. This only happens with this one number, all other contacts work fine. I'm using the default messaging app and on the latest Google update. Has anyone has this issue. Is there something that maybe I clicked on that could have caused this.
Click to expand...
Click to collapse
You haven't accidentally blocked that number by accident have you?
To check this do the following, go to the messaging app > click on the 3 dot menu > check to see if the number/contact is listed there.
If it is click on the contact/number and then click on unblock.
Hope this is of some help.

It doesn't sound like this is your issue, but carriers will have a separate block-list that works account-wide. For example, numbers blocked in the Google Fi app will be blocked for all phones covered by that account. I seem to remember my last carrier having something similar on their website.
Although, can you clarify something... does the SMS appear in your messaging app and there's no notification... or does nothing at all appear?

jljtgr said:
It doesn't sound like this is your issue, but carriers will have a separate block-list that works account-wide. For example, numbers blocked in the Google Fi app will be blocked for all phones covered by that account. I seem to remember my last carrier having something similar on their website.
Although, can you clarify something... does the SMS appear in your messaging app and there's no notification... or does nothing at all appear?
Click to expand...
Click to collapse
The message appears in the messaging app, I just don't get any notification. As far as I can see, it hasn't been blocked anywhere. It is my son's phone number so I know I wouldn't have done it purposely. I've thought about dirty flashing the FW again to see if that fixes it out just wait till the new one comes out next month

Keith W said:
You haven't accidentally blocked that number by accident have you?
To check this do the following, go to the messaging app > click on the 3 dot menu > check to see if the number/contact is listed there.
If it is click on the contact/number and then click on unblock.
Hope this is of some help.
Click to expand...
Click to collapse
I checked and the number is not blocked. Hopefully next months update will fix it when I flash it.

If you use Messages, look at the notification settings and make sure you haven't toggled a conversation name off. Doing so would match what you're seeing.

jljtgr said:
If you use Messages, look at the notification settings and make sure you haven't toggled a conversation name off. Doing so would match what you're seeing.
Click to expand...
Click to collapse
Ok thank you. I'll check that, but suddenly it is working again. I am leading toward it being a glitch in the FW. I'm gonna wait till the new one comes out and upgrade it and see if it happens again