Related
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, long time lurker, but I finally had to create an account because I'm flat out stuck.
I'm trying to fix Nook Color for a neighbour, the screen was cracked so she bought a new and I installed it. It works... "kind of." The touchscreen doesn't work. So, I figured why not try to install CM7.2 on it, maybe it has a driver the emmc (I think that what you call it) doesn't have since the screen might be newer. I don't know, it's the only thing I can think of, I tripled checked all the connections from the screen to the board.
Now the NC never boots of the uSD. The uSD looks great, image applied and packages ready, but after the boot up I get the Nook Setup screen (image attached) and then when I look on the uSD there are additional files (image attached) the NC put on there.
I've create the bootable uSD with the follwing images.
TWRP_2.3.0.2-encore-sdimg.img
1gb_clockwork-3.2.0.1-eyeballer.img
8gb_clockwork-3.0.1.0.img
All three images were tried with both the following commands and on 2 different 8gigs uSD's (PNY/SanDisk), one USB uSD reader and one those uSD in a SD card adapters.
sudo dd if=/Users/x/Downloads/TWRP_2.3.0.2-encore-sdimg.img of=/dev/disk2 bs=1m
sudo dd if=/Users/x/Downloads/TWRP_2.3.0.2-encore-sdimg.img of=/dev/disk2
I'm about to give up, but thought someone here might have another suggestion I can try.
Thanks!
-
rorius said:
Hi, long time lurker, but I finally had to create an account because I'm flat out stuck.
I'm trying to fix Nook Color for a neighbour, the screen was cracked so she bought a new and I installed it. It works... "kind of." The touchscreen doesn't work. So, I figured why not try to install CM7.2 on it, maybe it has a driver the emmc (I think that what you call it) doesn't have since the screen might be newer. I don't know, it's the only thing I can think of, I tripled checked all the connections from the screen to the board.
Now the NC never boots of the uSD. The uSD looks great, image applied and packages ready, but after the boot up I get the Nook Setup screen (image attached) and then when I look on the uSD there are additional files (image attached) the NC put on there.
I've create the bootable uSD with the follwing images.
TWRP_2.3.0.2-encore-sdimg.img
1gb_clockwork-3.2.0.1-eyeballer.img
8gb_clockwork-3.0.1.0.img
All three images were tried with both the following commands and on 2 different 8gigs uSD's (PNY/SanDisk), one USB uSD reader and one those uSD in a SD card adapters.
sudo dd if=/Users/x/Downloads/TWRP_2.3.0.2-encore-sdimg.img of=/dev/disk2 bs=1m
sudo dd if=/Users/x/Downloads/TWRP_2.3.0.2-encore-sdimg.img of=/dev/disk2
I'm about to give up, but thought someone here might have another suggestion I can try.
Thanks!
Click to expand...
Click to collapse
The screen has two components, the lcd display and the the touch matrix (digitizer). Did you replace both?
And sometimes getting an SD to boot can be difficult. See my NC Tips thread linked in my signature and read item A9. Are you sure you are dding to the correct disk partition? Needs to be the whole device.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
The screen has two components, the lcd display and the the touch matrix (digitizer). Did you replace both?
And sometimes getting an SD to boot can be difficult. See my NC Tips thread linked in my signature and read item A9. Are you sure you are dding to the correct disk partition? Needs to be the whole device.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Hey leapinlar, I honestly don't know. It was one assembled screen unit, I've attached an image, the one on the left is the original and the the right side is the replacement, can you tell from the image if the digitizer is included? Thanks!
rorius said:
Hey leapinlar, I honestly don't know. It was one assembled screen unit, I've attached an image, the one on the left is the original and the the right side is the replacement, can you tell from the image if the digitizer is included? Thanks!
Click to expand...
Click to collapse
I've not actually take one apart, so I don't know. You might search for a Nook Color tear down on the web. Seems to me I saw one years ago.
Sent from my Nook HD+ running CM10.1 on emmc.
That is a Nook Tablet, not a Nook Color. That start-up screen will say "Thank you for choosing NOOK Tablet™. We are sure you will love it! Please take a moment to set up your device." for the tablet, and "Thank you for choosing NOOK Color™. We are sure you will love it! Please take a moment to set up your device." for the Nook Color. Look at the text on the back of device under the speaker, and you will see model number BNTV250 or BNTV250a for the tablet, and BNRV200 or BNRV200a for the Nook Color.
Thanks GMPOWER, you are correct, it is a NT and the screen is suppose to be for a NT too. I've found this out from the neighbor after your post. I've attached images of both and it seems that they are the same? I keep hearing about to check if it has a digitizer, but I don't know how or where to look for this...
GMPOWER said:
That is a Nook Tablet, not a Nook Color. That start-up screen will say "Thank you for choosing NOOK Tablet™. We are sure you will love it! Please take a moment to set up your device." for the tablet, and "Thank you for choosing NOOK Color™. We are sure you will love it! Please take a moment to set up your device." for the Nook Color. Look at the text on the back of device under the speaker, and you will see model number BNTV250 or BNTV250a for the tablet, and BNRV200 or BNRV200a for the Nook Color.
Click to expand...
Click to collapse
rorius said:
Thanks GMPOWER, you are correct, it is a NT and the screen is suppose to be for a NT too. I've found this out from the neighbor after your post. I've attached images of both and it seems that they are the same? I keep hearing about to check if it has a digitizer, but I don't know how or where to look for this...
Click to expand...
Click to collapse
You don't show the front of it, but usually on devices the digitizer is between the glass and the lcd panel. Is it one unit with glass and lcd panel?
Sent from my Nook HD+ running CM10.1 on emmc.
Yes, both are one unit.
leapinlar said:
You don't show the front of it, but usually on devices the digitizer is between the glass and the lcd panel. Is it one unit with glass and lcd panel?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Jump back to the first post. You say it's kind of working. Even though you have installed the completely wrong CWM and ROM for It?
Did the neighbor run CM10 prior to the screen breaking. In that case the multi-touch firmware may have been installed. Make a bootable CM10 card for the correct devices and try again.
Here is a link to a ready-made sd image for the Tablet. PLEASE NOTE THAT THIS IS NOT FOR THE COLOR! http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Sent from my BNTV600 using Tapatalk 4
If you are looking at the front of the screen with the “n” button facing down, the ribbon on the right of the screen is the touch screen digitizer. All Nook Tablets came with the FocalTech FTx06 digitizer, and most Nook Color’s came with the Cypress Semiconductor TMA340 digitizer. Starting with the Nook Color 1.3 firmware, driver support for the FocalTech FTx06 was implemented. A number of blue dot Nook Color’s come with the same FocalTech digitizer as the Nook Tablet. A Cypress Semiconductor touch screen driver is included in the Nook Tablet kernel source code, but I don’t believe fully implemented.
I attached the following pics of the Nook Color, and Nook Tablet digitizer semiconductors chip. The Nook Color digitizer is the one with 8CTMA340-48LQI-01 CYP644895 PHI written on the chip, and the Nook Tablet digitizer is the one with FT5406EE8 ERE344D K01 written on the chip. If the digitizer in your neighbor’s device is the Cypress chip, it will most likely never work without some work to implement the correct driver into the kernel. She will need to try to return digitizer that she purchased, and get the correct one. Tell her to ask the seller next time before she purchases to verify that it has the correct FocalTech digitizer. If the digitizer is the correct FocalTech digitizer, and all connections are correct, then she should return the faulty one, and get another one that works.
GMPOWER, I think you got it! The one the neighbor was sent it a CYP512226. Last question, if she was to exchange it can it be for any FTxxxxxxx or is there a specific series to ask for? Thanks for the help.
GMPOWER said:
If you are looking at the front of the screen with the “n” button facing down, the ribbon on the right of the screen is the touch screen digitizer. All Nook Tablets came with the FocalTech FTx06 digitizer, and most Nook Color’s came with the Cypress Semiconductor TMA340 digitizer. Starting with the Nook Color 1.3 firmware, driver support for the FocalTech FTx06 was implemented. A number of blue dot Nook Color’s come with the same FocalTech digitizer as the Nook Tablet. A Cypress Semiconductor touch screen driver is included in the Nook Tablet kernel source code, but I don’t believe fully implemented.
I attached the following pics of the Nook Color, and Nook Tablet digitizer semiconductors chip. The Nook Color digitizer is the one with 8CTMA340-48LQI-01 CYP644895 PHI written on the chip, and the Nook Tablet digitizer is the one with FT5406EE8 ERE344D K01 written on the chip. If the digitizer in your neighbor’s device is the Cypress chip, it will most likely never work without some work to implement the correct driver into the kernel. She will need to try to return digitizer that she purchased, and get the correct one. Tell her to ask the seller next time before she purchases to verify that it has the correct FocalTech digitizer. If the digitizer is the correct FocalTech digitizer, and all connections are correct, then she should return the faulty one, and get another one that works.
Click to expand...
Click to collapse
She will need to get the Nook digitizer using the FT5406EE8 chip. The driver in the source code is specifically written for that one.
The FT5x06 series of digitizers consists of three different chips, FT5206GE1, FT5306DE4, and FT5406EE8. The FT5206GE1 chip is designed for touch panels sized 2.8” – 3.8”, FT5306DE4 is designed for touch panels sized 4.3” – 7”, and the FT5406EE8 is designed for touch panels sized 7” – 8.9”.
Bought new yoga 10 HD+. Everything seems to be really ok with it except the display. Colors are extremly oversaturated and are falling deeply into reds, especially on skin tones. Actually, all of the photos with people on them look like there is definitely something wrong with them - see the image attached (yoga at the bottom, all screens set to max brightness).
Is there anything wrong with my model and I should return it ? Or it's just a characteristic of IPS display installed on yoga, and if it's display - is there any way to tweak it ? I use my tablet mostly on trips to browse and upload photos. With issue like this yoga is useless for me in this aspect.
I have the exact same issue. I cannot find any app or menu on the tablet that would change the color profile very annoying
Try filter your screen from Google Play..
Bug
This is due to a bug most likely as it happens to more people including me.
https://forums.lenovo.com/t5/Idea-A...e-stand-mode-not-working-without/td-p/1690111
What happens is that the color mode gets stuck on one setting and does not get switched to anything unless yo do a full reboot.
I hate it but not much to do except keep rebooting and waiting for a solution.
~
My Nook STR display looks like it has worn out or faded out.The (black) colour seems worn out , dimmed and heavy ghosting.(even after shut down, see the attached images).I can recover it bit by refreshing the scree (everytime I turn a page) but it is annoying and distracting.And this happen after about 5 min of booting and soon after nook start it look ok (but dimmed a bit)
This started to happen about a month ago and I have been using my Nook for 2 years now without any problem.
To solve this I restored it using the Nook Manager but the problem remains.
Please give me your views and advice. I am suspecting a hardware problem.
Note I don't use any apps like NoRefresher or FastMode.
[I'm new to this thread posting and apology for mistakes]
Thank You in advance
https://my.pcloud.com/publink/show?code=XZRX5RZfborCh0jJ00V1zcOvKWHc7gwGIfy
https://my.pcloud.com/publink/show?code=XZdV5RZEdsmMHOOSfLRcde3suMgH0CrGBR7
https://my.pcloud.com/publink/show?code=XZiV5RZtRpXAJo8To49VJ8B9UtopRqExIW7
https://my.pcloud.com/publink/show?code=XZNV5RZVSgEsKNokHHPGt15BRzBA0J82Pey
Somebody like to help Please
I'm no expert but I can't imagine that something like that is NOT hardware-related.
NookST Student said:
My Nook STR display looks like it has worn out or faded out.The (black) colour seems worn out , dimmed and heavy ghosting.(even after shut down, see the attached images).I can recover it bit by refreshing the scree (everytime I turn a page) but it is annoying and distracting.And this happen after about 5 min of booting and soon after nook start it look ok (but dimmed a bit)
This started to happen about a month ago and I have been using my Nook for 2 years now without any problem.
To solve this I restored it using the Nook Manager but the problem remains.
Please give me your views and advice. I am suspecting a hardware problem.
Note I don't use any apps like NoRefresher or FastMode.
...
Click to expand...
Click to collapse
If the problem remains after you did a "factory restore/reset" then it is most likely hardware related.
My NST had ghosting issue when I was experimenting with FastMode/NoRefresher but it went away after I did factory reset and went with a less exotic kernel hack.
Thank you for your response guys
I think I could zoom in the problem.
I took several screen shots using the screen shot app in one of these threads
Surprisingly those images are perfect.
I think the software is working fine.
So the problem is in the display or the display driver. And I notice that the e ink display has becomer darker even when the Nook is power off.
Is there any way to test the display driver ?
Hmm, that looks strange.
It's certainly not the frame buffer, but you already proved that.
Dumping the frame buffer will give you a nice, clean shot.
It could be that the (plug-in) display itself has a problem.
It could be that the voltages out of the (electronic) driver are screwed up.
It could be that the VCom or the EPD waveforms are screwed up.
The first thing that I'd try would be plugging in another display.
I'd also check the dmesg to see if something happened.
You should see stuff similar to this (editted) version:
Code:
DSPTrace:=== DSP: Load waveforms for t = 25 ===
DSPTrace:=== DSP: EINK parser version 1.07 (MV5) ===
DSPTrace:-I- Mode Version: 0 INIT, 1 DU, 2 GC16, 3 GC16(r), 4 A2, 5 GL16, ...
DSPTrace:-I- WMTA = 000047 (hex)
DSPTrace:-I- Ranges: 0-3-6-9-12-15-18-21-24-27-30-33-38-43-48
DSPTrace:-I- [4] Loaded ID = 5, t = 24 - 27, Subframes = 38
Thank you Renate
I checked the dmesg log and found this part is different
DSPTrace:=== DSP: Load waveforms for t = 29
I am not an expert so I attached the log.
Testing with another display is the most reliable method but that takes time as I have to import one from China.:crying:
So is there anyother way to check the display driver ?
I checked the display cable it is perfect. I am really confused but also VERY curious to figure out this mystery
More pictures of disembled display ( isn't is look strange the ghosting even when no power)
No, your dmesg log looks fine.
It's just that your room is warmer than mine!
It looks pretty low-level, driver voltages or display.
I'm sure somebody who works for the display manufacturer could tell you in a second exactly what it is.
Renate NST said:
No, your dmesg log looks fine.
It's just that your room is warmer than mine!
It looks pretty low-level, driver voltages or display.
I'm sure somebody who works for the display manufacturer could tell you in a second exactly what it is.
Click to expand...
Click to collapse
Thanks Renate
I think the only way to check (or solve) this issue is to plug a new display.
I was reluctant to spend on a display (nearly $25):crying:
But I ordered one from ebay and now waiting for it .
However, do you think the weather has any effect on the eink displays ?
I found a similar thread from mobileread forum. One poster reports a similar issue with kindle and sony readers.
Permanently screen fading over time problem in e-ink readers - MobileRead Forums
Several posters say they are in Asian countries.So I am also in asia (Sri lanka) So I wonder whether there is a connection.
I could tell you to fiddle with the EpdWaveforms and stuff, but that is a bit of black magic.
Your waveforms are apparently happy and loading.
I don't remember if B&N really set the Vcom on their devices before they left the factory.
The good thing with playing with the Vcom is that it's easily editable.
You said that you took your Nook apart.
Did you see the sticker on the back of the Epd connector?
That tells you the common voltage to the panel, around -2 Volts.
(The barcode says the same thing in Code128B, "-2.25".)
That should correlate to the value in /rom/devconf/epdVcom
You can try changing it if it doesn't.
It probably won't make a big effect, this is more fine-tuning for gray scale.
In my case:
Code:
echo -n "-2250" > epdVcom
(The number is in millivolts, with a minus sign.)
I dunno, put your Nook in the fridge and see if other waveforms work better.
The voltage is the same Renate. But I don't think there is a problem with the Rom and other software stuff.Because I did a complete system restore and the problem remains.
What really bug me is whenever I boot it (or reboot) the screen become ok with clear text.But after about 10 min (this time varies) the problem happens.
I think it is difficult to troubleshoot without a new screen.Plus I haven't seen people complaining about faulty motherboards.This makes me hopeful. (correct me if I am wrong on this)
Anyway Thank you Renate for your time and effort I saw you always trying to help many posters here. Keep up the good work!
Update
I got a brand new display from a ebay seller and my Nook is better than a brand new.
The fading issue is in the display.
The new display is whiter and has better contrast than the orginal one.
The best thing is I can use Renate's Temblast Reader without complete Refresh.
I don't know whether the new display has high DPP but I am more than happy.
I think the weather has an effect on Eink displays.
Thank You Everybody for your kind consideration and advice specially Renate. (Renate look forward to see an updated version of your fantastic Reader app with dictionary and bookmark)
Hi all
I've been an original NST user for years now and love it, but the poor beast is getting very tired now and could do with a rest. So, I'm thinking of getting either the GL2 or GL3.
I was wondering which model people preferred? I know they're both Android 4.2.2, but is that as far as the similarities go? Am I right in thinking that the GL2 has a capacitive touchscreen and the GL3 uses the old-style IR sensors?
I think it's likely I'd do the SD card mod on whichever one I choose, plus any other recommended mods (hardware and software).
Thanks in advance
Alex
I've been using my Glow2 as my main reading device for years.
I picked up an extra or two on ebay.
I like that the bezel is flush and therefore doesn't catch dust.
You can just wipe it on your pants.
However, the capacitive screen has problems with being touchy and sometimes major screen updates will activate it.
I have Glow3's with the infrared interrupter similar to the NST.
Both of these are sensitive to dust accumulation on the edges.
You need to run a damp cotton swap around the edges to clean the IR transmissive layer now and then.
Then there is the issue of the shadow on the screen caused by the thick bezel.
With these IR touch, the NST had access to the driver so you could see what it was seeing.
There is Touch-1.0.apk in the signature which shows you where the IR beams are broken, helpful when cleaning/troubleshooting.
The Glow3 has a different driver and the info is not available.
Finally, if you use the Glow2 for a long time you might notice that the Glow3 has a little better contrast because there is no capacitive touch layer in front of the eInk screen.
Both the Glow2 & Glow3 (& Glow4) allow soldering in an SD card, but the Glow3 requires a kernel patch.