[XPOSED][MOD][LP+] Sensible Android Auto:Xposed

[thxcertified]

Would you be able to find the German verbiage in the attached strings.xml? An exact match would help out tremendously.

As shmykelsa already mentioned I'm also almost sure it's the string below. I have to drive to work in 45 minutes and I'm gonna verify it on the way and get back to you again.

<string name="park_to_use_keyboard">Zum Verwenden der Tastatur Fahrzeug anhalten</string>

 

[thxcertified]

Would you be able to find the German verbiage in the attached strings.xml? An exact match would help out tremendously.

So the exact wording is "Während der Fahrt nur Spracheingabe" and is unfortunately nowhere to be found in your strings xml. Tapping on the field directly activates voice control without a keyboard to pop up.

 

[agentdr8]

So the exact wording is "Während der Fahrt nur Spracheingabe" and is unfortunately nowhere to be found in your strings xml. Tapping on the field directly activates voice control without a keyboard to pop up.

Hmm, I'll have to see if I can find that string in GMaps. Am I correct in assuming it only happens when using Google Maps via Android Auto?

 

[thxcertified]

Hmm, I'll have to see if I can find that string in GMaps. Am I correct in assuming it only happens when using Google Maps via Android Auto?

That's absolutely correct, just tested it. Everything is normal on the phone while driving.


I just added 2 photos of my test this noon. One while standing, one while driving.

 

[shmykelsa]

Hmm, I'll have to see if I can find that string in GMaps. Am I correct in assuming it only happens when using Google Maps via Android Auto?

Actually whenever an app requires an input via Keyboard. So it could also be Waze or CarStream

 

[agentdr8]

Actually whenever an app requires an input via Keyboard. So it could also be Waze or CarStream

Interesting. Then it likely isn't the navigation apps themselves. But I find it odd that the localizations aren't present if AA is responsible for blocking input into those text fields.

Do both of you have integrated Android Auto-capable head units in your vehicles? It might be something specific to the OEM integrations, in which case it's a car sensor class that I need to override.

I'll have to see what my aftermarket head unit shows when trying to input text while moving.

 

[shmykelsa]

Interesting. Then it likely isn't the navigation apps themselves. But I find it odd that the localizations aren't present if AA is responsible for blocking input into those text fields.

Do both of you have integrated Android Auto-capable head units in your vehicles? It might be something specific to the OEM integrations, in which case it's a car sensor class that I need to override.

I'll have to see what my aftermarket head unit shows when trying to input text while moving.

Yeah my car has Android Auto natively, but are you sure localization are missing? Because Italian localization are there.

 

[agentdr8]

Yeah my car has Android Auto natively, but are you sure localization are missing? Because Italian localization are there.

I meant as verbatim from the screenshot. Unless the German localization for that string gets presented differently?

So what @thxcertified showed in the picture, the phrase when the text field is blocked is exactly: Während der Fahrt nur Spracheingabe

But what I see in the strings.xml for all de-variants is: Sprachsuche während der Fahrt

This is for the voice_search_title string, which may or may not be the correct string value for that textview.

The two strings that stand out in the GMaps package are these:

<string name="CAR_SEARCH_ALL_DESTINATIONS_HINT">Search all destinations</string>
<string name="CAR_VOICE_ONLY_WHEN_DRIVING">Voice only while driving</string>

The first looks like what could be translated to "Alle Ziele durchsuchen", and the second might end up as "Während der Fahrt nur Spracheingabe", but since there are no values-de/strings.xml located within the Gmaps apk, I'm not sure how it's localizing those strings into German.

 

[shmykelsa]

I meant as verbatim from the screenshot. Unless the German localization for that string gets presented differently?

So what @thxcertified showed in the picture, the phrase when the text field is blocked is exactly: Während der Fahrt nur Spracheingabe

But what I see in the strings.xml for all de-variants is: Sprachsuche während der Fahrt

This is for the voice_search_title string, which may or may not be the correct string value for that textview.

The two strings that stand out in the GMaps package are these:

<string name="CAR_SEARCH_ALL_DESTINATIONS_HINT">Search all destinations</string>
<string name="CAR_VOICE_ONLY_WHEN_DRIVING">Voice only while driving</string>

The first looks like what could be translated to "Alle Ziele durchsuchen", and the second might end up as "Während der Fahrt nur Spracheingabe", but since there are no values-de/strings.xml located within the Gmaps apk, I'm not sure how it's localizing those strings into German.

Maybe I might be wrong but... Aren't that photo with keyboard not open? Otherwise the search bar on the top would not be visible

 

[agentdr8]

Maybe I might be wrong but... Aren't that photo with keyboard not open? Otherwise the search bar on the top would not be visible

Good point, but maybe I'm confused on the actual behavior here. Does the keyboard pop-up and is grayed out when that textview is tapped while in motion? Or does it just show a toast message, and no keyboard is presented on-screen?

My thinking was if the text within that search box changes when it senses the vehicle in motion, then it would be much easier to locate the code that handles the switching of the text labels, and then that'll lead to the input-blocking method, which could be overridden.

 

[shmykelsa]

Good point, but maybe I'm confused on the actual behavior here. Does the keyboard pop-up and is grayed out when that textview is tapped while in motion? Or does it just show a toast message, and no keyboard is presented on-screen?

My thinking was if the text within that search box changes when it senses the vehicle in motion, then it would be much easier to locate the code that handles the switching of the text labels, and then that'll lead to the input-blocking method, which could be overridden.

When in movement and open an editText, by default AA says to check out phone's keyboard and no keyboard is shown at all. If then you tap on a symbol on the phone's keyboard, it will say to park the car

 

[thxcertified]

My car also has the android auto natively with the inbuilt panel.

When I click on the "Während der Fahrt nur Spracheingabe" field, it directly activates the Google voice thing, without showing a keyboard. As if I was clicking right on the mic icon.

In the "Alle Ziele durchsuchen" field (basically the same but when parked) it opens a keyboard on the screen where I can put my destination in.

 

[shmykelsa]

My car also has the android auto natively with the inbuilt panel.

When I click on the "Während der Fahrt nur Spracheingabe" field, it directly activates the Google voice thing, without showing a keyboard. As if I was clicking right on the mic icon.

In the "Alle Ziele durchsuchen" field (basically the same but when parked) it opens a keyboard on the screen where I can put my destination in.

Actually now that I remember, you are right. It won't let the keyboard show at all if you are on the go. But if you stop and then go the keyboard gets disabled

 

[agentdr8]

Thanks. It must be a CarSensor class that I'm missing, as it doesn't happen on my aftermarket AA headunit, even when in motion.

I'll see what I can find in the code.

 

[agentdr8]

Oops, double-posted.

 

[thxcertified]

Aaaaand here we go with version 5.2.501054 ??

 

[fkrrr]

Aaaaand here we go with version 5.2.501054

Does it work with 5.2?

 

[agentdr8]

Does it work with 5.2?

The current version won't likely work with 5.2. But I'll take a look at the new version and see if I can get a revised module out this week.

 

[agentdr8]

Uploaded a new release of the mod. Hopefully it works; there still isn't a 32-bit version of 5.2 available to test on my device. I found a few additional CarSensorEvent classes to override, so please let me know if any experiences have improved.

Also report any crashes with debug logs so I can try and address them.

 

[fkrrr]

AA-Version: 5.1.500644
Google: 11.3.9.21.arm64
Saax: newest

Notification don't show the message while in movement.