I'm having an issue using bluetooth with CM7 that may be difficult for most users to duplicate or even experience. This problem has persisted from the beginning of CM7 up through N37 including using Ladios' kernel and the latest radio update.
I'm a long distance motorcycle rider and use a a2dp bluetooth equipped helmet. This enables the full use of the Aria's telephone & music functions, from streaming music via BT to the helmet, to answering phone calls.
It's taken me awhile to realize it, but running with CM7, I'm experiencing a significant number of what I call bluetooth dropouts. This is very noticeable because I always stream music to the helmet when I'm riding. The bluetooth connection doesn't disconnect, the signal just seems to drop dead (go silent) for anywhere from a couple of seconds to as long as 15+seconds. This is something I could easily attribute to BT signal interference from power lines or RF interference, etc, if it wasn't for ONE thing;
I also have a second Aria running Gene Poole's Liberated Aria 2.2.2 and the same latest radio. With this phone and OS, the BT dropouts are non-existent.
Anyone have any suggestions? I'm really liking and well into being committed to CM7, but the BT dropouts are a real issue for me.
Edit: No, missing 10 or 15 seconds of music isn't a big deal, but when a phone call drops out for that long, it is.
.
try compare two roms /system/etc/*.csv
attn1 updated props before: https://github.com/koush/proprietary_vendor_htc/commit/0a8b318261979b71bf6fd099788210bf74e8e21e
Thanks, I'll see what I can find.
I have what I suspect is the same issue. In my case, it's localized and predictable - if I take my usual bus to work, it doesn't happen until I get off the bus downtown. If I take a different bus, it happens at certain intersections. It also happens when I walk the dog in my neighborhood. Obviously, there is some sort of interference occurring at these locations, but I can't figure out what.
Did they ever fix the issue with everybody running cm7 having the same bt address?maybe you folks are running across other root users running cm7 and a Bluetooth device.try loading cm7 on your wife's phone see if it creates the same dropout.
Sent from my Liberty using XDA App
No its not from being around rooted phones mine does it in towns, city's, and out in the country, around people and no people, there is something causing interuption within the phone or program itself.
Related
So I've had this issue since the first Eris leaked ROMs. Basically, any 2.1 ROMs I've tried, INCLUDING what I'm running now, DC 2.07.2
When I turn on bluetooth, and then try to pair my headset, I get a popup saying:
Code:
To pair with "Motoroal H270",
confirm that it is showing the
passkey: 001328.
{Pair} {Don't pair}
The numbers that show up for the passkey are always different, but always 6 digits. I'm assuming the phone is not registering the correct profile for my headset.
Of course, it never pairs.
In 1.5 ROMs I simply entered 0000 as the passkey, but I do not get that option.
I've searched, but with limited keywords to search for... let's just say the hundreds of posts are a little difficult to filter through.
Is that an older Motorola Bluetooth?
I've paired the Motorola H720 with the leaked Eris. Smooth like butter. All I did was enter "0000." Worked fine. Try another bluetooth device, possibly one of more recent vintage. (Don't know how old a model your 270? is.)
I have not had any problems with my Clarion car stereo or my plantronics headset. In my car, in fact, the 2.1's have worked better than stock, since my car stereo picks up the phone and streams the audio automatically every time I get into the car without having to delete and re-pair (as I had to do with stock).
Pete
I have had no luck pairing my phone and any of my cars with any ROM based on 2.1. It pairs, but will not stay connected. Phone says "paired but not connected"; car says "paired, connected; then disconnected"; then endless loops of connected/disconnected. Sucks!
The sad thing is it seems most of these amazing ROM cookers do not use BlueTooth so it is not something they worry about. I bet this is what is holding up releasing the official Sprint update.
I too have tried searching through endless posts about bluetooth and 2.1. All I can come up with is there are some libraries missing from the 2.1 BlueZ; or something to that effect.
I love Damage's 2.0.7.2 ROM! But I have to go back to stock since driving and talking on the phone without a handsfree device is now illegal here in El Paso, TX.
I don't have a car or stereo bluetooth device to pair against. Just tried pairing my bluetooth with the new 2.0.2v2? Alysious ROM. Took 2 sec and nearly totally automatic. Amazing.
My issue with all 2.1 roms is that I can pair, dial and audio stream all day. I just cant talk as no sound or mic. I reflash back to 1.5 and all works well. BT in the car is now useless. sigh
2.1 paired fine, but its a crappy connection on 2.1, on 1.5 i had a better connection
finally used my BT last night with my phone ...worked like a champ! everything was clear to me....i don't have no sound probs and haven't used any of the fixes...
I pair with my bluetooth headset most of the time without problem. I do occasionally have to turn on and off my headset and the bluetooth on the phone to get it to reconnect. Thankfully, it only happens occasionally.....
Maybe I'm just one of the lucky ones (this time) but I have been streaming audio from my hero to the car stereo while while using google navigtion, which politely talks over the music, and have not had any problems. I'll get an occasional skip in the music (probably during downloads of map data), but nothing worth complaining about.
Pete
poor_red_neck said:
So I've had this issue since the first Eris leaked ROMs. Basically, any 2.1 ROMs I've tried, INCLUDING what I'm running now, DC 2.07.2
When I turn on bluetooth, and then try to pair my headset, I get a popup saying:
Code:
To pair with "Motoroal H270",
confirm that it is showing the
passkey: 001328.
{Pair} {Don't pair}
The numbers that show up for the passkey are always different, but always 6 digits. I'm assuming the phone is not registering the correct profile for my headset.
Of course, it never pairs.
In 1.5 ROMs I simply entered 0000 as the passkey, but I do not get that option.
I've searched, but with limited keywords to search for... let's just say the hundreds of posts are a little difficult to filter through.
Click to expand...
Click to collapse
Guys, sorry to revive an old post but I am having this exact same issue as the OP. If anyone has found a fix, please post. Thanks.
Looking at FroYo they have updated some Bluez stuff (what makes out BT work) maybe it will be better when we get that.
Hopefully...
So I flashed to a froyo ROM over the weekend and have found someone posted a fix for the gps issues, but I'm having BT issues as well. Has anyone else experienced this: I can pair certain BT accessories but not others, and even when paired the devices cannot connect without multiple connection requests.
My specific issue is that I have motorola rockr bt earbuds, and a Jabra car kit, and they both pair with the phone (after a few trys) but neither will automatically connect to the phone once they're turned on. With the earbuds I have to manually try to connect 6 or 7 times in a row before they'll connect, and even then they may only connect with the phone audio only. This wasn't an issue with the stock ROM so I'm assuming its the bt radio library for Froyo thats the problem?
I'm not new to development, but I'm kinda new to development on Android. I've been trying to learn more about the radios and how they're configured within the OS but I haven't found a lot of good documentation on it. I'd be happy to work this out for myself and post any improved radio to the forum but it would be helpful if someone could send me a link to some learning material? If someone has an improved Epic Froyo BT radio to flash that would be helpful as well
yes bluetooth issues as well, but different in that only when i turn bluetooth on it foreclose's. the bluetooth is otherwise not affeceted. only on the initial start up.
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Delta1Fox said:
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Click to expand...
Click to collapse
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
revjtanton said:
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
Click to expand...
Click to collapse
I noticed that too with the stock 2.1. However, Bluetooth voice dialing is a feature built into 2.2. I've read that some people having it work great, but other's like myself, are not having it work at all. Oh well. I'll live for now. Hopefully if it isn't fixed beforehand then it'll be fixed with the "official" release. LOL.
now that you mention it, i had this problem too doing some bluetooth file transfers between my buddy and I's phones last night. it struggled to connect multiple times but after the first successful transfer it seemed to stop having problems for a little. I'm moving back to 2.1 until we get some non-beta custom roms for froyo because i use bluetooth and gps everyday. just out of curiosity though, for those who are having problems, which rom and modem are you using?
I put the DI18 modern on there and that has seemed to fix the gps more or less. I think I'm going to go back as well. Maybe I didn't flush data enough times but layar can't find the camera, neither can the bar code scanner...it's close, but Froyo just isn't ready for the Epic yet.
Sent from my SPH-D700 using XDA App
Still having Bluetooth problems with official Froyo release on Epic 4G
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
I am using the new official Froyo release from Samsung/Sprint. having the same buggy issues I had with the old leaked version.
donkeysauce said:
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
Click to expand...
Click to collapse
I can confirm these issues still exist in the official release.
I'm having the same problem, but when I use bluetooth in my car, it insists on transmitting sounds to my car's bluetooth, even when I repeatedly uncheck Use for media audio. I don't have an option in my car to disable A2DP. My only complaint with Eclair, other than speed (I'm using Bonsai4All, and previously, Syndicate) was that I was running out of space for software (was using EpicExperience). Sometimes, bluetooth won't connect at all, necessitating a phone reboot, or going into airplane moe and then back out. So I'm gathering that this is across the board, regardless of Froyo build? Syndicate didn't work at all with my car.
Hey All,
I have been scouring the web in hopes of answers and can find none. Evidently I'm not the only EVO owner in this boat either. I own a 2011 Ford Explorer with Sync & MyFord Touch (Fully updated). I pair the phone to the car it makes the connection fine. Begins the setup and sometimes will even connect and be recognized for a bit. But then the phone drops the bluetooth headset part of the connection. It appears (but I can't confirm) that Bluetooth streaming audio is still connected. There was a blissful 3 day window where it all just worked. Then it went to hell...... I saw one post where it said to switch the Bluetooth name back to "PC36100" and that didn't help. I saw another that said use a 4 digit pairing code and that didn't help either.
Its worth noting that I'm running Myn's Warm 2.2 rls5 with the stock & fully updated HTC kernel. So here's what I'm hoping to figure out:
*Have you had this issue with ANY car?
*Have you had this issue with Ford SYNC/MyFord Touch
*Aside from unpairing & repairing were you able to get around it?
*Is there a Kernel with a better bluetooth stack I should try?
Thanks for any help, many thanks will be given!
Unfortunately, the HTC bluetooth is totally worthless. I have a 2010 Ford Focus with Sync and it would connect and sometimes work for awhile, but people on the other line always complained of poor quality. And it wouldn't even connect all the time either. Lots of deleting and readding the phone.
Couple weeks ago I switch to CM7. Since CM has a bluetooth stack they built themselves and actually implemented correctly, I haven't had any problems pairing my phone. I can make calls, stream music, gps, etc and it is all fine. Always connects too. What is nice also is the audio will automatically stop if Google Navigation is giving directions or if someone calls. When I shut my car off and open the door, the audio stops and when I get back in it automatically starts again where it left off.
Basically if you want to use your Evo with a Ford Sync system, you'll need to run a version of CM.
Arg. I'm still waiting on my Explorer
On my 08 Explorer with Sync and Myn's RLS4, all is good. I turn BT off and make sure it is on before I turn the key. I stream audio constantly, and talk a bit. I literally just got around to putting on RLS5 today, haven't driven yet.
I partially agree with teamgreen02. It's HTC, not Ford. Does texting work with CM7? That would push me over the edge (or Explorer, pun intended)
It seems that there are a bunch of phones that have issues maintaining connectivity with the latest Sync system. I had to re-pair a BlackBerry to an '11 Explorer this afternoon. There is a backwards pairing procedure that may help rectify your issue. If you try searching for your phone from the vehicle instead of searching for sync from your phone, it has, in my experience, minimised connection drops, especially on the latest versions of Sync...
Btw, I am like the only tech at my dealership who really understands how to even pair phones to Sync, let alone diagnose the concerns our customers have described. There is also a system compatibility chart that we reference to determine if a particular device has been tested and verified to work with certain features of Sync. Last I checked (the October 2010 update) the Evo still wasn't certified compatible/tested...
Sent from my PC36100 using XDA App
Does anyone have any updates on this? My wife's Sync is working fine with her Evo but the sound quality sucks when she calls. Her phone isn't rooted.
I did update the Sync software from v1 to 1.1 (She has a 2008 Ford Edge Limited) but need to do further updates to the system since there are updates available.
Here is my experience/.02.
My wife drives a 2011 Ford Edge with sync....she has a stock Evo4g. When she bought the car 2 months ago, bluetooth seemed to work fine...now she is having the exact same issues everyone else is having. The bluetooth connects/disconnects and just plain doesn't work. I attempted to fix it and.....no. If i unpair from both the car/phone then retry to connect them, it connects for a second and when it tries to send the phonebook from the phone to the car, the connection dies. The phone still displays that bluetooth audio (not phone) is connected.
I then tried my Evo 4g (CM7) on her car...no problems whatsoever. Sync'd and connected fine...phonebook transferred over in about 5 seconds and everything worked great.
To note, my Evo 4g also works perfectly on my 2011 Infiniti G37...
So I think my example further proves that HTC's bluetooth software is likely the causative agent and is likely junk....root or die i guess =p
hope this helps someone
I rooted and installed MIUI and dont have any problems yet with sync.
Although,
I was looking looking to pull the bluetooth stack of the droid X which has the MAP bluetooth profile, that will allow ford sync to read and write text messages for you.
any ideas on how to do this? Or where to find in in the droid X?
2010 Ford Focus here, works fine for me. Using Fresh 3.5.1.
The bluetooth stack should all be dependent on what kernel you are using on your rom, so if you already have it rooted, try to change kernels and see how it improves...
as far as the MAP profile, i found this thread in the Q&A section, and it also recommends pulling the MAP profile (for text messessaging) from the motorola droid kernels.
I wish i knew how to do this.
I was hoping for someone to be able to do this for us
EDIT: I also found this thread:
http://forum.xda-developers.com/showthread.php?t=741332
its trying to get the MAP profile into the nexus one...
they found the new bluez stack had the MAP profile included:
http://code.google.com/p/google-summer-of-code-2010-bluez/updates/list
I have not used sync in a long time in my 2010 escape, but I'm wondering if the text message function works as well. Any word on this?
Sent from my PC36100 using XDA Premium App
lawmangrant said:
I have not used sync in a long time in my 2010 escape, but I'm wondering if the text message function works as well. Any word on this?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
No, the text messaging does not work for the unrooted Evo and it doesn't work for a rooted Evo under Myn's Warm TwoPointTwo RL5.
I Just had a 2011 Explorer limited for the past week as a rental and it worked fine for me (music & calls). I know this does not help much hope you get it going.
i had my EVO running fresh 3.5 and worked great in my Escape, i just switched to twopointtwo ROM and now here i am looking for a solution, not sure if its the rom or the kernel since i switched both..
alexdogg said:
i had my EVO running fresh 3.5 and worked great in my Escape, i just switched to twopointtwo ROM and now here i am looking for a solution, not sure if its the rom or the kernel since i switched both..
Click to expand...
Click to collapse
got it working for a day but its disconnected again, im going to explain what i did hoping someone with more knowledge can help us SYNC users to connect bluetooth
used fresh EVO 3.5 for a while and worked great, then i got bored and changed rom to myn's warm 2.2 with the kernel included and bluetooth started disconnecting after 30 seconds or so...
i tried
ms79723's SBC for Netarchy's CFS More Aggressive 4.1.9.1 Kernel (v7)
Ziggy471 Warm TwoPointTwo RLS4 Kernel
they didnt work either... so heres the funny thing..
i wiped and reflashed a fresh version of the same rom (Myn´s warm 2.2), this time i didnt restore anything, no apps, no contacts, anything, left it clean.. then i paired it up and voila.. it worked for a long time in my ESCAPE, so i thought it was working and restored all my apps and data.. and to my frustration... its disconnecting again.
so does this have to do with the kernel or with some apps or what.
has anyone figured out how to get sync working with blue tooth messaging.
marcw2 said:
has anyone figured out how to get sync working with blue tooth messaging.
Click to expand...
Click to collapse
I don't think the android kernels have the message access protocol that is needed for this to work.
Sent from my HTC Evo 4G
2010 Ford Focus. Bluetooth sucked with stock ROM and warm, dropped connection all the time. Works great with CM7. Definitely an issue on the phone side and not the car in my case.
I am also wondering if we can somehow get the text messaging working. I don't think its officially supported on any Sprint phones.
2010 Moutaineer here - never had a problem with Bluetooth on rooted stock EVO ROM.
Listen to music all the time - even the "call-transfer" functionality works fine when I enter the vehicle while talking on the phone.
Only thing is - I wish the damned thing would auto-synch for media-audio on Aux1 instead of me having to select the source all the time - anyone know how to do this?
2010 Lincoln with mytouch/sync and rooted with stock rom. No problems at all. Sometimes it gets a little static sound but I just turn my Bluetooth off then back on.
Sent from my PC36100 using XDA App
Think the problem lies with the Sense BT stack.
Good morning fellow forum member. I've recently begun having some significant bluetooth connectivity issues with my continuum and Ford Sync system in my 2011 Fiesta. Now, before you start ranting about your loath for microsoft or Ford please hear me out. In theory, the Sync system, combined with bluetooth technology, is a great way to go hands free. It also allows for the coordination of the system and Pandora & Stitcher Radio on an Android phone.
Anyway, lately my bluetooth connection to my car has been causing FCs on my phone. They are the type of FCs that cause the "long-short-short-short" haptic feedback but doesn't throw a pop-up message describing the cause of the FC. So, when the feedback occurs the phone will sometimes lock up but it always disconnects the bluetooth. I don't use bluetooth in any other fashion so I can't be positive that it's not an issue with the car's bluettoth system.
With all of that said, is there an inherent issue with the bluetooth system on our phone? If so, is there a fix for this? I'm currently running the EC07-clean_new ROM. This was installed over the SCH-I400-EC07-FROYO-REL-PRODUCTION ROM. My broadband version iss:i400.0.6v.EC06, Kernel 2.6.32.9 and build SCH-I400.EC07.
Any help that you brilliant folks could offer would be much appreciated.
Thanks,
Ray
I run bluetooth constantly (it's the only way I talk on my phone, driving or not.) I've never run into this issue. Have you recently downloaded any new apps? I found that there are some apps that simply don't play well with our phones. Especially radio based apps (I.E. the issues a lot of us were having with gps based apps, or gps losing it's lock, after a while. Wireless tether 3.06 beta completely screwed my phone up... etc). The only other thing I could suggest is to drop your phone from the sync, and reconnect it... I do this with all my bluetooth devices at least twice a week as a matter of course. And if you want to experiment to see if it's sync or your phone, assuming you have bluetooth stack on your computer, you could connect it to your phone. Other than that, maybe find a friend that has bluetooth and connect it?
Thanks for the suggestions. The most recent app I have installed that uses a radio is the new Stitcher, though I have been having some issues with "My Tracks" FCing but I think that is another issue. Anyway, prior to your reply I found an app on the market called "bluetooth fix repair" It's free and I gave it a shot. I've also deleted the phone from my car's list and repaired them. So far so good. I have a bluetooth stereo headset I'll have to try. I probably have too many apps to begin with. I'll see about deleting some of the ones I don't really need.
Thanks again,
Ray
Reborn627 said:
Thanks for the suggestions. The most recent app I have installed that uses a radio is the new Stitcher, though I have been having some issues with "My Tracks" FCing but I think that is another issue. Anyway, prior to your reply I found an app on the market called "bluetooth fix repair" It's free and I gave it a shot. I've also deleted the phone from my car's list and repaired them. So far so good. I have a bluetooth stereo headset I'll have to try. I probably have too many apps to begin with. I'll see about deleting some of the ones I don't really need.
Thanks again,
Ray
Click to expand...
Click to collapse
I think you should be good with rourine disconnect/reconnect. Asfor too many apps, the only thing rhat matters there is storage space. Android wint let you run "too many" at once. Itll delete from ram as needed. I was just saying that certain apps dont seem to play well with others. But that is an android issue, not your phone in particular.
I'm not here for a long time. I'm here for a good time. To hell with the red wine. Pour me some moonshine. - King George
I'm totally stumped here. Yesterday I decided to reflash my phone. I figured any issues might be ironed out. It must be an app issue, although it is going to be a PIA to uninstall then reinstall each app and test the BT after each app install. I thought that it might be the trailblazer101 car cradle, desk cradle or the sticher apps that were giving me the problem but that doesn't seem to be the case. Maybe I'll try replacing the BT files with the ones from eclair to see if I end up with the same trouble. Any idea if that might cause more problems? Are the BT files android version specific?
Peace
EDIT: I've not swapped the BT files from eclair but I did spend an hour or so listening to Stitcher radio via a bluetooth headset. It doesn't seem to be a BT issue. More likely an issue with the connection to the Sync system itself. Connecting via bluetooth is no problem in the car. It's not until I attempt to engage a function other than the phone that an issue occurs. I may try to reflash the EC07-clean ROM and see if there was something with the EC07-Clean_new version that I've been running for the last few weeks.
OK, the BT issue seems to be corrected. I flashed adrenalyn's EC07-clean ROM and that seemed to do it. Something must have gotten corrupted. So, issue resolved...i guess.
Hello!
I have a problem with delayed and cut off notifications over my bluetooth hands free device (Parrot MKi 9200). I can experience it on almost every ROM despite ROMs with Tytung's kernels.
Everytime my copilot live 8 says something like "In 500 meters turn left" it takes a little while (maybe one second) for the phone to establish the bluetooth connection to my handsfree device and all i can hear is "..eters turn left". The only ROMs without this issue are those using Tytyng's kernels. They work just perfect. And yes, I know the workarounds like letting the phone play music all the time, but this doesn't work for me, for i listen a lot to the radio or use the SD Card in my Parrot for playing music - so this is not a solution for me.
I tried to find out more about this issue, but all i could figure out was, that this seems to be an android problem. Due to power saving issues Android would close the A2DP connection and reestablish it, once there is a signal comming up. Please correct me if I am wrong on this one.
However, since Tytung figured out, how to get this thing done right it must be also possible on other kernels and smartphones. Is there a way, maybe to change some settings or a working app or some kind of bluetooth drivers, to solve this issue on other ROMs or even other android phones?
Thank you in advance for your help
Don't know of any app, but just by playing blank.mp3 in music player could help you(it holds bluetooth audio connection-stays on all the time)
your sound cuts are because of low power bluetooth mode, try asking kernel dev to disable it?
I have the same problem and it would be nice to have a buffer application which buffers sounds for Bluetooth for a second and transmit them when the connection is active.
Sure it's an old thread... but has anyone tried this?
https://play.google.com/store/apps/details?id=com.turboled.enhancedtts
Should at least fix the problem for the navigation commands...
Thanks, will try it