[Q] (ReLaunch) Restore Shop Quicknav - Nook Touch General

After installing ReLaunch, the Shop quicknav was permanently changed to start ReLaunch (but it still displays as Shop)
ReLaunch asked for root permissions to make this change, but it doesn't have a way to revert it.
Does anyone know how to restore the original behavior for the quicknav shop button?

Tell NTT that instead of B&N default, do launch application. Then pick shop. After a restart, the icon should change, but it will be a bit smaller.

brendan10211 said:
Tell NTT that instead of B&N default, do launch application. Then pick shop. After a restart, the icon should change, but it will be a bit smaller.
Click to expand...
Click to collapse
I did that, but I want to restore the (proper) original behavior.

That doesn't seem to work properly once you screw it up (at least for me)

brendan10211 said:
That doesn't seem to work properly once you screw it up (at least for me)
Click to expand...
Click to collapse
After rooting two separate devices several times each, the Shop QuickNav menu button has never worked for me. I always had to set it to launch the B&N Shop app using Nook Touch Tools. I finally permanently remapped it to something more useful since I don't hit the shop every day.

I mapped it to NoRefresh seeing as I don't have any money to buy anything anyway

Related

[Q] NST & Touchnooter install kinda sorta

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.

is it possible to remap icons or buttons

Is it possible to remap the quicknav keys to go to the adw launcher home, or remap the 'currently reading' icon to go to the adw launcher home?
the nook home or nook search have no use to me - it would be more useful to remap these to adw launcher home or one of the other apps.
this is for NSTGL
you can do it with "Nook Touch Tools" app .
I have NSTGL - Nook Touch Tools doesn't work with NSTGL
at the moment I am using button savior to switch from Nook to ADW - but would dearly love to do away with Button Savior.
ladykayaker said:
I have NSTGL - Nook Touch Tools doesn't work with NSTGL
at the moment I am using button savior to switch from Nook to ADW - but would dearly love to do away with Button Savior.
Click to expand...
Click to collapse
Come on, dude (dudette?).
You didn't even need to search for this one, just to read all the topics on the front page. In your defense...I only achieved this yesterday, and not everything is working, but:
http://forum.xda-developers.com/showthread.php?t=1692290
This dudette is a mom to five kids, ages 3 to 14.
I have read through the entire post you referred to, and am not clear on the steps to be taken.
Can you clarify them for me? I would be most grateful.
ladykayaker said:
This dudette is a mom to five kids, ages 3 to 14.
I have read through the entire post you referred to, and am not clear on the steps to be taken.
Can you clarify them for me? I would be most grateful.
Click to expand...
Click to collapse
LOL, sorry, I just didn't know what to go with there. Everything else sounded old fashioned (ma'am? gal?) - pray don't take it personally
I'm not sure what it is you already know how to do. Do you have adb set up on your computer?
yes - adb is setup and running (and kids are in bed
thanks for your assistance!
My solution was just to modify android.policy.jar so that the "n" button does what a Home button should.
I don't use any "Tools" or QuickNav.
I leave "Last Read" as it was.
I keep planning on making an installable patch for this but never get around to it.
Renata,
Can you explain more fully how to modify android.policy.jar and what you modified it to?
Thanks.

[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?

[Q] Some very simple questions!

Hi
Got my £29 Nook ST delivered on Friday to complement my Kindle Keyboard 3G which we use a lot.
Originally I intended to use the Nook in its vanilla flavour, but having read that rooting was possible and the Kindle app worked, thought I'd keep all of my reading in the same place by installing the Kindle app.
So far I've done the following:-
- rooted successfully (NST 1.2.1)
- installed Gapps successfully
- installed the Kindle app by browsing play.google.com and "pushing" it to the NST
- sync'd up my books and read a few on the Nook.
I'm no programmer, but I have rooted both of my other Android devices, as well as installed custom roms and kernels on my phone, so in general things going sweetly and as expected.
There are a couple of simple questions I'd like to post though which will help me (and perhaps others) speed through the process of getting the device into a truly workable format
1) I installed the Kindle App via the play store - thus this is the latest version I suppose. Is there a "better" older version for using on the NST which will bring any benefits?
2) If I choose one of the launches (stock or ReLaunch) as the default, will I lose the ability to get back to the menus?
3) Is there a list of what the various button mapping options from Nook Touch Mod mean? They don't appear to make much sense, though I have successfully modified the page ups and page downs to be volume up and down, which works OK with the Kindle reading app
4) Do I need to have an SD card permanently in the NST for storage, or is that not necessary for books?
5) If all I want to do on the NST is either read books using the Kindle app or read books using the NST's core functionality, is there a neat and tidy way of hiding the ReLaunch launcher etc? Its all usable to me, but I could see my family getting a little stuck when using it, certainly compared to the simplicity of using the stock app or using my Kindle Keyboard
6) Some of the rendering of the font from the Kindle app looks a little less than precise. What can I do to improve this?
Thanks in advance for the help!
Matt
larkim said:
2) If I choose one of the launches (stock or ReLaunch) as the default, will I lose the ability to get back to the menus?
Click to expand...
Click to collapse
What menus are you referring to?
larkim said:
3) Is there a list of what the various button mapping options from Nook Touch Mod mean? They don't appear to make much sense, though I have successfully modified the page ups and page downs to be volume up and down, which works OK with the Kindle reading app
Click to expand...
Click to collapse
Not that I know of. Ask questions on specific options. You can use the Tap Left and Tap Right instead of Volume up/down so that the hardware page up/down buttons work for both the stock NST reader and the Kindle app.
larkim said:
5) If all I want to do on the NST is either read books using the Kindle app or read books using the NST's core functionality, is there a neat and tidy way of hiding the ReLaunch launcher etc? Its all usable to me, but I could see my family getting a little stuck when using it, certainly compared to the simplicity of using the stock app or using my Kindle Keyboard
Click to expand...
Click to collapse
Use NTMM to map your n button long press to ReLaunch. Then when you short press the n button and the B&N quicknav comes up tap on Home then click on the use as default checkbox and select Home. Now your NST looks like stock unless you long press the n button to get into ReLaunch. You could also remap one of the quicknav buttons to Kindle if others want to use Kindle without going through Relaunch.
straygecko said:
What menus are you referring to?
Click to expand...
Click to collapse
I think I was meaning between the "ReLaunch" launcher and the "Stock" launcher. i.e. if I restrict myself to using one, how to I access the other.
Thanks for the rest of your help!
Matt
larkim said:
I think I was meaning between the "ReLaunch" launcher and the "Stock" launcher. i.e. if I restrict myself to using one, how to I access the other.
Thanks for the rest of your help!
Matt
Click to expand...
Click to collapse
By the stock launcher you mean Home I assume. In any case use NTMM to assign a hardware button to whatever you don't want to be the default launcher and set what you do as the default launcher. I described how to make Home the default and still have access to ReLaunch in my previous post answering another of your questions. I'd recommend always assigning ReLaunch to some hardware button just in case you accidentally make something else the default you can get back to ReLaunch to fix things.
straygecko said:
By the stock launcher you mean Home I assume. In any case use NTMM to assign a hardware button to whatever you don't want to be the default launcher and set what you do as the default launcher. I described how to make Home the default and still have access to ReLaunch in my previous post answering another of your questions. I'd recommend always assigning ReLaunch to some hardware button just in case you accidentally make something else the default you can get back to ReLaunch to fix things.
Click to expand...
Click to collapse
I always found that the launcher you chose as default is not persistent... that by power cycling you'd get a choice again. Could be just mine though?
amjl2000 said:
I always found that the launcher you chose as default is not persistent... that by power cycling you'd get a choice again. Could be just mine though?
Click to expand...
Click to collapse
If you check the box to use the launcher as default before selecting the launcher then it will persist across power cycles. That's how it works for me and there are a few threads here about people who have selected a default and can't get back to ReLaunch having to factory restore and reroot.

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.

Categories

Resources