Fixed RGB issues after QMK flash

[FrostyApeOne]

• Updated the RGB Matrix to include missing LEDs

• Added CAPS and NUM RGB indicators to the Galaxy100.c

• This PR also includes fixes and changes added by @samboosa5k which include:

• VIA Support

• Rotary Knob button mapping in VIA

[FrostyApeOne]

Commented out as not supported by this keyboard. Uncomment if needed.

[FrostyApeOne]

Commented out as not supported by this keyboard. Uncomment if needed.

[samboosa5k]

Wow @FrostyApeOne thank you for fixing this 😎 , I'm gonna flash this right away!

[FrostyApeOne]

@samboosa5k No worries, I think LEDs are just one of their firmware issues that we fixed, I believe the Bluetooth and Wireless also stop working after flashing Qmk, or maybe it was only mine that was faulty!
However if you don't use those and use it wired only the it doesn't matter and you should be fine.
Unfortunately their support ignored all my messages and no responses so far.

[samboosa5k]

My wireless is also not working, but this is very common: Epomaker pull requests are usually marked as crippled firmware because their source code is broken and this is the result.

Check this:

• https://github.com/qmk/qmk_firmware/pulls?q=is%3Apr%20is%3Aclosed%20epomaker
• https://docs.qmk.fm/license_violations
• https://www.reddit.com/r/Epomaker/comments/x7joao/epomaker_continues_to_advertise_some_of_their/

In conclusion, thank you for the collaboration 😄, this is a great keyboard. I only use the keyboard wired anyway, but Epomaker customer service + engineers must improved haha.

[FrostyApeOne]

My wireless is also not working, but this is very common: Epomaker pull requests are usually marked as crippled firmware because their source code is broken and this is the result.

Check this:

• https://github.com/qmk/qmk_firmware/pulls?q=is%3Apr%20is%3Aclosed%20epomaker
• https://docs.qmk.fm/license_violations
• https://www.reddit.com/r/Epomaker/comments/x7joao/epomaker_continues_to_advertise_some_of_their/

In conclusion, thank you for the collaboration 😄, this is a great keyboard. I only use the keyboard wired anyway, but Epomaker customer service + engineers must improved haha.

I see, interesting, to be honest I didn't know any of these, I literally got into the world of Mech Keyboards 2 weeks ago while searching for a good keyboard and trying not to pay £230 for a Keychron keyboard 😅
As you said this is a great keyboard physically and especially with the VIA support. But it's a shame that they don't provide the full QMK source code.

Sadly their support isn't any good, they stopped responding me, and shockingly removed my post of asking for help in Reddit 😳

I don't have any experience with QMK or C programming but I don't believe fixing this is going to be too hard, it just need some time spent on it and figuring it out.

I hope these PRs and comments (if not removed) will raise some awareness and help the others. 🙏

[Kolesan666]

guys, could you fix whireless connection?

[samboosa5k]

guys, could you fix whireless connection?

Unfortunately, no. It was a miracle me + @FrostyApeOne got anything to compile, but please feel free to do some research and maybe you will succeed 🧠

[manindersarao]

Hi @samboosa5k / @FrostyApeOne - thanks heaps for your efforts on this. I'm trying to compile this branch and getting compile errors
Compiling: keyboards/epomaker/galaxy100/rgb_record/rgb_record.c In file included from <command-line>: keyboards/epomaker/galaxy100/rgb_record/rgb_record.c: In function 'rgbrec_update_current_channel': ./keyboards/epomaker/galaxy100/config.h:62:48: error: 'EECONFIG_USER_DATABLOCK' undeclared (first use in this function); did you mean 'EECONFIG_USER_DATA_SIZ E'?

my qmk --version is 1.1.8 and qmk-firmware 0.29.11

Have you guys seen similar error before?