Hello guys. I recently installed Ultimate JPY v7.2 and now I have more lock shutdowns then usual. I have a version 1007 phone and it had fairly infrequent random shut downs that happened only when I locked the phone. Now they happen 1/5 times I lock the phone. Is it my phone, or the Rom? And is their a solution for either of them?
You can try different ROM first, like Phoenix, etc. Otherwise, it will be phone's problem.
are you in the defective imei range (anything below 6000 on last four of your imei)?
If you ARE in the defective range, I suggest you try using a more stable ROM, like Cognition or Darky's, and waiting for the new ATT Android phones to come out; warranty departments over the phone are advised about the random shut offs and have to replace it.
You might want to look into the Inspire, Infuse, or Atrix, the three new comparable models to the Captivate.
I'm not in the IMEI range, and if I tell AT&T will they replace it or will they give me a different a complete different phone all together? This is a defect and I'm not forking over another 200 dollars for a new phone. I'm happy with my captivate, but if need be I'll transfer to a different phone, but I'm deffinately non giving ANY more money to AT&T then I already am.
I had this issue with latest Darky 9.0.2(?) (using the v8.1 > Darky App method). Wasn't sure what it was, so I just flashed a different rom and the problem didnt follow me.
I had a ton of them on ultimate 7.2, a few on darkys pheonix di11i and stock. So i dont really know if its my phone or rom
Sent from my GT-I9000 using XDA App
Related
**THIS IS FOR I9000M ONLY**
I'm just wondering if others with a manufacturing date of 12/10 have any SD issues. I've updated to JL2 with mine and it's working great. GPS even seems to be fixed (as though it was a hardware issue and not a software). This GPS works flawless.
SO, my question is for those of you that have a phone manufacturing date of 12/10 (10/12 on the phone behind the battery - i.e. December 2010) AND you have updated to Froyo (ANY FROYO, particularly non-Bell specific ones such as JK4 and JL2), have you had any problems with your SD card?
My says 10.12 on back of the battery. I updated to JL2 since yesterday and no problems at all (had to do a factory reset since market didn't want to work, other than that nothing else). It would be cool if they fixed the internal sd card problem, I don't have to be too scared .
JL2 is supposed to fix SD Card issue, so users with device before september should have no problem.
As for the GPS, I can't tell since I've just installed JL2, but I haven't got any major problem with JK4 neither, so!
So far so good for me. Been running for about 5 days. Was on JL2 and now I'm on Darkyy's 7.0 Rom.
Okay, then I guess what I'm asking is...has anyone updated to ANY version of Froyo with a phone manufactured 12/10 and had SD card problems.
Although, I don't really see JL2 making much of a difference. I'm basically wondering if the SD card in 12/10 phones are like the other I9000 models where you can install any ROM and not have problems.
I'm running Doc's 6.2 with JK4 modem. No problems so far, and GPS actually works properly.
Sent from my GT-I9000 using XDA App
is there an actual manufacture date on the phone, and not the battery? for instance my buddy's phone got replaced, but he kept his original battery, so he doesn't know when it was made. i assumed going by the IMEI it was a 98, when the one he had before was a 53.
There is a sticker on the phone under the battery, mine is12.10, and it came with froyo JL2 out of the box.
Sent from my GT-I9000M using XDA App
How do you check how many satelite your device is connected to. Just got this and was wondering.
Sent from my GT-I9000M using XDA App
ive only had my 10.12 phone 1 day so far so i wont vote yet, but ya so far so good. my august manufactured phone died within 24 hours of the first 2.2 update so im past that point anyways.
I have a 10.12 phone. Got it on Thursday but have been to scared to update to jl2 yet. As I have previously reported however with this phone my gps has been flawless using jh2.
Sent from my GT-I9000M using XDA App
My phone was replaced with one manufactured 10.12. Next day I installed Darky's 7.0. So far, so good!
i hope no more SD card problems
i had Dead Sd card issues with 3 I9000M yes 3 ..they were on diffrent firmwares JH2 and JK4 all 3 died .Now i own a iphone 4 ..i am planning to replace it with I9000M i hope this SD card issue is fixed for good with 10..12s manufacturing dates and JL2 firmware .Keep us updated guys ...OH ya i hope if we install custom roms on the new 10.12s we dont get DEAD SD .i am sure that dead SD card was mostly hardware related issue
Been running JL2 on my 10.12 replacement for 5 days now. I recorded about an hour or so wourth of video + have 5gb wourth of media on a 16gb external SD card. My phone was locking up and being unresponsive the past few days at first I thought it was the lag fix but now I narrowed it down to the bluetooth as it always seemed to be locking up when right after turning off my truck. I installed a stereo with bluetooth everytime it drops the connection when turning off my truck it locks the phone up for a good 5 minutes before it becomes responsive again. Anyone else experienceing this issue with bluetooth on headsets or stereos?
Aside from those issues my phone is still alive I'm tempted to install hardcores kernal or possibly switch to doc's rom to see if it fixes the issue. Worse thing that could happen I guess is I get $100 credit to my account and another SGS replacement.
Is it strange that I want my 2 i9000m's to die so I can get December ones?
a friend of mine actually works at the samsung repair center, he told me that there is a internal hardware differences betweent the i9000 and i9000m. the i9000m is actually uses less parts to cut cost. of course, samsung and bell didn't know this will cause all these i9000m failure. and he told me the new build will still have the same issues, the engineers at samsung is only using software to avoid these potential problems from coming up not hardware because of cost of replacing these i9000m units.
htp1498 said:
a friend of mine actually works at the samsung repair center, he told me that there is a internal hardware differences betweent the i9000 and i9000m. the i9000m is actually uses less parts to cut cost. of course, samsung and bell didn't know this will cause all these i9000m failure. and he told me the new build will still have the same issues, the engineers at samsung is only using software to avoid these potential problems from coming up not hardware because of cost of replacing these i9000m units.
Click to expand...
Click to collapse
Yeah, that's a bunch of bogus.
well, i don't know why you say this. I owned a galaxy s myself, and i love this phone. Why do you think there are so many problems with this version of galaxy s compared to the regular i9000? you don't think there is differences in the manufacturing process and parts source? To me, this phone has manufacturing flaws.
And today, what pissed me off more about this bell galaxy s is that. They no longer do warranty service for ppl who bought this phone off of another bell user even if you have the original receipt with the phone. You need to call this number they provide you, and you need to have an active bell mobile account in order for them to do the replacement of the galaxy s. And FYI, my i9000m died on christmas eve after a week of darky's rom, which makes me believe that i9000m is prone to custom rom.
nemethb said:
Yeah, that's a bunch of bogus.
Click to expand...
Click to collapse
you can say that again
... there are pictures on other topics showing the internals of the phone, there are no more no less, just different chipsets
AllGamer said:
you can say that again
... there are pictures on other topics showing the internals of the phone, there are no more no less, just different chipsets
Click to expand...
Click to collapse
different chipsets = different manufacturing process
I just recieved a new phone from futuretel because my last one died. However, after reading through several threads, it seems all SGS vibrants with the 16GB storage are all dying regardless of where its from or when its made.
It is also noted that updating to froyo also increases the rate of decay. Has anyone had this issue? and also how are custom firmwares affecting the phone? As this sounds like to be a hardware issue, does anyone have any suggestions?
I would like to have all these questions answered before i take the plunge and update to froyo.
thanks
Well, Samsung has stated the supposedly the new JL2 firmware fixes the issue, however there have been reports (albeit much, much less) of phones running the JL2 firmware that are still dying.
Personally, I got my phone back 2 days ago and it was already running JL2. Flashed a custom JL2 firmware on top of it and I've been lovin' it. If it dies again, oh well, I'll just get another one from bell in 3-5 days.
For those that have received their replacement i9000m's from Bell/Samsung, what are you doing to them regarding ROM's and Kernels?
I am awaiting my second replacement (5th phone in total) and am quite hessitant to do anything with it. I am interested in knowing what others have decided to do ...
I'm getting my replacement phone back soon as well, (with JL2). I haven't found a concise answer on here. Has JL2 fixed the problems, or do the new phones still have defective hardware? If not, its outrageous to think that samsung would continue selling these phones, even though they know if has major issues.
I'm probably going to sell my phone on kijji when i get it back, and go buy an HTC. I'm sick of this, and just want a phone that works. right now I'm stuck with my treo pro, that is so slow and crappy.
My new phone (Date 10.12) has JL2 on it and has been working great for almost a month. The only thing I did was root it.
Ian
I'm not screwing around with mine. I'll stress the internal SD card but beyond that, I'm not gonna get too brazen. Right now, JL2 is running fine, is really quick and so is as advertised (2.2 I mean). Mind you, I just got it back yesterday from Bell (just reflashed to JL2 - no replacement or hardware replacement) so I guess time will tell.
I'll probably update it to JL2 (if its not already)...
when I get my phone BACK... been stuck in "In Transit to Store" for a freaking WEEK already... stupid Bell... I mean I can probably walk it from their service stores back to the store in less time... wtf...
I'll consider installing darkyy rom on it when official Gingerbread comes out instead of the gingerbread theme...
I just want my phone back ..!!
I received my phone back with a new board inside and JL2 already installed. I tried to root it with z4root in order to use OCLF abut it keeped crashing on me without being able to do anything. So i uninstalled everything. However, I can say that the phone is working great and is quicker than before.
I noticed that jl 2 in recovery mode gives option to format internal sd card. Until now my phoned is working ok but I haven't restarted it for a week. So.... Lets hope for the best.
Sent from my GT-I9000M using XDA App
ravi31naik said:
I noticed that jl 2 in recovery mode gives option to format internal sd card. Until now my phoned is working ok but I haven't restarted it for a week. So.... Lets hope for the best.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Yes, that is a 3e recovery feature.
Unfortunately totally useless when you get the dreaded 'cannot mount SDCARD error' as it cannot format what it cannot mount.
Sorry for my lack of knowledge on the subject - but are you guys all having issues with failing phones? If so, is it a specific version and how do I find out where I stand?
been following seeARMS bell JL2 rom for a bit and it seems good. he has some info there on corrupted SDs.
ive been using it for a few days and i have no complaints. its located here http://forum.xda-developers.com/showthread.php?t=906977
My phone died a few days after putting on JK4. I got it back on Dec 24, and about a week ago put on Darky's v8. It's not necessarily better, but definitely looks different.
After bricking my 1st one (me or the firmware), I got my new Galaxy S today, installed the speedmod kernel and then darky's 8.0, working perfectly, I've got root, most of aps back in and set up already. Will try it for a few days before running the lagfix. Scored about 1100 on quadrant as is.
The replacement phones are shipping with either JH2 or JL2. Neither of these are proving to prevent sd card failure. Period. Sorry for the bad news.
Btw, I received a jl2 (10.11) phone. I've since flashed a doc rom with jl2 modern. Works awesome so far (no lagfix).
gtg2 said:
The replacement phones are shipping with either JH2 or JL2. Neither of these are proving to prevent sd card failure. Period. Sorry for the bad news.
Btw, I received a jl2 (10.11) phone. I've since flashed a doc rom with jl2 modern. Works awesome so far (no lagfix).
Click to expand...
Click to collapse
I know,. My first replacement shipped with JH2 and failed 5 hours after upgrading to Darky's. My second replacement shipped with JL2 but unfortunately the back button was broken. Waiting for my 3rd replacement phone to arrive - looks like Monday.
I received a jl2 phone replacement. Rooted, unlocked, flashed Darky's v8, then the jl2 modem (no lagfix). Runs great so far!
How do I tell whether my phone is at risk of this or not?
Just got a 11.10 dated brand new phone as a replacement from bell.within an hour I had it unlocked and running doc's jpy with hardcore kernel. I will use this phone the way it I bought it to use
Sent from my GT-I9000 using XDA App
Be aware though, so far I've seen two replacement phones being shipped with JK4 (one of them being my own). I updated immediately to JL2 (stock) and so far it seems fine after some stress testing.
n0th1ng said:
I received a jl2 phone replacement. Rooted, unlocked, flashed Darky's v8, then the jl2 modem (no lagfix). Runs great so far!
Click to expand...
Click to collapse
What method did you used to root it? On my JL2 z4root doesn't seem to work.
Thanks.
Kops said:
How do I tell whether my phone is at risk of this or not?
Click to expand...
Click to collapse
Do you own one of the Bell versions of the Galaxy S (i9000M)? Then you're 100% at risk. The only question appears to be when it'll fail. Who knows, maybe it'll never fail over the life of your contract.
momyc said:
What method did you used to root it? On my JL2 z4root doesn't seem to work.
Thanks.
Click to expand...
Click to collapse
Use SuperOneClick. It works for me every time z4root doesn't (and I know for certainly that it works on JL2).
I have a Samsung At&T Captivate, rooted and running 2.2 (updated via kies) and during calls people can barely hear me, and sometimes I cut out altogether. I can hear them alright... any suggestions??
mmm try a different modem?
I would first recommend flashing roms to see if it is solved.
If it still doesn't work properly then then it into at&t for a new one
Sent from my Galaxy S captivate
Maybe your microphone didn't work test out by calling *#0*#
Sent from my captivate running firefly!
I can't return it to At&t as I bought it off ebay and am using it on the Canadian Rogers Network. I don't have the original receipt for it so returning it is out of the question.
I tried the *#0*# and it didn't give me an option to test the mic...?
I'm a little unsure about flashing roms as I don't entirely understand the mechanics of it and from what I here if you don't know exactly what you're doing you shouldn't try it. Plus I've got the phone working the way I want it (all the At&t crap is deleted, all the apps I like are installed).
This is not the only problem I've been having with this phone. I've owned it since August 2010 and experienced random shutdowns two months in, as well as crappy battery life. Since Froyo there has also been a lot of lag... I don't know why. I hard reset the phone before I updated and hard reset it after I updated as to make sure I was starting with a clean slate. The sound problem has only been since Froyo, I think.
I started a thread over at Android Forums in the Samsung Captivate Forum... it's about murdering my Captivate =P
estefana said:
I can't return it to At&t as I bought it off ebay and am using it on the Canadian Rogers Network. I don't have the original receipt for it so returning it is out of the question.
I tried the *#0*# and it didn't give me an option to test the mic...?
I'm a little unsure about flashing roms as I don't entirely understand the mechanics of it and from what I here if you don't know exactly what you're doing you shouldn't try it. Plus I've got the phone working the way I want it (all the At&t crap is deleted, all the apps I like are installed).
This is not the only problem I've been having with this phone. I've owned it since August 2010 and experienced random shutdowns two months in, as well as crappy battery life. Since Froyo there has also been a lot of lag... I don't know why. I hard reset the phone before I updated and hard reset it after I updated as to make sure I was starting with a clean slate. The sound problem has only been since Froyo, I think.
I started a thread over at Android Forums in the Samsung Captivate Forum... it's about murdering my Captivate =P
Click to expand...
Click to collapse
Did you get a good price on ebay? If you did I know why, it has the shutdown issue that a lot of early Captivates had. Buying electronics off ebay is dicey at best.
Added: It probably has a modem that doesn't work good on the Rogers network. Suck it up and try flashing a new one to see if it fixes your problem. Modem Sticky
Anyone else have any other ideas about a quick fix for this problem?
So I was on atomic fusion and tried to flash another gb rom. Somewhere during the odin process it seemed to be stuck and I stopped it and tried again to get a red screen of death. I tried everything to get to d/l mode but nothing. So I called att and I have about a week left in my warranty so I went that route. Am I gonna be charged 400 dollars when they find out I was rooted with roms not theirs? I'm really nervous, I should have never flashed to gb, its to freeking complicated for me to understand all the bootloading and kernal stuff. Any thoughts or experiences to help ease the pain? Thanks
Prolly shouldn't have flashed if you weren't confident. In yourself.
Sent from my SGH-I897 using XDA Premium App
If your phone shows any signs of life they will most likely be able to tell that you are not stock.
Your fine, I did the same thing as you are doing. I just acted like a clueless idiot and they never suspected a thing, but it was with Rogers not AT&T.
Sent from my Galaxy S Firefly 3.0
For all the topics asking this question I'm yet to see anyone come back saying that they have been refused, or charged extra after a new one is already sent out. In all likely hood they don't even check because they don't really care. If it is a hardware issues they are gonna have to swap pieces or even the main/motherboard which will come with stock pre-loaded at factory. If it is software they will just use what ever method they designed into the phone to force rewrite over what was in there before.
Now if you were taking it to a service center, where they are going to take a look in hopes of getting that very phone back into a working condition then maybe... just maybe. But if the phone does not boot then they are just gonna add it to the rewrite pile and give you a referb (or new if you ask nicely enough). This is why they always say "you might lose all your data so make a backup before hand."
Thanks, that makes me feel better, now all I have to do is survive a couple days without it. I won't be making that mistake again. What did I do wrong? I had no problem going from phoenix ultimate to atomic fusion. I was gonna try to go to cog5, I thought I was doing it right. All I did was use the odin that it said to use and it seemed to be stuck. What do you do when it freezes up during the odin process? Are you screwed no matter what you do? Should I have used the odin that takes you to stock 2.1 first? I'm really trying to understand all this but there's just so many ways about everything.