[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] FalconFour:
So... I'm looking to LineageOS as an upgrade on my Z2 Force, where being stuck at Android 8.0 has been a bit of a holdup as newer Android has better background app management and notification features.

I have a spare Moto Z2 Force I've used to test out LineageOS. So far it's been really amazing, but I held off putting it on my daily phone due to some bugs I've read about. As it turns out, I encountered every one of the known issues. :(

What can I do to help the developers solve these issues?

10/10 on the bug priority scale

Phone (calls) are completely unusable, as when you engage in a phone call (in any app that makes a "phone"-style call, like FB Messenger), it blanks the screen as if I'm holding the phone to my ear (I am not), and accessing controls is completely impossible - hitting the power button just shows the ambient display, or blackness, but never a phone UI. So I can't hang up the call. It gets stuck. This is a MAJOR BUG in my opinion, making it a show-stopper for using this ROM on the phone. I'd like to disable the prox sensor if possible, as that's a better functional tradeoff than not being able to control calls.

Update: Looks like this is a hardware issue, possibly. Using this proximity sensor tool, I was able to find that most of the time, the phone thinks the prox sensor is active ("close"). Pressing the area of my screen near the front-facing flash makes it register "far" for a while. The reading is completely digital - either 0.0 (close) or 5.000305 (far), nothing in between. It seems there's a reflectivity issue in this sensor (separating from the screen, maybe?) and it always sees its own reflection after it's sat out for a while. Simple fix: press the front-facing flash area of the phone to get your phone controls back. Seems likely that the stock ROM recalibrates this sensor during runtime, maybe.

2/10 on the bug priority scale

Ambient screen sometimes gets stuck-on - in my case, I rebooted the phone, didn't pocket it, left it on my table, aaaand... it just kept showing the clock.

Fixed:

https://www.reddit.com/r/Pixel4/comments/dm358m/_/f4xi1i6

9/10 on the bug priority scale

Moto Actions sometimes stop working completely - today I chopped the flashlight on, but couldn't shake it back off - and the chop flashlight and twist camera just completely stopped working from then on (hours later, still no fix). That's when I rebooted and got the above issue. I use both of those Moto Actions constantly (several times a day for both), and it's what has me stuck in the Moto ecosystem (that, and the Z2 Force's unbreakable plastic screen, an absolute killer feature I'm constantly thankful for). So if the Moto Actions stop working, I may as well have a Pixel.

5/10 on the bug priority scale

When a Moto Mod speaker is attached (I have the JBL SoundBoost 1), alarms are completely silent - neither out of the mod nor out of the speaker. Is it possible to redirect alarm sounds to a different endpoint? If they can't be played out of the Mod speaker, I'd prefer them to come out of the phone speaker. Just not totally silent. Music works fine, and plays with the screen off just fine.

Any way I can help nail down one or all of these? I'd really like to be able to keep using this phone with LineageOS. :)

update: LOL so I just smashed the phone on the ground in a fit of rage over more apps detecting "modifications" that Magisk couldn't hide, and kaked it, then found that my AT&T phone (my daily driver, used on TMo) has a locked bootloader that can't be unlocked because AT&T is a sick, horrible company... soooo this is probably the end of the road for me and LineageOS literally ever. Oh well.