Database Develop

Suddenly no wifi in cm9 and even cm10 (after reflash)

Touchpad just trying to turn wifi on without any success. I have no idea what happened. touchpad worked well for months and just lost wifi. when I boot to WebOs - wifi is working well. I tried to clean up cm9 and flash cm10 - same result.
output from catlog:
02-18 11:35:07.449 E/WifiStateMachine(350): Failed to reload STA firmware java.lang.IllegalStateException: command '40 softap fwreload wlan0 STA' failed with '400 40 Softap operation failed (No such device)'
02-18 11:35:07.459 E/WifiStateMachine(350): Unable to change interface settings: java.lang.IllegalStateException: command '42 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 42 Failed to set address (No such device)'
02-18 11:35:18.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:19.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:20.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:21.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:22.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:22.479 E/WifiStateMachine(350): Failed to setup control channel, restart supplicant
02-18 11:35:27.499 E/WifiStateMachine(350): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such device)'
02-18 11:35:27.509 E/WifiStateMachine(350): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
02-18 11:35:27.509 E/WifiHW (350): Unable to open connection to supplicant on "wlan0": No such file or directory
02-18 11:35:28.509 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:29.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:30.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:31.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:32.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:32.519 E/WifiStateMachine(350): Failed to setup control channel, restart supplicant
netcfg shows all interfaces down except lo.
wifi country is eu (never checked it before) and I can't change it.

You could try this; maybe it's something similar?

bananagranola said:
You could try this; maybe it's something similar?
Click to expand...
Click to collapse
no link?

Well, that's my first brain fart today. Won't be the last. http://forum.xda-developers.com/showthread.php?t=1813200

Thanks, but not. my wifi just stopped working without any updates etc.

My goodness - wrong device, wrong thread. Like I said, not the last. http://forum.xda-developers.com/showthread.php?t=1937109

No, didn't helped. wifi in webos works without any problems too.
I'm looking at dmesg and found:
board sdio wifi disable
mmc1: card 0001 removed
is it wifi card?

Sorry, then that was the limit of what I can help with. Other than a full wipe and reflash I don't know what else to try. Hopefully someone with more knowledge will show up.

More info from dmesg:
<6>[ 443.108696] CMTP-ATH6KL v4.4
<3>[ 443.108715] board_sdio_wifi_enable
<6>[ 443.114565] wifi_power(1) 1.8V sdio: set load
<6>[ 443.119068] tenderloin_wifi_power: New regulator mode for 8058_s3: 1
<6>[ 443.126264] wifi_power(1) 3.3V
<6>[ 443.126583] wifi_power(1) 8901_l1 3.3V
<6>[ 443.134761] wifi_power(1) 8058_l19 1.8V
<4>[ 443.135074] wifi_power(1) CHIP_PWD
<4>[ 443.498377] mmc1: queuing unknown CIS tuple 0x01 (3 bytes)
<4>[ 443.507770] mmc1: queuing unknown CIS tuple 0x1a (5 bytes)
<4>[ 443.511869] mmc1: queuing unknown CIS tuple 0x1b (8 bytes)
<4>[ 443.518944] mmc1: queuing unknown CIS tuple 0x14 (0 bytes)
<4>[ 443.529203] mmc1: queuing unknown CIS tuple 0x80 (1 bytes)
<4>[ 443.529474] mmc1: queuing unknown CIS tuple 0x81 (1 bytes)
<4>[ 443.541910] mmc1: queuing unknown CIS tuple 0x82 (1 bytes)
<6>[ 443.541961] mmc1: new high speed SDIO card at address 0001
<3>[ 443.598711] ath6kl: bef2fd6c
<3>[ 446.099490] ath6kl: bef2fcfc
<4>[ 446.099507] ath6kl: bef2fcdc
<6>[ 446.114969] ath6kl: bef2fbc4
<6>[ 446.114985] ath6kl: bef2fbc4
<6>[ 446.116982] ath6kl: bef2fbc4
<6>[ 446.119846] ath6kl: bef2fbc4
<6>[ 446.122747] ath6kl: bef2fbc4
<6>[ 446.125644] ath6kl: bef2fbc4
<6>[ 446.128447] ath6kl: bef2fbc4
<6>[ 446.131304] ath6kl: bef2fbc4
<6>[ 446.134207] ath6kl: bef2fbc4
<6>[ 446.137091] ath6kl: bef2fbc4
<6>[ 446.139949] ath6kl: bef2fbc4
<6>[ 446.142802] ath6kl: bef2fbc4
<6>[ 446.145628] ath6kl: bef2fbc4
<6>[ 446.148491] ath6kl: bef2fbc4
<6>[ 446.151356] ath6kl: bef2fbc4
<6>[ 446.154317] ath6kl: bef2fbc4
<6>[ 446.157094] ath6kl: bef2fbc4
<4>[ 446.160235] ath6kl: bef2fc94
<3>[ 446.163154] ath6kl: bef2fe14
<3>[ 446.166015] ath6kl: bef2fe44
<4>[ 446.168669] ath6kl_sdio: probe of mmc1:0001:1 failed with error -5
<6>[ 462.282740] adm_close port_id=0 index 0
<6>[ 478.764935] adm_close port_id=0 index 0
<3>[ 498.557702] board_sdio_wifi_disable
<6>[ 498.564551] tenderloin_wifi_power: New regulator mode for 8058_s3: 1
<6>[ 498.685586] mmc1: card 0001 removed

i dont know what cleanup cm9 + 10 means.. delete things?
uninstall?
nandroid restore and still no-go?
maybe rootzwixi knows..
goodluck

amkaos said:
i dont know what cleanup cm9 + 10 means.. delete things?
uninstall?
nandroid restore and still no-go?
maybe rootzwixi knows..
goodluck
Click to expand...
Click to collapse
format cache, sdcard, config and data from clockworkmod and then acmeuninstall. tried 3 times. Now trying to flash cm9.

this sounds impossible maybe ::
sometimes my router will not broadcast wifi but all things connected thru ethernet work fine.. or one wireless device cannot connect but others do or other connex issues..etc..
if i restart modem + router, everything connex just fine..
you didnt really give any detes about if hptp only fails on your network etc..
if you do uninstall then acme3 correctly, there is no way that HPTP wont connect to your network... unless you share some obscure hardware fubar that i never heard of..
GL
i hope you post what the outcome is and how you resolved prob.
your experience will help out someone in future time
btw, i dont wanna rub it in but when you get things going, make a nandroid backup .. make more as you tweak out your tab and safely delete prior backups... saved me many headaches..
GL
EDIT:: i see that you do connect w/ webos.. still its easy to restart router + modem..

So, new wifi driver in the new cm10 build - still no success. It's only internet browser with webos ;(

Epic 4g same thing
crea7or said:
So, new wifi driver in the new cm10 build - still no success. It's only internet browser with webos ;(
Click to expand...
Click to collapse
CM10 for 4 months no wifi issues. Suddenly the other morning wifi won't turn on. Boot to a stock image it is fine. Did you ever find a solution?

RichMichPA said:
CM10 for 4 months no wifi issues. Suddenly the other morning wifi won't turn on. Boot to a stock image it is fine. Did you ever find a solution?
Click to expand...
Click to collapse
stock image?

Multiboot utility
crea7or said:
stock image?
Click to expand...
Click to collapse
I use multi boot which lets you reboot into fc09 to add MSL etc. I just tried 9.1 ics and wifi is working.

Exactly the same problem
As yet, no fix in sight.
Wifi in WebOS is solid. I have managed to spontaneously connect a couple of times after several hours, sometimes days. I've tried reflashing several roms/updates, reformating, clearing cache and dalvik, resetting permissions. Nothing.
As long as I do not reboot, once connected the wifi is solid. My catlog shows exactly the same problems as OPs.
It may be a coincidence, but my problems seemed to begin after switching to airplane mode on a recent trip. Since then I've only managed to get the wifi up 3 times.
In settings under wifi it just says "connecting to wifi" regardless of whether the wifi button is set to "ON" or "OFF"
What bothers me, is the "not found" errors in logcat.
I'm out of ideas. If anyone can suggest a way to nail down the issue, I'm all ears. Thanks in advance!
Code:
07-24 11:37:27.209 E/WifiStateMachine(242): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
07-24 11:37:27.209 W/CommandListener(156): Failed to retrieve HW addr for wlan0 (No such device)
07-24 11:37:27.209 D/CommandListener(156): Setting iface cfg
07-24 11:37:27.209 D/NetworkManagementService(242): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
07-24 11:37:27.209 D/NetworkManagementService(242): flags <[down]>
07-24 11:37:27.219 E/WifiStateMachine(242): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
07-24 11:37:27.389 I/wpa_supplicant(6737): rfkill: Cannot open RFKILL control device
07-24 11:37:27.389 E/wpa_supplicant(6737): Could not read interface wlan0 flags: No such device

I'm having the same issue. WiFi works solid on webOs just when I boot into android and try to turn WiFi on, it stays stuck saying “turning on wifi" on cm9 any build and cm10 any build. I uninstalled everything at least 20 times wiped my TP clean on android and webOs(basically factory reset) wiped the cache wiped the delvik cache turned off turn on reinstall android also downloaded WiFi fixer apk and that doesn't help at all either. Everything on webOs works WiFi internet works great. Just when I go into android it stays stuck at turning on WiFi and when I reinstall cm9 or cm10 open up settings this is the only time I can switch the setting to turning on WiFi but everything is in gray with no luck just stuck saying turning on WiFi. Any help would be much appreciated! I hate webOs android is way better!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[email protected] said:
I'm having the same issue. WiFi works solid on webOs just when I boot into android and try to turn WiFi on, it stays stuck saying “turning on wifi" on cm9 any build and cm10 any build. I uninstalled everything at least 20 times wiped my TP clean on android and webOs(basically factory reset) wiped the cache wiped the delvik cache turned off turn on reinstall android also downloaded WiFi fixer apk and that doesn't help at all either. Everything on webOs works WiFi internet works great. Just when I go into android it stays stuck at turning on WiFi and when I reinstall cm9 or cm10 open up settings this is the only time I can switch the setting to turning on WiFi but everything is in gray with no luck just stuck saying turning on WiFi. Any help would be much appreciated! I hate webOs android is way better!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[email protected] said:
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
did u try doctore your TP?

[KERNEL] [WIP] Custom Kernel Project

Intro
I wanted to make a thread to document kernel development activities that we're doing. So far, this Ouya forum has been a great place to view what it takes to start developing for a new device!
First of all, alsutton over on GitHub posted the kernel source. It can be found here https://github.com/ouya/ouya_1_1-kernel.
XDA University has some great articles to get started:
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source
http://xda-university.com/as-a-developer/adding-features-to-your-kernel
Things noticed about the stock kernel so far:
-it's cpu governor seems to be permanently set to "performance" (1600Mhz all the time). There might be a way to override this, but in the voltage control app, I wasn't able to change anything (frequency or governor)
Wish List:
-Access to set more governors (could help the Ouya's fan stay off during menu surfing)
-Overclocking (we have a fan...let's break 2Ghz because we need moar hertz. Might help speed up some emulators)
Need more info:
-If we ever overlock, we need a way to view temperature to make sure we're not frying our Ouyas. Just a guess, but it's probably a file we can read from in /dev or /proc
-Just a blind guess after reading the XDA University article on adding overclocking, but SOURCE/arch/arm/mach-tegra/tegra3_clocks.c might be a place to look. It seems to have clock frequency tables. Other devs that have made tegra 3 kernels might know the appropriate files to edit

boot.img details
As an FYI,
for most android devices, the kernel resides in it's own partition on the device. When flashing a new kernel, a new boot.img is flashed to the partition. The boot.img file includes a header, the kernel image (pre-compiled), and the ramdisk. On boot, the kernel takes control and uses the ramdisk files to get things started. The rest of the partitions (including system, data, cache) are mounted and the Android OS is booted (from system).
Here's one way to take a boot.img and dissect it in order to view the ramdisk contents.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Here's another way as well (thanks, professorpoptarts)
http://forum.xda-developers.com/showthread.php?t=1890912

May I suggest not to try to overclock past known safe values of 1.9ghz?
As for the kernel....it is not set to be at 1.6ghz all the time... its set differently and actually stays and floats at 1ghz until utilization kicks in at to 1.6ghz
You wont be able to change any of these values until you compile your own kernel with the correct voltage/clock settings in place.
-----edit------
To add to that in respects to the 1-1.6ghz range it actually only utilizes those 2 cpu states ( from what I've recorded )

HTCdemon said:
May I suggest not to try to overclock past known safe values of 1.9ghz?
As for the kernel....it is not set to be at 1.6ghz all the time... its set differently and actually stays and floats at 1ghz until utilization kicks in at to 1.6ghz
You wont be able to change any of these values until you compile your own kernel with the correct voltage/clock settings in place.
-----edit------
To add to that in respects to the 1-1.6ghz range it actually only utilizes those 2 cpu states ( from what I've recorded )
Click to expand...
Click to collapse
What are you using to record? I have been using "system panel".
Sent from my SCH-I535 using xda premium

just fyi, I was looking at the init.rc for the 264 OTA, just in case a rom gets flashed that didn't remove this we could always disable the recovery flash at the boot level.
service flash_recovery /system/etc/install-recovery.sh
class main
oneshot

for any other aspiring kernel devs out there:
https://github.com/invisiblek/AnyKernel/tree/ouya
(fyi: this is on the branch named ouya of that repo, make your you add: -b ouya to your git clone or you'll get the branch for a different device)
just throw your zImage in kernel/ and your modules in modules/
make sure when you compile your kernel, you add -fno-pic to your KBUILD_CFLAGS_MODULE in Makefile in the root of your kernel source
otherwise it wont load the modules
wewt!

Just curious.....is anyone else having issues compiling the latest commit?
I reverted back to the previous commit but it still breaks.
Build machine hasnt changed.
Code:
drivers/dma/timb_dma.c: In function 'td_tx_status':
drivers/dma/timb_dma.c:521: error: 'last_complete' undeclared (first use in this function)
drivers/dma/timb_dma.c:521: error: (Each undeclared identifier is reported only once
drivers/dma/timb_dma.c:521: error: for each function it appears in.)
drivers/dma/timb_dma.c:521: error: 'last_used' undeclared (first use in this function)
drivers/dma/timb_dma.c:513: warning: unused variable 'td_chan'
make[2]: *** [drivers/dma/timb_dma.o] Error 1
make[1]: *** [drivers/dma] Error 2
make: *** [drivers] Error 2

HTCdemon said:
Just curious.....is anyone else having issues compiling the latest commit?
I reverted back to the previous commit but it still breaks.
Build machine hasnt changed.
Code:
drivers/dma/timb_dma.c: In function 'td_tx_status':
drivers/dma/timb_dma.c:521: error: 'last_complete' undeclared (first use in this function)
drivers/dma/timb_dma.c:521: error: (Each undeclared identifier is reported only once
drivers/dma/timb_dma.c:521: error: for each function it appears in.)
drivers/dma/timb_dma.c:521: error: 'last_used' undeclared (first use in this function)
drivers/dma/timb_dma.c:513: warning: unused variable 'td_chan'
make[2]: *** [drivers/dma/timb_dma.o] Error 1
make[1]: *** [drivers/dma] Error 2
make: *** [drivers] Error 2
Click to expand...
Click to collapse
Fine here
Now if I just had a working Ouya....we could make some cool stuff =P

Back with a new problem...
Code:
06-29 18:41:21.260: D/WifiService(322): setWifiEnabled: true pid=584, uid=10018
06-29 18:41:21.270: E/WifiHW(107): Failed to open wlan fw path param (No such file or directory)
06-29 18:41:21.270: E/SoftapController(107): Softap fwReload - failed: -1
06-29 18:41:21.270: E/WifiStateMachine(322): Failed to reload STA firmware java.lang.IllegalStateException: command '9 softap fwreload wlan0 STA' failed with '400 9 Softap operation failed (No such file or directory)'
06-29 18:41:21.270: W/CommandListener(107): Failed to retrieve HW addr for wlan0 (No such device)
06-29 18:41:21.270: D/CommandListener(107): Setting iface cfg
06-29 18:41:21.270: E/WifiStateMachine(322): Unable to change interface settings: java.lang.IllegalStateException: command '11 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 11 Failed to set address (No such device)'
06-29 18:41:21.280: V/WifiSetupActivity(584): Setting content visible: true
06-29 18:41:21.280: E/wpa_supplicant(986): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
06-29 18:41:21.280: E/wpa_supplicant(986): Failed to initialize driver 'nl80211'
06-29 18:41:21.280: E/wpa_supplicant(986): wlan0: Unsupported driver 'nl80211'
06-29 18:41:21.370: E/WifiStateMachine(322): Failed to start supplicant!
Anyone else having issues with this?
edit:
Looks like it's not loading any modules at all... I had no problems previously with older kernels till 328....anyone know what im missing?

My main issue here, and something I'd like to see done.
The Ouya seems to get hot sometimes during long durations of gameplay, could we put together a method on getting the fan boosting cool air through the device once it gets hot? Or would that be something hardware related as the Ouya can't say; "I'm hot, pour some water on me"?
If this was useful to you, I can only ask of a favor!
Check out my YouTube channel!
http://WWW.YouTube.com/user/TheDarkRosary
Subscribe if you will!

HTCdemon said:
Back with a new problem...
Code:
06-29 18:41:21.260: D/WifiService(322): setWifiEnabled: true pid=584, uid=10018
06-29 18:41:21.270: E/WifiHW(107): Failed to open wlan fw path param (No such file or directory)
06-29 18:41:21.270: E/SoftapController(107): Softap fwReload - failed: -1
06-29 18:41:21.270: E/WifiStateMachine(322): Failed to reload STA firmware java.lang.IllegalStateException: command '9 softap fwreload wlan0 STA' failed with '400 9 Softap operation failed (No such file or directory)'
06-29 18:41:21.270: W/CommandListener(107): Failed to retrieve HW addr for wlan0 (No such device)
06-29 18:41:21.270: D/CommandListener(107): Setting iface cfg
06-29 18:41:21.270: E/WifiStateMachine(322): Unable to change interface settings: java.lang.IllegalStateException: command '11 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 11 Failed to set address (No such device)'
06-29 18:41:21.280: V/WifiSetupActivity(584): Setting content visible: true
06-29 18:41:21.280: E/wpa_supplicant(986): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
06-29 18:41:21.280: E/wpa_supplicant(986): Failed to initialize driver 'nl80211'
06-29 18:41:21.280: E/wpa_supplicant(986): wlan0: Unsupported driver 'nl80211'
06-29 18:41:21.370: E/WifiStateMachine(322): Failed to start supplicant!
Anyone else having issues with this?
edit:
Looks like it's not loading any modules at all... I had no problems previously with older kernels till 328....anyone know what im missing?
Click to expand...
Click to collapse
Im getting the exact same problems on a stock OUYA bougth today
lsmod on the adb shell shows the following :
[email protected]:/ $ lsmod
lsmod
cfg80211 179175 0 - Live 0x00000000
inv_mpu_ak8975 3937 0 - Live 0x00000000
inv_mpu_kxtf9 6865 0 - Live 0x00000000
mpu3050 36222 2 inv_mpu_ak8975,inv_mpu_kxtf9, Live 0x00000000
Click to expand...
Click to collapse

I wish i had an Ouya.... i would be all over this

Ouya-XD said:
My main issue here, and something I'd like to see done.
The Ouya seems to get hot sometimes during long durations of gameplay, could we put together a method on getting the fan boosting cool air through the device once it gets hot? Or would that be something hardware related as the Ouya can't say; "I'm hot, pour some water on me"?
If this was useful to you, I can only ask of a favor!
Check out my YouTube channel!
http://WWW.YouTube.com/user/TheDarkRosary
Subscribe if you will!
Click to expand...
Click to collapse
sure through some code already published there are multiple ways to impliment thermal throttling
although that could impact game play
im sure there are also ways to open the unit and have it trigger a fan
im sure you also could make custom heatsink for the unit for those hardcore Overclockers
you wanna look in
tegra3_clocks.c
tegra3_dvfs.c
tegra3_thermal.c
tegra3_throttle.c
cpu-tegra3.c
and a few others
you can improve the GPU clocks and add governors easily as well as change between slab/slub/slob/slqb
this would be something really fun to play with ill try to save up for an ouya

Is this project still active? I would love to contribute in any way possible to an overclocked kernel, but I have never done any kernel development before.

BUS DR1V3R said:
Is this project still active? I would love to contribute in any way possible to an overclocked kernel, but I have never done any kernel development before.
Click to expand...
Click to collapse
I'm waiting till I can afford an ouya then I can code up some stuff
Sent from my SCH-R970 using xda premium

mybook4 said:
Things noticed about the stock kernel so far:
-it's cpu governor seems to be permanently set to "performance" (1600Mhz all the time). There might be a way to override this, but in the voltage control app, I wasn't able to change anything (frequency or governor)
Click to expand...
Click to collapse
Just for reference, I have two Ouya's. One came clocked (retail version) at 1.6, the other came (Kickstarter) clocked at 1.7.

[Q] Can't get WiFi to work on CM 10.1.3

Hi everyone! I'm new to custom roms and got thrilled with how CM's pervormance is better that LG's original rom, but since I flashed it I can´t use wifi :crying:
I ain´t even able to turn wifi on or of... As I work developing andoid apps, I've noticed the error log below at logcat... seems like the wifi drivers are missing... is it correct? how am I supposed to fix that?
Thanks you all in andvance for any help/suggestions!
Code:
10-30 09:31:30.726: ERROR/WifiStateMachine(477): Failed 6 times to start supplicant, unload driver
10-30 09:31:30.756: ERROR/WifiStateMachine(477): Unable to change interface settings: java.lang.IllegalStateException: command '5479 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 5479 Failed to set address (No such device)'
10-30 09:31:30.786: ERROR/wpa_supplicant(4967): nl80211: Could not configure driver to use managed mode
10-30 09:31:30.796: ERROR/wpa_supplicant(4967): Could not read interface wlan0 flags: No such device
10-30 09:31:30.796: ERROR/wpa_supplicant(4967): wlan0: Failed to initialize driver interface
10-30 09:31:39.336: ERROR/gralloc(146): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
10-30 09:31:41.796: ERROR/WifiHW(477): Supplicant not running, cannot connect
10-30 09:31:42.806: ERROR/WifiHW(477): Supplicant not running, cannot connect
10-30 09:31:43.806: ERROR/WifiHW(477): Supplicant not running, cannot connect
10-30 09:31:44.806: ERROR/WifiHW(477): Supplicant not running, cannot connect
10-30 09:31:45.806: ERROR/WifiHW(477): Supplicant not running, cannot connect
10-30 09:31:45.826: ERROR/WifiStateMachine(477): Failed to setup control channel, restart supplicant
10-30 09:31:45.876: ERROR/WifiStateMachine(477): Unable to change interface settings: java.lang.IllegalStateException: command '5482 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 5482 Failed to set address (No such device)'
10-30 09:31:45.906: ERROR/wpa_supplicant(5004): nl80211: Could not configure driver to use managed mode
10-30 09:31:45.906: ERROR/wpa_supplicant(5004): Could not read interface wlan0 flags: No such device
10-30 09:31:45.906: ERROR/wpa_supplicant(5004): wlan0: Failed to initialize driver interface
bonus:
Code:
10-31 14:47:38.139: ERROR/(25264): file /data/data/com.nvidia.NvCPLSvc/files/driverlist.txt: not found!

Check 'netcfg' output and also kmesg at boot. CM has the Wi-Fi driver built into the kernel and it's loaded when the system starts.

Nexus 5 (hammerhead) - Tethering broken?

Hi,
Since about 4.4.3 (possibly 4.4.2?) wifi-tethering broke.
logcat says:
Code:
D/AFWall ( 3615): OS reported AP state change: 11 -> 12
D/AFWall ( 3615): isWifiApEnabled is false
E/SoftapController( 1320): Cannot update "/data/misc/wifi/hostapd.conf": Permission denied
E/WifiStateMachine( 1837): Exception in softap start java.lang.IllegalStateException: command '79 softap set wlan0 AndroidAP broadcast 6 wpa2-psk [scrubbed]' failed with '400 79 SoftAP command has failed'
E/SoftapController( 1320): SoftAP is not running
D/SoftapController( 1320): Softap fwReload - Ok
D/SoftapController( 1320): Softap fwReload - Ok
D/dalvikvm( 3615): GC_CONCURRENT freed 390K, 11% free 12321K/13772K, paused 4ms+1ms, total 18ms
I/AFWall ( 3615): Now assuming 3G connection (non-tethered)
E/SoftapController( 1320): Cannot update "/data/misc/wifi/hostapd.conf": Permission denied
E/WifiStateMachine( 1837): Exception in softap re-start java.lang.IllegalStateException: command '83 softap set wlan0 AndroidAP broadcast 6 wpa2-psk [scrubbed]' failed with '400 83 SoftAP command has failed'
D/AFWall ( 3615): OS reported AP state change: 12 -> 14
D/AFWall ( 3615): isWifiApEnabled is false
This bug is reported on code.google.com but the only suggested solution is deleting /data/misc/wifi and reboot which didn't work for me.
I even chmoded 777 /data/misc/wifi and hostapd.conf but without any success.
I'm running a very recent nightly (a few days old).
Any thoughts?
Thank you.

Continuous spamming of logcat while device is sleeping

So I just noticed via Android Studio monitor while testing an app under development during device sleep, that it is continuously and at a good rate*, spamming the logcat log with:
10-21 15:59:43.543 239-239/? E/ccci_fsd(1): Failed to read from FS device (-1) !! errno = 4
I've felt that the battery use during sleep since buying it hasn't been all that great. Perhaps that's why with it continually spending the cpu on this.
This is with the latest official OS version for the Blu R1 with Amazon ads.
*Counted 16 lines in 5 seconds
Search turned up nothing. Device appears to work fine.
Factory reset does nothing as suspected. However, currently it looks to only show up when on battery power (I use wifi ADB and found this problem with device in discharge state during sleep) - it should show with a logcat reader app I suspect.
Eg (discharge)
10-21 14:20:38.236 854-919/? E/native: do suspend true
10-21 14:20:39.448 238-238/? E/ccci_fsd(1): Failed to read from FS device (-1) !! errno = 4
10-21 14:20:39.691 238-238/? E/ccci_fsd(1): Failed to read from FS device (-1) !! errno = 4
10-21 14:20:39.932 238-238/? E/ccci_fsd(1): Failed to read from FS device (-1) !! errno = 4
...
Eg (charge)
10-21 14:21:41.685 854-919/? E/native: do suspend true
10-21 14:23:29.666 1781-1871/? E/MPlugin: Unsupported class:
Anyone have any thoughts?

Nevermind, mystery solved. Found out airplane mode with wifi enabled fixes it.
Looks like it could be from not having a sim card.

Thread closed at the request of the OP.