yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] namtombout:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Have you checked MBQ's stickied post in the general section on kernels and governors? Plenty of info there.

Also just a reminder that all nexus devices are different and optimal settings (kernel, rom, governor, uv etc) for one user may not be optimal for your device.
[Samsung Galaxy Nexus] bolanrox:
Not MBQ's in perticular but a few different XDA posts. Both look to be for best for SSD devices, so like you said personal preference / device. Never had an issue with either, so i was wondering based on personal opinions.
[Samsung Galaxy Nexus] RevengeFNF:
I prefer ROW. Like the name say, Read over Write, without starving it. I found it to be the best one for my use.

Also for the read ahead buffer, i found 256 or 512 to give me the best performance.
[Samsung Galaxy Nexus] kpyhere:
Is there any way i can achieve the same Stock smoothness with the stock kernel, using Fancy Kernel ?
[Samsung Galaxy Nexus] namtombout:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Huh?
[Samsung Galaxy Nexus] abezzilla99:
I tried the kernel again and the freezing problem I had before is now gone but now this time I am getting about 10% an hour battery drop using ondemandplus and light usage (mostly idle the only thing the screen is on for is to check battery). Is this something I should worry about or do I need to let the kernel settle?
[Samsung Galaxy Nexus] :
Have the same problem yesterday, but after a full charge and let the Kernel settle down a bit, It's much better now. Just let the battery drain and charge it.
[Samsung Galaxy Nexus] abezzilla99:
Will do, Thanks!
[Samsung Galaxy Nexus] boype:
Well for the most part this is about personal preference I think. Both sio and row are schedulers that do not do as much re-scheduling as for example bfq or cfq. That said, I estimate them not being too different in terms of performance. Still, sio does slightly more scheduling work than row, since it does some basic merging as well. With the latest release r6, I tweaked sio to do some write starvation. In its original settings, sio hardly does any write starvation, which can cause lag. But my understanding is that row also does write starvation, how else would it achieve 'read over write' priority?! Please correct me if I'm wrong here, I have not read much about schedulers.

As for the read ahead buffer thing: 256 or 512 may give a little snappier performance with opening apps, I agree there. But I found that values below ~800 result in the CPU idling less when playing music. Also, single file reading performance is better with higher read ahead buffer. Long story short: I (personally) prefer read ahead buffer of 1024, since it is a nice intermediate value.

Lastly, an update on Trickster mod supporting task grouping properly and also the new ondemandplus tunables: The Trickster author sent me a test version of trickster with the new stuff implemented. I tested it thoroughly and everything works perfectly... So I guess next Trickster mod release on Playstore supports Fancy Kernel without any limitations :good:
[Samsung Galaxy Nexus] 7175:
This is a really awesome kernel!! I literally signed up on xda within a day of using Fancy rel.4 just so I could get to 10 posts, gain the ability to post in development sections, and applaud you for your work on this kernel boype. :good: :good: :good: Very cool kernel, I've run so many different tests on so many other kernels searching for the ultimate battery life from a kernel that still keeps things snappy. This one definitely takes the cake.

Haven't had a chance to try out rel.5-6 yet, but with rel.4 and my 1850mAh batt, I'm getting 6 hours of screen time with wifi and sync on, avast security, gmail, gvoice sync'd. Even better with 3g instead of wifi. Idle drain is great as well and quadrant runs a 3020 (2d gpu rendering enabled 24/7). This is on XenonHD-4-stable-feb3 with stock kernel settings except wifi_performance=ON, VAUX3_6030=2500, VMMC=1200, contrast= -24, gamma=6/10 or 1.2/2, and color multipliers (90,90,143). Also I reverted back to an older version of Trickster, the update from play store is definitely affecting battery life.
[Samsung Galaxy Nexus] boype:
Hi, welcome as a registered user and thanks for the kind words ;)

You should definitely update to r6, since it is yet a little smoother than r4.

About the latest trickster version draining battery: Is that just a gut feeling of your's or have you read other users reporting the same thing? I'm just curious...
[Samsung Galaxy Nexus] bolanrox:
I haven't noticed anything drastic with the new version of trickster. The battery drain seems to be about the same as ever, definitely no spike in drain on my phone or N7.
[Samsung Galaxy Nexus] RevengeFNF:
Cool ;)

What do you think about Trickster mod tell us there is a new version of your kernel, giving us the chance to download from the app?
[Samsung Galaxy Nexus] mpokwsths:
Installed v6 4.2.2 on the 4.2.2 KALO rom and got bootloop.
[Samsung Galaxy Nexus] gokturk_1976:
Keep up the great work.İt's the best kernel for me..Using stok 4.2.2 with "r6 standart" now and there is no SoD or any problem.Fast and succesful.Thank you.
[Samsung Galaxy Nexus] :
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

This is my batt stats using this kernel... :D
[Samsung Galaxy Nexus] gwindlord:
jfdsmabalot, man, system should not go on the 1st place, this is not really normal to my mind.
[Samsung Galaxy Nexus] :
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Yeah I know, it's eating up a lot. I'll check further.
[Samsung Galaxy Nexus] aHecticLife:
Trying 33 right now :)
[Samsung Galaxy Nexus] boype:
r33 up

Hi all,

r33 has arrived. Change log:

updated to Linux 3.0.84

reverted to Google GCC 4.7 toolchain (reported to be smoother than Linaro)

optimized LPDDR RAM timings (+ ~10% throughput; check the knowledge base for more info)

reverted a few commits from TI repo that have been responsible for unusual battery drain apparently

increased default thermal threshold to 70°C (was 64°C in r32; was 71°C in r31 and earlier; helps with slowdowns)

added 1344 and 1536 MHz CPU steps (above 1.2 GHz ONLY the chosen maximum overclocking frequency will be used. E.g., if you choose 1420 MHz, 1344 will not be used)

pulled-in latest interactive governor patches from Google 3.4 kernel source

implemented io_is_busy function into ondemandplus governor and activated it

implemented 'timer slack' feature (This will effectively reduce the number of CPU wakeups, saving battery; check the knowledge base for background information)

added MiHome Launcher to whitelist (com.miui.mihome2)

few other things

The surprise feature I was talking about is timer slacking. I'll post more information on this in (literally) a second. I have not tested this too much yet, but it definitly works and will hopefully save power. Thanks to Charmacas for mentioning it via PM and also thanks to Amperific for a commit that pointed me in the right direction.

Best regards
[Samsung Galaxy Nexus] boype:
Knowledge base: timer slack feature

Yet another post to be linked to OP's knowledge base. It is about the timer slack feature, which is implemented as of r33.

What does the timer slack feature do?

Timer slacking aims to synchronize applications' and processes' CPU requests. The goal is to wake up the CPU less often in oder to save battery. What you need to know here is the following: waking the CPU up and putting it back to sleep again consumes power. Imagine that four apps wake the CPU up four times each in one second. While without timer slacking the CPU would be woken up 16 times, it is desirable to coordinate the wakeups. If done right, the CPU would wake up less often, effectively allowing power savings and longer sleep periods. This is what timer slacking does.

I have activated timer slacking only for background applications, so that everything else stays as responsive as you know it.

Apple has recently introduced this feature under the name 'timer coalescing' with their Mac OSX Maverick (link).

More information: How Apple does timer slacking ('Timer coalescing') (Scroll a little down to the diagrams)

Best regards

(sorry for double post again... information was supposed to be seperated from previous post)
[Samsung Galaxy Nexus] nixholas:
Oops. CGROUP SLACKKKKK XD

Well done. (:
[Samsung Galaxy Nexus] jesssiii:
Nope. Sorceress version here!

Toro GNex
[Samsung Galaxy Nexus] cujo6801:
Same here...:D

sent from the DOG pound
[Samsung Galaxy Nexus] pcphobic:
Cool! Thanks. I will try r33 now1
[Samsung Galaxy Nexus] paarthdesai:
ahh lovely..

smooth as butter ;)

sent from my sexy Nexy ;)
[Samsung Galaxy Nexus] im the doctor:
Thanks :good:
[Samsung Galaxy Nexus] kinfolk248:
ok becuz im on sourceress too and do you guys get a random reboot every now and then...??????????
[Samsung Galaxy Nexus] Citizen_Snips:
Does this have hotplug helper? Saw [MENTION=5310723]Amperific[/MENTION] talk about it in his thread and I see you two are working together >:) !
[Samsung Galaxy Nexus] TheMan0790:
My setup (CM 10.1 nightlies with r33) is FLYING with this kernel. Unreal work!
[Samsung Galaxy Nexus] jesssiii:
No, none. I underclock to 192/1036 with minimum screen on changed to 192. And color change too. Otherwise stock.

Toro GNex
[Samsung Galaxy Nexus] kinfolk248:
thts what im at except at 384 instead of 192......hmmmmm interesting...thanks tho
[Samsung Galaxy Nexus] boype:
Care to try something?!

Put this in init.d...

#!/system/bin/sh

echo 4 > /proc/cpu/alignment

and please tell me if it's okay again.

No hotplug helper yet. I will probably try this in the future. The downside with hotplug is that the governor needs to support it. As this kernel has 'multi-core power savings', which works with any governor and even is supposed to have advantages over hotplug, I'm not sure hotplug would be a good and necessary addition to the kernel.
[Samsung Galaxy Nexus] stuffynet:
Very smooth. Smoother than r32. Thanks for your work. Really appreciated.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zoomy942:
I'll agree. Every time I have manually tried hot plug in any form it ends up being more trouble for me.

But you have proven 33 times that you are amazing so we will follow you anywhere..

I installed 33 ext and love it. Figured might as well stay with ext since the rest ones are too.
[Samsung Galaxy Nexus] boype:
Knowledge base: how to use init.d scripts

1.) create an empty textfile and name it something like '81alignment' (don't type the ' '; the number is random and does not matter; give the file any name you want, but DO NOT put an extension like .txt at the end)

2.) paste the following (or other) content to this file and save it:

#!/system/bin/sh

echo 4 > /proc/cpu/alignment

Note: the first line (starting with the #) is absolutely necessary!

3) copy the file 81alignment to /system/etc/init.d (using a file manager is easiest)

4) set the proper permissions to the file: 755 (rwxr-xr-x)

5) reboot
[Samsung Galaxy Nexus] cujo6801:
Not here....

sent from the DOG pound
[Samsung Galaxy Nexus] Seraz007:
well r33 is running with no issues

even at 700mhz the UI is smooth O)_(O !

Gr8 job Boype; just tested idle drain and nothin yet over the course of abt 90 mins :highfive:

Sent from my Katana
[Samsung Galaxy Nexus] flatflo:
r33 runs great with vanir :thumbup:

Very smooth and no recent lags.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] jesssiii:
This is what I got:

export PATH=/data/local/bin:$PATH

su

u0_a89@android:/ $ export PATH=/data/local/bin:$PATH

u0_a89@android:/ $ su

root@android:/ #cat/proc/cpu/alignment

sh: cat/proc/cpu/alignment: not found

cpu/alignment <

User: 0

System: 35

Skipped:0

Half: 0

Word: 0

DWord: 0

Multi: 35

User faults: 2 (fixup)

root@android:/ #

First time I didn't put a space after cat.

Doesn't look right. Permissions correct and rebooted. Made sure I had root access for system.

I'm not having reboots, just being nosey :D

Toro GNex
[Samsung Galaxy Nexus] Hoochie_Coochie:
Never overclocked my gnex before, does smart reflex need to be disabled to do it?
[Samsung Galaxy Nexus] jesssiii:
No.

Toro GNex
[Samsung Galaxy Nexus] helloworld1:
I have found lot of warning message in the log for the r33 kernel. I wonder if there is something wrong. I haven't seen them before.

W/SchedPolicy( 1165): add_tid_to_cgroup failed to write '6476' (Permission denied); policy=0
W/System.err( 1165): java.lang.SecurityException: No permission to set to given group
W/System.err( 1165): at android.os.Process.setProcessGroup(Native Method)
W/System.err( 1165): at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityMa
nagerService.java:13527)
W/System.err( 1165): at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityMa
nagerService.java:13568)
W/System.err( 1165): at com.android.server.am.ActiveServices.serviceDoneExecutingLocked(ActiveServ
ices.java:1449)
W/System.err( 1165): at com.android.server.am.ActiveServices.serviceDoneExecutingLocked(ActiveServ
ices.java:1420)
W/System.err( 1165): at com.android.server.am.ActivityManagerService.serviceDoneExecuting(Activity
ManagerService.java:11121)
W/System.err( 1165): at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:82
6)
W/System.err( 1165): at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerSer
vice.java:1674)
W/System.err( 1165): at android.os.Binder.execTransact(Binder.java:351)
W/System.err( 1165): at dalvik.system.NativeStart.run(Native Method)
[Samsung Galaxy Nexus] jesssiii:
I changed the name of the file to 90alignment just in case it made a difference. Still getting this:

u0_a89@android:/ $ su

root@android:/ # cat /proc/cpu/alignment

User: 0

System: 35

Skipped: 0

Half: 0

Word: 0

DWord: 0

Multi: 35

User faults: 2 (fixup)

root@android:/ #

Toro GNex
[Samsung Galaxy Nexus] nixholas:
Hotplug helper wouldn't help boype much, he has a better aim (: Well anyways, you can just enjoy the Timer slack I've found that fancy is using (: In other words, We are just sharing our commits (:
[Samsung Galaxy Nexus] boype:
User faults: 2 (fixup) <-- this is the line that's important. And the value has not been changed as you see.

I have a suspicion though: in the init.d script, try adding a 'sleep 10' before the 'echo 4 > /proc/cpu/alignment'
[Samsung Galaxy Nexus] cmoG530:
I just have to say man, I love this kernel. Great job!!!
[Samsung Galaxy Nexus] jesssiii:
Added the sleep 10 with a space after then rebooted. Same result:

u0_a89@android:/ $ su

root@android:/ # cat /proc/cpu/alignment

User: 0

System: 35

Skipped: 0

Half: 0

Word: 0

DWord: 0

Multi: 35

User faults: 2 (fixup)

root@android:/ #

Toro GNex
[Samsung Galaxy Nexus] nitsua98:
I think r32 worked better for me because I'm on a linaro ROM.
[Samsung Galaxy Nexus] boype:
I'm also on a Linaro built ROM (CM10.1 Euroskank) and r33 (Google toolchain) is way better for me... There's no such thing as incompatiblities between ROMs / Kernels that are built with different toolchains.

Read this and this.

Just checked it out and made myself an init.d script (without the sleep 10) and it works as intended. Did you set the right permissions? Are you able to run other init.d scripts?
[Samsung Galaxy Nexus] bunnahabhain:
It'd be new to me that linaro ROMs would work better with linaro kernels or vice versa...

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] shawnaye:
Hey boype, i've got something to ask you.

It is possible to make apps like Chrome start up much faster? eg. increasing priority or use of cores?

I'm jealous of my friend's phones opening up Chrome so quickly and me having to just slowly wait for it to load.

I'll do tests if necessary to make this come true.

You're really the only reason i haven't switched to a N4 given the chance to do so recently!

Thanks in advance!
[Samsung Galaxy Nexus] nitsua98:
Thanks for the explanation [MENTION=4615478]boype[/MENTION]

This is why you're one of my favorite devs
[Samsung Galaxy Nexus] tuemdeluxe:
Just one thing I noticed :

When I choose 1.5ghz as max frequency the phone freezes immediately, the set voltage seems to be to low for my phone. If I increase it to 1430mv (even a little less could work but like that I'm sure) it's working flawlessly.

Maybe you could increase the voltages slightly to avoid reboots and crying in this thread :D

Besides that r33 runs perfectly, no hiccups and great idle drain, thanks!
[Samsung Galaxy Nexus] jesssiii:
Yes, afaik. Screenies :

Toro GNex
[Samsung Galaxy Nexus] mpokwsths:
Of course not. What a useless request. Most people here don't even use Chrome. The tweaked RAM timings already should reduce the app load times.

too low voltage?

My phone works at 1536 @ 1265mV. Are you sure 1330 are not enough for you?
[Samsung Galaxy Nexus] shawnaye:
i'm sorry, where did this horrible assumption of most people here not using chrome come about?

did you even have ANY back up to support your claim?

not everyone's an engineer like you are (presuming you're such a smartypants), to know that it's impossible and henceforth useless.

I'm just trying to make my user experience a better one, and spreading it to POTENTIAL users hopefully.

Thanks for the reply.
[Samsung Galaxy Nexus] jesssiii:
Ah, success!

u0_a89@android:/ $ su

root@android:/ # cat /proc/cpu/alignment

User: 0

System: 35

Skipped: 0

Half: 0

Word: 0

DWord: 0

Multi: 35

User faults: 4 (signal)

root@android:/ #

I took off the sleep part, then moved the two lines closer together and all the way to the top of the file-so no spaces were at the top or between the two lines. Rebooted.

So, what exactly does that do? I just wanted to learn to make the initd script work. Thanks!

Toro GNex
[Samsung Galaxy Nexus] chikimonke:
This is why people hate XDA. I don't think it was a useless request. The superiority that users like you show on XDA is so annoying. How about explaining why it wouldn't help anything and not insulting the other user? Also, what are you basing your "Most people here don't even use Chrome" comment on? I use, and am quite happy with it.

To the original question, I don't believe it would help because that priority setting isn't for getting my memory or processing power, but rather, to keep it in memory/keep it from getting killed. Making chrome less likely to be killed would probably needlessly consume mire memory slowing the whole system down. At least that's my understanding and take on it.
[Samsung Galaxy Nexus] shawnaye:
Thank you for the useful reply.

Most of my friends phones are basically quad core, and they kinda load chrome, as fast as my phone can load eg. Dolphin.

So i was thinking, would it really take a quad core phone to really load an app that quickly? or would proper use of the two cores in my phone be able to do the same, hence my query :D
[Samsung Galaxy Nexus] tuemdeluxe:
1265mv? That's almost the voltage of the 1228 step!

My phone seems to be picky with that, the standard voltage for 1536 mhz was 1370 what caused a freeze two times I tried to turn it up to 1536. Increasing the voltage to 1400 or a little more solves that problem so the too low voltage (at least for my phone) seems to be the problem. Iirc another user mentioned the quite low voltages for the frequency steps over 1228 (no matter if they are quite low, in fact I'm not sure about that, they seem to be too low for some people's phones). Anyway that's the kind of problem that's easy to solve, just wanted to mention I had that problem.
[Samsung Galaxy Nexus] jesssiii:
Would using a higher clock setting help?

Toro GNex
[Samsung Galaxy Nexus] phishn:
Nope but test 3 was one cycle too.
[Samsung Galaxy Nexus] mpokwsths:
And you just explained why it was a useless request...
[Samsung Galaxy Nexus] shawnaye:
Hmm, it would seem so.

But wouldn't be feasible to have that because it would affect the whole phone?

I'm looking for more of a specific approach.
[Samsung Galaxy Nexus] BOY_:
For the slow chrome problem, the issue with chrome is the amount of syncing it does afik. Setting a higher CPU speed may help but I think for it to run well we need more RAM, plain and simple.

I've been on the stock browser for a while now and it is so much faster than chrome. I actually prefer it to dolphin. YMMV.
[Samsung Galaxy Nexus] mpokwsths:
Well, you could try to make the Chrome process hard to kill, as my friend said earlier, using a script (search the supercharger thread). The point I try to make is that ... it has nothing to do with a KERNEL thread! Launcher unkillable, it makes sense. But Chrome?
[Samsung Galaxy Nexus] n2rjt:
My phone also could do 1536MHz with default voltage on r32test4 but needs voltage increase on r33. I am using next lower frequency, to keep battery drain minimal. I don't ask for any change at all from boype. Overclocking is always tricky, which is why he keeps the default Max frequency 1.2G. For me, on a hspa+ at&t network with stock ROM, r33 is perfection.
[Samsung Galaxy Nexus] boype:
[EDIT] Nevermind, just saw you sorted it out yourself :)

What it does... The value of 4 makes the CPU not execute misaligned 32 bit accesses, while 2 lets the ARM CPU fix the misaligned access. You probably won't understand this (no offence) unless you're a tech geek :)

In case you're interested, here's the basics on alignment: http://en.wikipedia.org/wiki/Data_structure_alignment

Unless your system crashes for unknown reasons, leave the fancy kernel default (2)
[Samsung Galaxy Nexus] chikimonke:
Correct, but I explained it, which is where the difference lies. If more people were willing to help, rather than getting butt hurt every time some one asked a "useless question" we'd all be more knowledgeable in the end. Also, in my experience, some of the most seemingly useless or asinine questions or ideas can sometimes lead to some great ideas.
[Samsung Galaxy Nexus] kinfolk248:
well im confused as hell...!!!!!!!!!!! eff it i'll just manage lol lol
[Samsung Galaxy Nexus] helloworld1:
Anyone noticed this? It could cause lag in the system.
[Samsung Galaxy Nexus] KeithLing1115:
Smoking fast for me on Sorceress
[Samsung Galaxy Nexus] nitsua98:
I'm getting random ui lag with r33 :(
[Samsung Galaxy Nexus] zoomy942:
I just noticed that too.
[Samsung Galaxy Nexus] Hoochie_Coochie:
Are you overclocking? I noticed it on 1.5ghz but stock no lag
[Samsung Galaxy Nexus] nitsua98:
Nope. I have everything stock except WiFi high performance, CAB, and force fast charge are enabled.
[Samsung Galaxy Nexus] pcphobic:
Boype you are a genius! I am not sure what you have done differently for r33 but, this is my all time best idle drain record of all time.

I have never gotten such fantastic result.

After 9 hours ++ of idle on 3G (not WiFi) I only lost 4%.

That is like 0.4% per hour drain while on 3G.

With other versions or kernels that I have used the best was 1% per hour.

ROM: LiquidSmooth ver.2.5

Kernel: Fancy kernel r33 ext (stock settings)

Data connection: 3G

WiFi: Disabled

Bluetooth: Disabled

Data sync: Enabled

GPS: Enabled
[Samsung Galaxy Nexus] nitsua98:
So, I think the micro ui lag on r33 as well as r32 comes from playing 3D games (subway surfer, temple run 2, etc.). Also, my phone is super hot right now, almost burning.
[Samsung Galaxy Nexus] boype:
These errors appear when android tries to automatically adjust the oom value of your launcher. As the kernels whitelist feature blocks access to the corresponding variable, the logcat will throw some errors. As you see, this is intended.

You say it causes lags?! Are you sure about that?

Looks like timer slacking does a good job, huh?! :) I'm also getting really good battery life results. Will share when battery is empty.

Ah and this: you know that the battery drains slower from 100 to ~85 percent and faster from ~30 to 0 percent, right? Just want to make sure you're not surprised about varying results
[Samsung Galaxy Nexus] redj12:
Hi. If I want set back all stock values from this kernel, i must wipe the init.d folder in CWM ?

Envoyé depuis mon Galaxy Nexus en utilisant Tapatalk 4 Beta
[Samsung Galaxy Nexus] paarthdesai:
stunning battery life with r33

sent from my sexy Nexy ;)
[Samsung Galaxy Nexus] paarthdesai:
noo. just need to remove set on boot in trickster.. and al setting will be reverted to stock

sent from my sexy Nexy ;)