ShadowEO
commented
8 years ago Frankenstein's Monster
If you're wondering what's up with the codename, it's because I pulled in more commits and had to do some Frankenstein-shit to get mpdecision to compile correctly.
Stage log
- 11:11 PM EDT - Compiling the first build of Frankenstein's Monster after fixing some missing constants in cpu.h for mpdecision, testing will begin if it builds correctly. Once I have determined it runs properly and still gives some noticeable battery improvements, I'll push the tree's current status and create a new image release.
- 11:32 PM EDT - Compilation failed due to a missing include and call in linux/cpu.h along with some other lines. Pulled some changes that bring it in line from the stock kernel, and compilation has begun again. This. This is the reason I'm calling this release Frankenstein's Monster.
- 11:43 PM EDT - Another fail, this time it was the items I had just pulled in and reverted. I found the cause I believe and removed the offending line in drivers/base/cpu.c since it isn't present in the Android kernels I'm pulling from.
- 2:12 AM EDT - It's still building. If you're wondering what's taking so long, I've got it compiling in an ARMHF chroot rather than dealing with the annoyance of cross-compiling.
I have pulled in new commits from another kernel with the commits all in a line. These commits replace the current implementation of DT2W and MPDecision.
Next tag codename: Frankenstein's monster. I had to do soooo many manual changes to get some of this to compile and I'm not even sure it all works.