Related
I'm sure this has been covered, and I vaguely remember having this problem in the past, but my search-fu is failing me...
Suddenly, when on a call (I have my Kaiser configured to drop my data connection when making / receiving a call), my WiFi turns on and searches for an AP.
I turn it off, make another call, and the next thing I know it's on again and searching...
How do I configure my Kaiser so it won't turn on WiFi automatically?
Im having this very same issue! I think what is going on is the phone searching for data connection when a call cuts it off. What I mean is im using the phone on ATT so i can only use edge, so if i have lets say parlingo open using data and a call comes in it cuts off the connection thus the program switching on my wifi as an alterior method. Still very annoying and something i dont want happening..
I posted this in the general forum but got no replies. Is there any way to use direct push without it turning wifi on all the time? Every time I make a phone call or loose reception wifi switches itself on. It is extremely annoying. I am constantly turning it off and almost every time i take my phone out of my pocket wifi is back on. Does anyone else get this? Can I tell direct push to only use the cellular data connection? I know it is direct push because if I enable it the problem goes away. Please help!
Am I seriously the only one with this problem? Cause its drivin me nuts. When I turn wifi off, I want it to stay off. No suggestions?
push should automatically alternate between data and wifi. it gives wifi priority before data.
JKingDev said:
I posted this in the general forum but got no replies. Is there any way to use direct push without it turning wifi on all the time? Every time I make a phone call or loose reception wifi switches itself on. It is extremely annoying. I am constantly turning it off and almost every time i take my phone out of my pocket wifi is back on. Does anyone else get this? Can I tell direct push to only use the cellular data connection? I know it is direct push because if I enable it the problem goes away. Please help!
Click to expand...
Click to collapse
What what what? Your wifi turns on auto? Never heard such thing neither ever happened to me. Seems too odd since in the kaiser wifi only turns on when you activate via key combo or in the control panel! Don't u mean ur data conn is always switching on? Maybe it's cause of the rom you have!
uh use your imagination dude.
It automatically goes to wifi if it's on.
ChumleyEx, That's not the issue here.
The issue is that WiFi automatically turns on after a call, when it was OFF beforehand. JKingDev confused the issue in his OP.
The problem is not exclusive to the Kaiser either. My HTC Vox (WinMo 6.1 Standard) is doing the same thing.
Until reading this thread, I hadn't made the relationship between push activesync email and wifi being automatically turned on after a call. I still have yet to confirm that the issue exists without Push ActiveSync enabled.
One further peice of information - it only seems to be an issue after WiFi has been manually turned on at some stage of the phone's current power-on session.
i.e. If I reboot the phone and don't turn WiFi on manually, I can make/receive calls without Wifi turning on automatically.
Once I turn wifi on then off again, then make/receive a call, Wifi will automatically turn on after the call.
And it's very inconsistent as well, which makes this doubly frustrating. For example, I've just tried to replicate the issue using my examples above, and it's not happening now :-\
Perhaps it's only an issue after calls longer that 'x' seconds? Max call-time I tested was 13secs.
Phrak said:
Perhaps it's only an issue after calls longer that 'x' seconds? Max call-time I tested was 13secs.
Click to expand...
Click to collapse
Are you on EDGE or 3G?
On EDGE while in a call the data will be put on hold. That could mean that if your call is long enough the push connection will timeout, and it will try to use Wifi to maintain connection (as the goal of push is for it to be constantly connected)?
Just thinking out loud, I've never used push myself.
Hello,
I'm experiencing the same problem since I "update" the Touchflow 3D with a communications tab. Before that I didn't noticed thi.
Symptom are exactly from the post here upper.
* When I'm in a call after few seconds.
* I used Exchange ActiveSync
* Diamond last official ROM
* just added : http://forum.xda-developers.com/showthread.php?t=432528
Since them Wifi auto on and really anoying when I'm uing my bluetooth headset.
André
I get this issue with the stock orange UK 6.1 ROM.... any ideas yet?
Here's a classic problem I've been having:
I have wifi enabled at home, and it works great. I walk out to my car parked on the street, and from here my phone still sees my wifi network, but it has a very weak connection and basically can't transmit any data. I open Google Navigation to get directions to drive somewhere, and the phone just sits there trying to find directions, or connect to server, etc.
It would seem that whenever my phone can find a weak or public wifi (which requires a login-screen and does not actually "connect" to the internet), then I essentially get no data connection whatsoever. Isn't there supposed to be a function in the phone that will automatically switch over to 3G or whatever data network is available to fill in the gaps?
This is really annoying me, as Minneapolis has public wifi everywhere, which my phone thinks is "connected" when its really not, so basically its a coin flip as to whether my data connection will work when I'm driving.
Try turning off Wi-Fi?
Of course, I do turn off wifi and the problem is gone, but I seldom remember to do it on my first time. It's most apparent and annoying when I do a voice command or voice search while driving, and then it says "connection error" and I feel like chucking my phone out the window.
If I had true 4G and an unlimited data plan, I'd probably never even bother with toggling wifi on, but as it stands now, with a 200MB plan, I really need to keep wifi on whenever possible.
Is this a common occurrence with Captivate, or Android in general? I ask because this issue just came up yesterday, and I just got owned by an iPhone4 user. We both wondered if it was going to rain soon, so we both opened our browsers, and I was stuck looking at this stupid public wifi login screen, and was putzing around with wifi, when BAM, he just shows me his iPhone with fully loaded weather radar, etc. Hence I wanted to get this issue resolved now more than ever.
Not sure if the phone has this setting but windows 7 has an option to turn auto connect to open wifi spots off. So you gave to manually connect.
Sent from my GT-I9000 using XDA App
Hello,
I recently picked up an Urbane LTE to simply play around with. But my driving reason to get LTE was to pop a sim in and be able to use the watch without being tethered to my phone. But it seems like you can't do squat with the watch without a phone nearby except make a phone call and maybe receive some texts. Ok Google ceases to work when you lose Bluetooth connectivity to the phone.
Is this the way it is or am I missing something? Seems like all the apps. are pretty dumb too in that they need Android Wear in order to work right. The apps don't standalone at all. Maybe I came in with the wrong assumptions.
Thanks in advance!
jcaudill said:
Hello,
I recently picked up an Urbane LTE to simply play around with. But my driving reason to get LTE was to pop a sim in and be able to use the watch without being tethered to my phone. But it seems like you can't do squat with the watch without a phone nearby except make a phone call and maybe receive some texts. Ok Google ceases to work when you lose Bluetooth connectivity to the phone.
Is this the way it is or am I missing something? Seems like all the apps. are pretty dumb too in that they need Android Wear in order to work right. The apps don't standalone at all. Maybe I came in with the wrong assumptions.
Thanks in advance!
Click to expand...
Click to collapse
The Urbane 2 LTE isn't meant to be completely standalone on AW 1.5 (still waiting on 2.0), but you can pair to the phone through LTE data and do most of what you can through BT. When you leave the phone behind and turn on the SIM, are you paired to the phone (cloud icon with a line through it appears when not connected)? Which model of the watch are you using (W200A for AT&T, W200V for Verizon) and what service are you using on the watch's SIM?
mward1995 said:
The Urbane 2 LTE isn't meant to be completely standalone on AW 1.5 (still waiting on 2.0), but you can pair to the phone through LTE data and do most of what you can through BT. When you leave the phone behind and turn on the SIM, are you paired to the phone (cloud icon with a line through it appears when not connected)? Which model of the watch are you using (W200A for AT&T, W200V for Verizon) and what service are you using on the watch's SIM?
Click to expand...
Click to collapse
I have a W200A. I am using a full service T-Mobile SIM. You think that is part or the problem?
jcaudill said:
I have a W200A. I am using a full service T-Mobile SIM. You think that is part or the problem?
Click to expand...
Click to collapse
Sometimes it can be because the SIM/model watch don't match network bands but a full service T-Mobile SIM should work with the W200A. As long as the phone is on and connected to a network the watch should be able to pair through LTE or 3G data.
mward1995 said:
Sometimes it can be because the SIM/model watch don't match network bands but a full service T-Mobile SIM should work with the W200A. As long as the phone is on and connected to a network the watch should be able to pair through LTE or 3G data.
Click to expand...
Click to collapse
That's what I thought too. I'm not too sure where to to from here any suggestions? If at least I could hit the cloud through LTE then I'd be a lot more content.
jcaudill said:
That's what I thought too. I'm not too sure where to to from here any suggestions? If at least I could hit the cloud through LTE then I'd be a lot more content.
Click to expand...
Click to collapse
Do you see the cloud icon when bluetooth is off on the phone and cellular is turned on (and Wi-Fi off) in the watch?
mward1995 said:
Do you see the cloud icon when bluetooth is off on the phone and cellular is turned on (and Wi-Fi off) in the watch?
Click to expand...
Click to collapse
Yes indeed. I get the very unfriendly middle finger stricken-through cloud icon as if it's completely disconnected.
jcaudill said:
Yes indeed. I get the very unfriendly middle finger stricken-through cloud icon as if it's completely disconnected.
Click to expand...
Click to collapse
Ah ok. That's the problem then. You aren't paired for some reason. When I leave my phone behind and turn off bluetooth on the phone, I get the cloud also. However when I activate cellular on the watch the connection is made and I'm paired through cell data allowing me to do most things as I would on BT. I receive notifications for gmail, facebook, texts to the phone's number through messenger (and I can reply by voice) etc. I also forward my calls to the watch's number so I don't miss calls. Just need to figure where the hiccup is regarding the connection. I assume it is, but is 'Cloud sync' set to 'on' in the Android Wear app settings on the phone (under privacy and personal data)? Does pairing through Wi-Fi work at home when BT is off on the phone?
mward1995 said:
Ah ok. That's the problem then. You aren't paired for some reason. When I leave my phone behind and turn off bluetooth on the phone, I get the cloud also. However when I activate cellular on the watch the connection is made and I'm paired through cell data allowing me to do most things as I would on BT. I receive notifications for gmail, facebook, texts to the phone's number through messenger (and I can reply by voice) etc. I also forward my calls to the watch's number so I don't miss calls. Just need to figure where the hiccup is regarding the connection. I assume it is, but is 'Cloud sync' set to 'on' in the Android Wear app settings on the phone (under privacy and personal data)? Does pairing through Wi-Fi work at home when BT is off on the phone?
Click to expand...
Click to collapse
Ok I will try to pair it once more with my new phone. I have a feeling that my LTE might not be working right. I wish there was an easy way to confirm or deny that! I'll report back at least I know it's supposed to work! Thanks again.
You know - I wonder if I'm just being a dum-dum (insert picture of Gazoo here!)
I bet cloud sync only works when the phone is able to communicate with the cloud right? So if you shutoff all data services on the phone, of course the watch isn't going to work anymore. It's essentially the gateway between messages and the cloud. But I should be able to leave my phone on, walk away as far as I want and it continues to work right? That's the idea. I'm sitting here thinking the watch just works standalone and that really isn't the model I guess.
jcaudill said:
You know - I wonder if I'm just being a dum-dum (insert picture of Gazoo here!)
I bet cloud sync only works when the phone is able to communicate with the cloud right? So if you shutoff all data services on the phone, of course the watch isn't going to work anymore. It's essentially the gateway between messages and the cloud. But I should be able to leave my phone on, walk away as far as I want and it continues to work right? That's the idea. I'm sitting here thinking the watch just works standalone and that really isn't the model I guess.
Click to expand...
Click to collapse
Correct. The phone needs to be on and connected to a data source in order to pair through LTE/3G/Wi-Fi. Once paired through LTE, you can be miles away and still receive notifications etc.
First off, I can make outgoing calls 100% of the time, and never have any problem except a split-second delay (as expected with VOIP)
Receiving calls though......
First, wifi calling randomly turns off, with a note I find later about "wifi calling is not available at this location" ---- yes, I have poor reception, and I know wifi calling requires an always-active GPS signal so rain or clouds can kill it --- but it never turns back on once the storm/cloud/whatever is gone, it stays turned off until I manually turn it back on.
Second, even when it is turned on, I will randomly get no notification - no ring, no vibrate, the screen stays black, and no "miss call" notification, I just get told later that someone tried to call me and it went straight to voicemail.
Third, when it does register an incoming call, I will swipe to answer and the phone app will... kinda half-freeze... it acts like it's trying to answer the call, where the red end button appears, but all the other buttons are greyed out except message. It's in a strange limbo-like state of being answered and not... when this happens usually the other party will connect and can hear me, but whatever they say never reaches me.
Fourth, I answer the call, everything seems fine, I say hello and just hear my own voice echoing, and even though I answered the call, they never connect and end up on voicemail.
I know that WiFi calling is a "new technology" (even if we've been using VOIP for years....) and Sprint hasn't "ironed out the bugs" yet, but is there anything I can do to improve it?
I have tried doing a hard reset on the phone, updating PRL/settings/OS, changing the phone data mode from LTE to CDMA, sprint tech changed out my SIM card for a new one, airplane mode (which doesn't work because it turns off GPS)... none of it works and I still miss a good 60%+ of my calls... any other suggestions?
Ashton_Durkhun said:
First off, I can make outgoing calls 100% of the time, and never have any problem except a split-second delay (as expected with VOIP)
Receiving calls though......
First, wifi calling randomly turns off, with a note I find later about "wifi calling is not available at this location" ---- yes, I have poor reception, and I know wifi calling requires an always-active GPS signal so rain or clouds can kill it --- but it never turns back on once the storm/cloud/whatever is gone, it stays turned off until I manually turn it back on.
Second, even when it is turned on, I will randomly get no notification - no ring, no vibrate, the screen stays black, and no "miss call" notification, I just get told later that someone tried to call me and it went straight to voicemail.
Third, when it does register an incoming call, I will swipe to answer and the phone app will... kinda half-freeze... it acts like it's trying to answer the call, where the red end button appears, but all the other buttons are greyed out except message. It's in a strange limbo-like state of being answered and not... when this happens usually the other party will connect and can hear me, but whatever they say never reaches me.
Fourth, I answer the call, everything seems fine, I say hello and just hear my own voice echoing, and even though I answered the call, they never connect and end up on voicemail.
I know that WiFi calling is a "new technology" (even if we've been using VOIP for years....) and Sprint hasn't "ironed out the bugs" yet, but is there anything I can do to improve it?
I have tried doing a hard reset on the phone, updating PRL/settings/OS, changing the phone data mode from LTE to CDMA, sprint tech changed out my SIM card for a new one, airplane mode (which doesn't work because it turns off GPS)... none of it works and I still miss a good 60%+ of my calls... any other suggestions?
Click to expand...
Click to collapse
do u have a vpn active?
plus i dont think GPS has anything to do with "WIFI" calling.
as long as wifi is connected to a proper wifi network, that should be all you need.( other than if a VPN is activated or wifi network is congested/ to many AP ssids with overlapping channels, then it should work fine.)
I did before the hard reset (one-dot), I dont now. so it didn't seem to matter...
Ashton_Durkhun said:
First off, I can make outgoing calls 100% of the time, and never have any problem except a split-second delay (as expected with VOIP)
Receiving calls though......
First, wifi calling randomly turns off, with a note I find later about "wifi calling is not available at this location" ---- yes, I have poor reception, and I know wifi calling requires an always-active GPS signal so rain or clouds can kill it --- but it never turns back on once the storm/cloud/whatever is gone, it stays turned off until I manually turn it back on.
Second, even when it is turned on, I will randomly get no notification - no ring, no vibrate, the screen stays black, and no "miss call" notification, I just get told later that someone tried to call me and it went straight to voicemail.
Third, when it does register an incoming call, I will swipe to answer and the phone app will... kinda half-freeze... it acts like it's trying to answer the call, where the red end button appears, but all the other buttons are greyed out except message. It's in a strange limbo-like state of being answered and not... when this happens usually the other party will connect and can hear me, but whatever they say never reaches me.
Fourth, I answer the call, everything seems fine, I say hello and just hear my own voice echoing, and even though I answered the call, they never connect and end up on voicemail.
I know that WiFi calling is a "new technology" (even if we've been using VOIP for years....) and Sprint hasn't "ironed out the bugs" yet, but is there anything I can do to improve it?
I have tried doing a hard reset on the phone, updating PRL/settings/OS, changing the phone data mode from LTE to CDMA, sprint tech changed out my SIM card for a new one, airplane mode (which doesn't work because it turns off GPS)... none of it works and I still miss a good 60%+ of my calls... any other suggestions?
Click to expand...
Click to collapse
Oh sprint. I always had network connectivity issues with them. I wouldn't be surprised if this is something that is wrong on sprints end
bober10113 said:
plus i dont think GPS has anything to do with "WIFI" calling.
as long as wifi is connected to a proper wifi network, that should be all you need.( other than if a VPN is activated or wifi network is congested/ to many AP ssids with overlapping channels, then it should work fine.)
Click to expand...
Click to collapse
You have to have an active GPS signal for "e911 services" --- yes the app claims you can set your location manually, but doing so does nothing and as soon as my phone loses cell/GPS reception, wifi calling goes off and will NOT come back on till reception is restored (also I've used two of Sprints Femtocells and both of them required an active GPS for e911 so....)
Bober_is_a_troll said:
Oh sprint. I always had network connectivity issues with them. I wouldn't be surprised if this is something that is wrong on sprints end
Click to expand...
Click to collapse
yeah.... since about the start of this year my LTE speeds have gone down (though only in actual use! --- run speedtest and magically I have like 50mbps, even though I can't watch youtube even at 144p without it buffering and asking my phone "Alexa Next Track" returns an error about connectivity) Also my reception in my home has gotten worse in the last couple months --- for the last 17.5 years I've been able to make/receive calls on sprint over normal cellular without issue as long as it wasn't raining (yes, I've been with Sprint for almost long enough to raise a child.... they started out as the best carrier in my area, believe it or not), but now even though my phone reports 2 bars (out of like 8 or 10), I recieve almost no calls, and drop outgoing ones very frequently unless I switch to WiFi Calling.
So... yeah... I figured it was actually bad implementation on either Samsung or Sprint's part, but I was hoping there was something I could do to improve it....
Ashton_Durkhun said:
You have to have an active GPS signal for "e911 services" --- yes the app claims you can set your location manually, but doing so does nothing and as soon as my phone loses cell/GPS reception, wifi calling goes off and will NOT come back on till reception is restored (also I've used two of Sprints Femtocells and both of them required an active GPS for e911 so....)
yeah.... since about the start of this year my LTE speeds have gone down (though only in actual use! --- run speedtest and magically I have like 50mbps, even though I can't watch youtube even at 144p without it buffering and asking my phone "Alexa Next Track" returns an error about connectivity) Also my reception in my home has gotten worse in the last couple months --- for the last 17.5 years I've been able to make/receive calls on sprint over normal cellular without issue as long as it wasn't raining (yes, I've been with Sprint for almost long enough to raise a child.... they started out as the best carrier in my area, believe it or not), but now even though my phone reports 2 bars (out of like 8 or 10), I recieve almost no calls, and drop outgoing ones very frequently unless I switch to WiFi Calling.
So... yeah... I figured it was actually bad implementation on either Samsung or Sprint's part, but I was hoping there was something I could do to improve it....
Click to expand...
Click to collapse
Switch telco's... Sprint dropped the ball. They invested in. Winax , then LTE took off. They've been behind ever since