Related
So ever since I've gotten my Nexus One I've been noticing it drops out of a WiFi way too often. It does it both at home and at work on Wireless routers using the latest firmware. I've set the sleep policy to never go to sleep but most of the times I wake my phone up, I'll find it on 3G instead of the full strength WiFi it should be on. On 2.1 when I'd go into WiFi settings it would show the connection and say something along the lines of "Connection unsuccessful, tap to try again" and on 2.2 it just says "Disabled, Secured by blah blah blah". If I retry, it ALWAYS connects and WiFi will stay active for a short period of time before falling back to 3G.
Is there some way I can tell Android to retry the WiFi connection if it fails instead of just giving up? I've been looking through the WiFi API's on the Android Developer site and I'm this close to writing an application that will attempt to mitigate this issue for me.
If I'm within range of one of my pre configured networks, I want the phone to try it's hardest to stay on WiFi. If it loses connection, retry. It it can't get it after 5 retries, wait five minutes and try it again, don't just give up and mark the connection as disabled.
I've read tons of threads about people with WiFi issues and people always say "it's the router, it's the channel, etc, etc" but my WiFi works perfectly fine as long as there is a human to reconnect it if it drops.
Anyone else in the same boat as me?
ok so apparently I'm the only one with an N1 and a WiFi issue.......
I have the same exact issues.
I have the same issue as well and if it stays on I have to turn wifi off and back on so it will connect properly
-------------------------------------
Sent via the XDA Tapatalk App
same issue here. i had been looking for an app that would force the connectivity, but the market doesn't seem to have it. just a bunch of crappy wifi on/off switcher management apps. i'm surprised that no one has hacked this function or built an app for it.
It's certainly a very annoying problem. Mine will go to known good wifi networks, at work, at home and at other locations where my other devices work flawlessly. I have a coworker with the exact same firmware (we updated using the same file) on a nexus one that has never seen this problem, which I find odd, but I'm fairly new to Android. It looks like a software or driver issue to me, but as I said, I'm new to Android.
My device shows the known networks as "Disabled", but I can connect manually.
Looks like it's worth me coding up an App to fix this then.
what kernel are you using? i used to have that problem but that has gone away with newer kernels. unfortunately a new problem has arisen where after being in standby for a while, wifi shows as connected but doesn't have an outside ip. wondering if its my rogers modem or not.
y2whisper said:
what kernel are you using? i used to have that problem but that has gone away with newer kernels. unfortunately a new problem has arisen where after being in standby for a while, wifi shows as connected but doesn't have an outside ip. wondering if its my rogers modem or not.
Click to expand...
Click to collapse
2.6.32.9-27220-g328f560
android-[email protected]#1
I've never tried a new kernel.. Is this something I should look into?
I'm running the same kernel.
BootsSiR said:
Looks like it's worth me coding up an App to fix this then.
Click to expand...
Click to collapse
Personally I wouldn't do any work towards writing an app to fix this since it looks to me to be an OS or driver issue that should be resolved in a future release (hopefully in very short order).
An app would really just be a band-aid, but I'm the lazy type and I can deal with using my cell ular data when I don't feel like reconnecting my wifi.
Full disclosure: I'm a crummy programmer and it takes me forever to write stuff so I'm usually less inclined to do it.
w9ndb said:
Personally I wouldn't do any work towards writing an app to fix this since it looks to me to be an OS or driver issue that should be resolved in a future release (hopefully in very short order).
An app would really just be a band-aid, but I'm the lazy type and I can deal with using my cell ular data when I don't feel like reconnecting my wifi.
Full disclosure: I'm a crummy programmer and it takes me forever to write stuff so I'm usually less inclined to do it.
Click to expand...
Click to collapse
I'd rather take the time to fix it then wait for an update that may never arrive. Always fun digging into the API anyways
That's cool. I still find it a bit troubling, though, that some devices see it and some don't, using the same firmware, on the same wireless networks.
I guess it could be a board rev. difference or an app conflict or something. ::shrugs::
I have a similar problem. I use APNdroid to keep cellular data off and use wifi, but I continually have to reconnect wifi no matter what if I am not actively using it. Defeats the purpose of push email.
I downloaded APNdroid after checking data usage and finding that with wifi on there was still significant 3G leakage. Especially confusing with wifi set to never sleep and plugged in overnight.
On the plus side, APNdroid has netted me a lot more battery life, I can almost get two days and one night. I almost never use my spare battery anymore.
Just as an additional data point, I am having the exact same issue with 2.2 FRF83 (I had been on FRF50).
It looks to me like it is simply scanning all of the time and never associating with a known network. I'm not sure why it flags them as "Disabled", however.
Have you guys tried to set the "wi-fi sleep policy" to "never"
if not, try this:
Wifi settings->menu->advanced->wifi sleep policy->Never
safeplayer22 said:
Have you guys tried to set the "wi-fi sleep policy" to "never"
if not, try this:
Wifi settings->menu->advanced->wifi sleep policy->Never
Click to expand...
Click to collapse
Yeah, it doesn't help, that was one of the first things I tried. Any time I leave and come back, the networks show as "Disabled". It's a frustrating issue in that it isn't consistant. It's 80% fail, 20% work.
I had my g1 for a year now and just now got my n1. I havent rooted it b/c of this bug. At first i couldnt listen online radio b/c as soon the display went out it would buffer the whole time. I played with the wifi router and the n1 wifi settings an managed to fix it somehow, BUT when i wake up in the morning for some od reason it lost connection and never reconnected again. So i can hear online radio with the display out but after some hours w/o online radio and just in standby it loses wifi connection and never connects again
This issue is not new. There is a thread on the google forum many pages long. Nobody hase even a clue where it could come from. Some1 on the forum said if u call support they will tell its ur routers fault.
The n1 completly ignores the sleep policy settings.
I have rooted two g1s with goldcard and still using one w/o a problem.
-------------------------------------
Sent via the XDA Tapatalk App
Zapo said:
I had my g1 for a year now and just now got my n1. I havent rooted it b/c of this bug. At first i couldnt listen online radio b/c as soon the display went out it would buffer the whole time. I played with the wifi router and the n1 wifi settings an managed to fix it somehow, BUT when i wake up in the morning for some od reason it lost connection and never reconnected again. So i can hear online radio with the display out but after some hours w/o online radio and just in standby it loses wifi connection and never connects again
This issue is not new. There is a thread on the google forum many pages long. Nobody hase even a clue where it could come from. Some1 on the forum said if u call support they will tell its ur routers fault.
The n1 completly ignores the sleep policy settings.
I have rooted two g1s with goldcard and still using one w/o a problem.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Well, I know fore a fact it's not my access point. I am a network engineer and worked on wireless systems for years and debugging these types of problems is something I'm a bit obsessive about. This stinks of a software or driver problem to me. It could potentially be a hardware revision issue since we have a N1 that works perfectly in all scanerios.
I've tested this with the following access points:
Apple Airport Extreme
Apple Airport Express
Meru
Cisco 1231
Cisco 350
Belkin pre-n
Linksys WRT54G stock
Linksys WRT54G dd-wrt (I forget the build number)
Soekris Engineering running pfSense
All exhibit the same behavior, while my control devices (Apple iPhone 3g, Apple Macbook Pro and a MyTouch 3g running Cyanogen 2.1).
I wasn't aware that this was related to rooting, I'd be more than happy to move back to a stock ROM if that solved my problem. Maybe I'll try that today if I get some time.
Could you possibly post a link to the google forum you're referencing?
I'm currently digging through the alogcat output to see if there is anything interesting in there.
This issue is worse since I upgraded to 83. I'm actually holding off to try CM6 when it comes out to see if there is any better performance there. I'm not sure if he uses updated drivers or kernel that may give better wifi performance.
Hello, I wonder if its possible to put in a 3g modem and use mobile broadband on the nook ?
Please excuse me for bad my bad English
Hardware modification is a lot of work. In most cases it's not even possible.
You are better off tethering to your phone or a hotspot if wifi isn't available...
In my opinion.
k0ng0 said:
Hello, I wonder if its possible to put in a 3g modem and use mobile broadband on the nook ?
Please excuse me for bad my bad English
Click to expand...
Click to collapse
Where do you propose to insert the USB 3G device? Maybe once Bluetooth is working there will be a device to add 3g via Bluetooth. But there is not, as far as I know, 3G hardware available on the NC board... yet.
migrax
ps: forgive me if I appear to be a smartass.
k0ng0 said:
Hello, I wonder if its possible to put in a 3g modem and use mobile broadband on the nook ?
Please excuse me for bad my bad English
Click to expand...
Click to collapse
I'll make it simpler than the others...
Sorry, no.
Sadly the nook doesn't really have the capacity to add 3G hardware. Some tablets do have full sized USB ports that can physically connect to a USB 3G modem, but there is no built in driver support on those tablets either. Your only real option currently is wifi tether to a 3G phone.
Just in case any of these replies are missing information you need:
1. No, you can't add 3g to the Nook, in fact this is why i love it as a tablet - no extra data plan to pay for
2. BUT you can easily use the nook's wifi to connect to a portable hotspot
3. You could if you wanted buy a portable hotspot (e.g. Mifi, or overdrive), but these come with expensive data plans
4. You can use your regular cellphone. This requires rooting on an android device, and I do not know if this is possible on other platforms. Anyway, I reccommend "wireless tether" as the app to use simply because it can be set up to only communicate with MAC addresses that it approves (it's great being in an airport and seeing all the internet leaches being bounced off your phone's hotspot).
5. If you are super lucky, your phone will operate as an 'infrastructure network', and you can stop reading right now! ;-) However, more than likely, your phone will operate as an "adhoc" network, not an "infrastructure" network. This requires some tweaking of your nook on 2.1 ROMS (there's several threads on this), but is built into 2.2 (which is a major reason to move to Froyo).
6. The ad-hoc fix is a bit buggy, and whatever B&N changed in 1.1 makes this much worse. Again there's several threads describing this. In 1.01 the solution as to use an app to shut down and restart the wifi as the screen shut down or tuned off. BUT THIS DOES NOT FIX THE PROBLEM IN 1.1 AND IF ANYTHING MAKES IT MORE ANNOYING.
7. Basically there is some issue in 1.1 where when the nook wakes, the wifi is on but it may not reconnect to a network until you tell it to. This happens occasionally for the stock wifi, but happens continuously with the ad-hoc fix. The best workaround i have found is to have an app called "wifi buddy" in my dock - then when the machine wakes up if it can't see the network, i just launch wifi buddy and it connects immediately.
Hope that helps
That would be nice, what I do is tether my iPhone to my nook using MiWi. Its fast and reliable
Tether Nook Color to iPhone using PDAnet?
mateo124 said:
That would be nice, what I do is tether my iPhone to my nook using MiWi. Its fast and reliable
Click to expand...
Click to collapse
I am using PDAnet on the iPhone. It's free and also offers the option to broadcast a WiFi hotspot. Other iPhones and my laptop see the hotspot but the Nook does not. Has anyone tried that yet?
Found the answer!
Ad-hoc fix for tethering
I found a great guide to use PDAnet (free version) for tethering the NC with my iPhone 3Gs. Hooray for this awesome forum!
If you could somehow get the SoC from the Droid X in there... it might be remotely possible. But the time and effort required would make this a purely "did it to say I did" type of hack.
Save your duckets and get a real tablet when the dual cores get affordable.
cal3thousand said:
Save your duckets and get a real tablet when the dual cores get affordable.
Click to expand...
Click to collapse
I AM trying to get a real tablet... it's just that it's hard to find the perfect one
cal3thousand said:
Save your duckets and get a real tablet when the dual cores get affordable.
Click to expand...
Click to collapse
Or, while waiting a year for that to happen, buy a NC that will do 90% of what that one will do now for half that price.
/shrug
It's your choice.
Brand, spanking new NC, came with updated software version already installed. Freshly rooted. Won't recognize ad hoc networks, of course :-(
Already tried the most up to date wpa_supplicant file fix, to absolutely no avail. Using rooted droid 1, with well-functioning wireless tether. Barnacle also a no go.
Any suggestions would very appreciated. Pulling my hair out, one by one, getting balder...balder.......
mjf0000000 said:
Already tried the most up to date wpa_supplicant file fix, to absolutely no avail.
Click to expand...
Click to collapse
What does this mean?
Thanks for your help. What I mean is that the wpa supplicant fix (as described in previous threads - I'm using the Droid 1 browser or I would link back to that xda thread - sorry!) produces no effect. When the NC scans for wireless sources it recognizes many hotspots. Including my home wifi router. It simply will not list the phone's ad hoc signal (called either android tether or barnacle, depending which turned on.) The winbox connects just fine, so I don't think it's the phone's signal.
Others have used the wpa supplicant fix and their NC has worked well, but from what I can tell, they have NC's that were not upgraded to latest version, or had upgraded themselves. I wonder if brand new NC with the upgrade installed, needs a different fix. Not to be paranoid, but the wireless tethering apps have fallen out of favor with the powers that be. Maybe there is more disabling going on --- or I could just be doing something wrong. (Would not be a surprise)
Has anyone with a NC that came with the update pre-installed been able to get wifi tether? Using a phone with the paid wifi hotspot function will work with the NC. However, the droid 1 does not have a paid wireless hotspot option (it's too ancient, apparently). I had to sideload the wireless app to my phone, as it's not available on the market anymore, andit works well - just not with NC, even with the standard wpa supplicant fix.
Would upgrading the NC to CM7 take care of this issue? I'm a children's doc with skimpy hacking skills, & am a little afraid to try the procedure. Like doing an appendectomy with without knowing human anatomy
mjf0000000 said:
Has anyone with a NC that came with the update pre-installed been able to get wifi tether? Using a phone with the paid wifi hotspot function will work with the NC. However, the droid 1 does not have a paid wireless hotspot option (it's too ancient, apparently). I had to sideload the wireless app to my phone, as it's not available on the market anymore, andit works well - just not with NC, even with the standard wpa supplicant fix.
Would upgrading the NC to CM7 take care of this issue? I'm a children's doc with skimpy hacking skills, & am a little afraid to try the procedure. Like doing an appendectomy with without knowing human anatomy
Click to expand...
Click to collapse
Wireless tether is working perfectly for me with CM7 right from the get-go, however....It does not work with Honeycomb at the moment (and I have not done the supplicant fix yet).
Thanks, hockeyfamily. I should probably go ahead and do the CM7 ROM.
update
Still have rooted v 1.2, not yet CM7. What finally worked for enabling ad hoc wifi, was deleting everything i had done previously, redoing it over again, & using Barnacle. The Wireless Tether app just giving a message to the effect that it was 'connected, but no internet.'
I updated to 1.2, rooted with an early version of MN, have an Eclair phone running Barnacle and this http://forum.xda-developers.com/showthread.php?t=872521 works great for me.
Has anyone been able to get any version (2.0.7 or 3.x beta) of Google's WiFi Tether app working on their rooted Droid Bionic? Link to app
It didn't seem to work for this guy at the end of the video: Link
For me tethering is critical for work and I don't want to activate my Droid Bionic (which is coming tomorrow) until it can be confirmed working. Will keep using Thunderbolt for now... I can also imagine this is a huge issue for many other users.
However, I am aware that Motorola devices need some kind of device profile in the "Change Device-Profile" option in the settings of that app, has anyone played around with that, maybe choosing the Droid X or other Droid?
Any feedback greatly appreciated...
I hope you find a solution soon, I also have the same problem
Don't bother until a custom ROM comes out that can "hide your ass".
Since it is for work, paying for the monthly tether should be a business expense.
I tried some of the work-arounds on the net... barnacle did not work for me... choosing the droid x profile in device setup at least showed my wifi hot spot, but I could not obtain an IP... I had also noticed errors about dhcp in the log.
kierandill said:
Since it is for work, paying for the monthly tether should be a business expense.
Click to expand...
Click to collapse
exactly, in the mean time your going to be stuck using PDAnet and a USB cable.
Got it, rooted it, figured it out. Use version 2.0.7. Change the LAN option to 10.10.1.x
Also it only works in ad-hoc mode but at least its a start. I'm sure updates will fix it.
open1your1eyes0 said:
Got it, rooted it, figured it out. Use version 2.0.7. Change the LAN option to 10.10.1.x
Also it only works in ad-hoc mode but at least its a start. I'm sure updates will fix it.
Click to expand...
Click to collapse
Woot! I don't own one but I am glad you got it going perhaps a screenie of some data transfer?
Also try this with the 3. beta if you don't mind
Brenardo said:
Woot! I don't own one but I am glad you got it going perhaps a screenie of some data transfer?
Also try this with the 3. beta if you don't mind
Click to expand...
Click to collapse
Can't get 3 beta to work at all but it doesn't offer anything other than ad-hoc mode also. Also doesn't show data going through on the app. But hey at least it works.
Can anyone confirm the 2.0.7 wireless tether working?
not working
2.07 not working for me even using the 10.1 network. clients fail to obtain an IP address.
Same problem here - wifi tethering not working...
The newest 3.x didn't work for me. Has anyone tried manually setting the client's IP/Gateway/DNS? I don't remember what the dhcp issued on my incredible, otherwise I'd go grab my laptop and mess around with different static settings.
RawNis said:
2.07 not working for me even using the 10.1 network. clients fail to obtain an IP address.
Click to expand...
Click to collapse
It takes a long time I noticed. Wait for the little blue notification icon to appear that shows the device is connected. Can take as long as 3 minutes sometimes but it works for me I assure you. The key thing is the 10.10.1.x network which is still unblocked because VPN's can use that network, anything other than that won't work.
I can't get wifi tehthering to work but just using the phones built in usb tehering option works and does not send me to a page to subscribe for tethering. Don't know why this works but if I try the built in wireless tethering it says I have to sign up. EDIT Was working on launch day but tried again today and won't work so I guess the system wasn't updated the first day I tried it.
Hi,
I found way to enable Hotspot without Verizon Provisioning. I used SQLLite Editor to modify settings.db for "Settings Storage" application ( com.motorola.android.providers.settings ). Set entitlement_check to 0 and reboot the phone.
Dmitry
ddv2005 said:
Hi,
I found way to enable Hotspot without Verizon Provisioning. I used SQLLite Editor to modify settings.db for "Settings Storage" application ( com.motorola.android.providers.settings ). Set entitlement_check to 0 and reboot the phone.
Dmitry
Click to expand...
Click to collapse
I just tried this. It appears to be working. I was able to connect and browse from my laptop. Now the question is, does Verizon still know I'm tethering even though I'm not paying to tether?
I second. Works for me a well, with no warning or pop up. Cudos to you my good man
Sent from my DROID BIONIC using xda premium
Just did it and all seems fine so far.
btw, WOW. Ive never poked around the databases like that. Everything from the hdmi overscan to wifi info is in there. That is So cool.
Works for me too! However, only works properly with WPA security. If Hotspot is set to "open", you can connect but get no internet...
Like the title says my Wifi will not connect to my router at home, but works everywhere else..
I have a Linksys wireless-n router. I put in the password and it automatically says that it is remembered but not in range. Any ideas on how this could have happened? Any possible solutions?
I don't know about the wifi stuff too much, but I have seen reference to people changing from channel 11 (std factory setting) to channel 4 for example. Dunno if that helps. Good luck.
Sent from my SGH-I897 using XDA App
How does one do this? I've looked but couldn't find any directions.
Sent from my SGH-I897 using XDA App
Bjangles said:
How does one do this? I've looked but couldn't find any directions.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
you start with your router's IP address. if you don't know it, go to your command prompt and type "ipconfig" to figure out your router's IP address. Type the IP address into your internet browser to change the channel.
OK I'll try it later on tonight.
Go to google and type "linksys wireless n router change wireless channel" and select the first option you get (should take you to howtogeek.com)
Scroll down past the download it ask you to do and get to where it states Changing your wireless channel. Its pretty easy to do once you walk through that.
Does it only happen on the touchpad, or is it all devices?
It only happens with android (CM7 and CM9), web os is fine.
There has been issues with the wifi. I am running the bricked CM9 install myself and the wifi works just fine. Have you wiped the cache and all during install?
Seems that someone has posted a thread in the touchpad area concerning this same issue, thread will probably be moved once a mod gets a hold of it, but here is a link to it:
http://forum.xda-developers.com/showthread.php?t=1494458
ssid
Make sure you are broadcasting your ssid as android devices cannot see hidden networks, so you end up with "not in range" when you try to connect
I got it to work kinda. I have to leave and go out of range, them come back for it to work.
Does WPA2 broadcast the ssid?
There is an app in the Market labeled something like 'WiFi Fix' that 'helps' this issues as well. If I had my TP in front of me I'd get you the exact name, or if the Market would track free apps between devices like Amazon does, but I digress...
I use the word 'help' loosely above because the 'fix' wipes out all your wireless settings. It deletes all the profiles, etc. So after re-entering the keys you'll get right back on the wifi, but this is somewhat painful after every single time it goes to sleep...
Anyway, consider it an option, semi-viable at least.
If you can see your wireless in the list of available networks it is broadcasting the SSID.
I guess I'll just go for a stroll whenever my touchpad needs a restart. thanks for the help.
Bjangles said:
I guess I'll just go for a stroll whenever my touchpad needs a restart. thanks for the help.
Click to expand...
Click to collapse
I'd be going for lots of walks. Mine lasts for less than 5 minutes -- assuming it connects.
For the TouchPad, it seems the only thing that truly works is a wide open connection without authentication or encryption. People have had varying amounts of success, but I cannot get it to connect to my work's WPA2 Enterprise or anything above WPA at my house...
There's a couple of threads going on in the Development forum where they've basically said that Wifi for the TouchPad sucks and is in a major need of (re)working in order to get it right. The current ar6000 driver isn't cutting it and the ath6kl driver + wpa_supplicant are not Android complaint.
Someone has a kang (CherryKANG) with a supposed wifi driver fix, but if you look at what he supposedly built into his ROM vs. what is getting loaded, you can see it's not really there. (The link everyone points to is the new ath6kl driver, but if you look after flashing it's still running ar6000.)
I build a ROM with the ath6kl driver in place and it looked to work better for about 30 seconds. But you can tell it doesn't like to cooperate with Android too well at the moment. Makes me wish I was a hardware expert so I can rewrite the thing and make it work.
I'm pretty sure it's not a hardware issue since I can boot into WebOS and be find on ANY of the networks I normally connect to...