yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sajty:
boype doesnt have Nexus 4 (thanks God) -> no Fancy kernel for Nexus 4.
[Samsung Galaxy Nexus] im the doctor:
so... i hope he won't change phone soon xD
[Samsung Galaxy Nexus] stevensoaj:
The first value echoed in the script disables Content Adaptive Brightness. If you want it enabled, change the value to 1.
[Samsung Galaxy Nexus] Starsream88:
I'm running the latest r32 test version, and my trickster settings dont stick after reboot, dont know whats the problem, i tried cleaning app data, uninstall and reinstall the app but still have the same problem !
[Samsung Galaxy Nexus] quickstang:
They aren't going to unless you set it to at boot.

Sent from my iphone killing Galaxy Nexus running fancy kernel & apophis9283 AOKP ROM. For the love of everyone on forums READ BEFORE YOU POST.
[Samsung Galaxy Nexus] sajty:
Difficult situation now. Stay with r32, where is issue with deep sleep at flash back to r31, where is issue with GPU?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] namtombout:
Deep sleep issue is not the kernels fault

U.O.E.N.O
[Samsung Galaxy Nexus] sajty:
Did you read last few pages?
[Samsung Galaxy Nexus] billouetaudrey:
Thx very much ;)

Envoyé depuis mon Galaxy Nexus en utilisant Tapatalk 4 Beta
[Samsung Galaxy Nexus] CCaaNN:
Hey boype!

Is it possible to use dtim_skip_override with another kernel by creating that file or developer should add this stuff??

Galaxy Nexus cihazımdan Tapatalk 2 ile gönderildi
[Samsung Galaxy Nexus] Riekr:
Kernel dev should add that stuff

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Doublewise:
Boype, could you please add 360 launcher android.process.acore into white list?

Thanks
[Samsung Galaxy Nexus] chikimonke:
So even though LMT launcher is in the white list, I still constantly have it getting killed. It will happen after a long uptime as well as shortly after reboot. Though I've noticed it happening even on other kernels, so I'm wondering if it's more a function of the ROM? Thoughts?
[Samsung Galaxy Nexus] bolanrox:
Sounds like it might be the ROM? I have been using LMT for a few months now (always on fancy), and it has never been killed for me, regardless of up time.
[Samsung Galaxy Nexus] boype:
r32 test 03 up (--> kind of r33 RC1)

Hi all,

I've just finished the work on r33. To see if everything is working, here's another test version:

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

Changes:

optimized LPDDR RAM timings (+ ~10% throughput -> the one from test 01; is it stable for everyone?)

reverted a few commits that might have been responsible for unusual battery drain (remains to be seen...)

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

added 1.3 and 1.5 GHz CPU steps (above 1.2 GHz ONLY the chosen maximum frequency will be used! Works good from what I can tell.)

pulled-in latest interactive governor from Google 3.4 kernel source (should be working okay)

implemented io_is_busy function into ondemandplus governor and activated it (is it smooth enough?)

some other things (I have only listed the most important things here, so that you know what I'm up to)

Best regards :highfive:
[Samsung Galaxy Nexus] zoomy942:
Thank you sir.

So if we pick 1.3 for example, it'll lokc the CPU at that speed?
[Samsung Galaxy Nexus] chikimonke:
I was afraid of that, though it was never a problem just a month or so ago, I didn't notice it until I switched to Fancy. Another question, I use Nova as my launcher, and I have the Aggressive Desktop setting set. I know Nova is also in the white list that Fancy uses. Would the aggressive desktop being active cause the system to reserve too much memory for Nova when using this kernel and it's memory management as well, or are they both basically accomplishing the same thing and they become redundant?
[Samsung Galaxy Nexus] redj12:
What means extended version ? I am new on GN world :)

Envoyé depuis mon Galaxy Nexus en utilisant Tapatalk 4 Beta
[Samsung Galaxy Nexus] im the doctor:
ohu :\

just upgraded my rom and flashed r31, can i flash this without problem ?
[Samsung Galaxy Nexus] boype:
No no ;)

All frequencies up to (and including) 1.2 GHz are used with any overclock frequency. Only from the frequencies above 1.2GHz, there's only used that one you set as maximum.
[Samsung Galaxy Nexus] chikimonke:
From the OP

Extended version additional features

sound control (high performance sound, volume boost)

custom voltage control

fsync toggle

temperature control

zRAM

Also, all test releases are "extended"
[Samsung Galaxy Nexus] Seraz007:
yes ofc u can upgrade kernels anytime

just remember to wipe CACHE AND DALVIC CACHE only ;):D
[Samsung Galaxy Nexus] Riekr:
Each version of this kernel is released in 2 different flavors: STanDard and EXTended.

You can read the first posts to check the differences.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] chikimonke:
Just for clarification, max freq can only be 1.2, 1.3, 1.4 or 1.5? Or if you select 1.3, 1.4 or 1.5 does the 1.2 step still get used as well as the one additional step you chose? Thanks
[Samsung Galaxy Nexus] BOY_:
well boype, haven't been able to test much but what ever you did on test03 to the GPU governors worked! I just set a record on NenaMark2 at 512 MHZ :). Will report back later on battery and I'll test the CPU OCs as well. :D
[Samsung Galaxy Nexus] quickstang:
Good question. I have it set the same. Never thought about the two conflicting or being redundant. I'm curious as to the answer as well.
[Samsung Galaxy Nexus] d0ge01:
the phone is perfectly smooth ever, except when you use as governor interactive, my problem or general issue?

R32 extended , min : 190 Mhz, max : 1.4Ghz
[Samsung Galaxy Nexus] Efrenjr15:
might be the 190mhz

when testing voltages and clock speeds, my phone didnt play well with 192 might wanna bump it up a bit.
[Samsung Galaxy Nexus] Charmacas:
Quick feedback to r32 test 3.

As far as I tested it my RealFeel is that it's slower than r31 but way faster than r32 test 2.

Furthermore I tested the new frequencies. First I thought that if I choose 1,3 it will also use 1,2 but it's nice to see that it doesn't. But it's really good to put 1,2 back to race when using 1,4 or 1,5. :) So... really good work on that boype. As always! ;) You're the developer of my trust!
[Samsung Galaxy Nexus] n2rjt:
With this test, I find that 1.5Mhz isn't good for me but 1.4 is nice. Perhaps 1.5 voltage is too low. I didn't change it and it is same as 1.4 voltage. I'm happy with 1.4. Otherwise, this kernel version is snappy, smooth, responsive. At least within first hour.
[Samsung Galaxy Nexus] boype:
Okay, I will try to be clearer by giving examples:

1) Frequency settings: 192 MHz min, 1.3 GHz max

all frequencies from 192 Mhz to 1.3 GHz are used

2) Frequency settings: 192 MHz min, 1.4 GHz max

all frequencies from 192 Mhz to 1.4 GHz are used, except the 1.3 GHz one.

3) Frequency settings: 192 MHz min, 1.5 GHz max

all frequencies from 192 Mhz to 1.5 GHz are used, except the 1.3 GHz and the 1.4 GHz ones.

It really should not be slower than r31, except... That r32 and later versions are linaro built. Should I give the Google toolchain another go for a test?
[Samsung Galaxy Nexus] Charmacas:
So it looks like I am wrong with my theory. When I set 1,3 1,2 was not used within 5 minutes of use. :D But the system is able to. Hmm... Because there are only 80 MHz between could you disable using 1,2 when 1,3 is set? :)

Sent from my Galaxy Nexus with Tapatalk

-- EDIT --

Hmm... I don't know. Hard to say. I am going to test more.
[Samsung Galaxy Nexus] d4nteps:
Danke boype!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sym_m:
sorry off topic what this theme :confused:
[Samsung Galaxy Nexus] boype:
Oh okay I'll read through the code antoher time and think about the suggestion :)
[Samsung Galaxy Nexus] Charmacas:
Of course: Thanks for what you're doing! But just to be clear: I never asked for another frequency steps neither did I want you to look through the code again. I use 1,2 and I am fine with that! :) I am just suggesting thoughts which came through my mind.
[Samsung Galaxy Nexus] n2rjt:
Still good. I bumped 1536MHz voltage from 1330 to 1385 and it now works. No idea if it works better but at least it runs.
[Samsung Galaxy Nexus] splus:
Yup. I think voltage defaults in kernel need some adjustment for higher frequencies.

Every Gnex should be able to run 1.5 GHz. It's like a birth right considering that's the "normal" max frequency of our TI 4460 CPU. Google only underclocked it to 1.2 GHz because they like everything minimalistic... :rolleyes:
[Samsung Galaxy Nexus] d4nteps:
It's blackout theme x :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zoomy942:
Id think it might be worth a google tool chain build Just for testing.

---------- Post added at 11:11 PM ---------- Previous post was at 10:51 PM ----------

But I will say battery drain is much improved
[Samsung Galaxy Nexus] BOY_:
Well I can say this build is much improved. I'll also say that voltages are too low for my phone to run worth a crap over 1300. With some fiddling I was able to get things stable at 15 but only for testing (I like to have decent battery life, lol).

Looking forward to r33 :)
[Samsung Galaxy Nexus] RevengeFNF:
r32 seems to eat more battery than r31. Linaro toolchain could be the cause?
[Samsung Galaxy Nexus] Blackcrx:
That's already been mentioned and addressed there is a new test03 that's suppose to resolve all issues.
[Samsung Galaxy Nexus] IMGetwired:
r32 test03

Which you can get right here.
[Samsung Galaxy Nexus] Efrenjr15:
R32 t3 is smoooooothhhh but so smooth its raping my battery lol, no worries got another one on the way i think its borked anyways.
[Samsung Galaxy Nexus] apophis9283:
The newest test version is running extremely well for me. To soon to comment on battery but so far so good.
[Samsung Galaxy Nexus] clnzx2:
Switching tool chains will have different effects on different roms depending on what tool chain the rom uses
[Samsung Galaxy Nexus] Blackcrx:
Oh. Didn't know that. If that was true then it would make sense. I have no unusual battery drain with slim or mirage.
[Samsung Galaxy Nexus] zoomy942:
So google tool chain with cm?
[Samsung Galaxy Nexus] nixholas:
Nope. All wrong. It's something like when you're in a gym. You can carry an 8kg weight. But then you switch over to 10kg. Now, you'll have a hard time lifting it. Something like that. If the toolchain in a kernel is newer than the ROMs toolchain, you get alot of issues, like how I did to my kernel. I compiled with 4.8.1 and 4.7 based ROMs would have their data folders damaged, causing soft bricks.
[Samsung Galaxy Nexus] MartianCeo:
This is the first time I've heard of any tool chain issue concerning Roms and kernels. So I am a little led to believe that's nonsense and will continue flashing as normal :D I've been flashing for a while and never had a soft brick or any warning from any Dev about the tool chain of the kernel and ROM.
[Samsung Galaxy Nexus] chikimonke:
So on the latest test release I'm getting terrible I/O scores in Antutu. I know bench marks aren't everything, but the I/O scores were equal to or better than the stock scores of the GNex. On test 3 I'm only getting about a quarter of the stock score. Again, I know benchmarks aren't real world, but I have noticed my phone not being as responsive waking up and things seeming to take longer to load up. Not sure if there's anything that I can get you to quantify any of this. Also, what is the stock RAB for Fancy, I feel like Trickster changed it on its own to 1024.
[Samsung Galaxy Nexus] qu4nd:
Ignore me :)
[Samsung Galaxy Nexus] bunnahabhain:
Can anybody provide an init.d line to set RAB size?

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] Charmacas:
256 is standard in Fancy.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] un.droid:
Im facing a weird issue. Flashed yesterday the latest PAC nightly, flashed gapps. Rom booted all was good. Flashed latest fancy, rom booted, fantastic idle drain over night. Flashed a zip file containing all my apps (made with app2zip, using this since forever and never had a problem) and it takes forever to boot. Right now i think its been like 20 minutes and still on the boot animation. What could cause that?

edit

looks like the zip is damaged..
[Samsung Galaxy Nexus] aHecticLife:
Test 03 is having a huge battery drain..
[Samsung Galaxy Nexus] Charmacas:
This does not help at all.

What is huge for you?

And what are the exact numbers? Flashed and waited two circles to verify? Which program did you use?

Give information!
[Samsung Galaxy Nexus] Starsream88:
No problem here for test 3, soo smooth and 2% of battery drain all over night :thumbup:
[Samsung Galaxy Nexus] pcphobic:
Hmm...interesting....something to ponder on.
[Samsung Galaxy Nexus] mangusZen:
My feel_o_meter benchmark tells that test3 is good and smoother than r32.

sent from Vega gnex
[Samsung Galaxy Nexus] Charmacas:
Could you also test it against r31? Because that's the smoothest version for me so far.

Here: r31 > r32 test 3 > r32
[Samsung Galaxy Nexus] boype:
In my opinion, 4.8.x toolchains are simply 'too beta'. They are fairly new and, as far as I know, there's no 4.8.x toolchain that has been declared stable. I think that's all there is to it.

Someone with more knowledge on this please correct me, but there really should not be any incompatiblities between ROMs and kernels that are built with different toolchains. As long as both toolchains are known to be 'stable', you're all good.

Newer is not necessarily better :)
[Samsung Galaxy Nexus] Riekr:
boype is correct, there should be no incompatibilities since there are no abi changes in generated output. furthermore kernel is less dependant on abi and optimizations and many dangerous compiler optimizations are stripped away even if manually added to the command line.

the soft bricks mentioned are most probably due to some compiler bug (4.8 beta? not necessarily since bugs exists even in stable versions) or some too aggressive optimization, that trigger bugs, wich is not stripped away (user sources generally doesn't mind to strip dangerous parameters).

For example with gentoo linux building the whole system with -O3 would cause bugs until the devs stripped those parameters in the ebuild script of those problematic packages.

Another clarification: many times there is nothing wrong in the code, but enabling a special optimization may break it not for a compiler bug but because even if the code is correct to use that optimization the code would have been written differently. A newer compiler version may or may_not address that issue.

sorry for the partial ot :)
[Samsung Galaxy Nexus] jesssiii:
That's what I'm sticking with too. Just using the performance GPU set to 512, since it was said that would really be the 384.

Toro GNex
[Samsung Galaxy Nexus] stevensoaj:
This is how SlimBean does it.

echo "256" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;

Just change 256 to your preferred value.
[Samsung Galaxy Nexus] boype:
r32 test 04

So, as some people say that r31 is still slightly smoother than all of the r32 versions, here's r32 test 04, which is compiled with the Google toolchain instead of Linaro. The purpose of this is to collect opinions if there is a different feeling between the two.

Apart from the r32 test 03 changes (displayed below), there are few more changes (displayed even further below):

r32 test 04 changes:

compiled with Google GCC 4.7 toolchain (is it smoother than Linaro?)

change 1305 MHz CPU step to 1344 MHz; tune voltages of CPU OC steps for more stability (1305 was too less of a difference to 1228 in my opinion)

Linux 3.0.84

a 'surprise feature' to be revealed at the arrival of r33

Download: http://boypetersen.de/fancykernel/tst/fancy_kernel-tuna-4.2-r32-tst04-ext.zip
[Samsung Galaxy Nexus] shag_on_e:
Hey folks, is anyone having hotspot problems on test 3? I'm about to test 4 now, but when I turn hotspot on it says "turning on" then immediately switches to saying "turning off". I'll check dmesg while toggling and report back later.

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] creeve4:
Is anyone else finding interactive a bit more laggy than ondemandplus on test 3 and 4?
[Samsung Galaxy Nexus] sajty:
No.

No.

But boype will merge some latest interactive patches in r33 (maybe/i hope).
[Samsung Galaxy Nexus] shag_on_e:
After flashing test 4 hotspot is working fine. Must've been a fluke...my apologies.

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] Blackcrx:
I believe test 3 has the new interactive patches already.
[Samsung Galaxy Nexus] chikimonke:
Was Dyninteractive governor in the previous builds, or is that new to Test 4? I imagine this is Dynamic Interactive? Boype or anyone else privy to knowledge know what this governor entails? Trickster doesn't currently have support for it, so I can't get a look at the variables right now. (I realize there are other ways, but that is the easiest) If it is new to test 4, is this the "surprise feature" that was mentioned in the Test 4 changelog?
[Samsung Galaxy Nexus] parthipanramesh:
Wow can't believe it. Test 4 is a lot smother for me. It wakes up blazing fast. And my battery drain stopped. Amazing work!! Thank you very much! :)

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] sajty:
I think,that dyninteractive was developed by franco,so try to search at his thread.
[Samsung Galaxy Nexus] creeve4:
It is the same as Interactive, except the tunables are dynamic adjusted based on usage, hence dyninteractive.
[Samsung Galaxy Nexus] boype:
I think I can say that test 04 is better for me too. To me it seems that the Google toolchain wins the shootout...
[Samsung Galaxy Nexus] aHecticLife:
Sorry about that, and I use trickster, ondemandplus, sioplus. What settings do you use so that deep sleep is effective? :)

What settings do you use? Default?
[Samsung Galaxy Nexus] Nemed:
Test 03 seems to be smoother than test 04 to me...
[Samsung Galaxy Nexus] sajty:
I vote for tst04.
[Samsung Galaxy Nexus] zoomy942:
Agreed. It's running great. Battery drain is much better
[Samsung Galaxy Nexus] x3m.zone:
+1 here
[Samsung Galaxy Nexus] kevdliu:
Hmm its interesting how linaro toolchain actually made the kernel slower and use more battery. I'm wondering if the same applies to ROMs compiled with linaro toolchain
[Samsung Galaxy Nexus] Starsream88:
Test04 is much better, maybe we should wait for Linaro 4.8.1 to get out of beta status.

I have one problem using trickster app, my settings doesn't stick after reboot, even if i activate the apply on boot option :confused:

Please any solution for this problem ? Tried to uninstall and clear app data but no luck !
[Samsung Galaxy Nexus] The Gingerbread Man:
You'd probably find linaro kernels run better with linaro rom and vice versa
[Samsung Galaxy Nexus] jesssiii:
+1

Toro GNex
[Samsung Galaxy Nexus] Charmacas:
Guys please test test 4 especially for battery life. Please use a minimum of two cycles to verify.

[MENTION=4615478]boype[/MENTION] test 4 is better in terms of performance that's for sure. But as you also did other changes than just the toolchain would it be possible that something else did the improvement?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] jeffcavicchi:
Test 4 much better for me as well!
[Samsung Galaxy Nexus] phishn:
Running Linaro optimized atom 422 rom so I'll report how test 4 is vs 3.

And test 3 is smoother on this rom.
[Samsung Galaxy Nexus] DoesntPostAThing:
One thing I noticed, on test 1-3 on boot I see about 300-330mb ram used in trickster. On test 4 I see 400-420mb ram used. Does this have anything to do with the toolchain?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] KeithLing1115:
Test 4 is flying on Sourcery 5.5
[Samsung Galaxy Nexus] not balanced:
Test 4 working much better for me also. Drove 10 hours today, first 5 hours on test 3 and battery drained over 30%. Only drained 13% over the last 5 hours.
[Samsung Galaxy Nexus] cmoG530:
I too vote test 4. I'm loving it all around.
[Samsung Galaxy Nexus] lesp4ul:
No huge battery drain on t4, deep sleep is working good with 3G and google, twitter sync on
[Samsung Galaxy Nexus] adrianmak:
compatible with miui rom ?
[Samsung Galaxy Nexus] Lancez:
Test 4 is much better than previous kernel. Thanks a lot boype :thumbup:
[Samsung Galaxy Nexus] Seraz007:
flash this bad boy before going to sleep

woke up with 3% battery drain overnight

Super kernel!!!!!! :D:D :highfive: :p

im lovin it !
[Samsung Galaxy Nexus] klobkelosh:
Test 4 running smooth as a baby's bottom since boype dropped it earlier today. Good idle drain on 4g in bad coverage area. No issues whatsoever. :Happy: Thank you boype!
[Samsung Galaxy Nexus] pcphobic:
Wow! So many good reviews on test 4 especially in regards to idle drain.... ok man..gonna flash it now!
[Samsung Galaxy Nexus] zoomy942:
It has been much better.
[Samsung Galaxy Nexus] mangusZen:
Holy crap test4! Perfomance wise is stunning! Checking battery for now

Great job boype!

sent from Vega gnex
[Samsung Galaxy Nexus] paarthdesai:
my phone switches off when i oc the gpu to 512..any facing this issue? on the test4 version.. the versions before were working fine.. no settings changed

sent from my sexy Nexy ;)
[Samsung Galaxy Nexus] parthipanramesh:
I just woke up an now I have 1% more battery than last night. Idle drain is suuupeer!!! Great job boype!

I thought that Linaro is faster but it seems that I was wrong.

EDIT: on Aospa (stock)

Sent from my Paranoid Nexus running Fancy Kernel
[Samsung Galaxy Nexus] boype:
I'll put up r33 later today then. Like in 6 hours or something :)
[Samsung Galaxy Nexus] tuemdeluxe:
I just flashed r32 test 4 and I'm really impressed. I used to run ak's skl 248 kernel with 1600mhz as a daily driver.

Now r32t4 runs at least that fast with 1500mhz max, I love that added higher frequencies and I'm really looking forward to test r33 although it almost can't get better :eek:

It's really nice to see this dedicated developers for a quite old device, thanks a lot and big respect for you boype!
[Samsung Galaxy Nexus] Nemed:
I'm on test 04 too and i'm not facing any issue with gpu up to 512...
[Samsung Galaxy Nexus] flatflo:
Someone tested r32 with latest vanir rom?
[Samsung Galaxy Nexus] natezire71:
Yep, runs like a dream.
[Samsung Galaxy Nexus] bluerez79:
Running very well for the hour I've been using them together
[Samsung Galaxy Nexus] phishn:
All you folks blown away by test 4 on non Linaro optimized roms? It's not as smooth on atom 422 and overnight battery drain went from 1.0% per hour to 1.3% per hour.
[Samsung Galaxy Nexus] Charmacas:
Did you test it at least for two cycles?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] TnK8iD:
the flashing time is coming :D
[Samsung Galaxy Nexus] im the doctor:
r31 drained 5% this night, r32 almost 9/10%

i hope r33 will be awsome like r31 :D
[Samsung Galaxy Nexus] zoomy942:
I'm curious about the surprise feature
[Samsung Galaxy Nexus] kinfolk248:
am i only one still using sourcery rom with this kernel...?????
[Samsung Galaxy Nexus] Starsream88:
Maybe it's the cgroup timer slack feature :p

Anyway we will discover it in fiew hours :D
[Samsung Galaxy Nexus] thisguy23:
I know 33 is coming later but wanted to say that I've been using the test builds and b4 is the best of them all. Very nice! Great job!
[Samsung Galaxy Nexus] im the doctor:
r33 is online on boype site :Q_ gogogogo flash
[Samsung Galaxy Nexus] quickstang:
He said 6hrs so that would be 9a my time, so that's about right. Anxious to see the change log.
[Samsung Galaxy Nexus] sajty:
Already booting with r33 :D.
[Samsung Galaxy Nexus] boype:
I just used Apollo (and ondemandplus + sio + 1024kb readahead). Don't know why the kernel would make rocket player crash :confused:
[Samsung Galaxy Nexus] bolanrox:
Do you think there is doing to be a drastic difference between using sio and row? or are both pretty similar?