So I just got a brand new Galaxy S after my old one bit the bullet, and now within 2 days of owning my new one it keeps backing out of everything. It's like the back button is being pressed every few seconds. So no matter what application I am using it won't stay open. Any answers?
Mine is doing the same thing, the home button also gets stuck occasionally. I called tech support and supposedly they are sending me another replacement.
Same here
My third phone did the same thing after I upgraded to froyo. I was ready to take it back but I tried doing a factory reset (dialed the reset number) and after a couple more of the phantom button preses it just stopped and has been okay for a week or so now.
Not the best way to fix it but at least I didn't have to have it exchanged again... yet.
Bill Fahey
Edmonton, AB
So you say that you upgraded to froyo and now it.s only backing up
Maybe you have to upgrade to android 2.2.1 nobody knows what improvements there are in 2.2.1 maybe we have just found the awnser
Try and report back i want to know
And a last option is to go to the shop were you bought it maybe they can help
Sent from my GT-I9000 using XDA App
Mine has been doing it on 2.2 and several 2.2.1 roms actually. The reset did fix it for a day or so but it came back.
ok, that's weird
One thing to do left go back to the store or contact with
Samsung service & repair
Related
Well I'm not sure if it was from the multiple ROM flashes and what not, but my Captivate started acting like I hit the bottom back key as it would randomly go back in the browser or exit out of programs. The back key would blink like I pushed it and vibrate. So fortunately I was on the last day of my 30 day return period with Amazon, and they sent me a new replacement. Anyone have an idea of why it was acting up? Those bottom keys are touch so I wouldn't imaginr they could get stuck unless the sensor got messed up somehow.
Sent from my SAMSUNG-SGH-I897 using XDA App
himmelhauk said:
Well I'm not sure if it was from the multiple ROM flashes and what not, but my Captivate started acting like I hit the bottom back key as it would randomly go back in the browser or exit out of programs. The back key would blink like I pushed it and vibrate. So fortunately I was on the last day of my 30 day return period with Amazon, and they sent me a new replacement. Anyone have an idea of why it was acting up? Those bottom keys are touch so I wouldn't imaginr they could get stuck unless the sensor got messed up somehow.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
well I can hopefully tell you what it is. you seem to have a similar problem to what I did. i even called samsung for an RMA then figured it out and canceled lol. mine ended up getting REALLY bad and it annoyed the holy hell out of me. I went to the fair the day before I noticed it and thought when I was riding a ride I jacked it up. Little did I remember I 1Clicked back to JI6 and updated Cog right before we left..
What I determined was when I used the 1 click Odin to go back to the JI6 (iirc) and it has something to do with the Kernel. I flashed up to JH7 OTA using the other Odin and it fixed the issue.
You can see what touchscreen driver you are running by using the SGS Tools, go to the secret codes, in there theres something about touchscreen firmware version. I think the version on 6 is like 0x15 and the one on 7 is 0x16. I dont remember the number perfect but that is what I figured out. For soem reason when I flashed with the 1 click, then up to a COG release it kept the touchscreen from JI6 and my phone DID NOT LIKE IT. Also if you hit Update- it will kill the keypad and you have to reboot for it to work again.
Give that a go and see if it fixes the issue. If you dont want to flash 2.1, bump to Cog2.2 Beta X and I bet that will fix the issue too.
Eitherway, check your touchscreen driver. The touch key part is what you are specifically looking for- the part at the bottom of firmware version info page.
If you dont have SGS Tools, open the phone dialer and punch in:
*#*#2663#*#*
Well I did in fact go from the one click to the cog, but then when I just cleared everything and flashed back to the one click again, it was still there. I just got my replacement today, so I guess I will just take the new one since its free lol. But thanks to you I now know what to do should it happen again, though after that I'm a bit apprehensive about flashing :/
Oh and on this new one I updated it straight out of the box so I could avoid the failed updates, and the version is 0x16 as you said.
Sent from my SAMSUNG-SGH-I897 using XDA App
2 weeks after I got my SGS i had to swap it for a new one due to it bricking and seeming to be from the internal SD card issue.
A week ago it happened on the replaced handset.
The phone was sitting off on the desk, picked it up to check something and it would not turn on.
It would turn on the phone to the intro text screen before the animated S but go no further.
occasionally i could get it to boot past it into the OS but it would not read and forced closed basic functions like contacts and phone.
this was rare to occur.
Anyways, my question is did you get your phone repaired and how did it perform after? My worry is that it will come back seemingly repaired and start to act up again.
Also, did they repair it or replace it?
My phone is being repaired through Bell.
i should also state that my phone was stock everything on the latest official 2.1.
I dont have it with me so I dont know the release dates.
I purchased it August 16th and replaced it on the 25th.
SGS my baby!
well believe it or not ...i replaced my SGS 3 times in the last 2 months ...now i am back on the stock Eclair 2.1 No lag fix ...no nothing ...will wait for the official froyo 2.2 i hope its bug free ...as much as i love this SGS i would like to mention this dead sd card problem is a real turn off
oh did i mention my bro and cousin had to get their exchanged as well twice each ...i know what ur thinking all r back on stock Eclair 2.1 ..but honestly if u have patience Eclair isnt bad ...i have no issues with GPS and i do use gps a lot n i mean a lot ....me i am happy i bought SGS.... now all i need is an official froyo 2.2 without any need of lagfix.
that sucks.
my hope is that now that the new batch of phones are in (my guess is that during that dry spell where there was not an sgs anywhere in town they did a hardware fix) that the repairs will take better than when they were fixing them with faulty hardware.
here's to hoping we dont see any further issues. if it happens again i'll be selling the sgs and getting whatever the next best phone is. let it become someone elses problem.
Had the phone *repaired* not replaced 2 times and now it seems to finally be working properly. First time i sent it in because it would force close apps all the time and I didnt have 3 button recovery. Got it back and a few days later the SD card died... got it back a week ago and it is working so much better. So i suggest just getting your phones repaired not replaced. It will take longer, but in the end less problems will arise i think.
I voted for worked for a while, but borked later on.
Basically, I sent it in for repair in september, got it back in october, broke 3 days later, sent it back in and got it back last week and this time they replaced the mobo. The first time I brought it in, all they did was a reflash.
During the 3 days, I got FCs like mad, and freezing every hour or so until it died.
After the mobo replacement, I have had it for 6 days so far, and so far so good!! No problems yet.
surprised it took this long, had counted myself one of the lucky ones.... even though i was one of the unfortunate saps whose phone came with the three button recovery disabled, (a two week trip to samsung for repair).... was running darky's rom 9.3 and various eaarlier versions since october with no problems... today google voice started force closing so i tried to reboot the phone and it would not boot up again... i went into recovery and tried a wipe, still no go.... then i tried to reinstall the rom, still no go.... when it is booting up it just keeps looping the loading screen and vibrates once, then pause, then three times... i can get into recovery and download mode.
anywhose my questions are this,
A) best way to determine that the SD is in fact bricked.....
B) best way to get a bricked SD card back to stock so i can send it back to samsung for warranty.
C) if i get it back fixed from samsung, should i try to off this piece of Sh*t phone that has given me, and others soooooo many problems. that is to say, has anyone who has had their phone fixed recently had their new SD card go corrupt again??
P.S. never buying anything samsung ever again, PERIOD!!, had a 30 inch monitor of theirs recently go bad as well, like i dont care if they cure cancer, bring peace to the middle east, and resurrect jesus!!! i still wouldnt buy a rememberance day poppy from them!!!!!!!
Sounds similar to mine when it bricked. The best solution is to use Odin and flash jl2 onto it and send it in for repair.
They were doing a replacement and compensation program through bell for a while but I think that's over now.
On the plus side, since my repair in December the phone has been amazing. No problems flashing different roms many times. The phone has been better than I expected! The number of phones dying from this issue have dropped significantly since the new year.
Sent from my GT-I9000 using XDA Premium App
is there a link you have to flashing this frimware with odin? never used it before....
hope the replacement and compensation is still going on, kinda pissed that bell didnt call me about it...
tried flashing JL2 with odin, when i have odin open and my phone in download mode, and i plug the phone in, windows does not recognize my device and thus does not install drivers for it and thus im pooched.... ergo vis a vis help please
i know im just talking to myself but just in case anyone wants to know, installed kies to get usb working, flashed JL2, gonna take phone in for repair now (2nd time) awesome!!!
Sorry it took me a while to reply. Forgot to check this thread. There are a bunch of threads about dealing with it. If you get a hard time there's a thread you can search for about filing a complaint to the ccts. That would get you the replacement and comp I think. Good luck!
Sent from my GT-I9000 using XDA Premium App
Hey guys,
my captivate has been freezing when using regular phone features such as calling, sending txts, opening up contacts, and etc about once every two days.
It's been doing that ever since I've been messing around with this captivate
Factory reset and returning to stock did not help. I did not flash back to saved rom either. This even happens when using stock version.
As I could not find any solution, I called AT&T and told them that my phones been doing 'this' after upgrading to 2.2 and also told them that my desktop shut down due to power outage during the process.
So the question is... will they know what I've done and charge me?
They won't know. I took one back (to a service center) when the GPS was complete crap, after I flashed several ROMS then went back to 2.2 stock via KIES mini. The guy took it inthe back for a few minutes, then came back with a replacement. It probably was a refurb but hey, it works perfectly, has great gps, looks brand new, and all the button combos work great. I don't think they will know what you did with it, as long as it has the stock 2.2 on it that came fromo KIES mini.
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.