my second framework keyboard delete key just died. the second time i went with the clear keyboard from framework and it died much more suddenly than the first. very frustrating!
same here. delete key started being intermittent about 3 months ago. and about 1 month ago it completely stopped working. very annoying
We started using Framework 13 Laptops in our small business. 2 of 3 have now this problem.
- 11th gen intel, del key works, but was typed on significantly less…
- 12 & 13th gen intel, del keys broken, were used significantly more… OS are Linux & Windows
On the 12th gen I tightened the screws and for ~2 weeks the key worked again. But now it stopped while the screws are not loose 
I really think it has nothing to do with OS/usb hubs/charging port use etc, but rather an internal wear or hopefully some bending on the edge of the keyboard that could be reversed…
As much as I like Framework, I really hope they address this issue soon. It’s clearly not a defect of an individual unit anymore. I don’t want to buy a replacement part that will have the same problem soon… I have no problem buying a new keyboard but one that fixes this issue.
UPDATE
I am late in writing this, but I feel obligated. Maybe a week after tightening the screws, my delete key stopped working again and no amount of tightening would help. Hopefully it may be a semi-permanent fix for others?
I agree with the general sentiment here: it would be much appreciated if Framework somehow acknowledged the problem. In my experience, there seems to be a general issue of not recognizing defects/QC. In this case, I don’t want to buy a new keyboard/cover that is just going to fail again.
In other words, when does a reoccurring failure become a defect, and when does it become the responsibility of a (good) company to acknowledge it?
We traced the root cause of this back to a subsupplier issue where some Input Cover parts had a burr in the lattice near the delete key. We’ve since added additional quality checks. If you’re running into this, you can reach out to support to confirm if this is the issue you are seeing and then receive a replacement Input Cover.
Edit to add some clarification that I noted on Reddit: Our quality team was able to root cause this fairly recently, as the failure analysis process spanned multiple suppliers. On the support aspect of it, I’ve informed the team just this morning that we need to update the support flow for contacts where we can determine this was the root cause. It will still take a little time to roll out an updated process.
16 Likes
As a datapoint, the del key of my 11th gen framework also stopped working. I chalked it up to bad luck. I could repair it myself with a replacement keyboard, and I’m a happy camper with a spare keyboard minus a del key. Bonus: my framework now has a super key.
2 Likes
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.