touch tone dialing. voicemail problem - AT&T Samsung Galaxy Note I717

for some reason I cannot check my voicemail using my dial pad. Everytime I enter my password it does not recognize it on my cell phone. But if I check it from my house phone or from my wifes cell phone everything checks out. This happened a few roms ago and has been doing the same thing for the last 3 or 4 roms. Please help

I'm going to guess that you're doing this on speaker phone? If so and you're running a CM based ROM it's been a known and ongoing problem since mid April. Flash over to a Touch Wiz ROM or get a ROM released before the middle of April. Otherwise you can turn your volume down all the way and put in your password or not use the speaker phone until you get logged in.

Related

Can't make or receive calls

Having a really weird problem.
Every time I try to make a call, the call timer starts and gets to 5 seconds before saying call ended and I get a "beep" from the phone. No dial tone or anything. Then if I call my phone number it tells me that the call can't be completed.
I have pulled the battery and sim card. I even thought it might be related to the boot looping issue. So I was going to try and see what mode the phone was in. But I can't get the *#*#4636#*#* number to work. I dial it and nothing happens.
I did confirm that I could still connect to the mobile network and was still receiving data.
Also I might add I just did the ICS OTA update a couple days ago. After that I went through the process of unlocking the bootloader and rooting the phone. Haven't flashed a rom or anything. And the phone worked fine for a couple days, and boom now I can't make calls. I did uninstall updates and disable both the blockbuster and nfl mobile app.
Anyone have any possible advice?
Ok apparently Verizon is having problems in Columbia.
This thread can be deleted by the mods if necessary.
you can get into the 4636 hidden menu by using the HZutils app.

[Q] Possible baseband issue (Nexus 5)

Hello!
This issue just rared it ugly head early this afternoon. My Nexus 5 would not let me make any outbound calls. I could dial the number and the dialer would just sit there, no ringing and eventually it would time out and say "out of service area" which I clearly wasn't
I would reboot the device and that still wouldn't help. Here's the kicker! I could still send text messages and I still had data capabilities.
My device is a Nexus 5
Android 4.4.4
Build KTU84P
Baseband M8974A-2.0.50.1.16
The device is unlocked and rooted.
I was on the phone with my carrier and the tech people couldn't figure out what it was. I called LG to get a RA and send the phone in to be fixed/replaced. I decided to Google a bit deeper and found there is an issue that is possibly with the baseband drivers in 4.4.4. I've hear of people changing their baseband radio before I just don't know how or if this is going to work.
I did find a work around which doesn't make sense. I had to :
Place the device in 1x network mode
Turn off the device for about a minute
Turn it back on wait for it to completely boot up
Do a test call on 1x
Change the network mode back to LTE
Make the test call again.
This work unless you update the PRL or profile or you turn the device off or reboot it.
I don't know if it's worth me sending in the device to LG to be fixed/replaced or find out how to upgrade the baseband radio.
Ideas?
Hope you can help!
Regards,
Dave

AT&T Gear S - What's the dang deal with auto call forwarding?

I love my Gear S and the main reason I bought it is for the fact that it can auto call forward and connect remotely. Lately however the dang thing does not seem to work if at all.
What's the deal? I have my Note 3 connected via BT. Both devices are connected and working just fine, and all is good. If I leave the house 1/10 times the Gear S will work properly forwarding calls and being connected remotely. Otherwise, it just never works and gives me that dumb error on the watch to Try Again. It never works, so I reboot it. Again, 1/10 times it will work.
Today I decided to work through this and of course it's not working. It says that the phone is connected remotely but I am not getting any notifications. I can from the Gear S, I can send email from it, but texts and notifications go into limbo. WTF! I swear, it's a love / hate with Samsung and it's issues like this that make me hate them.
Now I've reset the Gear S and am in the process of restoring it in hopes that somehow this fixes it. If not, I'll blow it away again and remove the gear manager and start from scratch.......again!! I had to do this back in Feb due to the Gear S giving up taking a charge for some stupid reason.
Sorry for my frustration, but WTF is wrong here? Anyone have these issues? I'm on the edge of leaving Samsung for something else just because I"m getting tired of this crap.
I have the AT&T version too and was getting this issue. Go into the call settings on your phone to see if you're getting the NETWORK OR SIM CARD ERROR. If you see this, you need to reboot your phone and your Gear S.
I have a Note 4 on Lollipop, but what I do is:
Go to the Phone app
Tap the three dots on the top right
Tap settings
Tap Call
Tap More Settings
If you see the sim or network error here, the call forwarding to the Gear S will not work and you will have to reboot your phone and watch.
If you keep seeing that error, then call AT&T and have them reregister your device (phone) sim to the network.
That's what I did to fix mine. This might be just a Note 4 issue in my case but the steps might work for the Note 3 also.
It could also mean you have a bad AT&T signal where you are because the watch has to communicate with the phone before initiating the call forwarding.
Go to mobile carrier settings and set the phone to forward unanswered calls to your S's assigned phone #. This way if the software fails, the carrier's network will forward the call to your watch regardless.
mghtymse007 said:
Go to mobile carrier settings and set the phone to forward unanswered calls to your S's assigned phone #. This way if the software fails, the carrier's network will forward the call to your watch regardless.
Click to expand...
Click to collapse
Thanks. I actually do that through a nice widget if I know for sure I'm going to be out with watch only. Mainly so the inbound callers don't have to sit through a number of rings before their call comes to me.
That said, it's really a band aid as the darn auto forward should work. I'm going to check what was suggested above and see what I find. The problem is last week it said it was connected remotely but I wasn't getting any notifications. That coincided with no call forwarding, thus I think the problem is more than just forwarding.
I reset the watch, restored, etc. and it worked once. I'll know more this week. THank you again for the input. Any input if very much appreciated.
pdqgp said:
Thanks. I actually do that through a nice widget if I know for sure I'm going to be out with watch only. Mainly so the inbound callers don't have to sit through a number of rings before their call comes to me.
That said, it's really a band aid as the darn auto forward should work. I'm going to check what was suggested above and see what I find. The problem is last week it said it was connected remotely but I wasn't getting any notifications. That coincided with no call forwarding, thus I think the problem is more than just forwarding.
I reset the watch, restored, etc. and it worked once. I'll know more this week. THank you again for the input. Any input if very much appreciated.
Click to expand...
Click to collapse
Sorry to hear you have a&t. Connected remotely and call forwarding are two completely different things as you may know but regardless of the matter its not Samsungs fault. Your device showed that it was connected remotely therefore it was....the real issue is your wireless carriers crappy network not pushing your notifications plain and simple not your watch or your phone. Both are working just fine from what you've stated which leads to the fact that its your network connection. Only GSM networks are capable of auto call forwarding which as I stated is completely carrier network based. No offense but at&t sucks anymore and havent seen these issues with anyone but at&t customers. Its on at&ts end. Call and complain about your issue but unfortunately I doubt they will do crap which is why I left at&t 3 months ago. Hope you can get them to figure it out.
I was having the same problem. Used Gear Manager to turn off auto forwarding, rebooted phone, turned call forwarding back on and it solved the problem. Unfortunately you have to wait until you are back with your phone to resolve the issue.
pdqgp said:
I love my Gear S and the main reason I bought it is for the fact that it can auto call forward and connect remotely. Lately however the dang thing does not seem to work if at all.
What's the deal? I have my Note 3 connected via BT. Both devices are connected and working just fine, and all is good. If I leave the house 1/10 times the Gear S will work properly forwarding calls and being connected remotely. Otherwise, it just never works and gives me that dumb error on the watch to Try Again. It never works, so I reboot it. Again, 1/10 times it will work.
Today I decided to work through this and of course it's not working. It says that the phone is connected remotely but I am not getting any notifications. I can from the Gear S, I can send email from it, but texts and notifications go into limbo. WTF! I swear, it's a love / hate with Samsung and it's issues like this that make me hate them.
Now I've reset the Gear S and am in the process of restoring it in hopes that somehow this fixes it. If not, I'll blow it away again and remove the gear manager and start from scratch.......again!! I had to do this back in Feb due to the Gear S giving up taking a charge for some stupid reason.
Sorry for my frustration, but WTF is wrong here? Anyone have these issues? I'm on the edge of leaving Samsung for something else just because I"m getting tired of this crap.
Click to expand...
Click to collapse
The problem is lollipop if restore your phone to kitkat then setup call forwarding then upgrade to lollipop and you will not see sim or network error again
rickleasa said:
The problem is lollipop if restore your phone to kitkat then setup call forwarding then upgrade to lollipop and you will not see sim or network error again
Click to expand...
Click to collapse
I don't think it's lollipop. It's now been working fine since a Gear S reset. I just think Sammy needs to figure out the bugs where ever they are. Moot point once someone else comes out with a nicer styled one with a sim card as I'll likely go that route.
pdqgp said:
I don't think it's lollipop. It's now been working fine since a Gear S reset. I just think Sammy needs to figure out the bugs where ever they are. Moot point once someone else comes out with a nicer styled one with a sim card as I'll likely go that route.
Click to expand...
Click to collapse
ok glad to hear but that didn't work for me as when i went to call setting on my phone i still received the sim network error until i did the restore but glad it worked for you
djc-wi said:
I was having the same problem. Used Gear Manager to turn off auto forwarding, rebooted phone, turned call forwarding back on and it solved the problem. Unfortunately you have to wait until you are back with your phone to resolve the issue.
Click to expand...
Click to collapse
I finally figured out this only happens to me after I have Bluetooth paired to my car or a headset. Only happens every once in awhile. If I reenter my car and turn it on, as soon as Bluetooth reconnects it's back to working. The problem will come back if I don't reset my phone. Then all is fine for a few days. In my case obviously the bug is in gear S bluetooth not my phone or my car as the same thing at times will happen with a Bluetooth headset.
SaintCrispin said:
I have the AT&T version too and was getting this issue. Go into the call settings on your phone to see if you're getting the NETWORK OR SIM CARD ERROR. If you see this, you need to reboot your phone and your Gear S.
I have a Note 4 on Lollipop, but what I do is:
Go to the Phone app
Tap the three dots on the top right
Tap settings
Tap Call
Tap More Settings
If you see the sim or network error here, the call forwarding to the Gear S will not work and you will have to reboot your phone and watch.
If you keep seeing that error, then call AT&T and have them reregister your device (phone) sim to the network.
That's what I did to fix mine. This might be just a Note 4 issue in my case but the steps might work for the Note 3 also.
It could also mean you have a bad AT&T signal where you are because the watch has to communicate with the phone before initiating the call forwarding.
Click to expand...
Click to collapse
You're a doll. This was EXACTLY my issue, and I spent ages pouring through forum posts and even called AT&T. I saw your post, rebooted my devices together, and voila! <3 Best!
foulmouthedruffian said:
You're a doll. This was EXACTLY my issue, and I spent ages pouring through forum posts and even called AT&T. I saw your post, rebooted my devices together, and voila! <3 Best!
Click to expand...
Click to collapse
Hah I'm glad it's working for you now.

Problem after rooting and installing custom rom, phone won't ring on incoming calls

I have a rooted Verizon Note 2 that I had put the last N3BULA ROM on and used with an AT&T sim card. It has worked fine for a couple of years now. Wanted to update it so I have flashed just about every available updated ROM I can find to get either Lollipop or Marshmallow. Every ROM I have tried has the same problems. Everything seems to work with the AT&T APN settings except the Phone itself. When I place a call it does call out but once I'm finished it won't hang up. I have to shut the phone off to get it to hang up. Also, if I call the phone it will not ring and the call will eventually go to voicemail. Does anyone have any idea why this is happening and what I can do to fix it? I was going to try to put the N3BULA ROM back on it but can't find a good version that will work. I'd really like to get it going with a newer rom tho.
Thanks for any help.

LG G3 cant use phone for dialing services

well as thread title says LG G3 cant use phone for dialing services.
This problem has been there since I got the phone in May.
What happens is when I need to press my dial-pad to enter tones to access a service menu like press 1 to get that action completed it does not recognize it.
One thing about this phone is its a FreedomPop phone and I believe it somehow casing the problem using there phone app but there new to me as a provider as my last phone was a Galaxy S3 from boost mobile.
Let me post this now for comments and feedback TIA!
I found a way to get this working finally!!!

Categories

Resources