yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Puzzlegirl:
I auto flashed via the app - worked perfectly.
[Samsung Galaxy Nexus] SpecRek9:
Can this kernel be tweaked? If so, where is the config.

Thanks
[Samsung Galaxy Nexus] usmankh10:
i have been using ur kernal loving its performance ,just want to share my problem regarding sudden drain after 20% battery remaining ,this pic below shows the situation,help will be appreciated :)
[Samsung Galaxy Nexus] franciscofranco:
What?
[Samsung Galaxy Nexus] Serious_Beans:
If by that you mean adjust the settings get the Franco.kernel updater app

That's not unusual...at least not for me...at around 25% my battery just hits the floor...these batteries don't hold a good charge at lower battery levels.
[Samsung Galaxy Nexus] BigBake88:
yes it can be. It can be tweaked via Franco kernel app or through the termulator via commands he has listed in OP.
[Samsung Galaxy Nexus] fredryk:
I flashed this kernel and my screen seems a lot darker than before. What gives?

Running jb aokp 8/19 nightly
[Samsung Galaxy Nexus] derPianist:
That is the Trinity Contrast Interface.

I love it.

Adjust in the App

via Google Galaxy Nexus
[Samsung Galaxy Nexus] billykxda:
Thanks Franco! Elegant app - autoflash is awesome. It's a must-have purchase IMO.

Looking forward to seeing performance over the next few days on my GNex.
[Samsung Galaxy Nexus] electronixgimp:
love your kernal franco just flashed it bout 2 hours ago just wondering i use lookout and it keeps crashing and restaring im on stock 4.1.1 rom and your milestone5 kernal any help would be appricated
[Samsung Galaxy Nexus] CADude:
That's your screen being tweaked by the kernel to default settings that fix the screen's accuracy issues. Just let your eyes adjust to the change. You can tweak it with the app as well.
[Samsung Galaxy Nexus] Serious_Beans:
Try flashing the stock kernel and don't forget to wipe cache and dalvik and try again.
[Samsung Galaxy Nexus] derPianist:
Uhm, dont worry!

This Kernel will Rock ya Nexus. :thumbup:

via Google Galaxy Nexus
[Samsung Galaxy Nexus] thegtfusion:
Milestone 5 is flying franco! its even faster than r241! :D. I am using deadline/ondemand. hopefully the battery life is even better than r241 too :D
[Samsung Galaxy Nexus] electronixgimp:
thanks sir just did it no probs so far :good:
[Samsung Galaxy Nexus] sway40:
Guess im in the minority here, flashed m5 and it borked my phone, wouldn't boot past Google. I went and cleared cache and still nothing, had to restore. I never have issues but did this time, flashed from app.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thegtfusion:
Only wipe dalvik cache. Wipe the dalvik cache and install the zip. Then reboot
[Samsung Galaxy Nexus] mikeandjaimie:
Just flashed m5 through app, no problem and it downloaded super fast.
[Samsung Galaxy Nexus] sway40:
Ok I got it by just downloading it in the app and flashing it manually, don't know what went wrong but all good now. I wasn't worried, just funny bc im always the one saying worked fine on mine maybe you did something.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
I agree! It does seem even faster. But just curious, why do you prefer deadline?
[Samsung Galaxy Nexus] SpecRek9:
Thanks a lot, this is exactly what I meant.
[Samsung Galaxy Nexus] nikulogical:
Bfq is still the recommended scheduler for interactive.. Correct?
[Samsung Galaxy Nexus] franciscofranco:
In my opinion and type of usage - yes.
[Samsung Galaxy Nexus] 15israellai:
Hmm, it's been a while since I last used 384...I'm so used to 512 that I don't know whether there's any difference :p

Blazing on my Nexus Prime
[Samsung Galaxy Nexus] nnnnr14:
Your username is bawwwsss!!

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] joeyfong:
Will the kernel information display correctly in cm10? Thanks.
[Samsung Galaxy Nexus] franciscofranco:
No idea, I don't use that rom.
[Samsung Galaxy Nexus] kuntau:
What ROM you use then? Curious
[Samsung Galaxy Nexus] bhowanidin:
@kuntau

Probably Minco.

@Franco

Just wondering, as I know usage varies user to user... What's your set-up with this kernel (GPU @ 384/512, governor, scheduler, etc.)?
[Samsung Galaxy Nexus] franciscofranco:
MiNCO.

The kernel defaults is always exactly how I have my phone set up, but I use 512 GPU.
[Samsung Galaxy Nexus] Serious_Beans:
3g and 8hrs of airplane mode. Not bad at all. :D
[Samsung Galaxy Nexus] Wynnded:
No problems. :cool:
[Samsung Galaxy Nexus] J-Hop2o6:
Milestone 5 = 3.5 hrs of screen on time with moderate usage (texting, some web browsing, little bit of [Tegra 3 enabled Ultra GFX] Dead Trigger, little bit of phone calls, all day wifi, little bit of BT + car audio). Lasted me my whole work shift (10 hrs) + some at home time. Not bad (10am - 8pm). I can get up to 4hrs with lighter usage screen on time. NOTE: Screen brightness is never under 50%

EDIT: You guys really need to use http://tinypic.com to resize your screenshots for message boards.
[Samsung Galaxy Nexus] osm0sis:
or convert to jpg so the attachment will automatically get thumbnailed in the post.
[Samsung Galaxy Nexus] J-Hop2o6:
PNG looks MUCH better
[Samsung Galaxy Nexus] yumeul:
Milestone 5 even smoother than r41 !

thanks Franco :D
[Samsung Galaxy Nexus] SpecRek9:
Hi mates, I made this two changes[0] but I can't perceive the volume_boost nor the highperf, what is the purpose to this commendas and/or how can I measure the results? I tried playng some music and the max volume is the same as before installing Milestone 5.

[0]

Sound Control:

echo 3 > /sys/devices/virtual/misc/soundcontrol/volume_boost

Sound High Performance:

echo 1 > /sys/devices/virtual/misc/soundcontrol/highperf_enabled - to enable
[Samsung Galaxy Nexus] anoraknophobia:
When i only set the boost to 3 then the sound gets louder. When i enable High Performance Sound then the soundlevel is back to normal again.

Dunno if its a bug or working as intended. I have this poblems basicly since the option is available in every nightly so far.
[Samsung Galaxy Nexus] mike216:
Francos M5 or 241 and CNA 3.3.1 will make you smack your black berry using boss or friends! :beer:
[Samsung Galaxy Nexus] zammbi:
Has anyone else having issues where you connect to your wifi and it crashes your phone(the whole android OS)?

I have been having these issues since I've moved on to Jellybean and on this kernal ages back. Usually I will reflash the kernel again and it will last a couple or so days without crashing the phone then it will just randomly do it and continue to do it(crash loop) until I reflash again. I have been late to work(no alarm) because this! :eek:

Currently I have just turned off the wifi. But I rather not have 3g always on :S

I was hoping the latest stable version was going to fix it but nope.

I have tried reinstalling the rom, reflashing the default kernal and back again. But nothing seems to help. Should I post the android logs?
[Samsung Galaxy Nexus] schizophrenia:
this sounds a bit odd but i have never had such problem.

unlikely franco's problem

been on franco and AOKP JB
[Samsung Galaxy Nexus] Salv0:
Uhm maybe stupid question but where can I change the scheduler?

I feel the device a little bit slower with m5, the options are all default :/

Can someone suggest a good setup?
[Samsung Galaxy Nexus] gaich:
Or use some service like imageshack, as in my signature.
[Samsung Galaxy Nexus] rmcsc:
This + MiNCO = glory.
[Samsung Galaxy Nexus] djjonastybe:
Mr Franco

I have a patch for you that's better than your current workaround:

Undo these patches/commits

https://github.com/franciscofranco/Tuna_JB_pre1/commit/5348be72b2a651ba2de1c9ea6560bfd2ad99ae12

https://github.com/franciscofranco/Tuna_JB_pre1/commit/d641cc4066f27c0ad945f6bff70ccfa5b5e365e8

https://github.com/franciscofranco/Tuna_JB_pre1/commit/9a043fd8e100a4a705df0d71591066ba88b58712

Now:

Open opp4xxx_data.c

Change to

When applying null this will be skipped. Because it won't be able to retrieve valid values and it will retrieve null. In this case this calibration value will be skipped. What you also could do it applying directly the voltages you defined and entering it here in the table. But I believe null is better for readability and consistency.

If you still want to have Smartreflex influencing the voltages if you have a good sample of a Cortex A9 you could try this:

Let me know if you are interested in using this. I have tested it and seems to be working but not for 100% I need to fix something in the smartreflex file.
[Samsung Galaxy Nexus] jtag PH:
Franco performance + Trinity colors.

TAKE MY MONEY!
[Samsung Galaxy Nexus] J-Hop2o6:
What do you guys think of my battery life using m5?
[Samsung Galaxy Nexus] nnnnr14:
Well even for using WiFi I thinks that'd not good. Maybe you just flashed and didn't give the kernel time to settle. But I get 13+ hrs on scrictly 4g

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] Marcb:
New benchmark results for the benchmark junkies!

Just a reminder of the last one:

All done with Stock 4.1.1 ROM!

Stock Kernel:

Franco Kernel r241, 384Mhz... No changes to governor or frequencies!

Now, the new Milestone 5 kernel:

Looking better than ever!
[Samsung Galaxy Nexus] billykxda:
I was unhappy with the battery life of the stock kernels used with Vicious and Bugless Beast. Last week I purchased Franco's app and flashed 241 on BB and battery life instantly improved to the level I was accustomed to with stock ICS on my GNex. Battery lasts 14+ hours with moderate use throughout the day.

I flashed M5 last night (Monday) and battery life is not as good idling overnight, but I know to let it settle for a few days. I am also aware that kernels react differently across handsets, so I'll hang with M5 for a few more days as I am sure Franco has a winner here. If not, I backed-up the 241 build and will happily go back to it.
[Samsung Galaxy Nexus] franciscofranco:
Interesting approach. When you say it doesn't work 100% what do you mean exactly?
[Samsung Galaxy Nexus] fredryk:
What accuracy issues? It looks so dull now. I don't remember the Franco ICS kernels doing this.
[Samsung Galaxy Nexus] osm0sis:
Everyone's screens are different, it's less dull than the defaults on the majority of people's devices. Search the collaborative color thread for an open spreadsheet full of settings you can try.
[Samsung Galaxy Nexus] arhung:
Have anyone change to Milestone 5 from r241-gpu512? Is it worth to flash Milestone 5?thx a lot!!
[Samsung Galaxy Nexus] zammbi:
Franciscofranco any idea on my wifi OS crash?
[Samsung Galaxy Nexus] TEK112:
I had the same thing happen last night switching to Jelly Belly. It is the first time it happened to me. I rebooted into recovery and wiped cache and dalvik and it stopped rebooting when trying to connect to WiFi.
[Samsung Galaxy Nexus] franciscofranco:
Never seen that happen and its the first time I see it reported, so I guess its just a random ****.
[Samsung Galaxy Nexus] glennv17:
Franco, I know from a few pages back that you've addressed the issue of the bung download/boot where it hangs, but I was just wondering (and I may have missed/forgotten a changelog somewhere) if you'd done anything in particular to change the auto-flash procedure? Before, it would just reboot automatically and now I always have to click Yes - BRING IT ON. Is it something with Jelly Bean that is required now?
[Samsung Galaxy Nexus] SpecRek9:
Hi Franco, can you give us a hand here, I tried reseting values from a command line and setting them up again and couldn't feel the changes.

Thanks in advance
[Samsung Galaxy Nexus] cyanoviper:
i just autoflashed m5 and my phone seems to just dont do anything at all anymore

woohsa... all-clear, sorry i was afraid it was bricked. leaving out the battery for a couple of minutes did the trick
[Samsung Galaxy Nexus] mikeandjaimie:
He added this as a new feature for people who don't want/need the auto reboot. Sometimes flashing the new kernel isn't the last thing you need to do before a reboot :D also gives you a chance to change your mind if you flash the wrong version and want to change before you reboot with a kernel your phone can't handle.
[Samsung Galaxy Nexus] J-Hop2o6:
You are correct, that was the first cycle, so yea it needs to adjust/settle. But take note I was kinda pounding my battery with high brightness, heavy gaming, etc. Testing again right now at work with wifi on the whole time + steaming music thru the phone speaker w/ screen on the whole time @ 50%. Going good so far (about -20% / hr).

I did. m5 is really nice tho (even @ 384MHz). But I am waiting for r242 so i can test out 512MHz and compare 512 to 384.

No wifi issues here neither using EuroSkank JellyBro rom [CM10 Nightly].
[Samsung Galaxy Nexus] franciscofranco:
Exactly.
[Samsung Galaxy Nexus] sluflyer06:
Not sure if I'm the only one but USB fast charge has never worked on any release of the Jelly Bean kernel, worked perfectly on ICS.
[Samsung Galaxy Nexus] ssCISengineer:
No it works fine. There must be something wrong on your end.
[Samsung Galaxy Nexus] joeyfong:
m5 is already #243
[Samsung Galaxy Nexus] osm0sis:
M5 is technically r243 according to Settings > About Phone. So I guess we'll be waiting for 244 at the least to try 512 again. :)

Edit: Whoops, I see joeyfong beat me to it. ;)
[Samsung Galaxy Nexus] supernova_00:
Now if only they'd release the ROM for CDMA devices :fingers-crossed:
[Samsung Galaxy Nexus] djjonastybe:
franco how did you fix the bootloops mentioned in the very first posts of your thread ?

Some of my users are having the same issues. I never had them

My zip file extracts the boot.img, puts my zImage file in it, repacks the boot.img and then flashes the whole thing.

But for some reason some people are having these boot loops probably due to some mods in the boot.img file.

I am using CM10 right now.

As long as it's working here I'm glad. But I want to satisfy those few people as well.

I am currently working on smartreflex making it better and more flexible
[Samsung Galaxy Nexus] franciscofranco:
Are you using BFQ v4?
[Samsung Galaxy Nexus] djjonastybe:
No. Most things in my kernel are still stock. Then few mods from Ezekeel

This is my page

http://xdaforums.com/showthread.php?t=1823600

github is slightly outdated. I started from scratch again.

But it's pretty much all the same. But I think you had the same problems during your first days in the GN forums
[Samsung Galaxy Nexus] tFrost:
This rom just gives me the perfect battery life, I do not use my phone to play games, just text/call/surf basically.

I use the following setup:

cpu 1036/230MHz screen off: 384MHz

Rest is default, because I believe franco is better at setting the right parameters than me ;)

Just though I'd share, if you got any comments or improvements please say.

Btw I think the boot animation is just awesome!
[Samsung Galaxy Nexus] J-Hop2o6:
You know what I meant. But yes, can't wait for r244.

m5 2nd cycle: So far so good with the 2nd cycle using m5. Looks like I will get well over 3.5 hrs (screen on) for my second attempt with moderate usage @ 50% brightness. Will post my final results when at 1% w/ screenshots.
[Samsung Galaxy Nexus] GeekMcLeod:
I don't keep up with this kernel nearly as much as I used to but, any plan adding vibration strength? I used it with Trinity and really liked lowering the strength of it a bit.

GSM Galaxy Nexus -- ParanoidAndroid 1.9.91 -- franco.Kernel M5
[Samsung Galaxy Nexus] nnnnr14:
I think there's a tweak for that in the franco kernel updater app.
[Samsung Galaxy Nexus] GeekMcLeod:
I own the app but I use the Trickster mod, it shows options available. When flashing M5 from Trinity Stable35, the vibration strength option goes away. And francos kernel app, as far as I know, has never had a vibration strength option.

GSM Galaxy Nexus -- ParanoidAndroid 1.9.91 -- franco.Kernel M5
[Samsung Galaxy Nexus] ivan08v:
I'm the only one having trouble with volumen boost with M5?

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] yellowdie:
Hey, I read the faq in post 2, I searched the thread and searched the Googles--no joy. What's the terminal command to turn the logger off? The app has the option, but I can't find the manual switch. Thanks!
[Samsung Galaxy Nexus] nnnnr14:
Are you using superuser or supersu?

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] The Gingerbread Man:
Only works for headphones....

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nnnnr14:
It also works with the loud speaker.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] nikulogical:
Freeze and reboot while updating apps in play store. Milestone 5. First time something like this has happened on jelly bean.
[Samsung Galaxy Nexus] ivan08v:
I knowk it works only on headphones, i use it since it was released..i use superSU on Minco ROM when i select 3 the volume goes so much quiet

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] dominatore22:
Absolutely best kernel ever. Milestone 5 is awesome!!!! The only thing that you can do (mr.franco) it's making the battery a little bit longer than now. Now it s not bad but i think you can improve more than this ;) And i have no problem with sound boost. Sometimes i think that now volume is too high :D so i set it to 6 and not 7 :p very good work
[Samsung Galaxy Nexus] J-Hop2o6:
Milestone 5 Battery Life (2nd cycle): I'm sure this was expected, but I got longer screen on time than the 1st cycle. 1st cycle I got 3.5 hrs of screen on time. Now for the 2nd cycle, I got 4.5 hrs. Big improvement. This is with moderately heavy use (50% brightness, Wifi, lots of online streaming music w/ screen on, texting, a few games, web browsing, etc.). Screenshots below:
[Samsung Galaxy Nexus] leets4uc3:
Nice! What are your setting?!
[Samsung Galaxy Nexus] Guiding.God:
That's pretty good - I just got M5 and flashed it over AndroidMe, (had Trinity on CNA before but didn't play around with settings there much, it seemed ok by default) Not very adept with kernel settings and was a little confused with so many options available so have been reading about fsync and governers and schedulers and whatnot lol What settings do U have?
[Samsung Galaxy Nexus] glennv17:
Makes sense! I figured it was something added in purpose because of the way it was worded, but I wasn't sure if it was the reason for some of the hangs I'd been getting when the kernel was downloading and obviously then the flashing bug from 240 or whichever it was. Thanks guys.
[Samsung Galaxy Nexus] J-Hop2o6:
What kind of settings? Here a quick look:

CPU = Ondemand @ 386-1.5GHz

GPU = 384MHz

Brightness = 50%

Default OTB voltage

What else do u guys need?
[Samsung Galaxy Nexus] Guiding.God:
Thanks for that - tweaking this with Trickster - You've left all the other stuff like fsync, scheduler(BFQ/SIO), buffer size, reflex control etc on default settings?
[Samsung Galaxy Nexus] bradm23:
I agree. I'm getting a lot better performance with 9.2, but battery has gotten worst comparing it to 8
[Samsung Galaxy Nexus] franciscofranco:
It's running fine for me. But I'll check some things in hope to make it even better for #10, which is already looking awesome.
[Samsung Galaxy Nexus] just4747:
K thanks man. Yeah loving everything about this kernel thus far, just wishing I had better battery life (whether the kernel is affecting mine negatively or not). The weird part is, same settings but on an older version of the kernel and older version of AOKP, I was getting about 23 hrs of extended battery life for two days before the ROM was updated again.

Not sure what the cause was that it changed but it seems like it has a different drain for no reason between flashes. These things are so picky and different from one device to another, it's crazy.

Also, is the camera open and close thing still necessary for deep sleep to work that you know of? Or is that long gone now?
[Samsung Galaxy Nexus] Dr_Ownage:
Is anyone here running the latest PRIME bootloader? i think its PRIMEKL01?
[Samsung Galaxy Nexus] yyz71:
Sweet kernel
[Samsung Galaxy Nexus] RVDigital:
I got bored and grew tired of people pimping Kernels with no solid data to back them up. While my method is far from scientific, its better than saying one is better than the other just because. I do realize the two kernels that are utilized in this test are a day or two aprat in development, and a re-test using similarly current Kernels will be performed. Feedback on the report would be appreciated, if any.

View attachment 844333
[Samsung Galaxy Nexus] Trevorhimself:
Great Job, looks awesome!
[Samsung Galaxy Nexus] apsis:
Very nice test.and also very interesting. How did you do it? any chance you could compare franco's newest kernel with franco 8? Cause a few people reported better battery life on franco 8.

Best regards
[Samsung Galaxy Nexus] RVDigital:
I'd love to, but will have to do it tomorrow. Can you link me to #8?

Also, I'll be posting more detail around my test methods as I'd love to get some feedback.
[Samsung Galaxy Nexus] mrfuzzie23:
Franco not sure if this is a Kernel problem or ROM issue but I figured I'd ask.

if I download a file to my phone and then plug my phone into the computer..the computer shows the files on the phone but will not show the files I just downloaded unless I reboot the phone first....anyone else have this issue?

also using your kernel updater tool I set overclock to 1350 and enable hot plug but upon reboot the values go back to stock.... would that mean my ROM I'm using doesn't have init.d support? (using rootzboat 6.1). if I go to system/etc/init.d the two files for overclock and hot plug are there....

anyone else have similar issues?
[Samsung Galaxy Nexus] mjchung:
Holy Christ, you weren't kidding. That site is hideous. But my browser handles it just fine every time, with the occasional hiccup.

Check your background processes, perhaps? I know that Soundhound doesn't close properly (had it running all day by mistake, ate up something like 17% of my battery).

9.2 + Bigxie 6
[Samsung Galaxy Nexus] jknisley:
Stupid question, but did you do anything special to get that sort of battery life out of the LTE GNex? I get about ten hours of standby less, and am still in deep sleep most of the time.
[Samsung Galaxy Nexus] drawde40599:
Update the app from market, seen something in change log . But my OC setting r not staying after reboot I did hit OK
[Samsung Galaxy Nexus] Nebucatnetzer:
Not yet but I can test it on the weekend.

Do you suggest any specific method?

For example run the kernel unchanged vs locked at 350 - 700 Mhz and then just use it like normal?
[Samsung Galaxy Nexus] mrfuzzie23:
actually my hot plug settings stick its just OC that doesn't
[Samsung Galaxy Nexus] EchoVelocity:
Does this kernel support loop devices?
[Samsung Galaxy Nexus] just4747:
Well no, that's my point really, is that I randomly got that kind of life on Xmas Eve and the day before or after, but then one ROM and/or kernel update later (forget if I wiped or not that time), the battery life was gone and ever since, I've been back down to less than 12 hrs on moderate use (usually lower, like 8-10 hrs, and this is after tweaking settings, wiping and reflashing rom/kernel, checking battery and cpu apps, calibrating battery, etc...). And again, it kills me every time I have the screen on using my phone, I can watch the battery percentage drop a number every 1-2 minutes, no matter what I'm doing. It's depressing really, esp on an extended battery. I just want longer life..
[Samsung Galaxy Nexus] drawde40599:
oh sorry didn't read right, ya my setting don't stick either I went back to cpumaster ,I'm sure Franco app fixed soon
[Samsung Galaxy Nexus] Vangelis13:
What could theoretically be done with the screen..?
[Samsung Galaxy Nexus] definator:
this night i was watching the battery state being 50% at 12pm

this morning i woke up at 8.30am with 48%

for me, this is not a huge drain. its great

running 9.1
[Samsung Galaxy Nexus] J-Hop2o6:
Franco's app doesn't have options (that I see) to change settings for scheduler, buffer size, reflex control, etc. So yea, pretty much the default stuff. But I do have fsync on, and Wifi PM_FAST on.
[Samsung Galaxy Nexus] Guiding.God:
TY, let's see if I can get upto an hour more out of this after a few cycles :fingers-crossed: