yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Kappa Lamda:
r282 just doesn't fit to me... 5 hours deep sleep with only 2g and data on, nothing elese and from 65% battery I woke up and was on 52%! BBS didn't indicate any app causing this and I wasn't expecting something because only change I made is auto-flashing r282 over r281 but just in case I checked.

Trying now r283
[Samsung Galaxy Nexus] punkeroso:
I noticed that, if the phone is freshly powered on, the wifi actually works really good without any disconnection when screen is off. Instead, when I use wifi after have disabled the airplane mode, it keeps disconnecting on screen off.
[Samsung Galaxy Nexus] DarkBanHammer:
Idk if its my CPU or what but 1.7 GHz isn't stable for me anymore on r283
[Samsung Galaxy Nexus] gaich:
Everything seems to be fine, as usual, no changes detected...
[Samsung Galaxy Nexus] darkstar2k77:
Experimental r283 flies. Feels snappier than r282
[Samsung Galaxy Nexus] lucas4ever:
First impression on r283: quite laggy in Taptalk, not so smooth as r282.
[Samsung Galaxy Nexus] tobitronics:
Franco, i dont know what you did in 283 but it's AMAZING! Not. Drawer finally lag free, keyboard feels snappier in-app, generally everything is snappier! Probably it's going to hit my battery though ;)

Beamed from my Google Galaxy Nexus
[Samsung Galaxy Nexus] Fenvarien:
+1

R283 runs ****ing fast :)
[Samsung Galaxy Nexus] franciscofranco:
Awesome so r283 feedback is exactly as I thought it would be and exactly as I felt. I will release it as official in a little.
[Samsung Galaxy Nexus] The Gingerbread Man:
283 also great here. Still stock wifi driver?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] derPianist:
But please...

WITH changelog! :)

via Google Galaxy Nexus
[Samsung Galaxy Nexus] joeyfong:
still no changelog？
[Samsung Galaxy Nexus] dyepnoodle:
what would be the best choice for TCP Congestion Control? any suggestions guys?
[Samsung Galaxy Nexus] franciscofranco:
Yes 0 Wi-Fi changes.
[Samsung Galaxy Nexus] The Gingerbread Man:
What do you think of doing a poll to see who would like the 27# WiFi vs stock? I'm certain the new one felt faster. Otherwise I'm really happy with this, perhaps even one of your best yet!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Not bringing those back, 100% compatibility is what I want here, those drivers got pwned by WEP routers.
[Samsung Galaxy Nexus] franciscofranco:
r283:

* Changes on the lowmemorykiller driver - should be butter smoooooth
[Samsung Galaxy Nexus] Mgamerz:
Chose your kernel over trinity cause of the massive amount of off topic clogging the thread as well as the general immaturity of the users posting in said (trinity) thread. Will test next milestone.
[Samsung Galaxy Nexus] mixtapes08:
It's legal...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Mgamerz:
I meant the trinity thread. This one is fine.
[Samsung Galaxy Nexus] teriemer:
r283 GPU384 on CNA 3.6.6 is nothing but IMPRESSIVE - so smooth. Let's see about battery now...

Love your work Franco :good:
[Samsung Galaxy Nexus] tobitronics:
Franco one thing about 283-512 experimental (the one you posted this morning): when multitasking between apps the animation stutters. Other than that its perfect :)

Beamed from my Google Galaxy Nexus
[Samsung Galaxy Nexus] mrm43:
r283 gpu 384 is indeed super smooth here on Xenonhd
[Samsung Galaxy Nexus] tzyn:
Which settings do you use now? 8099,10132,20000,20000,50000,100000?

I'm using r276 at the moment (back from r277, lean back and reading r281/r282 feedback) with 384/1305, LMK tweak and hispeed_freq = 1036 and it's so fast and smooth, absolute amazing kernel. Great work!
[Samsung Galaxy Nexus] derPianist:
Sorry Franco, but 283 is really laggy and choppy for me running latest CM10, clean install.

WhatsApp is laggy as hell and much more laggy than before (282)

PlayStore is also kind of choppy. It stutters all the time. I never had got any problems with smoothnes and performance with PlayStore.

I know that also Tapatalk is not so good developed like WhatsApp but also there i can clearly see that it became a lot more laggy.

Phone also gets to hot.

I didnt changed any settings since using every nightly of your kernel and i never had got problems in terms of smoothnes, battery, overall performance and temperature.

Might take a look at it? Thanks.

via Google Galaxy Nexus
[Samsung Galaxy Nexus] --__LoRiS__--:
My phone is also hot than before...
[Samsung Galaxy Nexus] sluflyer06:
Just to put the word out that I'm nervous of changes because I'm seeing just amazing results on #10 of 1-2mv drain and stutter free performance. (GSM)
[Samsung Galaxy Nexus] stellaryt:
I'm on Franco 10/AOKP 14. Battery Monitor shows 50-70mA/5m no matter hotplug enabled or disabled.I thought it was weird.So I reflashed AOKP14and change back to Franco's 8.And sleep without Battery Monitor,from pm11:00 to am 8:00,just drain 3%. The best record of my device is 2% w/ Franco's #8.

Maybe I should try #10 and AOKP 14 with a reflash.

And a question seems stupid:how to see the hotplug is working? I had no different feeling between enabled and disabled.
[Samsung Galaxy Nexus] franciscofranco:
Yes I can. I'm still not sure if the problem is ramdisk based or some other patch. Which kernel did you flash to test this?
[Samsung Galaxy Nexus] s2d4:
The nexus has a current sensor?

If not, those estimates of battery monitor Widgets does more harm than good.

Since the app itself is a well known wakelock horder.
[Samsung Galaxy Nexus] Dr_Ownage:
I would agree, however. Back on the Nexus S we used BLN (Back light notifications) we had AMAZING battery with that phone, except when you had BLN on pulse...
[Samsung Galaxy Nexus] jan-willem3:
According to the post on the previous page this issue is there since version 9 so I think it is the ramdisk.
[Samsung Galaxy Nexus] aron7awol:
Yes, but on the Nexus S, blinking the button backlights wasn't a built in function, so the device had to keep being waked to turn the backlight on and off. On the Nexus One, and I'm guessing it's the same on the Galaxy Nexus, that one value just needs to be set and the built-in blinking function will continue to flash the notification light without having to wake the device and turn the light on and off.
[Samsung Galaxy Nexus] Stadsport:
Can I ask what you're using to read the battery's active drain in mV?
[Samsung Galaxy Nexus] mfish123:
Can't see to go low mA battery drain - please help

Thanks for the advice.....I unfortunately very rarely see 2 ma drain. Ussually between 25 - 60. I'm running Axiom 2.4 (clean install with everything wiped prior to install) and running franco nightly #10 (wiped davlik and cache before installing). I'm on the 4.03 CDMA radio and an running PRIMEKL01. I have governor set to conservative with hotplug enabled (I've use the workarounds suggested to make sure its enabled. I'm running 700 mhz - 1350 mhz and even tried 350mhz - 1350mhz with no tangible difference.

My battery life is solid but it sounds like it could be better. Do you think the difference is Axiom vs. AOKP? I've attached some cpu spy, better battery stats, and battery monitor screen shots. I can't seem to find any rouge apps chewing up my battery life although out of 16.5 hours total time on and about 3 of those with the screen on my Android OS is eating up 27% of battery life. Screen ate 49%. Android OS Keep awake is 6 hours and 25 mintues but cpu total only 1 hour 5 minutes. For most of this session I had wifi on and connected and juice defender disabled. For some of the test I had juice defender enabled which shut off wifi and 4g when screen is off. GPS and BT were off. I even uninstalled Google + as I don't use it and I left "use gps satellites off" in location settings.

Based on this can anyone point me in the right direction of getting lower battery drain?
[Samsung Galaxy Nexus] mfish123:
Can't see to go low mA battery drain - continued

More battery screen shots from the android settings menu
[Samsung Galaxy Nexus] kjwalker:
Can you post your partial wakelocks?
[Samsung Galaxy Nexus] mfish123:
Just added them to my original post and included more details in paragraph 2. Thanks for looking into this.

EDIT: Attached running apps screen shots too if that helps
[Samsung Galaxy Nexus] franciscofranco:
The drain comes from maps, I already wrote here that maps drains every damn battery that it cans.
[Samsung Galaxy Nexus] s2d4:
what is your take on this Francisco?

Btw, this is on your kernel.

Idles beautifully
[Samsung Galaxy Nexus] mfish123:
Thank you for chiming in and all your hard work. Your kernel rocks and I've tried em all (IMO, Apex, JD, etc.) I did just try to force stop maps and unfortunately it immediately reappears in my running apps list. I guess I could you use TiBu to freeze it. However, I do use google navigation sometimes, and I think if I were to uninstall google maps I'd lose google navigation as well. Is there any other more elegant to stop google maps from killing my battery? I'm not opposed to uninstalling it and paying for a better behaving GPS app if thats what it takes.
[Samsung Galaxy Nexus] jknisley:
Well, also, he's on a UKK radio, which is GSM. The LTE radio is an extreme hog on the power, but there's also this maps thing that Franco is talking about. We'll see how that goes, but, TBH, I couldn't possibly live without Google Maps. People were saying "Oh, I'm getting terrific battery life if I freeze maps/gmail sync/exchange/.../im" and, while I do need battery life, I also need a certain subset of things to function or I might as well have a clamshell phone. *shrugs*

Maybe I just have to deal with ****ty battery life.
[Samsung Galaxy Nexus] RVDigital:
Need a favor from anyone running this Kernel with Battery Monitor Widget.

Please post your Batt History if possible. I'm seeing an issue where the mV reading is bouncing when only drain (no charge) is occuring. I'm not seeing this with any other Kernel and I think the Battery reporting may be off. Thanks in advance!

EXAMPLE

1/8/2012 3:36:07 AM -26 99% 4135 28 0 0

1/8/2012 3:39:07 AM -24 99% 4135 28 0 0

1/8/2012 3:42:07 AM -23 98% 4130 22 0 0

1/8/2012 3:45:07 AM -23 98% 4130 22 0 0

1/8/2012 3:48:07 AM -23 98% 4130 22 0 0

1/8/2012 3:51:07 AM -23 98% 4130 22 0 0

1/8/2012 3:54:07 AM -23 98% 4130 22 0 0

1/8/2012 3:57:07 AM -23 98% 4130 22 0 0

1/8/2012 4:00:07 AM -23 98% 4130 22 0 0

1/8/2012 4:03:07 AM -23 98% 4130 22 0 0

1/8/2012 4:06:07 AM -23 98% 4130 22 0 0

1/8/2012 4:09:07 AM -23 98% 4130 22 0 0

1/8/2012 4:12:07 AM -23 98% 4130 22 0 0

1/8/2012 4:15:07 AM -23 98% 4130 22 0 0

1/8/2012 4:18:07 AM -23 98% 4130 22 0 0

1/8/2012 4:21:07 AM -23 98% 4130 22 0 0

1/8/2012 4:24:07 AM -23 98% 4130 22 0 0

1/8/2012 4:27:07 AM -24 97% 4135 21 0 0

1/8/2012 4:30:07 AM -24 97% 4135 21 0 0

1/8/2012 4:33:07 AM -24 97% 4135 21 0 0
[Samsung Galaxy Nexus] mfish123:
Good observation - I know 4G LTE is a battery hog. However, in the stats I posted I was either on wifi or wifi and mobile data was disabled. But I do agree, that like most things its usually a compromise. I do use google navigation so it wouldn't be practical for me to uninstall / freeze google maps even if keeping it installed decreases my battery life. But I do wish I could have my cake and eat it! :)
[Samsung Galaxy Nexus] jknisley:
I've been kinda playing around a little bit. I turned off all the radios and get almost no drain at all. Really insane life of 1% every two hours. It was crazy.

I also just played around with another setting. In the location services menu, there are a few options. #1 is the wifi identification thing, which still creeps me out, and #3 is using Google Location Services to aid searches and crap. I turned off #3 (and 1, in all fairness), and now Google Maps doesn't run 100% of the time. I don't see it running right now, actually.

So I don't know how active the garbage collection on it is after you've gotten out of it, but it seems like at least a measure of control for when you aren't actually using Google Maps.

EDIT: Doing this change and not having run maps, yet, it's made a significant difference in my battery life. Like steady battery life for the last half hour.
[Samsung Galaxy Nexus] dpaine88:
Thanks for the tip, I am trying this out now myself.
[Samsung Galaxy Nexus] doomed151:
Have you tried reverting to the last smooth kernel and see whether the lag issue is still there?
[Samsung Galaxy Nexus] sruel3216:
@franco, running great here. very smooth. battery seems nice on idle drain
[Samsung Galaxy Nexus] trailblazerz11:
Very smooth for me.

Had stuttering in whatsapp and tapatalk before but none now.

Came from m5 running cna, couldn't resist 283
[Samsung Galaxy Nexus] :
I didnt changed any settings since using every nightly of your kernel and i never had got problems in terms of smoothnes, battery, overall performance and temperature.

Might take a look at it? Thanks.

Sounds a bit strange ...

I'm running CM10 and #283 too and I have to say: very smooth. For me the smoothest kernel at the moment (compare to faux, fugumod, leankernel). Not hot at all.

The only thing missing is the zram possibility as it is in the cm, faux and lean kernel.

Great work!
[Samsung Galaxy Nexus] ac3theone:
R283 Running fine for me here
[Samsung Galaxy Nexus] bradm23:
Very fast update, but getting some small studders with slow scrolling in we pages. Because of this, not sure if 283 is better than 282 which didnt have these studders
[Samsung Galaxy Nexus] Fenvarien:
WhatsApp is flying here and super smooth. I don't experience any lags with r283 and the phone keeps quite cool.

Maybe one of your apps went rogue? Also try to change dyninteractive to interactive governor.
[Samsung Galaxy Nexus] zenzip:
r283 CNA clean installation and after flash kernel form franco app, and all work fine, 384-1420 interactive, wait for batterylife performance.
[Samsung Galaxy Nexus] federra7:
Very Smooth for me as well. Great work man!

The only problem I've noticed that since updating from MS5, I can no longer connect to the Enterprise wifi network at my university; however, home and other unsecured wifis seem to work just fine. Anyone else experiencing anything similar? Thanks!
[Samsung Galaxy Nexus] MatthewYiu:
+1 - using it on CNA 3.6, waiting for 3.7 =)
[Samsung Galaxy Nexus] kyokeun1234:
Flashed 283r, loving it! It is very smooth and fast! Will report about battery later.

PS. 282r battery life was awesome ;)
[Samsung Galaxy Nexus] KJW979:
r283 384 version on nexus evolution with CPU at 1228/729 running without a problem, no lag, no WiFi issues, no heat issues. Fabulous kernel as usual.
[Samsung Galaxy Nexus] usmankh10:
I was using v277 before

Flashed 283 its damn smooth nd no lag

Running Pa 2.16

Thanx franco for great kernal
[Samsung Galaxy Nexus] jltorrente:
So, this one (283) is going to become the next milestone? That's lovely... Milestone 5 is awesome and seems that things have only got better and killer since then!... Do you guys recommend dirty flashing it over the last milestone or full wipe?
[Samsung Galaxy Nexus] TEK112:
It is hit or miss with enterprise security. I work for a health system and I can access wifi at one of my sites, but not the other. They both have the same encryption/access, but they are two very different networks with different firewalls. Two different Android devices, one has francos kernel the other does not.
[Samsung Galaxy Nexus] FingerMove:
Anyone else wating for Franco to troll again?

Seems to be really fast, but I think it's probably part of the mind**** test, so we will know the truth in a couple of hours :laugh:
[Samsung Galaxy Nexus] RevengeFNF:
r283 running great with CM10.
[Samsung Galaxy Nexus] franciscofranco:
Makes no sense, only this two changes on r283:

https://github.com/franciscofranco/Tuna_JB_pre1/commit/339fa2989b8f9d6e4f862c498738f401400a90b9

https://github.com/franciscofranco/Tuna_JB_pre1/commit/69f1c210f911782cb9daacf7a5a46d45faf51333
[Samsung Galaxy Nexus] yellowdie:
No need to wipe anything when flashing kernels. And Franco said recently he's not quire ready for a new Milestone. He's very close but still tweaking a few things to perfection. :) It'll happen when it happens.
[Samsung Galaxy Nexus] jltorrente:
Oh, I see... Sorry about the confusion, as francisco said that he was going to make it official i was thinking that he meant new milestone... there's no rush or pressure, I'm very happy with Milestone 5 and things can only go upward.
[Samsung Galaxy Nexus] aeroseek:
No need to wipe when flashing kernel.

Edit: D'oh! Too slow
[Samsung Galaxy Nexus] jakTomas:
where is the r283 that everyone talking about :P ,, last one i see is franco.Kernel-r281-512GPU.zip
[Samsung Galaxy Nexus] kyokeun1234:
http://minooch.com/franciscofranco/Galaxy Nexus/JB/Jelly Bean/
[Samsung Galaxy Nexus] michi_1983:
franco app or 3-4 pages back he posted it

greetz
[Samsung Galaxy Nexus] jakTomas:
i just checked it 2 min ago :P and the last one was r281 :eek: o.O
[Samsung Galaxy Nexus] The Gingerbread Man:
So the 283 zip is just the same as the .img I flashed way earlier on?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kyokeun1234:
Yeah, just in zip file.
[Samsung Galaxy Nexus] peachpuff:
Sorry but its laggy, no wait its smooth now, nope laggy again, kind of smooth but with some lag and smoothness built in on the side... can't imagine being a dev with this kind of feedback.
[Samsung Galaxy Nexus] michi_1983:
It's a 512gpu Version I guess, but yeh
[Samsung Galaxy Nexus] ChazzMatt:
Hmmm... not sure why you loved 277 when that was the release where Franco says he took out all the scripts. :confused: 276 and before were the ones supposedly with the magic...

Now 275 & 276 (osm0sis post) would be in that category, but not 277.

That was why I went back from 281 to 276 for my phone a couple of days ago. I checked my wife's phone and she was still on 276. I had not upgraded her yet, so just left it there.
[Samsung Galaxy Nexus] asim0:
With so much oo's there's no way you get unbiased feedback, so I understand the blind changelog thing ;)
[Samsung Galaxy Nexus] Culex316:
My initial thoughts on r283: lag is indeed gone... Even in places where it was present before across all kernels I have tested with stock jelly bean so far, in fact it was so buttery smooth the phone slipped out of my hand. Luckily I use a case.

However I do think there is still room for improvement in terms of snappiness (maybe I'm nitpicking but the recent app menu opens like 1/4th of a second slower than previous builds.) but looks promising so far I like it thank you Franco for pushing the envelope even further!
[Samsung Galaxy Nexus] prulleman:
started using this kernel just recently on AOKP b3/4 first M5 then r281 where 281 was WAY more snappy then M5, but no this even more smooth. we will see what the battery will do, but it's probably worth it :D
[Samsung Galaxy Nexus] Vangelis13:
How on earth did you measure something as being 1/4 of a second slower..?
[Samsung Galaxy Nexus] Wh1t3Rose:
Just wanted to say #281 has given me the best battery life I've ever had on this phone. Though I've only have had it for a month. Stock battery. Yesterday on SlimBean I got 18 hours with 2:45 screen on. 30 minutes of bad piggies and some music. Today on Eclipse I'm gonna try for 20 hours and 3 hours screen on.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] doomed151:
1/4 of a second = 250 ms

Actually it's quite easy to measure,
[Samsung Galaxy Nexus] TEK112:
I guess the real question was what metric did you use to measure it?
[Samsung Galaxy Nexus] Vangelis13:
Please explain how you would do it. How you'd figure out that something on your phone is 1/4 of a second slower.
[Samsung Galaxy Nexus] thumm138:
I've been experiencing this too, not sure if its a ROM issue though. Currently on AOKP built on 9/27.
[Samsung Galaxy Nexus] SahilC:
Hey, I'm new to this thread :)

Is there anyone here who has come from Trinity? I flashed it yesterday, and I'm planning on flashing Francos next week, just to try each out.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
Welcome. I tried them all and keep coming back.
[Samsung Galaxy Nexus] Wh1t3Rose:
I came from Trinity. My phone likes this kernel more

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tjackbjorn:
Gonna flash r283 + latest xenon, I guess I can't imagine how fast it will be! :p

Sent from my super fast Prime filled with beans.
[Samsung Galaxy Nexus] Culex316:
Im going by personal intuition since I have been regularly flashing and using francos kernels. Basing it on "user experience" like franco himself says it is by no means a scientific benchmark.
[Samsung Galaxy Nexus] tyea:
Franco 283/512 + aokp or cm10, or CNA, works well with no artifacts.

For some reason, I thought my phone wouldn't work well with 512MHz GPU, but it is working well with this kernel. It seems every once in a while , a 512 GPU kernel (Faux123, Trinity, Franco, Imoseyon) will work, but most of the time I have to use a 384 GPU version, especially if I'm using Google maps. I usually have the CPU between 1200 and 1420, most often below 1350 to keep the CPU temp below 55.

SPH-L700, Tapatalk
[Samsung Galaxy Nexus] qtwrk:
Is it really necessary to use 512 instead of 384 ? , I thought it would make phone hot enough to cook eggs...
[Samsung Galaxy Nexus] yellowdie:
Starting with r277 (I think), Franco disabled SR (Smart Reflex) for CORE/GPU and set fixed voltages. I wasn't able to run 512 without artifacts prior to that, but now I can (like you). Enjoy!

:):D:laugh::good:
[Samsung Galaxy Nexus] zenzip:
which setting you recommend for smooth and fast user experience + good battery consumption ... around 20 hours and 3 hours screen on time.

currently I'm using brightness 70% interactive 384-1420mhz ... but have 15h with 2h of screen on .... normal usage...gmail, sms, what's up, facebook, tapatalk, greader, browsing, and sugarsync 1 time a day, 80% wifi, 20% 3G, no BT, GPS always off only use it with gmaps every 3 days ...

help me :D
[Samsung Galaxy Nexus] yellowdie:
512 is really only helpful when running 3D games and high demand stuff like that. Web browsing and emailing won't see anything different with 512, shouldn't get hot at all (again unless you're gaming, then it gets warmer, but not super hot).
[Samsung Galaxy Nexus] Rimher:
I'd recommend you to lower your screen brightness..70% fixed is pretty high. You could also try another governor, I've found wheatley to be my personal favourite in terms of battery life vs performance.
[Samsung Galaxy Nexus] yellowdie:
I think 1420 is not necessary. 381-1420 is what I used to run, but now I run 729-1228 and it feels even faster, with better battery drain. Increase the low and decrease the high. It's pretty impressive that way! :D And I run 50% and 100% brightness all day long.
[Samsung Galaxy Nexus] zenzip:
Interactive is too aggressive? trying whitely with same freq. 384-1420mhz this time with autobrightness... :D

---------- Post added at 06:44 PM ---------- Previous post was at 06:42 PM ----------

right... but 729 min freq. is too much when device is screenoff! trying 729-1305 wheatley and not interactive ;)
[Samsung Galaxy Nexus] tyea:
Sometimes it seems to make scrolling smoother, and maps generate quicker, but only a minor improvement. I agree with the temperature comment.

SPH-L700, Tapatalk
[Samsung Galaxy Nexus] yellowdie:
Nah, 729 max screen off is actually normal. And honestly, 1.2Ghz is "stock" but it's still fast as long as you have the min bumped to 729. I actually changed my max to 1036 yesterday and it still feels really fast! I highly recommend trying it (729-1036). 1305 is still sucking more battery life. And if you want to do something high intensive like gaming, it takes 20 seconds to bump it up to something like 1420. :)

btw, I use Interactive/bfq.
[Samsung Galaxy Nexus] CADude:
Hmmm I'm noticing the lag on the xda app's scrolling with r283.
[Samsung Galaxy Nexus] zenzip:
franco app have only 1305 or 1420 mhz freq. and I think they are the frequencies most suitable for this kernel, why you use 1036mhz ? :confused:

starting fight interactive vs. wheatley :D