Database Users

[Q] B&N Nook Color Original App Interface on Rooted Nook Color?

I tried searching and could not find an answer. Hopefully someone can point me in the right direction, etc.
I have my Nook Color rooted but am trying to find a way to use the B&N Original interface for the library that lets you do shelves, etc. Is this possible with a rooted nook or is it only possible with the stock rom?
I would really like to be able to use it if possible. I cannot find any Android readers that does this to my liking.
Thanks for any help.

Flandrel said:
I tried searching and could not find an answer. Hopefully someone can point me in the right direction, etc.
I have my Nook Color rooted but am trying to find a way to use the B&N Original interface for the library that lets you do shelves, etc. Is this possible with a rooted nook or is it only possible with the stock rom?
I would really like to be able to use it if possible. I cannot find any Android readers that does this to my liking.
Thanks for any help.
Click to expand...
Click to collapse
If you have simply rooted it, then the library is still there as the B&N pop up bar is there with it and it's also in the apps drawer.
If you have installed a different rom, like cm7 or something, then the best you can do is the Nook for android app that B&N makes available on the market. Not sure if it has shelves though.

I did the Honeycomb on SD Card and then ended up doing the CM7 Mod which is on the device itself. Now I am trying to figure out how to for sure get back to the stock rom. I am sure I can do it on mine easily since I was on update 1.1.0. My wifes nook color was at 1.2. This is the one I gotta figure out.
Now will simply rooting it allow me the features of the Android operating system, layout and apps like the CM7 mod does or will it simply just be the nook color part? I am not really sure what is benefited from rooting.
What my perfect goal would be is to benefit from the B&N Nook Color that was there along with the benefits of the Android like CM7 gave.
Is this even possible?
Thanks

Flandrel said:
Now will simply rooting it allow me the features of the Android operating system, layout and apps like the CM7 mod does or will it simply just be the nook color part? I am not really sure what is benefited from rooting.
Click to expand...
Click to collapse
Actually, that's kind of the entire purpose of rooting it
Not sure what state your nook is in, but if you want to get back to rooted stock, do the 8 failed starts if you can first to get back there. If you've overwritten that part, you'll need to flash it back - try here.
My recommendation is that unless you can use B&N's restore to go back to 1.2, that you go to a previous version and then do the B&N update to 1.2.
You can run manual nooter 4.5.6 after that to root and you should be good to go. Just make sure and follow the instructions in the main post there.
There will be an update soon, but if 4.5.6 is still the version, then you should follow up by fixing the multi touch preferences

Flandrel said:
I did the Honeycomb on SD Card and then ended up doing the CM7 Mod which is on the device itself. Now I am trying to figure out how to for sure get back to the stock rom. I am sure I can do it on mine easily since I was on update 1.1.0. My wifes nook color was at 1.2. This is the one I gotta figure out.
Now will simply rooting it allow me the features of the Android operating system, layout and apps like the CM7 mod does or will it simply just be the nook color part? I am not really sure what is benefited from rooting.
What my perfect goal would be is to benefit from the B&N Nook Color that was there along with the benefits of the Android like CM7 gave.
Is this even possible?
Thanks
Click to expand...
Click to collapse
Flandrel, you are exactly at the point I was a couple of days ago!
You can do it, these are roughly the steps I followed.
1. Mine is new so it was already at v 1.2 but you need to go back to stock 1.2 there are threads on the Dev thread on how to do it.
2. Follow the easy steps on how to root it with Manual Nooter (again instructions on the development thread).
3. I overclocked it to 1.1 mhz using the stock OC kernel for 1.2.
4. I installed Nook Home B&N launcher to easily switch between the stock B&N interface to Froyo. Also installed Nook Color app manager from the market to be able to put any android app on the B&N interface screens. Installed Spare Parts to enable correct scaling of all the apps (so they fill all the screen as some of them remain at the phone format initially).
5. I installed ADW launcher, Kindle app adobe reader and all my favorite games.
6. Did some additional tweaks like disabling all the phone services that drain battery life.
The end result: a fast android + B&N experience thanks to XDA!!!! I have the best of both worlds as I find the B&N interface to be good, love the magazines and newspapers!
Out of the box sliding screens and turning pages on the B&N interface felty choppy. After adding the overclock kernel to 1.1 mhz things are smooth !
I know that if I install Phiremod or CM7 internally it would be even faster by I feel right now I have the best solution for my needs!
If you cant find the links to the above PM me and I'll be glad to help out.

Garoto1973 said:
Flandrel, you are exactly at the point I was a couple of days ago!
You can do it, these are roughly the steps I followed.
1. Mine is new so it was already at v 1.2 but you need to go back to stock 1.2 there are threads on the Dev thread on how to do it.
2. Follow the easy steps on how to root it with Manual Nooter (again instructions on the development thread).
3. I overclocked it to 1.1 mhz using the stock OC kernel for 1.2.
4. I installed Nook Home B&N launcher to easily switch between the stock B&N interface to Froyo. Also installed Nook Color app manager from the market to be able to put any android app on the B&N interface screens. Installed Spare Parts to enable correct scaling of all the apps (so they fill all the screen as some of them remain at the phone format initially).
5. I installed ADW launcher, Kindle app adobe reader and all my favorite games.
6. Did some additional tweaks like disabling all the phone services that drain battery life.
The end result: a fast android + B&N experience thanks to XDA!!!! I have the best of both worlds as I find the B&N interface to be good, love the magazines and newspapers!
Out of the box sliding screens and turning pages on the B&N interface felty choppy. After adding the overclock kernel to 1.1 mhz things are smooth !
I know that if I install Phiremod or CM7 internally it would be even faster by I feel right now I have the best solution for my needs!
If you cant find the links to the above PM me and I'll be glad to help out.
Click to expand...
Click to collapse
Can you tell me how you did this?? Additional tweaks like disabling all the phone services that drain battery life.
Thanks!!

Garoto1973 said:
Flandrel, you are exactly at the point I was a couple of days ago!
You can do it, these are roughly the steps I followed.
1. Mine is new so it was already at v 1.2 but you need to go back to stock 1.2 there are threads on the Dev thread on how to do it.
2. Follow the easy steps on how to root it with Manual Nooter (again instructions on the development thread).
3. I overclocked it to 1.1 mhz using the stock OC kernel for 1.2.
4. I installed Nook Home B&N launcher to easily switch between the stock B&N interface to Froyo. Also installed Nook Color app manager from the market to be able to put any android app on the B&N interface screens. Installed Spare Parts to enable correct scaling of all the apps (so they fill all the screen as some of them remain at the phone format initially).
5. I installed ADW launcher, Kindle app adobe reader and all my favorite games.
6. Did some additional tweaks like disabling all the phone services that drain battery life.
The end result: a fast android + B&N experience thanks to XDA!!!! I have the best of both worlds as I find the B&N interface to be good, love the magazines and newspapers!
Out of the box sliding screens and turning pages on the B&N interface felty choppy. After adding the overclock kernel to 1.1 mhz things are smooth !
I know that if I install Phiremod or CM7 internally it would be even faster by I feel right now I have the best solution for my needs!
If you cant find the links to the above PM me and I'll be glad to help out.
Click to expand...
Click to collapse
In step one you say you were on v1. 2 but went to stock 1.2. Do you mean 1.0.1?
I'd like to be able to do this also and will write a step by step if I can do it.
Sent from my SHIFTAO5P using xda premium

[Q] Manualnooter 5.02.19 audio bug. (involves "read to me" books)

Hey all. As is evidenced by my name, I typically just lurk and learn rather than add to the confusion. But now I am stumped. Being a person that doesn't post much, I can't put this in the Dev section so I hope someone much more intelligent than I gets wind of this post.
I have recently found a previously unnoticed bug with my Manualnootered NC. I am on a first gen Nook Color running manualnooter 5.02.19 over stock 1.42. I also have the Dalingrin OC Kernel (1.2 Ghz). I'm running GoLauncherEX with homecatcher over the stock launcher. Nothing outlandish or special installed. (Dolphin,netflix,Titanium, CWM, etc...)
When I attempt to use the "read to me" function of the childrens books, the audio cuts out before each sentence is finished.
Example: Text would read "Jack climbed up to the top of the beanstalk"...... But the audio that plays would be "Jack climbed up to......".
With one particular book, "The astonishing secret of awesome man", it was cutting off the audio of the reading part but would still play a trumpet sound effect and perform the animation that was part of the story.
It happens on new downloads as well as old purchases. I have tried archiving and re-downloading, re-rooting, and factory reset..... I even spent nearly an hour on live chat with a tech support rep who only succeeded in talking me into wiping my device by assuring me that it would fix the problem. It did not.
Eventually I restored to 1.0.1 and ran the whole gamut of updates back to 1.42 just to make sure I had a clean install.
No luck, although at one point I was also getting the blank "red screen" before I managed to get it re-rooted again.
So now I am wondering if anyone else has noticed this problem. It isn't an issue for me (since I can read to my self, thank you ) but it would be nice to allow my kids to use their read to me books again.
Any ideas? If anyone needs a better idea of the problem I can make a youtube video and post a link to better illustrate the issue.

Does the problem only occur after you root or even when you are restored to plain stock 1.4.2? Sounds like it might be a B&N issue though they weren't able to help you. If it just occurs after rooting an easy solution would be to run a bootable SD card with CM7 or CM9 and leave stock unrooted so you could have the feature.
Then you have all the features of a full tablet from the SD card and can always boot back to stock for the read to me feature.
JP

I had considered that but it gave me the "red screen" on stock. Not sure if maybe there was some remnant from my previous root that may have bern causing this or not. All I am sure of is that before 1.42 they worked. I wonder if anyone else had the "red screen" on stock like I did. I saw one other post about it but I think they were rooted.
Sent from my BNRV200 using Tapatalk 2

I would set clock speed to 800 mHz and see if that fixes it. Overclocking it may cause the read to me app to process the video on them too fast for the speech to fully read the sentence.

That is what I had thought. I did set the clock speed to 800Mhz with no luck. I wonder if I should just reflash the stock kernel and try that...
Sent from my DROID X2 using Tapatalk 2

I will be looking into this issue over the next couple day and getting back with you. I have a couple ideas on what might be causing the issue, but no hard evidence at this time.

Thanks so much! I know you probably have other pressing issues but I (and everyone else who enjoys the use of their rooted Nook) appreciate your time and effort. If you need any specific info from me just let me know.
Sent from my DROID X2 using Tapatalk 2

TheDroidLurker said:
Hey all. As is evidenced by my name, I typically just lurk and learn rather than add to the confusion. But now I am stumped. Being a person that doesn't post much, I can't put this in the Dev section so I hope someone much more intelligent than I gets wind of this post.
I have recently found a previously unnoticed bug with my Manualnootered NC. I am on a first gen Nook Color running manualnooter 5.02.19 over stock 1.42. I also have the Dalingrin OC Kernel (1.2 Ghz). I'm running GoLauncherEX with homecatcher over the stock launcher. Nothing outlandish or special installed. (Dolphin,netflix,Titanium, CWM, etc...)
When I attempt to use the "read to me" function of the childrens books, the audio cuts out before each sentence is finished.
Example: Text would read "Jack climbed up to the top of the beanstalk"...... But the audio that plays would be "Jack climbed up to......".
With one particular book, "The astonishing secret of awesome man", it was cutting off the audio of the reading part but would still play a trumpet sound effect and perform the animation that was part of the story.
It happens on new downloads as well as old purchases. I have tried archiving and re-downloading, re-rooting, and factory reset..... I even spent nearly an hour on live chat with a tech support rep who only succeeded in talking me into wiping my device by assuring me that it would fix the problem. It did not.
Eventually I restored to 1.0.1 and ran the whole gamut of updates back to 1.42 just to make sure I had a clean install.
No luck, although at one point I was also getting the blank "red screen" before I managed to get it re-rooted again.
So now I am wondering if anyone else has noticed this problem. It isn't an issue for me (since I can read to my self, thank you ) but it would be nice to allow my kids to use their read to me books again.
Any ideas? If anyone needs a better idea of the problem I can make a youtube video and post a link to better illustrate the issue.
Click to expand...
Click to collapse
Could you download this file, and flash it with CWM, LINK. The problem that you are having is caused by a bug in the current release of Adobe Air. Once you have flashed this file, you will need to go into the Google Play Store and turn off auto updates for Adobe Air. DO NOT update Adobe Air.
What this file will do, it will delete your current Adobe Flash and Air from the data partition, install the most up to date Adobe Flash, and last working Adobe Air into the system partition. By installing the files into the system partition, you will always be able to go into manage applications, and uninstall any updates back to these working versions. When Adobe Air is updated in the future, you can update it to see if it works, and if it don't just uninstall back to this version.
As for the "red screen" that you came across, this will happen when Adobe Flash is uninstalled from the device.
Please report back to this post if it works, or does not work, so that I can update the whole MN 5 package for everyone else to enjoy. I only have a few read to me books to personally test this on, and not all of them had this problem, so I really need the feedback from you.

That did the trick! Thanks for sorting that out. Now my four year old can get his boogery little fingers all over my Nook again!
Once again, thanks.
Adam.
Sent from my BNRV200 using Tapatalk 2

TheDroidLurker said:
That did the trick! Thanks for sorting that out. Now my four year old can get his boogery little fingers all over my Nook again!
Once again, thanks.
Adam.
Sent from my BNRV200 using Tapatalk 2
Click to expand...
Click to collapse
Don't forget to use the "Thanks" button when a post helps you out Go on its right down there vvvv
Edit: I see you might not be able to if you are using the forum app to post at the moment.

Extreme increase of incompatible apps suddenly?

First, please excuse any typos made by me. I'm running an expired version of Swiftkey, which doesn't give me any autocorrect features. (this is actually relevant to my problem.) I just weny out today and purchased a prepaid google play card to make some more purchases when, behold, I find that the paid version of swiftkey is no longer "compatible" with my nook color. I found that to be true with the majority of apps that I have installed. (out of hundreds of apps, only about 35 of them claim to be compatible w/ my nook color. Of course, these apps aren't truly incompatible. I already have all of them downloaded and running flawlessly on my nook. So why the influx of "incompatible" apps? Has anybody else had this problem?
One thing I would note is that I changed my device model to a nexus 7. I did this for various reasons. For one, I needed to access some google books on my nook, but tey weren't compatible with ereaders (the nook is registered as an ereader), they were compatible with tablets though, so I edited some system files, cleared the cache and data for both the play store and google books, and I ended up getting the books that I wamted on my nook. I could see how this could cause problems with compatibility, but my nook had been altered for about 2+ weeks and nothing has happened to the play store since I changed the system files (that I know of). After all, if a problem would have decided to arise, it would have done so when I replaced the market cache, not randomly during a weekday. I'm next to certain that this sky-rocketed incompatibility did not originate at the time of alteration, as I just downloaded jetpack joyride only a day or two before it showed up as incompatible with my nook in the play store. I believe that I've only had this problem for the better of 3 days. Has anybody else haf this problem too?
System specs are the default of verygreen, though I'm currently running a nightly build of cm7. I think all this info is in my signature already. Note that I haven't changed anything on my tablet except for dpi density (set it back to 160), as I considered the possibility that it could have been caused by dpi problems, which it apparently isn't. This was after I notoced the increase of incompatible apps.
Again, take note that many of these "incompatible" apps are already installed and running fine on my nook color.
I'm sorry if I don't have very much helpful information. I'm confused, worried, and tired. When writing this, I could have even been half asleep. Please forgive me if I'm acting like an idiot.
Anyways, has anybody else had this problem? Cn anybody recreate my problem? Does anybosy have a way to fix this problem? Please let me know ifbyou can help
Sent from my Nook Color using the XDA Android app. The original text got deleted.

I'm running mirage 7.2 , on my Nook. I just checked and jetpack joyride is listed as compatible.
Sent from my MB860 using xda app-developers app

Running Swiftkey (purchased) on my NC running MirageKang CM7. Downloaded and installed it day before yesterday, I think.

When you changed your device to a Nexus 7... exactly what edits did you do?
You say you edited some system files as well...
If someone wants to give me the information in the Devices Thread in my signature, I will include Nexus 7 in the devices.dat for the IMEI Generator

DizzyDen said:
When you changed your device to a Nexus 7... exactly what edits did you do?
You say you edited some system files as well...
If someone wants to give me the information in the Devices Thread in my signature, I will include Nexus 7 in the devices.dat for the IMEI Generator
Click to expand...
Click to collapse
ro.product.model=Nexus 7 (with space)
ro.product.manufacturer=asus
ro.product.device=grouper
Confirmed from my second stock Nexus 7 with a broken screen already. Got a hug from an 8 year old wearing a wrist watch...the thing is FRAGILE! You should see my Nook Color, man. I dropped this thing on concrete several times already, the corner is busted in and the power button busted off a year ago, but the thing is running strong.
No wifi chip since my son dropped it in the bathtub though...let's see the N7 live through that.
I posted this here instead of in your Device Thread so people would know you got it. Maybe the wrong thing, idk...
(and bonus info..if you shake my Nook it rattles from the rice that is still shaking around in there from Project Dry...like Project Butter except more like Project Roadrunner...)

Are you sure you wiped data off Google play before changing the screen density.
Sent from my MT11i using xda app-developers app

mateorod said:
ro.product.model=Nexus 7 (with space)
ro.product.manufacturer=asus
ro.product.device=grouper
Confirmed from my second stock Nexus 7 with a broken screen already. Got a hug from an 8 year old wearing a wrist watch...the thing is FRAGILE! You should see my Nook Color, man. I dropped this thing on concrete several times already, the corner is busted in and the power button busted off a year ago, but the thing is running strong.
No wifi chip since my son dropped it in the bathtub though...let's see the N7 live through that.
I posted this here instead of in your Device Thread so people would know you got it. Maybe the wrong thing, idk...
(and bonus info..if you shake my Nook it rattles from the rice that is still shaking around in there from Project Dry...like Project Butter except more like Project Roadrunner...)
Click to expand...
Click to collapse
Thanks, added to devices.dat... will be uploaded in my devices thread in a minute.

SacTappingUni said:
I just weny out today and purchased a prepaid google play card to make some more purchases when, behold, I find that the paid version of swiftkey is no longer "compatible" with my nook color. I found that to be true with the majority of apps that I have installed. (out of hundreds of apps, only about 35 of them claim to be compatible w/ my nook color. Of course, these apps aren't truly incompatible. I already have all of them downloaded and running flawlessly on my nook. So why the influx of "incompatible" apps? Has anybody else had this problem?
Click to expand...
Click to collapse
I'm having a similar problem. Just changed from a rooted Nook Color running 1.X to a CM7 MiRaGe. Many apps are incompatible. So wiped/reinstalled everything. Before connecting to a Google account, I gave my NC a IMEI, thinking that would help. No luck. (With DizzyDen's IMEI generator, I tried NookColor stock 1.4.X, DizzyDen's CM7 settings, and Samsung Galaxy Tab.) Example incompatible app: Chrome.
Other ideas?
Thanks in advance...

Jake5Snooze said:
I'm having a similar problem. Just changed from a rooted Nook Color running 1.X to a CM7 MiRaGe. Many apps are incompatible. So wiped/reinstalled everything. Before connecting to a Google account, I gave my NC a IMEI, thinking that would help. No luck. (With DizzyDen's IMEI generator, I tried NookColor stock 1.4.X, DizzyDen's CM7 settings, and Samsung Galaxy Tab.) Example incompatible app: Chrome.
Other ideas?
Thanks in advance...
Click to expand...
Click to collapse
Chrome will not work with CM7 because that app is built for ICS Android 4.0 and up only. I looked over the permissions for that app.

DizzyDen said:
When you changed your device to a Nexus 7... exactly what edits did you do?
You say you edited some system files as well...
Click to expand...
Click to collapse
I changed the device info and manufacturer info and whatnot to match the Nexus 7.
In later news, after it was set to 160 dpi for a night, it deleted a couple of my apps and data caches in many of my important apps. Then it let me purchase swiftkey. But after setting my dpi back to 180, it showed as incompatible again. Making the dpi density is causing this?

Setting the dpi to 180 will definitely cause app incompatablity. The play store only likes 120, 160, 240 and now 172 for their new tablet. Most apps aren't compatible with nonstandard dpis. You can set to 160 in puild.prop, go to settings -> apps and clear data for google play. Then go into the market and download happily. When finished, change back to 180. You will have trouble updating the apps without changing back but it does work. Clearing the data just Makes google look again at your system. Otherwise, it takes a while before the changed dpi registers with the playstore.

Yes, non standard (160, 240 are "standard") density (dpi) settings will cause compatability issues.

Well, I guess that we've figured out the problem. I don't have anything against setting my dpi to 160. It's just that Google Play Music will only work if my nook's dpi is set to 180 or more. I supposed I'll have to find another fix for Google Play Music. Thanks guys!

New Nook HD+ owner here!

Hi all, Just got a Nook HD+ on sale. I know it isn't the newest, shiniest piece of gadgetry and I don't really care. So far I'm digging it, I really like the different aesthetic. (Who puts a hole in the corner of their tablets?!.. really?) and aside from rooting it, which I try to do to every android device I get right off the bat. What else is there?
I see there are a few 10.1/2/3 ROM's out there but what are the actual benefits compared to just using the stock ROM? Also, is there any custom kernels floating around? I'm always a fan of messing with kernel stuff like undervolting/overclocking/governor tweaks/etc.

I think your answers are in each rom development thread. But I'd say cm 10.2 (I didn't try cm 10.1) is much more responsive than stock. I didn't find any kernel out there besides those inside the roms.

I suggest getting the most recent RC3 release of CM 10.1 and in performance settings, set transparency to 16bit and purge assets.
That seems to be the best overall combo.
10.2 has no apparent benefit for the HD+ as far as performance. The trim function has been disabled since not Nook flash friendly for a lot of units and OpenGL 3 is not supported by the chipset in the HD+.

Hmm, OK, ok...
I could have sworn I saw a post here talking about using 10.3 but lurking through the dev thread I don't see it anywhere. I'll keep looking.
Are the nook apps usable on CM roms? I know the launcher won't be but is it possible to use just the reader, library, etc? Thanks for the response guys! Also, anyone familiar with using CM on the Nook, do Hulu, Vudu, Netflix all work also the HDMI-out and bluetooth? These are all things I use and can't lose.
UPDATE: Oh, my bad, the post says "10 1.3" which is a little confusing and I saw it as 10.3
http://forum.xda-developers.com/showthread.php?t=2459574

Im new to Tablets (only have a Nook HD+ for acouple weeks ) but not flashing.
Just installed CM 10.1.3 (last night)
One thing which i was after (and the main reason for me) was USB thumbdrive support/storage (link about it) and that worked great.
After, i did install the B&N "store" app (the green 'n' app) and it installed fine (had to install it via .apk found out side of the Google Play (dont know if i can post links to apps at this forum)). With that 'n' app, you can shop the B&N site along with reading a book. Will look later tonight and see if i can install there library app.
Dont know about HDMI (am wondering the same - but not a big deal for me).
As for bluetooth, i tried a Logitech MX5000 ("desktop") keyboard just to see what happens, they made the hand-shake and connected but nothing after that... i did not try too hard though... just wanted to see what would happen. That keyboard is the only bluetooth "device" i have.
_

iMisspell said:
Im new to Tablets (only have a Nook HD+ for acouple weeks ) but not flashing.
Just installed CM 10.1.3 (last night)
One thing which i was after (and the main reason for me) was USB thumbdrive support/storage (link about it) and that worked great.
After, i did install the B&N "store" app (the green 'n' app) and it installed fine (had to install it via .apk found out side of the Google Play (dont know if i can post links to apps at this forum)). With that 'n' app, you can shop the B&N site along with reading a book. Will look later tonight and see if i can install there library app.
Dont know about HDMI (am wondering the same - but not a big deal for me).
As for bluetooth, i tried a Logitech MX5000 ("desktop") keyboard just to see what happens, they made the hand-shake and connected but nothing after that... i did not try too hard though... just wanted to see what would happen. That keyboard is the only bluetooth "device" i have.
_
Click to expand...
Click to collapse
I'm pretty sure posting it would be fine because it isn't a paid app and is freely available. If you still leery you could IM it to me, I'd like to give it a try. I have the HDMI adapter and it worked fine with the stock ROM but I'm only getting a blank screen on the TV with 10 1.3. I've read it is working though so I am going to tweak it a little bit to see what the deal is.

felacio said:
I'm pretty sure posting it would be fine because it isn't a paid app and is freely available. If you still leery you could IM it to me, I'd like to give it a try. I have the HDMI adapter and it worked fine with the stock ROM but I'm only getting a blank screen on the TV with 10 1.3. I've read it is working though so I am going to tweak it a little bit to see what the deal is.
Click to expand...
Click to collapse
Since you've been here for 6+ years, ill take your word for it
http://www.apk-planet.com/download_NOOK_Read_Books_and_Magazines/tech/
Found that via a google search nook .apk
I did search for the Library app but did not find anything.
[EDIT]
Just discovered (thanks) 1mobile and they have the 'n' B&N store app also.
http://www.1mobile.com/bn-ereader-79949.html
_

I'm in the same boat, just got a new Nook HD+ (came free with my car). I used the stock ROM for a day or so, pretty fast but limited in scope. I've installed CyanogenMod 10.1.3 using the instructions from the dummies thread, it ran fine for about half a day and now suddenly performance is awful. Animations lag, trying to change the settings lags, there's input lag, I have to wait 1-2 seconds for the keyboard to come up, 2-3 seconds to tap on different sections in Settings. I thought maybe I installed too many apps so I tried to wipe it but I can't. "wipe data/factory reset" in CWM still leaves crap behind, Factory data reset in Settings does the same. Now I have 6 GB left of 12.67 GB and nothing installed. Is there any way to fully remove everything?
Edit: some exploration with du in terminal revealed two huge folders, Android/data and Android/obb. Sure enough, there's my missing 6 GB. How does this not get deleted? Does reset mean something else in Android than other mobile operating systems?

rpop said:
I'm in the same boat, just got a new Nook HD+ (came free with my car). I used the stock ROM for a day or so, pretty fast but limited in scope. I've installed CyanogenMod 10.1.3 using the instructions from the dummies thread, it ran fine for about half a day and now suddenly performance is awful. Animations lag, trying to change the settings lags, there's input lag, I have to wait 1-2 seconds for the keyboard to come up, 2-3 seconds to tap on different sections in Settings. I thought maybe I installed too many apps so I tried to wipe it but I can't. "wipe data/factory reset" in CWM still leaves crap behind, Factory data reset in Settings does the same. Now I have 6 GB left of 12.67 GB and nothing installed. Is there any way to fully remove everything?
Edit: some exploration with du in terminal revealed two huge folders, Android/data and Android/obb. Sure enough, there's my missing 6 GB. How does this not get deleted? Does reset mean something else in Android than other mobile operating systems?
Click to expand...
Click to collapse
Those folders are in your media (sdcard) folder and media does not get wiped in a factory reset. In CWM you need to go to mounts and storage and format 'data and datamedia' in order to wipe your media.
Sent from my Nook HD+ running CM10.1 on emmc.

I love my Nook HD+ and that is after trying a Samsung Note 8, a Nexys 2013 and others. Really for the prize you can't beat it!
I have tried pretty much every ROM there is here in XDA both from SDCard and emmc. For my Nook HD+ in particular nothing beats the Stock ROM with Unknown Sources and Root. I also tried Nova, Apex, SPB, Smart, Go EX, and AWD launchers in their Pro versions but the only one that was really fast and had no lagging at all was Next Launcher and that is the one I have know on my HD+.
To be able to use USB OTG (not needed on CM 10 thanks to verygreen) on Carbon, Slim, etc., I used the usbhostswither.apk that is included on Xperia Carbon JB, installed it and worked great. I haven't been able to installed it on my HD+ even with root and unknown sources enable, it gives me a parsing app error. Trying to see if I can installed it and if it workd to turn on and off USB Host on Stock Rom with root.
I tried and now use 3 apps from the forum that really rock, FX Explorer, Gallery Plus and WebSharing Lite.
You are gonna have a blast with your HD+ and now that some at XDA have started to test and port Ubuntu Touch to it, well you won't be without a whole lot of options to mess with your Nook :laugh:
---------- Post added at 01:32 PM ---------- Previous post was at 01:14 PM ----------
Hi leapinlar and community, first thanks for all your contributions, they have enable the Stock Rom to be a great alternative for those of us that like many of it features.
I have a problem installing the USBHostSwitcher app on the HD+ rooted and with unknown sources enabled. The weird thing is that I was able to install and use the app successfully when testing emmc Carbon Rom JB and Xperia Tweeked for HD+. I was also able to installed it to other devices like my Galaxy Note II (stock, not rooted).
The Nook installer error on HD+ reads " Parse error" "There is a problem parsing the package".
Is there a way to create a package so I can flash an app (like we do with the Google Apps?
Thanks in advance for any recommendations.

gmicalzoma said:
Hi leapinlar and community, first thanks for all your contributions, they have enable the Stock Rom to be a great alternative for those of us that like many of it features.
I have a problem installing the USBHostSwitcher app on the HD+ rooted and with unknown sources enabled. The weird thing is that I was able to install and use the app successfully when testing emmc Carbon Rom JB and Xperia Tweeked for HD+. I was also able to installed it to other devices like my Galaxy Note II (stock, not rooted).
The Nook installer error on HD+ reads " Parse error" "There is a problem parsing the package".
Is there a way to create a package so I can flash an app (like we do with the Google Apps?
Thanks in advance for any recommendations.
Click to expand...
Click to collapse
Even if you can get it to install, I'm not sure it will work on stock. I know verygreen had to mod the kernel to make it work. And I think all the other ROMs like Carbon, etc, use his kernel.
See this post:
http://forum.xda-developers.com/showthread.php?p=42501199
Sent from my Galaxy Tab 2 using XDA Premium

Nook Simple Touch Noob Question

Hi
I have a nook simple touch - 1.2.1 firmware not rooted yet, I only want to use it as an e-reader but the ghosting is awful compared to my wifes kindle of the same generation (non touch).
I've been trying to look around and find out what I can do, is there a way to force it to refresh every page, some searching seems to suggest the issue was better on older firmwares, why B&N didnt include an option like amazon to force refesh every page who knows (that's not enabled on my wifes kindle) - the Kindle is just much easier to read in direct bright sunlight but I'm sure theres some tweaking that can be done to improve it

I have to say I am surprised by your description of your NST. I've been paying close attention to mine today while reading and I may be losing my vision but I can't see the ghosting you are describing. I've always felt the native Reader and its default settings worked really well. In some other apps there may be issues with ghosting, but not in the reader.
I'm running FW 1.21 also and while I have rooted and altered my device a lot, to my knowledge I haven't done anything to the functioning of the Reader app. Are you sure you don't have some kind of hardware issue?

nmyshkin said:
I have to say I am surprised by your description of your NST. I've been paying close attention to mine today while reading and I may be losing my vision but I can't see the ghosting you are describing. I've always felt the native Reader and its default settings worked really well. In some other apps there may be issues with ghosting, but not in the reader.
I'm running FW 1.21 also and while I have rooted and altered my device a lot, to my knowledge I haven't done anything to the functioning of the Reader app. Are you sure you don't have some kind of hardware issue?
Click to expand...
Click to collapse
It could be a hardware issue but it's well out of warranty, I do notice the ghosting on the kindle too so maybe im just susceptable to spotting it and having it irritate me, just wondered if there are any tweaks to control thow often it refreshes as its ok once it refreshes the screen

damianiw said:
It could be a hardware issue but it's well out of warranty, I do notice the ghosting on the kindle too so maybe im just susceptable to spotting it and having it irritate me, just wondered if there are any tweaks to control thow often it refreshes as its ok once it refreshes the screen
Click to expand...
Click to collapse
OK, so look here at what Renate suggests.

nmyshkin said:
OK, so look here at what Renate suggests.
Click to expand...
Click to collapse
Seemed to be very complex, so I went for root and under there is the option for how many pages before full refresh
also installed cool reader for good measure and very happy - problem solved

damianiw said:
Seemed to be very complex, so I went for root and under there is the option for how many pages before full refresh
also installed cool reader for good measure and very happy - problem solved
Click to expand...
Click to collapse
Excellent! Your rooting method must be different from mine but now we're both happy

Good job, @nmyshkin!

Thanks everyone, my main concern was rooting would stop it behaving like an e reader but relaunch I a great launcher and the default options for home and library mean I have best of both and importantly control over the refresh as my nook does appear to ghost far more than a friends on comparison, for the £29 paid over a year ago the nook is awesome

Comparing my nook to a friends the contrast looks really different so maybe this unit wasnt calibrated right - i'm now looking for a contrast adjuster to see if that solves me needing to fully refresh the screen so much as that will be using more battery