I exchanged a phone today because of random shut downs. The service center originally tried to give me a build 1008 phone, which is the same build I had with random shutdowns and lost 3 button recovery. I raised a stink and they gave me a 1009 build.
Is there a catalog of issues by build? If I use Odin, will I loose 4 button recovery? Is random shut downs an issue with this build? GPS?
Is there anything I should know or watch out for before flasjing roms and rooting this phone?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
got a 1009er with GPS issues and shutdowns
-since i insert a 1650mh batt from the I9010 no more shutdowns
-back to stock via Odin and JF6 Final and download mode via volup,down at the same time then insert usb cable, no problem at all.
just my 2c
cdwhit said:
I exchanged a phone today because of random shut downs. The service center originally tried to give me a build 1008 phone, which is the same build I had with random shutdowns and lost 3 button recovery. I raised a stink and they gave me a 1009 build.
Is there a catalog of issues by build? If I use Odin, will I loose 4 button recovery? Is random shut downs an issue with this build? GPS?
Is there anything I should know or watch out for before flasjing roms and rooting this phone?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I read in the Vibrant forum that number isn't a build number... its the build month and year in Europeen format, so your first phone was made in 8/10. Your new phone was made in 9/10. I know that it does hold true for my wife 2 Captivates (exchanged 1010 for shutdowns), as well as mine.
That being said, the memo warns about all phones prior to 11/6/10. If this is a build month, then I would insist on a 1011 or higher.
When I exchanged my wife's phones (within 30 day period) I looked up the build date on Samsung's website based in the imei number on the phone box without even opening it before accepting it. You could do this to to be real sure it is built after 11/6. They're knowingly selling defective phones, so don't feel bad insisting on whatever it takes to make you feel whole.
Her new phone is 1012 - built on 12/25/10. No shutdowns yet and the GPS works well - even better than her 1010. I'm jealous of hers. Mine works ok, but randomly losses itself for 10-30 seconds while driving.
Both of our phones are stock and unrooted.
Sent from my SAMSUNG-SGH-I897 using XDA App
Natascha303 said:
got a 1009er with GPS issues and shutdowns
-since i insert a 1650mh batt from the I9010 no more shutdowns
-back to stock via Odin and JF6 Final and download mode via volup,down at the same time then insert usb cable, no problem at all.
just my 2c
Click to expand...
Click to collapse
I have 1009 build and so far I don't have any problem.
Related
I was having problems with every custom ROM on my captivate randomly shutting down, I had to use Captivate Keepalive to keep it running. I was using AXURA before, then a friend referred me to PR 3.5 and I switched. My shutdowns actually increased! I was thinking that I was going to have to go back to vanilla when I saw a post mentioning similar problems, and though that it might help me too. I installed the kernel, and I haven't had a shutdown in 4 days so far! So for me, Phoenix Rising 3.5 + Glitterballs' kernel is rock-solid.
I was pointed Here.
As strange as it sounds different kernels give me different results too. Some make my phone do Random Shutdowns and others are stable as can be.
I noticed that to, different rom/kernels would effect random shutdowns it seems. Then I spent 10 minutes on the phone with att (literally 10 minutes) and they sent me a new phone next day for $2 and I can run anything I want with zero shutdowns.
Sent from my SAMSUNG-SGH-I897
Then this and the fact that AT&T are replacing certain build and batch of phone with the shut down issue seems to point to bad RAMs. With different ROMs and Kernals, managing different apps and services and loading different parts of kernel and page swap of the RAM probably caused the shutdown. Sort of like the BSOD for windows when things go wrong with stuff in the memory. So it sounds like the AT&T shut down replacement are replacing a bad batch of RAMs. Just a thought.
overkillthemighty said:
I was having problems with every custom ROM on my captivate randomly shutting down, I had to use Captivate Keepalive to keep it running. I was using AXURA before, then a friend referred me to PR 3.5 and I switched. My shutdowns actually increased! I was thinking that I was going to have to go back to vanilla when I saw a post mentioning similar problems, and though that it might help me too. I installed the kernel, and I haven't had a shutdown in 4 days so far! So for me, Phoenix Rising 3.5 + Glitterballs' kernel is rock-solid.
I was pointed Here.
Click to expand...
Click to collapse
The official fix is sending it in to Samsung and having them replace the TIB board on your Captivate. Flashing various ROMs is YMMV and definitely not a real fix.
I cant bare this any more
my phone shut down randomly at least 3 times a day. I almost missed my class today. I am not charging it, battery is 60% full. fu-ck Samsung and att.
pobinghun said:
my phone shut down randomly at least 3 times a day. I almost missed my class today. I am not charging it, battery is 60% full. fu-ck Samsung and att.
Click to expand...
Click to collapse
Speedmod K12O kernel works wonders! No more shutdowns!
alled samsung today and requested manager, this did not help. I asked about random shut downs and was told they know nothing about this issue.
I was asked to send in phone to be be checked but told these ingnorant people that this will not work. Who is going to pay for service which i am not using during downtime. Class Action , this is what we need.
a2gtinut said:
alled samsung today and requested manager, this did not help. I asked about random shut downs and was told they know nothing about this issue.
I was asked to send in phone to be be checked but told these ingnorant people that this will not work. Who is going to pay for service which i am not using during downtime. Class Action , this is what we need.
Click to expand...
Click to collapse
it amazes me that there isn't already a class action law suit against Samsung.. I don't understand how they can keep producing all these phones with faulty hardware.. first there was the GPS not working then the Vibrants on Bell had faulty RAM.. now the Captivates are randomly shutting down and even the Nexus S has random reboots.. is it too much to ask to make a phone that actually works as expected?
My Captivate's random shut down "sleep of death" also disappeared.
There is no shut down with GB kernels (12.28 or 01.04 #47 kernel)
and there was also no automatic shutdown with Speedmod K12 kernels (500MHz)
I was on Darky's 7xx nd 8x ROMS.
I'm using Hamsters 6.3 ROM with Speedmod K12O 500MHz Warm kernel and ZMKP1 modem. There is no shutdows so far. Battery life is excellent.
I must have missed this thread earlier when I posted elsewhere, but I also found that Phoenix 3.0 seems to have fixed my issues.
pezx44 said:
I must have missed this thread earlier when I posted elsewhere, but I also found that Phoenix 3.0 seems to have fixed my issues.
Click to expand...
Click to collapse
I am wondering, would it resolve random shutdowns? Currently im using FF3.0, have random shutdowns.
Only true resolution is to get replacement from Samsung/Att
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
mpencexda said:
Only true resolution is to get replacement from Samsung/Att
Click to expand...
Click to collapse
Yep. My third phone has been shutdown free for over 2 months.
I downloaded load monitor and it hasnt shut down in 5 months, I was shutting down 20 times a day before i downloaded it.
what is monitor can you explaint me i have same shutting down 20 times a day only on miui i don't have such problem
Heyy everybody let's see which build everyone has!
(If you don't know what a build number is look at the sticker, on your phone, under the battery. It starts like this "10XX")
Let me start
I have a build 1008 Captivate
Cons: No three button fix after rom flashing.
(Make sure u flash a Rom with the three button fix, or just flash the fix!! Or have a jig on the side just in case )
1008 but no button combo problem. Jig on the side just in case
MIUI
I had a 1006, but then samsung swapped the motherboard after mine died. Now I have a body that says 1006 and who knows what on the inside.
1008 too.
Rocking CM7.
Sent from my SGH-I897 using XDA Premium App
Had a 1010, but had random shutdowns... ATT replaced it with 1007, everything works.
Looks like voting is all screwed up...
1007 here.
There's no 1013. Only 12 months in a year. The newer builds are 1101, 1102 and so on.
1007, and I have no standard Captivate problems whatsoever.
CM7 Inspire 4G
Just got a 1102 today, warranty exchanged my 1008 for unreliable GPS.
I have a 1007 that I got right when they released and another 1007 still new in the box I got on black friday last year when radio shack had them for free with a new two year agreement.
Sent from my phoenix ultimate js7, firebird 2 v1.0 powered SGH-I897 using XDA Premium App
Build number 1007 and everything works perfectly on it except gps of course...
1008 here. Three-button salute worked for me out of the box (JH7), but after I wrecked my phone and did the Odin one-click back to a slightly older stock firmware, my recovery mode went bye-bye. Ended up needing to borrow a Window's laptop (I have an old Mac) and installing the SDK to adb it into recovery mode before I could trick it out again.
My captivate works fine when running a non rooted stock rom, but as soon as I root it and load my apps it starts to get random shutdowns, so it's not overclocking or undervolting. I'm on darky's right now, and I am getting several shutdowns a day. I tried un installing multiple apps with root access to no avail.. Is it possible for a non root app to cause shut downs? I sent my phone in and it was sent back just fine because it was on stock eclair. I don't want to have to trade it in for an iphone but if it continues to shut down I will. Is there any way to diagnose the problem, or even fix it? I think it is an app issue.
Sent from my SAMSUNG-SGH-I897 using XDA App
Did you try a different kernel? All phones react different, I can't currently use i9000 roms. Worth a shot.
Caution swyping! Read at your own risk.
I tried Darky's and I got the same thing. I have switched to FireFly and have had no problems at all. Paragon is a good ROM as well.
I had the same problem but I would only have the majority of my shut downs within the first 10% of my battery after a full charge. After that for the most part, it would be just fine after that. I'm using cog 4.1 and have been for the last few months and I can count on 1 hand the number of times it shut off. I found that after a full charge,immediately after taking it off the charger, reboot the phone and it runs all day with no problem since I started doing that.
Sent from my SAMSUNG-SGH-I897 using XDA App
My best guess is that the officially confirmed bad ram problem is to blame. the rooted apps might be accessing bad sections of the ram and causing crashes. It makes sense that the frequency changes depending on which rom you are using since they all handle ram management differently
Sent from my SAMSUNG-SGH-I897 using XDA App
See I would think it was my kernel or rom if it didnt happen on stock eclair. It happens at any battery percentage.. I really don't know what to do. I might be able to trade it for an Iphone 3gs.. I really want to keep the phone but it seems like I might be stuck with a permanently shutting down phone.. which I can't keep.
How long have you had it? I just returned mine for a new/refurbed one a few days ago. I bought mine in Oct. I'm lucky enough to have a ATT service store near me. Went in, told them I had the shut down problem. Swapped phones and out the door. They are honoring the 1yr replacement from Samsung. Got a 1009 that has perfect GPS, for now, haha.
I got mine refurb, and sent it in to samsung, no go. Do you think an att store in a mall would honor the one year?
Sent from my SAMSUNG-SGH-I897 using XDA App
Since yours was refurbed, I think the warranty is limited by everyone to 30 days. Mine was new. One of the few perks to NOT getting a refurb.
I had same problem running seremdipity . Now i run continue and no more shut downs. I guess u should try other Rom like mentioned before
Sent from my GT-I9000 using XDA App
Give AT&T a call via 611 or their 800 number. I think the refurb policy is actually 90 days, but from my experience, if you complain hard enough and be rational and reasonable about your requests, they usually budge. I had the same shut down problem with my captivate. First thing they did was send me a new battery in case that was the problem, didn't have to return my original battery so I now have 2. Then after another call back, they told me to go to the service center and I swapped it out in under 3 minutes no problem. Just make sure to Odin to stock before returning your phone.
install setcpu app and set your min clock to 200 that helped some people with shutdown issues
I updated my phone (flashed stock 2.2 rom, flashed stock recovery, then used LG updater tool, then ran recovery after flashing) to 2.3 on the day v21e was released and from the day after flashing I am still having to do battery pulls as the phone locks while in standby. Am I the only one having this issue or are there others as well? hopefully the official release doesn't have this problem.
Znsale01 said:
I updated my phone (flashed stock 2.2 rom, flashed stock recovery, then used LG updater tool, then ran recovery after flashing) to 2.3 on the day v21e was released and from the day after flashing I am still having to do battery pulls as the phone locks while in standby. Am I the only one having this issue or are there others as well? hopefully the official release doesn't have this problem.
Click to expand...
Click to collapse
I've had lockups since day 1... It's gets me so mad. I have a replacement coming in a few days. I've tried everything... Rooting, unrooting, and the 2.3.3 update didn't fix anything! But one thing which was weird, is that 2 days ago, when I was at Oceanport, NJ Warped Tour, my phone was in my bag. It was about 98 degrees outside, and my phone was really hot... It managed to stay on the entire time... WHICH WAS WEIRD! But I hope my replacement doesn't have an problems.
My dad has a G2X with NO PROBLEM AT ALL. Absolutely NO screenbleeding whatsoever! and he's NEVER had a lockup/reboot!
7/29 EDIT: I received my replacement G2X in the mail yesterday, and it appears that all of my issues are gone!
I think I'm going to wait until the upgraded ones come out and try to do a return for the newest ones.
I am having the same problem. I got a new g2x about 2 months ago. it was perfect. lost it. got a replacement and have had the same issue you are having. after update i still have the same issue. i just leave it on the charger. i set it to not sleep while charging and it will not shut down. as soon as it is unplugged it will shut down.
I had to wipe my phone and factory reset to make run as it should after to the update
Sent from my LG-P999 using XDA App
skye206 said:
I had to wipe my phone and factory reset to make run as it should after to the update
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I did that as well, twice actually, but that didn't fix the issue.
I'm trying an experiment by uninstalling setcpu and juicedefender and just letting the kernel manage my cpu. I expect less overall battery life, but I'm hoping that by eliminating the screen-off profile and constant radio on/off, maybe...just MAYBE it might help with my sleep of death, freezes, and random reboots.
I have sinced changed where screen wont timeout for thirty minutes I did two factory resets since update and still does not work time to return or change the rom.
Sent from my LG-P999 using XDA App
I had very few random reboot issues before the GB update. Maybe 4 or 5 in the months that I've owned the G2x.
Since the GB update I've had several each day. I've hopped around onto various ROMs to see if one would correct the issue and to date, none have. I'm considering restoring my Froyo nandroid to see if that gets my stability back.
Tmo is sending new replacement. Finally got tired of attempts to fix.
Sent from my LG-P999 using XDA App
jimcarroll said:
Tmo is sending new replacement. Finally got tired of attempts to fix.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
You had a defective unit, software wouldn't fix it. If it was a "kernel" issue. One of the custom kernels on XDA should've fixed it.
My g2x froze all the time while idle. I read a thread once that claimed upping the minimum CPU clockspeed to 312MHz fixed the problem, so I used SetCPU to increase it and it stopped freezing after that. Reboots were another issue though...
I've had with my Crappy. This back/home button flashing thing makes my phone totally unusable. Doesn't matter what rom/kernel I run, same thing.
Anyone found the cause or fix for this? The rice trick doesn't do squat and it's not moisture, my phone is dryer than a popcorn fart.
Seriously about to throw this thing into a volcano.
No longer sent from my BlackBerry.
I had that happen when I first got my captivate. AT&T pushed some 9-12 meg file to my phone and it quit doing it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hmm, that doesn't help me unless I revert to stock. Yuck?
I'm taking it into Target for the $5 upgrade to a S2.
No longer sent from my BlackBerry.
Never had any problems with the soft keys. I love my CAPPY.
Sent from my SAMSUNG-SGH-I897 using XDA App
I remember reports of random automatic button presses from a year or so ago. Seems to have gotten better with the new ones, similar to the sleep death. I had random search boutin presses until I warrantied mine due to sleep death.
What's the date code on yours?
Sent from my SGH-I896 using XDA App
How do I get the date code?
No longer sent from my BlackBerry.
Should be a 4 digit number under your battery, something like 1010, two digits are the month, two are the year.
I forget which order it goes in but it should be evident. I know the sleep death problem was fixed in models built after early Nov '10, and the button problem might be the same.
Sent from my SGH-I897 using XDA App
Have you tried to remap or disable these two keys? For example you can disable home and back, and map the search key to back.
http://forum.xda-developers.com/showthread.php?t=1298820
Sent from my SGH-I897 using XDA App
mechanical tool said:
Should be a 4 digit number under your battery, something like 1010, two digits are the month, two are the year.
I forget which order it goes in but it should be evident. I know the sleep death problem was fixed in models built after early Nov '10, and the button problem might be the same.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
First two digits are year, second two digits are month. So 1007 = July 2010, 1101 = January 2011, etc.
My phone is 1011 so November, 2010. It's so bad that I can't even dial a number. Running Andromeda³ and Ursa Minor².
No longer sent from my BlackBerry.
Captain Zero said:
My phone is 1011 so November, 2010. It's so bad that I can't even dial a number. Running Andromeda³ and Ursa Minor².
No longer sent from my BlackBerry.
Click to expand...
Click to collapse
I had this problem really often when I had Andromeda3 loaded, care to try a newer GB ROM, or CM7.1 and post results? Oh and do you also get random shutdowns?
No random shutdowns, ever. I may try cym but I'll probably just trade in the cappy for a sg2 since I'm pretty well fed up with the captivate. I've tried many roms and it didn't seem to matter. My only "guess" is that it has to do with the blk mod that's pre-loaded with most roms.
No longer sent from my BlackBerry.
Found a fix; picked up a SGS2. Problem solved.
No longer sent from my BlackBerry.
I had the same problem with my cativate with every rom i installed my home button would go crazy. i flashed back to stock many times but it didnt fix the problem until one day I flashed back to stock and then let kies update to froyo and bam problem fixed. Never had another problem again with my soft buttons.