I've been running PACman for the past few months without any major issues I couldn't resolve.
Today as I made a call the display froze, I could see the notification bar animations eg circle battery, still working. I reset it. After work using poweramp, same thing, display wouldn't respond yet music was still playing. If I lock the XT and try to unlock it, the screen is awake yet unresponsive.
Anyone else experienced this? I've not made any changes.
Any logs that will help?
Sent from my Xperia T
No one experiencing this? It was fine all of yesterday but stopped responding this morning as I stepped out the house and woke it up.
Sent from my Xperia T
Related
So within the last two days I have been having problems with my phone coming out of sleep mode, just to give a little more information when i hit the power button to turn the screen on and go to unlock it, the screen doesn't respond and fades back out. The task bar stays on at the top for about 10 seconds as well. SOMEONE please help lol. I've only had this phone for about a week and this is very frustrating. (phone is rooted btw)
Thanks in advance
If you're having touchscreen malfunctions, then you should exchange it. You've had it one week, you can do that. I will say though, the screen timeout for the lock screen is 5 seconds long. As in, when I wake my phone if I don't touch it, five seconds later it fades out again. It sounds like you're having more serious issues however mentioning the notification bar staying on the screen like that. I recommend you look into exchanging it. Make sure you restore it and unroot it before you do that.
Unroot thread
I was just wondering if anyone had these issues, it didn't appear to do it the first couple days I had it, and I've installed a ton of apps since then. I un-installed some things today and it seems to have subsided, i'm still wondering if anyone else has had problems like this. It may have had to do with a task manager, but i can't be sure. Any insight is appreciated.
So, I downloaded and launched it perfectly... everything so far i tried is working fine except the lock screen... Some times when i press the Cancel key the button lights lid up but there is nothing on the screen and sometimes it appear the lock screen but nothing happen....
Do someone have any solution to this...
Thank you.
I have the same problem. I have been reading that possibly going back to an older kernel / roofs fixes this problem but have not seen and confirmed reports.
Can anyone confirm this and what version?
Thanks
Same problem at me. Both builds are running very fine for some tine but after that are running slow.I don't know why. Maybe is somehow related with the lockscreen problem?
I have this problem as well i get lucky if i manage to move passt the lock screen and the OS runs really slow it takes like 20 seconds just to open the app screen and the app screen laggs like no to morrow how come so menny ppls can get it to run just fine but i cant it makes me sad face
+1 one for me... I have got a TOPA100, it's almost impossible to wake up the device, sometimes the lockscreen is visible, but it's impossible to move the unlock slider. Usually I need about 10 times and something around 5 Minutes to wake up the device.
Same problem here, would be great if this can be fixed...
RaZz0r12 said:
I have this problem as well i get lucky if i manage to move passt the lock screen and the OS runs really slow it takes like 20 seconds just to open the app screen and the app screen laggs like no to morrow how come so menny ppls can get it to run just fine but i cant it makes me sad face
Click to expand...
Click to collapse
For me it's the same and the battery runs only for one hour, I think a (system?)process is running with 100% CPU time. I am new to android, so I don't know where to look.
Same here on an AT&T Pure. Sure would love to get this fixed however I'm reasonably noob to the Android world (not completely novice to linux in general, and I have successfully flashed my AT&T TyTN II thanks to this site.) Fixing this would be a huge help!
Thanks
More specifically on my device I encounter. The following:
- Turn screen off via end button.
- Turn on screen via call button.
HW button lights come on for a few seconds then cut themselves off.
Screen does not turn on at this point.
- Turn on screen via call button again
- Screen comes on with HW button lights
about half the time screen is unresponsive and will not all me to unlock with swipe of finger
Other times will accept input and unlock to the home screen
When unresponsive repeating entire process above will likely allow me to unlock successfully.
Thanks!
Sent from my AT&T Pure using XDA App
same
my screen never wakes up
end up using soft reset to windows mobile
(it could be something to do with startup??)
I've been having a bit of a strange problem lately - sometimes my phone won't enter the lock screen. I'll turn the screen off, or let it go to sleep, and then when I go to turn the screen back on again (could be hours later), it goes directly to the home screen, and never see the lock screen. This makes it very easy to pocket-dial, or launch apps - my pocket started blaring music one day.
A restart seems to fix it for a little while, but within a day it will start doing the same thing, and I don't think I saw the lock screen at all yesterday. Does anyone have any idea what might be causing this? It started a couple months ago, but it seems to be more frequent now.
I am currently running Motorola Milestone, CM7 (kabaldan's beta with swap enabled). It was also happening some with CM7.2.1
Thanks in advance!
Anyone have any ideas?
Another interesting point is that after NOT seeing the lockscreen, and then playing around on the phone, I'll open one of the apps (say the browser), and THEN it will drop into the lockscreen. So right in the middle of doing stuff, it will make me have to unlock the phone. Can be a little frustrating.
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
JimSmith94 said:
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
if youre using lightflow id suggest wiping the data in it and resetting your notification settings. it does tend to override the system so i can see that screwing with the duration of the notification, and starting fresh usually solves most problems
i have mine set to wake the screen for SMS but not MMS. it creates similar problems with the screen
Thanks for the info. I tried just toggling the screen on settings on and back off for all of the Light Flow apps, and it seems to have fixed my screen turn on problem, at least for now.
Sent from my Nexus 6 using Tapatalk
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
A.Ahmed79 said:
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
Click to expand...
Click to collapse
LightFlow fixed my screen problems, but it was just a coincidence that I installed Marshmallow and my sounds got cut off around the same time. I'm still looking for a solution to that issue. Similar to you, if my screen is on, the notification sounds work correctly. If the screen is off, they get cut off.
My device is completely stock.
I have noticed that the screen will randomly wake on its own to the lockscreen.
If i get a notification it does this however will also do it with nothing apparently new having happened.
Any ideas?
I noticed this before on my P9-L:ite but haven't seen it yet on my P10. In my case, I believe it happens when the phone loses or regains internet connectivity. Since networks are kind of spotty where I am, it happens somewhat often.
i have the p10 plus and i have the same situation...... any solutions?
Mine only does this when receiving a snapchat from someone. Could it be app related?
My one week old P10 plus has the same problem. It happens when I lock the phone while any app is active (I tried with a few apps). However, it doesn't happen when I lock the phone while the home screen is active.
Has anyone found a solution?
Still interested in this–
started happening to me a few days back aswell; I noticed the change after shooting some balls with my phone in the pocket, screen facing the skin. At some point the phone got insanely hot. When I picked it up all sorts of s*** happened, as if my thigh was able to make touch inputs through the pants? Notification center / quick settings were all toggled randomly. Flashlight, geo location and hotspot were switched on whereas Wifi and Bluetooth were off (which is unusual). And the camera was running with fully brightened screen, which I think was main reason for the heat.
I wasn't sweating extensively; meaning the phone wasn't wet in my pockets or something–
And I don't know if the random screen wake up enabled my thigh to make the touch inputs or of something else happened which from then on let the screen randomly wake up– chicken and egg, you know :F