Paulw11
Member
- First Name
- Paul
- Joined
- Oct 6, 2020
- Threads
- 0
- Messages
- 6
- Reaction score
- 5
- Location
- Hartley, Australia
- Vehicle(s)
- 2020 Ranger Wildtrak
I have had this same issue and have been cursing the Ford app developers, but I think the issue is with Apple.
I am an iOS developer so I know where to look for more information on what apps are doing;
if you have opted in to share data with app developers when you set up your device you can go to “Analytics & improvements-> Analytics data”
In privacy settings to find various log files.
Looking in the tree I can see numerous reports about the Ford Pass app’s high CPU usage.
What is interesting is that the fault is shown to be in the external accessory framework; this is the part of iOS that handles devices connected via USB cables. I suspect the trigger for the problem is connecting to your car via CarPlay, which is why the app seems ok for a while and then the problem comes back.
In summary, I think Apple needs to fix this not Ford.
I am an iOS developer so I know where to look for more information on what apps are doing;
if you have opted in to share data with app developers when you set up your device you can go to “Analytics & improvements-> Analytics data”
In privacy settings to find various log files.
Looking in the tree I can see numerous reports about the Ford Pass app’s high CPU usage.
What is interesting is that the fault is shown to be in the external accessory framework; this is the part of iOS that handles devices connected via USB cables. I suspect the trigger for the problem is connecting to your car via CarPlay, which is why the app seems ok for a while and then the problem comes back.
In summary, I think Apple needs to fix this not Ford.
Sponsored