The below guide is targeted mainly for E4GT owners but has been found to help other Samsung devices as well.
In ICS the file has been changed to the standard wpa_supplicant.conf in /data/misc/wifi. However, you cannot just copy the old bcm_supp.conf data in here as the device id has also changed.
For all cases where you see something in < > you need to replace it with your information in quotes. Example "MySSID", etc.
ICS Sample
Here's what's working as of now on FD26 (11:40 CDT - Restored P2P parameters):
Note: As of FE14 please remove the eapol_flags=2 as it caused a bootloop issue.
Code:
ctrl_interface=wlan0
driver_param=use_p2p_group_interface=1
update_config=1
device_name=Wireless Client
manufacturer=Samsung Electronics
device_type=1-0050F204-1
p2p_listen_reg_class=81
p2p_listen_channel=1
p2p_oper_reg_class=81
p2p_oper_channel=11
[B]ap_scan=2
country=US[/B]
network={
ssid=[B][I]<SSID>[/I][/B]
scan_ssid=1
key_mgmt=IEEE8021X
group=WEP104 WEP40
auth_alg=OPEN SHARED
eap=PEAP
phase1="peapver=0"
identity=[B][I]<ID>[/I][/B]
password=[B][I]<PW>[/I][/B]
phase2="auth=MSCHAPV2"
[B]eapol_flags=2[/B]
}
GB Sample - bcm_supp.conf
Working Sample for GB/EL29:
Code:
ctrl_interface=eth0
update_config=1
device_name=Wireless Client
manufacturer=Samsung Electronics
device_type=1-0050F204-1
network={
ssid=[B][I]<SSID>[/I][/B]
group=WEP104 WEP40
auth_alg=OPEN SHARED
scan_ssid=1
key_mgmt=IEEE8021X
eap=PEAP
phase1="peapver=0"
identity=[B][I]<ID>[/I][/B]
password=[B][I]<PW>[/I][/B]
phase2="auth=MSCHAPV2"
priority=2
}
Eduroam Users:
Please try adding these two lines first to your configuration file before trying anything:
Code:
ap_scan=2
country=<ISO Country Code - US,GB,DE,FR,etc. - [B]No Quotes[/B]>
Please refer to above for placement. If this does not work then please proceed with modifying network settings as mentioned above.
Thanks to fellow posters, such as kobridge, sfhub and others for continuing to suggest ways to keep poking at this!
Did you have a chance to check /system/etc/wifi/wpa_supplicant.conf?
/system/etc/wifi/wpa_supplicant.conf
I'm guessing this is the template version that builds when not found:
Code:
[email protected]:/system/etc/wifi # cat wpa_supplicant.conf
cat wpa_supplicant.conf
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
p2p_listen_reg_class=81
p2p_listen_channel=1
p2p_oper_reg_class=81
p2p_oper_channel=11
GB bcm_supp.conf
And for comparison here's my bcm_supp.conf before I went to ICS:
Please ignore the name bcm_good.conf as I always keep a good copy in /sdcard.
Code:
[email protected]:/system/etc/wifi # cat /sdcard/bcm_good.conf
cat /sdcard/bcm_good.conf
ctrl_interface=eth0
update_config=1
device_name=Wireless Client
manufacturer=Samsung Electronics
device_type=1-0050F204-1
network={
ssid="yyyyyyyyyy"
psk="yyyyyyyyyyyy"
key_mgmt=WPA-PSK
priority=1
}
network={
ssid="xxxxxxxxx"
group=WEP104 WEP40
auth_alg=OPEN SHARED
scan_ssid=1
key_mgmt=IEEE8021X
eap=PEAP
phase1="peapver=0"
identity="[email protected]"
password="xxxxxxxxxxxxxxx"
phase2="auth=MSCHAPV2"
priority=2
}
Just for kicks I tried renaming and dropping this one in as wpa_supplicant.conf - no change.
Not sure if you checked this thread - http://forum.xda-developers.com/showthread.php?t=1369856
I think it's the same issue.
A driver change would explain why the path changed as well - but I'm hoping this is a result of the leaks and will be resolved prior to OTA. If not then a big reason that I got this will be out.
Will probably pull the TAR for EL29 and see if I can find any differences... will pass on my findings here.
*Edit* OK, can't pull the ODIN .tar files where I'm at so I'll see if I can find it in Calk's EL29 build for now.
*Update 2* Driver dhd.ko is in the modem. Now I asked this before and supposedly modems are interchangeable. Will check again on using a GB modem with ICS but if good will try flashing EL29 modem and see if it fixes. Also changed /system/etc/wifi to EL29 contents.
Results #1
OK, here's what I did:
1) Replace /system/etc/wifi contents from FC22 with EL29 contents. (Includes 2 remounts to change to rw and back to ro)
2) Used ODIN to flash EL29 modem to replace driver.
3) Created /data/wifi directory and copied EL29 bcm_supp.conf there.
Turned back on. wpa_supplicant.conf was still the driver but was being rebuilt from bcm_supp.conf when I removed it. No change.
I just reversed #1 and flashed FC24 modem. I'm going to try rebuilding from scratch and see if it's just something in the config at this point.
Still trying...
Logcat significant events:
Code:
logcat -d
D/WifiService( 1883): setWifiEnabled: true
D/WifiService( 1883): ****************setWifiEnabled(), allowWifi***************
*true
D/WifiP2pService( 1883): P2pDisabledState{ what=131203 when=0 }
D/STATUSBAR-WifiController( 1993): Wifi state = 2
D/CommandListener( 1740): Trying to bring down wlan0
D/CommandListener( 1740): broadcast flag ignored
D/CommandListener( 1740): multicast flag ignored
D/STATUSBAR-WifiController( 1993): Wifi state = 3
D/STATUSBAR-QuickSettingButton( 1993): setActivateStatus(1) - 1:on, 2:off, 3:dim
E/WifiConfigStore( 1883): configuration found for missing network, ignored
D/WifiStatusReceiver( 3959): WIFI_STATE_ENABLED
E/wpa_supplicant( 4690): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/WifiStateMachine( 1883): Failed to set country code US
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-NO-C
I/wpa_supplicant( 4690): wlan0: Associated with
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
I/wpa_supplicant( 4690): EAP-MSCHAPV2: Authentication succeeded
I/wpa_supplicant( 4690): EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Complete
d
I/wpa_supplicant( 4690): wlan0: CTRL-EVENT-EAP-
W/wpa_supplicant( 4690): EAPOL: Failed to set WEP key to the driver.
More digging appears to indicate that this happening a lot with the 3.0 kernel - some fixes are out there for other Sammy devices. Again, hope that this is just a leak issue and that they will address this before OTA.
I'll post any more relevant updates as I get them.
Morning Update
Since it looks like this thread got quite a bit of reading I figure it wouldn't hurt to post an update.
First off, Wi-fi itself on FC24 radio and updated wpa_supplicant.conf is working fine for WPA-PSK. I've also ruled out the p2p comments in the configuration as these are part of the expanded support in the 3.0 kernel.
So I'm back to something with the driver and still trying to figure it out. Guess since Android never properly supported this PEAP/MSCHAPV2 configuration without editing (at least in my experience) it can't be affecting too many people. If anyone has a contact in Samsung you may want to pass this on to them and ask them to look at it.
I have not seen a problem with my WPA2 with caukens ICS 1.2
Is that simple WPA2 with password? If so I think I haven't had problems there either - it really seems to be with this WEP layered tunneling.
A little side note - a Cisco guy was in our office a few weeks ago and didn't know about this problem until his tablet couldn't connect to our Wi-Fi. Guess that most people are going away from the multi-layered authentication - at least using this combination.
garwynn said:
Guess since Android never properly supported this PEAP/MSCHAPV2 configuration without editing (at least in my experience) it can't be affecting too many people.
Click to expand...
Click to collapse
Can you direct me to instructions on how to edit this to work with PEAP/MSCHAPV2 in detail on EL29? My work uses this for our secure network and Android phones/tablets have never connected to it very consistently (it will if you sit still, but moving in and out of coverage or AP to AP is a nightmare). I haven't found anyone with much help. I'd love some detailed instructions. WebOS and iOS have figured out how to connect with ease.....just not Android.
mmark27 said:
Can you direct me to instructions on how to edit this to work with PEAP/MSCHAPV2 in detail on EL29? My work uses this for our secure network and Android phones/tablets have never connected to it very consistently (it will if you sit still, but moving in and out of coverage or AP to AP is a nightmare). I haven't found anyone with much help. I'd love some detailed instructions. WebOS and iOS have figured out how to connect with ease.....just not Android.
Click to expand...
Click to collapse
Here's what I did for EL29. You'll need to be rooted to do this:
1) Start ADB debug and type in SU to get superuser access.
2) cd /data/wifi
3) cat bcm_supp.conf > /sdcard/bcm_backup.conf
(Change from this command prompt window back to Windows)
4) Now use a hex editor to modify that file and add the following:
Code:
network={
ssid="[B]<Add SSID Here>[/B]"
group=WEP104 WEP40
auth_alg=OPEN SHARED
scan_ssid=1
key_mgmt=IEEE8021X
eap=PEAP
phase1="peapver=0"
identity="[B]ID here, usually network ID[/B]"
password="[B]Enter password here,normally network password[/B]"
phase2="auth=MSCHAPV2"
priority=[B]Use last number not assigned in other networks.[/B]
}
Save this as a file bcm_good.conf on the USB storage. (11GB partition)
Note: I have had it work sometimes by editing in Notepad, but I notice the hex editor always works. Line breaks appear to be the difference - you'll see a hex value 090A I believe between each line.
5) (On Phone) Turn off Wi-Fi now to replace the config file.
If you mounted the USB mass storage please also end this.
Now back to ADB Shell window:
6) rm bcm_supp.conf
7) cat /sdcard/bcm_good.conf > bcm_supp.conf
8) chmod 660 bcm_supp.conf (reset permissions)
9) chown system.wifi bcm_supp.conf (reset ownership)
Restart Wi-Fi and confirm connection. If it doesn't connect here you may need to tweak the settings slightly.
And for reference if anyone wants to know what options are in wpa_supplicant you can find them HERE. This does not include the p2p additions made available in the new 3.0 kernel.
Hope this helps! Good luck!
Worked great! Very detailed instructions. You rock!
Sent from my SPH-D710 using XDA
Follow Up
Since my MIL has my phone for a few more weeks I've been researching this further. I haven't found any case of ICS yet where this was working properly. A few posts talked about the MAC address not being correct but I have ruled this out in my case as the MAC address shows just as it always has.
Further searches found reports on Google Code but no fix. I find it hard to believe as devices start switching to ICS that this will remain unsolved.
Anyone that has experience with the Linux 3.0 kernel and/or wifi (particularly PEAP/MSCHAPV2) please feel free to throw in any suggestions to try and get this working again.
*removed - frustrated post*
Weekly Update
Sorry for clogging the thread but figure it doesn't hurt to share these findings. Have received a few PMs asking about this so obviously there are some reading up on it.
I flashed the nodata FD16 yesterday and dumped /system to /sdcard/sysFD16 and then thought more about sfhub's suggestion to check the wpa_supplicant binary. Thought this was in the modem so flashed EL29 modem and then dumped /system again but to /sdcard/sysEL29. Moved both to external_sd and brought the card to work since I can't bring the phone.
Got to work today, checked both out and they seem to match file for file. Dates are different but sizes are identical, which I didn't expect. Guess that means I should try pushing the full EL29 package, dump and compare again. (Will probably back everything up using TB though to save some of the headaches.)
I got to thinking and noticed in /system/etc/wifi the NVRAM_NET.txt file. Are these values are automatically applied when flashing through ODIN? I briefly noticed some values resembling these when looking through either ##DATA# or ##DEBUG# (don't remember which one) and will look again when have time. I know the device id changed in wpa_supplicant.conf, maybe it's looking for the wrong one still?
FD26 Update
As of FD26 I've noticed a new change, may have been since FC24 but wasn't able to test it at work.
The scan completes but now it doesn't even attempt to connect to the network! It seems like I've taken a step backwards
*Edit*
Found the problem - was failing due to the WPA-EAP in the key_mgmt section. That got me back to where I was.
Played around with it a little more and finally success! I'm on my network at work!
I'll be posting updates as I reintroduce the p2p strings, so long as they play nice.
Updated first post with a note covering FE14 and later (as of FE16).
HI,
In my case, i put
network={
ssid=<SSID>
scan_ssid=1
key_mgmt=IEEE8021X
group=WEP104 WEP40
auth_alg=OPEN SHARED
eap=PEAP
phase1="peapver=0"
identity=<ID>
password=<PW>
phase2="auth=MSCHAPV2"
eapol_flags=2
}
But, if you put <, dont work, you need put "
network={
ssid="SSID"
scan_ssid=1
key_mgmt=IEEE8021X
group=WEP104 WEP40
auth_alg=OPEN SHARED
eap=PEAP
phase1="peapver=0"
identity="ID"
password="PW"
phase2="auth=MSCHAPV2"
eapol_flags=2
}
This way it work´s....
Thanks so much for your help
Related
Basically, i'm looking for the file 'dev/tpa2018d1' or something along those lines, it might be called something slightly different. I'm not in a position where i can build the source so if anyone could do this for me, i would be incredibly grateful!!
Thanks!
may we ask what is it for =)
I am sure I can look around for you
Getting a volume hack working on the Nexus/Desire/Incredible. As they are running very similar firmware on very similar hardware it should be compatible across all 3 phones
tpa2018d1 controls speaker amplification on the Nexus/Desire but isn't present. I'm just hoping that the Incredible has it
I looked on my incredible and can't find such a file in /dev, or indeed any files beginning with the letters tpa.
i dont think we can get this file for you untill we have root..... but i will take a look and see what i can find.
here is what we have in /dev/
Code:
C:\AndroidSDK\tools>adb shell
$ ls /dev/
ls /dev/
cpuctl
msm_camera
mtd
ppp
input
vdec
oncrpc
network_throughput
network_latency
cpu_dma_latency
htc-portlist
btdiag
log
binder
device-mapper
akm8973_aot
akm8973_daemon
alarm
lightsensor
keychord
uinput
android_mtp_event
android_mtp_control
android_mtp_enable
android_mtp_tunnel
qct_diag_enable
diag_arm9
diag
android_adb_enable
android_adb
bma150
pmem_camera
pmem_adsp
pmem
kgsl
ashmem
cm3602
htc-acoustic
msm_qcelp_in
msm_aac_in
q6venc
msm_audio_ctl
msm_audio_route
msm_mp3
msm_pcm_in
msm_pcm_out
smem_log
qmi2
qmi1
qmi0
ttySA1
ttySA0
ttyHSUSB2
ttyHSUSB1
ttyHSUSB0
ptmx
console
tty
smd19
smd27
smd9
smd1
smd0
kmsg
urandom
random
full
zero
null
graphics
block
ttyHS0
ttyMSM0
socket
pts
$
Ah, that's a shame
It was worth a try though, thank you very much guys
I shall continue hunting and i'll let you know if i find anything!
Thanks again!!
Yea cant find them for you... yet
FWIW, I took a look at the output from dmesg and I think the first part of the file may be named tpa6130. I really have no idea. If this is irrelevant or unhelpful, please ignore this post. :]
Ok. I ran a full ls -R on the filesystem and found the following files containing the string tpa
/system/etc/TPA2018.csv
/sys/bus/i2c/drivers/tpa2018d1 (is a directory, contains uevent, unbind, bind)
/sys/bus/i2c/drivers/tpa6130 (is a directory, contains 0-0060, uevent, unbind, bind)
the CSV file contains the text
IncredibleC_20100104,,,,,,,,
TPA2018_MODE_OFF,1,a2,0,0,0,0,0,0
TPA2018_MODE_PLAYBACK,1,c2,20,1,0,0c,1e,c0
TPA2018_MODE_RINGTONE,1,c2,20,1,0,0c,1e,c0
TPA2018_MODE_VOICE_CALL,1,c2,20,1,0,0c,1e,c0
Let me know if any of the files in the i2c/drivers directories may be of use to you. I tried to pull one but got permission denied - the files themselves are chmoded to writable by owner (which is root) and readable by noone.
Has anyone compiled tun.ko under the 2.2 stock?
Bill T
I have TUN vermagic=2.6.32.15-g746f4f0
Since nobody seemed to have it
I compiled TUN from the HTC sources, It loads,
** BUT ** looks like it is creating the TUN device as /dev/tun
vpnc seems to be looking in /dev/net/tun
I Will get vpnc working on a rooted stock 2.2 if it kills me
# ls /system/lib/modules
sequans_sdio.ko
bcm4329.ko
tun.ko
# strings /system/lib/modules/tun.ko | grep vermagic
vermagic=2.6.32.15-g746f4f0 preempt mod_unload ARMv7
# lsmod
tun 10734 0 - Live 0xbf000000
Tun is attached
how do you get the source + compile tun.ko? i am using Fresh's 3.2.0.0 rom with the new HTC stock kernel that is supposed to save batter life. The kernel # is 2.6.32.15-g3a8614e
HTC EVO Source
When I build the HTC code - it did not completely build everything but it did go get past tun so that is all I needed
I did this under fedora linux
you can download the HTC EVO source here
http://developer.htc.com/
you will need the google android build here is the instruction page
http://source.android.com/source/download.html
the google android source download included prebuilt compile binaries for the cross compile. I had to add the directories to my path so make could find them.
needed to edit Makefile change
EXTRAVERSION = .15-
== to ==
EXTRAVERSION = .15-g746f4f0
then did a make -j4 and waited
Bill
btedeski said:
When I build the HTC code - it did not completely build everything but it did go get past tun so that is all I needed
I did this under fedora linux
you can download the HTC EVO source here
http://developer.htc.com/
you will need the google android build here is the instruction page
http://source.android.com/source/download.html
the google android source download included prebuilt compile binaries for the cross compile. I had to add the directories to my path so make could find them.
needed to edit Makefile change
EXTRAVERSION = .15-
== to ==
EXTRAVERSION = .15-g746f4f0
then did a make -j4 and waited
Bill
Click to expand...
Click to collapse
yikes... i do have a linux box but this seems like a huge task, any way you can build tun.ko for my kernel?
<< yikes... i do have a linux box but this seems like a huge task, any way you can build tun.ko for my kernel?
post your Kernel string here and I will see about doing it.
btedeski said:
<< yikes... i do have a linux box but this seems like a huge task, any way you can build tun.ko for my kernel?
post your Kernel string here and I will see about doing it.
Click to expand...
Click to collapse
Kernel Version:
2.6.32.15-g3a8614e
[email protected] #7
don't worry if you don't have time.. thanks if you do!
I am able to connect from the EVO to the work Cisco 3030 VPN
concentrator (I am the concentrator admin) so I am able to see the connection on the 3030 as well.
The 3030 sees the conneciton
I have been able to connect in the following modes
IPSec/UDP 3DES-168
IPSec 3DES-168
IPSec/NAT-T 3DES-168
But the VPN concentrator is reporting 0 bytes sent or received,
seeing the following messages when I start vpnc
/data/data/org.codeandroid.vpnc_frontend/files/vpnc --natt-mode force-natt /etc/
vpnc/vpnc.conf
Usage: ip link set DEVICE { up | down |
arp { on | off } |
dynamic { on | off } |
multicast { on | off } |
allmulticast { on | off } |
promisc { on | off } |
trailers { on | off } |
txqueuelen PACKETS |
name NEWNAME |
address LLADDR | broadcast LLADDR |
mtu MTU }
ip link show [ DEVICE ]
/etc/vpnc/vpnc-script: cannot create : directory nonexistent
backing up dns and resolve.conf
/etc/vpnc/vpnc-script: cannot create /etc/vpnc/dns1.txt: read-only file system
/etc/vpnc/vpnc-script: cannot create /etc/vpnc/dns2.txt: read-only file system
cp: cannot stat '/etc/resolv.conf': No such file or directory
vpnc-script ran to completion
VPNC started in background (pid: 4079)...
#
busybox route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
63.117.98.165 174.146.29.245 255.255.255.255 UGH 0 0 0 rmnet0
174.146.29.244 * 255.255.255.252 U 0 0 0 rmnet0
198.182.130.128 * 255.255.255.128 U 0 0 0 tun0
default * 0.0.0.0 U 0 0 0 tun0
busybox ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8439 errors:0 dropped:0 overruns:0 frame:0
TX packets:8439 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:507599 (495.7 KiB) TX bytes:507599 (495.7 KiB)
rmnet0 Link encap:Ethernet HWaddr 42:9C7:E2:B3:C4
inet addr:174.146.29.246 Bcast:174.146.29.247 Mask:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1472 Metric:1
RX packets:1165 errors:0 dropped:0 overruns:0 frame:0
TX packets:1686 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:538348 (525.7 KiB) TX bytes:234465 (228.9 KiB)
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-00
inet addr:198.182.130.158 P-t-P:198.182.130.158 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
#
Can anyone get vpn working at all?
tun vermagic=2.6.32.15-g3a8614e
vermagic=2.6.32.15-g3a8614e preempt mod_unload ARMv7
see attached zip file
btedeski said:
vermagic=2.6.32.15-g3a8614e preempt mod_unload ARMv7
see attached zip file
Click to expand...
Click to collapse
What does this do?
me too
First, thanks for the compiled tun.ko for the stock ROM. I just got my Evo yesterday and am diving into Android for the first time, and have gotten rooted and VPNC installed and connected, but I get 0 bytes transferred on my Cisco ASA and no actual connection on the Evo. So I'm in the same boat, and from looking around, it doesn't look like anybody has gotten this working on 2.2 stock. I don't know enough to solve the problem myself, but just wanted to confirm that I have the same issue.
VPNC Working
So... I have a workaround that does seem to work with 2.2 Froyo. I tried this on King's kernel, and netarchy's kernels (both worked). I then loaded the tun.ko from a few posts above, and insmod'd it to work for Fresh 3.2.0.0 (with the new HTC Kernel)
So, here's what you do...
-Connect using VPNC (should show connected, but not allow tunneling)
-Issue the following commands
3G: "ip rule del from all lookup gprs"
Wifi: "ip ru del table wifi"
I used the application GScript Lite to send the commands
Then tunneling works!
I have gotten the connection to work on my Evo running Fresh stock 3.28 ROM, using the commands above. However, when I disconnect the phone freezes and I have to pull the battery to reset. Any ideas of what would be causing this?
davidfretz said:
I have gotten the connection to work on my Evo running Fresh stock 3.28 ROM, using the commands above. However, when I disconnect the phone freezes and I have to pull the battery to reset. Any ideas of what would be causing this?
Click to expand...
Click to collapse
Mine is doing that also. Maybe the kernel. I tried to logcat it but dont see anything because that freezes also
Don't suppose you could post one for 2.6.32.15-gb7b01d1 ? Pretty please?
TUN vermagic=2.6.32.15-gb7b01d1 preempt mod_unload ARMv7
[email protected] net]$ strings tun.ko | grep magic
vermagic=2.6.32.15-gb7b01d1 preempt mod_unload ARMv7
The attached zip file contains tun.ko
This is the supersonic-2.6.32.15-g746f4f0 but with the compile string modified to be gb7b01d1
this should work as long as gb7b01d1 and g746f4f0 are close.
Bill T
VPNC Disconnect -- Phone Freezes
davidfretz said:
I have gotten the connection to work on my Evo running Fresh stock 3.28 ROM, using the commands above. However, when I disconnect the phone freezes and I have to pull the battery to reset. Any ideas of what would be causing this?
Click to expand...
Click to collapse
Hi there, did you ever figure out freezing issue while disconnects? Any work-around or help .. . much appreciated...
hits100 said:
Hi there, did you ever figure out freezing issue while disconnects? Any work-around or help .. . much appreciated...
Click to expand...
Click to collapse
I downloaded the source for VPNC and ran it on my EVO in debug mode. I can tell you that the problem is not with VPNC Android client directly, it actually relates to the VPNC process running in the background.
Basically.. when you run the Android client, it just acts as a simple GUI that starts/stops this VPNC process (native C++ code). The freeze occurs when that VPNC process tries getting killed. So when you click "Disconnect" from your phone, VPNC (Android client) issues a linux shell command for "kill" that is supposed to terminate the VPNC process.
I wasn't able to determine, because of my lack of C++ skillz, what the VPNC process is doing that is causing the freeze. Maybe it's trying to close tunnels that don't exist? I don't know.. I do know there is a stop command in the vpnc-script file that comes with VPNC, but I couldn't tell if that was ever getting called or what. I suppose the next step would be to add some sort of output to that script file to see if that is being called. I have a feeling it's closely related to the commands issued to get the VPN connection working. Maybe there are some commands to close the tunnels THEN kill VPNC process.. never got that far, but I hope this helps any other dev.
If anyone wants to know exactly where it crashes in the Android code, it's in the VpncProcessHandler.java file on line 238. In the "disconnect" fxn.
drizkol said:
I downloaded the source for VPNC and ran it on my EVO in debug mode. I can tell you that the problem is not with VPNC Android client directly, it actually relates to the VPNC process running in the background.
Basically.. when you run the Android client, it just acts as a simple GUI that starts/stops this VPNC process (native C++ code). The freeze occurs when that VPNC process tries getting killed. So when you click "Disconnect" from your phone, VPNC (Android client) issues a linux shell command for "kill" that is supposed to terminate the VPNC process.
I wasn't able to determine, because of my lack of C++ skillz, what the VPNC process is doing that is causing the freeze. Maybe it's trying to close tunnels that don't exist? I don't know.. I do know there is a stop command in the vpnc-script file that comes with VPNC, but I couldn't tell if that was ever getting called or what. I suppose the next step would be to add some sort of output to that script file to see if that is being called. I have a feeling it's closely related to the commands issued to get the VPN connection working. Maybe there are some commands to close the tunnels THEN kill VPNC process.. never got that far, but I hope this helps any other dev.
If anyone wants to know exactly where it crashes in the Android code, it's in the VpncProcessHandler.java file on line 238. In the "disconnect" fxn.
Click to expand...
Click to collapse
Yeah, It's not front-end. Front-End application only sends kill command to vpnc process. If I do that same from terminal, it still freezes the system. It's something with kernel..
12.29.10
HOW TO INSTALL VIDEO
http://www.youtube.com/watch?v=833C5nvuU4Y
==========================================================================
12.29.10
HOW TO CREATE FAT32 AND EXT2 VIDEO
http://www.youtube.com/watch?v=b6ID9jWXqVI
=========================================================================
12.29.10
GINGERBREAD FIRST LOOK VIDEO
http://www.youtube.com/watch?v=AQvZpM4HuI0
===========================================================================
12.29.10
hi, guys. i know a few people want to explore gingerbread. i know that xda version is not out yet, but i Mod this build (from neopeek) for you to try. this is ext2. this one have all the 3d driver plus gralloc for more power.
NO O/C
NEOCORE 30.1 FPS. no textures
FPS2D 30
QUADRANT 560. no textures
GETTING WITH A FULL CHARGE 12HRS
how install.
1-create 1-fat32 2-ext2 310mb. I WILL POST A VIDEO. HOW TO DO THIS
2- WM GO TO SD CARD/NPKINSTALL/PICK YOUR INSTALL STARTUP. YOU CAN USE MY (SPRINT USER)
3- RUN HARET
HOW TO RUN GINGERBREAD
0- WM PLUG YOUR CHARGER.
1- GO TO SD CARD PICK STARTUP. OR USE MY (SPRINT USER.LOCATION IN PROFRAM FILE FOLDER)
2-RUN HARET
setting. very important
1- see the welcome screen don't touch the phone wait for green light
2- don't sync yet. skip everything get to home screen. i add it launcher. pick that.
3- go to wireless & networks/mobiles networks/access point names/menu key and add apn
4- call setting if you have sprint
5- sound. get your sound and ring tone ready
6- location & security setting. unchecked gps satellites.
7- applications. check unknown sources
8- NOW YOU CAN SYNC WITH GOOGLE.
9-let the phone sync. see the green light
10-open all apps. then reboot your phone.
I'M STILL WORKING ON A FEW THINGS FOR MORE STABILITIES.
GOOD LUCK
THANKS
http://www.megaupload.com/?d=AE2V72XQ
tiad8 said:
hi, guys. i know a few people want to explore gingerbread. i know that xda version is not out yet, but i Mod this build (from neopeek) for you to try. this is ext2. this one have all the 3d driver plus gralloc for more power.
NO O/C
NEOCORE 30.1 FPS
FPS2D 30
QUADRANT 560
GETTING WITH A FULL CHARGE 12HRS
how install.
1-create 1-fat32 2-ext2 310mb. I WILL POST A VIDEO. HOW TO DO THIS
2- WM GO TO SD CARD/NPKINSTALL/PICK YOUR INSTALL STARTUP. YOU CAN USE MY (SPRINT USER)
3- RUN HARET
HOW TO RUN GINGERBREAD
0- WM PLUG YOUR CHARGER.
1- GO TO SD CARD PICK STARTUP. OR USE MY (SPRINT USER.LOCATION IN PROFRAM FILE FOLDER)
2-RUN HARET
setting. very important
1- see the welcome screen don't touch the phone wait for green light
2- don't sync yet. skeep everthing get to home screen. i add it launcher. pick that.
3- go to wireless & networks/mobiles netwotks/access point names/menu key and add apn
4- call setting if you have sprint
5- sound. get your sound and ring tone ready
6- location & secury setting. uncheck gps satellites.
7- applications. check unknown sources
8- NOW YOU CAN SYNC WITH GOOGLE.
9-let the phone sync. see the green light
10-open all apps. then reboot your phone.
I'M STILL WORKING ON A FEW THINGS FOR MORE STABILITIES.
GOOD LUCK
THANKS
http://www.megaupload.com/?d=39511890
Click to expand...
Click to collapse
Neocore = 30.1? Is that a typo? If that is correct that is an amazing improvement!
pdawg17 said:
Neocore = 30.1? Is that a typo? If that is correct that is an amazing improvement!
Click to expand...
Click to collapse
he should write that there are no textures in Neocore gingerbread.
perern said:
he should write that there are no textures in Neocore gingerbread.
Click to expand...
Click to collapse
That'll do it...thanks...
perern said:
he should write that there are no textures in Neocore gingerbread.
Click to expand...
Click to collapse
Oh. Sorry, forgot. Ill update the first post
sprint touch pro 2
You say :
"1-create 1-fat32 2-ext2 310mb. I WILL POST A VIDEO. HOW TO DO THIS"
But I don't understand ! We must creat a file which name system.ext2 with ImageMaker and put the file in the root ?
Damien50 said:
You say :
"1-create 1-fat32 2-ext2 310mb. I WILL POST A VIDEO. HOW TO DO THIS"
But I don't understand ! We must creat a file which name system.ext2 with ImageMaker and put the file in the root ?
Click to expand...
Click to collapse
no. you have to create 2 partition
1- fat32
2- ext2
when i get home i will upload the video.
thanks
tiad8 said:
no. you have to create 2 partition
1- fat32
2- ext2
when i get home i will upload the video.
thanks
Click to expand...
Click to collapse
ah !! ok I waiting for your video thanks ^^
me too and please post another video with gingerbread in rhodium and thanks
Can we try it on Topaz?
ext2 310mb- Does the ext2 size is strictly like you metioned?
Thanks.
ok, guys
i'm uploading 3 video on how to. right now.
1- stabilities. "very stable here"
2- how to create fat32 and ext2
3- how to install
thanks
xrshwy said:
Can we try it on Topaz?
ext2 310mb- Does the ext2 size is strictly like you metioned?
Thanks.
Click to expand...
Click to collapse
1-Can we try it on Topaz? YES
2-ext2 310mb- Does the ext2 size is strictly like you metioned? EXT2 WITH 310 MB IT PERFECT. I DON'T GET FC OR RANDOM REBOOT WITH 310MB. DON'T KNOW WHY BUT FOR ME IT'S PERFECT SIZE. TRY IT
THANKS
this is working great!!!fast,solid,stable ThankYou
First post updated
gingerbread first look video
First post updated
how to create fat32 and ext2 video
thanks
First post updated
how to install video
thanks
can your wifi work? I can scan APs, but can not connect.
D/GTalkService( 1415): [GTalkService.17] account missing
D/GTalkService( 1415): [GTalkService.18] account missing
V/WifiMonitor( 1304): Event [Authentication with 00:11:50:c8:26:63 timed out.]
V/WifiMonitor( 1304): Event [CTRL-EVENT-STATE-CHANGE id=0 state=0]
V/WifiMonitor( 1304): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
V/WifiStateTracker( 1304): Changing supplicant state: ASSOCIATING ==> DISCONNECTED
V/WifiStateTracker( 1304): Changing supplicant state: DISCONNECTED ==> SCANNING
V/WifiMonitor( 1304): Event [Trying to associate with 00:11:50:c8:26:63 (SSID='angel' freq=2412 MHz)]
V/WifiMonitor( 1304): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3]
V/WifiStateTracker( 1304): Changing supplicant state: SCANNING ==> ASSOCIATING
E/Tethering( 1304): attempting to remove unknown iface (usb0), ignoring
D/WifiService( 1304): ACTION_BATTERY_CHANGED pluggedType: 0
E/Tethering( 1304): attempting to remove unknown iface (usb0), ignoring
D/WifiService( 1304): ACTION_BATTERY_CHANGED pluggedType: 0
D/WifiStateTracker( 1304): Reset connections and stopping DHCP
D/WifiStateTracker( 1304): Disabling interface
D/NetworkStateTracker( 1304): setDetailed state, old =DISCONNECTED and new state=DISCONNECTED
V/WifiMonitor( 1304): Event [Authentication with 00:11:50:c8:26:63 timed out.]
V/WifiMonitor( 1304): Event [CTRL-EVENT-STATE-CHAN
SPRINT TOUCH PRO 2 (RHOD400)
Wifi cann't work, I change to new kernel-1245, wifi will be connected but the performance is not good.
FPS2D-31
GOOD!
Thanks.
thanks it's works ^^
I will test it today
Back to FRX03, Waiting new kernel that comera fixed.
After upgrading to stock 4.2 , I cannot connect to my office enterprise network ( WPA2-EAP ) using LEAP
It remains in a "connecting" status for a while, than disconnects.
Credentials (i.e. userid/passwd ) are obviously ok.
I guess it's a 4.2 issue because reverting to 4.1.2 (nandroid) I can connect again.
Home wifi (wpa2-psk) works with 4.2 , anyway.
Does anybody have the same issue?
If someone have a working LEAP Wifi configuration, could please provide his "wpa_supplicant.conf" configuration ( /data/misc/wifi ) or provide any useful hint ?
Thanks in advance.
Just wanted to confirm I have had the same experience. I have been using Advanced Leap WIFI from oneguyinabasement.com successfully for months. My 4.1.2 device (phone) still connects fine.
Regretting pushing upgrade on my Nexus 7, I would (and might have to) trade the excitement of the Android loader for a working tablet.
Hopefully this will be a short term blip, not a barrier to all the 4.2 goodness for us stuck in a locked down enterprise.
kliw said:
After upgrading to stock 4.2 , I cannot connect to my office enterprise network ( WPA2-EAP ) using LEAP
It remains in a "connecting" status for a while, than disconnects.
Credentials (i.e. userid/passwd ) are obviously ok.
I guess it's a 4.2 issue because reverting to 4.1.2 (nandroid) I can connect again.
Home wifi (wpa2-psk) works with 4.2 , anyway.
Does anybody have the same issue?
If someone have a working LEAP Wifi configuration, could please provide his "wpa_supplicant.conf" configuration ( /data/misc/wifi ) or provide any useful hint ?
Thanks in advance.
Click to expand...
Click to collapse
Same Issue
Hi,
I Have same issue with my Enterprise Wifi since I upgraded My Galaxy S III to Android Revolution 16 (4.1.2)
Before, I used to connect with leap wifi free (Why Android does not provide a native solution ???)
But I get an authentication error, and, of course, my credentials are fine.
Seems to be an Adroid 4.2 Issue : on android google bug tracker
Same issue here, Galaxy S3 with 4.1.2 Custom Rom, no wifi.
wednesday13 said:
Same issue here, Galaxy S3 with 4.1.2 Custom Rom, no wifi.
Click to expand...
Click to collapse
I encounted same issue, Galaxy S3 with 4.1.2 LIDROID V8.1 ROM, only found LEAP protocol has this problem so far.
Disappointed
I should have found this post and hold off upgrade to 4.2.1, when I came to my office this morning and can not connect to LEAP wifi anymore.
Same here.
Samsung galaxy S3 with 4.1.2 last stock rom ELL5.
No solution today - I've found an issue tracker in google http://code.google.com/p/android/issues/detail?id=34212
I'm investigating to use a modified wpa_supplicant
I have fixed this by copying etc/wifi folder from last version
Sent from my GT-I9300 using Tapatalk 2
wednesday13 said:
I have fixed this by copying etc/wifi folder from last version
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
wednesday13, Can you provide more information?
When I look at /etc/wifi on my 4.2 Nexus 7, I only see 1 file, wpa_supplicant.conf, and this file has the following 5 lines:
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
It would be great to know what you see, and especially if there's some simple difference.
Thanks! -David
In my galaxy s3,I just copied the whole folder from 4.1.1 to 4.1.2. It works on mine
Sent from my GT-I9300 using Tapatalk 2
I have the same problem since updated my Galaxy Note 10.1 form 4.0.4 to 4.1.1.
two days ago.
wednesday13 said:
In my galaxy s3,I just copied the whole folder from 4.1.1 to 4.1.2. It works on mine
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I understand. However, I no longer have a 4.1.1 to copy from, so I'm asking what files you now have in your /etc/wifi folder, and if you have only wpa_supplicant.conf (as I do), how it differs from the version I have. Perhaps with this information we can figure out how to fix those of us who have already updated and don't have the old configuration.
Thanks again! -David
I would like to find the answer to this problem. I have been compiling, configuring, and using wpa_supplicant with LEAP for many years, and am willing to do the investigation into what changed between Android 4.1.x and 4.2.x. However, I am new to Android and don't have a lot of resources available, so I need some help from someone who still has LEAP access working on 4.1.
For background, I have a rooted Nexus 7 with Android 4.2, running Terminal Emulator and BusyBox. Below is a console log of commands I have executed on my system. What I'd really like is for someone who is running 4.1 and has LEAP working (an IBMer would be ideal) and who has root access to execute the same set of commands and post the output. (I have added some blank lines for readability and removed some output lines not germane to the problem.)
==========================================================================================
[email protected]:/ # ps | grep wpa
wifi 578 1 2744 732 c0112160 401c010c S /system/bin/wpa_supplicant
[email protected]:/ # ls -al /system/bin/wpa_supplicant
-rwxr-xr-x root shell 670356 2012-12-12 11:24 wpa_supplicant
[email protected]:/ # /system/bin/wpa_supplicant -v
wpa_supplicant v2.0-devel-4.2
Copyright (c) 2003-2012, Jouni Malinen <[email protected]> and contributors
[email protected]:/ # uname -a
Linux localhost 3.1.10-g22b4fcd #1 SMP PREEMPT Fri Nov 2 10:55:26 PDT 2012 armv7l GNU/Linux
1|[email protected]:/ # find / -iname wpa_supp*
/system/bin/wpa_supplicant
/system/etc/wifi/wpa_supplicant.conf
/data/misc/wifi/wpa_supplicant.conf
[email protected]:/ls -al /wifi/wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf
-rw-r--r-- root root 77 2012-06-25 18:38 wpa_supplicant.conf
-rw-rw---- system wifi 3019 2012-12-26 19:12 wpa_supplicant.conf
[email protected]:/ # cat /system/etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
[email protected]:/ # cat /data/misc/wifi/wpa_supplicant.conf
update_config=1
device_name=nakasi
manufacturer=asus
model_name=Nexus 7
model_number=Nexus 7
serial_number=015d24a425080c1b
device_type=1-0050F204-1
config_methods=physical_display virtual_push_button keypad
... [other network stanzas removed for brevity] ...
network={
ssid="IBM"
scan_ssid=1
key_mgmt=WPA-EAP
eap=LEAP
identity="xxxxxxxxxxxxxxxxxxx"
password="xxxxxxxxxxxxxxxxxxx"
}
[email protected]:/ # logcat | grep wpa
... [unnecessary lines deleted]...
I/wpa_supplicant( 578): wlan0: CTRL-EVENT-SSID-REENABLED id=36 ssid="IBM"
I/wpa_supplicant( 578): wlan0: Trying to associate with 18:33:9d:a0:e4:01 (SSID='IBM' freq=2462 MHz)
I/wpa_supplicant( 578): wlan0: Associated with 18:33:9d:a0:e4:01
I/wpa_supplicant( 578): wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
I/wpa_supplicant( 578): wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=17
I/wpa_supplicant( 578): wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 17 (LEAP) selected
I/wpa_supplicant( 578): wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
I/wpa_supplicant( 578): wlan0: Authentication with 18:33:9d:a0:e4:01 timed out.
I/wpa_supplicant( 578): wlan0: CTRL-EVENT-DISCONNECTED bssid=18:33:9d:a0:e4:01 reason=3 locally_generated=1
I/wpa_supplicant( 578): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=36 ssid="IBM" auth_failures=2 duration=20
...[unnecessary lines deleted]...
==============================================================================
Another note: The IBM stanza in my wpa_supplicant.conf file is identical to the one that works for my laptop running OpenSUSE Linux on the same network.
Depending on the 4.1 output, it might also be interesting to try the version of wpa_supplicant running on 4.1 under 4.2 to see what would happen.
Thanks for any help! -David
Hi, Same issue here, except that my connection using leap wifi free stopped working when I migrated to 4.1.2, not 4.2. other symptoms seem to be the same. Unfortunately i do not have the older files.
wednesday13 said:
In my galaxy s3,I just copied the whole folder from 4.1.1 to 4.1.2. It works on mine
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I've just wpa_supplicant.conf and bcmdhd.cal inside that directory, and they are the same in 4.2.1 and in 4.1.2 .
Do you have other files ?
davidapease said:
Depending on the 4.1 output, it might also be interesting to try the version of wpa_supplicant running on 4.1 under 4.2 to see what would happen.
Click to expand...
Click to collapse
in a few days I'll back to work and I'll give a try.
David,
I am IBMer and want to get this fix as well, however when I did your command sequence, several commands are not found (grep, uname, etc)
What terminal emulator do you use ? I use Android Terminal Emulator by Jack Paelvich in Google Play store. My device is Galaxy Nexus, rooted, with Jellybeam 4.1.2. I have upgraded to 4.2.x, falled back to 4.1.2 after realised LEAP wifi is broken.
EDIT : ignore it, just installed busybox as well, it works ok now. I've posted the log in Google issue# 40023 http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=40023
LEAP working on Android 4.2
I have successfully gotten LEAP working on Android 4.2 by running the 4.1.2 version of wpa_supplicant. My steps for doing this are detailed here:
code.google.com/p/android/issues/detail?id=40023#c43
(Sorry, I'm too junior to post a proper URL.)
Have fun, and good luck!
-David
davidapease said:
I have successfully gotten LEAP working on Android 4.2 by running the 4.1.2 version of wpa_supplicant. My steps for doing this are detailed here:
code.google.com/p/android/issues/detail?id=40023#c43
(Sorry, I'm too junior to post a proper URL.)
Have fun, and good luck!
-David
Click to expand...
Click to collapse
The 4.1.2 version of wpa_supplicant is here http://snk.to/f-cu3a753u , if you don't want download a full image to extract it
The method posted by David works perfectly :good:
After installing last XXELLC on my G-S3 I930 - version 4.1.2 CSC XEF, I can't connect to LEAP WIFI.
I've also tested my Notes 10.1 tablet with 4.1.1 and it's not working.
part of logcat are here
I/wpa_supplicant( 8893): State: DISCONNECTED -> SCANNING
I/wpa_supplicant( 8893): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00
I/wpa_supplicant( 8893): Scan requested (ret=0) - scan timeout 30 seconds
I/wpa_supplicant( 8893): nl80211: Received scan results (3 BSSes)
I/wpa_supplicant( 8893): Trying to associate with 00.21.70 (freq=5180 MHz rssi=-79dBm)
I/wpa_supplicant( 8893): 49424D
I/wpa_supplicant( 8893): ASSOC when wpa_state = 3, do_assoc = 0, reassociate = 0
I/wpa_supplicant( 8893): State: SCANNING -> ASSOCIATING
I/wpa_supplicant( 8893): CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=00.21.70
I/wpa_supplicant( 8893): Start Assoc status = [0] !!!!!
I/wpa_supplicant( 8893): CTRL-EVENT-ASSOC-REJECT bssid=00.21.70 status_code=13
E/wpa_supplicant( 8893): Retrying assoc Iteration:1
I/wpa_supplicant( 8893): State: ASSOCIATING -> DISCONNECTED
I/wpa_supplicant( 8893): CTRL-EVENT-STATE-CHANGE id=6 state=0 BSSID=00.21.70
I/wpa_supplicant( 8893): 49424D
I/wpa_supplicant( 8893): State: DISCONNECTED -> SCANNING
Click to expand...
Click to collapse
One thing keep users away from running LolliPop on HOX: Seemingly random data disconnects.
I found a way to replicate the issue:
- Make sure you have internet on gsm (wifi off)
- Enable wifi, wait for full connectivity
- Enter AirPlane mode
- Toggle AP mode off
- Wait for wifi connectivity
- disable wifi
My phone will not connect 10-50% of the time - enough to make experiments.
One interesting observation: During no connection, just by entering "Phone info" (*#*#4696#*#*), radio get initialized.
From some of the logs it looks like android just reuse old data, but forget to initialize radio with it (or maybe ril don't understand?).
There are also some interesting Exceptions here and there.
HERE are two logs from SlimLP and two from CM12.1
One log wil successfully connect after wifi off, one will not.
I believe these logs should be enough to at least point to the root cause.
We simply need a wizard with radio/connectivity magic skills. @Thömy @eyosen @Lloir @Demetris or
anyone knowing such a wizard, please summon one.
Do you know if hox + has the same issue?
Demetris said:
Do you know if hox + has the same issue?
Click to expand...
Click to collapse
@Lloir will know I'm sure.
Pure-AOSP and OMNI have a few patches, that is not in CM and Slim. Looks promising, currently compiling omni, hope I can check tonight.
Edit: Need more work on wifi and SIM
teemo said:
@Lloir will know I'm sure.
Pure-AOSP and OMNI have a few patches, that is not in CM and Slim. Looks promising, currently compiling omni, hope I can check tonight.
Edit: Need more work on wifi and SIM
Click to expand...
Click to collapse
You might be kinda glad to know, a simular issue affects The Nexus 6 and some other HTC devices.
Demetris said:
Do you know if hox + has the same issue?
Click to expand...
Click to collapse
Yes
teemo said:
@Lloir will know I'm sure.
Pure-AOSP and OMNI have a few patches, that is not in CM and Slim. Looks promising, currently compiling omni, hope I can check tonight.
Edit: Need more work on wifi and SIM
Click to expand...
Click to collapse
Not sure why no one has taken my Android 4.4 branch of pure aosp and thrown a build up on here, (yes I broke it slightly easy enough to fix though)
Right now my time with the X+ is shortend by the need to work on the g620_a2/snapto myself. Can't let thoemy do all the work. Just tag me in a post or something if you need me, I get email notifs
From cm-wifi-off-no-net.log
Code:
D/ConnectivityService( 551): Setting MTU size: rmnet0, 1500
D/ConnectivityService( 551): Adding Route [0.0.0.0/0 -> 10.129.168.227 rmnet0] to network 106
E/Netd ( 179): netlink response contains error (Network is unreachable)
E/ConnectivityService( 551): Exception in addRoute for gateway: java.lang.IllegalStateException: command '151 network route add 106 rmnet0 0.0.0.0/0 10.129.168.227' failed with '400 151 addRoute() failed (Network is unreachable)'
And the when it works:
Code:
D/ConnectivityService( 551): Setting MTU size: rmnet0, 1500
D/ConnectivityService( 551): Adding Route [0.0.0.0/0 -> 10.164.14.213 rmnet0] to network 109
D/ConnectivityService( 551): Setting Dns servers for network 109 to [/194.239.134.83, /193.162.153.164]
Please post the output of "netcfg" and "ip route" for the working and not working case. I don't know what's causing the first to fail and the other one to succeed. There don't seem to be obvious differences besides the IP and gateway addresses. There was an "Android 5 cannot connect to networks with misconfigured subnet masks" issue (https://code.google.com/p/android/issues/detail?id=92646) but that should be fixed in 5.1.
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
Oh, there's a patch available. I should read threads more closely.
Thömy said:
From cm-wifi-off-no-net.log
Code:
D/ConnectivityService( 551): Setting MTU size: rmnet0, 1500
D/ConnectivityService( 551): Adding Route [0.0.0.0/0 -> 10.129.168.227 rmnet0] to network 106
E/Netd ( 179): netlink response contains error (Network is unreachable)
E/ConnectivityService( 551): Exception in addRoute for gateway: java.lang.IllegalStateException: command '151 network route add 106 rmnet0 0.0.0.0/0 10.129.168.227' failed with '400 151 addRoute() failed (Network is unreachable)'
And the when it works:
Code:
D/ConnectivityService( 551): Setting MTU size: rmnet0, 1500
D/ConnectivityService( 551): Adding Route [0.0.0.0/0 -> 10.164.14.213 rmnet0] to network 109
D/ConnectivityService( 551): Setting Dns servers for network 109 to [/194.239.134.83, /193.162.153.164]
Please post the output of "netcfg" and "ip route" for the working and not working case. I don't know what's causing the first to fail and the other one to succeed. There don't seem to be obvious differences besides the IP and gateway addresses. There was an "Android 5 cannot connect to networks with misconfigured subnet masks" issue (https://code.google.com/p/android/issues/detail?id=92646) but that should be fixed in 5.1.
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
Oh, there's a patch available. I should read threads more closely.
Click to expand...
Click to collapse
Not sure what patch you refer to. I found none that helps us.
Here is the output. The script just run "netcfg && ip route".
There are both routed and unrouted entries.