Database Users

Kernel for jw1

can semaphore jvz kernel be used for jw1 roms?
Sent from my GT-I9000 using XDA App

Yes, I just tried it and it works fine.

apparantly jw1 and jvz are almost identical (only diff is in lang files or something), so jvz kernel is fine.

i think that progress in changelog number is too great for the only changes to be were the language typos fixes
using custom kernel is bad
using custom kernel from previous version to some more recent is bad

but if you want various tweaks and overclocking there's no other possibility then using a custom kernel that supports it or am wrong?
greetz

well yes but take a second and think about it
kernel sources those guys use are half year old and are for 2.3.3 kernel version
currently used kernel by samsung in jw1 is 2.3.6 that sources are unreleased

$omator said:
well yes but take a second and think about it
kernel sources those guys use are half year old and are for 2.3.3 kernel version
currently used kernel by samsung in jw1 is 2.3.6 that sources are unreleased
Click to expand...
Click to collapse
Now i see. That's why i used to be so satisfied with my stock jvq rom and latest semaphore kernel. Now im on jvz and cant see any improvement. \/

i can tell that jw1 and jvx/jvz stock versions
are faster then jvt and eariler ones (2.3.5) - more responisive
tings like zergrush exploit gets patched
but it is still your fair choice to pick custom kernel
and overclock/ondervolt or do whatever you like with it
i am pissed a bit that those guys are not informing in op post
"builded from latest smsung source" is not saying that this source have half year
but i will not start another rant to get banned by some moderator for trollingas usuaal ;]

$omator said:
i think that progress in changelog number is too great for the only changes to be were the language typos fixes
using custom kernel is bad
using custom kernel from previous version to some more recent is bad
Click to expand...
Click to collapse
Not true. Were there any bugs that were not present in the stock kernel that is present in a custom kernel? None so far.
Samsung is obligated to release the latest source code for its kernel. If a compiled kernel doesn't boot or the kernel can't work with the binaries that are released, Samsung is liable to being sued for not being GPL compliant. So far they've been pretty quick in releasing sources (from the past year) with the delta being less than a 2 weeks after a release.
Also, if you spot any differences of stock with a custom kernel, you should report it to Samsung so that they release the latest source code. So far I have not detected any bugs stemming from using a compiled kernel from the source that's been released more than 3 months ago.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GB_Update2 you see is not even a full source - released in August

$omator said:
GB_Update2 you see is not even a full source - released in August
Click to expand...
Click to collapse
This is because Samsung expects you to use the pre-compiled modules for Wifi and a few others (from what I read from the source code).

still where is the latest source for jw1 or jvt ? any updated source i missed ?

$omator said:
still where is the latest source for jw1 or jvt ? any updated source i missed ?
Click to expand...
Click to collapse
No changes for them. Even their initramfs didn't change except for the magic number for the pre-compiled modules.

no changes since august in sources ? are you serious mate ))))

$omator said:
no changes since august in sources ? are you serious mate ))))
Click to expand...
Click to collapse
Yup
Decompile the initramfs and see for yourself
As for the kernel binaries themselves, it's harder to detect. However, no loss of functionality has been reported from custom kernel usage. I'm about 95% sure that no source change occurred.
Platform though, is another matter. The platform changed quite a bit, though all of it are closed sources ones (like Touchwiz).

;] 10 lulz!!

$omator said:
;] 10 lulz!!
Click to expand...
Click to collapse
If there is I didn't notice it. And gingerbread gpu drivers sucks.
Sent from my GT-I9000 using Tapatalk

About gpl and Samsungs obligation to release sources for kernel:
JW1 is not released for public use, is it?
This is a LEAK and should be treated likewise - WYSIWYG
Tapatalked - There's a Thanks button somewhere

shush! they mixup 10 zImage's and it is working

$omator said:
i think that progress in changelog number is too great for the only changes to be were the language typos fixes
using custom kernel is bad
using custom kernel from previous version to some more recent is bad
Click to expand...
Click to collapse
I respect that you hate custom kernels but telling people that 'using custom kernel is bad'...is bad.
Can you please post your arguments?
With your logic XDA should not exist. With your logic nobody should tweak or change the standard products that Samsung delivers. Nobody should experiment. Nobody should try experimental features/tweaks/mods.
Or maybe, nobody except you?

[Q] kernel for ICS

Hey,
I've read various topics on the forum, but they seem to confuse me as they say different things:
when ICS was released, some people said we needed a newer kernel for our nook in order to run ICS. but now, we have a pre-alpha build which runs on the old kernel. There are various other devices which have ICS builds on a 2.6.32.x kernel, so why did some people say that we needed a newer kernel?
Are Dal and fattire building ics ontop of a gingerbread kernel?
And which kernel is the "default" for ics? a 3.0 kernel?
i'd appreciate some answers to enlighten me

Take a look here, from the dev thread, kernel is 2.6.32.9.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Homer

Homer_S_xda said:
Take a look here, from the dev thread, kernel is 2.6.32.9.
Homer
Click to expand...
Click to collapse
Yeah, i know we are on that kernel, but my question is: how is this possible? Are they porting ICS to a froyo kernel?
The HD2 uses a froyo kernel too, for it's ICS builds.
But why were people saying when the ics source code was just released that we need a newer kernel before ICS could be ported to our nook?

I think you might be confused between NT and NC.
AFAIK, NT does need newer kernel (as set of drivers since it has new hardware) while NC doesn't require to. I might be wrong though.

It's my understanding that the NC (not sure about the NT) doesn't actually need the new kernel to run, but it would make things a hell of a lot easier. Mainly, the problem seems to be getting outdated hardware drivers working with the newer parts of ICS--thus the lack of sound and video, among others--and that 2.6.35 has code and/or links to drivers that would help. But until B&N updates to that kernel (unlikely for now)m anyone working on CM9 has to deal with the old code and thus has an uphill battle.
IIRC, at first the CM9 team said it might never come to the NC, so I feel like we're kinda lucky. And if you read the first post of the DEV thread, you'll see that they're still iffy (and that's being generous) on a final, working, daily-driver version ever being released.

A lot of misleading info here , I'll try to make it simple and understandable
First , NT has a locked bootloader - it doesn't have anything to do with ICS or kernel ver.
ICS doesn't NEED 3.0 kernel to run ( proven on many devices ) , BUT there are some compatibility issues that needs fixing/back-porting/revere-engineering
and there are some things that can't be exactly ported ( or it's pretty hard and not worthy to reverse engineer ) , such as closed-source drivers
The main issues most devices encounter are GPU & Camera
Since we don't have a cam , the GPU drivers are the main thing to worry about
As dalingrin explained some time ago , there are closed-source libs that we need updated from the manufacturer to support ICS - It seems some can be found compatible with newer kernel versions ( 2.6.35 ) , but again it doesn't promise full support till an official ICS version for a similar spec device comes out
As I see it , a 2.6.35/37/38 or even better 3.0 ( as some devices starting to concentrate on now to get full gpu support & camera working instead of back-porting closed source drivers ) eventually will be necessary , because all we do now is relying on legacy support / hacks
I'm hoping for a community port of 3.0 kernel once ICS port will reach its full potential using 2.6.32 kernel ( now that fat-tire has caused many people to learn how to build , maybe we will see more progress soon )

[REVIEW] Kernels Review using Benchmark

This test was done using Antutu Benchmark.
I did 3 tests using the Chainfire driver, but using a OC Kernel, the diference is pratically null. In pratice, using Chainfire driver the results is worse, in all kernels tested.
The firts test i use MIRACLE ROM V3 and after using CM7.2 cooper signed, but the results don't was expressive differents. This results are the mean of 3 test each kernel.
All the tests was done using the same device and the same sd card installing only new kernel code. Some results may be worng, sorry for that...
My next test will be of the battery drop. I'm not a judge, this is only for comparate and analyse for your future update in some kernel based these kernels for you enjoy the best of each.
Original kernel is the results of the Original kernel in CM7.2 cooper signed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=1296905
http://forum.xda-developers.com/showthread.php?t=1606352
ps.: This kernel reboot the devide twice during test.
http://forum.xda-developers.com/showthread.php?t=1634604

Did you know that our Ace natively runs at 787MHz? Not 806MHz!
Sent from my GT-S5830 using Tapatalk 2

KcLKcL said:
Did you know that our Ace natively runs at 787MHz? Not 806MHz!
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
This happens with OC kernel? Because it has two frequencies, 806 and 787.

Thanks for this interesting info!
The biggest differences are SD read/write performance (original kernel very slow) -- however note this does not affect database I/O at all!!! Is there some cache at play here?

With the default 800MHz value in stock kernel, It is actually 787MHz
There was a post describing how kernels calculate a thing called PLU and such which makes it's actually 787
Sent from my GT-S5830 using Tapatalk 2

iandol said:
Thanks for this interesting info!
The biggest differences are SD read/write performance (original kernel very slow) -- however note this does not affect database I/O at all!!! Is there some cache at play here?
Click to expand...
Click to collapse
I could be wrong, but..
DATABASE I/O - This is the speed of input and output signals (Processor and ROM) and not the speed of acess files and folders in sd card. The test in sd card varies, so i include the line with Exclude SD Results.

Good work. You actually bothered to contribute to the community! Even though some may say benchmarks are useless, its still a widely used tool. And there is no better way to test

thedisturbedone said:
Good work. You actually bothered to contribute to the community! Even though some may say benchmarks are useless, its still a widely used tool. And there is no better way to test
Click to expand...
Click to collapse
Tks friends. I fell very happy. New work in progress... I'll do more tests to post with here. Thanks.

wizarcl said:
Tks friends. I fell very happy. New work in progress... I'll do more tests to post with here. Thanks.
Click to expand...
Click to collapse
You're welcome. That would be great.

Great!

Thks friends.

I had assumed database I/O was combined file read/write along with CPU etc. -- sqlite uses filesystem based files so it should also be testing file access, but again this may be cached and therefore that is the difference to the read/write benchmarks? The Antutu website gives no technical description of what their tests do — very disappointing...

so ketut's kernel is better? i was going to try skynet28`s modificated by gorolegov in vo-1 (24.4.12)
should i change it or i keep with ketut's kernel?

doper22 said:
so ketut's kernel is better? i was going to try skynet28`s modificated by gorolegov in vo-1 (24.4.12)
should i change it or i keep with ketut's kernel?
Click to expand...
Click to collapse
I'm not judging any of these kernels, but for me, Blackhawk was more stable and showed a great performance. You can download them and draw their conclusions. Both improve the performance of the device! They're great work!

iandol said:
I had assumed database I/O was combined file read/write along with CPU etc. -- sqlite uses filesystem based files so it should also be testing file access, but again this may be cached and therefore that is the difference to the read/write benchmarks? The Antutu website gives no technical description of what their tests do — very disappointing...
Click to expand...
Click to collapse
I think so. It makes no sense to me he do a test database I / O, and then read and write to SD card, if the test I / O is being tested on the SD card.

Hi dude,can u test this kernel http://forum.xda-developers.com/showthread.php?t=1658911, on miracle rom?

[Q] Building AOSP (ROM + Kernel) for Nexus 10?

I'm pretty interesting in trying to build from AOSP, but just had some questions:
1. What branch would I choose? I seem to have a choice between android-4.1.2_r1 or master
2. What's the difference between those 2 branches? If I think I understand right, the 4.1.2_r1 branch is locked at what it is now, and won't receive regular updates (future updates coming from higher revisions, such as r2 or etc.), and master is updated with whatever patches are submitted?
3. Should building the ROM and Kernel be separate processes?
4. I was reading around here, and didn't really notice any entries for Nexus 10/manta. On the part about building for devices, should I just use "full_manta-userdebug" ?
5. Are the drivers listed for manta at https://developers.google.com/android/nexus/drivers#manta the only drivers I need? I don't need any special driver for DRM like the Nexus 7 seems to need?
6. Would trying to build with linaro be a good idea? More specifically, would it be compatible, and would it yield any performance benefits? I thought I read that some linaro patches were brought over to AOSP a while back, but I also noticed some people still building with linaro and reporting speed increases.

building a kernel with Linaro does not yield any tangible performance benefits, despite what some want to believe. I dont know about real benefits on the ROM side, I seem to remember seeing Linaro can help there but I dont have the benchmarks on hand to show proof or not.
Kernel proof:
non linaro:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
linaro:
Neocore:
Stock: 55.4 fps
Linaro: 55.6 fps (within margin of error, need at LEAST 1 full fps difference in many subsequent tests to prove one is faster than the other)
Quadrant:
Stock:
Score: 1368 (higher is better)
Linaro:
Score: 1320 (again within margin of error, and Quadrant is terrible in consistency anyway)
Linpack:
Stock:
MFLOPS: 15.671
Time: 10.76
Norm Res: 3.24
Linaro:
MFLOPS: 14.235
Time: 11.85 s
Norm Res: 3.24
and another thread by a good kernel dev:
http://forum.xda-developers.com/showthread.php?t=1371044&highlight=kernel+with+linaro

Cool, thanks for the info
I'll probably try downloading the source tonight; should take a good while though since my internet is pretty slow. I setup Ubuntu 10.04.4 x64 in a virtual machine and have it updating currently
Edit: Doing repo sync now. How much should I expect to be downloaded exactly, just so I have an idea on about how long to wait?

espionage724 said:
Cool, thanks for the info
I'll probably try downloading the source tonight; should take a good while though since my internet is pretty slow. I setup Ubuntu 10.04.4 x64 in a virtual machine and have it updating currently
Edit: Doing repo sync now. How much should I expect to be downloaded exactly, just so I have an idea on about how long to wait?
Click to expand...
Click to collapse
It's in the low to mid gigabyte range. Too took me about an hour and a half with 50mbs fiber
Sent from my Nexus 10 using Tapatalk 2

98ramair said:
It's in the low to mid gigabyte range. Too took me about an hour and a half with 50mbs fiber
Click to expand...
Click to collapse
Hmm, if it's like 7GB, I should have it overnight (max DL speed is 360kb/s... lol).

It downloaded overnight
I'm building it currently, not entirely sure how long that'll take though (4GB RAM + 4GB Swap + 3.3GHz X4 CPU on VMWare + -j4). I have CCache enabled too with 50GB.
Ran into 1 issue earlier where the repo sync ended because of gc error (can't recall exact error). Re-ran the sync with -j1 and it worked though (found that solution from search). I guess if I update my repo command, that'll fix it though.

And the build is done, took around a hour:
Some additional questions now:
- Should the Kernel date be that old?
- Do I have the latest Kernel belonging to the branch I chose?
- If I chose to build from master, would the Kernel be more up-to-date?

Not sure on the answer to those questions, but my guess would be the November 6th date is when the kernel repository was last updated rather than the build date
I think its great that you are getting into kernel developing. This device has a pretty poor dev community right now and we really need some more people.

Mind me asking, did you just run the flash command from the build, or did you extract the file and zip it for CWM?
I can't find the out file to flash manually either though :/

@espionage724 to answer your questions....
- Should the Kernel date be that old?
Yes, if you are building from AOSP it uses a prebuilt kernel (device/samsung/manta/kernel). You need to download the exynos kernel source separately (or use my source which has some changes over AOSP)...
- Do I have the latest Kernel belonging to the branch I chose?
Yes, unless you decide to build your own...
- If I chose to build from master, would the Kernel be more up-to-date?
Not always... and most often no...
---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------
Evostance said:
Mind me asking, did you just run the flash command from the build, or did you extract the file and zip it for CWM?
I can't find the out file to flash manually either though :/
Click to expand...
Click to collapse
Run "make -j16 otapackage" to create an update zip...

I've built and flashed a 4.2 aosp ROM (tried both master and r1), but noticed that I'm missing email.apk...anyone else seeing the same thing??

Turbo4V said:
I've built and flashed a 4.2 aosp ROM (tried both master and r1), but noticed that I'm missing email.apk...anyone else seeing the same thing??
Click to expand...
Click to collapse
Apparently a typo is AOSP... go to build/target/product/generic_no_telephony.mk and change Email2 to Email... you could manually build Email as well... mmm packages/apps/Email

craigacgomez said:
Apparently a type is AOSP... go to build/target/product/generic_no_telephony.mk and change Email2 to Email... you could manually build Email as well... mmm packages/apps/Email
Click to expand...
Click to collapse
Thanks Craig, I'll go and try building email manually!

espionage724 said:
I'm pretty interesting in trying to build from AOSP, but just had some questions:
1. What branch would I choose? I seem to have a choice between android-4.1.2_r1 or master
2. What's the difference between those 2 branches? If I think I understand right, the 4.1.2_r1 branch is locked at what it is now, and won't receive regular updates (future updates coming from higher revisions, such as r2 or etc.), and master is updated with whatever patches are submitted?
3. Should building the ROM and Kernel be separate processes?
4. I was reading around here, and didn't really notice any entries for Nexus 10/manta. On the part about building for devices, should I just use "full_manta-userdebug" ?
5. Are the drivers listed for manta at https://developers.google.com/android/nexus/drivers#manta the only drivers I need? I don't need any special driver for DRM like the Nexus 7 seems to need?
6. Would trying to build with linaro be a good idea? More specifically, would it be compatible, and would it yield any performance benefits? I thought I read that some linaro patches were brought over to AOSP a while back, but I also noticed some people still building with linaro and reporting speed increases.
Click to expand...
Click to collapse
Can you document your build process, with a compile script?
I want to fix some HDMI issues on my Nexus 10 and read the docs, but found myself stuck with what to do for manta?

Hello,
I am trying tot build Aosp for N10 but I cant select Manta when i do the lunch command. It simply doesnt show up. I can see grouper etc.
I did repo sync masterbranch.

ThugLife™ Kernel

Hello Everyone!
I've been working on my thuglife™ kernel for bullhead for a while, have included it in some ROMs, have released it yet
I'm planning to release it soon, and hence want to know how it is, and if you'll have some requests for it, etc
https://sourceforge.net/projects/thuglife/files/bullhead
There are a lotta zips there, been uploading quite a few of my builds
Latest one I'm currently running has been updated of Linux kernel version 3.10.99, and compiled with Ubertc 5.3
https://sourceforge.net/projects/thuglife/files/bullhead/thuglife-bullhead-20160305.zip
Kernel source --> https://github.com/akhilnarang/ThugLife_bullhead
I'm not really a kernel developer, just like having my own though, with all the features I like and want, all credit goes to various developers who actually wrote everything that's in the kernel
Enjoy
Sent from my Nexus 5X using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PS. - Huge thanks to @TJSteveMX for testing some builds and helping me debug stuff by providing logs

yeah, been running this kernel for a month now i guess.... good work tho
sharing the love is a great step for developing. good good...

Great! Hope to see your work on sprout.

akhilnarang said:
Hello Everyone!
I've been working on my thuglife™ kernel for bullhead for a while, have included it in some ROMs, have released it yet
I'm planning to release it soon, and hence want to know how it is, and if you'll have some requests for it, etc
https://sourceforge.net/projects/thuglife/files/bullhead
There are a lotta zips there, been uploading quite a few of my builds
Latest one I'm currently running has been updated of Linux kernel version 3.10.99, and compiled with Ubertc 5.3
https://sourceforge.net/projects/thuglife/files/bullhead/thuglife-bullhead-20160305.zip
Kernel source --> https://github.com/akhilnarang/ThugLife_bullhead
I'm not really a kernel developer, just like having my own though, with all the features I like and want, all credit goes to various developers who actually wrote everything that's in the kernel
Enjoy
Sent from my Nexus 5X using Tapatalk
PS. - Huge thanks to @TJSteveMX for testing some builds and helping me debug stuff by providing logs
Click to expand...
Click to collapse
Great new stuff for the 5X users,
off topic question but where did you get your navigation bar icons from?

Great kernel. Thank you

First of all, thank you for sharing your work! I flashed this just a few minutes ago, no immediate problems so far. I liked the fact that it's optimized with Uber and is based off the latest Linux version. I did run into one problem, however. I cannot select Zen as my I/O scheduler. I appears on the list in ElementalX Kernel Manager, but selecting it does nothing. I switched to SIO Plus for now, but this issue did not occur in Phasma Kernel which also has the Zen scheduler.

Alcolawl said:
First of all, thank you for sharing your work! I flashed this just a few minutes ago, no immediate problems so far. I liked the fact that it's optimized with Uber and is based off the latest Linux version. I did run into one problem, however. I cannot select Zen as my I/O scheduler. I appears on the list in ElementalX Kernel Manager, but selecting it does nothing. I switched to SIO Plus for now, but this issue did not occur in Phasma Kernel which also has the Zen scheduler.
Click to expand...
Click to collapse
Will check it out, thanks for the feedback
@JustPlayingHard : please don't quote full OP
The navbar is from iLayers theme

http://blazingphoenix.in/akhilnarang/ThugLife/bullhead/thuglife-bullhead-20160320.zip
Here's a new build, kernel is updated to 3.10.101, and March kernel updates included
Please test and let me know how it is

akhilnarang said:
http://blazingphoenix.in/akhilnarang/ThugLife/bullhead/thuglife-bullhead-20160320.zip
Here's a new build, kernel is updated to 3.10.101, and March kernel updates included
Please test and let me know how it is
Click to expand...
Click to collapse
Any info for the new build dated for August 13th?

https://github.com/akhilnarang/ThugLife-Misc has a changelog for builds
Sent from my Nexus 5X using Tapatalk

akhilnarang said:
https://github.com/ThugLife-Misc has a changelog for builds
Click to expand...
Click to collapse
Link ends in 404

TW1ST3D1NS4N3 said:
Link ends in 404
Click to expand...
Click to collapse
Fixed link
Sent from my Nexus 5X using Tapatalk

akhilnarang said:
Fixed link
Click to expand...
Click to collapse
Could there be a problem on my end somehow? Still getting same issue.

https://github.com/akhilnarang/ThugLife-Misc?files=1

Any future plans?