[Moto E Original Android Development] Mu009:
Sure thing!

Of course mate.

But before that, here's a disclaimer:

By faster than today's mid-rangers - I do mean that, but not all of them. And of course, the much lower RAM also comes into play. But let me take a moment to define it. It's perceptibly slower than the stock Android Mi A1. But only perceptibly - not substantially. Being used to a OP3T otherwise, for example, google assistant takes over the mic without lag on the OP. But wait times between firing up assistant and assistant being ready to record with the mic are almost identical with the A1 on this Moto E. It is faster however, than skinned devices which use the SD625 - like a RedMi Note 4 or Lenovo P2 (that's why I fobbed off my Mi4i pretty quick - I hated the laggy MiUI after the honeymoon phase, and though I got a lot of smoothness out of custom ROMs and kernels on it, since nothing was official, the lack of stability got to me). Back to the Moto E, Though of course, this can barely keep any app in memory in comparison to newer devices - the apps go out of memory even if you open a couple of chrome tabs, say.

And bear in mind that this phone not only has all 3 animations scales set to zero, but is being run very lean. I've uninstalled just about everything I don't use. Lineage browser, launcher, email, fm radio, the pesky cell broadcast receiver, live wallpapers, photo table, yada yada yada... All gone.

I'm running Nova Launcher, pico GApps and the only real bloat is a 60mb icon pack. There's nothing on the storage save a few photos. And I still don't have enough space to be able to use the excellent LineageOS Downloader app for updates (like the old CyanDelta for CM).

Otherwise, I'm rooted with SuperSU 2.82 SR5 and have ES File Explorer, Google Maps, GMail and Smart Office installed.

The phone is a spare phone and used for calls, messages, email, navigation and generally for stuff that

1. Doesn't drain my primary phone's battery unnecessarily (like navigation) and/or

2. Leverages the dual front facing speakers (like a White Noise generator or Metronome) and/or

3. Intensive screen-on activity with a static screen which I would want to avoid on AMOLED (such as using a metronome app)

I still have the original battery - a paltry sub-2k mah unit that is now 3.5 years old but with this kind of usage still shows admirable battery performance. I get a minimum of 2 days (when I'm not using my metronome, which isn't often, which entails hours and hours of SoT).

So either way, your mileage may vary.

And without further ado, for what it's worth, here's what I've done with Kernel Adiutor (it's fairly standard, and I really don't know where I get off advising anyone on this - I've just read a few posts on how to select this stuff and tinkered around with it x years ago and settled on something I found worked for me - so don't expect anything much really):

1. CPU - Performance Governor, maximum possible maximum frequency and minimum possible minimum frequency. Multicore power saving disabled.

2. CPU Hotplug - MPDecision Enabled.

3. GPU - Same as CPU

4. I/O - Deadline Scheduler, 128kB read-ahead value (given the 2gB ROM), I/O stats and Add Random Enabled, RQ Affinity 1.

*All settings are applied on boot with no delay.

And that's about it, really.

Cheers!