yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Slayer_b:
I tries CM9Captivate-Glitch-DEV-20111224_1801 kernel, install Nstools, OC'd to 1.4 GHz and my phone works well, after that I decided to try LiveOC, set alevel to about 110% (with regular OC to 1.4 GHz :-D) and get freeze and graphic artifacts on the screen, then my phone rebooted, Nstool gets SU permissions and all repeats again, and again... :-D

Reset script posted in NSTool thread doesn't help, I have to manually delete config of NSTool, I opened the script and replace string "rm /data/data/....." to "rm datadata/...." and after reboot my phone work like before that =)

Then I tries to reset all OC settings to kernel defaults and try only LiveOC, with 115% phone gets reboot, with 110% it works well about 12 hours and gets sudden reboot. Now i'm at regular OC @1.4Ghz.

At the moment I do not see the advantages of LiveOC method, maybe I'm wrong...

Also, can someone of DEVs look at my topic I'm not sure, but i think it is easy fixable by kernel....

sixstringsg, thank you for your great work!

P.S. sorry for my english, I hope you understood what I was trying to deliver to you :-)
[Captivate Android Development] nuwan32:
yea i meant the themed one that galnet put out a while back
[Captivate Android Development] yohannrjm:
There's a very new 'real ' ICS MIUI release available now. It's in the very early stages of development at the moment.

I'm on it at the moment - most things work, but it's still not as functional as the other two Captivate ROMS.
[Captivate Android Development] sixstringsg:
The script in that thread is, as youve discovered, incompatible. There is a button in recovery for it though. As for your compass the rest of ours are correct on the same hardware, so it can't be a kernel issue. Live OC over clocks the GPU and the memory, as well as the CPU. It is much more powerful, but requires more voltage tweaking for stability.

No, that is still GB. It will not work with V14 yet.

That should work with ours, since it uses Team Hacksungs kernel. As usual with MIUI, technically we support it, but all of the devs and testers run CM9, so we won't know as much about it.
[Captivate Android Development] jerkysh:
can i please get the 3.0.8 glitch kernel?

i don't care if the buttons don't work, i'll use the on-screen one's, this one is very laggy :(

P.s. i saw that the i9000 got 3 preview versions already ;(
[Captivate Android Development] shaolin95:
What exactly is lagging for you? Are you ocing or stock?
[Captivate Android Development] jerkysh:
i OC to 1200 + liveOC 109-111 % with smartassV2 governor

laggy as hell :(

i'll switch to teamhacksung's stock 3.0.8 , it's not fast, but at least doesn't lag
[Captivate Android Development] sixstringsg:
A) its three days after Christmas. I haven't been working.

B) the link to that is somewhere in this thread.

C) apparently you're doing something wrong, since its not consistently laggy for everyone else. D) the i9000 has three previews because first of all, their thread is much more active than this one, with bug reports and feature requests, and also we are working on the 3.0 kernel, which doesn't work on the Cappy yet, so you probably won't get new builds until thats fixed.
[Captivate Android Development] shaolin95:
Indeed mine is flying right now..although yes at a higher overclock. I do not use the stock home app if that matters. Unless you have lag all over.
[Captivate Android Development] jeromechrome1:
Does this have voodoo color?

Sent From My Bad Ass Cappy down here in the tropics. (Jamaica)
[Captivate Android Development] sixstringsg:
I refer you to the change log in the second post, which states " Reverted to stock CM colors implementation (fixing stuff for most users, Voodoo Color likely to be back when good settings will be found) / tweakable via Galaxy S CM settings."
[Captivate Android Development] jeromechrome1:
Thanx for the clarification man. But I really need voodoo color because stock colors are awful on "CM9" as well as no gamma hack. Display is just poor on a whole without it in my opinion. Colors are very washed out and all.

Sent From My Bad Ass Cappy down here in the tropics. (Jamaica)
[Captivate Android Development] tkjeeper:
I was disappointed to not see voodoo also, but was surprised not to see it because the colors looked good regardless! I had to switch because it was still a little laggy. Don't worry, these guys are amazing, I'm biding my time until they have the bugs ironed out!

Sent from my ice cream sandwich powered cappy, from my igloo, in the frozen tundra known as Canada.
[Captivate Android Development] Slayer_b:
sixstringsg, thanks for your answer, it's all clear now.

In v14 prewiew doesn't work proximity sensor, rolling back to stock teamhackung's kernel...

Does anyone have any suggestions why my compass sensor behaves as rotation sensor?

Does the magnetic field sensor responsible for compass working or not?
[Captivate Android Development] olo567:
Do you have a good way to roll back to their kernel without reflashing the whole build? I'd like to pop back and forth to test some things. :)
[Captivate Android Development] jerkysh:
yes sir, yes there is!

http://xdaforums.com/showpost.php?p=20804372&postcount=3016
[Captivate Android Development] slayp00n:
Am I blind? Where is the link for v14? It isn't in the glitch app and it isn't on this thread?
[Captivate Android Development] jaxf250:
Just upgraded to build number 39 - when will the new glitch kernel be released, and will it support 39? Eagerly waiting - thx
[Captivate Android Development] sixstringsg:
It will be released when it is done. As of now, we have been through 39 test builds. And as always with new versions, it will be synced with upstream. As far as I know 39 doesn't have changes that affect the kernel though...
[Captivate Android Development] jaxf250:
Good to hear thx!
[Captivate Android Development] melbourne408:
Working good here on

#39 all morning np :D
[Captivate Android Development] EnemyOfGlaDOS:
Sweet.. time to update I guess :p
[Captivate Android Development] shaolin95:
Just got 40 installed and all looks good so far.
[Captivate Android Development] melbourne408:
Yes!

Today is a good day!
[Captivate Android Development] EnemyOfGlaDOS:
Same here.. you beat me to it :p
[Captivate Android Development] markdexter:
you guys using glitch with latest build?
[Captivate Android Development] melbourne408:
Yea, working well :D
[Captivate Android Development] shaolin95:
Good point I am running a beta kernel.
[Captivate Android Development] rwells813:
Yea working well with latest cm7 and miui

sent from SGS Captivate 2.3.4 with CM7 or MIUI using Escapist or TKglitch
[Captivate Android Development] Johnston212:
Just want to check and see if anyone can tell me how this is working out with RC1/#41? I'm guessing there are some major changes given it's a RC and that the existing kernel might not get along with the RC.

I just want to be sure before I try and flash it. Thanks.
[Captivate Android Development] danduv:
I have no issues on newest nightly!
[Captivate Android Development] sixstringsg:
It works fine. There aren't major changes, it's just a state of stability that makes it a RC.
[Captivate Android Development] melbourne408:
Working very well on nightly #43, perfect stability on 1.5, can't wait for the next release!

Keep it up!

Sent from I'm sure glad Danger went under, else I'd still be on a Mr.Cartoon SK2.
[Captivate Android Development] sixstringsg:
Just an update, we're working very hard in V11. We are on test build 46, with a lot of things bring added in this release.

Sent from my SGH-I897
[Captivate Android Development] melbourne408:
Dope, can't wait!! :D

Thanks for keeping us updated!

Sent from I'm sure glad Danger went under, else I'd still be on a Mr.Cartoon SK2.
[Captivate Android Development] melbourne408:
Doing well on nightly #44!

(Edit-as on #45, can't wait for next nightly.)

Sent from I'm sure glad Danger went under, else I'd still be on a Mr.Cartoon SK2.
[Captivate Android Development] EnemyOfGlaDOS:
Just a heads up... i had to log in from PayPal.com ..all other attempts from the donate to me button do not work. Same for all the other donate to me buttons. Talk about a pain in the ass.. anyway. Thanks Sixstringsg for keeping a thread for us. Not that it makes much of a difference to me :p, but it's good to be organized:D

It's not much, but have a cold one, on me.

Unique Transaction ID # 2KB151615H4474306)
[Captivate Android Development] sixstringsg:
There is a working one in the thread somewhere. We're having issues with soft keys not working, so I haven't been updating the OP.
[Captivate Android Development] jerkysh:
is it so hard to search a little?

here you go :)

http://xdaforums.com/showpost.php?p=20699661&postcount=2303
[Captivate Android Development] sam razzy:
Which kernel is this? Is it. 32 or .35 based kernel?
[Captivate Android Development] sixstringsg:
www.github.com/Glitchkernel
[Captivate Android Development] sam razzy:
Thanks
[Captivate Android Development] imb951:
Having this problem as well.

I understand LiveOC clocks not only cpu, but gpu and memory.

Will you please share a recommended stable voltage table with us for using the LiveOC feature in NSTools? I'd like to be stable at 1.4ghz like when I was using Voltage Control and smartassv2. I do not really understand the difference between ARM Voltage and Internal voltage so I'm not sure which to mess with to get it tweaked right.

I can't get past 110% LiveOC without getting reboots.
[Captivate Android Development] imb951:
Back on the stock build 11 ics kernel, all the glitch lag is gone. Hope to be testing v14 final soon, thanks.
[Captivate Android Development] shaolin95:
This is what I use for 1603Mhz

123% LiveOC using 1300MHz step (giving 1.6GHz)

Now the voltages

ARM voltage

from 1500 to 1200 = 1.5V ; 1000 = 1.375V ; 800 = 1.250V ; 400=1.100V ; 200=950mV ; 100=900mV

Int from 1400 to 1200 = 1.2V ; 1000 = 1.15V ; 800 = 1.125V ; 400=1.100V ; 200=1.100V ; 100=1.000V

Governor I am still testing but usually Smartass V2

You can of course use it as a starting point for lower speeds if you like.
[Captivate Android Development] imb951:
Tested on Glitch again and I'm stable at 1.6ghz. Thanks Shaolin for those voltages! My Cappy is not lagging anymore with Glitch and LiveOC after I gave it a bit more juice!
[Captivate Android Development] shaolin95:
Sweet mate!
[Captivate Android Development] imb951:
Have you tried deep idle with these settings? Does it work or do you get reboots? I am on Froyo bootloaders and have been unable to get DIDLE working...
[Captivate Android Development] b-eock:
cuz you gotta be on GB bootloaders
[Captivate Android Development] zuN!:
I swear I had GB bootloaders prior to installing CM7 back in the day because GB bootloaders did give me better battery life for CM7 than the Froyo ones.

I used the Rogers bootloaders and I do not enter a DIDLE state on Glitch V14.

I'm gonna reflash from stock but is there a way to verify that you have bootloaders installed?
[Captivate Android Development] Slayer_b:
I think, once installed bootloaders doesn't reflashes anymore via CWM. CWM can reflash everything exept bootloaders

shaolin95, thank you for your config, I'll try it when v14 based on 3 branch will be released.

Does anyone on v14 preview mentioned non-functionality of proximity sensor?
[Captivate Android Development] imb951:
Ok so I found the post linking to the Odin package for the GB BL only: Here

Also here's an alternate

Can you verify that this is the correct package?

Sixstring, can you or anyone else confirm that flashing the ATT UCKF1 GB Bootloaders ONLY from that Odin package will not brick my phone if I'm currently running TeamHacksungs ICS build 11 and Glitch v14pre kernel? I don't have a jig at the moment and I don't want to regret doing a BL upgrade just to get DIDLE working....
[Captivate Android Development] b-eock:
He said that GB bootloaders work, he didn't mean they can be flashed on the ROM. You misunderstood that is an honest mistake. I knew they worked on CM7/CM9/MIUI!
[Captivate Android Development] imb951:
ok, so loraque is incorrect below?

^link to above post in the ICS thread
[Captivate Android Development] TwinkyOfHope:
I would also like to know
[Captivate Android Development] htcclay:
I just got a Vibrant again.

Nice work on this.

Plans on moving to 3.1.6?

Thanks

Clay
[Captivate Android Development] Tk-Glitch:
Thinking about it. Note yet decided ^^

Sent from my GT-I9000
[Captivate Android Development] Gromlakh:
You can flash a bootloaders only package. There's no reason it should brick your phone unless the flash screws up.
[Captivate Android Development] slayp00n:
Flashed this and is trying to flash build 12 of cm9, I am getting prop assert failures?
[Captivate Android Development] baghera1979:
Try flashing the rom first then the kernel after you've fully booted. That's what I've always done with no fail.

You are the product of million's of years of evolutionary success, act like it

the above is a sig, not an insult
[Captivate Android Development] Tk-Glitch:
Good news for Captivate users : the dead softkeys problem is now fixed on the 3.0.8 based Glitch kernel (and it was a pain to fix it, really..). You should get an update in a few hours if all goes well.
[Captivate Android Development] TheSoaresan:
Infinity char
[Captivate Android Development] aguila88psi:
Flash build 11 then build 12 then glitch v14 kernel worked for me. Hope I helped.
[Captivate Android Development] pizz0wn3d:
Cool beans, I get paid tomorrow so I'll be buying the market app if all goes well :D
[Captivate Android Development] zuN!:
Approximately how long do you guys remain in DIDLE? I have only 250ms ever since Glitch v14 was released to the public.

Sent from my SGH-I896 on Pre-CM9
[Captivate Android Development] Tk-Glitch:
Glitch V14 Preview 4 for Captivate :

http://androtransfer.com/tk-glitch/...vate/CM9-captivatemtd-Glitch-V14-Preview4.zip

3.0.8 based kernel with all the goodies and even more (not yet added to the changelogs).

One detail, DIDLE has been removed on this one for now and will be added back later.

Softkeys are working.

For ICS only ! ;)
[Captivate Android Development] shaolin95:
I can tell you guys... Glitch deserves a medal for getting this to work...it was a monumental task and he did not give up...I know because I was testing for him a lot and I was thinking man...if it was me I would probably just say...screw it! LOL
[Captivate Android Development] TheSoaresan:
Works pretty well so far
[Captivate Android Development] goob1284:
I'm sorry but pretty well is an understatement... I went back to cm7 because cm9 v11+ the other version of this kernel was a bit laggy. I came back and damn dude this is flying. Good work guys keep it up
[Captivate Android Development] alkiter:
Awesome! Now it's as fast as any of the old Samsung roms, even though Quadrant score seems to report half of what it really seems to be..
[Captivate Android Development] tsuda:
Would it make sense to revisit this request since Corn kernel has been able to implement audience support based on Rogers sources? This would be a great advance for Captivates!

Corn I9000 kernel with audience support:

http://xdaforums.com/showthread.php?t=1403723

Canadian Rogers sources by TRusselo (Mr. rogersRogers)

http://xdaforums.com/showthread.php?t=1326516

Thanks!
[Captivate Android Development] Monfro:
This kernel is really great!!!!

Thanks to all the people involved in this project!!!!
[Captivate Android Development] yohannrjm:
Excellent, excellent work!! I can't imagine how much effort you guys put into this, but it's been worth it.

It's smooth as is. I tried OC'ing it (using nstools) but that caused it to reboot periodically. Perhaps I'll play around some more with the OC settings.

Thanks again - Tk-Glitch, and everyone else who worked on this.
[Captivate Android Development] killmastern3:
Build 12 smooth as silk now. Amazing work... Thanks a lot!!!
[Captivate Android Development] sixstringsg:
That developer posted source in the worst possible way that there is, and only after I bugged him about it. Given that, I do not have the skill to implement it. If Tk wants to, that's his choice.
[Captivate Android Development] Smasher816:
Tell me about it. Glitch (TkGod) stayed up till 6am (probably an hour off) working on this. In order to fix the softkeys he started back with THS stock, and slowly added features in. Every time a new feature was added the beta testers had to make sure everything still worked. Now everything except for DIDLE is in and working and we have softkeys. I think it was worth it.
[Captivate Android Development] askpcguy:
I wanted to share this experience. I am using Miui 12.2 release and Glitch v13. I flashed the gingerbread bootloaders. Phone booted to recovery so I re-flashed Miui. Rebooted and was back in recovery. Ok, I format system/cache and re-flashed Miui and installed Glitch v13. Rebooted back into recovery.

After one clicking to 2.1 JF6, installed Clockwork mod and found it doesn't want to restore the Nandroid backup made on Glitch v13 kernel.
[Captivate Android Development] b-eock:
yahh cuz you can't flash Bootloaders while on any MTD ROM. Just go to 2.1 then flash GB bootloaders. then flash MIUI :D
[Captivate Android Development] sixstringsg:
That wasn't his issue I believe. You can't restore MTD backups on a BML partition table. After one click/clockwork, you have to flash CM7MIUI then restore.
[Captivate Android Development] b-eock:
Ohh ok i c C:
[Captivate Android Development] sixstringsg:
OP updated with current V14 preview, and V13.1. Changes are in the changelog in the second post.
[Captivate Android Development] RootTheMachine:
Latest kernel makes build 12 fly. Two things, though. What is causing the device build prop assert failure in Glitch CWM recovery? You can't even flash the latest ICS build straight over this kernel without flashing something else first. Also, is there anything to stop NStools from limiting my charge? No matter what I do to the slider, it defaults to the lowest value I've ever entered, and the app starts with 96%
[Captivate Android Development] b-eock:
When you flash the Glitch kernel, since TeamHackSung didn't let TK have the device tree, he had to build it himself and he only has made it for the I9000, the get|prop is checking the kernel, not the build.prop
[Captivate Android Development] Pechkin000:
Not sure if I am doing something wrong, but getting constant reboots on build 12. Tried various oc/uv settings with no luck. Basically the screen will freeze for about 5 to 10 seconds then reboot. Anybody else experiencing this?
[Captivate Android Development] MaxRabbit:
Thanks so much for 13.1 for the CM7 folks. Great to have reliable LED notifications!
[Captivate Android Development] krufttangoud:
Thanks again for the CM7 crowd.
[Captivate Android Development] stevebic83:
So far the new kernel has fixed most of my issues. Everything seems to be working just fine. It took flashing a couple of times, but it's all working now. Running it on ICSSGS RC2.1 and it's like having a brand new phone, it is so fast and smooth. Only issue is that it's a little jittery between transitions, was on Nushor's and could notice the difference is smoothness, but it hasn't had time to settle yet, so I'll report back. Good work!
[Captivate Android Development] :
Kernel is working great and is smooth but video recording is broken and random reboots from time to time. Thanks for the great work so far
[Captivate Android Development] bamonkey:
Just popping in to say thanks, im glad i supported by buying the app awhile back. Ive been going back and forth between ICS and miui the last week and the constant stream of updates to this kernel is astonishing. I think this is the part where if it was Ebay i would say something like "Excellent Developer A+++++++" :D:D:D
[Captivate Android Development] sixstringsg:
What ROM are you on, and are you UV'ing?
[Captivate Android Development] :
I'm on Teamhacksung Build 12 and yeah I'm UV'ing the camera issue persists even with a clean install of the ROM and then kernel. It records but when I stop it, it freezes and does nothing and gives a "Camera is not responding" message.The random reboots probably are the undervolting settings I put but I'll test it some more
[Captivate Android Development] sixstringsg:
The camera force closing is not a kernel issue.
[Captivate Android Development] :
I used the stock kernel on Build 12 and it doesn't force close, I record videos with no issues but on Glitch 14 preview 4 although much faster in just about everything, I can't record nothing.
[Captivate Android Development] sixstringsg:
Then get a logcat please.
[Captivate Android Development] mandy007:
I'm on MIUI using Glitch v13.1, do you recommend install pikachu's Thunderbolt! tweaks? and which addons should I install?
[Captivate Android Development] kiattiyos:
I have one question, LED notification on v13.1 compatible with miui? i can't see any notification and miui for captivate doesn't have led setting.
[Captivate Android Development] Snow.Goose:
Using 13.1 on cm7. How do notifications work now? Do I have to enable them through settings or anything? Thanks!
[Captivate Android Development] :
Don't know if I did it right but there ya go
[Captivate Android Development] igoa:
CM9-captivatemtd-Glitch-V14-Preview4

i897 Captivate

CM9-captivatemtd-Glitch-V14-Preview4

1. Can't Wipe User Data or Format /DATA from CWM

2. Turn Phone Off Then Plug in Charger or usb no matter = battery animation don't stop + screen stays constantly ON
[Captivate Android Development] mcala:
Go to settings/call settings & enable led missed calls.
[Captivate Android Development] MaxRabbit:
After saying this... I have tried flashing Glitch 13.1 twice on my cappy and no luck getting LED notifications to light up. Even the "test" within settings doesn't work. Any suggestions?

Thanks for your work!

Edit: TkGlitch says it's a known bug and will be fixed.
[Captivate Android Development] sixstringsg:
I do not recommend anything additional

like that.

Up to MIUI, not us.
[Captivate Android Development] Smasher816:
For #1 I believe this is not currently fixable.

The Initramfs (Recovery) is the one for the Samsung Galaxy S i9000, and may therefore be using the wrong partitions.

This is due to the fact that Teamhacksung has locked the device tree down, so TkGlitch had to hack up a buildable initramfs for some phone.

If you really want to wipe data you can flash THS ICS.zip, advanced->reboot recovery, wipe data.
[Captivate Android Development] Keland44:
you TK and SIX great job put v14 on my build 12 precm9 so good so far

I have two questions though:

do you all have any recommended settings for heavy users I was able to get about 7 hours on my 3500mah battery today I'm willing to test out settings you all recommend if you have any

and i can't remeber but why was it that samsung never released there kernel source code? was it because of some proprietary code they put into it? would there source code help make what you all make with glitch better? if so do you all think we could do a change.org petition for it?

okay so maybe it wasn't 2 questions :-S

thanks again for the great work
[Captivate Android Development] techguy615:
It appears that it is working just fine. Have mine overclocked to 1.5ghz.. only thing so far that is bugging me us the led notification not working. I am running the latest kang on it. I live the call volume script being integrated now. That is great.
[Captivate Android Development] sixstringsg:
Everyone that likes LED notifications, re-download the kernel and re-install. I uploaded a newer one, but didn't change the file name so I wouldn't have to update all the links in the forums.
[Captivate Android Development] donk232:
Before I mess something up the v14 preview for cm9 is for 4.0.1 and NOT for 2.3.7 right?
[Captivate Android Development] baghera1979:
For ICS only which is 4.0.x

You are the product of million's of years of evolutionary success, act like it

the above is a sig, not an insult
[Captivate Android Development] techguy615:
It looks looks like the led notifications work now. I just flashed the new one you uploaded. I am ok as long as i have led or bln that works. thanks