We have a car that supports android auto wired (Not wireless)
When my dads phone is connected and someone is scrolling true spotify it keeps coming up with a safety break every few seconds or so. Is their some way to disable this without rooting the device he is using a Pixel 7? My phone does not have this issue and i can scroll all day long without it coming up but i am using a P7P with Graphene OS so i suspect it is some kind of permission AA doesn’t have in my case.
I get that the safety break is supposed to be a “feature” to keep your eyes in the road. in practice it does the opposite as you are looking at the screen waiting for it to pass so you can go on with the scrolling.
There is no good fix. It’s a Google thing. People have tried using roots and OBD2 fixes, but there is no easy solution.
I don’t know the Spotify app that well, but it should be possible to scroll through songs on a playlist using controls on the steering wheel or voice control. Those methods shouldn’t trigger the scroll warning.
Alternatively, he could skip Android Auto and use Bluetooth instead if it’s only connected for the music. That’s what I do for other music apps and the steering wheel controls also work just fine that way too as long as I have prepared a playlist in advance.
He is also using it with maps which doesn’t work with Bluetooth. Steering wheel allows scrolling true the current playlist not select others. Voice control is more then useless it for some reason can not get a single word right and makes a mess of things.
I have also seem more complicated fix attempts by tricking a parking break sensor or something but that isn’t possible with this car (Audi etron)
I’ve never seen the safety break feature on my phone - looked into “settings” -> “app info” for “android auto” just now.
The thing that stood out to me: I’ve disabled the ability to overlay onto other apps.
Maybe this works for you too…
This is like a feature that seems well intentioned but dangerous anyway, like the Apple look at screen to unlock feature. Hope you succeed in disabling this feature.
Android cannot know who is scrolling but it does know it is connected to a car. The obvious solution is to disconnect it from the car in order to scroll through the app. It’s completely insane to use a phone while driving and that’s the origin of the message. Attempting to subvert that mechanism is asking for trouble.
Just because the phone is connected to the car doesn’t mean that the driver of said car is using the phone, or that the phone even belongs to the person driving.
It is Android’s job to provide music and entertainment to my car’s head unit. It is my job to drive safely. It is NOT the job of Android to make sure I’m driving safely. Why in the hell should my passenger have to sit through repeated “safety breaks” while they try to scroll down to play a new song?
That’s the point I’m making, android cannot know who is driving and has to assume it’s the user of the phone because that is the safest assumption. There should be an option to accept liability for using the phone and driving but that may not be legally defensible. Sexy people outside my window should also sign disclaimers because I keep crashing my car looking at them.
Indeed just issuing a warning at connection or so “keep in mind to drive safely and keep an eye on the road” would be more appropriate IMHO. There is the same kind of restrictions with Waze, you cannot access the keyboard when driving and are forced to use the speech recognition which is often difficult (especially in foreign countries where street names are in foreign language).
You may very well use it safely but many other people certainly do not. Personally I appreciate not having my life in their careless and inattentive hands.
Why in the hell should my passenger have to sit through repeated “safety breaks” while they try to scroll down to play a new song?
They shouldn’t. But Android doesn’t know who’s holding the phone.
I have the AAWireless dongle for my car and one of the advanced options is to “remove tap restriction” to allow over 6 taps in succession. Bonus, you can convert wired AA to wireless AA.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
There is no good fix. It’s a Google thing. People have tried using roots and OBD2 fixes, but there is no easy solution.
I don’t know the Spotify app that well, but it should be possible to scroll through songs on a playlist using controls on the steering wheel or voice control. Those methods shouldn’t trigger the scroll warning.
Alternatively, he could skip Android Auto and use Bluetooth instead if it’s only connected for the music. That’s what I do for other music apps and the steering wheel controls also work just fine that way too as long as I have prepared a playlist in advance.
He is also using it with maps which doesn’t work with Bluetooth. Steering wheel allows scrolling true the current playlist not select others. Voice control is more then useless it for some reason can not get a single word right and makes a mess of things.
I have also seem more complicated fix attempts by tricking a parking break sensor or something but that isn’t possible with this car (Audi etron)
Yes Android Auto is needlessly complex. I don’t think the parking sensor is the cause anyway.
Perhaps there are some options on the phone to disable screen takeover or pop-ups or something. Deleting all app permissions is my best guess.
I’ve never seen the safety break feature on my phone - looked into “settings” -> “app info” for “android auto” just now.
The thing that stood out to me: I’ve disabled the ability to overlay onto other apps.
Maybe this works for you too…
This is like a feature that seems well intentioned but dangerous anyway, like the Apple look at screen to unlock feature. Hope you succeed in disabling this feature.
Android cannot know who is scrolling but it does know it is connected to a car. The obvious solution is to disconnect it from the car in order to scroll through the app. It’s completely insane to use a phone while driving and that’s the origin of the message. Attempting to subvert that mechanism is asking for trouble.
Just because the phone is connected to the car doesn’t mean that the driver of said car is using the phone, or that the phone even belongs to the person driving.
It is Android’s job to provide music and entertainment to my car’s head unit. It is my job to drive safely. It is NOT the job of Android to make sure I’m driving safely. Why in the hell should my passenger have to sit through repeated “safety breaks” while they try to scroll down to play a new song?
That’s the point I’m making, android cannot know who is driving and has to assume it’s the user of the phone because that is the safest assumption. There should be an option to accept liability for using the phone and driving but that may not be legally defensible. Sexy people outside my window should also sign disclaimers because I keep crashing my car looking at them.
Indeed just issuing a warning at connection or so “keep in mind to drive safely and keep an eye on the road” would be more appropriate IMHO. There is the same kind of restrictions with Waze, you cannot access the keyboard when driving and are forced to use the speech recognition which is often difficult (especially in foreign countries where street names are in foreign language).
You may very well use it safely but many other people certainly do not. Personally I appreciate not having my life in their careless and inattentive hands.
They shouldn’t. But Android doesn’t know who’s holding the phone.
I mean if you look at it that way anyone just using a car is a security risk at that point.
You’re exactly right, which is why cars are legally mandated to have a myriad of safety systems.
Dude. Don’t text and drive.
If you must, try to pull over and proof-read before hitting that send button.
It is not about texting at all. Just stupid that you can not properly control some music.
I’ve used Android Auto for years on different Pixels but I’ve never seen a “safety break”. Maybe it’s the car?
I have the AAWireless dongle for my car and one of the advanced options is to “remove tap restriction” to allow over 6 taps in succession. Bonus, you can convert wired AA to wireless AA.
That sounds interesting. Strange that their is only a option for wireless aa though.
You need something in between to intercept the data and it just so happens that AAWireless works for that too while it’s acting as a wireless bridge.