Actually it looks like it may have been another app interfering. No worries on that.
But just noticed an interesting things re voltage control. Not sure if voltage control sticks? Seems to go back to defaults after boot... Also may be interesting to note, I had undervolted before installing kcontrol. Now when I hit the reset button it resets to my undervolted values. Works for me since I like the profile. Either way some time in the future, having the option to save voltage profiles may help ppl. Should I still pull the info above for this issue too?
Sent from my HTC One S using Tapatalk 4
For voltage sticking you need to have it ticked under settings, which is separate from the frequency toggle to protect people from applying 'testing' voltages on boot accidentally. (which could be unstable)
For applying voltages another file is responsible:
Code:
adb shell
su
cat /data/data/de.bricked.kcontrol/files/saved_cpuvdd
This file won't exist if you have reset to defaults. In light of your recent post that you launched KControl with non-stock settings and it remembered them as the reset voltages, the issue is this:
When you launch a section of KControl for the first time it saves everything it is reading in that section into a file: def_name.
If you click reset within that section KControl will reset everything to those saved values and reset the shared_prefs used to apply on boot to -1, the boothandler will then ignore that. (Voltages are an exception: It saves your modified frequencies to the above mentioned file saved_cpuvdd because it makes more sense for this number of shared_prefs, keeping in mind that those values could change every kernel flash. Resetting will delete that above file.)
The boothandler will not restore settings that have been 'reset' to their saved values, because we operate under the assumption that the settings KControl reads on first launch are actually the ones from the kernel and we don't want to mess with them if the user selected "reset".
For you this happens now:
If you reset the frequencies, your previously modified settings are restored immediately, because KControl has read them on first launch. It will ALSO DELETE the saved_cpuvdd file because you wanted to go back to stock.
The boothandler will launch on boot, check if you want to restore vdd and if the file saved_cpuvdd exists, which, in your case, is not the case. It therefore will just skip this section.
To fix this behavior with what you currently have (this is not an app bug): just hit apply once in the cpuvdd screen when you have reset to defaults. (the file saved_cpuvdd will be created and the boothandler will find it)
To have the intended function of KControl: reset it's data, prevent any app from setting anything and reboot. (The quickest way to get clean stock kernel settings back is still a reboot) When you now launch KControl it will save the actual stock frequencies and everything will work as intended.
