search

pulse-android-dev / device_huawei_pulse

Device configuration for Huawei U8220/U8230 / T-Mobile Pulse
3 stars 1 forks source link

No WiFi on Android 2.2 #5

Open pandinus opened 14 years ago

pandinus commented 14 years ago

If i enable WIFI it says: "Turning on.." -> "Connecting.." -> "Disconnected" -> "Scanning" and this repeats.

My WIFI is WPA2 personal with AES encoding. I also use staticIP.

I tried it also without a security mode with no success. It's always the same.

jinglemansweep commented 14 years ago

WiFi doesn't work. This also happens with me.

Currently running FLB-Mod v2 alpha 3. I upgraded from FLB-Mod v1.5 and fully wiped (system, data, cache). I even repartitioned and reformatted my SD card.

I flashed the Google Apps immediately after flashing the ROM with no reboot in between.

I am trying to connect to either one of my wireless networks. One is a Linksys WRT54GL (running DD-WRT) and the other is a Linksys WAP54G (running DD-WRT).

Class: 801.11g Encryption: WPA2 Personal Mixed WPA: TKIP+AES MAC Filtering: Enabled

saintVTi commented 14 years ago
<4>[1314, WifiService] [ 6914.938737] Normal WIFI mode. <7>[1314, WifiService] [ 6914.944142] enable_wlan_power: 1.2V voltage level successed <7>[1314, WifiService] [ 6915.024752] enable_wlan_power: wlan chip down successed to pull up <4>[1314, WifiService] [ 6915.106477] set_polling: no need to enable polling for slot 2 <7>[199, kmmcd] [ 6915.187569] mmc1: queuing CIS tuple 0x01 length 3 <7>[199, kmmcd] [ 6915.230710] mmc1: queuing CIS tuple 0x1a length 5 <7>[199, kmmcd] [ 6915.249140] mmc1: queuing CIS tuple 0x1b length 8 <7>[199, kmmcd] [ 6915.252787] mmc1: queuing CIS tuple 0x14 length 0 <7>[199, kmmcd] [ 6915.315595] mmc1: queuing CIS tuple 0x80 length 1 <7>[199, kmmcd] [ 6915.318705] mmc1: queuing CIS tuple 0x81 length 1 <7>[199, kmmcd] [ 6915.321764] mmc1: queuing CIS tuple 0x82 length 1 <6>[199, kmmcd] [ 6915.322809] mmc1: new SDIO card at address 0001 <4>[5035, AR6K startup] [ 6915.350449] update_regCode : 0x4067 <6>[5038, wpa_supplicant] [ 6916.283547] ADDRCONF(NETDEV_UP): eth0: link is not ready <6>[1280, SurfaceFlinger] [ 6920.135945] mdp_get_lcd_line_counter: mdp_lcd_rd_cnt >= mfd->total_lcd_lines error! <6>[5038, wpa_supplicant] [ 6921.249825] ADDRCONF(NETDEV_UP): eth0: link is not ready <4>[1314, WifiService] [ 6931.599010] AR6K: ar6000_cleanup_module ar6000_destroy [0] <6>[1314, WifiService] [ 6933.644113] enable_wlan_power: wlan chip down successed to pull down <7>[1314, WifiService] [ 6933.664425] enable_wlan_power: 1.2V voltage level pull down <4>[1314, WifiService] [ 6933.669825] set_polling: no need to enable polling for slot 2 this is from dmesg
pandinus commented 14 years ago

My Router is also a Linksys WRT54GL. It's running the original firmware (v4.30.11)

flibblesan commented 14 years ago

As updated by pandinus on the forum the issue was caused by his MAC address being different. I'm investigating

flibblesan commented 14 years ago

Ok, seems something is setting a different MAC. hard coded maybe?

flibblesan commented 14 years ago

OK good news is it's not caused by AWEXT. Bad news is I still haven't found the cause.

jinglemansweep commented 14 years ago

I'll change my MAC address filtering on my router when I get home tonight. If this works, I'm happy with this workaround until you find a better solution. Cheers.

saintVTi commented 14 years ago

Same here my mac was changed

pulse-android-dev commented 14 years ago

So all of these problems are from the incorrect MAC address? If so I will change the title of the issue. I have a fix for the MAC issue, I just need to finish writing the code (its almost done), and then add it into the init process.