yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] DarthPiggie:
This Kernel is impressive my friends. Screenshots posted.

Benches:

Overnight battery life: dropped only one percent.

Note that this was after I opened and closed the camera app.

This is under Roman's fabulous AOKP ROM .
[Samsung Galaxy Nexus] Dr_Ownage:
try this:

for the following instructions ignore the "" :)

1. open terminal emulator

2. type "su"

3. enter

4. type "echo 1 > /sys/module/omap2plus_cpufreq/parameters/hotplug_enabled"

5. enter

6. enjoy :)
[Samsung Galaxy Nexus] ro_explorer:
This build#9 reached a new level of awesomeness.

Great standby power saving, great performance.

I'm not interested in 1.35 GHz because I think a dual core at 1.2 is well beyond any current requirements I could have so .. no BSOD whatsoever. The internet speed was fast enough even before #9 so I can not tell if there was a real improvement.

My setup:

ROM: Bigxie's build6

governor: interactive

freq: range: 350-1200

radio: xxkk6
[Samsung Galaxy Nexus] Jiia:
What's the deal with the franco updater app? It still shows the latest nightly is 196 and it doesn't even show the JB kernels. I didn't pay for this :(
[Samsung Galaxy Nexus] decarre:
Franco wait a official release for update this :)
[Samsung Galaxy Nexus] dandyqb:
JB kernel releases are still considered a test build as the official JB is not even out yet, but it will come and you'll see it in the app and that's a fact. ;)
[Samsung Galaxy Nexus] franciscofranco:
Wtf... thanks I'll go check it out.

And **** it, I'll just add JB kernels to the app, can't stand any more posts/emails/shared posts on G+ asking why those kernels are not available from the app...
[Samsung Galaxy Nexus] rogersnm:
Just to note; the thermal throttling issue I mentioned before on the ICS kernel still exists. My max cpu freq is set to 1300 MHz but the throttle still starts from 1804 MHz when it should start from 1200 MHz:

<4>[ 324.979919] omap_thermal_throttle: temperature too high, cpu throttle at max 1804800
<4>[ 325.974731] omap_thermal_throttle: temperature too high, cpu throttle at max 1600000
<4>[ 326.974761] omap_thermal_throttle: temperature too high, cpu throttle at max 1500000
<4>[ 327.974670] omap_thermal_throttle: temperature too high, cpu throttle at max 1400000
<4>[ 328.974700] omap_thermal_throttle: temperature too high, cpu throttle at max 1300000
<4>[ 329.974700] omap_thermal_throttle: temperature too high, cpu throttle at max 1200000
<4>[ 330.974761] omap_thermal_throttle: temperature too high, cpu throttle at max 920000
<4>[ 332.979431] omap_thermal_unthrottle: temperature reduced, ending cpu throttling
[Samsung Galaxy Nexus] dwang:
With 5.6.2, the governor control settings don't seem to be applied on reboot.

The CPU settings like max CPU are applied at reboot however.
[Samsung Galaxy Nexus] Flukester69:
Love the theme option Franco!
[Samsung Galaxy Nexus] BixBix78:
Ditto holo light + miui = perfect match
[Samsung Galaxy Nexus] Puzzlegirl:
Yes, I get this too, but it's not really a problem as I don't reboot unless I have to. Phone's running fast and smooth and I'm more than happy - thanks Franco :D
[Samsung Galaxy Nexus] mingkee:
Somehow I made script in init.d folder works.

1. Root your phone

2. Get Root Explorer and Busybox from Google Play

3. You MUST install Busybox twice. Run the app and install the commands in /system/bin

4. Go to /etc and create /init.d folder, create a new text file named "99colorcontrol" and edit, and add the following:

!# /system/bin/sh

echo "1400000000 1500000000 2000000000" > /sys/misc/colorcontrol/multiplier

5. change the permission to rwxr-xr-x (owner: read+write+exe; group: read+exe; others: read+exe)

Restart the phone.
[Samsung Galaxy Nexus] franciscofranco:
No need to download busybox, init.d service uses custom busybox included on /sbin.
[Samsung Galaxy Nexus] franciscofranco:
Yeah that seems to be a problem with thermal throttle interface. They built it while having only 1.2ghz as the max freq so it makes sense that it cycles between all the freqs. The fix should be easy, will poke around later today.
[Samsung Galaxy Nexus] spaceman860:
Will set governor control on boot support ondemand soon

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] franciscofranco:
Yes.
[Samsung Galaxy Nexus] The Gingerbread Man:
****, are you being serious?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
You're right, you paid for ICS kernels...:rolleyes:
[Samsung Galaxy Nexus] The Gingerbread Man:
Franco should make a new JB only kernel app and people like that guy make actually have a reason to complain. Sod it let's go nuts and invest to a new company and call it Franco Store and we all pay him for sitting around writing kernels and then because we are all paying him we can have the right to complain we are not happy :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
Seriously!

People need to get out of the mindset of:

"Franco, I gave you $2.00 six months ago, you owe me!"
[Samsung Galaxy Nexus] Puzzlegirl:
I suppose it's a tribute to Franco's reputation that so many people want to use his kernel, but if I was him I would have gone mentally insane by now since so few people are apparently capable of reading the OP all the way through :banghead: Or even read the last few pages of the thread!
[Samsung Galaxy Nexus] The Gingerbread Man:
I was taking the piss, I donated $10, donated being the key word here the other day cos I love francos kernels

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] leelaa:
Here is an amazing idea ive just had.....read back a few pages.
[Samsung Galaxy Nexus] The Gingerbread Man:
My joke failed.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cpom1:
Where is francos special kernel stuff stored in the SD area?
[Samsung Galaxy Nexus] leelaa:
Sorry my friend, my bad i only read the first part as ive seen so many similar comments.
[Samsung Galaxy Nexus] purian23:
Should be located in the ROOT of you SD area - You can change this in his settings.
[Samsung Galaxy Nexus] rogersnm:
After a quick fiddle here's the fix, in arch/arm/mach-omap2/omap2plus-cpufreq.c in function omap_themal_lower_speed(), change:

curr = max_thermal;

to

curr = omap_getspeed(0);
[Samsung Galaxy Nexus] The Gingerbread Man:
Its fine honestly dont worry, I was just trying to have laugh. Don't worry though really it cool :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cpom1:
Thanks man. Do you know exactly which files these are by any chance?
[Samsung Galaxy Nexus] rogersnm:
If you're referring to the app's data it's stored in /data/data/com.franco.kernel/.
[Samsung Galaxy Nexus] mike216:
You know we love you Franco:D
[Samsung Galaxy Nexus] supernova_00:
Franco, could you please revert the wifi drivers again from the ICS kernel builds? The wlan wakelocks seriously drain the battery. Also, do you know if it has been reported to whoever does the drivers about that wakelock?
[Samsung Galaxy Nexus] deathshead:
the Last 3-4 Jb kernels are piss yellow, colors can be tweaked back via the app, but until the device boots it looks bad, the boot anims are nerfed, etc.

fast charge dosent seem to be working either, but Ill try to force it in te.

other than then running great.
[Samsung Galaxy Nexus] superbobup:
Colors work fine for me, and many others, on reboot

Fast charge is not enabled for the JB kernels, it's in the changelogs
[Samsung Galaxy Nexus] cpom1:
I'm talking about the files his kernel may leave behind.
[Samsung Galaxy Nexus] franciscofranco:
Yeah thats how I fixed it too and it works.

Use r196, has stock ICS wifi driver.
[Samsung Galaxy Nexus] simms22:
do you mean the sd file that helps with gaming?
[Samsung Galaxy Nexus] rogersnm:
The kernel itself doesn't leave behind any files per se, the latest kernel ramdisk overwrites a certain power library and the CWM zip overwrites the sdcard binary. If you are referring to the specific files which you can modify to alter certain settings then they are found in a variety of locations in the /sys folder. If you tell me which setting you wish to edit I'll tell you where to find it, I don't wish to list all of the file locations.
[Samsung Galaxy Nexus] osm0sis:
Set them via an init.d script if it bothers you that much - I did. The init.d script takes effect during the Google logo.

I know what you mean, and it's the reason most kernel installers have a cleaner script. Here's a standalone script from when I was checking out other kernels. Don't recall where I found it. Flashable via cwm. I used it between going from Trinity to Franco to be safe.

#!/sbin/sh

# clean modules
rm -rf /system/modules
rm -rf /system/lib/modules

# clean boot sound
rm -f /system/media/audio/poweron/PowerOn.*
rm -f /system/media/audio/poweron/poweron.*

# clean CMPlus stuff
rm -f /system/etc/cmplus.conf
rm -f /system/bin/cmplus
rm -f /system/bin/list
rm -f /sdcard/cmplus.conf

# clean Popcorn stuff
rm -f /system/etc/sysctl.conf
rm -rf /data/cron

# clean LeanKernelTweaks stuff
rm -f /system/xbin/installbb
rm -f /system/xbin/leantweaks
rm -rf /data/leantweaks

# clean Trinity stuff
rm -f /system/bin/fix_permissions

# clean init.d scripts
INITD_DIR=/system/etc/init.d
# GLaDOS
rm -f $INITD_DIR/90logger
rm -f $INITD_DIR/99nexusinit
rm -f $INITD_DIR/placeholder
# Trinity
rm -f $INITD_DIR/95dimmers
rm -f $INITD_DIR/98tweak
rm -f $INITD_DIR/99complete
# SG
rm -f $INITD_DIR/98_startup_script
rm -f $INITD_DIR/99_startup_complete
# Air
rm -f $INITD_DIR/89airtweaks
rm -f $INITD_DIR/98airtweak
rm -f $INITD_DIR/98airtweaks
rm -f $INITD_DIR/99airtweaks
# CMPlus
rm -f $INITD_DIR/98cmplus
# CM Default
rm -f $INITD_DIR/00banner
rm -f $INITD_DIR/90userinit
# franco
rm -f $INITD_DIR/13overclock
rm -f $INITD_DIR/00turtle
# Popcorn
rm -f $INITD_DIR/99sonic
# Lean
rm -f $INITD_DIR/99leantweaks
# Jame Bond
rm -f $INITD_DIR/007tweaks
# miscellany
rm -f $INITD_DIR/99nstools

# clean kernel setting app shared_prefs
rm -rf /data/data/mobi.cyann.nstools/shared_prefs
rm -rf /data/data/aperture.ezekeel.gladoscontrol/shared_prefs
rm -rf /data/data/com.derkernel.tkt/shared_prefs
rm -rf /data/data/com.franco.kernel/shared_prefs
rm -rf /data/data/com.liquid.control/shared_prefs

Edit: flashback7 pointed out this was from the GLaDOS thread, so here's a link back for credit - Under Switching Kernels;

http://xdaforums.com/showpost.php?p=21232559&postcount=2

[Attachment removed. The script can still be downloaded from the above link.]
[Samsung Galaxy Nexus] mike216:
Donation sent out to you franco. Appreciate you bud!
[Samsung Galaxy Nexus] mike216:
So how do you think battery life has been on 512 compared to 384. I think its hard to tell I also need more time to come up with a better guess. I've been a real kernel junkie lately :D
[Samsung Galaxy Nexus] :
I have been using the kernel preparation zip from Glados thread when I go between different devs kernels...

I'm using the 216 with the 384 gpu. My current settings are 1200-700 and 350 screen off. Butter!! I've been flashing and testing various kernels since JB was available for toroplus. :cool:idk if Franco has anything in his kernel that improves signal but I swear i get a slightly better signal on this kernel. I'm not the kinda person to make requests, but I noticed the themes for the updater.. It would be really cool to have a solid black theme.:D But like I said I'm not a request person. Really appreciate all you do Franco! Definitely one of the great kernel Gods of the Nexus. Gonna give the 512 gpu a shot.:D:D
[Samsung Galaxy Nexus] sago62:
I returned today after few days to Franco.kernel .... I hoped it solved the problem of loss of settings on reboot ... nothing! for you?
[Samsung Galaxy Nexus] laureanop:
The difference is negligible , at least with normal use. On a related note , the linaro version doesn't perform as well IMO

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] superbobup:
For anyone that knows (maybe you, simms or Franco?) Would the governor settings not stick on boot if they are not in range? For example, I think simms said the smallest value for sampling rate was 30000. So would setting it lower cause it to reset to default thus making people think it doesn't set on boot?

Just a thought...
[Samsung Galaxy Nexus] simms22:
if 30000 is the minimum, and you set 15000, as soon as you leave where you entered the 15000 itll change back to what it was before.
[Samsung Galaxy Nexus] Hanny:
oh hell, sorry franco for making a false report!

it is the derp of latest superuser app/binary by chainsDD, and the cause should probably be the new JB SDK of your app.

PGM nexus was not working on boot as well and i was like wtf

switched to SuperSU and everything works fine! even with the thermal thottle turned off checked.

and fyi, chainsDD's superuser is also giving issues on JB related things like stock screenshot weird su prompt and stuffs not sticking on boot. franco you may warn your users somewhere and recommend them to switch to chainfire's for now! :)

sorry again and thanks man! you're the best.
[Samsung Galaxy Nexus] franciscofranco:
I just added back FastCharge to my local build because my idea failed. I wanted to increase the mA that the USB port receives(I did that to the Note and the SGS3), but after few hours of search between files I couldn't find a single notion of that. I think the mA values might be defined in the battery chip or something... I can only find registers and registers :(
[Samsung Galaxy Nexus] Culex316:
Dude I was having the exact same problem with pgm nexus not starting on boot thanks for confirming I also installed SuperSU and everything is hunky dory
[Samsung Galaxy Nexus] derPianist:
So if we are using Franco Kernel should we all move to SuperSU from Chainfire?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
Rolling back to su binary 3.0.3.2 seems to cure these issues as well, so switching isn't the only option.
[Samsung Galaxy Nexus] franciscofranco:
Don't blame my kernel, blame the su binaries/apks whatever. This has been an issue since ICS shipped. SuperSu fixed most of our initial problems though.
[Samsung Galaxy Nexus] derPianist:
Seriously, i would NEVER think of blaming your Kernel!

Too great to do this. Period & Dayam!
[Samsung Galaxy Nexus] franciscofranco:
Lol it was just a manner of speaking ;)
[Samsung Galaxy Nexus] cgollner:
I've been using the Galaxy Nexus with Jelly Bean and Franco.Kernel. Just awesomeee. I'm like a happy kid :D
[Samsung Galaxy Nexus] Culex316:
Yeah I also thought it was the puta superuser binaries and not your app or kernel
[Samsung Galaxy Nexus] theMaDHakkeR:
I have no issues with chainsdd. Working flawlessly here.
[Samsung Galaxy Nexus] franciscofranco:
I just had the biggest laugh in a good while !
[Samsung Galaxy Nexus] ntorresla:
Wich version are you using pal?
[Samsung Galaxy Nexus] cgollner:
Modaco rom with a test version of franco.kernel
[Samsung Galaxy Nexus] msedek:
Bro im looking for francos app in playstore for the galaxy note and cant find it.. and im fearing you wont keep developing for note..

I just bought my note... flashed a stock gb rooted, flashed cwm via mobile odin... downloading at this very moment cm9 and and only need francos app to get francos kernel+cm9 wich its what i run in my gnex for the best experience..

If i cant get francos kernel on my note FML D:
[Samsung Galaxy Nexus] Sierra8561:
I'm on jellybelly 2.4 love it and just made it better with my first franco kernel
[Samsung Galaxy Nexus] mrfantastic:
Hey i have a question im assuming its something i did wrong with installing the kernel or using the updater app but i downloaded the r216 kernel and ony did a couple changes upped the cpu to 1300 did the trinity contrasts. Then used the changed the power mode to music, the app froze up and so did the phone when i changed power modes, rebooted by holding down the power button.

Now tho weirdly powerapp doesnt recognize my sd card i get a error saying "Folder is missing or not readable"

Im not sure if its kernel related or not, nothing i did i think should have messed with that. My music is still recognized by other players as well. Does anyone have any suggestions, flash back to stock, or clear dalvik cache

Sorry if this is the wrong section im running paulobriens mcr jr1 jellybean rom, francos r216 384gpu kernel

UPDATE: i was looking with dual filemanager to see what happened, i have 2 different places with sd storage on under /sdcard and also on for /storage/sdcard0

2ndUPDATE: Reading up on this it looks like jb partitions sdcards differently? when i installed the kernel and rebooted before anything started up i got the "Android is upgrading" and it started optimizing all my apps really weird. Im assuming then that it recognized /sdcard and /storage/sdcard0. Anyone else have similar issues?
[Samsung Galaxy Nexus] CADude:
I think some of you guys are experiencing problems because you're not using a ROM pulled from the JB source code but rather a preview pulled from an existing ROM image and you don't know what you're doing.

To anybody who wants to use JB with Franco's Kernel and isn't very experienced: Hold off on JB until we get a proper ROM pulled from the source code, and then start using Franco's Kernel for JB.

Only the pros should be using Franco JB right now, to make things easier for Francisco.
[Samsung Galaxy Nexus] cgollner:
Disagree... I think we are all enthusiasts here, hence we all want the newest exciting stuff. Also, Francisco disclaims any responsibility for damages or problems and therefor no one is making things hard for Francisco.
[Samsung Galaxy Nexus] mrfantastic:
I should delete my post but i think my issue wasnt with Franco's kernel i think(just guessing) is after i flashed the kernel and rebooted it was the optimizing of apps then some apps recognized the new /storage/sdcard0. My phone is running ok otherwise a lil hot at the top by all my apps seems to be working fine. Im not sure how this will effect flashing later on, which sdcard would i flash from would be the main question.

sorry for polluting the thread with my question/call for help/info tho lol
[Samsung Galaxy Nexus] simms22:
you probably should stay away from Franco JB for a bit, since rom source isnt out. it would make things much easier for Francisco. let us pros handle it, until its safe that is :cowboy:

just teasing. anyways, ive seen pros experience problems too. but its safe, even for a non-pro to enjoy :)
[Samsung Galaxy Nexus] TEK112:
Until the filesystem corrupts and bootloops at the Google screen or loses its nav bar. A lot of things can and have gone wrong for those less savvy. Especially if you bring all of the kernels into it and the su issues couple with nandroid that won't restore.

I feel that only those that know what they are doing should mess with JB until source is released. Funky things can and have happen.
[Samsung Galaxy Nexus] ntorresla:
Monaco don't have jb

Saludos desde Ecuador
[Samsung Galaxy Nexus] simms22:
and when i walk out the door of my home, i might get struck by a meteorite. funky things happen all the time. and when rom source gets dropped into aosp, funky things will still happen. imagine that, the same rules will apply. filesystems will still get corrupted, bootloops will still happen, and people will still be losing their navigation bars. but thats why we are here. if you werent willing to take those chances, i wouldnt be writing you a response. and thats a reason why i am here too, to help out those less savvy. maybe they will learn something, and grow. then teach somebody else. and so on. by its nature what we do here has risks, but most the time issues arise, they are from user error and easily fixable. instead of denying somebody a leaning experience, help teach them, so that they can grow too.
[Samsung Galaxy Nexus] franciscofranco:
r217 is out:

* Refactor all the frequencies to be multiples of 38.4

* Fix a bug into OMAP's thermal control thanks roger for finding it

* Add back FastCharge

* Tweaked Ondemand settings

App update v5.7

* Add support for Galaxy Nexus Jelly Bean kernels - only Jelly Bean rom users will be able to download the appropriate kernels

* Ondemand Governor Control now persists through reboots if the set on boot option is ticked

* Lots of fixes and bug fixes from old code

App will be up when Google accepts the update into their market
[Samsung Galaxy Nexus] mike216:
I'm glad your a young man franco, we have years to look forward . :D ahh you probably graduate and move on to make millions. I'm joking as long as its fun you'll be developing for years to come
[Samsung Galaxy Nexus] bigeyes0x0:
@franco: Can you move /sbin/busybox to /sbin/bb/busybox like imoseyon did, because /sbin is the first in PATH env var. It can conflict with user busybox which is normally installed in /system/xbin. I have seen busybox free app by stericson instead of seeing busybox in /system/xbin it sees your busybox and display the wrong info.

Some user might want different version of busybox than yours with different applets compiled in. I need inotifyd for example which is not include in your busybox.
[Samsung Galaxy Nexus] marceldy:
MCR

if Modaco doesn't have JB, then what would you call this : http://xdaforums.com/showthread.php?t=1738793 ?
[Samsung Galaxy Nexus] dominoes20:
I'm probably missing something simple but I can't find the JB kernels in Franco's App. Most recent nightly I see is 196. Am I missing something?
[Samsung Galaxy Nexus] mike216:
You'll have to wait a couple hours before the update that let's you download JB kernels hits the playstore
[Samsung Galaxy Nexus] mike216:
I've been testing 217 and was thinking it felt great and battery life felt good. I then realized I was still OC at 1420. What a pleasant surprise
[Samsung Galaxy Nexus] :
Mine updated about 10 mins ago. I grabbed kernel from op when it dropped. Running great. Your kernels run great fast..smooth..but battery is always my #1 aim. Seems I have better luck im idle with your kernel also. 216 burned a very very minimal on idle. Can't wait to see what this baby does when I wake up.:cool:Tks for adding the autoflash, fast charge ...themes..Gracias! :D

★Toroplus/Are-you-jellin-rc1/Franco's r217-384★
[Samsung Galaxy Nexus] xyzulu:
Any suggestions for replacing the Glados boot animation that installed with the JB Glados kernel? I've installed #217 now, but the boot animation still remains.

#217 is looking good.. seems more battery friendly than Glados already... granted Glados JB kernel has only been out about 24hrs.
[Samsung Galaxy Nexus] mike216:
Take the bootanimation of your choice and place it in data/local . Doing it this way will keep the bootanimation there even if you flash a kernel that brings its own like Glados
[Samsung Galaxy Nexus] mike216:
Here is a link to stock jelly bean animation. Copy it to data/local using root explorer

http://db.tt/I7Iv7DLQ
[Samsung Galaxy Nexus] hitman818:
Does the 512 gpu waste a lot of battery compared to the 384 gpu?
[Samsung Galaxy Nexus] mike216:
Absolutely No its very minimal if any

sent from my precious nexus
[Samsung Galaxy Nexus] xyzulu:
Very helpful, thanks.
[Samsung Galaxy Nexus] Myster:
I do not know if here is the right place to post but i am having problems with franco.kernel.updater

I donwloaded the latest version but settings do not stick after a reboot. Any help appreciated
[Samsung Galaxy Nexus] YashBhatt:
Same here,I'm on JB#217 and settings won't stick

Plus USB fast charge doesn't work

Never faced any issues with the ICS kernel
[Samsung Galaxy Nexus] theMaDHakkeR:
With #217 + Franco 5.7 and 512 GPU, I'm finally stable @ 1.8Gghz.

Amazing job Franco.

Donation coming your way.
[Samsung Galaxy Nexus] Treatcon:
I noticed the color control setting will all be default values after updating to 217 and the 5.7 app, but really the previous settings I had stuck. Only the GUI interface looks to be default values. If you open each setting they are actually saved previous settings. You need to change the settings and hit ok, then go back and change them again and then the GUI interface reflects the correct settings. I can post screenshots if necessary. Thanks Franco for all your hard work, this kernel is coming along nicely!