I've been having problems with my car's parrot (mki9100) bluetooth. My Redmi Note 2 seems to pair fine with it, but then it just keeps connecting and disconnecting every few seconds. It doesn't share contacts, it doesn't work for calls and it doesn't work for a2dp. I've disabled permission management but the issue persists. I don't seem to be an isolated case as there are people complaining about this on MIUI's forums. I'm running 6.7.5 from en.miui.com.
I've tried the usual stuff, clearing cache/dalvik, even reinstalling the rom; nothing helped.
Any ideas on how to troubleshoot this?
kritonas said:
I've been having problems with my car's parrot (mki9100) bluetooth. My Redmi Note 2 seems to pair fine with it, but then it just keeps connecting and disconnecting every few seconds. It doesn't share contacts, it doesn't work for calls and it doesn't work for a2dp. I've disabled permission management but the issue persists. I don't seem to be an isolated case as there are people complaining about this on MIUI's forums. I'm running 6.7.5 from en.miui.com.
I've tried the usual stuff, clearing cache/dalvik, even reinstalling the rom; nothing helped.
Any ideas on how to troubleshoot this?
Click to expand...
Click to collapse
I was just about to start a thread myself then I saw your post.
Sadly I'm having trouble too. In my case stereo Bluetooth A2DP is awful. I'm constantly having skips and stutters on both devices I have tested so far (a Samsung HS3000 and a Logitech Boombox). I'm currently using the MIUI dev ROM from September 11th. If you're using MIUI 6 then clearly the problem spans numerous ROMs. Poop.
My problems happen regardless of whether or not I'm doing anything else on the device. It also doesn't seem to matter whether or not WiFi or data are enabled.
As a kind of aside, I also can't get my Moga Pro to connect in Mode A. It appears to pair OK but then just won't connect. Searching around for answers, this also something that at least the MiPad suffers from too (since last year!). Looks like Xiaomi has Bluetooth issues full stop.
I like this device, but some of its quirks of both hardware and software are making it more and more likely to end up on an auction site.
I can't wait for a more stock-like rom to be out.
This might be of help to someone: Someone suggested replacing the bluetooth app from /system/data with an older one (needs root).
I wasn't successful in replacing the app. Instructions here:
http://en.miui.com/thread-122323-3-1.html
kritonas said:
I can't wait for a more stock-like rom to be out.
This might be of help to someone: Someone suggested replacing the bluetooth app from /system/data with an older one (needs root).
I wasn't successful in replacing the app. Instructions here:
http://en.miui.com/thread-122323-3-1.html
Click to expand...
Click to collapse
Thanks for the link.
I tried it too on the developer ROM. It doesn't work (it breaks Bluetooth completely).
A2DP doesn't seem to stutter with music for me after the 17th/18th update. I've only tried a few songs. It's possible that the actual bitrate has decreased though. Apart from the stutters I'm sure it sounded better before. Maybe I'm imagining it.
Briefly tested 6.7.7 and it seems to work! Contacts synced for the first time, A2DP and calls worked. I'll let you know on the audio quality as soon as I have the chance to listen for a longer period of time.
Related
I can pair my phone with my car but 90% of the time I cannot hear the other caller and get a lot of distortion and hear myself echoing. The caller can hear me but not too well. A couple of times it worked ok. It seemed to work better when I had lite'ning rom installed, but due to an issue with car mode popping up randomly I have played around with various different roms. Now though my phone whilst pairing fine will just not work audio wise with my car. It is a 2010 BMW z4. BMW site lists the phone as compatible. I have searched high and low but the only problem I can find tends to be contacts not showing up etc. For me this is fine I just can't hear anyone when I make a call.
Is there something I can do with the phone to make it work? I found a root related bluetooth apk file remnaming thing but it didn't work.
Please help as this is driving (literally) me nuts.
Anyone got any ideas on this?
Ok, I investigated more. I have a program called Total Recall installed. It can be set to record all calls. On previous ROM's I think it occasionally crashed or got stopped when I closed stuff with task manager. On this ROM it seems to work constantly. This may be why my car Bluetooth used to work on occasions and not others.
I froze it with MyBackup Pro and voilà my car worked properly with the phone.
So I guess my next question is does anyone know anything about this program and why it would mess up car Bluetooth? If I can't get it to work can anyone recommend an alternative?
EDIT: Seems I can set it not to try and record if BT connected. Shame as that would be useful.
So, I'm having a strange issue with my new Note that I can't quite determine where the root cause may be, or if it's a known issue.
If I register my Note with my car as both a phone and an audio device (how the Infiniti nav/stereo works) I can use the Note as a phone fine UNLESS I start an audio app, such as Pandora. Once a2dp audio starts the Note will no longer connect as a phone device, but it works fine for audio.
I had the phone paired with the stock ATT rom but only used it as a phone, so unfortunately, without a restore to stock, I can't tell if the problem exists with the stock rom.
I flashed to flappjaxxx's rom (which I love) the same day I setup the phone to run Pandora via Bluetooth and that's when I started seeing the problem.
I also see some random connect/reconnects that seem a bit more than usual.
So, I can't say there's a correlation, or if this is a known ICS beta issue or what, but I'm hoping it is and that it's not a design flaw
Way I see it it's either:
1. Flashing to any ICS beta rom has the problem, currently?
2. It's in flappjaxxx's build (doubtful)
3. It's user error...(possible )
4. It's an app issue (ie. Pandora is causing the problem?)
Anyone have any thoughts, suggestions or insights? I've done some searching but haven't found this exact issue yet on any posts.
Thanks!
I have a Kenwood DNX9960 in my Avalanche. It connects also for phone and for streaming media. I can be streaming media from either the stock music player or an internet site like pandora or TuneIn and my calls will automatically come through. When the call ends it goes right back to streaming.
It autoconnects to both as long as my phone is in range when I turn on the kenwood. I did have an issue at first where it would not autoconnect. I deleted the pairing from both my phone and headunit. Then when I repaired I paid close attention to check any boxes to "Always" allow connection and I haven't had any issues since.
I understand the normal pairing process, I've had several phones before that worked fine prior to the Note. So, I'm thinking that it is probably a corrupt bluetooth db... I'm going to be reflashing to Flaps new rom and we'll see how that does
Is there a way to delete the pairing from the nav? I would try that
Sent from my SAMSUNG-SGH-I717 using xda premium
There is. I've tried it all, on both sides of the pairing.
I've reflashed the phone to the B6 from FJ, still no joy. The pairing db was new (so no chance of corruption on the phone) and the pairing deleted on the device.
It seems to be a problem with the phone switching between a2dp and phone bt. When a call comes in (while playing say Pandora over bt) the audio cuts out and then the car shows "disconnected" and then "connection failed" if trying to reconnect to the Note as a phone (ie hitting the phone button in the car).
I'm hoping it's the current ICS build. Just have no way to really know. Hoping some other folks will have seen the same issue.
Going to run some tests with different audio sources and see if the behavior is the same.
Well things seem to be working now, for no obvious reason I'll have to assume that the reflash resolved the issue, I just can't tell for sure why it didn't work immediately after. I think it's due to deleting the old pairing on the car and not shutting down the vehicle.
Cheers.
BT connections
I have similar problem connecting to van audio system (vauxhall). After some experimentation it appears to be an ICS problem, if I reflash my note with gingerbread I have seamless connections for both audio and phone. As soon as I upgrade even with offical ICS bluetooth connections become problematic, I can pair but not autoconnect. Tried samsung and they just "fob off" with it's an incompatable device. Until a bug fix is issued it appears as though it's a choic of staying with gingerbread and have a working system or ICS and no handsfree.
Hello,
I am having a problem where Touchwiz crashes after about half an hour to an hour of listening to Bluetooth audio through my car stereo.
The problem does not occur with the stock music player (or hasn't yet in the timeframes I've been testing it). However it occurs with pretty much any other player I've tried (thus far PlayerPro, Poweramp, and Audible). The symptoms are pretty much always the same. Audio works perfectly for quite a while, then it stops, phone kind of freezes for a couple of seconds, then Touchwiz resets. Often after it restarts I have trouble either connecting to or playing audio through Bluetooth. Sometimes that fixes itself, sometimes I have to do a full reboot.
I have had the device replaced in case it was a Bluetooth hardware issue but I'm having the same issue on the new handset. So far the issue is 100% reproducible.
It's an unrooted, stock phone running IMM76D.I9300XXALF2. I'm on Three UK. At this stage I am not planning to root the device. However if there was a clear reason why doing so might fix this issue then I might.
Has anyone experienced this issue?
If someone has time to have a look, I have managed to record an ADB log from the crash. I believe the crash happens at 20:29:36 - based on there being a lot of information about a Fatal Signal 11 at that point (although I did think that was just related to specific apps crashing), and then all the services die very soon after.
At some point, I will try with another Bluetooth stereo to see if it's specific to my current one. But I don't have any available, so was hoping someone might be able to help narrow things down in the meantime.
I've also gone to Samsung with the issue, and sent them the log, but who knows if they'll ever get back with anything useful.
Touchwiz crash with Bluetooth
Hi.
I have the same problem with an S2 LTE (not S3) from Rogers in Canada and a JVC radio except mine crashes after 30 minutes. It worked fine before upgrading from 2.3 to 4.0.4.
Model SGH-I727R
Version 4.0.4
Baseband version: I727RUXLF3
Kernel 3.0.8-perf-I727RUXLF3-CL611724 [email protected] #1. Compiled Sat Jun 9, 21:24:26 KST 2012
Build number: IMM76D.RUXLF3
When playing a podcast (BeyondPod) or audiobook (Audible) for 30 minutes, the phone freezes and a few seconds later the screen locks and all the status icons disappear. They all come back as if the phone just booted but it's not the long boot you would get if you powered off and on so it must be Touchwiz crashing. I also see a notice saying it's safe to remove my SDCard and then it re-mounts.
For me it is 30 minutes +/- 1 minute and it's consistent. If I shut off Bluetooth and immediately turn it back on after 25 minutes, I will have another 30 minutes without any problems.
I tried manually unmounting the SDCard while streaming over Bluetooth and it gracefully shut down the application and unmounted the card without any issues.
Others have had this issue too. Google for 'Issue 28006: ICS Bluetooth and Sony car headset'
I contacted Samsung support but so far they haven't helped. Their first response was to take it back to the carrier.
Have you find a solution for this? If not can you submit a support request with Samsung? If they get enough reports maybe they'll do something.
richjhart said:
Hello,
I am having a problem where Touchwiz crashes after about half an hour to an hour of listening to Bluetooth audio through my car stereo.
The problem does not occur with the stock music player (or hasn't yet in the timeframes I've been testing it). However it occurs with pretty much any other player I've tried (thus far PlayerPro, Poweramp, and Audible). The symptoms are pretty much always the same. Audio works perfectly for quite a while, then it stops, phone kind of freezes for a couple of seconds, then Touchwiz resets. Often after it restarts I have trouble either connecting to or playing audio through Bluetooth. Sometimes that fixes itself, sometimes I have to do a full reboot.
I have had the device replaced in case it was a Bluetooth hardware issue but I'm having the same issue on the new handset. So far the issue is 100% reproducible.
It's an unrooted, stock phone running IMM76D.I9300XXALF2. I'm on Three UK. At this stage I am not planning to root the device. However if there was a clear reason why doing so might fix this issue then I might.
Has anyone experienced this issue?
If someone has time to have a look, I have managed to record an ADB log from the crash. I believe the crash happens at 20:29:36 - based on there being a lot of information about a Fatal Signal 11 at that point (although I did think that was just related to specific apps crashing), and then all the services die very soon after.
At some point, I will try with another Bluetooth stereo to see if it's specific to my current one. But I don't have any available, so was hoping someone might be able to help narrow things down in the meantime.
I've also gone to Samsung with the issue, and sent them the log, but who knows if they'll ever get back with anything useful.
Click to expand...
Click to collapse
That's quite interesting. Mine is also a JVC stereo so I wonder if that's related. Mine could be exactly 30 minutes - I've not actually checked that. I will next time.
Out of interest, have you used PowerAmp before? The log I attached is from using PowerAmp, but since a recent update it actually seems to be fixed in that! But it still happens in Audible and other audio apps. I'd be interested to see if it works for you as well.
Samsung haven't been particularly helpful, other than saying they will look at the ADB log and release an update (for the SIII) if "it turns out to be a real issue" (which annoyed be, because it obviously is a real issue).
The Audible developers on the other hand are very interested and I have provided them quite a bit of info on the problem. I will pass them this thread too. I should try out the shutting off Bluetooth thing as a work around. Surprised I hadn't until now.
I haven't used PowerAmp but I did try the stock Android music player and it also crashed. I played a one hour podcast and after around 35 minutes it crashed as usual. At first I thought it was going to keep working as it's usually right around 30 minutes but it did eventually crash.
Did you report the problem to the PowerAmp author or was it just luck that the new version had a fix for it?
Samsung sent me an RMA shipping label. I have no plans on sending back my device for a software bug only to get back someone else's defective/fixed unit back with the same bug.
If this really is a bug in Touchwiz on ICS then we should ask others to test it in a general forum. I don't think this happens when playing music, only when playing one stream over 30 minutes. We need to find more people with a Samsung, ICS and bluetooth receiver to test..
That's very interesting information. I will try a single audio stream on the stock player and power amp. But it does happen for me with multiple streams in other apps (PlayerPro for example), but it could be related to how it plays them - perhaps it combines them into a single stream.
In fact, thinking about it, it could well be that. I don't think the previous version of PowerAmp showed the song title over Bluetooth, so it may have just combined multiple songs into a single stream as far as the Bluetooth stack was concerned. But now it does, so that might break the stream each song.
And I had not informed them about it, it was just luck. And they haven't responded to my queries regarding what they changed (which of course, may not matter).
I have already replaced mine (through Amazon), and of course the problem didn't change at all. Meaning it's the software (and perhaps the specific Bluetooth devices), not the individual phone.
I am going to test mine with a different Bluetooth receiver at some point, and might also get other people to try their phone with my stereo. According to the person I've been in contact with at Audible, it is only affecting Verizon customers in the US (that they know of), and haven't been able to reproduce it themselves.
I haven't seen anyone else post this yet so I'm hoping someone can help me out. I have a Bluetooth speaker in my car that works fine on stock or on kit Kat roms. But on every lollipop rom I've tried, the audio through the Bluetooth is slightly slowed down (resulting in everything sounded a little lower) and kind of choppy.
The audio plays fine through the phones speaker or through a headset, it's only on Bluetooth that this happens.
Any body else having this problem? Any suggestions?
Same issue here.
I think it may be the speaker I'm using, because I had the same issue when I connected my tablet to it that is also running lollipop. I need to find a different Bluetooth device and see if the problem persists.
supermatt9 said:
I think it may be the speaker I'm using, because I had the same issue when I connected my tablet to it that is also running lollipop. I need to find a different Bluetooth device and see if the problem persists.
Click to expand...
Click to collapse
I was doing a search on this issue myself, which brought me here. It's actually only one speaker I have that does this, and it's the newest BT device I have. It's the HDMX Rave portable BT speaker. It worked fine with the KK ROMs I was using at the time I got it, but ever since updating to LP, only that speaker of all the BT audio devices I own does that.
Weird...
Similar Issue
Hi,
I've also experienced this, although it seems my Bluetooth plays much worse than yours. It's slow for a bit, then choppy and breaks up, then it'll speed up the music to get back to where it should be. It renders Bluetooth music completely unusable.
I've found:
High CPU usage causes this in KK (skydragon) for me. The high-usage culprit is the netd module, not sure if that's relevant.
I've flashed Jasmine Lollipop (5.0.11) lots of different ways, with several different modems, and it still has this issue.
It doesn't seem to depend on the app, as it happens with the default music app and with Spotify (192 Kbps).
It happens on both of my Bluetooth devices, a cheapo portable speaker and my nicer car stereo. I don't know the BT versions they use.
Disabling WiFi helps a little, disabling data does nothing.
Anyone have any workarounds?
i had the same problem when connecting to my car speaker.
funny thing is some days it works great, and other days all of a sudden it just plays all slow. anyone got fix?
So I've been doing some more tinkering. Turning off WiFi will fix the issue for my "dumb" bluetooth speaker (it's a pair button and a power switch only), however it will only fix the issue for the first ~3 minutes on my Clarion car stereo (with all sw updates). I've disabled literally every Bluetooth service, activity, provider, and responder that isn't essential for A2DP connections. I'm able to access the hidden menu item for Bluetooth testing, but I don't really know how to use it. If someone has directions for that I'd gladly put my phone through the paces.
Loving the phone so far, but I'm sad to say while connected to my Sony x-7s wireless speaker, I hear a Popping sound about every 15-20 seconds.
I jumped over to my old Note 3 and played the exact same file and the distortion vanished, so I know it's the phone.
Anyone else getting this or know of a workaround? Hopefully it can be fixed by an update.
xxceler8 said:
Loving the phone so far, but I'm sad to say while connected to my Sony x-7s wireless speaker, I hear a Popping sound about every 15-20 seconds.
I jumped over to my old Note 3 and played the exact same file and the distortion vanished, so I know it's the phone.
Anyone else getting this or know of a workaround? Hopefully it can be fixed by an update.
Click to expand...
Click to collapse
I'm having the same problem with my V10. Tried it on a Bluetooth headset and a Bluetooth speaker. On WiFi and cellular. Problem does not go away.
same here, only difference is that it happens to certain speaker and not the others.
I've tried on 4 different bluetooth speakers that I have, and on one of them it would sound absolutely horrible and distorted. Tested the same speaker with Note 4 and boom beautiful sound.
I'm lucky that the adapter that I use in the car isn't affected.
Bluetooth audio reminds me of the original OG Pro, which sounded like an over compressed files being broadcast over AM Radio. That problem persisted until it got the KitKat update.
I suspect it has something to do with LG overlooking the need to differentiate compression/bitrates for aptX vs non aptX devices. Its definitely a major letdown, but one likely to be fixed.
Sent from my LG-H900 using Tapatalk
JCred said:
Bluetooth audio reminds me of the original OG Pro, which sounded like an over compressed files being broadcast over AM Radio. That problem persisted until it got the KitKat update.
I suspect it has something to do with LG overlooking the need to differentiate compression/bitrates for aptX vs non aptX devices. Its definitely a major letdown, but one likely to be fixed.
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
streaming on my aptx receiver in the car is perfect, it actually sounded a lot better than my note 4. But yeah, on the cheap portable bluetooth speaker...not so much.
I have the Verizon LG V10 and occasionally hear the popping when connected to my Bose Soundlink III, and cheap BT speaker at work and in my truck (2013 Ford F-150). But what is even worse, it randomly "stutters" on all three as well all the time! I noticed today in my truck that every time it stuttered, the "play" and "pause" buttons flashed on the touch screen--kinda like the phone was telling it to pause and then play very quickly.
Anyone else seeing anything like this? Any ideas to fix? Other than this pretty major issue, I am lovin' this phone! Thanks for any help!
tomglass said:
I have the Verizon LG V10 and occasionally hear the popping when connected to my Bose Soundlink III, and cheap BT speaker at work and in my truck (2013 Ford F-150). But what is even worse, it randomly "stutters" on all three as well all the time! I noticed today in my truck that every time it stuttered, the "play" and "pause" buttons flashed on the touch screen--kinda like the phone was telling it to pause and then play very quickly.
Anyone else seeing anything like this? Any ideas to fix? Other than this pretty major issue, I am lovin' this phone! Thanks for any help!
Click to expand...
Click to collapse
The stutter is killing me as well. I have yet to pin point the exact cause to it, but this is quite unacceptable for a hexacore device.
I use poweramp btway, and I've tried increasing the buffer etc to no avail. At first I thought it was only struggling when google map is running in the background, or when the list of apps are full. But I've tried clearing all recent apps, even without anything in the background it still stutters.
I hope someone figures out what's wrong. Coming from note 4, I'm a little disappointed with all of these random quirks that frankly is unacceptable for a flagship device.
baymon said:
The stutter is killing me as well. I have yet to pin point the exact cause to it, but this is quite unacceptable for a hexacore device.
I use poweramp btway, and I've tried increasing the buffer etc to no avail. At first I thought it was only struggling when google map is running in the background, or when the list of apps are full. But I've tried clearing all recent apps, even without anything in the background it still stutters.
I hope someone figures out what's wrong. Coming from note 4, I'm a little disappointed with all of these random quirks that frankly is unacceptable for a flagship device.
Click to expand...
Click to collapse
My problem occurs with Google Play music streaming as well as downloaded playlists; the stock LG app with the LG that came with the phone and streaming Pandora. And occurs whether connected to my Bose SLIII, my truck or SoundPal speaker at work... I've tried clearing all recent apps, restarting the music app and restarting the phone... none of that works... Very disappointing and sure hope a fix comes out from somewhere soon!
tomglass said:
My problem occurs with Google Play music streaming as well as downloaded playlists; the stock LG app with the LG that came with the phone and streaming Pandora. And occurs whether connected to my Bose SLIII, my truck or SoundPal speaker at work... I've tried clearing all recent apps, restarting the music app and restarting the phone... none of that works... Very disappointing and sure hope a fix comes out from somewhere soon!
Click to expand...
Click to collapse
so I finally rooted and hard reset last night. Two things that I've changed now:
-Unchecked the NuPlayer option under developer mode
-Installed Viper4android
so far...no skipping yet!
So maybe you can try unchecking the Nuplayer option to see if it helps. Also, I suspected it could be some other app like AdGuard that I installed before I rooted. I don't have that anymore since I'm back to Xposed.
baymon said:
so I finally rooted and hard reset last night. Two things that I've changed now:
-Unchecked the NuPlayer option under developer mode
-Installed Viper4android
so far...no skipping yet!
So maybe you can try unchecking the Nuplayer option to see if it helps. Also, I suspected it could be some other app like AdGuard that I installed before I rooted. I don't have that anymore since I'm back to Xposed.
Click to expand...
Click to collapse
I'm on Verizon so rooting is not an option... yet... I'll try selecting the AwesomePlayer instead of NuPlayer and see if that makes any difference. Thanks!
I just switched to awesomeplayer and it seems to be working better, but it's still being a little weird.
Sent from my Nexus 7 using Tapatalk
tomglass said:
I'm on Verizon so rooting is not an option... yet... I'll try selecting the AwesomePlayer instead of NuPlayer and see if that makes any difference. Thanks!
Click to expand...
Click to collapse
I spoke too soon, the issues are coming back again now.
I noticed that the audio will start popping when data is flowing. e.g. when a notification is coming in, a text, an incoming whatsapp chat, a movement in map, etc.
this is frustrating.
Google Now Voice Settings
So I had this problem appear about a week ago, and then I tracked down what I changed. Try disabling Bluetooth Headset in the Google now voice settings. I turned it on hoping it would make OK Google detection better with my head unit. It didn't, it just made the audio pop every 3 seconds.
TL;Dr turn off Bluetooth Headset in Google now - voice settings.
cbvicious said:
So I had this problem appear about a week ago, and then I tracked down what I changed. Try disabling Bluetooth Headset in the Google now voice settings. I turned it on hoping it would make OK Google detection better with my head unit. It didn't, it just made the audio pop every 3 seconds.
TL;Dr turn off Bluetooth Headset in Google now - voice settings.
Click to expand...
Click to collapse
mine has always been off, issue still persists. I've resorted to it being an LG issue as I never had this issue with any Samsung phones I've had.
baymon said:
mine has always been off, issue still persists. I've resorted to it being an LG issue as I never had this issue with any Samsung phones I've had.
Click to expand...
Click to collapse
Yeah, turns out it only reduced the issue, not removed it. I don't understand why it would suddenly appear for me. Worked fine for 6 months, had the Marshmallow update for a while now. Suddenly one day it starts sounding like crap.
cbvicious said:
Yeah, turns out it only reduced the issue, not removed it. I don't understand why it would suddenly appear for me. Worked fine for 6 months, had the Marshmallow update for a while now. Suddenly one day it starts sounding like crap.
Click to expand...
Click to collapse
I usually reboot when it gets really bad, then it'll be good for some time before it starts popping like crazy again.
Again, this is not a new issue for LG. It's been reported since the day of G2.
I am having the same issue ATT LG V10 not rooted, Google voice Bluetooth headset settings is off. I have the problem when listening with my jaybird headset or 2016 Honda fit, mostly with Google music and beyond pod whether audio is downloaded or streaming. As a Samsung Note user for many years this is disappointing and debilitating!
I cleared the cache for all apps, and the skipping went away. I'm going to see how long it takes before it comes back.
Yeah, had this issue with my LG G3 and now with this phone. Not sure how LG can continually use poor Bluetooth chips. Other devices work fine but this one pops so often, it's painful using my Bluetooth headphones or speakers. It's sad cause I love the amp on it when listening wired.
Fixed (so far) my Bluetooth problems by disabling (check the box) battery optimization on system apps. My solution post http://forum.xda-developers.com/lg-v10/help/marshmallow-blue-tooth-problems-solved-t3409943/page1