Database Develop

Xperia Bluetooth problems :P

So I have an xperia, and I have a new JVC Bluetooth deck, I was so impressed how flawlessly it worked with my old phone the Kaiser/tilt, but to my surprise I have not been able to get it to properly pair up with my newer xperia. They will read each other and try to connect but I always end up getting an error. Sometimes it still shows up as connected but nothing works. I used my kaiser/tilt for both calls and streaming music through my new JVC bluetooth deck and I loved it, so its pretty dissapointing when I upgrade to what is/was one of the hottest & expensive windows mobile phones and it apparently has bluetooth issues.
I tried a few fixes already like changing the registry to read as a normal phone and I added in a missing bt profile, unfortunately nothings changed. I am curious tho because i had a magician and they had whole bt stacks that I messed around with, and I'm also wondering if a flash or two of a new rom may make a difference. Ocerall I'm really happy with the X1 (unlike my tilt/kaiser which had lots of problems) so much so that I don't really feel the need to flash a new rom, but if it might have a chance of fixing my bt I'm all for it.
Let me know if anyone has any suggestions, tia.

[ROM][30.09.2011]CM nightly + integrated external BT GPS] Android 2.3.7!

Guys,
I've implemented the external BT GPS for the CM7. Until now I only supplied a I9000 rom and source code. Since vibrant users with CM7 suffers from GPS performance (lack of it ;-) )
new build with android 2.3.7!
http://iloki.nl/2011/09/30/android-237/
Installation is the same procedure as the CM nightlies. Only rom file is different.
Howto install

cool will give it a shot

gekkekoe123 said:
Guys,
I've implemented the external BT GPS for the CM7. Until now I only supplied a I9000 rom and source code. Since vibrant users with CM7 suffers from GPS performance (lack of it ;-) )
I've decided to build a rom also for vibrant users. Give it a try: http://iloki.nl/2011/08/06/update-06-08-2011/
Beware, I'm uncertain if vibrant uses the same bootloader as the I9000. Changing bootloader isn't required for GPS support and is NOT recommended for vibrant users.
for more background information: http://forum.xda-developers.com/showthread.php?t=1170031
Please try to centralize feedback in the background topic.
Click to expand...
Click to collapse
Thank you! I love my Vibrant but GPS is a deal-breaker for me.
Sent from my HTC Glacier using XDA Premium App

This does not improve the internal GPS radio in any way. This just gives us a switch to enable a external Bluetooth GPS receiver natively without buggy 3rd party apps. This causes apps such as Google maps or navigation to be much more accurate due to the dedicated GPS receiver hardware. Using my GlobatSat BT-359 I have managed a app reported 0 accuracy and almost always below a 5 foot area. This pretty much makes the internal GPS cry like a newborn baby...
SkOrPn
Sent from my SGH-T959 using XDA App

so you'll need something extra for this to work?

On the download page, you will find step by step instructions on how to use it.
Basically, flash the rom, pair your gps mouse and just enable/disable GPS (using power widget for example).
But read the instructions at: http://iloki.nl/2011/08/06/update-06-08-2011/
it has screenshots and stuff
My rom basically gives you a switch to use our BT gps mouse as if it were your internal GPS. So you will get maximum compatibility , less battery drain and so on. Normally external receivers are way better than the ones that comes with your phone. My gps mouse is giving me 0.8m-2.0m accuracy for example. I was happy if I had 10m on my internal one. Most of the time I could get a lock (already tried soldering and so on).
To use my stuff the requirements are:
Galaxy S I9000/Vibrant -> binary builds. Other devices can be built from source.
NMEA 0813 capable GPS Mouse with Bluetooth Serial Port Profile (SPP)

gekkekoe123 said:
NMEA 0813 capable GPS Mouse with Bluetooth Serial Port Profile (SPP)
Click to expand...
Click to collapse
Does it matter what chipset is being used in the mouse? By the way, I call it a GPS Receiver, "mouse" sounds strange to me, lol....
My unit has the SiRF StarIII chip and is also NMEA 0183.
GPS Protocol Default: NMEA 0183 (Secondary: SiRF binary)
GPS Output Data: SiRF binary >> position, velocity, altitude, status and control
NMEA 0183 MEA0183 V2.2 protocol, and supports commands GGA, GSA, GSV, RMC, VTG, GLL v2.2 (VTG and GLL are optional)
GPS transfer rate: Software command setting (Default : 38400,n,8,1 for NMEA )
Connection: Communication with host platform via Bluetooth Serial Port Profile
Using the 3rd party app "Bluetooth GPS Provider" from the market, it lets me actually select my chip type, in this case SiRF. Does this even matter in this case?

Nope doesn't really matter as long as they output nmea sentences (I haven't seen one that didn't. But it doesn't hurt to check before buying).
I myself am using a MTK2 chipset.
btw: google GPS Mouse ;-)

gekkekoe123 said:
Nope doesn't really matter as long as they output nmea sentences (I haven't seen one that didn't. But it doesn't hurt to check before buying).
I myself am using a MTK2 chipset.
btw: google GPS Mouse ;-)
Click to expand...
Click to collapse
Yeah I already knew its called a mouse, I was just commenting that I do not like it. Its a GPS satelite receiver, or even a Wireless BT GPS puck would have been more appropriate I think... Come to think about it, mine is slightly smaller than a ice hockey puck but rectangled and very heavy for its size. I could easily play ice hockey with it, LOL....
Ok, so good NMEA support is all we need to worry about then. Most excellent...
EDIT: I hear MTK is better than SiRF, but not sure myself...

Synced with the low power mode patches.
new vibrant rom available.

This post is just asking for more clarity.. ..
gekkekoe123 said:
Guys,
I've implemented the external BT GPS for the CM7. Until now I only supplied a I9000 rom and source code. Since vibrant users with CM7 suffers from GPS performance (lack of it ;-) )
I've decided to build a rom also for vibrant users. Give it a try: http://iloki.nl/2011/08/06/update-06-08-2011/
Beware, I'm uncertain if vibrant uses the same bootloader as the I9000. Changing bootloader isn't required for GPS support and is NOT recommended for vibrant users.
for more background information: http://forum.xda-developers.com/showthread.php?t=1170031
Please try to centralize feedback in the background topic.
Click to expand...
Click to collapse
Thanks for your developments and this post, seems to have a great feature for the Vibrant users like my self, if I could understand your post....
External BT GPS...... If I had an external GPS, why would I use my phone....
External BT mouse . . . . this is not clear to me....
This post is just asking for more clarity.. ..

serendipityguy said:
Thanks for your developments and this post, seems to have a great feature for the Vibrant users like my self, if I could understand your post....
External BT GPS...... If I had an external GPS, why would I use my phone....
External BT mouse . . . . this is not clear to me....
This post is just asking for more clarity.. ..
Click to expand...
Click to collapse
He has enabled this phone to take advantage of the common GPS Pucks you see around the world. They do not have a screen of their own, all they do is have the high quality GPS chip like MTK or SiRF StarIII or something similar, and they have their own antenna and they connect via Bluetooth to computers, laptops and smartphones. Smartphones are given very cheaply made low quality GPS systems, but some people like myself included would prefer a much higher quality GPS result on their phone.
Advantages:
1. MUCH higher quality GPS accuracy down to 1 foot or less.
2. Uses less power since Bluetooth is MUCH more power efficient. I had my GPS on over 8 hours yesterday and when I went to bed I was still at 54% battery left, using the built in GPS system my phone would have died long long before then.
3. Lets people use their current GPS puck/mouse. Now I can use my GlobalSat BT-359 GPS mouse. My Samsungs built in GPS system is non-existant and has never worked properly. Now I finally have real GPS, so props to the OP.
This OP in my opinion was very very clear in the first place... You shouldnt roll your eyes or wink like you know what your talking about unless you truly know what your talking about. All you did was show how much you are lacking up stairs. Figured I get to now roll my eyes at your stupid post.
A GPS Mouse is a GPS unit made for smartphones and laptops and they DO NOT have a screen of their own, there are hundreds of them made and have been for many many years. This is what he is doing, letting us use these awesome Bluetooth GPS devices so we can have much more accuracy and bettery battery savings. I see no harm in this.
@the OP, thanks for your great efforts as this was long over due...

new vibrant build available http://iloki.nl/2011/08/24/update-24082011/

gekkekoe123 said:
new vibrant build available http://iloki.nl/2011/08/24/update-24082011/
Click to expand...
Click to collapse
The new Vibrant build still has flashing according to Skitz.... he broke it Im sure, lol....

Thanks SkOrPn for the explanation, this helped greatly.
SkOrPn said:
Click to expand...
Click to collapse
Thanks SkOrPn for the explanation, this helped greatly.

serendipityguy said:
Thanks SkOrPn for the explanation, this helped greatly.
Click to expand...
Click to collapse
Why certainly your most welcome....

I'm using this via Trigger - works BEAUTIFULLY on my BT 359 receiver. Although it was pretty confusing at first - after pairing initially it just said "paired but not connected" - needed to switch to the external first, then reboot, then turn on both BT and GPS (sometimes they turn on together in tandem, sometimes they don't..) before the light on the receiver indicated it was connected to the phone. And even then, it's still reported as not paired.
But that aside, this is ROCKING. I would tell you how accurate of locks I'm getting but GPS Test is freaking out (which seems to have been fixed and needs to be implemented in Trigger)
What are the odds of getting this into CM7 mainline?

strictlyrude27 said:
And even then, it's still reported as not paired.
What are the odds of getting this into CM7 mainline?
Click to expand...
Click to collapse
It reports itself as "Paired but not connected", not as not paired. I mentioned this somewhere else I think in the Trigger thread but now I cant find it. I believe it cant report itself as connected because it does not use a constant on connection similar to that of a BT Headset would. I believe the puck sends data at on/off intervals to short for the phone to display a connection. Just my theory though... My BT Headset on the other hand causes the phone to report as connected, but I think that's because its a constant connection, as obviously an on/off connection would be detrimental to transmitting voice... lol
I can't wait to get this in cm7 source myself, but I wont hold my breath. I wonder if there is anyone we can email to get this pushed along quicker?

Don't worry about paired but not connected message. The most important thing is that is it paired.
Connected is represented by the GPS icon.
flashing -> connected and waiting for fix, or temp lost a fix
solid -> connected and fix
none -> no connection.
Just pay attention to you gps icon and you should be fine. The connection should be there all the time, a fix can be lost temporary if you're going through a long tunnel.
It's generally best to first turn on gps and then enable it on your phone (handshake attempts are initiated from the phone). The first handshake attempt might failed otherwise and you have to wait a little bit for the retry. But eventually it will connect.

New vibrant rom is being build, should be up shortly.
This removes the reboot requirement when switching gps sources. Yes it means no more rebooting
http://iloki.nl/2011/09/08/reboot-requirement-removed/

Bluetooth Auto Connect

Hi,
I bought a Bluetooth Car Stereo. I've paired it and it pairs fine. When I connect it, it works great and IF I leave BT permanently on, it automatically connects when I sit in the car. If I disable bluetooth to conserve battery, upon re-enabling it, it DOES NOT automatically connect. Instead, I have to go Settings, Wireless, Bluetooth and press Connect manually.
Is there no way of making my phone automatically scan or check or whatever? I'm pretty sure my old Nokia could connect automatically, in fact I'll test now!
Thanks,
Joe

Anyone? Perhaps an app you can recommend?

Bluetooth Autoconnect (by WestOneTech) ... but it's not free ...

Okay. I flashed MIUI MintBerry Edition, and guess what? It allows automatic reconnecting on bluetooth enable. So I know for a fact this isn't some android limitation and it's definitely a setting or config of some sort in SGS firmware.
There has to be a way in which this can be fixed on a stock rooted ROM.
Any help would be smashing!

That happens to me with my samsung gt-s5560 witch is a rather crappy phone. I need to manually tell the phone to connect with my car, even if it's paired and set to auto permit.
On my SGS with ICS EliteRom 1.2, however, it works perfectly. Connects automatically whenever i have bluetooth on (either if it was on before being in range or if i connect while i'm in range).
Bluetooth works as handsfree for calls - from the car interface the phone allows to take and place calls, browse through recent and lost calls, phonebook (it even downloads it) and it even streams music to my car's speakers (using Google Music) with no additional configs.
It connects rather fast, like 3 or 4 seconds after turning BT on.

Exactly Kayn and that is why I can't understand why the stock room doesn't do this and more to the point why nobody has raised this issue before. I like the stock ROM. I genuinely do. I find it intuitive. So why can't it automatically connect to my car stereo when Bluetooth is switched on. This custom ROM has no problem doing it. I simply switch on Bluetooth and boom it connects. I need that functionality on the stock ROM if possible

Im going to flash the newest value pack tomorrow and see if that helps but I doubt it will. I genuinely believe this is an issue with the stock ROM. The only thing that might have caused it if the stock ROM does support it, is if I've removed something using TiBa but I very much doubt it. I didn't touch any core system components.

Haven't flashed the latest value pack but I've worked out how to make it work. Ridiculous on Samsungs part and I think they need to get their heads out of their arses and sort it.
If I activate Bluetooth before I turn on my car stereo, then it picks it up perfectly.
So if I turn on my car stereo and then switch on bluetooth... doesn't work.
If I turn on bluetooth then switch on my car stereo... works fine.
Absolute joke on Samsungs part that this glitch is the only way I can get it to work. I'll keep investigating and I'll eventually write a guide to help people with it.

skezza said:
Haven't flashed the latest value pack but I've worked out how to make it work. Ridiculous on Samsungs part and I think they need to get their heads out of their arses and sort it.
If I activate Bluetooth before I turn on my car stereo, then it picks it up perfectly.
So if I turn on my car stereo and then switch on bluetooth... doesn't work.
If I turn on bluetooth then switch on my car stereo... works fine.
Absolute joke on Samsungs part that this glitch is the only way I can get it to work. I'll keep investigating and I'll eventually write a guide to help people with it.
Click to expand...
Click to collapse
Makes us both but i can't really cope with the battery drainage when the phone's plugged during several hours (i use loads of battery intensive like torrent-downloading apps, radio streaming, etc and the phone needs to be plugged) so i had to make the change for some custom non-samsung based rom.
Samsung has loads of this minor quirks that make the experience that much less enjoyable. I only found solution in custom roms (very thankful to the devs for that!). Don't think they ever really cared about solving some under-the-hood issues (they did add some new features though) and even went as far as to pull the "flawed by design" apple-move.
I would still tell you to give a shot at customs, some out there are really good, but i can understand not wanting to change something we really like.
Good luck with that mate!

It's not that I don't like custom ROMs, I love custom ROMs but unfortunately, none of them have the Samsung Browser and let's be honest, everyone knows the best Android browser is the stock Samsung one. The browser that came with MIUI was very choppy and laggy.
I get decent battery life out of my stock ROM, but if I had to leave BT on permanently this would go down a lot! I suppose i just need to remember that as I get into my car, turn on BT and it'll connect first time.
Just crap that other Custom ROMs can search on enable and connect. Worst still, I can't believe we're the only ones who have this issue.

I never thought samsung browser was something that good, i hardly even see it being mentioned. I never really used it much since i have not used sammy's roms since ginger bread came out, but have you tried opera mobile? This is, by far, the best browser I've used, it's not even fair to compare - it's on a totally different league. I was actually losing hope of decent browsing (tried just about anything) on Android until i came across opera. Needs to be the mobile and not the mini. Faith in Android browsing restored
if you haven't, give it a shot, free on market. If that's the main reason not to use a custom rom, you may be changing your mind soon
Sent from my GT-I9000 using xda premium

I am having just the opposite issue, I have a bluetooth headset that auto connects every time it's in range if I want it to or not, I'm running a stock rooted room kitkat on an old Nexus 7

MTCB/MTCC Rom issues with ALPconnect app and Bluetooth

Hi Guys
Would really appreciate some help with this one, i am sure it been covered to some degree in other threads.
Since owning my unit I have wanted one application to run and I am not fussed about anything else, the app is ALPconnect.
ALPconnect is a application that connects to my radar detector via BT 4.0 only so it displays all the information on the dash for radar frequencies.
https://play.google.com/store/apps/details?id=com.alpriority.alpconnect&hl=en
Due to the limitations in the Bluetooth, no current rom has been able to allow the application to turn the BT on and search for the ALPconnnect Module
http://www.alpriority.com/product/alpconnect-bluetooth-module-gen2/
Over on the other forum i am apart of http://radarandlaserforum.com, one member has spent upwards of 2000$ buying android head-units to see if this app would run and connect on it.
our small thread is ongoing at @ http://radarandlaserforum.com/showt...-InCar-Enetertainment-unit-ALPconnect-Testing about this issue.
I don't normally ask for help, but I could really use some help and I am sure others on the forum that purchased it for that reason would greatly appreciate it too.
This is the last information I received from agentdr8, thank you aswell
agentdr8 said:
It's severely limited, when compared to any other Android device with BT. This is due to the OEM's choice of the BC5/BC6 module, and their poor BT implementation. Instead of routing BT audio traffic through the Android system, like a normal device would, they route it through the MCU. That would be fine on its own, except they route pretty much all BT interactions through the MCU, via serial AT commands, which is very non-standard. Simple things like pairing, or using SPP profile just don't work, or require a bit of finagling.
On top of that, there's code (at least in MTCB; dunno about newer MTCD) in MTCManager that filters which devices can pair via BT for OBD use. It checks the device name and if it starts with OBD, it will allow it to pass to the next step during pairing. I can only imagine they chose to do that so they could sell their companion BT OBD adapters with the headunits?
My XMTC module had accounted for this limitation in name-based filtering (apparently not the only limitation though; if your adapter was at least v1.4 it should work), but it hasn't been updated to work on any 2016 roms. Since I no longer have time to maintain that project, it's been open sourced on my github. The BT pieces could be extracted into their own module, but I thought I had read someone else (maybe MVG70?) had made a BT xposed module for these devices to try and address compatibility issues.
Click to expand...
Click to collapse

Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Sent from my iPhone using Tapatalk

shanetrainST said:
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Click to expand...
Click to collapse
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.

agentdr8 said:
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
Click to expand...
Click to collapse
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?

shanetrainST said:
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
Click to expand...
Click to collapse
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.

Guess the manufacturer is reluctant to release the source then.
Sent from my iPhone using Tapatalk

agentdr8 said:
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Click to expand...
Click to collapse
Just a couple of questions
1.Do you know if any developer is currently working injecting the drivers into the kernel, as impossible as it sounds.
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
3.Have any of the manufactures hinted at releasing the source and letting other developers fix the issue with custom roms
Just on another note
I have 30 emails from Eonon saying that their tech cannot do this and have assured me that.
We have our own brand and R&D department.
We use our software.
Click to expand...
Click to collapse
Which I don't believe for a second

I'm quite interested in getting this fixed as well - I have both an ODB2 adapter and Navdy that I'm unable to connect due to this limitation. And the fact that there's no available workaround via External BT is infuriating.
shanetrainST said:
Just a couple of questions
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
Click to expand...
Click to collapse
From my understanding, the only way to get this to work is through an external (USB) BT adapter, since the built-in BT stack sends everything through the MCU instead of directly to android. So enabling the proper USB drivers for BT in the Kernel would fix it. I'm not aware of any other USB devices that don't work (maybe gamepads or other HID devices, unconfirmed) so it seems they've cherry picked which USB devices to allow. Considering the otherwise hackable nature of these devices, it'd make sense to me to just enable all available USB devices and let us plug in whatever we want to plug in.

I'm in the same boat. I have an OBD adapter (Hondash) which refuses to pair. I've tried 2 Xposed modules which are supposed to sort this. I'm wondering if my particular issue is down to my 5.1.1 ROM so might try it on my old RK3066 4.4.4 HU which I gave to my Dad.
So I'm monitoring this thread in the hope a fix is found.

I am doubtful, I have contacted Klyde/Eonon/others and nobody is willing to release the kernel source code or address the issue.
So when someone gets a copy from Klyde/some reseller/MTC or whoever and a developer has the motivation to correct it, that can be the only solution.
I have given up hope on this one
Sent from my iPhone using Tapatalk

Does anyone know the location in the Android file system where the Bluetooth pairings are saved?

FINALLY! Someone with a similar issue. I've got a Valentine One, and the BT module for android, (connecting using YaV1) and I've been trying to get my android unit to pair with it as well. In for potential solutions.

This question may be off topic, and I apologize for that, but are you referring to the app not being able to turn on BT and look for the adapter; just getting stuck at "Turning on bluetooth..."?
I have an OBDII scanner which I can pair no problem. When I use a specific app (OBD Card Doctor Pro (or reg)) and attempt to connect it, I get a prompt letting me know that an app wants to turn on BT. I click allow and then it just sits there and never does anything. Is that the problem ALPconnect has?
Torque does not prompt me with this and initiates the BT connection just fine.

The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!

monza20vt said:
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
Click to expand...
Click to collapse
So this emulated effect is what causes my system get stuck "Turnning on bluetooth..." if I understand you correctly? There's no Android control over the BT hardware so the request is just lot in limbo?

Bluetooth Issues

Hi guys,
I'm experiencing some odd issues getting bluetooth to work on my BMW Series 5, 2011. I've already used multiple devices over time, including most iPhones, Xiaomi, Pixel 2XL, etc, without any issues. My Note 9 is able to find my car's bluetooth device and apparently connects just fine, however, after requesting a couple of permissions it seems to struggle to maintain connection and then seems to keep frequently connecting/disconnecting.
I've already tried using a different "AVRCP Version" under Developer options, but it doesn't seem to make any difference. This is my first Samsung device, are there any frequent issues I may not be familiar with?
SM-N960F - Exynos
No root - up to date software
Cheers

elmemyself said:
Hi guys,
I'm experiencing some odd issues getting bluetooth to work on my BMW Series 5, 2011. I've already used multiple devices over time, ...
Click to expand...
Click to collapse
Try to remove previously paired devices from your car, including this one and repair it.
You should leave the BT dev settings on their default as the phone is choosing the best based on the car's system.
Try also to go to Location's settings, improve location and disable always scanning of BT and Wifi.

mmuntean2 said:
Try to remove previously paired devices from your car, including this one and repair it.
You should leave the BT dev settings on their default as the phone is choosing the best based on the car's system.
Try also to go to Location's settings, improve location and disable always scanning of BT and Wifi.
Click to expand...
Click to collapse
Thank you, but unfortunately it didn't help. I even though it was due to being BT 5.0, but the Pixel 2 XL which I used before also had BT 5.0 and worked flawlessly. So weird

You might have to get a new car to go with the new phone

clone1008 said:
You might have to get a new car to go with the new phone
Click to expand...
Click to collapse
Don't be that person lol thats not helpful. I had these same issues when I owned the LG V20 and the only thing people did was mock my Bluetooth issues and told me to buy a new truck.

BigMosely said:
Don't be that person lol thats not helpful. I had these same issues when I owned the LG V20 and the only thing people did was mock my Bluetooth issues and told me to buy a new truck.
Click to expand...
Click to collapse
Lol... I'm sorry. If it makes you feel better I am having similar issues with my 2017 Audi A6. I have to constantly turn off my Bluetooth and turn it back on every time I get in my car to make it work.

I am having exactly the same issue with my 2011 330i. Connects then drops out. Phone says it is connected sometimes yet the signal strength icon on my car display flashes with no bars lit. I have unpaired and deleted the phone from the car but still will not work. I don't want to buy a new car either!!