yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] stevensoaj:
Despite being set on 3100 initially, mine is actually running quite nicely on 2500. So far at least. :fingers-crossed:
[Samsung Galaxy Nexus] siealex:
On 2500 my screen becomes too bright and non-uniform (horizontal stripes). Are you experiencing the same?

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] pcphobic:
Originally Posted by sajty

Here you go:

- governor: interactive

- scheduler: bfq

- frequencies: min screen off 192MHz,max screen off 537MHz,min screen on 384MHz,max screen on 1344MHz,hi_speed_freq 729MHz

- RAB: 512

- CAB: on

- vibrations: 100

- GPU: 384MHz

- colors: slightly modified morfic

- UV (from the lowest frequency): 750mV,800mV,850mV,950mV,1075mV,1175mV,1200mV

I didnt see any difference between r35 and pre36-1,definitely there is no battery drain,that was reported by some users.

[MENTION=1482521]SuperSalvo[/MENTION] I am using [MENTION=4885250]sajty[/MENTION]'s settings. It does help me gain better battery life especially screen usage time.

---------- Post added 25th August 2013 at 12:03 AM ---------- Previous post was 24th August 2013 at 11:54 PM ----------

http://xdaforums.com/showpost.php?p=25485028&postcount=365

Yeah I read that reducing the VAUX3_6030 & VUSIM values helps increase screen usage time
[Samsung Galaxy Nexus] siealex:
Where can I adjust vusim?

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] Seraz007:
yup and then it reboots :eek:

---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------

umm can't seem to find the VUSIM option

all i have is the VAUX and VMMC
[Samsung Galaxy Nexus] pcphobic:
Hmmm....

I think u can try adjusting VAUX3_6030 first.
[Samsung Galaxy Nexus] siealex:
2800 works fine, 2600 or less makes the screen look ugly and flicker.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] sajty:
ATM,i am running this:

- governor: ondemandplus

- scheduler: bfq

- frequencies: min screen off 192MHz,max screen off 537MHz,min screen on 384MHz,max screen on 1344MHz

- RAB: 512

- CAB: on

- vibrations: 100

- GPU: 307MHz

- colors: slightly modified morfic (130,130,200)

- UV for MPU (from the lowest frequency): 750mV,800mV,850mV,950mV,1075mV,1175mV,1200mV

- UV for VAUX3_6030: 2750

- UV for VMMC: 1500
[Samsung Galaxy Nexus] DaNi_!:
OK, here are my logos/signatures for the ones who want them:

- The colored one (purple & green): http://imageshack.us/a/img853/3158/3fel.jpg

- The grey one: http://imageshack.us/a/img41/8105/6vsu.jpg

I've also made a kernel boot splash image, flashable zip later...
[Samsung Galaxy Nexus] gamerman123x:
The kernel boot splash image failed when i tried to flash ?
[Samsung Galaxy Nexus] DaNi_!:
I noticed, working on it.
[Samsung Galaxy Nexus] gamerman123x:
ok thanks :good:
[Samsung Galaxy Nexus] boype:
Nice logos there, I like!

Prepare for pre40-2. It has zsmalloc and zram from 3.7 kernel. And lz4 compression for zram.

I feel like it's flying :o

Uploading in about 12 hours, though.
[Samsung Galaxy Nexus] Charmacas:
Cool! So we have to activate zram again? :)

I mean usually zram is not useful for our device. But if you're saying it's flying I will definitely try it out. ;)
[Samsung Galaxy Nexus] nitsua98:
So for people who don't use zram, we won't see much of a difference?
[Samsung Galaxy Nexus] Citizen_Snips:
[MENTION=4615478]boype[/MENTION] Using r39_ext and Pandora kept getting killed at work. I wouldn't close out of the app or swipe it away but eventually the music stops and I unlock the phone and Pandora shows the initial screen when you open the app for the first time after booting the phone for example. All stock kernel settings.
[Samsung Galaxy Nexus] jesssiii:
No, please. Just, no. Please.
[Samsung Galaxy Nexus] okanb3:
Waiting commits to checkout and try to build from source. Just for fun :)
[Samsung Galaxy Nexus] angourakis:
+1

While I love boype´s work and would use his kernel with or without a logo on it, I think the cleaner the better!

Anyway, feeling really excited for the new staff! boype, were all the "tricks" from the previous 4.2.2 versions already implemented in the newer 4.3 versions or you are reimplementing it one at a time?

PS: I would love if the devs could work on the GPU code to make the speeds switch to be efective... #justathough

Regards
[Samsung Galaxy Nexus] shawnaye:
hopefully the 12 hours would be well spent testing time for your kernel then!
[Samsung Galaxy Nexus] nitsua98:
3 hours left, guess I'm staying up until 4am :p
[Samsung Galaxy Nexus] boype:
pre40-2

I don't want to be responsible for you not getting enough rest ;) So here's the link. I'll add the description later.

http://boypetersen.de/fancykernel43/tst/fancy_kernel-tuna-4.3-pre40-2-ext.zip

[edit]

here's the change log

backport zram and zsmalloc from the 3.7 kernel and adjust them to 3.0 kernel

add lz4 compression libraries to kernel

implement lz4 compression into zram via a general crypto API

Credit goes to faux123 who was the first one to do most of this. I cherry-picked a couple of commits from his repo.

There's not much you need to be looking out for. I think the zram / lz4 implementation is solid, fast and stable. I won't hurt to test it nevertheless. More importantly, general stability is still an issue: In r39, there were people who reported random reboots, which I tried to fix with pre40-1. I have not heard anything stability related until now... Is there anyone who can comment on the stability of the pre40 versions compared to pre39?

Oh yes, for those who want to activate zram via init.d: Here's a script for 64 MB zram.

#!/system/bin/sh

echo 67108864 > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
[Samsung Galaxy Nexus] sajty:
Totally agree. No bootsplash please. It's like when 5 years old guy want to show, that he has something cool, but it's absolute bullsh*t.

Btw., two times I faced situation, when my phone froze on that funny bootsplash, when I was using AK. Once while benchmarking, second time while opening gallery.

Sent from my GN
[Samsung Galaxy Nexus] boype:
You'll never see any bootsplash with fancy. Take my word for it. I've been offered boot logos before, but I kindly refused :>
[Samsung Galaxy Nexus] shawnaye:
Haha to think I just woke up! Well at least now you don't have to wait anymore!

Will report back!
[Samsung Galaxy Nexus] ChavitoArg:
Boype why did you make such a cool kernel? I love it :3 downloading the update.

Do you know some of the Nobodyatall aka nAa work? Can u take some stuff of his github?

Enviado desde mi Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] -Jesco-:
hope to see the changelog out :P and what do we have to look out for in the pre-40-2 ?
[Samsung Galaxy Nexus] paarthdesai:
anddd i am proud to say that i am a fancy kernel user :) :D

love you boype :)

^ps not in a gay way obvio :P
[Samsung Galaxy Nexus] boonz19:
Sounds awesome! Cheers!
[Samsung Galaxy Nexus] boype:
Release post on the previous page is updated now.
[Samsung Galaxy Nexus] -Jesco-:
a quick question , does ZRam really makes a difference ?
[Samsung Galaxy Nexus] daniil1410:
I am using Proximity Screen Off Pro with my flip cover case. I noticed that the system sometimes killes the app when I play games and it needs RAM. For example Asphalt 8. If I told you the process name, could you add it to the launcher whitelist? Or at least tell me how to do it manually?

EDIT: The process name is com.itsme4ucz.screenoffpro .
[Samsung Galaxy Nexus] 7175:
I think you can add it to the whitelist at the bottom of fancyinit2 in /sbin. Might need to change fancyinit permissions temporarily to edit the file.

Yeah, I think kernel support for adjustment of VUSIM and other available reg. voltages needs to be added. Otherwise I think they're hardcoded to idle and non-idle voltages. Maybe boype can add some more of the regulator voltages.. would be really cool. :D I feel like a lot of them were never really optimized enough by users since they're more complicated in some sense.

Some people reported hardware failure with vaux3_6030 at 2500. I think this might be from a difference in the GSM and Verizon AMOLED. If 2800 works that's great! I kind of have a feeling the GSM is more optimized at a higher vaux3 voltage than Verizon. I could never achieve GSM screen time until I lowered vaux3. 2500mV has been my optimum value for a while now. I do notice the screen will get maybe 5% brighter --with no other screen distortion-- but screen on battery life dramatically increases, so it's a win-win. Been running at 2500mV vaux3 for 6 months now.

Here's some useful info from ti.com on the twl6030 power management IC for the GNex's OMAP4460 board. The regulator voltages are controlled through the twl6030.
[Samsung Galaxy Nexus] daniil1410:
I tried that, but after reboot the file is unchanged. I am sure that I added the process name(leaving a space after the previous launcher).
[Samsung Galaxy Nexus] siealex:
Lowering Vaux3 significantly increases the screen brightness. Anyone confirms?

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] boype:
You notice it when you're multitasking. Apps that have been used before open a lot quicker (most of the times).

I have a similar experience
[Samsung Galaxy Nexus] -Jesco-:
just to confirm to switch off zram i do

#!/system/bin/sh
swapoff /dev/block/zram0
rm -rf /dev/block/zram0

or ..?
[Samsung Galaxy Nexus] sajty:
Which value you set? I didn't see any difference.

Sent from my GN
[Samsung Galaxy Nexus] siealex:
2700.

Sent from my paranoid fancy galaxy nexus

Some people on older devices (not only nexus) use /cache block as swap. Is it possible on Maguro? Or any other location in the internal memory.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] Sik-1:
Anything after 2500 for me changes the brightness, I'm on 2300 now an its stable so far I'm just playing with colors atm

---------- Post added at 07:37 AM ---------- Previous post was at 07:35 AM ----------

U don't have to remove it unless u don't want it starting on boot again, but swapoff should b enough to turn it of and when ur ready u can just swapon again
[Samsung Galaxy Nexus] siealex:
Are you sure that lowering Vaux3 really decreases consumption?

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] Sik-1:
I honestly do see a difference here's my setup : hope you guys can give some input on how things look an act on your devices
[Samsung Galaxy Nexus] boype:
To me it seems like this:

The brighter the ambient light, the bigger the effect. I have it set to 2800 at the moment and when I go outside, the display is way better readable.

When I'm inside and it is dark, however, I cannot see any effect.
[Samsung Galaxy Nexus] siealex:
Contrast -24???

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] Sik-1:
Yes with my voltage that low [MENTION=353015]240[/MENTION]0, the -24 contrast balances out the whites on my device an gives the colors more saturation, if not then all the colors are just washed out lol
[Samsung Galaxy Nexus] ChavitoArg:
i want to show the real difference in VAUX3 lowering voltage beyond 2500, take a look the screen becomes washed out :P (sorry for my bad english if u dont understand me)

at 2500 as in the picture:

and with 2495 applied you can already note the difference on the screen:

Just sharing :)
[Samsung Galaxy Nexus] siealex:
Vaux3 can be adjusted only in 100 mV steps. If you set 2495 it really sets 2400.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] chikimonke:
So what is the risk over adjusting Vaux3? Undervolting the CPU can cause instability issues, but seems it's overall harmless. What is the chance of permanent damage tweaking this value. Thanks.

Follow up question, what should one be looking for when doing the initial calibration, how does one know if a value is good or bad? Thanks again.
[Samsung Galaxy Nexus] stevensoaj:
2500 is the lowest I can go without major screen distortion. At 2400 everything is washed out. At 2300, everything is washed out more, but things have a purple hue to them. 2500 is running nicely though.

Also, what about VMMC? I have mine set to 1500 (1800 default) and I haven't noticed any negative side affects.

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

boype, as far as stability is concerned with the pre40 series, I can't really comment on a difference. They've all been extremely stable for me. It pre40-2 sure feels fast though!
[Samsung Galaxy Nexus] AvErNaN:
I really love this kernel. It's so smooth! Just a noob question... It's better to flash the kernel along with the ROM or first boot the ROM with its kernel and then flash the kernel?

Inviato dal mio Nexus 10 usando Tapatalk 4
[Samsung Galaxy Nexus] nitsua98:
I've been flashing it with the rom and have had no problems.
[Samsung Galaxy Nexus] itasoulas:
+1.. I clean flash rom, flash kernel, wipe cache and boot
[Samsung Galaxy Nexus] Pkt_Lnt:
Check the outstanding post above by [MENTION=5109059]7175[/MENTION] for VMMC! Appears to be for a removable multimedia card, which GNex does not have, but who knows what it might affect changing it, since /mnt/SDCARD is virtual drive.
[Samsung Galaxy Nexus] smallcaps:
Thanks you so much for the great work on this kernel. I am on r39 with PA3.99. Anyone experiencing forced closes with the fancy kernel updater? Thanks!
[Samsung Galaxy Nexus] DaNi_!:
No but I do experience that the update notifies me about an update, while I'm on the latest version.
[Samsung Galaxy Nexus] 1haumann1:
Same here

swyped from my maguro
[Samsung Galaxy Nexus] siealex:
A bug with gamma settings in trickster. When I set green offset less than 0 my screen becomes totally green. What's this?

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] Pkt_Lnt:
Been too long since I worked with init.d scripts. So we should turn off zram enable in Trickster or leave it on if we add this script?
[Samsung Galaxy Nexus] sajty:
I already heard about this. This is problem of some devices, you are just unlucky, it's not fault of kernel.

Sent from my GN
[Samsung Galaxy Nexus] nitsua98:
Pre40-2 is so. freaking. fast. I almost dropped my phone a couple of times because of all the butter it was oozing.
[Samsung Galaxy Nexus] boonz19:
Agreed! The boost in speed is really noticeable. For a while I was wondering if it was just me hallucinating...
[Samsung Galaxy Nexus] Astug:
Same question here. :) Can we simply enable ZRAM in Trickster, or do we have to enable/disable it AND add the init.d script?
[Samsung Galaxy Nexus] boype:
Trickster is enough
[Samsung Galaxy Nexus] Kewyang:
may i know where is the download link for 40-2? Tq
[Samsung Galaxy Nexus] Pkt_Lnt:
1 pg bk Yw
[Samsung Galaxy Nexus] siealex:
With 40.2 I still get swappiness zero unless I set it in System Tuner.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] Astug:
How can I check to see if it's working, after enabling ZRAM in trickster?
[Samsung Galaxy Nexus] siealex:
Type "free" in the terminal and check the last line.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] Astug:
Yeah, used is 0 here aswell after enabling ZRAM in Trickster.
[Samsung Galaxy Nexus] Charmacas:
Set it. Reboot. If set Trickster delay... Wait for it. Set it again in Trickster. Type "free" in the terminal. :)
[Samsung Galaxy Nexus] siealex:
The kernel sets swappiness to 0 before trickster enables zram.

Sent from my paranoid fancy galaxy nexus

---------- Post added at 10:01 PM ---------- Previous post was at 10:00 PM ----------

PS. Is it really necessary to set swappiness to zero?

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] boype:
There's something wrong with trickster then, I suppose.

I'm not quite sure if setting swappiness to 0 is necessary - but I always felt like battery drain is better with it on 0.
[Samsung Galaxy Nexus] siealex:
Most zram enabled kernels have swappiness hardcoded to 40% (regardless to zram state) and it does not affect battery at all.

PS. Android Tuner keeps the device awake approx. 2 min. per hour and eats much more battery.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] Fenvarien:
I use an init.d script to set swappiness to 40.

#!/system/bin/sh
# chmod -R 755 /system/etc/init.d
# 14-08-2013

# wait for android os
sleep 36;

# vm settings
echo 40 > /proc/sys/vm/swappiness;
[Samsung Galaxy Nexus] boype:
You could of course activate zram via the init.d method I described a few pages back... Then swappiness would never be set to 0 in the first place ;)
[Samsung Galaxy Nexus] 0vermind:
Not sure if anyone else is having this problem, but my available ram is always really low. Usually less than 90mb of free ram. At times I have 32mb available ram. It's to the point where random apps get closed and are restarted, or crash with Out of Memory errors. I don't have a lot of installed apps, this happens with only one running app. When the ram is low, it causes a lot of performance issues and lag. If I flash a different kernel, the problem goes away.
[Samsung Galaxy Nexus] siealex:
It would be much simpler to enable zram by default or to remove this silly swappiness behavior. No other kernel resets it to 0.

PS. What oom limits do you recommend? The default ones are too high.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] vojkan22:
It sounds that you have a memory leak and that's hardly a kernel thing. What rom are you using?
[Samsung Galaxy Nexus] stevensoaj:
Be careful how you ask for things. Remember, this is boype's kernel, not yours, or anyone else's in this thread. Be polite. Just because "no other kernel" does it that way, doesn't mean fancy kernel has to.

That said, I actually like how it's handled. Seems smart to set swappiness to 0 when zRAM is disabled to me. I use zRAM, and my swappiness is set just fine, without use of any init.d scripts.
[Samsung Galaxy Nexus] 0vermind:
Goes away when I switch kernels. Guess it could be rom and kernel conflict. I'm on SlimBean.
[Samsung Galaxy Nexus] siealex:
But on my phone it works only when zram is enabled via init.d or userinit.d. Trickster applies its settings only after media scanning which usually takes about one minute after boot.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] vlasis_myr:
I have very big battery consumption when screen is on...with stock settings, in android 4.2.2 I used to have 1% for 5 or 6 minutes...now with the same settings every 2 minutes I have drop...

Στάλθηκε από το Galaxy Nexus μου
[Samsung Galaxy Nexus] vojkan22:
haha I knew it. I had the same problem with slim + fancy. When I check RAM usage in ROM toolbox pro's app manager, Android System was at 106 MB :eek: and SystemUI around 70MB. On Cataclysm + Fancy or Purity + Fancy combos this does not happen. Currently on purity + fancy and Android System is 66MB and SystemUI is 48MB after 20+ hours of uptime. But interesting thing is, that you do not have that problem with another kernel. With which one, if you don't mind me asking?

Correct me if I didn't interpret this screenshot the right way, but if this is drain from 18%-5% this is "normal" for gnex. Last ~30-35% goes away at insane rate.
[Samsung Galaxy Nexus] siealex:
I ask only for one thing: zram must work without any additional manipulations.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] vlasis_myr:
Check these 2 screenshots believe from 4 hours screen on time I have drop to 2 and a half...

Στάλθηκε από το Galaxy Nexus μου
[Samsung Galaxy Nexus] AbhishekS:
This means zRam is enabled for me, right?
[Samsung Galaxy Nexus] Fenvarien:
Just use the script boype posted or set swappiness via init.d like I suggested some posts ago.

And if you ask for extra features or something else try to be polite. :good: :)
[Samsung Galaxy Nexus] boype:
Try this (headline: 'Do you want to disable the whitelist?'): http://xdaforums.com/showpost.php?p=42537078&postcount=2341

I'd leave OOM as it is. In 4.3, the default minfree values are around 50% higher than they were in 4.2. However, free RAM is approximately the same.

I used to have custom minfree values in the kernel's ramdisk, resulting in almost no free RAM when using the values from 4.2 in 4.3.

What vojkan said. Did you let the phone settle for several charges after flashing fancy?

Yes.
[Samsung Galaxy Nexus] jackyhk02:
Will the battery consumption be higher if I enable zram?
[Samsung Galaxy Nexus] ChavitoArg:
Maybe, since it uses some resources. But nothing to worry about (:

Enviado desde mi Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] Charmacas:
pre40-2 with ZRAM runs great. I got no SOD and multitasking is much better now. But here and there I get some hiccups which were not there without ZRAM. Am I the only one? :)
[Samsung Galaxy Nexus] -Jesco-:
you arent the only one :)
[Samsung Galaxy Nexus] sajty:
Good question,but still some objective measure is missing.
[Samsung Galaxy Nexus] Charmacas:
Jesco aren't you the developer of Golden kernel? Don't you use your own kernel? :)
[Samsung Galaxy Nexus] -Jesco-:
thats Jeeko :P we have similar names ahha , im the maintainer for AOSPAL and PAC :P
[Samsung Galaxy Nexus] SuperSalvo:
Great will try that! Thx!

Are you setting your display brightness on auto? It is so dark i almost see anything :confused:
[Samsung Galaxy Nexus] sajty:
Correction,

- UV for VAUX3_6030: 2800

- UV for VMMC: 1600

Yes,i have auto brightness.But 95% of time i use my phone inside building,so i have not problem with brightness at all.
[Samsung Galaxy Nexus] vlasis_myr:
of course...these results are after 4 cycles...now im back to stock and i have 5minutes with 1% from the first cycle...what is yours battery consumption?
[Samsung Galaxy Nexus] boype:
Update: It turns out the few hundred lines of code were all written for nothing. For achieving scheduled trim I tried implementing kernel timers. Their timekeeping are based on system ticks and it appears there are no ticks when the phone is in deep sleep. So that wont work...

Anyway, modified the /cache trim routine a bit. Trimming will not happen every single time you switch off the screen, but only when the device has been awake for more than 15 minutes since the last trim.
[Samsung Galaxy Nexus] SaskFellow:
That sounds, like a much more effective means, probably cuts down on the lines of code too.

Might just have to sit out R9... Oh but I do so want that new keychain build... Oooh... hard choices! :crying:
[Samsung Galaxy Nexus] gwindlord:
boype, it is possible to make a scheduler on dalvik API application level, but is it possible on native app level as well?.. I've checked - there is no at and cron there, not sure how it could be done without VM.
[Samsung Galaxy Nexus] boype:
Actually I have tried cron on our phone. In principal it works, but then again, it does not work when the phone sleeps. I think the whole idea should be dropped, since it is too much hassle trying to get something working when one might as well manually trim every once in a while.
[Samsung Galaxy Nexus] gwindlord:
OK... Testing fstrim script automatic scheduled start via ScriptManager then.
[Samsung Galaxy Nexus] jjhrrsn:
Re: [KERNEL][4.2.x] Fancy Kernel (r9) (MAR-04-2013)

I personally think manual trim is where its at. Automated isn't my cup if tea when its easy enough to do once and a while. But that's just my .05$
[Samsung Galaxy Nexus] boype:
You won't have to wait too long. when Linux 3.0.69 is out, I'll make a new build. maybe it'll be available on Monday.
[Samsung Galaxy Nexus] Az Biker:
Re: [KERNEL][4.2.x] Fancy Kernel (r9) (MAR-04-2013)

Nvm: :eek:
[Samsung Galaxy Nexus] jjhrrsn:
Re: [KERNEL][4.2.x] Fancy Kernel (r9) (MAR-04-2013)

I seriously love this kernel. Was a huge Trinity fan, which this reminds me of most and tried every kernel from lean to ak to Franco. This is truly great, thank you.
[Samsung Galaxy Nexus] un.droid:
boype thanks for the work. i want to try this kernel but read that people who came from AK got into bootloops. how does these kernels differ and do i have to run the scripts anarkia mentioned in the op?
[Samsung Galaxy Nexus] okanb3:
I just stuck at boot animation.. Any ideas?

I'm using Atom V9, and i was using Ak Cylon 728.