yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Gafanhotz:
Stock kernel is pretty ****ty if you ask me. And in 4.3 they deactivated module load support. Right now I'm on a need of an custom kernel compatible with 4.3, or else I'll rollback. ):
[Samsung Galaxy Nexus] osm0sis:
A few more changes in the ramdisk to weed through than I'd hoped. Probably an hour.
[Samsung Galaxy Nexus] Edward Stanbury:
man stock 4.3 is blazing fast, there must have been a few under the hood optimisations :P cant wait to push the latest osmod(@osm0sis) or FK this phone is gonna fly like never before ! (well once the ramdisk is all sorted ofc haha)
[Samsung Galaxy Nexus] osm0sis:
franco.Kernel-tuna-r384 + JB4.3 Ramdisk Hybrid

Without further ado.. f.K-tuna-r384-hybrid ! This is for JB 4.3 ROMs ONLY! because that's what it had to be made for. ;)

I've added all the optimizations Francisco usually makes to the ramdisk. This is not an osmod, since I didn't add any of the stuff we're testing right now; it's the "original recipe" r384 defaults.

The only exceptions are:

- I included the smaller busybox binary (updated to the latest, 1.21.1 by Stericson) over Francisco's older, larger one.

- Where Francisco usually comments out the call to install-recovery.sh in init.rc I added support for Chainfire's new daemonsu (now v1.43!) root method, because all other root methods do not work anymore in JB4.3.

Check the daemonsu link for important info on root app sdcard compatibility and root zip download. Please update immediately to SuperSU v1.43 to resolve/workaround issues with his previous daemonsu (v1.41). You can disregard the install-recovery.sh stuff since, as I stated above, I've got it covered with an init service. :good:
[Samsung Galaxy Nexus] franciscofranco:
Hey guys. I'm on vacation at the moment. I'll be updating this Kernel for 4.3 when I'm back home around 29th of July. I didn't even bring my GN with me so no dice. Thanks for the comprehension.
[Samsung Galaxy Nexus] Sik-1:
Super smooth Os
[Samsung Galaxy Nexus] osm0sis:
No problem Francisco! Enjoy your vacay! :D

We could definitely use UVing for IVA and CORE back in f.Ku when you get the chance too. :good:

Only weirdness I'm noting is the lowmemorykiller numbers are a little wonky:

12134,15175,18216,21273,24314,30382

Those probably aren't right because of some interaction between things, so I recommend running the Franco's Dev Team 925vmsettings init.d script for now until Francisco can get things properly sorted for JB4.3. :good:
[Samsung Galaxy Nexus] thegtfusion:
was in the cinema.. watched red 2. awesome movie!

so i read all the posts, and what i get is that the v1.41 root works good?
[Samsung Galaxy Nexus] nitsua98:
https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L
[Samsung Galaxy Nexus] osm0sis:
Has to be the v1.41 "daemonsu" that I linked.

Edit: Ninja'd by nitsua! :D
[Samsung Galaxy Nexus] Sik-1:
Something for [MENTION=321228]os[/MENTION]

Memory is looking stunning!!!!
[Samsung Galaxy Nexus] marshy73:
Anyone encounter broken WIFI with #384_Hybrid?

I tried flashing twice and even had settings all cleared but Wifi doesn't turn on.

Flashing back #384_Osmod restores Wifi.

Just checking...
[Samsung Galaxy Nexus] osm0sis:
Wow! What are you using? Just the hybrid kernel as it is or with the 925vmsettings init.d?

I just went back to stock kernel again to compare numbers and those weird lmk minfree numbers are there too.. soo not sure how they're getting set?

8099,10132,12165,14213,16245,20295 were the old defaults. Should we stick with the new ones or should I add the old defaults back in and upload another revision?

---------- Post added at 01:01 AM ---------- Previous post was at 01:00 AM ----------

It's for 4.3 only... :rolleyes:
[Samsung Galaxy Nexus] Sik-1:
I flashed your current init.d scripts and that's it
[Samsung Galaxy Nexus] osm0sis:
K. So you're running our test vm tweaks which include the lmk minfree:

6144,8192,12288,16384,24576,40960

This is vs. old stock (and f.K) default:

8099,10132,12165,14213,16245,20295

and the new stock default:

12134,15175,18216,21273,24314,30382

Looks like Google kind of took it in the same direction we did. ;)

I'm going to go ahead and switch back to the 4.2 defaults since the lmk driver should still be the one Francisco has in r384 which is likely older than the 4.3 one.
[Samsung Galaxy Nexus] thegtfusion:
need help here... flashed 4.3 (stock image) , installed root and then franco. but now I cannot restore using titanium backup. but the franco kernel updater works fine.

also whatsapp doesnt want to install now. (tried to restore with tbu, hanged and now if i download the apk and install it doesnt work.) also if i reboot, the apk says app not installed.

any help? please osm0sis help me :(
[Samsung Galaxy Nexus] Pkt_Lnt:
He did, above. deamonsu link

http://xdaforums.com/showpost.php?p=43921407&postcount=42706
[Samsung Galaxy Nexus] Sik-1:
Most likely the apps compatibility with 4.3 , I have several apps that aren't working especially my beloved apex launcher :banghead::banghead::banghead:
[Samsung Galaxy Nexus] Gafanhotz:
For some weird reason the system isn't letting me restore the .img file as kernel backup. It reboots as it should, but when you look at it, still stock kernel. WTF?
[Samsung Galaxy Nexus] thegtfusion:
it works now, but whatsapp does not want to restore. it says app not installed. maybe because I tried restoring it before? what can I try? I really need whatsapp.... :(
[Samsung Galaxy Nexus] osm0sis:
Same issue as TiBU, read Chainfire's G+ post again. For TiBU it's an easy workaround to point it to the legacy sdcard symlink instead. For f.Ku, Franco will need to fix that in the code if Chainfire can't work out a clever way around these sdcard issues.

----

I'm uploading a new version of the 4.3 hybrid - it has the workaround to bring back the old default lmk minfree values, and a couple different options for the daemonsu service to try and make it behave better (daemonsu may cause the occasional CPU spike/slowdown as the posts I pointed to explain; Chainfire's working on it). Again, this is the only method for obtaining root on JB4.3 so far, and though it does work and works well, it's still a work in progress and there are still some other weird intricacies of JB4.3's changes to circumvent/accomodate.

Post updated: http://xdaforums.com/showpost.php?p=43921407
[Samsung Galaxy Nexus] Gafanhotz:
Thanks! Also, I managed to add the img file to a zip and flash through TWRP, worked fine. But I have to rollback to 4.2, my power button is broken and I need PGM, and for some weird reason, the system isn't letting the PGM app load the modules to make it to work.
[Samsung Galaxy Nexus] cmstlist:
The string "memory leak" appears 35 times in the changelog ;)
[Samsung Galaxy Nexus] thegtfusion:
Can someone upload the hybrid osmod kernel for me? A flashable zip? I want to flash jt but i cannot access pc now.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] agayabag:
Use flashify from market, it's free.
[Samsung Galaxy Nexus] thegtfusion:
Yeah, I found a method to make a flashable zip via phone. Everything works right now. It's perfection. (Whatsapp works also :D)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] abalam:
Do you have a link? I wanne flash it to.

Edit: found it http://d-h.st/A4Z
[Samsung Galaxy Nexus] Gafanhotz:
Loved the new hybrid, works fine! But anyone made PGM work?
[Samsung Galaxy Nexus] bunnahabhain:
So what i don't understand as far as the kernel work is concerned is the following:

With Android 4.3 we got a new kernel source don't we? That source is patched up to 3.0.72. Franciscos kernel however is patched to an even higher number. But are the sources the same? So basically the AOSP kernel + patches? Or is the 4.3 kernel based on different sources?

So my question is: Is osmosis' modified 384-hybrid just the same kernel with just ramdisk tweaks as it would be if franco would compile it from the new source or is the new source somehow better or more compatible or what?
[Samsung Galaxy Nexus] RevengeFNF:
I don't understand much of this, but Boype after taking a closer look at the source of the new 4.3 Kernel, decided to rebuild the kernel from the new source, and not only change the ramdisk in Fancy Kernel. He said it will take some days.
[Samsung Galaxy Nexus] osm0sis:
Yeah there will definitely be more changes kernel side. Those numbers are just Linux version, they mean little of what's actually in there.
[Samsung Galaxy Nexus] shawnaye:
Hey os, any wifi disconnections on 4.3? Haha.
[Samsung Galaxy Nexus] bunnahabhain:
Ok, good to know. That is good news - our Gnex just got a liitle bit better then. I heard that many memleks got fixed and that playstore installs don't lag anymore . Can't wait for an updated kernel with francos and your tweaks now :)
[Samsung Galaxy Nexus] tylerdurden83:
Just asking to learn, not to complain or try to say that benchmarks matter or anything, but why do I get much lower quadrant scores on franco's latest (2899ish) versus the latest AK (3688ish)?
[Samsung Galaxy Nexus] akash3656:
I personally feel the RAM still balloons up and leaks pretty bad but still smooth. But apps get killed often, though not laggy like 4.2. It's a bit hard to explain it properly. Play store installs still feel laggy to me (4.0 I think still is the smoothest for play store app install). I updated my phone via the factory images without wiping. On pure stock ROM and kernel not even rooted. As I've heard problems with CPU usage with the current supersu 1.41 on the 4.3 leak for the nexus 4.
[Samsung Galaxy Nexus] Ladaga:
In my case it's the same, 80% of ram in use... No change for me
[Samsung Galaxy Nexus] tloc:
On 4.3 with stock kernel, Wi-Fi works perfectly fine for me.

On the modded kernel Osmosis posted a few pages back, Wi-Fi drops just like it did in Android 4.2.2.
[Samsung Galaxy Nexus] supernova_00:
Does WIFI still disconnect when sleeping? On 4.2.X I can never get the settings to stick more than a day.
[Samsung Galaxy Nexus] jesssiii:
How would one backup the stock kernel img? I'd like to easily go back in case the hybrid has problems.

Galaxy Nexus Toro
[Samsung Galaxy Nexus] The Gingerbread Man:
Download the factory image and keep extracting it then you can fast boot it
[Samsung Galaxy Nexus] chiwou:
I get a hard reboot (I even heard some weird noise from the speaker) when flashing on PA

FYI latest version, franco kernel updater
[Samsung Galaxy Nexus] doomed151:
If you use TWRP, backup the "boot" partition only. That way, you can restore the kernel easily. Don't forget to give it a name or it'll be lost among other backups.
[Samsung Galaxy Nexus] whitedragonz83:
I found Android OS is handling clearing old apps out smoother when I have high RAM usage. When it was in between syncing Google Services data, I actually saw my RAM used was almost exactly where it was upon initial boot. So while the Android OS is not using less RAM (or minimally), it is being more aggressive (or cleaner) at unloading RAM when needed.

IMO, huge improvements. Also, this is on Stock 4.3, but wanted to provide feedback on the RAM usage.
[Samsung Galaxy Nexus] pkgnex:
This makes perfect sense given what osm0sis found with the LMK value differences between 4.3 and 4.2.2.

4.3 should behave more similarly now to where we had tweaked it on 4.2.2 with Os's 925 init.d script.

P.S. I think there may still be opportunity to tweak the 4.3 values to make them even a little better...
[Samsung Galaxy Nexus] thegtfusion:
i'll drop this here. this osmod (latest for 4.3 http://d-h.st/A4Z ) but packed in a flashable zip.

flash in recovery. (on your own risk :) )

Latest flashable osmod FOR 4.3 ONLY!
[Samsung Galaxy Nexus] tloc:
On stock 4.3 with stock kernel, it works perfectly fine. No disconnects.
[Samsung Galaxy Nexus] pikso:
Any chances to get Franco for 4.3 this week? :D

r400? perhabs :D
[Samsung Galaxy Nexus] Ziyan:
Are you talking about the official kernel? I'd like to see the differences between the official 4.2.2 and 4.3 kernel, but I couldn't find this changelog. Could you please post a link to it? :p
[Samsung Galaxy Nexus] playenball:
I would count on it. Franco is on vacation with his girlfriend. Even hard working kernel developers need some time off.
[Samsung Galaxy Nexus] cmstlist:
I mean the changelong for the entire OS.
[Samsung Galaxy Nexus] Gafanhotz:
I discovered that module loading is being made impossible by something on the system, anyone managed to discover what is it?
[Samsung Galaxy Nexus] stevensoaj:
Are you talking about this commit?

https://android.googlesource.com/kernel/omap/+/fbc1a9de516ca3539bc28531f452912da284748a
[Samsung Galaxy Nexus] Gafanhotz:
Nope. I was talking about the hybrid of FK that Osmosis made, and about the stock kernel other guys compiled without this commit and didn't succeeded anyways.
[Samsung Galaxy Nexus] osm0sis:
I'd guess ramdisk and ROM security changes are the culprit. There are a LOT of "security fixes" that basically break the way we've done everything forever. Rooting is the prime example we should all know of by now, also the sdcard symlink issues for root apps, and there's a good possibility this might also apply to modules.

By the way, if anyone on JB4.3 hasn't updated to SuperSU 1.43 - DO SO. Chainfire has fixed the daemonsu CPU spiking (that he knows of) and has a temp workaround for the sdcard issue until root app devs update: https://plus.google.com/+Chainfire/posts/Jkuu84odnx6 :D

If you're using my f.K + 4.3 hybrid, don't worry about install-recovery.sh - you can delete it, I've got daemonsu taken care of as a service via init.rc. And that should hopefully make the hybrid completely stable now, since those root ones were the only problems I've seen (Wi-Fi is fine for me). :good:

Edit: Whoops I see Chainfire changed the way the daemon gets called. Updating the f.K-hybrid now. Give me a bit to test and upload.
[Samsung Galaxy Nexus] osm0sis:
franco.Kernel-tuna-r384 + JB4.3 Ramdisk Hybrid (v3)

Something to tide us over until Francisco has time to update everything to JB4.3 after he's back from vacation at the end of the month... :highfive:

franco.Kernel-r384-hybrid ! This is for JB4.3 ROMs ONLY! because that's what it had to be made for. ;)

I've added all the optimizations Francisco usually makes to the ramdisk. This is not an osmod, since I didn't add any of the stuff we're testing right now; it's the "original recipe" r384 defaults.

The only exceptions are:

- I included the smaller busybox binary (updated to the latest, 1.21.1 by Stericson) over Francisco's older, larger one.

- Where Francisco usually comments out the call to install-recovery.sh in init.rc I added native support for Chainfire's new daemonsu (now v1.43!) root method, because all other root methods do not work anymore in JB4.3.

Check the daemonsu link for important info on root app sdcard compatibility and root zip download. Please update immediately to SuperSU v1.43 to resolve/workaround issues with his previous daemonsu (v1.41). v1.43 has a workaround for the sdcard issues but it still may not work in all cases, this is likely something root app devs will need to fix because now in JB4.3 mounts are isolated between root and user. Also, you can disregard the install-recovery.sh stuff in Chainfire's post since, as I stated above, I've got it covered with an init service. :good:

The SuperSU zip will create install-recovery.sh and lock it from tampering, so if you want to remove it after (because we've got the service running natively) you can go to Terminal Emulator and su -c busybox chattr -i /system/etc/install-recovery.sh and then delete the file normally. Leaving it there also won't hurt anything since it doesn't run.

This may or may-not work on CM-based 4.3 ROMs (if those happen before Francisco's back). It's got all the usual alterations Francisco makes to have it work with CM, so hopefully they still hold.

Custom recovery flashable zip and fastboot img available:

http://d-h.st/users/osm0sis/hybrid
[Samsung Galaxy Nexus] sym_m:
after flash f.K-tuna-r384-hybrid my phone reboot in recovery all time and it not work iam on 4.3 sorry for bad English
[Samsung Galaxy Nexus] osm0sis:
You did something wrong. :( The img and zip files both work fine here. The fastboot command is: fastboot flash boot boot-tuna-r384-jb4_3-hybrid.img
[Samsung Galaxy Nexus] sym_m:
ok try flash it now i have flash stock google image
[Samsung Galaxy Nexus] Starsream88:
One question guys, for now i want to update only the bootloader using fastboot, if i did so, i will lose all my data ? Btw i'm running 4.2.2 rom

Sorry for OT
[Samsung Galaxy Nexus] Astug:
Thanks man! Do we have to remove it, will it interfere with anything or can we just leave it as it is?
[Samsung Galaxy Nexus] osm0sis:
Yeah.. this belongs in an OTA/flash-to-stock thread but in a word: no. Only fastboot oem unlock or fastboot flash userdata userdata.img will wipe things.

Nah, you don't have to remove the file if you don't want, since I removed the call that runs it anyway. Won't hurt anything at all if you leave it there. :)

Edit: Sidenote, messing with all this chattr stuff, it just suddenly occurred to me as the perfect way to keep the system from tampering with the oom_adj values in my lmk whitelist script. Super pumped to try that out on the weekend. :D right now and upload it if it works before hybrid v3 gets too far. :p

Nah nevermind, the lmk whitelist script appears to not be working at all right now, so I will need to take a bit more time to investigate it over the weekend. Sorry folks! Good news is things seem nice and fast even without systemui and launcher reniced! :D
[Samsung Galaxy Nexus] sym_m:
thanks it work perfect now
[Samsung Galaxy Nexus] doomed151:
Don't forget

fastboot -w

I accidentally did that some time ago when flashing a factory image and lost everything.
[Samsung Galaxy Nexus] osm0sis:
True!

Also, I just fixed the link to SuperSU v1.43 in my hybrid v3 post. Sorry if anyone was confused by that. Then v1.44 will install from the Play Store as a system app update after you've flashed it. :good:
[Samsung Galaxy Nexus] Gafanhotz:
Edit->

It was discovered the trouble with PGM, if you unistall the SuperSU app and keep the su binary, PGM works well with FK hybrid and the new faux's kernel. Now its only a matter of time to things get stable.

(Oh, it's PGM app fault, not SuperSU.)
[Samsung Galaxy Nexus] Astug:
Running fireb33's stock 4.3 with osmosis's hybrid r384 since last night, for about 15 hours now and I've had 0 issues. Everything is doing what it's suppose to do and very smooth. Thanks again for the quick fixes osmosis!
[Samsung Galaxy Nexus] plasticities:
If I'm running stock 4.3 factory images, I can just flash the new hybrid kernel without having to flash the stock images again? Only wipe cache and dalvik right?
[Samsung Galaxy Nexus] jesssiii:
Yes. Don't even have to wipe anything.

Galaxy Nexus Toro
[Samsung Galaxy Nexus] Prasad:
r384 hybrid v3 works flawlessly! Thank you guys! :)

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] sui785:
Just flashed this on 4.3 and finally I got rid of the yellowish stock colors :D

So far no issues.
[Samsung Galaxy Nexus] Badger51:
Cautious newbie with burnt fingers...

Do I need to flash both the kernel files and the img file?
[Samsung Galaxy Nexus] Prasad:
You only ever flash zips from recovery, img is for fastboot.. And no, it's one or the other for the same effect.

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] osm0sis:
Figured out what was wrong with the priority stuff! JB4.3's toolbox has a different implementation of renice. If I switch it over to busybox renice then it all works fine again. :)

Still looking into what's up with the lmk part though. Once I've worked that out I'll put up a hybrid v4. :good:
[Samsung Galaxy Nexus] Milleniumlance:
i tried on muzzy 4.3, the phone app suffered severe force closes, gonna try something though
[Samsung Galaxy Nexus] sui785:
Can you get a logcat? Did you do clean flash?
[Samsung Galaxy Nexus] Milleniumlance:
i did a dirty flash shouldnt have done it, being lazy, doing clean install now. do a nandroid and try again
[Samsung Galaxy Nexus] Milleniumlance:
tried it with a clean flash, still getting phone app crash, ill just wait for an optimized 4.3 kernel thx though
[Samsung Galaxy Nexus] njiki11:
Can someone please help me. I'm on toroplus and I'm using r384 but battery life is horrible and my phone is heating up bad!
[Samsung Galaxy Nexus] Milleniumlance:
have you been making changes to the build.prop or making changes to the default kernel settings?
[Samsung Galaxy Nexus] njiki11:
No. My setup was cubic and bfq
[Samsung Galaxy Nexus] njiki11:
I think I found the problem. "Android System" is killing my battery.....
[Samsung Galaxy Nexus] wasdf:
do you mean flashing r384 on 4.3? is it compatible with it? I would like to goto 4.3 but I am waiting a good kernel like franco's one, if it is compatible then I am good to go :silly:
[Samsung Galaxy Nexus] horst0815:
here's something to play with by osm0sis. it works :)
[Samsung Galaxy Nexus] bigknowz:
renice in 4.3

scripts need this change?

renice -17 `pidof com.android.systemui`

to

busybox renice -17 `pidof com.android.systemui`
[Samsung Galaxy Nexus] osm0sis:
Bingo. I've been using -18 for awhile now though, and boype (Fancy Kernel) switched over to that as well. :good:
[Samsung Galaxy Nexus] sym_m:
where is Hybrid v4 :confused:
[Samsung Galaxy Nexus] osm0sis:
Patience is a virtue... :p
[Samsung Galaxy Nexus] StormIceX:
anyone test this? i'll flash 4.3 rom this evening and a custom kernel sounds good :3
[Samsung Galaxy Nexus] Sik-1:
Been playing wit it since v1 and its excellent
[Samsung Galaxy Nexus] osm0sis:
franco.Kernel-tuna-r384 + JB4.3 Ramdisk Hybrid (v4)

Francisco's back from vacation tomorrow, but I finally worked the kinks out of fkbootscript (systemui and launcher are reniced again, etc.), so even if it's just a few more days until he's able to update the GN with JB4.3's kernel source, this should keep us going. :highfive:

franco.Kernel-r384-hybrid ! This is for JB4.3 ROMs ONLY! because that's what it had to be made for. ;)

I've added all the optimizations Francisco usually makes to the ramdisk. This is not an osmod, since I didn't add any of the stuff we're testing right now; it's the "original recipe" r384 defaults.

The only exceptions are:

- I included the smaller busybox binary (updated to the latest, 1.21.1 by Stericson) over Francisco's older, larger one.

- Above where Francisco comments out the call to install-recovery.sh in init.rc I added native support for Chainfire's new daemonsu (now v1.45!) root method, because all other root methods do not work anymore in JB4.3.

Check the daemonsu link above for the latest root zip download and read the original daemonsu v1.43 release notes for important info on root app sdcard compatibility. Please update immediately to SuperSU v1.45 to resolve/workaround issues with his previous daemonsu (v1.41-1.43). v1.43+ has a workaround for the sdcard issues but it still may not work in all cases, this is likely something root app devs will need to fix because now in JB4.3 mounts are isolated between root and user. Also, you can disregard the install-recovery.sh stuff in Chainfire's post since, as I stated above, I've got it covered with an init service. :good:

The SuperSU zip will create install-recovery.sh and lock it from tampering, so if you want to remove it after (because we've got the service running natively) you can go to Terminal Emulator and su -c busybox chattr -i /system/etc/install-recovery.sh and then delete the file normally. Leaving it there also won't hurt anything since it doesn't run.

This may or may-not work on CM-based 4.3 ROMs (if those happen before Francisco's back). It's got all the usual alterations Francisco makes to have it work with CM, so hopefully they still hold.

Custom recovery flashable zip and fastboot img available:

http://d-h.st/users/osm0sis/hybrid

v3 downloads were 200+. Not bad. :)
[Samsung Galaxy Nexus] jesssiii:
If we delete the file, will it eventually come back? Is there any down side to deleting it?

Galaxy Nexus Toro