Database Users

OK Google with screen turned off

I think about buying the Axon 7, but got one question left and haven't found an answer anywhere:
Is the OK Google Command working without the screen being turned on or the device being charged?
Basically: is it behaving like a Nexus device would? I know many devices only react to "OK Google" if the device is turned on and/or charging.

This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.

Delete

xxBrun0xx said:
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Click to expand...
Click to collapse
This is not true. When charging, I can say ok google and the devices listens to me. Also, if the screen is on and I'm not charging, I can still say ok google and it will listen.

notese said:
This is not true. When charging, I can say ok google and the devices listens to me. Also, if the screen is on and I'm not charging, I can still say ok google and it will listen.
Click to expand...
Click to collapse
Could be wrong but it sounded like he was asking if off screen voice commands worked while the phone was not charging?

xxBrun0xx said:
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Click to expand...
Click to collapse
And the V20 apparently
xxBrun0xx said:
Could be wrong but it sounded like he was asking if off screen voice commands worked while the phone was not charging?
Click to expand...
Click to collapse
You are right! I got really used to using "OK Google" while the phone is in stand-by, i.e., screen turned off and not charging.
Why are vendors not able to properly implement this? The Snapdragon is technically able to do this.

smuurfi said:
And the V20 apparently
You are right! I got really used to using "OK Google" while the phone is in stand-by, i.e., screen turned off and not charging.
Why are vendors not able to properly implement this? The Snapdragon is technically able to do this.
Click to expand...
Click to collapse
Yeah it really breasts me. I miss that from my Nexus 6p, but that's about the only thing I miss other than camera and nougat. The snapdragon 820 is amazing and battery life on the Axon is better than the 6p.

Sorry to bring up an old thread, but I've missed being able to say Okay Google from when the screen is off like I was able to on the 6P. I've been trying to figure out why and I think maybe one of two things (maybe both) is happening. One is that the power manager automatically screen cleans the Google app. The app isn't in the power management menu so that you can toggle off screen cleaning. The other is that I think the phone turns off the mic when the screen turns off and locks. However, if I just used Google Assistant and turn off the screen, I am able to use Okay Google with the screen off if I say it a split second after I turn off the screen with the power button. Sometimes it works, sometimes I have to enter my PIN, but it always has to be right after using Google Assistant and locking the screen. Throwing this out there with the hopes that someone might be able to figure out how to get around this.

Yep same
Mike

"Ok Google" is not reliable

As title suggests, voice recognition has been really unreliable through my daily usage.
If the phone is locked - "Ok Google" never works, yes i have set Smart unlock to unlock through voice.
if the phone is unlocked - "Ok Google" works, but if connected to my car's Bluetooth, it doesn't.
any of you guys can share their experience?

gilad215 said:
As title suggests, voice recognition has been really unreliable through my daily usage.
If the phone is locked - "Ok Google" never works, yes i have set Smart unlock to unlock through voice.
if the phone is unlocked - "Ok Google" works, but if connected to my car's Bluetooth, it doesn't.
any of you guys can share their experience?
Click to expand...
Click to collapse
I have the same issue...

Same issue here. I think it's because of Samsung's aggressive management that won't allow Google Now to run in the background when the screen is off.
Sent from my SM-G950F using Tapatalk

Same issue here

I normally have to reboot to get "Okay Google" command to work.

for me ok google works for while, then stops working and a reboot is the only way to fix it. only annoying thing is i need to reboot every other day. this issue doesn't seems to be covered much?

electric0ant said:
for me ok google works for while, then stops working and a reboot is the only way to fix it. only annoying thing is i need to reboot every other day. this issue doesn't seems to be covered much?
Click to expand...
Click to collapse
fix for the OK Google issue on S8 & S8+ is to have the software re-flashed by Samsung or one of their retailers such as Best Buy. Other than rooting the device, there is nothing that can be done at the consumer level nor with tech support assistance that will resolve the issue.

Sikrik said:
fix for the OK Google issue on S8 & S8+ is to have the software re-flashed by Samsung or one of their retailers such as Best Buy. Other than rooting the device, there is nothing that can be done at the consumer level nor with tech support assistance that will resolve the issue.
Click to expand...
Click to collapse
what difference would re-flashing the software achieve?
flashing stock firmware can be achieved using odin.
and after rooting what can be done to fix this issue?

I don't know why re-flashing it worked but, it did. I also don't care. The phone works perfectly now. I keep seeing the same remedies over and over on forums such as this and NONE of them worked. Now that my phone is working, I shared what I did to get it fixed. I'm not a techie, I'm a truck driver so, if you said that I can flash stock firmware with Odin, you'd be wrong. Besides, why would I? Samsung screwed it up, they can fix it. It was free and it worked.

Trusted Voice MIA

Hi all, hopefully this has not been discussed. I searched but from the xda app search isn't so great...
Anyway wondering if anyone is having issues with trusted voice. I noticed okay Google was only working when phone was authenticated. And not from secured lock screen. Figured trusted voice was disabled, so I checked and it's just not there. (See image). I'm on 4.5.8 stock not rooted. I have tried clearing data on Google app.
Any suggestions is appreciated.
Thanks!

I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.

3DSammy said:
I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.
Click to expand...
Click to collapse
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.

tsuttie99 said:
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.
Click to expand...
Click to collapse
I'd read that others (UK) switched back to their native language after getting Google Assistant working and all was well. I've left it as US as primary with Canada as a second as it simply doesn't effect me. I like spelling colour as "color" which always made more sense to me.
My real reason for not switching back is that I've done a lot of home automation scripting with Google Assistant/Tasker's Voice Assist/Termux to automate my audio/video equipment and associated lighting. As far as I'm concerned Google Assistant may be in beta for built in functionality but is alpha for any third party integration. Every Google app update seems to break something while fixing other functionality (e.g. macros).
I like the automation I've created enough that I have little interest in rocking the boat at the moment. I had previously retested Trusted voice and the lock screen after updates and will again until it works. Right now I'm using a work around with an app called Caffeine (disables the lock screen timeout when charging) and Screen off (only turns the screen off but does not trigger the lock screen).
Also I may have tried toggling Trusted agents as I did so many tests and retests while working on Google Assistant functionality, I just can't remember.

I think there is something very broken with Smart Lock on this phone's stock OS.... I set up my cars BT as trusted device.... still i need to Authenticate with finger/pattern. Coming from a 6P where this all worked seamlessly it's frustrating.

My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.

ultramag69 said:
My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.
Click to expand...
Click to collapse
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?

3DSammy said:
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?
Click to expand...
Click to collapse
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash

tsuttie99 said:
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash
Click to expand...
Click to collapse
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.

3DSammy said:
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.
Click to expand...
Click to collapse
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.

Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?

tsuttie99 said:
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.
Click to expand...
Click to collapse
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.

Rebel7022 said:
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.
Click to expand...
Click to collapse
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?

tsuttie99 said:
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?
Click to expand...
Click to collapse
There's a xda article on OK Google that has a hack to do that. I tried it it works.. But that was 3 months ago

tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Yep, works from lock screen, not screen off...

tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Well fancy that. I just did your test, locked screen with power button, with screen off there's no reaction to "OK Google". I then double tap the screen and the lock screen displays. Now "OK Google" unlocks the phone and Google Assistant is fully functional.
Kind of feels like a sprinter that falls inches before the finish line. What the heck Google or OnePlus? I wonder if custom ROMs have the same issue?
Thanks for noticing this phenomena and posting about it.

Having Some Problems With my PH-1

At this point, I'm feeling a lot of love and hate for my PH-1, but I'm locked in. I'm on the Sprint lease plan and I'm passed the point of returning the thing. So here's the latest issues:
Voice-to-Text: Whether it's in Chrome, Brave, Messenger, Google Assistant or Keep, voice-to-text has the same problem. First of all, when the phone says it's listening, I have to wait a few seconds before saying anything. Otherwise, it'll miss the first few words of whatever I'm about to say. The other problem: If I'm trying to do voice-to-text, it'll take about 5 words and stop taking anymore even though the phone appears to still be actively listening. At that point, I can cancel and then tap the microphone button again. This will allow me to voice-to-text 5 more words. So voice to text is barely usable at this point.
I installed Google Voice, but it won't take over as the default voicemail app. I've dug around in Settings and such, but I can't seem to find where I can change this. Presumably, the install of Google Voice should have taken care of it, but that doesn't appear to have happened. It has all my old voicemail from my prior phone, but nothing since getting the PH-1.
Stays connected to my car and my LG headphones no problem, but has issues losing connection anytime my ASUS Zenwatch 2 runs out of battery. Three times so far, I've had to wipe the watch and reconnect to get the two devices talking to each other again.
Google Keyboard is interesting and all, but it seems to do a great job of registering the wrong keystrokes. Honestly, I'd gotten used to my Samsung keyboard anyways, so if there's an option to map the same second character layout, that'd be ideal. But I definitely need SOME keyboard app that presents large enough keys that my huge hands won't confuse the phone. G Board is as big as I can make it and it's just not enough.

BonkersTheClown said:
At this point, I'm feeling a lot of love and hate for my PH-1, but I'm locked in. I'm on the Sprint lease plan and I'm passed the point of returning the thing. So here's the latest issues:
Voice-to-Text: Whether it's in Chrome, Brave, Messenger, Google Assistant or Keep, voice-to-text has the same problem. First of all, when the phone says it's listening, I have to wait a few seconds before saying anything. Otherwise, it'll miss the first few words of whatever I'm about to say. The other problem: If I'm trying to do voice-to-text, it'll take about 5 words and stop taking anymore even though the phone appears to still be actively listening. At that point, I can cancel and then tap the microphone button again. This will allow me to voice-to-text 5 more words. So voice to text is barely usable at this point.
I installed Google Voice, but it won't take over as the default voicemail app. I've dug around in Settings and such, but I can't seem to find where I can change this. Presumably, the install of Google Voice should have taken care of it, but that doesn't appear to have happened. It has all my old voicemail from my prior phone, but nothing since getting the PH-1.
Stays connected to my car and my LG headphones no problem, but has issues losing connection anytime my ASUS Zenwatch 2 runs out of battery. Three times so far, I've had to wipe the watch and reconnect to get the two devices talking to each other again.
Google Keyboard is interesting and all, but it seems to do a great job of registering the wrong keystrokes. Honestly, I'd gotten used to my Samsung keyboard anyways, so if there's an option to map the same second character layout, that'd be ideal. But I definitely need SOME keyboard app that presents large enough keys that my huge hands won't confuse the phone. G Board is as big as I can make it and it's just not enough.
Click to expand...
Click to collapse
I have ZERO of these issues...
And Google voice hasn't put itself in the Google dialer since it was updated to material design like over a year ago...
Gboard is smart... And will get accustomed to your "large hands"
You do realize that this isn't the "***** at Essential" forum... Right?
Sent from my PH-1 using Tapatalk

rignfool said:
I have ZERO of these issues...
And Google voice hasn't put itself in the Google dialer since it was updated to material design like over a year ago...
Gboard is smart... And will get accustomed to your "large hands"
You do realize that this isn't the "***** at Essential" forum... Right?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I'm so happy for you! You have no problems in your life and nothing bad ever happens to you! Meanwhile, I see post after post after post on this forum where people are on their second or third PH-1 .... because their PH-1 had issues. Sprint's support for the Essential Phone is worse than nonexistent. Essential Phone's own support kinda sucks too. Honestly, this forum is the only resource for useful help I've been able to find period. Apparently, people posting who are frustrated with their new phone offends you. Meanwhile, I will continue to try to make my purchase of a PH-1 as livable as possible.

BonkersTheClown said:
I installed Google Voice, but it won't take over as the default voicemail app. I've dug around in Settings and such, but I can't seem to find where I can change this. Presumably, the install of Google Voice should have taken care of it, but that doesn't appear to have happened. It has all my old voicemail from my prior phone, but nothing since getting the PH-1.
Click to expand...
Click to collapse
Google broke the integration more than a year ago.
You will need to install an old version of the app manually.
The version you want is "com.google.android.apps.googlevoice_0.4.7.10.apk".
This is the last version that integrates with any dialer.
make sure you setup not to auto-update or the update will kill the integration.
BonkersTheClown said:
Stays connected to my car and my LG headphones no problem, but has issues losing connection anytime my ASUS Zenwatch 2 runs out of battery. Three times so far, I've had to wipe the watch and reconnect to get the two devices talking to each other again.
Click to expand...
Click to collapse
I didn't have that issue with my LG Urbane 2. Try uninstalling wear and reconnecting after resetting the watch.
BonkersTheClown said:
Google Keyboard is interesting and all, but it seems to do a great job of registering the wrong keystrokes. Honestly, I'd gotten used to my Samsung keyboard anyways, so if there's an option to map the same second character layout, that'd be ideal. But I definitely need SOME keyboard app that presents large enough keys that my huge hands won't confuse the phone. G Board is as big as I can make it and it's just not enough.
Click to expand...
Click to collapse
Maybe Swiftkey, but I used Gboard.

tech_head said:
Google broke the integration more than a year ago.
You will need to install an old version of the app manually.
The version you want is "com.google.android.apps.googlevoice_0.4.7.10.apk".
This is the last version that integrates with any dialer.
make sure you setup not to auto-update or the update will kill the integration.
Click to expand...
Click to collapse
Thanks, that explains a lot. Weird that they broke the integration. Can't think of a good reason for them to want to do that. Alternately, is there a different voicemail app that would work? Google Voice has it's good points, but if letting an update sneak through breaks it, I don't see the point in using Google Voice. Sometimes updates patch vulnerabilities after all.
Did Google replace Google Voice with something else perhaps?
I didn't have that issue with my LG Urbane 2. Try uninstalling wear and reconnecting after resetting the watch.
Click to expand...
Click to collapse
Did that so we'll wait and see. Hopefully it doesn't break again.
Maybe Swiftkey, but I used Gboard.
Click to expand...
Click to collapse
By rights, GBoard should be working great and isn't. Not really sure why. I've given myself time to get used to it but I fat finger crap way too much. I'll try Swiftkey and see if that works.
Thanks for the help!

Just an FYI, I have no issues with latest google voice, integrated with hangouts and used for my voicemail with Verizon after doing the standard *71(googlevoice#) *90(googlevoice#) an *92(googlevoice#). Maybe Sprint has a similar method of call forwarding you can use?
Also, maybe your phone has a hardware issue with a microphone. It wouldn't be the first case. Many of us really don't have an issue with voice to text, so that might be something to RMA about if you can test further.

manaox2 said:
Just an FYI, I have no issues with latest google voice, integrated with hangouts and used for my voicemail with Verizon after doing the standard *71(googlevoice#) *90(googlevoice#) an *92(googlevoice#). Maybe Sprint has a similar method of call forwarding you can use?
Also, maybe your phone has a hardware issue with a microphone. It wouldn't be the first case. Many of us really don't have an issue with voice to text, so that might be something to RMA about if you can test further.
Click to expand...
Click to collapse
The issue is not about being able to use it, dialer integration is broken.
Without integration you can't go to the dialer and listen to your VM.

tech_head said:
The issue is not about being able to use it, dialer integration is broken.
Without integration you can't go to the dialer and listen to your VM.
Click to expand...
Click to collapse
Try oreo beta... Or wait to oreo ota.. looks to be working or close to working in beta
Sent from my PH-1 using Tapatalk

Bixby questions from a Siri user

Hey everyone,
some years ago I had the Nexus One and started digging into Android development, custom ROMs, CyanogenMOD and so on. But since the iPhone 5S I've always been an Apple user.
One of the reasons I still prefer iPhone over Android phones is the convenient usage of Siri with headphones. Sounds awkward? Let me explain:
I use my bike every day, and while I try to find my way through the cars of the early morning traffic in Munich (Germany), I'm able to control the music I'm listening to with Siri.
A long press on my headphone button gives me accesss to Siri:
"Play some funk music".
Or: "Call Veronica."
Or: "Send a message to Peter: I'll be late for the rehearsal, sorry."
Or: "Set my alarm to 3 pm."
Stupid question: Is this possible with Bixby? Or Google Assistant?
Long story short: I don't want to have to fiddle around with my phone on the bike, especially when wearing gloves or anything. I'd love to activate the assistant from my headphones without unlocking the phone or taking it out of my pocket.
This is actually the thing that has kept me away from Android for quite a long time.
Thanks,
Ben

Assistant does all of that, plus much more. I don't use bixby.

Bixby currently is useless wouldn't even recognise my voice to train it as its Korean or US english only.
Google Assistant however is great BUT they've only started allowing assistant to work when the phone is sleeping and locked in the Oreo beta. I can now use voice commands (no button presses) to do anything like listening to music sending texts or calling. Nougat only lets you use the assistant with the screen on (and phone locked/unlocked).

Karlinski said:
Assistant does all of that, plus much more. I don't use bixby.
Click to expand...
Click to collapse
While the screen is off? Oblox said it won't work..

You can do that with "Ok Google" and it should work.
If you are still pending and not sure about switching, then check how this works on an Android in a phone store or get one from a friend.

heisven said:
While the screen is off? Oblox said it won't work..
Click to expand...
Click to collapse
I have not gotten the phone to wake by saying "ok google". but "Hi bixby" does wake the phone from a lockscreen.
what I do is say, "Hi Bixby, open Assistant" - and then Google Assistant launches and is listening.
saying, "Hi Bixby, open GOOGLE Assistant" just launches Google, so be sure leave out the word "Google".
Bixby: your *****'s *****.

As i stated above Samsung only made assistant wake the device in the Oreo beta which should be out in January if all goes to plan.
Ok Google works fine on Oreo to wake the phone so you dont have to mess with Bixby at all.
On Nougat i had to press the power button first then could say OK Google.

Oblox said:
As i stated above Samsung only made assistant wake the device in the Oreo beta which should be out in January if all goes to plan.
Ok Google works fine on Oreo to wake the phone so you dont have to mess with Bixby at all.
On Nougat i had to press the power button first then could say OK Google.
Click to expand...
Click to collapse
right, I think the OP may not have known that the S8 is still on Nougat (7.0) - Oreo (8.0) has been released only in beta form to certain users for testing.
so in other words, if you buy the device now, you will NOT be able to launch Assistant directly from the lockscreen. this feature should become available with the next software update.
but you could, in essence, use the device as you would like, but just have to say "Hi bixby" instead. also, as another user noted, test it for yourself. I have, and it works as advertised, just not as polished as google or Siri (takes training/repetition before you get the full AI experience).
this lockscreen wake capability has been around on android for quite some time. I had it on my 2014 Motorola Droid Turbo - and worked perfectly every time.

jco23 said:
right, I think the OP may not have known that the S8 is still on Nougat (7.0) - Oreo (8.0) has been released only in beta form to certain users for testing.
so in other words, if you buy the device now, you will NOT be able to launch Assistant directly from the lockscreen. this feature should become available with the next software update.
but you could, in essence, use the device as you would like, but just have to say "Hi bixby" instead. also, as another user noted, test it for yourself. I have, and it works as advertised, just not as polished as google or Siri (takes training/repetition before you get the full AI experience).
this lockscreen wake capability has been around on android for quite some time. I had it on my 2014 Motorola Droid Turbo - and worked perfectly every time.
Click to expand...
Click to collapse
Yep although as he's from germany id imagine he might have more issues than me trying to get US bixby to recognise his voice. It wouldn't even complete the training for me an I have a pretty standard UK english accent with no regional accent.

Thanks me later
https://www.youtube.com/watch?v=67PsQAqwoyI