yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] infectedorganism:
If we're talking about the same thing, I'm experiencing it on ext4. It has only happened while using Spotify -- the screen freezes completely and while the music continues to play, the phone remains unresponsive, requiring a battery pull.
[Samsung Galaxy Nexus] taylerdurden:
Hi boype. I use CM11 in EXT4. I was doing nothing with the phone (I was sleeping), only had some notifications making the led blink
[Samsung Galaxy Nexus] Osid:
[MENTION=4615478]boype[/MENTION] , what about integrating in Fancy Kernel new logic to bind with new GPU drivers from TI, as explained in this XDA article?
[Samsung Galaxy Nexus] pa.pn2:
Wow demanding this in every thread. I think the developer will be integrate as soon as possible. Be patient dude
[Samsung Galaxy Nexus] Conte Mascetti:
Read the previous page of this thread, you'll find some answers

From GNexus
[Samsung Galaxy Nexus] Osid:
I'm demanding this in both threads ROM + kernel, 'cause change involves both parts and I'm using ShinyROM and Fancy Kernel ;)

It's only a proposal, I'm not asking an ETA :)
[Samsung Galaxy Nexus] pa.pn2:
Ok :)

Im on shiny too:) works great
[Samsung Galaxy Nexus] boype:
I bet these are all symptoms of one and the same problem.
[Samsung Galaxy Nexus] RW-1:
I'm on shiny as well, ext4, but not yet had the issue, but most likely you're right.

Could it be tied to whether or not someone has a 3rd party app running notifications instead of "stock" ? (I.E. I use Light flow ...) Just tossing that out there.

Great work as always, I'm sure you'll quash it.
[Samsung Galaxy Nexus] 11zeno11:
I've been in full ext4 configuration for a while and now I have data and cache in f2fs. I've tried all your kernels and I can confirm that the sod problem with the f2fs fs is more frequent.
[Samsung Galaxy Nexus] pianistaPL:
I was using Omni with Fancy r58 and full f2fs and I hadn't any SOD's.
[Samsung Galaxy Nexus] lollipop:
same, here full f2fs and no sod
[Samsung Galaxy Nexus] spacemanr:
PA beta 3 fancy 58, no SOD for a long time.

Over Tapatalk
[Samsung Galaxy Nexus] aliesz:
I am also using OmniROM with fancy r58 but in ext4 filesystem and everything works fine and without any SOD.
[Samsung Galaxy Nexus] rrusso:
Wich version are you using? Im trying to install but gets a lot of errors after boot (system crash....)
[Samsung Galaxy Nexus] spacemanr:
The most basic version as it can be :), no f2fs or any changes, just pure rom + fancy kernel and that's it. Not enough knowledge to mess with all the other possibilities :/.

Over Tapatalk
[Samsung Galaxy Nexus] wkr.mky:
I'm on full F2FS. Past few days was running Fancy r58 with unOfficial Liquidsmooth with no problems. Trying Omni Nightly today (just for change) and trying init.d tweaks with r58. Still running great. Playing games like Tower Dwellers and Hellraid, tweaking photos, listening to music and Zombies RUN! ^_^ Enjoying every second, many thanks.
[Samsung Galaxy Nexus] Rezzha:
im on PA latest rom with fancy tuna r54, how about the r58 performance for gaming? if that better i would like to upgrade my kernel
[Samsung Galaxy Nexus] AquilaDroid:
A nandroid backup and kernel flash will take less than 5 minutes - why not try it out and report back?

From my Nexus 5
[Samsung Galaxy Nexus] boype:
r59

Hi there,

so here it is (check the OP for download links).

I hope this will remedy any remaining instabilities some experienced (SODs).

Oh and for the f2fs users, this will be fun, too: there's a mount option that has been removed, effectively unleashing the full write speed. I got 10,7 MB/sec now instead of 6-7 MB/sec in androbench :) I'm not much of a benchmark guy, but this is definitly good stuff.

Change log:

filesystem sync reverts (just a few minor backports that could cause instabilties)

f2fs: remove crippling flush_merge mount option. enjoy the full write speed.

ext4: adjust inode readahead

dirty_writeback tweaks
[Samsung Galaxy Nexus] cujo6801:
Thanks a lot and loving your kernel on Poo's liquidsmooth unofficial Toro

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Rushead:
Please don't quote the OP.

And I don't want to be a d!ck, but how about throwing some thanks out to [MENTION=4615478]boype[/MENTION] from whom you're asking a favor?
[Samsung Galaxy Nexus] motorazrv3:
I am very excited and downloading r59 right now.

Lets see what more we all will get in combination to r58.

I mean I don't use f2fs file system. Still using ext4 and I don't had any stability problems on vanir rom in combination with r58.

Thx again boype for the new kernel.
[Samsung Galaxy Nexus] aliesz:
Hi boype, I think we are going to infinity with your kernel! ;)
[Samsung Galaxy Nexus] spacemanr:
Well I must say I hate this kernel, it is killing every will to switch my Galaxy Nexus for something new :).

Over Tapatalk
[Samsung Galaxy Nexus] x3m.zone:
Just haved 3 restarts in a row. One when opening Tapatalk, one when unlock de screen, and one when batt low popup message appear. Switched back to r58...all fine. Weird...
[Samsung Galaxy Nexus] pianistaPL:
Logs... ;)
[Samsung Galaxy Nexus] boype:
ext4 / f2fs?

(please provide logs if possible)
[Samsung Galaxy Nexus] Conte Mascetti:
thanks [MENTION=4615478]boype[/MENTION] kernel works great as usual, but still no battery percentage when device is turned off and under charge. No problems with R57 instead, percentage is there. I'm on CM11 nightly.
[Samsung Galaxy Nexus] thomstrack:
One more time, r59 running really great on ShinyRom. You are amazing [MENTION=4615478]boype[/MENTION], thanks! :)
[Samsung Galaxy Nexus] boype:
I believe you that the issue is there, but there's no logical reason why it would work correctly in r57 and does not work in r58+. There have been no changes that may have triggered that. :confused:

[edit] strike that. the charger binary in the ramdisk has been changed with the RAMdisk import from CM11 2014-10-04. Funny... Why would the damn charger binary be changed at all? I suppose it has always been the same since the GNex was released :o

[edit2] Supposing that your ROM's charger binary is okay, you could dirty-flash your ROM and then install the anykernel2 version. That way you should be fine
[Samsung Galaxy Nexus] cujo6801:
Deleted....
[Samsung Galaxy Nexus] boype:
To everyone involved in this argument: Stop this right now, keep the thread clean. Feel free to continue using PMs.
[Samsung Galaxy Nexus] Conte Mascetti:
LOL I just finished to logcat my Gnex and was going to send it to you, well ok then I try anykernel version.
[Samsung Galaxy Nexus] sgspluss:
Saw new update and flashed it, dont had any sod on r58 BUT every update are welcome :)

Thank you once again [MENTION=4615478]boype[/MENTION] :good:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Loureiro:
Hell yeah. Hail to the champion.
[Samsung Galaxy Nexus] Conte Mascetti:
Tried with this procedure but doesn't work because CM itself doesn't have "charge percentage" anymore... So I flashed R57 then anykernel2 R59, charger binary is untouched and percentage is there.... now I understand why is CM fault. So question is spontaneous: there's anything you can do about it? (obviously no ETA), even though I'm ready to do all this stuff everytime you update Fancy

Thank you [MENTION=4615478]boype[/MENTION]
[Samsung Galaxy Nexus] 7175:
Thanks boype for R59, running great on Vanir 4.3.1 ext4.

Also for anyone interested in testing synapse with Fancy R59, I added it into the anykernel.zip attached. I fixed some bugs from the last time I posted. Any incompatible options have been removed, and I added general io tunables.

edit: added new synapse options, full io-sched tuanables, kernel/profile backup/restore, devtools, advanced memory/oom adjustments, other /proc/sys stuff

Also built a smaller musl libc busybox for synapse to use (~150KB).

edit2: added version4 attachment. If you don't have an init.d script to start /sbin/uci, this has it appended to fancyinit2. Sorry forgot to mention this. Also changed attached synapse.apk to latest version.

edit3: Fixed issues with 4.4.x not running synapse scripts properly.
[Samsung Galaxy Nexus] boype:
I tried to build with Google GCC 4.9 some time ago, but the kernel image won't boot. Opposed to that builds with Linaro 4.9 boot fine. However, The toolchain I've been using for quite some time now (Google GCC 4.7 androideabi) somehow generates the smoothest and fastest kernel images. Note that this is a subjective feeling, no benchmarks etc. have been made. But everytime I try another newer toolchain, I quickly go back to my favorite one because it has the best feeling.

I will just put the 'old' charger binary into the next releases' RAMdisk and everything will be fine again.

Is there any kernel that has this already? If yes, it shouldn't be a big deal implementing that feature.

Thanks mate, I appreciate these synapse versions. I never had time and motivation to implement it
[Samsung Galaxy Nexus] morfances:
Fancy r 59 , thanks Boype
[Samsung Galaxy Nexus] frickinjerms:
I'm glad to report that the SoDs I had with r56 - r58 are all gone ? [MENTION=4615478]boype[/MENTION] is boss! I'm using r59 (fixed ramdisk version) with the 10/12 omni nightly with ext4 on /system and f2fs on /data and /cache and it's soliddd!
[Samsung Galaxy Nexus] wkr.mky:
Great update. Playing with init.d tweaks and using my GNex pretty heavily past couple days on Omni nightly and now LiquidSmooth unofficial. Everything is solid. No issues. Thank you!
[Samsung Galaxy Nexus] pianistaPL:
Hmm... I would be original but i can't ;( R57&58&59 are working like a champ! For a week I didn't have any freeze and reboot :)

Oh, and I'm using it along Omni too - just perfect combo.
[Samsung Galaxy Nexus] quickdraw86:
r59 working great on slim 8.0, vanir 10/6/14, and liquid unofficial 10/11/14. Perfect release by Boype, many thanks. None of the heat or SOD issues I experienced on earlier versions.
[Samsung Galaxy Nexus] valkata1212:
Hello ive been using fancy kernel for some time on my gnex and i suffer great difficulty with it. Im using Carbon custom ROM. My phone randomly restarts, ive been observing him, in the night while im asleep he probably restarts himself 1-2 times, (always got the Trickster MOD-set on boot notification) Ive seen him restarting himself when i sit on the computer while he is doing nothing, just idling on my desk. Today i experienced something even more strange today - while idling in my pocket the phone randomly heated up and restarted again, set on boot notification popped, and after 5 sec the phone restarted again. Any speculations or someone can sugest any fix?? I really like Fancy kernel and i dont want to change it :(
[Samsung Galaxy Nexus] veldom:
Did you tried another ROM? I don't think it's kernel related.
[Samsung Galaxy Nexus] valkata1212:
I dont think its ROM related too .. bcus if i only flash the rom with default kernel i dont have any problems at all .. only when im with the fancy kernel
[Samsung Galaxy Nexus] drmxmyt:
what about disabling trickster and use default kernel settings? i remember cab was causing issues when enabled. it might related your trickster setup.
[Samsung Galaxy Nexus] siealex:
It's a memory leak in some of your apps or in ROM.
[Samsung Galaxy Nexus] pianistaPL:
Don't change kernel, change ROM ;) Honestly, Carbon is quite laggy and unstable. Try out Omni, LiquidSmooth or Vanir.
[Samsung Galaxy Nexus] thomstrack:
Quick question: Omni nightlys is recommended for a daily use?

I saw some people talking which is a ROM with no bugs and lags many as CM, PA, etc. .. and as I saw that you are using, I think I could answer most certainly. (Know each phone responds differently..).

My Gnex is my only one phone and need a ROM fast for use. Now I use shiny and fancy.

Thanks in advance.
[Samsung Galaxy Nexus] poo706:
In my experience, nightlies in general are almost always plenty stable for daily use. Certainly not always the case, but most of the time.

[poo]
[Samsung Galaxy Nexus] infectedorganism:
Could anyone give any insight as to why this occurs very inconsistently?

# wait for systemui to be up
until [ $($bb pgrep com.android.systemui) ] ; do
$bb sleep 1
done

# move systemui to the parent task group
$bb echo $($bb pgrep com.android.systemui) > /dev/cpuctl/tasks

If I check after start up, systemui usually resides in /dev/cpuctl/apps/tasks and not where it is specified in the script (fancyinit2). I've tried the code from osmo0sis ramdisk, but my systemui still fails to resided in /dev/cpuctl/tasks (cgroup?) on a consistent basis. I'm just curious if something may be 'off' with my setup that causes systemui to be placed in /dev/cpuctl/apps/tasks and not /dev/cpuctl/tasks as instructed, or reasons why that may be occurring.

From osm0sis ramdisk:

# wait for systemui, move it to parent task group, move ksmd to background task group, and adjust systemui+kswapd priorities
while sleep 1; do
if [ "$($bb pidof com.android.systemui)" ]; then
systemui=`$bb pidof com.android.systemui`;
echo $systemui > /dev/cpuctl/tasks;
echo `$bb pgrep uksmd` > /dev/cpuctl/apps/bg_non_interactive/tasks;
$bb renice -10 $systemui;
exit;
fi;
done&

I've tried placing just those lines in a separate init.d script, making sure it executes last, but it still fails to work consistently. Conversely, uksmd is always properly placed into its appropriate cgroup as instructed in the script -- with either the code in fancyinit2 (below) or the code from osm0sis ramdisk (above)

# move uksm daemon to bg_non_interactive task group
$bb echo $($bb pgrep uksmd) > /dev/cpuctl/apps/bg_non_interactive/tasks

Any help/insight is appreciated.

Thanks in advance.
[Samsung Galaxy Nexus] Rushead:
[MENTION=3927368]poo706[/MENTION]'s work is phenomenal. Unofficial Liquid is awesome.
[Samsung Galaxy Nexus] 7175:
Hmm, that is kind of strange. I just checked and my com.android.systemui pid is in /dev/cpuctl/tasks. (Vanir 4.3.1, fancy R59) Code looks good and pidof/pgrep should work the same since that's the only difference I see used. I guess you could try using pgrep for com.android.systemui's pid or $(ps aux | grep com.android.systemui | awk 'FNR == 1 {print $1}'). I'll check if mine switches on me or maybe write a startup script to see if it moves.

edit: Yeah, checked startup and in general /dev/cpuctl/apps/tasks seems to stay empty for me. I can echo the pid to /dev/cpuctl/apps/tasks though and it stays. Definitely kind of weird.

Another thing I thought of was adding some time between detection of systemui and before echoing/reassigning its task with a "sleep 1"

For anyone that checked out the synapse fancy anykernel zip and got "uci not detected" when starting up synapse. I made a new package that fixes that. I just forgot to add "/sbin/uci" to run via fancyinit. I was using init.d prior, so I didn't notice until trying it on a fresh rom. Should be good now though.

edit: Just in case people still get still get "uci not detected", you can add this script to init.d:

#!/system/bin/mksh
mount -o remount,rw /
/sbin/uci
mount -o remount,ro /

Adding this to fancyinit should work, but I still had some issues.

edit: added new options to synapse with a version 8, readded full /sbin/busybox to counter 4.4.x problems loading synapse scripts.
[Samsung Galaxy Nexus] aliesz:
Hi, nightly doesn't mean unstable but also most of nightly ROMs are stable enough for daily use. I am using omniROM with fancy r59 and it works very fast and smooth without reboots and other malfunctions. Although ROM Choosing is arbitrary.
[Samsung Galaxy Nexus] valkata1212:
As i remember, i know Tricksters mod from boype him self, he sugest using it. But it seems you dont read the whole post, i said i have no problems using Carbon ROM withouth the kernel, and i like Carbon rom myself and i dont think changing it. Someone said something about Memory leak, how can i check it some how or remove it??
[Samsung Galaxy Nexus] kl09:
r57 makes my Gnex smoother than r59 does. It also leads to a higher score in Antutu. I'm using r57 + slimkat now.

Anyone have the same experience and feel r57 is smoother than r59?
[Samsung Galaxy Nexus] pianistaPL:
I don't see a big difference in performance between r57 and r59. Both versions are supersmooth
[Samsung Galaxy Nexus] RW-1:
Have to agree there, same smoothness in the last few releases on Shiny ROM ...
[Samsung Galaxy Nexus] wkr.mky:
With the F2FS changes in r59 and tuna tweaks in LS I'm looking at ultra smooth.

Also trying to break stuff, but I feel like I'm throwing nerf balls at windows. Nothings breaking. :victory:

Many thanks. ^_^
[Samsung Galaxy Nexus] ilMessia:
My read speed hasn't changed with r59. I'm not complaining at all, this kernel is extremely fast, i'm just curious, could it be rom related? I'm running Carbon's 6/10 nightly

Edit: *write speed
[Samsung Galaxy Nexus] Charmacas:
Look at your write speed please. ;)
[Samsung Galaxy Nexus] 11zeno11:
I've the chip V3U00M, I've read a lot of things about it but I can get rid of getting worse performance day by day. The only thing that make my write speed run good are that few command in adb shell:

su

mount -o remount,discard /data

dd if=/dev/zero of=/data/tmp.bin

rm /data/tmp.bin

Now I've made an int.d script to mount /data and /cache with discard option.. I hope this will maintain performance good over time.

Someone have this chip? Some advice about it?

P.s. I have data and cache f2fs and ext4 system partition and I run liquidsmoth with r59 fancy kernel.
[Samsung Galaxy Nexus] Jar3112:
You don't need all of this if you are on f2fs. If you still have low write speeds perform a FULL WIPE, obviously after backing up, and include every partition, even sdcard. Move your files again in and reflash you rom/kernel, should be OK

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] 11zeno11:
I've flashed stock image immediately before turning to f2fs and with that I erased everything. When I first boot after the f2fs switch the phone seemed reborned but a few week later the lag become consistent and the poore write speed reappeared. This is driving me mad.

P.s After the dd command (i've used it today) the write speed retuned good.
[Samsung Galaxy Nexus] Jar3112:
This is strange because slowdown like these shouldn't happen while on f2fs..

How much free space do you have on your sdcard?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] 11zeno11:
Now I have 4gb free space but I cleaned my sd today because when the slowdown occurred I had 1,5/2gb free space
[Samsung Galaxy Nexus] Jar3112:
When storage capability goes under 25% you'll have a significant slowdown. No need to run that commands, simply free up some space.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ilMessia:
Sorry, of course i meant write speed ;)
[Samsung Galaxy Nexus] 11zeno11:
Thank you for your precious advice, I'll pay more attention on my free storage (I have the bad habit of downloading a lot of things and forgetting about them).

I tried that commands because after freeing up some space the phone seemed to remain slow. But I can say that after the command the phone returned fast, maybe a coincidence.

Thank you anyway for the assistance[emoji2]
[Samsung Galaxy Nexus] siealex:
Do not switch off or reboot your phone at least two days. FS trimming in 4.4 is performed after 48 h uptime.
[Samsung Galaxy Nexus] 11zeno11:
That's a good idea! Maybe a init.d script for trimming also during reboot?

Does the discard mount option have some contraindications? I'm thinking of leaving it enabled just for scruple.

I know I'm a little paranoid about this garbage flush and probably the best way is to leave the things as they are since we have a great dev and a great kernel whith all the mount option and the optimization we need.
[Samsung Galaxy Nexus] lparcshinoda:
You could use crontab to launch trim every hour, but if you have /data mounted on discard there is NO need to trim (discard options does auto trim after every write operation on Fs).
[Samsung Galaxy Nexus] thomstrack:
A quick question about you signature: Official Omni Nightly need convert for f2fs?

I have /cache and /data on f2fs e /system on ext4 with FML.

Thanks :)
[Samsung Galaxy Nexus] wkr.mky:
Official Omni Nightly does not need to be converted for F2FS, but you do need a compatible kernel. So every time you dirty/clean flash an Omni Nightly you need to flash Fancy (or other compatible kernels) right after. Do NOT use the built in Omni updater because it will take away Fancy (and cause a freeze on the logo) and will require a battery pull and a boot into recovery to reflash Fancy.
[Samsung Galaxy Nexus] kel29738:
Best rom for battery life?
[Samsung Galaxy Nexus] Reinvented:
no.

Just, no.
[Samsung Galaxy Nexus] Jar3112:
[MENTION=4615478]boype[/MENTION] I'd like to prevent uksm from starting, I tried modifying the fancyinit scripts in sbin folder but they are restored on reboot. How can I do it?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ali4ek:
I have lagfix performing trim every 24 hours at 4 am automatically
[Samsung Galaxy Nexus] infectedorganism:
Edit the file in the zip prior to flashing. Extract fancyinit1 on your computer, open and edit the file making the line read:

$bb echo 0 > /sys/kernel/mm/uksm/run;

... once you are finished, drag the file back to the zip and it should overwrite the original fancyinit1 with the one you just modified; you should be able to accomplish that with 7zip. Flash your new zip file.
[Samsung Galaxy Nexus] veldom:
Same time here ?
[Samsung Galaxy Nexus] kel29738:
I'm just asking a question......
[Samsung Galaxy Nexus] Jar3112:
Wrong question, wrong thread. Read the rules please..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kel29738:
Ok...
[Samsung Galaxy Nexus] Jar3112:
Anyway is a dirty rom flash needed to switch from fancy to another kernel? Or is there another way?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cujo6801:
Yep it cleans up the RAM disk

Sent from the "DOG" pound
[Samsung Galaxy Nexus] ama-ar-gi:
My huge thanks to the developers of this amazing Kernel. I really appreciate your work. It works good with Slim Bean ( Maguro) Rom! Thank you.
[Samsung Galaxy Nexus] faboz84:
[MENTION=4000471]lparcshinoda[/MENTION]

1. is trim working on f2fs?

2. have you had any huge lag during writing operation (eg. an app update) with the /discard option?
[Samsung Galaxy Nexus] skyleth:
hi! could you add support for tap to wake?
[Samsung Galaxy Nexus] pianistaPL:
Trim doesn't work on f2fs but I don't have huge lags durin apps updating
[Samsung Galaxy Nexus] morfances:
Use the apk touch control with module bonury
[Samsung Galaxy Nexus] spacemanr:
There is no more such app?

Over Tapatalk
[Samsung Galaxy Nexus] poo706:
It was removed from the play store, but you can find copies via google. I suggest v1.8.5.

[poo]
[Samsung Galaxy Nexus] wollac11:
If it isn't already could this MOD be added to the kernel to allow use of the HDMI Dock for display mirroring? http://xdaforums.com/galaxy-nexus/development/mod-enable-hdmi-mirroring-official-t1780481
[Samsung Galaxy Nexus] RevengeFNF:
If i only use the f2fs for cache and data, do i still need a compatible rom or just the kernel is enough?
[Samsung Galaxy Nexus] poo706:
As long as the ROM doesn't mount /data as ext4.

[poo]
[Samsung Galaxy Nexus] boype:
Trim doesn't need to be working on f2fs because it has something better: garbage collecting (GC).
[Samsung Galaxy Nexus] RevengeFNF:
Im using CM11 Nightlys. Just Flashing it with Fancy will work?
[Samsung Galaxy Nexus] poo706:
I believe so, but there's no harm in running it through the converter just in case. Or look at the updater-script.

[poo]
[Samsung Galaxy Nexus] Ashtrix:
I also had SOD's after long phone conversations, Till now no issue like that on r59.