yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mocsab:
Awesome and thanks - I found you in the other thread adn flashed your kernel and downloaded the updater ap from market - REALLY COOL stuff - thanks for your efforts.
[Samsung Galaxy Nexus] bigrushdog:
I cook kernels all the time. And I gotta tell you bro, your kernel and market app together is just epic man. Nightly Eos + Nightly Franco kernel = epic winning.
[Samsung Galaxy Nexus] Redneck Trash:
Can't believe the difference going from stock to milestone 3. Fast, smooth and the increase in battery life is huge. Great kernel and thanks for the work you put into this.

Sent from my Galaxy Nexus using Xparent Red Tapatalk 2
[Samsung Galaxy Nexus] shrumhead:
Flashed from stock last night and I'm not noticing quite the difference others seem to be in "smoothness" and battery-life. I do have the Franco app... which governor are yall using? SR/GH settings? Undervolts?
[Samsung Galaxy Nexus] Redneck Trash:
I'm using lazy governor and generic hotplug. That's made a huge difference for me with screen off. Not as big a difference screen on but we're pushing a lot of pixels on this screen. How was battery life and smoothness for you on stock? On stock my battery life was absolutely horrible even by my ridiculously heavy usage standards. It was pretty smooth on stock for me but smoother with Franco.

Sent from my Galaxy Nexus using Xparent Red Tapatalk 2
[Samsung Galaxy Nexus] shakuyi:
what governor do you have it set to?
[Samsung Galaxy Nexus] Swede2008:
I'm using the conservative governor. Would it be better to use the generic hot plug option or use a profile to switch to the hotplug governor?

Sent from my Galaxy Nexus (Sprint)! :-D
[Samsung Galaxy Nexus] Redneck Trash:
If you use the hotplug option you'll still be able to use the conservative governor with the screen off on one core. Use a profile if you want to change governors based on screen on/off. Just don't use the hotplug option with the hotplug governor.

Sent from my Galaxy Nexus using Xparent Red Tapatalk 2
[Samsung Galaxy Nexus] CruzECO13:
Give it a few days to notice difference in battery life. Yesterday, battery was pretty much same as stock for me. Today, it's much better. And as the days go by, it will get even better. I left the governor on Interactive, brought the CPU down to 1228MHz, use the Generic Hotplug and turned Logger off. That's my setup for now.
[Samsung Galaxy Nexus] Swede2008:
Is the "Battery Life eXtender" in the app similar to SBC? As in I can set it to 100 to get a full battery charge? I used SBC on my og evo for about 9 months with no issues so I'm thinking about putting the setting at 100.
[Samsung Galaxy Nexus] jesusice:
It's more like the opposite of SBC. Having your battery fully charged can reduce its life so BLX gives you the option of having it stop charging at a certain point to extend overall life of your battery.
[Samsung Galaxy Nexus] CruzECO13:
On stock kernel w/ a screentime of about 2hrs I was getting 4-5hrs of battery life.

Day 1 on Milestone3 w/ about 2hrs screentime:

Battery life is improving already =]
[Samsung Galaxy Nexus] snoopy1e11:
I'm running Twisted AOSP it seems most ppl who can't get it to boot are running AOKP. I flashed nightly 180 right over Milestone 4 only wiped dalvic cache. Maybe because AOKP 38 comes with the cm9 kernel as stock could be the reason as I heard some of cm9's features or whatever don't play nice
[Samsung Galaxy Nexus] MichaelMcEntire:
I'm running miui. No boot either.
[Samsung Galaxy Nexus] BenMGP:
BAMF Paradigm 1.25

Still running good for me. Flashed it via Franco app around this time yesterday.
[Samsung Galaxy Nexus] malibu_23:
Is auto brightness primarily controlled by the from itself or the me kernel? I ask this because I've flashed a few roms and the I'm currently settled on the codename android rc-2.0.

Love it but the auto brightness stinks. It seems to pop bright and pop dim at the most random of times. Maybe stock did this as well but since it gradually fades bright or dim its not very noticeable.

Currently on a Franco kernel variant milestone 3.08 that came with the rom. I even played with the auto brightness settings and values in the interface settings. But still get random changes in brightness that are annoying. Popping bright and popping low.

My question is how can I fix this? Any patches I'm overlooking? I've done a day of research and found hints of fixes but no links to them. Any one recommend a better kernel? Maybe just switch roms? Or just use the static brightness settings?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ifly4vamerica:
http://xdaforums.com/showthread.php?t=1635032

That thread might help. You can change the values so you don't get as abrupt a change.

GN Sent
[Samsung Galaxy Nexus] peabody42:
Any idea if compass fix will be incorporated?

http://xdaforums.com/showpost.php?p=27033045&postcount=564

CM9 fixes, flashing this kernel breaks it again.
[Samsung Galaxy Nexus] pastert33:
Can you link me to the BAMF sprint rom?
[Samsung Galaxy Nexus] FL0OD:
New to the gnex thing. Is there anyway to make the color adjustments stick? Nice to be back with Franco. Thanks for anyone's help in advance.

†††
[Samsung Galaxy Nexus] myepicyear:
I think they possibly stick on some ROMs, but not others. People using various ROMs have reported that colors don't stick after reboot. I bought Franco's updater app a little over a month ago, and in the time I've been using it, I've been running CM9 nightlies pretty much exclusively, so I'm a bit unsure about its compatibility with other ROMs. However, I do know that the colors have never stuck for me before, on any version of the app or kernel. Even after an app update that was supposed to make the colors stick, it hasn't changed. So that rules out CM9...

Has anyone ever had their color changes stick before , and if so, how recently, and what ROM were you using?
[Samsung Galaxy Nexus] mattallica76:
I have had the color changes stick on stock rooted with franco kernel, but never on cm9 with franco.
[Samsung Galaxy Nexus] emd2009:
Still won't boot on aokp b38
[Samsung Galaxy Nexus] Bradart:
Thanks. I thought I was the only one.
[Samsung Galaxy Nexus] Mele:
Milestone 4 boots on CM9
[Samsung Galaxy Nexus] funnief13:
Still no boot on 181!!! :mad:
[Samsung Galaxy Nexus] Somairotevoli:
Boots for me with paranoid rom. Very stable too at Max.

Sent from my Galaxy Nexus using Xparent ICS Blue Tapatalk 2
[Samsung Galaxy Nexus] MichaelMcEntire:
No boot here.
[Samsung Galaxy Nexus] duffkitty:
180 didn't boot on 6-5 CM9 nightly. I know it's not supported =P just sayin'.

Been thinking about going back to stock soon anyways with just a custom kernel.
[Samsung Galaxy Nexus] Sodikop:
Milestone 4 working great, still no boot on 181. Running stock ROM.
[Samsung Galaxy Nexus] JoshM813:
180 and 181 had both booted just fine on rooted stock rom
[Samsung Galaxy Nexus] ptfdmedic:
I don't boot on 180 or 181 either. AKOP 38
[Samsung Galaxy Nexus] maddoggin:
Man I can leterally see my battery drainning on milestone 4 kernel . Big time! Just normal use!
[Samsung Galaxy Nexus] dschoenike:
same here. I'm thinking I had an app not playing nice or something. as fast as the battery drained, the temp went up, with no usage. gonna try again with a different rom.

dschoenike
[Samsung Galaxy Nexus] auradefect:
I also can't boot on the last two nightlies. I'm running the newest version of BlackIce Rom.
[Samsung Galaxy Nexus] emd2009:
Just stay with milestone 4.
[Samsung Galaxy Nexus] jwischka:
Throwing in another vote for not being able to boot 180 or 181 on stock.
[Samsung Galaxy Nexus] dorkdotcom74:
+ 1 no boot on nightly

+ 1 battery drain on mile4
[Samsung Galaxy Nexus] emd2009:
Looks like op has abandoned toroplus
[Samsung Galaxy Nexus] mattallica76:
What do you mean? Is he releasing nightlies for other variants that we are not getting?
[Samsung Galaxy Nexus] emd2009:
No but there is a known boot issue with the latest two nightlies and he hasn't been active in this particular thread.
[Samsung Galaxy Nexus] myepicyear:
That's ridiculous. Putting aside the fact that all variants are easy enough to support with one kernel..you shouldn't make announcements on behalf of someone unless they personally gave you that information. He will work it out. I'm sure he's aware.
[Samsung Galaxy Nexus] mattallica76:
He never posts in this thread other than to announce new nightlies. He may not respond to individual posts, but he does read them. Just be patient. I'm sure he will get things fixed up.
[Samsung Galaxy Nexus] peabody42:
This guy is one of the hardest working people around. Look at the history of what he's contributed to the community, and the sheer number of updates he puts up, indicative of his work.

If he's taking a break (which I doubt he is, because he seems to work on this all the time), he deserves it. Cut him some slack at the very least, or do what I did and support him by buying his app.
[Samsung Galaxy Nexus] ifly4vamerica:
Besides these are nightlies, they are always used at risk, that's why they are nightlies so that he can get feedback on the new features. If you are woried just flash milestone 4 which after all IS the latest STABLE release.
[Samsung Galaxy Nexus] nsolo1717:
This guy makes sense. Listen to him
[Samsung Galaxy Nexus] franciscofranco:
I'm aware of everything, but I don't post in Verizon/Sprint threads. I'm only one and I don't have time to post everywhere.

It's so easy to blame the developer where only TWO users sent me dmesg logs on this boot issue... Think about it.
[Samsung Galaxy Nexus] auradefect:
I don't blame you at all but I am still not booting with newest nightly. I'd like to help, can you or anyone else instruct me how to send my dmesg logs? Or anything else I can send to help with this issue?
[Samsung Galaxy Nexus] emd2009:
I'm sorry man I made a mistake. Please accept my apology. Keep up the great work!
[Samsung Galaxy Nexus] SeauxCrazy:
185 is a no go for me also, same issue as 180/181. I'd love to help out also, just not sure how to create the log you need.
[Samsung Galaxy Nexus] jbloggs2008:
Same here - no boot since 180. How do submit logs? I always update latest CM nightlies and franco kernel at the same time so the bug also affects every CM build since 180 was released.
[Samsung Galaxy Nexus] auradefect:
Are dmesg logs the same as logcat logs?
[Samsung Galaxy Nexus] Reno Skyy:
Can't boot either sence 180 :-(

Sent From The Best Android Phone The Galaxy Nexus Using Tapatalk 2
[Samsung Galaxy Nexus] myepicyear:
Everyone that cannot boot with the last 3 nightlies

-What ROM do you use? (AOSP, CM9, AOKP, Gummy, MIUI, etc..)

-If not Toroplus, what carrier variant do you use?

-Is there any other info about your setup, that you think might be relevant to this problem?

Okay..lets start narrowing down.. I know some had success with these nightlies. What are they doing right?
[Samsung Galaxy Nexus] mookiejr05:
im on cm9 nightly 6/6/12

toroplus

only thing i can possibly think is that i have it undervolted by -50 on 192mhz , 384mhz, and 729mhz.

that is the only tweak that i have coming from milestone 4
[Samsung Galaxy Nexus] maddoggin:
Can't boot either since 180. Using cm9 ROM
[Samsung Galaxy Nexus] FL0OD:
+whatever can't boot past google lock:o

†††
[Samsung Galaxy Nexus] dschoenike:
wont boot for me, stock, unlocked and rooted.

dschoenike
[Samsung Galaxy Nexus] dorkdotcom74:
Straight CM9.(with fanco kernel when it boots) Very few performance changes, only one really is balanced power mode.
[Samsung Galaxy Nexus] FL0OD:
Sure hope Franco can get this all sorted out. M4 is great but I'm getting a little jealous of all the people over in the maurgo forums talking about how great these nightlies are.

†††
[Samsung Galaxy Nexus] Anon9mouz:
Has ne one tried the 192 drop on the M4 yet I'm scared to not wake up lol.

__________________________________________________
[Samsung Galaxy Nexus] Anon9mouz:
Franco also wanted to talk to u about using the M4 in my miui if ur cool with it if not they can just flash it lol

__________________________________________________
[Samsung Galaxy Nexus] myepicyear:
Yeah man, definitely. Lots of people use 192 as their set minimum, and I have personally not seen a single complaint about wake or corruption issues, etc... Whenever I use Franco kernel, I personally really enjoy using 192 as the minimum. It brings a noticeable stretch to the battery's unplugged time, while showing negligible differences in performance/responsiveness.

192-1036+Interactive (or lazy) is my phone personal balance w/francokernel
[Samsung Galaxy Nexus] Sodikop:
Has anyone managed to get a useful DMESG out of a non-booting kernel?
[Samsung Galaxy Nexus] southernchris7:
If I knew how to get the message I would gladly help. I follow directions well.

I'm running Twisted AOSP. I've also tried clean installs with nightly cm9 and Twisted. Not boot with the last three nightlies.

I appreciate your hard work that makes our phones amazing.
[Samsung Galaxy Nexus] belvedere:
New to the Galaxy Nexus, just picked it up yesterday. Coming from a Nexus S so had experience with Franco for a little while. I'm interested in this Hotplug feature but I don't see it available in the Franco app. I went with the Milestone 4 kernel, so I'm under the impression maybe this Hotplug feature is only on the nightlies?
[Samsung Galaxy Nexus] mattallica76:
It was removed a few nightlies ago. I believe Franco said it was a redundant feature.
[Samsung Galaxy Nexus] belvedere:
Ah, ok. I'll catch up eventually :)
[Samsung Galaxy Nexus] jbloggs2008:
Compass?

Any progress on getting the compass fixed? Its been fixed since the June 5th build in CM9:

plus.google.com/103634938164868136396/posts/SgC3e6JcAtG
[Samsung Galaxy Nexus] belvedere:
just came across this post in the other GNex section - http://xdaforums.com/showpost.php?p=27355627&postcount=19709

can confirm this r185 works as my phone is booting up now.
[Samsung Galaxy Nexus] mookiejr05:
I second that!
[Samsung Galaxy Nexus] MichaelMcEntire:
Works for me as well.
[Samsung Galaxy Nexus] southernchris7:
Working for me as well. :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] emd2009:
Works here too! Aokp B38
[Samsung Galaxy Nexus] FL0OD:
Thanks for the find I was getting a little disappointed we couldn't flash the nightlies.

†††
[Samsung Galaxy Nexus] Sodikop:
Just flashed the modded r185, and its working for me.
[Samsung Galaxy Nexus] belvedere:
there's also a Linaro version of Franco's kernel in the General section - http://xdaforums.com/showthread.php?t=1708982

I flashed the 'doc' version and it worked. I don't think my phone liked the GPU overclock to 512 so I'm going to wait for the 384 'doc' version that is said to be posted tomorrow. When playing Temple Run my phone would skip every now and then. Everything else seemed really quick and awesome though, haha.
[Samsung Galaxy Nexus] FL0OD:
Nice. I would love to flash that. Keep us up to date please :thumbup:

†††
[Samsung Galaxy Nexus] invisibastard:
It downloaded fast as hell. I'm too used to the painful goo.im speeds...

Can't wait to try it. I'm already getting insane quadrant numbers with linaro and m4.
[Samsung Galaxy Nexus] FL0OD:
This is freaking amazing

†††
[Samsung Galaxy Nexus] invisibastard:
Have to agree. 185 now boots and is insanely fast.
[Samsung Galaxy Nexus] DatDude123:
For some reason I cannot get r185 to boot. Stuck at Google. I tried 384 and 512. Using CM9 nightly from the 12th.

D
[Samsung Galaxy Nexus] FL0OD:
You need to go back several posts there is a link to a thread that has a bootable version. Franco's original version will not boot on our phone for the most part.

†††
[Samsung Galaxy Nexus] emd2009:
Try this
[Samsung Galaxy Nexus] DatDude123:
Thanks guys. I didn't go enough pages back in app, my bad. All I saw was r185 actually working and tried via Franco app......dundundun......lol.

Thanks again gents.

D
[Samsung Galaxy Nexus] DatDude123:
Up and operational.

Thanks

D
[Samsung Galaxy Nexus] FL0OD:
Cool enjoy it. It's been a screamer on my phone.:thumbup:

†††
[Samsung Galaxy Nexus] DatDude123:
I just pm'd you. No rush though.

Thanks,

D

Newsflash - your and you're.......there's a difference.
[Samsung Galaxy Nexus] DatDude123:
P to the M'd you again.

Newsflash - your and you're.......there's a difference.
[Samsung Galaxy Nexus] chaotic646:
Anyone have any idea why every time I reboot my phone my voltage settings go back to stock? Ive tried the franco app, voltage control, and setcpu...it wont stick after reboot with any of them.
[Samsung Galaxy Nexus] FL0OD:
Yes, if you are using any cm9 based rom this kernel will not play nice with it. It's a known issue.

†††
[Samsung Galaxy Nexus] chaotic646:
Im using black ice...aokp...
[Samsung Galaxy Nexus] FL0OD:
Are you using his app?

†††
[Samsung Galaxy Nexus] FL0OD:
Strange I updated my app and it sticks every time. I'm running BlackICE right now. Sorry I couldn't help and apologize even more for my poor reading skills :(

†††
[Samsung Galaxy Nexus] peabody42:
Compass still broken with nightly 186, using CM9.

CM9 kernel works.
[Samsung Galaxy Nexus] myepicyear:
I think everybody knows that at this point.
[Samsung Galaxy Nexus] Reno Skyy:
Damn 186 is amazing running like a champ on skankwich like a BOSS
[Samsung Galaxy Nexus] themassofthesun:
186 running perfectly on aokp nightlies!
[Samsung Galaxy Nexus] myepicyear:
I know, right?!?

I have nothing but wonderful things to say about this kernel version. You can tell how much work/testing went into making the 1420+1536 frequency options broadly adaptable, and tolerable to the average chip. I'm able to radically increase/decrease the voltages(SmartReflex on or off), use any governor available, and crank the clock to 1536- which I can comfortably stay at, without instability, freezes, etc. I'm really loving the addition of wheatly, and I'm wondering why I didn't feel the same way about it when using it on Ezekeels kernels.

Franco's color controls from his Updater app have suddenly started sticking for me on CM9 as well by the way! Not sure what changed, but I'm excited to have that working for me.

Things are getting exciting here in FrancoKernelLand! :D
[Samsung Galaxy Nexus] snoopy1e11:
Where do u find aokp nightly I've been using this with b39 its smooth
[Samsung Galaxy Nexus] FL0OD:
You're on a terror lately. Appreciate all the updates:thumbup:

†††
[Samsung Galaxy Nexus] snoopy1e11:
Are these the same as the builds in general or these don't include linaro toolchain
[Samsung Galaxy Nexus] belvedere:
these aren't the same as the builds in the General section.

ie. they don't contain the linaro toolchain.
[Samsung Galaxy Nexus] tlc77:
EDIT : Sorry my phone is a GSM version...
[Samsung Galaxy Nexus] franciscofranco:
r196

* Remove 576Mhz entirely - it was causing some undesired instability

* Add toggle to turn on/off fsync: echo Y > /sys/module/sync/parameters/fsync_enabled (it's disabled by default which means that enabled = less IO speed while having data integrity; disabled = more IO throughput but less data integrity)

* Add morfics contrast interface. To change the value: echo X > /sys/module/panel-s6e8aa0/parameters/contrast (change X to the desired value; the default is -24 so don't cry if you think your device is too contrasted)

* Change some ramdisk tweaks for better end-user experience

* Change BLX default value from 96 to 100 - this allows the users to use all range of 0-100 values for the BLX interface
[Samsung Galaxy Nexus] maddoggin:
Gamma color is way too dark. No option to make it brighter!
[Samsung Galaxy Nexus] FL0OD:
Gama can never be to dark.:D

†††
[Samsung Galaxy Nexus] blackout305:
It is a bit dark...
[Samsung Galaxy Nexus] kraminc:
Awesome kernel. Gama looks good to me. Use the tool and set the display settings to the recommended levels.
[Samsung Galaxy Nexus] southernchris7:
Colors look awesome to me as well. Using recommended colors. Also check what gamma interface you have it set at to make sure that's not causing it to be too dark.

Using the linaro version running smooth.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] maddoggin:
Yeah sorry i guess if you like black screens you would like these colors but i would like it to be stock with the option to make darker if i choose too. With this kernel there's is no way to make it brighter at all. The use if the gamma settings is useless its dark to darker. Just my opinion tho.
[Samsung Galaxy Nexus] FL0OD:
Wait your name is blackout and the gamas to dark?

†††
[Samsung Galaxy Nexus] blackout305:
Lol I know...its a bit confusing but even some blues are made to look black after flashing the latest nightly. There's no way to make it lighter...
[Samsung Galaxy Nexus] jhgti:
Has anyone gotten this kernal to work with cm9 rc1. I installed it but storage would force close on me every time I tried to open it under settings.

From a Galaxy far far away
[Samsung Galaxy Nexus] oiad:
Works great for me. I would wipe and reflash cm9.
[Samsung Galaxy Nexus] kraminc:
Maybe there can be a setting added to the app to change the gamma to stock and back again?
[Samsung Galaxy Nexus] slayp00n:
Having trouble finding my pre 196 contrast level, I have tried numbers from -24 to +20. but ti either looks super dark or very washed out. What was the original contrast setting?
[Samsung Galaxy Nexus] tatical:
This is my kernel of choice & the nightlies are usually pretty stable. I haven't noticed anything with my screen while using r196, but my sound volume was VERY low across the board (I rechecked all volume settings). When I reflashed r194, everything went back to normal.

Thanks for all your hard work.
[Samsung Galaxy Nexus] raphenucleus:
There is a setting in the app that changes the gamma back to stock. Simply set it back to 1.0. But if you're talking about the new morfics contrast interface instead of the OMAP4 gamma interface read on.

The original contrast setting was 0, because the morfics interface wasn't implemented before r196.

I already posted this in the Verizon thread, but I figure it's useful for you too. For anyone on ICS r196 or r200 that doesn't like the new morfics contrast interface or just wants to set a different value than -24 on boot, I made a simple init.d script to do that. It should work on Jelly Bean as well, but I think franco changed the default value to 0 in those releases, so the script wouldn't be necessary unless you want to change the value and he hasn't made it stick on boot yet. I'm sure he'll add this functionality to his app in the near future, but in the meantime this will have to do.

Download the attached file. Remove the ".txt" extension in the file name. Use root explorer or adb to place it in /system/etc/init.d. Change the permissions to rwxr-xr-x (Owner: Read, Write, Execute; Group: Read, Execute; Others: Read, Execute). Reboot and your screen will return to the way it looked before the contast interface was implemented. If you want to change the value of the contrast, simply edit the "0" in the script to whatever value you want (-24 is the kernel default).
[Samsung Galaxy Nexus] myepicyear:
Anyone who has put off purchasing Franco's app should just go for it. I've really grown to like it, as the setting menus are insanely convenient, and he updates and improves it very frequently.

After the last update, the app got so much better.

Most recent updates added an fsync on/off setting, the

brilliant

Trinity contrast-interface (which is totally amazing, so I'm not sure why some people are completely devastated by it :mad:. Have you actually tried... adjusting it, or do you insist someone do it for you?)Temperature throttle on/off feature, Content-adaptive brightness, and the settings interface was redone in such a way, that my settings stick every time with CM9 now.

If you're not comfortable/good with Terminals, or if you're like me, and you want convenience, take my advice and get it.

The updater-app and kernel updates are all amazing Franco, thank you :good:
[Samsung Galaxy Nexus] emd2009:
What's everyone undervolting at?
[Samsung Galaxy Nexus] Ziltoid:
I am running JellyBelly-3.4. Can I use one of these kernels? If so, which one?
[Samsung Galaxy Nexus] lowlow5683:
I'm running stock ics 4.0.4 which one do I need to download