I guess our issue wasn't worth getting any response to. 

Sorry for slow response. We're trying to understand this issue.

Physically triggering the lid-close sensor will trigger a screen-off/lock. It shouldn't be easy to do that accidentally. If the lid-close is triggering accidentally that would be a hardware defect on some level.

I suspect the "Status area_BrightnessChanged" message event is a side effect. Chrome OS logs can be difficult to interpret.

Its a strange occurrence as it work in OS versions prior to 53. Not sure what was modified and that is what lead us to believe that an OS change was the culprit. We have this model for about a year and it had up until this point been our least troublesome machine in the fleet. 

It's possible something changed in the switch detection making it more likely that a noisy/flaky switch would cause a problem.  I'm not aware of such a change, but it's a big codebase.

Is it a few devices experiencing this, or is it fleet-wide?

I'm retagging this to get some other people looking at it.  Also adding nsale@ and alexpau@ who know more about those specific units.

Please trigger the issue again and then immediately unlock the screen and hit Alt+Shift+i and submit a feedback report (if you use a different email address to file the report, please mention it here). Doing so will upload system logs that can be inspected to see what happened. Thanks!

FYI: Some of my fellow tech reported this last week and just attached my name to the reports

Thanks, here are the reports and what the power manager saw:

http://feedback/#/Report/15154344905
11/02 14:15:23  suspended
11/03 07:15:13  resumed
11/03 07:15:13  lid opened
11/03 07:15:52  lid closed
11/03 07:15:52  lid opened

http://feedback/#/Report/15154471821
11/02 14:15:18  lid closed
11/02 14:15:18  lid opened
11/02 14:15:18  lid closed
11/02 14:15:20  lid opened
11/02 14:15:20  lid closed
11/02 14:15:20  suspended
11/03 07:11:59  resumed 
11/03 07:11:59  lid opened
11/03 07:12:12  lid closed
11/03 07:12:13  lid opened
11/03 07:12:13  lid closed
11/03 07:12:13  lid opened
11/03 07:12:27  lid closed
11/03 07:12:27  lid opened
11/03 07:13:23  lid closed
11/03 07:13:23  lid opened
11/03 07:13:29  lid closed
11/03 07:13:29  lid opened
11/03 07:13:34  lid closed
11/03 07:13:34  lid opened
11/03 07:13:58  lid closed
11/03 07:13:58  lid opened
11/03 07:13:58  lid closed
11/03 07:13:58  lid opened

----

So yeah, it looks like the lid switch is being flaky. Moving to the EC component so someone there can comment on whether it could be a firmware issue or if it's definitely a hardware issue.

How many devices is this impacting? i.e. is this seen on multiple/many different N21s/N22s or just one?

The reason i ask is it would seem to be unlikely (but not impossible if they are all similar age) to have multiple HW failures all at the same time.

Also, would it be possible to test a failing device on R54 stable and/or R55 beta release? There was a graphics issue seen which has been fixed in R54 although it doesn't sound like the same issue.

The other useful data point would be to take a failing device back to R52 if the issue was only seen after R53 updates.

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot