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

You don't flash the boot.img. just place it in the kernel backup folder on your card and Franco kernel app will see it as a backup. Select it and that will flash it

Franco r364
[Samsung Galaxy Nexus] neo-X:
nothing to see here =)
[Samsung Galaxy Nexus] belvedere:
there are zips, located in the 'zips' folder..

http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/zips/
[Samsung Galaxy Nexus] osm0sis:
On my new replacement screen, setting the color multiplier too early in the boot via init.d (any time before the boot animation) made everything look dark, oversaturated, contrasted and dusky; basically the opposite of the way it used to work on my old panel. Adding sleep 2; before that line in the init.d script fixed this.

So I've reuploaded my init.d script in my settings post with my new colors, and a commented out sleep 2 in the appropriate place to make it easy if you have a newer panel and run into the problem I described above. I also reordered the settings, putting Trinity contrast before the RGB Gamma and Color Multipliers to avoid the -1 green issue for certain combinations of settings.

Download count of the original file was at 1068 which I'm sad to see go but thus is progress. Thanks everyone! :D
[Samsung Galaxy Nexus] shreddintyres:
just out of curiousity what exactly is the command "sleep 2" doing? i mean what was your reasoning in trying this particular command ?

Thank you as always for the informative post :good:
[Samsung Galaxy Nexus] osm0sis:
Ah well, once I figured out the multiplier was the one at fault, I wondered "what if I set it after the Google logo, during the bootanimation instead?" (since that used to make things worse on my old panel). And that's exactly what sleep 2 does, makes the script wait 2 seconds before continuing to the next command. The Google logo is only up for about 1.5 seconds after the busybox run-parts call which executes the init.d scripts, so 2 seconds should push it just over into the bootanimation, seamlessly changing the colors as the animation is fading in anyway. :)

If you've got a lot of sh*t going on in your init.d directory, or you're on a different kernel that calls run-parts at a different time then it's possible 2 wouldn't be long enough I suppose, but it should work for pretty much everyone on franco.Kernel.
[Samsung Galaxy Nexus] galakanokis:
Thanks osm0sis, running your script now. It originally turned my screen that nasty green so i had to bump the gamma for green to 0 instead of -2.

Is it better to have multiple scripts to set things or just one long script with multiple things inside? I want to look at setting colour, gamma, audio, frequencies yadda yadda yadda.

This no root thing is beginning to be a pain in the ass...
[Samsung Galaxy Nexus] osm0sis:
Shouldn't matter, really. All in how you want to organize things since you can order the commands in the script itself or using multiple scripts with different numbers at the beginning of the name to make them run in a particular order. I'm setting the IO Scheduler tunables on boot right now as well as my color settings in the same script, called 900bootsettings.

Also that's really weird that you got the -1 green gamma bug with my settings. At Trinity contrast -10, and the green multiplier up at 295 I can take the green gamma all the way down to -11 at lowest brightness. Hmm.. so it also appears to be brightness related, since on Auto (which generally keeps it a notch higher than lowest) I can put it down to -15, but then when the screen dims after 20 seconds (or whatever) before turning off it goes green.

So 4 things affect it:

-brightness (more likely at lower brightness)

-trinity contrast (more likely at lower, more negative, contrasts)

-green multiplier (more likely at a lower multiplier)

-green gamma (more likely at a lower gamma)

Possibly varies per device as well if you used my exact settings and are also getting the green at only -2. Maybe it's because of some brightness/color calibrations of the screen at the factory.
[Samsung Galaxy Nexus] lightingcloud:
cfq didn't solve the problem :( well, I managed to complete the download once, but the file was broken so I tried to download it again but the phone froze. back to row.

Looks like the freeze happens mostly when the screen is about to go off, but not always since I clearly remember one freeze while using it.

EDIT: anyway, I have no issue with Play Store, the apps update normally. I experience lags, but I think they are related to avast doing his scan after install is complete. this is the first time the phone freeze while downloading something from another app (specifically, Humble Bundle), and the problem seems to be only with bigger file. the app I'm triying to download is about 190MB (freeze at 30%) but I had no problem with a 53Mb download.
[Samsung Galaxy Nexus] Phk:
Hi Franco,

I'm curious on this patch, because no CM10.1 kernels\roms include the external SDcard EXT4 functionality.

Can you post the latest version of this hack? Or even the JB 4.1 version?

Can't find it anymore..

Thanks
[Samsung Galaxy Nexus] osm0sis:
Not needed, we just run the stock sdcard binary now and the world is a better place for it. The hack caused way more problems than it helped, and downright broke the Play Store and other things with JB4.2. Everything should work fine with stock.
[Samsung Galaxy Nexus] Phk:
The stock doesn't mount my external ext4 SD.

I need >4GB file support. Do you confirm that the stock mount ext4 sdcard?
[Samsung Galaxy Nexus] osm0sis:
In what world does a Galaxy Nexus have an external sdcard?

---------- Post added at 05:17 AM ---------- Previous post was at 04:51 AM ----------

OT: Guys I'm pretty excited about this sdcard backup solution I found buried in the Nook subforums: [TOOL] ADBsync ! Another RC came up with this brilliant utility to only adb pull files which are newer than your local copies (ie. changed). :victory:

I added a batch script for automation and my usage (android -> host, excluding Pulse's cache directory due to the excessively long filenames to zip it up separately), which someone else could tailor to their own needs here. I also have a sdcard fix permissions flashable zip script I uploaded to that post for after you restore your sdcard backups to your device.

Anyway, I just thought more people needed to know about this since it's freaking handy to be able to do a nandroid and then just grab your whole sdcard for a literal snapshot of your device at that moment; and this makes that easier than ever by saving you time on the sdcard pull where files haven't changed.
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Hey Osm0sis, I'd very interested to learn how you adjust the scheduler tunables via init.d script, as I experimented a lot with deadline in the last days but could never make the settings persistent. :good: :)
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Here ya go fen... I think osm0sis and I have settled on 351/3500/4/1/1 for deadline as the sweet spot but check them out yourself

Using osm0sis's commands above I made a file to just set the deadline to the sweet spot we found but the freq can be changed. Use this the same way you did the color settings removing the .txt and pushing to system/etc/init.d and chmod 755

900deadline

Franco r364
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Has anyone seen the following:

(I'm on r364 with RasbeanJelly 2/2/13 Build)

Charge phone to 100%

Unplug phone and have it stay at 100% for a looooong time (Battery Widget Reborn shows a 1% drop every 2+ hours)

But...once I hit around 65%, my phone shows "Charging"...but it isn't on the charger.

Percentage starts dropping like crazy after that.

First time I noticed this was with the latest kernel/ROM...don't know which to troubleshoot. Maybe I'll try r361 first.

Thanks,

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

Lemme know if you have any problems with that fen. I'm running that exact same script and chose to leave it out of the color settings init.d just in case I wanted to change or modify it

Franco r364
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Very nice and helpful indeed! Thx malaroth :good: :thumbup:

I'll now try and compare my deadline settings with yours. They are already quite close (406/4000/4/1/1).
[Samsung Galaxy Nexus] osm0sis:
Ah so you liked 4 over 6 too? In the end I decided I couldn't really tell the difference. Franco just made your scheduler tunables (with 6) the defaults on the N7 and N4, so I'd bet we're next. ;)

---------- Post added at 02:32 PM ---------- Previous post was at 02:14 PM ----------

Cool! Just tried them. I think I still feel 351/3500/6/1/1 is a bit snappier though, and tried 4/1/1 again and now I feel it's just barely perceptibly quicker than 6 as well.
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks to the handy script I tested 351/3500/6/1/1 as well as 4/1/1 and came to the same conclusion. Very nice and snappy settings :) :good:
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I liked 6 but figured you had more extensive knowledge with tiny variables. I thought it was just a placebo effect so I went back to 4.

Glad to see that's helping fen!

It's strange to see something you do come up as a standard. Pretty cool though. I took a lot of time reading up on it first then more experimenting until I first contacted you osm0sis. Then even after I kept testing and got Joaquinf into it and finally Franco. Didn't want to go to him without it being fully vetted

Franco r364
[Samsung Galaxy Nexus] osm0sis:
Oh man, I have very little knowledge about the scheduler tunables, about as much as you, or less I'd imagine since you've done all the recent reading on them. Do you still think 6 is quicker? Theoretically raising it should favor reads more, which makes things generally quicker (like row) but only to a point, after which writes get too starved and downloads choke the hell out of your device (like row ;)).
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Yeah I do... if I understand it correctly it means allowing a greater amount of writes to be starved before forcing the write, which kinda gives it a lil bit of ROW since reads are going to flash quicker.

Franco r364
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

By the way I've updated the download to 351/3500/6/1/1 so any of y'all that want to get a jump on the sweetness it's all set for you. Just please keep in mind that even though it's all the same design, no single Gnex is exactly alike. This should work for the vast majority but if it doesn't seem so great on yours don't say it doesn't work, it's easy to adjust to your device and we'll help work it out

Franco r364
[Samsung Galaxy Nexus] _chanstar_:
I have the same -1 green gamma bug with the settings and script. I also had an issue where the colors applied would go away after a few seconds making it seem like its dimming and about to go to sleep, or dimming due to Auto Brightness when it really isn't (same lighting within the same environment). The dimming issue only began when I decided to place the IO Scheduler Tunables into the same script. I disabled Auto Brightness and the issue went away.

Since that occurred I decided to check and see if the green gamma bug still occurs with Auto Brightness disabled but it remains.

If you see any issues in the 900bootsettings script, please let me know...

Permission on system/etc/init.d and 900bootsettings are rwxr-xr-x.

All settings in the script matches the settings in fK.U.

#!/system/bin/sh

# chmod -R 755 /system/etc/init.d

echo 0 > /sys/class/backlight/s6e8aa0/acl_set;

echo 5 > /sys/devices/platform/omapdss/manager0/gamma;

echo -10 > /sys/module/panel_s6e8aa0/parameters/contrast;

echo "-4 0 8" > /sys/class/misc/colorcontrol/v1_offset;

#sleep 2;

echo "2250000000 2950000000 4000000000" > /sys/class/misc/colorcontrol/multiplier;

echo 512 > /sys/block/mmcblk0/queue/read_ahead_kb

echo "deadline" > /sys/block/mmcblk0/queue/scheduler

echo 351 > /sys/block/mmcblk0/queue/iosched/read_expire

echo 3500 > /sys/block/mmcblk0/queue/iosched/write_expire

echo 6 > /sys/block/mmcblk0/queue/iosched/writes_starved

echo 1 > /sys/block/mmcblk0/queue/iosched/front_merges

echo 1 > /sys/block/mmcblk0/queue/iosched/fifo_batch

Overall though, disabling Auto Brightness fixed the dimming issue and thanks for the settings!! Everything looks alive and colorful!!
[Samsung Galaxy Nexus] osm0sis:
The f.Ku settings need to match, would be my only guess for why they'd reset.
[Samsung Galaxy Nexus] Wynnded:
I have a quick question for you fellas if i may. Is this happening to you?: In the IO Scheduler Tuning, when I input the read_expire to 351 and back out, then go in again, it's displaying 360. In will only display 351 when I input 350, back out and go back in to check it.

I'm simply wondering if this is happening with you guys as well. I read how inputing 350 yields 351, but may have missed where someone mentioned inputing 351 yields 360. Thanks gang.
[Samsung Galaxy Nexus] osm0sis:
Weird it's doing that (360 for 351) for us on the N7 now too.. Except it displays 350 exactly and multiples of 50 work exactly, whereas here before it was 125. So when you enter 350 you get 350 or 351? It still works as before for me here, with 350 giving me 351 and 351 staying at 351, both in f.Ku and via init.d.

Maybe there's some weird per-device sh*t that deadline calculates? Kind of like SR? Are you maguro, toro or toroplus? What's your read_ahead_kb value? Ours are all at 512 so try that first, even though my N7 is also at 512 and jumps to 360. Wynnded was confused. ;)
[Samsung Galaxy Nexus] Wynnded:
LOL, I just popped over and was catching up on the N7 thread.

Let me see if I can keep my explanation straight. ;)

On the GN if I enter 350 I get 351. Enter 351 get 351.

On the N7 if I enter 350 I get 350. Enter 351 get 360, like you mentioned.

So, I think that I may have been confused either on which device I had sitting in front of me or which thread I was reading. I need to try harder on keeping all this sorted. Whew. :silly:

So what I posted about what appeared to be happening with my GN was incorrect as I'm not able to reproduce it. Ah, well.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Enter the value as 350. It will change to 351 but till we figure out why that is that's the end result we want

Franco r364
[Samsung Galaxy Nexus] osm0sis:
Phewf, okay. The world is not crashing down around us. :p

351 for the GN, 350 for the N7. :good: Hopefully franco can explain why there might be a difference. Different patches to deadline on the N7 perhaps. :confused:
[Samsung Galaxy Nexus] Antob125:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Osm0sis these are the current numbers you all came up with as of recent correct? I'm trying to find you magic post that I always refer to but having a hard time find on tapatalk

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
Yes they are the magic values :)
[Samsung Galaxy Nexus] osm0sis:
Bingo! Those are the correct GN ones. I've got them in my settings post as well, so you can always refer back to that if you like until Franco pushes a new build with the correct ones here. :)
[Samsung Galaxy Nexus] Antob125:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Your settings post is what I'm looking for. Is there an easy way to find it on tapatalk?

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

http://xdaforums.com/showpost.php?p=34951507

Here it is. No there isn't an easy way with tapatalk...you have to click on a post of his and open in browser in order to see a clickable link in his signature

Franco r364
[Samsung Galaxy Nexus] gialandra:
Maybe a stupid question but every time you update the rom you have to flash the Franco kernel and set again all UV one by one. It would not be possible an automatic restore function?
[Samsung Galaxy Nexus] Khrushy:
Backup your fK.u settings with Titanium Backup, flash ROM, flash kernel, then restore fK.u data with Titanium. :good:

(Please note - may occasionally cause bugs if settings have changed between kernel versions, so you might need to wipe and redo it all sometimes - but it does work most of the time)
[Samsung Galaxy Nexus] lightingcloud:
Hi :) I tried using your color settings both via franco's app and init.d but the screen is way too... green. Just green, actually. Is there some kind of problem? Am I missing something? I read that those settings via app give this problem, but I also read that via init.d should solve.
[Samsung Galaxy Nexus] gialandra:
Do you mean the app data? Or what is the way to backup this file? Thank you
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

It seems Google is rolling out 4.2.2 to nexus devices. Anyone who received the OTA yet? For me nothing on my takju gnex and N7 in the Netherlands.
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

You have to flash the kernel itself separately first - it will have the default settings, then you restore the f.Ku app data using titanium, and it'll restore your voltage settings etc.
[Samsung Galaxy Nexus] bombadier:
Android Headlines has the update and instructions if you want to flash
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

WARNING 4.2.2 will not boot with franco 364!

Running 4.2.2 here's the stock gov control.

More governors

Different speeds

Settings about phone

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mkalter:
Thanks, was already thinking why it didn't boot.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Yeah even though its the same kernel version its newer so now we wait for Franco to update. 4.2.2 isn't much different than 4.2.1 there's no rush to update I'd say unless like me you live on the bleeding edge haha ;)
[Samsung Galaxy Nexus] Antob125:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Also are Timer_Slack and Boostpulse_duration both set to 80k for you?

Also in your magic post you list read ahead buffer as 512. I'm having a hard time locating that option in fku.

Also how are your now color settings working for you? You had to make changes since you got a replacement phone right?

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

Read ahead buffer is set by init.d, Franco hasn't updated fku to include it yet, and if not using fku, trickster mod has the option also
[Samsung Galaxy Nexus] Degrated Shadow:
nfs most wanted lags like hell unlike it was on 4.1.2 what's wrong? is there any fix?
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Answered multiple times throughout this thread, use the search function first and foremost
[Samsung Galaxy Nexus] osm0sis:
Fuuuck yes, OTA day!!! :D:p

Everyone on stock takju: OTA URL dropped, I'm already upgraded and ripped the radios. Check the OTA thread and flash in CWM/TWRP. :good:

Just a note: f.K users will need to delete /system/lib/hw/power.tuna.so and rename /system/lib/hw/power.tuna.so.fkbak to power.tuna.so to pass the OTA asserts.

P.S. App drawer scrolling on stock kernel is fast as hell now, so hopefully there's something nice in there franco can throw our way once the source drops. Even the widgets. Fastest I've *ever* seen them on *any* kernel.
[Samsung Galaxy Nexus] -Jesco-:
is the radio flashable on 4.2.1 >? heard that it might not work .
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I might be going a little off topic here but to me the colours on 4.2.2 look different again, against my n7 the supper amoled colours don't look as 'forced /over saturated' as before. I think it looks more natural and on full brightness the white isn't yellow which on 4.0 my panel was piss yellow colour hahaha
[Samsung Galaxy Nexus] osm0sis:
Just answered this in the radio thread:

http://xdaforums.com/showthread.php?t=1405345&page=205

Haha my new panel is kinda pissy yellow on stock and still is, so I can't wait to get my color control back, but it beats the hell out of the purple garbage I had before with my old screen. :)

But yeah things seem a little brigher, and whites do seem marginally better!
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Wacky. Just flashed the new radio and my colours have definitely just shifted a notch towards yellow.

Not a good look at all (my screen had gorgeous whites before).

Edit: fixed it, but I seriously had to ramp up the blue multiplier to get things back to balanced.
[Samsung Galaxy Nexus] CADude:
Yes, radios can be flashed regardless of version.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

I'm sticking with 4.2.1. Between waiting for Franco to go through and waiting for jbsourcery to build it in I'm gonna stick with 364 and keep up work on the schedulers

Franco r364
[Samsung Galaxy Nexus] ortrigger:
I have heard good things about franco kernel. I haven't tried it yet but will be flashing it shortly. I'm looking forward to seeing how it goes.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Franco has been my daily driver for over a year. It just keeps getting better

Franco r364
[Samsung Galaxy Nexus] tetrakinitis:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

The BEST. Just try it!

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] Cobra78:
Anyone have had problems with Franco Krenel r364 and the latest Ota update 4.2.2? My Phonwe won't boot, it remain stuck at the withe google word :|
[Samsung Galaxy Nexus] whitedragonz83:
I believe it was mentioned earlier that 4.2.1 kernels do not work with 4.2.2. Reflash stock ROM and Kernel and you will be fine. You might need to do this via fastboot.
[Samsung Galaxy Nexus] Cobra78:
I searched in the post but havent found this info, maybe my fault. Anyway the phone is already ok, i have always a nandroid backup, and recovery was working fine :)
[Samsung Galaxy Nexus] whitedragonz83:
I might have read it in another thread. It's been a busy day reading threads with the patch! :)
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Should be in red letters probably :);)
[Samsung Galaxy Nexus] Cobra78:
Uffff, i need to wait from Franco to make a compatible version :eek:
[Samsung Galaxy Nexus] ortrigger:
First thoughts of this kernel are very promising. It has all the features I like from other kernels I've tried and probably a few more that I haven't found yet.
[Samsung Galaxy Nexus] gauravraw:
Thanks!
[Samsung Galaxy Nexus] cyhamada:
You need Franco's kernel app.

Use root explorer to put the .img file into the "kernel_backups" folder...it's on your SD card if you've already installed the Franco app...and then the .img file will show up in the "Kernel backup/restore" menu in Franco's app.

It's simple after you do it the first time.
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel-r364 -&gt; 4.2 | r300 -&gt; 4.1

Or you can put it in to any flashable zip and flash. Easiest way is to replace the kernel in the Rom you have flashed with Franco and reflash the Rom.