I installed the android wear google app to check it out. After uninstalling it, reinstalling and uninstalling again, wiping cache including play services cache. The aformentioned in the title just wont go away! Any suggestions or insights? I have the 64gb Turbo.
Does it say "boot loop sync" if it does then you have developer options on. Turn that off and the message will go away.
Wait, do you even have a wear device do connect to? You have to have a watch of some type for it to connect to anything.
It will always show in your notification bar when it is trying to connect to a watch one you have Bluetooth turned on.
I'm assuming you don't have a watch which leads me to the most important question, why are you installing android wear if you don't have a wear device connected?
I have a chinese clone bt watch but it doesnt use android wear. I installed the app to check it out for i will be getting a wear compatible watch soon. The watch is currently connected to my phone but the android wear connecting notification is still there. And i do not have debugging enabled.
jndd333 said:
I have a chinese clone bt watch but it doesnt use android wear. I installed the app to check it out for i will be getting a wear compatible watch soon. The watch is currently connected to my phone but the android wear connecting notification is still there. And i do not have debugging enabled.
Click to expand...
Click to collapse
You answered your own question. If it's not compatible with android wear then wear is still going to be searching for a device to connect to
Sent from my XT1254 using Tapatalk 2
I did not have this issue when i first got the watch. I use a bt notification app and it syncs through that app. I installed wear a couple weeks after abd did not have this issue until after i uninstalled the wear app.
ok since no one else has helped I will bump this up again.I uninstall Android wear and all the other Bluetooth applications I tried with the watch I turn the Bluetooth off so nothing should be paired and I wiped Google Play services cache restart and its still trying to connect android wear.
jndd333 said:
ok since no one else has helped I will bump this up again.I uninstall Android wear and all the other Bluetooth applications I tried with the watch I turn the Bluetooth off so nothing should be paired and I wiped Google Play services cache restart and its still trying to connect android wear.
Click to expand...
Click to collapse
Why don't you post this in the android wear section? If you uninstalled android wear and it's off your phone I don't see how android wear can be requesting access unless there's a setting on your watch
Sent from my XT1254 using Tapatalk 2
Related
Updated my gear 1 to tizen and also my note 8 Ltd to 4.2.2 using the official Germany dom. ...
Watch pairs with phone both showing code but then......nothing.......tries to connect to watch and fails.....
am I missing something
please help cos right now I hate Samsung so much for making this gear not work
I had that happen while trying to flash a custom recovery and failing which resulting in the watch hard resetting itself. My phone would recognize and pair with the watch but it would go in an endless connecting spree. The solution is to go into your Gear manager and gear plugin app info on the phone or tablet and just clear the data. Or you could just uninstall/reinstall the app and it should do the trick.
BlackDave said:
I had that happen while trying to flash a custom recovery and failing which resulting in the watch hard resetting itself. My phone would recognize and pair with the watch but it would go in an endless connecting spree. The solution is to go into your Gear manager and gear plugin app info on the phone or tablet and just clear the data. Or you could just uninstall/reinstall the app and it should do the trick.
Click to expand...
Click to collapse
Have removed all traces of GM and installed a diff version...cant remember which one I first got that worked...could it be the GM thats doing this and not the version of android
Thanks to Tizen I have just bricked my watch, what a complete joke this is
No more smart watches for me ive had enough
Do a search
http://forum.xda-developers.com/showthread.php?p=53630254
Sent from my SM-G900T using Tapatalk
I have factory reset my watch to reconnect with a new Lenovo Vibe X2
The android wear app sees the phone and it is listed but when I click it fails to connect.
I am getting a message saying:
"Unable to pair with G Watch R 31B9. Incorrect PIN or password"
There is no way to enter any PIN since this should be automatically set by the Android wear app.
Any ideas?
rankorn said:
I have factory reset my watch to reconnect with a new Lenovo Vibe X2
The android wear app sees the phone and it is listed but when I click it fails to connect.
I am getting a message saying:
"Unable to pair with G Watch R 31B9. Incorrect PIN or password"
There is no way to enter any PIN since this should be automatically set by the Android wear app.
Any ideas?
Click to expand...
Click to collapse
Have you tried to reset/wipe the wear app on phone?
miffymiffy said:
Have you tried to reset/wipe the wear app on phone?
Click to expand...
Click to collapse
Yes, did a data wipe and a full uninstall and reinstall.
Try adb to watch
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
Click to expand...
Click to collapse
and see if it will allow you to connect this way
Here comes the Lollipop update review of Lenovo Vibe X2 https://www.youtube.com/watch?v=9YhDjUpwny0
The same thing happened to my with a Honor 3C that was previously paired with the watch and the cleaning data and then cache of Android Wear app in the phone solve the problem!
I had issues pairing with my Sony Xperia Z3 compact as well. Did a full reset of the watch without it helping. Had to turn off "stamina mode" which is a power saving feature on the phone to make the pairing work. Don't ask me why, but that helped me.
Last week i had the same problem (again), but this time after upgrading my Honor 3C! I try all the solutions I could find on the net, but none have solved... so after 2 days of trying everything (I even factory reset my phone and watch) I solved the problem... so you could try this!
1 - reset your watch;
2 - pair with other device (not your phone) like a tablet (I pair mine with my tablet);
3 - wait until the watch get set;
4 - go to the configuration menu on the watch and select bluetooth connection;
5 - put your phone bluetooth on and in visibility mode;
6 - wait until the watch find the phone and pair with him;
7 -with the phone and watch get paired, reset the phone;
8 - pair with the phone via android app!
I know that is a little confusing and with a lot of step, but in my case solved the problem since this way the phone received the correct pin from the watch, allowing for connecting with android wear app!
I've given up on the Google Forums, looking for some relief here. Last September we bought a new 2017 Honda CRV. Great car, except...
It worked for several months, now I can't get AA to remain connected at all. I think I have been through everything. I just tried the recommended high quality Belikin 3.1 USB cord, it didn't make any difference. Tried other cords as well. This is so frustrating. One of the main reasons we went with the Honda over the Toyota was the availability of Android Auto. Unfortunately, this has been a real excercise in frustration.
When I start the car (USB not connected at this point), Bluetooth connects and AA automatically starts up on my phone. After a few moments, I plug in the USB cord. On the CRV's home screen the blue Android Auto logo shows in the smartphone field. I tap it and my phone connects to the head. So far so good. However, within a minute Android Auto vanished from my phone's screen and on the car's display I get "Device Not Connected".
Has anyone else had/solved this problem? Any of you using an HTC phone? It's not like the phone disconnects, it seems more like AA on the phone just shuts itself off/crashes within a minute or two of starting, but what do I know? Here is the kicker, the system seems to work fine with my wife's Samsung Galaxy S7 phone, SM-G930V. I just went out for a little drive. The HTC refuses to remain connected, the Samsung did just fine.
Error message: On head, "Device Not Connected". AA on my phone just stops. It's like AA on the phone stops working causing a disconnect from the car. Here is more info about my system.
Car/Head Unit make & Model
2017 Honda CRV
Head model: MY16DA
Android Auto version 4.2.2
Kernel Version 3.1.10+
Build number 1.F195.80
HTC 10, model HTC6545LVW USB C cable
Verizon
Android 8.0.0
Android Auto version 3.4.582534-release
Google play services: ver. 12.8.72 (040400-202717283)
Developer Options >USB debugging enabled. USB set to MTP and also tried other settings.
Tried changing out HTC cords to no avail. Just purchased new Belikin USB 3.1 cord. It didn't make any difference.
I have done a factory reset on my phone and on the Honda's display unit as well. I uninstalled HTC's Boost+, reset my phone's Bluetooth. I changed the battery settings on my phone to not optimize AA, Waze and Google Maps.
How can I fix this? Is there anyway out of this rabbit hole?
Switch USB debugging off change Bluetooth from 1.4 to 1.6 in the developers settings
Running into the same problem with an after-market Sony head unit (XAV-AX5000) and a Samsung Galaxy S7 (Oreo 8.0). I'll have to give the BT setting a try.
dq0 said:
Switch USB debugging off change Bluetooth from 1.4 to 1.6 in the developers settings
Click to expand...
Click to collapse
Nope, didn't work. It seems to connect to the phone fine, but then it quickly disconnects, within seconds, or a minute or two. Posting on Honda thread, it doesn't seem to be an across the board problem, I think it's limited to my phone. Having said that on the AA forums there are plenty of complaints about connecting problems. I was hoping against hope that this forum might have a deeper understanding or possible resolutions.
SammyQ2 said:
Nope, didn't work. It seems to connect to the phone fine, but then it quickly disconnects, within seconds, or a minute or two. Posting on Honda thread, it doesn't seem to be an across the board problem, I think it's limited to my phone. Having said that on the AA forums there are plenty of complaints about connecting problems. I was hoping against hope that this forum might have a deeper understanding or possible resolutions.
Click to expand...
Click to collapse
Try turning Dev mode in AA. OPEN app go to About. Click on the title several times.
dq0 said:
Try turning Dev mode in AA. OPEN app go to About. Click on the title several times.
Click to expand...
Click to collapse
I'm willing to try anything, I had no idea that setting existed. Sorry to say that it didn't work. Ugh.
I have a Galaxy S9+ using a sony head unit. Since the android 10 update most things dont work anymore. Samsung doesnt respond to questions and either does google. I would roll back to 9 but my bootloader is locked. Is there anyway around this ?
I ran into 2 problems after upgrading to Android 10 on my S10e.
1. I had second AA app installed (I think it was the one for phone display)
2. Adb debug has to be off
Also app settings are accessible only through Settings -> Apps -> AA -> In-app notifications settings
mrdlejzr said:
I ran into 2 problems after upgrading to Android 10 on my S10e.
1. I had second AA app installed (I think it was the one for phone display)
2. Adb debug has to be off
Also app settings are accessible only through Settings -> Apps -> AA -> In-app notifications settings
Click to expand...
Click to collapse
This is because AA is built-in into Android 10, it is part of the operating system, so there is no need for the AA app. Upgrading to Android 10 should automatically remove the AA apk used on Android 9.
Sent from my SM-N975F using Tapatalk
uhi711 said:
This is because AA is built-in into Android 10, it is part of the operating system, so there is no need for the AA app. Upgrading to Android 10 should automatically remove the AA apk used on Android 9.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
I uninstalled the old aa app on my phone because i thought it was part of the os, restarted the phone and plugged it in my truck and it would not connect. The only way aa almost works is if you install the app on your phone.
As I said before, AA is built-in in Android 10, so there is no need for the apk. But you are right, there are still a lot of problems with AA on car's screen and Android 10. The fact that your phone does not connect to your car's infotainment system or that you are able to sometimes use AA after installing the apk, does not mean that it should be like this. I am sure that you sideloaded the apk because it shouldn't appear on your Play store after upgrading to Android 10.
I, for example, I refused to upgrade because of the many bugs I read about when using AA. I suffered enough (repeated connection problems), in the beginning, after upgrading my phone from the Note 8 with Android 8 to the Note 10+ with Android 9. I'm afraid that it is not possible to go back to Android 9, as far as I know. You'll have to stick with what you have and dig the internet to find possible solutions, because I'm sure there isn't yet a straight forward fix for your AA problem.
Sent from my SM-N975F using Tapatalk
uhi711 said:
As I said before, AA is built-in in Android 10, so there is no need for the apk. But you are right, there are still a lot of problems with AA on car's screen and Android 10. The fact that your phone does not connect to your car's infotainment system or that you are able to sometimes use AA after installing the apk, does not mean that it should be like this. I am sure that you sideloaded the apk because it shouldn't appear on your Play store after upgrading to Android 10.
I, for example, I refused to upgrade because of the many bugs I read about when using AA. I suffered enough (repeated connection problems), in the beginning, after upgrading my phone from the Note 8 with Android 8 to the Note 10+ with Android 9. I'm afraid that it is not possible to go back to Android 9, as far as I know. You'll have to stick with what you have and dig the internet to find possible solutions, because I'm sure there isn't yet a straight forward fix for your AA problem.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
So i uninstalled AA from my phone and then restarted it. Then i backed it up with smart switch, i then did a factory reset. Then i did a clean install of 10 from Chimera. I restored my phone and plugged it into my truck. It proceeded to install AA and still not worth a damn lol. That was a good 3 hours not well spent. So now i will play no more until if ever a fix comes out. Thanks
dinosaurus1 said:
So i uninstalled AA from my phone and then restarted it. Then i backed it up with smart switch, i then did a factory reset. Then i did a clean install of 10 from Chimera. I restored my phone and plugged it into my truck. It proceeded to install AA and still not worth a damn lol. That was a good 3 hours not well spent. So now i will play no more until if ever a fix comes out. Thanks
Click to expand...
Click to collapse
Sorry to hear about all the trouble. Just keep searching the internet about your specific problem and configuration. If you still have your previous phone and if it still has a working AA, you could use it just in your car connected to your wifi hotspot from your Note 10. Also try a different cable, a shorter one (I use a 1 foot only cable), all my connection problems went away with this shorter cable bought on Aliexpress. Wish you luck!
Sent from my SM-N975F using Tapatalk
---------- Post added at 07:59 PM ---------- Previous post was at 07:50 PM ----------
I forgot to ask, did you try using AA with a wireless connection? If you have a new car, chances are that you could use wireless connection between your phone and the car. There is a setting in AA to enable this. Just set this switch on before trying to connect to the car's infotainment system.
Sent from my SM-N975F using Tapatalk
@uhi711 what did you do to resolve the issues on note 10+
Since Samsung updated to android 10, my AA has not worked.
Cables are same that used to work on Android 9
Keeps disconnecting and reconnecting
Tried clear cache and data on AA
Reset the cars head unit
Used new cables, old cables, OEM cables same issues
Haven't tried a small cable, will try the charger cable that comes with Sony xm3 head phones
deepudips said:
@uhi711 what did you do to resolve the issues on note 10+
Since Samsung updated to android 10, my AA has not worked.
Cables are same that used to work on Android 9
Keeps disconnecting and reconnecting
Tried clear cache and data on AA
Reset the cars head unit
Used new cables, old cables, OEM cables same issues
Haven't tried a small cable, will try the charger cable that comes with Sony xm3 head phones
Click to expand...
Click to collapse
Unfortunately, I do not have a satisfactory answer for you. I just didn't upgrade my phone to Android 10, because of the many bug reports I read about. A long time ago, when I was using the Note 8 and Android 8, I had the same connection problems for a few months. Then, the only thing that helped me was using short (20-25 cm) quality cables, bought on Aliexpress. It might also be a coincidence, I'm not sure, because in the same time I changed cable after cable, Google also updated AA. As of now, I'm using the Note 10+ with Android 9 and the same short cable that I think it fixed my connection problem then, and I still don't have any problem. You'll just have to wait patiently for Google to fix the bugs.
Sent from my SM-N975F using Tapatalk
Hi
I have Lineage OS 17.1 which is Android 10.
Should I install just "AA for phone" instead of normal AA ?
With "normal" AA installed is working, except for notifications that I don't get for any apps (Whatsapp, Telegram,...)
Thanks
woody4165 said:
Hi
I have Lineage OS 17.1 which is Android 10.
Should I install just "AA for phone" instead of normal AA ?
With "normal" AA installed is working, except for notifications that I don't get for any apps (Whatsapp, Telegram,...)
Thanks
Click to expand...
Click to collapse
I'm sorry, I'm afraid I can't help you. I don't know what is Lineage OS and how it works. What I do know is that there is no such a thing as different AA versions. There is only one kind of AA app downloadable from the Play store if you have Android 9 or less on your phone. If you have Android 10 installed on your phone, then you do not need the AA app and you won't be able to download it from the Play store, because it is already built-in in the OS (Android 10).
Sent from my SM-N975F using Tapatalk
I had the same problem with my Note 9 with Android 10, it kept connecting and disconnecting. Restarting the phone worked for me.
The couple AA and Android 10 is known for a lot of bugs and connection problems.
Sent from my SM-N975F using Tapatalk
Found a lot of info on this for rooted devices. but not to much for non rooted devices
i want to install AA on a LTE tablet that will stay in my car. the tablet will run other car related apps.
but im tired of having my phone tied up playing music draining my battery. specially on long trip.
also i cant record videos or talk on the phone and still have music lol i know things i shouldnt be doing anyway..
is there anyway to make it work. i tried to sideload it. but got an error 22 that android auto needed to be installed on my os.
any help would be appreciated
maybe try AA emulator on this tablet?
Android Auto app is not targeted to tablets, only phones. And since Android 10, Android Auto is a system app, not a user app. So, if your current Android version is 10 or higher and you sideloaded the Android Auto apk, it will not work. To make it work you'll need to root the tablet and install Android Auto as a system app.
[GSI] Fix 'Communication error 22' on Android Auto
If you've installed a custom ROM that doesn't come with Android Auto pre-installed, you'll get the following error when connecting your phone to your car (the Android Auto app opens correctly, the error is only shown when you connect to the car)...
forum.xda-developers.com
The easiest alternative is to use your tablet as an Android Auto receiver using Hedunit Reloaded Emulator. It's available on the Play Store and is very cheap. It has even a free trial app with a 5 minute limit if you want to test it.
When installed, this apps acts as an Android Auto receiver. This way if you connect your phone to your tablet using an OTG cable (or a USB-C to USB-C cable if both devices have this port) your phone will detect the tablet as an Android Auto compatible headunit and show stuff on it.
You can use this app in Android headunits if they don't have Android auto compatibility, as long as they support USB OTG mode.