Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GK104 support #216

Open
keeperus opened this issue Jan 6, 2025 · 2 comments
Open

GK104 support #216

keeperus opened this issue Jan 6, 2025 · 2 comments

Comments

@keeperus
Copy link

keeperus commented Jan 6, 2025

Hello!
Just received a new keyboard "Skyloong GK104 Pro", but it's not supported yet.
I've configured it for my Win 11, but the configuration seems to be held in the system settings so it won't work with my main OS (Ubuntu 24.04)

Bus 001 Device 012: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge Mini Keyboard]
Bus 001 Device 015: ID 1ea7:0169 SHARKOON Technologies GmbH 2.4G Mouse
Bus 001 Device 018: ID 1ea7:0907 SHARKOON Technologies GmbH Keyboard
It's the same device.

Would be nice if you could add it.
{
"ModelID": 656802045,
"FWID": "0x83223310",
"Name": "104",
"LEType": "0"
},

{
"ModelID": 656802049,
"FWID": "0x83223320",
"Name": "104",
"LEType": "0"
},

{
"ModelID": 656802051,
"FWID": "0x84223310",
"Name": "104RGB",
"LEType": "0"
},
{
"ModelID": 656802044,
"FWID": "0x80223310",
"Name": "104RGB",
"LEType": "0"
},
That's what I've found in Win11 client
Copying files can help, but it would be nice to have it by default)
it runs, but still impossible to configure my kb

зображення
my kb is '104RGB' model:656802051 fw:v5.133

P:S: how can I map the knobs in UserData? it seems all of the knobs have the same name

@keeperus
Copy link
Author

keeperus commented Jan 6, 2025

keymap.js
{
"KeyName": "Print Screen VOLU",
"Show": "PrtSC",
"LogicCode": 122,
"LocationCode": 151,
"Position": {
"Left": 771,
"Top": 135,
"Width": 21,
"Height": 21
}
},
{
"KeyName": "Print Screen VOLD",
"Show": "PrtSC",
"LogicCode": 123,
"LocationCode": 152,
"Position": {
"Left": 791,
"Top": 135,
"Width": 21,
"Height": 21
}
},
{
"KeyName": "Print Screen MUTE",
"Show": "PrtSC",
"LogicCode": 121,
"LocationCode": 153,
"Position": {
"Left": 771,
"Top": 155,
"Width": 42,
"Height": 21
}
},

profile.json
{
"Index": 121,
"MenuPID": "",
"MenuID": "",
"MenuName": "",
"DriverValue": "0x02002C00",
"KeyLE": {
"GUID": "",
"Name": ""
}
},
{
"Index": 122,
"MenuPID": "",
"MenuID": "",
"MenuName": "",
"DriverValue": "0x02002C00",
"KeyLE": {
"GUID": "",
"Name": ""
}
},
{
"Index": 123,
"MenuPID": "",
"MenuID": "",
"MenuName": "",
"DriverValue": "0x02002C00",
"KeyLE": {
"GUID": "",
"Name": ""
}
},

should I add the knobs to the KeyValues.cs and recompile it?

@pixeltris
Copy link
Owner

It looks like you got it working, you might need to adjust the width/height of the window as it needs a certain aspect ratio otherwise buttons can't be pressed.

should I add the knobs to the KeyValues.cs and recompile it?

Yea if there are any new driver values you'll want to add them into the cs file. I think they are mostly for mapping using the command line / txt configs so they might not be needed if you're using the UI.

I really need to update the files for this project as there are quite a few missing keyboards now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants