I tried to search but alas Tapatalk isn't very good at that.
I bought a Captivate via eBay. Before I press to return it, is there a fix or ROM that fixes the dreaded random shutoffs? I tried resets and the GB Serenity ROM but alas I'm still encountering it...rather frequently. Every hour or less it'll shut off. So, other than the battery draining Captivate Keep Alive app...is there a real solution?
barring anything physical with your phone .. I have not had any sleep deaths or random reboots since switching to Fusion-CM-ICS-beta. It used to be a chronic issue with my phone.
Thanks for the fast reply Garyth. I'll give it a go.
I've heard the aosp roms seem to help the problem (this includes the ICS roms). They use different drivers than Samsung roms.
So far, so good. Data is consistently faster as well. Thanks again!
Hmm. Still getting random yet pervasive shut downs.
I believe this was a known hardware issue as well. There is a thread around somewhere will effected build numbers.
I saw that thread and don't believe mine is in the range. I'll be calling the seller tomorrow anyway.
Not sure if you are in the same boat as me, since the IMEI of my phone does fall into that catergory of the "recalled" phones, but since it was out of warranty by the time I saw that post, they wouldn't exchange it at the store.
At any rate, here's what I've gone thru:
Back in the Froyo times, I "think" CM7 fixed the issue, but I was too fidgety at the time so I was always trying new roms so I don't remember 100% if that was true or not.
I read somewhere that this could be caused by the battery shifting around due to temp changes as it charge/discharges, and that you should put some electrical tape or whatever to make sure your batt. made good contact. Didn't work for me at all.
So finally what fixed the problem was Captivate Keep Alive app, it's in the market.
First I tried it with two ICS roms: ICSSGS and Fusion, with Platypus and IcyGlitch kernels. The app work fine with a setting of 85%, but I was getting "charge death" as well, which I've never had before.
So now I've rolled back to KK4 (Serenity ROM) with the latest Corn kernel, and for some reason I have to set the app to 80% charge but works.
There'll be definitely an increase in battery drain, but for me it hasn't been that bad.
I used to have that problem when I first got my cappy, had froyo KB1 on it, and it would randomly shut down. Eventually when I got into hacking the android, when I finally updated to newer bootloaders, the problem went away. Though I can't recommend flashing bootloaders, since you can hard brick your phone if unsuccessful. Just saying that's what seemed to solve the problem for me.
mrhaley30705 said:
I've heard the aosp roms seem to help the problem (this includes the ICS roms). They use different drivers than Samsung roms.
Click to expand...
Click to collapse
Can anyone confirm this?
crt60 said:
I used to have that problem when I first got my cappy, had froyo KB1 on it, and it would randomly shut down. Eventually when I got into hacking the android, when I finally updated to newer bootloaders, the problem went away. Though I can't recommend flashing bootloaders, since you can hard brick your phone if unsuccessful. Just saying that's what seemed to solve the problem for me.
Click to expand...
Click to collapse
But what bootloader fix that to you?
Mine only rebooted randomly once when on eclair. Haven't had a problem in gb or ics.
Posted from my ICS'd Captivate
That would help if eclair wasn't completely useless.
Sent from my Samsung Captivate running Team ICSSGS 4.0.3
I tried Captivate Keep Alive. Even it didn't work. A replacement phone is on its way. The IMEI was actually affected, but I didn't realize at first because I only looked at the last digits. Apparently was a really early build. The seller photographed the new IMEI before shipping it out so I could verify.
I have Dark Knight's 4.0.4 ROM since 2 weeks ago.
At the moment, and I hope it remains 0 reboots.
Just wanna share with you, is up to you to try it....
http://forum.xda-developers.com/showthread.php?t=1501615
By the way, with this ROM also I got the best Quandrant Benchamark score (2400) without overcloking...
I'll keep that in mind but I got a replacement that works really well. I ended up getting it from another seller though.
Related
All, having a weird issue. I was on the phone yesterday using an automated menu system and my phone restarted. No rhyme nor reason why. It did that repeatedly throughout the day. I tried flashing a new ROM version, Phoenix 6.0!!, with no luck. I tried a normal restart, power down and then up, running a virus scan, pulling the batter for 30 minutes and no difference. The phone continued to restart. I finally got fed up and my battery was almost dead so I turned the phone off.
The phone was off for probably 5 hours and I charged it while off. I restarted the phone and transferred all of my content off, expecting to Odin back to stock and reflash Phoenix. The phone seemed to be behaving so I left it alone and plugged it into the wall for the night.
I got up this morning and everything appeared to be good. Went to work and still no problems, phone had an uptime of over 12 hours. Which would be what I would expect. Had the phone on my desk and I noticed it had restarted. When I mean it restarted, it went back to the boot animation and then loaded to the android screen and performed media scan and all my apps loaded on the home screens and services started up.
I went back to Settings->About->Status and the uptime was 18 hours now. So even with the restart, the uptime was still counting. Needless to say, I'm at a lose. Can't isolate any event that causes this reset or any app. Could I have gotten something from the automated call system? Is something just weird. I had been running Phoenix 5.2 for a few weeks with now problems so I'm confused. Any suggestions would be appreciated. I will probably flash back to stock and start again but I'd like to isolate this problem if possible.
To the best of your knowledge, no apps were just added, our settings adjusted?
Either way I would odin flash master clear. May even run stock for a but to see if behavior stops
Sent from my Captivate using XDA Premium App
sounds like a problem with the infamous 850-1900mhz handoff....
if your signature is accurate, that modem you are using is 1900mhz only i believe....it doesnt support 850, so if you are in an area where its trying to hand off to 850, it will cause a soft reboot.....i have seen it a million times myself when playing with the first run of i9000 roms
Pirateghost said:
sounds like a problem with the infamous 850-1900mhz handoff....
if your signature is accurate, that modem you are using is 1900mhz only i believe....it doesnt support 850, so if you are in an area where its trying to hand off to 850, it will cause a soft reboot.....i have seen it a million times myself when playing with the first run of i9000 roms
Click to expand...
Click to collapse
Hmmm...I have been using an i9000 roms for a few months with no issues. The last modem I was using was I9000UJK4, I think? I don't know without flashing back, whatever came with Phoenix 5.2 ROM. I had zero problems. I only flashed to that modem/ROM, Phoenix 6.0, in an attempt to fix the soft reboot.
flash just the JK4 modem and i bet the soft reboots stop. what you have listed there is i believe a 1900mhz only modem....
Pirateghost said:
flash just the JK4 modem and i bet the soft reboots stop. what you have listed there is i believe a 1900mhz only modem....
Click to expand...
Click to collapse
I will try that, when I can find it to download but the problem started with the JK4 modem. I was running Phoenix 5.2 with a JK4 modem and only flashed to the new one in an attempt to wipe whatever was causing the data.
Flashing UGJK4 right now, I'll see if that fixes anything however I'm not super confident since the problem occurred originally with a JK4 modem.
Update: Rebooted once after modem flash. Going to wait for a bit and see what happens.
if that doesnt work, i would think its a problem with your hardware
Pirateghost said:
if that doesnt work, i would think its a problem with your hardware
Click to expand...
Click to collapse
If the modem switch doesn't work, I'm first going to flash to stock and master clear. If the problem goes away, I'll flash to Phoenix again. If the problem comes back, it'll have to be part of my SW. If the problem persists at stock, back to AT&T for a refurbished phone.
Update: Looks like things are pretty stable right now. I'm not super in-tune with how the modems work but is there a way to allow the JK4 modem to use 850 or 1900 speeds, like an auto setting that will choose the best one. I use SGS tools for secret codes so if its in there let me know. So far so good, thanks pirate.
Reviving an old thread because I am also having soft reboot issues.
Unlike the previous poster, I am not using an i9000 based kernel. I am running the latest leaked Gingerbread for the i897 (JK3), rooted via Fugu kernel swap method; the only other tweak to stock has been to freeze via TiBu the AT&T Tethering Manager. I am even using the stock launcher as I try to isolate what is causing this.
The phone goes through spells where it will soft reboot every 10 minutes or less, and then periods where it will go days where it is stable. I have had this issue with multiple versions of the 2.3.3 and 2.3.5 leaks and am nearing wits end figuring out the cause.
Before each flash (and I have flashed multiple times with different stock leaks) I am wiping data and cache via recovery (I do not have CWM installed), then restoring apps only via TiBu. I have tried to be judicious about what I reinstall, but have not been able to identify if there is a misbehaving one yet.
I suspect this is software and not hardware, since I had this problem on my first Cap and have already done one warranty exchange; the external SD card, though, is the same for both.
I've looked for kernel panic logs and have not seen any, and have yet to find a good way to trap what is causing this.
This is my work issued phone (does Exchange sync and has company policies sent to it), so I am loathe to go all the way to a custom ROM, even though I realize that I voided the warranty when I rooted and went to leaked ROMs.
Anyone have an ideas as to what could be causing this, how I can isolate the problem, and hopefully resolve it once and for all? Worst case, I could go back to Froyo until AT&T finally drops the promised Gingerbread update, but I had different issues with Froyo with Market updates not always finishing and apps on the SD card not always being recognized.
My wifes captivate has the random shut down issue. Already got replacement phone and it started back up after a few weeks. If I use Odin one click to restore ucjf6 (or upgrade her phone to froyo) will this end my shutdown woes? I have been under the impression that the shutdown issue was a software problem.
I can't say I've ever heard of that happening to a stock rom (I'm guessing you never flashed any custom ROMs on to it)...
At this stage, I think it'll be better off if you take it back to AT&T as you've not really done anything to it (modding/romming wise).
Its out of warranty.she has been dealing with it by using an app from the market. I was hoping that upgrade to froyo would over write the defective software. Then I got to thinking that maybe odin would do the same thing.
The app from the market works perfectly, but it kills her battery life(it's called Captivate Keep Alive from Blue Steel).
Hmm, then yeah I suggest for you to flash her phone... Possibly to a custom ROM at this stage. Stock ROMs usually have way too much bloatware.
Also, if you can please check what version of Captivate she has... It'll be underneath where her battery is.
Usually a four digit code (1006,1007,1008,etc).
Hers is 1008.
Yeap, you should be fine to use any of these ODIN files.
2.1 - http://www.megaupload.com/?d=SBSMALFJ
2.2 - http://www.megaupload.com/?d=QL6NX702
If you need instructions, just yell again
I would probably recommend the 2.2 one (if you're not going to flash any custom ROMs).
If you are thinking of custom ROMs, then I recommend going to 2.1.
Thanks for the help. I, and my wifes battery, appreciate it.
My cappy also just randomly shuts off, but i know it isn't the battery because I've switched batteries from another cappy. I also heard there were re-calls on some cappy's as well. can it also be a hardware problem?
I have installed Firefly 3.0 on my captivate every now and then when the battery gets low to like 30% it turns off and then i gotta pop the battery out and pop it back in because it randomly shuts down. It has happened in games, phone calls from friends that are in iraq, and various other things. I just reloaded fire fly onto my phone but I am not sure whats going on with it.
After trying about everything to kill this gremlin, deleting widgets, CKA, Load Monitor, etc., I went back to JF6, charged the phone fully and let it run. The problem is still here. On the very next battrery cycle after reverting to JF6, the random shutdown occurred again while running off battery with a bone stock set-up. The battery was at about 70% when the failure occurred. (It is a new battery too.)
I bot my fone last Sept, just shy of one year ago. So today I called ATT and after a short discussion with the rep, a replacement is on the way. I described the problem and advised that one by one I had un-installed all the widgets and apps that I thought might be causing problems, then mentioned resorting to the factory reset.
A few questions followed. Then I was on hold awhile. I'm really glad I reverted to JF6 and ran the stock set-up to the fail condition. It allowed me to speak to the rep with confidence, and high hopes that they would get me an exchange. When it came time to answer questions about the Settings About details, it was all right as rain.
Now the question is will the new device have the power-off Gremlin? We shall see!
Guess I'll have some fun flashing different set-ups for these next few days 'til the replacement arrives.
Then one last flash to JF6 and back this first cappy goes...
If you are experiencing this shutdown issue, get back to stock and see if it stays. If you have had your phone less than one year, and it's dying on you, you should be able to get a refurb.
I have a general question about sleep death, is this always a hardware issue? I have recently flashed stock Gingerbread KH3 and have noticed it occuring now whereas it never happened when I was on Froyo Firefly or Gingerbread KF1. I have also switched out the battery but the issue persists. Any ideas or suggestions before I warranty it?
-it seems to occur when left idle for 3+ hours.
-it does not occur when it is plugged in to the charger.
My IMEI was not one affected by sleep death according to the AT&T press release.
Maybe it was a bad flash, try reflasing?
God luck
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I have also read on another post that this may occur when running any roms based on stock Captivate, thus I asked if this was only a hardware issue, thanks for any responses.
iphaded said:
I have a general question about sleep death, is this always a hardware issue? I have recently flashed stock Gingerbread KH3 and have noticed it occuring now whereas it never happened when I was on Froyo Firefly or Gingerbread KF1. I have also switched out the battery but the issue persists. Any ideas or suggestions before I warranty it?
-it seems to occur when left idle for 3+ hours.
-it does not occur when it is plugged in to the charger.
My IMEI was not one affected by sleep death according to the AT&T press release.
Click to expand...
Click to collapse
The random shutdown issue has been quite well documented as a hardware issue. The most common understanding is that it was caused by a problem with faulty internal memory. If that is so, it is possible to explain the various reports that the shutdown issue occurs only on certain roms, or first appears when switching to a new rom. Because different roms access memory in a different way, the new rom may have accessed an address space in memory that had not been being used by the previous rom.
That is not to say that your phone has the well documented random shutdown issue. But I was never convinced that the IMEI information in that unofficial press release thread was really useful. A better general guide was when the phone was manufactured. I think the phones manufactured after a specific date were quality controlled to not have the random shutdown issue. I don't know the date, but it was probably somewhere in November or December of last year. You could maybe find more specific info on the date by searching.
Hopefully, your phone's issue is something different, and possibly caused by software. The only way to know is to try to solve the problem with software solutions through trial and error over an extended period of time. If unable to correct the problem, then it is probably hardware related.
My first phone developed the random shutdown issue somewhere around three months after I got it. I tried solving the problem through trial and error for almost three months after that before I had it replaced by AT&T under warranty. The replacement phone I have now has been golden.
Hope this helps.
Thank you for your thorough response. I will do as you suggested and try different roms. I did purchase my phone from Ebay but did also get a Squaretrade Warranty so I hope that they honor it if it is in fact a hardware issue.
I reflashed Gingerbread KH3 and the phone would still randomly shut down.
Upon reverting back to Stock Eclair, and leaving the phone on standby overnight for the last 2 days, it has not shut down on its own.
Hi
I am new to Android world. So please handle with care
I used to use an iPhone. Recently (bout 3 weeks ago) I bought a galaxy note and am loving it.
I was going through a lot about Android system and found out 'rooting a phone'.
so I rooted the note and installed Rocket rom v22, GoLauncher Ex and few apps like Setcpu, Adfree, Bank, Xchange etc. I don't have games or many apps on my phone.
My phone turns itself off randomly every now and then. during phone conversation it rebooted itself once so far. and when my phone is stand-by, I found my phone is turned off.
I am not sure why it's happening. Is there any settings i shouldn't set?? or ???
Could anyone please tell me how to fix this issue?
If the phone is faulty, I need to make my phone as the same as when I first got which I am not sure how to :-( yet
The first thing to do is go completely stock. Flash the lastest stock rom and see if that fixes the problem.
When using ICS ROMs there's a known bug called Sleep of Death (SOD) that is similar to what you're experiencing. The phone simply won't turn on the screen and you have to press the power button for several seconds to turn it on again.
Almost all GNote users experience this issue so don't worry about it. Going back to stock will not solve the problem.
Hi
Thanks for the reply.
Before the rom v22, I had v19. my phone still did turn itself off several times. after flash the room v22, it didn't happen as many as v19 so I am not sure that the ICS causes the issue.
anyway, I will try the one you suggested and see how I go.
Thank you
kelvin fong said:
Almost all GNote users experience this issue so don't worry about it. Going back to stock will not solve the problem.
Click to expand...
Click to collapse
I am more worried about the alarm. if the phone turns itself off while i am in sleep, i won't be able to hear the alarm going off.
well if that happens again, i might have to get a alarm clock.
i was thinking of setcpu app might cause the issue... not sure though.
Thanks for your help
I experience the same issue when i was running stock. I've tried several stock versions but the problem still exists.
Sent from my GT-N7000 using XDA App
I have definitely never ever experience SOD when the phone is stock and lock.
The only time i did experience SOD is when i change to modded kernel.
I'm running stock with cf root and have never ever experienced this, so not all notes are affected. That would really suck!
Sent from my superior GT-N7000 using Tapatalk
Never had Sleep of Death on stock rom.
I am on stock ICS Rom n it has happenedwith me twice.
My GNote goes dead randomly and only starts up after pulling out battery.
Weird!
Install an ICS from Clean
Start from a Stock ICS rom using PC Odin, then follow my Post as follow :
http://forum.xda-developers.com/showpost.php?p=26772618&postcount=12
Try another rom other than that you had, or a higher versionof it.
The MIDTEAM v1.4.2 is Good and Stable.
Good Luck
I had this problem most of ICS ROMs on my Galaxy Note. SO I guess it's an ICS related bug and it is very uncomfortable to have to reset it to unlock it .
I too have tried several Stock ROMs but it still gets into the Sleep of Death at least once a day.
I guess that it should help to have a Kernel that changes the Deep Sleep settings...
Of my 2 GNotes, one of them had this problem. Happens when you put the note on the table with small drop or whatsoever.
The problem disappeared when inserted 3-fold 80g paper between battery and the edge of battery compartment. The battery tolerance is not so tight so when small drop (like putting on the windowsill) happens, the phone shut down.
The problem completely disappeared after inserting paper.
Of course, more professional would be go to Samsung repairs and show it and ask for replacement - either battery or phone internal casing. You can reproduce the problem by turning the screen on and dropping phone 10cm into hard surface.
But I did not bother.
I won't say that yours has exactly the same problem. But check the tolerances of battery 1st. Sometimes solutions are too obvious to see 'em.
I upgraded from stock to CM9 3 days ago and my Note has turned off several times a day since then. Never before upgrade, so I don't think it has to do with battery being loose in its compartment - not in my case.
I am loving ICS, but I will have to downgrade to gingerbread to get rid of this irritating bug.
this is happening to my galaxy nexus!!! yeah it turns off at random like sleep of death and small drops can trigger it. if i knew this could happen i would have never rooted
lol root itself has nothing to do with it.
if small drops cause it, and paper adding in compartment fixes it. its the gap between battery and whatever should fixate it.
if it occurs during deep sleep, dig into logs what you can find there. Also check roms/kernels feedback if others have it with that version. Many ways to illiminate possibilities.
I miss some good analyzes in this is issue from those experiencing stuff. Android I guess is not user friendly that way.
Sent from my GT-N7000 using Tapatalk 2
Galaxy Note Sleep of Death on 4.1.2 JB
I'm still trying to figure this out... I had hoped that with Samsung Stock upgrade to 4.1.2 it would be fixed but its not... anybody still experiencing this problem?
Things that I have tried
Move all apps from Internal SD Card (USB) and format
Factory Reset
Paper wedge between battery
Opened and re-connected all connectors to Motherboard
Install CPUSpy (deep sleep is OK)
I'm at wits end now, and this problem is very apparent. I havn't wanted to flash to a custom rom, because I've seen reported that it still happens with whatever ROM whether stock or custom
Any more ideas on how to make the Sleep of Death go away?
rasielbz said:
I'm still trying to figure this out... I had hoped that with Samsung Stock upgrade to 4.1.2 it would be fixed but its not... anybody still experiencing this problem?
Things that I have tried
Move all apps from Internal SD Card (USB) and format
Factory Reset
Paper wedge between battery
Opened and re-connected all connectors to Motherboard
Install CPUSpy (deep sleep is OK)
I'm at wits end now, and this problem is very apparent. I havn't wanted to flash to a custom rom, because I've seen reported that it still happens with whatever ROM whether stock or custom
Any more ideas on how to make the Sleep of Death go away?
Click to expand...
Click to collapse
What is the status of your phone now :
Working or not?
It works then it turns off by itself
Bootloop
Stuck on the white Samsung logo
Completely Off?
It does work but it turns itself of, the longest its gone without restarting is 44 hrs. I contacted Amazon where I bought and they are offering s full refund, so I , might send it back but I love it and had wanted tho keep it if the problem is fixed.
Sent from my GT-N7000 using xda app-developers app
Turning off problem too
I don't know if it is exactly the same problem, but my GNote keeps turning off every time, but not seem to be randomly. Looks like ti shut down every time a high performance is required. I tested several roms, ICS and JB, custom and stock, but the problem still goes on.
Please, any ideas?
This seems to be happening with every ics rom I flash. I first flashed ics to my phone when it first started to be ported to the Captivate.
My phone has suddenly started rebooting every so often (every 20-30 minutes.) My phone usually does this when it gets to about 60% battery. I have already tried calibrating the battery and using a different battery. Neither method has worked. Is anyone else having this issue or know how to solve it?
EDIT: meant to say shutting down not rebooting. Also it doesn't shut down on me while I use it, only when I set the phone down and the screen turns off.
Sent from my SGH-I897 using XDA
That's generally hard to troubleshoot, but the first step I would take in this situation would be to bump up the lower frequency voltages. Of course you'd need a different kernel to do that. Try Glitch or Semaphore if you want. If you've never played with that stuff before, there is some necessary reading involved before you can know what to do.
This has been an on-going problem with Samsung Captivates, ive had that issue, Ive tried all the above. Including all the ROMs on xDA, and also different methods of flashing. And ive had no luck either. I went back to GB. If u do find a fix, let me know.
In my opinion, i think its our phones, some can handle it, and unlucky ones cant. Sucks.
same issue with me. the last four digits of my IMEI are below the cutoff point of phones who would eventually have the issue.
Every single ICS rom shuts off my phone randomly. ever since I went back to GB, it has been running fine. tried a bunch of stuff to, but nothing works.