When I long press the media button on my Passport, BlackBerry Assistant launches but goes straight to the thinking logo before I can say anything. Anyone else experienced this?
PassportSQW100-1/10.3.2.2876
Printable View
When I long press the media button on my Passport, BlackBerry Assistant launches but goes straight to the thinking logo before I can say anything. Anyone else experienced this?
PassportSQW100-1/10.3.2.2876
Anyone?
PassportSQW100-1/10.3.2.2876
Is your wifi or data turned off? If yes, try turning it on.
Posted via CB10
Ok, thanks for that. For anyone else thinking of posting here, please assume that all settings are correct and data is on as well as WiFi. Assistant voice control hasnt worked for several days now. Just goes straight to thinking and then says 'voice command wasn't understood' or words to that effect. It doesn't listen. It does function fine when I type though. All other aspects of the phone and it's features function as they should.
PassportSQW100-1/10.3.2.2876
Bumpity bump bump.
PassportSQW100-1/10.3.2.2876
FWIW mine is working well. (Passport running 10.3.2.2876)
Ok, got it sorted. Reboot didn't sort the problem but another two reboots did the job. Weird problem lol.
PassportSQW100-1/10.3.2.2876
Sometimes it gets stuck like that. Another way to fix it sometimes is to change the assistant language to something else, and then switch it back. It's like a kick in the arse.
I'll bear that in mind, thanks. That would be a lot easier than rebooting.
PassportSQW100-1/10.3.2.2876
The assistant isn't working for me right now either.
It listens,gets a correct transcription, then says "the voice command was not understood" for anything not handled locally on device.
So no calendar, alarm, sports, messaging, settings, etc. Anything the cloud nlu is used for.
Knowledge, Websearch with a variety of engines, launching apps, digit dialing (but not address book calling???) are all working fine. Weird split of what is handled local vs cloud.
Hoping the cloud nlu comes back online soon.
Posted via CB10
Try the language switch trick I described above. Reboots work sometimes too.