I'm new to the Nook Color area of XDA, so I apologize in advance if my question is one that has been answered. I did search, but was not able to find an answer to my exact situation, so here it is:
I'm getting a NC as a gift for my family to use. I understand that the stock Rom for the NC allows you to access (what appears to me to be) B&N's version of the Market, with apps optimized for the NC. That sounds like a good thing, as it would seem like they would be the more stable versions (as they are built/tweaked specifically for the NC).
However, I'm familiar with (in general) the rooting/custom ROMs/overclocking concepts of an Android device, so I'm thinking I would like to put MIUI or CM7 on the device so that I can make it be the most powerful and useful device possible.
Here's my dilemma - I can't seem to find any posts that say whether the apps that a person can get from the B&N "market" will run (if transferred via ADB or Root Explorer, or whatever the NC equivalent may be) on a CM7/MIUI setup, or if it is just better to get the normal Market version of those apps.
For example: If I get Angry Birds in the B&N market, I would assume it's designed to run a certain way on the NC. If I download it from the Android Market, I would assume it's going to run differently. Is there any perceptible difference between the two?
I'm not entirely averse to staying with the stock ROM if the apps are heavily tied to (and perform better with) the stock setup. However, if it's not really going to matter whether they come from B&N or Google, I would prefer to be able to use a custom ROM and still be able to run (within reason) all the apps I'm used to using.
I guess that ultimately I can dual-boot if I find that the B&N app versions are superior, but having just dealt with a letdown from a Pandigital Novel, I'm wanting this experience to get off on the right foot. To me, the optimal situation would be a full install of a custom ROM, with either the optimized B&N apps running or equivalent Android Market apps running.
Thanks in advance for any advice/experiences anyone can offer.
I think it depends on whether or not the application requires anything that would be only in the B&N version of Android. I've used the Pandora application from the stock OS on CM7 and worked fine, but there may be some that won't. I haven't ran stock since about a week after getting mine.
Edit: I realized I rambled, so feel free to skip the long version below.
Short version: Not sure if you can ADB pull/push the paid B&N apps to another install, don't know how (if any) DRM works for that. While B&N apps are built specifically for the resolution, I find that they are very expensive (compared Angry Birds Seasons HD 99cents to B&N Angry Birds Seasons (HD) 3 dollars, and honestly I could not see a difference between the two) and if your Nook is not overclocked (which requires rooting), tend to be slow. There are some that are quite nice that I haven't found the equivalent of yet in Amazon App/Google Market such as Word Rainbow. You can find replacements/equivalents for most of the B&N apps in the other two stores I've mentioned. B&N sadly has a very small selection of apps that are actually any good, imo.
The native B&N reader app is far better than the Nook app (some functionality like enhanced children's books ONLY available on native app) and has not been, afaik, successfully ported.
Long, rambly, feel-free-to-ignore version pertaining more to ROMS than apps:
I've run unrooted stock, Manualnootered (rooted) stock, and various flavors of CM7.
- The native ereader app in stock has a very, very nice UI. Much better imo than the Kindle's. I still have to find a good replacement for it. It is also the only way, AFAIK, that you can read those enhanced children's books that lets you record your voice, or that has animations/reads to the viewer. If this is important to you, then stick to unrooted or rooted stock.
- Unrooted stock is so slow, that after having used overclocked rooted stock and CM7, I cannot bring myself to use it again. Even page turns were slow. App loading times are abysmal, and live wallpaper will not only eat your battery but cause everything else to slow down.
- Manualnootered stock is quite nice because you get to install 3rd party apps, have access to not only B&N's own store but also Google Market and Amazon App Store if you install them. You can also overclock so it's a much faster experience (highly recommended).
*Drawbacks are that there are some bugs that you may run into: Update issues with Adobe products, which cause boot loops (there's a fix for it). Not all apps may appear in Google Market (several things you can try to fix). And finally, if there's an OTA (over the air) update to the next (1.4, assuming you manualnooter to the latest 1.3 update), it will break your root/nootering and you will have to do it all over again.
- Installing a Cyanogenmod ROM: You get Gingerbread instead of Froyo (2.3.x vs 2.2.x), lots of goodies too many to list. With Tablet Tweaks (built in) and Nook Color Tools, you can tweak the bleep out of your Nook Color in terms of performance. You won't have to worry about OTA updates or the boot loop issue, but you do run into issues such as: "Your device is not compatible" messages when you try to install certain apps from Google Market (there are workarounds for most of them), SOD (Screen of Death, supposedly fixed with latest dalingrin kernel update), wifi issues (disconnect, difficulty connecting, etc.), force closes of random processes if using a nightly build. You could go with the stable build, but honestly the improvements in the nightly builds far outweigh the bugs which get ironed out pretty quickly.
The best part is, you don't even have to install just one of these. If you want, you can either a) dual boot stock + custom rom from EMMC (native Nook Color space), b) boot custom rom from SD install and keep unrooted stock to avoid voiding your warranty if you're concerned about that c) mix and match dual booting etc. It is pretty much impossible to brick your Nook Color.
After several months I've found that I prefer using CM7 builds simply because they are so much more customizable than rooted stock. I would suggest trying out both (stock, rooted or not, + CM7) via the SD card install + stock EMMC if you're not leaning towards one or the other.
Thank you. That was a very clear, concise, and complete answer to my question (and a good excuse for me to use some alliteration).
As I'm not really interested in the eReader functionality of the device, I'm guessing a Manualnootered/CM7(or MIUI) configuration is where I"ll go, at least until I'm sure what will work better for me.
Don't be surprised if you see me popping up in here again, asking more questions.
Sorry to revive an old thread, but I'm finding myself in a similar situation again.
I've downloaded and successfully been able to run CM7.2 from an SD card, and I've been really impressed with how much faster it makes the Nook run. I'm wanting to push this over to the internal storage so that my family can enjoy the faster performance with all of their stuff on it (I've tested and been able to make a Titanium Backup of a Nook app, which restored correctly in the CM7.2 SD image).
There's one hangup, though - I can't figure out how (if it's possible) to get the stock Nook reader app to work on the CM7.2 image. This wouldn't really be a problem except that I have some "read to me" books that I've paid for that absolutely have to be available on whatever is on the device.
I've looked at this thread in the Tablet section, which has a package that can "re-bloat" the device with the stock reader.
I'd like to do something similar, and I think I have the files needed to do this, but I can't figure out how to push them into the image on the SD card.
-When I open the SD card from my computer, I see all the non-expanded files (e.g. MLO, uRamdisk, uImage, etc.), but no standard Android root directory setup.
-If I attach it to my computer when CM is running, I can see the storage, but not the root directory.
-If I use a root file explorer, I can see the root directory, but I can't mount it as read/write.
-If I use ADB, I can't mount the image as read/write, and adb push fails because it's not read-write.
I'd really like to try and get this working, as I'm not feeling comfortable with messing with the internal setup just yet (I don't want to break something that is working), but I'm guessing I'm hitting a wall because the SD card method is running in some sort of virtualized environment.
Anyone have any suggestions?
jmtheiss said:
Sorry to revive an old thread, but I'm finding myself in a similar situation again.
I've downloaded and successfully been able to run CM7.2 from an SD card, and I've been really impressed with how much faster it makes the Nook run. I'm wanting to push this over to the internal storage so that my family can enjoy the faster performance with all of their stuff on it (I've tested and been able to make a Titanium Backup of a Nook app, which restored correctly in the CM7.2 SD image).
There's one hangup, though - I can't figure out how (if it's possible) to get the stock Nook reader app to work on the CM7.2 image. This wouldn't really be a problem except that I have some "read to me" books that I've paid for that absolutely have to be available on whatever is on the device.
I've looked at this thread in the Tablet section, which has a package that can "re-bloat" the device with the stock reader.
I'd like to do something similar, and I think I have the files needed to do this, but I can't figure out how to push them into the image on the SD card.
-When I open the SD card from my computer, I see all the non-expanded files (e.g. MLO, uRamdisk, uImage, etc.), but no standard Android root directory setup.
-If I attach it to my computer when CM is running, I can see the storage, but not the root directory.
-If I use a root file explorer, I can see the root directory, but I can't mount it as read/write.
-If I use ADB, I can't mount the image as read/write, and adb push fails because it's not read-write.
I'd really like to try and get this working, as I'm not feeling comfortable with messing with the internal setup just yet (I don't want to break something that is working), but I'm guessing I'm hitting a wall because the SD card method is running in some sort of virtualized environment.
Anyone have any suggestions?
Click to expand...
Click to collapse
First off, if you want to keep the kid's books, you have to keep stock on internal memory. It is the only way they can run. They won't work on CM. That rebloat pack is just to put the stock nook reader back on stock.
When you put the SD card in the PC it is normal that it sees only the boot partition of the SD.
When you connect your nook to the PC with the USB cable, the PC can only see the internal media partition (emmc) and partition 4 of the SD (sdcard).
Root Explorer will let you read/write if you touch the toggle button at the top of it's screen.
With adb, what are you trying to mount?
Thanks for the reply.
I'm using ES File explorer, which I know works to give me the read/write capabilities, but after mounting /system (and/or /system/app) as read-write, I was not able to write files into because it said that it was not read-write.
With ADB, I was trying to mount either /system or /system/app as rewritable, but I couldn't get it to take.
That's a bummer about the kid's books thing. I was hoping I could use a better rom to get the performance up. Just because I'm curious, what is the issue that keeps the reader from working with the CM roms? Is it some sort of signature problem that B&N checks when you sign in with the reader app?
jmtheiss said:
That's a bummer about the kid's books thing. I was hoping I could use a better rom to get the performance up. Just because I'm curious, what is the issue that keeps the reader from working with the CM roms? Is it some sort of signature problem that B&N checks when you sign in with the reader app?
Click to expand...
Click to collapse
The problem with the kids books is they are not really books. They are interactive applications that the stock reader can access. That is how the books are smart and know how to respond to the kids touches.
And people have tried to take the stock reader and install it on CM, but it will not run.
I assume you are running ES Explorer from CM. CM is already rooted so it should work. I have used ES Explorer a little and it seems to me it had a setting that turned on root access for it.
leapinlar said:
The problem with the kids books is they are not really books. They are interactive applications that the stock reader can access. That is how the books are smart and know how to respond to the kids touches.
And people have tried to take the stock reader and install it on CM, but it will not run.
I assume you are running ES Explorer from CM. CM is already rooted so it should work. I have used ES Explorer a little and it seems to me it had a setting that turned on root access for it.
Click to expand...
Click to collapse
Alright. Thanks, that makes a lot more sense.
I'm using Epsilon Project - ICS ROM on galaxy s3 but Easy UMS does not working as mass storage. Even it mount the card & works fine as MTP except UMS as mass stoare... plz provide help
Are you rooted?
You need to make sure you have busybox installed, busybox installer can be found in the Play Store.
(this question would have been better asked in Q+A forum section, or even better the thread for the app in question)
Lennyuk said:
Are you rooted?
You need to make sure you have busybox installed, busybox installer can be found in the Play Store.
(this question would have been better asked in Q+A forum section, or even better the thread for the app in question)
Click to expand...
Click to collapse
Yes my phone is rooted & installe busybox 1.19.4 but still same problem...
So your opening the app (without usb connected) hitting UMS button, it should then either give you an error message or tell you that it was successful.....
if successful - plug into pc
if not then tell us what the error message said.
I'v got the same prblem - last version of busybox is on board and tehrs an error sayin "could not mount maby busybox is not installed"...
Same problem on different ROMs...
Bought a new nexus 7 yesterday (after having my old one stolen...) and I decided to root and install AOKP JB MR1 Milestone 1. I'm really impressed with it but I was surprised to find the AOSP browser rather than Chrome and a lack of Performance Control.
I tried to install Chrome as a system app (download from Play, push from /data/app to /system/app and set permissions to rw-r--r--) and rebooted. I was again surprised when I found that "Chrome's installation was incomplete." It worked fine in /data/app but I am now curious as to why it won't work in /system/app. (Sorry if this sounds nooby, I haven't dealt with rooting Nexus devices before, I only rooted my crappy old GT-S5830)
Does anyone have a solution? Missing lib files or something else that I need to transfer over?
And as a sidenote, is Performance Control compatible with the N7 on this build? And does anyone have a working version of it?
why are you trying to force it to be a system app? what benefit do you think its going to give you?
Pirateghost said:
why are you trying to force it to be a system app? what benefit do you think its going to give you?
Click to expand...
Click to collapse
No major benefits, but it does save some space on the data partition (and my system partition is only half full). I'm just curious as to why it won't execute properly when installed and upgraded as a system application. I'm fine with having it in /data/app, I was just curious.
Anyone have an answer?
I found THIS
So as many of you know, bombsquad doesn't work out of the box on cm11. Fortunately, I've found a sollution!
As far as I can tell, bombsquad doesn't work because it has a built in "protection" that checks to see if your actually using an ouya. It does this by checking the build.prop file. In particular the line that says:
ro.product.device=ouya_1_1
However this was changed to
Ro.product.device=ouya
in cm11.
So summed up bombsquad checks, sees ouya instead of ouya_1_1, and gets upset, and proceeds to commit suicide.
So to fix this, all you have to do is:
1. open up your file manager.
2. go to /system/build.prop
3. And change:
ro.product.device=ouya
To
ro.product.device=ouya_1_1
And that's it! Just restart and the changes will take effect.
Let it be NOTED:
If you install the ouya everywhere stuff, ouya framework will continue to crash, to fix this instead replace:
ro.pruduct.device=ouya
With
ro.product.device=mojo
This works, because in a recent update, the bombsquad developer added ouya everywhere compatibility by supporting the mad catz mojo.
However, it should be noted that, once you do so you won't be able to install apps from th ouya store, and it will keep on trying to update. Probably because the apks in the ouya zip are outdated. For now I can't do anything about it, I might try and get some updated zips at some point though. Just switch between when you need to access the store.
Big thanks to the developer of bombsquad, cm11, bootmenu, ouya, and everybody else. Your all awesome!
Has anyone heard of any known compatibilty problems with Swapper2 on the Core Prime or the S820L?
Mine is flashed with psilocelium's custom ROM (which works great, rooted by default, got 4.5 GB internal storage free). SuperSU, BusyBox and Terminal Emulater are installed and TE is configure to use BusyBox commands. SuperSU confirms the Swapper2 app has been granted root privileges but its GUI presents no settings menu to allow me configure it, only "On," "Off," and "Ads Off" buttons. If I click the "On" button, it errors out because it's looking for the file "/sdcard/swapfile.swp", which doesn't exist because I intend using the bespoke swap slice on the SD card that I already formatted in Linux Swap. But I can't change the configuration because I it doesn't display a settings menu.
I've also tried alternate copies of the Swapper2 APK file from multiple sources and they all do the same thing.
So I'm wondering if there's anyone with a Core Prime, and especially an S820L, with Swapper2 running on it. Or who knows why it doesn't work.
If swapper2 isnt working then try roesoft ramexpander