yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] EddieN:
I'm guessing the browser performance (scrolling, zooming) is pretty kernel dependent since my browsing has improved by at least 10 fold with francos kernel compared to stock. I'm wondering though, in Sweden we have a news website that we often use as a benchmark of browser performance since it's got so much crap on it. Sometimes the site is buttery smooth in both scrolling and zooming with absolutely NO delay. Yet other times the site is really, really choppy when zooming with several delays and stuttering while scrolling. On different websites I can (albeit rarely) experience the same but most times refreshing the page several times fixes it in the end.

My question is if this differentiating browser performance is kernel or ROM dependent? Like i said before, considering the improvement in browser response and speed after installing francos kernel, I'm guessing it's kernel related.

If anyone would like to test, visit www.aftonbladet.se (swedish news site) and see how your browser performs. I'm getting varying results and I'd just like to know why.

Thanks for an otherwise perfect kernel :)

I'm running Franco 9.2 with AOKP m1
[Samsung Galaxy Nexus] Dr_Ownage:
Is there somewhere i can get all the old Franco Kernel releases?
[Samsung Galaxy Nexus] hkbr:
http://www.world-of-nexus.com/download-section/category/4-franco-kernel
[Samsung Galaxy Nexus] zephiK:
No. But I have them on my computer if you'd like them.
[Samsung Galaxy Nexus] Dr_Ownage:
Thank you :)
[Samsung Galaxy Nexus] just4747:
Are there any known battery drains with the kernel at this point? I've been flashing each nightly for a while now and am not getting particularly good battery life, even with the extended battery. Screen off drain is fine, CPU spy shows fine deep sleep. I'm on latest AOKP btw and have done many clean wipe/installs.

But once the screen is on, at 25% or less brightness, it just drains away like crazy. I watch the percentage drop a number every 1-2 minutes when using no matter what circumstance or settings. I see no apps draining in battery menu or with Better Battery Stats.
[Samsung Galaxy Nexus] franciscofranco:
This screen wastes a huge amount of power...There's not much to be done at that point as of yet.
[Samsung Galaxy Nexus] aleve1983:
With 9.2 there is battery drain! With 7 or 8 no

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] energie:
There id no battery drain, problem is the screen.

Is there any way to undervolt it?
[Samsung Galaxy Nexus] J-Hop2o6:
I guess every panel will differ, because mines isn't "blue", its actually "white" for me. When I first got the phone a few days ago and turned it on, white was really warm. Now I have white at the right color temp (yes, a bit on the cool side). I guess add a bit a red and see how it goes (unless you have your own perfect values). What's your favorite values? Oh and thanks Franco! If it wasn't for your kernel+app, I would've been very irritated with a "warm" screen. HATE WARM screens! lol
[Samsung Galaxy Nexus] jcurtis369:
Milestone 5 is coming soon to galaxy nexus near you :D

Check out his MiNCO rom minooch posted a screenshot of his about phone for the next version of his and franco's rom and it had franco m5 kernel in the pic.
[Samsung Galaxy Nexus] osm0sis:
Rumor has it that there are about 6 variations of screen coloration/defect. So sharing your "perfect" settings you can generally assume they won't work for most other people. That said, share in the open spreadsheet and check out other peoples' color settings in the following thread:

Galaxy Nexus Collaborative Optimal Color Settings

Odds are there is someone else with a screen like yours who has already shared their values. Share yours as well, as the long-term goal/hope/dream of that thread is to hopefully find the 6 "optimal" settings averages for the variations if there seems to be a pattern.
[Samsung Galaxy Nexus] jakiej:
kernel panic

Hi Franco,

Just got a random reboot and a glimpse into the last_kmsg, I saw a kernel panic.

http://dl.dropbox.com/u/13112181/last_kmsg

I am on #241.
[Samsung Galaxy Nexus] J-Hop2o6:
Thx! Will check out and report.
[Samsung Galaxy Nexus] creeve4:
Since updating to the newest version of the app (it may have been an earlier update, but I have noticed it since the latest update), the Trinity Contrast setting is not sticking after a reboot. When the Trinity Contrast setting dialog is opened it shows the last selected setting, but you have to select a different setting and then select the one you want to get it set.

All other color settings are reapplied after a reboot.
[Samsung Galaxy Nexus] nnnnr14:
This is good for me

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] creeve4:
Governor and settings?
[Samsung Galaxy Nexus] nnnnr14:
I just showed that my phone zips without hardly touching my max.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] franciscofranco:
It was a GPU microkernel crash, nothing related to me, it just happens.
[Samsung Galaxy Nexus] BigBake88:
Franco, is M5 coming tonight by chance? I only ask because I was about to flash 241 but if m5 is coming tonight I want to wait to flash it!
[Samsung Galaxy Nexus] franciscofranco:
Nope, its not.
[Samsung Galaxy Nexus] creeve4:
Anyone else?
[Samsung Galaxy Nexus] k_nivesout:
Here's a logcat for the settings FC when selecting "storage". Tried to leave only the relevant section. CM10 jellybro - Toro - R241.
[Samsung Galaxy Nexus] nikulogical:
R241 stock settings, 384gpu, official extended gsm battery.

14hours with 4.5 screen on. 25% remaining.

Franco>>>
[Samsung Galaxy Nexus] whittikins:
Impressive. What brightness? Do you have wifi/BT/syncing/gps/etc on?
[Samsung Galaxy Nexus] nikulogical:
Auto.

Wifi and 3g both on. Using wifi for most of the day, 3g for a bit when I went out. Synching on. bt and gps off.

For those wondering what rom, an aokp nightly from a week ago. No black themes either.
[Samsung Galaxy Nexus] eddie_gordo:
I'm not sure if it is because I've been dirty flashing the AOKP nightlies since I was in the ICS AOKP, but I can never get more than 1 hour and a half of screen on time.. I've tried running the franco kernel on stock settings without any luck.. It's no big deal for me as I can make it through the day, but I just get perplexed at seeing all you guys having 3 and 4 hours of screen on time, it's a huge difference! I have to fully wipe my device to check if that's the problem. :)
[Samsung Galaxy Nexus] Tarun95:
Depends on also what u use. If u play games then the screen time will be less. For me in normal use with slight games I get 3-4 hours and with lot of game play only 2 hours
[Samsung Galaxy Nexus] eddie_gordo:
No games during the day.. I have 3g on all day with syncing, and what I use during the day is SMS, a few calls, instagram, foursquare, twitter, xda developers app, and those kind of apps.. Usually it's just 2 or 3 minutes of screen on, each time.. :)
[Samsung Galaxy Nexus] phishn:
241 is running great here on jbsourcery 1.0 with the exception of the 230mhz slot. It is stable on my device but seems to cause an issue at some point in time where CPU 1 goes offline and never wakes up no matter what settings, forcing it with power modes, etc, are tried. A reboot fixes it. During times of trouble the settings were 230 / 1228 interactive , 729 max screen off.

Edit : its now happening at 384 minimum so something else is going on. Going to try another rom.
[Samsung Galaxy Nexus] jakiej:
thanks so much for checking it out!
[Samsung Galaxy Nexus] creeve4:
Uninstalled the app, cleared data, rebooted, and reinstalled. Still Trinity contrast settings are not being reapplied after a reboot.

Can I get an acknowledgement Franco?
[Samsung Galaxy Nexus] kickthefreak:
R200 compatible with CM9?

Sorry for the question.
[Samsung Galaxy Nexus] 15israellai:
Guys, I'll be getting another GN one or two weeks later. Wish me good luck so that I can get one that can run 1.8GHz + 512MHz :D
[Samsung Galaxy Nexus] The Gingerbread Man:
Use supersu instead of superuser, its been covered tons of times

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] creeve4:
Already using it. If you will notice in my original post, all other settings are reapplied after a reboot, but not Trinity contrast.
[Samsung Galaxy Nexus] arhung:
using r241-512gpu 230/1536 interactive governor, but seems a bit laggy with the 729600 of hispeed_freq, now I change it to 1037000, hope this can fix the laggy.
[Samsung Galaxy Nexus] renna1992:
holy **** ... rom? settings? kernel settings?
[Samsung Galaxy Nexus] nikulogical:
latest nightly 384gpu stock settings. aokp nightly. auto brightness. official gsm extended battery.
[Samsung Galaxy Nexus] J-Hop2o6:
That is why. Nothing to see here. And I didn't mean to +1 you :rolleyes: lol.
[Samsung Galaxy Nexus] nikulogical:
Official extended battery is only 14% larger. So divide the screen on time by 14% and you get 4h50m.

Not impressive?
[Samsung Galaxy Nexus] J-Hop2o6:
Hmm, interesting. I gotta test mine to see how much screen on time I get from 100 to 1 with the stock battery using r241 and AOKP-cm10-nightly.
[Samsung Galaxy Nexus] derPianist:
Will this Kernel work normal & without big problems on MIUI?

Thanks!

via Google Galaxy Nexus
[Samsung Galaxy Nexus] frenchy714:
I've achieved 5 hrs. screen on time with a stock battery and ****ty signal with 241/stock settings/wheatley gov.....It's definitely possible.

Sent from my Galaxy Nexus using Xparent SkyBlue Tapatalk 2
[Samsung Galaxy Nexus] tibere86:
I have never had great battery life with Wheatley...maybe because I listen to about 2 hours of music on weekdays during my commute. Interactive has always worked great for me.
[Samsung Galaxy Nexus] juanzr1:
When will we get 243 milestone 5?
[Samsung Galaxy Nexus] prembox:
Patience mate, Patience!!! This is exactly the kinda question that irritates an otherwise dedicated/focused Dev(s)..... R241 already packs Milestone characteristics so don't hold ya breadth for M5...
[Samsung Galaxy Nexus] velis74:
I'm having some strange issues with UV settings:

My phone seemingly works @600mV up to 700MHz, 650 up to 1.2GHz, above that I have not tried.

However, I have two kinds of problems with that:

1. after flashing the kernel, simply applying these voltages will usually just lock up my phone. I have to go from stock voltages down to 600 in gradual steps. Additionally the lockups occur while switching frequencies. If I set min and max to the same frequency, it will easily work @600mV - even @1.2GHz.

2. when voltages are set manually, the readings in "calibrated voltages" page cease so I have no way of verifying. However, the phone heats up more and has less battery life than smartreflex mode which is applying significantly higher voltages (990@729, 1110@1036)

So moving from 232 to 241 I haven't even bothered reducing the voltages by hand any more and just turned on smartreflex to see how the phone handles that. The result is listed above.

Are my UV settings working at all considering the results I'm getting?

Can I provide any additional info to help identify any issues?

BTW: Thanks for including 230MHz freq. Reminds me of a 233MHz pentium I used to have @ work a few years back :D
[Samsung Galaxy Nexus] djjonastybe:
I have been trying to find datasheets for the lddr2 modules of our phone but can't find any.

All I found is that the Row Latency should be 3T instead of the 6T we have now. I don't know if they are so high because we have 4Gb modules.

As with CAS Latency it raised the bigger the memory modules are.

I wanted to put all my overclocking experience in it.

Franco let me know if you know where to find the voltages for the lddr2 modules. I may be able to undervolt them or overvolt them for extra performance. That way you may be able to add a extra switch in a Kconfig
[Samsung Galaxy Nexus] Tarun95:
I get a feeling that there is something big coming in m5 :D
[Samsung Galaxy Nexus] gautam_nexus:
I don't think there will be a major code change r241 is already so stable

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gaich:
For those who use Poweramp app with latest Franco kernels. I had a bug with Poweramp stuttering when Google music worked well. In this thread I found a lot of similar problems without solving. I tried different settings, roms, kernels etc. So I finally realized - it is not kernel`s fault - Poweramp doesn`t work correctly (stutters) when min CPU is set to 230 MHz. If you set 384, the bug disappears.:cowboy:
[Samsung Galaxy Nexus] Bl4ck3urn:
Good to know!
[Samsung Galaxy Nexus] franciscofranco:
Why would you want to undervolt RAM? Overvolt? You want to burn the transistors? :p

Nop, adding big ****s for a Milestone would be a shoot in my foot ;)
[Samsung Galaxy Nexus] derPianist:
Thank you. Good to know why I wasnt able to listen to my music without problems.

via Google Galaxy Nexus
[Samsung Galaxy Nexus] creeve4:
Why is it that Poweramp played fine on my Samsung Vibrant at 100 MHz, but stutters on the GNex below 384 MHz?
[Samsung Galaxy Nexus] gautam_nexus:
Screen resolution mate

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] olivercervera:
Anyone has tested r241 with one of last CM10 nightlies? Are there any issues like "Storage" FC in CM9?
[Samsung Galaxy Nexus] creeve4:
Yep, still happens
[Samsung Galaxy Nexus] rmcsc:
To use franciscofranco's words, "Sometime between the beginning of time and infinity."
[Samsung Galaxy Nexus] :
+1, for me too.

Sent from my Galaxy Nexus running cm10
[Samsung Galaxy Nexus] TheSobadef:
This is because Poweramp doesn't use hardware decoding for audio playback and instead relies on software decoding. This requires puts more weight on the CPU and is the reason the battery drain is bigger
[Samsung Galaxy Nexus] nuwan32:
wtf.... 600 mV for 1.2Ghz....? that cant be possible.
[Samsung Galaxy Nexus] a5pe4:
What are the default governor control settings? I noticed that my phone is set for 1228 max but doesn't even use over 729. :confused:
[Samsung Galaxy Nexus] a5pe4:
Sorry Xda made me spam during maintenance! my bad!
[Samsung Galaxy Nexus] a5pe4:
Xda made me spam during maintenance :mad:
[Samsung Galaxy Nexus] droid3:
spammer
[Samsung Galaxy Nexus] IAmAN00bie:
It is definitely possible to under volt to 600mV at that frequency.
[Samsung Galaxy Nexus] nnnnr14:
I hope your spamming was an accident. But I have mine over clocked to 1.4 and it hardly touched it unless I'm playing wind up knight. The phone only uses what it needs.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] osm0sis:
Wow, so I removed a few old apps I never use the other day, and I suppose 241 is finally "settling in" like everyone talks about, either way, with light usage, a lot of web browsing, some light gaming, GPS + maps this is what I got. First time I've seen it do this well! Interactive 384/1536/729 screen off, hispeed_freq = 1037000, input_boost = 1, fsync on, bootlogger off. Oh, and standard battery. :D

[Pics removed since I'm closer to 4 hours screen on now ;)]
[Samsung Galaxy Nexus] a5pe4:
Can you tell me what is in your governor control settings please? Or a screenshot
[Samsung Galaxy Nexus] Salv0:
Here too..strange enough without touching any setting, unlike previous versions, I'm having much lag.
[Samsung Galaxy Nexus] zybertooth:
I have this same problem when using Interactive Governor.. Even if hispeed_freq was set to be the same as max freq of 1536.

I switched to Ondemand and I can see the use of higher frequencies.

Hope somebody can share their *working* Interactive Gov Settings..
[Samsung Galaxy Nexus] 5nickers:
is there any adventage using software decoding?
[Samsung Galaxy Nexus] nnnnr14:
I just use interactive but I'm on francos kernel.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] bar_rodoy:
Hey, franco. I have your kernel with minco rom and I bought your app which realy fixed my device screen color. I have a question, might be a noob question, should your kernel work with any JB rom or only with Minco rom? Thanks.
[Samsung Galaxy Nexus] cyberon:
Hi Francisco, can we expect superuser issue fixed on new version or is it a app bug?

I am using cm10 nightlies and have to uninstall it every time.

Thanks in advance.
[Samsung Galaxy Nexus] franciscofranco:
Works on every rom.

What superuser problem?
[Samsung Galaxy Nexus] cyberon:
The one where you can't overclock the phone.

If you reboot it returns to 1.2Ghz
[Samsung Galaxy Nexus] nnnnr14:
That's already been solved. Just use supersu

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] Marcb:
Franco, just one quick question!

Was the bluetooth touched at all in your kernel? Does it differ from stock 4.1.1 kernel?

Thanks man!
[Samsung Galaxy Nexus] garu12:
Any JB rom. Cm 10 roms have little quirks with it but that's it

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

Oups was already answered :/
[Samsung Galaxy Nexus] Marcb:
Ok, I don't really like benchmarks, but on a controlled enviroment, it is helpfull...

I did some tests with my GN and here's what I got...

I'm using the stock 4.1.1 ROM! No changes at all apart from being rooted.

Stock Kernel:

Now, after flashing Franco Kernel r241, 384Mhz... No changes to governor or frequencies!
[Samsung Galaxy Nexus] The Gingerbread Man:
That is probably the most useful benchmark post iv seen, nice one!

Edit

Try with the 512 GPU kernel and post the same series of results

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Marcb:
Thanks!

I'll try to flash the 512 kernel this afternoon and make some tests... I don't really like to push my device to the edge of performance so I think 384 is already the best solution!
[Samsung Galaxy Nexus] Flukester69:
Hi Franco,

Are you planning to build up the Backup/Restore option in your app? I think it's a great option however can I suggest a few things.

- allow more than 1 backup

- index backups by build number (display build)

It would be nice if there was a repository on my phone of your past kernels and the ability to just quickly select one and flash would be so cool.

Noticing some issues lately and I didn't see listed here.

- Sometimes when I flash a ROM and I install Franco it shows options are turned on but they aren't. For example, having franco boot animation is checked however I am currently using the stock rom animation.

- The sound enhancing options (max vol increase and high perf). Don't seem to do anything or the settings are messed up. If those sound enhancers are only for headphones too, maybe it would be great to have it saying as much. I think you told me once those sound options were for headphones only.

- I don't think sleep setting is showing true value either. Many times I've woken my phone and looked immediately at cpu cpy and it says it's running at the min mhz..when I disable it, set it to 384 and then turn it back on to 729 I see I'm in and around 700mhz when I turn it back on.

I assume the above problems are probably related to reading a config/settings file somewhere on my sdcard.

Love your latest kernels, they are running really well.
[Samsung Galaxy Nexus] Hungry Man:
Yeah the sound enhancement stuff doesn't actually seem to do anything/ change the volume at all.
[Samsung Galaxy Nexus] franciscofranco:
The backup/restore feature is already done and deployed on v6.0. You can backup as much as you want, no limits, and you can name your backups whatever you want. They will show the timestamp when they were created as well in the backups list.

Sound improvements work just fine, but only for headphones.

About the small bugs you notice thats helpful, I believe I got some small bugfixing to do, thanks.
[Samsung Galaxy Nexus] franciscofranco:
And here we go, Milestone 5:

* Built from Jelly Bean sources for Jelly Bean roms (kinda obvious duh)

* Custom frequency table from 230Mhz to 1,8Ghz

* All the usual interfaces: sound control, color control, Trinity Contrast, OMAP Gamma interface, fsync toggle, wifi power management toggle, thermal throttle toggle, fast USB toggle, BLX (Battery Life Extender) etc

* Patched up to 3.0.41

* BFQ v4 IO scheduler added, tuned for flash storage devices and made default

* Custom Tuna PowerHAL binary compiled from source to fix frequencies to be reset on screen on/off and other small fixes

* Ondemand and Interactive governors tuned and cleaned

* Compiled with the newer GCC toolchain 4.6.x from Google

* GPU clocked to 384Mhz using the same voltage as 307Mhz

* Lots of other small patches and improvements visible on my repository

http://minooch.com/franciscofranco/... Bean/milestones/franco.Kernel-Milestone5.zip

Current version of the app (6.0) won't load Milestone 5, you have to update to app 6.0.1 (once its available on the Market) to download Milestone 5 from it. If you can't wait just get it from the link above.
[Samsung Galaxy Nexus] J-Hop2o6:
Nice! Downloading now.

EDIT: I just realized. This doesn't OC the GPU (384/512MHz) correct? If not, I can wait for r242 :cool:
[Samsung Galaxy Nexus] franciscofranco:
Its 384mhz GPU because I made 307 and 384 share the same voltage so it ships with the higher clock.
[Samsung Galaxy Nexus] Marcb:
Nice Franco..

Just to clarify, r241 = Milestone 5 or you made additional changes?

thanks man!
[Samsung Galaxy Nexus] J-Hop2o6:
Thx for the quick response :good:
[Samsung Galaxy Nexus] The Gingerbread Man:
Is there going to be a 512 m5?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] derPianist:
Any major changes from 241?

via Google Galaxy Nexus

---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------

+1

via Google Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
For M5 I added 3.0.41.

Nopes.

See the answer above ;)
[Samsung Galaxy Nexus] ledionkoci:
Did you read the changelog guys????
[Samsung Galaxy Nexus] Flukester69:
Cool.

I realize they are for headphones but why not explicitly state that? Would be helpful in general.

Cool.
[Samsung Galaxy Nexus] J-Hop2o6:
Wow, M5 is a bit faster & smoother. Nice work Franco!
[Samsung Galaxy Nexus] Marcb:
Just flashed MS 5! OMG, awesome battery life!!.... Hahaha just kidding!

As smooth as the other ones! Thanks man!
[Samsung Galaxy Nexus] SpecRek9:
On the contrary, I just flashed M5 and I feel it slower than stock kernel :(
[Samsung Galaxy Nexus] duduzinho15:
can i use it on jellybean 4.1 ?
[Samsung Galaxy Nexus] renna1992:
my bad ...
[Samsung Galaxy Nexus] schizophrenia:
but he is asking about the binary flashable zip file..
[Samsung Galaxy Nexus] renna1992:
oh ****. it's too late here.

my bad, i take everything back, sorry man :highfive:
[Samsung Galaxy Nexus] pigr8:
flashed m5, got problems with auto flash from 6.0.1, got it up with manual on cwm..

let's how it runs

ps: franco is there any Kind of tweak for 2000mhA batteries? or it's ok so? i saw some Kind of tutorial for the 2100 on verizon's model, maybe is there something for mauro too..
[Samsung Galaxy Nexus] Admiral2145:
new to this kernel

I just got my vzw gnex a few weeks ago and I see this kernel looks to be the best... Can someone post there stable undervolting for the cpu with this m5 release or for the 241... I'm not new to under volting but, would like a base to start off with.

TIA
[Samsung Galaxy Nexus] c_86:
any milestone 5 512gpu?
[Samsung Galaxy Nexus] derPianist:
via Google Galaxy Nexus
[Samsung Galaxy Nexus] RevengeFNF:
Hello Franco,

In your App, it still says the last kernel is the 241, and not the m5.
[Samsung Galaxy Nexus] pupilov:
Nobody wants to read these days... Geez. How do you put up with them, Franco??
[Samsung Galaxy Nexus] c_86:
download the latest version of the app from play store... then try again... voila
[Samsung Galaxy Nexus] Puzzlegirl:
The difference between nightly and stable is? You have to learn to read ;)
[Samsung Galaxy Nexus] mike216:
Going to crash servers with a milestone release :)
[Samsung Galaxy Nexus] gparmar76:
Even the latest app that was released today doesn't auto flash the milestone...I had to manually flash it in CWM...might be due to server getting a lot of hits, but I thought I'd just say, the auto flash with latest app didn't work.
[Samsung Galaxy Nexus] nnnnr14:
Milestone 5 seems to have solved my frequent data cutoffs... :what:

I got 99 problems but bamf ROMs ain't one! -nnnnr12