Hi,
My RN8P audio is cut off for first 2 seconds while playing it through Bluetooth headphone. Making the Google map navigation useless. In Other apps also first 2 seconds are cut off.
Please give the solution.
Related
hi
couple days ago i bought thisd stereo BT headset, looks very nice, but i have one big problem, first time i have connected this headset everything was OK, it was clearly found by Universal, shown both of options to use it as HF and stereo headset, checked both of those options, sound was very clear using WMP/pocket Music/ and TCPMP also, but after that, next time i tried to play music i was confused - while using it as stereo headset to listen music hearing voice in headset is bouncing, i can hear it for 1-2 sec., then it is quiet for 5-10 secs, again playing, then stops playing
can you explain it please
thanx
PS: last indra's ROM in use
I´m constantlly getting lag when using Navigon with bluetooth head set. Its cutting out half the sentences and Im loosing important info. Is this a known problem?
Im using the GPS directions driving a MC and am thewrefore not able to watch the screen.
I'm getting this with Co-pilot too...
If the sentence was "Turn left in 100 meters..."
all I hear through my Jabra bluetooth is:
"...100 meters..."
It's almost as though the A2DP has a 'sleep' when there is no audio (power saving?), but then lags when it 'wakes' up.
That's exactly what is happening, it shuts down into a power saving mode when no sound it being sent, I get the same thing with notifications on my Jabra headset, I will get the end of the notification sound as it takes almost a second to "switch on" when the sound is played.
I get silence about every 30 seconds for a split second when playing music or sat nav, through a motorola bluetooth T505?
Any workarounds?
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!!
I've been having a problem where if I connect my phone to my car audio via bluetooth, and use both the music app (MIUI to be exact) and navigation, the navigation sound is EXTREMELY low. And yes, I did turn up the navigation sound to max.
In order to work around this, i have to turn my media volume really low, and then pump up the car audio volume.
I searched through the forums, but did not find a solution to this problem.
Have anyone ever seen this? Is there a fix for this?
Navigation volume is separate, have you tried turning the volume up while the navigation app is in the forefront?
The same thing happens to me on CM7 using Google Listen while connected to my car stereo via the headphone jack. The odd thing is that it's usually normal for the first 1 or 2 instructions and then it goes all weird. I have the nav volume maxed out... No idea why it happens. I've given up and just muted the nav sound and look at the screen periodically.
I got my Redmi Note 5 (SD636 ) 4 days ago and noticed something strange right away. When media is playing through the speaker, let's say from Spotify or YouTube, and I connect the earphones in the jack while it's playing, the phone takes some seconds to stop the speaker and play on the earphones.
Also when I play PUBG and enable my mic in-game, the sound starts playing from the speaker. Like it ignores the earphones completely. To fix that have to remove the headphones, minimize the app, open it again and then connect it once more.
I'm not sure if it's a bug or just compatibility issues, but the earphones are fine. They are the from Samsung and I got them with my Galaxy S7. I currently don't have another pair to test.
Has anyone else delt with that? Any tips?