Related
Hello all,
I love my X10, but the frustration with getting it to connect to my Netgear DG834 router was getting to me, so I dedicated an afternoon to working out a solution and I've found one that works for me, so I hope it'll work for you too.
Summary of problem
--------------------
The phone will connect to the Router once, and once only. Any attempt to re-connect to the wifi will result in the phone disconnecting, scanning again, then discinnecting until the user gives up. Nothing will cause the phone to reconnect (telling it to forget the connection for example). The only surefire way to reconnect is to reboot the router each time - not ideal.
Manually adding a Static IP also doesn't work - which is weird as that is how I've solved it, see below.
Scale of problem
----------------
The problem seems to be with the router and not necessarily the phone as it appears to be on a wide range of phones (Hero, Droid, Touch HD etc.). Seeing at the DG834 is the most popular router in the world, and Android is growing all the time, there are a large number of people affected.
However Iphone and Symbian phones appear to be unaffected.
Reason for the problem
-----------------------
Currently unknown, but appears to be something to do with the handshaking procedure when a device asks the router for an address (DHCP) - though as to what I don't know.
Solution
--------
1) Download an app called WiFiStatic from the App Market. WiFiStatic takes each DHCP assigned IP address and stores it in a small database to be re-applied whenever you are back in range of the same Router again. It is not an ideal solution as you may have to re-scan and re-assign if you visit a busy hotspot, but this is a two press function, so it's not that onerous.
2) Turn off your Router. Make sure the WiFi on your phone is off too.
3) With the router off, clear your Remembered WiFi connections (or at the very least the Netgear connection). Once that's done, turn the Router on again and wait until it is full back up again.
4) When the Router is fully operational again, turn on your wifi on the phone and let is scan for and connect to the Netgear Router. You may need to tell it to connect from the Wireless Settings menu on the phone.
5) The phone should now connect to the Router successfully. If it doesn't, repeat the above procedure.
6) With the phone connected to the router, fire up WiFiStatic. Check Auto Switch and Show Visual Prompt if they are not already selected, then Tap Add configuration at the bottom of the screen.
7) The IP address and other settings assigned by your router should be displayed at the top of the screen, at the bottom should be the name of your router and its MAC address. If not then tap Menu > Generate to populate the form.
8)Tap Menu > Done when everything is ok.
That's it. Now when you move into range of your Netgear, you should get connected, though it does take a bit longer than normal (the Router still wants to assign an address first before accepting the static IP). You can speed this up by changing the Device table on the router to always keep the Phone's static IP open.
This shouldn't work as all my other attempts with Static IP failed, but I've had five days now of instant connection to WiFi at home, so something has been freed up.
i can not tell you how seeing this post was like finding bin ladin in the white house. Prob would have found him twice trying to solve this WIFI problem. And the strange thing is this is the 1st phone i have had that there are so few posts about it...is everyone on that icrack? scary. cheers to you...
Thank you for posting this.
I tried this with my and it seems it doesn't make a difference for me. I still can only connect once to the router and for me to connect again i have to restart the router again. Am i missing something?
Problem is when I connect for the first time at home it works then when i leave to the office i use the wifi there and never have any problems there but when i get back home it doesn't work. Do you guys switch the wifi off manually when you are not using it?
one thing that is almost always overlooked is updating the router's firmware. this usually solves a number of issues. I dont know about netgear but it's worth a try to update
bimmerboii said:
one thing that is almost always overlooked is updating the router's firmware. this usually solves a number of issues. I dont know about netgear but it's worth a try to update
Click to expand...
Click to collapse
That was one of the first thing i tried....it seems i have the latest firmware.
Is this an issue for a lot of people then? Ive one of these routers and never had an issue connecting any phones to it. Had 3 nokias and 3 different android phones, currently on the x10, and they all connected fine everytime.
i have some troubles in x10i wifi connection and holp someone helps me~
------------------------------
im chinese, my x10i have had the lastest firmware but the phone cant connect the AP which set the channel is "13". but i used it long before and suddy just one day i find it dosnt work~ it cant scan(and find) the AP anymore !
then i have tried and config the router in another wifi channel(just like 1,8,11..) and the phone can scan and refind the AP.
i have tried to reload the phone's default setting,but it dont work(in channel 13)ToT
---------------------------
someone tell me why? and someone give me some suggest?
in china , lots of router's wifi channel are using "13" by default(factory setting);so, if my x10i cant works in that channel means i couldnt find the "opend APs" which in the public place(like KFC~~)
THX to help~
StampedChipmunk said:
Hello all,
I love my X10, but the frustration with getting it to connect to my Netgear DG834 router was getting to me, so I dedicated an afternoon to working out a solution and I've found one that works for me, so I hope it'll work for you too.
<snip>.
Click to expand...
Click to collapse
Thank you! I have spent three days trying to get my phone to re-connect to a DG834v5.
Your solution has worked! I had gone as far as reserving an IP address on the router and linked it to the MAC of the phone... no dice. The phone would connect once and then never again until the router was reset. Really irritating because I have two PPPoe connections running through the router with a routing table that has to be re-loaded via telnet every time the router is reset. I was considering a new phone or a new router.
HI,
I have near the same problem.
But I found out that when I remove on the access point the hidden function ( SID ) then it works perfect.
so that is a bug in the ROM of the X10, I have the R2b026.
At the moment everone can see my Access Point but I can live with that solution.
Worked for me! Many many thanks this had been infuriating me...
Same problem here - never had an issue with any other router, so I blame Netgear...
Let's just hope this works - it's been driving me crazy for the past 5 days...
Neh, hasn't worked for me....
Stupid freakin' Netgear...
works on the HD2 aswell. Thanks alot!
Not just Netgear, maybe Android
k1sr said:
Same problem here - never had an issue with any other router, so I blame Netgear...
Let's just hope this works - it's been driving me crazy for the past 5 days...
Click to expand...
Click to collapse
I am having the same issue on my HD2 Android 2.3.4, connecting to a D-Link DIR-635. If I use Static IP, everything is fine...
WORKS! I can't believe it, finally i can disconnect and connect without having to reset my router everytime. BIG thanks man!
alright, it worked fine for the first 5-6 hours. then it went back to not connecting without rebooting the router. this problem happens only with my home router, at work i can connect fine, as well as in other places.
any thoughts or solutions? i mean it did work in the beginning, then why did it stop? shall i change my router?
P.S.: i noticed that every time i connect to my home router i get the same IP address and all the stats are the same.
I'm puzzled by the behavior of my phone. For probably a week at a time, I go to work, connect to a WIFI there, then come home, connect to a WIFI there. No problems at all.
Then it seems like after a week or so of 'being good' sometimes I'll wake up the phone and it will see the network, but will not connect to it, asks for passphrase repeatedly (WPA2-AES Cisco E3000 router) but just will not connect. I have found no way to trigger the phone to reconnect (and I refuse to do another hard reset because that is no solution at all).
The simple fix is to reboot the router. Presto, the phone will connect almost immediately.
I am willing to accept that maybe something is wrong with my router, although I have 3 laptops and a couple of IP cameras, and an Xbox that connect wirelessly all the time, and I never ever see this refusal to connect on any of those devices, and my wife's Blackberry will also connect whenever. So I'm thinking its my phone.
So for the experts out there, what is it about rebooting the router that fixes the problem?
I only recently learned how to get into the manufacturer's special app, so I'm going to pay attention to my IP address next time I have an issue, and see if it actually changes when I reboot after this problem occurs again.
Where does one discover how and what can be tweaked in the secret app? I'm cautious but not afraid....hey, I've edited the windows registry countless times on my PC and never toasted the OS yet! Does that count for something?
Add: I had this happen once at my work WIFI, using an ancient DLink router using WEP. At the time, I was trying out a bluetooth headset (Plantronics Backbeat), which worked, albeit, after I was done listening to the podcast, be darned if I didn't get into this refusal to connect thing, and unbeknownst to me, I was using the 3G data connection for what I thought was a wifi broadcast. That sucked 175 megs that day! I was a bit pissed about that. I have not used the Bluetooth since then.
Rebooting my router at work fixed the problem but I hate doing that, because I've got other equipment on that network that likes to be permanently connected.
the same happened to a frined of mine: interoperability issues with that model of router and the phone, changed the router and after everything worked perfectly, that sucks, but it is
Had a similar problem, and simply could not pinpoint the cause. Solution? I resetted my router to factory settings, and started to change all the settings from scratch to my desired settings. One thing that helped solve my problem was that I changed the default IP address used by the router (in my case, 192.168.0.1) as well as the IP range to something more ... random. Also, I limited the number of allowed IPs to 10 rather than the default 100...That helped. Never got a disconnect or problem connecting again. I had the same thing happen on my mother's iPhone and my brother's Galaxy S, and this solved it.
hi everyone, some days ago I installed the virtuous 1.6, than replaced with a rooted stock 3.1. Since then, when I disconnect from my wifi for a while, getting far away from my router, it happens that coming back into the wifi field the tablet tries to reconnect but after 4 or 5 times it stops trying and tells me the connection is disabled. I see the dhcp service bouncing, no ip assigned. The only solution I've found googlin' around is to rename/delete the file dhcpcd-wlan0.lease in /data/misc/dhcp. It worked. but the issue got back again and again. I wanted to find out the cause and solve the problem once and forever, if possible. It's a pain in the... you know
Here is my topic. There is also one solution to it apart from the one you've found in google (which was probably my topic anyway ).
You're right, it'was your post. I've read it againg but I can't find out which could be the alternatrive solution. Keep in mind that when I got this wrong behaviour the first time obviously I invesitgated the possible causes, and I discovered the inability to retrieve a dhcp IP address either with my wifi router, with my wifi access point 3g and with a tethered connection via Iphone (all of them I normally use when I'm not at office). None of these would work until the uplisted file deletion). Would you be so kind as to suggest me, if you can, the possible solution in more detail (apart from performing a global reset that would be as annoying than deleting the file)
In any case, many tnx for your answer
Currently the common solution is to abandon the leaked 3.1 rom or put up with the bug.
Manually setting DHCP also works but it's usefull only if you'll use the tablet on one wifi. Else it's just a big pain in the arse.
I have same issue with the stock 3.1 rom.
At the end what I did was manually assign IP address for my iPhone's MyWi connection.
It seems mine has no trouble to connect to my home wi-fi network as well as work...
I also get that problem. But now, seems to have fixed it. I have done the followings:
- delete the dhcp lease file
- change the channel of my wifi router to 9 or below
- download the ad-hoc supported wpa_supplicant
Please try if above help you
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.
OK so device is a - LG D80210B - 16GB - UK - EE - UNLOCKED - ROOTED - StockMOD rom with update package. 4.5gb storage space left.
2nd device is a - HTC ONE 16gb - STOCK - NO ROOT
3rd device is a - SAMSUNG RV510 Laptop.
Im on EE uk network on both phones with EE ADSL Broadband at both mine and my partners house.
Now.... One would assume everything from the same company would be simple... If only that was the case! haha.:silly:
Now which ever property I visit within 15 - 20 minutes of being on the Wi-Fi the LG G2 kicks everybody out of the router, all at the same time. No one can access the network until one of 2 things happens... either I disconnect for 15mins plus or the router gets restarted nothing else will bring back the internet. Note - This does NOT happen when I am not present and surfing can be achieved all day on any device.
So ive spoken to the useless turds at EE technical support on the phone about 30 x they have absolutely no idea what the issue is but its definitely only related to my device. There suggestion is to cancel and go back to sky (which worked flawlessly previously to EE being installed). this is an option but it means another month with no internet at all and I also get an additional 10GB of 4GEE data on my phone allowance if I have there broadband so it would be beneficial to keep it.
Things ive tried;
Every different setting under the sun.
Different encryption.
Static IP addresses.
DCHP settings.
the brightbox will only broadcast internet on 2.4ghz as well if it helps anyone diagnose.
Using a known router as an access point to see if that solves the issue - again perfect until I log on.
Tech support.
Search the net and forums on here.
Spoken to a networking wizard mate of mine.
The problem seems to lie in the LG G2 and/or Jellybean firmware currently installed and installed as stock as the fault is not present when I log off the Wi-Fi...
So..... I decided to try a different rom, the Slim Kat rom
The Wi-Fi works flawlessly for me and everyone else however the rom is just too unstable at the moment to be a daily driver. It doesn't have the complete knock on knock off features and I don't really like the look I much prefer the stock rom as well as some of the games I play just will not work.
Now ive had and been flashing smartphones for about 8 yrs with the help of you lot on here leedroid especially was one of my faves so im not a novice or anything im just lost for what else to do or try????
Has anyone else experienced anything similar?! I would send it away to see if its a hardware fault but as it works perfectly on kitkat I assume its got to be some kind of bug in jellybean.
OR ive changed something that's ****** it up.
I would really appreciate any imput at all because I have a phone I cant use at my partners house or at home ...
Cheers brett
Just to add it also does it when Im on my own i.e. just the phone.
bump for today.... this is really breaking me now as no one can use the wifi for longer then 15 minutes lol
So theres not one single person that has even the faintest idea of what my issue may be?
Someone had this issue before, read about it. A router update fixed their issue. If setting device static, the router also needs to be configured to hold it, try this with all devices and lock local IP's. Next, leave a device off and see if it gets kicked. The G2 seems a bit picky with routers... On the Comcast Technicolor, it won't push past 3.5 dl, but max up. Some old drt firmware has problems as well.
Steamer86 said:
Someone had this issue before, read about it. A router update fixed their issue. If setting device static, the router also needs to be configured to hold it, try this with all devices and lock local IP's. Next, leave a device off and see if it gets kicked. The G2 seems a bit picky with routers... On the Comcast Technicolor, it won't push past 3.5 dl, but max up. Some old drt firmware has problems as well.
Click to expand...
Click to collapse
Thanks for the reply dude...
Yeah tried to update it but its telling me its on the most recent software even though its date is 2010. Called tech support they say it up to date.
I can set the IP in the DHCP section of the router but I cannot for one second find out how to do it on the phone... do you know?
I used DHCP to assign a static IP to both phones, the Nintendo wii, the sky box and the laptop, so they always pick up that IP from the router without fail. I also set the DHCP settings so that it does not conflict with any of the locked IP's just incase - so DHCP is from 192.168.1.2 - 192.168.1.99
Its not a router problem as much as id like to blame it on that because I used my old known working sky router as an access point to connect to as well and that make absolutely no difference apart from slow it down because it doesn't support "N" mode.
Its an EE brightbox router - piece of *****
I can leave the other 4 devices connected to the router 24/7 with no issue until I connect the LG G2. Then all devices are booted at the same time usually 15-20 mins sometimes less. never more. it also only occurs when just the LG is connected. Like now my phone is stuck at recovery ATM (another problem im trying to solve) and the internet hasn't dropped once my partner is on it and so is the sky box so its DEFO my phone that's doing the bad.
That's ODD that isn't it my up and downstream in the router are both above 10meg although the attenuation and line noise keep changing.
cheers for the input
In wifi menu of phone, hold on connection and select modify. Check show advanced options, chose static, input data(along with password again). Reboot phone. After you fix it of course.
Steamer86 said:
In wifi menu of phone, hold on connection and select modify. Check show advanced options, chose static, input data(along with password again). Reboot phone. After you fix it of course.
Click to expand...
Click to collapse
I ended up getting a new router that seems to be ok so far... what does that actually do? Thank you so much for it suggestions
Sent from my LG-D802 using xda app-developers app
Sets static for phone. Has to be set on both router and phone. I just found out the G2 has some issue with AES on certain routers. Try TKP only. I had to do this with my other Technicolor. Odd thing is AES works fine on the SB 6141. Lost on that one.
Had exactly the same issue with my shiny new G2. Using a Netgear modem/Router. I upgraded the firmware and that seems to have fixed it. It was killing the Router within about a minute of use. Now running 25 minutes without any drops. Fingers crossed it's permanent.
Sent from my LG-D802 using Tapatalk