Adding initial support for the EPOMAKER tide75 (Few Issues)… #797
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here's a little PR to add support for the tide75 from EPOMAKER.
As some of you already know, EPOMAKER's PRs to QMK upstream have been put on hold due to them not releasing their wireless bindings. While these bindings are currently drafted to be merged for the tide65, with the firmware for the tide65 already being in the upstream repo, this is not the case for the tide75 as of yet, so much of the base of this vial implementation has been pulled from EPOMAKER's own tide75 repo.
However, this repo seems to be slightly outdated in that there's some bugs that weren't present with the keyboard coming stock. The main issue is that the RGB matrices seem to be messed up, causing per-key RGB effects to be all over the place rather than taking the order they should, as well as the CTRL key not being lit up at all.
Secondly, the rotary encoder also seems to need to be turned twice to register, which also seems to be an issue with the firmware from EPOMAKER's repo once again.
To more or less confirm this, I re-flashed both the default and via keymaps which were provided, and the problem persisted, meaning that the official firmware for this board from the repo is buggy, and is different to what came stock with the board. Another giveaway that the firmware was different is that originally, my board's 'manufacturer' was Hangsheng, but since flashing with this firmware has changed to HS.
Currently, I've reached out to EPOMAKER themselves and @sdk66 who seems to be the main firmware developer for the board to see if I can get ahold of the proper, fully-working firmware and implement it here, allowing me to un-draft this PR. Just keep in mind that flashing this firmware in its current state will mess up your RGB, with no way to go back till Epomaker releases the right firmware.
PS. I know there's quite a bit of junk within the files that isn't interpreted by vial, I'll be looking to get rid of these later on once I can get ahold of the proper firmware for this board, but if anyone more experienced wants to help me brush everything up I'd appreciate it :D.
This is my first real PR on Github, so apologies if I've done anything wrong :p