Hey guys,
I was using Galaxy tab 7 since 6 months, yesterday i upgraded it to Galaxy Tab 7 Plus (P6200 with Honeycomb 3.2).
Basically i use my tab to make sip (voip) calls for example through Fring, Nimbuzz etc. it was working perfect in older version. But in newer one, when i try to make any call, it immediately disconnects.
There is also a genuine SIP setting in the tab, but same problem.
I have also installed SIP Driod, SAME PROBLEM.
Please let me know is there any special setting?
I have re-installed all above application, have done factory reset, rebooting many time. but
No one knows solution for my problem????
PLEASE HELPPPPP
Still waiting ...................
Hello everyone,
I just received a used 2nd Gen moto and I have some problems in make the first syncing with my mobile.
Pairing is successful, then it passes an updating process and finally it gets stuck at Syncing screen.
Is anyone having any ideas what can I do to solve this issue?
If I open the Motorola Connect app, I see my watch as Disconnected. I don't know if the syncing procedure is causing this or truly the BT connection is down.
So no such problems for XDA members?
At least can someone tell me if it's normal that from the Bluetooth menu of the watch,I don't see my phone as available?
Is it because they are already paired?
Unleashed by my M1 NOTE
I don't see my phome (Nexus 6) either.
I solved my problem, by activating all permissions for Android Wear and also its notifications.
Finally, enabling the location at the phone is needed.
Unleashed by my M1 NOTE
im still stuck with it... it shows me frequent pairining request, then it shows unable to connect, then stuck at syncing .... ( my device is nexus 4)
i don't know what to do with my watch
kakkash said:
im still stuck with it... it shows me frequent pairining request, then it shows unable to connect, then stuck at syncing .... ( my device is nexus 4)
i don't know what to do with my watch
Click to expand...
Click to collapse
I have also a N4 and everything was working fine since the beginning.
Don't do the pairing through the mobile Bluetooth settings, but through the android wear app.
Sent from my m1 note using Tapatalk
Hey guys,
I hope that someone got this phone work with his car and Android Auto.
In the past I've tested a few cables and a few ROMs. No combination worked.
In general: is here anyone who uses his Redmi 5 with Android Auto in his/her car?
When there is no hope that I can use the phone with Android Auto it's okay. Otherwise I can collect some more information that you'll need to solve the problem.
At the moment I'm using this ROM: https://forum.xda-developers.com/redmi-5/development/rom-lineage-os-15-1r46-xiaomi-redmi-5-t3849181
Hi all, can't get android auto to work on my s9 plus exynos running all latest updates. My in car dash just keeps disconnecting and reconnecting.
Tried with the same cable and my tab s6 and that works fine. So must be my phone.
Tried clearing cache and data that didn't work.
Can't reinstall app as its now built ibto android 10.
Anyone else having same issue.
Hi guys
i have the XQ-CQ54 model with android 12 and i'm experiencing a lot of crashes with Android Auto. Tried everything including factory reset. Problem appears both on USB connection and wireless and appears on all cars i've tried it on (about 4 this far of different brands and models).
Anyone else with this?
might be app related ,5 iv is very new and might need a new android auto update to work better i would advise reporting that to google so they can have that feedback .
I would try it on my car but my infotainment is a little bit older so i cant get to reproduce the same effect.
viper. said:
might be app related ,5 iv is very new and might need a new android auto update to work better i would advise reporting that to google so they can have that feedback .
I would try it on my car but my infotainment is a little bit older so i cant get to reproduce the same effect.
Click to expand...
Click to collapse
i've tried various versions of android auto, they all crash... but they don't on my Samsung S20FE with same Android OS version (12)
Latest thing i tried was making sure power management is off for both AA and Spotify. We'll see if that makes a difference...
Yet again s20fe is not new on the market ,i know what you are saying but i still feel bugs might need some time to be polished on 5 iv as they dont have same hardware .
You can try to test it in safe mode...tho i am not sure if android auto is disabled or not in safe mode
tried changing battery management settings for apps, i'll see if that makes a difference.
andost said:
tried changing battery management settings for apps, i'll see if that makes a difference.
Click to expand...
Click to collapse
nope, didn't... still crashes...
which firmware version are you running on the CQ54? and which version of Android Auto?
I have an XQ-CQ72 on 64.0.H.11.9, with Android Auto 8.6.124944 and don't have any issues
I have a 5 iv running Android 12 and Android Auto works flawlessly.
It didn't when I first tried it. My previous phone was a S22 and Android Auto worked flawlessly. On swapping the phone to the 5 iv, Android Auto couldn't hold a connection and produced error messages. After checking all the appropriate settings I couldn't find anything untoward. Past experience has shown at this point try a different usb cable....and with a different cable Android Auto started working and has continued to work flawlessly ever since.
I have come across this "sensitivity" to the usb cable before, with an older Huawei phone.
I would suggest trying a different usb cable, if you haven't already, as it may make a difference.
dhj1949er said:
I have a 5 iv running Android 12 and Android Auto works flawlessly.
It didn't when I first tried it. My previous phone was a S22 and Android Auto worked flawlessly. On swapping the phone to the 5 iv, Android Auto couldn't hold a connection and produced error messages. After checking all the appropriate settings I couldn't find anything untoward. Past experience has shown at this point try a different usb cable....and with a different cable Android Auto started working and has continued to work flawlessly ever since.
I have come across this "sensitivity" to the usb cable before, with an older Huawei phone.
I would suggest trying a different usb cable, if you haven't already, as it may make a difference.
Click to expand...
Click to collapse
yeah, it's just that the behaviour is the same both on wireless android auto and with USB-c connected...
tonysunshine said:
which firmware version are you running on the CQ54? and which version of Android Auto?
I have an XQ-CQ72 on 64.0.H.11.9, with Android Auto 8.6.124944 and don't have any issues
Click to expand...
Click to collapse
just updated to android 13 (64.1.x) from 64.0.x firmware - same problem except on the way home it was worse than it has ever been before, crashed / disconnected every 5 minutes and reconnected... extremely annoying.
i have 1 IV and don't have crashes. But generally, not as reliable as it was with my XZ2.
Car is Peugeot 3008 mk2 from 2017. Wireless does not work at all but don't really care about that because it just drains battery instead of charging. Now, charging........sometimes it does not charge despite having AA active and using sat nav. Cable that I used with XZ2 (ugreen) does not work at all for AA. And most of the time not even for data on laptop. Cable from XZ2 works with AA every time, did a 5000km trip a few months back, no issues. Except it does not charge sometimes, LED is on, sign for charging is on but battery charge goes down.
Try cleaning the AA app cache. I had same issues w/ my Pixel after update.
TodNex said:
Try cleaning the AA app cache. I had same issues w/ my Pixel after update.
Click to expand...
Click to collapse
Yeah, I've tried that including completely removing / reinstalling app etc.
Now trying on another phone (yes, another 5 IV) which is set up from scratch without restoring from backup.
I have exactly the same behavior with Xperia 5 IV on both Android 12 and 13. Random crashes. Sometime it works for 1 hour, sometimes 5 minutes. It appears to be worse with Android 13.
I tried changing cable, I even bought a new one... no change.
I don't have AA wireless but it does not appear to be cable related. When the crash occurs, my smartwatch (BT) is disconnected.
somm15 said:
I have exactly the same behavior with Xperia 5 IV on both Android 12 and 13. Random crashes. Sometime it works for 1 hour, sometimes 5 minutes. It appears to be worse with Android 13.
I tried changing cable, I even bought a new one... no change.
I don't have AA wireless but it does not appear to be cable related. When the crash occurs, my smartwatch (BT) is disconnected.
Click to expand...
Click to collapse
Hep, another one here!
i'm trying to remove apps one by one now...
Well, I had 1 hours without any crash... after enabling the debug layer for android auto. I didn't notice any difference or additional info but no crash.
Hey Guys; I am facing the same issue. Just, that it's not related to Android Auto.
Many apps were crashing just randomly.
For example, like Tidal, sometimes it was playing music for hours and sometimes just for a few minutes until it crashed.
So I enabled a feature in developer mode which allows to show a crashing dialog. And just a few moments later the nextcloud app crashed and the error message was something like "out of memory".
Looking in to it => Yep, there it was => the OS is holding almost all of the available memory.
So, you might want to check your memory in Settings => Developer Options => Memory.
And since I almost bricked my device last night, I just flashed the latest 64.1.A.0.857 via newflasher and at the moment (fresh OS) it seems to be better - but I will surley find out these days.
Merry Christmas everyone ...
Hi guys, I had similar problems with Android auto. I did a software repair with Xperia Companion, since then AA works fine.