Yesterday I got my brand new Nexus 5x and I was extremely pleased with my new phone. It arrived 6.0.1 so after applying all the security fixes I tested everything on the phone to make sure it's working properly.
After that, I upgraded to N by flashing the factory images and restored my apps and data from my Nexus 4. Everything was working perfectly except for the heart rate monitor, the Polar H7.
The problem is that my 5x sees the sensor, but when I initiate the pairing process nothing happens. It just says Pairing... for a while and then nothing. I tried to tap it a few times and it just didn't want to pair.
What I tried to do:
1) Force stop the Bluetooth Share thingy and remove data/cache.
2) Reboot my phone
3) Try to pair the sensor directly from the fitness apps I use, Polar Beat and Runtastic Pro.
Polar Beat sees the sensor, but when I try to pair it, it either says sensor inactive or doesn't display my heart rate before dropping the connection.
Runtastic Pro can't even find the sensor. It has to be paired in the Bluetooth setting for it to work properly.
4) Factory reset the sensor as I found on the Polar's troubleshooting page.
5) Factory reset my phone and try to pair the sensor before restoring my apps and data.
The sensor works just fine on my Nexus 4. I paired the H7 again with it after the factory reset and it worked just fine. The battery is almost full and I do wear the sensor on the chest strap when I try to pair it with my phone.
I've seen a few threads on Nexus support forums where users mention Bluetooth connectivity issues and even a few mentioned their H7s not working on 5x and 6p after the update.
Anyone here ran into this problem and is there a solution? Other than to pray that Google fixes the issue.
I'm glad you are having the same issue, I was already starting to think my Polar device was broken. I'm also using a Nexus 5X with Nougat.
I have also logged this on the official Google Support forum:
https://productforums.google.com/forum/#!topic/nexus/EgBjK6mutb0;context-place=forum/nexus
I have the same Problem with my H7 from Polar. Went back to 6.0.1 and it's working again... Hope it gets fixed soon.
philz03 said:
I'm glad you are having the same issue, I was already starting to think my Polar device was broken. I'm also using a Nexus 5X with Nougat.
I have also logged this on the official Google Support forum:
https://productforums.google.com/forum/#!topic/nexus/EgBjK6mutb0;context-place=forum/nexus
Click to expand...
Click to collapse
I have reported the issues on the AOSP bug tracker. Some Google employees labeled the issue for DevPreview-N. Sadly no comments, but I hope this means they will sort this out with the next Android N update.
Same problem here, Nexus 5X, Android 7.0 with September security update. My Polar H7 was connecting just fine before upgrading to Nougat, cannot connect any more after upgrade. My wife's Polar H7 connects just fine with her Samsung, but does not connect to my Nexus 5X with Nougat.
i Have the Same Problem with H7 and Nexux 6P Nougat 7.0
Same issue over here on a Nexus 5x Build-Nr. NBD90W and Polar H7 as well as Polar V650 bike computer.
I still have NBD90S and it is pairing with the H7 and working with polar beat.
I have a custom recovery so I didn't grab the latest security update yet. Will update and let you know if it then fails.
Upgrading through the the beta program to 7.1.1 (NPF10C) solved the problem for me.
Hi Guys,
Same problem here, not able to pair the H7 on my N5X running PureNexus 7.0.
Very annoying.
So is the 7.1.1 beta the only solution found untill now?
Updating to Android 7.1.1 worked for me too. Yay.
Same here, all fine now
FYI: I have a Polar H7 that would no longer pair on my Nexus 6P on Nougat 7.1.2 nor would it pair on my Samsung Galaxy Tab S on Marshmallow. It would just hang on 'pairing' in the polar beat app and never complete the process on the latest polar beat APK (2.3?). I rolled the Polar Beat app back to 2.0.1 via an APK download and it paired with no problem, so try that if you're still having issues.
How ca I update the Android 7.1.1 to my Huawei P9
Related
Hi guys,
the moto 360 doesnt connects to my phone. I hope someone knows a solution for this problem.
My situation:
The phone is a Lenovo S920 with chinese firmware. It has android 4.4.2 Vibe UI 2.0 and i flashed gapps-micro. the latest version of play services, google search and android wear are installed. Everything works perfect.
The website from google with the wear compatibility check works.
Pairing with the watch works also but it doesnt stay connected, just for a few milliseconds.
With other phones the watch is working and the bluetooth from my phone works with other devices, like speakers or computer.
For me it sounds there is a problem with the bluetooth. Is there a opperntunity to fix this. I'm wearing the watch since two weeks without any functionality. Well, it just does what a watch does, telling me the time
I fixes it. After I installed new firmware on my phone android wear asked for a permission to use bluetooth. But after any disconnection the pop up displays again. It doesnt remember my choice.
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
wakers said:
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
Click to expand...
Click to collapse
It worked fine for me with KitKat.
Friday evening I upgraded to LolliPop. (Did a clean install, no data restore from backup)
Since then I have the same problem. Once you lose your Bluetooth connection it won't reconnect anymore.
You have to unpair and the repair in order to be connected again. A real pain in the ass, as I use it only for the notifications on the bracelet.
I have had a Vivosmart since the week they came out. I had a lot of the BT issues the first few months (mainly due to their software being released before it was really production ready) but has been fine since. I'm rooted and have ran a few different roms without an issue. Currently I'm using SkyDragon's Sense 7 rom. I haven't had to pair to my phone due to disconnects for at least a couple months. Are you pairing from with-in the Connect app? At one time the pairing was done via the regular android BT devices but they got rid of that and now pair from the app only. So technically your Vivosmart shouldn't ever show up on the list of installed/connected BT devices because it's only paired from the Connect app. I'm sure you've been on the garmin forum but if you haven't or someone else reading this hasn't it's here https://forums.garmin.com/forumdisplay.php?478-vivosmart. I've seen posts over there about m8 users having problems but don't remember reading if anyone was able to get the problem fixed and what they did. It doesn't make sense that it works for some (like me).
Hello,
I have same problem with Garmin Fenix 3. Apparently there is some bug in HTC ONE M8 Android 5.0.1
I am able to connect and connection is quite stable but watch wont reconnect automatically.
Usually it will reconnect once you reset BT on phone and than on watch. But its quite annoying so I am also looking for solutions. Any idea? Ive tried to add watch to trusted device under smart lock but its not working either. I know most Garmin devices worked on previous version of android on HTC ONE M8 but with Lollipop its bugged..
wakers said:
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
Click to expand...
Click to collapse
G'day wakers,
I have had exactly the same problem with my m8. I also have only used insertcoin rom which may be part of the problem as I have an identical m8 with stock lollipop (never unlocked or rooted) and it has no problems with the vivosmart or Garmin Fenix BLE connection.
I have since sold my m8 and traded up to an m9, which is still stock, but I'm reluctant to flash custom Rom as the Bluetooth works perfectly... On the other hand, stock roms drive me mental with bloatware and ads.
If you try another Rom I'd be very interested to hear how you go...as it may give me some confidence to unlock my brand new m9.
Cheers.
great_lumbuey said:
G'day wakers,
I have had exactly the same problem with my m8. I also have only used insertcoin rom which may be part of the problem as I have an identical m8 with stock lollipop (never unlocked or rooted) and it has no problems with the vivosmart or Garmin Fenix BLE connection.
I have since sold my m8 and traded up to an m9, which is still stock, but I'm reluctant to flash custom Rom as the Bluetooth works perfectly... On the other hand, stock roms drive me mental with bloatware and ads.
If you try another Rom I'd be very interested to hear how you go...as it may give me some confidence to unlock my brand new m9.
Cheers.
Click to expand...
Click to collapse
Cheers for the reply i might try a few different rom's i presumed that lollipop was the issue from what your saying maybe not then i'll let you know...
I have any M8 stock lollipop and vivosmart. When vivosmart go out of range lose connection. When vivosmart come Back near smartphone, if I want to connect it, i must switch off Bluetooth and switch on manually.
It is not auto.
Can you help me?
Thank you
Inviato dal mio HTC One_M8 utilizzando Tapatalk
I'm experiencing an even worst problem with no pairing at all with my fenix 3 and Garmin Connect with Cyanogenmod 12.1 .
I've done the test with a Samsung SII, Oneplus X and Oneplus One. All pairing fail and all with Cyanogenmod 12.1
It's working well with a Samsung Galaxy S5 ! So if one Cyanogenmod developper is reading this, can you please let us know if this bug is known, or if you can log it, and i can help some troubleshooting as well.
Samyterje said:
I'm experiencing an even worst problem with no pairing at all with my fenix 3 and Garmin Connect with Cyanogenmod 12.1 .
I've done the test with a Samsung SII, Oneplus X and Oneplus One. All pairing fail and all with Cyanogenmod 12.1
It's working well with a Samsung Galaxy S5 ! So if one Cyanogenmod developper is reading this, can you please let us know if this bug is known, or if you can log it, and i can help some troubleshooting as well.
Click to expand...
Click to collapse
Solution found on my side by realizing that one dialog box is not scaled in Garmin Connect and so the "yes" button is not visible in material design. I've understood this by rolling back to Cyanogenmod 11 and see the process.
Workaround is to use a language with shorter words like english. My initial set was in French. So if it can help somebody else with Garmin Connect, use it
Hoping someone can help shed some light. Googling didn't turn up anything. My S6 after the 5.1.1 update, bluetooth is borked. It is connected to my Sony Smartwatch 3, Gear 2 Neo, and was connected to my Fibit Charge HR and Microsoft band. The Fitbit Charge HR got a firmware update and then would not pair with my S6, but would pair with my work iPhone. So I thought it was defective. But it pairs with my old S5. So I went into bluetooth settings and did a scan and it will not see it. So, I stupidly unpaired my microsoft band and now it's now recognized at all. The SW3, G2 Neo are paired, as well as my Sync in my car, but show up in bluetooth as "Not Connected" even though they are. This is frustrating and I don't want to go back to my S5. Everything else seems to work okay - just the bluetooth. Anybody have any thoughts? I'm on the latest OTA, OFE.
SO no one's got any ideas. I have wiped cache both while normally running and by booting into recovery. Bluetooth still hosed. Would a factory reset help?
Saafir said:
@kbboykin Does your devics keep a bluetooth pairing history? If so delete it and try again. Have to do that with a lot of my devics
Click to expand...
Click to collapse
I don't think it does. See screenshot. All of these devices are paired and connected, but bluetooth says they are "Not Connected".
I got a Nokia Steel HR watch, which I was using with my Xiaomi MI5s and my Sony Tablet. Working all the way through - but with this Moto Z2 Play, it cannot be connected through bluetooth. When I want to connect to the device, it says that PIN is not accepted. When I do this with other phones, it asks for a PIN - this phone doesn't. Other bluetooth devices, e.g. my H&K Speaker, are working - but this watch isn't connectable. Any clue what this could be about? I did also reset network settings and wiped cache&data for the bluetooth app... no effect.
Same problem here. On Nokia support website it saids Motorola 2nd gen phone (which update to 6.0) have some issues and Nokia gives as solution to use another device ...
Moto z2 play has problem with bluetooth devices in general. I have problems with my bluetooth headphones and with the pokemon go plus, wich I was using without problems with my previous galaxy s7. It seems that the issues was solved for the moto z play (1st gen) with the november security patch update, but it is still present for the z2 play. They should solve the issue with android O, along with the cell standby battery drain. At least, I hope. No solution for now.
So this issue is just with Nokia products?
The problem is to connect Bluetooth on a Moto Z Play Android 7.1.1 patchlevel 2/2018 (current in reteu, was same result with Android 6.0.1 12/2016) with a Volvo XC40 car.
The first pairing with Bluetooth succeeds for a second. Then, nearly immediately, both displays (car and mobile) show reconnecting for about 10 seconds. It has a connect for a fraction of a second, and then is reconnecting and so on.
Trying flight mode and then only Bluetooth enabled on the mobile did not help. IIRC it showed some message about "My Volvo Carnull not bonded" (the name of the car for Bluetooth is "My Volvo Car" and some message with typo, something like "conecnting not successful". After that I rebooted, result was the state before with reconnecting.
Did try this several times. Also did try to reduce the amount of Bluetooth access types the car tries. There are 4 connected: phone, audio, internet, contacts. Did also not help.
Has anyone an idea how to get a successful connection or what the cause of the problem is? Did search for similar problems with Bluetooth in cars, but could not find anything (except for that hint with flight mode which did not help).
What I tried by now:
- Flight mode, only Bluetooth (as already mentioned). No change
- Remove all bluetooth connections. Pair new. No change
- Delete data for sytem app "Bluetooth Freigabe". No change
All other bluetooth connections are working fine. Another Moto Z Play using Android 7.0 (01/2017) is working flawlessly with that car. Strange for me is that it didn't work on 6.0.1 in the same way it does now fail on 7.1.1, but the other Moto Z Play using 7.0 is connecting stable.
Still the question: Does anyone have an idea how to get the connection working?
Factory reset?
I see that you deleted all bt connection but do you have some apps that are using bt? Like for smartwatch, headphones...?
I have Amazfit and watch must be connected to be able to pair a new device. Drow me crazy first time when I had that problem. I thought that car audio is broken, then phone... After pairing, watch doesn't have to be connected to reconnect.
Sent from my KFSUWI using Tapatalk
Zeljko1234 said:
Factory reset?
Click to expand...
Click to collapse
I was afraid this reply could come. When doing a factory reset, I do following: Pack /data/media somewhere because Nandroid omits this. Backup all partitions using twrp. Backup all apk using adb. Export SMS. Export contacts. Screenshots of the launcher screens. All this takes about 2-3 hours. Then I struggle a week until my device behaves like before. I'd be willing to do it if I saw a reason why it could help.
Zeljko1234 said:
I see that you deleted all bt connection but do you have some apps that are using bt? Like for smartwatch, headphones...?
Click to expand...
Click to collapse
Headphone, yes, there is August EP650 configuration tool that is not necessary. Thank you for the hint, will try it. Also I read somewhere it may help to delete cache partition, that's also worth a try before doing factory reset. Maybe I'll wait for Oreo before trying factory reset, could be they fixed some bug there.
Edit: BatOn which shows Bluetooth battery for external devices could also be the culprit.
Zeljko1234 said:
I have Amazfit and watch must be connected to be able to pair a new device. Drow me crazy first time when I had that problem. I thought that car audio is broken, then phone... After pairing, watch doesn't have to be connected to reconnect.
Click to expand...
Click to collapse
That's a strange behavior indeed. Amazfit seems to do something wrong.
It doesn't get any better if you upgrade to Oreo, I've been having problems with my Moto Z play disconnecting and reconnecting to the radio in my Corolla constantly ever since I went up to nougat. To be honest I just bought a good pair of headphones and stopped using the radio. Good luck though, if someone finds something that helps let me know.
I'm using bt with car audio, headphones, smartwatch... No problems at all, except one with Amazfit. And that is related to their bt implementation, not Moto fault.
Sent from my KFSUWI using Tapatalk
Seems the last action to remove Bluetooth related apps was the right one . There were two apps installed:
1. BatOn showing the state of battery of connected Bluetooth device
2. August configuration app for August EP650 headset
Removed both as they are usually not needed and it seems to work now. Will see later if it only worked for the short test I did today (currently I try to avoid driving because of an injury) or if it keeps stable.
Good, you didn't have to factory reset after all
Sent from my XT1635-02 using Tapatalk