yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Moz007:
Rom stock, kernel 139, 1300Mhz/512Mhz.

I reinstall the app and its working again... :confused:
[Samsung Galaxy Nexus] raubkatze:
Atmospheric fluctuations -)

AOKP b32, r139 (512) 1228/729 - works without problems.
[Samsung Galaxy Nexus] CaspaTheGhost:
Yeah, saw that on Ezekeel's G+ page. I love the fact that with such an extreme OC, Conservative is then the governor of choice!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Eheh its ironic.
[Samsung Galaxy Nexus] dwang:
thanks...

r139 feels much better than r138.
[Samsung Galaxy Nexus] Metallice:
Hey Franco, would you consider adding the "Lazy" governor to your kernel? I've been adding it myself and it has been working very well. Lazy is basically ondemand but it sets a minimum time the mpu has to stay at a certain frequency before changing. This works really well as it prevents the phone from quickly bouncing back and forth between 384 and higher frequencies which I find this phone does a lot. Just a thought. Either way thanks for the great kernel, and I can always add it myself, but I figure it might be helpful to others too.
[Samsung Galaxy Nexus] nikulogical:
Battery drain slower on r139 as opposed to r138.
[Samsung Galaxy Nexus] franciscofranco:
Yes it wont hurt to add it!
[Samsung Galaxy Nexus] heo_con184:
My GNex was faster on r138 - 512mhz than on r139 - 512mhz.

Thanks Franco for the update.
[Samsung Galaxy Nexus] spaceman860:
Not sure if this is suppose to happen put if my battery is over 90% charged and I reboot my phone it resets battery stats back to 0 since on battery

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] franciscofranco:
Dont know whats that supposed to mean but its not kernep related.
[Samsung Galaxy Nexus] raubkatze:
In NenaMark2 with the same settings:

r138 (512) - 31.1fps

r139 (512) - 31.6fps
[Samsung Galaxy Nexus] Langduscher:
It's an ICS feature I think. When charged >90% and refreshing the stats in Settings-Battery it resets too.
[Samsung Galaxy Nexus] bballs91:
Mm mm looking sharp!

Thanks Franco!
[Samsung Galaxy Nexus] dwang:
those values seem kind of low. Especially the 2d and 3d scores.

I'm getting 3700 with cm9, r139 512gpu max cpu 1344mhz

This is the highest I've ever gotten actually. Most of the time its in the 3500 range.
[Samsung Galaxy Nexus] clepsy:
That's a low CPU score, are you sure not using the single core mode from the app?
[Samsung Galaxy Nexus] Metallice:
Oh man that is so great. I am REALLY bad at this whole git/source thing.

I don't know if it is any help to you, but this is the commit I was taking it from. I was adding all the code/text manually. Don't know if there is an easier way to do it lol. I'd be curious to know if you had any tips.

I had basically been adding/trying as many governors as I could. I set all the parameters/tunables to the same values for each governor, for example I set up_threshold and similar values to 80 for all governors.

OnDemand type - I liked Lazy the best as the min time in state feature is REALLY useful for our phones, and it seemed work great during actual use. However I also liked the idea behind Intellidemand, even though I haven't really tested it much. It lowers your max frequency when the GPU usage is low like when browsing the internet, but acts like normal OnDemand when GPU is active like when gaming. However, I'm not sure how this would work with ICS's GPU rendering.

Interactive type - I really liked LulzActive for its ridiculous customizability. It seemed pretty good with battery/performance too, but I didn't play with it too much as I prefer OnDemand governors. I tried SmartassV2, but the screen-off freq cap feature is worthless with our phones, and LulzActive seemed to be better on battery. Going to try SavagedZen next as a more battery friendly SmartassV2. Probably not going to bother with Brazilianwax as SmartassV2 with better performance seems excessive and not worth the battery cost.

Conservative type - I didn't find many good alternatives. I tried Lionheart, but I didn't see how it was much different from normal conservative except for the changed tunables. Scary seems to be just conservative with a screen-off frequency cap.

So TL;DR - I'm fond of Lazy and LulzActive with your kernel as better versions of OnDemand and Interactive. Going to look into the ondemand-based Intellidemand and the interactive-based SavagedZen
[Samsung Galaxy Nexus] clepsy:
By the way, had nice results with the latest releases, had nothing to complain about getting warm or battery drain, it just great for me, now testing R139, very nice for now
[Samsung Galaxy Nexus] raubkatze:
Franco, I noticed a strange thing. CPU usage in r139 looks like max and min cpu frequency are working equal time. Now I have: 1228 MHz - 21%; 729 MHz - 21%. But usually their relation is about 1/5

I tried all governors with the same result.
[Samsung Galaxy Nexus] sruel3216:
139 is awesome. the only problem i have with most of francos kernels is when i play music (from sd) it just drains battery faster then most kernels for me. tried interactive, conservative and ondemand. maybe if lazy is added it will help
[Samsung Galaxy Nexus] tcchuin:
Temperature on r139 is higher for me ..
[Samsung Galaxy Nexus] raubkatze:
And doesn't matter is SR turned on or off.
[Samsung Galaxy Nexus] meminiau:
Please tell me that the temp stats are not very accurate....?

I was just looking at them and it was 37C one moment, went up to 44 and then half a second later it was back to 37. Then just before I started typing this, it said 0C.

I was on 138, with the phone updating to 139 while typing this. Maybe it is just an issue with my phone... it would be the first! lol
[Samsung Galaxy Nexus] franciscofranco:
Maybe thats because of the latest interactive changes, I havent had time to test it enough.
[Samsung Galaxy Nexus] Protocol 7:
Many thanks!
[Samsung Galaxy Nexus] ock:
Tested flashing Nightly 5 over AOKP stock kernel, and opened and closed camera after a reboot. Strangely, battery drain when phone is idle increased, as seen from the battery graphs attached.

Not sure why this is happening, as I have been using the same set of apps for the past day, and had not installed any updates etc. Phone location also remains unchanged, on my table ;)

Forgot to add: Season's Greetings to Franco and everyone here!

More great kernels to look forward to in 2012 :)
[Samsung Galaxy Nexus] Spronx_:
Merry Christmas from Australia!

Many thanks for the hard work, especially updating a nightly on christmas day!

If I may, I would like to +1 to add UV in this kernel.

I understand battery drain is the current bug being squashed. Your kernel runs so much better than Apex, but I can squeeze 30 hours of battery from the apex kernel (standard battery).

Would it be possible to add a custom UV interface, similar to the one made by coolbho3k?

Thanks again
[Samsung Galaxy Nexus] incomer:
Great kernel, don't have the big drain others are talking about (see pic), but get some more time on the accu is never bad.. So plus one for me too for under volting a bit (so that it can't harm any device)

Happy Christmas!

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] mohitrocks:
Nightly on Christmas Day? You sir, are awesome. Thanks for your continued effort to make our Galaxy Nexus' the best it can possibly be! Merry Christmas everyone!
[Samsung Galaxy Nexus] pmicho:
Super smooth, but battery at 76% after 4h 20 min of very moderate use...
[Samsung Galaxy Nexus] Sjoerdos:
I experience bad wifi reception in combination with the latest MCR, i was running nightly 4 and just upgraded to nightly 5. Does anyone have a solution for this? Last night it was just fine. I'm running baseband XXKK6 and i tried wiping Dalvik cache and such.
[Samsung Galaxy Nexus] Sjoerdos:
I've figured out some parts of the problem, for one the reception isn't that bad, but it isn't what i expect it to be. The main problem:

The wifi won't recheck connection or something like that, i don't really know how to say this.

This is what i've done:

Run adb logcat and a continuous ping to my router side by side.

First the ping goes very well, then i move my phone to a location where it will still see the wifi, but can't use is due to the signal strength. The phone stays connected to wifi the whole time.

The ping starts to say: Destination host unreachable

Then i move my phone back to a position where signal strength was fine, but the ping won't resume, it still says host unreachable. Services like market, browser or anything that requires internet won't work. When i quickly toggle wifi off and on everything is fine again.

I'm running MCR Ir8 (latest), baseband XXKK6, franco's nightly 5. I had the same problem on nightly 4. The strange thing is that last night everything was fine. I wiped cache and dalvik cache. Now i'm all out of ideas.

This is the last wifi related thing i get via adb logcat is this:

D/PicasaSyncManager( 2140): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
D/PicasaSyncManager( 2140): background data: true
D/Beautiful Widgets( 461): CONNECTIVITY_CHANGE

This happens when the ping starts to fail, but the wifi stays connected the whole time.

I think it has something to do with the line: Background data: true

Does the kernel think 3g is taking over now and that's why wifi doesn't work?

Any help would be greatly appreciated. I hope i've provided enough information, ask if you wan't to know some more.

Edit: if i move the phone back before the ping says Destination host unreachable, it works just fine. And if i move the phone even farther away and it switches to 3g and then move it back to wifi, then it works just fine as well. Only the border case is a problem.
[Samsung Galaxy Nexus] energie:
Will i lose facebook synch using this kernel on bigxies rom?
[Samsung Galaxy Nexus] jeezy85:
am i missing something?

i got stock image rooted...

installed clockwork recovery

placed this kernel zip onto root and rebooted into recovery and installed from zip

now the phone is stuck on google sign everytime i boot up

what did i do wrong?
[Samsung Galaxy Nexus] Tung_meister:
Great kernel, only issue is the inability to run GTA3 sadly.
[Samsung Galaxy Nexus] aimetti:
u need a 4.0.3 rom
[Samsung Galaxy Nexus] jeezy85:
can i not use stock rom?
[Samsung Galaxy Nexus] jeezy85:
lol thanks

sorry for the noob question but my phone is on 4.0.2 and it shows that the system is upto date... how do i go about getting 4.0.3?
[Samsung Galaxy Nexus] MultiCulti:
4.0.3 isn´t out offizial @ the moment ;)
[Samsung Galaxy Nexus] The Alter Ego:
Here not working with ROM NexusBeam. Booting but not customizable
[Samsung Galaxy Nexus] MultiCulti:
lol ... nexusbeam is for nexus s:confused:

beamed in through my brain ...
[Samsung Galaxy Nexus] Grims:
I'm getting a few hard freezes on this one
[Samsung Galaxy Nexus] cancerouspete:
You can wait the unknown time till you get a 403 ota, or take the time to install peter alfonzos bugless beast 4.0.3 it runs smoother than stock, plus this kernel makes your screen prettier. Its worth it, read the General, and Q&A forums (and all the stickies at the top!!) Its easy

Galaxy Nexus Bugless Beast 4.0.3 cdma
[Samsung Galaxy Nexus] franciscofranco:
I ve answered that already its the CPU chip temperature not the device temperature.
[Samsung Galaxy Nexus] 6jaipur6:
Flashed 139 and lags in all apps and in games or gallery photos appear that artifacts many of them sometimes blurring the screen. No problems with temperature. Reverted to 135. Thanks for your work Franco.
[Samsung Galaxy Nexus] anfozy:
2366?! Thats as sharp as a potato! As others have said your not running single core are you?
[Samsung Galaxy Nexus] D3VI0US:
hello guys i'm new to the Gnex .. i guess the franco kernel have the same problem with the colors like the stock 3.0.8 .. the colors r so dimmed specially the White comparing to the cm9 stock 3.0.26 .. so i'm missing something here ?
[Samsung Galaxy Nexus] drawde40599:
lost data

Lost data connection 2x today on 384/build 139, this has never happened before on any of your kernels .. just letting u no .... running stock GSM 4.0.4 radio and bootloader. ,,, screen off
[Samsung Galaxy Nexus] javi3k:
sorry to aks this noob question but which mode of governor is better for battery life on franco kernel, im just testing it for the firts time , since i dont play game on nexus
[Samsung Galaxy Nexus] nklenchik:
Depends on the nightly. Ondemand or Interactive
[Samsung Galaxy Nexus] javi3k:
oh thanks im on r135 from what i read is more less hot cpu so far im ondemand

thanks :3
[Samsung Galaxy Nexus] isinisterx:
Back to r121 not liking these new nightlys
[Samsung Galaxy Nexus] Remoteconcern:
I've also moved back to 121. Less battery drain, just as fast. Although I think all the nightlies have been so good I can barely tell the difference, Franco has to try something to improve them!
[Samsung Galaxy Nexus] nklenchik:
Nah, 138/139 was by far the fastest
[Samsung Galaxy Nexus] drawde40599:
I ran 121 for over a week and 138 is a lot faster, 139 feels a lil slower than 138 even overclocked, both r just as smooth MY OPIONION
[Samsung Galaxy Nexus] isinisterx:
I was getting very bad screen off drain on the newer ones so I switched back
[Samsung Galaxy Nexus] svan71:
coming from a wipe? I did a clean with 135 and absolutely love it. went too 139 without any issues at all.
[Samsung Galaxy Nexus] drawde40599:
Ya I don't even look at my battery so I wouldn't no about that, I can't tell anything unusual battery the same as would be at this time of day .... I did go back to the 384 / 138 build its just faster: )

....

---------- Post added at 04:21 PM ---------- Previous post was at 04:09 PM ----------

I also noticed the screen is not as bright after, installing this kernel, I actually went back to factory images of 4.0.4 and started with fresh phone used it for a day then installed Franco kernel on top of and the brightness is lower even at stock color settings, dunno ....
[Samsung Galaxy Nexus] hosmsdos:
Tried the new nightly but 135 is by far the best kernel i have ever seen
[Samsung Galaxy Nexus] jeetS:
Im running r138 384GPU oc 1344.

Super happy with it. No issues and battery seems better than 135.
[Samsung Galaxy Nexus] isinisterx:
no I never wipe, too many apps and takes too long to keep restoring everything
[Samsung Galaxy Nexus] franciscofranco:
This is the reason I offer older kernels for download so users can use whatever they like the most.
[Samsung Galaxy Nexus] yyz71:
Love 135...
[Samsung Galaxy Nexus] svan71:
Titanium Backup is your friend...

---------- Post added at 08:40 PM ---------- Previous post was at 08:39 PM ----------

does Francos play well with CM9?
[Samsung Galaxy Nexus] isinisterx:
When you flash a new kernal every few days its annoying.

And i'm testing CM9 right now, so far the best combo i've had is Gummy 1.0 + R121
[Samsung Galaxy Nexus] svan71:
not the point, before complaining about issues, the first thing to consider is the fact its a dirty install. that goes for roms and kernels...
[Samsung Galaxy Nexus] Bosio91:
I'm having an issue with the Franco.kernel app widget, because the MPU, IVA and CORE VOLTAGE values are always 0mV.

Any ideas? I'm running r139
[Samsung Galaxy Nexus] SkaDiZ:
Love b135 too... Feel that b135 has longer on screen time compare with 138/139..

---------- Post added at 09:00 AM ---------- Previous post was at 09:00 AM ----------

If u read changelog for b138 u will get the answer...
[Samsung Galaxy Nexus] Bosio91:
Got it! Thanks
[Samsung Galaxy Nexus] franciscofranco:
Maybe, maybe not. I'll end up reverting SR3 eventually, this was just an experiment before I start closing the patch window for Milestone 3.
[Samsung Galaxy Nexus] dpaine88:
on 139 my phone is running hotter than usual.

On wifi and just using Tapatalk and twitter.. CPU sitting at 53C

ok it has calmed a bit to 45C

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nklenchik:
Again, no problems here on 139. My temp stays at 48C for pretty much all of my basic tasks
[Samsung Galaxy Nexus] franciscofranco:
I just added Lazy for r140 but I'm not gonna add any more governors sorry :)
[Samsung Galaxy Nexus] franciscofranco:
r140

* SmartReflex1.5 is the default again for temperature and stability purposes - thanks for all the testers in the last experimental builds

* Added Lazy governor from users request
[Samsung Galaxy Nexus] joeyfong:
Flashed, thanks
[Samsung Galaxy Nexus] svan71:
after all is said and done, which do you use for regular every day use?
[Samsung Galaxy Nexus] Metallice:
Of course. I wasn't expecting you to :). I was just stating my findings in case anyone was interested in the various governors out there and what I had found. I only suggested adding Lazy because I felt out of all of them it could be the most helpful to have specifically for our phones.

Edit: Anyway I was testing all the other governors out today. Meh. Lazy wins. Lulzactive is cool for the customizability. All the rest are worse than the default govs.
[Samsung Galaxy Nexus] siuba:
seems after r135 got compatible problem w/ voodoo display experiment 0.2

r138/r139/140 also! lately i found out i can star the franco.kernel.updater first then start voodoo again can solve it!

if run voodoo first then can see this screen!

r140 also can see the voltage now, even lower than r133, now showing 982mV, before over 1000mV

View attachment 1014610
[Samsung Galaxy Nexus] schizophrenia:
running r140 (512) on Lazy now

so far Nenamark2 shows good score again without artifacts

quadrant shows early 3k which is slightly lower/consistent to what I had with r135 (512)

overall smooth and snappy

temperature at 38C during idle... 46C during charging.. normal? i never really checked temperature before on r135 or before so i am not really sure what's a normal temp
[Samsung Galaxy Nexus] SkaDiZ:
Thanks Franco.. Will test for temperature and artifact issue...
[Samsung Galaxy Nexus] icbt:
I have used the Generic Hotplug with interactive govneror all time since RC125

I never get the Nenamark2 higher than 25 fps

but when I see the post above they can get the > 30fps without Generic Hotplug

I try it with RC139 with interactive and no Generic Hotplug

I easily get > 30 fps in Nenamark2 and better fps in Atuatu benchmark

I think that the Generic Hotplug may not run properly :o

hope this would help!
[Samsung Galaxy Nexus] drawde40599:
slow

384 and 512 build 140 feels really slow, compared to all the 130's?? Even with OC ? Franco u still have the 110 code laying around; ) that was your fastest build I'd go back but lots of app changes since then .... 140 still running very clean, smooth just seems slower
[Samsung Galaxy Nexus] drewlim:
Holy crap temp just went 60 aftr playing order and chaos for 20mins. R140 lazy 384-1228. Right now im idling 48-53ish. Testing interactive now...
[Samsung Galaxy Nexus] Metallice:
I flashed 140 and let it settle. Temperature is already lower than the previous build! I suppose my phone wasn't a fan of SR3. It's back to hovering around 40 degrees whereas with the last few it had been around 50.

Lazy works great just like it did added to the previous builds. I went into you app and let it idle. With lazy the frequency stays at 384, while with regular ondemand it (often) bounces between 384 and 1036. YAY!

You're the best man. So glad I don't have to mess with kernel sources and git anymore :D. Thanks.
[Samsung Galaxy Nexus] BrUhNiGGs:
Ive googled what lazy governor is and just to clarify, its just a better version of ondemand with a lower sample rate?
[Samsung Galaxy Nexus] ragnarokx:
It's Ezekeel's baby ;)
[Samsung Galaxy Nexus] Metallice:
Hmm. Looks like by default min time in state and sampling rate are both set to 15000. I have been setting it to 15000 for sampling rate and 30000 for min time in state and setcpu applied that when I booted up 140. I don't know if having them both at 15000 does us any good. I'm going to leave it how I've had it as it has been working great for me.
[Samsung Galaxy Nexus] franciscofranco:
As fast as the latest builds, nothing has changed that could make it faster or slower.
[Samsung Galaxy Nexus] inffy:
Franco

Possible to add the vibrate control to the app? Thanks
[Samsung Galaxy Nexus] SrTapir:
It doesn't seem that CORE and IVA voltages can be UV anymore in #140. You can manually change them but at the "Calibrated voltages page" they are still at the nominal values.

I'm at 384/1344 Lazy gov.
[Samsung Galaxy Nexus] BrUhNiGGs:
Isnt it because you have SmartReflex on?
[Samsung Galaxy Nexus] SrTapir:
It always have been. With UV you're limiting the max values of the Voltage, Smartflex plays with the lower one's. I think it does not affect in this case.
[Samsung Galaxy Nexus] raubkatze:
You need to disable SmartReflex in order that use your current uv values.
[Samsung Galaxy Nexus] Metallice:
His point is that the voltages are higher than the voltages he is setting. Usually with smart reflex the set voltages are the upper limit and SR calibrates down from there.
[Samsung Galaxy Nexus] BrUhNiGGs:
Hmm, well it seems like it was always like that for me regardless of the nightly version when I would try to UV manually. The CalibratedVoltages page would always show higher voltages than what I put.
[Samsung Galaxy Nexus] SrTapir:
It did not happen before, with last releases it always shown my top undervolted values. In the CPU line is shown that the 870mV is the UV value for 350mHz, does not happen with IVA and CORE.
[Samsung Galaxy Nexus] drawde40599:
Ya, didn't see anything in change log, so figured, maybe fast isn't fast anymore to me; ) 140 is running perfect tho, I've tried every kernel out there for our phone and not to kiss ass but ur combination of speed and smooth, hasn't been close to matched, only bad part is now I may only buy the phones u own =O! Thanks for ur time!
[Samsung Galaxy Nexus] BrUhNiGGs:
Well Franco may know the answer. Im no expert at this :p

You should just switch to an earlier release that works for you
[Samsung Galaxy Nexus] SrTapir:
It's only a little bug, I think, only to be noted. :o

#140 is great for me, very very smooth, batt to be tested today but I'm happy with these latest releases, now looking forward to LiquidSmooth development boost. :)
[Samsung Galaxy Nexus] tcchuin:
Its the sane for me.I used to set 820 for 384mhz.and it would obey, but not anymore since r140.

I can't read the core voltage on Franco apps either .

Btw, can anyone tell me of snartreflex controls voltage of CPU only, or it also controls other part such as gpu?
[Samsung Galaxy Nexus] BrUhNiGGs:
It calibrates CPU, GPU, and IVA.
[Samsung Galaxy Nexus] BrUhNiGGs:
Yeah, I too can't wait until the new release of Liquid. This phone is going to be smooth as shiiiet since a little bit of codes from Franco will boost it up and in future releases :D
[Samsung Galaxy Nexus] franciscofranco:
I wonder what kind of magic is working on your device. I have the same r140 and the same 4.1.1 app version on my device and all its working correctly. Smartreflex calibrates the voltages as it sees fit. If you set it lower than the calibrated value your own value will be used, if your value is above smartreflex it's obvious that the calibrated value will be used. It can't be more obvious than this.
[Samsung Galaxy Nexus] isinisterx:
I just got off liquid I like gummy better
[Samsung Galaxy Nexus] iGoogleNexus:
Quick question...

I noticed within the app that I bought there's a IMOSEYON Kernel.... can someone tell me about it? =]

Sank yu

- Google Galaxy Nexus
[Samsung Galaxy Nexus] maisi:
+ 1

According to dmesg SR knows the set UV values but ignores them and uses the ones it wants to use?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] BrUhNiGGs:
Everyone has their opinion. Gummy was the first rom I used and I liked it. I tried 1.0 and it did not feel as smooth as Liquid.
[Samsung Galaxy Nexus] wolfy:
R140 really smooth for me. No issues at all.

Nemamark2 31.8

512 MHz gpu 1036min/1344max

Interactive governor