Search results

Just popping in to say that my phone automatically rebooted after applying the latest update earlier last week and I've still had no issues with PaaK on P8P.

Sure, and yet FP works fine on my P8P and not on yours - so it's also not that simple either. I still believe the fault is at Google's feet. I posted a bugtracker a while back that seems to be exactly our issue, and that was a more generic issue (i.e. not specific to FP, or at least not...

You say that, and you do have some compelling data re: your Rivian, but the other common thread is Google... Specifically that Pixels are vastly over-represented in this issue, and at least in my case, PaaK on P8P so far has been literally flawless for a month now (while making me bash my brain...

I have the update installed and ready for reboot but I've purposely held out. I'll give an update here... eventually

Well, that makes me want to never update...

I was basing it around this update on the Android widget which stated that some API changes had disabled certain features, and then the next update stating the old API was shutdown and pending the release of a public API. My HA integration died at the same time (I incorrectly attributed both...

Mine stopped pulling info/updates back in October and I haven't been able to get it linked again. I'll have to look at it again later today.

I thought the HA integration was broken? At least it has been for me since October, and others (based on what I read), due to API lockdowns on Ford's end.

My P8P luckily has not broken at all and honestly my QoL has gone up significantly. I dread the day it (inevitably) breaks

You had issues with P8P + A14? Mine has had no issues and I've had it for ~1.5 weeks now and driven a lot.

I didn't take any betas, had the issue starting with March security update and never resolved (including sideloading A14 to my P7P) until I got the P8P. I didn't do this myself but there's not much to lose. In theory that is one difference between my P7P and P8P but I'm not convinced that was...

I received my Pixel 8 Pro and set up PaaK, it has worked flawlessly for about a week now. Seems like a cluster... Some combination of P7 (or older phones) + FP + A13/A14? My experience on P7P + A14 was the same as @zhackwyatt, it worked for a few days then went back to being terrible.

I very vividly remember the March update timeframe being where my PaaK broke horrendously. I'm sure I could find evidence of that somewhere in my chat histories or something if I looked. Prior to that, it worked 99% of the time

Can't be bothered to look for it now but I thought there were also reports further back in this thread that downgrading to a previously working FP version still didn't work. Your data is compelling, it just seems to be too highly coincidental for a lot of us to start seeing the issue with the...

Thanks, good info - although that probably is worse because I trust Ford even less to fix it if so. And annoying that iPhone users don't have the same issue. IIRC this occured with March Pixel update though and other Android OEMs don't seem to be affected?

Second or third day on A14 and PaaK already failed for me this morning. Force closed the app and started it up again to connect, then when I got to work I checked the app and it was showing disconnected and the dash had key not detected when I turned the car off. This issue is annoying me to no...

Android 14 is officially released. Hope it fixes PaaK for everybody. I'm on a trip and won't be back until the 8th to test.

To the surprise of nobody, September's A13 update still hasn't resolved the issue (for me). Patiently (or perhaps impatiently) waiting for A14 next week...

Looks like another month for those of us not on the beta. I thought this might happen based on the extra betas. Just hope the issue is actually fixed in the full release.

The fact that they were supposed to release 4 betas, then released 5, then 5.1, and now 5.2, says that's not happening any time soon