yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] phishn:
This kernel is awesome. Only issue I have is that bluetooth audio occasionally skips with the screen off, r17. The culprit seems to be when Mms messages come in. My device might not like the lower voltage changes. Nice work again Boype, stability wise I have yet to see a bootloop running this days straight with heavy use.
[Samsung Galaxy Nexus] boype:
I have been looking into this just a little. Do you have content adaptive brightness disabled (default) or enabled? If it is disabled, try enabling it and please report if the problem is still there. This goes to anyone having the "dark screen on wakeup" problem :)

Also, I have tried to reproduce the issues with occasional mp3 choppiness with screen-off (e.g. with poweramp). I cannot reporduce the issue, but it may have to do with the slightly lowered voltage.

[EDIT]

I have made a test build (standard version), which hopefully fixes the mp3 choppiness / bluetooth screen-off issues, as well as the dark screen on wakeup issue. Please test and report.

Link: http://boypetersen.de/fancykernel/tst/fancy_kernel-tuna-4.2-tst-std.zip
[Samsung Galaxy Nexus] phishn:
I'll try out the test build. Just to clarify, screen off with earbuds is fine for me. It's the bluetooth addition that makes it skip/fade momentarily which makes me believe that it's the extra voltage using the bluetooth that's doing it for me. If it's not replicable it's my device which I'll have to tweak settings. I am using poweramp too.
[Samsung Galaxy Nexus] gwindlord:
boype, I've checked out the sources, but do not know what to do to build your kernel :) ./configure says there is no such file, scripts/config says I have to define properties and there are many scripts... How can I just make kernel with latest changes? :)
[Samsung Galaxy Nexus] yyz71:
Flashed this on my girls nexus it's really smooth and i like all the governors option that you added :good:So is there a chance that this kernel will make it's way over to the nexus 4? Right now I'm using Air Kernel which i missed after getting my n4 but dr_data made his way over to the n4 forums:cool:
[Samsung Galaxy Nexus] boype:
get Android NDK and extract the arm-linux-androideabi-4.7 toolchain

get mkbootimg for tuna and extract it

git clone git@github.com:boype/kernel_tuna_jb42.git

cd kernel_tuna_jb42

make CROSS_COMPILE=/path/to/google-toolchain/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- ARCH=arm fancykernel_std_tuna_defconfig -j2

make CROSS_COMPILE=/path/to/google-toolchain/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- ARCH=arm -j2

copy the freshly compiled /kernel_tuna_jb42/arch/arm/boot/zImage to the mkbootimg folder

git checkout fancykernel-RAMDISK

copy the RAMDISK files to some folder in the mkbootimg folder, e.g. RAMDISK

cd mkbootimg

./repack-bootimg.pl zImage RAMDISK/ boot.img

the flashable boot.img is in your mkbootimg folder

This is a very brief description, hope you'll get it right. You probably get errors during the process because you may miss some required packages... If you don't know what the problem is, report back :>

Sorry, I don't have a nexus 4...
[Samsung Galaxy Nexus] RW-1:
Awesome job! R54 on Shiny ROM (toro) ...
[Samsung Galaxy Nexus] boype:
[MENTION=4920659]namtombout[/MENTION] [MENTION=1097461]siealex[/MENTION]

Have you tried my attempt to fix your issues already?

http://xdaforums.com/showpost.php?p=54784724&postcount=8764
[Samsung Galaxy Nexus] SoftWord:
Any news about synapse compatibility?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] aliesz:
Hi boype, I flashed the test_anykernel2 version on stock 4.3 android and everything works very well. No bootloop or internal storage problem exist. Thanks alot boype.[emoji4]
[Samsung Galaxy Nexus] boype:
Does connecting your phone with your pc work in usb storage mode? Another user PM'ed me and said he was getting FCs
[Samsung Galaxy Nexus] aliesz:
Yes I connected my phone to pc and the pc recognized the phone's storage. I have not FC till now.
[Samsung Galaxy Nexus] aosp:
[MENTION=4615478]boype[/MENTION] Have you tried merging in [MENTION=2633638]Ziyan[/MENTION] omapzoom 3.0 updates into fancy? https://github.com/Ziyann/omap/tree/stable
[Samsung Galaxy Nexus] namtombout:
Sorry for the delay. Cm 10.1.3 no internal storage access using the test kernel. Flashed stock cm kernel before flashing the test kernel.
[Samsung Galaxy Nexus] osm0sis:
I've heard that you can work around it by disabling the lock sounds. :good:
[Samsung Galaxy Nexus] motorazrv3:
I will test it but I am pretty sure lock sound is already disabled.

Du provided a new maguro version, maybe fixed from rom side now.

Or time to try a new rom. Carbon has got no audio stutters as mentioned here.
[Samsung Galaxy Nexus] osm0sis:
Nah I have them on Carbon. It's just from it trying to play the lock sound over the music stream. It's pretty much universal, like boype said. Very much a ROM thing.

And I can confirm the workaround does the trick here. :good:
[Samsung Galaxy Nexus] boype:
I have the lock sound disabled with cm11 and still experience the bug sometimes. I suggest deleting or renaming the lock sound itself might help as well?!

/system/media/audio/ui/Lock.ogg
[Samsung Galaxy Nexus] FredFS456:
I just made the jump from Franco.Kernel and I have to say, I'm pretty impressed. I figured F.K should go as it definitely seems like Franco is no longer really developing for the Gnex. After I flashed Fancy, my phone now feels much more reponsive than it did before. I currently have PA4.5beta2 and Fancy r54 with ZRAM on, and one thing that I definitely noticed was that the beautiful new Recents screen in PA seemed to respond much much better than on F.K. Good job, and keep it up!
[Samsung Galaxy Nexus] chinarobin:
c rom have the same problem, maybe the battery saving cause that problem.
[Samsung Galaxy Nexus] Ashtrix:
I've also had that issue of stutter while screen wakes up or locks it was since 4.4 (slimkat since 4.4), i guess it's a known bug for our device..:rolleyes:
[Samsung Galaxy Nexus] boype:
Okay, thanks. Could you grab a logcat / kmsg for me? Because I honestly don't know what's wrong and that might give a clue.

[MENTION=4544860]osm0sis[/MENTION]: It appears this is not USB OTG related (the entry in the fstab was removed for testing). Do you have any ideas?
[Samsung Galaxy Nexus] osm0sis:
Does deleting all the fstab files work for [MENTION=4920659]namtombout[/MENTION]? That would at least narrow it down to the fstabs. Then I'd compare the CM10.1 fstab/etc. to see what the problem is, if so.

Edit: Hmm things were pretty damn simple back then.. ;)

https://github.com/CyanogenMod/android_device_samsung_tuna/tree/cm-10.1?files=1

I guess the next step would be to flash the 10.1.3 kernel and manually unpack it, compare the permissions, run the AnyKernel2 commands on it, compare again to make sure it all applied correctly and the permissions match.

Edit 2: [MENTION=4615478]boype[/MENTION], has this always been a problem for you on AnyKernel2, or just since you added Unified f2fs/ext4?
[Samsung Galaxy Nexus] GilGameshn1:
[MENTION=4615478]boype[/MENTION] ... Hi bro ... Thanks for this blazing fast kernel ... I am very happy with it till new 8/11 LS released and I tried your kernel ... I have random SOD here and there ... The missed calls can be seen through led light notification ... So I think there is something wrong with display voltages ... After some reboots device freezes and battery pull in order ... Reflashed r53 and device come to cool again ... Wondering what is wrong . ? kernel sided or not ?

Edit : turned back again to DirtyV ... Really need my device for now ... I wish I could test it more ... It is very cool if you add synapse support ... Thanks man .?
[Samsung Galaxy Nexus] boype:
Thanks for the input. That would have been my next steps anyway. Thanks for the gihub link too. I'll reduce the fstab to those entries for 4.2 ROMs and we'll see if that's any good.

Ugh that's nasty. Are you saying that r54 worked fine until you installed the new ROM (11-08)? Because as far as I can tell and see from reports, r54 is rather stable
[Samsung Galaxy Nexus] hp13:
I confirm the shutter bug while listening to Music and locking the screen. using PA 4.45 and Fancy r54.
[Samsung Galaxy Nexus] infectedorganism:
That is the same working fstab that is currently on my 4.2.2 ROM; Slim Bean 4.2.2, Build 8.

Also, this may not be noteworthy, but looking at the fstab-ext4.tuna that is present in r54, the path for the USB storage device doesn't exist on 4.2.

The fstab in r54 has this listed as the path:

/devices/platform/omap/musb-omap2430/musb-hdrc

But on 4.2, the "correct" path is:

/sys/devices/platform/omap/musb-omap2430/musb-hdrc

I tried changing the path and flashing r54 again, but it had no affect on retaining access to the internal storage.

I'm not offering much insight, just trying to help when/if I can.
[Samsung Galaxy Nexus] osm0sis:
The OTG path is just like that. It's the same (and working) on 4.3-4.4, it just starts its search in /sys I guess.

Removing the extra fstab entries on 4.2.x will probably fix it, like boype was saying. :)
[Samsung Galaxy Nexus] mangusZen:
R54 is very very stable here in carbon, blazing fast and great battery life.

I had a lot of annoying freeze when I was on f2fs (system partition included) but now after a deep clean flash in ext4 I have probably the best experience ever.

Thanks [MENTION=4615478]boype[/MENTION]
[Samsung Galaxy Nexus] boype:
To both of you and everyone else having trouble with no internal storage access on Android 4.2: Please try this file on top of a clean kernel (e.g. achievable by dirty-flashing your ROM):

https://dl.dropboxusercontent.com/u/2652503/fancy_kernel-tuna-4.2%2B-r54-test3-anykernel2.zip

Fixed now? :confused: :D
[Samsung Galaxy Nexus] infectedorganism:
No access to internal storage after flashing test3.
[Samsung Galaxy Nexus] boype:
:eek::eek:

Can you post the content of the fstab that is in place with test3? You need to do that with adb I guess, since file managers won't work without access to internal storage (?):

adb shell

cat /fstab.tuna
[Samsung Galaxy Nexus] infectedorganism:
The contents appear to be the exact same as fstab-ext4.tuna that was provided in the zip.

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,noatime,barrier=0 wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/omap/omap_hsmmc.0/by-name/metadata
/dev/block/platform/omap/omap_hsmmc.0/by-name/misc /misc emmc defaults defaults
/dev/block/platform/omap/omap_hsmmc.0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/omap/omap_hsmmc.0/by-name/sbl /sbl emmc defaults defaults
/dev/block/platform/omap/omap_hsmmc.0/by-name/xloader /xloader emmc defaults defaults
/dev/block/platform/omap/omap_hsmmc.0/by-name/radio /radio emmc defaults defaults

/devices/platform/omap/musb-omap2430/musb-hdrc auto auto defaults voldmanaged=usbdisk:auto
[Samsung Galaxy Nexus] osm0sis:
Nice. That explains everything I think! :)
[Samsung Galaxy Nexus] namtombout:
logcat using vanir 4.2.2 and test 3 kernel

http://pastebin.com/v68v0tgE

cat /fstab.tuna using vanir 4.2.2 and test 3 kernel

http://pastebin.com/FH5i8ESa
[Samsung Galaxy Nexus] aosp:
[MENTION=4615478]boype[/MENTION] If you missed it http://xdaforums.com/showthread.php?p=54809649 ?
[Samsung Galaxy Nexus] boype:
[MENTION=4920659]namtombout[/MENTION] [MENTION=4078274]infectedorganism[/MENTION]

First of all, thank you for your effort!

https://dl.dropboxusercontent.com/u/2652503/fancy_kernel-tuna-4.2%2B-r54-test4-anykernel2.zip

This really ought to work now!!

Could you test again, pretty please? :highfive:
[Samsung Galaxy Nexus] osm0sis:
USB OTG was done differently in 4.2, so you'll still want to chop that out too; I think it was entirely handled in init.tuna.rc back then. Might need to swap the first auto in the line for vfat on 4.3 as well, that or try and insert the sdcard binary lines into init.tuna.rc to see if 4.3's binary can handle the new method.

Tried to sum it up a bit more concisely, plus allows you to easily add in compatibility fixes for other versions, what do you think?:

[ edit: removed; better version below ]

I'll probably bring this over to DirtyV, not that anyone uses our AnyKernel2 zip. :p
[Samsung Galaxy Nexus] namtombout:
no access with test 4. On my initial trial with the original r54 anykernel i deleted only the fstab files and not the fscheck file. No storage access until i deleted fscheck also.

Possible something wrong with fscheck?

Edit: tried older twrp and cwm and still no access
[Samsung Galaxy Nexus] osm0sis:
Nah. fscheck will just murder your fstab if you don't remove it along with the others since it's there to swap the ext4 entries for the f2fs ones. ;)

USB-OTG changes through the ages:

https://github.com/CyanogenMod/android_device_samsung_tuna/blob/cm-10.2/fstab.tuna

https://github.com/CyanogenMod/android_device_samsung_tuna/blob/cm-11.0/fstab.tuna

Looking like we'd need a fix for 4.3 as well..

Edit: If you've got a few minutes, I'll take a stab at fixing it real quick. Hold on. :)
[Samsung Galaxy Nexus] osm0sis:
Alrighty! Give this a spin! :cowboy:

Flash it over your ROM's default ramdisk (ie. flash your ROM's boot.img first), to make sure we're running clean.

If it still doesn't work then please give me a cat of your init.tuna.rc and fstab.tuna while booted. :good:

[ Attachment removed ]
[Samsung Galaxy Nexus] namtombout:
[MENTION=4544860]osm0sis[/MENTION] stuck at google logo. woah.
[Samsung Galaxy Nexus] osm0sis:
Balls. So much for that. Too aggressive I guess! :eek:

It probably killed the fstabs by mistake. I'll see if I can figure out why that's happening now.

Edit: Double checking all the changes in recovery manually now; anyway, I think we're close.

Edit2: Yup, it's just the funneling of the grep output back to the file that it's reading causing problems. Working out a fix.

Edit3: [MENTION=4615478]boype[/MENTION] This ought to do the trick!:

# fstab-*.tuna (backward compatibility for Unified f2fs/ext4 support)
android_ver=$(mount /system; grep "^ro.build.version.release" /system/build.prop | cut -d= -f2; umount /system);
case $android_ver in
4.2*)
for i in fstab-*; do
filetmp=`cat $i`; echo "$filetmp" | grep -viE "misc|boot|recovery|sbl|xloader|radio|usb" > $i;
done;
;;
4.3*)
for i in fstab-*; do
replace_string $i "/storage/usbdisk" "musb-hdrc auto auto" "musb-hdrc /storage/usbdisk vfat";
done;
;;
esac;

Finishing testing and I'll post another zip shortly. :good: :D
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4920659]namtombout[/MENTION] [MENTION=4078274]infectedorganism[/MENTION]

It definitely performs the changes correctly now. Fingers-crossed, boys! :fingers-crossed:

[ Attachment removed since boype's got r55-test out with the fixes included ]
[Samsung Galaxy Nexus] infectedorganism:
It works; internal storage is accessible after flashing!
[Samsung Galaxy Nexus] osm0sis:
F*ck yes! :highfive: :victory: :D
[Samsung Galaxy Nexus] infectedorganism:
Thank you [MENTION=4615478]boype[/MENTION] and [MENTION=4544860]osm0sis[/MENTION] for taking the time and having the knowledge to track down and fix an issue that so few of us had. It is very much appreciated. Respect.
[Samsung Galaxy Nexus] osm0sis:
:)

I enjoy a good puzzle! ;) :p

Thanks to you and [MENTION=4920659]namtombout[/MENTION] for all the patient and helpful testing over the last couple days/weeks until we could sort it out! :highfive:
[Samsung Galaxy Nexus] Cano IV:
I never felt my Gnex so smooth, thanks for your effort [MENTION=4615478]boype[/MENTION] :victory:
[Samsung Galaxy Nexus] boype:
... finally! :D
[Samsung Galaxy Nexus] boype:
[MENTION=4544860]osm0sis[/MENTION]

Seems like you overlooked this in your commit at the dirtyv repo:

# repack ramdisk then build and write image
write_boot() {
cd $split_img;
cmdline=`cat *-cmdline`;
[B] if [ $androidmajor -ge 4 ]; then
cmdline="androidboot.selinux=permissive $cmdline";
fi;[/B]
base=`cat *-base`;
pagesize=`cat *-pagesize`;
cd $ramdisk;
find . | cpio -o -H newc | gzip > /tmp/anykernel/ramdisk-new.cpio.gz;
if [ $? -ne 0 ]; then
write_status 4;
fi;
$bin/mkbootimg --kernel /tmp/anykernel/zImage --ramdisk /tmp/anykernel/ramdisk-new.cpio.gz --cmdline "$cmdline" --base $base --pagesize $pagesize --output /tmp/anykernel/boot-new.img;
if [ $? -ne 0 ]; then
write_status 5;
fi;
dd if=/tmp/anykernel/boot-new.img of=$block;
if [ $? -ne 0 ]; then
write_status 6;
else
write_status 99;
fi;
}

Explanation: The kernel needs to be compiled without the "androidboot.selinux=permissive" command in the defconfig's CONFIG_CMDLINE, or else many (some? all?) 4.3 ROMs will get stuck at bootscreen. This was reported a few pages back by [MENTION=5421988]aliesz[/MENTION], whose problems were fixed after removing that command from the kernel. However, Android 4.4 will boot in 'enforcing' mode if this is not set in some way. The boot.img's CMDLINE is concatenated with the kernel one's, that's why it's working this way.

[MENTION=2592033]nailz420[/MENTION]: Thanks, mate :) I added you to the list in the OP. Second donation even!

I'll cherry-pick some commits if I find the time. It's too much to merge I guess, plus I'm afraid stability is compromised by implementing hundreds of changes.

I have no plans for an implemetation yet...
[Samsung Galaxy Nexus] macravin:
I'm getting SODs, I've tried increasing the voltage, but it doesn't work, does anyone have any ideas?
[Samsung Galaxy Nexus] thecoolkid:
I got freeze overnight while sleeping, charged my phone, disconnected from the charger and when I woke up it was dead... cm11 f2fs, fancy r54, haven't had an issue with pre54-3...
[Samsung Galaxy Nexus] macravin:
I get a blacked out screen, adb still works, but nothing else does. I've had it on 53 54-3 and now 54.
[Samsung Galaxy Nexus] bsmitty83:
If you have adb access while it happens , I'm sure [MENTION=4615478]boype[/MENTION] would appreciate a logcat and dmesg [emoji106]

I'm kind of curious myself .........
[Samsung Galaxy Nexus] aliesz:
After flashing of r54- test anykernel2 ( the first test version for 4.2+ ROMs) on JB 4.3 stock ROM my phone have been very smooth and stable without any problems such as bootloop or internal storage in two days. The battery consumption is very low and performace on antutu benchmark is good. Is it necessary to flash newer test versions test4 or osmod?!
[Samsung Galaxy Nexus] AgentSmith:
This kernel just put a stop to weeks of huge lag with recent CM11 nightlies. Thanks Boype for bringing my phone back to life!
[Samsung Galaxy Nexus] osm0sis:
Ah, thank you! I missed it tucked away in write_boot! ;)

[MENTION=4608636]bsmitty83[/MENTION] can change the build and mkbootimg command lines in his setup and I'll fix the AK2 part for the older ROMs. :)

Feel free to use our implementation of Synapse, by the way. I've simplified it a lot from what I've seen on other GN kernels: All you need is my /sbin/uci and the single line in the bootscript to run it. Then all the files in /res/synapse/ of course! You wouldn't need to change much, maybe just remove the suspend_trim toggle in Misc if you don't feel like adding that feature back. :good: :D

Edit: [MENTION=4615478]boype[/MENTION] Oh and you'd need to add back the controls for UKSM instead of KSM. They're in the commit history for the Advanced config file. ;)

Only difference on 4.3 would be mine should have USB-OTG working again. :good:
[Samsung Galaxy Nexus] siealex:
Will it work on PA 3.99?
[Samsung Galaxy Nexus] osm0sis:
I'd imagine so.
[Samsung Galaxy Nexus] Bazzu:
Guys i'm running last omnirom nightly and i would like to ask you if you can give me (if possible) some suggestions about kernel tweaks? maybe a link? Beacuse i'm experiencing few lags with stock settings of r54 :(

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Charmacas:
The only thing I change is the MCPS setting from 2 to 0. Except that everything's stock and I don't have any lag at all. [MENTION=4615478]boype[/MENTION] outperformed himself with the latest kernel version. r54 is the smoothest kernel you can use right now. (Personal opinion!)

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] Bazzu:
And what rom are you running now?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Charmacas:
PA 4.5 B2 (all ext4)

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Yeah, didn't Franco say MCPS is terribly broken on OMAP4460?
[Samsung Galaxy Nexus] GilGameshn1:
Is there anyway to remove it from settings ... It could be available for scripts ... But for people it is better to not there ... It is useless feature I think . Thanks in advance . ?
[Samsung Galaxy Nexus] osm0sis:
Not useless, just broken for us, if what Franco said still holds.

Disable it via init.d or a tweaking app. Per usual. :good:
[Samsung Galaxy Nexus] Osid:
MCPS stands for...?

How can we disable it? TricksterMOD? Sysfs entry involved?
[Samsung Galaxy Nexus] motorazrv3:
Maybe multi core power save,

I don't know. Something on mind!

You can disable it with trickster mod. As described just set it to 0.
[Samsung Galaxy Nexus] GilGameshn1:
Is CAB broken too ... Or buggy ... [MENTION=4544860]osm0sis[/MENTION] ... Or it is OK now ... I remember some Q/A in earlier DirtyV that it is broken ... Is it universal in every kernel ... ? I am curious .
[Samsung Galaxy Nexus] siealex:
Yes, it gives spontaneous reboots if switched on or off in standby mode.
[Samsung Galaxy Nexus] namtombout:
I know Franco is a legend but I can't doubt anything boype does. He's dedicated and if he implemented it you can rest assured it does something positive.
[Samsung Galaxy Nexus] joelmonty:
I've tried flashing all the versions of the any kernel 2 on 4.3 , one posted on op and osmosis, but none of them are working , it's getting stuck at boot animation, I'm using stock Google 4.3 and I'm flashing these kernel after dirty flashing Rom and after rebooting once.
[Samsung Galaxy Nexus] aliesz:
There was the same problem on my phone but I suddenly found a strange way. when I have old r43 fancy kernel on 4.3 stock ROM and dirty flash the new r54 builds then wipe cache and dalvik cache, it works correctly and my system boots successfully and my phone starts to fly! :fingers-crossed:
[Samsung Galaxy Nexus] boype:
Does this work?

https://dl.dropboxusercontent.com/u/2652503/fancy_kernel-tuna-4.2%2B-r55-anykernel2.zip
[Samsung Galaxy Nexus] aosp:
Flashing the ROM .zip first before the anykernel2 .zip seems to boot everytime
[Samsung Galaxy Nexus] qtoo941:
I am using Cataclysm ROM 4.3 with Mpokang 1080p kernel. I wanted to flash latest Fancy_r54_anykernel2 so i downloaded the zip provided by [MENTION=4544860]osm0sis[/MENTION] with fixed OTG. First i wiped only dalvik and cache and flashed fancy but my phone was booting like 30 minutes. After that i saw what [MENTION=4615478]boype[/MENTION] has written about anykernel and ramdisk so i dirty flashed once again cataclysm, rebooted and i saw that i got original kernel from cataclysm. Went back to recovery, wiped cache and dalvik and flashed r54_test4_anykernel2 by osm0sis.. Phone rebooted, loaded all 101 apps i got on my phone and after loading the last app the phone rebooted by itself. And guess what - it didn't want to boot this time. There is something wrong. So now i am back to Cataclysm with Mpokang 1080p kernel.. Damn, i wanted to flash Fancy.
[Samsung Galaxy Nexus] joelmonty:
That's on 4.4 , I'm trying it on 4.3, thanks Boyle, will try and revert.