yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] splus:
If you check any benchmarks or games you'll see that article is not correct.

The power consumption difference between 307, 384 and 512 MHz for GPU is very small, and tested by many users.

And the difference in FPS between those frequencies is also greater than what the article says. Have a look at those Nenamark2 results and do the math:

Yay!!! :good: :D
[Samsung Galaxy Nexus] zoomy942:
Guess I misunderstood it as 307 is what all GPU would use as if stuck there.
[Samsung Galaxy Nexus] :
Glad the lower 3D performance I noticed was a bug c: was liking the kernel but switched back to Franco because of it. Hoping for new release soon
[Samsung Galaxy Nexus] parthipanramesh:
Great work boype!!! Everything is working great!

PS: Check your pm ;)
[Samsung Galaxy Nexus] billouetaudrey:
Hi, sometime I have fast reboot (reboot without ask pin code but lost apn, need hard reboot for refind apn) stock settings, I don't know if it's the rom or the kernel ? Fancy r31,Dirty rom, any suggestion ? Thx

Envoyé depuis mon Galaxy Nexus en utilisant Tapatalk 4 Beta
[Samsung Galaxy Nexus] stevensoaj:
Count me in as well! Can't wait. :D

Edit: ugh... You had to announce all the great work you're doing for the next version. I'm finding myself refreshing the thread constantly, hoping the new version is out. :p Don't give me an ETA though! I like surprises.
[Samsung Galaxy Nexus] Jaine:
Hey,

I was one of many people, whose wifi and data-sync connection completely died on 4.2.2 when screen was turned off. Since I noticed the DTIM skip override in the OP and tried it out, the problem is gone. It might drain a little more battery, but I still have no problem getting through the day and I receive my messages again :D

So thank you very much sir, for this exceptional kernel.
[Samsung Galaxy Nexus] im the doctor:
O M G

This kernel is fantastic, longest battery life ever

with other kernel i've got 3 hours of screen but battery went down in few hours..

AWSOME thx for your work :good:
[Samsung Galaxy Nexus] MartianCeo:
This kernel just works. Something I noticed which posses a question for me. When setting custom voltages and leaving SR on. I noticed that SR will respect the voltage you set and if it goes to the next step, it uses the set custom or default voltage for that step. For example 192mhz is set at 800v for me. When the CPU steps up to 384 it goes to 820v. In the past SR would disrupt what you set and end up going higher anyway. What changed?
[Samsung Galaxy Nexus] n2rjt:
After reading about the GPU governor issue, I switched to performance governor 512MHz. Smoother, still good battery life. I looked at the code but the bug isn't obvious to me. I'd suggest Boype to keeping governor selection in place but default to performance 512. First, get true 512 to work, then maybe experiment with on demand.

I'm tempted to compile this and start debugging it. I haven't done kernel work since I had my HTC kaiser!

Again thanks boype for an excellent kernel.
[Samsung Galaxy Nexus] boype:
I fixed it some time ago:

https://github.com/boype/kernel_tuna_jb42/commit/f455fed66d59afdda9f529e42903ea4a6e731cf6

:)
[Samsung Galaxy Nexus] sajty:
I believe,that 384MHz is absolutely enough.Even exacting games run well on 384MHz,512MHz is battery killer,mainly in performance mod.
[Samsung Galaxy Nexus] n2rjt:
Agreed! But today, 512 doesn't even work from what I read, so selecting 512 really selects 384. The default in the kernel should be the configuration that truly gives you 384 MHz.
[Samsung Galaxy Nexus] sajty:
Got it now.If 512 is 384 ATM,then yes,512 is the best choice :).boype wrote,that he already fixed this (governor will be probably removed,but it really doesnt matter for me).We must wait for new version.
[Samsung Galaxy Nexus] MartianCeo:
Oh ok :) even tho that's gibberish to me lol. I just like the fix :)
[Samsung Galaxy Nexus] boype:
512 works just fine and also improves graphic performance a lot. I'll go for standard 384 though. As I said, users can easily change the GPU frequencies themselves.
[Samsung Galaxy Nexus] zoomy942:
I'll agree. 384.
[Samsung Galaxy Nexus] Lancez:
sounds like r32 is in the pipe :p
[Samsung Galaxy Nexus] Charmacas:
Hope so! ;)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] boype:
Perhaps :p
[Samsung Galaxy Nexus] Lancez:
i was right :victory:
[Samsung Galaxy Nexus] aHecticLife:
Now you're just teasing us lol, can't wait D:
[Samsung Galaxy Nexus] Doublewise:
I'm using 360 launcher but I could not find its process name from terminal ps -p. Only found one I suspect android.process.acore

Boype or anyone could you check it... I want to put it in white list. Thanks.
[Samsung Galaxy Nexus] DoesntPostAThing:
I'm in the same boat, just got my GNex almost a year ago, but no money to upgrade for another year probably. Good to know that such a good kernel will continue to be developed for this device!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zoomy942:
Being the antsy user I am

What ya looking at to change in r32?
[Samsung Galaxy Nexus] boype:
r32 up

Hi all,

r32 is now available. Here's the change log:

updated to Linux 3.0.83

enable trim_override to allow >= 1.4Ghz frequencies without lagging the device (credits to francisofranco)

removed simple GPU governor (it wasn't working as it should. You can still pick from 307, 384 and 512 MHz like you can on other kernels)

several mostly power management related fixes and also a cache tweak from Texas Instruments

SIOplus/deadline: Allow 0ms deadline latency

implement temperature control (extended version only; credits to imoseyon)

WiFi drop workaround improvement (no need to disable / enable WiFi manually anymore)

switched compiler toolchain to Linaro Android GCC 4.7 (current version: 13.05)

few other things

As you can see, I switched the toolchain. While I said earlier that Google's toolchain is supposed to be very stable, Linaro's should be equally stable. Plus it gives builds with better performance (e.g. in some 3D applications) and is updated more frequently.

Enjoy and best regards!
[Samsung Galaxy Nexus] DoesntPostAThing:
Awesome! Flashing now :)

Also wondering what kernel settings you guys use for good performance? (With still good battery life, but mainly performance-oriented)
[Samsung Galaxy Nexus] splus:
I got my Gnex a year and half ago. I have money for N4 but I never considered N4 a good enough upgrade for me to buy it. Same size screen but little better, identical software as Gnex and again a mediocre camera with few more megapixels. Not even to mention the glass back. It just has a faster processor with more RAM which makes it smoother. If my Gnex was a laggy slouch then OK, but hell, it's smoother than some other newest smartphones!

If you don't have a phone then yes, N4 is a great value for money phone because it's cheap and it's a Nexus.

But I'll wait for N5 and some serious jump in specs...
[Samsung Galaxy Nexus] gwindlord:
All default, except governor (interactive), adaptive backlight and wifi performance gives me nice correlation.
[Samsung Galaxy Nexus] aHecticLife:
Just woke up and seeing a new update is the best feeling EVER!
[Samsung Galaxy Nexus] wtr_dhd:
On R31 since some days and this is the best combination I ever used in combination with CM 10.1.. AK was very fast but gave me crashes.. This kernel is the most stable and buttery smooth and no reboots/crashes at all so far..

Going to install R32 now, thanks for your good work boype!
[Samsung Galaxy Nexus] aikons:
std and ext version, which is better? Thx. :p
[Samsung Galaxy Nexus] Starsream88:
Give ext a try, its working great for me ;)
[Samsung Galaxy Nexus] Godra:
Ext has voltage, fsync and sound control options amd std doesn't
[Samsung Galaxy Nexus] Rufufu:
I want to report that the commit allowing OC to 1.4GHz withoug lag works very well!

I have one of the gnex which wasn't able to handle 1.4GHz with previous fancy version, and now I can OC without issues.

Thanks Boype!
[Samsung Galaxy Nexus] un.droid:
r32 is very responsive with bigbros v8. indeed this kernel keeps getting better, thanks boype.
[Samsung Galaxy Nexus] Blackcrx:
R32 is running awesome right now. Very smooth.

I noticed that a couple kernels have interactive patches. I was wondering if you will apply these also. Thanks.
[Samsung Galaxy Nexus] sajty:
I would like to know that too.boype,are you merging latest interactive patches?I prefer interactive governor over ondemandplus,so good to know that information.
[Samsung Galaxy Nexus] kaluoshi:
Thanks

Hi [MENTION=4615478]boype[/MENTION] i tried your kernel for the first time and i'm really impressed by the standard one of latest version (it follow my philosophy too :D ). Keep up the good work man :fingers-crossed: Cheers
[Samsung Galaxy Nexus] cuboc:
I'm trying for this script to work without the need for other progrmas in stock rom 4.2.2, but does nothing. There something wrong?
[Samsung Galaxy Nexus] 7175:
Awesome man! Really excited about the switch to linaro toolchain! This has made my day, thanks boype. Nice concise post on DTIM skip override. I'm curious if there's a time component that goes along with the request skipping.

Maybe try running script from sbin, ie, #!/sbin/sh. I think this should work since fancy has initd enabled from busybox /sbin location.

Edit - Just noticed boypes reply and gracefully checked /sbin in Solid Explorer, then effortlessly flipped to the other panel in /system/bin [/advertisement]. Yeah I stand corrected it runs through busybox in /sbin/bb/
[Samsung Galaxy Nexus] boype:
Stock ROM doesn't have busybox, which is needed to execute the commands. But lucky you: Fancy kernel has is as well.

Change your script to this and you'll be fine:

#!system/bin/sh

bb=/sbin/busybox

$bb echo "1" > /sys/class/backlight/s6e8aa0/acl_set
$bb echo "1" > /sys/class/misc/soundcontrol/highperf_enabled
$bb echo "2" > /sys/class/misc/soundcontrol/volume_boost
$bb echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
$bb echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
[Samsung Galaxy Nexus] DroidOnRoids:
Does the fixwifi script do something else to fix Wifi drops other than going to wifi settings and disabling Avoid Poor Connections and Wifi Optimization?
[Samsung Galaxy Nexus] jjhrrsn:
When downloading anything large over WiFi like a ROM or torrent (music CD) my phone is almost not possible to use. I'm on cm nightlies which could have something to do with it but was wondering if anyone else can reproduce
[Samsung Galaxy Nexus] cuboc:
I tested this way. but there are some things that have not changed!

$ BB echo "1"> / sys / class / misc / soundcontrol / highperf_enabled

$ bb echo "0"> / sys/devices/system/cpu/cpu0/cpufreq/gpu_oc

$ BB echo "1"> / sys/class/backlight/s6e8aa0/acl_set

not for at these 3 script

How do I automatically change the script each reboot.
[Samsung Galaxy Nexus] kinfolk248:
what do you mean by not possible to use exactly?
[Samsung Galaxy Nexus] jjhrrsn:
Its like everything is being used by the download process. Cant use any apps, the app drawer, takes 5-10 seconds to wake
[Samsung Galaxy Nexus] MartianCeo:
It must be your settings. That's always half the problem. Using the default may not be right for your phone. I have it set up so my phone only lags just a little when installing apps. Everything runs as smooth as butter most of the time. I'm on PAC, so that's saying something. Its undervolted(the core, and iva voltages are lowered) and everything running at 1.2g for max and 192mhz for min.
[Samsung Galaxy Nexus] paarthdesai:
rom problem

i don't have any problem on carbon...

just downloaded 300mb of mobile right now.. and here we have slow connection soo it took 2hrs to download..

i was able to play with my phone normally,

also developer kudos to you.. such a wonderful job you have done with this kernel i fail to express..

minion rush was lagging with ak kernel and with ur rom the game is awsme as fcuk ;)

sent from my sexy Nexy ;)
[Samsung Galaxy Nexus] namtombout:
Can you post your core and iva voltages?

U.O.E.N.O
[Samsung Galaxy Nexus] MartianCeo:
Its -50 across the board.
[Samsung Galaxy Nexus] sajty:
I tested lower voltages for 14 days and i found those absolutely stable:

192MHz: 775mV

384MHz: 820mV

537MHz: 875mV

729MHz: 940mV

1036MHz: 1095mV

1228MHz: 1200mV

1420 MHz: 1255mV

I believe,that all steps are able to go even lower,but i dont want to risk freezes because of 25mV lower voltage...
[Samsung Galaxy Nexus] MartianCeo:
Awesome. I tried to go that low but my phone couldn't quite handle it yet. I need to keep working on it until I can. Every phone is different so some will work and some won't. Thank you for the insight.
[Samsung Galaxy Nexus] boype:
Yes, it does none of the things you mentioned. It ejects the WiFi module and re-inserts it.

If what you posted is exactly what is in you script, it cannot be working. Linux in general is case sensitive and there are also spaces where there should not be any. Check again what I posted on the previous page and copy-paste it to your init.d script.

[EDIT]

I spotted another mistake in the script. There's a missing slash in the first line. This is how it should be working fine:

#!/system/bin/sh

bb=/sbin/busybox

$bb echo "1" > /sys/class/backlight/s6e8aa0/acl_set
$bb echo "1" > /sys/class/misc/soundcontrol/highperf_enabled
$bb echo "2" > /sys/class/misc/soundcontrol/volume_boost
$bb echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
$bb echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
[Samsung Galaxy Nexus] mpokwsths:
Man, I believe your are much higher than 25mV.

My setup (tested for months):

192MHz: 730mV

384MHz: 780mV

537MHz: 845mV

729MHz: 930mV

1036MHz: 1060mV

1228MHz: 1125mV

1420 MHz: 1210mV

Look at hi freqs, where voltage does play a critical role in consumption . And keep in mind that these are not the absolutely lower I can go. I took a 10-15 mV safety margin...
[Samsung Galaxy Nexus] Charmacas:
Why do you guys use custom voltages?

SmartReflex does always use the lowest possible voltage available. And I read it does a great job.
[Samsung Galaxy Nexus] shawnaye:
Because life is an experiment for us waiting to fail.

Haha.

You can try using custom voltages, if you get better battery life. No harm no foul!

But only the people who are capable of undervolting should ever touch it.
[Samsung Galaxy Nexus] mpokwsths:
SmartReflex

does not use

the lowest possible voltage. It actually uses pretty high voltage.

Undervoltage has 2 benefits. Lower consumption (especially in high freqs) and lower temperature. Lower temps mean less throttling (especially if overclocked), thus better overall operation...
[Samsung Galaxy Nexus] Syfer_Fever:
there are always upside and downside

but if you wanna to try Undervolt, you have to be patient
[Samsung Galaxy Nexus] im the doctor:
Sorry guys, numb question

i'm on r31 (extended version), i don't have wifi or data connection right now, so i can't use use terminal to update.

can i download and flash r32 on r31 ?
[Samsung Galaxy Nexus] Seraz007:
ofc

just wipe cache and dalvic after flash ;) :D:D
[Samsung Galaxy Nexus] agritux:
i feel google version was better than linaro version :( gaming performance reduced with r32. Web scroling too. i feel lags. :(
[Samsung Galaxy Nexus] sajty:
I tried even lower voltages,but i had one freeze when phone was in high load.So i dont wonna risk again :).

---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------

Exactly!
[Samsung Galaxy Nexus] im the doctor:
someone else is having this problem ?

r31 works good for me, not sure if flash new version or keep this :\
[Samsung Galaxy Nexus] Riekr:
No, r32 seems better to me but starting from r31 I switched to bfq from sioplus since it seems better at power consumption. Need testing tough.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] agritux:
i am always using stock kernel settings. Not change anything. i made clean install. Full format full wipe. Because i tried this fridays miui. But i feel lags. Using latest cm nightly. R31 was fine for me. i dont know why :(
[Samsung Galaxy Nexus] Charmacas:
I know how to undervolt. I thought boype did some tuning to SmartReflex which made it as good as finding out all the lowest voltages. Because every hardware inside phones handles voltages different I think this algorithm is very nice.

I would like to hear what [MENTION=4615478]boype[/MENTION] think about this topic!?

[MENTION=4589777]agritux[/MENTION] don't feel alone. I have the same feeling. But it could also come from another changes boype did. Anyway it's always good to report things so the he sees there might be something 'wrong' and can have a look into it. I am sure boype noticed it himself if it's really there and is already working on 'fixing' this. :good:

-- EDIT --

I am back to r31. And it's back to speed again. ;)
[Samsung Galaxy Nexus] boype:
Knowledge base: tuned LPDDR RAM timings

Hi,

I have optimized the device's LPDDR RAM timings. I was able to increase the throughput by ~10 %, in my opinion a fairly good improvement for the fact that no overclocking is happening. Here are benchmarks (performed with RgBandwidth RAM misc benchmark; threads: 1. 20 benchmark instances each, best result wins):

Stock Tweaked

Copy 1249.9 MB/s -> 1373.0 MB/s --> 9.86 % improvement
Scale 1084.8 MB/s -> 1188.1 MB/s --> 9.52 % improvement
Add 938.4 MB/s -> 1050.2 MB/s --> 11.91 % improvement
Triad 923.0 MB/s -> 1043.5 MB/s --> 13.06 % improvement

The settings have been tesed over a longer period of time and seem to be absolutely stable. Also, there's no heat problems or increased battery drain that came to my attention.

So what have I changed? People who have tweaked their computer's RAM timings might find some of the variables familiar. I changed the RAM timings from

tCL = 6
tRPab = 21
tRCD = 18
tWR = 15
tRAS = 42

to

tCL = 5
tRPab = 14
tRCD = 14
tWR = 10
tRAS = 30

For more information on RAM timings, read this Wikipedia article.

Best regards
[Samsung Galaxy Nexus] boype:
Are you willing to help finding out what the problem is? For me, everything is fine, that's why I need someone to test. I have two things in mind that could cause the issues.
[Samsung Galaxy Nexus] Charmacas:
I would like to help because I also got this problem as described above. :)
[Samsung Galaxy Nexus] angourakis:
r31 version was lagging a lot for me, mainly because I use 1400Mhz slot. r32 there are no lags at all!

RAB: 512

Sched: sioplus

Max: 1400Mhz

Gov: ondemandplus

Wifi HP: On

Fsync: Off

GPU: 512Mhz

Zram: Enable

Gonna test the new version with improved memo \o/

Best Regards
[Samsung Galaxy Nexus] sajty:
Switch to interactive governor and you have ultimate battery killer! :D
[Samsung Galaxy Nexus] angourakis:
Not true my friend. I've decreased the voltages a bit so I can't really see the battery going fast (actually yesterday I was even asking myself if there was some problem with it because it got stucked at 72% for an hour +/-)

Anyway, I do prefer to recharge twice a day than not use the full potencial of the phone.

boype, I was thinking about KSM: http://en.wikipedia.org/wiki/Kernel_SamePage_Merging_(KSM)

Do you think it improves performance? I can't see any conclusion about the subject (at least in Android world)
[Samsung Galaxy Nexus] gwindlord:
I do not feel lags - at least yet, synthetic tests are ok too, maybe the reason is interactive governor, which is IMHO smoother. With my fair usage I have battery life 2-3 days, which is generally normal for this kernel and not bad at all :) So any bad feelings could be a matter of settings.

Also long time ago (but still on Android 4 :) ) I've tried to test KSM feature on a couple of kernels and visually seen no difference, synthetic shown little decreasing of performance, so I turned it off and forgot about it forever :)
[Samsung Galaxy Nexus] mpokwsths:
[MENTION=4615478]boype[/MENTION]

Nice idea about mem timings...

What is the mem score in Quadrant with the tweaked timings?
[Samsung Galaxy Nexus] quickstang:
Tested these & got a reboot a minute ago while browsing on here. Testing the test release now but with stock voltages.

Unfortunately my phone doesn't like those voltage settings.
[Samsung Galaxy Nexus] boype:
I don't know, why don't you try it? I expect around 10% better scores, as the benchmark indicates...
[Samsung Galaxy Nexus] sajty:
In my opinion,high frequencies are too much undervolted.Try to raise voltages for 1036 and 1228 (1125MHz is very low number) step.
[Samsung Galaxy Nexus] mpokwsths:
Not all chips are created equal. If the crash occurs after some time (and not immediately) it usually means that you are close. I would add 10mV to the high voltages and try again.
[Samsung Galaxy Nexus] sajty:
I am now testing those:

192MHz: 775mV

384MHz: 795mV (lowered by another 25mV in comparison with last posted by me)

537MHz: 875mV

729MHz: 940mV

1036MHz: 1095mV

1228MHz: 1175mV (lowered by another 25mV in comparison with last posted by me)

1420 MHz: 1255mV

Benchmarks OK,no freeze.
[Samsung Galaxy Nexus] Starsream88:
Running the last test version, working good so far, smooth and fast. Apps open little bit faster. I'll continue testing and report back later.

Some benchies :
[Samsung Galaxy Nexus] sajty:
interactive + bfq,min 384,max 1420,hi_speed_freq 729,RAB 512,GPU 384
[Samsung Galaxy Nexus] stevensoaj:
Just wanted to report r32 is working great for me. And it seems to have smoother performance over r31 (I'm contributing this to linaro and 512MHz GPU). Now I'm going to give the test version a shot. Battery life is also exceptional on r32 BTW. Great job boype. :thumbup:
[Samsung Galaxy Nexus] Starsream88:
Oc to 1420, normal score :cyclops: !
[Samsung Galaxy Nexus] mpokwsths:
Tried r32-test with the improved mem timings. Everything OK here. It feels slightly faster. Quadrant scored over 1950 for mem (1228mhz). Also tried Nenamark 2 with 512mhz GPU. The score is improved to 39.2fps (38.7 before) as the mem timings affect the GPU also. Nicely done Boype!
[Samsung Galaxy Nexus] zoomy942:
But gpu is 384 right?
[Samsung Galaxy Nexus] Blackcrx:
[MENTION=4615478]boype[/MENTION]

I asked this question before also regarding the interactive patches. Any chance these were included or might be included in the next test or official release?
[Samsung Galaxy Nexus] mpokwsths:
No, GPU speed is selectable from Trickster. Either 307,384 or 512Mhz.

The 39.2 score was with 512 GPU.
[Samsung Galaxy Nexus] creeve4:
The highest I get with 512 MHz is 32 fps in Nenamark2. :(

With r32
[Samsung Galaxy Nexus] mpokwsths:
With previous Fancy kernel versions you mean. Where the GPU governor thing wasn't working well and the GPU speed kept fluctuating irrationally. As of r32, GPU speed is fixed to whatever you choose and the performance is what should have always been. For Nenamark 2 it is: 384: ~33, 512: 38.7. And now it is even better with the improved timings!
[Samsung Galaxy Nexus] creeve4:
No, I mean r32. I'm only getting 32fps when the GPU is set to 512 MHz and 27fps with 384 MHz
[Samsung Galaxy Nexus] mpokwsths:
This is not right. With every kernel at 384 you should score 33 and at 512 38+. 28.7 if I remember correct is the score with stock clock of 307.
[Samsung Galaxy Nexus] gwindlord:
I have 39 dead in Epic Citadel and GPU 384 - maybe they have different FPS :)
[Samsung Galaxy Nexus] splus:
I haven't done any benchmarks except Nenamark2, and with r32 test 1 I get now around 38 fps, whereas in r32 I had 37.2.

Everything also feels smoother.

This RAM tweak definitely works.

Great work boype! :thumbup:
[Samsung Galaxy Nexus] creeve4:
Any idea why? I'm running a self compiled AOKP ROM with r32 at stock settings except for GPU overclock.

307 MHz: 24 fps

384 MHz: 27 fps

512 MHz: 32 fps
[Samsung Galaxy Nexus] boype:
I have it on my to-do-list :cyclops:

I'd rather not have it... I'm worried this might wake up the CPU more often to check if it can merge pages.

I'm only familiar with building CM from source and don't know if AOKP uses the same build script and stuff... But do you (knowingly) have any options to set compiler flags? You should definitly have armv7 and neon optimizations enabled...
[Samsung Galaxy Nexus] creeve4:
I am not sure, where would the options likely be to set such flags?