yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] zmore:
TV Out

While rummaging in the attic I found my old 3.5mm-to-RCA cable that I bought when I got my Captivate, and decided to give it a quick test.

1) It works after switching it on in Settings. (also had to physically switch the video out with one of the L/R audio lines; known h/w problem at the time with this cheapie cable from Amazon)

2) PAL was the default so it looked like flickery B&W crud, but after switching to NTSC it was OK color crud. NTSC should really be made the default since the Captivate was a bigger seller on ATT in the US market.

3) RCA is the crappiest of crappy video interconnects, so I don't know why I bothered. I'll never use TV out again until I upgrade to a phone with wired/wireless HDMI out.
[Captivate Android Development] theytalkalot:
Did you actually watch anything..I can't seem to get

Netflix to show in the TV but shows on my phone
[Captivate Android Development] zmore:
Yes - I used my phone in portrait mode for a bit, then played Reckless Getaway (my 2yrold's fav game) in landscape for about 15mins. All was fine, as expected, since it's just mirroring the phone.

(I can't comment on Netflix - and any DRM-y things they might be trying - since I don't use it, but regular vidplayback is fine too)
[Captivate Android Development] crecsky:
Are you doing some sort of magic trick to get this "best battery life" on this particular rom? It seems to eat my battery.

I'm using it regular:

Texting

Personal Gmail

Work Email - checking every 5 minutes

Minor phone calls if any in a day

Facebook - not syncing automatically

Twitter - not syncing automatically

Tumblr - not syncing automatically

Wifi on - never sleep

GPS on
[Captivate Android Development] Joecascio2000:
Not sure. I get OKAY battery.

Texting (Very Little)

Gmail (A bunch)

Yahoo (Even more than Gmail)

phone calls (~20 Mins)

Google Account (Everything Syncs)

VERY POOR SIGNAL!!

Something I noticed. Screen on uses a lot more battery than GB but standby time is much better. Also, after 15% it seems to last a lot longer.
[Captivate Android Development] mbc663:
Battery doesn't look calibrated properly. It's going back up at one point in the red
[Captivate Android Development] M3drvr:
I get 6 hours battery life usually. All Gmail sync. Google+ and whatsapp. Near perfect signal. Pretty heavy use. I'm pretty happy with it.
[Captivate Android Development] shane87:
Not a problem, man. Always happy to help any way I can.
[Captivate Android Development] RootTheMachine:
How much % of that time is screen on?
[Captivate Android Development] NightHawk877:
Nice. I could have easily gotten the same as you, but I needed a fully charged phone for the morning.
[Captivate Android Development] MikalCarbine:
My camera has ceased to work completely. At first it would work and FC depending on settings. Now when opening it just hangs completely and won't open
[Captivate Android Development] Mauijpm:
What build are you on? Stock kernel?
[Captivate Android Development] Minor723:
Here is a pic of battery life.
[Captivate Android Development] Joecascio2000:
These pictures say nothing without screen on time.
[Captivate Android Development] RootTheMachine:
Really, anybody can just not use their phone for a day and get battery life like that. I think the point of battery life is to see how long it lasts under normal use. I wouldn't consider 19% screen on to be normal use. These battery life posts are becoming clutter in the dev thread

Sent from my (CM9) ICS i897 Captivate
[Captivate Android Development] mbc663:
What is normal use to you may not be normal to other people. Everyone uses there phones differently.
[Captivate Android Development] Joecascio2000:
Normal use for me is at least 2 hours. But still it not to see how he uses his phone. Everyone knows the screen uses the most battery. So without it we can judge good battery or not.
[Captivate Android Development] mbc663:
Might as well be concerned about brightness too then.
[Captivate Android Development] MikalCarbine:
Glitch 14pre. It didn't work all day and I just force closed and reopened once again and its magically working now :p
[Captivate Android Development] rajendra82:
Since Samsung decided to finally get around to releasing KK4 Gingerbread today, only 13 months late, and many months after we already had leaked native GB ROMs. As a giant F.U. to them I decided to flash Build 13 ICS today. There won't be an official Galaxy S ICS build coming out of Sammy, and they have the gall to lie about Galaxy S not being able to run ICS, so I had to stay ahead of whatever they were doing. Everything is running better than it was under official GB for the most part. I had to flash the gapps fixer a couple of times to get calendar to start syncing, but it was no biggie. I love you teamhacksung. I had hesitated in moving over to your work until today, because Samsung was still providing me with support. It is now time for me to cut the cord and move on.
[Captivate Android Development] Joecascio2000:
I doubt anyone keeps their phone at 100% brightness. So brightness isn't a concern. But like I said screen on time matters. If I posted 10 hours with 4 hours screen on that's short but still great battery life. If I posted 10 hours with 1 hour screen on, that is horrible. If I posted 20 hours with 2 hours screen on (which is my average) that I consider pretty good. Or if I posted 1d 8hrs with no screen on time, how can we compare.
[Captivate Android Development] b-eock:
Full brightness right here :D with stock kernel, will be testing Glitch before he let's the public have it. He is an amazing Kernel dev as he built it from scratch since TeamHackSung wouldn't let him have source. No offense to THS, I love their ROMs that us why I stay on ICS. I have no complaints!
[Captivate Android Development] Joecascio2000:
See I can tell this is great battery life. Btw how is your AOS so low. Mine displays really high but its listed known bugs.
[Captivate Android Development] b-eock:
I truly don't know, it changes in amount every time I flash this ROM(last time about 34%). And I come from a seriously clean slate every time there is an update, that might help it.
[Captivate Android Development] Joecascio2000:
Interesting. I started on Build 13 coming from Serendipity VII. Ill wait to see how the following updates change things up. I may do a complete install from stock->cm7
[Captivate Android Development] dutch55:
Music has stopped error after unplugging headset in Build 13

This has happened a few times on Build 13 in the past day with my wired headset. I have been using Build 13 since it first came out, and had not seen this problem. It occured frequently on earlier builds, do not remember when it stopped happening, my guess is I had not seen it since Build 10 or so.

Since it did not occur for several days after I installed Build 13, maybe it is caused by an app. Anybody besides me wish that manage apps had an option to order the apps by most recently installed? It would be a help in isolating a problem.

There is a possibility it is related to having configured and used a Bluetooth headset. I am not sure if I had used my BT headset on the recent builds when I didn't have the problem, but I did use my BT headset before I saw these most recent Music stopped errors.
[Captivate Android Development] ptesmoke:
Working awesome here..better battery than my g2
[Captivate Android Development] shane87:
I MAY have found a temp fix for those seeing reboots mid-call. I just had a reboot about 15 minutes ago, so when I got booted back up, the first thing I did was add a new profile under setcpu. The profile activates on In Call, and raises the min cpu to 400mhz. I set it with a higher priority than my screen off profile, then I made a call. I talked for 10 minutes with no reboot. I haven't had a chance to test it for longer, being at work, but before I added the in call profile, I was lucky if I could talk for 2 minutes before a reboot. I will do some more test calls tomorrow and see what happens.
[Captivate Android Development] Born2BeMild:
I'm on build 13 and everything is working great! No force closes or any other errors so far.

Some experiences on 12: I had my power button acting up, it worked on it's own rules. Sometimes slight pressure(running your finger over it) put the phone to sleep. Sometimes you needed to press it more than once to register a button press. Or you had to press it akwardly, such as sliding your finger with some pressure over the button to work.

I thought it was a hardware problem i was just going to have to deal with. But then I flashed build 13 and problems have been solved.

Whatever you did, team hacksung, keep doing it!
[Captivate Android Development] Kaik541:
Samsung did not say the device was incapable of running ICS (I really don't know where people get this sentence from). what they actually stated was "it lacks the internal storage to run it with touchwiz and would be an unfavorable user experience." we at teamhacksung even had to increase /system size to make space for AOSP ICS, with touchwiz on top, it would be a joke (if there was even enough space on BML for AOSP as it was). and to anyone (not saying you did) who says "well they should just release AOSP ICS"... that is a stupid thing to say. it's a WILDLY different experience from touchwiz 2.1/2.2 and would a terrible annoyance for the average user (even if you made th update optional).

to those of us who take the device and absolutely trash the original user experience, we want more from Samsung, but we won't get it because it doesn't make sense for them to do it (not just financially, probing us to buy new phones).

and as sad as it is to say, we should be impressed Samsung even did the value pack option and managed to backport a few features (gimmicks) from ICS.

if you want the device to be truly yours, don't expect anything from Samsung, look toward Google.
[Captivate Android Development] KarateKick:
Glitch and TeamHackSung

I thought the work from TeamHackSung and the rest of the CyanogenMod group was all open source?
[Captivate Android Development] Kaik541:
as we have stated before (and eve in the OP), the kernel has been and always will be open source (because of GPL). the ROM can be open or closed based on what we feel constitutes being open or closed (because of Apache). when *we* feel it's ready, we'll open the device trees up by pushing them upstream to cyanogenmod's git.

one of the main reasons we closed them temporarily is because we're sick and tired of people creating custom kernels and ROM's derived by our team's work. all it does is create more people coming to us with issues we have nothing to do with (in the last few pages on this thread and the i9000 thread, there are tons of posts about bugs that come entirely from people using glitch kernel).
[Captivate Android Development] Joecascio2000:
That's smart. The least variables the easier it is to make this rom the best it can be.
[Captivate Android Development] ScottyNuttz:
For people who have had their Captivate for over a year, especially if you are frequent flashers, and their battery is begining to disappoint, I recommend picking up a fresh Anker battery on Amazon for 10 bucks. It made a world of difference on my phone.

It's not 100% fair to compare battery life to older ROMs because your battery is (sadly) always degrading.
[Captivate Android Development] jerkysh:
i got a new battery 2 months ago, a 1650 mAh one... and i got over 2 days (jk, aroung 30 h) without connecting a charger :)
[Captivate Android Development] poncespr:
I can vouch that I have been using this rom with the included stock kernel for three days now, and, apart from the calendar bug, which was easily solved, I have not had a single issue. Not even reverting back to stock before flashing, but jumping from Sparko KK4 btw.
[Captivate Android Development] ryandelman:
Hats off

The developers of this ROM deserve an all-expenses paid vacation to whereever they want to go, for a month.

This ROM runs smoother than and more reliably than stock (on my ph anyway), and so I just wanted to say my little thanks, as I feel there couldn't be enough thanks given to these folks.

Android beats all others, every time, hands down because of stuff just like this.

-Ryan
[Captivate Android Development] shane87:
Not to beat a dead horse, but I am fairly impressed with battery life on this rom. I have 18 hours on battery, with almost three hours of screen on. To me, that is pretty good, considering how heavy of a user I am. Keep in mind, most of this usage was while I was at work, with no wifi, using 3g data. My typical usage is about 15 minutes of calls, a few texts, and lots of web browsing, especially checking up on xda, lol. And, I had my wifi on all night, but not connected, except for a few minutes when I enabled airplane mode, to get data to reconnect.

I am attaching pics of my battery usage graph, and my display power usage as well.
[Captivate Android Development] airtower:
no no no!!!! i will not go a month without a flash! :D
[Captivate Android Development] ThreeofNine:
Per Android Central http://www.androidcentral.com/no-samsung-ics-value-pack-coming

"According to a Samsung source who spoke to The Next Web:

Samsung "will not offer the update due to the hardware specifications of the older Galaxy devices, in that they are limited to and fully optimised for the Gingerbread experience." "
[Captivate Android Development] JoshJ22:
Is anyone getting a "low on storage" ongoing notification? For me, sometimes its there and sometimes it isn't. I honestly have no clue what it means because I have about 10 gigs free on the internal SD card
[Captivate Android Development] speedy_11:
Search the thread. This issues has been answered and talked about so many times already.
[Captivate Android Development] rabi347:
Despite using various captivate modem data is running very slow and not getting more than two bars on the phone side. Is anyone else having this experience. Although it shows "H" most of the times data speed is slow.

Can anyone please suggest how to improve the data speed and get more bars on the phone.
[Captivate Android Development] mbc663:
u have no clue cuz u didnt search. been covered a thousand times.
[Captivate Android Development] saobang3886:
show my batterry use in normal, just call, text, and some other things :D
[Captivate Android Development] mod777:
Loving the rom but having problems getting music to play through stereo bluetooth headset. Pairs fine says connected to phone audio and media audio, but doesn't play through bluetooth.

I have the Sony-Ericson MW600 which is amazing. On CM7 it would say the name of the track on it's led display and could >> or << through tracks.

It works perfect for phone audio, just not media audio. My captivate just plays the audio through it's speaker.

Anyone else having this issue and found a resolution?

thanks in advance

Edit: I uninstalled an old bluetooth app and it started working! nice
[Captivate Android Development] gstern:
Though I don't use a bluetooth headset, media audio works flawlessly on my Bluetooth car kit (parrot), and I am able to control google music with the kit's remote. Doesn't display track info though ( can't recall if cm7 did).
[Captivate Android Development] crecsky:
I've been running it since it came out. I'll probably just upgrade to a Nexus or a SG2 when it gets to that point.
[Captivate Android Development] bentonhall:
I just tried this and it seems to work for me. Thanks for the idea. I set my min CPU to 200 and so far it is working fine. I'll try 400 if it reboots again.
[Captivate Android Development] airtower:
do you get nasty static over A2DP? I do, but never did on a GB ROM
[Captivate Android Development] Nelsocracy:
I use A2DP in my car and have no static issues. Sometimes the next track/previous track buttons won't work until I disconnect/reconnect the bluetooth though.
[Captivate Android Development] andeke07:
Perhaps this is more a JuiceDefender issue, but I'm finding it always seems to jump around in my notification list. Sometimes it will jump around 2 or 3 times before it finally settles - needless to say this makes it difficult for selecting my email or text notifications, as occasionally the split second before I select it they will shift again. Has any one else experienced this?
[Captivate Android Development] mbc663:
whats the purpose for using Juice Defender??? :confused::confused::confused:
[Captivate Android Development] Nelsocracy:
It seems to me that notifications on ICS are added to the top of the list whereas on GB they were added to the bottom. Maybe this is it?
[Captivate Android Development] loserskater:
I believe that when a notification is updated it re-adds it to the top of the list. This has happened to me with weather. I'll get a text/email and when I unlock and pull the notification bar down my weather gets updated which causes it to move to the top and pushes the text/email down... It's an ICS thing. I'm sure with Juice Defender it is constantly updating the notification which is why it keeps getting pushed to the top.
[Captivate Android Development] Kaik541:
that quote has never been tied to anyone at samsung (and they were proven completely wrong since the entire article is about how SGS won't be getting a value pack upgrade when JVU proves that entire sentence wrong).

Let's go with something that actually came from Samsung: http://translate.google.com/transla...ff&client=ubuntu&hs=cKn&channel=fs&prmd=imvns

as even google translate can demonstrate, it all basically came down to "lack of internal storage" (on the oneNAND, not the moviNAND)
[Captivate Android Development] lurkingdevil:
Music app is having issues. Spamming the next track button results in a app crash.

I have had this happen on build 12 and now on build 13, but it isn't there in Known Issues so..Anyone can confirm?
[Captivate Android Development] littlewierdo:
I dont even need to look at any quotes, given that the Cappy never even got an official Gingerbread release, why would anyone expect an ICS release?

The fact of the matter is, Google is the one loosing here.

At least with an Iphone, you are guaranteed software updates for 2 years with no bloatware.

Say what you want about the differences between the OS's, I wonder how many consumers notice that their Android device never (or rarely ever) has software updates?

And then, we could go down the road of security and how the official Froyo release from Samsung is riddled with security holes that Google has patched but Samsung never saw fit to even update Froyo with the fixes Google implemented...
[Captivate Android Development] whyareyou:
FWIW we just got an official GB release.
[Captivate Android Development] malbolgias:
Im having sleep deaths and charge deaths every day on buid 13 stock kernel. If the phone is left un atended for over 5 hours it just dies. Did not happen on any other build and I have been here since build 1.
[Captivate Android Development] bentonhall:
Turns out that setting it to a min speed of 200 and 400 didn't make a difference. I still get reboots during calls unless the screen is left on.
[Captivate Android Development] nkrick:
If you look at the i9000 teamhacksung ICS thread (http://xdaforums.com/showthread.php?t=1363593) it appears there is an issue starting in a recent build that is causing reboots. Below is a quote directly from the i9000 thread:

Even though the same information was not posted in the OP for this thread, it is probably a good idea to follow the same guidelines and give the information pawitp is requesting from the i9000 users. Don't try the test kernel though since it is an i9000 kernel, not a i897 kernel! I removed the URL for the test kernel to help prevent someone from installing it "accidentally."
[Captivate Android Development] nbell13:
Uhh... Yes it did...
[Captivate Android Development] malbolgias:
Thanks for the post, but my phone is not rebooting. It just dies, turns off and stays off. I hope it is related to this problem and a fix is posted for next build.
[Captivate Android Development] b-eock:
you using a 1500 mah battery or larger? and nice no 3G and no WIFI no syncing...
[Captivate Android Development] yohannrjm:
Had this happen to me too. Didn't happen with Build 12.

Even with Build 13, I was able to flash to one of the older Nushor kernels, and that took care of the issue. I think it was the xx38 Nushor that worked.
[Captivate Android Development] sa1yan:
no problems for me on glitch kernel. however, im still having the android os battery bug where android os is stay awake for like a really long time. anyone know how to fix?
[Captivate Android Development] mbc663:
just passing it along.

Edit: i have not tried this yet.
[Captivate Android Development] richsale:
Does anbody know if I drop the Allshare/dlna.apk from gingerbread into /system/app will it work or will I end up breaking something?

I hate to try it and end up breaking something.
[Captivate Android Development] whyareyou:
It will not work as it depends on ouch wiz
[Captivate Android Development] richsale:
Thanks whyareyou
[Captivate Android Development] saobang3886:
stock 1500 mah battery, use 3G network ( not data), syncing enable :) some time use wifi :D
[Captivate Android Development] fishfingers15:
Can I change the font that comes along with this Build 13?
[Captivate Android Development] mbc663:
Try an app called rom toolbox
[Captivate Android Development] ConeyKiller:
Just installed. Came from Fast KK4. Boot looped first as it said it might, just flashed again and booted up just fine. Loving it!!!!! This is how smooth and fast thus phone should have been when we bought it.
[Captivate Android Development] RockRatt:
I cannot guarantee that it will work jn every situation but i decided to test it out for myself. I flashed the other ICS ROM( ICSSGS) and it installed. I know it makes the captivate look like a different phone (i9000 i believe)

Went into recovery and TRIED to flash the Team Hacksung build and got the get prop error. Then flashed the same exact build that I removed the settings from and it flashed with NO issues. I hope it can help those with the get prop errors coming from other roms.

Sent From My KickAss ATT SGS2 SPORTING CM7

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] Joecascio2000:
Best $5 spent. Just the ad blocker makes up the money (sorry devs).
[Captivate Android Development] :
Well you could have copied the "hosts" file in a ROM like Illuminance with ads blocked into the /system/etc folder and replaced the old file and fixed the permissions same as the old one and you could have saved yourself $5. Rinse and repeat on any ROM and ads will be blocked
[Captivate Android Development] Joecascio2000:
Too much work. Plus ad block is only one of the features. Like I said best 5 bucks ever. Plus tibu is hella expensive. And rom toolbox does so much more.
[Captivate Android Development] M3drvr:
Anywhere from 30-45 minutes usually.
[Captivate Android Development] RichIrish:
Best battery life I've been able to get out of my Cappy. Wi-Fi on all the time, if on the road 3G active, auto sync enabled for 3 Google accounts, 2 yahoo accounts, whatsapp, Facebook, Facebook messenger, Gtalk. Google calendar Widgets 2, weather, pulse, Facebook,tweetdeck, score mobile, ESPN score center.

Thanks developers for this awesome ROM.
[Captivate Android Development] ConeyKiller:
Without going through all 4000 posts...other people are getting the sleep death too, right?
[Captivate Android Development] TigerEnigma:
I have had it occur twice, once per build below:

1) Build 11

2) Build 12

I have been using this since build 1, I have not tried Build 13.

Both times it occurred over night and it's not that it "Shuts down", but when you tap the power key to turn the screen on nothing happens, then i "vibrates" as if you just shut it down. In order to get it to reboot, I hold the volume keys and the power button down. Takes a bit, but reboots.

The only thing I changed, as of build 11, was I started using JuiceDefender, not sure it mattered, but thought I would list the only change I made between builds.