• Bug FeedbackSystem bug reception

  • 241118 PIP wrong voice language selection

[1] Describe in detail the error you encountered.
If you want to enter a destination to GMaps in PIP using the voice input (this microphone)

it will only listen for English, even though the application is set to German.
If, however you use the microphone in GBoard (type into text field to bring up GBoard, then hit microphone in GBoard) it will understand German. Google Assistant also understands German. Only the voice input in PIP (circled microphone) is limited to English only.

[2] Provide screenshots of system information

[3] Whether the bug can be reproduced, reproduced is what the steps are

100% reproducible using the above steps.

I encountered the same bug. I needed to set in GMaps itself the language from system to Dutch (for you that would be German)

Thanks, yes that helped. It was on "system setting" before. Interestingly, my system is also set to German 😉 And in 241008 it worked ok on that setting. Anyway, have now changed the app language of GMaps to German and am good for now.

    My system is set to Dutch but GMaps did not pick up anymore.
    (I only change my system to English when making screenshots).

    8 days later

    On the dudu7 7870 3.5 pre-release with the 4 additional apk updates.
    My system is set to Dutch, my google Maps internal language is set to Dutch (since 241118).
    Now it is even worse. Inside GMaps, using the small microphone in the top-right of the search bar, everything I say is "interpreted" as English, leading to complete nonsense for Dutch addresses. I can't even speak English (navigate to ..) as the Dutch address is still interpreted to nonsense.
    Using the Google Assistant I can indeed speak Dutch, but it loads GMaps in full screen but with the navbar overlayed over the bottom of the GMaps screen.
    It means I have to tap the home button a few times to switch back to the pip window (dual-pip or minimal doesn't make a difference). From there I have to tap "start" again.

    a month later

    @DUDU-HUANG @YAOXILONG @DUDU-Meng

    It seems that nobody reacted on this this bug message apart from @gismo and myself. And multiple users in the telegram channels also reported it (but that's a fully unstructured flow of messages in all channels).
    It makes for me voice commands completely unusable.
    Voce commands (in English) work, but if I say something like "navigate to robijnhorst", it "tries to" translate this to " navigate to Robin hood". When I say in Dutch "navigeer naar Robijnhorst", it does not understand it at all.
    Please pay attention to this as Toppal is only for six languages and does not understand Dutch street names either.
    A big part of your users is in countries outside Toppal supported languages.

      Hello. This happens to me too, both in Maps and Chrome. I have everything set to Spanish but the instructions are "listened to" in English. I don't know what to change to make it understand me.
      I have a DUDU7 with the latest official firmware to date.
      As a curious fact, Waze does understand me when I speak to it in Spanish.

        Xkliburi You must set Spanish in the Waze app. Have you done that?

            MihaiFlorin As I said, it works fine for me in Waze.

              MihaiFlorin
              That was on the version before the 241118. In above posts you can read that both @gismo and myself did set the app language in Maps to Dutch (and German for @gismo).
              It doesn' t make a difference. It only listens to English and it did work fine at least on 241008 and before.
              It is a bug.

                  gismo I hadn't understood this answer well. I had the Maps language set to "System Default" in that option. I set it to "Spanish" and Maps now understands me when I speak to it. Thanks.

                      Xkliburi
                      I see that you are on the 241222 version.
                      It really doesn' t work for me. I just tested again.
                      It doesn' t work on 241224 (beta, not publicly available), and before that on 241222.
                      As soon as I get a new firmware it is really literally the first thing I test and it is literally my most used option before on my 7862 and in the first releases on my dudu7.
                      So strange (but good for you).

                        • Ggismo

                          • Post #13
                          • Edited

                          surfer63 actually it still works for me in 241222 if I set the GMaps app language to German, as described above. I only have the problem if I set GMaps to system language (which is German as well but then it only understands English).
                          Still a bug as it should honour the system language setting.

                            It doesn' t work for me.
                            I have my Google Maps app language on Dutch. I have my Android system language on Dutch. It only understands English. Google Maps texts and menus are entirely in Dutch.

                            If I set my app language to "system" it is still Dutch (System (Nederlands)) and then it doesn't work at all. I see the 5 Google bars "wave" to indicate that it receives audio, but it doesn't resolve anything. It times out and then gives suggestions in English, even though system language is recognized as Dutch.
                            The screen text and menu themselves are indeed in Dutch, but in this case voice search doesn' t get anything at all.

                            25 days later

                            And it functions again. Don' t ask me how and why.
                            App language was on Dutch and still is on Dutch. I am still on 3.5 and did not upgrade to 3.6 after the many issues, also on VAG (VW, Skoda, Seat) based cars.
                            Last Tuesday I tried voice search again and it worked again.
                            The only thing I did was switch from dual PIP to miminalistic mode (3 PIP windows). I only realize that now that I am typing it.
                            Tomorrow I will switch back to dual PIP and try again.

                            Unfortunately, the Polish language is not available in Google Assistant or Gemini for Google Maps voice search. Theoretically, it can be set, but English is used during searches. I can change it to German, Dutch or another language, for example, and it works correctly in the selected language. If I change Google Maps to Polish, it works in English, regardless of whether it is in PIP or the application is turned on full screen. When I had the Mekede M600s, voice search in maps worked in Polish. What can I do about it?

                            surfer63 Not sure if I should tag the support team again but this bug should be fixed properly. It also occurs on my DUDU5 (secondary unit) and that offers no workaround through app languages as it's Android 10...

                              And Yesterday and today it didn' t function anymore, again. It is very annoying. Rebooting doesn't help either.
                              There is something inconsistent and I do not know what it is (yet).

                              Edit: Was 2 days on the road. Didn' t see above messages.

                              For Dudu7 with DuduOS 3.5 I did a full data reset and now it works fine. Without having to select the language in maps, voice search works correctly in Polish.

                                • Ggismo

                                  • Post #20
                                  • Edited

                                  Slavus Did you backup/restore and if so what did you use? Or configured as new?
                                  It's a bit hard to understand why this reset makes a difference: My Dudu7 hat earlier fimwares, ok. But my Dudu5 started with v3.5 so was configured as new and still shows this error.
                                  I'd prefer guidance from DUDUAUTO as to what part of a configuration should be reset. It's easier to work from a reset of Google Services than the entire device...