yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] vivanshah:
http://minooch.com/franciscofranco/Galaxy Nexus/JB_test/Jelly Bean/
[Samsung Galaxy Nexus] mtmjr90:
So I've flashed JB and I'm really liking the stock kernel for now but I also want to test franco's kernels. Is there a way to backup the stock kernel before flashing just so I can revert later?
[Samsung Galaxy Nexus] d0msen:
Nandroid
[Samsung Galaxy Nexus] vivanshah:
you could extract the boot.img from the OTA update
[Samsung Galaxy Nexus] franciscofranco:
Yes you have to cat the the boot partition somewhere else. I dont remember the boot partition though think its mmcblk0p7.
[Samsung Galaxy Nexus] rogersnm:
Thanks for your thorough reply :)
[Samsung Galaxy Nexus] BFirebird101:
Yeah the only decrease in performance I can tell is opening closing app drawer and swiping between app pages in the drawer especially in the widget section. On stock kernel there was absolutely no lag. Just letting you know Franco. Either way I'm glad to already have your kernel on JB since I use your kernels religiously
[Samsung Galaxy Nexus] Flukester69:
Same problem Franco I leave wifi and the handover to mobile doesn't happen and needs a reboot. So I guess I'm stuck on 189 until JellyBean stuff matures.
[Samsung Galaxy Nexus] chakra:
Why is your app showing the most current nightly at 196??
[Samsung Galaxy Nexus] franciscofranco:
Maybe the newer radio fixes that for you.

Because I dont want to get 1 star ratings based in test kernels that are not ready for mass usage but rather get feedback here on XDA.
[Samsung Galaxy Nexus] Flukester69:
Ya I will try that later tonight I guess. It's aggravating me to heck to say the least.
[Samsung Galaxy Nexus] yyz71:
Smart move:D
[Samsung Galaxy Nexus] Razer(x):
Do you see any improvement using this kernel over JB?
[Samsung Galaxy Nexus] franciscofranco:
If nothing fixes it Im inclined to say that you have an hardware malfunction.
[Samsung Galaxy Nexus] slayp00n:
This kernel with JB is the fastest my phone has ever been, it is insane. faster than ios faster smoother then anything I have ever used. It is what ICS should have been. WOW...

FRANCO EXCELLENT WORK!!!

p.s. any chance of a 1700+mhz step?
[Samsung Galaxy Nexus] BFirebird101:
*In other news, a fire broke out at a home today after their phone apparently exploded causing severe devastation*
[Samsung Galaxy Nexus] :
Fastbooted r201 about a hr ago or so...Running good on toroplus.:D
[Samsung Galaxy Nexus] BFirebird101:
Franco what exactly does flashing the 201 boot image do and can it be done through the phone
[Samsung Galaxy Nexus] 15israellai:
Wait, how did you find out I ride a bike to school? Have you been following me?! Seriously

Blazing on my Nexus Prime
[Samsung Galaxy Nexus] franciscofranco:
All the same ****s you can do with the latest nightlies... although I forgot to push FastCharge.
[Samsung Galaxy Nexus] leets4uc3:
Why do I keep reading the same thing over and over again. "App FCS" "what do I need to flash" ect.

The answers to all of these repetitive posts are out there. Just read the forum or search.

If you start any post off with "I'm a noob", Google it first please.
[Samsung Galaxy Nexus] BFirebird101:
what do I type in adb? Thanks in advance
[Samsung Galaxy Nexus] Razer(x):
Flashing franco on JB right now, will post thoughts soon
[Samsung Galaxy Nexus] bongostl:
I'm confused...Do i need to use flashboot to flash the kernel on jb, or is there a cwm flashable zip?

Hoping i can use cwm, as I'm out of the country with only a chromebook...
[Samsung Galaxy Nexus] Razer(x):
Feeling less smooth than JB and contrast is too high
[Samsung Galaxy Nexus] Misledz:
Tried 201, Changed it to 1229 using NoFrills, Everything worked out great but the performance drop is there. It's starting to lag and hiccup every now and then. no issues with WiFi but compared to stock, this is really taking its toll. Anyone else getting it?
[Samsung Galaxy Nexus] DJ Gx:
Exactly!

Screen doesn't look so good and it is not so smooth
[Samsung Galaxy Nexus] az93civic:
please update kernal app for JB kernels

Thanks:good:
[Samsung Galaxy Nexus] Misledz:
Please read a few pages back, Thanks o/

Like he said, there's nothing wrong, it works perfectly fine, I don't know if it's a little hard to skim a few pages back to what's been said over and over :silly:

To avoid 1 star he hasn't uploaded any JB kernels onto the app. It works fine after flashing his kernel. Just use SetCPU or NoFrills to 1229 and it won't crash, it will set the kernel SU permissions properly.
[Samsung Galaxy Nexus] meanwhile:
Franco, app crashes when trying to move away from initial window. Granted running jb, with stock kernel.

I'm in missing something?
[Samsung Galaxy Nexus] SpOuK-3-:
CPU speed on boot

@franco ...

Installed the JellyBean version of your kernel ... CPU speed settings and Governor are don't stick on boot ...

I'm rooted with busybox installed ... Is this a known issue ... I know that the kernel is only a couple hours new ...

Thanks for the help. (BTW, was working OK on ICS)
[Samsung Galaxy Nexus] BFirebird101:
Flash 201 kernel
[Samsung Galaxy Nexus] Misledz:
Just use something like NoFrills and set it to 1229 & "Set on boot" then you're good to go.
[Samsung Galaxy Nexus] SpOuK-3-:
Well I'm using franco app to change those kernel options ... I don't want to use another app ...
[Samsung Galaxy Nexus] Misledz:
Well it's free. not like you're being paid to use NoFrills lol

Besides JB is a pre-release with tons of bugs not yet mentioned, can't blame franco for all of it.
[Samsung Galaxy Nexus] SpOuK-3-:
Yeah, I know ... But if there's an issue ... franco need to know about it...
[Samsung Galaxy Nexus] Misledz:
It's been addressed in over the last 10 pages bro, Don't worry, he got this. :good:
[Samsung Galaxy Nexus] grizzjr1:
He has already addressed this, he can't find a way to make it stick. When he does he will let us know.
[Samsung Galaxy Nexus] Flukester69:
Yeah the radio does seem to fix the problem. I have left wifi range 3 or 4 times now and it has gracefully switched to mobile data. Worked flawlessly on 4.0.3 roms it was only until I moved to 4.0.4 and a certain time of franco kernels (like nightly 150 or something) that the problems started happening.
[Samsung Galaxy Nexus] Misledz:
Tried flashing Radios? that may be the counter fix for it. XXLA2 works fine for me, Perhaps the new one posted might work for you. Kernel normally just affects drivers. Doubt the radio issue is kernel related
[Samsung Galaxy Nexus] lortay78:
Couldn't get my phone to charge with newest JB kernel. Just thought I'd mention that. May have been a bad flash.
[Samsung Galaxy Nexus] Hanny:
hmm like everyone is tasting jelly bean :p but my ice cream hasnt melt yet (or in other words im not patient enough yet to back up 340 apps)

report regarding r200-ICS on ICS rom (upgraded from r196)

apart from those new JB features franco included in his changelog, here are something else :D :

contrast settings are fixed - the contrast values now apply immediately after echo command. therefore before franco releases an app update, a simple tasker run shell with root can also do the job :)

default governor changed from wheatly to interactive - im not sure about the intention of this, maybe make ensure the stability? but personally i like the new interactive so much ;) now we have wheatley for ultra performance so why not let the interactive do a smart-balanced job between performance and battery!

and after these here are some feedbacks after using for a shortwhile:

unlike the JB versions 200 and 201, 1228mhz is stick correctly.

again unlike the JB versions, franco app is running correctly without the assistance of third party set cpu apps.

wifi driver is quite cool. regarding signal strength, it is similar as before so by far i feel good with a new driver which no disadvantage can be discovered yet :)

oh but however the overvolt voltage bug of 1536 and 1651 hasnt been fixed yet :(

1536mhz is using the same voltage as 1651mhz as displayed on franco's app! so i assume some battery juice is wasted on the 1536 slot.

and thats it! :D r200-ICS running cool on ICS and i think i will soon feel the extra fixes from google and samsung very soon! thanks alot franco and cheers!
[Samsung Galaxy Nexus] SpOuK-3-:
Ho! my bad ... sorry ... Tried to read a couple page ... Missed it ... So, life's good ... :)

Thanks! for the answer, my bad!
[Samsung Galaxy Nexus] Rovian:
Is there a way I can restore back the stock kernel? from the JB zip files maybe? I couldn't find it though..
[Samsung Galaxy Nexus] SpOuK-3-:
You can reflash the boot.img from your nandroid or from the zip file.
[Samsung Galaxy Nexus] Flukester69:
Regardless, it started working after I put the radio on. When I had the data drops, I went in and out of range of wifi and it would result in gray bars. Disabling wifi outright did nothing as mobile data was flickering between 3G and 4G and stayed gray (usually solves problem though). I rebooted the phone and mobile data came back right away. Re-enabled wifi and went back into wifi range and it connected. Walked out of wifi, same problem again. Repeated the above with the new radio and it hasn't happened yet. So god knows man..
[Samsung Galaxy Nexus] Rovian:
Thanks man, I just flashed the stock kernel itself.. found it on the JB thread. :)

I really like Franco though and wanted to try it out, found few bugs here and there, I'm sure he'd fix them up in no time.
[Samsung Galaxy Nexus] BFirebird101:
What thread is this? I'm sticking with this kernel but I would like the stock kernel for safety reasons
[Samsung Galaxy Nexus] franciscofranco:
Yes I will fix them. I'm gonna play a bit with 4.1 though, haven't tried any of the new software.
[Samsung Galaxy Nexus] marshall39:
What I really do love in your kernel and app is the WI-FIPM_FAST , it's the only way I guess to be able to stream music when screen is off, thanks for this :o
[Samsung Galaxy Nexus] nodstuff:
Roughly 24 hours since JB was announced and already there have been two releases.

Legendary stuff Francisco!
[Samsung Galaxy Nexus] Moz007:
192Mhz seem to not working ?
[Samsung Galaxy Nexus] Rovian:
Don't want to upload the Kernel inside Franco's thread, so I'll link the thread instead..

http://xdaforums.com/showthread.php?t=1737849&page=78

Scroll down and you'll see it.
[Samsung Galaxy Nexus] slayp00n:
Evert time I reboot safety_enabled gets set back to 1.

How can I stop this from happening?
[Samsung Galaxy Nexus] rogersnm:
I seem to only be able to get 384, 729 and 1036 MHz freqs :(

Edit: My bad, supersu issue.
[Samsung Galaxy Nexus] Dragooon123:
Just wanted to confirm about your JB kernel, it's the stock 4.1 kernel with your patches applied from your 4.0 branch, correct? Also, do you plan on making a 512 GPU version (is it even required)?
[Samsung Galaxy Nexus] az93civic:
I meant for the downloading the JB kernels and flashing through the app. Just an added convenience
[Samsung Galaxy Nexus] rogersnm:
See this post: https://groups.google.com/forum/#!topic/android-building/pf6ppcoWJLc

As far as I know the source code available to developers at this point in time is not complete and therefore is not at the same level as the stock kernel. Also, not all of Franco's patches from his 4.0 branch have been applied (for obvious reasons, there are hundreds).

You could say it's based off of

a

stock kernel but it's not really based off of

the

stock kernel.
[Samsung Galaxy Nexus] emerica243:
Im sure it was probably already answered. But, im using latest Updater app + r201, and set cpu settings on boot isnt working. resets to 1200mhz and interactive
[Samsung Galaxy Nexus] rogersnm:
Yeah Franco is aware: http://xdaforums.com/showpost.php?p=28010434&postcount=21051, seems like there some code in the ROM that's setting it.
[Samsung Galaxy Nexus] SeanHacker:
Just wanted to thank you Franco for putting out all the work you do. It takes a lot to listen to all the repeat bullsh$t day in and day out. :D
[Samsung Galaxy Nexus] mullemulle86:
dont know if its a bug but when i change omap gamma via your app the whole screen turns greens for some seconds

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] grizzjr1:
Yes, I can't agree more. I would have killed someone by now, thanks for your hard work! :)
[Samsung Galaxy Nexus] mullemulle86:
running jb with r201

interactive governor is really bad

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] rogersnm:
You're going to have to be more specific.
[Samsung Galaxy Nexus] marshall39:
+1 I've experienced some lag , but on demand resolved this issue.
[Samsung Galaxy Nexus] mullemulle86:
it was a bit laggy so i tested with linpack

with interactive i have about 24 mflops

with ondemand i have about 82

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] slayp00n:
I get 103 on interactive.
[Samsung Galaxy Nexus] Enhanced:
So I guess the issue isn't really the kernel that's making it laggy, but the governor? Would love to come back to this JB kernel if this is true.
[Samsung Galaxy Nexus] SeanHacker:
Cool! You would get the same result if you didn't post this useless bs dude. You've given no information. You could've just posted the word "shoe" and it would have the same exact meaning.
[Samsung Galaxy Nexus] metalspring:
I just tried popcorn kernel and it didn't lag (kept hot rebooting though probably due to voltage or something like that)

It gave me an idea for a possible quick fix though...

I notice popcorn uses the mkbootimg rather than a full boot.img, I know the mkbootimg basically patches the stock kernel and ramdisk, so would changing your format to mkbootimg work as a temp fix/test?
[Samsung Galaxy Nexus] mullemulle86:
i just checked the cpu speeds.

it seems that interactive gov always stays at the lowest freq.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
You're wrong there. The source is indeed up to date. Latest merged commit is dated to 18 Jun and the kernel shows as compiled on 19th.

Anyway I'm re-doing it from scratch again, I think I can't merge some of my previous patches because they somehow ruin the performance (hint: 4.0.y frequency table).
[Samsung Galaxy Nexus] arzbhatia:
Franco, the Color control values (over 200) aren't sticking when you set them on JB (r201). Hope you fix that soon.
[Samsung Galaxy Nexus] metalspring:
I'm thinking it's the multiplier safety isn't getting disabled that does that...for some reason it's enabled by default
[Samsung Galaxy Nexus] franciscofranco:
Yes I left the safety on, was too tired to make all the little adjustments. All should be ok today :)
[Samsung Galaxy Nexus] rogersnm:
Are you sure it includes all the commits inbetween? I know it has recent commits but I wasn't sure if older code changes not covered by the GPL were intentionally omitted?

I realize the kernel is covered by the GPL however I wasn't sure whether there was some code that counted as an extension rather than a modification. Although upon further reflection it appears this probably isn't the case.
[Samsung Galaxy Nexus] The Gingerbread Man:
Well I'm very impressed with JB and using bigxie rom and tried both r200 and r201. R201 is great and nice to use the Franco app with high performance sound mode again. For such a new OS things are remarkably stable, not a single random reboot. Great work Franco many thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Jikenda:
Hi guys, coming from the trinity kernel.. which is the latest 512 gpu nightly? The highest number I'm assuming? Just want to confirm. Also, I guess I should just ask if I should go with another version?

Currently on latest fitsnugly CM9 nightly skank.

Thanks!
[Samsung Galaxy Nexus] dandyqb:
franco kernel r201 JB / bigxie 4.1 JB ROM

Antutu

interactive - 2501

ondemand - 5426

a bit laggy when using interactive, i'll stick with ondemand for the meantime,.. :laugh:
[Samsung Galaxy Nexus] franciscofranco:
The kernel is under GPL as you know, they are obligated to share all the code that is compiled in the distributed binary, so yes it's completely up-to-date. But I'm pretty sure they will keep pushing more **** for the final OTA.
[Samsung Galaxy Nexus] CMNein:
I'm not sure how "real" these scores are, maybe Franco has some insight? BM apps not fully compatible?

I have thrown everything I can at it, and don't have any lag, despite what the benchmarks are saying.
[Samsung Galaxy Nexus] franciscofranco:
My app also "lags" a little bit on JB. As soon as I used the latest SDK it flies in the screen transitions, so I'm sure most apps will benefit lots as soon as they are using the latest SDK. I can be wrong, but its a strong guess.
[Samsung Galaxy Nexus] Flukester69:
That 201 build does not work for me. I stay at the Google logo but 200 works fine though.

Also the new radio and kernel are working pretty good with no drops yet. Some things are choppy but I expect like always Franco will get it fixed up and like he says once everyone is on new SDK things will get better.
[Samsung Galaxy Nexus] dandyqb:
im still using the old franco updater (5.3.1) but at least it still serve me well despite of some bugs :laugh: i need the color multiplier/omap and OC/UV features :cowboy:
[Samsung Galaxy Nexus] rogersnm:
Franco can you append this onto the end of init.rc to enable init.d script support in future builds:

# Execute files in /etc/init.d before booting
service userinit /system/xbin/busybox run-parts /system/etc/init.d
class late_start
user root
group root
[Samsung Galaxy Nexus] metalspring:
I do think there's something off about your jb kernels as of right now...whether it's the governor or some patches, the stock kernel just seems smoother on the same apps

For instance, with stock kernel scrolling through tapatalk is buttery smooth, with your 201 it just seems so much less fluid almost like it doesn't register all the touches when scrolling...

I really do love your kernel normally but it certainly seems stock is smoother for right now...hopefully a new version from scratch will help
[Samsung Galaxy Nexus] franciscofranco:
Yes I can :)

Yep 100% true. I'm already working on a better version, I was REALLY ****ing tired last night, I only rushed it in to get feedback. This one is looking good ;)
[Samsung Galaxy Nexus] leelaa:
Cant wait, thanks mate :D
[Samsung Galaxy Nexus] The Gingerbread Man:
Sounds like another all nighter too me :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Nice! I was just reading up on the minimum init.d reqs last night so I could disable content adaptive brightness on boot. Only issue I see is that the busybox installer from the market installs to /system/bin ... Any way to make the script inclusive of the different install locations people might have?
[Samsung Galaxy Nexus] franciscofranco:
Isn't it always? *hint* Groundhog Day *hint*
[Samsung Galaxy Nexus] The Gingerbread Man:
I know its a movie but never seen it myself. Any who I'll leave you to do what you do best and hopefully wake up to find 202. Have fun coding and really thanks for working so hard for us to enjoy our phones

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
You can change it to /system/xbin in the drop down :cowboy:
[Samsung Galaxy Nexus] eezdva:
Don't recieve messages or wifi cuts when screen goes off on latest JB kernel ....:-(
[Samsung Galaxy Nexus] Misledz:
Ok so upon using the kernel for the last 6 hours I've come to notice a few things.

The lag only occurs during any sort of reboot. When doing so you get these lag that really puts a number on the phone. After which it tends to just stay there for a while. Opening any sort of app that requires high frequency tends to stabilize it. Upon opening Six Guns just to test compatibility, the lag stopped which was weird. Tried rebooting to see if it was fixed and again it happened. Opened a game again and playing for a minute it became all stable and good. Now the home screen is flawless. Which makes me really confused

JB 201, anyone else opinion is welcome.
[Samsung Galaxy Nexus] nikulogical:
Anyone noticing improvements in battery life with the new builds?
[Samsung Galaxy Nexus] Antob125:
I'm assuming that the JB kernel has the new contrast stuff in it?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Jelly Bean only!

r207 is up. I'll take some time to explain whats here and what changed in a very simple manner.

For r207 I started again from scratch so this is a clean build, but I merged lots less useless patches. The biggest change here between r207 and r200/201 is the frequency table. Now we have 350/700/920/1200/1300/1400/1500/1600 table because I think the previous one was causing that strange lag. Why not lower than 350Mhz? Not yet because I want this kernel to be stable and in an usable state before I think about adding a lower step.

Other than that the kernel is very similar, but I took out a considerable number of patches that I think are useless.

Morfics contrast interface now ships with a value of 0 by default. Previous value is -16 if anyone wants to use it, but I prefer to ship with 0 without forcing users to have a darker screen by default.

GPU is 384Mhz using 304Mhz OPP. I won't be shipping 512Mhz yet, same reason as of the <350Mhz for the CPU.

FastCharge isn't merged as well because I want to try something different first.

All the other interfaces are present: BLX, SoundControl, ColorControl, GammaControl, CustomVoltage (damn you Ezekeel!), Wi-Fi PM toggle, fsync toggle, temperature threshold toggle etc.

Be careful that Franco Power Modes in the kernel side are tuned for the older frequency table, so I'd advise you now to use any of those modes for the current r207 release.

I think I covered it all. As always ENJOY and please ****ing read the thread before asking dumb questions, I really hate it.

The source for this kernel is here: https://github.com/franciscofranco/Tuna_JB_pre1/tree/4.1
[Samsung Galaxy Nexus] CADude:
HAHAHA you are the best developer ever. Thanks a lot.

Just wanted to quote this in case people don't read it.
[Samsung Galaxy Nexus] MistaBishi:
So is there a way to get the Updater app working on JB? I've seen mixed reports of methods to get it to work. It isn't requesting SU access when I open it.
[Samsung Galaxy Nexus] franciscofranco:
It works for me. Make sure you're on the latest kernel version.
[Samsung Galaxy Nexus] Culex316:
Hi Franco,

Was Slide wake support removed from the latest ICS nightly (r200)? I flashed it and it didn't work anymore (app said kernel didn't support it)

Flashed back r196 and it was working again.
[Samsung Galaxy Nexus] franciscofranco:
I didn't remove anything, maybe its not compatible with the newer source or the symbols don't match when loading the module that he injects. I have everything needed for the injection I believe.
[Samsung Galaxy Nexus] MistaBishi:
Going to give it a try now. Might need to reflash SuperSu.
[Samsung Galaxy Nexus] metalspring:
Franco 207+ 4.1jb + gnex= sgs3? I think so...now this REALLY flies
[Samsung Galaxy Nexus] SpOuK-3-:
Thanks for your work franco...
[Samsung Galaxy Nexus] Dragooon123:
What governor is everybody using with r207?
[Samsung Galaxy Nexus] dandyqb:
mine is running normal though im still using the older version (5.3.1), before it FC in JB/franco kernel but after i installed SetCPU, the franco apps suddenly back to normal :D
[Samsung Galaxy Nexus] kmakiki:
Dat speed...dat speed.
[Samsung Galaxy Nexus] loki980:
Not working with JB yet:

http://xdaforums.com/showpost.php?p=27999295&postcount=348
[Samsung Galaxy Nexus] Enhanced:
I assume we just leave it with what the kernel shipped with.
[Samsung Galaxy Nexus] metalspring:
Btw, sio I/o scheduler removed? Only noop and deadline?
[Samsung Galaxy Nexus] Culex316:
[/COLOR]

Even though it's for the latest ICS nightly (r200), it makes sense since the source is based off of Jelly Bean's kernel
[Samsung Galaxy Nexus] kimboinatl:
I'm running Viscious JB V2 plus Franco 207 right now. Seems a bit choppy. I've got it set on interactive and it still hiccups here and there. Kudos for getting this out for JB so quickly!
[Samsung Galaxy Nexus] deathshead:
Is fast charge working?
[Samsung Galaxy Nexus] Neejay:
dude, are you ****ting me?