Database Develop

[Q] My screen taps/touches/clicks itself

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.

[Q] screen won't turn on. restarts by itself

so for the past month my screen has been dead when it is in portrait mode. it would only turn on if i open my keyboard in landscape mode. if i close the keyboard the screen will freeze. the screen is still responsive in portrait mode though, for example, i can still slide to unlock even though the screen is off. i also can't turn on the phone unless it's the keyboard is on til i get to the lock screen.
also my phone has been restarting itself a lot this past month. usually i notice it does it when i walk and it's in my pocket. but it also happens even when i'm just using the phone, it'll randomly restart itself.
is there any solution to my problems or is it a lost cause?

This sounds like a ROM/overclocking issue. If you're overclocking, turn your levels down a little bit. Flash a different ROM if that's not the case. And if neither of those work, rip her open and check and make sure everything is in their proper place. There are guides online that you can google.

[Q] Screen goes black during call, CM10.1 dialer

Hiya folks. Running CM10.1 stable on my targa (aka Droid Bionic). It was beautiful except for lack of nav dock support, a problematic Google Now (different problem, with workaround), and this particular problem, which I hope someone know what I am talking about...
When a call comes in and I answer by the slider, the screen goes black, whether or not I held the phone up to my head.
I cannot turn the screen back on. None of the buttons seem to do anything, though backlight for the 4 hard buttons does turn on indicating that some command was received by the touchscreen. Not even the power button will bring the screen back during the call.
If the other party hangs up, the phone goes back to normal.
With screen off, I can't hang up.
I can hang up if my Bluetooth headset was connected and I hang up with that.
I've searched all over and this issue seem to be a pretty popular issue last December across all CM 10 builds. However, I don't know if this was ever resolved for this build.
I can't find an option in the ROM to just flat "turn off face proximity detection" either. Or in any way to "tweak" it.
CPU-Z says my proximity sensor is working, so I guess it's just not calibrated properly for the dialer?
Can we get a "special hidden tweaker" much like the light sensor tweak for the auto-brightness levels?

Figured it out. It wasn't CM. It was Screebl and the stupid orientation sensor, and how the Launcher is fixed to portrait mode.
I think I had my phone laid down and it's at a diagonal so it's in landscape mode, and the phone's fine with that when it's just showing contacts. Screebl kicks in and determines that landscape, phone orientation says stay on, so screen stayed on. It was set to turn off the screen IMMEDIATELY when the orientation goes out of "viewing range". (Saving batteries, ya know).
When the call was answered, Screebl should have turned itself off (i.e. ignore input while call is in progress). But it didn't. The "answer the phone" screen flipped the display back to portrait mode. The phone, still laid flat, in "landscape", is now "out of viewing range", and Screebl turned off the screen.
Strange interaction among the various apps, yes.
I'm still trying to figure out how to make my Bionic, with extended battery last the whole day. Juicedefender Ultimate somehow just keeps turning the screen back on every X seconds (taking root control for SOMETHING) and Wakelock detector says the phone is not going into enough deep sleep (kinda like me, hahaha)

What did I possible do so I don't do it again?

I was lying down on my back. Hands up looking at phone. I watched some video. I viewed some pictures. I turned it off and shortly after I got up to plug it into the charger.
When I turned the screen on to verify my alarm was set, the screen is normally portrait in orientation was landscape. It would not rotate. So, I unlocked it in landscape mode, which is a tad awkward just because I'm not used to it.
The screen would only rotate into landscape, or portrait, but portrait was upside down! The buttons for back or home were away from me. Turn off screen and back on. Same thing. Lock screen landscape.
So, I figure I'll go do that calibration where you put your phone on a level surface. It pops up in landscape and all I could see was a letter G and rest was black screen.
Rebooting fixed the problem, but does anyone know if I might have hit something or if there's a fix without rebooting?

yuppicide said:
I was lying down on my back. Hands up looking at phone. I watched some video. I viewed some pictures. I turned it off and shortly after I got up to plug it into the charger.
When I turned the screen on to verify my alarm was set, the screen is normally portrait in orientation was landscape. It would not rotate. So, I unlocked it in landscape mode, which is a tad awkward just because I'm not used to it.
The screen would only rotate into landscape, or portrait, but portrait was upside down! The buttons for back or home were away from me. Turn off screen and back on. Same thing. Lock screen landscape.
So, I figure I'll go do that calibration where you put your phone on a level surface. It pops up in landscape and all I could see was a letter G and rest was black screen.
Rebooting fixed the problem, but does anyone know if I might have hit something or if there's a fix without rebooting?
Click to expand...
Click to collapse
Personally this hasn't happened to me but I have heard of it happening. From what i have read and heard is that the proximity sensor for some reason gets stuck. i have heard of people using the old flashlight trick that was used on the M7 to fix it but a reboot fixes it every time. So I don't think you bumped anything. hope this helped .

screen randomly wakes up

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