yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] spirit1002:
Got a freeze about 3s. Device uptime 2day11h. CM11 M5. DirtyV-R 4/12.

Here is the log: https://www.dropbox.com/s/5fcsb065t7vtjwd/2014-04-15_13.47.zip
[Samsung Galaxy Nexus] luckana:
i got 1 or 2 freezes too, dunno if it's from the undervoltage or sth else
[Samsung Galaxy Nexus] pvkiniyan95:
Glass updates are out, no idea about the source though hope it enhances gnex
[Samsung Galaxy Nexus] WILLI120:
Was asking myself the same thing. Same processor as our GN so maybe someone is able to port the 3.4 kernel :)
[Samsung Galaxy Nexus] Shambola:
So is still safe/useful to use lagfix on KK?

I dont' remember...(issues of age)

OT: I laugh every single time I look at my signature, as if it were not mine... LOL
[Samsung Galaxy Nexus] ramos247:
random soft reboot. liquid latest with smity4-12 fresh install 18 hours prior

log

https://www.dropbox.com/sh/ut67h84mbs6gfoq/GNwrI7Mi8W
[Samsung Galaxy Nexus] büscher:
I did some testings with tripndroid

First I wanted to know which RAB to choose, I did the same test like I did to find out my RAB on zen.

Did 30 benchmarks with multiple file sizes (100MB, 10MB, 5MB, 2MB, 1MB, 512KB) with android tuner what gave me a RAB of 1532KB as the best overall. (With zen it was 5632KB)

Then I tested each file size 10 times with tripndroid@1536 and zen@5632

As a result I can say zen@5632 is faster that tripndroid@1536. Especially with large files (100MB) zen@5632 is 66% faster than tripndroid@1532. I also did a cross check with zen@1532 for 100MB files and the result is about the same.

with smaller files the difference is -4% (10MB), +3% (5MB), 0% (2MB), +8% (1MB) and -1% (512KB)

maybe I'll find some more time to do such a detailed test on other io schedulers.
[Samsung Galaxy Nexus] DR3W5K1:
I like where your going with this. I'm interested in Zen vs Deadline those are my gotos.

Thanks keep up the good work!
[Samsung Galaxy Nexus] Atento:
OS is consuming too much and I don't know why. Any clues? SmithV 0412.
[Samsung Galaxy Nexus] büscher:
just did the same test with deadline@3072 (best overall)

in this test zen was equal or better than deadline.

100MB: 36% faster

10MB: 1% slower

5MB: 1% slower

2MB: 1.5% slower

1MB: 10% faster

512KB: 1.5% slower

please have in mind that every phone acts a little different and this test is not 100% accurate.
[Samsung Galaxy Nexus] infectedorganism:
If you're up to it, at some point could you test sioplus?
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] latest on LMK issues from Fancy:

Edit: Didn't read all the way through the Fancy thread; I see you spotted this already. :p

Didn't someone else in here mention vmalloc was unnecessarily high on our devices recently?

---------- Post added at 02:30 PM ---------- Previous post was at 02:21 PM ----------

Here we are, it was [MENTION=4328678]metalspring[/MENTION] at the beginning of March:

http://xdaforums.com/galaxy-nexus/development/kernel-dirtyv-t2613655/post50747678#post50747678

Goes through the next page with [MENTION=2838735]aosp[/MENTION]. :good:
[Samsung Galaxy Nexus] bsmitty83:
I used to have vmalloc set at 480 but [MENTION=4328678]metalspring[/MENTION] was wondering why and not 740 like the other kernels . so he was wondering why it was set so LOW , but points for the recalling of the mention ...lol
[Samsung Galaxy Nexus] osm0sis:
Haha true true.. I see that now. But was that not around the time that all this LMK craziness started? So it all kind of makes sense.

Edit: Or not, since that actual commit was 2 years old. :confused: :p
[Samsung Galaxy Nexus] Punkiderma:
Last dirtyV is smooth for me, but sometimes my phone freezes (release before the last one didin't have this problem on my phone). Also, I'm getting some launcher redraws (nova launcher).

Apart from this, multitasking is great!
[Samsung Galaxy Nexus] Droiderat:
OK, I wasn't sufficiently precise. The launcher (itself) isn't being killed. When I would switch to it, I would have a screen of wallpaper, with a circle near the bottom w/6 dots in it. :) What I *didn't* have was any icons; they would reappear 4-7 seconds after I returned to the launcher home screen. Interestingly, the layout of what appears to be the launcher is actually stored in the data for Google Search. Clear the Google Search data, and you will lose all of your customized icon placement, and will be back to a virgin start screen.

So, as recommended, I did some experimenting. Open App and Secondary Server values had no effect on my reported issue. However, I found that by increasing the Content Provider value from 20 to 30, then my issue was resolved. After that, any time I return to the launcher home screen, it has icons (and there is no launcher "redraw"). So, my MinFree values are 2, 5, 10, 15, 30, 25. Smooth, no freezes, and no random reboots ... oh, and icons w/o having to wait for them.
[Samsung Galaxy Nexus] bsmitty83:
You guys are bringing some great stuff to the table . thank you for taking the time to not only solve your problem , but let everyone know as well what solved it . I've found so many cures for little annoying problems like that just by trolling old threads and reading peoples comments just like the one above my post .

I may have the best "seat" in the house for bugfixes since I did make it and I have the most knowledge on all the trivial little things I did to the source that can affect everything , but sadly i can't fix everything or even know what it is or how to fix it , but the community on this thread is nothing but helpful and cool with everyone .

I continue to work on this kernel simply for you guys now . I use my gnex for testing and a house device .

I may just go back to my old lmk , it was working good and I wasent really finished with it , but who knows . I'm looking at a few things right now , but thanks again for the responses in this thread . I feel honored that I get to host such a great thread .
[Samsung Galaxy Nexus] jhonnyx:
Dirty gang is always here for you :). Thanks bsmitty83 for staying with us
[Samsung Galaxy Nexus] michierusama:
Neph told me once that his settings are the base to get your personal ones. You can tune and see what is best for your phone. Oh and I remember when I was a silent user here in xda. Just reading and downloading stuff. Without reporting but this thread was my door to being more active in this and more topics on xda.

So do you recommend to use Deadline@ 3072? I download torrents on my phone.
[Samsung Galaxy Nexus] dbh369:
Just 1 question, is there some factor that lets you get to 5632, not an option on trickster...
[Samsung Galaxy Nexus] michierusama:
Hey I was thinking the same, how can we get that value, trickster users.
[Samsung Galaxy Nexus] brymaster5000:
[MENTION=4608636]bsmitty83[/MENTION] check this $h1t out:

Sense4 on my m7 vzw. Lol...sorry for the troll. Just too excited about getting it to work.
[Samsung Galaxy Nexus] HONG86:
Well...

You should try smitty 4.13

Feel so good! ;)
[Samsung Galaxy Nexus] bsmitty83:
Op updated , SmittyV 3/15 ,went back to previous lmk , lots of work to zram , added a whole new zRAM back end from nexus5 3.4 kernel . it works. Still not finished yet but its there to try
[Samsung Galaxy Nexus] büscher:
Did not find the time to complete my procedure yet. What I can say that on my phone sioplus@512 or @2560 give the best results overall.

---------- Post added at 07:59 AM ---------- Previous post was at 07:48 AM ----------

Hm, with my testings I'd recommend zen@5632. Its faster with biger files. But on the other hand bittorrent loads small parts of big files. I think you wont feel the difference by downloading but by copying and moving files.

---------- Post added at 08:01 AM ---------- Previous post was at 07:59 AM ----------

I set it with an init.d script, you can go up to at least 6MB RAB.
[Samsung Galaxy Nexus] dbh369:
Smitty 3.13, long wake-up lag

https://app.box.com/s/0zjhhpv64i901lbz9ayg
[Samsung Galaxy Nexus] Unzitron:
This new Zram works really well.
[Samsung Galaxy Nexus] gohamstergo:
Does wireless N not work with dirty/smitty? I thought I remembered reading something about that a couple hundred pages ago...I'd search, but can't exactly search for "wireless n" as the n would just be ignored. Asking since I recently tried connecting to a wireless n router and it refused to connect. Tried both the 2.4ghz and 5ghz bands. Anyone remember if my memory serves me? [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] büscher:
I redid the I/O benchmarks on newest SmittyV with whole new results...

I really begin to think that my storage is just borked...

New Results:

sioplus@512:

100MB: 37.84MB/s

10MB: 46.84MB/s

5MB: 30.08MB/s

2MB: 17.85MB/s

1MB: 10.94MB/s

512KB: 6.63MB/s

zen@5632:

100MB: 37.80MB/s

10MB: 45.68MB/s

5MB: 30.49MB/s

2MB: 17.47MB/s

1MB: 10.79MB/s

512KB: 6.68MB/s

deadline@3072:

100MB: 36.71MB/s

10MB: 45.47MB/s

5MB: 30.38MB/s

2MB: 17.57MB/s

1MB: 10.68MB/s

512KB: 6.62MB/s

tripndroid@1536:

100MB: 27.47MB/s

10MB: 45.66MB/s

5MB: 30.60MB/s

2MB: 17.22MB/s

1MB: 11.05MB/s

512KB: 6.52MB/s

So all I can say now is:

sioplus is the fastest scheduler overall

tripndroid really has problems with big files

the differences between sioplus, deadline and zen are extremely small

maybe someone can confirm my measurement... what I did is the same as before but without any break between the measurements.

1. Lagfix

2. Test every file size 10x with each governor

3. Take average out of excel

sorry for the false information some pages back...

Edit: I may also found out why my wifi's get deleted randomly:

If I have backup&restore enabled in settings my remembered wifi's are gone after a restart or even just a disconnect.

If I disable it they also get lost

What works:

Disable backup&restore in settings. Forget the networks, add them manually (not searching and just entering the password). Power off and reboot - they are still there. Will report if this did not work.

and [MENTION=2408813]gohamstergo[/MENTION]: I also have more wifi problems, I can't connect to my 5GHz n network. The 2.4GHz works though.

Edit2: goddamnit, another run and my phone gets 80MB/s on 100MB files... I don't get it... maybe just forget about those benchmarks and use whatever you like...

Edit3: and if I continue the scores go down to 40MB/s then 30MB/s and stay there.
[Samsung Galaxy Nexus] pkgnex:
-

I don't believe wireless-n connectivity is a problem... just WEP security is no longer supported (you have to use WPA or WPA2).
[Samsung Galaxy Nexus] gohamstergo:
Ya, I'm on WPA2. But hmm.. strange..

Thanks. Odd I couldn't connect to either. :|
[Samsung Galaxy Nexus] bsmitty83:
Wep should be the only thing not working for WiFi . I use my n-router on 5ghz all the time .
[Samsung Galaxy Nexus] büscher:
do you own a netgear router btw?
[Samsung Galaxy Nexus] gohamstergo:
Linksys E4200 with DD-WRT.

I see..I'll keep fiddling with channels and other settings to see if I can get it to work. Not the biggest deal since the phone would never utilize max N speed anyway.
[Samsung Galaxy Nexus] büscher:
I'm on a netgear with OpenWrt.

Do you use CCMP as encryption? If so, try something else like TKIP or AES...

whoooop, that did it for me, just now. right now :D:D:D forgot to change it on my second router (FritzBox) and now I'm able to connect to my 5GHz nwtwork. whuupwhuup.

Annoying problems solved this week: 3 :good:
[Samsung Galaxy Nexus] gohamstergo:
haha nice, but no, I'm using AES. Thanks for the help though, I'll investigate further when I have time.
[Samsung Galaxy Nexus] TheMan0790:
Just curious (sorry for OT), but how easy/difficult is it to set up DDWRT? Was interested in trying it in the past, but didn't think I would get it working properly...
[Samsung Galaxy Nexus] bsmitty83:
SmittyV4.15
[Samsung Galaxy Nexus] dbh369:
Had an sod and a warm beer reboot on 4.13, but with these results I clearly need to update again!
[Samsung Galaxy Nexus] frimpasi:
Plis [MENTION=4608636]bsmitty83[/MENTION] give us your settings XD. It's impossible to me reach these numbers...
[Samsung Galaxy Nexus] büscher:
I changed some values in my init.d script for SmittyV/dirtyV.

Because of my latest storage benchmarks I switched back to sioplus

Also I lowered input_boost_freq, high_speed_freq, max_screenoff_freq and min_freq. (It's still buttery smooth for everyday use).

In addition I switched to the new minfree values for latest SmittyV.

you can grab it here
[Samsung Galaxy Nexus] osm0sis:
I used to be all about DD-WRT, I even left a good guide thread there for the WRT160Nv3 that you might be able to use for another device to make it easier for you to set it up. :good:

...Then it became apparent the mod team there were kind of huge dicks and removing valid posts they shouldn't be, like when I tried to bring up issues that were long unaddressed (like obvious important stuff like builds exceeding the sizes of the flashes they were intended for..) :eek:

Anyway, long story short, I left and now I'm rocking Tomato by shibby on my WRT300Nv1 and it's like a new device! :)

Those latest results you posted were a really good read! Thank you for that! Honestly the best 3 all had good results within what looked like a normal variance though; they all seemed on par. How did you pick sioplus out?

Holy ****!:D
[Samsung Galaxy Nexus] büscher:
That was just the feeling while I was on sioplus, it somehow felt snappier... like opening whatsapp just felt smoother...

No numbers behind, only gut feeling [emoji28]
[Samsung Galaxy Nexus] bsmitty83:
1.6 GHz CPU

512gpu

Interactive

Zen

4080 read-ahead

Cab off

Throttle off

Airplane mode . WiFi off .

Stock minfrees

Stock voltages .

Everything else stock

SmittyV 4.15.14
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION]

/sbin/suspend_trim:

#!/system/bin/sh
# boype @ xda-developers.com
#
# modified by osm0sis @ xda-developers.com

bb=/sbin/bb/busybox

TRIMHLPFILE=/data/trimhelper
MASTERSWITCH=$($bb cat $TRIMHLPFILE | $bb sed -n '3p')

if [ $MASTERSWITCH -eq 1 ] ; then

RESUMETIME=$($bb cat $TRIMHLPFILE | $bb sed -n '1p')
CURTIME=$($bb date +%s)

if [ $RESUMETIME -eq 0 ] ; then
$bb sed -i "1s/.*/$CURTIME/" $TRIMHLPFILE
else
NOTRIMTIME=$($bb cat $TRIMHLPFILE | $bb sed -n '2p')
TIMEDIFF=$((CURTIME - RESUMETIME + NOTRIMTIME))
if [ $TIMEDIFF -ge 1200 ] ; then
OFFTIME=0
while [ $(dumpsys power | $bb grep mScreenOn | $bb cut -d= -f2) == "false" ] ; do
$bb sleep 1
OFFTIME=$((OFFTIME + 1))
if [ $OFFTIME -ge 60 ] ; then
CURIVAVOLT=$($bb cat /sys/kernel/debug/voltage/vdd_iva/curr_vp_volt)
if [ $CURIVAVOLT -lt 925000 ] ; then
$bb fstrim /data
$bb fstrim /cache
TRIMCOUNT=$($bb cat $TRIMHLPFILE | $bb sed -n '4p')
$bb sed -i '2s/.*/0/' $TRIMHLPFILE
$bb sed -i "4s/.*/$((TRIMCOUNT + 1))/" $TRIMHLPFILE
fi
break
fi
done &
fi
$bb sed -i '1s/.*/0/' $TRIMHLPFILE
$bb sed -i "2s/.*/$TIMEDIFF/" $TRIMHLPFILE
fi

fi

Made some alterations that seem to work. It waits 60 seconds before trimming and aborts the counter if at any point in that time the screen comes on.

I took out /system to speed things up since we have it covered with discard in the fstab. It also shouldn't necessarily tie up the suspend/wake anymore/as much since I put it in an independent loop. :)

Edit: Oh, and I figured out what the IVA voltage check is for too! It's so it doesn't trim while screen off music playing. Very clever of boype. :good:
[Samsung Galaxy Nexus] ashclepdia:
I just gotta say(still on 4.12 haven't had connection couple days lol catching up)

Anyways:

You'd be proud of me(and [MENTION=2838735]aosp[/MENTION] too! Lol) I made it past the 24hr mark uptime! Finally!!! Hahaha I usually swap batteries when low but decidedly made sure to NOT let device die just to see how she behaves after a few days of uptime.

I ran that logcat grep after 36hrs and saw the trim DID indeed run(my device prolly needed that BAD lmao)

And I'm now at +72hrs uptime and damn my Gnex STILL running smooth. Can't wait to test out these new versions, but gotta say again [MENTION=4608636]bsmitty83[/MENTION] killed it on 4.12 version. Can't believe this thing still going strong after 3days up. Been while since I've even attempted that on this thing. So excited to try some newsness and for future updates. Amazing man, just amazing.
[Samsung Galaxy Nexus] bsmitty83:
Working on a super RAM version .......

Hope to have a release soon
[Samsung Galaxy Nexus] qwas7899:
Working great on latest Bam rom!
[Samsung Galaxy Nexus] juju2011:
I was using slimkat 2.3 beta, and carbon 01/14,14
[Samsung Galaxy Nexus] Culex316:
Glad to see a SuperRAM version is in the works!

I have a few questions though...where can I find online documentation regarding the meaning of all those voltage regulator symbols? I know VAUX1 has to do with the screen and VMMC is the NAND controller but what about the rest?

Also, does this kernel support loadable modules?

Otherwise, thanks! :laugh::good:
[Samsung Galaxy Nexus] abhishek93:
This kernel is awesome feels perfect in performance as well as on battery, but I have some problem with WiFi .. I can not connect my nexus through WiFi..
[Samsung Galaxy Nexus] Nemed:
I know it's a noob question, but i'd like to help…so...how can i provide a logcat?

Edit: nevermind, i figure it out! :)

I'm on cm11
[Samsung Galaxy Nexus] Vekhez:
You might wanna add this to the OP as the kernel features

KERNEL FEATURES:

Governors:

Interactive from 3.4.X Kernel (Default) with Early Suspend when screen goes Off

Conservative with Early Suspend cpu1 when screen goes Off

Ondemandplus

Ondemand

Wheatley

Performance

Powersave

Userspace

Hyper

Lazy

Hotplug Governors:

Abyssplug

Hotplug

Sakuractive

* Schedulers:

Row (Default and Optimized)

Bfq, Fifo, Vr, Sio, Cfq, Noop, Deadline, Fiops

* Cpu Freqs:

350Mhz (Default Min)

1200Mhz (Default Max)

+180Mhz

+230Mhz

+525Mhz

+810Mhz

+1350Mhz

+1350Mhz

+1420Mhz

+1480Mhz

+1560Mhz

+1640Mhz

* Gpu Freqs:

384Mhz

* TCP Congestion:

Westwood (Default)

Cubic, Bic, Westwood, Htcp, Hstcp, Hybla, Vegas, Scalable, Lp, Veno, Yeah, Illinois, Reno

Interactive Governor from 3.4.x Kernel

Content Adaptive Brightness

Voltages Control (Core, Iva, Mpu and more ...)

Blx control

Fastcharge control

High performance audio

Sound Boost control

Temp control

Vibrator control

Color Control

Gamma Control

Trinity Contrast
[Samsung Galaxy Nexus] mrgnex:
[MENTION=5427457]Vekhez[/MENTION]

Thanks I was waiting for this. I'm getting curious. Gonna test this..
[Samsung Galaxy Nexus] drmxmyt:
whats this cpu temp, freeram and load thingy in your statusbar?
[Samsung Galaxy Nexus] NeverSeparate:
Are you using a wireless network with wep encryption? I don't recall if this kernel is this way, but some kernels break wep compatibility. It's out dated anyway. Use wpa2.
[Samsung Galaxy Nexus] bsmitty83:
its called cool tool . its a free app from the goolge play store . a great little monitor tool ,thats always there realtime
[Samsung Galaxy Nexus] bsmitty83:
yes the kernel supports modules , as for the docs on the voltage regs try looking around here , someone posted what they were somewhere in the nexus thread , it might be in Neps custom kernel settings thread or in one of the mpokang threads
[Samsung Galaxy Nexus] bsmitty83:
i havent messe with wifi yet , i did update the drivers to 3.4 , but it breaks WEP , and native tethering so i reverted it .
[Samsung Galaxy Nexus] bsmitty83:
no your doing it right but if you have ADB on your computer , its easier to just type adb logcat and while you try to reproduce the freeze whach the terminal and you can coly and paste the output like you did . that way you can watch the log as it happens , but thanks for trying , i dont know if the one entry you caught ([ 01-18 14:49:00.910 28111:28111 I/Choreographer ]

Skipped 50 frames! The application may be doing too much work on its main thread.) may be the problem
[Samsung Galaxy Nexus] Nemed:
Ok, i'll try with adb asap!
[Samsung Galaxy Nexus] bsmitty83:
Cool thanks , I just personally find it easier to find what part of the log corresponds to what your doing on the device

I'm currently fetching the mainline Linux git and am gonna try bringing up the cpufreq drivers to current . maybe a few other things like block io and filesystem's too . and a superram version too lol . I'm getting busy on this project :sly:
[Samsung Galaxy Nexus] rtfpessoa:
Try to update little things. Like block and then fs. And post some versions here so we can do some testing on different devices.:good:
[Samsung Galaxy Nexus] Pjodor:
+1 superram :)

Skickat från min Galaxy Nexus via Tapatalk
[Samsung Galaxy Nexus] lagendbun:
[MENTION=4608636]bsmitty83[/MENTION] can you share the best setting for your kernel using trickster :)
[Samsung Galaxy Nexus] Nephilim:
So all versions will have the AK interactive?

Also, don't forget the f*cking fiops, never forget the f*cking fiops! :p

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Yes and I didn't (I hope)
[Samsung Galaxy Nexus] metalspring:
Btw, what is the difference between the 3 versions anyway?
[Samsung Galaxy Nexus] bsmitty83:
Dirty V is 5 MB less reclaimed Ram than bigmem 50 vs 55 MB . as close to normal as your gonna get from me

SuperRam is 69 MB reclaimed I believe . obviously 1080p does not work .

SmittyV is SuperRAM with less govs and schedulers , its also my personal kernel and test branch . I currently am using joes rcu on it that's about the only differences
[Samsung Galaxy Nexus] djtutis:
What module should I select in Touch Control to achieve double tap 2 wake feature? Thanks a lot again for your magnificent kernel!!!!
[Samsung Galaxy Nexus] Rushead:
Been running the latest Dirty V on interactive. Trickster shows the cpu spike to 100% occasionally, but no overheating / battery life issues (for the last 12-13 hours at least).

Why 10.2? I'm on FML 12-15 CM11 build. Runs great.
[Samsung Galaxy Nexus] bsmitty83:
Not really sure I don't use the app . maybe someone else here knows ?
[Samsung Galaxy Nexus] bsmitty83:
So does anybody like the all in one zip ? If so I'm trying really hard to put them in an aroma installer with a gapps package installer as well , maybe adblocker etc . any thoughts ? I stopped working in it to fix this kernel but this next update should be solid . just a little longer
[Samsung Galaxy Nexus] scarcry:
Sound awesome [MENTION=4608636]bsmitty83[/MENTION] :)

I'd rather have a fantastic kernel that has all/most of the kinks fixed then a fancy installer tbh but that's just me.

but hey if the feedback on your amazing kernels is good and you fancy whipping up a fancy installer I'm sure peeps would be thankful :)

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] bsmitty83:
Should be good I'm running it still with no problems
[Samsung Galaxy Nexus] Kaemo:
I've been hearing about these new WiFi Drivers, and I have no idea what they are and where can I get them. Do you mind explaining?
[Samsung Galaxy Nexus] sd3993:
Once the kernel is absolutely bug free you can start working on the installer then for future versions ;)
[Samsung Galaxy Nexus] rtfpessoa:
You should improve the OP with that kind of info to have less questions in the thread about it.
[Samsung Galaxy Nexus] Nephilim:
Not sure if you ever followed the AK kernel thread back in the day but there were constantly new builds all the time. With all the things that can be refined and modded on kernels there will never be a single perfect version. I had about 5 AK kernels saved on my PC that I just couldn't let go of because I couldn't choose. What I love is that there will almost always be nightlies or bi-nightlies because of little things smitty will see and want to try out. Following a kernel thread is always more fun than following a rom thread because even when you've found the perfect rom you can always be excited about improving its performance through new kernel updates.

Even if smitty is working on another projects along with the kernel, I dont forsee any delay in new kernel releases. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
OP updated . should al be fixed this time , wife is buggin me so i hope i didnt screw up in my haste

thanks guys

enjoy ......
[Samsung Galaxy Nexus] bsmitty83:
probably Lol:good:
[Samsung Galaxy Nexus] KJW979:
Can't DL any, getting file not found