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.
Related
Hey guys. By now, I'm sure most of you are probably familiar with the screen alignment issue (where, sometimes when you go to click on something, it clicks something above or below and is about 1/3 of an inch off).
Well, I've noticed something on my device and was wondering if anybody else has had the same experience. If I have the screen brightness all the way down, I can use the screen for quite some time before this happens. Then, I just hit the power button, put it to sleep, and then wake it back up and the problems corrected. What's weird is, if I have the brightness all the way up (like when I'm outside on a sunny day), it takes far less time for the misalignment issue to show it's ugly face.
Basically, what this says to me is that it might be related to a heat issue from the screen itself. Just wondering what everybody else has noticed.
Mi|enko said:
Hey guys. By now, I'm sure most of you are probably familiar with the screen alignment issue (where, sometimes when you go to click on something, it clicks something above or below and is about 1/3 of an inch off).
Well, I've noticed something on my device and was wondering if anybody else has had the same experience. If I have the screen brightness all the way down, I can use the screen for quite some time before this happens. Then, I just hit the power button, put it to sleep, and then wake it back up and the problems corrected. What's weird is, if I have the brightness all the way up (like when I'm outside on a sunny day), it takes far less time for the misalignment issue to show it's ugly face.
Basically, what this says to me is that it might be related to a heat issue from the screen itself. Just wondering what everybody else has noticed.
Click to expand...
Click to collapse
Yes I have notice it too with the same setting but didn't think much of it and just put it to sleep and woke it up and worked after that.
dont know if its a heat issue, my phone is always on 0% brightness and it still randomly happens.
Yesterday I was texting someone, didnt even finish the message because something else demanded my attention. So I close the keyboard and put it in my pocket.
5 minutes later I take my phone out, and its off. I try to turn it on but nothing happens. Tried taking out the battery and SIM, waiting a few minutes, and put them back in, still nothing. I take it up to T-mobile and they tell me its a month out of warranty.
So earlier today, I say "ehh what the hell" so I try again, this time I held the power down for about 10 seconds, while its connected to a charger, and it boots up! I get past the G1 screen to the Cyanogenized boot screen (5.0.7 test 5 if it helps...) and in excitement I call someone in to show them. As I pick up the phone to show them, the usb cable is yanked out, and the screen goes black. Never felt ****tier. Tried to get it to power on again....back to square 1.
About an hour or two later, I look over and the face keys and keyboard are backlit, but still nothing on the screen. I also noticed that if I take the battery out while its off the charger, the backlight for the buttons will turn off, but will immediately come back on once the battery goes back in.
Basically, Im stumped, and any help would be appreciated.
EDIT: Now the button backlight is off...
I think your phone didn't shut off actually.
Try the 3 finger solute!
Hold send, end, and the menu button.
I've also had this happen to me, and to tell you the truth it didn't turn out good. :/
After awhile My touch went completely out.
It happened when I was running an experimental rom.
Also try restoring a back up if you created one before it started happening. :/
Well I know its off, Ive taken the battery out, and havent gotten it to come back on except for the one time. And Ive removed the battery since then as well. Ive tried power+home, power+camera, power+menu+send. None of them have worked.
One of two things, hopefully the first:
1.) You have a bad battery, replace it, or borrow a friend's and see if that works.
2.) You have a new paperweight. In that case, my condolences, friend.
Seriously, though, from what you described, it sounds like your battery just bit it. Try taking it out and examining it for any bulging or swelling that may not have been there before.
The woman at the T-mobile store tested a different battery and a different charger, so in my case its not likely, but I will give it another shot, since things have somewhat perked up. Right now the button backlights will randomly come on and stay on for a while, slowly dimming, and then eventually turn off, only to come back on later.
thegreatcity said:
The woman at the T-mobile store tested a different battery and a different charger, so in my case its not likely, but I will give it another shot, since things have somewhat perked up. Right now the button backlights will randomly come on and stay on for a while, slowly dimming, and then eventually turn off, only to come back on later.
Click to expand...
Click to collapse
After reading you tried different batteries, I think you're in the market for a new phone. =[
The battery idea was the only thing I could have thought of as well.
Hope you manage to figure this out without having to buy a new phone, though. =[
In regards to your most recent post, sounds like some kind of short. There wasn't any water exposure was there? I've actually heard of people having there phones in their jeans pocket and sweating enough to turn the indicator and fry the board.
But yeah, it sounds like phone death. I would totally disassemble it and check for any corrosion though. Who knows, you may save it, then you have fat bragging rights
Ninjineer said:
In regards to your most recent post, sounds like some kind of short. There wasn't any water exposure was there? I've actually heard of people having there phones in their jeans pocket and sweating enough to turn the indicator and fry the board.
Click to expand...
Click to collapse
They must be doing some serious running.... or be really, really fat.
Btw, you can check to see if your G1 got exposed to water, OP. Take out battery and there's a little sticker under the IMEI sticker. Its round. If it's white - you're good. Any other color (i think it turns red or blue?) there's water damage.
anyone have their nook hd + start acting like it haunted? while reading a book pages turn back and forth by itself. watching a youtube video and it starts doing its own thing. entering and exiting apps???
the screen also started doin some weird pixellating thing.
hydro6773 said:
the screen also started doin some weird pixellating thing.
Click to expand...
Click to collapse
I have had the screen do odd things from time to time but I have never seen "some weird pixellating thing".
did you do anything to fix it?
hydro6773 said:
did you do anything to fix it?
Click to expand...
Click to collapse
Did you try cleaning your fingerprints off?
Sent from my SCH-i705 using XDA Premium HD app
yes i cleaned the screen off and all my finger prints. I was doing some reading and some people say that they had the same problem and they said something about holding the power button for 20 seconds and then holing it for 2 seconds to turn it on. I tried that but it still eventually did the same thing. I also read some people said that once they put a screen protector on it seemed to help. What do you think?? Have you had this problem at all. I cant return it to B & N since its rooted and was purchased off craigslst. Is this a known issue?
When mine gets weird and I get phantom finger presses just shutting the screen off and turning it back on fixes it. Usually happens after long game sessions.
Sent from my SPH-L900 using XDA Free mobile app
This is the only problem I have with my nook HD+, but I am getting close to finding the problem.
I have managed to get dmesg to print out when the problem is occurring, and that isn't easy when it wants to start doing random presses !
Every time this problem occurs I see the same thing:
lowmemorykiller: killing 'ndroid.settings' adj 1000 to free 19712KB on behalf of 'kswapd0' because cache 85116KB is below limit 86016KB for oom_score_adj 12
free memory is 5568KB above reserved
When the crazy screen presses start happening lowmemorykiller begins closing all sorts of things one immediately after another, and then crashes out with a negative memory available like :
-58329KB available
I'm guessing there is a memory leak somewhere.
I've been getting phantom touches since upgrading to CM 11 (6/16 build and up), although I left the Touch & Hold delay to its stock "short" setting when I upgraded, so not a good experiment. (Two variables.)
For me, a web page will register a "click" while browsing with my thumb hovering about an inch over the screen.
I have "show touches" enabled, but I don't see a touch.
I have a screen protector. (Have had it for months.)
For now, I'm setting the Touch & Hold delay to Medium as a work around.
TLDR: I was cuddling my gf to sleep while using my phone. I fell asleep too. The phone was in bed with us for a couple of hours, but I don't think either of us lay on it, though my gf may have put some weight on it while getting up from bed to go to the w/c.
This morning it was unresponsive to touch, after rebooting it twice it won't turn on at all
When I press on the screen 1/3 of the way down with a bit of force, I feel it moving a bit and I can hear and feel a click on the inside.
The glass is intact.
-----------
I fell asleep with the phone in my hand and I must have let go of it in my sleep. I woke up when my girlfriend was going to the bathroom in the middle of the night. The phone was still in the bed near where my hand was when I was falling asleep, but it was also in the path of my half asleep girlfriend rolling out of bed. I checked to see if it was still alive by pressing the power button and the screen turned on. Satisfied, I put it on my nightstand and went back to sleep.
When I woke up this morning I tried using it. It wasn't responding to touch at all, not even the home row buttons. But the volume rocker worked and so did the power button menu, but I couldn't select reboot in the menu with the touch not working. I force closed it with power + volume up, and when it rebooted it still wouldn't respond to touch. I force closed it again and now it won't turn on at all. I tried numerous button combinations (power on + volume up, down, all three, holding for up to 20 seconds) and it doesn't respond to being plugged into the wall or to the computer either, no led light and it's not mounting on the PC. It had about 60% power left before force closing it.
The funny thing is is that I couldn't figure out what the cause was for a long time. I googled it and search results for Z1's "sudden death issue" appeared and I figured it was something like that. Or maybe it was a delayed effect of putting it underwater 2 days ago.
But then it dawned on me, it was (of course) what had happened in the middle of the night. The phone looks completely fine, but after examining it closer, when I press on the screen 1/3 of the way down with a bit of force, I feel it moving a bit and I can hear and feel a click on the inside. I wonder what that could be..
What are my options now? I got the phone just a couple of days ago. I doubt this is covered by warrenty right? User error?
I'm not sure if this is even the real cause though - I didn't see it happen.... but I guess it's the most logical explination.
My girlfriend is pretty small so I'd imagine she would have had to put all her weight on her hand or elbow when she was getting up to be able to break the phone like that. I have a foam mattress which probably absorbed a lot of the weight? If this is indeed the case, I'm a little disappointed in the build quality if this broke something in the phone's innards with relative ease.
Any advice would be appreciated. It's the UK model bought outside of the UK from a local retailer. This is my first good smartphone and I loved it for the short time we had together. I'm devistated about it and not really sure what to do next.
Someone hold me
No visible damage = return it as faulty
Just say it died overnight while charging.
Sent from my D5803 using XDA Free mobile app
pricey2009 said:
No visible damage = return it as faulty
Just say it died overnight while charging.
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, that's the plan I just emailed the seller
Edit: They said to go to a Sony store to claim warrenty on it
adamk7 said:
Thanks, that's the plan I just emailed the seller
Edit: They said to go to a Sony store to claim warrenty on it
Click to expand...
Click to collapse
You should have a 14 day guarantee with the seller if you bought from UK..
I would go back to them and demand a replacement..
Sent from my D5803 using XDA Free mobile app
So I was just about to go to the sony store, I had the phone, cables and everything neatly packed up an ready to go. I decided to give it one last try just in case to avoid the all too common scenerio when it unexplicably magically starts working in the store. I plugged it into a wall charger and held down the power button and the red light turned on! I left it for a minute and then pressed the power button again, and the screen turned on with a battery charging logo! It looked like the battery was fully dead so I left it for 5 minutes and turned it on again. It booted up! Now the moment of truth: will the touch screen work....
Drum roll......
It does!
Everything works normally now. I have no idea wtf happened but I'm really happy that I don't have to deal with sending it in and everything.
Though I'm a little worried about what the screen clicking is, that's still there.
I'll post a video later and might take it in to sony anyway to see what they say
Edit: I made a new thread with the video: http://forum.xda-developers.com/z3-compact/help/video-pressing-screen-spot-makes-t2918289
adamk7 said:
So I was just about to go to the sony store, I had the phone, cables and everything neatly packed up an ready to go. I decided to give it one last try just in case to avoid the all too common scenerio when it unexplicably magically starts working in the store. I plugged it into a wall charger and held down the power button and the red light turned on! I left it for a minute and then pressed the power button again, and the screen turned on with a battery charging logo! It looked like the battery was fully dead so I left it for 5 minutes and turned it on again. It booted up! Now the moment of truth: will the touch screen work....
Drum roll......
It does!
Everything works normally now. I have no idea wtf happened but I'm really happy that I don't have to deal with sending it in and everything.
Though I'm a little worried about what the screen clicking is, that's still there.
I'll post a video later and might take it in to sony anyway to see what they say
Click to expand...
Click to collapse
Glad to hear it
I have the same phone symptoms as OP. Except, I was using the phone just 15 minutes before it refused to turn on. Also, for the first time I noticed the glass making a clicking sound when pressing coming from the middle of the screen, inline with the power button. I`ve tested the phone before and never heard this clicking sound.
At this point, even if the phone fixes itself, I`d rather send it in for repair before the clicking turns into a screen fracture.
I dont know why, but sometimes my screen will stop responding to touch. I can still use the top and bottom of the screen, but the 90% in between the top and bottom lip of the screen wont respond until i restart the phone. This can happen once a week or three time a day, seemingly at random. Anyone know about this problem?
I had this happen the other day and it really surprised me - exactly where you said as well. The top & bottom worked, but the middle was dead. I did have a little skuzz on the phone, so I spat on it & wiped it off and that brought it back to life. Not sure if that was truly the problem, or if it was just coincidence. Which screen protector are you using?
burnxtc said:
I had this happen the other day and it really surprised me - exactly where you said as well. The top & bottom worked, but the middle was dead. I did have a little skuzz on the phone, so I spat on it & wiped it off and that brought it back to life. Not sure if that was truly the problem, or if it was just coincidence. Which screen protector are you using?
Click to expand...
Click to collapse
At the moment i dont have a screen protector on, ive had the problem with and without screen protectors. Its so weird, its like the screen just dies.
Hopefully it's just a background app/service and not a hardware issue. I'd try freezing the snot out of background apps - particularly anything that didn't come pre-packaged with the phone - and go from there. Should this work, enable a handful at a time until you find the culprit. Pretty much anything can lock up an app nowadays, particularly keyboards and the like.
Below is my "final" list of frozen apps on a11 and the phone performs exceptionally. No root & no security broken. This is a preset file for ADB AppControl - I hope this helps.
When you say freezing, do you mean adding to deep sleep or removing with adb?
DS1000RR said:
When you say freezing, do you mean adding to deep sleep or removing with adb?
Click to expand...
Click to collapse
I mean freezing/disabling via adb. I only remove once I'm completely comfortable with a practiced configuration.