Search results

Yeah I forgot the Wu went to work for Google and with the key attestation API he said that it was infallible. I'm still going to guess that it's because you're rooted. I have the P6P and so do many others here. I haven't seen anyone with that issue. As to what is causing it I have no idea...

As a former android ROM developer I would say that you having a rooted phone is the issue. Are you using MagiskHide? Do you pass safetynet?

Myself and many, many other's on this forum have the Pixel 6 Pro and we have no issues. Sounds like a you issue and not an app issue.

say what???? I use 1pd exclusively and have never had to blast them... "jes sayin"

Both @Neil4Real and @macchiaz-o are correct. The car will automatically put it on in certain circumstances, normally when opening a door while in drive, but there's also some vehicles that are bugged where it happens when you turn off the car. Either way, you don't have to manually disengage...

I've had my GTPE since October and I have 20k on it. I drive over 2k a month, 95% highway driving. I'm not the least bit worried that I'll have a 0.5% chance of failure. Additionally, every week I DCFC no less than twice. Statistics show that you have a 50% chance of being in a car accident...

I haven't seen a DCFC with a Slurpee machine yet, so some of us might want to go to gas stations still. Because someone is bound to comment on the above ... yes, gas stations are where you buy Twinkies as well.

No it's just not the latest. There's been two GWM updates and it installs the first-oldest. Yes

It's not just charge data. It's also the main screen % of battery left, range, ability to charge to 100%, trip data etc. What I missed the most was charge to 100% because I take a lot of longer trips and use that often. A few times I had to change my charge settings manually in the car...

From my post it's only happening to some people, not everyone. I'm not sure why it happened to some of us and not others. I just spoke with @benk016 who also confirmed 2.8.2 is the old GWM on his car, but he still has charge data.

Looks like we have confirmation that Job 2 OTA 2.8.2 installed the same GWM update that broke my charge data. Since I installed it prior to the OTA I experienced this issue ahead of what, presumably, will be an onslaught of others here with the same issue. I'll update the thread to provide...

Check here Should be: LJ8T-14J007-EKR LJ8T-14H021-EKR MU5T-14H152-EKG LJ8T-14J009-EKR MU5T-14H027-EKJ MU5T-14H151-EKG MU5T-14H394-AAE

Interesting ... Ford will get an ear full if that's the case. I just knew it was the GWM. I didn't know what version. Thank you for pointing this out!

You might have a defective unit. I would power cycle it at the breaker and see if that revolves it. Try the charger that comes with the car and start a process of elimination. Once you know what works and what doesn't you can then contact the appropriate company.

2.8.3

Negative

The update for the GWM is being rolled out OTA in power up 2.8.2. OTA 2.8.2 was the GWM release prior to this version.

If it says "ready to charge" and the light on the CPH50 is blue then the CPH50 is in communication with the car. The car isn't requesting a charge. So it's probably, as others mentioned, the cars schedule. If it the CPH50 was not in communication with the car it would say "not plugged in"...

I'm not sure where you got that I'm being defensive. You commented on my comment and I commented as a reply. That's a conversation.

You must have missed the "design" part. Design is before manufacture. If they outsourced the design too, then they are taking the blame for someone else, likely because it's still their job to verify the part will work correctly. The buck stops with them. It's their car. I have thousands of...