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.
Related
Wifi Calling now working! This is a T-Mobile US only feature as your phone carrier must have the architecture on their end for this to work.
Wifi Calling still uses your minutes as if you were connected to a tower.
Wifi Calling turns off your cellular radio when it's connected. This saves power and will also show -113dB signal.
Wifi Calling also sends SMS and MMS over wifi.
[11/10/10 v1.0]
-fixed kineto_ko kernel module. its now included and loads on bootup, compiled from cyanogenmod-exp kernel
-should make it easier for everyone past and present to get wifi calling up and running.
-temporarily disabled bundled kineto app, it was causing problems so until I figure it out I'm not including it with the update.zip
Thanks to Rsotbiemrptson for getting the Libraries and everything into an update.zip.
Thanks to intersectRaven for the kernel mod's regarding kineto and applying the WiFi PM FAST patch.
Thanks to Myshkinbob for the research and creating PM FAST patch.
To Install
1)If you don't have the 5.08 or 5.12 radio installed you MUST install that first!
2)Download and flash the Wildmonks or intersectraven kernel(before flashing kineto!)from the links below
3)Download and flash kineto-n1-bundle attached below.
4)Download and install MS-HTCVISION-KNT20-02.apk
5)If you install any kernel, 720p hacks or mods it can break wifi calling.. any time you flash an update.zip re-flash the kineto bundle. There are important libraries linked in build.prop that must be in or there will be problems. You can attempt to make a custom build.prop or post in the forum for help.
5)Enjoy!
Known Issues
-Bluetooth - Calls are not being connected to a bluetooth at this time.
-Bootloops on enabling wifi - Update your radio! 5.12 or 5.08 is required.
-After flashing if you still experience call problems it will be necessary to change your setcpu screen off profile to 245min 384max.
-Volume is low
-Sporadic MMS sending problems(APN related)
intersectRaven Kernels
CM Based Kernel 20101108_1328 - http://www.mediafire.com/download.php?4obtdv52efkvece
NON-CM Based Kernel 20101108_1328 - http://www.mediafire.com/download.php?urv9wl2ek0fae9c
wildmonks Kernels
http://forum.xda-developers.com/showthread.php?t=693375
dekips said:
Credit to the G2 OTA Update thread and Stryf3 for the APK extraction. I've installed this but I keep getting "Please wait while connecting to T-Mobile". I figured I'd upload it here for fellow N1's while I played with it.
*Update with logcat:
I/Kineto::main( 312): Kineto: SendAlarmEvent Enter
E/KINETO ( 312): KLOG0A2- ERROR: IBS Msg Q Post: size is too large
E/KINETO ( 312): KLOG0A2- ERROR: Failed to post to Queue
I/Kineto::Receiver( 312): onReceive Exit
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
I/Kineto::Receiver( 312): onReceive Enter
I/Kineto::main( 312): Kineto: SendAlarmEvent Enter
E/KINETO ( 312): KLOG0A2- ERROR: IBS Msg Q Post: size is too large
E/KINETO ( 312): KLOG0A2- ERROR: Failed to post to Queue
I/Kineto::Receiver( 312): onReceive Exit
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
D/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
E/KINETO ( 312): KLOG0C3- xmk_QueryOSQueue SDL Queue empty : WAIT_FOREVER
E/KINETO ( 312): KLOG0A3- ibs_os_GetMsg: Timeout forever for UKCC qHnd 0x814310a4
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
I/Kineto::Receiver( 312): onReceive Enter
I/Kineto::main( 312): Kineto: SendAlarmEvent Enter
Click to expand...
Click to collapse
same here stuck on enabling.....please someone fix...keep us posted please
From the looks of things, there is an underlying app that the Wifi Calling app connects to. Any thoughts?
dekips said:
From the looks of things, there is an underlying app that the Wifi Calling app connects to. Any thoughts?
Click to expand...
Click to collapse
Kineto apk has a oss.html which calls out files used for IPSec VPN connections. I suspect some VPN magic at work.
daijizai said:
Kineto apk has a oss.html which calls out files used for IPSec VPN connections. I suspect some VPN magic at work.
Click to expand...
Click to collapse
It's possible there is a tunnel which it is trying to establish, I'd like to think that it would only do that when the wifi calling is enabled. I'm getting a crazy flow from logcat of it trying to connect even when wifi calling is off and wifi is off.
There is a local daemon or missing piece of software it can't connect to. Is this application in the radio or is it another apk?
Ive stripped it down and am in the process of reading, but it needs to be set to try to connect to something or somewhere, without the datafile that tells it where to connect to it just cycles a connect to localhost
the package just loops trying to connect to 127.0.0.1
Viralblack said:
Ive stripped it down and am in the process of reading, but it needs to be set to try to connect to something or somewhere, without the datafile that tells it where to connect to it just cycles a connect to localhost
the package just loops trying to connect to 127.0.0.1
Click to expand...
Click to collapse
I'm in the process of getting a full update.zip.. no luck tonight so I'm calling it and goin to bed
I want to guess that it *could* possibly be in a host file.... It seems like it is doing a port loopback, to the radio... I assume...
do we have an IRC to talk to the guy that pulled this out of his phone?
It could be in the hosts file. I hope we get this soon, because I have like zero service in my apartment and this will be amazing
iria said:
It could be in the hosts file. I hope we get this soon, because I have like zero service in my apartment and this will be amazing
Click to expand...
Click to collapse
can someone get a line in to the guy(s) that has the file?
same problem
im getting same as everyone else
Here's a quote that might clarify some things:
So here’s the update on yesterday’s reported OTA update to the G2, which brought Wi-Fi calling and mobile hotspot creation to a very small set of users. T-Mobile released this official statement to clarify its position:
“Wi-Fi Calling and tethering Wi-Fi sharing are not currently supported on the T-Mobile G2. T-Mobile knows these features are important to consumers and we’re working to deliver them to G2 users in the future. We have nothing further to announce at this time.”
It’s pretty much what they’ve said before on the subject, and it doesn’t tell us much. It could mean that the update we saw yesterday was just a test and won’t be rolled out to the rest of G2 owners. Or it might be a test sample to see how these features affect data traffic, in order to help T-Mo with pricing. Or maybe they really are rolling it out to everyone and just haven’t put the support feautres, etc. in place yet.
via PhoneScoop by way of TmoNews
Click to expand...
Click to collapse
Just installing the apk won't be enough. There are a few libraries that will be needed as well. The kineto libraries and module(s) will be needed as well. The path to the RIL will have to be redirected also. This is likely changed via the build prop. A full system dump from a WiFi calling equipped G2 would be needed.
I still have not been able to source the original G2 OTA update.zip nor have I any luck finding someone with an updated G2 to pull specifics on the Kineto app configuration. If anyone has any luck with any of the above please post.
dekips said:
I still have not been able to source the original G2 OTA update.zip nor have I any luck finding someone with an updated G2 to pull specifics on the Kineto app configuration. If anyone has any luck with any of the above please post.
Click to expand...
Click to collapse
A co-worker recently obtained a G2. I will see if he has gotten the update, and if so, if he will help us
bennettm89 said:
A co-worker recently obtained a G2. I will see if he has gotten the update, and if so, if he will help us
Click to expand...
Click to collapse
yeah he should have the same problem and once they go online meaning tmobile it will and should automatically configure itself like ota
Weird thing is that I installed this and it actually worked, or at least looked like it worked for a minute. I got a new icon on the taskbar when calling with it enabled, and the call went through fine.
I turned the wifi calling off and then back on and now it is acting like everyone else's now... stuck on enabling.
Not sure if it actually was working for that one call, but it sure seemed like it. Wish I would have thought to grab a screenshot.
I'm stoked. I really need this at home.
Same here. When I originally installed the app, I had WiFi turned on and was at home near my UMA router. Worked fine until I disabled the application and attempted to re-enable it. Now stuck on enabling like everyone else.
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?
i am developing a cutom rom for lg p500 everything works execpt wifi can anyone help me please
here is the logcat
E/WifiHW ( 694): wifi_load_driver:idriverType=0
E/WifiHW ( 694): DRIVER_MODULE_ARG=firmware_path=/system/wifi/sdio-g-cdc-full11n-reclaim-roml-wme-aoe-pktfilter-wapi.bin nvram_path=/system/wifi/nvram.txt
W/WifiHW ( 694): Couldn't turn on SDIO polling: /etc/init.qcom.sdio.sh 1
E/CheckinTask( 1222): SSL error, attempting time correction: javax.net.ssl.SSLException: Not trusted server certificate
samrox144 said:
i am developing a cutom rom for lg p500 everything works execpt wifi can anyone help me please
here is the logcat
E/WifiHW ( 694): wifi_load_driver:idriverType=0
E/WifiHW ( 694): DRIVER_MODULE_ARG=firmware_path=/system/wifi/sdio-g-cdc-full11n-reclaim-roml-wme-aoe-pktfilter-wapi.bin nvram_path=/system/wifi/nvram.txt
W/WifiHW ( 694): Couldn't turn on SDIO polling: /etc/init.qcom.sdio.sh 1
E/CheckinTask( 1222): SSL error, attempting time correction: javax.net.ssl.SSLException: Not trusted server certificate
Click to expand...
Click to collapse
Have you tried using the stock driver for the WiFi? Not a developer as you can see BUT I've messed up and FIXED my share of devices and I can tell you from experience that 99.9% of the time is usually something really simple that you might be overlooking......GOOD LUCK dude!
Ok i will try
Sent from my LG Optimus One P500 using XDA App
(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 guys.
I need a solution about my problem.
I have a Zyxel modem and S3. Problem is my s3 constantly dropping connection to my Wifi.
When I disable the wifi psm (power safe mode) from secret code *#0011# the problem is gone.
I need a permanent solution on this. I mean I have to do this everytime I reboot the phone.
Code:
I/WiFiDebugScreen(12068): mPowerSaveMode Value= 1
D/dalvikvm( 2935): WAIT_FOR_CONCURRENT_GC blocked 0ms
I/WiFiDebugScreen(12068): onResume
D/WiFiDebugScreen(12068): [WiFiInfoActivity] WakeLock Acquired
D/PowerManagerService( 2311): acquireWakeLock flags=0x3000001a tag=WiFiDebugScreen uid=1000 pid=12068 myUID=1000 myPID=2311 myTID=2323
I/WiFiDebugScreen(12068): 1:WifiManager.NETWORK_STATE_CHANGED_ACTION
I/WiFiDebugScreen(12068): 3:WifiManager.WIFI_STATE_CHANGED_ACTION
D/WindowManager( 2311): mInputFocus is not null.
Is there anyway for it? Like adding build.prop to a PowerSaveMode=0 etc?