yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] ptesmoke:
NP added everyone who has requested.

Derp...had to go to the actual website and share as public. Good to go.
[Nexus 4 Original Android Development] mgear356:
If I got zero issues, should I remain on b12 or upgrade to b14 for battery nf performance?
[Nexus 4 Original Android Development] mobilehavoc:
I have B14 downloaded but B12 is running so perfectly right now I can't bring myself to flash 14. Will flash it later on....great work as always..is B14 not as smooth because of the inert PowerHAL?
[Nexus 4 Original Android Development] consolidate42:
Are these your lowest stable for each clock? Or is this a constant across-the-board UV?

B14 has the option to enable/disable input_boost. It should be as smooth as b12 with it enabled.
[Nexus 4 Original Android Development] eikaramba:
just wanted to say that b12 is running fine here on faster binned. I think i will stay on B12 and watch whether there are reboots or not, in the case there are, i know what to do :P
[Nexus 4 Original Android Development] ptesmoke:
On 14...several reboots...looking into it.

Dunno if it helps. Kernel panic - not syncing.

Will post kmsg once I'm back at PC.

Side note...if anyone's using my UV table as a rough guide, I'd love if anyone who wants to pm me your voltages and I'll compile a list. Also include your binning...and I'll organise them :)

I'd like to keep it specific to Motleys experimental and if I get enough data I'll make a thread later on.
[Nexus 4 Original Android Development] popophobia:
I got a few reboots. I don't know if it's my UV. But I used it the whole day yesterday without a problem

here are the last_kmsg. They say HW reset. But the phone rebooted itself. In one instance it froze and vibrated non stop.

https://dl.dropbox.com/u/10917179/last_kmsg_b14_2212.txt

https://dl.dropbox.com/u/10917179/last_kmsg_b14_2215.txt

https://dl.dropbox.com/u/10917179/last_kmsg_b14.txt

I'll ease on the UV to see if that happens again. I have to do a manual e2fsck to repair the filesystem from these reboots.
[Nexus 4 Original Android Development] ptesmoke:
Looks like WiFi to me...but I'm no expert by any stretch. I also eased off a bit on my UV. Seems stable now...but obviously it doesn't like UV as much as previous.
[Nexus 4 Original Android Development] greg17477:
nah, its not necessarily true ;) by using target_loads, your cpu should use a wider range of frequencies.

Now, going to test b14, thx motley :)
[Nexus 4 Original Android Development] Wanya79:
with which App i can asset those settings? I have got Trickster Mod and System Tuner installed, but didn't find all settings under Trickster Mod
[Nexus 4 Original Android Development] batman368:
trickster mod -> general -> interactive governor control (grey button right under CPU governor control)
[Nexus 4 Original Android Development] Remoteconcern:
This is a great thread guys. Everyone seems to help each other nicely, and it's refreshing that it's quite quiet. Thanks motley and everyone!
[Nexus 4 Original Android Development] antih3ro:
First of all nice work! I'm on b12 and battery is amazing and still everything is smooth and no reboots so far. Thanks :good:

Can anyone with an nominal chip share his/her UV settings. It seems like the most of you have a fast or faster binned chip ;)
[Nexus 4 Original Android Development] Domx92:
am i going crazy ? if i lay down my phone the touchscreen doesn't notice my touches on the system buttons (home, back, recent) and the statusbar.. but when i hold the phone in my hand all is working perfect o.O

is it just me?

Stock rom + b14
[Nexus 4 Original Android Development] Remoteconcern:
It's just you. Or at least, it's not me.
[Nexus 4 Original Android Development] mko000:
It's fine here.

Is this while you're charging the phone?
[Nexus 4 Original Android Development] ethoss:
On b14 I have some lag on lockscreen and 2 signal drop, reverted to b12 for now :)

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] keda:
b12 is working just fine here as well. No reboots after 2 days. No extra uv, stock setting and stock Rom.
[Nexus 4 Original Android Development] _motley:
Guys, I think we have a working theory going here. Thanks ptesmoke for posting all your settings and giving feedback. Now that we are adding the boostpulse feature (and also some load tuning likely also playing a role), the mid-range frequencies are now being used more often. I believe it is exposing weakness in some people's voltage tables. When I looked at your table, my first thought was "Wow, I can't believe how low they are and that it even works at all!" Now that we spend more time at these frequencies, they need to be scaled properly and have enough juice. Before, they were mostly ignored. This can explain why some that opted for the "inert" PowerHAL b12 fixed their problem. This can also explain why many of us have no problems at all since we haven't UV'ed to the extreme.

I have a nominal chip, here is my setup. These are UV'ed a bit further from my default UV settings.

https://docs.google.com/spreadsheet/ccc?key=0AhMvXgjEztvAdEk0V0JjeWVRSEVSNllhZmRmNmhjWWc

For those having issues, please check this out and let me know if it makes sense for you if you are having problems. Go back to the default UV settings and see if you have any problems. Then scale back down carefully if you want.

That is up to you. Both should be very similar. If you can test them both and give your feedback, that would be great. I'll be testing b14 longer today to see how it performs.
[Nexus 4 Original Android Development] ethoss:
Testing b14 with stock voltages and Fsync on. I don't changed enything :)

Keep update!

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] batman368:
i have a fast cpu, 1.5ghz@1V, 300mhz@675mV, linear scaling in between. this runs absolutely perfect with all motley version (b10,b12,b14) never had a reboot, also never had any performance issues, buttery smooth the whole time. i didn't think it's possible, but b12 and b14 are even smoother than b10.

maybe everybody experiencing reboots should test with stock voltage, just as ethoss also mentioned. that way the issue should be easier to find.

@ motley: any chance we might have something like input boost for N7 kernel as well? right now N4 feels just smoother :)
[Nexus 4 Original Android Development] elkhouri:
Just to chime in here, when I had a reboot earlier with b12 without flashing the inert powerHAL, the kernel was at all stock settings with no voltages changed and whatnot. I've a fast binned chip.

Testing b14 today and will report back later with findings. So far, seems like there are much less hsic wakelocks when I left it idle overnight..?
[Nexus 4 Original Android Development] ptesmoke:
Thanks so much for your input motley! I started questioning my 1026mhz voltage. Bumped all of mine up 12.5 mv and haven't seen a reboot yet. Will continue testing today and update my table for anyone interested. Again I encourage anyone with a proper tested voltage table to pm me your settings/binning and I will add them all to the table as a reference. Motley I will add yours when I get home today :)

Gotta school myself in understanding kmsg :)
[Nexus 4 Original Android Development] Hausschuh:
Thanks for the kernel!

But I'm little bit confused, I flashed the b14 kernel because I had terrible battery life, and now? You are speaking about undervolting and so on and I have no idea, never did it. I tried to read the faq and some posts but I'm still confused. I just want the best battery life out of my phone, so is there a tutorial or could someone help me? Would be great!
[Nexus 4 Original Android Development] Remoteconcern:
I'm a fast bin, my phone is stable at 600mV up to the 1100mHz step. Used it all day today and overnight, and no stability problems at all. However, I noticed massive battery drain and I wonder if it's due to that. Going to raise them a bit and see what happens.
[Nexus 4 Original Android Development] rlaw:
So maybe those who had reboots on b12 should test it again with a greater incremented voltage table.

Here's my table for reference. Fast binned chipset.

I've read elsewhere that the power requirement for 1026MHz is a much steeper step than previous frequencies, so it very well could be the mid-level voltages.
[Nexus 4 Original Android Development] rlaw:
Oh and I highly recommend this app to check your system stability while tweaking your voltage table.

https://play.google.com/store/apps/details?id=com.into.stability
[Nexus 4 Original Android Development] popophobia:
It's normal. That's how capacitive touchscreen works. You can look around. Basically when you touch the phone it is grounded properly to detect your finger touches. If it lays flat, I think it's grounded and can't tell the touches. Try to put it on the mattress, touchscreen should work even if you don't touch the phone.
[Nexus 4 Original Android Development] jazzboyrules:
Thanks for what you are doing. You can convert your spreadsheet to have form based entry (a tutorial video over here if you don't know what that is or how to do it: http://www.youtube.com/watch?v=E5CfuRTy1V4 ). Once you set up the form, you can keep the spreadsheet edits to yourself and still allow people to add their configs.

PS: I used a form based spreadsheet to gather Nexus 4 shipping stats of 1k+ redditors [ link ]
[Nexus 4 Original Android Development] Wanya79:
Just one quick question, in the Past i bought Franco's Kernel Updater App, can i use the App to adjust motley Kernel settings? such as uv and governor control and so on? or is it not possible aka recommended?
[Nexus 4 Original Android Development] ceejay83:
use system tuner or trickster mod
[Nexus 4 Original Android Development] Domx92:
i didn´t know that :b thanks:b but scrolling and so on was working well ... only at the navigation bar and statusbar

i wasn´t able to touch anything!
[Nexus 4 Original Android Development] ethoss:
I can confirm lag in lockscreen, when it wake up after deep sleep I think... No reboots at the moment.

On b12 I have no lag at all. :)

CM10.1

STOCK VOLTAGES

FSYNC ON

INTERACTIVE GOVERNOR

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] lazer155:
Do you have the default undervolting scaled to the different binned CPUs? So for example the nominal have slightly higher voltage tables than the fast CPUs by default in your kernel?

---------- Post added at 11:05 AM ---------- Previous post was at 11:02 AM ----------

What kind of linear scaling? What value of voltage increase between each frequency? I have a fast binned cpu too and am trying to figure out what the best linear increase is.
[Nexus 4 Original Android Development] mobilehavoc:
Got a reboot on b12 so I've now flashed b14 and will post if I see issues. I'm not rooted so I always run kernels with stock settings.
[Nexus 4 Original Android Development] batman368:
to be honest all i do is stock settings for fast cpu and hit -12.5mV 4 times in system tuner, that gets me too 1V for 1,5ghz and 675mV for 304mhz. 486mhz is at 825mV, from there on it's linear.

i always wanted to test each frequency properly with stability test, however i was too lazy so far, and what i have works just fine, lighting fast and 0.1%/hour at night, with sync&wifi on :)
[Nexus 4 Original Android Development] lazer155:
You haven't had any problems with poorer battery life like this previous poster have you?

Does excessive undervolting result in more battery drain as the cpu tries to compensate?

I'll definitely give your settings a try. With the stock b10 settings, I've gotten over 7 hours of screen on time while reading a book with data, wifi and syncing on. Undervolting will hopefully improve that even more.

Which beta are you currently using? Have you noticed a difference between b12 and b14? I'm currently on b10 and trying to decide which 12/14 to try.
[Nexus 4 Original Android Development] vineet381:
dumb ques- can i flash experimental builds through CWM. Reason I ask is I tried flashing b12 yesterday and was stuck on Google logo after that. Just wondering if I missed something. I dirty flashed my ROM, gapps and then flashed the kernel, fixed permissions and got stuck.
[Nexus 4 Original Android Development] ctfrommn:
Should be able to. I would try a fresh download of the kernel and flash again.
[Nexus 4 Original Android Development] ptesmoke:
I'm faster binned..not far off your voltages actually. Maybe 25mv less. Like you said 1026 is a touchy level, I can run it at 600 but I'll get odd glitches. I think I'm at 775mv on it right now and its been flawless so far today. Also its not good to go from say 600mv at 800mhz then jump to 775 at 1026. It needs a linear increase on voltage or you'll run into issues. I start at 600mv at 304mhz and increase all the way up to 975mv at 1.5ghz.
[Nexus 4 Original Android Development] lazer155:
Here's the table I compiled based on the undervolt levels people have recently provided: https://docs.google.com/spreadsheet/ccc?key=0AnlqtEwFJwR6dE55WkZYSThEM3U4SGtKMVl2V1VqMmc

Feel free to put your settings in if you want, just try to keep the format the same so it is organized.

I have a fast binned cpu so I filled those default voltage settings in but I don't know the nominal or faster settings since I don't have either of those cpu bins. So it would be great if someone with either of those bins could fill in the stock spot in the speadsheet.
[Nexus 4 Original Android Development] Hrithan2020:
Can you tell me why non-linear increase on voltage will lead to issues? Any particular source or just common sense?

Also, considering that in one of the links posted in this thread, where extreme UV actually led to higher power draw from cpu possibly bcoz of more error correction requd in words of OP of that thread [not accounting for the restarts which may occur because of instability], I think it'd be interesting if someone is able to measure the actual power consumption of our CPU when UV'ing and extreme UVing [say -200 or -250 mv or more].
[Nexus 4 Original Android Development] ctfrommn:
Am I alone in thinking exp10 is still the best? I feels noticeably smoother than exp14. I didnt try 12 but 10 is so nice.

And if so, what changed?
[Nexus 4 Original Android Development] greg17477:
you did everything right, but forgot to clear dalvik cache ;)
[Nexus 4 Original Android Development] ctfrommn:
No need to wipe anything when flashing a kernel.
[Nexus 4 Original Android Development] batman368:
awesome idea this spreadsheet, i added some info about power usage, cause that was asked in this thread. i have really awesome power usage. i would also advice people with high drain issues to check if this high drain is related to something else (BBS, etc)

also a question to the other UV guys: did you test every frequency/voltage combination with stability test?
[Nexus 4 Original Android Development] renna1992:
If you're coming from francos kernel you should reflash your ROM or the reset kernel that is to be found in fauxs thread. Its a known "issue" :)
[Nexus 4 Original Android Development] lazer155:
Great idea with those additions. :good:

Can battery drain be caused by excessive undervolting?
[Nexus 4 Original Android Development] ctfrommn:
He said he dirty flashed his Rom 1st.
[Nexus 4 Original Android Development] batman368:
to my knowledge and experience UVing only leads to massive instabilities once the critical voltage is reached.

BBS is better battery stats, imho the best source to find out what eats away your battery
[Nexus 4 Original Android Development] air2k57:
Just installed b14, was on matrix for last couple of days. I don't know why, but my data works so much better on this kernel. I usually get data timeouts left and right on pretty much all kernels, even stock while at my house.

Is there a way you may consider adding that same color patch revert that matrix has? I really like this kernel, but the colors without the Google patch look amazing IMO.
[Nexus 4 Original Android Development] ctfrommn:
Agree....Franco and Trinity are also using the reverted colors. The whites are amazing on those kernels.
[Nexus 4 Original Android Development] air2k57:
Yea, everything looks too red to me now. Lol by no means is a fault of this kernel, I truly think this is the best all around kernel, but would be nice to have that same revert :).
[Nexus 4 Original Android Development] tooeasyforkevin:
Hm...even with aggressive undervolting I'm still only on pace for ~4 hours screen on time. I'm at 80% right now with 50 minutes screen on time.
[Nexus 4 Original Android Development] jazzboyrules:
+1 to that.
[Nexus 4 Original Android Development] dwang:
if your on 3g that's pretty good.

I usually get 4+ hours with 3g and 5+ hours with wifi.

With no gaming that is. Once u start gaming, better be close to a charger. :)
[Nexus 4 Original Android Development] consolidate42:
I usually get 7-8 hours on WiFi browsing w/ some light gaming. 5-6 hours on 3g
[Nexus 4 Original Android Development] ctfrommn:
Rom? Settings?
[Nexus 4 Original Android Development] tooeasyforkevin:
Just wifi :(
[Nexus 4 Original Android Development] samwebbo1990:
+1
[Nexus 4 Original Android Development] consolidate42:
Paranoid Android.

Autobrightness, gps on, sync on, a bunch of app receivers disabled. You can find my voltage entry in the community table a few pages back.

Those screenshots were taken back on b10

Min clock = 304mhz

Maxclock = 1512mhz

governor settings were b10 defaults save for go_highspeed_load maybe

above_highspeed_delay 20000 (haven't really notice a difference tweaking this)

boost off

go_highspeed_load 80 (80 might have been default)

input_boost off (b10 had no input boost)

min_sample_time 40000 (haven't really notice a difference tweaking this)

timer_rate 20000 (haven't really notice a difference tweaking this)

My battery current(mA) readings on b14 /w input_boost off are at least as good as they were on b10.
[Nexus 4 Original Android Development] lazer155:
Are you seeing any issues by having your voltage scale flat linear for a good portion of you frequencies? I saw that motley mentioned awhile back that he thought the increasing linear scale was important for stability and use of all the frequencies.
[Nexus 4 Original Android Development] consolidate42:
I've run the scaling stability test for around 15 minutes with no problem.

For a long time I thought my voltages weren't applying correctly at the low end because the scaling of my lowest stable voltages was indeed very non-linear. But the heat mitigation and battery life gains seem pretty real.
[Nexus 4 Original Android Development] lazer155:
That's great. I'll give those voltages a try. In the event that they are too low will I always be able to boot into recovery and reflash a new kernel copy with default stable voltages?

Right now the best screen on time with WiFi (not actually browsing the web, just having it on and using an eBook app the whole time) I get 7 hours absolute maximum of screen on time. With 3g and web browsing the entire time, it is about 3 hours. But I'm not undervolting at all.
[Nexus 4 Original Android Development] whittikins:
I don't really follow the idea that it needs to be linear because the CPU doesn't always step from frequency to frequency all the way up. It can go straight from 300 mhz to 1500 MHz, which means going from 800 or so mv to 1150 mv (or whatever it is), even on stock kernel.

If the CPU is tested stable at 1026 MHz with 650 mv for instance, then it should be fine having 300 MHz through 1026 MHz at 650 mv, and have 11xx at 850 mv (or whatever it requires), and so on. It doesn't make sense that a 200+ mv jump between 2 frequencies would cause problems as long as each individual clock speed is stable at the designated voltage.

Right? :)

Or wrong, but it seems to be true!
[Nexus 4 Original Android Development] batman368:
i totally agree, linear voltage steps are not necessary, i just have them because so far i was too lazy to find better settings. actually i think it's very common for cpus to have non-linear voltage tables, with the the higher frequencies needing much more power than the lower steps. i remember a few computers, notebooks, etc. where i just never used the highest voltage level because it needed such a big extra voltage for that. tomorrow i'll try to find out my real voltage limits, let's see how the f/U curve looks like :)
[Nexus 4 Original Android Development] lazer155:
Do any of you use the trickster mod app bootloop preventer feature?
[Nexus 4 Original Android Development] consolidate42:
I recommend using system tuner to find your lowest voltages; just make sure not use set at boot any modified profiles and you should be fine after a crash.

Cap your max frequency @ 486mhz and begin lowering your 304mhz voltage one step at a time (swipe between screens to test cpu load). The reason you can't lock the frequency @ the step you are trying to test is because voltage changes for a clock step won't take effect if the cpu is currently occupying that frequency.

If you get all the way down to 600mV for 304mhz, then move on to testing 486mhz (by setting min @ 486 and max @ 594). If at any point you crash, upon reboot reload your safe across-the-board UV to save time and test the voltage above the one which caused the crash. If it seems stable, I recommend recording the one 12.5mV above that as your 'lowest stable voltage'.

Repeat this for each frequency step making sure to use previous found lowest stable voltages for all those below it. In practice, this whole process shouldn't actually take too long if you have pen and paper in front of you.
[Nexus 4 Original Android Development] lazer155:
When you say lowest across the board, do you mean keep lowering all frequencies until just before I get a crash? What is the acceptable CPU load*that I watch for when testing cpu load?
[Nexus 4 Original Android Development] consolidate42:
Actually, upon reflection, I don't think you need to do that step. The only reason I had the global UV profile saved was because I was using it prior to feeling motivated enough to find each individual lowest stable.
[Nexus 4 Original Android Development] lazer155:
Okay. And how do I find the lowest voltage for the highest frequency if there is nothing above it to select while I am adjusting the maximum frequency?
[Nexus 4 Original Android Development] ptesmoke:
OK uhm. You guys rocked the table so I'm not gonna bother :) been a long day and lazer made it exactly how I planned to do it! So props! I'll be doing some more testing in a few hours and will update the table. Cheers!
[Nexus 4 Original Android Development] mundixx:
Something wierd happened while i was asleep. The battery reporting has gone mad :D
[Nexus 4 Original Android Development] consolidate42:
You can use 1.4 min and 1.5 max again.