Automatically Powering Off Solution?

Automatically Powering Off Solution? - Captivate General

I know the issue of people's Captivates turning off by themselves has been discussed a lot and if there is a solution that is already provided, I apologize for cluttering up the forum a little more. If not, I have something that works for me and was wondering if it might be helpful for troubleshooting what the issue is/how to fix it.
For myself, it seems to be an issue when the battery is near full more than any other time. If I just unplug the phone in the morning and come back to it later it will be off. However, I often go running in the mornings. When I do, I like to listen to music and I use Grooveshark to do it. Just opening Grooveshark does not seem to fix the issue, but if music is playing (even if there is no volume) my phone does not turn itself off. I haven't played around to see if the same is true for just playing music through the regular music player, but I was wondering if perhaps accessing audio playback somehow keeps the phone alive.
Again, if there is already a known solution I'm sorry for cluttering things. Maybe I just had to search around some more...

pezx44 said:
I know the issue of people's Captivates turning off by themselves has been discussed a lot and if there is a solution that is already provided, I apologize for cluttering up the forum a little more. If not, I have something that works for me and was wondering if it might be helpful for troubleshooting what the issue is/how to fix it.
For myself, it seems to be an issue when the battery is near full more than any other time. If I just unplug the phone in the morning and come back to it later it will be off. However, I often go running in the mornings. When I do, I like to listen to music and I use Grooveshark to do it. Just opening Grooveshark does not seem to fix the issue, but if music is playing (even if there is no volume) my phone does not turn itself off. I haven't played around to see if the same is true for just playing music through the regular music player, but I was wondering if perhaps accessing audio playback somehow keeps the phone alive.
Again, if there is already a known solution I'm sorry for cluttering things. Maybe I just had to search around some more...
Click to expand...
Click to collapse
My guess is you guys have tried to overclock and your phone really didn't like it and caused some minor damage. I have heard reports from stock 2.1, 2.2 and Cognition, most of them I have talked to have tried overclocking at some point. If you haven't, maybe just faulty hardware out of the box, if you can flash stock and it still happens, take it back and exchange it.
Personally I won't be overclocking again, 200mhz is not working breaking a $500 phone. I find the lagfix isn't even needed on 2.2 stock.

I only had overclocking on my phone once in a sre build and tested it once and found it worthless to me so i disabled it.
Anyways i have never had an issue with shut downs prior to flashing ji6. Now when i leave my phone plugged in over night, on, i wake up in the morning to find it off. This has happened every day so i cant use my phone for an alarm at the moment. Otger than that ive had a few random shut downs during the day. I do want to know what the problem/solution is for the phone shutting off during the night though.
When i flashed over to ji6 i formatted sd odined jf6 then odined ji6. I did try to do tge master clear only to have it start then say FAIL! In a red box. Someone suggested i reinstall my drivers. I do plan on trying that but am getting so sick of flashing and redoing stuff i havent got aroubd to it.
Would a master clear do anything or make a difference you think since i formatted the sd?
Sent from my SAMSUNG-SGH-I897 using XDA App

designgears said:
Personally I won't be overclocking again, 200mhz is not working breaking a $500 phone. I find the lagfix isn't even needed on 2.2 stock.
Click to expand...
Click to collapse
Agree - the extra battery drain and heat buildup in the chip is not worth it... this device works pretty good with stock and/or new FS tweaks applied.
I do hope the OP gets his device recovered with Odin etc.... hopefully just a glitch that can be remedied back to stock....

I've Odin'd it back to stock but currently am running Cognition 2.2. This has been an issue from the getgo, however (maybe I should mention that I SIM unlocked it if that makes a difference). I couldn't return it because I live out of the country and didn't even receive the thing for about 40 days (gotta love Costa Rican customs). I agree that OC seems pretty pointless on this phone and I have avoided OC roms. I only thought it was interesting that running programs doesn't seem to prevent it, but for some reason playing music does seem to prevent the shutdown perhaps meaning that accessing a certain dll or something fixes the issue (I really have no idea why it works). I just thought that info might be helpful to people who understand the OS better than I if it is a consistent problem for people and if no solutions other than "return it" have been found.
Edit: Oh and DG, great work. You'd be one of those smarter than I guys I referenced...

i've never overclocked my phone and i've mostly run it without a lagfix and no matter what ROM i've used (i've been using cognition beta 1 since it came out) i've always had random shut-downs. For a while there on the stock rom it seemed to only happen when my wifi was on but now it doesn't matter. I don't have any special automation software running (task managers, tasker, ..etc). It's the single most maddening thing about this phone.

Same here... i have had my phone since launch... i had random shut downs since launch. I have had less problems now then before and i have flashed every rom that has come out including overclocking.
Sent from my SAMSUNG-SGH-I897 using XDA App

My wife's phone was never overclocked and it developed the random shut down problem about two weeks after she got it. After trying numerous things to fix the problem, some resulting in it working fine again for a few days and then starting random shut downs again, I came to the conclusion that it was definitely a defective hardware problem and had her return and exchange it. The new one is now set up exactly the same as her old one (rooted stock jf6 with the bloatware removed, side loading enabled, and market fixed) and has been running fine, with no shut downs for over two weeks.
I have been in the electronic repair business for over 25 years, and my conclusion is, the only fix is to return it and get it repaired or replaced. Nothing you can do is going to fix your defective hardware.

I had my phone for a month and it was flawless, updated to 2.2 beta and started getting random shutdowns. I replaced the phone and the new one doesn't shutdown at all on 2.2. The one I returned would shutdown at least 5-6 times per day. Again only after installing 2.2, on 2.1 it seems ok. Which could be a software issue, or just more strain on the hardware making the problem happen
Personally I think it's just bad hardware. Replace the phone.

I guess I'll have to see if there's any way of getting the hardware replaced but I don't think I'm going to be able to manage.
I just want to repeat, however, that I have tested this many many times and with numerous iterations of DG's roms as well as stock. I can guarantee a shut down soon after unplugging the phone in the morning, but I have never gotten it when I start playing music (specifically through Grooveshark - I have not tested it with the regular music player). I just think that even if it's a hardware problem, there appears to be a relationship which suggests that a software solution could prevent it (at least given my experience). I just thought it might be helpful information to people who might understand a possible relationship between the two and to see if anybody else can confirm or refute this behavior. If there is any way to trick the phone into thinking it is playing the music without actually playing it, the problem may go away for people who are experiencing it.
If anybody else can refute my observations or back them up, I would be interested to hear. Perhaps if enough people can confirm it, it may be worthwhile to investigate further. If people can refute it, I guess I'll just count myself "lucky" to have only a mildly faulty phone. Either way I'm happy with my phone. I just thought I might be able to help others out.

I actually convinced four coworkers to pick up Captivates here (our company policy is with at&t) and my boss' phone (completely stock) would randomly shut-down four or five times a day. I've been around the community since the G1 dev launch and my phone is definitely not stock but has never randomly shutdown.
I finally convinced him to return it and his new one came in today. With this many reports, it is not a user-induced problem.

+1 to everything im reading here. i tried a few software and hardware 'fixes' so to say and nothing fixed the issue for long term. sent in for a new captivate #3 yesterday. Im sorry its just got to be a hardware problem, its just to far widespread from what im seeing.
I did want to point out one fear that is starting to cross my mind. i got my 1st one off craigslist which is hilarious because im still covered by warranty. HOWEVER. after the first exchange its then 90 days on a refurb *which begs me to wonder if samsung will still honor the 1 year warranty claim*..anyways.. im really really really hoping that i dont get one that seems to last a while and has this issue start up again....because that will be the last captivate for me...obviously lol

Believe it or not, this has been working for me for a couple of days now
http://androidforums.com/captivate-...hone-shutting-off-randomly-5.html#post1572891

I called ATT and was told to call Samsung because I don't have an account. They did tell me, however, that they didn't know anything about a bad production run or anything like that or about many exchanges. Of course I take all of that with a grain of salt...
Out of curiosity, to the people that have had the shutdown issue: Did you SIM Unlock your phone? I have and I use a foreign SIM (just trying to see what is in common).
I understand that it seems to be a hardware-based issue, but there really does seem to be a correlation to software as well. If I'm told by Samsung that there was a bad production run, I'll go with it. But until then, I'm the meticulous sort and will continue testing.
I don't want to beat a dead horse though and I don't want to be one of those guys claiming some fanciful fix to something there is no fix for. I'm still doing some testing on my end. So far the music "fix" has worked for me (although I do not see it as a long term solution) and I just wanted to float it because it seems to work consistently (unfortunately you can't prove a negative). I understand, however, that others have claimed fixes that just plain don't work and so if I hear of anybody trying this and it not working for them I'll move along to focus on other possible correlations. Thanks for all the feedback so far!

Why are people blaming hardware if it is exclusively a Froyo problem?
I've never OC'ed. Learned my lesson on the Evo 4g.
The power-off problem ONLY happens on Froyo builds
Issue happens with the ODIN-packaged 2.2 and all Cognition 2.2 releases
Inexplicably, I do not have the problem with my current Froyo build based on beta 4. Previous installs of Beta4 did have the problem, just not this one.
Odd behavior on a leaked build does not mean bad hardware. Once again, I NEVER have this problem on Eclair.
There is some combination of software and/or settings that causes this.

ZoinksS2k said:
Why are people blaming hardware if it is exclusively a Froyo problem?
I've never OC'ed. Learned my lesson on the Evo 4g.
The power-off problem ONLY happens on Froyo builds
Issue happens with the ODIN-packaged 2.2 and all Cognition 2.2 releases
Inexplicably, I do not have the problem with my current Froyo build based on beta 4. Previous installs of Beta4 did have the problem, just not this one.
Odd behavior on a leaked build does not mean bad hardware. Once again, I NEVER have this problem on Eclair.
There is some combination of software and/or settings that causes this.
Click to expand...
Click to collapse
Blaming the 2.2 builds as the sole culprit is false. I have coworker who has two stock captivates. His had never had an issue, his wife is up to phone #2 and has had power issues on both.
Sent from my SAMSUNG-SGH-I897 using XDA App

It is definitely not exclusively Froyo. It has been happening to people (myself included) for a while.
I just got off the phone with Samsung (general customer support then level 2 technical support). I suggest that anybody else have the problem also call them to at least document the issue (888-987-4357 options 1-6-2-4). They said I can send it in for repairs (yeah right - like I can be away from my phone for that long!) but more importantly that they have not heard of this being a widespread problem but that probably just means that people aren't reporting it. I urge others to call in to at least let them have an idea of how widespread (or not) it is.

pezx44 said:
It is definitely not exclusively Froyo. It has been happening to people (myself included) for a while.
I just got off the phone with Samsung (general customer support then level 2 technical support). I suggest that anybody else have the problem also call them to at least document the issue (888-987-4357 options 1-6-2-4). They said I can send it in for repairs (yeah right - like I can be away from my phone for that long!) but more importantly that they have not heard of this being a widespread problem but that probably just means that people aren't reporting it. I urge others to call in to at least let them have an idea of how widespread (or not) it is.
Click to expand...
Click to collapse
Hmm im pretty sure i just got them yesterday HOWEVER they also sent me to their android support team *wha? really?* pretty much the same level of service but they made sure i was on the newest ota and had me try it for a day and said they would call back after 24 hours to check if the issue persisted.
Why did they tell you to send it in for repairs thou? this is going to be my 3rd and each time they send out the new one FIRST and i rma the bad one back in the box. only reason i havent been so when i have to go through this process

bamonkey said:
I did want to point out one fear that is starting to cross my mind. i got my 1st one off craigslist which is hilarious because im still covered by warranty. HOWEVER. after the first exchange its then 90 days on a refurb *which begs me to wonder if samsung will still honor the 1 year warranty claim*..anyways.. im really really really hoping that i dont get one that seems to last a while and has this issue start up again....because that will be the last captivate for me...obviously lol
Click to expand...
Click to collapse
If you bought a new phone from AT&T, the warranty is 1 year. During this one year, you can have the warranty replacement (refurbs) as many time as you want and your warranty stays as the original (counted from the day you purchased your phone).
If you bought a refurb phone from AT&T, the warranty is 90 days.

bamonkey said:
Hmm im pretty sure i just got them yesterday HOWEVER they also sent me to their android support team *wha? really?* pretty much the same level of service but they made sure i was on the newest ota and had me try it for a day and said they would call back after 24 hours to check if the issue persisted.
Why did they tell you to send it in for repairs thou? this is going to be my 3rd and each time they send out the new one FIRST and i rma the bad one back in the box. only reason i havent been so when i have to go through this process
Click to expand...
Click to collapse
If I lived in the states I probably would have pushed for that myself. Unfortunately getting things shipped to/from me where I live costs money plus customs delays so I'm sort of resigned to the fact that I'm stuck with this handset for now. I was hoping I could just bust into an ATT store and get it exchanged but it doesn't look like that's an option. Calling Samsung was more to just document it with them. I'm glad you have had better luck.
3rd you say though? Has it been the same issue with each?

Related

Fuze Times Out on Data Connection

Half the time when I try to go to a website the Fuze just times out. Loads forever and times out.
When it doesn't time out, it's slow as molasses.
I can throw my SIM in either of my other two 3G phones, sitting in the exact same spot, and everything flows just fine.
Anyone else having this issue?
I'm about ready to take this back, after months of waiting for its release, because the data connection is so unreliable.

have you tried tweaking it and maybe flash to another rom?
or maybe you just have a lemon. Get it exchanged and see if problem persists.

baboola said:
have you tried tweaking it and maybe flash to another rom?
or maybe you just have a lemon. Get it exchanged and see if problem persists.
Click to expand...
Click to collapse
Have already returned it for a different one. Exact same issue. Actually I've posted a lot of details about this, if you look at my other posts.
Many others are having this same issue. Many others in the threads on here, like the HSDPA / 3G Fuze threads. Here's a guy on ATT forums with the exact same symptoms as me: http://forums.wireless.att.com/cng/board/message?board.id=cingular&thread.id=108522
I do not want to flash to a different ROM because I saw someone in another thread post that they tried flashing back to the stock ATT ROM and it didn't work. Haven't seen anyone post saying that it DOES work for this specific phone to the ATT ROM.
If it was just "kinda slow" I would mess with tweaks and other ROMs, but the fact that it's literally unusable makes me want to just give up and possibly re-buy the phone if and when a REAL fix for it comes along.
The frustrating thing is it seems like about half people are getting awesome speeds on this phone, and the other half are getting abysmal, unusable speeds. I've seen a lot of posts on here of people saying they're just returning the Fuze as it's useless. I'm so disappointed, I really wanted this phone bad.

I'm sorry to hear that. I'm actually on my second Fuze right now (returned the first one for some stupid reason). Both phones had around the same speed. It's not stellar, but at least it's not doing terribly worse than my friend's iphone 3g, which I use as a comparison cuz we all know they're the connection hoggers.
Have you tried calling AT&T tech support? They've been extremely helpful with some of my questions.
Lastly, why not just flash it? May people are having a bit of a problem getting stock ROM to work after flashing it back, but if you're going to exchange it, who said the stock ROM has to work flawlessly? Besides, someone will eventually find a way to fully re-flash stock ROM soon, not that I'd ever understand why anyone would want to do that aside for warranty purposes.
I would bring your phone to AT&T store, talk to the manager (chances are someone working there also has a Fuze). Tell them your problem and ask them to do a comparison. Cuz right now I can only think of two possibilities:
1) you got 2 lemons in a row
2) Stock ROM really sucks
Good luck

Thanks man. I might just try a flash and see. I have not called tech support yet even though I've been thinking about doing that for days, because it's such a hair pulling experience, i just hate going through the phone systems and then getting people who don't have a clue what your'e talking about.
I did email the manager of the store, mainly about a different issue I had with the process and the associate (who lied to my face repeatedly, but i wont go into details) and mentioned the problems i'm having with my phone and the fact that the replacement is the same way.
I also live in OC (southern cal) and have heard others are having issues w 3G in general here. However the fact remains that my other two 3G phones work perfectly for me.

Returning Captivate...

Need to return this. I've been waiting on two fixes, and they haven't come...
1. Random Powering off (i use no setcpu, widgets, etc, i'm rooted, did a factory reset, etc).
2. GPS Fix
2a. Waiting on 2.2 Froyo could be forever on AT&T.
I'll return to my crappy iphone 3gs, until the problems on the 1st batch of phones is fixed.
main thing is the random powering off, gps, i've started to live with, but is really annoying once you become lost while driving and REALLY need directions fast w/o fumbling around on your phone.
I do love the phone.... just wish it was really reliable.

Hopefully youll be back soon.
if its just turning off randomly i'd be pretty annoyed with that as well.

I'm sorry if I'm being naive but, if it were me, I'd try bracing up the battery with a thickness or two of card stock paper to see if the problem was just a loose battery.
That would be easy and free to try and it just might solve the problem.

pmpntl said:
Need to return this. I've been waiting on two fixes, and they haven't come...
1. Random Powering off (i use no setcpu, widgets, etc, i'm rooted, did a factory reset, etc).
2. GPS Fix
2a. Waiting on 2.2 Froyo could be forever on AT&T.
I'll return to my crappy iphone 3gs, until the problems on the 1st batch of phones is fixed.
main thing is the random powering off, gps, i've started to live with, but is really annoying once you become lost while driving and REALLY need directions fast w/o fumbling around on your phone.
I do love the phone.... just wish it was really reliable.
Click to expand...
Click to collapse
I've replaced my original captivate due to random shutdowns. Since then there was no single power off problem for me.
Sent from my SAMSUNG-SGH-I897 using XDA App

The random powering off issues sound like a hardware defect you should definitely return that phone.

Sorry to go a litte off topic but how do I do a return through AT&T? I still have all the original equipment, box, return label, and everything. I'm tired of this random shut down + GPS issue as well.

michintom said:
Sorry to go a litte off topic but how do I do a return through AT&T? I still have all the original equipment, box, return label, and everything. I'm tired of this random shut down + GPS issue as well.
Click to expand...
Click to collapse
Bring everything to the store.

michintom said:
Sorry to go a litte off topic but how do I do a return through AT&T? I still have all the original equipment, box, return label, and everything. I'm tired of this random shut down + GPS issue as well.
Click to expand...
Click to collapse
I'm sorry your having probs, but I still believe this is the best phone on the market and I could never return it other than to get another one. Chances of you getting another one with the shut off issues are slim.
The GPS fix and Froyo are not far off and in my situation I can wait. I understand others rely on their GPS more than me. I just couldn't give up all this Galaxy S has to offer.

he's a troll dont answer him. What in the world is the purpose of creating threads saying, im bringing it back?

droidal said:
I'm sorry your having probs, but I still believe this is the best phone on the market and I could never return it other than to get another one. Chances of you getting another one with the shut off issues are slim.
The GPS fix and Froyo are not far off and in my situation I can wait. I understand others rely on their GPS more than me. I just couldn't give up all this Galaxy S has to offer.
Click to expand...
Click to collapse
I'm really bad with directions and the map application is great if the gps ever worked correctly. I called about 10 at&t stores and couldn't find any store that had the iphone 4 in stock. I still have till next week to return the phone. I guess I still have some time to re-think everything.

I do know that mine will freak out once in a great while and shutdown or require a battery pull but not enough for me to take it back and exchange it for an iPhone! If you really want the iPhone that bad why didn't you buy it instead? I bought the Captivate because I wanted a high end android phone and I did not want an iPhone because I am not a huge apple fan. Like if yours is shutting off daily then I would suggest return the phone and exchange it for another Captivate, my gps works fine with out any issues.
HTH,
Charlie

On my second captivate and I have experienced both of them shutting down on me. It's still not a reason for me to return this phone and that wasn't the reason I happen to be on my second one. Problem only occurred after the phone was rooted and some non market apps were installed.

If it weren't for the fact that I'd be returning to a first Gen iPhone or a Nokia E63, I'd return mine until the community developed more.
I like the hardware but I'd really like vanilla android. Even stock eclair. The GPS issues are able to be overlooked. I did it with my Fuze for the longest.
Sent from my Samsung Captivate.

BigJayDogg3 said:
If it weren't for the fact that I'd be returning to a first Gen iPhone or a Nokia E63, I'd return mine until the community developed more.
I like the hardware but I'd really like vanilla android. Even stock eclair. The GPS issues are able to be overlooked. I did it with my Fuze for the longest.
Sent from my Samsung Captivate.
Click to expand...
Click to collapse
god that fuze was just balls.
ne way, mr. troll, phone should never be locking up and requiring a battery pull. go get a new one.

EXCHANGE IT!
as of august 1st, firmware 2.1-update1 has been released. it fixed ALL of those problems! (I had the random shutoff, gps probs, and my fbook barely synced)
definitely worth the exchange and its FREE!

what
new firmware released? will i get it if i check for updates?
have i been under a fkin rock or something?

systoxity said:
what
new firmware released? will i get it if i check for updates?
have i been under a fkin rock or something?
Click to expand...
Click to collapse
apparently i've been misinformed, check my other thread and see if yours matches up

droidal said:
I'm sorry your having probs, but I still believe this is the best phone on the market and I could never return it other than to get another one. Chances of you getting another one with the shut off issues are slim.
Click to expand...
Click to collapse
I swapped mine for a replacement 3 days ago because of the random powering off issue, and this morning my new one was off when it should have been sounding an alarm to wake me up for work. I actually had to pull the battery to get it to work again. Then two hours later, while I was using it, it shut off again. It's an instant-off. The screen just suddenly goes black and it's all dead until it gets manually powered up again.
I've got three days left on my 30-day return period, so I'm anxious to call the warranty folks tonight.

weird. I have never had mine lock up.....ever.
its really hard to believe but its true. but then again I never do these so called "tweaks", I find that they tend to do more harm than good too often

My captivate had shut off randomly a few times, but every since I installed juice defender, and advanced task killer, it hasn't shut off at all.... as for GPS, that should be fixed with 2.2, but I don't use it that often, so not a huge deal for me, I say exchange, I'm sick of apple, I'm glad AT&T picked up a killer android phone!!
Sent From My Captivate

If you have captivate problems or don't like it because it is slow!! Gps fix!

EXCHANGE IT!
sorry! I'm just really excited, I wasn't getting any GPS signal so I took it back to the corporate store, saved a quick ti backup to my sd, swapped the phone and BAM! I now get perfect GPS locks within SECONDS of activating maps!
also! I had some weird Facebook errors, only few would sync, wouldn't sync all the time etc. etc. NO PROBLEMS ANYMORE all my contacts sync and match up perfectly.
seriously the phone is now like it should be.
I asked the corporate rep (same guy I've been going to for years) he told me that the first batch of captivates went out with corrupt firmwares, but they weren't bad enough that they would have noticed anything wrong (or they did and chose to ignore it...) anyways, round two of the phone is fixed up and great!
My firmware: 2.1-update1
my baseband: I897UCF6
my kernal 2.6.29
that is the LATEST firm/base/kernal and If you can't get your phone to OTA update to it, I HIGHLY suggest you make a Ti backup and exchange it, you'll be out a few hours of your life but the phone will WORK

I bought my Captivate on launch day, and I've been running the same firmware/baseband/kernel since day one. You were misinformed about an initial batch of bad firmware.

That is the same Firmware, Baseband, and Kernel everyone has...
You were misinformed.
Expect your GPS to work for a few days then crap out.

Same here. Got it on release day and have the same firmware. I have not noticed any issues yet.

jmreed97 said:
That is the same Firmware, Baseband, and Kernel everyone has...
You were misinformed.
Expect your GPS to work for a few days then crap out.
Click to expand...
Click to collapse
well my GPS didn't work out of the box but i just figured it was because I was in the mall. but as soon as I got the new one, it started right up.
facebook sync wouldn't sync properly either, and now it is syncing 100% fine
the phone would randomly shut down, it's been 4 days no shut downs
I dunno, I waited to post this to make sure it wasn't a fluke, maybe its just mine but it seems legit and my launch day device was definitely NOT 2.1-update1, I checked it right before I turned it in and it was just 2.1

yup, same here, got it on launch day, same info, but no dice on a consistent GPS lock.

you just got a bad phone dude. my friend got a launch day phone and his ate his external sd card, had a dead pixel, and would random shut off. just one of those thangs!

I got mine on launch day and have same firmware and everything. We didn't all happen to get a few bad phones. Samsung has manufactured phones that are bad from the beginning and they won't admit to it yet. This is worse then antennagate with apple.
Atleast then all you had to do was stick a piece of tape on the corner and voila! no problems. I wish fixing the issues with this phone were that easy. But we have the brightest minds at xda trying to fix our issues and they are still stumped by gps... nearly a month after release.
And even if xda minds can fix the issues... I find it extremely frightening that part time developers that do this for fun can fix issues faster then samsung can even admit to it(lag fix for example..) The more and more I think about this whole issue... the less I feel confident about Samsung as a mobile manufacturer.

V DidDy 210 said:
my baseband: I897UCF6
Click to expand...
Click to collapse
Are you sure it is I897UCF6, or is it I897UCJF6 ? Mine has a J.

Mine has JF6 also.

:facepalm:
everyones GPS works for the first day or two.

Can anyone confirm OP's post? It is possible that Samsung released a corrupted batch. At this point I almost want to unroot my Captivate and exchange it for a new one. I paid $500 for this and it's not working.
Speaking of which can someone PM an UNROOT tutorial for the Captivate. I'll be a guinea pig and go exchange my phone for a new one to see if this fixes any issues.

I returned my Phone yesterday and can confirm the GPS issue still exist on the replacement. Also, according to the sales rep this was from a newly shipped batch, so take it for what its worth.

So I wonder if I should even bother returning it?
This is a little ridiculous. This is supposed to be the best smartphone on the market and it can't even get a GPS lock in under 10 minutes.

IsaiahC said:
So I wonder if I should even bother returning it?
This is a little ridiculous. This is supposed to be the best smartphone on the market and it can't even get a GPS lock in under 10 minutes.
Click to expand...
Click to collapse
The Gps problem is a known problem for last few months, so i wouldnt be holding my breath for any fix to be coming out anytime soon. I am sure they will get around to it eventually if they do. Seems to me they are more concerned getting galaxy s phones out in multiple markets

IsaiahC said:
So I wonder if I should even bother returning it?
This is a little ridiculous. This is supposed to be the best smartphone on the market.....
Click to expand...
Click to collapse
According to who?

i have the same firmware as you bro, everything is the same with the same GPS issue as everyone else.

IsaiahC said:
Can anyone confirm OP's post? It is possible that Samsung released a corrupted batch. At this point I almost want to unroot my Captivate and exchange it for a new one. I paid $500 for this and it's not working.
Speaking of which can someone PM an UNROOT tutorial for the Captivate. I'll be a guinea pig and go exchange my phone for a new one to see if this fixes any issues.
Click to expand...
Click to collapse
So to follow up from yesterday, I installed a lag fix and messed my phone up pretty badly. I flashed back to stock rom and took it back to AT&T and exchanged it for a new one.
I HAVE ABSOLUTELY NO TROUBLE GETTING A LOCK IN UNDER 1-3 SECONDS EVERY TIME. Also, as a note, the SIM tray in the back of the phone is different than the one I had previously.
I'm not telling you to go exchange your phone but AT&T has an under 30 money back or exchange return policy. Just tell them you called Samsung or AT&T already and they told you to bring it in for a new one because it has trouble establishing a GPS lock.

Anyone try gps status app?
Run that first, get a lock then go to maps, should get a lock fast...

I Had my phone for 2+ weeks and gps works, not great but works (locks under 2 minutes if I can point to the sky, drop signal occasionally, pretty accurate).

Why I am not angry at Samsung or [email protected]

Maybe I am the only one, but flashing roms and learning how to screw up my captivate, and more importantly learn how to fix it afterwords, has made me not really care about when my phone will get 2.2 or 2.3. The developers here have made roms that I believe are just as good, if not better than the "official" versions. Sure Samsung promised 2.2 a long time ago, but what is the fun in just a boring update? Am I the only one who feels this way, or am I just addicted to flashing?

Here, here!

The only thing an official AT&T update would bring at this point in the game, would be better custom ROMs.
IMVHO of course.

I respect your right not to be upset. Still, I think there are a number of things to be legitimately upset about - none of which are addressed by the ROMS on xda.
The restart issue: this problem has been known for a long time. Neither AT&T nor Samsung have made it easy to get a working phone. They denied the issue for a while. They then recognized it, but never made the exchange process easy. Look at all the random shutdown threads and see the mixed experiences people have had. To make matters worse, broken phones are often replaced with other broken phones. AT&T has been either too lazy or too cheap to pull the affected IMEIs from circulation. People have gone through 2 or 3 phones before getting one that 'works.'
My GPS doesn't work at all. I can stand out in the middle of a field and my phone will see 1 satelite. I get a lock every once in a while, but it NEVER has tracked. I've tried just about every GPS fix out there and none of them work for me (and I shouldn't need to try a bunch of fixes off some internet forum anyhow). Has there been any help from AT&T or Samsung on this issue? - No. They seem to pretend it doesn't exist. To make matters worse, some phones seem to work as expected - BUT some of those have the shutdown issue. People are afraid to turn in their screwed up phone with a working GPS because they might end up with a 'normal' phone with a broken GPS. That's outrageous. Seriously, it shows the truly pathetic quality of the Captivate and the companies that manufacture/distribute it.
There are features that came on my phone that have still not been enabled. Media Hub, for example, was billed all over the place as a great new feature - to be enabled later. It's later...much later. When do I get Media Hub? I don't see it. I can't get it to work via any custom ROMs (unless I'm missing something).
The way that AT&T and Samsung have handled this situation reads as a case study in poor customer service. Is it the end of the world? No. Is it enough to get me to avoid another Samsung phone? Probably. I bet many others would say the same.

Custom ROMs saved me from hating this phone and made it a really great device in every way I can think of, but it doesn't excuse AT&T+Samsung's lack of support on this device.
All I can say is thank goodness for people on this forum who have the interest, know how and drive to do what those companies have not done: make the Captivate a great device.

delugeofspam said:
Here, here!
Click to expand...
Click to collapse
Where? Where?

Wdustin1 said:
acctually there is a working media hub .apk in one of the forums and it works great
Click to expand...
Click to collapse
Where? 10 characters

I agree, I love this phone and I'm thankful for samsung and AT&T not doing their job, because it's made people on these forums come up with some amazing roms/kernels/what-have-you.

The rom leaks developers are working on are part of a conspiracy. Think about it.

rwj5279955 said:
The only thing an official AT&T update would bring at this point in the game, would be better custom ROMs.
IMVHO of course.
Click to expand...
Click to collapse
Yup! My Sentiments exactly.

fldude99 said:
Where? 10 characters
Click to expand...
Click to collapse
It was on the Epic forums.
I tried this a while ago on one of the early versions of cog and it worked fine, but I don't use it enough to keep it on my phone. But I can confirm that it did work for me.

sarcasmo said:
I respect your right not to be upset. Still, I think there are a number of things to be legitimately upset about - none of which are addressed by the ROMS on xda.
The restart issue: this problem has been known for a long time. Neither AT&T nor Samsung have made it easy to get a working phone. They denied the issue for a while. They then recognized it, but never made the exchange process easy. Look at all the random shutdown threads and see the mixed experiences people have had. To make matters worse, broken phones are often replaced with other broken phones. AT&T has been either too lazy or too cheap to pull the affected IMEIs from circulation. People have gone through 2 or 3 phones before getting one that 'works.'
My GPS doesn't work at all. I can stand out in the middle of a field and my phone will see 1 satelite. I get a lock every once in a while, but it NEVER has tracked. I've tried just about every GPS fix out there and none of them work for me (and I shouldn't need to try a bunch of fixes off some internet forum anyhow). Has there been any help from AT&T or Samsung on this issue? - No. They seem to pretend it doesn't exist. To make matters worse, some phones seem to work as expected - BUT some of those have the shutdown issue. People are afraid to turn in their screwed up phone with a working GPS because they might end up with a 'normal' phone with a broken GPS. That's outrageous. Seriously, it shows the truly pathetic quality of the Captivate and the companies that manufacture/distribute it.
There are features that came on my phone that have still not been enabled. Media Hub, for example, was billed all over the place as a great new feature - to be enabled later. It's later...much later. When do I get Media Hub? I don't see it. I can't get it to work via any custom ROMs (unless I'm missing something).
The way that AT&T and Samsung have handled this situation reads as a case study in poor customer service. Is it the end of the world? No. Is it enough to get me to avoid another Samsung phone? Probably. I bet many others would say the same.
Click to expand...
Click to collapse
Very well said! Btw, LOVE the screen name, lol.
I don't even own this phone, my gf does and I've done limited research so I could flash Cog2.3b8. The phone is WAAAAY better with Cog, but the gps blatantly disappeared on us halfway to our destination last weekend. I sighed and pulled out my mt4g which caught a lock in about 1/10th of a second and guided us there with absolutely no errors.
This made ME feel pretty stupid considering I gave her the phone as a gift. Thank god I bought it used and can probably sell it for what I paid for it.
From my limited experience with AT&T and Samsung I am furious. This phone had tremendous potential but I will avoid Samsung and AT&T like the plague from now on.
Delaying updates is one thing but the GPS issue is ****ing ridiculous. It's a joke!! There's no other way to describe it. You should all be irate and demand your money back.
Yes, T-mobile has had QC issues with the MT4G but everyone in the thread who has returned their phones has praised T-mobile for the way they handle their customer service, including myself. How many have had that experience with AT&T?

You should still be mad at Samsung.
Instead of making good ROMs great, we're making crappy ROMs good.

vunuts said:
It was on the Epic forums.
I tried this a while ago on one of the early versions of cog and it worked fine, but I don't use it enough to keep it on my phone. But I can confirm that it did work for me.
Click to expand...
Click to collapse
It worked for me as well. I just didnt care for it. I would much rather have netflix. I have a different apk somewhere around here. If his doesnt work for you let me know via pm and I will send it... nm i just posted it

Phateless said:
You should all be irate and demand your money back.
Click to expand...
Click to collapse
Nah. I don't really need GPS, and last time I tried it outside my work building it got lock in about 2 or 3 seconds. I've tried it a couple of times while driving with mixed results. It seems to depend a lot on the area. As expected (or maybe not), it seemed to worked the best in the "wealthy" part of the city. I live in San Jose, Costa Rica.
Other than that I don't know. I haven't had any single random restart that I know it wasn't caused by me, same with charging death, mainly caused by bad UV settings.
I only used the stock rom for about 2 days before I moved and lagfixed it. I killed it once in a bad kernel flashing attempt. The fact that I can revive it using a home made usb jig makes me love it even more.
Right now, I just wished people could experience that same phone I'm experiencing. I think I'm in love with it.

I'm mad at both. My Captivate is my work phone, provided by my employer - so I am less comfortable flashing it to overcome the shortcomings of the standard AT&T build - yet I did root the phone and install the MobileAP so I can actually work when my client doesn't let me connect to their network.
My beef is on smaller things like - disabling tethering, not having more robust support for Exchange, the inability to sideload, or even load Android Market apps that AT&T doesn't want me to see.
As a work tool, I want my phone to let me work, and these limits, largely self-imposed are galling.

I've learned so much over the last week. I must have flashed my phone at least 20 times and got a few good bricks out of it too. Samsung and At&t can do what they want. These roms works much better than anything they could ever do.
Sent from my SAMSUNG-SGH-I897 using XDA App

I'm not mad at Samsung or Rogers for the reasons stated above, I'm mad at them for broken promises as they relate to hardware - namely the USB-to-HDMI issue, which was a big reason for me to go with this phone over another. We were promised a software update to enable this and were even shown a cable on the official Sammy site, but nada.

[Q] Can someone with a stock Verizon build test Netflix? (audio sync issues)

So this is a bit of a cross-post from here where I asked the general M8 community.
There is at least some minor evidence that T-Mobile and/or Sprint M8's do not have this problem - but at least on the former it may be due to a custom ROM.
Basically Netflix audio sync is off. You will see lips move a good .25 seconds before sound comes out. That may not sound like much, but it is very noticeable - like watching a bad dubbed movie.
As the thread above shows, I have tried just about everything I can think of. I'm 100% sure it's not my network connection, Netflix account, or show - as everything works fine under the same controls on my wife's S5.
I'm sure there has to be a good chunk of people who use Netflix, and I find it hard to believe I'm not finding more reports about this problem.
thanks.

I just tried it on mine. Stock 4.4.3. Seems just fine. I tried several different movies and they all seem to play as they should.

I tried it on my wife's which is running sense and I didn't notice any sync issues either

robocuff said:
I just tried it on mine. Stock 4.4.3. Seems just fine. I tried several different movies and they all seem to play as they should.
Click to expand...
Click to collapse
Just doesn't make any sense. If mine doesn't work - and the Verizon one I tried didn't work, and the AT&T one I tried didn't work... ???
I'm thinking about swapping it out (again), but since every one I've actually had my hands on has this issue, why should I expect any to function?
Advice?

TraderJack said:
Just doesn't make any sense. If mine doesn't work - and the Verizon one I tried didn't work, and the AT&T one I tried didn't work... ???
I'm thinking about swapping it out (again), but since every one I've actually had my hands on has this issue, why should I expect any to function?
Advice?
Click to expand...
Click to collapse
Why not try flashing the vzw adsp and see what happens. You can easily flash back to what you had originally

dottat said:
Why not try flashing the vzw adsp and see what happens. You can easily flash back to what you had originally
Click to expand...
Click to collapse
I'm not S-Off on this phone yet and am not going to pay for sunshine until I'm 100% sure I am keeping this phone (don't want to pay if I need to return it). I usually prefer to run a stock (close to stock ROM)... although if I could I certainly would flash another to test. But, at this point I'm stock to only trying things on stock.

TraderJack said:
Just doesn't make any sense. If mine doesn't work - and the Verizon one I tried didn't work, and the AT&T one I tried didn't work... ???
I'm thinking about swapping it out (again), but since every one I've actually had my hands on has this issue, why should I expect any to function?
Advice?
Click to expand...
Click to collapse
I don't know what to tell you. It is odd that you see the same problem on multiple devices like that. I tried it again and watched for the slightest bit of out of sync and mine is spot on. I'm pretty fussy about this type of thing too. Used to have PMP. I'd rip my own movies to put on it and would run into sync issues like this once in a while. Drove me crazy. That's not much use to you but I'm just trying to get the point across that if mine was out of sync, I'd notice it.

robocuff said:
I don't know what to tell you. It is odd that you see the same problem on multiple devices like that. I tried it again and watched for the slightest bit of out of sync and mine is spot on. I'm pretty fussy about this type of thing too. Used to have PMP. I'd rip my own movies to put on it and would run into sync issues like this once in a while. Drove me crazy. That's not much use to you but I'm just trying to get the point across that if mine was out of sync, I'd notice it.
Click to expand...
Click to collapse
I do appreciate it...knowing that someone else is on Stock and cognizant of the issue, but not seeing it.
Curious how long have you had your M8 for and if it is the standard Gunmetal grey?
Also...are you rooted and/or Unlocked//S-Off? Have you ever flashed a custom ROM or been on stock?
Finally, are you running the latest Netflix from Play Store? (updated Sept 9th)

Or try installing an older Netflix.apk? That's what I'd try.

TraderJack said:
I do appreciate it...knowing that someone else is on Stock and cognizant of the issue, but not seeing it.
Curious how long have you had your M8 for and if it is the standard Gunmetal grey?
Also...are you rooted and/or Unlocked//S-Off? Have you ever flashed a custom ROM or been on stock?
Finally, are you running the latest Netflix from Play Store? (updated Sept 9th)
Click to expand...
Click to collapse
My phone is one of the earlier ones. Bought it 4 days after the launch date. And yes, it's gunmetal grey. It's rooted, unlocked, and S_Off. Has been since they released Firewater. Seems to me that was within the first 2 weeks after launch.
I've flashed quite a few custom roms in the past but it's been a while now. Stock Sense suits me just fine (first time I've ever said that about stock anything ) . I always ended up coming back to stock. I can make all the tweaks I want using things like xposed or a root file manager and stuff still all works
As for the version of Netflix I'm using, mine was a version or 2 behind but I just updated it to the newest this morning to see if there was any difference. I still don't see any sync issues.

calebcabob said:
Or try installing an older Netflix.apk? That's what I'd try.
Click to expand...
Click to collapse
I did backrev to two different 2.x versions and then finally an 1.8x version. They all had issues, although the 1.8 was much less noticeable. I may not have even noticed it on that one if I hadn't had the previous issues. Of course, 1.8x is over 2 years old and has some other buffering issues.
robocuff said:
My phone is one of the earlier ones. Bought it 4 days after the launch date. And yes, it's gunmetal grey. It's rooted, unlocked, and S_Off. Has been since they released Firewater. Seems to me that was within the first 2 weeks after launch.
I've flashed quite a few custom roms in the past but it's been a while now. Stock Sense suits me just fine (first time I've ever said that about stock anything ) . I always ended up coming back to stock. I can make all the tweaks I want using things like xposed or a root file manager and stuff still all works
As for the version of Netflix I'm using, mine was a version or 2 behind but I just updated it to the newest this morning to see if there was any difference. I still don't see any sync issues.
Click to expand...
Click to collapse
Thanks. I think I'm going try to get another replacement - although I don't have high hopes based on the fact that the other ones I've had my hands on had the same issue.
One last thing...can you tell me one show/movie that you were watching that looked good to you (time stamp too)?
I can't believe I just had bad luck with the 3 I picked, especially since they looked fine on my wife's phone.

Well, just received my 3rd M8 from the retailer.
1st one I didn't test the Netflix issue on because I had a return issued quickly due to the screen not being flush and loosey buttons.
2nd one is what i have posted about here with the Netflix issues.
3rd one just arrived - screen also has quality issues, not being flush where it meets the grill (and no, it wasn't designed to be that way as my 2nd one is almost perfect and the other two vary the level the glass meets the grill in a variety of ways...inconsistency means that at least 2 of the 3 of them are wrong).
Anyway... I have the exact same issue with the audio sync on the new phone as well.
At this point, I have to believe that every M8 has this issue and those that don't see it either haven't tried or don't care enough to notice.
Perhaps this issue only happens with the Stock ROM, which is why many of you don't see it(?).
I have watched half a dozen shows/movies on Netflix and all of them have the issue. I would say 4 of them it is just blatant...easily a quarter second off or more. On the other ones, it is maybe barely noticeable...but still there.
Again, I have tried 2 M8s that were in my possession, one in the Verizon store, and one in the AT&T store (4 total).
I've contacted Netflix and they were mostly useless. They claim they escalated the issue to R&D, but could provide me no sort of ticket tracking or call back, which basically means nothing will ever be done.
I was surprised that HTC support took more interest than I thought, since I normally would blame this issue on the software vendor as they should be the ones responsible for coding to work with a particular OS. HTC escalated as well, but by the time someone gets back to me on it (7-10 days), my return period will be over. Even then, I doubt HTC will do anything about it as it appears to only be Netflix (not YouTube). OTOH, seeing as Netflix works fine on their competitor's phones (S5), maybe they will actually pursue it.
I appreciate that some people responded that they don't see the issue - but from my standpoint...you can understand how I can't see that it is possible that I have tried 4 phones (from 2 providers) that all have the issue. I have no explanation.
The only thing I haven't tried on these is to run something other than Stock, because I can't firewater S-OFF, and am not paying for Sunshine since it is tied to device and I have had to switch the device so many times.
Right after I did the tests today, Netflix appears to have gone down. When I get back from dinner tonight I will post a couple of samples that show the issue clearly and some others where it is more minute.

New Girl - Season 3 - Episode 1 - Starting at 3:25 (after intro), the whole conversation between the two dudes. It is really clear when the white guy says at 3:35 "To become best friends" and at 4:37 when he says "I'm also a socket." Really the whole conversation it is evident, but these two lines it is exceptionally apparent.
3 Days to Kill (Movie) - 49:58 "I'm plugging in my phone, this stuff sucks." In reality, much of what I skimmed through in this movie looked pretty good...I think it is partly because of how the actors enunciate and move their lips (as opposed to the white guy in New Girl who really moves his lips when he speaks). But, here at 49:58 you can see it off.
Bones - Season 1 Episode 1 (Pilot) - 15:36 "Lennie Kravitz or Vanessa Williams"
There does seem to be a bit of inconsistency in how good or bad things are. Usually, I can see something off within the first 10 seconds of conversation, and sometimes I need to watch a couple of minutes. I'll admit that there are some points where it looks almost perfectly fine - enough that I might not have detected it were there not these more blatant areas.
Nonetheless, when I watch on my PC, or on my wife's S5 there are absolutely zero problems.
Netflix still seems to be flaky right now, so I'm not going to try to get more examples until I get some more feedback.

I have the same issue. I just installed the newest firmware and update and the poroblem is still there. I do have the HK audio installed, maybe I should disable it? It's only an issue with netflix though.
Ordered a chromecast, it better not persist the problem onto that!
Then again youtube has it's own problem, seems to be network throttling to me pauses every 10 seconds or so...Been like that for some time too.
BTW most M8's don't have perfectly flush screens, those seem to be the anomaly rather than the standard. Some are worse than others though. I honestly never really notice it though in use, just when I first purchased.

Justintoxicated said:
I have the same issue. I just installed the newest firmware and update and the poroblem is still there. I do have the HK audio installed, maybe I should disable it? It's only an issue with netflix though.
Ordered a chromecast, it better not persist the problem onto that!
Then again youtube has it's own problem, seems to be network throttling to me pauses every 10 seconds or so...Been like that for some time too.
BTW most M8's don't have perfectly flush screens, those seem to be the anomaly rather than the standard. Some are worse than others though. I honestly never really notice it though in use, just when I first purchased.
Click to expand...
Click to collapse
Good to know that the issue is still there with HK (which means you upgraded the audio DSP, right?). I wanted to try that, but since I'm not S-Off I couldn't.
I have hardly used YouTube, so haven't seen a throttling issue...I just watched a few videos long enough to validate there were no sync issues.

No way this is carrier specific. I just installed 4.4.4 Pac man Rom on my nook HD+, then installed netflix. Audio is also out of sync, maybe not quite as bad as the M8 (which is faster) but it is still an issue. It does not look like it affects the chromecast though.
Looks like LG, Motorola Maxx and other phones are also having issues. Might be more or less related to 4.3 / 4.4 android devices.

Well it's not just 4.3/4.4 since my M8 was tested on 4.2.
The only other KitKat device that I tested on was a G5...and it was flawless there.
I suppose though if there are a lot of other devices having issues on KitKat then it definitely may be more of a Netflix problem.
Also, due to the extreme lack of response to my post, and others I have seen over the past year on various devices, most people claim not to see the issue.
I can only believe that (at least on the M8) these people either don't watch closely enough to see/care, or else they are almost impossibly watching only shows that it wouldn't be visible in (which based on my sampling would be pretty amazing).
I have an escalated case with HTC and they should be getting back to me shortly if they can recreate the problem.
At this point I'm just as frustrated that no one else is making this an issue as I am that it is one. If I can get HTC to at least admit that there is a sync issue, then I will at least feel exonerated and perhaps other people will begin admitting that they see issues on their devices as well. If this extends beyond the M8, then likely Netflix is the one that is going to need to be prodded by the public to get their act in gear.
I supposed i would be a nice test if someone had a device that could run something pre KitKat to see if the problem doesn't exist, and if it arises when upgraded to KitKat.

TraderJack said:
Well it's not just 4.3/4.4 since my M8 was tested on 4.2.
The only other KitKat device that I tested on was a G5...and it was flawless there.
I suppose though if there are a lot of other devices having issues on KitKat then it definitely may be more of a Netflix problem.
Also, due to the extreme lack of response to my post, and others I have seen over the past year on various devices, most people claim not to see the issue.
I can only believe that (at least on the M8) these people either don't watch closely enough to see/care, or else they are almost impossibly watching only shows that it wouldn't be visible in (which based on my sampling would be pretty amazing).
I have an escalated case with HTC and they should be getting back to me shortly if they can recreate the problem.
At this point I'm just as frustrated that no one else is making this an issue as I am that it is one. If I can get HTC to at least admit that there is a sync issue, then I will at least feel exonerated and perhaps other people will begin admitting that they see issues on their devices as well. If this extends beyond the M8, then likely Netflix is the one that is going to need to be prodded by the public to get their act in gear.
I supposed i would be a nice test if someone had a device that could run something pre KitKat to see if the problem doesn't exist, and if it arises when upgraded to KitKat.
Click to expand...
Click to collapse
Maybe the lack of response indicates that few people watch Netflix on their PHONE??
Love the screen, but for watching movies I switch to tablet or smart TV....

berndblb said:
Maybe the lack of response indicates that few people watch Netflix on their PHONE??
Love the screen, but for watching movies I switch to tablet or smart TV....
Click to expand...
Click to collapse
The fact that the phone isn't the optimal media for Netflix doesn't diminish the problem. Although, admittedly I'm sure it is a secondary or tertiary outlet for most...as it is for me, it is still supposed to work (i.e. it is listed as a compatible application). Additionally, it has worked on other phones/versions of android...so there is obviously some issue.
I Netflix doesn't want to support it on phones, because they think it is unimportant, then they should clearly indicate it is not compatible. Since many new phones are 4x+ more powerful than a $40 tabled that runs Android, there isn't a great reason why it shouldn't work fine.

October 15th update of Netflix hadn't made anything better.
HTC was supposed to follow up with me and it has been 3 weeks. I am reaching out to them today to see where they are with their testing.

Database Info

welcome