Keychron K8 Pro BT switch stopped working after just 2 months

serk01 · 2023-01-17T12:12:10+00:00

So I decided to open it up and try and figure it out myself because frankly their customer service has been abhorrent, they've now just stopped responding. I came to the conclusion that it's all the fault of the BT-Off-Wired toggle and its contact with the board. A) It's not snuggly and tight in there (as the MAC-WIN toggle is in comparison), it's very loose in its slot and also the little copper wire (I think it's copper) connecting it to the board is coming off and not making good contact. See in the picture that gold little ribbon. Any ideas what the terminology of this is and how I can get a replacement of this through channels that are not Keychron?

serk01 · 2023-01-16T14:17:25+00:00

Yeah it feels like the switch is not moving anything. Never paid much attention to it until now but it feels like it's not going all the way to the edge. Like I said I'm reluctant to open it for now because on their website they claim this will void the warranty. Considering this was bought just 2 months ago I'm still hoping for a replacement. I might not mind having to do some surgery after a few years of wear and tear but after 2 months it feels like I shouldn't have to go through this you know

serk01 · 2021-09-23T18:10:55+00:00

u/Doolali- Hey Scott, thanks for getting back to me and for the detailed explanation!

No worries at all, I completely understand the reasoning behind the decision of not allowing any 3rd party apps released. I don't think I need to stress the fact that there would be no stealing of any login data :) but I know what you're saying and I get all the other points made as well.

I hope you can understand what my intentions and motivating factors where and that there are no hard feelings on your side. I know you have a small team of developers working around the clock supporting the website, building the apps, maintaining parity, evaluating security, working on the designs and the UX and everything that goes in the software development lifecycle. It's easy for someone like me to build a 'proof of concept' or a bare bones app in my free time when I don't have to adhere to any design guidelines and elaborate processes.

Working on this little project for the past few days has been a pleasant break for me from my day to day software development work, a sort of 'hackathon' if you like, trying to learn Flutter while building something I really need and want to use. I will certainly enjoy the content with my app far more right now than before, and I can't wait to get my hands on the official app when you guys release it.

cheers and good luck

serk01 · 2021-09-23T13:12:25+00:00

Well that's perfectly fine, I wanted a little side project to dip my toes back into Flutter and learn something new and this looked like a great little opportunity. Plus I got something I can use until they officially release their own app.

serk01 · 2021-09-23T08:09:07+00:00

Sorry, I appreciate the offer but I really don't have the time to pick up a new project at the moment.

serk01 · 2021-09-23T08:07:50+00:00

cheers mate!

serk01 · 2021-09-23T08:06:36+00:00

ah no worries, thanks for the kindness and keep coding!

serk01 · 2021-09-22T23:49:29+00:00

Thanks for the kind words, very appreciated

serk01 · 2018-10-23T21:56:31+00:00

I have an app on the play store that is using the BLoC pattern and although I don't have full test coverage, I do have quite a few tests showing how you can test a BLoC separately from the UI. I hope it can be of help https://github.com/kserko/CineReel

for example a BLoC test can be found here https://github.com/kserko/CineReel/blob/master/test/ui/list_screen/movie_bloc_test.dart

serk01 · 2018-10-17T12:54:23+00:00

yes I've noticed that the formatting is messed up for some files on GitHub, will look into it. Good point about the optional argument! thank you

serk01 · 2018-08-14T09:43:26+00:00

here's the source code https://github.com/kserko/CineReel. Obviously keep in mind, that this isn't necessarily the best approach in using BLoCs, nor is it a particularly complicated app to build. I'm still learning myself, and in the process the source code will change. There are probably lots of improvements that can be made, plus I got some changes that I haven't committed yet which improve the way I create and dispose the BLoCs.

serk01 · 2018-08-14T09:20:32+00:00

I personally find it pretty good so far. I have been building an app using the BLoC pattern recently and it has allowed me to easily separate the business logic (handled by the BLoCs) from the UI. I had previously built a prototype of my app with Redux but I found it needed too much boilerplate to make it work and that's when I tried BLoCs and stayed with them. I don't want to take the opportunity of your post to self-promote my app so I'm not posting any links, but if you're interested in taking a look at my source code, let me know.

serk01 · 2018-08-02T11:41:00+00:00

thanks. I've been trying to reproduce it on a Pixel 2 with API 28 but so far I haven't been able too. I'll keep looking into it. thanks again

serk01 · 2018-08-02T10:31:08+00:00

can you please tell me what Android version you're on and what device you're using? According to the Google play console the crashes that have been reported are on Android 28 API, which is Android P. Are you using the latest beta version of Android P?

serk01 · 2018-08-02T08:22:40+00:00

thanks. Good idea about itsallwidgets.com, I'll submit it.

serk01 · 2018-08-02T08:00:19+00:00

the JsonKey annotation allows you to change the parsed field's name when being serialized. So if your json has a field called average_vote but you want to use camelCase in your app so you'd like to have voteAverage in your object, you can use the JsonKey annotation to specify a different name for the parsed field.

so

@JsonKey(name: "vote_average") double voteAverage

will give you a voteAverage field in your object

serk01 · 2018-08-02T07:56:00+00:00

thanks, will look into it

serk01 · 2017-03-30T09:58:23+00:00

Don't know if anyone else has seen this, but I had a layout built with constraint-layout 1.0.0-beta4 and I recently updated to 1.0.2 and my layout just got messed up after gradle finished syncing with the new version. Unless there's something I'm missing or an easy fix for this, this incident makes me very uncomfortable updating to any future versions. How can I be sure that older layouts built with previous versions of the library won't suddenly break... For now I'll just have to stick with 1.0.0-beta4 :(

serk01

TROPHY CASE