yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] leets4uc3:
I use the dyninteractive. Works great for me. Lazy is good to. Ondeamand is alright too. If you don't know what you are doing I would recommend trying all or just using dyninteractive. It adjusts for what tasks you do
[Samsung Galaxy Nexus] garu12:
275 384 running good so far. WiFi is solid and no issues. Smooth as hell too. Man Franco you know how to juice this phone keep it up. No idea on battery seeing as it hasn't been long
[Samsung Galaxy Nexus] nikulogical:
Yes dyninteractive is what I've been running but since franco has implementing a lot of things into the interactive governor. I thought maybe I'd try that.

Sent from my PARANOID ANDROID
[Samsung Galaxy Nexus] Controvrsy046:
Just wanted to double check. Should I wipe anything when switching from Trinity back to Franco (r275 looks way to appealing to pass up) or will franco's kernel do its ramdisk magic with just flashing it? I ask because I know you have to wipe /system when switching from Franco to another kernel because of how it utilizes its own ramdisk.
[Samsung Galaxy Nexus] kyokeun1234:
Just reflash the ROM. Just in case

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] osm0sis:
Yeah. Once Franco made interactive the default again I gave it a try and found it so much snappier than dyninteractive. Definitely give it a go, and may I suggest switching your hispeed_freq to 1037000 for an extra little boost. I'm also still convinced 230MHz runs a bit more smoothly with a voltage of 825mV (or 840mV, but then it runs higher than SR cal'd 384MHz), so you can give that a shot too if you like and help me test. ;)

Edit: I notice Franco bumped up the default voltage for 230MHz to 820mV. :good: Thanks Franco! Running it for awhile to see if I feel it's good or if a bit more would help.
[Samsung Galaxy Nexus] Sayan1987:
Con someone explain shortly each governor?

I mean lazy is for battery life?dyn is for?
[Samsung Galaxy Nexus] osm0sis:
http://lmgtfy.com/?q=android+governors+xda

For dyninteractive search the thread, but in a nutshell, interactive with dynamic tunables.
[Samsung Galaxy Nexus] vrehenriqu:
Version 275 absolutely rocks!
[Samsung Galaxy Nexus] tobitronics:
What kernel settings do you use?

Beamed from my Paranoid Google Nexus 7
[Samsung Galaxy Nexus] Astug:
I'll try this aswell, though are you sure you mean 1037000 or is it 1036000? Thanks.
[Samsung Galaxy Nexus] franciscofranco:
1036800.
[Samsung Galaxy Nexus] osm0sis:
Yes 1037000. :) IIRC it's that because we discovered it needed to be equal to or higher than the target frequency, so 6000 is actually too low.

Edit: What franco said! :D 1036800 would be the "equal to" we overshoot with 1037000. Both work the same. :good:
[Samsung Galaxy Nexus] J-Hop2o6:
Is OnDemand like this with higher priority? Any other governs?
[Samsung Galaxy Nexus] franciscofranco:
No. If it were I would've said it.
[Samsung Galaxy Nexus] lippol94:
This is unbelievable Franco! Your last release just ramped up to first place my smoothest kernel list!

I'm still wondering about possible battery life reduction (expecially due to that boost feature), but I guess only the horses ehm... the time will give me an answer.

Up to now.. Good job man!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] !crazy:
interactive

Interactive is now amazing, but dyninteractive performs pretty bad. Have u you changed priority of dyninteractive too or not?
[Samsung Galaxy Nexus] Fenvarien:
Here is a great guide: http://xdaforums.com/showthread.php?t=1369817

Latest kernel release runs like a beast xD

GNex with franco.Kernel / MiNCO ROM
[Samsung Galaxy Nexus] The Gingerbread Man:
I've never tried messing with governor control stuff before but this with interactive and your latest patches definatly seems to make interactive much much more snappy and responsive which is shown very well scrolling through the panels in your app. Will test battery now but I suspect it wont last as long as with it does with lazy governor. Thanks to this latest release though, great work as normal!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Empty Hand:
Anyone other recommend tweaks, or everything else stock settings?
[Samsung Galaxy Nexus] vrehenriqu:
Just use default settings with dynamic interactive.
[Samsung Galaxy Nexus] dpaine88:
Over on the RootzWiki forum, many of us are running an LTE ROM called Axiom and loving this kernel.

However several users have hinted that the hotplug(cpu1-off) setting on all governors of this ROM is OFF by default...I could have sworn it was ON by default due to this in his changelog:

Could someone please clarify this for me?

EDIT: Maybe I am the one that is wrong...I navigated via Root Explorer to /sys/module/omap2plus_cpufreq/parameters/hotplug_enabled and the value in the file is 0.
[Samsung Galaxy Nexus] Redflea:
There are a lot of us LTE users in here, since Franco's kernel runs in both. (And it's obvious that Winner00's CM9 Kang if the best ROM with this kernel, anyway. ;))
[Samsung Galaxy Nexus] belair56:
Really? :confused:
[Samsung Galaxy Nexus] dpaine88:
App officially purchased, great work here!
[Samsung Galaxy Nexus] mzet:
My biggest problem is that LED notification does not work while screen is on. Is this kernel related or ROM related? I'm afraid, if it is even solvable... (fixed in HW)
[Samsung Galaxy Nexus] ugapug:
It's in the hardware.
[Samsung Galaxy Nexus] grinch247:
do we know what the improvements are?
[Samsung Galaxy Nexus] just4747:
When we say we have battery drain it's because we have battery drain lol. People don't make it up and no one's blaming it on ROMs or kernels. We don't know what causes it. So you may not have battery drain, but some of us do.
[Samsung Galaxy Nexus] mzet:
I was thinking about it now and I don't believe it. Because LED is blinking even when I turn screen on, but it stops when I unlock. So I think, it must be in OS control... so maybe it's ROM related, so sorry for OT :)
[Samsung Galaxy Nexus] aron7awol:
The Nexus One behaved the same way and the CM team figured out how to make it turn on while the screen was on.
[Samsung Galaxy Nexus] el_bori1:
Works great with Axi0m rom. Thanks for the hard work.
[Samsung Galaxy Nexus] sluflyer06:
#10 is just awesome, very smooth and didn't even lose 1% overnight with data and sync on. Thanks!
[Samsung Galaxy Nexus] dpaine88:
+1 running great on Axiom 2.4 for me.
[Samsung Galaxy Nexus] aron7awol:
Francisco: The changes you made in #10 make the phone noticeably faster once unlocked. Good work once again!

I have been noticing intermittent lock screen lag here and there, most of the time being in between when the unlock button is pressed and phone wakes to the lockscreen, and once in a while in between when you unlock and the homescreen is appearing. It seems to be the same lag that existed in 9, 9.1, and 9.2

I think one of the changes you introduced in 9 is causing this lag. I never had any of the lag that people were talking about having with ondemand on the nightlies previous to 8, probably because I was running interactive. But I suspect that something related to the re-writing of the screen_on and screen_off functions introduced these new lockscreen lags.

I flashed back to 8 and tested for a while and definitely noticed the device was waking and unlocking much faster and more reliably. Now I'm back on 10 and def enjoying the speed increase once unlocked, but it's unfortunate that we have to choose between consistent unlocking and slightly less speed, or intermittently laggy unlocking and more speed.

If your goal is to create the fastest and best kernel, I think it's worth testing what you end up with if you revert changes from 9 and create sort of a hybrid 8/10 kernel. I think it would turn out to be super fast in all aspects from unlocking to general usage.

Again, thanks for your work, and I'm really just trying to give you my feedback to help you create the fastest kernel possible.
[Samsung Galaxy Nexus] EddyOS:
Noticed this same lag since #9 on the lockscreen as well, once the phone is running it flies but this lag when waking is a tad annoying! :D
[Samsung Galaxy Nexus] dpaine88:
Battery life is awesome as it is but does anyone know if this kernel is Undervolted by default? I don't see anything about it in the OP.
[Samsung Galaxy Nexus] wilbur-force:
am i ok flashing this over the latest villain ROM ?

(sorry for noob question - been flashing ROMs for ages but kernals are a bit new to me)
[Samsung Galaxy Nexus] EddyOS:
Should be OK (so long as it's 4.0.3). Nandroid backup first of course
[Samsung Galaxy Nexus] atiasdudi:
What rom are you using?
[Samsung Galaxy Nexus] nikosrs4:
as long as I changed to interactive, any lags in lockscreen have gone with no other impact to daily usage and speed and smoothness.
[Samsung Galaxy Nexus] franciscofranco:
Before this release the cpu frequency boosted to 729mhz on touch event, always did. But now I made it configurable and boosted it to 1036mhz.
[Samsung Galaxy Nexus] sotoskawasaki:
Hey guys, I have an off topic question. On Ubuntu 12.10 daily build, there is an iso image for Omap 4 processors. Could we theoretically, flash it on our Nexuses? Or will it be possible in the future? And does that affect or impact us as Franco Kernel users? I mean from Kernel v3.4 the linux Kernel and Android Kernel will be the same thing. Franco?

Heres the link.

http://cdimage.ubuntu.com/daily-live/current/
[Samsung Galaxy Nexus] osm0sis:
I run everything but hispeed_freq=1036800 under interactive Governor Control at the defaults.

CPU I go 230MHz to 1536MHz but I have 1536MHz and 1420MHz undervolted at 1300mV and 1250mV respectively, SR on to handle all other frequencies.

729 screen off max (also default) since we don't want to choke the race-to-idle by putting it too low - a common mistake. This allows the phone to deep sleep more quickly.

Edit 2: Tried a higher hispeed_freq since franco bumped up the inputboost_freq, but nah, sticking with 1036800, since there are plenty of cases where you might not be touching it but load could go up. Probably battery savings over a higher value this way too.
[Samsung Galaxy Nexus] rebretz000:
Running Franco Kernels for the first time in months and so far they are amazing. Incredible battery life. Very smooth.
[Samsung Galaxy Nexus] Culex316:
This kernel has made my phone buttery smooth :D good job franco voce é grande!
[Samsung Galaxy Nexus] osm0sis:
yellowdie, do you have any documentation for how the following work?

# file system speedups
busybox mount -o remount,noatime,barrier=0,nobh /system
busybox mount -o remount,noatime,barrier=0,nobh /data
busybox mount -o remount,noatime,barrier=0,nobh /cache

# Screen on scheduler tweaks (credit ch33kybutt)
echo "1000000" > /proc/sys/kernel/sched_latency_ns
echo "100000" > /proc/sys/kernel/sched_min_granularity_ns
echo "100000" > /proc/sys/kernel/sched_rt_period_us
echo "25000" > /proc/sys/kernel/sched_wakeup_granularity_ns

# Aggressive minfree settings
echo "0,1,2,4,8,15" > /sys/module/lowmemorykiller/parameters/adj
echo "8099,10132,20000,20000,50000,100000" > /sys/module/lowmemorykiller/parameters/minfree

If those "aggressive minfree settings" are from/the same idea as a supercharger script, then they're probably a bad idea.. franco has said a few times they do more harm to memory management than good.

---------- Post added at 09:14 PM ---------- Previous post was at 09:00 PM ----------

franco, there's no way for it to write to /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state anymore?
[Samsung Galaxy Nexus] cruel91:
Seem PGM doesnt work on r275. It did work with the previous r273.
[Samsung Galaxy Nexus] creeve4:
Working fine for me. Did you re-enable it after flashing?
[Samsung Galaxy Nexus] cruel91:
Thanks. I need another reboot to make it work
[Samsung Galaxy Nexus] Culex316:
Pgm works for me as well. If you flashed the kernel via recovery then you have to re enable it
[Samsung Galaxy Nexus] joeyfong:
r275 with interactive is amazing fast!!!!!
[Samsung Galaxy Nexus] yellowdie:
Sure. The general idea came from jakebites' "LeanKernelTweaks" from here: http://rootzwiki.com/topic/17176-kerneltweaks-leankerneltweaks-v160. Some was from here: http://xdaforums.com/showthread.php?t=1808791. And there were a few more threads on XDA mentioning the same tweaks, but I can't find my bookmarks right now. I'll look on my work computer tomorrow and see if I saved the links there.

I'm not sure about the guts of a supercharger script. Those tweaks were recommended by others, but I trust Franco more! So if he think's they aren't good, I'll try it without. :) Also Simms22 recommends only 1024 as the SD read ahead and that 2048 slowed things down a bit, so I'm gonna change that as well.

On another note, r273 has been really good so far! I'm gonna install r275 shortly here, I've just been busy until now. :D Awesome job AGAIN, Franco!! :good:
[Samsung Galaxy Nexus] shahrukhraza:
I'm sorry for this nooby question but how do I install/flash this?
[Samsung Galaxy Nexus] yellowdie:
Do you have a Recovery installed like CWM or TWRP? http://xdaforums.com/showthread.php?t=1592689

You copy the .zip file to your SD card, then choose Install from inside the Recovery. Or you can use Franco's app (the paid or free one) and install it in just a few clicks. It's pretty easy that way. Personally, I like to do it manually, but it's just preference.
[Samsung Galaxy Nexus] shahrukhraza:
Yep. I have cwm. Thanks for informing me!! :D

One more thing... are there any battery life improvements?
[Samsung Galaxy Nexus] yellowdie:
No problem. Download this file: http://goo.gl/SZjyr (Franco's latest r275). Save it to your SD card (I made a folder called 000FLASH so it's at the top of my list). Inside CWM, just install the .zip file--no need to wipe anything. Pretty easy. :) Feel free to let us know if you have any other questions about it. Flashin' stuff is one of the things that makes Android so incredibly awesome!

As far as battery, it depends on what you're coming from. If you're using a stock kernel right now, then absolutely yes. If it's another Franco.Kernel or something like Trinity, then it'll probably be better, but you're already doing well.
[Samsung Galaxy Nexus] shahrukhraza:
Ok I got it! Thanks for the help! And yes android is truly amazing!! :thumbup:
[Samsung Galaxy Nexus] abrcrmdl23:
Maybe I am missing something but is there anywhere to change to I/o scheduler in the Franco app? I really do t want to have set CPU and Francis app controlling the CPU at the same time but I can't find it anywhere and the i/o changer in codename android is broken for me.
[Samsung Galaxy Nexus] osm0sis:
You can do it via init.d script until franco makes an option in the updater app:

http://xdaforums.com/showpost.php?p=31894326&postcount=27582
[Samsung Galaxy Nexus] yellowdie:
Unfortunately, no--not yet. Franco's got it in the works, but not yet. But honestly, I was set on SIO, then I got converted to Deadline--but after spending time on here with 'Franco and Friends' I've learned the speed of Franco's BFQ v4. Now I just leave the I/O set to Franco's default. After all, he's an uber-genius wizard and knows his stuff--so if he prefers BFQ, then

I

prefer BFQ! lol :laugh:
[Samsung Galaxy Nexus] bimasakti85:
Have you try to change the i/o scheduler via set cpu?
[Samsung Galaxy Nexus] abrcrmdl23:
yes I have changed it with set cpu but i was trying not to have setcpu and franco's kernal app running simultaniously. I find for some reason bfq has been lagy for me when I set it to deadline it is way faster.
[Samsung Galaxy Nexus] armisis:
R275 failing to boot, even after cache, and permission clean and fix.

Hangs at Google screen.
[Samsung Galaxy Nexus] osm0sis:
Reflash it via recovery.
[Samsung Galaxy Nexus] TEK112:
How long did you wait? Boot can take 15 minutes.
[Samsung Galaxy Nexus] nikulogical:
New interactive governor + increasing the hi speed freq is smooth and fast but drains way too much battery. Back to dyninteractive.

Sent from my PARANOID ANDROID
[Samsung Galaxy Nexus] Mayday_XL:
The r275 runs very fast but

this is a no go for me. :crying::crying::crying:

Back to r273.
[Samsung Galaxy Nexus] mpokwsths:
Yes, interactive with aggressive settings drains more battery but it is responsive, like stock JB. With dynamic interactive it is less responsive than stock, which is unacceptable for me. Verified many times with 2 GNs side by side.
[Samsung Galaxy Nexus] FingerMove:
No problems here.

I have to say the interactive governor is really smooth and that's what everybody wants. Why does everybody want it? Really simple: you can change your governor if you think it drains much battery life, so dyninteractive is your way to go.

Personally I don't really care about battery drain, since I have an external battery, so I'll stick with interactive ;)

Thanks Franco!
[Samsung Galaxy Nexus] schizophrenia:
but you will be missing the speed that r275 gives.

i am normally not very sensitive on this but i do feel an improvement of speed from 273 to 275
[Samsung Galaxy Nexus] Mayday_XL:
Maybe a little bit faster, but i need CPUSpy.
[Samsung Galaxy Nexus] drawde40599:
CPU spy not working with 275? Search brought up nothing, so I'm it probably
[Samsung Galaxy Nexus] jcmm11:
It'll show you time spent in deep sleep, but that's all. Time spent at frequency isn't shown, in any app that I've tried so far. Franco mentioned this in the release notes for this nightly.
[Samsung Galaxy Nexus] Fenvarien:
Although r275 requires more battery juice compared to earlier nightlies, especially r249, the performance improvements are worth it.

Previously I oc'ed to 1305, now I'm running with 1036 and the new interactive governor with comparable smoothness and performance in everyday tasks (no gaming).

Thank you Franco for this innovative release!

GNex with franco.Kernel / MiNCO ROM
[Samsung Galaxy Nexus] Kurre:
Running 275 with interactive w/ hispeed_freq @ 1036800, CPU 729-1420, screen off 729 and this phone is flying :D idle drain is also quite nice..bad signal, 3g data & sync on equals about 1%/1-2h..not bad at all. Kudos to Franco again :thumbup:

I'll continue my testing for a couple of battery cycles..Maybe those governor tweaks etc aren't really needed..:)
[Samsung Galaxy Nexus] frankyyy02:
Screen Fade Fixed

And

http://xdaforums.com/showpost.php?p=26232661&postcount=16176

Hey Franco

Posted a couple of months ago regarding a screen fade issue on 384 and less min CPU freq. with SR on.

The last couple of nighties has resolved it. Not sure if it's related to the voltage changes you mention in your change log, but I no longer need to have minimum CPU set at 729 to avoid issues.

Not sure if anyone else was experiencing the same issue.
[Samsung Galaxy Nexus] Mayday_XL:
My settings are :

r275

Interactive/ Deadline

230-1036 Mhz

hispeed_freq @ 1036800

384 Mhz Screen Off

Runs smooth. :good:
[Samsung Galaxy Nexus] shawnaye:
I know some of you guys may run your phones for performance. But does anyone have any battery saving setups that they can share?
[Samsung Galaxy Nexus] 11768:
Hi guys, where can I view the changelog for nightly? Thanks!
[Samsung Galaxy Nexus] boki2911:
r275 kernel simply flying

thanks franco- Only one reques, try to fix spu stats
[Samsung Galaxy Nexus] bartolinio:
a few pages back
[Samsung Galaxy Nexus] osm0sis:
No need to downgrade. The thread priority boost was only for interactive governor only, so if you want CPUspy to work just switch to dyninteractive or deadline for now.
[Samsung Galaxy Nexus] Kappa Lamda:
Why someone needs so much CPUspy or any programm like this... If you FEEL that the response is faster, the software runs smoother and battery life is on the same level or even better I dont see the need of CPUspy! Everything comes to what you feel from the use you do and stats by themselves mean nothing...
[Samsung Galaxy Nexus] chrisgtl:
Can anyone recommend a profile for both;

- Ultimate performance (when im inside with charger to hand)

- Battery saving (when I'm out and about all day)
[Samsung Galaxy Nexus] Wynnded:
Some like to have tangible proof of their experience I suppose. Others like to have proof of comments of claims made by those making them.

Hey Franco! Well done once again. I thank you.
[Samsung Galaxy Nexus] billykxda:
Thanks for this. Giving it a try now. Seems like many on this thread are trying similar settings.

I am back to Franco Kernel after about a month on GladDos - a fine kernel that comes with Affinity, my ROM of choice these days.

I sense that Franco Kernel is faster/snappier, but I am trying to determine what the price is in battery life that I am paying.

Always a balance!

BTW: Where is the "Deadline" setting?
[Samsung Galaxy Nexus] yellowdie:
For ultimate I would recommend:

Min: 729

Max: 1305

Max Screen Off: 729

Hispeed_freq: 1305

For battery I would recommend:

Min: 729

Max: 1036

Max Screen Off: 729

Hispeed_freq: 1036

:laugh::good::D
[Samsung Galaxy Nexus] Bl4ck3urn:
or here: http://minooch.com/franciscofranco/Galaxy Nexus/JB/Jelly Bean/appfiles/changelog-n.txt
[Samsung Galaxy Nexus] ChazzMatt:
I got that with the R275 - 512 version. I battery pulled, then it booted OK but I kept seeing "sparklies" on my display. Reflashed r275 -384 and every thing is fine.

512 worked OK for several other releases, but not this one -- for my phone. I'm OK with that. 384 is still very good.

_______________________________

---------- Post added at 09:33 AM ---------- Previous post was at 09:30 AM ----------

Shouldn't that be 1306800/13070000? :confused: See this page...

http://xdaforums.com/showthread.php?t=1367341&page=2781
[Samsung Galaxy Nexus] jericho7:
exact same for me, 512mhz failed to boot the first time after autoflash, turned it on and booted up with the "sparkling" during the boot animation. 512mhz is giving me artifacts and reboots ever since 272, every version before that worked perfectly.
[Samsung Galaxy Nexus] yellowdie:
Two different things. 1305 and 1036 (technically it's 1305600 and 1036800) That's 1.3Ghz and 1.0Ghz. :)

---------- Post added at 10:00 AM ---------- Previous post was at 09:44 AM ----------

Franco, I have a brilliant idea!!! The app needs an 'instant auto update' checkbox so that it autoflashes the new kernel as soon as it posts! I don't care if I'm in the middle of an important business call--when that number changes, I WANT IT INSTALLED!!! :D :laugh: :D

I know my priorities; everything else can wait, I just gotta get my new fix! :good::good::good:
[Samsung Galaxy Nexus] emd2009:
Franco I have a question on how you developed your app.

The tabs, are those fragments created by a main activity? I am a noob developer and have been having trouble understanding how to implement a tabbed interface.
[Samsung Galaxy Nexus] ChazzMatt:
Ah, sorry for my apparent dyslexia. :o
[Samsung Galaxy Nexus] jsn:
+1,

yeah, that would be awesome...

Just let the app flash it in the background whenever there is a newer build, and put a notification in the tray.

This way, you can also restart it by confirming the notification f.i.

Ofcourse, not everyone would like to autoflash newer builds, it should be a toggle in the app.

It would be a nice addition, but I think Franco has other things on his mind which are more important.