yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Ashtrix:
Unfortunately after the synapse installation it doesn't work properly with my 265 DPI & shows minor errors....
[Samsung Galaxy Nexus] faboz84:
info about synapse

Hi dudes, what the diferrence between Synapse and TricksterMod (i've the paid version).

is there a gain in term of stability?!
[Samsung Galaxy Nexus] kerpert:
After I've installed the r57 the phone vibration has stopped working.

Any suggestions?

The battery life instead has increased a lot.

UPDATE

After a complete wipe and restore of the CM M10 rom + fancy r57, all return working well.
[Samsung Galaxy Nexus] Ashtrix:
They are both almost similar ;) , here iIm using free version though. And no stability difference AFAIK, Plus I think Synapse offers more robust and deep control for free of cost....:good:
[Samsung Galaxy Nexus] Qafix:
I'm still having forced reboots (since r55) and I believe it's due to active display. I've tested switching things off here and there along with previous kernel versions and only when active display feature is turned off does the reboots stop happening. Any idea what might be causing it? I'm using FML 05/07 + fancy r57 currently.
[Samsung Galaxy Nexus] pkgnex:
Those minfree values are the ones developed by osm0sis, myself, and the rest of Franco.kernel Dev Team.

... and they are still the boss settings as far as I'm concerned, at least now that Fancy is back to the standard low-memory-killer! There was a time when boype was testing either 3.4 kernel or Nexus 10 min-free routines and the standard values didn't work, but those changes were reverted long ago.

FWIW, I've been running these settings on every kernel I've used (most of them) for about 18 months, and except for the time when boype and bsmitty83 were tinkering with other routines, they have always been rock solid.

So, feel free to un-comment out those lines in buscher's script.
[Samsung Galaxy Nexus] Jar3112:
What is the converted value of those minfrees?

Sent from my Galaxy Nexus

---------- Post added at 07:11 AM ---------- Previous post was at 06:58 AM ----------

Nvm, found out dividing by 1024

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pkgnex:
You actually need to divide the script values by 256 to convert them to MB.

The conversions are:

6144,8192,12288,16384,24576,40960 (pages) = 24,32,48,64,96,160 (MB)
[Samsung Galaxy Nexus] Pjodor:
Can I convert cache and data to f2fs, not convert system and still use a non f2fs ROM?

Skickat från min Galaxy Nexus via Tapatalk
[Samsung Galaxy Nexus] Ashtrix:
Yes you can :good: .
[Samsung Galaxy Nexus] Jar3112:
Woops! :o

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] boype:
r58

Hi there,

I just pushed r58:

tuna: sharper ram timings according to specs

import latest f2fs kernel 3.0 backport by arter97 (2014-09-26)

net: wireless: bcmdhd: Disable OOB interrupt when WLAN is off

writeback: fix occasional slow sync(1)

static RAMdisk: Merge RAMDISK from CM11 2014-10-04 nightly

Have fun :good:
[Samsung Galaxy Nexus] pianistaPL:
Wow, a little surprise, thank You :) I will tell this again - r57 is working crazy fast and stable, I don't know how did you do but it's really amazing. Please consider to build next version with Google GCC 4.9 :highfive: As I know, it's now a default toolchain, Franco uses it for new versions of his kernels.
[Samsung Galaxy Nexus] aliesz:
Although smitty's dirtyV, Franco and pattyboy's kernels all are very nice kernels but I believe that boype's fancy kernel is another thing that attracts everyone. :)
[Samsung Galaxy Nexus] quickdraw86:
Glad to see a new release, and excited to try it out, am always impressed by fancy kernel.
[Samsung Galaxy Nexus] sergialess:
Is it lately supporting Synapse?

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] Conte Mascetti:
[MENTION=4615478]boype[/MENTION] fancy r58 works just fine, but charging percentage when device is turned off, disappeared again ?

From GNexus
[Samsung Galaxy Nexus] morfances:
Thx Boype!!!

Fancy r58

[IMG="Mandhi 2.8 Unofficial Maguro+ Fancry r58"]https://fbcdn-sphotos-f-a.akamaihd.net/hphotos-ak-xap1/v/t1.0-9/10628404_10204800110673615_3069304625956749894_n.jpg?oh=04571c9c9926d44586166e28da0a5b6a&oe=54AC93A3&__gda__=1422462710_75d850f0a20cd47de697e9b75ce3642d[/IMG]
[Samsung Galaxy Nexus] pianistaPL:
Mahdi for maguro??
[Samsung Galaxy Nexus] morfances:
YEs,Unofficial !! See G+ Community
[Samsung Galaxy Nexus] pianistaPL:
This one? https://www.androidfilehost.com/?fid=95747613655041185 Could you send me a PM how this ROM is working? I don't want to make OT here :)
[Samsung Galaxy Nexus] sergialess:
Let's test the new rom! xD

It could be cool to have a thread here at XDA.
[Samsung Galaxy Nexus] motorazrv3:
Wow mahdi rom looks interesting. A shame that our old device isn't supported officially.

Anyways let's find out how fancy r58 is working with vanirs dho build.
[Samsung Galaxy Nexus] sergialess:
DHO = Commotio?
[Samsung Galaxy Nexus] motorazrv3:
Yes.
[Samsung Galaxy Nexus] sergialess:
I usually use Vanir and not Commotio, but I think I'm going to give it a (new) try ;).

BTW, Fancy R58 is performing awesome in latest Vanir.
[Samsung Galaxy Nexus] motorazrv3:
Try it. As I understood there is no difference between vanir and commotio.

I tested both and I find the graphical design commotio use much better.
[Samsung Galaxy Nexus] RW-1:
Awesome Boype!

I had been checking for a pre_58 all week, figures you had something up your sleeve hehehe.

OT (but related to Gnex users...):

Seems DirtyJerz over on rootzwiki had an idea for us shiny users having such a time with KK and data switching, he checked the APN's and compared them to latest, there were changes, so last Friday some us brave/bold (or stupid hehehe) tried out the new ones - BAM! no more 1-2 minute 4G/3G switching or long data drops depending on one's area.

We're still evaluating, but from m yown experience, it's the best thing to come along since we got KK Shiny on the VZ GNex.

So those out there who haven't tried it, check out the thread over at RW.

/OT

So having a nice new kernel build to go with the new APN is niiiiice! Thank you!

Lastly, anyone else see this, if on chrome beta looking at the newly designed forum thread, on the upper pages I don't get the "Last" link, but if I scroll down, I will see it there ....
[Samsung Galaxy Nexus] cujo6801:
My phone usually heats up

When I'm on a phone call..

But not so much with r58 thanks

Running poos unofficial liquidsmooth Toro

Sent from the "DOG" pound
[Samsung Galaxy Nexus] ashclepdia:
I've been thinking, ever since I've seen the commits and info about the changes made to Bluetooth chip being powered on all the time(now fixed) it has ms wondering if this is ALSO happening with NFC, at least on GNEX.

the main reason I'm thinking this is happening is because even with airplane mode on, and also nfc toggled off in settings, I still see nfc holding wakelocks and "being used". it's not actually functioning though, I've tested that part. no reaction when held up to nfc tags. but a lot of times I'll see nfc as using SOME kind of power when I look to gsam battery monitor. whats weird is that sometimes it will only be a few minutes over say 12hrs, BUT OTHER times I've seen it with over an hour or two. I've even gone as far as ripping nfc antenna out of one of my batteries, but it STILL does this.(btw, it's odd but my wifi connection seems more stable and stronger reception when I use the battery that I've taken nfc antenna out of hahaha)

if I was more technically inclined, I would have already looked into a similar solution for this as was done with Bluetooth. I'm hoping someone else who knows more about this could maybe look into it and see and let us know. also, I don't know if is possible or not, but can a kernel be modified to NEVER send ANY power to nfc? making it so that nfc is just completely disabled all the time? I never use it anymore and have always wondered if I would see any battery improvements from such a modification. which has also made me wonder if a kernel can be modified to NEVER send ANY power to the cellular radios, essentially turning it into a wifi only device, since I already use it airplane mode on with wifi toggled on. just suspicious that SOME battery is still trickling to those radios, since it happened with BT what's to say it isn't happening elsewhere also? even if it was just some battery going to radios during boot until airplane mode got applied, that would STILL be some battery saved. and I'm sure I'm not alone in only using this device on wifi only.

apologies for barrage of questions LOL, been a while since I've been able to use my gnex(wouldn't turn on for longest time :( and I'm loving being back)

can't wait to give r58 a try,.as well as all these other kernel releases lately, friggin love this community
[Samsung Galaxy Nexus] pianistaPL:
r58 is absolutely flying with Omni (full f2fs), this kernel is getting better and better, thanks boype!
[Samsung Galaxy Nexus] massoudsh:
Me too!!
[Samsung Galaxy Nexus] ali4ek:
14,852 in Antutu, nice, thanks!
[Samsung Galaxy Nexus] infectedorganism:
I've been wondering the same thing.

If I disable NFC in settings, the NFC service still runs but no NFC wakelock occurs. If I completely remove every trace of NFC from the system, the service is killed, but an NFC wakelock occurs.

Here is the thread that has a flashable to conveniently remove all traces of NFC from the system. Also, thanks to 7175, I also use this in an init.d script.

chmod 0000 /dev/tty03;
echo 0 > /sys/devices/platform/nfc-power/nfc_power;

Even with all of that, I have yet to find a way to completely kill NFC. And I too removed the NFC antenna from the battery, ha.
[Samsung Galaxy Nexus] ashclepdia:
YES!

I actually think it was a post of yours that I read that inspired me to rip that antenna out.

I just couldn't remember for the life of me where I read it. so thanks for THAT.

are you certain there is no nfc wakelock though? cuz no matter what I tried, I still see nfc within "view kernel wakelocks" in gsam battery monitor(I'll post screens of my next battery usage when I go through one battery of normal use)

also, through some of my testing, I noticed that when I removed certain nfc apks from system, airplane mode failed to initiate properly. so it would SHOW as being in airplane mode, but if I tried to Google it off, it would just not do anything, kinda start to turn radios back on, but then freeze, could use device, but airplane mode would never fully switch either way.

and THEN in battery usage, it would show cell radios signal with red line, as if it were searching for signal, meaning it would drain battery like crazy, cuz without certain nfc apks in system, airplane mode didn't fully activate, which would cause HUGE battery drain, I'm hoping me posting this info will make any others realize that their recent battery drainage could be caused by such a thing as removing certain nfc things from system, cuz I almost blamed it on kernel when I did it, not remembering that I had also done something small like that.

this is why I was asking/wondering, if these things could be fully disabled at kernel, so that any issue like that can't happen since no power is going there ever anyways.

and I'd be happy to build my own kernel if those things were possible, I'm NOT asking at ALL for yet another branch or variant of kernel for those of us who want these things, I just need to know if it's possible, then I could figure out how to build it and maybe,.just maybe be able to "maintain" "Wi-Fi only variants" of kernels. :)

no matter what, if I get answers or not, yall devs are fuggin AWESOME, and you have no idea how much I appreciate everything you do, ESPECIALLY for "aging" devices like this Gnex. so many who cant afford, or even don't WANT to move on yet, and those of us who just enjoy using unofficial builds, and tweaking our devices, without you devs, we have n joy.

okay, enough from ash, I'll wait patiently for any info, and enjoy this r58. I honestly don't even care if it lags, or makes my gnex fly out my hands, the amount of work that has gone into these creations in development section blows my mind, and I enjoy it all, love yall #nohomo

---------- Post added at 01:03 AM ---------- Previous post was at 01:00 AM ----------

even that sys devices nfc_power thing, mine is already 0, that seems to just be something set by going into settings and turning off nfc
[Samsung Galaxy Nexus] quickdraw86:
Commotio and official vanir utilize different scripting, commotio is basically DHO's custom vanir build, just as atom is primedirective's personal vanir...
[Samsung Galaxy Nexus] h4xx0rr:
Rom?
[Samsung Galaxy Nexus] tostep:
AnTuTu 5.1 results (Cyanogenmod 11 M10 + Fancy Kernek r58):
[Samsung Galaxy Nexus] Ziyan:
Shouldn't be. This appears in dmesg when you turn it off:

<6>[43991.316833] nfc_power_apply OFF

So NFC is turned off fine. I don't remember seeing NFC wakelocks anytime at all, so if you do, it's your rom, or some app behaving buggy.
[Samsung Galaxy Nexus] ali4ek:
CM11 M10 snapshot
[Samsung Galaxy Nexus] Ashtrix:
Edited : The charging indicator while power off is workin fine for me here....
[Samsung Galaxy Nexus] GorfDroid:
Is anyone else having issues with video playback freezing the system?
[Samsung Galaxy Nexus] taylerdurden:
Two nights with R58 and two nights that my phone is in coma in the morning. I have lost the alarm for waking up to work!

The phone was with the screen off (logical), but the notification led blinking (I had some notifications), but when I pressed the lock button, It doesn´t wake up. Have to remove the battery.

Revert to R57
[Samsung Galaxy Nexus] motorazrv3:
Two days ago I changed my ROM from dirty unicorns, android 4.4.4 to vanir commotio build, android 4.4.4 and flashed fancy r58.

This combination is absolute fantastic. Phone is performing perfect. No problems at all.

Video playback is working fine. I use my phones alarm clock each morning and the alarm never faulted.
[Samsung Galaxy Nexus] TheMan0790:
Try using the kernel and keep your phone in airplane mode while you sleep. I had this exact problem with the alarm on r57. I now put my phone in airplane mode and have not been able to reproduce this problem.
[Samsung Galaxy Nexus] GorfDroid:
I think I may have cracked it but I still got one freeze. I think it was a Governor issue. I switched from on demand plus to interactive.

I have liquid unofficial with r58 and v6 supercharger as well as trickster tweaks.
[Samsung Galaxy Nexus] sgspluss:
Is it possible to flash this kernel without dirty flashing CM11?

What steps will i do:

- Flash CM11 test kernel (THIS ONE)

- Then will flash this kernel

Is it possible to go on this way?
[Samsung Galaxy Nexus] pianistaPL:
Try out with Ramdisk version and wipe cache&dalvik before flashing. But I'm not sure if it will work.

---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------

I'm happy with latest Fancy and LiquidSmooth 2.37 with full f2fs. It's much smoother than KitKat...
[Samsung Galaxy Nexus] siealex:
What I/O scheduler are you using? It's a common problem with BFQ and CFQ.
[Samsung Galaxy Nexus] pvkiniyan95:
the feautures in ls 2.37 were simply superb that totally suprised me....long press the right corner icon in notification drawer:highfive:
[Samsung Galaxy Nexus] tostep:
See instructions at http://xdaforums.com/showpost.php?p=54582591&postcount=8683
[Samsung Galaxy Nexus] GorfDroid:
I am using sioplus.
[Samsung Galaxy Nexus] CommanderDuplex:
could you make a kernel that works with the new GPU-Driver for this Beta-Rom?

http://xdaforums.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064

the new beta with the new GPU-Drivers works pretty good! but it has just a "Stock" kernel almost :crying:
[Samsung Galaxy Nexus] ali4ek:
Very nice, R58 + CM 11 M11 Snapshot

[IMG="Antutu"]http://i.imgur.com/7UGdzll.png[/IMG]
[Samsung Galaxy Nexus] GorfDroid:
Do you have ART enabled?
[Samsung Galaxy Nexus] ali4ek:
Nope, Dalvik.

TCP Westwood

Read Ahead Buffer 512

Scheduler sioplus

CPU Governor ondemandplus

Max CPU set at 1344000

Minfree control setting by Nephilim:

10

20

100

120

95

195
[Samsung Galaxy Nexus] nailz420:
1420, art, vanir
[Samsung Galaxy Nexus] GorfDroid:
LS unofficial

:)
[Samsung Galaxy Nexus] ataris_kid:
+1 for this!! :victory:
[Samsung Galaxy Nexus] eternal70:
The camera is still buggy. Let the dev's fix that till the whole driver stable
[Samsung Galaxy Nexus] Loureiro:
Wait until gnex developers find a way to fix all the major bugs related to new GPU driver. then kernel can migrate.

You have two options, stick with fml kernel or flash the stable version and choose the kernel you like most.
[Samsung Galaxy Nexus] sgspluss:
Finaly flashed now this kernel after finding some time, just amazing the speed, so now will keep an eye about batterylife... Thank you [MENTION=4615478]boype[/MENTION] for this :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] boype:
r18 is up

Hi all,

r18 is built and uploaded. The changelog is rather long this time:

updated Linux to version 3.0.75

added and enabled SLQB memory allocator

reverted the 10 percent brightness decrease (was just too dark outside)

reverted the still present slight CPU undervolt (was too low, could cause some micro lags)

improved automatic /cache trimming

added power.tuna.so to flashable zip package (fixes the issue with resetting CPU frequency)

fixed slightly inaccurate pixel clock setting

pulled-in another 2 OMAPDSS patches from omapzoom repo

some memory handling tweaks

updated Broadcom WLAN driver (not the backport one other devs use)

decrease the amount of time the device waits after entering low power mode to freeze processes (by franco)

removed 'nodiratime' mount option

probably solved the low-brightness on wake-up problem (not entirely sure; please report)

Best regards
[Samsung Galaxy Nexus] gwindlord:
Updated to r18 via fuss, tried to enable PGM, but it failed to load and then got sudden reboot. Could anyone please confirm?..
[Samsung Galaxy Nexus] Charmacas:
I already reported to PGM thread and everyone else should do the same. This thread is for kernel issues and not PGM.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] stevensoaj:
[MENTION=4615478]boype[/MENTION], I haven't been able to undervolt the ext. version of Fancy Kernel. What I would like to do is be able to undervolt while keeping SR enabled so that I can still see the voltages in Trickster MOD. It's what I've always done when undervolting in the past with other kernels. Any idea why it doesn't work that way on Fancy?

Also, would there be any interest in implementing MIN SR Calibrated Voltages, similar to Lean Kernel or AK Kernel? If you don't have time, or simply aren't interested in adding it to Fancy, I completely understand. I know in the OP you said you weren't interested in modding every part of the kernel, and I enjoy the stability that goes along with that.

So far, r18-ext is running very smooth. And now 1420Mhz is sticking on boot for me. Unfortunately, I can't verify the brightness issue fix, as I never experienced it in the past. Either way, thanks for the hard work. :good:
[Samsung Galaxy Nexus] motorazrv3:
+1

I am back to 17 exp. for now.
[Samsung Galaxy Nexus] kinfolk248:
i get bootloops when i reboot the phone and leave it be, but if i hurry up and start using the phone it stabilizes. Idk whats going on but its highly annoying...!!
[Samsung Galaxy Nexus] boype:
It's the slqb allocator's fault. Will release new version tomorrow.

I suppose this is slqb as well..
[Samsung Galaxy Nexus] stevensoaj:
This sounds like CAB here. If you have Content Adaptive Brightness enabled, try disabling it. Or if its disabled, try enabling it.
[Samsung Galaxy Nexus] guitmz:
Hmm i get this with r15 and latest cm as well
[Samsung Galaxy Nexus] kinfolk248:
idk what slqb even is lol

---------- Post added at 07:49 PM ---------- Previous post was at 07:42 PM ----------

I have it enabled, but i may just wait till tomorrow and for 19 and see if things work out...

thanks for the advice tho!!
[Samsung Galaxy Nexus] gwindlord:
I was sure that if app works on previous kernel version and does not on current one, something definitely changed in kernel and it's worth at least to ensure if the issue happens on my device only. I also was sure it is appropriate and can help to find the real reason, which appears to be actually our goal.
[Samsung Galaxy Nexus] albsat:
There will be a fix soon said the developer.
[Samsung Galaxy Nexus] boype:
r19 is up

Hi all,

r19 is up. Its main concern is eliminating the bugs and errors introduced with the SLQB memory allocator. E.g., PGM works again now.

Changelog:

reverted from SLQB memory allocator to SLUB (fixes PGM issues)

Add assembler versions of AES and SHA1 for ARM platforms (better encryption performance with webpages)

3 minor fixes from ARM and TI

Best regards
[Samsung Galaxy Nexus] agritux:
and fix comes :) r19 released :)
[Samsung Galaxy Nexus] momomok:
actually what is the benefits of SLQB memory allocator over SLUB?
[Samsung Galaxy Nexus] boype:
(http://lwn.net/Articles/311093/)

Probably not a very satisfying answer, since it is very geeky :eek:

Anyhow, if SLQB causes problems, there's no point arguing if it should stay or not. What good is a fast kernel when it's not stable whatsoever?!
[Samsung Galaxy Nexus] Charmacas:
As I used it it was very stable. No problem whatsoever. And the problem with PGM could maybe solved if the author of it updates its app.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] gwindlord:
boype, thank you very much for fast fix! Let us now hope that PGM will fix their issues, and you'll be able to implement SLQB again.
[Samsung Galaxy Nexus] momomok:
PGM is never important to me... so I prefer performance :P

but anyway, I have no complaint - your work is awesome!

it's a pity that your kernel does not gain much popularity... I have been trying hard to promote this good little beast in one local G+ community

and hopefully more crackflasher can enjoy your work :laugh:
[Samsung Galaxy Nexus] boype:
Thanks for the support!

I think the problem with popularity is that I entered the GNex scene too late. Other develeopers do this alomst as a full-time job and became legends - I suppose franco and others can make a living out of their development, selling apps on Playstore and stuff. But that doesn't matter to me. Neither am I an envious person, nor did I ever have the expectation to be very popular or earn money. I just enjoy tweaking kernels. :victory:
[Samsung Galaxy Nexus] redj12:
So you tried this ROM ? I heard many good things about this rom, on officially supported devices.
[Samsung Galaxy Nexus] morfances:
Work fine on maguro !!Although it is unofficial is great, no lags xD
[Samsung Galaxy Nexus] Ashtrix:
Guys, Please stop relying on those AnTuTu Benchmarks (I also used to count on them a lot but not now...they are just on paper synthetics for just an overview) got 15K easily and mostly u can get a max diff of ~200-400.

It'd be better if we go with the personal UX (Like response, gaming, wifi, phone, SOT & rest...) and about those Updated GPU drivers it was hell of a job done by Ziyan, Hashcode & Mwisthebest kudos to them.

Please give time for them to stabilize this progress made so far, Boype would definitely implement them once he gets to know about this new GPU driver update.

Hope i was not mean & a Big thanx to all the devs for keeping this device alive & kickin :good: !!
[Samsung Galaxy Nexus] boype:
Actually, I have been chasing this / similar behavior for over a month now (and finally found the reason).

There appears to be a problem with some fsync commits that are included since r52. Those commits can make the phone hang.

Personally, I've been getting that kind of behavior only with f2fs while listening to music / watching chromecast. ext4 seems fine, however. But since the culprit is not the f2fs implementation but the fsync commits, ext4 might also be affected.

I'll dig a little more into this in the following days and will release a new version when I'm done.