yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] blackbird5308:
I maybe have a solution for this.. i don't know why, but since ziddey stopped compiling the "original" version of this the zip used contains the old ramdisk modifier file.. it was updated on >r198.. i use the new one and i don't have any problem :)

i have a question for [MENTION=4261467]xtrymind[/MENTION] too.. is r206 F2FS compatible? i tried flashing on a converted version of CM with no luck.. Keep up the good work man!
[Nexus 4 Android Development] boardlord:
Many thanks! Will tray this in a few hours after a nandroid backup. Now if only franco fixed the "2nd core stuck on 1.2Ghz" bug quickly :)
[Nexus 4 Android Development] blackbird5308:
huh, a quick tip.. make sure you first flash the original cm kernel, or the two ramdisk mods will create a conflict.. ypu may just dirty flash cm on top of the old one!
[Nexus 4 Android Development] boardlord:
Yup, that's what I'm gonna do. I'm on a nightly from March, so it's time to update anyway :)
[Nexus 4 Android Development] boardlord:
So, this took longer than I expected, but I flashed today's nightly and your compile [MENTION=4103497]blackbird5308[/MENTION]

It booted up fine, will see how it goes :) Thanks again for the effort!!

Edit: ok, to enable exposed I had to reboot and no bootloop! *thumbsup*
[Nexus 4 Android Development] blackbird5308:
good to know! but do not give me credits for what i did not make :silly:

i just repacked [MENTION=4261467]xtrymind[/MENTION] r206 with the updated modrd.sh by [MENTION=584916]ziddey[/MENTION]! i did not make anything, just put the puzzle together
[Nexus 4 Android Development] boardlord:
Still, really appreciate it!
[Nexus 4 Android Development] blackbird5308:
Franco r207 is up! waiting for [MENTION=4261467]xtrymind[/MENTION] to do some of your magic ^^

By the way, i read on the F2FS thread on general forum that some devs added "new F2FS code". Is there something worth checking out maybe? :p
[Nexus 4 Android Development] k1l:
No New Franco 207 news?
[Nexus 4 Android Development] anandbibek:
This is CM ramdisk repacked original franco. But it'd work with CM as it will replace CAF lib files

https://www.dropbox.com/s/f112zclhotlxac9/207.zip
[Nexus 4 Android Development] blackbird5308:
http://xdaforums.com/nexus-4/general/f2fs-roms-kernels-23-4-2014-t2728201/page44

check out the F2FS thread, you can find a working copy of Franco r207, it's F2FS and EXT4 compatible ;)
[Nexus 4 Android Development] mastel97:
Hey [MENTION=4261467]xtrymind[/MENTION], will there be a Franco #208?

Sent from my Nexus 4
[Nexus 4 Android Development] blackbird5308:
same as your friend up there, check the F2FS thread i linked one post up ^^
[Nexus 4 Android Development] 0.0:
New faux kernel! Could a 38m be made for cm [MENTION=4261467]xtrymind[/MENTION]? Thanks :)

Sent from my Nexus 4
[Nexus 4 Android Development] stab244:
If anyone is willing to help me, I can hopefully compile v39 for faux. I'm following this this guide and I have faux's repository synced and cherry picked the CM commits needed. When I get to the make step though I get an error. Picture is below.

I've followed every step in that guide so I'm using compiler they said to use. I've looked at xtrymind's github and couldn't figure it out.

EDIT: I can see that it says that I'm missing some files, but I don't see that directory on xtrymind's github.

Edit2: Just found the Chef's Central guide. Gonna test when it's done compiling. And figure out how to pack it...

Edit3: Okay now I'm really stuck. I got it to compile but it won't flash. I tried using AnyKernel and it wouldn't flash. I tried taking faux's official zip and replacing the zImage and zip it up but that didn't work either.

EDIT4: Okay finally figured out what went wrong. Here is the zip I made for Faux 039u. Let me know if it works for you. It booted on mine and all Faux features seem to be functional. But the voltage table seemed a bit weird. Gonna need to look into that.

PLEASE NOTE THIS IS FOR NIGHTLIES 6/6 OR LATER ONLY

Last edit I promise:

Screenshot of the kernel info:
[Nexus 4 Android Development] sergej_7:
could you compile 039m too? i'll try your 039u soon

EDIT1: testing right now, everything seems to be working flawless.

EDIT2: voltage screenshots attached let me know if that is normal because i dont know never played around with voltage
[Nexus 4 Android Development] 0.0:
Good job [MENTION=2222926]stab244[/MENTION]. I was trying to build the kernel too but it failed at the CPU_MAX_FREQ or something like that and I couldn't figure it out

Sent from my Nexus 4
[Nexus 4 Android Development] stab244:
Yeah voltages were fine. I was just being derp after being excited that it actually worked xD. I'll try to get 039m built once I can figure how to do it. I'm guessing there's an option somewhere during the make process.

If it helps I took the config.gz file from /proc and used that as the config to build from. The standard defconfig gave me some issues. The chef's central guide tells you how. I'll link once I get off my phone.

EDIT: Here you go. That should help you get the correct config. I was already on xtrymind's 037 kernel when I pulled the config.gz file out to use as a config file for the compiler.
[Nexus 4 Android Development] stab244:
Faux039m

It boots up and the frequencies are correct. Let me know if there are any other issues.
[Nexus 4 Android Development] sergej_7:
working like it should thank you :good:
[Nexus 4 Android Development] thunder2k:
Hi,

any news for fk?

Sent from my Nexus⁴
[Nexus 4 Android Development] stab244:
Faux40u

Faux40m

Compiling Faux40m right now. Link will be editted in when I'm done. 40u boots and has the new intelliplug options. I won't be testing 40m so I'll need someone to let me know if it works once it gets posted.

Edit: For whatever reason the m version is larger. I have no idea why. Oh and can someone tell me how I can update my sources if I used git clone to copy fauxs source to my computer?
[Nexus 4 Android Development] apb_axel:
If you open the .zip for the m version you'll see another .zip inside which is about the same size. I think that's why it's larger.
[Nexus 4 Android Development] stab244:
/facepalm

Forgot I had the other zip in the same directory when I was zipping it up. Thanks.
[Nexus 4 Android Development] 0.0:
Will git pull work to update the sources locally?
[Nexus 4 Android Development] TheDarkDefender:
Yes
[Nexus 4 Android Development] pinoyz:
Can anyone make franco's r209 cm compatible? Thanks!
[Nexus 4 Android Development] anandbibek:
One here http://xdaforums.com/showthread.php?t=2548897
[Nexus 4 Android Development] abalam:
Nice kernel. Perfect for cm. Keep up the good work man!!
[Nexus 4 Android Development] pinoyz:
Thanks for the link! :)
[Nexus 4 Android Development] stab244:
Faux_041u

Faux_041m

This has been tested by me and works fine. Mainline currently compiling. Will post link once it is done. It won't be tested however but it should work unless my computer decided to derp.

And just a notice to others who might still be using this (guessing not very many people do), I just ordered a OnePlus One (please don't ask for invites) so I don't know if I'll continue doing this. I will most likely keep my Nexus 4 but I have no idea currently. If I do I can still keep this up to date.
[Nexus 4 Android Development] natzy85:
I doesn't seem to be working on the mic gain part. It saves the setting on the Faux's Sound app but when opening the camera app and start to record after hitting stop camera freezes and the file gets corrupted. After this any camera app won't start and I have to restart. This only happens on CM. On stock everything works fine.
[Nexus 4 Android Development] aipaloovik:
Could someone be a dear and re-upload these?
[Nexus 4 Android Development] martinsjt:
I´m using the latest liquidsmooth rom and this kernel version saved the day :)

Thank You :good:
[Nexus 4 Android Development] anandbibek:
Anyone can confirm if this kernel works with latest PACman nightly?

Sent from my Nexus 4

---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------

So does this change make CM more incompatible with custom kernels now?

I'll keep an eye out when the next nightly breaks. Learnt a old lesson again yesterday.. ALWAYS TAKE NANDROID BEFORE

Sent from my Nexus 4
[Nexus 4 Android Development] thunder2k:
No need to nandroid.. Just flash back again the previous nightly.. In worst cases a format system.. But nothing more is needed IMO

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Android Development] ziddey:
Haven't looked too much into pacman. It doesn't look like there were any additional kernel changes, so it may be a ramdisk issue as well. If anyone has the last nightly that works and a recent one that doesn't, it'd be worth comparing the two ramdisks. I can take a look at that if someone uploads the boot.img from both.

The short version is yes, it does make CM more incompatible. However, it's a common debate as to who should have "jurisdiction" over the ramdisk. It does make sense that a custom rom would want to also make customizations to the ramdisk. The issue is that the ramdisk is bundled with the kernel to make boot.img. This is why the "anykernel" method came to be-- when the zip is flashed, it takes the existing ramdisk and the kernel to be flashed and creates a boot.img on the fly and flashes that. A lot of kernel devs have taken to using this method to release kernels (Faux for example). The issue is that this leads to a lot of confusion when switching to different kernels, especially when dealing with "reset" kernels.

Franco bundles a customized ramdisk as well (mainly for his interactive governor as well as some additional tweaks), which makes it difficult to fully support all the different roms that also customize the ramdisk. In the past, I have extended the "anykernel" concept to try and apply Franco's ramdisk mods on-the-fly during flash. However, this is a manual process on my end, comparing Franco's ramdisk to what I believe he based it on. Further, I'd then have to manually check for ramdisk changes with each release, and determine how to script it so they're able to be universally applied. Just a bit of a tedious effort that can potentially not work (what if rom X's ramdisk also made related changes, etc).

Of course as it stands already, CM (and of course all its derivatives) has a whole slew of additional kernel commits that aren't included. These two recent ones that have now become somewhat dubiously termed "the CAF commits" are the first to cause drastic usability issues. I can't speak as to whether or not any other commits are having any negative (or positive) impacts by not being included.
[Nexus 4 Android Development] Nathan-NL:
With the first kernel and 21 I get distorted speaker sound. Cyanogenmod kernel doesn't have this problem.
[Nexus 4 Android Development] anandbibek:
That's because Franco has increased speaker gain more than normal in his code. He did 15 instead of default 12. Check his thread to know more and fix the issue.

That's what I believe too, but the screwup was due to ramdisk, and probably bcoz of this, my problem persisted even if I flashed other nightly

Sent from my Nexus 4
[Nexus 4 Android Development] Nathan-NL:
Thanks for the good info.

Edit: I should note the distortion is not continuous.
[Nexus 4 Android Development] v12xke:
Confirming this modified kernel works with the latest cm nightly - cm-10.2-20131023-NIGHTLY.
[Nexus 4 Android Development] Alex93917:
Thank you OP ! :)
[Nexus 4 Android Development] mastel97:
So, can someone confirm that this works also with the latest pacman nightly?

Swyped from my Nexus 4
[Nexus 4 Android Development] ziddey:
Here's a test for pacman rom:

4.3: 2013.10.23 1450ET r191: [JWR] [JSS/JLS]

I diffed pac's ramdisk against cm's:

$ diff -r tmp/pac/rd/ ~/tmp/cm/rd1/ |more
Binary files tmp/pac/rd/charger and /home/ziddey/tmp/cm/rd1/charger differ
diff -r tmp/pac/rd/default.prop /home/ziddey/tmp/cm/rd1/default.prop
4,5c4
< ro.adb.secure=0
< persist.sys.root_access=3
---
> ro.adb.secure=1
Binary files tmp/pac/rd/init and /home/ziddey/tmp/cm/rd1/init differ
diff -r tmp/pac/rd/init.rc /home/ziddey/tmp/cm/rd1/init.rc
49c49
< export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/fra
mework.jar:[color=red]/system/framework/framework-pac.jar[/color]:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framewor
k/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar
---
> export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/fra
mework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framewo
rk/services.jar:/system/framework/apache-xml.jar:[color=red]/system/framework/telephony-msim.jar[/color]
224a225
> mkdir /data/misc/radio 0770 system radio
Only in tmp/pac/rd/: logo.rle
Binary files tmp/pac/rd/sbin/adbd and /home/ziddey/tmp/cm/rd1/sbin/adbd differ
Binary files tmp/pac/rd/sbin/ueventd and /home/ziddey/tmp/cm/rd1/sbin/ueventd differ
Binary files tmp/pac/rd/sbin/watchdogd and /home/ziddey/tmp/cm/rd1/sbin/watchdogd differ

Like how CM now has telephony-msim.jar in BOOTCLASSPATH, PAC has framework-pac.jar.

Realistically, going with an "anykernel" method is the only way to have a chance at supporting all these various roms (and even then, a missing commit in the kernel source could still have undesired effects).
[Nexus 4 Android Development] mastel97:
It works! :D

Thanks man, you're my hero of the day.

Swyped from my Nexus 4
[Nexus 4 Android Development] Tennic:
Should we use as well to the CM?

Or, with the CM, we should use the version of yesterday (4.3: 2013.10.22 1549ET r191)? :confused:
[Nexus 4 Android Development] NUNsLAUGHTER92:
The kernel for pacman works perfectly for the nightly on the 20th, thank you.
[Nexus 4 Android Development] ziddey:
I built faux's kernel with the two commits as well if anyone is interested in testing. If it works, I'll update the first post.

faux-027u-JSS-CM-ziddey.zip

I built https://github.com/faux123/mako/tree/jb_mr2_jss with the config extracted from 027u.

Note this is an "anykernel" and uses whatever the existing ramdisk is. Because of this, the BOOTCLASSPATH additions aren't needed. If switching from Franco, a "reset" kernel is recommended (reflash rom).

Built with arm-linux-androideabi-4.7, with bfd linker instead of gold. Forgot to reset .version before building so I believe it'll show #193. Can someone confirm if faux's 027 actually shows #27?
[Nexus 4 Android Development] kenshinta:
I'm using 10.23 JSS/JLS in combo with Vanir 10.20 , good so far except for an initial hiccup while booting it the 1st time, needed to wipe 2x.
[Nexus 4 Android Development] hasanandnexus:
[MENTION=584916]ziddey[/MENTION] flashed faux027 cm boot after "com.android.phone has stopped" please help :/
[Nexus 4 Android Development] defconoi:
Flashed [MENTION=3305976]Zidd[/MENTION]ley's faux27u kernel, works great
[Nexus 4 Android Development] anandbibek:
Please tell us your ROM and build version too. That gives actual useful information. :)

Sent from my Nexus 4
[Nexus 4 Android Development] Stryder5:
Can you please explain what we're looking for or what this statement means?
[Nexus 4 Android Development] bongostl:
I tried this on the newest Carbon build, but it boots up with the screen being REAL weird (nothing but the background showing, and it flickers on and off).

Anyone have a guess?
[Nexus 4 Android Development] nibblet787:
Works with faux and latest PAC nightly (10/21)! Woot! I did a clean wipe of the system partition first, but kept /data intact and had absolutely no problems on first boot. I also did not flash the old colorfix zip either, in case anyone asks.

EDIT: Forgot to add that I can't find anywhere that says it's faux #27. Not even on the device info page of his kernel control app, nor the About Phone section in Settings. Where else could I look?
[Nexus 4 Android Development] defconoi:
Sorry, running it with crdroid build 26
[Nexus 4 Android Development] defconoi:
Faux has a new kernel 28u hasn't been fixed yet
[Nexus 4 Android Development] DarkhShadow:
Which ISN'T public yet
[Nexus 4 Android Development] Stories:
Thanks. I used Faux 27u on the CM 10-25-13 nightly and it works great.
[Nexus 4 Android Development] Matt Devo:
hey ziddey, any chance you can do a build for faux's 27m JSS/JLS kernel? the -u kernels don't like my phone for some reason (lots of green screen crashes)
[Nexus 4 Android Development] XlAfbk:
Is there any chance to get a mod of Faux' JSS Stock Plus kernel? Would be greatly appreciated!
[Nexus 4 Android Development] uncola:
Wow this is working great with the LTE unofficial cm 10.2 nightly, jss franco version.. and touchcontrol actually works now
[Nexus 4 Android Development] karol1981:
Any chance to add support for otg in this kernel?

Wysłane z mojego Nexus 4
[Nexus 4 Android Development] thunder2k:
Hi, there is something with today build that broke compatibility with gamma correction and color profiles. Anyone else experiencing the same?

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Android Development] SilverMist1:
can you please add m version of faux kernel too?
[Nexus 4 Android Development] tupac4u:
Great work! I hope work on crdroid...Regards
[Nexus 4 Android Development] radzik2908:
Confirm, works on CrDroid, build 26.
[Nexus 4 Android Development] ziddey:
Franco:

4.3: 2013.10.26 2049ET r193: [JWR] [JSS/JLS]

I'm out the door now. Will look into mainline faux tomorrow. I'm assuming no one needs a JWR build?

Are there any roms that require the "CAF" commits -AND- a JWR kernel even?
[Nexus 4 Android Development] RTNDO128:
Does this work with the recent CM nightly builds?
[Nexus 4 Android Development] thunder2k:
Yes, I'm on latest nightly and this works flawlessly. Really thanks [MENTION=584916]ziddey[/MENTION]!

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Android Development] JG:
yes please make a JWR faux please!
[Nexus 4 Android Development] LordDeath:
Franco uploaded r193 again because previously it had an issue with deadlocks. :rolleyes:
[Nexus 4 Android Development] ziddey:
new: [JWR]
[Nexus 4 Android Development] SilverMist1:
is the faux m version coming? by the way thank you what you are doing is a real community service :)
[Nexus 4 Android Development] ziddey:
What ROM requires a JWR kernel with the commits?

Faux-CM: [027u-JSS] [027m-JSS] [027u-JWR] [027m-JWR]
[Nexus 4 Android Development] JG:
Deleted post ! no longer irrelevant to me ! thanx though::o
[Nexus 4 Android Development] ziddey:
"AOKPK is non-CAF" :confused:
[Nexus 4 Android Development] JG:
You know yesterday when I read this for some reason I understood it to be something else ,but after getting your response and re-reading it I realized this was something completely different than what Iu thouight it was and yes I already knew aokpk is De-Caf-enated and the official aokp now is as well but I should have read a bit further before posting .I heard something needed to be added in the Ramdisk you know the init.rc but that was a mistake I read something wrong in and in the wrong thread and then I came accross your thread and thought it was needed but now I know is not,after comparing those commits the OPand by your comment so thanks for catching that for me Bro..:D
[Nexus 4 Android Development] SilverMist1:
thank you for faux 27m version
[Nexus 4 Android Development] betobm:
hi guys, i have a question if anyone can help...

i'm on the last nightly that supports the original faux and its working fine (colorfix flashed too). i tried to update to 26/10 CM10.2 (wiped dalvik and cache) and flash the faux CM compatible from this thread but i got stucked on the google logo.

what should i do? anybody had the same problem? do i have to flash any reset kernel before the cm compatible faux? :confused:

thanks and sorry for the bad english!
[Nexus 4 Android Development] EnginEAR:
Good luck!!!

If you use CWM I would suggest that you also go to mounts/storage and format the system partition. I didn't reboot into recovery to write this so the actual options might have different titles.

After wiping cache and dalvik and formatting system you can flash the latest nightly and kernel from this thread and it'll work. DO NOT FLASH THE COLOR FIX ZIP!!!

Good luck!
[Nexus 4 Android Development] thunder2k:
Wait, if you're using the modified kernel from this thread, you must revert the colorfix. To cut a long story short, you must use the liboverlay.so from the latest cm nightly zip and delete any backup script in addon.d directory.

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Android Development] arlenwoot:
Delete /system/addon.d/95-cm.sh

It's left behind from the colorfix zip and doesn't get removed when you flash a new rom.
[Nexus 4 Android Development] betobm:
Worked just fine!

Thank you so much!

** I have to reinstall GAPPS after this procedure, just in case for users with same problem...
[Nexus 4 Android Development] GalaxyGusta:
I confirm this work with crdroid build 26
[Nexus 4 Android Development] gabriel_hart:
Ahh... back on CM w/ FK. Thanks for putting this together [MENTION=584916]ziddey[/MENTION]!
[Nexus 4 Android Development] arlenwoot:
Anyone else noticing increased deadlocks with 193 on cm? Pre 193 I hadn't had any deadlocks for weeks, but with 193 I started getting a few everyday. Currently using 10/27 nightly and late last night I went back to 191 and so far haven't had any issues.

Noticed in the actual franco.Kernel thread a few people have reported issues with deadlocks so I don't think the problem I'm having is related to using this special build for it to work with cm.
[Nexus 4 Android Development] Stryder5:
Faux 027m JSS working great with PACman ROM (10/28 nightly). Works fine with Touch Control too :) Thanks ziddey!
[Nexus 4 Android Development] ziddey:
Franco had accidentally merged one of the JSS commits into the JWR branch, which resulted in deadlocks for JWR users. It was swiftly removed and rebuilt.

Other than that, there's nothing that would have affected deadlocks one way or another. Just a coincidence. I went deadlock free for over a week at one point, only to hit deadlock after deadlock after deadlock while trying to type one reply in tapatalk. Pretty frustrating.

There was some talk about the last two commits to the CM msm kernel helping some with deadlocks (probably merely speculation though..): https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-10.2
[Nexus 4 Android Development] arlenwoot:
Yeah just a coincidence I guess. Weird how the deadlocks come and go like that. Thanks.
[Nexus 4 Android Development] saint_cow:
What faux kernel do I use with the latest cm10.2 nightly now?
[Nexus 4 Android Development] Jur1nator:
27 u/m JSS...

But I would wait until op updates to v. 28 wich is out since a few hours ;p
[Nexus 4 Android Development] ziddey:
Faux: [028u-JSS] [028m-JSS] [028u-JWR] [028m-JWR]
[Nexus 4 Android Development] EnginEAR:
Confirmed + Thanks

Confirmed: Working very well with CyanogenMod 10.2 Nightly (October 29th, 2013).

Thanks, [MENTION=584916]ziddey[/MENTION]!!!
[Nexus 4 Android Development] klutch:
Ziddey ur the man bro!!! thumbs up kep the work :good::D
[Nexus 4 Android Development] muzaffarkhan95:
Nexus 4

which of these will support touch control? on PA 4.3 rom???
[Nexus 4 Android Development] Luigi_2:
Hi OP, could you please consider a version for Semaphore kernel aswell? That's a really really good kernel.
[Nexus 4 Android Development] XlAfbk:
any chance for Faux JSS Stock Plus Kernel?
[Nexus 4 Android Development] ziddey:
oh dear. might just be me but it looks like cm1031 results in black screen.

edit: never mind, was a freak occurrence. reflashed and it's fine now

edit: hmm, be careful everyone. 10/31 ramdisk is the same as 10/27. no new kernel commits. but there seems to be an issue.