Last night, I decided to check out some of the new roms out for the droid 4 so I downloaded the avatar rom and tried it out. It worked fine except when I would lock my phone and put it into sleep mode, it wouldn't always wake up the screen when pressing the power button. The lights for the hard keys lit up, but not the screen. Then sometimes the screen would light up, but the touch screen wouldn't be active so I couldn't swipe to unlock. It usually takes between 5-10 tries until it finally works. I had the same problem with the AOKP rom as well.
I thought it might be the performance controls keeping the CPU too low when the screen was off and therefore having trouble waking it up so I set the minimum to 600 but that didn't help. Any ideas?
Also, slightly unrelated question but is there a way to turn off the transition animations for 4.2.2? I can't seem to find it :/
nuhusky4 said:
Last night, I decided to check out some of the new roms out for the droid 4 so I downloaded the avatar rom and tried it out. It worked fine except when I would lock my phone and put it into sleep mode, it wouldn't always wake up the screen when pressing the power button. The lights for the hard keys lit up, but not the screen. Then sometimes the screen would light up, but the touch screen wouldn't be active so I couldn't swipe to unlock. It usually takes between 5-10 tries until it finally works. I had the same problem with the AOKP rom as well.
I thought it might be the performance controls keeping the CPU too low when the screen was off and therefore having trouble waking it up so I set the minimum to 600 but that didn't help. Any ideas?
Also, slightly unrelated question but is there a way to turn off the transition animations for 4.2.2? I can't seem to find it :/
Click to expand...
Click to collapse
I have had similar issues with the 4.2.2 ROMs although not as often as you. It would happen to me maybe once a week. I would just hard reboot the phone when it happened. Not sure if it's an issue with the kexec kernel or what.
As for the transition animations I would assume they would be in the launcher settings somewhere.
Related
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??)
So on Monday I went out and got a shiny new Turbo. I'm loving it so far and hoping for root and or bootloader unlock eventually. This morning though something odd happened. For a period of about ten seconds my capacitive buttons quit working completely - no vibrate when I touched them, no nothing. The phone wasn't frozen or anything. Then they suddenly started working again. About five minutes later it did it again, but it hasn't done it since. Should I be worried? What should I do?
I'm having the exact same issue, seems to be random.
Ok I have the Moto Maxx and noticed that too... then I figured that in my case it happened because I was touching the screen with my palm while tying to reach for the capacitive buttons. The buttons stop working while you are touching the screen. Check if that is what is happening to you.
jfassad said:
Ok I have the Moto Maxx and noticed that too... then I figured that in my case it happened because I was touching the screen with my palm while tying to reach for the capacitive buttons. The buttons stop working while you are touching the screen. Check if that is what is happening to you.
Click to expand...
Click to collapse
I've even had it do that if there is any liquid on the screen...like maybe a few small drops of water after you just washed your hands or something like that.
Does the proximity sensor disable the buttons? Thinking that if the phone thinks it is near your face for a call, it might shut off the screen and buttons to prevent accidental presses.
Ekkoria said:
So on Monday I went out and got a shiny new Turbo. I'm loving it so far and hoping for root and or bootloader unlock eventually. This morning though something odd happened. For a period of about ten seconds my capacitive buttons quit working completely - no vibrate when I touched them, no nothing. The phone wasn't frozen or anything. Then they suddenly started working again. About five minutes later it did it again, but it hasn't done it since. Should I be worried? What should I do?
Click to expand...
Click to collapse
They will automatically dim and turn off when in a well lit area/room. If you are in a dark environment they will always be on.
Just hold the device under a lamp and watch buttons dim slowly off. Turn lamp off or go to a dark room and watch them illuminate back to life after 8-10 seconds.
Pretty standard, however, if they are going on and off constantly in the dark, than most likely a defective unit.
jfassad said:
Ok I have the Moto Maxx and noticed that too... then I figured that in my case it happened because I was touching the screen with my palm while tying to reach for the capacitive buttons. The buttons stop working while you are touching the screen. Check if that is what is happening to you.
Click to expand...
Click to collapse
I'm pretty sure this is what happened to me, after playing around with it I noticed my phone does the same thing. That's a load off my chest, I was a bit worried about it. thanks!
Screen pinning vs Long press for menu
Just a note, I recently discovered that if you have lollipop screen pinning enabled under the security settings and also the "Use long press for menu" setting enabled under display settings, they seem to conflict and cause all kinds of key lag with any of the capacitive keys. Must be because both utilize a long press of the recents/overview key. As long as you only enable one or the other it should be fine. Just thought I'd throw that out there.
I have had this problem too, it simply has to do with the fact that the screen is and capacitive keys are combined. You can use one or other, but not both. If you encounter this, just mess around on the screen for a few seconds and the keys should work again.
Clear cache. That usually fixed the problem for me.
Sent from my XT1254 using Tapatalk
Hello there,
I got my hands on a M7, which was fully stock and working. It has some minor scratches and damaged material here and there, though it worked fine, except for phone calls only being audible in speaker mode.
I flashed TWRP recovery and installed the latest nightly of Cyanogen mod (cm-12.1-20151005-NIGHTLY-m7). Though to prevent the custom recovery from being patched I unlocked the bootloader (Not sure if that was the solution, though).
It was all fine, until the screen dimmed, and I tried powering on the screen again by pressing the power button. Though it wouldn't turn on. I even tried setting on the option to turn on screen when connected to a power source, though it never powered on again. I also noticed a slight flash of blue light every now and then, and the screen feels too sensitive. It might register a press when you're just scrolling.
Could someone help me out with this? Of course I believe a hardware fix would be appropriate, but as how everything worked until the flashes, I believe it might be fixed with some software.
Any help is much appreciated.
Byrkoet said:
Hello there,
I got my hands on a M7, which was fully stock and working. It has some minor scratches and damaged material here and there, though it worked fine, except for phone calls only being audible in speaker mode.
I flashed TWRP recovery and installed the latest nightly of Cyanogen mod (cm-12.1-20151005-NIGHTLY-m7). Though to prevent the custom recovery from being patched I unlocked the bootloader (Not sure if that was the solution, though).
It was all fine, until the screen dimmed, and I tried powering on the screen again by pressing the power button. Though it wouldn't turn on. I even tried setting on the option to turn on screen when connected to a power source, though it never powered on again. I also noticed a slight flash of blue light every now and then, and the screen feels too sensitive. It might register a press when you're just scrolling.
Could someone help me out with this? Of course I believe a hardware fix would be appropriate, but as how everything worked until the flashes, I believe it might be fixed with some software.
Any help is much appreciated.
Click to expand...
Click to collapse
If you are talking about the screen not turning on (as opposed to the complete phone) Its a known bug of CM roms. The screen can't be turned back on when it was set to minimum brightness, or when the auto brightness set it to minimum. To avoid that, you'll need to adjust the brightness yourself instead of auto mode, avoiding the minimum adjustment. CM is known to be a buggy rom for the M7, you shouldn't have this issue if using a GPE or Sense rom.
alray said:
If you are talking about the screen not turning on (as opposed to the complete phone) Its a known bug of CM roms. The screen can't be turned back on when it was set to minimum brightness, or when the auto brightness set it to minimum. To avoid that, you'll need to adjust the brightness yourself instead of auto mode, avoiding the minimum adjustment. CM is known to be a buggy rom for the M7, you shouldn't have this issue if using a GPE or Sense rom.
Click to expand...
Click to collapse
Thanks for the info. I figured as much, I will try Exodus.
EDIT: I have tried Exodus, XenonHD and Dirty Unicorns. Though no success: none of them were able to turn on the display after it dimmed.
Non rooted, T mobile branded 3 month old note 8. No water damange, no drops etc.
Using chrome one miniute, set the phone down to watch a movie on my tablet, picked up the phone to check messages and boom. Screen is off. The phone works, I can even answer calls because I know where the answer button is on the screen, haptic feedback works, all indicator lights work. The phone screen remains off.
Tried a soft reset (tried hard reset too the best I could being I cant see the screen) and the phone seems to reset based on the vibration and indicator light patters but the screen remains off. It's as if a physical connection between the screen and the brains of the phone has been severed. Literaraly the weirdest thing that has happened to me in a decade of Android phone ownership.
Googled all the black screen issues with these phones and most of them are resolved with just a soft reset... some said that the phone is in it's lowest dimmed state and go to a dark room and i'll see it faintly and then can increase brightness... no luck...
Has anyone experienced this?
I would say it's a warranty job, just tried turning my brightness to zero and you can still see the screen.
I did have a similar problem on an old note that had root and custom rom though but I had somehow set the volume rocker to control brightness and it had lowered itself to minimum in my pocket
KEVIN88GT said:
Non rooted, T mobile branded 3 month old note 8. No water damange, no drops etc.
Using chrome one miniute, set the phone down to watch a movie on my tablet, picked up the phone to check messages and boom. Screen is off. The phone works, I can even answer calls because I know where the answer button is on the screen, haptic feedback works, all indicator lights work. The phone screen remains off.
Tried a soft reset (tried hard reset too the best I could being I cant see the screen) and the phone seems to reset based on the vibration and indicator light patters but the screen remains off. It's as if a physical connection between the screen and the brains of the phone has been severed. Literaraly the weirdest thing that has happened to me in a decade of Android phone ownership.
Googled all the black screen issues with these phones and most of them are resolved with just a soft reset... some said that the phone is in it's lowest dimmed state and go to a dark room and i'll see it faintly and then can increase brightness... no luck...
Has anyone experienced this?
Click to expand...
Click to collapse
Try pressing and holding Volume down and power button for 5 to 7 seconds to force power off, then try to boot to download mode Volume Down + Bixby + Power button and see if the download mode screen shows......if not then probably a bad screen.
Sent from my God Mode 8
Tried it......nothing.....warranty job it is.... Bummed to have some refurnished phone in exchange for a Brand new 900 dollar phone just a few months back?
KEVIN88GT said:
Tried it......nothing.....warranty job it is.... Bummed to have some refurnished phone in exchange for a Brand new 900 dollar phone just a few months back?
Click to expand...
Click to collapse
Yeah that sucks, i can imagine..... i too hate the idea of refurbished units being swapped for warranty....bs, should be brand new unit!
Sent from my God Mode 8
so I had it replaced under warranty through T mobile. Refurb phone will come in today. One quesion. Should I let the Tmobile techs do the data/settings transfer from old phone to new one or just do everything myself from scratch (which will obviously take longer).
This happened to my phone twice for the past month or so. (both in Nougat and Oreo - Non rooted) Black screen but phone seems to be responding -- I can receive calls and notifications etc -- And force reboot doesn't fix it. I've also tried drainging the phone when it first happened to me but doesn't work. HOWEVER, it gets okay so randomly. Like I just left it for couple of hours and it just worked when I hit the power button.
I did tried bringing the device to Samsung but what they did is to just manually upgrade/reset the software in their end which I could have done in my part but I just let them do it. They told me to come back if it happens again which is kinda BS.
I can conveniently say this is a Hardware issue. I will wait for it to happen again on my phone and request for a replacement. Phone is 4 months old when it first happened.
I have the same issue with blank screen but phone is working.
It started couple of weeks after i dropped my phone on the ground. There is black dot on my screen and broken glass but phone was working ok and was still pretty usable. But then it started:
Display works fine but when i switch display of, lock the phone or display switched because of its timer it didn come switch on... But phone works, i can use it with blank (black) screen.
I had to do force restart so the display will turn on with samsung logo and booting screen, and keep on till another switch of.
I was trying every setting (but no hard reset) and then i found a little hack:
When you turn on the "Always On Display" (AOD) function you can let the screen switch off or do it manually, wait for 1-2 sec and always on display will come up to the screen. Then when you press home button or lock button screen will swtich on normally. YOu can type pin and use phone witch screen working. But when you try to unlock from "AOD" with your finger or your eyes it unlock but with screen black.
So i was using it like this. everytime you need to wait second untill AOD comes up, but it was working fine.
Problem nu 2 is that now it stop working, AOD is working but when i want to switch screen on from AOD it shows black screen and phone is working on blind.
So everytime after my screen goes black or to AOD i have to unlock the phone blindly and "Force restart" it and have to keep waiting until boot, and then have to never let phone to screen of.
Its not usuable.
¨
Now what do you think? Is it hardware problem or software problem? Because screen is working but randomly. The black dot of dead pixels on the screen is getting slightly bigger in time (about 1 year) but its like 1.5cm round. Maybe this cause the problem? And why hack with AOD was working for half a year and then stoped working? There wasnt any updates right before, but i tried to install some apps (non display related) so ill try to uninstall them.
Hawe you got any idea if i can repair it on my own even if i loose the waterproofability?
Or can it be replaced for free if i have a warranty? (I dont have insurance)
Thanks for your tips guys.
Reprocrastinator said:
I have the same issue with blank screen but phone is working.
It started couple of weeks after i dropped my phone on the ground. There is black dot on my screen and broken glass but phone was working ok and was still pretty usable. But then it started:
Display works fine but when i switch display of, lock the phone or display switched because of its timer it didn come switch on... But phone works, i can use it with blank (black) screen.
I had to do force restart so the display will turn on with samsung logo and booting screen, and keep on till another switch of.
I was trying every setting (but no hard reset) and then i found a little hack:
When you turn on the "Always On Display" (AOD) function you can let the screen switch off or do it manually, wait for 1-2 sec and always on display will come up to the screen. Then when you press home button or lock button screen will swtich on normally. YOu can type pin and use phone witch screen working. But when you try to unlock from "AOD" with your finger or your eyes it unlock but with screen black.
So i was using it like this. everytime you need to wait second untill AOD comes up, but it was working fine.
Problem nu 2 is that now it stop working, AOD is working but when i want to switch screen on from AOD it shows black screen and phone is working on blind.
So everytime after my screen goes black or to AOD i have to unlock the phone blindly and "Force restart" it and have to keep waiting until boot, and then have to never let phone to screen of.
Its not usuable.
¨
Now what do you think? Is it hardware problem or software problem? Because screen is working but randomly. The black dot of dead pixels on the screen is getting slightly bigger in time (about 1 year) but its like 1.5cm round. Maybe this cause the problem? And why hack with AOD was working for half a year and then stoped working? There wasnt any updates right before, but i tried to install some apps (non display related) so ill try to uninstall them.
Hawe you got any idea if i can repair it on my own even if i loose the waterproofability?
Or can it be replaced for free if i have a warranty? (I dont have insurance)
Thanks for your tips guys.
Click to expand...
Click to collapse
If you're under warranty it will likely be a free repair, unless they find other damage. Like moisture damage.
As far as fixing it yourself, it's just about as cheap to have Samsung do it than it is to buy the parts yourself. It's $229 for Samsung to do it, and you'll maintain the water resistance rating.
same has happened to me
KEVIN88GT said:
Non rooted, T mobile branded 3 month old note 8. No water damange, no drops etc.
Using chrome one miniute, set the phone down to watch a movie on my tablet, picked up the phone to check messages and boom. Screen is off. The phone works, I can even answer calls because I know where the answer button is on the screen, haptic feedback works, all indicator lights work. The phone screen remains off.
Tried a soft reset (tried hard reset too the best I could being I cant see the screen) and the phone seems to reset based on the vibration and indicator light patters but the screen remains off. It's as if a physical connection between the screen and the brains of the phone has been severed. Literaraly the weirdest thing that has happened to me in a decade of Android phone ownership.
Googled all the black screen issues with these phones and most of them are resolved with just a soft reset... some said that the phone is in it's lowest dimmed state and go to a dark room and i'll see it faintly and then can increase brightness... no luck...
Has anyone experienced this?
Click to expand...
Click to collapse
This has just happened to my note 8 too. I was about to update it and had started it. set my phone down and picked it up and phone screen is black but can hear the haptic feedback.
I can only see the lock screen and the notifications. Everytime I try to unlock my phone I only get to see a glimpse of the notescreen and then the screen turns black. Even when I try to go to camera through the lock screen the screen goes black too. When I charge my phone it heats up so I haven't really charged it as well. Has this also happened to anyone? It seems as if the phone's sensitivity still works in all places but when I unlock it the screen just goes black.
I also have problem of freezings and always rebooting. Tried soft and hard resets/factory reset. Still same problem. This phone has hardware issue. Do not buy.
I realize this thread is quite old but I have this exact same issue now. I have managed to discover some other information by playing around with various settings which are noted below. To begin with, I was able to used the AOD hack posted above for a while but it no longer works. The only way I can get my screen to come back is with a soft reset - but as soon as the screen times out or i turn it off, it goes black, with or without AOD enable. All the on screen buttons still work as well as the haptic feedback - I just can't see anything.
Now on to what I have found:
One thing I have found is if I turn off adaptive screen brightness and crank the brightness slider to the right, when it goes black I can faintly see some of the buttons - enough that I can turn the phone off or restart it from the power menu (If I switch the default setting to night that also helps to see the buttons a bit better). Also, if I enable night mode I can also see the brightness slider faintly but when I slide it left, it just makes the screen completely black and when I slide it right, it only returns it to the very faint brightness level.
So at this point I am stuck. To summarize the issue:
1. When the screen either times out or turns off, it is still "alive" but goes black. It will not return to normal brightness.
2. Turning off adaptive brightness and cranking brightness slider to right allows you to see faint buttons after screen times out but won't return to normal brightness.
3. Enabling night mode helps to see the faint buttons, in particular the brightness slider a bit better. However the screen still cannot return to normal brightness.
4. The only way to get the screen back to full brightness (albeit temporarily until the next timeout) is to turn off the phone or reset from the power menu; or soft reset holding volume down + power simultaneously.
Hopefully someone else has figured out a way to recover this. I am on Android 9 with Samsung UI 1.0
Phone is completely stock, never rooted and completely out of warranty.
After upgrading to Lineage OS 15.1, I realize that if I have screen lock set to pattern, then it is extremely hard to unlock when the screen has been off for a while. The screen will stay black while when I'm holding power button the phone will vibrate as if I'm calling power menu. This black screen can last at least one minute. I also set long press to open flashlight when screen is off and that doesn't work. Those symptoms makes me believe that the phone is awake, yet for some reason can't get GUI rendering. Sometimes even when I enter the correct pattern and the animation moves dots and timer away, I can still draw unlock pattern on the hiding unlock dots, and phone will vibrate in a very laggy manner.
Currently I'm running with no screen lock as even "swipe" still cause the unlock process to be very painful. Is this a known issue for LOS or is there a way to fix it? I saw a post says the battery should be replaced if phone is laggy. Is that a possible cause?
LolitaPlus said:
After upgrading to Lineage OS 15.1, I realize that if I have screen lock set to pattern, then it is extremely hard to unlock when the screen has been off for a while. The screen will stay black while when I'm holding power button the phone will vibrate as if I'm calling power menu. This black screen can last at least one minute. I also set long press to open flashlight when screen is off and that doesn't work. Those symptoms makes me believe that the phone is awake, yet for some reason can't get GUI rendering. Sometimes even when I enter the correct pattern and the animation moves dots and timer away, I can still draw unlock pattern on the hiding unlock dots, and phone will vibrate in a very laggy manner.
Currently I'm running with no screen lock as even "swipe" still cause the unlock process to be very painful. Is this a known issue for LOS or is there a way to fix it? I saw a post says the battery should be replaced if phone is laggy. Is that a possible cause?
Click to expand...
Click to collapse
This isn't a known problem.
From what did you upgrade?
Which build are you using?
Did you do a clean install?
Which gapps are you using.
Do you have Expanded Desktop enabled?
Elektroschmock said:
This isn't a known problem.
From what did you upgrade?
Which build are you using?
Did you do a clean install?
Which gapps are you using.
Do you have Expanded Desktop enabled?
Click to expand...
Click to collapse
I was using Stock Android before, but I fully wiped everything before I install.
15.1-20180508-NIGHTLY-shamu
Yes.
I got my GApps from Open GApps, but didn't remember which variant but most likely nano.
I actually have this enabled. I'm gonna disable it and see how that works.
After turning off Expanded Desktop the issue seems to be gone. Though when turned on again after some times the lag is still somewhat exist.
there's a Xposed module fix for this http://repo.xposed.info/module/fr.merams.r.deepscreenoreo