yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Misledz:
Hmm, Im hesitant to try r180 over M5, I haven't done any benchmarking tests lately to test stability or anything. Just flashed the M5 a while back was highly pleased with lazy governor. Any upperhand with the 180 over M5? , I can't seem to notice any changes.
[Samsung Galaxy Nexus] andQlimax:
but they tweaked also the kernel..or im wrong? why they should not have tweaked it?
[Samsung Galaxy Nexus] bigeyes0x0:
Long time no see, Misledz :D.

Seems like you also got yourself a GNex.

About your question I think you mistook AOKP Milestone with franco's kernel as the latter is at M4. #180 is fine and has a lot of new interesting things that franco added.

Generally I find franco's stuffs to be stable, he derped his releases very rarely. If you want more fun, try morfic's.
[Samsung Galaxy Nexus] opethrocks:
Im trying 1536mhz with smart reflex turned off, i know franco said smart reflex wont affect 1536 but its my last resort. On a side note, my signal strength is muuuch improved with r180. I dunno if its just coincidence but i have a steady 2-3 bars now in places where i would usually have 0-1
[Samsung Galaxy Nexus] franciscofranco:
Go to their repository and see for yourself. I picked one or two commits like it is on the changelog that I took time to write. Other than that I saw nothing major. Most of thier kernel work is for pandaboard.
[Samsung Galaxy Nexus] lovelymobile:
Hi great work Franco i m on 180.384 with modaco custom rom IR13 imm76d band 1536@1375v. No problem and very fast and responsi ve.

I have a problem with lightflow, the led doesn t work.

Thanks

Bye
[Samsung Galaxy Nexus] Misledz:
Aye, Glad to see you here on the scene too mate :P Was surprised you got yourself one. Been here and there stuck with Gtab10/9003 and now finally the Gnex scene. (Didn't find the S3 appealing and IMO Nexus > S3) Anyways yeah sorry was a major typo, Got confused as I flashed way too many Milestones today..:confused:

Ive tried other kernels but franco's volume improvement keeps me coming back plus the constant update makes it worth the use. Would try 180 later today after flashing aokp r38 (Also it's been 2 days since I got this baby, what's so good about morfic?)

Thanks franco for your amazing work :) Makes me feel the Gnex was worth the grab after all.:D
[Samsung Galaxy Nexus] Diger36:
Tried ondemand now. Again spontaneous reboot. Logs attached.

http://db.tt/tRKRnRUx

http://db.tt/22lRkMqZ
[Samsung Galaxy Nexus] dipole:
So what voltage are you going with then?
[Samsung Galaxy Nexus] vomer:
oh! thanks for clarifying :D
[Samsung Galaxy Nexus] six_dfx:
r180 testing report :

192/1536 wheatley @ 1400mV : 2 reboots while charging with screen off, 1 reboot while in deep sleep, 2 freezes with screen on

192/1536 interactive @ 1400mV : no reboot or freeze in several hours of testing (quadrant, antutu, temple run)

192/1536 interactive @ 1375mV : testing for 6 hours now, still no reboot or freeze

More infos: GSM, stock rom, interactive governor hispeed_freq set at 1536000
[Samsung Galaxy Nexus] Bonvaz:
Guys I have a problem..I installed franco from recovery and now nova 3,minimotor, shadowgun,and all the games with sd data don't find anymore the files.....
[Samsung Galaxy Nexus] opethrocks:
Currently running 1350mv on 1536mhz no reboots so far...(fingers crossed)
[Samsung Galaxy Nexus] :
Hi franciscofranco :D,

In your application,why not make a setting for the CPU temp limit.

It's actually 75°C but it's hard-coded in the kernel,right?

It would be great to have a choice (with a big warning maybe :D) and allow the users to set it.Maybe no limit (110°C) :eek::p:D or maybe something like 90/95°C?

Because according to the use at 1.53Ghz the limit of 75°C can be reached quickly,not only in benchs...

:)
[Samsung Galaxy Nexus] rogersnm:
I can't speak for nova 3 and shadowgun but minimotor runs fine for me. Use something like root explorer and make sure /sdcard has files in it (is mounted).

People will probably end up doing damage with that, my phone already reaches 94C with the current 75C throttle point.
[Samsung Galaxy Nexus] strife91:
Hi guys, i have a small issue here.. i'm using milestone 5 4.0.4 and with franco kernel and i have this clock freezing issue. When I lock my phone, the time displayed on my lock screen is different from my statusbar. I had to go to rom control, hide and enable the clock and restart the phone. But the problem still appear. Can someone explain to me what is happening and help me to solve this perhaps. Thanks, have a nice day.
[Samsung Galaxy Nexus] Adrian312:
Screen turn on just like that

Hi guys,

could you please confirm if I am the only one affected by this:

with Milestone3 no problem at all. With milestone4 my screen goes on from time to time without any notification or anything like that.

Its on, after 15 sec, goes black.

Happens 5 time already.
[Samsung Galaxy Nexus] :
Hi,

Maybe maybe not...In any case the CPU shut down at 110°C,with Glados kernel I set my CPU temp limit at 90°C...so far no issues.Trinity kernel also have this option.

In long term...I don't really know but I think it will not turn at 110°C permanently so no more damage and in any case higher CPU temp->reboot...

It might just help a little in some tasks...For guys who like stress her CPU :D

And with an option in the app after it's a user choice->no complain.

It's like the overclock/undervoltt here is the possibility,maybe not really good but the user have the choice...

It's just an opinion...

:)
[Samsung Galaxy Nexus] franciscofranco:
Yep it makes sense now. I will probably just make a toggable to deactivate/activate thermal control.
[Samsung Galaxy Nexus] The Gingerbread Man:
Hi Franco, any ideas or possible fixes for this issue where several people aren't able to boot up on r180 384 gpu. Is there a way I can provide any more detail than I already have tried?

Sent with a shake
[Samsung Galaxy Nexus] rogersnm:
Could you make it so that it still prints the temps to kmsg when they are above the 75C threshold? It'll allow people to watch the temps via adb [cat /proc/kmsg] if they so desire.
[Samsung Galaxy Nexus] Speedum:
Not exactly your problem but using M5 yesterday, my Beautiful Widget clock is different from the status bar.. Only killing the Beautiful Widget App will 'reset' the clock to the correct value. Happened once only
[Samsung Galaxy Nexus] a5pe4:
I believe some people have experienced that on aokp. I don't think its a kernel issue.
[Samsung Galaxy Nexus] FlipFlops24/7:
Similar thing happened to me but I was on B37. I auto-flashed from the Franco App and it rebooted and sat at the Franco Bootloader animation. I wiped data and flashed B38, then 180 and all is well.
[Samsung Galaxy Nexus] :
Yes,thanks;)

You know what?

Since a few months I'm not running your kernel...It's a choice,need test and blablabla...:D

You intoduce again a 1.53Ghz slot so give it a try ;)

I forgot something about Francisco's kernel...The battery life even if I don't care a bit...

Flash nightlie r180/512Mhz GPU,re install your app then full battery charge...

3H in sleep/23 min screen on and I am at 96% battery.Only browsing in 3g and settings in your app with 60% brightness!

Smartreflex disable with Ondemand governor...

I will not make comparisons with other kernels that satisfies me,but here...:eek:

Usually with the same settings I'm at about 90%...

I will continue to test and report ;),It seems awesome...Yes forgot the Francisco Franco's battery life...:)

:)
[Samsung Galaxy Nexus] Moz007:
I'm trying to find my undervolt values but i don't understand how SR works...

If i want use my personal values, i have to disable SR ?

But when i put my values, SR still show me this values !

My values are : 700-725-875-1000-1125-1175-1375.

It seem to be stable, i'm still testing.

But when i select 1536mhz for max frequency the first time, with stock voltage, the phone reboot immediatly and the app lost every parameters...

So i'm not sure the voltage is the probleme...
[Samsung Galaxy Nexus] WitchMX:
I have AOKP 37 + Milestone 4 and shadowgun is running beautifully
[Samsung Galaxy Nexus] Remoteconcern:
Franco, I have a small suggestion.

It would be really useful to me if your app could display time spent in each CPU state, like CPU spy does.

I know this is quite simple to do, but I think people would find it useful (you might suddenly become less popular with the CPU spy developer though!)
[Samsung Galaxy Nexus] rogersnm:
SR overrides all your values except for the 1536 MHz value (in your case 1375 mV), if you disable SR then the kernel will use your specified values (although I believe it won't set them below 830 mV). If you get immediate crashes with 1375 mV then try raising the voltage to 1400 mV.
[Samsung Galaxy Nexus] static416:
In my experience that isn't a software issue. That's caused by the USB port malfunctioning.

I think it starts shorting out against something and thinks that you are plugging in the USB cable. Happened to my phone and progressively got worse. Eventually the screen would stay on continuously and the battery would die quick as a result.

It's a relatively common problem on this phone and the SGSII.

I took it back to the retailer and they sent it to Samsung for a warranty repair. Samsung replaced the USB port no questions asked, and everything is fine now.
[Samsung Galaxy Nexus] olivercervera:
Uhm, updated from M3 to M4 using the updater app. Everything seems good!

AntuTu benchmark: 6369

no OC no UC

It's good? I think so, a friend of mine with his Note has reached only 6446 (ICS, stock kernel)
[Samsung Galaxy Nexus] qballe:
a lot of users have problems using 1500mhz cpu , but a lot of reboot are in idle :

so, it is possible that is not a voltage problem but a voltage drop ?

ALL of yours x86 cpu on yours moterboard computer drop from full load to idle about 0.1V, I don't know so well how the Gnext motherboard give voltages, but someone can check the dropping ?

obv imho

Marco
[Samsung Galaxy Nexus] rogersnm:
Do desktop computers not go the other way and drop voltage under load so as to ensure there is no damage from voltage surges when the load disappears? [Meaning that a desktop CPU runs closest to it's nominal voltage when load is at its minimum]
[Samsung Galaxy Nexus] jhondidfool:
I asked this yesterday, but seems my question is to remain unawnsered...
[Samsung Galaxy Nexus] dpaine88:
Looks like I got a good piece of silicon, running 1500 for 20hrs now

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] opethrocks:
Which governor? Smart reflex on or off?
[Samsung Galaxy Nexus] L-ViZ:
milestone4, on which nightly is it based? and when has it been released?
[Samsung Galaxy Nexus] rogersnm:
r175, about a week ago [31/05/2012]

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

Testing on r180:

I can run interactive 192-1536 MHz no problems and wheatley 192-1344 MHz no problems however wheatley 192-1536 MHz results in frequent reboots.

It seems like the wheatley governor and the 1536 MHz slot don't like each other
[Samsung Galaxy Nexus] The Gingerbread Man:
Well 175 was the previous nightly if that's what you mean and 2 or 3 days now

Sent with a shake
[Samsung Galaxy Nexus] WitchMX:
Usually I don't care about benchmark scores, as long as my phone is silky smooth, but it is a reference, no matter what.

With AOKP + M3 I had erratic results with Quadrant Standard, between 1090-2600. Now with M4 I have scores around 3400-3600 and 6700+- with Antutu. No OC either.

And more important, the phone is really showing that improvement, no lag whatsoever.

Since it is running so smooth I'm not gonna jump to r180 for now. If its not broken, don't fix it.

Awesome job Franco.
[Samsung Galaxy Nexus] six_dfx:
No they don't. The higher the voltage, the lower the transistor switching time will be, so modern CPUs run at their nominal voltage at their nominal speed, and drop clock and voltage when there is no load in order to reduce power drain.

That's also why overvolting is needed to achieve high overclocks on desktop CPUs where heat dissipation is less of an issue.
[Samsung Galaxy Nexus] Ashtrix:
M4 is pretty good & i had almost evry kernel out here flashed & this one's got better color calibration by default :D ..!!
[Samsung Galaxy Nexus] wildguess:
I have the stock ROM and Franco kernel r175, no custom settings in the Updater utility.

When I flashed r180 using the Updater last night the phone did not boot.

It got stuck on the initial screen with the word "Google" on it and the top part of the phone got hot quite quickly.

I flashed r175 and the phone could start.

I downloaded r180 again, flashed it in CWM, erased cache and Dalvik, and the phone refused to boot again.

So, I returned to r175.

What should I do for the phone to be able to run on r180?
[Samsung Galaxy Nexus] qballe:
no, the "perfect" motherboard should not drop ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
Just wait, something needs fixing. That makes 5 of us now with this. Which rom are you on?

Sent with a shake
[Samsung Galaxy Nexus] monkey hung:
Alright don't know if this is a ROM issue or kernel issue but I'm on 180 with AOKP B38 and when the battery is low, it doesn't shut up and keeps popping up no matter how many times I press OK. The battery stats are all messed up too.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] wildguess:
Stock IMM76I, radio XXLA2.
[Samsung Galaxy Nexus] The Gingerbread Man:
That makes 2 cm roms, 2 stock roms and 1 akop

Sent with a shake
[Samsung Galaxy Nexus] rogersnm:
I'm know intel uses SpeedStep to underclock/undervolt CPUs when they are unloaded but I'm talking about vdroop on fixed clocks.

http://images.anandtech.com/reviews/cpu/intel/penryn-oc2/transient_vdroop.jpg

http://images.anandtech.com/reviews/cpu/intel/penryn-oc2/transient_no_offset.jpg

from: http://www.anandtech.com/show/2404/5

Those two images best explain it, when load is removed the CPU voltage spikes before returning to it's normal level. To combat this the CPU voltage droops under heavy load, so that when the load is removed it never spikes beyond the nominal voltage. This means that the CPU runs closest to it's nominal voltage when there is no load.
[Samsung Galaxy Nexus] dpaine88:
Wheatly gov 700-1500 SR is on

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] qballe:
yes , and I have seen also cases of "positive droop" , so the voltage on full load is +0.01X of the nominal !

I'm talking about my experience with desktop x86 stuff, don't know ARM, these are only hypotheses :p
[Samsung Galaxy Nexus] Sveke:
Giving it another go.

Upped 1500 voltage to 1450.

Got reboots at 1400 & 1425.

Cmon ****ty silicone.......hang in there
[Samsung Galaxy Nexus] Diger36:
/Off topic (sorry)

You know you are on Franco when you start talking to your silicone :D

/Back on topic

My phone get's a lot hotter on this nightly then on r175. Even now that I am using the settings I had before on r175 I can feel a substantial increase in heat once in a while. Tried to pinpoint it but didn't succeed. Will keep on trying.

This nightly doesn't like my phone or vise versa...
[Samsung Galaxy Nexus] Theshawty:
What you mean with ****ty silicone?
[Samsung Galaxy Nexus] rogersnm:
Just got a reboot with the interactive governor (192-1536):

Last reset was MPU Watchdog Timer reset (PRM_RSTST=0x8)

Screen was off and it was in fast charge mode whilst connected to the PC.

It seems to occur much less frequently on interactive than wheatley. (1 in 6 hours vs 1 every 30 mins)
[Samsung Galaxy Nexus] Gahh Its Lee:
Some phones are just made better. Some, like mine can't run 512 gpu and can't over clock to 1.5.
[Samsung Galaxy Nexus] Sveke:
It's the non uniform totally random mine sucks and yours might not stuff that our chips are made out of......
[Samsung Galaxy Nexus] Sveke:
Well phone just took a dump at 1450mv too. Freeze and Reboot.

Looks like my 1536 days are over unless Franco makes some miracle happen.
[Samsung Galaxy Nexus] nathanson666:
180 is a beast. with 1536 cpu and 512 gpu everything is smooth.

for some reason I got artifacts when running 512 gpu on glados but not on this kernel. does anyone know why? does it have to do with the fact that the gpu frequency can be changed on the fly in glados?
[Samsung Galaxy Nexus] Remoteconcern:
Franco mentioned a while back that he had to remove live GPU overclock due to some users experiencing errors, so maybe.

On the other hand, it might be something to do with voltages being lower in GLaDOS or something.
[Samsung Galaxy Nexus] tempera:
Where can I find the 512 gpu r180? I don't have the Franco app as my credit cards playing up.

Thanks
[Samsung Galaxy Nexus] Think420:
I don't really see the point in overclocking...

the performance gains are hardly noticeable and the battery drain is increased, the only reason I see for over clocking is benchmarks and we all know that those don't matter either

so the real question I'm asking is why overclock at all?
[Samsung Galaxy Nexus] kolyan:
i dont know why people overclock.... they are benchmark whores i guess.

although some kernels run better with 1 step up and battery is still better then stock.
[Samsung Galaxy Nexus] jhericurls:
I don't see the point in 1.5GHz, I'm happy with 1228Mhz. Having a faster clock speed does render webpages faster.

Test it out with TheVerge website.
[Samsung Galaxy Nexus] jnr21:
What about first post of this thread?
[Samsung Galaxy Nexus] dspcap:
I am so bummed. NO matter what I do (I have tried many things), I can't get decent battery life out of this kernel like I used to. Not even getting 6 hours with minimal use.

Prior to AOKP 37 the kernel and ROM combo was perfect for me.
[Samsung Galaxy Nexus] sert00:
HARDLY NOTICEABLE...?not my case..i use glados kernel 400-16xx mhz cpu wheathley governor tweaked,512 mhz gpu and +7% bus\ram OC,SR off (for mpu&core,ON for iva)cpu with medium undervolt,gpu with little overvolt (for overclock bus and core more)and undervolted VANA,VUSIM etc etc etc.\with that configuration i have extreeme smothness,in all conditions,zero lags,optimal scrolling\rendering on lanchers\homepages and a decent battery life (from 24 to 30 hours with medium\high usage).with stockish kernel and stock freq. i haven't the smoothness that i have now,in some situation there are micro-lags,blocks,and many games don't run how i like.with that i find my way.i like overclocking and manages parameters in kernel,i have the need to do that,and if i haven't the need,i could do that only for fun.;)
[Samsung Galaxy Nexus] nikulogical:
Battery drain is same between 1200 and 1350 steps so why not. 1500 is another issue.
[Samsung Galaxy Nexus] Theshawty:
Will the battery drain be much higher if ill use 1344/729 instead of 1200/384 MHz freq? The phone's probably gonna idle a lot tomorrow, though so what are your thoughts on that?
[Samsung Galaxy Nexus] superbobup:
Because these are testing nightlies where we want to see what happens. These kernels aren't just there for stability/performance, we wanna have some fun too ;)
[Samsung Galaxy Nexus] CaspaTheGhost:
Man, busy day at work combined with the 1.5 slot results in me having 20 pages to read through!

I've experienced the same reboots as everyone else so for stability on a work day I've been running wheatley on 729/1344 and no issues.

Hard to judge performance and battery compared to interactive after a single day, will test further but for now...

View attachment 1111555

View attachment 1111556

My usual push and sync running but with a bit more than usual as added 4hr checking on Plume, Tapatalk and trying the updated FB app as well. Also includes 49mins of calls and a good 30mb of Play updates on my way home (dodgy train signal!)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Zflash:
Because we can.... :)
[Samsung Galaxy Nexus] laureanop:
Don't forget that the gnex was originally meant to run at 1.5 mhz and 384 gpu. Because of variances in hardware and cpu chips google and samsung brought it down to 1.2 and 307 respectively .

I'm one of the lucky ones that can run the phone at this original speeds ( 512 gpu actually ) and boy it puts any phone to shame for a slight price in battery ( with the wheatly governor the jury is still out on that one )

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] superbobup:
What brightness are you running? Just curious as I usually do 90% and feel like I never break 3.5 hours on my setup which is similar to yours
[Samsung Galaxy Nexus] atsavlis:
Running liquidsmooth 1.4 with franco nightly - 180.... Tried all the combination of governors and havnt had a single freeze or reboot. Ran benchmarks with power mode on full power, performance governor and managed to get 7019 antutu and 3940 quadrant.... Pretty damn good if you ask me! Keep it up Franco!
[Samsung Galaxy Nexus] jhericurls:
I'm getting similar results but running 192/1228. 7% Battery left with 3h 40m screen time (extended 20mAh battery)
[Samsung Galaxy Nexus] andrew53517:
So I have been running 192 mhz with 1.5 ghz all day yesterday and today (using Wheatley). Then I suddenly got two back to back reboots with 4G on for the first time. So weird.

I increased the CPU 1.5 ghz voltage from 1390 mV to 1400 mV to see if that does anything.. I guess I'll just have to wait and see. :cool:
[Samsung Galaxy Nexus] dimgl:
Pretty happy with milestone 4 so far. Waiting to reset battery stats to have optimal battery life
[Samsung Galaxy Nexus] holyzombiejesus:
You don't need to reset battery stats. That doesn't do anything ;)
[Samsung Galaxy Nexus] nikulogical:
Anyone do any any tests regarding min freq and wheatley?
[Samsung Galaxy Nexus] Timmyfoxeh:
r180 is pretty awesome on me :D

Testing out wheatley and having pretty great results!
[Samsung Galaxy Nexus] metalspring:
Almost right, I don't think they lowered the CPU/gpu speeds for stability, the CPU and gpu are tested to work perfectly stable at 1.5+ GHz and 384+ mhz respectively

most likely they lowered the speeds for battery saving purposes
[Samsung Galaxy Nexus] franciscofranco:
They lowered it because of an hardware/software bug that made the devices unstable with 1.5ghz or more. Luckily some of us can run with higher frequencies because of our blessed silicons.
[Samsung Galaxy Nexus] opethrocks:
So those of us having random reboots with 1.5ghz will never be able to run that speed and be stable?
[Samsung Galaxy Nexus] do0b:
running aokp b36 + franco r180 @ 1536-384MHz, wheatley, and SR on.

everything seems stable.
[Samsung Galaxy Nexus] franciscofranco:
Dunno, Im not a vident.
[Samsung Galaxy Nexus] laureanop:
Francisco : the 384 mhz gpu and the 512 gpu have the same voltage. Do they use the same OPP as well ? Even if it is not the same opp : do they consume the same battery because they draw the same voltage ?

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] collin911:
Heyy guys,,i just want to ask whether you guys have had problems playing HD games with this kernel i am asking this cause i am experiencing some problems with this the problem is that the games just exit when i start them this starts happening as soon as i flash this kernel this only happens with HD games the other games work very well.I have tried this kernel on aokp,silm ics rom and android revolution hd and the same thing happens on all these roms.The HD games do work fine with the stock kernels. I would like to ask if you guys could help me fix this problem cause my G-Nexus is just awesome with this kernel(P.S. I have tried milestone 3 and 4 and i'm currently running aokp.)
[Samsung Galaxy Nexus] opethrocks:
You're right, dumb question
[Samsung Galaxy Nexus] shonen45:
It should help if you can name those HD games having problem running on your phone. Currently I have problem playing two games from Gameloft: Modern Combat 3, and Dungeon Hunter 3. They simply turn off and back to home screen, without force close dialog box.

ROM: AOKP Milestone 5.

Kernel: Franco nightly 160.
[Samsung Galaxy Nexus] franciscofranco:
Different voltages because they run on different OPP.
[Samsung Galaxy Nexus] anuraj1:
Just wanted to let you guys know that there are several of us on VZW GNexuses that can't get past the Google logo on r180 too.

I'm on AOKP b38 but others are on other ROMs.
[Samsung Galaxy Nexus] Timmyfoxeh:
By the way, congratulations Franco on reaching a thanks meter over 10000!

You deserve it man!