[PSA] - PaaK and Pixel 7 / Pro

[hack-e]

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.

Sorry to hear. No luck yet here. I have an appointment at the local dealer on Wed morning to see if they can fix it.

Sponsored

 

[Eraser]

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.

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.

I have some VERY odd Bluetooth issues with my P7P, however it's only with certain devices. I was actually having these issues on my Pixel 5 after upgrading to Android 13. That said, I don't think the issue is with the phone but with Android 13.

When I run into these Bluetooth issues and devices won't connect for some reason. I will start by closing the related app, then toggling Bluetooth off and on again. If that still doesn't work, toggling airplane mode off and on again always does the trick. Just make sure to close the app between these attempts. When I setup PaaK I had to use that method to get through the setup process, otherwise it would get stuck part way through.

I also highly recommend deleting any old keys from the app before starting over again. In addition, delete any existing Bluetooth connections tied to the car.

 

[hack-e]

Sorry to hear. No luck yet here. I have an appointment at the local dealer on Wed morning to see if they can fix it.

The service appointment failed to fix the PaaK issue. The person who looked at the PaaK issue was very knowledgeable but ultimately unable to fix it. They were going to report the issue back to Ford.

 

[hack-e]

The service appointment failed to fix the PaaK issue. The person who looked at the PaaK issue was very knowledgeable but ultimately unable to fix it. They were going to report the issue back to Ford.

I forgot to mention that the dealership person had me do the Master Reset (which I wasn't personally brave enough to do) and that did not make things better. I wanted to be sure let people know that won't help so that they don't have to try the Master Reset and potentially lose some trip odometer history and other stuff.

 

[Eraser]

I forgot to mention that the dealership person had me do the Master Reset (which I wasn't personally brave enough to do) and that did not make things better. I wanted to be sure let people know that won't help so that they don't have to try the Master Reset and potentially lose some trip odometer history and other stuff.

Did you happen to try the steps I outlined? I've followed those steps twice and was able to setup PaaK.

 

[ElectricDriver]

I have some VERY odd Bluetooth issues with my P7P, however it's only with certain devices. I was actually having these issues on my Pixel 5 after upgrading to Android 13. That said, I don't think the issue is with the phone but with Android 13.

Yes, you do bring up a good point about Android 13. With my Pixel 5, I had zero issues with using my phone as a key for both Mach-E and Tesla Model 3, but with the introduction of Android 13, it broke a steady connection for my Tesla while the Ford worked consistently well. Google acknowledged that they changed the way low energy Bluetooth connection worked on the new OS and they eventually released an update in Beta version that took care of that. I'd have to toggle bluetooth off and on, every time. So maybe a week after I got my Pixel 7 (which didn't have any issues), my Pixel 5 worked well for both cars.

Before getting rid of the Pixel 5, I wiped it, went to the car, reset PaaK setting via General, Reset, etc, and was able to connect my Pixel 7 without any issues. It only worked for that day, and next day, toggling Bluetooth or restarting didn't help. I'd see the Fordpass app say Disconnected, and that it's trying to connect, but wouldn't connect. I then wanted to reset to try again, but the PaaK reset was greyed out like it was for "hack-e", and I've gone through master reset, etc. No luck, and it also doesn't show which profile is selected anymore and is stuck in "Guest", ugh. I took my wife's Samsung Z Flip4 to try connecting, and same situation with my phone. It's like the car doesn't respond to a connection request even though the connection for Android Auto works reliably.

I read somewhere that someone unplugged the battery from the car and it then worked out, but after having done some resets and holding down on the buttons to restart the center screen, no luck I think our cars have some glitches in there that wouldn't reset.

 

[hack-e]

Did you happen to try the steps I outlined? I've followed those steps twice and was able to setup PaaK.

Yes, I tried your steps too with no luck.
Thanks for the information though.

 

[hack-e]

Unbelievable! I have PaaK working again. I was given the potential fix information via a private message and now that I have tested it and proven it works, I am sharing. Apparently the Bluetooth module is in a bad state and must be powered off and back on.

All you have to do is pull fuse 19 (18 and 19 are together) in the BCM fuse box and put it back in, and after that PaaK setup will work again. This is the fuse box located in the panel below the glove box (I hope it's ok to show some snipits from the manual):

I watched a youtube video to understand how to remove the cover to access the BCM fuse panel. In the video the guy removes the glove box. This is not necessary. The cover that must come off is a two part hinged piece:

The bottom part can just be pulled away. For the top part, there are two clips just behind the base of the glove box (while closed) that must be pulled out (screw driver is helpful), then the top part of the plastic cover can be pulled down.

Presumably Ford is now aware of this and hopefully can modify software to not allow this module to ever get in a bad state.

 

[Eraser]

Unbelievable! I have PaaK working again. I was given the potential fix information via a private message and now that I have tested it and proven it works, I am sharing. Apparently the Bluetooth module is in a bad state and must be powered off and back on.

All you have to do is pull fuse 19 (18 and 19 are together) in the BCM fuse box and put it back in, and after that PaaK setup will work again. This is the fuse box located in the panel below the glove box (I hope it's ok to show some snipits from the manual):

I watched a youtube video to understand how to remove the cover to access the BCM fuse panel. In the video the guy removes the glove box. This is not necessary. The cover that must come off is a two part hinged piece:

The bottom part can just be pulled away. For the top part, there are two clips just behind the base of the glove box (while closed) that must be pulled out (screw driver is helpful), then the top part of the plastic cover can be pulled down.

Presumably Ford is now aware of this and hopefully can modify software to not allow this module to ever get in a bad state.

Great news glad to hear you got PaaK up and running again.

Whatever is going on with Bluetooth seems intermittent, but if it's with the car that might explain why things have been acting up. I still have the random issue of the puddle lights coming on as I approach the car but then the doors won't unlock. I hope this means there will be a fix sooner than later.

 

[ElectricDriver]

Unbelievable! I have PaaK working again. I was given the potential fix information via a private message and now that I have tested it and proven it works, I am sharing. Apparently the Bluetooth module is in a bad state and must be powered off and back on.

Wow, I'm so glad you posted this and thank you to you and to the person that sent you a PM. After trying it out with multiple devices and also trying on iOS, it was clear that it wasn't related to Android 13 or any OS, but rather on the car itself, since it wouldn't let me reset PaaK from its settings. Pulling out and resetting the fuse did the trick and I was able to connect my phone for PaaK at last! Who knows if it won't work in the near future but at least the connection is established now, yay. This also explains why when someone pulled out the connection from the battery to "restart" the car, it also worked.

I'm going to share your post with other posts I've seen where people were struggling with connections. But yes, I do hope Ford will fix these issues. My rear windows go down instead of up when we pull up the switch all the way (so that we don't have to hold it up) and it's clearly a bug, at least on my car. Thanks hack-e, and Eraser!

 

[hack-e]

Thanks hack-e, and Eraser!

Thanks should go to the person who contacted me privately and the team behind them for getting me the information. They are the problem solvers here. I just shared it publicly as soon as I knew it worked for me, so it could help others.

 

[babgvant]

I have some VERY odd Bluetooth issues with my P7P, however it's only with certain devices. I was actually having these issues on my Pixel 5 after upgrading to Android 13. That said, I don't think the issue is with the phone but with Android 13.

When I run into these Bluetooth issues and devices won't connect for some reason. I will start by closing the related app, then toggling Bluetooth off and on again. If that still doesn't work, toggling airplane mode off and on again always does the trick. Just make sure to close the app between these attempts. When I setup PaaK I had to use that method to get through the setup process, otherwise it would get stuck part way through.

I also highly recommend deleting any old keys from the app before starting over again. In addition, delete any existing Bluetooth connections tied to the car.

I'm fairly confident that something is very wrong with the Bluetooth stack in Android 13. Lots of funky issues with my P7P. Got my hands on a P6 running Android 12 to test, things that were working stopped working when it was upgraded to Android 13.

 

[Eraser]

Thanks should go to the person who contacted me privately and the team behind them for getting me the information. They are the problem solvers here. I just shared it publicly as soon as I knew it worked for me, so it could help others.

We as forum members solve way more issues

I'm fairly confident that something is very wrong with the Bluetooth stack in Android 13. Lots of funky issues with my P7P. Got my hands on a P6 running Android 12 to test, things that were working stopped working when it was upgraded to Android 13.

Agreed 100%. I'm not saying there aren't still lingering issues with PaaK but I've had my fair share of issues with other Bluetooth devices that I didn't have prior to Android 13.

 

[MacherAWD]

Running a pixel 6a with android 13 and I am in the beta program with android. I only have 1 issue with PaaK, every time I drive I get in the car starts fine, but then as I shift to leave I get a "no key detected" message, this is virtually every time I drive, I just ignore it and keep shifting and the car drives fine. Then when I exit the car I get the "key needed restart" type message, which again doesnt impact the driving.

 

[hack-e]

Running a pixel 6a with android 13 and I am in the beta program with android. I only have 1 issue with PaaK, every time I drive I get in the car starts fine, but then as I shift to leave I get a "no key detected" message, this is virtually every time I drive, I just ignore it and keep shifting and the car drives fine. Then when I exit the car I get the "key needed restart" type message, which again doesnt impact the driving.

Those sound familiar. For me, since I couldn't get PaaK to work for a month or so, I had to use the key fob daily for the first time. I was surprised that probably more than half the time I got in the car and pressed the brake and pushed the start button, it only turned on accessory power. I had to press the start button a 2nd time. The PaaK was much more reliable. I couldn't believe the key fob is worse.

Another thing that made my PaaK more reliable when walking up to the car on both my Pixel 6 and 7 Pro was to set the FordPass app to unrestricted battery, something that isn't set by default:

Sponsored