Working fine on 55 on the samus I tested.  Did you try testing on another account on the same device? 

Tested on ToT, somehow I didn't even see options to enable "OK google" in the settings page.

Never mind my previous comment. It has to set branding to google chrome instead of chromium to make hotword available.

Tested on ToT, and not managed to get a repro.

I can reproduce this on my Pixel 2 on samus. Immediately kills itself whenever you say "Ok Google"

Version 55.0.2883.103 (64-bit)
Platform 8872.73.0 (Official Build) stable-channel samus
ARC Version 3583806
Firmware Google_Samus.6300.174.0

 Issue 694287  has been merged into this issue.

I want to point out that it doesn't respond at all on the Samsung +. No triggering on the NTP, Launcher or "Ok Google" when the screen is on and unlocked.

Deleted: chrome___voicesearch_kevin.pdf 54.1 KB

chrome___voicesearch_kevin.pdf 54.1 KB Download

One issue here never resolved. It's a feature poorly implemented. Samsung Chromebook Plus.

This works again (59.0.3035.0) despite no commits originating here. 

I'm really curious why. I would guess something to do with native client?

Any word on this? Wondering if it works now on Samus too.

Bumping this

Ok google voice search is not working on Samus

Tested on Chrome Os version 59.0.3070.0/9469.0.0 

Anybody try it on a Kevin since my issue gotten rolled into this one?

Tested on Kevin and fails to enable Ok google option on setting page .

Bug logged
https://bugs.chromium.org/p/chromium/issues/detail?id=713778

Any updates? 

Just tested on ToT on samus.
In training steps, 'ok google' works fine.
After that, 'ok google' does not works.

#16, I was unable to apply the setting at first after returning to Canary, however I did a hard reset and was able to toggle it on again with full functionality.

Update on #19
I retested on ToT on samus, OS version: 9460.29.0.
It sometimes work after training steps. (More often, it does not react to "ok, google")

Then, I tested again on ToT on samus, OS version: 9533.0.0.
It works fine both in and after training steps.

willg76x@ could you confirm this works again on Kevin too?

This is pretty much what we've seen.  Sometimes it will work flawlessly other times it wont work at all and there's no pattern to it that we've been able to find.

Yeah, works, but can be flaky sometimes like noted above.

Yes, I think the odds to trigger on 'ok google' depends on how well I perform in training steps. For example, If I said 'ok google' loud and clearly in training step, it has higher possibility to work well.

What does it mean that the status has been changed to "Won't Fix"? Is this issue being disregarded or is it something that is out of Chromium's hands?

Re #26, "Saying Ok, Google (with hotwording enabled) does open the launcher but then immediately kills itself (i,e, the voice UI comes up but then goes away immediately)." seems fixed.
Tested on 9460.60.0, cannot repro the issue.