search

WeirdTreeThing / cros-keyboard-map

Utility to generate keyd configurations for use on Chromebooks
BSD 3-Clause "New" or "Revised" License
33 stars 10 forks source link

Google assistant key on Pixelbook #11

Open denneyg opened 4 months ago

denneyg commented 4 months ago

Is there any way to remap the Google Assistant key on the Pixelbook (Eve)?

WeirdTreeThing commented 4 months ago

What keycode do you get in evtest when you press it?

denneyg commented 4 months ago

It generates type 4 )EV_MSC), code 4 (MSC_SCAN), value d8

Gary

On Mon, 12 Feb 2024 at 20:34, WeirdTreeThing @.***> wrote:

What keycode do you get in evtest when you press it?

— Reply to this email directly, view it on GitHub https://github.com/WeirdTreeThing/cros-keyboard-map/issues/11#issuecomment-1939528629, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARKVHQQTIXCS4B2RVZIKGG3YTJ4GHAVCNFSM6AAAAABDFIJUTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZZGUZDQNRSHE . You are receiving this because you authored the thread.Message ID: @.***>

WeirdTreeThing commented 4 months ago

Create the file /etc/udev/hwdb.d/61-eve-keyboard.hwdb and add the following:

evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGoogle:pnEve:pvr*
 KEYBOARD_KEY_d8=leftmeta

Then reboot

I dont think keyd is able to map this special key

sporeking commented 1 day ago

I have run the script to fix my google assistant key. However, neither before and after running the script make the assistant key available. In evtest I get nothing when I press the Google assistant key, but any other key is available. How can I make the assistant key available?

WeirdTreeThing commented 1 day ago

I just added support for this in the script. Pull my changes and see if it works now.

sporeking commented 1 day ago

Thanks for your help. But it seems that the situation has not improved. I have tried to modify 61-eve-keyboard.hwdb myself, but it didn't achieve any results. I am now very curious about which link is wrong. My pixelbook go is second-hand, and it was installed with manjaro when it came to me, so I don't know how the original owner flashed the UEFI firmware. I reinstalled arch linux myself, but the audio, keyboard mapping and other problems were not successfully fixed. Is there something wrong with my own installation? I plan to reinstall it according to Chrultrabook Docs when I have time in the future, but now I decided to make do with it, anyway, the Google Assistant key is not convenient. Anyway, thanks for your help.

WeirdTreeThing commented 10 hours ago

Try running evtest on it with the hwdb config and see which key it reports as.