Hi randomblame, I can't comment on your KB7x30 kernel fork, so here is a comment intended for the initial boostpulse commit so you don't jump the gun and use a powerHAL with it in a release. Also should note that you must remove the download to your 5.1 release to stay within GPL and XDA regulations due to kernel source no longer being available for the kernel in use in it (I don't blame you for deleting it after changing a comment of mine to "I'm a tool" though). Here's that comment meant for the commit: Hi, just letting you know this alone without the commits following breaks load based scaling and will only scale to min or max with the Andromadus ported powerHAL in use. Same in their ondemand boostpulse setup which is why Super reverted to the old kernel due to poor battery life. Nice to see devs being given credit for their work now for a change
. Also should note the kb-wip branch stands for a work in progress branch. Hope this helps you.
PS: It should be noted I was never upset about my work being kanged (which it wasn't), but full repos being taken (from devs who have given us JellyBean in it's current form), without any form of git history making them look like original content. Credit and teamwork is what this community's about.
PPS: The 5.1 link is on google code
PPPS: The device repo I forked was a combination device/vendor repo that would not build when you were still zipping blobs into the roms to get them to boot. Not at ALL to CM standards. I ended up realizing that AFTER I forked and completely redid it from scratch based on my booting jellybean HTC Holiday device repo (just compare the device repos, as well as the proprietary Ace and Qcom
[10:00:06pm] <@synergye> vendor repos (which random doesn't use)).
--Synergy
Empfohlener redaktioneller Inhalt
Mit Deiner Zustimmung wird hier ein externer Inhalt geladen.
Mit Klick auf den oben stehenden Button erklärst Du Dich damit einverstanden, dass Dir externe Inhalte angezeigt werden dürfen. Dabei können personenbezogene Daten an Drittanbieter übermittelt werden. Mehr Infos dazu findest Du in unserer Datenschutzerklärung.