Carplay motion restrictions

[Crewbert]

Hi guys

New to the forum, and fairly new to owning a Ford. I’ve driven almost exclusively Honda vehicles for the past 15-20 years. I love the ‘25 Lightning I bought this summer, very happy with the purchase. But there’s one little quirk that’s really pissing me off that I never had with any of the Honda vehicles I had.

In the Ford, while using Carplay, I’m restricted from using some controls when in motion. There are no restrictions like this with Honda. Numbers are one thing that are a no-no with Ford. If I call a 1-800 number and a machine answers, and tells me to “push 2 for english” or something like that, I can’t push 2 unless I pull over and come to a complete stop, or lift up my phone and select “i’m not driving” and then go in through my phone to hit 2.

Another thing is in the Music app. For some reason, I’m restricted from picking any artist I want in my library. I can only select “recently added artists”.

What kind of stupid feature is this that makes me even more distracted by having to open up my physical phone in order to do what I need to do? There’s probably other features that are locked but those two are things I’ve needed many times and can’t do. I think Ford is doing this thinking that hitting buttons is distracting, but what’s more distracting is getting frustrated that you can’t hit the button, and then picking up your phone, and scrolling through settings on your phone while you’re driving. It’s not like I’m trying to play Tetris while I’m driving or something, I just want to hit a number or pick an artist that’s not a “recently added” artist. Does anyone know how to fix this? Is there a Forscan mod to get rid of the motion restrictions in Carplay?

Thanks for the help

Sponsored

 

[Scorpio3d]

I don’t think I have that problem with CarPlay and I don’t remember changing any settings, but you might run through your menu on the truck (or maybe the phone )and check there?
I’m guessing you would need to be in your vehicle with it running and connected, but I could be wrong.
Also, you can just use the voice controls for choosing the songs or artists but probably not for selecting a number on your phone. I use the voice controls for all kinds of things whether it’s for the vehicle or things through my phone!

 

[Heliian]

Switch to Android?

Maybe time for a new phone?

 

[jpatt2020]

Apple car play sucks. Android auto is so much better. I have an Iphone and a Samsung, and I exclusively use android auto from my Samsung since it's leaps and bounds ahead of apple, just like most other things on the Android over the Apple (except imessage--only reason to buy the inferior phone).

 

[ClevelandBeemer]

This is not a CarPlay issue Apple haters. This has to do with Fords implementation of CarPlay. Ford has chosen to lock out keyboards while in motion.

 

[jpatt2020]

All I'm saying is that's not how it is in Android Auto. But my Carplay locks a lot of things out. Maybe Ford, Maybe Apple. Apple develops Carplay, not Ford. Google develops Android Auto. Ford just has to follow suit with Google and Apple developers.

 

[ClevelandBeemer]

All I'm saying is that's not how it is in Android Auto. But my Carplay locks a lot of things out. Maybe Ford, Maybe Apple. Apple develops Carplay, not Ford. Google develops Android Auto. Ford just has to follow suit with Google and Apple developers.

Again, it’s Fords implementation of CarPlay. Ford sets the parameters for the CarPlay instance connected to the vehicle. So your assertion is just plain wrong…… That’s why none of my BMW’s have this restriction because they have not locked keyboards in motion for CarPlay..

 

[jpatt2020]

Intersting....I'll have to test with the X7. I rarely use carplay anymore since Android Auto is leaps and bounds ahead in my experience using both. Especially in the beemer, where Android/Google Maps is the native software, so AA should function better.

 

[16cards]

Hi. Mobile app developer here. The in-motion "feature" you are describing is guidance by the National Highway Traffic Safety Administration of the Federal Department of Transportation. It is worth noting that it is non-binding and not law, but is a very, very strong recommendation. This might explain why it is inconsistently implemented across carmakers. But it is very likely that all carmakers will implement in-motion limitations at some point.

The NHTSA proposal goes as far back as 2013, but were updated in 2019 when CarPlay and Android Auto, along with enhanced carmaker infotainment systems. The guidelines center around acceptable criteria...

for driver glance behavior where single average glances away from the forward roadway are 2 seconds or less and where the sum of the durations of all individual glances away from the forward roadway are 12 seconds or less while performing a testable task, such as selecting a song from a
satellite radio station.

Ford's SYNC apps and settings also implement limited options when the vehicle is in motion.

The way this works is that the integration between Fords Sync and CarPlay includes a signal to the iPhone that the vehicle is in motion. The Apple guidelines for implementing CarPlay apps describe the "feature" with this language:

Some cars limit keyboard use and the lengths of lists while driving. iOS automatically disables the keyboard and reduces list lengths when the car indicates it should do so. However, if your app needs to adjust other user interface elements in response to these changes, you can receive notifications when the limits change. For example, you may want to disable a keyboard icon or adjust list items when list lengths are shorter. Use CPSessionConfiguration to observe limitedUserInterfaces.

It is worth noting that CarPlay apps utilize screen templates and cannot draw arbitrary user interfaces. These templates automatically change based on the vehicle signaling to the iPhone that it is in motion.

Android Auto also implements similar screen template restrictions.

In summary, both CarPlay and Android Auto will respond to a vehicle signaling that the vehicle is in motion. The extent in which they modify the user interface is slightly different between their implementations. Further, carmakers are responsible for signaling to iPhone and Android devices that the vehicle is in motion, thus attributing to inconsistent behavior across vehicles.

For reference, here is a video screen capture of the CarPlay simulator running on my MacBook connected to my real iPhone. The simulator allows me to toggle between "Full" and "Limited" to simulate the in-motion signal from the vehicle to the iPhone.

 

[ZSC100]

Again, it’s Fords implementation of CarPlay. Ford sets the parameters for the CarPlay instance connected to the vehicle. So your assertion is just plain wrong…… That’s why none of my BMW’s have this restriction because they have not locked keyboards in motion for CarPlay..

If what you're saying is true then why do all the magic box type devices (There are over a dozen) use carplay with zero restrictions.

 

[ClevelandBeemer]

If what you're saying is true then why do all the magic box type devices (There are over a dozen) use carplay with zero restrictions.

That exactly proves my point. The device developers chose to not restrict anything on those devices, that’s way many of them allow video streaming. Ford on the other hand chose to restrict this functionality.

 

[ZSC100]

That exactly proves my point. The device developers chose to not restrict anything on those devices, that’s way many of them allow video streaming. Ford on the other hand chose to restrict this functionality.

Ford doesn't restrict anything on my CarPlay MagicBoxes. I can do everything on the screen as if it were a phone. This leads me to believe it is Apple's problem.

 

[jpatt2020]

Why would things be restricted by Ford in Car Play, but not Android Auto. I can do anything when connected to my Samsung, and nothing when connected to my Iphone. It's crippling, and almost makes Carplay worthless. Very large inconsistencies between the two. I can even type on a keyboard when using AA, but only voice on carplay. Really I see almost nothing limited on AA when in motion.

I guess maybe just two different programmers at Ford? Or just inconsistencies they aren't aware of/haven't caught yet. Who knows.

 

[ClevelandBeemer]

Ford doesn't restrict anything on my CarPlay MagicBoxes. I can do everything on the screen as if it were a phone. This leads me to believe it is Apple's problem.

That’s because your MagicBoxes are the host of the CarPlay instance, bypassing the Ford hosted implementation…..

Again, this is a Ford problem. You bypassed the Ford Sync system and magically the problem is solved.

 

[ClevelandBeemer]

Why would things be restricted by Ford in Car Play, but not Android Auto. I can do anything when connected to my Samsung, and nothing when connected to my Iphone. It's crippling, and almost makes Carplay worthless. Very large inconsistencies between the two. I can even type on a keyboard when using AA, but only voice on carplay. Really I see almost nothing limited on AA when in motion.

I guess maybe just two different programmers at Ford? Or just inconsistencies they aren't aware of/haven't caught yet. Who knows.

Wait…. You’re surprised to hear there’s inconsistency in technology implementation at Ford?

This is yet another glimpse is the fragmented nature of Fords development. Given all the goofy issues with these trucks, it’s very clear there are many teams that don’t talk to each other.

Sponsored