[Nexus 4 Original Android Development] Hanny:
As I have read, many of you have experienced "My past stable UV values are not stable on r80" problem

Personally, I am not an UV lover, I don't pretty much care about extended battery life (if any), but as you all know I am an intense gamer and I UV the phone for lower temperatures (it does definitely work in this aspect)

You may not care about my phone's UV capabilities, and I don't as well, cause I am all fine with the temp stock (franco's) voltages give + the thermal throttle threshold (58) I set, but we are all here to discuss to make everything as good as possible, right?

For me, I assume that I have already reached my minimum UV on r61, and I now do believe some changes in the CPU hotplugging behaviors does affect our stable UV voltages.

Why? Because based on the statistics I have collected on Bootlog Uptime, I was already experiencing "My past stable UV values are not stable on this newer version" since r67.

When r61 was released, it came with the possibility to undervolt. I UVed -150 across my board and -100 (totally -175 in addition to franco's default -75 since r52) and did scaling stability test on the stability test app. I have tried to make it as accurate as possible according to some reference threads on some other devices about undervolting. I unplugged my phone and ran the tests on all % of battery level from 100 to 0 (some reported stable voltages on high battery level are unstable on low battery). It was totally stable.

On 7 Feb, I flashed r69 (68 and 69 were only color changes, and the change about CPU from r61 is actually on r67) r67 has introduced the testing version of new hotplugging routines. I had 2 random reboots that night, not so frequent.

On 10 Feb I flashed r70, it has the final 1.0 version of CPU hotplugging. I even did gaming test for franco and there were completely no reboots. However the next day my nightmare began. (same as on r71 and 72 as they were just color changes) There were at least 18 random reboots in these days until today afternoon I started to increase my voltages as they were the last step solution for me. I never believed the "past stable voltages" would be unstable, as well as the kmsg log did not show last boot reason = kernel panic. Instead it just shows last boot reason = reboot. That's why I didn't believe it and I removed all apps on my phone tagged with "beta", still random reboot and I started fresh from everything stock to fastboot flash TWRP, wipe /data partition and do everything again. It was still there then I increased the voltages to just -75 across the board. (still on r72) (stay on franco stock 950 for 1026) (with a fast chip) that is half of my stable voltages before!

[for r80 just flashed it guess i will stay on -75 and continue observing]

I am not saying I have discovered magic but should there be a reason for this? I am earlier than you guys to experience similar stuffs for a few days thats why I am quite serious about it. From my wild memory on franco's git the hotplugging changes on r80 were

auto_hotplug: use the same timer for all works. Also make sure cpu0 and cpu1 are the ones online, not cpu0 and cpu3.

auto_hotplug: change the INIT_WORK call to the new name.

I'm not a code reader, there may be more stuffs from 4.2.2 changes that have increased the cpu voltage hunger on r80, but as what I have experienced in pre-r80 releases, the changes in hotplugging behaviours have affected the hunger on my phone.

Thanks for reading such a long post and sorry for any stupidity! Any inputs?

--------------------------------------------------------------------------------------------------------------------------------------------------------------

By the way PLEASE allow me to ask an OT question here as here has so many experts:

this has been in my mind since the galaxy nexus time. in the past (android 2.3) i fix permissions in terminal emulator with su then fix_permissions but it isnt there anymore on ics and now, i didnt know why. so I use the one in recovery.

but however, everytime after i fix permissions in recovery, all my boot-apps that require root (franco updater, touch control, LMT, as much as you can name) delays (2-3minutes) to gain superuser permissions or even did not gain it at all. same with both superuser app and supersu. Sometimes, one or two reboots fixed it and it goes back to the proper timing of getting permissions ~20 seconds after boot.

Yesterday fix permissions were also one of my attempts for the random reboots and the delays never got fixed even after like 10 manual reboots. Until I had to use the "reinstall" option in supersu then things were back to normal again.

Please forgive my poor skills in searching, because I have done it and got no other people reported similar things. Could anyone tell me why is this happening and how to get rid of the delay? fix permissions is really useful when it comes to intolerable app-FCs. Thank you very much in advance.

---------- Post added at 02:46 AM ---------- Previous post was at 02:46 AM ----------

i guess thats me... well my /data partition did not get totally "borked", but just the "LOST+FOUND" folder not accessible by anything, showing error in recovery after every type of wipe or install. thats probably some ****s appearing randomly while i **** my phone up. actually that doesnt affect directly to anything related to my system but in order to prevent future ****s i just backup my sdcard and flash 4.2.1 stock userdata partition on my phone again then restore. everything worked fine afterwards

actually, after reading some pages before your post, if i were you, i would already have unchecked apply voltages box (even when stable before r80) and then go flash r80 as what i have just done :)

One thing to note about the first boot after flashing r80:

I did not have only-once instant reboot

but my screen's color was completely washed out (I was staying on default gamma values all the time + a bit RGB tweaking only), like something is completely wrong with gamma

I opened franco updater and pressed the reset to default, reboot, and colors were back to normal

guess thats not a high priority / high demand feature here so lets not create more hassle for franco :P

make two profiles on Voltage Control Extreme, one stable and one experimental, set stable profile on boot and manually apply experimental as you like - there you go