Dear all,
I wish share my experience, with Supernexus 2.0 Build 4.0 on my gs3, more especially with the wifi tethering.
Like most of people, i encountered the issue with the last version where wifi tether did not work, although in the release note, it is indicated as fixed.
So, like others guys, second device was properly connected to the wifi hotspot (it had an IP adress).
Ping to gateway OK... For me, all should be ok to provide internet to second device, but never.... :crying:
I decided, after many tests, wipes, re-install, to check logfile with logcat tools, and i found this :
05-06 08:29:14.255 D/Tethering(2264): notifying tethered with iface =null
...
...
05-06 08:29:20.775 D/libgps (2264): agps_ril_update_network_state: Waiting for IPC connection - timeout
05-06 08:29:20.775 E/libgps (2264): GpsiClient: Can't write to closed pipe
05-06 08:29:20.775 E/libgps (2264): IPC Communication Error, /tmp/11980989/proprietary/deliverables/android/gps_interface/../gps_interface/gpsi_client/GpsiClient.cpp:1143 agps_ril_update_network_state
05-06 08:29:20.775 D/libgps (2264): proxy_agps_ril_update_network_state: called
05-06 08:29:20.775 D/libgps (2264): agps_ril_update_network_availability: Waiting for IPC connection...
05-06 08:29:21.780 D/libgps (2264): agps_ril_update_network_availability: Waiting for IPC connection - timeout​
Where id 2264 is regarding the tether process in activity for my test.
So, when i read logfile, I found this very weird :
05-06 08:29:20.775 E/libgps (2264): IPC Communication Error, /tmp/11980989/proprietary/deliverables/android/gps_interface/../gps_interface/gpsi_client/GpsiClient.cpp:1143 agps_ril_update_network_state
So, by curiosity, i enabled GPS by the toggle, and a miracle appear, the wifi tethering has worked perfectly.....
My second device connected to the hospot, can browse and get data from internet.... :victory:
May be, someone (an expert) can explain this, but for the moment I wish share this workaround with all.
See you,
Manuxme.
May be relevant to us, don't know. But should be noted the ROM you mention is for the international, just in case someone gets eager and tries using it.
We have hotspot unlocked for the most recent builds of TW.
He is posting in the wrong g forum
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
He is posting in the wrong g forum
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
You are right.... Sorry for that, it was my first ppost altough I follow many subject since few weeks....
DO not hesitate to move the post to the good one
Manuxme.
Is the post can be move to this area :
Samsung Galaxy S III I9300, I9305 > Galaxy S III Q&A, Help & Troubleshooting (and not Sprint Samsung Galaxy S III > Sprint Galaxy S III Q&A, Help & Troubleshooting ).
Sorry for the inconveniences.
Manuxme.
Manuxme said:
Is the post can be move to this area :
Samsung Galaxy S III I9300, I9305 > Galaxy S III Q&A, Help & Troubleshooting (and not Sprint Samsung Galaxy S III > Sprint Galaxy S III Q&A, Help & Troubleshooting ).
Sorry for the inconveniences.
Manuxme.
Click to expand...
Click to collapse
You can report the thread (from the browser) and just say you want the thread moved, or PM a mod
CNexus said:
You can report the thread (from the browser) and just say you want the thread moved, or PM a mod
Click to expand...
Click to collapse
Done
Transmitted with a portable device using Xparent Blue Tapatalk 2
All,
About the workaround indicated yesterday by enabling the GPS, actually, it does not work !!!!
I do not why yesterday it works. When GPS turn UP wifi tether works when turn down, it does not works. A strange luck ??!!
BTW, I continu investigations, tests and founds the really root cause (already found by people on other forum) :
Code:
AccountRecoveryService$Receiver }
05-07 13:06:28.145 D/dalvikvm(2725): GC_CONCURRENT freed 360K, 5% free 9328K/9784K, paused 1ms+1ms, total 14ms
05-07 13:06:28.320 D/ConnectivityService(2268): handleInetConditionHoldEnd: net=0, condition=100, published condition=100
05-07 13:06:30.230 D/ConnectivityService(2268): ConnectivityChange for mobile_dun: CONNECTED/CONNECTED
05-07 13:06:30.270 E/SecondaryTablController(1907): [B]ip route add failed: /system/bin/ip route add 0.0.0.0/0 via 10.221.59.1 dev rmnet1 table 60[/B]
05-07 13:06:30.270 W/FrameworkListener(1907): Handler 'interface' error (No such device)
05-07 13:06:30.275 E/ConnectivityService(2268): Exception trying to add a route: java.lang.IllegalStateException: command '182 interface route add rmnet1 secondary 0.0.0.0 0 10.221.59.1' failed with '400 182 ip route modification failed (No such device)'
05-07 13:06:30.275 E/ConnectivityService(2268): Exception trying to remove a route: java.lang.IllegalStateException: command '183 interface route remove rmnet1 default 0.0.0.0 0 10.221.59.1' failed with '400 183 Failed to remove route from default table (No such process)'
05-07 13:06:30.295 W/NetworkPolicy(2268): shared quota unsupported; generating rule for each iface
05-07 13:06:33.300 D/Tethering(2268): TetherModeAliveState.processMessage what=3
05-07 13:06:33.300 D/Tethering(2268): chooseUpstreamType(true), preferredApn =4, got type=4
05-07 13:06:33.335 D/TetherController(1907): setDnsForwarders(0 = '192.168.10.110')
05-07 13:06:33.335 D/TetherController(1907): Sending update msg to dnsmasq [update_dns:192.168.10.110]
Everytime, Wifi tethering is enable; this issue apear :
05-07 13:06:30.270 E/SecondaryTablController(1907): ip route add failed: /system/bin/ip route add 0.0.0.0/0 via 10.221.59.1 dev rmnet1 table 60
So, with a terminal emulator in root acces on the phone (example below in the screenshot), i launch exactly the same command line, and it works ?! :
Screenshot explanation:
1 - Check the new entry, added by the start of wifi tether process.
In orange, the exact command line launch on the terminal, in the history command line number 10.
Now, i sure, with this manual intervention, it works , the wifi tether allow other device to reach internet.
But why it failed everytime by the the normal way ? Is someone know ?
FOr the moment, i am going to try to write a shell script to add/remove the entry when necessary.
Thanks,
Manuxme.
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
(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!
First Post so I cant send this to the dev forum for the actual build!
I am suffering from the lack of "3G" which I have noticed is widespread across many users for this build of Android.
To help the developers I have tried doing my homework...and it's fair to say that the 3G connection is connecting, however it isn't getting any data routed via the 3G connection.
I found this out by doing the following:
From the Phone keypad type *#*#4636#*#*
I made a note of the following settings.
Ping IP Addr: Fail: IP addr not reachable
Ping Host Name w w w.google. co. uk):Fail Host unreachable
HTTP Client test: Fail IOException
GSM Service:In Service
GPRS Serice:Connected
Network Type: GPRS
GSM Disconnects:========DATA=======
StatecActiveState
connected at 7:00PM and elapsed 20:42 to ApnSettingV2 Vodafone Contract Iteernet, 196,23415, Internet, h t t p: / / mms .vodafone. co. uk/servlets/mms/212.183.137.012,8799,,-1, default | supl | mms, IP, IP
Interface:rmnet0
address:10.163.102.xx (all anyone needs to know is that the xx here and the xx what I pinged in busybox below were the same!)
gateway:10.163.102.yy
dns: 88.82.13.60, 88.82.13.60
ping 10.163.102.xx (10.163.102.xx): 56 data bytes
ping: send to: Network is unreachable
ping 127.0.0.1
64 bytes from 127.0.0.1 seq=0 time=0.427ms
64 bytes from 127.0.0.1 seq=1.....etc
(yes loopback worked)
However....
In BusyBox:
su root
route
Kernel IP Routing Table
Destination Gateway Genmask Flags Metric Reg Use Iface
#
The whole routing table is blank!
Now from what I have been taught this week, a routing table should at least have an ip address and an adaptor, a gateway via an adaptor,and an internal loopback address.
WIFI was turned off deliberately and so far has not been enabled. This was so that no settings were contaminated (plus I didn't have a wifi connection available to me at the time).
These settings were taken from a clean installation of the 08mar12 magldr version of the nand rom.
Developers....please please please help me in this matter - I am trying to do diagnostics by adding routes on the routing table or look at a cached routing table (if one exists).
This is a brilliant build of android - it's just a shame that there is this problem. I moved from the sd build to the nand build because I was so impressed - unfortunately this wasnt a wise move for the timebeing even as a stopgap until this problem is resolved - I can't go back to it because I dont have the pre 2012 sd build to hand and all prior sd releases from fileservers have been removed (....
Big thanks to the American Android and Cyanogenmod team so far for a brilliant piece of software development and programming!!!
Hope this data helps warrenb & copenhagen with diagnostics!
BW
Hi, did you find a resolution to this. I'm experiencing the same problem with this build and orange UK.
Nope....still waiting on some expert assistance...or a new build that works...whichever is the sooner.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Hello,
I'm new to the world of Fascinate and am currently running my Fascinate on Page Plus. Using the stock TouchWiz ROM, I have 3G working with no problems. Once I flash to an AOSP ROM such as AOKP or MIUI, 3G no longer works. Does anyone know of anything I could be doing wrong, or if there are any files that I can modify to make 3G work on AOSP/ICS ROMs using Page Plus Cellular?
Thanks!
ac_lanham said:
Hello,
I'm new to the world of Fascinate and am currently running my Fascinate on Page Plus. Using the stock TouchWiz ROM, I have 3G working with no problems. Once I flash to an AOSP ROM such as AOKP or MIUI, 3G no longer works. Does anyone know of anything I could be doing wrong, or if there are any files that I can modify to make 3G work on AOSP/ICS ROMs using Page Plus Cellular?
Thanks!
Click to expand...
Click to collapse
Prolly just need to copy over the network specific stuff in the build . Prop and the apn -config
Sent from my Glitched AOKP Unicorn.
Stephen.k.spear said:
Prolly just need to copy over the network specific stuff in the build . Prop and the apn -config
Sent from my Glitched AOKP Unicorn.
Click to expand...
Click to collapse
Thanks sir. I'm going to give that a shot.
Ok, I'm making some slight progress on this issue.
I ran an ADB logcat on the device (excuse me if I got the terminology wrong, very new to Android) and got the following message
E/ConnectivityService( 261): Exception trying to add a route: java.lang.IllegalStateException: Unable to communicate with native dameon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route add ppp0 default 0.0.0.0 0 66.174.168.64} failed with code 400 : {Failed to add route to default table (No such device)}
D/NetworkPolicy( 261): applying policy NetworkPolicy[NetworkTemplate: matchRule
=MOBILE_ALL, subscriberId=valid]: cycleDay=3, warningBytes=2147483648, limitBytes=-1, lastSnooze=-1 to ifaces [ppp0]
D/pppd ( 4014): using channel 163
I/pppd ( 4014): Using interface ppp0
I/pppd ( 4014): Connect: ppp0 <--> /dev/ttyCDMA0
W/pppd ( 4014): Warning - secret file /etc/ppp/pap-secrets has world and/or group access
I had to dink around with the chap-secrets and pap-secrets some and it finally authenticated. Hopefully when I get past this it will be smooth sailing.
Damn this thing is kicking my butt. If anyone has any suggestions, please help
I'm getting the following message now in adb logcat
E/pppd ( 4275): Could not determine local IP address
I/pppd ( 4275): Connect time 0.2 minutes.
I/pppd ( 4275): Sent 97 bytes, received 58 bytes.
I/pppd ( 4275): LCP terminated by peer
W/Netd ( 202): No subsystem found in netlink event
D/NetlinkEvent( 202): Unexpected netlink message. type=0x11
Almost acts as if it may be DHCP
ac_lanham said:
Hello,
I'm new to the world of Fascinate and am currently running my Fascinate on Page Plus. Using the stock TouchWiz ROM, I have 3G working with no problems. Once I flash to an AOSP ROM such as AOKP or MIUI, 3G no longer works. Does anyone know of anything I could be doing wrong, or if there are any files that I can modify to make 3G work on AOSP/ICS ROMs using Page Plus Cellular?
Thanks!
Click to expand...
Click to collapse
I can't speak for MIUI (never tried it), but AOSP, AOKP, THS and CM9 ICS ROMs work fine for my on PagePlus. I've never had any 3G issues. I've never had to make any changes to get 3G to work.
Does anyone have a working solution for PPTP VPN on custom O1 roms? I've tried a lot of ROMs and even CMs don't seem to have it.
It's an important feature so I'm a little bit disappointed that it's not yet properly implemented in these ROMs.
Sadly I'm not a Linux programmer so I couldn't fix it myself, but I hope some devs will see this post and tell me whether it would be possible to implement it in the feuture releases.
I'd be happy to assist in debugging if someone would try to fix the PPTP VPN module.
Here is the log (the error is always the same - Socket() Address family not supported by protocol) :
07-18 15:09:00.469: I/Vpn(198): Switched from [Legacy VPN] to [Legacy VPN]
07-18 15:09:00.479: V/LegacyVpnRunner(198): Waiting
07-18 15:09:00.479: V/LegacyVpnRunner(198): Executing
07-18 15:09:00.559: D/mtpd(5449): Waiting for control socket
07-18 15:09:00.719: D/mtpd(5449): Received 20 arguments
07-18 15:09:00.719: I/mtpd(5449): Using protocol pptp
07-18 15:09:00.719: I/mtpd(5449): Connecting to vpn.[my vpn host].com port 1723 via wlan0
07-18 15:09:00.789: I/mtpd(5449): Connection established (socket = 11)
07-18 15:09:00.789: D/mtpd(5449): Sending SCCRQ
07-18 15:09:00.809: D/mtpd(5449): Received SCCRP -> Sending OCRQ (local = 54508)
07-18 15:09:00.809: I/mtpd(5449): Tunnel established
07-18 15:09:00.829: D/mtpd(5449): Received OCRQ (remote = 27834)
07-18 15:09:00.829: I/mtpd(5449): Session established
07-18 15:09:00.829: I/mtpd(5449): Creating PPPoX socket
07-18 15:09:00.829: A/mtpd(5449): Socket() Address family not supported by protocol
07-18 15:09:00.919: I/LegacyVpnRunner(198): Aborting
07-18 15:09:00.919: I/LegacyVpnRunner(198): java.lang.IllegalStateException: mtpd is dead
07-18 15:09:00.919: I/LegacyVpnRunner(198): at com.android.server.connectivity.Vpn$LegacyVpnRunner.execute(Vpn.java:569)
07-18 15:09:00.919: I/LegacyVpnRunner(198): at com.android.server.connectivity.Vpn$LegacyVpnRunner.run(Vpn.java:447)
Try flashing DjnoxD's kernel
http://forum.xda-developers.com/showthread.php?p=24560941
sent from xda app. it's all good. flash a custom rom. you will thank yourself.
mrcorey said:
Try flashing DjnoxD's kernel
http://forum.xda-developers.com/showthread.php?p=24560941
sent from xda app. it's all good. flash a custom rom. you will thank yourself.
Click to expand...
Click to collapse
Thx. I'm going to try that.
[Edit]
Unfortunately it still doesn't work . DJNoXD's shows exactly the same error with hephappy's ICS.
I've enclosed the working VPN log with stock GB kernel and ROM (works only with encryption OFF).
I really hope developers can fix this problem in the next kernels / roms.