yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Kyuta Syuko:
I think the BLN module has only been compiled for I9000 kernels/ROMs and needs to be compiled for I897 kernels/ROMs or it just won't work. At least I haven't gotten it to work yet... (BLN App tells me the BLN mod is not installed despite the .so being where it's supposed to be.)
[Captivate Android Development] Jsmokey:
Most likely this is the case, I haven't really messed with bln though, I tried it out in andromeda and turned it off within the same day. Wasn't my cup of tea...lol
[Captivate Android Development] smully1:
Somehow I lost root when I flashed this? Anybody else experience this?
[Captivate Android Development] moore808:
I just experienced the same thing. Even reinstalling superuser didn't work.
[Captivate Android Development] prbassplayer:
Odd I'm using this kernel in a fusion beta build and I used it just fine on Fasty III. I used kernel flasher app, not odin if that means anything.
[Captivate Android Development] smully1:
It worked fine at first, but then I was rebooting and lost root???
[Captivate Android Development] Oxicottin:
I second that thought! :D
[Captivate Android Development] BitteredBro:
Hi MT.

I found something interesting. After installing your kernel over kyutas atutu benchmark gets stuck at the sdcard test (85%).

On another note, it didnt recognize my custom bootanimation.

I reinstalled kyutas kernel and the animation came back but no the capacity to complete atutu benchmark.

Quadrant works fine.

Enviado desde mi SAMSUNG-SGH-I897 usando XDA Premium App
[Captivate Android Development] mtcarey:
Hmmm... I put some extra checks in to make sure that root doesn't get messed up. For those still having problems with it, please indicate what you are flashing over (ROM/kernel) so I can figure out what's going on.
[Captivate Android Development] mtcarey:
BLN support needs to be compiled into the kernel, and Samsung has not released the source code for this yet.
[Captivate Android Development] mtcarey:
This checks for "bootanimation.zip" in /data/local or /system/media. Is that what you've got?
[Captivate Android Development] smully1:
Kyutra's kernel
[Captivate Android Development] Taderich:
Lost root as well. Was running kyutas kj3 kernel over stock rooted rom. Regained root by launching connectbot from market and ran

/system/xbin/su

Then deleted

/system/bin/su

As the superuser app only would refer to the /system/bin/su binary. Once it was deleted, I updated the su binary via the superuser app and all was as it should be.

I suggest deleting any su binary in

/sbin or /system/bin via shell script launched via the update script.

Might also test out symlinking the su binaries that were deleted.

All that said, awesome work on the kernel!
[Captivate Android Development] mtcarey:
I am now modifying my test to look for "/system/xbin/su", "/sbin/su", "/system/bin/su" or "/bin/su". I was previously only checking the first two. If it finds su in any of those places it will leave everything alone. There were more problems with an earlier version which attempted to move things around.
[Captivate Android Development] BitteredBro:
the zip file was in system/media on both kernels. Just replacing the kernel made it work.

Enviado desde mi SAMSUNG-SGH-I897 usando XDA Premium App
[Captivate Android Development] Jsmokey:
I am working on all this too and my updater script does symlink su but to xbin from bin and that hasn't gave me any problems. Haven't tried putting it in xbin and then symlink to bin though but should work the same in theory.
[Captivate Android Development] Kyuta Syuko:
bootanimation.zip shouldn't work if the kernel maker is using the binary that comes with Gingerbread as it'll only work with sanim.zip. At least that's how it was for me and everyone else who tried my kernel before I fixed it.
[Captivate Android Development] mtcarey:
New version 3.05 is out

Should fix all issues brought up over the last few days. Thanks for the feedback, and keep it coming!
[Captivate Android Development] matmanchu5:
Thanks for all your work

just had one little issue other than the ones reported. Im not sure that this is really an issue but I've been running the stock odexed Odin kj3 package and trussello's att kj3 and on both it seems that after flashing this kernel over kyutas my boot sound starts during a black screen a few seconds before the stock "S" animation. I don't think this was the case when I flashed your kernel while on FusionVIII. Is there any way I can get rid of the black screen or at least get the sound to coincide with the animation. Would flashing a different boot animation fix this?
[Captivate Android Development] msprag13:
Stock kj3 with boogs kernel for cwm. Flashed 305 and lost root.
[Captivate Android Development] papashex:
I ran into the same issue with 3.04. It's like the startup sound and then the startup animation play in sequence instead of together (with the screen banked during the startup sound.)

I did not flash over a previous kernel per se. I had rolled the files from 3.04 zip into the appropriate locations of my rom.zip and flashed the whole thing. Ran fine except for the startup issue. FWIW I also have lagfix disabled via voodoo directory on SD so conversion never happens.
[Captivate Android Development] simbill:
flashed 305 over 304 lost root

---------- Post added at 11:50 AM ---------- Previous post was at 10:58 AM ----------

i can attain root via terminal emulator by going into /system/xbin/su. and ADB is automatically su. would a "symlink" work between /bin/su and /xbin/su to get superuser up and running again? tried re-flashing 304 and doesnt fix it
[Captivate Android Development] mtcarey:
Could you do me a favor and look at your /sdcard/Voodoo/logs/<date-time-gmt-immediately-after-flashing>/voodoo_log.txt and look for the line near the end:

"secure su binary for Superuser apk now installed"?

If you already had root it should say "...already installed". If you see "now installed" then I'm still not detecting it properly. Thanks.
[Captivate Android Development] mtcarey:
I'll take a look at that. I have the start-up sound disabled, so I never noticed.
[Captivate Android Development] simbill:
Says already installed
[Captivate Android Development] tamanaco:
I was unable to disable Voodoo using the the Recovery menu of 3.05. I was having performance problems with Pinnacle 1.3 and decided to remove lagfix and re-flash Pinnacle 1.2 then 1.3, but in order to do it I had to go back to stock. After trying to disable it using the Recovery menu... the phone got stuck in a loop with the Voodoo voice repeating itself and the AT&T logo alternating with a black screen . I also tried clearing the cache, the dalvik cache and using the clear data (factory reset), but no matter what I did the phone when back to the endless loop. By chance I figured out that to get back to Recovery I had to press the Vol up + Vol Down key while the was in the black screen. From there, at least, I was able to put the phone in Download mode and flash back to stock using Odin.

Is the feature to enable/disable Voodoo from Recovery working in this Kernel? Should I use the Voodoo Control App or something else to enable/disable Voodoo?
[Captivate Android Development] mbc663:
ive been back and forth between rfs and ext a few times, using the voodoo control app each time with no problems
[Captivate Android Development] smully1:
I also lost root again on the new version.
[Captivate Android Development] mtcarey:
If that's the case it would have left it alone. It's possible that the execute permission gets changed at some point by accident... I'll put a check for that in and see if that finally solves these su problems.
[Captivate Android Development] mtcarey:
I just now used the Recovery menu to successfully go back to RFS, so I'm not sure what happened when you tried it. Did you originally convert to ext4 with a version of my kernel, or Kyutu's?
[Captivate Android Development] mtcarey:
Did you by any chance try to flash Pinnacle and convert to rfs at the same time?
[Captivate Android Development] simbill:
Is that something that could be fixed with a chmod? If so what numbers would I use? Remember I still have root access via /xbin/su. So its just /bin/su that superuser uses having the problem

I also updated busybox after flashing 305 could that be a cause?
[Captivate Android Development] mtcarey:
You should delete /bin/su. I'm not sure how it got there... definitely not from my kernel.
[Captivate Android Development] simbill:
That WORKED. Deleted it and after reboot had to update su binary file, granted it su permission nd got it.
[Captivate Android Development] mtcarey:
Good! I was trying to avoid having to manipulate multiple copies of su, but I think I'd better.
[Captivate Android Development] rayburne:
Didn't see if it's been asked/confirmed....does nandroid backup/restore work with this kernel?
[Captivate Android Development] Kyuta Syuko:
I was talking to existz about the version of recovery he uses in TalonDEV and according to what he said 4 and 5 have issues (to include nandroid) where as 3.0.0.5 (the version he uses in TalonDEV and I now use in my kernel since I'm using TalonDEV's recovery) works "perfectly".
[Captivate Android Development] mtcarey:
Yes, it works with this kernel! :)
[Captivate Android Development] -Thrive-:
Hmm. Lagfix got a little laggy. Converted back to RFS and running smoothly now. Strange since I always got good results from lagfix when on i9000 ROMs. No matter though because RFS works fine. Great to hear about Nandroid working. That alone is enough to keep me on this kernel.
[Captivate Android Development] mtcarey:
Hmmm... that hasn't happened to me - not sure what would cause that. That reminds me though... next version I'm going to add an option to turn-off journaling in ext4... not very safe, but should be interesting to see how much faster it is.
[Captivate Android Development] q659503934:
still have problem with 305 version (i flash tar version)

mount the USB storage it display this "E:Unable to open ums lunfile (No such file or directory)"
[Captivate Android Development] tamanaco:
I went from Pinnacle 1.3 with Boog's KH3 no lagfix to Corn Kernel KI1 (v1.01) with lagfix. Then I updated to Corn KJ3 (v3.05) with lagfix. I have not used a Kyutu kernel.

No, I was experiencing some lag, launcher restarts and phone freezes with Launcher Pro and Go Launcher EX and decided to remove Voodoo lagfix to see if the issue was related to the lagfix. In the past, after installing a few applications, I have found that I gain some performance back by disabling and enabling lagfix. I did that a couple times with Cognition (Froyo) with voodoo and had good results.

I'm back on Pinnacle 1.3 with Boog's without lagfix and I'm still experiencing performance issues with the launcher, but not as many launcher restarts or phone freezes. The launchers start fine, but after a while they take a little too long get back from a running application. You can see the icons populating the home screen. This delay issue is not as pronounced with voodoo lagfix. I'm now beginning to think that the launcher restarts and phone freezes might have been caused by something else. I just finished restoring my apps without data using Titanium and will probably re-install Corn Kernel with lagfix tomorrow and see how it goes.

Thanks...
[Captivate Android Development] mtcarey:
Just a shot in the dark, but are you sure you are on AT&T (Captivate) Gingerbread bootloader?
[Captivate Android Development] Kyuta Syuko:
I've been having this issue where if I install too many apps (not sure how many is too many just yet), or perhaps it's too many at once, my phone locks up and reboots... At first I thought it was the launcher not playing nice with the leaks, but then I started to realize it only happens after I install a bunch of stuff and most of the time the stuff that gets auto-moved to the SDCard doesn't show up properly if at all.
[Captivate Android Development] golfslicer:
Flashed over 3.05 lost root again and magic root doesn't help this time.
[Captivate Android Development] IceMonkey82:
I just flashed this (3.06) over Fusion IX and lost root. When I checked this file, it says:

<time> running extension: install_su.sh

<time> installing secure su binary for Superuser apk ...

<time> secure su binary for Superuser apk now installed

and in the init_log.txt I have:

+ find /voodoo/extensions/ -name *.sh

+ test /voodoo/extensions/sdcard_cleaner.sh

/voodoo/extensions/install_su.sh !=

+ echo /voodoo/extensions/install_su.sh

+ cut -d/ -f 4

+ log running extension: install_su.sh

+ indent=

+ test = 1

+ test = 2

+ date +%Y-%m-%d %H:%M:%S

+ echo 2011-10-18 12:04:37 running extension: install_su.sh

+ . /voodoo/extensions/install_su.sh

+ name=secure su binary for Superuser apk

+ binary_source=/voodoo/extensions/su/su-2.3.6.1-ef

+ apk_source=/voodoo/extensions/su/Superuser.apk

+ binary_dest=/system/xbin/su

+ apk_dest=/system/app/Superuser.apk

+ test -d /system/xbin

+ test -f /bin/su

+ test -f /sbin/su

+ test -f /system/bin/su

+ rm /system/bin/su

+ test -f /system/xbin/su

+ test /voodoo/extensions/su/su-2.3.6.1-ef -nt /system/xbin/su

+ extension_install_su

+ log Installing secure su binary for Superuser apk ....

+ indent=

+ test = 1

+ test = 2

+ date +%Y-%m-%d %H:%M:%S

+ echo 2011-10-18 12:04:37 Installing secure su binary for Superuser apk ....

+ chown 0.0 /system/xbin/su

+ chmod 777 /system/xbin/su

+ cp /voodoo/extensions/su/su-2.3.6.1-ef /system/xbin/su

+ test -f /system/app/Superuser.apk

+ chown 0.0 /system/xbin/su

+ chmod 775 /system/xbin/su

+ log secure su binary for Superuser apk now installed

+ indent=

+ test = 1

+ test = 2

+ date +%Y-%m-%d %H:%M:%S

+ echo 2011-10-18 12:04:37 secure su binary for Superuser apk now installed

+ echo /voodoo/extensions/sdcard_cleaner.sh

---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------

I also looked for the /system/etc/init.d that was specified in the OP and I could not find it. It may have been removed from the latest Fusion.
[Captivate Android Development] ScottyNuttz:
I flashed over whatever kernel comes with Pinnacle 1.3 and lost root also.
[Captivate Android Development] mbc663:
lost root going from 3.05 to 3.06 ;///
[Captivate Android Development] -Thrive-:
Right after I reverted to RFS because of laggyness, I noticed that a couple of TIBU restores that I did the day before went to the external SD card. I usually check this and move them to the phone but forgot this time. I have a suspicion that this is what caused my lag so I am going to convert back to EXT4 to check it out. It is so annoying that GB or TIBU or whatever is defaulting installs/restores to external SD card. Maybe EXT4 doesn't play well with apps on external SD card?
[Captivate Android Development] rayburne:
Flashed Corn 3.06 over top of stock Pinnacle 1.3 - Lost Root.

Flashed Samurai-1.1 from CWM and got Root back.

Re-Flashed Corn 3.06 over top Samurai and Root stuck.
[Captivate Android Development] mcx6:
I believe that it is TIBU default setting of "restore backups to" in TIBU Preferences is set to Default Location and it need to be set to Internal storage. To get to it in TIBU, hit Menu, then Preferences, scroll down to Restore backups to, then select Internal storage before you restore your applications.
[Captivate Android Development] tamanaco:
I think so... I used the KF1_bootloaders.exe that I downloaded from the Pinnacle thread to install the GB bootloader.
[Captivate Android Development] -Thrive-:
Thanks. Didn't know that. Too many apps, too many settings, too little time. :D
[Captivate Android Development] tamanaco:
Hmmm, I also have a bunch of apps, but I was not having these issues while using Cognition (FROYO). When I restored the 3rd party apps using Titanium I noticed that some apps installed (restored) into the SD Card which were not there before. I don't know exactly which ones. I'm sure Pandora was not in the SD Card prior to the restore, because after the restore I could not find Pandora listed under widgets. To fix it, I moved Pandora from the SD Card (USB Storage) to the Phone (Device). My understanding is that apps with widgets should not be installed in the SD Card. Are there any other type of apps that should not be installed in the SD Card? Are there some apps that should be not be installed in the Device?... As I said before, in the past, after installing a few apps on a ROM with lagfix I start to experiencing lag. I was able to gain some performance back by removing and reinstalling Vooodooo lagfix. Does anyone know if there a limitation on the number of apps or on the size of the partition that one can have with Voodoo lagfix?
[Captivate Android Development] mbc663:
Thanks for the heads up, got it back with samurai, gonna try this again...

EDIT: didnt stick for me
[Captivate Android Development] tamanaco:
I didn't read this before my last post... In my phone Tibu is set to Restore backups to... "Default location (chosen by Android)". Does Android get info from the Apps' installation process to chose where the app is going to be stored? (Device, SD Card or External SD)... If this info comes with the App, maybe it can be determined with "some" tool where the app(s) requires that it be placed..

Edit: I'm going to try moving most apps (except games and the such) to the device internal memory and see what happens.
[Captivate Android Development] Jsmokey:
I've had this problem with recent versions of pandora no matter where it installs on my own rom and kernel with or without lagfix, usually reinstalling works to get it back in widgets not sure what the deal is with it but it's done it everytime and I'm using an older version with transparent background mod tried a few other backups I have of it and it does the same thing.

Mtcarey, for now why not pull the su installer part from the kernel and let everyone know they need root before hand that way you can keep working on that part without the trouble of helping fix so many cases of people breaking root, the onix kernels and a few other older ones have some really good su installer bash scripts included you can refer to to help figure this out btw. If you want I can decompile corn kern and take a look and see what I can find that could be causing the root issues, not trying to step on your toes just wanting to lend a hand cause I know this has to be driving you crazy.
[Captivate Android Development] mbc663:
gonna have to stick with Samurai until i can get root back on this. Ive tried everything, cant obtain it.
[Captivate Android Development] Boldizzle:
Same here.
[Captivate Android Development] mtcarey:
Root

I've tried just about every Superuser install script out there, and every one breaks something for somebody. I think I will do separate versions with and without installer. Kind of a pain, but might be the only way to get rid of this problem! :mad:

Update: Done! Separate versions now available.
[Captivate Android Development] mtcarey:
For sure apps with widgets need to be on internal storage, not sd. Android's "AppWidgetManager" requires it. As far as gradual laggy-ness with ext4, I haven't seen it myself, but I'll look into it. Usually creeping lag is due to a memory leak in something. I definitely had it with an earlier version of the Talon kernel, and since UCKJ3 is essentially a beta from Samsung, I wouldn't rule it out here.
[Captivate Android Development] -Thrive-:
Question. If I have 3.0.4 installed and root working and want to upgrade to 3.0.6, which version should I flash to avoid problems? Will the version without root leave my working root intact or will it wipe it requiring me to install root separately?
[Captivate Android Development] mtcarey:
If you already have working root, use the version without the SU installer.
[Captivate Android Development] Boldizzle:
Is there any real advantage to using this kernel over Samurai?

I'm just running Pinnacle 1.2 and am currently using Samurai until the root problem gets fixed with this Kernel but then if there's not really any discernible difference between the 2 then I'll just stick with Samurai from here on.
[Captivate Android Development] mbc663:
Awesome work man, your quick fixes and work is much appreciated. Flashing the non su now, will report back shortly.

EDIT: had root on Samurai, flashed the non su .06, lost it again ;//
[Captivate Android Development] mtcarey:
The main differences between this kernel and Samurai are:

- Samurai has various kernel, vm, and tcp tweaks built in. Corn Kernel leaves these settings stock, and let's you tweak them through sysctl.conf and init.d as desired.

- Samurai leaves lot's of CWM bits in memory (ram disk) after booting... Corn Kernel gets rid of them to save a few megabytes.

Otherwise, they are pretty much the same.
[Captivate Android Development] mtcarey:
Arghhh....

I'll take a look at this and Samurai to see what's going on.
[Captivate Android Development] mbc663:
hate to break the news to you bro...

u gotta be pullin ur hair out by now
[Captivate Android Development] Boldizzle:
Thanks for that. Good to know!

:)
[Captivate Android Development] mtcarey:
What hair?!

OK... the "without root" link now points to a "-2" version which is slightly modified. I flashed Samurai then flashed this one and kept root. Give it a shot!
[Captivate Android Development] mbc663:
Was hoping u weren't bald! Thanks again, will report back in a little
[Captivate Android Development] mtcarey:
Just kidding... I have hair, but I have been pulling it out!
[Captivate Android Development] Jsmokey:
Haven't had time to pick your kernel apart but how exactly is it installing su, every updater script I have I checked to see how it installs su and it puts it in bin and symlinks it to xbin then chmods them both and if I remember correctly only chown's the one in bin and none have ever gave me issues installing this way also the default for how dsixdas kitchen sets it up. Thats also how I've been doing it with my kernel without any problems with root.

The only other way I've seen it done is calling a bash script from the updater-script but the bash scripts always do it that way too just allows for more control in the checks to see if su is already in place.

Has anyone thats having these issues tried checking the permissions on su? Sometimes the script can mess it up and you dont even realize till after checking.

Just trying to help you narrow things down mtcarey. I really hope you get this straightened out I know it's driving you insane especially when it's working fine for you.
[Captivate Android Development] Kyuta Syuko:
The first difference that comes to mind is my tests are done with the -u flag rather then the -f (Voodoo thing). Second thing that comes to mind is that I remove all instances of su that aren't in xbin and don't install the Superuser.apk (due to lack of space). Also have it posted to clear Superuser's data if they lose root. Hope that helps.
[Captivate Android Development] mtcarey:
Actually, the "-u" flag just checks for the file's existance with the suid set. The "-f" flag just checks for existence period. It's a Bourne shell command... not related to Voodoo. My script also checks everywhere just like yours. The only relevant difference is that I haven't asked anyone to clear Superuser's data... I'm trying to solve this without manual intervention. :D
[Captivate Android Development] Kyuta Syuko:
Yeah I know the what the -u flag is/does which is why I put "Voodoo thing" in () because I'm not sure what kind of benefits there are to using the -u flag vs the -f flag if any, and yeah I totally understand wanting to make things as easy and convenient for the user as possible.
[Captivate Android Development] golfslicer:
I flashed with root and lost root, flashed samuari and magic root wouldn't work, flashed samuari and got root back, flashed this without root and lost root again, flashed magic again and got root back. I suspect that if I was to flash it again, but don't need to, I would lose root again and wouldn't be able to get it back without first flashing samuari kernel?
[Captivate Android Development] IceMonkey82:
I just installed the No Root CWM installer over Fusion IX and lost root.