[ONE Original Android Development] magnamentis:
some settings revert back boot

hi,

i hope that i'll get the wording right, otherwise i beg your pardon upfront, these are just observations and my personal opinion about it, i'm ready to learn about reasons and/or to stand corrected ;) after several days of using beta 9 on cm11 (always lates nightly ) i observed the following:

a) charging current settings don't stick, back to 0 each time, this might be intentional and is not important, just a bit unusual compared to other settings but i understood it would be only the 1st time

b) read-ahead buffer size doesn't stick upon reboots. this may as well be intentional but i don't see the benefit IMO not the best choice if intentional & i understood that it would be only the 1st time

what are the downsides?

that's obvious, i have to open the app and delete the profile and re-import the profile and acitvate it, or i have to open the app and change the above mentionend settings back to my choice. while the second way is a bit shorter the first way guarantees that all my previous settings are re-applied. why is the later important, it's because otherwise i have to check all the settings each tim to be certain because i never know what other settings eventually are not sticking anymore. so the time i need to check all settings, partly having to scroll down to to that, makes the set on boot feature almost obsolete. to avoid that even lengthier procedure, i better choose procedure one.

whatever the reasons to make these two settings not stick might be, IMO they are not worth the extra effort and the lack of trust what sticks and what not. if it would be only charging amperage it would somehow be an acceptable exception albeit i think we know that we can set that to 10A and nothing will kill the battery as long we don't raise the voltage to FORCE-PUSH that extra power into the battery which probably is prevented anyways.

however i think if that danger would really exist, that the feature as a whole should be removed ( but the risk does not exist ) and the moment i have to tweak the kernel upon each reboot which under certain circumstances can be quite several times per hour (troubleshooting, playing with different setups etc.), setting a profiles as well as the set on boot feature are only worth 10% of what they were before. the 10% would be the small amount of time to slide a slider instead of just looking it up, which i have to do anyways now, because i cannot trust the app anymore as to which settings do stick from version to version and which don't. i will make further test to get a better picture, that is how it looks for me at the moment

EDIT1: it looks like after a simple reboot ( no rom update ) switching to default profile and back to my profile does the job while it seems not working like that after flashing a new nightly

EDIT2: this starts to be weird, when i do a softreboot the above settings stick but row is set instead of noop, again if i switch to default and back to the profile which was active on boot the settings come back. so it's certain that the correct profile was set on boot, the settings were correct before boot and still the scheduler does not stick while like above mentioned, upon full boot it's the charge amperage and the read-ahead. i can reproduce that, means i can make a full boot and it's the way i described and i can perform a softboot and the scheduler changes to row.

i will send you the debug file via email as it is requested in the app, perhaps it helps, if not and if you will have mood and time, just let me know what else i can do or which other logs you would like to see, for now i will email you that debug file

don't put too much into this is not a real problem, i'm just reporting what i see and after several days of use and seeing the same i thought that at least it's not totally intermittent and thus worth to report to keep an eye on it.