[Q] CM Crashing Issues - Motorola Atrix HD

Has anyone else noticed problems with CM crashing on their Atrix HD? I have been running CM on mine since September and have noticed the same problems in both CM 10.2 (epinter) and CM 11 (official). I never noticed any problems with the stock software. I have identified at least two different types of crashes.
Type 1 typically happens overnight when plugged into a charger (though less so with more recent builds) or when the phone is idle in my pocket. There is no notice the phone has crashed though sometimes if it happens in my pocket the phone seems to warm up somewhat. When I pull out the phone and press the power button I get nothing at all. This requires holding down the power and volume buttons for an extended period to force the phone off and then restarting it.
Type 2 typically happens when on an active phone call, though it can happen other times when using the phone as well. This involves the phone crashing and immediately going into a reboot (red M on the display as soon as I pull the phone away from my head).
I also have a less serious issue where when I press the power button to turn on the screen it will occasionally display the lock screen but refuse to take any touch input. I can usually get things to work by pressing the power button a few more times to turn the screen off and on again.
Just yesterday I switched to the new unified builds and have not seen all of these happen yet but I have definitely seen a type 2 already. Just wondering if these problems are widespread as I don't see them discussed a lot and if there's anything I can do about them.

Nothing? Am I really the only one having these problems? For the record I have now seen both types of crashes on the unified build.

May be you can try to flash stock rom:silly:

Try flashing the latest Validus ROM. I have been using version 4.3, which is based on KOT49H and it's been very stable with no crashes.

Is there a crash log that I can capture and review after a crash?

BenFranske said:
Is there a crash log that I can capture and review after a crash?
Click to expand...
Click to collapse
/proc/last_kmsg - kernel log from before the last reboot
/data/dontpanic/apanic_console - last kernel crash log
If the kernel crashed and the crash caused the last reboot, the content of both will be the same.
Regarding the non-responsive touchscreen after pulling the phone out of your pocket - it is usually caused by static electricity build-up. Subsequent turning off/on of the screen usually invokes ESD recovery procedure in the touchscreen circuit and the touchscreen starts to respond again.
It's very common on wide variety of phones (including e.g. iPhone). Change your trousers or use a belt case .

kabaldan said:
/proc/last_kmsg - kernel log from before the last reboot
/data/dontpanic/apanic_console - last kernel crash log
If the kernel crashed and the crash caused the last reboot, the content of both will be the same.
Click to expand...
Click to collapse
Great, I'll check those out the next time I have a crash. I am thinking there will almost certainly be some useful information for the second type of crash where the phone actually reboots itself. I am less optimistic that there will be any information when it simply locks up and I'm forced to reboot it by holding power and volume down buttons.
kabaldan said:
Regarding the non-responsive touchscreen after pulling the phone out of your pocket - it is usually caused by static electricity build-up. Subsequent turning off/on of the screen usually invokes ESD recovery procedure in the touchscreen circuit and the touchscreen starts to respond again.
It's very common on wide variety of phones (including e.g. iPhone). Change your trousers or use a belt case .
Click to expand...
Click to collapse
Thanks for the helpful information there too. My sister has forbidden me from wearing belt cases for at least the last 10 years but it's at least nice to understand what the problem is!

Crash Logs
Sorry it took me a while to get back to this. I've attached a few crash logs that I captured last month. I have updated the OS several times since then but I'm still experiencing both of the types of crashes I originally mentioned. Any assistance in interpreting the logs is appreciated!

Any ideas about what might be causing these crashes and reboots?

Am I really the only person with these issues? How can that be?

Related

[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 ?

[FAQ] - Known bugs & issues for the HTC ONE (M7)

Like every other device on the market, the HTC ONE is not perfect, both at device and software levels it is likely that some glitches and hitches will be discovered, this is exactly the place to report those bugs. It is important here to distinguish between a bug from the device and a bug from an XDA ROM developer, the latter case must be reported in the appropriate topic and not here.​
Confirmed or Known BUGS:
BUG : I find that on the odd occasion my back button or home button becomes dead.
SOLUTION : Have a read HERE​
BUG : Beats causes a hissing background noise, most noticeable at low volumes.
SOLUTION : Some say disabling WiFi and re enabling it solved their issue.​
BUG : Bluetooth streaming audio issues, audio keeps cutting out.
SOLUTION : Some has solved this by disabling the energy saving options or simply turn OFF WiFi. To discuss this issue click HERE​
BUG :
SOLUTION :​
BUG :
SOLUTION :​
Post your bugs and issues and if they get confirmed frequently I will add them to this list.​​
I find that on the odd occasion my back button or home button becomes dead. This usually fixes itself immediately when shifting to another screen or something. A minor inconvenience.
Other than that I've not experienced anything else.
I find that on the odd occasion my back button or home button becomes dead. This usually fixes itself immediately when shifting to another screen or something.
Click to expand...
Click to collapse
Also beats causes a hissing background noise, most noticeable at low volumes.
Xperia23 said:
I find that on the odd occasion my back button or home button becomes dead. This usually fixes itself immediately when shifting to another screen or something. A minor inconvenience.
Other than that I've not experienced anything else.
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?t=2231832
Thank you guys, OP updated.
the cursor jumps into false positions, when i drag it to one. (keyboard)
Sometimes my keyboard disappears, when i was writing and no i didnt pressed back or anything like this.
o2 v1.27 firmware
I had a weird issue in the car the other day
I was using the USB plugged into a Fiat 500 which has the Blue & Me system. I wasn't particularly bothered about having sound through the speakers, I just wanted to charge.
The stereo turned on anyway, and I was having random directions given through the stereo, with the Highlight Video music in between!! And then the ACTUAL directions coming through the phone speakers. I just turned the stereo off but it was really weird
Martin
I've had problems with random restarts and WiFi not connecting/WiFI settings freezing. Not allowing WiFi to be switched off during sleep seems to have cured it.
HTC One M7 speaker
I got my new HTC one the othe day from Harvey Norman and I have noticed that the bottom one of the two speakers cuts in and out and if you press on it then it works, but this is for all audio has anyone had this issue or know why it is happening?
Thanks
I got my HTC One last week and the wifi signal is really weak. When I am at 5mt from the hub (virgin media) I bearly have a signal.
My boyfriend's Xperia Z (with known wifi issues) has more signal at the same distance.
Anyone else experiencing this?
Phone in pocket after call
I am surprised no one has reported this annoying bug:
1) Have the phone in the pocket
2) Listen to music via the provided headphones (same if you use bluetooth)
3) Someone calls you and you answer via headphones button
4) After you or the other party hangs the phone, the phone turns on in the pocket.
VERY annoying!!! Please report this bug to HTC (I already did)
Otherwise I just LOVE this phone!!!
Problems charging phone and file transfers.
Ive had my HTC One for just over 2 months now. Havent had any issues besides the back button not responding. But just the last few days out of the blue, i am unable to charge my phone using the provided htc micro usb cbale that came with the phone to charge my phone. Keeps saying to use supported cable or doesnt detect my phone at all. It wont even charge through the wall power point using the adapter and cable provided. Ive attempted using other micro usb cables from previous devices and still no luck. Only way to charge my phone is using the extend battery pack.But have to restart my phone before charge otherwise it wont detect usb connection.
I also unable to copy and transfer files from my phone to pc also due to the usb cable and detection issue.
Has anyone else here experienced the same issue?
If so,how did you resolve the issue?
ive contacted HTC Support and still waiting on a response.
xqlusive84 said:
Ive had my HTC One for just over 2 months now. Havent had any issues besides the back button not responding. But just the last few days out of the blue, i am unable to charge my phone using the provided htc micro usb cbale that came with the phone to charge my phone. Keeps saying to use supported cable or doesnt detect my phone at all. It wont even charge through the wall power point using the adapter and cable provided. Ive attempted using other micro usb cables from previous devices and still no luck. Only way to charge my phone is using the extend battery pack.But have to restart my phone before charge otherwise it wont detect usb connection.
I also unable to copy and transfer files from my phone to pc also due to the usb cable and detection issue.
Has anyone else here experienced the same issue?
If so,how did you resolve the issue?
ive contacted HTC Support and still waiting on a response.
Click to expand...
Click to collapse
Sounds like you have accidentally bent some pins in the connection, potentially hardware not software related. I'd return for exchange.
2G connection issues
I have no idea whether its my ONE's problem or of the connection provider........ I cant use my 2G connection, it connects and disconnects at its will........Is there any way to test whether my ONE has any problem?
Strangeness with touch screen sounds
I may be the the only one.... but I like a click sound when the touch screen is presssed for a command. This works alright on my Sensation (pyramid) but not on my new HTC (M7).
There is sometimes a very very faint noise about a second or more after touching the screen for a command, kind of a delayed reaction? Anyway no amount of tweaking volume controls or using any sound mod produces a decent loud click sound. I revert any tweaks after experimenting with them.
Setup; HTC M7ul - ARHD ROM (12 currently)
Any information on this would be gratefully received!
This has been annoying me for the past week...
When I make or receive a call people tell me that they hear me far away. People cant tell its me on the phone! Gonna try to clean the speakers with a toothbrush but this phone is fairly new, bought it in September...
Push Bug (Whats app, sms), htc stay in standby
Hey,
I'm new here and i hope, this is the right forum for my problem
I bought me a htc one a few days ago, and i've already root it, unlocked the bootloader, set it s-off. my recovery tool is twrp-2.6.3.3, and i have the ViperOne 4.3.0 with ElementalX-m7-10.10.1. for the rights management i use LBE_Security, exactly this Version: LBE_Security_RC_5.1.5446_A1_EN_VI_1st_12.20.2013.
Sometimes, 2-4 times/day, if i write with somebay via sms or whats app, and my handy is in standby and i get the message, my handy vibrates and the LED blinks green, and when i try to unlock it, with double2wake or logo2wake, my handy vibrates, but my display still is black, like it is still in standy. Music works, i can turn the volume higher or lower, and i can keep klicking the power button or double2wake or logo2wake, but my display didn't react. It only vibrates, wenn i click use double2wake or logo2wake. i have to click the power button and the lower-sound button to reboot my handy.
First i thought, maybe it is the kernel, because i used undervolt 800 and max cpu 1890mhz, so i install viper new and the kernel new, but without undervolt etc., everything stock. But the bug is still there. i have the same bug, if i start the camera app and close my htc via the power button, but without closing the camera app, the bug is there, too. this is something i can live with, but not the problem with push messages.
And i don't know how to contrain the apperance of the bug. yesterday i installed everything new, and i install lbe security master, too, but i think, i forgot to give him superuser right, because today apps pushed me things, but they weren't allowed to do this. maybe it has something to do with the bug, but today i realised it and set lbe as a superuser and then the bug appeared again. before that the bug didn't appeared. maybe it was coincidence, i don't know.
all i know, is that the bug has something to do with sms and whats push, and i'm not 100% sure, but i think it's not the fault of the kernel elementalX. Maybe it's LBE or Viper Rom's fault, or may something else.
Do somebody please help me? This bug is very annoying me and i don't know android very well, it's my first android phone.
And excuse me for my bad englisch, i am from Germany and i wasn't good in englisch in school
thepate94227 said:
Hey,
I'm new here and i hope, this is the right forum for my problem
I bought me a htc one a few days ago, and i've already root it, unlocked the bootloader, set it s-off. my recovery tool is twrp-2.6.3.3, and i have the ViperOne 4.3.0 with ElementalX-m7-10.10.1. for the rights management i use LBE_Security, exactly this Version: LBE_Security_RC_5.1.5446_A1_EN_VI_1st_12.20.2013.
Sometimes, 2-4 times/day, if i write with somebay via sms or whats app, and my handy is in standby and i get the message, my handy vibrates and the LED blinks green, and when i try to unlock it, with double2wake or logo2wake, my handy vibrates, but my display still is black, like it is still in standy. Music works, i can turn the volume higher or lower, and i can keep klicking the power button or double2wake or logo2wake, but my display didn't react. It only vibrates, wenn i click use double2wake or logo2wake. i have to click the power button and the lower-sound button to reboot my handy.
First i thought, maybe it is the kernel, because i used undervolt 800 and max cpu 1890mhz, so i install viper new and the kernel new, but without undervolt etc., everything stock. But the bug is still there. i have the same bug, if i start the camera app and close my htc via the power button, but without closing the camera app, the bug is there, too. this is something i can live with, but not the problem with push messages.
And i don't know how to contrain the apperance of the bug. yesterday i installed everything new, and i install lbe security master, too, but i think, i forgot to give him superuser right, because today apps pushed me things, but they weren't allowed to do this. maybe it has something to do with the bug, but today i realised it and set lbe as a superuser and then the bug appeared again. before that the bug didn't appeared. maybe it was coincidence, i don't know.
all i know, is that the bug has something to do with sms and whats push, and i'm not 100% sure, but i think it's not the fault of the kernel elementalX. Maybe it's LBE or Viper Rom's fault, or may something else.
Do somebody please help me? This bug is very annoying me and i don't know android very well, it's my first android phone.
And excuse me for my bad englisch, i am from Germany and i wasn't good in englisch in school
Click to expand...
Click to collapse
Sounds like you've set your minimum frequency/screen off to too low, increase it to around 800Mhz and see whether you face the same problems again.
Sent from my iPod touch using Tapatalk
thepate94227 said:
so i install viper new and the kernel new, but without undervolt etc., everything stock. But the bug is still there. i have the same bug, if i start the camera app and close my htc via the power button, but without closing the camera app, the bug is there, too.
Click to expand...
Click to collapse
There's a fix for the camera bug in Venom Hub/Addons/Other
Thank you for your answers
@spiralOut
Thank you, this add-on fixed the camera bug, I hope, it fix the other too
@n1234d
Do you mean the undervolt option during the elemtalx kernel installation? Because first I choose 800kHz, now I choose stock, I think the stock is higher than 800, right? And the bug still appeared.
And what I forget to say: I used the swift option from HTC, that i can write with swiping on my keyboard, maybe this has something to do with the bug, now today I deactivated it.

Touchscreen problems

hey,
since one or two months i have some troubles with my touchscreen. Randomly it starts to press something that i didn't touch and when i stop touching the screen, the system touches from alone. mostly opening google now by swiping up the home button. it also types thigns in whatsapp or so. Sometimes when i turn on the phone the touchscreen doesn't respon. all those problems are solved when i turn off the screen for 5 secs and turn it on again. i am running eXistenZ v3, i also tried some aosp 4.3 roms and had the same problem.
Any idea ?
EDIT: because the problem is solved as soon as i turn of the screen and on again i am not sure if it is really a hardware problem, is it ?
zFr3eak said:
hey,
since one or two months i have some troubles with my touchscreen. Randomly it starts to press something that i didn't touch and when i stop touching the screen, the system touches from alone. mostly opening google now by swiping up the home button. it also types thigns in whatsapp or so. Sometimes when i turn on the phone the touchscreen doesn't respon. all those problems are solved when i turn off the screen for 5 secs and turn it on again. i am running eXistenZ v3, i also tried some aosp 4.3 roms and had the same problem.
Any idea ?
EDIT: because the problem is solved as soon as i turn of the screen and on again i am not sure if it is really a hardware problem, is it ?
Click to expand...
Click to collapse
I was just about to post with the same issue!
I replaced the screen and back cover on my Xperia Z back in August and it was running issue free for 2 months but after the update last month to 4.2.2 I started having serious issues with touch screen.
Random inputs, no response to touch, looping homescreens and random apps opening and worse.
I am torn between a hardware issue?
As when the USB cable is connected the problem seems to gone so I think there may be a slight voltage leak screwing with the screen?
What is the best way to ensure that it is not a ground/voltage leak issue?
Or
Or because the issue cropped up almost immediately after the last Sony update, is there a chance it could be a software issue?
I am running on Stock 4.2.2 and any advice will be much appreciated
I have noticed yesterday that my Z's screen keeps pressing a certain spot randomly. Its by the O / P when i use the onscreen keypad. I opened the note app and drew lines, and there is an actual break in the lines when i draw in that area. This happened so sudden. I didnt drop my phone or anything. I just noticed it while typing that the letters started to get jumbled.
I have the same issue but only on certain kernels, I'm using that XZK "Stock kernel" with dual recovery and it's fine now (Note: This kernel only runs on Sony roms) Also, not sure if it's related but if i leave my phone to charge over night, ill turn the screen on and the touchscreen won't respond at ALL unless i hard-reset...
---------- Post added at 01:10 PM ---------- Previous post was at 01:09 PM ----------
banie01 said:
I was just about to post with the same issue!
I replaced the screen and back cover on my Xperia Z back in August and it was running issue free for 2 months but after the update last month to 4.2.2 I started having serious issues with touch screen.
Random inputs, no response to touch, looping homescreens and random apps opening and worse.
I am torn between a hardware issue?
As when the USB cable is connected the problem seems to gone so I think there may be a slight voltage leak screwing with the screen?
What is the best way to ensure that it is not a ground/voltage leak issue?
Or
Or because the issue cropped up almost immediately after the last Sony update, is there a chance it could be a software issue?
I am running on Stock 4.2.2 and any advice will be much appreciated
Click to expand...
Click to collapse
It might have even been a corrupt update, if you run windows go onto the sony application and get it to RE update your phone see if it fixes, it might. And if it does, yay. if not, then atleast you've ruled that out, right?
Well I noticed a small distortion in the screen on a white background in the area that my screen was experiencing random touches, and today I pulled my phone out of my pocket....and 4 cracks spread all over my screen....cant use the touch screen now have to look to order a screen

Strange behavior from Nexus 6 Display

My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
So weird, but same thing has been happening to me the past few days. But I have a justified cause. It started immediately after installing Franco Kernel.
Sent from my Nexus 6 using Tapatalk
queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Pkt_Lnt said:
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Click to expand...
Click to collapse
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
I've since flashed stock pn, and now elementalx. It's not acted up yet. Seemes to be a better performance kernel. We'll see how battery is. Sorry to hijack your thread!
Sent from my Nexus 6 using Tapatalk
queensgate555 said:
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
Click to expand...
Click to collapse
Well, so much for "scientific testing" and wishful thinking.....didn't take long to eliminate the wristwatch, now to fix the problem.
.

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.

Categories

Resources