yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kyokeun1234:
Just switched to 268, and GOD is it smooth? I have AOKP build 2 and was running Trinity and I thought that was smooth... Last version I've used was 249 and the improvement from 249 is HUGE. I don't know about battery life, since I just flashed it, but I will report on it after about a day or two of use :)

This will be my daily driver for now!
[Samsung Galaxy Nexus] evostevo1:
268 = milestone 6. Nice work.
[Samsung Galaxy Nexus] Hungry Man:
So I updated my kernel, hit "reboot" or whatever it asks when it finishes installing, and when I get back my Nova is reset. It seems like multiple applications rolled back to older versions.

Franco's app is uninstalled and when I try to install it again I get error -24.
[Samsung Galaxy Nexus] kyokeun1234:
And this is why you do things manually :p

Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
[Samsung Galaxy Nexus] osm0sis:
Franco, to me these two posts seem to contradict, though I'm sure it's just because I don't entirely understand. The first seems to say that all steps up to 1536 are SR calibrated, but then you said that 1536 can't be added because SR will run it at the voltage of 1228Mhz? What about 1420Mhz? Are we just lucky that SR running 1420Mhz at the voltage of 1228Mhz doesn't crash things?
[Samsung Galaxy Nexus] Hungry Man:
First time it's been an issue. I think an app was updating in the background and that's why there was such an issue.
[Samsung Galaxy Nexus] franciscofranco:
I mean up to 1536Mhz, excluding 1536Mhz step ;)
[Samsung Galaxy Nexus] franciscofranco:
Fsync disabled am I right?
[Samsung Galaxy Nexus] kyokeun1234:
Maybe. Hopefully you have a nandroid backup :)

Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
[Samsung Galaxy Nexus] Hungry Man:
Naturally. The combination of Fsync being disabled and the apps updating probably messed it up. I usually enable Fsync before doing anything in the Franco,updater app but forgot this time.
[Samsung Galaxy Nexus] jcmm11:
For interactive (not dyninteractive) is input_boost still being set automatically? There's still no sysfs entry for it so we can't set it manually.

Just loaded the new nightly so no comments on performance, although I expect it will be up to the usual high standards. Love your kernels.
[Samsung Galaxy Nexus] osm0sis:
Okay I did some experimenting and I think I get it now! For some reason SR drops the higher frequencies to around 1220mV... Just a limitation of SR until someone fixes it I guess? 1420Mhz doesn't seem to get calibrated either though; seems to be anything with a voltage of 1300mV or higher doesn't, to be precise.

I've got SR handling up to 1420Mhz working quite well now though (by lowering the nominal for 1420Mhz to below 1300mV, I used 1285mV), and have 1536Mhz running quite stably by having it just excluded from SR at 1300mV. And of course this way SR still handles everything else. :D
[Samsung Galaxy Nexus] Blackcrx:
So I've always been using deadline and ondemand for the longest time and I've never had a problem. Battery is awesome everything is smooth.

I decided to try bfq and interactive since it seems that everyone's using it. Not really noticing a difference. Just curious what I should be expecting with this I/O and scheduler change.
[Samsung Galaxy Nexus] franciscofranco:
Input boost is handled in Tuna PowerHAL
[Samsung Galaxy Nexus] ÜBER™:
Franco will you consider doing GPU OC scalability instead of making multiple versions? Seems easier no? Then add an interface for it in your app. I think it'd be a good idea. :thumbup:

Sent From My Toro+ via White Tapatalk
[Samsung Galaxy Nexus] christophicer:
Hard to beat the battery life. Trying 268 tonight and will see how it works but 262 was fantastic.
[Samsung Galaxy Nexus] ÜBER™:
Would be even better without JD. Just an FYI. :p

Sent From My Toro+ via White Tapatalk
[Samsung Galaxy Nexus] prembox:
+10 on this!
[Samsung Galaxy Nexus] Dattack:
I was wondering how I go about adding or changing some of the new kernels to include the new WiFi drivers? 251 is the only kernel I can get good WiFI reception.
[Samsung Galaxy Nexus] nikulogical:
He had it set up like that before and it was causing issues or not working as well or something so that he set it up another way.

Personally, I don't think overclocking more than 384 gives any noticeable benefits at all.
[Samsung Galaxy Nexus] phenom9:
thanks for the posts, so there are 4 steps to get the nexus running ideally

1) gn toolkit

2) bootloader

3) aokp

4) franco kernel
[Samsung Galaxy Nexus] Stretlow:
Ive got homescreen scroll lag again, it seems to come and go between versions:o
[Samsung Galaxy Nexus] incomer:
Very strange, I've NON lagg at all? It is very fast..

What rom do you use?
[Samsung Galaxy Nexus] definator:
dont have any with aokp 14

but for me seems to be random, coz before i was running egb rom and sometimes happend, sometimes not

dont know if its kernel related or rom or whatever
[Samsung Galaxy Nexus] Stretlow:
Using the same rom, sometimes i get it some times i dont, with the latest rom and the latest kernel its back again
[Samsung Galaxy Nexus] Mnemoch:
Which live background?
[Samsung Galaxy Nexus] ljwnow:
Hi Franco and fellows, I would like to know what a deep sleep is. Is it called a deep sleep when the awake bar is blank?
[Samsung Galaxy Nexus] Stretlow:
its just a photo from my gallery that i always use

---------- Post added at 12:43 PM ---------- Previous post was at 12:36 PM ----------

Im just putting a photo from my gallery (one i always use the same one) and it lags if i put a system wallpaper on there it doesnt, wierd
[Samsung Galaxy Nexus] :
Hi,

Performance has been improved with nightly #10... :D

No reboot/Ondemand governor/350Mhz-1,35Ghz:

A little better than before for SD card write/CPU integer/CPU float-point :)

Always great kernel ;)
[Samsung Galaxy Nexus] Stretlow:
I wontder if its something to do with gallery wallpapers v system wallpapers
[Samsung Galaxy Nexus] definator:
i wonder how u get these scores.... my max was 6324 with 1200mhz... but with franco 10 and aokp 14 i am reaching ~6000
[Samsung Galaxy Nexus] :
Hi,

Same rom...And what i said running 350Mhz/

1,35Ghz

/On demand...Nothing more...No scripts or something else,i had used for a time Ram Manager Pro by Juwe11,but it overwrite some kernel values in the wrong direction.

I have also about 6300 running at 1,2Ghz...(much more than the Galaxy nexus with stock kernel :eek::D).

No reboot before my benchs,but i kill some apps running in background (just for a bench :D).

If you do multiple benchs,wait until the phone run cools->thermal protection->decrease cpu freq->lower scores...
[Samsung Galaxy Nexus] abz54:
My phone won't go into sleep mode, I have updated the boot loader and running the latest kernal, I have turned all sync off, any help
[Samsung Galaxy Nexus] ro_explorer:
It is not kernel related. Is either a rom bug or an application gone berserk.
[Samsung Galaxy Nexus] abz54:
Thank you
[Samsung Galaxy Nexus] definator:
cant say that. as i was on stock just received the phone i ran antutu and scored 6140. thats not much more for me...
[Samsung Galaxy Nexus] :
I mean with Franco kernel,running at stock cpu freq (1,2Ghz) i have about 6300/6380 in Antutu it's more than with stock kernel,i have also tested and with stock kernel i never had more about 6100...

Or i misunderstood you?

Btw with this kernel the perfs are awesome.
[Samsung Galaxy Nexus] chrisexv6:
A little late to the show, but Im fighting with a "warm" screen on my phone.......whites dont look as pure white as my Fascinate did.

As far as black emitting light, I noticed when I used a color adjustment app (Screen Adjuster), if you add some blue to make it more like Im used to, the black pixels dont completely shut off anymore.

Im not sure if this is similar to how Franco implemented his color tweaks, but it might be.

Interesting thing is that I cant see a difference with Francos kernel, even though I can see the tweaks he made in the kernel source itself. Im wondering if it has something to do with the ROM I happen to be running (AOKP)

---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------

My phone in general is like this........before and after Franco's kernel. The strange thing is that its mostly in the app icon text. White screens look pretty close to dead on white.

Debating trying to get another (although Ive seen pics of where its REALLY bad, a lot worse than mine........the Google.com home page looked completely Orange in the example pics, whereas mine looks almost pure white)
[Samsung Galaxy Nexus] definator:
Ok then everything is fine. What program are you using for oc?
[Samsung Galaxy Nexus] Nebucatnetzer:
Deep Sleep is when you're not using your phone then after some time the CPU goes into something like a standby mode called deep sleep. In this state the CPU uses a very small amount of power.

But the CPU isn't actively doing something. So everytime you want to use your phone or receive a message etc. the CPU awakes and is doing it's task and then goes to sleep again.
[Samsung Galaxy Nexus] ÜBER™:
0.0 384 and 512 is night and day. Best way to tell is the keyboard. Typing is seamless on 512. Its very choppy with 384. At least for my self.

Sent From My N7 via White Tapatalk
[Samsung Galaxy Nexus] nikulogical:
The only difference I could say is that 512mhz sucks battery faster when playing 3D games.

The keyboard being choppy is not a good sign. I don't think it's choppy even with the stock underclocked gpu.
[Samsung Galaxy Nexus] nswenson:
The latest R268 512 GPU appears to be running at 384MHz GPU speed. Perhaps there was a mistake when it was uploaded to the server? I used the Franco app to autoflash it.
[Samsung Galaxy Nexus] c_86:
K ... idk what's going on here. But no matter what kernel I use I cannot get internet via WiFi...

Signal meter shows connected to the WiFi network but no data transfer.... its happenings on both 268 and 264.

I have rebooted modem, router, phone etc.

Help...
[Samsung Galaxy Nexus] drawde40599:
I agree with other guy I don't notice **** with 512 GPU on either my gnexus, my keyboard is smooth as hell with both. Every phone different ;)
[Samsung Galaxy Nexus] nikulogical:
I have a name you know.
[Samsung Galaxy Nexus] mohaimed:
how does the dyinterarctive governor works? does it help to save battery life?and will the 384gpu helps to save battery life as well? wat do u guys recommend?-384 or512?
[Samsung Galaxy Nexus] stick1300:
Same here.
[Samsung Galaxy Nexus] dyepnoodle:
can someone please share the default settings for the color multipliers on franco kernel updater app. And what is the best settings u guys have for that? TIA. :)
[Samsung Galaxy Nexus] numb_:
Look at Galaxy Nexus Collaborative Optimal Color Settings ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
How are you measuring this?

read back from the last 4 or 5 pages Franco explains about dynamic interactive. About GPU version I'd say if your nexus can handle 512 then use it, if you have problems with weird behaviour and / or unexplained reboots try the 384 one.

Look here http://xdaforums.com/showthread.php?t=1790325

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bartolinio:
I'm late, sorry
[Samsung Galaxy Nexus] dyepnoodle:
Thanks dude !! :)
[Samsung Galaxy Nexus] Gaku86:
Guys sorry for this noob question but what are SR/GH Settings? And also can you tell me what is the best governor and powermode? I'm looking for good battery and smooth phone
[Samsung Galaxy Nexus] Kurre:
Well, who doesn't want a smooth phone with a good battery ;) but anyway, stock settings are very nicely tweaked, so I'd suggest trying those at first and then try small changes if you feel like it :)

interactive and bfq are good choices and for a powermode..can't really say since I'm using custom ones. You should get easily 3,5-4 hours of screen on time with medium/heavy usage in about 14-18 hours of uptime.
[Samsung Galaxy Nexus] mohaimed:
facing lags while switching tabs in browser with stock kernel settings.
[Samsung Galaxy Nexus] nuwan32:
LOL you do realize they both use the same voltage?
[Samsung Galaxy Nexus] caioketo:
Hi there,

Some people said that the problem with charging while OTG in use is kernel related,

Is there anyway to confirm that, or, if franco kernel enables it?
[Samsung Galaxy Nexus] osm0sis:
Franco, just wanted to make sure I understand correctly, am I right that 1420Mhz is also not calibrated since it's nominal voltage is over 1300mV?
[Samsung Galaxy Nexus] a5pe4:
Sigh I want to use this kernel but it makes the screen way too dim when set to auto brightness...
[Samsung Galaxy Nexus] ace-user:
having problem with wifi on r264…

just now i turned on the wifi but it stucks at optaining ip address …it connects after 1min but the setting force close alot of times…so i turn off my router but later my phone still wont auto connect to the wifi…and again yhe setting it stucks on optaining ip address and setting force close…it finally connects after like 5 mins…wats the cause? is it kernel related?
[Samsung Galaxy Nexus] franciscofranco:
Been there, done that, and then most users who could run 512Mhz GPU couldn't anymore, so I decided to have extra work and deliver this kernels like this.
[Samsung Galaxy Nexus] franciscofranco:
512mhz and 384mhz use different voltages.

Every frequency that has more than 1300mV is not calibrated by SR yes.
[Samsung Galaxy Nexus] Antob125:
Yes! Please don't change it! We love you!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nuwan32:
Then how come on the under volting menu they're both together

---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------

change the color modes in Franco kernel app. I use:

200

215

280

-2

0

10

Trinity -12

It's really nice, but people say that over 200 isn't good for the screen, so beware
[Samsung Galaxy Nexus] a5pe4:
I don't want to mess up the screen tho lol. I wonder what kind of values the default cm10 kernel has?
[Samsung Galaxy Nexus] 11768:
Thanks for the info. My max is now set to 1305mhz (the last step before 1300mv). :good:
[Samsung Galaxy Nexus] RevengeFNF:
For some time now, in Franco Kernel App, the MPU Voltage alwasy shows 0 mV.

It started to happen after i went to CPU Undervolt, and saved the settings(without changed anything).
[Samsung Galaxy Nexus] franciscofranco:
You're right, I have to fix that, it shows 512/384 but in reality its 307/384 and then 512 with the higher values.

CM has 400/400/400.
[Samsung Galaxy Nexus] Tommy_FIN:
My phone feels a lot smoother with dyninteractive. Gonna keep it for a while. Good work!
[Samsung Galaxy Nexus] jellymelly:
wifi is connected but extremely slow to start downloading, on M5 + aokp JB build 2.

Still the same after upgrade to r268.

Help?

was fine before on stock rom + m5
[Samsung Galaxy Nexus] franciscofranco:
I'll do this as smooth as possible to prevent someone to call me a jackass or smartass for joking with my users:

Scenario 1: Milestone 5 + stock rom = rainbows everywhere, flying unicorns, perfectly stable environment with good Wi-Fi speed.

Scenario 2: Milestone 5 + AOKP Build 2 = Thunders, bad weather, tornados, and not so stable environment with slow Wi-Fi speed.

What do you think changed between the two scenarios? You don't need a major in Rocket Science to figure it out ;)
[Samsung Galaxy Nexus] gm007:
Rom bug.
[Samsung Galaxy Nexus] supernova_00:
I'm pretty sure someone posted a fix for that yesterday.

http://xdaforums.com/showthread.php?t=1894765
[Samsung Galaxy Nexus] Kurre:
And AFAIK, one can't just compare voltages while comparing batterydrains...since in uP world also frequency is needed to taken in to the equation of the power consumption. But anyway this goes little off-topic now.. :rolleyes:

Anyway, as always kernel is running great..close to milestone material, I think :)
[Samsung Galaxy Nexus] boysetsfire:
is this normal? while downloading it always stays at 0%, showing that strange -1B thing... but in the end (actually after a long time, much more than usual) it successfully flash :confused:

btw, r268 great as always, thx franco!!! :laugh:
[Samsung Galaxy Nexus] franciscofranco:
Thats no fix, thats just a post with an explanation of one of Smartreflex internal routines.
[Samsung Galaxy Nexus] yahyoh:
nightly 264 work like charm on cm10 thx franco . i didn't flash 268 yet :p

btw what do u think about add Triggering actions with touch gestures : http://xdaforums.com/showthread.php?t=1831254

:cool:
[Samsung Galaxy Nexus] mssam:
I was curious about that also. Saw the same thing using the app on the n7...
[Samsung Galaxy Nexus] franciscofranco:
Probably a bug in the app when calculating the file size. I'll take a look later today and if needed I'll re-program the download function again.
[Samsung Galaxy Nexus] mpokwsths:
A lot smoother than what? Than static interactive or than previous versions of the kernel? If it is the second you are probably wrong because for a long time now the "interactive" gov has been what "dyninsteractive" is now.
[Samsung Galaxy Nexus] Marcb:
Seriously, I think users running AOKP shouldn't even bother coming here to complain about issues with this kernel... not even close to being reliable...

CM is more or less stable...

Stock is preferable and more reliable to spot kernel issues...
[Samsung Galaxy Nexus] EDNYLaw:
Franco, just wanted to say r268 is running phenomenally well! I'm on a mix of 4G LTE or WIFI(no data) all day with usually 2 hrs or so of screen on time and I end the day somewhere around 50% of my battery left. I'm also running an AOKP variant and my settings are dyninteractive 2xx to 14xx, 7xx max screen off and SR enabled. You've apparently stopped the battery from discharging, great job! Everything in the kernel and the app runs so smooth. Thanks for all your hard work, it's definitely appreciated!
[Samsung Galaxy Nexus] sluflyer06:
Been running AOKP since its inception for this device. Don't know how it could be any more reliable than it currently is. Runs fast, GREAT battery life, no FC, no crashes, no bugs I can find. :confused:
[Samsung Galaxy Nexus] nuwan32:
So is everyone using interactive or dyninteractive? I'm using normal interactive and set my own rates, I think it has been better for the battery so far
[Samsung Galaxy Nexus] Marcb:
but if you ever need to report errors or bugs, it's hard to distinguish between the kernel or the ROM... especially if users are running nightly builds...
[Samsung Galaxy Nexus] Tommy_FIN:
Smoother than static. I forgot to mention that.
[Samsung Galaxy Nexus] qtwrk:
Anyone else has same problem as I have that phone gets extremely hot running r268 ?

You can't believe it, it even heat up to 68 °C when I was just browsing internet which should be about 40 °C usually

GSM, 1.2G weatheley 384GPU , I9250UILE1, AOKP JB B1

...

Back to r264 see if it helps
[Samsung Galaxy Nexus] osm0sis:
Seeing a ton of these errors in the logcats today running dynint:

09-21 12:03:14.166 E/Tuna PowerHAL( 309): Error writing to /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such device

I'm guessing you might have missed one "interactive" that needs to be "dyninteractive" somewhere. ;)
[Samsung Galaxy Nexus] despard:
Did you disable the smrtreflex?
[Samsung Galaxy Nexus] nswenson:
"Quote:

Originally Posted by nswenson

The latest R268 512 GPU appears to be running at 384MHz GPU speed. Perhaps there was a mistake when it was uploaded to the server? I used the Franco app to autoflash it.

How are you measuring this?"

Just use a GPU specific benchmark like Nenamark2. Jelly Bean kernels with a 512MHz GPU will bench at 38fps. 384MHz will bench at 32-33fps. With R268, both the 384 and 512 version bench the same at 33FPS. All other 512 GPU versions have benched at 38.
[Samsung Galaxy Nexus] lippol94:
But it's been there since days! :D

At least since August 30 ;)

https://github.com/franciscofranco/Tuna_JB_pre1/commit/0377a5749eeac729cc209c1b6e239c7be8ca8c28

On my end actually I'm enjoying the stock interactive! It's damn smooth. Is there any reason why, Franco?
[Samsung Galaxy Nexus] nuwan32:
It's actually cooler with 268 for me with the same modem
[Samsung Galaxy Nexus] nswenson:
Very easy fix. Just change the color calibration to the following settings under Franco's Kernel Updater-> ColorControl

Color Multipliers:

red: 135

green: 135

blue: 200

RGB: 0, 0, 0

Trinity Contrast Interface: -10

OMAP4 Gamma: 1.2

These setting will give you the most neutral colors and the whitest whites. It will appear brighter due to the color temps.

Another option, use a rom like CM10 which allows you to tweak the auto brightness levels to your taste.
[Samsung Galaxy Nexus] mixtapes08:
What's the best settings for static interactive governor? Performance and battery life?

Sent from my Nexus Prime™
[Samsung Galaxy Nexus] akash3656:
Franco, I really do not know why but when I try out your kernels from 24* and the latest nightly 268 my WiFi tends to disconnect quite often. I was previously using trinity alpha 60 and Jame bond kernel. They did not exhibit random WiFi disconnections. I have already unchecked avoid poor WiFi connections. I know you reverted back the linux 3.4 WiFi driver but something isn't right for me. Thanks btw things seem smooth other than the WiFi.

Edit: I think its a bit too early for me to comment on it; Franco I'll have to use your kernel longer to make a valid observation.
[Samsung Galaxy Nexus] drawde40599:
I run AOKP and it works flawless and has for months and months its 100% as reliable as stock and Franco kernel and all others I've tried work great . So your wrong;) u should probably try out the ROM be4 talking bad about it
[Samsung Galaxy Nexus] franciscofranco:
Because the Tuna PowerHAL is made to work with stock interactive. I'll have to patch the HAL to work with dyninteractive as well.
[Samsung Galaxy Nexus] sotoskawasaki:
Well, thats not completely true. I am using AOKP Build 2 on my Galaxy Nexus and Nexus 7. On Galaxy Nexus I have no problem/issue at all. In Nexus 7 I had an issue with the screen going black/flickering but it seems the CM10 had that issue too. So I guess there are a lot of factors to take into consideration, the user being the most important.
[Samsung Galaxy Nexus] abjexstallion:
Yup... same here. Only thing I'm noticing is that I'm trying to set a custom power mode, and it says that there is one blank space, that i should fix it. And since 264, I'm not getting that much deep sleep. I'll check my apps, but haven't change anything lately.

Edit: Nevermind... cleared the whole thing and everything back to normal.

Sent from the Best ANdroid ever BUILT using xda premium
[Samsung Galaxy Nexus] Marcb:
Dude, you sound a little butt hurted... It's not my inttention to diminish anybody's work!

When you test something like Franco's kernel, your system has to be the most reliable as posible... and it's not something you'll achieve with nightly builds of CM or AOKP... I' have used AOKP and that's exactly why I said it's not realiable as a "test" ROM for the kernel...

Maybe Franco's kernel works great using stock or Minco's ROM and maybe the developers of AOKP change something that completely breaks something in the kernel.... understand my point? It's not that I don't like AOKP or CM... it's just no as reliable as the stock ROM for testing purposes...
[Samsung Galaxy Nexus] nikulogical:
Never had any issue with aokp/franco either. Then again I only use official builds, not experimental nightlies or unofficial kangs.
[Samsung Galaxy Nexus] J-Hop2o6:
Wow, weird. Wonder why it caused that issue. I know CM has it built-in the ROM now.

Should be around 180, 180, 200 | -4, 0, 5. So start from there, then adjust the red -/+ to your liking. Don't worry about adjusting the blue. Less Red = less warm/tan whites. If greys have a tint of green, ONLY lower the multiplier. The green gamma (below 0) will make the whole UI green for some reason.

:eek: seriously?