yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bleeeeeeek:
I dunno if its just me or what.. but I've gotten the best performance out version 12.. so I'm back to that.. I got a boot loop with 14.2..
[Samsung Galaxy Nexus] mike216:
Franco I got the best battery life I've ever seen on 14.1 after I let it sleep all night and seen I was at 94%! Do you suggest to go to 14.2 anyways? Any help would be greatly appreciated

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] DarkKnight62:
i actually deleted my download path so it didn't work. i put /mnt/sdcard/Download and it doesn't download into that directory. it always downloads to /mnt/sdcard. i've tried mnt/sdcard/Download and it still goes into the sdcard.
[Samsung Galaxy Nexus] b33zu:
Yes that's with conservative
[Samsung Galaxy Nexus] b33zu:
I disagree the clock settings turned down with conservative is a good mix. I recommend it for people right now. The phone is still more then fast enough even with he lower clocks. No body even with this phone needs those way over locked speeds. ;)
[Samsung Galaxy Nexus] BFirebird101:
I'm still confused as to why we can't clock our processor at 1500 since it runs that way stock? Will someone care to elaborate? :)
[Samsung Galaxy Nexus] b33zu:
I believe the reason this is not downloading to where you want is because the dev made it download specifically to the SD card on purpose. When you flash kernels it needs to be applied to the root directory anyways for flashing. ;)
[Samsung Galaxy Nexus] bobby janow:
No it doesn't.
[Samsung Galaxy Nexus] Gahh Its Lee:
Because it's 1.2 stock.
[Samsung Galaxy Nexus] BFirebird101:
Oh from what I read our processor is supposed to run at 1.5 but they underclocked it for battery life
[Samsung Galaxy Nexus] Gahh Its Lee:
I genuinely believe if this phone could pull off 1.5 they'd have it booting it at 1.5. Also why would you need it? I can run my phone at 700 and its faster anything else.
[Samsung Galaxy Nexus] TEK112:
The TI OMAP 4460 is a 1.5GHz processor underclocked to 1.2GHz for battery life, but mainly for stability. Just like the OG Droid which came with an ARM A8. It was factory set to 550MHz, even though it was very capable of 1.25GHz and was designed to run at 800MHz. Processors are like cookies, while they all have the same ingredients and are baked the same, they all don't come out of the oven the same. These tolerances cause manufacturers to play it safe and underclock. If all processors ran at their full potential there would be no way to overclock.
[Samsung Galaxy Nexus] DarkGruf:
A / is missing the right path is : /mnt/sdcard/Download/

---------- Post added at 09:26 PM ---------- Previous post was at 09:10 PM ----------

In a 700-1350 scenario would you recommend an other governor ?
[Samsung Galaxy Nexus] TEK112:
I have had better luck with 350 - 1200 on demand. The 1350 slot IMHO is unnecessary.
[Samsung Galaxy Nexus] mike216:
I'm on 14.1 and everything especially battery is outstanding! Is it highly suggested to go to 14.2 or should I be on on 14.1, thanks

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] Elganja:
I updated just for the pure fact I want to be on the latest version... probably an ocd thing... lol
[Samsung Galaxy Nexus] EyeOfTruth:
From what I have read currently it does not run stable at 1.5 ghz. I remember reading about some people trying to get it up to that speed but for some reason it would not run well. Which is why currently the max for most kernels I have seen is 1.35GHz. Not that you need that speed on the phone for the average user. But if you want to use your phone more as a computer it is nice (especially if you install debian on it or a full linux distro). But its all just a matter of time you figure by the time this phone matures you will probably see kernels that run up to about 2ghZ Which is not that far of a stretch when the recommended by TI is 1.5
[Samsung Galaxy Nexus] franciscofranco:
Update to 14.2. The UV table is exactly the same, but it will be more stable because I did some **** in the file that takes care of the voltages in 14.1. Now in the 14.2 it's fine ;)
[Samsung Galaxy Nexus] Gahh Its Lee:
Since 13.1 is actually had to up my voltages 125 for 1200 and 75 for 700... UV is so frustrating. Is it just my phone or the kernel that caused the needed boost?
[Samsung Galaxy Nexus] jake:
Interesting 10 char
[Samsung Galaxy Nexus] CDuke619:
Just had a reboot on 14.1 with conservative on 700 1200 and I see there is a update for stability. Hopefully whatever caused my reboot is fixed
[Samsung Galaxy Nexus] drmp3z:
Question:

I flashed 14.1 but want to flash 14.2 over 14.1. What are the steps to take ?
[Samsung Galaxy Nexus] EyeOfTruth:
Just format the cache and dalvik cache and install 14.2 over 14.1
[Samsung Galaxy Nexus] mark manning:
Same way, flash from recovery. Wipe cache and dalvik cache first tho
[Samsung Galaxy Nexus] cc16177:
What is the experience so far with 14.2? I'm having fantastic luck with 13.1 and I'm scared to update haha

I've read the past 4-5 pages so I know what has been said so far but im looking for more input.

I'm currently running at 350-920 with interactive/hot plug and slight undervolted and getting great battery life.
[Samsung Galaxy Nexus] EyeOfTruth:
My only complaint seems like it really could be a nice feature but not if you want to run 350mhz. Is the fact that on version 14 it is either in one of 3 states. Deep sleep, your min processor setting, or max. It do not scale, which is ok but it almost makes the 350 mark pointless because when your using the phone I doubt it will be able to be in 350 most of the time. But I haven't used my phone enough to know for sure yet. I am running 350/920 convervative with about 100 mV uv and hot plug. With this new setting it would be best to probably install cpuspy and monitor it for 24 hours after updating it and see how things look. If you spend most of the time in 920 you might get better battery life by using 700 because it should be able to spend more time in 700 before it has to ramp up to 920.
[Samsung Galaxy Nexus] cc16177:
So far my phone has spent 75%of its time at 350mhz and the rest mostly 920 so its working well. I'm at 12 hrs 15 min with 1 hr 40 min screen on time at 27%. I'm happy with that for how I use my phone but its always tempting to update to the latest version haha
[Samsung Galaxy Nexus] EyeOfTruth:
If that is the case you probably could upgrade and not worry about it. Typically updates fix more issues then they cause and the GPU is over clocked again which is always a nice feature.
[Samsung Galaxy Nexus] Chopes:
Quick question. Is this kernel functional with all 4.0.0roms or is there certain roms that this isn't going to work with? ( will it work with stock fully updated for instance?)
[Samsung Galaxy Nexus] tu3218:
this is for 4.0.3 only.
[Samsung Galaxy Nexus] mike216:
I did,thanks for responding. I let it sit uncharged while sleeping last night (14.1) and was at 94% with data off. That's the best I've seen. Even on other great battery life kernels I would be at 88%

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] Breezer23:
14.2 is giving me a ton of soft reboots..
[Samsung Galaxy Nexus] mike216:
Bump your voltage up some,that will solve it

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] nycdiplomat:
The best two bucks i have ever spent!!! LOVE this kernel, this phone and this community!!! ANDROID FTW!!! :D:D:D:D:D:D
[Samsung Galaxy Nexus] Grady:
with 14.2 my battery is draining quicker than before

EDIT: 3-4% every 20 minutes
[Samsung Galaxy Nexus] nycdiplomat:
did you wipe cache/dalvik cache before flashing 14.2? Also install better battery stats and open the app and it will tell you what is draining your battery.
[Samsung Galaxy Nexus] Grady:
No, I didn't. In Franco's app, it says not to wipe anything, so I didn't. can I just reflash?

EDIT: Android OS is at 47%
[Samsung Galaxy Nexus] TEK112:
Start with wiping cache and dalvik, then flash the kernel.
[Samsung Galaxy Nexus] nycdiplomat:
If you run into issues though, 9 times out of 10 wiping the cache fixes it especially with kernels
[Samsung Galaxy Nexus] Grady:
wipe cache partition?
[Samsung Galaxy Nexus] nycdiplomat:
yup, then go to advanced and wipe dalvik cache, then reflash the kernel
[Samsung Galaxy Nexus] TEK112:
In clockwork recovery. Both cache and dalvik.
[Samsung Galaxy Nexus] winner00:
I am getting stuck at the boot animation on my latest CM9 Kang 1/26. Its only with this kernel and imo's kernel. If I use the stock kernel it boots up fine. I am thinking since your kernel replaces the init.rc that its causing problems with the latest code. I am thinking it might be this change that edits the init.rc: https://github.com/CyanogenMod/android_system_core/commit/1fa0f096173867f1c09d3829a579b1d3d0fbb4c6 Heres part of the patch that goes along with it: https://github.com/CyanogenMod/andr...mmit/f7726315cad9ad9ab202ba98eed12f58614dc1c0

I could just put this code into the init.tuna.rc file and it might fix the issue but I won't be able to do that till tomorrow night.
[Samsung Galaxy Nexus] Wicked4u2c:
Wiping cache partition and dalvik cache is not needed. Franco has said this in previous posts, it does nothing for kernel.
[Samsung Galaxy Nexus] nycdiplomat:
It worked for me when i was having issues with the previous nightlies
[Samsung Galaxy Nexus] TEK112:
Correct, it does nothing for the kernel. However, it does something for the ROM to play nice with the kernel.

Clearing cache and dalvik is the ancient answer to fixing bootloops from a kernel change. There are too many reports (personal experience included) that support wiping cache and dalvik before changing kernels. There are even more that show wiping the caches solves the bootloop caused by switching kernels.

There have to be files that have to do with OS operations that reference the kernel. I was on Nightly 14 (upgraded from 13.1) and noticed the phone would not deep sleep. Rebooted and still no deep sleep. I rebooted into recovery and wiped cache and dalvik and upon booting up, within seconds of the screen being turned off I had deep sleep.

Just too coincidental for me.
[Samsung Galaxy Nexus] Stockmoose16:
I'm getting a kernel wakelock called vbus-tuna_otg on 14.2. What is it and how do I get rid of it?
[Samsung Galaxy Nexus] Wicked4u2c:
14.2 did it again, broke my last personal record. Trying to get past 7100 is difficult!
[Samsung Galaxy Nexus] breizhim:
Well, i'll wait for this patch before re-install Franco's kernel. I had the same problem.

Franco, can you include these modifications for next nightly ?

I believe in you ^^
[Samsung Galaxy Nexus] housry23:
I also couldn't get it to boot with the 1/26 build of winner00 CM9. The stock kernel, as stated before, boots up just fine. I tried everything. Wipe cache and dalvik, install at the same time, install separately and still get stuck in boot animation. I'll check back for a fix. Good work Franco! I have loved your kernels ever since my Nexus S 4G days.
[Samsung Galaxy Nexus] franciscofranco:
About CM9 we have to wait, I don't know what yet what exact changes they did for this big ****-up

Either way I just pulled an all-nighter to deliver #14.3. I hope it fixes out the **** caused by the latest ones.
[Samsung Galaxy Nexus] kichard:
What's this animation you speak of in the change log?
[Samsung Galaxy Nexus] dwallersv:
I download 14.2, post then go away and find 14.3. Leaves me wondering... more cowbell?

Franco?

:D :D
[Samsung Galaxy Nexus] kichard:
My text to speech doesn't seem to work on the newest...works fine on 13.1

EDIT

I retract that statement. Re flashed and its working fine. Idk lol. So appreciate all your work man.
[Samsung Galaxy Nexus] Natolx:
Thanks a lot for this! My phone was only in 50% deep sleep last night(no use) so something was definitely up
[Samsung Galaxy Nexus] Elganja:
thanks for burning the midnight oil... just updated and working great!
[Samsung Galaxy Nexus] jermaine151:
EDIT: Found my answer.
[Samsung Galaxy Nexus] hogowner:
just a quick question..

how can you tell if it is working great after installing without giving it time?

No being funny.....would like to know how I can check kernals if they are working right after install
[Samsung Galaxy Nexus] Elganja:
real usage ... i didn't literally just update...
[Samsung Galaxy Nexus] dwallersv:
Okay, serious question (no cowbell this time :-))

How do I use CIFS with it included "as a module"? Tried CIFS manager with 14.2 last night, no dice. Same result as when CIFS wasn't there (11,12): No such device (or something like that).

Do I need to grab an ICS version of cifs.ko from somewhere and put it in /system/lib/modules?

Thanks in advance!

PS: Kernel needs more cowbell (couldn't resist :D)
[Samsung Galaxy Nexus] b33zy682:
Every since I updated to the 14s.I've been getting these kworker processes eating my battery. Any ideas? Anyone else? And does anyone have the link to the 13.1 kernel. That kernel was bad ass
[Samsung Galaxy Nexus] Tree of Knowledge:
I've only been unplugged on the latest 14.3 kernel for about an hour now and I'm at 90% with not a whole lot of usage, this is definitely a bit concerning. I'm going to try and hunt down 13.1 again.
[Samsung Galaxy Nexus] cc16177:
I don't have the link but I have the kernel installer itself, I don't know if that's helpful at all.

I have neglected to upgrade beyond 13.1 because i'm getting such fantastic battery life... I've also read that you may not be able to undervolt 14+ as much as 13.1 so i'm nervous about that.

I'm currently running 350-920 with 350 undervolted to 750 and i'm pulling 14-18 hours per charge with around 2 hours of screen time which is awesome for me.

Even right now i'm at 5-6 hours with around 75-80% left which would never have happened before.

Until I start hearing of people doing as well with the newer builds i'm just going to stick to 13.1
[Samsung Galaxy Nexus] Tree of Knowledge:
I just reverted back to 13.1 for this very reason. I'm not in a position to be able to post it right now but I will as soon as I get home.
[Samsung Galaxy Nexus] MFD00M:
I just flashed test 2, will report back if i notice anything funky
[Samsung Galaxy Nexus] qman66:
a different boot animation is included? how do we keep the stock one.
[Samsung Galaxy Nexus] Gahh Its Lee:
Your kernel is still amazing man. People just love to *****. Make the kernel you want. Its running fine for me. The only issue I've had is that I had to boost like UV 125 mv and like 75 mv but oh well lol. Still getting great battery life.
[Samsung Galaxy Nexus] BusyPooping:
Do these kernels effect 3g and 4g? I feel like it got worse with 14, but it could be the rom...

Also, with 14.3 I can't access voltage controls.

I agree with everyone else that 13.1 was the best. I had run 17 hours before it got to 50% and I don't see it now lol
[Samsung Galaxy Nexus] BigJermZ:
I tried installing the latest kernel (14.3) from the updater app and I got stuck in bootloop....Is anyone else having this issue?
[Samsung Galaxy Nexus] franciscofranco:
The latest is 14.4. I bet you tried to install 14.3 with CM9, which had ramdisk changes and it didnt boot. Now with 14.4 it will boot just fine I hope.
[Samsung Galaxy Nexus] 5280WRX:
14.4 is magic. I installed it with my battery at 60, rebooted and now it reads 87. Wow! Cleared cache and dalvic before install.
[Samsung Galaxy Nexus] BusyPooping:
Weird.... regular or extended battery?

I have lost 7% in the last 10 minutes flashing and reflashing lol

But it seems to work though
[Samsung Galaxy Nexus] 5280WRX:
Extended. It is draining fast now. Already down to 77 since I last posted.

---------- Post added at 01:50 PM ---------- Previous post was at 01:49 PM ----------

I'm going to clear battery stats and see if that helps - down to 75 - I guess I'll wait and see what happens first
[Samsung Galaxy Nexus] BigJermZ:
Yup 14.4 did the trick...nice work!
[Samsung Galaxy Nexus] ndwatkins:
Btw Franco, I just wanted to tell you (hopefully not to confuse anything further) I'm getting some of the best battery life and real-time performance I've ever had on the 14 series. Will be updating later. I did recently do a fresh reset if that matters to you any, not using hot plug, using conservative, 1200/700 and my own UV, no OC at 1175, 1050, 975, and 850. Also, running AOKP 21 in case that matters.

So, shrug. Anyway, don't get discouraged. Love your work. :)
[Samsung Galaxy Nexus] BusyPooping:
Good tips for clock and volt specs. I haven't even thought about that.

I may mess with it later and try your settings.

I never understood voltages
[Samsung Galaxy Nexus] asmodea:
The 14.4 version doesn t contain the new boot animation ?
[Samsung Galaxy Nexus] franciscofranco:
It does, it's in /data/local.
[Samsung Galaxy Nexus] Berzerker7:
Any reason why FIOPS was removed?
[Samsung Galaxy Nexus] MFD00M:
Is 14.4 different than the two test kernels you posted earlier? Currently on test2 and all seems well so far. I won't bother updating if they're the same.
[Samsung Galaxy Nexus] Wicked4u2c:
I'm going back to 14.2 you can see after flashing 14.4 battery went to **** and performance feels laggy. I didn't try 14.3 since 14.4 came out a few hours later. Also score dropped a lot on Antutu.
[Samsung Galaxy Nexus] franciscofranco:
No offense but... complaining about battery when you're with the low signal all the time, wifi turned on, bluetooth, some gps, and screen on most of the time...I'm surprised you could've made it to 6 hours.
[Samsung Galaxy Nexus] TEK112:
I could not help but notice that after (what I assume is the point at which you flash the kernel) the phone was awake the rest of the time. Did you wipe cache and Dalvik before flashing the new kernel? If you did wipe cache and Dalvik before flashing, the ROM will work very hard to rebuild those caches with new data. This is resource intensive on the phone and could have contributed to your poor battery life. It is always best to let a kernel settle for at least a day or two.
[Samsung Galaxy Nexus] pauliewalnutted:
I am not seeing it while using root explorer.
[Samsung Galaxy Nexus] rockingwing:
Just wanted to post that...
[Samsung Galaxy Nexus] Wicked4u2c:
I use my phone about the same everyday, I keep everything on. All I'm saying that when I flashed your latest kernel I went from 38% battery life to 13% in minutes.

With your other kernels I would have 33% battery life and still last a whole hour with everything on and have battery left.

I'm not complaining, I'm letting you know just like everyone lets you know that something is not the same. I never had any issues with your kernels. 14.2 was the best for me, I never bothered with 14.3 since 14.4 was released so fast.

Yes, I cleared all caches. Also the fact that I'm scoring much lower on Antutu also proves performance has been hindered.

I appreciate the work you put in and the late nights you stay up coding. If you look at previous pages I'm always giving you kudos, I'm just trying to help that is all. After all, I am trying to break the Antutu record with your Kernel and I'm getting close.

Thanks again.
[Samsung Galaxy Nexus] dwallersv:
Guys, what do i have to do to get CIFS working?
[Samsung Galaxy Nexus] BusyPooping:
Seems good to me... battery has been draining constantly all day from different flashes so im not worried.

Loving all the updates.
[Samsung Galaxy Nexus] franciscofranco:
I wasn't complaining either, it just seemed too obvious with everything on =)

My antutu values are exactly the same and my battery is actually much better. I challenge you to stay with 14.4 for a while and see if it improves, sometimes it takes a little while to settle ;)
[Samsung Galaxy Nexus] Protocol 7:
Franco, I've been using your kernel since nightly #5, and I love it. However, since 14.0, (currently on 14.4), my battery life is horrid. Now, I'm not complaining, I just wish to vouch for the others also raising this problem, and that it is existing.

14.4, I believe, made it worse. It took me about a minute and a half to type this and I lost 3% of battery with my phone being underclocked to 700, on WiFi, with brightness all the way down.

Still, I'll only use your kernel, because its the only one I like. Thanks for all the hard work you've done.
[Samsung Galaxy Nexus] pauliewalnutted:
I would imagine not deep sleeping is the culprit.
[Samsung Galaxy Nexus] Wicked4u2c:
Fair enough, never doubted you man thanks!
[Samsung Galaxy Nexus] CDuke619:
Been running 14.4 for 5 hours now. Everything is running pretty smooth but I did have one reboot :(
[Samsung Galaxy Nexus] Gahh Its Lee:
Is 3g controlled by the kernel? Having some issues where its connected but it doesn't work.
[Samsung Galaxy Nexus] djh816:
looks like the opengl stuff for the planets quadrant test is broken again. don't know if this is kernel related or the new cm9 nightly 1/27
[Samsung Galaxy Nexus] mike216:
If you guys get reboots there easily solve able, just bump the volts up by 25. Ecru phone handles UV differently so what works for me may not work for you

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] mike216:
The only issue I can report on that I don't experience on other kernels is occasional lag while typing? On 14.4 but everything else is smooth as can be!

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] EyeOfTruth:
nope that would be the baseband.
[Samsung Galaxy Nexus] J.Max:
I was wondering this too.
[Samsung Galaxy Nexus] BusyPooping:
just to add to the testing. 14.4 has been doing something with my battery. it seems like it goes down 1% every minute and no i was not watching it. I put it back on the charger and im gonna wipe battery and try again later.
[Samsung Galaxy Nexus] zeppelinmad4:
Is that while you're sleeping? You used your phone for a total of about 8 minutes while in airplane mode. While impressive, it would be any better to see that during actual use.
[Samsung Galaxy Nexus] dwallersv:
I feel like I'm being a pest, and apologize.

Does not anyone know how to get CIFS to work on 14.X? Simply installing CIFS Manager did not do it.

I'm certain it's something very simple, and would greatly appreciate anyone that knows the answer taking a minute or so to help out with a reply. Thanks!
[Samsung Galaxy Nexus] b33zu:
You guys need to do this. First off no one with this phone needs to overclocked to 1.5. Here's my settings. Turn the kernel clock down to 350 min and 920 max. Then enable hot plug. Leave everything else alone. I'm getting great speeds and great battery life. On top of that battery stays cool most times and if it gets at a higher temp it just stays warm not hot. Don't touch UV.
[Samsung Galaxy Nexus] Wicked4u2c:
Sorry Franco, I did my overnight test (charge the phone to 100% right before I go to bed, and unplug it from charger without ever touching the phone until i wake up 8 hours later). All your other Kernels have lasted above 90% I got 85% after 9 hours ( it was Saturday I slept an hour more).

I have attached both screenshots from 14.1 I took and today. I'm telling you, something is wrong, I knew it the minute I flashed it when the battery went down like crazy.
[Samsung Galaxy Nexus] TEK112:
Open up your battery stats for cell standby. That usage is way too high. That indicates that you are in a no service area for a good majority of the time. I can almost guarantee that is the biggest issue you are facing right now with the kernel. Also install CPU spy from the market and see how long your phone is spending in each state.
[Samsung Galaxy Nexus] BusyPooping:
OK my phone is hardly going into deep sleep. Mostly at 350mhz.

How do you tell it to go to deep sleep
[Samsung Galaxy Nexus] lazcoreaedu:
How do I use color control? Sorry for noob question, new to this
[Samsung Galaxy Nexus] TEK112:
The easiest way is to download his app from the market and then play around.
[Samsung Galaxy Nexus] lazcoreaedu:
Thank you :)