Related
after the 1.6 update i can no longer use my headphones. i was able to use them with toggle headset widget before. anyone know how i can fix this?
anyone have a solution, i cant listen to music
Me too
I'm having this exact problem. It was odd; when i first installed 1.6 the headphones flicked on and off for all of 5 minutes and then stopped working fully. I have the standard usb to 3.5 converter that came with the phone, and it seems to work in another device.
I tried a couple of fixes that had been suggested to people having a similar problem when they had upgraded to cupcake but neither of these worked.
Halp would be appreciated
What radio version you guys have?
First thing i read on your reply was about cutting throuats and spreading cheese which totally threw me...
Anyway, am using CyanogenMod 4.1.999, and if i'm right in thinking radio and baseband are the same thing..... 62.50s.20.17H_2.22.19.261
I just updated to the latest mod 4.1.9999 and still it won't recognise the headset. It is the original one that came with my G1.
Have searched fairly extensively and can't find anything.
Any pointers or suggestions would be very useful.
theres an app called sound route switcher, its updated and i heard it works, but i dont have a credit card, wish someone would update headset toggle widget
I've come to find out I'm not the only person that has a panasonic kx-th1212b telephone in my home. I use this to link my cell with the house phones after work. I just recently rooted my phone and put on the vanilla new sprint leak modified by damage to keep root access. This rom paired but did not connect to my phone. I'm going to try fresh 2.1.1 today when i get home but I am assuming this is the same issue since its based of the newest sprint leak. Has anyone found a good rom that will allow for hands free bluetooth pairing?
Does it pair as a regular blue tooth headset or does it do something above and beyond that. I haven't had luck with the new leak gettin ANYTHING to connect, everything just about pairs, but nothing connects.
as far as i know it pairs just like a bluetooth headset. Obviously it can make calls and answer the phone. It says it paired correctly, but it never connects.
I know it doesnt help with the panasonic, but I have the Vtech and it synchs flawlessly with my hero
waltkap said:
I know it doesnt help with the panasonic, but I have the Vtech and it synchs flawlessly with my hero
Click to expand...
Click to collapse
and what rom are you using?
the only rom i got to sync with my bluetooth system built in my car is aloysius and the new fresh toast and fresh rom if that helps with anything.
Well, now that the leak is the same as the official rom i guess my bluetooth will never work on this phone again. I just restored my nandroid backup to go back to stock 1.5 and my phone will connect to my phone no problems. I guess that the 2.1 release is what is killing my connection to my bluetooth phone. great work htc. I'm going to write to them and sprint about my issue. glad i didnt use the official 2.1 because then i would never be able to use my home phone again.
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, hopefully this will be a quick, easy question for someone. For some reason, when I try to make a call from my in-car bluetooth, it always returns 'Dialing Failed'.
ie, I push the 'Call' button on the steering wheel, say "Call Bob", the car will confirm "Calling Bob at Home" (which tells me it downloaded the phonebook properly), but then will just say "Dialing Failed".
The phone pairs fine, will receive calls with no issues, will play music and internet radio without a problem, and will even make calls if I hit Dial from the phone instead of the car buttons. It also used to work just fine with my old Motorola Milestone.
So, any suggestions? Is there some setting somewhere I'm missing? Do I have to start downloading some 3rd party apps? (would seem strange if I did)
Currently running Paranoid Android 3.99, stock kernel. Bluetooth is Chevy's MyLink, if it matters.
Thanks for your help!
I also discovered that it will make calls if I say the number instead of the contact name, or if I scroll through the car's screen and select the contact name.
Any suggestions? It just seems odd that it worked fine with a much older phone, but I can't get it to work with the Nexus.
I've tried a few different 3rd party apps, and nothing seems to help - the phone doesn't even seem to see any sort of command, I never see it try to do anything.
Is it something with the kernel? With the radio? Does anyone have this working properly? (ie bluetooth dials from the phonebook downloaded into the bluetooth device). I'd like to have some idea before I start mucking around and wasting too much time.
I'm a little disappointed, I just got the Nexus, and bluetooth functionality should be something straightforward and flawless, not have significant flaws like this.
So I've tried a few different ROMs, different kernels, and different radios, with the same results. Is this a known bug? This must be happening to other people. Is there anyone that can help?
Should I post this somewhere else?
CanAndroid said:
So I've tried a few different ROMs, different kernels, and different radios, with the same results. Is this a known bug? This must be happening to other people. Is there anyone that can help?
Should I post this somewhere else?
Click to expand...
Click to collapse
Does the Chevy MyLink software download your contact list or access the list from a synced phone? If it downloads the list, I'd try removing it and re-downloading it to the car.
GoPadge said:
Does the Chevy MyLink software download your contact list or access the list from a synced phone? If it downloads the list, I'd try removing it and re-downloading it to the car.
Click to expand...
Click to collapse
Yes, it downloads the phonebook. I've re-paired and re-downloaded it numerous times now, with each of the new ROMs/kernels/radios.
I'm thinking it is an Android 4.3 issue, assuming you have 4.3 on your Nexus.
I have had exactly the same issue with my HTC One since I changed the ROM from Android 4.2.2 to 4.3. With 4.2.2, voice dialing worked perfectly when paired with my Camaro Mylink.
Did you ever find a solution?
k818mn1 said:
I'm thinking it is an Android 4.3 issue, assuming you have 4.3 on your Nexus.
I have had exactly the same issue with my HTC One since I changed the ROM from Android 4.2.2 to 4.3. With 4.2.2, voice dialing worked perfectly when paired with my Camaro Mylink.
Did you ever find a solution?
Click to expand...
Click to collapse
Try removing all brackets and hyphens from the phone book numbers. Worked for me.
Not a solution but a workaround.
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...