Android Auto Problem with Z Force - Moto Z Force Questions & Answers

I'm coming from a Nexus 6 which always worked well with the Android Auto in my 2016 Accord. I just tried connecting the Z Force and keep getting a USB error on the in-dash display. I've tried everything - unpairing, clearing cache & data from Android Auto app, restarted phone, car, etc. - still getting the same error. The USB-C cable I'm using is fine. Anyone having similar issues or any suggestions on how to fix? Can't keep the phone if it won't work with AA. Thanks.

Have you tried a complete factory reset? This tends to solve many issues with android devices. Just a thought!

Related

Android Wear Crashes Constantly

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.

Auto rotate suddenly stopped working! Help!

So I only noticed the issue a few days ago. I turn on my tablet (running 5.1.1 stock, non rooted) and it locks itself into portrait if held in that position and likewise for landscape. Now when I attempt to auto-rotate the screen the usual way, nothing happens.
Any apps that use a forced orientation setting like Google Books (which I have set to forced portrait) will force it from landscape into portrait mode and remain that way, even after closing the app. Likewise for apps that force portrait to landscape.
I've tried checking that auto-rotate was enabled, tested. That it wasn't enabled, checked. Re-enabled it and checked.
Tried the same process above, but with a reboot in between each step.
Tried a few apps that use the accelerometer and found that it appears to be working fine:
GPS Status & Toolbox by MobiWIA - EclipSim - full range of movement detected.
Accelerometer Sensor by Victor Dmitrienko - full range of movement detected.
Sky Map by Google - full range of movement detected.
Heard people on Nexus 7 had solved it by disabling Google Now and Location Services. Tried both of these, rebooting the tablet each time. No fix.
Tried factory resetting the tablet - Backup & reset > Factory data reset.
Nothing seems to fix the issue. It only seems to have arisen since the recent 5.1.1 update. Anyone got any suggestions on what else I can try to fix this? Would I be right in assuming, that as other software apps seem to suggest the accelerometer is working, that this is an OS issue and NOT hardware?
I've become so despondent, I'm considering donating my tablet to my parents and looking for a replacement.
Thanks in advance for anyone that can help resolve my issue.
A desperate N10 user.
i don't think it's a problem with the 5.1.1 update as i had this problem on kitkat, it was working fine for ages then suddenly out of the blue it wouldn't auto rotate. then when i got the ota update for lollipop the issue went away and it has never come back even after the other lollipop updates. i never could find a solution to it so i can't really help you, i just got lucky that it went away by itself
Hi,
Can you try reflashing system firmware? It seems a system issue and this might help solving it.
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Xperia Z1

Paired Bluetooth Devices Keep Unpairing

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.

Bluetooth Broken

Can anyone upload the Bluetooth Share apk for the stock 6.0.1 image? My Bluetooth was malfunctioning, I tried doing a couple things, freezing and unfreezing in TiBu, etc., and now it's basically become corrupted. Anyone have something they can share or a place they can point me to snag a version? TIA.
EDIT: Should rename this thread to "Bluetooth is broken." At startup I get the error the Bluetooth share has stopped working. Any attempt to toggle on the BT results in the same error. Things I've tried to resolve the issue:
Clearing cache and Dalvik
Uninstalling the BT system app itself and reinstalling
Restoring from TiBU (which probably ****ed it up in the first place)
Various apps from Play Store that purport to fix these issue (none work because they require BT to be on--I can't actually turn BT on)
Booting into safe mode to see if it was a conflict with a 3rd party app
Nothing works. Same issue over and over, Bluetooth share stopped working.
Any suggestions on how to fix this? I don't want to have to re-flash just for BT, but I really rely on it for car audio as well as my watch.
I also tried restoring the system partition from a recent backup in FlashFire. Still same issue.
This ****ing thing. After repeatedly going through all the different steps outlined in the posts above, I one last time went in, force stopped the app, hit the "more" button, then chose to uninstall updates and return to factory version (which, yes, I had done previously). This time Bluetooth randomly turned on and showed my connected devices. Go figure.
I know now this thread seems pointless, but hopefully someone else runs across this and tries some of the steps that randomly ended up working for me. Thanks for reading. LOL.

Bluetooth won't turn on after update to Nougat

I had tried many different ways, such as:1. Wipe cache. 2. Clear Bluetooth cache. 3. Reset Network. 4. Factory Reset. None of them work out. And I almost need the Bluetooth all the time for my headphone, smartwatch, speaker.
I am having the same issue with my S7 Edge from AT&T.... It was working just fine my bluetooth watch was synced to it up till all the sudden bluetooth refuses to turn on at all... I'm miffed as to why.. I"ve tried all the cache wiping factory resetting also.. no dice... I am super mad its broken...
Let me know if anything comes of this.
I was thinking maybe it was caused because I installed root access on it, but it was working fine for quite a while after rooting so I doubt thats the case.
Bluetooth Not Working
WowTheDog said:
I am having the same issue with my S7 Edge from AT&T.... It was working just fine my bluetooth watch was synced to it up till all the sudden bluetooth refuses to turn on at all... I'm miffed as to why.. I"ve tried all the cache wiping factory resetting also.. no dice... I am super mad its broken...
Let me know if anything comes of this.
I was thinking maybe it was caused because I installed root access on it, but it was working fine for quite a while after rooting so I doubt thats the case.
Click to expand...
Click to collapse
I bought a used S7 Edge with AT&T that has a bluetooth issue and I believe the OTA update was installed before I ended up with the phone. Can I back up to the previous update to see if that will fix the problem? Bluetooth will not turn on, slider moves, but doesn't lite up, and reverts back to off as soon as I leave that screen. I think that reverting to previous update might restore Bluetooth function.

Categories

Resources