yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rogersnm:
Sorry I thought you had bootloops when you said "had some serious reboot issues. It rebooted several times". If it rebooted well after the boot cycle then the init.d scripts wouldn't have helped.

---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------

Append to /etc/init.d/98tweaks (or 90tweaks if that's what it's called... or any init.d script):

echo "level1 level2 level3 level4 level5 level6 level7 level8" > /sys/devices/virtual/misc/customvoltage/mpu_voltages
echo "level1 level2 level3 level4" > /sys/devices/virtual/misc/customvoltage/iva_voltages
echo "level1 level2 level3" > /sys/devices/virtual/misc/customvoltage/core_voltages

Replace "level*" with the appropriate voltage, just an integer, no units. The first voltage corresponds to the highest frequency, so level1 corresponds to the voltage for 1536 MHz.
[Samsung Galaxy Nexus] Theshawty:
Oh yeah, it cures cancer and aids too ^^
[Samsung Galaxy Nexus] jhondidfool:
I bet it's like that, but my last phone was a buzz which could not be unlocked. -i know the names of things and their meaning, but not the procedure to do it, I haven't been clarified with the several tutorials for similar things I've looked into, so I ask again here.
[Samsung Galaxy Nexus] Crackking:
I have a question to the updater app:

Whats the "singel core mode"?

Does it shut down one core for power saving and when its needed switch back on?
[Samsung Galaxy Nexus] Lochman79:
Nexus Noob question. Is this kernel fully compatible with the MIUI ROM? I searched the OP, but didn't see anything.

Thanks!
[Samsung Galaxy Nexus] rogersnm:
I wasn't being obtuse, that is how to do it.
[Samsung Galaxy Nexus] Gahh Its Lee:
Pretty sure it just shuts down one core and it acts like a single core phone.

Ive seen a lot of people saying it works wonderfully so I'd assume yes I've never seen a complaint.

You were being quite acute actually <... I had to
[Samsung Galaxy Nexus] diesel2k:
What is the default governor on milestone 4?

Sendt fra min Galaxy Nexus med Tapatalk2
[Samsung Galaxy Nexus] Crackking:
I think ondemand.

@Gahh Its Lee:

Thanks :)
[Samsung Galaxy Nexus] rogersnm:
Yep it's ondemand.

From config.gz:

CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
[Samsung Galaxy Nexus] Gahh Its Lee:
Not a problem. And yea on demand is a great gov choice IMO.
[Samsung Galaxy Nexus] theMaDHakkeR:
Franco!

#185 has got to be the smoothest kerned release yet! Furthermore i had some issues with HW MKV playback on 181, and its now solved in 185! Everything is screaming at @1536Mhz w/ 512Mhz GPU! Not only that but with some minimal use (Left the phone at home 1 day) i got 3 days out of the damn thing with #181!! Just amazing work Franco!

Thank you!
[Samsung Galaxy Nexus] leets4uc3:
Just tried b38 linaro with 47. It was terribly slow with lean kernel. Went back to B38 with r 185 and it is phenomenal. Zero issues. Fast as **** and great battery life.

Question. I have my min freq and screen off freq set to 384. (Wheately gov) when I play music with the screen off, does the frequency stay at 384 or the more favorable Max freq like Normal wheatley?
[Samsung Galaxy Nexus] rogersnm:
Grab CPU Spy off of the play store and find out :p
[Samsung Galaxy Nexus] metalspring:
Anyone who wants white whites should try out these settings I found

Color multipliers

Red 200

Green 200

Blue 265

Gamma

Red -6

Green 0

Blue 8

Omap4 1.2

They look pretty good to me :D
[Samsung Galaxy Nexus] rogersnm:
For those of you who want to try it, here is r185 built with the latest linaro toolchain: http://hoxroms.serveftp.com/franco.Kernel-linaro-r185.zip

Copy to your phone and flash via CWM as normal.
[Samsung Galaxy Nexus] irizwan:
Hey thanks for sharing but can you please attach it here? because that site is blocked in KSA

thanks =]
[Samsung Galaxy Nexus] rogersnm:
Sure, it's attached to this post :)
[Samsung Galaxy Nexus] metalspring:
Notice a difference?
[Samsung Galaxy Nexus] rogersnm:
I only just started using but there's no immediately noticeable difference.
[Samsung Galaxy Nexus] metalspring:
I notice one already...normally on quadrant I need to disable smart reflex for the core and up the top voltage from 1050 to 1060 to get rid of small graphics glitches on the second graphics test but with the linaro build it works just fine at 1050

Anyone else want to test lower voltages than stock 185 to see if linaro makes a difference?
[Samsung Galaxy Nexus] rogersnm:
I agree the GPU tests seem to be a bit slicker although the actual benchmark result at the end is the same, I can't comment on the voltage as mine ran fine before @ 850 mV. The notification tray does seem to slide down a bit more smoothly for me.
[Samsung Galaxy Nexus] Puzzlegirl:
Did you ask for Franco's permission first? Or not?
[Samsung Galaxy Nexus] yyz71:
Just flashed linaro 185 damn :) never got scores like this..

Using PROVISION Rom..
[Samsung Galaxy Nexus] SupWiz17:
Is this with 512mhz gpu or 384mhz gpu?
[Samsung Galaxy Nexus] metalspring:
Good point :eek:

I always use the 512 gpu one
[Samsung Galaxy Nexus] yyz71:
Is there a 512 gpu? My phone could:) handle it Would love if you could compile one:D
[Samsung Galaxy Nexus] Meannekes:
Its 384

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] arshad14:
Has anyone noticed with the 185 update, wifi hot spot doesn't work?
[Samsung Galaxy Nexus] kolyan:
I have the same issue..... :(
[Samsung Galaxy Nexus] Meannekes:
With your linaro toolchain Version my mV for 1228 & 1344 MHz are 30 mV lower!

SR on..

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] leets4uc3:
Definitely stays in Max state. Might have to switch to ondeamand
[Samsung Galaxy Nexus] leets4uc3:
Pretty good! Ima keep it for a while. I only changed blue gamma from 8 to 4. The grey was a little blue.
[Samsung Galaxy Nexus] yyz71:
Man sweet quadrant scores
[Samsung Galaxy Nexus] leelaa:
Look i know some people dont agree wiyh benchmark scores BUT..i installed the linaro build that the user uploaded and these are the best results ive ever had. And i allways use 512 gpu. And this one is 384.
[Samsung Galaxy Nexus] yyz71:
Same here :) This thing kicks ass :D
[Samsung Galaxy Nexus] metalspring:
Can you make a 512 gpu one? You can pm me it if Franco doesn't like it being posted here
[Samsung Galaxy Nexus] iGoogleNexus:
I'm in love =]

- Google
[Samsung Galaxy Nexus] Antob125:
Well Franco wanted proof if there was a difference using the toolchain and I know quadrant isn't enough for him to change his mind. Is there any other numbers you guys can provide to convince Franco to add the toolchain. Cause if not I don't think he'll be convinced.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] leelaa:
If i new any other way to prove i would. But its not just quadrant, the phone feels smoother, now iam waiting for gummy to release the nightly with linaro 4.7 and i shall combine the 2 beast's :D
[Samsung Galaxy Nexus] iGoogleNexus:
O.o on it

- Google
[Samsung Galaxy Nexus] jdec529:
I should give this a try, I tried another linaro kernel, but had opposite results that u guys r having.
[Samsung Galaxy Nexus] iGoogleNexus:
Its Francos kernel man . Nuff said ;)

- Google
[Samsung Galaxy Nexus] Antob125:
To the guys that posted those quadrants what rom and build are you using and what's your cpu set to?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] iGoogleNexus:
Lol stock rom here...

Max - 1420

Min - 729

Performance

- Google
[Samsung Galaxy Nexus] rchristy:
+1 only works with no security, not WPA/WPA2.
[Samsung Galaxy Nexus] yyz71:
Using PROVISION ROM

Max 1536

Min 729

On Demand
[Samsung Galaxy Nexus] leelaa:
Aokp

1536

384

Wheatley.
[Samsung Galaxy Nexus] bat0nas:
Just made test 181 vs 185_linaro.

Difference is 90 score points when max cpu is 729 and 16 score points when max cpu is 1536.

In all cases - wheatley governor has been used.

Attached: 1536Hz tests. The bigger score: using 185_linaro.

What can I say.. Linaro toolchain = fail?! :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] iGoogleNexus:
e.e ur scores suck

- Google
[Samsung Galaxy Nexus] rchristy:
New bug found in r185. Every time after reboot, mobile data switched on automatically regardless it was off before shutdown.
[Samsung Galaxy Nexus] nodstuff:
Same scores as before without 4.7 toolchain.

I don't notice any difference.

Used liquid smooth 1.5beta2 built using 4.7 and it was smoother alright but I'll wait til a proper release.
[Samsung Galaxy Nexus] mrasquinho:
Sorry the newbie question, but I just bought my Nexus a couple of days ago and I can't find this answer:

When flashing the nightly kernel, which GPU value should I choose? I prefer to use stock one, but I don't know which one is it..

Best regards
[Samsung Galaxy Nexus] leelaa:
Looking at the time diferances in those screen shots you have had about 10 minutes to flash the new kernel set it back up, and run the benchmark. Everyone knows not to benchmark when there phone is hot. Your tests are unfair.
[Samsung Galaxy Nexus] supernova_00:
185 sucks for battery life on wifi. LOTS of wlan related kernel wake locks.
[Samsung Galaxy Nexus] bat0nas:
I didn't know about that. And you are right: I really made those tests one after another.

But how this "hot phone" issue affects the results?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bat0nas:
I just wanted to show that there's no difference between two kernels.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
A cool phone allows the CPU/gpu work more efficiently and also with a hot phone you will get temp throttling unless you have it disabled
[Samsung Galaxy Nexus] bat0nas:
Thanks!

I will repeat my test (with 185) when the phone is cool and will compare with 181.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nodstuff:
I have temperature throttling disabled and could find no difference between r185 and r185-linaro.

Franco won't use it anyway as it isn't going to be released for Mac, only windows and Linux.

Morfic released 4.7 ones too and people were saying there was no major difference so it looks like all the benefit will be got from roms built with it.
[Samsung Galaxy Nexus] leelaa:
Youre comparing with 181? It should be comparing 185 with 185 linaro.

Also i can safely say that i benchmark every kernel i use.

I was on aokp 38 franco 185 and benchmarked and got about 3900,no i dont have screenshots as i dont screenshot every result i get.

I flashed 185 linaro exacly the same setup, and got my results i shared before. For me its an improvement, it may not be that way for everyone else but it is for me.
[Samsung Galaxy Nexus] nodstuff:
Compare 185 to 185-linaro.

What's the point in testing with two different releases??
[Samsung Galaxy Nexus] morfic:
The increased cpu and mem scores get drowned out by the wobbly io and out of the norm 3D scores dropping the average

considering we are memory bandwidth starved that is significant.
[Samsung Galaxy Nexus] morfic:
If you benchmark ram and cpu so the unaffected 2d/3d and highgly fluctuating IO scores don't skew the average, there is a difference even just from 11.10 LInaro 4.6 to 12.05 Linaro 4.6/4.7

But agree a 185-vanilla/185-linaro would be more useful.
[Samsung Galaxy Nexus] leelaa:
Lol he compared the wrong kernels.
[Samsung Galaxy Nexus] bradm23:
+1 on poor wifi battery life
[Samsung Galaxy Nexus] do0b:
currently on r181 atm, worth updating to r185? seems quite buggy
[Samsung Galaxy Nexus] shohratshankar:
Use the 384 version. That is closest to stock.
[Samsung Galaxy Nexus] willl03:
It is not, real good
[Samsung Galaxy Nexus] schizophrenia:
have tried "open" and the "wpa2" without a problem
[Samsung Galaxy Nexus] dr_w:
I have to say, quadrant score of 4110 aside, this kernel is blistering fast. Everything opens so fast. True test well be battery life.
[Samsung Galaxy Nexus] H2O_c:
It is smoother when scrolling in some apps using the linaro build. Thank you!
[Samsung Galaxy Nexus] bat0nas:
OK.

So I compared now 185_linaro_hot and 185_linaro_cool (couldn't get lower than 40C).

Surprise surprise - no difference. Actually there's a little difference. Something about 10-20 score points.

I just have no time comparing 185 vs 185_linaro. Bet I bet the results would be the same.

---------- Post added at 05:34 AM ---------- Previous post was at 05:33 AM ----------

Seems that I'm not the only one without ping glasses here.

---------- Post added at 05:37 AM ---------- Previous post was at 05:34 AM ----------

I know.

But look... the other guy compared the same Kernels and got same results :P

I also repeated the test with different temperatures - same results.

And this says that:

- Temperature is not such a big impacter. Even if yes, I don't see any sense making tests when a phone is cool. I want my phone to perform when I'm using it (when it's hot of course) and not when it's idle.

- 185 vs 185_linaro = 1:1
[Samsung Galaxy Nexus] grognaz:
has anyone tried a custom power mode with the single core option?

i tried to set one up but core1 always says its online. when i choose francos power saving mode it goes offline.

can someone test this and see if i might need a reset or if it might be a bug?
[Samsung Galaxy Nexus] BrUhNiGGs:
Dammit I know quadrant scores really dont matter but I dont get how most people are getting 4000+ with Linaro and this kernel. All I get is 3600 with regular AOKP or Linaro version of it.
[Samsung Galaxy Nexus] simms22:
at 1536, you should be getting 4000+ without linaro. unless its aokp holding you back.
[Samsung Galaxy Nexus] 8BitVoxel:
Will there ever be a day when this kernel will have cifs included? It's the only feature missing which stops me every time from using it for more then a hr before reflashing stock CM9 kernel which supports cifs. I'm a big user of this for streaming and efficient file transfers from multiple network file servers. Why don't you compile it in when you release a nightly or even with milestones.... Stock CM9 does it for every build....

I think your kernel and App which I've paid for are fantastic, wish I could use it full-time.

Oh and r185_linaro with CM9 20120611-NIGHTLY is great, looking forward to CM9-20120612-NIGHTLY with the rest of the Linaro hotness.
[Samsung Galaxy Nexus] morfic:
what frequency do you run and do you run it min and max being set to max frequency/the one you want to test?

they may not use thermal throttling either (which leaves only the thermal shut down protection between you and a device failure)

They may have disabled fsync (can lead to quick data loss on crash, including having to reinstall)
[Samsung Galaxy Nexus] metalspring:
Do you have force gpu rendering on in developer options? That usually makes a big difference...I just got 4090 while downloading a new rom at the same time lol
[Samsung Galaxy Nexus] morfic:
you win, i bet he has it off :)
[Samsung Galaxy Nexus] 52brandon:
my quadrant with 185-linaro is 3844. Was about 3600 on r185. Both at 1536. My CF bench went up from 7700 to 8160 though...
[Samsung Galaxy Nexus] metalspring:
Off topic

Btw you should see nocoasts antutu benchmarks on liquids test build, I think he is using your latest kernel and is getting around 9000 lol
[Samsung Galaxy Nexus] simms22:
both 3600 and 3844 are low. did you bench it at 1536/1536(high/low)? how many quadrants? if that was your first and only bench, bench2 or three times. the first bench can be dramatically lower than all the rest. did you have a lot running in the background or did you kill your apps before benching? also, from what ive seen around, aokp tends to bench lower.

---------- Post added at 01:55 AM ---------- Previous post was at 01:55 AM ----------

link?
[Samsung Galaxy Nexus] BrUhNiGGs:
Okay I just did 1.5ghz and 700 min with wheatley with force gpu rendering + linaro and got 3900 on quadrant. Not too bad...

The thing is my phone gets way too hot, way too fast. The app reports around 40C when really, its like 60 and it hurts to touch the top half of the glass.

No matter what CPU I choose it gets hot. I'm not sure what to do at this point. Tried many combinations can't find the sweet spot. Any suggestions?
[Samsung Galaxy Nexus] simms22:
when you check the cpu temperature, you have to check it during a benchmark, not after. after is too late, the cpu cools down very quickly. set the cpu to 1536/1536, start antutu, open up the app and check the temp while antutu is running. youll be surprised how hot it can really get.
[Samsung Galaxy Nexus] FC1032:
Just updated to 185 through the app, it seems to be running well

On paranoid android, I usually get lower quadrant and nenamark scores. Today, quadrant broke the 4000 mark... impressive. Nenamark is still low, but I suspect that's a rom problem. Not all numbers though, seems snappier in scrolling too.

Great work!
[Samsung Galaxy Nexus] metalspring:
Even though benchmarks aren't the best things to test performance with all my scores are excellent with linaro aokp and linaro Franco
[Samsung Galaxy Nexus] Lambetts:
Bump bump. :D
[Samsung Galaxy Nexus] 52brandon:
I only ran once. And it was on performance, which I was under the impression that it stays at max on performance so I wouldn't have to change the min as well. I'll try it a few times though
[Samsung Galaxy Nexus] bat0nas:
For those who are not getting 4K score with Quadrants.

Try that:

Kernel: 185 Linaro

Max cpu: 1536

Governor: Performance

Smartreflex: Disabled (checkmark checked in the options)

Force 2D rendering: On

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
I got this without linaro on 181:

They were purely down to running the 1536 MHz slot at 1225 mV for the bench in order to reduce heat. With 1250 mV I get around 4050 with or without the kernel compiled with the linaro toolchain.

Btw regarding the 512 GPU, from google dev Colin Cross

Now if you disregard the bit about the voltage change between 307 MHz and 384 MHz (as they now run on the same OPP) and use this formula to compare power usage between 384 MHz and 512 MHz:

Processor Power Draw = C x F x V^2 (where C=capacitance, F=frequency, and V^2=Volts squared)

I don't have the SR values for the CORE voltages without flashing it, so I'll use the voltage values from the kernel source.

#define OMAP4460_VDD_CORE_OPP100_UV	1127000
#define OMAP4460_VDD_CORE_OPP100_OV_UV	1250000

#ifdef CONFIG_OMAP_GPU_EXTRA_OVERCLOCK
OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 512000000, OMAP4460_VDD_CORE_OPP100_OV_UV),
#else
OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 384000000, OMAP4460_VDD_CORE_OPP100_UV),
#endif

This means that the 512 slot runs at 1250 mV stock and the 384 slot runs at 1127 mV stock. Calling 1250mV one arbitrary unit and using the formula above:

Power Draw @ 384 MHz = C*384*(1127/1250)^2 = 312C

Power Draw @ 512 MHz = C*512*1^2 = 512C

Therefore the additional power draw if you use the 512 MHz slot is 64%. As above the GPU's performance is limited by the memory bandwidth, so this 64% increase in power draw results in almost no increase in performance.
[Samsung Galaxy Nexus] jhondidfool:
my best score so far has been 3954 on quadrant, and 6090 on antutu... reading thisnmakes me feel i'm doing something wring... maybe the ROM? (and yes, at forced max CPU and forced GPU rendering)
[Samsung Galaxy Nexus] rogersnm:
6090 is pretty weak, even with 1228 MHz max I still get 6500. Give it another run once your phone has been idling for 10 minutes and see what it gets. You may just be running into throttling problems.
[Samsung Galaxy Nexus] vonapets:
USB

Hey Franco,

I am running R185, MoDaCo ROM Ir13.

I don't use the USB drive on my Galaxy Nexus and connect it to the computer very often. I tried to copy some files to the computer. The computer couldn't find my nexus. I use a friends S3 and the computer found it using the same cable etc. I then flashed your milestone 4 kernel and the computer then found the nexus.

I like experimenting with all your nightly builds and don't often use the milestone ones. Could you please look into this?

Cheers,

Dimitry
[Samsung Galaxy Nexus] The Gingerbread Man:
That sounds more like a driver issue than kernel.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Dr Byte:
Anyone else seen this minor glitch since 181?

Up to and including M4, when my phone booted, it would blank the screen briefly before it finished booting (about 2-3 seconds before you can first "unlock" it)

On 181, it has been producing "static" (graphic glitches) like an off-station TV for half a second instead (same duration that it previously blanked). I'm staying on 181 for a while because I'm testing a radio/RIL combination.

That's it. Nothing else to report, it's the only time I see it. Sometimes white static, sometimes light purple.

Mentioned only because it has the hallmarks of using uninitialised memory somewhere, which is rarely safe :)
[Samsung Galaxy Nexus] vonapets:
Yes, that's what I thought. However the only thing that I changed was the build. I have the all in one driver from another guy on the forum. Device manager wouldn't pick up the phone or anything. As soon as milestone was on it it was found instantaneously.
[Samsung Galaxy Nexus] bat0nas:
Franco vs. Franco+Linaro comparison (using free version of Quadrant app)

I just repeated the test with original Franco 185 Kernel and same settings:

Kernel: 185 Franco

Max cpu: 1536

Governor: Performance

Smartreflex: Disabled (checkmark checked in the options)

Force 2D rendering: On

And the results are in the screenshot. I repeated the test with original Franco kernel so many times (with big pauses between to cool my Nexus down) and couldn't get the score above 3978.

FINAL RESULTS FROM MY TESTS:

185 Linaro 4115 vs. 185 Franco 3978

Is this a big improvement? You tell me. In my opinion - 137 score points are just 3% of performance improvement on the doubtful benchmark.

Verdict: Not worth :D

--------------------------

Kernel: 185 Linaro B2

Linaro r185 built test results with a higher level of compiler optimization...

Source: http://xdaforums.com/showpost.php?p=27296645&postcount=19540

Same settings as above. Just the Kernel was changed to Linaro B2.

4209

Which now is +5.8% (compared to original Franco r185)..

Verdict: Results are getting more and more interesting... :D In a good sense.
[Samsung Galaxy Nexus] rogersnm:
Here's linaro r185 built with a higher level of compiler optimization. I haven't booted this myself yet as I'm doing a battery life test atm.

There's some nice linaro builds of AOKP (-O3) around if anyone wants to test them together.
[Samsung Galaxy Nexus] rogersnm:
Give the above kernel a go.
[Samsung Galaxy Nexus] GStar01:
**** my Nexus isn't rooted yet, hope someone testing it soon :D
[Samsung Galaxy Nexus] bat0nas:
Post has been updated: http://xdaforums.com/showpost.php?p=27296367&postcount=19539

New version of Linaro now scored 4209. Which is +5.8% compared to original Franco r185.

WOOHOO!!!!
[Samsung Galaxy Nexus] metalspring:
Sometimes things that look good on paper fail to be true in real situations...I have tested 384 gpu vs 512 and do notice a decent difference in performance and practically no difference in battery, which is negligible due to all the other factors involved

Don't forget linaro shouldn't do anything for kernels yet it seems as though it actually does
[Samsung Galaxy Nexus] bat0nas:
Check the Franco vs. Linaro vs. Linaro B2 comparison here:

http://xdaforums.com/showpost.php?p=27296367&postcount=19539

All r185.
[Samsung Galaxy Nexus] rogersnm:
Not entirely true, the linaro toolchain should do something for the kernel, it's just a matter of whether it's negligible or significant. Shall I build a 512 GPU version of linaro-r185-b2?
[Samsung Galaxy Nexus] metalspring:
Sure, can't hurt lol
[Samsung Galaxy Nexus] rogersnm:
But my poor little linux VM :eek:

Building now - give it 20 mins :cool:
[Samsung Galaxy Nexus] metalspring:
Also I have a bug to report, random reboot after disabling temp throttle and running a benchmark test

I know I was nowhere near the regular shutoff temp but it restarted anyway

It seems like setting the temp throttle off changed the restart temp much much lower...

Anyone else see this?
[Samsung Galaxy Nexus] rogersnm:
Did it shut off while running the benchmark, or well after? If you grab /proc/last_kmsg it should tell us a bit more