yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] CptTwinkie:
Sounds like full /datadata partition. Open terminal and type "df" look at the % for datadata. If it's full you need to move some apps to sd or uninstall a few.

Also I recommend you read up a little more because this is extremely common in cm based roms. That is assuming this is actually the problem of course but you didn't say you checked for it.

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] Gromlakh:
Any chance you could share with us where this setting is located for the lights? There are several people who do actually prefer to keep the soft keys lit while the screen is on. I for one don't watch movies on my phone and my game playing is minimal. I do use my phone in low light quite frequently, so being able to see the soft keys dramatically increases usability for me.

I'd be happy to write up a script or something if it can be changed that way.
[Captivate Android Development] Holmes108:
I definitely don't find them bright on the Captivate, and the power draining is quite insignificant.

True KTLO support, with the widget, makes it simple if you liked to turn it off and on though.
[Captivate Android Development] jerkysh:
mikeymike01 made a mod that lights the buttons on touch (http://xdaforums.com/showthread.php?t=1109216) , they do turn off, but only when you don't touch the screen :) pretty usefull !!
[Captivate Android Development] sixstringsg:
By popular demand (see the poll) we made them time out. On the Captivate, I do agree that they are quite a bit less annoying on other phones. We are looking at implementing the CM7 way of LED notifications, but that is not a sure thing, nor is there an ETA.

If it could be changed that way, then we would've told everyone long ago, and the poll wouldn't be required. THe settings are in lights.aries.so, which in it's current implementation cannot be changed by a script.

That would work great, if we were using a Samsung kernel, which we aren't, so it doesn't help.
[Captivate Android Development] cmfrtblynmb:
Thanks for the reply

It says 93%

I honestly googled for the problem, but it was hard to describe and vague. Thanks for the reply again
[Captivate Android Development] MrTrunks:
I used my multimeter and checked the ohms of my jig and it only read 295k. Supposedly it needs to be 301k to be effective. I went ahead and ordered a jig from mobiletechvideos in hope its my less than perfect jig that I do not want to waste any more time getting more resistors to achieve the 301k ohms, now I wait....I hope it ships fast. No phone for a few days...:(

If anyone in Arizona has a jig and wants to save me a few days, shoot me a pm. :)
[Captivate Android Development] Gromlakh:
Referencing my earlier question for you, what happens when you try to go to d/l mode using the buttons? I know you said it was not letting you go into recovery, but you should be able to button push your way into d/l mode if you can get to the kernel splash screen.

---------- Post added at 02:33 PM ---------- Previous post was at 02:28 PM ----------

I thought I might have a simple solution for this, if lights.aries.so is the only thing driving the boat. I tried copying lights.aries.so from the latest nightly, along with lights.default.so from Glitch12, into /system/lib/hw, to see if that would fix the issue. No luck. Phooey.

I'll have to keep playing with it. Apparently there's something else at work besides lights.aries.so that's turning the lights off.
[Captivate Android Development] sixstringsg:
You are correct, that won't work. CM7 uses LED notifications, which is implemented in lights.aries.so from the nightly, and V12 uses a different driver, hence it's different name. To change this, it is required do the work before compiling, so that everything plays nicely together.
[Captivate Android Development] Gromlakh:
Curses! :D

Oh well, it was worth a shot.
[Captivate Android Development] MrTrunks:
When trying to enter d/l mode using the buttons, first at&t splash screen shows, then a quick flicker of the glitch v13 splash screen and then nothing...I went to sleep and woke up to my phone still on the glitch splash screen.
[Captivate Android Development] Gromlakh:
That's very odd; your phone should not be booting at all. The key combo for download mode is Vol. Up + Vol. Down, then insert USB cable. You should never touch the power button, so the phone should never have a chance to boot. Are you pushing the power button when you're trying to get to download mode? If so, try again using only the volume buttons and inserting the USB cord.

Also, if you're doing the combo correctly and it's still for some reason booting (even though you haven't touched the power button), try taking the battery out. I've never had a problem getting to download mode if the battery is completely out.
[Captivate Android Development] Fate-Silver:
I bet he's using 3 Button Combo to get into Download Mode...

This is only applicable if you're on Batch 1007 or below or maybe you've have flashed the 3 Button Combo Fix for your device.

Else, 3 Button Combo will only let you to go into Recovery Mode.

I recommended a USB Jig or the 301k ohm resistors to get your phone back to the Download Mode.
[Captivate Android Development] uzbeque:
Is it possible to flash this kernel through Odin?

I was on Glitch (CM7), and tried Talon kernel, now it's hanging while booting.
[Captivate Android Development] sixstringsg:
Through Heimdall, yes. Through Odin, you could make a package yourself. Google has instructions.
[Captivate Android Development] uzbeque:
Now phone is hanging while booting, and Odin can't see the phone in download mode :( pls help? I couldn't enter to CWM too.
[Captivate Android Development] MrTrunks:
holding volume + and - while inserting usb cable just starts up the battery icon showing that the phone is charging. I have also tried taking battery out, inserting while holding combo. Same result.

The label on back of phone says "10.07". I am assuming this is the batch number 1007 you are referring to. holding volume + and - while inserting usb or holding volume + and - and power button while inserting usb has no result on getting me into download or recovery mode. I ordered a usb jig and should be receiving it in the next few days. I hope that works.
[Captivate Android Development] b-eock:
On the new V13 there is the problem with the green screen at low brightnesses...
[Captivate Android Development] mcala:
Oh noes not again! Read the FAQ's & adjust the colors using voodoo control app from the market.

COLOR PROFILE:

Voodoo profile v1

SCREEN RGB

300****

300****

370****

COLORS HACK:

-50

-53

-44
[Captivate Android Development] mcala:
Do I need to install the screen state script after every update or did you update the kernel? I do not see the link in the op anymore.
[Captivate Android Development] sixstringsg:
What link is missing? And the screen state patch is required each nightly.
[Captivate Android Development] Smasher816:
Not sure mcala, ill leave that to sixstringsg or glitch to answer. (Edit: ninja)

Oh and for that download mode problem dude. This method has a 100% success rate for me.

Pull battery. Plug in usb. Hold both volume buttons. While still holding volume buttons but in the battery. Download mode should show on your screen.

This way it defently shouldn't boot/charge as the battery was out.
[Captivate Android Development] mcala:
The screen state patch link. I can't find it, am I blind?

Edit: found it at androtransfer!
[Captivate Android Development] RichMD:
Problems with low memory settings?

I've been running the Kang builds from the location in my sig. Previously the Glitch kernel has worked great for me. However, a few days back I found my phone getting SUPER sluggish - timeouts in various apps, etc. I am running Go Launcher and found that I could click the x to kill apps and it would be responsive again for a while. I updated to the 11/24 Kang build without applying Glitch again and the problem seemed to be gone. I then installed V13 stable again and ran into the problem again after a while. I also had to restore Go Launcher settings even though I didn't choose a wipe, etc. I just tried to install the 11/26 Kang build over it (wiping dalvik and cache first) and my google account settings got wiped, ROM mgr was gone, etc. I have wiped data, installed Kang 11/24 again and just restored via Nandroid (from the 11/24 build before installing Glitch). The phone is OK again. Recently, when I installed Glitch I left defaults - no OC/UV, I/O scheduler and governor left untouched. Any ideas?
[Captivate Android Development] goob1284:
I flashed cm9(the ics thing) and then glitch. It just boot looped. Like wtf man? Jk. I really miss this kernel. You did a good job with this and can't wait to see this kernel updated for ics. If this ran with ics, my god would it fly. Good be and thank you!:)
[Captivate Android Development] MrTrunks:
0% success for me. Looks like the usb jig is my only hope...
[Captivate Android Development] RichMD:
Has anyone else seen this? Is there some setting I can check/set to more aggressively shut down background apps when memory gets low? I haven't done any advanced tweaking like that so I don't know why I am seeing this problem.
[Captivate Android Development] mcala:
Have you tried not using GO launcher? Last time I used it it was a memory hog! See it that helps then if not I would 1 click back to a GB stock w/ CWM then reflash & restore apps only WITHOUT data.
[Captivate Android Development] RichMD:
I actually bought ADW EX and used that in the past. It seemed like most people said Go Launcher was better on memory, etc so I tried it and I like it now. Regardless, I seem to have a problem with really sluggish performance when memory gets low on Glitch but not on the stock kernel. It sometimes seems like RC2 worked better (for me) than the stable release. I haven't yet tried RC2 to see how it works on these latest Kang builds.
[Captivate Android Development] Gromlakh:
I have (kinda sorta) had issues like the ones you described. I've never used Kang builds (yet), but after upgrading to nightly 181 & Glitch 13 things got a bit sluggish a day or two later. I also use GO Launcher EX. I can't really tell you anything about how to fix it...'cuz my problems just resolved themselves. I honestly didn't do anything other than reboot a couple of times when it got sluggish, then suddenly it just stopped doing it and I haven't had a problem since.

Out of curiosity, have you applied the new screenstate_scaling script? I recall the sluggishness stopping somewhere around the time I updated mine, but don't know if that was related. If not, follow the link in the OP to androtransfer.com and you can find it there.
[Captivate Android Development] RichMD:
Thanks, I had not tried the patch - I had never even gone into Screenstate scaling. I have applied V13 on top of the 11/27 Kang build, applied the Screenstate patch, set max CPU to 1200, left deadline and Ondemand, and set Smartass for screenstate scaling. I "assume" this should be the most reliable settings. I also set very modest UV - 100/-75, 200/-75, 400/-50, 800/-25, no UV for 1000 and 1200.
[Captivate Android Development] bearnakedbrew:
Dumb question number 3, will this work with true ICS 4.0? If not will it soon?
[Captivate Android Development] sixstringsg:
Not yet, but soon.
[Captivate Android Development] bearnakedbrew:
Perfect, will we be able to use the updater app?
[Captivate Android Development] FredOak3:
@ RichMD

Did you try going into Terminal Emulator, type su, then type df datadata and see what percentage you get.

If you get over 85% then you could be running into space/memory issues.

I had that problem and deleted a few apps and moved a few more, got it down to 75% and the odd behavior stopped.
[Captivate Android Development] RichMD:
Thanks. I use diskusage and I have 51 of 172 free in /datadata. It still seems to be OK with V13 set like I mentioned above. What do others choose for screenstate scaling? Again, my main concern is consistent good (not necessarily great) performance - same for battery.
[Captivate Android Development] krufttangoud:
Android OS v. Android System

There is talk all over XDA about this. The old kernel I was on, Android OS never came up. With Glitch it is almost immediately there. Anyone know the reason?
[Captivate Android Development] CptTwinkie:
I also did not see the high os usage until I started using glitch. I was never sure if it was using more power or if everything else was using that much less. My battery life overall is better with the glitch kernel so I don't complain about it but I have wondered.

Another issue that I mistakenly posted in the cm7 thread was that I had to stop using the sio scheduler in v13. It became completely unstable when I updated from rc2. Things ran more smoothly for me when I was able to use sio so I was wondering if there is a bug or just an optimization that made that particular schedular less stable. I'm able to use the default but the GUI lags more often. I would go back to rc2 but I had occasional sleep deaths.

Sorry if I'm complaining too much. My thanks to the devs for all the work you do!

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] Raul77:
anyone else having problem with Bluetooth Volume? it was CRAZY loud then i used the script so its much better but the main issue is, the volume + - is disabled while in Bluetooth call, so doesnt matter if its in MAX or Min, same volume. anyone else experienced this?
[Captivate Android Development] iluretar:
awesome kernel nice job, im currently testing teamhacksung's ics build and i miss the high incall volume from glitch and i was wondering if i cold use the 90call_vol script with that kernel ( or any other kernel) or is it a glitch specific feature
[Captivate Android Development] krufttangoud:
Here is a new one to me. On the older versions on glitch i would flash a new miui rom by formatting sys and factory reset. Flash ROM flash kernel, reboot recovery. Then using advanced restore to restore my data only from the backup i had previously made. Now it either says no file found in advanced restore or cant verify Md5 sum????

ideas. flashed twice to confirm.
[Captivate Android Development] sixstringsg:
No, it won't work with that, it is Glitch specific.
[Captivate Android Development] jerkysh:
awesome, you da man :)
[Captivate Android Development] simple man:
I've been having trouble with nandroids too on newest rom manager, so I switched back to 4.7.05 and it works again. Not sure if this would help you, but thought I would mention it.
[Captivate Android Development] goob1284:
+1 I can't wait!:)
[Captivate Android Development] sixstringsg:
ICS is booting with Glitch, and no major bugs other than typical ICS bugs. I might be posting an alpha here soon, keep an eye on the thread.

Don't forget to hit "thanks"!
[Captivate Android Development] goob1284:
You're a saint.:)
[Captivate Android Development] tiuk:
Exciting news!

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] pizz0wn3d:
Whoa. Please make this so.

Herp derp Captivate XDA Premium.
[Captivate Android Development] sixstringsg:
I need a Captivate user in IRC to test for me. Must be running the latest ICS build from Team Hacksung. The first three to join and tell me they have a Captivate will get builds.
[Captivate Android Development] Koizuma:
Interesting, wouldn't mind testing it if you need people

Swyped from my SGH-I897 using XDA Premium App
[Captivate Android Development] razielvn:
I still have problem when answer incoming call with headset. I press headset's button, nothing happen and when I try slide down lock screen to answer, my call hang up automatically.

I'm using MIUI 1.11.25, everything is ok with Platypus kernel.
[Captivate Android Development] skynet11:
Do you want us to report our results here or in irc?

Has anyone seen John Connor?
[Captivate Android Development] airtower:
This makes my day! Will development continue in this thread? I have a tendency to only read my subscribed threads and dont often check the actual development forums for new threads.
[Captivate Android Development] sixstringsg:
PM me please.
[Captivate Android Development] slayp00n:
nvm.............
[Captivate Android Development] sixstringsg:
So, on the ICS Glitch build, USB doesn't work. Like at all. So I doubt anyone wants it until that's fixed. I'm working on it, and should have a fix soon.
[Captivate Android Development] r3ferrei:
You would be surprised how many of us would say screw USB, glitch my phone.

Best to play it safe though.
[Captivate Android Development] tiuk:
Agreed on both counts. Only thing my USB port gets used for is power (i email, Bluetooth, or dropbox files), but I don't mind waiting until you (the devs) feel it's ready.

Sent from Captivate, teamhacksung ICS.
[Captivate Android Development] sixstringsg:
Oh, and market downloading doesn't work. I have no idea how a kernel can break the market, but I succeeded. I'm starting over from V13 as a base, and re-adding all the ICS stuff back on top. I'll see what comes out, and let everyone know. If people would run it without USB and Market, then I might put one out tonight. Completely unsupported, but most of you would assume that from an ICS kernel. You can always flash a nightly if you need market/USB.
[Captivate Android Development] tiuk:
I'm willing to try it, have the time tonight. Maybe i can help figure out how it broke market xD

Sent from Captivate, teamhacksung ICS.
[Captivate Android Development] goob1284:
Sorry. Rough week and its making me angry
[Captivate Android Development] sixstringsg:
Please don't post issues with an un-released kernel here. To people that don't know that you are talking about an extremely alpha ICS kernel, it looks like you're having these issues with V13.
[Captivate Android Development] Koizuma:
Lol that is something I could care less about myself my USB port hasn't worked for about a month now anyways.

Swyped from my SGH-I897 using XDA Premium App
[Captivate Android Development] nm131:
what is callvolume script can you explain?
[Captivate Android Development] sixstringsg:
Did you read the OP?
[Captivate Android Development] kant5t1km3:
is v13 an ICS kernel?
[Captivate Android Development] :
So, I flashed the scaling patch. Do I have to go into recovery and re enable screen state scaling and choose anything?
[Captivate Android Development] sixstringsg:
Not at all. I dont think custom kernels are possible until the device tree is published.

Yes.
[Captivate Android Development] :
Ok, I did that, and went into System/etc and changed the Sleep governor file to say "lazy" and nothing else. Is this right?
[Captivate Android Development] MrTrunks:
Got the usb jig yesterday, plugged it in and booted into recovery instantly! Odin back to stock (3 button fix), heimdall speedmod w/ clockworkmod, clockworkmod cm7.1 install, clockworkmod gapps, clockworkmod glitch v13.

All is working good so far :) Now to put the usb jig in a safe place where I wont lose it.

Also, my 3 button combo to get into recovery now works properly and so does the volume + and - and then plugging in usb gets me into download mode. I am guessing my phone didn't have the 3 button fix in the boot loader.
[Captivate Android Development] sixstringsg:
So, here's what's going on with ICS. We have merged in all of the changes into the Glitch kernel that are required to run ICS, and it runs. GAPPS don't work for some reason, talk force closes and the Market quits itself. I've talked to efpophis, and we both agree that it is more than likely due to the fact that we are building off of the CM7 device tree, instead of the CM9 device tree. We will not be receiving the device tree until Team Hacksung people decide it, and in the words of Kaik541:

"This project" being Team Hacksung. Important to note that Kaik does not contribute code to the project. Due to this reason, we have no idea when we will be able to get a working kernel out, because it is not up to us.
[Captivate Android Development] krufttangoud:
Link to v12b?

I am troubleshooting an issue with CWM, did v12B have the most current Recovery menu? With leakage settings built in?

If so, could someone link it if they have it?

Thanks
[Captivate Android Development] sixstringsg:
A) V12 did not have the current recovery in it.

B) all old kernels are in the OP.
[Captivate Android Development] krufttangoud:
Cool!

Ok, it must not be labeled V12b I have looked thru all the ROOT and FTP links and I found v11 and v13. I guess the ones labeled with the leakages between v11 and v13 are the beta's for 12. I was looking for one actually labeled v12b. I should have known it was those. Der.

Thanks!!
[Captivate Android Development] sixstringsg:
ML: http://androtransfer.com/tk-glitch/.../CM7Captivate-Glitch-HL-DEV-20110922_2025.zip
[Captivate Android Development] slayp00n:
Sound's like he is kind of being a douche.
[Captivate Android Development] goob1284:
Hey six, sorry if I kinda went behind your back in the other thread, but I wanted you to get the device tree pretty badly so you could fix the kernel. Also, kiak or speedy 11 said that the nexus s received the official ics update which will allow the source to drop and therefore the bugs can be fixed. I'm sorry if I made you angry or anything, just wanted this kernel to work really badly
[Captivate Android Development] Keland44:
Glitch will make its way to ics in due time and your supporters will be patiently waiting
[Captivate Android Development] sixstringsg:
No problem. I have a Nexus S, and I haven't heard about any OTA. I'll go look though.

Edit: There is not any OTA for the Nexus S. Just more rumors.
[Captivate Android Development] nm131:
yeah but I'm thinking if this can applied on samsung based rom?
[Captivate Android Development] sixstringsg:
Our source is open, any kernel developer is welcome to use it. You cannot just take the script and apply it somewhere else, it will not work.
[Captivate Android Development] goob1284:
Hey what's so important about the device tree? Can't you just whip a kernel up from the ics rom? If you don't mined, can you teach me a few things?
[Captivate Android Development] tiuk:
You just simultaneously downplayed/made assumptions about kernel development and then immediately asked to be taught how to do it.

Sent from Captivate, teamhacksung ICS.
[Captivate Android Development] goob1284:
I was just taking an educated guess? Sorry.
[Captivate Android Development] Smasher816:
The device tree gives us the actual source code. Right now all we have is the finished, compiled, version. Without the source there is no (easy) way to merge in the specific changes for the glitch kernel. Without the source the most you can really do is hexedit or inject stuff. With the source you have everything, so you can actually edit and add the needed lines of code.
[Captivate Android Development] goob1284:
If I was to start messing around with kernels(yes I know the pros/cons) what programs would I have to get and what do they exactly do? I already have Ubuntu installed on my computer and i finally understand the jist of it. Would I know how to code? Or us there a guide somewhere? Sorry if this is off topic but I really want to learn.
[Captivate Android Development] sixstringsg:
You need everything required to build cyanogenmod, and that's it.
[Captivate Android Development] goob1284:
Are there wikis there that can help me learn?
[Captivate Android Development] sixstringsg:
Yes.

10char
[Captivate Android Development] sixstringsg:
Mostly unrelated to kernel stuff, but I found a cool dropbox alternative that I wanted to share. It's called SpiderOak. It's fully encrypted, and lets you pick different folders to sync. 2gb free, or $10 a month for 100Gb. If you want it, use my promo link please :) https://spideroak.com/download/promo/androtransfe