yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
Nightly #9.1 is up. I hope if fixes the problems reported.

I don't like lower clocks because the phone takes longer to enter idle and some other things I already said, don't feel like repeating it all again =(

No, I don't support older builds.
[Samsung Galaxy Nexus] sishgupta:
Is anyone having an issue with kworker threads using a lot of CPU?

I keep getting watchdog alerts for them.
[Samsung Galaxy Nexus] daandman:
Ok, thanks for the response
[Samsung Galaxy Nexus] mikeacela:
Can someone tell me how the 9.1 kernel is doing ;)

I have yet to flash a kernel on my nexus and i really don't want y phone to freeze ilk in the n1 days. Im running Team kang AOKP milestone 1 4.0.3
[Samsung Galaxy Nexus] ro_explorer:
#9.1 is excellent. For me it was excellent also #9 :) ... maybe someone with the non-waking-up issue should say if it is fixed now.
[Samsung Galaxy Nexus] ourakot:
with 9.1 everything works just fine:) the wake up issue ise solved.great job franco
[Samsung Galaxy Nexus] sam razzy:
Is this is what the change log ? Is that 200 as disabled the fast charge.. after goin through 196 kernel ... my cell goes on decreasing battery while on USB charge... but before wen I had 200b .. it use to charge even while on USB charge .. getting confused... anyone can lead me to change log of nightlies

EDIT:

Everything is okay now... I found answer maself

sent from jElly Belly NeXus PrimE
[Samsung Galaxy Nexus] volapyk:
Interactive/deadline. No OC atm.
[Samsung Galaxy Nexus] gundamboy:
phone is getting super hot and rebooting every 45 seconds after updating to 220@512
[Samsung Galaxy Nexus] jaycarag:
Have you tried checking your CPU voltage? If it's rebooting your phone a lot maybe you under volted too much? Just a suggestion.
[Samsung Galaxy Nexus] gundamboy:
Yeah managed to get in there and adjust it before it rebooted again.

All seems to be working well, still gets pretty hot though :s

Thanks!
[Samsung Galaxy Nexus] P30SiNa:
Using r220-384Mhz. Everything is fine and even better than r217
[Samsung Galaxy Nexus] funkyblue04:
What is the best battery saving governor?
[Samsung Galaxy Nexus] craigbailey1986:
Sounds like your gpu is heating up rapidly. I use the 384 kernel as my phone doesn't get as hot and I can run 1.6. Without any hiccups that way.
[Samsung Galaxy Nexus] craigbailey1986:
Conservative. But you loose performance and it then becomes what's the point of having a super fast phone if your just going to slow it down....
[Samsung Galaxy Nexus] The Gingerbread Man:
Lazy works well

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] THS1989:
OH MY GOD........4.1.1 stock + this kernel

IT IS SOOOO FAST!!! Feels like I upgraded to a Galaxy S3 !!!!!

ICS was such a joke compared to JB. Like Vista vs Windows 7

What's the best governer for a good balance ???

Max- 1305

Min- 384

Max screen off- 384

Interactive

Any better combination ??? I just want the snappiness with good battery life

Btw just got the 2000mah genuine extended battery.
[Samsung Galaxy Nexus] mikeandjaimie:
I'm thinking this is what was happening to me with 217... I had problems running higher freq with constant reboots, and attributed it to the cpu. But now I've switched to the 384 gpu to test for ****s, and giggles and having no reboots at all, even with the higher freq. Think maybe a combination of 512 and >1.5 caused it cause 384/1.8 is running like a dream... Also noticed that abit, of stutter here and there is gone too... Which is weird cause never had a problem with 512 but never been as stutter free/butter smooth as this 384... Either way, hats off to franco for kick ass work as usual.... Running 220 now on the same settings as 217 and not a single reboot.. Plus even my lwp seems to be smoother!
[Samsung Galaxy Nexus] ceredics:
http://androidforums.com/xperia-mini-all-things-root/513426-android-cpu-governors-explained.html

Read this.
[Samsung Galaxy Nexus] ceredics:
You read this too.
[Samsung Galaxy Nexus] Frenix27:
I flashed r220 384 gpu on jelly bean 4.1.1 stock but i have 2 problems:

- Games like fifa12 crash at start

- Colors on my phone tend to purple

Thanks!
[Samsung Galaxy Nexus] TheWhiteBandito:
Hi Franco,

Running r220, trying to get USB out audio to work. This is what I get.

But snd-usb-audio.ko module is definitely there

Any help?
[Samsung Galaxy Nexus] r3ferrei:
Make sure under governor control highspeed_ freq is set to your new maximum as well.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] fronc:
In terminal emulator, go into preferences and uncheck "Verify PATH ..."

Not sure if that will help but it fixed a similar problem with some lean kernel tweaks
[Samsung Galaxy Nexus] Faideelah:
R220 got rid of my wlan wake lock. My battery went down about 4% an hour on 217 but it's down to 1% or less in deep sleep

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] an430:
Lazy gov well fine! Great work!
[Samsung Galaxy Nexus] TheWhiteBandito:
Thanks for the suggestion, but still getting the same error unfortunately
[Samsung Galaxy Nexus] r3ferrei:
I experience this as well. Interactive seems to avoid other speeds except sleep, base and maximum. Under cpuspy I spend very little time in intermediate clocks.

Could this be due to the new "ramp up speed" that is part of project butter?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ceredics:
Cfq or deadline?

I did a search im seeing deadline as best just want an opinion.
[Samsung Galaxy Nexus] splus:
In r220 hispeed_freq parameter in governor control has been changed from 1200000 (was an old value from first version of Franco JB kernel) to 1228000. As a result CPU now spends most of its time at either at 384 or 1228 MHz, and much less time at higher frequencies.

For some reason if speed_freq value is set to a step lower than 1228000 then it will make CPU to use all higher frequencies in a more balanced way.

What I noticed is that for 1036 it needs to have slightly higher value of 1037000, because 1036000 will put the CPU only to 729 MHz. This is probably because the real 1036 MHz frequency is something like 1036.xx MHz, so it's best to set speed_freq value to a 1000 more than the desired frequency.

Hispeed_freq parameter is just an initial higher speed frequency that CPU will jump to when there's some CPU load. And if the CPU load is still high after the CPU goes into this frequency (in other words if this frequency is not enough to finish the job) then interactive governor will put the CPU in even higher frequencies.

On stock JB kernel max frequency is 1200 MHz, and hispeed_freq is 700000.

When speed_freq is set to 1228000 it will use mostly 384 and 1228 MHz frequencies.

Set speed_freq to 1037000 (or previous 1200000) and more higher frequencies will be used.

There's certainly many possibilities to play with min and max CPU values, together with speed_freq to come to the best values. And probably for each max CPU frequency different speed_freq value would work best...
[Samsung Galaxy Nexus] splus:
It shouldn't be set to max frequency, that's not what this parameter is. It's an initial higher frequency the CPU tries to switch to to finish the work, and if thats not enough it will go higher.

After lot of fiddling I found it works best when hispeed_freq is set to 1037000 (not 1036000, it looks like that frequency is actually closer to 1037 MHz so 1036000 doesn't "reach" it). Best performance and battery life.
[Samsung Galaxy Nexus] osm0sis:
Does the Autoflash in franco App replace sdcard like the cwm zip does, or does it leave my original sdcard intact?

On a completely different topic, I added "sleep 2" to the beginning of my colorsettings init.d script to try and time it between the Google logo and the bootanimation and it JUST barely pushes it into the bootanimation, which would be perfect EXCEPT for some reason when they take effect during the bootanimation everything gets TOTALLY messed up looking and even tweaking from in the app seems to not be working the same. Any shorter sleep (0,1) keeps it in the Google logo and this doesn't happen. Any ideas? Any way to fine-tune sleep by the millisecond (decimals don't seem to work)?
[Samsung Galaxy Nexus] garu12:
Props Franco you always deliver. As I read earlier my phone too is heating up much more on 220 384gpu. I don't have it clocked high either on 1305 max. No other mods other than color. Same on Xenon HD and bugless beast. Didn't heat up like this on 217. Nothing drastic but noticeable.
[Samsung Galaxy Nexus] funkdified:
CIFS support

Can anyone please tell me if r220 supports CIFS, and if not is there a module that would enable CIFS support
[Samsung Galaxy Nexus] fronc:
Is it possible to manually set the gamma to 1.1? I feel like that might be the sweet spot on my device but can't find the proper command to change it outside of the updater app.
[Samsung Galaxy Nexus] osm0sis:
I don't think it's possible... but the command is: echo 5 > /sys/devices/platform/omapdss/manager0/gamma

Values run from 5-10, corresponding to 1.0-2.0 (by 0.2), so you'd have to set it to 5.5 and I don't think it'll accept that. Worth a try though? :)

I don't mess with the omap contrast personally due to the way it glitches the display when it changes, and I feel like it increases the saturation too much.
[Samsung Galaxy Nexus] funkyblue04:
OK thanks. What is the best middle ground governor then?
[Samsung Galaxy Nexus] mikespe:
Question: when I update a new ROM (went from jelly belly 3.4 to 3.5) and I go back into the Franco app the gamma settings all say zero. Yet when I click to reenter them they show in the input box? I click done but they still show zero? I cleared the app cache but that didn't work? Do I need to delete the apps data to get it working again? Thanks
[Samsung Galaxy Nexus] garu12:
Your ROM flashed another kernel when you updated. Re flash franco
[Samsung Galaxy Nexus] spaceman860:
Is there a way to keep fsync off after a reboot

Sent from my JB Yakju Nexus
[Samsung Galaxy Nexus] franciscofranco:
I will post every shell command on the second post tomorrow, I took the day off today (saturday).

Good night.
[Samsung Galaxy Nexus] mikespe:
I always reflash franco's kernels...I'm on 220
[Samsung Galaxy Nexus] fronc:
Awesome! You're def entitled to a lazy Saturday every now and then... ;)

By the way, here's something for you to have a look at tomorrow... over on RootzWiki, under the JellyBelly thread, users (myself included) are having trouble with sending MMS when WiFi is on/connected. However, the strange thing is that this doesn't occur on the stock ROM kernel... only when a user flashes your 220 kernel.

Here's a log for you to have a look at (inside a ZIP archive because it exceeded the max filesize). I don't know enough to say whether it's the ROM or the Kernel (sounds more like a ROM issue to me) but maybe you can help shed some light.

Thanks, and have a good night!
[Samsung Galaxy Nexus] osm0sis:
Franco, can I suggest adding a link to this Android governor list to the first posts as well?

http://xdaforums.com/showthread.php?t=1663809

Might save on at least a few noob questions ;)
[Samsung Galaxy Nexus] Necrolust:
Anyone else having huge wifi troubles with Franco kernel? Wifi is fine with the stock jb kernel but with Franco it barely works.

It connects fine but just doesn't actually work properly
[Samsung Galaxy Nexus] hamdroid94:
Can I use this with jelly belly 4.1.1
[Samsung Galaxy Nexus] sway40:
Seriously??? You can read right? If you answer this post, then im assuming you can, which means that just says your being lazy and don't wanna look back at op or the 100 identical questions.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] hamdroid94:
Why so much anger?

Geeees mayne

My bad
[Samsung Galaxy Nexus] sway40:
Not angry, im not green. Just a lil irritating to see the same question more times then I want to count. The info is there for a reason that's it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] hamdroid94:
Then don't count bro
[Samsung Galaxy Nexus] an430:
What is your setting on your nexus??
[Samsung Galaxy Nexus] jeetS:
Its working fine for me.....
[Samsung Galaxy Nexus] splus:
I just switched to ondemand governor and I'm noticing much better battery life than on interactive.

Ondemand was very choppy in first JB kernels but now is quite good. I see with CPU Spy that it's using mostly min and max CPU frequencies, but much less max comparing to interactive. It's as if ondemand uses max frequency only when it needs it and quickly goes back down to min, whereas interactive tends to stay at max for longer times and hence uses more battery...
[Samsung Galaxy Nexus] osm0sis:
WiFi isn't working so hot for me either, but it seems to be a JB issue in general. Disable "Avoid poor connections" under WiFi options and you'll see some improvement with drops, but it doesn't resolve everything.
[Samsung Galaxy Nexus] laureanop:
Lazy, which is a modified on demand, works even better for me

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] Necrolust:
Yeah I had tried that but no dice. It would be completely unresponsive when trying to use wifi until you refresh whatever you were trying to do and even then it wouldn't work all the time.

Back on stock jb kernel and all is well :(
[Samsung Galaxy Nexus] theMaDHakkeR:
If you set the right high speed frequency interactive is the best.
[Samsung Galaxy Nexus] CADude:
Yep, I can confirm that Lazy works best for me too when it comes to battery life.
[Samsung Galaxy Nexus] laureanop:
It does indeed work the best with the phone, but the screen on battery consumption is a bit higher too. I've found the perfect balance of performance and battery life with lazy

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] lukasb9000:
Is it normal to only see change log up to 196 in the app? I'm using 217 right now on 4.1 rom... Where can I see the change log without going through 100 pages every time on this thread?
[Samsung Galaxy Nexus] despard:
The NetworkLocationLocator from Google Map has been creating wakelock, can anybody help me to get rid of it? It's strange i mean i never open the map app.
[Samsung Galaxy Nexus] The Gingerbread Man:
Turn off Google location services and freeze maps until you want to use it

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cyanoviper:
Hi everyone!

I am one of those plagued by the wlan rx wakelock, so i did a little research of my own;

Here's what i (think) i have found out:

1. it does only happen on certain routers

2. it only happens on wireless networks that are maintained by several accesspoints (e.g. i have a wireless lan repeater at home, and the network in my university consists of many accesspoints)

can i provide anything to confirm this? is there hope for a fix? im running r200 so the new wlan driver probably doesnt do the trick =(

Thanks for the awesome kernel franco!
[Samsung Galaxy Nexus] Kas206:
Anyone experiencing lag on r220? I had no lag lag on r217
[Samsung Galaxy Nexus] bookerok:
Which high speed frequency are you using?
[Samsung Galaxy Nexus] Smokuevo:
R220 n r217 512 GPU don't boot on euroskanks cm 10 skank..... didn't try others
[Samsung Galaxy Nexus] franciscofranco:
I know I havent done that yet, my days have been hectic. Hope to do it today.
[Samsung Galaxy Nexus] asapelectric:
color multipliers

I know it's already been said, but we could really use an app for color change. You know, one that changes just like the regular auto-brightness does, but to your preset values. Like when you step out into the sun, it automatically changes to 375/375/375, when you go back inside, changes back to 134/134/215. Somebody already mentioned this for a toggle, but I was wondering if there's a way to integrate this into auto-brightness code. Please, please, please somebody come out with this, would be the best thing ever!!!
[Samsung Galaxy Nexus] The Gingerbread Man:
The problem with values so high values could 'burn in' certain screens. Cool idea though. You could always just use 215, 200, 222 and turn up to 100% brightness. Works for me

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Nope this is better than ever. Check your CPU settings and governor maybe. Make your your not running a single core power mode

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] asapelectric:
Oh, yeah that's true. But that's what the app would be for, to easily choose those values. Not an easy feat, huh? Franco?
[Samsung Galaxy Nexus] Kas206:
Seems Like its running in single core mode. But I can't find anywhere to turn it back on. Anyone know how its done?
[Samsung Galaxy Nexus] The Gingerbread Man:
Use francos power mode to 1st switch to full power, then balanced. Then look into what settings you want

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] maatae:
Hi,

so I've been wondering if I should jump on the franco bandwagon, but I keep hearing that stock kernel is best for stock rom (I'm on 4.1.1)

I care more about battery life and stability over performance, and wanted to get your guys' opinions on how well r220 performs on 4.1.

I'm averaging about 9 hours with 2, 3 hours screen time, everything stock (google now is off,too). I've seen people get around 20 hours on this thread?

Basically I'm asking is stock kernel really best for stock rom (why are people saying this?) or am I safe going with franco!

Thanks!

edit: I should mention I'm using the oem 2000mah
[Samsung Galaxy Nexus] Kas206:
Core 1 is still showing as offline :-l
[Samsung Galaxy Nexus] LNJ:
Set to none and reboot. If that doesn't work, clear data in the app and reflash kernel.

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] theMaDHakkeR:
I'm using 1037000 @ 1.7Ghz and it scales through all the frequencies perfectly. Its quick and easy on the battery.
[Samsung Galaxy Nexus] osm0sis:
Sorry to repeat myself, but I didn't get a response a few pages back:

1) Does Auto flash via the app replace /system/bin/sdcard like the cwm zip does?

2) Applying color settings during the boot animation seems to really mess things up (better explained in my original post), any ideas?
[Samsung Galaxy Nexus] franciscofranco:
1) Nope.

2) OMAP Gamma interface does that. Whats your value in that setting?
[Samsung Galaxy Nexus] osm0sis:
Thanks for answering franco! I only ever had it at 5 in the init.d script, but the issue is still there even when I remove the OMAP gamma line altogether...

All I know is it happens if applied during bootanimation, and doesn't happen if applied before (ie: during Google logo).

Any way to fine-tune a "sleep" command by the millisecond (decimals don't seem to work)?
[Samsung Galaxy Nexus] sway40:
R220 is THE ****, just broke 3hrs screen on time with over 20 hrs on battery. Stock battery clocked at 1.5, barely any wifi and horrible signal (no bars) while at work, which tells me I could've gotten way better. Im happy with this kernel big time, I've got performance and bat life.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Haha had to read that twice, I thought you said 220 is **** and was like :what:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sway40:
Fixed

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sway40:
I used to think I wanna be a superhero or something, nope I wanna be franco, homie got skills.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] momomok:
@franco I remember a while back you said there is a new GPU driver @ OMAP source, but fails to make it working

I wonder if there is any progress?
[Samsung Galaxy Nexus] volapyk:
I'm getting poor wifi performance (bad range and low signal strength) in JB 4.1.x. It's the same with stock kernel, so it's not related to Franco's great #220 kernel. But I'm now using the "Wifi PM_FAST" setting in the Franco app to see if this will improve wifi stability.

Does anyone have experience with this setting and the possible additional battery drain? Any info would be most welcome.

Thanks for #220 Franco. Extra butter on top of project butter, love it.
[Samsung Galaxy Nexus] TEK112:
Search xda using Google. There is a GPS Wi-Fi fix that was posted 7-7-12. Sorry I can't be if more help. Just make sure you flash the correct version for your phone.
[Samsung Galaxy Nexus] volapyk:
This fix is for the Verizon GNex. AFAIK the fix corrects an error that was introduced while porting the GSM firmware to the Verizon version, so it does not solve anything on the GSM version. Thanks for the tip anyway.
[Samsung Galaxy Nexus] CADude:
It only affects Wifi performance when the screen is off so that you can stream stuff better. It's not a big hit on battery and only useful if you depend on Wifi for not having a data plan or do a lot of streaming.
[Samsung Galaxy Nexus] volapyk:
Ahhh...how about when downloading big files during screen off?

Thanks for the info.
[Samsung Galaxy Nexus] franciscofranco:
Thats only to boot JB sources on ICS. Normal JB kernel has all that.
[Samsung Galaxy Nexus] CADude:
Yeah that too. It's basically just to make sure Wifi doesn't go into low-power mode when the screen is off. That's it.
[Samsung Galaxy Nexus] sing1gnis:
What was your min cpu and governor?
[Samsung Galaxy Nexus] Quipper2008:
Sorry guys,

but which one is the latest for JB 4.1.1?

I'm not sure.

Thanks.
[Samsung Galaxy Nexus] xyzulu:
If you are not able to work that out from the title of this thread, or the original post, you really should not be installing a kernel.
[Samsung Galaxy Nexus] derPianist:
Why you don't simply tell him, rather than waste your time by typing something unnecessary.?

It is r220 for Jelly Bean.

via Google Galaxy Nexus
[Samsung Galaxy Nexus] LNJ:
Some people just rather be mean than answer a simple question it seems.

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] Quipper2008:
Thanks.

Its the first day i have the Nexus and its confusing how many franco versions there are.

But now i understand everything.
[Samsung Galaxy Nexus] xyzulu:
Welcome aboard.. I hope you love the Nexus as much as we all do. The current version of Franco's kernel is always listed in the thread title FYI.
[Samsung Galaxy Nexus] sway40:
Ondemand, 384

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
I do not mean to sound rude / hostile / aggressive / what ever but there is so much information around and definitely a clear label of what is what in the thread title. I don't know how much time you spent on this thread or read it all the way through but the amount of repeat questions on most pages here are just crazy or just posts asking such simple things and just so much ****e gets posted than you would believe. Us guys who hang around kind of act as some kind of secondary support giving advice and most of the time its cool really but peoples patience gets pushed with the same questions on a daily basis. I know this thread is now very long and would take 2 weeks to read but if there was a question then try to search on Google or xda. I guarantee if there wasn't so many repeat questions this thread would be half the length, at least.

Any way like I say no hard feelings or hostility meant towards anyone in particular etc etc but I think you get the drift of where I'm coming from which is basicly people don't tend to help them selves by not looking / searching for what they need / want

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jcpq:
In andoird 4.1 (using r220) which the governor for the best compromise performance / battery life?
[Samsung Galaxy Nexus] Puzzlegirl:
Us guys and gal(s) ;) Wholeheartedly agree with you there. XDA Search and/or Google = Knowledge :D
[Samsung Galaxy Nexus] dascjb:
Lazy
[Samsung Galaxy Nexus] kuntau:
I do find interactive with max_freq set to 1036 give me the best result
[Samsung Galaxy Nexus] xyzulu:
As was posted before in this thread, see: http://xdaforums.com/showthread.php?t=1736168 for more information on governors.
[Samsung Galaxy Nexus] Edwrib:
Hi, any plans to add exFat modules?

TY.
[Samsung Galaxy Nexus] franciscofranco:
Just posted all the commands in the second post.
[Samsung Galaxy Nexus] dyndragon:
I know that this thread and Franco isn't here to support other ROMs, but I'm just curious--is anyone trying this on the CM10 nightlies that various folks are putting out and finding that the Franco JB kernel isn't able to boot?

Thanks