Related
Hi - ive tried looking through the threads but cant find anything, so apologies if im repeating something all ready asked..
Ive been noticing on recent phone bills that im getting charged for gprs calls that i definatly havnt been making but my phone company insists that i have. After further investigating, ive seen that if im using wifi, and the phone turns to standby, when it switches back on gprs has been activated and is running underneath wifi.. and this is where (i think) my call charges have been coming from...( i hope that makes sense!)
Is this a common problem with the stellar/kaiser/tilt or just a problem with this individual unit - also, if it is a common problem is there anyway in which i can stop it happening?
I can understand where it is coming from.
When you go into standby (ie turn off the screen), the phone turns WiFi off to save battery. This makes sense, but imho WM is still too stupid to understand the concept of money. Result is that when it tries to continue doing whatever it was doing it will open a new connection and it's first choice is the GPRS/HSDPA connection.
As far as I am aware, the options to stop this from happening again are....
1) Stop WiFi from turning itself off when the phone goes into standby. I'd do this using KaiserTweak - the Option is under "Data -> Wifi standby mode"
2) Disable the GPRS connections so it can't connect. One way is to remove the password so it asks before it connects. There's also a tool on here somewhere that allows you to quickly enable and disable connections. Here looked promising, posts a link to modaco
Hope that helps.
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?
Have you guys have the same problem?tryed all the radios on the market..they stream perfectly on wifi ,but when i lock the screen it just stops streaming.If i turn the screen back starts as normal.Any idea how to get over this?
No problem for me with lastFM.
This should work ... but it doesn't
Just in case you haven't tried - in the settings menu, Wireless and Networks, Wi-Fi settings, then press menu again and find 'Advanced'. Here lives 'Wi Fi sleep policy'. It looks promising, the obvious move is to set this to 'Never'.
But it doesn't solve the problem. Like you I'm finding that it is a problem with all radio streamers, some worse than others. If I turn wireless off and use 3G its fine.
Thanks for posting the issue. I thought I was the only one.
No problems with TuneWiki over WiFi and 3G...
i find that even if you set the wifi never to sleep it still does. i frequently use aftp to transfer movies and stuff to my phone over my lan, so ill set it to transfer like 3 gigs of stuff and go to bed, even though its set never to sleep the socket still gets closed at some point at night. so id say your problem lies with wifi sleeping.
also some online radios stop automatically after a certain amount of time incase you arent listening anymore to save bandwithd
Maybe its in the app settings. You didnt specify which app it was also...
This might help
When you connect Wi-Fi make sure to turn off your cellular network. N1 has this weird problem where in as soon as screen is off, it drops the wi-fi connection and goes on to cellular network.
So if you switch off ur cellular network it maintains its Wi-Fi connection even when the screen is off.
SiNJiN76 said:
Maybe its in the app settings. You didnt specify which app it was also...
Click to expand...
Click to collapse
i use mainly "AOnline radio" but i have tryed pretty much all from the market and all do the same. trying with the settings now..post if any change.
edit:yea still stops...strange try with gsm off and still same thing...is it there any solution to get over this thing?i just liten now with the screen on) eats the battery..it's ok but why not better?
The Nexus one activates some kind of energy saving mode as soon as you turn off the screen. This makes the WiFi connection very laggy, though stable for me. This is independent of the WiFi sleep policy. There's a bug report because of this for Sipdroid and I've also seen this issue while being connected to the phone via SSH. The connection is just fine as long as the screen is on, but if it's off, there's about 1 second delay.
However, I never had the problem you describe. Droidlive, for example, works just fine.
robert-qfh said:
The Nexus one activates some kind of energy saving mode as soon as you turn off the screen. This makes the WiFi connection very laggy, though stable for me. This is independent of the WiFi sleep policy. There's a bug report because of this for Sipdroid and I've also seen this issue while being connected to the phone via SSH. The connection is just fine as long as the screen is on, but if it's off, there's about 1 second delay.
However, I never had the problem you describe. Droidlive, for example, works just fine.
Click to expand...
Click to collapse
i will check droidlive myself right now...thank you for explinations..is there a way to talk with cyan and maybe he could overpass that wifi sleepy thing.
edit: also noticed if you ahve a download or something and turn the screen off goes very slow..so this problem i think really have a priority to be solved.
edit2:still stops...what would be the thing?wifi priority changed.do you have any type of settings?full app?
I'm listening to a ShoutCast stream with AOnline right now, using WiFi, screen is off. Works perfectly. Do you see this problem with other access points, too?
SLightworkaround....
If you can keep it plugged in...set the SCREEEN TO NEVER SLEEP...under settings>>>applications>>>DEVELOPMENT>>>STAY AWAKE... hope that helps!
robert-qfh said:
The Nexus one activates some kind of energy saving mode as soon as you turn off the screen. This makes the WiFi connection very laggy, though stable for me. This is independent of the WiFi sleep policy. There's a bug report because of this for Sipdroid and I've also seen this issue while being connected to the phone via SSH. The connection is just fine as long as the screen is on, but if it's off, there's about 1 second delay.
However, I never had the problem you describe. Droidlive, for example, works just fine.
Click to expand...
Click to collapse
This is the problem yes... Just try to ping your N1 while turning the screen off/on... Ping jumps up as soon as the screen is turned off...
For me Streams stop when I have a weak signal to begin with, which does not get better when turning the screen off
"KeepScreen" might help...
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
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