yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] eddie_gordo:
I have just installed 241 and I had no problems with the boot.. Everything seems fine now, Francisco! :) Great work.
[Samsung Galaxy Nexus] meanwhile:
Just flashed #241, stuck at boot. removed battery, rebooted into recovery wiped both cashes. Working ok now.
[Samsung Galaxy Nexus] The Gingerbread Man:
If you get it again pull the log and post it, go to proc/last kmsg. 241 is running well for me and booted fine.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] eddie_gordo:
I forgot to say that after flashing in recovery, I wiped cache and dalvik cache.. :)
[Samsung Galaxy Nexus] 6jaipur6:
I use r241 abd i have no problem all is ok.Only one probleam apear today when i make a nenamark2 test and on my screen apear artifacts.I use recomanded settings and i have 512 version.
[Samsung Galaxy Nexus] danielvc:
install 384Mhz-version.
[Samsung Galaxy Nexus] osm0sis:
Can anyone confirm that 1228 is the new default? I like to try running full Franco defaults for awhile to see how it performs each revision. A in-app full reset would definitely be handy.
[Samsung Galaxy Nexus] djjonastybe:
comment deleted
[Samsung Galaxy Nexus] slvrarrow:
If any more tweaking is possible keep working away at the new bfq as it is yielding fantastic improvements to performance, particularly with scrolling
[Samsung Galaxy Nexus] djjonastybe:
It's your ROM that triggered the reboot I think. Not the kernel.

I quote the error message
[Samsung Galaxy Nexus] franciscofranco:
I didn't change screen off max freq settings.

It's rom **** indeed, not kernel.
[Samsung Galaxy Nexus] chugger93:
Franco, I purchased your updater app awhile ago, and use it alot. I noticed a weird bug though. Sometimes the screen off frequency just changes on its own. I set it to 230 for example and when I check back, it seems that not every time, but once in awhile when I'm in the app verifying things, its back to 729. Any thoughts?

Plus I have to change my MIN CPU to something else, then change my screen off frequency in order for it to stick.
[Samsung Galaxy Nexus] chugger93:
Also, wouldn't everyone agree that this quadrant is a sh*tty score? shouldn't I be seeing in the 5-6000 range?
[Samsung Galaxy Nexus] sway40:
Show off!!!
[Samsung Galaxy Nexus] supernova_00:
Same here using Lazy gov.
[Samsung Galaxy Nexus] jcmm11:
Small bug/quirk that's been around for a few versions now. Not sure when it started.

If using init.d script for governor settings (in my case interactive, settings for min_sample_time, go_hispeed_load, hispeed_freq) the settings don't take unless I precede them with a sleep command. I used to be able to use sleep 10, but with 241 I've had to up it to sleep 20 (somewhere between 15 and 20 is a more accurate statement, I use 20)

Other settings in init scripts take fine with no sleep. It's only governor specific ones that need the sleep command.

Workaround is simple (use sleep), but I don't think it should be needed.
[Samsung Galaxy Nexus] IAmAN00bie:
Just leave the screen off CPU at 729 MHz. When your phone's screen is off it should be in deep idle anyways. If there is a wakelock, the higher CPU cap will allow it to race-to-idle more quickly, going back into deep idle. For most use cases, this is beneficial, as Ezekeel's tests have shown. (I will admit that if you are doing something that requires a continuous wakelock like streaming music, then having a lower CPU cap should extend battery life.)
[Samsung Galaxy Nexus] franciscofranco:
Did you actually take some time to see what changed between r240 and r241 to be able to say that, or you flashed the kernel 10h ago and decided its wasting more/less than the last version?
[Samsung Galaxy Nexus] Tarun95:
R241 is simply brilliant. Battery life is too good :) speed has obviously never been an issue in your kernel :)
[Samsung Galaxy Nexus] RoscoeDpG:
i always flash the newest kernel BUT 240 has been AMAZING for me on batt life i almost dont want to mess with it lol
[Samsung Galaxy Nexus] Marcb:
r241 here... no problems so far... I had a weird "phone freeze" in r240, but now it's running really good!
[Samsung Galaxy Nexus] mike216:
+1 241 is absolutely the best kernel in the world!

I use default settings. 60% brightness. I woke up 9 hours later and only lost 5%, I usually loose 10%. Screen on drain is the best I've ever seen. Was on track to get near 5+ hours of screen on Time yesterday. (Verizon)

To sum it up its definitely a milestone as far as I'm concerned!

Franco is my Michael Jordan, beetles, or whoever your favorite idle is. :D
[Samsung Galaxy Nexus] mpokwsths:
Franco, I have a question:

It is common knowledge that for many other devices the SmartassV2 governor is the best performing governor. Wouldn't your kernel be even faster with a possible implementation of the aforementioned governor? Not that it needs it ... you have done an amazing job so far, it just crossed my mind.
[Samsung Galaxy Nexus] mike216:
Anyone know how to play DAC through a fiio amp? Like the E17 or E7,10?

I know jelly bean has support for DAC now.

I can't seem to get it to play through the micro usb to usb.

I ask here because I know Franco implemented DAC on ICS builds. I figured some here may have some experience in this kernel sound department. Thanks any help would be greatly appreciated! :thumbup:
[Samsung Galaxy Nexus] chugger93:
From the changelog there was only like 2 changes in 241...not sure why its so much more amazing...??
[Samsung Galaxy Nexus] LNJ:
BFQ is huge!
[Samsung Galaxy Nexus] mike216:
What if you never ran 240?

---------- Post added at 08:34 PM ---------- Previous post was at 08:26 PM ----------

I'm struggling a little financially right now Franco or I would have certainly donated yesterday. I will definitely make up for it Thursday when I get paid.
[Samsung Galaxy Nexus] franciscofranco:
Nope, that isn't happening, smartass sucks for SMP devices. Smartass is mostly based on interactive anyway.

I haven't tried to link the FiiO E7 since JB, it's still packaged in the same box that when I tried to send it to Ezekeel - basically I have not much free time lately.

I definitely appreciate your concern, but if you're struggling a little bit keep it please :)
[Samsung Galaxy Nexus] mike216:
I totally understand. Time is precious as I've been stuck working a lot lately. Oddly enough the DAC amp plays fine on the nexus 7?

Appreciate everything!
[Samsung Galaxy Nexus] Kostas1601:
Noob question alert!

Can I flash this while running stock 4.1.1 ?
[Samsung Galaxy Nexus] dropback:
Sure
[Samsung Galaxy Nexus] mikeandjaimie:
Bug report maybe? I never set my phone to the new lower freq step, yet with 384/1.6 on demand, I keep seeing jumps to the 2xx step in your app

Edit:sorry latest kernel as of post
[Samsung Galaxy Nexus] Kostas1601:
Great! :D And how do I flash the stock kernel afterwards if I want to go back to it?

Or will the nandroid restore also restore my kernel?? (if I make nandroid backup of my stock rom)

Thanks in advance for your reply
[Samsung Galaxy Nexus] whittikins:
241 is running really well for me (fast and good battery). I'm on track for 23+ hours standby and 5 hours screen on time (with the official samsung extended battery--2000 mAh). This would equate to about 4h 20m+ on the stock battery :)

I'm using Interactive with 1536 max, 384 min, and 1037 hi-speed load. All smart reflexes are ON. Brightness = autobrightness. Next battery cycle I'll use 50% and compare because I like it brighter.

I also have all functionality turned on. Wifi/gps/bluetooth/location/push email sync are always on. Google now too (and Latitude running/updating my location). I don't disable any features or notifications, etc. I'm running the latest AOKP nightly. Being able to use all the features of the phone without worrying about battery is GREAT. Thanks Franco!
[Samsung Galaxy Nexus] RayGarden:
Can you share ALL your settings please....tnx
[Samsung Galaxy Nexus] dascjb:
nandroid restore will restore the kernel.
[Samsung Galaxy Nexus] The Gingerbread Man:
You can flash back to stock with a flash able zip, I have on if you needed it or in recovery (don't delete your back up of stock ever) and restore/advanced/boot.IMG and that will be the stock kernel only getting restored back.

Stock kernel zip: http://db.tt/RKSz1nqs

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mike216:
CNA rom 3.2.

Default kernel settings.

60% brightness and that's about it nothing special besides the amazing kernel
[Samsung Galaxy Nexus] JkdJedi:
Don't know if it's been discussed here but I'd first like to mention that this kernel is the Real Deal Holyfield!! My only concern is that it sometimes does not play nice with music apps, Spotify, Google Music. Music will pause in middle of play for no apparent reason. I had to use or can only use stock kernels to remedy this. I was using your nightlies up to 240 when this started acting up again. I go to stock and boom I can hear my music w/o the pause glitch. Any thoughts or am I alone w/ this?

Beamed from my GneX via TaPaTalK.
[Samsung Galaxy Nexus] whittikins:
Franco, what are your thoughts on overclocking and its effects on battery life? There is the whole "race to idle" argument that claims running faster and finishing the task and returning to idle is going to save more battery than running it slower and taking longer to finish the task.

Do you think there's a sweet spot or point of diminishing returns regarding choosing a higher CPU frequency? 1200 runs great, but I do notice better response time with 1500. I would think going higher than 1500 might be that point of diminishing returns (eg. going from 1500 to 1800 will decrease battery more so than going from 1200 to 1500, but with the same performance gain).

Thoughts?
[Samsung Galaxy Nexus] nikulogical:
Probably not the kernel, but anyone having frozen clock issue?
[Samsung Galaxy Nexus] Serious_Beans:
Been running at 1536mhz with 232-241 and I dont notice any better or worse battery than on stock 1228 on interactive.
[Samsung Galaxy Nexus] ourakot:
hi.The animations when oppening applications are sometimes a bit laggy.Does someone have an idea why is this happening?Thank you
[Samsung Galaxy Nexus] danielvc:
Are you running interactive as governor? if no: select it. You can also lower the animations in developer settings :)
[Samsung Galaxy Nexus] ourakot:
Thank you for your answer..yes i am running interactive governor...and the animations speed in settings is set to 1x....I am dissapointed because everything is buttery smooth exept from the app animations...any other solutions?
[Samsung Galaxy Nexus] The Gingerbread Man:
Turn off all animations

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] hasnol143:
Man it's been a while since I've been here! Took me a while to get JB, but i got 2 questions to ask. First of all, am i the only person who gets extremely low volume during calls when i set volume boost to level 3? I always have to put it back to 0 to make a call.... Also, what's the difference between interactive and ondemand? They sound similar to me...
[Samsung Galaxy Nexus] IAmAN00bie:
Probably because your phone rarely even goes to that frequency anyways. It isn't "running at 1536 MHz" that is just your max frequency. Your phone probably spends 90% of its time at the lower frequencies + deep idle state.
[Samsung Galaxy Nexus] kuntau:
there are magnitude difference between ondemand and interactive. You can search this thread or other kernel thread which they discuss intensively.

Basically ondemand the cpu frequency will up each frequency on frequency table after certain cpu load threshold while interactive will jump straight to whatever high speed frequency you set which will lead to better performance at the cost of battery life
[Samsung Galaxy Nexus] IAmAN00bie:
The deep idle argument is when the phone is in deep sleep, ie. when the phone's screen is off (barring wakelocks). Overclocking your device will affect your phone's screen on performance (ie. when you are actually using your device.) Setting a high screen off maximum frequency only affects how fast your device exits a wakelock and returns to deep idle. In theory, this should save battery because deep idle uses the lowest amount of power. Someone correct me if I'm wrong.
[Samsung Galaxy Nexus] garu12:
Hey Franco 240 and 241 seem a tad sluggish on cm10. (not terrible but noticeable compared to how freaking smooth they usually are). Had the same result with trinity so I'm thinking your wonderful experiences with cm roms is making a comeback. Also had a few sods as well. Clean installs nothing but color mods and running interactive. Obviously rom related but thought I'd share. Flashed 241 on xenon and zoom! no issues.
[Samsung Galaxy Nexus] dark06:
Am i the only one who has unknown on kernel?

fod
[Samsung Galaxy Nexus] dascjb:
Same here on 241
[Samsung Galaxy Nexus] garu12:
Running cm10 I presume? It's always like that
[Samsung Galaxy Nexus] nnnnr14:
Running paradigm it recognizes

Sent from my Galaxy Nexus using Xparent Red Tapatalk 2

---------- Post added at 07:38 PM ---------- Previous post was at 07:22 PM ----------

Man this is one badass kernel! I just oc'ed to 1.8 and ran the stress test and it didn't even run hot! But my daily oc is 1.4.

sent from my 1.42hz Franco kernel Gnex!
[Samsung Galaxy Nexus] jaycarag:
WOW! This is the first time that I have experienced a very VERY good battery life. Using 240 then 241, I have almost 30 hours of battery with almost 3 hours of screen time and I still have 45% left.

My settings for those who are interested:

1. OC 1536-384 Ondemand

2. Smartreflex enabled.

3. Franco's stock color calibration

I use 3g moderately and I don't play any games but, the battery life is really fascinating in my opinion. Good job Franco! :good:
[Samsung Galaxy Nexus] nnnnr14:
Where is smartreflex and where do I enable it?

sent from my 1.42hz Franco kernel Gnex!
[Samsung Galaxy Nexus] JkdJedi:
I read the opposite, kinda, on demand takes a little longer to get up to speed so your using more battery life vs. Interactive where it's always in the "ready" state, a smoother transition, saving u time, saving u battery.

Beamed from my GneX via TaPaTalK.

---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------

Which phone do u have this on? Sounds incredible, never got anything like that on my phone.

Beamed from my GneX via TaPaTalK.
[Samsung Galaxy Nexus] LNJ:
How are you guys getting 30 hours out of r241 when it isn't even 24 hours old?

Exaggerate much?
[Samsung Galaxy Nexus] akaleshnikov:
I've done some searching but I want more specific information as it relates to the recent JB nightlies of this kernel

What are some of the best settings for the interactive governor, to improve latency/lag while normal use, and to keep battery life as efficient as possible. I don't do any gaming, light browsing, but I do unlock my phone 2-6x an hour to check if I have any communications. I don't like using notifications

Currently I am as follows on the r241 512 build

Min CPU: 384

Max CPU: 1420

Governor: Interactive

above_hispeed_delay

10000

boost

0

go_hispeed_load

75

hispeed_freq

1037000

input_boost

1

min_sample_time

30000

timer_rate

20000
[Samsung Galaxy Nexus] Serious_Beans:
I'm sure the person who had asked the question is aware of the fact that I'm referring to 1536mhz being the max as opposed to 1228mhz.
[Samsung Galaxy Nexus] osm0sis:
I had my screen off at 384 until you informed me of the race-to-idle situation, changed it back to the default 729 and since then my deep sleep has been much much higher: like 90s instead of 70s!

As for overclocking, I don't. At least, not technically. I "de-under-clock." :p I use 384GPU and 1536MHz CPU since these are what the hardware was built for and the "stock" settings were merely underclocks by Google/Samsung for battery savings franco.Kernel more-than makes up for.

Also: Holy 2500 pages! :D
[Samsung Galaxy Nexus] JkdJedi:
THats What I'm saying!! LOL!!:p
[Samsung Galaxy Nexus] CADude:
Stop running CM10. Seriously. Why do you guys have to continue using something that won't be stable for MONTHS and post about it in the kernel's thread as if it's the kernel's fault? :mad:
[Samsung Galaxy Nexus] LNJ:
Exactly. Even CM9 only became stable a few days ago!
[Samsung Galaxy Nexus] kuntau:
and you charge in the middle of it? show me the graph :angel:
[Samsung Galaxy Nexus] RoscoeDpG:
this was on 240 i just recently went up to 241 but so far seems similar in idle drain and usage.....

By roscoedpg at 2012-08-13

By roscoedpg at 2012-08-13

By roscoedpg at 2012-08-13

:good:
[Samsung Galaxy Nexus] kuntau:
This is not almost 3 hours and not 45% left so I can confirm you do charge in the middle of it of what you claim before. BTW the above stats is normal nothing extraordinary :good:

---------- Post added at 09:46 AM ---------- Previous post was at 09:42 AM ----------

When you become as big as CM it is not easy to declare anything stable while not reaching their standard.. with their long list range of supported devices it is just gonna backfire back to them. It is totally different with other ROM with only 1 2 3 devices
[Samsung Galaxy Nexus] dandyqb:
i'm having a good battery life with this combo -> franco kernel + JB 4.1.1 JRO03C OTA by bigxie than franco kernel + Minco v3 ROM :cowboy:
[Samsung Galaxy Nexus] chugger93:
What the sh8t are u boneheads talking about. Cm10 is stable as ****. I run kang cm10 and this kernel and my phone smokes its so fast and stable. Battery life? Ya...I won't even go there and embarrass u
[Samsung Galaxy Nexus] imtjnotu:
Just flashed 241 on xenon v8 and I got stuck at the Google splash screen... Couldn't even get to boot screen

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nnnnr14:
How long did you wait?

sent from my 1.42hz Franco kernel Gnex!
[Samsung Galaxy Nexus] Aweloi:
This kernel is amazing! Great, great work with this one! Immediately bought the updater. Got to finically support this kind of work. :)
[Samsung Galaxy Nexus] brocktice:
9.1 = battery whore

I have been running the Franco kernels since I think #5 or #6, so far they have been great. However, I was running 9.1 and it sucked battery like I have never seen before on this phone, just totally abysmal. I'm trying 9.2 now to see if it helps. I may also try the interactive governor, which I saw suggested here. Just adding a data point -- keep up the good work, Francisco!

EDIT: I noticed with 9.1 the phone was defaulting to a minimum clock of 700 MHz? I'm trying forcing that to 350 with SetCPU now. Might be the culprit.
[Samsung Galaxy Nexus] abz54:
Im on GSM in the UK
[Samsung Galaxy Nexus] DivinityCycle:
What (if any) effect does this have on battery life? I'm trying to be disciplined and leaving my phone as is for at least one "complete" charge cycle to help get some baseline numbers for my own testing / reference.

My plan is to let the current cycle run completely down, then update to Franco's 9.2 kernel and possibly test that build.prop. I haven't looked at the CM9 nightlies recently, so I may update my ROM as well.

Too many variables!
[Samsung Galaxy Nexus] Dr_Ownage:
Franco sets it to 700 because of race to idle. Your phone SHOULD get to idle fast and there for increase battery life if you have the Min set to 700...
[Samsung Galaxy Nexus] lichti1901:
Have you wiped your battery stats? Maybe thats the issue!
[Samsung Galaxy Nexus] DivinityCycle:
Just to check my understanding of this, the battery stats are calibration values. The "proper" way to clear them is to fully charge your device, then clear the battery stats, then let the device completely discharge and die. Is this correct?
[Samsung Galaxy Nexus] Spronx_:
Thought I would share my experiences with this.

Running AOKP build 10, franco kernel #8, GSM extended 2000mah battery - this seems to be the winning combination for me.

Everything runs perfect and the battery life could not be better.

Easily reached 38 hours from a single charge, with normal use.

Keep up the awesome work!!
[Samsung Galaxy Nexus] mDroidd:
it is really funny to know, that when you buy a phone, It can do three times better with doubled battery life with a franco.Kernel :)

Greets!

| ThunderG # Optimus One |

Nitrogen

AOSP, Theme Chooser on Nitrogen

| Maguro # Galaxy Nexus |

working on ICS theme :P​
[Samsung Galaxy Nexus] loudaccord:
Yes up til 'and die.' Let it get down to about 20% and you should be good to go.
[Samsung Galaxy Nexus] Thracks:
Regarding my deep sleep battery drain in this post:

It is the battery log from the "Battery Monitor" app in the market.

In this instance, WiFi was off. I don't turn it on unless I need it. I am thinking about switching to "only when plugged in," however.

I've uploaded a CWM-flashable version here: http://www.zshare.net/download/9830316040a12868/

It's also worth noting to everyone that I have hotplug enabled. Between that and the conservative governor with the 700-1350MHz steppings, everything is fantastic.

---------- Post added at 04:31 PM ---------- Previous post was at 04:26 PM ----------

Charge to 100% (4201mV on the SGN). After that, unplug your device and wipe battery stats. Run it until it dies, and keep trying to turn it back on until it won't even do that any more. Then charge it back to 100% on AC power only.
[Samsung Galaxy Nexus] daandman:
Is there any difference between wiping battery stats in recovery or with an app like battery calibration?

I saw before you should recharge it after it dies with power off, is that necessary?
[Samsung Galaxy Nexus] Thracks:
Highly recommended. :)

No difference. Both just delete the batterystats.bin file.
[Samsung Galaxy Nexus] grinch247:
for clarification...I have setcpu configured like:

1200max

700min

with Interactive..

Under Profile with screen off:

350max

350min

with Interactive

is this proper or is there something more/better effecient?
[Samsung Galaxy Nexus] Redflea:
Just so you know, the batteries in our phones do not like being fully discharged...not good for them. If you keep them from falling below 40% or so on a regular basis, you'll get longer and better life from your battery. You do not have to discharge to zero to calibrate, you can simply run it down half-way or so and then recharge and clear the battery stats easily using the Battery Calibration app. Discharging to zero is overkill, and if done frequently for calibration will negatively affect your battery.