Database Develop

[Q] CM7 shutdown issue

Have anyone other than me experienced that the phone suddenly is turned of? It's not the BSOD or reboot, but just turned off and can be turned on right away..
I've saw it yesterday when it was in my pocket, and this morning when i woke up.
I'm using the CM7 RC1 ROM straight from the box.

Yes. I get this to... (With every build of CM that is)

Same happens to me also with the latest CM7.

Me and my brother also get this, started with cm7 57 I think
Sent from my Optimus 2X using Tapatalk

Does anyone know how to use ADB to log? Then we could maybe capture some logs when this happens and post to aremcee to see if he can help us..

The same thing has happend to me 2 times in the week a have had this replacement device. It's worse than the one I traded this one for
But I'm on stock havn't rooted or anything.

Just had a BSOD aswell.. Gotta hate this phone. It's works on stock so I can't send it to my dealer and get my money back

Install a Froyo Rom
Profit.

My findings on the CM7 sod (sleep of death) issue (I post this here, as I don't have enough posts to post it to dev area):
I've been using CM7 occasionally since the first nightly. About 2 months ago I suddenly had 3 sods in 2 days. This was after I bought JuiceDefender Ultimate. In JD I had sync enabled once per hour, and JD set to first try to connect to wifi and then mobile data. In Android wifi settings I had wifi sleep policy set to "when screen turns off".
After I set JD to use only mobile data on sync events, and turned wifi sleep policy to "never", I haven't had a single sod since. If I remember correctly, I once managed to induce a sod by turning wifi on or off (can't remember which) through the power control widget, and immediately after that I turned the screen off normally by pressing the power button (while wifi was "dimmed" in the power control widget meaning it was changing it's state).
So I strongly believe that my sods were caused by the combination of turning wifi on or off (either through widget or JD doing it) and turning the screen off at the same time. I didn't experiment any more, since I found my solution above.
I wrote this here, because people try hard to hunt down what's causing the sods, and I wanted to share my thoughts. If it is of no help, then sorry.

it happens sometime... don't trust your phone's alarm to wake up. you could have bad surprise (just had the experience 2 days ago) :'(

i am running cm7 no. 165. and vork kernel clocked to 1504 no reboots or black out issues. i also have green power managing my network data only... good luck all... just remember that cm7 is still nightly and is not considered stable.

Hi, I'm about to get one LG, but I've had the same issue with an Orange Boston mobile with a 2.3.5 CM7. I disabled Wi-Fi sleep too and it seems to help.
Before the scren weirdly shut down and the phone rebooted.

Hmm might try this out and see if it works.
I can't seem to get this issues myself. I will try and test this later on my other phone.

That is the reason why I don`t use CM7 anymore ...

Moderator Message
Extensive discussion going on here >
http://forum.xda-developers.com/showthread.php?t=997705
THREAD CLOSED

[Q] Galaxy Note not waking up?

I can't put my finger on this issue I've been having with my Note.
Don't get me wrong, this device is a godsend!
The problem I've been having is that sometimes when I take my Note out of my pocket and try to press the unlock or menu button it doesn't show anything on the screen. I've read about people having issues with delay before it pops up, but it doesn't pop up even after 10 seconds or a minute, it feels like the device 'hangs' or doesn't want to wake up. The only way I can turn the phone on again is by pressing the unlock button for like 10 seconds and the phone reboots.
I thought it was a problem with Green Power, I thought it maybe had issues turning off the wifi or data when the screen was locked and that the service would cause the OS to crash or 'hang'. When I look at my battery history after the reboot it shows that I lost a significant amount of battery (5-15%, depending on how long it took for me to 'discover' the crash) and there's a 'jump' in the graph.
Things I've tried:
Stock rom - problem persists
Different kernels - tried all the kernels available in the market including stock, problem persists
Add a bit of paper between back-cover and battery (to make sure it doesn't lose contact)
Checked if there was dust between battery connections
Tried different sim card
Tried disabling wifi and data all day (mysteriously persists)
DIfferent governors (ondemand and interactive) (the phone reverts to default governor after the forced reboot, normal? i have my phone set to interactive on boot, but somehow it skips that after the forced reboot)
I've attached a picture of the battery graph. According to the stats there's a 25 minute gap where the phone was 'stuck' and you can see that the screen was on and active for that duration.
There are NO funny apps running in the background, this is is a clean install with some standard Samsung apps frozen.
tl;dr version: phone randomly won't wake up; battery loss after forced reboot;

I might have found the issue myself. Now when I come to think of it, I think it always occurs after I've been in my car for like a 30 min drive... Maybe the phone is having trouble switching networks? Anyone know what might be causing this?
Or better yet, how can I research this issue? Can I enable some logging somewhere to track this?

I had the note for about 10 days and today, about 1 hour ago it happened to me for the first time. I tried the home button to wake the screen but nothing, tried the power , nothing and holding the power but nothing happened. I had to pull the battery.

I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.

tamarian said:
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
Click to expand...
Click to collapse
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.

I'm on stock room and unrooted. Like I said first time it's happened.

i've had the GNote since 4 days now , and yesterday same thing happened as the device was in my pocket and i couldnt wake it up at all , battery pull solved it.
im on stock , non rooted

I can't believe that we are the only ones with this issue. Anyone else? OR better yet, how did you resolve it?

Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.

kirkla79 said:
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
Click to expand...
Click to collapse
Thanks for your reply. I did some research, and apparently it had to do with static being built up in the screen from wearing it towards your body in your pocket.
This issue was that you couldn't swipe the lockscreen cause the touch screen wouldn't respond. The problem we are having is that the screen won't even turn on and that the system locks up.

Same issue here with my 2 days old Galaxy Note, that's how I found this forum. In my case it went from not waking up occasionally to every time WIFI was ON (I did some experimenting with settings to see which one could be the one causing the problem). But then...occasionally it would not wake up even with WIFI OFF: very annoying. And this is my first Android, so I didn't have any custom anything, pretty much same as out of the box when I got it The only solution was to reset the handset. And definitely has nothing to do with having it in my pocket as I don't carry it in my pocket. Rang Samsung, they told me it was faulty, I returned it. Now I'm concern the next one is going to have screen issues? As so many people complain in this forum? we'll see.

My issues have been resolved after flashing AbyssNote 1.4 and when I stopped using System Tuner. I've started using Voltage Control instead and now I'm not even having problem @ 100Mhz undervolted 50mV from stock.

Same problem with my wife's Gnote, totally stock, just a small handful of apps installed. Happened twice, about a week apart.
She does a lot of travelling, maybe you're right about that. But it happens after she gets home when it's still OK.

Had the same same issue twice in two days and had to do a battery pull, just did a master reset and re -installed the applications manually, so far so go.
YOu guys think its a hardware or a software issue?

Hmm.. Happened to me too about three times in the last two weeks. I am on stock rom but rooted, and running Green Power. Hopefully samsung will fix it in the next updates. Seems like a software bug to me. Maybe not enough juice when in deep sleep?

metus666 said:
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
Click to expand...
Click to collapse
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically

neunzehn77 said:
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
Click to expand...
Click to collapse
problem is it also happens on stock rom.

mfractal said:
problem is it also happens on stock rom.
Click to expand...
Click to collapse
It's very well possible that the stock kernel has faulty settings for the CPU. Haven't had the problem again with AbyssNote 1.4 and Voltage Control (even with custom cpu frequencies)

I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??

qazkamakazi said:
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
Click to expand...
Click to collapse
at this point we're just guessing, there haven't been any official confirmations of the problem as far as i know.
But if it's so accute that it keeps happening all the time you must have a faulty device.. call samsung ?

[Q] Galaxy Note GT-N7000 crashing regurlaly how to find out the culprit?

My Note has started crashing regurlaly, I have had it since release and have a lot of software on it. I am not sure when it started happening but it is definatley getting worse as time goes on.
Is there any log file or event browser that can be installed to tell me what is causing the problem?
When I say crashing I mean literally crashing dead not a force close. I either find it in my pocket turned off and then have to hold the power button for an age to turn it on or sometimes it is sat on the desk and I suddenly hear the noise it makes when it re boots.
Any suggestions for finding out what the problem is that don't involve uninstalling software until the problem goes away?!
Thanks

Have you tried better battery stats? It gives a list of processes that have been running.
Definitely strange - do you have an anti-virus program you can run to see if it can help?

That sounds like a Sod (Sleep of Death) issue that's been reported many times b0t with no definitive solution of yet..
Some said changing modem helped, others with changing kernel or even ROM but no consistent solution across all users
Try to fix permissions through advenced menu in recovery but am afraid there is not much I can help with

wingnutLP said:
My Note has started crashing regurlaly, I have had it since release and have a lot of software on it. I am not sure when it started happening but it is definatley getting worse as time goes on.
Is there any log file or event browser that can be installed to tell me what is causing the problem?
When I say crashing I mean literally crashing dead not a force close. I either find it in my pocket turned off and then have to hold the power button for an age to turn it on or sometimes it is sat on the desk and I suddenly hear the noise it makes when it re boots.
Any suggestions for finding out what the problem is that don't involve uninstalling software until the problem goes away?!
Thanks
Click to expand...
Click to collapse
Omfg, I don't think your alone cause I have the exact problems at times when the note just freezes up and you have to manually boot up...lets hope the upcoming pics update will solve this ongoing problem... I'm getting this about 3-4 times a week
Sent from my GT-N7000 using XDA

it is starting to make the phone a liability as I keep finding it turned off in my pocket!
Is there no software that will produce a crash log of some sort?

wingnutLP said:
it is starting to make the phone a liability as I keep finding it turned off in my pocket!
Is there no software that will produce a crash log of some sort?
Click to expand...
Click to collapse
I hope there is...
Sent from my GT-N7000 using XDA

this is driving me nuts. The phone is unusable.... is there no possible solution??
At this point I will try anything. It crashed during the night on Thursday, didn't restart and so there was no alarm and I was late for work!

Please post your current configuration Kernel, Anti Virus program if any, undervolting, overclocking ?

By any chance are you using easy task killer... if you are just change the auto optimize to nothing - I did that and it stopped sleeping...if your problem is persisting then you could just do a factory reset and use default settings...
Sent from my GT-N7000 using XDA

My note recently started crashing as well, whenever i turn on my mobile data plan or the wifi it will crash right away
However this is ironic because when ever i put my mobile in charging mood than i have no problems at all.
So im thinking ,is this the battery problem or the software problem?

mumuxy said:
My note recently started crashing as well, whenever i turn on my mobile data plan or the wifi it will crash right away
However this is ironic because when ever i put my mobile in charging mood than i have no problems at all.
So im thinking ,is this the battery problem or the software problem?
Click to expand...
Click to collapse
battery problem.Try to see what is the output of ur battery in full charge by messure it with electric potension meter (sry for bad english).
If the meter say less than 1850mAh in full charge than u need a new battery.

Xperia V standby hang, cannot wake up

anyone experience Xperia V cannot wake up or hang in standby?
it happens at nite after i sleep. but when i wake up, i press the power button several times but the screen doesnt on. notification light is working and blinking.
only way is to remove battery. its been happening everyday. even alarm is not working. checked my backup(sms, call log), it didnt backup. :crying:

I at least dont have that problem. Is your phone stock? Rooted etc?
Sent from my LT25i using xda premium

I have this problem too. Not rooted. Probably, while charging this problem not appears.

Wrong section. This belongs in Q&A.
And for your problem, few users with.XT and XTX also reported similar problems. They are known as SoD (Sleep of Death).
There is no known fix yet. One users took it back to the store and the the Sony tech guru told him it's an isolated problem and he got a new one. So I suggest you go back to the store.
For anyone using adw launcher, one user reported that that caused his SoD. When he uninstalled that it was gone. Can be an app.
Try factory reset, and start first day without installing apps. And day by day add a new app, this way you can rule out if apps cause the problem.
Also format internal and external sdcard. Don't just empty them by wiping, you should really format, so no traces of possible app malfunction can be found back by the system.
Sent from my LT30p (Xperia T) using XDA Premium.
Did I help? please press thanks button

after several days of testing, it doesnt hang on mine for 3 days already.
i guess its because there is a additional line in build prop "dalvik.vm.heapsize=36m" that cause this? this also cause my Need For Speed Most Wanted to force close too.
i also increase min clock freq to 594MHz.
also run TempMonitor(paid) on my notification bar.
not sure the above method works for most of u.. but try if it works.

I've got this problem since the first day. Got the phone, booted it up without even installing a sim card/downloading anything, plugged it into the charger, and it froze.
Since then it would go a few days without freezing, or it would freeze 3 times a day. The freezing always happen in standby mode.
Since it froze on a fresh system with no apps installed, it can't be app-related. There are users who have never experienced this problem, so I suppose the only way is to return the phone or take it to your local sony service center.
Normally it would just hang there and you'd have to pull the battery out. There was once where it hung and the phone got incredibly hot, and battery would be drained really fast.
Currently I am experimenting with keeping WiFi OFF, and surprisingly the phone has been fine for 4 days straight without freezing now. Its just something I'm trying and by no means this is a fix, but returning the phone to a sony store isn't an option for you, you might want to see if this works for you.

for those still having SOD, maybe u can try this. not sure it helps or not. because before i install jellybean, i review the code in build.prop first. so that is why it didnt happen on me for 2 weeks. well, i test it out yesterday.
use either ES file explorer or Root explorer, go to system -> build.prop.
find this line dalvik.vm.heapsize=36m, put a # in front of it to disable this code.
it could be because there is another similar code, thus conflict. u can find another similar line at the bottom of build.prop.
hope it helps!

Have you had anymore sod since disabling that?
Sent from my LT30p using xda app-developers app

scythekain said:
Have you had anymore sod since disabling that?
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
before i install custom rom jellybean, i already disable that. didnt had any SOD since than.
but of cos 1 day i decided to test it out, and it SOD the next morning.

Disconnected...

OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?

I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?

Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app

skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty

I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?

shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.

I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification

disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...

Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.

I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.