Related
Hi team,
I am using Samsung Galaxy Note 3 Neo(SM-N750) INU(Indian version) running Android 4.4.2 Kitkat Stock ROM.
Currently my moto360 is not able to discover from Bluetooth but the watch is working fine with other phone.
This issue is occurred after I paired my pebble with the phone and installed pebble software.
I uninstalled and pebble software and rebooted the phone / watch many time and tried , no luck .
Tried reinstalling the moto connect and Android wear on phone.
I noticed both pebble and moto360 wont work together , there was an issue connecting pebble(watch not discovered from Bluetooth) when I first install the moto360. There moto360 work but not pebble now pebble is working but not moto360.
Can you guys help me how to resolve this ? I believe the phone factory reset will resolve but any alternate solution to this?
Currently I would like to connect my moto360 only and I really appreciate if you help on this & is any option to work both pebble and Android wear together?.
Regards,
Tintu Kuruvilla
Tintu Kuruvilla said:
Hi team,
I am using Samsung Galaxy Note 3 Neo(SM-N750) INU(Indian version) running Android 4.4.2 Kitkat Stock ROM.
Currently my moto360 is not able to discover from Bluetooth but the watch is working fine with other phone.
This issue is occurred after I paired my pebble with the phone and installed pebble software.
I uninstalled and pebble software and rebooted the phone / watch many time and tried , no luck .
Tried reinstalling the moto connect and Android wear on phone.
I noticed both pebble and moto360 wont work together , there was an issue connecting pebble(watch not discovered from Bluetooth) when I first install the moto360. There moto360 work but not pebble now pebble is working but not moto360.
Can you guys help me how to resolve this ? I believe the phone factory reset will resolve but any alternate solution to this?
Currently I would like to connect my moto360 only and I really appreciate if you help on this & is any option to work both pebble and Android wear together?.
Regards,
Tintu Kuruvilla
Click to expand...
Click to collapse
You should try to factory reset your watch, not your phone. Connect your watch like is brand new. Do the same with your pebble after everything is ok with moto.
Also you should delete cache and data from your pebble watch apk.
Hi Calinormy,
Thank you very much for your prompt support.
Now My Moto360 connected and working fine after the watch reset.
I tried a factory reset with my pebble and installed pebble app on my phone.
Now moto works fine but pebble is not able to discover.
I think both watches wont work together and I believe If i uninstall Android wear and moto connect from phone(clear the cache too) then probably pebble will work but not moto.
Anyhow this helps and many thanks to Calinormy.
Regards,
Tintu Kuruvilla
calinormy said:
You should try to factory reset your watch, not your phone. Connect your watch like is brand new. Do the same with your pebble after everything is ok with moto.
Also you should delete cache and data from your pebble watch apk.
Click to expand...
Click to collapse
After Android 5.0 upgrade my Note 3 has many bluetooth problems that stops me from using my smartwatches (Moto 360 and Pebble Time). Frequent dropped connection on bluetooth, both moto 360 and pebble can`t connect, i have problems with my car stereo, and sometimes when i push the back or home button on an app, nothing happens. Tried everything, wipe cache, phone reset, deleted cache from the Bluetooth and Bluetooth test app, factory reset the pebble and moto 360, no luck.
Android 5.0 is a big mess and i can`t use my bluetooth devices, that worked perfect on Android 4.4.4.
My phone is still in warranty, i have never done root on it, only installed stock updates, OTA, from Samsung.
I want now to downgrade back to Android 4.4.4 stock with ODIN. I want to download stock Android 4.4.4 for my Samsung Note 3 and flash it with ODIN. Can i do that?
Please help, Android 5.0 messed up my phone.
It's better to do a reset after every OTA update...
I personally feel the performance never goes down if I do a reset after update...
And I'm using my Moto 360 with my Aryamod Lollipop Note 3 (had no issues with stock Lollipop as well for 6 months)
Sent from my Nexus 7 using Tapatalk
I tried delete cache from Bluetooth and Bluetooth Test apps, factory reset from phone settings, reseted my watches Moto 360 and Pebble Time, deleted all paired bluetooth devices and paired again. Still connections are dropped, android wear says moto 360 is connected but watch is not, the same with Pebble drops connections, unable to connect, it ask for some bluetooth key, sometimes the pairing is gone by it self and i have to repair, etc., just a nightmare. Moto 360 and my car stereo worked perfect on Android 4.4. The Pebble Time is 3 days old, never worked fine on Android 5.0.
Now i did a full reset (wipe data) by restarting the phone into Recovery Mode. Contacted Samsung and i`m waiting for a reply.
I downloaded stock Android 4.4.2 from sammobile for my Note 3 LTE. If i can`t find a fix for bluetooth issues i will use ODIN and flash back the stock Android 4.4.2 ROM...
I can not believe that Samsung and Android will push out this update terrible. On the Pebble forums i see lots of users complaining about Android 5 ruined their bluetooth connections.
Just downgraded my Note 3 to Android 4.4.2 this morning. So far my Pebble Time works like a dream, no more dropped connection, no more unable cu connect, all bluetooth issues are gone.
Because i never rooted my Note 3 and downgraded to stock firmware, the downgrade process was pretty simple using ODIN, just uncheck F.reset.
great then!
Anturaju93 said:
Just downgraded my Note 3 to Android 4.4.2 this morning. So far my Pebble Time works like a dream, no more dropped connection, no more unable cu connect, all bluetooth issues are gone.
Because i never rooted my Note 3 and downgraded to stock firmware, the downgrade process was pretty simple using ODIN, just uncheck F.reset.
Click to expand...
Click to collapse
great then.. I believe there were no great features to miss Lollipop... other than the fact that Touchwiz looked better...
the biggest feature I would miss is Trusted device, so the Pebble can keep my phone unlocked and I don't need to type the PIN every time. Also S View cover issues are resolved with Android 5. So I am really not happy to downgrade. Did anybody receive any official statement from Pebble or Samsung where is the problem and when we can expect it to be resolved? There are several threads around like
sammobile.com/forum/showthread.php?t=27542
or
forums.getpebble.com/discussion/26926/bluetooth-connectivity-issue-after-android-5-0-update
but no statement
I own two smartwatches, Motorola Moto 360 and Pebble Time, and both not working on Android 5.0, but are working fine on Android 4.4.2. This is not Pebble fault. I had problems even with my car stereo with Android 5.0 , and now, after downgrade, all are working fine. My Pebble is connected for 2 days now, with no disconnect
I do like Android 5.0 and i like to keep my devices up to date, but i need bluetooth connection to work with all my devices.
Anturaju93 said:
I own two smartwatches, Motorola Moto 360 and Pebble Time, and both not working on Android 5.0, but are working fine on Android 4.4.2. This is not Pebble fault. I had problems even with my car stereo with Android 5.0 , and now, after downgrade, all are working fine. My Pebble is connected for 2 days now, with no disconnect
I do like Android 5.0 and i like to keep my devices up to date, but i need bluetooth connection to work with all my devices.
Click to expand...
Click to collapse
hey i just want to knw which firmware 4.4.2 u flashed ? and did u use LTE on 4.4.2 rom .... ?
my note 3 model is SM-N9005 and is the LTE version. I did use the last firmware available here http://www.sammobile.com/firmwares/database/SM-N9005/ROM/
L POF3 sol ce BT problems for most users......
There was OTA update last days that has resolved the bluetooth problems! Connection to Pebble is now stable!
yeah, switched to iphone 6 now. Samsung said they don't care if my watch is not working, they guarantee connections only with gear devices.
Hi, I want to share with you a problem that I detected with the Galaxy S8 and the Huawei Watch 2.
During the configuration of Android Wear, is impossible to send Google Account from the S8 to the clock. I tried all ways, also delete the account and configure it later from the Android Wear prompt, but did not work and the clock don't receive the account.
The phone remains searching but never permit to select an account to send.
The clock works with other phones, so I think is a software bug in the S8 firmware, but if you know any solution I will thank you very much!!
Do anyone have the same problem?
Hi, same problem on my new Galaxy S8 and my old, but always very good, LG G Watch R !
My previus phone was a Galaxy S7, and I never had problems on Android Wear.
Now, on my S8, when I start Android Wear, he never display my watch, to select them (on connect screen) !
I can connect both trought Bluetooth, but with or without Blutooth connected Android Wear don't see my LG G Watch R
I tried restart phone and Watch, but without succes !
Does anyone have a solution ?
Same problem here with Huawei Watch (first one). Made a thread last week but no replies.
Annoying bug.
https://forum.xda-developers.com/galaxy-s8/help/problem-adding-android-wear-account-t3592974
Same issue with Android Wear and my Samsung S8+. I can pair my Fossil Q Marshal I Understand that Samsung makes watches but we as consumers should be able to pair non Samsung watches. Im going to send Samsung Tech Supoort an email. That is why Im Android and not Apple
Got 2.0 on my 2nd gen Moto 360 yesterday. Same issue.
Hi, I've been looking for a solution for this issue , and finally got it working again. You need te clean data from google app, google play services and android wear, then eliminate your google account from your phone, factory reset watch, and then when you are trying to pair it, it would ask for a google account, input your account and it will be working, hope it helps .
Just switched from Galaxy S7 to S9 and run into the issue with my LG Watch Urbane. Unfortunately cleaning data and removing the Google account temporarily didn't fix the issue for me. Annoying that a phone upgrade rendered the Smartwatch unusable. I have no real idea what to do now.
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Sent from my Nexus 6P using Tapatalk
glenb83 said:
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Click to expand...
Click to collapse
Hello,
Backup your data's and try to factory reset.
You can install a custom ROM, but I guess it doesn't fix drivers issues which are closed sources.
Otherwise you can downgrade to a 6.x stock firmware.
Option 1 and 3 needs you to unlock your bootloader. Backup important datas, unlocking bootloader wipe all datas!
Good luck...
glenb83 said:
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I suggest you fully wipe your phone and install the May Google image (N2G47O). There was a major BT rework introduced with 7.1.2 that fixed an issue just as you describe. I went 5-6 months without being able to connect with one of my cars (2014 Cadillac). When the 7.1.2 beta came out I did a fresh install and it immediately fixed the problem. BT has worked flawlessly since.
glenb83 said:
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You need a completely clean 7.1.2 install.
There is a setting somewhere (I don't know where) left over from previous OS version or app.
My phone was doing the exact same thing with my BMW, and only my BMW.
Clean install of 7.1.2 fixed the issue for me.
I wiped my 6P today hoping it would resolve my BT issues with my 2015 Toyota Highlander. No such luck, it still boots my Toyota in an endless loop until I disable the BT on the phone. The car works fine on my Samsung S3.
What is the process to do a Clean install of 7.1.2?
Since the previous two updates on my Verizon V20 were installed (VS99518A & VS99519A) running 7.0 , I have been having bluetooth issues where there are momentary pauses while connected to BT earphones and random "rustling" sounds when I am connected to my car stereo (A2DP). There are even times the bluetooth does not reconnect (have to manually select the paired device at the pop-up).
I have already performed a factory reset and it still happens. These issues do not occur on other android phones so it can't be my stereo and bt earphones' at fault.
Any ideas? What should I check?
Thanks.
I really wish I could help you. Ive been having the same issues. Please follow up if you figure it out and I will as well
Same here
The 7.0 update took a while to get to me but now that it has, I'm not impressed and wish I could revert.
Immediately after I started noticing the same issues as OP. In addition, I can no longer BT FTP send to my desktop but I can receive from the desktop.
I've tried quite a number of things to resolve but none have. Several soft resets, hard reset, network reset, factory reset, reset of desktop settings (although apparently not needed a SIM-less Galaxy S4 does NOT have issues with BT FTP to the same desktop....
Attempting to pair the two, the S4 can see the V20 but the V20 does not recognize the S4.
I believe it is 7.0 update related because all was fine prior and the issues were noticed just 20 minutes after.