LG G3 cant use phone for dialing services - Android Q&A, Help & Troubleshooting

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!!!

Related

Why does it always say "Conditional call forwarding active" when I make any call?

Why does it always say "Conditional call forwarding active" when I make any call?
Hi there, basically I bought a new and sealed T-Mobile branded Samsung Galaxy SII phone from eBay and am using my 3 mobile sim in it.... I assume it wasn't originally locked when I bought it, as I went through the root and unlock method (ChainFire app), and the code was 00000000, and never at any point asked me to enter that code into the system, so hey, my 3 sim seems to work in it.... apart from the fact that for every call I make the message "Conditional call forwarding active" always crops up with a beep to go with it, then after a couple of seconds the call is made. It isn't a major problem as such I don't think, but hell it definitely isn't normal and is quite annoying after spending £400 on this otherwise amazing phone.
I have tried to fiddle with the settings but for some reason I cannot disable any of the call forwarding settings, some sort of error message crops up. I have phoned up the 3 network who I am with three times today and they asked me to enter a few # codes to sort the problem out, but I had no luck, and then they had me factory reset the phone using the option in the settings. I did that, and I still have this problem. I also get the message "Connection problem or invalid MMI" when entering most # codes, this seems to have happened after rooting, though I am not 100% sure if that is the case.
My phone is the Samsung Galaxy S II I900, just to confirm that.
I look forward to hearing from you guys
I am on Three and I get the same message although my S2 was purchased from O2 then rooted. I have not seen any other reports about this but the message has not bothered me.
I have the same message. Ave tried several hings without success, however since it really does nothing, I am starting to get use to it. But if someone knows how to solve it please let us know
voice mail
Hi guys i have this to but it only started when i activated my voicemail so i think its down to the voicemail
e.g if your on the phone and someone else calls they are placed forward to your voice mail ???
hope this helps
Hey there guys, thanks for the replies so far, glad to hear others are experiencing this annoying problem. I seem to have had this since rooting it, originally T-Mobile though I am 99% it was never "locked" to the network for some reason as I mentioned as I have never had to enter the 00000000 code, which the free ChainFire sim app gave me (seems like it means it is unlocked already???). The guys on the 3 helpline were giving me loads of codes which weren't of any help, and telling me about what options I could fiddle around with, but I had tried all of these to no avail.
Are people also getting the MMI message I mentioned in my original post, whenever they enter # codes in the dialer? It seems to me that both of these problems started at the same time (this error message and the forwarding issue - I am sure they are linked). It means, for example, I probably won't be able to set up a speed dial because of it, nor will I be able to use the "secret codes" as mentioned in the dedicated thread of the same name on this site.
Why is it a problem for some and not for the majority of people, we must have something in common which we have done with our phones which has caused this?
I really hope someone can sort this annoying problem out.
It's normal. "Call Forwarding Active" is displayed when all calls are forwarded. "Conditional Call Forwarding Active" shows when forward when busy, forward when unanswered, or forward when unreachable is selected. To make the message go away you'd have to disable the three forwarding options in their settings. The pre-populated number is always your carrier voicemail (read from the SIM) or Google Voice.
BarryH_GEG said:
It's normal. "Call Forwarding Active" is displayed when all calls are forwarded. "Conditional Call Forwarding Active" shows when forward when busy, forward when unanswered, or forward when unreachable is selected. To make the message go away you'd have to disable the three forwarding options in their settings. The pre-populated number is always your carrier voicemail (read from the SIM) or Google Voice.
Click to expand...
Click to collapse
Cheers for the reply Barry, yeah I expect it is normal but the thing is I cannot change these settings, my phone won't let me as an error comes up. I know it's not a major problem, just a bit annoying I can't get it to go away. I can't disable those three things, I tried a few times already.
Plus, I constantly get the MMI error message, which I mentioned before, seems a bit of a coincidence how these problems started the same time. I can't enter the majority of "#" codes into the dialer, it always says "USSD Running" or something along those lines and then produces the message like 2 seconds later.
Any ideas? Thanks so far for the advice
I have this problem but unlike all others I cannot make any calls on account of it. When I try to disable call forwarding I get an error msg saying it's not supported by the operator.
There HAS to be a way to fix this. I cannot make any calls or use 3G.
Try this
menu-call-additional setting-select network default...
It work with my sgs2.
On the Galaxy S2 if you go to: settings-call-call settings-call forwarding-voice call forwarding -- You will most likely see that for unanswered or unreachable calls it's not disabled because it forwards it to your voicemail, that's why it says conditional call forwarding is active. If you disable all options you won't get the message but then unanswered calls won't go to voicemail.Hope that helps.
Satish
dynamicbot said:
Hi there, basically I bought a new and sealed T-Mobile branded Samsung Galaxy SII phone from eBay and am using my 3 mobile sim in it.... I assume it wasn't originally locked when I bought it, as I went through the root and unlock method (ChainFire app), and the code was 00000000, and never at any point asked me to enter that code into the system, so hey, my 3 sim seems to work in it.... apart from the fact that for every call I make the message "Conditional call forwarding active" always crops up with a beep to go with it, then after a couple of seconds the call is made. It isn't a major problem as such I don't think, but hell it definitely isn't normal and is quite annoying after spending £400 on this otherwise amazing phone.
I have tried to fiddle with the settings but for some reason I cannot disable any of the call forwarding settings, some sort of error message crops up. I have phoned up the 3 network who I am with three times today and they asked me to enter a few # codes to sort the problem out, but I had no luck, and then they had me factory reset the phone using the option in the settings. I did that, and I still have this problem. I also get the message "Connection problem or invalid MMI" when entering most # codes, this seems to have happened after rooting, though I am not 100% sure if that is the case.
My phone is the Samsung Galaxy S II I900, just to confirm that.
I look forward to hearing from you guys
Click to expand...
Click to collapse
Its just simple, Just take out ur sim card put it will some other mobile and cancle all diverts....and then put it back to ur mobile again and then check out wat happned....
Thanks
---------- Post added at 01:41 PM ---------- Previous post was at 01:36 PM ----------
dynamicbot said:
Hi there, basically I bought a new and sealed T-Mobile branded Samsung Galaxy SII phone from eBay and am using my 3 mobile sim in it.... I assume it wasn't originally locked when I bought it, as I went through the root and unlock method (ChainFire app), and the code was 00000000, and never at any point asked me to enter that code into the system, so hey, my 3 sim seems to work in it.... apart from the fact that for every call I make the message "Conditional call forwarding active" always crops up with a beep to go with it, then after a couple of seconds the call is made. It isn't a major problem as such I don't think, but hell it definitely isn't normal and is quite annoying after spending £400 on this otherwise amazing phone.
I have tried to fiddle with the settings but for some reason I cannot disable any of the call forwarding settings, some sort of error message crops up. I have phoned up the 3 network who I am with three times today and they asked me to enter a few # codes to sort the problem out, but I had no luck, and then they had me factory reset the phone using the option in the settings. I did that, and I still have this problem. I also get the message "Connection problem or invalid MMI" when entering most # codes, this seems to have happened after rooting, though I am not 100% sure if that is the case.
My phone is the Samsung Galaxy S II I900, just to confirm that.
I look forward to hearing from you guys
Click to expand...
Click to collapse
Just simple take out your sim card and put in some other mobile and cancel all divert and then put it back to ur mobile and check out wat happened ....
s_rajkotia said:
Its just simple, Just take out ur sim card put it will some other mobile and cancle all diverts....and then put it back to ur mobile again and then check out wat happned....
Click to expand...
Click to collapse
you realise thats almost a year old? Check the dates on threads before you post
ADMIN EDIT: True, but it is a current issue for some people so it's still valid to answer the question.
Doesn't work
My phone drops every call, even with SIM cards from different countries and in all conditions. Thinking this call forwarding might have something to do with it, I tried to deactivate it, first through the settings -- no luck -- than by reformatting the phone. Nothing, cannot get rid of it because it says it is set by the 2 different phone companies I use.
I don't mind the message but when I call someone, I can hear that the call is being sent somewhere, there is a 1st ring, then it rings the other phone. Does this have to do with call forwarding? Can it be interrupting the phone signal and causing the call to drop ?
I have also removed both the Turkcell and Telefonica SIM cards, put them into another unlocked phone and tried to cancel but as soon as I put them back, the message returns and my calls drop.
Im also getting this error when I updated to 4.1.2 and used galaxy s2 sim unlock
Has nothing to do with call forwarding !!!
The Message worked on all AT&T cell phones, since i can remember,. i been using go phones since 06..... and they all had this message when right after the number was just dialed, right after pushing the green phone icon button to dial it , right after entering the number to be dialed on the keypad.
I have found this message on LG Cell Phone 500 CU series... and all my other phones as well...
IT is NOT a CALL FORWARDING ISSUE>.. because i had worked on that for awhile myself...
IT is a Carrier Issue I believe.
and it doesnt happen ever single time , just on certain days . not sure, why... but perhaps, call your carrier and ask them what type of phone they have your phone listed as.
Then tell them the model and make u have. that might change things... Cell phone carriers know how to mess with your phone and break it too...
so if ur having issues with messaging, call forwarding, it just may be the settings the carrier has you listed or down for.
blah.
anyways. yes it is annoying, i just got a new phone, samsung galaxy express. it is starting to happen too on this one. but had it for a few days and it never showed up till about 2 days later.
I thing it is perfectly normal for your device to display this message, I'm central america and mine also says the same thing anytime i make a call "Conditional Call Forwarding Active. However since I have a prepaid or pay as you go plan with my carrier and whenever I have no more credits to make calls i get the message "Calling Barring Enabled". I guess it has something to do with your carriers settings, it doesn't bother me at all though since I'm already used to it so hope that helps.
Enabling call forwarding for real and then disabling it seems to work
I got the same error also on every version of the stock rom (it used to appear occasionally, though) on my Samsung Galaxy S2 (i9100, without g), in that case going into forwarding settings was enough, because the mobile used to read the current configuration from the network and recognized that there was no forwarding active!
I moved to Cyanogen Mod 10.1.3 / Stable and going into forwarding settings was useless... He was updating with the data from the newtwork, all the forwarding options were disabled but the notification message was still there...
I decided to enable it for real by putting a friend number from the same carrier and then disabling it immediately after, and it solved my problem! Hope it helps!
PS: I'm not sure that enabling the call forwarding is free of charge, just double check with your carrier first!
dynamicbot said:
Hi there, basically I bought a new and sealed T-Mobile branded Samsung Galaxy SII phone from eBay and am using my 3 mobile sim in it.... I assume it wasn't originally locked when I bought it, as I went through the root and unlock method (ChainFire app), and the code was 00000000, and never at any point asked me to enter that code into the system, so hey, my 3 sim seems to work in it.... apart from the fact that for every call I make the message "Conditional call forwarding active" always crops up with a beep to go with it, then after a couple of seconds the call is made. It isn't a major problem as such I don't think, but hell it definitely isn't normal and is quite annoying after spending £400 on this otherwise amazing phone.
I have tried to fiddle with the settings but for some reason I cannot disable any of the call forwarding settings, some sort of error message crops up. I have phoned up the 3 network who I am with three times today and they asked me to enter a few # codes to sort the problem out, but I had no luck, and then they had me factory reset the phone using the option in the settings. I did that, and I still have this problem. I also get the message "Connection problem or invalid MMI" when entering most # codes, this seems to have happened after rooting, though I am not 100% sure if that is the case.
My phone is the Samsung Galaxy S II I900, just to confirm that.
I look forward to hearing from you guys
Click to expand...
Click to collapse
I had the problem. Just solved it. select any one sim. Select settings-call settings-call forwarding-make sure all the options listed therein are disabled. Do this selecting all your sims one by one. The problem will have solved.
anilcsimon said:
I had the problem. Just solved it. select any one sim. Select settings-call settings-call forwarding-make sure all the options listed therein are disabled. Do this selecting all your sims one by one. The problem will have solved.
Click to expand...
Click to collapse
I can't disable the last option (please check the pics)
Sent from my Micromax Canvas 4 A210
Hello,
I also got the similar problem I can't call anyone since 2 days whenever i try to call someone the call drops out and shows the pop up message "Conditional Call Forwarding Active".
I tried to disable call forwarding in call settings but i cant disable the fourth option " Forward Call When Unreachable "
When i try to disable it another pop up message shows up " Unable to deactivate call diverting when phone is Unreachable. Unsupported by operator. "
Please help it is really annoying i can't call anyone.
I use Samsung Galaxy Note 3 Neo

Samsung Dive lock phone questions

I've registered a samsung account and I'm really impressed with the way this remote thing works. On testing, it rang my phone successfully and also retrieved my call logs for the past week. On find my mobile, it's found my road or at least, the marker is close to my road.
My questions relate to the lock tab.
The message displayed says " This mobile is lost. Please keep it for a while and I will contact you. Thank you." How would I find out and contact where the holder of the phone is?
Assuming the phone is lost or stolen, and I remotely lock the phone, I would then cancel the SIM card with T-Mobile and receive a new one from them with my same number and put it in an old backup phone of mine. Where I type the mobile number to receive notification of SIM card change, what number do I then put in?
on another note...how do you add your phone number in samsung dive? i means it recognize the phone model but say no phone number....
I guess noone knows.

touch tone dialing. voicemail problem

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.

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.

Answer Phone with Voice Control

I have a new Verizon LG Stylo 2v. I would like to be able to answer calls using voice only and put it on speaker phone. There is an app called "Voice Answer Free" and it worked fine on my Samsung Note 3 but I am unable to get it to work on the new LG phone.
It requires me to go to Settings - Sounds and Notifications - Notification Access and place a check mark next to the app name. On the Samsung it was very easy to do. On the LG Stylo 2v there is no "Notification Access" on the list in the same directory. I called Verizon support and they acted like they had never heard of this setting and had me call LG. They also had no idea what I was talking about and asked me to call Android. They did not know anything about it and told me to call Verizon.
The Samsung is on android 5.0 Lollipop and the LG is on android 6.0 Marshmallow so this difference may be the problem.
I just need to have the ability for my aunt to be able to answer her phone while it is on her lap without touching it, voice only.
Any help would be much appreciated.

Categories

Resources