I am pretty new to Android and still trying to get all the grips on I need. As of now, there is one thing that really bugs me badly.
I use the device for Sat-Nav driving a lot, I have a semipermanent installetion in my car from my previous smartphones. Basically just a power feed and a 3,5mm Jack that come out of the dash panel where the device holder is mounted. I recharge plug in for recharge as needed. The audio jack goes into the device, from there to a so-called Fastmute box behind the dash which is connected to the stereo head unit (the loudspeaker output cables running away from the head unit to be specific. The Speaker lines are interrupted by the box and just pass through whatever audio is being played back by the stereo. However, once there is current on the 3,5 audio jack (i.e. speech from the SatNav) the music immediately goes mute and you can hear the turn instructions in perfect quality through the car speakers. Once the signal fromthe satnav dies down stereo music comes back.
For my taste this beats most commercial, fixed systems.
Now, since I am on Android weird stuff happens.
On a first testrun shortly after I gut the Desire (which was o2 branded stock 2.1 at that point) I noticed that I do not get any announcements through the fastmute. Checked the jack, opened the dash to check internal wiring, retried a mp3 player. It's all good on that side. The accouncements come through the device speaker, hard to hear, easy to miss a turn etc. I do not why or how, but it seems that the audio routing takes a route different from other audio. This had me pretty much meh!
Well few days later, now with a ModaCo R8 custom ROM and Froyo I was hoping for good luck and gave it another whirl. Of course, no dice. When I plug in the jack of the supplied headset (which I assume doubles as a handsfree) I get the symbol for that in the upper symbol bar. When I exchange that headset jack with the regular 3,5mm jack the symbol looks different, but still vaguel like a set of speakers.
But now here comes the completion of the mindfaq... I had the SatNav volume at about medium (so barely hearble with driving ambient noise) when the phone went and I took the call through the Bluetooth Handsfree instaalled in my car and was distracted by the call (the car came euipped with the BT Handsfree from factory, so the stereo goes to "pause" and the conversation is routed into the vehicle speakers.. A few minutes into the call I suddenly hear a perfectly well understandable, clear turn instruction hopping into the phone conservation. I was extremely intrigued and was hoping that I discovered that CoPilot can route instructions either into A2DP or more likely emulate a "call event" that results in routing the audio into the according BT profile.
However, after that singularity I tried reproducing this for a god part of an hour, driving a route that forces many instructions from the SatNav, all the while calling my own answering machine fo have an connection established.
Sorry for the lengty explanation. Questions:
1 Has anyone ran into this before? What was your solution? Bear with it, switch SatNav software, avoid listening to music in oder to not miss any turn directions?
2. Is there a hack, hidden configuration that would enable me to _force_ this audio routint into the direction of the BT Handsfree, making it think it is an incoming call?
As a fellow co-pilot user I share your frustration.
You will probably find that it's nothing as technical as it not routing to bluetooth or whatever.
Co-pilot has a nasty habit of messing with it's own volume setting when a headset is plugged in. It tends to reduce itself down to zero without notification or cause. You would try to reset the volume, but firstly, it wont go more than a third of the way up, and secondly, it will simply jump back down to zero again on it's own.
They know about this issue and their response is not to use it with a headphone jack!
It is rather annoying!!
Related
Hi All,
This morning I was listening to my favorite Podcast through the speaker of my SX66. I then headed out the door (still listening) and plugged the unit into my car stereo via the 2.5mm audio jack. I continued listening over the car stereo with no problems during my drive to work.
When I parked the car, I unplugged the SX66 expecting to have the audio switch back over to the speaker so I could hear the conclusion of the Podcast as I walked to the building. However, when I unplugged the unit there was complete silence. If I plugged it back in, the audio played normally through the car stereo again.
After playing around a bit, I found that except for the playing of ringtones for incoming calls, no sounds come from the speaker. The volume controls have no effect, and anytime I plug the headset in, I can hear all of the sounds normally through the headset (menu clicks, WMP, etc.).
I tried soft resets followed by more desparate hard resets. No effect. What in the world would cause the system and WMP sound to stop playing through the speaker only (headset OK), but ringtones for incoming calls play through fine? I'm confused. Is this a software or hardware problem? Anyone seen anything like this?
:?
Thanks for any suggestions,
Paul
Paul, it sounds like you have broken the audio jack socket on the unit, they have a switch type arangement in them to disable the speaker when on external sound, if a bit breaks off (which is what I suspect) then the removal of the jack plug will not re-make the connection for the audio to route back to the internal speaker - sorry to be the bearer of bad news - it needs a repair mate - Mike
Thanks for the suggestion, however it turns out this is a software problem. :lol: Specifically, it has to do with the BT patch that I was running (Cambridge Silicon Radio Ltd. BHCS, posted here: http://forum.xda-developers.com/viewtopic.php?t=36626&postdays=0&postorder=asc&start=75). It seems that if I add any BT device at all (even non-audio devices like a keyboard) and have the tray icon enabled (BTIcon.exe), then I have no sound. I'm not sure whether it's the patch, BTIcon, or a combination of both.
I removed the patch and took BTIcon.exe out of the Startup folder and everything went back to normal.
Paul
I have such problem
Sorry, I really tried to find something like this, but stuck.
Ican't solve it, and Removing BTtray - doesn't helps.
After update from
PH20B_0_B_WWE_E_BRIGH001_1.22.00_0_0_1.22.126_1.06.00_06.00
to
PH20B_0_B_WWE_E_BRIGH001_1.22.00_0_0_1.22.169_1.06.02_06.02
- same result.
Please - any ideas?
Thank you.
Hey so I've tried searching other threads for my specific challenge and none of them seem to really touch on this so here goes.
I have a Samsung Fascinate, I'm rooted and I've flashed a bunch of kernels and ROMs no problem and as far as I can tell my Bluetooth works fine and audio works fine.
My issue is this: My car supports hands free calling via bluetooth and i've paired them with no issues and have made/received calls no problem. I've also used my phone to play music through the AUX cable no problem. I know that my car STEREO does not support Bluetooth and here is where i run into a problem.
I have my phone plugged in on my way to work singin along to my favorite tune when a call comes through. But (I think) when the AUX is plugged in, it interferes with the audio when connected to the bluetooth. Basically i can hear a call coming through on my car stereo and i can push the buttons on my steering wheel for functions on the phone but i can't hear and the other end can't hear me. So i have to end up unplugging the AUX cable out then the audio returns.
First off... is it just me? did I do something wrong along my journey of flashing all sorts of stuff? cuz i could've sworn at one point (i think before i went voodoo) it was all working fine together, but i could be wrong.
So if it's not something I did, is there a headset adapter out there with controls and possibly some kinda screen for like caller id or at least current track? like something that can connect to regular earphones that has an inline mic and controls.
Unless you fine folks have a better idea I would love to hear them. (I don't have a budget for this... just want to get it working... unless it's cheaper to buy a new car that can support it all)
Thanks
I think this is a fascinate specific or limited problem
http://forum.xda-developers.com/showthread.php?t=894452
I'm using an HTC Touch Pro 2. It lacks a 3.5mm headphone adapter, so I thought, I'd get a bluetooth headset with A2DP support to get around it. I've bought a Plantronics Voyager Pro+ and been using it the last few days, however, I've noticed a few problems:
1) Ringtones don't go directly to the headset. I've fixed this halfway with a mortscript to adjust the handsfree options in the registry. Now my ringtone goes to the headset, but the ringtone that plays in the headset that the headset comes with plays along with my ringtone. Not cool.
2) Half the time when I'm walking around listening to music or in my car on a call, I get my sound dropping in and out or the people I'm on the phone with complain about me breaking up a lot or being static-y. Are there certain things around me that attribute to this? The first thing I had thought was my phone's radio playing into the bluetooth communication with the headset, but I'm just guessing.
I've considered getting a new headset instead, but before I take that plunge, I thought I'd try to gather some input on other perspectives. If I do go for a new set, what are some suggestions for one in the $70-80 price range to start with?
I have the Samsung Car dock, and I have my phone paired to my stereo (Sony DSX-S300BTX [aka. alphabet soup]) with an external mic which I have mounted up by my visor. I can use vlingo once every time I'm in the car, and after that it goes haywire trying to listen all the time. Is there a way to turn down the sensitivity from the phone, or do I have to do it in the stereo somehow? I have a relatively loud car (Mustang GT) but the exhaust is stock, so I don't think it's that loud. I just want to be able to use the voice recognition reliably.
When you trigger the speech recognition, make sure you leave about half a second of silence before you actually speak. I think it uses that "silence" part to actually build a baseline. That helped quite a bit for me.
Under the Voice talk Settings, Motion, turn off Motion Activation. Most vehicles shake and vibrate too much for that to work right anyway.
Did any of these work? I have the car holder (no bluetooth or audio in/out) and I want to use the phone as my navigation with voice commands. Problem is, unless the car is at a complete standstill, voice talk will hear "Hello Galaxy" but then it won't hear anything after that. The red bars in the microphone icon are going off the charts indicating its picking up too much background noise. I usually use it in a rental car and I've tried all kinds of cars, all of them fairly quiet sedans. I've also tried it in my friend's Mercedes and same problem. Is there a work around? I've never had the motion control turned on. Thanks.
Anyone have a solution for this one?
I have a 2008 car with factory installed Bluetooth phone interface. The Bluetooth is ONLY for the phone, not music. The car also has an aux in jack for the stereo. (Know where I'm going with this yet)?
Yesterday I was listening to music using the 3.5 mm jack on the phone, and it was also connected by Bluetooth to the car's phone interface. A call came in. The stereo automatically muted like it should but when I answered the phone I couldn't hear anybody there. After 30 seconds or so I hung up.
Then it dawned on me, with something plugged into the 3.5 mm jack, the phone audio may have been routed through that jack instead of Bluetooth. BUT the car assumes that when a call comes in you want the stereo muted so it kills audio from everywhere except Bluetooth. I suppose I could have reached over and unplugged the 3.5 mm jack, but that's inconvenient when I'm driving.
So, the question is, is there any way to set up the phone to always route phone call audio through Bluetooth when Bluetooth is connected?
I have the same issue.
I listen to music in my car via a cable from the headphone jack to my car stereo's aux in. If I get a call over bluetooth, I can't hear anything. If I unplug the cable on the phone side, I can hear the person on my car speakers, and the caller can hear me via the car's mic.
Are you using the stock firmware or a custom ROM? If it isn't a problem on a custom ROM then perhaps it can be fixed. It's very annoying -- my 3-year-old HTC Hero could do this, why can't the S3?
I was told by someone with a different version of the S3 (an international one) that this isn't an issue on their phone.
I'd love to find this out while I still have time to return the phone.
I'm going to try building a "car adapter cable" that feeds audio out the USB port to see if that works, Instructions are in this thread:
http://forum.xda-developers.com/showthread.php?t=1395173
That could be one option. Still seems pretty lame that we have to come up with workarounds for this pretty basic problem.
And I'd love to hear from someone running a custom ROM to try and figure out if it's a hardware or a software issue.