Well, it shouldn't be a surprise that the case is not as good as would like it to be if you followed the news and the issues we had with the first company.
It's at least as good as Pandora's case though, and I definitely plan to improve the case in the future with new moulds (which are pretty...
Unfortunately, it's still the old unit. But I never had an issue with overheating myself (and you've got warranty as well), I guess it depends on which games you play (and you could even mod it to add cooling as well).
You can, it's just a config file.
It's /etc/pyrainput.cfg, mouse.deadzone
You can increase the deadzone and see where yours works properly.
Restart the input daemon afterwards with systemctl restart pyrainput
As mentioned, I'll send the next batch of mails out this week (probably tomorrow).
Had to finish some other things first (assembling an original case and one with fixes applied so I can send them over to Greece so they know how to tweak the molds,
Closing the lid should switch off the backlight of the LCD at the moment (AFAIR).
We've not yet included that for the keyboard backlight, I usually switch it off manually before closing the lid.
Well, I only have the keyboard backlight enabled when I'm dark rooms anyways :)
Yeah, at that spot plastic is being injected (did I mention already that FA made some bad choices for the injection points?)
We're filing the area down already and I'm now doing it more thoroughly...
I can make a video how to best open and close the screen lid.
However, DRIFTING shouldn't have...
Alltogether around 30 so far.
Oh, it doesn't have to do with the number. When I'm assembling units, I am combining the same types.
So from order numbers 23 - 50 (which is what I'm currently assembling), I first count what I need and then assemble the units accordingly.
Some might've wondered why not all units I planned to ship until yesterday have shipped yet - and some followed IRC or our Discord channel and could imagine what the reason was.
During assembly, I noticed that about 10% of the units didn't want to boot up after they had been powered down.
This can be related to some weird audio mixing / channel mapping.
I already mentioned to aTc during the tester that it sounds as if the audio is coming from both speakers whenever I only play from the left one (as I'm sine waves for testing, this could've been my imagination and I've not further...
Yes, that can be the issue. The volume daemon is very simple at the moment and needs optimization (deadzone, polling, handling ALSA / PulseAudio, etc.... I'll post more about that.
That's why I mentioned to open AlsaMixer. If the volume wheel is the issue, you will see the AlsaMixer slider moving :)
Oh. And I remember there's some low-power mode for the audio stream.
It can be enabled / disabled in Alsamixer as well (it's that hpll or similar controller, forgot the name).
Maybe that can cause such issues.
I'll also try on the units I have here.
Hm, interesting. Please check the following:
1. Test if volume changes if you press on the case (not a key). The speakers use spring contacts - maybe they don't have a proper contact on your unit (which changes if you press on the case).
2. Open Alsamixer to see if the volume actually changes.