yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mikespe:
165 has been AWESOME so far! AMAZING battery life and ZERO lag! Maybe the new Milestone? ;-)

---------- Post added at 01:21 AM ---------- Previous post was at 01:18 AM ----------

However I suggested to him if he could build into his app a backup feature where we could backup the kernel & app settings so we can revert back to a known working setup/kernel...He said he is strongly considering it!
[Samsung Galaxy Nexus] ms0chez:
I agree, 165 is a win. 166 wasn't showing my nexus enough battery love and I didn't like the lag. 165 was lag free and banging battery life.

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
I'm considering to add a backup too to save the app settings, just that.

Anyway I'm preparing a little surprise for this kernel for the next release (who should be the last build before Milestone e no **** happens). It's nothing major for the majority of the users, but it's a big deal for us geeks. Will be revealed when it's finished :)
[Samsung Galaxy Nexus] sruel3216:
160 is the best for me in terms of stability. Everything after I have had a reboot with these settings:

1228max/728min

Interactive

Tried sr on and off

Just reporting. Happy with 160 :)
[Samsung Galaxy Nexus] Lambetts:
Bump :-)

Thanks.
[Samsung Galaxy Nexus] smokestorm:
I used to have very frequent data drops with stock rom and stock/franco/lean kernel.

But since I moved to liquid 1.4 & franco's nightlies, the signal has been very stable across the board.
[Samsung Galaxy Nexus] drawde40599:
Yep!! 160 and 162 are perfect!! Best out of all of them IMO
[Samsung Galaxy Nexus] franciscofranco:
r169

* I present you the FIRST and only kernel for the Galaxy Nexus completely free of compiler warnings/errors - it's completely clean!

* Added a fix from Ezekeel to fix the sound boost being reset when we receive a sound notification while listening to music

* Added a fix found by Imoseyon to fix a long lasting bug in the stock kernel that random rebooted our devices in some rare cases - more information visit my repository
[Samsung Galaxy Nexus] BigBake88:
Can someone explain "free of compiling warning/errors in noob terms?! :confused::D
[Samsung Galaxy Nexus] swaser18t:
First time iv had a data drop #169 :(
[Samsung Galaxy Nexus] dpaine88:
Am I correct in assuming it goes like this...

Interactive = little more performance for a little less battery

OnDemand= a little less performance for a little more battery?
[Samsung Galaxy Nexus] BigBake88:
Yes, interactive will spend more time in the higher frequencies. OnDemand is king IMO. Best of both worlds.
[Samsung Galaxy Nexus] ragnarokx:
The sound bug fix has been a looong time coming, happy to see a fix :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] duowing:
I'll have to give 169 a go, but I've had 166 going all day the 384mhz version and I haven't experienced the data drops or at least not that I've noticed. I at least haven't had signal completely drop out. I haven't noticed the data dropoffs and I've been going all day. I had some yesterday. I'm wondering if part of it is simply just that person or area's mobile signal/towers, etc?
[Samsung Galaxy Nexus] :
I was on 166/384 since release & didn't notice any data drops..I use my phones ALOT! Soon as u posted 169 I flashed it on my maguro and toroplus..Running perfect. Franco u are a boss!:D
[Samsung Galaxy Nexus] KingDavid63:
I've experienced allot of data drops lately myself, don't know if it's kernel related or not...
[Samsung Galaxy Nexus] Bavilo:
Gamma settings on r169 don't work :-(
[Samsung Galaxy Nexus] ranasrule:
yup....same here

---------- Post added at 09:18 AM ---------- Previous post was at 09:11 AM ----------

sounds sweet....if you can get the Gamma settings fixed:)
[Samsung Galaxy Nexus] Hanny:
you dont have to reflash those (solely regarding to battery thing not reboots) to make the battery shows correctly.

because as your phone auto reboots, or kernel panic, or battery pull, there are chances that your battery current may temporary **** up itself and display a huge decrease of battery after the phone boots. however it is simply the phone's battery reading / displaying problem and it means nothing. if you leave your phone there (unplugged), the 15% will slowly goes up back to the correct level of battery in half an hour :) of course it is no harm to plug it while it "regenerates" because as i have said it is just the matter of displaying. in your case i guess flashing the rom have reset the displaying stuff or whatsoever so it goes back up to the correct level. generally speaking, it is unnecessary to do that.

but for your auto reboot thingy, i do not have clue for that and maybe you are recommended to do a clean install ;)

Sent from me who tests OC and A2SD on P500 and experience auto reboots for 136 times in a month :p
[Samsung Galaxy Nexus] iGoogleNexus:
=P not updating til gamma fix

- Google
[Samsung Galaxy Nexus] stellaryt:
EDIT:My fault..Sorry.
[Samsung Galaxy Nexus] ranasrule:
maybe its an issue with the 512 version as that's the one I'm using and Gamma Settings aren't working for me :(
[Samsung Galaxy Nexus] willl03:
OMAP4 gamma not working here too, 169 512mhz, slim ics 3.8 rom
[Samsung Galaxy Nexus] Cadillac Johnson:
Looks like it, running 512 on Liquid 1.4 and no OMAP Gamma.
[Samsung Galaxy Nexus] castaway1:
No OMAP4 Gamma not work on 384 too
[Samsung Galaxy Nexus] jnr21:
After 20mins of using r169 i get signal drop and also quite high battery drain (same issues with r166). With r166 i get ~2 hours lower screen-on time compared to r160. Going back to r160 which is stable and battery friendly for me.
[Samsung Galaxy Nexus] stellaryt:
:what: So sorry.I saw the screen ws changed so I think it's working....My fault...
[Samsung Galaxy Nexus] ch33kybutt:
Admire your perserverance as it must have taken a while to fix all the warnings :)

Upside is that compiling is definitely cleaner (never really bothered with all the warnings, to be frank) but the downside is that this clean-up job will make merging of any new upstream patches a real PITA later on :(
[Samsung Galaxy Nexus] kompressorgpl:
Hello! What is the main difference between version 384 and version 512? And what do you recommend?
[Samsung Galaxy Nexus] xyzulu:
The difference is 128
[Samsung Galaxy Nexus] kompressorgpl:
Easy maths! Can you translate dose numbers for the real world?
[Samsung Galaxy Nexus] xyzulu:
The difference is 128Mhz of GPU speed.
[Samsung Galaxy Nexus] Moz007:
It's the gpu's overclock, you have to test like your computer !

Also if anyone has Virtua Tennis, could you test if you have artifacts in the sky of presentation before a game ?
[Samsung Galaxy Nexus] Hanny:
thank you franco for your efforts! :) however, unfortunately the cellular signal drops (upon wakeup from deepsleep) is come back now for me :( two times since flashing 169... i would be glad to test it if you have any idea of fixing, thanks!
[Samsung Galaxy Nexus] safir187:
can you add more low frequencies? like 200mhz or even lower?

wouldn't that help the battery life extension?

edit:

ok, i searched the thread after i posted this.

recommendation:

can you please add recommended settings to the FAQ in the first post? it sounds more leave-me-alone and less problem solving (are these words?!) now.

it would prevent us from asking the same questions over and over.

edit2:

okay! i did a bit more searching and now i'm confused the the timeline of the experiencing process.

i think we really need to have the latest recommendations in the FAQ section.
[Samsung Galaxy Nexus] mistermojorizin:
in addition to the gamma presets not working, it appears that at full brightness you can't set the blue multiplier above 240 or so - it causes everything to become yellow instead of blue. turning up the multipliers at 100% brightenss helped the usability on sunny days.
[Samsung Galaxy Nexus] DarkGruf:
When I flashed 169(512 version) my screen turned all green. I had to play with color multipliers to revert that. Previously my setting was 400 400 400.
[Samsung Galaxy Nexus] Moz007:
Evites de mettre ce genre de réglages ça crame l'écran !
[Samsung Galaxy Nexus] ZiCoN:
Dude.... When you can say "rødgrød med fløde" in perfect danish, you're allowed to write in your native language....
[Samsung Galaxy Nexus] DarkGruf:
I like white to be... white and with this setting hey are. About screen burning future will tell... But that's not the point. Why the screen turns green with this setting on 169 and not with the other versions. Could someone test this on his device ?
[Samsung Galaxy Nexus] Benji1983:
I can do it and im german ;-)

Sent from my PARANOID Nexus Prime ( I see people Ahhh)
[Samsung Galaxy Nexus] mistermojorizin:
yea same, look 1 post before yours.

you can turn down the brightness or turn down the multipliers, especially the blue one.

you can't have both on this kernel high brightness and high multipliers
[Samsung Galaxy Nexus] Puzzlegirl:
I got the sunglasses out ;) and tried these settings with no problems on 169. My gamma presets work perfectly at every boot on either 384 or 512 versions. It's the colours multipliers that haven't worked for me on the last 3 or 4 nightlies.
[Samsung Galaxy Nexus] Treatcon:
Just throwing it out there, no problems at all with 169. Colors, gpu, benchmarks, blahhhh blahhhh are all good. Smooth and very responsive. Good battery so far as well.

Thanks Franco!!
[Samsung Galaxy Nexus] DarkGruf:
Just seen your post. I guess we wrote more or less at same time :) What do you call brightness control ?

---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------

Have you tried 400 400 400 on color multipliers ?
[Samsung Galaxy Nexus] Diger36:
Maybe a little late but spend yesterday trying out some Roms. Was on AOKP and experienced data and signal drops with every Franco Kernel from r6x until r166. The moment I tried liquid, slim and rascream, I had no problem at all. Switched back to AOKP and I instantly had the drops back. I am keeping rascream for a while now. I think it's ROM related, or at least not ONLY kernel related...

For what it's worth anyway... :D
[Samsung Galaxy Nexus] krex:
...sure you didn't if you use always. It can be seen for some seconds when you wake up your phone from sleeping.
[Samsung Galaxy Nexus] Hanny:
may you please check the default RIL of the roms without problems? (rascream etc) with the GetRIL app. are they XXLA2 as well?

thank you.
[Samsung Galaxy Nexus] Diger36:
Yeah, XXLA2 it is...
[Samsung Galaxy Nexus] DarkGruf:
Could you try 400 400 400 on color multipliers and tell me if it's still good.
[Samsung Galaxy Nexus] gubshi:
AOKP / XXLA2 / latest nightly (#169 since this morning ;) ) of franco's

runs PERFECT. And because of that, just purchased the app :)

Keep up the good work, just wanted to say thanks :)
[Samsung Galaxy Nexus] Benji1983:
i run it this way 400-400-400 and its perfect for me no issues

greetz benji
[Samsung Galaxy Nexus] lynxboy:
OMAPGamma settings not working for me either on #169. Back to #166 for the time being.

Regards.
[Samsung Galaxy Nexus] jnr21:
since tomorrow? :D
[Samsung Galaxy Nexus] DarkGruf:
Really strange I try again...

And it's same... Normal colors on boot beginning and after boot is finished my screen turns green. Back to 166 all normal.
[Samsung Galaxy Nexus] zok-star:
im getting bad battery with 169 :( Anyone care to share their settings plz?
[Samsung Galaxy Nexus] CaspaTheGhost:
Back at work and so far so good! Wifi issue seems to have been fixed, bars are white when the phone wakes up!

Great stuff, thanks Franco... I was going to post my battery life shots from yesterday but as we are now on r169 I'll just write my screen on time which was about 4hr30... That's under my usual conditions but with quite a lot of radio playing, video playing and GTAIII fun!

Also, the first 4hrs the phone was asleep (as was I) but wifi was off so it was on the mobile network, had 2% drop so all in all...

VERY IMPRESSED! Now then, let me see what this new release is all about!

EDIT:

Flashed the 512 version of r169, gonna see how that goes as 512 have been fine for me apart from r166... All my colour settings have stuck but after checking the OMAP Gamma it does appear to be broken, i.e. changing the value makes no difference.
[Samsung Galaxy Nexus] simacai:
169 color multiple blue >238±1 then all screen become green

and back to 166, all good

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] relax24:
I think everyone who mentions that they are getting good/bad battery life should post exactly what settings and undervolts they are using, otherwise it's so pointless.
[Samsung Galaxy Nexus] Emilius:
r169 @384 the app doues not remember min/max cpu and scaling governor after reboot anymore for me. I am on Paranoid Android. Also what about vibration control? Any chance to ad that in to the app?
[Samsung Galaxy Nexus] Hanny:
hello guys who have signal/data drops , i have just done something to my phone and it has been 6 hours that i havent seen a drop of either thing.

(before doing this, i had 3 drops in 4 hours after flashing 169)

im now with franco 169 and AOKP b37

my baseband is SC04DOMKKD and did not change to XXLA2

where my RIL is XXLA2 which comes together with AOKP

therefore they are mismatched, but this is probably not the root cause based on my information collected​

this seem stupid, and i would like to test it myself for two days before i report this "workaround", however i had a random thought - why dont i let more people try it and report together?

therefore please allow me to disclaim that this is NOT A CONFIRMED REPORT but just to invite more users who got their signal/data drops to test with me together

this is what i have done:

1) *#*#4636#*#* -> phone information -> turn off radio (and wait 20 sec) -> turn on radio (until internet connected and bars are blue)

2) power off phone, unplugged

3) pull the SIM card out

4) power on the phone without SIM card

5) let the boot complete and all necessary apps started (as normally you power on)

6) power off phone completely

7) insert the SIM card correctly

8) power on

9) see if you got the drops and report

thanks for your attention! i also hope that i will not get further drops and will report back. :) cheers
[Samsung Galaxy Nexus] DarkGruf:
It feels good not to be alone :) Perhaps a bad interaction rom/kernel. I'm using Modaco, what is your rom ?
[Samsung Galaxy Nexus] jnr21:
It's cm9 issue. Set min/max freqs via performance settings (not franco app).
[Samsung Galaxy Nexus] franciscofranco:
Gamma settings are not working on r169, I confirm that. I will fix it in a few hours. Other people saying "amg battery life is ****ed halp plz" I just laugh...nothing changed besides code fixes and crying that in less than 10h of usage makes me laugh so hard :)
[Samsung Galaxy Nexus] DarkGruf:
And about color multipliers and "green screen" with multipliers >240 ?
[Samsung Galaxy Nexus] Emilius:
I see. Tnx man
[Samsung Galaxy Nexus] franciscofranco:
Dunno about that, I have to check.
[Samsung Galaxy Nexus] Theshawty:
As far as every nightly go for me, it seems that they get better and better with each build ^^
[Samsung Galaxy Nexus] retareq:
I agree. I'm at 166 and yesterday I went to a wedding with full charge and tortured the hell out of my phone. Video recordings, taking pictures, phone calls and text, facebook, browsing and later some internet music streaming too. Almost 4 hours screen on and still came home to 30% battery. I decided I'll try to kill the battery and do a wipe battery stats so I started watching hd videos on youtube and added another half hour and still had juice left. I just gave up and charged it.

Is it okay if I use the fk icon as my avatar ?
[Samsung Galaxy Nexus] Horoscope:
Hey guys,

i installed the Franco kernel for the first time on my Nexus, I am on CM9 latest build,

kernel installation went smooth but every now and then i see sort of on my phone display.. i see fonts and images split or broken...

why does this happen ?
[Samsung Galaxy Nexus] Hanny:
Do not install 512 mhz GPU version. Get the 384 one. Next time please do a search lol.
[Samsung Galaxy Nexus] David Horn:
Very impressed - now on fourth day of light use on this kernel and phone's still going! Mix of voice calls, bit of web browsing, Squeeze Commander use and email / Gmail sync.
[Samsung Galaxy Nexus] drawde40599:
Pulling the sim is something recommended by At&t when there are data issues that could be the "fix"might explain y I don't have data issues,i pull my sim before I fastboot the stock boot.img .....before I flash this kernel almost everytime ... ( necessary, NO !!! But I rairly ever have issues....)

---------- Post added at 06:59 AM ---------- Previous post was at 06:54 AM ----------

Franco can u say if its the kernel or the app? ( I don't wanna flash 169 if 170 coming in few hours ....I'm lazy; )
[Samsung Galaxy Nexus] craz6r:
Close to your setup but with r163. I haven't had any data/ signal drops. T-Mobile . None, besides where my low signal areas are. Ril matches
[Samsung Galaxy Nexus] Langduscher:
If only I could have the low wifi voltages & v384 power saving stuff from r156, combined with the reverted patches from #999/ r160, plus the r163 stuff to make transitions as smooth as they are now... :rolleyes:

I ××××ing wish I could code that :o (yes my Gnex takes everything I can throw at it, it loves it :D). I'd happily pay $$$ for that combo :cool:

Some really good sh!t in the past nightlies Francisco, thanks for having us experiencing all that good stuff whilst trying to make a great kernel even better each update!
[Samsung Galaxy Nexus] franciscofranco:
Kernel. To fix one of the warnings I gave a variable const status (because the function was trying to equal a const u8 and a u8 arrays) and the compiler was crying. I'll fix it later, got better things to do now.
[Samsung Galaxy Nexus] Reviz:
no signal with r169, now using trinity with no issues
[Samsung Galaxy Nexus] drawde40599:
Cool thanks, ya me 2, suns up; ) . Thanks Franco
[Samsung Galaxy Nexus] franciscofranco:
Wow this GetRil app is nice. I bet most of the users with data **** have RIL/baseband mismatches.
[Samsung Galaxy Nexus] dpaine88:
I've been researching kernel govs, mainly interactive and on demand.

Is there anything tweaked in Franco's OnDemand that would make it behave differently than the general governor descriptions I have been reading?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CMNein:
Mine have always matched, I've gotten the data drop when coming off of a wifi connection a couple of times, but usually with "experimental" kernels. I think there's too many bloody variables contributing to this data drop that many have. If my phone did it on a regular basis it would be in several pieces.
[Samsung Galaxy Nexus] mistermojorizin:
i mean settings-->display-->brightness
[Samsung Galaxy Nexus] CerB:
Nope your wrong there :-)

XXLA2 AOKP 37 your 169. Often data drops, very short but also very annoying :-)

Sendt fra min Galaxy Nexus med Tapatalk2
[Samsung Galaxy Nexus] franciscofranco:
Install a stable rom, AOKP's nothing but unstable.
[Samsung Galaxy Nexus] renna1992:
me too, matching ril and baseband but data drops
[Samsung Galaxy Nexus] mistermojorizin:
when you check, check it out with brightness turned up to 100%. I'm sure you'll see what we're talking about with the multipliers turned up
[Samsung Galaxy Nexus] Basian Mile:
So, after i tryed this idont see any differnce.

Its like before. but i havent seen any Drops here on my Pgone.

But!!! I always have Gray Bars and when i turn on 3G its getting Blue. When i turn on WiFi its getting Blue too. Is that normal?
[Samsung Galaxy Nexus] franciscofranco:
Eheh indeed, something is doomed here :p I'll see what I can do.
[Samsung Galaxy Nexus] kompressorgpl:
Nice tip! Wich ROM do you use/recommend?

Um abraço desde Vila do Conde!!!
[Samsung Galaxy Nexus] navodwickra:
CM9 FTW!
[Samsung Galaxy Nexus] The Gingerbread Man:
He recommended a rom called Rascream ( think that's correct spelling ) its a cm9

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] dpaine88:
As far as I know Franco is involved with Team Liquid

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rascarlo:
No it's not.
[Samsung Galaxy Nexus] Theshawty:
I too use GetRIL to check what the status is and I do this after every ROM flash to see if the current RIL has stayed.

I wish I could say if I have the real data drop issue or not as, again, my carrier has ****ty reception where I live. It might just be a connection drop because of it. It's strange, though, that I don't seem to have a higher signal reception than -75dBm. Maybe it's because of the phone, because I've seen people with other phones and in great conditions have like -30dBm.

I can personally recommend CM9. Fast, great, stable and made by the notorious team douche :)
[Samsung Galaxy Nexus] The Gingerbread Man:
My bad :o

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] fatappel:
Had constant data drops when I would leave a wifi area. data bars would not go from grey to blue until I rebooted. this was until I updated my baseband radio about a month ago to UGLC1. All of the google play store phones shipped with European radios but I am on T-Mobile USA and even though my RIL's do not match, I now get no drops. Just a heads up that RIL's do not have to match to have great results. Love your work franco. 169 working great as I leave omap gamma at zero anyway. Thanks
[Samsung Galaxy Nexus] drawde40599:
Liquid 1.4, has been working flawless for me couple weeks now, if u like AoKP u will love liquid, CM9 is OK, but there really behind when it comes to features if that's ur thing and even though there stable cm9 don't have a " milestone " yet so I don't think its what franco meant by stable ....
[Samsung Galaxy Nexus] dpaine88:
As my testing has gone..I found Interactive and OnDemand spend nearly identical ratios between min and Max freq.

I also tested the effect of turning the screen on on both govs to see how much they ramped up since I know interactive ramps up automatically when you turn the screen on. My testing found that both govs go to Max speed for 1 second after you unlock it.

So basically for my use, there is no reason not to use interactive.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I recommend rascream or liquid, both are high quality roms.

Anyway for what its worth, and I can't promise that this is true (at least until I release it for testing) I think the increase in data drop reports *might* be caused by a wrongly set OPP tables when I added 192mhz step. I'm "fixing" it to see if this helps.
[Samsung Galaxy Nexus] kompressorgpl:
Liquid as portuguese language?
[Samsung Galaxy Nexus] dpaine88:
Never thought I'd say this but with all these data drops...damn it feels good to be on CDMA

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Prod1702:
Loving the kernel. This is the only kernel i have used since i got my GN a few weeks ago no problems here. I also do not have any data drops at all. with any of the versions of the kernel.
[Samsung Galaxy Nexus] CerB:
Thanks, only problem with liquid is missing language, and ras is pretty boring feature wise

Sendt fra min Galaxy Nexus med Tapatalk2
[Samsung Galaxy Nexus] Diger36:
/offtopic

Thanks Rascarlo. Been running your ROM for two days now and liking it. Very stable!

/end offtopic
[Samsung Galaxy Nexus] nikulogical:
Rascarlo.. where can I find your rom?

Also, Franco what do you think of paranoid android?
[Samsung Galaxy Nexus] kackburt:
I switched from r165 to r166 a few a days ago. Used it for a day without any glitches and after a reboot this morning I am experiencing signal drops aswell, dunno why. Newest baseband XXLA2.
[Samsung Galaxy Nexus] jnr21:
It has english only.
[Samsung Galaxy Nexus] Antob125:
GetRil doesn't support Galaxy Nexus (Toro) only maguro :(

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kompressorgpl:
Thank´s... It's a petty...
[Samsung Galaxy Nexus] BrUhNiGGs:
Got good battery life yesterday. Not impressive but I'd say the best I ever had.

Running 166 with full power mode (1344 Max and 729 min, interactive governor, SR on)
[Samsung Galaxy Nexus] Basian Mile:
I can recommend SlimICS.!! Its in Version 3.8 now and its great. With Francos Kernel its just awesome.