Related
Hi all,
Looking for a bit of help/advice.
On occasions, probably between 1-3 times a day, when I try to make a call on the Hero, the call appears to look like it is dialing out but it just sits there saying 'dialing' but never connects to the destination which can be any UK number / Orange 150 etc. Either rebooting the phone or leaving it for 10 mins or so fixes the problem, but it does become annoying!
At the same time as this happening, when I try to send an SMS, I get the error 'SMS not able to send' in the notification bar. Again, I have to keep trying and it sorts itself out.
A final problem and I am not sure if it is related or not is I have had numerous people try calling me at various times, my phone doesn't ring or display a missed call, nor do I get a missed call SMS but the person who tried calling me said the line was actually ringing first and then went through to voicemail. I have witnessed this myself by calling my phone, getting a ringing line but the phone doesn't respond?
Any ideas of help would be appreciated. This problem has existed on Modaco Roms 2.2, 2.8 and 3.0 - I'm on Orange UK.
Thanks,
Nick
I have the same problem with the Orange Poland. When I logged on to the 3G sometimes you can not call or send SMS. When I switch to the 2G network problem disappears.
Yeah, it is strange, I have done that too, turn off the 3G to 2G and back to 3G which sometimes cures it, but not all the time.
I've tried various things, made sure the apps aren't closed with Taskkiller or anything like that. There is no specific time or occasion it happens, it just does now and again.
Well I have tried everything. I recieved all the settings from my operator , changed over 10 ROMs and gone back to the original too, i tried what you said to turn 3G off , i reset to factory , i unrooted.....Nothing works for me. I just get "Unable to send". I also tried 4 SIMs from different operators !!!
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
I've had the Galaxy S2 for about 2 months now without any problems.
As of last Friday, I can't receive incoming calls. People who try to call me hear one beep and then they get my voicemail.
Outgoing calls work just fine, as does SMS (incoming and outgoing).
I've put my T-Mobile SIM in another phone and then it is able to receive a call. Another SIM in my phone -> same problem: no incoming calls.
So I figured it must be the phone.
Customer support has started an investigation but that can take up to 1 week, so I thought let's ask XDA.
Can it be a simple setting that I've accidentally changed? Pretty often when I take my phone from my pocket, the screen is unlocked so that could be a cause.
If anyone has a clue or an identical situation, please let me know.
Zjoske said:
I've had the Galaxy S2 for about 2 months now without any problems.
As of last Friday, I can't receive incoming calls. People who try to call me hear one beep and then they get my voicemail.
Outgoing calls work just fine, as does SMS (incoming and outgoing).
I've put my T-Mobile SIM in another phone and then it is able to receive a call. Another SIM in my phone -> same problem: no incoming calls.
So I figured it must be the phone.
Customer support has started an investigation but that can take up to 1 week, so I thought let's ask XDA.
Can it be a simple setting that I've accidentally changed? Pretty often when I take my phone from my pocket, the screen is unlocked so that could be a cause.
If anyone has a clue or an identical situation, please let me know.
Click to expand...
Click to collapse
Does your phone ring when a call comes in and also does it go straight through to your voicemail?
daleski75 said:
Does your phone ring when a call comes in and also does it go straight through to your voicemail?
Click to expand...
Click to collapse
Straight to voicemail. But I've figured it out after 3 days
There's an option to automatically block all incoming calls in the settings. Must have accidentally been activated when the phone was in my pocket.
daleski75 said:
Does your phone ring when a call comes in and also does it go straight through to your voicemail?
Click to expand...
Click to collapse
In my case, the phone does not ring when I get a call at all. I have searched hi and low and I cant find a solution. I have rebooted, i have reflashed, I have changed my ringtone and nothing seems to work, please help!!
Hello my girlfriends SGS 2 has almost the same problem it cannot receive calls sometimes even though she can call everyone. The problem seems to fix by itself sometimes and it appears random.
I read that there was a problem with the samsung galaxy s when using 2G/EDGE connection with data activated and the problem was that the user could not receive calls randomly.
Can you confirm that you are using 2G/EDGE connection and Data activated? I am also trying to find the cause of this problem...
Hope my research helps good luck and waiting for your reply. (http://www.samsunggalaxysforum.com/...eive-incoming-calls-and-sms-while-using-edge/)
Later EDIT ---
She also has a vodafone provider but i have the same provider and never had this issue. Also no call filtering is done.
Make sure Call Forwarding is Disabled under Settings- Call- Call forwarding. And also try to delete the Voicemail number if you had set any.
Regards.
it's nothing Call Forwarding is Disabled related it is because of EDGE connection you can't have a sync or internet connection and while "dialing" data receive calls if you want to call anyone the network prioritizes and let's you dial whoever you want but it is not the same thing for incoming calls
^ Went over my head !
had the same problem in a bad 3g/data coverage area. solution was simply to turn data off and the calls started to come through.
turned data back on and now working ok.
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.
I haven been noticing that I been missing a lot of calls and getting delayed text messages once in a while I am currently running on the t-mobile network here in the US. I have a one plus 6t as well and I tested it and I receive my calls with no one mention that my phone has went to voicemail. I have even performed a hard rest to see if maybe it was an app or a setting and still continues. Anyone else experiencing the same thing? Call log shows no missed calls and asked several people to text me with the time they sent out the text and it's delayed at times for over 30 minutes thanks in advance
I've had an issue similar, no one could call me until I call them first, Just went straight to voicemail everytime someone tried to call me.. I think it has something to do with the Wi-Fi switch because I turned off the Wi-Fi and turned it back on and it corrected itself. I could still receive msgs but where delayed until then.
Crock1989 said:
I haven been noticing that I been missing a lot of calls and getting delayed text messages once in a while I am currently running on the t-mobile network here in the US. I have a one plus 6t as well and I tested it and I receive my calls with no one mention that my phone has went to voicemail. I have even performed a hard rest to see if maybe it was an app or a setting and still continues. Anyone else experiencing the same thing? Call log shows no missed calls and asked several people to text me with the time they sent out the text and it's delayed at times for over 30 minutes thanks in advance
Click to expand...
Click to collapse
Hi mate,
I had similar issues (at least with delayed text's) when locked. It was a battery saving issue, just make the Messages always run without power-saving option enabled.
Had issues with calls when Call over WiFi was enabled (enabled by default), disabled it and now works flawless (even with VoLTE).
Yea, been having this issue since I replaced my S9+ with the Mate 20 Pro.
My MintMobile SIM registers as T-mobile on the Mate 20 Pro. Most of the calls I don't receive and my wife says it goes to voice mail after first ring.
Where in the settings I can make adjustments to help eliminate this issue? Thanks!
Sent from my LYA-L09 using Tapatalk
bhagiratha said:
Yea, been having this issue since I replaced my S9+ with the Mate 20 Pro.
My MintMobile SIM registers as T-mobile on the Mate 20 Pro. Most of the calls I don't receive and my wife says it goes to voice mail after first ring.
Where in the settings I can make adjustments to help eliminate this issue? Thanks!
Click to expand...
Click to collapse
I'm having the same issue on MintSim in the US. Messages seem fine but sometimes calls seem to go straight to voicemail. There is no calls over wifi setting on my phone as far as I can tell (and no volte) so I would be interested if there is a fix for this as well. I never had the issue with my P20 Pro but it's happened several times with the Mate 20 Pro.
I'm tempted to manually input the MintSim APN settings but since the signal is very strong with the default T-Mobile settings I'm not sure how that could help.
I'm using the MintMobile Ultra APN settings. If I default to the T mobile settings, mms don't work.
jhs39 said:
I'm having the same issue on MintSim in the US. Messages seem fine but sometimes calls seem to go straight to voicemail. There is no calls over wifi setting on my phone as far as I can tell (and no volte) so I would be interested if there is a fix for this as well. I never had the issue with my P20 Pro but it's happened several times with the Mate 20 Pro.
I'm tempted to manually input the MintSim APN settings but since the signal is very strong with the default T-Mobile settings I'm not sure how that could help.
Click to expand...
Click to collapse
Sent from my LYA-L09 using Tapatalk
This only happens to T-Mobile and most likely related to WIFI calling, incoming calls goes to voicemail right away for me sometimes (both Note 8 and Mate 20 pro), but my wife on AT&T never had this issue
bhagiratha said:
I'm using the MintMobile Ultra APN settings. If I default to the T mobile settings, mms don't work.
Click to expand...
Click to collapse
Strange. With the default T-Mobile settings mms works for me and my signal app shows a stronger signal than with the Ultra settings.
Which signal app are you referring to? For me, I usually have to turn wifi off for mms to come in or sent out. It doesn't work when the wifi is On, with either the T-mobile or Ultra APNs.
jhs39 said:
Strange. With the default T-Mobile settings mms works for me and my signal app shows a stronger signal than with the Ultra settings.
Click to expand...
Click to collapse
Sent from my LYA-L09 using Tapatalk
bhagiratha said:
Which signal app are you referring to? For me, I usually have to turn wifi off for mms to come in or sent out. It doesn't work when the wifi is On, with either the T-mobile or Ultra APNs.
Click to expand...
Click to collapse
Network cell info.
Hi everyone,
Did anyone find a solution to the problem? I still have an issue with text messages and calls. I'm wondering if I should get a new phone....
Actually I just found one. I believe it has to do with Wi-Fi calling being on. Normally this option is supposed to be usable under settings and mobile networks, but since I'm using T-mobile I find the option completely off the phone or so it seems. I downloaded quick shortcut maker from the Google play store. Once opened I just typed in the top search bar Wi-Fi. From there you'll see 3 icons, a phone, settings, and wifi. Select the settings icon, scroll all the way down. Now you should see 2 entries that read Wi-Fi Calling, select the first one, the click on the middle button that says try. Wifi calling should be enabled, just switch it off and that should be it. Attached some screen shots of the process so it shouldn't be difficult. I was going crazy when people said they tried calling so many times but not one I receive or messages that are delayed for up to 30 minutes. I hope this solution helps anyone in this situation
Wi-Fi calling on my Mate 20 Pro is grayed out. So that cannot be the case for me.
Yea, my wife gets very upset when she calls me. Out of 10 calls, just one will come through. She will leave a voice mail, and hours later I will get the notification.
Sent from my LYA-L09 using Tapatalk
You selected the first one? When trying the second wifi calling option in shortcut maker the wifi calling was greyed out and the slider didn't work at all
Same issue
I've been fighting with my Mate 20 Pro since the day I got it. I'm on T Mobile. Some calls go to voicemail, some calls make it through. It's hit and miss. I haven't been able to find a common denominator. There's also a cellular data issue with the phone. When streaming video, the connection will suddenly drop out. The phone shows good signal, but it loses data. Turning the cellular data off and back on again fixes this issue. I think the data issue may still be related to the Visual Voicemail issue that T Mobile has with these phones. I was able to get Visual Voicemail to work (mostly) but I think the data is still affected by the Visual Voicemail issue , albeit to a much lesser extent than then it was before. I've been in contact with T Mobile and they have no solution to this issue. They did a sim card swap for me, but the issue persists.
Same sort of problem here. I'm on a KPN business contract, have been for many years. Never a call problem with the mate 9 and 10 but if people call me on the m20pro they don't hear the dial tone so they usually hang up thinking my phone is switched off or something. This really sucks!
I loved the m10pro especially but the m20pro is not my friend due to the calling issue and the really crap LG screen.
I've posted this issue on T-Mobiles Forum in hopes of getting them to take notice. Here is the link.
CloseCoder said:
Actually I just found one. I believe it has to do with Wi-Fi calling being on. Normally this option is supposed to be usable under settings and mobile networks, but since I'm using T-mobile I find the option completely off the phone or so it seems. I downloaded quick shortcut maker from the Google play store. Once opened I just typed in the top search bar Wi-Fi. From there you'll see 3 icons, a phone, settings, and wifi. Select the settings icon, scroll all the way down. Now you should see 2 entries that read Wi-Fi Calling, select the first one, the click on the middle button that says try. Wifi calling should be enabled, just switch it off and that should be it. Attached some screen shots of the process so it shouldn't be difficult. I was going crazy when people said they tried calling so many times but not one I receive or messages that are delayed for up to 30 minutes. I hope this solution helps anyone in this situation
Click to expand...
Click to collapse
Thanks! I will try that and see if it changes anything. I missed so many calls that don't even appear on my missing calls list. I hope it's gonna fix the phone because I really like it, other than you cannot receive phone call lol
CloseCoder said:
Actually I just found one. I believe it has to do with Wi-Fi calling being on. Normally this option is supposed to be usable under settings and mobile networks, but since I'm using T-mobile I find the option completely off the phone or so it seems. I downloaded quick shortcut maker from the Google play store. Once opened I just typed in the top search bar Wi-Fi. From there you'll see 3 icons, a phone, settings, and wifi. Select the settings icon, scroll all the way down. Now you should see 2 entries that read Wi-Fi Calling, select the first one, the click on the middle button that says try. Wifi calling should be enabled, just switch it off and that should be it. Attached some screen shots of the process so it shouldn't be difficult. I was going crazy when people said they tried calling so many times but not one I receive or messages that are delayed for up to 30 minutes. I hope this solution helps anyone in this situation
Click to expand...
Click to collapse
So far this seems to be working but 1 day without any missed calls is still too early to celebrate.. Thanks for sharing what you found--the missed calls were driving me crazy.
There's another option that I disabled in Hope of fixing the call issue. I attached some images of what to look for. The option was enabled by default so just click on the slider to disable