SpeechRecognizer stopListening method does nothing on Android 10 devices [158198432]

Fixed

Bug

[AOSP] assigned

adexe s nau

Status Update

No update yet.

Description

er...@gmail.com

created issue #1

Jun 4, 2020 08:48PM

Hey there!

I have an application that makes use of the Android SpeechRecognizer.
I noticed differing behavior for the stopListening method between Android 9 and 10.
On Android 9 devices, calling stopListening stopped the recognition and resulted in an ERROR_SPEECH_TIMEOUT immediately after it. However, on Android 10 devices, stopListening seems to do nothing. It does not stop the recognition at all. Partial results are continuing. There is no onSpeechEnd or immediate ERROR_SPEECH_TIMEOUT like on Android 9.
So the only way to stop recognition is the normal timeout or speech end detection.

Is there something I am missing?

buildToolsVersion = "28.0.3"
minSdkVersion = 26
compileSdkVersion = 28
targetSdkVersion = 28

Comments

ra...@google.com <ra...@google.com> Jun 5, 2020 02:44AM

Assigned to ra...@google.com.

ra...@google.com <ra...@google.com> #2Jun 5, 2020 05:47AM

https://issuetracker.google.com/issues/389280099

er...@gmail.com <er...@gmail.com> #3Jun 5, 2020 09:48PM

https://issuetracker.google.com/issues/383751192

https://stackoverflow.com/questions/79333995/3rd-party-cookies-in-android-14-new-chrome-using-angular-firebase-auth-hosting-a

er...@gmail.com <er...@gmail.com> #4Jun 5, 2020 09:58PM

Thank you for filing this issue!

While it doesn't seem directly related to third-party cookie dependencies or Privacy Sandbox, we may be missing something. If you are confident that this issue is related to third-party cookies, please submit a new report with more details about how the issue might be impacted by third-party cookies.

Marking this as duplicate. Please see the previous issue here issuetracker.google.com/u/1/issues/383751192 for more details.

This thread will no longer be monitored for responses.

pe...@gmail.com <pe...@gmail.com> #5Jun 8, 2020 10:53PM

This is related to 3rd party cookies because in my Chrome browser on my cell phone with Android 14 I disabled 3rd party cookies and it still didn't work. In Firefox on the desktop I disabled 3rd party cookies and it worked.

er...@gmail.com <er...@gmail.com> #6Jun 16, 2020 06:17PM

Note-00: I think the solution necessarily goes through the last answer of this post:

https://www.googlecloudcommunity.com/gc/Serverless/Session-cookie-won-t-be-set-due-to-domain-name-mis-match-despite/m-p/610335/highlight/true

er...@gmail.com <er...@gmail.com> #7Jun 17, 2020 11:41PM

I'm switching from signinWithDirect to signinWithPopup (because a test project about firebase auth that I have, worked with Popup and presented my error that the main project using Direct).

The issue atual (When I switching) is(photo ATTACHED): main-NYXVCRV2.js:8 Cross-Origin-Opener-Policy policy would block the window.closed call.

so...@csdcorp.com <so...@csdcorp.com> #8Jun 27, 2020 09:06PM

I'm seeing the same behaviour on a Pixel 3a running Android 10 Kernel version: 4.9.210

I see this exception in the log:

2020-06-27 17:04:26.816 31580-2030/? W/Binder: Caught a RuntimeException from the binder stub implementation.
    java.lang.SecurityException: uid 10124 does not have android.permission.UPDATE_APP_OPS_STATS.
        at android.os.Parcel.createException(Parcel.java:2071)
        at android.os.Parcel.readException(Parcel.java:2039)
        at android.os.Parcel.readException(Parcel.java:1987)
        at com.android.internal.app.IAppOpsService$Stub$Proxy.checkOperationRaw(IAppOpsService.java:1617)
        at android.app.AppOpsManager.unsafeCheckOpRawNoThrow(AppOpsManager.java:5012)
        at android.content.PermissionChecker.checkPermissionCommon(PermissionChecker.java:403)
        at android.content.PermissionChecker.checkPermissionForPreflight(PermissionChecker.java:162)
        at android.content.PermissionChecker.checkCallingOrSelfPermissionForPreflight(PermissionChecker.java:373)
        at android.speech.RecognitionService.checkPermissions(RecognitionService.java:185)
        at android.speech.RecognitionService.access$700(RecognitionService.java:39)
        at android.speech.RecognitionService$RecognitionServiceBinder.stopListening(RecognitionService.java:366)
        at android.speech.IRecognitionService$Stub.onTransact(IRecognitionService.java:141)
        at android.os.Binder.execTransactInternal(Binder.java:1021)
        at android.os.Binder.execTransact(Binder.java:994)

ra...@google.com <ra...@google.com> #9Jun 30, 2020 07:27AM

Thanks for update. Please provide singned apk and bug report as requested in

comment #2

, to check this issue further.

so...@csdcorp.com <so...@csdcorp.com> #10Jun 30, 2020 05:59PM

I thought that had been provided in #3?

vi...@google.com <vi...@google.com> #11Jul 1, 2020 10:35AM

Reassigned to vi...@google.com.

We are getting error while installing the apk, could you please build your project again and send new apk.

er...@gmail.com <er...@gmail.com> #12Jul 3, 2020 12:04PM

I am sorry, I updated the APK to a signed and hopefully working version I tested it on a few devices.
You can find it in the drive I shared earlier:

https://drive.google.com/drive/folders/1cm1Fiw38hq0LR3GbGGt2bydVyII-p5qI?usp=sharing

vi...@google.com <vi...@google.com> #13Jul 7, 2020 01:54PM

We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

er...@gmail.com <er...@gmail.com> #14Jul 12, 2020 10:57AM

I see that this issue was marked blocked by some other issue I don't have the permissions to view. Could you shed some light on that?

li...@gmail.com <li...@gmail.com> #15Jul 21, 2020 10:27AM

Hi guys, any progress about this issue? I'm also seeing this problem on Pixel 4 Android 10. Security patch level July 5, 2020. Google Play system update July 1, 2020. Kernel version 4.14.170. Build number QQ3A.200705.002

jr...@gmail.com <jr...@gmail.com> #16Oct 1, 2020 11:25AM

Hello there! Any update on this issue? I'm having the same issue too. I'm using a One Plus 6 with Android 10

ad...@epopsoft.kr <ad...@epopsoft.kr> #17Nov 17, 2020 05:19AM

Any update?

vi...@google.com <vi...@google.com> #18Dec 28, 2020 01:57PM

Re-

Comment #15

, please confirm the AGSA version number.

vi...@google.com <vi...@google.com> #19Jan 4, 2021 05:27AM

Please share the details requested in

comment #18

ts...@gmail.com <ts...@gmail.com> #20Jan 9, 2021 05:17AM

Any solution or update on this guys ?

jy...@coyote-group.com <jy...@coyote-group.com> #21Mar 25, 2021 04:49PM

Hello
I can confirm on Samsung S9 Android 10 that stopListening() is not working. It does not stop the current recognition. It has no effect.
Please Google we need a fix. We can't manage a timeout, so the user can speak indefinitly and it can happen if he's listening to music.

ma...@gmail.com <ma...@gmail.com> #22Nov 29, 2021 08:10PM

having the same issue, neither stopListening() nor cancel() has any effect on AndroidTV 10.

vi...@google.com <vi...@google.com> #23Nov 30, 2021 12:43PM

Marked as fixed.

This issue has been fixed and the fix will be available in a future Android release.

17...@gmail.com <17...@gmail.com> #24Dec 11, 2022 12:19PM

Can someone share code where it is working and stopListening() is actually stopping recognition, because even on Android 12 it is doing NOTHING

de...@gmail.com <de...@gmail.com> #25Mar 15, 2023 11:16AM

Comment has been deleted.

Message last modified on Mar 15, 2023 11:18AM

me...@gmail.com <me...@gmail.com> #26Jan 24, 2024 04:23AM

May I know is it permanent bug in Android 10 or it can be fixed in backend?