yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Jsmokey:
That's nuts! Too bad I'm gone till sunday night. Oh well looks like I'm just going to have to hold in my excitement till then.
[Captivate Android Development] Jsmokey:
Source Built!

Well I had a little time before me and the wife are out till sunday night or so. Went ahead and pulled the new source from samsung and poked around it a bit. Well more or less my curiosity got the best of me and I went ahead and compiled the stock source and guess what.... it built without a hitch. Threw it in a cwm zip and flashed to see if it booted and it did.

So first thing when we are back from our family's get-togethers I'll start throwing in some patches and post progress as it comes along. Just for an idea of what I'm going to try to get in there here's a little list of things I've been getting ready while waiting for the source to drop.

1)native oc/uv support

2)bln

3)most of the voodoo patches, like sound and color

4)ULF (universal lagfix) this one will probably take a version or two to get pushed in to the kernel

Plus a few other little odds and ends I've been contemplating adding or not.
[Captivate Android Development] Jsmokey:
Made a little progress!

KK4 Source Build Update

Well guys I have made a small amount of progress, came down with the flu on Christmas which put me behind a little and finally started feeling better so I got back to work on this thing.

Here's the progress so far with this thing. First off the list is OC/UV support. The current alpha I'm working on only goes to 1.2ghz, mainly for testing of stability at this point, in the next couple builds I do it will definitely go up. Hopefully around the 1.7ghz mark like glitch has maybe something a little more mild not really sure yet. Next up is BLN which unfortunately is giving me some problems hopefully I can get it worked out before I release it but for now I'm just moving on and working on other patches and mods.

I've made quite a few patches throughout the source that I forked over from many different sources including talon and glitch that should make quite an overall bump in stability and performance. From what little testing I've been able to do, only had the oc patched version flashed for like an hour and a half, its pretty damn fast even at only 1.2ghz. Usually I run right around 1.4ghz and couldn't really tell any difference with this alpha build when before running 1.2 just seemed kind of laggy in certain situations. Also all my benchmark runs with quadrant standard and advanced, antutu, cf bench and smart bench were just barely lower than when I run 1.4. Most were roughly 40-70 points lower a couple actually came out higher.

Hopefully in the next hour or so if I'm feeling any better than I do now I'll put in some more work and get voodoo color and maybe sound patched in and get this thing close to release worthy. Also wanted to mention since I forgot in the last post that I will also be adding alternate cpu governors into the kernel as things progress.

Edit: Looked through the smartass v2 source and since it was such a small chunk of work to patch in went ahead and threw it in and recompiled to make sure everything was ok with the code. No time to test it tonight, I'm off to bed, but it did compile without any issues.
[Captivate Android Development] Wdustin1:
AWESOME. I finally hearing somebody doing something with source. you are the man jsmokey.
[Captivate Android Development] Kyuta Syuko:
Nice. I can't even get my kernel to boot ;/ Voodoo logs complain about devices not existing when trying to mount/modify the partitions...
[Captivate Android Development] Jsmokey:
No problem man I've been waiting for the source to drop forever.

@kyuta

That's awfully strange especially when I checked out the make menuconfig ext4 was enabled for support but not reiserfs.

Have you checked through the config to see if theres any mount options you could change. I don't think that there is any but you never know. I know there is some file system debugging options you can try out to see if it helps narrow the issue down.

Last thing I can really think of which I doubt is missing or you forgot is the mount options in the initramfs for ext4. Might be worth double checking though.

Oh and I almost forgot but is it boot looping or does it just get stuck? If its a boot loop you shouldn't be in too bad of shape and should be able to pull a kernel debug log that would really help you see exactly where its failing at.
[Captivate Android Development] Kyuta Syuko:
Yeah I noticed that too and thought it was strange. I didn't bother enabling it because I wasn't 100% sure about it. I wonder if that's the issue. The kernel just hangs at the kernel logo screen. The Voodoo init scripts get executed like normal but like I said when it tries to mount or modify any of the partitions it gets a device does not exist error...

Also what files do I need to modify for OC?
[Captivate Android Development] Jsmokey:
The easy way to figure out the oc side of things is go to exists github and look at his patch for overclocking, you can actually run his patch on this source too because the cpu freq files are almost completely identical.

If you look through the talondev source there's some other nice little patched pieces related to cpu scaling, voltage leaks and other things that are pretty much copy/paste to add in that are a big help all the way around.

Governors can be a little more tricky to get built in. Smartass is straightforward to get in but you actually need to change certain values around for smartass to function properly. His github explains it a little but its best to reference another kernel that uses it already, like glitch or one of the many others.

You may also want to wait till the end of everything to add lagfix in, I've had a few problems with it when I was playing with the old froyo source for some reason and never was able to figure out why. That's also part of why I'm going to try to get ULF in this instead if voodoo, everything I've tried with it in the past with it has been much less of a pain than voodoo.
[Captivate Android Development] Kyuta Syuko:
Well I compiled the kernel w/o Voodo and it still hung on the kernel screen... Might have to try to compile the kernel w/o any mods and see if that one will work or hang.
[Captivate Android Development] Jsmokey:
Ok, lets see what else could be the issue because you should at least get loops and not just a hang. What initramfs are you using exactly to build from and are you using one? I know silly question but I actually was so psyched about the source I forgot to specify one and it compiled without throwing any errors about it and I drove myself crazy trying to figure what was wrong till I tried to unpack it and there was no initramfs. Also are you positive all the options you absolutely need for the filesystem to mount are checked? That's about all I can think of off hand, really hope you can get yours up and running.

edit: just dawned on me but exists github source for talon i9000 has the config setup he uses for the captivate also under arch/arm/configs/aries-captivate-defconfig which you may want to check out to see if everything is setup right with the default config that way you can check to see all the right options are there for the filesystem.

another edit: Man I completely jinxed myself talking about this now my kernel is getting stuck too and I really didn't add or change jack. wtf!!! I guess its back to the drawing board. Maybe I'll just altogether pull talons build setup over to it and build it that way see if I can get it back on track without too much hassle.
[Captivate Android Development] Kyuta Syuko:
I'm using the initramfs from my original kernel as I didn't think that would be a problem. Also I've been trying to make a custom logo but everything I try has the messed up. The image only takes up 2/3 - 3/4 of the screen with the bottom just a mess of colors (like if I had the wrong bootloaders or something) And the image itself is skewed and looking like it was run through a horizontal shredder and then the pieces copied and laid out in 6-7 different columns. I might throw a default kernel together tomorrow and see if it'll boot to at least rule out what I'm using to build it.

But you did change something. Think you can remember what all you messed with because chances are that might be my issue too, or something similar.
[Captivate Android Development] Jsmokey:
What are you using to make the boot logo? The script in tk-glitch's github or something else?

Well for one I switched over to the kk4 initramfs from the leak... think that may be the root of the problem honestly especially with how many problems I had with it before just modding the init.rc and trying to get cwm working which you were helping me with. I was originally building with the kj3 initramfs before this when it was working but I also did alot of small patches all over the place between adding kk4's initram and compiling which was also a terrible idea without first testing out the kk4 initram without doing anymore additions. Guess I got a little too cocky.

I went ahead and pulled the initramfs that exists uses for talon so I'm going to give that a try for the hell of it since it has cwm, voodoo and quite a bit added and already working. Maybe it will work maybe it wont but its worth a shot and if it does work talk about a massive time saver even if some things need changed to fix some issues I'm sure will come up from using this initram over a native cappy one. I'm also going to pull his captivate config and build script and try using it to see what comes of that using his initram and kj3's again.
[Captivate Android Development] Kyuta Syuko:
I'm using the same one existz is using by morfic. I'll check that one out and see how it works for me.

*edit*

It's the same one I'm using yes.

*edit 2*

You know what... I think I'm making my image the wrong size...
[Captivate Android Development] xpakage:
It may lag on first boot after installing but the boot scans are much quicker after that. My scans seemed to take a long time before where my mail would have downloaded but it was still scannng. Now it has booted before mail has had a chance to download.

Working very well.
[Captivate Android Development] Jsmokey:
lol, yeah it scans pretty crazy fast after the first little stutter. I have over 5 gigs of music, pics, roms, kernels, and on and on and it takes on average 5-10 seconds I'd say to scan everything and be ready to go. Once again thanks for the support everyone I'm glad everyone is enjoying my first release so much and keep an eye out over the next day or so cause I'm working on testing more tweaks now to boost responsiveness even more!
[Captivate Android Development] q659503934:
could you build the UXKH2 version from I896 ？thank you
[Captivate Android Development] Jsmokey:
I'll consider it but I can't promise anything my times pretty well tied up between this, my rom, work, and my small computer repair service I run on the side, plus programming work I pick up here and there.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] Kyuta Syuko:
Glad I could be of help. I wouldn't be where I'm at with my kernel if it wasn't for help from people like boog, mtcarey, yourself, existz, pikachu01, and so on. Granted pikachu didn't help me directly, but his thread about tweaks and what not did.

*edit*

Think I might dive into your kernel later and borrow some of your tweaks.
[Captivate Android Development] xpakage:
Boot Screen Running

This morning when I started the phone, it seemed normal but the boot animation kept playing. I restarted the phone and it happened again. The phone was booted in the background and the animation would stop if power was pressed, but would start up again.

I was trying some different modems last night so I cleared the D cache and cache before shutting it down and charging it.

I reinstalled the kernel.zip and all is working properly again.

Just letting you know. It could have been a fluke.
[Captivate Android Development] Kyuta Syuko:
Just to make things easier for me are all your tweaks in the init.d scripts or do you have some in the kernel as well?
[Captivate Android Development] zvadim:
Lagfix removal is finished, flashing KJ3 version. will report shortly :)

You should probably add lagfix removal as a step under installation instructions, in case some people aren't clear about that.
[Captivate Android Development] Jsmokey:
Feel free kyuta, not sure how well some will work by themselves and some are in the kernel itself but all values are re-affirmed in the init.d scripts just to be sure they are applied and the right values so no need to really open up the kernel. That's actually the main reason I put them all in the scripts also, easier testing plus I can change values on the fly and run the script through script manager and test the difference of new values without needing to reboot, or at least 90% of the time some things need a reboot to work fully.(probably close to 2000 reboots this method saved me during testing lol)

If you are still using the update.zip I sent you xpackage you may want to grab the one I posted in the op instead it has the line in it to stop the bootanim once the system is booted all the way the KJ3 I sent you was the same one that would just loop the anim on my kh3 rom when I tried it. I thought since it was ok for you but looped for me it was a bug isolated to kh3 roms but it seems it might not be. Oh and I fixed the updater script to display "flashing Red Nebula Kerenl" instead of Firestrike which is what the project started as. Oh and I don't know if anyone really noticed but the installation does wipe caches for you so after the install its not necessary unless you wanna do it again to make sure it gets done.

Thanks I'll definitely add remove lagfix in there, I thought since I put dont ask for a lagfix version in there it would be enough but yeah you're probably right that I should add it to installation so no one flashes over a cappy with lagfix on.
[Captivate Android Development] AnarchoXen:
Flashed over «« Illuminance 1.1 »» and is working well.

For what it is worth the score using CF is 3147. When running CF on the previous set up my score was less than yours reported in the OP.

Nice job.
[Captivate Android Development] Jsmokey:
Thanks. Is that overclocked? I run mine at 1.3ghz with tegrak constantly thats why mine are so high and truly a lot of my tweaks values are optimized for around 1.2-1.3ghz but if its running fast enough for you with out it then that what counts.
[Captivate Android Development] Oxicottin:
Can i flash right over kernel corn or do i have to disable lagfix then flash? thanks!
[Captivate Android Development] Wdustin1:
Lol if you read up a few post there is a discussion about it. You have to disable before flashing

Currently Fusionized
[Captivate Android Development] AnarchoXen:
This was at 1.2

At 1.3 the score was a touch lower...

At 1.0 the score is 2264
[Captivate Android Development] zvadim:
after a bit of playing around, compared to ext4 samurai 1.2: media scans are faster on red, but system overall feels snappier & more responsive on samurai, particularly when loading apps or camera. My non-scientific observations. Still major props for hard work!
[Captivate Android Development] Jsmokey:
Wow thats a little strange, also I do kill all open apps before any tests just as a note.

Strange that its that way for you everyone so far has reported the opposite other than at the initial boot up. But as always it can vary from one device to another and with lagfix apps may load a little faster but shouldn't make much difference after the initial load. More or less the way I set it up the kernel is able to swap through processes faster but time to load will be slightly higher because of no lagfix and also possibly because of the read ahead buffers, if you open multiple apps it will eventually load up ram cause swappiness (the amount of stuff pushed to swap basically) is set to leave more in ram longer for faster access when multi tasking. You also may want to give 1.1 that I just posted in op a try as it finishes off the tweaks to kernel scheduler and might help with what you are talking about.

note: I just checked my camera and it loads pretty much instantly and also I noticed most of the little lag it used to have when taking a pic is pretty much gone. So maybe try running the new vers 1.1 a day or so if you want and see what happens.

edit: I did add disabling lagfix to op just so everyone knows and thanks for reminding me to add it!

Oh and is everyone using the ondemand governor cause most of my tweaks are also optimized for it, just thought I'd throw that out there.

And yes you read right v1.1 is now out check op for link!
[Captivate Android Development] AnarchoXen:
3157 Overall Score at 1.3ghz all apps closed after a flash of 1.1.
[Captivate Android Development] Jsmokey:
I think the difference might be that I'm running a kh3 rom, mine actually, which would explain the drastic differences between my scores and everyone else's. Only think I can really think of off the top of my head.

Edit: also the differences in score between v1 and 1.1 are much more notable on kh3 roms, a little over an increase of 100-150 on average.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] AnarchoXen:
I'm happy with it all so far.
[Captivate Android Development] mattern1974:
I'm downloading the Red Nebula kernel v1.1 now to try with Illuminance.

Where can one find the Antares Darkcloud rom?
[Captivate Android Development] Jsmokey:
Thanks both of you. I appreciate everyone trying my kernel out and giving feedback. I just find it odd the massive difference between kj3 and kh3 roms scores running my kernel though.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] Wdustin1:
Very nice kernel, I agree I don't notice much difference between ext4 and rfs but I notice no difference in speed and snappiness between this and samurai 1.2 nice jobs

Currently Fusionized
[Captivate Android Development] crt60:
Thanks for a great kernel. Was hoping for a performance rfs kernel. Works great so far.
[Captivate Android Development] ddoubt:
I'm having issues with bluetooh with both Nebula and Samurai (didnt test Boog's or Corn)... anyway, if I turn WiFi On (through notification bar) and then try turning Bluetooth On, it won't stay on! Even if I turn WiFi off and try again, it will only turn on after a phone reboot. Now, if after reboot I turn Bluetooth on first, then Wifi, everything works as its suppose to be! Isn't this a kernel issue? I remember early builds of talon presenting this same problem on Continuum... I haven't tested this on other ROM than mine... could just be me... anyone having this same problem?
[Captivate Android Development] Kyuta Syuko:
Don't seem to be having an issue on Samurai using a modified, odexed stock KJ3. How long is your Wifi on before you try to turn on BT? How long is your phone on before turning on Wifi?
[Captivate Android Development] ddoubt:
Hmm... just reboot the phone, try turning wifi on then bluetooth... the issue should occur right away...
[Captivate Android Development] Tritan88:
I am having the Bluetooth issue. I am running this kernel with a modified KH3 Rom that I put together using Pinnacle as a starting point.
[Captivate Android Development] Kyuta Syuko:
Well I just turned on Wireless then BT and BT stayed on for me. Though I think it's more of a ROM issue then a kernel issue.
[Captivate Android Development] Jsmokey:
Same here I've never had any issues with bluetooth whatsoever on anything I've used with my kernel.

To me this sounds more like a rom problem or possibly hardware, as I know mine and kyuta's kernel do set up bluetooth just as it should be and is all the way back to eclair. Trust me I've went through every line of init.rc of at least a dozen kernels all the way back to eclair trying to troubleshoot an issue with wifi which turned out to be the rom and matched up almost every line in them.

Truth is as far as the kernel goes not much has changed internally since at least eclair which is why all the tweaks are so effective that everyone is using, they fix what google has pretty much completely neglected over the years.

I'd recommend to try another rom, either that or maybe try corn kernel or the boog kj3 kernel. I don't think any amount of kernel swapping is going to help though as me, kyuta, and mtcarey all worked from boog's as a base.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] Jsmokey:
Same here kyuta did it with both kh3 and kj3 and even flashed yours and still no wifi/bluetooth problems.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] ddoubt:
ok then, I'll try hunting down the problem in the ROM tweaks...

thanks!
[Captivate Android Development] Jsmokey:
It may not even be the tweaks, dhcp connections for wifi are broke in my rom and I've tried starting from a clean base with just su and busybox and it still broke it. Static ip works fine still and connects but I can't for the life of me, no matter what I try, get dhcp working.

I honestly believe its more the fact we're working with leaks and no matter what small things are going to break here and there till the official gb comes to the captivate.

I'm not saying don't try to sort it out just that I wouldn't drive myself crazy trying to because more than likely its nothing you, kyuta, or I did but something that's not quite right in the leaks.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] :
Running kj3 v1 for a few hours now and everything is good. Great battery life. Excellent job
[Captivate Android Development] Kyuta Syuko:
Not that it matters much but you have ro.ril.hsxpa and ro.ril.gprsclass getting set twice. Don't really see anything (and didn't really expect to) that would conflict with the BT working.

I would just like to note that I didn't use boog's as a base I just scanned his for tweak ideas and unpacking/repacking practice. I used the KJ3 kernel as the base and pulled the cwm and voodoo folders out of the JVT Voodoo kernel.

Did you attempt to set the DHCP lease or whatever from the router to something other then forever? I know not really a fix (specially since you can't do it to every router/AP you connect to) but it at least helps in some places.
[Captivate Android Development] Jsmokey:
Oh sorry about that I just thought you used his as the base.

Yep I've literally tried every wifi fix there is, different versions of dhcp, disabling security on router, miscellaneous router settings that could block it, pretty much every piece of information I have gathered between getting networking cert and almost literally every google result about problems with android and non android dhcp connections and absolutely nothing will get it to work and that's with just adding busybox and root to the rom and nothing else.

In older roms on some devices people had the same problems and none of the fixes I found in any of those threads would work either.

I know that sounds crazy and I know there are a couple kh3 roms out and dhcp works on them but it just absolutely refuses no matter what I try on mine. Stock kh3 works.fine on my captivate btw.

I even thought I may have by accident removed something and that messed it up so I found a page that lists what all the stock system apk's are and what they do since some have very obsure names and no luck there either.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.