yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Stevenrogers_420:
I feel stupid for asking but do I need to zipalign more than once? Meaning must I zipalign for every reboot? I assume no. But you know what happens when you ASSume...
[Captivate Android Development] xpakage:
That is true but I was answering the question if the phone turned on as soon as it was plugged in, which mine does not. It's just "normal" :p
[Captivate Android Development] Kyuta Syuko:
It's ok to leave it enabled. The script checks if the apk is zipaligned before it zipaligns it. If it already is then it just skips it. Granted after the first zipaligned boot you'll probably want to disable it for system since that folder doesn't change much if any, or not even enable it for system if you're already on a zipaligned ROM. It's more for stock rom.
[Captivate Android Development] Ikonomi:
Ha, I like the name. :)

Sent from my thing with the thing
[Captivate Android Development] Stevenrogers_420:
The file I added disappears after I reboot. Was just making sure. Thanks!
[Captivate Android Development] Kyuta Syuko:
Just uploaded 1.1. Nothing too big. Just changed to TalonDEV's 3.0.0.5 recovery due to issues with v4 and 5 (backing up and restoring should work) and added su binary install. All you have to do is download Superuser.apk from market to get root.
[Captivate Android Development] xpakage:
Should we disable lagfix if upgrading from Samurai 1.0?

EDIT: I disabled it to be on the safe side. All is well and back on EXT4.
[Captivate Android Development] silverslotcar:
No u don't have to.
[Captivate Android Development] Kyuta Syuko:
When changing kernels going from one lagfix to the same lagfix there's usually no need to disable it. When going from one lagfix to a different lagfix or to no lagfix then you'll need to disable it.
[Captivate Android Development] matmanchu5:
I know this kernel supports init d but after flashing I have no init d folder are there no init d scripts included with this kernel?

EDIT: Nevermind that I just flashed 1.1 and when i boot into recovery it checks every thing done! and then It has:

E:cant mount /cache/recovery/command

E:cant mount /cache/recovery/log

E:cant open /cache/recovery/log

E:cant mount /cache/recovery/last_log

E:cant open /cache/recovery/last_log

but everything seems ok, other than that i cant mount cache, wipe cache and whenever i "go back"

in recovery i get the same cache error. I have flashed with both odin1.85 and cwm and i get same error even after going back to stock kj3 and redownloading and reflashing samuri1.1 using odin.....

OMFG WTF is going on here? stay calm, stay calm.....ok

could this be my phone dying?

To answer my own question, No I flashed back to Samuriv1.0 and all is well.......... Phew!

I wonder what might have caused this. I dont think its my phone although i could definitely be wrong.

i must be the first to flash this kernel, or i've done something to cause it. Who knows anyway my phone isnt dying so thats good. :)

by the way the timestamp is wrong its 10:54 Am where im at
[Captivate Android Development] boog:
It's only means cache wasn't auto mounted in recovery, so it couldn't read the /cache/recovery folder. I wouldn't think it would be a problem.
[Captivate Android Development] matmanchu5:
Im sure youre right. But things like that scare the heck out of me because the last time i saw "cant mount" was when i formatted everything and accidentally hit reboot wich only reqired flashing back to stock but i was kicking myself hard because ive been using my freinds computer wich i didnt have access to at the time. Still, though i've never seen it do that which makes me think something might not be quite right. Did you try flashing Samurai v1.1 to see if you get the same error? There must be some reason. Wierd, just....wierd.
[Captivate Android Development] boog:
Nope, I haven't tried his kernel yet (though I have looked inside it), but I have played with the recovery from talon and saw the same error. If you manually mount cache the error stops. I am guessing it could be fixed in recovery.rc.

All of this is starting to spark my curiosity, I may have to try his kernel, then building something on top of his kernel.

@Kyuta Syuko, we may have to collaborate, I need to figure out a bit more on android bootable recovery, but I have the environment set up to compile. And after looking closer at your kernel and mtcarey's I have a couple things I want to try, not sure if they will work, but I want to try anyway lol.
[Captivate Android Development] Soy_Filipo:
Why rom manager isn't working with this kernel? Is asking me to install cwm when it's actually installed

Enviado desde mi SAMSUNG-SGH-I897 usando Tapatalk
[Captivate Android Development] boog:
Because there isn't a Rom Manager Official version. You should be able to tell it that you already have cwm.
[Captivate Android Development] Stevenrogers_420:
Just updated from your KJ3 to this and worked perfect. Thanks for workin on this Kyuta!!!
[Captivate Android Development] mbc663:
All three of you geniuses should get together. When source drops, then split up.
[Captivate Android Development] Kyuta Syuko:
Not sure why it would do this to you. Only thing that changed was the recovery and the added su binary. The way it's loaded is still the same and it doesn't do it for me and I just reflashed the main parts of stock (factory.rfs, cache.rfs, dbdata.rfs, the kernel, and modem.bin) then reflashed 1.1. If anyone else chimes in about it to verify it's not just an isolated incident.

As for when source comes out. I'm not sure how active I'll be with compiling my own kernel once sources drop because it's a bit more time consuming then unpacking, adding stuff in and editing scripts, and repacking. We'll just have to see if I manage to get a decent laptop to use or not since I don't really want to use my gaming PC for it.
[Captivate Android Development] Stevenrogers_420:
Has nandroid backup been figured out with this rom or was I imagining things?
[Captivate Android Development] Kyuta Syuko:
As I had explained in another thread I was chatting with existz about the version of recovery he was using in TalonDEV verses the other, newer versions currently out (such as 4 which was used in boorg's original kernels though I think he's using 5 now) and he said that 4 and 5 have quite a few issues (such as nandroid) while 3.0.0.5 works "prefectly".
[Captivate Android Development] Stevenrogers_420:
Thanks for the ubr quick response. I thought I had read that somewhere.
[Captivate Android Development] boog:
I flashed your kernel, and the first boot into recovery (before conversion to ext4) had the error for cache, just like my experiments, but, after converting there is no error. Cache is mounted properly. I guess the next experiment would be to convert back to rfs and see if the problem comes back.

And I am feeling somewhat the same about the source. It appears to be much harder than just hacking up and repacking a kernel.

He told me the same thing, but my experiments ended in a soft brick. I guess it needs tested. Not sure I want to redo my phone tonight lol, think I will save that for another night. But, I could have been missing something, it looks like you have all of his cwm, I only copied his recovery file over to mine. Could be a difference in the scripts and things.
[Captivate Android Development] Kyuta Syuko:
I only copied over his recovery into the cwm folder since the voodoo scripts pulls it from there. There's no recovery binary in the sbin or home/base folder to save on space. All the scripts are still the ones I pulled from the I9000 JVT Voodoo kernel. Some that I modified of course. As well as the stock KJ4 .rc files.

I don't really use the nandroid backup myself, but I suppose I should test it out a bit.

I don't see why cache would mount while using ext4 but not rfs. I'll have to test it out tomorrow and see if that's what's happening.

As for collaboration, what do you have in mind?
[Captivate Android Development] Darkuso:
Anyone has tried the zipalign? How works?
[Captivate Android Development] Stevenrogers_420:
I have used it and assume it works. My qudrant scores jumped 600 points.
[Captivate Android Development] boog:
I can build cwm, let me work on a few things. Might take me a bit to build and test. Have some crazyness going on irl.

I can pull exzistz's source for android bootable recovery, and customize it.

I also think there may be a couple things in the source that may need changed. Will need to test a factory reset to see. By default, it looks like the source wants to format /ext-sd instead of /dbdata, but the sd-ext isn't being mounted in fstab, so it shouldn't get formatted.

Here is the line of code I am talking about:

https://github.com/existz/android_bootable_recovery/blob/gingerbread-cyanogen/recovery.c#L687
[Captivate Android Development] Kyuta Syuko:
Yeah I noticed that when doing a factory reset a few times. dbdata never got wiped and I always got an error about sd-ext.
[Captivate Android Development] boog:
That's why I think there is something way different in our cappy gingerbread. And I am almost willing to bet nandroid restoring will fail (I would love to be wrong!).
[Captivate Android Development] mtcarey:
Hey boog! I'm doing the same with another version of CWM source. One thing to look for are references to "datadata".... for Gingerbread that should be changed to "dbdata".
[Captivate Android Development] Kyuta Syuko:
I wouldn't be all that surprised if it was. Why don't we try to do our own backup system? Make recovery lzma (or some other, better compression) the important directories (system, data, dbdata?, etc.) and store them on the SDCard in a hidden directory or something. Unless of course we can rewrite nandroid to make it work.
[Captivate Android Development] Boldizzle:
@Kyuta Syuko

I just want to say, thanks a lot for all the work you've put into this kernel. I've never really used it before(usually use mtcarey's) but since root is broken on his at the mo, I've had to use Samurai and I must say, the performance has been phenomenal and my battery life is even better than usual.

It might be a fluke with the battery life but anyway, just wanted to express my thanks.

:D
[Captivate Android Development] Kyuta Syuko:
It's appreciated. Like most people who have created something and/or continue to create stuff will tell you, while they originally created it for their own enjoyment the enjoyment others have when viewing, using their creation is what makes creating it worth it. Or something...
[Captivate Android Development] silverslotcar:
Just thought I'd drop in and say that this kernel is solid as a rock. I've been running this Samurai kernel with a slightly modified version of TRusselo's deodexed KJ3 rom and it is great. I get 1% drop per hour in standby, even while using Tegrak O/C to 1200 with no voltage changes. I have S.A.S. tweaks, extended power menu, 9 scrollable toggles, CRT off animation, custom bootani, and voodoo sound driver from VC Plus. Loving all of it, and your kernel makes it run smooth like butter. For that I thank you! Keep up the good work.
[Captivate Android Development] Boldizzle:
hahaha, nice! Seriously though, it's awesome. I'm loving my phone a lot more now.
[Captivate Android Development] Kyuta Syuko:
Tegrak doesn't step up the voltage automatically when OCing. Not sure where it pulls the default voltages from, but on a stock kernel it just replaces the highest frequency with whatever you choose. In your case you're running 1200 @ the 1000 voltages. Just FYI.
[Captivate Android Development] matmanchu5:
Yeah what he said...it feels like something very cool is going to happen here. I cant tell you how great it is to stumble in to this universe called android and reap the benefits of the genius that resides in this unrevoked and all welcoming community of people who dont just want make things, they want make things better, and who dont mind sharing with those who are looking for the same thing..whoever they are. Its like im a part of something that could change the world! No seriously! This is awesome!....... Did I go too far?:p
[Captivate Android Development] Stevenrogers_420:
Easy Tiger...
[Captivate Android Development] aznxprd:
loving the smoothness of this kernel so far.
[Captivate Android Development] mbc663:
have root?
[Captivate Android Development] Geezer000:
I flashed over from mtcarey.s kernel and never lost root. Works great.

Sent from my Cappy using the XDA app.
[Captivate Android Development] getinlost:
Am I mistaken in thinking that system mount in Recovery restore was fixed?
[Captivate Android Development] mbc663:
you might have never had root to begin with then, unless you odin the tar. i think corn kernel is creating SU problems with the CWM zip only
[Captivate Android Development] Geezer000:
Believe me I have root. I have many apps that require root and they all work great. I CWm'd MTCAREYS kernel and then I used sgs flasher for Samurai.
[Captivate Android Development] sinichi21:
Kyuta just want to ask will pikachus thunder bolt tweak work along with your kernel or its for talon only
[Captivate Android Development] Kyuta Syuko:
The only thing I can see that I'm 99.9% sure won't work is the Conservative governor. My kernel already supports zip-align and at least one person has verified that it's working (or at the very least not causing problems). Other then that I don't really see anything that could conflict in the overview (haven't looked at the scripts themselves) and you shouldn't have any issues so long as you flash the "Others" version. With exception to the Conservative governor of course.

As for root there should be no issues with it using my kernel so long as you download the Superuser.apk from the market.
[Captivate Android Development] hokiemoto:
Does this kernel support UV?

Also curious why Tegrak can work with this kernel but not Voltage Control. thanks
[Captivate Android Development] Stevenrogers_420:
It does.
[Captivate Android Development] poncespr:
I just flashed this kernel over VictoryRom 2.0 (KH3) and have to say, so far it is working well. Great job!
[Captivate Android Development] mbc663:
Anyone have any diff results using the other governors?
[Captivate Android Development] Kyuta Syuko:
This kernel doesn't natively support UV but you can download Tegrak Overclock from the market which will allow you to OC/UV, but the free version doesn't set on boot so you'll have to manually go in and set them each time you reboot your phone.
[Captivate Android Development] mbc663:
Kyuta, CPU spy shows my phone 71% @ 800mhz, and only 6% @ 1200mhz using tegrak paid version for oc. Any ideas?
[Captivate Android Development] Kyuta Syuko:
Using the default ondemand governor? What do you do on your phone?
[Captivate Android Development] mbc663:
Yes using ondemand. Just been surfing the Web and on the xda app.

Edit: 31% on 1200 now with 7% @ 800. Reboot solved the issue
[Captivate Android Development] Kyuta Syuko:
Well I'm glad a reboot seemed to have helped. Not sure what to really tell you about it though since ondemand shouldn't really stop on the intermittent frequencies for very long... Thinking about going over the various tweaks I added in and maybe changing some of them up (namely the LMK tweaks) but I'll keep an eye open to see if there's anything in there that might affect the ondemand scaling since there are ondemand tweaks.
[Captivate Android Development] -Thrive-:
I have been on your kernel for a couple of days overclocked at 1200 using Tegrak. On-demand scaling appears to be working perfectly. I just added undervolting to a couple of frequencies and observing. Everything seems stable so far.
[Captivate Android Development] tamanaco:
Talking about tweaks... what exactly do " topiratiko's ORAM+ inspired LMK settings (not exactly the same but similar)" and "Tweaked TCP settings from pikachu's modded Zach's tweaks" do? I read the whole thread and found no specifics.

I tried Corn Kernel with lagfix a couple days ago and I'm considering flashing this kernel. I'm back on Boog's KH3 Kernel on Pinnacle 1.3. Besides disabling/enabling lagfix (if necessary) and clearing cache+dalvic should I be aware of any other requisites if I want to switch from Boogs to Samurai to Corn and back again if I run into some issues?.
[Captivate Android Development] Kyuta Syuko:
I was messing with Tegrak OC to see what I can get my kernel to do and noticed that it does in fact support the Conservative governor so I was wrong about that in the quoted post. Didn't think it was a default governor.
[Captivate Android Development] Kyuta Syuko:
I think you got it down pretty well. As for the tweaks the LMK settings just adjust what apps Android kills and when and the TCP tweaks should help maximize your data speeds (definitely can't hurt them).
[Captivate Android Development] -Thrive-:
Can't answer the first part of your question about the tweaks but there are no other prereqs to switch from Boogs to Samurai. I was on Pinnacle 1.3 with Boog's KH3 kernel and flashed Corn 3.0.4 using CWM (somehow avoiding the problem others had with losing root) and then flashed Samurai 1.1 via CWM without any issues. I did revert to RFS before the flash to Samurai. I have not flashed back. No need to because both kernels worked well and had no issues.
[Captivate Android Development] sa1yan:
I WANTZ THE UV/OC PWEEEZE!

thanks:P
[Captivate Android Development] rajendra82:
Buy full version of Tegrak Overclock app from the market. It allows you OC and UV.
[Captivate Android Development] Kyuta Syuko:
That requires source for native OC/UV support...
[Captivate Android Development] Wdustin1:
So I flashed this kernel last night and I have tried every other kernel as well and I saw this and did a speed test, where I live I'm lucky if I can hit 500kbps , but with your kernel I consistency am hitting 1500kbps. What did you do I love you lol

Currently Fusionized
[Captivate Android Development] tamanaco:
I installed the Samurai kernel (voodoo lagfix enabled) on Pinnacle 1.3 with the KJ3 modem last night. So far, I'm very happy with the performance as I switch from home screen to home screen and from running app to home screen. I'm not experiencing lag or seen the icons on the home screens populating as I return from a running app. I also found better average and consistent download speeds. The GPS also locks a lot faster. Only "once" last night did the phone freeze and rebooted. It just froze in a home screen, then the screen turned black and the next thing you see, after a couple minutes, is the lock screen with the media scanning running. During this reboot you do not see the AT&T logo or the Samsung "S" bootanimation. Kyuta, in another thread you mentioned that this "might" be caused by having a large number of apps installed. I have 209 user apps installed as reported by Tibu... do you think this is a problem? I did not experienced this reboots when I was using Boog's kernel (no lagfix) with Pinnacle 1.3 with more than 220 apps. So far, these reboots are not as frequent as I experienced them with the Cornkernel with lagfix. Just a shot in the dark... could this be a lagfix + large number of apps issue?

Btw, I never tried a bootanimations, but given that it's supported in this kernel, I'd like to give them a try. Is there a place where I can find some cool bootanimation to test?
[Captivate Android Development] Wdustin1:
The best place I have found for bootanimations is over at our friends the facinate xda forums under the themes and apps there is a HUGE list of bootanimations. I am on my phone right now or I would get you the link to it.

Currently Fusionized
[Captivate Android Development] -Thrive-:
Don't think it is the number of apps. TIBU shows I have 206 apps and I never get lockups or reboots. I suspect one of your apps is bad. What launcher are you using? I use LauncherPro and it is problem free. Check to see if you have any apps installed on external SDcard and move them to phone if you do. Android System Info (free market app) is good for checking this and moving apps. Apps on external SDcard has always caused problems for me, not just with widgets. The other thing I do is freeze or uninstall user and system apps that I am not using. Seems to help with stability (less apps loading in the background) and makes it easier to narrow down problems. Android System Info has a Tasks tab that shows running tasks so you can check on what's going on.
[Captivate Android Development] Geezer000:
What frequency does it stick at when your charging? It might be at 800 a lot because of charging. Mine stays at 800 when charging for some reason.

Sent from my Cappy using the XDA app.
[Captivate Android Development] tamanaco:
So far, it has not rebooted since last night. Knock on wood. I will double-check all the apps that are running in the background if it crashes again. 95% of my apps are installed in the phone. I only have a couple games in the SDcard. I use System Info and Apps 2 SD to move apps back and forth when necessary. Recently I have been switching between Launcher Pro and Go LauncherEx. I've been using Launcher Pro for a long time and did not run into problems until I switched to Gingerbread based ROMs. I was getting Launcher restarts and a black screen covering the home page after every restart. I had to swipe this black window off the screen to get to the home screens. For the last two weeks or so I have been using Go LauncherEx and I have found that it has as many, if not more, features, settings and widgets than Launcher Pro and it's very stable. It's also being updated frequently, something that I can not say about Launcher Pro. Lately, Launcher Pro is more of an orphan child as the developer has not released any updates, but he has said that a new "rewrite" is in the works. We'll see. I also use UberMusic, his music player, which I find has very intuitive Zune-like UI with one of the skins .
[Captivate Android Development] -Thrive-:
I doubt that either of these launchers caused your problem but it seems to be launcher related. If the problem continues to happen, you might want to try wiping data for whichever launcher you are using and then recreating any widgets you are using one at a time to try to narrow down the problem. Also, if you are using homescreen shortcuts to any game or other app installed on the external SD card, these shortcuts should be deleted because they will often cause problems.
[Captivate Android Development] Kyuta Syuko:
I was actually discussing the lockup/reboot issue with another user. Seems it has to do with having a lot of apps on the SDCard and using lagfix. I installed my apps a little at a time and moved all my non-game apps to the phone while he reverted back to RFS and neither of us have had lockups/reboots since. ADW.Launcher EX hasn't been updated since August... Maybe I'll try out Go Launcher EX since a lot of people seem to like it.

*edit* Also whatever launcher you're using being on the SDCard can cause issues regardless of if you're using ext4 or rfs
[Captivate Android Development] TRusselo:
i am having issue restoring a nandroid backup in the cwm,getting passed md5 check, then ERROR

E:format_volume failed to unmount "/system"

if i go to mounts and storage, and try to unmount system, i get

Error unmounting /system /system!

i thought 1.1 was to fix nandroid backups! lol! damn back to stock Effin Eh, eh.
[Captivate Android Development] Kyuta Syuko:
Must be a GB issue then...
[Captivate Android Development] TRusselo:
was that the same issue as before? i have restored without issue on GB, mosiac VII 7 (stock kernel) worked fine.
[Captivate Android Development] Kyuta Syuko:
I honestly never use nandroid so I don't know what the issue is/was before. I just know some people were having issues with it after GB came out...

What kernel were you using on Mosaic VII?