Hello everyone. I'm new here and someone recommended I join this forum. Having major issues with the phone. So here's the story.
Bought a brand new Pixel 6 from TMobile on Nov 8 2021. When initially setup, I backed up data from a Samsung S9 plus via my Google account. Took over 24 hours for all apps and contacts to transfer. Thought that was odd. For the first week I didn't know anything was wrong. Then people told me they send me texts and I realized I wasn't getting them. I tried texting numbers in order to myself and some where missing. Live in NYC area and 5g is very good in my area. Spent about 3 hours on phone with TMobile. They had me toggle off 5g and use LTE. Didn't fix the issue. Texts were delayed or missing. Only way to get them was airplane mode or restart the phone. Reset message cache and network settings refresh/reset. After about of week playing games with TMobile, they recommended swapping out the SIM card for a new one at the store. So I did that and texts were flying in. Phone was actually nice for a few days but then a new issue popped up. Incoming calls would ring but I had no way to answer. Screen was blank with no notifications other than the ringer. I could open the phone and it would go to the home screen but still no way to answer. Never got a missed call notification and the call log was frozen/blank. If I restarted the phone or waited a few minutes the call would sometimes show in the call log. Called TMobile. Tried resetting cache on stock call app, tried network settings reset but neither helped. They then recommended a full data reset and not to back up from my Google account from the S9 phone. Did a reset and started fresh. Problem still persisted. Called TMobile they only wanted to give a refurbished phone because I had it more than 20 days. That pissed me off and I battled their supervisors on the phone for probably 10 hours last weekend. Called Google and explained all of the above. They sent me a new phone. I set it up from scratch and got the same problems! Now I want to blame T-Mobiles network. Called them they said my line is clear of issues and blamed android 12. They told me Google has to update my phone and it could take 2 months! Got another new 5g SIM card and have the same issues. Finally today I called Google again and explained all the above. I'm told an update will be coming out tomorrow that may fix the issue. What gives? Can anyone verify any of this?
Sounds like you did all the right things. Maybe try disabling 5G for now if possible, see if this helps.
Does it happen in safe mode? Rule out 3rd party apps especially carrier. Try a network reset and have Tmobile reset it on their end.
Android 11 and 12 are a mess. Google bit off more Apple than they or the developers could chew
I'm still running Android 9 and 10 on my Samsung devices, neither will ever be upgraded past 10... lockdown.
Thanks for your reply. Disabling 5g didn't help. Tried it for a few days. Safe mode didn't help either. Network reset and TMobile reset didn't help. I did turn off adaptive connectivity per a 9 to 5 article. May have helped the text issue. Let you know tomorrow.
You're welcome.
Try disabling all power/data management.
Start digging through the default settings for everything. It's fun to do and you learn more about the device... you may even find a fix.
Yea, I tried messing around with everything. I even put a LTE SIM card in that I have and it seemed to work a little better. Tmobile, Google, and now I cant figure it out. Hoping tomorrow's update from Google fixes everything.
Related
I know it's been a pretty common issue for rooted EVO 3D users to get an error 16 while roaming, which requires them to call Sprint and go through some rigmarole to get the phone working again.
I seem to be having a different (although similar) issue. I have no issues making calls, or with data while I'm on the Sprint network. But now that I'm roaming off of a nearby Verizon tower out here in the middle of no-where, I'm having issues. I try to place a call, and immediately the phone sounds a disconnection beep and that's it. I also do not have data.
About 45 days ago up here I received a message about not being authenticated (the error 16), but I was told that they couldn't fix this without me bringing my phone into the store. I just reset the phone and did hands free activation again, and avoided the store. I haven't noticed any issues after that, and I do go in and out of roaming areas sometimes while in the city.
I just tried to do a chat with Sprint. I specifically said I had an error 16 and needed an HRL refresh (I lied). The rep had me power off my phone while she attempted to send it a signal. After this she had me dial *2 and my phone process crashed while I tried this. I also still couldn't call out. She tried having me power off again. Same problem. Next she told me to power off my phone and keep it off for 30 mins. If it wasn't fixed by then, she gave me a support number to call.
Anyway, not sure if the support number will help. Figured I'd just see if anyone has had a similar issue or experience. I found another thread mention resetting through ##786# and using your MSL to get into it. My EPST process seems to crash when I try this. ##DATA# doesn't crash though...hm.
I'm running the Synergy 3Dvo Rom (Nightly 344 I think?). Stock kernel.
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.
Hey all,
I purchased this phone off Amazon about 6 weeks ago and instantly feel in love with it. And this was right before they announced that Sony would be selling these phones in local retailers in the US.
I've noticed for the last few weeks now, however, that some texts are coming in multiple times. It can range from 3-7 times that I receive the same text, and you can imagine how annoying that'd be. Sometimes, when I send a text to someone, I'll receive a duplicate of the previous text I got from whoever last texted me. Sometimes, I won't receive a text until much later- up to hours later. To top it off, sometimes MMS or group texts won't come through without prompting me to download the text. It wasn't bad at first, as it would happen sparingly, but now it's constant.
I've tried many options, from
- switching and updating/downgrading texting apps (Hangouts, Messenger, Stock texting app)
- editing and switching APN settings
- clearing my phone's cache.
To give some context, I transferred over my data from my Moto X 2013 and moved everything to my SD card the next day after transferring everything. The phone is not rooted. I'm also on AT&T but haven't contacted them about the issues yet (I would rather avoid hours of basic troubleshooting, unless they can actually fix it).
I'd really like to not have to lose all my text messages, and I shouldn't have to. Has anyone else had a similar problem and managed to fix it? What other routes should I try? If factory reset is the only option, what's the best way to back up and restore all my data (contacts, photos, texts)?
travfran said:
Hey all,
I purchased this phone off Amazon about 6 weeks ago and instantly feel in love with it. And this was right before they announced that Sony would be selling these phones in local retailers in the US.
I've noticed for the last few weeks now, however, that some texts are coming in multiple times. It can range from 3-7 times that I receive the same text, and you can imagine how annoying that'd be. Sometimes, when I send a text to someone, I'll receive a duplicate of the previous text I got from whoever last texted me. Sometimes, I won't receive a text until much later- up to hours later. To top it off, sometimes MMS or group texts won't come through without prompting me to download the text. It wasn't bad at first, as it would happen sparingly, but now it's constant.
I've tried many options, from
- switching and updating/downgrading texting apps (Hangouts, Messenger, Stock texting app)
- editing and switching APN settings
- clearing my phone's cache.
To give some context, I transferred over my data from my Moto X 2013 and moved everything to my SD card the next day after transferring everything. The phone is not rooted. I'm also on AT&T but haven't contacted them about the issues yet (I would rather avoid hours of basic troubleshooting, unless they can actually fix it).
I'd really like to not have to lose all my text messages, and I shouldn't have to. Has anyone else had a similar problem and managed to fix it? What other routes should I try? If factory reset is the only option, what's the best way to back up and restore all my data (contacts, photos, texts)?
Click to expand...
Click to collapse
are you using the stock texting app? I had these issues when I tried to use a 3rd party messenger a very long time ago. other than that Ive not had this issue.
also maybe check out your system time, something might be up with your towers in the area. I use clocksync as cricket had issues a few months back and I fell in love with the app.
civicsr2cool said:
are you using the stock texting app? I had these issues when I tried to use a 3rd party messenger a very long time ago. other than that Ive not had this issue.
also maybe check out your system time, something might be up with your towers in the area. I use clocksync as cricket had issues a few months back and I fell in love with the app.
Click to expand...
Click to collapse
Thanks for the reply,
I use Hangouts as my default texting app. The week that I used the Stock Texting app, I still received duplicates and delayed texts, so I switched back to an interface that I enjoyed more. (Also, the Stock texting app is sometimes really slow when opening conversations)
My system time is on point, but I went ahead and turned off automatic sync for the time and dates.
What settings do you use for Clocksync, and did it fix any texting issues? I just now installed it.
Update to Marshmallow. See if that fixes the problem
travfran said:
Thanks for the reply,
I use Hangouts as my default texting app. The week that I used the Stock Texting app, I still received duplicates and delayed texts, so I switched back to an interface that I enjoyed more. (Also, the Stock texting app is sometimes really slow when opening conversations)
My system time is on point, but I went ahead and turned off automatic sync for the time and dates.
What settings do you use for Clocksync, and did it fix any texting issues? I just now installed it.
Click to expand...
Click to collapse
Come to think of it google talk is what I was using when I was having those issues haha. probably not related but its something to keep in mind.
i use 1 hour intervals only when awake. idk if you need to be rooted or not for it to work.
There may be a problem with your sim card. Had this a while ago on another phone. Got the sim card replaced and it was gone
A few days later and I have some updates:
1. Have yet to change out my sim card. I will be going to ATT tomorrow to see if that fixes the issue.
2. Marshmallow update is not yet available. However, if I read it right, won't it disable using an external sd card? I wouldn't want to be rid of that feature, it was a big selling point for me.
3. I switched to the stock text message app, and it seemed to work well. It stopped duplicated texts from happening, but some MMS texts don't come through to me at all, and if they do they appear much later. Some texts I receive don't come in until about at least an hour after the contact sent it. Sometimes even 7 hours. Not to mention, the app itself is terribly slow.
4. I tried to switch back to Hangouts for a day after downgrading the app and using the stock texting app, but still had the existing issues from before.
5. Clocksync hasn't done anything for me.
Double Post,
Update:
It appears that getting a new SIM card did the trick after all. Went to the store on Saturday, days ago, and the texts don't appear to be duplicating and they seem to be showing up on time. I'm even back on Hangouts again. Yay!
You just need the patience to deal with how busy the store may be.
If anything changes, I'll let y'all know.
Anyone able to get enhanced messaging to work yet? If you are using Messages (Google Messenger) it is listed under advanced but it never completes.
It worked great on my Note 4. I like the ability to text over wifi.
xPhrostx said:
Anyone able to get enhanced messaging to work yet? If you are using Messages (Google Messenger) it is listed under advanced but it never completes.
It worked great on my Note 4. I like the ability to text over wifi.
Click to expand...
Click to collapse
Yes, it's working for me on my Sprint Galaxy S8 +. I did have trouble were it wouldn't work right away, had to wait like 24-48 hours after I activated the phone on my line for the system to provision it or whatever. Just keep trying and eventually it should complete and go through.
I use Android Messaging because the Samsung app supposed to have RCS and play nice with Android messages but when Ive sent messages from the Samsung app it acts like I dont have RCS at all
Doesn't work
I have had my phone for a few weeks but it still doesn't work. Every time I try it, it tells me Excuse the wait... Messages will let you know when this step is complete but it never completes.
Strange I was able to enable it on my wifes S8+ but mine will not enable. Tried clearing cache and uninstall and reinstall. Anyone else had this issue?
I chatted with TEP and Sprint, they sent me a new sim card and that didn't resolve it. I factory reset the phone twice and that didn't resolve it. I called Sprint and Sprint said to call Samsung.
Here is the definitive answer from Samsung "It is being rolled out in batches and certain versions of the phone have not received that update."
xPhrostx said:
I chatted with TEP and Sprint, they sent me a new sim card and that didn't resolve it. I factory reset the phone twice and that didn't resolve it. I called Sprint and Sprint said to call Samsung.
Here is the definitive answer from Samsung "It is being rolled out in batches and certain versions of the phone have not received that update."
Click to expand...
Click to collapse
I wonder if taking the phone to a best buy that has a Samsung experience store if they can add it.
It will go thru after Day or 2 I had issues but it resolved its self
Hello folks.
I'm having an issue with my phone, S21 Unlocked SM-G991U1 (purchased directly from Samsung). This post might be long because I want to include all info to help answer questions that I might already have eliminated possible issues on.
I bought the phone March 18th and it's been working perfect up until exactly 4 days ago. What's been happening is that it will fail to send sms/texts randomly throughout the day. I can be having a conversation with someone then suddenly the texts I'm sending will begin to fail and they will get the ! or endless spinning circle depending which messaging app I'm using. I tried several apps (stock messaging, Google messages, textra) to eliminate the possibility of it being a specific one, it happens with all of them.
I then switched my sim card to another phone for several hours (S8) to see if it was a network issue... The S8 works perfect, no failed texts. As soon as I switch the sim back to the s21 the messages will fail again.
This happens at any given time, it will go from working fine for about 5 messages in a row then fail on every next message for about 10-15 mins then start working again.
This does not affect MMS or phone calls. Only SMS.
I'll also be able to receive any sms messages sent to me without issues at any time, even when outgoing ones fail.
I've tried resetting Network Settings to no avail.
I just did a complete factory reset, also no to avail. I'm lost here.
The phone has the latest update and had been working perfect up until 4 days ago. I can also say that I don't think the latest update was the cause because it started the day before I received the push notification for the update.
I'm on AT&T prepaid.
Please let me know if you have any questions I might not have covered or if you've encountered this issue before or what might be the fix. Thanks in advance!