yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] gwindlord:
Maybe it is placebo, but it seems notification drawer got a little bit less smooth on 25 after 24 - though it could be just imagination. boype, are you sure it was bad idea to set systemui nice to -20?.. It was incredibly smooth, I've never seen that before.
[Samsung Galaxy Nexus] RevengeFNF:
Flashed R25 and i se visible improvements. Thanks :)

I only do this Changes:

GPU to 384Mhz

Color profile do Franco Values.

Turn Off MPU Smartreflex and to some Undervolting(My Cpu might good, cause its works 100% stable).

Rest is Default.

My Undervolt:

192Mhz - 730

384Mhz - 780

537 Mhz - 830

806Mhz - 960

1036Mhz - 1080

1228Mhz - 1150
[Samsung Galaxy Nexus] Charmacas:
He set it really high with -17. As he said -20 is for real critical processes only and that is important for the Android system. So as the priority is with -17 also really high the smoothness should stay as it was. I wouldn't worry about that! r25 is incredibly fast! I have also no problems with the notification drawer. It comes down as fast es usual.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] motorazrv3:
Flashed r25 ext over r24 ext and booting took no longer than last boot of r24.

So far no problems on purity 5.4.1.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] boype:
... so I re-applied for RD status. I have not set my hopes too high, I think there's a 50 / 50 chance I get accepted.

Speaking about 'magic', I spend a little time finding out good tunables for SIOplus.

If anyone's got time, try this:

#!/system/bin/sh

echo 3000 > /sys/block/mmcblk0/queue/iosched/sync_write_expire
echo 5 > /sys/block/mmcblk0/queue/iosched/writes_starved
echo 156 > /sys/block/mmcblk0/queue/nr_requests
[Samsung Galaxy Nexus] bolanrox:
first start ups have never taken that long for me. I run fstrim on data maybe once a week, and don't have the storage super filled. Would that be the reason?
[Samsung Galaxy Nexus] Charmacas:
I hope you get accepted. I will try this and report back. :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] manolone:
Hello

I'm trying to flash the Last vetsion of fancy kernel on cm 10.1 rc 2 but after i get into recovery, wipe dalvik and cache, flash the fancy kernel zip, once i reboot i don't go after the boot screen...

Which is the right sequence in order to flash the fancy kernel on cm 10.1 rc2?

Thx

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Charmacas:
Hmm... Just try it again and wipe cache and dalvik after you flashed the kernel. Shouldn't make any difference but who knows... ;)

[MENTION=4615478]boype[/MENTION] I don't have nr_requests inside trickster. Should I apply it with script or terminal?

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] bolanrox:
was wondering the same thing myself
[Samsung Galaxy Nexus] boype:
Do it from terminal (in that case, leave out the #!system/bin/sh in the beginning)

[EDIT]

Here's a test version which has the new settings implemented:

http://boypetersen.de/fancykernel/tst/fancy_kernel-tuna-4.2-tst-ext.zip

I think it really is magic.
[Samsung Galaxy Nexus] zoomy942:
Awesome. I'll install it now.

Using 384/1420
[Samsung Galaxy Nexus] 1haumann1:
great kernel

great work

a small donation as a thank you is on the way
[Samsung Galaxy Nexus] Blackcrx:
hmm.. just flashed r25, it didn't take nearly as long as r23 did on the first boot. If anything the first boot was average to other kernels like Franco r378 and AK r246.
[Samsung Galaxy Nexus] Syfer_Fever:
anyone having problem with deep sleep issue on r25? me only have 60% deep sleep and 55% at lowest freq. on r24 no problem at all. it is just me or anyone have problem just like me?
[Samsung Galaxy Nexus] stevensoaj:
I'm not currently on the test verison, but I'm on r25 with an init.d script setting the values you suggested on boot, and it is very smooth so far. I'm enjoying it quite a bit. :good:
[Samsung Galaxy Nexus] jjhrrsn:
Just keeps getting better. Thanks !
[Samsung Galaxy Nexus] bolanrox:
one SOD so far on r25

---------- Post added at 12:22 PM ---------- Previous post was at 12:15 PM ----------

I had it hang at 192 for and hour and change seemed to be due to the data signal though. And one random just now. Phone is down to 65% charge - normally this time of day i would be in the 90's still.
[Samsung Galaxy Nexus] stevensoaj:
I have also had one SOD, which then caused a reboot. I couldn't find a last_kmsg though.
[Samsung Galaxy Nexus] motorazrv3:
No problems here. Deep sleep working fine here on purity 5.4.1 in combination with fancy r25 ext.
[Samsung Galaxy Nexus] Blackcrx:
People with sleep of death. What is your min frequency?
[Samsung Galaxy Nexus] odavans:
feels like a bit faster, thanks
[Samsung Galaxy Nexus] bolanrox:
stock settings across the board 192 min with the GPU bumped up to 384
[Samsung Galaxy Nexus] Blackcrx:
Not sure with Fancy but with other kernels it is always suggested to run 350-384 min cpu to prevent SOD

I have never ran anything lower than 350-384 and have never had a SOD

Also if you check the voltage smart reflex settings, there is no battery/power savings from 192/230/350/384. They all use between 820-850mv depending on kernel and min cal voltage settings
[Samsung Galaxy Nexus] Syfer_Fever:
lol true, there is no problem with deep sleep in r25, it's only me with init.d scripts conflict, tried to delete several last init.d that i installed and the deep sleep problem is gone and my deep sleep is working fine again on CM-10.1.0-RC2 :D
[Samsung Galaxy Nexus] zoomy942:
Agreed. Try it at 384.
[Samsung Galaxy Nexus] n2rjt:
I haven't had SOD with this kernel but with some versions have had a "comatose" issue. LED blinks but phone doesn't turn on the screen. I wait patiently though and it always turns on after a few minutes. Sometimes I have not been able to wait and pulled the battery. But whenever I have been able to wait, it always wakes eventually.

I do occasionally see a dark screen. Backlight is of but when I hold the screen up to a light I can see a display. I have seen this twice, once with r25, immediately after setting GPU oc to 512 with trickster. I use stock ROM, ext kernel, with max oc of CPU and GPU. No lags.. Very good performance. I use PGM too.

Edit: I report this because people are talking about SOD. I. Have not had an issue since about r20, though. The no backlight issue I have seen but not the coma or SOD-like issue.
[Samsung Galaxy Nexus] stevensoaj:
I've had a quick reboot and a full freeze/reboot on r25 now.

Min Freq: 384

Max 1036

Max Screen Off 384

Min Screen On 384

GPU 384

Stock everything else.

Slimbean Build 5
[Samsung Galaxy Nexus] bolanrox:
bouncing min up to 384 rightnow. After the battery pull and reboot everything is going smoothly, might have been a fluke thing. thanks guys!
[Samsung Galaxy Nexus] Argasil:
The difference between r25 and r25 test si only a out smoothness?or maybe the r 25 is more battery friendly..?:)
[Samsung Galaxy Nexus] TheMysteriousOne:
GPU OC at 512 with ondemand GPU governor. Games like Hungry Shark are smooth now!

And the phone doesn't even get that hot.

Nice work.

Also, I just implemented your sio+ tweaks. I can't say I notice more smoothness since it was really smooth anyways.
[Samsung Galaxy Nexus] Riekr:
I've always had min freq lower than 350 without sods. The only sods I've had with this or other kernels in the past were due to bad CPU governors (like some version of hotplug) or io scheduler (like bfq).

Stock settings of this kernel are very good and i don't feel the need to change them so far.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] bolanrox:
SOD'ed again loading r24 back up again for now.
[Samsung Galaxy Nexus] boype:
Sods are most likely caused by the 806 MHz CPU step, since the voltage is not high enough. Will fix.
[Samsung Galaxy Nexus] Invicta:
no problem here, been playing for 2 hours games and heavy multitasking
[Samsung Galaxy Nexus] mpokwsths:
r25 working great here. The 806Mhz step is great, it indeed offers good responsiveness and low power needs.

Have MPU SmartReflex disabled and voltage set at 980mv for the 806Mhz step.
[Samsung Galaxy Nexus] omid900:
Haven't any kind of sod's since use ondemandplus governor!! Plus I set the voltages at least 50mV less then stock provided! So my very ignorant tip is probably it's not fault of voltage!

Are the people that reported sod's, using ondemandplus as default governor? Not using any kind of scripts from Rom's initial scripts or coming from others kernels and having conflicts with some stuff not properly deleted!

Well just my 2cents, oh thank you boype for these wonderful kernel development :)

I think my phone can't run faster then this! This is great, the only thing is that it drains a bit more my battery then others kernels (lean is the best on it from those I have tried) , is the only thing that I can point this kernel (special on r25) but still good :thumbup::thumbup:
[Samsung Galaxy Nexus] Charmacas:
I've monitored my CPU and tested the options well the last hours. I am experiencing mid lags all over. I've tried many things to work this around:

- Played with voltages

- Turned on/off Content Adaptive Brightness

- Don't use the 1420 MHz step

- Use deadline as default scheduler

Nothing seemed to work until I realised that I've forgot to set MCPS to 0 again. I don't know why but if it's set to 2 it's okay for me, if it's set to 1 it causes these mid lags and if set to 0 my phone is flying.

Monitoring the CPUs while the MCPS is set to 1 showed me that it seemed to be more aggressive than on 2. It's strange, isn't it? ;)

So everything's great with r25, SIOplus and the tunings for it. Just had to set MCPS to 0. :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] bunnahabhain:
Is MCPS set to 0,1 or 2 by default?
[Samsung Galaxy Nexus] Charmacas:
In r25 it is set to 1. In the versions before it was set to 2.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] Blackcrx:
806mhz shows as 1050mv in trickster. That is roughly the same voltage as AK kernel

I am not a developer by any means but I find it hard to believe that 806mhz is the cause of SOD.

Default max screen off is 537, to my understanding when the screen is off the cpu should never see 806 anyways

I believe the ppl with SOD issue is more likely to be related to min cpu being set to low

I would suggest that anyone with a SOD issue to revisit r25 and make min cpu 384 and see if the SOD comes back.

As I mentioned before, there is no power savings to my knowledge between 192 and 384, so why use 192?

edit: I always have MCP set to 0 with my custom underclock settings.

Question for the long time Fancy users, does the kernel get any smoother or faster after a couple days of usage? I noticed that with some kernels that with the exact same settings after the 2-3 charge the device really starts to shine/fly

As of right now my 2 cents for this kernel is that battery life is great... but isn't as smooth as some of the other kernels.

No disrespect to the developer or anyone, just throwing out my user feedback
[Samsung Galaxy Nexus] szucsgf:
There is power savings between 192 and 384. Power = (voltage^2)*(frequency)*(capacitance). If they used the same voltage, 192 would use half the power of 382 (capacitance is a constant).
[Samsung Galaxy Nexus] Pelide:
Never had sods with min freq 192, with fancy r8 to r24 (not all versions, but I've flashed lot of them)

Before r24, battery and smoothness were good since first battery cycle.

With r24, first cycle was bad, 2nd was better and 3rd was great!

Please, read szucsgf post, so you understand why people use 192mhz

Tapatalkeggiato
[Samsung Galaxy Nexus] 7175:
Thanks boype, gleich perfekt as usual.

Ditto!

Running r25 with sioplus, ondemandplus, 384-1036 screen on, 192-537 screen off, 307gpu ondemand, mpu uv'd all below stock to my phone's correctly determined minimum stable voltages +25mV, mpu-SR off.. -vaux3 at 2500 -vmmc at 1200 as usual, and everything else stock. Zero sod's, ever, on fancy kernel and ondemandplus.

+1 to everything omid900 said. If you're having problems be cognisant of the fact that it probably isn't the kernel itself but some other complication. Please post a logcat and provide more information, settings, previous kernels used, trouble shooting, etc. Otherwise there's so much uncertainty in your claim that it's pointless and can't be related as a possible kernel problem with any significance. Hope that makes sense, it's true. This is just something to think about for people posting stuff like "lag in uron man3, SOD's all over my 87x dirty flashed nightly."
[Samsung Galaxy Nexus] Blackcrx:
OK, I will take your word for your formula because again, I am not a developer

For me I just used trickster mod to monitor voltage. 192 was at 830mv and 384 was at 840mv

---------- Post added at 02:21 PM ---------- Previous post was at 02:20 PM ----------

How was the performance? same as initial install?
[Samsung Galaxy Nexus] mrm43:
ON r25 everything is better than ever. Smooth, fast, battery are excellent. All stock settings here with ak47.
[Samsung Galaxy Nexus] szucsgf:
Here's a source of you're interested. Second paragraph.

http://en.m.wikipedia.org/wiki/Dynamic_frequency_scaling

You've absolutely got the right idea; they do run at almost the same voltages, and Voltage is one of the variables that determines power usage. It's just not the only variable.
[Samsung Galaxy Nexus] Charmacas:
Oh the lags appeared again. So I think I have to test more. My conclusion that setting MCPS to 0 could save the problem seems to be wrong. Hmm... I will test... Maybe it's my ROM...

So far I think it's my System UI getting huge very fast.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] Blackcrx:
I used the formula you posted, and you are right, more than half the power savings

BUT... what does that relate to in real life experience/value? Do you really notice a dramatic battery life increase?

Also I have been seeing a lot of ppl reporting that r25 is smooth, which I agree. It is smooth when it comes to scrolling, opening apps etc..

The problem I have is that for some reason my swift keyboard lags

I use the same settings as I did with Franco and AK

RAB256

deadline with Franco tweaks

min 384

max 1036

interactive default except

go hispeed 70

hispeed freq 806 (Franco 729, AK 810)

min sample 20

MCP0

Also I noticed that Fancy stays at 384 a lot longer than Franco/AK (according to CPU spy and trickster)

Can someone maybe shine some light as to why my ONLY my swift keyboard lags?

---------- Post added at 03:39 PM ---------- Previous post was at 03:35 PM ----------

Have you tried restarting your systemUI? It is suppose to be the same as rebooting your phone without the battery drain of an actual reboot

There are scripts out there that can do that for you, I have personally been using driodgram reboot. My ROM is Mirage 2.1 which is based off of SLIM v5. So far I haven't really had to use the systemUI reboot, probably because I usually reboot my phone once every 24hrs (give or take depending on kernel or tweaks I change on a daily basis)
[Samsung Galaxy Nexus] szucsgf:
That is a question that I've been trying to answer for a little while. This is all theoretical. My thought is that the total power savings should be about:

(power savings at 192MHz)*(%time spent in 192MHz)

The time spent at 192 is the time that would otherwise be spent at 384. Currently my %time at 192 is 21%, and I calculated 192 uses about 49% of the amount of power that 384 does. So power savings is 51%. 21*0.51=10.71% less power overall. That sounds like it might be noticeable, though I'd guess it's small enough to be difficult to test for unless you run very controlled experiments (e.g. same rom, kernel, apps, phone usage, temperature, and all the other things that can effect battery life). And it's only an example given my current %time spent at 192. I'm sure it would be more accurate to use your average %time at 192.

Like you, I'm not a specialist. The power equation in my earlier post I'm quite certain of. The stuff in this post is just my best guess.
[Samsung Galaxy Nexus] zoomy942:
I went back to the non test r25. The test one got lagged really quick.
[Samsung Galaxy Nexus] jjhrrsn:
FYI its osmOsis that figured out the whitelist script Franco just uses it. Not a huge deal might want to clear that up though. :thumbup:
[Samsung Galaxy Nexus] parkson:
Any other toro users suffering from reoccurring data drops? CM 3-15 build stock settings

They stop occurring if I change kernel. Any kernel
[Samsung Galaxy Nexus] agritux:
boype, did you changed anything about screen touch sensivity since r23?
[Samsung Galaxy Nexus] Pelide:
Battery: 1st charge bad, 2nd better, 3rd very good

Performances: 1st bad, since 2nd charge good

I don't know if it is only on slimbean (tested a lot of rom like liquidsmooth 2.2 and 2.3,carbon,axiom,... and I think it is the smoothest while it has a large number of customisations) or with all roms

Tapatalkeggiato
[Samsung Galaxy Nexus] Charmacas:
Another report: I switched back from the Nightly from the 15th of May to the stable 1.7 Carbon Rom. And now lags are nearly gone. :) So it maybe was a Nightly issue.

A thought which I had: If voltages AND frequencies are important for the battery consumption, why is it better to set MCPS to 2?

If two cores running at 40 % it does make 80 %. On the other side if one core runs at 100 %, which happens often with the setting 2, and the other runs at 30 % it does make 130 % in addition. That should take more battery in my opinion.

Another example: (a bit lighter)

1: 60 % / 2: 60 % > 120 %

1: 90 % / 2: 30 % > 120 %

I think it may be higher than 30 % but I set that to show that even if it's light we come to the conclusion that even the same power is used. And I think that with option 0 the race to idle may be faster which also is better for out battery.

What do you think [MENTION=4615478]boype[/MENTION] and all the others in here?

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] sergini:
So far r25 is behaving great, never had any sod's with this one, on the other hand, when I was on r24 I had 2 sod's.

Boype: why not implement dynamic fsync? Any reason for that?
[Samsung Galaxy Nexus] gwindlord:
Also as I know, to get the best battery life, it is necessary a day or two to get kernel settled. Wiping battery stats after really full charge (not 100%, but when the device does not take power from charger anymore, could be controlled e.g. via Battery Monitor Widget) can be useful as well - like a slight battery calibration.
[Samsung Galaxy Nexus] vakaviti:
By far the best battery life on my gnex using this with latest liquidrom beta its amazing!!

Never had one SOD or had to pull the battery once coming from Trinity kernel which i was in love with i think i have found my new lover here!!!

Keep up the great work devs
[Samsung Galaxy Nexus] friguy3:
Was getting good battery life bu the lag was just too much. took a very long time to open a video before it started to play. Changed back to "another" kernel and now it all works faster. anyone else have these lag issues?
[Samsung Galaxy Nexus] KelevrA_8:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

I have actually had less lag with this kernel than most
[Samsung Galaxy Nexus] lost_:
#3 extended is UV-friendly. At 11% left now after 36.5 hours with 2.5 hours screen time, some torch, some GPS, a few short calls and some browser and market sessions. Went to work 2 days without recharging. Now, I've gotten similar results with other kernels but Fancy is stable and shows no noticeable lag. Your mileage will vary.
[Samsung Galaxy Nexus] boki2911:
default settings or?
[Samsung Galaxy Nexus] slimdizzy:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

CM 10.1 nightly and and sound modification (ie high performance on or volume boost) and music players freeze. Same as Franco and any other kernel with these mods in. Am I only one getting this?
[Samsung Galaxy Nexus] ak:
No ... the same for me with 10.1 Nightly .. i have to reboot for fix.
[Samsung Galaxy Nexus] lost_:
As noted, undervolted (UV) and, again, YMMV. The UV result is not vastly different than with other custom kernels, but Fancy feels more stable for me. I think if I spent more time with them, I could get similar, stable results out of Air or Lean Kernels (no disrespect to other kernels, those just happen to be my favorite ones in addition to Fancy).
[Samsung Galaxy Nexus] drive2droad:
there are two thing immediately noticeable when using fancy :

1. There is no lag

2. Battery life keeps on improving every day
[Samsung Galaxy Nexus] drafgnjom:
NVM :D
[Samsung Galaxy Nexus] Doublewise:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

Agree no 2, I notice improvement in screen on time. For smoothness not bad, but I think need to be slightly improved,
[Samsung Galaxy Nexus] Karle:
Also getting random freezes. Trying interactive gov now...
[Samsung Galaxy Nexus] koodiifin:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

I use cm10.1 and the pgm premium app and I had freezes with the default gov pegausq. I switched to interactive and it's good so far.
[Samsung Galaxy Nexus] Karle:
tried interactive, but also had one freeze so far... I hope #4 will solve the problem
[Samsung Galaxy Nexus] boype:
I'm working on it :fingers-crossed:
[Samsung Galaxy Nexus] larkhillv:
Wasn't getting freezes until yesterday. Since then, it's frozen at least 5 times. Switching to air kernel or Franco until these issues get ironed out. I was running interactive, stock voltages, and row as the scheduler, BTW.
[Samsung Galaxy Nexus] koodiifin:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

I haven't had a freeze for 24 hrs on interactive gov. Are you sure that your not using interactive x gov?
[Samsung Galaxy Nexus] larkhillv:
Koodiifin, I am positive that I was on plain ol' interactive. Previously, I was on Pegasusq, and it was lag city, so I tried interactive. It was smooth for awhile, and then it started freezing up and getting slower.
[Samsung Galaxy Nexus] Karle:
thats exactly my experience. well, I'm still using interactive and "only" got two freezes, one after hanging up and one while surfing with chrome...knock on wood!

and even though the kernel is quite smooth, I also recognize more and more random lags... damn, I like this kernel, really good battery life, but I hope the issues will be fixed in next release :)
[Samsung Galaxy Nexus] Charmacas:
So I've tried different settings, reverted my ROM to a known stable version and even now it is not so smooth.

Now I also reverted back to r24 which ran here as hell and I got nearly no lags. I will test and report back.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] zoomy942:
I also went back to r24.

The main difference is the 20 to 17 change and white list of systemui.

---------- Post added at 01:26 PM ---------- Previous post was at 01:20 PM ----------

I wonder what the whitelist thing and 20 for systemui would be like.
[Samsung Galaxy Nexus] boype:
Why would the overall load increase by 10% when the load is just transferred to another core? I don't think so much overhead is possible.

In theory, when there's a 60% / 60% split, MCPS should not happen, since it would not be possible to keep one core idle (as you said, the load for one of the cores would have to be over 100%, which is not possible.

Also, the benefits of sched_mc_power_savings is not a myth, there's benchmarks and energy statistics and stuff. sched_mc_power_savings = 2 is the optimal and most battery friendly setting.

http://lwn.net/Articles/297306/

Go ahead and check yourself... You can manually change the systemui priority from terminal:

su

pgrep systemui (this will output the process id)

renice -20 <process id>

Also, the whitelist thing is not making anything smoother. It just prevents the launcher being killed by the low memory killer.
[Samsung Galaxy Nexus] agritux:
i feel it reduced?
[Samsung Galaxy Nexus] boype:
Interestingly, sometimes when scheduler tunables are changed, the touch responsiveness (and scroll speed) is different. I noticed that as well. It is nothing that is directly changed or that is intended. It's just a side effect it seems.