Develop Bugs

[Q] DHCP Lease very short

Hi there
My IP adress keeps on changing on my Android (Cyanogen 6.1.1) Desire and so I keep on hopping between different IP addresses. The IP adress of the only other system on my network has not changed.
I would prefer not to use a static address but to understand and fix the cause of this. I have a laptop which does'nt hop around so frequently so
I think it must be related to a phone/Android setting but so far i've been unable to find out where this is configured.
My link speed is 54 Mbps so I have a good connection to my wireless router.
How can I fix this ? Perhaps I just need to install an extra application.
Elixir displays the lease in binary for some reason, 10101000110000000 (86400 base 10). 86400 seconds is a lease time of 1 day.
And this is confirmed on the OS itself.
Code:
# getprop dhcp.eth0.leasetime
86400
# dhcpcd --version
dhcpcd 4.0.15
Copyright (c) 2006-2008 Roy Marples
# pgrep -lf dhcpcd
1486 /system/bin/dhcpcd -ABKL -h android_dddddddddddddddd eth0
dhcpdcd options if they are the same on Android : http://roy.marples.name/cgi-bin/man-cgi?dhcpcd
-A, --noarp
Don't request or claim the address by ARP. This also disables
IPv4LL.
-B, --nobackground
Don't run in the background when we acquire a lease. This is
mainly useful for running under the control of another process,
such as a debugger or a network manager.
-K, --nolink
Don't receive link messages for carrier status. You should only
have to use this with buggy device drivers or running dhcpcd
through a network manager.
-L, --noipv4ll
Don't use IPv4LL (aka APIPA, aka Bonjour, aka ZeroConf).

[DEV] Packet injection and monitor mode support

Hi,
Motivated by zewelor´s thread about injection support for the G1, I decided to create an equal one for our beloved Hero .
The attached kernel is Flykernel 13 by erasmux with patched compat wireless kernel modules, using the injection patches from David and Bobs msm_wifi patch. Thanks to zewelor for the prepatched sources. This means the kernel supports packet injection and monitor mode, so you can inject packets with aireplay-ng or capture them with kismet/aircrack and so on.
ALWAYS MAKE A NANDROID BACKUP!
What do you need?
1. Rooted HTC Hero
2. Installed recovery Image
3. 2.2 Rom
4. It is suggested to install debian in chroot to use aircrack, kismet and set the card into monitor mode. An debian image with aircrack preinstalled by zewelor you can find here: http://www.megaupload.com/?d=HA6CJKET (159MB) extract it on the /sdcard/ and chroot in your debian environment with "sh /sdcard/debian/startdeb". [TEST IT YOURSELF]
Second method:
Use Lil`debi installer to mount the image, instructions are here: https://guardianproject.info/2011/06/18/easy-installer-for-debian-on-android/.
Click to expand...
Click to collapse
Instructions:
1) Download injection_FlyKernel-13.zip
2) Flash the kernel in recovery mode
3) Use the attached start-inject.sh and stop-inject.sh scripts to load and unload the patched wifi modules for "injection mode".
4) Have fun!
Click to expand...
Click to collapse
Known Issues/Bugs
-If the interface is not associated to an access point it drains battery like crazy. The fix is to backport the idle mode patch, needs more investigation in my tests the kernel becomes very unstable.
-Airodump-ng and kismet stop showing traffic after 20-30mins, not sure if display error or interface stops working.
-In "adb shell" you need to start "screen" otherwise airodump shows no output, or you use connectbot or any other terminal app.
Click to expand...
Click to collapse
For Devs:
Patches to backport for the wl1251 driver you can find here:
http://build.meego.com/package/file...:Testing&rev=477436ad94f99819a5a97b5db4ad89ff
An injection patch for the compat-wireless-2.6.37-4-sn you find here: http://trac.pentoo.ch/export/2496/p...pat-wireless/files/wl1251-inject-2.6.37.patch
Prepatched compat-wireless-2010-12-22 with n900 patches by david and config patch you find here http://forum.xda-developers.com/attachment.php?attachmentid=727820&d=1316713392 thanks for the work zewelor.
Click to expand...
Click to collapse
89fc9c7fd97dab56d3220e93dea77d63 kernel-config_2.6.29.zip
e03c0a22bcb5425f1b301f463ea87490 injection_FlyKernel-13.zip
8009fa3c70211aaa329a6456eb0af6c8 iwconfig-static.zip
14b1866cc2b60ddbc1b565dab4a219d8 injection_scripts.zip
Yes the scripts are very dirty, but hey they work!
start-inject.sh: http://pastebin.com/MDKc2WJm
stop-inject.sh: http://pastebin.com/UuX83CBD
kernel config 2.6.29: http://pastebin.com/8ASmEAgN
ATTENTION!
If you want to set the interface into monitor mode without a linux image, push the attached (static compiled) iwconfig to /data/local/bin and execute "/data/local/bin/iwconfig wlan0 mode monitor" or uncomment the line in both shell scripts, of course you can copy the binary in any directory you like.
Action Time:
Code:
$adb shell
# sh start-inject.sh
[x] Injection startup
[x] Firmware/calibration file found
[+] Load injection modules
[+] Start wlan0 interface
wlan0 should be up and running :)
lo UP 127.0.0.1 255.0.0.0 0x00000049
dummy0 DOWN 0.0.0.0 0.0.0.0 0x00000082
rmnet0 UP 2.45.243.195 255.255.255.248 0x00001043
rmnet1 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet2 DOWN 0.0.0.0 0.0.0.0 0x00001002
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
wlan0 UP 0.0.0.0 0.0.0.0 0x00001003
# debian [B][I](I'm using lil´debian this command starts the chroot script)[/I][/B]
[email protected]:/# ifconfig wlan0 down [B][I](In order to set monitor mode you most shutdown the interface or edit the injection script to start iwconfig)[/I][/B]
[email protected]:/# iwconfig wlan0 mode monitor
[email protected]:/# ifconfig wlan0 up
[email protected]:/# iwconfig wlan0
wlan0 IEEE 802.11bg Mode:Monitor Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:on
[email protected]:/# aireplay-ng --test wlan0
15:27:09 Trying broadcast probe requests...
15:27:13 Injection is working!
15:27:13 Found 1 AP
15:27:13 Trying directed probe requests...
15:27:13 E0:91:F5:XX:XX:XX - channel: 4 - 'XX_G'
15:27:43 Ping (min/avg/max): 982.727ms/993.888ms/1001.832ms Power: -70.16
15:27:43 19/30: 63%
[email protected]:/# exit
logout
# sh stop-inject.sh
[x] Stop Injection
[-] Stop wlan0 interface
[-] Unload injection modules
[+] Load wlan.ko module
[+] Load Firmware
[+] Start tiwlan0 interface
tiwlan0 should be up and running :)
lo UP 127.0.0.1 255.0.0.0 0x00000049
dummy0 DOWN 0.0.0.0 0.0.0.0 0x00000082
rmnet0 UP 2.45.243.195 255.255.255.248 0x00001043
rmnet1 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet2 DOWN 0.0.0.0 0.0.0.0 0x00001002
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
tiwlan0 UP 0.0.0.0 0.0.0.0 0x00001043
[B][I]Now enable wifi in android![/I][/B]
Remember these are not my patches, I only provide the patched kernel/kernel modules and loading scripts! Regarding the functionality and stability, Take it or leave it!, I have not the time and skill to make real modifications to the kernel module code to fix or improve stuff. You are free and welcome to post any progress you made.

FAQ
Q: What does packet injection and monitor mode mean?
A: It means that this thread is not for you!
Q: Does this stuff work for my XY phone?
A: No!, This kernel is only for HTC Hero, you need a phone which has the TI WL1251 wifi chipset, e.g G1, HTC Hero aka G2, Nokia N900 maemo...and build your own kernel.
Q: I have a problem with aircrack-ng,kismet...
A: This thread is about packet injection and monitor mode for the TI WL1251 and not about aircrack or kismet. I have nothing against serious questions, but want to avoid script kiddies derailing the thread with non topic related questions.
Q: I can't get the debian image running
A: Search the forum, there are a lot of different threads with instructions or use Lil`Debi Installer.
Q: I have a problem not related to aircrack-ng or kismet, can you help me?
A: I try to, however please post the question in the thread and _NOT_ via PM.
Q: Why not use Las Venturax kernel sources?
A: If there is demand I will post it, unfortunately it does not support "on the fly" switching between "regular and patched" wifi, which means every time you want to use the normal wlan module you need to reflash the kernel.
A lot questions are already answered in the G1 thread: http://forum.xda-developers.com/showthread.php?t=1271854

[GUIDE] GS2 Custom Wi-Fi (Eduroam, PEAP/MSCHAPV2) - GB/ICS

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

[Q] LEAP Wifi broken in 4.2 ?

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

The T-Mobile G3 is IPV6 only

T-Mobile has gone full IPV6 on the G3 (or maybe it was LG, or both). You will notice that you are not able to get an IPV4 only APN to work on T-Mobile's network, with epc, fast or pcweb APNs. The phone always connects to IPV6, and then uses NAT64 to provide IPV4 service to IPV4 only applications on the phone, and 464XLAT to communicate to IPV4 networks on the internet.
EDIT: I have confirmed that using epc.tmobile.com and forcing to IPV4 will work. This explains why using this combination makes data roaming work abroad. It seems like it's the fast.t-mobile.com APN that is forced to IPV6 only on the G3.
Here's a log of the data connection being set up on a T-Mobile G3 when using fast.t-mobile.com
Code:
D/libc ( 314): _dns_getaddrinfo: query_ipv4=1, query_ipv6=1
I/clatd (19471): Detected NAT64 prefix 2607:7700:0:a::/96
W/clatd (19471): ifmtu=1440
W/clatd (19471): ipv4mtu now set to = 1412
I/Vold ( 308): [LGE][VOLD][NetlinkHandler.cpp][onEvent()] subsys:net, action:1
I/Vold ( 308): [LGE][VOLD][NetlinkHandler.cpp][onEvent()] subsys:queues, action:1
I/Vold ( 308): [LGE][VOLD][NetlinkHandler.cpp][onEvent()] subsys:queues, action:1
I/Vold ( 308): [LGE][VOLD][NetlinkHandler.cpp][onEvent()] subsys:net, action:1
I/Vold ( 308): [LGE][VOLD][NetlinkHandler.cpp][onEvent()] subsys:queues, action:1
D/DHCP ( 314): ifc_init_returning 0
D/DHCP ( 314): ifc_close
I/Vold ( 308): [LGE][VOLD][NetlinkHandler.cpp][onEvent()] subsys:queues, action:1
I/Nat464Xlat( 1073): interface clat4 added, mIsRunning = false -> true
I/Nat464Xlat( 1073): Adding stacked link. tracker LP: {InterfaceName: rmnet0 LinkAddresses: [2607:fb90:2119:99f2:3c3d:1928:98a6:3341/64,] Routes: [::/0 -> fe80::4168:e92e:6776:e831,] DnsAddresses: [fd00:976a::9,] Domains: null MTU: 1440 Stacked: [ [{InterfaceName: clat4 LinkAddresses: [192.0.0.4/32,] Routes: [0.0.0.0/0 -> 192.0.0.4,] DnsAddresses: [] Domains: null MTU: 0} ],] }
D/ConnectivityServiceHSM( 1073): Actual State: DefaultConnectivityState, Current State: DefaultConnectivityState.processMessage what=458753
D/ConnectivityServiceHSM( 1073): send additional Connectivity Action
I/Nat464Xlat( 1073): sending message to ConnectivityService: { when=-9h45m41s893ms what=458753 obj=NetworkInfo: type: mobile[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: fast.t-mobile.com, roaming: false, failover: true, isAvailable: true, smCause: 0, isConnectedToProvisioningNetwork: false target=com.android.internal.util.StateMachine$SmHandler }
D/QcConnectivityService( 1073): makeGeneralIntent(): SM Cause is added to CONNECTIVITY_ACTION intent for [mobile], SM cause : 0
D/LocSvc_java( 1073): LocatioService.java action : android.net.conn.CONNECTIVITY_CHANGE_IMMEDIATE
D/ConnectivityServiceHSM( 1073): Actual State: DefaultConnectivityState, Current State: DefaultConnectivityState.processMessage what=5003
D/DHCP ( 314): ifc_init_returning 0
I/TelephonyProvider( 1434): getPreferredApnId: subscription=0
D/QcConnectivityService( 1073): makeGeneralIntent(): SM Cause is added to CONNECTIVITY_ACTION intent for [mobile], SM cause : 0
D/QcConnectivityService( 1073): handleConnectivityChange:0 is conntected
D/QcConnectivityService( 1073): [DATA]ePDG Dual Connectivity feature : false
D/BubblePopupHelper( 1217): isShowingBubblePopup : false
I/iptables( 314): iptables: Index of insertion too big.
I/iptables( 314): iptables terminated by exit(1)
E/BandwidthController( 314): runIptablesCmd(): res=1 status=256 failed /system/bin/iptables -I bw_INPUT 2 -i rmnet0 --jump bw_costly_rmnet0
I/iptables( 314): iptables: Index of insertion too big.
I/iptables( 314): iptables terminated by exit(1)
E/BandwidthController( 314): runIptablesCmd(): res=1 status=256 failed /system/bin/iptables -I bw_OUTPUT 2 -o rmnet0 --jump bw_costly_rmnet0
I/LGEPowerSaver( 341): GBM state is 1
I/ViewRootImpl( 1217): ViewRoot's Touch Event : ACTION_DOWN
E/BandwidthController( 314): Failed set quota rule
E/BandwidthController( 314): No such iface rmnet0 to delete
F/NetworkPolicy( 1073): problem setting interface quota
F/NetworkPolicy( 1073): java.lang.IllegalStateException: command '1039 bandwidth setiquota rmnet0 9223372036854775807' failed with '400 1039 Bandwidth command failed'
F/NetworkPolicy( 1073): at com.android.server.NetworkManagementService.setInterfaceQuota(NetworkManagementService.java:1978)
F/NetworkPolicy( 1073): at com.android.server.net.NetworkPolicyManagerService.setInterfaceQuota(NetworkPolicyManagerService.java:2318)
F/NetworkPolicy( 1073): at com.android.server.net.NetworkPolicyManagerService.updateNetworkRulesLocked(NetworkPolicyManagerService.java:1359)
F/NetworkPolicy( 1073): at com.android.server.net.NetworkPolicyManagerService.access$1300(NetworkPolicyManagerService.java:192)
F/NetworkPolicy( 1073): at com.android.server.net.NetworkPolicyManagerService$16.onReceive(NetworkPolicyManagerService.java:1155)
F/NetworkPolicy( 1073): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:782)
F/NetworkPolicy( 1073): at android.os.Handler.handleCallback(Handler.java:733)
F/NetworkPolicy( 1073): at android.os.Handler.dispatchMessage(Handler.java:95)
F/NetworkPolicy( 1073): at android.os.Looper.loop(Looper.java:136)
F/NetworkPolicy( 1073): at android.os.HandlerThread.run(HandlerThread.java:61)
F/NetworkPolicy( 1073): Caused by: com.android.server.NativeDaemonConnector$NativeDaemonFailureException: command '1039 bandwidth setiquota rmnet0 9223372036854775807' failed with '400 1039 Bandwidth command failed'
F/NetworkPolicy( 1073): at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:413)
F/NetworkPolicy( 1073): at com.android.server.NativeDaemonConnector.executeForList(NativeDaemonConnector.java:340)
F/NetworkPolicy( 1073): at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:305)
F/NetworkPolicy( 1073): at com.android.server.NetworkManagementService.setInterfaceQuota(NetworkManagementService.java:1975)
F/NetworkPolicy( 1073): ... 9 more
D/QcConnectivityService( 1073): handleConnectivityChange: address are the same reset per doReset linkProperty[0]: resetMask=0
D/QcConnectivityService( 1073): RoutesChanged, Remove old dns /fd00:976a::9
E/NetworkManagementService( 1073): [LGE_DATA]isHostRoute = true isDefaultRoute = false
V/ ( 314): [LGE_DATA]route append fe80::4168:e92e:6776:e831 via :: dev rmnet0 table 254 metric 512
V/ ( 314): RouteController
D/QcConnectivityService( 1073): RoutesChanged, Add new dns /fd00:976a::9
V/ ( 314): RouteController
V/ ( 314): RouteController
W/NetworkManagementService( 1073): route cmd failed:
W/NetworkManagementService( 1073): com.android.server.NativeDaemonConnector$NativeDaemonFailureException: command '1042 route add append v6 rmnet0 512 fe80::4168:e92e:6776:e831 ::' failed with '400 1042 route append fe80::4168:e92e:6776:e831 via :: dev rmnet0 table 254 metric 512: RTNETLINK answers: Invalid argument
W/NetworkManagementService( 1073): '
W/NetworkManagementService( 1073): at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:413)
W/NetworkManagementService( 1073): at com.android.server.NativeDaemonConnector.executeForList(NativeDaemonConnector.java:340)
W/NetworkManagementService( 1073): at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:305)
W/NetworkManagementService( 1073): at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:290)
W/NetworkManagementService( 1073): at com.android.server.NetworkManagementService.appendRouteWithMetric(NetworkManagementService.java:2757)
W/NetworkManagementService( 1073): at com.android.server.QcConnectivityService.modifyRoute(QcConnectivityService.java:2995)
W/NetworkManagementService( 1073): at com.android.server.QcConnectivityService.modifyRoute(QcConnectivityService.java:2975)
W/NetworkManagementService( 1073): at com.android.server.QcConnectivityService.modifyRouteToAddress(QcConnectivityService.java:2933)
W/NetworkManagementService( 1073): at com.android.server.QcConnectivityService.addRouteToAddress(QcConnectivityService.java:2903)
W/NetworkManagementService( 1073): at com.android.server.QcConnectivityService.updateRoutes(QcConnectivityService.java:4813)
W/NetworkManagementService( 1073): at com.android.server.QcConnectivityService.handleConnectivityChange(QcConnectivityService.java:4637)
W/NetworkManagementService( 1073): at com.android.server.QcConnectivityService.access$6100(QcConnectivityService.java:244)
W/NetworkManagementService( 1073): at com.android.server.QcConnectivityService$ConnectivityServiceHSM$DefaultConnectivityState.processMessage(QcConnectivityService.java:6047)
W/NetworkManagementService( 1073): at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
W/NetworkManagementService( 1073): at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
W/NetworkManagementService( 1073): at android.os.Handler.dispatchMessage(Handler.java:102)
W/NetworkManagementService( 1073): at android.os.Looper.loop(Looper.java:136)
W/NetworkManagementService( 1073): at android.os.HandlerThread.run(HandlerThread.java:61)
E/NetworkManagementService( 1073): [LGE_DATA]isHostRoute = true isDefaultRoute = false
V/ ( 314): [LGE_DATA]route append fd00:976a::9 via fe80::4168:e92e:6776:e831 dev rmnet0 table 254 metric 512
V/ ( 314): RouteController
D/QcConnectivityService( 1073): Adding v6 fe80::4168:e92e:6776:e831/128 -> :: for interface rmnet0 with metric 512
V/ ( 314): RouteController
V/ ( 314): RouteController
V/ ( 314): [LGE_DATA]res empty
V/ ( 314): RouteController
I/ViewRootImpl( 1217): ViewRoot's Touch Event : ACTION_UP
D/DHCP ( 314): ifc_init_returning 0
D/DHCP ( 314): ifc_close
D/DHCP ( 314): ifc_add_route(clat4, 192.0.0.4, 32, 0.0.0.0) = 0
D/DHCP ( 314): ifc_init_returning 0
D/DHCP ( 314): ifc_close
D/DHCP ( 314): ifc_add_route(clat4, 0.0.0.0, 0, 192.0.0.4) = 0
D/ConnectivityServiceHSM( 1073): Actual State: DefaultConnectivityState, Current State: DefaultConnectivityState.processMessage what=112
D/ConnectivityServiceHSM( 1073): Actual State: DefaultConnectivityState, Current State: DefaultConnectivityState.processMessage what=112
D/ConnectivityServiceHSM( 1073): Actual State: DefaultConnectivityState, Current State: DefaultConnectivityState.processMessage what=112
D/ConnectivityServiceHSM( 1073): Actual State: DefaultConnectivityState, Current State: DefaultConnectivityState.processMessage what=112
D/QcConnectivityService( 1073): Adding v6 fd00:976a::9/128 -> fe80::4168:e92e:6776:e831 for interface rmnet0 with metric 512
D/QcConnectivityService( 1073): Route attribute is null, Adding 192.0.0.4/32 -> 0.0.0.0 for interface clat4
D/QcConnectivityService( 1073): Route attribute is null, Adding 0.0.0.0/0 -> 192.0.0.4 for interface clat4
D/Nat464Xlat( 1073): requiresClat: netType=0, hasIPv4Address=false
E/Nat464Xlat( 1073): startClat: already started
D/QcConnectivityService( 1073): CLAT started, enable dns query A and AAAA types for netType=0
D/MobileDataStateTracker( 1073): default: setPolicyDataEnable(enabled=true)
D/MobileDataStateTracker( 1073): default: setPolicyDataEnable(enabled=true)

You can make a new one to support both

BACARDILIMON said:
You can make a new one to support both
Click to expand...
Click to collapse
If you configure it for IPV4/IPV6, it will use IPV6. That's how my APN copy is setup and that's what the above output is using. Setting it to IPV4 only will leave you without a data connection.

Yeah just tested and saw.

BACARDILIMON said:
Yeah just tested and saw.
Click to expand...
Click to collapse
I know that T-Mobile has IPV6 deployed on LTE, but not sure about HSPA, so if there is no IPV6 support in a part of the network, the phone would fail to use data. This is what happening with international roaming and why people are having issues.
I did find that I can get data by changing the APN to epc, then setting it to IPV4, but also forcing the phone to WCDMA only.
I don't know if the phone would automatically fall back on IPV4 where there is no IPV6. I'll have to see what it does when on EDGE.

My phone here in UAE is using the epc APN with IPv4 only and at 2G, 3G, and 4G...?
Sent from my LG G3

Nitemare3219 said:
My phone here in UAE is using the epc APN with IPv4 only and at 2G, 3G, and 4G...?
Sent from my LG G3
Click to expand...
Click to collapse
I don't think T-Mobile has any LTE roaming agreements yet. The epc APN lets you connect to data with IPV4 in the US, and this is why it makes things work abroad too. The phone probably will not connect to data services over IPV4 using the fast APN

I have ipv4 only working with 4g. I'm going to re trace some steps and hook everyone up. May not be until tomorrow night but yeah good news.

Why are there smiley faces in the log? Lol
Sent from my LG-D851 using XDA Premium 4 mobile app

You mean the sad faces?
Sent from my LG-D851 using XDA Free mobile app

ThePagel said:
I have ipv4 only working with 4g. I'm going to re trace some steps and hook everyone up. May not be until tomorrow night but yeah good news.
Click to expand...
Click to collapse
Are you using the epc APN? I have not been able to get data when using the fast APN, but it works with epc.
I did find that forcing 2G gets you data with fast. It's possible the phone is using a special APN for 2G networks, or there's a built-in bypass that allows IPV4 on 2G. It's also possible that T-Mobile has IPV6 enabled on 2G connections as well, and thus the built-in IPV6 only APN would work.

havanahjoe said:
Are you using the epc APN? I have not been able to get data when using the fast APN, but it works with epc.
I did find that forcing 2G gets you data with fast. It's possible the phone is using a special APN for 2G networks, or there's a built-in bypass that allows IPV4 on 2G. It's also possible that T-Mobile has IPV6 enabled on 2G connections as well, and thus the built-in IPV6 only APN would work.
Click to expand...
Click to collapse
Nope fast, I flashed the Korean version. Thought I could get it working on the t mobile ROM but no go. I'll be posting a port tonight because it seemed better overall. It also gets 3g and unless it was a bug it also gets hspa. I only messed with it for about ten minutes before I reverted back to my t-mo backup. Guess we will find out tonight.
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
havanahjoe said:
Are you using the epc APN? I have not been able to get data when using the fast APN, but it works with epc.
I did find that forcing 2G gets you data with fast. It's possible the phone is using a special APN for 2G networks, or there's a built-in bypass that allows IPV4 on 2G. It's also possible that T-Mobile has IPV6 enabled on 2G connections as well, and thus the built-in IPV6 only APN would work.
Click to expand...
Click to collapse
Nope fast, I flashed the Korean version. Thought I could get it working on the t mobile ROM but no go. I'll be posting a port tonight because it seemed better overall. It also gets 3g and unless it was a bug it also gets hspa. I only messed with it for about ten minutes before I reverted back to my t-mo backup. Guess we will find out tonight.
*edit*
I have yet to see 3g on T-Mobile G3 only LTE and 2g but that might just be me.
*edit*
Oops double post

ThePagel said:
Nope fast, I flashed the Korean version. Thought I could get it working on the t mobile ROM but no go. I'll be posting a port tonight because it seemed better overall. It also gets 3g and unless it was a bug it also gets hspa. I only messed with it for about ten minutes before I reverted back to my t-mo backup. Guess we will find out tonight.
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
Nope fast, I flashed the Korean version. Thought I could get it working on the t mobile ROM but no go. I'll be posting a port tonight because it seemed better overall. It also gets 3g and unless it was a bug it also gets hspa. I only messed with it for about ten minutes before I reverted back to my t-mo backup. Guess we will find out tonight.
*edit*
I have yet to see 3g on T-Mobile G3 only LTE and 2g but that might just be me.
*edit*
Oops double post
Click to expand...
Click to collapse
A port of the Korean version would be awesome! I'm sure Tmo put in a lot of specific limitations on their version, including only using IPV6 on fast. I don't like how US carriers call HSPA+ 4G. Having a port would probably also fix the tethering block we are seeing on the Tmo version. Once you publish it I will be one of the first to try it.
The indicators you are seeing are the normal AOSP ones. You will see E for EDGE, G for GSM, 3G for UMTS, H for HSPA, H+ for HSPA+ and LTE for LTE.

havanahjoe said:
A port of the Korean version would be awesome! I'm sure Tmo put in a lot of specific limitations on their version, including only using IPV6 on fast. I don't like how US carriers call HSPA+ 4G. Having a port would probably also fix the tethering block we are seeing on the Tmo version. Once you publish it I will be one of the first to try it.
The indicators you are seeing are the normal AOSP ones. You will see E for EDGE, G for GSM, 3G for UMTS, H for HSPA, H+ for HSPA+ and LTE for LTE.
Click to expand...
Click to collapse
So is T-Mobile calling edge 2g?

ThePagel said:
So is T-Mobile calling edge 2g?
Click to expand...
Click to collapse
Yup!

What are the issues with using IPv6?
In my APN settings I have an option for "APN protocol" (set to Ipv6 only) and "APN roaming protocol" (set to IPv4 only). Does that not work? Does it still try to use IPv6 when roaming in that case?
At least within the US I haven't seen any issues with using IPv6 on T-Mobile so far, but then I don't really travel that much.

apmon said:
What are the issues with using IPv6?
In my APN settings I have an option for "APN protocol" (set to Ipv6 only) and "APN roaming protocol" (set to IPv4 only). Does that not work? Does it still try to use IPv6 when roaming in that case?
At least within the US I haven't seen any issues with using IPv6 on T-Mobile so far, but then I don't really travel that much.
Click to expand...
Click to collapse
No issues for normal operations, it does seem to affect international roaming. Where do you see APN Roaming Protocol? It doesn't show up in my APN configuration on the T-Mobile stock ROM.

havanahjoe said:
No issues for normal operations, it does seem to affect international roaming. Where do you see APN Roaming Protocol? It doesn't show up in my APN configuration on the T-Mobile stock ROM.
Click to expand...
Click to collapse
I have an Samsung S4 not a LG, but I presumed that all phones have that option? At least I have seen it in other phones as well. Here it is listed just under the normal APN settings.

apmon said:
I have an Samsung S4 not a LG, but I presumed that all phones have that option? At least I have seen it in other phones as well. Here it is listed just under the normal APN settings.
Click to expand...
Click to collapse
Oh, yes, most phones have that option, but the G3 is different. This is most likely the future of T-Mobile customizations

Its going to be a day late fyi