Database Users

[UPDATE]Official Nexus one Wifi issue thread(every N1 owner should read)

Sorry I know this problem probably has been brought up many times. But here I just want to make a total one and collect all the feedbacks from N1 users regarding to the wifi sleep issue with N1.
Let's just make it simple: Every N1 owner PLEASE DO test out the wifi connection when your phone goes to sleep as there are MANY people suffering from this problem all over the world. Especially the later buyers since February this year, almost every phone is potential to this problem.
######################################################
Diagnosis:
1. Set the wifi sleep setting to "never" in the wifi advanced setting menu.
2. Turn on Last.fm app(or Pandora, but Last.fm is most effective and responsive one to test it out), leave the phone on wifi and turn off the phone screen or let it goes to sleep.
3. The symptom is the app will stop streaming shortly afterwards(with Pandora stops maybe after one song, for which I suggest everyone test it for at least 15 minutes). Also most likely you will stop getting any email notification or anything requires data connection. And you might not be able to ping your phone or the ping responses VERY slow as well.
######################################################
######################################################
Background:
This problem was recorded from earliest almost 6,7 months ago and has affected both AT&T and T-Mobile versions(with reports of the same issue on other versions sold outside US). So far, it's suspected that the problem mostly likely lies in the lower level architecture of the phone(either software or hardware) because the problem still exists even after people has replaced the stock ROM with the custom ROM. Another proof is that people get problem with brand new phone and also the replacement phone. Another note is the problem has been found both before FROYO update and after. At this moment, there's no official fix(some Google employee blatantly brushed the issue away and asked N1 users to get over it, check out the link below for original conversation) for this issue except a work around thanks to wifi fixer app developer.
######################################################
This issue is often times neglected by N1 users because usually people don't use the phone on wifi all the time or they simply switch between 3g and wifi. But for people who use wifi a lot or use VOIP, it could be a real deal breaker.
So here I just hope everybody could test your phone out and see if you have this issue or not. Please report how your result turns out in this thread. Also, for further and more detailed discussion and cases, please check this out:
http://www.google.com/support/forum...52&hl=en&fid=01a47ff5b0a92d5200048be07b6cb5c1
You are more than welcome to add your experience to the discussion above so hopefully it can wake google up.
####################################################
UPDATE:
So Broadcom just released a wifi driver fix several days ago which may solve this issue. According to the record, phones with non-zero MAC address suffer from problem.
The driver has been incorporated into the latest Cyanogenmod(either RC or nightly build). People are reporting it fixes the problem while in some other cases, the problem still exists even after the fix, even for people who's MAC address starts with 00.

Last.fm works fine with the screen off here, always has done. I even turned off mobile data to be sure it's not switching over to that.
This is with the wifi set to sleep with the screen off (ie. the default setting).

i've been using wifi fixer and since i installed it, i haven't had a single wifi disconnect on my home network(it seems to be a network dependent issue as i never have issues on other networks)

Jep4444 said:
i've been using wifi fixer and since i installed it, i haven't had a single wifi disconnect on my home network(it seems to be a network dependent issue as i never have issues on other networks)
Click to expand...
Click to collapse
But you did have the problem before you installed wifi fixer, right?

Rusty! said:
Last.fm works fine with the screen off here, always has done. I even turned off mobile data to be sure it's not switching over to that.
This is with the wifi set to sleep with the screen off (ie. the default setting).
Click to expand...
Click to collapse
yeah, the point here is that many phones have the wifi sleep policy issue(doesn't work).

Indeed, however mine does, so this thread will need both sides of the argument

No problems on my Nexus One, running latest CM 6 nightly build.
I bought it couple months ago from eBay, so I'm not sure which shipment it is from.

Only issue I'm having after upgrading to Froyo is that my phone won't connect to my home network by itself when in range.
I have to go into Wifi Buddy and manually connect. This never happened on 2.1, but magically started after the FRF50 update, and never fixed itself in the next couple of builds.

Forge94 said:
Only issue I'm having after upgrading to Froyo is that my phone won't connect to my home network by itself when in range.
I have to go into Wifi Buddy and manually connect. This never happened on 2.1, but magically started after the FRF50 update, and never fixed itself in the next couple of builds.
Click to expand...
Click to collapse
I have always had this same issue! Maybe its something to do with my home wifi? I am yet to test it on froyo.
I am mostly connected to wifi with no sleep issue.

I have kind of the same issue at home, I recently replaced my wireless router, I never had problems connecting to the old one it would just stop broadcasting constantly but my N1 would always connect automatically. With the new router my N1 keeps saying the connection is disabled and I have to connect manually. This never happens at work, it always connect automatically so it seems to have something to do with the router settings but I have no idea what.

No problems here. Last.FM works fine for me on WiFi when screen is off. I also get notifications. Running FroYo rooted with locked bootloader
Sent from my Nexus One using XDA App

Divster said:
I have always had this same issue! Maybe its something to do with my home wifi? I am yet to test it on froyo.
I am mostly connected to wifi with no sleep issue.
Click to expand...
Click to collapse
i am having the same problem, when i go out of range from my wireless and then back in range, the n1 just says scanning and never re-connects.
that said, using a channel lower than 11 on my router did seem to help with the sleep issue.

hbkmog said:
But you did have the problem before you installed wifi fixer, right?
Click to expand...
Click to collapse
sorta, i never had the issue on any network besides my home one

I've also been having the disconnect problem with my N1. Maybe it would help if people whose sleep policy is actually working could post what wifi router/AP/whatever they are using. Also, if possible the first for identifiers of their MAC address. I read on one of the Google posts someone with a MAC address starting with 38:E7 having problems. The MAC for my phone is the same. For what it's worth I'm using a D-Link DIR-655 router and a Speedtouch 716 v5 WL and am experiencing the disconnect on both.

I've had the issue with 2 N1 tested on 3 different routers. I've read that it is related to the low power mode the N1 uses while sleeping not playing nice with routers. Not all N1 show the problem, apparently only the most recent ones. I've called google support and was told google knows about the issue and is working on it, but I am a bit cynical and I'll believe it when I see a fix.
Wifi-fixer fixed my problem only after I disabled Sipdroid which was interfering with it.
Mac adress: 38:E7: D8
I'll post my router model later when I get home.

Divster said:
I have always had this same issue! Maybe its something to do with my home wifi? I am yet to test it on froyo.
I am mostly connected to wifi with no sleep issue.
Click to expand...
Click to collapse
williec30 said:
i am having the same problem, when i go out of range from my wireless and then back in range, the n1 just says scanning and never re-connects.
that said, using a channel lower than 11 on my router did seem to help with the sleep issue.
Click to expand...
Click to collapse
as a quick update... i installed wifi-fixer and things have been much better. will report back if things start to derail again.

cabreca said:
I've also been having the disconnect problem with my N1. Maybe it would help if people whose sleep policy is actually working could post what wifi router/AP/whatever they are using. Also, if possible the first for identifiers of their MAC address. I read on one of the Google posts someone with a MAC address starting with 38:E7 having problems. The MAC for my phone is the same. For what it's worth I'm using a D-Link DIR-655 router and a Speedtouch 716 v5 WL and am experiencing the disconnect on both.
Click to expand...
Click to collapse
D-Link DIR-615 with DD-WRT v14684, phone's MAC starts 00:23

It's weird because most of the time I don't have this problem. My WiFi stays connected all night long to WiFi. But once in a while it does disconnect and switch to 3g. I think its certain routers, because I didn't have this problem for first 3 months on my old router, now it happens with my new router.
My phone never has trouble reconnecting back to WiFi. Everyday when I come home from work, as I walk up my driveway the phone has already automatically connected to WiFi. I've made sure about this one since I read this problem all over.

I bought my Nexus One directly from Google when it came out for AT&T. It certainly has the wifi issue and it is very annoying. My expectation is that the phone jump on my wifi network when in range as all of my other phones have done. Instead I have to manually engage the phone to get on wifi. SUCKS!

this is the biggest problem for me with my n1.
although the wifi does stay awake, it slows right down..
if i ping my phone, the response time increases when the phone is asleep, but doesnt time out.
if i ftp a file from my laptop to my phone, the speed drops from 1mb/sec to 100kbps/sec when the phone is asleep.
i have found the app "fix my wifi" solves the problem of waking the phone after a few hours of sleep and finding the wifi has failed. if only there was a way of getting the speed to stay the same.

[Q] How to allow incoming TCP connections (WebDroid, SSHDroid, etc.)?

Hi all,
Wondering if anyone knows how to make Android open the ports necessary for incoming connections for server apps to work without having to ping the client first under su?
Or failing that, is there a way to run a script that will ping the client IP instead of having to run the command by hand in terminal?
Thanks!

New, clearer, catchier title

This is the dev section not Q&A.

TheATHEiST said:
This is the dev section not Q&A.
Click to expand...
Click to collapse
Sorry, my bad. Mods, could someone please move my question to the appropriate venue?
LOVE your nick and avatar, dude!
Greetings from a fellow damned heathen!

i would really love to see a solution there too!
RemoteSMS over wlan would be awesome

Yom said:
Sorry, my bad. Mods, could someone please move my question to the appropriate venue?
LOVE your nick and avatar, dude!
Greetings from a fellow damned heathen!
Click to expand...
Click to collapse
.............

Any takers?
Posted from My Hacked HD2

Second that! Something's off in 99/100 ROMS, TCP doesn't seem to do anything. Only one Sense ROM by cotulla seems to work.
I disabled the adblocking hosts file to test if it had anything to do with it (e.g. SSHDroid doesn't work with it) but that didn't help anything either

Agreed, does not seem to work on any rom I've tried, only Cotulla's 'Stock Desire' Sense build seems to work (this one: http://forum.xda-developers.com/showthread.php?t=893620).
Too bad Sense's so completely dire, otherwise I'd use that. I want CyanogenMOD.

Having the same question. I am sure here must be someone who knows how to enable inbound connections....

Little update:
I noticed it is possible for me to ping and use all services when using the gateway to access everything, in my case the access point/wifi router.
So it looks like this is some kind of routing/firewall issue but I can't find anything about default blocking or firewalling on android...

Good news. I found out what is causing this on almost every build.
It has something to do with the stock wifi tethering. If you try and enable it in almost every rom it will fail, but now turn on your wifi again and everything works as it would normally do!
The build it does work on also has working stock wifi tethering, so that explains that...
For now it's good to have this workaround and I hop to have a proper fix in the future

im using RAFDROID 3.0 and i dont think i have this problem at all. I tried SwiFTP and it connected without any issues.
Try to update the busybox version mine is 1.15.2

SantanaNL said:
Good news. I found out what is causing this on almost every build.
It has something to do with the stock wifi tethering. If you try and enable it in almost every rom it will fail, but now turn on your wifi again and everything works as it would normally do!
The build it does work on also has working stock wifi tethering, so that explains that...
For now it's good to have this workaround and I hop to have a proper fix in the future
Click to expand...
Click to collapse
I tried this on Frankinstine's awesome ROM, but no cigar. There has to be a firewall rule or setting we can tweak to allow this kind of traffic...

Yom said:
I tried this on Frankinstine's awesome ROM, but no cigar. There has to be a firewall rule or setting we can tweak to allow this kind of traffic...
Click to expand...
Click to collapse
It works for me, but it's not 100% foolproof. It seems to work for a while, but not permanently. However, it's still better than the ping method. The ping method would never work for me, since I use Wifi at least 4 different places a week. Even when done automatically, how would I know what to ping on what Wifi network?! Random DHCP on workstations notwithstanding...
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
At that point it "works" for me, at least for a while.
At the very least this seems to indicate that the broken Wifi hotspot and this problem are related -- on Cotulla's build (where stock Wifi hotspot WORKS), this problem is non-existent.

Unfortunatly your steps do not work for me :-(
strikernl said:
It works for me, but it's not 100% foolproof. It seems to work for a while, but not permanently. However, it's still better than the ping method. The ping method would never work for me, since I use Wifi at least 4 different places a week. Even when done automatically, how would I know what to ping on what Wifi network?! Random DHCP on workstations notwithstanding...
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
At that point it "works" for me, at least for a while.
At the very least this seems to indicate that the broken Wifi hotspot and this problem are related -- on Cotulla's build (where stock Wifi hotspot WORKS), this problem is non-existent.
Click to expand...
Click to collapse

engst03 said:
Unfortunatly your steps do not work for me :-(
Click to expand...
Click to collapse
That's unlucky. Those steps seem to "work" for me on CleanDroid 1.30. Maybe we can just hope it works again when the stock wifi hotspot is fixed.
Alternate "solution":
Get Cotulla's "Stock Desire" ROM: http://forum.xda-developers.com/showthread.php?t=893620
It definitely works on that. Too bad sense is dog****, and your battery will last for a day max.

strikernl said:
This does it for me:
turn on normal Wifi
wait around 10 seconds (for Wifi to 'start')
turn on Wifi hotspot (normal wifi should turn it self off automatically)
wait around 20 seconds (the hotspot takes a while to 'start', it actually fails (error) for me, but still does the trick)
turn normal Wifi on again
Click to expand...
Click to collapse
Just tried this and it worked. As soon as I started the wifi the second time my computer started pinging HD2.
My usual procedure for fixing this was to start wifi, see assigned IP address and then ping my computer from 'Net Ping' app. This can be faster sometimes.
Is there a way to port hotspot from Cotulla's build to a nonSense build? No way for me to come back to sense again

clyder said:
Just tried this and it worked. As soon as I started the wifi the second time my computer started pinging HD2.
My usual procedure for fixing this was to start wifi, see assigned IP address and then ping my computer from 'Net Ping' app. This can be faster sometimes.
Is there a way to port hotspot from Cotulla's build to a nonSense build? No way for me to come back to sense again
Click to expand...
Click to collapse
Don't know, it's probably in the kernel, so shouldn't be too difficult, but then again, I haven't really got a clue about building ROMs.

agarp said:
im using RAFDROID 3.0 and i dont think i have this problem at all. I tried SwiFTP and it connected without any issues.
Try to update the busybox version mine is 1.15.2
Click to expand...
Click to collapse
RAFDROID is also a sense build, we want it to work on all builds, stock and CM

[Q] Anyone else having wifi issues since OTA upgrade?

My unrooted Xoom does not want to keep connected to my wifi signal since the upgrade. I did not have this problem before, but now if I set the Xoom down for a minute or so, the screen on or not, and pick it back up it is no longer connected. Sometimes I find I am without a signal when clicking on a link just after entering a web site while actively surfing. I have the wifi disconnect policy set "Never." Is anyone else experiencing more problems since the upgrade?

No issues for me so far.

None here
Sent from my Xoom using XDA App

Not a problem so far..

wayne710 said:
My unrooted Xoom does not want to keep connected to my wifi signal since the upgrade. I did not have this problem before, but now if I set the Xoom down for a minute or so, the screen on or not, and pick it back up it is no longer connected. Sometimes I find I am without a signal when clicking on a link just after entering a web site while actively surfing. I have the wifi disconnect policy set "Never." Is anyone else experiencing more problems since the upgrade?
Click to expand...
Click to collapse
The only wifi problem I have is the kernel wifi driver memory leak mentioned elsewhere. My xoom will eventually reboot itself if left on wifi overnight.

wayne710 said:
My unrooted Xoom does not want to keep connected to my wifi signal since the upgrade. I did not have this problem before, but now if I set the Xoom down for a minute or so, the screen on or not, and pick it back up it is no longer connected. Sometimes I find I am without a signal when clicking on a link just after entering a web site while actively surfing. I have the wifi disconnect policy set "Never." Is anyone else experiencing more problems since the upgrade?
Click to expand...
Click to collapse
This really sounds like the WiFi driver leak problem as mentioned before. Your symptoms are exactly what I was experiencing, pre upgrade.
The workaround is to not set the disconnect policy to "Never". Since I have turned that off, I have not seen the problem.

Nope... no problem here... tried to restart?
Sent from my Xoom using XDA App

Sorry, no problems here with wifi.
Sent from my Xoom using XDA App

No problems here either.

Thanks everyone for all the input.
I must have missed the discussion on the wifi driver leak problem but will do a search on it. If you don't use the "never" setting, which one do you use? It looks like a compromise with the other two settings as I like to have the email and the internet ready and waiting when I turn the Xoom on.
To another suggestion, I have tried rebooting several times.
After further use, it now appears to be an intermittent problem as on occasion today it has not been dropping out.

Im also having this problem since the OTA with my Wireless tether connection.

The tiamat kernel fixes the wifi issues. Check it out in the dev section

i am running stock xoom non rooted. I too am seing issues occasionally with wifi. I have noticed the signal has become lower since the upgrade. My connection used to he good and now ranks as fair. I have restarted bit he the access point and the xoom no change

[Q]WiFi Problem when Dowloading

Im having some problems with the wi-fi connection. When it first conects, everything goes ok, but when I start to download anything, the connection just stops responding, even tough it looks like conected. What should I do?

I'm having the same problem and couldn't find the solution, did any solve the problem?

Wifi problem on MS2
After months of researching and suffering the pain I still have not got a full solution for my MS2. My wifi problem is that it connects well, great wifi speed on my home network. But after a couple of minutes there's no more internet access even though it shows that its connected. I chanced upon this link laptopmag.com/review/cell-phones/motorola-droid-2.aspx?page=4 where it had the same problem brought up. It had a solution/fix which I do not want to use though. Further information can be found on the droidforums link on that page. What I have been doing all along is the same as what the guys at laptopmag has been doing, just reconnect whenever internet is down. Irritating yeah, but don't really have any other option..
Hope someone does have a proper solution :X
In addition to the sporadic troubles loading some sites with Flash elements, we had a much more persistent problem maintaining Wi-Fi connectivity. On three different routers, the Droid 2 would connect and then, after a few minutes, would continue reporting that it was connected but stop downloading data. The solution to the problem, once you notice it, is to disconnect from the router then reconnect, but that is a huge hassle.
Our original Droid experienced the same Wi-Fi problem so many times that we eventually gave up and resolved to use 3G only. However, after searching through several Droid forums and finding dozens of posts from other users who experienced the same problem on first-gen Droids and Droid Xs, we found a possible solution that seems to have worked with the Droid 2. After we changed the settings on our 802.11n router from mixed mode to 802.11g only, we did not experience the problem again, though we had to operate all of our computers on the slower 802.11g speed, which is unacceptable.
Click to expand...
Click to collapse

in my case all I had to do was port forward som port i dont remember
Sent from my A953 using XDA App

I installed the BlurLess GB rom and the problem is now gone.
Btw, my router @ home is G only, so the solution posted did not apply for me.

Known problem or defect device?

So I've been using my Kindle Fire for a couple of weeks now, and I've found a problem that's been hindering my use.
When I am (decently) far from my router, my Wifi on the Kindle Fire keeps dropping and then it reconnects. The connection is still at around 2 bars whenever it does it. I don't understand, because with my smaller phone (HTC Sensation 4G), my Wifi does not do this...
Is this a firmware issue (I am not rooted) or is it unique to my device? I have updated the firmware and everything...
Thanks.

I've been running into this exact problem (non-rooted KF). For the first few weeks, I had zero issues.
Now suddenly, I can't seem to stay connected for more than a few minutes at a time.
Even standing literally next to the router produces the same results.
I use plenty of other wireless devices in the house and I've never ran into any of these problems.
I'm using a Netgear WNDR4500; not a cheap router by any means.
I did a little research the other day, this seems to be a somewhat well-documented problem. Doesn't seem like any solutions have been found yet, though. I noticed the problem only seems to happen when the Kindle has been on standby for a few days. A restart seems to stop all the disconnects, at least for a few days.

maybe cleaning up saved networks helps
to do this:
disable wifi
open /data/misc/wifi/wpa_supplicant.conf and delete everything exempt the first two lines:
Code:
ctrl_interface=tiwlan0
update_config=1
save the file (beware the permissions rw-rw----)
enable wifi
you start with a wifi configuration like out of the box

b63 said:
maybe cleaning up saved networks helps
to do this:
disable wifi
open /data/misc/wifi/wpa_supplicant.conf and delete everything exempt the first two lines:
Code:
ctrl_interface=tiwlan0
update_config=1
save the file (beware the permissions rw-rw----)
enable wifi
you start with a wifi configuration like out of the box
Click to expand...
Click to collapse
Does this require root? I'm not rooting for another couple months to be safe.
Sent from my Kindle Fire using xda premium

Also, does anyone else have this same problem?
Sent from my Kindle Fire using xda premium

N4rbs said:
Does this require root? I'm not rooting for another couple months to be safe.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
don't really know cause mine is rooted - you can try it with es file explorer or any other which reaches the file - if you can't safe it then you need root - but i don't think so cause it has write permissions to the user group

KF's WiFi does seem to be a bit wonky... I've had trouble associating with networks a few times, required a reboot/toggling WiFi on and off.
Does anybody have this problem with a custom rom? If not, it could be Amazon trying to do something funky with powersaving. On my dm1z, if I set my WiFi adapter to "max power saving mode", I see very similar behavior...

The wifi on the kindle is great....it probably has to do with interference in your network. Try changing the channel you use for your network.

So, I compared another kindle fire to mine and it did not have the problem...I guess I will be calling amazon for a new one.
Sent from my TripNiCE Pyramid using xda premium

G1ForFun said:
The wifi on the kindle is great....it probably has to do with interference in your network. Try changing the channel you use for your network.
Click to expand...
Click to collapse
There's no 2.4ghz network within about 1500 feet of my home (and I know what channel that network is on), so I really doubt that's the problem.
As I stated above, as soon as I restart the KF, the wifi works perfectly for a while. It's only happens after the KF has been on standby for about 4-5 days; that's when the connectivity issues start.
The only reason I'm here (over the amazon forums) is because people here actually know what they are talking about. Everyone over there has the generic "it's your network" response. I manage networks for a living, something is most definitely not working correctly on the KF. When the parents came over, I had them test their KF (I made sure it was on standby for at least a few days); I had no problem staying connected.

I have the same issue and I'm running CM7. I'm constantly having to disable and then re-enable wifi to jump start it. Phones never have this issue on my home network and this is the only network that my Kindle has ever connected to.

N4rbs said:
Does this require root? I'm not rooting for another couple months to be safe.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
yes it does. without root you cannot manipulate any files in /data

hnosaj said:
I have the same issue and I'm running CM7. I'm constantly having to disable and then re-enable wifi to jump start it. Phones never have this issue on my home network and this is the only network that my Kindle has ever connected to.
Click to expand...
Click to collapse
Same here. It is not in any way a network issue. Never happens with my desktop, laptop, or phone, all on wifi.
Sent from my Kindle Fire using xda premium

my wifi on my fire is stronger than on my infuse

Wifi strength isn't the issue for me, it's plenty strong.
The issue is that it cuts out in the middle of me using it, which leads to me turning wifi off and then back on.

Mine does this after it's been on standby for awhile, The wifi won't turn on and i have to do a reboot to get it working. had the problem with KF 6.2.1 And CyanogenMod7, seems to be the hardware.

Aronoskarss said:
Mine does this after it's been on standby for awhile, The wifi won't turn on and i have to do a reboot to get it working. had the problem with KF 6.2.1 And CyanogenMod7, seems to be the hardware.
Click to expand...
Click to collapse
only a possibillity:
do you use manual ip-settings on the kf ? - it don't seem to like that
and if you switch wifi off and on again instead of rebooting - does it work again ?
seems to be a common problem ...

I don't use manual ip settings.
Turning Wifi off and then back on works for me but it's kind of annoying.

I too have had this happen twice since I got my fire 12/23. There is no problem with anything else connected to the network. Turning the network on and off does not help nor does rebooting the kindle. I have run wifi analytics and it does not see my network. The only solution is to reboot the router. I have not rooted mine yet either.
If this is a known problem with the fire hardware I will need to contact CS. Hopefully I will not need to go to the hastle of returning it.

i have this problem too - very rare but have it also - reboot the router and everything is ok again - every other device connects flawlessly - seems like a problem of the router (linksys 160nl)