ericNdfw
Well-Known Member
- First Name
- Eric
- Joined
- May 2, 2021
- Threads
- 25
- Messages
- 436
- Reaction score
- 507
- Location
- DFW, TX
- Website
- ericsmalling.com
- Vehicles
- `21 MME Prem 4X w/GTPE wheels,`22 Hyundai Palisade
- Occupation
- Solutions Architect (software)
- Thread starter
- #1
I've been using PAAK for the last few weeks after giving my wife the key FOB to keep in her bag (she has started driving the MME more now that gas prices are so high). It was seeming like most of the flakiness I saw last year may have been ironed out by either Ford or Apple. The only regular annoyance has been "No Key Found" errors even though the phone is sitting on the charger pad, with wireless CarPlay active ?.
I have, however, found a new, reproducible PAAK failure use case: if I have my AirPod Pros connected, the doors won't unlock and power will not come on. As soon as I disconnect them, it works fine. Obviously, this is some kind of BlueTooth conflict but it's highly annoying when on a call for work to either flip to speakerphone or have to type the code and password to open and start the car.
Preaching to the choir here, I know, but IMO, Ford really needs to comp' us early buyers a 2nd key FOB.
I have, however, found a new, reproducible PAAK failure use case: if I have my AirPod Pros connected, the doors won't unlock and power will not come on. As soon as I disconnect them, it works fine. Obviously, this is some kind of BlueTooth conflict but it's highly annoying when on a call for work to either flip to speakerphone or have to type the code and password to open and start the car.
Preaching to the choir here, I know, but IMO, Ford really needs to comp' us early buyers a 2nd key FOB.
Sponsored