yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
26th April - Milestone 3

This is the perfected version of the last 35 days of testing of roughly 1 nightly build a day. The most important changes from Milestone 2 are:

* Merged 4.0.4 kernel patches from Google (IMM76D and IMM76I)

* Data dropouts is fixed

* Interactive Governor patched up to be in line to android-3.0 branch

* Hotplug governor added and tweaked for stability

* Merged a lot of patches from omapzoom.org for battery and performance improvements in our OMAP4 board drivers

* Hotplug_mod renamed to Generic Hotplug and changed paths to: /sys/module/omap2plus_cpufreq/parameters/generic_hotplug

* Added BLX from Ezekeel. The default value is 96. Path: /sys/kernel/fast_charge/force_fast_charge

* Reduced VAUX3 and VUSIM voltages for more screen_on time at the end of the day

* Simple IO scheduler added and made default

* EXT4 patches from 3.0.2X kernel.org patch

* Lots of small tweaks and improvements that are available on my bitbucket git repository

Thanks for everyone whos been with me, helped, reported and supported me. Big shout out to +Ezekeel Johnson and +IMosey On for their awesome work on their kernels, some of their patches, code and long hours discussing kernel stuff.
[Samsung Galaxy Nexus] nklenchik:
Am I considered a flashaholic if flash my kernel while driving haha
[Samsung Galaxy Nexus] triStateMindgate:
Haha, been there..But Yes.
[Samsung Galaxy Nexus] Razer(x):
Can't somebody do a post or something about governors? i don't know what's these interactive and hotplug
[Samsung Galaxy Nexus] dwang:
Any chance of 144 w 512gpu? The input boost parameter for interactive seems interesting.
[Samsung Galaxy Nexus] drawde40599:
U must not have kids, pretty dumb!!!
[Samsung Galaxy Nexus] dpaine88:
Francisco do you prefer 384 or 729 as a minimum with the interactive gov?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Neejay:
Does the app install the 384 or 512 version?

Thanks for all your hard work and time!
[Samsung Galaxy Nexus] franciscofranco:
There is no r144 :p
[Samsung Galaxy Nexus] ceejay83:
think it flashes stock speed, which is like 308?
[Samsung Galaxy Nexus] nklenchik:
Think about what you said then get back to me. I think the wrong action would be not to flash this thing immediately, but to answer your question, no I don't have kids.
[Samsung Galaxy Nexus] franciscofranco:
Milestone = stock GPU.
[Samsung Galaxy Nexus] triStateMindgate:
Milestone is always Stock freq.
[Samsung Galaxy Nexus] raubkatze:
Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs

Hotplug governor is simply ondemand + dynamic hotplug.
[Samsung Galaxy Nexus] triStateMindgate:
I had that question back in the day, always wondered what governors are, how they scale, and overall operate. There is some info online regarding this, for now, this should be a good read. Plenty of info, enjoy...

http://androidforums.com/xperia-mini-all-things-root/513426-android-cpu-governors-explained.html
[Samsung Galaxy Nexus] franciscofranco:
About the governors and Governor Control in the app I suggest you all to search for yourselfs, even I don't know one or two of those options and with all the information available for searching it would be a waste of my time to write every bloody explanation in every damn Governor settings ;)
[Samsung Galaxy Nexus] raubkatze:
Thanks for M3!!! Now waiting for new nightly)
[Samsung Galaxy Nexus] isinisterx:
How many hours of screen on time do you guys usually get in a normal day off stock battery? Like constantly turning on and off the screen
[Samsung Galaxy Nexus] raubkatze:
About 2-2,5 hours.
[Samsung Galaxy Nexus] franciscofranco:
Nightlies are not going to be back for at least a week. I have some roadmap to draw for the next nightly bunch and I need a few days off nightlies building ;)
[Samsung Galaxy Nexus] dpaine88:
Enjoy the time off Francisco

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] raubkatze:
We'll wait patiently -)
[Samsung Galaxy Nexus] dwang:
Any chance of milestone 3 w 512gpu oc?

especially given that you aren't going to put out a new nightly for a while.
[Samsung Galaxy Nexus] triStateMindgate:
That really depends on a lot of things, chipset, battery, ROM, Kernel, Usage, how often you turn the screen on, what you do when its on. having the screen on while doing nothing on a static wallpaper is not going to draw as much battery as let say streaming Netflix via 4g/3g....

All depends, there is countless of threads/discussions in here and General section about this.

For me I would say 2.5 - 3 hrs
[Samsung Galaxy Nexus] franciscofranco:
No, Milestones are stock GPU only.
[Samsung Galaxy Nexus] raubkatze:
Only nightly with 512 GPU OC - http://xdaforums.com/showpost.php?p=25320498&postcount=13742
[Samsung Galaxy Nexus] BFirebird101:
I'm really sorry if this has been answered, however, here it is. So I want to DISABLE Smartreflex if I'm using my own CPU voltages for each incremental step (such as setting them in SetCPU? Or is Smartreflex strictly for GPU voltages, and everything else other than CPU voltages?
[Samsung Galaxy Nexus] vomer:
Thanks franco! M3 :cool:

What are you planning on next if you don't mind me asking? :D
[Samsung Galaxy Nexus] Serious_Beans:
If you want to use your own voltages disable smart reflex.
[Samsung Galaxy Nexus] mazubo:
Franco, thank you very much for this m3! And also a big thank you to all who have helped myself and others with kernel questions! Of the threads that I visit, Franco's forum (and kernel) is top notch!

Thank-You:):):)

:-D
[Samsung Galaxy Nexus] myrdog:
Thanks for M3!

Btw, this is a bad time for your paypal donation thing to not be working haha!
[Samsung Galaxy Nexus] javi3k:
omg m3 ready to goooo niceee thankks franco for your great work.
[Samsung Galaxy Nexus] homer2320776:
Nightlies were my crack! The thrill of the flash, oh well, guess it's back to updating firmware on my router to get my fix. Enjoy the time off! :D
[Samsung Galaxy Nexus] vomer:
True, but you can just buy the app several times ;)
[Samsung Galaxy Nexus] neotekz:
is milestone 3 384mhz gpu or 512? does it come in both clock speeds?
[Samsung Galaxy Nexus] franciscofranco:
I didn't know it was ****ed, thanks for the heads up... paypal idiots with their bureaucracies...

Comon it was answered one page before.
[Samsung Galaxy Nexus] nklenchik:
M3 running effortlessly on Liquid 1.3. I'm gonna stay with this for a while I hope...maybe I can take some time off from checking the app every day lol
[Samsung Galaxy Nexus] triStateMindgate:
You can't do that with one account can you? Unless you get the other device apps lol.

Let's make sure those paypal thieves get that fixed soon Franco, lil something is well deserved apart from your work on the app.. :D:D:D

---------- Post added at 09:40 PM ---------- Previous post was at 09:37 PM ----------

I have a feeling M3 is going to be a beast, waiting to see what the feedback is after a day or 2 tho, current setup that I flashed yesterday is amazing so far, leaving it untouched.
[Samsung Galaxy Nexus] QUEDRO:
Franco,

Not sure if it was reported, but Disable Smartreflex in franco app has a bug. After reboot the Smartreflex turns active even though it is checked. I have to recheck and gain root to disable again.

build 141 was awesome! my new record on battery - 2 days 11 hours with lite use on 4G and WiFi. Thanks for M3!
[Samsung Galaxy Nexus] drawde40599:
m3

Milestone 3, seems just as snappy as overclock g p u versions, interactive stutter completely gone . Thanks again for your time franco
[Samsung Galaxy Nexus] vomer:
You should try AlertPay :)
[Samsung Galaxy Nexus] dwang:
yep, interactive seems golden with m3.

Only thing I'm noticing is that the GovernorControl settings in the franco app isn't saved across reboots.

I set input_boost to 1 and hispeed_freq to 1344000, but it goes back to default on reboot.
[Samsung Galaxy Nexus] asianboy9:
Sorry if this has been asked before, search didn't turn up my answer, nor did trawling through the last 20 or so pages (I.e. the last 1 hour of postings :p).

Will there be any problems with running M3 (or any 4.0.4 based nightly kernel) on a 4.0.3 ROM?

As yet my rom (apex) hasn't been updated yet, and I haven't seen enough stability in the aokp/liquid roms (yet) to justify changing everything over.

Thanks!
[Samsung Galaxy Nexus] triStateMindgate:
No problems at all, go for it.
[Samsung Galaxy Nexus] BrUhNiGGs:
Just flashed milestone 3. See how it goes after a day at school tomorrow.
[Samsung Galaxy Nexus] willl03:
M3 running as smooth as it gets using the hotplug gov, cant wait to see the battery life. Amazing to see this release being as smooth as nightlies with its 308mhz gpu
[Samsung Galaxy Nexus] mikeandjaimie:
I'm seeing a little stuttering with m3 over 143. Scrolling doesn't seem as smooth, especially tapatalk.. Dunno if this is cause of the gpu stock freq, usually only run 512.
[Samsung Galaxy Nexus] nklenchik:
I've been running music and browsing Google Currents the entire time. 3+ hours of screen on time? I'd say so
[Samsung Galaxy Nexus] yyz71:
First benchmark run with m3
[Samsung Galaxy Nexus] franciscofranco:
I know they don't set on reboot, it's written in the description.
[Samsung Galaxy Nexus] dwang:
Ok I see that u just added that comment with your latest app update.

Easy enough to create an init script.
[Samsung Galaxy Nexus] drawde40599:
It's working perfect on my phone, I've actually never seen it run this smooth
[Samsung Galaxy Nexus] The Nexus Project:
Same here, Milestone #3 for me

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] BryanChung:
Congrats on hitting Milestone 3! :) Will be staying on this for a while now! :D
[Samsung Galaxy Nexus] brianisme:
2h 30 - 3h with 1d 3-4h standby time with normal usage. With that said, looking forward to testing M3! Will take a lot to pry me away from r121. Thank you very much Franco!
[Samsung Galaxy Nexus] BrUhNiGGs:
M3 is running A LOT cooler than any nightly i've tried. Could be just the stock GPU which I see no different with 385 or 512mhz :confused:

Guess I'll be sticking with this for a while!
[Samsung Galaxy Nexus] -viperboy-:
Great work on this! Flashed milestone 3 on my Sprint GNex and bought the app. Really nice work! So surprised how well 384mhz runs! I locked it to that to test voltages. Keyboard is slightly slow but I could legit run it like this without it annoying me.

Keep up the good work!!

Edit: uh oh, undervolt still seems to not be working. Turned off SR with your app and the phone tells me its running at 600mv @ 384mhz. No way. Any suggestions?

Edit2: happens with CPU, Iva, and core voltages. None seem to respond to the voltages I enter.

Edit3: Let's see how many more edits I need lol so it seems that when you apply the voltages, you need to toggle the SR disable checkbox. I rebooted the phone, 384/384 was still set. 600mv was set, SR disable checkbox was checked. Applied the insanely low values, no crash. Unchecked the SR disable box (which should enable it) and it locked up. Maybe some odd code that handles the SR disable checkbox? Cause the phone should crash right away when I reapply the voltage if SR disable is checked, correct?

Edit4: Last edit, I hope. It seems that the SR disable checkbox is backwards. When checked (SR disabled), applying those values don't do anything. When unchecked (SR enabled), the table still says what it's doing but applying the values are live. I hope that clears it up :)
[Samsung Galaxy Nexus] bendirkss:
Well battery life with M3 should be OK considering my phone went up from 7 to 8 percent unplugged;)
[Samsung Galaxy Nexus] TheInVisibleGoD:
You can't judge the battery life only according to that... In fact that's normal behaviour because the phone measures battery percentage by his voltage, and can have fluctuations between screen on (battery load) and screen off (battery stabilizes his voltage).
[Samsung Galaxy Nexus] kevinngck1:
Is that milestone3 only have 384mhz to choose?
[Samsung Galaxy Nexus] franciscofranco:
That happens because I use PM:FAST instead of PM:OFF. With PM:FAST we get stronger signal, but wifi doesn't actually sleep, while OFF does the opposite.
[Samsung Galaxy Nexus] altimax98:
Netflix HD is not compatible with 4.0.3. Mcr ir8 is not full 4.0.3 only selected portions. So wherever they did over there allowed Netflix to keep working properly.
[Samsung Galaxy Nexus] RMatt1992:
Will that be the only change?
[Samsung Galaxy Nexus] eiabea:
is that the same nice feature as in your NS kernel? :-)

full speed wifi while screen is off?
[Samsung Galaxy Nexus] franciscofranco:
No it won't.

Yes it is ;)
[Samsung Galaxy Nexus] Thracks:
Any chance of getting the powersave governor for screen off/in-call situations? How about a UV interface? Or is that still unstable/unworking?
[Samsung Galaxy Nexus] Nydoria:
Hi I "flashed" your Kernel in CWM via .zip function and now im stuck in the Google logo bootscreen.

Did i do something wrong?
[Samsung Galaxy Nexus] superbobup:
Are you running a 4.0.3 rom? Did you make sure to wipe cache and dalvik?
[Samsung Galaxy Nexus] Nydoria:
Oh its just for 4.0.3? That sucks.

Thanks for your help :)
[Samsung Galaxy Nexus] beekay201:
Hey Francisco, could you help me out here? Don't know if I'm right.

For UV'ing, I could edit arch/arm/mach-omap2/opp4xxx_data.c, right?

#define OMAP4460_VDD_MPU_OPP50_UV - would define voltage for 350mhz.

#define OMAP4460_VDD_MPU_OPP100_UV - would define voltage for 700mhz.

#define OMAP4460_VDD_MPU_OPPTURBO_UV - would define voltage for 920mhz and

#define OMAP4460_VDD_MPU_OPPNITRO_UV - would define the voltage for 1200mhz.

:) thanks.
[Samsung Galaxy Nexus] franciscofranco:
Yes exactly. UV comes next nightly though, fixed two bugs with the previous implementation and now it works.
[Samsung Galaxy Nexus] beekay201:
:D

yeahh, that's good news. I think I won't stop sniffing around though.

Also, after browsing some more through the code, I have a couple more questions.

What are OMAP4460_VDD_IVA and OMAP4460_VDD_CORE?

edit: realized i had copy/pasted OMAP4430 lines.
[Samsung Galaxy Nexus] vladtdr:
doesent work on android revolution hd rom, keeps you at google screen
[Samsung Galaxy Nexus] Jrbourque:
Arhd isn't 4.0.3 ...not compatible
[Samsung Galaxy Nexus] beekay201:
10chars plus 1
[Samsung Galaxy Nexus] aron7awol:
I think you've differentiated your kernel from the others with your tweaks. Let me share my kernel testing and benchmarking results...

I've tested every kernel that I found to be available in order to see where each would stand performance-wise. I did real world testing by running the kernels for extended periods of time and also took notes on anecdotal performance and battery life. Franco #5 with interactive governor seemed to give me the smoothest performance opening apps, probably because of it's I/O prowess. Apex @ 1.35 had the best anecdotal performance using the web browser, probably because of its CPU prowess. I also did some benchmarking with AnTuTu and Vellamo. It came down to a battle between Franco #5 and ApexV4, so I focused a lot of my detailed testing on those two.

AnTuTu:

Apex @ 1.35 GHz - 6570

Franco @ 1.2 GHz - 6301

Apex @ 1.2 GHz - 6012

Franco @ 1.35 GHz - 6800+? (hypothetical)

Vellamo:

Apex @ 1.35 GHz - 1081

Franco @ 1.2 GHz - 980

Apex @ 1.2 GHz - 970

Franco @ 1.35 GHz - 1090+? (hypothetical)

Some notes from my testing:

* Franco dominated Database IO in AnTuTu. Always around 500 while all other kernels could barely break 300 in that test.

* Apex at 1.35 GHz dominated the CPU tests in AnTuTu as well as overall AnTuTu and Vellamo scores due to the 12.5% clock speed advantage.

* Franco dominated the SD read tests, always around 23 MB/sec while all other kernels were around the 17 MB/sec mark in that test.

* Apex had noticeably better battery life, even at 1.35 GHz, but that's certainly due to its 15-20% undervolting. Since power consumption is proportional to f*V^2, it makes perfect sense that lowering voltage has a huge effect on power consumption. Luckily, I see Francisco has managed to fix the UV interface and upon the release of nightly #6, it will no longer be an advantage of Apex.

* GPU OC doesn't seem to be working in any of the kernels. I saw basically no difference in 3d performance whatsoever between kernels.

My conclusions:

Francisco, you've obviously done an excellent job with your I/O tweaks. They show up in the real world testing as well as the benchmarks. The magnitude of the performance increase is impressive. You also managed to squeeze out a tiny bit more CPU performance over stock.

The CPU performance crown goes to Apex.

The I/O performance crown goes to Franco

The battery life crown is a tie once Franco #6 is released.

Of course, adding that extra 1.35 GHz step would instantly make Franco kernel the winner in all categories ;)
[Samsung Galaxy Nexus] sluflyer06:
I agree with this, I've not yet seen any evidence the GPU overclock is working or ever has worked to date on any kernel. :confused:
[Samsung Galaxy Nexus] leoaudio13:
Com'on FRANCO! make it a 'nightly' build! Release the SIXTH tonight please :D
[Samsung Galaxy Nexus] Spronx_:
Thanks for this info - I have been kernel shuffling to test real world performance but never really benchmarked and I found this kernel to be the best with overall performance but apex was great with battery.

It is FANTASTIC news to hear that undervolting is coming in the next nightly.

A few generous beers will be heading franco's way.
[Samsung Galaxy Nexus] MontAlbert:
I hope this is a joke... If not maybe read this http://six6sicks.wordpress.com
[Samsung Galaxy Nexus] drawde40599:
It was a joke brother
[Samsung Galaxy Nexus] bendirkss:
A joke...
[Samsung Galaxy Nexus] drawde40599:
Been posted 3 times already that its stock gpu no overclock
[Samsung Galaxy Nexus] crazyald:
sorry for sounding like a total noob but you flash this kernel through recovery, right?
[Samsung Galaxy Nexus] joeyfong:
Yeap or you can flashed by updater.
[Samsung Galaxy Nexus] swiftyy:
Thank you for M3! Franco you're always hardworking :)

Flashed and going to test it out
[Samsung Galaxy Nexus] jnr21:
Ok, m3 has stock gpu freq, but is it 307mhz (stock google underclocked) or 384mhz?

Edit: It's 307mhz
[Samsung Galaxy Nexus] fish0729:
hi Franco, thx for the M3! Does it support USB digital out to USB DAC, such as the fiio e17?
[Samsung Galaxy Nexus] jcmm11:
307. All milestones are 307. If that changes I'm certain we'll be told.
[Samsung Galaxy Nexus] mistermojorizin:
you can also verify that in the app, under where you can change core voltages, it'll show you 307 mhz
[Samsung Galaxy Nexus] Stretlow:
not that i can see any difference playing 9mm or virtua tennis but on benchmarks (i know, i know) there's a 30fps difference from running 384.

Just an observation
[Samsung Galaxy Nexus] oct_7:
Is it expected that the build number is still IMM76D and not IMM76I?

Or, it is supposed to be updated by the ROM?
[Samsung Galaxy Nexus] joeyfong:
The build number is for the ROM, not kernel.
[Samsung Galaxy Nexus] raubkatze:
Franco, I had a problem with battery drain the last night.

M3 729/1228, no UV, interactive, Generic Hotplug on, SR on

Kernel wakelocks log attached.
[Samsung Galaxy Nexus] psyren:
Just had a reboot with an accompanying loud pop from the speakers...

Was playing Draw Something at the time.

This has never happened before, and the kernel logger was turned off, so I don't think I can provide a log.

384/1228 interactive, SR on, no custom UV, hotplug on, using milestone 3.
[Samsung Galaxy Nexus] monkey hung:
I don't wanna be one of those people complaining about battery drain, but I'm complaining about battery drain. Down to 84% with 1 hour and 52 minutes ON time and 18 minutes screen on time. No apps installed and using AOKP B34. My mobile network signal is amazing, however. It's been green the entire time. Using M3, interactive, 1.3GHz Max min and 329 or whatever. No other settings enabled.
[Samsung Galaxy Nexus] rene_r:
Hi Franco, I found a little bug in your kernel updater - app, if you download your latest milestone(3), the file name is xyz-milestone-2.zip, I think it should be xyz-milestone-3 ;)

but no big deal, just want to let you know!

Keep up your great work!!

br

rene_r
[Samsung Galaxy Nexus] ArmanUV:
Does anyone know what I should change hispeed_freq to when I want interactive to scale up to 1344? it used to be 1228800, what is that 800 at the end?

Also, what are good performance values for input_boost and above_hispeed_delay? I coudln't find anything about these two values on the governer thread.
[Samsung Galaxy Nexus] raubkatze:
And now...

I'll reboot and look further.
[Samsung Galaxy Nexus] psyren:
Just had my second reboot from looking into my settings =\

EDIT: sent logs via Franco app. I had logger turned off through the app as well, so I hope there's still useful information there.
[Samsung Galaxy Nexus] Razer(x):
Had something similar, lost around 6% while sleeping
[Samsung Galaxy Nexus] stellaryt:
Did you update the app？
[Samsung Galaxy Nexus] jcmm11:
30 or 3? 30 sounds absurd. 3 seems plausible. Latest nightly running at 512 is about 5fps faster on nenamark. Practically speaking the difference is meaningless in the great majority of cases. And for those cases where it does matter the nightlies are still there.
[Samsung Galaxy Nexus] raubkatze:
I lost around 8% for about 3 hour. It's not so much but as a rule I lose just 0,5-0.8 %/h when screen is off.
[Samsung Galaxy Nexus] drawde40599:
So u haven't even had the kernel installed for even 24 hours, or even ran a few charge cycles and ur complaining about battery??
[Samsung Galaxy Nexus] monkey hung:
Yup. Because when it drains that fast, 24 hours doesn't matter.
[Samsung Galaxy Nexus] drawde40599:
Mentioned on very first post after update, fix is update the app,

Em I the only one that at least skims threw the days posts when I have an issue? Be4 I post

---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------

Ur right its ur phone cause mine don't do that
[Samsung Galaxy Nexus] Stretlow:
It was using Quadrant (im aware this isnt the greatest) Theres a part of the test where there are two planets, on 143 384 its 60fps on M3 its 30.

not complaining, just an observation
[Samsung Galaxy Nexus] monkey hung:
Just because you don't have a problem doesn't mean no one else can have a problem. Besides, it's draining slowly now for some reason but was draining faster when it was full. I guess I'll see what happens after a few days.
[Samsung Galaxy Nexus] raubkatze:
Use NenaMark2 to test it.
[Samsung Galaxy Nexus] stellaryt:
About the app's governor control.

The value which I set would saved by app but everytime（after reboot or change governor） to set them need to enter another value and then enter the saved one,otherwise they would not take effect.
[Samsung Galaxy Nexus] drawde40599:
U don't have a problem all I'm saying, u can Google over and over and read its recommended to run few cycles before judgment battery . + even the stock kernel runs threw first 15% pretty fast then slows down . But .... OK bye
[Samsung Galaxy Nexus] jhericurls:
To save me going over the same ground, I'll quote franco
[Samsung Galaxy Nexus] stellaryt:
Maybe my bad english...I know it not save after reboot and change govornor.

Just like uv,there are values saved and you only need to hit apply button.And in the input box of govornor control the values were saved and exist,but if you hit confirm,the value weren't change,you need retype another value then type the one you want.
[Samsung Galaxy Nexus] leelaa:
Does anyone else's widget just state the same values? Its all ways saying my CPU frequency is at Max.
[Samsung Galaxy Nexus] raubkatze:
It seems strange since reboot I have no kernel wakelocks in log at all...
[Samsung Galaxy Nexus] leelaa:
Try the reset kernel and flash Franco again maybe?
[Samsung Galaxy Nexus] raubkatze:
I'll try to reflash M3 later after some test.