Database Develop

[Q] Wifi issues - connected to wifi but no data

Hi folks
Since I updated to JellyBean (JellyMod currently) I have an issue with my wifi connection.
It shows connected but i cant transfer any data (every app fails to establish a connection) until I turn off the wifi and turn it on again. then it ill work for some time and fails again after a not defined period of time.
I found a lot of threads regarding similiar problems but I did not find a solution yet (and for me having a rooted phone installing an app that that runs in background like wifi fixer is a workaround, not a fix
I already did a complete factory reset and fresh install of jellymod.
My router at home is a netgear wndr3700 with the latest dd-wrt. all my other devices work great.
I set the wifi of my i9070 to always on. also i installed auto wifi for location based wifi on/off-profiles.
all of this worked with gingerbread, never had problems...
any idea? seems like a lot of galaxy phones and even tabs are affected...
Thanks in advance!

Wifi signal drops to "poor" and won't connect with 2014 moto x

I just received my gen 2 moto x last night and am having trouble connecting to Wifi at work. It connects to my home network and one of my work networks just fine, but when I try to connect to the work network I need it to connect to the signal strength drops to "poor" as soon as I press connect. My home network and work network both are password protected. I've verified the password and have the same connection settings as my friend's gen 1 moto x, which connects properly. The work network has excellent signal at all times when I am not trying to connect to it. It just keeps cycling from "connecting" to "saved."
Has anyone else experienced this or know a workaround? I found this but this is for a gen 1 (I'm not sure if that would help) but I'm not rooted so I don't have access to phase 2 authentication. http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-signal-drops-trying-to-connect-t2872241
Thanks,
Mike

mikekory87 said:
I just received my gen 2 moto x last night and am having trouble connecting to Wifi at work. It connects to my home network and one of my work networks just fine, but when I try to connect to the work network I need it to connect to the signal strength drops to "poor" as soon as I press connect. My home network and work network both are password protected. I've verified the password and have the same connection settings as my friend's gen 1 moto x, which connects properly. The work network has excellent signal at all times when I am not trying to connect to it. It just keeps cycling from "connecting" to "saved."
Has anyone else experienced this or know a workaround? I found this but this is for a gen 1 (I'm not sure if that would help) but I'm not rooted so I don't have access to phase 2 authentication. http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-signal-drops-trying-to-connect-t2872241
Thanks,
Mike
Click to expand...
Click to collapse
Exact same problem. Fine at home and everywhere else. Spent a couple hours this week on the phone with Moto. They keep saying it's the network, yet everyone else is on it. They say update firmware and open MAC. Both of which are done.
This is the message in the Access point every 3 seconds when my phone is trying to connect...
"Client Deauthenticated: MACAddress:9c:d9:17:a1:c8:51 Base Radio MAC:b8:62:1f:ad:5e:90 Slot: 0 User Name: unknown Ip Address: unknown Reason:Unspecified ReasonCode: 1"

My wife's phone drops WiFi in favor of 4G LTE at home. I have to turn off data to connect to WiFi but it eventually drops the WiFi. I'm still waiting on my pure edition so I'm not sure if its just her phone or if its a common problem.

bradley26 said:
My wife's phone drops WiFi in favor of 4G LTE at home. I have to turn off data to connect to WiFi but it eventually drops the WiFi. I'm still waiting on my pure edition so I'm not sure if its just her phone or if its a common problem.
Click to expand...
Click to collapse
This!
I have this problem all the time ON multiple networks, its very frustrating

Mines will disconnect from my 5ghz when the screen goes off and reconnects when turned on, works fine on 2.4ghz. I have a Nighthawk ac1900 so the phone is definitely the problem.
Sent from my Hammerhead

This is related to 802.1X, We have it implemented Radius and 802.1X at work and it doesnt connect. But the same AP has a guest SSID which has no protection and a separate vlan which has access only to internet and it works fine.

giovannirc said:
This is related to 802.1X, We have it implemented Radius and 802.1X at work and it doesnt connect. But the same AP has a guest SSID which has no protection and a separate vlan which has access only to internet and it works fine.
Click to expand...
Click to collapse
Sounds like this could be my problem. We have 4 networks we can login to, but they are all broadcast from the same access point. One says "secured with 802.1x" and is for laptops, two say "secured with WPA/WPA2" and are for cell phones/other, and the final is unsecured. I can only connect to the unsecured network.
So does it sound like it's the phone that's refusing the network, the network is refusing the phone for something the phone is sending back to it, or the network is refusing the phone for another reason?

I'm having this same issue. 1st Gen Moto X sitting right next to 2nd Gen, and the 1st Gen is connected while the 2nd Gen can't.

I'm having the exact same issue. It appears the problem is that older Cisco firmware doesnt support 802.11w, which is what the moto x 2014 uses by default. Here is a thread where a moto rep explains it to Cisco - https://supportforums.cisco.com/discussion/12331486/connectivity-issues-cisco-controllers-and-pmf-enabled-moto-x-gen-2

My girlfriend and I have this phone and we had a similar problem. It would connect/reconnect like a billion times before staying connected on our home network but connect fine on other networks. I tried several solutions but the one that worked was changing the channel on the router. I live in an apartment building and there are a lot of WiFi networks around me so I figured that might be causing some interference. I changed my channel from 6 to auto (it automatically jumped to 11) and now it connects instantly and is solid. What's weird is I tried channels recommended by WiFi analyzer and my other devices would connect just fine but the Moto X's couldn't even see the network in the list when it was on a lot of channels like 12, 13, and 14.
Seems like a weird WiFi radio firmware bug to me.

Is there a client side fix for this?
I just ran into the problem at my work. It is a major hospital. They are not going upgrade their cisco firmware so a couple of people's personal phones are able to connect to the network.

WiFi in general is bad on the X2014 and I am reading the same in the Droid Turbo forums.
Sent from my XT1095 using XDA Free mobile app

What!? Really?

I've not had a single issue with WiFi connectivity. I'm an IT professional so heavily reliant on WiFi.

will54880 said:
WiFi in general is bad on the X2014 and I am reading the same in the Droid Turbo forums.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
Wutang200 said:
I've not had a single issue with WiFi connectivity. I'm an IT professional so heavily reliant on WiFi.
Click to expand...
Click to collapse
I never had a WiFi problem with the Moto X 2014 until today at work. It wouldn't connect to a few different clients Wireless APs. At the first client site I power cycled the phone and WiFi still wouldn't connect. I then went to another client site and once again it would no longer connect. I power cycled again and this time it connected just fine albeit Bluetooth was acting funny and not connecting to the Moto 360. After cycling Bluetooth off and on again the 360 finally connected. Not sure if this is an actual issue or just dumb luck. I wonder if anyone that was having WiFi issues with this phone also has a Moto 360 connected via Bluetooth?

I don't own a 360 and my bluetooth is normally switched off unless I'm streaming music at home.

I know none of what I am about to write will solve anyone's issue but sharing my experiences mught help understand you're not alone. I wander between as many as a dozen different wifi networks daily. I manager a 63 room hotel on 7.5 acres where we are currently running EnGenius EAP350 AP's broadcasting in 2.4mhz band ONLY using .11bgn. I set the entire network to use one SSID so roaming is, in theory, problem free. My XT1095 has not had any issues at all here on property.
I also have my personal network in the lobby and main building under 2.4/5/.11AC side by side with out guest network. No issues bouncing around. I honestly expected issues but have found none.
There is one issue I have found in Android in general which can happen randomly, or I have not been able to induce the behavior only recognize it. Occasionally when I move from one building to another Android (ICS forward for sure) will forget which actual AP it's after and just hang. My solution is to tell the device to forget that node then once forgotten the network, of course, shows up in the list. I then select it and boom we're back in business.
I do have issues when I visit a network at say, the grocery store which requires accepting an EULA...the device simply will hang Wifi wize, even when I delete and reconnect I won't get the note to open the authorization page. I end up just killing wifi and going with LTE.
I get the same behaviors from all my phones ICS though Kitkat, don't have Lollipop yet darn it!!
I have long been frustrated with this weirdism from Android but have reached a point of M.A.D. with my devices but never found a solution.
I have noted I have the most issues by far with Cisco/Linksys devices. It has been almost assured that if I have an issue it's one of those routers running an older firmware version (amazing how many AP/routers use default password settings...I mean, really???)
Not 100% sure it's a firmware only issue but I do think it's some common bit of hardware in an AP/Router which can go spastic for some reason preventing Android from figuring out how to remain or get connected. I even had one of the EnGenius AP's go nuts, a fast swap with a freshly configured AP resolves but, again, still does not identify or solve the problem
I also sense there is some oddness deep in the bowels of Android's wifi/networking subsystem which just was never written correctly and may never be fixed.
Last I run and app called Wifi Analyzer by Kevin Yuan, it helps me a GREAT deal because I can target a specific AP/node to connect with. Android versions often defeat this by not remaining connected to that desired target AP and switching to something else. Here is where I think some of the issues with wifi connectivity live...Google MUST spend some time refining their wifi subsystem.
No matter this is a Very frustrating issue when it happens. My best solution has always been to forget the current connection then reconnect with it again once it reappears. Better yet use Wifi Analyzer or similar app to target a specific AP/node and connect/forget from inside the app, that really does seem to help, mostly...sigh, I know, sorry...

This WiFi issue is really aggravating. I have tried so many things:
1. Rebooting Router
2. Powering Off/On Phone
3. Turning WiFi Radio Off/On
4. Resetting Phone Cache Partition
5. Using WiFi analyzer and setting my router to various channels manually
6. Changing Router SSID
7. Forgetting SSID on phone and re-adding it
8. Verifying MAC Filtering is not enabled
9. Enabling MAC filtering and specifically allowing phone MAC address
10. Disabling "Avoid Poor Connections" in WiFi settings
11. Manually setting WiFi frequency band to 2.4ghz in phone settings
12. Disabling "WiFi Optimization" in phone settings
23. Changing WiFi direct and BT phone names (yeah, a big stretch, but I read somewhere that this worked)
24. Installed updated firmware on my ASUS RT-N12D1 (3.0.0.d.376_3602)
25. Disabled WPS on router
26. Switched router between Auto, Legacy and N-Only
27. Disabled Authentication and Encryption on router, just an "Open" connection.
After all of this, the phone still has WiFi connectivity issues. Sometimes after a phone power cycle it will connect to WiFi, but never for very long. Every other device I have connects to the WiFi without issues. I just got the Moto X a few days ago (AT&T version) and this is the first time I have ever had a device with WiFi connectivity issues like this. Very aggravating. There is clearly something wrong with either the hardware, or software on the phone.
There are some other oddities. When it won't connect to WiFi, there is something strange with the phone. Its not like it just can't connect or stay connected to WiFi, but somehow it seems like the WiFi is in a stalled state. Sometimes it won't show any WiFi networks and just says "Searching for WiFi networks..." until I turn off wifi and turn back on again. Then as soon as it turns back on, it will show the nearby SSID's, and try to auto-connect to my router, but after a few seconds it shows "Disabled" under the SSID. Then after a few seconds the disabled goes away, and it just shows the SSID name. It also won't let me change the WiFi Direct phone name while the WiFi is in this state, it gives me an error saying "Failed to rename device", followed by "Group Creation Failed". However, when I am actually connected to WiFi, I can rename the WiFi direct name just fine. So its not just simply an issue with bad radio signal or something, but something more serious, like the WiFi state is hung or something. If I can't resolve this in another day or two, I am going to have to return the phone, and hopefully a replacement will work. If not, I might have to get something other than a MotoX because I can't not have WiFi while at home and work.
---------- Post added at 12:29 PM ---------- Previous post was at 12:10 PM ----------
I found a way that seems to work to connect to WiFi. To clear, this isn't a fix for the data-sync issue that some people are having, or poor signal, but the issue where you can't connect to an SSID, and there is no error or anything.
1. Hold Down Power Button
2. Turn Airplane Mode On
3. Turn Wi-Fi On
4. Connect to SSID
5. Press Power Button down again
6. Turn airplane mode "Off"
I have now tried this several times, and it works everytime. If I turn off Wi-Fi and back on again, it won't connect, until I do the airplane mode trick. I don't know who to give credit for this, I have spent days and hours searching, and I remembered reading that from somebody else, but not sure where, so this is not my fix, I am just posting it here as it seems to work.
This issue is strange, and must be some combination of Android, and Motorola software/hardware/firmware configuration. I hope they get this fixed, but it at least now, this temporary fix will work whenever WiFi is not connecting.

For those of you getting WiFi connectivity problems, it could be related to your router setup. Download an app called InSSIDer and run a scan, then choose a channel that's not being used but make sure it's 5 channels higher or lower. For example, if it detects 3 networks on channels 3, 5 & 6, then you want to choose channel 10 or 11. If it detects one network on channel 6, then you should choose channel 1 or channel 10 or 11.
I noticed issues like this when I bought my Nexus 4 after my iPhone 4. Android devices seem to ship with rubbish WiFi radios.
Like I've mentioned before, I've not experienced a single disconnection with my phone either at home, work, in laws, coffee shops or anywhere else ever. Same with my first gen Moto X.

Mine is slightly different. Now and then, after power cycling or rebooting, it forgets all the WiFi passwords. Not every time. Just now and then.
Also sometimes it's quite fast, some slow. My wife's firs gen is pretty constant.

T-Mobile Wifi Calling Issues (Caused by modified boot.img)

This is going to be embarrassing if I'm missing something easy and obvious, but I've done as much as I can think of. I can't seem to get wifi calling to work. I just flashed the LYZ28E factory image and used wugfresh's modified boot to disable encryption, I'm also rooted with supersu. I don't see T-Mobile Wifi Calling in the status bar on the lock screen, and when I put it on airplane mode with wifi on I can't make calls or send texts. I've read that sim status should change to IWLAN, but mine still shows LTE.
I've rebooted after turning on all settings. Turned wifi calling off and back on.
I've turned wifi calling on and set to wifi preferred.
I've updated my e911 address.
I've seen one other person with similar issues. Wouldn't be because I'm unencrypted/rooted/etc. Does airplane mode have to be off in order to work? Is there a better way to test this or know its working?

Are you on your home WiFi?
I'm not a nexus user but a Galaxy S5 user, I experienced this on certain WiFi networks like at work.

I also flashed a fresh image of the latest software and could not get it to work. This was at my home network. My wife's WiFi calling works perfect on her S6 so I know its not my router.

Even if WiFi is set preferred, mine seems to only switch if it drops off of LTE or the LTE signal is weak. At home, 70% of the time I've been on WiFi calling, with the rest of the time on good ol' cellular.
The calls are still negotiated over the cellular control channel, so if Airplane mode is on, you won't be able to make or receive calls.
edit: the above sentence is incorrect. I don't know why it didn't work for me at first, but it's working now. Calls can be placed on WiFi solely.

Same here with this build.... I'm where I would prefer having it.

ignitionnight said:
This is going to be embarrassing if I'm missing something easy and obvious, but I've done as much as I can think of. I can't seem to get wifi calling to work. I just flashed the LYZ28E factory image and used wugfresh's modified boot to disable encryption, I'm also rooted with supersu. I don't see T-Mobile Wifi Calling in the status bar on the lock screen, and when I put it on airplane mode with wifi on I can't make calls or send texts. I've read that sim status should change to IWLAN, but mine still shows LTE.
I've rebooted after turning on all settings. Turned wifi calling off and back on.
I've turned wifi calling on and set to wifi preferred.
I've updated my e911 address.
I've seen one other person with similar issues. Wouldn't be because I'm unencrypted/rooted/etc. Does airplane mode have to be off in order to work? Is there a better way to test this or know its working?
Click to expand...
Click to collapse
I have read in numerous forums that disabling encryption is breaking the WiFi calling. Try it again without flashing wug's boot image.

TheAmazingDave said:
The calls are still negotiated over the cellular control channel, so if Airplane mode is on, you won't be able to make or receive calls.
Click to expand...
Click to collapse
I don't think this is true. The whole point of Wifi calling is to be able to call when you have no cell signal.
xxfwmxx said:
I have read in numerous forums that disabling encryption is breaking the WiFi calling. Try it again without flashing wug's boot image.
Click to expand...
Click to collapse
I have encryption enabled and having the same issue.

andy o said:
I don't think this is true. The whole point of Wifi calling is to be able to call when you have no cell signal.
Click to expand...
Click to collapse
Sir, you are correct. I based that statement on my experience of not being able to place a call on WiFi alone originally after the update. I just tried it again though, and it worked. Strange it didn't work before, but no matter. I'll append my post above.

Do any of you have a prepaid plan? I got the 5GB 100 minute $30 plan, maybe that's it?
Edit: although wifi calling with prepaid plans works fine on other phones.

esjames said:
Are you on your home WiFi?
I'm not a nexus user but a Galaxy S5 user, I experienced this on certain WiFi networks like at work.
Click to expand...
Click to collapse
Yup home wifi.
xxfwmxx said:
I have read in numerous forums that disabling encryption is breaking the WiFi calling. Try it again without flashing wug's boot image.
Click to expand...
Click to collapse
I've talked to two people who are having the same issue while unencrypted. I wasn't looking forward to reflashing again but gave it a shot. It does work now, guess I'll have to get over my placebo effect of thinking I can notice a difference between encrypted/unencrypted.
Wonder if there will be a way to get around this in the future, don't particularly care to be encrypted and I will definitely want to use custom kernels.

ignitionnight said:
I've talked to two people who are having the same issue while unencrypted. I wasn't looking forward to reflashing again but gave it a shot. It does work now, guess I'll have to get over my placebo effect of thinking I can notice a difference between encrypted/unencrypted.
Wonder if there will be a way to get around this in the future, don't particularly care to be encrypted and I will definitely want to use custom kernels.
Click to expand...
Click to collapse
I don't think it's the encryption. Are you sure wugfresh's tool have the latest T-mo unencrypted kernel? In my case, I flashed the new boot.img and it started encrypting my phone, I had assumed that it had also flashed the kernel, but it had not. After reading your post I checked and my kernel still was dated in January, so I just flashed the boot.img again, and now it's the new one (3.10.40-g8887dbc dated Mar 20 15:56:38 UTC). Maybe you just need to wait until the kernel is modified for not forcing encryption.

andy o said:
I don't think it's the encryption. Are you sure wugfresh's tool have the latest T-mo unencrypted kernel? In my case, I flashed the new boot.img and it started encrypting my phone, I had assumed that it had also flashed the kernel, but it had not. After reading your post I checked and my kernel still was dated in January, so I just flashed the boot.img again, and now it's the new one (3.10.40-g8887dbc dated Mar 20 15:56:38 UTC). Maybe you just need to wait until the kernel is modified for not forcing encryption.
Click to expand...
Click to collapse
Maybe I'm misunderstanding the difference between the kernel and the boot.img. I was under the impression that the kernel was in the system.img, I was using the stock kernel. The only thing that was modified was the boot.img that I was using to turn off encryption, I didn't think the kernel mattered. I'm not too much of a noob, but I'm far from an expert so let me know if I'm wrong All I know is I was definitely unencrypted and wifi calling wasn't working.
Here's the modified boot.img that was downloaded via the wugfresh toolkit, I flashed everything manually with fastboot/adb though (I only keep the toolkit as backup just in case).
https://drive.google.com/file/d/0BxkNfETYeJqSZkFvX2t6cmFNNWs/view?usp=sharing

ignitionnight said:
Maybe I'm misunderstanding the difference between the kernel and the boot.img. I was under the impression that the kernel was in the system.img, I was using the stock kernel. The only thing that was modified was the boot.img that I was using to turn off encryption, I didn't think the kernel mattered. I'm not too much of a noob, but I'm far from an expert so let me know if I'm wrong All I know is I was definitely unencrypted and wifi calling wasn't working.
Here's the modified boot.img that was downloaded via the wugfresh toolkit, I flashed everything manually with fastboot/adb though (I only keep the toolkit as backup just in case).
https://drive.google.com/file/d/0BxkNfETYeJqSZkFvX2t6cmFNNWs/view?usp=sharing
Click to expand...
Click to collapse
The kernel and the ramdisk are in the boot.img. Wifi calling ability is in all likelihood in the kernel. According to the file name it's the correct build version though, but the sizes vary significantly at 8,338KB for the modified img and 7,442 for the original boot.img, but this could be because of repacking. Someone who knows better might chime in. I followed this to check the version, and it matches (Linux version 3.10.40-g8887dbc). It's weird that they would disable wifi calling for unencrypted devices though.

I don't know if this will help with the issue of the LYZ28E update not switching to T-Mobile WiFi calling for others, but let me share what is happening with my Nexus 6.
I'm running LYZ28E and no encryption (kernel dated Mar 20 15:56:38), and sure enough my phone isn't giving any indication in the status bar that it has switched to WiFi calling. I noticed this morning that the quick setting menu (which I never use - I pulled it down by accident) shows "T-Mobile WiFi Calling" below the signal strength indicator. I just received a call (at home), and my T-Mobile routers LED's began flashing very rapidly while I was on the call, and went back to a slow flash immediately as I ended the call. So it looks like my phone is indeed using WiFi calling. If it will help you gentlemen, it's not encrypted and obviously rooted, everything is stock, and it gives absolutely no other indication that I'm using WiFi other than in the quick setting menu. I have very little cell signal (if any) at home, and there is no way I could have made a cellular call if the phone wasn't on WiFi. I hope this might be the case for others, and perhaps it may just not be indicating WiFi calling is really working.
For others folks that WiFi calling is working for, do you see the "T-Mobile WiFi Calling" in the status bar, or how does it let you know it switched over to WiFi?

bob110011 said:
I don't know if this will help with the issue of the LYZ28E update not switching to T-Mobile WiFi calling for others, but let me share what is happening with my Nexus 6.
I'm running LYZ28E and no encryption (kernel dated Mar 20 15:56:38), and sure enough my phone isn't giving any indication in the status bar that it has switched to WiFi calling. I noticed this morning that the quick setting menu (which I never use - I pulled it down by accident) shows "T-Mobile WiFi Calling" below the signal strength indicator. I just received a call (at home), and my T-Mobile routers LED's began flashing very rapidly while I was on the call, and went back to a slow flash immediately as I ended the call. So it looks like my phone is indeed using WiFi calling. If it will help you gentlemen, it's not encrypted and obviously rooted, everything is stock, and it gives absolutely no other indication that I'm using WiFi other than in the quick setting menu. I have very little cell signal (if any) at home, and there is no way I could have made a cellular call if the phone wasn't on WiFi. I hope this might be the case for others, and perhaps it may just not be indicating WiFi calling is really working.
For others folks that WiFi calling is working for, do you see the "T-Mobile WiFi Calling" in the status bar, or how does it let you know it switched over to WiFi?
Click to expand...
Click to collapse
Rooted, but otherwise stock. Mine shows WiFi Calling on the lockscreen next to T-Mobile, in the quick settings shade as you've mentioned, and on the dialer when in a call.

Oops, I totally forgot about the lock screen, I don't use it, I just turn off the screen. Mine does in fact have the "T-Mobile WiFi Calling" indicator there (text). Thanks Dave.

bob110011 said:
Oops, I totally forgot about the lock screen, I don't use it, I just turn off the screen. Mine does in fact have the "T-Mobile WiFi Calling" indicator there (text). Thanks Dave.
Click to expand...
Click to collapse
Yes, and also during the call there's an indicator on the screen. Where did you get your boot.img?

I noticed that when I'm on stock kernel (or boot.img maybe) WiFi calling works but on a custom kernel even those made for 5.1.1 it never switches to WiFi mode.

@ignitionnight I installed the no encrypt boot.img here http://forum.xda-developers.com/nex...ed-encryption-gain-root-t2946715/post61015828 and wifi calling is working. You'll also notice the size is very close to the original. I think something was wrong with the NRT file. FWIW, I tried the NRT yesterday and it detected the wrong TWRP and wanted to install its own boot.img when I already had those two installed.

Hey guys, so I might have a solution to the issue with WiFi calling not showing in the notification bar or during a phone call. I recently side loaded the new update and then rooted. After rooting I tried out WiFi calling and it worked flawlessly, notifications and all. Immediately after I modified the build.prop file to allow a miracast connection to my Xbox One. After realizing my WiFi calling wasn't showing up anymore I thought the miracast line may have messed with WiFi calling, so I deleted it from my prop file. I rebooted and you guessed it!! WiFi calling shows up in the pull down menu and during a phone call. So give it a shot and see if it works like it did for me. Best of luck
Mike

T-Mobile WiFi Calling causing WiFi instability on school network (PEAP & MSCHAPV2)

T-Mobile WiFi Calling causing WiFi instability on school network (PEAP & MSCHAPV2)
Hello everyone,
I'm on T-Mobile and whenever WiFi calling is enabled, it causes my WiFi to disconnect and reconnect every 5 seconds but when it is off, I have a stable connection. Is there a workaround this? My school has fixed the TLS 1.2 issue related to PEAP and MSCHAPV2 connections from (https://code.google.com/p/android/is...tail?id=188867) already as I pointed that out to them, and we could never figure out why I was still getting disconnected until now.
Note that connecting to my own home WiFi or an open "Guest" connection at school is fine, but one that requires my school account login has this problem.
Thank you!
EDIT: This issue has persisted in Android 6.0 to 6.0.1, but was not prevalent to the T-Mobile specific builds of 5.1.1.

zerrisk said:
Hello everyone,
I'm on T-Mobile and whenever WiFi calling is enabled, it causes my WiFi to disconnect and reconnect every 5 seconds but when it is off, I have a stable connection. Is there a workaround this? My school has fixed the TLS 1.2 issue related to PEAP and MSCHAPV2 connections from (https://code.google.com/p/android/is...tail?id=188867) already as I pointed that out to them, and we could never figure out why I was still getting disconnected until now.
Note that connecting to my own home WiFi or an open "Guest" connection at school is fine, but one that requires my school account login has this problem.
Thank you!
EDIT: This issue has persisted in Android 6.0 to 6.0.1, but was not prevalent to the T-Mobile specific builds of 5.1.1.
Click to expand...
Click to collapse
This is most likely due to the protocals that are blocked in your school. I would run a logcat and see whats up. Without a logcat posting threads like this are a waste of time.

I would try a version of HellsCore kernel with the old wifi drivers. What it states about these kernels
"Its known some networks don't like the new marshmallow wi-fi driver. People reporting disconnects, not able to connect at all, or an instable connection in general. If you suffer from this, switch from the marshmallow driver to the lollipop one."

zelendel said:
This is most likely due to the protocals that are blocked in your school. I would run a logcat and see whats up. Without a logcat posting threads like this are a waste of time.
Click to expand...
Click to collapse
I'll talk to the IT dep. and Aruba engineer next week. I don't know much about networking so I thought I'd post on here to see some ideas, sorry for not posting a logcat. Will see if I can get it soon.
Dopamin3 said:
I would try a version of HellsCore kernel with the old wifi drivers. What it states about these kernels
"Its known some networks don't like the new marshmallow wi-fi driver. People reporting disconnects, not able to connect at all, or an instable connection in general. If you suffer from this, switch from the marshmallow driver to the lollipop one."
Click to expand...
Click to collapse
I've tried the old drivers with HellsCore, and it doesn't work with WiFi calling on. All kernels and ROMs I've tried have the same issue as long as WiFi calling is enabled. Disabled - it works like a charm.

WiFi randomly disconnecting on .575

Hello,
I recently flashed .575 on my Z3C, now WiFi connection is unstable, disconnects after a while. The consequence is that updates do not work correctly, file transfers through WiFi are often interrupted. Did any one notice the same behavior? Any fixes (tried different AP and to reflash the FW)...
Thx

Problem persists in 23.5.A.1.291

Similar issue here

I also have problems with the latest 23.5.A.1.291 firmware. There are two problems in fact, sometimes it disconnects and can't reconnect anymore without rebooting and the other is that, while it still seems connected to wifi, it's effectively offline as internet doesn't work anymore, after a while it starts working again.
It's a pity because the Z3C was the device with the best wifi and coverage that I've ever tried with the previous Lollipop. I partially resolved the problem, meaning that it happens less, changing a few parameters into the router, disabling every possible feature, still isn't completely resolved...

difto said:
Hello,
I recently flashed .575 on my Z3C, now WiFi connection is unstable, disconnects after a while. The consequence is that updates do not work correctly, file transfers through WiFi are often interrupted. Did any one notice the same behavior? Any fixes (tried different AP and to reflash the FW)...
Thx
Click to expand...
Click to collapse
settings/developer options/use legacy DHCP client - enable

Didgesteve said:
settings/developer options/use legacy DHCP client - enable
Click to expand...
Click to collapse
I'm not OP, however I tried that setting but it didn't improve much. After all, DHCP is a protocol which should be used only at connection startup theoretically

I also have the same issue, however installing Auto Wifi Manager seems to have helped -
https://play.google.com/store/apps/details?id=auto.wifi.toggle.manager

Didgesteve said:
settings/developer options/use legacy DHCP client - enable
Click to expand...
Click to collapse
Already tried but it didn't helped. As for the issue, for me it disconnects and reconnects instantly even with full signal every 5-10 min. So it does not eat my mobile data however every lengthy file transfert by wifi might be interrupted.
Tried different channels, 2.4ghz, 5 GHz on two different routers at home, on several public Wi-Fi AP, behavior is still the same.
If screen is on the connection stays but is sometimes interrupted and reconnects directly. If screen is off Wi-Fi gets cut for 2-5 min then reconnects (according to logcat, might be Doze? Wi-Fi is set to be always on). Tried also a full reset of radio settings.

Solution
Does not work unfortunately.
I might have a good news for you guys. I think I finally managed to solve the issue:
1) Download a Lollipop FTF
2) Open flashtool in Flashmode for this FTF and exclude everything except packages beginning with AMSS* (it will not alter any data on the phone and it's very quick, also does not need to regenerate the dalvik cache)
3) Flash
-> You just replaced the baseband / modem with the Lollipop one. Tested briefly on mine and so far no disconnections

Same problem here, after update to .575, and .291 didn't help.
Sometimes when I open WiFi networks phone doesn't find any network at all. Also bluetooh is acting weird sometimes (disconnects, can't turn on).
Tried with DHCP and clearing radio settings, and even downgrading to 23.4.A.1.264 and 23.1.A.1.28, didn't helped.

May be it is hardware related... I am on 4.4.4 and have same issues. On some routers better, on some worse. Also sometimes works ok for long time, next day same place disconnecting...

In my case, everything was OK until upgrade to MM

pawlak2 said:
Same problem here, after update to .575, and .291 didn't help.
Sometimes when I open WiFi networks phone doesn't find any network at all. Also bluetooh is acting weird sometimes (disconnects, can't turn on).
Tried with DHCP and clearing radio settings, and even downgrading to 23.4.A.1.264 and 23.1.A.1.28, didn't helped.
Click to expand...
Click to collapse
For me downgrading to Lollipop 23.4.A.1.264 solved the issue but as soon as I install Marshmallow, even a clean install by PC Companion the problem reappears. So I will stay on Lollipop for now, it also has Stanima
I think something is wrong with the way Marshmallow manages the WiFi connection

difto said:
For me downgrading to Lollipop 23.4.A.1.264 solved the issue but as soon as I install Marshmallow, even a clean install by PC Companion the problem reappears. So I will stay on Lollipop for now, it also has Stanima
I think something is wrong with the way Marshmallow manages the WiFi connection
Click to expand...
Click to collapse
you're right. but luckily this problem can be solved! go to Developer options in Settings and check "Use legacy DHCP client". then reboot your device - problem solved!

toxic-hero said:
you're right. but luckily this problem can be solved! go to Developer options in Settings and check "Use legacy DHCP client". then reboot your device - problem solved!
Click to expand...
Click to collapse
This trick seems to solve another problem, for me it did not change anything in the issue

thanks