yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rsantana:
Big ups

Firstly thanks to Franco the man for developing these amazing kernels that make these phones fly and last all day. Secondly to Stadsport for reposting kernel 18, another thanks to luckylui, and lastly to the amazingly awesome community on display here @ XDA. Y'all rock.
[Samsung Galaxy Nexus] masri1987:
I wants franco turtle back!
[Samsung Galaxy Nexus] Rootuser3.0:
#18 running the best for me so far this thing flies also battery is better.Im on stock 4.0.4 and no SOD like the previous builds 17-17.2 Thanks Franco for putting this out I'm in for buying your app and supporting your hard brilliant work
[Samsung Galaxy Nexus] franciscofranco:
#18.2 is out, just a little treat ;)
[Samsung Galaxy Nexus] DammitCubs:
LOL....running mine at 1.65. Beast mode confirmed
[Samsung Galaxy Nexus] franciscofranco:
Yeahhhhh thats what I like to hear!!!
[Samsung Galaxy Nexus] jordanetodd:
Just ocd to 1.6. Now this phone, that I used to disappointed with, is now beating the galaxy s 2 in performance. I couldn't be more ecstatic! Thank you so much!
[Samsung Galaxy Nexus] jordanetodd:
+1
[Samsung Galaxy Nexus] jkc120:
color control to fix gamma problem in videos?

Can the color control features be used to fix video playback, re:

http://code.google.com/p/android/issues/detail?id=23862

http://androidforums.com/verizon-ga...reas-during-video-playback-5.html#post3948367

http://xdaforums.com/showthread.php?t=1344714 (similar issue on Galaxy Note as the Nexus, though it looks like it's much worse for Note owners).

Just wondering if this "gamma offset triple" can be used to fiddle with the overall gamma curve? People in the google code thread above mention an "industry standard 2.2 gamma" vs. the Nexus that has 1.5-1.8 and I'm wondering if this /sys interface affects that or if it's just fiddling with the R/G/B values?

I found two other gamma-related /sys entries, but they look read only and just for debugging:
[Samsung Galaxy Nexus] franciscofranco:
I have no idea, screen drivers aren't my strong point at all, I just used Ezekeel's implementation.
[Samsung Galaxy Nexus] jkc120:
Ok thanks, I'll ping him about it. :)
[Samsung Galaxy Nexus] chris157:
From what I've been reading the it seems like the limit of the clock frequency that a phone will take pretty much varies from phone to phone. Is this true or can change the voltage values allow a phone to take higher frequencies. The reason I ask is becuase my phone freaks out with anything higher than 1.35 GHz
[Samsung Galaxy Nexus] kichard:
Zoom zoom :D
[Samsung Galaxy Nexus] luckylui:
Ohhhhhhhhhh mannnn!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
With or without DCC enabled in the kernel?
[Samsung Galaxy Nexus] KassaNovaKaine:
I'm new to OC'ing; are there any recommended settings when going at 1.35 or above? Or is it ok to just select the desired option and leave pretty much everything by default (I'm using franco's market app)?
[Samsung Galaxy Nexus] sway40:
Damn this **** is fast at 1.66ghz, you the man franco. Just set it and forget it all you gotta do.

~ Sent from my GNexus @1.66ghz~
[Samsung Galaxy Nexus] wilshyre:
What I want to know is if Franco has figured out the dcc/dpll bug they were having such trouble with that wasn't really letting our phones get much faster than 1.42ghz with dcc on, because apparently it was designed to be turned off at around 1000mhz and DPLL was supposed to kick in and allow us to clock to 1.5 ghz stock. And then that Collin dude said that the tuna board wasn't compatible with 1.5ghz, but didn't elaborate.. so has something changed? Did you figure out some work-around or fix for this? Why is this suddenly possible when 1.42 ghz wouldn't run on many nexus devices(though it ran fine on mine.) Please tell me you figured out a work-around! Also.. I did notice than almost every benchmark performs at about stock performance besides linpack.. and Antutu benchmark seems to show some other stuff getting lower in scores like RAM, where CPU integer has increased.

Also, thanks for everything you do! I love your work!
[Samsung Galaxy Nexus] csseale:
Amazing kernel. Running at 1.6 and its flawless and fast. I must say Franco.....I.....I....love you....
[Samsung Galaxy Nexus] SwiftLegend:
Can someone post the default voltages or even what they have found that gives good life? I was toying with the voltages earlier, and have messed it up:o
[Samsung Galaxy Nexus] chris157:
I'm using whatever the stock settings are for the kernel
[Samsung Galaxy Nexus] williamthegoat:
So since Im on 4.0.4, can I just root and flash this?
[Samsung Galaxy Nexus] Wicked4u2c:
Well 18.2 is bitter sweet for me. My phone runs like a banshee from hell!! My phone is ranked 55 in the world on Antutu on all Galaxy Nexus and ranks 2086 compared to all Android devices including tablets.

Here is the problem, i changed my min to 350 and max to 1000 on ondemand governor, if i restart phone it reverts back to 700-1200 even when "set on boot" is checked. The next problem is I'm losing almost 1%	per min and 2%	every 5min while screen is off. I'm running 4.0.4 done everything possible clear all cache etc.

**edit Nevermind I just rebooted my phone and the battery seems to be draining normal now. However it's still not saving my frequency settings.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rsantana:
Color issues

Anyone else having color issues with this rom like black not always displaying in black but rather brown??I flashed with no wiping of anything to 18.1 then most blacks I originally had became brown. I then tried flashing 18 also with no wiping of anything, and colors remained the same. Anyone had this issue before?
[Samsung Galaxy Nexus] Rootuser3.0:
Yes sir
[Samsung Galaxy Nexus] psohn:
Has anyone tested the sqlite defrag and the turn logger off options to see what sort of difference they make if any? I haven't been able to get repeatable/uniform results. Every full charge and reboot seems to give me different results than the previous reboot, with or without these options selected, so I can't determine the impact.
[Samsung Galaxy Nexus] Rootuser3.0:
Wouldn't 1.6GHZ drain battery faster?
[Samsung Galaxy Nexus] Wicked4u2c:
Flash 18.2 he fixed it

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
Yes, but you don't have to run it at 1.6. Just like 1350 uses more than 1200 or 1000. You can set your max.
[Samsung Galaxy Nexus] kichard:
4.0.4 gave me weird battery life in general.
[Samsung Galaxy Nexus] Dylerium:
Loving 1.65ghz, and i could even undervolt 100 mV, my phone is champin it :P
[Samsung Galaxy Nexus] zman6900:
1.65GHz sounds scary. Whenever I think of high overclock with high use on a phone, I always think of the TV show "1000 Ways To Die." There was a lady who used her phone all the time and it literally blew up on her face and killed her. I'm guessing the phone was extremely hot - and probably overclocked.
[Samsung Galaxy Nexus] Dylerium:
>.> i dont think thats why it blew up... but anyways, it only gets hot when i run 2 or 3 quandrants, which is a lot of stress. not hot under normal use
[Samsung Galaxy Nexus] RickROM:
I have the spare battery charger and two spares, so nothing I do is an issue as long as they are kept charged before I leave home :D
[Samsung Galaxy Nexus] cuzzinz:
Not that it matters for a lot of people but I have been testing different under voltages and I have found clocked at 700/1350 with the voltages set below I always yield high quadrant and antutu benchmarks (3400+ in quadrant & 6500+ in antutu). If I leave voltages as default my scores drop 1000+ points.

Is it that the cores are running more stable at lower voltages?
[Samsung Galaxy Nexus] KillerVamp09:
Oc'ing to 1.65 works fine on NY beast. An Oct that high doesn't yield as high results in benchmarks as I thought it would but it may just need tweaking to score higher.
[Samsung Galaxy Nexus] Stadsport:
18.2 up and running great so far. I tried 1650mhz but it didn't seem faster, and my Quadrant scores were exactly the same, so I'll just stick to 1.3ghz or whatever it is. Honestly the phone is plenty responsive at 700mhz, everything above that it just for funsies!
[Samsung Galaxy Nexus] cuzzinz:
Play with the undervolting. I just brought 1.5ghz to 1200mv and I scored 3985 in quadrant lol. Ran it again and scores in the 3900 range. Haven't tried higher OC yet.
[Samsung Galaxy Nexus] EyeOfTruth:
I agree but I leave my phone at a max of 920mhz.
[Samsung Galaxy Nexus] anton2009:
Yup
[Samsung Galaxy Nexus] danman7:
Ouch,

So I loaded 18.2 last night before going to bed. I had a full charge on it and decided to test the deep sleep capability of the new kernel. Boy, was I disappointed to find a dead phone in the morning. In 6 hours, it had gone from 100% to not being able to power up. Unfortunately, I wasn't able to determine what was the culprit, since it had to be plugged in to even boot. I was running 700/1200 ondemand with no undervolting and using the hotplug mod.

Any suggestions?
[Samsung Galaxy Nexus] tps784@yahoo.com:
I'm running Gummy 0.7.0 and I flashed #18 franco yesterday and was getting amazing battery life yesterday and to top it off only lost 2% while I slept for 7.5 hours! Thanks Franco.
[Samsung Galaxy Nexus] TEK112:
Not if you can't tell us what the culprit was. Did you wipe both caches before and after the flash? Sometimes the device will not deep sleep if you don't re-wipe after flashing.
[Samsung Galaxy Nexus] avid.aria:
I would appreciate if someone can explain How to undervolt the Kernel?
[Samsung Galaxy Nexus] RussianMenace:
Use SetCPU or voltage control baked into your ROM and simply specify lower voltages for a desired frequency.
[Samsung Galaxy Nexus] martin0285:
Possible??

Hey Franco,

I was wondering if you think it will be possible to have "hotplug" persist through reboots??? I've been using your kernel awhile now and love it!! I just started using "hotplug" today and noticed that it doesn't stay enabled through a reboot... Would this be possbile??

Sorry if this was covered... Didn't see it in the OP FAQ....

Great work Franco!!
[Samsung Galaxy Nexus] TEK112:
Are you using terminal or the app? I know it persists in the app.
[Samsung Galaxy Nexus] Tree of Knowledge:
It has always stayed enabled through reboots for me.
[Samsung Galaxy Nexus] Flip35:
Russian when I specify lower voltages do I have to set the numbers myself or there's numbers there to choose fr cuz that's where I get lost, I don't knw what numbers to choose or it is just click undervolt and it does it by itself, sorry for the question but I've never done it before but would like to learn, thanx
[Samsung Galaxy Nexus] TEK112:
You have to set the numbers yourself, but beware how low you go. No two phones are alike. There are variances that could cause one phone to like a lower voltage, but cause another phone to not boot.

The best practice is to do step downs in increments of 50 (850-800-750, etc...) and see how low you can go before instability occurs and then run your phone like that for a couple of days before telling it to set on boot. If you set on boot prematurely without testing the phone may not boot the rom and bootloop until you reflash the kernel. It is not for the faint of heart and could cause very irradic behavior. Start small and document your changes.
[Samsung Galaxy Nexus] Flip35:
Thanx a bunch man, last question when we undervolt is it for better batt life or performance, I haven't flashed Franco's latest how's the batt and performance with it, I'm running black ice latest rom
[Samsung Galaxy Nexus] TEK112:
Think about it. Undervolting is underpowering the kernel. Less volts is less energy and less battery use. So better battery life without sacrificing performance. However, there may be instability... back to the whole every phone is different discussion. As for Franco's kernel, just try it yourself. You can always swap kernels. Just wipe cache and dalvik before and after flashing.
[Samsung Galaxy Nexus] Flip35:
Yup I'm gonna flash it to try it, thanx for the info
[Samsung Galaxy Nexus] rgoyena:
But its already undervokted by the dev.
[Samsung Galaxy Nexus] TEK112:
Yes, but some people like to undervolt it more.
[Samsung Galaxy Nexus] luckylui:
By default from qualcomm the nexus should be running at 1512 as other dual core devices w qualcomm. Like my evo 3D came at 1188 but specs said its supposed to be at 1512..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cuzzinz:
like TEK said... be careful when undervolting...

i highly recommend undervolting thought.

I am one of those people that likes to show off my benchmarks and i couldn't figure out why my gnex was never benchmarking well.

I undervolted and discovered that was my problem. my scores in antutu and quadrant went WAY up (Like even at 1GHz Max OC I was scoring almost 3k in quadrant). i am still working out the kinks with my battery but we will see after today now that things have settled.
[Samsung Galaxy Nexus] macellaio:
There's a huge debate as to the true effectiveness of undervolting. According to bedalus's results (found here) even extreme undervolting can only produce a minor savings.

Didn't Francisco remove his custom undervolting somewhere around release 17 or something? Has some of that been added back in recent releases?
[Samsung Galaxy Nexus] TEK112:
Honestly, most of it is negligible as the screen is really the biggest battery killer. Undervolting (if done properly) can save juice and increase performance. By performance I mean stability, not necessarily faster speed. Like tuning a car. Identical cars being tuned can net identical gains if one runs leaner while the other runs richer. Then again, some blow up making the same changes that make another identical car perform better. It really is phone/car dependent.
[Samsung Galaxy Nexus] RussianMenace:
I actually found that undervolting increases performance, at least on my phone. According benchmark scores only, no RL difference that I can see.
[Samsung Galaxy Nexus] mrkmrk:
You'd think that the kinds of people who buy Nexus devices would at least know the manufacturer of the SoC (namely, that it's TI silicon in this baby).
[Samsung Galaxy Nexus] danman7:
After wiping cache and dalvik before and after (funny how the Franco app doesn't appear to do this) re-flashing 18.2, I've decided that this version is not for me. I was running through battery astonishingly fast while using the device only moderately. Also, for the first time the phone was REALLY laggy. This hadn't happened to me with earlier Franco kernels. I was running on demand with 700/1200, no undervolting for those wanting to know. I've gone back to 18 for the short term. I'll reassess what I plan on doing.

Questions: In BadAssBattery, while using the any of the Franco Kernels, Kernel is always one of, if not the top, user. There will be many "kworker" threads running at any one time. This does not appear to be the case with some of the other kernels I've tried. Is this something I should be concerned with? Is there a way I can determine what these threads are doing? Is there something I could be doing to minimize this usage?

Thanks in advanced.
[Samsung Galaxy Nexus] macellaio:
If bedalus is right, the 2% juice savings you might get from undervolting isn't worth the risk of a reboot. Rebooting takes a lot of juice and at 2% a single reboot will cost far more than what you could save in several days. The stock voltages are designed to be as stable so I think the only valid reason for undervolting is for benchmarking, for those who are into it. The rest is probably just the placebo effect. Personally, I didn't notice a bit of difference in battery life when Francisco removed his custom undervolting.
[Samsung Galaxy Nexus] Jdella681:
Anyone else having problems with data connections? My razr maxx and galaxy tab are pulling data w no problems..
[Samsung Galaxy Nexus] Gahh Its Lee:
I've had a few issues but doubt its kernel related.
[Samsung Galaxy Nexus] TEK112:
YMMV. However, if you undervolt properly it may increase performance and should never reboot. If it is rebooting it is a bad setup. No reboots mean that there is a gain from undervolting. Then again, as I said before, it really is negligible as the screen is the biggest culprit. Full screen brightness and a white background will kill the battery in well under two hours.
[Samsung Galaxy Nexus] billku:
Even though 18.1 supposedly fixed the issue, I was having major SOD problems with 18.2, so I rolled back. I used Franco's app to install 18.2, does it wipe caches before it does so? If it doesn't, does anyone think it's worth a shot to re-install 18.2 manually and wipe caches before and after? Thanks!
[Samsung Galaxy Nexus] TEK112:
I don't use the auto-flash option because I did not know the answer. I download wipe flash rewipe boot everytime I upgrade any kernel.
[Samsung Galaxy Nexus] cuzzinz:
Do you guys leave your 4g on all day?

I swear I haven't been able to break past 10 hours on a single charge.
[Samsung Galaxy Nexus] darrendm:
http://xdaforums.com/showpost.php?p=22813125&postcount=6940
[Samsung Galaxy Nexus] Gahh Its Lee:
I believe most of the people reporting ridiculous times are mostly on Wi-Fi. With 4g I can't break 10 lol. Just remember man our phones eat it as far as battery goes.
[Samsung Galaxy Nexus] billku:
Thanks, hmmm, I guess then I'll have to wait for the next release as wiping caches clearly isn't the problem. Anyone else still having SODs?
[Samsung Galaxy Nexus] Gahh Its Lee:
No sods what's your min? I use 700
[Samsung Galaxy Nexus] cuzzinz:
So with 4g you are at about 8-10 hours?

I am hoping I am not the only one. Been considering turning off 4g when i don't need it.
[Samsung Galaxy Nexus] RussianMenace:
I'm on 4G most of the time and I avg around 7-8hrs of moderate use, mostly browsing the web.
[Samsung Galaxy Nexus] EyeOfTruth:
I leave it on all day, I typically get 10-14 hours depending on usage, I also have the extendended battery.
[Samsung Galaxy Nexus] TEK112:
The script only clears Dalvik. That is why you don't get an "Android Is Upgrading" upon reboot.

I still say wipe both caches, flash and rewipe.
[Samsung Galaxy Nexus] Neo3D:
hmm, been using 18.2 for 48hrs and so far got random reboot once and Sleep of Death once. Had zero issues with 16.2
[Samsung Galaxy Nexus] billku:
I can't remember what it's set at (don't have my phone right now), but I used Franco's app to install it, and I didn't change any of the settings in the app, just went with the defaults.

---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------

Agree now, though it's too bad because the app is really convenient. But obviously not a big deal to do it manually. Do you think using the app to install, which as you point out doesn't wipe the cache, may be causing the sods?
[Samsung Galaxy Nexus] TEK112:
You would be surprised what can cause a SOD...
[Samsung Galaxy Nexus] billku:
So is that a "yes"?
[Samsung Galaxy Nexus] ffejeroni:
derp10char
[Samsung Galaxy Nexus] Jdella681:
It's weird cuz when I toggle 3g to 4g and vice versa the connection would last four a minute and drops afterwards.. It's just been happening today so I don't know what's up. I had to replace my first sim card cuz I wouldn't get 3g and was working fine till today.. Just hoping it's not hardware related..
[Samsung Galaxy Nexus] TEK112:
Yes.......

---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------

Verizon did have another 4G outage today. If you were not set to CDMA only that may be your issue.
[Samsung Galaxy Nexus] Jdella681:
Yea I did know about the outage (I work for vzw) but what was didn't make sense was that all our 4g devices had no problem about signal. Just my phone... sad face
[Samsung Galaxy Nexus] Gahh Its Lee:
Is it better yet?
[Samsung Galaxy Nexus] idkwhothatis123:
running 1.65 Max 700 min on interactive. 4g data all day. On wifi for about 2 hours.
[Samsung Galaxy Nexus] franciscofranco:
New franco.Kernel updater app update:

#3.2

* Added testing version of Color Multipliers interface - pretty similar to Voodoo Color

* Another try to fix "set on boot" CPU frequencies

* Added preventive toasts when trying to do tasks that require internet connection and no connection is found
[Samsung Galaxy Nexus] psohn:
I usually don't play with the colors but I tried your suggested multipliers and gamma offsets and everything pops now. It looks MUCH better than stock! When will the multipliers be able to be set on boot? :)
[Samsung Galaxy Nexus] franciscofranco:
No eta, but soon, I'm too tired today to code it.
[Samsung Galaxy Nexus] kichard:
Love the multiplier. But I LOVE that you gave us values to play from. Looks great. Thanks dude!
[Samsung Galaxy Nexus] Stadsport:
Nice custom buttons.
[Samsung Galaxy Nexus] Cheesejam:
Just to confirm: Does franco's app work with 4.04?
[Samsung Galaxy Nexus] mike216:
Been away for a while and decided to try 18.2

Holy **** this mother ****er is fast!

Its almost perfect! Ones in a while it hangs for a second but over all its one of the fastest if not the fastest.
[Samsung Galaxy Nexus] thisismalhotra:
How do I set the governor to francoturtle, I dont see that as an option in francos app?

NVM: read the last few changelogs the governors are not implemented yet.
[Samsung Galaxy Nexus] TEK112:
How about another galaxy nexus in your store?

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

Yes, but it was not showing on the market. I don't know if he fixed that, but titanium backup is your friend.
[Samsung Galaxy Nexus] lenard_hester:
I got several SODs yesterday running 18.2. I installed via the app. Went back to 17.2 last night (so far this has been the most reliable for me). I will try 18.2 with clearing the caches and update.
[Samsung Galaxy Nexus] upther:
I've gotten 2 SODs this morning. Once after coming out of Angry Birds Rio and once after coming out of AOKP ROM settings. Probably going to have to roll back to an earlier kernel.
[Samsung Galaxy Nexus] yhbrandon:
Have you done anything with frequencies? Or are you just running whatever is set in the governor? I would kill for this battery life and I'm not even over clocking this thing.
[Samsung Galaxy Nexus] yhbrandon:
Sorry my last post was in reference to this :)
[Samsung Galaxy Nexus] nycrazyg:
Same here for me on 18.2 I received two SOD's yesterday. I reverted back to 18.1 yesterday and I've been in good shape since. Both caches always cleaned every time of course.
[Samsung Galaxy Nexus] Gwanatu:
I had another one this morning. Just want to make sure franco knows. So far for me the 16 series kernels were my fav. I'm going to revert to stock voltage and see if I still get SODs. I'm also going to try the 1500/700 interactive mix to see how I fair. Things have been janky for me lately and I don't know what's causing it (weird slowdowns, etc).
[Samsung Galaxy Nexus] calebv2:
Wow I've gotten no SOD at all I'm running 18.2 at 1500mhz great battery life mild UV and I wiped before install
[Samsung Galaxy Nexus] kjwalker:
I also got a sod overnight. Phone was plugged in for 7 hours. I woke up to my extra alarm clock (that I normally never use), checked the phone and it was unresponsive. Rebooted and only had 22% battery. Got another Sod about 10 minutes ago while in class.
[Samsung Galaxy Nexus] Tree of Knowledge:
Been running 18.2 for two days, haven't had any issues at all. I think this is due largely in part to the fact that I wiped data and installed this at the same time as flashing a rom. I'm really enjoying 18.2 though.
[Samsung Galaxy Nexus] pvspencer22:
I've been seeing SoD since coming to 18.2 with AOKP. This was from a full wipe. Anyone have a link to the stock kernel, so I can do some better testing?

I've searched the Kernel Lists and Googled for it, but no luck...maybe I'm just missing something.