Screen height too big for Nook Touch - Nook Touch General

Been struggling with Touchnooter 1.6.24 and 1.6.22 for several weeks with a fairly new Nook Touch. Some Android system and app buttons on the very bottom don't respond. These are key buttons such as the Android Market accept terms of use, the Add app Finish button, and the SlideMe accept button. I found a work around for the home page bottom buttons that at least lets me access the app drawer. If the status bar is set to hidden the bottom buttons come up a very small amount and then respond. I haven't found a way to hide the status bar in apps though. I'm currently trying to figure out how to get the Nook recognized as a device so I can load the driver thats supposed to let me use adb to install apps. I've found that putting apps on the SD card prior to installing Touchnooter and starting the adk in Root Explorer just gives an error that non Android Market apps are blocked.
The real solution is to get everything on the screen. Presumably all the bottom buttons will work if the height could be shrunk. How do I do this?
Could BN be trying to block rooting by introducing small changes into recent Nooks?

Stumbled on a work around once I figured out how to use adb. All the google hits about using USB for adb had me confused. Once I realized that the SDK adb is made to work over wifi I was able to install Dolphin browser. I discovered that it has a setting for landscape, and that its add-ons are loaded through the Android Market. AM pops up in landscape mode and the accept button is no longer on the bottom. Now I can install software from the AM app and I can start making good use of my Nook.
I'm convinced that this isn't a peculiar fault of my Nook and that the Android window is not set right with Touchnooter for at least some Nooks, maybe the more recent ones. Unless I can find another app that sets landscape for all apps, or that allows the window size to be customized, there are still major problems with the Touchnooter package on my Nook. Can't uninstall, for example, since the prompt button is on the very bottom. Have to rm with adb.

Related

[Q] Put device in standby from Terminal Emulator or Gscript

Hello,
I am using CyanogenMod nightlies and would like to setup my long-press home option to shut of the screen and lock the device. There is an option to have it run a script from gscript, but I can't find the right commands. I have search the internet and haven't found anything(maybe not looking for the right thing).
I have also tried some programs from the market(didn't try them all), but they have funny side effects. The programs make the arrows that allow you to hide the status bar appear but not function, and won't go away without a reboot. They even show when I'm on the home screen.
Any help, advice, or some direction to where I could find the answer would be great.
Thanks,
Rsotbiemrptson

[Q] Accidentally set Button Saver Home to Nook's Home

How do I reset ButtonSaver's Home setting or reset the default launcher when I accidentally set ButtonSaver's Home icon to the Nook Home screen.
I rooted last night using the minimal touch method which worked great. I wanted my rooted Nook Simple Touch to boot to the Nook Home screen and still have the ADWLauncher available. Somehow, I screwed up the settings and now I can't get to the Launcher screen anymore. I installed the beta5-2 XWFullTouch version.
Install a new launcher from market. This will allow you to choose/set the default again.
Try Launcher Pro.
--
cbay said:
Install a new launcher from market. This will allow you to choose/set the default again.
Try Launcher Pro.
--
Click to expand...
Click to collapse
But how do I get to the market when my Nook boots to the Nook Home screen and Button Saver's home button also takes me to the Nook Home screen.
Thanks for the help. I searched for "adb wireless" and found the following page:
www DOT androidcentral DOT com/android-quick-app-adb-wireless
I then searched for and downloaded the apk for the latest version of Launcher Pro as you suggested.
Then:
Code:
$ ./adb.osx connect 192.168.1.139
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 192.168.1.139:5555
$ ./adb.osx devices
List of devices attached
192.168.1.139:5555 device
$ ./adb.osx install ../LauncherPro-0.8.6.apk
355 KB/s (2170663 bytes in 5.964s)
pkg: /data/local/tmp/LauncherPro-0.8.6.apk
Success
$ ./adb.osx reboot
It asked me again about which launcher to use right away. Thanks again.
I just realized (now that I can access my device again) that the program's name is Button Savior. I'm trying to figure out of I can have my nook boot by default to the regular nook home screen, but then still be able to use button savior (or something like it) to get to another launcher when I need it.
Primarily, after rooting, I want my Nook to just be a Nook reader, and then when needed, I want to be able to access the other apps.
The other way is more convenient,and that is what
most people do. Boot into ADW or Launcher Pro, and hit the
N button to go to the nook reader. Button Savior -> home
to get back to ADW or Launcher Pro.
If u leave the nook in the nook reader mode, it will not switch back
to ADW unless you hit Button Savior home. So just leave it
in the reader mode always if that is what you want.
I tried Button Savior at first. It's not bad for what it does and it tries to be low-key.
Still, it wasn't low-key enough and some of the buttons don't even do anything.
I finally got rid of Button Savior and the B&N QuickNav and just have the "n" button go right to my ADW Launcher desktop.
I ended up just deciding to leave it booting to Launcher Pro and then I switch it over to the Nook home screen with the N button upon first boot. I also figured out how to create a shortcut to an activity so I could get to the unreachable android settings. Mainly, I wanted to lock the device with a pin code since it now links to my google account. Also, the latest version of Button Savior requires turning on USB debugging which is what led me to try and figure out how to get to that settings menu.
sr105 said:
But how do I get to the market when my Nook boots to the Nook Home screen and Button Saver's home button also takes me to the Nook Home screen.
Click to expand...
Click to collapse
I had the same problem but the solution is very simple - you can access market/Google play from any computer and choose programs to download to your nook (assuming it's registered) ...
sramotylf said:
I had the same problem but the solution is very simple - you can access market/Google play from any computer and choose programs to download to your nook (assuming it's registered) ...
Click to expand...
Click to collapse
Good suggestion. Definitely easier for most people than downloading and using adb.

[Q] ReLaunch: Missing applications bar, Settings gear stopped working

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?

Resetting the 'Home' button?

Hi again..
I seem to have set the Nook ST glowlight to go to relaunch instead of the B&N homepage . Now when I click on 'n' and 'Home', it goes to the Relauncher instead.
Is there a way to reset this so it goes to the B&N page again?
I *think* that if you just install another launcher (anything from the market) you will be presented with the possible choices again when you try to access "Home". Then you can select the default B&N Home screen and later uninstall the added launcher.
Yeah, I installed Launcher 8 recently and this didn't trigger that option again. It is there when I do some things, but I think I asked it to remember my choice for the Home button. I am used to Windows OS and when you do something like that, you can always rectify it, by using either default programs or file associations etc. Android must have something similar, no?
When you make a default choice there is a message that tells you where you can reset the option but it seems to refer to a utility that is not accessible the way the Nook is configured. Can't remember exactly what it says but I've run into the problem before and what I offered seemed to work for me. Did you reboot after installing the additional launcher? I guess the other alternative is to UNinstall all of the Android launchers you've added and reboot. Then there would be no alternative to the Nook "Home". Assuming that works you could then reinstall your launcher of choice. It's a pain, I know. I've "rebuilt" my Nook many times while trying to get over the learning curve. Finally bought an additional SD card so I could save a backup every so often when I'm trying out something new. That's come in handy.
No, it's not like Windows at all (which some people would probably say is a good thing).
No need to uninstall anything. With reLaunch go to the app "nook touch mod". Using this app you can map the nook button to anything you want including the B&N Home page.
Unfortunately this doesn't work either. You can set the 'n button' to do anything but bring up the small taskbar at the bottom, which then takes you to the Home page you have set up.
What I wanted back was the ability to hit the n button, and then be offered the choice of relaunch or B&N home. I can still get to the B&N homepage when the unit starts from being powered down. It's not the end of the world, but a little frustrating.
I haven't even tried to sideload apps or anything yet. And my one attempt to download a book ended when it seems my download location is set as an SD card.. I used to think I was tech savvy. It's only going to get worse. :silly:
gozo81 said:
Unfortunately this doesn't work either. You can set the 'n button' to do anything but bring up the small taskbar at the bottom, which then takes you to the Home page you have set up.
What I wanted back was the ability to hit the n button, and then be offered the choice of relaunch or B&N home. I can still get to the B&N homepage when the unit starts from being powered down. It's not the end of the world, but a little frustrating.
I haven't even tried to sideload apps or anything yet. And my one attempt to download a book ended when it seems my download location is set as an SD card.. I used to think I was tech savvy. It's only going to get worse. :silly:
Click to expand...
Click to collapse
There is a Android App "Default App Manager" on Google play that may work.
gozo81 said:
Unfortunately this doesn't work either. You can set the 'n button' to do anything but bring up the small taskbar at the bottom, which then takes you to the Home page you have set up.
What I wanted back was the ability to hit the n button, and then be offered the choice of relaunch or B&N home. I can still get to the B&N homepage when the unit starts from being powered down. It's not the end of the world, but a little frustrating.
I haven't even tried to sideload apps or anything yet. And my one attempt to download a book ended when it seems my download location is set as an SD card.. I used to think I was tech savvy. It's only going to get worse. :silly:
Click to expand...
Click to collapse
I had a vague notion that NookTouchModManager didn't work with Glowlight, but I might be wrong. If it does work, then you don't want to set the "N" button to bring up Home. Rather you want to set the QuickNav Home button to "default". That's going to get you the B&N page you seek. But that means you will need a way to access your app drawer/launcher as well. For that purpose either one of the other QuickNav buttons could be reassigned OR you could assign a long press of the "N" button to initiate the launcher.
If NTMM doesn't work with Glowlight then I stand by the original idea: uninstall any launchers and reboot. With no alternative, you should get the B&N Home screen unless you have in some other way reassigned the QuickNav Home button.
Don't get discouraged. As a noob (still...) I had to start over quite a few times and there were times I was sure I had bricked my Nook. But I didn't.

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.

Categories

Resources