Related
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on. I don't know if it is Cyanogen or some sort of app, as I download apps quiet frequently. I am going to go through my apps now and also reinstall Cyanogen 3.4 tonight and leave my phone on all night. I guess I will have to see in the morning..
Anyways, can someone help
I ve fot sometimes the same issue with dudes cupcake which use th cygnonen kernel...
I ll be glad to have a fix
Are you overclocking the processor? That might contribute to it shutting down.
I do overclock but why do i have to 'battery pull' to make it reboot?
Yes, same issue here.
Uhh, again...
Powered up, set to standby, waited 1 min, shut down.
EDIT: I'm on Rogers Cyanigenized.
Same issue here. Complete lockup with screen off, have to pull battery to boot again. Seems to happen every 6-12 hours for me.
My Phone:
Cyanogen 3.4
radio 2.22.19.26I
Haykuro's SPL
Kernel 2.6.27.24-cm by [email protected] )
NOT overclocked, and no clocking tools even installed. Persists after several clean wipe and reflash also.
This thread's timing is great... I was just about to reset back to rc29 and build back up. Thought I was going to have to replace my phone
Rastasia said:
I do overclock but why do i have to 'battery pull' to make it reboot?
Click to expand...
Click to collapse
This question should probably be in the Dream section and will probably get locked/moved but Pulling the battery reset the "overclock" until it boots back up. This would be why pulling the battery helps.
hey you don't havbe to pull battery just push end call start call and menu all at once it will reboot you phone
Ok, thanks to Jakob, we know, that android freezes, is doesn't shut down.
I now tested with and without overclock, it made no matter to me not to overclock, there's no difference.
But I experienced it didn't happen when it's connected to a charger..
mysterious..
This keeps hapening to me, first it was happening in Cyanogized Rogers rom, then in The Dudes 1.3 b 12, I'm flashing JAC1.62 right now, this never happened to me before I got my class 6 16gb and started using apps2sd
Just curious, does this happen to anyone without a2sd
i'm having the same problem
seems to happen in the builds using the Cyanogen kernel. I'm sure this issue will iron itself out in future releases so just sit tight.
I too am having the problem on the Cyanogen 3.4 build. Its definately a change in 3.4 as I didn't have this problem in any of the 3.3 betas. I'm doing Apps2SD as well.
One thing I have noticed as well is that networking has been acting flakier than normal.
I had this issue on the pre-cupcake radio but not as frequent, so maybe it's just an amplified version of the same problem? There was a thread about it before but I'm too lazy to search for it.
The hangs was the only reason I moved to virtududes rogers rom v3
I'm going to try and get this sorted out tomorrow. For some reason the OOM killer kicks in sometimes and kills a critical process like zygote.
atleast you don't have this problem!
I've reflashed,wiped,formatted and apps2sd2 or sdpsplit, so many times already... trying different ways for each. But same thing always happens... my memory card gets damaged then wiped all by itself.
Uninstall toggle Setting and use Reparing Ext partition with Cyonagen recovery seems to fix this issue
So happy I found this thread! I'm using Google Ion and having this issue since yesterday. So annoying. Anyone got a fix?
I`m having the same problem, the phone freeze, looks like is a hardware problem, i`m on CRC1
I have started to have this issue as well. I am currently running Cyan4.1.999. It happened yesterday while on a call, after a call, and also while the phone was on charge.
Solutions?
Something weird is happening to my Captivate.
I flashed updated from Apex 9 to 9.1 with a full wipe on Tuesday I think. After that, when my phone is just sitting there and the screen goes to sleep everything is fine, but if I leave it sleeping a long time, say 30 minutes give or take, when I try to wake it up, the soft keys light up, but the screen won't wake, I can't do anything but remove the battery to reset the phone. Today I flashed newe ROM (Sensation), New Kernel (Talon 4.3 - 1200) and new Modem (JW2). Went to the kitchen to get a bowl of cereal, I saw the softkeys on (was chatting with my wifey) and tried to wake it up, same thing.
Anyone going through something even near as weird?
I'm thinking it can be the lockscreen, honestly haven't tried, but just changed it to MIUI to see. If it does it again, I will try waking it up and sliding the lockscreen in the dark. Will keep you guys posted.
If anyone has a solution or knows what the issue might be, I will be very grateful, still saving for the SGSII.
vette95 said:
Something weird is happening to my Captivate.
I flashed updated from Apex 9 to 9.1 with a full wipe on Tuesday I think. After that, when my phone is just sitting there and the screen goes to sleep everything is fine, but if I leave it sleeping a long time, say 30 minutes give or take, when I try to wake it up, the soft keys light up, but the screen won't wake, I can't do anything but remove the battery to reset the phone. Today I flashed newe ROM (Sensation), New Kernel (Talon 4.3 - 1200) and new Modem (JW2). Went to the kitchen to get a bowl of cereal, I saw the softkeys on (was chatting with my wifey) and tried to wake it up, same thing.
Anyone going through something even near as weird?
I'm thinking it can be the lockscreen, honestly haven't tried, but just changed it to MIUI to see. If it does it again, I will try waking it up and sliding the lockscreen in the dark. Will keep you guys posted.
If anyone has a solution or knows what the issue might be, I will be very grateful, still saving for the SGSII.
Click to expand...
Click to collapse
are you Overclocking or Undervolting. That could be the problem, happened to me once. try higher voltage or wipe voltage settings in recovery.
kant5t1km3 said:
are you Overclocking or Undervolting. That could be the problem, happened to me once. try higher voltage or wipe voltage settings in recovery.
Click to expand...
Click to collapse
Nope, have it at default speed and voltage.
I will still try wiping the voltage settings, because I remember OC/UV when running Apex 9.0
BRB, let me try...
Ok, just did, I'll let it rest there for about an hour...
Will keep you posted.
just a though but also try wiping data/cache/dalvik
kant5t1km3 said:
just a though but also try wiping data/cache/dalvik
Click to expand...
Click to collapse
Yeah, I wipe everything before flashing always, the only thing I never wiped was the voltage settings, it just might do the trick.
vette95 said:
Yeah, I wipe everything before flashing always, the only thing I never wiped was the voltage settings, it just might do the trick.
Click to expand...
Click to collapse
ok... keep me posted
Having the same problem from time to time
i was once told that keeping pressing the soft key would wake the screen up when power key couldnt work
that method sometimes does work for me
however,mostly,it makes no sense 8
regards
It stopped doing it.....
It hasn't happened anymore since I wiped the voltage settings. But now, every now and then it just like soft reboots, it's weird. I hear the boot sound all of a sudden without any apparent reason.
New challenge.
Well, went back to APEX 9.1, hopefully this will solve the soft-reset issues I was having.
vette95 said:
It hasn't happened anymore since I wiped the voltage settings. But now, every now and then it just like soft reboots, it's weird. I hear the boot sound all of a sudden without any apparent reason.
New challenge.
Click to expand...
Click to collapse
Same thing happened to me on dlevs rom. I thought it was a processor not getting enough power thing so I just let it go. (I do extreme under volting
Sent from a phone controlling a computer controlling a different phone
sepherian said:
Same thing happened to me on dlevs rom. I thought it was a processor not getting enough power thing so I just let it go. (I do extreme under volting
Sent from a phone controlling a computer controlling a different phone
Click to expand...
Click to collapse
Under volting the processor on these phone will help you very little as far as battery life goes. The screen is what drains the battery like crazy. Your probably causing more harm by extreme under volting.
This is what one of my friends captivates kept doing on the stock froyo rom and the only fix that I found was flashing a different 2.2 rom over it.
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?
I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.
stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues
Hi Guys,
I have a serious problem with my Inc S. Lately, after using a few apps (mainly on the bus) the phone will go to the lock screen. A this point when the power button to wake the phone, it will just hang. The backlights will still be on but the phone is unresponsive. I have pull the battery out for 10-15 mins before it will restart. This issue happens at least 2-3 times a day. I can see no reason why this would happen. I have tried a factory reset but nothing works. Any help to resolve would be greatly appreciated.
GiantP2 said:
Hi Guys,
I have a serious problem with my Inc S. Lately, after using a few apps (mainly on the bus) the phone will go to the lock screen. A this point when the power button to wake the phone, it will just hang. The backlights will still be on but the phone is unresponsive. I have pull the battery out for 10-15 mins before it will restart. This issue happens at least 2-3 times a day. I can see no reason why this would happen. I have tried a factory reset but nothing works. Any help to resolve would be greatly appreciated.
Click to expand...
Click to collapse
Telling us your issue is fine. However, we need more information such as your bootloader status as well as what ROM you are currently on (if you are of course)
I have unlocked the bootloader, cwm recovery, but still running stock Rom. Haven't flashed a new Rom as yet. The phone seems to get quite hot, too. I think overheating may be the problem as it won't turn on for 15 - 30 mins after battery has been pulled out, which suggests the phone would need that time to cool? Dunno, just a thought.
Sent from my HTC Incredible S using Tapatalk 2
GiantP2 said:
I have unlocked the bootloader, cwm recovery, but still running stock Rom. Haven't flashed a new Rom as yet. The phone seems to get quite hot, too. I think overheating may be the problem as it won't turn on for 15 - 30 mins after battery has been pulled out, which suggests the phone would need that time to cool? Dunno, just a thought.
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
Overheating is most likely your culprit. But its pretty difficult to pull the phone to about 50 degrees you really should watch whats running in your background and what applications you are running. Overheating may damage your phone and I assume you probably won't want that.
Would flashing a new Rom help? Never done it before.
Sent from my HTC Incredible S using Tapatalk 2
Ok, so when the screen blacks out, I can still receive sms. I have turned the screen time out to "never" (as it seems to only lock up when it goes to sleep mode), but it still blacks out after say 1/2 hour and screen becomes unresponsive. Have to pull battery out for a while. Is this a hardware issue rather than a software issue?
This still an ongoing issue, and driving me nuts. When ever the phone goes to the lock screen or after a phonecall, it wont come back on. The touch still works (can play music, etc by touching screen from memory) but the screen wont show anything. Have flashed cm7.2, done wipes, etc with no luck. Any help?
GiantP2 said:
This still an ongoing issue, and driving me nuts. When ever the phone goes to the lock screen or after a phonecall, it wont come back on. The touch still works (can play music, etc by touching screen from memory) but the screen wont show anything. Have flashed cm7.2, done wipes, etc with no luck. Any help?
Click to expand...
Click to collapse
Ok now that is not an overheating issue. That's probably a ROM issue or a kernel issue. I would suggest switching ROMs, maybe CyanVivoX or CyanVivo10.1 if AOSP is your thing. If not then maybe SVHD, Nik Project X Rebirth, or ViperVivo for Sense 4.1 (or Blackout or ARHD if you want Sense 3.6). Happy flashing
After a month of stuffing around and flashing my phone with different tons, I am still having the same problem. The only solution I have found is to install a wakelock app from the playstore, which isn't ideal as the screen stays on, drains battery and everything gets activated when the phone is in my pocket (mates are sick of getting phantom calls from me). The phone is no longer in warranty so I don't wanna take it to a tech.... There has to be a solution. Any further help woyl be greatly appreciated.
Sent from my HTC Incredible S using Tapatalk 4