yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Stephenv1971:
If you are coming from 1.3.4 you won't need to change any of your settings.
[Captivate Android Development] jojorios:
Perfect! Thank you.
[Captivate Android Development] InsaneJester17:
Just flashed Tayatuma's 1.0.3 lite rom and tried to flash the jpp update moden found in the first post via clockwork but it fails. :o
[Captivate Android Development] newter55:
Wanted to see if anyone else is experiencing cell signal fade issues when pushing the voltages too low.

I ran Doc's rom yesterday, jfs advanced (tttffff), with jpp modem and noticed the signal would "disappear" even though I was in areas where i would normally get service. This morning I loaded up Tay's good old standby and stuck with jpm modem (love the gps with this btw on my phone, ymmv) same jfs adwanced, no other tweaks and whenever I try to uv at -75 or lower on low end, my cell signal faded again to nothing when the phone was idle. This is at my house where my signal typically ranges from -70 to -85 on 850 band.

Everything else seemed great and phone was stable in every other respect (at 100, 100, 100, 75, 125, 125) as long as the 800mhz remained at -75. Below that would cause freezes as I stated before in another post.

If I keep the uv to -50 or above in the 1, 2, 400's, the problem with signal loss does not appear to be occurring.
[Captivate Android Development] newter55:
The one for ODIN works, or you might try downloading again I have not flashed just the modem file through cwm so it may be bad?
[Captivate Android Development] RKight:
So my battery life was horrible on 1.3.4 but is awesome on 1.3.5. I had force close issues with Launcher Pro on both kernels. I disabled all of the extra tweaks via recovery, and Launcher Pro has yet to force close on me.

My current settings are:

JFS for all partitions, no loops, no bind

All tweaks off

BLN off

Stability is awesome and so is battery life.
[Captivate Android Development] stuff:
Can anyone upload the .7zip odin version of 1.3.5 to another website? I cannot extract the .tar for the love of me. It ALWAYS comes up corrupt, and I've tried everything I can think of.
[Captivate Android Development] florelui001p:
Does anyone know if I can safely flash this kernel over cognition v2.3b2? Or will I run into problems?
[Captivate Android Development] lpsi2000:
Go back to the Cog thread and ask the same questions you have been asking. Based on your previous posts, it looks like you have no interest on reading and even trying to comprehend what is going on. The safest way to do anything here is to read.

Edit: I am going back 1.3.5 and give that shot. It seems as most PPL are finding it much more stable now.
[Captivate Android Development] TheTodFather:
Yeah your phone will hang up if the low freq is too low...i have it at 50 50 75 100 125 125 and no problems. When i push the last 100 or 200 settings to 150 problem. Nice to see your settings those are too aggressive for my phone, i would have problems but it's great you are running that.
[Captivate Android Development] TheTodFather:
I HAZ COG and nowz i have no sound i think the kernel had viruses and now its brikcked. If i flashy this kernel will it be haven quadrantz like 3000?

J/k :D

Today is day 2.5 from last charge.... Two days and half that's pretty awesome. I used my phone moderately and used pandora to stream music through bluetooth in my car for about an hour as well. NICE!
[Captivate Android Development] lpsi2000:
It looks like we might be back in business with 1.3.5 and 1.2.6. I have been running it for a few hours with the configuration in my signature and I have not had any issues. Good job on this and thanks for the efforts.

Little something for your effort (Transaction ID # 04G9818604013681M)
[Captivate Android Development] Stephenv1971:
Been on 1.3.6 for 24 hours now (or nearly). No reboot in the middle of the night, no stability issues, fast as all get out. I can't imagine wanting to use a Captivate rom now with all this speed.
[Captivate Android Development] crazililazn:
Do you mean 1.2.6? If you do, when i tried 1.2.6, it would not save voltage settings after a reboot :[
[Captivate Android Development] Stephenv1971:
I mean 1.3.6, which is what is in the current 1.3.5 zip on the main page. Voltage settings are sticking with 1.3.6. See my previous posts to get a better explanation.
[Captivate Android Development] crazililazn:
Wait what? why would it be called 1.3.5 if it is version 1.3.6? typo in the file name? O.o
[Captivate Android Development] bts0uth:
I knew this would lead to confusion.

The original 1.3.5 didn't load voltage settings on reboot so SetiroN fixed it but didn't update the thread to reflect anything changed. The build number in the phone says 1.3.6 otherwise no one would know.
[Captivate Android Development] Stephenv1971:
He's had a long week I suspect. There is a difference between 135 and 136 in that init.d is not enabled in 135.
[Captivate Android Development] crazililazn:
OHHH lol ok. thanks for the explanation. So, Looking at some post, seems like the 1.3.6 and 1.2.6 release have had no charging problems or random reboots right?

Just want to make sure, Don't want to go on a flashing frenzy again ><
[Captivate Android Development] bts0uth:
The charging issues seem to be gone in 1.3.5. Only issue is not only does custom bootanimation not work but I have no boot screen at all.

Not sure if its the kernel or cog 2.4.

I will be totally happy once the bootanimation is back!

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] crazililazn:
D: i cant live without my apple is nom boot animation tho :(
[Captivate Android Development] Stephenv1971:
It's cog for sure, no problems on tayutama.
[Captivate Android Development] bts0uth:
I figured. That sucks, cog 2.4 is working very well for me

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] shaolin95:
No animation prob with mine either.
[Captivate Android Development] SetiroN:
Fixed.

Hope the bottom line I added clarifies. It's 1.3.5, build 136. Build 135 was up for just a couple hours.
[Captivate Android Development] rraquib:
Would be nice if there was a way to disable the bootanimation all together. I would rather have a fast booting machine.
[Captivate Android Development] MikeyMike01:
Make a boot animation with one still image.

Done.

Sent from my Captivate.
[Captivate Android Development] Kizzmiazz:
Well just to piss off all the people who don't like us cognition users flashing this kernel lol I flashed cognition v2.4.1 and Setiron's v1.3.6 kernel and all is working perfect except no boot animation which has happened to all with this combo. Lag fix ext4 x 3 ffff . Uv is set to 125,125,100,75,75,75 and all good. So far after a week of flashing i19000 roms and kernel this is by far the fastest and best running combo.

Sent from my Samsung Cognition | Cognition v2.4.1 | SetiroN's i9000 SuperOptimized ReOriented Kernel v1.3.6 | [THEME]Darkness v2.3
[Captivate Android Development] iamcombat:
How do I flash this over Cognition? rename the file to update.zip??
[Captivate Android Development] Kizzmiazz:
No need to rename the file. You flash through clockwork recovery. Just make sure you read a lot about modems and read this whole thread.

Sent from my Samsung Cognition | Cognition v2.4.1 | SetiroN's i9000 SuperOptimized ReOriented Kernel v1.3.6 | [THEME]Darkness v2.3
[Captivate Android Development] iamcombat:
All 92 pages? haha....I don't have that much time
[Captivate Android Development] Kizzmiazz:
Just telling ya the truth lol always good to read all about what your gonna flash.

Sent from my Samsung Cognition | Cognition v2.4.1 | SetiroN's i9000 SuperOptimized ReOriented Kernel v1.3.6 | [THEME]Darkness v2.3
[Captivate Android Development] newter55:
You will likely spend more time fixing a f'd up flash than taking time to read this thread
[Captivate Android Development] Kizzmiazz:
And don't ask for help here lol, you will get the kernel Nazis after ya. Pm me our newter lol

Sent from my Samsung Cognition | Cognition v2.4.1 | SetiroN's i9000 SuperOptimized ReOriented Kernel v1.3.6 | [THEME]Darkness v2.3
[Captivate Android Development] l7777:
No one has a problem with Cognition users trying this kernel and it's great that it's working for you. You seem to understand that mixing the two has the potential for issues large or small. What we do have a problem with is them asking the same question over and over and then being surprised and upset when not everything works as expected when the kernel has never been advertised as working with Cog.

And we won't have time to help you when you ask a question that has already been answered.

Some more kernel info

Two days on 1.3.5 build 136 and no charge issues.
[Captivate Android Development] bts0uth:
Is kernel build supposed to say 2.6.32.9 ? I could have sworn it used to say setiron build#

Did my kernel get screwed up somehow?

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] crazililazn:
Wow... WTfreak... Rebooted the phone, it came up with a message say i had changed the lagfix i was using. So i just clicked Remove the new configuration, and now the phone just gets stuck at bootanimation....
[Captivate Android Development] bts0uth:
Mine did the same after flashing a theme in cwm but I selected remove new config and it booted. I'm using cog 2.4 so I don't have a bootanimation, it goes from the i9000 screen to the lockscreen

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] crazililazn:
I didnt flash a thing. I was just rebooted and now its stuck... I have no idea wtf just happened...
[Captivate Android Development] bts0uth:
Try disabling your lagfix or restoring a backup in cwm

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] crazililazn:
KK trying to disable lagfix to see if it will boot up...

Nope... didnt work... -_-

anything else i could do... I think this is the 2nd time it has happened...
[Captivate Android Development] bts0uth:
You can try restoring a backup it made when you first applied your lagfix. Not sure what else would work. Its happened to me before and I usually change lagfixs or restore a backup and it fixes it.

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] sorata98:
So, maybe this is a stupid question, sorry but I'm new to android flashing. Can I flash the jg8 modem using clockwork instead of odin by using the jg8_modem_update.zip file included on this thread? Thanks in advance.
[Captivate Android Development] smokestack76:
No you unzip that and place the file in the phone slot of odin.
[Captivate Android Development] Haloruler64:
Why did I run into problems flashing Cog 2.3b3 over 2.3b2 when running this kernel? After flashing a newer version of Cog it wouldn't boot until I ODIN flashed the kernel again. 3 button combo to get into Recovery didn't work either, though Download Mode did (I always have 3 button). This was a while ago, but I'm just curious to why it does that and how that works.
[Captivate Android Development] newter55:
It replaced your kernel when flasing cog
[Captivate Android Development] Haloruler64:
Yeah, why did that cause it to become unbootable? It's just a kernel change. I had lagfix disabled
[Captivate Android Development] lpsi2000:
There could be many reasons why it did not fully boot or kernel panic. Technically your phone did boot (e.g. when you saw the i9000 screen, or AT&T wall paper), however the kernel may panic for many reasons. I don't think you going to find out specifically without troubleshooting through adb shell and reviewing the logs (Good luck).
[Captivate Android Development] existz:
Mine done the same thing yesterday... got a FC on Tapatalk, phone froze, rebooted, then went into CWM saying lagfix was changed (which I didnt do) .. tried just rebooting, and tried remove new config...had to start all the way over and reinstall everything..
[Captivate Android Development] Sulphur4724:
This happened to me too. Just once.
[Captivate Android Development] crazililazn:
Lol, so i ended up installing cog 2.4.1, and i have one question.

Is this kernel + Cog 2.4.1 breaking the boot animation? Because I had a look in the Cog thread, and people had the boot animation working normally.
[Captivate Android Development] Sulphur4724:
/ducks and covers...
[Captivate Android Development] crazililazn:
lol, im not asking to be flamed, i just want to make sure. Btw, I did search, and yes i saw the post but im just double checking ><

I miss my apple is nom boot animation :(
[Captivate Android Development] Kizzmiazz:
Yes you loose boot animation with 2.4 & 2.4.1 all the earlier builds work guessing cause its a vibrant rom.

Sent from my Samsung Cognition | Cognition v2.4.1 | SetiroN's i9000 SuperOptimized ReOriented Kernel v1.3.6 | [THEME]Darkness v2.3
[Captivate Android Development] pillz424:
Hahahaha! I was reading it on my phone so at first thats all I saw, I couldn't believe it, then I saw the rest of your post,. Funny ****.

I've been running di11i's raw steel 2 for a couple days, all ext 4, all tweeks, uv 75 75 75 50 50 50. I had issues with #134 shutting of my phone when on the charger. Running #136 took care of that problem. So far so good. Batt life is great too. Thanks setiron, doing awesome.

I also receive quadrantz for like 3000 too
[Captivate Android Development] LinuxNewb:
Do you mean #135? #134 messed up on me too but #135 has been very stable.
[Captivate Android Development] Haloruler64:
Thanks for the response man
[Captivate Android Development] pillz424:
No I mean# 136. I guess# 136 is 1.3.5, but# 135 was only out for a couple hours and was missing something with the init.d for the undervolting. 135 was taken down and fixed, replaced by 136. If yours says 135 you should update it.
[Captivate Android Development] jhnstn00:
OK, now I see why Cognition users want to use this kernel. I tried Cognition 2.3.b3 for a few minutes, but my available RAM was 100mb after all my apps were installed. OK back to flashing an i9000 ROM to use this kernel.

Thanks for this kernel. I had no problems with #136 version with bootanimation, resets, or charging. Had it installed for 24 hours, prior to that had 1.3.3 for several days without any issues.

I don't use the lagfixes, just the OC and extra RAM is fine with me.
[Captivate Android Development] Haloruler64:
Doesn't really matter how much RAM you have free, I really never noticed a difference between 150 and 100. Just as fast either way. Never go too low anyway, so this RAM hack doesn't do much for me :P

Also, 25 MB free on a Backflip :D
[Captivate Android Development] Stephenv1971:
I can't tell you how much freedom this kernel gives us. I can just waltz over to the i9000 dev forum and pick a rom, flash it, flash setiron and I am off to the races. Been on a flashing binge this weekend. So far have tried raw steel 4.1

Tayutama 1.0.3, Doc Froyo XWJPA v7.6.2, and DOC Froyo XXJPO v7.6.2. I think I am going to stay on JPO even if the rumored ATT froyo release appears tomorrow.
[Captivate Android Development] netnerd:
nice! i want to try more i9000 rom too, but i worry it will take away my "ok" button.
[Captivate Android Development] Stephenv1971:
Okay I'll bite, what's an "ok" button?

Btw you can get your polar clock back on any i9000 rom by copying the livewallpapers.apk from cog 4.1.
[Captivate Android Development] netnerd:
thanks! but i already find a app for polar clock livewallpaper.

http://xdaforums.com/showthread.php?t=819101&highlight=polar+clock
[Captivate Android Development] bts0uth:
1.3.5 build 136 is working perfectly over the past couple of days.

I disabled all tweaks in CWM and my battery life increased dramatically.

Voltage control app has been updated by the way, been using it for a few days now. Working well and it added BFQ support

http://xdaforums.com/showthread.php?t=829731
[Captivate Android Development] MikeyMike01:
Your constant defense of Cognition is real tiring.

Sent from a Samsung Focus. ;)
[Captivate Android Development] DemonWav:
ROM: Tayutama's I9000

Set-up:

DATA:EXT4

CACHE:EXT4

DBDATA:EXT4

DATA_LOOP:EXT2

CACHE_LOOP:EXT2

DBDATA_LOOP:EXT2

BIND_DATA_TO_DBDATA:False

I know this is probably just a problem with my processor being as bad as bad gets, but seems like its the kernel cause the same set-up on other kernels doesn't do this and I was UVing with an OC back in the Eclair days, but with no OC and no UV, I am getting sleeping-death. This is really annoying because I should not - and I don't on other kernels - be getting sleeping-death with no UV or OC (yes I checked many times) and I used to be able to UV with an OC just fine. Just thought I'd let ya'll know.

EDIT: Forget everything I just said, I remembered about Superpower's CPU Scaling, disabled it, and I'm back to OCing and UVing like normal.
[Captivate Android Development] Haloruler64:
Sorry? 10char
[Captivate Android Development] custommsp:
For those people with kernal panics try CFQ instead of BFQ.
[Captivate Android Development] whitesox311:
i dont know if anyone has actually tried this....but what i did was flash the jpp modem linked in this thread and didnt have the wcdma 850 functionality....all i did was flash the JI6 captivate modem over it and now i still have HSUPA enabled and also have the wcdma 850 band enabled.....its so much better

here's a direct link for anyone that wants to try that instead of doing the factory reset flash and whatnot

http://xdaforums.com/attachment.php?attachmentid=438260&d=1289409848
[Captivate Android Development] fatttire:
edit: sorry, /me fail at reading
[Captivate Android Development] TheTodFather:
I have a suggestion why dont you guys try to use the COG irc for help, please?! It is just that cog isnt even in the OP for roms to use even. Lets not trash the thread with a million cog related questions.
[Captivate Android Development] Alexstarfire:
Ok, I searched for the answer to this but couldn't find it and I'm not looking through 96 pages to see if it's here. So, sorry if this has been asked.

Exactly what do the "tweaks" in the modified CWM do?
[Captivate Android Development] smokestack76:
Anytime you want to mod a kernel or use a custom one its best to read up on them first :confused:

# Remount all partitions with noatime

atime is a setting where the filesystem updates the access time of a file. This creates a write-after-every-read which slows things down. By default all partitions are mounted with relatime, which is an optimized version of atime. noatime is the fastest, and afaik we don't need atime.

# Tweak cfq io scheduler

Tweaked settings of the disk io scheduler more for flash memory. Defaults are optimized for spinning harddisks. Lowered the idle wait, re-enable the low latency mode of cfq, removed the penalty for back-seeks and explicitly tell the kernel the storage is not a spinning disk.

# Tweak kernel VM management

Set tendency of kernel to swap to minimum, since we don't use swap anyway.

Lower the amount of unwritten write cache to reduce lags when a huge write is required.

Increase tendency of kernel to keep block-cache to help with slower RFS filesystem.

Increase minimum free memory, in theory this should make the kernel less likely to suddenly run out of memory.

# Tweak kernel scheduler

Make the task scheduler more 'fair' when multiple tasks are running. This has a huge effect on UI and App responsiveness. These values (less aggressive settings) are 20% of the Linux defaults, and about half of the Android defaults.

# Miscellaneous tweaks

Manually set the starting dalvik heap size.

Increase wifi scanning gap to reduce battery usage.

SO. Use this at your own risk :cool:
[Captivate Android Development] fatttire:
Here is your answer
[Captivate Android Development] TheTodFather:
That was very informative. Thank you smokestack
[Captivate Android Development] Alexstarfire:
@somkestack76, ty, even if it was condescending.
[Captivate Android Development] newter55:
Condescending...in this thread??? No way and especially not smoke...;)
[Captivate Android Development] smokestack76:
Yeah im the spoon feeder today. But working on a faQ for this thread. So PM me what you all want in it!!
[Captivate Android Development] smokestack76:
So no one has any request?. I have all the basic faQs covered i think. And a half a$$ how too for cog roms. All the normal like what settings are for and what the FS mean........
[Captivate Android Development] Haloruler64:
Much appreciated!
[Captivate Android Development] fatttire:
That sounds very helpful, thanks. If you want we can try to contribute / once its published.

I feel like we should start a wikia page or something. I don't mind adding a few points but it seems unfair to give the burden for a FAQ fall on one person.

I'm imagening a gloriously detailed wiki page...
[Captivate Android Development] smokestack76:
I am sure one we get the faQs made up we can move it to a wiki page. Since most issues here are the same for most I9000 kernels.
[Captivate Android Development] krazyphire:
Hey guys beware JFS if you run your battery to zero. Not sure if anyone else knew this but if you have JFS partitions they will corrupt upon the battery running out and you will definitely have to reinstall your rom. Happened to me today T_T
[Captivate Android Development] DOAlaboratories:
+1, i got nailed with that this morning.

Sent from my Cappy using mental telepathy, *****ezz.
[Captivate Android Development] Haloruler64:
Is it just me or is JFS slower than EXT4? Messaging app took forever to load threads under full JFS conversion.
[Captivate Android Development] krazyphire:
I think they both have their ups and downs with JFS being overall faster, but generally incredibly unstable apparently. And EXT4 is more power hungry, but I'll take that over mass corruption any day lol

EDIT: Also its a known fact in the i9000 dev forum that when the battery reaches zero that corruption will occur on jfs. So please do not assume this is an isolated incident. Careful Flashing!
[Captivate Android Development] newter55:
That is odd...i am using jfs after testing ext4 and have not seen any stability issues of any kind since upgrading to 1.3.6.

What are you seeing happen?

Btw, settings are jfs advanced. Bln off running tay's rom atm. Not bothering with uv anymore as battery is superb even without pushing them lower though I was running at-100to,-125 except for 800 which I had to keep at-75

Btw, just saw in another thread (not cog one) that dg said he is working on am i9000 rom.....even he is coming around;) he will have to keep cog going though for the newbies...
[Captivate Android Development] bts0uth:
I had been running jfs advance with no problems for the past week and then last night my battery hit 0 for like 20 seconds before I plugged it in and after that my launcher pro did nothing but FC and I couldn't do anything. I had no idea JFS corrupted data like that until it happened to me lol

Posted from my Captivate running Molecule aosplike rom with SetiroN's i9000 SuperOptimized kernel
[Captivate Android Development] krazyphire:
The issue doesn't start till your battery hits zero. Try it if you think its so stable lol
[Captivate Android Development] DemonWav:
So regardless of the ROM I used, or the lagfix setup or the OC/UV setup I use I always get kernel panic mode when I try to charge with the phone off. v1.3.5

Edit: Same thing for v1.2.6
[Captivate Android Development] newter55:
I was assuming that the original post i was referring to was claiming "incredible" instability beyond the battery at zero issue being reported which i do not doubt. And, since you felt the need to chime in with such an informative comment, I have indeed had my phone shut down due to the battery being low but have had no problems with corruption. Perhaps you need to learn to calibrate your battery correctly so that the phone behaves properly and still has enough power to shut down rather than just die. oh... almost forgot lol