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.
Related
Anyone ever have connectivity/inconsistent connectivity with Bluetooth on the Vibrant?
I never use it, but another XDA user mentioned they were having issues.
If you have had issues, what suggestions can you make?
The only connection problem I have ever experienced is sometimes with my phone, it will connect --- disconnect ---then connect when I first turn on my car (Infiniti m35) but it does that all in a matter of 5-7 seconds then it never has issues after that. Bluetooth is remarkable on this phone....... wish the GPS was as good. Running latest Bi-winning now
Me and my wife have both had the same issue with a paired device not connecting and you have to turn Bluetooth off and then back on and all is well. Doesn't happen often but can be a little annoying when it does. By the way my wife's vibrant is completely stock and I'm on cm7.
Sent from my SGH-T959 using XDA App
oka1 said:
The only connection problem I have ever experienced is sometimes with my phone, it will connect --- disconnect ---then connect when I first turn on my car (Infiniti m35) but it does that all in a matter of 5-7 seconds then it never has issues after that. Bluetooth is remarkable on this phone....... wish the GPS was as good. Running latest Bi-winning now
Click to expand...
Click to collapse
I quit reading when I saw m35. Love that car. Oka, want to hire a NC boy for cheaps? ha.
I use Jawbone Era and it randomly disconnects even when phone is in my pocket and bluetooth in ear. It reconnects a few times but mostly I have to turn the headset off/on to reconnect. Froyo 2.2.1 is better with Bluetooth than 2.2.0
It might be the headset though, our phonen is one of the FEW devices that has Bluetooth 3.0
Even the new LG G2X has 2.1 and not 3.0
I use bluetooth headset regularly on bionix 1.3.1. No disconnections, but the signal strength seems week as there is lot of distortion if the phone is in my pocket. So I have to always hold phone in my hand.
Sent from my SGH-T959 using XDA App
The issues I have (no matter what ROM I use) are Connect - Disconnect - Connect and then the stack is hosed. Have to reboot the machine to get Bluetooth to reconnect (Using Motorola H117). Also, can't figure out the exact pattern, but if I get a notification while bluetooth is on I turn it off and no more notification sounds... or ringing... or anything. I have to reboot to get sounds back.
I connect to my car stereo and sometimes I hear skipping. With my plantronics headset sometimes the signal gets weak if the phone is in my pocket
Sent from Glensta's phone
It is a weak signal in the phone. I have had several phone over the years and my old nokia flip phone was the only one that could do more then 3 feet without issues. My HTC kieser, HTC Shadow, N1 and my current SGS all have issues with my BT headset if the phone is in my pocket on the opposite side of my body from the headset. My old Nokia would let me use the same headset a room away so go figure.
One thing I have noticed is I if I try and transfere a file to any phone(other then the nokia) the file transfere always fails. It works to and from a PC but not to another phone of any kind(except the nokia).... very odd.
my bluetooth has been inconsistantly connecting since I started using 2.2.1 ROMs. it always worked fine previous to that on all the 2.2 ROMs I used.
zaphod_fl said:
The issues I have (no matter what ROM I use) are Connect - Disconnect - Connect and then the stack is hosed. Have to reboot the machine to get Bluetooth to reconnect (Using Motorola H117). Also, can't figure out the exact pattern, but if I get a notification while bluetooth is on I turn it off and no more notification sounds... or ringing... or anything. I have to reboot to get sounds back.
Click to expand...
Click to collapse
After turning bluetooth off on my phone or turning off my headset once or twice I frequently lose all sounds as well. Glad i'm not the only one.
I have the problem of sound not switching back to the speaker if I turn off either the headset or Bluetooth on the device.
How does Samsung screw something as simple as this up and it not be fixed after 4 official updates?
Nothing about Samsung's top notch screen is worth dealing with the headaches that come with their software. I'm trying to wait for the second generation dual core devices but, if I see good reviews on the Sensation, I am jumping off the Samsung emotional rollercoaster.
Sent from my SGH-T959 using XDA App
I have been back and forth with Samsung over the past 6 days attempting to troubleshoot this.
I have used a Motorola H117 and a Rocket Fish Stereo Headset that I have used with the phone. The following *almost* replicates the sound system crash every time.
1. Turn on Bluetooth headset
2. Press button
3. Voice Dial a contact
4. Phone conversation for 25 - 30 minutes
5. Disconnect phone conversation
6. Bluetooth remains connected for another 20 - 30 minutes
7. Turn off Bluetooth headset... no more sounds from phone.
Nothing fixes it short of a reboot of the phone.
I am running STOCK 2.2 KB5 right now. Factory Reset, No root, on the 5th Phone replacement from T-Mobile. I have an open case with 2nd Level support with Samsung however they have given me every excuse from "It's your headset" to "We don't replace phones". I have not asked for a phone replacement and I am earnestly trying to troubleshoot this problem with them.
If anyone has any additional information, please add it to this thread. I have passed the URL for this thread on to Samsung (I do not know if they will bother with hitting it) but I am cross posting at the T-Mobile forums as well as publishing on Twitter.
My only issue is that I have to manually connect bluetooth every time I get in the car. I don't know if this is a problem with my phone or with the bt-fm transmitter our both. otherwise, once I'm connected, music plays great.
Sent from my SGH-T959: Trigger 3.2, Overstock 2.4.1
Basically, my BT has been pm'sing on any 2.2.3 and up ROM.
zaphod_fl said:
7. Turn off Bluetooth headset... no more sounds from phone.
Nothing fixes it short of a reboot of the phone.
Click to expand...
Click to collapse
I have the same problem. I found an alternative to rebooting your phone to hear your sound again. Just play a visual voice mail message and hit the speakerphone button in the UI. Your sound will return. You can also play a google voicemail message and hit the speakerphone. It's not a fix but it will keep you rom rebooting your phone several times a day.
I use 2 Bluetooth devices on my phone.
Sony bluetooth headset:
Skips a lot, depending on what I have running. It's worse the more apps I have. To get the best performance, I usually need to end task everything that's running, clear all RAM, then run the music app again. I use the stock music app. I have had better performance out of several ROM's. I think it might be tied to the kernal used, depending on how much space is left (i.e. Bullet's 339mb kernal that I'm using with Simply Honey). Almost like there's a buffer issue.
Kenwood headunit:
I only use the bluetooth connection for handsfree while I'm driving. The only issue I've encountered is that the bluetooth connection is not always automatically restored everytime I get in my truck. If I go into Wireless and Network>Bluetooth, I can get the connection working again. It seems to always be a phone issue, not the headunit.
If you want a beta tester for something, let me know. I use both the headphones and headunit quite frequently.
We just got a '12 Honda Odyssey.
My Sensation works perfectly with the car's bluetooth but the wife's Vibrant is crap for connecting. Very disappointing. Came here hoping rooting her phone and installing CM7 would fix the problem, but that appears to not be the case.
Shame.
No more Samsung phones for us....
I use trigger 8/22 and the Bluetooth works better than ever. Stock gave me head aches
Sent from my SGH-T959 using xda premium
+1 for Vibrant bluetooth problems. I have a garmin nuvi in my car and sometimes it works, sometimes I get the connect-disconnect-connect, and sometimes it doesn't even try to connect.
I've tried stock, bionix 1.2, 1.3.1, and NextGen 2 and only bionix 1.2 seemed to work reliably.
When it works it is fine.
When it does the connect-disconnect-connect thing it sometimes works for phone calls be most often the audio is going through my handset even though the phone claims a BT connection has been made.
Finally in the case where the BT stack is so f'ed up that it doesn't even try to connect it seems like there's some serious battery drain that doesn't show up on the battery stats screen. I suspect the BT is stuck in some kind of loop that causes it to fail and burn lots of power.
The inconsistency is probably the most aggravating part of the whole thing...
Hi,
I have the following problem:
Everytime I pair my Samsung Galaxy SII I9000 with my car (Renault Fluence 2012) and its built in bluetooth System, it says that it's correctly paired (and honestly it doesnt even take a minute to pair correctly), but it plays no music. It just has no sound (even when the song is playing correctly on the phone) but everything else just works perfect. I mean, i can control the music (songs, playlists, etc) from my car, but the sound just wont come out. The only way to make it work is to 'unlock' the sound by calling someone. So when the call starts, then the audio starts working. That is, so far, the only way to make it work. And i have to do it EVERY SINGLE TIME that i turn on the car or that the device stops being paired with my car.
It does EXACTLY the same thing with my bluetooth headphones (Motorola S305), so I realized it was my phone. I have tried other phones with my car and they work just fine. I have tried other things with my headphones too (like my Psvita) and they work smoothly.
The weird thing about it, is that my phone used to work perfectly fine with both things, and just a random day it decided not to work anymore.
I used kies and re-installed android from 0, and that solved the problem for a few days and then it all started again. I have tried cleaning all the bluetooth devices that my phone is paired with. Going back to factory settings in my car, removing the battery on the phone, resetting the phone, taking everything out (including the sim card( everything. And nothing seems to work.
Please, help!
My phone is a Samsung Galaxy SII with Android 2.3.6 (it came with 2.3.3 and i upgrade it twice through kies) I have never rooted my phone or done anything to it, except for upgrading Android through Kies.
Thanks so much!!!
Pirithous said:
Everytime I pair my Samsung Galaxy SII I9000 with my car (Renault Fluence 2012) ... it says that it's correctly paired ... but it plays no music. It just has no sound ... but everything else just works perfect. I mean, i can control the music (songs, playlists, etc) from my car, but the sound just wont come out. The only way to make it work is to 'unlock' the sound by calling someone. So when the call starts, then the audio starts working. That is, so far, the only way to make it work. And i have to do it EVERY SINGLE TIME that i turn on the car or that the device stops being paired with my car.
It does EXACTLY the same thing with my bluetooth headphones (Motorola S305), so I realized it was my phone. I have tried other phones with my car and they work just fine. I have tried other things with my headphones too (like my Psvita) and they work smoothly.
Click to expand...
Click to collapse
Wow... That's very strange. First off, I'd be looking at compatibility issues. Do you have the BT specs for the car? Maybe they're the same as the headset and not quite 100% compatible with the phone.
Another possibility (although remote) is that the headset and the car are fighting over which gets to talk to your phone because phone services are much different than A2DP (Audio).
You might just have a flaky BT antenna in your device, or a bad (stock) modem/baseband.
I'd try rooting and see if a different modem/baseband clears up the issue. Then at least you'll know what the deal is.
Hey, I also found this on the Renault web site... http://www.renault.co.uk/bluetooth/default.aspx
>> Why does my telephone not reconnect to the system when the vehicle is started?
- In order for your telephone to automatically connect when the vehicle is started, it may be necessary to activate the automatic Bluetooth connection function on your telephone with the hands-free kit. For details on how to do this, please refer to the instructions manual for your telephone.
- Upon reconnection and if there are several telephones paired within the hands-free kit reception area, it is the one that was paired last that will be connected even if it is outside of the vehicle.
So it looks like it might actually be a Renault AND a Motorola problem.
There's also a list of compatibility files at the bottom of that page based on the system you have.
First of all, thanks so much for your help.
The problem with whats going on with my phone, is that it used to work just fine before, with those 2 things (my car and my headphones) Its not like they never worked, they used to work completely fine with my phone.
And i never use them together, like my headphones have never even come close to my car. And since i thought that it could have been a problem with they 'fighting' with each other, even if they werent close, i erased all the cache on my bluetooth settings and unpaired all devices that were ever set with my phone.
So its like if i had never used bluetooth. That obviously didnt work either
It turns out that your car likely keeps up to 5 phones in memory... Is there a way to clear the phone list in the car as well? Then re-pair from scratch on both sides?
well either the blueth is defect or ur doing some wrong settings,root ur device there r plenty of bt apps tht work more powerfull than the default...y possible ur car mus hav a reset buttun for bt so delete all pairs frm phone an reset ur car bt,,,,then start fresh.....hope it helps
I restored my car's settings and deleted every phone paired. That didnt work either... I also tried with a friends phone (iphone 4) and that worked completely fine...
Pirithous said:
I restored my car's settings and deleted every phone paired. That didnt work either... I also tried with a friends phone (iphone 4) and that worked completely fine...
Click to expand...
Click to collapse
Time for a warranty replacement I think.
Jeez... thats exactly what i was trying to avoid, because my cellphone company will have me waiting for like a month without my phone and will give me in return the ****tiest phone ever while they try to fix it and then realize they cant.
FML
thanks anyway for your help!
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.
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.