Database Develop

Nook Touch Screen Problems

I have a brand new Nook, with CM7.2 installed on the EMMC. This is my second Nook I gave my old one to my mom. Never had a problem like this with the old one. The problem with this one is when it sleeps and I turn it back on, quite often my touch screen won't function. The tablet seems to be working fine otherwise, but I can touch the screen all I want and it will do nothing. Can't even shut off the tablet by holding POWER for a few seconds because I can't click "Shut Down" on that menu. So i have to do a hard reboot. Every time. It's very annoying. Any help from anywhere would be greatly appreciated!

Do you actually see the screen and it won't work or is it just black? If it is just black it sounds like you might be dealing with the "sleep of death" issue.
If you can see the screen but it is just frozen to touch you may want to try a screen calibration app and see if it fixes the issue. Also try cleaning the screen really well.

Landara said:
I have a brand new Nook, with CM7.2 installed on the EMMC. This is my second Nook I gave my old one to my mom. Never had a problem like this with the old one. The problem with this one is when it sleeps and I turn it back on, quite often my touch screen won't function. The tablet seems to be working fine otherwise, but I can touch the screen all I want and it will do nothing. Can't even shut off the tablet by holding POWER for a few seconds because I can't click "Shut Down" on that menu. So i have to do a hard reboot. Every time. It's very annoying. Any help from anywhere would be greatly appreciated!
Click to expand...
Click to collapse
I don't know if this is the problem, but the new nooks have a new touch screen. In CM9 they had to update the drivers. I don't know if the devs did that on CM7. I have heard of no other complaints from CM7 users though. Don't know of a solution.

J515OP said:
Do you actually see the screen and it won't work or is it just black? If it is just black it sounds like you might be dealing with the "sleep of death" issue.
If you can see the screen but it is just frozen to touch you may want to try a screen calibration app and see if it fixes the issue. Also try cleaning the screen really well.
Click to expand...
Click to collapse
I can see it fine just can't do anything. Could you recommend a good Screen Calibration app? Also the device is 2 days old so I think it's not dirty and the screen works fine until it's waking up from sleep.

You can try this https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en. Unfortunately it sounds like you may just have a hardware issue. Did you have a chance to use it stock?

J515OP said:
You can try this https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en. Unfortunately it sounds like you may just have a hardware issue. Did you have a chance to use it stock?
Click to expand...
Click to collapse
No just nuked that locked down OS the second I got it out of the box.

You might want to go back to stock and return the device if it isn't working. I don't usually recommend that since most issues are user created but it sounds like it might be a legitimately defective device in this case.

J515OP said:
You might want to go back to stock and return the device if it isn't working. I don't usually recommend that since most issues are user created but it sounds like it might be a legitimately defective device in this case.
Click to expand...
Click to collapse
I agree, sounds like a hardware problem to me. You might try installing CM7 on SD first to see if you have the same issue.

Ok, update: I fixed it. The only thing I did was put on JuiceDefender Ultimate. I set it to turn off my Wifi when sleeping to avoid Sleep Of Death®. I did not see then(and do not see now)how that could have solved my touch-recognition problem. But it seems that it has. Before, this was a constant problem. Nearly anytime I woke up the Nook. Hasn't happened now since yesterday. So perhaps this whole issue was somehow Sleep Of Death® related... I don't know if that's even possible. I will leave that to you smart guys to figure out. But my problem does seem resolved now.

[Q] Soft key lights stay on permanently

Hello there, first post on here.
Anyone have/had a similar problem to this? The three soft key lights on my Optimus 4X now stay illuminated permanently. Even when the phone is switched off, they remain lit. I went so far as to completely drain the battery (or so I thought) so that there was insufficient power to turn the device on but the lights are still on. Does anyone know of any fix for this? Obviously, having these lights on all the time drains my battery quicker. I've tried the options in settings to switch it off and nothing works. I can only assume that this is a hardware fault.
Any thoughts?

foggyhorse said:
Hello there, first post on here.
Anyone have/had a similar problem to this? The three soft key lights on my Optimus 4X now stay illuminated permanently. Even when the phone is switched off, they remain lit. I went so far as to completely drain the battery (or so I thought) so that there was insufficient power to turn the device on but the lights are still on. Does anyone know of any fix for this? Obviously, having these lights on all the time drains my battery quicker. I've tried the options in settings to switch it off and nothing works. I can only assume that this is a hardware fault.
Any thoughts?
Click to expand...
Click to collapse
Maybe its some kind of short circuit...
You didn't do nothing like messing with firmware (flashing or rooting), or any crazy app?
It was always like that?

RuedasLocas said:
Maybe its some kind of short circuit...
You didn't do nothing like messing with firmware (flashing or rooting), or any crazy app?
It was always like that?
Click to expand...
Click to collapse
Nope, I wouldn't even know how. I've done a factory reset so it appears it is a short circuit. You think this can be fixed? I'm thinking I have an expensive phone on my hands that I can't use now.

Could these be related?
http://forum.xda-developers.com/showpost.php?p=34083067&postcount=35

Arne_B said:
Could these be related?
http://forum.xda-developers.com/showpost.php?p=34083067&postcount=35
Click to expand...
Click to collapse
Unlikely. The other thread is a well known problem with the phone, whereas this thread is the only time I have ever heard of the lights staying on all the time.

SimonTS said:
Unlikely. The other thread is a well known problem with the phone, whereas this thread is the only time I have ever heard of the lights staying on all the time.
Click to expand...
Click to collapse
Is it? I couldn't find a forum thread about this specifically so I thought only a few had this strange problem.
But you're right that this probably is a different problem than what I'm experiencing.

[SOLVED] Speakers suddenly dead!

Hello,
Both the earpiece and the other speaker suddenly stopped working on my nexus 6. I am suspecting it is a hardware issue since I performed a hard reset but the issue still persists. The odd thing is that both the earpiece and the speaker are affected at the same time. Are they connected to each other?
Is there any way I can make sure that this is indeed a hardware issue before cracking open the phone?
Thanks

backslashV said:
Hello,
Both the earpiece and the other speaker suddenly stopped working on my nexus 6. I am suspecting it is a hardware issue since I performed a hard reset but the issue still persists.
Is there any way I can make sure that this is indeed a hardware issue before cracking open the phone?
Thanks
Click to expand...
Click to collapse
Hello had the same bug super user app libs was away no root from here to now did nothing.reflashed super su, without​ super user app like supersu or magisk it dont work for me. hope i can help.
Another question, some times i turn on my display an for 3 sec i had more than max brightness, like a sun, no auto adjust always 20%, may the old nexus now die hard, hope not

Before I opened the phone, I'd boot to safe mode and see if things work. If they do, reboot and see if the problem comes back. Booting into safe mode disables all unnecessary apps, clears caches and resets settings to default. Sometimes that resolves your problem and on reboot things are working again.

ktmom said:
Before I opened the phone, I'd boot to safe mode and see if things work. If they do, reboot and see if the problem comes back. Booting into safe mode disables all unnecessary apps, clears caches and resets settings to default. Sometimes that resolves your problem and on reboot things are working again.
Click to expand...
Click to collapse
Thank you for your response. I forgot to mention I already booted to safe mode but it didn't make a difference.

backslashV said:
Thank you for your response. I forgot to mention I already booted to safe mode but it didn't make a difference.
Click to expand...
Click to collapse
So I guess it sounds like hardware. You might take s close look and see if there is damage/dirt in the jack making the device think the headphones are connected. The pin is easily bent and wears so it's probably just that. ifixit has a repair guide.
Alternatively, you might consider Bluetooth headphones [emoji4]

ktmom said:
So I guess it sounds like hardware. You might take s close look and see if there is damage/dirt in the jack making the device think the headphones are connected. The pin is easily bent and wears so it's probably just that. ifixit has a repair guide.
Alternatively, you might consider Bluetooth headphones [emoji4]
Click to expand...
Click to collapse
Thanks. I don't think it's the jack issue because I installed an app that shows a headphone icon in the status bar when a headphone is plugged in and it doesn't show it when nothing is connected.
Do you know why both speakers ceased functioning at the same time AND if there is a way for me to direct audio to only one of them, either the earpiece or the speaker, to see if one or both
are dead?

wow. I reverted back to an earlier build from Feb and now it's working. Very interesting.

speakers
backslashV said:
Hello,
Both the earpiece and the other speaker suddenly stopped working on my nexus 6. I am suspecting it is a hardware issue since I performed a hard reset but the issue still persists. The odd thing is that both the earpiece and the speaker are affected at the same time. Are they connected to each other?
Is there any way I can make sure that this is indeed a hardware issue before cracking open the phone?
Thanks
Click to expand...
Click to collapse
First, sorry to hear about your problem. But, I am actually happy to see this up at xda. Tell you why. I purchased a uesd nexus 6 from a seller on ebay. Description was everythings works. Pics showed it was in excellent condition.
Problem was when it arrived. I discovered the top speaker was trash. Total robot like voice. Of course seller denied any knowledge of it. My option was to return it to him. But judging from the way he spoke to me. I could tell it was going to be a fight. There is no way he did not know about this. I wound up eating the phone and am currently awaiting a new top speaker. So, please dont forget to ask about speakers if buying used. My concern was body and screen. I never thought to ask about speakers and I never thought there would be crooks like him. Wrong...

backslashV said:
wow. I reverted back to an earlier build from Feb and now it's working. Very interesting.
Click to expand...
Click to collapse
It is interesting. Is it possible you had a mismatch between kernel and security updates? "Newer" kernel on "older" ROM? Or vice versa. The difference doesn't have to be more than one has a security update that the other didn't.

ktmom said:
It is interesting. Is it possible you had a mismatch between kernel and security updates? "Newer" kernel on "older" ROM? Or vice versa. The difference doesn't have to be more than one has a security update that the other didn't.
Click to expand...
Click to collapse
More like mismatched or corrupted libs or drivers

Know this is an older thread, but just figured I'd post what I found regarding a similar issue I had. My phone basically took a 3 second dunk in the sink. Everything seemed fine the first hour or two, then the speakers stopped working. However, it seems like the speakers failing is some kind of water damage failsafe or something. The solution is just to turn your phone off and on around 5 times (I can't remember the exact number, but once or twice won't cut it), and you will have the speakers return to normal. Not sure if the OP had the same issue, but just an idea in case something similar happens to others.

Bumping an old thread but I had this same issue and had to flash back to previous builds. I stopped updating my phone around Jan/Feb. Tried to update to the Aug 7.1.1 build and the same thing happened again. I didn't try the turn on and off 5+ times, I'm just once again restoring my Jan/Feb build.
Can anyone else confirm this "fix" or has this same problem?

I'd boot to safe mode first. If it works then, it has something to do with an app, your app restore process or something like that.

Touch screen issues after some time

I am having touch screen issues with the phone after some time of it sitting in place,its becoming super unresponsive and i have to restart the phone,i have tried flashing xiaomi eu,china dev latest,but i was having the issues even with latest xiaomi eu.

vlatko98 said:
I am having touch screen issues with the phone after some time of it sitting in place,its becoming super unresponsive and i have to restart the phone,i have tried flashing xiaomi eu,china dev latest,but i was having the issues even with latest xiaomi eu.
Click to expand...
Click to collapse
Same here, since then my 1 week brand new MI 5 is used as a paper blocker...

vlatko98 said:
I am having touch screen issues with the phone after some time of it sitting in place,its becoming super unresponsive and i have to restart the phone,i have tried flashing xiaomi eu,china dev latest,but i was having the issues even with latest xiaomi eu.
Click to expand...
Click to collapse
same here, i tried almost every ROMs from Android 6 (CM/MIUI/ASOP) to Android 7.xx (MIUI China, and RR...)
The touch screen will suddenly have no response until i force rebooting the phone.
However, it seems hardware-related issue, i had found the touch not work while entering TWRP (the ROM is not loaded yet).
Next step, i will try to teardown it and re-assemble to see the method works or not.

mingjongjou said:
same here, i tried almost every ROMs from Android 6 (CM/MIUI/ASOP) to Android 7.xx (MIUI China, and RR...)
The touch screen will suddenly have no response until i force rebooting the phone.
However, it seems hardware-related issue, i had found the touch not work while entering TWRP (the ROM is not loaded yet).
Next step, i will try to teardown it and re-assemble to see the method works or not.
Click to expand...
Click to collapse
hi, i tried to teardown my phone and re-connect all connectors, but the touch screen will still be no response after a while.
does anyone have any other idea?

Its probably hardware problem, as i don't stay long enough in recovery to notice the issue or unable to notice it because all you do is press and not a lot of swipes, and another problem is that its almost impossible to buy a new original oem screen,all those sellers on aliexpress claiming to sell new screens in reality just sell a refurbished screen with very low quality, it looks like the old saying "if its made in china its
sh*it" is true, yes most phones are Chinese but they are older companies, better engineering, more experienced, yes issues like this also happen with them but a lot rarer, but here it looks like 10%off all sold phones have problem, some same as ours some worst, and i was typing this for so long, i try to type one letter, another one is pressed or none at all ?

Have you tried flashing Stock ROM ? If you don't then please give try.
earlier versions of TWRP had this issue but only in TWRP. Now it's fixed. And some devices doesn't support such custom kernel and causes problem with nav button.
So first flash thw stock rom and see if the problem exist or not.

rhrokib said:
Have you tried flashing Stock ROM ? If you don't then please give try.
earlier versions of TWRP had this issue but only in TWRP. Now it's fixed. And some devices doesn't support such custom kernel and causes problem with nav button.
So first flash thw stock rom and see if the problem exist or not.
Click to expand...
Click to collapse
I am currently on stock global beta firmware and still facing the same issue, no root not costume recovery and still facing the same issue, now i almost sure that its a hardware problem, like many other users that face it ?

Okay you can post this one to MIUI forum. Try submitting an issue there. Hope you'd get some solution.

I don't think there is another solution other than changing the screen, but thanks anyway

i thing this is the hardware issue, anybody can detect the problem?

CristalClear said:
i thing this is the hardware issue, anybody can detect the problem?
Click to expand...
Click to collapse
While the touch screen lose response, you can press middle part of mi5 (i.e. the connector) vigorously without shutdown the phone. And then, you can find the touch screen will work again. Therefore, in my case, that indeed a hardware issue.
FYR

mingjongjou said:
While the touch screen lose response, you can press middle part of mi5 (i.e. the connector) vigorously without shutdown the phone. And then, you can find the touch screen will work again. Therefore, in my case, that indeed a hardware issue.
FYR
Click to expand...
Click to collapse
Can you explain this better? I have the same issue, if there's a way to fix it without reboot I want to try it, but I don't understand where/what I should "vigorously press"...

For your reference.
I had touchscreen problem at the beginning when I received it from Gearbest in 2016. It would take much time to send it back and forth so I decided to flash it with a newer Global stable rom (I think I was Miui7) by myself; after that, the problem was 95% gone, (it still happened sometimes but not severe). Lately, I cable updated it to Miui 9 Global Stable and the problem was back and severe.
I TWRP installed Miui 9 Global developer Rom - not working
TWRP LineageOS 14.1 - not working
There are no points to use LineageOS 14.1 if the touchscreen problem is still there.
So I TWRP cleared data and cable-installed Miui 9 developer Rom, and The problem is completely GONE!!!!
Maybe you could try some of the steps above.
I also change my charger from 2V to 1V output after installing, and only charge it from the wall socket. (I used to charge from the extension ones more)
I only installed necessary apps at the beginning then gradually add more.
Hope that would help!!

Note 8 Screen suddendly turn full flicker green !

Hello Guys !
I have a big massive Problem with my Note 8 SM-N950F.
I was watching Youtube and my Phone has worked fine no Problem no Green Screen till suddendly my Screen went full Green Flickering mode and I dont know what the Reason is. I restarted the Phone and it worked again no problem for 30min then it went back to Green flickering screen.
I have try : Restore the Phone as New completly Wipe out / Result = Negative
Installed a Custom Rom / Result = Negative
I did not dropped the Phone nor does it has a Water Damage.
The Green Flickering screen only comes when Im in the System but while I am on TWRP it never shows up so I think it has something to do with the system and not Hardware.

Problem still there still need a Help

LuxyFlex said:
Problem still there still need a Help
Click to expand...
Click to collapse
A full wipe and flashing the latest official firmware usually solves non-hardware issues. If you tried that and the issue is still there, then it sounds like a hardware issue that would need repair (hopefully within warranty).

sefrcoko said:
A full wipe and flashing the latest official firmware usually solves non-hardware issues. If you tried that and the issue is still there, then it sounds like a hardware issue that would need repair (hopefully within warranty).
Click to expand...
Click to collapse
But how can it be a Hardware problem, i didnt drop nor does it have any Damage and if im on TMRW or Download mode i dont see the green flickering only after I boot

LuxyFlex said:
But how can it be a Hardware problem, i didnt drop nor does it have any Damage and if im on TMRW or Download mode i dont see the green flickering only after I boot
Click to expand...
Click to collapse
Motherboards can be faulty, etc. It doesn't have to be caused by the user. If you flash stock with full wipe and the issue persists then the only remaining variable is hardware. Either that or maybe you didn't do the full wipe when flashing latest firmware. Not sure what else to suggest beyond those two possibilities. Hope you get it working.

I had this also on my N950F. It happened very suddenly while I was using it:-
* Greenish tint
* Reduced brightness capability
* Flickering
* ~half-inch border of more intense tinting on all four sides
Cut a long story short - couldn't fix it with a complete factory reset.
Today, the problem has suddenly disappeared and the screen is perfect after four days with this issue. Just out of the blue - screen back to normal.
I'm guessing it was either a dodgy board connection which righted itself, or a temporary light sensor issue.

it is a hardware fault relating to the lcd. this is usually seen when the phone has been dropped. and is a broken lcd. i know its stated it wasnt dropped but that is the issue

galaxys2Tav said:
it is a hardware fault relating to the lcd. this is usually seen when the phone has been dropped. and is a broken lcd. i know its stated it wasnt dropped but that is the issue
Click to expand...
Click to collapse
Utter nonsense. It hasn't been dropped and it doesn't have an LCD screen. Know-it-alls spoil it for others by making unfounded comments.

aZooZa said:
Utter nonsense. It hasn't been dropped and it doesn't have an LCD screen. Know-it-alls spoil it for others by making unfounded comments.
Click to expand...
Click to collapse
unfortunatly i missed judged and put lcd as infact its an O-LED screen! my bad, and as i fix samsung screens on a daily basis weather they would be LCD or O-LED screens this is infact the fault. never sujested you had dropped it im saying that this is the probblem with it weather it has been dropped or become faulty. know-it-all spoil sports are here to help on xda and unfortunatly its not the right answer you are looking for but i posted the right answer to the question that was asked in the Q&A section. just thought i would help out but, but hey

Thread cleaned
Please keep it on topic
FSadino

galaxys2Tav said:
unfortunatly i missed judged and put lcd as infact its an O-LED screen! my bad, and as i fix samsung screens on a daily basis weather they would be LCD or O-LED screens this is infact the fault. never sujested you had dropped it im saying that this is the probblem with it weather it has been dropped or become faulty. know-it-all spoil sports are here to help on xda and unfortunatly its not the right answer you are looking for but i posted the right answer to the question that was asked in the Q&A section. just thought i would help out but, but hey
Click to expand...
Click to collapse
Yes, that's it, if not droped, then a faulty screen, just like that, many people wish that all problems can be fixed by some trick, clever app or hidden setting, but, in true, a very little number of troubles are fixed this way, so my advice would be to take the device to an authorized samsung service center

aZooZa said:
Utter nonsense. It hasn't been dropped and it doesn't have an LCD screen. Know-it-alls spoil it for others by making unfounded comments.
Click to expand...
Click to collapse
Be nice to people trying to help you.
There is two causes to this. Software or hardware. Next time it happens try screen capture. If appears on screen shot it's software buggy. Although highly unlikely but if it does usually a reboot or factory reset solves it.
Other more likely scenario is hardware. If you used a crt tv you'll know as its the same symtom of failing picture tube.
And it's definitely not connector issue.
Sent from my SM-N950F using Tapatalk