Database Develop

[Q] wifi problem (azusaROM 1.04.29062010)

hi, I bought a second hand tattoo last month, the previous owner installed azusa 1.03 on it but wifi didn't work at all (I was able to switch on the wifi) So I flashed with the last Azusa ROM (1.04).
first the wireless worked fine, but, I think after a reboot, the phone wasn't able to get IP address on every AP I tried. however I can connect a wireless network if I set a static IP on the phone...
any idea to fix this, please?
(sorry if it's a problem to post it a second time, but I don't know if the problem come from the ROM or not...)

Well, I have the same problem with the wifi. It sucks cause this rom is really fast and non-functional wifi is the only deal beaker... Try to contact the developer Coburn and ask him. If you reach him, tell him that I already posted a log of the problem on the project's site.
Sent from my Tattoo using Tapatalk

Any news on this? I really like the ROM but not having wi-fi completely kills it =\

None so far... And I doubt that there ever will be a fix for the issue. I abandoned this Rom.

hi, I didn't find a real solution for my problem... I just installed an app named "wifi static" and I set the few network config I use usually, it works, but I can't connect to any free hotspot easily.

CM7 Wifi Needs to be restarted every 3mb

Ok this is not your typical "my wifi wont connect issue"
i have tried a fios router, linksys cisco router w/ dd-wrt and linksys router stock. I first had cm7 on sd and assumed that was the issue so I flashed to emmc. It works great but the wifi stalls after about 3mb of transfer (or a couple of minutes of light usage) and i have to restart wifi with the power widget and it starts working again. EDIT: droid x and moto bravo work perfectly with these routers at the same time of the issue.
I already disabled wifi sleep policy.
I am using CM7 stable installed to emmc. its works fantastic otherwise but this is making it completely ususable for me. I dont think its a bad wifi chip since wifi was solid with HC on sd and seemed fine with stock nook 1.1.0
if i try to install an app it dies 75% through, if i try to play a youtube video it buffers 75% and then dies. it seems anything more than a simple web page lookup kills the wifi stack.
I havent had time yet to really dive in (been porting CWM to the motorola bravo in most my spare time) but hoping there is a simple fix out there, maybe i need to switch to dalgrin's kernel? but it also mentioned wifi issues and seems 2 weeks older than the kerenl supplied w/ cm7 but i am not sure.
This makes the nook completely unusable. Id rather not flash something else, it seems other people are having success w/ cm7 so I would like to work this out.
any ideeas? thanks

that sounds like possibly defective hardware honestly.... But you say it was fine on other ROMs so I dunno. I have had fewer problems on CM7 than Froyo myself. In fact CM7 has been solid with wifi. I wander around a lot with my NC and use many access points.

Do you have a logcat dump per chance?
If nothing is in the log, what is output of dmesg? Anything there that might suggest what's going on?
Also you might try checking out the command line program "wpa_cli". See if it helps you narrow down the issue. You can turn on additional debugging there.
Or, if you know how to rebuild your uRamdisk, appending "-DD" to the wpa_supplicant line in init.encore.rc would also give you more info in logcat...
One last thought-- if you are using dalingrins oc kernel, he took out a lot of debugging stuff (for speed), so if you want more info, revert to cm's stock...

swaaye said:
that sounds like possibly defective hardware honestly.... But you say it was fine on other ROMs so I dunno. I have had fewer problems on CM7 than Froyo myself. In fact CM7 has been solid with wifi. I wander around a lot with my NC and use many access points.
Click to expand...
Click to collapse
I hope its no hardware, its over 30 days old, i didnt get the extended warranty and I have a ghost armor on the screen
good to know your wifi is solid w/ cm7 and its not a general cm7 wifi issue. what encryption are you using?

bandroidx said:
I hope its no hardware, its over 30 days old, i didnt get the extended warranty and I have a ghost armor on the screen
good to know your wifi is solid w/ cm7 and its not a general cm7 wifi issue. what encryption are you using?
Click to expand...
Click to collapse
You have 1 year manufacture warranty.

Hello-
Its very unlikely to be Nook issue. I have had this issue with laptops and its always the ISP or the router.
Hope this helps.
Cheers,
mg

I had almost identical symptoms. I disabled encryption on my router and have had zero issues since.
Sent from my NookColor using Tapatalk

the same thing was happening to me and it just seemed to stop one day.. i think it was after nightly 35 or 36
Sent from my NookColor using Tapatalk

Calla969 said:
I had almost identical symptoms. I disabled encryption on my router and have had zero issues since.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Check out my thread on wifi http://forum.xda-developers.com/showthread.php?t=959823&highlight=dummies
My guess is that it's something in the wifi chip driver ir the wifi software stack. I have the identical symptom where on youtube, it stops after a few mb of download. (Note for mine it was stock NC with auto-nooter 3.0.0) The fix for mine was to set the router to 802.11 g only. So try this test:
1. set the router to 802.11 g only
2. turn off encryption
Let us know what happens.

I'm thinking that these devices have varying wifi quality.
My Nook Color is rock solid with wireless, regardless of encryption. WPA2 AES works as well as no encryption. I use my NC regularly with about 5 different access points around town. I'm using Dalingrin's 1100 MHz kernel with CM7 stable.
On the other hand I have a Motorola Droid that barely works unless I either turn off encryption or go to 802.11b! Those Droids were rather notorious for poor wifi. It does the same thing the OP mentioned - it stops transferring after a few megabytes although it says it's still connected. The wireless must be disabled and re-enabled.

It's AES, plain and simple. Turn it off on your router. if you're using WPA2, set it to WPA.
Your problems will go away. Now go to this thread, star it, and add your info please: http://code.google.com/p/cyanogenmod/issues/detail?id=3314

khaytsus said:
It's AES, plain and simple. Turn it off on your router. if you're using WPA2, set it to WPA.
Your problems will go away. Now go to this thread, star it, and add your info please: http://code.google.com/p/cyanogenmod/issues/detail?id=3314
Click to expand...
Click to collapse
Lol I was 99% sure of this. I had the same problem on 2.6.29 kernels on my dx. it magically went away on 2.6.32.
I am using AES, I was going to try to turn it off next, now I know
thanks.
Fattire, thanks, I checked wpa_cli and it just fails to find anything and the scans fail once the issue happens.
The one thing all those routers I tried had in common was AES, its the only thing I really trust. I guess i will have to setup a stub network and seperate AP for the nook color
thanks!

After setting the AP to WPA2/WPA Mode the Nook's wifi is working perfectly under CM7 (except for needing to be restarted after the screen is off when sleep policy is on but i beleive this is a common documented issue)
thanks!
I posted on the cm7 thread and hopefully they will get this fixed asap.

[Q] WiFi occasionally 'killing' routers

Search function is currently unavailable, so apologies if this is a dupe...
Anyways, I'm currently running Rooted Stock 2.3.4 on my N1, and I've noticed that whenever I connect to my friend's DLink router (DIR-655, I think) the Wireless will work for some amount of time, but eventually it will stop working. And not just on my phone, either - the entire router stops working (at least for Wireless requests. Didn't have any wired devices connected to it). Thing is, last time I noticed it, it worked for quite a while - hour or two, maybe - then everything broke about 10 minutes after I received an email... At that point, the router needs to be rebooted, after which it continues working just fine.
The router is using WPA2 encryption, for what it's worth.
I've noticed this with previous versions of Android, so it's not a breaking change introduced with 2.3.4 or anything.
Unfortunately, I don't have an awful lot of Wireless routers to test with, and I haven't yet found an opportunity to test at home, so I'd be hard-pressed to say whether it's a router/D-Link problem, or if it's a device problem...
Has anyone else experienced this? Would flashing a custom ROM (e.g. CM7) fix this? Or would I need a new device? Any thoughts on what else I could do to debug this problem? As I said, this is a rooted device, with an unlocked bootloader and the latest version of Busybox installed.

I'm running 2.3.4 and haven't had this issue with this version or any previous ones.
I've had my phone disconnect from Google Services (the icons turn white instead of green), but the internet stays on and all other devices work just fine.
I have a Netgear router at home and a Linksys one at work and I'm connected to both the whole time I'm at either place.

Hmm... That's interesting.
I've never had Google Services disconnect, but I do have another issue with data randomly turning off. That's not a big deal, as I can just turn it actually off then back on again, and all is good.
Anyone else able to chime in with their experiences?

I have had this happen with cheap, crappy routers. Sometimes upgrading the router to DD-WRT helps, sometimes it doesn't. I had an ASUS this would happen to all the time, and an Airlink that this would happen to occasionally.
This doesn't ever happen to my Linksys WRT610N, and it never happened to an old ZyXEL X550.
I'm going to say, it's just a crappy router.

Thanks. Not really what I was hoping to hear, but that's life.
Did either bad router ever have this issue with other devices? One of the other folks living there has an iPad, and never has this issue, so I'm inclined to say it's at least partly my N1s fault. Also doesn't happen with any of the PCs connected to it.

Yeah, they actually did occasionally have issues with other devices. Hard to narrow it down because I have a ton of Wifi devices. The ASUS also seemed to go down based on time... after so long, it would just stop working properly. The Airlink seemed to get stuck based on demand and range. If I had my phone or laptop at the far end of the house and started using it a lot, it would get stuck. It was as if the router decided it was too much work to pump its signal that far and it would get tired.
Stock ROM on my N1 doesn't seem to allow it, but if you have a custom ROM, you might see if there is any way to set the Wifi to G-only. I had noticed on my old router that G wireless devices seemed less demanding for it.

[Q] Wifi - problems..

Hi,
let me thank you for all the help you may give me.
The problem is i get stuck on obtaining ip address or the cell doesn't even try to connect automatically so i have to manually start the wifi connection to the network after turning on wifi.
The problem of my SGS not connecting automatically is rare, the first is not, it's actually quite often.
I looked through all the guides and sugestions but i couldn't find any permanent solution for this problem.
Note: I've used the AllShare app but sometimes even that doesn't work.
Thank you for all help

The same problem kept happening with me. Some of the fixes which I tried were
Change channel on router - didnt work for me
Use the allshare app first - worked
Set up a static ip in advanced settings - almost always worked
But I have found that I didnt have this problem with other routers, only mine, maybe because of a power problem with the router.
Many of baffling errors are usually caused by bad input power to devices.
Hope it helps

Thanks for the reply, the problem is that i use it alot on my university, where i can't do any changes to their router (or use static IP).
Also the AllShare app is indeed a fix, but only if used every time i think. I'll do some more testing, this problem is really annoying and that's a shame because it complicates the use of most of the smartphone capabilities.
So if anyone else as another solution i would be glad to hear it.
Also i'm on stock rom installed by my operator Vodafone (had the same problem on JPY).
Edit: After a very quick test, it seems that using Allshare once does work, but i had the impression that sometimes it would be needed more than once (even without rebooting). TY for the tip.

Update:
After some more tests i came to the conclusion that at home i need to use AllShare every time i want to connect to my network.
This seems to be a problem affecting several users of SGS, does anyone know the answer to this problem? Or at least an app that minimizes it?
It's quite bad and very frustrating. Thanks, for any and all help.

I had the same problem with stock Android 2.2.1 on 3 phones all Galaxy S. Dropping the packages on voip calling, internet was slow most of the time. I use a linksys wrt54g with dd-wrt, I never had problems with any other devices.
My problem was solved when I installed GingerReal. Also on Miui I didn't had any problems with the wifi connection.
Maybe is just the stock driver incompatibility with some devices.

Thanks for the reply,
I've only had bad experiences with flashing, last time i did everytime right and Odin just hanged, i almost had a serious problem in my hands.
Since this is probably the first and last good phone i'll ever have, i would really like not to kill it (also some people in my family would be very disappointed, it was a gift).
So any workaround? Sorry i'm so insistent but i think that are a lot more people interested in this. TY.

[Q] why does wifi always die in DjangoManoucheX?

Okay guys I've got a constant problem with DMX, not just with this version, but I start to get tired of it. So after a day or two of flashing, wifi starts to stuck at "Obtaining IP address", and does not connect at all after that. As I said it's not only with this version (I'm on 1.6.5), I have also tried different kernels, etc, but it's still the same. I don't want to always reflash, but I'd also stick with this ROM as I really like it. This problem does not come up on CM-based ROMs at all. Thanks for any tips.
Btw I've also tried static/dynamic IP settings, I've changed a router (not because of this), reseted it many times, so not that I didn't try anything at all.

I never had a issue... Have you installed the rom with full wipe?

Of course I did a full wipe, didn't restore any system apps, and as I said it works perfectly for a few days, then bamm! I was playing SongPop, started a game with someone and it stopped when downloading songs.. then I went in wifi options and it showed this IP bug once again. By the way I've just finished reflashing (now without full wipe), and it doesn't even connect now. I really like flashing ROM's etc, but not the same one all over again lol.

Finally I could set static IP on my phone, works now, Thread can be closed. If anybody has the same problem (I've read I'm no the only one), then holla at me!

I'm having a wifi issue from the day i have purchased this phone my wifi always go in the sleep mode don't know why no matter which ROM i use it goes to sleep after the screen is locked or after 5-6 sec of no use of phone.
i'm the only one having this prob i guess.. I thing its an hardware issue, not sure, hope some1 could help me out ^_^
Note: i have kept wifi policy sleep never

Problems with wifi is a kernel issue.
Its adviseable to post which kernel is used

Well I wouldn't be sure, as I was using Kowalski kernel and KoB kernel too, both had the same problem, and only on DjangoManoucheX ROM. But it seems to work now with static IP set.
akash.mahadeshwar has his ROM/kernel stated in his signature, too bad I can't help you.

Lol I don't know if its hardware or software issue but changing rom or kernel dosent fixes it :-/
Sent from P990 the beast phone ^_^

akash.mahadeshwar said:
Lol I don't know if its hardware or software issue but changing rom or kernel dosent fixes it :-/
Sent from P990 the beast phone ^_^
Click to expand...
Click to collapse
have you tried changing your wifi to static ip?
if not, then go into wifi settings and long press/modify the one you cannot connect to. Go to advanced settings and change from DHCP to Static IP. Run Windows commander (just type 'cmd' in the Start Menu search box), and type 'ipconfig /all'. It will show all the informations you need to type to your device's wifi settings. You can give almost any number to the first IP field (when your IP getaway is, for example 192.168.7.1, you only have to change the last number to any you want to, like 192.168.7.155.. but the best way is to get the IP number your device used before wifi got stucked). If you can't see DNS1 and DNS2 in your ipconfig, then you have to go into your router's settings (in browser), that will show them. If you type everything correctly, then Save button won't be greyed out no more, and voila. Wifi works perfectly for me since then. I hope it helps.
Sent from my LG-P990 using xda premium

Changing Wi-Fi to static is far from being a solution; at best it's a workaround.
It's probably related to LG code, used to compile the module loaded by kernel.
I'm not sure if the problem you're reporting us exactly this: I have a brief disconnection/reconnection sometimes when I unlock the phone (Wi-Fi suspends policy sets as never), but this it's not annoying me to much because while sleeping it's connected, and the 2-3s after wake-up is not to much.
Do not say "thanks"; just press it under here.

louiscypherbr said:
Changing Wi-Fi to static is far from being a solution; at best it's a workaround.
It's probably related to LG code, used to compile the module loaded by kernel.
I'm not sure if the problem you're reporting us exactly this: I have a brief disconnection/reconnection sometimes when I unlock the phone (Wi-Fi suspends policy sets as never), but this it's not annoying me to much because while sleeping it's connected, and the 2-3s after wake-up is not to much.
Do not say "thanks"; just press it under here.
Click to expand...
Click to collapse
No, my problem was I could not connect to my wifi AT ALL. Couldn't even do it after a full wipe and reflash, so using a static IP is a solution for me, as it works for 3 days by now. It can be related to the stock ROM's code, as CyanogenMod ROMs don't have this problem for me.

Try flashing KoB kernels again, in mine its wifi work correctly
Sent from my AD683G using xda premium