Really Disappointed with Framework QA

[betalars]

I honestly am right now shocked with how poor the Quality Assurance over at framework seems to be.

 

I am using a Framework 16 on Linux and am so far experiencing these glaring issues:

 

1. The Keyboard module is being recognized as an external USB Device, breaking palm rejection.
2. When grabbing the laptop to put in my backpack, I always press down the trackpad, causing my framework to wake up from suspend and become a baked potato in my backpack.

The first issue has been resolved in the new libinput version and you can fix the palm-rejection issue yourself while waiting for your distro to update libinput.

 

However, the waking up while lid is closed behavior is a lot more difficult to resolve on your own (I am as of writing this still trying to create a workaround for this) and it should just be resolved by firmware.

 

And honestly ... the firmware. On release, the framework 16 was configured to wake up on lid closing.

 

None of this has been mentioned in the review on LTT.

 

I am pretty disappointed in framework and LTT right now. Stuff like throwing your laptop in a backpack just needs to work out of the box. And I do not know if this is the case, but I really would like to see a procedure for finding day to day quirks to be part of the labs reviewing laptops.

 

Because all battery life tests are pretty meaningless when suspend is botched on a device.

[Kilrah]

7 minutes ago, betalars said:

And honestly ... the firmware. On release, the framework 16 was configured to wake up on lid closing.

7 minutes ago, betalars said:

when suspend is botched on a device.

Suspend being botched is a Microsoft-enforced pain every laptop is currently subject to and that LTT has made videos complaining about, IMO it doesn't make sense pinning a specific manufacturer ties or not when everyone's affected anyway.

[betalars]

2 minutes ago, Kilrah said:

Suspend being botched is a Microsoft-enforced pain every laptop is currently subject to and that LTT has made videos complaining about, IMO it doesn't make sense pinning a specific manufacturer ties or not when everyone's affected anyway.

As I have written in my post:

This is botched, because framework configured a touchpad press on a closed lid to trigger a wakeup.

At the release, this was botched, because framework configured the lid closing event to trigger a wakeup.

 

Both behaviors happen on a firmware lavel and are independent of any additional microsoft mess.

[TempestCatto]

Not sure what flavour of Linux you're running, but I bet just like in Windows, there's a way to not "allow this device to wake the computer" which is a checkbox somewhat buried in the mouse settings for Windows.

[betalars]

7 minutes ago, TempestCatto said:

but I bet just like in Windows

Unfortunately, very few linux developers actually seem use laptops, so fixing stuff like this most often requires users to dig really deep and sift trough incredibly cryptic config options to resolve.

 

But I guess I can ask for this as an enhancement in kde.

[betalars]

Adding Insult to Injury here.

 

To prevent a device from waking your linux laptop, you need to configure that using its manufacturer-set ACPI name.

 

Most laptops follow simple naming conventions here, like using TPAD for trackpad.

 

Framework however choose to not do this, so I have to figure out witch device of these is meant to be the trackpad:
GPP0, SWUS, SWDS, GPP2, GPP5, GPP6, GPP7, GPP8, GP11, SWUS, GP12, SWUS, XHC0, XHC1, XHC2, NHI0, XHC3, NHI1 or XHC4

 

[Nordithen]

3 hours ago, betalars said:

As I have written in my post:

This is botched, because framework configured a touchpad press on a closed lid to trigger a wakeup.

At the release, this was botched, because framework configured the lid closing event to trigger a wakeup.

 

Both behaviors happen on a firmware lavel and are independent of any additional microsoft mess.

That... sounds like a OS issue, as I've never heard of anyone having that happen on Windows. Which distro are you using? Obviously use whatever distro you want, but I don't think it makes sense to complain that aspects of it don't work out of the box unless you're using one of the distros they officially support.

[betalars]

30 minutes ago, Nordithen said:

That... sounds like a OS issue, as I've never heard of anyone having that happen on Windows. Which distro are you using? Obviously use whatever distro you want, but I don't think it makes sense to complain that aspects of it don't work out of the box unless you're using one of the distros they officially support.

I replicated this behavior on the officially supported distros.

[Nordithen]

11 minutes ago, betalars said:

I replicated this behavior on the officially supported distros.

That sounds like something the Framework team would be interested in hearing about then, in case they aren't already aware of it. I suggest pinging Matt Hartley, probably on the Framework community forum.

[betalars]

17 minutes ago, Nordithen said:

That sounds like something the Framework team would be interested in hearing about then, in case they aren't already aware of it. I suggest pinging Matt Hartley, probably on the Framework community forum.

I did this before complaining here. It is just really frustrating how many small things are not working right now with my device.