Related
Hey everyone,
I just got myself a Gear Fit and wanted to connect it to my (rooted and Custom-ROM) S4.
Everything works fine on my (stock) Note 10.1 2014, it connects to the Fit and everything seems to be ok.
I want to pair it with my S4 though and that does not work.
I got the Latest Download from Here and installed the Fit Manager.
It does attempt to connect to the Fit and then when pairing it jst sits there and does nothing. After some time the Fit attempts another connection, however it does nothing after that either...
Does anyone have an Idea?
Edit:
By now I've tried versions:
1.111.1216 (no connection)
1.78.0721 (crashes on connection)
1.96.1124 (same)
and the "Latest Official" from Here (no connection)
Same with zopo 3x
Hi I have the same or a similar problem. With Samsung s3 on cyanogenmod pairing and connection was fine. My gear fit is on newest firmware and I tried all managers from 1.55 to 1.88. My zopo does pair but not connect. Connection screen on phone is waiting forever. No message. The gear fit wait for pair confirmation of phone. Very strange
Any idea? I tried also to delete pairing in Android Bluetooth settings. Same behavior on next pairing.
Disabling "Developer options" helped in my case on Galaxy Note 4 pairing with Gear 2.
No solution for this Problem? Can't connect my gear fit since firmware upgrade :crying:
alternone said:
Hi I have the same or a similar problem. With Samsung s3 on cyanogenmod pairing and connection was fine. My gear fit is on newest firmware and I tried all managers from 1.55 to 1.88. My zopo does pair but not connect. Connection screen on phone is waiting forever. No message. The gear fit wait for pair confirmation of phone. Very strange
Any idea? I tried also to delete pairing in Android Bluetooth settings. Same behavior on next pairing.
Click to expand...
Click to collapse
i have tried pairing gear fit with rooted xperia c ,
same problem with the confirmation screen , it sticks on screen " Connecting to gear fit "
any solution for this, i have disabled developer option.
seem like SS did something on their rom. My note 3 connect perfectly with GF when using TW base custom rom(both kitkat and lollipop) but when i try with AOSP rom(lollipop), it have a same problem with GFM. So if you want to use ur GF, u need to stay with TW base roms, GFM work well and no problem with both kitkat and lollipop
Sent from my SM-N900T
I have an S4, and that is how I fixed it
Apparently, you need to download the Gear Fir Manager from apps.samsung.com/gearfit not from the samsung app store.
The Samsung app store version does not work, you need to download the latest gear app from the website, gd luck
Yeah it's a bit late but try to get back on Sammy based firmware. That's strange because on lollipop on my Note 4 I couldn't connect to Fit but on S3L with 4.4.4 Note'd 4 software it works perfectly(hah because of Fit went back to S3 )
Sent from my SHV-E210S
THX WRX
Greetings All!
I have a rooted LG G3, Kit Kat 4.4.2, no custom ROM but several apps that required Root.
This is a new problem that has only appeared for a few days. I have no problem connecting to already paired devices. When I try to "Search for devices" it starts the search, then the phone turns Bluetooth off, complains that I need to turn Bluetooth on, then actually turns Bluetooth on. At no point does it show any sign of finding the new Bluetooth device I want to pair with. And I've tried this with a couple of different Bluetooth devices.
On a lark I tried cleaning Cache and Dalvik Cache but that didn't help.
Does anyone have any ideas or thoughts?
Many thanks in advance.
Cheers, Henri
I wanna say latest lollipop firmware fixed many Bluetooth issues.
sent from my LG G3
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
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.
I am using Galaxy Wearable with Galaxy Plugin for Samsung Galaxy watch classic.
After MIUI 14 update its not keeping Bluetooth connectivity properly, its getting disconnected after few seconds.
I have uninstalled whole software and reconnected watch but issue still exists.
Help!
Have you tried Factory Resetting the watch?
teji007 said:
I am using Galaxy Wearable with Galaxy Plugin for Samsung Galaxy watch classic.
After MIUI 14 update its not keeping Bluetooth connectivity properly, its getting disconnected after few seconds.
I have uninstalled whole software and reconnected watch but issue still exists.
Help!
Click to expand...
Click to collapse
Same problem, but on Note 10 Pro. Watch just randomly disconnects, bluetooth connection needs to be manually started again. Tried reinstalling apps, restarting watch, a2dp, turning off miui optimalization, and still nothing.
Everything was working fine on android 12. Now the lifetime of my active2 watch is down from 3 days, to maybe 1,5 days.
Anybody has any ideas? I am considering downgrading to android 12, cause it's so bad.
Thanks!
ccclcccv said:
Same problem, but on Note 10 Pro. Watch just randomly disconnects, bluetooth connection needs to be manually started again. Tried reinstalling apps, restarting watch, a2dp, turning off miui optimalization, and still nothing.
Everything was working fine on android 12. Now the lifetime of my active2 watch is down from 3 days, to maybe 1,5 days.
Anybody has any ideas? I am considering downgrading to android 12, cause it's so bad.
Thanks!
Click to expand...
Click to collapse
Yeah I am also considering downgrading it to Android 12
teji007 said:
Yeah I am also considering downgrading it to Android 12
Click to expand...
Click to collapse
I performed a phone factory reset and everything started working again. Lost all my data, but watch works fine now. So yeah, great update.
ccclcccv said:
I performed a phone factory reset and everything started working again. Lost all my data, but watch works fine now. So yeah, great update.
Click to expand...
Click to collapse
Bro I followed youe steps, but I am still facing same issue. Even after factory reset galaxy warch is still not connecting and getting interrupted connection.
SOLVED: enable auto start from app manage for both:
1-galaxy watch plugin
2-galaxy wearable
teji007 said:
I am using Galaxy Wearable with Galaxy Plugin for Samsung Galaxy watch classic.
After MIUI 14 update its not keeping Bluetooth connectivity properly, its getting disconnected after few seconds.
I have uninstalled whole software and reconnected watch but issue still exists.
Help!
Click to expand...
Click to collapse
SOLVED: enable auto start from app manage for both:
1-galaxy watch plugin
2-galaxy wearable