Related
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.
Why my LG Optimus 2X freezes and/or reboot?
Most of us have the same problem, we are trying to find a solution. In the meanwhile we can solve only removing battery.
Is it related to baseband version?
It does not seem related to baseband version. The problem is present in last baseband versione too:
1035.21_210110405
FRG83G
V10b
Is it related to ROM Version?
Apparently it happens on both stock and custom ROMS
I read that it is due to wall charger problem
Some of us have the same problem recharging both from USB PC and Wall Charger
I read this is due to overheat problem
Some of us still have the problem in standby mode with battery under 25° C.
LG told me to ask for a replacement
Some of us did it and had the same issue on the replaced phone.
I read it is due to hidden menu/car navigation/ecc. ecc.
There are no prooves about it.
Could it be a ROOT problem?
No. Same thing happens on both rooted and original phones.
I got it. It's a SD problem
Some of us has this problem both with or without SD card
So it's a HW problem
We are not sure about it. Most of us (me too) think this is a SW related issue. Some other thinks about a HW one.
Anyway it looks like a Nvidia/Tegra related problem.
It happens on Motorola Atrix too:
http://forum.xda-developers.com/showthread.php?t=969974
http://forum.xda-developers.com/showthread.php?t=1009510
So: what can I do?
Follow this thread and partecipate
Try to install latest version v10b and do a full reset.
Try to uninstall the "Any cut" application.
Try removing your SD.
NOTE: These are temporary solutions while we wait to understand something more.
Nothing else?
Sure, you can add informations here to keep updated the FAQs.
What about contacting LG?
It looks like something is moving and a new update will be released soon:
http://translate.google.com/transla...alligevel-problemer-med-optimus-2x,lid.15324/
Hey, new V10C is available. Does this solve?
Not sure yet. Some of us still have problems, but some others solved with this upgrade.
How can I help?
You can sign this petition on line
http://www.petitiononline.com/LGO2XPrb/petition.html
Last updated: Tue 7th July 2011
Mine has now shut down 3 times while i was in a call, battery pull on each occasion to rectify the problem
Added in the first question that pulling off the battery temporary solves.
1 week ago I do faced 2 time reboot each after receive sms during standby mood.
Dont know what happen.
Later I remember the reboot problem started after I had installed "Any cut" sw and started to activate the hidden menu.
Then I uninstall it and now haven facing any reboot no more.
Already 1 week pass and no reboot at all. I also never restart my O2X yet and seem everything is OK, no lag or etc on the system.
Hope this help.
Was using the original lg rom only for a good day and had one shutdown. Switched to custom rom and didnt have a reboot or shutdown yet in over a week. Appears to be software related.
Sent from my LG-P990 using XDA App
Useful topic, thanks!
My experience in 15 days of use.
with stock rom V10a and external sd:
- 1 time screen locked black in a warm day during standby
with stock rom V10a without external sd:
- many times screen locked black just after a notification (almost always after sms incoming notification)
with official rom V10b without hard reset and without external sd:
- 1 time reboot after pressing power button to exit from standby
- 2 times screen locked black the day after I've changed the useragent setting from the hiddenmenu and installed "AutomateIt" app
with official rom V10b after a hard reset 2 days ago and without external sd:
- no problem till now (2 days of use)
All the time I used both original charger (at home) and a generic usb adapter with an output current of 1mA (at office).
This is the sort of stuff that should be sent to LG to deal with. Not the idiots at call centres but the people who made the phone and get them to work on it.
Problem with these phone guys, they make a phone and then just stick out to the salesman and then when things like this happen to everyone we get no support or real contact.
It's always send it for repair. The phones are like a month old and that is really a valid response?
Time LG were held accountable (as well as other company's)
Ok, added some "Possible solutions"
Good thread, will hopefully cut down on some of the idle speculation that has been going on!
I believe that it is a software bug, namely in Nvidia's cpufreq-dvfsd driver. I saw this process misbehaving when doing a 'top' command via an ADB shell after it froze, and I'm not the only person to have witnessed that. I've posted that info over at MoDaCo.
As kholk is the only person other than Paul I know around here who might be familiar with a Linux kernel, I've asked him to take a look. Not sure what will come of that, if anything.
And just to add fuel to my argument that this is a Tegra/Nvidia issue, and *not* necessarily an LG one, check this out (from Moto Atrix forums):
http://forum.xda-developers.com/showthread.php?t=969974
http://forum.xda-developers.com/showthread.php?t=1009510
Read from the postings that, for charger-specific reboot/lockup problem, it might be better charging from a computer USB port or a charger with lower current output (I think someone is using as low as 350mA).
Fyi, I've never had AnyCut installed and I've had these problems.
Yup, we do not have still found THE cause, but some events.
We are trying to understand if they are related to the issue.
I am reporting infos from the other thread and from this one to help people ti find a partial solution.
Very interesting withoutwings
A problem related to tegra system could explain why LG can't solve anything?
Checking all of the messages I can see that the problem is one ( phone locking/restart) but the symptoms are very different and almost always unrepeatable.
Is also strange that many people have a lot of apparently casual restart/lock and many other people have no problems. If a part of source code is corrupted I think the problem should occurs for all the phone.
follo said:
Very interesting withoutwings
A problem related to tegra system could explain why LG can't solve anything?
Checking all of the messages I can see that the problem is one ( phone locking/restart) but the symptoms are very different and almost always unrepeatable.
Is also strange that many people have a lot of apparently casual restart/lock and many other people have no problems. If a part of source code is corrupted I think the problem should occurs for all the phone.
Click to expand...
Click to collapse
Not necessarily. In embedded/real-time systems, timing is crucial and in some components varies according to manufacture tolerances, heat, etc. Also everybody's phone has different apps and they do things at different times so you can't say that everybody's phone is just "the same" as everyone else's.
And this bug could well be one that only happens for some very specific condition that the original developer didn't forsee when he wrote that code or tested it. But the law of chance means that so many of us are seeing it - some more than others, and some days worse than other days.
So this would explain why people think that doing something like switching launcher or taking out an SD card might be solving or making the problem worse, because every action can and does change the likelihood of this specific condition occurring by changing how the phone behaves overall, workload, sleep time, etc etc. And why all these "solutions" that people are posting are so random and unrelated but each person is convinced that theirs is the one that works!
Basically, we need more evidence from logs to see what is really going on...
LG Denmark has just announced that they have acknowledged the problems and found a fix for it - they are currently sending out an update to correct it as we speak
Should be available OTA soon (how soon depends on each carrier)
http://www.mobilsiden.dk/nyheder/lg-alligevel-problemer-med-optimus-2x,lid.15324/
mikeyd85 said:
Fyi, I've never had AnyCut installed and I've had these problems.
Click to expand...
Click to collapse
Im not an expert, but its work for me. I will keep you all updated if reboot happen again.
Edit: just having my FB hang in 15 second and force to close. This definately due to sw problem.
Sent from my LG-P990 using XDA App
i will believe only when i will see one
spawndk said:
LG Denmark has just announced that they have acknowledged the problems and found a fix for it - they are currently sending out an update to correct it as we speak
Should be available OTA soon (how soon depends on each carrier)
http://www.mobilsiden.dk/nyheder/lg-alligevel-problemer-med-optimus-2x,lid.15324/
Click to expand...
Click to collapse
they said that gingerbread update will be on 18 april to and didnt
They said jun/jul. Check out dk site.
lmerega said:
They said jun/jul. Check out dk site.
Click to expand...
Click to collapse
Well thats the most realistic schedule
I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...
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.
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?