just got the Fitbit Charge HR watch, and I'm having some trouble syncing it to the Motorola Droid Razr device. When I go to my bluetooth settings on the phone, I see the Charge HR there, but when I select it, I get an error message saying that it cannot pair due to invalid PIN or Passkey even though I never entered one.
The only thing that I can think of is that i was near the wireless sync dongle that was plugged into the computer, so perhaps I need to either get out of range or disconnect that.
Anyone have any experiences?
thanks!
figured it out ( I think). the bluetooth version on JB 4.1.2 was not compatible with the watch. thus, I flashed the AOKP 4.4.4 ROM, and now it works fine.
Related
I have a weird problem with my SGSII. If i connect my phone to my car bluetooth with the car charger, it stay connected for as long as I am in the car. If however i connect to the car on battery, once the screen turns off I lose bluetooth connect. I have tried changing the screen time and that didn't work, I also tried making my bluetooth visable always and that also didn't work. Can't understand why it only happens while on battery.
Any suggestions?
I have the same issue with bluetooth on my SII.
Whenever the screen is asleep bluetooth devices will not connect, I have to turn the screen on to allow the devices to connect.
I've setup auto pairing in the linkkeys file which works fine if the screen is on (so no prompts to pair devices, just works).
The main device I want to use is a liveview, which I understand has problems, but I've tested other devices and the phone seems to be at fault.
It can't be designed that bluetooth will only connect if your using your phone, kinda defeats the purpose of most bt devices.
tried making my phone always visible, and even tried disabling the lock screens.
using CM7 stable, and a fix would be highly appreciated!
Hmmm.... I don't have that problem.
Maybe some weird power save option?
that's what I was thinking, but I've not been able to find any settings on the phone or through google.
I've just updated to the latest cm7 nightly and the problem seems to be the same. It has an addition bluetooth setting called 'Fast Connections' but this doesn't seem to change anything.
The only other thing I've noticed is that the linkkeys file that I edited to allow the liveview to auto pair (without me having to pull down the notification bar nad authorise it) seems to keep re-editing the file so the phone prompts to pair, so I'm assuming now that's the issue rather than a power thing, so how to prevent that?
Hello all,
Most of the time when I connect my Note to my MINI with MINI Connected (Nav, Pandora interface, Vehicle diagnostic interface, etc), it reboots the phone. It's not instant, sometimes the music will start playing, the car will confirm that the phone directory is updated, and I might even receive a message, but it usually reboots at some point. Once it reboots it usually is ok for the rest of the trip, even after disconnecting and leaving the car.
Yesterday, it started rebooting after disconnecting as well; once again, not every time...just did it yesterday at the mall and this morning when leaving my car for work.
This morning after it rebooted when leaving the car for work, I turned off the voice talk "Connect on Bluetooth" option to see if that does anything, but I thought I'd check to see if anyone has heard anything else.
Thanks!
Update:
So yesterday I rooted my Note and loaded Titanium backup and froze some services I thought might be causing issues. NOGO there.
I also repaired the phone as my primary (which syncs the phonebook) phone and with media audio. NOGO.
Next I repaired with just audio. NOGO
This morning I repaired as a secondary phone (no phonebook). So far so good. On the ride home today I'll pair as primary phone again and see if it stays.
I have a Cubot One, using the G800_CUBOT_D1_V0.8_20140124_MJK firmware (4.2.1) - it was previously on the 0.6 firmware and had the same issue.
What I have experienced is that when connecting to a device with Bluetooth - in this case a Sony SW2, but have also tried Bluetooth headsets - it has problems pairing.
The phone sees the BT device as an available device, and when I select it, it starts the pairing process. Initially it seems to be ok and successfully pairs for 2-5 seconds, the the device is relisted as an available device, but not connected. I have had success twice. The first time was immediately after rooted my phone, and this was ok for several days, even rebooting my phone and the watch didn't seem to cause the issue again, but then it randomly stopped working. I was unable to connect until flashing with the 0.8 ROM. At this point is was again working for about 24 hours - even better than before - until I switched the watch off. Since then I have been unsuccessful in pairing again.
Interestingly, when I try to pair with my Galaxy Tab 2 I have the same problem, UNLESS I initiate the connection with the tablet, then it is fine.
I know that there were problems with the Bluetooth stack on 4.2.1 when it first came out, and it may be related to that, but can anyone offer suggestions as to what else I can try?
Anyone having problems with constant disconnects with android auto?
I have latest UK firmware installed along with the latest android auto and waze on my phone.
I can connect fine , sometimes I can drive 30 minutes without a disconnect, other times it is 5 minutes.
The only way I can get it working again is if I unplug the phone from the car and reconnect.
Then this happens again.
I have not made a journey yet where the phone has not disconnected at least once.
My old phone (nokia 8) never had this problem.
Im using a good quality USB cable.
Any ideas of which settings I need to change to help this issue?
Try using the phone manager app's battery settings to set Android Auto and Waze to manage manually as to me it seems that the battery management's the issue.
Sent from my Mate 20 Pro using Tapatalk
Works fine for me, using Waze/Spotify most of the time. Using default battery optimization for Android auto.
I'm using a Huawei cable.
You could try to the one coming with the phone to test.
Hi ,
Thanks for the replies.
Im using the cable that came with the phone in my car and it still has the same problem.
I changed the settings to manage manually, but again I plugged the phone in to my car and it stopped working after 5 minutes. I had to unplug and start again before the car would see the phone again.
There are 3 sets of settings in the manage manually option. did you change any of these?
Should say that im plugging into a vauxhall Astra 2017 car with the latest software installed on my car.
Thanks again for any help.
I've only had my UK Mate 20 Pro for about 3 weeks now, but I too am having issues with Android Auto. Initially I was getting disconnects, I think this was due to the handset trying to ask me how I wanted the USB connection to be treated - charge only, transfer files, MIDI device etc. It didn't seem to matter what I chose, it always flicked back to charge only. Or, it could have been down to the third party always-on-display app(s) that I was trialling and have since deleted.
The disconnects now seem to have stopped and it's more stable for me - I don't know why, it could due to the above deletions or a recent EMUI update (I'm on 9.0.0.210), or maybe Android Auto updated?
I now have different issues with AA, in that when I connect the handset and the Android Auto home screen comes up, there's no play button showing for my Audiobook app (Listen Audiobook Player), when I click into the app and click the play button it stays on 'getting your selection' forever and nothing plays. Incidentally I can start playing a book on my handset, but AA doesn't notice that anything's changed and stays on the 'getting your selection' screen.
The only way I have found to return functionality to normal is to restart the phone and enter my pass code - this takes me back to the phone desktop and a different error message which says 'android auto can't find any supported devices to use' (or something similar), when I unplug and re-plug all works as it should again - this is all a bit of a pain to do whilst driving, or requires me to park up.
Additionally I have noticed similar issues when switching audio apps i.e. to Spotify and then to an audiobook etc., It doesn't seem to go smoothly like it used to on my S8+
I'm using a 2017 Vauxhall Astra also ?
Ive sent a message to customer services to see if they can offer any help.
Dont know if we will have to wait for a firmware update to sort this out?
Same every single time. Did a 120 mile trip today and had to disconnect and reconnect 7 times
andywright1982 said:
Same every single time. Did a 120 mile trip today and had to disconnect and reconnect 7 times
Click to expand...
Click to collapse
Do an factory reset and try it again. See if it works.
Verstuurd vanaf mijn LYA-L29 met Tapatalk
Hi, Can you all please share the model of your car ? Maybe the issue is also connected to the car, not only the M20Pro. Thank you.
My car is a vauxhall astra.
I know it is not the car at fault as my last phone which was a Nokia 8 running android pie worked fine without any disconnections.
pau1777 said:
My car is a vauxhall astra.
I know it is not the car at fault as my last phone which was a Nokia 8 running android pie worked fine without any disconnections.
Click to expand...
Click to collapse
Same car. Used a samsung a9 yesterday and worked flawlessly.
Done a factory reset on the mate and still ****s up. If it wasnt such a good camera I would be getting a different phone
I tried it on a Mercedes CLS, just for a short run. It worked fine. With non-official Huawei Cable. Just basic USB-C. Maybe I need to try for a long run to be sure about it.
Anyone tried it on a Volvo XC40-60-90 ?
Disconnects
Did you find a solution to this? my device also suffers from constant disconnects and sets the USB method to charge only and as soon as you change it just goes straight back. battery management is set to manual and all apps and phone are up to date. using it on a Vauxhall insignia 66 plate with OEM cable.
Hey guys,
The problem seems to be with a nearly full battery.
When the battery is >=92% the connection of AA drops very often.
Is anyone here with EMUI 10 to test if it's more stable?
EDIT: I've missed that today is the launch of the beta so forget my question.
Edit2: some links for the same topic.
https://support.google.com/androidauto/thread/15209528?hl=en
https://www.android-hilfe.de/forum/android-auto.3315/android-auto-verbindungsprobleme-bei-akku-ladung-ueber-90.920529.html
My p6 will see most some of my Bluetooth devices (laptop, tablet, TV, earbuds) . It pairs with the earbuds, but everything else it will try and pair, usually does not. If and when hen it does pair, that pairing is dropped dropped within 5 secs. Cleared BT cache, rebooted. No joy. It will show no paired devices.
Network reset.
Clear system cache.
Hard reboot.
Do not factory reset; find to root cause as it will likely reoccur otherwise, eventually.
It may be a 3rd party app, try in safe mode.
Try rolling back associated apks to their factory load versions if updated.
Double check permissions and settings.
blackhawk said:
Network reset.
Clear system cache.
Hard reboot.
Do not factory reset; find to root cause as it will likely reoccur otherwise, eventually.
It may be a 3rd party app, try in safe mode.
Try rolling back associated apks to their factory load versions if updated.
Double check permissions and settings.
Click to expand...
Click to collapse
Thanks. Tried everything but the "roll back " . It will remain paired with ear buds and car, but laptop, desktop,tablet and phone all disconnect immediately
Tool Belt said:
Thanks. Tried everything but the "roll back " . It will remain paired with ear buds and car, but laptop, desktop,tablet and phone all disconnect immediately
Click to expand...
Click to collapse
You play with bt settings in Developer options?
Is power management active? This doesn't fit power management's profile for erratic behavior but maybe it got "smarter".
Played with BT in developer. I will give power a try, but I don't understand why the buds and car are seemingly 0k. I haven't the chance to be in the car for an extended period.
Tool Belt said:
Played with BT in developer. I will give power a try, but I don't understand why the buds and car are seemingly 0k. I haven't the chance to be in the car for an extended period.
Click to expand...
Click to collapse
Think about the clues.
Are the other devices configured properly?
Check Event Viewer in Windows for error messages, it might tell you why this is happening.
Try some Google searches for similar issues, it can be other devices and OS versions. Many issues span both. With a newer device this strategy works many times.
To see if power management is active Developer options>standby apps, all buckets should show as active, otherwise power management is running. It can't be disabled here though.
Power checks out. I tried to send a file from the tablet. Phone showed the attachment, file failed. Was able to send a file to tablet using "nearby device"
Tool Belt said:
Power checks out. I tried to send a file from the tablet. Phone showed the attachment, file failed. Was able to send a file to tablet using "nearby device"
Click to expand...
Click to collapse
Do it to the PC and see what error messages Event Viewer shows.
Sent file from lap top to P6. P6 paired and accepted. Closed send window on LT and P6 dropped connection. Sent another file and did not click finish on LT and P6 remains connected and LT acts as trusted device for Smart Lock. The purpose here is not having to get frustrated with the FP sensor while at home. Using Trusted Location enables an area with nearly a half mile radius
It's not just bluetooth, it has to do with the Wifi+Bluetooth implementation. You can reliably crash System Settings after a factory reset if you type a wifi password wrong on the same network more than once, or if you attempt to connect to the same network with an incorrect password too many times. Attached "proof" (not really proof but). Once it crashes it'll restart setup but won't let you continue past Network Setup.
I could not get my Android Wear watch (Fossil Gen4) to connect. It was seen once and tried to but the bluetooth stack crashed. Even after a reboot, settings reset, forgot the device, and factory reset the watch it would not work.
My Pixel buds connected via fast pair and "worked", but the phone refused to identify them as Pixel Buds and I could not use the dedicated settings app. Same thing with my Galaxy Buds Live, the Samsung Wearable app would not find the buds even when connected.
MichRT said:
It's not just bluetooth, it has to do with the Wifi+Bluetooth implementation. You can reliably crash System Settings after a factory reset if you type a wifi password wrong on the same network more than once, or if you attempt to connect to the same network with an incorrect password too many times. Attached "proof" (not really proof but). Once it crashes it'll restart setup but won't let you continue past Network Setup.
I could not get my Android Wear watch (Fossil Gen4) to connect. It was seen once and tried to but the bluetooth stack crashed. Even after a reboot, settings reset, forgot the device, and factory reset the watch it would not work.
My Pixel buds connected via fast pair and "worked", but the phone refused to identify them as Pixel Buds and I could not use the dedicated settings app. Same thing with my Galaxy Buds Live, the Samsung Wearable app would not find the buds even when connected.
Click to expand...
Click to collapse
This sounds similar to my problems. Try and contact support (took 50 minutes for a call back) and get it into their system.
Tool Belt said:
This sounds similar to my problems. Try and contact support (took 50 minutes for a call back) and get it into their system.
Click to expand...
Click to collapse
I'm sorry you're dealing with it I've since factory reset the device and haven't tried crashing anything, so things seem to be working so far. I have an RMA P6 on the way already due to terrible screen tint issues on my phone. Took over 3hrs (1hr waiting for chat to be available, 1hr in line on chat, 1hr on chat)
I may try a reset when I am bored. Gr8 you have a new one coming