yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Jay120171:
I am having issues as well with it crashing to a screen that says something about kernel in red text. Sorry I don't remember the exact text. I have to pull the battery to reboot. It seems to happen at random times and is not related to charging. I even disabled all lagfix options and have not adjusted any OC/UV setting so it is using the stock configuration.

Here is my install process:

Odin to stock 2.1

Install CWM

Flash Tay 1.0.3 Lite and boot

Disable lagfix and boot

Flash your kernel 1.3.3 and boot

Hope this helps.

Jay

EDIT: Thought I was using 1.3.4 but it was 1.3.3. I am downloading now to test it out today.

I've used all 1.2 versions prior 1.2.5 without issue. Haven't used 1.2.5 yet.
[Captivate Android Development] SetiroN:
...

What version are you using?

What versions have you flashed before?

Did you repeat the process after (eventually) having flashed a 1.3 kernel as I suggested in your quote?

Also, are you using setcpu?
[Captivate Android Development] sifulee:
On earlier 1.3 kernels I was having the random shutoff issues while charging, but I'm not have any problems so far on 1.3.4 :D I always one click to JF6, master clear, etc.
[Captivate Android Development] joedon3:
Quick question on Master Clear: I've tried this in the past, normal boot, USB debugging ON. and nothing ever happens, I'll let it sit for 10 mins before giving up and flashing my ROM.

Am I doing something wrong here, should I see some type of progress? or just wait longer? :D
[Captivate Android Development] l7777:
Keep us updated, I'm also seeing the charge issue and will wait for your report on a solution or not before I start trying to wipe things out. :)
[Captivate Android Development] shaolin95:
1.3.4 is also working great for me just like 1.3.3 .

Testing UV now to go as low as possible for 1.2 and 1.0

Regards
[Captivate Android Development] jojorios:
I'm sorry for the newb question but I've tried searching all over and can't seem to find the answer. How exactly do I set the UV settings.

I have tried

adb echo "50 50 150 75 75 100" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

adb shell echo "50 50 150 75 75 100" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

And I get The system cannot find the specified file. I have also tried using the Voltage Control Programs 1.97b, 1.98 and 1.98b and all I get is the blank screen.

I am currently using Deviant Rom from 11/06/10 with Setiron Kernal v1.3.3 and SetCpu.
[Captivate Android Development] joedon3:
The app should work if you are using the correct kernel. I'd start with removing SetCPU, it seems to have been causing some people some problems.
[Captivate Android Development] shaolin95:
Agreed, the only time I got a blank screen was when using the 2.1 with version 1.67 of the utility as they are not compatible.
[Captivate Android Development] lpsi2000:
That is interesting, however I don't understand why the issues are only happening with 1.2.5 and 1.3.X. Based on your theory it should not happen to 1.2.5. 1.2 is still working fine and I would expect this to continue with all versions.

I am just trying to help figure this out. I also ruled out Launcher Pro but using ADW and the issues were still there. When I have time to start over, I will give it a shot but I am hoping this is not the case.
[Captivate Android Development] jojorios:
Well I tried uninstalling SetCPU and don't know what happended but it totally killed my rom. Won't get past the animated boot screen. Going to do odin 1 click and restore and start over.

How would I go about and set the UV settings manually with the echo command since the echo command I'm using seems to be wrong?
[Captivate Android Development] bts0uth:
Well I will admit I thought some of you guys were crazy but last night I went to sleep and my phone was on charging and I just woke up and it was all black and I had to pull battery to get it back on.

I do not use setcpu.

My voltages are -125 -125 -100 -100 -50 -50

Captivate rom

Launcher pro plus

V1.3.4

First time ever happened and I have been using every 1.3 build that's been released

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] RKight:
I'm running MikeyMike01's modified Doc's ROM and I have to say, I loved it...with the 1.3.3 kernel. I noticed, since updating to the 1.3.4 kernel that he included in his latest build, my battery life is horrible. Has anyone else noticed major battery drain with 1.3.4?

Edit: I should note, the new kernel was the only update to the ROM, so that eliminates any other possibilities.
[Captivate Android Development] Stephenv1971:
No black screen, it just reboots now. This could be progress.
[Captivate Android Development] lpsi2000:
I guess with the two of you still having issues, I guess fresh ROM installs will still produce the issue. I don't have any other angles to work on so I will wait until someone else come up with something better or an update kernel.
[Captivate Android Development] shaolin95:
Either 1.3.4 is better for UV or SetCPU was messing up my phone because on 1.3.3 with SetCPU (had it install only for the stress test) any time I dropped to -125 for 100mhz it would freeze right away.

After upgrading to 1.3.4 and uninstalling SetCPU I am currently testing -125 and so far so good.
[Captivate Android Development] Stephenv1971:
Done, I didn't want to but you needed someone to do it. I'll let you know how it turns out.

Stock-->Master Clear--->JG8 Modem--->Tayutama---->Setiron
[Captivate Android Development] thecellx:
Charging issues. Still on 1.3.4 and 2.1.5

As many here posted, battery charging issues are not fixed. I did odin to stock, and update to Darky 3.0, first with 1.3.4 and after with 1.2.5 and the issue is the same, phone is not charging while turned off. The only kernel that works is 1.2
[Captivate Android Development] shaolin95:
I guess we need to come up with a database of people having issues and ones not having issues to try and find a pattern of why it works for some and not for others.
[Captivate Android Development] Stephenv1971:
I tested this on 1.2.5 last night, cleared battery stats, drained battery, turned off and plugged into AC charger. It charged up just fine. I did not Odin or do anything but change to kernel 1.2.5 from 1.3.4.
[Captivate Android Development] arffer:
Great idea

With random posting of "works" and "doesn't work" it's too difficult to know the scope of the problem and configurations. It will be important to know the config: rom-modem-uv settings-lf settings-tweak settings-setcpu installed.

My gut feeling is that it will be related to UV usage. A lot of this sounds like the old 'sleep of death' syndrome.
[Captivate Android Development] DemonWav:
Boot animations don't work wtih 3.1.4. At least, not for me.
[Captivate Android Development] Grif7:
When I try to wipe the the Dalvik I get this: E:INFO is WRONGDalvik Cache wiped. Is this normal? thx
[Captivate Android Development] bts0uth:
Work great here. Put your animation in system/media

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] l7777:
I can rule out UV already as I've never enabled it.

Rom: Tayutama 1.0.3

Modem: XXJPP

UV: None

Tweak settings: All

setcpu: No

FS: JFS and now EXT4
[Captivate Android Development] Stephenv1971:
Okay well, it took several hours to get my machine restored after this but was worth it to note something, for about 5 hours I was running under touchwiz. The minute I switched to and configured Launcherpro+ I rebooted twice within 30 minutes. I am not willing to give up LP+ so am going back to 1.2 until we have another build where you need more troubleshooting. Hope this helped.
[Captivate Android Development] Stephenv1971:
Okay, went to redownload 1.2.5 and it's downloading 1.2.6. I think I'll wait 15 minutes here and see if we have a 1.3.5 coming.

Update: Ha! I nailed it! See next post!
[Captivate Android Development] SetiroN:
- v1.3.5

removed config optimizations

removed -noatime remount script

(should provide stability for those experiencing hangups/reboots/charging issues)

- v1.2.6

removed config optimizations

removed -noatime remount script

(should provide stability for those experiencing hangups/reboots/charging issues)

HZ=300

***IF YOU WERE HAVING PROBLEMS WITH 1.3.X/1.2.5 KERNELS, PLEASE STATE WHAT KIND OF LAGFIX AND STARTUP TWEAKS IF YOU WERE USING ***
[Captivate Android Development] shaolin95:
So I guess since I am having no issues with 1.3.4...I dont need to upgrade yet right?
[Captivate Android Development] SetiroN:
Right. I'm trying to come on top of those issues, but being rock solid on my phone, what I can do is just throwing rocks at the ocean, hoping to hit a fish... heck I even spent a day rebuilding everything from scratch, and didn't accomplish a thing.

***IF YOU WERE HAVING PROBLEMS WITH 1.3.X/1.2.5 KERNELS, PLEASE STATE WHAT KIND OF LAGFIX AND STARTUP TWEAKS IF YOU WERE USING ***
[Captivate Android Development] bts0uth:
Thank you kind sir. Testing 1.3.5 now

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] newter55:
Docs jpo

1.3.4, jfs adv, no other tweaks

Prior to modifying voltage settings, I got several random reboots.

uv settings now at 100, 100 100 75 125 125, low to high. No reboots in last eight hours no problem charging, power on or off, usb or ac.

When I was playing with the uv I found that I could not get 800mhz below 75 without issues with lockup, ie when using maps, gps, trying to swype in search for address, instant freeze. Not sure I am going to flash 1.3.5 tonight as I seem to be good where I am....for at least a day ;)

Edit....i also gave had one issue with launcher pro not starting correctly....wierd screen freeze, redraw issue....on launcher 2 for the most part now to eliminate that variable

Also to soon to comment on battery but seems good
[Captivate Android Development] thecellx:
Sorry..i really dont understand the *** warning of 1.3.x/1.2.5... I will need to reconfigure laxfix after update??
[Captivate Android Development] bts0uth:
Voltage control no longer saves settings after a reboot. I believe init.d isn't running at startup because the script is there. 3.1.5

Posted from my Captivate running Geomod rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] darkamikaze:
Occasional freeze (gotta remove battery)

NO OC, NO UV,

LAGFIX: ext4, ext4, ext4, ALL OTHERS FALSE

Tweaks: ALL ON

I still think it's one of the tweaks
[Captivate Android Development] d1g1talphyre:
Not only that, but you need to disable the current lag fix configuration that your running before you flash the newer version of the kernal. otherwise, you might be heading to brickville
[Captivate Android Development] crazililazn:
This kernel has the universal lagfix. You don't need to uninstall the lagfix before flashing a new version of the kernel.

V1.2.5

Turns off while charging

Have to remove and put battery back in to boot it back on.

V1.2.6

Voltage did not stick after reboot.

These were both with jfs advance lagfix.
[Captivate Android Development] Haloruler64:
Since when do you disable lagfix when flashing over the same kernel? I thought the point of ULF is not needing to disable it. But I flashed from Cog 2.3b2 to 2.3b3 (no data wipe) and flashed the new version of this kernel about a week ago, and without disabling lagfix it worked perfectly. All I did was turn off UV.

So I WAS running Cog 2.3b3 (now 2.4 without this kernel for now). v1.3.4 with overclock, -100 UV across all frequencies with edited script, full EXT4 conversion without any binds (No-RFS Advanced I believe?), no tweaks from CWM besides BLN, and TouchWizGTG New Dock Mod. I have had NO problems with shutdowns, black screens, or reboots. Only problem was for 2 days it would have a minute delay between plugging in and it showing the battery icon (only happened when off, when on it was instant).
[Captivate Android Development] d1g1talphyre:
your right, for some reason I was thinking about the UV settings instead. Got things crossed in my head for a sec.
[Captivate Android Development] Lertets:
I flashed to 1.2.6. Same problem with the voltage not sticking. Other then that minor annoyance this kernel is solid.

Thanks!!
[Captivate Android Development] shaolin95:
WoW I have no idea how you even can attempt this without having the issue yourself...you are a really patient man! I will be contributing next Wednesday with a little $$$ hope more people the do the same thing :)
[Captivate Android Development] DemonWav:
Set-up:

ROM: Cognition v2.4

Kernel: v1.3.5

Lagfix:

DATA= EXT4

CAHCE= EXT4

DBDATA= EXT 4

DATA_LOOP= EXT2

CAHCE_LOOP= EXT2

DBDATA_LOOP= EXT2

BIND_DATA_TO_DBDATA= false

And same problem as always, phone goes into kernel panic mode whenever it is turned off and charging.
[Captivate Android Development] SetiroN:
Sorry about that, please re-download it.
[Captivate Android Development] thecellx:
Ok... So do i need or not disable lagfix and before update from 1.3.4 to 1.3.5?
[Captivate Android Development] arffer:
Remember, this kernel is based off of the reorient kernel, which DG himself pulled from Cognition quite a while back because that kernel, intended for I9000 roms and not Captivate roms like Cog, have stability issues when mixing a Captivate rom with an I9000 kernel.
[Captivate Android Development] arffer:
no (10 characters)
[Captivate Android Development] bts0uth:
Thanks man. Regardless of bugs, this kernel is the best to date for our captivates. My phone wouldnt be so badass without your work!
[Captivate Android Development] DemonWav:
Not really dude. It's a FroYo kernel, works with a FroYo ROM. Kernel, ROM, aren't strictly made puzzle pieces. I have no bugs using the two, never have, until the 1.3.4 and 1.3.5 update.
[Captivate Android Development] arffer:
In the words of Adam Savage, you reject my reality and substitute your own. Enjoy...
[Captivate Android Development] DemonWav:
When what you are saying isn't true, yeah.
[Captivate Android Development] shaolin95:
That does not make then compatible....take a program I support at work...people were using it with firefox even thought we told them it was not tested under it....it worked until the new update for firefox....maybe somethings were fine but since they are not designed for each other, sooner or later things will go bad.
[Captivate Android Development] lpsi2000:
How did you come up with this conclusion that any Froyo kernel will work? How can you dismiss his comments without any facts, logic, or common sense. He is providing you with good valuable information and this the thanks he gets with no real justification. So you expect the Froyo kernel from the Facinate or Vibrant to work on your captivate. I am very much interested in your logic for your response beside pure luck it worked for you thus far. Pardon my enthusiasm, but eagerly await to learn a bit more of your findings.

I am not sure it was substitute for any reality, because there was nothing real about the response.

It is true, look it up. Do a little bit of research to help contribute to this thread.
[Captivate Android Development] DemonWav:
A Vibrant kernel works on the Captivate, it has the same usual problems, but so do i9000 kernels. That's why the reoriented kernel exists, so you can run i9000 ROMs on an i9000 kernel that works on the Captivate. I got that. I understand that. Still doesn't change the fact that running it on a Captivate ROM isn't a death sentence to your phone, or even a stability issue.
[Captivate Android Development] lpsi2000:
Yes, you are correct on both counts (it is not a death sentence and it could work fine for you). However that is not the rule and you should expect issues even if you don't have any right now or previously. I am glad to see you do understand what is going on and the above response could have been your original response:D. Anyway, I am happy to hear you device is doing well with your combination of ROM and Kernel (unlike us Mortals:p).
[Captivate Android Development] RKight:
I'm running MikeyMike01's JPA ROM.

With 1.3.4, I had jfs on all partitions, ext2 loops, no bind, all tweaks on. My phone shut itself down while it was charging. Also, LauncherPro would always force close on startup. I would have to pull up task manager and end the process. Hitting home to restart would start LP fine, and it was good until the next reboot.

With 1.3.5, I'm using all jfs, no loops, no tweaks. Charging seemed okay but I've only had it for about 3 hours now. Battery life is a lot better (I've dropped 12% in 90 mins with moderate use). I'm still having the LP force close issue at startup.

Also, several people have said there's no need to disable the lagfix before upgrading the kernel. I successfully upgraded one time with ext4 enabled...but now that I'm using jfs, if I don't disable the lagfix before upgrading, I'll get stuck in a soft-boot loop where I'll get the force close vibration after my boot animation, and the animation will start over, followed by another force close, and so on.
[Captivate Android Development] fatttire:
Arffer was nice to give you feedback and generally most people in this thread agree with what he/she told you.

Also I ran your set up and got the same kernel panics which I didn't get with the i9000 ROM, so I can back it up with my experience of that helps
[Captivate Android Development] arffer:
Death sentence?

Where in my answer did I ever say mixing the the two was a death sentence?

I said "...have stability issues when mixing a Captivate rom with an I9000 kernel".

And stability issues is exactly what you were reporting and asking about... "same problem as always, phone goes into kernel panic mode whenever it is turned off and charging."

Your comment that SetiroN's kernel being based on a kernel intended for an I9000 rom "does not change the fact", the FACT is that mixing the two DOES cause stability issues. It was stability issues that caused DG to pull the reorient kernel from Cognition.
[Captivate Android Development] MikeyMike01:
The boards' infatuation with Cognition is alarming.
[Captivate Android Development] arffer:
Battery usage

Typical usage today; calls, reading e-book, surfing, reading news. Just passing the 24 hour mark on the battery, and it still has 50% charge!

Prior to this kernel, I almost never got a full day's use without swapping batteries, or throwing it on charge.

This is wonderful!
[Captivate Android Development] arffer:
OT I know... but I just wanted it known that in my personal opinion, Cognition IS a wonderful rom. I am a big fan of DG and his work. It is so easy to install, it is such a complete, ready to go package, and so much better than out-of-the-box.

But I'm one of those that got bitten by the I9000 bug, and greatly prefer it over the AT&T based roms. Personal opinion.
[Captivate Android Development] yimin090:
Can out of a kernel do not overclock
[Captivate Android Development] bamonkey:
In the middle of testing and noticed build is #136?? Anyone else

edit: by testing i mean ive been messing with various settings all day and plan to for the next 4 hours or so starting now..

in the process of rebuilding with a=jfs, various tweak settings and probably a different UV setting once its up..I will change or reply if its different after the jump.. thanks mikeymike for confirming this really quick for me
[Captivate Android Development] MikeyMike01:
#135 here.
[Captivate Android Development] bamonkey:
:( Well i dont know what happened but i did a complete shutdown to test battery charge while off.. decided to turn it back on and it prompted to back and restore as if i changed the FS..i had already did this before and fearing some problems i told it to just ignore changes...well this proved a bad idea i guess because it would absolutly not boot after this.. tried alot of different things but still nothing. so i tried a backup from 3 days ago via cwm and yeah it boots but its right back where i was 3 days ago EXCEPT i still show the #136 build :confused: may have to start this process from all my backups from 3 days ago//drag titanium folder// redownload the kernel and pray i can get close to were i was:eek:

Edit: Its completly toast :( .. tried to restore apps on the 3 day old build and now its having random restarts. time to start from scratch.
[Captivate Android Development] bts0uth:
Weird bug, I've never had problems with bootanimation and on 3.1.5 running Geomod they worked.

I went stock then cog 2.4 then v3.1.5 of this kernel and bootanimations don't work. Stays on galaxy s i9000 screen for a long time then black then my lockscreen

This is with putting my file in system/media. That's the only way I know how to set it

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] amtrakcn:
Is there a way I could recover the stock boot animation?
[Captivate Android Development] Stephenv1971:
The 1.3.5 that is in op is actually 1.3.6. Setiron had forgotten to enable init.d and ran a quick new build .
[Captivate Android Development] ugokind:
?

I never read if it fit on a Vibrant model.. I really like to test it.. shuld I?

anyone has tested before?

thanks

ugo
[Captivate Android Development] Jay120171:
I ran the 1.3.4 version with Tay's 1.0.3 lite yesterday and didn't have any issues. It charged fine last night and was ready to go this morning. I was using no-rfs ext4 without changing any OC/UV settings from default.

I flashed 1.3.6 this morning and will run it today to see what happens.

I appreciate all your work bro and putting up with all the BS that is going on in this thread. I still don't get why peeps are using this over the Cog ROM's and wondering why it is jenky. Isn't is designed for i9000 ROM's? Maybe I am just biased because I like Tay's ROM (mainly the theme) and have been running it exclusively with your kernel or xcaliburinhand's reorient.
[Captivate Android Development] opcow:
I'm still running 1.3.4. Prior 1.3.x versions gave me kernel panics or the phone sometimes just wouldn't wake up after sitting idle for a bit. As soon as I saw problems I disabled UV and all kernel tweaks, but it didn't make any discernible difference. I never had any issues when using the phone, just while it sat idle--plugged in or not, full charge or charging. I ran 1.3.4 with no tweaks or UV for a while and when that went without incident I added all of the tweaks and setup UV. Still running fine. I've used ext4 no rfs on all 1.3.x kernels including 1.3.4.
[Captivate Android Development] l7777:
This is a silly statement. Just because you've had no problems doesn't mean it will work flawlessly for everyone. And if any FroYo kernel would work with any FroYo rom, why did samsung themselves make a second kernel? The reorientation that Xcaliber did fixed a lot of issues with the captivate, but there are still issues. You still can't use the wired headset to make calls for example.

When the designer of said ROM says that there are stability issues, why would you come back and say that there aren't? I suppose we should just all agree to disagree.

As arffer said, there is nothing wrong with Cog, but when laymen can take a kernel like this and plug it in where it was never intended because it's the latest and greatest thing, bad things happen.

If you are asking if overclocking can be turned off, yes. You just use the voltage app and turn off the OC.

If you have to ask the question, the answer is no. The real answer is that no one knows as it has only been tested on the captivate unless a brave vibrant owner has tested it. The vibrant forums would be a better place to ask.

And finally my update on the new kernel. Charged up last night with no issues. I will continue to update.

Rom: Tay 1.0.3

Kernel: 1.3.5 build 136

Modem: JPP

Tweaks: All but IOScheduler

Lagfix: advanced ext4, no loops, no bind

UV: None
[Captivate Android Development] jojorios:
I'm currently running 1.3.4 and want to upgrade to the newest build. Do I have to reset any of my options/tweaks/UV settings or can I just flash without worrying?