Related
I have an unrooted ATT version of the nexus one. Randomly about 1 or 2 times a day while I am texting I will get a failed to send message and no matter how many times I try it just keeps failing. It won't allow me to send texts to anyone else either. however I continue to receive texts which is kinda odd.... the worst part is that always while this is happening I cannot make or receive phone calls this is very frustrating since I could be missing phone calls and wouldn't know it until I try and send an SMS or make a call. I have tried a lot of different things such as setting my bands to USA and setting my network preference to WCDMA Only but to no avail... I also tried a factory reset... also if I try and toggle airplane mode or turn off the radio it just crashes and I need to reboot.. if i try checking the SMSC while this is occurring but hitting the refresh button
I get refresh error and if I try and update it with the correct number I get update error... I really love my N1 and would really appreciate anyone who could shed some light on this issue
Re: My Nexus One won't send text messages or make phone calls unless I reboot
Could this be an AT&T network issue? I had similar symptoms with my HTC Hero (admittedly running EDGE) in certain parts of San Francisco earlier this year. It seemed to be the result of network congestion. Does this occur in a city or other urban area?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I am actually not on AT&T I am on Rogers network in Canada. I am living in Toronto so the 3G coverage is really good and I`ve never had this kind of issue with my previous phone which was a BB9000 and none of my friends seem to have any of these problems
I also found ppl on some other nexus one forums describing the exact same problem which leads me to believe its not a network issue but I am still not 100% sure I tried calling Rogers and had them do a cancel location and it didn`t fix the issue either
I had this issue only this morning and I'm in the UK, I put the phone into Airplane mode and back again and then everything is fine.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
jasrups said:
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
Click to expand...
Click to collapse
Same thing happened to me today. I'm on a stock unrooted AWS version of the N1.
hayden1987 said:
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
Click to expand...
Click to collapse
I am unable to make phone calls, send texts, etc. until I reset. It has no impact on Wifi but kills the cell network completely.
wmm said:
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
Click to expand...
Click to collapse
I also have a long delay after hitting restart when I get this issue. Maybe Ill try to get a logcat and see what it gets stuck on..
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
http://www.google.com/support/forum/p/android/thread?tid=3f4ad5ffac46bf92&hl=en
http://www.google.com/support/forum/p/android/thread?tid=47dc569ca9667ba7&hl=en
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
blisk said:
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
Click to expand...
Click to collapse
I`ve tried all the solutions u`ve mentioned except for swapping to a new SIM card... I guess it might just be my next step but I have my doubts
I get this kind of issue occasionally, under these specific conditions only:
1. I'm at work.
2. I bring my phone with me into an area with no signal (screen says no signal, and I have 4 blank bars with an X) for more than a couple of minutes (for me, it's the room with the coffee machine - which I use a lot - no provider gets signal there on any phone).
3. It doesn't always happen, just sometimes, but when I go back to my desk, it won't reconnect.
4. Going into and out of airplane mode fixes it every time. However, with the latest CM and Ivan's Diet kernels, going into and out of airplane mode causes an immediate reboot when I try to come out of it, and only when I'm NOT connected by USB and when I AM coming from "dead" service, making logging the problem, well, problematic. Using other kernels (even OC'd kernels) does not seem to cause this airplane mode problem.
Only had this happen once trying to send a plain old SMS. I restarted the phone and no problem. I didn't think of trying to make cell calls, but if it happens again, I'll try that.
I too have had this issue with SMS. My browser works though when the SMS problem occurs. Haven't tried a phone call. I am on T-Mobile USA.
Are any of you using task-killers that may somehow be interrupting an important background service?
I have the same exact thing happen and I am on T-mobile US. I was hoping that I wasn't the only one but it seems to happen on all of my phones so I have just chalked it up to network congestion. Unless someone has an actual answer.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
Click to expand...
Click to collapse
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Have any of you edited your build.prop yet?
This helps with the switch from Edge -> 3G -> H.
I wonder if it would fix this issue.
I don't have the issue so I am unable to test myself.
This link may help. Its at least something to try.
http://forum.cyanogenmod.com/index.php?/topic/1721-3g-connectivity-issue-fix/
This link my help too.
http://forum.xda-developers.com/showthread.php?t=659102
Re:
same thing with me im going to check out those steps your provided.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
azalex86 said:
Are any of you using task-killers that may somehow be interrupting an important background service?
Click to expand...
Click to collapse
I am using Advanced Task Killer Free, but I'm pretty sure I added important background services to the ignore list so they shouldn't be killed.
Just to double check, what background tasks shouldn't be killed?
My N1 will not reconnect to a mobile network if it has been sitting for a few hours in a no-coverage area, such as a building. I cannot get it to reconnect, even after refreshing the network search. This action only leaves me with no result or a message saying that there was an error in searching or connecting to mobile networks. The only solution is to restart the phone. Every time I try to turn the phone off after this error has occurred, the shutdown sequence hangs until either I become frustrated and do a battery pull, or it automatically restarts and do a battery pull, or it automatically restarts itself. Furthermore, the phone used to give me an error notification saying that the phone does not have carrier service. Now, it does not. Furthermore, the phone used to give me an error notification saying that the phone does not.
I tried uninstalling all my programs and nothing has worked for me. I've also tried toggling the airplane mode to no avail.
I'm considering putting on the cyanogen ROM to see if it would fix this error, but I am hesitant to void my warranty. It's a pretty serious problem as I'm very frequently in a building where I don't get service. It's quite frustrating to have to wait to reconnect to a mobile network once I leave the building and hope that the error didn't occur or have to do a battery pull every time I realize that the phone simply won't reconnect.
Can anyone suggest any solutions?
Mod it. What have you got to lose? Your overall performance will increase. The radio signal may even improve. Your call.
jacka$$1 said:
Mod it. What have you got to lose? Your overall performance will increase. The radio signal may even improve. Your call.
Click to expand...
Click to collapse
thanks for the tip. i've been thinking about it. it's the warranty i don't want to lose. eh i'll keep thinking about it.
this phone sucks. it's glitchy, can be sluggish. iphone got dumbed down but at least its functions work.
meh
Hey!
You dont want to lose your warranty, then use it!
Your phone seems to be faulty...
My phone is experiencing the same problem as of yesterday. Won't connect. Wonder if it's a T-Mobile issue.
laughter95 said:
thanks for the tip. i've been thinking about it. it's the warranty i don't want to lose. eh i'll keep thinking about it.
this phone sucks. it's glitchy, can be sluggish. iphone got dumbed down but at least its functions work.
meh
Click to expand...
Click to collapse
Its only glitchy coz you have stock rom
Cyanogen is really stable and adds alot of features / functionality.
Fair enough you dont want to lose warranty but i remember in the general thread that lots of hardware failures and others can still fix your n1 under warranty even though they unlocked the bootloader.
I too have this problem, hopefully the 2.2 update will fix the problems.
Can you guys confirm if its android or your service provider thats causing this...
laughter95 said:
My N1 will not reconnect to a mobile network if it has been sitting for a few hours in a no-coverage area, such as a building. I cannot get it to reconnect, even after refreshing the network search. This action only leaves me with no result or a message saying that there was an error in searching or connecting to mobile networks. The only solution is to restart the phone. Every time I try to turn the phone off after this error has occurred, the shutdown sequence hangs until either I become frustrated and do a battery pull, or it automatically restarts and do a battery pull, or it automatically restarts itself. Furthermore, the phone used to give me an error notification saying that the phone does not have carrier service. Now, it does not. Furthermore, the phone used to give me an error notification saying that the phone does not.
I tried uninstalling all my programs and nothing has worked for me. I've also tried toggling the airplane mode to no avail.
I'm considering putting on the cyanogen ROM to see if it would fix this error, but I am hesitant to void my warranty. It's a pretty serious problem as I'm very frequently in a building where I don't get service. It's quite frustrating to have to wait to reconnect to a mobile network once I leave the building and hope that the error didn't occur or have to do a battery pull every time I realize that the phone simply won't reconnect.
Can anyone suggest any solutions?
Click to expand...
Click to collapse
I have the same problem and it's starting to bother me a lot because my car is parked in a garage with no coverage. My in-car BT then becomes useless as my phone won't reconnect to the network once I exit the garage
I just called Google support 10 mins ago about this and they went through normal protocol to reset to factory settings. They then called Tmo and let them know what the issue was while I was still on the phone. Tmo unregistered my phone from the network while my battery was taken out of my phone and then reregistered my phone to the network. Tmo asked me to monitor this for a few days and call them directly (not Google) if the issue persists. They will then elevate this to a higher level because they feel this would be a network problem, and not a hardware issue.
Hope this helps! Please post what you have tried to solve the problem!
rensky said:
I have the same problem and it's starting to bother me a lot because my car is parked in a garage with no coverage. My in-car BT then becomes useless as my phone won't reconnect to the network once I exit the garage
I just called Google support 10 mins ago about this and they went through normal protocol to reset to factory settings. They then called Tmo and let them know what the issue was while I was still on the phone. Tmo unregistered my phone from the network while my battery was taken out of my phone and then reregistered my phone to the network. Tmo asked me to monitor this for a few days and call them directly (not Google) if the issue persists. They will then elevate this to a higher level because they feel this would be a network problem, and not a hardware issue.
Hope this helps! Please post what you have tried to solve the problem!
Click to expand...
Click to collapse
^ it worked! my phone reconnects to the cellular network after what Google/Tmo did for me on the phone!
I haven't tried calling tmobile, but it is NOT something that will be fixed by hopping on cyanogen's rom. I've been rooted on cyanogen's rom for quite some time and this problem still exists on my n1 which is SUPER annoying. I will try calling tmobile to see if they can fix it on their side, but rooting is not the fix here.
I had the same issue. I used anycut and phone info shortcut and changed the wireless default setting to us and it totally fixed the problem. Have not had that issue again.
-------------------------------------
Sent via the XDA Tapatalk App
I resolved this by going to the T-Mobile store where they replaced my SIM card. They made a copy to a new SIM card, installed it and everything works fine.
For the record symptoms included:
* "Error while searching for network" message
* Found networks but said "your SIM card is not authorized for this network" when connecting
* Network listed as "No service" or "Emergency calls only | T-Mobile"
I get this too with an at&t phone.
Have asked for a replacement device from HTC (since the reception is crappy to begin with).
I also have audio quality problems when reception is only 1-2 bars.
Will see if the new phone is better.
I had this problem regularly. It hasn't happened once since I upgraded to Froyo, so I think it has been fixed in that release.
sometimes have this too, i fix it by going to the settings > wireless > mobile networks > APN. at first i deleted and retyped my password in the selected APN, now i just click my network in the APN settings, don't change anything and leave. It immediately reconnects after that.
edit: and i have stock froyo & live in belgium.
I got a new, replacement phone from HTC today.
This new phone has a BIG PROBLEM with this issue.
Even if I am only without reception for a couple of seconds (go through the garage, etc.) it will not connect to any network until I reboot.
My old phone would only experience this problem maybe 25-35% of the time.
Very, very annoying!!!
wildfyr said:
I resolved this by going to the T-Mobile store where they replaced my SIM card. They made a copy to a new SIM card, installed it and everything works fine.
For the record symptoms included:
* "Error while searching for network" message
* Found networks but said "your SIM card is not authorized for this network" when connecting
* Network listed as "No service" or "Emergency calls only | T-Mobile"
Click to expand...
Click to collapse
I had similar issues and called tmobile support. I was first linked to Google support. They went through the similar process as described by in the first page. (#*#*4636*#*# select USA band etc). While I was on hold, they called t mobile tech support and had them reset network connection and tried to get me onto a different tower etc.
Tmobile support stated that my sim card (had for about 2 years) was the cause of the issue as they can't handle smartphones as well as their new sim cards. They also said the new sim should improve reception and connection stability (Don't see how a new sim could do this but what do I know?). Moreover, they noted my account and told me to go into the nearest store for a new sim card. Went into the nearest tmobile store told them the issue, they pulled up my account and gave me a new sim. Took less then 5 minutes and I have not had the issue with staying connected to the tmobile network.
I will update this after a few days to see if I still have the issue.
I have the same problems that i cannot connect to network here in germany. first i think it was my sim card, but befor i had another provider (E-Plus) where i had the same problems with reconnecting to network. and one day my eplus sim card is broken so i had to buy a new one by t-mobile. i have tried a lot of roms from here (cyanogen/ 5.0.7 /5.0.8T5 Kangorama rodriquezstyle and leofroyo) everyone seems to have the same problems with reconnecting to network. i hope im not alone with my problems and someone can help.
hmm...
Count me as another. I just upgraded to froyo and it went beserk. Had no service for a while. It would only come on after constantly tapping "select network automatically" until it kicked me out of the menu. It started getting better but kept kicking me out of 3g. I set it to stay always on 3g and it seems to be better... still I'm going to call tmobile and see if I can get a new sim as well.
Thanks for the info guys!
I have a Galaxy tab from TMobile, I followed the directions on how to make it a phone here dub dub dub dot youtube dot com/watch?v=9oADoLHWHH4 It all seemed to go without a hitch but I cannot make phone calls or get data access (wifi works well though). At one point I was able to make one phone call and send two texts, but it all stopped and does not work. At first I thought it was a reception issue. Then I reflashed it with the euro roms, all in an attempt to get it working reliably.
After doing the above procedure I did sometimes get the edge icon to show up, I can see data going UP but the down arrow never seems to change color (I think they are supposed to change colors).
I have an AT&T SIM, could that be my problem? I do not get a message to eable the network, so the system is unlocked (I think).
SHould I sell the tab and get an AT&T tab? maybe that will have better luck?
I am starting to thing this is an issue with a blocked Emei number.
Can you borrow a T-mobile SIM to try? That would prove if it's a SIMlock issue & also prove the hardware.
Sent from my GT-P1000T using XDA App
Having my Nexus 6 for almost a month. Things working perfectly in the starting(or after reset), but after two or three days, No incoming calls, no outgoing calls. No mobile data. Cant realy tell it as a mobile sometimes. Wifi is working good always. After reset, it is working properly for two or three days. Whenever it is not working, I am able to see a !-mark near the tower bar.
My mobile always connected to 4G when no wifi.
No Custom ROMS and no root. Plain Android given by google.
Anyone having this issue. Any suggestion?
Go get a new SIM.
Sent from my Nexus 6
I was begining to think i was the only one who had this problem!
Yesterday morning i woke up and to my suprise my signal bar had a (!) it it but it was still displaying my regual signal level.
I switched my wifi of and i couldnt get a data connection just the (!) sign. I got my girlfreind to give me a ring and see if a
call would go through which it didnt it just said that i was unavalible. I then desided that a reboot might sort the problem
but when i my phone booted back up i was presented with the holow triangle signal icon to say that i had to signal. I then
popped my simacard out thinking it could have just been a bit of dust on it. I gave it a little bit of a dust of and popped it back
into my phone and i was given the same no signal and emergency calls only yet it was picking up that there was a simcard inserted.
The day before i had flashed the alpha version of PA so my next thought was that this would be a ROM bug and went ahead and
flashed chroma which i was using prior to PA and i had had no issues with. Held my fingers crossed as it booted up but much to my
dismay i was greated with the same no signal problem but i went into the settings and searched for networks. Three was one of
the network it had picke dup so i tryed to reconnect to it but i got the toast to tell me i couldnt connectto the network and to
try again later. I checked the APN settings and it had automatically grabbed threes APN from the sim card so at this stage i was
completly baffled by them problem.
My next move was to try my sim in my girlfreinds phone and what do you know it worked a charm. As a last shot to check everything
was okay and i was upto date on my bills etc i gave three a ring and they told me there was nothing wrong with my sim and everything
was working as it should be and that it was a problem with my phone.
That brings me to the point i am at now completly baffled as to the problem and slightly angry at the 2 week old phone that had been working
perfectly up until now has suddnely desided to stop with no warning.
So you are not the only one and i expect their are more of us. I am going to flash the offical stock rom from google and see if that does the
trick but im not holding up much hope i feel like im going to have to contact google and find out where the problem lies.
New SIM which is working good in other mobiles
SilkyJohnson said:
Go get a new SIM.
Sent from my Nexus 6
Click to expand...
Click to collapse
I got this as new nano SIM from the retailer and seems like working in all other mobiles except Nexus 6. Also I can see lot of people having the same issue with Sprint Provided in US. One more Victim replied too.
greatleo said:
I got this as new nano SIM from the retailer and seems like working in all other mobiles except Nexus 6. Also I can see lot of people having the same issue with Sprint Provided in US. One more Victim replied too.
Click to expand...
Click to collapse
i reverted back to complete stock using the image from there site to no luck so i relocked the bootloader and took it back to the carphonewarehouse and they straight swapped it for a new one which is working perfectly
My sim died after a month. My calling went out and then only lte worked no 3g. Got card replaced and it works perfect now. I have US Cellular.
I've posted this in few other threads also, but I had also problem where I only had tgt exclamation mark no matter what I did. I solved the problem by waiting like 5sec before inputting my pin-code. If I input my pin code too fast after a boot, it will open my phone, but won't give me cellural network. This seems to happen in every ROM I've tried
Hi,
Solved the issue. Working fine after enabling request for SIM Pin and set my sim pin.
Usually i disable sim pin lock to have uninterrupted boot. But with ROM this is not working.
Enabling SIM pin request solves the issue.
Is this problem with carrier or Android L?
Sent from my Nexus 6 using XDA Free mobile app
greatleo said:
Hi,
Solved the issue. Working fine after enabling request for SIM Pin and set my sim pin.
Usually i disable sim pin lock to have uninterrupted boot. But with ROM this is not working.
Enabling SIM pin request solves the issue.
Is this problem with carrier or Android L?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I have not seen this issue on three devices I've owned with Lollipop. So it appears to be a carrier issue?
My wife bought me the international version of the Samsung Gear S (SM-R750W). She said that she researched and from her understanding it should work on the T mobile network. From what I've found though the consensus seemed to be it would not work, or if it did it would be spotty at best depending on the specific towers/area you were in because Tmobile utilizes different network types in different areas.
I decide to give it a shot anyway and went to the T-Mobile store where I signed up for the wearable plan and got a new nano sim card. I was crossing my fingers but as soon as they put the sim card in the watch it came to life. It looked to be working fine but as I left the store I received a text from T-Mobile stating " the SIM for your wearable devices is in an ineligible device. Services to the SIM are locked until it returned to your eligible wearable device".
I pessimistically started thinking well great, there goes that idea. But as I got into my vehicle I shut my phone down and tried to see if the watch can work on its own as a phone when unencumbered from my Note 4 bluetooth/WiFi data connections. It worked perfectly-I started calling my friends and they couldn't believe I was talking on a watch phone. Several I actually felt the call sound quality was better on the watch speaker phone compared to normally speaking on the Note 4. I called customer service but they told me they couldn't see anything and if it was working fine not to worry about it.
For the next eight or 9 hours it worked perfectly and I was using it a lot. I drove around large swaths of town and neither data nor call experienced even the slightest issue - for once I was happy to be wrong.
Eventually, as I am oft to do, I fell asleep. When I awoke this morning the watch was no longer connected to the network. It gave me a message saying it was unable to connect and did I want to scan for additional networks. I selected yes and it was able to find the T-Mobile and ATT networks. T-Mobile was selected and a "registering" notification was displayed. It took awhile but eventually said it was unable to register with the network.
I call T-Mobile and they said pretty much exactly what I expected them to say -that because it was not a T mobile device they could not ensure proper operation. But he said (and he characterized this as "good news", "light at the end of a tunnel" and "viable solution” Seriously said all 3 things.) I could either forget all about the cellular connection and just use this as a companion device OR go and buy a new Gear S from T Mobile if I really wanted that feature.
I’m truly and utterly baffled that he believed his suggestions merited the positive sayings from above. Never in my lifetime has my head been closer to exploding.
After I was finally able to speak again, I explained that it seemed unlikely to be an issue with the watch. If my Gear S was working perfectly yesterday and can still detect Tmobile & ATT networks, then something on your end seems to be preventing registration. He agree to file a ticket with the engineering team and tomorrow I should hear from them hopefully. He also told me to go and try another nano-SIM, gratis, at the Tmobile store. So today I went and as soon as I put the new card in all systems were go. I assumed that I somehow had received a bad card because here again now, data and voice are connected.
This time I didn’t even make it out of the parking lot before it notified me that that it was again unable to register with the network. There is conflicting information regarding the radio frequencies and bands that the different Gear S models have and I didn’t have high hopes. But then it actually did work, WELL, so any ideas as to what is going wrong?
I don't know how I put this in the wrong forum, could one of the mods please delete it? It's already been reposted in the correct forum.