yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Ah I'll fix it I'll fix it! My friend is coming over to play some Mario Kart, but he wants me to show him a day in the life of Quantum Dev really quickly! I have all the bugfixes lined up thanks to you two, so look for it very very very soon! So Mario Kart, Quantum, and burritos! :victory::victory:

ROM is still lagging a bit behind.... just mostly from lack of time to give it my full attention/waiting for things to commit.

Have a great Monday night everyone :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Thanks, pwn. Have fun with Mario Kart. Is it the new one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pilothaz:
Enjoy the time... Make it some Beerio Kart!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
4.4.3 is live on aosp, can't wait for some 4.4.3 quantum goodness:victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xsever:
I got a reboot on 6/1 as i was using whatsapp where upon finishing the reboot, a bunch of apps booted on their own, Nova undefaulted itself, and my ringtones were back to default too.

As if all settings were lost. Will try to get a log next time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
http://d-h.st/mZ6
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
TWRP wouldn't flash your kernel either on RR, nor would Philz. But Since I was back on Philz I flashed it on Carbon 6/2 and works well. I did get one random reboot though. Nothing since. [emoji106]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] some_shyguy:
Am I the only one having issues with my display not showing anything after flashing the new kernels?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Trying to remember, is Intelliactive or Intellidemand the gov that's well balanced?

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I had that issue, but it's been fixed. You're the only one.

Intelliactive!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryanstfl:
Was it fixed in the 6-3 version? I tried it on my d2vzw and it still had the same result as the previous versions. On a side note, I'd be willing to test out versions you have posted to your dev host. My phone legit feels incomplete without your kernel, especially because of the sound enhancement via Faux. :\
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
He was the only person who has had that issue so far. I will only upload builds of kernels that I have at least tried myself. There's tons of kernels out there! You don't have to run stock linux if you don't want
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
[MENTION=1683096]PwnCakes193[/MENTION]

Just had two reboots in a row on D2VZW w/ C-Rom 6.4 and the Quantum 6/3 kernel running Intellicactive and BFQ.

First reboot happened when using GoLauncher 5 and opening a folder. The next happened as soon as the device booted from the first reboot.

I'm not sure what you need, but I managed to pull a logcat, dmesg and last_kmsg.

Hope that helps!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryanstfl:
There's not many kernels that stay as up-to-date as yours and include features and governors that keep my phone running long
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Looks like data flush corruption. Turn off DYNAMIC FSYNC until these reboots are resolved.

That thing is pretty dangerous, but useful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
6/3 is working well, very smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unit68:
After flashing 6/3 I've noticed the default for mobile network has changed to 3g/wcdma and I have to change it to 3g/wcdma/LTE in order for LTE

This happened on last kernal as well

Running quantum 4.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksd316:
On newest slim weekly, 6/3 nothing but boot screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnXKnown0:
Whether or not Im disliked on this thread, the new toolchain IS NOT causing reboots. I have been running dkp (4.10) and deathly kernel (4.10) for days switching back and forth every couple days and not a single reboot. The reboots are only coming from quantum kernel, nothing else. That's the way its been for a month or 2. Figured I'd throw my 2 ¢.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Input is valid, no matter what. I personally do not run Quantum kernel anymore because of said reboots which do not occur on other kernels but I don't mind helping either way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnXKnown0:
I may have came off as standoff-ish before and my apologies to pwn, but that aside, he should have taken the links down for the broken kernel builds, new users are probably flashing these builds not realizing its actually the kernels fault unless they read through some 100's of pages for info. Just my opinion.

Pwn I think its time to start the kernel over from scratch, ground up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I already did start it over from the ground up... A few days ago. I actually do it all the time. It got rid of the one nasty reboot we've been getting that was universal for everyone.

Good to hear about the toolchain, I won't even have to try it out now. I'm not gonna take links down... Still only a smaller percentage of people are having the reboots, there are a lot of users who have still not experienced a single one since the redo.

In the quest to not come off a little devious, you made yourself seem mean again. I thought it was the toolchain causing errors but I still haven't tested. I never said it wasn't the kernel, in fact if you actually read through the other pages you'll see that firsthand... And the fact that I'm way ahead of you in terms of trying to get rid of reboots out of this kernel. Like I said, why pull down links if every log cat and issue people face actually help towards the development of the kernel? Reporting back is what makes it so that we can make the kernel better!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Send me a PM or something and I'll try to send you a kernel with the necessary commit. Is anyone else having issues with new slim? Or any new ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnXKnown0:
Oh didn't realize you did start over. I haven't been on xda for some time so I haven't read much that's why I said what I said. No hate towards you? I wasn't trying to be mean. I hate text over voice you can't tell the tone or gesture of the other person. Sorry if you took it the wrong way. No hate intended.

But that sucks man, well I hope you can figure out whatever is going on, I know it would bug the sh!t out of me sifting through everything over and over and over hoping to find something that could of gone wrong.

Hey we all make mistakes.

(Let's show a little mercy for Percy)

LoL love black knight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kwmike:
I had the same problem with the latest Omni (6/2) with QK 6/1. Have now loaded QK 6/3 with older Omni( 5/13) with no problem. Will load latest Omni nightly when time permits.

Thanks for all the hard work. Greatly appreciated!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] involuntaryqool:
Reboot on 6/3 kernel..browsing the play store. Here's a log: https://www.dropbox.com/sh/7tnrl1uj3zq6pps/AAAylWdPhtoXDj599C9GuZbWa
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peach007:
Same here. Newest slim weekly won't go past boot with 6/3 kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I actually had that issue with Carbon 6/02 and the Quantum kernel from 6/02. It wouldn't go past the Gimme Pwncakes screen, but it would still act like it booted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Check the main folder on my dev host. I uploaded an old test build that should work. ONLY FOR NEW ROMS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
Same here on Carbon 6/2 & 6/3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryanstfl:
I don't see it but same boot issue with CM11 6-3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bonnatron:
Restart log using maps for navigation https://www.dropbox.com/s/t4wnv16sds5av6m/bugreport-2014-06-03-12-49-47.txt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksd316:
We have boot! Many thanks!

AT&T Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Ok seeing as how we need a new build I'm gonna stop getting the sun outside and I'm gonna bust this ROM out and finish it up today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Effing right! Thank you bruh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unit68:
Just had a random reboot while trying to search on google . after it rebooted supersu asked for permission for trickster mod which I found odd but then typing this I realised both chrome and trickster were updates today without a restart so maybe that caused the issue?

Either way...how the heck do I get the appropriate logs for you guys? Any of the log getting programs I try they just sit there blank.....

I'd like to help by providing logs when ever I can
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Try Syslog by Scott Warner.

Its on play store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lectron8:
can we just use the bug report that comes with the rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
I don't know if this even matter... but every time the phone does reboot, my Swiftkey always goes back to where you have to set it up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
+1 for Syslog! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
Agreed, but tell me, what is the most useful posting, the entire zip, or is there an easier way?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bonnatron:
Got another one playing a game https://www.dropbox.com/s/vkcjaxgh4x8yx7e/2014-06-03_22.17-log1.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kronstedt:
Got a bunch of reboots using waze on both 6.1 and 6.3 https://www.dropbox.com/s/b9yy87s19yg434m/2014-06-03_23.27.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Guys, Pwn's last comment seemed quite sour to me.... I hope you guys give him the credit he deserves busting his chops for us while we watch shows.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I wanted to stay outside as long as possible, you can imagine how translucent one would get working on an Android kernel and ROM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nostrings:
Thanks for your hard work - definitely appreciated!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Blame the Dynamic FSync man. Just turn it off bro. It causes data corruption on sudden power failure/kernel panic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Trust me it's getting the hell out of the next kernel as soon as possible. I may use ASYNC_FSYNC in the future, but for stability... especially with the new Quantum I am going to go for stability.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Another reboot while snapchatting. Took the best pic of me ever and didn't even send it lmfao.

https://www.dropbox.com/s/s355l9kddrdqpmr/2014-06-03_23.37.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
What ROM are you on if I may ask?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Quantum 3.67 hah... Kinda behind but this one been the most stable for me. Plus I don't really like the Slim base...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
No issues. That's crazy though. I have a list of commits needed to be reverted in the kernel that I researched earlier today. About 11 possible reverts.

On the plus side I have finally got some ART optimizations into the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Damn, just found out Developer Settings crash Settings.apk

Probably ROM issue, but I really don't want to switch to Slim based version, so I'll suck it up. Minimal "error only" log attached.

https://www.dropbox.com/s/wcocq2iidkqrxzd/logcat_and_device_info.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Bleh. I'll make one last kernel update that works on the previous CM and then form here on out it's all new stuff. I reverted the FSYNC and other potential offending commits.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xbiker321:
Thanks Pwn.. Looking forward toward a fresh new start!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Just a question tho... Could you go back to your base with the ROM? I honestly think your design is much better and well organized than the Slim one (no offence to Slim devs)

No pressure though, I'm just wondering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
All due respect and props to Pwn for all his hard work, I too am not a fan of Slim, for various reasons, which is why I'm still rocking the CM-based Quantum (3.65) with the dkp kernel. I've given serious thought to going back to vanilla CM at some point in the future, but based on everything I've read in the CM thread, it still has a lot of issues, maybe even more than CM 10 did at this stage in its development. Still, though, you gotta love the wealth of custom ROMs and kernels this two-year-old device still has. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Hardly has any actual issue per se.

Dave (nardholio) as well as others are working around the clock bringing updates/commits to the d2 platform. If you check the nightlies changelogs you'll see hundreds of commits have been merged recently, but prior to that things were pretty stable (also known as dead), so most of the issues remaining at this time have been caused in the very last few days and will therefore also be fixed in the near future. Android 4.4.3 is right around the corner too. ;D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Just flashed Liquid Smooth which is the first 4.4.3 I've seen. So far, very nice. Still looking forward to Pwn's next creation though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
That's not really 4.4.3. It was done as a joke. Think it was just a change in the build.prop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Well I went for it hook, line and sinker then! Now I'm really looking forward to Quantum Next! :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tiernan22:
I really like this Slim base. The features are second to none and it's been extremely smooth. I think this is what CM should look like when it grows up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That's a funny comment, considering it's the other way around. Slim is still in its infancy compared to CM. Not that old age means quality, featureset or anything, but "grows up" made me laugh.

CM aims to be a little more mainstream and a little bit less obscure featured than most custom roms, which is what gives it its popularity. It's a good entry level rom for people beginning in the world of rooting and custom roms while still providing plenty enough of features to appease most power users. It's not and hopefully will never be like Slim, not that there's anything inherently wrong with it, just they are likely better separated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tiernan22:
All true statements. I said that in jest. It is certainly more mainstream and universal. There will always be a place for that in this sphere. One can't discount the contributions the CM team has made to the community. I never really came away from CM feeling truly satisifed, where I now do on the 4.0 Quantum base. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] freaksavior:
4.1 and 6/1 are not booting for me. Screen times out. I've done both a dirty flash and a clean flash. If I load 4.1 by itself, it works fine.

edit: works now, sorry to clutter up the thread. Check your md5sums if you're having issues.

Old one that was having issues.

Awesome-Horsey: Downloads$ md5 QuantumKernel-6-1.zip

MD5 (QuantumKernel-6-1.zip) = 0b8c131dbadc3a91a5aae838e6961a17

new one that worked.

Awesome-Horsey: Downloads$ md5 QuantumKernel-6-1-new.zip

MD5 (QuantumKernel-6-1-new.zip) = e1d36ed0baef3189d5450fe333a97748

Awesome-Horsey: Downloads$ e1d36ed0baef3189d5450fe333a97748

Very quick and buttery smooth, finally back to something stable, lets hope it stays that way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
If you want features, you can always xposefy your framework. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I understand your feeling, and I've had the same sour taste in my mouth quite a few times. The biggest issue seems that they're "too" mainstream. Devices get dropped left and right, even somewhat flagship devices like the S3 only have a handful of devs working on it. Phone was one of the most sold smartphones ever with over 50 million sales...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Come help me then. You get the new camera stuff working. How about new Bluetooth? Gps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
We all appreciate your work, and I wish I had the necessary knowledge to help you make this business a 2 men team instead of a 1 man band. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Just had a reboot while inputting a calendar appt on Carbon ROM from 5/28 and Quantum Kernel 6/2. I'll attach the log.

I'll flash Carbon from 6/3 and the new kernel in the root directory and see if I get any more. I've had several just haven't posted them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Flashed Carbon from 6/3 and the new kernel (6/3) and phone would not get past the kernel boot screen. Went back and flashed just the ROM and it would boot completely.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Known issue so far. There's a kernel in the very main root of my hosting folder that will work on the newer ROM labeled 6/1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
oh ok I thought it was the 6/3 kernel that was there. Sorry about that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Why would you pull a logcat after a reboot? Logcats don't show kernel related errors and they get erased every reboot. You need the kmsg, last_kernel log.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
That's what I thought I needed to include, sorry for my ignorance. Pwn already told me the fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangtastic:
bluetooth

02E69363ET4340712

Thanks for an awesome ROM/Kernel - Quantum 4.1 works awesome!

Enhancement Request, if you get time: I'd love to see the Bluetooth implementation from Task650 migrated over - his works flawlessly with BMW Office (specifically, SMS & Exchange Updates), etc.

Most ROMs only connect with Bluetooth for Audio, Telephone (service and contacts) - No other ROM I've tried has an implementation bringing in Email and SMS to the Idrive screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
"Tumble weeds roll by"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
I'm hoping this is some sort of sarcasm. We've had an updated kernel just in the last week, and pwn has been around here letting us know what's going on.

I'm itching for updates just as much as any other flash addict, but as far as thread abandonment goes, this isn't it.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
*Broken code rolls by*

Seriously can't build anything right now. Getting a crazy error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
Lol not development, just very little going on in the thread today, no disrespect:p

Also how do you change the time zones on xda, all posts show incorrect times
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yeah today has been super quiet. I've been trying to build for the last 2.5 days and no matter what I do I keep on getting the worst errors possible. I would assume settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Have you tried turning it off and turning it back on? :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
No rush, everybody appreciates the work you do for us. Best rom and kernel I've ever seen(except the reboots, those will probably be gone soon!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Thanks a ton! When I got the notification I was walking my dog and it was all nasty and rainy, thanks for cheering my day up a bit! Maybe I'll finally go out and get some lady issues off the mind :highfive:

A few times... I honestly don't know what the issue is. Followed the same procedure as always and then some.

I totally forgot to do that part, I have the kernel cooking now and I'll post it up in a minute! This WILL NOT WORK FOR ANY ROM MADE PAST 6/2

Ahhh.... the beauty of super fast computing :) With the case you guys all helped me get to keep everything cool and the cleaning and optimizing I've done just with eveyrthing in my computer I can bust out kernels in less than 3-6 minutes or so.

http://d-h.st/Bny
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bonnatron:
Is there anyway to get the s4 keyboard my wife has an s4 and I really like the number row above the keyboard
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Find an apk or something for it. I have absolutely no idea because I use Fleksy.

For everyone here you should be very grateful about our bootloader unlock, my Moto X just FINALLY got a TETHERED root!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bonnatron:
Could I pull it from her phone? If so which files
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
http://bit.ly/1kExu27

Not trying to be nasty, just had to do it :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
Ahhh.... the beauty of super fast computing :) With the case you guys all helped me get to keep everything cool and the cleaning and optimizing I've done just with eveyrthing in my computer I can bust out kernels in less than 3-6 minutes or so.

http://d-h.st/Bny[/QUOTE]

once again sir , thank you for your work that we all get to enjoy.!

& not to be in your ' business ' but good wishes for a clean flash on your personal life.

thanks again. :thumbup:

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
A clean flash... I like it! If there are any more reboots please leave a log and detailed info. There may be one more offending commit. Not exactly sure!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangtastic:
Hey pwn I believe everything happens for a reason! I'm sure in time you'll see it was for the better!

I'm glad I could return the favor and bring some happiness back to you. Just a small token of appreciation for all time and effort you put into this.

:highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unit68:
Pwn, could you update the OP with the trickster setting you use? i know each device is different but i'll like to try to start with what you use then change it from there to suit my device/usage

currently im using:

256 bfq

intelliactive
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
10 seconds into booting the 6/6 kernel I got a hot reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Try jiggling the cable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BretR574:
Is that the solution to help with the build issue or the lady issue? :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
We be knockin dem bootloops.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
[MENTION=1683096]PwnCakes193[/MENTION]

Hey, you busy? I was wondering if you could add something to the ROM but I don't want to bother you or make too much work for you if your doing something right now.