Though I admire your ambition to contribute something, and I am not forbidding you to use your script, I would like to voice my opinion to that ^^
What you described is EXACTLY what mpdecision does. More sophisticated. Mpdecision checks from userspace if the second core is needed and activates it if it is. If not it stays deactivated and saves power. This is good. We want it to do that since we are usually not near an immured pig (outlet ). Our cpu hotplugs really fast and I think we should use that to our advantage rather than forcing the cpu1 online. but then again, my opinion
i create this script to avoid the slowless response of mpdecision.. i see it when something uses the second core, as like, i'm using chrome, if i have core1 able, animation of tables is smooth, if i have core1 disable, i see low framerate..
the advantages of qualcomm is the asyncronic structure, if you turn on core1, it will come to low power consuption until something uses it.. sure.. if you use this condiction with a governor like ondemand, it eat the battery in 10 minutes, it happen because governor put all of 2 cores at maxfreq even cpu usage is about 50%.. so.. 50% of "power" frequency, looses, for nothing
now with this badass it could be possible to put a low maxfreq, and, i see it's a good condiction
i create this script only for users witch want to try to use natively multicore without mpdecision lags
on sense4 rom, with stock badass governor, all UI is so slow, with ondemand at 1.56ghz was accettable.. now it's smooter and smooter
sure, than you for your great job.. if you don't want to see my script in you thread, teach me, i'll delete it