[PSA] - PaaK and Pixel 7 / Pro

[DevSecOps]

Does the Rivian also have 2 BT connections to the car?

There's an audio and a PaaK bond, which is the same as the MME. The double pop-up on the MME doesn't create 2 connections, it's 2 acknowledgements for the same connection. Blue is Rivian, red is the MME.

Sponsored

 

[Eraser]

I've been on A14 on my P7P for two weeks now and PaaK has been flawless since the upgrade. I've had zero issues with unlocking doors, starting the car, opening the hatch and walkaway lock. A few times when I'm driving the car it has said no key detected. This usually happens early on in the drive after Android Auto connects. I assume this a very brief disconnect as walkaway lock has never failed after exiting the car. I don't consider that a failure since it has no impact on usability.

On a slightly related note, Android Auto has only failed to connect once in this two-week period. I think the issue was with Sync, as a quick reboot of Sync and the connection was restored. In the past I would need to either toggle BT and or reboot my phone before AA would reconnect.

It has been so refreshing to have both PaaK and AA working perfectly. Neither has worked this smoothly since I got the car in early 2021. Sadly, I suspect this will be short lived. It is just a matter of time before some software update on the phone, car, or Ford pass will break things yet again. Until then, I'm going to enjoy this while it lasts.

 

[zhackwyatt]

Another reason I think it's Google's fault. This past week it's been pretty good. I started my app for my hearing aids (which is normally always running but the latest version crashes sometimes). About 20 minutes later I went to the car and it was very slow to connect and not responsive. Perhaps a combination of the two apps. More testing required.

 

[babgvant]

Applied the November Update to my P8P, and now it's as bad as it ever was with A13 and the P7P...

 

[mdpmdp]

Applied the November Update to my P8P, and now it's as bad as it ever was with A13 and the P7P...

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

 

[babgvant]

It's weird. After messing with it a bit, it looks like the issue might be that FordPass is getting scavenged to save battery by A14. When I launch FP as I approached the car (what I would do on A13), it would be in a deep sleep state (like a cold launch), and then generally connect OK. Every so often, cycling BT after re-hydrating FP was necessary.

I am seeing slightly better reliability after I changed the battery optimization settings around, then put them back to where they should be.

 

[MacherAWD]

It's weird. After messing with it a bit, it looks like the issue might be that FordPass is getting scavenged to save battery by A14. When I launch FP as I approached the car (what I would do on A13), it would be in a deep sleep state (like a cold launch), and then generally connect OK. Every so often, cycling BT after re-hydrating FP was necessary.

I am seeing slightly better reliability after I changed the battery optimization settings around, then put them back to where they should be.

Do you have Fordpass set to unrestricted access, or did you do something somewhere else with battery optimization?

 

[babgvant]

Do you have Fordpass set to unrestricted access, or did you do something somewhere else with battery optimization?

Yep. Unrestricted. I changed it to one of the other settings and exited out, then came back in and changed it back to Unrestricted.

FordPass still seems to get dehydrated if I haven't opened it or driven the car for longer than a day, but for the most part it seems to be working better now. I don't know if that did or anything though, seems crazy that it would.

 

[mdpmdp]

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

 

[DevSecOps]

I really can't believe you guys are on page 20 of this mess.

Here's the TLDR for this thread:

Android OS 12 (P6):

It works
It doesn't work
It's google's fault
Maybe it'll be better in OS 13

Android OS 13:

The new OS fixed it
The new OS didn't fix it
It's google's fault
Maybe it'll be better in OS 14

Android OS 14:

The new OS fixed it
The new OS didn't fix it
It's google's fault

Can't y'all see the trend here? It's FordPass that is messing with BT. No matter how many times you hope for Google to fix it, it never fixes it. It's the same thing every year. Process of elimination.

Now that I don't have FP on my phone anymore nothing messes up. I never have PaaK issues with the R1T, I never have Bluetooth issues with my pods or anything else for that matter. I always had issues when FP was installed. Try it... remove FP and let me know how things work.

 

[mdpmdp]

Can't y'all see the trend here? It's FordPass that is messing with BT. No matter how many times you hope for Google to fix it, it never fixes it. It's the same thing every year. Process of elimination.

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 on P7P), which leads me away from FP.

 

[DevSecOps]

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 on P7P), which leads me away from FP.

I don't see the commonality with Google. I had the same issues with my P8P, but you don't, and in the P8P thread others are reporting the same issue.

I understand your point, but apps need to be designed for a variety of phones, their hardware and software. There's many times where apps work fine on Samsung phones but don't on Pixel phones, that's not an Android issue, it's an app issue. Additionally the Pixel series doesn't have the same hardware as it did in previous years, the BT radio firmware is different, the OS is different. The only thing that's remained constant over the last 3 iterations is FP.

 

[mdpmdp]

I don't see the commonality with Google. I had the same issues with my P8P, but you don't, and in the P8P thread others are reporting the same issue.

I understand your point, but apps need to be designed for a variety of phones, their hardware and software. There's many times where apps work fine on Samsung phones but don't on Pixel phones, that's not an Android issue, it's an app issue. Additionally the Pixel series doesn't have the same hardware as it did in previous years, the BT radio firmware is different, the OS is different. The only thing that's remained constant over the last 3 iterations is FP.

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 inherently obvious that all users have FP installed)

 

[MacherAWD]

I don't see the commonality with Google. I had the same issues with my P8P, but you don't, and in the P8P thread others are reporting the same issue.

I understand your point, but apps need to be designed for a variety of phones, their hardware and software. There's many times where apps work fine on Samsung phones but don't on Pixel phones, that's not an Android issue, it's an app issue. Additionally the Pixel series doesn't have the same hardware as it did in previous years, the BT radio firmware is different, the OS is different. The only thing that's remained constant over the last 3 iterations is FP.

My PaaK was basically flawless until Dec 22, then my pixel took the update with revamped Bluetooth, it's been hit or miss since. My phone has issues after I connect to other devices.

 

[DevSecOps]

My PaaK was basically flawless until Dec 22, then my pixel took the update with revamped Bluetooth, it's been hit or miss since. My phone has issues after I connect to other devices.

And you probably said the same thing a year ago and 2 years ago etc.

If Android changes the way their OS works, as an example, it's up to the developers of apps to update their apps to comply. Every time there's an update I get an email to ensure my apps are compatible with the next release and detailing changes, breaking changes and new features. I'm sure you've had other apps break due to OS updates in the past, right? Do you complain to the app developer or Google? You complain to the app developer and they then bring their app into compliance. Google doesn't update Android OS to make apps work correctly.

Sponsored