[Verizon HTC One (M8)] dragontology:
Not seeing an M8 Layers folder. Could you link it? Oh wait — this? Downloading now. Got another ROM I'm going to try, and I strongly suspect it won't boot. So I'll try this too. Would really like to play with some AOSP/GPE goodness tonight.

edit, 9 hours later: Booted in just under 4 minutes. 3:53; I used a stopwatch. ;) Very nice. And that includes the "Optimizing app X/Y" thing, except you guys changed it to say "Installing" rather than "Optimizing." (I don't care what the strings are edited to say, to be honest.)

Got GPS, for now. GPS has been one of my major problems running anything but Sense. The other major issue I've had is the speakers. At high levels they sound bad. Or quiet (as an attempt to solve the real problem). Playing the newest 311 album (it's at the top, and it has great range) and it's plenty loud, with just a little scratching. Turn the volume down 2 notches, and it sounds great.

edit, 26 hours after last edit: This ROM is great. Layers is awesome, I got a good dark theme going on and I love it.

One kinda big problem: Speakerphone could be said to be broken. It works, but at its highest level, I still have to hold the phone up to my ear to hear it. I do have a Bluetooth earpiece, but the quality of the speakerphone on the One M8 has made me lazy, I just hit the speaker button and use it that way. Media is plenty loud at max, so I don't understand why speakerphone is capped so low.

The screen off gestures don't work. With "double tap to wake" enabled in settings, that sometimes works. This phone has spoiled me, being able to swipe up to bypass the lock screen. (But then, even on the stock ROM, that meant you couldn't use a lock screen replacement, because then you'd be here.) That might just be a limitation of AOSP. It works in GPE, but GPE runs HTC code. Can't fault AOSP there.

Battery is fine. The ROM chewed right through it on the first run, but we started low. Took my phone off the charger 9 and a half hours ago, and I'm down to 62%. That's pretty agreeable. It says I have 16 hours left, estimated of course. I only need 9. Might use 10.

SlimPie is as awesome as I remember it from the d2usc (Samsung Galaxy S3). I had problems activating it in the camera, though. Google Camera, that is. Didn't use AOSP Camera much. It doesn't have photo sphere, which I never use, but like to have around. Over half the time, it wanted to focus where I was dragging from. I was only worried because I disabled the navbar. It was great until I couldn't get to the Pie. I would not recommend disabling the navbar.

edit: the next night: Well, looks like this ROM is plagued by the infamous TWRP /data encrypt bug. Link goes to my YouTube channel where I trip the bug on a different ROM. I actually discovered the bug trying to MAKE a Nandroid, which doesn't screw up the phone. It's restoring one that does it, since it overwrites /system, then when it tries to WRITE to /data, it soft bricks it, and the user must RUU. The problem is, TWRP thinks /data is encrypted. The ROM is fine, as far as reading/writing to /data. It's just, if I want to change ROMs at any time in the future, or do anything else with TWRP, I'm gonna need to RUU first. Flashing a ROM that writes absolutely nothing to /data should work, too, but generally a lot of them write symlinks to /data, and that screws it up. I mean, /data/media is your internal storage, and nearly all of them symlink that to something like /sdcard, so when it tries to to that... Can't mount data for r/w. Install fails.

I wonder... If I get a 128GB microSD card (because I need the space!) I wonder if I can symlink /data/media to a folder on the microSD card. I mean, the /data partition is still gonna get seen as encrypted by TWRP, but yanking the microSD card would make the RUU a lot less painful (internal storage wouldn't really be lost). The cost would be the use of the phone's considerable internal storage, of course. Hence the 128GB card. Just thinking out loud.