yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Jsmokey:
Not at this point, I built a test version with lagfix and in tests it didn't really make enough difference in overall performance with the tweaks I made to the rfs scheduler to make it worth the extra bloat to the kernel.

I've made a few posts about why I decided to keep rfs, mainly because its optimized for small files which is what most files are on a phone and the biggest problem rfs had was the cfq scheduler and how it was set up. If you read through the op it talks about this some and about initial lag at start up caused by the read ahead buffers, which is worth it because media scans, gallery loading etc are much faster, it just pauses for a second when it first boots up.

File system read and write speeds are about as high as we can get with how I tweaked the scheduler and I also got rid of most of the overhead caused from using cfq on rfs systems and on the /sdcard partition it uses noop instead of cfq. Mostly because cfq is mainly designed for platter type drives which phones clearly don't have.

Once I get cwm finished it will have universal lag fix built in though.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] Soy_Filipo:
Im currently using Samurai Kernel 1.3, I guess I should go back to rfs before flashing this one, correct?
[Captivate Android Development] Jsmokey:
Yep if not you'll end up in a bootloop.
[Captivate Android Development] Jsmokey:
Zipalign versions up!

Update: Attached the new zipalign versions to the OP, finally got permissions sorted out still not sure exactly what the problem was though just changed a few things here and there and it worked. Basically the script will just check all the apk's /system and /data to see if they are already aligned and if they aren't then it aligns them. Also saves a log to /system/zipalign.log to see how many apps weren't already aligned just for those that are curious. Other than the zipalign script there aren't any other changes, working on a few things atm to try for the next version though.

Also wanted to let everyone know that modding cwm is coming along, just really slowly. Still working on the KH3 boot animations too, starting to make myself a little nuts in the process of it. Anyways hope everyone enjoys the new zipalign versions it really does make a difference even if it is a small one.
[Captivate Android Development] lilbigdude1:
I flashed the kk1 stock rom...just curious....and ran quadrant on your aggressive ver. Scored from 950 to 1050. Flashed your aggressive-za version, first run 1620 third run 1927.....major difference. So far its been stable on this rom Thanks for this amazing work'

SGH-I897

2.3.5

I897UCKJ3

SAMURAI KERNEL 1.2

ILLUMINANCE 1.1

TEGRAK UOC 1.3 ghz
[Captivate Android Development] BitteredBro:
Hi, Jsmokey.

I was reading a post of yours on Kyuta's thread about using V6, Adrenaline Shot, etc. with your Kernel. Is there a easy way to undo the changes done by those tweaks?Reflashing the kernel it's not enough right?
[Captivate Android Development] Kyuta Syuko:
If you're talking about the USAS tweaks just delete them from the init.d directory and reboot.
[Captivate Android Development] Jsmokey:
If you want to you can you can also just remove them as kyuta said. And really if you want you can leave them just no promises either way on what may happen on performance. I just don't believe they work very well with my kernel. If you do decide to remove them you could leave the mount script though and it should bump performance up slightly.

I actually gave v6 a go btw and it may make a slight difference or might not since it tweaks alot of the same stuff my kernel does I just advise against adrenaline shot because it only tweaks a few settings that by them selves are ok but combined with mine could cause some weird results. You should just be able to run the supercharger script again and it will undo the changes if you want.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] BitteredBro:
Thanks Kyuta. What about this changes:

"/system/bin - fugu binaries both from honeycomb 3.1(3.2 is on the way)

/system/lib - patched sqlites for better I/O performance

/system/etc/sysctl.conf - systclt.conf allowing compatibility with supercharger script"

How can I bring them back to normal?

Should I search for the files in the original ROM and sustitute them? Should I let them alone? Or the scripts deletion would do the job?

---------- Post added at 12:14 PM ---------- Previous post was at 12:01 PM ----------

Thanks Jmokey and Kyuta.

I did remove the scripts and replaced them with Jsmokey's. Also applied some build.prop tweaks for rendering GUI with GPU and responsiveness . The change is for the better, specially while playing ShadowGun wich has been my objetive for the last couple of weeks.
[Captivate Android Development] Jsmokey:
As far as everything but sysctl.conf they could stay and with sysctl.conf you can open it up with /system mounted as rw and clear all the text out of it or just remove it all together it just writes settings on boot just like most of the init.d scripts in my kernel.

Its actually the file linux uses to change settings on boot they just re-enabled it in android with one of the adrenaline shot scripts. That way if you remove the scripts that write to sysctl the settings stick still unless you erase its contents or remove it all together.

Glad you got shadow gun working btw. Next version will have a couple more adjustments to a few settings and the last of the tweaks will be put in place should see it by around thursday or so. Altogether it should be a little more refined as far as the scripts go instead of just echoing values into there respective places.

If anyone has looked through the zipalign script they will all resemble it a little more, the originals were just a quick and dirty way of doing things. The zipalign script is my work I just used another as a model to see how it should work, the one I used was made for running from term emu or script manager so it used the tee command and alot of little run arounds to do the same thing. I also wanted to mention that the zipalign binary is located in the /system/bin directory just incase anyone was curious of where it went on install.

I'm also going to try to get kh2 sources built and booting so I can get a voodoo color, sound, and bln version pushed. Fingers crossed on that one cause no one can get it to build right for some reason.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] Jsmokey:
Hey guys just wanted to drop by and see if there was any interest in a kk2 version of Red Nebula. I was holding off thinking the kk3 leak would be out at the beginning of the week but since it hasn't dropped I thought I'd ask if anyone was still using Red and wanted to see a KK version out.

CWM project is still in the works btw guys just coming along slowly with everything else I have going on right now. My kh3 rom should also be out here pretty soon, getting a few things finished out when I have time here and there but it is finally almost ready.(by my standards, I hate pushing things if I'm not 100% happy with it)

Anyways hope interest in Red Nebula hasn't died off and that everyone is still enjoying it.

PS: I'm working on an ICS port now that I have source to work from, never could get more out of the sdk than to boot and a few things barely half working, so keep your eyes peeled for that too.
[Captivate Android Development] BitteredBro:
I'm on red nebula and happy with it. It's really necessary update to KK2? Did it bring something to the table?

I definitely want to see Antares and your take on ICS. I think your effort could be better placed there.

Well that's just my opinion.
[Captivate Android Development] Jsmokey:
Pretty much just considering kk2 versions because of the possible bug fixes they may have implemented, since they definitely have fixed some problems with how samsung handled rfs over the froyo versions of android I'm guessing they are slowly implementing other fixes into the kernel/firmware although its really hard to say without source code to compare.

Antares has been my 'baby' over the past couple months and has a ton of work and modifications especially in the theme. I'm really excited to get it out there but everytime I get close I think "well maybe I could tweak this icon or add this feature" and it just keeps on going.... that's my ocd for ya.

ICS build is slowly coming along I've just about got past all the errors building it just got to wait for it to finish once the last of the kinks are worked out in the make files if there are any left and get to testing and fixing. As soon as its booting and at least somewhat usable I will post it up though.
[Captivate Android Development] jlsesler:
Yes. Please make a kk2 version!
[Captivate Android Development] lilbigdude1:
Bricked my last cappy....building courage to do the unbrick mod.. but I went and got the SGSII its 2.3.4 KH7. Am I able to use the KJ3 CAPPY kernel?

SGH-I897

2.3.5

I897UCKJ3

Red nebula aggro-za

ILLUMINANCE 1.1

TEGRAK UOC 1.3 ghz
[Captivate Android Development] Jirv311:
Since I just finished the KK2 version of MaxQ, I'd be interested. I've had requests for your kernel on my KJ3 version. :D

I understand the lack of time to get these things done. It took me way too long to get my KK2 out. Personal life first though right? Good luck with your builds.
[Captivate Android Development] jbabbler:
Tagging for BLN updates.... :D Only think keeping me on I9000 Roms as of now.
[Captivate Android Development] Wdustin1:
I really doubt it, could be wrong but kernels are device specific. By the way how did you brick your cappy

Currently Fusionized
[Captivate Android Development] Jsmokey:
I'll try to get a kk2 version packed up tonight if I get the time.

And personal life almost always comes first. Wife always comes first. lol

As far as the build for ics goes, at this point I'm working on getting it to boot to be blunt.

@the post about sgs2

I'd highly advise against even thinking about it, at best you'd probably get stuck at the kernel boot screen if that far.

edit: Now that the kk4 leak is finally out I'm going to go ahead and package up a new version of the kernel, this was really what I was waiting on before making a new version just didn't think it was going to take so long for the new leak to drop.

Also I wanted to get some feedback on my antares roms theme. I decided for the initial release to go with a blue theme loosely based on the look of ICS. I mean very loosely just using its color scheme and layout as a general base and I just wondered if this would be a more welcome initial color scheme for everyone since the overall consensus with red was pretty much a no go, the Revolution theme will still be released alongside antares as a flashable theme pack but I wanted something that would be more welcome from the get go.

Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] Jsmokey:
Wanted to give an update on those waiting for the new kk version. I'm having troubles getting it to boot not sure if its the new extract/repack method I used on it or something else altogether. Hopefully I can get it sorted out and posted in the next day or so.
[Captivate Android Development] xhozt:
Hey ild love a red theme ;-) only thing is i also want the attwifi app left in . . .
[Captivate Android Development] Jsmokey:
Lol well I could throw it in a cwm flashable zip but all the att bloat is taken out. I was going to release a flashable zip anyways so people that wanted the bloat could flash it back then remove whatever they don't want after that with an app manager or root explorer.

As far as the theme goes I decided to stick with red for the release since the theme is near completion and the blue theme, which I decided on the name Dark Ice for, has a lot left to do must say though I'm really liking the way its coming together with some of the ICS theme incorporated. I hate the way some of ICS looks and other parts look amazing with what google changed around.

Update to kk4 progress

I also wanted to let those waiting for word on the kk versions to come out that its most likely going to take some time. I'm having a hell of a time getting cwm into the kernel and working right, not my cwm mod project but the one that's been in previous red nebula versions. If there is any interest I would be happy to post a non cwm kernel for now till I get the problem sorted out. Only real problem with that though is pretty much anything you would want to flash you would need to odin or heimdall it on there which means no cwm theme flash packs, bug fixes, etc.

As far as needing to release a kk version I really don't think at this point it is really necessary since all the leaks for gb will work with any of the older gb kernel leaks and vice versa and from what I can tell there really is no changes to the kernel anyways in the newer leaks. I really wish I could get this out for everyone though since there is a demand for it but at the rate its going unless boog puts out a new version with cwm already in it to work from or I can get around the issues I'm having there may not be a new version of the most recent leaks although I will keep updating the old one's and trying to get the new leaks sorted out and working till captivate gb source drops for the kernel then I will get started with it.
[Captivate Android Development] Jsmokey:
Ok should have kk4 ready tonight guys. I think I finally got all the quirks worked out. It'll be basically the same build but I have changed a few settings around and I'm working on getting a couple small additions to the tweaks finished.

Sorry for the long wait everyone but I've been busy working on my rom trying to get things finished up for release since kk4 was giving me so many issues.

Playing around with ics kind of set me back on my roms release because it gave me a lot of new ideas for the theme that took a lot of time to get sorted out and looking right.
[Captivate Android Development] jlsesler:
Which rom is yours?
[Captivate Android Development] Kyuta Syuko:
He hasn't released it publicly yet.
[Captivate Android Development] Jsmokey:
Nope but it will be out soon, I keep pushing it back to add more to it and get the theme to where I'm completely happy with it. It's finally almost to that point now.

update: Ok guys I have a build based on kk4's initramfs compiled with parts of kj3 to get it booting and cwm working properly. I tweaked lmk settings around some to be more aggressive and keep home from being killed. It runs a lot another than previous versions. If anyone is interested I'll post it up in the mean time I'll keep working on getting a full fledged kk4 version up and running.
[Captivate Android Development] xhozt:
all ok man?
[Captivate Android Development] edtonn:
+1, miss you 'round these parts, Jsmokey. Your posts are always so informative & comprehensive...definitely helps me understand some of the inner workings at least
[Captivate Android Development] Wdustin1:
he's so busy he lost all track of time lol. add me to the miss ya list haha
[Captivate Android Development] Jsmokey:
Lol its definitely been a busy past couple weeks, I did add to my post above your guys about a hybrid kj3 kk4 build working a few days ago but work on my rom has kept me from working on a full kk4 build. If anyone wants to try the hybrid just let me know and I'll post it up.

Anyways since I'm talking about my rom anyways and its nearing completion here's some more screenshots. Also this is an odexed rom but I'm doing all I can to get the deodexed mods working, so far accurate batt among others is working perfectly. Also working on the cam mod where you can take pics with the power button and use it below 15% batt.

Some things I'm still working out the kinks in like the quick panel buttons being overlapped by the indicators, still need to pull and re color the ics signal bars and other odds and ends. If you notice I used the pop ups from ics also, they have a much cleaner look to me.

Reason I went odexed was the size difference and the increase in speed over deodexed, personally I think we should all put more effort into getting odexed mods put together and working. It may be harder but in the end it pays off I think.

Need to work on my status bar pull down a little more and have to open up twframework still to change the tabs at the top in the dialer among other things.
[Captivate Android Development] Wdustin1:
is your rom still kh3 based? lol nice job you are putting your heart and soul into this thing. I will love to see this thing. its gonna be hard to take criticism after all this work. very excited for a look at your rom and a kk4 kernel
[Captivate Android Development] Jsmokey:
It is kh3 based atm but once its finished I'm going to pull it all into a kk4 or whatever happens to be the newest firmware when it is done and release them both.

Yeah I've put a ton of effort into this thing, I think almost a total of probably 8-10 hours just getting an odexed battery mod working correctly and probably almost 40 in the rest of the theme including testing and everything.

Criticism I don't really mind people will either like or hate it but that's why I'm working on a few different themes for it and if they still don't like it well.... tough **** lol.
[Captivate Android Development] Kyuta Syuko:
Just out of curiosity are you using the APK Multi-Tool for creating/modifying your ROM? Used to be called APK Manager I think or maybe it's an updated version by someone else. Not really sure...
[Captivate Android Development] Jsmokey:
No I use android utility by tommytomato to decompile, recompile, any smali work, and zipaligning after compiling basically its apktool, aapt, dex2jar, zipalign, and most of the major needed tools with a term gui that does all the leg work. You just drop what you want to work on in the right folder, fire up au, and run the options you need.

Everything else I do manually. He also built dsixda's kitchen into the new version of android utility and it also has an all in one tool for drawn9patch's, compile raw. .9's, decompile, etc among other things.

By far the best and most complete/feature filled tool for theming and now rom building also. I highly recommend it if you plan on doing any work on apk's. Really the new version takes most of the "work" out of it since tommy added in an auto meta-inf injector, which will put the original meta-inf back if you extracted it in the first place, and an auto zipalign option that pops up whenever you recompile an apk.

Oh I also use 7zip and the ubuntu archive manager to push or pull pngs and edited and compiled xml's to do quick tests for new icons/xml tweaks. Its an old trick but it saves a lot of time and hassle when just testing out one or two things at a time.

Gimp is what I use for making my icons and I use inkscape to make vector templates for my scratch made icons so its easier to make different color variations and its also easier to make slight tweaks to the shape with a vector than with a template, png, etc. If I happen to be on my windows set up and feel like doing some work or my osx partition I use photoshop usually. Anymore I kind of prefer gimp though especially since it supports photoshop plugins now.

Once my current projects are all finished up I plan on making a theme guide since most I've come across barely cover most of the basics and use outdated methods and tools.

edit: here's what the main menu for android utility looks like just so you can get an idea of what all it can do.

Welcome back tommytomatoe,

Android Utility by tommytomatoe. Version 1.0.7. Special Edition

|-------------------------------||-------------------------------|
|-------------------------------||-------------------------------|
| BASIC TOOLS || ADVANCE TOOLS |
|-------------------------------||-------------------------------|
| 1. adb tools || 7. apk Re-Engineering |
| 2. keystore manager || 8. apk Optimization |
| 3. sign apk and update.zip || 9. dex code utility |
| 4. zipalign ||10. draw9patch utilities |
| 5. change-log creator ||11. AU ROM Utility |
| 6. png swap themer ||12. 3vodex |
|-------------------------------||-------------------------------|
| K. Run dsixda's Android Kitchen |
|----------------------------------------------------------------|
|----------------------------------------------------------------|
| x. Run Installation Guide || e. Extras |
| i. Install Android SDK || q. Quit |
| u. Update Android-Utility || |
|-------------------------------||-------------------------------|
Select an Option:
[Captivate Android Development] jlsesler:
Looking forward to trying the new rom...
[Captivate Android Development] Kyuta Syuko:
Where/how do I get that program? Tried using repo -- like when getting the Android source -- with the gethub but got errors.

*edit*

Nvm I totally forgot about the Download tab on the github...

*edit 2*

Wow that slow text output is REALLY annoying...
[Captivate Android Development] Jsmokey:
Yeah I know but it only does it on the first install after that it loads right up. Someone else had issues using the installer due to git issues its on the last couple pages. Had to do with the version of repo I believe.
[Captivate Android Development] bimmernut318:
Whats happening with this project? Looking forward to the progress on this and the rom.
[Captivate Android Development] Jsmokey:
Well the kernel has pretty much stopped dead in the water due to my problems with kk4.

As far as the rom progress is still coming along but very slowly due to me trying to do the mods on an odexed source. Its making things a huge pain but it really is worth it due to the reduced size of the rom and the extra free ram an odexed base has.

A few things currently have me completely stumped. For one I'm trying to get extra lockscreens built in, which I don't have prior experience with and its really put a halt on things. Also the camera hacks are really killing me but aren't nearly as bad as the lockscreens.

A few other things have gave me problems but nothing like the previously mentioned which are really all I have left to finish up.

For some of the mods I have no choice but to deodex the needed apks and jars then do the mods and once they're done I have to push them to the phone and use dexopt-wrapper to reodex the files, which in itself is a big pain to go through over and over.
[Captivate Android Development] Wdustin1:
I don't think the lockscreen mod is too big of a deal. Now the go locker works great I don't ever even see the built in lock screens. But thank you for putting in the work always nice to have options. I am ready to give a odexed rom a try I have never ran one. Well except for stock. I hope you can get those problems figured out soon. good luck on your endeavours lol
[Captivate Android Development] Jsmokey:
I agree go locker is pretty awesome and it doesn't use many resources but it does lack some of the lockscreens I've come to like the most namely the sgs2 lockscreen which I fell in love with and even though go locker uses very few resources factory lockscreens use even less since the process is already loaded into memory regardless if you use it or not.

Between deodexed and odexed the biggest difference you'll see is in the amount of ram used. Its nothing drastic but enough of a difference to notice especially when running multiple apps.

Aside from that the ui feels smoother and the rom comes out a little smaller in the end.

There's quite a few other tweaks and add-ins throughout. A small list of what I've done so far is.

custom wallpapers (around 250 and counting)

modded ui sounds

a whole ton of ringtones, notification and alarm sounds

modded aosp desk clock

tons of ui mods on top of the actual theme

changed the default screen time out rates(removed 15secs added 5mins)

And a whole metric **** ton of other small tweaks throughout.
[Captivate Android Development] Kyuta Syuko:
Here's something to make your Christmas even brighter :)

I897UCKK4 Sources are up on opensource.samsung.com