I've had CM7 running on my TouchPad for quite some time now, and all of sudden, after rebooting it, it will no longer complete the boot process. Keeps hanging on the boot animation.
I rebooted to recovery and wiped system, cache and dalvik and reflashed CM7 and Google Apps. Keeps hanging at the exact same place:
There is no more logging entries generated after this:
W/BluetoothHeadset( 249): Proxy not attached to service
W/BluetoothHeadset( 249): Proxy not attached to service
E/wpa_supplicant( 453): wpa_driver_priv_driver_cmd failed (-1): GETPOWER
D/WifiStateTracker( 249): DHCP request started
I/bluedroid( 249): Starting bluetoothd deamon
D/WifiStateTracker( 249): DHCP succeeded with lease: 86400
V/WifiStateTracker( 249): IP configuration: ipaddr 192.168.1.123 gateway 192.168.1.1 netmask 255.255.255.0 dns1 192.168
.1.1 dns2 0.0.0.0 DHCP server 192.168.1.1 lease 86400 seconds
E/BluetoothEventLoop.cpp( 249): event_filter: Received signal org.freedesktop.DBus:NameAcquired from /org/freedesktop/D
Bus
D/BluetoothHidService.cpp( 249): hid_event_filter...
D/BluetoothService( 249): found 3 bonded devices
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
D/BluetoothService( 249): Bluetooth state 11 -> 12
Anyone have any idea how I can resolve this? How do I turn off bluetooth via ADB?
Obviously, wiping data will resolve the issue, but I would rather not do that (although I do have all of my apps backed up via TB)
Turge said:
I've had CM7 running on my TouchPad for quite some time now, and all of sudden, after rebooting it, it will no longer complete the boot process. Keeps hanging on the boot animation.
I rebooted to recovery and wiped system, cache and dalvik and reflashed CM7 and Google Apps. Keeps hanging at the exact same place:
There is no more logging entries generated after this:
W/BluetoothHeadset( 249): Proxy not attached to service
W/BluetoothHeadset( 249): Proxy not attached to service
E/wpa_supplicant( 453): wpa_driver_priv_driver_cmd failed (-1): GETPOWER
D/WifiStateTracker( 249): DHCP request started
I/bluedroid( 249): Starting bluetoothd deamon
D/WifiStateTracker( 249): DHCP succeeded with lease: 86400
V/WifiStateTracker( 249): IP configuration: ipaddr 192.168.1.123 gateway 192.168.1.1 netmask 255.255.255.0 dns1 192.168
.1.1 dns2 0.0.0.0 DHCP server 192.168.1.1 lease 86400 seconds
E/BluetoothEventLoop.cpp( 249): event_filter: Received signal org.freedesktop.DBus:NameAcquired from /org/freedesktop/D
Bus
D/BluetoothHidService.cpp( 249): hid_event_filter...
D/BluetoothService( 249): found 3 bonded devices
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
D/BluetoothService( 249): Bluetooth state 11 -> 12
Anyone have any idea how I can resolve this? How do I turn off bluetooth via ADB?
Obviously, wiping data will resolve the issue, but I would rather not do that (although I do have all of my apps backed up via TB)
Click to expand...
Click to collapse
Yep, you need to do a full wipe and reflash. Happened to me and its annoying, but im trying to minimize the number of apps i install and am currently staying away from restoring apps from TiBu. Havnt had a problem for the last few days...
jackdonogy said:
Yep, you need to do a full wipe and reflash. Happened to me and its annoying, but im trying to minimize the number of apps i install and am currently staying away from restoring apps from TiBu. Havnt had a problem for the last few days...
Click to expand...
Click to collapse
Do you know if it was the same problem? Were you able to take a look at logcat?
Related
Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
h2o pete said:
Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem on a ROM i have made... That's just for Tattoo not Desire... But it's the same logcat... So can somebody help us??
Yeah I'm pretty stuck on what to do :/.
Added some information about my software to the first post.
i have same problem on my htc dream
BUMP...
-------------------------------------
Sent from my übercharged HTC Tattoo
Fixed it by setting a static IP address.
Wi-Fi > Menu Button > Advanced > Use static IP
i had yesterday the same problem on my desire,
i fixxed this with flash a "older" stock rom and update it with the build-in updater....
same problem with my desire. how to fix it?
It's broke again. Setting a static IP doesn't fix it any more. Any ideas?
got the same problem here
can any one help???
Bump
Sent from my HTC Desire using XDA App
seems like wlan.ko is not available in /system/lib/modules/
I've had similar problems in the past, but was unable to solve them. You can check several things though.
1) wlan.ko in /system/lib.modules <-- has to match up with the kernel that you are using
2) any entries for wifi and/or dhcp in the init.rc and init.devicenamehere.rc files that are in the ramdisk in the boot.img
3) wifi settings in the build.prop
4) files in /system/etc/wifi
5) I'm not sure about this one, but even some of the files in /system/etc/firmware might have something to do with wifi.
6) files in /system/etc/dhcpd
7) any files in /system/bin and/or /system/xbin that are called by *.rc from #2.
Just take a working ROM (stock is usually what I use), and compare the files with the corresponding files in your build. I use either WinMerge or N-way Folder Compare or just plain old 'diff' in Linux.
I had the same issue.
Flashed a new ROM with full wipe etc. Wifi OK.
Flashed a kernel update on top of the ROM. Wifi broken. Turning wifi on it would error and turn off again.
The only way I could fix it was to flash a full ROM and make sure I wiped everything from the recovery.
Any more info you can provide? Current ROM +version +any other mods applied like status bar or OC kernels?
Did anyone fix this?? I am stuck here, G1 Dream
CM 5.0.8 DS
Please help!!!
Are you getting the same error in logcat as others have? If so, I think .mak fixed it, but he never let us know how.
Same Issues...
Ive tried Reverting to CM 5.07, 5.07 and now the beta 6.0 and all have yet to fix the wifi issue. I also tried switching between the radio's and doing a full format/partition and wipe. Any fix to this yet?
That was Lovely Bro...Really Useful...I got my DESIRE today and could connect to WIFI but was unable to browse...This tip helped me...Thx a lot... Keep up the good work..
Trying to replace bcm4329.ko
I did the OTA update for my Desire today, and of course have the wi-fi problem.
However, when I enable wi-fi, I see the following appear at the end of dmesg:
Code:
<3>[ 8197.511535] bcm4329: version magic '2.6.32.15-g6a358a9 preempt mod_unload
ARMv7 ' should be '2.6.32.15-gf9c0527 preempt mod_unload ARMv7 '
The update zip (via thread 778852) contains a bsdiff patch file patch/system/lib/modules/bcm4329.ko.p... and from some examination of that file it appears just to patch the vermagic field of the .ko file.
I tried to use a hex editor to 'fix' bcm4329 and used adb pull/push to replace it, but I get
Code:
failed to copy 'bcm4329.ko.fix' to '/system/lib/modules/bcm4329.ko': Read-only
file system
Can anyone help me with this?
Update: I am a fool. I was using the wrong goldcard! Once I put the right goldcard in, then sdcard:update.zip applied correctly and wi-fi started working again.
@dleonard, could you please make step by step instructions of how to fix this wifi issue?
thanks
Mixu
Hi all,
I have a t-mobile phone and tried to install android 2.2. there. I used mdeejay's and darkStone's builds, but wifi didn't work at any of them. I've found a person who uses T-mobile hd2 too and installed the same versions of rom and radio. It didn't helped. In windows mobile wifi works well.
Could you please advice how to hande it? Did anyone face the same problem?
Thank you in advance.
#did some debug via adb:
I suppose that the red line below tells about reason.. But I haven't dealt with WPA on android before.. Any help is appreciated.
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
I/WifiHW ( 1916): wifi_load_driver enter
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
I/WifiHW ( 1916): wifi_load_driver end right 3
I/WifiHW ( 1916): wifi_start_supplicant enter
I/WifiHW ( 1916): wifi_start_supplicant end right 2
D/WifiService( 1916): ACTION_BATTERY_CHANGED pluggedType: 2
I/wpa_supplicant( 2771): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00
:00:00
E/wpa_supplicant( 2771): Failed to disable WPA in the driver.
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/PowerManagerService( 1916): New lightsensor value:40, lcdValue:90
D/lights ( 1916): set_light_buttons
D/lights ( 1916): set_light_keyboard
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x6257a8), index=0, pid=2298,
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x4ca268), index=0, pid=2298
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
V/WifiStateTracker( 1916): Supplicant died unexpectedly
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/WifiStateTracker( 1916): Disabling interface
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/WifiStateTracker( 1916): Disabling interface
I/WifiHW ( 1916): wifi_stop_supplicant enter
I/WifiHW ( 1916): wifi_stop_supplicant end right 1
I/WifiHW ( 1916): wifi_unload_driver enter
I/WifiHW ( 1916): wifi_unload_driver end right 2
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
how to set up MAC address for android builds (except startup.txt)?
Hi again,
I did some search and found that the core of the problem is in getting MAC address for wifi. (as dmsg says). Exactly the same problem was for Touch2, Tilt and other devices (http://forum.xda-developers.com/showthread.php?p=9211659) and it was resolved after they corrected wifi-nvram.txt. This file is responsible for setting up MAC address there, but I couldn't find it at builds for hd2.
if anybody knows what file is used to set up MAC address for wifi, I would be very appreciated.
Thanks!
I believe they just checked for their WiFi mac address from one of the following locations:
Settings->About phone->Status
Wireless & Networks -> WiFi Settings -> Menu Button -> Advanced
Then they edited the nvram.txt file @ /system/lib/hw/wifi/nvram.txt to include the proper MAC address.
Thanks for the answer!
Unfortunatelly wireless settings are not available until wifi is turned on.
I investigated the problem deeper and found that the reason could be in wifi hardware initialization. I did dmesg and saw the following:
wlan: wifi_set_power = 1
htcleo_wifi_power: 1
wlan: wifi_set_carddetect = 1
htcleo_wifi_set_carddetect: 1
mmc0: card_present 1
mmc0: Slot status change detected (0 -> 1)
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
Since in windows mobile wifi does work I used the firmware files from WM: nvram.txt and rtecdc1.bin. As it turned out nvram in android is located in /proc/calibraion. But unfortunatelly it didn't help. So, I think that the problem is in bcm4329.ko driver. I'm not sure why other people with the same hd2 (t-mobile US) and the same ROM/RADIO/Android have no such issue. Perhaps my broadcomm hardware has a problem which is bypassed in windows, but not in Android.
I wonder if there is a way to get more detailed info than dmesg and logcat give (except building andoid sources of course ).
I don't know if it can help, but still, I'll say it anyway.
I think i had the same problem some times ago.
Wifi in android wouln't work, but was perfectly working in winmo.
it seems that if wifi is on in winmo when you boot on android, the wifi device seems to be blocked in some way.
Do you have wifi enabled in winmo? if yes, try to disable it, and boot on android to see if it works.
Hi kushulain,
Thanks for the advice! (I've almost started to build andriod by myself to find out the reason..) Unfortunatelly wifi was turned off when android was booting.
But this is another point to play around. I haven't tried to boot andriod with wifi turned on.
Thanks!
Just tried to boot andriod with wifi turned on. The device hangs at the beginning of the booting (even before screen with 'htc' appears). I think it is connected to my problem.
Did someone have similar problems?
Hey, I have the same problem, did you find any solution ?
Guys have you tried to change the radio part of the phone with a suitable one?
canavaro said:
Hey, I have the same problem, did you find any solution ?
Click to expand...
Click to collapse
hi, I didn't fix it actually due to lack of time. I tried to use wm hw init files in Android, but it didn't help. There is a score of my posts on this forum regarding this topic so you can find exactly what I tried. The funny thing is that WiFi works in wp7.
To stealth21
yes, that was the first thing I tried.
Hello, there.
I installed void #e a while ago on my O1, everything went smoothly until I had to setup a VPN with L2TP/IPsec.
After poking around with adb logcat, I found that the bundled kernel (mik_os's one) missed support for NETKEY sockets, IPSec over IPv4 and PPP altogether, so I rebuilt the kernel from source adding all missing options to .config.
I flashed the new kernel, boot it and tried to start the VPN, but it failed again.
This time - however - racoon was able to set up an IPsec security association with the remote host, but pppd complained about missing PPP support in kernel:
Code:
I/racoon ( 4330): ISAKMP-SA established <scrubbed>[500]-<scrubbed>[500] spi:<scrubbed>
I/racoon ( 4330): initiate new phase 2 negotiation: <scrubbed>[500]<=><scrubbed>[500]
I/racoon ( 4330): IPsec-SA established: ESP/Transport <scrubbed>[0]-><scrubbed>[0] spi=<scrubbed>(0x<scrubbed>)
I/racoon ( 4330): IPsec-SA established: ESP/Transport <scrubbed>[500]-><scrubbed>[500] spi=<scrubbed>(0x<scrubbed>)
I/mtpd ( 4532): Tunnel established
D/mtpd ( 4532): Received ICRP (remote_session = 65060) -> Sending ICCN
D/mtpd ( 4532): Received ACK
I/mtpd ( 4532): Session established
I/mtpd ( 4532): Creating PPPoX socket
I/mtpd ( 4532): Starting pppd (pppox = 13)
I/mtpd ( 4532): Pppd started (pid = 4533)
I/pppd ( 4533): Using PPPoX (socket = 13)
E/pppd ( 4533): This system lacks kernel support for PPP. This could be because
E/pppd ( 4533): the PPP kernel module could not be loaded, or because PPP was not
E/pppd ( 4533): included in the kernel configuration. If PPP was included as a
E/pppd ( 4533): module, try `/sbin/modprobe -v ppp'. If that fails, check that
E/pppd ( 4533): ppp.o exists in /lib/modules/`uname -r`/net.
E/pppd ( 4533): See README.linux file in the ppp distribution for more details.
I/mtpd ( 4532): Received signal 17
I/mtpd ( 4532): Pppd is terminated (status = 4)
D/mtpd ( 4532): Sending STOPCCN
I/mtpd ( 4532): Mtpd is terminated (status = 36)
I double-checked /proc/conf.gz and sure enough it contains all ppp options:
Code:
# zcat /proc/config.gz | grep PPP
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_MPPE=y
CONFIG_PPPOE=y
CONFIG_PPPOL2TP=y
CONFIG_PPPOLAC=y
CONFIG_PPPOPNS=y
I noticed in mik_os's sources that LG also set CONFIG_ANDROID_PARANOID_NETWORK to y, while in mik_os's build it is set to n.
Does anyone know if they are related and/or if I'm running into another issue (permissions, maybe)?
Thanks in advance
Sure enough, it was CONFIG_ANDROID_PARANOID_NETWORK.
For future reference, if this option is undefined AID_NET_ADMIN and AID_NET_RAW have no special meaning for the kernel (iow, CAP_NET_ADMIN and CAP_NET_RAW are not granted to non-root processes belonging to those special groups).
Moreover, network access restrictions are completely ignored, so any application can create sockets and/or access the bluetooth stack even if its manifest does not specify the relevant permissions.
(The procedures can be found at post #4)
It is apparent that prior to ICS, ad hoc wireless networks are not supported: h t t p:// code. google.com/p/android/issues/detail?id=82
Does anyone know if ad hoc wireless is supported under ICS? I can't seem to find ad hoc wireless networks on my U9GT 2 tablet, running Android 4.0.3.
Anyone???
Saw this useful thread: http://szym.net/2010/12/adhoc-wifi-in-android/
Source Code to wpa_supplicant (ICS): https://github.com/jhonxie/android_external_wpa_supplicant_6/tree/ics
But I still can't get it to work. HELP!
After ploughing through the materials on the Internet, I finally got it to work! I believe this method works for any Android device, of any Android version. However, this method is tedious as I couldn't get the system to accept the adhoc configuration in wpa_supplicant.conf.
Here are the steps:
Ignore the first character of my example command-lines as it represents the prompt (i.e. $, #, >)
Run Terminal Emulator and elevate to root privileges / be the superuser. Then run "wpa_cli", the software interface to the wireless stack:
Code:
$ su
# wpa_cli
>
Now that you're in wpa_cli, the first command is to add a network:
Code:
> add_network
5
Take note as the system would output a number. That is the number that represents your adhoc network. In my example, the number is "5".
Next, type the following commands to set (configure) network "5" (be sure to fill in the respective SSID and BSSID):
Code:
> set_network 5 mode 1
OK
> set_network 5 ssid "MyAdHocWiFi"
OK
> set_network 5 bssid aa:BB:cc:DD:ee:FF
OK
> set_network 5 key_mgmt NONE
OK
> enable_network 5
OK
> ap_scan 2
OK
> select_network 5
OK
If you don't know your bssid, run WiFi Analyzer from the Android Market. The system would reply an "OK" after every successfully executed command. If you get a "FAIL", check your syntax - is the an extra / missing quote?
At this point, you should see a bunch of system messages. There might be some error messages but that might not mean the adhoc wireless connection had failed. Check if your device has successfully obtained an IP configuration:
Code:
# busybox ifconfig
Now, you might think this is a hell lot of work... You're right! It should be able to read the configuration file (e.g. /data/misc/wifi/wpa_supplicant.conf) and connect automatically, but I couldn't get wpa_supplicant to accept my adhoc configuration! I'll update this thread when I got it sorted out.
Finally, I am able to tether to my Nokia phone with JoikuSpot!
References:
- http://szym.net/2010/12/adhoc-wifi-in-android/
- http://www.olsr.org/?q=olsr_on_android
Do you have something that would work with wpa_supplicant v0.8.x?
The wpa_cli command is failing because it cannot be found. Should it be in my system/bin folder? I've since installed busybox and would love to connect to my adhoc network. Suggestions?
wendal has kindly compiled the wpa_supplicant that works with adhoc wireless networks (IBSS). For more info, refer here: http://www.slatedroid.com/topic/286...licant-source/page__view__findpost__p__304667
Has anyone got that file to work? I always try it but my wireless stays frozen. I've changed the ownership and permissions and still nothing!!!
megabiteg said:
Has anyone got that file to work? I always try it but my wireless stays frozen. I've changed the ownership and permissions and still nothing!!!
Click to expand...
Click to collapse
It didn't work for me on my ICS kindle-fire.. According to the log it seems like it doesn't recognize the kindle-fire wireless interface. I am wondering at this point whether each device uses its own wpa_supplicant that works with its own driver or what else. I am going to find out more about it and see if I can get my own wpa_supplicant patched with IBSS and compiled.
Code:
I/ActivityManager( 1400): No longer want com.android.vending (pid 2307): hidden #16
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiStateMachine( 1400): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1400): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
D/CommandListener( 1296): Setting iface cfg
D/CommandListener( 1296): Trying to bring down tiwlan0
D/CommandListener( 1296): broadcast flag ignored
D/CommandListener( 1296): multicast flag ignored
D/NetworkManagementService( 1400): rsp <213 f0:a2:25:77:b3:22 0.0.0.0 0 [down broadcast multicast]>
D/NetworkManagementService( 1400): flags <[down broadcast multicast]>
E/wpa_supplicant( 2457): Unsupported driver 'tiwlan0'.
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiStateMachine( 1400): Failed to setup control channel, restart supplicant
Not working on hidden WPA2 AES Wigi
Hi there, I have a rooted stock ICS Google Nexus. On my workplace, the wifi has hidden SSID with WPA2-Personal and AES. When I try to connect with it, nothing happens. It's does not save on the wpa_supplicant.conf also.
I've tried the compiled wpa_supplicant mentioned on the post, but the same thing happens... I've even tried to edit manually the wpa_supplicant.conf but the wifi crashed after that (thankfully I had a backup).
So any ideas on how to get this thing connected? On my later Atrix with stock 2.3.6 it connected just fine...
Thanks.
Hello i tried many adhoc fixes and now i can connect to adhoc network but after 1-2 minutes connection get lost. Does anybody know how to solve the problem?
i use Htc Sensation with ICS
I have ICS CM9 on my HTC legend and can't recognise the wirelss network at my office. At home no problem.
If I launch wpa_cli I get:
Using interface 'tiwlan0'
Inteactive mode
>
<2>CTRL-EVENT-SCAN-RESULTS
and the last line continues to loop.
Is it correct? What should I do then and to let this wi fi network accessible?
Try this
Hello,
I just got a new Idolian tablet and couldn't connect to my hidden home SSID. I just thought I'd try something really quick and it worked..! I added network in manually but it said not in range. Try temporarily turning the SSID broadcast back on then connect. Mine was successful. I then turned off the SSID broadcast on the router and the wifi off and on again on the tablet and it connected perfectly.
I've been reading this forums for almost a year but this is my 1st post so hopefully it will help someone out as these forums have for me.
Has anyone got it to connect and not get the obtaining IP address loop? My device finds the Ad Hoc network for my cars ODB2 wifi adapter but will never connect.
Good day friends, I really need to enable ad-hoc on my HTC One X, to use my Brookstone Rover, more'm not getting my wpa_supplicant is v8.
I have a doubt, this command set_network 5 bssid aa: BB: CC: DD: ee: FF, this is the bssid mac network card from my smartphone or mac card that will connect my smartphone?
thank you very much
Edit wpa_supplicant.conf instead of wpa_supplicant
I changed data/misc/wifi/wpa_supplicant.conf instead of /system/bin/wpa_supplicant.
Step1:First i scanned my adhoc network using Wifi Manager. It shows adhoc networks. I ignored it's warning and tried to connect. It'll fail.No problem! We now have the adhoc network listed in wpa_supplicant.conf.
Note: you can skip this step if you know how to edit wpa_supplicant.conf manually or if your device already lists adhoc networks on scanning.
Step2: You'll need to root your device if you're doing this through your device itself. If you use adb you may not need to root your device.(I had root access by default through adb. So rooting the device wasn't necessary for me). If you're using pc(windows or linux), i recommend Android Commander. If you're doing this from device itself, use some Root Explorer and Terminal Emulator.
Pull and/or edit data/misc/wifi/wpa_supplicant.conf. Add the following line
ap_scan=2
Find line like
network={
ssid="your adhoc name"
bssid=*some value*
.
.
}
Delete bssid line.
Add/Change the following
scan_ssid=1
priority=1
mode=1
Push back/save the modified file.
chown ownership back to system.wifi. Type the following in adb/Terminal Emulator
#chown system.wifi data/misc/wifi/wpa_supplicant.conf
Ok, done! Now you can turn on wifi and if the specified adhoc network is nearby, your device'll automatically connect to it. Don't scan for new networks. If you do, adhoc support will be lost and you'll have to start over again!
Advantage: Safer than modifying system/etc/wifi/wpa_supplicant binary. Saves you the trouble of compiling modified wpa_supplicant or finding a compiled one for your platform.
Drawback: This is just a temporary solution.You'll have to repeat this process for every new adhoc network as it doesn't enable adhoc forever. It is good for connecting to your home network or other known networks, but if you want to connect to any adhoc network you scan,then this is not your method. Because, wpa_supplicant.conf will be overwritten every time you scan a new network.
For more details refer
http://forum.xda-developers.com/showthread.php?t=1591207
error adhoc network
Hello,
I have android 4.2.2 ,Nexus 4
I did the same steps but I can not connect to adhoc network
I receive the output below:
> OK
<3>CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<4>Failed to initiate AP scan
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
<3>CTRL-EVENT-STATE-CHANGE id=4 state=0 BSSID=1a:79:c3:0c:b1:bd
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
have you any idea about why doesn't work with me.
---------- Post added at 10:28 AM ---------- Previous post was at 10:24 AM ----------
Hello,
I have android 4.2.2 ,Nexus 4
I did the same steps but I can not connect to adhoc network
I receive the output below:
> OK
<3>CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<4>Failed to initiate AP scan
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
<3>CTRL-EVENT-STATE-CHANGE id=4 state=0 BSSID=1a:79:c3:0c:b1:bd
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
have you any idea about why doesn't work with me.
fyresg said:
After ploughing through the materials on the Internet, I finally got it to work! I believe this method works for any Android device, of any Android version. However, this method is tedious as I couldn't get the system to accept the adhoc configuration in wpa_supplicant.conf.
Here are the steps:
Ignore the first character of my example command-lines as it represents the prompt (i.e. $, #, >)
Run Terminal Emulator and elevate to root privileges / be the superuser. Then run "wpa_cli", the software interface to the wireless stack:
Code:
$ su
# wpa_cli
>
Now that you're in wpa_cli, the first command is to add a network:
Code:
> add_network
5
Take note as the system would output a number. That is the number that represents your adhoc network. In my example, the number is "5".
Next, type the following commands to set (configure) network "5" (be sure to fill in the respective SSID and BSSID):
Code:
> set_network 5 mode 1
OK
> set_network 5 ssid "MyAdHocWiFi"
OK
> set_network 5 bssid aa:BB:cc:DD:ee:FF
OK
> set_network 5 key_mgmt NONE
OK
> enable_network 5
OK
> ap_scan 2
OK
> select_network 5
OK
If you don't know your bssid, run WiFi Analyzer from the Android Market. The system would reply an "OK" after every successfully executed command. If you get a "FAIL", check your syntax - is the an extra / missing quote?
At this point, you should see a bunch of system messages. There might be some error messages but that might not mean the adhoc wireless connection had failed. Check if your device has successfully obtained an IP configuration:
Code:
# busybox ifconfig
Now, you might think this is a hell lot of work... You're right! It should be able to read the configuration file (e.g. /data/misc/wifi/wpa_supplicant.conf) and connect automatically, but I couldn't get wpa_supplicant to accept my adhoc configuration! I'll update this thread when I got it sorted out.
Finally, I am able to tether to my Nokia phone with JoikuSpot!
References:
- http://szym.net/2010/12/adhoc-wifi-in-android/
- http://www.olsr.org/?q=olsr_on_android
Click to expand...
Click to collapse
Thanks brother! This was what I was looking for everywhere!
The wpa_supplicant method did not work for Me and this did! Thanks a lot!
Hi all,
I recently purchased a SGS3 and ran the stock ROM for approx 30mins before flashing a CM10 nightly build (i9300 intl). Because of this I am unable to verify if the wifi was working on my home router prior to flashing a custom ROM.
At work I am able to connect to our wifi connection without problemson 2.4ghz or 5ghz. At home I've got a D-Link DSL-G604T wireless router which I am unable to connect to. I've tried changing the wifi channel, password, removing protection, factory reset and installed a seperate CM10 nightly build without any help.
When trying to connect to the WIFI connection I get the following output in adb logcat.
Anyone have any ideas what may be stopping me from connecting ot my wifi?
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
I/wpa_supplicant( 5841): wlan0: Trying to associate with 00:1e:58:80:a2:e2 (SSID
='HOMEWIFI' freq=2452 MHz)
D/CommandListener( 1913): Clearing all IP addresses on wlan0
I/wpa_supplicant( 5841): wlan0: Associated with 00:1e:58:80:a2:e2
I/wpa_supplicant( 5841): wlan0: Authentication with 00:1e:58:80:a2:e2 timed out.
I/wpa_supplicant( 5841): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00
reason=0
More info of my phone (kernel, build etc): i.imgur.com/PRaEx.png
Cheers
You could try install the latest Siyah kernel, which contains the updated Wifi driver which could help. I used to have my Wifi absolutely fine with my ICS stock ROM. When I upgraded to CM 10 Jelly Bean, my Wifi works but very unstable. Two solutions that worked for me. 1- Use Wifi fixer app 2- Upgrade Siyah 1.7b4 kernel.
And now I can enjoy CM10 and AOKP at the same time without Wifi problems
Hope this helps
this is also happening on the verizon cm10 builds to for the gs3.