Related
My nexus 7 just came in the mail and I'm running into error 497 on the play store while trying to update chrome, Google keyboard, and talk back. A few seconds after choosing update it'll give me this error but I've been able to download everything else with no trouble. I already tried a factory reset with no luck.. So I'm hoping someone can help me find a solution.
Is it possible that this could have anything to do with my Google account or maybe WiFi?
Edit: From searching around on the web I have found a solution that works for me. Download tunnelbear vpn from the market, make a free account, and then turn it on and connect to the US. You should now be able to download any of the apps that were giving this error. Alternatively, you can tether your phones mobile connection if data limits aren't a concern. Every other solution I have found has not worked for me including factory reset, clearing Play store data, etc, etc, but these two have. Hopefully this helps anyone else running into these issues out.
Edit : oh you did a factory reset...
Hmm dunno
Sent from my Nexus 7 using xda premium
Alright, so I've tried everything from clearing play store data, Google services data, wiping cache/dalvik and so on to no avail.
However, I was able to update and download apps that were giving me the error by using my phone as a wireless hotspot.. So maybe it's a problem with my internet provider. Anybody else with Comcast having this issue?
Sent from my SCH-I535 using xda app-developers app
jguns112 said:
Alright, so I've tried everything from clearing play store data, Google services data, wiping cache/dalvik and so on to no avail.
However, I was able to update and download apps that were giving me the error by using my phone as a wireless hotspot.. So maybe it's a problem with my internet provider. Anybody else with Comcast having this issue?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I just now experienced this same issue, and I also have Comcast. My Galaxy Nexus was able to update some apps without issue on 4G, and when I went to update my apps on the Nexus 7 it updated all but Facebook Messenger and Google Japanese keyboard support. Got error 497, cleared my cache/data/force stopped Google Play, tried again, same thing. Cleared out some other things that may have made it even worse (Google Play Services, which appears to have completely messed up my list of Installed/All apps in the Play store, oops) but still no go. Tethered the Nexus 7 to my Galaxy Nexus via Mobile hotspot, and it was able to update, but on wifi it fails. This just started happening today, and I've had my Nexus 7 for about two weeks. Not sure what's going on, and your post was one of the first things that came up when I googled it. I see a factory reset didn't help you. I really don't want to have to resort to that, but it appears it wouldn't have helped me anyway. I'm stumped.
jguns112 said:
Alright, so I've tried everything from clearing play store data, Google services data, wiping cache/dalvik and so on to no avail.
However, I was able to update and download apps that were giving me the error by using my phone as a wireless hotspot.. So maybe it's a problem with my internet provider. Anybody else with Comcast having this issue?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hi:
I have Comcast and am not having this issue. Keep us posted on your progress.
Best,
Tom
I have tried the standard google search results fix: force quit and wipe cache/ data for Google Play Store and Google Services Framework, reboot
I have tried installing the Google Play Store to the latest update using the apk.
I've tried pushing the update to the device using the online Google Play Store.
I've tried wiping the system caches.
I've reset and formatted it back to factory settings.
I've tried using different google accounts.
I tried using my wifi (custom setup of dd-wrt) as well as resetting dd-wrt back to the default settings. (Charter)
I tried tethering with my cellphone. (Sprint)
I tried a complete fastboot erase and re-flash of system, bootloader, recovery, etc.
Nothing seems to work. Next step is taking it back and trying a new one, unless someone else can think of something that I missed.
My Facebook messenger fails to update, says package file is invalid, not sure if that's my end or theirs, I'd just wait and see if the update eventually pushes through. Maybe just let it be And see if Google knows of the issue and eventually it'll update...
Sent from my Nexus 7 using Tapatalk 4
Try and reset your routers and reboot your nexus 7.
huskers15 said:
Try and reset your routers and reboot your nexus 7.
Click to expand...
Click to collapse
Thanks??
sublimeike said:
I have tried the standard google search results fix: force quit and wipe cache/ data for Google Play Store and Google Services Framework, reboot
I have tried installing the Google Play Store to the latest update using the apk.
I've tried wiping the system caches.
I've reset and formatted it back to factory settings.
I've tried using different google accounts.
I tried using my wifi (custom setup of dd-wrt) as well as resetting dd-wrt back to the default settings. (Charter)
I tried tethering with my cellphone. (Sprint)
I tried a complete fastboot erase and re-flash of system, bootloader, recovery, etc.
Nothing seems to work. Next step is taking it back and trying a new one, unless someone else can think of something that I missed.
Click to expand...
Click to collapse
None of this things worked for me either except for tethering with my phone. So this leads me to believe it's a problem on Google's end and not the tablet. I would wait a little while for a fix before returning it..
Sent from my Nexus 7 using xda app-developers app
How old are your comcast modem and wifi router? I had an issue where my internets stopped working because the modem was supposedly too old. I got a new modem from amazon (much better one) and now all is well. And i decided to go ahead and update my router. Its ac capable, so if anyone with a moto x or macbook pro air comes over, I will be ready for them
adamhlj said:
How old are your comcast modem and wifi router? I had an issue where my internets stopped working because the modem was supposedly too old. I got a new modem from amazon (much better one) and now all is well. And i decided to go ahead and update my router. Its ac capable, so if anyone with a moto x or macbook pro air comes over, I will be ready for them
Click to expand...
Click to collapse
I'm not entirely sure but I think both are fairly new so I don't think that should be the issue. It just seems weird to me that some apps will download while others won't.
Sent from my Nexus 7 using xda app-developers app
I think I have found a work around. Going to the play store on the web and pushing the app to your tablet seems to work for apps that are giving me this error. However I'm not sure if the web version will push updates or not so that could still be an issue.
Edit: try updating to the newest play store 4.3.10 that is floating around on the web. The issue seems to be resolved now, crossing my fingers.
Sent from my Nexus 7 using xda app-developers app
jguns112 said:
I think I have found a work around. Going to the play store on the web and pushing the app to your tablet seems to work for apps that are giving me this error. However I'm not sure if the web version will push updates or not so that could still be an issue.
Edit: try updating to the newest play store 4.3.10 that is floating around on the web. The issue seems to be resolved now, crossing my fingers.
Click to expand...
Click to collapse
Neither worked for me.
*pushing from the online store added to my list because I forgot that I'd tried that already.
sublimeike said:
Neither worked for me.
*pushing from the online store added to my list because I forgot that I'd tried that already.
Click to expand...
Click to collapse
Hmm well that is no good then. Are you still getting error 497 or is it something else?
Sent from my SCH-I535 using xda app-developers app
jguns112 said:
Hmm well that is no good then. Are you still getting error 497 or is it something else?p
Click to expand...
Click to collapse
Honestly, it was becoming really inconsistent.
After updating the Play Store using the apk, I was, again inconsistently, able to get some apps to download and install that were not previously doing so, but only after I cleared Play Store and Frameworks caches and reboot and even then only one would work before I had to clear caches all over again.
Updating the apk also changed the error I was getting for Google services (maps, music, chrome) to "Package file is invalid."
sublimeike said:
Honestly, it was becoming really inconsistent.
After updating the Play Store using the apk, I was, again inconsistently, able to get some apps to download and install that were not previously doing so, but only after I cleared Play Store and Frameworks caches and reboot and even then only one would work before I had to clear caches all over again.
Updating the apk also changed the error I was getting for Google services (maps, music, chrome) to "Package file is invalid."
Click to expand...
Click to collapse
Well that is definitely not good then. I've had no issues since updating the play store but it's too early to say for sure. If I were you I would call Google support to see if they have any useful advice.
Sent from my Nexus 7 using xda app-developers app
I was having this issue on My Nexus 4 and Nexus 7 last night on Comcast. This morning the apps updated without issue.
jguns112 said:
Well that is definitely not good then. I've had no issues since updating the play store but it's too early to say for sure. If I were you I would call Google support to see if they have any useful advice.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Error 492; 497; and "bad package" are all errors that I had been getting with my first device and then with my replacement.
Finally did enough searching to learn it was likely a Comcast DNS issue.
I tried everything from my office internet and it worked fine. I suspect it's why my earlier device started to go wonky because updates didn't update properly or something got corrupted.
Had this issue updating I forget what at work, it would stop at 1.38MB. Which is weird cause didn't have issues with other apps that same moment. Did a google search and tried a different wireless connection... Was able to update.
Two days after, updates apps at work, no problem. Maybe just a hiccup.
Sent from my Nexus 7 using xda app-developers app
Google recently released an update for chromecast enabling screen cast on supported devices.
Unfortunately, Moto X is not one of the lucky ones
But an user in a Moto X brazillian G+ community, found out that downgrading Google Play Services to factory version enables the option for us!
I just tried myself and for my surprise, it actually WORKS!
Depending on what you're mirroring, it's kinda laggy by now, but you may try yourself. Audio also works! :good:
Vinicius Costa was who made the discovery.
Checkout the post in G+ and a few screenshots and photos:
https://plus.google.com/u/0/+DanielWilliamTR/posts/QphJc1qNetB?cfem=1
EDIT1: Is not really practical downgrade GPS (for day to day use) as it breaks a lot of Google apps. This is only a workaround to enable screen cast while we don't get official support.
EDIT2: I just made a video demonstration of cast screen in my Moto X, the audio is in portuguese, but you can ignore that.
http://youtu.be/9pFlsmqH-Q4
EDIT3: A xda developer released an app that enables mirroring by adding an entry in Google Play Services database (no need to uninstall gps updates).
http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
Sweet. Can't wait to mirror NFL red zone to my TV...
I hope the audio quality is good. Could be my only hope for Slacker radio.
Sent from my XT1060 using XDA Free mobile app
Someone in the Chromecast forum said they modded the build.prop file and got it to show without downgrading anything..
abuttino said:
Someone in the Chromecast forum said they modded the build.prop file and got it to show without downgrading anything..
Click to expand...
Click to collapse
My guess they change model name in build.prop to one of those devices already support it. That could be a better work around
Sent from my XT1060 using Tapatalk
Could you change your build prop to get the new version of the app from the play store, then once working, change it back? My fear is that changing your build prop will break things like Motorola apps and Google wallet, which can be picky about your build prop.
Sent from my XT1053 using Tapatalk
sorullo_xgrx said:
My guess they change model name in build.prop to one of those devices already support it. That could be a better work around
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I think this is worst than downgrading GPS... Changing model name may get you a lot of problems with system and other apps...
I hope there's another workaround other than these two...
xxBrun0xx said:
Could you change your build prop to get the new version of the app from the play store, then once working, change it back? My fear is that changing your build prop will break things like Motorola apps and Google wallet, which can be picky about your build prop.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
The problem is not about updating the app, you can do this by downloading the apk from androidpolice.
But once updated, it won't show the option to cast screen on Moto X by default.
abuttino said:
Someone in the Chromecast forum said they modded the build.prop file and got it to show without downgrading anything..
Click to expand...
Click to collapse
Please share the link...
fndpena said:
The problem is not about updating the app, you can do this by downloading the apk from androidpolice.
But once updated, it won't show the option to cast screen on Moto X by default.
Please share the link...
Click to expand...
Click to collapse
Ok guys, tried this for myself
I DON'T have a Moto X, but a Sony Xperia Z2, but the process should be quite the same, i changed this values from my original build.prop:
Code:
ro.build.product=D6503
ro.product.brand=Sony
ro.product.name=D6503
ro.product.device=D6503
to:
Code:
ro.build.product=hammerhead
ro.product.brand=google
ro.product.name=hammerhead
ro.product.device=hammerhead
I took the changed build.prop variables from a original Nexus 5 build.prop file.
Happy testing
nEUTRon666 said:
Ok guys, tried this for myself
I DON'T have a Moto X, but a Sony Xperia Z2, but the process should be quite the same, i changed this values from my original build.prop:
Code:
ro.build.product=D6503
ro.product.brand=Sony
ro.product.name=D6503
ro.product.device=D6503
to:
Code:
ro.build.product=hammerhead
ro.product.brand=google
ro.product.name=hammerhead
ro.product.device=hammerhead
I took the changed build.prop variables from a original Nexus 5 build.prop file.
Happy testing
Click to expand...
Click to collapse
Is that suposed to work even with the latest Google Play Services?
Any FC's ?
Changing these values crashed Google Play Services for me when I tried last night
Sent from my Nexus 7 using Tapatalk
I was able to get it to work basically perfectly (albeit no audio) just by changing my ro.product.device to hammerhead and nothing else. I didn't see the quick option for casting my screen (probably because I'm using GravityBox), but the new ChromeCast app had the option after a reboot!
nm3210 said:
I was able to get it to work basically perfectly (albeit no audio) just by changing my ro.product.device to hammerhead and nothing else. I didn't see the quick option for casting my screen (probably because I'm using GravityBox), but the new ChromeCast app had the option after a reboot!
Click to expand...
Click to collapse
Works fine here, including audio and quick option (I also have GravityBox).
But I didn't changed anything in build.prop...
If anybody gets this to cast audio from the Audible Audiobooks for Android App on a Moto X, please let me know! (or even on one of the supported phones, I'd still be curious.)
fndpena said:
Works fine here, including audio and quick option (I also have GravityBox).
But I didn't changed anything in build.prop...
Click to expand...
Click to collapse
I did not downgrade Google Play Services at all though, I didn't even have the option available in the app settings.
I just made a video: http://youtu.be/9pFlsmqH-Q4
I did have a working "Cast screen" button from the quick settings menu about 1 month ago which worked for about a week then either a Google Play or Motorola update disabled it. This is on a stock XT1053 connecting to a rooted Chromecast running Eureka ROM; screen mirroring and video both worked but no audio. Settings/Display/Cast screen showed my Chromecast as well. After it not working for the last several weeks I was anxiously awaiting this latest Chromecast Android app update that came out today...but after updating the "Cast screen" option is still not back working on my Moto X. I think it was something changed by Motorola because my 2012 Nexus 7 has had "Cast screen" working from the same time as the Moto X and it has never stopped working.
The posted video wasn't working, uh unfortunately.. Does anyone have a link to the downgraded Google play servicwa apk file?? It would be greatly appreciated.. I'm trying to get this working on my nexus 7 2012.. I changed the build prop to hammerhead and now get the option to cast screen but it Google play services crashes afterwards.
ironmaskusa said:
The posted video wasn't working, uh unfortunately.. Does anyone have a link to the downgraded Google play servicwa apk file?? It would be greatly appreciated.. I'm trying to get this working on my nexus 7 2012.. I changed the build prop to hammerhead and now get the option to cast screen but it Google play services crashes afterwards.
Click to expand...
Click to collapse
You mean the video I posted on youtube? It IS working. Maybe when you tried to watch youtube was processing it.
Here is the version of GPS that worked for me: https://drive.google.com/file/d/0B2xwvLA6kyxANkxHWEd3S0JWaTA/edit?usp=sharing
http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
Amazon just posted the source code to software version 51.1.4.0_user_514006420 on the US Source Code Notice page. So far this update has been limited to UK Fire TVs, but based on the timeline of the German updates, we should all start to see this update roll out soon. The last two updates both began arriving on US Fire TVs 3 days after the source code was posted.
Be warned that there is an older update prior to this one, numbered 51.1.40_user_514005520, that is reportedly causes XBMC/Kodi to instantly crash on launch. I'm guessing most, if not all, will skip it and update directly to the newer version.
Reason number 1 to root and block updates.
Download URL for software version 51.1.4.0_user_514006420 is http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.4.0_user_514006420-signed.bin
Interestingly, the file path is slightly different from previous updates.
amzdigitaldownloads.edgesuite.net/obfuscated-otav3/... (this update)
amzdigitaldownloads.edgesuite.net/obfuscated/... (all previous updates)
Thankfully the domain has stayed the same.
Like the previous update, the Fire TV I don't want to lose root on is the one that received the update. So I'll post my overview of the changes this update brings when either my "sacrificial" Fire TV gets the update or rbox gets time to pre-root this one.
Psst, @rbox
My FireTV updated last night to this firmware (I am in the Netherlands). XBMC/Kodi still works.
AFTVnews.com said:
Download URL for software version 51.1.4.0_user_514006420 is http://amzdigitaldownloads.edgesuit...ueller-ota-51.1.4.0_user_514006420-signed.bin
Interestingly, the file path is slightly different from previous updates.
amzdigitaldownloads.edgesuite.net/obfuscated-otav3/... (this update)
amzdigitaldownloads.edgesuite.net/obfuscated/... (all previous updates)
Thankfully the domain has stayed the same.
Like the previous update, the Fire TV I don't want to lose root on is the one that received the update. So I'll post my overview of the changes this update brings when either my "sacrificial" Fire TV gets the update or rbox gets time to pre-root this one.
Psst, @rbox
Click to expand...
Click to collapse
So I just updated my Fire TV and uploaded it to my prerooted thread. It looks pretty much the same although my Menu Items xposed module stopped working. It looks like they added the English (UK) language to the selection list. FreeTime still shows up even when switching the language, so not sure how the German/UK boxes know to hide it. Netflix told me I had to update. I hadn't seen anyone mention a new Netflix version and I don't know if people on the old firmware can update to it. The old one is here and the new one is here. It looks like it's a completely different package name, but somehow the Fire TV knows to remove the old one in the process. Some Amazon magic probably, because stock Android doesn't do that. I think this is the "new" layout people have been waiting for. It also seems like it's possibly a native android app vs the old one which seemed to be an html5 app. I am having issues with actually using the Netflix app though. At first it wouldn't log in, then it finally did and it doesn't seem to want to play anything. It might have to do with the fact that the tz partition was updated and it requires that update. I hope not because updating tz can cause an instabrick. I may have to look into this later if Netflix doesnt start working tomorrow.
same issue here. I hope, there is a solution for this as i want the new netflix ui
I tried too. I was forced to upgrade the Netflix app which then prompted me to re-enter my login credentials. I had no problem with that, but nothing will play. I restarted the app multiple times. It always connects to the service, but cant play anything. The circular indicator comes up and spins a bit, gets to 3% and then fails with a message saying that the video cannot be played right now.
Unless Voice search is part of this NetFlix update or not sure if it was already functioning ?? Isn't it better to just sideload NetFlix from the PlayStore since it's the one that gets the most/quickest updates anyway ?? And get rid of this one ?
Y314K said:
Unless Voice search is part of this NetFlix update or not sure if it was already functioning ?? Isn't it better to just sideload NetFlix from the PlayStore since it's the one that gets the most/quickest updates anyway ?? And get rid of this one ?
Click to expand...
Click to collapse
I tried the Android Netflix app once. Thought it ran and looked like crap.
If I update to this with a prerooted image, will I get root, if I don't currently have root?
shollywood said:
If I update to this with a prerooted image, will I get root, if I don't currently have root?
Click to expand...
Click to collapse
Well, you need root (and custom recovery) to update the pre-rooted image. So, no, you won't...
possible Netflix fix?
rbox said:
So I just updated my Fire TV and uploaded it to my prerooted thread. It looks pretty much the same although my Menu Items xposed module stopped working. It looks like they added the English (UK) language to the selection list. FreeTime still shows up even when switching the language, so not sure how the German/UK boxes know to hide it. Netflix told me I had to update. I hadn't seen anyone mention a new Netflix version and I don't know if people on the old firmware can update to it. The old one is here and the new one is here. It looks like it's a completely different package name, but somehow the Fire TV knows to remove the old one in the process. Some Amazon magic probably, because stock Android doesn't do that. I think this is the "new" layout people have been waiting for. It also seems like it's possibly a native android app vs the old one which seemed to be an html5 app. I am having issues with actually using the Netflix app though. At first it wouldn't log in, then it finally did and it doesn't seem to want to play anything. It might have to do with the fact that the tz partition was updated and it requires that update. I hope not because updating tz can cause an instabrick. I may have to look into this later if Netflix doesnt start working tomorrow.
Click to expand...
Click to collapse
I just had a look over on the amazon forums and found this below. Is someone able to try this to see if it fixes Netflix please? If I upgrade & break Netflix I'll be in a lot of trouble with the family
From Amazon customer discussions...
"I found this tip somewhere, and it finally worked. Apparently the Amazon Video app has problems clearing cache or some such.
Go into your settings--> Apps---> Amazon Video. Click the clear cache, and then the delete data. Let it sit for about 30 seconds. Back out and view it to make sure they both show 0.0 MB. Then just turn off (unplug) the FireTV for about 30 seconds. When you come back in, Netflix, Hulu and anything else that has been having trouble connecting will work again. IIts clearly a bug in the Prime Video software "
Resnoid said:
If I upgrade & break Netflix I'll be in a lot of trouble with the family
Click to expand...
Click to collapse
Just backup and restore the backup if it doesn't work.
rbox said:
Just backup and restore the backup if it doesn't work.
Click to expand...
Click to collapse
You are quite correct. Complete brain failure on my part
Tried it and its not working. Same problem as before...
Sent from my One A0001 using XDA Free mobile app
moqwai. said:
Tried it and its not working. Same problem as before...
Sent from my One A0001 using XDA Free mobile app
Click to expand...
Click to collapse
How about clearing the cache of the NetFlix app too... Or uninstalling Netflix & trying to get it from the Amazon Store again.
Y314K said:
How about clearing the cache of the NetFlix app too... Or uninstalling Netflix & trying to get it from the Amazon Store again.
Click to expand...
Click to collapse
I tried that earlier. I cleared data and cache from the Netflix app but it didn't help. (Though I still had no problem connecting again after entering my credentials for the second time.)
I have a possible fix for Netflix. I'm not very confident about it and there is a very good chance it could brick the Fire TV. If anyone wants to try it, knowing that it could very well brick it, PM me.
rbox said:
I have a possible fix for Netflix. I'm not very confident about it and there is a very good chance it could brick the Fire TV. If anyone wants to try it, knowing that it could very well brick it, PM me.
Click to expand...
Click to collapse
i cant get the new netflix to install on the older firmware, not backwards compatible for me at least.. which is weird since US users aren't forced to update yet afaik so it should work, amazon store says it sent it to my fire tv but it was still the old app. so i added it to the amazon cloud, which got it showing up on the TV, when i goto download it i get "install failed". Are any US users using the new netflix app with an older firmware and updates blocked?
can we swap boot and recovery and still get to fire OS via reboot recovery? might make it safer to test.
nhumber said:
i cant get the new netflix to install on the older firmware, not backwards compatible for me at least.. which is weird since US users aren't forced to update yet afaik so it should work, amazon store says it sent it to my fire tv but it was still the old app. so i added it to the amazon cloud, which got it showing up on the TV, when i goto download it i get "install failed". Are any US users using the new netflix app with an older firmware and updates blocked?
can we swap boot and recovery and still get to fire OS via reboot recovery? might make it safer to test.
Click to expand...
Click to collapse
The new netflix app seems to require a newer version of the Amazon SDK. After playing around with some things I noticed it's expecting a new type of drm library that if it doesn't exist it will fail to run. And that library didn't exist before 51.1.4.0.
As for testing my fix, it's something that would prevent the main bootloader from working if it were to brick it. If only someone was able to figure out how to write the mmc, it'd be very risk free to test...
Marshmallow was automatically installed a couple of weeks ago and has no discernible improvements whatsoever and a whole host of problems (not least that the casting function is now either flakey or non existent and appears and disappears randomly) Because of the casting and dlna problems I want to do a factory reset and revert to lollipop. How can I stop the np automatically 'upgrading" to marshmallow? I know I have the option to turn off app auto updates on Google play but I can't see how to stop it installing marshmallow. Thanks very much.
gmjh said:
Marshmallow was automatically installed a couple of weeks ago and has no discernible improvements whatsoever and a whole host of problems (not least that the casting function is now either flakey or non existent and appears and disappears randomly) Because of the casting and dlna problems I want to do a factory reset and revert to lollipop. How can I stop the np automatically 'upgrading" to marshmallow? I know I have the option to turn off app auto updates on Google play but I can't see how to stop it installing marshmallow. Thanks very much.
Click to expand...
Click to collapse
Google how to use auto starts app for ota updates
OathYvne said:
Google how to use auto starts app for ota updates
Click to expand...
Click to collapse
Ok thanks. But I said I knew how to stop app auto updates. I'm interested in seeing if I can stop auto system updates. It's easy on a phone or tablet. I can't see how it's done on the np. Thanks.
Sideload the "My Android Tools" app which is available at https://play.google.com/store/apps/details?id=cn.wq.myandroidtools&hl=en. After it's installed on your Nexus Player, open and configure it as shown here by using a mouse but you will need root access for this to work.
Service >> System >> Search >> Google Play Services >> Disable SystemUpdateService.
Service >> System >> Search >> Google Services Framework >> Disable SystemUpdateService.
gmjh said:
Ok thanks. But I said I knew how to stop app auto updates. I'm interested in seeing if I can stop auto system updates. It's easy on a phone or tablet. I can't see how it's done on the np. Thanks.
Click to expand...
Click to collapse
Yes I know, you can stop system updates aswell,. ^ basically does what gabby said
Ok. Will do. Thanks very much to both. It's a pity I can't do it without rooting it though (which I don't want do) So it looks like I have no choice but to have marshmallow installed which is crazy really.
gmjh said:
Ok. Will do. Thanks very much to both. It's a pity I can't do it without rooting it though (which I don't want do) So it looks like I have no choice but to have marshmallow installed which is crazy really.
Click to expand...
Click to collapse
Yes, marshmellow is very buggy for me. I have constant error messages where it says this has stopped working, and external storage issues. Are you having the same issues?
My issues are all casting related. Casting is non existent on Ethernet and buggy as hell on wireless. Dnla is also awful and frequently won't work under marshmallow. On my phone I deliberately don't update to a new os until all the problems are sorted. With the nexus player I'm given no choice.
Hi All,
With Google Assistant officially official on Android TV, how to get it on Nexus Player, which technically should be getting it first. Any way, is there a work around to enable it in Nexus Player with Oreo?
Thanks
Prabhu
Any News?
Maxpawner said:
Any News?
Click to expand...
Click to collapse
Someone on reddit posted the ARM version, i don't think that will work on x86
Finally it's work
just download this file:
https://www.apkmirror.com/apk/googl...ndroid-tv-android-tv-3-0-1-172043791-release/
and install it in your Nexus Player
I know its for arm not x86 (nexus player) but its work , I download and install it in my Nexus Player and work 100%
Now I have Google Assistant
thedark1979 said:
Finally it's work
just download this file:
https://www.apkmirror.com/apk/googl...ndroid-tv-android-tv-3-0-1-172043791-release/
and install it in your Nexus Player
I know its for arm not x86 (nexus player) but its work , I download and install it in my Nexus Player and work 100%
Now I have Google Assistant
Click to expand...
Click to collapse
it worked! thank you so much!
Waiting Next Update
Thanks a lot,
I was affraid of try that version until I read your post.
By the way, it works on Nexus Player, but not as good as I wish.
Anyway waiting for the NEXT UPFATE (VERSION) to see if it works better.
It kind of hard to listen your complete Question or Command,
and after frst question you need to close and reopen Google Assintance to maka a new question,
is very lag so far.
Waiting next update of "Google App for Android TV"
thedark1979 said:
Finally it's work
just download this file:
https://www.apkmirror.com/apk/googl...ndroid-tv-android-tv-3-0-1-172043791-release/
and install it in your Nexus Player
I know its for arm not x86 (nexus player) but its work , I download and install it in my Nexus Player and work 100%
Now I have Google Assistant
Click to expand...
Click to collapse
Yesterday, I noticed that the OTA update had added GA, but every time I press the microphone button the device shows the "Meet your Google Assistant" welcome page.
Factor Reset, un-installed and reinstalled the Google App, all without success. :/
Thoughts?
osetivo said:
Yesterday, I noticed that the OTA update had added GA, but every time I press the microphone button the device shows the "Meet your Google Assistant" welcome page.
Factor Reset, un-installed and reinstalled the Google App, all without success. :/
Thoughts?
Click to expand...
Click to collapse
I noticed the latest update with November Security Patch is supposed to have Google Assistant now. I recently bought an nVidia Shield TV device which also has Google Assistant (well was the first device to get it anyway) and it works flawlessly on that device (which currently runs 7.1.2).
I'll have to hookup my NP tonight and update it to see how it works. Mine is running Oreo but I disconnected it when I picked up the Shield TV last weekend. My NP is fully stock, and I did read that GA was a little quirky with the Nexus remote and it was suggested to use your mobile device for a better experience with it. Anyway, point is, I'll hook mine up tonight, update it and check it out. Let you know how it goes [emoji6]