Alright! Just got back home today and did a "check for updates" in App Brain and it detected an update for Droid Overclocker (to version 2.1.7). I made the update and now it works fine. So there must have been some glitch with some phones due to Gingerbread since the only thing it said was new with this version was that it was to work with Droid X Gingerbread better.
Out of curiosity... after you have your Droid Overclock set the way you used to have it, and assuming you then set up certain OC'g parameters On Boot, can you let us know if the settings stick, after a hard reboot?
I am running .596 deodexed now and see the following behavior:
Upon hard reboot, the Interactive/Conservative/Smartass governors intermittently become disabled. The clock speed/vsel always revert to the following:
Slot1: 300MHz, 33V
Slot2: 600MHz, 48V
Slot3: 800MHz, 58V
Slot4: 1000MHz, 62V
I have no profiles defined. This happens when I select predefined CPU Frequency Scaling (I usually select ULV 1.2GHz or 1.25GHz), as well as when I use a Custom Preset.
This also happened when I previously went from .595 deodexed to .596 deodexed. I then SBF'd, did the 2-part upgrade to .596 odexed, saw the same Droid OC behavior, then flashed the .596 deodexed file and still see the same behavior.
I've tried clearing Droid OC data, also tried uninstalling then reinstalling, but see the same results each time.
Side note: Sysctl settings seem to get cleared upon hard reboot as well, as seen in Terminal emulator w/ sysctl -a | grep vm
