Related
Let me start by saying thank you to all the devs for making rooting the Nook Color (NC) possible.
I'm having a couple of issues after MN rooting and installing the 1.1 Ghtz OC kernel. I'm a systems engineer with experience rooting other droid devices including my HTC Incredible.
1. non-market Apps not loading on NC. I use dropbox to move apps to my NC. some apps didn't have any issue loading. Such as Nook Home and Live Wallpapers but others just don't do anything;i.e. prompts to install but install app doesn't open.
a. SetCPU_2.13-donate.apk : want to use for the OC kernel
b. Quickoffice Pro v4.1.2.apk : payed app pulled from my HTC Incredible.
2. XDA App does not save my login information. this is just an inconvenience.
Thanks in advance for everyones help.
eejimen said:
1. non-market Apps not loading on NC. I use dropbox to move apps to my NC. some apps didn't have any issue loading. Such as Nook Home and Live Wallpapers but others just don't do anything;i.e. prompts to install but install app doesn't open.
a. SetCPU_2.13-donate.apk : want to use for the OC kernel
b. Quickoffice Pro v4.1.2.apk : payed app pulled from my HTC Incredible.
2. XDA App does not save my login information. this is just an inconvenience.
Thanks in advance for everyones help.
Click to expand...
Click to collapse
1a. I don't believe SetCPU is compatible unless you are using the new 2.6.32 kernel...
1b. I run Quickoffice fine on my nook...here is the APK I installed, give it a shot...
2. The free XDA app didn't save my login info either. Then I upgraded to the paid version and that works GREAT!
My $0.02
How new is your Nook? It might be related to the partition sizes B&N is loading the NC with.
http://forum.xda-developers.com/showthread.php?t=1077973
I apologize in advance, I'm not posting any solutions =( just to share my experience on my rooted 1.2 with Manual Nooter and OC 1.1 mhz kernel. It runs awesome in general, B&N interface runs smoothly and fast now, no creashes, apps I've been able to install run great. Quadrant score is 1680 . Issues so far:
1. Market is obsolete, even with Market Fix I cant see all apps I can see boot from my Phiremod sd.
2. I did find SetCPU , runs without issues, OC is fine/
3. Asphalt 5 doesnt run full screen even with Spare Parts compatability mode disabled (or enabled).
4. Air Attack HD doesnt install correctly. Runs fine from Phiremod sd.
5. Quick Office doesnt install correctly. Strange thing is that I thought it was part of the B&N package. I do see the apk but app doesnt open or install.
bekyndnunwind said:
1a. I don't believe SetCPU is compatible unless you are using the new 2.6.32 kernel...
1b. I run Quickoffice fine on my nook...here is the APK I installed, give it a shot...
2. The free XDA app didn't save my login info either. Then I upgraded to the paid version and that works GREAT!
My $0.02
Click to expand...
Click to collapse
bekyndnunwind: Thanks for your responses.
1a. I am using sugwacee's recompiled OC kernel 2.6.32.9.
1b. Thanks. Now I'm at least getting a message when trying to install, something about "archive" then "unarchive". Did you have to uninstall the Quickoffice viewer? If so, how?
2. Thanks for that info. Just curious why on my Dinc it saves the user profile and password.
imdickie: Thanks for the info. I'm going to check out the link.
imdickie said:
How new is your Nook? It might be related to the partition sizes B&N is loading the NC with.
http://forum.xda-developers.com/showthread.php?t=1077973
Click to expand...
Click to collapse
My Nook is showing 5GB of EMMC storage.
Garoto1973 said:
2. I did find SetCPU , runs without issues, OC is fine/
Click to expand...
Click to collapse
Can you share the SetCPU APK you used to install on your nook.
Worked fine last night.
Still works on incredible.
It says I need new version
but it's not in market?
I have HTC Vision in build.prop
anyone know how to fix it?
Sent from my ADR6300 using XDA Premium App
I also used the htc vision fix.
I had the exact same problem last night. I opened netflix & couldn't use it, just got a message saying there was an update for the netflix app and I could not use the app till I downloaded the update. Clicking on the Ok button took me immediately to the update on the market, the screen where you can click to download the app.
Then the updated version of the app wouldn't work. Just an error message saying something like there is a problem with my netflix account, or my device has been deactivated at netflix.com.
I got it working again but had to try lots of things. I deleted the updated app, and tried restoring the older version from titanium backup, but got the same message about needing to install the update,& updated app gave same error message. Cruising around netflix.com website wasn't useful, my device (nc) hadn't been ' deactivated' as far as I could tell.
Side loading the netflix app didn't work. After I reloaded the old app ( titanium) a few times, & updated & rebooted a few times, i started getting stuff to play sound, but no picture. Then I discovered it will work perfectly after a reboot, but only for the very first thing you pick! After that it's just sound again, & i have to reboot again to watch something else!
Anybody else having a netflix issue?
[Solved] Netflix weirdness
It appears there is a new client version. 1.2.1 build 843839-1.2.0-30
I copied the apk from my Incredible (one of the supported phones),
and used Titanium Backup to uninstall, and Root Explorer to install
new apk. The new file is a little bigger, I guess it adds new supported
phones. The apk has the same file name but is a different file.
That fixed it for me.
I attached the apk (taken from my Incredible).
Interesting.....
I had the modified .apk which didn't need a prop.build change.
Of course, it died last night like the above threads state.
Wouldn't let me update it either as everytime I tried to install, it would error out...
But, I went an uninstalled the program (first deleteing cache) then found the program in the market and it installed with no problem....
It runs fine... no chipmunks.... nada....
Lucky I guess.... Running CM7 off the emmc on an overclock of 1200.
Lego
Legobricke said:
Interesting.....
I had the modified .apk which didn't need a prop.build change.
Of course, it died last night like the above threads state.
Wouldn't let me update it either as everytime I tried to install, it would error out...
But, I went an uninstalled the program (first deleteing cache) then found the program in the market and it installed with no problem....
It runs fine... no chipmunks.... nada....
Lucky I guess.... Running CM7 off the emmc on an overclock of 1200.
Lego
Click to expand...
Click to collapse
Woops, hit the thanks by accident I was trying to quote your post. So you didn't modify your build.prop and the updated client works without chipmunk voices? I'm running .32 CM7 after a restore to stock (was having issue with a later nightly) and when I downloaded the updated Netflix app it still gave me chipmunk voices until I edited build.prop again.
Are you running 7.0.x stable or one of the newer (.32) nightlies?
I am using CM7.0.3 - encore stable.
I also am using the ext4-CM7-dalingrin-OC-emmc-042411 overclock set to 1200.
These are running from the internal. Not an SD card.
I have had zero issues with netflix.
The stable (and the .29 kernel nightlies) have no problems running Netflix now that device check has been disabled.
It's only the .32 installs (later nightlies and beta1) that have the chipmunk voice regardless of what Netflix client is used (and thus needs the build.prop mod)
Just to add to the conversation. The Netflix Market Update worked perfectly fine for me.
Nook 1.2.1, rooted.
fuzzynco said:
It appears there is a new client version. 1.2.1 build 843839-1.2.0-30
I copied the apk from my Incredible (one of the supported phones),
and used Titanium Backup to uninstall, and Root Explorer to install
new apk. The new file is a little bigger, I guess it adds new supported
phones. The apk has the same file name but is a different file.
That fixed it for me.
I attached the apk (taken from my Incredible).
Click to expand...
Click to collapse
Also running SD card Nookie Froyo 0.6.8, but I'm still getting the chipmunk effect with this APK :/
Worked for me on 2 versions of NF.
I did have to do the build.prop fix though.
I used HTC Vision.
This worked perfectly... Thanks so much!!!
fuzzynco said:
It appears there is a new client version. 1.2.1 build 843839-1.2.0-30
I copied the apk from my Incredible (one of the supported phones),
and used Titanium Backup to uninstall, and Root Explorer to install
new apk. The new file is a little bigger, I guess it adds new supported
phones. The apk has the same file name but is a different file.
That fixed it for me.
I attached the apk (taken from my Incredible).
Click to expand...
Click to collapse
Thanks that worked for me.
I just updated to CM7 Nightly #93 via ROM Manager yesterday.
The only thing I had to do was update build.prop with the HTC Vision information to get it working again.
Rocking...
Edit: Just updated to #94 via ROM Manager, updated build.prop again, rebooted, and still working.
NOTE: I updated to most current version of CWM using ROM manager prior to CM7 update as well...
running rooted 1.2 with dalingrin's OC kernel --> was able to install and run netflix from market but had the chipmunk / fast forward feature... changed my build.prop with the HTC/Vision mod and all works great.
FYI, I was able to copy the latest apk from my Nexus One to the Nook Color, and Netflix is working again.
Can't get Netflix to work after update
I am at a total loss what to do. I updated my netflix app like it asked me to but now it lets me put my login info in (all red screen) and then I hang where it is a white screen with Netflix in a red bar at the top of my nook color. It never goes any farther than that and it used to work for me great before the update and I am doing the Vision HTC build prop thing and I have tried clearing data. Any thoughts. Thanks
bhaycraft said:
I am at a total loss what to do. I updated my netflix app like it asked me to but now it lets me put my login info in (all red screen) and then I hang where it is a white screen with Netflix in a red bar at the top of my nook color. It never goes any farther than that and it used to work for me great before the update and I am doing the Vision HTC build prop thing and I have tried clearing data. Any thoughts. Thanks
Click to expand...
Click to collapse
Exact same thing just happened to me. But I actually got it to work after the update. Then today it suddenly started giving me the white screen with Netflix at the top. Arggg.
Ditto for me on my ManualRooted Nook; however, Netflix still works from my SD-based CM7. What are you guys running on?
What I am running
I am running on Manual nootered latest 4.5.25 and I am running the OC kernel from Dalingrin.
I have exactly the same problem. Running the same combo.
So far I've uninstalled, and re-installed, cleared dalvik cache, but nothing has made a difference.
Working one day, then broken.
Hello,
Ive searched and searched but can not find a definite answer, I have Phiremod 7.1 up and running. I am curious if you can run the original B&N Home launcher, with the library and shop, is this possible or am I shooting blanks? I cant seem to access my books already on my NC's main Memory.
Thank you!
Short answer: nope.
I believe you can just install the B&N app and sync with the account you had previously (I don't really use mine for books). Doesn't the stock ROM store books internally? In which case would have been wiped out when installing Phiremod?
yes I do believe the books are wiped from installing the rom, but i was curious to see if i could get the B&N App and Launcher, and reload the books.
App from the market yes (but not same as stock), launcher no.
Sent from my HTC Vision using XDA App
Just to let everyone know you can now go to Swype.com, sign up for the beta with your KF and get your fully functioning and official Swype hot off the press!
Sent from my Kindle Fire using xda premium
Mine is rooted and running and ICS (cm9) rom but after I log into the installer, it says that the screen size is not supported. Think you might know why?
okyere said:
Mine is rooted and running and ICS (cm9) rom but after I log into the installer, it says that the screen size is not supported. Think you might know why?
Click to expand...
Click to collapse
From the MIUI Forums
[FIX] Getting more market apps to show up
If you have an Android phone, you might have noticed that some of the apps and games that you are able to download onto your phone do not show up on your Kindle Fire. There could be several reasons that this happens, but one of the main reasons I have seen is because of the density of the Fire's LCD display. Although it is a large display it is considered a medium density display because of how many pixels fit into a square inch.
Any easy fix would be to edit /system/build.prop and change ro.sf.lcd_density=160 to ro.sf.lcd_density=240. Sure this works but you will be left with items on screen being enlarged quite a bit. Icons will be much larger and you will not be able to fit as many on each homescreen. There is one other thing you can do to help this situation.
1. Change ro.sf.lcd_density=160 to ro.sf.lcd_density=240 in /system/build.prop (you will need to mount /system as RW using adb or something like ES Explorer or Root Explorer)
2. Create a file named local.prop in /data and add qemu.sf.lcd_density=160
3. Reboot and enjoy having more apps and games available in the Android Market
So why does this work? Well the Android Market will get your density from ro.sf.lcd_density and see it as a high density display. qemu.sf.lcd_density will override this for the drawable objects in apps and will use the medium density setting for displaying these items. So you end up getting the best of both worlds.
Enjoy!
Click to expand...
Click to collapse
This also fixes FCs that you might get! You could also get "LCD Resolution (Root)" but you'll have to manually set it back to its original resolution.
I don't think screen density is the answer. Mine is set to 160 and I have no problems getting my apps to show up in the Market.
Sent from my Kindle Fire using xda premium
okyere said:
Mine is rooted and running and ICS (cm9) rom but after I log into the installer, it says that the screen size is not supported. Think you might know why?
Click to expand...
Click to collapse
What color is the Swype "S" on your installer icon? If it is anything other than Orange, then you're not installing the version compatible with your Fire.
Since I also use Swype on my Thunderbolt, I signed up for another beta with another email address I have, and that let me download the latest beta on my Kindle. I tried this 2 weeks ago and got an error that Swype was not compatible with my device. I saw that they have Swype now for the Galaxy Tab and that was my cute to try again. I did and magic happened.
If you have the orange S and are not able to do the install, make sure you don't have any other versions of the installer on your KF and try again. You might also try downloading again just in case the download was bad.
Good luck!
Sent from my Kindle Fire using xda premium
I am stuck once I get to the swype installer. I click the "enable swype" button, which according the swype installation page is supposed to take me to the keyboard recognition page, which technically it does, but doesn't allow me to choose a new keyboard.
My fire is stock with the most recent update (6.2.2?). Does it need to be rooted or running another rom for this to work?
dougdirt24 said:
I am stuck once I get to the swype installer. I click the "enable swype" button, which according the swype installation page is supposed to take me to the keyboard recognition page, which technically it does, but doesn't allow me to choose a new keyboard.
My fire is stock with the most recent update (6.2.2?). Does it need to be rooted or running another rom for this to work?
Click to expand...
Click to collapse
I was just going to ask you if you were running the stock ROM. That is the problem. You can still do it though. I had Swype when I ran stock ROM.
I'm working right now and can't refer to the instructions I found, but Google it and read the threads completely. You can do it, but it involves moving the Swype apk to your system apps folder, changing permissions and then deleting the apk to keep Swype from force closing. It's a hassle, but worth it if you don't want to install a recovery and flash CM7 or other ROM.
Sent from my Kindle Fire using xda premium
Is there a version just for the kindle or is it the same download that you use for your phone? Does it work with the stock firmware?
SirVilhelm said:
Is there a version just for the kindle or is it the same download that you use for your phone? Does it work with the stock firmware?
Click to expand...
Click to collapse
It does not appear to be resizeable, so I assume it's the phone version, but Swype apparently approves of it for this device, and it does work perfectly with the KF. It is a large size though, but I don't mind because my fingers are big.
Sent from my Kindle Fire using xda premium
I'm running Swype on my KF stock, I followed these instructions to install it.
h t t p : / / androidforums.com/amazon-kindle-fire/473807-how-successfully-install-swype-root-required.html
(Sorry for bizarre link formatting. I'm new here and apparently now allowed to post outside links.)
Still no luck; even with a new swype account.
djkeller3 said:
What color is the Swype "S" on your installer icon? If it is anything other than Orange, then you're not installing the version compatible with your Fire.
Since I also use Swype on my Thunderbolt, I signed up for another beta with another email address I have, and that let me download the latest beta on my Kindle. I tried this 2 weeks ago and got an error that Swype was not compatible with my device. I saw that they have Swype now for the Galaxy Tab and that was my cute to try again. I did and magic happened.
If you have the orange S and are not able to do the install, make sure you don't have any other versions of the installer on your KF and try again. You might also try downloading again just in case the download was bad.
Good luck!
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Ok. So I even went ahead to create a new swype beta account just to use for my kindle fire. But after the installation, it still tells me the screen size is not yet supported. Yes, the color of the installer is orange. And since I just created the account, I'm sure I have the latest installer. Could it be due to the fact that I'm running the ics (cm9) rom? What rom do you have on your KF?
okyere said:
Ok. So I even went ahead to create a new swype beta account just to use for my kindle fire. But after the installation, it still tells me the screen size is not yet supported. Yes, the color of the installer is orange. And since I just created the account, I'm sure I have the latest installer. Could it be due to the fact that I'm running the ics (cm9) rom? What rom do you have on your KF?
Click to expand...
Click to collapse
I'm thinking the ROM is the issue. I couldn't install on CM9 but do have it working on CM7
Hmm I have it workin just fine. Does any1 kno if there a version just for tablets that we can steal, lol. (APK) I would prefer the resizable is all.
NPC_Izzy said:
From the MIUI Forums
This also fixes FCs that you might get! You could also get "LCD Resolution (Root)" but you'll have to manually set it back to its original resolution.
Click to expand...
Click to collapse
I tried the screen density fix and am still receiving the "screen size not supported" error after a reboot.
I too am rooted and running the latest CM9. Any other potential resolutions?
Still no luck with official update (2/16) for swype for cm9 ics on the Kindle Fire
djkeller3 said:
What color is the Swype "S" on your installer icon? If it is anything other than Orange, then you're not installing the version compatible with your Fire.
Since I also use Swype on my Thunderbolt, I signed up for another beta with another email address I have, and that let me download the latest beta on my Kindle. I tried this 2 weeks ago and got an error that Swype was not compatible with my device. I saw that they have Swype now for the Galaxy Tab and that was my cute to try again. I did and magic happened.
If you have the orange S and are not able to do the install, make sure you don't have any other versions of the installer on your KF and try again. You might also try downloading again just in case the download was bad.
Good luck!
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
So swype has a new update today (2/16) that is supposed to support ICS tablets officially. I tried my luck by downloading a new installer and tried to install in on my rooted KF running the cm9 ICS rom. No luck. Still gives me the 'not supported screen' error message. Are there any hacks that can get our lovely swype to work on the KF for ICS yet? I'm getting tired of the stock keyboard.
gT7kr93I said:
I'm running Swype on my KF stock, I followed these instructions to install it.
h t t p : / / androidforums.com/amazon-kindle-fire/473807-how-successfully-install-swype-root-required.html
(Sorry for bizarre link formatting. I'm new here and apparently now allowed to post outside links.)
Click to expand...
Click to collapse
I did this as well, and it had been working great. Now I received notification of a Swype update. Has anyone installed the update?
Sent from my Kindle Fire using xda premium
I may do a TRWP backup and then do the update.
Sent from my Kindle Fire using xda premium
okyere said:
So swype has a new update today (2/16) that is supposed to support ICS tablets officially. I tried my luck by downloading a new installer and tried to install in on my rooted KF running the cm9 ICS rom. No luck. Still gives me the 'not supported screen' error message. Are there any hacks that can get our lovely swype to work on the KF for ICS yet? I'm getting tired of the stock keyboard.
Click to expand...
Click to collapse
I'm running CM7 and had no problem downloading and installing the latest Swype update. Honestly, not being able to use my Swype on CM9 will keep me on CM7 indefinitely.
Sent from my Kindle Fire using xda premium
I extracted the Swype apk from my backup of CM7 so I could use it on my CM9 install. It works just fine but the keyboard is more narrow than the screen even in the vertical orientation and it occasionally nags about the version being incorrect for the screen size when going from vertical to horizonal.
Instead of using your backup to install, just run your installer and download a fresh install of the beta. As long as you have your user name and password, Swype will let you download it again. Then you have a fresh install without any settings that may exist in the backup.
One annoying feature of new Nook HD+ (and assuming Nook HD) is that during initial set up it will look for and force you to update (if one is found). There is a neat and really easy trick to bypass this process.
Once you get to that step in the process, during the process hold down the power button and force it to shut off by selecting "OK" in the prompt. You have to do it before it finishes downloading the update.
Once you power it back on you'll have to restart the whole process of entering your WiFi and information again. When you get to the point where the device looks for an update, it will look for a few seconds and determine that its got the latest version installed and proceed to the next phase.
To make sure you did it correctly just go into "Settings" and check the version. For me my default was 2.0.4, for you it may be different, but either way its not 2.0.5.
I've tested it multiple times and always with great success.
What about 2.0.4 do you prefer over 2.0.5?
Also, let us know if this actually stays on 2.0.4. Those of us who had already registered Nooks (both HD and HD+) when 2.0.5 came out got updated in spite of having turned off auto updates.
lkmiller said:
What about 2.0.4 do you prefer over 2.0.5?
Also, let us know if this actually stays on 2.0.4. Those of us who had already registered Nooks (both HD and HD+) when 2.0.5 came out got updated in spite of having turned off auto updates.
Click to expand...
Click to collapse
It was for rooting purposes, since at the time I couldn't find a rooting tool for 2.0.5, that's why. Also I too had registered once under 2.0.5, and when starting fresh found that this method does work regardless of what you initially registered under. Though it only buys you little time to do whatever modifications you need to to your device before it automatically updates you (you could also leave WiFi turned off too).
dcoke said:
It was for rooting purposes, since at the time I couldn't find a rooting tool for 2.0.5, that's why. Also I too had registered once under 2.0.5, and when starting fresh found that this method does work regardless of what you initially registered under. Though it only buys you little time to do whatever modifications you need to to your device before it automatically updates you (you could also leave WiFi turned off too).
Click to expand...
Click to collapse
What device are you running? Still would like your factory zip.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
dcoke said:
It was for rooting purposes, since at the time I couldn't find a rooting tool for 2.0.5, that's why. Also I too had registered once under 2.0.5, and when starting fresh found that this method does work regardless of what you initially registered under. Though it only buys you little time to do whatever modifications you need to to your device before it automatically updates you (you could also leave WiFi turned off too).
Click to expand...
Click to collapse
Ok, I thought that might be why. Thankfully we can root 2.0.5 now. But it's good to know this method of postponing that initial update if I ever need to reset and start over.
nook hd+ auto-updated after leapinlar root+cwm fixes
My Nook HD+ notified me last night that it had auto-updated to 2.0.6 but I was able to get back my original Nova Prime Launcher and the Google Play store continues to work (it broke Beautiful Widgets, but uninstalling it and reinstalling it fixed that)
I had originally rooted it from 2.0.5 using the Universal Root method here: http://forum.xda-developers.com/showthread.php?t=2062613
I had the following images installed:
NookHD-HDplus-Gapps+Extras-for-stock-rev1.zip
NookHD-HDplus-Universal-Root-rev1.zip
NookHD-HDplus-LocationServices.zip
Using CWM for here:
NookHDplus-bootable-CWM-6023-for-emmc-stock-4GB-rev1.zip
Note - I did not manually update or in anyway 'induce' the update, it just happened. Did I miss something in the instructions to prevent auto-update?
Atleast the play store and Nova Launcher keeps working (not had time to check if root is still working though) But I did notice that the B&N Home launcher keeps showing up more often than before (hitting apps and going back brings back Nova)
Thanks
vtmanryn said:
My Nook HD+ notified me last night that it had auto-updated to 2.0.6 but I was able to get back my original Nova Prime Launcher and the Google Play store continues to work (it broke Beautiful Widgets, but uninstalling it and reinstalling it fixed that)
I had originally rooted it from 2.0.5 using the Universal Root method here: http://forum.xda-developers.com/showthread.php?t=2062613
I had the following images installed:
NookHD-HDplus-Gapps+Extras-for-stock-rev1.zip
NookHD-HDplus-Universal-Root-rev1.zip
NookHD-HDplus-LocationServices.zip
Using CWM for here:
NookHDplus-bootable-CWM-6023-for-emmc-stock-4GB-rev1.zip
Note - I did not manually update or in anyway 'induce' the update, it just happened. Did I miss something in the instructions to prevent auto-update?
Atleast the play store and Nova Launcher keeps working (not had time to check if root is still working though) But I did notice that the B&N Home launcher keeps showing up more often than before (hitting apps and going back brings back Nova)
Thanks
Click to expand...
Click to collapse
We have known for a while that setting the OTA to manual does not seem to stop auto updates anymore. The good news is that it still accepts the root. Just flash universal root again.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
I might have found a way how to disable Nook HD OTA autoupdate feature.
For some reason setting com.bn.device.fota.mode to manual does not work, so there is more straight approach to solve this.
So far i have found two:
1) Once you have rooted your device it is just a matter of editing /etc/hosts file and adding couple of lines
127.0.0.1 nook.com
127.0.0.1 barnesandnoble.com
127.0.0.1 su.barnesandnoble.com
which effectively blocks access to autoupdates, but when you reboot your device, all your data will be erased (nook will restore itself to factory state). So some way around is needed.
2) There is an app on google store called "Android Firewall", install it. Once installed block Wifi for NookConnectivityService. GAPPS and browser will not be affected, you'll get norification "Wifi error". But otherwise wifi is fuctional.
2) There is an app on google store called "Android Firewall", install it. Once installed block Wifi for NookConnectivityService. GAPPS and browser will not be affected, you'll get norification "Wifi error". But otherwise wifi is fuctional.
Click to expand...
Click to collapse
Blocking NookConnectivityService kills connectivity to the Google Play.
greenya said:
1) Once you have rooted your device it is just a matter of editing /etc/hosts file and adding couple of lines
127.0.0.1 nook.com
127.0.0.1 barnesandnoble.com
127.0.0.1 su.barnesandnoble.com
which effectively blocks access to autoupdates, but when you reboot your device, all your data will be erased (nook will restore itself to factory state). So some way around is needed.
Click to expand...
Click to collapse
You can symlink the hosts file. See my HD/HD+ tips thread linked in my signature. Look at item 15. Of course there are othe ways to prevent the update, like symlinking build.prop and doing the white on white repair. But those just cause the update to fail, while this may prevent them even checking. If this works, I may update my CWM zip to include it.
EDIT: After researching this a little I have found an easy way to accomplish this. That is to use AdAway. You can safely use that program if you configure it to put the hosts file on /data. It automatically symlinks it for you. But you need to be rooted to use this app. And it has a feature where you can add your own sites to block. Just add those sites listed in the post above. Then every time AdAway updates its own list, it adds your list to it also. This will block B&N from using those sites to download their updates. But realize that it also blocks you from browsing their site.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
leapinlar said:
EDIT: After researching this a little I have found an easy way to accomplish this. That is to use AdAway. You can safely use that program if you configure it to put the hosts file on /data. It automatically symlinks it for you. But you need to be rooted to use this app. And it has a feature where you can add your own sites to block. Just add those sites listed in the post above. Then every time AdAway updates its own list, it adds your list to it also. This will block B&N from using those sites to download their updates. But realize that it also blocks you from browsing their site.
Click to expand...
Click to collapse
Nice! It works then Including it to CWM zip is a good idea, with a warning, that you get to loose one site. That rooting thing imho is the whole reason for not using it, but substituting with google play.
BTW Is your hybrid cm10.1 stable on nook hd+ ?
greenya said:
Nice! It works then Including it to CWM zip is a good idea, with a warning, that you get to loose one site. That rooting thing imho is the whole reason for not using it, but substituting with google play.
BTW Is your hybrid cm10.1 stable on nook hd+ ?
Click to expand...
Click to collapse
WARNING! Hybrid not for HD+ !!!
greenya said:
BTW Is your hybrid cm10.1 stable on nook hd+ ?
Click to expand...
Click to collapse
My Hybrid setup on the HD+ is experimental and a hacked version by me. And I am running verygreen's 1-07 version of CM10.1. The Hybrid works great and is very stable, but the CM10.1 is buggy.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
leapinlar said:
My Hybrid setup on the HD+ is experimental and a hacked version by me. And I am running verygreen's 1-07 version of CM10.1. The Hybrid works great and is very stable, but the CM10.1 is buggy.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
Seems i missed somewhere something
datas0ft said:
Seems i missed somewhere something
Click to expand...
Click to collapse
You did not miss it. I just got it working this weekend and this is the first I have told anyone. I am going to test it a while before I even consider making it for anyone else. It does work but I had to manually configure some things. And it only works on CM10.1, not CM10. Until we get some better CM10.1's it does not really matter anyway.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
leapinlar said:
You did not miss it. I just got it working this weekend and this is the first I have told anyone. I am going to test it a while before I even consider making it for anyone else. It does work but I had to manually configure some things. And it only works on CM10.1, not CM10. Until we get some better CM10.1's it does not really matter anyway.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
This news change many things. But seems verygreen is so busy last time or found something new interesting.
Anyway. If you need some "hard testing" (when testing may make item dead) then ask me. I have one item with no warranty and ... you know, its not mine ... and its not last one.
greenya said:
I might have found a way how to disable Nook HD OTA autoupdate feature.
For some reason setting com.bn.device.fota.mode to manual does not work, so there is more straight approach to solve this.
So far i have found two:
1) Once you have rooted your device it is just a matter of editing /etc/hosts file and adding couple of lines
127.0.0.1 nook.com
127.0.0.1 barnesandnoble.com
127.0.0.1 su.barnesandnoble.com
which effectively blocks access to autoupdates, but when you reboot your device, all your data will be erased (nook will restore itself to factory state). So some way around is needed.
2) There is an app on google store called "Android Firewall", install it. Once installed block Wifi for NookConnectivityService. GAPPS and browser will not be affected, you'll get norification "Wifi error". But otherwise wifi is fuctional.
Click to expand...
Click to collapse
Thank you for this. It works. I added the manual way to do it via AdAway to my HD/HD+ Tips thread and added a CWM zip to my HD/HD+ CWM thread to automatically do it for you if you are not rooted. Both threads are linked in my signature.
Sent from my Nook HD+ running rooted stock
leapinlar said:
Thank you for this. It works. I added the manual way to do it via AdAway to my HD/HD+ Tips thread and added a CWM zip to my HD/HD+ CWM thread to automatically do it for you if you are not rooted. Both threads are linked in my signature.
Sent from my Nook HD+ running rooted stock
Click to expand...
Click to collapse
Could you also just freeze the NookConnectivityService app using Titanium Backup - seems to work for me
docfreed said:
Could you also just freeze the NookConnectivityService app using Titanium Backup - seems to work for me
Click to expand...
Click to collapse
Someone earlier says doing that blocked his Google Play. Is yours working ok?
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Someone earlier says doing that blocked his Google Play. Is yours working ok?
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
If you mean the Play Store, yes no problem - I don't use any other Play apps (like music, books, etc.). I am on 2.06, rooted, ADW EX Launcher and see no issues whatsoever with WiFi (as a matter of fact, no issue signing in to BN.com and downloading one of my books.