[Q] Cannot access Nook viewer after rooting Tablet - Barnes & Noble Nook Tablet

Hi,
I followed the very good instructions to move my Tablet's firmware to 1.4.0 (was 1.4.1 out of the box) and to then root it. (Much thanks to Indirect and AdamOutler and everyone else!)
During the root script, I chose NOT to debloat and to go with the ADW launcher.
Everything went smoothly and I've rebooted it several times now. However, I can't seem to access the (B&N installed) nook reader anymore. I do have an icon for "NookViewer" in my apps, but when I select it I get a white screen that does nothing. I also tried downloading the "B&N Nook" app from the Android Marketplace, which installed correctly (it says), but when I select it, I get sent to the ADW home page and nothing else happens.
Does anyone have any idea how to get either one to work, short of me wiping it back to 1.4.0 and starting over again?
Thanks,
Peter

Hi Peter,
I might have had a similar issue, and it involves the defaults for home launching. When you were choosing whether to launch the "home" (which is nook home) and "ADWLauncher", did you check the box to launch ADWLauncher by default? I did that with GoLauncher and could not get back to the nook home screen.
The way this issue is solved is by finding the application settings for your launcher (in your case ADWLauncher, in mine it was GoLauncher) and clearing the defaults. When you go back to the rooted home screen and double click the n button, you should see the prompt for your launcher or the home launcher. Select home and you will be back to the nook reader.
I hope this helps.
In the video it looked very easy to switch back and forth without any prompts. I am curious how that was performed.

I'm having the same issue as the OP. I'll let him chime in but if I understand correctly this is not an issue with being able to see the B&N default launcher. As I understand the issue is that the NookViewer, which does appear in the AWD Launcher (or other launcher), is non-functional. When selected all you get is a blank white screen.

Ok, I took this as the issue:
However, I can't seem to access the (B&N installed) nook reader anymore.
Click to expand...
Click to collapse
Otherwise I am seeing the same issue with NookViewer where a blank screen is open. I provided a way to get back to the nook reader, although I'm sure there is a more elegant procedure. I have no idea what the issue with NookViewer is or what NookViewer is supposed to do.

Dito here
I have rooted, de-bloated, and went with the ADW. I too have the exact same issue, when you click on the reader icon, I get a completely blank white screen.
I have not tried any type of fix, because I am having greater issues with the MarketPlace saying the N.T. is not compatible with most apps.

Mark Read said:
I have rooted, de-bloated, and went with the ADW. I too have the exact same issue, when you click on the reader icon, I get a completely blank white screen.
I have not tried any type of fix, because I am having greater issues with the MarketPlace saying the N.T. is not compatible with most apps.
Click to expand...
Click to collapse
Have you tried this for apps compatibility

lavero.burgos said:
Have you tried this for apps compatibility
Click to expand...
Click to collapse
I will have to try this out. The market used to let me download more than it does now. In fact one app that I downloaded to the market now has an update. When I go to update it says that my device isn't compatible! I would assume this would correct that. Are there any potential drawback to modifying the build.prop?

I am not sure, but I don't think you can click on the reader to make it work. You need to go to the library. From the library, you select what you want to read, that brings up the nook reader. I have links to download the reader and the library; you have to have both, but the library is the executable.
http://www.makingitdigital.net/android/index.html

If you went with snoball-mod it removes all B&N apps including the reader from the device and depending on which Debloat option you choose in indirects root script it can remove all B&N apps as well

gr8wing said:
I am not sure, but I don't think you can click on the reader to make it work. You need to go to the library. From the library, you select what you want to read, that brings up the nook reader. I have links to download the reader and the library; you have to have both, but the library is the executable.
Click to expand...
Click to collapse
That makes sense and going to the library is what I do to access and read my B&N material. So even though it doesn't impact the ability to read B&N material I guess it's more of a "why is it doing that?" issue. I know after I rooted my Nook the first thing I did was click on every icon to see what it was. The Nook Viewer was the only one that seemed to not work (but again your explaination makes sense).

Related

[Q] bricked (ish) (solved)

So I was all rooted. I had Go Launcher, Market, and Swiftkey all working awesomely. My NT life was good. Then Swiftkey started throwing up errors. So I went to Any Cut to find a shortcut to Swiftkey's settings. There was like 8 settings under activities but not a specific Swiftkey settings. So I created shortcuts to the 8 settings and thought I would try them all and maybe one was for swiftkey.
When I clicked on the second settings shortcut the NT through up an error that stated there was an authorization error and the tablet would reset. When the tablet restarted it forced a wipe to factory settings. I thought...that sucks...but whatever I'll start over.
When the tablet had finished and restarted It started to go through the setup screens as one might expect. However, Swiftkey is apparently still selected as the keyboard and the NT keeps giving the Swiftkey force close errors. I can't enter in my registration info because I haven't an effin' keyboard. I didn't have usb debugging turned on so I don't think I can use adb to remove swiftkey. Although, I've never really used ADB unless I'm rooting and following very specific instructions from one of these forums.
Is there a way to bypass the initial registration and sign in crud so I can install root explorer and remove Swiftkey?
Sorry for the long story. Hopefully someone will have a suggestion on how to fix this.
Thanks in advance.
tldr- NT hard reset and now stuck without keyboard because Swiftkey was still selected and Swift key won't work during initial registration....argh!
Tip the screen corners starting top left in clockwise motion.
http://nookdevs.com/NookColor_Factory_Mode/Skip_Out_of_Box_Experience
This has worked for people to skip registering their device good luck god bless.
I did test this method when i got t the last prompt to skip Oobe(out of the box experience) I did get a force close error. However I just reopened the menu by hitting the volume up and the lower right portion of the screen. The Oobe button came back up and i clicked it with success, bypassing the registration.
Well I was able to bypass the Nook Experience BS...Thanks for the tip! But I still didn't have a keyboard to download any apps from the browser. So I created an epub file with Callibre that contained web addresses of all the software I needed to get rid of Swiftkey from system/app. I then transfered the epub to the nook...opened it with Nook's reader....selected a web address....and did a google lookup from within the reader. I was able to download and install what I needed, and it worked. All Better.
demonhater said:
Well I was able to bypass the Nook Experience BS...Thanks for the tip! But I still didn't have a keyboard to download any apps from the browser. So I created an epub file with Callibre that contained web addresses of all the software I needed to get rid of Swiftkey from system/app. I then transfered the epub to the nook...opened it with Nook's reader....selected a web address....and did a google lookup from within the reader. I was able to download and install what I needed, and it worked. All Better.
Click to expand...
Click to collapse
I think what you did is really smart( never mind the semi brick part) and important. This could help out a lot of people that lose keyboard access or other issues that occur. Using the nook reader with google search was a great way around your problem.
SwiftKey force closes on me randomly and will not stop until I re-run the apk inside /System/App again but after that it works fine for awhile. I wonder if it's just SwiftKey because I haven't tried any other keyboards yet
I've noticed several keyboards don't stick after a reboot. Thickbuttons and Hackers seems to be the only 2 I've tried that do stick.
yaggermr said:
I think what you did is really smart( never mind the semi brick part) and important.
Click to expand...
Click to collapse
The scary part was that the NT forced a random wipe on it's own after a quick error about "authorization."
Sorry didn't know about the authentification error and I was joking about the semi brick part. I just thought your recovery method could help somebody out of semi brick hell.
No need to say sorry. I knew you were joking. And hopefully, it will help someone else.

[Q] B&N Nook reader app on snowball-mod NT

Hi,
I have successfully applied snowball-mod to my NT (Thank you cfoesch!). It makes the NT into a very reasonable general purpose tablet.
However, I am having one problem. I install the B&N nook android reader but it doesn't work. I have downloaded the reader from Google market and also tried side loading B&N Nook-19.apk from another device. In both cases the app installs without reported error but when I try to run it nothing starts up.
Has anyone successfully installed and used the nook android application on Snowball-mod?
Any pointers on how I might debug this?
Thanks,
-A
I have the same issue, but I used Indirect's full debloat method. I don't care to use any of the BN stuff so last night I ran the script and performed full debloat. I downloaded nook reader and like you said installed with no issue, but would not run. I just installed a different reader and was back to reading. I do wish though that the book icon still worked though, I did like that feature. No matter I am going to install the ics toolbar today anyway. My belief is the less BN junk on my tablet the better.
wired12 said:
However, I am having one problem. I install the B&N nook android reader but it doesn't work. I have downloaded the reader from Google market and also tried side loading B&N Nook-19.apk from another device. In both cases the app installs without reported error but when I try to run it nothing starts up.
Click to expand...
Click to collapse
Yep, this is a none problem, and there's not really much we can do about it. I think the app is detecting something about being on a Nook, and quitting out as a result. Or maybe last vestiges of Nook apps or something.
Either way, because it doesn't force quit, it's most likely that this is intentional "working-as-designed" behavior.
Has anyone successfully installed and used the nook android application on Snowball-mod?
Click to expand...
Click to collapse
Nope.
Any pointers on how I might debug this?
Click to expand...
Click to collapse
Wait for custom ROMs. Snowball-mod is deprecated right now. So, enjoy using your tablet with all the quirks for another month-ish, or so maybe, and then everything will be fine with the custom ROMs.
Some fella at XDA mentioned extracting the library.apk and reader.apk from the stock 1.4.0 rom and install that.
I tried that and it work perfectly. Snowball mod with original reader + library and no FC at all.
Try FBReader from the market. I like it better than BN reader. also, go use indirects update block tool. Mine updated yesterday using snowball-mod and I had to use the card method to roll back and then start over.
I have "Cool Reader" installed on a non-debloated Nook Tablet and when I press the 'book icon' it brings up the 'complete action using' menu. Once Cool Reader is set as 'default' it opens when the book icon is pressed. I'm not sure if this will work with a debloated Nook, but it may be worth a try. This feature does not work with others readers (Moon +, Aldiko, etc).
I have made a web page
http://www.makingitdigital.net/android/index.html
to share what I have installed on my NT. I have a link on there for the Nook Reader and the Nook Library. You need to install both. You will not be able to bring up the reader, but you can bring up the library and then select what you want. That brings up the reader.
Very nice putting This together. Much appreciated.

Dual Booted Tablet acts like has a Virus

I have a dual Booted Tablet. When I hit the N button it usually asks me if I want to go home or ADW Launcher(The launcher I chose). Now it stays on the original Nook screen and randomly opens up different books on its own and flips pages on its own. Also, the option to open up ADW is gone. if I hit the N button it just opens up whatever book I was reading last. I turned the device and back on but it acts the same way. Can anyone help me?
I'm not sure what you mean by 'dual booted'. With CM7?
Similar behavior to what you describe (things opening randomly, pages flipping, etc.) usually happens when the battery is very low. I've also seen it happen trying to use USB power adapters that don't really work correctly for the NT. Make sure you're not operating on a very low charge or other power issue.
I used Indirect's Root. I was able to keep the original Nook look as well as boot into another launcher. It was working fine until yesterday. Now the Home button doesn't do what it should but the main thing is that the screen types and writes all on its own. I heard about the low power setting issues with some people. My Nook was at 60% so I don't know if that's considered low enough to be under that umbrella
OKAMIsama said:
I used Indirect's Root. I was able to keep the original Nook look as well as boot into another launcher.
Click to expand...
Click to collapse
I can't help you with your problem, but I want to make things clear.
You don't have dual boot or anything like that, you just installed alternative launcher application.
In general you have the same stock firmware you had before rooting with addition of a few apps, allowing you to do more, than B&N wants you to be able to do.
dalkor said:
You don't have dual boot or anything like that, you just installed alternative launcher application.
Click to expand...
Click to collapse
This is correct.
Disclaimer: I am a noob. Please take the following suggestions with a grain of salt.
Perhaps, clearing the homecatcher defaults will clear things up?
Alternatively, you could try installing a different launcher, such as golauncher, and see if it behaves as strangely as your current configuration.
Sent from my BNTV250 running Team B's CM7 "don't format your sd" beta build.
Well I would just install another launcher but the problem is that I can't access the other launcher any longer. The Home button doesn't work like its supposed to but instead opens up the Nook's Book Library. The whole thing just started acting weird and randomly the keyboard would pop up and write by itself in addition to opening and closes the book Library. Its been acting like it has a virus. I factory reset it but unfortunately it didnt help. So I figure my screen is faulty
OKAMIsama said:
Well I would just install another launcher but the problem is that I can't access the other launcher any longer. The Home button doesn't work like its supposed to but instead opens up the Nook's Book Library. The whole thing just started acting weird and randomly the keyboard would pop up and write by itself in addition to opening and closes the book Library. Its been acting like it has a virus. I factory reset it but unfortunately it didnt help. So I figure my screen is faulty
Click to expand...
Click to collapse
I got the same few hours after I rooted but using go launcher, just clean your screan very very clean if you haven't put a screen protector on it, then make sure its charged. Now try to open anything in that you could find a link click on it so it opens the browser then go to the android.market.com and download another launcher. After that I took my tablet and removed all the B&N crap apps, ijust left the games. Don't forget to apply the OTA block again.
Advice: remove home catcher.
PS: you could also use adb to push a new launcher but as you factory reseted usb debugging must be disabled, you need can enable it again by downloading tgps_launcher.apk from indirects root thread using the Nook browser.
~ Veronica
Sent from XDA premium using my Nook Tablet
what should I use to wipe it down. Im thinking I wiped it down pretty good but its still doing it. I noticed the z, e, and s buttons on the keyboard get pressed a lot so maybe its in the lower right region of my device.
OKAMIsama said:
what should I use to wipe it down. Im thinking I wiped it down pretty good but its still doing it. I noticed the z, e, and s buttons on the keyboard get pressed a lot so maybe its in the lower right region of my device.
Click to expand...
Click to collapse
OK if you havent installed CWM you're good to make the wipes, to know how to... read my FAQ . Link in my signature.
~ Veronica
OKAMIsama said:
Well I would just install another launcher but the problem is that I can't access the other launcher any longer. The Home button doesn't work like its supposed to but instead opens up the Nook's Book Library. The whole thing just started acting weird and randomly the keyboard would pop up and write by itself in addition to opening and closes the book Library. Its been acting like it has a virus. I factory reset it but unfortunately it didnt help. So I figure my screen is faulty
Click to expand...
Click to collapse
Have you tried going in to manage apps and deselect the default for ADW, B&N's Home Launcher and Homecatcher if your using it? I use button savior so I have software buttons rather than the n button. by deselecting the default launcher you should get a window again asking which launcher do you want to use as home.

My Rooted 8GB Nook Journey and Kudos to jichauan89.

Here are my thoughts on the Nook Tablet and my rooting process. I try to write to be as friendly as possible for the newbies to rooting devices. This is really just a reflection of my experience with the device and my rooting effort thus far .
If money is no issue, by all means go with the 16GB. But if you really want the best bang for the buck, go with the new 8GB version over the 16. The main difference is the RAM but since we are not talking about a true multitasking device, the extra RAM does little. Even if you root and hack and upgrade and tweak the hell out of it, you'll never really do more than one thing at a time on the device itself so 512MB is usually plenty. I have found that the Nook is the perfect companion device (for references and reading) to go with my netbook (which is the pefect portable productivity device) and my rooted android cell (universal connectivity device with tether hack). Those three things working in tandum mean that I can get online anytime, anywhere, and work comfortably. Now, if I can just find an Android phone that has a battery that lasts for more than 4 hours with the wi-fi/tethering/mobile hostpot turned on.
I have successfully used jichauan89's Root for Nook Tablet 8GB (w/ Android Market) root method number 1 (the SD image). Thank you jichauan89! It was easy and worked great the first time. His procedure...
http://forum.xda-developers.com/showthread.php?t=1529553
Here was my specific procedure and thoughts.
Prior to the attempt. Make sure that the device has plenty of battery power or is plugged in the wall adapter. This is a good practice for all rooting/hacking attempts on these types of devices, including cell phones and media players. I backed up the data on my SD card by simply copying all the files to a folder on my netbook's desktop.
Used Sandisk 8GB microSDHC card I had in my old Samsung Captivate. I used the SC card adapter it came with orginally to insert it into the built in SD Card reader in my Windows XP netbook.
Downloaded the SD card image from exactly where jichauan89 described.
Used Win32DiskImage.exe to format and write the image to the SD card. Worked without error. I used the safely remove hardware option in Windows to disconnect the hardware before removing the card from the reader.
Powered off the Nook Tablet 8GB.
Inserted the freshly formatted and imaged SD card into the Nook.
Held the power in until it powered on.
Saw a cardboard box. It reminded me of Amazon's frustration-free packaging.
Waited.
Saw the "Read Forever" Nook logo.
Waited exactly 3 minutes.
Held the power button in until the powered off.
Removed the SD card and set it aside. It's mission is complete.
Held the power button in until it powered on.
Routine booting began.
Upon boot completion, I clicked the n button and selected "search". I searched for "market". It found the Android Market. Don't look for "play". The hack itself uses an old version of the market that will upgrade itself to Google Play after you run it (as long as you are connected to WiFi).
At this point, your device is rooted successfully. Anything else you do is really just gravy. I suggest doing the NT Hidden Settings to allow sideloading and I also suggesting doing the hack to stop updates so that you get to keep all your hard (not really) rooting working in tact if and when B&N rolls out 1.4.3 of the Nook's firmware. Here are the additional steps that I took, again, this is all thanks to jichauan89's simple instructions and the feedback given in his thread. Also note, when I did have issues, I kept reading the thread rather than jumping the gun and posting my own questions. All the answers were already there...
I installed NT Hidden Settings from the market.
I immediately used the hack to allow 3rd party apps. There was some confusion and error here. I ran it a few times and it didn't appear to do anything, but then I pressed the n button once and a super user screen appeared asking me to give NT Hidden Settings rights, which I allowed. I tried the 3rd party hack a few more times to no avail. I rebooted the device and tried and tried and it wasn't working and the check mark on the previous screen for allowing Uknown Sources simply seemed to uncheck itself. I was watching the new episode of South Park on TV and at one point I reran the hack for about the 300th time it felt, a message came up that the app had been given SU rights, and I moved my attention to South Park for several minutes. When my eyes came back to the Nook, I checked the Unknown sources setting again, and it was checked, all by itslef. Lesson, I believe that the 3rd party app hack takes a few minutes to actually do anything after it is granted SU rights but doesn't give any notification that it is successful (or I missed it while grandma was trying to make Butters eat a urinal cake). I believe the app checks the Unknown Sources box itself as a part of its script and all the other times I had run the hack, I was just being impatient. After several reboots, the check now stays.
I then ran the NT Hidden Settings hack to keep updates from being installed. I was notified almost immediately that the installation was successful.
I then installed Go Launcher and HomeCatcher. I got Homecatcher from an XDA forum post and not from the Android Market. After running HomeCatcher, I clicked the n button and selected home and I was prompted to choose between a little andorid guy and the stock nook launcher. I made sure that put a check in the box to make this decision default (which i kind of wish i didn't, but it should be easily undone) and then selected the Andorid icon. Now whenever I select home, it goes to the Go Launcher app, awesome.
I also immediately installed File Expert and Titanium Backup and everything seems to work perfectly.
I then installed the Amazon App Market from Amazon.com in the Nook's stock browser. Every app from their seems to fail and says "SD card required" or some such thing. I am assuming that if I put the SD card back in everthing would work fine, but I'm not sure why this is an issue. Shouldn't it be able to use the Nook Tablet's internal memory? I'll keep testing.
The only thing I'm thinking about now is that I want to find the fastest way to switch back and forth between the stock B&N launcher and Go Launcher. I like B&N's ecosystem, even though it is limited, but I enjoy the advantages I get from walking in the store and getting to read books and even though the user interface of their digital store is one of the dumbest things I have ever seen, I find myself wanting to us it because I support Barnes & Noble a lot and wish them the best. I do, however, wish they would listen to all of us who are *****ing about their Market's limitations and ridiculous pricing and either treat the device more like a tablet like the name implies. But I'm preaching to the choir, right?
Try installing adw launcher, it should break the default status of go launcher, I'm not positive if there is a way to disable it other than that.
Sent from my Nook Tablet using XDA
You can actually go into the application settings and clear the cache and clear the defaults for HomeCatcher and then do a force stop. Run it again in the app drawer and the next time you click the n button it will ask wich launcher to run again. I made sure I didn't select the default action checkbox this time. Now everytime i hit n, it asks which launcher I want to use. I like it! Quick access to my wonderful root stuff and just as quick access to to an (essentially) stock Nook environment.
I have read it and did not find anything about pre-requisites. So am I totally safe doing this from a stock 8gb 1.4.2 nook tablet with no prior mods installed?
I understand the risks involved of course.
Piercing Heavens said:
I have read it and did not find anything about pre-requisites. So am I totally safe doing this from a stock 8gb 1.4.2 nook tablet with no prior mods installed?
I understand the risks involved of course.
Click to expand...
Click to collapse
If you're just looking to root, then yes, use the method linked in this thread.
The "N" button
I rooted mine and everything worked fine.
I installed Button Savior and use that when I wanna be in Android tablet mode for going to the home screen and I just leave the Barnes & Noble 'n' as it is so when I press it I can go straight to the B&N look. It's pretty easy.
But this thread has been a great help to me.
Thanks
I followed a very similar procedure and everything worked great the first time, thanks to this board!
Thanks
I wanted to throw a thanks out to you as well.
I read your post as well as jichuan's post before I even tried anything.
The only issue I have had is the "unknown sources" not staying checked.
Like you, I tried and tried to get it to stick, finally looked away for a bit, and poof! Magically it's checked. Maybe patience is indeed a virtue! However, I can not for the life of me get HomeCatcher to install. I am rooted obviously as I was able to download NT Hidden Settings from the Play store. Any ideas, or did I overlook something?
I had a lot of problems with unknown sources but it just happened all by itself
1.4.3
Doesn't seem to be working with 1.4.3. I installed NT Hidden settings and some apps from the play store but they are nowhere to be seen.
THANK YOU!!!!!
Thank you!!! I did this to my NOOK Table and it's working fine!! Thanks!! :laugh:
issue
I'm hoping someone can help me.
I rooted my NT last week (using these tips and tricks) and installed a bunch of stuff on it. And just today I installed the BEATS AUDIO on it and it asked me to reset the device... upon resetting it, it started up like a stock NT and I had to re-register it. Does that mean my device is no longer rooted?
I have an SD card on there and I did a backup using Titanium, but I'm not able to access the apps or get to NT Hidden Settings to download anything. When I navigate the web to the play store I'm able to see that it recognizes some of the apps as installed, but I cannot even download an apk or get anything to download through the play store even though it says a download will begin soon. Also, in the SEARCH option I do not get an option to choose where to search, it's just a general nook search.
I hope this is enough information. I want to try to re-root it but am afraid I might brick it.
PLEASE HELP!
Was your NT running 1.4.2? If so check to see if it's now on 1.4.3 in which case you had an OTA update which un-rooted your tablet.
digixmax said:
Was your NT running 1.4.2? If so check to see if it's now on 1.4.3 in which case you had an OTA update which un-rooted your tablet.
Click to expand...
Click to collapse
still on 1.4.2.
I guess somehow it reset itself and I lost the root. I had to reroot it and use titanium to get most of my files back. So glad I had set up a backup right before I downloaded the app. I ended up deleting the beats installer and just installed Volume+.
I'm still not sure what went wrong.

1.4.3 Update rolling out?

Looks like B&N will be sending out an OTA update to version 1.4.3 starting today.
A post here about a deal with DC Comics mentions the following:
To use 'Zoom View' you will need a small update to the software in your Nook Tablet or Nook Color: software version 1.4.3 and you can get it for the Nook Tablet at www.nook.com/tablet/update or for the Nook Color at www.nookcolor.com/update. A free automated over the air update will bring this to your device beginning June 27th (that's tomorrow!) if you don't manually get the update.
Click to expand...
Click to collapse
Thought y'all might appreciate a heads-up.
We appreciate, thank you sir.
Okay, color me confused. Isn't "Zoom View" where you use two fingers and pinch them together to make things smaller, and un-pinch to make things bigger ? Ah, this is broken ?
old_fart said:
Okay, color me confused. Isn't "Zoom View" where you use two fingers and pinch them together to make things smaller, and un-pinch to make things bigger ? Ah, this is broken ?
Click to expand...
Click to collapse
From B&N:
The NOOK Tablet Ver1.4.3 update contains new features and enhancements, including:
• Zoom view in comics and graphic novels
• 2-Page mode in landscape for viewing PagePerfect™ and PDF documents
• Other minor system enhancements
Sent from my Nook Color running ICS and Tapatalk
old_fart said:
Okay, color me confused. Isn't "Zoom View" where you use two fingers and pinch them together to make things smaller, and un-pinch to make things bigger ? Ah, this is broken ?
Click to expand...
Click to collapse
I haven't seen this in action, but I'm guessing it's similar to how other 3rd party comic viewing apps can detect and automatically zoom and advance through panels on a page without you having to "drive." The Dark Horse Comic app and (to a lesser, tunable degree) ComicViewer both have this. You still have the freedom to pinch-zoom and double-click to do full page views, but you can mostly just sit back and tap on the right side of the screen, and the app will maximize the viewability of a portion of the page. Very handy for smaller (7" or less) screens.
Different systems do it different ways. I doubt it panel by panel guided view, since the Nook Comics do not seem to have the required panel dimension information, but actually, it doesn't require it.
All it needs is the ability to lock the zoom at the level you want through page turns, starting at the top left corner of the page (left to right) or top right corner (right to left) and the pan and scan would be fine with me. Keep It Simple.
Anyway, this is definitely a change that I'll let go through and then run the manual rooter again afterward.
Changes made by update
Well bn updated my NT to 1.4.3 last night.
Now any app that i had pinned to the home page that was not gotten from BN will not open from the icon. These were pinned to the homepage using app manager.
I have to search for the adw launcher and get into them that way
Any body else have any issues.
1.4.3 is a nook killer
krier32 said:
Well bn updated my NT to 1.4.3 last night.
Now any app that i had pinned to the home page that was not gotten from BN will not open from the icon. These were pinned to the homepage using app manager.
I have to search for the adw launcher and get into them that way
Any body else have any issues.
Click to expand...
Click to collapse
Same issue here. Had root but lost it to OTA for 1.42. Never bothered to re-root because I got 95% of the apps I cared about installed. Now 1.4.3 basically broke all of my apps and is not really usable anymore until I root again. Hoping SD card root works on 1.43. B&N are really making the move to CM7 seem smarter than ever.
Verified
So, my nook also updated to the 1.4.3 last night.
I can verify that my device is no longer rooted, however I can still install applications from Google Play, and Amazon's app store. All of my previous applications are still working however not from the Nook home screens.
I haven't tried re-rooting with the sdcard method again yet.
The problem is that the API's changed that App Manager used to give access to the apps. The developer is aware of the issue and is trying to find a different way to achieve the same results. I just changed my default launcher to Go Launcher so I have access to all my apps, at least until App Manger starts working again.
I actually hadnt used mine in a while, but noticed yesterday the keyboard was back to default and realized something was up. Most of my apps still work, but the Play store asks me to login with an account, and when I click ok it just closes. Any ideas?
I don't remember how the sdcard root method pushed the play store, but if it pushed it to /system/apps, then play store is going to be screwed until you clear it out and install it again (reroot).
Edit: Just looked at the root zip file and it pushes all the gapps to /system/apps. The OTA update would wipe these out (as well as superuser).
Any tried Rerooting using the SDcard?
Having the same problem with Google Play.
Has anyone tried using the SD Card to reroot their device?
I think I will try it an see what happens.
SD Root
So, I backed up my nook, and took the plunge and used the SDcard I made to root 1.4.2 to root 1.4.3 and it worked flawlessly.
I had to re-login to Google Play, but I expected that.
The apps installed to the home screen of course still don't work, but opening them with another launcher or the App manager works fine.
I thought the SD card root method was designed to block OTA updates? Checking under the NT hidden settings showed an OTA block, though it now shows that I'm missing superuser since the new update unrooted my NT. Did this update have something different to defeat the block? I guess I need to seach for a new method to block updates (I seem to recall looking at some other posts on that topic).
Sent from my BNTV250 using xda app-developers app
Rooting in itself does not block OTA I believe. It simply gives you the ability to do so (either by changing the version to 9.9.9 or blocking B&N services entirely).
Understood, thanks. I'm a noob and just thought I remembered that being one of the "features" on the SD card along with a bunch of other apps (superuser, gapps, ADW, busy box, etc.). That was an issue at the time because 1.4.2 had just been published and was different than the prior versions for rooting. Thanks for the clarification!
Sent from my BNTV250 using xda app-developers app
I manually installed the 1.4.3 update and the SD Card root worked perfectly. One problem I've had since rooting though is that after updating apps from the Android Market/Play Store, the download arrows in the status bar stay active after the last app is 100% updated. The arrows go away after a reboot, but it's a little weird. I don't know if it's a market problem or has to do with 1.4.3., but everything else I had installed and loaded before the update is working flawlessly.
Supposedly when you actually install CWM on the device itself, not just on SD Card, you will not get updates due to factory recovery not being there. I do know that with CWM being internally installed + using the OTA blocker (999 one or Brian's) works. That is the way mine is and I've not gotten any updates.
Sent from my Transformer TF101 using xda premium
I was using the sdcard root method here:
http://forum.xda-developers.com/showthread.php?p=23591839
And only using CM7. It worked great and I wanted to check out CM9 so I wiped the card and started over to create the dual boot card on the same post. While doing that, 1.4.3 updated on my NT and now the sdcard wont boot into cyanoboot. Does anyone know if this is a problem with 1.4.3 or am I just screwing something up?
Sent from my DROIDX using Tapatalk 2

Categories

Resources