Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

about wifi fails #5

Open
sammao opened this issue Jun 1, 2011 · 6 comments
Open

about wifi fails #5

sammao opened this issue Jun 1, 2011 · 6 comments

Comments

@sammao
Copy link

sammao commented Jun 1, 2011

my tab had flash 0530 rom,modem use JK5.
2 days normal use,it fails to connect wifi.
it can work before.
how strange!

@techomancer
Copy link
Collaborator

Does it authenticate? Can it obtain IP address? Is there anything in logcat?

@sammao
Copy link
Author

sammao commented Jun 2, 2011

It always has been show connecting,then disconnect directly.Repeatedly!
Sometime it can't find any signal.
didn't have any logcat.

ps:this rom flash in HK TAB use JK5 signal very bad!

@cm7sgt
Copy link
Owner

cm7sgt commented Jun 3, 2011

Does the time on your tab match the time on your router? I think the tab gets 1 hour DHCP leases so if the time is off by more than hour getting IP address from the accesspoint may be broken.

@nunocodex
Copy link

In the samsung rom when tab found wireless ap open a popup with wireless found.. is possible to porting in cyanogenmod?

@cm7sgt
Copy link
Owner

cm7sgt commented Jun 6, 2011

Everything is possible, but we are here to port CyanogenMod to Galaxy Tab, not to change CyanogenMod itself. If you have ideas about how CM should work, please talk to Cyanogen&Co.

@pearson
Copy link

pearson commented Oct 21, 2011

I've had something similar happen with my Galaxy Tab. I'm new (4 days) to this firmware (well done, btw, and thank you!), but I've already had a period of time when it would not connect to any WiFi. Rebooting, etc, etc, didn't seem to help. I deleted all the stored access points (there were only two), recreated one, and then it was working again.

I realize that's not the most useful bug report, but I think there's more to the problem than that since I've seen quite a few issues with the Galaxy Tab's WiFi. For example, with the JMQ (2.3.3) firmware, the Galaxy Tab would hang while scanning access points, and this leads to it not finding APs and not automatically connecting to them. This was seen on several Galaxy Tab units. To fix this we would replace the wpa_supplicant file with one built for allowing ad hoc networking. As well, the JMQ firmware would only return new access point scan information on every second scan. It would appear to take around 7s to do a scan, but in reality it was taking closer to 14s due to this problem. (Note that this CyanogenMod firmware is still slow at access point scanning but it does return new data on every scan.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants