yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] DonXoB:
The kernel will probably increase your battery life. There shouldn't be problems while updating to future official updates.
[Samsung Galaxy Nexus] superbobup:
I'm on 152 and I only get 2% drain over 8 hours. I don't know why I had the previous weird drain, it was just some oddity
[Samsung Galaxy Nexus] franciscofranco:
r154

* Revert all the experimental OMAP and omapzoom patches. From now on there won't be merged a single OMAP patch thats not from android-omap-3.0 branch. The experimental patches were introduced on r121 and r133 so now we'll have the same stability and battery life as we had before plus all the introduced improvements and tweaks applied from r133 up to r152

* Merged more Interactive patches from android-omap-3.0
[Samsung Galaxy Nexus] Moz007:
When we apply a new kernel, all the old files are deleted automatically ?
[Samsung Galaxy Nexus] drawde40599:
**** ya!!!! Those r my 2 favorites!!!! Ur 2 all time best my option!!

---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------

Few tried to help u yesterday ,didn't see ur reply,ur issue probably not even an issue read backwards...
[Samsung Galaxy Nexus] yungboss22:
With r154, undervolt doesnt work now.
[Samsung Galaxy Nexus] Timmyfoxeh:
Sounds great, flashing now!
[Samsung Galaxy Nexus] Emilius:
Thanks man, testing it....
[Samsung Galaxy Nexus] mert2go:
nightly 154 512 gpu seems to work great till now!
[Samsung Galaxy Nexus] alphaola:
Franco help my battery won't drain itself. What should I do. Latest nightlies and Aokp m5. Well done bro.
[Samsung Galaxy Nexus] franciscofranco:
All you need to do is flash the kernel, the rest I take care of.
[Samsung Galaxy Nexus] jhericurls:
154 is soooo much smoother than 153, Not noticed any lag at all on 192 Mhz.
[Samsung Galaxy Nexus] jan-willem3:
Congrats everyone with fail of the GS3:D
[Samsung Galaxy Nexus] johno168:
Samsung: "let's remake the Galaxy nexus"
[Samsung Galaxy Nexus] opethrocks:
My phone is getting really hot again, this hasnt been happening since milestone 3. With only about 5 minutes of browsing my mpu temp was 145 degrees
[Samsung Galaxy Nexus] franciscofranco:
Yikes 145 degrees is like the face of the sun.
[Samsung Galaxy Nexus] nklenchik:
I was getting pretty good battery life on 152, but a-flashing we shall go
[Samsung Galaxy Nexus] Metallice:
To clarify, r154 has reintroduced that old bug where smart reflex ignores you custom undervolt values during its calibrations. It's starting its calibrations from the default voltages instead. Custom undervolting now only works if you disable smart reflex.

And i know some people think that's how smart reflex is supposed to work, but its not. We want it to start at the nominal voltages we set and calibrate down from there, and it had been working correctly in the last few builds.

No biggie, I know the voltages SR would have calibrated to anyway so I can just disable SR and set them manually for now.
[Samsung Galaxy Nexus] Moz007:
This kernel is always getting better ! Can't wait for a 1.5Ghz version and it will be perfect !
[Samsung Galaxy Nexus] franciscofranco:
Exactly. I gotta revert the patch again. The patch comes from IMM76I though.
[Samsung Galaxy Nexus] bradm23:
I'm alittle curious why u decided to revert all of those patches. 151 and 152 were sooo smooth and still good battery. 154 seems to get some jitter when scrolling again
[Samsung Galaxy Nexus] yyz71:
Hungry for 1.5ghz :)

Sent from M5
[Samsung Galaxy Nexus] bswpt:
@Franco: is there a certain reason for not supporting cifs anymore? I can remember, that i could use cifs-manager and a fitting cifs.ko with your kernel. It's not working anymore and i don't find cifs-support mentioned in the opening posting.
[Samsung Galaxy Nexus] mikespe:
The true test will be tomorrow when I start off with a full charge but this version seems to have fixed my battery drain issue. It's draining MUCH slower now than it did on 152. I will say the Milestone 3 gave me good battery life but it did seem a LITTLE slower.

Thanks for fixing...I'll report more tomorrow...if I can figure out which thread I posted in! (it's difficult to keep track of both threads...anyway of combining them?)
[Samsung Galaxy Nexus] bradm23:
Getting really hot on 154. Never had a heat issue before
[Samsung Galaxy Nexus] blackdub370:
+1 please 1.5 Ghz

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] The Gingerbread Man:
OK took the plunge, I'm back using this again after using stock for a couple of months, my inner flash junky took hold :D

I'm using milestone 3 from the Franco kernel app and using the settings I tried out the high performance sound, it made my headphones quieter, I expected it to be louder. Rebooting made no odds.

Worth noting I have been using the Alsa mod off the market for a while, could this effect it? I did freeze it with titanium and tried rebooting again and still when turning on high performance sound it gets quieter. I dunno if its cos I'm using klipsch s4a's wouldn't of thought that would make a difference.

Could some explain why this is going on? Sorry for not searching on this occasion but I left this thread months ago and was a billion more pages since I used this last.
[Samsung Galaxy Nexus] endymion2k5:
Thanks for reverting those OMAP patches. Im not a good tester, hence i never reported any good information about it. I use my phone differently each day, which is not a good test. I do not deem 'screen on' time a valid way of testing it, since i listen to a lot of music. The screen isnt on, it isnt in deep sleep either. It varies each day.

Used 121 for a day, then the 151 for a day, 151 did not match the 121 battery drainage (including idle/deep sleep, 1% ~each 6 hours, compared to 2%+ each 6 hours (with new OMAP patches)). 121 is way better in terms of deep sleep/idle, as far as i can see with batterystats and cpuspy anyway. Did not look at the temperatures.

From my perspective, 192 mhz adds a little bit of convinience, since i listen to music. its only a -20 mV lower then 384 mhz that i could detect (with smartreflex), but still its that tiny bit for which i want to use bleeding edge (aka nightly), to see these patches reverted is just music in my ears.

Thanks again for this awesome kernel, love it each day (the gamma feature is awesome aswell)!
[Samsung Galaxy Nexus] paranoid2007:
Heat issues with 154 here too. This didn't happen with Milestone 3.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] CaspaTheGhost:
A flashing we shall go, a flashing we shall go, hey ho hey ho a flashing we shall go...

Lets see how tomorrow goes...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Saying "heat here" doesn't help. I need data, settings, and how can I reproduce it. Without it there is no heat problem, just over usage.
[Samsung Galaxy Nexus] endymion2k5:
Yee hoo Yee hoo and a bottle of rum!

May i ask how those heat issues are detected? I dont like staring at the franco app, any app that can measure it?
[Samsung Galaxy Nexus] jhericurls:
No heat problem here, high 30c idle and 50c+ during gaming.

ondemand (sampling rate 20000, up threshold 98, sampling down factor 20, powersave bias 0) 192mhz - 1036mhz
[Samsung Galaxy Nexus] mazubo:
anyone having issues trying to download the new nightly? I see the "downloading Franco kernel......" however it doesn't reboot and flash, it just hangs there. I'm using paranoidndroid tablet rom; not sure if that's the issue..

Edit: it just flashed, however took about 10 minutes to do so.....

:-D
[Samsung Galaxy Nexus] willl03:
Holy!! Using r154 I'm getting much lower temps than I used to compared to m3 and r151-152. I tested this extensively yesterday to compare m3 to r151-152, all had similar results, but r154...

m3 / r151 / r152 idle (screen on): 36-39*c

m3 / r151 / r152 after an Antutu bench: 55-60*c

r154 idle (screen on): 26-28*c

r154 after an Antutu bench: 38-40*c

It's night and day, no joke

I'm using ondemand 384 - 1.2ghz, aggresive manual UV and 512mhz gpu. All the antutu runs gave between 6.3 and 6.4k.

r154 is 10/10 smooth just like r152, and the MUCH lower temps can only be good. Heat = electricity = battery eh? I'm glad that r154 is similar to r121, my previous fav, real clean and lean. Battery should be awesome

r154 seems to stay in the 384mhz slot a lot more during low usage, no more micro jumping to higher freqs for no reason. I see it on the calibrated volatage page of franco app, and in CPU Spy on m3 - r151-152 I used to get 3-4 sec spent at 1.2 ghz for every minute just staring at the screen, now it's 100% 384mhz

Thank you once again franco, this kernel is stuff of legends!

---------- Post added at 11:28 PM ---------- Previous post was at 11:24 PM ----------

Franco app FC'd a few times before it downloaded the kernel correctly. The kernel was in my download folder, but I did not dare to flash it because of the crash. After a few tries it downloaded w/o FC'ing
[Samsung Galaxy Nexus] MS.:
Where's 153?
[Samsung Galaxy Nexus] franciscofranco:
Somewhere over the rainbow.
[Samsung Galaxy Nexus] mazubo:
lol. Its probably in the same place as that elusive pot of gold!

:-D
[Samsung Galaxy Nexus] Metallice:
I'm also seeing much lower temperatures than r152. Quite significant actually. Around 10 degrees lower on average while gaming and during idle. On 152 I was about 35 degrees idle and 50 degrees at high load, but with 154 my temperature coming out of idle was about 25 degrees and while benchmarking it never got above 45. Great stuff. These low temps mean good things for extreme overclocking :D.

(Lazy 192 - 1228 for 152 and 154)

---------- Post added at 08:28 PM ---------- Previous post was at 08:14 PM ----------

Having one other issue other than the custom undervolting problem. For some reason on 154 my SR voltage for the 384mhz slot is WAY higher than normal. Usually SR calibrates to 886mv, 1025mv, and 1050mv. Now its setting them to 886mv, 1025mv, and 1278mv.

From testing I've determined that I can run 384mhz GPU at 950mv before my framerate dropped, so 1050mv was a very reasonable calibration. 1278mv, however, is overkill.
[Samsung Galaxy Nexus] andrew53517:
Oh yes, agreed!
[Samsung Galaxy Nexus] franciscofranco:
Mine calibrates a lot lower and I use 512mhz, so I dunno :/
[Samsung Galaxy Nexus] emerica243:
Whats the difference betwen flashing the 300ghz gpu or the 512mhz gpu? Im using hotplug governor i just want good batt life
[Samsung Galaxy Nexus] Serious_Beans:
If you want better battery get the 384gpu version. The difference isn't that significant but you will save more battery on the lower clocked gpu.
[Samsung Galaxy Nexus] javi3k:
hi im king noob about kernel i used franco m3 and some nithigly before was greeat but never try to do uv, since i dont have the knowledge to do it, idk how much volt to drop and if just freq or core, if not too much to ask, i just want to see like a standard uv so i can star testing i know all cpu are different but at least a point where to star
[Samsung Galaxy Nexus] Emilius:
Start here Galaxy Nexus Undervoltage Tests
[Samsung Galaxy Nexus] javi3k:
ohhh very nice thank you very much :3
[Samsung Galaxy Nexus] Metallice:
I fixed it. Now calibrates to 1038mv and working great.

In opp4xxx_data.c -

/* SGX OPP1 - OPP50 */
OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 153600000, OMAP4460_VDD_CORE_OPP50_UV),
/* SGX OPP2 - OPP100 */
OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 307200000, OMAP4460_VDD_CORE_OPP100_UV),
/* SGX OPP3 - OPPOV */
#ifdef CONFIG_OMAP_GPU_EXTRA_OVERCLOCK
OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 512000000, OMAP4460_VDD_CORE_OPP100_OV_UV),
#else
OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 384000000, OMAP4460_VDD_CORE_OPP100_UV),
#endif

Basically changed the 384 to use OPP100_UV instead of OPP100_OV_UV
[Samsung Galaxy Nexus] jeetS:
Been flashing every nightly since the hundred teens. Much love for this kernel, works well with the app.

Noticed some faster battery drain than normal with the past two nightlys, heres hoping 154 is back its legendary status
[Samsung Galaxy Nexus] unity04:
Just flashed 154, noticing an increase in performance and speed. :)
[Samsung Galaxy Nexus] javi3k:
one question so i just uc cpu freq and do a auntutu bech test if i dont get freeze that mean is good or there is another test just to be sure
[Samsung Galaxy Nexus] opethrocks:
I posted earlier that the latest nightly was making my phone run hot. It seems i posted a lil hastily. Now the phone runs much cooler, it barely get over 120 degrees with heavy use like loading 5 consecutive websites. Maybe i didnt give the kernel time to settle in properly. Im running ondemand 192-1228 no hotplug. Earlier i was running interactive with the same freq and no hotplug, will test batt life tomorrow. Thanks for the killer kernel, franc tha tank!
[Samsung Galaxy Nexus] Metallice:
Found something interesting... if you look in voltage.h in mach-omap2 you can see that the phone is limited to a minimum voltage of 830mv. When I lowered this to 700, SmartReflex calibrates my 384mhz frequency to 770mv instead of 830mv. Running just as stable as before. :)
[Samsung Galaxy Nexus] Serious_Beans:
Where is that file located exactly?
[Samsung Galaxy Nexus] morfic:
yeah OV_UV is not needed until higher speeds
[Samsung Galaxy Nexus] morfic:
https://bitbucket.org/franciscofran...e9aa9b26/arch/arm/mach-omap2/voltage.h#cl-180
[Samsung Galaxy Nexus] franciscofranco:
I remember messing with the limits before and somethings fishy about decreasing the minimum limit, I just dont remember why.
[Samsung Galaxy Nexus] morfic:
data drops if you lower core
[Samsung Galaxy Nexus] franciscofranco:
Exactly. I might try to reduce the mpu limit and see what goes.
[Samsung Galaxy Nexus] Metallice:
Nevermind. Morfic beat me to it.
[Samsung Galaxy Nexus] Metallice:
Well I didn't bother lowering core or iva since SR calibrates mine to higher values than the minimum anyway. Lowering the MPU min to 700 has been working fine so far for me.
[Samsung Galaxy Nexus] franciscofranco:
Yeah thanks for bringing it up, might be a good idea for testing in the next nightly.
[Samsung Galaxy Nexus] nklenchik:
Gonna try disabling SR for the first time in a while tonight and uv while I'm sleeping. We'll see how this goes :D
[Samsung Galaxy Nexus] BrUhNiGGs:
Same with me. Just wish the manual voltage values could be applied at boot.
[Samsung Galaxy Nexus] morfic:
Just create an init.d script that echoes the values to the right sysfs location.
[Samsung Galaxy Nexus] yoshi161:
My CPU temp. doesn't change on r154.

screen on idle 37-42*C

screen off idle under 30*C

heavy use 55-65*C

Now, I'm using aokp m5 rom.

I tested below combinations before, but no difference.

AOKP m5 + franco m3, r152, r143, r135, r121

LiquidSmooth 1.35 + same as above

CM9 nightly20120501 + same as above

I'm stuck now.
[Samsung Galaxy Nexus] Meannekes:
much lower? how does it come? did you lowred your min. mV limit?

it jumps between 1063 an 886 mV here.

something that is confusing me is, in your app,

MPU jumps every second from 384mhz/840mV to 1228mhz/1270mV an back every second.. (SR on, 384-1228mhz, interactive & ondemand tested)
[Samsung Galaxy Nexus] Serious_Beans:
Oh so I have to compile the kernel with those values edited? Crap. Too much work >_< I'll just UV myself. lol Thanks for the reply though Morfic!
[Samsung Galaxy Nexus] qballe:
app in background ? some service up ? ;)
[Samsung Galaxy Nexus] drawde40599:
Was getting temps over 62° c on everything after 135 I think it was 154 temp has not got over 49°c with any and all use: ) thanks Franco!!! Love this one so far
[Samsung Galaxy Nexus] Meannekes:
i think it was a strange bug,

after changing to ondemand and directly back to interactive it´s normal again^^

edit:

Back to nice temps :) GTA3 max. Temp 54°C
[Samsung Galaxy Nexus] The Gingerbread Man:
Sorry to quote myself, just after a quick yes or no is this normal behaviour? The sound control is 95% of why I wanted to use this, the other stuff is just nice extras but not really why I'm using Franco kernel and it seems more permanent and sounds better than alsa.
[Samsung Galaxy Nexus] paranoid2007:
Normal temps for me again on 154 with on demand. High temps occurred with lazy governor.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] jcpq:
For milestone 3.

What is the best configuration for battery life (governor and settings OC/UV)?
[Samsung Galaxy Nexus] joeyfong:
airplane mode
[Samsung Galaxy Nexus] CaspaTheGhost:
Its normal behaviour as the high performance refers to sound clarity etc rather than volume. Volume is dealt with using the option above it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Cheers, thanks for not over looking my post.

Hopefully we could have an even louder volume boost implemented (+5 / +6). Loving the nightly with nice low CPU speed should help with battery life.
[Samsung Galaxy Nexus] ChongoDroid:
Well guys I did it... I bought the OneX

Now my GneX is strictly for testing :D
[Samsung Galaxy Nexus] afterburn:
Just wanted to say a thank you to franco for all the work. I managed for months running the GN completely stock, but a couple of weeks ago I succumed once more to the lure of roms and kernels. Running AOKP M5 and franco 154 now, I have to say it is running flippin' fast, feeling like I doubled the performance while at the same time the battery lasts twice as long. I don't know how you guys do it, but you're doing a hell of a lot better job than Google is. If you want cutting edge technology and performance, you don't need a Google phone, you need an XDA phone!
[Samsung Galaxy Nexus] yyz71:
Hey franco what are the chances of getting 1.5ghz ? I know some phones can't handle it!!! Mine can :)

BTW not all phones are created equally!!

Sent from M5
[Samsung Galaxy Nexus] qballe:
please stop asking , as franco said is planned ;)
[Samsung Galaxy Nexus] leelaa:
I don't see the need for 1.5.

This phone is fast enough.

But I wouldn't mind the option. :)
[Samsung Galaxy Nexus] SleemLDJ:
Getting heat issues for the first time on Franco kernel. Something is wrong with 154
[Samsung Galaxy Nexus] Langduscher:
It would help if you state what you were doing at the time your phone developed "heat issues".
[Samsung Galaxy Nexus] dpaine88:
Can anyone clarify the "Increase Maximum Sound",

I read elsewhere this only works for headphones but don't see it mentioned in the app.
[Samsung Galaxy Nexus] franciscofranco:
Like I said few pages ago: 99% of the users say their device is way cooler than before, so if you're having that problem I need to know what were you doing at the time, what rom, frequencies, governor, voltage, your underwear color, your dogs name etc. Fail to comply with the above and it shall not be treated as a bug or irregularity.

It's for headphones.
[Samsung Galaxy Nexus] Benji1983:
the same here i got 74 degress in franco app :-( (while charging)

42 while screen on

50 on light use

what can i do ?

paranoid android

franco nightly 154

512 gpu

384-1228 MHz

governor lazy

single core mode

fast usb charge

smartreflex on
[Samsung Galaxy Nexus] dpaine88:
My app is just hanging on downloading for the 154-512gpu version....cant seem to download the .zip
[Samsung Galaxy Nexus] loudaccord:
Took me 3 tries... give it a bit.
[Samsung Galaxy Nexus] simensk:
I rebooted my device when this occured and it flashed fine afterwards. :)
[Samsung Galaxy Nexus] Tommy_FIN:
I noticed that lazy governor heats my phone quite a bit. Switched to ondemand and now it's way cooler.
[Samsung Galaxy Nexus] franciscofranco:
r156

* Decrease wi-fi interface voltage

* Change 384mhz GPU OPP to OPP2 for less power usage. This change only affects 384mhz GPU builds

* Decrease MPU smartreflex minimum voltage threshold to 700mV. This change will make smartreflex to calibrate the CPU entries for lower values

* Increase the temperature throttle threshold from 64C to 75C

* Switched back to Ondemand as default. It's still the more balanced governor of all
[Samsung Galaxy Nexus] The Gingerbread Man:
Potential bug nightly 154

Phone won't use 1036 CPU speed. Xda usage, SMS, YouTube, browser, general usage medium to light usage. Interactive governer, no OC or UV. My phone feels nice and cool and battery life definately seems better than stock kernel.
[Samsung Galaxy Nexus] brianisme:
Thanks Franco! Flashing now. Ondemand has been my favourite governor overall.
[Samsung Galaxy Nexus] dpaine88:
The new 156 certainly helped lower the SR voltages for MPU.

My 384mhz slot used to be 840mV and now it is 800mV.
[Samsung Galaxy Nexus] SleemLDJ:
Was just on basic mobile browsing and listening to music at the same time.
[Samsung Galaxy Nexus] BrUhNiGGs:
Going to finally make a switch from interactive to ondemand, and manually UV'd. Let's see how battery life goes today with r156.
[Samsung Galaxy Nexus] Metallice:
830mv was the absolute lower limit so it would usually calibrate 384mhz to 840mv because of some buffer system in SmartReflex; however, if you set the nominal voltage to 840mv it would calibrate to 830mv but never go lower than that. Now my 384mhz calibrates to 770mv, and, I assume, if custom undervolting was working, it would calibrate to 760mv or lower if the nominal is set to 770mv.

EDIT: Or in your case, it will calibrate and buffer to 800mhz, but if you set the nominal to 800mhz (if custom UV was working) it would probably calibrate to 790mhz or lower.
[Samsung Galaxy Nexus] loudaccord:
I've been having that problem for a while... only way it will pick up the 1036 is if I make that the max freq.
[Samsung Galaxy Nexus] leelaa:
Franco, why does the widget not show live stats? It only shows the stats of when I first dropped it in the home screen.

Or is that how it should be?
[Samsung Galaxy Nexus] WesMantooth:
Touch the widget and it will update
[Samsung Galaxy Nexus] isinisterx:
Anyone having battery problems with the browser?
[Samsung Galaxy Nexus] drawde40599:
156???

156 o_O; ) There's always coffee at ur house huh Franco; ) flashing now
[Samsung Galaxy Nexus] Metallice:
Unless your using the conservative governor (which you really shouldn't, testing with nexus s showed no better battery life than with ondemand) that's pretty much how it should look. With OnDemand when it reaches threshold it will ramp up to the maximum frequency, and, once load decreases, ramp down to the lowest frequency it can. Interactive works similarly, but will "preemptively" jump to max frequency coming out of idle if it determines it may be needed. So in both cases it will jump to max frequency (in your case 1228) and then ramp down to the lowest frequency it can, preferring 192 over 384 over 728 over 1036. Therefore its perfectly reasonable to expect little to no usage of the 1036 frequency.

EDIT: Haha for example checking CPU spy it shows that over a period of 6 hours my phone used the 1036 slot for a grand total of 12 seconds :)
[Samsung Galaxy Nexus] loudaccord:
I didn't really think of it that way... good point and thank you
[Samsung Galaxy Nexus] BlindWolf8:
What's the default min CPU? 384? Thanks!
[Samsung Galaxy Nexus] justinjustin234:
hi everybody

im using Franco kernel updater

why do the uv values revert back to the original every time i reboot?

thanks :)
[Samsung Galaxy Nexus] Sveke:
Because Franco tried to make it idiot proof.
[Samsung Galaxy Nexus] franciscofranco:
Yes I have a Nespresso machine :)
[Samsung Galaxy Nexus] drawde40599:
bright

154-56 running great no issues atm, one thing I did notice coming from GOOGLES 4.0.4 kernel and aokp M5 rom for last few days before installing 154, 100% bright is not near as bright as Google's kernel? I usually set phone at 75% on all Franco kernels I only had to set at 50% to.get same brightness on android Google kernel?? I've seen this mentioned few times in thread and tried to search for it but could not really find anything .....
[Samsung Galaxy Nexus] Metallice:
You can either look in the nightly changelogs for your answer or just install the kernel and see for yourself.
[Samsung Galaxy Nexus] tcchuin:
"* Increase the temperature throttle threshold from 64C to 75C"

is it possible for you to add a interface where we can adjust the threshold ourself?

The phone is already very hot running at 64C for long times=x