yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] johno168:
WoW! Really?!!? I hardly get 2 hours screen with turtle 700/1000. Any screenshots to back 3.5+?!?!
[Samsung Galaxy Nexus] opensourcefan:
Yep 3hrs screen time is the norm for me. I think this may have been Gazelle since I was only at 9% battery.

View attachment 895490

View attachment 895491
[Samsung Galaxy Nexus] johno168:
Damn!

10char
[Samsung Galaxy Nexus] Stretlow:
It purely depends on your brightness level. I can't use that auto brightness anymore due to that stupid lag when being unlocked.

I have been having the brightness on just over 50 percent and been getting about 3 hours screen on time.
[Samsung Galaxy Nexus] johno168:
I'm using auto, don't get the lag too much. usually only when it goes to sleep for more than an hour
[Samsung Galaxy Nexus] Stretlow:
But it's there and not present when you switch it off. It's annoying and disappointing.
[Samsung Galaxy Nexus] minipaolo:
franco, would you suggest slight undervolting or it is partially useless?
[Samsung Galaxy Nexus] Nebucatnetzer:
This isn't so special since you're the most time connected to a WIFI. That helps really a lot.
[Samsung Galaxy Nexus] Arcadia310:
Is there an update.zip for the newest kernel? If not can anyone tell me how to install this in terminal?
[Samsung Galaxy Nexus] johno168:
Yes download kernel from link in OP and then flash it through recovery.
[Samsung Galaxy Nexus] minipaolo:
I don't know why I have always heard that, but I have better battery life when connected to 3G only. (I'm under wifi 99% of the time)
[Samsung Galaxy Nexus] mgear356:
Seems like under volt is not working in 16.2
[Samsung Galaxy Nexus] laserprom:
turtle 700/1000

screen 25% wi-fi on ,

24 h on battery 5.19 h of screen
[Samsung Galaxy Nexus] atsavlis:
Bussy running v16.2 and trying to read and understand how Custom Voltage from ezekeel works.

Unfortunately havnt found it yet, can anyone give a small description?? Is there anything that needs to be done from our side??
[Samsung Galaxy Nexus] minooch:
Seriously! It's sitting there on my server - Go grab it :D
[Samsung Galaxy Nexus] atsavlis:
I think I found a bug in 16.2....

I use set CPU to adjust freq and governor, and when I set it to 400 - 1000 gazele, the CPU drops down to a 200mhz frequency...

Funny thing is my scaling options dont show any 200 frequency, they all start from 400.

Can anyone else reproduce this, or is it just me?
[Samsung Galaxy Nexus] Shetlander:
I use No Frills and have just run Antutu and System Tweaks and when the cpu is throttled it drops from 700Mhz to 200Mhz. I set the min to 400Mhz so it would appear you are correct.

Edit - Unless it is a throttling thing. Half way through the Antutu test it is now using 400Mhz as the min as it was set. Even with the min set to 700Mhz, when been thermal throttled it drops to 200Mhz! Never seen that before.
[Samsung Galaxy Nexus] drawde40599:
using Franco's app to set settings, and it dose drop to 200 for sec in set cpu maybe y feels laggy
[Samsung Galaxy Nexus] Nebucatnetzer:
Really? For me it's the total opposite. With I can get nearly 4h screen on time with 3G not even 3h.
[Samsung Galaxy Nexus] isinisterx:
how can I lower my phone idle? I just woke up and checked and its at 27%.

Is this normal?
[Samsung Galaxy Nexus] minipaolo:
you're not the only one saying that! :)

I've flashed the new radio... let's see if something changes.
[Samsung Galaxy Nexus] psycho2097:
So dig this: found out that polish guy at work had a nexus.we beamed,naturally! Then he was like,wow how is yours so fast? And how do you have 4 way lock? And blue navbar icons? And SO FRIKKING FAST? And I told him all about the awesome world of custom roms and kernels? Then I unlocked ,rooted and installed aokp n Franco's!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] laserprom:
If i undersand corect uv is setup by defult.franco is this corect ?
[Samsung Galaxy Nexus] ratson:
same for me, whatever governor I choose
[Samsung Galaxy Nexus] atsavlis:
Doesnt get better than this....

About 3 hours screen time, plus went to a basketball game last night, and used the camera and photo uploading quite allot.... Keep it up Franco, we getting there!
[Samsung Galaxy Nexus] franciscofranco:
Now that's something I've never seen before O.o... I'll take a look later I guess.

Undervolt works as it always worked before, just use my app or setCPU to take care of the voltages.
[Samsung Galaxy Nexus] THE_KINGDOM:
Where can I download 15.2 from? Always the most current nightly kernel is posted on the site.
[Samsung Galaxy Nexus] franciscofranco:
Yes, I don't support older versions, been my policy since I build Android kernels. #16.2 feels the best release for me, mostly bugfree where older ones had slight bugs.
[Samsung Galaxy Nexus] Antob125:
When on wifi, does it make a difference turning off LTE since you're Lready connected to wifi?
[Samsung Galaxy Nexus] jdk82:
AFAIK the LTE radio is automatically turned off when you are on wifi.
[Samsung Galaxy Nexus] loudaccord:
I like 16.2 a lot. Been on it for about an hour and nothing but good so far. I did get one SOD with the last kernel but that was with Dynamic Hotplug enabled. I'm going to leave everything as is, no UV this time.
[Samsung Galaxy Nexus] sishgupta:
Thank you for 16.2.
[Samsung Galaxy Nexus] mgear356:
or is it because of the new undervolt thingy? How to enable undervolt again?
[Samsung Galaxy Nexus] franciscofranco:
What? Undervolt is working just fine.
[Samsung Galaxy Nexus] poopooface:
Updated to 16.2 this morning and thus far all looks good! I like 400 as the minimum although I never had any problems running 350. A full hour of screen on time and music listening and I'm still at 91% on my Chinese extended battery. Nice.
[Samsung Galaxy Nexus] alfa71omega:
CPU clock

hi Franco, first .... great job.

second: I'm not able to fix the cpu clock to 1200. everytime I boot the phone it starts from 700 mhz instead 1200 mhz. my rom is foxhound.

Any ideas?
[Samsung Galaxy Nexus] Vangelis13:
1. Read the last couple of pages.

2. Check that your rom doesn't have a set at boot setting under performance or whatever they might call them. Uncheck that option.
[Samsung Galaxy Nexus] drawde40599:
Settings stick here on aokp
[Samsung Galaxy Nexus] Vangelis13:
1. Always read a couple of the last pages before posting a question.

2. World-of-nexus.com
[Samsung Galaxy Nexus] Arcadia310:
I'm going to flash this kernel soon! Do I have to be on a 4.0.3 from or is it okay to be on 4.0.2?
[Samsung Galaxy Nexus] DonXoB:
You need a 4.0.3 rom.
[Samsung Galaxy Nexus] cancerouspete:
Originally Posted by atsavlis

I think I found a bug in 16.2....

I use set CPU to adjust freq and governor, and when I set it to 400 - 1000 gazele, the CPU drops down to a 200mhz frequency...

Funny thing is my scaling options dont show any 200 frequency, they all start from 400.

Can anyone else reproduce this, or is it just me?

as a foreword, im cdma (but this matches my issue) I see this, but i'm getting a weird interaction between this and bugless beast 2/7...right now it is flip-flopping between the 1200 i chose, and 200 (400 is selected)...flips 1 a second on Gazelle

i turned off set-on-boot in francoapp because it wasn't allowing me to change the governor after bugless beast introduced a CPU settings in developer options...from in there i can change the gov and speeds fine, with the exception of the flip-flop

Quick observation, just after typing above, i turned my screen back on to check again, and it was at 1200 for a couple seconds, then dipped to 400 for a few seconds, then back into the 1200/200. i dont have any of the hotplug options turned on, nor am i UV'd

(no logcat messages, but i'd be glad to personally email you a full cat if you think you'll find something)
[Samsung Galaxy Nexus] michie:
Hey Francisco, thanks for the kernel!

one question, is MHL-USB a kernel or rom dependent feature ?

Cant get it to work here :(
[Samsung Galaxy Nexus] neverhappy:
on 16.2 since a few minutes after Franco announced its release. I am CDMA, francoturtle, 400-1200, hotplug.

It has been working flawlessly and battery life looks really good so far.

I started with a fully charged stock battery. I was on 16.1, 700-1200 dynamic_hotplug for about 11hrs.

I was at 75% when I switched to 16.2. I kept the same battery that was at 75%. I'm at 35% 16.5hrs later on 16.2.

Reflecting back when I got this phone in Dec. I was getting about 5-7hrs. So things are dramatically better now.

PS. I'm not seeing the drop to 200Mhz. System Tuner is showing 400Mhz as lowest drop.
[Samsung Galaxy Nexus] franciscofranco:
Thank you. That is some rare bug, never seen that before to be honest, and I have 0 idea of what causes it. I can have my settings stick through reboots with Set on boot on my app, so does some of my testers, so I don't know what goes on there. I'll check the strange 200mhz issue tonight.

What is MHL-USB?
[Samsung Galaxy Nexus] jhericurls:
Been running 16.2 for over 8 hours and working great so far. Over 2 hours screen time and 40% battery left.
[Samsung Galaxy Nexus] michie:
Micro usb to hdmi adapter, sorry forgot the hdmi part
[Samsung Galaxy Nexus] sishgupta:
This should be working stock out of the box.

Link your adaptor. If it is not a powered adaptor it may likely not work. Your MHL adaptor should have two MALE plugs and one FEMALE. Male HDMI to your TV, Male micro USB to your phone, FEMALE micro usb which is power input.

I am still waiting for my MHL adaptor to come in the mail but I know it works with stock samsung devices.

EDIT: lol and by out of the box i mean i think you need 4.0.2 update OTA ;)
[Samsung Galaxy Nexus] michie:
ok i just got it to work for 0,5sec, i have the adapter cable from samsung and it SUX, it doesnt even fit tight, it falls out of the micro usb slot itself.

Conclusion its not kernel related etc, guess i have to send the damn thing back :s

EDIT : Yes its the cable, if i really push it hard in the micro sub it works, am going to get a replacement. thank for the info anyway!
[Samsung Galaxy Nexus] daandman:
I bought the app & usually change my settings through that now & sometimes forget to change it on SetCPU, so it may be like 400-1000 on Franco app & 700-1200 on SetCPU. Does that mess with it if I forget to change it on both?
[Samsung Galaxy Nexus] sishgupta:
Curious...Samsung sells/makes these? I've seen knockoffs with Samsung logos but they are clearly no name Chinese rips.

Also is yours powered?
[Samsung Galaxy Nexus] minipaolo:
Must be on 4.0.3
[Samsung Galaxy Nexus] zerozoneice:
is BT not turning on a known issue on #16.1?

running modaco 4.0.4
[Samsung Galaxy Nexus] franciscofranco:
No, works perfectly.
[Samsung Galaxy Nexus] Baguett:
Getting very low scores in AnTuTu with 16.2 on AOKP. is it maybe becuase i use the cpuconfiger that is built in AOKP? should i switch too setCPU or something?
[Samsung Galaxy Nexus] nkostis:
git

hi, i noticed that git has stayed at what seems to be 16.0. Any chance of pushing your 16.1 and 16.2 changes to bitbucket? thanks!
[Samsung Galaxy Nexus] franciscofranco:
I pushed #16 changes 3 days ago. New code will be pushed when the code is ready to be published.
[Samsung Galaxy Nexus] sluflyer06:
I'm running the same combo Antutu scores are just fine. (7,044)

I use Franco's app to control settings.
[Samsung Galaxy Nexus] Baguett:
Ok, guess it is some problems with the cpu-controller built in AOKP.

Can't really buy things from market as i am only 17 years old :(
[Samsung Galaxy Nexus] sluflyer06:
I never had a problem using setCPU, try that? Also I believe theres a alternative place to buy his app listed somewhere in this thread.
[Samsung Galaxy Nexus] nikulogical:
any advantages to OCing to 1350 as opposed to 1200?
[Samsung Galaxy Nexus] delvirtud:
Not to be redundant (well, maybe a little), but I am experiencing the same thing. Over a period of time in CPU Spy, I was noticing that my phone wasn't going into deep sleep very often and while it was awake it split time between 1200 and 400. Looking at it in real time with System Tuner, I could see that every 2-3 seconds the CPU would spike to 1200, stay there for about 2 seconds then drop back to 400. This was using Gazelle. When I used turtle, the issue went away.

Using GummyNex with your 16.2, hotplug enabled.
[Samsung Galaxy Nexus] Baguett:
Tried it twice now, did not get better. i heard about someone talking about that AnTuTu had a script that may be blocking one fo the cores, named init.d or something, but i guess i would get even lower scores then?
[Samsung Galaxy Nexus] Arcadia310:
I'm new to Franco Kernel and just flashed it. Can anyone explain to me the different CPU governers and what they mean? Also what are some good voltages to set it at?
[Samsung Galaxy Nexus] Baguett:
* francoTurtle is made for battery hungry users. Its the default governor and it will boot at 700/1000

* francoGazelle is made for performance hungry users while trying to maintain a reasonable battery life

Also i've read that on-demand and interactive is almost the same, but that interactive is faster to speed up the cpu freq. when needed. Performance explains itself.
[Samsung Galaxy Nexus] nic85:
someone can post custom uv for 400mhz?
[Samsung Galaxy Nexus] darrendm:
900mV is what I'm on, not checked if I can go lower.

I'm not really sure if UVing makes that big of a deal after reading most of the posts on this thread.
[Samsung Galaxy Nexus] ChongoDroid:
Getting crazy battery life with pauls 4.0.4 pre bakes and 16.2

400mhz is the happy medium!!
[Samsung Galaxy Nexus] drawde40599:
Dose the phone feel fast / faster??? Those scores never the same IMO waste of time judging speed by any of those apps, if it feels faster than it is faster: )
[Samsung Galaxy Nexus] radekg7:
I have set 775mV, when I set up lower I have restarts.
[Samsung Galaxy Nexus] yyz71:
Damn Pauls 4.0.4 and 16.2 kernel phone is wickedly fast and smooth, and as for benchmarks who cares!! I end up getting different scores anyways.

sent from pimped out galaxy nexus 4.0.4 :)
[Samsung Galaxy Nexus] ratson:
I had a hard freezing, display was not coming back I had to pull the battery. after reboot I was looking for /proc/last_kmsg but there were no such file. should it be there? is there any other way how I could help you fix the problem? #16.2
[Samsung Galaxy Nexus] franciscofranco:
Yes, tell me your full stats, clocks, UV, settings, rom, basebands etc
[Samsung Galaxy Nexus] pesc96:
you have to be on 4.0.3 otherwise it don't boot

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] b33zu:
Here's the big issue with this kernel. Franco keeps changing the settings. Which for some its good and others its bad. For example 15.1 worked amazing for me and has been slowly going down hill from there. For others 16.2 is decent and others its not and there's lock ups and freezes. He really needs to make a tutorial that has 4 different setups with specific settings everyone can choose from. That way the no one will wonder what other peoples settings are.
[Samsung Galaxy Nexus] jdk82:
While I agree that the kernel is changing quite a bit, that's kind of the point of development ;) I think (and correct me if I'm wrong Franco) he's going for finding a happy medium that will work well on the majority of the devices. For the second part, I don't see how that's his responsibility. Anybody who can use the search function and/or read the this thread can figure out how to test the various settings.
[Samsung Galaxy Nexus] opensourcefan:
To avoid this kind of frustration one needs to create a reaction time to new versions of anything. In our fun android world you can be flashing constantly if you don't apply some discipline. In respect to ROM's I wait about about 3-4 days before flashing the next, that gives soak time. For kernels I usually skip one revision if possible and often go backwards and stay until I really see a reason to go forward.

Just because things are updating around you doesn't mean you have to bite and frequent updates are not a bad thing... as long as there's a stable version somewhere.
[Samsung Galaxy Nexus] jdk82:
I'd never heard of that ROM before you mentioned it (was happily on AOKP), have been using it for an hour or so and it is fantastic! Thanks for mentioning it.
[Samsung Galaxy Nexus] kin24173493:
franco,

your kernel is supported KSM? (kernel samepage merging)
[Samsung Galaxy Nexus] franciscofranco:
Well that ain't my job. I do whats best for progress, I can't do all the work by myself, users have a part to play, I'm not gonna write a tutorial with 23492349 different setups, thats for sure. Every user has a different way to use its device, so they have to adapt themselves to the changes I keep introducing, and that's not going to stop anytime soon. If you don't like it there are plenty of other kernels to choose from, feel free to try :)

Aye aye captain.
[Samsung Galaxy Nexus] psycho2097:
Franco as someone else reported I have a weird bug to report. My freq goes to 400 when I am plugged in. And gets stuck at 400sometimes.And phone lags like crazy...I never set my minimum to below 700,ever. A couple of times it even went to 200,like another guy reported.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Manya3084:
nothing is wrong with the kernel, it's the users setup....or enabling dynamic hot plug has thankfully been removed.
[Samsung Galaxy Nexus] drawde40599:
Ya not true (: this 16.2 is very laggy for me with stock setup no extra settings turned on stable and 16.1 working best for me
[Samsung Galaxy Nexus] opensourcefan:
Bump the min to 700, use turtle and set at boot, working awesome for me. Fast and smooth.
[Samsung Galaxy Nexus] ratson:
#16.2, 400-1350, no UV, ondemand, aokp M3, XXKL1
[Samsung Galaxy Nexus] franciscofranco:
Laggy? 16.1 and 16.2 are 99,9999999% equal, the only thing that changed is in the changelog, and that doesnt make anything laggy.

Try with my stock settings.
[Samsung Galaxy Nexus] renaud:
Francisco,

I think you should do like me and release kernels with a increasing number scheme and keep older ones. This allows people to find where it broke for them, and increase the odds you find the bug your are searching.

Doing it the BSD way with testing/stable/current scheme allows people to test and report with more accuracy.

Given you now have the most popular kernel, this will help everyone

That's just my 2 cents.
[Samsung Galaxy Nexus] philipseth:
16.2 kernel is absolutely great with Paul's IR11 ROM. thanks to both
[Samsung Galaxy Nexus] samizad:
#16 series have been very smooth and no lag, even with 400 Mhz francoturtle. Thanks Francisco.

I don't know what you did but my phone loves 16.2 much more than 16.1, batterywise.
[Samsung Galaxy Nexus] blackdub370:
16.2 is laggy, gta 3 laggy ... !! with 13.1 no lag !!!
[Samsung Galaxy Nexus] jan-willem3:
Change governer to interactive.
[Samsung Galaxy Nexus] blackdub370:
I did ... still lag ..
[Samsung Galaxy Nexus] collindubya:
is this kernel compatible with the AOKP M3 Rom?
[Samsung Galaxy Nexus] MarcLandis:
Yes sure as it is based on ICS 4.0.3

Marc
[Samsung Galaxy Nexus] Tubes6al4v:
I liked Franco 's reply that we should pay a bigger role in helping people out. I built the initial xda wiki page for just that reason. Let's upload previous versions there, suggested setups, etc

http://xdaforums.com/wiki/Samsung_Galaxy_Nexus/GT-I9250/ROMs/FrancoKernel

Franco, maybe you can add this to the op to get some more work going on there.
[Samsung Galaxy Nexus] poopooface:
As for the issue of instructions, repetitive questions, ease of adoption, etc., it seems to me that there are a few main issues that accout for 99% of all of these annoying, repetitive complaints. It seems that it might be helpful to prominently add a few clarifications to the OP in order to keep the lazy people from defecating all over the thread.

1. I know that 4.0.3 is in the thread title, but for some reason people don't read titles. Might want to say in the OP specifically that 4.0.2 is NOT usable with this kernel.

2. Most people who ***** about lag and decrease in battery life are doing so based on results that are convoluted with them ****ing with their phone in other ways... If you do decide to use a stable, test, current release and leave them all on your server for download, you could clearly post in OP that if users have a decrease in battery life or unexplained lag, they should go back to the stable version. Note that if that doesn't solve the problem, it's user error involving a rogue app or something, so don't bother the rest of us.

3. In the OP should be clear instructions not to bother the rest of us about reboots, etc. until they have tried your recommended voltages and governors (post these in the OP as well).

4. One of the main things to put on the wiki should be a list of ROMs on which people have had good experiences. Franco would not have to do this as the users would contribute the names of working ROMs. That way people could stop posting asking whether such and such ROM is supported.

5. In the OP you might want to link to helpful posts in the thread on various topics, because many people don't use the search function or get too many results when they do.

I think those suggestions could help ease of adoption and end all the repetitive questions.
[Samsung Galaxy Nexus] yyz71:
Half the time is user experience and not able to read what build the kernel is made for!!!

sent from pimped out galaxy nexus 4.0.4 :)
[Samsung Galaxy Nexus] loudaccord:
Confirmed 200mhz, I didn't change any settings from stock

Yikes, sorry for the giant pic, posting from my phone.
[Samsung Galaxy Nexus] drawde40599:
If stock Android kernel runs at 350 with no lag Franco should be able to also at 400 ,16.2 looks like he trying something different running 400, so if 400 laggy just bumping to 700 dose not fix anything just skipps a possible issue .

+ I was running gazzele 350/1350 with no lag whatsoever on 16.1

---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------

They might be 99999% the same 16.2 is running bad lots of hicups, 16.1 runs flawless .Stock settings yes I did not change anything.
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the advice, I will definitely think about it ;)
[Samsung Galaxy Nexus] ChrisM001:
Hi Francisco,

could you try to improve the weak GPS signal with your kernel. That would be a great improvement over the stock kernel.
[Samsung Galaxy Nexus] franciscofranco:
Today is my gf's brother birthday so I will be offline for a while. Later I will read the big posts from some of you and reply accordingly.
[Samsung Galaxy Nexus] dyndragon:
I don't know if this is a kernel thing....but I've sort of noticed the same problem--weak GPS. Not sure if it has always been like this or only recently though. Franco I'm sure will say if it might be kernel related or not.
[Samsung Galaxy Nexus] aimetti:
I'm sure this has come up before but not on PC so perhaps someone could give some info. I was having issues with settings sticking. I deleted the init.d folder and now oc and governor stays put but my UV resets on every boot up.

On 16.2 and newest app update.
[Samsung Galaxy Nexus] ChongoDroid:
Strange I get crazy fast GPS even in semi remote areas. I'm in Vancouver on Fido and I get a lock (10M) in around 2 seconds . On 4.0.4 and I used GPS status to lock 8 sats before hand.
[Samsung Galaxy Nexus] franciscofranco:
Yes, UV settings are not set to work on reboot. I disabled that with my app, I don't want people to have boot issues because of mistakenly set UV values.
[Samsung Galaxy Nexus] lafrad:
I had really awful GPS and Location fix experiences with the Slim rom... moved to CM9 and 16.2 and location lock seems to be ridiculously fast.
[Samsung Galaxy Nexus] aimetti:
Ahh gotcha.

Thanks!
[Samsung Galaxy Nexus] sishgupta:
I use the GPS almost daily and its super fast for me so I don't know why people are having problems.

I dunno if I updated my sig but I'm on 16.2 and AOKP M3.

Also no lags or stutters. 16.2 is my fav release since...13.1.
[Samsung Galaxy Nexus] khenderick:
If you get weak signals (phone, wifi, gps, ...), you could try some radio's that are posted in various topic in this forum.

About the kernel; I'm running for 1d 19h now. This kernel is epic.
[Samsung Galaxy Nexus] AfroCreame:
I keep coming back to this kernel. Thanks for your hard work!