Related
When wifi and wifi-calling are enabled, it disconnects from the tmo network.. Great.. no problemo. I don't want it connected to the tmo network at the same time.
But.. when I lose the wifi.. i.e. service is interrupted, I leave the area, etc., then wifi-calling is stuck "ON" and I cannot return to the tmo network because the app is trying to find the wi-fi connection. This causes all voice/data to be dead.
I have tried killing the wifi-calling app via ATK, it won't shut down. I tried to FC it, no go. I tried to reboot the phone.. no go. I tried to kill it via Watchdog.. no go.
So basically, if I forget to shut off the app b4 I leave my wifi area, I'm screwed and dead in the water. Or, if the wifi connection is lost (i.e. service interruption), I'm screwed.
The only way wifi-calling will display the on/off button is when it has a wifi connection.. I know, I know.. I must force myself to remember to shut the stupid app off before leaving the local network.. but I forget at times.
I have only found 1 work around, and I'm hoping someone else can chime in on this. I'd like to see if there is an easier way around this.. It can be fixed via freezing the app. Then the tmo network kicks in. As soon as the app is unfrozen, it goes back to searching out wifi and disabling all voice/data.. until I get a wifi connection.
Thoughts?
can someone test this to see if they get the same results?
Mine switches as it should when I leave a wifi area.
GideonX said:
Mine switches as it should when I leave a wifi area.
Click to expand...
Click to collapse
Seriously? You have wifi calling and wifi enabled. You shut off wifi and it automatically switches off wifi calling?
that's messed up. If I do that, I'm w/o service. Guess I'll reinstall the app..
GideonX said:
Mine switches as it should when I leave a wifi area.
Click to expand...
Click to collapse
Thanks!!! I have discussed this on the forums a bunch of times in misc. conversations and no one has said "Hey, that's not the case for mine." I thought it was a glitch with the app.
R&R'd the app.. good to go. Thanks so much.. It's been like this since I took it out of the box.
Hey there,
I'm having a weird issue with my stock Nexus S. I've tried a few custom roms, but after realizing that I was better off with stock, I flashed stock again... Now, I've noticed that sometimes, with the WiFi off, I would receive emails and Google+ notifications! It turns out that my wifi is turning on and off, and I don't know how!
I don't have, to my knowledge, installed a program that controls wifi(if you want, I can post my list of apps).
So, what's happening here? Anyone has any idea?
Thanks
Ditto here
strung said:
Ditto here
Click to expand...
Click to collapse
You have the same issue? Can you post your list of installed apps? I seriously don't know what's going on!
This may seem really obvious - but have you double-checked that those notifications aren't coming in via your mobile network?
If you have Juice Defender (or something similar) installed, that might also be responsible for switching on your wifi periodically.
RGX521 said:
This may seem really obvious - but have you double-checked that those notifications aren't coming in via your mobile network?
If you have Juice Defender (or something similar) installed, that might also be responsible for switching on your wifi periodically.
Click to expand...
Click to collapse
Nothing like that... I was just activating my alarm clock for tomorrow and the wifi came on, out of thin air! It shutdown in less than a second, too! And I did absolutely nothing!
Also, I don't have any app like Juice Defender
Ok, so I've flashed the stock rom,locked the bootloader, etc, and I thought I had solved the problem. I didn't, the thing keeps turning on and off!!
I'm seriously thinking about sending it for repairs
you could send it in to samsung or install some newer 2.3.5 kernels which seemed to solve any wifi issues i may have had. Android 2.3.5 made some changes to wifi signal strenght.
dinuvali said:
you could send it in to samsung or install some newer 2.3.5 kernels which seemed to solve any wifi issues i may have had. Android 2.3.5 made some changes to wifi signal strenght.
Click to expand...
Click to collapse
I have stock, and it's the regular nexus S, not the 4G one (so I haven't received 2.3.5 yet).
I'll try installing the 2.3.5 kernels and report back
check your advanced wifi settings.
by default they are set to turn wifi off when screen is off. so even if you have wifi on it will turn off when screen is off automatically.
menu>settings>wireless and network settings>wi-fi settings>menu(softkey)>advanced>wifi sleep policy>check the "never" radio button.
thedudejdog said:
check your advanced wifi settings.
by default they are set to turn wifi off when screen is off. so even if you have wifi on it will turn off when screen is off automatically.
menu>settings>wireless and network settings>wi-fi settings>menu(softkey)>advanced>wifi sleep policy>check the "never" radio button.
Click to expand...
Click to collapse
I wish it were that simple... I've the wifi sleep policy set to never since I can remember. I only turn on wifi when I need it
I have a droid that I am about to put in a drawer. Its fully functional. Is it possible to modify this droid so that it only uses wifi? I'd like it modified so that my young son cannot make phone calls using minutes and verizon can't track, but he can still get to the market using my wifi at to play games. Is something like this possible? A possible Droid version of Ipod touch??
benjr06 said:
I have a droid that I am about to put in a drawer. Its fully functional. Is it possible to modify this droid so that it only uses wifi? I'd like it modified so that my young son cannot make phone calls using minutes and verizon can't track, but he can still get to the market using my wifi at to play games. Is something like this possible? A possible Droid version of Ipod touch??
Click to expand...
Click to collapse
If the phone isn't active on any line, then yes. If he tries to dial out he'll just get an error message.
You can put it in airplane mode as well.
lowandbehold said:
You can put it in airplane mode as well.
Click to expand...
Click to collapse
Airplane mode disables wifi...
Sent from my HTC Wildfire using XDA App
OllieArmageddon said:
Airplane mode disables wifi...
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
WIFI works in Airplans on "some" phones, worked on my MT4G, MT3GS, and on newer phones. I'm not sure if that's a function of the OS version, or the phone type. It may be a feature implemented later on.
I tried to access my wifi from this OG droid in airplane mode and it doesn't work. Perhaps there are developers here who could think of a way to do this?
Try this.
As far as I know, you can enable wifi while on Airplane Mode, no matter the device you hold.
I am aware that when you turn on airplane mode with WiFi on, it turns it off.
But you should be able to turn it on after engaging airplane mode.
Also mentioned before, as long as the phone is deactivated
The only phone calls that could be successful are 911 and customer care;
Used to talk to a rep. in order to re-activate your device.
I use two devices (Samsung Vibrant, Moto Droid X) that are not in service with airplane mode on;
It will save battery by turning off the CDMA Radio completely, otherwise the radios will constantly be communicating with the tower.
Keep in mind, this does not matter if the phone is in service or not, If its ON,
its trading packets with the tower.
Thanks!
-Masterfuel
You could also delete Phone.apk lmao. I can't believe I didn't think of that.
I would also say to just have the phone deactivated.
Just make sure he doesn't dial 911
masterfuel said:
As far as I know, you can enable wifi while on Airplane Mode, no matter the device you hold.
...
It will save battery by turning off the CDMA Radio completely, otherwise the radios will constantly be communicating with the tower.
...
Thanks!
-Masterfuel
Click to expand...
Click to collapse
How do I disable the cmda radio?
Just delete/freeze the phone and messaging apps with Titanium Backup! Or uninstall them.
To confirm what everyone has posted...
1) Deactivate phone with Verizon.
2) In Titanium Backup, Freeze the messaging and phone app.
3) Turn phone into Airplane Mode.
4) Turn on Wifi.
Did I get it all? Thanks everyone for the help.
As several people have experienced, when upgrading their HTC One S to the 4.0.4 update, FoxFi (wireless hotspot program that doesn't require root) has experienced some issues. It works and works well, but when the screen times out, it stops transferring data to the connected device. Keeping the screen from turning off is NOT a permanent solution, so I am asking for suggestions and/or proven solutions to this issue.
HOWEVER! There are some restrictions for the solutions I want to see:
-Do not want to require rooting the phone or flashing a ROM. I consider that the easy way out.
-Do not want to downgrade to the previous version. The update does have some nice advantages that I like. Also would be an easy way out.
So if you have any settings that I should be looking at, or software that could be working in the background that might cause it, I'm all ears. If T-Mobile/HTC release a patch, I'll download it.
So.... any ideas?
You can't downgrade from 4.0.4, or for that fact any software update, you can't downgrade. It's one of the consequences of being on T-Mobile 4.0.4 update.
I don't think there's a way, apart from connecting your phone to your computer via usb, and selecting "stay awake" mode.
usaff22 said:
You can't downgrade from 4.0.4, or for that fact any software update, you can't downgrade. It's one of the consequences of being on T-Mobile 4.0.4 update.
I don't think there's a way, apart from connecting your phone to your computer via usb, and selecting "stay awake" mode.
Click to expand...
Click to collapse
Well, the WiFi works fine until the screen turns off. I can keep the screen from turning off so that's not a big deal.
And I included mention of a downgrade just because I wanted to head off anyone trying to suggest that.
I'm not giving up on this. There's either a setting that the phone defaults back to, or a patch that should update this.
jhooper90 said:
Well, the WiFi works fine until the screen turns off. I can keep the screen from turning off so that's not a big deal.
And I included mention of a downgrade just because I wanted to head off anyone trying to suggest that.
I'm not giving up on this. There's either a setting that the phone defaults back to, or a patch that should update this.
Click to expand...
Click to collapse
I agree with you that there has to be away to get it working again. The other 2 recent radios out of Europe exhibited this same behavior on AOSP based roms. However, it behaved correctly on Sense based roms ie. Stock or Viper rom.
I think the easiest way to get the functionally back is to flash on Viper Rom and test if it works there. If it does then T-mobile just screwed up their rom or did it on purpose. If it doesn't work then that opens up a whole other issue.
I'm not about to flash my phone in specific (It's my primary phone and I can't afford to have it out of comission if I make a mistake), but if someone can provide that information it would be useful.
yeah this is a very odd problem with foxfi...I wonder how it shuts off the connection when the screen turns off. also why were you guys using foxfi before if you could just add a new apn and the hotspot worked fine? Now the new apn method does not work after the update though.
cheaplikeafox said:
yeah this is a very odd problem with foxfi...I wonder how it shuts off the connection when the screen turns off. also why were you guys using foxfi before if you could just add a new apn and the hotspot worked fine? Now the new apn method does not work after the update though.
Click to expand...
Click to collapse
Yes FoxFi worked correctly on 4.03, there is a hitch to the data shuttng off once the screen cuts off. If you are say watching netflix with a constant data draw from the one s, the screen can tun off and you'll still be tethered, but once the constant data draw stops so does the data until screen comes back on.
You guys doing something special to connect with foxfi? I can connect to my phone when I turn it on, but the computer I'm trying to tether to always says no Internet. I can live with the screen time out, but I can't get it to work at all sense the update.
Edit: I can't connect to Foxfi at all from my computer.
Edit2: I uninstalled And reinstalled foxfi, now it's working!
I have a similar problem, ie. not related specifically to tethering but in general to wifi stopping working with screen off.
I opened up terminal emulator, chose menu>activate wake lock and voilà! Everything's working fine for me now! :good:
Try it out and hit thanks if helped!
nor-ric said:
I have a similar problem, ie. not related specifically to tethering but in general to wifi stopping working with screen off.
I opened up terminal emulator, chose menu>activate wake lock and voilà! Everything's working fine for me now! :good:
Try it out and hit thanks if helped!
Click to expand...
Click to collapse
For me data still stops while tethered when screen goes off unless it's a constant data pull.
Go to settings tap WiFi open menu go to advanced select keep WiFi on during sleep and set it to always let me know if this works
Sent from my HTC VLE_U using xda app-developers app
cheaplikeafox said:
yeah this is a very odd problem with foxfi...I wonder how it shuts off the connection when the screen turns off. also why were you guys using foxfi before if you could just add a new apn and the hotspot worked fine? Now the new apn method does not work after the update though.
Click to expand...
Click to collapse
FoxFi never required the new APN method to work previously. In 4.0.3, I never even heard of the new APN method, but still got it to work.
beccadevin said:
Go to settings tap WiFi open menu go to advanced select keep WiFi on during sleep and set it to always let me know if this works
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I've tried that as well. To be sure, I tried turning it off and back on again, and it doesn't seem to have an effect on the connection.
nor-ric said:
I have a similar problem, ie. not related specifically to tethering but in general to wifi stopping working with screen off.
I opened up terminal emulator, chose menu>activate wake lock and voilà! Everything's working fine for me now! :good:
Try it out and hit thanks if helped!
Click to expand...
Click to collapse
Well, on the HTC One S I could just set the screen to not time out. that seems to accomplish the same goal, would it not?
Yeah you can do that.
Mine works ok too while the screen is on.
But while the screen is on it is taking much more power to a process that already takes alot of power from the phone.
TheArtiszan said:
Yeah you can do that.
Mine works ok too while the screen is on.
But while the screen is on it is taking much more power to a process that already takes alot of power from the phone.
Click to expand...
Click to collapse
And not only that but burn in on the screen, saw one at tmobile store with horrible burn in.
nor-ric said:
I have a similar problem, ie. not related specifically to tethering but in general to wifi stopping working with screen off.
I opened up terminal emulator, chose menu>activate wake lock and voilà! Everything's working fine for me now! :good:
Try it out and hit thanks if helped!
Click to expand...
Click to collapse
well since foxfi turns on wifi to do the wifi hotspot, then maybe it is related to this problem. do you have to root your phone to open up a terminal emulator or did you just have to download a terminal emulator app to do that?
jhooper90 said:
FoxFi never required the new APN method to work previously. In 4.0.3, I never even heard of the new APN method, but still got it to work.
Click to expand...
Click to collapse
yeah...adding a new APN worked with the built-in hotspot so no extra apps were even needed to use the hotspot. That method worked on the Amaze and then on the One S before the 4.04 update.
cheaplikeafox said:
well since foxfi turns on wifi to do the wifi hotspot, then maybe it is related to this problem. do you have to root your phone to open up a terminal emulator or did you just have to download a terminal emulator app to do that?
Click to expand...
Click to collapse
Nope, root is not required. Just download "android terminal emulator" from the play store and choose wake lock from the menu. There is also wifi lock if you wanna try. Wake lock is sufficient for me though.
Yeah I tried using the take wake lock option in terminal emu on t-mo us one s and it won't work still even with that being on.
TheArtiszan said:
Yeah I tried using the take wake lock option in terminal emu on t-mo us one s and it won't work still even with that being on.
Click to expand...
Click to collapse
Well, I'm assuming that wakelock would keep the screen on. I don't know if it would do anything else.
Hi All,
I got the Lollipop 5.1 OTA 2 days ago and installed it - everything went smooth and the phone working fine...
But I noticed that if I reboot my router (or turn it off / on again) the Wifi don't reconnect unless I turn on the screen (the second I turn on the screen the wifi connect normally).
I didn't have this issue with Lollipop 5.0.1
P.S.
I know that this is happening because I have a led on my router telling me if any of my Wifi devices is connected or not. And to make sure I also entered the router settings to see if my phone is connected or not.
Anyone noticed that issue with the new lollipop 5.1 ?
Cheers,
I think that your problem is not switching off the router. The problem is when your phone goes to suspension (screen off) and then it drops the wifi off.
My Nexus 5 with 5.1 is doing the same
skorzo said:
I think that your problem is not switching off the router. The problem is when your phone goes to suspension (screen off) and then it drops the wifi off.
My Nexus 5 with 5.1 is doing the same
Click to expand...
Click to collapse
I've got some similar behaviour here, both when updated from 5.0, and with a fresh install from the factory images. When I arrive at a place with known WiFi, the phone only connects once I turned on the screen. After that, it stays connected until I move out of range and back again.
It's probably a matter of responsiveness/battery life. The more it polls for networks, the more battery it uses. It should connect, even with the screen off, within a few minutes.
That being said, I have my wifi set to always stay connected, and I've seen it not connected when I turned the screen on, then connect a couple seconds later. So, there's that. Curious how often it does that.
Aerowinder said:
It's probably a matter of responsiveness/battery life. The more it polls for networks, the more battery it uses. It should connect, even with the screen off, within a few minutes.
Click to expand...
Click to collapse
That's what I suspected. Sometimes, the waiting game works, but I've had my N5 lying on my desk – where it usually gets full WiFi bars – for about 40 minutes the other day, still it did not connect until I turned the screen on.
Edit: Just now, my phone disconnected from WiFi when the screen turned off, which leads me to believe that this is all caused by the WiFi sleep policy. Could it be that Google messed up something there?
dadrc said:
That's what I suspected. Sometimes, the waiting game works, but I've had my N5 lying on my desk – where it usually gets full WiFi bars – for about 40 minutes the other day, still it did not connect until I turned the screen on.
Edit: Just now, my phone disconnected from WiFi when the screen turned off, which leads me to believe that this is all caused by the WiFi sleep policy. Could it be that Google messed up something there?
Click to expand...
Click to collapse
My "research" has led me to believe this is the case.
Anything in terms of a workaround?
I came across those settings in the developer options (see screenshot), especially the "Always allow WiFi Roam Scans" looked promising. Been playing with them, but so far no luck.
Hi All,
exactly the same issues as yours guys are happening since I received the OTA 5.1 and installed it !
I Guess something messed up with this new update in regard of the wifi... as you mentioned.
If you come across a workaround or a confirmation from "Google" please share.
Cheers,
(With almost everyone nowadays having data ..it is difficult to notice such a behavior due to the fast wifi/data switching)
I have seen this happen as well. My battery graph will even show a missing area for WiFi indicating it turned itself on and off twice within a few hours and then stayed on after that.
Google just now released LMY47I, has anyone had a chance to see if that version fixes our problem? Once I'm off work (in about 8 hours), I'll give it a whirl and report back.
Tasker will help you
OsBuilder said:
Tasker will help you
Click to expand...
Click to collapse
Could you please elaborate on that? I'm familiar with Tasker, but I can't think of a way of dealing with this, since I'm not sure what actually happens with the WiFi. The settings appear untouched.
dadrc said:
Could you please elaborate on that? I'm familiar with Tasker, but I can't think of a way of dealing with this, since I'm not sure what actually happens with the WiFi. The settings appear untouched.
Click to expand...
Click to collapse
I'm sorry, but my phone is now in the service center , and press that I do not remember specifically . The idea is that when you disable wifi, a time interval is forced to connect to a particular network . Look presence on the internet , here is full of instructions.
dadrc said:
Google just now released LMY47I, has anyone had a chance to see if that version fixes our problem? Once I'm off work (in about 8 hours), I'll give it a whirl and report back.
Click to expand...
Click to collapse
http://www.androidpolice.com/android_aosp_changelogs/android-5.1.0_r1-to-android-5.1.0_r3-AOSP-changelog.html
Almost all of the changes on these different builds are SIM related for specific carriers.
LMY47I was only released to LGD821 devices with SIM cards from Indian and Australian carriers
Same problem here. I am slowly losing faith in Google. Get the frickin basics going guys!!!
Back to my 5.0.1 build.
I've gone back to 5.0.1, too. Pity, except for this I was pretty happy with 5.1. Maybe 5.1.1 will actually be usable.
Do you think it can be related to Issue 163350? code.google.com/p/android/issues/detail?id=163350
I have just reported that, but I'm still trying to understand if it just happens to me or what.
fabiastik said:
Do you think it can be related to Issue 163350? code.google.com/p/android/issues/detail?id=163350
I have just reported that, but I'm still trying to understand if it just happens to me or what.
Click to expand...
Click to collapse
I think the solution is "use vibrate mode on". Get your device to vibrate mod and test it.
I am waiting for your feedback.
MindLeader said:
I think the solution is "use vibrate mode on". Get your device to vibrate mod and test it.
I am waiting for your feedback.
Click to expand...
Click to collapse
This trick didn't work.
I have this proble too