Related
I've been having a problem with my Fuze randomly not being able to receive text messages or calls.
Sometimes when people call, they say it rings twice and goes to voice mail. All the while, I never hear anything or get a notification. This happened once after I texted someone to call me when they get a chance. They tried 3 times and then texted me back to say that they were getting sent to voice mail. I didn't get notification for either until after I called this person myself 20 minutes later. Right when the call connected, I got notification of a new text message.
Another time, somebody was calling me for 3 days. I didn't know he was trying to reach me until he finally left a voice mail and I got the notification for that (no missed call notifications).
I called AT&T and their tech support did some tests (called my phone) but since it isn't reproducible 100% of the time, they couldn't offer any explanation.
This isn't a bars/signal issue either as this is occurring in the same spot where my Tilt would always receive calls fine.
Has anyone else seen this?
I had the exact same problem with my Sprint Touch Pro & ended my contract early & switched to at&t. Hopefully it's not a fundamental hardware problem.
8notime said:
I had the exact same problem with my Sprint Touch Pro & ended my contract early & switched to at&t. Hopefully it's not a fundamental hardware problem.
Click to expand...
Click to collapse
Did you get a Fuze when you switched? Has that worked better for you? I'm still within my 30 days, so I'm debating exchanging it or just returning it and giving up.
I'm having the same problem. I did a quick search and found this;
This AT&T Forum Post
I tried the workaround and haven't had a chance to really test it yet though. I also noticed a few other settings in there that might have accounted for it.
One selection inside the phone settings had to do with whether calls went to voicemail when you're "Unavailable" or "Busy." I'm not familiar enough with the phone to know when it might tag me as either one so I unchecked both and I'm going to recreate my missed calls this morning.
Someone called after the phone had been sitting on my desk all night so I thought maybe it thought I was "Unavailable" due to inactivity (I dunno, I'm winging it) so I'm letting it idle for a few hours and getting a call later to see what happens.
Incidentally I have the exact same problem, no call coming in, but then I get the voicemail message after I try calling someone.
Unless I'm misunderstanding your point, "Unavailable" just means that your phone is switched off or out of signal, and "Busy" means you are already in a call. It's nothing to do with the behaviour or features of the phone.
Cheers,
Steve.
Yeah, I'm wondering if the phone is becoming "Unavailable" for some other reason than me being out of range. I have full bars in the house and that's where this all happened.
I've noticed, too, that I didn't get any email (I have it set to check every hour, even hit send/receive after someone told me they sent me something and it still didn't find it until I sent a second email to myself from another address)
Again, I don't know much about phones but it almost seems like the phone has bars but drops off the network for accepting calls/messages until you do something to activate the system again... or something. I dunno, just speculating.
Last week I went in and exchanged my Fuze for a new one since it was still within the 30 days. Up until tonight, I thought the problem was fixed. I was chatting with my wife over IM and she told me that she tried to call but that it just went to voicemail. I asked her to call back and leave a voicemail to see if it would notify me. I also asked her to send me a text. I didn't get notification for either. I checked my data connection by starting up Opera and going to a few sites. So I know that I had a verifiable connection to the network. I called my voicemail and checked the message I knew that she had left. Only after I made the call did I get notifications for the text messages I had missed. I never got any notification for the voicemail or missed calls.
Unfortunately, it seems this is a problem that isn't related to individual hardware as this is my 2nd phone with the same problem. I've also replaced my SIM card since a salesperson at an AT&T store suggested that it might help. I'm running the stock AT&T ROM minus the bloat, so it's not a custom ROM issue either. At this point, I'm not sure what I should do.
The only other thing I can think of that makes me unique is that I currently reside in Washington state but my number is one that I had ported from California. Is there anything about you're (skyau) situation that makes you unique?
Well the same thing happened again tonight. I received text messages 10 minutes late and I didn't get a voicemail notification until I initiated a call. As much as this sucks, I'm hoping it will stay this consistent so that I can have tech support replicate the problem and then try and fix it.
You may have a problem with your phone number. I'd try changing it.
Have you had experience with a problem like this? Is the phone number really the issue?
If that's what the problem actually is, I'm willing to get a new number. But I don't want to change it just to check and see if that fixes it.
same problem! Really pissing me off I just lost a important job because of this issue a few moments ago! Is everyone running a stock rom? I tested a few, now back to stock no apps nothing trying to find this gremlin WTF!
I'm running stock ROM without the bloat.
I exchanged my Fuze (I'm now on my 3rd) on Saturday and changed my phone number yesterday. I'm waiting to see if the issue happens again. If it does, I'll probably do stock ROM, all the bloat, no apps. If there are still problems, I'll probably try different ROMs.
I was able to get AT&T tech support on the line when the problem was occurring luckily. We went through his battery of tests and he verified that there was a problem. It would seem that the phone forgets/loses it's connection to the towers/network. Notifications (calls, texts, voicemails) aren't received until after the phone remembers/reconnects to the network. It remembers/reconnects when you initiate a call or send a text (essentially require the phone to use the network).
The tech told me that as far as he could tell, it was a hardware issue and that I should exchange my phone. So I'm on number 3 now and hoping for the best. I changed my number because I've been in a different state for 2 years and I had no ties to previous area code. So I figured now was as good a time as any to get a full fresh start (phone/number/SIM).
That sucks about losing the job.
Bump, I just realized a few moments ago that my phone rings once and then it says missed call, i always assumed they called me and then hung up after one ring in case i was in class or i was busy so that i could call them back. this is not the case? Also a few cases a call will drop every now a then... is this due to the radio rom i flashed? typical symptoms of a incompatible radio for a specific location? I'm using the .25.35 blackstone radio in ithaca, ny.
Having the same issue. Phone is asleep, then alerts me to a VM. Missed call doesn't show up in missed call list.
Really pissing me off and I think is responsible for my issues with Slide2Answer somehow.
The only time I have missed calls is because of MSVC. If someone calls and it is private or unknown, it will not ring. If it is somebody in my phone book or who doesn't have a private number, the phone will ring.
So I turned MSVC off and the private callers and the unknown callers will ring in.
it happens to me sometimes as well sometimes the d pad area will flash but i cant answer and it wont appear on screen then it wont say missed call.
sometimes if i try to hit the dial button it will also drop connection and instantly pick it up again
annoying but not a huge problem for me
and of course not on stock rom
Hey,
I looked around the windows phone forums and didn't find a similar question. Was going to post this in Lumia 800 Accessories but figure I'll get a better response here (and it is windows phone generic).
Does anyone know a Bluetooth watch that will work fine with Windows Phone? I'm looking for something which will simply give me a subtle vibration anytime I get a phone call, text message, e-mail or any other notification.
I've been looking at these:
http://www.ebay.co.uk/itm/Bluetooth...e_Phones_Bluetooth_Acc_ET&hash=item25739e79d5
Not really a watch, more a bracelet but it vibrates when the phone has a call. It would be perfect for me but it doesn't look like it would notify you of any other notifications such as texts or emails. Phone calls and Texts would be ideal, I'm not really fussed about anything else.
I just want something small and simple which will vibrate/alert me when I receive something, allowing me to leave my phone on silent in my pocket when I'm in work but still alert me when I receive something.
Anyone here using tmo with their S2? when in stand alone are you able to take/make calls and have them look like they're coming from your cell number?
(trying to figure out if tmo screwed my setup)
if you are connected via bluetooth, your calls made from the watch should look like your cell phone number
if you are in "stand alone" mode, with no phone connected, it should look like your watch phone number is making the call
how do text messages from your cell get to your s2 if in stand alone? (just on the s2 number?)
they dont get forwarded to your watch when in stand alone if the text is to your cell phone number, since your watch has a different phone number than your cell..
tmo mislead me then. good times. they told me in stand alone all my calls and texts would use the same number as my ph. thanks for the info.
If you have remote connection on, they do forward.
where do you enable that?
thanks
On your gear, go to settings-call-auto forward I believe will do it
I believe that just forwards calls, NOT texts..
I have mine linked with a moto x pure. Although it doesn't save them in the messaging app, I can reply and read, and get texts remotely
on my nexus 6. no matter what settings I use, I do NOT get texts forwarded to my watch; everything else, like emails, facebook, etc does get forwarded, but no texts..
Mine works in standalone with watch number and with cell number when connected with Bluetooth. When remote connected all calls forward after 4 rings on my cell and all text messages are forwarded. I had to call t-mobile to get it working properly. They said the had to change the way the auto forwarding was setup on the network. I would suggest calling them if yours doesn't function as mine does
Sent from my SM-N920T using Tapatalk
thats a good idea, since mine doesnt work that way now..
thanks:good::good:
wase4711 said:
I believe that just forwards calls, NOT texts..
Click to expand...
Click to collapse
On a Samsung Note 5 my text get forwarded to me when I am in stand alone mode. My phone is on Verizon, my Gear S2 is on T-Mobile. When I leave my phone at home (phone is on), my text are forwarded. If I turn the phone off the text do not come through. When I leave my phone on and am using the Gear S2 in standalone (physically separated from my phone), I get all notifications, calls, text, social media, etc...
good news/bad news.
I've got everything working as I'd hoped. I had to trade in my LG G3 and now have a samsung phone. I see more apps in the gear store, and I noticed when I reset the watch, I now have different options in the call forwarding area than i had before. I honestly believe that the watch was made to work with samsung gear only...and any other handsets are an afterthought.
Also, it works on it's own with autoconnect. I turn off bluetooth, and the watch goes to stand alone, and once remotely connected tells the handset to fwd calls/sms to it.
I am straying here from the original issue but I think this is related. I have a Moto X Pure (MXP) on AT&T. I have the AT&T Gear S2 (GS2) LTE. I am going to be verbose with this. Both have unique SIM's, IMEI's, phone numbers. I have successfully forwarded the MXP# to the SG2# when connected over the LTE network. MXP will ring 4-6 times, then roll over and ring to SG2 2-4 times. Voicemail goes to SG2.
I have used the watch's settings and S. Gear app settings to forward/unforward (so I thought). I have recently noticed I am not getting voicemails on my phone (doesn't happen much anyways as I don't get many calls I don't pick up). Odd part is that more than once, the voicemail on the GS2 only pops up when I disconnect bluetooth connection between devices. I have figured out this is likely tied to when the GS2 is connected via bluetooth to the MXP, it acts in headset/handsfree mode and controls my MXP dailer.
When I go into S. Gear app, under call forwarding, I see "Turn Off" as "Deactivated XX:XX". When I push Turn On, I see "a request has been made..." on the MXP and "Request has been made..." on the GS2. Toast on MXP after success is "Call Forwarding, Registration was successful". Turn On shows "Activated XX:XX". Then I push Turn Off, and see "A request has been made...." on the MXP, then a "Call forwarding, Connection problem or invalid MMI Code" on the MXP, and then a "A request has been made..." on the GS2. No error on the watch. Funny is that under Turn Off, it shows "Deactivated XX:XX" again.
Calls first go to MXP, then to GS2 and end up in GS2 voicemail. When to MXP Dailer settings, Calls, Call Forwarding. Interestingly, 3 of last 4 options for call forward show forwarding to the GS2. When I click on any of the 3 of the 4 forwarding, I can push Turn Off. Error toast shows up as "Your operator doesn't support disabling call forwarding when your phone is busy". What constitutes "busy"?...and why can't I turn this off?
---------- Post added at 06:38 PM ---------- Previous post was at 06:24 PM ----------
UPDATE: I went to the Call Forwarding wiki and used some of the codes to help. ##67#, ##61#, ##62# were used successfully. All is back to normal. I can pick up via the watch, transfer to the phone, reject as needed. Voicemail goes to the MXP as expected. Network really wouldn't let go of the number. I am sure there is a good reason for that but don't get why.
I have a Galaxy S7 edge on Tmobile.
1) Is there anyway to decrease the 30 seconds to a minute it takes for forwarding to turn on after Bluetooth disconnect?
2) When forwarding, My S7 will still ring a bunch of times before the call is forwarded. Anyway for the call to go directly to the Gear S3?
kronium said:
I have a Galaxy S7 edge on Tmobile.
1) Is there anyway to decrease the 30 seconds to a minute it takes for forwarding to turn on after Bluetooth disconnect?
2) When forwarding, My S7 will still ring a bunch of times before the call is forwarded. Anyway for the call to go directly to the Gear S3?
Click to expand...
Click to collapse
I have the same setup. I don't believe there is a way to change this at this point. There will be a delay
Gratchf703 said:
I have the same setup. I don't believe there is a way to change this at this point. There will be a delay
Click to expand...
Click to collapse
Yikes, it makes it virtually unusable as the caller has to wait almost ten rings before you pick up on your watch. Most people would hang up by then!
I'll have to look into Google Voice to see if there's a quicker solution.
kronium said:
Yikes, it makes it virtually unusable as the caller has to wait almost ten rings before you pick up on your watch. Most people would hang up by then!
I'll have to look into Google Voice to see if there's a quicker solution.
Click to expand...
Click to collapse
I have a solution that uses a 3rd party program. It is a program called "Automagic" for your android phone. If you are familiar with "Tasker" it is similar. Automagic runs in the background on my phone. I have 2 "Flows" set up in the program. The 1st one looks at the BT connection between my phone and the S3. As soon as the connection is broken (I walk away from my phone), it automatically has the phone dial call forwarding and turns it on. I have it set to dial the number for instant call forwarding so all calls to my phone are instantly forwarded to the watch number (there are usually 2 types of call forwarding on the different carriers, one for instant transfer of all calls, and another for allowing the 1st number to ring a few times before forwarding). A caller never knows they are calling my watch. The first ring happens instantly on my watch. If I call someone from the watch they will see it as coming from my watch number (numbersync doesn't do this)
I have the 2nd "Flow set up to watch for BT re-connection with my watch (when I walk back within BT range of the phone). It then has the phone automatically dial to turn off Call Forwarding.
Check with your carrier to see what numbers need to be dialed to turn on and off call forwarding. Also remember there are usually 2 types of forward, an instant, and a delayed. Post back in these forums if you try Automagic. I can share the "Flows" I set up to work with call forwarding. There is a free version of Automagic that allows you to have a couple flows. I ended up buing it since it worked so well and I wanted to support a developer.
ScottyKnox said:
I have a solution that uses a 3rd party program. It is a program called "Automagic" for your android phone. If you are familiar with "Tasker" it is similar. Automagic runs in the background on my phone. I have 2 "Flows" set up in the program. The 1st one looks at the BT connection between my phone and the S3. As soon as the connection is broken (I walk away from my phone), it automatically has the phone dial call forwarding and turns it on. I have it set to dial the number for instant call forwarding so all calls to my phone are instantly forwarded to the watch number (there are usually 2 types of call forwarding on the different carriers, one for instant transfer of all calls, and another for allowing the 1st number to ring a few times before forwarding). A caller never knows they are calling my watch. The first ring happens instantly on my watch. If I call someone from the watch they will see it as coming from my watch number (numbersync doesn't do this)
I have the 2nd "Flow set up to watch for BT re-connection with my watch (when I walk back within BT range of the phone). It then has the phone automatically dial to turn off Call Forwarding.
Check with your carrier to see what numbers need to be dialed to turn on and off call forwarding. Also remember there are usually 2 types of forward, an instant, and a delayed. Post back in these forums if you try Automagic. I can share the "Flows" I set up to work with call forwarding. There is a free version of Automagic that allows you to have a couple flows. I ended up buing it since it worked so well and I wanted to support a developer.
Click to expand...
Click to collapse
Hey, thanks so much for writing that up. I may check it out in the future. I called T-Mobile up and they reduced the 30 second forwarding lag to 5 seconds on the their end. That was the lowest they can go, but I'm able to answer the Gear by the 3rd ring now, and it only rings once on the phone.
kronium said:
Hey, thanks so much for writing that up. I may check it out in the future. I called T-Mobile up and they reduced the 30 second forwarding lag to 5 seconds on the their end. That was the lowest they can go, but I'm able to answer the Gear by the 3rd ring now, and it only rings once on the phone.
Click to expand...
Click to collapse
I didn't know you could have T-Mobile adjust that, thanks for the info. I may also try the 5 second delay.
Got mine (LTE through TMob) a couple of days ago and immediately started with problems. I have a separate watch line with an S7 Edge. Essentially I can send/receive text in the stand alone mode but can not call out or receive. (Can on BT) Had the tech guys play with it (they thought it was a line issue) and they put a ticket in. That might get it working in a week. I thought I could bypass the problem with the line using DIGITS and my cell but nope. Turns out (according to the DIGITS guru) its a sim card problem so they are exchanging the watch. Not an impressive first start but I'm hopeful it'll get better. Hopefully...
Everything BT seems to work but its only been 2 days. I still need to check all the stand alone things when I get the replacement. And, of course, stand alone was the point of the watch.
Also make sure it works in remote connect mode, which is more useful than standalone mode.
How does remote connect work? Wifi?
The connection mode is shown by pulling down on the watchface. It will say "standalone", "connected via BT", or "remotely connected via carrier".
In remote connection mode, the watch doesn't communicate with the phone. Only calls and messages directly to the watch's number are transmitted. No notifications (ie. email, missed calls, Hangouts) from the phone are passed through. In remote connection mode, the watch communicates via it's LTE radio to the phone whether it be in different room or a different state. This allows all notifications to be passed through.
I keep WiFi turned off, it seems (inadequately) redundant for an LTE watch.
And the difference between that and Stand Alone is what?
afblangley said:
In remote connection mode, the watch doesn't communicate with the phone. Only calls and messages directly to the watch's number are transmitted. No notifications (ie. email, missed calls, Hangouts) from the phone are passed through.
Click to expand...
Click to collapse
I made a typo. What I meant to say is that in standalone mode the watch doesn't communicate with the phone.
afblangley said:
I made a typo. What I meant to say is that in standalone mode the watch doesn't communicate with the phone.
Click to expand...
Click to collapse
AHHHHH... That makes more sense. I'm going to use DIGITS. Do you know how that impacts? Or if it does?
rogerperk said:
AHHHHH... That makes more sense. I'm going to use DIGITS. Do you know how that impacts? Or if it does?
Click to expand...
Click to collapse
Nope, sorry. I use Google Voice, so I don't have first hand experience with Digits.
afblangley said:
Nope, sorry. I use Google Voice, so I don't have first hand experience with Digits.
Click to expand...
Click to collapse
How does Google voice work with t-mobile
Sent from my SM-N950U using Xparent Purple Tapatalk 2
cherylbaker said:
How does Google voice work with t-mobile
Click to expand...
Click to collapse
Google Voice for the most part, is carrier ignostic. Calls to a GV number can be forwarded to any of several landlines, cell lines, or digital lines. Outgoing caller ID is a bit trickier and device dependent. Messages can be handled through the messaging app or Hangouts.
In my setup, since my public number is under Google's custodianship, carrier assigned numbers are irrelevant/disposable. My watch, phones, and tablets each have their own carrier number, GV is configured to forward calls to each of these numbers, and they ring simultaneously and independently. Ditto with messages. The carrier has no input in this process. The Gear is also ignorant of this. I don't need to use it's call forwarding setting.
I don't doubt that T-Mobile, AT&T, and Verizon will eventually get all the kinks worked out of their number sharing system. But Google has been at it for a few years and offers more features, flexibility, and gives power back to the user.
So here's what we got after 5 days:
With my second watch in hand Im informed that the tMob engineers have decided the watch os bad and needs to go back to Samsung. After explaining that the odds against 2 bad watches were pretty small and demanding to be escalated I got a good manager who agreed. The watch is fine. After some digging she decided the problem was that the line is screwed up on the back end and won't connect voice. Problem is she has no idea why or how to fix it. So I'm waiting for their "engineers" to look at it again with her cracking the whip. Bottom line for me is if I can't get a stand alone watch I'm not interested and expect a full refund AND for them to not market what they can't provide. We'll see.
If the line is messed up, why can't they just start from scratch and assign the watch a new number? Then setup the watch without a phone to make sure it works. This is true standalone. If that works, then the problem is with Digits, not the watch or the line.
afblangley said:
Google Voice for the most part, is carrier ignostic. Calls to a GV number can be forwarded to any of several landlines, cell lines, or digital lines. Outgoing caller ID is a bit trickier and device dependent. Messages can be handled through the messaging app or Hangouts.
In my setup, since my public number is under Google's custodianship, carrier assigned numbers are irrelevant/disposable. My watch, phones, and tablets each have their own carrier number, GV is configured to forward calls to each of these numbers, and they ring simultaneously and independently. Ditto with messages. The carrier has no input in this process. The Gear is also ignorant of this. I don't need to use it's call forwarding setting.
I don't doubt that T-Mobile, AT&T, and Verizon will eventually get all the kinks worked out of their number sharing system. But Google has been at it for a few years and offers more features, flexibility, and gives power back to the user.
Click to expand...
Click to collapse
Well THAT certainly cleared up the question...
REALLY PISSED OFF!! Over a week now and TMob STILL can't fix whatever THEIR problem is with getting this watch to use voice! They were really happy to take my money though! SO PISSED!!
So today it actually.worked! With the phone off!
Then it stopped.
Wrote the CEO of TMob and got an answer in 2 days. Seems not all of their networks supports Voice-over-LTG on 4G lines so it doesn't work everywhere (or something like that). Like where I am. They are hoping the Tizen 3.0 will correct that so the watch accepts a.lower quality line but not sure. Outstanding...
UPDATE 15 Oct - if I ran the watch as truly stand alone it would work. By using DIGITS it only uses 3G, which my area does not have. More info.