yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Redneck Trash:
Apparently I'm a little dense today. What does everyone mean by active bar?

Set from my toroplus
[Samsung Galaxy Nexus] _chanstar_:
It seems you may have already flashed a new ROM and Kernel. But if you run into the issue again, connect your phone to your PC with a Toolkit installed and have the Stock boot image ready to flash. Once your phone boots back up, quickly flash the Stock image.

The boot loops should stop and then un-check all 'set on boot' options in FKU. You can then flash the latest nightly and manually set your settings again.

Hope that helps.
[Samsung Galaxy Nexus] bradm23:
Could be few things... Check better battery app for rogue apps using battery. Also, it might just need time to settle in
[Samsung Galaxy Nexus] shreddintyres:
my experience has always that the kernel takes a couple days to settle in after which i get back to good ole 1-2% battery drain with background data on
[Samsung Galaxy Nexus] osm0sis:
I agree! I think the interactive changes alone have gotten rid of the jittery scrolling in Stock Browser at 192MHz min. Testing that out with cfq now. So far cfq somehow seems "lighter" for scrolling where deadline feels "heavy". Gonna try it with some games in a bit. If anyone's ever played that Frisbee game, I find that when it hits the stars you get dropped frames, so I've been using the smoothness of that as a bit of a benchmark. deadline was better than noop was better than bfq in that scenario. Overall I find bfq to still be better than noop though. Hopefully cfq can trump them all. :)

Not entirely sure but I think he means what I mentioned the other day about how since JB4.2 the Awake bar in Battery details graph barely ever has anything in it, even though the screen-on bar below it is showing accurately. Someone thought it might be that it's only reporting Awake during screen-off now, but I've had it also randomly show during screen-on time too so I think that theory is out. Hopefully JBQ can shed some light on it! :good:
[Samsung Galaxy Nexus] duduzinho15:
I revert to r345, but when i have time i Will do it. Thanks
[Samsung Galaxy Nexus] osm0sis:
Bootloops? How far does it make it before it reboots?
[Samsung Galaxy Nexus] bradm23:
I've played the Frisbee game, i think it lags out because of the sound it makes when u get a star. Some reason any time audio is played i get that type of bog down
[Samsung Galaxy Nexus] gaich:
I think I have. In the morning I posted this screenshot, I had 57 % and in 3,5 hours my battery drained to 0 without any obvious reason - just some 20 minutes of music, maybe 15-20 of browsing, 10-15 of reading and some manipulations with settings and notes...

Who`s this misterious JBQ?:p
[Samsung Galaxy Nexus] shreddintyres:
Jean Baptiste Qeuro , technical Lead of AOSP at Google
[Samsung Galaxy Nexus] Khizar:
no, idle drain is pretty good on r348
[Samsung Galaxy Nexus] Culex316:
Hey franco (or anyone else reading this), does your kernel have MHL enabled? (The usb to Hdmi thingie)
[Samsung Galaxy Nexus] Khrushy:
MHL works fine. I use it all the time. :good:
[Samsung Galaxy Nexus] DoesntPostAThing:
It seems that after I flashed r348 settings -> battery only shows a graph, no detailed apps and "screen" and stuff? I flashed r345 over and same thing.
[Samsung Galaxy Nexus] gikoche:
on firmware Xenon RC3 348 kernel update, the phone freezes after some time, only helps the pulling power. Fell back to the kernel 345 and everything is fine. Also to all the previous kernels all right.
[Samsung Galaxy Nexus] franciscofranco:
Its incredible the amount of random issues people get. I wonder how many crap roms and crap apps and crap scripts people use...

For the user above, I don't have that problem, sorry.
[Samsung Galaxy Nexus] franciscofranco:
Its your problem, only added two interactive patches.
[Samsung Galaxy Nexus] mrm43:
I once had this problem on 4.1. After flashing roms (full wipe and format system), settings/battery had the graph only. Reflashed again, same thing. I noticed that while I was flashing, I was charging at the same time. Reflashed again but this time unplugged my cable. Problem fixed. I don't know if it was just coincidence but somehow it solved my problem.
[Samsung Galaxy Nexus] alangrig:
Totally agree.

Never had issue with your kernels: reboots, SOD. At least on latest kernels for Android 4.2.1

R348 first charge
[Samsung Galaxy Nexus] llevo3:
OMG! I went to sleep with 93%, and after 6 hours i woke up with....... 93%!!!

r348, AOKP 16-12 Steve Spear, osm0sis UV and colors, min/max CPU 192/1305, hf 1036, ibf 729, IO cfq, TCP westwood,

very snappy, no lags, no SODs, no reboots, just PERFECT!

thanx Franco :good:

EDIT: wi-fi on, sync on
[Samsung Galaxy Nexus] _chanstar_:
Lol you're good bro. Sux how people complain about your kernel when it's the other ish they have. Your kernel is amazing and I don't know and don't want to know how you do it lol. But keep it up!

Chanstar Entertainment
[Samsung Galaxy Nexus] teriemer:
OMG r348 with CFQ scheduler is smooth!!!

I'm speechless :good::good::good::good:

Lets see about battery the next days...
[Samsung Galaxy Nexus] gaich:
The same firmware and kernel, no freezes.
[Samsung Galaxy Nexus] anshulajain:
Great kernel, franco! I was an avid fan of your kernels when you built for the Nexus S...you're following the great trend with Galaxy Nexus as well!
[Samsung Galaxy Nexus] The Gingerbread Man:
I have bumped min freq up to 384. Literally only tapatalk has minor stuttering and its directly related to the scroll bar on the right and sometimes pictures. Everywhere else at 192 is fine. Forcing 2d GPU rendering didn't really help either, tapatalk seems like its in need if being updating and coded better. Otherwise I'm very happy with 348 and worthy of milestone status :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kaluoshi:
@franciscofranco, did you removed high performance sound and volume boost in 4.2.x kernel? cause i can't find "/sys/devices/virtual/misc/soundcontrol" or "/sys/class/misc/soundcontrol/" :( thanks man
[Samsung Galaxy Nexus] gikoche:
Perhaps the problem is that I want to update gapps for 12,12,12?
[Samsung Galaxy Nexus] xeonyxorich:
Yeah, but not as severe as you. Checking upon it, in the kernel wakelocks section of BBS, powermanagerservice had been running since boot. So it hasn't gone into deepsleep yet. I'm just going to see if it'll resolve itself for now.
[Samsung Galaxy Nexus] Khrushy:
Weird. Using the xda app or some other tapptalk? Definitely sounds app related rather than a general issue. Maybe clear all app data and reinstall?

I dialed min CPU back to 192 today (from 384) given the new interactive patches. Seems smooth so far.
[Samsung Galaxy Nexus] gaich:
Yes, my gapps are 12/12/
[Samsung Galaxy Nexus] :
Just stopping by to say tks Franco! I've been back on my Gnex lately & your kernel is running great as always.:thumbup:

Sent from my Galaxy Nexus (Aokp & Franco kernel)
[Samsung Galaxy Nexus] The Gingerbread Man:
Its the tapatalk app, and its definitely app related not kernel. You can see it slow or jitter if you try to swipe or scroll really fast down the page when reading in threads (like the speed bumps osmosis and yellow were talking about in stock browser some while ago). Am going back to 192 as in fairness its about the same for both speeds and I'll blame bad app coding for now :p thanks :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] epunk:
stock JB 4.2.1, rooted,SuperSU 0.99,, get SODs all the time with R348 (never did until now)

Default settings in Franco app as well.

Attached is a logcat after rebooting

Reverted back to R345 in the meantime
[Samsung Galaxy Nexus] sajty:
If you are talking about lags when scrolling in Tapatalk,its definitely app related.I tried 6 kernels and its lagging with all of them.
[Samsung Galaxy Nexus] F_T_B:
Nope, JBQ said he has no idea.
[Samsung Galaxy Nexus] lasentenza:
I do too... first time I got SOD with franco kernel... :confused:
[Samsung Galaxy Nexus] Sailor Saucy:
Had a SOD with 348 last night, running everything stock except CFQ scheduler. As a result I missed my alarm! But it's no big deal, work's a pain anyway and I got away with it.

Sorry - not sure how to access logs.
[Samsung Galaxy Nexus] chickentuna:
this thread is great, I've learn so much about kernels and how it controls the OS/system. This isn't just your ordinary kernel thread, this is franco's kernel thread and it's just awesome
[Samsung Galaxy Nexus] epunk:
@Sailor Saucy

I used the Galaxy Nexus toolkit (you'll find it the the GNex section, should be amongst the top threads).

Its under the Logcat section.
[Samsung Galaxy Nexus] mannyvinny:
Can I use this kernel with Cyanogen 10.1 nightly build?
[Samsung Galaxy Nexus] gautam_nexus:
Yes... And please don't quote the entire OP
[Samsung Galaxy Nexus] Khizar:
yes the 4.2.1 kernels will work on cm10.1
[Samsung Galaxy Nexus] mannyvinny:
Any battery drain issue??:silly:
[Samsung Galaxy Nexus] Sik-1:
Dude it clearly states what it is this beast runs on in the first couple sentences, smh shame u had time to quote that and didn't even read it

BTW yes it does work on cm10.1, it is 4.2.x

Sheesh that was annoying
[Samsung Galaxy Nexus] mannyvinny:
Ya my fault..didn't read.but pls dont laugh atleast. I was just assuring myself so that i wont mess up wid my device.

:o
[Samsung Galaxy Nexus] Khizar:
read the thread.. and you will find out if there are any issues
[Samsung Galaxy Nexus] kaluoshi:
can anyone help me? thanks :good:
[Samsung Galaxy Nexus] RevengeFNF:
Franco, i found a problem in the new r348, probably because of the new Interactive Patchs.

When screen on, my phone is almost alwasy at maximum speed. I testid with the device monitor in your app. An i see it also with Cpu Spy.
[Samsung Galaxy Nexus] tetrakinitis:
He removed because it was buggy. He will add again sometime in the future.

Sent from my SmoothCriminal™

---------- Post added at 01:10 PM ---------- Previous post was at 01:04 PM ----------

No such problem for me. Have you keep the stock kernel settings?

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] Khrushy:
Not here. Problem is something with your setup.
[Samsung Galaxy Nexus] RevengeFNF:
Very Strange. Gonna try with OnDemand to check if its an app doing that.
[Samsung Galaxy Nexus] smileyanz:
Not here as well and running as good as anything I've tried in the past. Hats off to Franco . :thumbup:
[Samsung Galaxy Nexus] kaluoshi:
thanks man, sorry i finished my daily thanks :(
[Samsung Galaxy Nexus] RevengeFNF:
Ok, it was probably a Rogue App, because i rebooted the phone and its working fine now.
[Samsung Galaxy Nexus] doomed151:
Awesome standby with r345
[Samsung Galaxy Nexus] duduzinho15:
All the time :-$
[Samsung Galaxy Nexus] Wynnded:
To those of you who have changed TCP. How are you doing this? I have looked into doing this via the paid app, but when I press on that option nothing happens. My initial though was that it is deactivated but in the last couple days I've read folks listing that they've set theirs to westwood. This is what I had mine set to with 4.1 but haven't messed with it since using 4.2. I haven't seen anything in the thread about this in quite some time either, so I ask. Thanks gang.
[Samsung Galaxy Nexus] Sik-1:
How does that help???

Are you coming from a different kernel??? The only time I recall that happening to me is if I came from a different kernel that changes the ramdisk
[Samsung Galaxy Nexus] tetrakinitis:
It's ok! ;)

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] yellowdie:
The app works for me. I also do it with init. (see the second OP for the command lines). I'm running Westwood just fine. :)
[Samsung Galaxy Nexus] Khrushy:
Franco paid app. Seems to change fine for me.
[Samsung Galaxy Nexus] calinoii:
Hey can someone help me with this ? http://xdaforums.com/showthread.php?t=2055260 I'm running on AOKP 4.1.2 and I'm stuck with this
[Samsung Galaxy Nexus] vigan_ks:
r348 is amazing smoothness and great battery life rhank a lot. my only question is with color setup how to setup our colors to be like dinamik option on i9300 (s3).
[Samsung Galaxy Nexus] Khizar:
use a kernel app like FKU or trickster to modify color settings
[Samsung Galaxy Nexus] timbck2:
Ditto. I'll add that with r348 and cfq scheduler, scrolling is smooth as buttah even in Tapatalk! :cool:
[Samsung Galaxy Nexus] vigan_ks:
i already using trickster but i dont know correct configuration
[Samsung Galaxy Nexus] alfiemenace:
Wow doomed! Don't know you're here, I'm a fan of your work on the arc/s forums!

Stock ROM, custom user.
[Samsung Galaxy Nexus] Paragon_X:
So my experience here with Franco kernel I've found that r335, r345, r348 seem to do the best battery life for me on AOKP 12/06 averaging 12-16hrs combination of wifi/3g with 2-3 on screen time. I commute to work told of 2 hours of day and music plays an integral part of my experience with the kernel. So my concern is with the latest version r348 which has noticeable stutter, along with every other version aside from r335 and r345. My settings remaing 537mhz screen off and min 345mhz. I use poweramp and I'm not sure how to address this. I've revert back to r345 but I've switched to scheduler to cfq and it does seem smoother imo, so I'd really like to stick with r348 atm... does anyone have suggests how I can eliminate or reduce the stutters? If it matters quality of my music is 320kbps, thanks in advamce!
[Samsung Galaxy Nexus] Khrushy:
Odd. I'm on the Fitsnugly AOKP Nightlies and I get no stutters with Google Music. Min 384 / max 537 should be fine for playing even 320kbps with screen off, but you could always bump up "screen off max" to 729 to see if that helps fixes it.

Alternately, test with a different music app, just to see if part of the problem is power amp, or if it's all ROM/kernel based.
[Samsung Galaxy Nexus] Paragon_X:
Thanks for the suggestions mate, a few obvious things I can go on that I never even considered. Will report back later.
[Samsung Galaxy Nexus] calinoii:
What is the best gov and i/o scheduler?
[Samsung Galaxy Nexus] 5pace:
Funny, how people complain that they have problems with the kernel, like SOD, wakelocks, etc. I didn't even have a single problem with any of the kernels since I bought my phone. Might be phone specific, but I highly doubt people tend to use those RAM scripts, RAM managers or poorly baked ROMs which makes them cry. Believe me those pesky stuff aren't even needed. I am on CM10.1 official nightly and the phone beats every other dual-core phone it comes across in performance, may it be the benchmarks or the daily usage. :)

Yeah, thanks again to osm0sis for his awesome settings. :good:

Personal preference (I like to use CFQ I\O scheduler with Interactive governor). This is a good post to know about governors and I/O schedulers, which can be found HERE. :)
[Samsung Galaxy Nexus] Paragon_X:
interactive - cfq/deadline
[Samsung Galaxy Nexus] osm0sis:
I think you're getting confused... r348 is the first build with cfq. Try raising hispeed freq a notch to see if that helps, that and/or reduce the go hispeed load so that it ramps up sooner, hopefully before it gets the chance to stutter.

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

Awesome. :rolleyes: I guess we can just add it to the list of things Google broke and somehow failed to notice in JB4.2.
[Samsung Galaxy Nexus] kissme99:
Hello. I don't know why but my Nexus became so slow. All apps are opening really long time, about 20-30 sec (even apps like dialer, sms or people, when I tap on the icon the screen become black for a few sec and later the app is opening)

I am running stock 4.2.1 with latest franco kernel (stock settings)

What's the problem? Any solution?

PS: sorry for my English.
[Samsung Galaxy Nexus] supernova_00:
Thanks. I'll give it a try today, battery was too dead to notice anything last night.
[Samsung Galaxy Nexus] osm0sis:
I think it was that you put I've instead of I'd. Gotcha now. :good:
[Samsung Galaxy Nexus] arhung:
Still get some lag with 348, can anyone share the settings in the fku app?thx!
[Samsung Galaxy Nexus] 5pace:
HERE you go! :)
[Samsung Galaxy Nexus] Sik-1:
:D:eek:
[Samsung Galaxy Nexus] osm0sis:
I'm finding cfq and deadline pretty even. cfq might be a touch more smooth in the Launcher, Browser, etc., but deadline seems to edge it out just slightly in games (like with the star-lag I was talking about before in Frisbee :p), probably due to franco's patch for read prioritization. The interactive patches alone make r348 the smoothest in awhile, so it's actually hard to judge scheduler now, but basically I think bradm23 and gparmar76 are spot on with their assessments.
[Samsung Galaxy Nexus] Angelakaro:
Someone is playing modern combat 4? How does it works on your galaxy nexus? With franco kernel mine was running very smoothly,but after some times it's installed it doesn't run like before,it's laggy and my phone heat up much more quickly. It's my phone that need a refresh,or someone else is experiencing my problem?

EDIT: tried with all I/O scheduler but the result is the same
[Samsung Galaxy Nexus] timbck2:
I installed a color settings script in init.d, but what prevents Franco app from changing them back to my color profile settings when it runs (after init.d)? After rebooting, the app still shows my profile settings instead of the ones in the init.d script.

EDIT: Never mind, I forgot to set execute permissions on the script. It's working now.
[Samsung Galaxy Nexus] osm0sis:
Ah, I always have my f.Ku settings set to match my init.d just in case. ;)
[Samsung Galaxy Nexus] calibachrome:
Quick question, I've had juice defender installed on my phone since I've had it. Does it negatively or positively affect the custom kernel performance. Any insights or experienceswould be greatly appreciated.
[Samsung Galaxy Nexus] yellowdie:
When I'm testing init.d stuff I usually clear the f.Ku app data just for good measure before rebooting. :)

Bad. Don't need it at all. It takes more battery than it saves. :)
[Samsung Galaxy Nexus] osm0sis:
Kernel Emergency Settings Reset Zip

Alright so here's something that's been requested for awhile.

I wrote it up recently with Franco's stamp of approval, so I'm posting it here now. Please direct people back to this post from other threads.

This can/should be everyone's go-to when experiencing problems after updating to a new kernel build, you get stuck in a bootloop, or you think there's a conflict between ROM and kernel (or kernel tweaking app) you can't track down, since likely some leftover settings (voltages, etc.) are at fault. It's also useful if you just want to make sure you're running clean defaults. This should work on any device franco.Kernel and f.Ku support, as well as a variety of other devices, kernels and control apps: eXperience (Free/Pro), GLaDOS Control, TricksterMod, Trinity Kernel Toolbox, ROM Toolbox (Lite/Pro), SetCPU, Faux123 Kernel Enhancement Project, Performance Control and Synapse.

Flashing this via custom recovery of your choice will delete the kernel app settings file(s), disable init.d and userinit.d scripts by moving them to a subfolder (/system/etc/init.d/off/ and /data/local/userinit.d/off/ respectively) and wipe cache and dalvik-cache for good measure.

Hopefully it helps!

Note: If your ROM has a Performance/Tweaking App built-in you should also manually disable any Set On Boot options it has. For example, I couldn't include clearing CM's Advanced Settings since they're built into the main com.android.settings/Settings.apk along with a lot of other Android OS settings (APNs, Developer Options, etc.), so to run clean and without conflicts on CM you need to unset them yourself.

You should also avoid having more than one control app installed at a time. Conflicts have been reported even with everything "unset" in two apps.

I also chose not to disable anything your ROM may have in /data/cron or /system/addon.d since some rely on it heavily, so you can choose to review those directories' contents and whether you want to leave them enabled on your own. I also left out disabling sysctl.conf since that's done by f.K and the Franco's Dev Team scripts, and also seemed a bit heavy-handed for this zip script.

Download counts for the previous versions: 790; 2678.
[Samsung Galaxy Nexus] shawnaye:
Thanks bro. Something that should have been done from the very beginning.

It's like standard procedure to use a cleaning script back when I was using my s2 just for good measure.
[Samsung Galaxy Nexus] osm0sis:
franco's zips do have a cleaning script. This is more for those who update (auto-flash or zip) and their f.Ku settings send them into a bootloop or something. Thanks yellowdie for reminding me; mentioning wiping f.Ku settings on the last page jogged my memory. :)
[Samsung Galaxy Nexus] timbck2:
Good idea.

I did that, but wouldn't Franco's default color settings still get applied after the init.d runs?
[Samsung Galaxy Nexus] allgsmnetwork:
set + 25

Hi ,

I set voltges like you and reboot tested on 2 rom,i up set just + 25 all mhz is ok very nice :good:
[Samsung Galaxy Nexus] osm0sis:
Nah. Those aren't set by f.Ku or script. They're hardcoded somewhere I think.
[Samsung Galaxy Nexus] allgsmnetwork:
OK friend, i using 345 tested now all -25 :D

Thanks for you :good:

you are very kind :)
[Samsung Galaxy Nexus] alfiemenace:
Fair enough, 3g data on 80% of the time :cool:

Stock ROM, custom user.
[Samsung Galaxy Nexus] allgsmnetwork:
Hi,you have navbar 24 dpi?where can I find?

Thanks :)
[Samsung Galaxy Nexus] osm0sis:
Back to deadline. cfq terribly lagged scrolling in Currents. :(
[Samsung Galaxy Nexus] Paragon_X:
CFQ isn't the problem, it's Currents lol... ugh terrible app, hoping Google combines the form of Current into Google Reader.
[Samsung Galaxy Nexus] irminsul:
Its really smooth here, with deadline slightly smoother than cfq, but hard to notice. Stock settings.
[Samsung Galaxy Nexus] osm0sis:
Right but with deadline it's buttery smooth on my device so I'll stick with it. ;)
[Samsung Galaxy Nexus] smileyanz:
Yeah I've noticed longer I've used Franco 348 it seems to get smoother. Think he's just about sorted it and wouldn't surprise me if a stable comes from it shortly
[Samsung Galaxy Nexus] malaroth:
Sync? Wifi? Rogue app?

JBSourcery 4.0 + r345 Franco FTW. Keep the Magic alive!

---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------

I did notice stutters with cfq more than usual so I went back to deadline too. Gonna go up a stage to 1406/384 from 1305 though.

JBSourcery 4.0 + r348 Franco FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] bradm23:
Noticed the same thing. I wonder how much tweaking Franco can perform on i/o schedulers
[Samsung Galaxy Nexus] nikulogical:
What about sio? I'm on lean kernel right now and interactive/sio is smoother than a baby's ass.

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] franciscofranco:
An IO scheduler tweaking part is planned to be included in the app soon. Its planned for a month already but as you can imagine I'm not an autobot machine, specially with CES coming I've been having so much work... I'll be at CES btw.

Nah, what we have is enough.
[Samsung Galaxy Nexus] malaroth:
I'm not sure Franco, I have my doubts still about whether you're fully human just now... you put out way too much amazing quality at such a rapid pace for me to not have doubts :P

JBSourcery 4.0 + r348 Franco FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] franciscofranco:
If you're using CFQ you can try these:

echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle

echo 0 > /sys/block/mmcblk0/queue/iosched/back_seek_max

echo 0 > /sys/block/mmcblk0/queue/iosched/back_seek_penalty

Tell me how that feels.
[Samsung Galaxy Nexus] jendrassik:
Please somebody explain me this behaviour. Image attached.

I didnt manage to fix it so my battery dramatically drains away.

Thank u all.
[Samsung Galaxy Nexus] nikulogical:
Turn off gps when you're not using it.

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] jendrassik:
I have it always off.

What is waking up the device so often?