yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] cesium:
When you compile the kernel, you basically translate the source code from one language into another language that runs natively on the phone. Before, during the translation process, errors appeared (seemingly due to different pointers and variables that didn't exist and whatnot). Now all these errant issues have been fixed, such that when the compiling happens, there are no errors whatsoever. C is the programming language that the source is written in.
[Samsung Galaxy Nexus] mikespe:
Lighten up...any moron knows when you put a "smiley face" it means I was joking! Go take a cold shower & chill out!

---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------

Thanks for taking the time to write a HELPFUL reply! Others need to take note! :p
[Samsung Galaxy Nexus] laureanop:
I don't know how it gets better than 166 but thank you Francisco.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] laureanop:
Francisco : it looks like omap gamma settings is broken In 169

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] mike216:
Try clearing data for his app
[Samsung Galaxy Nexus] laureanop:
Still broken

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] LocoTSX:
You could download the "brightness level" app from the market. Its works great!
[Samsung Galaxy Nexus] mike216:
I don't know what rom your on but go in let's say rom control settings and try clearing that data. Go in recovery and wipe cache. But it could be broken also,I'm just throwing out ideas
[Samsung Galaxy Nexus] revolt1:
Yes gamma is broken
[Samsung Galaxy Nexus] laureanop:
You don't realize how important it is till you don't have it. Screen looks washed

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] innov8ion:
There were no errors. There were warnings. If there were errors, it wouldn't have compiled. This may or may not improve stability but it does increase peace of mind. Congrats!
[Samsung Galaxy Nexus] zeke1988:
yup, it's broken. but dont worry, he will release a fix soon.
[Samsung Galaxy Nexus] impulse101:
After I get up in the morning it always switches my phone to single cpu mode overnight. I have never put it in single and I never use hot plug... Is this a bug? I thought it might put it in single cpu after being asleep for a while but it doesn't revert back to dual
[Samsung Galaxy Nexus] eman3316@optonline.net:
Totally agree. Went back to 166. Once you have this setting it is pretty hard to go back to something without it.
[Samsung Galaxy Nexus] kuronosan:
Was about to chime in on gamma but looks like I'm late to the party.
[Samsung Galaxy Nexus] eman3316@optonline.net:
Here are my color settings if anyone wants to try. I think it makes the screen look amazing and rival that of super amoled plus screen.

Remember you need to go back to 166 or wait for a fix for the gamma settings.

http://xdaforums.com/showpost.php?p=26256101&postcount=197
[Samsung Galaxy Nexus] tu3218:
Is there anyway to flash back to older nightly versions within the franco app? I'd like to go back to 166 but I only see options to flash the latest. I know the file is can be found on his site with every kernel but it'd be nice to get it within the app. Is this possible?
[Samsung Galaxy Nexus] kingoanklebreakn:
No it's not.
[Samsung Galaxy Nexus] Aerocaptain:
Completely agree with boosting the blue multiplyer. I go up to 260 and my screen looks fantastic.

Sent from CDMA V6 SC GNexus w/Liquid & Franco.kernel
[Samsung Galaxy Nexus] ncfastls1:
Hey so I'm setting up my friends nexus and I already put android revolution on it but I'm curious about this kernel. How stable is milestone 3? Like are there random reboots? Also how's the battery savings since its undervolted?
[Samsung Galaxy Nexus] Gahh Its Lee:
Just put him onto a nightly they are better none of the kernels have ever given me reboots. Milestone three was good though.
[Samsung Galaxy Nexus] laureanop:
Nightlies 65 and 66 are phenomenal . Install the 384 mhz gpu version though. Not all phones can handle the 512 mhz gpu

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] ncfastls1:
Thank you. So there are two versions one with stock gpu and one over locked? Also before I install it, does anyone have a link to the stock kernel incase he doesn't like it?
[Samsung Galaxy Nexus] kingoanklebreakn:
The only one of these that has stock gpu is the milestone which is 307mhz. There are two versions of each milestone but each is overclocked.
[Samsung Galaxy Nexus] laureanop:
Stock is 307 mhz. Only the milestones have that.

The link that I'm giving you is for the Butternutz kernel by imnuts. That's the closest to stock as possible with the necessary optimizations . He makes very reliable kernels

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

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] GinoSylum:
Whatever version you put on, do yourself and your friend a favor and spend the couple bucks on francos app... It's a must have. You can control everything this kernel can do, and it's nice to support the developer... You'll be glad you did once you start using it.
[Samsung Galaxy Nexus] Shamrock13:
I installed the latest nightly, and I'm having a giant problem. When I have a headset plugged in, whatever music I play, stops after like three seconds. Is there any link to the 166 512 MHz kernel? I downloaded the one from the website but its telling me the signature is invalid and won't install.

Oh please help!
[Samsung Galaxy Nexus] laureanop:
There you go

http://db.tt/oJRumcVd

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] Shamrock13:
I just tried again. Thank you for that by the way. And it said Signature not verified, Install aborted.

Why? I don't understand why I can't install this kernel.

EDIT:

Apparently, having it in a subdirectory is a bad idea. I had to move it over to the ROOT of my drive. Once I did that, it installed fine. :D Let's see if I'm still having that issue now..

166 seemed to fix my issue.

Anyone else on 169 having the same issue I was? Plug in a headset or to an AUX port, and your music plays for about 10 seconds then stops.

Anyone?

Bueller?
[Samsung Galaxy Nexus] pluto22:
Anyone having random reboot issues with 169? I had 4 reboots when the phone was just resting. Every time it froze during the boot animation and I had to pull the battery. I went back to 156 for the time being.
[Samsung Galaxy Nexus] nate6138:
Put 169 on here for giggles and wow. I know I haven't used the phone that much but this is the best idle I've had. I currently have 1 hour of screen on time.
[Samsung Galaxy Nexus] daviddemarco79:
I'm having the same issue.... All day it was happening to my Pandora
[Samsung Galaxy Nexus] upther:
No problem here. I was listening to both Rdio and Slacker in my car today without issue.
[Samsung Galaxy Nexus] parkson:
For being a small sample size, that's about as good as you can hope for with the Gnex. Typically with 1 hour screen time I'm down to 75% battery with only maybe 3-4 hours standby.
[Samsung Galaxy Nexus] Dave778:
Nice!
[Samsung Galaxy Nexus] gnexdude:
Im not having any problems with 169, actually, it feels quite fast!
[Samsung Galaxy Nexus] raphenucleus:
So far so good on r173. No noticeable problems after about an hour. Smooth as butter!
[Samsung Galaxy Nexus] Shamrock13:
Can you test and see if my previous problem occurs?

Plug in your phone via headphones or auxiliary, and then play music through Pandora, Google Music, or Amazon MP3 or whatever you use, and tell me if it pauses your music after a few seconds.

Thank you! :D
[Samsung Galaxy Nexus] raphenucleus:
Just tested with headphones, streaming on google music and everything played perfectly. I tried with two songs, one over wifi, one over LTE and both played exactly as expected. So hopefully the issue is fixed for you.
[Samsung Galaxy Nexus] laureanop:
No problems here. Liquid 1.4

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] Shamrock13:
Wonderful. When I get home, I'll install the new kernel. I've been loving these kernels as of late. The only one that caused me any issue was... 169 I think the number was.

Thanks again to both of you! :D
[Samsung Galaxy Nexus] upther:
Working fine for me too.
[Samsung Galaxy Nexus] yami951:
Nice update franco. Bought your app a few days ago, it's definitely a must have for anyone using your kernels.
[Samsung Galaxy Nexus] chrisanthropic:
For the record, I had the same issue with 169, but it only happened when the music volume on my phone was at max. It would also play from the phone's speaker for half a second right before stopping. Lowering the volume on the phone by 1 fixed the issue.

I just updated to 173 (running Liquid) and still have the same problem.

I'm not concerned about it really, just wanted to share if anyone else runs into it.

**Update**

Changing "Increase Maximum Sound Volume" from 3 to 2 solves the issue on my device as well.
[Samsung Galaxy Nexus] kynolin:
Question:

Can anyone help point me in the right direction for help with the Franco app? I'm having trouble finding a solid description of what everything does for the new update. Specifically, I'm looking for what each power mode does so I will know which one I'd prefer and how that affects the settings I choose.

Extra Information:

What I'm going for the 200mhz-1.3ghz, max screen off 700mhz with one core off, and either the interactive or ondemand governer. I don't want to choose a conflicting power mode for my ideal setup, and I can't manually turn off one core, I have to choose a power mode and then change everything else. Any help or direction to information is appreciated. There are quite a lot of pages to search through here and I don't have a bookmark. :confused:
[Samsung Galaxy Nexus] Gahh Its Lee:
Would this do anything for us cdma users?
[Samsung Galaxy Nexus] franciscofranco:
I recommend you to flash it, I made some changes that benefit both GSM and CDMA.
[Samsung Galaxy Nexus] Gahh Its Lee:
Good to know I'll flash tomorrow. I'm actually trying to near kill my battery on 173 right now as this is the first time I'm getting the mythical 4+ hours of screen on. Funny thing is I'm at 51% battery like just under 2.5 hours on and yet I'm in a **** service are I'm lucky to get one bar. Great work man. Like really great work.
[Samsung Galaxy Nexus] revolt1:
what happened to the lazy setting
[Samsung Galaxy Nexus] Gahh Its Lee:
Well clearly its gone. I wonder why I quite enjoyed it
[Samsung Galaxy Nexus] djk21108:
Sorry for being ignorant, but where is the francoGazelle governor?

I'm new to the Nexus
[Samsung Galaxy Nexus] supernova_00:
I would also like to know this. I don't understand the difference between power modes and govenors, especially which should be used together.
[Samsung Galaxy Nexus] danman7:
Long gone. Deprecated.
[Samsung Galaxy Nexus] supernova_00:
He accidently removed it

http://xdaforums.com/showpost.php?p=26747790&postcount=17642
[Samsung Galaxy Nexus] Shamrock13:
I'm not going to lie, but I've never EVER in my life felt my phone SO cold. This kernel is absolutely wonderful. Seriously, this paired with Eclipse paired with the newest radios makes this phone run super cold (in good reception). I haven't tested a bad reception area, but I'm pretty sure this thing starts burning and going through battery. Not sure if kernel or if it's actually the continuous looking for signal killing the battery. I don't really have anywhere to truly test that.

Anyway, I just wanted to say, thank you for another wonderful kernel update.
[Samsung Galaxy Nexus] UK_Wildcats_Fans:
I love the kernel. It is definitely running faster and longer with it. I read through the threads. Is there vibration control? I am looking for a way to adjust the vibration to be longer and/or more intense. I know that it will drain the battery more. I just have a difficult time feeling it with certain jeans and slacks.
[Samsung Galaxy Nexus] supernova_00:
Smart Vibrator works great for this
[Samsung Galaxy Nexus] Shamrock13:
Anyone else getting a battery drain with Google Music?

Here's the situation... I played a cached song on my phone for about 10 minutes earlier in the morning. Got to work with 98% left. Didn't really touch it till about 20 minutes ago where it was at 91%. I had to stream a song, and after it played. I noticed my phone was a little hotter than normal. I'm in great coverage by the way. I look at my battery, and it's at 81%. I mean this is after the song has played. That's the ONLY data intensive thing I've done today, and it has taken an 8% hit on my battery in about 25 minutes.

I don't know if it's the kernel, the ROM, or the app that's causing this. Anyone have any idea?
[Samsung Galaxy Nexus] Amphibliam:
My battery has been pretty impressive. I'll post screens tonight.
[Samsung Galaxy Nexus] UK_Wildcats_Fans:
I tried this app but it does not work. When I make the changes for the default SMS and call, it does not play them. I am using ContApps, which I love. I believe this app constantly lets the phone use the default phone settings. That is why I was hoping to get a way to change it within the kernel.
[Samsung Galaxy Nexus] Shamrock13:
I got this PM the other day from that user about the music playing and then stopping immediately afterwards. Well, I switched back to 166, and my music worked fine. On 174, the issue has presented itself again. Something broke in between 166 and 169 and hasn't been fixed.

Think you can look into that for me Franco? If not, I'll understand. I know you're a busy guy!
[Samsung Galaxy Nexus] flytechguy:
Getting the signal (3g/4g) lost again on r174. Straight gray bars. Does not come back after a full cache wipe as well.
[Samsung Galaxy Nexus] GinoSylum:
What ROM are you running? I have literally never seen that for more then 3 seconds when switching from wifi to data... I'm on AOKP 37 with Franco 174.. also running the latest CDMA radios...
[Samsung Galaxy Nexus] flytechguy:
AOKP 37, latest radios as well.
[Samsung Galaxy Nexus] GinoSylum:
so strange... no 2 android phones are the same... we are running the exact same software...
[Samsung Galaxy Nexus] nbajwill55:
Has anyone else successfully edited the gamma/color levels using AOKP's ROM Control? Or do I need to purchase the Updater App?

I'm new to this kernel- thanks for the help!
[Samsung Galaxy Nexus] GinoSylum:
Just get the app.. It's fantastic, you can control everything so easily... It's a great kernel, and it's nice to support the developer...
[Samsung Galaxy Nexus] nosit1:
Man, I read the changes. I don't understand how you do it, but you do! Thanks for the nightlies!
[Samsung Galaxy Nexus] Amphibliam:
Where is his repo?
[Samsung Galaxy Nexus] Shamrock13:
Do you know if the kernel is the reason as to why I'm getting that music start/stop bug? It seems as that is why. I'm just seeing if you could possibly look into that when you get a chance. I tried to find the change log, I just didn't know where it was. >_<
[Samsung Galaxy Nexus] cj1896:
Is anyone still experiencing problems with the color multipliers and gamma values not loading? I still can't get them to set at boot. I have uninstalled the app and reinstalled it, and tried both the milestone 3 and nightlies. I am running CM9.
[Samsung Galaxy Nexus] timbck2:
I've been experiencing a very annoying problem every once in a while. After turning my screen on, the touchscreen is completely unresponsive. My only option when this happens is to pull the battery (I've tried everything else I can think of when this happens). I'm on Franco nightly 174 and it just happened. Is this likely a kernel or ROM problem? I'm running Liquid 1.40.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nosit1:
https://bitbucket.org/franciscofranco/android-tuna-omap/

I believe it is that. Correct me if I'm wrong.
[Samsung Galaxy Nexus] akademix:
+1

I experienced this the other day after running the same kernel (R166) for a couple of days. I was able to turn the screen on and off but that's it. Screen was unresponsive and then boot looped. Had to do a battery pull.

I'm also on Liquid 1.4
[Samsung Galaxy Nexus] jbdan:
Yeah this is the first time I've had this issue. Color multipliers will not stick through a reboot. M3 aokp b37. Could it be the update to the app on 28th....
[Samsung Galaxy Nexus] upther:
I wonder if it's an issue with CM9. I'm running ParanoidAndroid and having the same issue.
[Samsung Galaxy Nexus] pluto22:
Is that better than the Jack Rabbit? :p

Sorry I couldn't resist! You know everyone else was thinking it too... :)
[Samsung Galaxy Nexus] supernova_00:
Actually it is! You can set the length and strength of the vibrations to your preference lol

Was the lazy govenor added back to 175?
[Samsung Galaxy Nexus] jcmm11:
All I can tell you is that I'm also on liquid, been running all the nighties,.and have never run across this problem.

The only suggestion I can come up with is to try a full wipe and reinstall and see if that fixes it.
[Samsung Galaxy Nexus] jcmm11:
yes it was
[Samsung Galaxy Nexus] cj1896:
I have the app...it isn't working.
[Samsung Galaxy Nexus] buckmarble:
I've been experiencing a lot of wifi connectivity problems and drops on 175. Aokp b37
[Samsung Galaxy Nexus] Droid_JD:
Franco,

I've been constantly having a Bluetooth sound problem. I don't believe it's Kernel related, but I was wondering if there's a kernel fix for it.

I use a Bluetooth headset when I drive, and I can never hear the voice commands from my phone; even the caller on the other end is very quiet. I have to flash the attached file in order to make BT/Phone commands audible.

The Ezekeel sound volume increase does nothing for it, is it supposed to? Is there a way to adjust this in the Kernel?

I don't know where the appropriate place to submit a request is, or if one exists, so I though I'd say something here and see if anyone else experiences this.

I believe the attached file is just a modified voice dialer APK.

If it's just me I'll shutup and deal with it, but does this happen to/annoy anyone else?

Thanks Franco for all the work you put into these. It's much appreciated by all.
[Samsung Galaxy Nexus] Shamrock13:
I'm still experiencing the audio start and stop when the volume is max. I thought it went away because I tested a pair of headphones, but when it's plugged in via my aux port in my car, it stops playing.

I've reverted back to 166 till that issue is fixed. I've tried all versions, and it still happens. Can't be my ROM as it works flawlessly on 166. I don't know what the issue is with the new ones. Oh well. I'm not complaining. I do love to have your latest and greatest that's for sure. 166 is wonderful, too though. :D
[Samsung Galaxy Nexus] Mikes30000:
I'm on AOKP B37 and Franco's app won't keep the color multipliers between reboots. I don't know if it's an app or kernel issue. The gamma values and OMAP Gamma do seem to stick on reboot however.
[Samsung Galaxy Nexus] thefivetheory:
I had something similar a few pages back. Try "updating" your su binary even if there's not a new version available. After I did that I was able to set color multipliers and have them stick on reboot. I have to do this every time I update my ROM but YMMV.
[Samsung Galaxy Nexus] jbdan:
Tried. No go for me
[Samsung Galaxy Nexus] laureanop:
Set the color multipliers to default first with aokp rom control ( or whatever is called ). Then adjust franco's

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] TEK112:
You will only hear voice commands if your headset supports A2DP. Meaning, if your BT headset can't hear your music, then it won't be able to hear voice prompts. You can verify this in the Bluetooth settings of your device, it should have two audio options checked off for it.
[Samsung Galaxy Nexus] jbdan:
Doesn't work either but thx
[Samsung Galaxy Nexus] tehgyb:
Anyone having issues with Pandora? It'll play, then pause, every time I hit play it does it again, within seconds. both screen on and off. Flashed back to m3 and the problem is gone. Been happening for the last three builds.
[Samsung Galaxy Nexus] Shamrock13:
Yes, sir. A few of us have actually been having this happen. Are you using headphones or an auxiliary cable? If I'm not mistaken, your volume is max when you are using it, correct? I had to turn down my phone's volume two clicks and then it played my music fine. It's annoying when I'm driving and the music is softer because it's turned down a bit.

I flashed back to 166 and all is good. Apparently, it's not that big of an issue or something. Look back a few pages and you'll note that I've posted about this as well as maybe 2 other people.
[Samsung Galaxy Nexus] Droid_JD:
Thanks, I did not know that. Having checked the Mfr website and the BT settings I can verify that my BT does support A2DP and that I have both the "Phone Audio" and "Media Audio" enabled.

Any idea where to go from here? The notifications are audible, but only barely - as in, a step quieter than a whisper.

Thanks
[Samsung Galaxy Nexus] upther:
Once your headset is connected, you may have to go into bluetooth settings and click the media audio box again. I have a bluetooth speaker that I use around the house and sometimes it won't fully connect for media playback.
[Samsung Galaxy Nexus] Droid_JD:
Thanks for the suggestion, it already is enabled though.

Does anyone know if this is any way kernel related or kernel alterable?
[Samsung Galaxy Nexus] upther:
Tap it anyway. Mine is always checked but when it doesn't play music I have to tap it again and that does it. Sounds weird but I've dealt with it on both AOKP and ParanoidAndroid.
[Samsung Galaxy Nexus] Droid_JD:
I'll give it a shot later. Thanks for the help
[Samsung Galaxy Nexus] Moonkae:
Hello,

First of all I'd like to thank Franco for his kernel. It is excellent to say the least. I'm currently running nightly #173 and have 1d 6h of time on a single charge with over 2 hours of on screen time (which, for me, is pretty decent). I'd like to point out that the standby time is really good with very few wakelocks. I was using the interactive governor and when looking at the time spent in each state it seemed like it was doing its job well with an appropriate range through the frequencies. I'm also a fan of the OMAP4 gamma interface and think it is a good addition to the kernel. I'm about to flash #175 and hope for similar results and will respond if I encounter any problems. Good work Franco!

edit: #175 was definitely not as battery friendly as #173
[Samsung Galaxy Nexus] tehgyb:
Thanks for the suggestion man, and sorry everyone for not searching or reading back like I should have, was in a huge rush this morning and mobile app searching is crap.
[Samsung Galaxy Nexus] Zacisblack:
I've been having this issue since the 150's but not even on Max volume. It even happens on my replacement Nexus. Also get a really loud buzzing sound while listening to music and using data at the same time.
[Samsung Galaxy Nexus] Eschmacher:
Hmm... The original post says you don't need to wipe anything... Flashed 173, I couldn't get 3G or 4G for 30 minutes, at which time I decided to reboot and clear cache and dalvik.

Suddenly, data works...
[Samsung Galaxy Nexus] nosit1:
What are people using for UC with #175?
[Samsung Galaxy Nexus] timbck2:
I experienced this for the first time this evening. I had a cable running from the headphone jack to the aux in jack in my car. I started music playing and within 10 seconds it stopped. Started it again, about 5 seconds later it stopped again. Want through this a couple more times before I remembered reading something about it on this forum.

I did *not* have the headphone volume turned up to max (I checked).

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] upther:
I updated the Franco app last night and got in the car this morning and ended up with the same problem. I had to go into the Franco app and turn the max volume hack down to 1 for it to play consistently. I miss the added volume but it's still better than turning the actual volume down a couple notches. Wonder what suddenly changed? I'm on 174 now but getting ready to update to 175.
[Samsung Galaxy Nexus] Mikes30000:
No luck with either of these methods. Any other suggestions?