Related
I have a Nexus 5 (4.4 stock). No Exchange accounts configured. I do use Pushbullet and NILS adn also have a Garmin GPS paires via Bluetooth.
I bought a Moto 360 so installed Android Wear. It started crashing instantly. I rebooted - same thing. I uninstalled/reinstalled - same thing. I can successfully launch Android Wear for like a minute directly after rebooting and then it crashes and proceeds to show the "Unfortunately , Android Wear has stopped." error like every 30 seconds. I have managed to pair my phone and watch but using my phone with this constant pop-up is more than just a pain...
Any ideas ?
Hi,
I have the exact same issue since this morning.
I have a MOTO 360 for more than one month, paired with a Nexus 5 (running KitKat) and everything was running fine ... until today.
I know have this "Sorry, Android Wear has stopped running" message every 30 seconds on my phone.
I've remove/installed Android Wear (client), factory reset my watch, removed developer options, the Bluetooth association... It does not help.
Android Wear won't start and I can't connect it to my watch. But the message is still here, again and again.
I suspect that the very last update of Google Service play is behind that (this thing is the worst part of Android) but I can't sort this issue.
Have you been, by chance, able to sort this issue?
Thanks,
M
I'm having almost exactly the same problem as you aimache. I've got a moto 360 paired to my Oneplus One, which is running on Cyanogenmod 11S.
I've had my moto 360 for 3 weeks and it was working fine, until suddenly about two days ago, the android wear app started crashing and I'm now getting pop ups on my phone literally every few minutes to tell me that "Unfortunately, android wear has stopped". If I try to open the android wear app it crashes after 1-2 seconds, so I can't do anything in it at all.
Oddly, the moto 360 seems to still somehow be pairing with my phone and receiving google now cards, but isn't getting any of my notifications like emails, texts, or calls.
I have no idea what caused the issue, but it's very frustrating and I would love it if someone could find a fix!
---------- Post added at 12:42 AM ---------- Previous post was at 12:21 AM ----------
I've just cleared the cache of Google Play Services in settings, and that seems to have fixed the issue. I can now open the android wear app with no problems and it's not crashing at all any more.
Fingers crossed it will continue to work :fingers-crossed: So try clearing the google play services cache on your phone and hopefully it will fix the problem for you too
Well I've tried clearing the Google Play Services cache but no luck...
Me too
Just wanted to add to this thread - having the same problems with Android Wear app. Bought a Zen watch, Android Wear crashes before I can even get it paired. I get to the screen about "select your device" see the watch and usually get as far as getting the pair request on my watch. It never completes the pairing. Sometimes crashes right away, sometimes a few seconds, sometimes 10 or 12 seconds but never yet successful. Have tried clearing app cache and app data. Will try uninstall/reinstall with reboot between but not very hopeful.
Kinda sucks cuz the watch is useless without. Hopefully it IS just an app update and we'll have in a day or two. Otherwise it goes back
Nexus 5 running 4.4 based Cataclysm rom.
I've tried looking everywhere but haven't been able to find anyone with this issue. I have a fresh install of Resurrection Remix Marshmallow on my Galaxy S 5, and I have factory reset my Gear Live. When I download and open the Android Wear app, it acts as though there is already a watch paired, but has no information on it. Resetting the app, google play services, clearing caches and reinstalling has not fixed this issue. The app does not come up with the welcome screen, just goes straight to the screen as in the attatched image, with no way to pair a watch.
Anyone able to help here? Next step is to reinstall the ROM, but I want to check there's no simple solution first.
Is your Gear Live up to date? Did you check, if there is newest firmware for it? Maybe there is update, which you should force your Android Wear app with?
Uninstall Android and reinstall. Takes care of that occasional problem for me.
On the watch:
Settings, Un-pair with phone. (Old release of AW may say Factory reset.)
Do not set up the watch yet.
On the phone:
In Android Wear use the Disconnect... option.
In Android Wear, use Settings, Device settings and touch the watch name, Touch FORGET WATCH.
Settings, Bluetooth. If you still see the watch, touch Forget... the watch so it no longer appears in the list of paired devices.
Settings, Device, Apps, select Google Play Services. Clear cache and Clear data. Uninstall updates.
Settings, Device, Apps, select Google App. Clear cache and Clear data. Also Uninstall updates.
Settings, Device, Apps, select Android Wear. Clear cache and Clear data. Also Uninstall updates.
Play Store, Apps, My apps, touch the Update all button.
Let all updates complete. This may take several hours. The best thing to do is to put your phone on its charger overnight, with the phone having a steady WiFi Internet connection. Double check the next morning by going to My Apps again.
Reboot.
Now set up the watch as if you had just un-boxed it.
Let all updates complete. This may take an hour or so. If your watch is one or more major releases behind it may take several hours. The best thing to do is to put your watch on its charger next to your phone on its charger, with the phone having a steady WiFi Internet connection.
Reboot watch and phone.
kaise123 said:
I've tried looking everywhere but haven't been able to find anyone with this issue. I have a fresh install of Resurrection Remix Marshmallow on my Galaxy S 5, and I have factory reset my Gear Live. When I download and open the Android Wear app, it acts as though there is already a watch paired, but has no information on it. Resetting the app, google play services, clearing caches and reinstalling has not fixed this issue. The app does not come up with the welcome screen, just goes straight to the screen as in the attatched image, with no way to pair a watch.
Anyone able to help here? Next step is to reinstall the ROM, but I want to check there's no simple solution first.
Click to expand...
Click to collapse
Hello @kaise123,
I am having the exact same problem. The Android wear app doesnt show anything just remains blank. Did all sorts of deleting cache/data/uninstall/reinstall. Nothing is working.
Please can you let me know how you solved this issue?
rvs80 said:
Hello @kaise123,
I am having the exact same problem. The Android wear app doesnt show anything just remains blank. Did all sorts of deleting cache/data/uninstall/reinstall. Nothing is working.
Please can you let me know how you solved this issue?
Click to expand...
Click to collapse
Sorry for the really late reply, but I ended up simply reinstalling my ROM. I believe the issue was caused by using Titanium Backup to restore data to some Google services, even though I kept a fresh install of Android Wear.
I keep having to reconnect my previously paired bluetooth devices, and I believe this started after upgrading to Marshmallow. Initially, my devices seemed to unpair infrequently, like maybe every 10-14 days. But now, for whatever reason, it is happening more frequently and sometimes daily.
After reading through the forums here and at AC, I thought it might be happening because I rename the devices after I pair them, but that didn't solve the problem when I stopped that.
After Marshmallow, Android Pay required a screen lock to use, which I never had done in the past, so I also enabled Smart Lock and set my paired bluetooth devices as trusted devices. I just disabled all of that (screen lock, android pay and smart lock) so I maybe that will solve the problem, but I suspect it won't.
Anybody have any ideas?
Hi,
I have the exact same issue!
VEry annoying!
Clearing, hard reseting, repairing etc... tried EVERYTHING!
Now i also set smart lock and trusted devices.. Will go to a meeting and back, will test it on the way.
magdan83 said:
Hi,
I have the exact same issue!
VEry annoying!
Clearing, hard reseting, repairing etc... tried EVERYTHING!
Now i also set smart lock and trusted devices.. Will go to a meeting and back, will test it on the way.
Click to expand...
Click to collapse
Well, that didn't work for me. I also tried clearing the cache from the boot menu, but it's still dropping my paired BT devices.
My new Square Up Contactless + Chip credit card reader arrived yesterday. Unlike their previous credit card readers that connect through the earphone jack, this one connects through BT. I cannot get it to connect to my XPE, but am able to connect it to my Moto X 2nd Gen.
I really hope this is a Marshmallow issue that will be fixed soon, but the lack of responses has me concerned that it won't.
I tried resetting the network settings and wiping the cache, neither of which fixed it. I decided it was time to do a full factory reset, but that didn't fix it either. Any other ideas?
I going to assume you are unrooted... But either way if you can change your SELinux to permissive that might help your Bluetooth issue there is this app here that might help out
https://www.dropbox.com/s/xdllg9xxodnib77/com.mrbimc.selinux_42.apk?dl=0
Sent from my XT1575 using Tapatalk
Got the new phone from Motorola a couple of days ago. After reinstalling all my apps and customizations, including renaming my device and the 4 Bluetooth device I connect to, I started to experience the same problem. Not initially, but soon after I turned on the new System UI Tweak option.
So, I turned off the feature and it hasn't happened since. It has been a few days and I have restart (soft reset) several times, which I found would usually trigger the loss of pairing, so I'm keeping my fingers crossed that it was related to the UI tweaker.
Lately I have been seeing the message "Controller Disconnected" followed almost immediately by "Controller Connected". This flashes near the bottom of the screen several times while watching anything. I've had no problems with the remote functioning. I've changed the batteries in the remote and also unpaired it and repaired it. Does anyone have any ideas what is causing this message?
I get it sometimes as well... Have you paired it with the phone app?
Yes, and that is a possible source of the message. I may try uninstalling the app. I also have an Android Wear watch that could also be the cause.
I've ruled out the phone or the watch. My wife has seen the messages while I am at work. There would be nothing but the remote connected at that time.
I Got the update through a couple of days ago and I've had nothing but trouble since, lots of force quitting and locking up, the console has reset itself a few times as well.
I use the Shield with a 64gb Micro SD and a 500gb external Hard drive, I set the SD Card to act as internal storage, the setup worked fine but the Shield started to lock up so I took that out which fixed the issue. I did a factory reset on the console at this point as well.
Ive been able to setup the Sheild using the Hard Drive or SD Card as internal storage, that seems ok but at the minute the Google Play store wont stop Crashing. First thing I did after the restore was make sure the bundled apps were up to date, this I can do just fine but if I try to go into any app to download it to the console, I just get the 'Unfortunately Google play has stopped' error and nothing happens.
Ive tried resetting the console, clearing the cache on the store, trying the store before I update any bundled apps.. nothing works. The apps installed on there are fine but I cant add anything new.
Is anybody else having similar issues?
mozza54 said:
I Got the update through a couple of days ago and I've had nothing but trouble since, lots of force quitting and locking up, the console has reset itself a few times as well.
I use the Shield with a 64gb Micro SD and a 500gb external Hard drive, I set the SD Card to act as internal storage, the setup worked fine but the Shield started to lock up so I took that out which fixed the issue. I did a factory reset on the console at this point as well.
Ive been able to setup the Sheild using the Hard Drive or SD Card as internal storage, that seems ok but at the minute the Google Play store wont stop Crashing. First thing I did after the restore was make sure the bundled apps were up to date, this I can do just fine but if I try to go into any app to download it to the console, I just get the 'Unfortunately Google play has stopped' error and nothing happens.
Ive tried resetting the console, clearing the cache on the store, trying the store before I update any bundled apps.. nothing works. The apps installed on there are fine but I cant add anything new.
Is anybody else having similar issues?
Click to expand...
Click to collapse
I am having an issue when it wakes after sleeping, I get a message saying Nvidia HDMI Services has stopped working. If you click OK, it just shows the message over and over. The only way to get out of it, is to pull the power cord and reboot. Didn't have the issue until I upgraded to 6.0
gPhunk said:
I am having an issue when it wakes after sleeping, I get a message saying Nvidia HDMI Services has stopped working. If you click OK, it just shows the message over and over. The only way to get out of it, is to pull the power cord and reboot. Didn't have the issue until I upgraded to 6.0
Click to expand...
Click to collapse
I guess we need wait when official mm build shows up on Nvidia home page and then just clean install through fastboot. P.s. ...I have kind of weird lags with remote control, when I start using/presing buttons constantly - volume level goes up and down randomly, and also found even random woke ups from sleep.
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
I have three nVidia Shield 16GB versions and the one attached to a receiver gives me the "Unfortunately, NVIDIA HDMI Services has stopped." message every time I wake it from sleep (which you can click OK, but it immediately respawns). As was stated, the only option is to pull the plug. The other two don't have this issue and I'm wondering if it has something to do with being attached to a receiver. I've had zero issues until the 6.0 update.
stazna01 said:
I have three nVidia Shield 16GB versions and the one attached to a receiver gives me the "Unfortunately, NVIDIA HDMI Services has stopped." message every time I wake it from sleep (which you can click OK, but it immediately respawns). As was stated, the only option is to pull the plug. The other two don't have this issue and I'm wondering if it has something to do with being attached to a receiver. I've had zero issues until the 6.0 update.
Click to expand...
Click to collapse
I have a 16GB Nvidia Shield TV plugged directly into my Sony 4K television. Since the 3.0 firmware/Marshmallow update, I am getting the same "Nvidia HDMI Services have stopped" error as described above. And yes, pulling the plug is the only solution.
Yup. Mine is plugged into a Sony receiver. The irony is that this build was supposed to include a bug fix that people with Denon receivers were having. Well if they fixed that issue they apparently broke the rest of us! Face Palm
I have 2 shields, the one connected to a 4k TV has the HDMI service problem and the one on a 1080p TV don't. I switched both and problems persisted on the 4k TV.
I don't pull the plug to reboot. I just hold back to make the power menu open. I press OK and spam the down button to get on the reboot option and the just spam the OK button for the reboot.
Very annoyed by this.
Contacted Nvidia support about this "HDMI services have stopped" issue: useless. They just provided a generic power cycle/ reboot troubleshooting procedure...which didn't work anyway.
Sent from my Nexus 6P using Tapatalk
same here
mozza54 said:
I Got the update through a couple of days ago and I've had nothing but trouble since, lots of force quitting and locking up, the console has reset itself a few times as well.
I use the Shield with a 64gb Micro SD and a 500gb external Hard drive, I set the SD Card to act as internal storage, the setup worked fine but the Shield started to lock up so I took that out which fixed the issue. I did a factory reset on the console at this point as well.
Ive been able to setup the Sheild using the Hard Drive or SD Card as internal storage, that seems ok but at the minute the Google Play store wont stop Crashing. First thing I did after the restore was make sure the bundled apps were up to date, this I can do just fine but if I try to go into any app to download it to the console, I just get the 'Unfortunately Google play has stopped' error and nothing happens.
Ive tried resetting the console, clearing the cache on the store, trying the store before I update any bundled apps.. nothing works. The apps installed on there are fine but I cant add anything new.
Is anybody else having similar issues?
Click to expand...
Click to collapse
gPhunk said:
I am having an issue when it wakes after sleeping, I get a message saying Nvidia HDMI Services has stopped working. If you click OK, it just shows the message over and over. The only way to get out of it, is to pull the power cord and reboot. Didn't have the issue until I upgraded to 6.0
Click to expand...
Click to collapse
I have the HDMI issue upon waking from sleep, going through a Yamaha surround amplifier. Never had the issue before update. I also cannot do anything with the play store, selecting anything in the store brings up the unfortunately plat store has stopped. Called Nvidia and spoke to tech there, no help thus far, we have a thread in the nvidia forums about the play store. Called google, and they refused to even speak to me because they say it's a manufacturer's problem. Please report to our forum at the nvidia site, there are many of us there and we have tried almost everything to no avail.
Here's the link to the Nvidia forum. https://forums.geforce.com/default/...le-play-store-not-working-with-new-update-/9/
So this Nvidia Shield TV v3.0 firmware/6.0 Android update when about as bad as possible short of bricking everyone's box.
So far I'm seeing in the forums from other owners:
New "Nvidia HDMI Services Have Stopped" error message that can only be addressed by power-cycling
Shield not powering on from Sleep
Google Play Store broken/crashing
Shield controller mis-behaving
Netflix app dropping frames during playback.
Various issues with storage
And I'm sure many others I'm not aware of.
This has been compounded by the Kodi v16 update that just came out and broke 4K playback which is now being resized to HD resolutions.
I have not had any problems with my shield and this update. But must admit that I have not used it that much since the update.
Btw. As far as I can read on the Nvidia shield forum, choosing an SDcard as internal storage, will overwrite use of the internal storage for apps and games.
All the same problems on mine as well. Wish I didn't update!
16g model. I have not had any power cycling or app crashing or services stopped issues. But once again, they've clearly changed how bluetooth works, because sixaxis is currently non functional, which I loathe. Ever since the console came out, the DS4 controller has worked better than Nvidia's own controller, regardless of previous bluetooth issues. Makes me wonder if Nvidia targeted it for convenience.
I have an Android TV Shield (v3.0) which is connected via an amp Denon April-x4100w (hdmi back cover). The first day everything was fine, the second day more image. I tried restarting the shield, reset the amp, turn off the upscaling of the amp, change the video frequency .... do you have a solution???
"NVIDIA HDMI Service stopped" (NVIDIA HDMI Service wurde beendet"
gPhunk said:
I am having an issue when it wakes after sleeping, I get a message saying Nvidia HDMI Services has stopped working. If you click OK, it just shows the message over and over. The only way to get out of it, is to pull the power cord and reboot. Didn't have the issue until I upgraded to 6.0
Click to expand...
Click to collapse
So to say, I am glad not being the only one having that big issue with the NSATV.
Since the update to FW 3.0 (Android 6.0), I often have the problem that I get the pop-up "NVIDIA HDMI Service stopped" (as my NSATV is set to German language it is "NVIDIA HDMI Service wurde beendet").
Even if I accept by clicking "OK", nothing changes. The pop-up doesn´t disappear and I can´t do anything else.
I need to plug-off from power to restart it completely.
Any idea or workaround known?
May be it can be solved by using a different power-off or sleep-mode as before?
Appreciate any idea and help as it is not really amusing to plug-off the NSATV every time..
Dietmar
realcams said:
Since the update to FW 3.0 (Android 6.0), I often have the problem that I get the pop-up "NVIDIA HDMI Service stopped" (as my NSATV is set to German language it is "NVIDIA HDMI Service wurde beendet").
Even if I accept by clicking "OK", nothing changes. The pop-up doesn´t disappear and I can´t do anything else.
I need to plug-off from power to restart it completely.
Any idea or workaround known?
Click to expand...
Click to collapse
I'm having this same exact issue, and have been for a couple weeks (since the update). I've even searched to see if there is some way to go back to the previous version. I don't have a nandroid backup or anything (wish I had thougth ahead), but does anyone know if there's a way to rollback to the Lollipop stock release (including any firmware/boot/etc)?
It will only crash HDMI if unit was sleeping. If you power off instead, it will not happen. Only caveat is that you can not wake the device with controller or remote and have to manually touch the shield unit and wait for the android to load. Not ideal but manageable.
My Shield TV is not usable anymore. Right after a reboot the desktop/home screen is freezing. The spinning circle while loading recommendations stops spinning and the Shield TV does not react to any input. Even the clock is not counting anymore. After about 5 minutes the Shield TV reboots itself (watchdog reset?). And again keeps freezing as soon as the home screen appears. This sucks.
I take it that the general consensus is not to upgrade to FW 3.0 whatsoever? I just received my Shield today, and I'm a little hesitant to even power it up