yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] uhhhyeahhh:
hi everyone, i tried searching for my issue but with the four pages of results that came up, i couldnt find an answer... so hopefully someone can help.

the first time i tried to flash CM7, i soft bricked my phone (att logo loop). so i was able to go into download, use odin3 to go back to factory ROM. great (except the ROM is 2.1 and not 2.2! which is originally what the phone came with)

anyway, just now i used ROM manager premium to install CM7 (i checked everything, add gapps, wipe dalvik, wipe cache, wipe user info, back up current ROM) and everything seemed to run smoothly until the phone finished installing the ROM and reboots. it basically goes into a loop from the screen that says galaxy s and cyanogenmod then acts as if it's installing the ROM again (for a short period) and repeats....

so i went into recovery and flashed my back up but then i soft bricked my phone, again HAH! so now i'm back to 2.1 stock ROM.

can someone tell me what i COULD be doing wrong? thanks
[Captivate Android Development] RockRatt:
It has been seen/read that SOME people have had to flash CM7 twice for the FIRST TIME installing. It sounds like yours was booting up correctly and I have even seen it go to the home screen with the slide lock then go back and start over with the CM7 bootscreen again, then finish normally. Either way what I WOULD DO is install it, let it reboot (if it makes it all the way through), then go back out to cwm and go to INSTALL ZIP, CHOOSE ZIP, go locate where it was downloaded to (normally clockworkmod/get/ find correct nightly and choose it) and flash it the second time. Then once it fully boots then use the power button, reboot, recovery, then flash gapps (or open up go to rom manager and go through the motions to download and install gapps again).

Just be patient as the first time flashing can take a little while longer since it is doing a dalvich cache wipe. You were ALMOST THERE and SO CLOSE to having it fully installed.

So again to install manually is put it in your SD card (NOT THE EXTERNAL SDCARD). Go to recovery mode, wipe data &factory reset, when done Choose zip from sdcard, Choose zip to install, flash CM7, (let it reboot if it goes to it), go back to recovery if your still in it and flash it again. Then reboot, then back out to recovery (or through rom manager) flash gapps. NOW YOU SHOULD BE GOLDEN.

You will NOT have to do it this way everytime, from that point on you can just use rom manager to install nightlies. Hope this helps you figure it out.

Sent From My KICKASS CM7 AT&T SGS2
[Captivate Android Development] uhhhyeahhh:
thanks. i made the mistake and not move the zip file to the sd card... it was in the external :(

now it's stuck on the same loop! and i cant get into download to use odin3!
[Captivate Android Development] simple man:
I saw in the miui thread that if you continue to hold the recovery key combo through the loops, that eventually it will put you in recovery mode, so you can reflash.
[Captivate Android Development] kschumake83:
I had that and a long battery pull worked. Pull the battery out for about 2 minutes and it allows you to go back into recovery or download.
[Captivate Android Development] loraque:
All those tweaks do, and ever did, is hide the fact that a Captivate with crummy GPS is providing bad position data. I have a 1007 that has bad GPS- it locks, but will drift randomly. Tap the Bluetooth GPS widget, no GPS data clearing required mind, and I get 1m accuracy with no skips. It is entirely a hardware issue.
[Captivate Android Development] ballz0iron:
Not sure what your setup is but my HD recording appears fine....
[Captivate Android Development] cfili:
Mine usually starts to skip around 12 seconds worth of recording. Are you OC and on default kernel?
[Captivate Android Development] tbrummell:
Go get a GoPro, problem solved. :)
[Captivate Android Development] mcala:
Ok I just filmed two 30 second clips, 1 using the HD setting & 1 using the YouTube HD setting. No stuttering during filming or playback. I am OC/UV @ 1300mhz with the Glitch kernel w/ #165 release of CM7.
[Captivate Android Development] cfili:
I'll have to give Glitch a try, just patiently waiting on them to release v13... from what I understand v12 does not have LED notification support which I need.
[Captivate Android Development] XsceneXhippieX:
Only tweaks I'm using are v6 supercharger, which doesn't have anything to do with the camera.apk or whatever is causing my skippiness, but mine skips randomly, never predictable to any point, sometimes after 1 second, sometimes after 4, I use pimpmycpu to UV -75 on every clock speed and oc'ing hasn't helped, and for the record its been this way since I got my cappy and I always thought it was a hardware issue (never used a Samsung ROM on this particular phone) until somebody else brought it up and related it to my software, ranging from nightly 80 something to nightly 163 that I'm currently running, it even skipped on glitch kernel that I normally used before this nightly because the free glitch boot loops me on this nightly every time, I'm in the stock cm kernel experiencing the same issues, So that's my bug report, if I can logcat it or something to help I will but I think its reproducible on many devices within 4 seconds of recording anything, I'm starting to think my UV might be the culprit, I'm going to experiment with it some more

Sent from cyanogen mod 7
[Captivate Android Development] airtower:
There's a v13 RC available if you purchase the app in the market
[Captivate Android Development] throwawayaccount9500:
How do you install the glitch kernal...on the latest nightly right now
[Captivate Android Development] EnemyOfGlaDOS:
Whooah horsey.. wrong thread. (Flash in recovery)
[Captivate Android Development] uhhhyeahhh:
thanks for responding! i tried both ways and i still cant get into recovery or download. :(
[Captivate Android Development] cbasse:
You've probably already seen this, but looks like there's some Captivate-specific changes coming down the pipe on the next nightly... :D

http://cm-nightlies.appspot.com/?device=captivatemtd
[Captivate Android Development] shopealope:
Thanks everyone for replying, ill give it a shot. I have pinnacle 1.3 right now so I should be good to go.

Sent from my Cappy
[Captivate Android Development] Keland44:
How possible would it be to use the AOSP RIL on the cappy or is that like opening pandoras box? i wonder if we could sign an online petition for them to release the source wouldn't them not releasing it violate the opensource laws?
[Captivate Android Development] XsceneXhippieX:
im broke :p new kid/college at 19 years old keeps the budet tight

good for you! im glad your phone works better than ours :p im hoping to achieve the same

again.. literally broke lol i loved v12b3 anyways and v13 will be public in time so ill use it then :)

this is EXACTLY why i mentioned the camera issues repeatedly :) plant an idea and the AMAZING devs here on xda and associated with cyanogenmod in general take action, thats my favorite thing about open-source information, and overall nice people :) device specific settings changes/libcamera something or other right after i mention it in the threads makes me overwhelmingly happy to be a part of our community, keep up the awesome work guys!
[Captivate Android Development] loraque:
I will be watching to see if this resolves the camera. I tried it again just yesterday, and I get the tearing effect from the video camera, with Glitch 13, with 1.2 OC no UV, during a slow 180 degree pan about 3-4 times. The comments about an additional camera are bunk... this phone takes EXCELLENT photos and videos, and is part of the reason I am using it! Three kids, need to snap a lot of pics and vids...
[Captivate Android Development] Kaik541:
we actually used to use the AOSP RIL a long time back. But it caused the modem to crash a lot and you'd get a lot of modem dump files on the sd card that didn't have any useful info for us.

as for open source, I think people are confused by what that term means. Android isn't as open source as you all seem to think it is. While it is certainly far MORE open than say iOS or WP7, it's still licensed under the apache license (only the kernel is GPLv2), which means anything in userland doesn't have to even remotely be open sourced and manufacturers are allowed to keep it as hidden and locked up as they want (this makes sense from a commercial standpoint... why would someone want to develop on a completely open platform as they'd have to release all their changes and then there'd be nothing unique about their builds... hence why things like Sense and TouchWiz and Blur even exist in the first place).
[Captivate Android Development] littlewierdo:
Lets clear up the gps issues.

There are basically three issues with the gps on the Captivate.

1. The antenna is a VERY short wire that is designed to make contact with the metallic backing of the phone (to be clear, not the metallic battery cover but the metallic backing underneath the battery). If you are adventurous, you could take the phone apart, locate the antenna and 'very carefully' pull the wire back slightly so that is parallel with the phone which should cause the antenna to make contact with the back of the phone.

This is a design flaw, first, because they used copper instead of another more stiff metal and secondly because this antenna is not secured or forced to stay vertical, it is literally hovering with gravity pulling it downwards so that it does not stay in contact with the back of the phone. Do a Google search and once you see how it is designed, you'll understand.

2. Power consumption. Some Captivates cannot get enough power to the gps to function correctly with every radio on the phone turned on. This luckily is an easy enough fix, turn off your radios (wifi, bluetooth, if you have map access stored locally, cellular data) and see if that helps. And yes, you can ignore the 'wifi should be on to improve accuracy' message. Wifi ONLY helps to get a general location initially and then the gps lock takes over, the wifi only used again if gps locks are lost.

3. For lack of a better word, drivers/software/Android wonkiness. Ive used every gps fix in the book and the two that work for me are plumbob (when I was on Cognition) and mysteriously, CM7 works stock. Any other simply does not work. You can try GPS Essentials on the market and it may or may not help with getting faster locks but no tool on the market will help with maintaining a lock.

A little tip for those with 'floaty' gps, turn off wifi, that should help.
[Captivate Android Development] shopealope:
Just flashed cm7 nightly on my captivate with gb bootloaders and its running awesome. Glitch kernel v12 too of course :) awesome rom!

Sent from my Cappy
[Captivate Android Development] nkrick:
Any chance of two versions? One with audience support and one without? If not, perhaps it makes sense for stock CM to support audience (as a feature included with the phone) and AT&T modems, but other kernels (such as glitch) could choose to leave out audience and use non-i897/6 modems.
[Captivate Android Development] cfili:
Yep same here, I use it a lot for quick vids/pics of the kids.
[Captivate Android Development] spiritssight:
Hi Devs,

I my self would prefer audio chip as I use LTE hotspots for internet with phone. Keep up great work.
[Captivate Android Development] nkrick:
Nightly 167 is available and probably has those changes in it. For some reason the changelog doesn't update to show the latest nightly is ready until long after it is ready. http://download.cyanogenmod.com/?device=captivatemtd
[Captivate Android Development] tiuk:
Bummer. Only radio I have on when I'm driving is cellular, stopped using Bluetooth because having that, GPS, and cell on all at once drained the battery faster than it would charge, even in AC mode. Guess my problem is my antenna. For the antenna you mentioned carefully pulling it back, are you referring to the part that is visible when you remove the battery cover? I think you are, just wanted to be clear because you said "take the phone apart", which to me would imply using a screwdriver.

Thanks for the post. If bending the antenna doesn't do the trick, would it be possible to solder an antenna to it? I recall someone posting about attaching one to the round connector (like you see on mini PCIe wifi cards for laptops, but I'm pretty sure they also said after they removed it the connector was destroyed.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] CptTwinkie:
The word leaked from Samsung is that the round connector next to the sim card is an antenna connector for the wireless radio(phone). If there is gain increase in the GPS signal by attaching a GPS antenna it is only due to proximity to the GPS circuitry. The former samsung employee goes on to speculate that the GPS unit is poorly designed resulting in inconsistent and possibly erroneous results.

That's the best insider info I've been able to dig up in a year of looking.

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] kimocal:
Does anyone has any issues with the camera losing connection? Maybe it's just the particular program I'm using (DailyRoads Voyager) but I will lose connection to the camera after a bit and then need to restart the phone to get it working again.

...or is there any way to reconnect the camera without having to restart?
[Captivate Android Development] RockRatt:
This also was said last year sometime that you can ALSO take an eraser to the battery backcover where the antenna touches it. It is a square box. It can get corrosion on it and look whitish in color. I did that last year sometime when the cappys first came out and it does help. Their are TWO antennas on the backside under the battery cover. One is for your radio signal the other is for GPS if I remember correctly. You can lightly pry either/both of them up to make better contact. Somewhere in the captivate forum there is a post about it.

I had/have two out of my 3 cappys still that are 1007 models that always had good GPS. They would stray off course when all we had was eclair and early froyo leaks. Once I went to cm7 I NEVER had any issues with GPS straying off the roads while driving or losing signal UNLESS it was a heavy rain day/heavy cloudy day. I know I was one of the lucky ones, but most 1007 builds were pretty good. I got my first Cappy about three weeks after launch.

Sent from My KickAss CM7 Captivate
[Captivate Android Development] gilpdawg:
I've got a 1007 as well and GPS has never been good. I've given up on ever having decent GPS on this phone.
[Captivate Android Development] kimocal:
All the captivates I've used (wife's too) have had terrible GPS. We've gone thru 5 total. Glad I've kept my bluetooth GPS from back in my WinMo Imate Jam days.
[Captivate Android Development] tiuk:
So there's really not much else I can do besides getting a Bluetooth GPS?

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] smithisize:
On nightly 167, I can't get LED notifications, or BLN to work. I've tried platypus, glitch, and stock. It won't work :/ it worked before though. Any ideas?

Regards

Smith
[Captivate Android Development] shadvich:
I've never gotten BLN to work on any combo of CM7 and glitch. It'll show as enabled in BLN Control, but when I get an notification, nothing happens (though I can still press the buttons with the screen off and get them to light up). Maybe try using blinky to control?
[Captivate Android Development] ballz0iron:
My original cappy (power button stopped working, acted like it was stuck in, was a 1009 build) wasnt perfect on gps but it wasnt too bad, and right now ive got a refurb 1012 and its pretty darn good
[Captivate Android Development] smithisize:
Is there a working zip with updated scripting? I can never get the root function of it to properly install the libraries, and old scripting doesn't work in cwm3 :(

Sent from my SGH-I897
[Captivate Android Development] GRACO:
I noticed than my battery connected to AC will charge to 100%, and after 1 hour will start dropping until 95% without disconnecting the AC cable!

I try to disconnect and connect the cable again will say "Charging 95%", after few minutes to "charged" ... When I disconnect the AC cable the battery indicator will be 95% =/

I calibrated my battery like 4 times, and no change, may be is problem from Glitch kernel?

regards
[Captivate Android Development] Javs2010:
I've had this happen to me too a couple times

Sent from my CM7 Captivate with glitch
[Captivate Android Development] jjtitus098:
Pretty sure this is a common problem with Gingerbread. It does it to keep the battery healthy and not over-charging, if that makes sense. At least this is what I've been told. Someone else might know better.
[Captivate Android Development] Gromlakh:
Pretty sure you're right. I believe it charges to 100%, then stops charging to preserve the battery from damage. If it detects your battery drop back down to 95%, it starts charging again (I think).
[Captivate Android Development] tiuk:
I believe this is common for all devices that use LiIon batteries, it preserves battery life. Without it it would rapidly cycle between charging and discharging at 100%. Pretty sure the only reason some devices show the drop and others just display charged or 100% is down to how the manufacturer chooses to represent it for the sake of the user.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] Soy_Filipo:
I know its a nightly, but how stable is it?

Sent from my Galaxy Captivate, not that you care, just saying...
[Captivate Android Development] GRACO:
Oh! that makes sense! ... thx!
[Captivate Android Development] Aus_Azn:
Very stable.
[Captivate Android Development] ghost13:
ok so first time added a rom to my captivate. running night build 11-03-11. do i need a different modem? i am running build gwk74 and baseband t959tljl3

how do i tell what modem i have? i tested phone calls/sms/mms/gps and all are working well.
[Captivate Android Development] RCDuke:
The baseband IS the modem; you're running the stock CM7 modem which is JL3.
[Captivate Android Development] ghost13:
thanks for the info RCDuke... do i need to change my modem? are there better ones than the stock one? new to android. was on the wm6.3xx side before:)
[Captivate Android Development] nbell13:
not unless they decide to implement support for the a1026 audience chip. otherwise you should be fine.
[Captivate Android Development] ghost13:
thanks nbell13. i guess i'll just play with this rom and see how i like it:) very stable so far
[Captivate Android Development] iphone=closedsystem:
Yeah, the nightlys have been stable for quit some time. 99% missing very few if anything as of now.

Quackafella Records INC
[Captivate Android Development] ghost13:
ok million dollar question here....

some of my progs need to see my external card as "external card" but it is showing up as "emmc" anyway to change this?
[Captivate Android Development] littlewierdo:
In short, yes, it is standard for the battery to drop to 95%-97% and then fully charge back to 100% on CM. Based on my understanding, CM is actually reporting the battery charge level CORRECTLY where as, most roms bias the full charge because they are not polling the battery hardware as often. This is why on many roms outside of CM you will have 100% battery when pulling from the charger and it will reduce very slowly at first and once you get to 65-75% you will notice it drain at a much faster rate, on CM, you will notice the battery drain is pretty consistent starting at 100%. There is also some things dealing with the charge level of each cell and making sure that each cell is charging correctly and making sure the level of charge between each cell is even. Too much to get into, battery technology and management in electronics today is much more complicated than say 2-3 years ago.

Props to the CM team on this by the way, I have been VERY impressed with the battery reporting in CM (I know it is kind of stupid but I prefer a pure accurate reading rather than my phone staying at 100% for 2 hours and then mysteriously dropping like a rock).

For the hardware GPS fix I mentioned earlier...

http://xdaforums.com/showthread.php?t=878970
[Captivate Android Development] tiuk:
My thoughts exactly on the battery reporting, I much prefer to know where I stand on a linear (or at least, mostly) scale. I don't think balancing cells comes into play in this case, every cell phone battery I've taken apart has been a single large cell.

Thanks for the link.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] Aus_Azn:
So these recent Captivatemtd focused changes... What exactly did they do?

Demarcated as Aries, does that mean it only affects those on Aries-based (KC1, JL2, etc.) modems?
[Captivate Android Development] iphone=closedsystem:
Sorry if it's a repeat reply but in regards to the GPS, no there really isn't much else you can do as far as I can find out on any search it boils down to poor design of the hard ware on the device by Samsung and the cm 7 guys have done the best possiblea far as soft ware can go to help improve it.

Quackafella Records INC
[Captivate Android Development] brandon_L:
I flashed the latest nightly, 168, and the battery is dropping like a rock. Anyone else noticing this? At work, so I'll flash back to 167 for now, it was working well for me.
[Captivate Android Development] mcala:
I have not noticed that. Did u try clearing battery stats then reboot?
[Captivate Android Development] atinm:
We could do this now, but then we'd lose HSUPA (ability to run Galaxy S modems). So for now we're leaving it alone.
[Captivate Android Development] mnjm9b:
Oh...please do this now....

I am sure there are more than enough users who would prefer the audience chip to actually work.

I for one, am one of the unfortunate users that have to use a captivate modem in order to maintain signal. So I always have people complaining how horrible I sound.

I would prefer not to have to use an alternative kernel but could that be an option to at least add the framework support for the chip and then allow alternative kernels to actually use it.
[Captivate Android Development] shaolin95:
And I hope it stays that way. I do not want to lose HSUPA (which also made my downloads slower) for any reason. :)
[Captivate Android Development] gabby131:
No please don't kill HSUPA! Kill my cat instead!
[Captivate Android Development] shaolin95:
hahaha yes kill his cat!

Heck, I will throw in one of my gold fish too as part of the sacrifice! :D
[Captivate Android Development] nbell13:
I for one have no preference, as I'm usually connected to wifi, however call quality seems adequate with the stock CM7 modem too.
[Captivate Android Development] Aus_Azn:
I definitely would have HSUPA preferred...

<sarcasm> I mean, who ACTUALLY calls people with their phone? </sarcasm>
[Captivate Android Development] Gromlakh:
Is this because of a lack of source code? 'Cuz I would think with the recent Rogers GB source code drop that it would at least be possible to implement Audience Chip support on an i9000/HSUPA modem. Or is there another problem I'm not aware of?
[Captivate Android Development] CptTwinkie:
The code in question is proprietary, not open source, as I understand it

Sent from my Captivate w/ CyanogenMOD and Glitch