Voice commands aren't available at the moment with Google app 14.45.24 for Android 10 [310762252]

Assigned

Bug

Status Update

No update yet.

Description

pe...@bluechipcomputers.com.sg

created issue #1

Nov 14, 2023 03:31AM

In AA, activating Google Assistant will show a toast box "Voice commands aren't available at the moment".

I've isolated it to Google app (GA) 14.45.24 being the issue for Android 10 as it works fine on Android 13. AA versions didn't matter.

Here are the details:

Samsung S9+ Android 10: AA 10.9.134544-release.daily GA 14.44.29.28 - works fine GA 14.45.24.28 - voice commands aren't available at the moment GA 14.45.24.29 - voice commands aren't available at the moment GA 14.44.31.28 - works fine

Huawei P20 Pro Android 10 (spare phone and only just turned on to update selectively as below: AA 10.6.634004-release and GA 14.40.33.28 - works fine AA 10.6.634004-release and GA 14.45.24.28 - voice commands aren't available at the moment AA 10.9.134544-release.daily and GA 14.45.24.28 - voice commands aren't available at the moment

Samsung S10 Lite Android 13: AA 10.7.634234-release and GA 14.44.29.28 - works fine AA 10.7.634234-release and GA 14.45.24.28 - works fine AA 10.9.134544-release.daily and GA 14.45.24.28 - works fine

Comments

ki...@google.com <ki...@google.com> #2Nov 14, 2023 01:04PM

Assigned to pe...@bluechipcomputers.com.sg.

for example, many different devices return the same longitude and latitude.such as : longitude is 121.474000 and latitude is 31.230001.
i donnot understand why is the data the same?

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #3Nov 14, 2023 02:09PM

the fractional part of the location data is exactly the same.

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #4Nov 14, 2023 02:36PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

What steps are needed to reproduce this issue? Frequency of occurrence?

Which Android build are you using? (e.g. AP4A.241205.013.A1)

Which device did you use to reproduce this issue?

Can you confirm if this issue is reproducible on a Pixel/Nexus device?

Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #5Nov 14, 2023 03:33PM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

deleted

0 B

ki...@google.com <ki...@google.com> #6Nov 14, 2023 04:53PM

I only aply permission android.permission.ACCESS_COARSE_LOCATION.I use android.location.Location in the program.
for example,we hava 100 users.
20 users returned the same location information, longitude is 121.474000 and latitude is 31.230001。
30 users returned the same location information, longitude is 122.474000 and latitude is 32.230001。
15 users returned the same location information, longitude is 120.474000 and latitude is 30.230001。

as for Android build,all versions have it.
I dont reprodouce this issue.

what may be the cause of this issue?please

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #7Nov 14, 2023 05:09PM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

tr...@gmail.com <tr...@gmail.com> #8Nov 14, 2023 11:21PM

Thanks for reporting this issue.

COARSE_LOCATION typically takes location information from the nearby cell tower. If many users are near the same cell tower, each of those users will be given the same position. Using a FINE position will give much more detailed information.

Also, in certain areas, for privacy reasons, a less-exact location will be given, and that less-exact location might be identical for many users. Again, a fine-location configuration will return more precise location data.

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #9Nov 15, 2023 03:59AM

We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.

fi...@gmail.com <fi...@gmail.com> #10Nov 15, 2023 08:16PM

Thank you very much! it is very useful to me . It solved my confusion.

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #11Nov 15, 2023 11:59PM

The message came back this morning. It was still fine when I last used yesterday night about 14 hrs ago last night. Although AA updated from 10.9.134544-release.daily to 10.9.134604-release.daily this morning, I think it's on point 3 of my comment#9 https://issuetracker.google.com/issues/310762252#comment9

Attached a screenshot showing the message.

Link to new bug report generated after reproducing on Kenwood DDX917WS:

screendump - 2023-11-16-07_26_44.png

55 KB

View

Download

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #12Nov 16, 2023 04:34AM

Forgot to mention comment #11 is for S9+.

I just checked Huawei P20 Pro and the same thing happened despite haven't yet install any new updates since it worked.

co...@gmail.com <co...@gmail.com> #13Nov 16, 2023 10:26PM

Same issue with GA = 14.45.24.28 in multiple cars (Subaru XV, Mitsu Pajero Sport). Rolling back fixes the voice command issue.

Oppo Reno Z - CPH1979
Android 11

AA - cache clear does nothing to fix the issue when the GA 14.45.24.28

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #14Nov 18, 2023 03:25PM

Any update on this issue?

Today GA 14.46.33.28 is pushed to my Play Store which I allowed it to update not expecting it will work and it didn't because I've already tried all newer beta and production versions to date since it broke.

Further to this, GA 14.46.33.28 is listed as beta in APKMirror but I'm not registered as a Google app beta user because I've seen too many cases of AA bugs that were due to Google app beta. Unless APKMirror is wrong, why is beta pushed to me then? I noted non-registered Google app beta users were also pushed beta version with similar bug not too long ago.

jo...@gmail.com <jo...@gmail.com> #15Nov 19, 2023 10:43AM

Google Assistant has been flaky. Past few days it would not work within AA. It is just beeps and then nothing happens. However during the afternoons drive navigation instruction worked. The voice command "Ok Google, take me home/ ABC destination" etc
Device: Pixel 7
Build Version: UP1A.231105.003
AA: 10.7.634234
Google: 14.46.33.29.arm64

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #16Nov 19, 2023 01:14PM

Comment #15 isn't the same issue. This issue appears to only affect older Android version and not Android 13.

fl...@gmail.com <fl...@gmail.com> #17Nov 20, 2023 12:14AM

Comment has been deleted.

Message last modified on Nov 20, 2023 12:15AM

fl...@gmail.com <fl...@gmail.com> #18Nov 20, 2023 12:16AM

Started getting same issue since last update, Samsung A50, Android 11, AA version 10.7.634234-release

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #19Nov 20, 2023 12:47AM

AA versions didn't matter in my tests. It's soley on any Google app version newer than 14.44.XX.XX.

ga...@gmail.com <ga...@gmail.com> #20Nov 20, 2023 07:45PM

I have a motorola one 5G and have the same issue of "Voice Commands aren't available right now". I have Android version 11 Build # RZK31.Q3-45-16-8-19-1

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #21Nov 22, 2023 08:49PM

Still not fixed with GA 14.47.33 and 14.47.35.

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #22Nov 23, 2023 08:35PM

So 14.47.35 didn't work yesterday but today it's working without doing anything. On another phone without this update, it didn't work until I forced stop google app and clear its cache which is what I always do before but didn't work until now. In the official AA community thread a few reported it now started working on versions that also didn't work before while some with the same version still having the same issue with same versions. So clearly it's something server-end but the usual workaround is needed to expedite it or get it working.

Hopefully this time it sticks because I also had it working before but the message subsequently came back.

co...@gmail.com <co...@gmail.com> #23Nov 23, 2023 11:10PM

Good to know, and thanks for the update. I'll update to that latest version of GA and test on the way home from work this arvo.

sh...@gmail.com <sh...@gmail.com> #24Nov 25, 2023 06:06AM

Currently using GA 14.46.33.28 on Huawei P20 Pro, and having same issues with voice command not working in vehicle.

pe...@bluechipcomputers.com.sg <pe...@bluechipcomputers.com.sg> #25Nov 25, 2023 07:12AM

Is it the same bug?

My P20 Pro is using same version but it needed a force stop and clear cache to work.

If it's only not responding to hey Google, make sure it's enabled in setting. Toggle off and on if already enabled as sometimes this is needed.

be...@gmail.com <be...@gmail.com> #26Jun 4, 2024 08:07PM

I have the same issue. My phone is Motorola G9 power with android 11. All apps are up to date. I noticed that the problem happens only when there is a WhatsApp message notification pending. The message can't be read using Google Assistant (due to the issue) BUT can be read by opening the WhatsApp app (but you can't reply). When you clear the whatsapp notification then Voice Commands work regulary until a new whatsapp message arrives. Hope this can help. If you need some additional info, please let me know. This bug results in a very poor user experience.

be...@gmail.com <be...@gmail.com> #27Jun 4, 2024 08:13PM

I forgot to report the exception I've found using logcat when the issue happens:
06-04 17:08:18.070 5752 30366 E CarAssistantClient: Error starting assistant session
06-04 17:08:18.070 5752 30366 E CarAssistantClient: aakf: RESOURCE_EXHAUSTED: Inbound Parcelables too large according to policy (see InboundParcelablePolicy)
06-04 17:08:18.070 5752 30366 E CarAssistantClient: at aakd.h(SourceFile:3)
06-04 17:08:18.070 5752 30366 E CarAssistantClient: at aayq.e(SourceFile:15)
06-04 17:08:18.070 5752 30366 E CarAssistantClient: at aaji.e(SourceFile:84)
06-04 17:08:18.070 5752 30366 E CarAssistantClient: at aaoa.a(SourceFile:32)
06-04 17:08:18.070 5752 30366 E CarAssistantClient: at aaor.run(SourceFile:7)
06-04 17:08:18.070 5752 30366 E CarAssistantClient: at aauh.run(SourceFile:17)
06-04 17:08:18.070 5752 30366 E CarAssistantClient: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-04 17:08:18.070 5752 30366 E CarAssistantClient: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-04 17:08:18.070 5752 30366 E CarAssistantClient: at java.lang.Thread.run(Thread.java:923)
06-04 17:08:18.071 5752 5752 I CarApp.H.Har: getCarHardwareResult dispatchResult=23
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: handleInternalError: START_VOICE_SESSION_REMOTE_EXCEPTION
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: aakf: RESOURCE_EXHAUSTED: Inbound Parcelables too large according to policy (see InboundParcelablePolicy)
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: at aakd.h(SourceFile:3)
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: at aayq.e(SourceFile:15)
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: at aaji.e(SourceFile:84)
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: at aaoa.a(SourceFile:32)
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: at aaor.run(SourceFile:7)
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: at aauh.run(SourceFile:17)
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-04 17:08:18.078 5752 5752 E GH.Assistant.Controller: at java.lang.Thread.run(Thread.java:923)

be...@gmail.com <be...@gmail.com> #28Jun 13, 2024 12:51PM

Just tested with Google app version 15.22.33.28 and the bug is still there...

be...@gmail.com <be...@gmail.com> #29Jun 25, 2024 07:38AM

I subscribed the Beta program for Google app and tested with last revision 15.25.31.28, but no luck... What else can I do?

be...@gmail.com <be...@gmail.com> #30Jul 2, 2024 09:20AM

Release 15.26.34.28 still broken... Please fix it...

be...@gmail.com <be...@gmail.com> #31Jul 30, 2024 01:19PM

I'm installing every single new version of google app and the problem is always there! Now i'm on 15.30.27.28 ... Please solve it!!