Well i think my Polaris has finally given me the finger.
The touch screen no longer responds to finger/stylus presses. If i press randomly for long enough it does register a click, but never in the right spot or consistently.
What do you think it could be?
Ive tried reloading different roms that have worked perfectly before, hard resets, and ive even tried taking it apart and reconnecting the connectors.
It was dropped a few days ago but it was fine, then one day, while doing nothing in particular it decided to stop responding to touch input, the normal buttons work fine.
My XDA Orbit2 (same as Cruise) has the same problemccasional freezing and touch screen decalibration (needs to be recalibrated every 5 min). problem is that this occurs infrequently. therefore i have lost hope that sending in for repair would work.....
i have a same problem..
my polaris's touch screen sometimes not responding to any touch.
i have to connect it to my computer or battery charger, and then it will work again.
can anybody explain to me why??
thanx before
same happened to me last week! well, its on its way to o2 service partner right now... guess it was supposed to brake in about 7months from now.
adderz91 said:
Well i think my Polaris has finally given me the finger.
The touch screen no longer responds to finger/stylus presses. If i press randomly for long enough it does register a click, but never in the right spot or consistently.
What do you think it could be?
Ive tried reloading different roms that have worked perfectly before, hard resets, and ive even tried taking it apart and reconnecting the connectors.
It was dropped a few days ago but it was fine, then one day, while doing nothing in particular it decided to stop responding to touch input, the normal buttons work fine.
Click to expand...
Click to collapse
Hi!
I broke my touchscreen (Tytn2) and replaced it with a touchscreen from ebay for 10 €.
It works, but there are some problems:
1. I have to press very strong onto the screen for a signal!
2. On the edges i have to press very very strong - even stronger then in the middle.
3. the signal itself is on the right position......
4. i have already tried to reset the sensitivity of the touchscreen (and increase/decrease it)
5. i have already aligned the screen several times....
My questions are:
1. is it installed well?? (I had to connect 4 pins on my own.....)
2. if it gets the right signal (but only when I´m pressing very strong), can there be anything wrong with the connectors?
PLEASE HELP ME!
greetings!
Well i was SO close to just giving up and buying a new phone.
I found however, an entire brand new housing for the low low price of $65 AUS. I could of just bought the digitizer for about $30.
When i look at the devices out there...they arent that great...i was going to get a Nokia E72 but realised i would miss the touch input.
So i will suffer along with my touch cruise, checking these forums for updates on the Android progress
ANd ill have a spiffy new case to boot.
My 02 Orbit 2 touch screen has stopped working also - I found that a temporary solution is to hold the top of the screen tightly over the earpiece
It would register touches, enough to Flash back to Original ROM
It Going back to 02 this weekend.
I spent several hours over the weekend rooting, unrooting, and re-rooting my new NST. Each time I rooted it, I ended up with a touchscreen problem where touches registered with the wrong column.
For example: when trying to use the backspace key, 'h' would also register. When trying to use 'p', 'e', or 'r', 'y' would also register. Both the key that I wanted and the central key would indicate a keypress (turn black) but only one of them would register in the text box. This is entirely dependent on software, but it's something that is cleared with the 8x failed boot restore and not with the two bottom buttons restore.
I have tried both TouchNooter and MinimalTouch twice. My latest attempt was MinimalTouch:
Start with a clean NST with software 1.0.1
Install 1.1 update (keyboard still works)
Follow MinimalTouch procedure
NST is rooted and android home screen is accessible, however, the keyboard no longer functions properly
Perform reset (hold bottom two buttons on startup)
Button Saver is gone, android home screen is not accessible, keyboard still does not function properly
Perform 8x reboot restore
Keyboard functions perfectly
Has anyone dealt with this before? I couldn't find anything with the search function.
Though this thread appears to be doing nothing, I will at least let you guys know of the current idea:
I have gone back and checked the touchscreen after each step in the procedure, and appears like the 1.1.2 update causes the problem.
Without any rooting or funky installs:
Perform 8-reboot reset
Touchscreen works fine, SW 1.0.1
Install 1.1.2
Touchscreen is impaired, SW 1.1.2
Perform 8-reboot reset
Touchscreen works fine, SW 1.0.1
Did the 1.1 update include a change in the touchscreen sensitivity?
How do I ensure that the IR sensors are clean? A shot of compressed air?
Should I just call B&N/sears and try to get a replacement that functions properly with the update?
I believe that I have determined the cause of my touchscreen difficulty:
The front bezel of my NST is not entirely glued down. I noticed that the spacing was irregular between the eink display, the black (really dark) plastic layer, and the top matte gray layer.
Squeezing my NST temporarily blocks the issue (until the glue re-expands)
The software updates must change the touchscreen sensitivity to some extent, causing the poor tolerance in my particular NST to result in inaccurate touchscreen response.
I'll be talking to the manufacturer or the seller (Sears) soon about a replacement unit.
I hope noone else has to figure their way through this with a brand new nook!
Sorry for resurrecting a death thread. But my nook simple touch (which was rooted and had button saviour etc), slowly started having problems with touch. Now since 2 days, touch screen isn't working anymore, no matter how much cleaning I do to the bezels. I can't even open it due to the slider lock screen. Don't know what to do. I would be happy to settle with a button-based navigation, all I want to do is to read epubs. Any help greatly appreciated. I can prob for problems. I have a rooted nst1 which I haven't tinkered since 2012.
If this isn't the right place, I will start a new thread.
TIA
Forthe55 said:
Sorry for resurrecting a death thread. But my nook simple touch (which was rooted and had button saviour etc), slowly started having problems with touch. Now since 2 days, touch screen isn't working anymore, no matter how much cleaning I do to the bezels. I can't even open it due to the slider lock screen. Don't know what to do. I would be happy to settle with a button-based navigation, all I want to do is to read epubs. Any help greatly appreciated. I can prob for problems. I have a rooted nst1 which I haven't tinkered since 2012.
If this isn't the right place, I will start a new thread.
TIA
Click to expand...
Click to collapse
Have you tried swiping two fingers across the screen from right to left? This is not my original idea but someone else long ago delivered me from your situation with this simple tip. If I ever knew the explanation, I have forgotten it. Probably something with the multi-touch kernal. It will even work on an unresponsive lock screen. I still use it on occasion, so something triggers the behavior, but it is generally infrequent.
If that doesn't work to restore functionality then something more dire has happened.
Forthe55 said:
Now since 2 days, touch screen isn't working anymore.
Click to expand...
Click to collapse
Your swipe lockscreen may present a problem.
I don't see any entry in the settings on my NST, so I don't know how to disable it.
You can download my Touch-1.0.apk from the signature.
That will help you debug the tricky IR paths.
All the lines should be light gray, darker lines indicate an occlusion.
The corners are always difficult and you may have a line or two dark.
The problems are either dirt on the bezel or the bezel/filter/display coming unglued.
You can install and run it (without a launcher or touch screen):
Code:
C:\>adb install Touch-1.0.apk
C:\>adb shell am start -n com.temblast.touch/.Touch
I am sure that my nook is rooted , but adb isn’t working. May be usb debugging isn’t on. The problem is that I can’t even unlock it past the “drag to unlock” screen. Now I have to find out how to enable adb without having a working touchscreen to install the touch1.apk.
The two finger swipe isn’t working. I used to draw a single finger across the borders clockwise, which used to help calibrate the touch , not working anymore.
Forthe55 said:
Maybe usb debugging isn’t on.
Click to expand...
Click to collapse
Well, you should be able to tell.
There are three ways to interact with a running Nook:
Touch screen
ADB over USB or WiFi
Hardware root console
You seem to say that the first two don't work.
You can also try a factory reset or recovery.
There is the whole OmapLink thread that describes how to unbrick an NST.
Here is the middle of the thread, you might need to read before and after:
https://forum.xda-developers.com/nook-touch/general/root-nook-glowlight-t2853056/page6
I did a factory reset and the nook is at startup screen with the NEXT button, which obviously can’t be pressed. So the touch issue is definitely “hardware-related “. Few days back I travelled to a hot and humid place , carrying my nook and the soft rubber part in the front of the bezel, started coming of. No matter how much I clean the bezel , this time touch isn’t coming back. I am wondering whether there’s any way to disassemble and readjust the ir sensor for touch.
Renate NST said:
The problems are either dirt on the bezel or the bezel/filter/display coming unglued.
Click to expand...
Click to collapse
It's stuck together with the standard super-double-stick tape.
It's hypersensitive to the slightest bending up or down of any of the layers.
Without ADB and diagnostics (like Touch-1.0.apk) it's impossible to figure out which bit of the edge is out of whack.
It sounds like you only have two options:
Get the hardware console working with a 1.8V level shifter and a UART.
(Easy for me, may not be easy for you.)
Use OmapLink to boot an image that has ADB running (like Noogie or CWMR)
and enable ADB on your main image.
I remember rooting it in 2012 with some image burned on my SD card. Is there a way to again root with the help of an SD card without involving touching the screen with adb enabled rom. That way I can install the diagnostic app and dismantle it to prob further.
Sorry, it's been so long that I forget all this stuff.
Yeah, if you put Noogie on an SD card, I believe that it will boot from there.
With the OmapLink and Windows 10 it can be a bear sometimes to get the three (all the same) drivers working.
Windows 10 is really crappy on recognizing/capturing USB devices that appear briefly.
I can't get W10 to see 0451/d00e
My Raspberry Pi grabs it immediately:
Code:
[ 60.061477] usb 1-1.3: new high-speed USB device number 4 using dwc_otg
[ 60.202744] usb 1-1.3: New USB device found, idVendor=0451, idProduct=d00e
[ 60.202756] usb 1-1.3: New USB device strings: Mfr=33, Product=37, SerialNumber=0
[ 60.202766] usb 1-1.3: Product: OMAP3630
[ 60.202774] usb 1-1.3: Manufacturer: Texas Instruments
[ 63.348937] usb 1-1.3: USB disconnect, device number 4
It appears for 3 seconds from a cold power up, that's too quick for W10 to do anything.
I saw a video on YouTube on screen replacement, with complete disassembly and assembly. Opened the nst , took out the screen from the bezel (keeping the screen and the aluminium metal frame intact, too much sticky tape there), wiped everything clean, reassembled everything back. Still the same problem. I am wondering, even if I somehow get to install and run the diagnostic app, what kind of hardware alterations we need to do. Since the infrared touch LEDs are on the back of the motherboard, what kind of alignment would be necessary.
Is it to the metal frame or the plastic bezel, do we need to tinker?
Did you use new tape?
I think that everything has to be really tight and old tape seems to leave gaps.
There is also the possibility that the MSP340 has lost its mind.
I'll have to look at my oldest NST.
I haven't detached the screen from the metal frame. But the screen attachment to the front bezel seems to be attached to a plastic ribbon which was partially coming out of the front frame. It was sticky so I reattached the screen/metal frame back to it the front plastic part. Now when I see the screen up front, the bezel space/gap between the screen and the black plastic part is uneven. I don't thing that can be repaired as the front black part is disintegrating. Three of my four page turn buttons are no more attached to the frame, I have kept them there with tape.
Well, I completely cleaned with Goo-Be-Gone and isopropyl alcohol the bezel, the filter and the display.
I redid everything with 4mm Tesa film: https://www.microcenter.com/product/507366/tesa-double-sided-tape-4-mm-wide
The horizontal spans (except for the corners) are good, the vertical spans are still problematical.
You can lightly press and warp the bezel and things go in and out.
I think that I'm throwing in the towel on this one.
Reasons to dump the NST: Android 2.1, 256M RAM, OMAP3621 not being further developed by B&N
Reasons to keep the NST: Only Nook with a bare eInk (no backlight layer, no capacitive layer)
Don’t know about the filter, but the bezel looks very fragile to handle. I also believe that the time has come to retire it. But what I liked the most about nst was it’s screen and ability to side load books via wifi. I had gmail and opera mini installed on it. All I needed was to send a link to gmail to download the book, after the Dropbox support was gone. I am searching for a similar ebook reader. Can’t decide between Kindle paper white(which is available locally) and nook glow light 3(which has to be imported). Any suggestions welcome.
Well, the "filter" or "lens" or "light pipe" is what I'm calling the flimsy green translucent piece.
I've never even looked at the Kindles. I don't want to get involved with that whole ecosystem.
The Glow3 is physically almost the same as the NST.
I've got enough devices with browsers on them.
I use my Nooks with WiFi off and sync with USB (ADB & AdbSync).
Hi,
I have recently bough a Nook Simple Touch with Glowlight (BNRV350). Used, no guarantee. It looks fine (has only a minor scratch on the light dispersing layer). Problem is - the lower half of the touch sensors give misplaced readings. For example - during the registration process I cannot get through the language selection screen. I can correctly mark English, but when I want to press an arrow to go further, Nook changes my mark to French, instead of getting me to the next screen. Cleaning borders of the screen with microfiber cloth and cotton swabs did not help.
I have another NSTG working fine, so:
1. I tried to copy its stock system backup and loading it to malfunctioning one. It didn't help. I could not even unlock the screen (although I could press "power off" or "cancel" buttons after holding power button).
2. I tried swapping mainboards (IR sensors are on them, not in the screen assembly). And It turned out, that wherever mainboard of the faulty unit is, the touch does not work properly. I tried to blow out the dust from those misbehaving sensors hoping that it just somehow got on the motherboard, but it did not help either.
So the question is: What else can I do to make those IR sensors work properly?
Thanks in advance for looking into the problem!
(Sorry for my English, I'm used to reading, not to expressing my thoughts with it.)
Maybe try to look on the sensors with a cellphone camera in dark room-then probably you will see which of the ir leds aren't working (if the problem is in leds not the sensors)
Sent from my Lenovo P780 using Tapatalk
Unfortunately I couldn't find any camera able (tried mobile phone, point'n'shoot, DSLR...) to detect IR in their stock configuration (and messing up with disassembling the sensor filters seemed as not worth the case). I ended up buying another NSTG with shattered eink screen and salvaging its properly working mainboard (+completely fine battery, all for about $7). Problem solved. Kind of.
If you are having problems with the touch screen try using the app posted here:
http://forum.xda-developers.com/showthread.php?p=52723066#post52723066
It may give you insight into where the problem is.
It will help us get an idea of where problems are occurring.
Thank You. I've read about Your program, but since I could not even unlock the screen or get past registration wizard (when trying to get that unit to factory state) I was unable to use it.
The Menu button (when you mapped) gets past the swipe.
You can start stuff with ADB intents.
Hello,
Since a few days, the touch input of my front (LCD) screen stopped working. Nothing looks damaged, the screen still displays what it is supposed to, but there is no reaction to my inputs (actions on volume and power buttons do work, as well as on the e-ink screen). Did this happen to any of you? Any suggestion on possible ways to fix it?
I should also mention that it still works by moments, like half a day working, then 2 days not responding, etc. I tried shaking it in different ways should a connector be slightly displaced, with no success: the few times it started working again came like a (good) surprise. I also had the great idea to do a factory reset, so now the phone is stuck on the Android configuration wizard, which must be done on the front screen (no possibility to use YotaMirror, apparently).
Thanks!
wicoz said:
Hello,
Since a few days, the touch input of my front (LCD) screen stopped working. Nothing looks damaged, the screen still displays what it is supposed to, but there is no reaction to my inputs (actions on volume and power buttons do work, as well as on the e-ink screen). Did this happen to any of you? Any suggestion on possible ways to fix it?
I should also mention that it still works by moments, like half a day working, then 2 days not responding, etc. I tried shaking it in different ways should a connector be slightly displaced, with no success: the few times it started working again came like a (good) surprise. I also had the great idea to do a factory reset, so now the phone is stuck on the Android configuration wizard, which must be done on the front screen (no possibility to use YotaMirror, apparently).
Thanks!
Click to expand...
Click to collapse
i recommend reflash it. possibly and more strongly recommend to flash the same version and region which was installed for example HongKong 4.4.3 baseband number .HK1.0.36a
ftp://fw.ydevices.com/YotaPhone2/Firmwares/
Actually, I forgot that the front screen was replaced several months ago (by a repairer that mistakenly changed the front screen instead of the e-ink one which was having an issue).
The factory reset didn't improve the situation, the front screen becoming "touch-insensitive" every few days. After checking how the screen connectors are supposed to be plugged (opposed to the screen), I noticed that gently tapping the phone front screen down helped to solve the issue each time it happened. A few days ago, I finally opened the phone (quite easy, there are two useful videos online) and unplugged/replugged the screen connector. It has been working fine since then.
If it happens to anybody (who would have its front screen replaced), I hope it can help!
Here's the issue:
Intermittently, the screen is blank (I still see the back light come on) but the phone is still responsive. OK Google works, bluetooth car stereo connection works, and if I know where to touch, I can still snooze my alarm and unlock the phone! So, it's functioning, just not DISPLAYING anything.
I haven't tried a full factory reset yet, as it seems like a hardware issue. I searched many threads that had people taking it back for replacement (not an option, it's way off warranty), and generally not solving the problem.
After some extensive searching, I found this hidden in another thread:
" brought it to a shop, they gave it a light twist and the screen came back fine and was in the setup wizard (as I had remotely reset it)."
Sure enough, a twisting action seems to affect the phone screen being on. Given this poster's experience, I'm afraid it won't just be the ribbon connector, but I may attempt a repair anyway.
Just wanted to put this out for others having the same issue.