Hi there, is there any way to force S7 latestes nugat update to remember PIN code for Car Audio of mine?
It has no problem connecting to OBDII adapter remembering the PIN, but wont connect to Car Audio, i have to enter PIN manually every time i enter the car.
any solution?
Same problem here. No automatic connection. Pin input every time. Are we alone?
Looks like... sadly.
I have the same problem - 2016 Volkswagen. Sometimes the phone is remembered, but it asks me to pair 90% of the time. I have a Pixel XL
Of note: I also use Android auto - which I suspect could be the culprit. When I plug in via that connection, the Bluetooth connects without asking for a PIN, but then the phone invariably asks my permission to access messages. Why won't it remember?
No problems in my 2015 Chevy Silverado...
Mine works omn my cars and with my other paired devices.
Some devices I was able to add to smartlock and others I couldn't
Are you on stock rom?
Are you rooted?
I remember I faced this issue once on a previous smartphone because when I installed a custom rom I lost the IMEI.
IMEI corrupt will result in that bluetooth issue.
Hope not your case....
Any one found a solution to the issue maybe?
Did anyone find a resolution for this? I am having the exact same issue on my new S9+. It was working when I first purchased it then the phone updated and now it can't remember bluetooth pin numbers so everytime I get in the car I have to type in the pin code.
Thanks.
bowan.anderton said:
Did anyone find a resolution for this? I am having the exact same issue on my new S9+. It was working when I first purchased it then the phone updated and now it can't remember bluetooth pin numbers so everytime I get in the car I have to type in the pin code.
Thanks.
Click to expand...
Click to collapse
Are you rooted? If so, there's an issue with rooted S9+ not remembering bluetooth pairings after reboot. You have to download a Magisk module called libsecure_storage companion.
Related
I have a 2011 Jeep Grand Chreokee. When I first got the phone, it paired fine and I was able to make and receive calls through the BT. I had this setup for about 1-2 days. I then rooted the phone with the stock ROM only removing bloat ware...now I cannot connect via bluetooth back to the car. It seems to connect then disconnect me right away. Ideas?
I know this seems obvious but have you tried unpairing and repairing the phone to the car? Sometimes bluetooth can get fidgety and most of the time it requires you to repair the device. In my experience that generally solves the issues I have had with bluetooth.
Any time I have factory restored my phone I have had to repair it to any Bluetooth devices it was once connected to. Not sure if the Bluetooth address changes for the phone or not on a reset or ROM change, but it seems to be the case. My Infiniti G37s has Bluetooth and I experienced the same issue as you, pair it again and see if that helps.
Thanks for replies...I tried to repair about 6 different times...same result. It seem that the phone and audio connections both connect for about 2 seconds, then the phone disconnects.
Funny, I wanted to try this but kept forgetting. So I just went down to my garage and tried it, and it paired successfully on the first try. Tried making a call via number/phonebook and it all worked.
I'm rooted running Das BAMF 1.3, and paired it with a '11 Sonata Limited.
So I got it working...but without the phone book downloaded. The issue is in fact when it tries to download the phone book. Need to get another phone loaded up with my contacts and do a sync to get phone book loaded to car.
DieselvRR said:
So I got it working...but without the phone book downloaded. The issue is in fact when it tries to download the phone book. Need to get another phone loaded up with my contacts and do a sync to get phone book loaded to car.
Click to expand...
Click to collapse
Did you do anything to get it working?
When the device asked me to allow connection to download the phone book, I declined, only then would it pair properly.
I think I figured it out, I have the Infiniti G37, when I rooted & re-paired the Bluetooth, somehow I ignored the question when it popped up asking to "allow" or "deny" the connection.
Yesterday during the whole 4G fiasco, I reflashed & had to re do everything this morning, when I paired my BT, it asked me whether to allow & this time I clicked allow & my BT connects & stays connected fine now.
My question is, is there a way to delete the BT pairing on the phone without having to completely wipe the phone with a reflash?
ruddogg said:
I think I figured it out, I have the Infiniti G37, when I rooted & re-paired the Bluetooth, somehow I ignored the question when it popped up asking to "allow" or "deny" the connection.
Yesterday during the whole 4G fiasco, I reflashed & had to re do everything this morning, when I paired my BT, it asked me whether to allow & this time I clicked allow & my BT connects & stays connected fine now.
My question is, is there a way to delete the BT pairing on the phone without having to completely wipe the phone with a reflash?
Click to expand...
Click to collapse
nevermind, I just found the answer
http://support.vzw.com/clc/devices/knowledge_base.html?id=39262
just hold down "paired"
I believe the issue is just with the MyGig radio on the Chrysler products. I have a SRT8 Magnum with the MyGig and allowing it to download the address book "Breaks" the B.T. connection. I don't know what the issue is? Perhaps too much information being sent to the MyGig and it "locks up"?
I also have a Ford Focus for a daily driver and allowing it to download the Address Book over the phone has no such issue.
DieselvRR said:
When the device asked me to allow connection to download the phone book, I declined, only then would it pair properly.
Click to expand...
Click to collapse
It does it on my aftermarket Kenwood double-din unit, too. I've seen it happen on several Ford units too.
usafle said:
I believe the issue is just with the MyGig radio on the Chrysler products. I have a SRT8 Magnum with the MyGig and allowing it to download the address book "Breaks" the B.T. connection. I don't know what the issue is? Perhaps too much information being sent to the MyGig and it "locks up"?
I also have a Ford Focus for a daily driver and allowing it to download the Address Book over the phone has no such issue.
Click to expand...
Click to collapse
I updated my 430N radio with the latest firmware update and phone book downloaded and BT is working without getting disconnected.
Thanks
Thanks for that info. Although I can't do it as I have the "MyGig" retro-fitted into my 07 SRT. So, if I apply the "official update" I will lose GPS time and a bunch of other things.
But, nice to know it works.
DieselvRR said:
I updated my 430N radio with the latest firmware update and phone book downloaded and BT is working without getting disconnected.
Thanks
Click to expand...
Click to collapse
Hi,
Did somebody try to use an android auto function? My car (Peugeot 308SW 2018) and the phone not connecting with latest (8.1.0) android version. I tried to enable an USB debugging (as workaround recommendation), but nothing changed...
Have you other idea or working solution?
thx!
rawen69 said:
Hi,
Did somebody try to use an android auto function? My car (Peugeot 308SW 2018) and the phone not connecting with latest (8.1.0) android version. I tried to enable an USB debugging (as workaround recommendation), but nothing changed...
Have you other idea or working solution?
thx!
Click to expand...
Click to collapse
Yes, it works perfectly in my mid 2017 Kia Cee'd SW. Check if you have android auto enabled(i have the option to disable it and the apple car play). Also, the usb cable is working properly when connecting to a pc?
At the car side is enabled, at phone side i didnt found any additional options...
The best result was the android auto icon at phone appears and disappears continously with 2-3 different cables.
Is it possible the car head unit firmware not compatible with N7P latest SW version?
rawen69 said:
At the car side is enabled, at phone side i didnt found any additional options...
The best result was the android auto icon at phone appears and disappears continously with 2-3 different cables.
Is it possible the car head unit firmware not compatible with N7P latest SW version?
Click to expand...
Click to collapse
Doubt it. The car is from this year, it seems unlikely(to me) that the firmware wasn't up to date.
Stupid question, you have the android auto app installed on the phone right? Android has a Car Mode but to use android auto you need to install the app 1st(https://play.google.com/store/apps/details?id=com.google.android.projection.gearhead&hl=en). If the link says that you have no compatible device, download the latest version from here(https://www.apkmirror.com/apk/google-inc/android-auto/)
For almost a year I thought my head-unit wasn't up to date as the android auto would freeze, the app would say that the head-unit wasn't up to date, waze would display random artefacts, etc.
Now with the N7p it is butter smooth, no funky stuff and way more responsive that when I was trying to use it with my Redmi 4 Prime(same cable but with a micro-b to usb c adapter)...
No issues with AA in Seat Ateca 2018.
Everything works like a charm.
For phonecalls, you need to select default sim first, otherwise the call hangs on a sim selection prompt on the phone.
I write to nokia support and they send:
- clear the bluetooth cache
- do a soft reset
after this steps working fine...
what is Bluetooth cache?
Tequila.CZ said:
what is Bluetooth cache?
Click to expand...
Click to collapse
You found here, how to clear: http://support.hereplus.me/hc/en-us/articles/115003497328-Clearing-your-Bluetooth-Cache-Android-/
Do you install android auto app on your smartphone ? some lands doesn't have android auto on the play store, so you need to download manually on apk mirror web site (arm64 version)
A good quality cable is also needed.
I'm having similar issues.
This phone won't work in both my VW cars.
If I clear all settings it works fine.
I get to my destination, unplug and then when I head out on my next trip it doesn't. Just a blank screen on the head unit and the phone has the green screen saying launch Android Auto on the head unit.
Tried the BT cache clearing as above. Will try a factory reset of the phone shortly too otherwise wait for pie and if still no go then sell the phone which I will miss
Though can't work without Android Auto now
It is definitely problem with Nokia 7 plus. In my car it connect and after few minutes black screen and solution is only disconnect and connect again.
matonka007 said:
It is definitely problem with Nokia 7 plus. In my car it connect and after few minutes black screen and solution is only disconnect and connect again.
Click to expand...
Click to collapse
I've found the bluetooth with my N7P poor anyway. This is my second one and the same as the first.
All HMD will do is send you a list of the bluetooth protocols they support.
So you may need to change your car ?
My 7+ works perfectly now.
Enable USB debugging and disable the extreme power saving settings.
I have OP7 PRO running android 10 and stock Oxygen OS (not root).
When I pair my device to my car bluetooth set everything works fine, but once the connection is lost it will not auto-reconnect the next time i'm in my car.
Moreover, in order to connect again i need to do the pairing again (not just select the device from the existing devices list).
I saw tons of threads online about this with no solution, some mentioned they think it's an issue with android OS and not the phone itself (this is supported by the fact that my wife just got a new Xiaomi and have the exact same problem).
Does it make sense that this is a global Android issue and has no fix for such a long time? did anyone experience it and managed to fix it?
I would guess at an issue with the car Bluetooth. May be theres a firmware update for that ?
UrbanBushman said:
I would guess at an issue with the car Bluetooth. May be theres a firmware update for that ?
Click to expand...
Click to collapse
That was my first thought, but it seems that the issue is on the device side as i can see that after connecting the device doesn't appear in the previously connected devices list.
As if the phone forgets it for some reason.
I've had occasional problems too. I'm using Launcher 10. Just last week, I turned on my wifi before starting my car as usual. It connected, then disconnected 2 times and then was stable. There's been times where I'll restart my car to fix it. It's irritating but who knows what can be done about it.
I have a rooted stock op7pro and I have a Samsung active2 watch that randomly disconnects and reconnects once or twice an hour. I have battery set to all Samsung apps on my phone to not optimize battery usage and I have no idea why it does this.
Sent from my OnePlus7Pro using XDA Labs
I have understood that it's also possible that it depend on the order in wich you connect.
You should first have to connect the car to the phone instead of the phone to the car.
Iow have the car lookup the phone
Yes, i head a lot about people with flaky connection but i hope that was the situation, for me it won't reconnet 100% of the times.
Changing the order of connections didn't work.
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Turn off global power management completely in Device Care.
Network reset, reboot and clear system cache from the boot menu.
Ok, I've done a network reset, and cleared the cache partition. I checked Device Care for something like global power management, and I couldn't find anything. Most of the pwm settings are off except the "optomise daily" setting.
I'll let you know later if I have the same issue again.
These, this is a N10+ running on Pie.
To check if you have disabled global power go to Developer options>standby apps, all buckets should show as active otherwise power management is enable.
KindarConrath said:
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Click to expand...
Click to collapse
Are those the only three devices you connect via BT? What other apps do you use that need to use BT (i.e. Galaxy Wear, Apple Music, etc.).
You mentioned "Nordic Semiconductors Bluetooth App." I looked it up. Why do you need a third party generic BLE connecting app? It seems to me that could be the problem. You shouldn't need a third-party app to connect your BLE devices. The S22U's native pairing will work with any BT device that adheres to BT standards.
Try uninstalling the nRF Connect app and see what happens.
The only other Bluetooth devices I have are other in-house hardware, running on SiliconLabs BGM13P chips or NRF52840 chips...
The NRF app isn't a replacement for your bluetooth pairing app, its a debugging app... it can connect to BLE devices and show their GATT profiles, update devices that have Nordic's OTA update code and copy a devices GATT profile to act as a BLE Server.
We use it for testing and debugging.
KindarConrath said:
The only other Bluetooth devices I have are other in-house hardware, running on SiliconLabs BGM13P chips or NRF52840 chips...
The NRF app isn't a replacement for your bluetooth pairing app, its a debugging app... it can connect to BLE devices and show their GATT profiles, update devices that have Nordic's OTA update code and copy a devices GATT profile to act as a BLE Server.
We use it for testing and debugging.
Click to expand...
Click to collapse
Ok. I recommend uninstalling nRF Connect anyway. If anything, to rule out the app. How old is your car and the Raspberry Pi? Even though BT 5.2 is backwards compatible, sometimes older BT devices won't work with newer devices. That doesn't account for the S Pen issue though.
I uninstalled nRF connect, and changed all the settings you both recommended. Exactly the same behaviour when I went to leave work. My car stereo would do music but not calls, then when I restarted my phone, it worked. Then when I got home, my S Pen would not connect to my phone, then I restarted my phone and it worked.
Its not a problem of not being compatible, its a problem of something stops working.
Please also note that these devices worked fine together in the past. I am concered that it is either a change made by an update or a Bluetooth chip that is faulty....
OP- Have you debloated at all and if so maybe you've removed something relevant that might be causing these issues?
No, stock image, no OS modification beyond the things that Samsung offers (GoodLock and Stock customisation)
I have our in-house apps for interacting with our equipment (over Bluetooth) installed, but #1 they shouldn't affect anything if they are not open and #2 they don't do this to ANY of our other test equipment.
I would just like to say, that I appreciate the assistance that you are all offering! I have used many forums over the years when looking for support on things and I rarely find a place that is more ready to try and help than XDA forums!
KindarConrath said:
I have been experiencing issues connecting to devices over Bluetooth. Sometimes it just works, other times it doesn't work at all, and some times it kinda works but not right.
All of these issues are resolved by restarting the phone, but that isn't a solution because the issue comes back.
3 Devices I have been having issues with
1. S Pen - Sometimes it won't connect to the phone, I get an "S-Pen Missing" message and it will not connect. If I t ry to connect to it manually via nRF Connect (The Nordic Semiconductors Bluetooth App) it tells me that the BLE device has a GATT error. It happens semi-randomly but I can always make it happen by doing #2
2. Car Stereo - This is the weird one, it will connect and play music, but it will not do "calls" if I connect to Discord it won't recognise the car as a Bluetooth device it can route to.
3. Raspberry Pi - This one it appears it will connect to ONCE, and then after a disconnect it will not connect again.
Again, each of these can be fixed by restarting the device, but they happen again after a while. The pen & RPi use BLE, I don't know what the car uses for calls.
Click to expand...
Click to collapse
I've seen the issue of the spen disconnecting but only a couple of times and the issue worked itself out within a couple of minutes with me not having to do anything.
I've also have had a couple of wonky issues when connecting a new Samsung phone to my car. I've narrowed down my issue to the fact that when I transfer my data & settings via Samsung smart switch, it includes the details of my Bluetooth pairings. To fix it, I have to go in and delete my Bluetooth phone settings from the car and from my phone and re-pair them.
Rubby1025 said:
I've seen the issue of the spen disconnecting but only a couple of times and the issue worked itself out within a couple of minutes with me not having to do anything.
I've also have had a couple of wonky issues when connecting a new Samsung phone to my car. I've narrowed down my issue to the fact that when I transfer my data & settings via Samsung smart switch, it includes the details of my Bluetooth pairings. To fix it, I have to go in and delete my Bluetooth phone settings from the car and from my phone and re-pair them.
Click to expand...
Click to collapse
As cool as I think Smart-Switch is as a program, I actually never use it when moving from one phone to another. The junk that Google drags with me from one phone to the next is already too much, I like to use a new device as a chance to do some housecleaning. So no old-data oddities here.
KindarConrath said:
I uninstalled nRF connect, and changed all the settings you both recommended. Exactly the same behaviour when I went to leave work. My car stereo would do music but not calls, then when I restarted my phone, it worked. Then when I got home, my S Pen would not connect to my phone, then I restarted my phone and it worked.
Its not a problem of not being compatible, its a problem of something stops working.
Please also note that these devices worked fine together in the past. I am concered that it is either a change made by an update or a Bluetooth chip that is faulty....
Click to expand...
Click to collapse
Hmmm.. Ok. You're probably right about the suspect causes. I know there is a code you can dial to get into diagnostic mode, I just don't know what it is.
The only other option you can try (as a last resort) is to factory reset it. If it is update caused, a factory reset MAY fix it. If you take it to a service center, send it in for repairs, or do a warranty replacement, they're going to factory reset it, or have you reset it.
have you tried running diagnostics in device care ?
or check with this dc
android
Bluetooth test*#*#232331#*#*
samsung
Bluetooth Test Mode*#232331#
I still haven't done a factory reset, but I continue to have the issue.
I have run the BT Test in device care, it always reports good.
I tried the codes, neither of them work as the first one is for vanilla android and the second is for older versions of Samsung firmware.
I've tried completely unpairing from the car radio and re-pairing, disconnecting and connecting from the other device to no avail.
KindarConrath said:
I still haven't done a factory reset, but I continue to have the issue.
I have run the BT Test in device care, it always reports good.
I tried the codes, neither of them work as the first one is for vanilla android and the second is for older versions of Samsung firmware.
I've tried completely unpairing from the car radio and re-pairing, disconnecting and connecting from the other device to no avail.
Click to expand...
Click to collapse
I'm not entirely sold on the idea that it is a hardware fault. It could be a hardware limitation; meaning you cannot connect to more than a certain number of devices simultaneously. I don't know how many BT devices you can connect to at once. I know at least two simultaneous connections (I've only had two simultaneous connections at a time).
You said you have other BT devices in your house other than those three your having issues with. How many are there? How many are you connected to at any given moment?
Is it possible that you have too many simultaneous connections?
When you try to connect to your car.. Did you check under BT connection (your vehicle) to make sure both audio and calls are checked..
doubledragon5 said:
When you try to connect to your car.. Did you check under BT connection (your vehicle) to make sure both audio and calls are checked..
Click to expand...
Click to collapse
Yes, and I've disconnected, reconnected and even unpaired and re-paired the phone to the car.
gernerttl said:
I'm not entirely sold on the idea that it is a hardware fault. It could be a hardware limitation; meaning you cannot connect to more than a certain number of devices simultaneously. I don't know how many BT devices you can connect to at once. I know at least two simultaneous connections (I've only had two simultaneous connections at a time).
You said you have other BT devices in your house other than those three your having issues with. How many are there? How many are you connected to at any given moment?
Is it possible that you have too many simultaneous connections?
Click to expand...
Click to collapse
Unless having multiple connections causes the BT to fail completely, no. Even after turning the car off and walking away, it still will not connect to the S Pen. The only BT devices I use with that phone regularly are:
S Pen, Car (Music & Calls)
At work I develop devices that use Bluetooth and I sometimes connect to them, but only ever one at a time.
Hi guys, tried to use android auto today for the first time and having absolutely no luck. Either with wireless or a cable. Car says device not recognized. I've rebooted both, deleted all devices off the cars system etc and still nothing. The phone connectsvia Bluetooth and takes calls and plays music no issue but android auto won't connect. When I plug the phone in via USB it says device not supported?
I've Googled and it seems this is a common issue. Does anyone know of a fix or having similar issues? I'm rooted so wondering is that the issue or could there be a workaround as I'm rooted instead perhaps. All suggestions welcome, thanks!
Bxperiaz3 said:
tried to use android auto today for the first time and having absolutely no luck
Click to expand...
Click to collapse
I was able to connect using these actions:
Developer settings - wireless Android Auto