Seems that all of a sudden I can no longer receive calls. I thought it was just certain people since I had received calls before but now the people who were successful in the past can't get through any more. It's either just dead or says call not allowed from this device or those beeps you get when the recording says "if you'd like to make a call...".
I'm wondering if I inadvertently did something to cause this. I'm totally new to smartphones, android and sense. I've gone through settings that I know I went into and I can't find anything. I rebooted phone, leaving it off for a few minutes, still no incoming calls. I can call out though, even before reboot. Have not done any temp rooting since I'm still reading up on all that stuff and don't have a grasp on it yet.
I did install some apps but this seems to have started without connection to that although I can't be certain. I can gather a list of them if needed.
I'm thinking of doing a factory reset. I've backed up all the pics and videos I took over thanksgiving to my computer and I believe there's only one app that wasn't free that I got from the Amazon app store. Will all my contacts stay if I do a factory reset? I still have my old phone so I suppose I could get Verizon to transfer them over again, or maybe I can get them off my car since I just put them on there.
Oh!!! Would it have anything to do with me having set it up to use in my car? I was sending out music via bluetooth so I had to set it up as a "portable player" in my car. Maybe I changed something in the phone... I can't really remember and I'm not finding any settings in the music app or in the main settings.
Anybody know if there's something I might have done? Am I safe to do a factory reset?
Edit: One other thing I did to the phone was add a "Music" folder on the external sd and put in a bunch of music. I couldn't find how to do this in the manual or via google so I just hooked it up to my computer and tried that and it worked as far as listening to music. Doubt it would affect phone but wanted to be complete in this post.
Installing apps and making music folders should in no way affect your ability to receive phone calls. Sounds like you need to call Verizon.
punman said:
Installing apps and making music folders should in no way affect your ability to receive phone calls. Sounds like you need to call Verizon.
Click to expand...
Click to collapse
Agreed, before you go resetting anything call *611 from your handset or whatever Verizon's 800 number is and see if they screwed something up(more than likely)
punman said:
Installing apps and making music folders should in no way affect your ability to receive phone calls. Sounds like you need to call Verizon.
Click to expand...
Click to collapse
MrSmith317 said:
Agreed, before you go resetting anything call *611 from your handset or whatever Verizon's 800 number is and see if they screwed something up(more than likely)
Click to expand...
Click to collapse
Yeah, I called earlier but I don't have another phone to call from so I'll have to go down there. I made her promise they would compensate me for my time since I complained about switching from AT&T and having problems already.
Hahahaha.... I inadvertently turned on call forwarding and it was forwarding to number 9. I know exactly how I accidentally did it too. I was clearing out my old AT&T contacts which had come over and they all start with *. I wanted to be certain they were not Verizon numbers so I dialed each one first and one of them activated the forwarding. I didn't seem to get any notification of it being turned on that I noticed.
Needless to say I thanked the guy at Verizon for finding out what it was and did NOT ask for any compensation.
Glad you got it all figured out I would have been in panic mode!
I almost did that when he started talking about me having to return it to Amazon for a replacement. I immediately started thinking no! I have red buttons! My phone doesn't overheat or reboot on its own! What if I get a bad one. Plus they're on backorder there! I need a phone, my old one is AT&T!! LOL.
Related
Hey guys, i thought i saw some time ago a way to be able to make and receive phone calls through the Sprint Evo View 4G? Am i right or was it the Flyer? now is this even possible at all?
I have made and received calls on my view using an app called grooveip.
Sent from my PG41200 using xda premium
shotguntheenforcer said:
I have made and received calls on my view using an app called grooveip.
Sent from my PG41200 using xda premium
Click to expand...
Click to collapse
Yes I am sure that works but i mean a native phone dialer like the Flyer(GSM) version? has anyone gotten this to work?
I don't believe so, Sprint disables voice on the network side, not handset side.
DevalB said:
I don't believe so, Sprint disables voice on the network side, not handset side.
Click to expand...
Click to collapse
Are you sure? While attempting to port an Evo View ROM to the 3D I came across a line in the build.prop mentioning the disabling of the dialer. I Don't remember exact syntax at the moment but we ended up changing that value on the port to get the dialer working for the 3D.
I thinks it's possible to the point that I think I'm going to try it sometime in the near future lol.
Well on my View I have the native phone dialer enabled with icon and everything. The phone doesn't connect to anything, however. It just vibrates like it's connecting and timer runs like I'm connected tho I'm not. Therefore, I just use grooveip for phone calls. This looks promising tho since the native dialer is there. But my pessimism is telling me that this is next to impossible due to voice being disabled on Sprints end as stated by a previous poster.
If I have just the data plan, then I only get data? I send and receive sms/mms just fine. Does Sprint offer a voice package for the View or one at least compatible?
EDIT:: I actually pay for unlimited SMS/MMS with my tablet plan. So ignore that part, but since messaging uses the same 1xRTT network as voice, I don't imagine it would be too hard to get voice working on this thing.
As far as I'm aware, the hard part of getting the View to make "native" phone calls, is the fact that the ESN for the device needs to be associated with the a plan that supports voice, and Sprint, as a corporate policy, won't do this. Whilst I suppose it is possible that a very, very friendly CSR could do this for you, I wouldn't like to bet on it.
Regards,
Dave
I believe the system blocks certain plans from being applied with certain ESNs. Things were different before I believe but not now.
I did manage to get a phone call out from my view to my 3d. As soon as i answered it on my 3d both lines disconnected. If I were a gambling man, which I am, I'd say you guys are correct in the no calls to/from a tablet on Sprint.
My only remaining questions are why? The device is capable of sms and if I'm not mistaken still uses 1xRTT which is also what voice calls use?
mbobino said:
I did manage to get a phone call out from my view to my 3d. As soon as i answered it on my 3d both lines disconnected. If I were a gambling man, which I am, I'd say you guys are correct in the no calls to/from a tablet on Sprint.
My only remaining questions are why? The device is capable of sms and if I'm not mistaken still uses 1xRTT which is also what voice calls use?
Click to expand...
Click to collapse
That's a good question, but I'm getting the majority of the folks who would use this device wouldn't want a 7" phone
DevalB said:
That's a good question, but I'm getting the majority of the folks who would use this device wouldn't want a 7" phone
Click to expand...
Click to collapse
Well, I bought the device for a 20$/mo 7" phone, and I love it.
The reason sprint won't let you use voice is because they don't want the secret to get out that in reality you only need one PIPE (ie data plan) to do everything you need... they love selling you a 40$/mo voice plan.
Think about how LITTLE you use the phone (even if you use it a lot it doesn't cost as much as data) and think that they basically charge the same amount for the voice as for the data, on a standard smart phone.
Great cost/benefit ratio...
I really hate how you guys make so much sense... It really does suck though that if my 3d dies that I can't make a call from my view. I might call sprint and see if they can just share my minutes between both lines. I use a whopping 3 a month total.
Sent from my PG86100 using Tapatalk
I'm using a View Port on my Evo 4g. Im using Dailer one.
Ok guys i got calls outgoing on my view an it works wel through a bluetooth headset. Im not using it on sprint. Anyone interested PM me. But i can't get calls to come into the device. When people call me it rings about 5 times then it goes into voicemail.
Ostthug2k said:
Ok guys i got calls outgoing on my view an it works wel through a bluetooth headset. Im not using it on sprint. Anyone interested PM me. But i can't get calls to come into the device. When people call me it rings about 5 times then it goes into voicemail.
Click to expand...
Click to collapse
Does it really work well? Whenever I use bt i get very delayed and crackling voice... I can hear about 30% of what is said through all the crackling. It is unusable...
I followed the build.prop in the guide... any ideas?
sdge said:
Does it really work well? Whenever I use bt i get very delayed and crackling voice... I can hear about 30% of what is said through all the crackling. It is unusable...
I followed the build.prop in the guide... any ideas?
Click to expand...
Click to collapse
Mine works perfect,? sounds great! Are you using the native Dialer, or grooveip?
Im using the native phone app. But i cant receive incoming calls. Do you receive incoming calls?
sdge said:
Does it really work well? Whenever I use bt i get very delayed and crackling voice... I can hear about 30% of what is said through all the crackling. It is unusable...
I followed the build.prop in the guide... any ideas?
Click to expand...
Click to collapse
I called Sprint yesterday or the day before because I was having connectivity issues which gave me an idea. The Sprint reps (all 7 of them) had no idea that the Evo View was a tablet, they kept telling me to go into the dialer and dial in EPST codes and stuff which I kept telling them was impossible since I didn't have a "Phone" app to get to the dialer from. I finally got someone who did realize that the dialer is inaccessible because its a tablet and not a phone and told me to use the dialer codes in the calculator app substituting hash/pound/# for exclamation/!
My idea being, with CDMA Workshop/QPST/EPST you should be able to swap ESN's (illegal as hell so I don't recommend it nor will I share how to do it) and get the tablet up on the voice network.
As for the quote above, with your view in landscape, open the calculator and type in !!3282! = and you should get EPST. You will need your MSL code! It'll ask you for View Mode and Edit mode to which you'll want to edit the settings. Go to Advanced and make the following changes::
- EVRC-B from Disabled to Enabled
- Home Orig from EVRC to EVRC-B
- Roam Orig from EVRC to EVRC-B
What this will do is change the voice codec (kinda like .mp3 or .wma) for your incoming and outgoing voice quality to one that is newer, has better compression, and has better quality (Almost like the difference between .mpeg and .mp4).
All of this is based on my knowledge of CDMA Android phones. I'm not 100% that it will work on the view at all as mine isn't in front of me at the moment. Also, just to be safe, I'm not liable for damages if you screw up your phone. It's very easy to revert the settings back to factory defaults and doesn't require a full device wipe. I just don't remember the dialer code.
Anyways, best of luck to you in getting this working. I'm taking a break from the view (I really want Honeycomb but I'm too scared to flash radio.img and hboot.img to try and get it working) to work on my Evo 3D projects. I'll still be lurking though so I'm not gone for good. The View needs some more devs and hopefully I'll have something I like on my 3D enough to stick with it for a while.
mbobino said:
I called Sprint yesterday or the day before because I was having connectivity issues which gave me an idea. The Sprint reps (all 7 of them) had no idea that the Evo View was a tablet, they kept telling me to go into the dialer and dial in EPST codes and stuff which I kept telling them was impossible since I didn't have a "Phone" app to get to the dialer from. I finally got someone who did realize that the dialer is inaccessible because its a tablet and not a phone and told me to use the dialer codes in the calculator app substituting hash/pound/# for exclamation/!
My idea being, with CDMA Workshop/QPST/EPST you should be able to swap ESN's (illegal as hell so I don't recommend it nor will I share how to do it) and get the tablet up on the voice network.
As for the quote above, with your view in landscape, open the calculator and type in !!3282! = and you should get EPST. You will need your MSL code! It'll ask you for View Mode and Edit mode to which you'll want to edit the settings. Go to Advanced and make the following changes::
- EVRC-B from Disabled to Enabled
- Home Orig from EVRC to EVRC-B
- Roam Orig from EVRC to EVRC-B
What this will do is change the voice codec (kinda like .mp3 or .wma) for your incoming and outgoing voice quality to one that is newer, has better compression, and has better quality (Almost like the difference between .mpeg and .mp4).
All of this is based on my knowledge of CDMA Android phones. I'm not 100% that it will work on the view at all as mine isn't in front of me at the moment. Also, just to be safe, I'm not liable for damages if you screw up your phone. It's very easy to revert the settings back to factory defaults and doesn't require a full device wipe. I just don't remember the dialer code.
Anyways, best of luck to you in getting this working. I'm taking a break from the view (I really want Honeycomb but I'm too scared to flash radio.img and hboot.img to try and get it working) to work on my Evo 3D projects. I'll still be lurking though so I'm not gone for good. The View needs some more devs and hopefully I'll have something I like on my 3D enough to stick with it for a while.
Click to expand...
Click to collapse
I did this on my View, but can only get Calls out, cannot get calls to come in while tab is idle or not in a call. If some one would look into the phone app. I'm sure we could fix it.
sdge said:
Well, I bought the device for a 20$/mo 7" phone, and I love it.
The reason sprint won't let you use voice is because they don't want the secret to get out that in reality you only need one PIPE (ie data plan) to do everything you need... they love selling you a 40$/mo voice plan.
Think about how LITTLE you use the phone (even if you use it a lot it doesn't cost as much as data) and think that they basically charge the same amount for the voice as for the data, on a standard smart phone.
Great cost/benefit ratio...
Click to expand...
Click to collapse
Don't get me wrong, I love it too!
Like the title says, everytime I flash a new one, or if I flash ziggy kernel especially I cannot get voice calls or data, i get radio interface shortage errors when texting ect, i have to do the ##3282# reset about 5 times to get anywhere, any theories or suggestions? I haven't seen anyone else with this problem and it started when I flashed xron ROM a few nights back..
Are you a google voice user? Are you gsm or cdma?
I only use google voice for voicemail, its Sprint CDMA
Did you update your radios AND firmware? I think the file was radio firmware nohboot or something like that?
3VO Sent
PaulB007 said:
Like the title says, everytime I flash a new one, or if I flash ziggy kernel especially I cannot get voice calls or data, i get radio interface shortage errors when texting ect, i have to do the ##3282# reset about 5 times to get anywhere, any theories or suggestions? I haven't seen anyone else with this problem and it started when I flashed xron ROM a few nights back..
Click to expand...
Click to collapse
It doesn't happen to me EVERY time, but I find myself having to go through the whole reprovisioning and re-setting data thing a lot more than I would prefer to. Hell, I've had 6 of these handsets since release date and I've had to **** around with this issue right out of the box on EVERY one! Love the phone but cmon HTC....wtf!! They really screwed the pooch on this phone, lol.
---------- Post added at 08:00 PM ---------- Previous post was at 07:47 PM ----------
My problems are usually data problems. As far as losing voice, that happened once after using one of the older "superwipe" files floating around. Took a whole Saturday to get it back, had to get Sprint involved...boy was I pissed! Been using XRON superwipe lately and it's doing the trick!
Try ##scrtn# from dialer then enter your msl. After it reboots let us know if that works.
jonnybueno said:
Try ##scrtn# from dialer then enter your msl. After it reboots let us know if that works.
Click to expand...
Click to collapse
Still didn't help, when I go to more info on the radio interface shortage error the error code is 67,wasn't that the code a lot of people were getting after revolutionary first came out?
Call sprint and have them reset on their end....and good luck
Sent from my PG86100 using xda premium
I might have to do this, for some reason this actually happens after every single reboot, had to clarify that.
This happened to me too, even with those resets you are talking about I wasn't able to fix it. You have to call sprint, they do something on their end, guide you through the same process you are talking about, and then it works. Dial 611, tell them the error and any error code you have. Apparently they are familiar with it because they know exactly what you are facing and know how to fix it without doing any research or any other diagnostic steps.
I don't think this problem has anything to do with HTC, or the phone itself. I think it has to do with Sprints Google Voice integration. I use GV for voicemail only and I have this problem every once in s while. Next time it happens, try making the call using GV. If it works you know this is your problem. For some reason, even though you have it set up differently, GV will take over. This is a completely separate issue from the error 16 that a lot of people are getting with this phone. If it is an error 16 a simple call to Sprint will fix it. If it is the GV integration thing, then it is much harder to fix and rebooting to recovery, wiping cache and dalvik will sometimes fix the problem. Also, reflashing the kernel will sometimes fix it too. I haven't figured out a definite way to fix it yet though. It seems every time this happens, it takes something different to fix it.
I'm actually not even setup to make calls on google voice, I went directly onto the voice. Google. Com website and changed the settings to voicemail only and turned off all other integration.. Can it still be interfering?
PaulB007 said:
I'm actually not even setup to make calls on google voice, I went directly onto the voice. Google. Com website and changed the settings to voicemail only and turned off all other integration.. Can it still be interfering?
Click to expand...
Click to collapse
Yes. Mine is set up the same way and when this happens if I choose to ask me every time I make a call in the GV app settings and choose GV to make the call it goes through, but when I chose do not use GV it won't work. I get a message that says, "I'm sorry, we are unable to complete your call at this time. Please try again later" and that's it. Since the Google Voice integration with Sprint I have noticed that no matter who you are calling you must dial 1, then the area code, then the # even if it is a local call.
I don't know how confusing was the title but I have a problem.
When Im talking on the phone, and someone else calls, the call that Im currently in, is muted.
So if Im on the phone with my dad, and my mom calls while I speak with my dad, then I can't hear my dad and he can't hear me either. Even if Im the other person hangs up, the sound doesn't resume. So I need to call my dad again. Those were all example yes?
My phone is not rooted, never been modified since I got it out of the box and also, I never had this problem before.
What can I do?
What apps have you installed and what settings have you changed? How come you haven't rooted it?
andrewwright said:
What apps have you installed and what settings have you changed? How come you haven't rooted it?
Click to expand...
Click to collapse
Its my grandad's phone. He doesn't need a rooted phone, haha...
I highly doubt he installed or changed anything since he doesn't understand most of the things that the phone offers. Either from making calls, Skype and emails, he doesn't really do anything else...
Bkup you're /his contacts with google and flash stock with Odin. I guess you know how to do this. And I guess as its you're granddaddy phone and nandroid and rooting and all that won't really matter.
So yesterday I'm on the phone and I go to send a picture to someone(MMS) and after a bit it came up with a box saying it failed and to retry now or later. I tried it a few more times and still nothing. I know my Galaxy S3 allowed me to send picture messages while in calls so is this a device limitation? Am I the only one experiencing this? Or is there a New law or something that doesn't allow picture sending while in calls for some reason?
Just wanted to get some feedback to see what other people are experiencing.
XXchocolatetouchXX said:
So yesterday I'm on the phone and I go to send a picture to someone(MMS) and after a bit it came up with a box saying it failed and to retry now or later. I tried it a few more times and still nothing. I know my Galaxy S3 allowed me to send picture messages while in calls so is this a device limitation? Am I the only one experiencing this? Or is there a New law or something that doesn't allow picture sending while in calls for some reason?
Just wanted to get some feedback to see what other people are experiencing.
Click to expand...
Click to collapse
Which app were you trying to send it through? And no, there is no new law that would stop this.
Is it possible you were on wifi when you were trying? From what I understand Verizon devices will not send picture messages over wifi, they have to use the network.
Stock LG messaging app, stock dialer. Rooted device and that's about it. I noticed I actually do not need mobile data on to send and receive picture messages normally (not in a call) so I typically leave it off when I don't need it for data.
My setup when I tried was WiFi on and connected to my home network, mobile data off, and phone call present. Would not allow me to send the picture. I'll try it with data on later and see if it works.
Didn't think it was a law, Which is good. May be that the data was off. And yes Verizon phones do not send pictures through WiFi they do need mobile data for Verizon services (text,MMS).
Well weird.. Called my voicemail and sent a picture message to myself and it went through both with data on and off.
Well I must have had another issue last night where it wasn't wanting to send. Weird thing is it sent after I hit try again and was off the phone.
Only thing I could think of is that the area I was at before typically gets less coverage (although still 4g).
So I'm confused but as long as it works I'll be happy!
Any solutions please update us
XXchocolatetouchXX said:
Stock LG messaging app, stock dialer. Rooted device and that's about it. I noticed I actually do not need mobile data on to send and receive picture messages normally (not in a call) so I typically leave it off when I don't need it for data.
My setup when I tried was WiFi on and connected to my home network, mobile data off, and phone call present. Would not allow me to send the picture. I'll try it with data on later and see if it works.
Didn't think it was a law, Which is good. May be that the data was off. And yes Verizon phones do not send pictures through WiFi they do need mobile data for Verizon services (text,MMS).
Click to expand...
Click to collapse
XXchocolatetouchXX said:
Well weird.. Called my voicemail and sent a picture message to myself and it went through both with data on and off.
Well I must have had another issue last night where it wasn't wanting to send. Weird thing is it sent after I hit try again and was off the phone.
Only thing I could think of is that the area I was at before typically gets less coverage (although still 4g).
So I'm confused but as long as it works I'll be happy!
Click to expand...
Click to collapse
shamiflavour said:
Any solutions please update us
Click to expand...
Click to collapse
I the solution was found. Apparently a fluke issue.
Yes, seems something else was the issue there. I figured it was the call because that was the main thing I was using the phone for. If I get anymore info on this I will share.
XXchocolatetouchXX said:
Yes, seems something else was the issue there. I figured it was the call because that was the main thing I was using the phone for. If I get anymore info on this I will share.
Click to expand...
Click to collapse
Thanks a lot for your sincere efforts...☺
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.