yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Jsmokey:
lol, well that was pretty unanimous. I'll keep working on cwm for the time being guys, it'll probably be a few days to get it sorted out if I can, I don't want to go getting everyone's hopes up. My C skills are a little rusty, been a few years since I really used anything but java, python, pearl, or plain ol' bash scripting with a few others thrown in here and there but I'm picking it back up pretty quick as I go so hopefully in the next couple days I can at least get an idea of why nandroid has been failing for everyone.

No matter what I am putting in a modified version so there isn't so many no's in all the menus, change the color and a few other tweaks and I should have an update to the tweaks scripts in the next couple days too. Basically just adding a few tweaks and modifying the scripts a little to to do checks before modifying some things.
[Captivate Android Development] droiduzr2:
Can someone post a pic or confirm what it should say under kernel (from the about phone screen).

I installed this kernel but still displays the "stock" info.

2.6.35.7-i897uckj3-cl614489

Using Fasty KJ3 v1.2 ROM
[Captivate Android Development] Jsmokey:
That's what it should say. Without source we can't change the kernel info. You can check contents of /system/etc/init.d to see if it installed properly but that's about it.

I wish we could hurry up and get some official gb for the cappy so we could get source. I have so much I'd like to do to the kernel.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] boog:
The rogers kh2 kernel will boot on the other builds, I have been fighting with trying to get it to boot after I compile it locally (the stock released kernel will boot on mine, just not my build). I think I'm not getting my initramfs modules loaded correctly, because it doesn't appear to even be mounting or seeing any of the partitions (on rfs, haven't even tried to implement ext4).

I got tired last night and gave up for the night, but I have a few more ideas I want to try tonight.

Just blundering my way through everything I do!
[Captivate Android Development] Jsmokey:
I'll have to check that out, I was wondering if it would boot it or not. If I can get it to compile and boot that would be awesome cause I have pretty much everything set up to patch in voodoo color, sound, and bln for when the source drops.

Sometimes blundering around leads to the best discoveries so its not always a bad thing.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] jasonsymack:
hey mine is the same! Fasty 1.3

Doesn't seem to want to overclock in Tegrak as well. *always shows 1.0GHz*

when I choose another clock freq, it runs through stability check but doesn't seem to overclock...?
[Captivate Android Development] Jsmokey:
That's very strange have you tried clearing data and cache for tegrak through settings--> applications? No one has reported any problems overclocking so far.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] -Thrive-:
Had the exact same problem. Tried switching kernels and it didn't help. Very frustrating. Then I went to a backlevel version of Tegrak. Have no idea what the cause is but that fixed it. Try Tegrak Ultimate version 0.5.1.4.
[Captivate Android Development] jasonsymack:
let me try that~

so in tegrak where it says 'CPU MAX FREQUENCY'...if the OC is working...it should show 1.3 GHz right?

cuz right now i only see 1.0 GHz, 1.275 v no matter what i set it to
[Captivate Android Development] Jsmokey:
Yep should say 1.3. I did notice the last time I updated tegrak the change log said something about a fix with issues running it on gingerbread.

You might want to check the market and make sure you're running the absolute newest version. If so you may need to try to dig up an older version and see if that works. Or you could try just to unistall and reinstall and see if that helps.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] jasonsymack:
sweet! did as you said...finally works now. I was on 7.0.4 downgraded it to 5.14

Thanks a lot for the help Thrive and JSmokey~
[Captivate Android Development] Jsmokey:
You're very welcome and I hope you enjoy the kernel.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] jasonsymack:
so far its great

overclocked, it feels a lot snappier than when I was on corn.

awesome work! :)
[Captivate Android Development] Jsmokey:
Glad to hear it. The difference in 'snappiness' has to do with the kernel scheduler tweaks. It pretty much is devoting most resources to what's in the foreground and when switching between apps its set up to reassign resources very quickly.

Plus the vm is tweaked to only use swap when absolutely necessary so 90% of the time what you're using the most is staying in ram for faster access and only dropped to swap when the kernel knows its no longer needed, after a specified period. All this combined is why even when ram drops to 60mb or less free things are still pretty responsive.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] kdot25:
tried this kernal over [Rom 2.3.5][Fasty KJ3 EditionV1.2] and know its stuck at the at&t boot screen for like 30 minutes. Pulled the battery out several times and nothing is happening when i reboot (back to the at&t bootscreen). Recovery nor download mode is working.. dammm it
[Captivate Android Development] Jsmokey:
Sorry to hear that, sounds like the flash went bad somewhere, or possibly the download was corrupt.

There's a few tricks to get in dl mode when things go bad, you can try to pull the battery leave it out, plug the phone in to the pc then hold down the volume buttons like normal and then touch the contacts on the battery to the ones in the phone.

Also sometimes the phone actually has enough loaded to run adb reboot recovery or reboot download I found out a few weeks ago.

If none of that works about the only option is to buy or make a jig. If you have an extra micro usb around and a radio shack or any electronics store near by you can easily make one. I've even jumpered a resistor that was the correct value right off the contacts before when I couldn't find my jig but I highly advise against it as it can easily damage the phone and doesn't always make enough contact to work.

If anyone else has any ideas please post I hate seeing someones phone stuck like this.

Oh I almost forgot.... tell me you didn't flash this with lag fix enabled.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] boog:
Sounds like you flashed this kernel while on ext4. flash samurai/corn kernel/kernel from latest fusion/kernel from fasty, then convert back to rfs, then red nebula.
[Captivate Android Development] Jsmokey:
The more I thought about it the more I thought that's what happened too. I hope he/she can get it sorted out. I'm going to re-edit the op so the disable lag fix part is in red so hopefully it stands out a little more and it doesn't happen again.

I also wanted to give an update to everyone about nandroid/modded cwm update. Its going to at least be a week to get things sorted out with nandroid. The code for it is completely screwed when it comes to our devices. It is completely missing support for rfs and its going to take quite a bit of coding to get it working even half way on our devices and I'm pretty rusty as far as C goes. I'll most likely release an update with a few new things well before I get this worked out but I will keep everyone posted on how it goes along the way if there's any progress worth posting.

Again thanks for the support everyone and if there's anything you might want to see implemented into CWM let me know and if its possible and worth putting in I'd be more than happy to give it a go.

So far plans are basically in this order:

fix nandroid

incorporate szupty's universal lagfix

add zipalign to recovery for /system and /data apps

change menu colors and background image

a few other random things
[Captivate Android Development] kdot25:
got it up all and running

pretty much what happened was my captivate is getting old and the volume rockers hardly move, i had to push them in extremely hard to get into recovery. Then i disable the voodoo and re-installed the kernal.

Thanks guy
[Captivate Android Development] Jsmokey:
Glad to hear you got it working. I'd definitely recommend a jig if you plan on keeping it a while with the buttons getting wore out so if nothing else you can at least always get into dl mode if they ever decided to crap out the rest of the way.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] BitteredBro:
I know there are different lagfixes, but that is as far as my knowledge goes. Why the preference for szupty's universal lagfix? Why is different to voodoo? Voodoo is more common, no?

+1 to nandroid, by the way :)

P.D. I found something interesting using your KJ3 Kernel with KH3 ROM. The phone wasn't recognized by windows when connected using USB cable. Tried different cables, windows versions, reseting phone and computers and nothing. Reverted to KH3 kernel and everything works fine.
[Captivate Android Development] Jsmokey:
Basically his lagfix is made to be built entirely into recovery and has more options for different lagfix setups meaning much more flexibility plus there are options for conversion other than ext4. If you check his thread out you'll see what I mean. On top of that it requires well under half the space that voodoo does inside the kernel.

It seems there are a few little quirks running kj3 kernels over kh3 roms from what I've seen, I run linux and osx 95% of the time so I'll flash the kj3 version tonight and see if they recognize it with kj3, might just be a windows thing.

I'm going to go back through some things tonight and see if I can find where the differences are and work on getting kh3 boot anims working again.

The only time so far I've been able to get them to play it would just keep playing and now that I figured out how to get them to stop I can't get them to play again.

Yeah I hear ya on nandroid and its a complete mess, as mtcarey pointed out truly all of cwm is at this point with all the revisions and patched in code. Its making it very difficult to track problems down. I think I probably underestimated a time frame of a week to get it done. Especially since I really need to brush back up on C.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] BitteredBro:
Ohhh. I googled that lagfix name and the only result was you mentioning it. Sounds very interesting. I'll try to find more info. It isn't like I could do something with that info, but who knows? maybe some day, if I study really hard I could do something different than try others people stuff, right? :)

Probably is just some windows thing. It's the only OS I have used but I trust your work more than theirs.

Talking about your work... keep it on!!! You are doing great man!
[Captivate Android Development] Jsmokey:
xdaforums.com/showthread.php?t=814228

That's the link to it just incase you want to read up on what it does and the different settings for ULF the first post is intended to explain things for user's and the second post is aimed at dev's.

Thank you for the kind words it's much appreciated.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mfdemicco:
I wonder if that was just coincidence. I've had a hard time getting Windows 7 to recognize my phone no matter what ROM or kernel I'm running. My other computer running XP has no problem. I plugged the phone into a rear panel USB port on the Windows 7 box the other day, and it worked fine. It may be sensitive to what USB port you are plugging into. Use the rear ports.
[Captivate Android Development] Jsmokey:
Yeah you almost always need to use the rear ports, they run a higher voltage which the phone needs to connect properly, most mobo's have jumpers to increase front port voltage but I don't recommend messing with it as you can really mess things up.

I did try kj3 with linux and it worked fine for me didn't try in osx yet.

I will have an update tonight with a few changes and I'm going to put out a new version with a little more aggressive lmk and oom values for everyone to try that should help keep a little more ram free for everyone.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] ddoubt:
I notice a little RAM drain on Serenity with red nebula kj3 v1.1 after long idle times... waiting for the update to test it out! :D
[Captivate Android Development] Kyuta Syuko:
Have you read the LMK Section of pikachu01's thread linked in my sig? Lots of useful information there.
[Captivate Android Development] Jsmokey:
Yeah that's because I have swappiness so low in the vm tweak script, if you open it up with a text editor like 920 text editor, or any that has root permissions with /system mounted as rw there's some values for swappiness and a couple others that you can play around with just comment the one that's in use out and uncomment the one you want to try.

The comments explain it fairly well there's another setting in the script that should be changed along with swappiness, it tells you which if you read through it.

The reason I set it so low by default is it keeps more in ram for faster access when switching between apps, but it fills up ram a little quicker which is why I wanted to get a more aggressive lmk version out, especially for kj3 since its such a resource hog when it comes to ram anyways.

I will leave the old one up as a highly multi tasking oriented version then put the new one up as sort of a ram saver for lack of a better term.

Yeah I've looked through it a few times, I have most of his pages about different tweaks bookmarked, they're some pretty good resources for rom and kernel building.

The settings I'm testing are a little different than most I've looked at, kind of a readjusted version of some I've came across pulling different kernels apart over the past weeks.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] Kyuta Syuko:
You still having issues with the boot animations on the KH3 kernel? You try to make a symlink and rename it to the other zip (ie if you have sanim.zip make a symlink to it in the same folder and call it bootanimation.zip)? If that works then you know you have it looking for the wrong file. I was having issues with the black screen when I had it setup to look for bootanimation.zip but only supported sanim.zip.
[Captivate Android Development] Jsmokey:
Yeah I am still, that's another thing I'm hoping to get sorted out before the release tonight. Thanks for the tip.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] Jsmokey:
OP will have updates in a few minutes. I added two new versions v1.2 and v1 aggressive of red nebula. The only differences in the two are lmk settings I got it to where you should never really drop below 60mb free without killing background processes unless absolutely necessary.

I also changed vfs_cache_pressure a little in the aggressive version to help with the small lag after a day or so without a reboot. It was caused mainly because I had it set to not drop caches very frequently which helps performance for a period of time till caches would start overflowing more or less and as a side effect pretty much really required a reboot every other day to keep things running smoothly or required the user to drop caches manually.

I aslo did a few more tweaks to the file system schedulers that should help a little more with file access.

I also added an init.d folder backup script that runs on kernel install to the new versions so you no longer should need to back up the scripts you had before you flash my kernel. It backs them up to /sdcard/initd_backups.

Anways check OP for the new updates in a few and enjoy!
[Captivate Android Development] ddoubt:
have you changed the kernel or just the init.d script files?
[Captivate Android Development] Jsmokey:
Mostly the init.d scripts specifically vm_lmk tweaks and the now renamed internal_mem_tweaks, I did a few minor tweaks inside the kernel itself but just very minor tweaks, not really much left any of us can do in the kernel itself without source for it, other than messing around with kh3's bootanim calls which I still can't get to work. It also has the addition of an init.d backup script in the .zip plus a few updates to the updater script.

The aggressive version is running pretty awesome though, what I did change made a pretty big improvement in how responsive it stays over time. It still has that small lag at start up but after running it most of the day I haven't got the slow filling up of the ram like it would before.

Also disk throughput has gone up more with the added tweaks I did to the file system schedulers in this version over the last one.

Edit: I just re installed for the hell of it after deleting the backup directory that my init.d backup script makes to triple check it was working and for some reason it isn't backing up now. I'm off to bed for the night, its 5:30 am here, so I'll fix it when I wake up. Just make sure to back up init.d still for right now till I get it straightened out.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] ddoubt:
hey Jsmokey, I took the liberty of making some changes in your script to fix the backup init.d procedure:

backup_initd.sh

#!/system/bin/sh

if [ -d /system/etc/init.d ]; then
mkdir /sdcard/initd_backup ##makes a backup folder to store user's scripts##
cp -R /system/etc/init.d /sdcard/initd_backup ##copies init.d to backup folder##
echo "init.d has been backed up."
else
echo "There is no init.d directory present."
fi

updater_script

ui_print(" ____________________________________");
ui_print("| + Installing... + |");
ui_print("| + -Red Nebula KJ3 Kernel- + |");
ui_print("| + -Clockworkmod- + |");
ui_print("| + By : Jsmokey + |");
ui_print("| + Source : Boog Kernel + |");
ui_print("|____________________________________|");
ui_print("");
ui_print("Mounting partitions...");
run_program("/sbin/mount", "/dev/block/stl9", "/system");
run_program("/sbin/mount", "/dev/block/stl10", "/data");
run_program("/sbin/mount", "/dev/block/stl11", "/cache");
ui_print("");
ui_print("Backing up current init.d scripts to /sdcard/initd_backups.");
package_extract_dir("scripts", "/tmp/scripts");
set_perm(0, 0, 0755, "/tmp/scripts/backup_initd.sh");
run_program("/tmp/scripts/backup_initd.sh");
ui_print("");
ui_print("Copying new init.d scripts by Jsmokey.");
delete_recursive("/system/etc/init.d");
package_extract_dir("system", "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/etc/init.d");
ui_print("");
ui_print("Cleaning caches.");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
ui_print("Caches wiped.");
ui_print("");
ui_print("Symlinking....");
show_progress(0.200000, 90);
symlink("/system/media/bootanimation.zip", "/system/media/sanim.zip");
ui_print("");
ui_print("Extracting package....");
package_extract_dir("updates", "/tmp/updates");
set_perm_recursive(0, 0, 0755, 0755, "/tmp/updates");
ui_print("");
ui_print("Flashing Red Nebula Kernel...");
run_program("/tmp/updates/redbend_ua", "restore", "/tmp/updates/zImage", "/dev/block/bml7");
ui_print("");
ui_print("Unmounting partitions...");
unmount("/system");
unmount("/data");
unmount("/cache");
show_progress(1.000000, 0);
ui_print("");
ui_print("Welcome to Red Nebula by Jsmokey.");
ui_print("Installation finished, please reboot and enjoy.");

well, that worked fine here for me! its only a suggestion ok, please mod your way, its your kernel and your script, I´m just meddling here :D
[Captivate Android Development] edtonn:
Been running v1.1 KH3 for a few days and noticed that after about 10-12 hrs uptime the launcher would redraw every time I either hit "back" or "home" back to the homescreen. Last night didn't happen until I started using Google Nav, but seems to happen every night.

Cleared cache/dalvik & flashed v1.1 KJ3 this morning, so I'll see how that works. Could the changes in the v1.2 update(s) help this issue? Running Pinnacle 1.3 for now.
[Captivate Android Development] Jsmokey:
Yeah the problem is the updater script, I have two copies stored in my kernel directory on my pc one with the extra lines necessary to make the script function and one that didn't. :facepalm.

The actually script should work fine as is, its just a different way of writing the check with a little different code layout, there's like 3 different ways to write shell scripts. Either should work though.

Thanks for pointing that out though it was.a late night and I was getting a little mixed up going back and forth between this and working on cwm.

@ post about redraw you'll probably want to try the aggressive version to see it helps, v1.2 just added a couple new tweaks and that was it.

The aggressive version will drop caches more frequently and has more aggressive lmk values.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] ddoubt:
I´m already on v1 aggressive! Its running fine.. I´ll tell more tomorrow!

UCKK1 just dropped... please have a look if your kernel runs along with it!

sorry for the meddling on your script!

EDIT: I´ve just changed swapiness to 70 and page cluster to 3 to test it out... the phone has started to lag on some apps (clock, calendar, etc) - RAM dropped to 50m
[Captivate Android Development] Jsmokey:
Yeah aggressive seems to be a lot smoother in the long run and I also noticed test scores are very, very similar after the first run. Managed to squeeze a few more hundred out in cf bench and disk scores went up a good chunk but they were always within 50-100 each run after the first warm up run, in antutu benchmark it actually never really varied more than about 10 points after the first run and it actually scored higher than a lot of cappy's running in the 1.4ghz range in the antutu score submissions.

I'll have to give it a look and see if it will work or not.

Its no problem, I'm glad you pointed it out so I realized what I did and its all part of why there's so many ways to write the syntax for shell scripts, I have almost all my background in Java, C, Python, and Pearl so the way I write it is just more natural to me and easier to remember. Other people would write it different and then there's a third group of people that use the other way to write bash scripts and those are usually strictly bash script programmers or that's what they learned as one of their first languages.

I really appreciate you pointing it out and after going back through the backup script I realized a lot of the problem is I was calling to have the directory made and the backup copied to /mnt/sdcard which doesn't work unless the phones actually booted up which was how I was originally testing if the script was working or not and forgot to change it when I put in the .zip.

I have to ask though why add:

ui_print("Unmounting partitions...");

unmount("/system");

unmount("/data");

unmount("/cache");

I was just curious why you added that, I've seen a few updater-scripts that do that at the end but not many. I just never have done it personally because most people reboot right after they install a new zip so I never really found it necessary.

Edit: Updating OP now with fixed versions for the init.d backup scripts give me a few and redownload if anyone wants to give it a try. Look for update-backup script fixed at the end of op to make sure you are getting the fixed version.