Open caksoylar opened 2 years ago
It would also be nice to pose them like FAQs, but we already have an FAQ page which doesn't deal with any troubleshooting questions.
I think that an FAQ-style troubleshooting page would be a helpful format. Perhaps if we restructure the Troubleshooting page as you propose, we could simply continue to refer the page as "Troubleshooting" in the sidebar – leaving FAQ as-is?
If anyone can think of other common issues that could be a good fit we can note them in this issue as well.
A quick one from the top of my head that popped up yesterday, it's not super common, but we do see questions about firmware size from time to time and this tip seems to be rather unknown:
west build -t rom_report
and ram_report
to see at a breakdown of things.Examples where this has come up:
If anyone can think of other common issues that could be a good fit we can note them in this issue as well.
We could also mention "double keypresses" and link to the Debouncing docs. This one also comes up now and again.
Thanks @dxmh!
I think that an FAQ-style troubleshooting page would be a helpful format. Perhaps if we restructure the Troubleshooting page as you propose, we could simply continue to refer the page as "Troubleshooting" in the sidebar – leaving FAQ as-is?
Yeah, I think this is a good idea. Some of the existing section headings would need to be renamed.
I added the two other issues you described to the main post. I also added a big one I had missed re: right half of split keyboards. It can refer to a page like proposed in #948 when it exists.
Here’s a couple more FAQs:
Would it be worth having a separate keymap/behavior-specific FAQ section? That way we can have one focused on troubleshooting problems and another on common keymap use cases.
That sounds good. Less of an FAQ and more like a "tips and tricks" section for using features and behaviors in creative ways. 🙂
Another for the troubleshooting FAQ?
Q: My keyboard causes my computer to wake from sleep periodically.
A: There are reports of macOS being woken by the battery status notifications. One workaround is to enable deep sleep for your keyboard, which will prevent the broadcast of battery status notifications.
References:
Related issue: https://github.com/zmkfirmware/zmk/issues/1273
There are a few common problems that folks run into and they usually get helped in the Discord, but I think they can be documented in the Troubleshooting page with steps to help debug and resolve them.
It would also be nice to pose them like FAQs, but we already have an FAQ page which doesn't deal with any troubleshooting questions. I currently have two such issues in mind with a sketch on what the recommendations can be:
If anyone can think of other common issues that could be a good fit we can note them in this issue as well.
Edit: Updating with a few more suggestions from below.
west build -t rom_report
andram_report
to see at a breakdown of thingssettings-reset
procedure before flashing right side firmware