Can't use speaking mode on my android device

I tried out the speaking mode for the french fluency fast track course on my ipad and it works like a charm. But i can’t get it working on my android device. Every time i try clozemaster shows me an error message: access to speech recognition required to play speaking mode. Sadly i’m not able to find a way to grant the programme this permission. It didn’t ask for it. When i look in the permission settings for the app, there is no permission denied.
Does this feature work unser andoroid, or is it only me who is experiencing this problem?

Welcome @chyro! You are not alone. My android Samsung tablet “speaking” doesn’t work either. Have never discovered why.

However, everything else great.

I have the same issue, Android 11. I’ve pulled android logs and it says this.
05-17 13:25:00.561 1355 5388 W ActivityManager: Unable to start service Intent { act=android.speech.RecognitionService cmp=com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService } U=0: not found

05-17 13:25:00.482   938   938 I SurfaceFlinger: Touch=1, Idle=0, DisplayPower=0
05-17 13:25:00.488  1355  1401 D TspStateManager: updateCustomValue customSetting=
05-17 13:25:00.489  1355  1355 D PowerManagerService: [api] userActivity : event: 0 flags: 0 (uid: 1000 pid: 1355) eventTime = 43282260
05-17 13:25:00.489  1355  1401 D TspStateManager: updateCustomValue customSetting=
05-17 13:25:00.492  1355  1355 E Native_CFMS: nativePerfMgrSendFps    Fail    fps : 120    return : -1
05-17 13:25:00.492  1355  1580 I CAE     : handleMessage(CaPowerManager.java:202) - AP_WAKEUP_Already_Delivered
05-17 13:25:00.492  1355  1580 I CAE     : handleMessage(CaPowerManager.java:212) - SCREEN_ON_Already_Delivered
05-17 13:25:00.493  1851  1851 D DisplayLifecycle: updateDisplay id = 0
05-17 13:25:00.494  1355  1355 D MotionRecognitionService: [DisplayListner] getRefreshRate 120.00001
05-17 13:25:00.495  1355  1583 D LiftUpHandler: already ended..
05-17 13:25:00.495  1355  1355 D GameManagerService: onDisplayChanged. displyId: 0, state: 2
05-17 13:25:00.495  1355  1583 D MotionRecognitionService: [REFRESHRATE]  : 120
05-17 13:25:00.495  1355  1355 D GameManagerService: dpi: 450, longPixel: 2190, shortPixel: 1080
05-17 13:25:00.495  1355  1583 D SensorService: setSContextDataLocked ints length 3 , byte length 8
05-17 13:25:00.495  1355  1583 D SensorService: setSContextDataLocked 100048c1
05-17 13:25:00.495  1355  1355 D AODManagerService: requestReCalToTSP IsSingleTouchMode = false / previousDisplayState = ON
05-17 13:25:00.495  1355  1597 D GameManagerService: onLooperPrepared(), msg: MSG_LCD_ON
05-17 13:25:00.495   938   938 D Scheduler: onPrimaryDisplayConfigChanged to 4
05-17 13:25:00.495   860   860 D Sensors : c1 48 00 10 78 00 00 00
05-17 13:25:00.495   860   860 E Sensors : inject_scontext_data: New ssp_data_injection_fd(41)
05-17 13:25:00.498   938   938 D SurfaceFlinger: SurfaceFlinger - GPIS:: sendDrawingTid Pid : 938    Tid : 938
05-17 13:25:00.498  1355  5137 E Native_CFMS: nativePerfMgrAddTask    Fail    tid : 938    return : -1
05-17 13:25:00.499   860   860 D Sensors : SContext Data Injection return 8
05-17 13:25:00.505 18075 18075 I BWU@ApWakeupService: Ph_onDisplayChanged() - display id : 0, state : 2, prevDisplayState state : 2 [main]
05-17 13:25:00.506  1355  1355 D PowerManagerService: [api] userActivity : event: 0 flags: 0 (uid: 1000 pid: 1355) eventTime = 43282277
05-17 13:25:00.508  1355  5388 I Telecom:SamsungTelecomServiceImpl: getCallState - callingPid : 18075 / processName : sts
05-17 13:25:00.508 18075 18075 I BWU@ApWakeupService: Ph_isRecognitionAllowed? false :: callState : 0, serviceDisabled : false, displayState : 2, isInteractive : true, isMultiRecording : false [main]
05-17 13:25:00.522  1355  1355 D PowerManagerService: [api] userActivity : event: 0 flags: 0 (uid: 1000 pid: 1355) eventTime = 43282294
05-17 13:25:00.530  1355  1355 D PowerManagerService: [api] userActivity : event: 0 flags: 0 (uid: 1000 pid: 1355) eventTime = 43282302
05-17 13:25:00.539  1355  1592 D InputReader: Btn_touch(11): value=0 when=43282.310715
05-17 13:25:00.539  1355  1592 I InputReader: Touch event's action is 0x1 (id=4, t=0) [pCnt=1, s=] when=43282.310715
05-17 13:25:00.539  1355  1355 D PowerManagerService: [api] userActivity : event: 0 flags: 0 (uid: 1000 pid: 1355) eventTime = 43282310
05-17 13:25:00.539  1355  1355 D InputDispatcher: Inject motion (0): action=0x1, time=43282310715000, f=0x0, d=0
05-17 13:25:00.539  1355  1591 I InputDispatcher: Delivering touch to (4625): action: 0x1, f=0x0, d=0, 'b541594', t=1
05-17 13:25:00.540  4625  4625 I ViewRootImpl@8ceb3c2[MainActivity]: ViewPostIme pointer 1
05-17 13:25:00.543 19723  8072 I .gms.persisten: Explicit concurrent copying GC freed 400478(14MB) AllocSpace objects, 3(124KB) LOS objects, 49% free, 19MB/38MB, paused 122us total 72.403ms
05-17 13:25:00.545 19723 19740 I BluetoothSocket: close() this: android.bluetooth.BluetoothSocket@1d9b9c4, channel: 6, mSocketIS: android.net.LocalSocketImpl$SocketInputStream@1e600ad, mSocketOS: android.net.LocalSocketImpl$SocketOutputStream@5f12fe2mSocket: null, mSocketState: CLOSED
05-17 13:25:00.561  1355  5388 W ActivityManager: Unable to start service Intent { act=android.speech.RecognitionService cmp=com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService } U=0: not found
05-17 13:25:00.561  4625  4625 E SpeechRecognizer: bind to recognition service failed
05-17 13:25:00.904   648   648 I io_stats: !@   8,0 r 6665205 168450180 w 2999960 35583096 d 1118872 72408968 f 0 0 iot 4234552 0 th 0 0 0 pt 0 inp 0 0 43282.675
05-17 13:25:01.015  1355  1421 I AppOps  : updateUidProcState uid: 10248 procState: 5 capability:7
05-17 13:25:01.017  1355  1421 D PowerManagerService: [api] setDeviceIdleTempWhitelist: appids: [0]11063  (uid: 1000 pid: 1355)
05-17 13:25:01.037 19677 19703 E TUI_SERVICE_JNI: socket_wrapper_create_client[line: 122]connection to tuill_iwd_server failed, errno: 111

My system Info

[ro.product.board]: [exynos2100]
[ro.product.brand]: [samsung]
[ro.product.build.date]: [Mon Oct 18 19:32:06 KST 2021]
[ro.product.build.date.utc]: [1634553126]
[ro.product.build.fingerprint]: [samsung/p3sxxx/p3s:11/RP1A.200720.012/G998BXXS3AUJ7:user/release-keys]
[ro.product.build.id]: [RP1A.200720.012]
[ro.product.build.tags]: [release-keys]
[ro.product.build.type]: [user]
[ro.product.build.version.incremental]: [G998BXXS3AUJ7]
[ro.product.build.version.release]: [11]
[ro.product.build.version.release_or_codename]: [11]
[ro.product.build.version.sdk]: [30]
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [arm64-v8a]
[ro.product.device]: [p3s]
[ro.product.first_api_level]: [30]
[ro.product.locale]: [en-GB]
[ro.product.manufacturer]: [samsung]
[ro.product.model]: [SM-G998B]
[ro.product.name]: [p3sxxx]
[ro.product.odm.brand]: [samsung]
[ro.product.odm.device]: [p3s]
[ro.product.odm.manufacturer]: [samsung]
[ro.product.odm.model]: [SM-G998B]
[ro.product.odm.name]: [p3sxxx]
[ro.product.product.brand]: [samsung]
[ro.product.product.device]: [p3s]
[ro.product.product.manufacturer]: [samsung]
[ro.product.product.model]: [SM-G998B]
[ro.product.product.name]: [p3sxxx]
[ro.product.system.brand]: [samsung]
[ro.product.system_ext.brand]: [samsung]
[ro.product.system_ext.device]: [p3s]
[ro.product.system_ext.manufacturer]: [samsung]
[ro.product.system_ext.model]: [SM-G998B]
[ro.product.system_ext.name]: [p3sxxx]
[ro.product.vendor.brand]: [samsung]
[ro.product.vendor.device]: [p3s]
[ro.product.vendor.manufacturer]: [samsung]
[ro.product.vendor.model]: [SM-G998B]
[ro.product.vendor.name]: [p3sxxx]
[ro.product.vndk.version]: [30]
[ro.product_ship]: [true]
[ro.property_service.version]: [2]
type or paste code here

This issue could very likely correlate with using Android 11, according to this source.

the problem seems to be related to this new Android 11 “feature”

That could be the cause of @siniy’s problem.

Android 13 made further breaking changes. On Samsung devices, Android 13 was released starting October 2022, which fits with when @chyro and @Floria7 reported their problems.

1 Like

Hi. Just out of interest, I tried again this evening, with variations of Hard Easy Text etc but it still doesn’t work on my Samsung tab.