Database Users

Changing screen size/dpi

In the dev options there's an input field 'smallest width' - set it to like 450px, then in accessibility change text size to large or huge, whichever is best for you.

You can also do this through ADB.
To retrieve the current density:
adb shell wm density
Click to expand...
Click to collapse
To set a new density (replace 450 with desired density):
adb shell wm density 450
Click to expand...
Click to collapse
You should force quit the launcher (or reboot) after you update the density... Sometimes it doesn't react well to the change.

sevnsevn said:
You can also do this through ADB.
To retrieve the current density:
To set a new density (replace 450 with desired density):
You should force quit the launcher (or reboot) after you update the density... Sometimes it doesn't react well to the change.
Click to expand...
Click to collapse
What else can you do through adb that you can't do through settings?

I just wanted to confirm that this works up to 450 (auto changes to 449), however when doing this, it glitches out the dock some times where the icons get condensed in the middle, but on reboot they go back to normal until an app is opened, any higher than 449dpi and the phone completely glitches out, at 480 the labels in the app draw start to get cut off, and at 500 the app drawer won't even open.
This is just from testing on mine, which is a Pulse colour model (known to have way more issues than Eclipse Black) so your mileage may vary.

bANONYMOUS said:
I just wanted to confirm that this works up to 450 (auto changes to 449), however when doing this, it glitches out the dock some times where the icons get condensed in the middle, but on reboot they go back to normal until an app is opened, any higher than 449dpi and the phone completely glitches out, at 480 the labels in the app draw start to get cut off, and at 500 the app drawer won't even open.
This is just from testing on mine, which is a Pulse colour model (known to have way more issues than Eclipse Black) so your mileage may vary.
Click to expand...
Click to collapse
I have this same problem on my Redmagic 6. Did you find any solution to this? Also, dial pad in phone app slides to the left side when I change width value.

OnePlus 6T Navigation Gestures

The navigation gestures on the 8 Pro are usable. However, I dislike the swiping to go back. It doesn’t allow for access to slide out menus from the side on different apps. On the 6T, you would swipe up on the right or left hand side to go back keeping the sides of the screen free. Is there anyone who would be able to somehow pull the navigation gestures that were on the 6T to be used on the 8 Pro?

I had asked this twice already and so far I've been told it's not possible just downloaded fluid navigation gestures and set them up and you're good to go.

There are alternatives when it comes to the swiping (All in one gestures/Vivd etc.) They do that job well in my opinion.
The thing they all have in common is that they need that area in the bottom to function, and for my case that messes with the lower end of my keyboard.
I enjoy having the swiftkey keyboard dragged down all the way to the bottom of the screen.
If someone is able to pull the OP gestures and somehow make it available as a module or whatever, I would surely donate some coffee..
This is almost a dealbreaker, and I miss my 7 Pro which also have them.

666syco said:
I had asked this twice already and so far I've been told it's not possible just downloaded fluid navigation gestures and set them up and you're good to go.
Click to expand...
Click to collapse
Were you able to set them up in a way that operates the same? Does it seem to work well and reliably/consistently?

WyldOne91 said:
Were you able to set them up in a way that operates the same? Does it seem to work well and reliably/consistently?
Click to expand...
Click to collapse
the application itself one setup does perform like the regular OnePlus just the sensitivity area of where you're swiping up from kind of makes it like a dead zone for touching on other spots underneath the swipe area. But you can configure your sensitivity area I have mine set to a little bit of past half so this way I get the best of both I get my swipe gestures and I can still access the stuff that's underneath them. I also left the right side back gesture available so this way if it doesn't function properly on the bottom I still got the side.

666syco said:
the application itself one setup does perform like the regular OnePlus just the sensitivity area of where you're swiping up from kind of makes it like a dead zone for touching on other spots underneath the swipe area. But you can configure your sensitivity area I have mine set to a little bit of past half so this way I get the best of both I get my swipe gestures and I can still access the stuff that's underneath them. I also left the right side back gesture available so this way if it doesn't function properly on the bottom I still got the side.
Click to expand...
Click to collapse
Are you able to use root to hide the system navigation bar? It hides it for a second for me but it doesn't stay hidden which is frustrating. Unless that's a pro feature?

WyldOne91 said:
Are you able to use root to hide the system navigation bar? It hides it for a second for me but it doesn't stay hidden which is frustrating. Unless that's a pro feature?
Click to expand...
Click to collapse
Use vivid N.G.

WyldOne91 said:
Are you able to use root to hide the system navigation bar? It hides it for a second for me but it doesn't stay hidden which is frustrating. Unless that's a pro feature?
Click to expand...
Click to collapse
Yes you can here is a screen shot of mine all set up and nav bar hidden with root. Here is how mine is all set up I set my wife's the same way she likes it and is new to OnePlus this 8 Pro is her 1st she was looking forward to OnePlus system navigation gestures but you know no dice. Mine stayed hidden all the time after I set I rebooted and haven't had a issue yet.

My set up on FNG

666syco said:
My set up on FNG
Click to expand...
Click to collapse
Cool, thank you for the input!

Guide for Calibration Finger Print after loss data calibration

Guide for calibration FingerPrint for Red Magic 5G
After unlock bootloader .. some people may loss data calibration and some people could get it back simply just by locking the bootloader,
but if you want to get ur finger print back to work for both bootloader unlock and bootloader locked after loosing data calibration
You have to do same like instruction below:
- Dial *#9959# (dont allow data memory and clear data in system app In-Display FingerPrint)
- uncheck performance checkbox , check only calibration checkbox
- 4 step for calibration
All steps shall be in dark place
1. Press START and dont press anything it will pass
2.Press NEXT and by lattice glove press on circle it should pass
3.Press NEXT and put some anything black non reflectuvec( the display became black for calibration of the black) and it should pass
The fourth step the hardest u may fail so many times
4.Press NEXT and by thumb finger almost in vertical position press on circle(keep the thumb well pressed the initial part of the finger and slightly raised on the knuckle must be vertical in the straight direction not horizontally or slightly)
Note fourth step u may fail and repeat from begining u may reach 20 trials or more dont get bored u will success
If you are lucky see success alert in green color
In system app in setting In-Display-Fingerprint allow access data memory and reboot device .
Enjoy again your Finger Print!
P.S. = doing this procedure in a place in total darkness, there must be only the light of the display
In 4 step the finger must cover the darker part of the circle (for this I say to raise it slightly) and it must be well pressed but not too strong.
For test I used before unbricktool NO EU after I did ota update to 3.13 ,note in "in display finger print" system app you must have 3.91MB without cache and user data only for app this is very important also delete cache and data.
This procedure isn't professional but effective!

Realy appreciate the way you explained the process thanks bro it worked for me for bootloader unlocked ??

Step 4 is making me want to throw my phone at the wall lok

I notice you have actual values for each of your tests.... Mine always come back 0s

i'm having the exact same issue on the oneplus 7tpro 5g mclaren. same deal, calibration data gets shot when you unlock bootloader. ive been working on LOS bringup and have everything working but fod. I tried the calibration tests but it fails at black_rubber_sleve test. our app looks different then yours. How did you figure out the procedure? could we maybe get together and you could help me?

viper98 said:
I notice you have actual values for each of your tests.... Mine always come back 0s
Click to expand...
Click to collapse
This error may depend on the brightness of the place where you are doing the calibration and above all on the position of your thumb and the pressure you apply on the rim.

albinoman887 said:
i'm having the exact same issue on the oneplus 7tpro 5g mclaren. same deal, calibration data gets shot when you unlock bootloader. ive been working on LOS bringup and have everything working but fod. I tried the calibration tests but it fails at black_rubber_sleve test. our app looks different then yours. How did you figure out the procedure? could we maybe get together and you could help me?
Click to expand...
Click to collapse
This procedure is for Nubia Red Magic 5g ,dont know that for your device because dont should test it.

Can you show us the right way and make a video

Anaswish said:
Can you show us the right way and make a video
Click to expand...
Click to collapse
no but i already calibrated my finger print if you follow well all step and notes you will recovery FP. Many people restored with success.

Does anyone have any better tips on how to do step 4?
I've tried north of 50 times and can't proceed

A video... Dont Work for me. Error zoom ratio or get scal ratio. Ty

@s4lv0.88 Can you do me a favour?
Can you check your Drawable setting's Smallest Width for me, and also check the fingerprint scanner placement?
Smallest Width: In Developer options, scroll down to the Drawing category, and you'll find Smallest Width
For Fingerprint scanner position, if you run "adb shell am start -n com.goodix.fingerprint.setting/com.goodix.fingerprint.setting.MainActivity", you can go into "Locate Sensor"
This will really help! Thank you!
EDIT: I've just reached out to the CEO of Goodix, the sensor manufacturer to see if it's possible to get access to at least the specs of the actual calibration weights, or possibly the option to purchase them directly.

gamebenchjake said:
@s4lv0.88 Can you do me a favour?
Can you check your Drawable setting's Smallest Width for me, and also check the fingerprint scanner placement?
Smallest Width: In Developer options, scroll down to the Drawing category, and you'll find Smallest Width
For Fingerprint scanner position, if you run "adb shell am start -n com.goodix.fingerprint.setting/com.goodix.fingerprint.setting.MainActivity", you can go into "Locate Sensor"
This will really help! Thank you!
EDIT: I've just reached out to the CEO of Goodix, the sensor manufacturer to see if it's possible to get access to at least the specs of the actual calibration weights, or possibly the option to purchase them directly.
Click to expand...
Click to collapse
This is:

s4lv0.88 said:
This is:
Click to expand...
Click to collapse
Thank you so much - do you know what your DPI setting is at? The combination of the two allows for everyone to make sure that the fingerprint reader (software) is in the same position as the physical one

gamebenchjake said:
Thank you so much - do you know what your DPI setting is at? The combination of the two allows for everyone to make sure that the fingerprint reader (software) is in the same position as the physical one
Click to expand...
Click to collapse
360 dp

Tried too many times with no luck, step 4 always fails.
If anyone succeeds with this, tips will be appreciated.

I am having the same problem. I went all the way to deleting the Efs file of the phone. I could not find a solution in neither Chinese rum nor global rum. I wrote to Supporta. I saw that they didn't know anything. The thing I'm most sure about this phone is the worst phone in the world when it comes to software. I will never use zte or nubia again and would not recommend anyone to buy it.

Someone who has success in calibration, please send me the in-Display Fingerprint.apk app. I'll just try.

Successfully ! I did it !!! I passed more than 2000 attempts, but without success. I asked my wife to do it, and she did it on the second try ? I knew something was wrong with my finger

3Danger said:
Successfully ! I did it !!! I passed more than 2000 attempts, but without success. I asked my wife to do it, and she did it on the second try ? I knew something was wrong with my finger
Click to expand...
Click to collapse
Bro can u explain what happened exactly! Like is there's any trick ?

Nook simple touch tousch screen unresponsive

Hi I have a nook simple touch. I have factory reset it, and its stuck on the language selection screen as the touch screen is unresponsive.
The nook is on 1.2.1.
I have cleaned the screen with IPA, and used a bush to clean the edges of the screen.
Several months ago I replaced the battery, and its been working well since until now, and I have charged the battery fully.
I can't see any IR beams with my phone - I do see some blinking with a separate IR remote
Would be grateful for any suggestions to fix my nook.
Thanks

Do you have ADB working?
Your problem is that you factory reset it and now you probably have no ADB.
mdwsmith said:
I can't see any IR beams with my phone - I do see some blinking with a separate IR remote
Click to expand...
Click to collapse
Remotes are designed to work at 20 feet.
The NST Neonode zForce is designed to work at 4 inches and use the minimum of power.
When not actively being touched it only flashes periodically a single (or two? I forget) LED (instead of 26).
It's the lower left corner.
There's an app for the NST in my sig called Touch-1.0.apk
It will show a diagram of the rays and show which ones are blocked.
Most of the lines should be light gray.
Dark or dotted lines are occluded.
You may have one or two of those on the edges.
It's hard to get the bezel aligned nicely.
Use a cotton swab on the edges, the screen itself hardly matters.
When I fire up my old NST I usually have no touch sensitivity until I clean the bezel.
Code:
C:\>adb install Touch-1.0.apk
C:\>adb shell am start -n com.temblast.touch/.Touch
First thing, try a cotton swab with water going around the bezel.
Use a couple wet, then one dry.

mdwsmith said:
Hi I have a nook simple touch. I have factory reset it, and its stuck on the language selection screen as the touch screen is unresponsive.
Click to expand...
Click to collapse
Seems odd that you got to that point, presumably using the touch screen, and suddenly the screen won't respond. A few things come to mind:
1. Is it still on that screen? If so, is it even on? Perhaps the system crashed for some reason and it just left that image on the screen--or perhaps some hiccup caused the device to enter a fugue state. Either way, a forced restart with the power button might be in order.
2. Try swiping two fingers across the screen from right to left. This bit of "finger magic" was related to me a long time ago when I made a post similar to yours. Suddenly my screen would not respond! I thought the proposed "fix" was near ridiculous, but it worked! I've had the same thing happen to me very infrequently, sometimes even on the "drag to unlock" screen just after trying to wake up the device. The two-finger swipe always sorts it.
3. You are on 1.2.1 after a factory reset. I don't remember the setup sequence exactly, but at some point you're going to run into trouble unless you have skipped OOBE. Maybe the device has reached the "trouble" point?

This might be wrong place to ask this question but here it is anyway. I vaguely recall that in some thread were said that it is possible to place current version of software in factory reset partition so that when you are forced to do a factory reset you do not have to do all the upgrades after that. Am I wrong?

SJT75 said:
This might be wrong place to ask this question but here it is anyway. I vaguely recall that in some thread were said that it is possible to place current version of software in factory reset partition so that when you are forced to do a factory reset you do not have to do all the upgrades after that. Am I wrong?
Click to expand...
Click to collapse
This post: https://forum.xda-developers.com/t/nst-nstg-rom-1337-rom-apr-9.2931567/post-59790217 suggests a way to replace the factory recovery when it has been displaced by emmc CWM. Presumably the method could be used for what you suggest--if it is correct.
Although not exactly the same thing, you can come close by doing a factory reset, updating to FW 1.2.2 and then making a backup. NookManager can do all of that without rooting (I think...). I've done this for each of my three devices. As you say, it saves steps.

@renate,
Thanks for your help - I think your correct "Your problem is that you factory reset it and now you probably have no ADB."
I downloaded the platform tools and using
.\adb devices
list no devices.
Whats the best way of gettin adb working - I'm aware some files are missing from the forum.....
Thanks
Marcus

Well, there's a ton of ways to skin this cat.
Me? I'd use OmapLink to boot from the ROM bootloader into ClockworkMod recovery.
Code:
omaplink.exe aboot.bin u-boot12.bin uRecImg uRecRam
If your drivers aren't set up already this can be a bit painful.
Then you can go and mount system and data and configure things how you want.
Code:
# /system/bin/sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=1 where name='adb_enabled';
sqlite> .q
# echo -n 1 > /data/property/persist.service.adb.enable
The problem is that your regular system is working well enough it might be hard to get to a recovery or something on the SD card.
This is the easiest way for me, but @nmyshkin probably knows more ways.

I have a clockwork recovery sd card that I can boot from and adb into. I mounted system and data and tried via the CWM menu and then via windows powershell terminal;
PS C:\Users\mdwsm\Downloads\platform-tools_r31.0.1-windows\platform-tools> .\adb.exe install Touch-1.0.apk
Performing Push Install
Touch-1.0.apk: 1 file pushed, 0 skipped. 29.5 MB/s (11760 bytes in 0.000s)
/sbin/sh: pm: not found
PS C:\Users\mdwsm\Downloads\platform-tools_r31.0.1-windows\platform-tools> .\adb.exe shell am start -n com.temblast.touch/.Touch
/sbin/sh: am: not found
so some success, but I'm guessing cwm does not support running apks via adb?
Thanks Marcus

Oh, so you can get to CWM?
CWM does not include the Android subsystem so you can't use anything that uses that, like pm or am.
You can use things like sqlite3 or Linux utilities to change some things.
CWM does not use the touch screen, but it uses a normal kernel so it does load the drivers.
You can do the following:
Code:
C:\>adb shell
~ # cat /dev/input/event2
�!K���K���K�������
=�����f����J����
J��6
Touch the screen, you'll get something similar if the screen is working.

Hi, Unfortunately my replacement battery after 6 months seems to be faulty, which may or may not be responsable for some of these issues. I'd like to thanks the posters here for supporting me - its much appreciated keeping a 10 year old device going and avoiding waste.
XDA is great for this I have had the nook touch for 10 years, and i still have a nook HD+ still going - like the screen on that one good for comics.
May have to look for another e reader kobo clara looks good but eill have to see ahat supported well by XDA.
Thanks again Marcus

mdwsmith said:
I can't see any IR beams with my phone - I do see some blinking with a separate IR remote
Click to expand...
Click to collapse
Hi there, I'm in a similar boat here with my NSTG. What does your line here mean exactly? Should I be able to see the IR beams shining at the edge of the Nook screen? I haven't used mine in years so I can't remember if I should.

DannySolo said:
Hi there, I'm in a similar boat here with my NSTG. What does your line here mean exactly? Should I be able to see the IR beams shining at the edge of the Nook screen? I haven't used mine in years so I can't remember if I should.
Click to expand...
Click to collapse
reply from renate indicated that even if working the ir beams are liklely too faint to see in a phone camera (which can see IR)

IR remotes are blasters. They put a few hundred milliamperes into an IR LED to work at 20 feet.
The Neonode Zforce sensor works at a couple of inches.
Phone cameras are inherently IR sensitive. That's why they have "IR cut" filters in front. Something has to be pretty bright to blast through. The Raspberry Pi "IR" camera is just a normal camera without the filter. Colors look weird because it's sensing the IR too.
Yes, you can detect the pulsing of the Zforce LEDs but you'll need an IR photodiode hooked up to an oscilloscope.
The lower left corner pulses during idle to see if it has to start doing a full screen scan.
In any case, Touch-1.0.apk can tell you what's going on.
Ha! It took long enough to find this stupid picture.

Strangely, when I was putting in the SD card with NookManager the English language option became selected?!?! I could not reproduce this or any other on screen action.

DannySolo said:
Strangely, when I was putting in the SD card with NookManager the English language option became selected?!?! I could not reproduce this or any other on screen action.
Click to expand...
Click to collapse
?
NookManager is to boot from "power off". If that's how you started it and didn't see the first menu, then the card is defective in some way.
That said, I am not optimistic about using it. My suggestion was predicated on the ability of the adbgrab utility to give you remote touch access via your PC. It now appears that does not work.
It is possible to use series of sendvents via adb to "touch" the screen at specified coordinates but I think that would try the endurance of even the most single-minded enthusiast. Assuming you had some sort of plan to harness the hardware buttons.
I just don't see a realistic way forward without touch access.

Tabbing (slowly) and hitting enter (slowly) should be able to get most controls on a window.

Renate said:
Tabbing (slowly) and hitting enter (slowly) should be able to get most controls on a window.
Click to expand...
Click to collapse
Should is not does.
On the first "tab" press after the mirror of the home screen is displayed the device Search function is activated. That function icon exists nowhere on my home screen. Subsequent "tabs" move the cursor in the search entry field.
Next I tried something simpler like the app drawer (only six options). I opened that from the touch screen, refreshed, and then hit "tab". Lo and behold, device Search opened again.... It's really excited about searching all the books on the device. Again, no such icon in the app drawer.
So returning to the app drawer via the touch screen and refreshing, I hit "enter". The first icon is now highlighted and hitting the right "arrow" key moves the highlighting to the second icon.
Now we're getting somewhere. (but this only seems to work with launcher icons; on the home screen, for example, the status bar icons can't be accessed)
Hitting "enter" again opens the app that is highlighted, but a refresh is needed to make the mirror correspond to the actual device.
(Ha-Ha, PgDn turns on the glowlight...whoops, PgUp takes me back to the home screen...)
So...yeah, you can do some really basic stuff in unexpected ways. But when it comes to really interacting with an app screen, I'm stuck. For example, the attached screenshot. The up and down arrow keys scroll from top to bottom of the list and back. But there appears to be no way to select an individual item (no..."tab" opens device Search...). Not that the user would be wanting to get a crossword puzzle, but the problem of getting your desired input across to an app in this way is significant.
Out of curiosity I opened the NookTouch ModManager app which I had previously suggested to the user as a way to harness ten function options from the hardware buttons. But once I got it open using the utility, I had no way to navigate the screen to choose the options I wanted, not even on the opening screen with just two large menu bar selections, similar to the crossword item display.
So I can't see this working for him. It has potential, but unless there is further magic I am not getting, it just won't do the job.
And BTW, Touch-1.0.apk does not run properly (at least not for me). It seems to crash back to Home without doing or displaying anything.

Did you try the arrow keys?

Renate said:
Did you try the arrow keys?
Click to expand...
Click to collapse
Yes.
"The up and down arrow keys scroll from top to bottom of the list and back. But there appears to be no way to select an individual item."
That does not mean scrolling down the list one item at a time, rather that the entire list shifts. No indication that any single item is targeted. "Enter" has no effect there.

NSTG - options with a broken IR array.

Hi all. After buying a Kindle (booooo) for somebody for Christmas I remembered the broken NSTG I had in a box for years. It was given to me broken after a hard fall and the screen was kaput with just a lot of horizontal line and the occasional "ghosting" if you pressed the physical buttons. I couldn't really tell if the touch was working because the screen was so bad.
Anyway, I bought a replacement screen which was definitely for a NSTG... but the ribbon for the glow connector was in the wrong place (I bet there's several revisions a noob like me just didn't know about) so I abandoned it.
So just now I've attached this screen anyway and it works great, looks beautiful... but the touch doesn't work. I'm sure I'm not blocking the IR array and everything fits back together nice and tight. I don't see anything on the PCB but does the IR commonly break with a fall?
Assuming I now have a NSTG which is really just an N... is there any future for this little thing? How much can I do with it purely via the USB port? If I could even open a book on it and read using the physical buttons it would be somewhat useful, or I see other people turn these into display screens for messages etc.
Any ideas welcome!

I've never had a NST*G*.
Do you have ADB working?
You can use my diagnostic app Touch-1.0.apk in the sig.
It will show you if anything is responding.
If you have ADB working you could use AdbGrab.exe which will mirror the screen and let you click.
I'm not sure if they ever fixed the screen format problems on the NST/G.
The NST/G sort of had USB host mode, but it's not the easiest thing to get working without touch.
You certainly need either ADB or touch.
I use a Glow3 as a status display. You could do that.

Renate said:
I've never had a NST*G*.
Do you have ADB working?
You can use my diagnostic app Touch-1.0.apk in the sig.
It will show you if anything is responding.
If you have ADB working you could use AdbGrab.exe which will mirror the screen and let you click.
I'm not sure if they ever fixed the screen format problems on the NST/G.
The NST/G sort of had USB host mode, but it's not the easiest thing to get working without touch.
You certainly need either ADB or touch.
I use a Glow3 as a status display. You could do that.
Click to expand...
Click to collapse
Thanks for reply. I've used ADB before for Android phones, is that what you mean? Like I said, if I could get the Nook to page 1 of a book via ADB I'd be very happy because then I could use the physical buttons to change the page.
If the screen mirror app allows control then that would be cool and really resurrect this old thing!

Yes, by ADB, I mean ADB.
It's kind of hard to turn on now if it wasn't on already.

DannySolo said:
Thanks for reply. I've used ADB before for Android phones, is that what you mean? Like I said, if I could get the Nook to page 1 of a book via ADB I'd be very happy because then I could use the physical buttons to change the page.
If the screen mirror app allows control then that would be cool and really resurrect this old thing!
Click to expand...
Click to collapse
If you root with NookManager (all actions with hardware buttons), you could use the NookTouchModManager apk to assign functions to the hardware buttons (using the adb utility to make the selections). That would give you 10 actions (regular and long press).
Is that enough to read and run the library? Maybe. You'd have to play around.

Renate said:
If you have ADB working you could use AdbGrab.exe which will mirror the screen and let you click.
Click to expand...
Click to collapse
I can get the screen to mirror, but there is no response to clicking with the Windows pointer. Maybe not for Android 2.1?

Oh, yeah, "input" didn't get "tap" until later.
Does tab key and enter do it?
Arrows, PgUp/PgDn, Home, Escape, Enter...
F5 refreshes the Windows screen in case a command took too long and you only have an interim screenful.

Renate said:
Oh, yeah, "input" didn't get "tap" until later.
Does tab key and enter do it?
Arrows, PgUp/PgDn, Home, Escape, Enter...
F5 refreshes the Windows screen in case a command took too long and you only have an interim screenful.
Click to expand...
Click to collapse
No, it's pretty funky. "Tab" (with or without anything else) invokes device search. "Home" seems to work. Sort of. Arrow keys crash the program. Not sure about pgup and pgdn. Sort of like tapping on a blank spot on the screen. "Enter", for me, first highlights then eventually opens one of the launcher folders.
So it's pretty random. Touch input on the screen is not reflected on the mirror without F5.
Looks like this would not get user where he would need to go.
Without touch, the device is pretty much cut off from the world except for interaction with the hardware buttons (or, more cumbersome for routine use, ADB). I'm sure someone could come up with a display use that would rely on the buttons for user interaction of some kind, but that would take some programming.
Edit: BTW, Touch-1.0.apk does not run correctly on the NST/G as far as I can tell. There is some screen flashing and then back to the home screen. Logcat is pretty complex (and lengthy). Nothing jumps out at me.

Don't hit the buttons too fast. This is not a robust thing.

nmyshkin said:
If you root with NookManager
Click to expand...
Click to collapse
I'm only reading the instructions in the FAQ but this seems to require some touch selections during the install from SD card.
Edit: OK I've done the backup and root. I can not get screen grabs over to my PC via ADB. But I can't interact with the screen so I can't click anything.
When I was fiddling with the SD card I accidentally selected English from the language menu... but I could not reproduce this with any amount of manipulation. Maybe the IR isn't completely dead at all?

Looks like the end of the line then for this Nook. The thing I really like about it is that it has physical buttons so I don't need to touch what I'm reading. I might go to ebay and buy a second hand one!
Thanks anyway.

Clean the bezel really well. A wet cue tip all around the inside. A dry cue tip to dry. Repeat.

Renate said:
Clean the bezel really well. A wet cue tip all around the inside. A dry cue tip to dry. Repeat.
Click to expand...
Click to collapse
OK I didn't give up just yet. I scrubbed the bezel within an inch of its life but it didn't help. BUT now I've taken off the back and when I pinched the bezel in one particular place the touch is fixed! But only while pinched. The bezel or PCB or something must be warped in some fashion? I notice right behind the "sweet spot" around the power button there are two rubber pads that push into the PCB, maybe they aren't doing their job correctly?
Anyway, now I have a somewhat reproducible way of registering touch I can try to do the FACTORY route and get to the homescreen.

Yes, the bezel position is very tricky.
You can try taking it all apart and using new 4mm double-sided sticky tape.
It will probably end up worse than you started.
If you try, definitely have ADB working already so that you can start Touch-1.0.apk for troubleshooting.

Renate said:
Yes, the bezel position is very tricky.
You can try taking it all apart and using new 4mm double-sided sticky tape.
It will probably end up worse than you started.
If you try, definitely have ADB working already so that you can start Touch-1.0.apk for troubleshooting.
Click to expand...
Click to collapse
I have gotten to the point of a book being displayed! Now at least I can use the thing as a reader!
It isn't obvious to me what is the correct spacing to have between the screen and the IR black bezel (bambadam) and I thought I had it really well centred. Maybe not though and could be worth redoing.
I can push that touch app using adb now? Do I do that in RootManager or at any time at all?
Thanks for the help, real signs of life now!

DannySolo said:
I can push that touch app using adb now?
Click to expand...
Click to collapse
Yes, just adb install Touch-1.0.apk

Renate said:
Yes, just adb install Touch-1.0.apk
Click to expand...
Click to collapse
I've done that... but where is it? There's no apps in the regular launcher. I see "Home" and "Relaunch" and neither have an app tray.
Maybe I need to do something else.

I dunno. Try this: adb shell am start -n com.temblast.touch/.Touch

This app is super. Why did I think the IR array was just a grid? Anyway I now see the left-right works fine all the time but the up-down has some line that seem permanently on and others that can be activate with the same pinching the bezel trick.
My first guess is there's a block at the top of the screen somewhere and the up-down isn't registering because there's a sensor always on?

Do a screen grab.