Related
Im having some problems with the wi-fi connection. When it first conects, everything goes ok, but when I start to download anything, the connection just stops responding, even tough it looks like conected. What should I do?
I'm having the same problem and couldn't find the solution, did any solve the problem?
Wifi problem on MS2
After months of researching and suffering the pain I still have not got a full solution for my MS2. My wifi problem is that it connects well, great wifi speed on my home network. But after a couple of minutes there's no more internet access even though it shows that its connected. I chanced upon this link laptopmag.com/review/cell-phones/motorola-droid-2.aspx?page=4 where it had the same problem brought up. It had a solution/fix which I do not want to use though. Further information can be found on the droidforums link on that page. What I have been doing all along is the same as what the guys at laptopmag has been doing, just reconnect whenever internet is down. Irritating yeah, but don't really have any other option..
Hope someone does have a proper solution :X
In addition to the sporadic troubles loading some sites with Flash elements, we had a much more persistent problem maintaining Wi-Fi connectivity. On three different routers, the Droid 2 would connect and then, after a few minutes, would continue reporting that it was connected but stop downloading data. The solution to the problem, once you notice it, is to disconnect from the router then reconnect, but that is a huge hassle.
Our original Droid experienced the same Wi-Fi problem so many times that we eventually gave up and resolved to use 3G only. However, after searching through several Droid forums and finding dozens of posts from other users who experienced the same problem on first-gen Droids and Droid Xs, we found a possible solution that seems to have worked with the Droid 2. After we changed the settings on our 802.11n router from mixed mode to 802.11g only, we did not experience the problem again, though we had to operate all of our computers on the slower 802.11g speed, which is unacceptable.
Click to expand...
Click to collapse
in my case all I had to do was port forward som port i dont remember
Sent from my A953 using XDA App
I installed the BlurLess GB rom and the problem is now gone.
Btw, my router @ home is G only, so the solution posted did not apply for me.
anyone else experience wi fi issues ??? tablet keeps losing signal ?? laptop is perfect also my phone is full signal to ?? any fix for this ?? thanks
I posted a thread in this section about the same thing called "wifi strength". It is a problem with the antenna, it gets REALLY bad reception. Mine gets 25db less than my phone in the same exact spot in my house so it is obviously an issue with the tablet.
Someone in the general section replaced the antenna and said they got significantly better results, but it looks like no one has found a US vendor for the antenna yet.
I had this problem. If you have your Wifi set to stay on all the time (even when the tablet sleeps) the Wifi will not reconnect when you wake it up. It's something to do with the rotation of the Wifi address (DHCP).
Change the Wifi disconnect setting to "when the screen goes off." That fixed my problem.
If you setup a static ip address for your connection it will stop dropping the connection. Also, there is a fix for this in the development section. Search for wifi dhcp fix and install it.
Here is the file you need, you have to flash it through recovery so if your not rooted your out of luck. Otherwise the static ip trick should fix your problem.
I've been having problems with this recently. My a500 worked fine for ages, then started playing up when I got a new wireless router (Netgear DGND3300v2). It would keep dropping out, despite my other wireless devices working even better. If I turned the wireless off, it would take ages to reconnect, or not reconnect at all.
My issue was caused with the 11G channel on the wireless router being set to auto. I changed this to 6 and as soon as I did that, it worked flawlessly. Not had 1 problem since.
cruise350 said:
Here is the file you need, you have to flash it through recovery so if your not rooted your out of luck. Otherwise the static ip trick should fix your problem.
Click to expand...
Click to collapse
Many thanks for posting this fix cruise.
I am on Timmydean's 3.2.1. (rooted)
Could you explain how to install this fix?
Many thanks
This thread is intended to be a gathering point for all wifi issues on Android Touchpad ROMs.
Having a separate specific issue thread for this will serve several purposes.
Avoid wifi issues getting lost in the more general Touchpad ROM threads.
Allow issues common to wifi operation on all the different ROMs to be concentrated in one thread.
Reduce annoyance to those who are currently enjoying good wifi operation and who see repetition in the issues being aired.
Make it easier to report tests and experience on different set ups and as new drivers / ROM integrations appear.
Make it easier for users with questions to see if it has been asked before.
Background
Wifi operation on Android Touchpads currently is a hit and miss affair. Some users report flawless operation regardless of access point. Others can get stable operation with careful set up and / or choice of access point but problematic operation on access points over which they have no control. Others still fail to get conditions right for any form of stable operation.
This is in comparison with WebOS based operation where the problems seem to be much fewer. Probably most of the explanation for this difference is the current lack of suitable drivers integrated into the ROM environment. Hopefully this will be fixed at some point and there are some encouraging signs already that improvements are possible.
Factors affecting operation
There are several factors which could potentially affect the wifi performance with Android Touchpads including the type of Access point, the set up of the Access point, the local signal strength and interference conditions, variations in Touchpad hardware build, and how the ROM software has been installed and set up. A key factor on top of all these is the wifi drivers used and how they are integrated.
General advice
Until the fundamental performance is improved the end user of the Touchpad can do some things to help get better performance particularly if they have control over the Access point. Typically this will be in the home situation. Possibilities for adjusting setting for work or public access points tend to be small or non-existent.
Note that not all suggestions work for everybody affected so you have to be prepared to experiment a little to see what may work for you.
The primary suggestions I offer that worked for me in my home situation is to lower the channel setting on the router to Channel 1 even though for me that was worse from a local interference point of view. Other suggestions include avoiding dual band operation and experimenting with security settings (like using WPA instead of WPA2).
Posting
Please post to this thread if
You want to ask Android Touchpad wifi specific questions including problems you are encountering
You can answer Android Touchpad wifi specific questions posted here
You have reports on specific problems that may help resolve wifi issues
You have suggestions on how to improve operation in the short term with existing drivers
You have reports on new driver operation either better or worse.
Please also include the ROM and version used in any specific reports. Although wifi issues have been present on 2.3( e.g CM7) and 4.0 (ICS) the focus for development is now firmly on ICS and that is where improvements are likely to be made.
It is unhelpful at this stage just to post here that you do not have any wifi problems unless you have some specific advice on how that can be generally applied. We already know there are many who enjoy good wifi performance.
Currently I am using CherryKANG 0.2a which does have some experimental new drivers in and for me gives much better performance.
I'm on cm9 alpha 0.6 with stock kernel @1.5 installed with clockworkmod 5.x with a webOS 3.0.5 dual boot. My home router is open (but I use MAC Address blocking to keep the creeps out). My wifi is about 80% on point but will go out about every 24 hours and I have to forget the network, wifi off, power down. Power back up, wifi back on re connect and good for another 24 hours. I noticed if my device "reboots" instead of turning all the way off my wifi WILL NOT connect. How are people doing on cherrykang? Any better?
rochford77 said:
I'm on cm9 alpha 0.6 with stock kernel @1.5 installed with clockworkmod 5.x with a webOS 3.0.5 dual boot. My home router is open (but I use MAC Address blocking to keep the creeps out). My wifi is about 80% on point but will go out about every 24 hours and I have to forget the network, wifi off, power down. Power back up, wifi back on re connect and good for another 24 hours. I noticed if my device "reboots" instead of turning all the way off my wifi WILL NOT connect. How are people doing on cherrykang? Any better?
Click to expand...
Click to collapse
My experience so far with 0.2a of Cherry has been 60 hours of operation without a wifi issue. This includes about 6 hours on a work network where before the wifi fix in Cherry about the only way I could gt a connection was by moving very close to the access point and it would drop out within 5 minutes of moving away. During that 6 hours with Cherry it found the connection straight away, maintained it all the time and even reconnected automatically when I tried a reboot. I'll report further on this when I have had more time on the work network this week.
lafester said:
Nice post but wrong forum
(@ op)
Click to expand...
Click to collapse
Which forum are you suggesting this should be in?
I know this is development but this thread was an attempt to pull out all the wifi related questions which are already being posted in the various development threads here. I thought that development was more appropriate as the main intention is to help and encourage the development of wifi to the point where the need for wifi support becomes much less.
Clearing /data/misc/wifi and rebooting makes my touchpad connect to the router without any hesitation, I guess it is similar to forgetting and rebooting(but haven't tried that)
ROM: 0.2a Kang
ClassicNerd 0.0.4
My home network is a Netgear N600 dual band router with WPA2 security as well as a guest SSID. i connect to the 5G band with no issues with the exception of when I have to reboot. On rebooting if I connect to an access point I have to keep the screen alive for around 10 minutes. After that everything is fine, otherwise the system reboots when the screen goes off.
My work network is an overlapping pervasive network using PEAP authentication. On reboot if I do not shut down with WiFi off my settings get into a state where it refuses to connect, or even try. Forgetting the network and then entering the information again fixes the issue. I also get the sleep reboot if I don't leave the tablet on for a bit of time problem here.
I never have any disconnects that are tablet related on ether network.
Kang 0.4.8a truly rocks and addresses wifi as I can now connect even when channel is 11!
Sent from my cm_tenderloin using xda premium
guho said:
Kang 0.4.8a truly rocks and addresses wifi as I can now connect even when channel is 11!
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for that. I had been holding off switching to 0.4 based on the kernel issue comments but it looks like 0.4.8a is good to go so I'll try that.
I note with sympathy the response you got from your comment in the other thread. Some guys can get very territorial even though all these ROMS are largely based on same open source and rely heavily on the work of some central devs .
Here is my feedback from 1st full day using CherryKang 0.4.8a in my work environment.
Bottom line is that the wifi fix is giving me a big improvement over previous builds but I don't think is totally problem free.
At the start of the day it found and connected automatically.
Over a 10 hour period it dropped the connection twice after staying connected about 4 hours each time. It didn't reconnect automatically after a drop but required the wifi control to be turned off and then on again to perform the reconnect which it did very rapidly.
This is still a dramatic improvement over before where I struggled to get a connection at all and it would always drop in less than 5 minutes.
To get a better handle on comparative performance I plan to run it under WebOS tomorrow just to get a baseline on how the native tablet performs under the local conditions. I had previously tried out WebOS here and it was stable over the hour or two I had it on but I've never tried it for a full day.
Having said that I also have an ICS Nook Color here which is absolutely rock solid on this access point and has never dropped the connection over several weeks of use so I know its not a fundamental access point issue.
bobtidey said:
I'm fairly neutral about whether this is better in general or development. My original thinking that it was Android based discussion rather than general chit chat, that the end goal was the 'development' of improved wifi operation, and that it might be better local to much of the ROM discussions where wifi can be a trigger issue..
Click to expand...
Click to collapse
I was always told that the dev section is for software that you create - ROMs, kernels, tweaks, etc. It's usually something that you need to flash on your device that affects performance or functionality in some way (themes and visual mods are not included however).
Any sort of "Discussion" or any troubleshooting is usually in General or Q&A, since it can usually span across different roms, and/or software settings. No offence to you, as it is sometimes confusing to people exactly what belongs in the dev section. Usually, if it's not something you are flashing on the device, it goes in another section.
That said, I'm running ClassicNerd Butta v1, and have no issues connecting to my 2.4ghz channel on my router, but it won't connect to the 5ghz channel for some reason.
I have a netgear wndr3700 N600 router with dd-wrt firmware flashed on it.
Edit: changed "wireless networking mode" on the 5g channel from "N only" to "Mixed", and I'm now able to connect.
Since I just had some pretty bad Wi-Fi issues, I guess I should share what I found and how I fixed it.
I've been using my TouchPad very reliably on my home and work networks. I don't know what channel either are on, but at home I'm pretty sure I've been on an 802.11n access point (5 GHz channel). The router at home is a Netgear WNDR3700 v.1, but after problems with the firmware dropping countless other devices, I installed the dd-wrt firmware and configured it to only be an access point, and I'm relying on another router upstream to provide my DHCP and private network. This configuration has been rock solid for a couple months now, and I've never had to reset the access point since! After I installed CM9 alpha 0.6, I've had maybe 3 or 4 times where I've lost network connectivity on my TouchPad, but other devices continued to work; clearly a problem with the TouchPad in those cases since simply rebooting the TouchPad restores connectivity. I do not stop Wi-Fi before rebooting. This is a reliability I can live with since outages have been quite infrequent and easily fixed.
Currently I'm traveling, and I needed to setup a temporary wireless network. To do so, I used Connectify on an older Windows 7 laptop, and I'm using the Wi-Fi board built into the laptop to share the wired connection I've plugged into it. The wireless board is a Broadcom 802.11g with a BCM43XX chip set. When using Connectify, the wireless board runs on channel 11, with no way to configure it that I can find.
After ~48 hours uptime, I tried to use my TouchPad today and found Wi-Fi was not working. Using "Wifi Analyzer" from the market, I observed the TouchPad could "see" a few different access points, but it was unable to connect to any of them, while I was still able to measure things such as signal strength. Forgetting the network connection and reentering the WPA2 key did not work. Connectify showed that my Nexus S running Android 4.0.3 was still connected, but my TouchPad was "Disconnected." Rebooting the device did not restore Wi-Fi. Shuting down my laptop and rebooting did not restore Wi-Fi, although I observed my Nexus S reconnecting. I then rebooted the TouchPad into WebOS, where I could connect again, but booting back into CM9, I could not reconnect. I then turned Wi-Fi off, and rebooted. After turning Wi-Fi back on, I could see the access points again, but still couldn't connect.
What seemed to finally unstick things was turning Wi-Fi off, setting Airplane Mode on, turning Wi-Fi back on, and when I observed that turning Wi-Fi on was not automatically turning Airplane Mode off, I manually toggled it myself. Almost immediately, Wi-Fi connected.
I believe in my case, toggling Airplane Mode in the future may be a simple fix, but I only have the one data point to go by so far.
Sent from my cm_tenderloin using XDA App
For the most part my wifi works pretty good, but I have problems with my touchpad wifi at work. The wifi connects for a few moments then simply loses connectivity. The setup at work is a system of enterprise access points all using the same ssid, and for whatever reason it throws the touchpad (and some other android devices) for a loop. My android phone used to have issues too, but it was fixed with a custom rom, and webos connects fine also.
I have tried almost every rom with mixed results. The "Bricked"rom v4 gave the best experience. CM9 A6 was ok.. Next I tried classic nerd buttah 0.1.0 v1 and v2. I found it wasn't really any better than other roms out there, and had some pretty annoying glitches. I read though all of the classic nerd posts looking for answers, I found their thread to be hostile, so I didn't bother posting any questions. I promptly uninstalled, and moved on to CherryKang with the hopes that the wifi driver fix would work out. It didn't seem to do anything, but I have to say that CherryKang runs pretty good, hasn't given me any problems, and I like the 132 dpi. Every install was preceded with full wipe.
So I started tinkering with the build.prop and wpa_supplicant.conf
My hope is that something in there can be tweaked and solve my issue.
After doing some research I found a few settings that have helped other people:
-Changing hostname to a shorter hostname. The default touchpad hostname = android-78abb09201c4bca8. Edited the build.prop and added net.hostname=touchpad
found here: http://ergh.org/cmtp/-
*didn't work for me but may work for you
-Setting scan_ssid=1 in wpa_supplicant.conf
Oddly made the disconnects less frequent. Still testing
-Disabling WMM support. WMM causes havoc with some routers and devices, shutting it off sometimes clears things up.
*haven't tried it yet but I will post something when I try it tomorrow.
Other than that, I'm not sure what to try next. Any ideas?
Cubicsilver said:
For the most part my wifi works pretty good, but I have problems with my touchpad wifi at work. The wifi connects for a few moments then simply loses connectivity. The setup at work is a system of enterprise access points all using the same ssid, and for whatever reason it throws the touchpad (and some other android devices) for a loop. My android phone used to have issues too, but it was fixed with a custom rom, and webos connects fine also.
I have tried almost every rom with mixed results. The "Bricked"rom v4 gave the best experience. CM9 A6 was ok.. Next I tried classic nerd buttah 0.1.0 v1 and v2. I found it wasn't really any better than other roms out there, and had some pretty annoying glitches. I read though all of the classic nerd posts looking for answers, I found their thread to be hostile, so I didn't bother posting any questions. I promptly uninstalled, and moved on to CherryKang with the hopes that the wifi driver fix would work out. It didn't seem to do anything, but I have to say that CherryKang runs pretty good, hasn't given me any problems, and I like the 132 dpi. Every install was preceded with full wipe.
So I started tinkering with the build.prop and wpa_supplicant.conf
My hope is that something in there can be tweaked and solve my issue.
After doing some research I found a few settings that have helped other people:
-Changing hostname to a shorter hostname. The default touchpad hostname = android-78abb09201c4bca8. Edited the build.prop and added net.hostname=touchpad
found here: http://ergh.org/cmtp/-
*didn't work for me but may work for you
-Setting scan_ssid=1 in wpa_supplicant.conf
Oddly made the disconnects less frequent. Still testing
-Disabling WMM support. WMM causes havoc with some routers and devices, shutting it off sometimes clears things up.
*haven't tried it yet but I will post something when I try it tomorrow.
Other than that, I'm not sure what to try next. Any ideas?
Click to expand...
Click to collapse
Your experience I think is very similar to mine. I could get home wifi access OK by adjusting router, but work access was a complete nightmare with none of the ROMs being perfect. Most were very difficult to connect and would disconnect after a few minutes making them unusable.
I find CherryKang is much better and typically lasts about 3 hours for me. I did also try all the wpa_supplicant tricks like you say, short hostnames etc but I can't get it perfect at the moment. What is interesting is that if I turn wifi off and on to get it to reconnect then it either obtains ip straightaway or there is a delay of about 30 secs and then just says saved and isn't connected and won't recover from that. It is about 50/50 which happens and I suspect something similar is happening with a rescan to cause the drop out after it has been functioning. The work SSID is also not published and I wonder whether that can have an effect.
I tried out WebOS at work again to get a benchmark, and got 8 hours with no drop outs so the hardware and access point can function OK.
I am a little puzzled by the nature of the wifi fix in Cherry Kang so plan to post a message in there and I notice some other wifi drivers for a similar device seem to be surfacing. So I'm optimistic that this issue will be finally sorted out soon.
Bobtidey,
I also have done some in depth research regarding the wifi issues and the patches some are compiling into their kernel or as the other post in the CherryKang thread suggested manually inserting and removing the new/old modules. I definitely am noticing an increase in performance when I tried the rom, wifi was stable but for me I just got lucky and have not really had problems besides the random disconnects and what I thought was hanging turning it on. Anyway let me quote from the commit of which both these fixes originate from "Patch Set 1: I would prefer that you didn't submit this This needs stress test before it can be committed (dalingrin)." "Patch Set 1: I'm wondering if you get any firmware crashes using the new ath6kl module (check dmesg - it was the main reason why activating Wi-Fi sometimes takes very long). That's the main reason that I withheld this patch for now." So that prompted me to be a little skeptical on using this as obviously I would consider dalingrin's advice over all. There's some more to it than this as there is also a timing issue that causes crashing :
"This is not quite ready. It is the most promising driver for us going forward. However, none of the android specific functions are implemented yet. There also a crash related to timing issues though I think I can fix that. I will upload another patch set when I get a chance."
Anyway just thought I'd chime in on the subject especially after the last comment which in my opinion is rather unsettling
Links/sources from quotes and for a nice look at the material.
Expand al if you want to view the comment exchange,
http://review.cyanogenmod.com/#change,12342
http://review.cyanogenmod.com/#change,12341
Thanks,
Sent from my cm_tenderloin using Tapatalk
Classicnerd Butta v2 vs v2.1
Add'l infoI have been running the succession of Classicnerd team builds including the predecessor Xron series. I had no problem in either WebOS or in any build until Classicnerd-Butta-0.1.0-v2. Then I had several instances of connection failure after waking.
I also noticed that the signal strength was shown as dismal even right next to the router. I'm thinking that some of the problem may be the radio not waking up when the tablet does. I was able to connect by tapping the SSID listing on the TP. Then the signal strength returned to normal.
I updated to v2.1-Odex yesterday and haven't experienced any more connection failures.
All of my flashes have been done with factory reset and wiping everything on clockworkmod, reinstalling Gapps and reinstalling apps. I have not restored any backups or backup data.
Update: I have now experienced a couple of instances where the wi-fi is not connected and doesn't automatically reconnect after the TP has been sleeping. Simply turning off and turning on the wi-fi has fixed it.
Just an update on the issue I was having with my 5g network. I changed the "wireless networking mode" on my router from "N only" to "mixed" and am now able to connect.
Nizda1 said:
Bobtidey,
Links/sources from quotes and for a nice look at the material.
Expand al if you want to view the comment exchange,
http://review.cyanogenmod.com/#change,12342
http://review.cyanogenmod.com/#change,12341
Thanks,
Sent from my cm_tenderloin using Tapatalk
Click to expand...
Click to collapse
I had looked at those before, but I think they may have changed a little now and clarified things. If my current understanding is correct then Cherry Kang has the new board file referenced in the 12342 and gets some wifi benefits but this is a temporary measure. 12341 then refers to fundamentally replacing the drivers when more work has been done on them, hopefully leading to even better long term wifi support.
bobtidey said:
Which forum are you suggesting this should be in?
I know this is development but this thread was an attempt to pull out all the wifi related questions which are already being posted in the various development threads here. I thought that development was more appropriate as the main intention is to help and encourage the development of wifi to the point where the need for wifi support becomes much less.
Click to expand...
Click to collapse
WiFi has been beat to death in almost every thread in the development section, I encourage this thread and hope it can decrease the the clutter in the ROM threads.
mike-y said:
I was always told that the dev section is for software that you create - ROMs, kernels, tweaks, etc...
Click to expand...
Click to collapse
I have said this many times, and this is very true in most instances...however in this case I feel differently.
krook6023 (mod team)
Sent from my HTC_Amaze_4G using xda premium
This morning at work my wifi was dropping out more frequently than recently even using Cherry Kang build; it was lasting about 15-30 minutes.
It seems to be correlated with the probability of it connecting properly when wifi is toggled off and on. When it works it immediately says getting IP address. When it fails it delays and then just says saved. This morning this was happening 50% of the time and I had to toggle it off and on again a few times to get it to connect.
I suspect it is also something to do with re-activating the device from screen off even though I have wifi set to the default of never sleep.
So in the afternoon I left it on WiFi Analyser app with the setting to prevent the screen turning off. It stayed connected for 5 straight hours leading more credence to a theory that is somehow a re-connection on screen waking up that could be part of the issue.
Has there Ben any fix for the wifi issue? I'm almost ready to ditch Android on the tp and get a real tablet.
Have done some searching and have not found this exact issue. Sorry if its a repeat. Also please excuse typos. N7 keyboard and me don't always see eye to eye.
I own 2 32 GB N7s (well one is my gf's) . Both purchased refurbished at the same time on woot. Both upgraded to 4.4. Mine was very quickly unlocked and rooted. Mine has a custom recovery (forget which right now) and multirom. Only other ROM is ubuntu touch.
Mine will randomly disconnect from WiFi. The interval varies from less than a minute to more than 10 between disconnects. The stronger the signal the less it occurs, but it will occur right next to a router. It also seems to occurs (or is more noticeable) when doing things that require more bandwidth, such as streaming or loading heavy pages.
Most often it will reconnect on its own, but I can normally speed the reconnect by turning WiFi off and on or forcing the reconnect in settings. I have tried multiple routers, and other devices on the network (android phones, laptops,and the other N7) do not exhibit this behavior.
I did have to reeplace my USB jack. And I was inside the n7 one other time, it got dropped and would not boot. The battery had shifted and come partially unplugged. The issues started well before the port replacement, but the drop was to early in my ownership to tell if it was the cause. If it is I can only assume that it would be weak signal. Probably from removing the case and there being a poor connection to the antennas, but signal strength shows about the same as the other n7 when side by side.
There is a precourser to the drop as well. Data will stop before the WiFi indicator greys out. If you catch it and look at the notification area you can often see the send I dictator but no receive before the disconnect.
Anyone have any ideas? Are there any logs that may hold clues? It is annoying when streaming in house to have to reconnect multiple times during a show, and then often restart the stream and fi d your place only to have it happen again. Gaming suffers to. For email and browsing it is not a major issue,but I would still love to try to fix it.
Thanks!
Hi brad we are on the same boat . Wifi unstable but the other phone working good. Ive tried update to 4.4.3, and wifi connected very fast but the problem still there. But now i change my router to docsis 2.0 by cisco (rented from tv cable) and now its working great event sometime youtube still buffering. Before that i used tplink 941nd router.
I hope this wil help.
vs980
My Nexus 6P has the bootloader unlocked but is running completely stock, un-rooted, vanilla android (MDB08M). Project Fi is my carrier. When I am at home and on *most* wireless networks, I see no issue. While I am at work, my wifi constantly disconnects and reconnects. I will pick up my phone, and it will either A) not have wifi (though I have previously been connected) and quickly reconnects or B) Will have wifi, but after some amount of use, will disconnect from wifi, then reconnect a few seconds later.
I've tried all the simple items:
Making sure "Keep wifi on during sleep" or whatever the setting is is turned on
Turn off optimization on Google Connectivity Services
Forget network and reconnect
etc...
I turned on verbose wifi logs and was able to catch a logcat of when the issue occured. The disconnect occured at almost exactly 9:29:00, as I saw my wifi go out and then almost immediately after the clock tick 9:29.
I can't find anything in particular that stands out as the cause or leads to a solution.
I assume it is some misunderstanding between my job's wireless network and my phone. My previous phone (Nexus 4) had none of these issues. I am unclear on whether this is a Marshmallow issue, Project Fi issue, or what software might be causing it. Since it only happens on this certain network, I am making the assumption it is most likely software and not a faulty wireless chip. I have no control over the wireless configuration of the network, so anything on that end is a non-starter.
Any help or direction on where to look next is greatly appreciated!
Dropbox link to txt logs: https://www.dropbox.com/s/co95ov2u5kps23s/wifi_log_092855.txt?dl=0
I have exactly the same issue. It seems to happen mostly at work - my phone is locked laying on my desk for some time, and when I pick it up and unlock it, there is no WiFi connection but it reconnects after few seconds. It happens randomly as sometimes WiFi connection is there after unlock. It also happend at my home wifi network, though it's more rare at home.
I have two friends at work having Nexus 6P and they don't have this issue, so it looks like something wrong with my unit. I have 'Keep wifi on during sleep' turned on. Any ideas?
manalesar said:
I have exactly the same issue. It seems to happen mostly at work - my phone is locked laying on my desk for some time, and when I pick it up and unlock it, there is no WiFi connection but it reconnects after few seconds. It happens randomly as sometimes WiFi connection is there after unlock. It also happend at my home wifi network, though it's more rare at home.
I have two friends at work having Nexus 6P and they don't have this issue, so it looks like something wrong with my unit. I have 'Keep wifi on during sleep' turned on. Any ideas?
Click to expand...
Click to collapse
I haven't made much headway but I have filed an Android bug here: https://code.google.com/p/android/issues/detail?id=196035
It has the attention of the networking devs. Any further evidence (bug report!) you can provide there would be extremely helpful.
manalesar said:
I have exactly the same issue. It seems to happen mostly at work - my phone is locked laying on my desk for some time, and when I pick it up and unlock it, there is no WiFi connection but it reconnects after few seconds. It happens randomly as sometimes WiFi connection is there after unlock. It also happend at my home wifi network, though it's more rare at home.
I have two friends at work having Nexus 6P and they don't have this issue, so it looks like something wrong with my unit. I have 'Keep wifi on during sleep' turned on. Any ideas?
Click to expand...
Click to collapse
I'm seeing this same issue as well, I submitted logs to the bug report opened by cpswaim, but I wonder if this is a different issue and I should have opened a new bug.
]grimm[ said:
I'm seeing this same issue as well, I submitted logs to the bug report opened by cpswaim, but I wonder if this is a different issue and I should have opened a new bug.
Click to expand...
Click to collapse
If those are your bug reports, the error in the reports:
FAILURE: LOST_PROVISIONING, NeighborEvent{elapsedMs=94908702, 192.168.1.1, [(null)], RTM_NEWNEIGH, NUD_FAILED}
is the same error I'm getting. My phone disconnects while the screen is off, I've just also caught it disconnecting with the screen on too, so I'm under the impression our situations are related, if not the same.
Thank you for the bug reports!
cpswaim said:
If those are your bug reports, the error in the reports:
FAILURE: LOST_PROVISIONING, NeighborEvent{elapsedMs=94908702, 192.168.1.1, [(null)], RTM_NEWNEIGH, NUD_FAILED}
is the same error I'm getting. My phone disconnects while the screen is off, I've just also caught it disconnecting with the screen on too, so I'm under the impression our situations are related, if not the same.
Thank you for the bug reports!
Click to expand...
Click to collapse
Not getting this error in my reports, but experiencing the same issue on stock 6.0.1 rooted. Can't find any solution.
qtpa2tnh said:
Not getting this error in my reports, but experiencing the same issue on stock 6.0.1 rooted. Can't find any solution.
Click to expand...
Click to collapse
I wasn't getting that error either, one of the Google engineers on cpswaim's bug asked me to open a new bug report instead and I did so here: https://code.google.com/p/android/issues/detail?id=197272
]grimm[ said:
I wasn't getting that error either, one of the Google engineers on cpswaim's bug asked me to open a new bug report instead and I did so here: https://code.google.com/p/android/issues/detail?id=197272
Click to expand...
Click to collapse
Thanks for the link!
Since Greenify's Aggressive Doze feature is what caused my status bar clock to freeze last time I had an issue, I disabled Greenify but my wifi issue persists (although not as severe). I got a logcat and saved it right after the wifi dropped and reconnected, anybody with some knowledge who can see what's going on in there?
Edit: The general consensus online is that this is a Marshmallow issue. I don't have unlimited data so at home on wifi, this is a killer.
So I reflashed my stock boot image (6.0.1_r3 MMB29M), flashed FED Patcher, flashed the latest systemless root (2.64), and deleted the legacy directory Chainfire had made for old root apps that hardcoded to su (I deleted /su/xbin_bind) to get Android Pay working again...
My wifi issues have disappeared. I've seen a lot of reports saying the issue mysteriously resolved itself, but could it have been anything I just did?
Edit: Wifi is still randomly shutting off while the screen is off, but will even sometimes turn back on. The intermittent connection dropping is gone though.
This has been a constant issue for me starting with the Developer Previews on my Nexus 5 and has now moved onto my Nexus 6P.
i'm getting sick and tired of these little issues. google needs to fix this **** asap. such bull**** to have to deal with this crap
I had this issue on my home network with my Samsung devices. My tablets and TV would always drop off. My router was a cheap Asus model and was showing its age. I bought the brand new Asus router
"Asus - Extreme Wireless-AC2400 Dual-Band Gigabit Router - Black
Model:*RT-AC87R/U"
And I have not had a single drop since. Even on marshmallow. Now I know this isn't a cheap or reasonable fix but it seems maybe older hardware is to blame. YMMV
Gizmoe said:
I had this issue on my home network with my Samsung devices. My tablets and TV would always drop off. My router was a cheap Asus model and was showing its age. I bought the brand new Asus router
"Asus - Extreme Wireless-AC2400 Dual-Band Gigabit Router - Black
Model:*RT-AC87R/U"
And I have not had a single drop since. Even on marshmallow. Now I know this isn't a cheap or reasonable fix but it seems maybe older hardware is to blame. YMMV
Click to expand...
Click to collapse
Unfortunately this is the same router with which I am having problems as indicated in my bug report. I've also found at least a few other anecdotal accounts of problems with other Quantenna-based routers as well. The evidence seems to be fairly sparse though, so it's hard for me to draw a meaningful conclusion from what I've seen so far.
For whatever it is worth, I currently have another user with a Nexus 6P on 6.0.1 on my network on that device doesn't seem to have the same issues that I am seeing.
]grimm[ said:
Unfortunately this is the same router with which I am having problems as indicated in my bug report. I've also found at least a few other anecdotal accounts of problems with other Quantenna-based routers as well.
Click to expand...
Click to collapse
Well that's lame. I have had no problems since I got mine. I did get my own cable modem at the same time but don't see any connection there.
I'm guessing we're waiting on an update from Google?
My random disconnects have stopped, but wifi will still randomly shut off/turn back on in my pocket. Even in Safe Mode.
Flashing factory images and factory wiping haven't solved the problem.
Is anyone looking into this?
Edit: Even after the January security patch update, still having these issues.
It seems like my wifi issues have resolved themselves somehow.
FWIW, I was having a similar problem on my Sprint HTC One M8 after upgrading to Marshmallow. The problem happened on every wifi I would connect to... work, home, a friend's place, etc. After trying out several things, I finally fixed it by uninstalling "Sprint Connections Optimizer". I tried disabling it first, but every time I disabled it and went back into the settings, it appeared to still be enabled. So I'm not sure if disabling it was actually working.
To uninstall it, you need to go into "Manage apps" from your apps drawer to find it. I don't think it's listed with an icon in your usual set of stock and installed apps.
Posting this just in case no one has thought of it before, or someone knows something and hasn't spoken up. I have noticed a lot of people mentioning they only have this issue at work, and others who have "changed their router" and stopped the behavior.
I run a Cisco Wireless LAN Controller at home, with multiple APs (Cisco 1252 a/g/n). Typically this gives me better performance and stability than most consumer-grade stuff, but I have to wonder if there isn't a setting on this enterprise-grade stuff that is related to the disconnect issue, or if this is truly simply a Marshmallow bug. This could also be the common link with people who only have this issue at work, their work may be using Cisco enterprise Wireless gear.
I will do some more digging, I did have a spot in my house where my phone would randomly disconnect, turning on "Fast SSID Change" stopped that, so I am hoping there is something that might affect this disconnect while sleeping thing as well. I noticed my WLC reports my phone as being "Power Save Mode ON" in the client info page.
More to come if I discover something.
I have same issue at home, stock Nexus 6p and an AT&T router. Limited Data plan, so it's frustrating to be at home sitting 2' from WiFi router & drop off.
If people might say how they get their log errors & post them to Google, that'd be interesting reading.
I'm 90% sure this is a software bug. My wifi is consistent & always on, iPhones & Note 3, Roku, & PS3 have no problems connecting.
Please Google find this bug & patch it!!! (And while you're at it, re-enable Dark Theme setting!!)
REkzkaRZ. com
Add me to the list of people having this problem. I am between several different locations on a typical week and so far, the Cisco AP's by far have the most issues. In fact at my locations with Ubiquiti AP's, I have a perfect connection with no drops.
I really hope this gets resolved soon as well. Many applications are unusable when the WiFi does its drop and reconnect dance.