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.
Related
I hope someone is able to help me.
Okay I have the Wizard, upgraded to Wizard Mobile 6.
Shortly after, all my bluetooth devices (car kit, headset...) had their microphones die. In other words nobody could hear me when speaking through any kind of bluetooth.
I then flashed the Radio ROM to a different version, and bluetooth was repaired. But now the problem has returned for no reason.
Why does my Wizard's bluetooth audio in keep failing, yet its speaker works fine and I can hear other people?
Is there a recommended update to the Bluetooth Stack I can try?
CJSnet said:
I hope someone is able to help me.
Okay I have the Wizard, upgraded to Wizard Mobile 6.
Shortly after, all my bluetooth devices (car kit, headset...) had their microphones die. In other words nobody could hear me when speaking through any kind of bluetooth.
I then flashed the Radio ROM to a different version, and bluetooth was repaired. But now the problem has returned for no reason.
Why does my Wizard's bluetooth audio in keep failing, yet its output works fine and I can hear other people?
Is there a recommended update to the Bluetooth Stack I can try?
Click to expand...
Click to collapse
I do have exactly the same problem. After flashing XDA Mobile 6 Release 3, microphone has worked for couple of days, and then suddenly died. Interesting, microphone is working with Notes but not with phone. I went back to
XDA Mobile 6 Release 2 for some other reasons (read: 2MB more free memory for critical application) but the problem with Bluetooth microphone remains. Radio is 2.25. Any advice?
--
Pogo
There are also at least 3 people at the Wizard Mobile 6 thread with the same issue. Very surprised none of the experts here have been able to propose a fix. Makes the phone virtually worthless if you can't use it in the car etc.
As a workaround, I have found if you mute then unmute the phone volume, the issue is sometimes temporarily resolved for a short time. It always comes back though
I have been asked to join this thread. Per a PM:
We love the ROM you have provided, and are very thankful, however it was not until installing it that this issue arose. It does not seem fair to leave a number of people with a phone that is unusable for 'phone calls'.
Click to expand...
Click to collapse
(Bolding added by me)
I don't know what to tell you. If the rom doesn't work for you, then don't use it... Don't tell me its "not fair". I use MS Voice Command, and XM6r3 and have never seen this issue with my Bluetooth headset (Jawbone). I've also tested this out with a Plantronics Explorer 210 headset that I have and it has not problems with XM6r3 either. My A2DP headset (Spider) also works fine on XM6r3 with MS VC. I've stated this in the past when people have said they have BT issues on my rom. Sorry, but I can't reproduce it, so its hard for me to fix something that isn't broken for me.
Try this... Do a hardreset on your device (take a backup first if you want), then leave it as the base rom with NOTHING extra added. Run that way for a few days (how ever long it has taken before) and see if the problem happens again. If it doesn't then its not my rom but something being added to it (probably screwing with the registry someplace). If it does happen, then as I've stated before, I've seen a number of BT devices be flakey on WM6 (especially car kits). Try a different rom then. If someone with the problem can pin it down, I'll be happy to do what it takes to fix this issue if its something in the rom that is causing it.
Thanks mfrazz. What wasn't fair was not the bug, but that you had not responded to previous mentions of it, i.e. not fair to leave us with it. We love the ROM and put a lot of our life in your hands in a way, as we rely on our device so much for work and play. Hope you understand.
Now then, I have already tried a hard reset and the problem never occurs, until WM6 is put back on. Sure, 'use another ROM' is all very well, but we love yours - again, hope you appreciate the sentiment. If you're in a relationship, are you the kind of guy who tells a girl who loves you, 'find another boyfriend', or do you try to make it work
SO, I am wondering if this is related to the glitch you mention where sometimes when switching out of vibrate mode, the ring tone becomes muted. For that, your solution is to play the ringtone again, then it becomes unmuted.
Similarly, our Bluetooth devices mic's are being muted, and if we mute then unmute them again, then they become unmuted. A link that helps point you in the right direction?
Please note, this is not certain bluetooth devices being 'flaky', this is ALL devices. 4 at the latest count, including rock solid Nokia CARK7W car kits and Jabra headsets.
Some people put it down to MS Voice Command, which I have never installed. What does that program do, do you know, to cause the bug? Again I hope that might help point you in the right direction.
Please don't dump us Let's try to fix what is wrong in this relationship
BT problem solved?
CJSnet - not sure if you have resolved this. I was having the same problem and noticed people with reTouched dialer were not, so I loaded that dialer and the problems went away. I am using a Plantronics Voyager 510. Seems the problem might be with the standard dialer.
Hope this helps
CJSnet said:
There are also at least 3 people at the Wizard Mobile 6 thread with the same issue. Very surprised none of the experts here have been able to propose a fix. Makes the phone virtually worthless if you can't use it in the car etc.
As a workaround, I have found if you mute then unmute the phone volume, the issue is temporarily resolved for a short time. It always comes back though
Click to expand...
Click to collapse
Thanks, I'll give that a try. However WM6 has pretty much finished the Wizard for me, and I'm hoping to get a TyTN II soon as a replacement. Shame.
Hello all. This is my first time posting a new thread although I've been lurking around here for a while soaking up all the information from this wonderful site. That said, I have been researching my problem for days now both here and on google and have found no solutions that work. So I'll see if there's anyone here who can help. Here goes....
I have recently flashed DCD's 3.2.6 ROM on my Verizon XV6800 and it works great (love the aGPS too, Thanks GC14) in every area but my car. I have a 2004 Audi A4 with the RNS-E Nav system with integrated bluetooth. Before I flashed to DCD, I had the original stock ROM (2.09.605.8 with Radio 1.30.00) which gave me full functionality with Jetware Mobile (Phonebook and Recent, Received & Missed Calls all transferred). Now, with DCD, it'll only connect to the car and won't transfer anything. If I try to load Jetware, it'll just lock up my phone while I'm connected to the car. Thanks in advance for any help you can provide.
No one else has this problem or a fix for it?
TGabriele said:
No one else has this problem or a fix for it?
Click to expand...
Click to collapse
I wish I was rich enough to afford such a car, then I could maybe help you out. LOL
But I would gladly accept such a car as payment for figuring out your problem.
Nevermind that the car is an Audi. Does anyone else have this problem with a factory BT system that transfers the phonebook to their car.
I had this same issue on my X3 and it seemed to be the way the PPC wanted to transfer the phonebook was by using some file transfer protocol the car did not understand. I could sync it and make and receive calls but no phonebook. Took it to the sprint store and we tried a blackberry and a standard moto handset. The blackberry did not sync the phonebook either but the standard moto phone did. I don’t think it’s possible based on the profiles in the car so I gave up on the phonebook. Try changing the bluetooth stack in the rom, you will have have to make your own rom and beware of the stack you use to make sure it is one for your phone.
I flashed DCD's rom using the kitchen, so making a custom rom from there is no problem to me. What I'm not sure of is how to change the bluetooth stack. I thought it is part of the hard coding for the OS? If you or someone else reading this thread has any information on this or can point me to some info on this it would be greatly appreciated.
I have the 6800 with DCD 3.2.6, and an Audi, with full phonebook transfer so I'll try to help you out:
1. Which 6800 radio are you using? I have found 3.42.50 to be the best as far as Audi bluetooth compatibility is concerned.
2. Jetware will not work with WM 6.1 on the 6800, but you don't need it, since 6.1 included phonebook transfer enhancements.
3. What version of Audi software are you at? There have been several releases since your year. You should be able to get more info from www.navplus.us and of course from your stealer.
4. You do have your bluetooth settings set for "discoverable", right? And, (I don't know why this is the case) it seems when OBEX is on, the phonebook and other items transfer quicker.
If you have the 6800 radio and Audi software updated, you should have no problem. Jetware is no longer necessary.
1. I am using radio ROM 3.42.50
2. The reason I loaded Jetware is to have it sort my contacts by Last,
First. Is there another way to do this?
3. I am running sw0200 on my RNS-E, but was considering moving up to
sw0260.
4. I haven't tried this, but I will.
Lately I've also had the issue where if the phone is connected to the car for a while, the bluetooth on the phone will shut itself off and not turn back on until I do it manually. I'm beginning to wonder if I should just hard reset and start from scratch. Any ideas? Thanks in advance.
I'm sure there's a reg tweak for listing First name first in contacts. Hunt around here or at ppcgeeks. If you want to stay on 6.1 jetware will not work (unless they release a new version).
Definitely update the Audi software to the newest version.
DCD has done nicely fixing power settings in the last few ROMS to solve the bluetooth shutting off issue, although when memory gets very low, it may still happen. You must have some other program or process running that sucks up memory if you are still experiencing this.
It never hurts to hard reset, as long as you have the time.
So, I've updated to SW0260 and done a hard reset and I'm still experiencing problems. Do you have any more suggestions? Thanks in advance.
TGabriele said:
So, I've updated to SW0260 and done a hard reset and I'm still experiencing problems. Do you have any more suggestions? Thanks in advance.
Click to expand...
Click to collapse
I'm running an after market HU (Pioneer AVH-P4000DVD) and DCD's latest ROM, and Jetware works fine on mine. Just re-transfered my phone book earlier today....
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,
Recently got my n4 and am currently running cm10 nightlies on it, but today I picked up our new car (Hyundai i30 premium) which has bluetooth built into the audio system and I can't get my n4 to sync with it properly. My partners Desire HD syncs no problems and all her contacts phone book everything shows up fine. My n4 wouldn't even sync originally then I just kept retrying and eventually it synced but nothing really works, music won't play through the speakers (the audio system just sits there waiting for music and nothing happens) my phonebook etc don't show up (after me allowing them permission) I can't even make calls.
I have heard that the n4 has some bluetooth problems but nothing this bad, anyone have any suggestions that I can try? Happy to go to another ROM if that will help??
Thanks,
Hosh
this build has serious BT issues. i can't even find a mouse that works. wait and see what the 4.2.2 update brings.
I own a Hyundai Elantra GT which is the US version of the i30 - I didn't seem to experience any issues when I paired it this morning, but I"ll double check when I get out of work this afternoon that the contact sync is working. I am, however, on the stock rom.
I own a 4 day old Dodge Journey and it pairs with no issue to Uconnect.
Try a different rom?
If thats not it, then its your hardware.
The new bluetooth stack in Android 4.2 is causing a lot of issues. Personally, I don't have any problems connecting to UConnect (Jeep Grand Cherokee) or my SmartMini (bluetooth music streaming).
I am waiting on delivery for my MetaWatch, there have been complaints that 4.2 isn't connecting well with it but I guess we'll see. CM10.1 users don't seem to have as many problems. I'm running Xylon w/ Franco r53.
I had the same problem with Chevrolet captiva until I have installed custom ROM and is working perfect now.I have tried every custom ROM and is OK with all.
I have this problem but there is a way around it (for me anyway).
Download Bluetooth file transfer from the market.
Delete the connections with your car. Both on the phone and your car.
Open Bluetooth file transfer. Select the Bluetooth screen.
Make a connection. The default android Bluetooth will ask for a password. Don't enter it. Instead go to your recent apps and select Bluetooth file transfer. Put the password in the request screen the app supplies.
Bluetooth file transfer should pair the devices and make a connection.
Once done. Kill Bluetooth file transfer as you won't be able to exit.
You can then uninstall Bluetooth file transfer if you want (although I tend to keep it for when I change ROMs or have to do a factory reset etc).
Hope this works for you
Sent from my Nexus 4 using xda premium
Hey all,
Sorry for the late reply, been away for the weekend. Thanks for all the advice, tried them all and no luck. Will try out a mates n4 tomorrow and see if he has any luck syncing with the car, if he does might just flash roms again.
after flashing a new rom, I had problems pairing w/bluetooth and connecting w/wi-fi. I fixed the problem by restoring my system settings w/titanium backup thanks to someone's suggestion.
Seems the only thing that worked for me is when it asks to sync my phonebook I have to say no, if I say yes it seems to freeze the whole thing. Makes me think if I click yes I might just need to give it 10-15 mins to sync, might try that tomorrow. But for the moment at least it's half working!
Having an issue pairing my Motoactv to the new bluetooth headset I just bought, the LG Tone+ (HBS-730). Motoactv won't even see it. Headset connects just fine to the phone, and Motoactv connects to phone and old headset (Motorola S10-HD) without a hitch. Tried removing all existing bluetooth connections on all devices. On Motorola's advice, factory reset Motoactv. Nothing seems to be helping.
Does anyone know if this is something that a dev could fix? If it's a simple "no, there's no way modding will fix that", please let me know, so I can return this headset. I really appreciate any help. I bought this thing because it can connect to 2 devices, where the S10 could not. Doesn't do much good if it won't pair, does it?
I couldn't find a better place to put this, since Motoactv doesn't have its own section. Hope that was OK.
davidam091 said:
Having an issue pairing my Motoactv to the new bluetooth headset I just bought, the LG Tone+ (HBS-730). Motoactv won't even see it. Headset connects just fine to the phone, and Motoactv connects to phone and old headset (Motorola S10-HD) without a hitch. Tried removing all existing bluetooth connections on all devices. On Motorola's advice, factory reset Motoactv. Nothing seems to be helping.
Does anyone know if this is something that a dev could fix? If it's a simple "no, there's no way modding will fix that", please let me know, so I can return this headset. I really appreciate any help. I bought this thing because it can connect to 2 devices, where the S10 could not. Doesn't do much good if it won't pair, does it?
I couldn't find a better place to put this, since Motoactv doesn't have its own section. Hope that was OK.
Click to expand...
Click to collapse
If the MotoACTV does not see the headset while the headset is in pairing mode then it won't work. It will not pair with something it cannot see. Not sure why it wouldn't see it though. The MotoACTV uses bluetooth 4.0 so the LG's bluetooth 2.0 should be seen with ease. My suggestion would be to remove all bluetooth devices from MotoACTV. Reboot the MotoACTV and try again. Also make sure that ALL other devices have their bluetooth turned as so they don't see the LG and try to pair with it. If that doesn't work then odds are it won't work at all.
I think this new version of the headset is Bluetooth 3.0. It's the Tone+ 730, not the Tone 700 original (which, apparently, has no issues pairing with the Motoactv).
davidam091 said:
I think this new version of the headset is Bluetooth 3.0. It's the Tone+ 730, not the Tone 700 original (which, apparently, has no issues pairing with the Motoactv).
Click to expand...
Click to collapse
MotoACTV is still 4.0 so it should be compatible with 3.0, good luck
pairing
Ill let you know i own one of these headsets and should be recieving my motoactv in the mail soon.
Any ideas on the issue guys? I have a Motorola h500 and an LG-HBM 235 and neither will pair with the motoactv. It drives me absolutely nuts that the Motorola headset doesn't even work with the motorola motoactv. I mean really, WTF man? I don't want a big stereo headset. SMH. If i could finally get bluetooth audio, this thing would be great. In fact, they need to make a new model with a speaker and mic then it would be the greatest!
Figured it out. Your bluetooth earpiece/headset must be A2DP compatible.
heat22 said:
Figured it out. Your bluetooth earpiece/headset must be A2DP compatible.
Click to expand...
Click to collapse
I can't post links yet, but on the LG site, it says the 730 has A2DP...
Man, this is driving me nuts. I love these headphones, and they seem awesome for running. But I'll never know at this rate...
davidam091 said:
I can't post links yet, but on the LG site, it says the 730 has A2DP...
Man, this is driving me nuts. I love these headphones, and they seem awesome for running. But I'll never know at this rate...
Click to expand...
Click to collapse
I have these headphones as well but have always had them paired to the phone. I just tried to pair them with my actv just to see if my results were any different but unfortunately, I have the same issue.
It may be possible to pair them through a third party app but I haven't tried.
Artimis said:
I have these headphones as well but have always had them paired to the phone. I just tried to pair them with my actv just to see if my results were any different but unfortunately, I have the same issue.
It may be possible to pair them through a third party app but I haven't tried.
Click to expand...
Click to collapse
Any suggestions for 3rd party apps that would do this? I'm willing to try.
Also, does anyone think that modding the ACTV with some of the work the guys here on XDA have done will have any effect? I'm reading threads dealing with similar problems with other devices (e.g. car kits) and some are saying its a bluetooth driver issue. Maybe a custom UI will include different bluetooth drivers?
I know it's annoying to hear people ask for free work, but if any of you ACTV programmers/modders think you can tackle this issue, we'd all really appreciate it. It's incredibly frustrating when you buy 2 things that should work together just fine, but for some unknown reason, just don't.
Thanks!
davidam091 said:
Any suggestions for 3rd party apps that would do this? I'm willing to try.
Also, does anyone think that modding the ACTV with some of the work the guys here on XDA have done will have any effect? I'm reading threads dealing with similar problems with other devices (e.g. car kits) and some are saying its a bluetooth driver issue. Maybe a custom UI will include different bluetooth drivers?
I know it's annoying to hear people ask for free work, but if any of you ACTV programmers/modders think you can tackle this issue, we'd all really appreciate it. It's incredibly frustrating when you buy 2 things that should work together just fine, but for some unknown reason, just don't.
Thanks!
Click to expand...
Click to collapse
Perhaps something like this could work? https://play.google.com/store/apps/details?id=com.IG.BluetoothManager
Alternatively, if your device is rooted there are .conf files under /system/etc/bluetooth/ that could potentially be modified to get this working. For example, audio.conf could be modified to remove "Disable=Headset" as well as enable HFP. These changes could possibly resolve the issue but I haven't tried tinkering with them.
Artimis said:
Perhaps something like this could work? https://play.google.com/store/apps/details?id=com.IG.BluetoothManager
Alternatively, if your device is rooted there are .conf files under /system/etc/bluetooth/ that could potentially be modified to get this working. For example, audio.conf could be modified to remove "Disable=Headset" as well as enable HFP. These changes could possibly resolve the issue but I haven't tried tinkering with them.
Click to expand...
Click to collapse
Ok, so I decided to tinker a little and the app I mentioned did not work.....neither did some of the modifications I made to to the audio.conf file.
However, I did download this app:
https://play.google.com/store/apps/details?id=es.qrr.android.btoolkit
In the app settings, I enabled experimental mode and was able to find the HBS-730 headset and pair with it. Unfortunately, I wasn't able to go any further than that. Even though it is paired, music wasn't routing to it (granted I didn't use the stock music player -- that may have worked).
I believe the actv is treating the HBS-730 like a phone, tablet, or comp rather than just a headset which is why it is not interacting directly with it. There may be another app with root privileges (like the original app I suggested) that could possibly route the audio correctly but I haven't had the time to tinker with it and don't typically need audio output from my actv anyway.
Hope this somewhat helps.
Artimis said:
Ok, so I decided to tinker a little and the app I mentioned did not work.....neither did some of the modifications I made to to the audio.conf file.
However, I did download this app:
https://play.google.com/store/apps/details?id=es.qrr.android.btoolkit
In the app settings, I enabled experimental mode and was able to find the HBS-730 headset and pair with it. Unfortunately, I wasn't able to go any further than that. Even though it is paired, music wasn't routing to it (granted I didn't use the stock music player -- that may have worked).
I believe the actv is treating the HBS-730 like a phone, tablet, or comp rather than just a headset which is why it is not interacting directly with it. There may be another app with root privileges (like the original app I suggested) that could possibly route the audio correctly but I haven't had the time to tinker with it and don't typically need audio output from my actv anyway.
Hope this somewhat helps.
Click to expand...
Click to collapse
I had similiar problems pairing my motoactv with a pair of UE 9000's. It could see the device, but would not pair through the stock menus. Tried downloading some third party bluetooth managers and was unable to get any audio. I believe it has something to do with Apt-X codec for bluetooth not being implemented in 2.3 gingberbread on the motoactv
Artimis said:
However, I did download this app:
Click to expand...
Click to collapse
Here's where I lose all credibility (and help)...
You mean download the app to my ACTV, right? So... How do I do that?
How do I download 3rd party apps to the ACTV? I haven't modded mine at all. Do I need to do anything to it?
I realize I have just exposed myself as a NOOB. Alas, I had no choice. Please continue to speak to me.
davidam091 said:
Here's where I lose all credibility (and help)...
You mean download the app to my ACTV, right? So... How do I do that?
How do I download 3rd party apps to the ACTV? I haven't modded mine at all. Do I need to do anything to it?
I realize I have just exposed myself as a NOOB. Alas, I had no choice. Please continue to speak to me.
Click to expand...
Click to collapse
No worries .
Yes, you'll need to download the app to the ACTV. It will require rooting of the device and installing a custom ROM is the best way to get everything necessary for the market to work so that you can install these apps.
There is a step-by-step tutorial in the MOTOActv rooting thread in this forum.
Any further updates?
Just curious to see how this solution worked out. I am having the same problem and am definitely a NOOB. Attempting to download an app to my Motoactv seem a bit daunting to me...