Related
I've been collecting free apps from Amazon on my rooted NC for awhile now. At the time I got each of these apps, they were listed as "compatible" with my device.
Now suddenly a lot of them are not, and I am unable to go back and re-install the ones that I had removed.
Even worse, pretty much everything I've tried so far today to grab has come up as incompatible. Even really simple stuff that should have no problem running.
Oddly, at some point early on, Amazon listed my device as simply "Nook Color". Most of the apps are still showing as compatible with that device. Unfortunately, that's not what Amazon thinks my NC is anymore! I now have a second device on my list called "BarnesAndNoble NOOKcolor", which almost nothing is compatible with.
So then I wanted to check to see if Amazon was behind this, maybe to screw B&N fans. But nope! The Android Marketplace lists every game I've checked so far today as incompatible with my NC!!!
That's certainly news to me, considering some of the games I checked are currently installed on my NC and work perfectly.
I'm not sure what's going on here, but it's sort of scaring me. Who's locking down my rooted NC? If the official android marketplace says everything is incompatible... there aren't a lot of options for getting apps.
Do search with "Market" keyword, you will see about 10 threads with many responses and instructions how to fix this.
votinh said:
Do search with "Market" keyword, you will see about 10 threads with many responses and instructions how to fix this.
Click to expand...
Click to collapse
There are quite a few threads found that way, but none of the ones I read helped. I did the "stop/restart Framework/Google and reload" and nothing changed. Most of the others seem to be related to problems with the new market, which was working perfectly for me up until today, or problems run into right after rooting. I've been rooted for about 5 months with no market problems of any kind, and I haven't changed anything on my NC for over a month.
I also tried clearing the settings for the Amazon market and also deregistered the device from my amazon account, forcing it to re-register. Still no luck.
Anyone else seeing this, or have another suggestion?
My old market and new market were working fine too, just like yours, until a few days ago. If you try the 160 dpi/reboot/clear-data-from-market procedure below and that doesn't work, then you may have a totally unique problem that just happens to have the same variety of symptoms everyone else is having. (I'm doubtful.) This procedure seems to be fixing the problem for almost everyone else. Did you try it? It fixed mine.
1) set dpi to 160 in build.prop
2) reboot
3) clear market app data (force close first may help?)
4) restart market, accept terms, let it rebuild data at 160 dpi
5) profit
the above we all seem to agree on now. Next steps are more speculative
6) set dpi back to 161 (or whatever you had)
7) reboot
8) profit indefinitely (unknown how long this lasts; I rebooted >5 times including flashing a nightly w/o issue)
9) do NOT clear data again as this rebuilds data at the wrong dpi again.
Click to expand...
Click to collapse
Thanks, I had tried the first half, but not the second. I used manual nooter, so my dpi entries originally looked like:
ro.sf.lcd_density.xdpi=169.3333
ro.sf.lcd_density.ydpi=169.3333
I don't know if that makes a difference.
Anyway, I just tried the second half of the above process but I'm still showing as incompatible. I wonder if I need to re-noot.
Everyone trying to be helpful here seems to miss the poster's dilemma. He is talking about the Amazon Market, not the Android Market. Hopefully someone familiar with the workings of the Amazon Market will chime in with some suggestions.
My original problem was with Amazon's market, but it looks like that's just a symptom of the bigger problem that I noticed first because I use it every day, as opposed to much less frequent use of the android market.
But the Android market suffers the same problem and from what I've read online it sounds like the problem was started with changes by Google that Amazon also adopted.
Interestingly I noticed this for the first time last night on the Android market and this morning with the Amazon market. Ebook downloads presently are unaffected to my rooted NC. Amazon recognizes my device as an Android but when I tried to make an app purchase this morning it suddenly tried to download it to a BN Nook. Amazon emailed me this morning saying that unless I have their market preloaded by the manufacturer they do not support it. Collusion?
I got the "not compatible" message after installing the most recent update from the Amazon App Store. Fortunately, I have the very first app store apk. I uninstalled the updated app store, then installed the old apk, logged in and then updated it and for some reason that worked for me. You might try not updating also to see if that works. I am not using CM7 though and I'm not manualnootered. I'm minirooted meaning I can side load apps and have superuser access, but no Android Market access and some other things.
I have attached the apk I used. I hope it works for you.
unibroker said:
Interestingly I noticed this for the first time last night on the Android market and this morning with the Amazon market. Ebook downloads presently are unaffected to my rooted NC. Amazon recognizes my device as an Android but when I tried to make an app purchase this morning it suddenly tried to download it to a BN Nook. Amazon emailed me this morning saying that unless I have their market preloaded by the manufacturer they do not support it. Collusion?
Click to expand...
Click to collapse
A better question would be is Amazon trying to bork the Nook Color with their app?
Anyone else have a suggestion for getting the Android Market working again for me?
thanks for the APK, I'll try it when I have a chance... But since the Android market from Google doesn't work either I'm hoping for a fix to that.
If you make the change in your build.prop “ro.product.manufacturer=BarnesAndNoble” to “ro.product.manufacturer=samsung” then reboot the device. This seems to fix most of the device compatibility problems in the Amazon appstore. I went down the top 100 paid and free app list, and the only apps that came up with the compatibility problems after doing this are,
Soundhound
Peggle
Thumb keyboard
Trainz simulator THD
Chuzzle
Talking Tom Cat
flexT9
GrooVe IP
Ultra Voice Changer
TV.com
Compass
Also attached is the amazon appstore v.1.14, it has the double click buying fix, but does not give all the compatibility issues. With installing this version does fix the compatibility problem, but you will be constantly hounded with the update reminder.
I don't use Facebook, but I was able to find, install and open the Facebook app with the new market. Do the density change using 240. Its more stable than 160 for whatever reason.
GMPOWER said:
If you make the change in your build.prop “ro.product.manufacturer=BarnesAndNoble” to “ro.product.manufacturer=samsung” then reboot the device. This seems to fix most of the device compatibility problems in the Amazon appstore.
Click to expand...
Click to collapse
Thanks for the suggestion. Unfortunately it had no effect. The first four apps i tried not on your list all came up incompatible, as did stuff on the google market.
I'll try your attachment to see if it helps. Thx!
kayak and tripit does not install
Running MN4.5 on NC. Kayak and Tripit are visible in Market and downloads - but I get a window that just says "error".
Any suggestions?
GMPOWER said:
Also attached is the amazon appstore v.1.14, it has the double click buying fix, but does not give all the compatibility issues. With installing this version does fix the compatibility problem, but you will be constantly hounded with the update reminder.
Click to expand...
Click to collapse
The old version of the market is working! I was able to install a number of apps that didn't previously work.
Now if I could just get the Google market to work!
Thanks for that link!
I was having the same problem with the AMAZON appstore (but not the android marketplace, for some reason) but I couldn't find the old amazon appstore apk. Going back to it totally fixed the problem. But you're right, the constant reminders to update the apk are a pain in the whatsus.
Also try going into application management and goto market and tap uninstall updates. Also use titanium backup or similar program to freeze market updater.
By what I read, I bet amazon is trying to block the competition because they are fixing to come out with their own tablets and by horning something like the nook you might be enticed to buy their tablet.
I voided my warranty and your mum.
My markets all seem to do whatever the f*ck they want the moment i need an application that was perfectly available minutes before. What i've done to get around the issue if neither the market or the amazon store have what i'm looking for is: (i know its tedious but hey it works)
1) install astro
2) using your android phone assuming you have one, download the applications you want regardless of them being compatible with the nook color according to the android market.
3) once your files are installed on your phone use astro to create a backup of the .apk files you want (open astro > menu > tools > application manager/backup)
4) i then take my sd card out of my phone and pop it into my nook color and install my apps through w.e file manager it is i have on the nook color
all the games that i cant normally download onto my nook through the official methods i've been able to install and play through the method i've been using. not ALL apps will allow you to back them up though =/
I love my Nook Color! It is an excellent tablet, that can run almost anything.
But I have to download most of the stuff from the Amazon Appstore on my phone, back it up, then copy it over to the Nook and install it manually. I always get the app of the day (whether I want it or not, I figure I may someday and just don't install it). So I have more than a hundred apps available on my phone when I open Amazon Appstore. On my Nook I have 17.
I have successfully installed many of the apps that I cannot see in the Amazon Appstore on my Nook, and they work perfectly. I used to be able to see everything in the Amazon Appstore and then a while back they added some sort of device check that is causing this.
How might I get around that device check? The phone-to-nook shuffle is a pain. It apparently isn't working off build.prop like the Google Market does.
Hm, I have 40~ish apps visible to both my Nook and my G1, and none that only one could see but not the other.
I think it does go off the build.prop - but only the first time you connect with the device. It stores the information for future accesses. So modify your build.prop, then go into your Amazon account from a web browser and click on "Your Apps and Devices". Deregister the device, then run the Amazon Appstore from your Nook (with the phony build.prop). It should re-authenticate with Amazon and register as whatever device your build.prop says it is. It worked for me, anyway.
I find this development a little disturbing, though. Amazon is clearly just trying to freeze out a competitor. They didn't have a problem letting me buy apps for my Nook until they got close to releasing their own e-reader tablet, and suddenly none of the apps that are installed and working on my Nook are deemed "incompatible" on the App Store. I've bought a couple apps through Amazon (and have a good number of the free "apps of the day"), but I certainly won't ever buy another one from them. Sure, I can work around it with this little trick, but I shouldn't have to resort to trickery to get around their bad business practices.
Beautiful. Worked like a charm. I went from 19 apps available to 122. Many thanks.
JMMusic said:
Beautiful. Worked like a charm. I went from 19 apps available to 122. Many thanks.
Click to expand...
Click to collapse
So what build prop info did you use?
doncaruana said:
So what build prop info did you use?
Click to expand...
Click to collapse
I used this:
ro.product.model=Nexus S
ro.product.manufacturer=Samsung
I'm not so convinced it's a nefarious plot by Amazon in their Apps store, nor Google in their Market as I am that I've hacked something in a non-standard and not fully understood way and broken something. I'm seeing the same 61 Apps (on the All tab) on my Nook Color running CM 7 as on my Droid 2 phone. If I go flash a new ROM, it all breaks again. That's ME, though, not them.
I'm enjoying the Free App of the Day enough not to take this out on Amazon.
All I've done is set density to 160 and cleared data.
There's little doubt in my mind that Amazon is restricting apps on Nooks. They're getting ready to launch their own device, so it makes sense to try to reduce the value of a competing product. It's good business sense, but it shows very little respect for the customer.
I hadn't changed anything in months on my Nook, and one day it was suddenly "incompatible" with most apps on the Amazon market. Changing nothing but the product name in build.prop and re-registering the device makes it all work again, and if I change it back to the Barnes & Noble information, suddenly my apps are incompatible again. Sure seems like Amazon is filtering for "Nook" in the app store.
Are we certain this is a plot by Amazon or is this a response to the same type of "feature" recently implemented on the Google App Store?
Homer
It's not the same LCD density issue as the Google Market. I tested that. I registered the Nook as both a Nexus S and the default Nook Color settings in build.prop, at various screen densities, and no matter what the density is, if Amazon thinks it's a Nexus, it shows all my apps. No matter what the density is, I get about 75% of my apps not showing up when it's registered as a Nook Color.
It really appears to me that Amazon's App Store is looking for "Nook" or "Barnes & Noble" or something in the product model at registration. There might be another explanation, but I can't think of one. Especially with Amazon getting set to launch a direct competitor to the Nook Color...
Care to list a few of the apps you're having trouble with? If it's a plot, they shouldn't work for any Nook, right? This should be an easy test.
Never had a problem with any of the apps I wanted.
Just got the app of the day today without trouble too for example.
Guess the conspiracy is not yet fully in force.
Wait... I purchased some books with the Kindle app on my Nook. Perhaps they gave me a good comrade status.
I'm running Stock 1.3 rooted and I have had AppStore since 1.1 rooted. I just bought ThumbKeyboard and followed the directions on the preceding page to modify my build.prop because it wasn't showing. Now Amazon's website tells me it's incompatible with my "Samsung Nexus S" (Nook Color). Any ideas?
Isn't it possible they are simply trying not to give noob customers apps that may freeze their device...like say a nook that doesn't have a back button? It may not be some diabolical scheme to drive people away from the Nook Color simply because they HAVE to have the App of the day.....
A few weeks ago, both amazon and google markets made changes which made their markets more "device aware". This was not done due to any plot by amazon or google but was a change brought about to ensure that apps downloaded to a device would function well. This relieved the markets of the issues that come about by folks downloading incompatible apps then wanting refunds when they did not work. App developers were asked to list devices that their apps were designed to run on and these devices were included in the devs database on the market. This also protects the developers. As I said, no plot, just good business sense.
You can certainly change build properties and reregister your nook but remember that if the app does not function, you have no recourse through the market for a refund.
Just sayin......
Sent from my NookColor using Tapatalk
Ditto to moshe5368 with one correction. A few months ago both Google and Amazon markets made their changes. I ran into the same problem. Unregistered from both markets, edited the build.prop file, followed the directions on repairing / replaceing the market , and finally it worked. Amazon is not plotting against other tablets, for now at least.
My wife's Nook wasn't eligible for the Apps from Amazon. I changed the Build.Prop file to the Samsung Nexus S per the instructions. I deregistered the device from her profile. I changed the screen Density to 160.
Now that I have done all of that, I can't get her device to re-register with Amazon. I tried to delete and reinstall the Amazon App using Titanium, but it wouldn't delete...any ideas? How do I re-register her device?
It's not just on the nook. I'm getting the same responce on my Viewsonic G Tablet.
Skunkeye said:
It's not the same LCD density issue as the Google Market. I tested that. I registered the Nook as both a Nexus S and the default Nook Color settings in build.prop, at various screen densities, and no matter what the density is, if Amazon thinks it's a Nexus, it shows all my apps. No matter what the density is, I get about 75% of my apps not showing up when it's registered as a Nook Color.
It really appears to me that Amazon's App Store is looking for "Nook" or "Barnes & Noble" or something in the product model at registration. There might be another explanation, but I can't think of one. Especially with Amazon getting set to launch a direct competitor to the Nook Color...
Click to expand...
Click to collapse
Amazon is subsidizing the Fire, so it doesn't make financial sense for them to block competitors. They get more money from Nook users up front then they will those that purchase the Fire.
On my wife's rooted nook color, I loaded the Next Issue app for magazines. She has a subscription to better homes and gardens and can view them free if she has the Next Issue app. However, the Next Issue version only supports 1280x800 and doesn't even show as a magazine to select. I've tried every trick I could think of, DPI, Product ID, etc to fool the app into thinking I was using a different tablet (like the Tab 10.1). It must detect the actual resolution. Anyone know of a way around this or where it might be reading the table resolution?
Like I said, changing the DPI didn't fool it and it isn't looking at other tablet identifiers. I don't see where or if the native resolution is stored for apps to check.
OK, I know that this is a pretty common problem...but over the course of a week I've tried every piece of advice I can find on the Internet. But some apps just will not show up in the Google Play Store for me, including ones I've paid for.
Things I've tried:
Read through every post on GMPOWERs impressive thread at least twice and tried every suggestion at least 3 times
Tried both the regular manualnooter zip and the apps2sd one
Tried this post
Since it's fixed almost everybody's problem: I've tried every permutation possible of stopping and clearing data + cache for both Google Play and Google Services framework
Tried restoring Nook to stock and re-rooting with a different SD Card twice
Uninstalled the Google Play updates so that it goes back to being the old-style Market
I'm just about at my wits end - nothing I've tried as fixed the likes of Facebook or Flash Video Browser (what I'm really looking for) not showing up in the Google Play store. Does anyone have any other advice to fix this?
same problem here...
I have three NC. One was rooted in Feb and had full market visibility. The last two NC was rooted last week using the SAME SD card and CWM and with the same procedure. Indeed trying all the fix without success. There was a post indicating that installing MN apps2sd would work ... tried that too without success.
There may be something going on with market/playstore.
Could you give me some more examples of apps that you are having problems with, this will help me out significantly. You should not have a problem seeing facebook in Google Play. You will have a problem with Flash Video Browser, because the description for it in the store says “Requires Android 2.3+.” Since the stock firmware Froyo 2.2.1, the store will not show you the app. A number of people are currently having an issue with the Play Store not listing apps that they have purchased, LINK.
You can try changing your build.prop ro.build.fingerprint to verizon/voles/sholes/sholes:2.2.1/FRG83D/75603:user/release-keys
If you change the build.prop, you will need to reboot the device, then perform the Market has limited visibility found in the ManualNooter 5.02.19 post. If the play store stops working after performing the steps, simply open manage applications and uninstall updates for the Play Store.
GMPOWER said:
Could you give me some more examples of apps that you are having problems with, this will help me out significantly.
Click to expand...
Click to collapse
All the NC had 5GB partitions. I did a wipe data/cache before installing BN1.4.1 (didn't bother to upgrade to 1.4.2).
Followed instructions and installed MN apps2SD on one and non-apps on the other. Flashed OC kernel to both. After rooting, did a search for ES File explorer and only File Expert came up on both NC. Installed File expert then the remaining apks. This may be important. The NC were signed into different gmail accounts (not mine).
Though not related to NC, google moving to Play store seem to have messed up visibility on Nook Touch http://forum.xda-developers.com/showpost.php?p=24288916&postcount=285
Thanks for all your efforts - don't spend too much time on this.
On top of clearing the cache and data for the google play store, did you clear it for google framework services?
fpga_guy said:
All the NC had 5GB partitions. I did a wipe data/cache before installing BN1.4.1 (didn't bother to upgrade to 1.4.2).
Followed instructions and installed MN apps2SD on one and non-apps on the other. Flashed OC kernel to both. After rooting, did a search for ES File explorer and only File Expert came up on both NC. Installed File expert then the remaining apks. This may be important. The NC were signed into different gmail accounts (not mine).
Though not related to NC, google moving to Play store seem to have messed up visibility on Nook Touch http://forum.xda-developers.com/showpost.php?p=24288916&postcount=285
Thanks for all your efforts - don't spend too much time on this.
Click to expand...
Click to collapse
Thank you for giving me that information. It is hard to get accurate information when some people don’t report back. I get some people that complain of limited visibility when it really is limited market access, they can’t find certain apps in the market that they want because it is not compatible with the device. What you described is exactly what I would describe as limited visibility.
I went through that same problem two days ago after a fresh install. I first did a search for Astro, it said 556 apps, but when I clicked on it, only 5 apps showed up, none of them were Astro. I then tried ES File Explorer, and had the same results as you. After I cleared the play store data and google services framework data, and then rebooted the device, it went back to normal. I have had the full market access since then.
I do agree with you that the Play Store has had a lot of problems since being released, not only on the NC, but wide spread. If this continues to be a problem on new installations, I might try updating the vending.apk in the MN package to the current release to see if it would help in anyway.
On a side note, I looked into that google voice issue some more. Using the build.prop that I posted allowed me to download google voice from the play store, but still have the error downloading the voicemail. You can see the voicemail files in /data/data/com.google.android.apps.googlevoice/files, but I could not get them to play. It is still on my list of items to look into more.
Man I'm sorry I can't help you. But I have to say this is one the best written questions I've seen in a while. You stated the problem, said what you did to fix it and let people know you are willing to help yourself. And look who you got helping you out mate. It is nice to see threads like this. Thanks.
- this sig is just so I don't have to write 10char when on my phone -
Possibly stupid suggestion on my part, but what is the LCD density you have now? I had no luck at all using several of the roms until I started changing the LCD density to at least 160-200 until I did that most of the apps I wanted to find wouldn't even show up. Not saying this is the answer for sure, but it may be worth checking out, right?
Never had the problem, but you mentioned the verizon spoof, I thought that would work. What about going to the market on chrome and logging in and selecting you device, I have done that with the nook running cyanogenmod. How about the Amazon app store and sideloading google specific market apps. At least you could have some selection of paid/free apps. Can you install from the uSD card to get by?
---------- Post added at 06:59 PM ---------- Previous post was at 06:50 PM ----------
Never had the problem, but you mentioned the verizon spoof, I thought that would work. What about going to the market on chrome and logging in and selecting you device, I have done that with the nook running cyanogenmod. How about the Amazon app store and sideloading google specific market apps. At least you could have some selection of paid/free apps. Can you install from the uSD card to get by?
manage applications has no options in it
GMPOWER said:
Could you give me some more examples of apps that you are having problems with, this will help me out significantly. You should not have a problem seeing facebook in Google Play. You will have a problem with Flash Video Browser, because the description for it in the store says “Requires Android 2.3+.” Since the stock firmware Froyo 2.2.1, the store will not show you the app. A number of people are currently having an issue with the Play Store not listi...
Click to expand...
Click to collapse
I have a similar problem as the one qouted above however, when I go into settings, manage applications I don't have an option to uninstall updates or the ability to uncheck or check on device-install. any suggestions?
GMPOWER said:
You will have a problem with Flash Video Browser, because the description for it in the store says “Requires Android 2.3+.” Since the stock firmware Froyo 2.2.1, the store will not show you the app.
Click to expand...
Click to collapse
but stock 1.3, 1.4.1, 1.4.2 are gingerbread already?
Current B&N version is 1.4.2 which is Android 2.3 Gingerbread
B&N 1.3 is Android 2.3 Gingerbread
B&N 1.2 is Android 2.2 Froyo
B&N 1.1 and 1.0 are Android 2.1 Eclair
Click to expand...
Click to collapse
I have a few questions before I go & buy the Nexus 7 that I'm hoping someone can answer
1) I will be rooting my Nexus 7 to change the LCD density (Tablet UI ftw!) What i want to know is will this break an functionality of the Tablet or apps? I've heard of Google Play Movies no longer working with root, is this true?
2) Does the Nexus 7 have an LED light on it?
3) Will I still be able to get official updates if the device is rooted & if so what will happen when I apply the update? (I only plan to change the LCD density & that is all)
Thank in advance guys & girls
KarlosTheJackal said:
I have a few questions before I go & buy the Nexus 7 that I'm hoping someone can answer
1) I will be rooting my Nexus 7 to change the LCD density (Tablet UI ftw!) What i want to know is will this break an functionality of the Tablet or apps? I've heard of Google Play Movies no longer working with root, is this true?
2) Does the Nexus 7 have an LED light on it?
3) Will I still be able to get official updates if the device is rooted & if so what will happen when I apply the update? (I only plan to change the LCD density & that is all)
Thank in advance guys & girls
Click to expand...
Click to collapse
1) there are mixed opinions on that. I've seen people posting that it does. I've seen people posting that it doesn't. its a matter of playing with the values but comes at risk of your device not booting up. plenty of people got in a bind over it. I've seen 160 being a good value. those 170 ones seem to cause alot of issues although some still had issues with 160. its sketchy..lol. I believe there is a workaround for the Google movies to play while rooted. can't remwber where its at.
2)No, not that I've seen or noticed. you have to turn screen on to tell if its fully charged or not. you could always install a battery app that sets off a notification or sound when its fully charged.
3) technically, yes you should be able to still receive updates if rooted. just make sure to use Voodoo OTA rootkeeper to backup/save your root first. then you update(in which you will loose root) as you normally would unrooted. then open voodoo app up and press the restore tab to restore your backed up root file and now you rooted after new update.
now the kicker is that alot of times if you change something in system files or make build.prop changes, the Over The Air(OTA) update will fail. As it runs prechecks for those files to be stock configuration before it applies the update. when it detects something is changed, it fails. now you could just manually install the update and it "should" override all of that. its the complete update and doesn't run those particular checks, I believe. most of the time, from what I've heard, the OTA only updates certain files or whatever that has been updated in new release. Manually updating gives the complete updating of everything(I could be wrong though). kinda like installing the whole updated firmware into nexus vs. OTA just updating certain files.
now with you changing the LCD density n all that, I'm not sure if it'll cause update to fail. if changing that resides in system files or build.prop, then it will likely fail. hopefully someone else will chime in on this also.
1. Some apps only support certain LCD densities so if you change the density to something uncommon, some apps might not show up in the store. I'm not sure about the root and movie situation.
2. If you mean a notification LED, then no.
3. If all you do is root (no custom recovery or ROM), then you'll still get updates. If you apply the update, then you'll lose root.
Thanks for the answers guys!
Delivered by Western Union in the rain after 70 Years
May I AKS you a question? :3
Don't have my nexus yet, have to wait until tomorrow.
If possible can someone give the XBMC build a whirl on it and let me know if it is stable (launches, plays SD video nice/youtube, no FC's)
thank you :angel:
edit: found a relevant thread!
XBMC Running on the Nexus 7
Here is another one to the list..
are there different variants from the N7 that you can buy from the Play Store and those you can buy from other retailers? I mean like the Galaxy nexus TAKJU, YAKJU etc
rootusr said:
Here is another one to the list..
are there different variants from the N7 that you can buy from the Play Store and those you can buy from other retailers? I mean like the Galaxy nexus TAKJU, YAKJU etc
Click to expand...
Click to collapse
I doubt it as its a WiFi only device but even if it is you can do the same as the Galaxy Nexus & just flash the better version
I believe people buying from the play store said the device knows their g+ nickname right out of the box but aside from that I don't know of any other differences