Develop Bugs

[Q] PROBLEM: WLAN (WPA Enterprise) does not work for a long time

Hi!
First: I do not know wether General discussion - Networking would be a better place, so if an admin thinks so, please move this thread.
my problem: after some hours, offen after night, my wlan does not work properly:
my config:
2 WLAN-routers Syslink WRT54G with DD-WRT v24-sp2 with identical config (SSID and so on - but of course different channels):
two virtual WLANs on each
1) WPA(2) Enterprise with username/pass or user certificate
radius server
for individual users
2) WPA(2) PSK for wlan radios and so on
my Desire uses 1) (tried both: username and certificate, same result)
my Desire:
various radios, now 5.10.05.23
LeeDroid V2.0a Froyo
my problem:
after some hours in the Wi-Fi config I got:
Wi-Fi: Authenticating with MY_SSID...
and this messages does not change.
This has interesting effects to my Desire:
there is still the wlan symbol in status bar, no G3 (mobile network setting is on) so my Desire seems to know, that wlan is working
htc weather app - refresh - "Unable to connect You need a network connection to use this application. Please turn on mobile network or Wi-Fi"
standard internet browser - internet works fine
http://mobil.tagesschau.de Streaming of Tagesschau in 100 Sekunden
popup "Movies or Streaming Media Player" - Movies = all works, Streaming = "Connection failes This application requieres network access ..."
Astrid snyc - works
maps - works
K-9 - new mails are received after manual "check mail" but not pushed via IMAP idle
via *#*#4636#*#*
Wifi Config
* ID 5 SSID: "MY_SSID" BSSID: null
PRIO: 67
KeyMgmt: WPA_EAP IEEE8021X Protocols: WPA RSN
AuthAlgorithms:
PairwaiseCiphers: TKIP CCMP
GroupCiphers: WEP40 WEP104 TKIP CCMP
PSK:
eapEAP
phase2: auth=MSCHAPV2
identity: My User Name
anonymous_identity:
password: xxxxxx
client_cert:
private_key:
ca_cert:
Wifi Status
Wifi State: enabled
Network State: Authenticating with MY_SSID
Supplicant State: COMPLETED
RSSI: -61
BSSID: 00:14:xxxx
SSID: MY_SSID
Hidden SSID: false
IPaddr: 192.168.1.15
MAC addr: 38:xxxx
Network ID: 5
Link Speed: 54 Mbps
Scan results:
run ping test:
ping IpAddr: pass
ping Hostname (www.google.com): pass
HTTP Client test: pass
even if there is an "authentication ..." message
my radius server log shows me no authentication process, no working and no failing one.
so, now I have to options:
wifi off/on or
going to the second wlan ap, so my Desire switches to it because this is then the stronger wifi
signal
in wifi setting now: Connecting MY_SSID, scan, Connecting, Connected with MY_SSID
after this K-9 get immediately new mails pushed via imap idle, weather updating works, streaming is fine ... and my radius server log shows me an authentication process
(I swaped both routers but no effect for my problem.)
changes in *#*#4636#*#*
Wifi State: enabled
Network State: Connected to MY_SSID
RSSI: -64
Any idea for this strange phenomenon? It is very annoying!

nobody here who uses WPA enterprise / wpa with radius?

Hi
were you able to ever fix this problem. I am currently having the same issue
thanks

there is an issue in google's android bugtracker, with many concerned users, but no help by google.
http://code.google.com/p/android/issues/detail?id=12125

Hi Folks
Does anyone know if there is a ROM that fixes this issue, or if there is a fix anywhere. We have a number of Desires in the office which all suffer this issue when connected to our Cisco based WiFi network (WPA Enterprise). We have managed to get IT to extend the re-auth period to 1hr, but they will go no further. Current work around is to take a walk to the other side of the office and force a re-associate to a new AP (or dis/enable wifi on the phone). Not ideal.
Thanks

there is still no fix to this, but I found a working solution:
Fix My Wifi
https://market.android.com/details?...wsMSwxLDEsImNvLnVrLnN5c2x5bnguZml4bXl3aWZpIl0.
https://market.android.com/details?...xLDEsImNvLnVrLnN5c2x5bnguZml4bXl3aWZpZGVtbyJd
HTH

Galaxy Nexus Wi-Fi dropping / reconnecting

Been having this issue lately with my Galaxy Nexus. Not sure if its the phone, or my router.
When I'm connected to my home wifi network, the connection on my Galaxy Nexus is constantly in and out. It will stay connected for a few minutes, and then drop for a few seconds, reconnect, and keeps repeating the same cycle. I can watch it do this in the wifi connections menu under settings. This is super frustrating when trying to web browse / use apps that require connection, etc.
*Note, this also happens at my Mom's house too. Same issue.
Anyone else have this issue or a fix? Would be greatly appreciated.

I've been having the exact same issue. GSM Galaxy Nexus from Rogers running stock 4.0.1, rooted, unlocked bootloader, UGKL1.
I've tried a few roms (Android Revolution, AOKP 19) with some custom kernels (franco 13.1, GN-GSM by faux123) and still had the same problems.
I've been having the same issue with my Xoom running stock ICS 4.0.3 (rooted, unlocked) as well, so I thought it was my router too. I've reset that and still the problem persists.
I've adjusted both my phone and tablet to only use 2.4ghz in WiFi -> Advanced which was no help either. All other wifi devices in the house are running without issue.
Not sure what to do at this point.

Are there many other wireless networks in your house/area? Is the 2,4GHz band crowded? You can check that with an app called "Wifi Analyzer" from the market. If it is crowded around your channel you, can try to switch it to one less crowded.

Go into Settings>Wifi Settings>Menu>Advanced. Click on "Wifi Frequency Band" and change it from Auto to 2.4 GHz Only.

Herman76 said:
Are there many other wireless networks in your house/area? Is the 2,4GHz band crowded? You can check that with an app called "Wifi Analyzer" from the market. If it is crowded around your channel you, can try to switch it to one less crowded.
Click to expand...
Click to collapse
I've looked into that and changed to a less crowded channel, no change for my phone or tablet. My Xoom was fine before when running HC 3.2.2, my N1 was fine running CM7 Nightly and all other wifi devices are fine in the house. Problems only exist with my ICS devices.
zeppelinmad4 said:
Go into Settings>Wifi Settings>Menu>Advanced. Click on "Wifi Frequency Band" and change it from Auto to 2.4 GHz Only.
Click to expand...
Click to collapse
I've made that change as well, still keeps dropping and connecting.

Have you tried giving your Xoom and GN a Fixed IP (advanced in wireless menu).

No I didn't want to have to go that route, but I guess it's a logical next step. I'll try that tonight.

Did you fix the problem?
Hey
Sorry to dig up an old thread but I have started to experience exactly the same problem with my GSM nexus.
I have had the device since release in November and have nit had any problems until recently. Wifi keeps dropping and reconnecting a few seconds later. Have tried resetting my router and have completely reset my nexus to make sure its not an app. Phone was and still is completely stock 4.0.2, my Xoom has no issues on the same wireless network.
Service centre maybe?

you might want to try the recommended radio and bootloaders and perhaps another kernel (i'd recommend Fugumod kernel)
see the link for recommended radio/bootloaders in the developers section of fugumods kernel (as i cannot post links yet)

Might also want to see if there is newer firmware available for your wireless access point…

I am also experiencing drop and reconnect issues they suck on the battery
but they do not interfere with usage
Code:
Mar 24 08:13:14 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: deauthenticated due to local deauth request
Mar 24 08:13:17 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: authenticated
Mar 24 08:13:17 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: associated (aid 2)
Mar 24 08:13:17 OpenWrt daemon.info hostapd: wlan1: STA WPA: pairwise key handshake completed (RSN)
Mar 24 08:23:05 OpenWrt daemon.info hostapd: wlan1: STA WPA: group key handshake completed (RSN)
Mar 24 08:33:05 OpenWrt daemon.info hostapd: wlan1: STA WPA: group key handshake completed (RSN)
Mar 24 08:43:14 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: deauthenticated due to local deauth request
Mar 24 08:43:17 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: authenticated
Mar 24 08:43:17 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: associated (aid 2)
Mar 24 08:43:17 OpenWrt daemon.info hostapd: wlan1: STA WPA: pairwise key handshake completed (RSN)
Mar 24 08:53:06 OpenWrt daemon.info hostapd: wlan1: STA 3 WPA: group key handshake completed (RSN)
Mar 24 09:03:05 OpenWrt daemon.info hostapd: wlan1: STA WPA: group key handshake completed (RSN)
the phone looses handshake every 10min and reauthes every 30min?!?!

had this exact same problem because of restoring apps and data with google during the initial rom startup. did a complete wipe using recovery mode and skipped the google apps and settings restore at the start and it's working fine since then.

puhhh not cool but I will try it

Try ddwrt if you need a custom fw on your router, openwrt doesnt seem to cut it for you.
Try resetting your router as well or check wifi settings, try wpa/wpa2, try with open network.

İ have same issue my nexus i turned off small character to normal one and gone dropped andbewconnect issue but before i did factory reset and didnt choose my data back i load my application again
Sent from my Galaxy Nexus using XDA

Hi,
could ANYONE having had or still having the specific issue comment on this post?!?
https://plus.google.com/110074557516559184630/posts/1TSvLrXnooy
Samsung has now stopped replacing phones and is throwing the ball at Google.
Please comment on the issue with your experience and tell others of this post.

DooMMeeR said:
Hi,
could ANYONE having had or still having the specific issue comment on this post?!?
https://plus.google.com/110074557516559184630/posts/1TSvLrXnooy
Samsung has now stopped replacing phones and is throwing the ball at Google.
Please comment on the issue with your experience and tell others of this post.
Click to expand...
Click to collapse
This problem started yesterday for me. No problems before yesterday. I have been always on stock. I have IMM76I now... this is annoying...

@DooMMeeR: I think the 10 minutes are just the key-rotation interval of your AP, the periodic handshakes are pretty much normal. What isn't normal are the deauth requests. Do they happen every 30 minutes, every time?
I've recently been getting those Wifi disconnects myself. I think they've started sometime after I've gotten the 4.0.4 update.
This is what a disconnect produces in my wireless logs: (802.11g WPA2 PSK AES)
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: pairwise key handshake completed (RSN)
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 RADIUS: starting accounting session 4FB97683-00000777
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.1X: authorizing port
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: received EAPOL-Key frame (4/4 Pairwise)
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 3/4 msg of 4-Way Handshake
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: received EAPOL-Key frame (2/4 Pairwise)
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 1/4 msg of 4-Way Handshake
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.1X: unauthorizing port
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: start authentication
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: event 1 notification
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.11: associated
May 25 11:52:28 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.11: deassociated
May 25 11:52:28 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.11: deauthenticated due to local deauth request
May 25 11:52:28 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.1X: unauthorizing port
May 25 11:52:28 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: EAPOL-Key timeout
May 25 11:52:27 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:27 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: EAPOL-Key timeout
May 25 11:52:26 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:26 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: EAPOL-Key timeout
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: received EAPOL-Key 2/2 Group with unexpected replay counter
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: group key handshake completed (RSN)
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: received EAPOL-Key frame (2/2 Group)
May 25 11:52:25 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:25 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: EAPOL-Key timeout
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: EAPOL-Key timeout
May 25 11:52:25 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:25 hostapd: ath0_wlan0: WPA rekeying GTK
Click to expand...
Click to collapse
It looks like something fails during WPA key-rotation. (presumably the same thing for DooMMeeR)
I've now increased my key-rotation interval from 60s to 3600s to see if that reduces the annoyance of the bug... Which I'm pretty sure is not a wise thing to do from a security standpoint.
Hopefully the problem gets some attention from Google.

Well I've been having this issue. Been messing with my router and set it to channel 1 and its fine now
Sent from my Galaxy Nexus using xda premium

Please use for every Access Point an own SSID.
WiFi Roaming (same SSID on more APs) causes on my devices connection dropping.

Issues Tethering with codefireX

Hello,
I am currently running codefireX SR14. My provider is Petro-Canada Mobility. I am having issues when tethering through their "unlimited browsing service" Basically this service only allows http/SSL TCP traffic on ports 80/443.
Anyhow, I've been using autoproxy and this has allowed me greater functionality of most apps. Here lies the problem. When I attempt to tether (wifi hotspot or USB) Traffic is not being forwarded at all from the hotspot gateway. As a result, connected hosts cannot access the internet. After doing some initial troubleshooting, I have concluded the issue appears to be the OS itself.
Regardless of the situation, the hotspot gateway will not forward traffic with autoproxy connected, disconnected, or if I use my Junos VPN.
As a result I have 2 questions:
1)How does the Android tether operate?
2)Are there any "Backend" options I can access someone to force the gateway to forward traffic through autoproxy or my Junos VPN?
I have included the trouble shooting results below:
When tethered:
My PC IP = 192.168.43.83
gateway = 192.168.43.1
Ping to gateway is ok:
>ping 192.168.43.1
Pinging 192.168.43.1 with 32 bytes of data:
Reply from 192.168.43.1: bytes=32 time=23ms TTL=64
Reply from 192.168.43.1: bytes=32 time=2ms TTL=64
Reply from 192.168.43.1: bytes=32 time=1ms TTL=64
Reply from 192.168.43.1: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.43.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
This means my PC can reach the gateway fine (with autoproxy on and off) With that in mind, I try to ping the Petro-Canada proxy server:
Proxy server IP = 10.128.1.69
Ping to Proxy server fails
>ping 10.128.1.69
Pinging 10.128.1.69 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.128.1.69:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
This happens regardless if autoproxy is connected or disconnected. What this means is that the gateway traffic on my phone is not being properly forwarded.
When I usb tether it's the same issue:
PC IP:192.168.42.142
Gateway:192.168.42.129
Ping to gateway is ok:
>ping 192.168.42.129
Pinging 192.168.42.129 with 32 bytes of data:
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.42.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Ping to Proxy server fails
>ping 10.128.1.69
Pinging 10.128.1.69 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.128.1.69:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
This happens regardless if autoproxy is connected or disconnected. What this means is that the gateway traffic on my phone is not being properly forwarded.
At this point I believe the issue to be Android OS. I am running Jellybean 4.2.2, I also have Junos VPN installed, and I have full internet from my phone when connected (all ports tcp/udp) through Petro-Canada unlimited browsing. I still run into the same issue where trying to ping any outside IP results in a timeout. (i.e Google DNS 8.8.8.8)

I fixed the issue. I'm not sure if it's the ROM or my provider.

[Q] Trouble Connecting to VPN Over T-Mobile 4G

Is anyone else having trouble establishing a connection to a PPTP VPN over T-Mobile's network? Whenever I try to connect to my home VPN, the initial request is received by my wireless router (which hosts the VPN, router is an Asus RT-N53), but the connection hangs until it times out on my phone (displays connecting for some time and then disconnected). However, when I tried connecting to my VPN over multiple different wifi networks, it worked perfectly every time, leading me to believe it's a problem with T-Mobile's network. From what I've researched so far, there's conflicting reports whether T-Mobile blocks VPN connections or not. How can I fix this issue? Thanks.
Here's the log from my router:
Code:
Oct 23 17:56:27 pptpd[834]: CTRL: Client 208.54.39.193 control connection started
Oct 23 17:56:27 pptpd[834]: CTRL: Starting call (launching pppd, opening GRE)
Oct 23 17:56:27 pptp[835]: Plugin pptp.so loaded.
Oct 23 17:56:27 pptp[835]: PPTP plugin version 0.8.5 compiled for pppd-2.4.5, linux-2.6.22.19
Oct 23 17:56:27 pptp[835]: pppd 2.4.5 started by admin, uid 0
Oct 23 17:56:27 pptp[835]: Using interface ppp10
Oct 23 17:56:27 pptp[835]: Connect: ppp10 <--> pptp (208.54.39.193)
Oct 23 17:56:57 pptp[835]: LCP: timeout sending Config-Requests
Oct 23 17:56:57 pptp[835]: Connection terminated.
Oct 23 17:56:57 pptpd[834]: CTRL: EOF or bad error reading ctrl packet length.
Oct 23 17:56:57 pptpd[834]: CTRL: couldn't read packet header (exit)
Oct 23 17:56:57 pptpd[834]: CTRL: CTRL read failed
Oct 23 17:56:57 pptpd[834]: CTRL: Client pppd TERM sending
Oct 23 17:56:57 pptpd[834]: CTRL: Client pppd finish wait
Oct 23 17:56:57 pptp[835]: Terminating on signal 15
Oct 23 17:56:57 pptp[835]: Modem hangup
Oct 23 17:56:57 pptp[835]: Exit.
Oct 23 17:56:57 pptpd[834]: CTRL: Client 208.54.39.193 control connection finished

Create a new apn keeping everything similar to the tmobile one, or if you can edit it. Under APN Type, add admin after supl, Under APN Protocol change it from IPV6 to IPv4/IPV6
Sent from my SM-N900T using Tapatalk

mardukeme said:
Create a new apn keeping everything similar to the tmobile one, or if you can edit it. Under APN Type, add admin after supl, Under APN Protocol change it from IPV6 to IPv4/IPV6
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Thanks! It worked.

T-Mobile VPN access changes with Android 6.x Marshmallow?
Apologies for reviving an old thread, but since upgrading to Android 6.x Marshmallow, I can no longer connect to my PPTP VPN over T-Mobile 4G using this technique (establishing a separate APN with IPv6 disabled). Are others able to confirm this behavior with Marshmallow? [EDIT: Or any Android version. It appears the timing of T-Mobile network changes and Android Marshmallow rollout were coincidental and this behavior is likely not tied to Android specifically.]
I used this method successfully on the same device with previous Android versions. I verified IPv6 is still disabled. Same VPN setup as in the past and I'm still able to connect to the VPN over wi-fi networks, just not T-Mobile 4G, so it points to a networking issue rather than software.
[FWIW I'm not using a Galaxy Note 3, but this topic is likely device-independent.]

imit8 said:
Apologies for reviving an old thread, but since upgrading to Android 6.x Marshmallow, I can no longer connect to my PPTP VPN over T-Mobile 4G using this technique (establishing a separate APN with IPv6 disabled). Are others able to confirm this behavior with Marshmallow?
I used this method successfully on the same device with previous Android versions. I verified IPv6 is still disabled. Same VPN setup as in the past and I'm still able to connect to the VPN over wi-fi networks, just not T-Mobile 4G, so it points to a networking issue rather than software.
[FWIW I'm not using a Galaxy Note 3, but this topic is likely device-independent.]
Click to expand...
Click to collapse
Hi imit8,
Since my phone was upgraded to Android 6.x Marshmallow, I've been experiencing the same issue. I'm able to successfully connect to PPTP VPN using wifi, but not able to connect when using T-Mobile network. Please let me know if you make any progress.

f99999999 said:
Hi imit8,
Since my phone was upgraded to Android 6.x Marshmallow, I've been experiencing the same issue. I'm able to successfully connect to PPTP VPN using wifi, but not able to connect when using T-Mobile network. Please let me know if you make any progress.
Click to expand...
Click to collapse
I can confirm, not on phone, not on pc's over a dedicated T-mobile hotspot, it would appear t-mobile is blocking a port or something

Probably has nothing to do with marshmallow. I'm using a mobile hotspot + laptop and I can't vpn either. My VPN server log indicates port 47 being blocked.

I can confirm as well. Not a marshmallow issue. It's a T-Mobile issue.
I'm on Lollipop and just noticed that I can no longer connect to my home openvpn server on lte. On wi-fi it works with no issues. Same profile used to work on lte connection up until recently (I last tried it a few weeks ago I believe).
UPDATE: I did some research and more testing.
There were reports that IPv6 that is now used by T-Mobile could be the culprit. I changed my APN to IPv4, still not working.
The only way it worked is if I used TCP.
So basically, T-Mobile is doing something with the udp ports.
Could this be related to the Binge On fiasco? Because they monitor udp data for video and do their "optimization" *cough *throttling
I suspect that is the reason why openvpn through udp no longer works. Can anyone more knowledgeable chime in?
Thanks
PS. I have Binge On turned off since day 1 (on unlimited plan)

Even with deactivated AGPS: Strange SUPL connections to amazonaws

I just discovered that my lineageOS (starlte) is doing a connection to amazonaws every time I'm using GPS (doesn't matter which app). The used port indicates that its a SUPL connect for assisted GPS (which I deactivated) . But I didn't found a configuration file like gps.conf to change that. Probem is: Those SUPL requests are known to reveal IMEI and location.
Code:
starlte:/ # tcpdump -i any -s0 port 7275
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
12:01:27.77129 IP 192.168.179.29.33724 > ec2-52-34-211-161.us-west-2.compute.amazonaws.com.7275: Flags [S], seq 2728158607, win 65535, options [mss 1460,sackOK,TS val 4294942063 ecr 0,nop,wscale 6], length 0
15:06:27.777399 IP ec2-52-34-211-161.us-west-2.compute.amazonaws.com.7275 > 192.168.179.29.33724: Flags [R.], seq 0, ack 2728158608, win 0, length 0

Hi,
You should sniff the packet that are sent/received through these connections, both to know what information is leaking and to know of who are these servers.
you could setup a bridge connection on a PC , Fiddler should be the software for you. Or wireshark if you are more advanced.

I've also seen this on multiple of my past devices