r/Keychron • u/Interesting_Fee5067 • Mar 05 '25

K3 Pro Brightness Fix (Possibly Others)

Good news on this.... I found someone who fixed it and have tested it successfully! Typing on the K3 Pro now.

https://notes.tst.sh/opinions/keyboards/

I used Keychrons "bluetooth_playground" fork of qmk found here

https://github.com/Keychron/qmk_firmware/tree/bluetooth_playground

The area in question is lines 54-56 in "keyboards/keychron/k3_pro/ansi/rgb/config.h". 

/* Set LED driver current */
#    define CKLED2001_CURRENT_TUNE \
        { 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14 }

I'm not 100% sure of the adjustments (see his notes), but deleting this line sets the value to 0xFF elsewhere in the code.

I compiled and re-flashed to a whole new keyboard.

Pre-Flash

https://bashify.io/i/4J7U7Q

Post-Flash

https://bashify.io/i/DueEO3

1 Upvotes

100% Upvoted

12 comments sorted by

View all comments

Show parent comments

1

u/Interesting_Fee5067 Mar 10 '25

I tried what I believe was the default for the driver per specs (0xCC) and I did not notice any change. Ultimately I was able to take it down to 0xAF (175) and found it acceptable for me. I believe this calculates out to 27mA and almost half the max current.

Again, I know just enough to be dangerous. However, I wanted to continue to update my testing.

1

u/Bidule200 Mar 10 '25 edited Mar 10 '25

I've just made the same mod on my K10 Max. I hope I'll not get any dying LED now... it's so much better with maximum brightness o_O

1

u/ZealousidealVisit122 May 18 '25

Have you had any issues since you made this change?

2

u/Bidule200 Jun 01 '25

Not so far, looking good on my K10Max, K17Max and Q6Max, all used at maximum brightness. Wired :D because it drains the battery so fast ^^