Related
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.
I have encountered an issue with the wifi connection on my nexus 7. When I go to connect to my home wifi, it claims that I have a link speed of 65 mbps, and yet it proceeds to either 1.)stop in the connection process after it gets to "obtaining ip address" and then it stops trying to connect and says"saved" or 2.) after several attempts it occasionally does connect and the connection speed is ridiculously slow (250kbps when compared to about 20-30 mbps on other devices). I encountered this problem some two weeks or so after the device's purchase. Before then I had no difficulties whatsoever. It was around the two week point when the connectivity got really slow and I had difficulties connecting. When I got the device it was running 4.1.2 jelly bean and since then I have updated to 4.2.1 jelly bean and this has not helped. I would greatly appreciate any suggestions as to why my connection is so slow and what I might do to fix this.
Additional information
My nexus 7 is running a stock rom, unrooted, locked
It is the 32gb model
My router is secured with wpa2
It will connect to other networks (including other networks with wpa2 security), it is only my default network which has a problem
Once again any input is appreciated and if you have any other questions please do not hesitate to ask
I had wifi issues several days ago (I'm into my second week since I bought it), with extremely low speeds or shoddy connectivity.
A couple of things I did:
1) Installed Wifi Analyzer from GooglePlay.
2) Using Wifi Analyzer, I figured out a wifi channel which wasn't so heavily used in my apartment (there's about 20 hotspots around me). 1, 6, or 11. I now use 11. This didn't work, but it might for you. Even if it doesn't, it's probably a good idea to set it to the least used channel anyway.
3) I reset my modem to factory settings and reconfigured everything. This fixed my speed and I now have 20-30Mbps consistently. What was different to my original configuration was two settings, which are disabled by default: Block Port Scan Detection and Block IP Flood Detection. Seems like I had inadvertently set these to enabled when I first got my modem. This might be the 'real' fix, but I'm not a networking expert. Maybe just resetting the modem fixed it for other reasons.
My current modem settings:
Mode: 802.11n 2.4GHz
Radio Band: Wide - 40 MHz Channel
Standard Channel: 11
Security: TKIP + AES
SSID Broadcast: Open
Hi.
Had my S5 since Tuesday but having really really slow WiFi.
Not sure why but need to switch back to 3G.
Any ideas why? Every other device can connect to my 100mbps connection via my Virgin Media Super Hub.
You gave us almost zero information so of course we have no idea. Rather than make a large list of possible causes, you should tell us a lot more about your configuration so that we can spot problems or narrow things down.
Look for patterns. Does this occur with all wifi connections? Have you tried wifi connections at work, coffeeshops and other places as well? If it is only on your router that should tell you a lot right there. What does your router log say? Even better, post a link to your router log or an excerpt thereof.
A snail's pace is a very vague description. Do a speed test and post that. Does the speed vary by the time of day? If this is a problem with your home router, try moving the router or changing the default channel. What mode (a,b,c,n) are you connecting in? How about a screen shot of your phone's wifi settings? You need to tell us a lot more about your phone and give us a detailed, step by step description of what you've tried so far if you are looking for good answers.
.
First my setup:
XT1572
TruPureXMM 2.6.3
frankenclark kernel 0.8
Is there anyway to connect to my homewifi faster? I've selected to only show 5ghz wifi networks and I'm only seeing two when I enable wifi yet it dosen't connect to my wifi for maybe 5-10 seconds. Is this a problem with the rom/kernel? I don't remember connecting being this slow when I was on stock 5.1.
If I can change connect speed through the rom/kernel that would be best. Otherwise is there an app that can do it?
Heaby said:
First my setup:
XT1572
TruPureXMM 2.6.3
frankenclark kernel 0.8
Is there anyway to connect to my homewifi faster? I've selected to only show 5ghz wifi networks and I'm only seeing two when I enable wifi yet it dosen't connect to my wifi for maybe 5-10 seconds. Is this a problem with the rom/kernel? I don't remember connecting being this slow when I was on stock 5.1.
If I can change connect speed through the rom/kernel that would be best. Otherwise is there an app that can do it?
Click to expand...
Click to collapse
i cant see why you would choose 5ghz over 2.4ghz maybe thats the reason for your problem
5Ghz allows for faster throughput (more bandwidth available) - uses 80 mhz channels vs 20 mhz on the 2.4ghz.
I noticed the slow connection too. Seems if you open wifi settings, it connects immediately.
Heaby said:
First my setup:
XT1572
TruPureXMM 2.6.3
frankenclark kernel 0.8
Is there anyway to connect to my homewifi faster? I've selected to only show 5ghz wifi networks and I'm only seeing two when I enable wifi yet it dosen't connect to my wifi for maybe 5-10 seconds. Is this a problem with the rom/kernel? I don't remember connecting being this slow when I was on stock 5.1.
If I can change connect speed through the rom/kernel that would be best. Otherwise is there an app that can do it?
Click to expand...
Click to collapse
Did you try changing the channel in your router?
Haven't tried changing the channel. Will report back after I get home after work.
Heaby said:
First my setup:
XT1572
TruPureXMM 2.6.3
frankenclark kernel 0.8
Is there anyway to connect to my homewifi faster? I've selected to only show 5ghz wifi networks and I'm only seeing two when I enable wifi yet it dosen't connect to my wifi for maybe 5-10 seconds. Is this a problem with the rom/kernel? I don't remember connecting being this slow when I was on stock 5.1.
If I can change connect speed through the rom/kernel that would be best. Otherwise is there an app that can do it?
Click to expand...
Click to collapse
I can say that problem is with ROM.
It has very slow auto connection time.
To connect faster I am using:
- drop down notification menu - tap wifi menu where its possible to choose wifi's from that setting - just wait, as soon as it turns on wifi and actually starts to scan area it will auto connect faster than when you just turn on wifi and wait.
I confirm this behavior on XT1575 as well. It takes quite a long time to connect when i enable WiFi.
But if I enter the WiFi settings, it connects instantly.
And i think it's like this since Android 6. I don't recall having this issue on Android 5.
I can't say I've noticed any problems connecting to WiFi networks at home.
I'm running 6.0 stock (Feb 2016 security update) rooted to hell and back.
I have access to five different WiFi networks at home, and am registered to all five for convenience.
I use an app called Best WiFi to auto-connect to the strongest signal whenever my current signal drops below a user-configurable strength threshold.
Perhaps that's the reason I'm not feeling this issue?
https://play.google.com/store/apps/details?id=com.pintacdesign.bestwifi&hl=en
I've been using this app for years, since Android 4.0, and across four or five different devices now.
Edit - Before the inevitable questions. I live in a basement and have my own personal WiFi network down there. Upstairs, we have two network piping out of the office (2.4 GHz and an associated 5 GHz link). For the far side of the home, we have a WiFi extender that mirrors and extends those two signals coming from the office (2.4 GHz-Ext and 5 GHz-Ext).
My report:
Whether connecting to 2.4 Ghz (20/40 Mhz) or 5 Ghz (20/40/80 Mhz) the connectspeed is between 5-15 seconds if singlepressing on the wifitoggle. If longpressed it takes about 2-3 seconds. Either this is a problem with the rom or this is the intended behaviour in Marshmallow. But this was not the behaviour in Lollipop as far as I remember. Of course you could argue this a nonissue since longpressing the wifitoggle is the solution. However I would like singlepressing to behave the same since I use Gravitybox to hide the statusbar when pressing 2-state tiles.
Yeah this is a huge pain in the ass. I set up a WiFi shortcut on my home screen so I would start using WiFI more to save battery, but it takes so long for it to finally connect. I also have Tasker turn WiFi on in the morning when my alarm goes off, and it takes so long. It took a few seconds in Lollipop, and now it takes 10+ seconds in Marshmallow. It's ridiculous. Anyway there is no real fix except going into the settings or tapping the drop-down toggle multiple times, as others stated.
I notice the same thing too. Wifi takes long to connect on boot. When I go to connect wifi off, it always shows the routers in the previous area before showing what's in the current area. I turn wifi off when leaving home. I'll connect to a public router, but will still show my home router before showing any around me. I had a Galaxy S5 before and wifi connected right away.
Heaby said:
First my setup:
XT1572
TruPureXMM 2.6.3
frankenclark kernel 0.8
Is there anyway to connect to my homewifi faster? I've selected to only show 5ghz wifi networks and I'm only seeing two when I enable wifi yet it dosen't connect to my wifi for maybe 5-10 seconds. Is this a problem with the rom/kernel? I don't remember connecting being this slow when I was on stock 5.1.
If I can change connect speed through the rom/kernel that would be best. Otherwise is there an app that can do it?
Click to expand...
Click to collapse
First off, I am not sure if the OP is turning wifi on first when arriving at home and then seeing the delay, or if Wifi is already ON when you arrive home (EDIT: just reread OP and it appears you are turning it ON - see below), but I leave Wifi ON all the time and do not see any delay when I get home (I pull into my garage and my apps are already updating via my home wifi before I park my car).
There are various steps involved in "getting onto wifi" that don't just involve the client device (authentication to the access point; getting an available IP address from your AP or a separate router, and the stability/software quality of those devices, for example). but you may want to consider a few things to speed up the process at home regardless if Wifi is on, or you turn it on first:
1) go into "Saved Networks" in your wireless settings and "forget" any networks you don't need
2) make sure the device on your network issuing IP addresses (DHCP server software built into your router or AP, whichever you use - also make sure only ONE of the them is acting as DHCP server) has enough available IP's in its pool - better yet, assign the same IP to your MotoX's MAC address (set up a static IP in your routers LAN/DHCP settings if it has them so your MotoX gets the same IP every time)
3) while I agree with another poster about avoiding the 2.4 GHz for Wifi (congestion and more interference), even many 802.11n client radios today don't support 5GHz so keep that in mind if you shut down 2.4GHz in your home completely
4) Use WPA2 with PSK for authentication AND make sure your home SSID is being broadcast (not hidden, which they really aren't anyway with the right tools - A strong WPA2 PSK password is better security even if the world can see your SSID.
4) If you do turn Wifi On and Off, consider leaving it ON and see if that helps your connection time (I suspect it will If you are concerned about battery drain, you can disable wifi during sleep in wireless settings, but I don't have a battery issue with Wifi on 24/7. The Wifi radio beaconing for SSID's or even staying connected to an SSID in the background, when you're not using Wifi, is a very minimal power drain compared to having your screen brightness higher than you need (you can however turn off the annoying wifi network notification setting).
Hope this helps.
For those with this delay, are you running xposed with gravitybox? Tried disabling gravitybox? It maybe GB that's introducing the delay. Need feedback from those running stock.
If stock exhibits similar behavior then it's probably characteristic of the quick toggles in the moto x. The delay appears to be in the actual wifi connection phase, not acquiring ip. As once it actually connects, IP acquisition is almost instant. Toggling wifi off then on directly through settings is very fast, maybe 3-4 seconds.
I have a moto g lte (xt1045) on cm13 which takes about 5 seconds to connect after toggling wifi off then back on. The moto x takes a good 15 seconds.
ech1253 said:
First off, I am not sure if the OP is turning wifi on first when arriving at home and then seeing the delay, or if Wifi is already ON when you arrive home (EDIT: just reread OP and it appears you are turning it ON - see below), but I leave Wifi ON all the time and do not see any delay when I get home (I pull into my garage and my apps are already updating via my home wifi before I park my car).
There are various steps involved in "getting onto wifi" that don't just involve the client device (authentication to the access point; getting an available IP address from your AP or a separate router, and the stability/software quality of those devices, for example). but you may want to consider a few things to speed up the process at home regardless if Wifi is on, or you turn it on first:
1) go into "Saved Networks" in your wireless settings and "forget" any networks you don't need
2) make sure the device on your network issuing IP addresses (DHCP server software built into your router or AP, whichever you use - also make sure only ONE of the them is acting as DHCP server) has enough available IP's in its pool - better yet, assign the same IP to your MotoX's MAC address (set up a static IP in your routers LAN/DHCP settings if it has them so your MotoX gets the same IP every time)
3) while I agree with another poster about avoiding the 2.4 GHz for Wifi (congestion and more interference), even many 802.11n client radios today don't support 5GHz so keep that in mind if you shut down 2.4GHz in your home completely
4) Use WPA2 with PSK for authentication AND make sure your home SSID is being broadcast (not hidden, which they really aren't anyway with the right tools - A strong WPA2 PSK password is better security even if the world can see your SSID.
4) If you do turn Wifi On and Off, consider leaving it ON and see if that helps your connection time (I suspect it will If you are concerned about battery drain, you can disable wifi during sleep in wireless settings, but I don't have a battery issue with Wifi on 24/7. The Wifi radio beaconing for SSID's or even staying connected to an SSID in the background, when you're not using Wifi, is a very minimal power drain compared to having your screen brightness higher than you need (you can however turn off the annoying wifi network notification setting).
Hope this helps.
Click to expand...
Click to collapse
gpz1100 said:
For those with this delay, are you running xposed with gravitybox? Tried disabling gravitybox? It maybe GB that's introducing the delay. Need feedback from those running stock.
If stock exhibits similar behavior then it's probably characteristic of the quick toggles in the moto x. The delay appears to be in the actual wifi connection phase, not acquiring ip. As once it actually connects, IP acquisition is almost instant. Toggling wifi off then on directly through settings is very fast, maybe 3-4 seconds.
I have a moto g lte (xt1045) on cm13 which takes about 5 seconds to connect after toggling wifi off then back on. The moto x takes a good 15 seconds.
Click to expand...
Click to collapse
@ech1253: I've checked everything you suggested and you are right, having wifi on will make it connect almost instantly.
@gpz1100: I'm running xposed with gravitybox. Disabling gravitybox didn't change anything. I'd rather not uninstall xposed and/or go back to stock so if someone on stock without xposed could chime in that would be helpful.
It does it on stock android 6 for me and on a custom rom as well. Since day 1 with the moto x but at least wifi works just a long delay that no other android flagship from suffers from. :S
hexxor93 said:
It does it on stock android 6 for me and on a custom rom as well. Since day 1 with the moto x but at least wifi works just a long delay that no other android flagship from suffers from. :S
Click to expand...
Click to collapse
That's...not encouraging
Hopefully it's a softwarebug.
So I may have come across something that may help someone else out as well...
Recently (as in less than 15 days) purchased a oneplus 8 pro from oneplus.com. When I first got it it was on android 10 and I was not able to connect to either my 2.4ghz wifi or my 5ghz wifi using WPA2. I had a oneplus 7 pro previously that still connects without issue. I had read elsewhere that the open beta was better so I tried that and it indeed was better but sometimes though I was connected to the wifi, no traffic would travel over the network and it would stall to the point that the only way I could do anything internet or network related was to go to my cellular data. I did the 'device mac' as opposed to random mac and that helped for a brief time however that even cause the same stall/lack of response issues.
Since I don't have much for 5g cellular where I am, I changed it to only look for 4g....still no improvement. On a whim, I disabled any and all security on my 5ghz wifi and low and behold I could connect. I wasn't about to leave either of my wifi networks wide open but also remembered the network I connect at work is also not wpa or any sort of protection so theres a hint as to how to 'fix' these issues. I then read someone about the possibility of having special characters in your wifi password can cause issues. I removed the ! in my old wifi password so it is now alpha numeric and have had no issues with my 5ghz wifi network. I have been able to stay connected with my 5ghz wifi WHILE bluetooth has also been abled and the speeds are roughly normal.
Try at your own risk but in summary:
1. upgrade to the open beta 2
2. disable 5g cellular connections
3. connect to your 5g wifi and make sure the password has no special characters in it as well as use device mac NOT randomized mac
4. perhaps success
With all the above being said, I do still intend on sending this phone back in hopes that I got a dud unit but I'll admit seeing these results makes me feel like its more of a software issue and certain incompatibilities with certain routers.
Just dropping what info I have discovered in hopes it helps someone out there...I would not normally endorse using NO password on wifi or a weak password, but for this phone it may be a requirement at least until the updates can come into play.
Thanks,
E|
I am backing everything up to go to Android 11 tonight, and I switched to a new WPA2/WPA3 router here, but my password has no special characters.
On Android 10, complete nogo, as using WiFi calling with a BT headset on 5ghz slows the network down so much, the other person can't hear you (no upload bandwidth).
I'll let you know how Android 11, OB2 works out for me.
If there are issues, I am going back to the OnePlus 7 Pro and selling the OP8 Pro.
Since I have not been using WiFi, I blew through 55Gb of data this month already so am subject to throttling, thanks OP8 Pro
MetroWestMA said:
I am backing everything up to go to Android 11 tonight, and I switched to a new WPA2/WPA3 router here, but my password has no special characters.
On Android 10, complete nogo, as using WiFi calling with a BT headset on 5ghz slows the network down so much, the other person can't hear you (no upload bandwidth).
I'll let you know how Android 11, OB2 works out for me.
If there are issues, I am going back to the OnePlus 7 Pro and selling the OP8 Pro.
Since I have not been using WiFi, I blew through 55Gb of data this month already so am subject to throttling, thanks OP8 Pro
Click to expand...
Click to collapse
You could try om a different router of someone else to pin point out if it's your router yes or no.
Sent from my IN2023 using Tapatalk
I did upgrade to OB2 a few days ago and wifi is generally better. But VOWiFi never works with a bluetooth headset - the other person can never hear me.
Also when streaming over WiFi the connection drops or stalls and causes rebuffering. I have confirmed these behaviors with 3 different routers.
Can anyone on TMobile (USA) confirm working VOWiFi while using a bluetooth headset?
Also 4G and 5G speeds slow down when on a call using bluetooth.
Maybe this is all due to qualcomm 865 chipset issues as the galaxy S20 users are having similar issues?
I had faced lots of stability and speed issues on the 5gz band. Received the OS11 update today and my issues seem to be resolved. So far the 5gz connection has been very stable, lightening fast speeds.