Database Develop

[Q] nc randomly reboots

Hey guys, my nookcolor has been randomly rebooting since i rooted it. Never while i was using it, i just sometimes hear the bootup sound, and look to find that my book is now on.
Im just concerned this will affect my battery, and i also don't want it rebooting while im using it.

I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..

Divine_Madcat said:
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Click to expand...
Click to collapse
I still want to use the B&N stuff. Any rom that emits them, I will not be installing.

I think it likely that there are NC users in both camps-
Those who want the B&N stuff and those who don't.
I am one of those who don't; the Nook for Android software does better for reading ePub, imo and I am rarely near a B&N store.
Right now we have root and Market plus B&N and I would guess (could easily be wrong) that the first custom roms will be pure Android with no B&N.
We will probably end up with an option to set while flashing: retain B&N customizations or straight Android.
I base this guess on what I have seen in the other roms for various devices (mainly Droid) I have looked at.

Same here. If I want to read B&N books, I could still use their Android app on a custom ROM.
After switching to Cyanogen on my phone, it's been quite relaxing to not have to worry about provider updates bricking the thing or otherwise screwing up the rooted customizations (or just randomly resetting the thing back to factory defaults because I started up one of their apps and it got confused). Not to mention that the CM team does a far better job supporting the device than the manufacturer and my service provider does.
And yes, like other Android devices, there will probably be ROMs in both categories: completely built from scratch with no B&N portions at all, and improvements on the B&N system to add more functionality.

Fair enough for those that are interested in the reader portions - i have to admit, i bought this as a tablet, with literally 0% in it as an e-reader; i already have a Sony 505 for that. I may use it on occasion, but only as an afterthought.
However, this topic is really drifting - perhaps we should just bring it back to the rebooting issue?

Yeah, I installed the Uptime Widget on my NC today and picked it up a few ago and its uptime was 1:30; max 15h (from before it rebooted 90 minutes ago). I'll keep running it.
What we need to do is get a logcat when it happens.. So maybe overnight I'll leave it running or something. It just rebooted on me and I was semi-watching it, didn't even notice but Uptime Widget was reset to 7m up, 15:30 max..
I have started up a logcat and I'm going to leave it running while I get ready to go out for the day.. Although I just installed and fiddled with Google Earth, which failed badly, so I wonder if it caused some problem. Also saw it happen after playing with Google Maps, so I wonder about Location stuff maybe doing it.. Dunno. I just launched Maps a few ago and it's been up since. Hopefully a logcat will capture some info.
I have noticed that I've seen some crashes that don't show the Crash dialog.... TweetDeck is particularly bad about crashing viewing some Facebook posts, and in this case it just goes black for half a second then back to the list of posts. A logcat shows it crashed. But I don't know the two are related (not having the crash dialog stuff and the reboots that is).

I had it reboot on me twice last night, one time I didn't know about it until I picked it up later and noticed the uptime widget was down to some 30 minutes, and another time right before bed I hit the power button and about 10s later I saw the boot up text and a reboot happen.
Still haven't caught it on logcat.

My doesn't reboot spontaneously, but it does "lock up" and won't turn on with the power button from standby occasionally. If I remember to use the Nook Button to wake from standby, I don't seem to have this issue. If I use the power button, and it won't wake, I need to hold it down for ~15 seconds and it reboots.
AFIAK, it has done this since I purchased it (I rooted after about 1 hour with the NC in my hands).

Mine has never reboot WHILE I'm using it, it's sneaky about it. But I suppose I'd much prefer it reboot while I'm not using it than while I'm using it; I have yet to have it do a full reboot while using it.
Trying to set up a Delicious account.. yeah, that rebooted the Java VM. But only time I've made it reboot at all.
Hahah, damnit, it just rebooted after it went to sleep. I seriously think it has something to do with going to sleep. I've been sleeping it and waking it repeatedly on adb logcat and it won't crash. Figures.

I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.

isolated_epidemic said:
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
Click to expand...
Click to collapse
Actually not using any of those on mine.. I have Beautiful Widgets in ADW and Beautiful Widgets + Note Widget in WidgetLocker.. Not adjusting the backlight at all either, in fact I don't think I have at all since getting it now that I think about it.

I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.

mastroiani said:
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
Click to expand...
Click to collapse
I suspect it's a software thing, as it doesn't randomly reboot in use, it ONLY seems to happen going into standby, and I have YET to make it happen connected USB for adb.
You know actually, I think alogcat can log automatically now, maybe I should try that.. but it'd have to run for a day or so, as I only see this happen like twice a day at most.

Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!

wvcachi said:
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
Click to expand...
Click to collapse
I myself had not played with SetCPU at all. So had you in the past and set it to conservative, and switched it back, or you switched it from its defaults? Reminds me, per my observation that it never has rebooted while on AC or USB, was there a default profile when plugged in that it's set to ondemand vs conservative? This could start making some weird kind of sense. I'll try it, but using something called CPU Tuner since it's free..
EDIT: I looked on USB and on Battery, both times was conservative, so looks like that's the default... Does the Nook have an automatic switching utility like cpuspeed in it? Hmm.. /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is the file if anyone else wants to look.
BTW, has anyone on 1.0.1 auto-nooted etc not seen these random sneaky ninja power-off reboots? I swear mine waits until I'm not looking and reboots. I've only SEEN it do it once or twice, but in the last 5 or so days it's rebooted at least 10 times while powered off. Again NEVER while I'm using it, so I'm at least thankful for that. If it were rebooting while using it that would not be acceptable.
I have the Uptime Widget, kinda wished I had an uptime graph to see if there is a pattern.. I'm about 99% sure it never happens when plugged in AC or USB.
EDIT2: IT IS CLEARLY MOCKING ME. It just rebooted after I peeked at the governor files and let it idle to sleep.

I have the same random reboot problem since I upgraded to 1.0.1 and used auto-nooter. I only see it when it goes to sleep...or so I thought. This morning I heard it reboot and i hadn't touched it since last night. FYI, it was not plugged in when it happened. Thankfully it never reboots while in use.
Oh...ad i havent used any CPU clocking tools. Also...never saw this on 1.0. So weird but I am sure someone smarter than I will figure it out.
UPDATE- Just got out of the shower and while getting dresses...heard the Book reboot twice within a minute or two.
Wondering if its an app that is causing a fatal crash when it tries to update.
Sent from my Nooxus One using Tapatalk

I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk

rckymtnrfc said:
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
Click to expand...
Click to collapse
I've had one unexpected reboot today that I know of, I think this has helped, although I keep finding my Wifi turned off, even though this program I installed is only set to turn it off when the battery is extremely low. So I changed that profile and it hasn't turned itself off since, so seems to me maybe the battery reporting is a little wonky sometimes.
I've been watching, and I'll keep an eye out, but I think wvcachi is onto something.
BTW, the Nook has been primarily idle for the last 5 hours, just popped it on a few times to read an email, check on something, or see if it reboots so I haven't used it a bunch but it's lost a whopping 2% battery in that time. I also disabled the Phone stuff too, per this thread:
http://forum.xda-developers.com/showthread.php?t=883908

I am at 6.5 hours now....no rebooting so far.
Sent from my Nooxus One using Tapatalk

[Q] Torch problem

I have been having some issues with the torch/flashlight LED programs recently. I didn't used to have problems and prior to this when I used the HTC torch it had the same problem. When I used older versions of MIUI I didn't have this problem with flashlight apps that I had. But now with the most recent versions (since December or so I think when they added the torch button in the notification bar) I am having the problem again.
The problem when using a flashlight app (or the button in the notification bar) the light will turn on for about a second and then turn off. It will still show it off in the app or on the notification bar. If it does not do this it does one of 2 other things. It turns on and then after one second becomes brighter and then after about 1 more second turns off. On rare occasions in an app I can turn it on and it will stay on... but then when I try and turn it off there is usually a delay of a few seconds before it actually turns off. Then it is back to turning on for a second then off.
I had seen this same problem when I used the HTC Torch previously but it went away when using different ROMs and such so it makes me believe it is some kind of software problem. Seeing that the LED does seem to work and if I use the camera it seems to actually work properly with the program I am pretty sure there is nothing actually wrong with the hardware. Has anyone else seen this problem or know what could be causing it? Is there some way or some test program I could use to find what exactly is causing the problem? If someone has had this issue before... do they know how to fix it?
EDIT: I tried manually turning on the flashlight via "echo 1 > /sys/devices/platform/flashlight.0/leds/flashlight/brightness" and it turns the light on but then after about a second gets brighter then after another second turns off. When I did a "cat /sys/devices/platform/flashlight.0/leds/flashlight/brightness" it seems something changed it from the "1" which I wrote to the file to "127". Also, when I tried to "echo 0" to the file... the change did not stay. After doing the echo and then trying to cat the file it was still "127". I then tried to the torch app in the notification bar to turn it on and then off. After I turned it off via the application, I check the file and it was then set back to 0.
EDIT: I have witnessed the issue on 3 seperate Nexus One phones... surely someone else has had the same problem and possibly come up wit a solution.

you have to be careful with the flashlight apps esp with the high brightness setting. the LED is not designed to be on constantly on the nexus one and i have heard of people burning out their LED's from leaving it on too long both in normal and high brightness modes.
i have found out while using mine esp in high brightness if its left on too long it will overheat it and flicker. ever sense i seen mine do that i never use high brightness in fear of burning it out and when i use it in normal mode i try to keep its use as short as possible and i have not had it shut off on me sense. if yours is shutting off in normal mode then i'm afraid you may have already damaged it too much and that is why its turning itself off. thats my opinion anyways.
(if roms matter, i've always ran CM6 and now currently have been running CM7 nightlies and RC's

Frito11 said:
you have to be careful with the flashlight apps esp with the high brightness setting. the LED is not designed to be on constantly on the nexus one and i have heard of people burning out their LED's from leaving it on too long both in normal and high brightness modes.
i have found out while using mine esp in high brightness if its left on too long it will overheat it and flicker. ever sense i seen mine do that i never use high brightness in fear of burning it out and when i use it in normal mode i try to keep its use as short as possible and i have not had it shut off on me sense. if yours is shutting off in normal mode then i'm afraid you may have already damaged it too much and that is why its turning itself off. thats my opinion anyways.
(if roms matter, i've always ran CM6 and now currently have been running CM7 nightlies and RC's
Click to expand...
Click to collapse
Well... I would expect... if the LED was "burned out" then it shouldn't turn on at all. The simple fact that it turns on at all means the LED isn't burnt out. Also, I would suspect that to be the case if I had not witnessed it happen on a brand new Nexus One (Old one of a friends was replaced because it was stolen). Her's had to go in for repair (turns out a cable inside the phone going to the camera was loose) and I had reverted it back to an original ROM. Once it was reverted the LED didn't have problem. Another thing that indicates to me that it is a software problem is I have seen the exact same thing before on previous versions... and it went away when changing to other ROMs. Tonight I am thinking I will wipe and flash CM7 and test it with a light app and make sure... if that has the same symptom I will flash to a shipped ROM and test it. I am pretty sure it is a software issue though. I just don't know... what... is causing the problem.
EDIT: I also forgot to mention... when it was working properly... I never witnessed it overheat and flicker though I never had it on for long periods of time. One last thing, I only saw the symptoms after a flash to a new version. When it was working properly it was always working properly. When it was acting like this on a ROM it always acted like this.
UPDATE: I did flash to CM7 nightly and the torch app works perfectly as do other apps on the market. After being back on CM7 and with the advent of the theming engine for it... I think I may just end up moving back to CM for daily use. I would like to know if anyone else has run into this issue still and/or has a solution just in case I run into the same issue later. For now I think I will just chalk it up as a kernel/ROM problem... though it doesn't explain why others didn't have the same issue =/.

[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] Note 3 screen wont turn off

As stated, screen will not go off via timeout or power button tap. Power button is recognized and will bring up shut down menu like normal.
Device is rooted (thanks DG) and had been running well for over a week. Defrosted all apps from tibu in case I got over zealous but no better. A factory reset has not cleared it up either. Hoping the oneclick from the root package will correct the issue, but thats not until I get home later this evening.
Has anyone experienced / recovered from this issue?
Smart stay is turned off

I've had noticeable lag like a few seconds and sometimes I wonder if it's going to shut off but it always does. Better set a dark lock screen wallpaper to conserve your battery
Sent from my SAMSUNG-SM-N900A using xda app-developers app

I know this is kind of basic, but what is your setting here:
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!

3496255310
papashex said:
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
Click to expand...
Click to collapse
I'm having the same problem, I rooted through vroot.... what do you mean one click fixed it little my incite would be helpful....
thank you

Mine just did this, scared the hell out of me It also didn't go into deep sleep before it started. (Not rooted).
Pulled the battery, waited 30 seconds, plugged it back in.... same thing. Waited a few minutes, seems to have sorted itself out.
Scary....

This is definitely a software bug and it is related to the Headphone detection bug that people are having too (it's actually the same bug causing both issues). This happens to me quite often after I restart my phone. It's kind of like the phone hangs during the startup process. I've also noticed that the wifi/bluetooth status that was present before restarting the phone (i.e. whether they on/off) doesn't get applied until the bug sorts itself out.
For me sometimes this works: open an app like Chrome and then hit the home button to get back to your launcher. This works 95% of the time for me. I'm wondering if it has something to do with not having Touchwiz set as the default launcher.

I'm experiencing this same problem. If I don't manually turn the screen off by tapping the power button, the screen will not timeout.

phone randomly turning off

Hey all just checking to see if anyone has same issue, it is persisting beyond an update. I plug in for night and usually every morning screen is off. Takes me holding down power button for ten seconds for it to come back. Not sure if I'm rebooting phone and it was on or if it was off.

Same here. Got it 2 times. No idea!!!

Exactly same issue, happens every 3-4 days.

I have same problem. After last update, that hapoend 3 times already. I wonder why...

Guys you have to search before posting. Here is the topic i made a while back. Have had this issue since then and i notice it because i have the aod (always on display) and the screen disappears.
https://forum.xda-developers.com/ro...ly-to-hold-t3994037/post80721405#post80721405
Apps i suspect:
Blockada
Owntracks
Health mate
Spotify
Which of these are you guys using? Maybe we can deduce if its an app or some firmware issue.

From your list I'm using only Spotify. However I'm afraid that my phone was turning off even before I got this app. Will check anyway (already uninstalled it), and will let you know.
What I can say for sure is that my phone is switching off completely (not only display) as all my Bluetooth devices are disconnected straight away.
Hope we will find a solution for this issue!

it happened to me twice as well, having the phone for almost 2 months. It is a bit annoying and I dont understand why it happens. Among the list of these apps, I only have Spotify installed as well.

I dont have any apps from Your list. My phone turned off twice since last update, before that, for 1 month everything was ok. Now seems good aswell, we will see.

Seems like its none of the apps. My phone also completely disconnects from my devices and none of the buttons work (like double press volume button for camera). Have to hold the power button for a while and it starts up.

My Always on display is off
Random phone off was happening before the update and it's still happening after!
Also at times phone send to be so sluggish! 7gb+ram still available at that time.
North America 12gb/512gb.
All stock.
Sent from my ASUS_I001DC using Tapatalk

Ok, this issue together with the reported complaints of dust in camera lens has made me hold on the purchase of this phone.
Isn't there an official ROG II forum where all of you can complain so Asus can look into this issue maybe request dump files and resolve it once and for all?

baddar said:
Guys you have to search before posting. Here is the topic i made a while back. Have had this issue since then and i notice it because i have the aod (always on display) and the screen disappears.
https://forum.xda-developers.com/ro...ly-to-hold-t3994037/post80721405#post80721405
Apps i suspect:
Blockada
Owntracks
Health mate
Spotify
Which of these are you guys using? Maybe we can deduce if its an app or some firmware issue.
Click to expand...
Click to collapse
Well my doesn't randomly turn off and I'm using blockada if that sheds any light...
Also, I don't use Spotify

I have deleted all the apps. Literally done a reset to the factory settings to see what happen and this morning phone turned off again... That's really annoying.
I have found relevant topic on Asus forum: https://zentalk.asus.com/en/discussion/12715/rog-phone-2-12-512-freezes-and-auto-restart-problem
Looks like they are not fully aware of the problem....

Is there any update for this case?
I'm experiencing random hangs as well after updated the firmware to the latest. It reads my power button and will shows the options to reboot but the UI is totally not responsive, have to hard reset it Everytime.

Since factory reset everything seems to be fine, however it's just few days since I have done it.
09/12/2019 - I can confirm that after factory reset everything works fine. If anything change I will let you guys know straight away.
02/01/2020 - Annnnnd it's back... After few weeks phone started switching off again and tbh the whole thing intensified. Yesterday phone went off 9 times. On top of that when it's off it drains battery like crazy - 5mins and 20% is gone. Bluetooth doesn't work properly as well. I'm aware that others don't have any problems with ROGII, however I'm afraid that due to personal experience I won't buy Asus phone again and won't recommend it to anyone.

Rog phone 2 turns off automatically
Same problem here happened twice in 2 days everytime phone is off i have to hard restart to switch on the phone
Does anybody got any solution for this problem

Yes I have faced a similar issue since I have updated to android 10 beta. This happened once. I left my phone for charging and the screen blacked out. I had to press the vol up+dwn and power to restore the functionality. Strange.

Shahruq said:
Yes I have faced a similar issue since I have updated to android 10 beta. This happened once. I left my phone for charging and the screen blacked out. I had to press the vol up+dwn and power to restore the functionality. Strange.
Click to expand...
Click to collapse
What version of beta you use?
It happened to me twice in three months. The smartphone got stuck/freeze in standby mode: no response from the physical buttons or touch. I use the official android 9 rom.
I managed to restart it with the power button and volume up/down pressed for 15 seconds.

baddar said:
Guys you have to search before posting. Here is the topic i made a while back. Have had this issue since then and i notice it because i have the aod (always on display) and the screen disappears.
https://forum.xda-developers.com/ro...ly-to-hold-t3994037/post80721405#post80721405
Apps i suspect:
Blockada
Owntracks
Health mate
Spotify
Which of these are you guys using? Maybe we can deduce if its an app or some firmware issue.
Click to expand...
Click to collapse
No apps install in the list nd it randomly switch off my phone it's software issue

Mine started turning off after 1 minute of use. Couldn't stop it nor control it.
Managed to barely get the WhatsApp backup and then factory reset the device. So far things are ok. But setting up from scratch is a pain in the ass.
I suspect that I tried to enable twin apps on WeChat while being on Nova Launcher. That may have triggered something, But I'm not sure.