Hey I hope one of you guys can help me.
I have a galaxy s running cm10 and I have had this persistent problem with my phone turning off automatically.
When I use it, I press the side button to turn off the screen and it is fine for a minute or so, but if I leave it any longer than that it turns off.
I have heard of something called Deep Sleep, is this the problem?
Is there a way to change how long it has to be locked to go into deep sleep?
Please help
I am losing hope
Cheers
HazzaGalaxy said:
Hey I hope one of you guys can help me.
I have a galaxy s running cm10 and I have had this persistent problem with my phone turning off automatically.
When I use it, I press the side button to turn off the screen and it is fine for a minute or so, but if I leave it any longer than that it turns off.
I have heard of something called Deep Sleep, is this the problem?
Is there a way to change how long it has to be locked to go into deep sleep?
Please help
I am losing hope
Cheers
Click to expand...
Click to collapse
Sounds interesting i know this from the first custom roms i tried a year ago!
Which build of cm10 are you using? Any "faulty" app installed? for me dropbox made cm10 instable and laggy, so i stopped using it.
Have you checked the md5-sum of the .zip file of your downloaded rom? Maybe the download was faulty... Happened to me twice on cm-nightlies.
Cheers
EDIT: Which kernel are you using? For me Stock-Kernel ist aboslutely rocksolid! My phone had 140 hours ontime this morning, before i flashed the newest build.
Hi,
Is you IMEI ok ? I had this problem with CM10 too but now my IMEI is ok I have no pb at all
have you overclocked your phone? i had the same thing happening with other roms...as soon as i had overclocked and turned the screen off, my phone got stuck after a while. try cleaning nstools settings. if that doesn't work, you might try turning off deep idle if it's active, could also be the reason
SKArabaeus said:
have you overclocked your phone? i had the same thing happening with other roms...as soon as i had overclocked and turned the screen off, my phone got stuck after a while. try cleaning nstools settings. if that doesn't work, you might try turning off deep idle if it's active, could also be the reason
Click to expand...
Click to collapse
Hey
Where is deep idle?
I have no idea where it is and ive looked everywhere in settings.
Do you have photos?
That would help.
Cheers
ThrashJan said:
Sounds interesting i know this from the first custom roms i tried a year ago!
Which build of cm10 are you using? Any "faulty" app installed? for me dropbox made cm10 instable and laggy, so i stopped using it.
Have you checked the md5-sum of the .zip file of your downloaded rom? Maybe the download was faulty... Happened to me twice on cm-nightlies.
Cheers
EDIT: Which kernel are you using? For me Stock-Kernel ist aboslutely rocksolid! My phone had 140 hours ontime this morning, before i flashed the newest build.
Click to expand...
Click to collapse
Hey
I would not know the first thing about what to look for?
How do i know its faulty?
Cheers
HazzaGalaxy said:
Hey
I would not know the first thing about what to look for?
How do i know its faulty?
Click to expand...
Click to collapse
Okay, let's start from the beginning :silly:
Whats the exact name of the rom you flashed?
How do you flashed it? (Wipe, etc.)
Have you flashed any other stuff? (Inverted Gapps, Battery mod, Kernel, etc.)
Have you many apps installed?
If i where you, i would flash the newest build with a full wipe, so you got a new, bugfree and stable system
same issue
I have been having the same issue ever since switching to CM10, I have been installing nightlies hoping it will end, but appears to be isolated. Would it help to manually flash boot for each ROM? It cuts off randomly and won't turn on unless charged by a wall charger, or other high-power input (doesn't turn on or charge from car outlet). It doesn't appear to be caused by an app.
Did you wipe when installing nightlies?
If you try to go stock with Odin, and the issue is exactly the same, I think you should consider it could be battery malfunction.
Sent from horseback.
Related
Guys a Problem..
Am Running Team hacksung B16 for around 1week and i love using it..
for the 1st 2days i was Running on Stock Kernel which came with the build.
Now am running on ICY Glitch B5..
The Problem is.
When i Turn on Wifi and go to bed, my Phone dies.. But when i remove my battery nd place it back in, my phone power on..
This problem does not occur when Wifi is turned off..
At the 1st, on stock kernel i didnt experienced this issue when i kept wifi turned on.
Any possible solution for this?
I need my yahoo and Gmail to be synced for new mails
Turn off Didle
b-eock said:
Turn off Didle
Click to expand...
Click to collapse
how do i do tat?
Am noob to droid..
DL NStools from market and make sure it isn't enabled...
b-eock said:
DL NStools from market and make sure it isn't enabled...
Click to expand...
Click to collapse
Yea i downloaded it and Its Status in OFF by default When i opened it..
Will Give a Try by today night and lets see..
If it fails then go into CWM Recovery and Glitch>voltage settings>remove NSTools settings>yes
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
docsportello said:
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Are you on a custom rom or stock rom ?
If on custom what rom and kernel u using?
Flashing another kernel may help
Sent from my GT-N7000 using XDA
docsportello said:
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Are you sure it's totally off? I had this issues when phone looked like it's turned off, but when I pushed buttons for a while it was waking up, so I didn't have to restart it. Some people recommend using jBroid Kernel Cleaning script before you flash new kernel.
And if it's happening after installing new ROM I would recommend to flash stock ROM, then doing a full wipe twice and then flashing ROM you currently use or want to use.
I don't have such problem anymore so it might help.
I'm on the custom rom, I've never rooted my device. The phone is like dead, it's not even turned off. At first I had to put the battery out and then put it in again. Then I discovered that if I pressed the power button for something like 5-6 secs it started again, with the samsung logo and all. Not a big issue but if I don't check my note often I risk to miss important calls. Please help me! Thanks
Sent from my GT-N7000 using XDA
docsportello said:
I'm on the custom rom, I've never rooted my device. The phone is like dead, it's not even turned off. At first I had to put the battery out and then put it in again. Then I discovered that if I pressed the power button for something like 5-6 secs it started again, with the samsung logo and all. Not a big issue but if I don't check my note often I risk to miss important calls. Please help me! Thanks
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
What apps do you have installed? I had this problem with both WidgetLocker and NoLed.
WidgetLocker I have just given up with - wish id never bought the stupid thing, as it's never worked reliably on my Note or my tablet! (rant over).
NoLed I traced the problem to the flash-the-screen battery saving features. Changing it to leave the screen on all the time when notifying hadn't seemed to use any more battery life and my dead screen problems have gone away.
Just something to consider!
You can try connecting your Note to the PC when running Samsung Kies software. Maybe it will find an update to the ROM you are on right now and this might fix your issue. If not you should go to the developement section of this forum and search for the recent stock rom available and then follow dr. ketan's guide http://forum.xda-developers.com/showthread.php?t=1424997
If flashing new ROM wouldn't solve your problem, then I guess it's a hardware issue that requires professional service.
squicky said:
You can try connecting your Note to the PC when running Samsung Kies software. Maybe it will find an update to the ROM you are on right now and this might fix your issue. If not you should go to the developement section of this forum and search for the recent stock rom available and then follow dr. ketan's guide http://forum.xda-developers.com/showthread.php?t=1424997
If flashing new ROM wouldn't solve your problem, then I guess it's a hardware issue that requires professional service.
Click to expand...
Click to collapse
I think he should try a different kernel first. Another possibility is that some apps in your phone cause this problem.
Sent from my GT-N7000 using XDA
kelvin fong said:
I think he should try a different kernel first. Another possibility is that some apps in your phone cause this problem.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I think its a stock kernel and ROM he's on... Even though he says 'custom ROM' he also says its never been rooted, so how would he get the custom ROM working if not by rooting the phone?!
That being the case it must be something interfering with the sleep mode so its probably best to check what has been installed recently, remove those apps one by one over a period of time and check if the problem goes away!
Yes it's a stock rom I am using and the issue happens randomly... Is it maybe lockscreen app? I read the users' comments and no one mentioned such a problem...
Sent from my GT-N7000 using XDA
me too my ho jus shuts off by itself.. I m using KL1 kernel wif KL3 rom
Note randomly shuts down - Did you solve this issue?
Hi,
I was wondering if you managed to solve this issue as I am experiencing the same issue where the phone randomly switches off when the screen is locked.
I am using easy battery saver app which sets the sleep schedule to check network data every 15 min.
Cheers
Galaxy Note 2 shuts down
The issue exists on the Galaxy Note 2 as well and has nothing to do with software.
The problem is hardware related. The phone is flawed and shuts off on it's own under various conditions, all hardware related. Take a look at this video: http://www.youtube.com/watch?v=SjLn2yikYnI
Also, take a look at this site I built that goes in to more detail regarding the issue: www.GalaxyNote2ShutsOff.com
One look at that short video and I am sure there will be some light bulbs going off. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.
thanks for the heads up with NoLed....I just hope my issue ( phone's screen just dies when not in use - but I think the device is on as the headphone jack responds with the disconnection sound when unplugged) gets resolved...
I was thinking too that philz cwm may be affecting it ( kernel issues )? ...any way I will update as time passess
My brother's galaxy note have been facing serious sod problems since he bought the phone at Nov 2012. After he faced it the 1st time , he sent to SC and got it back. After 1-2months the problem came again and he asked for my help. I persume it was because the malaysian firmware of the ICS was somewhat unstable from what i read from forums here and there. So i changed the firmware to JB duno from which country when it came out in MAC. After a week or so. The problem reappeared . So I just decided to root and chnge the kernel and also the ROM. Changed the ROM to a stock rom and a kernel. Still the problem persist. I'm out of options. Went to the ****ty SC and the idiots just factory reset the phone and give u back. BUNCH OF RETAR*S . (sorry for my languange)
Hope someone here may help me out with my problem. Thanks a million :laugh:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I just installed an aosp rom (PA) and I hope it fixes the problem. Well I've seen the amount of apps installed in the note and its jst a quarter the amount I have in the Galaxy S2 and my S2 works like a charm. The note has been giving me headache ever since I got it from my brother. Hope this does solve it , if not I guess its something else maybe hardware
Phone sod twice on paranoid android. FML! Guess im visiting SC tmrw again.
Same problem with me..
My Note 1 has SOD since 1st time bought it..
be patience to install JB --> still SOD
change kernel to SpeedMod 5.3 --> SOD again
change kernel to PhilZ --> sometimes SOD
I have read many information that related with SOD in galnote 1, my opinion it is related with hardware too.. sometimes
or it is related with kernel... it can not wake from deep sleep..
anyone have another better suggestion to cure this ?
if u're using pure stock rom still facing the same problems then definitely is hardware issues!
if ur device still under warranties suggest bring to SC ask them do a thorough check on it n let them know what's going on actually...
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
psywarx said:
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
Click to expand...
Click to collapse
Yeah and they will give your phone back only doing a factory reset lol
Sent from my GT-N7000 using Tapatalk 2
I too get this SOD once a week on my GT-N7000
Phone status when this happens:
stock JB(earlier ICS), non-rooted, data connection, wifi, GPS, bluetooth all disabled. Battery mostly above 80%.
Gmail, Google+, Facebook and all other social n/w apps disabled (yes, i am an oldtimer )
During SOD, if a third party calls my number, he hears it ringing, but my handset is dead as dodo (quite dangerous as the calling person may think i am not answering it)
i used to get this when it was on ICS and still getting it after i upgraded to JB.
Most of the time, SOD occurs during wee hours in morning ( i used battery monitor app that logs battery stats every 10 minutes to check the time when this happens).
Sometimes it occurs when the phone is in my jeans back pocket. phone needs a 10 second press on pwr switch to restart it.
Turning off the "power saver" mode seem to reduce the probability of SOD.
i have taken this phone to SC and they re-flashed the JB.
i told the SC chap that i have already done this and couple of factory resets, but he said that they do "much more" than just re-flashing through kies like calibrating camera, bluetooth )
does anyone in the know, know if this is indeed true ?
Thanks
-mprab
updates...
After 2 days of re-flashing at a samsung authorised service center, i got SoD 2 times in a period of 12 hours.
once last night and second time when i was traveling to office.
Last night i installed some bare-minimum apps back after waiting 2 days for any SoD to happen in "stock" condition.
Well.... i did not pay 30K to use the GNote as just a phone, so installed some basic apps (Battery monitor, Bangalore BMTC, RealCalc, GPS Test, ES File explorer and a first time app StatusLogger)
phone went dead at 1:00 am in morning and as usual there was no wakeup alarm.
phone was warm to touch when it was lying dead. The battery which was 96% at 00:30 AM had gone down to 54% at 7:00 AM.
Status logger did not show any loss of GSM signal which might have resulted in phone transmitting at higher power/hunting for signal etc.
The "radio" seemed working, because when i made a call to the dead phone from my landline, i could hear the phone ring instead of expected "phone is switched off" message i was expecting.
So this has to do with application processor going in some infinite loop.
Uninstalling all apps is NOT an option.
anyone know if we can establish any debug connection to phone and know what the hell CPU is up to in this situation ?
any processor logger that will periodically log all the processes running on phone ?
SOD resolved... not a single one since 6 months.
Hey guys, just wanted to share this info with you, I had SOD's like anything and did all freakingly possible things right from flashing roms to kernels, speed up CPU, banging my head in front of the dumb witted morons at samsung service... to get rid of that pain. What helped me was an app called "WAKELOCK" by darken which is merely 72kb in size but works wonders, not a single SOD after that. What u need to do is.... it has a list of presets that makes sure your cpu stays up. You need to select the preset called "partial wake lock" which is at no. 4, and viola...
It ensures that the CPU is running. No SOD ever after. Also, you need to make it autorun on boot from the options. Yea, it does eat up batter a bit more but its definitely manageable. I still need to charge my note only at night.
Just to be sure, I uninstalled it and guess what, SOD returned. So, do try it, I hope it helps...
Hello all. I am writing about my wife's Note1 (N7000, 16Gb).
The phone functions just fine except for one thing. At about 50% battery, it will just go to deep sleep and will require a long press power to wake up. Happens with any battery and have tried a few different ROMs (custom and stock). A SECOND Note we have (my sister's; I have a Note2) doesnt do any of this with same batteries and same ROMs, so does seem to be weirdness with this one.
I DO have a solution which has been proven to work with a scientific cause/effect relationship:
I installed THIS app from the PlayStore:
https://play.google.com/store/apps/details?id=eu.thedarken.wl
Now I dont fully understand wakelocks, but I reckoned the CPU was going into deep sleep so I set the wakelock to be FULL (see screenshot 1). This 100% solves the problem and the phone is fully normal now, and my wife says she cant tell any loss of battery life.
SO....
Looking to do one of two things:
1. is there a way we can have this app AUTORUN on boot cos she keeps forgetting to run it when she swaps battery (which is once a day cos she is heavy outside house user) and then wakelock not running then phone sleeps! DOH! If autoruns, then she can at least SEE the wakelock screen and press the lock to be active (we are still testing how LOW a wakelock can we get away with but for now using 7)
2. even better, is there a KERNEL I can flash her to that will give me same functionality so she never even needs the app? Something where I can set a minimum CPU level in a similar fashion and it is now a set-it-and-forget-it even surviving a reboot?
See pic2 for the stock ROM she is on now and is great. Given that phone is otherwise fabulous and all else is stable and functional, I would like to keep to this ROM if at all possible so as not to introduce new weirdness. Also, given that this is such an easy software fix, I am not looking to hardware repair the phone as just want to fix this and get on with life.
Hope this is enough info for an informative and educational discussion and looking forward to some good advice.
Thanks to all, and kind regards,
Asif
So are you wanting to prevent the phone from going into deep sleep?
maskerwsk said:
So are you wanting to prevent the phone from going into deep sleep?
Click to expand...
Click to collapse
Correct, yes. Need to stop the phone from sleeping so deeply that it is effecttively off now as wife misses critical reminder alarms, as well as phone calls etc. As it is (without the wakelock) the phone is pretty useless. WAS actually my sister's but had to swap and now SHE has the wife's old one. Sister is a surgeon and when phone was deeply asleep, hospital could never contact her so not good. So swapped and sister has wife's good one so that is off my back. Wife's (sister's old one) is here and easier to test out as sister lives in England and I am in Glasgow. Easier to take dodgy one and work on it here.
So need phone to remain functional until such time as battery is dead, like you would expect any normal phone to do.
So need wakelock to remain in force as described above, as WITH the wakelock active, the phone is perfect.
Thanks.
Is the phone rooted?
If so you could flash this mod i made. It prevents deepsleep.
http://forum.xda-developers.com/showthread.php?p=39915561
Only works on xxlsz though
maskerwsk said:
Is the phone rooted?
Click to expand...
Click to collapse
Yes it is. Sorry forgot to mention.
See edited post above
maskerwsk said:
See edited post above
Click to expand...
Click to collapse
Looks like the kind of thing I need, thanks.
Was very much not keen on switching ROMs tho as this one just working perfectly, and we all know that every ROM has it's quirks. Didnt want more headaches with the wife giving me daily anecdotes of weirdness!
What do you reckon would happen if I were to try flashing this on LSO ROM? I suppose the worst thing is a bork and then I just wipe and reflash LSO fresh? Is this just a typical CWM zip?
Or is there anything just like this (kernel or mod) that could be flashed on LSO?
Appreciate your time and help so far.
The mod is in the androidpolicy.jar so i doubr it will work. Worth a try as long as you backup first
maskerwsk said:
The mod is in the androidpolicy.jar so i doubr it will work. Worth a try as long as you backup first
Click to expand...
Click to collapse
OK, thanks.
Before I do, will wait to let the thread cook a wee bit and see if any other alternatives emerge.
Cheers.
asifanwaruk said:
OK, thanks.
Before I do, will wait to let the thread cook a wee bit and see if any other alternatives emerge.
Cheers.
Click to expand...
Click to collapse
Bump.
Any other ideas before I try the above?
Thanks.
Just a follow up if anyone is following this.
I DID flash the LSZ ROM and the zip patch and phone still died that night and failed to ring the morning's wake up alarm. To be honest, I am not sure what is going on with it. I have done a 'deep clean' (actually too much and I bricked it and then recovered it! Code Brown!!) and now flashed Slim Bean 4.2.2 to try something totally different and get away from a Sammy based ROM.
We shall see by tomorrow if phone can sleep at night without going into a coma, and then wife's wake up alarm can still ring.
If not then I think it is time for a service.
But wanted to come back on here and thank you for your time and efforts anway.
Kind regards.
Hi guys, I have annoying probnlem with my LG 4x... When I work little bit longer on my phone, it just starts to behave crazy. Screen starts to "touch himself" I just look at it and he starts to get in menus, opening pictures, closing apps, opening new ones... I just lock screen for 10 secs and than everything is fine for few minutes. Than same thing again. This happens with every ROM and every karnel I try til now. Works fine only with stock. I'm now on Beanstalk 4.4 and iodak 9.95. Thanks!!!
flashroyal said:
Hi guys, I have annoying probnlem with my LG 4x... When I work little bit longer on my phone, it just starts to behave crazy. Screen starts to "touch himself" I just look at it and he starts to get in menus, opening pictures, closing apps, opening new ones... I just lock screen for 10 secs and than everything is fine for few minutes. Than same thing again. This happens with every ROM and every karnel I try til now. Works fine only with stock. I'm now on Beanstalk 4.4 and iodak 9.95. Thanks!!!
Click to expand...
Click to collapse
Its a weird issue, are you sure it works fine on stock? because it sounds like a digitizer issue to me (rather than software, since the rest of us dont have this issue)
im not sure where to begin lol, can you pull some logs? (dmesg and logcat)
Oh.. and I guessed it was only me.
I have this problem too, works fine with stock but it goes crazy with custom rom.
Any idea ?
stefan2012 said:
Oh.. and I guessed it was only me.
I have this problem too, works fine with stock but it goes crazy with custom rom.
Any idea ?
Click to expand...
Click to collapse
Logs?
JoinTheRealms said:
Its a weird issue, are you sure it works fine on stock? because it sounds like a digitizer issue to me (rather than software, since the rest of us dont have this issue)
im not sure where to begin lol, can you pull some logs? (dmesg and logcat)
Click to expand...
Click to collapse
I saw this problem first time when I instaled facebok massanger, so I thought app was problem...uninstaled it, same thing again...new rom, new karnel, same thing again...today my phone was on sun, and I have been using it for 3 minutes...same thing again
and if you please can just shortly explain me how to pull those logs
flashroyal said:
I saw this problem first time when I instaled facebok massanger, so I thought app was problem...uninstaled it, same thing again...new rom, new karnel, same thing again...today my phone was on sun, and I have been using it for 3 minutes...same thing again
and if you please can just shortly explain me how to pull those logs
Click to expand...
Click to collapse
Its easier for me and better for you if i leave this here http://forum.xda-developers.com/showthread.php?t=2414731 (worth bookmarking:good
JoinTheRealms said:
Its easier for me and better for you if i leave this here http://forum.xda-developers.com/showthread.php?t=2414731 (worth bookmarking:good
Click to expand...
Click to collapse
Sorry for a late answer, I was in my night shift. I hope that's it. One more thing...my cpu temperature when this happens is around 50°C...is that normal temp???
flashroyal said:
Sorry for a late answer, I was in my night shift. I hope that's it. One more thing...my cpu temperature when this happens is around 50°C...is that normal temp???
Click to expand...
Click to collapse
No worries, nothing out of the ordinary in the logs, its looking more like hardware(hopefully im wrong). It might be worth testing a stock rom under the same conditions again, if there is no issue, then theres something weird going on. btw 50c is fine temp for cpu, around 75c is the limit.
Can you get a screen recording of it? (most 4.4 based roms have this functionality built in) this could be helpful also https://play.google.com/store/apps/details?id=ds.cpuoverlay
JoinTheRealms said:
No worries, nothing out of the ordinary in the logs, its looking more like hardware(hopefully im wrong). It might be worth testing a stock rom under the same conditions again, if there is no issue, then theres something weird going on. btw 50c is fine temp for cpu, around 75c is the limit.
Can you get a screen recording of it? (most 4.4 based roms have this functionality built in) this could be helpful also https://play.google.com/store/apps/details?id=ds.cpuoverlay
Click to expand...
Click to collapse
I don't know why, but every time I tried to record screen, phone just reboots. I tried with various apps, every time same thing. I cant find built in app in beanstalk 4.4. I'll try stock again but cant before tomorow. Thank you for your time
Use beanstalk with grouper blobs, and press vol up and power simultaneously to record
Sent from my LG-P880 using Tapatalk 4