[X 2014 Original Android Development] Jaytn:
Alright, now that I've been using this ROM for almost half a year now, I must say I'm pretty happy with it. Ok, there was nothing wrong really with the stock ROM, I just wanted to have the nice new Nougat features, but some CM Lineage sugar on top doesn't hurt either. That being said, I have some issues / minor annoyances, that would bring it just those last 10% of being awesome, so I'm assembling this post, hoping you can tell me your experiences and maybe help get over some of those points. Let's begin.

Oh right, my starting point was the first or second nightly of Lineage, which I clean flashed because the experimental didn't work. After that I've flashed several other nightlies over it and currently I'm on March17 build since from the reports here no build after that was really worth flashing.

Weird bugs​

I've seen here, that sometimes there just happen to be random bugs which may or may not be resolved by (repeated) clean flashing, but since that's somewhat of a hassle I want to talk about it first, and maybe see if someone else has it too.

•Mario Run - doesn't work. It just starts, shows the splash screen and closes itself again. Tried cleaning data / cache / dalvik, reinstalling etc, nothing works.

•MTP doesn't work. Ok I just double checked as I wrote this, works now, let's just write it off as a fluke.

•Files search - crashes. Whether opening the "Files" app or going via Settings->Storage->Explore (though I think it's the same app since recently?), the app crashes when performing a search. I think it didn't always crash, but one way I can consistently reproduce is the following:

Open Files app.

Switch to "XT1092" (internal storage)

Tapping the maginifying glass at the top

Enter "mp4"

Hit "Search"

"Files has stopped.

Open app again

Mute until device restarts"

•Goggles app - doesn't work. (no not a typo, I mean the "Goggles" image search app from Google) It seems to work mostly, except when I hit the shutter button to take a picture and start a search, nothing happens. But when I enable "Search from camera" in settings, I sometimes get notifications about what it found in my images, so that part seems to work, just not the taking an image part.

•Google Assistant - I don't have it. Do you have it? I thought it would be enabled on all Nougat devices with the Play Services 10.2.99 update. But mine just stuck on 10.2.98 for forever, last week or so I enabled Beta for Play Services and had Beta for the Google App even before that. I just can't get it to show up. Am I missing something?

Minor annoyances​

These aren't really breaking issues, just "first world problems" that bug me every once in a while.

•Live Display with Battery Saver - I like the built in "Live Display" which adjusts the screen color temperature based on time of day (more red / less blue towards the evening - that sleeping better hormone stuff). But, since at the end of the day I often run into the <15% area before I charge overnight, the battery saver turns on, and with it Live Display seems to turn off. Doesn't seem to make sense to me, because with that the screen actually gets brighter, so not really saving power on the OLED I guess.

•Custom Boot Animation - While the Lineage boot animation isn't bad, I like to customize and even made my own. But since the location in /data/local/ isn't supported anymore (I checked the source code), whenever I flash a new Nightly, my custom one in /system/media/ gets overwritten and I have to put it there manually again. Not really an issue but annoying enough that I haven't even bothered since the last flash.

•Clock resetting on reboot - As discussed before, the clock resets on a reboot to the device RTC. Not really a problem, but makes the phone be confused for a few seconds while it's updating the time. Plus, potentially an issue with random reboots due to the battery issue, while having no internet access.

•Date in Quick Settings - I'm the kind of guy who has to look at his watch 5 times in a row to remember what time it is, so I can forget about remembering what day it is (I'm happy if I know the month). On the stock or the CM Rom (can't remember), it would show the date in the notification bar (pull down ONCE) next to the time. Now I have to open the full quick settings (pull down TWICE) to show it. I know, it's on the lockscreen and the homescreen of the Pixel Launcher too, but that's usually at least one more tap/click away than just glancing at the notification bar. Ok, that's really a first world problem, but since there's enough space there I can't see why it can't be there and I didn't find a setting for it anywhere.

Features​

Ok, some of these might be "minor annoyances" too, but I think they're more of a feature request than a bug report, but think of this and the last category of kind of the same if you wish.

•User-aware display - or Attentive Display, or whatever you want to call it, the proximity-keep-screen-on thing. I have to say, IMO the Motorola one was just simply better. I'll quickly describe how both work in my experience and the up-/downsides of both.

The Lineage one just simply uses the IR sensors (not just the proximity one) to detect whether "something" is in the vaguely defined proximity of the screen. If it detects something, it keeps the screen on, if not, well not. The problem here is, it's not picky and very picky at the same time. For example, just putting it in a shelf or even next to / under a pot of flowers will keep the screen on and drain the battery, and you're not accustomed to paying attention to those situations, because you're not used to flowers keeping your screen on. I've even had it more than once sink into my pillow at just the right angle while snoozing the alarm in the morning and such killing the battery if I didn't charge overnight. Then again, sometimes while reading on the phone, apparently my face is too far away / not at the right angle so it turns off on me while I'm reading. It may occasionally detect my fingers but then it won't reset the screen off timer, but just postpone it, so as soon as the finger doesn't get detected anymore, it turns off.

The Moto one used the IR sensors to detect whether it was worth turning the camera on and then used that for face detection - plus when it did detect me, it would reset the screen off timer, so it would just have to detect me once every 30 seconds (or whatever the timer is set to) to keep it on. The upside is, it won't randomly trigger on pieces of furniture next to it. The downside of course, it doesn't work in the dark, and you can't just wave your hand over it, but have to angle it such that the front camera sees your face, also it has problems with sunglasses. Despite all of that it had worked simply better for me than the current one.

Now I don't know what or how to change it, you are way smarter than me for that, but I thought I'd tell you my experience.

•Ambient Display - the turn-screen-on-on-notifications-or-proximity. I quite liked the Moto one, but this one isn't bad either. But I have one problem with it, that it basically turns on the lockscreen (albeit in black and white) - fully functionally. While that would be a nice touch, the problem is when I carry the phone (- to hold it securely, I grab it with my full hand, putting my thumb on the display) it inevitable triggers Ambient Display, and it doesn't reject my thumb that was on the screen already before it turned on, so that might do all kinds of things on the screen while I'm holding it and walking. I probably have already blocked notifications for some apps already, at least that dialog is almost always open after I have carried the phone - or even just taken it out of my pocket. Once I even managed to make a little mess of my homescreen - apparently just my thumb managed to swipe up the lockscreen (I have no passcode) and then continued to wreak havoc on my widgets... On the Moto Display that wasn't really a problem, since you had to hit exactly the little circle in the middle of the display (which you could easily train yourself to put the thumb somewhere else) and even if you hit it, it would vibrate, alarming you, that you've triggered it. That being said, I do like the current setup (eg I can just wave and then immediately interact with the music notification, so wave -> tap for next song is really simple) but I wish it would be better at rejecting unintentional interaction.

•Wave to snooze alarm - This is the single most feature that makes me sometimes wish the stock ROM back. To clarify, on the Moto ROM, you could enable a gesture that waving your hand over the display would snooze a ringing alarm (similar to silencing calls now). Yes, it didn't work sometimes and yes it made sleeping in more prevalent by making snoozing easier, but gosh I loved it that you could tell the alarm just to buzz off like a fly. I can't imagine that it would be that hard to implement (since the call one is there already) and would love you so much if you did. I even considered digging through the source myself, but I just don't know Java enough for that. :(

Aaaaalrightie... that was a lot of complaints (and I probably forgot some), but please don't take it as criticism. I know you donate your time for us and really appreciate having this ROM. I just think I might as well give my thoughts for you to have feedback (I know I like feedback of any kind when I'm developing) - and I hope it was constructive feedback :)