Good evening all !
I recently started experimenting with Android on my Nook Color. The Nook Color is running 1.4.1, I followed all the instructions to run it from my SD Card, which seems to work fine. The problem I have is connecting to my wireless router. I have managed to connect to an unsecured router (A random one that showed up) and it works fine. I have unchecked uPnP, and I have three laptops, Xbox360, PS3, WII, you name it and it connects just fine after entering the password. It is currently WEP. It attempts to obtain an IP address, then says connecting, and starts the process all over again. As I have said, I am running it from an SD Card and it seems fine, except for the wireless. I was able to connect to the Android Market, etc. I was just playing around with it and have discovered this issue. Any ideas out there? I would greatly appreciate any tips. I have restarted the router, even tried clearing it out in the terminal (I found somewhere else, for the airplane mode, the icon shows all the time)............
Nevermind everyone..got it....wrong freaking key..changed while i was deployed
Related
Hi Folks,
I just got a Nook Color for xmas and I am seeing some very odd issues when I try to connect to my home wireless network. I am seeing the issue when it tells me it's "Connected, but no internet". The odd thing I am seeing is that it seems to be stuck trying to use the same IP and default gateway no matter what I do. I have a Belkin router and it was using WEP. The device was assigned an IP of 192.168.2.36 and it worked for a little bit. Then it stopped working. I tried changing it to WPA2 and still no luck. Figuring it was my router I bought a new one. I created a new wireless network with a new name and new subnet of 192.168.5.0/28 and STILL when the nook connects to this network it tries to use the IP 192.168.2.36. I put the network back to 192.168.2.0/28 and still it does not work. I setup the Belkin again as a wireless access point and made it open with no security with a totally different network SSID and it still wants to use this IP address. I connected to the nook with adb shell and tried ipconfig, netcfg, setting default route etc all with no luck. At some point during this process I rebooted it 8 times and flashed back to 1.0.0 firmware, wiped the /data directory and it STILL tries to use the 192.168.2.36 IP address. I am at a loss as to what to try at this point. The odd thing is I can connect to my neighbors open access point which is using 192.168.1.0/28 as its subnet and the NC works. Any suggestions anyone could provide would be much appreciated.
Thanks in advance.
You need to get the latest update.
ovidsmuse said:
You need to get the latest update.
Click to expand...
Click to collapse
I have software version 1.0.1
Hey guys, so here at PITT, the school runs a 802.11x infrastructure wifi network, and I cannot connect.
I am running HC v4. When I go into WIFI, the Nook will see the network. Then when I put in PEAP, my username, and password, nothing happens. I just hit "connect" and the nook does nothing. It is like it does not remember the settings I just put in.
It connects fine to the adhoc network on my phone (tether). Also, it connected to PITTnet fine before when just rooted, and with nookie froyo.
I tried doing this (with slightly different settings): http://forum.xda-developers.com/showthread.php?t=974689&highlight=wifi
But it did not work. It is like the Nook sees the network, but just refuses to do anything with it.
Any ideas? Thanks.
I connect to an 802.11x network here @ work, and my recommendation is to hop on the market on another wifi connection, and download "Wifi ACE" to facilitate editing the config easier. If you can't download from market but have ADB working, you could manually install the .apk from here: http://code.google.com/p/android-wifi-ace/
I will tell you - I've had spotty capability to access this network using HC v4, internal eMMC build v2. I have 100% success using Nookie Froyo and Phiremod, by comparison, using the exact same settings - I manually saved off the wpa_supplicant.conf file between installs. I experience the same symptom you do, I see the network fine, just refuses to connect.
Think we're just stuck till AOSP releases and we get a new version of HC on the NC.
Same as you, any other WiFi network connects with ease. It is just the 802.11x network I have problems with. It worked for me on HC eMMC v1 though, so if you haven't tried that give it a shot.
Hi everyone.. I'm really hoping you can help me with this final issue to get my color nook up and running. I am running a rooted nook (autonooter) with the ad-hoc workaround installed. The machine can find and see the ad-hock network that I setup using my iphone with mywi 4.11.2 (no wpa setup).
The nook attempts to connect to it and gets stuck obtaining the IP address - nothing I have done (reboot, toggle wifi, etc) allows it to connect successfully. I am able to connect other machine (netbook/ipad) to the iphone so I know it is broadcasting/connecting ok... also, I can establish a connection on the nook to other wireless networks.
I'm about at my wits end as this is the final piece I need to get things rolling... any thoughts/ideas, etc?
Thx!!
Never mind... I fixed it by installing the 4.50.6 version of Mywi on the phone.. works like a charm now! Thx!
I have been having issues where i am connected to the wifi but the device stops passing any traffic. I have fing installed and i can't ping any other devices on my network. I know its just my phone because i have my work phone and tablet connected to the wifi and they still work fine browsing webpages, watching movies etc while the droid turbo can no longer communicate with the local lan or out to the internet. If i switch the wifi off then on again it will reconnect and then work normally. I can then ping devices on the local lan and access pages on the internet. This has happened a number of times now since i got the device.
Edit: I just updated the phone and still get the issue. I have a cisco WAP at home, we have cisco WAP's at work which i will test tomorrow. If this thing still has issues i am just going to swap it out for a Note 4.
Check this out:
http://forum.xda-developers.com/showthread.php?t=2925844
I've been seeing issues with Cisco wlans too.
Sent from my XT1254 using XDA Free mobile app
so it looks like it works good at work, something with my home cisco ap and this phone as all other devices at home work ok.
-magnum- said:
I have been having issues where i am connected to the wifi but the device stops passing any traffic. I have fing installed and i can't ping any other devices on my network. I know its just my phone because i have my work phone and tablet connected to the wifi and they still work fine browsing webpages, watching movies etc while the droid turbo can no longer communicate with the local lan or out to the internet. If i switch the wifi off then on again it will reconnect and then work normally. I can then ping devices on the local lan and access pages on the internet. This has happened a number of times now since i got the device.
Edit: I just updated the phone and still get the issue. I have a cisco WAP at home, we have cisco WAP's at work which i will test tomorrow. If this thing still has issues i am just going to swap it out for a Note 4.
Click to expand...
Click to collapse
Yeah this phone does not seem to like my router for some reason. Keep in mind I'm not a networking expert, but I've tried every combination of options and settings every which way from Sunday and I just can't get the thing to work. When I do connect the phone to my wifi it kills the the connection on every device in the house. At first I though it was just a wireless thing, but even the downstairs computer which is plugged in directly to the router doesn't work. Then as soon as I disconnect the phone every device works again. I thought maybe there was too many devices, so I disconnected all but the downstairs computer, still had the issue when I connected the Turbo. I've tried just turning off the WPA2 and just having an open system, I've tried connecting the phone using a WPS pin (This one actually worked for a good 5 minutes before crapping out and hasn't worked since). On the advanced options of the phone I tried an automatic IP as opposed to the default DHCP setting (This also worked for a good 5 minutes before not working ever again). I've tried limiting it to just one frequency band. I have tried so many different things and I just cannot make this phone work on my router. And I know it's my router because the phone works fine at work.
phone: Droid Turbo
Router : Asus rt-ac66r
yup within ten minutes of getting home, the device no longer passes traffic. My work S5 still works fine at home and so does my samsung tablet. The device worked on wifi all day at work on our enterprise wpa2 network no issues. I tried doing static ip at home, changing to 2.4 ghz, trying new ssid. Not sure what else to do with this thing...
Not just you
I posted a comment on Motorola's forum where people are discussing their wifi issues... And my work around. I currently beleive its a software issue and can be fixed via update. Also, today I found (it appears) that the longer the phone goes without a reboot, the shorter amount of the it appears to go with out needing the wifi card reset.
https://forums.motorola.com/comment/829632
My work around fix...
First, over night my wifes phone now behaves just like mine. It now connects to wifi and after sometime passes it no longer passes data (but stays connected). I needed a way to auto disable/enable the card... I installed Tasker. I have it set to check every 15 minutes, if the phone is connected to WiFi, to disable then enable the WiFi card. I use WifiMatic to enable the wifi card when the phone is connected to the cellular tower that is near my house. (Doing this by GPS uses more battery power...) Using Tasker with the rule to verify its connected to wifi first helps not enabling wifi if its nit needed and lets WifiMatic enable/disable it as needed.
wicketts.net
I use the ComicRack PC and Android programs to sync comic files to my tablet on my home network. This generally works okay but occasionally the tablet will not connect to the server.
When this occurs, I have tried pinging from my tablet to the PC (using various android network tools like Fing) and the pings fail. In fact, when this happens I can't ping ANYTHING from my tablet, not even localhost. But my network connection is active because I can still get to both my local network files (using ES File Explorer) and the internet just fine.
I have tried resetting my wifi connections, setting static ip addresses, changing from 2.4 to 5 g networks, and a number of other things. The fact that it won't even ping localhost, however, would seem to indicate the problem is with the tablet and not the network.
After a few days (or weeks), it seems to start working again randomly - not from rebooting or anything else, it just does.
I am currently not rooted, running factory rom (see attachment). I'm considering rooting to see if I can get around the problem but since I use Private Mode I've been hesitant to do so.
Any ideas? I seem to remember reading somewhere that Samsung devices occasionally had wifi problems, but don't know if that applies to this issue.
Any help would be appreciated. Thank you.