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.
Related
Sorry I know this problem probably has been brought up many times. But here I just want to make a total one and collect all the feedbacks from N1 users regarding to the wifi sleep issue with N1.
Let's just make it simple: Every N1 owner PLEASE DO test out the wifi connection when your phone goes to sleep as there are MANY people suffering from this problem all over the world. Especially the later buyers since February this year, almost every phone is potential to this problem.
######################################################
Diagnosis:
1. Set the wifi sleep setting to "never" in the wifi advanced setting menu.
2. Turn on Last.fm app(or Pandora, but Last.fm is most effective and responsive one to test it out), leave the phone on wifi and turn off the phone screen or let it goes to sleep.
3. The symptom is the app will stop streaming shortly afterwards(with Pandora stops maybe after one song, for which I suggest everyone test it for at least 15 minutes). Also most likely you will stop getting any email notification or anything requires data connection. And you might not be able to ping your phone or the ping responses VERY slow as well.
######################################################
######################################################
Background:
This problem was recorded from earliest almost 6,7 months ago and has affected both AT&T and T-Mobile versions(with reports of the same issue on other versions sold outside US). So far, it's suspected that the problem mostly likely lies in the lower level architecture of the phone(either software or hardware) because the problem still exists even after people has replaced the stock ROM with the custom ROM. Another proof is that people get problem with brand new phone and also the replacement phone. Another note is the problem has been found both before FROYO update and after. At this moment, there's no official fix(some Google employee blatantly brushed the issue away and asked N1 users to get over it, check out the link below for original conversation) for this issue except a work around thanks to wifi fixer app developer.
######################################################
This issue is often times neglected by N1 users because usually people don't use the phone on wifi all the time or they simply switch between 3g and wifi. But for people who use wifi a lot or use VOIP, it could be a real deal breaker.
So here I just hope everybody could test your phone out and see if you have this issue or not. Please report how your result turns out in this thread. Also, for further and more detailed discussion and cases, please check this out:
http://www.google.com/support/forum...52&hl=en&fid=01a47ff5b0a92d5200048be07b6cb5c1
You are more than welcome to add your experience to the discussion above so hopefully it can wake google up.
####################################################
UPDATE:
So Broadcom just released a wifi driver fix several days ago which may solve this issue. According to the record, phones with non-zero MAC address suffer from problem.
The driver has been incorporated into the latest Cyanogenmod(either RC or nightly build). People are reporting it fixes the problem while in some other cases, the problem still exists even after the fix, even for people who's MAC address starts with 00.
Last.fm works fine with the screen off here, always has done. I even turned off mobile data to be sure it's not switching over to that.
This is with the wifi set to sleep with the screen off (ie. the default setting).
i've been using wifi fixer and since i installed it, i haven't had a single wifi disconnect on my home network(it seems to be a network dependent issue as i never have issues on other networks)
Jep4444 said:
i've been using wifi fixer and since i installed it, i haven't had a single wifi disconnect on my home network(it seems to be a network dependent issue as i never have issues on other networks)
Click to expand...
Click to collapse
But you did have the problem before you installed wifi fixer, right?
Rusty! said:
Last.fm works fine with the screen off here, always has done. I even turned off mobile data to be sure it's not switching over to that.
This is with the wifi set to sleep with the screen off (ie. the default setting).
Click to expand...
Click to collapse
yeah, the point here is that many phones have the wifi sleep policy issue(doesn't work).
Indeed, however mine does, so this thread will need both sides of the argument
No problems on my Nexus One, running latest CM 6 nightly build.
I bought it couple months ago from eBay, so I'm not sure which shipment it is from.
Only issue I'm having after upgrading to Froyo is that my phone won't connect to my home network by itself when in range.
I have to go into Wifi Buddy and manually connect. This never happened on 2.1, but magically started after the FRF50 update, and never fixed itself in the next couple of builds.
Forge94 said:
Only issue I'm having after upgrading to Froyo is that my phone won't connect to my home network by itself when in range.
I have to go into Wifi Buddy and manually connect. This never happened on 2.1, but magically started after the FRF50 update, and never fixed itself in the next couple of builds.
Click to expand...
Click to collapse
I have always had this same issue! Maybe its something to do with my home wifi? I am yet to test it on froyo.
I am mostly connected to wifi with no sleep issue.
I have kind of the same issue at home, I recently replaced my wireless router, I never had problems connecting to the old one it would just stop broadcasting constantly but my N1 would always connect automatically. With the new router my N1 keeps saying the connection is disabled and I have to connect manually. This never happens at work, it always connect automatically so it seems to have something to do with the router settings but I have no idea what.
No problems here. Last.FM works fine for me on WiFi when screen is off. I also get notifications. Running FroYo rooted with locked bootloader
Sent from my Nexus One using XDA App
Divster said:
I have always had this same issue! Maybe its something to do with my home wifi? I am yet to test it on froyo.
I am mostly connected to wifi with no sleep issue.
Click to expand...
Click to collapse
i am having the same problem, when i go out of range from my wireless and then back in range, the n1 just says scanning and never re-connects.
that said, using a channel lower than 11 on my router did seem to help with the sleep issue.
hbkmog said:
But you did have the problem before you installed wifi fixer, right?
Click to expand...
Click to collapse
sorta, i never had the issue on any network besides my home one
I've also been having the disconnect problem with my N1. Maybe it would help if people whose sleep policy is actually working could post what wifi router/AP/whatever they are using. Also, if possible the first for identifiers of their MAC address. I read on one of the Google posts someone with a MAC address starting with 38:E7 having problems. The MAC for my phone is the same. For what it's worth I'm using a D-Link DIR-655 router and a Speedtouch 716 v5 WL and am experiencing the disconnect on both.
I've had the issue with 2 N1 tested on 3 different routers. I've read that it is related to the low power mode the N1 uses while sleeping not playing nice with routers. Not all N1 show the problem, apparently only the most recent ones. I've called google support and was told google knows about the issue and is working on it, but I am a bit cynical and I'll believe it when I see a fix.
Wifi-fixer fixed my problem only after I disabled Sipdroid which was interfering with it.
Mac adress: 38:E7: D8
I'll post my router model later when I get home.
Divster said:
I have always had this same issue! Maybe its something to do with my home wifi? I am yet to test it on froyo.
I am mostly connected to wifi with no sleep issue.
Click to expand...
Click to collapse
williec30 said:
i am having the same problem, when i go out of range from my wireless and then back in range, the n1 just says scanning and never re-connects.
that said, using a channel lower than 11 on my router did seem to help with the sleep issue.
Click to expand...
Click to collapse
as a quick update... i installed wifi-fixer and things have been much better. will report back if things start to derail again.
cabreca said:
I've also been having the disconnect problem with my N1. Maybe it would help if people whose sleep policy is actually working could post what wifi router/AP/whatever they are using. Also, if possible the first for identifiers of their MAC address. I read on one of the Google posts someone with a MAC address starting with 38:E7 having problems. The MAC for my phone is the same. For what it's worth I'm using a D-Link DIR-655 router and a Speedtouch 716 v5 WL and am experiencing the disconnect on both.
Click to expand...
Click to collapse
D-Link DIR-615 with DD-WRT v14684, phone's MAC starts 00:23
It's weird because most of the time I don't have this problem. My WiFi stays connected all night long to WiFi. But once in a while it does disconnect and switch to 3g. I think its certain routers, because I didn't have this problem for first 3 months on my old router, now it happens with my new router.
My phone never has trouble reconnecting back to WiFi. Everyday when I come home from work, as I walk up my driveway the phone has already automatically connected to WiFi. I've made sure about this one since I read this problem all over.
I bought my Nexus One directly from Google when it came out for AT&T. It certainly has the wifi issue and it is very annoying. My expectation is that the phone jump on my wifi network when in range as all of my other phones have done. Instead I have to manually engage the phone to get on wifi. SUCKS!
this is the biggest problem for me with my n1.
although the wifi does stay awake, it slows right down..
if i ping my phone, the response time increases when the phone is asleep, but doesnt time out.
if i ftp a file from my laptop to my phone, the speed drops from 1mb/sec to 100kbps/sec when the phone is asleep.
i have found the app "fix my wifi" solves the problem of waking the phone after a few hours of sleep and finding the wifi has failed. if only there was a way of getting the speed to stay the same.
My wifi is spotty, at best. I've tried every ROM but every ROM has the same issues: wifi will work for awhile, then it won't, then I power the phone off, then it doesn't work after I power it back on, then I disable it and re-enable it, and it may/may not work. Basically, it's totally unreliable.
I AM running a 2.4 mouse/keyboard combo, but I've tried different channels on my router: 1,6,11 ... they all have issues. My router is a D-LINK 615 and supports 801.11b-n.
I have an iPhone and it is rock solid on the wifi; plays nicely with the keyboard and mouse and doesn't miss a beat. But I REALLY want my HD2 to work: it's more baddass!
Can anyone help me out?
by not working, could you be more detailed? coz if the problem is about wifi went to sleep state after you lock the phone, then there's a settings for that.
danxtian said:
by not working, could you be more detailed? coz if the problem is about wifi went to sleep state after you lock the phone, then there's a settings for that.
Click to expand...
Click to collapse
Where's the setting?... I must have missed it! I can restart the phone and get the wifi symbol, but the reception bars aren't fully lit... only the very lowest (I'm on a sense build now).
I go into wifi settings and it says 'connected' ... but I try to load the browser, or marketplace, or Amazon AppStore ... and I'm not connected. I disable wifi then I renable it and my wifi bar is full! And the wifi works for, maybe, 30-45 seconds before it doesn't work again.
Really, really odd. And this is how it behaves on all ROMs I've tried.
*EDIT* I just saw that my wifi sleep policy is set to 'never' go to sleep.
I just turned on "best wi-fi performance" but I have my doubts that it will work... and my battery is going to suffer, big time.
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Thanks! Help installing a new kernel...
linj said:
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Click to expand...
Click to collapse
Hrmm.... I've been searching high and low for a good kernel and was thinking it might be the issue. I found g.lewarne's kernel http://forum.xda-developers.com/showthread.php?t=917590 ... but I have no idea how to apply it to my current build: http://forum.xda-developers.com/showthread.php?t=1027768
Is it possible to apply the g.lewarne kernel to CME Desire HD2?
linj said:
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Click to expand...
Click to collapse
I just flashed g.lewarne's GL_CORE_V5 from here:
http://forum.xda-developers.com/showthread.php?t=917590&highlight=reboot
... I flashed the whole ROM and I'm getting zero wifi. Even with the other kernels I was able to get some wifi, but none with this one. I like the ROM look a lot, but nothing doing on the wifi front.
Anyone else have suggestions??
WPA vs WPA2
Make sure you set ONLY WPA and TKIP in your router settings... I have much more reliable wifi because of this.
Also, choose specific wifi channel ... channel 6 works for me, and I've seen channels 1 and 11 as recommended channels as well.
Mixed WPA/WPA2 and TKIP/AES modes were horrible for wifi
FYI!
My ROMs are working relatively well now... much better than mixed modes (no wifi working)
diznanl said:
Make sure you set ONLY WPA and TKIP in your router settings... I have much more reliable wifi because of this.
Also, choose specific wifi channel ... channel 6 works for me, and I've seen channels 1 and 11 as recommended channels as well.
Mixed WPA/WPA2 and TKIP/AES modes were horrible for wifi
FYI!
My ROMs are working relatively well now... much better than mixed modes (no wifi working)
Click to expand...
Click to collapse
Ah. Unfortunately I have little control over the wifi infrastructure on campus (I'm in a college environment). That said, I'm not connected to the WPA2 Enterprise ssid but the unencrypted one.
Good to hear you found a resolution!
I have found that WiFi works just as good as my laptop when I'm running Windows Phone 7. Much faster at connecting and can connect further to the edges of signal then Android. I wonder why this is.
I've had my Transformer for about 2 months now and my WiFi connection has always been reliable and robust, but ever since the last OTA update (8.4.4.11) it's gone flakey. I know the problem is not my wireless router since WiFi was working great before the update and I have lots of other devices that connect without any issues.
At least once or twice a day after resuming from standby, the WiFi icon stays dark and no amount of trying to reconnect will get it back. After a few tries, I can actually watch the checkbox for WiFi settings toggle on and off repeatedly by itself.
I've tried changing the WiFi disconnect policies, closing down apps, and stopping non-critical processes but the only thing that fixes the issue is to power down and restart. WiFi will then work for awhile but eventually goes out again.
Anyone else seeing this?
I have the same problem
Sent from my PC36100 using XDA Premium App
same thing here =/
same here and i'm getting piss off at the fact that new updates is screwing over my wifi connection.
FWIW - it's also discussed in these 2 threads and is worked around by giving your TF a static IP. Not ideal, I know, but at least it will get y'all working.
http://forum.xda-developers.com/showthread.php?t=1041502
http://forum.xda-developers.com/showthread.php?t=1190896
there has been issues with other tabs and OTA upgrades with WIFI. Try brouse in the A500 forums. There was a file to delete that fixed the issue. Must have root access.
41 UOTE=cvfl;16258699]FWIW - it's also discussed in these 2 threads and is worked around by giving your TF a static IP. Not ideal, I know, but at least it will get y'all working.
http://forum.xda-developers.com/showthread.php?t=1041502
http://forum.xda-developers.com/showthread.php?t=1190896[/QUOTE]
That's kewl and all but what if you connect to different AP's during the day. I access through my EVO 4G while at work and then access my home network when I get home. This may or may not work. I'll have to see when I get my TF on Thursday. Thanks for the quick links though.
You can also increase the dhcp lease time in your wireless router, it also works for me.
AcIdC0R3 said:
... but what if you connect to different AP's during the day.
Click to expand...
Click to collapse
Download WiFi Analyser, which will show you, which IP data you need for static configuration.
cvfl said:
FWIW - it's also discussed in these 2 threads and is worked around by giving your TF a static IP. Not ideal, I know, but at least it will get y'all working.
http://forum.xda-developers.com/showthread.php?t=1041502
http://forum.xda-developers.com/showthread.php?t=1190896
Click to expand...
Click to collapse
Not exactly the same issue and I already set up static IPs for all the devices (32 of 'em!) on my wireless network long ago.
I did find that one particular app was probably the cause (PCFile Sync) and since replaced it with another having similar functionality, but I still very occasionally lose WiFi and have to reboot.
Tigrev said:
Not exactly the same issue and I already set up static IPs for all the devices (32 of 'em!) on my wireless network long ago.
I did find that one particular app was probably the cause (PCFile Sync) and since replaced it with another having similar functionality, but I still very occasionally lose WiFi and have to reboot.
Click to expand...
Click to collapse
I've been following this issue since I started having it on the 3.1 update when I unboxed the thing, so I'd really like to understand what issue you found with PCFile Sync, or at least what led you down that road.
Up to this point because of my specific goings on I've been thinking it was more a DHCP/routing issue and not in fact a WiFi/connection issue - i have strong connection before and after whatever the event that shuts things down is, just no traffic.
A little more info here as well - http://forum.xda-developers.com/showthread.php?t=1191792
cvfl said:
I've been following this issue since I started having it on the 3.1 update when I unboxed the thing, so I'd really like to understand what issue you found with PCFile Sync, or at least what led you down that road.
Up to this point because of my specific goings on I've been thinking it was more a DHCP/routing issue and not in fact a WiFi/connection issue - i have strong connection before and after whatever the event that shuts things down is, just no traffic.
A little more info here as well - http://forum.xda-developers.com/showthread.php?t=1191792
Click to expand...
Click to collapse
The behavior I described in my initial post (watching WiFi toggle on and off in settings) seemed to suggest something was blocking or interfering with the normal connection after resuming from standby (I have my WiFi disconnect policy set to turn off WiFi when the display is off).
So I just started closing down apps that had WiFi access and when I killed PCFile Sync (which I use to sync files between the TF and an NAS), the problem went away. I'm now using FolderSync Lite which doesn't seem to cause any issues, although on rare occasions WiFi will still loop for awhile before connecting.
This never happened in HC 3.1 so I think it's a vulnerability in 3.2 under certain conditions ... and those not using a static IP on their LAN are probably seeing something similar happen.
You know, after using my TF after the update, I think what this wifi bug is really just a fix gone wrong. Maybe it's some condition set to turn on wifi only when in use (to save battery life, or allow certain tablets that won't go into deep sleep to go into deep sleep or something like that) but it's set with some super sensitive conditions that make it turn off unless there is an actual request for internet?
My bar goes from blue to grey/white after a minute or something, but I can seem to always access some webpage when I click it from an app. Hmm.
Tigrev said:
... something was blocking or interfering with the normal connection after resuming from standby (I have my WiFi disconnect policy set to turn off WiFi when the display is off).
Click to expand...
Click to collapse
This happens to me with 3.1 randomly, though my policy is set to keep WiFi alive and I never used this PCSync app.
In my opinion the Android Broadcom WiFi card driver is buggy, because the SGS2 with android 2.3.3 has similar problems and also a Broadcom card.
So I guess it has nothing to do with the Android version, but is a buggy WiFi driver. I remember, that I had similar problems with an Intel card in a Toshiba notebook years ago and it was fixed with a driver update.
The question is, who develops the drivers, Google's Android team or Asus & Co? I guess the later? If it are the manufacturers, I find it strange, that Samsung has similar issues.
+ 1 on this very frustrating bug; since upgrade to 3.2 it happens every now and then ; as I did not install any new Apps I assume that this is just a very annoying 3.2 bug...
Anybody with any solution plz?
bmszabo said:
Anybody with any solution plz?
Click to expand...
Click to collapse
A german TF owner reported in a german Android forum, that he phoned Asus support about all well known 3.2 issues and they told him, that a firmware fix will be released by OTA next week.
Knock on wood that this is true.
So far ... static IP.
Aymara said:
This happens to me with 3.1 randomly, though my policy is set to keep WiFi alive and I never used this PCSync app.
Click to expand...
Click to collapse
Me too, before I static IP'd the TF.
Aymara said:
In my opinion the Android Broadcom WiFi card driver is buggy, because the SGS2 with android 2.3.3 has similar problems and also a Broadcom card.
So I guess it has nothing to do with the Android version, but is a buggy WiFi driver. I remember, that I had similar problems with an Intel card in a Toshiba notebook years ago and it was fixed with a driver update.
The question is, who develops the drivers, Google's Android team or Asus & Co? I guess the later? If it are the manufacturers, I find it strange, that Samsung has similar issues.
Click to expand...
Click to collapse
I have had several other problems with Broadcom WiFi drivers, so this doesn't shock me at all.
cvfl said:
Me too, before I static IP'd the TF.
Click to expand...
Click to collapse
I always use static IPs.
I have had several other problems with Broadcom WiFi drivers, so this doesn't shock me at all.
Click to expand...
Click to collapse
I feared, that someone would say this
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.
Curious to know if the community is having tethering issues since going to Nougat.
Tethering does turn on and it does work to an extent but it'll either turn off whenever it wants or it'll simply stop serving requests. There is not a set amount of time for either before experiencing the issue. I'm pointing this issue directly at the tethering aspect as the phone will always browse and do anything as expected even tho the tethering clients are unable to. Even when the clients are unable to browse I can still ping the exact website that will not load. I can even curl those pages and get data back..
Here's what I've tried:
- Disabled adblocker on the phone
- Kept phone awake
- Connected to the charger
- Disconnected from the charger
- added net.tethering.noprovisioning=true to the build.prop
- Nuked and paved with different ROMs
Going to try installing a different tethering app to see if that works. UPDATE: This also produced the same results
I can connect to another 6p not running nougat and everything works as expected with the same computer so that rules out the computer.
Anyone else running into this issue? Anyone have a fix?
Thanks
What carrier are you on? Does hotspot work ok?
v12xke said:
What carrier are you on? Never had any issue on AT&T and use it extensively. Stock rom, rooted, EX kernel.
Click to expand...
Click to collapse
Verizon also using EX kernel. It's almost like some sort of cache fills up
Thank you!!! I thought it was just my phone hardware maybe. Having the same exact issue once I hit the official version of nougat. It didn't pop up until I believe thr 5th developer release as an issue. It really annoys me either streaming or online gaming it'll just cut out. I am really close to just going back to one of the developer previews that it did not occur on. Please anybody who can fix this issue or needs anything like a logcat, let me know.
DragonRyderX said:
Thank you!!! I thought it was just my phone hardware maybe. Having the same exact issue once I hit the official version of nougat. It didn't pop up until I believe thr 5th developer release as an issue. It really annoys me either streaming or online gaming it'll just cut out. I am really close to just going back to one of the developer previews that it did not occur on. Please anybody who can fix this issue or needs anything like a logcat, let me know.
Click to expand...
Click to collapse
What carrier are you on? Tethering can mean Wi-Fi, USB, or BT. I guess you are talking about the Wi-Fi hotspot because it's the most commonly used. My Wi-Fi hotspot is working fine on AT&T, although I haven't used it for gaming. Haven't heard back from OP, but I think he may be talking about Wi-Fi as well? You could try changing frequencies under advanced settings to toggle the hotspot to use 5Ghz instead of 2.4Ghz if you haven't tried that (and your equipment supports it).
I was having same issue also running latest PN, EX 4.04, radio/bootloader & vender.
This seemed to help but just started yesterday.
In Terminal Emulator, enter below code one by one:
su
settings put global tether_dun_required 0
exit
------------------------------------------------------
Reboot
Now if I could figure out how to stop adding a network every time I connect to hotspot with cp when I turn hotspot off & back on.
I'm thinking this could me a Verizon unlimited thing since not many people have anymore & very few people have stated issues.
Update: The above is not going to cut it! Hotspot seems to hang on longer but still disconnects!
I have Verizon, and yes, I am speaking to*Hotspot tethering. I have this issue only on Nougat. When I use a*Marshmallow based rom it doesn't happen. I use my hotspot as my home internet (laptops, smart tv, tablets, smartphones) and all of them drop connection after random intervals (most times after an hour to few hours). Not until the DPs for 7.1 did a change in the way it failed happened. Before those DPs, it would shut off and the notification icon would disappear (hotspot actually off). After*the DPs for 7.1 started, the tethering would still be on (on the*6P) but no device would show that it was on (in range). I have to shut it off, then*turn it back on. I use stock, Cortex or PN mostly. Root or no root. I also do not use custom kernels unless they come with the rom, although I have tried a couple to see if it would fix it. It didn't.*I have always attributed it to either faulty hardware somehow or DOZE improvements that kicked in. The DOZE came to mind as it almost seems as the phone is trying to*get into deeper sleep. I don't know. Any help would be appreciated.
Same issues with pixel, some said it works others did not.
https://forum.xda-developers.com/pixel-xl/how-to/root-guide-native-hotspot-t3493286
Yes for wifi tethering.
Well cannot seem to find anything on disconnect solving issues, posted solutions seem to be if tethering does not work at all.
Hope someone can solve.
crackerjack1957 said:
Well cannot seem to find anything on disconnect solving issues, posted solutions seem to be if tethering does not work at all.
Hope someone can solve.
Click to expand...
Click to collapse
Did you try toggling hotspot to use 5Ghz instead of 2.4?
v12xke said:
Did you try toggling hotspot to use 5Ghz instead of 2.4?
Click to expand...
Click to collapse
Laptop I'm using only does 2.4.
Was never a problem with the HTC M8 on MM, just recently bought the 6P.
Thanks
Had another laptop that had that had a 2.4 / 5Ghz dual wireless card.
Holds wifi hotspot with no disconnects whatsoever, longest time connected was 2.5 hours.
I will have to settle for usb tether on the 2.4 laptop for now until the wiser ones can find cause.
Just ran into this issue on the 6p running 8.0 beta 3. Seem related to the data encryption of the wifi hotspot. Turning encryption seems to solve the problem. However, I would say that is not really a solution, unless you don't running unsecured hotspot.
Edit: Turns out it only helps. Not a solution. Still disconnects just not as often often.
Deleted