yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] WillyWonka23:
Oh! Thanks for the fast reply. I didn't see that part. Thanks! :D
[Captivate Android Development] cfili:
HD recording

A few pages back some of us mentioned that HD video recording was jittery and jumped around when playing it back. Is this something the devs are looking into?

Also I've noticed with the latest nightlies a significant improvement in overall system responsiveness... not sure why, but it is definitely there. Thanks for the hard work!
[Captivate Android Development] XsceneXhippieX:
they changed something in the NEON acceleration that makes things look/feel snappier i believe, but on the video playback, it doesnt "play back" all skippy, it records ****TY and skippy as hell, and it always has, when i got my captivate i was EXTREMELY excited for the HD video recording because i am a sponsored skateboarder that is *required* to film a full length video quarterly and I was expecting the video to be better on this phone than my old HD2 running cm7 because this phone actually natively runs android. but no, i couldnt have been more wrong about that, i actually got ONE out of FIFTEEN videos to record/playback with little to no jitters last night filming my son for his first halloween, that issue has always pushed my buttons and yet i have been quiet about it hoping it was in the works... but it apparently hasnt been. thus I'm now voicing it alongside the post im quoting, video recording/playback on nightlies/stable releases of cm7 = complete ****. either that or my camera is faulty which would also make sense, yet the pros of cm7 (the thousands upon thousands of things it just does better than anything else ever made) outweigh the single con for me still..
[Captivate Android Development] GRACO:
Happened to me.

Settings->Cyanogenmod settings->Performance and remove the enable surface dithering ..

HD video now is ok.

regards
[Captivate Android Development] cfili:
Recorded HD video still stutters with this setting change. Just to be clear, it is the actual recording that is messing up from what I can gather, not the video playback itself.
[Captivate Android Development] XsceneXhippieX:
Yes, i believe you are correct, playing back the crap skippy unusable footage is smooth as silk
[Captivate Android Development] nkrick:
Just in case Team Hacksung hasn't seen it yet, the i896 2.3.3 source is available (http://xdaforums.com/showthread.php?t=1326516).
[Captivate Android Development] XsceneXhippieX:
okay, so cappy GB source (for either cappy) *should* lead us to these things from what ive picked up around these threads since ive had my cappy, please correct me if im wrong:

1. better battery life

2. a tighter kernel to rom integration which would like increase benchmarks and performance (like theres even room for performance improvements at this point)

3. better functionality of hardware (like the camera issues stated in my rant on above, or *oh my god* better GPS performance!)

4. lots of cool things for non-MTD roms that i dont care about because i hate samsung roms :p

pretty much everything that comes from building from source = better, right?

what else might we see betterment in with said source code release?
[Captivate Android Development] Kaik541:
actually, the only major thing we're likely to take from this source is the a1026 drivers... and we're still unsure about that since enabling it will be a one way to trip to ONLY using Captivate modems (so no HSUPA)
[Captivate Android Development] littlewierdo:
For those wondering the i896 is the same hardware as i897. The only difference was branding.
[Captivate Android Development] Gromlakh:
3. The fundamental problem with GPS is hardware, not software, related. The GPS unit in the Galaxy S just flat-out sucks. We can polish it up with software hacks, but at the end of the day it's still bad hardware so there's only so good it's ever going to get.
[Captivate Android Development] cfili:
You have anything to add about the HD recording stuttering? I am very curious to hear if that is something that is on your radar or not.
[Captivate Android Development] XsceneXhippieX:
yeah, i understand that i guess it slipped my mind, i dont think i have ever turned on my gps on purpose anyways, thus this effects me 0% :p

i swear i heard repeatedly that the i896 has no audience chip, but other than that yup, they are identical
[Captivate Android Development] bumbernut:
I'm confused, we can get HSUPA with the i9000 ROM's and decent battery life, can't we?

I was hoping this source was the holy grail.
[Captivate Android Development] Kaik541:
it's nothing I'm working on. if you want a decent video recorder, invest in a flip camera.

whoever told you that was a liar as they are identical boards. it's the same reason you can't use Canadian captivate modems on non-Captivate kernels without getting terrible audio quality.

this source cannot give what it doesn't have. Enabling the A1026 chip will cause there to be hardware audio decoding for voice calls, meaning much clearer in call audio. The side effects will include that you *must* switch away from an i9000 modem. The i9000 modems perform software voice decoding, combining the two results in them being over-processed and the end result sounds similar to static both ways on the call. So to activate this feature, you must use a modem that does not contain software voice processing, such as a captivate-specific modem. By doing this, you also sacrifice HSUPA (but HSDPA is still active).

tl;dr - the same problem i9000 vs cappy ROM's has always had.

PROS:

better voice quality

CONS:

no more HSUPA
[Captivate Android Development] mbc663:
Our phones do take 720p recordings. For a phone, I don't see any reason to complain. Besides missing a flash, what else r u expecting?
[Captivate Android Development] cfili:
HD recording does not work correctly on this ROM... never had problems on others including stock. One would expect the equivalent on CM7, nothing more.

The suggestion of buying a flip cam is basically dodging the real problem. Oh well, everything else about this ROM is fantastic, that is my only gripe.

Sent from my SGH-I897
[Captivate Android Development] mbc663:
Dropping $100 plus on a device to carry around with u, instead of switching to a Samsung based ROM? they're really not that bad :)
[Captivate Android Development] cfili:
Well, when you put it that way ;)

Sent from my SGH-I897
[Captivate Android Development] XsceneXhippieX:
some people hate Samsung based roms, like myself for instance, the color/lack of functionality in comparison to cm7 is too much for me to handle, my personal phone usage has higher standards set by an HD2, a non-android native phone, running cm7, and Samsung roms feel like a downgrade from a franken-phone to me, and I didn't get the cappy to downgrade you know? The device is truly capable of great things, even my HD2 could record things just fine with older hardware and hacked software, so my point is that my phone can record in 720p, and if the gracious developers at XDA feel like working on it then I would be grateful and enjoy my device much more, I don't see what would cause cm7 to have a basic thing like the video recording to be broken after multiple stable releases, I just find it unusual and made an attempt to bring it up in hopes it might get fixed, it can't hurt to plant an idea you know?

Sent from cyanogen mod 7
[Captivate Android Development] bumbernut:
That all makes perfect sense, im not worried about the noise cancellation.

I was under the understanding that the source would provide the drivers we needed to obtain better battery life.

I find that i9000 based roms give me similar battery life as i897 ones do. CM doesn't seem to get as good life.

Do you ever envision a increase in battery life ?

either way i don't see myself leaving cm7
[Captivate Android Development] Aus_Azn:
Personally, I just like the little things that AOSP gives, like a fully TW-stripped interface, universal theming, statusbar tweaks and longpress-to-kill.

Plus, 100% fully up to date, what's not to like?
[Captivate Android Development] RCDuke:
I personally don't mind the small few issues with CM7, considering the battery life has gotten significantly better over time with the nightlies and using the Glitch kernel.

I'm confused on something though: Switching to i897 source would yield better voice quality, but people have mentioned that we would lose HSUPA but keep HSUDA. To my knowledge, the Captivate could not support HSUPA because it is not 'AT&T semi-4G' capable, while it could support HSUDA. Can someone clarify for me?
[Captivate Android Development] mbc663:
I understand what you are saying...hang in there, source will be dropped soon enough. Appreciate the response.
[Captivate Android Development] emuneee:
Unsure about the differences in source between the I897 and I9000. The general rule is that I897 based kernels play better with I897 modems. The same goes for I9000 based kernels.

Oh and its not HSUDA... its HSDPA. And you are right, though I have no earthly idea as to why the I897 was limited to UMTS upload speeds when the hardware is clearly capable.

I9000 modem

Pros: faster HSDPA speeds as well as HSUPA (faster upload speeds - ~1-1.5Mbps)

Cons: No audience hardware voice cancellation

I897 modem

Pros: Audience hardware noice cancellation

Cons: average HSDPA speeds and limited to UMTS upload speeds (~384Kbps)
[Captivate Android Development] Kaik541:
our kernel source is more or less optimized for the i9000 and captivate (and the fascinate)... not as much on the vibrant because it's the little bastard child of CMSGS. there are probably a few things we missed that could help things a little, but we're mostly as good as it's going to get. The biggest battery drain is in the RIL, which is a userland blob that Samsung does not release source to and there's really not much we can do to fix it unless there were to share their source.

the team has requested several times that they stop using the proprietary RIL and switch to the AOSP RIL which works just fine, but it appears that is one of the major suggestions/advice that they are consistently ignoring.
[Captivate Android Development] mcala:
I read somewhere that a minimum overclock/UV would take care of HD video stuttering. Try to OC to 1200mhz. Should hurt nothing.
[Captivate Android Development] nbell13:
to my knowledge, at&t's faux 4g is hspa+, not hsdpa.
[Captivate Android Development] cfili:
OC to 1300mhz with stock CM kernel helps a bit but I still get some stutter.
[Captivate Android Development] CptTwinkie:
I was oc'd to 1200 sometime around the stable release when I shot a bunch of video at a homecoming football game. It was right after the update that fixed the HD video. Anyway I got very little stuttering at all on the recordings...maybe once or twice in an hour of video. It was probably the oc and I generally manage background apps/processes fairly well. Rather than use an appkiller I just don't have things check in very often. Once an hour tops. It prevents starting and stopping in the background which would interrupt video recording.

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] XsceneXhippieX:
I've tried OC'ing and it doesn't help really for what I'm talking about

Yes, but our hardware only supports hsdpa/hsupa

We are talking about video recording, not playback, I think playback is beyond acceptable lol, just when you film in HD, or in my case almost any quality, it comes out skippy, like really skippy
[Captivate Android Development] pwnerman:
I know this is most likely an old question depending on which nighty it was implemented on.but I haven't updated since 120 and I noticed now that when you get a notification the lights stay on. Is there anyway to turn this off? I downloaded the bln app to see if u could turn it off that way but it said bln wasn't found I know I could flash a kernel with bln then turn it off but I like the stock kernel less problems for me. Any ideas?

Sent from Captivate
[Captivate Android Development] tiuk:
I do agree that the GPS sucks. However, my experience has been inconsistent. With my first captivate, bought exactly a year ago when Rogers launched it, it sucked stock, but once I flashed some of the Samsung based group roms (mainly cognition and Darky's were the two I used the longest) and tried different modems I eventually got it to the point that I could call it reliable. Then around January/February when the first CM7 beta was released, I got ready to flash and discovered my captivate's USB controller was fried (my own doing), and I couldn't use Odin anymore (was required to flash initial CM7 at the time). So, I got the phone replaced and immediately flashed CM, which I have been on ever since. What I've noticed is no matter what I try now, GPS is extremely unreliable. I can get a lock quickly enough, but I frequently lose the signal while navigating and it often gets my orientation wrong or thinks I'm on a street perpendicular to the one I'm actually on.

Point is, GPS hardware on my first captivate seemed decent enough with the right modem and tweaks, but I was only ever able to use Samsung based roms on that one. On this second one, GPS has always sucked, but I've only ever run CM. So, there's a gap in my personal experience, and I don't know if my GPS problems are caused by a hardware problem in this second phone, or if it's just a CM issue and I would be having the same problems if I had been able to flash CM on my first captivate.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] mcala:
From what I remember u have to turn off led notifications in all your apps that have it on. Including text & phone calls. The leds don't waste battery from what I read. Check cm settings also in the settings menu.
[Captivate Android Development] bulletproof1013:
Ok on it now. Wow just wow. Thanx. If I needed to go back to stock I hit repartition. Is that correct?
[Captivate Android Development] coderunner:
Nevermind I didn't check repartion the first time now I fixed my problem
[Captivate Android Development] bobbylx:
I never do. From cm7 I just use Odin one click. Just make sure one click is right for your phone.
[Captivate Android Development] bulletproof1013:
Is that to me?
[Captivate Android Development] bulletproof1013:
Ok. Well cm7 install page just said to do so. But I never have
[Captivate Android Development] jmbradd:
So if i'm following this correctly, I cannot flash this as I do not have 3 button working? Dunno why it doesn't, it did when I first flashed over to froyo but it no longer works =/

Was really hoping to flash this today
[Captivate Android Development] bobbylx:
One click may repartition automatically, I don't know.
[Captivate Android Development] coderunner:
After everything is flashed I try to reboot and it just boots back into recovery and says "no misc partition"
[Captivate Android Development] harpo1:
Deleted........
[Captivate Android Development] bobbylx:
3 button is absolutely necessary to flash this. There's no other way to enter recovery without it. Adb doesn't work.
[Captivate Android Development] Scarchunk:
GPS is working well out of the box on a 2.3.2 build I compiled on 2/27. Can't comment as to if anything has changed since then.

I have one of the rare cappys that actually has working GPS to some degree on any rom I run, so ymmv
[Captivate Android Development] bobbylx:
That message is normal for me. It sounds like something didn't flash right.
[Captivate Android Development] jhernand1102:
What about lagfixes, should we disable prior to flashing this?
[Captivate Android Development] Konner920:
http://xdaforums.com/showthread.php?t=812434

Please flash this before you do anything else..
[Captivate Android Development] slifer315:
no, it does not matter if you have a lagfix enabled or not.

Sent from a phone, playing a phone, disguised as another phone.
[Captivate Android Development] The_Zodiac:
is it just me or is anyone else disappointed there isnt a cwm flashable version ?
[Captivate Android Development] cumanzor:
There is a version of Odin One Click that cripples the 3 button combo I think. The unlucky ones should be able to use a jig I believe (not that I am recommending this).

Is anyone else getting an "Invalid image type" message under odin after selecting the initial kernel?

Disregard.
[Captivate Android Development] cchant:
It says that because we don't have a misc partition. Just ignore it. It has no effect on us
[Captivate Android Development] bobbylx:
The ROM is cwm flashable. You just have to use Odin for the kernel. I'm sure if you wait long enough someone will figure it out.
[Captivate Android Development] darkamikaze:
No. This isn't just any ROM.. it's based off of AOSP. etc. etc.

Great work cm team! flashing this when i'm back from sch00led
[Captivate Android Development] grkmaster:
I think what he did was restore some settings from TIBU because I did that and the only two options showing holding down the power button were Reboot and Power off. Silent mode, airplane mode and choose profile dissapeared.

And on the FC issue it was a few that were FCing.. RIght before i decided I need to go back to a 2.2.1 for now, PowerAmp, OpenAlarm when i restored my alarm settings for it was FC as well. LiveProfile as well. There might be one or two more programs but those were off the top of my head.
[Captivate Android Development] comdei:
Any news on the captivate /i9000 getting official nightlys?
[Captivate Android Development] Kaik541:
high quality youtube doesn't work at 100% and if you're on wifi, youtube usually defaults to HQ. make sure you aren't attempting to use HQ.

seems to be related to restoring system data (WHICH YOU SHOULDN'T DO ANYWAY). as for the forcecloses, a lot of that can easily be chalked up to not being properly updated to support gingerbread.

once merged into mainline, this will be a certainty. until then, stop asking or build yourself.
[Captivate Android Development] chipsa964:
Yea I turn off hq and it still shows nothing

Edit: I turned off wifi, and youtube app played videos fine in both hq and regular. Turned wifi back on, now hq also works...weird
[Captivate Android Development] malicenfz:
Used it for 2 days, LOVED it but the battery life is terrible I guess I'll just have to wait until it is a stable build.
[Captivate Android Development] techmik67:
see previous posts about wifi......
[Captivate Android Development] bay_wolf:
You probably used Titanium Backup to restore right?
[Captivate Android Development] RockRatt:
Yes. I downloaded the files and applied them and they ate working fine. I have now swapped between the cm7-jl2 and cm7- jk4
[Captivate Android Development] JBLogic:
Seems pretty reasonable to me,

13 hrs for me at 17% with pretty heavy usage. Was on wifi for about half the day as well.

this is on JK4.
[Captivate Android Development] blazin619:
I am following the sgs cm7 team on twitter and was wondering if all of there tweets are fixes that will be included in the update? I cant really identify with what there talking about but just wondering. If they are tweeting fixes then there working at a really fast pace. I really need to donate.
[Captivate Android Development] Kaik541:
twitter.com/teamhacksung

the old account (cmsgsteam) is being exclusively used for galaxy tab and epic development... all GSM phones are on teamhacksung now. every tweet = one attempt to squash a bug or optimize something, so every time you get a new tweet, it isn't just testing something, it's usually a pretty tested fix. :)
[Captivate Android Development] Haloruler64:
Been running for a few days. Just saying, I enabled the notification that lowers volume of music in the Music settings and in CM settings. What it does is lower music volume, play a notification, raise music volume, then volume goes to 0 and back up to whatever it was. So it still has no sound at one point. Weird, am I the only one with this problem?

Camera/YouTube worked after a few reboots, it seems everything is working well ATM. Only got one random reboot. Took a day for auto rotation to start working. Rotary lockscreen overlaps the album artwork. Very fast and stable ROM, very happy!
[Captivate Android Development] randy_khoo:
is this an alpha build?

Beta build?

Or a RC???
[Captivate Android Development] zyexx:
Anyone found a good Video player that can browse to the external SDCard?
[Captivate Android Development] mcord11758:
I would say beta closer to RC then alpha
[Captivate Android Development] atinm:
Actually - the tweets are teamhacksung tweets on CMSGSTeam twitter feed - we've kept them there. So yes, we're working on CM7 as you can see on twitter.com/cmsgsteam :)
[Captivate Android Development] Matrioux:
Rock Player works fine, you need to go into rockplayer's settings and change the root directory to just a / . By default its /sdcard which means it can't see the external sd directory.

-Matrioux
[Captivate Android Development] nkrick:
AFAIK, the car dock uses proprietary Samsung drivers and the support for the dock may be built into TouchWiz. It is likely that the Samsung car dock will never be supported in a non-Samsung based ROM. If the car dock is important to you, use a ROM from Samsung (or built off of a Samsung ROM).
[Captivate Android Development] MentalDragon:
Most Amazing thing to Happen to Captivate

Thank you Thank you Thank you. This is by far the most amazing thing to happen to my captivate. I have ran almost every rom that has been created in these forums since I got my Cappy. Some where fantastic and played a part in my Cappys life for longer than a few days and some where not what I needed and were soon replaced. This though, guys there is a tear in my eye, is by far the greatest experience I have found for my Cappy. You guys are the greatest. I have been jealous of my wife's HTC Aria that I had installed this on because it is so stable and smooth. Now that I have it Im like a kid who just got everything he ever wanted on Xmas morning. Thank you guys, this is great.

P.S. No Kittens or Puppies were harmed in the installation of this software. LOL
[Captivate Android Development] loraque:
Are you guys sure about this? Isn't it just basic USB audio out we are talking about here? I know Xcaliburinhand added this support to his kernel, but did not realize it touched on anything Samsung specific. Just assumed it was USB audio support compiled into the kernel.

This is me sad, lol.
[Captivate Android Development] shopealope:
I have GB bootloaders on my.captivate and I really, really don't want to flash back to eclair/froyo, am I able to flash this with GB bootloaders? Ill lose my 3 button combo by going back to eclair/froyo

Sent from my Cappy
[Captivate Android Development] mcala:
I'm using the Glitch kernel with a modest 1300mhz OC/UC & I have not tried HD video recording. I will check it out to see if I studder.
[Captivate Android Development] mcala:
You can flash with the GB bootloaders. There are froyo Odin's in the development thread that don't include bootloaders. Check the stickies. Turn off any lag fixes.
[Captivate Android Development] wizurdofawwz:
Does anyone else have problems with Wifi? I've had problems with it initially connecting since the first one I started using around #80. Whenever I connect I really cannot access anything until I launch the browser and load something and then I can finally access the market, etc. Is it the modem? CM7 related?

I'm currently on #160 fully CM7 stock.

Please help, I'm frustrated.
[Captivate Android Development] mcala:
Router running the lastest firmware? I connect just fine with a wndr37AV with wpa2/AES encryption. When you flash do you reset/format everything?
[Captivate Android Development] gilpdawg:
Yes. If you want to go to stock first flash the GB stock package without bootloaders and Boog's kernel. You may have to flash twice if it bootloops.
[Captivate Android Development] nimper:
You really don't need to odin anything before installing CM7.
[Captivate Android Development] Gromlakh:
One thing to note is if you're running an i9000 ROM, you will need to either flash some kind of stock or manually edit your build.prop file. The CM flasher will crap out otherwise because it thinks you're trying to install Captivate CM on an i9000.