yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rogersnm:
ADB onto your phone and run cat /proc/kmsg and then run Antutu a couple of times, I guarantee it'll hit 80C minimum.

Btw, I'm going to try and compile franco's kernel between r175 and r180 to try and see which commit broke it for a few people. So if you're willing to test out a few kernel images (and r180 won't boot for you) send me a PM. I can't test them myself as r180 works for me :o

---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------

Yes, currently there is no set on boot option built into the app. It's worth noting that SR automatically calibrates the voltages to over 100mV below the stock voltages, so if you've only taken 50 mV off the stock voltages then you're probably using a higher voltage than SR used.

You can't cause hardware damage from undervolting however you may have data loss if the system crashes, so make a nandroid backup first!
[Samsung Galaxy Nexus] The Gingerbread Man:
For your edit the answer is yes, its there to protect you so if you undetvolt too much you won't be stuck in permanent boot loop basicly

Sent with a shake
[Samsung Galaxy Nexus] Sveke:
Undervolting is useless.

I used to obsess about it then I just looked in the mirror, slapped myself, and now I'm good.

Made zero real life difference.
[Samsung Galaxy Nexus] Luuthian:
Is there anywhere or anyone who can describe how the various scaling governors work and what the benefit of each one is? I checked the wiki, but it only had descriptions for francoTurtle and FrancoGazelle. I'm assuming those are discontinued, because my list says lazy, interactive, etc.
[Samsung Galaxy Nexus] franciscofranco:
Google usually does the trick ;)
[Samsung Galaxy Nexus] ArmanUV:
Most comprehensive writeup I found: http://xdaforums.com/showthread.php?t=1369817
[Samsung Galaxy Nexus] The Gingerbread Man:
OK so for those you who like the sound mods may like this, its a dsp manager which works with rascream rom (maybe more not tested) http://www.mediafire.com/?a27iaq0tn36yjtz.

Iv spent ages looking for a copy of dsp manager that actually works without cm9. Hope you guys enjoy it. Btw I'm not the one who made / modded / altered this to work I just found it through a whole lot of searching and playing. Don't forget to settings/sound/music effects if your on something which allows the choice or it won't work, rascream for instance.

Edit

If anyone ones interested in where I found it http://rootzwiki.com/topic/14354-moddsp-manager-for-ics-roms/page__st__20 end of page 2.

Edit 2

Compression doesn't work so well with bass boost but the bass boost works very very well set to extreme with bass booster set in preset eq panel :D

Sent with a shake
[Samsung Galaxy Nexus] franciscofranco:
r185

* New Wi-Fi driver from android-omap-3.0 repository - may contain bugs because it's around a 30 patches merge

* Decreased a little bit the nominal voltages to accommodate the change to the smartreflex driver change for the 1.5Ghz and 1.4Ghz steps

* SR now skips calibration if the nominal voltage is >= 1300mV instead of the previous 1350mV value

* New toggle to disable thermal throttle: echo N > /sys/module/omap_temp_sensor/parameters/throttle_enabled (need testing on this, might or might not work as I can't achieve higher temperatures than 68ºC no matter what I do)

* Small tweaks and optimizations - check repo
[Samsung Galaxy Nexus] leelaa:
Is this one also using the linaro chain?
[Samsung Galaxy Nexus] SupWiz17:
Going to try these out and see if I can get similar results
[Samsung Galaxy Nexus] franciscofranco:
No, I never compiled a kernel with linaros 4.7 toolchain.
[Samsung Galaxy Nexus] Antob125:
Will future kernels be compatible with linaro since it was merged with AOKP Gummy and CM9

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Why wouldn't it be compatible?
[Samsung Galaxy Nexus] Antob125:
No idea. Some people were saying that kernels would have to be compatible with linaro in order to use.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Dr Byte:
Mine is also HW9 and has no such issues. It even runs cool at 1500MHz for the limited tests I've done up there (just so I could report a problem if it didn't - I have no intention of using >1.2G for any length of time.)

It would be intriguing to see what would happen on a "crash'n'burn" special build of Franco's Kernel with DCC enabled and a hard-wired lower frequency of 1GHz... and a truly high upper limit. I guess that isn't going to happen though, especially since other kernels are already walking that tight-rope.

1GHz is more than enough grunt for my purposes!
[Samsung Galaxy Nexus] nodstuff:
Am -I- compatible with linaro? :/
[Samsung Galaxy Nexus] metalspring:
Battery life extender is still broken, it won't go higher than 96...I set it in your app and the file still says 96, glados app also reports 96 and can't change it higher

Its been like this on the past few nightlies and even on different roms

Did you mean to do this or is it a bug?
[Samsung Galaxy Nexus] franciscofranco:
Probably a bug. Will check later.
[Samsung Galaxy Nexus] nikulogical:
Whats wrong with Sr calibrating the 1344 step?
[Samsung Galaxy Nexus] franciscofranco:
Nothing? That step is still being calibrated, otherwise I would've write that in the changelog.
[Samsung Galaxy Nexus] nikulogical:
Ah sorry. I read mv as mhz.
[Samsung Galaxy Nexus] dermann:
Your kernel with aokp is great! I do loss the ability to calibrate my Color Gamma/Multipliers Tuning, but from what I can tell it doesn't need it after your kernel is flashed. Everything became more snappier, apps and windows seem to open quicker and smoother. Apex Launcher follows suit as well. :)

I've tried the beta Linaro roms, IMO I think my phone runs better without Linaro... at this point.

But better with fransicofranco.kernel and aokp. I, as many others have done, will make this my default kernel from now on. ;)

Thank you fransicofranco for all the love you've put into this.
[Samsung Galaxy Nexus] mgault:
I have a question about undervolting. If i am undervolting do I want to turn off the smartreflex too. The way it reads i need too or it wil pick its own voltages anyway. Is that correct or am i reading wrong.
[Samsung Galaxy Nexus] jnr21:
Yes you need to disable sr if you want to uv. Sr is for calibrating voltages automatically, manual uv settings doesn't work if sr is enabled.
[Samsung Galaxy Nexus] Lambetts:
PM.
[Samsung Galaxy Nexus] bat0nas:
I will give your voltages a try. Thanks!

I had a bit bigger mV setting by 50-100mV.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] relax24:
Have been using 181 for the last 10 hrs, and I noticed when I listen to music it tends to use the 1228mhz cpu value rather than <729mhz like I've set in the app
[Samsung Galaxy Nexus] rogersnm:
Got to 107C on the widget and then it shut down :rolleyes: Seems to work anyway :)
[Samsung Galaxy Nexus] zjmdp:
when i turn on sr, however, my uv setting does work according the value read from the panel MPU Voltages
[Samsung Galaxy Nexus] rogersnm:
It'll work to some extent, however if you do more significant undervolting then SR will cause instabilities.
[Samsung Galaxy Nexus] franciscofranco:
Good to know thanks :) guess next step is add the toggle into the app.
[Samsung Galaxy Nexus] bat0nas:
So far so good. Stable as rock!

Just interested.. saves this battery just a bit or not? :):):):)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
That's an area of debate, the answer is somewhere between not very much and a bit.
[Samsung Galaxy Nexus] P30SiNa:
Uh finally I can post here :)

I bought GNex last week and flashed with Milestone 4

Now I flashed with r185 2 hours ago

It's really really better than Milestone 4. I had some wifi problems it was very weak.

But after I flashed r185 now wifi works like a charm and it's powerful!

No problems with r185. It's stable!

I had 5 hours screen on time with Milestone 4. Let's see how is it with Wheatley governor!

Thank you Franco. You are awesome!

One question: Auto Brightness makes my phone a little laggy. Is it only my problem?
[Samsung Galaxy Nexus] energie:
Just flash :)
[Samsung Galaxy Nexus] lamecake:
Y U NO HAVE MY KERNEL?!

"oops.." *blush*

Testing right now :)
[Samsung Galaxy Nexus] triStateMindgate:
Personally I always Wipe Cache and Dalvik before flashing
[Samsung Galaxy Nexus] Vangelis13:
Because people will ask for sure: file is called "franco.kernel-nightly" at download; it doesn't mention that it is the #8 BUT it is.

First impression (at 1,2 GHz) is...ooops! Didn't even have time to see it, something flew by on the screen..!!

You might have (as expected, you've spoiled us..) over-performed on this one once again mate! :-D

Edit: I didn't know (still at 1,2 GHz..) that apps can open that fast..!!!
[Samsung Galaxy Nexus] energie:
Around 6800 antutu@1350!
[Samsung Galaxy Nexus] franciscofranco:
It will always download the latest kernel available. I had to change the filename to be like that otherwise I would need to implement the download procedure in a different way and this is much simpler and cleaner. :)
[Samsung Galaxy Nexus] Vangelis13:
Francisco, you can probably call it "4 bananas & an orange" and still everyone will flash it to get to use your kernel.

Well done young man, well done!! ;)
[Samsung Galaxy Nexus] joshnichols189:
LOL looks like someone on the market thinks Franco is kanging his own kernel..
[Samsung Galaxy Nexus] rabhw:
Hey Franco, just had a thought about 700mhz being the minimum, I understand you said fewer steps means its faster to ramp down, but what about battery usage in a case where the screen is on but no user interaction is happening?

Example being reading a book with Google books? Sitting idle with the screen on @ 350mhz vs 700mhz? Just a thought, I'm just interested in what you think.
[Samsung Galaxy Nexus] ro_explorer:
No cifs apparently .... too bad. I'm forced to stick with #7 then.

// sent from my green robot //
[Samsung Galaxy Nexus] sirj00:
wow, super, tremendous

This kernel just eclipsed another sphere.

Not a benchmark junky but it does give you a since of were you are at,

from one kernel to another.

Quadrant just went from 2250 and change to 3186. SAY WHAT.

If battery drain stays the same, I will have to be evicted from this

kernel to change. I'M NOT MOVING. I'M HOME

My money has been well spent with you sir, Fantastic work

thank you Franco
[Samsung Galaxy Nexus] franciscofranco:
Yes of course I am kanging other kernels, I have this available for download almost since this phone is out and before all the other kernels and yes I'm definitely kanging isn't it obvious?! ;)
[Samsung Galaxy Nexus] triStateMindgate:
I just saw that, pathetic really..

Francisco, you keep outdoing yourself bro. Cool touch with the updater, can't really get any easier.
[Samsung Galaxy Nexus] Redflea:
Damn, trying not to be the guy who says everything is always better...but this is definitely better/faster than 7.1. Still running at 1200...

Great work, Franco.
[Samsung Galaxy Nexus] ro_explorer:
Despite the fact there is no cifs in #8 I think I'll keep it for a day or two. It looks and feels very snappy. I wonder how it behaves :).

Anyway, here is s request .... please make a cifs module if yoy're not compiling this directly into the kernel. I know there aren't many cifs/tun users but nevertheless .... you know what I mean.

// sent from my green robot //
[Samsung Galaxy Nexus] knzo:
It's a good question but the answer may be tricky.

First, there's the question of how low the frequency can go while the screen is on even if there's no user interaction. While it is true that the frequency will only step up when there's enough demand, this may not apply when the screen is on because it would hurt user interaction. Why? Check next paragraph.

Secondly, assuming the clock will go as low as 350 Mhz when the screen is on and there's no interaction (which I have my doubts), would this be desirable? As soon as you interact with your device, the clock is so low it will ramp up at the smallest touch. Since it's on 350 Mhz, scrolling to the next page (if you're reading a book) may not be a pleasant experience and kind of sluggish and like I mentioned before, it would obviously ramp up a few steps which isn't the most battery-friendly operation a CPU can have - there's a correlation between graceful-agressive scaling and more-less battery saved.

Thirdly, also assuming the clock can go as low as 350 Mhz when the screen is on, does the difference in voltage between 350 Mhz and 700 Mhz outweigh the probable decreased experience in snappiness I mentioned in the second paragraph?

Finally, it'd be more wise to tackle this like I have on void kernel (Galaxy S2) - when there's less demand, one CPU automatically turns itself off. However, the clock remains whatever's been defined as lowest frequency. This seems to gather the best of the 2 worlds.

Sorry for the long reply, but I was interested.
[Samsung Galaxy Nexus] Vangelis13:
What they think is old news, don't restart that again guys..
[Samsung Galaxy Nexus] adamleerusse:
battery life on AOKP #12 and this kernel.. lost around 19/20 percent in 45 minutes.. is that normal? Everyone else experience this? Phone hasn't been to sleep during the 45 minutes though :D
[Samsung Galaxy Nexus] rabhw:
Thanks for the great reply. I do know that the screen on with no interaction will idle at 350, you can actually see it easily by opening up setcpu. Leave it on the main screen and it'll idle at 350, and if you rapidly flip between another tab and main, you can see it ramping up to 1200.

But like you said, there are other considerations to think about, I trust you know best!

About your S2 kernel, does this one disable second CPU depending on demand? Or is that something not supported in OMAP44XX? Or coming in a future release?
[Samsung Galaxy Nexus] drawde40599:
After a rom update or kernel u need give phone 2-3 days before u can actually see battery performance. Since 12 just came out I'd say not long enough,id install #8 kernel just came out, and by Wednesday u could actually see FULL benefits of combo . This has been my experience with all 13 of my Androids, and I've been " crack flashing " for years now
[Samsung Galaxy Nexus] rogersnm:
The auto brightness lag is due to google's wonderful implementation, I think most people just use a set brightness and adjust when necessary.
[Samsung Galaxy Nexus] The Gingerbread Man:
Franco you want a log for 185 not booting?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] lukasb9000:
My phone is acting somehow strange, does anyone have the same behavior?

Using conservative the cpu steps keep jumping from 380 (set min frq) to 700 to 1200 (thats my set max. freq) even if I'm not doing anything witht he phone just the display is on

Using wheatley it keeps jumping from 380 directly to 1220.
[Samsung Galaxy Nexus] rogersnm:
That's pretty normal, the phone has a variety of processes that idle away in the background and occasionally add a bit of CPU load. The wheatley governor is more aggressive and so scales straight to the maximum frequency whereas the conservative governor uses the intermediate 729 MHz frequency first.
[Samsung Galaxy Nexus] franciscofranco:
Yes please. Paste them on pastie.org and email me please, it will be easier for me to track the logs down on my email than here. I still dont understand why or how I broke it for some users on toroplus mostly. Hope we can find the cause soon.
[Samsung Galaxy Nexus] The Gingerbread Man:
No worries I'll try and get that for you today.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] matt22:
Oh yes it will be great !

I just find this kernel, that it support the usb Audio : http://rootzwiki.com/topic/14685-28-may-glados-v134/

Thanks for your work !
[Samsung Galaxy Nexus] Theshawty:
Franco, I don't know what spells you use to make the kernel, but it's only getting better and better! :)

185 is awesome!
[Samsung Galaxy Nexus] Antob125:
Will you put it in future builds?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
No I won't.
[Samsung Galaxy Nexus] sago62:
why??:o
[Samsung Galaxy Nexus] bat0nas:
LOL

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Culex316:
Wi-Fi performance seems to have improved a bit with this new driver. I did some speed tests and whereas before the speed would often decrease and increase now it's consistently fast. (stays at around 22-23mbps download with speedtests app instead of sinking to 15-16mbps then slowly climbing)

Certainly better than other kernels I have used
[Samsung Galaxy Nexus] bat0nas:
That's strange. I have 20Mbps wifi speed all the time (when the wifi signal bar is full of course). Even with stock kernel.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Because I build on a mac and because the supposed improvements are on the OS side and Im pretty sure the toolchain wont do jack squat to the kernel performance. Bring me raw data and numbers, then we'll talk.
[Samsung Galaxy Nexus] Antob125:
Sad face. Anyone that's good with this stuff can bring some raw numbers in for Franco? I mean all the roms will most likely convert to linaro. And I've been reading that some kernels have compiled the toolchains I would just love to see it in your kernel. Yet I have no idea what to do or how to help. I'm an amateur.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
Ask imosyeon, the developer behind leankernel, he uses the linaro toolchain in his latest kernel builds
[Samsung Galaxy Nexus] bigeyes0x0:
FYI, no noticeable benefit on leanKernel as well.
[Samsung Galaxy Nexus] spaceman860:
I got this on 185?

View attachment 1122292

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] ssglackey:
Franco, on 185 wifi theter wpa2 is not working, multiple clients can't connect. Only open hotspot is currently working.

Flashed 163 and it is ok, than flashed back to 185 and theter is gone :(

It may work on 180, but I didn't tested it.
[Samsung Galaxy Nexus] loudaccord:
Ezekiel already proved that the toolchain compilers do nothing for our kernel. Search for it.
[Samsung Galaxy Nexus] digiangel:
I confirm that wifi tether doesn't work with r185. Thanks you Franco for your diligent hard work!
[Samsung Galaxy Nexus] spaceman860:
Even after reboot I keep getting kernel wakelock WLAN_RX_WAKE

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] relax24:
I've had it since as far back as I can remember. Nothing is syncing, I believe it's maybe just a pc/router issue.
[Samsung Galaxy Nexus] P30SiNa:
I had this on Milestone 4 too I guess!

-----

Guys what max cpu freq do you recommend for screen-off with Wheatley gov?
[Samsung Galaxy Nexus] rogersnm:
All the testing I've done shows the max screen off freq doesn't seem to work for the wheatley governor, when you play music with the screen off it just uses the max freq available.
[Samsung Galaxy Nexus] jhondidfool:
At long last I tamed the voltages. Stable, even after reboots... lovely thing.

Now.... is there any way this frequencies set themselves on boot and not make me set them every time?
[Samsung Galaxy Nexus] Gahh Its Lee:
Need to make a script in initd
[Samsung Galaxy Nexus] Theshawty:
The weirdest thing happened to me right now and I think it would be kernel related since it has never once happened on any other kernel versions. Might be app related, but I'm gonna try my luck.

Today I was playing Continuity 2 as I do sometimes and when I exited out of the app, my system crashed, completely. I couldn't touch anything, not even the navbar keys. Shortly after, they disappeared. I had to do a battery pull to come out of it and upon reboot, it all seems fine.

Strange, I have never once before had this issue on any kernels, kernel versions or ROMs.

I run the latest Franco nightly (#185)
[Samsung Galaxy Nexus] sago62:
why when I choose the frequencies and the governor, flag on boot, if I turn the phone back all stock?
[Samsung Galaxy Nexus] CaspaTheGhost:
Sounds like a System UI crash especially if the navbar disappeared, normally resets itself so the navbar comes back after a minute or so.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Theshawty:
I notice I could actually lock the phone even after the navbar went away, but it looked and felt like the "CRT animation" was slowed down a 1000%.

What could have been the reason for this to happen?
[Samsung Galaxy Nexus] clepsy:
Disabling smart reflex actually disables the voltage control?

Did a test and with sr disabled whatever voltage I set to GPU(512) does not seems to affect, with sr on I can't go bellow 1050mv, however disabling it I could even set 700mv, I believe it the same for others

Was just wondering because I saw some guys with extreme UV settings that actually goes bellow minimum voltage that a transistor would switch (there is a minimum value around 800mv dono exactly) :p
[Samsung Galaxy Nexus] dominoes20:
Since flashing Milestone 4 I haven't been receiving my push notifications. Is anyone else experiencing this?
[Samsung Galaxy Nexus] rogersnm:
You can check /sys/kernel/debug/voltage/vdd_mpu/curr_nominal_volt to see what the voltage value is. I would suggest the values are being implemented as if I set it too low it does crash.

Just reached a new peak temp (without shut down) of 109.8C :o
[Samsung Galaxy Nexus] dr.sonic:
These are min values i could get, even with sr off (at least I think it's off). How can I be sure that sr is off?

1344 mhz - 1225 mV

1228 mhz - 1175 mV

1036 mhz - 1050 mV

I didn't have time to test 729,384,192.

During these tests I came to conclusion that there is no real difference in phone performance regarding speed and responsiveness between 1536mhz and 1036 mhz.

GNex via tt
[Samsung Galaxy Nexus] CaspaTheGhost:
I sometimes get it when mucking about with themes, but it comes back on its own (same as when you change recents style)...

If you were playing a game it could have been a simple system orientation issue or the like.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] schizophrenia:
just tried wifi tethering to my laptop and it works just fine.

strange

on r185 AOKP b38
[Samsung Galaxy Nexus] Diger36:
Hmmm, after 2 days flawless running with my CPU UV settings my phone had some serious reboot issues. It rebooted several times. Start over... But first on default settings...
[Samsung Galaxy Nexus] Gahh Its Lee:
Corrupted data probably. Do apps all work? Do a bunch force close?
[Samsung Galaxy Nexus] Diger36:
One is FC. Haven't discovered any else yet. I'm afraid it could be since recovery acted strange at first. I'll see how it goes. Worst case I'll restore a nandroid.
[Samsung Galaxy Nexus] Theshawty:
Solution = don't undervolt.

I thought it was pretty clear that undervolting doesn't help the overall battery time much, and that playing with undervolting can be quite dangerous.
[Samsung Galaxy Nexus] rogersnm:
Did you make the init.d modifications? If you didn't then there's your problem :p
[Samsung Galaxy Nexus] wildguess:
None of r18x nightlies boot up my phone.

My battery dies from full charge with minimal use on M4 in 8 hours.

WiFi never turns off during sleep even though it is supposed to.

I was very excited when I first used Franco kernel, but it is high time to come back to the stock one, sorry.
[Samsung Galaxy Nexus] Diger36:
I thought it was pretty clear as I stated before that I UV-ed for heat issues and not for

battery life, but thanks anyway.

Nope, didn't make the unit.d mod's. I wasn't aware they where absolutely necessary? Why? I made them manually, disabled SR and they stuck on boot. No problems with bootloops. Just some spontaneous reboots in about half an hour time...
[Samsung Galaxy Nexus] Gahh Its Lee:
Yea 3% battery savings or something. However awhile ago uving somehow became magical again so everyone's doing it and now the world has no more hunger lol.
[Samsung Galaxy Nexus] ssglackey:
Did you tried wpa2 or open ?
[Samsung Galaxy Nexus] schizophrenia:
tried both....
[Samsung Galaxy Nexus] jhondidfool:
Brilliant ... ... .... how did you say one does that, again?