[RESPONDED] Waking from suspend w/ lid closed

[Harry_ten_Berge]

@Matt_Hartley

To be clear, as shown in the video above, resume, backlight is off on keyboard. Fn plus spacebar is not bringing it back as you tap it a few times? And this is with the latest BIOS, Framework Laptop 16?

Yes, exactly that.

[jared_kidd]

@Harry_ten_Berge

Up until now a suspend/resume always resulted in the backlight not working anymore.

Regarding this. Is it possible you might have set up the udev rules listed here and forgot about it? When I tried them I had the same issues you mention, they cause the issue; the keyboard backlight not working after resume from suspend. Without those rules, the backlight never fails for me.

[jared_kidd]

@Matt_Hartley

I agree, which is why this will be officially addressed long term in an upcoming BIOS update.

Hey Matt, It’s been almost 5 months since this was posted. Can you please update us on the status of the ever expanding list of bugs that need fixing on the 16? 5 months on top of the year since this device was released is an eternity in tech time. Is Framework seriously struggling on the software side still? Software/firmware issues are killing this product and I do not want to see that happen.

[Harry_ten_Berge]

@jared_kidd

Software/firmware issues are killing this product and I do not want to see that happen.

Totally feel the same. My company is considering more 16’s, but as ‘first user’ I’m seriously hesitating because of this. The backlight issue is still not fixed, and the last firmware update is ages ago. And on top of that the biggest issue that makes me hesitant for bying more 16’s: lack of communcation.

[James3]

I seem to remember that FW used to be much more open with future plans up until the FW16 release. The batch 1 FW16 was months late. The abuse they received from customers was extreme. Some customers were even stalking their support staff! So, they changed policy. If customers don’t know about a pending release being late, they cannot complain.
So, effectively, it is their customers / users that have caused FW to clam up.
I think it is a case of a few bad customers making the rest of their customer base suffer.

[Charlie_6]

Was some bad customers complain/abuse predate the batch 1 FL16 late, or the other way round? Either way the correlation is insufficient to conclude causation. I think it could be unpredictably, supply chain issues, tariffs etc. Correct me if I’m wrong

[jared_kidd]

@James3

The abuse they received from customers was extreme. Some customers were even stalking their support staff! So, they changed policy. If customers don’t know about a pending release being late, they cannot complain.
So, effectively, it is their customers / users that have caused FW to clam up.

That’s unfortunate if true. Closing up like this will hurt the company far more than having to deal with the minority insane “customers”. With the Framework 16 already being out, holding back info about fixes is the last thing they should be doing because that tells everyone they are giving up on an existing product line. I see people all over the forums complaining more and more and it’s a terrible look. Also, whether they are quiet or not, their actions speak the loudest. Not having any bios update for this long is quite telling.

[jared_kidd]

@Matt_Hartley

To be clear, as shown in the video above, resume, backlight is off on keyboard. Fn plus spacebar is not bringing it back as you tap it a few times? And this is with the latest BIOS, Framework Laptop 16?

I finally tried your sleep solution as I was going to drive into work this Friday and didn’t want to have to shut the laptop down while traveling. It worked great for this purpose but I do have the same issue as others, in that it completely disables the keyboard backlight. After waking the laptop up again, the keyboard backlight remains off and there is no way to enable it again.

To fix it without rebooting, this worked:

for device in /sys/bus/usb/devices/*/power/wakeup; do echo enabled > "$device"; done

And then sleep and wake it again and keyboard will be back to normal.

[marsmathis]

Honestly, how the hell is this still a problem? @Kieran_Levin care to explain why this isn’t fixed? We are all aware that we bought a device which might have teething problems in the first half year or so, but not having a BIOS update to remedy this issue after more than a year is not acceptable.

[Myriad]

I’m still sort of dealing with this. I cannot tell what’s doing this-- from what I can tell, I don’t even need to have the laptop closed and it can just be sitting in place and it’ll just sometimes do this behavior. I’ve gotten into the habit of, whenever I shut down the system, I’ll power it back up and immediately go into the BIOS, then shut it off from the BIOS, which seems to prevent this from happening. Of note is that I never use sleep mode, or any sort of “suspend” or “hibernate” mode, only using the actual “shut down” option within Fedora. I’m guessing even that’s not a true “shut down” but it’d be nice if I could make it just do what I expect to begin with.

Mostly just posting here to say it’s still happening. Not sure what happened to the BIOS update or if I’ve just not installed that or something.

[HandyHat]

Are there any workarounds for the poor Windows users?

Running powercfg /devicequery wake_armed doesn’t give me anything useful and the Keyboard entries in Device Manager don’t have any Power Management options.