yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] gautam_nexus:
what are your settings..? I am only getting around 12.6k
[Samsung Galaxy Nexus] motorazrv3:
This kernel has always been on steroids. Thx boype for your update, time to download and flash.

Gesendet von meinem Galaxy Nexus mit Tapatalk

---------- Post added at 02:00 PM ---------- Previous post was at 02:00 PM ----------

Overclocked to 1420 MHz. Look at the screen.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] motorazrv3:
Just flashed, booted up without probs.

Touchcontrol 1.8.5 in combination with cm11 module works fine.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] agritux:
[MENTION=4615478]boype[/MENTION]

i am using carbon rom, i am on latest nightly

i wiped cache and dalvik cache and flashed r45 but after system boot "system media storage", "play store", "calander storage" etc gave fc and fc and fc...

i removed the battery and wiped cache and dalvik again

no fc for now

i take a logcat but it didnt show anything because i take it after reboot

i dont know what happend or what is wrong

i can take only screenshots...
[Samsung Galaxy Nexus] Edoardox:
Hi [MENTION=4615478]boype[/MENTION] can you tell me where can I find the ASRAM version of your magnificent kernel? :) thx for your work!
[Samsung Galaxy Nexus] infectedorganism:
The changelog for the newest version (r45) says:

[*]ASRAM instead of BIGMEM (was in pre45-2 already)

If that is what you're looking for, the link is in the first post of the thread.
[Samsung Galaxy Nexus] boype:
This.

I still have to update some of the documentation in the OP to make that clear :)

But it's all okay now, right?!
[Samsung Galaxy Nexus] agritux:
Yes! As usual, everything is GREAT! :)
[Samsung Galaxy Nexus] RevengeFNF:
Using the last r45 version, with no problems so far.
[Samsung Galaxy Nexus] infectedorganism:
Bumping this post. Any truth to this?
[Samsung Galaxy Nexus] boype:
[Update for the knowledge base]: You can disable MMC CRC checking by adding this line to an init.d script:

echo N > /sys/module/mmc_core/parameters/crc

Of course, CRC is a mechanism aiming to prevent data corruption when enabled. So if you disable it, there may be a chance you run into problems.

That said, I would not exactly recommend disabling CRC if you have your work-in-progress master thesis saved on your phone.

On the other hand, there may be some good speed improvements - but I have not benchmarked anything yet.

DirtyV kernel for example has CRC disabled by hardcoding that setting and as far as I know, there have not been any reports of data corruption.

I myself have disabled CRC for a couple of days now and it runs just fine.

I'll check it out
[Samsung Galaxy Nexus] Alkemix:
You must use into init.d script:

echo N > /sys/module/mmc_core/parameters/crc

or if You can re-compiling the kernel .. set int use_spi_crc = 0; from code
[Samsung Galaxy Nexus] boype:
I wasn't sure about 0 and 1 are working too instead of N and Y, but they are. So you're fine with both letters and numbers.

And I'd like to leave the choice about disabling such a potentially delicate settings to the users instead of hardcoding :)
[Samsung Galaxy Nexus] qu4nd:
Sorry if that's a noob question, but what is this for?
[Samsung Galaxy Nexus] infectedorganism:
From the changelog:

[*]mmc/core: implement sysfs variable to switch CRC off / on (you can now disable the memory's CRC (cycle redundancy checking) via sysfs: 'echo N > /sys/module/mmc_core/parameters/crc'. This may gain you a faster file system and overall experience)
[Samsung Galaxy Nexus] Alkemix:
0 and 1 are wrong ;) ... y and N are right :good: in fact I've tried by hardcoding and If I set to 0 "int use_spi_crc" , N appears into path /sys/module/mmc_core/parameters/crc ;)

Boype this change together "ext4: speed up truncate/unlink by not using bforget() unless needed" commit work fine! Great system smoothness improvement !!! :good:

I've not included into re-compiled kernel this "CONFIG_OMAP_32K_TIMER_HZ=256" for now...

If You disabled crc (cycle redundancy checking) ..file system will be more reactive but maybe (probably) less secure for data lost
[Samsung Galaxy Nexus] boype:
Yes you are right, but you can also use 0 and 1 as sysfs input parameters. If you 'echo 0 > ...' into the variable, it will also be set to N. The sysfs accepts both letters and numbers for this boolean variable. That's what I wanted to say :eek:
[Samsung Galaxy Nexus] Alkemix:
Ah ok.. better that way ;)
[Samsung Galaxy Nexus] jwillmeng:
I'm sorry if this has already been covered, but how exactly do we make it go faster?

I feel like some kind of android-kernel-speed junkie.
[Samsung Galaxy Nexus] cujo6801:
Well the way I do it is I jump in my car I jump on the freeway and I bring it up to a hundred miles an hour..

Sent from the "DOG" pound
[Samsung Galaxy Nexus] jwillmeng:
I like it...OC'd to 100mph!

I'll have to look for that setting.
[Samsung Galaxy Nexus] Charmacas:
I would like to say that the CRC thingy does not to effect the performance much. I would say it is not even noticeable. So I would prefer to let it switched on because it is a potential risk.

In all other terms: Fancy runs great again! Good to have you back boype. ☺

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] CommanderDuplex:
could you disable SR for frequency higher than 1.3Ghz ? so I can use 1.5ghz ... It works only on DirtyV and on Francokernel atm. at all other kernel i got instabilities :crying:
[Samsung Galaxy Nexus] friedCELLS:
Odd. I was running CM Remix for 1 week without issues. Was using SmittyV. Then to try this kernel, I wiped dalvik and cache and flashed. Tried twice. Wouldn't boot. Wiped dalvik and cache again, flashed SmittyV, and that was fine again. Maybe it has to be installed on a completely fresh install of a ROM? Really bummed, because I want to try without wiping everything.
[Samsung Galaxy Nexus] gummie:
Woah, [MENTION=4615478]boype[/MENTION] is officially back in the biz. I can confirm that the USB OTG issue is now fixed. So far no issues encountered, have to play around more while I still got the hold on the GN. BTW, any chance you would be on N5? Lol, only a month now before I sell my N4 because unfortunately my Wife don't want it because it does not support OTG.
[Samsung Galaxy Nexus] motorazrv3:
Strange. Normal way is just to flash kernel. Maybe a bad download. Have you tried downloading and flashing again?

Another way to try is: wipe cache and dalvik, flash your currently used rom again and flash fancy of course.

Besides all of that do a backup before for your safety.

Good luck.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] friedCELLS:
Thanks for the help. I decided to go ahead and flash a new Rom and this kernel. And I'm glad that I did. Liquid Smooth with this kernel is the best that my phone has been in a very long time. So happy. Great that Boype is back. My 2 core nexus feels like it has 8 cores :cool:
[Samsung Galaxy Nexus] qu4nd:
Unfortunately wifi doesn't always automatically reconnect when entering a wifi covered area.

Worked fine on DirtyV...
[Samsung Galaxy Nexus] gummie:
Hi again, attached is the first battery cycle from the new Fancy Kernel r45. This is on 3G and WiFi On straight till critical battery and playing game, got minimal lag due to quite intense visual effects and prolonged CPU work load. No WiFi drops during deep sleep. I guess this result is quite decent considering this is just the first cycle :good:
[Samsung Galaxy Nexus] RevengeFNF:
I got 4 hours on my first use in screen time. Im using the 2000Mah battery.
[Samsung Galaxy Nexus] Piti8576:
Works, for me no problems ;)

I use the app wifi connection manager and bind wifi to mac adress.

https://play.google.com/store/apps/details?id=com.roamingsoft.manager&hl=de
[Samsung Galaxy Nexus] Astug:
No offense, but does that mean it's actually NOT working for you and you have to resort to a 3rd party app to get it to function as it should?

I just don't want any misinformation out there. It used to work correctly on 4.1.2, ever since then it's been an issue.

For those unaware of the issue I'm speaking of:

Wi-fi doesn't automatically connect to known networks, f.ex. when I arrive home from work, it doesn't connect to my home network.

I have to manually go into the wi-fi settings menu and scan or connect to my network.

I (& many others) have the same issue and have been looking for an actual solution that can simply be implemented into the kernel or ROM, to stay as true to stock as possible.
[Samsung Galaxy Nexus] Piti8576:
When i have only one wifi account saved, the autoconnect works fine for me when i come home.

But when i have more then one network saved (i have over 10) then the autoconnect don't work.

But with the app it works every time by me.
[Samsung Galaxy Nexus] TheGeekRedneck:
I just wanted to pop in and say how awesome it is that Boyd has come back to continue updates for Fancy Kernel. I am extremely happy!

I have tried just about every custom kernel out there for the Galaxy Nexus (especially recently when CM made the ramdisk changes that caused problems with previous versions of Fancy). No other kernel offers the speed, stability, and impressive battery life that Fancy brings to the table. If the project had been abandoned there would have been many sad pandas out there, and I would be one of them. So glad to see you again, Boype!

As for the Wifi issues.... I've never experienced them. I routinely go in and out of Wifi and my handset has no problems with connecting automatically to a learned SSID when in range. This is using Cyanogenmod 11 nightlies (and 10 before that) and using 2.5ghz connections.

I'm wondering if the people having issues are using 5ghz connections knowingly or unknowingly? It's no secret that the GNex has a 5ghz radio that's absolutely abysmal even under the best of circumstances. Most handsets I've seen can't reliably hold a 5ghz connection and when they do the range is terrible.... just a thought. ;)
[Samsung Galaxy Nexus] nikodr:
Does the latest version have a bigram version that has 1080 p enabled like the paranoid android stock kernel tga has 65 additional Mbytes of ram with 1080 enabled?
[Samsung Galaxy Nexus] erghetto:
yes, it has ASRAM and 1080p

edit: hey [MENTION=4615478]boype[/MENTION] i've noticed that phone used more 384 mhz or 500, and then if it needs more cpu tends to use 1228. 700 and 100 are quite ignored..

later or tomorrow i'll post some screenshoots, but in the meantime could you tell if it's ok, or if i can change some parameters?
[Samsung Galaxy Nexus] Ashtrix:
Every governor and the kernel has it's own setup, for eg. Im on Mpo's Hyper with an 1.4GHz OC and i can never see that 1.3 step plus adding to that even those 1.2GHz and 1GHz step are at ~0-1% that doesn't mean it's a problem, it's just fine and fancy's code is just great :good:!!!
[Samsung Galaxy Nexus] boype:
This is not kernel specific, it is CPU governor specific. ondemandplus tends to use 384, 729 and 1200 steps the most with stock settings. It's like that because those are the chosen steps to be used while scaling the CPU frequency up. When the frequency is scaled down, the intermediate steps may also be used.

With many governors, leaving out steps while scaling up is intended to save time and make the phone more responsive.

Take the following example with two scenarios:

1) You use a governor that scales up to the next higher speed if you have high load (= does not skip steps). If we assume 20ms of time to scale up for each step, you need 80 - 120 ms time to reach the full speed. This causes the phone to be less responsive.

2) You use a governor that leaves out steps, like ondemandplus and interactive. those governors reach full speed in shorter time, improving responsiveness.

Hope this helped you in some way, assuming you didn't know this already :)
[Samsung Galaxy Nexus] erghetto:
as always very gentle :D and very usefull everything you explain :D thank you very much boype. i've read something at this your link

http://xdaforums.com/showpost.php?p=38456009&postcount=390

and it has been very usefull. i asked you that thing because i thought that using more 729mhz and 1036mhz before jumping immediately to 1228 could be good to save a bit of battery.. so i was trying to understand. now i know that it is meant to be a specific choise to have more responsiveness

thanks again boype :D
[Samsung Galaxy Nexus] d0ge01:
Yes sir, but i noticed that full speed is almost useless... I always change all tunables to use always 7xx mhz step ( input boost and high speed ) , 1200 mhz is useless except high load, with high_speed = 729000 and above_highspeed = 80000 ( instead 20000 ) i can achieve 10-20% more battery life without any visible lag
[Samsung Galaxy Nexus] wasdf:
It seems we can't overclock with the latest r45:confused:
[Samsung Galaxy Nexus] namtombout:
I think only performance governor is derped, but overclock works on ODP
[Samsung Galaxy Nexus] wasdf:
I see.. just double check with ODP and it is working, interesting... :silly:
[Samsung Galaxy Nexus] joelmonty:
This is the best kernel , no unnecessary heating, best performance, best color , very stable .
[Samsung Galaxy Nexus] agritux:
and battery life is great :)
[Samsung Galaxy Nexus] boype:
Haha I like that testimonial slogan in your signature picture: 'perfect with f' ;)
[Samsung Galaxy Nexus] tostep:
r45 BIGMEM Version

boype, first of all, thanks for your very nice kernel! :)

Are you going to make BIGMEM ('big') of r45 version? :confused:
[Samsung Galaxy Nexus] erghetto:
o.O but this is already a bigmem XD well, ASRAM to be right.
[Samsung Galaxy Nexus] siealex:
And are you going to make a 4.3 version? I'll not switch to 4.4 until PA makes a fully functional hybrid engine.
[Samsung Galaxy Nexus] shadowam:
Hey, could you tell me what's this APP name?
[Samsung Galaxy Nexus] Qafix:
Has anyone gotten an error on video recording mode? I can't choose the option of recording coz the camera app would then fail. Normal camera and photo sphere mode seem to be working well. I'm using the latest r45.

---------- Post added at 10:51 AM ---------- Previous post was at 10:08 AM ----------

I flashed the pre-45-2-fixed and video recording started working again. Gonna stay on it for the moment.
[Samsung Galaxy Nexus] gummie:
Mine is recording just fine at 1080p setup, maybe you just missed something like clearing cache and dalvik mybe? USB OTG doesn't work on pre45-2 that's why I had to ditch it for sometime but now it's fixed so I'm happy now.
[Samsung Galaxy Nexus] Qafix:
It's great that your video is working just fine. Unfortunately that doesn't really answer my problem question. I've made sure not to miss things like clearing cache and dalvik and I've reflashed a few times but to no avail. Even cleared camera app data and made sure the media_profiles.xml has no error. Maybe it's because I had it set up at 1080p on the pre version before flashing the current but I have yet to test that theory; I'll be sure to do it today. Thanks.

P/S: Big OP fan as well!

Edit: I did what I said I would try, I set video settings as 720p first, then flashed r45 and hey presto, video works and I set it back to 1080p and all is well :)
[Samsung Galaxy Nexus] wasdf:
https://play.google.com/store/apps/details?id=com.roy.wifimonitor
[Samsung Galaxy Nexus] tostep:
According to 1st post Extended ('ext') version of r45 only is available now. And BIGMEM gives you an additional ~65 MB of available RAM, but disables 1080p video recording modes, however. So I repeat my question:
[Samsung Galaxy Nexus] erghetto:
ahh ok, i thought you were reffering to ASRAM. actually available RAM is 743 MB

i don't think boype is planning to do a superram version without 1080p. well, this is what i hope XD
[Samsung Galaxy Nexus] L-ViZ:
hey guys. got a little question.

i am still on 4.3 but want to try a 4.4 rom. is there a fast/stable 4.4 rom?

which rom do u use or recommend? atm i am still on psx but i think it might be time to upgrade :)

if u don´t want to bloat the threat u can write me a pm. would be really happy about suggestions :)
[Samsung Galaxy Nexus] infectedorganism:
I think he ditched BIGMEM in favor of ASRAM. Hopefully he can give you a solid answer on that though.
[Samsung Galaxy Nexus] thomstrack:
I stayed a long time in 4.3 for that reason, but I'm from the middle of February with Shiny and ROM is fast and smooth. (combination in my signature) :D
[Samsung Galaxy Nexus] thomstrack:
Idle drain on overnight it's really great! Only 6~7℅ in 10h (0.6℅/hour).

Amazing work [MENTION=4615478]boype[/MENTION]! Thank you so much! :D

Sentido from my Galaxy Nexus 4.4.2
[Samsung Galaxy Nexus] qu4nd:
This one is very stable. Performance and battery are pretty nice.

But unfortunately I have to say that I'm suffering from wifi-drops and the matter of not reconnecting to WiFi when entering a WiFi area...
[Samsung Galaxy Nexus] agritux:
Look my signature ;) i prefer carbonrom + fancy kernel. Slim, stable, smooth and many customization! Best for me.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rjshrjndrn:
Do you have any custom kernel settings? Coz my battery drain is comparatively large! But I love Fancy kernel since 4.3!
[Samsung Galaxy Nexus] sym_m:
you will never find rom like CM11 its very fast real perfect rom
[Samsung Galaxy Nexus] L-ViZ:
thx for rom suggestions :)

atm using carbon, makes a solid/stable/fast first impression :)

didnt flash something since latest psx version (9months ago), nice to have some new stuff and again with fancy kernel ;)

so thx at boype for this awesome kernel and the rest of the community :)
[Samsung Galaxy Nexus] thomstrack:
This test was with default settings. The only change it was minfree settings by Nephilin, but this no effect in battery in this case.

This can be ROM effect, what rom you use?

My combination: ShinyROM(stock-like) + FancyKernel has been perfect for me.

PS: one thing that can make a difference too: Greenify! ;)
[Samsung Galaxy Nexus] aliesz:
Stable slimkat build 3.0 with the fancy r45 kernel surely is the best choice between all ROMs and kernels released until now.
[Samsung Galaxy Nexus] L-ViZ:
[MENTION=4615478]boype[/MENTION]

coming directly from r43 (4.3). could it be that the wifi performance isn´t as good as in 4.3? at least for me it seems like that my wifi was a lot faster on 4.3. tested two roms and both have got pretty much the same wifi speed, both is lower than on 4.3. (even both times with latest fandy kernel)

used always westwood so it only could be the router or 4.3 // 4.4 difference or the kernel. besides from that i´m scoring a lot higher with 4.4.

with 4.3 i always had about 3700p in quadrant.

not i got 4400p :)
[Samsung Galaxy Nexus] victor2868:
Is this kernel support touchwake?
[Samsung Galaxy Nexus] qu4nd:
The question is, does Touch Control support this kernel?

And the answer is to use the search function... It's probably been asked before...
[Samsung Galaxy Nexus] victor2868:
Haha...OK! Thx for the correction
[Samsung Galaxy Nexus] boype:
It's possible that 4.3 performed better with WiFi. But this cannot be caused by some kernel change, because there have not been any WiFi related ones.

I have rather weak WiFi in some rooms of my apartment and I have not seen any differences between the two android versions.
[Samsung Galaxy Nexus] L-ViZ:
i did a hell of a lot tests to find out what caused the low wifi speed. now i know it.

i´m using fancy + carbon rom.

the low speed came by enabling art. on dalvik the speed was normal.

so for all people who use art on carbon, the wifi speed will problably decrease.

just so happy that i know what caused it :D really made me crazy to know that my phone didnt work properly without knowing why it behaves strange :D
[Samsung Galaxy Nexus] franchixco:
Boot Loop on PAC-MAN 4.4 ROM

I have a bootloop testing r45 in Pac-Man 4.4, I wiped /cache and /dalvik-cache, the download is fine (not corrupted). Using adb sideload don´t work too. anyone have the same ROM?
[Samsung Galaxy Nexus] 47th_Ronin:
Pac ROM can only use kenels that are any-kernel format as far as I know.

I've not found any with a ramdisk that work other than lean-kernel and burstlambs burst kernel which is lean kernel based by the way.

Of course PAC comes with lean kernel I think, so that may be why those work.
[Samsung Galaxy Nexus] -Jesco-:
PAC need a line in ram disk to point to it's framework , I'll send a pull request for boype after I go home from work

EDIT: send the pull request .
[Samsung Galaxy Nexus] alienmind:
Is there a "big" build for r45 ? Thanks
[Samsung Galaxy Nexus] tostep:
I asked about this question: http://xdaforums.com/showpost.php?p=51455786&postcount=7727, http://xdaforums.com/showpost.php?p=51480795&postcount=7735. But boype (autor) haven't answered yet.
[Samsung Galaxy Nexus] AutomaticFailure27:
I'm pretty sure he changed from bigmem to asram since it's only about ~10mb difference and doesn't disable 1080p. After following the Dirty_V thread, memory management is more important than having more available ram. His builds are running "normal" amounts of ram yet handles oom/lmk situations perfectly (lmk currently is having a bit of a bomb out lately though)

Really, there is no reason to have a bigmem version anymore. Just tweak the minfrees and other memory management areas and it should run flawless.
[Samsung Galaxy Nexus] boype:
What he said ;)

Speaking of minfree values: did you dig into this by any chance, so that you could propose better values?
[Samsung Galaxy Nexus] AutomaticFailure27:
Not entirely. I use what [MENTION=4544860]osm0sis[/MENTION] and the Franco Dev Team proposed. I also tried what [MENTION=3777325]wavedashdoc[/MENTION] and [MENTION=2853378]Nephilim[/MENTION] use but found that seems to cause more redraws and killed apps faster but it does increase the overall performance.

Once I get home I can post the actual values unless one of the mentioned gets to it first ;)
[Samsung Galaxy Nexus] thomstrack:
I have used the minfree by Nephilim and have a very good result. :)

Forground App: 10

Visible App: 20

Secondary Server: 100

Hidden App: 120

Content Provider: 95

Empty App: 195
[Samsung Galaxy Nexus] osm0sis:
minfree uses an interim boot value before switching to the default. The amount of time varies per device so I wait for the defaults and then set a custom value. Otherwise it'll just get overwritten.

minfree=6144,8192,12288,16384,24576,40960;
lmk=/sys/module/lowmemorykiller/parameters/minfree;
minboot=`cat $lmk`;
while sleep 1; do
if [ `cat $lmk` != $minboot ]; then
[ `cat $lmk` != $minfree ] && echo $minfree > $lmk || exit;
fi;
done&

Another idea was rounding stock defaults:

minfree=12288,15360,18432,21504,24576,40960;

The higher last number is the most important thing though. Worth mentioning that they don't have as large an effect as they did on 4.2 or even 4.3.
[Samsung Galaxy Nexus] aamadorj:
Good to have boype back!!

I just finished running a quick comparison of stock ParanoidAndroid 4.2BETA3 kernel, another very popular GN kernel and Fancy. With Antutu, under similar conditions and settings (interactive governor, no OC, same minfree settings), Fancy Kernel r45 scored around 11300, the highest score of all three.

My device feels very smooth with this kernel, there are no problems at all (freezes, microfreezes, SODs, reboots) and so far battery life is very good. :highfive:

Thanks a lot, [MENTION=4615478]boype[/MENTION].

Note: I disabled Fancy memory CRC before running the benchmark with the command shared by the dev.
[Samsung Galaxy Nexus] dadenet:
Dear Friends ,

Could use this kernel on Nexus 5 ?
[Samsung Galaxy Nexus] agayabag:
No
[Samsung Galaxy Nexus] boype:
Hi folks,

I'll be posting a new version tomorrow. Nothing major, but a few bugfixes and improvements.

Take care ;)
[Samsung Galaxy Nexus] GilGameshn1:
Change to WPA from WEP ... could be the prob . new WiFi driver cause this .

Sending From Nephalem Rift
[Samsung Galaxy Nexus] qu4nd:
Haven't used WEP for a long long time ^^
[Samsung Galaxy Nexus] boype:
..and I don't recommend you do - it's hackable within seconds. :o

Apparently there is a good chance Google fixes all dropout and no-reconnect issues with android 4.4.3. At least that's the rumours fueled by leaked information...
[Samsung Galaxy Nexus] jwillmeng:
deleted