Develop Bugs

Wap settings for Base operator in Belgium

Most probably this is a stupid question for all of you out there, so please help me.
I got the following settings from Base Operator in Belgium but I can't find where I need to input this info.
The info which I got:
Homepage: http://wap.base.be
Type connection: passthrough (this is transalated from dutch:doorlopend)
Connection Security(transalated): off
Type: DATA
Number: +32486927927
IP port : for wap1:9201 wap2:5080
IP adress 172.031.198.037
verification type: Normal
Data Type: ISDN
Speed: 9600
user name: Base
Password: 1234
Where do I have to insert all that info so that I can get a wap connection with my Blue Angel.
P.S. Base does NOT have GPRS

how do you set up EDGE

how do you set up EDGE in wm6.1 for t-mobile uk

rickwyatt said:
how do you set up EDGE in wm6.1 for t-mobile uk
Click to expand...
Click to collapse
Not really sure this is the answer you're looking for, but try this
GPRS Connection :
Connects to : "The Internet"
Access Point : "general.t-mobile.uk"
User Name : "user"
Password : "user" or "wap"
Primary DNS : blank
Secondary DNS : blank
GPRS WAP Connection :
Connects to : "WAP Network"
Access Point : "general.t-mobile.uk"
IP : "149.254.001.010"
User Name : "user"
Password : "wap" or "user"

Click on my signature below and it should help you set it up and show you how to set it up.

Good link, but I don't think it gives settings for T-Mobile UK.

Oh I didnt see the Tmobile Uk haha

[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

[MOD/SETTINGS TWEAK] SiRF GPS on SGS2

This is the updated sirfgps.conf file ONLY for ICS and has been modded by myself. As the GPS serial port is changed in ICS ROM.
#CSR SiRF plc
#PROJECT_NAME : white Space is not allowed
#UART_DRIVER : Uart Driver Path
#RESET_GPIO : Reset GPIO Driver Path
#ONOFF_GPIO : OnOff GPIO Driver Path
#EXTERNAL_LNA : 1 - use External LNA, 0 - use Internal LNA only
#REF_CLOCK_26MHZ: 1 - use 26MHz TCXO, 0 - use 16.369MHz TCXO
#UART_BAUD_RATE : 0 - 115200bps 1 - 230400, 2 - 460800, 3 - 57600
#FREQUENCY_AIDING : 0 - Disable, 1 - Enable
#SENSOR_AIDING : 0 - Disable, 1 - Enable
#SET_ID_IMSI : 1 - Use IMSI for SET ID, 0 - Use MSISDN for SET ID, especially for Japan Network Operators
#DEBUGGING_FILES : 0 - no log file, 1 - log files enabled
#SSL_ENABLED : 0 - SSL Disabled, 1 - SSL Enabled
#CERTI_VERSION : 0 - TLSv1 , 1 - SSLv3 , 2 - SSLv23
#CP_RESPONSETIME : 0 - no priority, 1 - resposne priority time, 2 - resposne priority position ,3 - resposne priority use entire response time
#REAIDING=20
#CONTROL_PLANE : 1 - CP Enabled, 0 - CP Disabled, for MP3 player or PND
#ATT_NETWORK_OPERATOR : 1 - for AT&T, 0 - for other network operator
#SGEE : 1 - SGEE ENABLE 0 - SGEE DISABLE
PROJECT=SAMSUNG_S5PC210
UART_DRIVER=/dev/ttySAC1
RESET_GPIO=/sys/devices/virtual/sec/gps/GPS_nRST/value
ONOFF_GPIO=/sys/devices/virtual/sec/gps/GPS_PWR_EN/value
REAIDING=20
EXTERNAL_LNA=1
REF_CLOCK_26MHZ=1
UART_BAUD_RATE=2
FREQUENCY_AIDING=1
SENSOR_AIDING=1
SET_ID_IMSI=1
DEBUGGING_FILES=0
SSL_ENABLED=1
CERTI_VERSION=1
CP_RESPONSETIME=3
CONTROL_PLANE=1
ATT_NETWORK_OPERATOR=0
ICS_NETWORK_OPERATOR=0
EMC_ENABLE=1
CIQ_ENABLE=1
SGEE=1
CGEE=1
LOG_PATH=/data
Click to expand...
Click to collapse
======================================
I meddled with the stock SGS KH3 firmware and found this file inside (/etc/sirfgps.conf).
It got so many settings for GPS chipset but is untouched by AngryGPS program or any system's GPS settings, it must be edited manually.
I noticed a big differences by turning on this sensor aiding, freq aid, and emc feature in this file.
I do notice that sensor aiding is toggleable in the system's setting but it only work in software level and this conf file is in hardware level.
If any of you want the edited file, let me know and I'll post it for you.
============================================

Please share, I'm curious about your discovery
Sent from my htc.desireZED

Yes. It would be nice if you posted the updated file.

This is the mentioned file found in my stock rooted /etc folder. Modified of course...
Permission is rw-r--r--
Group is root|root

hm I m looking for difference and you switch AIDING to ON manuall but when I enable in setting>>location>>use sensors- It is the same I think .)

Crescendo Xenomorph said:
This is the mentioned file found in my stock rooted /etc folder. Modified of course...
Permission is rw-r--r--
Group is root|root
Click to expand...
Click to collapse
This looks interesting, but unfortunately the zip file seems to be corrupt. Can you please re-upload the file?

I just trying to open the file and it works OK.
Try to extract it using WinRAR. I compressed it via WinRAR.
Hmm, when I enable the sensor aiding in the location menu, the sensor aiding in that conf file is still 0. When I disable it, the file also says 0. The last modified time is months ago, which is before I activate this device.
I notice the faster fix (mainly when you try to get a cold fix inside a fast moving car) and slight improvement in accuracy.
The interesting settings are: frequency aiding and emc feature.
I dunno what it's for but it improve my lock time and accuracy.

#CSR SiRF plc
#PROJECT_NAME : white Space is not allowed
#UART_DRIVER : Uart Driver Path
#RESET_GPIO : Reset GPIO Driver Path
#ONOFF_GPIO : OnOff GPIO Driver Path
#EXTERNAL_LNA : 1 - use External LNA, 0 - use Internal LNA only
#REF_CLOCK_26MHZ: 1 - use 26MHz TCXO, 0 - use 16.369MHz TCXO
#UART_BAUD_RATE : 0 - 115200bps 1 - 230400, 2 - 460800, 3 - 57600
#FREQUENCY_AIDING : 0 - Disable, 1 - Enable
#SENSOR_AIDING : 0 - Disable, 1 - Enable
#SET_ID_IMSI : 1 - Use IMSI for SET ID, 0 - Use MSISDN for SET ID, especially for Japan Network Operators
#DEBUGGING_FILES : 0 - no log file, 1 - log files enabled
#SSL_ENABLED : 0 - SSL Disabled, 1 - SSL Enabled
#CERTI_VERSION : 0 - TLSv1 , 1 - SSLv3 , 2 - SSLv23
#CP_RESPONSETIME : 0 - no priority, 1 - resposne priority time, 2 - resposne priority position ,3 - resposne priority use entire response time
#REAIDING=20
#CONTROL_PLANE : 1 - CP Enabled, 0 - CP Disabled, for MP3 player or PND
#ATT_NETWORK_OPERATOR : 1 - for AT&T, 0 - for other network operator
PROJECT=SAMSUNG_S5PC210
UART_DRIVER=/dev/s3c2410_serial1
RESET_GPIO=/sys/devices/virtual/sec/gps/GPS_nRST/value
ONOFF_GPIO=/sys/devices/virtual/sec/gps/GPS_PWR_EN/value
EXTERNAL_LNA=1
REF_CLOCK_26MHZ=1
UART_BAUD_RATE=2
FREQUENCY_AIDING=1
SENSOR_AIDING=1
SET_ID_IMSI=1
DEBUGGING_FILES=0
SSL_ENABLED=0
CERTI_VERSION=0
CP_RESPONSETIME=2
CONTROL_PLANE=1
ATT_NETWORK_OPERATOR=0
EMC_ENABLE=1
LOG_PATH=/sdcard/gps/csr

Testing
Hi,
I have tried this trick, but i saw no difference ...Inside my car (i have those "heat-protected" windows) i still have problems, my accuracy is awful, usually between 15-20 m in an open road (with spots of 5-10 m), and 25-30 m inside the city (which makes it useless).
I have changed the UART_BAUD to 3 and i will test it later....the reason is that i realized that when i turn right/left with my car, or in the road when a curve is closed enough to generate "centrifugal force" the accuracy drops from 10 m to 25 m and then when i come back to a straight lane the precision goes down to "normal" values....so i reduced BAUD to minimum, it will be slower but i hope more stable....
I'll try and post my results tomorrow

Crescendo Xenomorph said:
#CSR SiRF plc
#PROJECT_NAME : white Space is not allowed
#UART_DRIVER : Uart Driver Path
#RESET_GPIO : Reset GPIO Driver Path
#ONOFF_GPIO : OnOff GPIO Driver Path
#EXTERNAL_LNA : 1 - use External LNA, 0 - use Internal LNA only
#REF_CLOCK_26MHZ: 1 - use 26MHz TCXO, 0 - use 16.369MHz TCXO
#UART_BAUD_RATE : 0 - 115200bps 1 - 230400, 2 - 460800, 3 - 57600
#FREQUENCY_AIDING : 0 - Disable, 1 - Enable
#SENSOR_AIDING : 0 - Disable, 1 - Enable
#SET_ID_IMSI : 1 - Use IMSI for SET ID, 0 - Use MSISDN for SET ID, especially for Japan Network Operators
#DEBUGGING_FILES : 0 - no log file, 1 - log files enabled
#SSL_ENABLED : 0 - SSL Disabled, 1 - SSL Enabled
#CERTI_VERSION : 0 - TLSv1 , 1 - SSLv3 , 2 - SSLv23
#CP_RESPONSETIME : 0 - no priority, 1 - resposne priority time, 2 - resposne priority position ,3 - resposne priority use entire response time
#REAIDING=20
#CONTROL_PLANE : 1 - CP Enabled, 0 - CP Disabled, for MP3 player or PND
#ATT_NETWORK_OPERATOR : 1 - for AT&T, 0 - for other network operator
PROJECT=SAMSUNG_S5PC210
UART_DRIVER=/dev/s3c2410_serial1
RESET_GPIO=/sys/devices/virtual/sec/gps/GPS_nRST/value
ONOFF_GPIO=/sys/devices/virtual/sec/gps/GPS_PWR_EN/value
EXTERNAL_LNA=1
REF_CLOCK_26MHZ=1
UART_BAUD_RATE=2
FREQUENCY_AIDING=1
SENSOR_AIDING=1
SET_ID_IMSI=1
DEBUGGING_FILES=0
SSL_ENABLED=0
CERTI_VERSION=0
CP_RESPONSETIME=2
CONTROL_PLANE=1
ATT_NETWORK_OPERATOR=0
EMC_ENABLE=1
LOG_PATH=/sdcard/gps/csr
Click to expand...
Click to collapse
I dont think this will make much difference.. on my phone anyway if you look at the line
Crescendo Xenomorph said:
UART_DRIVER=/dev/s3c2410_serial1
Click to expand...
Click to collapse
looking in that file location there is no such driver present..

I DO have the s3c2410_serial1 file on that location....And a serial0, serial2, serial3 and serial4
I dont really know if this is doing something or not...I tried to enable debugging and i see no file created on sdcard

But why Samsung put that file inside their ROM?

Hi,
this works for me, gps fix in 10sec.
with friendly greet
starbase64

So you only copy sirfgps to /etc and not more?
Thanks. Sounds interesting.
Sent from my GT-I9100 using XDA App

lynx2k50 said:
So you only copy sirfgps to /etc and not more?
Thanks. Sounds interesting.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
yes
german forum: http://goo.gl/o2aa4

IN new italian ROM LA2 2.3.6
Code:
#CSR SiRF plc
#PROJECT_NAME : white Space is not allowed
#UART_DRIVER : Uart Driver Path
#RESET_GPIO : Reset GPIO Driver Path
#ONOFF_GPIO : OnOff GPIO Driver Path
#EXTERNAL_LNA : 1 - use External LNA, 0 - use Internal LNA only
#REF_CLOCK_26MHZ: 1 - use 26MHz TCXO, 0 - use 16.369MHz TCXO
#UART_BAUD_RATE : 0 - 115200bps 1 - 230400, 2 - 460800, 3 - 57600
#FREQUENCY_AIDING : 0 - Disable, 1 - Enable
#SENSOR_AIDING : 0 - Disable, 1 - Enable
#SET_ID_IMSI : 1 - Use IMSI for SET ID, 0 - Use MSISDN for SET ID, especially for Japan Network Operators
#DEBUGGING_FILES : 0 - no log file, 1 - log files enabled
#SSL_ENABLED : 0 - SSL Disabled, 1 - SSL Enabled
#CERTI_VERSION : 0 - TLSv1 , 1 - SSLv3 , 2 - SSLv23
#CP_RESPONSETIME : 0 - no priority, 1 - resposne priority time, 2 - resposne priority position ,3 - resposne priority use entire response time
#REAIDING=20
#CONTROL_PLANE : 1 - CP Enabled, 0 - CP Disabled, for MP3 player or PND
#ATT_NETWORK_OPERATOR : 1 - for AT&T, 0 - for other network operator
#SGEE : 1 - SGEE ENABLE 0 - SGEE DISABLE
PROJECT=SAMSUNG_S5PC210
UART_DRIVER=/dev/s3c2410_serial1
RESET_GPIO=/sys/devices/virtual/sec/gps/GPS_nRST/value
ONOFF_GPIO=/sys/devices/virtual/sec/gps/GPS_PWR_EN/value
EXTERNAL_LNA=1
REF_CLOCK_26MHZ=1
UART_BAUD_RATE=2
FREQUENCY_AIDING=0
SENSOR_AIDING=0
SET_ID_IMSI=1
DEBUGGING_FILES=0
SSL_ENABLED=0
CERTI_VERSION=0
CP_RESPONSETIME=2
CONTROL_PLANE=1
ATT_NETWORK_OPERATOR=0
ICS_NETWORK_OPERATOR=0
EMC_ENABLE=0
CIQ_ENABLE=0
SGEE=1
LOG_PATH=/sdcard/gps/csr
This line are new:
ICS_NETWORK_OPERATOR=0
CIQ_ENABLE=0
SGEE=1

Hi,
Please would someone post the original settings as my GPS will not lock at all now and I would like to reset them.
Thanks

From stock rom..
#CSR SiRF plc
#PROJECT_NAME : white Space is not allowed
#UART_DRIVER : Uart Driver Path
#RESET_GPIO : Reset GPIO Driver Path
#ONOFF_GPIO : OnOff GPIO Driver Path
#EXTERNAL_LNA : 1 - use External LNA, 0 - use Internal LNA only
#REF_CLOCK_26MHZ: 1 - use 26MHz TCXO, 0 - use 16.369MHz TCXO
#UART_BAUD_RATE : 0 - 115200bps 1 - 230400, 2 - 460800, 3 - 57600
#FREQUENCY_AIDING : 0 - Disable, 1 - Enable
#SENSOR_AIDING : 0 - Disable, 1 - Enable
#SET_ID_IMSI : 1 - Use IMSI for SET ID, 0 - Use MSISDN for SET ID, especially for Japan Network Operators
#DEBUGGING_FILES : 0 - no log file, 1 - log files enabled
#SSL_ENABLED : 0 - SSL Disabled, 1 - SSL Enabled
#CERTI_VERSION : 0 - TLSv1 , 1 - SSLv3 , 2 - SSLv23
PROJECT=SAMSUNG_U1
UART_DRIVER=/dev/s3c2410_serial1
RESET_GPIO=/sys/devices/virtual/sec/gps/GPS_nRST/value
ONOFF_GPIO=/sys/devices/virtual/sec/gps/GPS_PWR_EN/value
EXTERNAL_LNA=1
REF_CLOCK_26MHZ=1
UART_BAUD_RATE=2
FREQUENCY_AIDING=1
SENSOR_AIDING=0
SET_ID_IMSI=1
DEBUGGING_FILES=0
SSL_ENABLED=0
CERTI_VERSION=0

Crescendo Xenomorph said:
But why Samsung put that file inside their ROM?
Click to expand...
Click to collapse
did you try to use an external SiRFIII GPS through BT, maybe it's for that....

Crescendo Xenomorph said:
Hmm, when I enable the sensor aiding in the location menu, the sensor aiding in that conf file is still 0. When I disable it, the file also says 0. The last modified time is months ago, which is before I activate this device.
Click to expand...
Click to collapse
Most likely there is an interface (maybe a control socket?) that allows these settings to be overridden by the Settings app without changing the file.
To confirm if the file is even used (sometimes cruft makes it into a ROM for no good reason...), try changing the serial port from s3c2410_serial1 to something else - it should completely break things. If it does not totally break things, then the file is most likely not used.

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