3.29.0 Fordpass update just released

[sockmeister]

After updating the app (Pixel 5) and left PaaK running in the background things looked CRAZY good.

After coming back from lunch it took a noticeable dip of 3% in about 2 hours. Even if I round that down to 1% per hour that is still too high, but that is still night and day better than it was in prior versions.

I think the battery drain really kicks in when you connect to the car, then disconnect. When the connection is severed it aggressively looks to reconnect. The PaaK wasn't aggressively checking this time since I was already at work with I updated the app. Tomorrow I'll have a better benchmark against my theory. If I'm right, the battery drain will be around 15% after 9 hours. I like being right, but I hope for all of our sakes I'm dead wrong?.

Let us know.
I typically do a similar test after every update. I've noticed the same thing. It's definitely overcompensation with PaaK after a disconnect. It might have made PaaK more responsive, but the trade-off in battery drain is awful. I'd rather have it back before v.24 where this all started.

 

[‘64 GTO]

I received my update earlier today. I am not sure if what I just discovered is a result of that but I just found the results of all of my journeys for the week with a analysis of my driving. I have never seen this before but it sure is cool. Love this car!

 

[kevcody]

Faaaaantastic. Seemed to work OK until this AM when I realized Walk Away lock didn’t trigger…. So I tried to manually opened the app and lock remotely when the app boot crashed. Now I can’t get it to open and at all and likely will need to fully delete it and reinstall. This of course will then delete my PaaK and I’ll have to fully reenroll.

This is the second time since getting the car in July that I’ve had to delete and reinstall the app to stop it from crashing.

iPhone 12 Pro Max - 14.7.1

 

[Shayne]

Plugged in car @31% and app popped up waiting to charge. Will see what it does by tomorrow.

@DYohn it started charging at scheduled time and charged to scheduled SOC. Charging working here. No charging log but unless it makes it go faster, farther or maintains the car I am not really too concerned about that. All works fine here on limited testing. Thinking not the app that is causing your problem?

Does it behave the same with the fob? Mine did. If so, no app update will fix it. I’d try the 12v battery disconnect, that’s the fix for needing to open one door before another.

Do not have this problem but It would be nice to find a switch instead of ripping off panels to disconnect the 12V for problems like these.

I had a miserable time this morning with the car. Would not open. When I used the door code. There was no key detected. Rebooted the phone and tried again. Nothing. Bluetooth connected. Ended up using the fob. CarPlay would not work either. Went to the store and when I came back out everything was fine.

Ford Pass sucks.

Betting you bought a snickers.

 

[Kamuelaflyer]

Betting you bought a snickers.

You win the internet for the day.

 

[Jimrpa]

I had a miserable time this morning with the car. Would not open. When I used the door code. There was no key detected. Rebooted the phone and tried again. Nothing. Bluetooth connected. Ended up using the fob. CarPlay would not work either. Went to the store and when I came back out everything was fine.

Ford Pass sucks.

Oh, in other words, you had a perfectly normal PaaK experience ?

 

[Jayhawkoholic]

It seems to have fixed the buggy security alert schedule. Before it wouldn’t save a schedule for when the security alerts happened when a door has been opened.
When activating the feature before, it had to always be on- even at peak driving times so it would bombard me with texts saying the door has been open when I was driving. Now hoping it will only message me between certain hours when I’ll probably not be driving or opening my door.

 

[OH2AZ2OH]

I just had my first app crash in a long time when I got to work. No journey recorded either. I just turned journeys on, I may try turning it back off if this keeps up.

 

[DYohn]

Update re: my issue with the car charging outside of scheduled times. I drove the car to a store and back yesterday evening, and when I returned home and plugged in the schedule was in effect. So while I have no idea why or what was going on, it doesn't matter as the situation seems to have rectified itself. Thanks to everyone who chimed in to help.

 

[GoGoGadgetMachE]

I don't know if this is a new bug, but I've noticed that if I force charging to 100% (override the charging schedule), the "when charging will complete" doesn't seem to understand that. It always says it will complete when last updated - it seems to be saying "your normal charge level was complete already," which is interesting, but not what I'd want to be told.

 

[JoeDimwit]

Finger-as-a-key... Someday, someone can say, "FaaK your car!"

 

[Shayne]

I don't know if this is a new bug, but I've noticed that if I force charging to 100% (override the charging schedule), the "when charging will complete" doesn't seem to understand that. It always says it will complete when last updated - it seems to be saying "your normal charge level was complete already," which is interesting, but not what I'd want to be told.

Ok read it a few times and think I understand. It does not tell you after it reaches the schedule state of charge how long it will take to go for there to 100% when you override it? Not sure about the top end on a L2 and whether it throttles at the top as I have not tested to that extend but what I have noted it is in the 10% an hour ballpark for me. Understand that does not fix the problem but a possible workaround now it is flagged. I know 99 to 100 will take longer and it is not linear for that last percent. Maybe test 80 to 100 and note how long it takes I would be interested in your amps and your findings.

 

[JohnnyForensic]

After updating the app (Pixel 5) and left PaaK running in the background things looked CRAZY good.

After coming back from lunch it took a noticeable dip of 3% in about 2 hours. Even if I round that down to 1% per hour that is still too high, but that is still night and day better than it was in prior versions.

I think the battery drain really kicks in when you connect to the car, then disconnect. When the connection is severed it aggressively looks to reconnect. The PaaK wasn't aggressively checking this time since I was already at work with I updated the app. Tomorrow I'll have a better benchmark against my theory. If I'm right, the battery drain will be around 15% after 9 hours. I like being right, but I hope for all of our sakes I'm dead wrong?.

I don't know...1-ish% per hour for something with a constant keep-alive doesn't sound bad to me at all.

 

[Kamuelaflyer]

Oh, in other words, you had a perfectly normal PaaK experience ?

A very unusual one for me honestly. Which makes it even more frustrating and annoying. So ... normal I guess. Never mind.

 

[Woeo]

Nope.. still no option to re-enable or 'Setup Phone as a Key"... AT least my recall notice is gone.. Bright Side

Do you have two blue tooth connections? One for the car & one for Sync? There were some posts early on about enabling Sync before the car/app interfering with PAAK setup.

Sponsored