Related
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.
Hi,I checked the similar themed threads and there was no answer... anyway, I installed Codename Android 1.6 on top of my CDA 1.5.5 install and everything went smoothly, however Tiny Tower was missing and installing it from the Store shows the missed shared library error... any ideas on how to fix it?
Hi,
I've manually installed FW v.1.2.0 on my NSG. Rooting with Nook Manager went without any problems.
Now I'm trying to manually add gapps from glownooter 1.5.26 package. Since it is for older FW it causes hangs on loading screen.
While putting manually files from glownooter with adb, I've found that the root of the problems lies probably in framework.jar. It was patched to provide IMEI for registration purposes, but now it seems that new FW changed that file.
It would be great if it was possible to update authentication patch for fw v.1.2.0 following this thread:
http://forum.xda-developers.com/showthread.php?t=955847
Meanwhile I can boot fine, when the new framework.jar stays untouched. But then I can not go through android initial wizard - on the first screen I can not get through clicking on droid icon. If SetupWizard.apk is removed from nook system boots fine, but apps (apart from YouTube) does not start since device is not connected to google account.
I hope that with little help we would have gapps running on new fw.
zetet said:
Hi,
I've manually installed FW v.1.2.0 on my NSG. Rooting with Nook Manager went without any problems.
Now I'm trying to manually add gapps from glownooter 1.5.26 package. Since it is for older FW it causes hangs on loading screen.
While putting manually files from glownooter with adb, I've found that the root of the problems lies probably in framework.jar. It was patched to provide IMEI for registration purposes, but now it seems that new FW changed that file.
It would be great if it was possible to update authentication patch for fw v.1.2.0 following this thread:
http://forum.xda-developers.com/showthread.php?t=955847
Meanwhile I can boot fine, when the new framework.jar stays untouched. But then I can not go through android initial wizard - on the first screen I can not get through clicking on droid icon. If SetupWizard.apk is removed from nook system boots fine, but apps (apart from YouTube) does not start since device is not connected to google account.
I hope that with little help we would have gapps running on new fw.
Click to expand...
Click to collapse
Have you had any luck with this? having similar issues! When selecting 'My Channel' in Youtube, it gives a 'There was a problem authenticating' message.
Also used NookManager as all attempts at trying to root 1.2.0 with TouchNooter failed. It would never get past the 'your nook is starting up' page.
It came pre-installed with 1.2.0 but looks like I may have to downgrade to get the play store to work:
http://forum.xda-developers.com/showthread.php?t=2040040
Guantonio said:
Have you had any luck with this? having similar issues! When selecting 'My Channel' in Youtube, it gives a 'There was a problem authenticating' message.
Also used NookManager as all attempts at trying to root 1.2.0 with TouchNooter failed. It would never get past the 'your nook is starting up' page.
It came pre-installed with 1.2.0 but looks like I may have to downgrade to get the play store to work:
http://forum.xda-developers.com/showthread.php?t=2040040
Click to expand...
Click to collapse
Hi,
I managed to get through - at least partly. I mean I have working google apps, but market is not working. It seems that BnN changed their framework.jar and the already patched version from nooter is not working anymore - that is why after rooting with nooter Nook is not booting.
If getting working gmail etc. is enough I can give You detailed instructions to get it working - unfortunately it is not single step procedure.
zetet said:
Hi,
I managed to get through - at least partly. I mean I have working google apps, but market is not working. It seems that BnN changed their framework.jar and the already patched version from nooter is not working anymore - that is why after rooting with nooter Nook is not booting.
If getting working gmail etc. is enough I can give You detailed instructions to get it working - unfortunately it is not single step procedure.
Click to expand...
Click to collapse
I already have email working, it was mainly the Play store I was after, thanks anyway.
zetet said:
If getting working gmail etc. is enough I can give You detailed instructions to get it working - unfortunately it is not single step procedure.
Click to expand...
Click to collapse
Yes please, could you explain how to get gmail etc working?
I used k9 mail for my gmail account, I find it is more useful on the nook ereader.
Did you get google calendar working yet?
I created a diff from the glownooter's framework.jar (1.1.5) and the original. I then applied this diff to the 1.2.0 framework.jar. (This is without the debug information.) Although I have since deleted all the gapp stuff, it worked at one time.
This is my first post although I have been reading and researching off of xda for the last 6 weeks.
You have to know what you are doing. If you need help, let me know.
here is the patch I used:
I just posted an addon for NookManager to install Google Apps for firmware 1.2.0 and 1.2.1. The thread is http://forum.xda-developers.com/showthread.php?t=2086582 Hope you find it helpful.
BTW, I used an awk script to patch the smali instead of diff / patch. It's more resilient to changes in the firmware and the oddities of line numbers and baksmali labels. It should make creating a new patch for the next firmware simple. I also added a patch to services.jar to get the setup wizard working and eliminate the YouTube - GMail dance. I'm uploading all my work to github now and will link it from the above thread.
Howdy,
I really did search the forums, so I'm sorry if the answer is out there and I couldn't find it.
I'm running CM 10 from an SD card on my Nook Color. My Android version is now 4.1.2, with Cyanogen Mod Version of 10-20121220-NIGHTLY-encore (the latest nightly. I had one from 12-12 before that).
Prior to this I ran a version of CM7. Everything worked fine on the CM7, I just thought I should check out Jelly Bean.
Everything works fine on the new (Android 4.1.2) system EXCEPT netflix. I downloaded it from the Google Play store, and all it does is hang on the loading screen.
I'm competent to flash downloaded nightlies on my SD card, but not to build ROMs myself.
Any thoughts? Thanks so much!
RevTom said:
Howdy,
I really did search the forums, so I'm sorry if the answer is out there and I couldn't find it.
I'm running CM 10 from an SD card on my Nook Color. My Android version is now 4.1.2, with Cyanogen Mod Version of 10-20121220-NIGHTLY-encore (the latest nightly. I had one from 12-12 before that).
Prior to this I ran a version of CM7. Everything worked fine on the CM7, I just thought I should check out Jelly Bean.
Everything works fine on the new (Android 4.1.2) system EXCEPT netflix. I downloaded it from the Google Play store, and all it does is hang on the loading screen.
I'm competent to flash downloaded nightlies on my SD card, but not to build ROMs myself.
Any thoughts? Thanks so much!
Click to expand...
Click to collapse
The updated Netflix version in the Play store will not work. You need to install Netflix version 1.81. Search this forum and you will find the link to the apk. Or you can Google Netflix version 1.81 apk download. There is also a modified black screen version that will work.
Thanks so much. I found it and downloaded it.
What exactly do I DO with the apk? Put it in my boot sector and boot into recovery?
RevTom said:
Thanks so much. I found it and downloaded it.
What exactly do I DO with the apk? Put it in my boot sector and boot into recovery?
Click to expand...
Click to collapse
When you download the apk it should be in your download folder. Use the download manager (icon with green downward pointing arrow) to select the file. Box will pop up asking if you want to install. Select install. If you want to move Netflix to SD card go to system, apps, all, Netflix. You will see an option to move it to SD card.
Awesome! Got it, thanks so much! Consider this solved.
Hey all,
I've rooted my Nook stock before, and had it work just fine, but after awhile it became very unstable and slow. I recently re-rooted, using GMPOWER's method, everything seems to be working, except the Android Market.
I followed the steps for limited market visibility, but there's been no change. The Market won't update to Google Play, and when I access it, it doesn't show any apps - just a message stating, "No matching content in Android Market." I am able to search for some apps, but very few show up. (I've installed File Expert, and updated it just fine, but that's about it.)
For the life of me, I can't figure out what's wrong. My Gmail app works fine. But my Amazon Appstore .apk won't install either. It'll ask if I want to install using App Installer or Package Installer, but both give an error message. App Installer says, "Unable to install. This application was not able to install onto your device," as if my device were not rooted. Package Installer says, "Cannot parse the package." I tried downloading a newer version of the Google Play Store, and got the same errors.
I feel like I might be missing something obvious, but I can't figure it out. I'm tempted to revert back to 1.4.2 or earlier and re-root again, but that's a lot of work (mainly to download all my B&N content again).
Any thoughts or suggestions or mere stabs in the dark? Anyone?
Wipe Dalvik
h2j0NT20 said:
Hey all,
I've rooted my Nook stock before, and had it work just fine, but after awhile it became very unstable and slow. I recently re-rooted, using GMPOWER's method, everything seems to be working, except the Android Market.
I followed the steps for limited market visibility, but there's been no change. The Market won't update to Google Play, and when I access it, it doesn't show any apps - just a message stating, "No matching content in Android Market." I am able to search for some apps, but very few show up. (I've installed File Expert, and updated it just fine, but that's about it.)
For the life of me, I can't figure out what's wrong. My Gmail app works fine. But my Amazon Appstore .apk won't install either. It'll ask if I want to install using App Installer or Package Installer, but both give an error message. App Installer says, "Unable to install. This application was not able to install onto your device," as if my device were not rooted. Package Installer says, "Cannot parse the package." I tried downloading a newer version of the Google Play Store, and got the same errors.
I feel like I might be missing something obvious, but I can't figure it out. I'm tempted to revert back to 1.4.2 or earlier and re-root again, but that's a lot of work (mainly to download all my B&N content again).
Any thoughts or suggestions or mere stabs in the dark? Anyone?
Click to expand...
Click to collapse
Have you tried installing Rom Manager via sideloading and wiping the Dalvik cache? If that does not work try installing a custom ROM.