[Q] XT1527 pure stock - excessive CPU? - E 2015 Q&A, Help & Troubleshooting

Just picked up an XT1527 (full package, box, accessories, everything) from a craigslist seller for $40 - I figured it would give me something to play with until Motorola ships my "free" Moto X (32GB 2013 model) as a replacement exchange for my old Atrix HD which bricked when I installed the last update for it. For the record, this is the Cricket model.
Upon playing around with it for the past few hours, however, I've noted it tends to run just a bit warm even when I'm not really doing much of anything so I started checking into it - I'm still pure stock, mind you, 5.0.2 build LXI22.50-13.4) and I'm thinking about rooting it and perhaps checking out the CM12.1 build but there's no hurry at the moment.
Having said all that, I grabbed CPU-Z and took a peek at the SoC specs: it shows an idle speed of 800 MHz for all four of the cores even in spite of them having a 200 to 1.2 GHz range. One would think that the device would ramp down to 200 MHz when idle and not doing much of anything at all but, that's not the case so far.
So I grabbed System Monitor Lite to check just in case CPU-Z was reading things incorrectly and got the same exact results. Upon checking the pie graph it clearly shows a range of 800 MHz to 1.2 GHz and nothing below it.
Has anyone else noted this issue with the Moto E 2015 model or... am I just so new with this thing (having owned oh, maybe 200 other devices in the past decade and doing some rather intensive customizations on 'em) that I'm missing something here and just not even noticing it?
Had hoped to keep this device relatively clean and stock but, it appears that's not practical if this CPU speed situation can't be resolved. I see there's basically only the one custom kernel available so far (Squid) and while I'm not opposed to using it once rooted/etc I'm still curious as to know why this thing isn't ramping down the clock as it should. It's using the default interactive governor as well, would be nice to be able to alter that but again that's where it gets more complicated.
Anyone else noted this on their XT1527 (or any of them, really, just as long as it's a 2015 model) or would someone else that's running pure stock be willing to check their CPU usage with CPU-Z or System Monitor or something else and see if it's not ramping down below 800 MHz as it actually should? Obviously the battery life would dramatically improve if this thing would slow down as it should - there could be some new Qualcomm trickery at work here that I'm not aware of, but if it's capable of dropping back to 200 MHz, it damned well better.
Any comments and suggestions are appreciated...
ps
Also I've noted the GPU doesn't ramp down to 200 MHz as it should either, it hovers at 310 MHz almost constantly which again is just another waste of battery when staring at a static image on the screen (save for the info updates themselves but that's not really a thing that should or would trigger a big spike in GPU speed).

---

o.o thank you so much. You'd wonder why. Well, yesterday (I think) I made a topic about how my phone drains battery abnormally and I just checked with the app you said (cpu-z) and it seems I have the same problem. My phone feels warm almost all the time and it also keeps working up to 800 MHz in all cores. Also, I own the same model and someone in the other topic told me that battery should last 2 or 3 days without doing something. Oh anyway, thanks because now I have a hint about what's going on. Maybe its a manufacturer problem.

---

For some reason, Motorola set the CPU idle speed to 800 MHz. I don't know why. I lowered the idle speed to 400 MHz on my phone, and I'm not noticing any performance degradation. I haven't noticed any heat or battery issues though. My phone stays fairly cool, even under heavy load (like running benchmarks repeatedly). I've undervolted my phone slightly, that may reduce heat a bit, though I don't recall having any heat issues without the undervolt either.

---

Well squid, I'm guessing you are using a pretty customized setup at the moment including the kernel you've created so, I'll most likely end up getting a similar situation I suppose. Since the Snapdragon 410 can do 200 MHz to 1.2 GHz it damned well better do it; if Motorola for some reason chose to "hard lock" it at an 800 MHz idle speed that's a bit ridiculous and will only serve to hamper battery life overall.
Performance isn't the issue here since as soon as some CPU power is required it'll ramp up as expected - the issue here is the 800 MHz "bottom" which should actually be 200 MHz. That's a big difference in terms of overall battery life in the long run.
I owned an LG Tribute in late 2014 and was regularly getting 8+ hours of SOT with that which is powered by a Snapdragon 400 (1.2 GHz quad core) and that has a 2100 mAh hour battery - the Snapdragon 410 in this Moto E should be better for battery efficiency + we've got a 2390 mAh in it so, as long as it's ramping down to the 200 MHz "bottom" that it actually should be hitting then I, for all intents and purposes, should be able to expect or even exceed that 8+ hours of SOT without issues. The Tribute has an 800x480 panel in it, the E has the 960x540 so in the long run that increase in pixels should be covered by the increase in battery amperage (290 mAh more).
This Moto E 2nd gen model should be able to do 7 hours of SOT without breaking a sweat, even with cellular/Wi-Fi/Bluetooth/location services on and functional.
At least that's my goal with it... I'm on my first full charge since I bought it earlier today and currently at 58% with 3.5 hours of SOT and that's using Wi-Fi a lot with video playback as well. I've been keeping on top of the Baltimore riots that are happening presently and monitoring things using Scanner Radio Pro as well as a lot of surfing for info and news too. So far so good on the battery life, but obviously it can be much better as long as that CPU speed can be brought under better control.