yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] EthanMG:
yes, stock kk4. and i did install root and busybox, didnt think to mention that. i didnt replace and commands, not sure if that option is necessary. but when i booted into recovery, i switched to kk4, sio, smartass, installed root and busybox, turned 1200 oc on, and left everything else at default. it booted up fine, but after about five minutes of going through settings and setting things up, it rebooted, but i gave it the benefit of the doubt, kept working on it, then it rebooted while just sitting on the home page. let me know if any other info can be helpful, il keep trying to get it to work right!
[Captivate Android Development] basily:
I'm "El Tour" on paypal by the way, and I hope that my donation wasn't too modest - come on all you (other) chumps (besides me that is) cough it up! You know this kernel it's worth some dough!

The only problem I'm having now, after I put my installed apps collection on a serious diet (down to 87 user apps as reported my TiBu), is that I get the occasional freeze, but no permanent freezes. I'm running no tweaks, EXT4, Illuminance 3.01, and I can't say when it happens - it seems to be anytime. Oh, I've had to uninstall Google Goggles because it always freezes my phone.

Also, not a problem, more of a feature request or question. When I'm out in the strong sun and turn on my phone, with auto brightness set, it takes my phone an eternity to figure out that it's bright out and brighten the screen. Is there some way to control this delay?

Thanks again for all your hard work.
[Captivate Android Development] Red_81:
I'm one of those guys who have stuck up for devs and recommended donating any ammount if you like their work. Some may have seen me on the soapbox in other threads. That being said, I got lazy and forgot to support my new favorite kernel developer. I appologize and I have remedied that problem.

On a side note, I've been reading alot of the problems posted here and one trend seems to be popping out (not 100% though). I see people who are have reboots are most of the time converted to ext4. Has anyone who has been having the issues try converting back and seeing if that fixes their issue? What about removing all the scripts from init.d? What about turning off all OC/UV? Try doing these 1 at a time.

Just some thoughts from a guy who has done software/hardware testing.
[Captivate Android Development] mtcarey:
Thanks! Much appreciated. Not sure about your freezes... you might play with the LMK settings in Recovery. Maybe you have a background process running that triggers a lot of memory management shuffling. As for the auto-brightness delay, it's something I've got on my list to look into - I noticed it myself.
[Captivate Android Development] bonefan03:
In my instance I was having constant reboots when I was OC'd and had the interactive governor tweak. once I removed OC everything was fine. So not sure if only OC was.the problem or if the two combined caused the problem.
[Captivate Android Development] pupochek:
FWIW, The first (of the 2 Captivates I have in the house) on which I tried 7.0x was running Illuminance on rfs (with Corn 6.03). Could not even make it get out of bootloop till I converted to ext4 and reflashed the rom. Now it's running perfectly with 7.06 (no tweaks).
[Captivate Android Development] mtcarey:
There is another possibility for the cause of reboots that I hesitate to suggest because I don't have any hard evidence for it and don't want anyone to waste their money, but it's possible that given the age of a lot of these phones, the battery might be reaching the end of it's useful life. The KK4 kernel uses significantly less power than the I9000 kernels, which might make it more sensitive to current fluctuations. Amazon carries a replacement battery with about 20% more capacity than the stock battery here. Just ordered one myself - I've read positive things about it and for $12 you can't go wrong. Of course, I could be wrong!

P.S. I learned of this battery reading the Talon kernel thread, where several people also report reboot problems. Nobody has yet reported that this solved anything, however.
[Captivate Android Development] El Niche:
I guess every cappy is a bit different. Tried switching to ext4 just to see how it ran. had a couple of reboots. For me, rfs runs much smoother... Great kernel tho, thanks mtcarey!
[Captivate Android Development] Red_81:
It's exactly these kind of back and forths that can help track down issues. As we all share our experiences the data just builds naturally. Unfortunately it's well know that all the captivates act differently.
[Captivate Android Development] b-eock:
[start_rant]You people just amaze me how you treat the people that give you free stuff! He doesn't have to do any of this. mtcarey is the one who figured out how to add audience chip support to I9000 kernels, how to compile the KK4 source(since doo-doo Samsung didn't provide full source!!!!) He releases this for free and with no expectations, only hopes that people will have a great time with his work! You people need to be more considerate and grow up! It pisses me off the see people piss hard working DEVS, and then they leave.[/end_rant]
[Captivate Android Development] mtcarey:
Thanks... I probably would have blown it off, except that I went to visit my (very much missed) son in college this past weekend. Thought I'd show him what I've been messing around with (he has a DroidX) and the first thing that pops up on my XDA thread is some bozo basically telling me I need to scrap everything and start over! Nice.
[Captivate Android Development] EthanMG:
i saw that post. i know i cant speak for everyone, but i believe a large majority of those who use your kernel are very satisfied and are grateful for anything, since it is all better than stock. Keep it up, we really do appreciate it, and ignore people like him =P thanks again
[Captivate Android Development] basily:
Thanks, I look forward to some solution to the screen brightness delay thing, if you find one.

I'll try playing with the LMK settings, and experiment with disabling OC/UV, remove all scripts from init.d, EXT4 vs RSF, etc...

I wonder about some rogue process/app, I guess I could use something like aLogcat and do a periodic dump to try and see what's causing it? I dread trying to make heads of tails of that though...
[Captivate Android Development] mtcarey:
You can use apps like OS Monitor, Android System Info, etc. to track memory and cpu usage. I'm not sure how useful logcat would be for that.
[Captivate Android Development] kevria:
My wife's captivate is royally pissing me off. I just brought her up to Legend 3.0 and Corn 7.0a which is the same that I am running and set her IO Scheduler to Deadline to be in line with my phone and I immediately ran into issues with it locking up while trying to reinstall Swype so I cleaned both cache's. It still took me about 5 tries to get Swype fixed but now she is seeing a "Blank SD Card" message after her phone runs for awhile and when I look in external_sd all I see is a tibu directory instead of all of her music (a reboot fixes this for awhile). This morning she woke up with the BLN on but the phone was locked up so she pulled the battery and on reboot it hung at the ring unlocker. I think I am going to copy the legend and corn zip's from my phone to hers and reinstall the kernel and rom.

Whats weird is that her phone ALWAYS has more issues than mine.

Oh, and ignore the idiots that tell you to start over. What your doing is great and Im glad that someone is doing it.
[Captivate Android Development] pupochek:
What he said :-)))

Donation sent, BTW:)
[Captivate Android Development] cbalt:
I have the anker battery myself which is less than 2 months old and was getting random reboots while on the phone here and there on legend, I don't recall having init.d scripts at all, was using smartass v2 and had oc on. I also was EXT4, I returned my phone to 100% stock and restarted and left it on RFS so far and haven't had a single reboot. I would guess its EXT4 fwiw. BTW don't worry about what people say, your doing a great job.
[Captivate Android Development] basily:
Ok, i do use os monitor, but the thing is, when things are freezing up, I can't access it to see what's happening because the phone is unresponsive. And then, when I finally can access it, everything had settled down, and if i look at the "message" tab it only shows what's going on right now (actually, when I just looked at it, it seemed to be showing me the future - I don't know where it's getting the time stamp, but everything was about a minute ahead of the current time showing in my notifications).

Also, how do I disable OC/UV? Do I just use the voltage app and set the max to 1000khz?

Lastly, correct me if I'm wing, but it seems that BLN works even if I don't have the app installed - the only easy to disable it is to install the app and disable it though there? And I have to keep the app installed to keep BLN disabled?
[Captivate Android Development] kevria:
Yes it does, at least on my wifes phone which doesnt have the BLN app installed.
[Captivate Android Development] mtcarey:
You can disable overclock in Recovery, as well as BLN. And yes, you don't really need the BLN app... I put that in the O.P. to cut down on questions about whether it was working, since it's easy to see and test with the app.

As for your freezes... yes, the monitor-type apps are not helpful for that. If you're feeling ambitious, you can download (onto your desktop computer) the Android SDK from Google (no need to install Eclipse and all that, but you do need the Java run-time) and run ddms in the "tools" folder. It will give you a nice gui with easy-to-read logcat output and several other tools.
[Captivate Android Development] mtcarey:
You could try eliminating a couple of hardware variables as the cause.... swap battery and/or SD card with her and see if that makes a difference.
[Captivate Android Development] mtcarey:
That's interesting about the battery... are you saying that the replacement battery was causing re-boots? As for problems with ext4, they are usually caused by init.d scripts (like the Thunderbolt re-mount script) which try to change the ext4 mount options. Not a good idea... the ext4 mount options are already optimized in this kernel. Did you actually convert to ext4 with Recovery in this kernel, or was the converion done under another (Voodoo-based) kernel?
[Captivate Android Development] greenleaf10:
I am running 7.06 with DAG8's KK4 rom. Everything is good. One thing I noticed was that in my task manager, it showed I had 329MB of RAM. While I was on I9000 ROMs with Talon kernel, the standard one had 340MB and the BIGMEM version had 353MB (broke 720P recording). Is this something that can be done to this kernel as well? I know 10-20 MB isn't a lot. But GB seems to use a lot of RAM and every little bit helps.

Thanks!
[Captivate Android Development] mtcarey:
Given the number of issues some people have had with this kernel, I left the Samsung values for reserved video memory intact. I believe I used the Talon values in 7.01, but changed them back in 7.02. The bottom line is that I could spend an eternity experimenting with the thousands of variables in the kernel, I could blindly trust the work of others (in this case Talon, which has it's own share of issues), or I can trust Samsung for the bulk of it.

Let's put it to a vote! All those in favor of the Talon values in the next version, say aye. Opposed, nay.

---------------------------------------

Samsung defaults used in Corn:

// optimized settings, 19th Jan.2011

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC0 (12288 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC1 (9900 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC2 (12288 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_MFC0 (32768 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_MFC1 (32768 * SZ_1K)

//#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMD (3000 * SZ_1K) MTC - replaced with better calc below

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMD (S5PV210_LCD_WIDTH *	S5PV210_LCD_HEIGHT * 4 *	CONFIG_FB_S3C_NR_BUFFERS)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_JPEG (5012 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_PMEM (5550 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_GPU1 (3300 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_ADSP (1500 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_TEXTSTREAM (3000 * SZ_1K)

=================================

Modified values used in Talon:

#ifdef CONFIG_S5P_BIGMEM // Breaks 720p video recording

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC0 (5000 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC1 (5000 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC2 (5000 * SZ_1K)

#else

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC0 (11264 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC1 (5000 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC2 (11264 * SZ_1K)

#endif

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_MFC0 (32768 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_MFC1 (32768 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMD (3000 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_JPEG (5012 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_PMEM (2048 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_GPU1 (3300 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_ADSP (1500 * SZ_1K)

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_TEXTSTREAM (3000 * SZ_1K)
[Captivate Android Development] cbalt:
It was done under one of your older kernel versions, I always flashed the newest version the second it came out. The anker battery is still in my phone. I was running the No.Tweaks Init.d scripts and that was the only thing in my init.d folder iirc. Now I have syscorps tweaks, lmk at 80mb, oc on still and am on RFS still since I haven't converted to EXT4 yet and haven't had a single reboot since. I hadn't messed with lmk settings before until now, BLN was off, Startup and Shutdown sounds off which is still the same.
[Captivate Android Development] geeve420:
Just flashed 7.06 with CWM and running great so far, no boot loops or anything. I am on TRusselo's stock kk4 rooted deodexed rom. My question is can we turn off the corn logo boot screen?

Thanks

Geeve
[Captivate Android Development] mtcarey:
Sorry, it's compiled in. Would you really rather watch the static AT&T boot screen? :confused: It ain't beautiful, but at least the Corn boot screen has some feedback.
[Captivate Android Development] popfan:
I know it is a pain to make 2 kernels, but people will never be sure of what they want unless they see an effect of it in person and know how it works with their Rom.
[Captivate Android Development] geeve420:
I am not knocking your work at all, It just seems to last a little longer than the version he orignialy used and sets my custom sound and boot animation off kilter. I guess it's just me being anal LOL!

Geeve
[Captivate Android Development] mtcarey:
I already have two kernels (7.0A and 7.06) and adding more versions to accommodate everything everyone wants is unmanageable. :eek: I'm wondering what happened to the others who were working on source-based kernels... this is the kind of thing that they could do to differentiate themselves.
[Captivate Android Development] kevria:
I am going to reflash the rom and kernel on her phone tonight along with switch scaling gov and io scheduler to those you previously mentioned. I guess realistically I shoud probably just switch the scaling governor and see if that fixes anything.

one thing I did notice with her phone last night when she had the SD card missing issue is that there looked to be cat fur in where the sd card goes (like 2 strands) which I pulled out along with reseating the card. I have no idea if she has seen that problem again today and will check tonight.
[Captivate Android Development] mtcarey:
It does last a bit longer than in earlier versions... newer compiler with optimizations seem to take longer to set up in the initial boot phase, but the trade-off is a faster kernel overall. However, this has zero impact on the boot animation and start-up sound. If those are out of sync with each other, it's because the overall boot process is way faster than stock and the original timings are skewed.
[Captivate Android Development] mtcarey:
Ditch the cat! ;)

P.S. That brings up a good point... folks having problems might want to do a lint check inside. Couldn't hurt.
[Captivate Android Development] cbalt:
You technically have 3 Kernels man, 7.0A, 7.06, and the JW1 1.05. Everyone wants something and it seems like some people are NEVER happy. When you get stuff for free what reason do you have to complain. Look at the hours Mtcarey has in all this for free since I know donations more than likely don't add up to a minimum wage job hours pay. PS my follow up was a page back in case you missed it man. Thanks again also.
[Captivate Android Development] geeve420:
Right on, makes sense! Thanks

Geeve
[Captivate Android Development] storm717:
Great work on this kernel. Running with stock KK4 and its extremely stable, great battery life, and really fast. OC/UV:

With smartassV2, sio, LMK@80, and EXT4, plus massive amounts of frozen stock apps/services via TiBu, this has been the best Captivate experience since I purchased the phone around launch.
[Captivate Android Development] mtcarey:
Cool! Glad to see some under-volt numbers... same as I use (though I went -75 @ 100). I've been avoiding the topic though, since I'm sure someone's going to soft-brick their phone doing this and I haven't yet added under-volt adjustments to Recovery to get out of it.
[Captivate Android Development] kevria:
Cats, plural. We have 3 of them which range from the fat lazy slob to the "if it moves I can kill it and bring evidence" type. Our mid-range is a spastic kitten who thinks that the dog is there for riding...

We get cat fur in everything, mouse, keyboard, now phone...sigh
[Captivate Android Development] prbassplayer:
LOL your post made me look how to change voltage on something else than 25mV steps! xD Learning something else today!
[Captivate Android Development] mtcarey:
I hear you. Dog hair in the keyboard is my "pet" peeve.
[Captivate Android Development] cbalt:
mine was

1200 - 1260mv

1000 - 1200 mv

800 - 1175mv

400 - 975mv

200 - 875mv

100 - 850mv

For the last couple of days including about an hour or so of gaming.

I use Voltage Control Lite and have them as my startup settings and the nice thing about voltage control lite is it puts a file called vcremoveboot-CMW.zip in the sd card folder so you can flash that to remove the settings if you soft brick. Changing the voltages at where they are startup without a way to remove them in case of trouble is a very bad idea.
[Captivate Android Development] Kyuta Syuko:
While I've yet to get a source kernel working (I've been busy with SWTOR I'm a Gamer first sorry...) I was playing with LMK and CFS Values of my repackaged stock kernel (Used the 60MB LMK settings and the default CFS values from Thunderbolt) and it made my phone impossible to use so trying out more aggressive LMK settings might help with the reboots.

As for the two different settings, couldn't you just use an init.d script to change them? Leave the kernel with Stock settings and provide an init.d script that'll set them to Talon's settings?

*edit*

Or in your case add a Recovery option to use Talon's Settings
[Captivate Android Development] mtcarey:
No. Reserved video memory values are compiled in. That's why there is a separate "bigmem" version of Talon.
[Captivate Android Development] herofmm:
mt_carey,

I love your kernel. It is very stable, fast. So, I like to donate, but don't know how. I looked for the donation link, but could not find it. Can you add the link on your signature or something like that? The donation will not be much, however, I like to show I am happy with your development. This is the tread I like most in this website. You are very responsive and do very good development. Cheers~
[Captivate Android Development] :
Right on top of his avatar on his posts lol
[Captivate Android Development] mtcarey:
Latest update (ver 3.03) will hopefully fix sdcard mounting problem when something goes wrong. I've flashed this many times over boog's earlier kernels, but not KJ3... I think I'll try it now!
[Captivate Android Development] ccheung:
I had my phone in download mode and run odlin program. Then click PDA and chose the lastest kernel file and then flash.

Is that all for flashing kernel file through odlin? I still have the mounting problem in CWM after flashed. How do I know I already flashed the updated kernel? Is there anything I did wrong in flashing?
[Captivate Android Development] ou812bkewl:
This kernel is the only KJ3 kernel I have seen so far that has blue text in CWM. That's how I knew.
[Captivate Android Development] ccheung:
Yes, its blue text. I have its 3.01 version flashed already. My question is how do I know I sucessfully flashed 3.03 over it. 3.03 claimed to fix the mounting problem. I flashed but still have problem.
[Captivate Android Development] mtcarey:
Mounting problem with sdcard after boot?
[Captivate Android Development] mtcarey:
Corn > Boog > Corn

I just flashed boog's KJ3 kernel over this with no problems (back to rfs first!). Then flashed this back over boog. No problems.

I took the opportunity to do some comparative Quadrant testing (3 runs each):

Boog KJ3 (rfs) - 1398, 1559, 1637 (tweaked kernel settings)

Corn KJ3 (rfs) - 1261, 1366, 1454 (stock kernel settings)

Corn KJ3 (ext4) - 1843, 1970, 2023 (stock kernel settings)
[Captivate Android Development] ccheung:
Yes. CWM still can't see sdcard.
[Captivate Android Development] mtcarey:
When you're in CWM Recovery you are not "after boot". Can you see your sdcard when the full Android experience is upon you (Touchwiz, Launcher Pro, etc.)?
[Captivate Android Development] Boldizzle:
Still having mounting issues in CWM using 3.03 here as well even though after I've booted into Pinnacle, I can see both internal and external SD card fine.
[Captivate Android Development] mtcarey:
So when you select "install zip from sdcard >> choose zip from sdcard" in CWM you get an error or don't see anything?
[Captivate Android Development] pcguy23:
this is how I got 3.02 working

I got home from work and saw 3.03

Back to the flash

I have been using sgs kernel flasher without issue
[Captivate Android Development] ou812bkewl:
Mounting Issues

I can confirm that the CWM mounting issue still exists. This time I got back to my computer, one clicked back to stock KJ3 (using I897UCKJ3_noBL.exe), downloaded CornKernel_UCKJ3_v303.tar, and flashed in PDA slot with Odin v1.83. Now root is working perfectly and SU can be updated to the most current version. There is no indication of a problem until I try CWM. The ROM I flashed is still odexed. Not sure if that is the cause of problem or not. I hope this helps.
[Captivate Android Development] mtcarey:
Good you got it going! I'll have a look at the SGS kernel flasher and try to figure-out what it does that Odin doesn't.
[Captivate Android Development] prbassplayer:
So when you go in CWM you get no errors?
[Captivate Android Development] mtcarey:
I'm still not clear about what the CWM mounting issue is. Is it when you try to select a .zip from the sdcard and nothing shows up?
[Captivate Android Development] Boldizzle:
I get an error, sorry I'm just going to try a couple things then see what I come up with.
[Captivate Android Development] ccheung:
It has error. Directory doesn't exist or something like that.
[Captivate Android Development] ou812bkewl:
By saying the quoted text that I mean that after bootup the SD is fully visible and mounted and my external MicroSD card is all working just as it did when fully stock. CWM is the only place that this occurs. The only thin that can be see under Mounts and Storage menu in CWM is "Mount USB storage". Selecting it just outputs another error about a file that cannot be found in a path starting with the "E" drive.
[Captivate Android Development] pcguy23:
when I first flashed 3.01 I was

the he posted 3.02 - flashed that and still go mount errors

then flashed the kyuta kernel and all was good

flashed 3.02 again after that and all is good

I used sgs kernel flasher for all of this