yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Kyuta Syuko:
So custom boot animations are working for everyone else? As in the one you're loading into your phone is playing and not just the basic Android one.
[Captivate Android Development] Wdustin1:
ok i have a question hopefully somebody with way more knowledge than me can jump in here and answer. so ever since GB has leaked for the captivate we have been told not to do a nandroid restore because it will brick your phone. Now we have Voodoo support, from what i can tell voodoo does a backup then deletes all data, redoes the system to EXT4 then does a RESTORE, so should there be some concern in doing this? also if it is running just fine on the restore part why cant we seem to fix the normal restore through CWM? just a few questions?
[Captivate Android Development] Kyuta Syuko:
The way Voodoo does it is that it copies/moves everything to your SD Card then formats the partitions into ext4 and moves everything back. So it's just a simple Copy/Cut and paste. Nandroid on the other hand does other things such as compressing everything so it's smaller. I don't know much about Nandroid backups so I don't know what all it does, but something it does is broken and thus shouldn't be used until it's fixed.
[Captivate Android Development] golfslicer:
FYI: Running KJ3 Kernel and modem on KI2 Rom and running fine.

I did flash and install lagfix with Boogs Kernel first with lagfix which took about 10 minutes. I then just flashed this kernel via odin booted and made the changes to voodoo on the first page, not sure what they do, but Quadrant score was a little better.

Running Tegrak at 1.2

Quadrant with Boogs lagfix 2559

Quadrant with K3 kernel 2841

Quadrant with zipalign in voodoo 2950

Current LinPack Score first run 20.818 second time 21.149 3.96 seconds

Overall the K3 kernel is faster than KI1 both with lagfix and I like that CWM is back to version 4.
[Captivate Android Development] mbc663:
Running a pretty similar setup. Oc, lagfix, only for the past couple days. How's battery life compared to pinnacle?
[Captivate Android Development] Kyuta Syuko:
The /voodoo folder houses all the voodoo files from the kernel. Might make a script to clean it up in the next release since I don't think it's used after boot.

As for wiping battery stats it's a good idea to do it, but I don't think it's needed.
[Captivate Android Development] axeman007:
I'm using Illiminance 2.1.1 (KK2) . Can I flash Samurai 1.4 on this? Which flash method do you suggest?
[Captivate Android Development] ln100:
I flashed Samurai 1.4 via CWM on Illuminance 2.1 (KK2) w/ no problems.
[Captivate Android Development] BitteredBro:
I flashed Samurai 1.4 via CWM on Pinnacle 1.3 (KH3). Everything working fine except Voodoo Control. The kernel doesnt support extendend sound controls said. I dont think its kernel related because the same message apeared using Red Nebula.
[Captivate Android Development] tamanaco:
I'm currently using Illumainance 2.1.1 with Samurai 1.3. I was about to update to 1.4, but just noticed the post regarding the Voodoo Control App. I use the paid Voodoo Control App every day (Voodoo Sound). Can someone verify that Voodoo Sound does not work with Samurai 1.4?

I have also noticed that the Voodoo Sound "Map Volume Keys hack" option does not work as smoothly as it used to work with FROYO ROMs and Kernels. It still works on GB ROM and Kernels, but the phone volume bar and the Voodoo volume bar are no longer in sync. Has anyone else noticed this?
[Captivate Android Development] -Thrive-:
In my experience, Voodoo Control Plus always stops working when I flash a new kernel. Each time I kill VCP, wipe data, and restart VCP. This forces it through the setup again and always works after that for me. YMMV but you might as well try it because it is so easy to flash back to your prior kernel if it doesn't work.

Edit: Just tried the Map Volume Keys Hack. When I reduce the volume, the media volume bar lags but if I keep going, it starts moving again in sync with the Voodoo volume bar.
[Captivate Android Development] ddoubt:
hey kyuta, your sql_optimize script uses sqlite3 binary, right? is it included to your kernel or I must have it on a specific path?
[Captivate Android Development] Boldizzle:
I also use Voodoo Control Plus and I can confirm that it works fine with Samurai 1.4 running on Illuminance 2.1.1.
[Captivate Android Development] BitteredBro:
Hey! Thanks button pressed.

Even tough I rebooted the phone several times, the aplication refused to work and now it does. Kyuta and Jsmokey do such a clean work that I knew the error couldnt be kernel related!
[Captivate Android Development] sfernandez:
Everything is working fine here. No issues at all.
[Captivate Android Development] jjbarisax:
I am on stock KK4, Samurai 1.4 kernel with the paid Voodoo Control app, no problems. When you reboot, was the voodoo ctrl app granted su permissions successfully?
[Captivate Android Development] Kyuta Syuko:
The best method to flash (either Odin/Heimdall or recovery) is whichever you're most comfortable with. Sometimes recovery doesn't flash properly and Odin can be a pain. I personally prefer Heimdall via Kubuntu or Ubuntu (depending on if I'm on my laptop or my PC) as it's never failed me.

You know... I knew I forgot something...

While I appreciate the complement I don't really do much...
[Captivate Android Development] jjbarisax:
your too modest - the samurai kernel is rock solid.
[Captivate Android Development] -Thrive-:
That may be the "root" of the problem LOL but I'm not sure how to confirm it or resolve it. When I wipe Voodoo Control data, one of the things it does is ask for root permission during the new setup. I am using ChainsDD Superuser v 3.0.7. Voodoo Control Plus shows up in its list of apps allowed. Not sure why changing kernels would mess this up. Any ideas?
[Captivate Android Development] Kyuta Syuko:
Were you on Samurai or a different kernel? If you were on a different kernel it could have been because I check for any and all instances of su and remove any not in xbin and whatever kernel you were on before might have installed it somewhere else and thus Superuser might have gotten confused for a bit.
[Captivate Android Development] -Thrive-:
Good to know. I have used all three of these kernels (yours, Corn, and Red Nebula) at different times. This issue with Voodoo Control Plus keeps coming up in the different threads. Removing instances of su may be the source of the problem but its not a big deal for those of us who like to flash kernels a lot because the work around is very easy if you know about it. But it can be frustrating for users who don't.
[Captivate Android Development] Kyuta Syuko:
Yeah well that's what you get when you flash multiple things from different people because each person has their own idea on what's better (mine's the best of course) and thus conflicts sometimes arise.
[Captivate Android Development] ddoubt:
so... if I have a copy of sqlite3 on /system/xbin will your "enable-sqlite-optimize" work? also how does your enable-zipalign work? is the zipalign binary included into your kernel also?
[Captivate Android Development] BitteredBro:
My sqlite3 it's in system\bin not xbin. It's that right?
[Captivate Android Development] Kyuta Syuko:
Because of when the script is run I'm not sure it will work or not due to /system being mounted or not. You can try it and then check the init_log.txt in the /sdcard/Voodoo/logs/very_last_folder near the bottom to see if it gives an error about sqlite3 missing. I've fixed it in the kernel I'm working on so the binary is there. I've been trying to get a cache fix in there too, but the busybox that's in the kernel now doesn't have losetup and there's not enough room to put the only one I have access too that does... So I'm reverting those changes and I'm about to pack a kernel with the sqlite3 binary.
[Captivate Android Development] Kyuta Syuko:
Ok added 1.4.1 w/missing sqlite3 binary to OP.
[Captivate Android Development] Kyuta Syuko:
I've made some progress on the sqlite optimization. It's now running, but it's giving me "unable to open database file" errors. Probably permission related.
[Captivate Android Development] Kyuta Syuko:
Another update. I've managed to get it to work with the exception of the db files on the sdcard giving me the error "Error: attempt to write a readonly database" and that's after chmodding the file to 776...
[Captivate Android Development] Kyuta Syuko:
Got the sqlite optimize script working OP has been updated!
[Captivate Android Development] Xx-Ness-xX:
Just one quick question, can I use kernel 1.4 on UKK2?
[Captivate Android Development] Kyuta Syuko:
You should be able to. All the leaks have been compatible kernel wise.
[Captivate Android Development] Jsmokey:
Yep can run kh3 rom with a kk4 kernel if you really wanted to. Really theres no discernable difference in the kernels till we get an actual kernel revision.
[Captivate Android Development] Xx-Ness-xX:
Thanks, and once I flash the kernel I would have to reflash the LMK setting again right?

Sent from Samsung Captivate
[Captivate Android Development] Kyuta Syuko:
if it's an init.d script there should be no need since the updater script doesn't remove them.
[Captivate Android Development] diakonos:
Does using sgs-kernel-flasher to flash the 1.4.2 version "run the script" you are referring to?
[Captivate Android Development] Kyuta Syuko:
No. You have to put a file in the /sdcard/Voodoo folder and reboot to run the sqlite optimize script. It's in the change log but I'll update the OP to make it easier to find.
[Captivate Android Development] tmusall:
sqlite optimize problem

I'm still getting errors when enabling sqlite optimize. Here's the log for the first db it tries to optimize:

+ log running extension: sqlite_optimize.sh
+ indent=
+ test = 1
+ test = 2
+ date +%Y-%m-%d %H:%M:%S
+ echo 2011-11-27 15:27:49 running extension: sqlite_optimize.sh
+ . /voodoo/extensions/sqlite_optimize.sh
+ CHECK_FILE_SQLITE=/sdcard/Voodoo/enable-sqlite-optimize
+ sqlite3=/system/xbin/sqlite3
+ libncurses=/system/lib/libncurses.so
+ test -e /sdcard/Voodoo/enable-sqlite-optimize
+ test -x /system/xbin/sqlite3
+ test -x /system/lib/libncurses.so
+ mv /voodoo/extensions/sqlite/lib/libncurses.so /system/lib/libncurses.so
mv: can't create '/system/lib/libncurses.so': Read-only file system
+ find /data -iname *.db
+ find /dbdata -iname *.db
+ find /sdcard -iname *.db
+ tempdb=/tmp/ApplicationCache.db
+ mv /sdcard/miren_browser/.cache/databases/ApplicationCache.db /tmp/Application
+ chmod 776 /tmp/ApplicationCache.db
+ /system/xbin/sqlite3 /tmp/ApplicationCache.db VACUUM;
link_image[1963]: 721 could not load needed library 'libncurses.so' for '/syst
^@+ /system/xbin/sqlite3 /tmp/ApplicationCache.db REINDEX;
link_image[1963]: 722 could not load needed library 'libncurses.so' for '/syst
^@+ chmod 770 /tmp/ApplicationCache.db
+ mv /tmp/ApplicationCache.db /sdcard/miren_browser/.cache/databases/Application
+ tempdb=/tmp/GeolocationPermissions.db
[Captivate Android Development] Kyuta Syuko:
That's strange. You using RFS or EXT4? Anyone else having issues with the sqlite script? If so what file system are you using?

A work around this issue until I can figure out why your /system is mounted ro on boot-up while mine's rw on boot is to put the /voodoo/extensions/sqlite/lib/libncurses.so into /system/lib manually.
[Captivate Android Development] tmusall:
My system partition in formatted RFS.
[Captivate Android Development] Kyuta Syuko:
Alright well I'll see how many more chime in with this error and see if they're all on RFS as well.

Did you try putting the /voodoo/extensions/sqlite/lib/libncurses.so into /system/lib manually and rerunning it?
[Captivate Android Development] tmusall:
Yeah that allows sqlite3 to run, but on every database it errors out with unable to open database.
[Captivate Android Development] Kyuta Syuko:
I figured it'd do that. Just have to figure out why. Would be nice if others would chime in with this problem as well as the file system they're using.
[Captivate Android Development] diakonos:
I added all three of the "enable" files ("enable-zipalign-system," "enable-zipalign-data," and "enable-sqlite-optimize") in the Voodoo folder and restarted my phone. I haven't noticed any odd behavior on restart. I am running KK4 RC6 and your 1.4.2 kernel on EFS. Where would I see errors (if there were any)?
[Captivate Android Development] sfernandez:
+1 I applied all 3 an no errors. Im running RFS on Fusion
[Captivate Android Development] Kyuta Syuko:
There are logs stored in a new folder per boot so it's easier to find if it was the most recent boot that it was done during as it'll be the last folder in /sdcard/Voodoo/logs and the file you want to look at is called init_log.txt. What you'll want to look for will be near the bottom.
[Captivate Android Development] sfernandez:
ooh I see what your talking about yea i got error on enable-sqlite
[Captivate Android Development] Kyuta Syuko:
Well here is a kernel I've hopefully fixed the issue with. If you could try it out and then copy and paste or upload or whatever the sqlite_optimize.sh part of the init_log.txt here or in a PM to me it would be greatly appreciated.

http://dl.dropbox.com/u/15795752/Samurai-1.4.3β.tar

If you need a CWM flashable zip you can just take the zip from the OP and replace the zImage in it with the one in this tar.
[Captivate Android Development] sfernandez:
I flashed the1.4.3 kernel,and still getting the error. Here is the init_log.txt. If you want me to flash anything else or tweak anything let me know
[Captivate Android Development] Kyuta Syuko:
Thanks. I'll have something else for you to flash once I get off work and put it together.
[Captivate Android Development] tmusall:
Those where the same errors I got with 1.4.2.
[Captivate Android Development] Kyuta Syuko:
I'm having a bit of an issue with one of the checks. Once I get that worked out (whenever I get it worked out) I'll post the update.
[Captivate Android Development] EthanMG:
im wanting to flash stock kk4 and then this kernel, but im confused on how to root after that point. in the op it says to simply download superuser from the market, but in the stock thread, they say to use the fugu root method. id prefer to just download the apk, as that would be easier. can anyone clarify?
[Captivate Android Development] ddoubt:
hey kyuta, I'm about to update serenity, has the sql optimization been fixed? Which version should I update? 1.4.2 or 1.4.3b? Is there a 1.4.4 :D ?
[Captivate Android Development] Kyuta Syuko:
sqlite optimization works for ext4. I'm having an issue getting it to work with rfs for some reason. So far everything I've tried hasn't worked, but I have a few more things left to try.
[Captivate Android Development] rajendra82:
You don't need to flash fugu, once a kernel like Samurai, with CWM recovery is available. What I did was Odin flash KK4 (which made me lose ROOT). Then I Odin flashed Samurai. Then I flashed the CWM zip file you can download from the xda page about the Superuser app. You also have to install busybox from the market after root.

This approach avoids having to flash fugu root and then deal with the outdated su binary and busybox it contains.
[Captivate Android Development] Kyuta Syuko:
Didn't notice your post before. Was in a hurry. As mentioned above most custom kernels will install the su binary and usually the Superuser app, but there wasn't enough room for the app which is why you'll need to download it from the market as well as Busybox.
[Captivate Android Development] EthanMG:
thank you!

---------- Post added at 09:13 AM ---------- Previous post was at 09:11 AM ----------

thank you!
[Captivate Android Development] sfernandez:
Just flashed the 1.4.3B on RFS and no errors at all. Here is my init_log. Ill even upload the zip i used also. Sorry took so long just noticed the b version.
[Captivate Android Development] Kyuta Syuko:
While I appreciate the help the kernel itself isn't causing issues/errors it's the sqlite optimize script which wasn't run. You can check the first post for more info about that.
[Captivate Android Development] Kyuta Syuko:
Ok I think I've managed to squish the sqlite optimization script issue and got it working with rfs as well. Here's a beta kernel to test. Again make sure the enable-sqlite-optimize file is in Voodoo when you boot after flashing and post the init_log.txt for that boot. Thanks.

http://dl.dropbox.com/u/15795752/Samurai-1.4.3β2.tar
[Captivate Android Development] sfernandez:
here you go..let me know if you need anything else.
[Captivate Android Development] Kyuta Syuko:
That's perfect thanks!
[Captivate Android Development] Kyuta Syuko:
Just found an issue in the Beta I just posted with the sqlite optimize script that will cause ext4 users to bootloop. Issue has been fixed already and will not be present once the kernel is released. The betas have been primarily for those using RFS.
[Captivate Android Development] Kyuta Syuko:
And now 1.4.3 is live! Please post in the thread with any issues. Thanks.
[Captivate Android Development] IlluminatedOne:
You didn't change the thread title and details?
[Captivate Android Development] Kyuta Syuko:
Tired, forgot lol

I also decided to flip the change log so people wouldn't have to scroll to see what's been changed.
[Captivate Android Development] EthanMG:
what is the best way to get busybox? there are multiple options for it on the market, not sure which one is the right one. (i see a 'busybox', a 'busybox installer', and im pretty sure titanium will install it for you as well) any suggestions?
[Captivate Android Development] IlluminatedOne:
I prefer this one.
[Captivate Android Development] Kyuta Syuko:
I second that one. Granted I have the paid version. Didn't realize there was a free version till it was too late, but it's always good to support devs.

Maybe tomorrow I'll add the web market links for Busybox and Superuser in the OP.
[Captivate Android Development] blutruck:
Question

From the OP:

To enable the various scripts:

On your internal sdcard is a folder called "Voodoo". Inside this folder, create a blank file accordingly and then reboot:

"enable-zipalign-system" to enable zipalign for /system/app

"enable-zipalign-data" to enable zipalign for /data/app

"enable-sqlite-optimize" to enable the modified sqlite optimize script from ThunderBolt by pikachu01.

The file to be created; is it to be an empty folder or a text file named for the above?
[Captivate Android Development] hokiemoto:
Never looked at the init_log.txt before, but I see a lot of

syntax error: unexpected "("

Is that okay?

(voodoo_log.txt says sqlite optimize completed though)

I'm trying out 1.4.3 Thanks
[Captivate Android Development] sfernandez:
here is all 3 I put in zip..NOT Flashable just extract it and add what ever script u want 2 use
[Captivate Android Development] Kyuta Syuko:
Empty File.

That's a strange issue there. You on ext4 or rfs? Anyone else noticing these errors in their init_log.txt? When sqlite optimize is run by itself or when it's run with the zipalign script?

*edit* Yeah I didn't get it running the sqlite optimize script with zipalign for system and data. Try deleting the sqlite3 binary out of system/xbin and trying it again with the zipalign script and see if you still get the errors. Make a back-up of the sqlite3 binary first just in case.
[Captivate Android Development] hokiemoto:
On ext4. I flashed kernel with CWM, rebooted, then created the 3 script-enabling files all at the same time, then rebooted.
[Captivate Android Development] Kyuta Syuko:
This should be unrelated to your issue, but do/did you have a /system/etc/init.d.old directory? Just want to see if the new updater-script performed as expected.
[Captivate Android Development] hokiemoto:
Yes, I do have that directory.

Regarding your instructions to try again, which do you mean for me to do after deleting sqlite3.... the two zipaligns for data and system? or the sqlite optimize?
[Captivate Android Development] Kyuta Syuko:
Whatever you did and got those errors (I think you did all three based off your log)
[Captivate Android Development] hokiemoto:
Cool - now I see a bunch of VACUUMs and REINDEXs and no errors :)

voodoo_log.txt still shows SQlite optimize completed just like before.

BTW now the /system/xbin/sqlite3 file is about a quarter of the size of the backed up one. (not sure what that means)
[Captivate Android Development] hawkzq:
i flashed the 1.43 ,but i do not have a /system/etc/init.d.old directory what is the reason?
[Captivate Android Development] Kyuta Syuko:
Did you have a /system/etc/init.d directory before you flashed it? As stated in the Change Log I modified the updater-script to rename the /system/etc/init.d to /system/etc/init.d.old to eliminate any complications the scripts in the init.d directory might cause rather then just deleting a select few. So of course if you didn't have a /system/etc/init.d directory before flashing then there's nothing to rename, and it only happens with the recovery flashable zip.
[Captivate Android Development] Kyuta Syuko:
Good to know it was the binary that was causing the issues like I thought. Where did you pull the backed up binary from?

As for the "sqlite optimize completed" in the log it'll always show that to show the script finished running. Be it successful or not.
[Captivate Android Development] hokiemoto:
I just renamed the old one (whereever it came from) with ".bak" and compared the two side by side in root explorer.
[Captivate Android Development] tamanaco:
Quick question... in Voodoo Control Plus is there an option to disable logging? I never looked in the Voodoo Log folder and I just noticed that I have a bunch of dated folders with log files in them. I guess they're created by Voodoo every time I boot. Shouldn't this logs only be created when the debug option is enabled?
[Captivate Android Development] Kyuta Syuko:
No those aren't debugging logs they're just normal boot logs and as far as I know there's no way to disable them. Of course I could go through every script and add in a way if more people would prefer that.
[Captivate Android Development] mbc663:
After 2 weeks on corn, I'm coming back to samurai. For some reason i get an extra hour screen time on samurai. Thanks again. Corn cwm doors rock though!
[Captivate Android Development] Kyuta Syuko:
Well I tweaked some of the settings in the new Samurai Kernel so hopefully those don't negatively affect your screen time.
[Captivate Android Development] mbc663:
I'll be sure to let u know sir
[Captivate Android Development] jswclw:
Just wanted to say I'm running Illuminance and upgrade from 1.4.2 to 1.4.3. It is a marked improvement. Before it would not play music in the background, behind navigation usually. Now, no problem. Good work!
[Captivate Android Development] Kyuta Syuko:
Well there are still a few settings I have tweaked that I'm still trying to find optimal settings that won't be too aggressive that it closes programs that you're using or too lenient that it causes your phone to lag after a while. Kind of hard when I'm not much of a multi-tasker. Not to mention I'm still learning.
[Captivate Android Development] 4-2ndtwin:
Kyuta Syuko, I appreciate as well ur work here and the continual work u do for this kernel. Just wanted to show my appreciation. Really glad for the work that u and the other Devs do and the time that ya'll put in.
[Captivate Android Development] EthanMG:
off topic for this thread, i apologize, but what is the option to custom tune when you use this installer?
[Captivate Android Development] Kyuta Syuko:
It's not an installer. It's a stand alone OC/UV app. The custom tuning is done under the first option Optimize.
[Captivate Android Development] EthanMG:
i was referring to the busybox you both suggested i use from the market. it is an installer for busybox, and it offers a custom tune option when you install. dont know what it is.
[Captivate Android Development] Kyuta Syuko:
Sorry was reading from my phone and some how Tegrak got in there... The custom tune option allows you to choose to not install some components or to install others from the busybox even though the system already has them installed. I would just ignore it unless you know what you're doing.
[Captivate Android Development] EthanMG:
thank you! =D