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.
Related
Renate NST suggested I post this in this forum
To all the developers - Thanks in advance for all the GREAT work!
The Saga
Installed touchnooter-2-1-31 and NST hung on install.
Waited an hour and rebooted
NST booted to "walking dots"
Used n2T-Recovery_0.2
Went thru "start-up" dialog (register, etc) and got the machine running again.
Noticed that NST SW was at 1.0
Updated NST to 1.1.2
Installed touchnooter-2-1-31.
Boot screen was "Read Forever"
Android fired up.
Missed the select ADW - should have done that
Button Savior wanted Superuser - should have done that
Buttons on side grayed out
Used n2T-Recovery_0.2 again
did not get me to the "register" start-up dialog
Updated NST to 1.1
Installed touchnooter-2-1-31 again
Boot screen is still "Read Forever"
Same action on buttons - grayed out
So .... my take on this is given the multiple installs I have scrambled something but good.
Is there a way to get to square zero?
Will the erase and de-register do that?
Is there a way to correct the ADW / Button Savior issues?
Is there a way to get to Android despite to side buttons?
Thanks in advance for any help.
The NST works as a reader - so I'm not dead - just wounded
I think you're jumping the gun on doing recovery. When you reboot, aren't you at the ADW Launcher screen? It's been a while since I rooted my NST using TouchNooter (TN), but I believe you can launch the Superuser app after a basic TN root and change the settings for any apps you goofed on (e.g. Button Savior). Just launch Superuser, click the icon of the desired app at left, then click the little android icon at right to toggle the Status between Allowed and Denied.
Erase & Deregister Device in Settings->Device info should suffice to get you back to an unrooted state for a repeat attempt, assuming you can get to it. I've used it many times. If not, power off, then press & hold the lower left & right buttons as you power back on for a few seconds to get a factory reset option. I believe this would have helped you after that first TN hang. You could just retry after a factory reset and reboot. (Haven't had to do this myself, so not 100% sure.)
Download and install Default App Manager from the Google Market to change your default launcher so you can set it to ADW, or whatever you prefer. This works for changing defaults for any app, so is a good thing to keep around.
For the side buttons, do you mean the hard side buttons? You can change those settings with the Side buttons option in NookTouch Tools.
Also in NTT, you can change the 'n' button behavior to take you straight to your home app (ADW) if you don't like the QuickLaunch menu (I do). Be sure to check the Show extra action buttons in recent option, and you'll get Back, Home, Menu, Search and Orientation buttons (just like Button Savior) when you long-press the 'n' button, as well as your most recent apps.
As I mentioned in a separate post, I prefer to use NookTouch Tools to override the B&N QuickLaunch options to eliminate the need for Button Savior or similar apps altogether. Between a QuickLaunch option or two, and the extra options in the recent apps dialog, I've got those options covered. I did remap two of the hardware side buttons to Back and Menu just because they're handy.
I've had very good luck using TouchNooter, but you do have to read the step-by-step directions carefully. There are ways around most problems if you can get to ADW.
Good luck with it!
bobstro said:
I think you're jumping the gun on doing recovery. When you reboot, aren't you at the ADW Launcher screen? It's been a while since I rooted my NST using TouchNooter (TN), but I believe you can launch the Superuser app after a basic TN root and change the settings for any apps you goofed on (e.g. Button Savior). Just launch Superuser, click the icon of the desired app at left, then click the little android icon at right to toggle the Status between Allowed and Denied.
Click to expand...
Click to collapse
It boots to the reader ... buttons are there on the right side, but grayed out and non-functional (no superuser on button.savior)
So .. is there something I can boot from off the SD card that would allow me to
1.) Set ADW as the default, and / or
2.) Give Button.Savior the Superuser permissions?
Erase and Dereg is available as I only have access to the reader and not ADW.
Thanks for the help folks!
Were I the original poster, I would recover from my nonrooted backup image and re-root, or if I could not find it or found it but found that it was not 1.8 gig in size, would force factory reset (first, erase and deregister, then 8 failed, IIRC, to get both /system and /data wiped.)
Once I'd done a full reset, if I'd needed to do it that way, I'd boot from noogie and make my backup.
Then i'd reroot, probably using one of the Clockwork-based tools rather than the Touchnooter system, as it seems that
folks are sometimes seeing TN not quite finish (it happened to me on occasion) and the Clockwork tools seem to be
very robust, enough so that the Glownooter uses clockwork.
I actually like to really baseline something like this and be sure there's no odd cruft hanging out in /system or /data that may confuse me later.
WorkenOnIt said:
It boots to the reader ... buttons are there on the right side, but grayed out and non-functional (no superuser on button.savior)
Click to expand...
Click to collapse
You're definitely seeing some odd behavior. I always wound up at ADW on any reboot.
Erase and Dereg is available as I only have access to the reader and not ADW.
Click to expand...
Click to collapse
You should still be able to get to it via Settings->Device Info. In my experience, erase and dereg was sufficient to make another rooting attempt, but you might want to get back to ground zero. The restore option you've been using, a restore from backup as roust suggests, or doing the 8 failed boot attempts are all options. Be sure to update to whatever version of firmware you want before attempting.
Roust: After you do a CWM noot, what version does Device info show? Mine always shows 1.1.0 after TN, even though I updated to 1.1.2 previously. This has to do with some of the framework tweaking, IIRC. My TN may be old by now.
To all,
Thanks for all your help.
I did an Erase and Deregister.
That appeared to work
Checked firmware - was 1.1.0
Tried to reload TouchNooter (2-1-31)
Screen hung again - like the first time.
Waited 30 minutes and pulled the SD and rebooted.
Boot screen still says "Read Forever"
Went thru the startup dialog and selected the ADW launcher and allowed superuser on the button.savior.
I can now "complete the action" with the ADW launcher and the side keys function.
Everything appears to be working ...
Gmail gets to the account ..
Now why does it still say "Read Forever"?
Anyway - again - thanks for the help
This can be closed ... but I dont think it is "solved"
WorkenOnIt said:
[...] Screen hung again - like the first time.
Click to expand...
Click to collapse
When TN completes, you just get the black screen. This is not spelled out in step 8 of Gabrial's procedure, but it is mentioned in the on-screen instructions. Is that what you were seeing?
Boot screen still says "Read Forever"
[...] Now why does it still say "Read Forever"?
Click to expand...
Click to collapse
When I first power mine on, I get the "Read Forever" screen which is shortly followed by the rolling dots as the device boots. After a few moments, I get the slider unlock screen. Is that what you're seeing?
If so, I think that's normal.
Once you unlock, you're at the ADW screen now, right? Or at least you can get back to it in some way?
bobstro said:
When TN completes, you just get the black screen. This is not spelled out in step 8 of Gabrial's procedure, but it is mentioned in the on-screen instructions. Is that what you were seeing?
When I first power mine on, I get the "Read Forever" screen which is shortly followed by the rolling dots as the device boots. After a few moments, I get the slider unlock screen. Is that what you're seeing?
If so, I think that's normal.
Click to expand...
Click to collapse
Screen never blanked .. it did in tries #2 and #3 .. but not #1 and this last one
I thought it would say "Root Forever" ... but hey, as long as it works!
bobstro said:
Once you unlock, you're at the ADW screen now, right? Or at least you can get back to it in some way?
Click to expand...
Click to collapse
It boots to the "Home" reader .. but buttons on side (House) get me to the ADW / Reader selection
WorkenOnIt said:
[...] It boots to the "Home" reader .. but buttons on side (House) get me to the ADW / Reader selection
Click to expand...
Click to collapse
Good to hear it's working. If you don't like the side buttons that Button Savior uses, you can use Nook Touch Tools to provide a couple of alternatives.
You should also be able to change your default Home app using the technique I described above.
IIRC, the "rooted forever" screen only shows during the rooting process. I think Noogie uses that.
I'm setting up a tradeshow display for my company, we're using 3 Nexus 10s in a bent 36"x36" panel. They'll just be looping video, though interactivity may be added to one of them later on. Before I got the Nexus 10s I tested some apps on my Note II that disable the touchscreen because I wanted to prevent anyone from interfering with the looping video.
Unfortunately, I've come to find that while those apps will disable interacting with the main content, it doesn't prevent the Home/Back/etc buttons from working on the bottom bar on the Nexus 10. Additionally, it seems to prevent the video from going completely full screen, leaving the Home/Back/etc icon bar up.
Does anyone have any ideas on how I might truly disable the touchscreen once I have video going? Even if it meant requiring a full reboot to restore touch, that would be fine with me, for the most part we'd just set it and forget it. Some way to just crash or disable the touch screen driver? I'm not rooted right now, but I can be if that's what it takes.
Otherwise we'll end up going with clear acrylic overlays with magnets in them for quick access to the screen,that approach is just generally uglier though, and I'd love to avoid it.
Thanks for any suggestions.
what about this: http://forum.xda-developers.com/showthread.php?t=2266402
then use your existing disable touch program from there?
chaosdefinesorder said:
what about this: http://forum.xda-developers.com/showthread.php?t=2266402
then use your existing disable touch program from there?
Click to expand...
Click to collapse
Perfect, this is exactly what I was looking for. I ended up using a similar app called full!screen that allowed me to specify two touch areas but then make the icons for those tiny/transparent. BSPlayer has a lock so that casual interaction with the device won't do much. From there I can probably fully lock the touchscreen and have it only unlock with a triple tape or messing with a hardware button (only the operator will have access to the buttons, it's mounted inside an enclosure).
You're a hero, chaos. Many thanks to you.
Hi all,
Having followed the instructions I now have a non-bricked NST with NookManager and ReLaunch. I now have two fairly irritating problems, probably due to me poking around in the settings menu a bit too hard.
PROBLEM THE FIRST
In ReLaunch, my Settings gear does nothing. I press it and the screen flicks and then goes back to ReLaunch (exactly where I was in the first place). This makes my inner tinkerer sad and also makes it more than a little difficult to try and fix the issue with:
PROBLEM THE SECOND
If I go to the Nook e-book reading mode and then take myself back to ReLaunch (I'd bound it to long-press of the hardware n key before my Settings button stopped working), the entire bottom bar has vanished. Which means no Applications button, which means I can't really get to launching any of my apps, which means I have... an ebook reader. The only way I can restore it is by rebooting the NST and selecting ReLaunch from the launcher menu at startup.
Any clues?
Floomi said:
Hi all,
Having followed the instructions I now have a non-bricked NST with NookManager and ReLaunch. I now have two fairly irritating problems, probably due to me poking around in the settings menu a bit too hard.
PROBLEM THE FIRST
In ReLaunch, my Settings gear does nothing. I press it and the screen flicks and then goes back to ReLaunch (exactly where I was in the first place). This makes my inner tinkerer sad and also makes it more than a little difficult to try and fix the issue with:
PROBLEM THE SECOND
If I go to the Nook e-book reading mode and then take myself back to ReLaunch (I'd bound it to long-press of the hardware n key before my Settings button stopped working), the entire bottom bar has vanished. Which means no Applications button, which means I can't really get to launching any of my apps, which means I have... an ebook reader. The only way I can restore it is by rebooting the NST and selecting ReLaunch from the launcher menu at startup.
Any clues?
Click to expand...
Click to collapse
You say you cannot access apps, so figure you have Android Market installed? You could try this - Install launcher 7, once installed, you can 'open' it from the notification. You should then be able to access your apps. Make your first port of call the Nook Touch Mod Manager.
Or you could reset the settings in ReLaunch
I have the same problem.
Floomi said:
In ReLaunch, my Settings gear does nothing. I press it and the screen flicks and then goes back to ReLaunch (exactly where I was in the first place).
Any clues?
Click to expand...
Click to collapse
I even unrooted my Nook and rooted it back to fix his. Unfortunately after one use of settings, this problem occured again. Would anyone help?
Undoubtedly it hit an error and died.
What error? Look at the logcat and see.
You need ADB to see logcat.
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
Floomi said:
PROBLEM THE FIRST
In ReLaunch, my Settings gear does nothing. I press it and the screen flicks and then goes back to ReLaunch (exactly where I was in the first place). This makes my inner tinkerer sad and also makes it more than a little difficult to try and fix the issue with:
Any clues?
Click to expand...
Click to collapse
I have the same exact problem. Could anyone please help fixing this?
I found this post by user _ig_ on this thread:
https://forum.xda-developers.com/showthread.php?t=1693666&page=2
_ig_ said:
So, I created an apk (NookIROff) to disable the touch-screen and this part worked. I also created another apk (NookIROn) to cat a "1" to on_off, and managed to bind the n button to my NookIROn app. However, as per Renate's post, this didn't re-enabled the IR / touchscreen and I had to reboot the NST by holding the power button for some 10sec, release, and hold it again for another 10sec.
Any ideas? I suspect if we manage to tweak the IR on/off then we could leave the NST permanently on the home page, with wifi enabled and with a few widgets for email etc for a few weeks without any need to recharge it.
Click to expand...
Click to collapse
Does anybody have this apk file or something similar in storage? If so, I would be more than grateful.
ALinkToTao said:
I found this post by user _ig_ on this thread:
https://forum.xda-developers.com/showthread.php?t=1693666&page=2
Does anybody have this apk file or something similar in storage? If so, I would be more than grateful.
Click to expand...
Click to collapse
So....I might be willing to help but I am not willing to mess up my NST. It seems to me that based on what @Renate NST has said that a "solution" that actually addresses the IR sensors is imperfect, at best. You can turn them off but not on. So why go there? What about a transparent screen overlay? I could easily create a little app that would produce one. My preference would be to have an "escape" in the form of a very small ghostly "x" at one corner of the screen (bottom right--you choose whether portrait or landscape). That way you have not done any partial mischief to the OS. The screen is blocked from touches but functional, and you can get at things if you need to easily by simply tapping that small, ghostly "x".
This does not, of course, address the supposed battery life gain of the more draconian solution. If you insist I could probably write a little app to turn off the sensors. If there is a response from a single press of the power button it's certainly possible to simulate that in the app. Seems to me a good goal would be a toggle that operates from a hardware button (using NTMM to assign one of the side buttons to the app).
I know I can make the transparent overlay app. The other will be guesswork.
nmyshkin said:
So....I might be willing to help but I am not willing to mess up my NST. It seems to me that based on what @Renate NST has said that a "solution" that actually addresses the IR sensors is imperfect, at best. You can turn them off but not on. So why go there? What about a transparent screen overlay? I could easily create a little app that would produce one. My preference would be to have an "escape" in the form of a very small ghostly "x" at one corner of the screen (bottom right--you choose whether portrait or landscape). That way you have not done any partial mischief to the OS. The screen is blocked from touches but functional, and you can get at things if you need to easily by simply tapping that small, ghostly "x".
This does not, of course, address the supposed battery life gain of the more draconian solution. If you insist I could probably write a little app to turn off the sensors. If there is a response from a single press of the power button it's certainly possible to simulate that in the app. Seems to me a good goal would be a toggle that operates from a hardware button (using NTMM to assign one of the side buttons to the app).
I know I can make the transparent overlay app. The other will be guesswork.
Click to expand...
Click to collapse
I really appreciate your reply and interest in this. I agree with you on that, a toggle that operates from a hardware button would work perfectly.
I believe what people learned when they experimented with the variable that Renate mentioned-- turning off the IR sensors would reset itself (the IR sensors would come back on) when the power button was long pressed, and the system rebooted.
This app would have many implications in re-using the NST not only as a super efficient reader (using only the hardware buttons), but also it could be used as a really efficient black and white photoframe, calendar, very readable digital clock, and anything that simply displays information like the daily weather, a looping video on display with fastmode enabled etcetera. This would extend the usable life of the Nook beyond its use as an awesome e-ink tablet, but beyond that to other household applications. This can also be used on Nooks with partially functioning IR arrays (functioning enough to install apps, but not functional enough to use as a tablet).
This is common if people open the Nook for some reason and mess up the positioning of the array on the screen or one of the infrared LEDs burn out. If this were to happen to someone, the nook could still have a legitimate use beyond its life as a reader/tablet, and it would not be tossed in the garbage.
If you're not willing to mess up your OS with experimentation. I am. I have a few Nooks I can mess with. I'll be your guinea pig if you're willing to take the time. If you need some fundage for your time, I'd be glad to supply some.
Here is Renate's post on the matter from that thread.
_ig_ said:
So, I created an apk (NookIROff) to disable the touch-screen and this part worked. I also created another apk (NookIROn) to cat a "1" to on_off, and managed to bind the n button to my NookIROn app. However, as per Renate's post, this didn't re-enabled the IR / touchscreen and I had to reboot the NST by holding the power button for some 10sec, release, and hold it again for another 10sec.
Any ideas? I suspect if we manage to tweak the IR on/off then we could leave the NST permanently on the home page, with wifi enabled and with a few widgets for email etc for a few weeks without any need to recharge it.
Click to expand...
Click to collapse
Renate NST said:
Is it possible to disable the Zforce touch screen? Yes
Is it possible to enable the Zforce touch screen? No
Apparently there is a bug in the driver.
To disable the touch screen:
Code:
# cat /sdcard/zero.txt>/sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
(Where zero.txt is a single byte file of the digit zero without any line termination.)
There is also the issue that if you do turn off the touch screen you would have to use a hard button to turn it back on.
Click to expand...
Click to collapse
Sorry, duplicate post
ALinkToTao said:
I found this post by user _ig_ on this thread:
https://forum.xda-developers.com/showthread.php?t=1693666&page=2
Does anybody have this apk file or something similar in storage? If so, I would be more than grateful.
Click to expand...
Click to collapse
I may have it trying to find it...
OK, so just to be sure, do you have Nook Touch ModManager on your device? Without that it will be difficult to assign the toggle to a hardware button.
Since rebooting seems to clear the IR-OFF condition, it seems like the place to start is a toggle that initially turns off the IR and then after that reboots the device when accessed again. Then it's set up to start over again.
Does that sound like it would work for you?
Edit: I've attached my first go at a toggle app. After installation the first run should disable the IR sensors. The next run should reboot the NST (and hopefully turn the sensors back on). Then it's reset to turn them off again, etc. If you do not have Nook Touch ModManager to assign the app to a hardware button I recommend against running it because it will likely leave you on the screen where you tapped it until a forced reboot.
I used Tasker to make this app so if you have not installed GApps on your device at some point in the past or don't have one of my other apps installed you will need two Google maps library files that Tasker and its daughter apps look for during installation. Without those files present (even though they are not used) the app will not install. I've attached everything in a zip. If you do need the two library files here's what to do with them before you install the IR Control app:
Copy the two files into the locations shown below:
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Set permissions for both files to rw-r--r-- and reboot. Without these files resident, the app will not install.
You can also do:
Code:
# echo -n 0 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
(Be sure to leave a space between the '0' abd the '>'.)
This does turn the touch screen off.
echo -n 1 almost turns it back on.
Using the Touch.apk utility you can see that it is scanning and sensing.
Unfortunately, it doesn't get as far as spitting out events to /dev/input/event2, which is what it should be doing.
Semi-related: The NST apparently doesn't have uinput.
I use a daemon and uinput on my NG2 & NG3 to inject keystrokes from a external button box.
Renate NST said:
You can also do:
Code:
# echo -n 0 > /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/on_off
(Be sure to leave a space between the '0' abd the '>'.)
Click to expand...
Click to collapse
Yes, that's the technique used in the app. Hopefully I got all the spaces in the right places
nmyshkin said:
Hopefully I got all the spaces in the right places
Click to expand...
Click to collapse
Yeah, it's a little gotcha:
Code:
echo Hello > hello.txt [color=green]send "Hello\n" to the file hello.txt[/color]
echo Hello>hello.txt [color=green]send "Hello\n" to the file hello.txt, no problem here[/color]
echo 1 > one.txt [color=green]send "1\n" to the file one.txt[/color]
echo -n 1 > one.txt [color=green]send "1" to the file one.txt[/color]
echo 1 2> one.txt [color=red]send "1\n" to the terminal while redirecting all errors (stderr) to the file one.txt![/color]
echo 1> one.txt [color=red]send "\n" to the file one.txt![/color]
The only danger point is a single digit immediately to the left of the greater-than.
OK, foolhardy that I am, I decided to test the app I posted in #7 above. To my amazement, it does exactly what I said it does
First run requires SuperUser approval because of the shell command to turn off the IR. There's a little flash of the screen and then it goes "dead" (thankfully not literally). I assigned the app to one of my hardware buttons for testing and on the second press of the button the NST rebooted and..........all was restored!
So @ALinkToTao, I hope it does what you wanted in terms of power consumption. Sort of freaky to have the screen unresponsive, though
nmyshkin said:
ok, foolhardy that i am, i decided to test the app i posted in #7 above. To my amazement, it does exactly what i said it does :d
first run requires superuser approval because of the shell command to turn off the ir. There's a little flash of the screen and then it goes "dead" (thankfully not literally). I assigned the app to one of my hardware buttons for testing and on the second press of the button the nst rebooted and..........all was restored!
So @alinktotao, i hope it does what you wanted in terms of power consumption. Sort of freaky to have the screen unresponsive, though
Click to expand...
Click to collapse
duuuuude!!! Thanks!!
I would like to sincerely thank @Renate NST @nmyshkin and @_ig_ for all of your inputs and help.
I wish there was something I could do for you all to thank you for your time?? Can I give you guys a modest tip for your help??? This is so awesome!!
Is there a way to label or re-post this thread so that it indicates that it contains a new app for the NST in the forum for people interested in doing this?? Thanks so much again!
@nmyshkin This app works wonderfully! One suggestion for anyone that installs this on their own nook...
After install don't hit "Open" at the package installer screen and initiate until you have already set one of the hardware buttons to initiate the app! You can re-initiate the app as nmyshkin said to reboot the nook once there is a hardware button that can trigger the app.
If you accidentally do by force of habit tap "Open", definitely hit "Deny" at the superuser prompt!
If you accidentally hit "Accept" by force of habit, your Nook is not lost. If you do a hard shut off by holding down the power button, the IR will come back when it reboots.
Thank you all so much.
I do notice that if the Nook goes into deep sleep, the IR will also come back on.
@nmyshkin , I've been testing it today, and I think it may be better to remove the reboot trigger from the app and only have it turn the IR off. Simply having the app trigger IR off should be sufficient. The reason being that if you want to read with no IR, and you put the Nook to sleep or the screen times out and it goes into deep sleep, it will turn the IR back on.
In order to turn the IR off again, you have to trigger the app which will reboot the Nook, even though the IR is back on. That being said, it is still very useful for a huge majority of applications that I was planning on using this for. Again, I thank you so much for your time and effort putting this together.
If we were to remove the reboot function of this simple and awesome app:
Rather than having to reboot the Nook entirely to get IR back on, you can simply let it go into deep sleep by putting it to sleep and waiting probably as long as it takes to reboot the Nook and the IR array comes back on. If for some reason the Nook can't go into deep sleep, a hard power off and then power on will do the trick.
ALinkToTao said:
If we were to remove the reboot function of this simple and awesome app:
Rather than having to reboot the Nook entirely to get IR back on, you can simply let it go into deep sleep by putting it to sleep and waiting probably as long as it takes to reboot the Nook and the IR array comes back on. If for some reason the Nook can't go into deep sleep, a hard power off and then power on will do the trick.
Click to expand...
Click to collapse
Or, if we knew how to put the NST into deep sleep mode via command, said command could replace Reboot in the toggle, I guess.
Anyway, I've attached an app that only turns off the IR (no toggle).
nmyshkin said:
Or, if we knew how to put the NST into deep sleep mode via command, said command could replace Reboot in the toggle, I guess.
Anyway, I've attached an app that only turns off the IR (no toggle).
Click to expand...
Click to collapse
Thanks so much, man. I agree with you. If we knew the command for deep sleep, we could toggle it that way. Much appreciated. I hope this serves the xda NST community as well for anyone that would like this also. Thanks man. May you recognize the light of pure love shining in your life.
@nmyshkin Thanks again for writing this simple app!
I must say that this is significantly lengthening the battery life for apps that use the e-ink screen to display something for long periods of time without letting the Nook go to sleep. In particular, that clock app which I mentioned in an early post in this thread, it was draining the battery like 30% in a few hours. Now, with the IR off, the battery went down only 3% in a few hours! This was a very loose test--more like a casual observation. It wasn't a controlled experiment, so I would like to perform a controlled experiment with this and give you the results! It's looking really awesome though!
Also thanks again for removing the reboot! Now that we know that the IR comes back on after a deep sleep, it is much more convenient to not have it reboot.
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.