Related
Today I went to the AT&T store to complain about the GPS issues on the Captivate. The associate (after looking the device over), gave me a flier/form and told me to take the phone to the local AT&T warranty center. The flier seems to indicate that the warranty center folks would either fix the issue or replace the device if they agree that my phone has an issue and is not (water) damaged etc.
Anybody have any experience with this?
I don't have any experience while owning a Captivate and going to the Warranty Center...
But when I had my Samsung Impression, and the phone display (it was a touchscreen with a slideout keyboard) completely stopped working, it wouldn't register any touch at all, I took it to them, they turned it on, tested that it truly didn't work, and they gave me a new phone (might have been refurbished) on the spot. Walked out with a smile on my face and went on with my day.
Same experience with two LG Xenons with bubbles under the screen. On the spot replacement within 10 minutes after they verified that the moisture sensor was clear.
Sent from my SAMSUNG-SGH-I897 using XDA App
Refurbished phones are the replacement. Very easy to deal with.
I had the same thing with my wife's Bold - warranty center didn't really try to fix it, just did the replacement. You have to make sure to do the data wipe before the exchange, and they can't do much in terms of data transfer. Process itself is very quick and straight-forward.
For my captivate GPS I just did a mail replacement. Gives me the time to swap everything at home with no pressure.
Funny you should ask. I'm currently dealing with a warranty exchange via phone and mail. I called customer support and told them about the random shutdown issue. They transferred me to the "Android" department. The Android department has heard about this so-called random shutdown issue so they sent me a replacement (refurb) phone after asking me questions like "Has your phone ever been dropped?" "Are there any damages to the screen?" "There is a square sticker right next to the 3 golden battery connector prongs. What color is it?" (FYI. If your phone gets wet, that white square will turn to a different color! Mine is still white. Never been in water. Anyway...)
They sent me the phone yesterday and today I turned it on. There was a new problem. It randomly takes me back to the Home screen when I'm just casually browsing the web, flipping through my apps, etc. It doesn't force close the app or system that I'm on. I just boots me out of whatever I'm doing and shows me the Home screen. So, I called to tell them about this problem. It is now in a box that it originally came in and it's waiting to be shipped out. They will give me another Captivate in the mail by Friday.
jaykishora said:
Today I went to the AT&T store to complain about the GPS issues on the Captivate. The associate (after looking the device over), gave me a flier/form and told me to take the phone to the local AT&T warranty center. The flier seems to indicate that the warranty center folks would either fix the issue or replace the device if they agree that my phone has an issue and is not (water) damaged etc.
Anybody have any experience with this?
Click to expand...
Click to collapse
The Warranty Repair Center in my town doesn't stock Captivates. They'll take a look at the phone to see if it was damaged or submerged, then tell you to call the 800 number. Or, you can skip driving in to a warranty center and just call the 800 number. The people there will talk you through some basic troubleshooting, then ship you a replacement (ground is standard, you can pay for an upgrade to overnight). You have 10 days after that to return your phone.
As for your GPS problems.... if you've upgraded to JH7 and can get a solid lock out in the open under a clear sky, well... Sorry to disappoint, but your replacement phone is probably going to have just as many problems with the GPS. I do (and I'm on my 4th Captivate), so do 7 of my friends and coworkers who have Captivates, and so do about 90% or more of the people reporting on the forums.
According to AT&T and Samsung, the JH7 update 'addressed the GPS issues'. And it did make it better... Before, it would just about never lock on. Now I can usually get a lock within 10~20 seconds and it'll show me where I should be.... until I go for a drive.
The test is this: install My Tracks and go for a drive around town. Once you're done, take a look at your track.
If you've got a softtop convertable or a fiberglass roof, you're good.
If you've got the phone far forward on the dash and have a large, steeply raked windshield, you're good.
If you've got a large sunroof, you might be good.
Otherwise, you're stuck with a measured 50m~100m accuracy (it reports 15m~30m, but don't believe it) if you can even maintain lock.
Good luck!
RexEscape said:
Funny you should ask. I'm currently dealing with a warranty exchange via phone and mail. I called customer support and told them about the random shutdown issue. They transferred me to the "Android" department. The Android department has heard about this so-called random shutdown issue so they sent me a replacement (refurb) phone after asking me questions like "Has your phone ever been dropped?" "Are there any damages to the screen?" "There is a square sticker right next to the 3 golden battery connector prongs. What color is it?" (FYI. If your phone gets wet, that white square will turn to a different color! Mine is still white. Never been in water. Anyway...)
They sent me the phone yesterday and today I turned it on. There was a new problem. It randomly takes me back to the Home screen when I'm just casually browsing the web, flipping through my apps, etc. It doesn't force close the app or system that I'm on. I just boots me out of whatever I'm doing and shows me the Home screen. So, I called to tell them about this problem. It is now in a box that it originally came in and it's waiting to be shipped out. They will give me another Captivate in the mail by Friday.
Click to expand...
Click to collapse
Mine was doing this too. I disabled plugins and a problematic page would render. Might be something to try just for the heck of it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Very easy to deal with IMO. I am on my 3rd captivate.
1st one experienced random shutdowns, 2 days later received second one in mail and wouldn't get any network signal, 2 days later my 3rd and hopefully last captivate was on my doorstep.
All you have to do is send in your old unit. I was satisfied with the android people over at ATT.
Dealing with AT&T is MUCH more pleasant then dealing with Samsung for your warranty support. They're quick, they're nice, and they get you in and out in about 30 minutes.
z28james said:
Mine was doing this too. I disabled plugins and a problematic page would render. Might be something to try just for the heck of it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, I don't think it's that. It wasn't just on the Browser. It was also doing it while I was just flipping through the apps or reading an email using the stock email, or SMS, or looking at Settings. Anything I was on, it booted me out and took me to the Home screen. I returned it. I'm getting my 5th Cap today.
Thanks for all the replies. I'll post my experience if it turns out to be any special or interesting.
One other question. My phone is currently rooted. Should I spend effort unrooting it or it should be fine?
Unroot it and/or flash it back to original JF6 using ODIN One-click. If you've installed Froyo, do a Master Reset so it'll delete traces of 2.2 folders and whatnot. Backup first!
Pleasant experience
I went to the AT&T warranty center last weekend and was in and out of the store in less than 10 minutes with a new Captivate in hand. It was an extremely pleasant experience.
Just want to say that this replacement device (new and not refurbished) locks the GPS in about 10 sec inside the car and even faster under the sky and remains spot on. This leads me to believe that it may be some batches of device with buggy hardware with GPS issues.
Thanks
100% of the phones you get at the device support centers are refurbished sport. I'm a manager at one. If they told you it was new you have been whamboozled
Sent from my SAMSUNG-SGH-I897 using XDA App
RexEscape said:
Unroot it and/or flash it back to original JF6 using ODIN One-click. If you've installed Froyo, do a Master Reset so it'll delete traces of 2.2 folders and whatnot. Backup first!
Click to expand...
Click to collapse
I'm a manager at one of the at&t device support centers. Odin one click flash to original software is the only way to pass our inspections. We're not dumb. We can see if you've monkeyed with it in exactly 3 clicks
Sent from my SAMSUNG-SGH-I897 using XDA App
Walked in, gave them a Captivate that refused to charge, boot, or respond in any way, walked out with one that works.
Took maybe 30 minutes tops.
danalo1979 said:
100% of the phones you get at the device support centers are refurbished sport. I'm a manager at one. If they told you it was new you have been whamboozled
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
When I asked specifically whether the device was refurbished, I was told that it was new unit, as the refurb units have some red sticker on the device (when you take the battery out). Either way it does not matter to me as this unit works perfectly including the GPS.
jaykishora said:
When I asked specifically whether the device was refurbished, I was told that it was new unit, as the refurb units have some red sticker on the device (when you take the battery out). Either way it does not matter to me as this unit works perfectly including the GPS.
Click to expand...
Click to collapse
Looks like you were lied to.
Unless if you were still under your 30 days, which would put you under the buyer's remorse program [completely apart from Warranty], then you'd be receiving a new model.
+ most Warranty Captivates are affected by the random shutdown issue, as they aren't scrapped if they're under the affected IMEI range.
You're using a refurbished Captivate, all in all.
My first phone was rooted and then the random crashes started. It got so bad I couldnt turn the phone on unless I did a battery pull then with the charger plugged in and finger banging and milking a cow at the same time.
I finally got it into download mode and went back to stock. I went to the tech center explained what happened and she replaced it right on the spot and gave me a NEW phone, battery and charger. BUT she gave me my old battery cover. :-(
Sent from my Captivate.
Ok, first off I just want to say I have searched around the forums for a similar problem in hopes for a solution and to avoid reposting a question.
For information about my phone, see below the problem description.
Here is the problem:
This just started today, the phone will not play any ringtone or notification sound. I can confirm the speaker itself still works by playing music or choosing ringtones. Alarms do still work, just not call tones or notification tones(even using default ones).
Now that is only part of the problem, along with that, is the fact that when a text message is received, I can view it and dismiss it (Using Handcent as Default). But 30 seconds to a minute after getting the message, or usually while replying to it, the screen will go black and the capacitive buttons stay lit up. No button presses are registered and the only way to gain access into the phone is by removing the battery and putting it back in.
I am also not getting every message sent to me, some will come through while others don't.
Another unrelated issue:
If I wait an extended time between listening to music, usually 20+ hours, for the first minute or so I hear a little bit of static and then it clears up and doesn't happen until the next day.
Info about the phone:
I bought the phone new on eBay at the end of September, the 28th.
The only modification done to it is doing the latest VooDoo lagfix from the link below(I did this within two weeks of having the phone, and it worked fine):
http://forum.xda-developers.com/showthread.php?t=784170
Aside from that, the phone is completely stock running the latest OTA update.
I am using a GoPhone SIM card that has never given me any issues before.
Kernel Version: 2.6.29 voodoo_lagfix_3.0_v1.10
Firmware: 2.1-update1
Build: ECLAIR.UCJH7
Baseband: I897UCJH7
My Background
This is only my second Android phone, coming from the myTouch 3g. I have had the same SIM card for years. Now I have the Captivate, and this is the first time it has given me this kind of problem. I have experience flashing ROM's and all that, I just wanted to wait for an official update for the Captivate to see if GPS gets improved.
I hope I have provided enough information to diagnose the problem, let me know if there is anything else you need to know and thanks for your time.
Side note if this can't be resolved with you guys:
Would I be able to call up Samsung and get a replacement from them?
codyrt said:
[*]I bought the phone new on eBay at the end of September, the 28th.
Side note if this can't be resolved with you guys:
Would I be able to call up Samsung and get a replacement from them?
Click to expand...
Click to collapse
Probably why it was sold on Ebay in the first place. Just a shot in the dark, maybe the speaker connection is loose? There are a few threads about taking the phone apart if you are so inclined.
Can't see how it would be a warranty, you bought it through a third party. Could always try.
Swyping...please read slowly!
cappysw10 said:
Just a shot in the dark, maybe the speaker connection is loose?
Can't see how it would be a warranty, you bought it through a third party. Could always try.
Click to expand...
Click to collapse
I did think something like that at first, but every other sound works fine and when it is supposed to(startup sounds, games, etc.). And I would think if it's a loose connection that shaking the phone or moving it around would make sound cut out, but it doesn't.
I figured the manufacturer warranty wouldn't apply, but I have gotten warranty replacements in the past on other electronics from eBay. So maybe a little fibbing will be in order to receive another unit.
I'm thinking it is something software, I have no clue what, I haven't made any major software additions or changes since yesterday. But if all else fails I will try changing to a different ROM and if that fails, get a replacement from Samsung.
I would try flashing again.....and running that kernel....kinda makes your phone far from stock...
For some reason the issue has stopped. I only did a few things, I powered off the phone, turned it on with the 3-button combo, and then restarted the phone from that menu. After the restart, I reassigned the notification tones and ringtones to what they were(my personal choices, not system sounds) and it seems to work.
I will probably wait a few days to see if it occurs again, and if it does, I will move on to a ROM from the Dev section because I am convinced its just some apps conflicting with each other.
newter55 said:
and running that kernel....kinda makes your phone far from stock...
Click to expand...
Click to collapse
I figured that was a minor modification, so i just counted it as stock, but I see what you're saying.
Hello everyone.I'm having a problem with no sound coming from the ext. speaker.I was running Firefly 2.0.5 and Suckerpunch build #28 kernel.Out of the blue today,sound just stopped working,no ringtone,no media sound.There is sound coming from the earpiece,just not speaker.I've odin back to stock JF6 and master cleared but still no sound.I'm pretty sure now that it's a hardware issue,but just wanted a couple of opinions before I send it back for warranty.Any help or advice is greatly appreciated.Thanks in advance.
I've been running that same combo. No sound issues here.
I'm on board with the hardware issue.
nickm50 said:
I've been running that same combo. No sound issues here.
I'm on board with the hardware issue.
Click to expand...
Click to collapse
That's what I'm afraid of,but part of me has already known it is hardware,since JF6 yields no sound.Thanks for replying!Guess I'll send it in....
physically push the speaker down some..worked for me and others
mathur.3 said:
physically push the speaker down some..worked for me and others
Click to expand...
Click to collapse
From what i've read, this is the "official" fix.
Take the back off, battery out, then "thump" the area under the battery. Believe it or not, that's really it.
I had the speaker not running out of the blue. When I was putting back my phone in the original config for a return to ATT, it started to work again for 2 hours, then stopped, then restarted and now it has been working for 2 days.
I am glad to see it's not an isolated problem and that there is an "official" fix.
Dropped
By any chance have you dropped your phone? Salesperson at BB dropped my new Cappy while installing a Zagg screen protector. On day 2 I had to go back to BB with no sound. The salesperson pushed down on the speaker and then it worked! I fussed enough at him to get another new Cappy! I haven't dropped this one yet!
It worked, but as soon as i play some sound it went silent again.
Yeah, my phone had a few history violent drop on the ground. this sucks.
I bought 2 Herod with CDMA about 18months ago.
Each day I have differenet problem but I don't want to talk about that.
2 days ago both phones sratrted to break voice while calling and even while connecting.
We wern't be able to talk because people heard us good but we couldn't understand even 10% of words.
I called Sprint(my phone carrier) customer service and I spent 3 hrs on telling what's my problem.
As usual it ended up on that they see no problems with my service and told me to check phone in the store.
I already did that procedure more than 5 times, spending more than 200hrs on talking with CS, driving to store and replacing both phones 4 times. Nothing ever changed so we just think that we try to live with those problems until contract ends.
But this is too much.
We both have rooted phones and installed CyjanogenMod7. It was working better but all problems stayed.
So.... now...
Lady on the phone updated our phones/profiles and since that moment both phones died.. literally died. That exactly happened half day later when I wwas at work. Both phones always act the same(weird right?)
So now they act in 4 ways(randomly)
1)phones are dead, I can't turn it on. Removing battery doesn't help
2)phones can be turned on. I see HTC logo and nothing else
3)phones can be turned on but they constantly restart themselves after showing HTC logo for 5-10sec
4)finally phones can be turned on but I have no connectivity, no internet, no bars and big sign "searching for signal"
BTW I have signal in my house, it's not like I moved to North Pole or something.
Usually my phone is dead and the best part is that even I finally turn it on...somehow then it's going to turn off after few minutes and I will never see signal(super weird).
It all started to happen after updating your profiles and phones but you can call me crazy but I got a feeling that they "broke" our phones wirelessly because I asked really bad for corporate number and for waiving my cancellation fees because I just have enough. That is the most... the worst company and phone ever.
Please help me. Maybe there is something I can do.
probably not much help here but try to update profile and prl again from stock sense 2.1 rom
no service/connectivity/signal sounds like a bad radio flash, try to update your radio to the latest sprint offering, if nothing else works a ##786# reset saved me one day from a bad pri, good luck and i hope you figure out whats wrong
My phone doesn't want to turn on from 3hrs(didn't happen yet) and I can't charge it. That is the end...
I'm goingf tomorrow to pay all fees and get new phones and plans in different carrier.
I couldn't run it yesterday anymore. But today it finally turned on and I'm charging it(17%). What is the quickest mnethod to install stock rom? Can you give me some links?
sorry for the late posting, but here you go:
http://support.sprint.com/support/a...e-gb746811-20091009-155624?&INTNAV=SU:DP:HDIA
read through that and you should be able to get back to complete stock
hope that helps some, and good luck
Hey guys,
Does anybody who ever or being suffered from the call issue like hearing nothing from the receiver during phone calls??Sometimes it work,but sometimes it doesn't!!And the speaker works in most of the cases,whereas sometimes it also breaks down liked the receiver.Moreover,I can hear some cracks from the receiver in some cases.
I am totally freaked out because I am sure that the receiver is good (no problems with skype and wechat,and I also have checked it by using "*#0*#" when the situation happens) and it seems impossible to be solved after wiping and flashing different firmware(both by cwm and odin),and so do the modems.
Any solutions or suggestions will be totally appreciated!!!:crying:
Edit: I've tried to flash the Perseus and disable the dac direct,it seems that the cases happen less frequent.
Update:
I found sth strange about the call issue by chance: when I lock the screen maybe for more than 5 mins,then wake it up and make a phone call soon,the receiver can't work every times.However, when I put it into use(light the screen) for more than 3 or 4 mins,and then the receiver works again during calls.
What I want to say is: maybe there are sth wrong with the cpu setting or the power management?
I actually got the static phone call issue today (first time) after installing ripper rom yesterday but im sure it was just a once off issue because I could not reproduce the same result
Change roms ect but if the issue persists then your only option is to jump on triangleaway, stock firmware and dial away to Samsung or your telco
Sent from my GT-I9305 using xda premium
takooo said:
Hey guys,
Does anybody who ever or being suffered from the call issue like hearing nothing from the receiver during phone calls??Sometimes it work,but sometimes it doesn't!!And the speaker works in most of the cases,whereas sometimes it also breaks down liked the receiver.Moreover,I can hear some cracks from the receiver in some cases.
I am totally freaked out because I am sure that the receiver is good (no problems with skype and wechat,and I also have checked it by using "*#0*#" when the situation happens) and it seems impossible to be solved after wiping and flashing different framekworks(both by cwm and odin),and so do the modems.
Any solutions or suggestions will be totally appreciated!!!:crying:
Edit: I've tried to flash the Perseus and disable the dac direct,it seems that the cases happen less frequent.
Click to expand...
Click to collapse
It's a hardware issue. I had the same thing with my i9300; You have to take it to a repair center for motherboard replacement. It's the audio chip that goes bad (on the i9300 the component number is U604). Happened to me twice, with both my new and replacement motherboard, but it happened to go away for me the 2nd time.
Product F(RED) said:
It's a hardware issue. I had the same thing with my i9300; You have to take it to a repair center for motherboard replacement. It's the audio chip that goes bad (on the i9300 the component number is U604). Happened to me twice, with both my new and replacement motherboard, but it happened to go away for me the 2nd time.
Click to expand...
Click to collapse
Thanks!! I've saw your thread and now I have nothing to do with it except considering repair.If the issue happens again,i will probably send it back to the company which I bought this phone.
BTW,are you sure both your phones are now preforming good during the calls?You have said that the issue happened again a month later after it got the first repaired? If you have some news with your phones,please notice me~~~
Magik_Breezy said:
I actually got the static phone call issue today (first time) after installing ripper rom yesterday but im sure it was just a once off issue because I could not reproduce the same result
Change roms ect but if the issue persists then your only option is to jump on triangleaway, stock firmware and dial away to Samsung or your telco
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yep!! Last time I had flashed the ripper rom and then I found this issue.First I thought it was the problems that come from the rom,but after several tries then I thought it probably due to the hardware issue that I cant solve....
Anyway,thanks for your suggestions!!
takooo said:
Thanks!! I've saw your thread and now I have nothing to do with it except considering repair.If the issue happens again,i will probably send it back to the company which I bought this phone.
BTW,are you sure both your phones are now preforming good during the calls?You have said that the issue happened again a month later after it got the first repaired? If you have some news with your phones,please notice me~~~
Click to expand...
Click to collapse
I've had the phone for about 6 months total. The first time the issue happened, I had owned the phone for 3 months. The phone came from a company in Germany, and I live in the US (purchased through Amazon). The i9300 is not sold or repaired in the US (because the US version has different components), so I had to ship it to the seller, to ship to a repair center on my behalf. The phone itself carries a 2 year warranty, which is good because in the US phones only have a 1 year warranty. However, it cost me $80 to ship the device to Germany, and about a month total time before I got it back.
Anyways, I got a paper back in German that detailed the issue and said they had to replace a component, which turned out to be the entire board. They also copied over the original IMEI number to the new board. The second time this issue started happening was literally on New Year's Day (on 12:00 AM EXACTLY). I tried to call a car service place for my girlfriend and her family, and my phone had no audio going in or out for calls. My phone was working perfectly before that and I hadn't flashed anything new for over a month (I was on Omega ROM 35 with Siyah kernel 1.8.6). Immediately I knew the issue had come back again. For whatever reason, the issue went away maybe 4 days later and hasn't come back. I flashed the latest modem (for the i9300 it's XXELLA), but I'm still on Omega ROM v36. I don't think me flashing anything fixed anything; more likely that it went away on its own since it's 100% a hardware issue.
To clarify, sometimes an incorrect modem for your region CAN cause there to be issues with calls, but if it happens out of the blue, and flashing anything doesn't help, it's a hardware issue. Take it to a Samsung repair center for sure. The i9300 and i9305 use the same parts except for the modem and a few other things. Other than that they're the same exact device.
Product F(RED) said:
I've had the phone for about 6 months total. The first time the issue happened, I had owned the phone for 3 months. The phone came from a company in Germany, and I live in the US (purchased through Amazon). The i9300 is not sold or repaired in the US (because the US version has different components), so I had to ship it to the seller, to ship to a repair center on my behalf. The phone itself carries a 2 year warranty, which is good because in the US phones only have a 1 year warranty. However, it cost me $80 to ship the device to Germany, and about a month total time before I got it back.
Anyways, I got a paper back in German that detailed the issue and said they had to replace a component, which turned out to be the entire board. They also copied over the original IMEI number to the new board. The second time this issue started happening was literally on New Year's Day (on 12:00 AM EXACTLY). I tried to call a car service place for my girlfriend and her family, and my phone had no audio going in or out for calls. My phone was working perfectly before that and I hadn't flashed anything new for over a month (I was on Omega ROM 35 with Siyah kernel 1.8.6). Immediately I knew the issue had come back again. For whatever reason, the issue went away maybe 4 days later and hasn't come back. I flashed the latest modem (for the i9300 it's XXELLA), but I'm still on Omega ROM v36. I don't think me flashing anything fixed anything; more likely that it went away on its own since it's 100% a hardware issue.
To clarify, sometimes an incorrect modem for your region CAN cause there to be issues with calls, but if it happens out of the blue, and flashing anything doesn't help, it's a hardware issue. Take it to a Samsung repair center for sure. The i9300 and i9305 use the same parts except for the modem and a few other things. Other than that they're the same exact device.
Click to expand...
Click to collapse
Ok,thanks a lot for telling me these!!! I've sent a email to the customer service and hope to get respond soon.Anything news i will update it.