yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] neverhappy:
I'll consider it a lesson learned the hard way. RTFM from now on FIRST.
[Samsung Galaxy Nexus] wedz:
For the starters; I have nothing against people overclocking, or trying to reach max scores in benchmarks. I have done it as a hobby in the past with my home PC's, and I agree - it's fun.

But nevertheless, I would like to voice up some concerns about the current trend that seems to be creeping up.

I'm happy to hear that you Franco also consider this "milestone" idea, actually that is basic principle for any professional SW development, and I'm glad it's coming here too.

What I would like to point out in all this "quadrant and overclocking madness" that's sweeping this thread, that not all people are geographically in similar conditions (for example heat, humidity etc), that is why this device has been originally clocked to 1.2GHz, and I'm sure Samsung had clear reasons to do that.

I'm sure there are others as well, who run this device in mission critical tasks, and SoD is an reason to change the kernel, that just can't happen.

Franco, I fully understand (and really appreciate) how difficult it's to do professional level of development, with the resources you must have.

I do too, want to squeeze best performance out of the device, but still can't change out of 13.1 because of the instability recent kernels seem to have to some users (of which I'm sure 90% are self-made).

Basically, I guess I just want to encourage you on your basic principle (rock solid stability), in the wake of the recent "Man look at these scores, they are awesome. I only had to stand for 10minutes in the balcony to get them".

Keep up the great work, I've been using this kernel since 13.1 came out, and it totally changed user experience for me.
[Samsung Galaxy Nexus] ChongoDroid:
18.2 @ 1.65 GHz is stable for me but 18.3 @ 1.65 GHz is instant reboot for me. I liked the new conservative tho
[Samsung Galaxy Nexus] neverhappy:
You and I need to go to reading classes.

You should not set the 1.65 setting in 18.3. The last couple of pages are a an example of why not to do that.
[Samsung Galaxy Nexus] drawde40599:
I understand 100000% but for us that can read, maybe have kernel that downloads with ur app not have the 1500+ settings and a big ugly link on xda for kernel with 1500 + settings?? My phone loves the 1500 setting and when I'm at home on the phone o love being able to use it .

Just a thought
[Samsung Galaxy Nexus] franciscofranco:
That's not viable and causes fragmentation. Just built 18.4 without 1,6ghz and 1,65ghz, I can't afford more issues.
[Samsung Galaxy Nexus] drawde40599:
Ya thought bout it after I posted, not everyone has app, never understood how anyone could just flash something on there 700$ phone without reading what it was first . Anyways 18.3 running perfect at stock settings, set the colors at " recommended' settings from ur app, very nice makes seem like different phone .
[Samsung Galaxy Nexus] lemmy_0:
ok will test it
[Samsung Galaxy Nexus] ChongoDroid:
Thank you for your patience and time franco, your a great asset to the galaxy nexus community.
[Samsung Galaxy Nexus] dmmarck:
This times a million.
[Samsung Galaxy Nexus] minooch:
For those wondering, I've been running 18.3 for 26:17 Hours, 25:45 on battery currently sitting at 71% - Screen on time 40m

I'm using Conservative 700/1500

1500 - 1300mv

1350 - 1275mv

1200 - 1250mv

1000 - 1150mv

700 - 1050mv

350 - 900mv (not actually used though)

No probs what so ever - I think that voltages can go down a little still

EDIT: I forgot to say - I pre warned you guys about 1600 & 1650 not working from 18.3 onwards & It's in the OP - Can't believe how many of you DON'T read!
[Samsung Galaxy Nexus] bendirkss:
My GF says the exact same thing! "You love you phone more than me" ;)
[Samsung Galaxy Nexus] raniosman:
My girlfriend plays with my Android phone way more than I do.

And by girlfriend, I mean my right hand. **forever alone :( *

Two releases in one night? Franco, bro, go sleep!
[Samsung Galaxy Nexus] dmmarck:
First, amen. Second, thanks for posting the voltages!
[Samsung Galaxy Nexus] raniosman:
When changing CPU or voltage settings, is it wise to set 'apply on boot' or no?
[Samsung Galaxy Nexus] dmmarck:
I don't mainly because of what was seen tonight.
[Samsung Galaxy Nexus] GrandMstrBud:
Why is 1.6 or 1.65 even an option then?
[Samsung Galaxy Nexus] dmmarck:
It is not anymore. It was and then people had problems. Stability > benchmarks.
[Samsung Galaxy Nexus] M3drvr:
Man m on 18.2 and have been running at 1.65 since the kernel came out without a single reboot or issue. Will play games and stream video and music for hours without so much of a hiccup. There will be some heat at times but so far very solid I feel. I appreciate the excellent quality of your work. Keep it up! Thank you.
[Samsung Galaxy Nexus] minooch:
18.3 @ 1.5 is actually better than 18.2 @1.5, 1.6 or 1.65 - throttling is constantly happening & ruining your experience - upgrade :D
[Samsung Galaxy Nexus] drawde40599:
I no just released 5 seconds ago but do u / can u recommend voltage for 1300 and 1400? Nice to hear from guy actually involved in dev
[Samsung Galaxy Nexus] mistermojorizin:
with which version did the color multiplier get added to the kernel? also do you guys change it from default? what settings are you setting for the v1 offsets?
[Samsung Galaxy Nexus] ChongoDroid:
Yeah set on boot is good for your "everyday" settings if you're experimenting with higher speeds like I did tonight on 18.3 :D then it's best to leave it unticked.
[Samsung Galaxy Nexus] drawde40599:
All those answers in the app .
[Samsung Galaxy Nexus] kashix:
sorry but just wondering, can I just use this kernel without the use of any governer or what in setcpu? just like it work normally? does it work like that as well?
[Samsung Galaxy Nexus] mrfuzzie23:
hey Franco is there anyway to see the calibrated voltages that smart reflex sets thru term? also is there anyway to see if the CPU is being throttled at certain clocks? seems like everything is running good at 1.5 but just wanna check if any throttlin is happening
[Samsung Galaxy Nexus] drawde40599:
1.4

I normally run 700 /1350 but this 1400 is niceeeeeee!!!
[Samsung Galaxy Nexus] mistermojorizin:
that's nice. could someone please answer my questions though?
[Samsung Galaxy Nexus] drawde40599:
Funny, just 10 posts ago dev were just talking about how no one can read guess u missed that two? Ur asking someone to take the time and go look / read for info u can find urself on this thread possibly on first page??? . Just saying! Have a great night: )
[Samsung Galaxy Nexus] Nezorflame:
Using almost the same settings (350-1500) on #18.4 I'm getting constant reboots.

last_kmsg follows...

Seems that I have to cope with not lowering voltages)
[Samsung Galaxy Nexus] drawde40599:
1500 works no UV? Mine is hit and miss one day it likes one day it don't .
[Samsung Galaxy Nexus] mistermojorizin:
i've taken a lot of time to search this thread, as well as the one in cdma and the one on rootzwiki. first page doesn't help me. neither do your sarcastic comments.

i meant first page doesn't help wit hthe specific questions i was asking - when the multiplier first appeared in the kernel, whether you guys keep it stock or change it, and what are some color settings you're all using. i'm on 13.1 and contemplating going to the latest kernel depending on those answers.
[Samsung Galaxy Nexus] drawde40599:
It was added in 17, there settings u need ask them . I was an ass because of ur " that's nice " comment I was trying to help u by telling u that that info is in the app along with a lot more .

Have good night
[Samsung Galaxy Nexus] simone87stilo:
Hey Franco hello, congratulations for all the work you do, you deserve 5 stars: D

I 18.2 18.4 I have now flashed the see how it behaves: D
[Samsung Galaxy Nexus] bendirkss:
That's a lot to answer
[Samsung Galaxy Nexus] simone87stilo:
hotmod plug best to keep it enabled or not nellla version 18.4? thanks
[Samsung Galaxy Nexus] minooch:
"I no just released 5 seconds ago but do u" huh? What do you mean?

It's very hard to recommend - every device differs - for example, Franco's almighty GN can't UV past 1400mv on 1.5

Try lowering 25/50mv & test for a day - if all good, try again
[Samsung Galaxy Nexus] ratson:
with #18.4 it still throttles like hell :) is Smartreflex proven to be any help?

or will it reduce battery consumption?
[Samsung Galaxy Nexus] maisi:
Since smartreflex is enabled again, UVing yourself shouldn't be needed anymore, the Chip UVs itself already!

To see the calibration use dmesg | grep sr_ in the terminal!

Core =gpu

Mpu =cpu

Iva =Video Decoder and other stuff

If it doesn't display anything try to use it after a reboot.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] drawde40599:
Funny, I'm so used to texting its kinda ruined my writing: ) ya that's what I usually do just wondering what u had at . I'm using your settings took 1400 down a 100 v working great test here for awhile . Thanks
[Samsung Galaxy Nexus] nklenchik:
Still using conservative from 18.4 still guys?
[Samsung Galaxy Nexus] ratson:
with #18.4 I already had 2 hard freezes at 350-1.5, #18.2 worked great at 350-1.65
[Samsung Galaxy Nexus] ratson:
for me the given command returns

<4>[ 1.640319] sr_init: No PMIC hook to init smartreflex

it looks like smartreflex cannot be enabled

EDIT:

actually it looks like it is doing its job
[Samsung Galaxy Nexus] maisi:
I get the same line but right after it SR gets initialized and starts to work.

Tried a reboot ?
[Samsung Galaxy Nexus] SrTapir:
Your Kernel is amazing Francisco.

Amazingly fast, good battery and rock stable.

Continue developing this please, a little contribution: 7J420207FD382333L

+1 to a full stable (no nightly) release.
[Samsung Galaxy Nexus] Shetlander:
First of all I would like to say Im amazed by the number of people who cant read. Your playing around with a £500 phone and just seem to be flashing what you appear to not understand.

Franco, a huge congratulations with 18.4. It seems you have created the beast that has slain the previous champion that was 13.1. No more thermal issues even at 1.5Ghz, just a nice smmoth phone with monster scores to match.

Thankyou.
[Samsung Galaxy Nexus] hosmsdos:
Thank you franco 18.4 is awesome man. Btw GTA is super smooth now. Thanks again.
[Samsung Galaxy Nexus] minipaolo:
How did you tune it, franco?
[Samsung Galaxy Nexus] nklenchik:
Alright, I'm gonna be one of those guys...

What are you guys running on 18.4?

I'm on conservative 700/1500

Edit: 700/1400 now...1500 crashed the phone on PowerAMP
[Samsung Galaxy Nexus] atsavlis:
Guys for us that don't have Franco's app, can you tell me what Franco's recommended values are for the color multipliers so I can try them out using the echo command??
[Samsung Galaxy Nexus] Niksko:
Suggested multipliers are 143, 158, 194 and -8, 0, 10 gamma values

Hope that helps
[Samsung Galaxy Nexus] zack80:
Hello Franco

I just installed version 18.4, I paid for the processors in 1500Ghz maximum and minimum in 350Ghz I currently Millestone ROM 3. At the moment I just had a reboot and I have FC on all my applications. This now I'm forced to do a system restore.
[Samsung Galaxy Nexus] phunghoang24:
after test quadrant benchmark (PowerVR SGX 540):

My GN: everything is good, but 3D is bad <= 40FPS 1296 point, Hizzzzzzz.

My GS1 (i9000) with the same GPU, 3D = 60FPS stable 2210 point :( it's not OC GPU.
[Samsung Galaxy Nexus] cgollner:
Now compare the screen resolution of GN to GS1.. It's much harder to render on a bigger resolution. This is why you can't make a decent Graphics benchmark for Android.
[Samsung Galaxy Nexus] maisi:
Try to enable the forced 2D hardware rendering, results should be higher then ;)
[Samsung Galaxy Nexus] phunghoang24:
exactly, thank. Quadrant more than about 300points.
[Samsung Galaxy Nexus] whiteintegsg316:
View attachment 917512

1.5 on conservative

Bamb!

I'm happy
[Samsung Galaxy Nexus] freddan83:
I just updated to 18.4 and has come over a problem. everytime i turn my screen off i loose my reception and when i turn the screen on it connects again.

im running the 4.0.4 prebaked modaco with radio xxkl1
[Samsung Galaxy Nexus] rahan95:
Sorry but I never went above 1.5 with conservative =(

On top of that, I think I messed up file structure while trying to recover and had to reflash google stock image.
[Samsung Galaxy Nexus] phunghoang24:
wow!

My Quadrant Benchmark : 3880 points!

Sweet ^_^
[Samsung Galaxy Nexus] sonyboypatrick:
i have really nice quadrant scores, battery life is nice too but could be a bit better, i would like to know how guys got a screen on time of 3 or 4 hours :confused:

Uploaded with ImageShack.us
[Samsung Galaxy Nexus] phunghoang24:
Sometime could't unlock screen, someone is like me???

phone could't get driver camera and patient touch unlock!

reboot to fix :( i don't know because kernel or ROM AOKP buil 25!
[Samsung Galaxy Nexus] yyz71:
Just finished doing CF benchmark. Here you go :)
[Samsung Galaxy Nexus] IINexusII:
18.4 working great :) no lags on conservative default 1200-700 settings, 4% drain in 4 hours
[Samsung Galaxy Nexus] nicandris:
i clicked on Turn CPU1 on in the app and the phone crashed/rebooted... didnt had this before. what log should i post? ;)

Also all the settings lost from the app

*edit* now whenever i choose to change settings from the app the phone crashes (1400/1500Mhz/hotplug)... anyone else having this or should i wipe?
[Samsung Galaxy Nexus] atsavlis:
How can the multipliers be 143, 158, 194 when in the script they are larger numbers ex - "2004318071 2004318071 2004318071"
[Samsung Galaxy Nexus] franciscofranco:
Those are the first three numbers of each number string, change the "200" part with the respective number.
[Samsung Galaxy Nexus] atsavlis:
Franco do you still suggest we run 700 as a min?
[Samsung Galaxy Nexus] franciscofranco:
Yes, I think I've set 700mhz as minimum by default.
[Samsung Galaxy Nexus] mekanismen:
Edit: franco beat me to it.

Might aswell add that 18.2 worked wonders for me batterywise, 1% drain/2 hours while idle. Just flashed 18.4 and no issues so far. Thanks a lot for all your work!
[Samsung Galaxy Nexus] itolson:
18.4 causing boot loops then not booting at all

Mine was fine after 18.4 but now the phone tries to boot i.e the boot log's and animated boot but thats it, it never gets to the desktop as it where.

any ideas...

even a factory reset and re-install modaco r11 rom it wont boot....

had to factory reset then reload rom, and restore...
[Samsung Galaxy Nexus] nklenchik:
Okay here's my setup. Anyone have something similar? I'm about to go to bed (I work nights usually) so I'll report back with idle drain.

I'm on AOKP b25 with the 4.0.4 radios (3G area with sync on)

Edit: I'm using the saved values
[Samsung Galaxy Nexus] Simer03:
Mine is very similar! I got 3730 quadrant with 1.4 - 700 values

sent from my Nexus Prime
[Samsung Galaxy Nexus] whiteintegsg316:
why 700mhz. Just so I understand
[Samsung Galaxy Nexus] rahan95:
Same thing happened to me.

After flashing google stock image, Modaco 4.0.4 and Franco kernel again, it seems my chip wont stand 1500 Mhz any longer, whereas it used to do on previous releases.

However, 1400 Mhz has been fine for the past 2 hours
[Samsung Galaxy Nexus] dmmarck:
Could be rom conflicts? Mine's been fine on both CM9 #1 and AOKP MS3; I was a bit worried about it still being alive/well this morning, but all fears were alleviated.
[Samsung Galaxy Nexus] loudaccord:
you guys are daring to use apply at boot. If you make one mistake, you could be stuck in a bootloop.
[Samsung Galaxy Nexus] rahan95:
So true, exactly what happened to me yesterday, won't happen again =)
[Samsung Galaxy Nexus] bendirkss:
Why 700? I have 350. Won't 700 use a lot more battery?
[Samsung Galaxy Nexus] bendirkss:
What's an example of a mistake
[Samsung Galaxy Nexus] dmmarck:
Having it overclocked past 1.5ghz, setting on boot, and autoflashing or flashing 18.4 while having those settings.

I guess there are a couple of mistakes in there ;).
[Samsung Galaxy Nexus] itolson:
was not set to apply at boot plus a reflash of the kernal did not sort or format cache and data...

had to completely start again for some reason not blaming the kernel could be another program i had installed as the kernel has been stable for the last few weeks ive been trying it.
[Samsung Galaxy Nexus] bendirkss:
I had mine set on boot 350-1000 ondemand and flashed 18.4 and it booted with those settings, no issues.
[Samsung Galaxy Nexus] Vangelis13:
Then you revert to your back up which you have made for that very reason
[Samsung Galaxy Nexus] dmmarck:
Well yeah because that is within the smart reflexes threshold. I'd hope you wouldn't have any problems!
[Samsung Galaxy Nexus] bendirkss:
I don't understand how this messes you guys up. I always have apply at boot.
[Samsung Galaxy Nexus] Craiq:
Hi

after flashing 18.4 every thing works fine

(crash in 18.3 was clock settings at boot from my rom)

but my screen has a blue tint (also in 18.3) and my cf bench scores are bad ... (6576 overall) ...

is there for any reason?

(cache/dalvik clear and battery pull befor flash, voltagecontrol clocksettings at boot off)
[Samsung Galaxy Nexus] bendirkss:
So having this set on boot is totally fine? Someone who has it set to 1500 would need to watch it ?

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] kjwalker:
Been explained quite a bit. This is the best explanation.
[Samsung Galaxy Nexus] Simer03:
the blue tint is courtesy of Franco himself.....benchmarks mean nothing! its fun to play with, but in the end, nobody ever notices the "increased" speeds! lol
[Samsung Galaxy Nexus] drawde40599:
Update radio , and did u drop min to 350?? Put back to 700 if u did
[Samsung Galaxy Nexus] :
Hi Franco,

I flashed your kernel #18.4 last night and it's running great even at 1.5Ghz for several hours of testing,so far no problems:no random reboots,freeze,overheating or lag it's perfect!

I prefere the old name for governors like conservative than those you use before (franco_gazelle,etc...) :D,easier with some apps that can change some values for conservative governor for example without the good name you can not make ours "tweaks" via an app,or keep conservative with your governors :D

Since the kernel #13.1 that was for me the best,now it's the kernel #18.4 which is the best for me :)

A quick bench,without reboot/Ondemand governor:

Conservative governor:

All is stable and fast!

Thank you very much for your hard and great work;)
[Samsung Galaxy Nexus] bendirkss:
So bottom line. I'll have a better battery life with 700 min?

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] drawde40599:
Yes better or the same, always best test urself every phone different but really no need to 700 is great!!

I thought there was something built in to kernel that when it crash it auto go back to stock.settings?

When I.do.normal reboot my setting always stay, when it crashes from me pushing to hard and reboots itself, my settings are gone everything is stock??

Is this not a " safety" feature built in to.kernel? I thought it was
[Samsung Galaxy Nexus] darrendm:
What are your UV values mate?
[Samsung Galaxy Nexus] loudaccord:
what if the 350 slot wasn't there in the next kernel? You could be in trouble. Nightly 17 didn't have 350... went to 400mhz.
[Samsung Galaxy Nexus] :
Hi,

Stock with #18.4,no under/overvolt...

:)

EDIT:Franco,I just noticed that my init.d scripts to modify certain values for governors ​​in /sys/devices/system/cpu/cpufreq/***** works well now (like with nightly#13.1,I told you about this problem a while ago by mp,and it did not work after nightly#13.1).

I am testing and my scripts work properly,thank you for watching it ;)
[Samsung Galaxy Nexus] darrendm:
Great. Using that now. I have pretty good performance with simply 700/1000 with conservative. But I'll test 700/1500 over the next 24 hours to see how it feels.
[Samsung Galaxy Nexus] timsen11:
I dont like this Kernel anymore ! Always lags and every second day another update which makes it worse ! Im angry about myself that i bought the app. Popkorn Kernel runs much more betrer.

Taptalked by GNex running CyanogenMod 9
[Samsung Galaxy Nexus] dmmarck:
I've been riding 700/1500 w/ conservative for almost 20 hours now and it's run fantastic. No hangups and wicked fast. Best of luck!
[Samsung Galaxy Nexus] bendirkss:
Your so right. I'm at 700-1000 now cause its better apparently. Let's see how battery life goes today with it.

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] sg1969:
Does someone come to your house, point a gun to your head, and forces you to update? No? Then nobody is forcing you to update. If an old version works better, then use that.
[Samsung Galaxy Nexus] monkey hung:
*sigh* rebooted when I OC to 1.5GHz on AOKP B25, Franco 18.4
[Samsung Galaxy Nexus] sg1969:
Ok that was kind of a douchy reply... Didn't mean to sound like an ass.

But it would help more if you told us what version you have, which one worked best for you, what problems you have, your settings, etc.

As you can see, everyone is flashing and testing different versions, settings, it's really trial and error until franco comes up with what he thinks is a stable build. Until then, use what you think is best. You don't really have a right to complain, you paid for the updater app, not the kernel.
[Samsung Galaxy Nexus] drawde40599:
Dose that come with butter?? U will be missed: ).

OK OK I'm sorry I couldn't help it .
[Samsung Galaxy Nexus] GchildT:
Well i hope everything works out. It was real. Peace...
[Samsung Galaxy Nexus] bendirkss:
AOKP+Franco= Such a sloppy greasy buttery orgy!

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] paratox:
!voteforkick

most pathetic xda member since a looooong time!
[Samsung Galaxy Nexus] rahan95:
His post was not exactly nice =)

Now, It's hard to read people saying "how in the world could you mess up your device", "how dared you flash without backing up first", etc...

That make newcomers as myself feel like dumb people for no reason.

Naively thought new versions could only improve things. The updater app, which i gladly paid for only to support the Dev (and the amount is very low compared to the benefits) made me get the (bad) habit to flash updates as soon as they show, no matter if I'm home with a computer around or on the road.

Now I know it's wrong, learnt it the hard way =)

Still don't understand though why 1.5 Ghz used to work perfectly well up to version 18.2 and only 1.4 will with 18.4, on a brand fresh install after flashing stock Google image file.
[Samsung Galaxy Nexus] dmmarck:
Yeah that makes no sense at all to me. Try reflashing?
[Samsung Galaxy Nexus] franciscofranco:
I will explain why 1,5ghz might not work anymore in a little bit, on my way to home at the moment.
[Samsung Galaxy Nexus] joelteixeira:
Good to hear that 18.4 is working nice for most of ppl. I've been using the first oficial CM9 released today and without change any setting on franco app my phone reboots immediately if I set the max to 1500. Tried 1400 and got some random reboots, and using 1300 was looking stable but rebooted when I tried to transfer some file via USB.

Reverted to stock kernel for awhile, anxious to get back to a new shot when another version be released.
[Samsung Galaxy Nexus] dmmarck:
I backed off from 1500 to 1200 just to be safe, but I had 0 problems with it. Do you think it won't work anymore for the majority of users or just a few? Thanks!