yashsingh1/xdaforums huggingface dataset:
[Captivate General] hauj0bb:
I'm personally on my second phone and my second battery, and I'm still experiencing issues. Going to wait until the HTC Inspire 4G has refurbs available, and then try to get them to replace it with one of those.

Funny thing is, both my original device, AND my current replacement device we're not affected by this manufacturer defect.

So it's not just limited to those devices.
[Captivate General] Miami_Son:
Since buying my Cappy in mid-December I've had 4 random shutdowns, the most recent was yesterday. All have been spaced out by about a week or more, not one after the other like so many in here. The first 3 happened when the phone was in my leather case, so I thought they might be temperature related. I also thought it might be the stock ROM because I was having lots of other problems. A week ago I flashed Andromeda 1.2 and it cleared up all my other issues. Then I had a random shutdown yesterday while the phone was out and sitting on a table connected to the charger. Now, I'm worried that it will continue since my IMEI is in the range and it is a 1007 build. I really don't want to go through the hassle of a return because my shutdowns don't sound like what I've seen reported.:(
[Captivate General] Miami_Son:
Just got off the phone with AT$T warranty. They're sending me a refurbished phone. The first lady I spoke with was aware of the problem, then she transferred me to warranty and the jerk said he had no official notice of such a problem with the Captivate. I had to make a stink and he finally agreed to send me a replacement. Guess I'l be doing another Odin flash soon. What a pain.:(
[Captivate General] atldawg:
That was my plan, to wait on the refurb Inspire. I lost count, but my last replacement was number 6 or 7. First two within 30 days for GPS (right at release, not realizing that it was a Galaxy series issue. The other 4-5 were for shutdowns. I have a device support center near my house, so I could swap at will. Well, I finally had enough and called AT&T. They told me I would have to wait until they had refurbs, which could be up 6 months (i doubt that, but that's what I was told). I swapped it out again, and decided to wait. I left it stock, and remembered how bad the stock phone is. I got fed up, and decided that I was going to go buy an Inspire, and sell my new refurb Captivate to cover some of the costs (it still has plastic wrapping on the body) I decided to call AT&T one last time, and take the nice guy approach. I went straight to "cancel service", which means no hold times. I nicely explained my situation (again), and the lady apologized, gave me a $260 credit on my bill, and I went and bought the Inspire off contract. Moral of the story, the warranty department will/can do nothing but send refurbs. Retention can give you credits. I am not sure how they determined my credit amount, but it was more than I had hoped. I'll sell the captivate and come out ahead.

I'll keep it brief, as this probably belongs in another thread, but the Captivate was my first Android phone, coming from and iPhone. It almost ruined the Android experience for me. The Inspire is a completely different phone. The phone, out of the box, is so far superior to the Captivate (even with Cognition ROM - which is the only reason I had the Captivate for as long as I did) that it blows me away. I will not miss one thing about the Captivate, and will not be buying a Samsung phone anytime in the near future.
[Captivate General] flo7002:
I'm on my third captivate, but I was talking to a salesperson at the local ATT store and he said that if you have to have the phone replaced more than 3 times they should give you another model of comparative value. Since you had your replaced so many times, did you ever ask them to give you a different model/make?
[Captivate General] ou812bkewl:
I had the issue on a 1009 build and got mine replaced. The one they sent me is a 1007.
[Captivate General] joeyl:
same here. and it has not shutdown on stand-by yet....
[Captivate General] Gr8Danes:
Got my wife's replaced the other day for this. Funny thing is that the tech diag. line wanted us to monitor it for another 24 hours after we did a factory reset. I can't blame them for that, but when they called back and my wife told them that it shut off twice, they said "Only twice?". They wanted her to monitor it for another 48 to 72 hours. That was f'n hysterical. I called them back and asked what the hell that was going to do? They finally sent us a new one (or refurb), and no problems thus far.

As soon as we got it, I dropped a custom ROM back on it. ;)
[Captivate General] Miami_Son:
The more I think about this, the more pissed I am getting. AT$T knowingly sold me a phone it had reasonable suspicion would be defective. I bought a brand new phone and less than 2 months later I am having to exchange it for a used and refurbished product because of this known defect. I don't know of any other product that a consumer would be forced to accept replacement with a used/refurbished product after only a few months for a known defective item. Why is this acceptable? I should be able to get a new phone, which is what I paid for. How do they get away with this?:mad:
[Captivate General] hauj0bb:
I can also attest to this.. and I actually wouldn't have even thought of this had I not read this post.

Strange.. is this a hardware or software defect?
[Captivate General] jel7:
Hey man what number did you call?? What did you do? I keep getting sent to warranty and I don't want to be spent a refurb.
[Captivate General] hauj0bb:
I'm thinking that if the captivate is shutting down because it gets cold, maybe something like the battery connections are shrinking slightly, causing the device to power off?

I stuck 7-8 layers of scotch tape on the bottom end of the battery to make it a bit more snug, will report back.
[Captivate General] Miami_Son:
Interesting. The one I'm sending back is a 1007.
[Captivate General] Miami_Son:
Every time mine has shut down, I have to pull the battery to get it to restart. That would indicate it is not just a loss of battery contact issue.
[Captivate General] hauj0bb:
That doesn't happen to me though. I've never had to pull the battery to get it to restart. Strange .. seems to be multiple different 'shutdown issues' here.
[Captivate General] Pierce533:
My Captivate is outside the IMEI number range listed in the PR, being ...55578. I still had the shutdown issue. I called Samsung and talked with a tech and told him what was going on with the phone. He immediately asked me to RMA the phone for repair. I have to admit they did a good job with the RMA. They paid for 2nd day shipping there and back, and they had my phone fixed within two business days. The tech report was that they replaced a TIB (I have no clue what that is) eventhough they could not reproduce the issue. I have not had a shutdown issue since. Here's an interesting point though. My wife's Captivate hasn't had the shutdown issue, and she never uses wifi or bluetooth. I used both and left them on. I didn't think to try turning them off to see if that resolved the shutdown. I suspect whatever the TIB is, it might have something to do with what ever circuit board the bluetooth is built on.

Anyway, Samsung did a great job turning the phone around for me, and since I have a spare phone, it didn't affect me all that much. It is good to finally have it fixed.
[Captivate General] hauj0bb:
Following up on the temperature-based shutdowns:

I put several layers of scotch tape on the back end of the battery for a more snug fit yesterday morning, and I'm happy to report that my device did not shutdown last night.

I will continue to test this and report back.
[Captivate General] hauj0bb:
No go, shutdown twice last night.
[Captivate General] Miami_Son:
Sorry to hear that. My replacement phone was supposed to be here yesterday.:mad: I'm lucky in that my shutdowns happen a week apart or so, but I never know when and it is a real pain when it happens and I don't know for hours. I insisted on a replacement because I didn't want the hassle of a repair.
[Captivate General] hauj0bb:
Yeah, I'm gonna be heading to my local device support center pretty soon. I'm hoping that if I raise enough hell, they'll give me an inspire (if they have refurbs yet).
[Captivate General] LightningGA:
My phone has recently gotten worse. The other morning my phone must have shutdown at least 6 times. Everytime I took it out of my pocket it was off. Called samsung today, they are paying for 2day shipping to them and back. They said that it should only take them 2 days to fix it. I also complained about my sh!tty gps in hopes that they switch the gps chip out for a different one and I am also having the random flashing home button problem. My phone does fall into all the affected ranges and is a 1008. Its going to be hard to go back to my Samsung Impression for a week :(

Sent from a phone using an app.
[Captivate General] Miami_Son:
:mad::mad::mad::mad::mad::mad::mad::mad:My replacement got here on Friday and I had 4 random shutdowns in less than 18 hours. Called AT$T on Sunday and raised holy hell when I saw that the replacement was also within the affected IMEI range. They sent me another one overnight. It got here a little over an hour ago and I've done nothing but turn it on. Already had a random shutdown 20 minutes ago. Looked at the IMEI # and, you guessed it, is also within the affected range. I'm so mad I could spit nails!!!!!!:mad::mad::mad::mad::mad::mad::mad::mad::mad:
[Captivate General] skullvet:
Exactly, I am waiting for news that someone has done this successfully and if they were able to choose between an Inspire or an Atrix.
[Captivate General] loonieryan:
Same problem here: I'm on the Rogers stock 2.2, had Perception before but did a clean flash of stock, wiped data/factory reset. When the battery is at 100% the phone tends to die. Doesn't do it any other time.

I did install the Voodoo lagfix for the stock Rogers kernel.
[Captivate General] Miami_Son:
Well, number 3 has been OK so far. Up and running on Andromeda 1.2 since I got it on Tuesday. No shutdowns, but battery life hasn't been as good as it was on that ROM on my first phone. Probably needs the stats to stabilize a bit. Stock Froyo was a real disappointment and Cog.4.1 had terrible GPS. Fingers crossed.
[Captivate General] mfpmax:
After not having the issue, I started getting the issue after flashing a rom. Returned to stock(rom was draining battery insanely fast) and it started having the issue. Sometimes its random, but it occurs almost like clock work at around 40-50% battery.
[Captivate General] maxjivi05:
I noticed some roms caused my phone to shutdown at certain %'s but all is good now

sent with Captivate w/ Gingerbread 2.3.3
[Captivate General] elfie:
Got mine exchanged today..

Original was 1010 3518X...X7784

Current is 1007 3518X...X8910

Went to the device support center, just told them my phone randomly powers off.. they said "unfortunately" the only thing we can do is replace your device, I agreed.

Came with JH7 upgraded to KB1, removed all Samsung and AT&T bloatware and applied lagfix.

Charged it to 100% once No shutdowns so far.
[Captivate General] feilian:
Does the issue still exist on the newly released stock Froyo?
[Captivate General] reinbeau:
A hardware issue isn't going to be fixed with a software fix.
[Captivate General] Coak5:
One thing I've done to (so far) prevent the random shutdowns has been using Voltage Control app to set my minimum hertz at 200 Mhz instead of the default 100 Mhz and so far it has worked good even with UVing it at -125. Before I UV'd my 100 Mhz and UC'd my phone at 800 Mhz and it only happened once the entire time I was running my Precision 3.5 ROM after 2 weeks so that's when I decided to up the minimum to 200 Mhz. So far so good, you guys should try it out.

P.S. I had it the worst when I was on 2.1 that I needed to download the Captivate Keep Alive app from the market and set my threshold to 30 percent in order to prevent the random shutdowns at 80% battery. Even when my Precision 3.5 ROM randomly shutdown it was around 80% also before it happened. That's one thing I've noticed.
[Captivate General] bames:
Part 1: Replacement Phone Saga

Received 1st replacement phone tonight. Things were great because the phone arrived in 24 hours.

Unfortunately:

1. The phone was in the imei range of affected devices

2. While the body of the phone was flawless the screen had a 1/2 inch by 1/2 inch M scratched nearly in the center.

Called in and 2nd replacement on the way =)

Lady said they shouldn't have sent a phone in that imei range but then also told me she couldn't promise the next phone sent wouldn't fall in that range but she was hopeful it wouldn't because those should be removed. Told me to call back if it was.
[Captivate General] Miami_Son:
She's a freaking liar! My first replacement was in that range and so was my second, which I'm now using. Luckily, it has not shutdown yet in almost a week. They are simply taking their chances sending out supposed refurbs from that IMEI range. What does it cost them but a little shipping? We, the customers, are the ones being inconvenienced.:mad:
[Captivate General] bames:
it was actually fortunate it had such a blemish on the screen it made the whole replacement a non-issue. She asked if it had shutdown yet and i said "i don't know and i am not going to find out. I saw the scratch on the screen on the first boot when i removed the plastic from the front and shut it down"
[Captivate General] Miami_Son:
I hate to say it, but what do you want to bet the next one is in that range, as well?
[Captivate General] bames:
about 95% certain i will get another in that range.
[Captivate General] bames:
the idea of a refurb doesn't bother me i just don't want one in the affected range.

I have purchased refurbs on multiple occasions (tilt, tilt2, ipods) but i have never received a refurb with such an apparent physical blemish as was the case with the screen on this phone. Seriously, how do you not see the some has scratched and M (or W depending on which way you hold it) into the center of the screen?
[Captivate General] Dante04SRT:
... Are people buying NEW Captivates that are still having this issue? My first Captivate (mfgr'd 12/19/10 - purchased 2/4/11) had the shutdown issue.

I've had two since then (one still fell in the IMEI range, the other doesn't) and NEITHER had the issue.

I've seen enough evidence to suggest that the IMEI range no longer matters (if it ever really did). Bottom line, if you replace your phone, don't worry about the IMEI range - Just make sure you get documented record of "if it still does it, We'll replace it" kinda lingo.
[Captivate General] bames:
that other semi-annoying thing is that they are still sending out the refurb/recond w/ jh7. Not a biggie but as much trouble as some have had with kies and the updates you would think they would have the on 2.2 OOTB
[Captivate General] Miami_Son:
I was actually glad it didn't since I knew I would be going the custom ROM route and didn't want to hassle with the 3e issue of Froyo or with having to Odin it back to JF6 to avoid it.
[Captivate General] bames:
point well taken same thing here...even though both issues are easily remedied in 2.2 it is OOTB easier to root and get to a custom from jf6 or jh7.

I was speaking more in terms of product support and providing the end user with up to date software when they receive their device.
[Captivate General] Miami_Son:
This is AT$T and Samsung we're talking about.:D
[Captivate General] sween01:
The flurry of conflicting information and misinformation on this topic has had me baffled for a few weeks now. Yesterday, I went to an AT&T Device Support Center. There were two guys behind the counter who seemed to be genuine, seemed to know what they were talking about, and seemed to be trustworthy, which is more than I can say about some of the various other people at AT&T and Samsung that I have dealt with.

I asked, simply, "If I want to buy a new Captivate that doesn't have the shut down problem, what do I need to do to ensure that I am getting one of the good ones?"

So, for what it's worth, here is what they told me:

- The shut down problem is caused by two completely unrelated issues. One is hardware and one is software.

- There definitely was a hardware problem with the units that were manufactured earlier. Get one with an IMEI that ends with a number higher than 5394. In terms of this problem, it doesn't matter what the other digits of the IMEI are. So, if you're like me, for example, and you're only finding units with an IMEI that begins with 351, don't be concerned with that. The 351 units weren't necessarily built before the 352 units (352 being the first three digits of the IMEI that was mentioned in the memo).

- There definitely is a software problem with 2.1 that can cause random shut downs, regardless of your IMEI/manufacture date. If you download 2.2, that will solve the problem.

They then asked me why I want to get a Captivate, versus another model. Long story short, they think that the Captivate has enough other problems to warrant avoiding it. They're big on the Inspire, as well as HTC in general. They're not big on the Atrix, and believe that the second core of the dual-core processor is a waste, and goes unused, for tech-speak reasons that were over my head.

That said, I like the Captivate over the Inspire, due to some of my own personal preferences (assuming that it works properly). So, I guess I'm going to roll the dice and try for one again, armed with the information that they gave me.

I hope that information is reliable, and that it helps some of us.
[Captivate General] elfie:
The IMEI range does not seem to make sense, I had 351....7784, which is definitely 5394 but it still had random shutdowns even after 2.2 and also with other roms based on i897 and i9000. So I think the hardware issues is there in phones other than the mentioned IMEI range.

Unless of course 351 comes before 352.
[Captivate General] sween01:
Really?......Sh*t, I thought the info I got was too good to be true.
[Captivate General] elfie:
I think it is more like luck... but atleast they are now exchanging the defective phones without too much fuss.

I have had my replacement device for 4 days now, no shutdowns so far.
[Captivate General] sween01:
I wonder why they haven't just pulled these phones from the market, like all of the other ones that appear, then suddenly disappear from the lineup. Maybe they have too much invested in the Captivate? Maybe they don't want to be the only carrier of the major four without a Galaxy S phone? Hmmmmmm.
[Captivate General] godpancho:
no why i love the samsung captivate
[Captivate General] Miami_Son:
The same reason Ford didn't yank Pintos and Bronco IIs out of circulation when their problems became known. It is more cost effective to the manufacturer to just let them fade out from attrition. There are probably a lot of users who have no idea about some of this phone's shortcomings and are not complaining. Why rile them up? Better to keep selling them and just replace bad ones as needed, at least from a corporate standpoint. That way, they only have to eat the ones actually returned. If they stop sales they have to eat ALL of the ones they currently have on hand. Keep in mind, the Galaxy line is probably the 2nd most popular phone behind the iPhone. I'm sure Samsung doesn't want to upset that apple cart.
[Captivate General] bames:
the original internal memo stated any phones starting 351 and ending 5394 or lower were the potentially affected models. Anything higher...which would have included those starting 352 were not included in that memo.

that being said either way you look at it my 2nd replacement arrived today and is within the affected ranger (by the memo standards and/or by what they told you).

At least its in great physical shape and doesn't have a giant M carved in the screen like the last one so i am going to keep it and see how it does. At least i have until mid july on my warranty =)
[Captivate General] Miami_Son:
I win! Sorry.:( Hope it works out for you.;)
[Captivate General] sween01:
bames:

Unless someone has tinkered with the original memo, the IMEI that was referenced does not start with 351. It starts with 352. The full number is 352982040855394.

I don't know why the memo does not appear in post #1 of this thread, which was started by danolo1979, but he is quoted in post #24, and that quote contains the following memo:

Originally Posted by danalo1979

Samsung has released an imei range for the problematic random shut down phones. If the last 4 numbers of your imei is lower than 5394 then your phone will have the shutdown problem eventually. SAMSUNG has found that all captivates manufactured before November 6th 2010 have this defect. This press release was published on Dec 20th

ID: myc_spt_iss_wid_sam_189047

Date Published: December 20, 2010

Manufacturer(s): Samsung

Model(s): i897 (Captivate)

Issue Type: Informational

Issue Summary

AT&T and Samsung are working together on a power off issue on the Samsung i897 Captivate. There is a small group of Samsung i897 Captivate devices which may experience power off when in standby mode. All devices manufactured after November 6, 2010 should not have this issue. Most customers are not expected to see an issue, however the following IMEI range could potentially have the issue and AT&T and Samsung want to ensure these customers have the best possible experience and quickly address customer care inquiries should they arise:

IMEIs manufactured before November 6, 2010: 352982040855394 or lower - 5393, 5392, etc.

If customers reports that their device is powering off when in standby mode please assist them with exchanging their device.

SKU: 65187

Critical Must Know/Must Do

Customer/Embedded Base: If a customer has the power off issue when in standby mode please exchange their device. Customers with the launch software version i897UCJF6 are more apt to have the standby power off issue. Meanwhile customers that have devices manufactured after November 6, 2010 should have software version i897UCJH7 which fixes the Power Cycling related to SW issues.

Existing Product: All devices that were manufactured before November 6, 2010 have the potential to be affected.

New Product: Devices manufactured after November 6, 2010 should not experience this issue.

Distribution Center: No action necessary.

Channel Instructions

Company Owned Retail: Continue to sell through existing inventory. If a customer has the power off issue when in standby mode please exchange their device.

Dealers: No action necessary.

National Retail: No action necessary.

Direct Fulfillment: Continue to sell through existing inventory. If a customer has the power off issue when in standby mode please exchange their device.

Customer Returns and Exchanges: Standard under 30-day returns are in effect for this issue.

Accountability/Responsibility

Distribution Centers: No action necessary.

Channels/Markets: Adhere to Standard Operating Procedures.

Returns Processing Center: Adhere to Standard Returns Processes.

Supply Chain: Please send questions or comments to SCM Product Advisory.
[Captivate General] sween01:
(Please disregard this post. It was a duplicate of the prior post until I edited it. Apparently, you can edit a post, but you can't delete one.)
[Captivate General] elfie:
The memo just mentions about 352, nothing about 351... so there are 2 possibilities:

1. IMEI range 351 was made before 352 and has defect in it.

2. IMEI ranges 351 and 352 were made at 2 different physical locations, so their affected IMEI range might be different.
[Captivate General] elfie:
By the way, my original was 351..7784 . and replacement was 351..8910, 5 days no shutdown yet. Hopefully it is fixed, otherwise I still have warranty till November end.