FordPass - somebody should get fired

[Dmhccs]

I've been using FordPass with our 2018 Expedition for the past four years. I honestly haven't had any issues. It reports gas level / range, and remote start and lock/unlock have always worked. The app is much reliable than our Volvo app, which is a complete disaster.

Maybe it's different with Mach-E?

I have to agree. I also have the Volvo app for my XC90 recharge. I really don’t think I’ve ever used a more frustrating app than the Volvo.

Sponsored

 

[Luke]

I could only setup PaaK two days after the car purchase, but that was back in March. When the app starts crashing like that in iOS the solution for me was to remove and reinstall the app. Thai will for sure break PaaK if you had it enabled. You would also need to remove the two Bluetooth devices the MME adds to the phone and start the process again. In some extreme cases you have to do a master reset in the car too.

I gave up on PaaK three months ago and payed for a new keyfob. After the second keyfob you can get a cheap knockoff eBay version and create a third one.

Good luck in your configuration and try not to let these issues get in the way of enjoying the car. PaaK is all frustration for now (at least it was for me).

 

[alexgorod]

• The car is in control of opening the doors and turning on.
• The FP app doesn't control what the car does, it just authenticates to the car "allowing" it to take action
• If the CAR thinks that the phone is outside the vehicle it won't turn on
• 50% of the equation is with the car and the modules/BT antennas.
• We know the location of the BT antennas as shown below
• If your modules are not updated you will have issues. This is a CAR problem and not a FP problem especially if you see it say "Bluetooth Connected" in FP.

I kinda new all that, well, except the locations of the antennas. It still doesn't answer why it has to be that sensitive to the exact location of the phone.

Thank you for the answer and the picture.

And thank god for the fob.

 

[DevSecOps]

I kinda new all that, well, except the locations of the antennas. It still doesn't answer why it has to be that sensitive to the exact location of the phone.

Thank you for the answer and the picture.

And thank god for the fob.

It's the same for a FOB. If you're outside the vehicle or if locking the FOB in the car, the car has to know where the PaaK enabled device or the FOB is located. This is, my guess, a security feature.

So if your modules/antennas aren't calibrated correctly then the car just has issues figuring out where the PaaK enabled device is. This makes more sense when you think about putting the phone towards the middle where both the front and rear interior antennas are located.

This goes back to my entire thread about the RFA update fixing a lot of the issues with PaaK. If your build date is in line with with customer satisfaction update the RFA is included in that and I would recommend it.

 

[drironman]

On a positive note...Just went out to my Premium and low and behold the Frunk does open! I tried it once in the house but didn't work. didn't realize I needed to be "near" the car. Wow so excited to put groceries in there now. Just the little things. So far so good with PAAK. did have to reset it once so not perfect but sounds like much better than some.

 

[barry2557]

Nobody has a (working) frunk button in FordPass. Some people have a non-functional frunk button

I haven’t had any problems with my PAAK. I do have a frunk icon on my app and it works.

 

[barry2557]

I'm struggling with FordPass. Same as everybody else - PaaK setup on iOS is a goat rodeo. It thinks I'm in Detroit when trying to set departure times. The thing crashes like the Hindenburg, and it times out so often that I think this is the secret name for it - Timeout! And, I have stable gig internet.

Does anybody know a feedback channel that we can use? This POS is Charlie Sheen levels of unstable.

Got my Mach-E GT a month ago. I haven’t had any problems with PAAK or Apple Car Play. I’m happy with it… so far.

 

[Ejectionseatfixer]

Havent had any issues as of yet.

 

[mkhuffman]

This makes more sense when you think about putting the phone towards the middle where both the front and rear interior antennas are located.

This could be why placing the phone on the magic charging pad before starting the car seems to work better than keeping it in a pocket near the driver door - it can better detect that the phone is inside the car. Maybe it isn't magic after all!

 

[dsuyang]

It's the same for a FOB. If you're outside the vehicle or if locking the FOB in the car, the car has to know where the PaaK enabled device or the FOB is located. This is, my guess, a security feature.

100% correct It should even know which door you are approaching and only unlock that door for you.

So if your modules/antennas aren't calibrated correctly then the car just has issues figuring out where the PaaK enabled device is. This makes more sense when you think about putting the phone towards the middle where both the front and rear interior antennas are located.

100% correct Android is much more challenging than iOS, because we could only calibrate so many popular model year, while Android has tens of thousands of model year...

This goes back to my entire thread about the RFA update fixing a lot of the issues with PaaK. If your build date is in line with with customer satisfaction update the RFA is included in that and I would recommend it.

 

[DevSecOps]

This could be why placing the phone on the magic charging pad before starting the car seems to work better than keeping it in a pocket near the driver door - it can better detect that the phone is inside the car. Maybe it isn't magic after all!

You're killing me...

 

[dsuyang]

I asked this privately, and was told there is a beta program but I too cannot find any way to join it. They're not using the Play Store beta channel so hopefully someone from Ford can let us know if they want more signal from super-engaged users.

We did terrible on the public beta testing part, TBH.
I am circulating the public beta ideas among groups. I know my boss would love it.

 

[dsuyang]

One suggestion here is perhaps the car shouldn't scream that it can't find the key as quickly as it seems to do. We all can look down at our PAAK-enabled phone or feel it in our pocket to know that this is an erroneous warning.

Showing this warning as frequently as it is doing diminishes confidence in relying on this as the mission-critical way to unlock and drive your car.

Disclaimer: My PoV does not represent Ford Motor Company.

As a MachE user, my wife and I could not agree more about annoyness of seeing those Key Not Detected on the screen.
Unfortunately as @DevSecOps mentioned, FP doesn't control that part. FP can only answer when the vehicle is asking where is the Phone/FOB? ?‍ If somehow the Bluetooth signal is weak or FP doesn't answer the vehicle's question quick enough, (it is computational heavy to jump through all the craziness of cyber security), and you see that infamous Key Not Detected. ?

 

[locks66]

Pretty sure GT/GTPE owners have a functional frunk button. I think the newer delivery Selects/Premiums do too.

Sure do in my GT!

 

[alexgorod]

Pretty sure GT/GTPE owners have a functional frunk button. I think the newer delivery Selects/Premiums do too.

My late September built Premium has a fully functioning Frunk button in FordPass v.3.35.0 on Samsung S21 powered by Android 12.

Well, it's called "Front Trunk", but I can live with that

Sponsored