yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] hp13:
i am happy with 51. no issues. is wifi the only major changes?

keep up the great work mate!:good::good::laugh::laugh:
[Samsung Galaxy Nexus] thecoolkid:
Fixed SuperSU issue maybe?

Update:

NOT....
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4615478]boype[/MENTION] great to see you active in here again!

I am going to test pre52 now.

As FSYNC on definitely decreases performance on our GNex is there any chance of implementing another way of syncing? I don't understand much what FSYNC actually does but from its name it does some kind of syncing which is performance hungry. Could this syncing maybe lowered to a minimum or could another method be implemented?

I would like to read much about this because it makes such a difference on my device when FSYNC is off. But I can't use it because even previous installations of apps are vanished after a reboot. And if something happens to the system partition it could happen that the system does not boot anymore.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] thecoolkid:
That's why FSYNC should be always ON. From what I understand FSYNC syncs your data in memory to actual files on flash storage, so when it's off changes are lost after a reboot. Everytime I used DirtyV with dynamic FSync I ended up with a bootloop, and had to restore my data using some black magic ;) So I think FSYNC is here to stay ;)
[Samsung Galaxy Nexus] Ashtrix:
more info on Fsync ;)
[Samsung Galaxy Nexus] Charmacas:
Hmm... so the question is how we can ship around the call block but also write the data in the background!? Is there any possibility to do so?

-- EDIT --

Maybe the following links are helpful:

This is a patch which avoids unneccessary work in fsync. Maybe this could also be done in our kernel? https://git.kernel.org/cgit/linux/k.../?id=e34947056076ca5467ee8256d2d9cbc594a79b37

Fsync on directories seems to be not neccessary. http://oss.sgi.com/archives/xfs/2011-10/msg00002.html http://oss.sgi.com/archives/xfs/2012-08/msg00274.html

Maybe this helps a bit too: http://thunk.org/tytso/blog/2009/03/15/dont-fear-the-fsync/
[Samsung Galaxy Nexus] boype:
/proc/sys/vm/

dirty_background_bytes / dirty_background_ratio,

dirty_bytes / dirty_ratio

dirty_writeback_centisecs

are your friends here. If data was issued to be written to the disk, these limits control when they are actually written to the disk. Before they are written, they are held in memory as "dirty" memory.

Of course, without fsync there's always an increased risk of data loss.
[Samsung Galaxy Nexus] Charmacas:
Yeah this was what I also read in the links I posted/edited above but as for now I don't understand how it can be optimzed. Do you have any idea?

If we could do anything there than I think the kernel would dramatically improve in terms of performance. Especially with F2FS as you said yourself.

-- EDIT --

I think there is no tuning possible. Everything is already set to write directly. Or could this also give hiccups?
[Samsung Galaxy Nexus] RW-1:
I apologize beforehand, I'm having a dense moment (plus some AH's at a domain host that cant get 41 subdomains of mine back working). Should I try pre-52 with Shiny?

Or is that issue with ramdisk (possibly) still being looked at?
[Samsung Galaxy Nexus] spirit1002:
I can't turn on portable WiFi hotspot with pre52 & cm M8 , the wifi auto connect issue seems fixed.

DirtyV seems change power.tuna.so & hostapd to make it work?
[Samsung Galaxy Nexus] thecoolkid:
I'm looking at this thread like every 5 min waiting for the fix xD

Perhaps anykernel version in the meantime? ;)
[Samsung Galaxy Nexus] aliesz:
I tested it and the problem exist already in pre52-1.[emoji20]
[Samsung Galaxy Nexus] boype:
I'll try to make it happen this weekend. Sorry but I definitely cannot make it any sooner
[Samsung Galaxy Nexus] RW-1:
Hi Boype,

No worries, I'm holding on r50, patience is an art form hehehe ....

---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------

Don't break your F5 Finger now ... :eek:

I'm just holding on r50 for now.
[Samsung Galaxy Nexus] thecoolkid:
Don't get me wrong, not asking for ETAs (rule no. 1). Boype, take your time ;) I'm just eager to try it, i tried it for couple of seconds without root, and it feels so smooth! Definite improvement over r45 that I am on now ;) just wish I could try it already :P but oh well... I'll wait ;)
[Samsung Galaxy Nexus] giorgis91:
My phone is hot after some mins of screen on time :/

I'm using v51
[Samsung Galaxy Nexus] Charmacas:
Getting hot is no problem here. Everything works fine with pre52.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] boype:
I think I may have isolated the issue during my lunch break. I cannot make changes and test at work, though. But hopefuly I got it right.
[Samsung Galaxy Nexus] _hz:
No more wifi-reconnecting issues with pre52_1! :) can activate wifi-hotspot without problems on slimkat 6.2 f2fs

.

Had SuperSU issues with slinkat 6.4 f2fs but i think thats actually a known problem... :)

Thanks so far! :)
[Samsung Galaxy Nexus] Ashtrix:
I'm on Slimkat 6.2 no su problems here, try in built super user app under developer options..
[Samsung Galaxy Nexus] _hz:
i don't have issues on 6.2 with supersu, only on 6.4 but i switched back to 6.2 and wait for a fix... ;)
[Samsung Galaxy Nexus] RW-1:
I hear that. Kewl!
[Samsung Galaxy Nexus] thecoolkid:
Yay! ^^ I mean... wow you're fast :P
[Samsung Galaxy Nexus] gauravraw:
Want to download the older versions but http://boypetersen.de/ is down?
[Samsung Galaxy Nexus] poo706:
I presume you also don't have a problem if I include your kernel with my unofficial LiquidSmooth builds? I'd like to start releasing unified ext4/f2fs builds and I didn't have any luck with making the stock LS kernel F2FS compatible by swapping fstabs.

[poo]
[Samsung Galaxy Nexus] Ashtrix:
Yeah it is :(
[Samsung Galaxy Nexus] aliesz:
Yes, for example I have tried franco r396, also the Fancy's old versions (r45 to pre_51 ) . have not this problem.
[Samsung Galaxy Nexus] boype:
I didn't even notice it was down - must have been only for a short period of time. I paid for 99.99% uptime until the beginning of 2015, so that's what the hoster should be delivering :p

Go ahead, go ahead ;)

(Swapping fstabs is not enough, there's over 400 kernel commits + scripts involved in dirtyv/fancy f2fs support)
[Samsung Galaxy Nexus] Ashtrix:
I guess the only downside of F2Fs is when u are backing up in recovery it just gives me speeds of 4-9MB/s :silly:, Maybe due to the un official twrp is causing it, idk :(
[Samsung Galaxy Nexus] poo706:
Thank you, thank you. The thing was that I ported over the unified stuff from LS's grouper build and that kernel handled ext4 vs f2fs by simply swapping fstabs. I'm the in the process of talking to that dev to see what else he may have done. In the mean time, using your kernel is working perfect!

[poo]
[Samsung Galaxy Nexus] Ashtrix:
Unfortunately the pre52 is not stable for me giving me freeze ups , so i had flashed r51 again over pre52 and after a reboot it says one time init stopped, i guess any changes to the ramdisk may cause this issue while rolling back..
[Samsung Galaxy Nexus] demlv:
Pre 52 works perfectly for me. Haven't tried to tether yet, but I have no issues to report.
[Samsung Galaxy Nexus] Osid:
I've a maguro GNex with ShinyROM too.

Those are my findings:

- ShinyROM dirty flashed (no wipe of /data) over stock and Fancy Kernel r51: SuperSU 2.01 working

- ShinyROM clean flash (wipe of /cache, dalvik cache, /system and /data) and Fancy Kernel(s) pre52, r51, r50, r49: NO root. I've tried to install SuperSU 2.01 in recovery as a standalone ZIP.

- ShinyROM clean flash with another kernel (Franko r396 and DirtyV latest): root works.

UPDATE: I was able to obtain root invoking adb root on my PC (and USB debugging on device) and, after that, manually execute adb shell /system/xbin/daemonsu --auto-daemon
[Samsung Galaxy Nexus] boype:
pre52_2 (fix root on shiny)

Hi,

pre52_2 is available from the OP. I hope it fixes root for shiny rom users, but I haven't explicitly tested that.

Also, I've included a few updates to fsync. Haven't really tested or benchmarked anything yet.

Please report.

Have a nice weekend - it's gonna be 35°C again here. Too warm for me :(

[edit]

I've also had some of those freezes. It's the new wifi driver. r52 will come with the previously used (stable) wifi driver, but I'll see if I can do anything against the reconnect problem
[Samsung Galaxy Nexus] Osid:
Flashed pre52_2 in recovery and, after kernel, SuperSU 2.01 update ZIP; rebooted: root works :)
[Samsung Galaxy Nexus] thecoolkid:
It works! And it's so so smooth ;) You're the best!

I have only one issue: Performance Control force closes for me :( haven't had any issues before, trickster works fine though... cleaned dalvik and cache, cleaned app data, revoked su permissions and allowed again... nothing works...

http://xdaforums.com/devdb/project/?id=600#downloads
[Samsung Galaxy Nexus] aliesz:
Are the versions released for 4.4KK android compatible with stock 4.3 jb?
[Samsung Galaxy Nexus] neopbm:
The OP says :

r51: Android 4.4 only (fixed ramdisk for f2fs support). r49 to r50: Android 4.2/4.3/4.4 (anykernel2)

So i think you sould try r50
[Samsung Galaxy Nexus] Ashtrix:
Thankyou [MENTION=4615478]boype[/MENTION]. Have a great weekend man :good: !!

I got freezes after a phone call (screen just went blank ) & while playing a game on PSP emulator & completely idle state and once with wifi on, dunno whether the idle state of newer driver is causing this or could be any conflict.

Flashed pre52-2 alr, will report if any issues come up further..!

edit : i cannot see the toggle for wifi high perf anymore on pre52-2 same as pre52-1, unlike r51 .
[Samsung Galaxy Nexus] boype:
I suppose it's the new driver.

wifi high perf had been removed with the wifi update.
[Samsung Galaxy Nexus] thomstrack:
Flash pre52_2 over r45 (clear dalvik/cache) and SuperSU 2.0.1 and nowroot works with latest ShinyROM.

Thanks [MENTION=4615478]boype[/MENTION] :D

Sent from my Galaxy Nexus 4.4.4 ShinyROM + FrancyKernel
[Samsung Galaxy Nexus] boype:
r52

Hi again,

here's r52:

r51 >> r52

fsync updates from later kernel revisions

defconfig: enable CONFIG_DHD_USE_SCHED_SCAN (hopefully helps with wifi reconnection issue)

add self-compiled stripped busybox with f2fs support

re-add ROM-independent init.d support

execute init.d through busybox's run-parts instead of sysinit (which is not available in every ROM, e.g. shiny; fixes root issues reported by some users)

fix /system mounting to ro with f2fs fstab

increase sched_rt_runtime_us marginally (~1% more realtime cpu usage granted for parent cpuctl group; likely not noticable?!)

dont renice flush-daemon(s), they're already at +20 by default

As usual: take care, have fun :good:
[Samsung Galaxy Nexus] RW-1:
Hi Boype,

All good on R52 with shiny for me as far as root. Awesome!

Will evaluate as I resetup Trickster, but based on others, I believe I'll be ok.

Enjoy your weekend as well! Thanks!
[Samsung Galaxy Nexus] thomstrack:
Flash R52 with latest shiny and latest superSU and all works fine and smoothly. Awesome!

Thanks [MENTION=4615478]boype[/MENTION] for your amazing work :D

Sent from my Galaxy Nexus 4.4.4 ShinyROM + FrancyKernel
[Samsung Galaxy Nexus] motorazrv3:
Going to try out final r52. Pre 52 was the first kernel since long time that was able to reconnect to my router automatically when i reach wlan signal again. Hoping r52 will still do this.

Anyways as always thx for your fantastic work boype.

Update:

Yeah reconnection seams to work on final r52.
[Samsung Galaxy Nexus] andry23jsv:
Hello,

I'm on cataclysm ROM, so still 4.3 but I want to add GNL to whitelist.

Since the latest fancy's version are compatible just for 4.4, how can I do?

Thanks a lot
[Samsung Galaxy Nexus] johansenmo:
Can confirm auto reconnect working for me as well with final r52 (slimrom/f2fs). Thanks & good job!
[Samsung Galaxy Nexus] sergialess:
Hi. I'm sorry to bother you, but I'm wondering where I can find Trickster settings for this great kernel.

Thanks in advance! :good:
[Samsung Galaxy Nexus] boype:
If I understood this correctly, you are not running fancy kernel on your 4.3 ROM. You need to

1) find a kernel that has support for launcher whitelisting

2) edit the RAMdisk to include your launcher for the list / ask the kernel's author to add your launcher to the whitelist.

What do you mean exactly? Like some kickass custom settings that will make the phone fly?

By default, fancy kernel comes with settings that offer a good compromise between fluidity and battery savings.
[Samsung Galaxy Nexus] sergialess:
I agree with you. I was just curious about it. Clarified then.

When idle, consumption is perfect. Performance is great.

Thanks.
[Samsung Galaxy Nexus] andry23jsv:
I'm on fancy kernel. Latest version compatible with 4.3 (r50).
[Samsung Galaxy Nexus] Ashtrix:
[MENTION=4615478]boype[/MENTION] if there is any slight chance how about synapse for future rel ? , I've heard in dirtyv's thread it's free & offers deep kernel side settings but i couldn't test it myself (as dirtyv's non SR causes my phone to get hot always).

Besides that the r52 is perfectly running :good:, thanks !!

Edit : Osmosis does know much about synapse if u are interested :D .
[Samsung Galaxy Nexus] xiaoaxel:
Guy..

I wanna ask for the latest fancy kernel work for 4.3?

Or.. Is it any suggestions for 4.3?

Because I just wanna stay at cataclysm 4.3 it it smooth enough for me ?

Thanks you...
[Samsung Galaxy Nexus] cabalio83:
Check OP

Compatible to:

all Galaxy Nexus devices (maguro, toro, toroplus)

r51 or later: Android 4.4 only (fixed ramdisk for f2fs support). r49 to r50: Android 4.2/4.3/4.4 (anykernel2)
[Samsung Galaxy Nexus] Heidegeist:
A bit strange i guess. I'm on cataclysm 4.3 and fancy r50 and my phone leaves the 1228 MHz state nearly unused :D does anyone know why? I just use the phone for calls, messages, Whatsapp, Threema, FB and so on. No gaming and no lags overall... In earlier fancy releases the state was often used. Standard settings.
[Samsung Galaxy Nexus] Ashtrix:
That might be due to kernel changes in governors, clocksteps coz much of the kernel devs prefer their own custom values to their clock steps, governor values etc.. for their needs ;)
[Samsung Galaxy Nexus] siealex:
It looks like your Trickster sets the max frequency to 1036. Check it in settings.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] xiaoaxel:
I have the same problem and i do check to the setting of frequency setting.. but it look fine as setting to 1200ghz..

the cpu still lock at 1000ghz:confused:
[Samsung Galaxy Nexus] Ashtrix:
Try using freq lock ?
[Samsung Galaxy Nexus] xiaoaxel:
freq lock does lock between max/min frequency..

but i think that will be more drain battery...:rolleyes:
[Samsung Galaxy Nexus] ~SonkuB~:
root fail when install this kernel

ROM : Shiny ROM: Android 4.4.4, KTU84P for Galaxy Nexus (Maguro)

Root : Chainfire's SuperSU Root

If I don't install this kernel root complete. but when I install this kernel root is fail.

when open superSU it show about ROM version 4.3 can't use superSU this version.
[Samsung Galaxy Nexus] Ashtrix:
Just an idea though worth a shot, well it just lockdowns the max and min steps and it works on our phone prob wont take drain, i used to use that sometimes when the clocks wont stick (A month ago, dunno the rom/kernel but my device was running 1.4ghz oc but it will go back to again 1.2GHz and it used to fix that clock at 1.4), basically the governors take this job depending upon the needs & I think it's fine like that from kernel side.
[Samsung Galaxy Nexus] Heidegeist:
Nope max freq 1228 MHz, min freq 192, but min freq screen on 384 und max screen off 537 :P
[Samsung Galaxy Nexus] xiaoaxel:
thnks for it!

learned a lot~:cowboy:
[Samsung Galaxy Nexus] thomstrack:
You flash the latest release SuperSU (2.01) again after flash Kernel Fancy?)

I use the same ROM and you had no problem with the latest version of FancyKernel. ;)
[Samsung Galaxy Nexus] RW-1:
No issues with Shiny on r52 after we reported root loss to Boype, however I'm on Toro, not Maguro, but would not see why that might factor in.
[Samsung Galaxy Nexus] boype:
r53 (+experimental anykernel for Android 4.2 & 4.3 ROMs)

Hi all,

here's r53. For those who want(ed) to install Fancy Kernel on 4.3 ROMs, you should now be able to do that with the anykernel version. I'm clearly saying you should be able to, since I did not test it! For the time being, I'll not put the anykernel version to the OP until I hear it is working fine.

Of course, there's also a version with a fixed RAMdisk of r53 (available from the OP), like we used to have in r52 and r51. That said, I advise all f2fs users to use the fixed RAMdisk version from the OP, because your f2fs ROM will most likely come with a custom kernel that has a non-pure RAMdisk. Applying anykernel to such RAMdisks will cause nothing but problems. You have been warned :)

Anyway, here's the change log:

r52 >> r53

mm: add ultra kernel samepage merging (UKSM) and enable it by default (will save you some 10-30 mb RAM; UKSM is more CPU efficient and has more tuning options than KSM)

move uksm daemon to background tasks (so that timer_slack applies)

disable android ram console (2 mb more RAM)

sioplus: relax sync_read_expire, tighten sync_write_expire

ARM: 7493/1: use generic unaligned.h

OMAP4: do not force (some) workarounds for errata fixed in 4460

mmcblk0: set add_random 0

adjust f2fs ram threshold (/data should get some more than the way smaller /system and /cache)

Download for experimental anykernel2 that should work with Android 4.2/4.3/4.4:

[edit] there have been reports about hangs at the bootlogo with the experimental anykernel2 version. the Android 4.4 only version from the OP works fine, however!

Mirror #1: boypetersen.de

Mirror #2: mediafire.com

Best regards, take care, have fun.
[Samsung Galaxy Nexus] Ashtrix:
Just wanted to clear things up about the kernels...

r52 and r51, since they are also anykernel2 like the new f2fs r53 from the above post, can we flash any other custom kernel over them w/o any issues (sorry, didn't knew that they are not anykernel..).... ?

& thanks for the update :)
[Samsung Galaxy Nexus] boype:
R51 and r52 were not anykernel, they had a fixed ramdisk. Therefore they could be flashed on top of all kernels, since the previously installed ramdisk does not matter (it is replaced).

the above posted experimental r53 with anykernel2 should not be flashed on top of any custom kernels. Files from the previously installed ramdisk are inherited by anykernel and you will have mixed ramdisk with wrong settings and unnecessary files afterwards. This might even hinder the proper functioning.

Now, since all f2fs kernels are custom kernels until now, you should never flash anykernel2 on top of such a kernel.

Hope that clears the confusion
[Samsung Galaxy Nexus] ahmadairfan:
Testing r53 experimental on cataclysm, booting as I type. Flashed over r50. Will report back :)

Thanks boype!

Edit:

Somehow I stuck at boot animation.. :/

Flashed stock 3.0.72 kernel and r53 again, still same result.
[Samsung Galaxy Nexus] Ashtrix:
That was well put, thanks a ton :good:.

It would be great if there's a chance/possibilty to have the final r53 be flexible (anykernel), coz some users might miss the point and could end up unusual state with the kernel/phone.

And if i wipe the /system i'm good to flash with another kernel or a rom packed with other kernels right ?? (Though fancy is perfect for me, just in any case. Sorry for being a noob with the anykernel2 stuff)

Thanks again boype for your precious time...:)
[Samsung Galaxy Nexus] gautam_nexus:
can i flash it over r52 ?
[Samsung Galaxy Nexus] Ashtrix:
yes, i'm already running it.

edit : I believe it's faster than r52 :D
[Samsung Galaxy Nexus] hp13:
r53 is alot snappier than previous versions. great job! i am not sure if its a placebo effect but i do feel it. clean flash and didn't restore any apps yet.
[Samsung Galaxy Nexus] zoomy942:
15 was silky smooth at all times. I've noticed ui choppiness with 16

---------- Post added at 02:26 AM ---------- Previous post was at 02:22 AM ----------

I'm looking for an r15 link
[Samsung Galaxy Nexus] rob151515:
Just change the 16's to 15's in the latest link. Unfortunately for me, the flickering with recents is happening with 15 as well.
[Samsung Galaxy Nexus] zoomy942:
Thank you!

And just like that it's smooth again r16

---------- Post added at 03:11 AM ---------- Previous post was at 02:42 AM ----------

Changing it to 15 didn't work
[Samsung Galaxy Nexus] nowetdio:
Can someone confirm with r16. Drain the battery all the way until the phone turns off, plug it in, then turn it on. I get into a bootloop. Thx
[Samsung Galaxy Nexus] boype:
Regarding the flickering: anarkia has pointed me to the commit responsible for that. Will fix this soon.
[Samsung Galaxy Nexus] RevengeFNF:
Everytime i flash a new version, my kernel settings go to the defaults.

Is this issue Kernel or Trickster app related?
[Samsung Galaxy Nexus] boype:
Must be Trickster IMO.
[Samsung Galaxy Nexus] gwindlord:
Indeed, it always drops settings, when kernel is changed (sometimes even to random, not to default).
[Samsung Galaxy Nexus] Rufufu:
I think it is for preventing some bootloops, in case of unstable settings with the new kernel.
[Samsung Galaxy Nexus] bolanrox:
it is Trixster this will happen any time you flash a new kernel.

---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------

do you have the bootloop prevention setting enabled?
[Samsung Galaxy Nexus] gwindlord:
No, it's disabled (I guess as a result of such options drop, because I've enabled it some time ago :D )
[Samsung Galaxy Nexus] bigknowz:
New kernel settings

You need to get into init.d scripts if you want your settings to stick across kernel flashes. Lots of good stuff on the subject in the franco thread if you want to read up on it.
[Samsung Galaxy Nexus] bolanrox:
maybe something happened with one of the updates last week to trixter? usually (and I mean every other time i flashed a kernel since i got trixster) the boot loop prevention has stayed checked. When I looked today it was unchecked. I have to guess it was the last update.

I will take a look at my n7 when i get home and see if that is unchecked now as well.
[Samsung Galaxy Nexus] zoomy942:
I'll look fire an r15 today. Unless someone can post it?
[Samsung Galaxy Nexus] FTW_260:
Upgrade from r12 now... Everything works fine, as always. Thanks, Boype! :fingers-crossed:
[Samsung Galaxy Nexus] Syfer_Fever:
currently using your kernel r16 for a couple of hours, running great so far. smooth and good deep sleep. thanks boype! keep up the good work!
[Samsung Galaxy Nexus] zoomy942:
Any plans to make older versions available?
[Samsung Galaxy Nexus] guitmz:
Do not fear. Old version (r15 ext) is here.

https://skydrive.live.com/redir?resid=28E197456E1529A1!365&authkey=!AHhtofMv3oO3u70
[Samsung Galaxy Nexus] boype:
Just take the link from the OP: http://boypetersen.de/fancykernel/r16/std/fancy_kernel-tuna-4.2-r16-std.zip and replace the both "r16" with rXX.

I've tried to find the directory listing option in the webspace settings, but interestingly I could not find it. Will try again :D

[EDIT] found it and activated it. Check out http://boypetersen.de/fancykernel/
[Samsung Galaxy Nexus] kevdliu:
Hey boype,

Someone over at the AK thread posted a commit which allows global CPU hot plug out on screen off. I'm on mobile now but I'll update with link as soon as I can. Since you are on a roll with battery saving changes, would that be helpful?
[Samsung Galaxy Nexus] RW-1:
Ok ok ok, slap me, but ok ... which one should I flash on top of R52 for shiny (toro)? [head spinning]

Boype, you're terrific, I mean that.
[Samsung Galaxy Nexus] aliesz:
I installed r53 over leankernel v83 and my ROM is rooted stock 4.3 . the same problem is there here. It stops on animation boot I waited for 6 minutes..!
[Samsung Galaxy Nexus] boype:
Could somebody grab a few lines from adb logcat while the phone hangs? That would be very helpful.
[Samsung Galaxy Nexus] cujo6801:
No problems with smittyV 7/17 and DU ROM... :D:p

Sent from the "DOG" pound