PaaK Pixel Performance After Google Fixed Bluetooth

[tomthetenacious]

Hello, All. How is PaaK performing for Google Pixel users after the Android OS update to fix Bluetooth connectivity? Please reply to thread with your experience.

Sponsored

 

[ashadkc9]

So, maybe mine is a unique case, but my wife has a MachE and I have a Lightning. Most days I have to turn off bluetooth and force close the Fordpass App to get it to work. What I can't do is have my wife's MachE PAAK setup as well. Every time I get into my Lightning, it won't detect the PAAK because it connects to the MachE first. Even with no keys nearby and Lightning selected in the Fordpass app. This is infuriating to me, and not sure if its a Ford or Pixel issue.

 

[tomthetenacious]

So, maybe mine is a unique case, but my wife has a MachE and I have a Lightning. Most days I have to turn off bluetooth and force close the Fordpass App to get it to work. What I can't do is have my wife's MachE PAAK setup as well. Every time I get into my Lightning, it won't detect the PAAK because it connects to the MachE first. Even with no keys nearby and Lightning selected in the Fordpass app. This is infuriating to me, and not sure if its a Ford or Pixel issue.

Hi Andrew,

You're probably referencing the fact that the app can only host one PaaK vehicle at a time. There are limitations in the Bluetooth stack which prevent hosting multiple vehicles. So, if you have multiple PaaK vehicles, for the time being you will have to manually switch to the vehicle you intend to use. For instance, to access your wife's vehicle, you have to select that vehicle in FordPass and then when you're done using her vehicle, switch back to your own. I hope that helps.

 

[ashadkc9]

Nope, not the issue. I assumed that was standard procedure. I'm saying even if I have my lightning selected, the phone connects to the MachE first and the only way to use PAAK on the lightning is to delete the Bluetooth object for the MachE, rendering it unusable. Makes no difference if I force close Ford pass, cycle Bluetooth, etc.

 

[tomthetenacious]

Nope, not the issue. I assumed that was standard procedure. I'm saying even if I have my lightning selected, the phone connects to the MachE first and the only way to use PAAK on the lightning is to delete the Bluetooth object for the MachE, rendering it unusable. Makes no difference if I force close Ford pass, cycle Bluetooth, etc.

So, you have two keys setup one for the Lightning and the second for the Mache and with the Lightning selected, you're able to use PaaK with the Mache? And the Lightning is unreliable even when selected in FordPass?

 

[ashadkc9]

So, you have two keys setup one for the Lightning and the second for the Mache and with the Lightning selected, you're able to use PaaK with the Mache? And the Lightning is unreliable even when selected in FordPass?

When I select the lightning, its just No Key Detected. When I select the MachE, I can use PAAK with the MachE. The only way I can use PAAK with the Lightning is if I select it in Fordpass, and delete the MachE from the bluetooth by clicking forget. Then that grenades the PAAK for the MachE moving forward, but the lightning works.

 

[tomthetenacious]

When I select the lightning, its just No Key Detected. When I select the MachE, I can use PAAK with the MachE. The only way I can use PAAK with the Lightning is if I select it in Fordpass, and delete the MachE from the bluetooth by clicking forget. Then that grenades the PAAK for the MachE moving forward, but the lightning works.

Does the No Key Detected LIghtning issue happen only when you are in the vicinity of both Mache and Ligthning or is it all the time?

 

[ashadkc9]

Good question, I would assume its only when I am in the garage right next to one another. I do seem to have to randomly cycle fordpass and bluetooth sometimes when I am out.

 

[bananaslug79]

I would vote here but none of the options seem to fit: hasn't made a difference.

For Sparky the PaaK is fine. Quite usable with a few random caveats that are often resolved with a phone reboot if necessary. If Sparky doesn't recognize the PaaK right away, usually opening the app (or at worst, restart the phone) will almost always fix it.

I've had two Pixel devices using PaaK with Sparky: the Pixel 8 Pro seemed to be fairly bulletproof with the above procedure only occasionally needed. Upgrading to a Pixel 9 Fold has reduced the reliability; I've always chalked that up to a difference in each devices' BT module that just seems finickier on the latter.

 

[telrod11]

Got Android 16 beta 3.2 a couple of days ago. It will take a few more days of testing to really know (for me)

Sponsored