[Nexus 6P Android Development] Beakhole:
Alright, I really need some help. I searched and saw that one other person experienced this issue but no one ever responded to them.

My wife has the 6P and is running PureNexus 6.1.1 from 20170821 and running Dynamic GApps. She's also running ElementalX kernel.

Her phone has been just fine on this version of the rom up until about 2 months ago. Seemingly out of nowhere, every time she'd try to load a web page in either Chrome or Firefox it'll take over 3 minutes to load. She'll also send a message with Facebook Messenger and it'll take a couple minutes to actually send. This persists even after wiping app data for Chrome, Firefox, and Messenger and even after uninstalling the apps and reinstalling them. This is while she's on WiFi and LTE. We have gigabit internet from Google Fiber and right after trying to load a slow web page, I'll run a quick speed test on her phone and she's getting 100+ down and up. She'll turn off wifi and switch to her Project Fi LTE and the web pages and fb messenger will do the exact same thing. A speed test on LTE says she's getting at least 30 down.

Probably the weirdest thing that happens at the same time as all this is that her clock will start displaying the time 56 minutes slower than what the correct time is.

So, naturally, the first thing I did was completely wipe her phone and do a clean reinstall. That seemed to do the trick until about a week went by. Then the slow crap and messed up time in the clock started happening again.

So I clean reinstalled again. Same thing. After a week or so, same crap.

In total, I've wiped and reinstalled 3 or 4 times now and it persists each time after about a week.

So today I had the idea to run a ping test on her phone to Google while a web page was taking forever to load. This is on our super fast Google Fiber btw:

root@angler:/ # ping -c 40 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
40 packets transmitted, 0 received, 100% packet loss, time 38998ms

1|root@angler:/ #

So it's just 100% packet loss to Google. What the crap?

I then immediately ran the same ping on my Nexus 6 (running PN 6.1.1, 20170821, with ElementalX kernel and Dynamic GApps) and it pinged just fine:

root@shamu:/ # ping -c 40 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=25.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=25.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=19.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=25.1 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=25.1 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=57 time=25.9 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=57 time=22.3 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=57 time=25.8 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=57 time=25.5 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=57 time=25.0 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=57 time=24.9 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=57 time=25.5 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=57 time=24.9 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=57 time=19.9 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=57 time=19.6 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=57 time=24.7 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=57 time=26.0 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=57 time=25.6 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=57 time=25.9 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=57 time=25.0 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=57 time=25.1 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=57 time=25.0 ms
64 bytes from 8.8.8.8: icmp_seq=23 ttl=57 time=25.0 ms
64 bytes from 8.8.8.8: icmp_seq=24 ttl=57 time=25.0 ms
64 bytes from 8.8.8.8: icmp_seq=25 ttl=57 time=25.3 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=57 time=24.8 ms
64 bytes from 8.8.8.8: icmp_seq=27 ttl=57 time=25.8 ms
64 bytes from 8.8.8.8: icmp_seq=28 ttl=57 time=25.3 ms
64 bytes from 8.8.8.8: icmp_seq=29 ttl=57 time=25.0 ms
64 bytes from 8.8.8.8: icmp_seq=30 ttl=57 time=24.9 ms
64 bytes from 8.8.8.8: icmp_seq=31 ttl=57 time=26.2 ms
64 bytes from 8.8.8.8: icmp_seq=32 ttl=57 time=25.5 ms
64 bytes from 8.8.8.8: icmp_seq=33 ttl=57 time=25.1 ms
64 bytes from 8.8.8.8: icmp_seq=34 ttl=57 time=25.7 ms
64 bytes from 8.8.8.8: icmp_seq=35 ttl=57 time=25.1 ms
64 bytes from 8.8.8.8: icmp_seq=36 ttl=57 time=25.3 ms
64 bytes from 8.8.8.8: icmp_seq=37 ttl=57 time=25.2 ms
64 bytes from 8.8.8.8: icmp_seq=38 ttl=57 time=25.9 ms
64 bytes from 8.8.8.8: icmp_seq=39 ttl=57 time=25.5 ms
64 bytes from 8.8.8.8: icmp_seq=40 ttl=57 time=24.9 ms

--- 8.8.8.8 ping statistics ---
40 packets transmitted, 40 received, 0% packet loss, time 39063ms
rtt min/avg/max/mdev = 19.664/24.878/26.252/1.560 ms
root@shamu:/ #

I'm all out of ideas on what to do to fix her phone.

Has anyone else seen this? Does anyone have suggestions on what I can do to fix her phone? It's extremely frustrating to her.