[PSA] - PaaK and Pixel 7 / Pro

[hack-e]

Then I used SYNC to disconnect from Android Auto and tried again... And it worked. I got the three or so bluetooth pairing request pop ups on the phone, like @DevSecOps described, with one of them prompting for a password.

I tried tried again, disconnecting from Android Auto like you mentioned, and I just never get the popups for connection.

Sponsored

 

[Sneezy]

Reset PaaK in the car before attempting to pair and that should fix it

I did this on Saturday and it solved my problem.

 

[DevSecOps]

I tried tried again, disconnecting from Android Auto like you mentioned, and I just never get the popups for connection.

I hate to ask but have you toggled BT off and on or restarted the phone. Also, does FordPass have nearby devices and location permission (at least set to while using app)?

 

[hack-e]

I hate to ask but have you toggled BT off and on or restarted the phone. Also, does FordPass have nearby devices and location permission (at least set to while using app)?

Thanks for the suggestions. I think I did BT toggle and reboot phone before, but I just tried both and still no luck. I checked the permissions and nearby devices is allowed, but location permissions were not. I will try again with location permissions.

 

[hack-e]

I did this on Saturday and it solved my problem.

Does anyone know what it means if Phone As A Key Reset is grayed out? It may be hard to see in this photo, but it is grayed out in my car:

Does it mean that it is already reset as much as it can be? If so, then I would think the problem is on the phone, but I have removed all BT remembered connections and cleaned off the FordPass app (force stopped it, cleared cache, cleared storage, uninstalled, then reinstalled). I am sure it's something simple I'm missing, but PaaK just won't complete setup.

Also, does FordPass have nearby devices and location permission (at least set to while using app)?

I checked the permissions and nearby devices is allowed, but location permissions were not. I will try again with location permissions.

I added location permissions and still could not get it to setup PaaK. It gets here:

Then in a minute or so, it goes to this:

The notifications are:

I miss PaaK.

 

[macchiaz-o]

Does anyone know what it means if Phone As A Key Reset is grayed out? It may be hard to see in this photo, but it is grayed out in my car:

Does it mean that it is already reset as much as it can be? If so, then I would think the problem is on the phone, but I have removed all BT remembered connections and cleaned off the FordPass app (force stopped it, cleared cache, cleared storage, uninstalled, then reinstalled). I am sure it's something simple I'm missing, but PaaK just won't complete setup.


I added location permissions and still could not get it to setup PaaK. It gets here:

Then in a minute or so, it goes to this:

The notifications are:

I miss PaaK.

While on the Connecting Your Ford phase, I was continuously monitoring the notifications to look for the Bluetooth pairing requests. I found that some popped up but some only showed in the notifications list.

And yeah, it's super stupid that we have to deal with crap like that and also that the timeout before reaching "connection trouble" is so short.

 

[hack-e]

I found that some popped up but some only showed in the notifications list.

Thanks for the tip. I will check on that soon.

 

[hack-e]

I found that some popped up but some only showed in the notifications list.

Thanks for the tip. I will check on that soon.

I didn't see any come up in the notifications list, unfortunately.

 

[MacherAWD]

(sorry if this is a slight thread hijack... feel free to ignore me). I set up PaaK with my Pixel 6a, and got the warning about "limited support for this device" but I was able to complete setup successfully and it seems to be working ok. But it did make me wonder what "limited support" is supposed to mean. The 6a really isn't that new of a phone at this point.

I was using PaaK on my 3a and switched to the 6a in Aug, I havent noticed any difference in phone/app performance. the 6a is working great.

 

[hack-e]

I will try to use my wife's phone and if that works, then maybe the "Phone As A Key Reset" menu item will not be grayed out. I should have thought of this earlier.

 

[DevSecOps]

I will try to use my wife's phone and if that works, then maybe the "Phone As A Key Reset" menu item will not be grayed out. I should have thought of this earlier.

Remember that for Pixel devices you need to turn off and back on Bluetooth immediately before trying a new app generated pairing request.

 

[Eraser]

PaaK has been hit or miss(mostly miss) since switching from the Pixel 5 to P7P. Walk away lock works 25% of the time. The car rarely detects me when I approach, even when it does it won't unlock any of the doors when I press the button. Oddly enough even though it won't unlock the doors with my phone I can start the car with no issues 100% of the time. I also removed PaaK and started over from scratch but it made no difference.

Oh well, these are the costs of being on the bleeding edge. Hopefully things will improve with future Android and or Power-up updates.

 

[hack-e]

I will try to use my wife's phone and if that works, then maybe the "Phone As A Key Reset" menu item will not be grayed out. I should have thought of this earlier.

Finally had a chance to try my wife's phone, a Pixel 6 all updated, formerly my phone that was paired to my MME with PaaK, and I turned off BT then back on as recommended before trying, and it also gets stuck in the same place where it's waiting for the car and it ultimately times out. With both phones having the same experience, I now think the problem is in the car software.

I really, really miss PaaK.

 

[viche12345]

PaaK has been hit or miss(mostly miss) since switching from the Pixel 5 to P7P. Walk away lock works 25% of the time. The car rarely detects me when I approach, even when it does it won't unlock any of the doors when I press the button. Oddly enough even though it won't unlock the doors with my phone I can start the car with no issues 100% of the time. I also removed PaaK and started over from scratch but it made no difference.

Oh well, these are the costs of being on the bleeding edge. Hopefully things will improve with future Android and or Power-up updates.

I'm pretty much having the same exact experience too. Walk away lock works only intermittently, and I've had trouble unlocking doors despite seeing puddle lights turn on. I also can start the car even though I've had to manually unlock via the app.

 

[ElectricDriver]

Finally had a chance to try my wife's phone, a Pixel 6 all updated, formerly my phone that was paired to my MME with PaaK, and I turned off BT then back on as recommended before trying, and it also gets stuck in the same place where it's waiting for the car and it ultimately times out. With both phones having the same experience, I now think the problem is in the car software.

I really, really miss PaaK.

Any luck? I'm exactly in your situation where PaaK used to work really well with Pixel 5, but after switching to Pixel 7, I was first able to connect to it, but after resetting PAAK setting from the car once, I'm now unable to, and it's greyed out like your screenshot. I've spent too long trying different things and I miss PaaK quite a bit, too.

Sponsored