It doesn't do this every time, but quite often and it seems to be random as I can't make it happen by doing one thing in particular. So, I used the phone for whatever, and then put it down, wait for the screen to go off and then in between the screen powering off and the always on display coming on, I get what you see in the photo below, and also in the bottom left corner in tiny writing, it says something about screen powering down and then something else that flashes on too quickly to read.
What do you reckon? Thanks.
Apologies for the screen protector, not got round to fitting the Whitestone dome yet.
I tend to get that whenever I open the keyboard for the first time after opening an app like WhatsApp or Snapchat. I don't get it when turning off.
I also get it when I press the middle button to go home from within an app.
But then again, I also have the taskbar to swipe up whenever I need it, so I'm not sure if this is relevant to me.
I.e I don't have the taskbar set to be static
Related
XDA-Dev:
I hope this finds you in high spirits and good health. Just a day ago my phone started acting peculiar regarding the lighting of the touchscreen.
Firmware: 1.6 // Build: DRC83 // Rooted: No
Damage: Slightly scratched hard plastic from dropping 2-3 times. Otherwise, outwardly pristine
Upon purchasing the phone, I immediately noticed that the screen would creak if it was pressed on the bottom right hand side (by the send button). The right side of the screen also protrudes slightly higher than the left when in the open position. I have owned the device for about 7-8 months now and have noticed that on the rear, when in open position, there is a scratch where the sliding mechanism moves. The paint is stripped and the underlying metal is displayed in those areas. And now on to the issue at hand:
When the phone is closed (touchscreen only):
- When pressing MENU, or any key that would normally illuminate the screen, this does not happen. The screen stays dim, yet the lights on the buttons bellow it brighten.
- If I slide out the keyboard while the screen is supposed to be on (meaning the buttons are lit up), nothing happens.
When the phone is open (keyboard presented):
- And the screen is off, if I press MENU, the screen comes right up with no brightness issues.
- At this point, if I close the keyboard, the backlight disables itself. The screen is NOT completely blank. If I reflect the light of the room off of it, I can just barely make out that it is indeed displaying whatever task it was that was open, but if I were in a dark room, there would be no chance of recognising what is being presented.
- Continuing from above, once the screen's backlight is disabled and I reopen the keyboard, it does not turn back on. I must turn off the screen and turn it back on for the backlight to resume normal functioning.
One would think that if the issue lies in a loose wire that once the keyboard is extended that the backlight would regain normal functioning. Because this is not happening and that it is only working under certain circumstances, I cannot accurately ascertain whether this is a software or hardware problem.
Attempted remedies:
- Soft reset (both rebooting the phone by powering off and on and by going into the reset menu)
- Hard reset (by going into the reset menu and hitting ALT+W, etc)
Neither of these attempts succeeded in restoring functionality of the backlight. I've also search high and low through the settings, but see nothing other than 'Brightness' under 'Sound & Display.'
It may be noteworthy that I have the paid application 'Power Manager' installed. Though, perhaps not since this issue was still occurring AFTER the factory reset when no foreign applications were installed.
If you require any additional details, feel free to give a reply with any questions. I'm sincerely hoping I don't have to deal with T-Mobile or HTC to have this repaired. Any tips, ideas or possible solutions would be greatly appreciated!
Regards,
Ian
Update on issue:
On the way home from work, as the battery was on it's last leg (less than 10%), I turned off the screen while the device was in the open position after finishing a text. Upon attempting to re-activate the screen, it would not do so. As always, the side buttons lit up, but the screen was blank no matter what I did. I could hear the vibration from receiving texts and the red 'omg I\'m dying LED' was still flashing, so the device had not died.
Returning home, I gave it a reboot by removing and replacing the battery. I've kept it in the open position since it has been plugged in and am quite afraid of manipulating the slide mechanism any further.
I'll be calling t-mobile to get their opinion on any further troubleshooting momentarily and report back.
Sorry for opening an older thread. do you remember what t-mobile said was the problem? i am having the same issue.
simplewhite said:
Sorry for opening an older thread. do you remember what t-mobile said was the problem? i am having the same issue.
Click to expand...
Click to collapse
The ribbon wire in the slide mechanism is either broken or pulled out of socket.
as the title says i was reading when the menu started showing and hiding again and again i tought was some book issues but when i got to the homescreen it began to run apps i had on it, i have no idea of the cause of this problem
I've had this same problem. I believe it's just the software and not a deficient screen. If you look over on the nookdevs website, there's a page about recalibrating the screen. I've tried it a couple of times and it's definitely improved it. Every now and then something wacky happens, but I guess that's to be expected when you let B&N develop for Android.
I had this happen myself once, and it was pretty annoying... If I didn't have adb available I don't think I could have fixed it until I did. I wasn't able to tap the screen myself, it was taping all over the place.
I did manage after a few minutes to get multitouch paint installed and it was drawing weird dots, lines, angles, etc...
I now have the recalibrate command in gscript but not sure I could run it while it's acting up. Luckily it's only happened once, and it happened while plugged in but never seen it happen again.
Happens a lot on my NC, and I think every time its because my kids touch it with dirty fingers (sweets, chocolate etc), smearing small amounts of dirt on the screen.
The screen goes nuts within few seconds, thinks its being clicked etc...
Wiping/cleaning the screen helps to resore normal behavior, btw - while the screen is moist it does not work for me at all...
Ordered screen protectors, lets see if it makes a differencel
My screen randomly goes nuts as well. It seems like a sudden, rather than a gradual thing. The screen sometimes gets pretty dirty, but cleaning it didn't seem to make much difference. Odd thing is, what DID make a difference was taking it out of the aftermarket case. I have no idea why this would work, but it does. One thing this case does is that it pushes the power and volume buttons in, as it uses four elastic straps at the corners. Maybe holding these buttons a certain way recalibrates the screen, and if you're touching it at the time, it freaks out?
I've noticed my screen only bugs out when I have it plugged into the charger.
As long as its unplugged, its fine. As soon as i pop in the cord, the screen goes haywire.
Only the wall charger though, not when its plugged into the USB on the computer.
My screen was doing that until I got a screen protector.
Sent from my LogicPD Zoom2 using XDA App
Also, if you lock and unlock the NC it should stop acting funny.
I noticed that too. Mine hasn't gone REALLY nuts since I took it out of it's case, but sometimes when playing angry birds, it freaks out to the point where I can't play. Hitting the power button, and then hitting it again, and unlocking makes it normal. Wouldn't that indicate it's software instead of hardware? Maybe there's more than one problem?
RChadwick said:
I noticed that too. Mine hasn't gone REALLY nuts since I took it out of it's case, but sometimes when playing angry birds, it freaks out to the point where I can't play. Hitting the power button, and then hitting it again, and unlocking makes it normal. Wouldn't that indicate it's software instead of hardware? Maybe there's more than one problem?
Click to expand...
Click to collapse
Mine does the same thing every now and again. And like you, locking the screen and waking it back up fixes it every time. It's definitely software related.
Do your cases have a latch? With a magnet? Because I'm starting to think that may have something to do with it.
My case has a latch, but the magnet is not against the nook when I'm using it..
HotShotAzn said:
Do your cases have a latch? With a magnet? Because I'm starting to think that may have something to do with it.
Click to expand...
Click to collapse
Heh, I've considered that.. Also considered the mystery sensor to the left of the Nook button too.. Nook is afraid of the dark.
Seriously though, with the CPU guvna' set to ondemand and wifi turned OFF before I power it off I haven't seen it reboot yet. It rebooted once yesterday and I know it had wifi left on as I had just been using it and didn't turn it off before it went to sleep.
So totally making up numbers here....
Default CPU governor + wifi on = 30% chance it's gonna reboot when it goes to sleep..
ondemand governor + wifi on = 20% chance it's gonna reboot
ondemand govenor + wifi off = <10% chance it's gonna reboot (not gonna even say 0 here.. heh)
RChadwick said:
My case has a latch, but the magnet is not against the nook when I'm using it..
Click to expand...
Click to collapse
I tested this theory. When the Nook is in the case, I get crazy screen taps when i try to type something. Out of the case, its perfectly fine.
When I just rest the Nook on the open case (not inside the straps/holders), it will also get crazy screen taps.
One thing to note is I also did not have any problems before updating to 1.0.1. Not saying the update is the cause of the problem but its one of the variables.
I'm absolutely sure there is an easy way, but I cannot see it right now.
The problem is: if I look at my KFHD and see a black screen I have no way of understanding if it is off or on.
The recommended way is "press the power button", but the effect of that action is that the KFHD turns immediately on!
Other devices have a "short press"/"long press" different behaviour (short press and the screen comes on, or nothing happens if the device is turned off / long press to turn the device on), but this is not the case with the KFHD.
Pressing the volume buttons does not help.
Any good idea?
Am I the only one believing this is a problem?
EDIT: I'm on CM10.1
Not really a direct answer, but figured I'd throw it out there anyway.... You could get a case that has the magnetic opener. When you open such a case, the screen turns on if the device is on, but of course will stay off if it is powered down.
JulianPaoloThiry said:
You could get a case that has the magnetic opener. When you open such a case, the screen turns on if the device is on, but of course will stay off if it is powered down.
Click to expand...
Click to collapse
Very cool idea! :good:
Do you happen to know where the sensor is located? (assuming the device is in landscape, with camera in the center of the top edge)
I'm asking because I could test with a small magnet and see how it may work out
EDIT: Found out! After a number of attempts, I realised the sensor is centered, a bit more than 1 inch from the bottom edge. It definitely works! Thanks again
I'm randomly getting a split screen, half of the screen turns upside down, half stays right side up. Screenshots do not show it however. I have to turn off the screen for it to go away. Happens periodically after several minutes of use. Any thoughts?
looks a bit like a slot machine yes? I have a vertical split where the the image is not flipped, but it does scroll up/wrap around the screen so that the notification bar is somewhere in the bottom half of the screen and the bottom of the image is wrapped around to the top.
I only really get it on custom kernels, I reported it to the maker of Elite and he said from what he has heard its a hardware issue and the only fix would be to RMA. Haven't done that yet as it fairly occasional, but plan to soonish.
kinda sucky how we are getting screen issues on this phone, i also have a screen issue with vertical gradient line appearing on some material themes.
sadly i cant RMA it. if i could i would have, i have ordered it all the way from the Middle east. :/ i will stick to the phone for a while longer as i love it.. and hoping that the line somehow dissappears by its own.
Now there is another long topic on freezing, but its basically about 10seconds freeze , then things normal and stuff. Mine is different so I made a new topic.
Have sprint note. On Marshmellow now but happened on Lollipop as well.
The problem is:
After several hours of use, or may even a day, the phone just freezes....partly. Let me explain. Basically if you touch anywhere on the screen, it won't register the touch. If you hit the hard recents button, it'll show recents, but you can't click any program (it doesn't register your touch). When it first happened I thought I needed a new screen, but quickly found out I probably don't: If I hit the nav bar, it will pull down full screen, and if I have it full of notifications, I can click any of the notifications, whether its near the top, middle, or bottom, and it registers the touch and sends me to the app. But then again, at that app, the screen doesn't register. Even if I touch in the same place on the screen where I clicked the notification that sent me to the app. But the nav bar still works. It recognizes the touch, and will pull down full screen, and I can click anywhere on the screen and my touch will register. Also if I hold the power button and the reboot options come up (which on mine has option from top down to bottom, I can click any option on the screen, and it will register my touch. But if I hit the home button, the whole screen is non responsive. So I have a partial freeze. The whole screen doesn't work, but then the whole screen will work when I pull the nav bar down, so im totally confused. I already tried usually differnt launchers, but same thing, after while, screen will be non responsive
If I reboot then everything works fine and normal, so I doubt its a screen issue. Because if its broke its broke. Also tried a hard reset,problem still came back. I guess it may be an app clashing problem but I have over 100 apps it could be any one of them
Has anybody experienced something similar?
I had a buddy give me an LG Lucid3 that had a similar issue... It actually got worse over time and the touchscreen totally stopped working. (He thought) I took it apart and actually the connection was good. Put it back together and just kept rebooting it multiple times in a row. Finally, the touch started to work a little an for some reason I thought to go and download an antivirus program. The phone had 11. Got rid of them and phone has been working fine for a couple weeks now. Idk if that's your problem but I figured I'd share this experience because I've never seen anything like it.
Sent from my KYOCERA-C6745 using Tapatalk