I bought a Samsung S20 and smart switched all my apps across from S10 with no issue bar WhatsApp. I can't get it to work at all.
There is not a lot of online support for the problem I am seeing and what I've tried has failed.
The only thing I suspect is that when I go SIM manager there is no number against it. However it still rings with the assigned number etc.
Any ideas?
Related
I've been flashing random ROMS lately for note 2, and i've been running beanstalk 4.4 without any issues for about one week. All of a sudden, i have no service. On lock screen it says, 'emergency calls only". I reverted back to the original 4.3 Bell rom, which also unrooted my phone, and still no luck. My IMEI is correct, and so is my serial number (however before reverting back to stock my IMEI was 'null' and serial number didn't match. As of now, my phone number, IMEI, serial number are all accurate, but I just can't get any service. I've went to my carrier, and they tried everything, including trying different sims etc....but can't get any service? My sim card is fine too. I didnt backup EFS, nor do i know if there is any problem with the EFS components.
However, i just remembered something. The day my phone stopped getting service, i vaguely remember clicking on the terminal emulator app just to see what it was all about. I must have clicked somewhere on there, because suddenly i had a notification that said i had 140 new text messages (all my messages came up as new messages in the notification bar). I would try to clear the notifications, but the text message icon in the notification bar would persistently keep popping up immediately, saying i had 140 new text messages. I didn't know what to do, so i went to application manager and disabled the terminal emulator app, and this stopped the new text message notifications.
Now, i don't know if this caused the issue of not getting any service, but its the only thing outside the norm that i did to my phone. If anyone has any ideas on possible solutions, I would really appreciate your help. Thanks.
As per the topic, I am on Three in the UK and the voicemail notification doesn't ever switch off, even after deleting voicemails (no saved voicemails either).
I was previously with EE/Orange with this phone (as well as in USA & Canada), and the notification disappeared moments after deleting messages with all other providers. It makes me think there is something different about the way Three deals with voicemail as opposed to a purely Android 5.0 fault as I upgraded prior to moving to Three.
If anyone has any advice I would appreciate. I have tried other solutions online (leaving myself a voicemail and waiting before hanging up after deleting it, ending the process of the 'phone' app, etc) to no avail.
Thanks BT
Any ideas dudes.... this is figuratively killing me!
Any thoughts yet???
Can only get rid of it temporarily by ending the phone app but returns on either getting a new voicemail and then won't disappear, or when restarting.
Best, BT
brokentelephone said:
Any thoughts yet???
Can only get rid of it temporarily by ending the phone app but returns on either getting a new voicemail and then won't disappear, or when restarting.
Best, BT
Click to expand...
Click to collapse
Any fixes???
I am still plagued by a permanent notification on my screen. 3 apparently doesn't send the typical 'ping' about voicemails and only sends SMS so they don't reset normally as do other networks. I can clear it manually, but as soon as I get a new voicemail, its there again until I clear manually again.
Problem permanently resolved -- I went to 3 and got a new SIM card and the problem is completely solved.
I see a lot of threads on this issue. I'm hoping since most of them are dated around 2012, maybe there is a fix for this recently.
I have ElectronTeam's dn4v2 rom on my t889. There are a few issues I'm having in the past couple weeks (since flashing) but the latest is a problem with texting.
It starts with the fact that I'm not receiving group messages in Samsung's SMS app. So, I don't really like Hangouts as an SMS/MMS app, but one good thing about it is that it receives group messages and displays them as such. However, when I try to send a message to a new contact/start a new thread, it gives me the option to send from my Google voice # or Carrier Number "Unknown". I'm assuming that means the recipient will not know the text is from me?
In one of the threads, I read that if my phone number is correctly listed in "About Device", I would be able to send and receive Group messages in Samsung's SMS app( a feature introduced after JB)
In About Device>MY Phone Number> Unknown.
In my contacts, the first contact listed is ME, and my phone number is correct.
I've gone into Contacts>Settings>Contacts>Contacts to display> Sim card and my number is there.
I put the sim card in my old phone running Cyanaogen, and went into call settings etc., and the phone # is listed.
So I believe that my sim card has my number. But for some reason it's not getting recognized. Perhaps this is a rom issue?
Anyone else have erratic results with this app? Using it on my s20+ with Tmo us, I can't send txt messages. The store replaced the sim card, still no luck. App works fine on my wife's A71 5g. Switched to the Google messages app and it seems to work fine. I'm a bit puzzled by this. The store tried to tell me that messaging wouldn't work with Wi-Fi calling enabled, but disabling it doesn't seem to be helping. No real problem using Google app, just seems strange.
Pauls57 said:
Anyone else have erratic results with this app? Using it on my s20+ with Tmo us, I can't send txt messages. The store replaced the sim card, still no luck. App works fine on my wife's A71 5g. Switched to the Google messages app and it seems to work fine. I'm a bit puzzled by this. The store tried to tell me that messaging wouldn't work with Wi-Fi calling enabled, but disabling it doesn't seem to be helping. No real problem using Google app, just seems strange.
Click to expand...
Click to collapse
I have the S20 dual SIM with both Google Fi (TMO Network) and AT&T. I actually switched from Google messages to Samsung messages and have no issues sending our receiving with either Network.
I have the 9810 model.
Thanks for the info. Must be something to do with the version I have or other software on my phone. My messages app is version 11. 1.65.17
Pauls57 said:
Anyone else have erratic results with this app? Using it on my s20+ with Tmo us, I can't send txt messages. The store replaced the sim card, still no luck. App works fine on my wife's A71 5g. Switched to the Google messages app and it seems to work fine. I'm a bit puzzled by this. The store tried to tell me that messaging wouldn't work with Wi-Fi calling enabled, but disabling it doesn't seem to be helping. No real problem using Google app, just seems strange.
Click to expand...
Click to collapse
I had the same issue before. Biggest pain in the butt. I tried changing sim cards too, asking tmobile to refresh my phone signal with no luck.
What worked for me was deactivating the chat features from the google messages app then waiting like 5 min, just to be safe. Then use my sim card on another phone and turn it on and wait like 5 minutes, for me the refreshing sim data prompt showed up twice. Text some people that use the advanced messages(rcs) with the stock app to make sure it works. Then switch the sim back to my phone and i was able to text the people i used to have issues with fine.
What i figured was the issue was that since you used google messages which used the google jibe servers for rcs, your phone number is still stuck in the servers. I did all that before this form was available to unlink your phone from the jibe servers. Give it a try too.
Dear Community,
I hope that this message finds you all well.
I have recently purchased a second-hand Samsung Galaxy S20 5G which runs on Android v13. I am living in the United States and LycaMobile is my provider.
Everything works well with one major exception:
I cannot send any text messages. (Receiving text messages works however.)
Whenever I try to send a text message, I immediately get the message "Free Msg: Unable to send message - Message Blocking is active." This happens with any of my 700+ contacts in the address book. On top of this, I have made sure that no contact has been accidentally blocked in the phone.
As sending text messages worked perfectly with LycaMobile and my previous Motoral phone and as it also works well when I insert another SIM card (e.g., my European provider), I assume that it has something to do with the settings of the text messages on the Samsung Galaxy S20.
I have found out that LycaMobile needs the following number entered in the Message Centre:
"Go to Lycamobile SMS settings and check, MCN (Message Centre Number). It should be +61469000111.
In SMS settings, if you see other number replace it with +61469000111 and reboot your smartphone handset."
My key problem though is that I can't access the SMS settings where I would be able to change any number in the Message Centre (as described here https://deviceguides.vodafone.co.uk/samsung/galaxy-s20-5g-android-10-0/messaging/set-up-your-phone-f...). I can't click on the field Text Messages (as displayed under Step 5!) because it does not exist on my Samsung Galaxy S20 5G ). I can only click on Multimedia Messages there.
If anybody had any idea what to do, I would be eternally gratefully. As it is currently, the phone is basically useless to me.
Many, many thanks in advance for your kind support!
Warmest regards
Eichelober