yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I have already added a 480Mhz step for GPU and currently testing it. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hopefully klin will be releasing kernel for CM stable shortly, that is what he quoted couple of pages back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
So excited for this next update. Is the OC GPU proving stable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Actually I added the oc step, but it made it compile with a forbidden warning. So I edited the makefile to allow it to compile correctly, but it didn't boot... I'll have to investigate further.

But I've been working on adding custom voltage control. I'm almost done, just have to fix a bug that is causing weird artifacts and random reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
So I guess here's a status update:

I just got custom voltage control working, and it seems to work well with different apps, like system tuner, setCPU, etc.

As for GPU OC, I have to do more work on that because it's not booting for some reason. I'll be working on it tomorrow and try to fix it.

Sorry if it's taking a while for the next update...I want to make sure that everything works and is optimal before releasing it to the public.

Thanks! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Another update today:

I got busy today, so the only thing I was able to to was ifdef out the voltage control code. I did this because for some reason, my device always had weird artifacts (black squares) and random app crashes with kernels that can undervolt (kt747, lean kernel, etc), even when I do not touch the voltage table. I think that there are a few minority who are plagued with the same issue as well, although the majority of others do not have this problem. In the next release - no ETA - I will be releasing a voltage control enabled edition and a stock voltage edition for the few who have the same issues that I have.

Also, I with probably be donling these "heads ups" ofteb...I like to let users know exactly what my thought process is, what I'm working on and what to expect, and why. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Running your last build and so far, smooth as butter. Can't wait to see what the next build has.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
which release are you running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
The latest release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
My phone has been unplugged since 6:15 CST this morning and I still have 90% battery!! I do have a 5300 mah battery but by this time, 5:30 CST I'm usually at 75%, so this kernel is great! I'm on a GS3 with Carbon Rom nightly build 6/26.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Told ya!! LOL

Glad it worked out. Really is a strong kernel.

Thanks klin!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I'm gonna use my stock battery tomorrow and see what I get on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nickdoherty:
Any chance of adding fast charge?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
No, because drawing anything over the intended 500mA from a USB 2.0 port is dangerous and could potentially harm your hardware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
This kernel is the best fit for cm10.1! Battery life is awesome.! Waiting for next release for sure!.. Thanks for your hard work!!

Cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't see how it could damage your hardware. Your phone will take what it can and what the USB 2.0 provides, you can't "force" it to take more if it can't.

Fast charge only enables you to charge at the same rate as a wall charger from a USB port. This is especially useful if you have a USB charger in your car that can provide more than 500mA but your phone detects it as USB thus will only charge as fast as if you plugged it in your computer.

Edit: Although I guess it could technically potentially harm your USB port in shoddy conditions, after much thinking. So scratch that, for the sake of not breaking people's computers or something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Whatever features come I'm so excited. This kernel gives me such great battery life and performance. Can't wait for the next release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
That's correct. I can't find the link right now, but a fast charge commit for CM was rejected because 2 of the 2 electrical engineers and all the devs rejected the patch because it could harm the computer's USB port.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
It's been a while before my last release...I'll try to get one out today! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yeah I was thinking of the phone issues, which seems there would be none, but I know a lot of cheaper motherboards have very bad quality USB ports so you could technically end up frying them. I imagine it would be similar with cheap car lighter USB ports or even embedded car USB ports.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
7/2/13 Update

The new update is out!

Here are some of the key changes:

Please refer to the 2nd post (writing it up now) on how to configure GPU OC. Enjoy! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
why is 6/24/13 ? just asking
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
I just had an ''install aborted'' error message when flashing with CWM.

The file size being 3.3mb's, is that correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Lol sorry my bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Hmm its supposed to be 5.3 MB. Must have been a bad upload, let me redo it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I did as well using TWRP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I've re uploaded it..please try again...

The file size shows 5.3 MB this time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Alls good now klin.

Thanks man:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
What happened to the 189 step? Just curious.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
The 189 Mhz step needed modification of the init.com.post_boot script, otherwise one core would be set at 189 MHz and the other at 384 MHz. Since I do not want to modify anything from the system or ramdisk to ensure compatibility with all ROMs, I dropped the 189 MHz step.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Sounds good to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I have released another update, labeled 7/3/13.

The only change:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Asphyxiation:
would not let me download the July this update you just put out ! won't find any mirrors . thought i would let you know my luck . and then again, maybe it is only me . ahah .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Hmm.. It seems fine right now. I know earlier today AFH was under a DDoS attack, so they had to suspend downloads temporarily.

But try again, it should work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Any way we can get a quick recompile with all these changes in the last nightly? I'd be willing to blind test it, just waiting for my CM to build right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Sorry, I can't until tomorrow. But the CM updates do not affect us..I think that the revert: http://review.cyanogenmod.org/45051

only affects d2vzw and d2spr because they're CDMA. The rest of the commits aren't significant either; one is for inline kernel compiling with GCC 4.7 (I already use linaro 4.7), and the other is just for fixing compiling with a debug option disabled.

The updates are already cherry picked and pushed to my source, plus another CAF update and an update to Linux 3.4.52. I'll release it soon, after I do some procedural testing. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
Kernel+ is running flawlessly here....!.... great job! my battery had never been so long.... Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
What is the Custom Voltage Control listed in the OP under features? I saw no voltages listed in Trickster...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Sorry what is trickster?

But voltage control means the ability to under volt the voltage table to potentially save battery life. Use system tuner from the play store to under volt, or if you know your stuff than you can create a init.d script to write to the sysfs voltage table.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Trickster Mod, an app to control different kernel settings. Get it from the play store. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Oops, I just noticed that voltage control isn't enabled in the 7-3-13 version...

Sorry about this, I accidentally built with my own defconfig instead of the default one.

I will be releasing another update very soon to address this issue and add a few more features. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
7/5/13 Update

I have uploaded another update, 7/5/13.

Changes:

I recommend using Trickster Mod to undervolt...I've tested it and it works without issues. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the update. How to under volt with trickster mid? Does UV means mpu voltage?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
Does under volt make some real battery saving??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Yes, in theory it should, although I have never been able to actually undervolt my device because I get weird artifacts and reboots if I just run a kernel that supports voltage control.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
I tried to undervolt many times in many of my old devices.... I didn't feel a real difference... So I'm trying to figure out if it is a placebo effect or not....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Undervolting isn't a placebo, the problem is most people undervolt too much and that causes a bigger drain for many reasons which I outlined before in my earlier posts on this forum.

Personally, I do not undervolt my phone. I undervolt my personal computer, undervolt many other things, but my phone no. These things are pretty well optimized by the makers and suffering from reliability issues due to an overdone undervolt isn't my cup of tea. My 2 cents.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
kernel or ROM

CM may have fixed some bluetooth issues with this commit: HERE

I like running custom kernels, like this one... my question is, is this commit present in the CM ROM or kernel? And if it is in the kernel, is it present in yours yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Doesn't Bluetooth already work? I don't have anything to test with, but the last time a user reported that it worked after a fresh CAF merge that changed some of the Bluetooth code.

Also, the commit you mentioned is device specific to the apexq, aka galaxy s relay 4g.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Same here, I do not undervolt my phone, because it can't handle ANY UV and because I feel that stock voltages are most optimal. But I still implemented the feature for those who want to undervolt.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
The commit is listed for the d2-common for last night. I think it addresses some of the reconnect issues that some have with Bluetooth. I have to unpair and repair my headphones everyday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Like I said, that is only for ApexQ, plus it is in the ROM, not kernel. But I will take a look at Bluetooth...I never knew that it is broken again. CM's Bluetooth code is a bit behind CAF, probably because the bleeding edge code doesn't work properly (yet).

If anyone wants me to send them a test kernel tomorrow with attempted Bluetooth fixes, please PM me. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Could somebody please test something out for me? I've been scratching my head around this issue for a day now.

So.. In trickster mod, it shows the current GPU frequency. When I open it, even when the phone becomes idle and CPU load is low, the GPU seems to be locked at 400Mhz all the time, rarely ever dropping down to 300Mhz and never 200Mhz or 128Mhz. But the moment I plug my phone into a charger, the GPU somehow drops to 128Mhz and starts going up if I touch the screen, and dropping back down when it's idle. That is how the ondemand GPU gov should be working it think, but for some reason when I'm not plugged in, it jumps back to 400Mhz and locks at 400Mhz, even when idle. Can someone test if the same behavior is displayed on your phone as well? I tested with CM10.1 kernel too and I'm getting the same behavior.

I have attached screenshots (I've disabled the 480Mhz step on my device)

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Alright klin, just did some testing. Trickster Mod here and Carbon Nightly 7/5.

When not plugged into the charger, and touching the screen, it would jump around, 300,200,128. Funny tho, at one point for a second it hit 480. Other then that, locked at 400.

Same readings as yours when plugged into charger

GPU Gov 480/Ondemand
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Thanks bro :)

Now I know that it's not specific to my device only, and I'll continue to investigate.

Edit:

You're right, when touching the screen it jumps over the place, but it seems like the GPU likes to idle at 400 MHz.

Edit #2:

I'm suspecting that the behavior is due to the interactive CPU gov touch boosters, and the GPU responding to it. I think that when the CPU frequency is high, then the GPU freq can go down a bit because the CPU can render the screen without issues. But when the CPU is idle or under low load, then the GPU has to bump up its frequency to render the display to make up for the lack of power when the CPUs are in low frequency. This is just a guess with no research yet though...so I may be completely wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I am having some strange behavior out of the kernel. I can't get it to hot plug and CPU1 is staying pegged at max along with the GPU. I re-flashed a stock CM10.1 from last night and hot plugging is working and GPU idles at 300; drops to 200 when I touch the screen.

I re-flashing kernel+ and now have hot plugging... GPU idles at 400 again.

Edit: I will report that kernel+ is running flawlessly now. Smooth, fast, and really light on the battery with some slight under-volting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Just letting you guys know that I won't be able to update this kernel until next weekend because I am going to attend an intensive class for the next two weeks, Monday through Friday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Oh WTF bro!!!?

LOL

Appreciate the heads up man.

:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Why would you go and take an "intensive class" right in the middle of developing such a kickass kernel... just sayin... :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Because I want to learn more programming skills to make this kernel even better. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Fair enough. We'll miss you for this week! Lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Bettering oneself is an option? Can you include that as an option in the next kernel? I'll bet more folks would choose to do it then. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
sooo... how'd your course go this week? Learn anything useful?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
sure he did, klin is a fast learner! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Yep, learned some advanced android app development.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
You See PPL, Now we are getting the best of the best from one of the best!!!! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
CM finally updated their kernel, I miss frandom!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Waiting for him to return :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Hi guys. I'm back, and I'll continue working on this. Expect and update soon. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hungmung:
Didn't see it on the op but thought I'd ask does this support USB otg?

Sent via carrier pigeon...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I don't know, I've never used USB otg. But if the CyanogenMod kernel does, than kernel+ will too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I can test it later tonight and reply back when I get home. Should be around 8pm CST when I can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Sorry for the delay, been busy with my kids. USB OTG works just fine. I'm using Carbon ROM on the latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Thanks for the report! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
So excited for the next update. You rock klin :) :good::highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
7/23/13 update

Thanks guys for waiting patiently! The new update is uploaded!! Even though the CM kernel was updated and synced with CAF recently, this kernel is still ahead of it, with Linux 3.4.54 and a fresh CAF merge this morning.

Changes:

Enjoy :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Just flashed the latest build and caused my phone to not boot. Was stuck at loading screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Unfortunately same here :( Carbon 7/23 nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
and same here with the latest CyanogenMod nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Sorry about this, I will look into it. It works on my phone with my own CM build though..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
something different between the d2tmo and d2att kernel?

by the way, I flashed the latest version of leankernel... and this one works fine with the rom that I'm using.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
No, d2tmo and d2att use the exact same kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Looks like I've found the cause of the kernel hanging at the boot screen...

To all users:

If this kernel is not booting for you, please use TWRP file manager (or some other method) to change the name of /system/etc/init.d/98kernelplus to 98kernelplus.bak. For some reason the frandom script is not working and is maybe conflicting with something else right now. I will do my best to fix it in the next update, but for now please follow this workaround. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
If you need to do some testing, I'm available...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
I just installed your kernel again this morning and it's working fine with the latest CyanogenMod nightly after renaming the file...

perfect kernel... everything is working fine.

I only have one suggestion/question for you... is there a way to add cpu overclock or downclock to your kernel?

I had overclock working fine on my device with ~1800MHz frequency... this frequency is not used very often... but when it's used, it's fast and stable. with the correct voltage setting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hey klin, so much silence in the thread... Vacations?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I've actually been working on my new app, so I haven't been able to devote much time to kernel +... I will wait until CM10.2 nightlies are out before starting work on this kernel again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
as far as i know, 4.2.2 zimage works on 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Do you think you'll update the kernel for 4.3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperAfnan:
2 posts up here said he'll wait until the CM10.2 nightlies to come out, then continue development. So yes he will. ;) Always read, but I don't know how you missed that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Well I don't know how you missed that 10.2 nightlies for CM have been out for a week or so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SuperAfnan:
Patience my good man, he'll update it when he gets time. Now enough playing around let's get back on topic. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Yes I know he will I was just asking since he said he hadn't worked on it in a while. Its a great kernel and great with battery life so I don't want to miss it whenever I go to 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Yep, just wait a little longer... :)

CM10.2 is still kind of unstable and is still in active development, so I will wait about one more week before starting work on the new 4.3 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
AWESOME!! Thanks man. I'm using Carbon and they've been on 4.3 for about a week now but I'm staying on 4.2.2 for a bit longer that way all of the big bugs can be worked out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I have a question to ask, that I can't seem to find an answer for. On CM10.2, after playing with it eventually it will say cannot connect to camera (both focal and stock camera app), and when I reboot I get stuck on the splash screen. The only way to recover is for me to restore my TWRP backup or wipe my data again. Does that happen to you on 4.3 ROMs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I've seen on Carbon's G+ page that Focal was still hosed for d2's, but for the few hours I was on 4.3 last week I didn't have camera issues. I'll probably clean flash and go to 4.3 this Friday, as thats when I have time to do it. I can let you know if I have camera issues then if you want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdidtht:
No. If that happens I clear data in gallery and it temp fixes the camera.

infected sgh-t999
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Thanks, I'll try it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Read that you have cm 10.2 bootable on your phone, so can we expect something sooner than later?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
use lastest cm10.2, its been a DD for me since then from build ,28 and up.

also im looking to see a good 4.3 kernel from you!!! , cuz you know, you rock!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] itzdustin:
flashed kernal and get a boot loop. what happened? flashed with cw touch recovery. can still get into recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Last update was 7/23 and still only supports 4.2.2. I'd assume this project is closed.

Might want to find another kernel.
[Galaxy Tab Q&A, Help & Troubleshooting] sarayevo:
:rolleyes:hi guys is it posible to port a sense rom on a samsung divice?
[Galaxy Tab Q&A, Help & Troubleshooting] ferdroyd:
possible if...

Hi,

It's possible if the rom that you are about to flash is specifically made for your device. I've seen some xperia rom developed for samsung devices. Just be 100% sure that the ROM is developed for your device. If not, don't try to flash it, it may brick your device.

/f
[Galaxy Tab Q&A, Help & Troubleshooting] sarayevo:
I like to try a sense rom on my galaxy tab p1000 im searching for one
[Galaxy Tab Q&A, Help & Troubleshooting] jalil123:
hi

use custom luncher or them
[Galaxy Tab Q&A, Help & Troubleshooting] sarayevo:
id rather search for a rom thx