yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

They perform voodoo, black magic and mad crazy **** huh? :D go to page 312 of http://xdaforums.com/showthread.php?t=1823671 and read

---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------

Here

Sent from my Galaxy Nexus

---------- Post added at 10:36 AM ---------- Previous post was at 10:19 AM ----------

You can find a governor comparison by having a Google search I'm sure, search isn't just exclusive to xda but how Google got so successful and made our androids ;) About your freezes, which rom are you on? I did see someone the other day saying they were on cyanogen and it wasn't working well with Franco kernel. I'm on stock rom and it performs great, scrolling is so smooth I can flick from one end of play store/my apps/all in one swipe and back up to the top in one. Try a asop rom or stock is my advice

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] KostasR:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

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

Sent with my thumbs using Tapatalk 2
[Samsung Galaxy Nexus] RevengeFNF:
Where can i change Read Ahead on f.ku?
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

You can't right now, you can with a terminal command posted by osmosis a few pages ago or use trickster. Hopefully this feature will be added to next app update.

Sent from my Galaxy Nexus

---------- Post added at 12:16 PM ---------- Previous post was at 12:14 PM ----------

Just had my first SOD in weeks, maybe more, playing music with 192 slot enabled. Could it be part of what we are doing with the tuneables or just bad luck and part of the broken 4.2.1. Funnily enough my music was still playing when my sod happened I only noticed it wouldn't wake when going to check if I had an sms

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I have been using 15/95/.7/45/30/85 for a couple days now and everything feels pretty smooth. I'm pretty sure this was one of the many a and b's we were supposed to test, but if not, my bad. There was a lot of 'em. Still not happy with my idle drain though. Probably app related. Guess its time to figure that out.

Edit:

Just saw osmosis' post about the final round of testing. Guess I was a little late. Time to change timer rate to 15.
[Samsung Galaxy Nexus] Angelakaro:
I suggest you to change your timer rate to 15,i'm having great overall performance with these setting: 15/95/0.7/45/30/85 (by osmosis) i was getting also high idle drain but that was cause i setted wrongly some parameters,i guess,cause my apps are ok and are always the same and they didn't wake up my phone never before
[Samsung Galaxy Nexus] osm0sis:
I think you hit the nail on the head there. 192MHz might be more prone to SODs.
[Samsung Galaxy Nexus] pkgnex:
I'm done testing, and 15/95/.7/45/15/85 is my choice.

It seems a little more responsive, especially when first turning the screen on, than the 15/90/.7/45/15/80 combo.
[Samsung Galaxy Nexus] osm0sis:
And that's interesting because 95/85 should really just be better for battery while hopefully being as smooth as 90/80. Thanks for the help testing. :)
[Samsung Galaxy Nexus] RevengeFNF:
Im testing 15/95/.7/45/15/85 and so far so good.
[Samsung Galaxy Nexus] stevensoaj:
I'm also testing these. Liking it so far.
[Samsung Galaxy Nexus] pkgnex:
I know it's weird... But I'm pretty sure it's not just in my head!
[Samsung Galaxy Nexus] joaquinf:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

So I think we have a winner here, huh?

Row/2048

384/1228 <-- minfreq set to 384 to avoid SOD

15/95/0.7/45/15/85
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

+1

That's a great setup :good:
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Sorry to ask but can some explain to me the measures of times these settings are in reference to???? Ex. Min_sample_time=45000 is equal to how man seconds????
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Those are MICROSECONDS! (EDITED,SORRY FOR MY MISTAKE)

However i agree,the winner is the one posted by joaquinf

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] osm0sis:
:D

Picking winners all around today! I can't wait for the next builds..
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

So 45000 should equal 45sec. ???? If so how does that work out in CPU time if we use the phone for seconds at a time per say, thanks for the replies, just looking for a better understanding as to why the phone is running so got damn smooth :D:thumbup::p
[Samsung Galaxy Nexus] RayGarden:
Can someone please show screens with the "winning" tweaks? :)

Tnx
[Samsung Galaxy Nexus] Robdyx:
Great, let's put this clear for everybody

Max CPU frec: 1228

Min CPU frec: 384 (SOD avoiding)

Governor: Interactive

above_hispeed_delay: 15(k)

boost: don't touch

go_hispeed_load: 95

hispeed_freq: 0.7=729MHz

min_sample_time: 45(k)

time_rate: 15(k)

target_loads: 85

IO Scheduler: row

Read Ahead: 2048 (Can't be set through f.ku YET)
[Samsung Galaxy Nexus] Jar3112:
R: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Sorry, I may sound inappropriate asking this, but are these setting referred to governor control am I right? I searched the topic in order to understand what the talking is about but I didn't find the start of the discussion.. Could someone kindly point it out to me?

EDIT: never mind, above post explained it all XD

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Mevordel:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Did you have auto brightness enabled? Since the music was still going, it sounds like a 4.2 bug where the screen turns off and won't come back on until you pull the battery, not a SOD.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
It is pretty confusing, the way we divide it for the shorthand. The timers are in microseconds (μm) so 45000 is 45 ms which is the same as our shorthand. :) I think that's where the talk of milliseconds got started and confused everyone.
[Samsung Galaxy Nexus] creeve4:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

microseconds not milliseconds. Micro = 10^-6. Milli = 10^-3

45000 microseconds = 0.045 seconds
[Samsung Galaxy Nexus] RayGarden:
above_hispeed_delay: 15(k) = 15.000 or 150.000 ? Normally....15k = 15000 .... but i saw some screens back which had 150000. Just 2 b sure
[Samsung Galaxy Nexus] jjhrrsn:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Its 15000 those screen shots aren't correct I tried it first based off that and ran like poo
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Sorry guys,i'm posting a lot of bullsh**s in the last few days! Before i was thinkin to write "microseconds" but then i wrote milliseconds. This is called "lapsus",from latin :D i'm very sorry,i'll pay more attention to avoid people misunderstanding some important things.

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] whitedragonz83:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Still happy with this setup in the photo
[Samsung Galaxy Nexus] osm0sis:
No.
[Samsung Galaxy Nexus] whitedragonz83:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Default 80000 for both. I don't touch them.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

It was my option C from last night, same values I'm proud :cool:;)

Edit

In fact I'm mistaken someone came up with having 95 ahd instead of 90.

Good team work guys :o:)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] 93fuelslut:
iv downloaded f.ku app, and tricksters kernal mod app, and i dont see where to go to set my frequencies like the screen shots posted.

like what robdyx said-

max cpu freq: 1228

min cpu freq: 384

governor: interactive

well in trickster kernal mod app, the smallest min freq available to choose is 100000, and the max freq choices are 100000, 200000, and 400000 and 600000 and so on.

i can however select "interactive" governor.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I just had a hot reboot, phone was sat idle for 10 mins or so since my last post. Went to proc/ but no last ksmg. I'm confused. So these settings are great but I've had a sod and random reboot and before my phone has been completely stable for pretty much as long as I remember. Before we call this the winner I really think we need a 3/4 days of everyone testing for stability. CPU 1228/192 same as its been for ages, row since it was introduced. Only change is the tunables which seem to now make my phone unstable :confused:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RevengeFNF:
Don't use 192.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Yeah easy to say that but before today its been perfectly stable for as long as I remember, its these tunables I reckon as its the only thing I changed

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Never had sod or random reboots with franco kernel and modded tunables nor with stock ones. I think you have to raise your min freq to 384mhz (I used 192 MHz for test purposes for two days, but i didn't see any change, so i set it again to 384 which gaves more stability because,i guess, cpu has to scale less frequently,i'm not sure about it)

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] bombadier:
Could one of you boffins please explain why Content Adaptive Brightness seems to be the cause of my random SOD battery pull to fix crashes?

Thanks in advance
[Samsung Galaxy Nexus] Wynnded:
Just guessing that if anyone knew what the cause was, I'd like to think that it would have been sorted by now. :)
[Samsung Galaxy Nexus] osm0sis:
Jelly Bean 4.2 is the cause. Thank Google, and then pray 4.2.2 isn't still garbage.
[Samsung Galaxy Nexus] bombadier:
Random factor like a tractor........ Thanks for pointing the finger,fingers crossed
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

They've taken long enough and taken enough heat from the community that I think it should be decent. Maybe not spectacular but at least not crap. One would hope...

Shiny + Franco 361
[Samsung Galaxy Nexus] Mevordel:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

By hot reboot you mean back to boot animation, but not Google logo, right? That means Android framework crashed, not the kernel, so no last_kmsg. It also means 192 is not the culprit. If you didn't my last post, having auto brightness on means it's not a SOD either, but a 4.2 bug. Like you, I'm confused as nothing else changed, but it just recently started happening to me too (like 4 times each yesterday and today), and I didn't change any tunables from the defaults until 5 minutes ago.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RevengeFNF:
2048 value in read_ahead_kb is not working for me. Changed back to 256, and the ui feels much more smoother.
[Samsung Galaxy Nexus] osm0sis:
Where did you get 256 from? That's a very small buffer; the default is 1024.
[Samsung Galaxy Nexus] drnbrk:
Is the new version will not come out now?

Example r362, r363...
[Samsung Galaxy Nexus] RevengeFNF:
I was trying different values and i think 256 is the default from the Stock Kernel..

With 2048, when scrolling the widget section, it becomes very slugish. With 256, its almost perfect. I need to try some more values.
[Samsung Galaxy Nexus] parkson:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

128 is Google stock kernel ;)

256 is your best bet for typical use, 512 if you're a gamer. Anything higher only slows the phone (IMO), yet many say "tests" show it increases performance?
[Samsung Galaxy Nexus] osm0sis:
This is for the N7 but a similar test was done for the GN a few months back:

https://docs.google.com/spreadsheet/ccc?key=0AqRFyVFtJ0vodDF2V2FrYlVSTkhseV9DWjlaRkltRmc#gid=6

The GN results were similar. IO speed increases to a point with higher read_ahead_kb buffer values, then decreases again.

If I recall correctly, 2048 was found to be the sweet spot both times.

Edit: Wrong graph.. I'll try and find the one with 3072, etc.

Here we go, it's from M-Kernel, but results are similar:

https://docs.google.com/spreadsheet/ccc?key=0AqRFyVFtJ0vodHQ0Q3dqa2NWUXBzSG4tRHNqSmwzUFE#gid=6
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

How's this for a funny bug although not perhaps not kernel related, that's if you look carefully youl see what I mean

So apparently my phone is charging, even though I'm in the garden having a cig at 1.41am while not charging at the same time lol

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] parkson:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Looks like USB/charging port issue.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Yeah as in I'm not connected to one haha A reboot should fix it. I was having issues with my USB port before with it not charging, that's till osmosis said to fastboot entire stock rom and it stopped having that issue somehow :confused: This is a new one even for me lol

Edit

Reboot did fix it :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gaich:
Logging disabled in FKU?:)
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

About hot reboots: having them every now and then, every two days or something. Totally irrelevant when it happens: while listening music, or just when the phone is laying on the table with the screen on. Hopefully Google fixes this, not Franco related.
[Samsung Galaxy Nexus] LibertyMonger:
I have never had a reboot or sod using Franco especially the latest one. Never while running Xylon ROM and now over a month on Baked BB7.
[Samsung Galaxy Nexus] Nighthound:
What about the max CPU freq for screen off?

Also just for completeness, what's the recommend TCP congestion avoidance algo? Is it westwood?
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

It isn't a hard reboot though, when you check your uptime the phone doesn't see the reboot. Just the glowing X bootscreen.

SOD doesn't happen on Franco, luckily because my phone is sensitive for it :)
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

The final winner tunables are running perfectly stable here on the GNex of my wife and on my own GNex.

No problems with 192/1228 :good:

I used a lot of gaming, listening to music, web browsing with Chrome, Tapatalk and Repligo Reader (PDFs). Performance and battery life are just amazing, no stability issues at all. :)
[Samsung Galaxy Nexus] marcocsh:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

They are prefect except that I need to set read ahead buffer to 128 for listening to FLACs.:thumbup:
[Samsung Galaxy Nexus] eng.stk:
Yes, 1024 is the safe used by most users (and kernel devs), 2048 if I recall, as you say is "the point".
[Samsung Galaxy Nexus] RevengeFNF:
Benchmarks are one thing, real usage is another one.

With 2048 i feel my phone being sluggish in transitions. The best way to test that is scrolling the widget section very fast. Its simple a no go for me.

After that i tested some other values, and for now i found that 256 gives me the best transition in the Widget Section.
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I can confirm that, with 2048 my phone gets laggy. With 256 it's faster in transitions. It's just how you use your phone what's good for you :good:
[Samsung Galaxy Nexus] supernova_00:
I didn't know exactly which comment to quote since there have been dozens on comments with different tunables but why the just from 30 to 15? I haven't seen anything in between like 20 and 25. We might as well get it perfect instead of just dividing the numbers in half each time for a test, I've seen every other number be tested in increments of "5" except this one.
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

That's true, it depends from personal usage. Until Read Ahead becomes configurable via f.KU I use an init.d script to set it to my taste :)
[Samsung Galaxy Nexus] stevensoaj:
I'm so glad I saw your post. I have been annoyed by the lag when scrolling vertically through the widgets on nova launcher for quite some time. 256 buffer cleared things right up! With no noticeable draw backs so far. Can someone who knows more than me explain the benefits of higher buffer sizes?
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Although 512 is a little smoother to me when opening Google now for example. Using that value now.
[Samsung Galaxy Nexus] joaquinf:
From yellowdie's post

So that's why we've set that value to 30 or multiple of that e.g 30/2 = 15; 30*(3/2) = 45 and so on :)
[Samsung Galaxy Nexus] supernova_00:
Got cha, thanks! So these tunables have been implemented in the latest fku, correct?

Has anyone played with the new IO scheduler options?
[Samsung Galaxy Nexus] joaquinf:
Those are governor tunables and always have been available to tune on fku under frequencies/voltages > Governor control

On the newest version released today franco included I/O scheduler tuning which is a completely different thing and those options are available under custom kernel settings > io scheduler tuning

And no, i haven't played with that yet. I'm at work atm and sh*ty mondays are sh*ty so not so much spare time to play around :)
[Samsung Galaxy Nexus] supernova_00:
I meant have the tunable values you guys been playing with for about a week been updated in the app? Are they the new default now?
[Samsung Galaxy Nexus] joaquinf:
To make them the default values they should be updated on the kernel img not in the app. You can always mod them to your personal preferences though :)
[Samsung Galaxy Nexus] stevensoaj:
Just to double check, would this be the correct init.d script to set read_ahead to 512 on boot?

#!/system/bin/sh
echo 512 > /sys/block/mmcblk0/queue/read_ahead_kb

Also, I'm not quite sure I completely understand the naming schemes of init.d scripts. Is a name of "10sdboost" ok?
[Samsung Galaxy Nexus] tristan202:
Sv: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

You can call them what you want. The numbers in front is to make them run in a specific order, ie you would want it to mount something first, and then symlink after, not the other way round.

Sendt fra min Galaxy Nexus med Tapatalk2
[Samsung Galaxy Nexus] davisac:
I updated the test I did of the read ahead values to include 128, 256 and 512. The link osm0sis posted earlier will work or here it is again:

Test Results on Google Docs

(Note: Test was done on Nexus 7 but principles etc should still apply)
[Samsung Galaxy Nexus] pkgnex:
I'm not sure you can make the logical leap that what works on N7 will apply directly to Galaxy Nexus. I seem to recall the whole reason the Interactive governor tunables just got re-hashed is because these two devices were not both optimized on the same set of parameters.

My own (albeit much less thorough) testing has shown lower values "win" on my Galaxy Nexus, with anything over 512 being detrimental to read/write speeds in some objective tests, and also feeling more sluggish subjectively while scrolling in some apps. I run 256.

I'd be really interested to see the same set of data posted for the N7 run on a GNEX ;).
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Had a weird thing happen after switching to ROW for the first time (been on Deadline always). I just upgraded to the latest RasbeanJelly and was tweaking it. I apply the GPS Patch by copying gps.conf and SuplRootCert from my Downloads folder, to system/etc. This has worked every single time since forever. This time, after selecting ROW, those two files wouldn't copy to system/etc. I definitely had it mounted as writable in ES File Explorer. Now, at this point I did two things (should have just done one and tested): I rebooted, and then changed back to Deadline...then the files copied over fine.

I'm on 15/95/729/45/15/85, readahead_kb=1024 (stock) with Interactive/Deadline, on both the GNex and N7 at the moment.

I just edit the readahead_kb file with ES File Explorer's Text Editor.

RF
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I had a similar issue today. I was writing an init.d script to set the read ahead value on boot. After I created a file, I noticed it wouldn't allow me to change the permissions. I also noticed it wouldn't let me delete other init.d scripts I was trying to get rid of. After I rebooted, the issue was gone.

I have been using ROW for awhile now and have never had such an issue. I used Solid Explorer to edit the files, and I'm on Slimbean 4.2.1 RC 1.
[Samsung Galaxy Nexus] jcmm11:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Just double check that it takes. I've had trouble setting this with init.d scripts for some reason. If I run the script after it finishes booting it works fine.
[Samsung Galaxy Nexus] CarlosAbia:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Don't like updating kernel too often, but kinda miss it here,lol.. Just kidding and being flashaholic, cause i'm running 361 with no issues.

Amazing kernel, tried a different one and came back to franco a few hours later :D never changing it again
[Samsung Galaxy Nexus] yumeul:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Is is possible to limit the GPU to 384? I suspect my phone get hot due to the 512...I was previously on the 384 stable build and the most I got was 44C now I'm getting 57C while only browsing the web.
[Samsung Galaxy Nexus] franciscofranco:
Hola everyone, heres a little treat:

r364:

* Set different set of interactive tunables researched by some of the community users - thanks guys you know who you are

* Merge 2 interactive patches

* Merge 3.0.58 to 3.0.61 from kernel.org

* Merge Sound Control interface again - original code by Ezekeel

* Merge few patches from my Nexus 4 kernel

Have fun :)
[Samsung Galaxy Nexus] Myster:
New Kernel broke compatibility with PGM (http://xdaforums.com/showthread.php?t=1721895)
[Samsung Galaxy Nexus] jesfreak:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

There is no zip for newest version :confused:
[Samsung Galaxy Nexus] franciscofranco:
Go post that on the app thread and tell him to fix his code.
[Samsung Galaxy Nexus] tjackbjorn:
Sv: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Here you go :) http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/zips/

Sent from my super fast Prime filled with beans.
[Samsung Galaxy Nexus] alexdemonumber3:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Its there, its just titled nightly with no number.
[Samsung Galaxy Nexus] jesfreak:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks! I just saw it but thanks anyway :thumbup:
[Samsung Galaxy Nexus] michi_1983:
AW: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

thanks for the kernel update Franco.

is it just me or did anybody elses phone not reboot after pushing the 'bring it on' button in fku?

greetz
[Samsung Galaxy Nexus] Myster:
I did , just reported so other people know this before installing ,

Thanks
[Samsung Galaxy Nexus] franciscofranco:
Works fine.