Related
My captivate has a problem. It'll connect to WiFi no problem. Unfortunatly, after a while (could be anywhere from long 30 seconds to a few minutes) the WiFi stops sending data. I have to disable/reenable wifi to get it to work again. It still says connected to network, it just won't receive data.
Anyone know of this happening, have a fix, or maybe what I should look for that might be causing this issue?
I disabled recently installed running apps, no help.
I did try a speedfix last night, and it was unsuccessful, and I uninstalled it. Didn't test enough after that to know for sure if it was the issue, but I don't think so.
It was like, I was going through google reader, started a youtube vid, paused it, restarted it, and it wasn't loading. Just wouldn't load. That's when I think the problem started, and I haven't installed anything since then, that i haven't disabled/uninstalled.
Have you tried flashing the stock OS. Maybe this will help. My wifi has been solid so far but i will see if i get a problem like yours. Try reflashing. If it doesn't work post back.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have the exact same issue on enterprise class cisco wifi APs. The only difference is the symptom is immediate, and not after an interval of time.
Sent from my SAMSUNG-SGH-I897 using XDA App
abezapata said:
Have you tried flashing the stock OS. Maybe this will help. My wifi has been solid so far but i will see if i get a problem like yours. Try reflashing. If it doesn't work post back.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm thinking of this, but I don't know...
I have my music on my computer, I have my .apk's in a folder and my market synced with appbrain. Anything else I need to do? Will appbrain reset, and make me go find and reinstall everything?
What about the apps that I paid for, what happens to them?
Would be my first flash, and I'm thinking about flashing one of those I9000 roms, but that would be a last ditch effort. I really hope to avoid this.
jhannaman82 said:
I have the exact same issue on enterprise class cisco wifi APs. The only difference is the symptom is immediate, and not after an interval of time.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It's an AT&T U-verse router, and only started a few hours ago, as near as I can tell.
I experience the same phenomenon of dropped wifi, and it occurs at any AP, but I have an interesting twist.
One time out of twenty when I start wifi, the 3g icon doesn't go away, but stays up on the status line with my wifi icon. On those rare occasions, my wifi stays solid for days. Unfortunately, it's random and rare.
same issue
My Wifi stops sending data and the 3G still shows. Sometimes restarting the router helps and sometimes nothing helps.
For anyone that might find this later, turns out (after two rom flashes) it was the router. I found this out when connecting my laptop to it. Surprised the captivate didn't admit it lost connection though.
I wish that were the case for me. My Captivate stays connected, but stops receiving at many different APs--Home, Starbucks, airport. I need a solution or a Scotch.
Peter
I had this exact problem, I tried a factory reset and it was still broken. I exchanged my phone and now it works perfectly holding a signal (except for enterprise 802.1x ap's which are known to be broken). (Also if you run dd-wrt check your logs for "deauthenticated due to local deauth", there is a problem with the wpa/wpa2 modules in either android or dd-wrt that they are not compatible with each other).
I actually found this searching for a solution to my own issue with WiFi. I actually fixed it while I was reading this. Unfortunately I have AT&T DSL with 2wire Modem. I went into the setting and setup MAC filtering and assigned it it's own IP. It has worked flawlessly for the past hour. I know this probably will not help when at other locations but at least at home I have a good connection.
VooDooVonz said:
I actually found this searching for a solution to my own issue with WiFi. I actually fixed it while I was reading this. Unfortunately I have AT&T DSL with 2wire Modem. I went into the setting and setup MAC filtering and assigned it it's own IP. It has worked flawlessly for the past hour. I know this probably will not help when at other locations but at least at home I have a good connection.
Click to expand...
Click to collapse
Same router type as mine that lost it originally. Interesting, wonder if there is a connection? Or random coincidence.
I'm having a wifi issue as well, but not to the extent others have.
I connect fine, but it appears as though my data download speed is capped at <2mbps for both wifi and 3g?
My wife's iPhone is getting download speeds of over 10mbps on the same wifi network and >3mbps over 3g.
Is it worth flashing back to stock? or is this a known issue?
I'm running stock JH3 with SRE 1.2.1a with lagfix
I have this same issue and it's really random. Running JH2, sometimes it works on wifi, sometimes it doesn't. Sometimes disabling\re-enabling wifi fixes it, but rebooting the phone always fixes it. Really frustrating...
All WiFi issues consolidated into 1 topic
[Q] Wifi signal?
Does anyone get a weak wifi signal with their Nexus S? Whenever I connect to my at home wifi I never get full bars and something I'll just randomly lose signal. Also it seems to go pretty slow. I used to have the Mytouch4G and it work flawlessly with the wifi. Anyone else having this problem?
damrong18 said:
Does anyone get a weak wifi signal with their Nexus S? Whenever I connect to my at home wifi I never get full bars and something I'll just randomly lose signal. Also it seems to go pretty slow. I used to have the Mytouch4G and it work flawlessly with the wifi. Anyone else having this problem?
Click to expand...
Click to collapse
OMG yesss I do.
Just about a room away I loose signal, almost completely. = 0
IDK, but I see more flaws every day that passes
Mine's been working fine over Wi-Fi. I'm pretty glad it does too, because my only data option with it is Wi-Fi..
Sent from my Droid using XDA App
Wifi has been working great for me. It reconnects automatically and doesn't drop. The signal seems on par with my nexus one.
Speed wise, is it on par with the 3G network?
[Q] Wifi does not work anymore after rooting :(
So, I unlocked my Android 2.3.1 and rooted it ... But if I click on wifi so I could connect to my modem it says Error and wont even search or anything. I tried reseting too but still no luck .. What is the problem and how to fix this ??
That's odd, I didn't have any issues with wifi as I connected to Android Market to downloaded ROM Manager during my rooting process earlier. Have you tried flashing a custom ROM on your device to see if it'll fix it?
No I didnt, would that work? .. A friend told me to install a new "kernel" but I dont want to overwhelm my android with custom made kernels .
your problem is you used one of the quick methods of rooting your phone, which used a kernel that wasn't from the exact rom you have.
if your on stock 2.3.1, you will need the stock 2.3.1 boot.img, and then you'll need to root it manually the long way via adb command line. search the nexus s development section for how-to's. they are all there.
i too had this problem, had to install MoDaCo ROM to fix it, but i dont regret rooting, i now have custom rom and over clocked cpu on the nexus s
you have two options, either to flash NANDROID backup to un-root and return to stock or install a custom ROM, i choose MoDaCo bcoz of its UI, it looks and feels just like the stock one.
golu12 said:
you have two options, either to flash NANDROID backup to un-root and return to stock or install a custom ROM, i choose MoDaCo bcoz of its UI, it looks and feels just like the stock one.
Click to expand...
Click to collapse
Yes, that's the point of MoDaCo roms, to make minimal changes to the look and feel of the phone, but to improve performance with his custom optimizations.
[Q] Nexus S wifi issue. Unable to access wifi from my nexus s.
Hi Guys,
I was able to connect to my wifi network for a day. I am using windows 7 machine as hotspot with connectify. From second day I am unable to connect to any wifi network. I did factory reset my nexus s but no results . Can some one help me how to solve this issue?
Observations:
*when i use static ip, It shows connected but the bars are in white instead of green color and i am unable to browse.
*When i use dynamic ip I am unable to connect to wifi. It shows obtaining Ip and never connects.
*In connectify when I was able to connect to wifi the device is shown with an android device name. but now the device is shown as unknown.
Sorry for my bad english, I m not a native english speaker.
[Q] Nexus S Wifi Settings - force close
Hi all,
Just got a new Nexus S - all was well at home. Took it to work today and noticed something very odd. It was fine until entering the wifi settings menu - at which point it dramatically slowed down. I got two 'not responding,close or wait' messages before being able to join the network.... all other settings are fine - just the wifi area.
Weird - wondering what could cause this... too many wifi networks broadcasting (am in middle of London)...?
Anyone seen anything similar?
Rich
rakh1 said:
Hi all,
Just got a new Nexus S - all was well at home. Took it to work today and noticed something very odd. It was fine until entering the wifi settings menu - at which point it dramatically slowed down. I got two 'not responding,close or wait' messages before being able to join the network.... all other settings are fine - just the wifi area.
Weird - wondering what could cause this... too many wifi networks broadcasting (am in middle of London)...?
Anyone seen anything similar?
Rich
Click to expand...
Click to collapse
Too many WiFi around you shouldn't cause that.
Try rebooting and setting again if you haven't already.
Hmmm - rebooted and still have the same issue. At home, or even a block away from the office it all works fine. But in the office itself, although it connects and uses the wifi fine, the settings page is VERY slow to load and gives me the wait/force close message.
Out of interest - I also have 'wifi analyser' from the marketplace. This too is very slow and unresponsive when in the office.
So - it is definately something to do with the wifi here.... but have not got a clue what. Before I join the wifi, or when I am physically somewhere else it all works fine.
Wifi is WPA-TKIP, the key is a very long jumble of letters but surely that is not an issue.
Strange eh!!!
Rich
[Q] Possible WiFi problem?
Hi there, just bought a Nexus S, also used to have Nexus One.
The thing is for some wireless networks even though I enter the password correctly, it says connected and still there is no connection at all. (I mean browser tries to connect but at the end it says page could not be found) I even tried with an ad-hoc network that I created with my laptop but still the problem exists.
At home I'm able to my network without a problem. The type of network I'm trying to connect is: WPA2 Personal with AES. Is there any known issue about AES at Android system? Afaik there is no way to change the encryption used right?
this might actually not be a nexus S issue.
some modems/switches/routers are configured to block certain devices/applications/package's
we have a modem and router with both wifi.
but my psp/nDS cant connect to the modem,but can connect with the router
kharikishan said:
Hi Guys,
I was able to connect to my wifi network for a day. I am using windows 7 machine as hotspot with connectify. From second day I am unable to connect to any wifi network. I did factory reset my nexus s but no results . Can some one help me how to solve this issue?
Observations:
*when i use static ip, It shows connected but the bars are in white instead of green color and i am unable to browse.
*When i use dynamic ip I am unable to connect to wifi. It shows obtaining Ip and never connects.
*In connectify when I was able to connect to wifi the device is shown with an android device name. but now the device is shown as unknown.
Sorry for my bad english, I m not a native english speaker.
Click to expand...
Click to collapse
i have a similar problem. My Nexus S connects to my router only within a few hours after a router reset. Then it stucks at "obtaining ip" and never connected before I do another router reset.
My home wifi is WPA2 type, and for WEP type wifi my NS never got connected.
Ever since I got my Captivate, it has had issues with wifi. It's not my routers, or any configuration in my routers, as it happens with 3 different routers (not to mention that I work in IT, so it's definitely not the routers).
Here's what it does. When you start with a fresh boot, it works perfectly fine. As the day goes on, it gets worse; it starts dropping the connection randomly, and eventually stops working altogether. This wouldn't be so bad of a problem, but the point that it "tries" to start accessing a wifi AP, it drags the phone down in speed, eventually freezing, causing me to ave to reboot the device.
I already tried all options with wifi sleep policy; I've tried 3 different ROMs; I've tried clearing all wifi settings and letting the ROM generate a new .conf file, I've tried different wifi firmwares. Nothing works as it should.
What should I do now? Does anyone have any tips for me? I know it's the OS and not the phone, because the last ROM that worked perfectly was Perception 4.
Thanks for the help.
Easy fix I found.
Open Allshare, it should have come pre-installed.
Connect.
Your Wi-Fi problem should be fixed.
You will have to repeat this step when switching between locations, or when you come back to the troublesome router. I don't know why this works, but it does. It seems to have helped alot of other users in other forums with this problem. Maybe someone should make a sticky of this...seems to be a big problem with 2.2 Foryo.
Similar experiece with both an EVO and Captivate with a Linksys router and DLink wireless AP. Whenever I walked into the house, the other PCs attached to the router would stop working, the phone would not get data although it showed as connected and I had to reboot the router - both wired and wireless clients. The Linksys was a very old firmware and I had bad experieces with flashing a few previous devices. I ditched my Linksys for a DLink 8 port and wireless and have not had the issue with either the EVO, Captivate nor any devices attached to my network.
yamabigdog said:
Easy fix I found.
Open Allshare, it should have come pre-installed.
Connect.
Your Wi-Fi problem should be fixed.
You will have to repeat this step when switching between locations, or when you come back to the troublesome router. I don't know why this works, but it does. It seems to have helped alot of other users in other forums with this problem. Maybe someone should make a sticky of this...seems to be a big problem with 2.2 Foryo.
Click to expand...
Click to collapse
This is news to me. You are correct, I do have Allshare. I'll try it the next time I have the issue.
What if I simply remove Allshare? Will that fix the problem?
bdfx69 said:
Similar experiece with both an EVO and Captivate with a Linksys router and DLink wireless AP. Whenever I walked into the house, the other PCs attached to the router would stop working, the phone would not get data although it showed as connected and I had to reboot the router - both wired and wireless clients. The Linksys was a very old firmware and I had bad experieces with flashing a few previous devices. I ditched my Linksys for a DLink 8 port and wireless and have not had the issue with either the EVO, Captivate nor any devices attached to my network.
Click to expand...
Click to collapse
I have 2 Linksys routers with the latest firmwares, and one D-Link. No matter, it does the same thing with them all.
I should also mentioned that I already tested with changing the router's wireless broadcast channels, signal strengths, firmware updates, the whole 9 yards. The problem is the phone, not the networking equipment.
I used this on 3 Captivates in our house and they are all working great now. Had F&*%%#ed wifi issues before that. They are all ok now. Hope it lasts!
https://market.android.com/details?id=com.brilliapps.wifiandmorefixer&feature=search_result
ajm786 said:
This is news to me. You are correct, I do have Allshare. I'll try it the next time I have the issue.
What if I simply remove Allshare? Will that fix the problem?
Click to expand...
Click to collapse
I'm not sure if that will work. I don't think this is by any means a permanent fix, but a temporary work-around. I think it just kicks the wi-fi into gear again somehow...=-(
Hope it helps someone out though.
I had a friend who was having issues with her phone not even attempting to scan for wireless, seems there is an issue on android phones that the networking cache file or whatever it is gets cluttered and needs to be renamed. (Android recreates it)
The process is rather simple, I walked my friend through the steps over the phone w/o issues.
I had her use oneclick root/unroot to root her phone.
http://forum.xda-developers.com/showthread.php?t=739304
Then Had her go through these steps to rename the file.
http://androidforums.com/samsung-moment/46179-unable-scan-networks.html
The steps are for a samsung moment but still work. Also noted that the steps w/o rooting do not work. After you finish renaming the file you can use the application in the first link to unroot the phone and go back to stock
SlappyMcgee seems to have the best fix
It wont hurt anything and I suggest just renaming the file to .old instead of deleting it. the entire process takes like 8 mins
SlappyMcGee said:
Then Had her go through these steps to rename the file.
http://androidforums.com/samsung-mom...-networks.html
Click to expand...
Click to collapse
Link doesn't work, at least for me.
Update:
The Allshare thing works. The problem is that it's not a feasible workaround, because you have to keep doing that every time you want to restart the wifi after the screen goes to sleep or what not.
I will next try that config file delete. I read up on that last night, but didn't think that was it, because I already did a few ROM installs which didn't seem to clear it up.
Nelimungous said:
I used this on 3 Captivates in our house and they are all working great now. Had F&*%%#ed wifi issues before that. They are all ok now. Hope it lasts!
https://market.android.com/details?id=com.brilliapps.wifiandmorefixer&feature=search_result
Click to expand...
Click to collapse
Little early for me to say this is working for sure. But ill be damned if it didn't, at the very least, temporarily fix it. Instant reconnect. Doesn't hang. Seems like it might be the real deal, for me at least. Ill come complain if it craps out again.
Edit: .... worked for 15 minutes. Aka doesn't work...
What's your kernel?
xdahgary said:
What's your kernel?
Click to expand...
Click to collapse
I tried all different ones. Firebird and Speedmod mainly. When I flash newer versions, I always wait till the battery is 100%, and I clear the Dalvik cache. Nothing ever works.
phlunkie said:
Link doesn't work, at least for me.
Click to expand...
Click to collapse
Sorry about that. I fixed the link in the original post.
http://androidforums.com/samsung-moment/46179-unable-scan-networks.html
i had wifi issues and still do. my girlfried does too with her Aria. The phone really seems to only work on routers who have a DNS set to google. The bar near my house it flys and at home i was getting no wifi so I changed my router DNS to google from comcast and its fine. I agree there is a problem but not one that is going to get fixed by Google
My wifi workaround
I had two captivates which both had problems with my home router. Reseting the router never fixed the issue, but resetting the phone did, at least for a few minutes.
I found that phone has problems using DHCP with routers that assign addresses in the 192.168.1.xxx range. It seems to be a conflict with some other internal IP in the Captivate or something. To get around this problem, I had to change the local address of my router to 192.168.2.1, and change the DHCP range to 192.168.2.xxx The new subnet cleared up the problem immediately for me and it hasn't returned, at least, not on my home router. Unfortunately, this won't work on hotspots or other networks that are stuck in the 192.168.1.xxx range.
timsline said:
I had two captivates which both had problems with my home router. Reseting the router never fixed the issue, but resetting the phone did, at least for a few minutes.
I found that phone has problems using DHCP with routers that assign addresses in the 192.168.1.xxx range. It seems to be a conflict with some other internal IP in the Captivate or something. To get around this problem, I had to change the local address of my router to 192.168.2.1, and change the DHCP range to 192.168.2.xxx The new subnet cleared up the problem immediately for me and it hasn't returned, at least, not on my home router. Unfortunately, this won't work on hotspots or other networks that are stuck in the 192.168.1.xxx range.
Click to expand...
Click to collapse
I ran into this problem on my Router. Netgear wndr3700. For some reason when I turned the wifi on my phone either the router was assigning it the same address as my Tivo or my phone wasnt accepting anything but that address. To resolve I forgot the connection my phone then reflashed the firmware on my router. Then reconfigured the wifi on my phone. After that no more issues.
Well i honestly dont know whats wrong with mine. I've done all the "fixes" in this and other threads but it doesnt work. What is weird is that it connects using All Share and only All Share. However it does connect at other places like my friend's, sister's, granparents and gf's houses. I think I'm gonna go to att and demand a new phone and an upgrade
Just wanted to post an update on this. For the most part, deleting the wifi configuration file in data\wifi seems to have cured the problem. The wifi signal did get stuck on one or two occasions, but I'm bound to believe that the issue was caused elsewhere.
Hi,
I'm on 11-20140804-SNAPSHOT-M9-ville, official (HBoot 2.15), Radio 1.35a.32.45.27
I have a strange problem with my WiFi. I can't really tell what details are important, so I'm gonna give you guys the full story.
After rebooting, everything works fine and the phone instantly connects to my WPA2 PSK secured WiFi at home. When I'm at university during the day, I'm connected to another WPA2 WiFi (maybe some of you have heard about "eduroam", TTLS/PAP authentification), which also works fine. However, when I get home in the evening, my phone won't connect to my personal WiFi at home any more. I see the SSID, but when I try to connect, it says "Connecting..." for a milisecond, then just jumps back to showing me it's a WPA2 secured WiFi without having done anything. I get no error message or anything, it just doesn't connect and doesn't even seem to really try to connect.
When I reboot the phone it instantly works again without a problem.
Any ideas? Are there error logs for failed WiFi connection attempts anywhere for further analysing the problem? Any hint is appreciated!
- Folrot
Folrot said:
Hi,
I'm on 11-20140804-SNAPSHOT-M9-ville, official (HBoot 2.15), Radio 1.35a.32.45.27
I have a strange problem with my WiFi. I can't really tell what details are important, so I'm gonna give you guys the full story.
After rebooting, everything works fine and the phone instantly connects to my WPA2 PSK secured WiFi at home. When I'm at university during the day, I'm connected to another WPA2 WiFi (maybe some of you have heard about "eduroam", TTLS/PAP authentification), which also works fine. However, when I get home in the evening, my phone won't connect to my personal WiFi at home any more. I see the SSID, but when I try to connect, it says "Connecting..." for a milisecond, then just jumps back to showing me it's a WPA2 secured WiFi without having done anything. I get no error message or anything, it just doesn't connect and doesn't even seem to really try to connect.
When I reboot the phone it instantly works again without a problem.
Any ideas? Are there error logs for failed WiFi connection attempts anywhere for further analysing the problem? Any hint is appreciated!
- Folrot
Click to expand...
Click to collapse
Hi,
I had exactly the same problems with m8. I have a Virgin Superhub 2 at home which broadcasts on 2.4 and 5 Ghz. After disabling one of these frequencies, the behaviour briefly changed. Then went back to not working. With eduroam all worked nicely.
I read somewhere that I should activate the "Scan always available" setting. Sadly, I didn't get a chance to try that because I was so fed up with
- the significantly lower sound on CM (is that something you experience with radio 1.35a?)
- mobile signal drops
that I wen back to Maximus 10 where I have no problems at all.
I had radio 1.15 and 2.15 HBOOT when I had those problems. Now I'm on also 1.35 with Maximus 10 and problem free but would like to return to CM if the low sound problem and the WiFi problem could be sorted out.
Here's an interesting little detail I noticed: When I stand right next to my router (full WiFi signal strength) and click on my WiFi and choose connect, the signal strength drops down to one bar immediately. Also, the eduroam network changes from "not in range" to "disabled".
Playing around with the WiFi options didn't help.
edit:
What exactly do you mean by lower sound? That the phone's maximum sound volume is lower than normal? That's something I experienced on my old htc desire, but not with my htc one s. Also mobile signal seems to be stable, no signal drops. The only thing I found curious is that with activated mobile internet, it often changes between 3G, H and H+, but judging from google search results that seems to be normal or not connected to the custom rom.
went through the CM bugtracker, apparently it's a known issue without a solution
https://jira.cyanogenmod.org/browse/CYAN-3923 if you want to know more
One last question, maybe someone here can answer it: As far as I understand the issue, it's a problem with an old WiFi driver and the corresponding kernel modules.
Wouldn't this issue then be present in all ROMs which don't use the stock kernel? Or did I misunderstand something?
Folrot said:
One last question, maybe someone here can answer it: As far as I understand the issue, it's a problem with an old WiFi driver and the corresponding kernel modules.
Wouldn't this issue then be present in all ROMs which don't use the stock kernel? Or did I misunderstand something?
Click to expand...
Click to collapse
Same problem here with Miuri. Tries to connect and then gives up.
The problem has been resolved by the CM11 devs. I'm running nightly 20140819 and it's working fine now for me. :good:
Hey guys,
I'm having some issues with my Wi-Fi connectivity on my N5 and it's freaking me out! :crying:
When I'm trying to connect to my home network, the Wi-Fi icon is getting orange after some random time.
Some times it gets back to white, some times it's not.
I know its a known issue but nothing seems to fix it.
I tried everything - reboot my phone, reboot my router, reboot into safe mode, forget the network and connect again, toggle into airplane mode and back, change Wi-Fi settings to connect only to 2.4 GHz, avoid poor connections, update my router firmware.
NOTHING worked!
The only thing I haven't tried yet is factory reset but I read some people saying it didn't help them either.
Only turning Wi-Fi off and than on again makes it "white" again for some other random time.
I'm running stock everything on a rooted device with Android 4.4.4 build KTU84P.
My Wi-Fi is working great with other devices in the network including a Nexus 7 2012 and some laptops.
And it seems that my Nexus 5 is connecting fine to other Wi-Fi networks.
It worked fine in the past and I think it all went wrong when I replaced my Modem.
Any ideas what else can I try?
Do you think maybe the Lollipop update will fix this annoying issue?
Thanks!
Forgot to mention (I guess it is obvious) - I can't connect to any website or run any network connected app when I'm "orange" (I know it means I'm not connected to google services).
Tried also to change my Wi-Fi channel. still not working.
Doesn't anyone have an idea what is wrong here?
This is really frustrating ... :crying:
Well, I'm kind of talking to myself here, but in case someone else is facing this annoying issue, here is what fixed it for me eventually:
Configure a static IP to my phone in the router configurations ! :victory:
Before that, I also tried to disable Wi-Fi optimization in the phone Wi-Fi settings, buy it didn't seem to help.