This morning my N6 started showing an "update available" notification but when tapped the PA updater shows that it is current. Anyone else having this or is it me? Build no. MTC20F on 6.0.1.
Related
"unfortunately, the process com.google.process.location has stopped"
Just popped up on a new CM11 nightly build.... Does this have anything to do with Gapps?
I've been using 1-11_GApps_Core_4.4.2_signed.zip which was working fine, yet I'm wondering if that's what's throwing this error??
Edit** Just discovered an update 1-16_GApps_Core_4.4.2_signed & It's fixed the problem!
I guess Google apps has to be updated fairly often!
If any developer could shed some light on this it would be appreciated...
before I was on 1-11 now 1-16 does that mean its good for up to 16 nightly releases or something?
netwave said:
"unfortunately, the process com.google.process.location has stopped"
Just popped up on a new CM11 nightly build.... Does this have anything to do with Gapps?
I've been using 1-11_GApps_Core_4.4.2_signed.zip which was working fine, yet I'm wondering if that's what's throwing this error??
Edit** Just discovered an update 1-16_GApps_Core_4.4.2_signed & It's fixed the problem!
I guess Google apps has to be updated fairly often!
If any developer could shed some light on this it would be appreciated...
before I was on 1-11 now 1-16 does that mean its good for up to 16 nightly releases or something?
Click to expand...
Click to collapse
I really have no idea. I mean some people have Google Play Services errors and some don't. I don't get them, but maybe somebody else can shine some light.
Hi..
It is a little bit old but i just got the same problem and i found out the solution..
Uninstall the updates of "Google Play Services" and re-install it again.. this will solve the problem..
The newest play services update has made my N5 crazy.
Constant force closes on play services and processes.location.
Yesterday play services kept my device awake all day and made it un-chargeable while plugged in wall charger. I mean it showed "charging" but was in fact diacharging whole time. Swapped couple of nokia and moto and samsung chargers but to no avail. Finally wiped everything and did a fresh install of mahdi rom which solved the charging issue but force closes have kept their vow of diaturbing my normal usage.
Sent from my Nexus 5 using Tapatalk
Try the Nexus5 forum section...
I just bought my Asus zenwatch today and I updated it all the way to 5.1.1. I noticed that when I turn off the "always on" feature, when the screen is off and I tap the screen to wake it, a green screen flashes real quick before the screen wakes.
Has anyone else had this issue? I feel like when I updated to 5.1.1 alot of weird things have been happening. I was not able to connect for a while and the screen randomly turned off like if it got stuck.
I have already uninstalled and reinstalled and done factory resets on the watch and the phone. I am still getting the green screen flicker.
I don't know what I should try next. On the Asus website they have 2 previous updates and no android 5.1.1 on there. Can I somehow roll back to an older version of the zenwatch? or should I try to reinstall the Android 5.1.1 update?
Hi, I just received my brand new SW3 and I'm having trouble setting it up.
I link it to my phone (Galaxy S6) and then it brings up the "Downloading" screen on the watch. About 1/10th of the way through it comes up on the screen that "Android Wear has stopped", followed by "Google Play services has stopped".
I've tried resetting the process many times and it happens over and over.
Any advice?
Edit: Downgraded to an earlier version of the Android Wear app, apparently the latest ones don't keep in constant contact with the watch, hence the crash. Went to the version from the 25th February and so far so good, it's got to 50%.
Have you got the latest firmware on the watch? I have a sw3 and s6 combination - it has been difficult with the latest updates, but a new version of play services a few days ago seems to have helped
Outcasst said:
Hi, I just received my brand new SW3 and I'm having trouble setting it up.
I link it to my phone (Galaxy S6) and then it brings up the "Downloading" screen on the watch. About 1/10th of the way through it comes up on the screen that "Android Wear has stopped", followed by "Google Play services has stopped".
I've tried resetting the process many times and it happens over and over.
Any advice?
Edit: Downgraded to an earlier version of the Android Wear app, apparently the latest ones don't keep in constant contact with the watch, hence the crash. Went to the version from the 25th February and so far so good, it's got to 50%.
Click to expand...
Click to collapse
For anyone interested, the exact wear companion version that can get you past this error is 1.0.5.1724356. It will update device from 4.4.* to 5.0.2. You may get a warning that "something went wrong" while downloading which can be ignored.
I'm having this exact problem. After using the earlier Wear app, should I update it after?
My wife had this same issue with her watch when she was trying to set it up. She has a S5. It kept getting stuck at the same point when downloading. I thought the watch was defective but it was an issue with the phone. I used my phone to setup the watch instead and had no problem. After it finished I connected it back to her phone and she hasn't had any problems since.
Sent from my LG-D850 using XDA Premium 4 mobile app
US firmware S8+ (orig. t-mobile)
Just got my Zenwatch 3, and installed the latest version of Android Wear, as well as the Google App. Reset the connection, watch, reset my phone, this ****ty notification keeps popping up every 30 seconds. Any ideas?
Thanks.
So I was on lineage today and all of a sudden I got the update icon on my notification bar I proceeded to downloading what seemed to be DP 5 and was wondering if anybody else has gotten this as I don't see any thread regarding the new update there's nothing noticeable about it but it runs smooth just in case anybody is wondering I am running magisk 16. 7 and everything is running smooth