Related
I haven't seen this particular problem discussed yet, so here goes. Prior to the B&N 1.2 update, I was running B&N 1.1 with the AutoNooter. I had no particular problem using the Market. After cleaning everything back to stock B&N 1.1, I updated to 1.2 and rooted with MN 4.5.6. After doing the Market visibility fix, the downloads shown in the Market did not include any of my freeware downloads, but did include all but one of my paid downloads. In any event, I was able to recover everything but the one paid download, something called Ibird Pro. Some things (News and Weather) did not work as they had before, but most were fine. When I try searching for Ibird Pro (or Ibird Lite for that matter), the Market would not return the program. When I visit the Android Market on my PC, "My Account" shows the program, but won't let me download it because it insists that "This item is not compatible with your device." The Market Help advice is that the app is incompatible either with my screen size or Android version. Well, it was compatible before the B&N update and MN 4.5.6, and Android is now supposed to be 2.2. It seems like this is an issue of the NOOKColor reporting the wrong OS or wrong hardware info to the Market. Any help would be appreciated. (I have tried MN 4.5.18 and .25, after wiping back to a clean B&N 1.2, but they give me flakier results with the Market than 4.5.6.). If this has been discussed, can somebody point me to the thread. Thanks.
Sorry if this seems a silly question, but you don't mention what fixes you have tried other than the market fix in the MN OP. Have you tried any of the other fixes mentioned in the thread itself?
I had a few missing apps, not the amount you seem to be reporting, but others had more and reported that clearing market data and cache, then renaming vending.apk to somethinbg like vending.apk.OLD, reboot, rename back to vending.apk, reboot again, worked to fix the visibility. Worked for me too and no problems since. This was for MN 4.5.25, and can be found somewhere around pg 96 of the MN thread in the dev subforum.
As for the incompatible app message, there are a couple fixes depending. Some have had to go into nook color tools and uncheck 'allow non-market apps', reboot, recheck it, reboot,and it should be fine. This seems to work even for some apps you get from the market but don' t install with the same message you received.
Using a different app to install also works for many. I had to use color tools for one, root explorer for two others which would not install. I copied them from another device onto an sd card, then copied into the correct folders in my nook before installing. Adb is another option to install problem aps.
After doing the market visibility fix, all of the apps, except Ibird Pro, that were still missing form "my downloads" were free ones. That was not a big problem. I just had to look them up and install them again. After I did that, they were back in "my downloads" again. The problem with Ibird Pro appears to be that the Market thinks it won't run on my Nook, so it doesn't show it on the Nook. As I explained, the Market on PC Browser won't send it to the Nook because it claims it is not compatible. I tried several of the fixes mentioned in the developers thread, including renaming vending.apk, etc., but nothing worked. After reading your post I tried unchecking "allow market apps, rebooting, etc." also without any luck. My hope is that this is a different issue than those fixes address. (I can't post in the developers forum because I'm considered a newby here.) It seems like the Nook is simply reporting the wrong hardware or OS to the Market. There could be a simple solution to this, like finding and modifying a text file somewhere in the system. If I were a betting man, I'd bet this is an issue with the B&N 1.2 update, rather than the MN files.
Yeah the post restriction is kinda painful. I only registered to be able to thank those whose work I used and post my experiences w/ .25 as there have been some interesting differences in how the update has been affecting users, and more data can help poinpoint why. Still, I understand why it's there.
I missed that the unsupported message was on your pc, sorry. I think the issue is MN from what you said though. I may be mixing up the large amount of info I've been absorbing recently, but there was a signature issue with the new market or something like that, and I believe I read part of the fix was to change the device the market sees the nook as.
I could be way off, but I remember reading something to that effect in the mn thread. I'm still very new to anroid roms, this is the first I've gotten to play with. =) But this could be exactly your problem.
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.
Searched and haven't found an answer yet... rooted 1.2 Nook (latest version of MN), encountered my first Market error ever while installing Foursquare.
The install fails with a "Installation Error - Missing Shared Library" dialog.
Any ideas as to what library this is referring to, and possible fixes? I have a feeling it is somehow related to geolocation or Google Maps (which is installed, updated and working fine on its own).
same in here
glaeken said:
Searched and haven't found an answer yet... rooted 1.2 Nook (latest version of MN), encountered my first Market error ever while installing Foursquare.
The install fails with a "Installation Error - Missing Shared Library" dialog.
Any ideas as to what library this is referring to, and possible fixes? I have a feeling it is somehow related to geolocation or Google Maps (which is installed, updated and working fine on its own).
Click to expand...
Click to collapse
stuck with the same error with foursquare too, any solution so far ?
Seyfovski said:
stuck with the same error with foursquare too, any solution so far ?
Click to expand...
Click to collapse
You should contact the app developer. Your Android version might not be supported by Foursquare. Check its minimum API requirement.
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.
Hello there,
so I just revived my old Nexus 2012 wifi model and wanted to try to run TFT on it and maybe some Anime stuff(which is working perfectly fine like it did back then). Now I'm running into the problem that both the playstore and the apk install wizard(or just installer?) tells me that my device is incompatible.
I tried to install the app through Aptoide and I tried to change the build.prop to make it look like it's my OnePlus6 but it's not working. The Playstore still refuses to list the app and when I try to install it through Aptoide I get the incompatible error when installing.
Does anyone know a way to resolve the issue?
I'm currently running on 7.1.1 nAOSPRom, I thought about testing another rom but the system is running kinda smooth overall which is not how I remembered the tablet to be when I last used it like 3 years ago xD