Database Users

Bluetooth not connectig automatically to the car kit

Hi guys,
I have a very strange problem with my beloved note. After I get in the car and drive off I remember that I have to turn bluetooth on so it can connect to the hands free system. The thing is that it doesn't connect automatically, I have to go into the settings and tap the BT name in order to connect it. If on the other hand if I have BT already enabled on the phone before starting the car, it conmects automatically. With the first version of GB the Note had in November I didn't have this issue, but after the first update it started not to work. Now I am on official unrooted ICS 4.0.3. Never had this problem with any other phone.... Any help would be highly appreciated.
Thanks.
Sent from my GT-N7000 using XDA

Anyone?
Sent from my GT-N7000 using XDA

n.vasiliu said:
Hi guys,
I have a very strange problem with my beloved note. After I get in the car and drive off I remember that I have to turn bluetooth on so it can connect to the hands free system. The thing is that it doesn't connect automatically, I have to go into the settings and tap the BT name in order to connect it. If on the other hand if I have BT already enabled on the phone before starting the car, it conmects automatically. With the first version of GB the Note had in November I didn't have this issue, but after the first update it started not to work. Now I am on official unrooted ICS 4.0.3. Never had this problem with any other phone.... Any help would be highly appreciated.
Click to expand...
Click to collapse
You can try Automatic Bluetooth Toggle PRO (I think there is trial version on Google Play). I don't know if it will help you. If not then I'm sorry you will probably have to go back to GB. I'm still on GB as I was also having issues with bluetooth on stock ICS (CM9-based ROMs worked well though).

Thanks a lot. GB had the same annoying problem though :-(... so it's not that....
Sent from my GT-N7000 using xda app-developers app

Hi,
Did you allow the pairing automatically between the devices?
When you pair at installation, it isn't permanently (= automatic) yet. When you get in your car and pair for a second time, normally your phone asks you if you allow your hands free system to access your phone; at that moment you have to tick "don't ask me again" and "yes" for automatic paring.
You might want to disassociate the two and try a new setup (pairing).
To disassociate, stop the system in your car (that cuts the BT connection between the two), disassociate on the phone (push and hold your hands free system in the BT section of the phone and chose disassociate), reboot your phone (so it forgets your cars BT system) and start pairing all over again.
I would provoke the second connection so you get the "automatic" question to make it work.
Good luck :good:

I have the same problem with the original ICS rom.
Flashing a custom ICS rom fixes this problem.
I tried kingdroid (worked ok)
I tried Cyanogen (phone ok, no media audio over BT but connection OK).

I had a similar problem after upgrade with stock ICS through software update. I couldn't pair Note with Mercedes bluetooth. Galaxy Note recognized Mercedes BT & vice versa, but connection was impossible. I read every forum on internet but no help. Everybody was blaming Samsung and ICS. Some suggested resseting Note to factory default, others downloading bluetooth app etc.
Until...I finally figured out that something was confusing my car's BT, so I resseted car system, and the problem was solved.
Sent from my GT-N7000 using xda app-developers app

These is a twist with "old" BT systems and ICS: Old BT systems want you to insert a pin code, ICS wants you to to confirm a code that the BT system sends and that ICS shows on the screen.
It's obvious that that ICS on an old system can be a hassle.
A work around is to put the car in discover mode (so it shows the pin code) and then send a contact (or a picture) from the phone to the car system. As the car replies, your phone will show the possibility to insert the PIN Code.
After that your system should work.
At second connection make the pairing automatic (as I described above) and you're happy.
(This is not my discovery, I found this solution on the SE XPeria Ray forum as I had problems with my wifes phone )

Thaks a lot. I will try as soon as I get the chance and will let you guys know.
Sent from my GT-N7000 using xda app-developers app

So with the workaround mentioned above - it doesn't work. When turning on bt on the phone it won't automatically connect to the car.
Sent from my GT-N7000 using xda app-developers app

Try A2DP Volume on the market.

I have the same problem as you. I used a leaked ics rom on my galaxy s2 and also had the same problem we now have on our ics galaxy notes. My car's head unit is a 3 year old eclipse cd5030. For the last month ive just been manually pairing it every time. PITA. Ill try the workaround suggested earlier in this thread and let you know. Otherwise i think cyanogen mod rom may work.
Sent from my GT-N7000 using Tapatalk 2

Let me know. I am.not going through the trouble of putting anoyher ROM on the phone.just for that
Sent from my GT-N7000 using xda app-developers app

n.vasiliu said:
Let me know. I am.not going through the trouble of putting anoyher ROM on the phone.just for that
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I had similar issues with Parrot 9200 kit in my car. Paired automatically under GB but on stock ICS wouldn't pair unprompted. Sometimes it would but only after minutes.
I'm on Paranoid Android 0.4 now which is CM9 based. It's better but often still slow to pair unprompted. Main improvement for me is that the phone doesn't carry on playing music through its own speaker, like it did on stock ICS, when I turn off the engine.

There is an app on the market called "Auto Connect 2.0", but it is only available for ICS and above Android versions

atiesfo the
i have same problem with my note, but with my Galaxy S1 works fine, when i upgrade the android to 4.0.4 solves the problem.

[Q] Polar H7 & 4.3

HI All,
My Nexus 4 was ota to 4.3 last night. This morning I have been trying to get my H7 to pair via bluetooth, given that both the Nexus 4 and H7 support Bluetooth Smart.
Has anyone managed to pair their H7's over bluetooth? If so what did you do and which app did you use.
I think that the H7 is working as it's sending a t31 signal to my polar f6 watch, so i'm assuming that the bluetooth is also switched on, however I no way to verify this, as i don't have another bluetooth smart receiver to check it with.
Thanks
Satpal

Polar H7 can get paired with android 4.3
schander said:
HI All,
My Nexus 4 was ota to 4.3 last night. This morning I have been trying to get my H7 to pair via bluetooth, given that both the Nexus 4 and H7 support Bluetooth Smart.
Has anyone managed to pair their H7's over bluetooth? If so what did you do and which app did you use.
I think that the H7 is working as it's sending a t31 signal to my polar f6 watch, so i'm assuming that the bluetooth is also switched on, however I no way to verify this, as i don't have another bluetooth smart receiver to check it with.
Thanks
Satpal
Click to expand...
Click to collapse
I just have tried it also without success. But just take the battery of the H7 short out and you will be able after inserting the battery to get paired. So hardware works fine now, but apps aren´t working yet: edemondo pro, runtastic pro. Does somebody have already an app that works?

Same here. I was able to pair after removing the H7 battery and inserting again but is not showing my heart rate.
Sent from my Nexus 4 using xda app-developers app

Same here!
My N4 is able to pair with the H7, but apps don't show my heart rate..

Hi,
I also tried this and my Nexus 4 was unable to find the H& in the BT pairing menu.
I realised yesterday that my wifes S3 also support BT smart, via smasungs own bt stack. I tried to pair via the normal BT menu but failed. However I download an app called NRF (by Nordic Semi) and managed to pair the device directly from there, so atleast i know that my H7 works. I guess it just matter of time before support is introduced by the various apps.
I wonder if manufacturers like Samsung will provide wrappers for the own BT Smart api's to conform with the Android API v18 (the one with BT Smart)
Thanks
Satpal

HI
i tried yesteday to connect the Polar H6 to the Nexus4 using Runtastic app. Didn´t had success i tried to reboot the phone and also released the battery of the polar sensor.
Do you know if there´s other software which i can use to pair them? Or how bluetoot smart pairing works in general?

I am also unable to pair my Bluetooth Smart heart rate monitor to my Nexus 4.
I am using a 60beat Blue and the device is not detected in either the Bluetooth settings menu or the Runtastic PRO V4.0 App.
When I try and connect to a app 'nRF HRM Demo' (the app 60beat support directed me too to test if the device worked) I get a message pop up "Bluetooth Low Energy isn't supported by your phone " Could other users try this app and let me know if they get the same message before I reply to 60beat?
I am running Android 4.3 (stock factory image and I am not rooted) JWR66V
I am waiting for a reply from Runtastic support to see if this device is compatible with their APP.
I do know my heart rate monitor uses the Transmission frequency of 2.4 GHz maybe this is the problem.
I will reply again once I receive a response from Runtastic as I requested a list of compatible hardware.
It does seem strange that I am unable to find much information about this new feature and how to test it.
FIngers crossed we will be able to definitive rundown of what works and does not work on both the Nexus 4 and Android 4.3

After having no luck getting a response out of Runtastic I have finally found an App in the store that reads my 60beat cheststrap (released today);
I am unable to post a link to the Play store but search for BLE Heart Rate Monitor
My device still does not show up in the setting menu but at least I know that 4.3 is working with BLE and it's Runtastic's fault that my monitor does not pair with it's APP.
I will reply again once I hear back from Runtastic with there response to this issue.
Let me know if anyone finds any other apps that work with their devices.

Dichdude said:
After having no luck getting a response out of Runtastic I have finally found an App in the store that reads my 60beat cheststrap (released today);
I am unable to post a link to the Play store but search for BLE Heart Rate Monitor
My device still does not show up in the setting menu but at least I know that 4.3 is working with BLE and it's Runtastic's fault that my monitor does not pair with it's APP.
I will reply again once I hear back from Runtastic with there response to this issue.
Let me know if anyone finds any other apps that work with their devices.
Click to expand...
Click to collapse
Thanks for that Info with BLE
Will try it also and report if its also working for me

Sirbubu said:
Thanks for that Info with BLE
Will try it also and report if its also working for me
Click to expand...
Click to collapse
Tested it out BLE is also working for me so its really a Runtastic issue.
I will also write them.

Sirbubu said:
Tested it out BLE is also working for me so its really a Runtastic issue.
I will also write them.
Click to expand...
Click to collapse
Got a response from Runtastic via Twitter;
"@Runtastic Why do you lock out the use of other BLE HRM from you Android Platform, I thought the point of BLE was for easy implementation?
@Dichdude From now we don't offer support for third-party hardware anymore. Thanks for understanding."
To sum it up Runtastic will only work with there own BLE heart rate monitor. I did reply asking them why and that it looks like a money grab but they have not responded to that question (suprise), so it looks like we will have to wait for other Dev's to implement Smart BT.

We just have to wait for developers to update their apps to be able to make use of BLE. The internal libraries don't yet support that protocol even though the phone does. I'm sure it won't be that long until apps updates start rolling out for the more popular apps. Unfortunetly there is only the one app (BLE HRM that a few have mentioned) that works. Considering 4.3 was released/announced less then 2 weeks ago, we should give the developers some time to get that update out before we start to fully complain.

Sirbubu said:
Tested it out BLE is also working for me so its really a Runtastic issue.
I will also write them.
Click to expand...
Click to collapse
I got an H7 today and downloaded BLE Heart Monitor. As soon as I started scanning I got it in the list of devices. I was able to connect and it seemed pretty accurate. However, I'm not able to connect again and it's not even detected as a device. I tried taking out the battery, re-booting the phone but nothing seems to work. Anything else I can try to get this to connect again with my Nexus 4?

Runtastic says they will only support their Runtastic-branded Bluetooth Smart HRM chest strap. I'm still waiting on Endomondo & RunKeeper to respond to my inquiries. The best thing to do is keep hounding them.

Confirmed working Polar h7 - at least in a basic app that was just updated today.
Sent from my Nexus 4 using Tapatalk 2

jawz101 said:
Confirmed working Polar h7 - at least in a basic app that was just updated today.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Just wondering, can you pair the h7 every time? I can do it once, get to the heart rate screen, see my heart rate but if I close the app it will no longer pair with the H7. It will show it in the list of devices but will hang on the "Connecting" screen. After this I have to clear the data for the app and take out the battery of the H7 to get them to pair again.
Sent from my Nexus 4 using xda app-developers app

I'll check when I get back home.

I tested for a little while tonight. Doesn't seem to handle a reboot nor temporary disconnection. I'd hope it would reconnect if I toggle the Bluetooth radio for a moment. In the event of temporary loss of signal I had to stop the app in android settings and once I restarted the app it would recognize the monitor once more.
My concern with all of that is my phone could reboot for whatever reason mid-run and I'd have to mess with whatever running app again. I'm usually listening to Stitcher radio and using whatever running app in places where phone signal isn't always great. That combination seems to cause my phone to restart on rare occasion which already annoys me so I'd expect reliability.

So I confirmed that turning Bluetooth off and on will resolve the connection issue, it's able to re-connect everytime. I did a ride today running both BLE Heart Monitor and RunKeeper and I had a stable connection throughout. At the end I just entered the average heart rate in RunKeeper. I really wish RunKeeper would release an update already or at least provide an ETA!

You're saying runkeeper saw it? Nm. I just read it

Bluetooth 4.0 (BLE) Support on the Note 3

Hi all,
After doing some research on BLE support for Android, I'm somewhat disappointed by the apparent lack of commitment on both Google and Samsung's part to get this sorted out properly, especially given the fact that they advertise BLE support on the product's packaging. By "properly" I mean the ability to find and pair with devices using the device's native Bluetooth Settings menu, not varying support from app to app. There seems to be a bit of information floating around for Nexus and Galaxy S3 devices, but none for the Note 3 - which prompted me to start this thread.
I have a BLE Heart Rate Monitor (Mio Alpha Pro strapless HRM watch) which I have been using to test functionality with my stock, unrooted Galaxy Note 3. Here is a summary of what I've discovered so far:
The Galaxy Note 3 does not find the HRM using the system Bluetooth scan feature,
Samsung's built in "S Health" app does not find/connect to the HRM.
The "BLE Heart Rate Monitor" app in the Play Store finds/connects to the watch fine and receives the HR signal, all without changing the Bluetooth icon's connection status in the notification bar.
Runtastic is the only fitness tracking app that finds and connects to the HRM, with no issue, straight from the app store. Endomondo, Runkeeper, MapMyRun etc have all failed to find and connect to the HRM
xda user dimfish has posted this thread in the Android Software and Hacking General forum, it's a mod that enables BLE conectivity for Fitbit (I am yet to test this, but replies suggest that is working on all 4.3 ROMs).
Given the fact that BLE connectivity works fine on Runtastic (and now Fitbit, with the mod), I am hopeful that native support for all hardware capable Android devices isn't too far away. In the meantime, please share what your thought's experiences are.
Cheers,
BT

bobbytod said:
Hi all,
After doing some research on BLE support for Android, I'm somewhat disappointed by the apparent lack of commitment on both Google and Samsung's part to get this sorted out properly, especially given the fact that they advertise BLE support on the product's packaging. By "properly" I mean the ability to find and pair with devices using the device's native Bluetooth Settings menu, not varying support from app to app. There seems to be a bit of information floating around for Nexus and Galaxy S3 devices, but none for the Note 3 - which prompted me to start this thread.
I have a BLE Heart Rate Monitor (Mio Alpha Pro strapless HRM watch) which I have been using to test functionality with my stock, unrooted Galaxy Note 3. Here is a summary of what I've discovered so far:
The Galaxy Note 3 does not find the HRM using the system Bluetooth scan feature,
Samsung's built in "S Health" app does not find/connect to the HRM.
The "BLE Heart Rate Monitor" app in the Play Store finds/connects to the watch fine and receives the HR signal, all without changing the Bluetooth icon's connection status in the notification bar.
Runtastic is the only fitness tracking app that finds and connects to the HRM, with no issue, straight from the app store. Endomondo, Runkeeper, MapMyRun etc have all failed to find and connect to the HRM
xda user dimfish has posted this thread in the Android Software and Hacking General forum, it's a mod that enables BLE conectivity for Fitbit (I am yet to test this, but replies suggest that is working on all 4.3 ROMs).
Given the fact that BLE connectivity works fine on Runtastic (and now Fitbit, with the mod), I am hopeful that native support for all hardware capable Android devices isn't too far away. In the meantime, please share what your thought's experiences are.
Cheers,
BT
Click to expand...
Click to collapse
up!
no news from app vendors in terms of adding BLE support. Don't much understand why it should be that difficult now that the android 4.3 OS does add support for it. So from the app standpoint it should be quite straight fwd!

It looks like Samsung is backing Ant+ rather than BLE somewhat.
The good news for us competitive cyclists that use Garmin products (Garmin owns Ant+), the Note 3 now ties-in with our heart rate monitors and power meters.
While I don't see me strapping the Note 3 to the handlebars, it can stay in my jersey and record the data.

peakjunkie said:
It looks like Samsung is backing Ant+ rather than BLE somewhat.
The good news for us competitive cyclists that use Garmin products (Garmin owns Ant+), the Note 3 now ties-in with our heart rate monitors and power meters.
While I don't see me strapping the Note 3 to the handlebars, it can stay in my jersey and record the data.
Click to expand...
Click to collapse
From a developer point of view, the ANT+ API is much, much simpler to implement than the BLE API. The ANT+ API already handles device discovery and decoding of data events from sensors into the useful data without even reading the Device Profile. You just request access to heart rate, cadence, etc, and then subscribe to the event handlers which pass the data to you decoded. The BLE API still requires a lot of work to do the decoding properly, handling characteristics, etc
BLE
http://developer.android.com/guide/topics/connectivity/bluetooth-le.html
ANT+
http://www.thisisant.com/APIassets/.../plugins/antplus/pcc/AntPlusHeartRatePcc.html

Any update
bobbytod said:
Hi all,
After doing some research on BLE support for Android, I'm somewhat disappointed by the apparent lack of commitment on both Google and Samsung's part to get this sorted out properly, especially given the fact that they advertise BLE support on the product's packaging. By "properly" I mean the ability to find and pair with devices using the device's native Bluetooth Settings menu, not varying support from app to app. There seems to be a bit of information floating around for Nexus and Galaxy S3 devices, but none for the Note 3 - which prompted me to start this thread.
I have a BLE Heart Rate Monitor (Mio Alpha Pro strapless HRM watch) which I have been using to test functionality with my stock, unrooted Galaxy Note 3. Here is a summary of what I've discovered so far:
The Galaxy Note 3 does not find the HRM using the system Bluetooth scan feature,
Samsung's built in "S Health" app does not find/connect to the HRM.
The "BLE Heart Rate Monitor" app in the Play Store finds/connects to the watch fine and receives the HR signal, all without changing the Bluetooth icon's connection status in the notification bar.
Runtastic is the only fitness tracking app that finds and connects to the HRM, with no issue, straight from the app store. Endomondo, Runkeeper, MapMyRun etc have all failed to find and connect to the HRM
xda user dimfish has posted this thread in the Android Software and Hacking General forum, it's a mod that enables BLE conectivity for Fitbit (I am yet to test this, but replies suggest that is working on all 4.3 ROMs).
Given the fact that BLE connectivity works fine on Runtastic (and now Fitbit, with the mod), I am hopeful that native support for all hardware capable Android devices isn't too far away. In the meantime, please share what your thought's experiences are.
Cheers,
BT
Click to expand...
Click to collapse
Hi BT,
Have you had any success in this since the post. Got the same gear you have and given Alpha MIO says the phone was supported i find this very dissappointing.

Hi mate,
It turns out support for the Alpha is down to application level. I am using it with the latest version of Endomondo and it works as it should. I believe Runtastic works as well, but anything else I can't speak for.
Good luck!
BT
andrewisinchina said:
Hi BT,
Have you had any success in this since the post. Got the same gear you have and given Alpha MIO says the phone was supported i find this very dissappointing.
Click to expand...
Click to collapse

Ignore... i found it, thanks
bobbytod said:
Hi mate,
It turns out support for the Alpha is down to application level. I am using it with the latest version of Endomondo and it works as it should. I believe Runtastic works as well, but anything else I can't speak for.
Good luck!
BT
Click to expand...
Click to collapse
Thanks, I have loaded BLE Heart Rate and can get that to work but was wanting something like MapMyRide as it autolinks to MyFitnessPal. Will take a look at Endomondo.
---------- Post added at 03:58 AM ---------- Previous post was at 03:36 AM ----------
andrewisinchina said:
Thanks, I have loaded BLE Heart Rate and can get that to work but was wanting something like MapMyRide as it autolinks to MyFitnessPal. Will take a look at Endomondo.
Click to expand...
Click to collapse
Hi BT,
Just went endomondo premium but cant get it to hook up the Note 3 and the watch? Do i still need to buy the premium app seperate from the premium account?
thanks for the help
Andrew

It Works
andrewisinchina said:
Ignore... i found it, thanks
Thanks, I have loaded BLE Heart Rate and can get that to work but was wanting something like MapMyRide as it autolinks to MyFitnessPal. Will take a look at Endomondo.
---------- Post added at 03:58 AM ---------- Previous post was at 03:36 AM ----------
Hi BT,
Just went endomondo premium but cant get it to hook up the Note 3 and the watch? Do i still need to buy the premium app seperate from the premium account?
thanks for the help
Andrew
Click to expand...
Click to collapse
UPDATE: I have Endomondo Premium, Linked with MyFitnessPal and this now works well. I have used it for the past 6 weeks no problem. You need to connect in the right order but this does work.
So, Myfitnesspal is linked to Endomondo Premium (needed for the Heart Rate Monitor)
On first application you need to ADD the Heart Rate Monitor in the Endomondo APP itself, with the Alpha in Workout mode. Make sure you turn WIFI off, on your phone for connection. After the first application the following works everytime
1. Alpha on, put into find heart rate
2. Turn WIFI Off and then Bluetooth on and GPS on (if tracking run or ride)
3. Ignore connection from Native Samsung connection
4. Go into Endomondo, after about 10 secs its then connects
5. Press to start workout mode on the alpha (Endomondo will still track the heart rate and zones even if you forget to put it in workout mode as the app is purely using the Alpha as a heart rate input device.
6. Press Go in Endomondo.
At the end of the training session, do the above in reverse order

U10 Uwatch bluetooth problem - assist req

Another U series watch from Uwatch. Supposed to be upgrade from U8. Seems to use same software/apk.
Watch was working fine initially after installing the apk (first day)...could make and receive calls...notifications...
phonebook, camera never worked with my galaxy note 2
Now, everytime the watch connects via bluetooth, it connects at first (with apk connected notification), but then I see the goodbye screen (for a split second), and the screen goes dark...I then push button to "wake" watch and it goes thru the bluetooth connection process again...and disconnects. Seems like once the watch connects and sees the apk, the watch does a mini reboot (not like full powercycle where you get the sounds of the shutdown and restart).
If I connect the watch without the apk, it doesn't do this. If I uninstall and reinstall the apk, this happens again. Any ideas?
Thanks in advance for any help!

Figured it out myself...with help of forums on the U8Pro.
Figured since the interfaces and watches are very similar...went to the U8Pro forum.
Unistalled the apk that the U10 has you install. Tried installing the bt.smartwatch (by rwatch) found on google play. Now works again. Still limited functions...but at least the notifications and receiving calls part works! Overall happy if this continues working for the price of about $55
philw007 said:
Another U series watch from Uwatch. Supposed to be upgrade from U8. Seems to use same software/apk.
Watch was working fine initially after installing the apk (first day)...could make and receive calls...notifications...
phonebook, camera never worked with my galaxy note 2
Now, everytime the watch connects via bluetooth, it connects at first (with apk connected notification), but then I see the goodbye screen (for a split second), and the screen goes dark...I then push button to "wake" watch and it goes thru the bluetooth connection process again...and disconnects. Seems like once the watch connects and sees the apk, the watch does a mini reboot (not like full powercycle where you get the sounds of the shutdown and restart).
If I connect the watch without the apk, it doesn't do this. If I uninstall and reinstall the apk, this happens again. Any ideas?
Thanks in advance for any help!
Click to expand...
Click to collapse

Can you please tell me where these forums are ? i can't seem to find the website of this company.
Also do you have the USB drivers for the PC? I just got one and i'm actually satisfied with it for the price i paid.

philw007 said:
Another U series watch from Uwatch. Supposed to be upgrade from U8. Seems to use same software/apk.
Watch was working fine initially after installing the apk (first day)...could make and receive calls...notifications...
phonebook, camera never worked with my galaxy note 2
Now, everytime the watch connects via bluetooth, it connects at first (with apk connected notification), but then I see the goodbye screen (for a split second), and the screen goes dark...I then push button to "wake" watch and it goes thru the bluetooth connection process again...and disconnects. Seems like once the watch connects and sees the apk, the watch does a mini reboot (not like full powercycle where you get the sounds of the shutdown and restart).
If I connect the watch without the apk, it doesn't do this. If I uninstall and reinstall the apk, this happens again. Any ideas?
Thanks in advance for any help!
Click to expand...
Click to collapse
You may want to try the U10 apk from the download ftp site. I've posted this to another U10 forum, "U10 U Watch Review - not a bad smartwatch". It's the latest version 7.1.3 of the apk and gives you the most features including camera with real time preview on watch screen - this feature is quite rare with other similar apps.

Hello. Could you give the link please. Thank you.

temium62 said:
Hello. Could you give the link please. Thank you.
Click to expand...
Click to collapse
Hi, it's post #49 on this page. I recommend you following this thread.
http://forum.xda-developers.com/sma...10-watch-review-bad-smartwatch-t2957239/page5

Thank you

GOLBSTAR said:
Hi, it's post #49 on this page. I recommend you following this thread.
http://forum.xda-developers.com/sma...10-watch-review-bad-smartwatch-t2957239/page5
Click to expand...
Click to collapse
Do you have a firmware for U10 that support Traditional Chinese (not Simplified Chinese) and English ?
If so, please post the link.
Many thanks in advance for your help.

Bluetooth blues

Hello all.
I am having some bluetooth connectivity problem with my moto g 4 US xt1625 Retus channel (non amazon version) stock everything.
Basically the connection to my smartwatch is unstable and keeps dropping on and off.
Normally I would be blaming the smartwatch for this BUT it connects absolutely perfectly to my moto G2 (cyanogenmod 14) without any hint of misbehavior
I've already tried;
Forgetting and re-pairing device (also rebooting phone before repairing)
Factory resetting watch
clearing app data and cache of system bluetooth apps ("bluetooth share" and "bluetooth MIDI")
Disabling 4G (sometimes interferes apparently)
Disabling wifi
Running phone in safe mode.
*edit - also tried disabling power optimisation for both system bluetooth apps AND the watch companion app
I also reconnected my smartwatch to my old moto G 2 after trying all these things and it still works perfectly.
Old moto G2 had blutooth 4.0 LE and this moto G4 has bluetooth 4.2 LE which would offer no comparability issues.
Has anyone had any similar problems with their bluetooth?
Thanks in advance

I think my next move will be to root, and start removing G apps that could be interfering with the bluetooth connection

hotdog18882 said:
I think my next move will be to root, and start removing G apps that could be interfering with the bluetooth connection
Click to expand...
Click to collapse
I have had a problem with my Fitbit connecting that didn't happen on my G2 or G3. I keep my cordless home phone connected with no problem though. What I have to do is forget the Fitbit in my bluetooth devices and it connects fine. If it's even showing up in the bluetooth devices it won't connect. That seems strange that it will only connect that way but others have reported the same thing. Maybe try and see if it connects after you forget it in the bluetooth settings and it's not even showing up.
Sent using XDA-Developers Mobile App

Tel864 said:
I have had a problem with my Fitbit connecting that didn't happen on my G2 or G3. I keep my cordless home phone connected with no problem though. What I have to do is forget the Fitbit in my bluetooth devices and it connects fine. If it's even showing up in the bluetooth devices it won't connect. That seems strange that it will only connect that way but others have reported the same thing. Maybe try and see if it connects after you forget it in the bluetooth settings and it's not even showing up.
Sent using XDA-Developers Mobile App
Click to expand...
Click to collapse
OK maybe you're on to something.
If I connect to the watch using the companion app, then enter bluetooth settings and "forget" the device..... It still appears to be connected
But a few seconds later, it automatically pairs and re-appears in the "paired devices" list.
Is there a way to prevent re-connect?

Actually, after "forgetting" it several times, It's staying connected and has done for a 15 minutes now.
I'll report back if and when it disconnects.
Cheers

Ok so the watch disconnected a couple of times in a few hours. (this is a huge improvement from before)
Each time, "forgetting" the watch in bluetooth settings caused an automatic re-pair and return to good connection.
Maybe I can use "tasker" or similar app to automate this unpair upon disconnect?
Cheers

hotdog18882 said:
Ok so the watch disconnected a couple of times in a few hours. (this is a huge improvement from before)
Each time, "forgetting" the watch in bluetooth settings caused an automatic re-pair and return to good connection.
Maybe I can use "tasker" or similar app to automate this unpair upon disconnect?
Cheers
Click to expand...
Click to collapse
Yeah, it's strange that it works that way. I think it's the device not compatible with that version Bluetooth. My Fitbit doesn't try to reconnect once I forget it unless I make it pair then it will actually work sometimes and sometimes it doesn't when paired. It always works if I don't pair it at all. Have you tried clicking on the gear besides your watch in more settings once it connects and unchecking what ever connectons it shows in the check boxes?

Tel864 said:
Yeah, it's strange that it works that way. I think it's the device not compatible with that version Bluetooth. My Fitbit doesn't try to reconnect once I forget it unless I make it pair then it will actually work sometimes and sometimes it doesn't when paired. It always works if I don't pair it at all. Have you tried clicking on the gear besides your watch in more settings once it connects and unchecking what ever connectons it shows in the check boxes?
Click to expand...
Click to collapse
If i click the gear next to the watch in the bluetooth settings, the only options i have are to rename the device, or to forget it
I have no checkboxes or anything like thar.
Do you have advanced bluetooth settings installed or something???

hotdog18882 said:
If i click the gear next to the watch in the bluetooth settings, the only options i have are to rename the device, or to forget it
I have no checkboxes or anything like thar.
Do you have advanced bluetooth settings installed or something???
Click to expand...
Click to collapse
Some of my devices have check boxes for contacts, audio, etc. but not all. I thought maybe that would be something to look at.
Sent using XDA-Developers Mobile App

Ok, its still messing around. I'm going to install the Temasek unofficial cyanogenmod 13 and see if that is an immediate fix, or if the additional options offers a fix.
Cheers

update;
after ugrading moto g4 to android nougat (7.0.1) I no longer have any issues with bluetooth connectivity.
6.0.1 was to blame!

my phone is updated to stock Nougat also and still having bluetooth issues staying connected to my car (2012 ford fusion with mysync) I will be keeping an eye on this thread.

vrm4 said:
my phone is updated to stock Nougat also and still having bluetooth issues staying connected to my car (2012 ford fusion with mysync) I will be keeping an eye on this thread.
Click to expand...
Click to collapse
I seldom connect my phone to mysync but my wife does. She also keeps her G4 connected to the Panasonic home phone system while home. I've noticed that since the update to Nougat mysync is very slow to connect on her phone. The Panasonic cordless phone seems to connect fine. Mysync will usually connect although she has to drive for 10 or 15 minutes before it does occasionally and other times it connects instantly. One time I had to delete her phone in the car and add it back. I wondered if it was a problem of it not disconnecting from the Panasonic, but that shouldn't be past the end of the driveway. Then again it may be just a rip in the space time continum. ?
Sent from my SM-T530NU using Tapatalk