I've had my SGS4G for about a month now and, until recently, it seemed reliable in connecting to wifi networks, both open and WPA2/PSK. Recently, it has started to not be able to connect when "turning on" the wifi, generally through the pull-down from the status bar, or through WiFi Widget. Going to the Settings > Wireless and network > Wi-Fi settings page shows, when it had failed, "Error" under the "Wi-Fi" heading. Generally, if I try to turn it on from there, it will "try" for a while and usually result in "error" again. Sometimes returning to the home screen (Go Launcher, in my case) and trying again will result in a connection, but not consistently.
Stock kernel, firmware, etc.
Looking at the logs, it appears that the kernel module is not loading. For example
as opposed to a "good" load
Removing WiFi Widget (com.rb.wifiwidget) has not resolved the situation.
Is this something that anyone else has run into?
Amusing update -- For a brief while, I was seeing both the WiFi and 4G emblems in the status bar.
I'm trying removing mirin browser, which has a wifi-state listener (who knows why) and will try killing DriveSmart if the problem persists.
Stock kernel, firmware, etc.
Looking at the logs, it appears that the kernel module is not loading. For example
Code:
V/WifiProgressStore(18818): WifiProgressStore Created
E/WifiHW ( 2482): return of insmod (args:firmware_path=/system/etc/wifi/bcm4329_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=10 dhd_poll=1) : ret = -1, Invalid argument
E/WifiService( 2482): Failed to load Wi-Fi driver.
as opposed to a "good" load
Code:
I/WifiHW ( 2482): [WIFI] Load Driver
I/WifiHW ( 2482): [WiFi.c] insmod() Start!!
I/WifiHW ( 2482): [WiFi.c] start init_module() Start!!
Removing WiFi Widget (com.rb.wifiwidget) has not resolved the situation.
Is this something that anyone else has run into?
Amusing update -- For a brief while, I was seeing both the WiFi and 4G emblems in the status bar.
I'm trying removing mirin browser, which has a wifi-state listener (who knows why) and will try killing DriveSmart if the problem persists.
Last edited: