Database Users

(Q) Swype Beta

Does anyone have the exact method for installing Swype Beta on a stock based Rom (i.e. Iced Glacier)? I can't get it to install correctly at all.
Geoi1006 said:
But without further chit chat here's what I did:
Using Super Manager I:
1) Mounted the system as r/w.
2) Went into System» App» Deleted the swype.apk
3) went into System»lib» deleted the libswype file
4) Then followed normal install procedures as laid out in Swype Beta using the Swype Installer you receive when signing up for their beta.
It should be noted as with any system file you may or may not need later that its always smart to back up the stock Swype files for future restoring if needed.
[\QUOTE]
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse

yes, I currently running cyanogen I pulled the following from stock, or evil roms..
you ll need two files....
system/app/swype.apk
system/lib/libswypecore.so
Anytime I updated from cyanogen, I would still have swype but received the for close error, until I pulled the libswpecore
hope that helps
edit....think you want to download it from the swype site, enroll in the beta program and you should be good to go, may have to remove the above files to get the beta though

I got it figured out. I'm already enrolled in swype beta, thanks though. The question was how do I install swype beta on a stock based rom, Iced Glacier in this case, in which Swype is a system app(protected if you will). I got it figured out though. If anyone uses swype beta then they know that its much sexier than the stock Swype included lol. But without further chit chat here's what I did:
Using Super Manager I:
1) Mounted the system as r/w.
2) Went into System» App» Deleted the swype.apk
3) went into System»lib» deleted the libswype file
4) Then followed normal install procedures as laid out in Swype Beta using the Swype Installer you receive when signing up for their beta.
It should be noted as with any system file you may or may not need later that its always smart to back up the stock Swype files for future restoring if needed.
Sent from my HTC Glacier using XDA App

My lib was named libSwypeCore.so not libswype.so. Although that may be because I had / mounted rw but didn't actually delete the files first.
This was really terrifying. Swype is what makes the difference between me needing a phone with a keyboard or not. I find the poke&peck keyboards absolutely unusable.
But I was very envious of the mic button built into the keyboard because I've also found the voice recognition to be shockingly good. Historically I've found voice recognition software to be about 30% accurate and generally produced results one would expect from a slightly retarded monkey.
But I digress. These instructions worked perfectly and the new Swype is even cooler than the stock one.
Swype is an application I would pay a significant amount of money for. But free works too!

Glad to help man
Sent from my HTC Glacier using XDA Premium App

And I hate the white keyboard swype is skinned with from the stock apk.
Sent from my HTC Glacier using XDA Premium App

i did this on my stock rom, and swype basically deactivates itself after the phone is rebooted. swype keyboard will come up, and peck-typing works, but the swyping function is disabled. i've seen this before when playing with swype hacks. it means it's not licensed properly. i removed swype.apk and libswypecore.so manually before doing this.
is yalls swyping functions still working properly after a phone reboot?

I have to select the android keyboard then reselect the swype keyboard on every reboot. I find this is necessary on sense based roms mostly.
Sent from my glacier using XDA Premium App

So is there any way to get the beta version to properly recognize its license, so you don't have to manually switch away from, and then back to, the beta Swype keyboard after each reboot to get it to work correctly?

Like maybe there's some type of an auto-script that could be written to run on each boot that would select the stock keyboard and then re-select the Swype beta keyboard?

I thought swype comes preinstalled?
Sent from my HTC Glacier using XDA Premium App

The beta version has the microphone button on the keyboard, which is why I want to use that one instead of the pre-installed one...

Netflix stopped working today? ?

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.

[HOW TO] *New Instructions* Add Amazon VOD to Android Phone

*NEW INSTRUCTIONS*
Today I figured out how to get Amazon Video On Demand app on my phone and watch videos
I did this with a rooted phone, I am not sure if you phone needs to be rooted to accomplish this task. I have attached the required files to accomplish this task. These steps are assuming you have a rooted phone.
REQUIREMENTS:
Download attached APKs
Wireless connectivity
VooDoo OTA for rooted phones (https://market.android.com/details?id=org.projectvoodoo.otarootkeeper)
INSTRUCTIONS:
1. Copy downloaded APKs to your phone
2. Install each APK and make sure to click DONE after each installs
3. Enable phones Wireless and connect via WiFi
4. Go to your phone SETTINGS>ACCOUNT AND SYNC
5. Press ADD ACCOUNT
6. Press AMAZON and enter your Amazon Prime credentials
7. Start the VooDoo OTA app
8. Press TEMP.UN-ROOT and allow the program to temporarily unroot your phone
9. Reboot your phone
10. When the phone comes up, still be attached via wireless and try your app
I hope this works for everyone who tries, please report your findings
Currently this app only works on wireless it will not work with your cell signal. I am looking to see if I can figure out how to enable the app to use the cell signal, I'm not a developer but I do have an idea to try!

ill try this on my Amaze 4G when i get home

I did all of these on my CM7 mod and "Watch Now" is still grayed out for me.

MoToKrusheR said:
I did all of these on my CM7 mod and "Watch Now" is still grayed out for me.
Click to expand...
Click to collapse
The only think I can say is that make sure the device is un-rooted and reboot after using the VooDoo OTA
You're just about there!

do you guys think this would work with the bionic?

elephant007 said:
The only think I can say is that make sure the device is un-rooted and reboot after using the VooDoo OTA
You're just about there!
Click to expand...
Click to collapse
I've done the reset 3 times, still a no go. Going to keep looking into it though.

MoToKrusheR said:
I've done the reset 3 times, still a no go. Going to keep looking into it though.
Click to expand...
Click to collapse
Are you doing this on a phone or on your Fire?
I wonder if you can remove root from some alternative method and see if you can run VOD, perhaps remove BurritoRoot if that's what you have installed.

There is something about CM7 that amazon does not like. I have never gotten it to work on CM7, even after temp unrooting. But if I did the same thing on a none cm7 rom, it worked fine. Go figure.

elephant007 said:
Are you doing this on a phone or on your Fire?
I wonder if you can remove root from some alternative method and see if you can run VOD, perhaps remove BurritoRoot if that's what you have installed.
Click to expand...
Click to collapse
It's on a fire. Before I flashed CM7 over, I was running just a rooted fire, and voodo ran just fine allowing amazon video to work when needed. Would be a shame if I couldn't get it to run on CM7.. not a huge loss, just would like to see if it could work on this variant..

That's too bad that it doesn't work on CM7
Maybe I should try it and see what I can find out

will try and post quick feed back

for those of you having problems running this one CW7, according to this link here http://forum.xda-developers.com/showthread.php?t=1390773 I'm guessing it's the MAC Address issue
Just a guess

elephant007 said:
for those of you having problems running this one CW7, according to this link here http://forum.xda-developers.com/showthread.php?t=1390773 I'm guessing it's the MAC Address issue
Just a guess
Click to expand...
Click to collapse
Wonder if an update.zip could be made for the CM7 variant in this thread?

MoToKrusheR said:
Wonder if an update.zip could be made for the CM7 variant in this thread?
Click to expand...
Click to collapse
EDIT - I flashed the updated/MAC address fix - No wipe ROM, but still a no go... Might have to do a full wipe/install?
This is the ROM: http://www.mediafire.com/?hmdc0lmgvnlbg97
Located in this thread - http://forum.xda-developers.com/showthread.php?t=1390773&highlight=mac
"If you're upgrading from an EXISTING CM7 install then use this ROM instead. This one will NOT wipe the cache and data partitions which should mean that you can upgrade from one version of CM7 to another without losing any of your existing date (or that's at least the idea)"

I tried this on my CM7 Kindle Didn't Work
I copied the apk's and ran the installs. It won't let me login to Amazon even. I just grabbed the apk's from the Kindle Fire .bin file though. I'll try the ones you have for download in your post and see if they work differently.

Hmm, MAC wasn't the problem
I'm on ICS and when I try to add an Amazon account I get a failure. I've checked my MAC and it's the same as under stock, but what does concern me is my serial number is all 0's.
Has anyone got this to work under ICS? Is everyone's serial number all 0's? Any other hints on how to get VOD working?

its working fine on my amaze 4g!

thedarksavant said:
I'm on ICS and when I try to add an Amazon account I get a failure. I've checked my MAC and it's the same as under stock, but what does concern me is my serial number is all 0's.
Has anyone got this to work under ICS? Is everyone's serial number all 0's? Any other hints on how to get VOD working?
Click to expand...
Click to collapse
Did you try logging into Amazon via WiFi?

"Parse error. There is a problem parsing the package" when install MyAccount-unsigned.apk. Any ideas?

Emerald214 said:
"Parse error. There is a problem parsing the package" when install MyAccount-unsigned.apk. Any ideas?
Click to expand...
Click to collapse
Redownload and try again, sounds like maybe it didn't download or get copied to your phone correctly

How To Bypass the Auto-Update (Tested on Nook HD+)

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.

Netflix: Menu Loads Fine to Black Screen Permanent

Hi guys. Anybody having trouble running Netflix on a rooted Nook Color. Pretty sure I'm still running CM7.2. The menus load without problem, then you select a show and it's a total blank screen. Thanks for any help.

What version of Netflix are you using? I've heard you can use the latest one with CM7, but I have always used version 1.8.1. If you Google it, you should be able to find the app file.
Sent from my SGH-T999 using xda premium

Yeah, from everything I've seen 1.8.1 is supposed to be the best option. I need to get the same for my CM10 installed Nook.
http://forum.xda-developers.com/showthread.php?t=1749707
Just downloaded the .apk from the dropbox link. A couple of the others seem to not work. Haven't put it on the Nook yet (needs to charge).