-
-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
Update for 'A-JAZZ AKC084' (A-JAZZ AKP846) #24853
Comments
Not sure where you're getting your firmware from but it's not a QMK-supported board. |
|
Sorry if I don't understand something, but here it is: |
For the indicators, yes, that should be changed, although I'm not sure where the Scroll Lock LED would be as there is also no Scroll Lock key either. The default keymap and bootloader instructions in the readme do look like they need adjustment as well. |
In the standard layout, the ScrollLock button is activated via FN+DEL. The layout can be set according to the picture and keyboard instructions: |
Issue Description
Hello everyone!
I recently purchased an AJAZZ AKP846 keyboard and attempted to flash it with the standard QMK firmware. In the web configurator, I selected the model 'A-JAZZ AKC084', customized a few keys, and flashed the device. However, I encountered several issues:
Keyboard Indicators:
The standard firmware includes indicators for CapsLock and ScrollLock. After flashing, these indicators changed to CapsLock and NumLock, even though there is no NumLock key on the keyboard.
Layout Mismatch:
The standard layout does not match the keys Pause, Del, End. This discrepancy is visible in the image in the Readme and on the product page in the store.
BootLoader Entry Instructions:
To enter BootLoader mode, you need to press Esc and reconnect the keyboard, instead of Enter as stated in the instructions.
Can I make changes and update the firmware for the 'A-JAZZ AKC084' model to help new users avoid these issues? Or are 'A-JAZZ AKC084' and 'A-JAZZ AKP846' different keyboard models?
Thank you!
The text was updated successfully, but these errors were encountered: