yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rseiler:
Looking forward to trying this. While I'm not new to ROMs, I am new to kernels, so might I humbly offer one suggestion for this differentiation post?

http://xdaforums.com/showpost.php?p=54582591&postcount=8683

In the case where someone is in group #1 and so can run either, it would be helpful to see a brief rundown of the differences between the two and maybe even which would be the better choice for group #1. My guess is that's the fancy_kernel-tuna-4.4-rXX.zip one, but I don't know why (beyond the fixed RAM disk).
[Samsung Galaxy Nexus] gauravraw:
So according to the version-post, I need to dirty flash my stock ROM (which will have stock kernel) first, before flashing r56? :(

If that's the case, any way I could backup my apps/settings/data?
[Samsung Galaxy Nexus] AquilaDroid:
Dirty flash won't affect your data or settings.

From my Nexus 5
[Samsung Galaxy Nexus] gauravraw:
Thank you. From where do I get the CWM zip flash'able version of stock ROM?
[Samsung Galaxy Nexus] drmxmyt:
you will flash your current using rom not stock rom. its saying flash your roms stock kernel. so just dirty flash your current rom.
[Samsung Galaxy Nexus] büscher:
upgraded my ROM, wiped cache and dalvik, installed r56 again and no issues since two days now. so that somehow cleared out [emoji106]
[Samsung Galaxy Nexus] veldom:
I just flashed r56 and had a SOD after few hours.

Back on r 54 everything is ok.

By the way, thank you for your hard work !
[Samsung Galaxy Nexus] siealex:
I have no SODs, but I had a reboot when Titanium started making the everyday backup. First I did not notice this reboot, but Llama saved in its logs: "4:02 am: startup sound". "Startup sound" is a Llama action which generates a sound after full boot.
[Samsung Galaxy Nexus] elPicione:
HALP OP, r56 killed my dog in the sleep

Reverted to r54 made it came back to life and stable. Staying on r54 rite now

Please fix ASAP
[Samsung Galaxy Nexus] pkgnex:
For anyone having init.d script-not-running issues, try adding this to the line after the #!/system/bin/sh and before any other code:

sleep 60;

This worked for me on r54 and r56. Seems the os is trying to run the script too early in the boot cycle for it to affect the kernel parameters, but making the code pause for a minute allows it to execute.
[Samsung Galaxy Nexus] infectedorganism:
The only issue I have is getting force fast charge to set via init.d. I'm not sure what the problem is as every other parameter works properly.

Edit: Thanks pkgnex. Adding 'sleep 20;' to the beginning of the script allowed fast charge to apply properly.

I did have an issue with getting the governor frequencies and settings to apply, but this bit of code cleared that up. Credit to osm0sis:

#!/system/bin/sh

# busybox installation
bb=/system/bin/busybox;

# disable the PowerHAL since there is now a kernel-side touch boost implemented
$bb mount -o rw,remount /system;
$bb [ -e /system/lib/hw/power.tuna.so.dvbak ] || $bb cp /system/lib/hw/power.tuna.so /system/lib/hw/power.tuna.so.dvbak;
$bb [ -e /system/lib/hw/power.tuna.so ] && $bb rm -f /system/lib/hw/power.tuna.so;
$bb mount -o ro,remount /system;

If anyone is interested, here is the script I am currently am using to apply my settings on this kernel. Credits to buscher (for the

majority

of the script) and to osm0sis (for the code to apply the minfree values)

Kernel Settings: http://pastebin.com/Nr66X7Hj

Zram: http://pastebin.com/1DQ9gh5G
[Samsung Galaxy Nexus] Piti8576:
Doesn't work for me with SlimKat Stable 7.0.

All my other init.d Scripts work and with Fancy r54 the script works.

With TricksterMod i can change the settings but can't set den DTM Skip :(
[Samsung Galaxy Nexus] pkgnex:
No problem. I know the sleep value can be different for each device. 10 never works for me (if sleep is needed at all), 20 usually does, 30 almost always does. I just threw 60 out there to make sure!

---------- Post added at 07:15 AM ---------- Previous post was at 07:10 AM ----------

If sleep 60 doesn't work, there must be some other issue. I would start with ensuring you have a good busybox install, then try clearing trickster data and rebooting - maybe even wipe cache and dalvik in the process. You never know...
[Samsung Galaxy Nexus] Piti8576:
I have the SlimKat Stable without any changes and my script works with fancy r54.

I have nothing change only update the kernel (busybox and complete rom i do nothing).

When i click the script with root explorer and excute it the settings doesn't set.

My other scripts for trim, remount is working fine all the time.

Only trickster set it. I have trickster installed today for the first time to test it.

I use for now trickster and wait for a new version of fancy or slimkat.
[Samsung Galaxy Nexus] aldroidx:
r56 so smooth thanks

Is there any way to make TouchControl works like in dirtyv kernel ?

Thanks
[Samsung Galaxy Nexus] poo706:
Use the CM11 module and v1.8.5 of the TC app.

[poo]
[Samsung Galaxy Nexus] hardstyle86:
Or TouchControl 2.2.1 with stock module.
[Samsung Galaxy Nexus] aldroidx:
Thanks problem solved [emoji108]
[Samsung Galaxy Nexus] infectedorganism:
[MENTION=4615478]boype[/MENTION] I'm not sure if requests are considered, but could we have the ability to fast charge while still having access to adb/mtp?

If I knew where to find the commits, I'd dig them up for you -- hopefully someone who also would like this implemented will be able to find and link them.

If you have no desire to add that feature, disregard this post.

Thanks in advance.
[Samsung Galaxy Nexus] FredFS456:
I know that DirtyV has that implemented (or at least it says so on their OP...). However, I'm not sure I'd personally like that idea, because I use Fast Charge mode in a similar way to a USB condom. =P But I can see it being useful to other folks...
[Samsung Galaxy Nexus] Piti8576:
I found a Solution that my init.d Script works with r56.

I simple at a remount to the Script and now it works and change all Settings.

#!/system/bin/sh

sleep 20;
mount -o rw,remount /system;

# Screen Off Min Freq
echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo "384000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq;

# Headphone Volume Boost
echo 1 > /sys/devices/virtual/misc/soundcontrol/volume_boost;

# High Performance Sound
echo 1 > /sys/class/misc/soundcontrol/highperf_enabled;

# DTM Skip
echo 1 > /sys/module/bcmdhd/parameters/dtim_skip_override;

mount -o ro,remount /system;
[Samsung Galaxy Nexus] boype:
pre57_1

Hi,

pre57_1 is available from the OP. It is trying to fix the random SOD (sleep of death) issue some of you report. I had one of those as well.

Have a nice weekend!
[Samsung Galaxy Nexus] cujo6801:
Works fine w/ AOKP 9/3 toro

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Conte Mascetti:
I really appreciate your dedication into this project. Thank you a lot Boype!
[Samsung Galaxy Nexus] aliesz:
Thanks bro, the latest pre57_1 anykernel version works smooth and fast on 4.3 stock
[Samsung Galaxy Nexus] Conte Mascetti:
Sorry if it's OT (please delete or redirect me to right place)

I'm wondering guys..... what if the gnexus had not a removable battery? what's the standard way to reboot a device stuck like that? That's my fear!! If I had a N5 ?? :eek:
[Samsung Galaxy Nexus] siealex:
No way. N5 needs full disassembling in such cases.
[Samsung Galaxy Nexus] FredFS456:
Are you sure? I have a TF101 from long ago with a non-removable battery, and if I hold the power button for 10 or so seconds it hard resets.
[Samsung Galaxy Nexus] siealex:
Does this work even if the CPU is fully stopped, e.g. if it is improperly undervolted?
[Samsung Galaxy Nexus] marouane80:
thanks for sharing this kernel. can you add dynamic fsyn feature, please ?
[Samsung Galaxy Nexus] AquilaDroid:
No, with the N5 you just push and hold the power button for 10+/- seconds.

From my Nexus 5
[Samsung Galaxy Nexus] mrgnex:
[MENTION=5322273]Conte Mascetti[/MENTION], [MENTION=1097461]siealex[/MENTION], [MENTION=4586167]FredFS456[/MENTION]

I have a Nexus 10 with a non removable battery and if it freezed or something you can just hold the power button for 5 or 10 seconds (never timed it) and it reboots.
[Samsung Galaxy Nexus] lollipop:
yes , phones with non removable battery have this option
[Samsung Galaxy Nexus] aosp:
And phones with removable batteries ?

Add support reboot on very long power key hold · b595628 · Quarx2k/jordan-kernel · GitHub - http://goo.gl/1kgIfn
[Samsung Galaxy Nexus] Ashtrix:
Dyn Fsync is not better than normal fsync..as it's mechanism varies over the screen state, result - unstable as you might lose your data. Happened to me once while my phone crashed the next reboot was not possible due to corruption of data.
[Samsung Galaxy Nexus] Conte Mascetti:
I had sod yesterday due to a wrong setting in trickster mod

BTW apparently pre 57_1 doesn't like 512 gpu oc

... well I don't know how long is very long power key hold, but for me nothing happened after a minute... I had to pull out the battery

From GNexus
[Samsung Galaxy Nexus] mangusZen:
This would be very nice to have too

[emoji12]
[Samsung Galaxy Nexus] siealex:
This must be implemented in hardware (at least in the power controller), otherwise it will not work when CPU is totally frozen.
[Samsung Galaxy Nexus] Ashtrix:
[MENTION=4615478]boype[/MENTION], the pre57_1 is also good but recently i was having some slowdowns & during gaming also on both r56 & pre57, could also be a cpu load issue. Doesn't use to happen on r54...just a point though.
[Samsung Galaxy Nexus] nonoperez:
I used to have sods while listening music with the screen off. Not today with r57—1, more than one hour playing music without a problem. Thanks boype.
[Samsung Galaxy Nexus] x3m.zone:
I also confirm that r54 performance are better than r56.
[Samsung Galaxy Nexus] aldroidx:
Sod using r56 and r57-1?
[Samsung Galaxy Nexus] infectedorganism:
Now that my swap is full, what happens? Will the system continue to swap files/pages as necessary, or will I need to perform a swapoff/swapon so that the phone can continue to utilize the swap space?
[Samsung Galaxy Nexus] boype:
Linux is smart, so 1).
[Samsung Galaxy Nexus] jmtjr278:
Had my first SOD this morning. Using stock kernel settings for 57_1. Running latest PA. It's always alarming to realize you slept too late. Anything else I can help with to assist in finding a solution?
[Samsung Galaxy Nexus] pkgnex:
No SoD's or reboots here on r54 through r56, including pre56's... with one exception being a random reboot on r55.

[MENTION=4615478]boype[/MENTION], would any info from trouble-free users help, such as Trickster settings, init.d scripts, etc.?
[Samsung Galaxy Nexus] siealex:
I had random reboots with r56, but no reboots with pre57-1.
[Samsung Galaxy Nexus] Nautilus74:
I also had random reboots on F55 and F56

None on F57_1 :) (it runs on f2fs Liquid 9/3)
[Samsung Galaxy Nexus] Ashtrix:
Well so far this random reboot and SOD thing doesn't follow a pattern, i had an SOD yest with pre57_1....:(
[Samsung Galaxy Nexus] Culex316:
Same here. Pre 57-1 is rock solid for me.
[Samsung Galaxy Nexus] GilGameshn1:
Sometimes SOD happened because of old battery or unaligned battery . but you can try clear cache and data of trickster app . it could give headaches . ?
[Samsung Galaxy Nexus] faboz84:
is a good way to clear cache and data of Trickster before a new kernel flashing and sometimes even if you play around with different test settings

...if you still have problems do it again and then uninstall/reinstall the app before flashing the kernel.

i agree with GilGameshn1, old batterys could cause SOD problems. if you have a 2 years battery replace it!!!

[MENTION=4615478]boype[/MENTION] i had several problem in the past (read SOD) and the problem was Trickster; you should insert the above procedure in the OP

Bye
[Samsung Galaxy Nexus] poo706:
The recovery reset zip on this page is pretty handy too.

[poo]
[Samsung Galaxy Nexus] aliesz:
I agree, I have returned to r54, because I feel my phones weight is lighter with it in comare with r56?!! :p;)
[Samsung Galaxy Nexus] madhavs:
yes r54 is the best kernel so far :good:
[Samsung Galaxy Nexus] thomstrack:
This in android 4.3 Jelly Bean ?!
[Samsung Galaxy Nexus] aliesz:
Yes I have stock 4.3 jwr66y ROM on my device.
[Samsung Galaxy Nexus] büscher:
+1 on r54

But anyway... I'll move to new territory, my Gnex just isn't reliable anymore.

5 to 10 battery pulls per day is to much, emmc is giving up - flashing recovery with fastboot at a friends birthday party... somewhat odd.

and finally oversleeping because of SODs, not good for my final year at university.

Thank you [MENTION=4615478]boype[/MENTION] for this great work with Fancy Kernel!

will snoop around just to keep my backup-Gnex updated but won't be very active anymore.

And a big THX to the community here! You are awesome! :highfive:
[Samsung Galaxy Nexus] AgentSmith:
I tend to have SODs when downloading torrents with ttorrent in the background. Maybe it's the strain on the emmc but I'm really just guessing here. Before with the CM kernel I had no problems. I'm using r56.

Maybe SOD isn't the right label though because when I move away from the WiFi AP downloading stops (ttorrent is on WiFi only) and then within a minute or two the phone comes back to life.
[Samsung Galaxy Nexus] Riekr:
I had disconnections only when dtim interval was higher than 1 on the ap: the higher the interval the lower the time between disconnections.

I think not all access points lets you change that parameter though.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] bolanrox:
yes it happened with any kernel Tiny, & lk also. not sure why turning it on and off fixes it though, not complaining :)
[Samsung Galaxy Nexus] phishn:
Played 3 hours of bluetooth music on r14 without issue. Something in r15 and higher seems to be the culprit.

I'm running deadline scheduler, Ondemand plus governor, 192-537 screen off, 192-1228 screen on, WiFi high performance on, gpu Ondemand, oc 384.
[Samsung Galaxy Nexus] fr4nk1yn:
I'm noticing the maximum cpu frequency settings changing back to default after sometime.

I'm using trickster mod to make the changes. Reminds me of a stock powerhal.
[Samsung Galaxy Nexus] bigknowz:
Max CPU

I had the same problem on the test kernel. Franco also had the issue with r374, it was related to PoweHAL.
[Samsung Galaxy Nexus] fr4nk1yn:
I stole power.tuna.so from a faux kernel and it's holding.

I love the battery life as is but Google Now and Swype really needs some extra push to south them out.

I'm running at 1.42ghz with multicore power saving on 1. I'm sure ondemandplus will still be superior.
[Samsung Galaxy Nexus] bimasakti85:
Use this : http://db.tt/TWRbm4cL, flash it from CWM. Its the fix for powerhal problem.
[Samsung Galaxy Nexus] Fabur87:
Yep, I am also still seeing the Wifi problems.

But I didn't notice any real difference in battery drain by wifi, so if it fixes some other stuff it might be worth leaving it in.

If anyone is interested I can describe my 'workaround' to lessen the problem a bit. It is just a tasker profile though.
[Samsung Galaxy Nexus] zoomy942:
I just can't seem to get the 10% brightness increase script you posted to work.

Maybe ill just hope and dream for a version with no brightness adjustments. ;)
[Samsung Galaxy Nexus] boype:
Is there anything speaking against just using trickster mod? it can set stuff on boot too...
[Samsung Galaxy Nexus] zoomy942:
As a recovering flashaholic I try to stay as stock as possible. Resist the urge to tweak.

Serious struggle for me so a kernel flash is all I'll allow for myself.

Cool thing about yours is indemandplus is default so I just flash and go.
[Samsung Galaxy Nexus] bolanrox:
honestly the only thing i change from stock Fancy is the color setting. still trixster (pro or not) is a great thing to have installed. :)
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4615478]boype[/MENTION] Nice to see a developer from Germany over here. Especially that you're from Flensburg was surprising. I come from Schleswig and now live in Hamburg. ;)

The guy who posted a few pages back that your kernel is totally underrated is right. This kernel is the first after the stock Carbon kernel which causes no lag at all even while multitasking after a few hours. I really like OnDemandPlus! I used AK and he also implemented it but out of nowhere freeze or SOD happened.

Thank you for the work you did and hopefully will do! ;)

I set Multicore Powersaving to 0 because I think that will do a faster race to idle. What do you guys in here think?

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] ak:
Its very strange why you never post this problem on the thread and i dont know why you write things that are not true or proven.

Thanks a lot. :good:

+it is known that the problem of systemui is not the kernel.
[Samsung Galaxy Nexus] Charmacas:
Excuse me Anarkia I did not want to offend you! :(

I thought I posted it. Did I forget it? Da**!!!

And I know that the problem with System UI is not kernel related. Maybe there is something else which does the trick or I am not running this kernel long enough. We will see and I will report back to you Anarkia and boype of course. ;)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] jesssiii:
Could someone post r14 please?

I only have 15 and up.
[Samsung Galaxy Nexus] bolanrox:
Boype posted the link to all the past versions a few days ago (i believe all you need to do is take the current link and change the r## :) )
[Samsung Galaxy Nexus] zoomy942:
Understood. The tweaking resisting will continue.
[Samsung Galaxy Nexus] jesssiii:
Duh, didn't even have to change anything, just went to the website! Sorry, all.

http://boypetersen.de/fancykernel/
[Samsung Galaxy Nexus] Charmacas:
Yeah yeah yeah! r18 is there!

Had no freeze whatsoever with r17. A few slowdowns but they are related to the standard 4.2 "bug". ;)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] cujo6801:
Good luck to you bro..

You're one of the good ones

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Ashtrix:
Back to r54, feels smoother & no SOD's either.
[Samsung Galaxy Nexus] Orilin:
Back to r54 too. I hadn't no problem with r57_pre1, no sod, reboot, anything. But I feel r54 a bit smoother and responsive.

Just to say my experience.
[Samsung Galaxy Nexus] siealex:
I had a strange issue during a Skype video call. If I turn off screen and then turn it on (e.g. via the proximity sensor), the CPU frequency sticks at 384 MHz and does not change for several minutes. My settings: ondemand plus, min 224, max 1036, max screen off 384.
[Samsung Galaxy Nexus] aSKAp6uH:
Hi there. Is fancy kernel r56 compatible with cyanogenmod 10.2.1? I installed it over cm and all works just fine except camera. Unfortunately, Gallery has stopped working displayed every time i started camera.

---------- Post added at 01:44 PM ---------- Previous post was at 01:29 PM ----------

Never mind, I'll do it myself. Just reflashed cm10 and fancy kernel again. TY for extremely fast kernel, boype
[Samsung Galaxy Nexus] siealex:
Have you flashed proper GAPPS?
[Samsung Galaxy Nexus] morfances:
I am better with r56 !!

[IMG="Mandhi 2.7 Unofficial Maguro + Fancy r56"]https://lh6.googleusercontent.com/-19sxCRPO6G4/VBGz4IrMNZI/AAAAAAAAMwo/z2yZoWgGTyc/s512/2014-09-11.jpg[/IMG]
[Samsung Galaxy Nexus] AgentSmith:
Any new ideas whether it's ok to lower vaux3_6030 setting in trickster on maguro? Would it make a difference?
[Samsung Galaxy Nexus] Ashtrix:
Well, had an SOD while charging & when i missed a call...was on r54. SoD's are random and might be dependent on settings or ROM or maybe 4.4.x :confused:
[Samsung Galaxy Nexus] mrgnex:
Yeah thats the screen so if you undervolt its a major battery saver. I have it at 2600 as far as I know that is a safe value :)
[Samsung Galaxy Nexus] bsmitty83:
Turn proximity sensor off for calls , specifically screen off behavior
[Samsung Galaxy Nexus] siealex:
But remember, decreasing this value by 0.1 V increases brightness twice. Don't forget to decrease also all color multipliers.

---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------

No, it's not a solution. I never have this problem if I set max screen off to 729, but it consumes 10% per hour with this setting.
[Samsung Galaxy Nexus] Ashtrix:
I'm unable to find out the app...
[Samsung Galaxy Nexus] bsmitty83:
Dialer app , phone/settings/call settings /speaker proximity
[Samsung Galaxy Nexus] Ashtrix:
I guess in SLIM that option is not available...:(
[Samsung Galaxy Nexus] pkgnex:
Do you mean once you go below 2600, or any change from stock in 0.1 V increments? I see no change, or almost no change, until I get down to about 2400 or 2500, at which point the screen gets a lot brighter when you make that next step down. I have my setting 0.1 V or 0.2 V above the point at which the screen brightened, and I have not needed to change my color multipliers.

---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------

Maybe this is carrier dependent... I don't have that option either (I have a Toro), and I'm on about the most stock AOSP-ish 4.4.4 ROM there is (ShinyRom).
[Samsung Galaxy Nexus] Ashtrix:
Antutu v5 ran on my device running r54 with 15k+ , doesn't used to work properly on the others (r56) plus the score would be around 13k unfinished....
[Samsung Galaxy Nexus] siealex:
Any change below 2900 mV.

---------- Post added at 12:17 AM ---------- Previous post was at 12:17 AM ----------

Does it pass the 3D test?
[Samsung Galaxy Nexus] pkgnex:
Since the new version came out, I can't pass the 3D test at all - at least not with the kernels I've tried.
[Samsung Galaxy Nexus] Ashtrix:
I too had that 3D issue earlier but it passed the 3D test with r54.
[Samsung Galaxy Nexus] danijel00:
I was one step away from throwing in the towel, my phone was totaly unrealiable, battery, ost 1hr, total 16hrs etc...

then I flashed there original google image 4.3 (all wiped), got a new battery (looks like original, but i doubt it).

used it like that for a few days.

Now i am on Slim and fancy kernel, and gnex is better then new. So I feel like someone gave me a present of a few hundred euros :)
[Samsung Galaxy Nexus] atiartstudio:
....off topic https://plus.google.com/114298483458899933963/posts/aFTrZbqLhbT

Any thoughts? [emoji24]

Edit: http://review.cyanogenmod.org/#/c/72826/

Light at the end!
[Samsung Galaxy Nexus] rajputrajat:
I read somewhere on Franco's thread that Google has moved to GCC 4.9 as official toolchain. [MENTION=4615478]boype[/MENTION], could you please upgrade to this one as well.

Thanks a lot. :)
[Samsung Galaxy Nexus] AgentSmith:
I set it to 2600. Below this number the screen becomes noticeable brighter. 2600 and up all look the same. Now let's see what that does to battery life.
[Samsung Galaxy Nexus] poo706:
Just double checking... r54 supports mix and match EXT4 and F2FS, right?

[poo]
[Samsung Galaxy Nexus] Ashtrix:
It works, just had my /sys converted to ext4 and rest on f2fs...:good:

Well something's odd i had changed my sys to ext4 still it shows f2fs...i could have made a mistake...will recheck

Edit : it works, i flashed the rom which was converted using your tool. Flashed the regular one now it's fine...
[Samsung Galaxy Nexus] SoftWord:
What have you do to get this result? ROM / KERNEL used? Some tweaks?

Which are your trickster settings?
[Samsung Galaxy Nexus] Ashtrix:
I'm running fancy r54 + slim, with OC up to 1.4GHz with UV..here are my settings

RAB - 1024, row.

Ondemandplus, and voltages from 1420 step to 1036 MHz - 1240, 1200, 1160, 1120.
[Samsung Galaxy Nexus] poo706:
Great, thanks. I updated my tool yesterday to support /system being ext4 and wanted to make sure it was still appropriate to include that particular version of fancy.

[poo]
[Samsung Galaxy Nexus] gautam_nexus:
Hi Mate! can I use your tool to flash the latest PA build with Mix Partition? sys being EXT4? Thanks!
[Samsung Galaxy Nexus] poo706:
As I said in the dirtyv thread, you don't need it for this particular ROM, but it won't hurt anything if you do use it.

[poo]