[ONE Original Android Development] Natakranta:
I've been using March 12th (clean flash) and 14th (dirty over previous one) builds since they been released as a secondary ROM in MultiROM.

Stock karnel with stock settings as I believe Robbie knows better what he is setting in karnel defaults than I do :)

Observations

Flawless, smooth, fast work. No FCs. No random reboots. And surprisingly despite Google going recently totally bananas with Play Services, I have had no issues with deep sleep many people were reporting. No wake locks apart of normal dozen of minutes a day generated by gmail and FB Messenger constant syncing.

Not seeing anything suspicious going on I was surprised with quick battery drain on day 1 after flash (heading to over 4h SOT only). But you know what they say, don't judge the ROM / karnel after one day. Day two it got better, day 3 statistics started to look normal (over 6h SOT heading towards over 7h SOT, I didn't have enough spare time to actually drain it down to 5%).

So now I have standard Lollipop battery drain for my pattern of usage being about 45-50 minutes SOT per 10% battery juice.

On SlimKat I was getting 60-70 minutes SOT per 10% battery juice. (These are not precise scientific calculations!)

Bluetooth. Bought new car recently. It has JVC KD-R801 radio which is BT capable when you put a BT dongle into it. So I bought one.

Chip one :D

And it works. It works flawlessly! No stutters. No strange noises. Loud and clear :)

People were reporting BT volume going sky high after receiving a notification. I haven't observed anything like this. Maybe because my volumes are set to max and I adjust it on radio volume knob. Anyway, I was anxious about using BT after I've seen two thousands BT related posts on last four months. Instead BT works fine for me, at least with my car radio setup, I don't have any other to check.

The only bug I notice (both Slim LP and SlimSaber LP) recently is when Tasker is using Secure Settings to disable pattern lock on lock screen after activating "home" or "work" profiles (WiFi SSID based) with screen of, I turn on the screen, pattern appears, OK, unlock it once before lock disabling takes effect, screen freezes until it deems and switches off itself or I switch it off with power button. After switching the screen back on, swipe up on the lockscreen works normal - pattern lock is disabled as long as phone is connected to home or work WiFi network.

Now I should put a logcat which I'm ashamed not to have [emoji16] but I'll get if necessary.

You may probably be thinking why the hell he is not using Trusted Places. Well the thing is they require location to be turned on constantly and I don't like it. I don't like when an app keeps on demanding precise GPS location when I'm mostly indoors where it's not possible to lock GPS, what results in GPS being kept on active for minutes or hours (of you don't notice it) and draining battery in search of satellites it just can't see through few levels of concrete floors and roofs.

You would say why not use Batter Saving location mode, GPS would be of and phone will still have location services. From my experience it's asking for Google Play Services wake locks - they were often coming up when I was using battery saving location mode in the past. Moreover I just don't like having location on when I don't use it. I turn it on when I need navigation. That's it.

At least in car I can use now Trusted Devices: car BT. I wish it was possible to set WiFi SSID as trusted device. Why Google? Why you haven't thought about it?

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.