Related
Hi I'm new to the site, i had read a lot post about upgrading roms from different companys, i read people describe how good the a2dp quilty is, but the problems comes, i first upgraded the rom to T-Mobile , then i found there are a high pitch nosie, at first, i though it was just my earphone, after i changed it, it still the same, then i upgrade to the QTEK rom, the nosie still comes, the nosie comes as the singer start to sing!!! it makes my so dizzy, i had try to link my BT to my PC, but they sound much different! no nosie plus clearer sound!
the second problem is that when a phone call-in, the ringtone goes via BT rather than built-in speaker???
the third problem is if you set ur BT as both hands free/set and wireless stero, during a connected phone call, if you press any button on the dial pad, all the sound will gone, but the phone is still connected, i found this problem when i using my voice mail?!
also after i update to the non-O2 rom, my phone is no longer accept any MMS, i already config all the setting from O2, is just that i don't have my MMS acount appear on my mail box. i also try the .cab setting file too!
My A2DP BT is i-Tech S35
ROM Version: 1.30.77WWE (QTEK)
Radio Version: 1.09.00 (QTEK)
ExtROM Version: 1.13.188 WWE (O2)
Many Thanks!!!
Was it just me than having this problem???
- I've not the first problem.
- I've the second problem
- I never experienced third problem
:wink:
http://forum.xda-developers.com/viewtopic.php?t=46540
Click on the above link , download the file and run it on your phone, do not alter any of the options, just click next on everything it will fix your MMS problem
thx a ur advice coff... but it still doesn't work, plus i starting to think that the nosie might cause by my s35, due to the campasility.. (sorry can't spell)
Hi MicmiC901,
Yes, it probably is something "locally" with your phone/headset/area/etc, since I also have same experience as asci, meaning;
1. NO, don't have that problem
2. YES, I have same issue (to me this is actually OK, since when headset is connected, I WANT it to only ring in the headset)
3. NO, never experienced this problem
I use the latest Qtek ROM with AKU2 and A2DP, but have never experienced that high-frequent-noise-issue you mention with any other of the A2DP ROMs on my JasJar (TMobile Germany ROM, a custom-ROM from the forums).
so RonnyGydar, which bt headset u using @ the moment? i just try with my friends logitech bt headphone, it get worse than my i.tech, sound get Stuttering , so i think i better change a new bt, would u recommand moto ht-820?
Hi MicmiC901,
Sorry the veeery slow response...but now I have even one more BT Stereo headset...so then you get the "bonus" of even more info in my reply!
I have 3 BT Stereo Headsets, and here is a short summary of experience of them all.
HP BT Stereo Headphones (same HW as the Logitech ones as I understand).
Sound is good, clear, OK bass. Nothing exceptional, but I was very pleased with them. Sound could be a bit higher at the highest volume...if you plan to use then in noisy environments...but not really an issue...since they are quite loud.
Motorola HS820
Soundwise (clarity and bass) very simmilar to the HP ones...can't point my finger on any differences. But they seem actually a little less loud than the HP ones...so with these I struggeled to hear Podcasts when I sat on a bus going through tunnels. The HP headphones are slightly louder, I think.
Bonus of these are the excellent batterylife and miniUSB plug...plus the HP ones do not have a microphone, so the HP ones are only for music. So I would easily chose the Motorola's before the HP headphones.
One minus for me with the Motorola's are that they hurt my ears after a couple of hours of use. ...that at lack of "powerfull" bass, got me to look at the i-Tech BluePRO's...
i-Tech BluePRO
These have very good bass (and they sure look like they should have it too...pretty big earmufflers...with these, you look like you are working at a construction site or something, but the clarity of the sound is actually worse than HP and Motorola...they sound a bit fuzzy.
...but I still use these all the time...mainly for two reasons. One is the excellent bass (I like to listen to techno and trance...and then bass is important, the other is that they isolate outside sounds (due to the enormous padding), so I can have the sound as low as I prefer...and STILL hear all my music without disturbance from other sounds in the environment (like sitting on the bus in a tunnel, or at a noise Gym).
It also seems that there is quite a bit difference in how the different manufacturers implement BT profiles.
My Motorola and i-Tech BluePRO have problems with "Pause/Resume"-button on headset when used with my JasJar (Pause works, but not resume...or opposite...not sure which it was, dont have the headsets with me today)...but the HP ones does not (I tested them a couple of times, and the HP headphones worked all the time)!?
Re-connection after a time without use seems also to vary a bit. The Motorola I can turn off/on the headset, and they reconnect automatically to my JasJar. The i-Tech BluePRO's I must choose re-connect in "Bluetooth settings" on my JasJar every time I want to use them.
The "famous" "lag-issue" everybody experiences I experience with all my headphones in some situations...and it does not seem any better or worse among the headsets. It seems to also be affected by general radio disturbance, since I have a lot of problems with lag at work, but no problems at all at the Gym (which is good for me...since that is the place I am most happy with having my wireless headphones), and some issues at home.
Hope this was of any help!
actually i have the problem micmic is talking about.. it happened when i upgraded my wiz to a newer rom to get the a2dp function. eventually i do not have a bt.stereo -headset yet.. (coming in about 2 weeks) but i have the issues with the sound. it's almost like a bad bitrate or something? ..wierd it is since i remains even if i downgrade my rom. =/
Hi epluribus and MicmiC901,
Is the "stuttering" you both mentioning the same as I call "occational lag"?
IF it is...it you should certainly not have it when you do the following test;
1. Reset your JasJar/Universal (to clean memmory completely)
2. Started listening to music over headset with...
3. The Universal lying on the desk in front of you completely still 50cm from your face
4. You sitting completely still
5. No WiFi on close to you.
...this test is completely overkill...but if it STILL stutters in that "controlled scenario"...well then it must be something different with your Universal or headset HW. Cause I can walk around with my JasJar (also in areas I know there are 5-6 WiFi connections active...like my appartment), and even put the JasJar on the table and walk 5-10 meters away from it...and have no or at least nothing more than an "occational stutter"/"lag".
It seems to be two major factors affecting this "stuttering"/"lag" (from my experiences at least...I have used A2DP a lot with my Universal...couple of hours every day);
1. Universal struggling outputting(RAM/CPU...or both!?)
One help here is to apply the registry "A2DP priority" fix (found it in the forums here).
Another is to close all programs before using it (I usually do not do this...I usually only do it in hindsight when I get the problem).
2. Signal between Universal and headset struggling (obstructions between Universal and headset, WiFi nearby, so forth)
I for example get this problem if I put my Universal in my trouser pocket (I know, I must have big pockets, and walk around, I get stuttering/lag occationally. If I then take it out, and hold it in my hand farily still when I walk...no stuttering. I have found, that when I walk, it is OK to have it in my backpack/rugsack...then for some reason it very rearly stutters...so I usually do that.
But when I walk of the bus at work, and walk into the "campus" of my workplace, which is cramped with radiotransmitters (is norways largest Telecom company)...I get a lot of stuttering, and need to take it out of backpack, and hold it in my hand, at it gets a lot better.
In short: A2DP with the Universal works, but is sensitive to disturbance/obstructions/moving around...and to make it worse, it is also sometimes dependant of the Universal itself struggling with CPU/RAM.
I have BTW had the exact same problems before with Qtek2020 and Qtek9090 (which I got hold of some "A2DP patches", when I had those devices). ...but I really had a LOT more stuttering with those two...so much so, that I never used A2DP with them on a daily basis.
...so it can seem that HTC is getting slightly better on each new device...?
Hope this info can be of some use!
...but it might not...if my assumption at the beginning here is wrong, and your "stuttering"-issue is something completely different than the "lag"-issue I talk about!?
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!!
Hello everyone,
I am trying to understand what is the key fault of my HTC Desire. I since have changed to a HTC One X, due the fact that my Desire has lost both full phone networking and sound capabilities. The rest of the device works like a charm, currently with Paranoid's Jelly Bean rom, even on heavy load.
The phone has gone through three accidental falls (bad luck serie), that required me to change the amoled screen only three times up to now. The original digitizer is still like new. After the last fall, it started to develop some sound issues before the two ones I expose here. It started with the music only in one of the headset speakers thing (by compressing the left part of the phone, I could get back music in both ears).
Rapidly, I discovered my Desire could no longer catch the phone network, and so could no longer be used for calls, SMS or mobile Internet.
Additionally, no sound comes out from anywhere : front speaker, back loud speaker, headphone. The microphone appears muted as well. The volume settings are all at maximum, including using a more complete audio manager app from the Market. Headset detection plug/unplug works fine.
So apart from the other functionalities that all work (screen, digitizer, vibrator, Wi-Fi, Bluetooth, SDCard , Sim card (detected and activated), USB, heavy load from benchmarks and games, volume buttons, camera, etc...), the phone is rendered useless by not being able to catch phone networks and not produce any kind of sound.
I have replaced some parts of the phone since this issue has begun : the upper board with flex cable (that was tired) and the loud speaker (was tired as well). It has not solved these issues (it only solved appearing detection issues due to the tired flex cable and failing volume buttons).
I now use the Z-device test app to try to diagnose the issue. I am not sure I understand them, but they may give hints :
- He is detects the SIM card well and displays its information.
- He detects the phone as gsm type, but is unable to display the gsm cell id (blank space). He finds the device id (long number) and the software version (00).
- Data state is therefore set to disconnected.
- Multemedia chip is undetected (blank space)
- ALSA version is undetected (blank space)
- SCO for off-call use is set to true
- Microphone is set to muted
- Speaker phone and wired headset are, whatever happens, always set to false.
This is it. I haven't got further yet. I try to situate the possible hardware fault, since full wipe and reflash has not solved the issue. I only have those suspects :
- What is called the Wi-Fi cable, that is damaged (the thin cable can come out easily from one of it's metal end, while it is clipped properly).
- What is called the antenna cover (that looks like yet another plastic piece, with two metal pins on the left side), the cover being slighly cracked on the right side but still completely screwable.
- One of the motherboard's IC chips or component for an unknown reason.
The phone is in good state and works well now, aside of these two key features. It does not look like it has fallen down once, a shame. What is your opinion on this? Do you have ideas or suspicions?
I thank you by advance.
About your sound issues (speakers, headphone), sounds like your amplifier died.
TheRamon said:
About your sound issues (speakers, headphone), sounds like your amplifier died.
Click to expand...
Click to collapse
Probably. I doubt the isseu would come from the so called Wi-Fi cable as it may not both transport sound and act as an Antenna.
I therefore need to see if it is possible to replace the amplifier chipset. Might require precision soldering though.
Still idea concerning the gsm fault...
Concorad said:
Probably. I doubt the isseu would come from the so called Wi-Fi cable as it may not both transport sound and act as an Antenna.
I therefore need to see if it is possible to replace the amplifier chipset. Might require precision soldering though.
Still idea concerning the gsm fault...
Click to expand...
Click to collapse
you would probably need hot-air to do that
Has anyone noticed something similar with their LG G4?
When playing music, or podcasts, using different apps (eg CloudPlayer, GMusic, Pocketcasts) via bluetooth in our newest car (Honda Civic '14) I get a noticeable scratchy electric noise now and again - sounds a bit like an old jack cable that needs some cleaning.
Weirdly though, when I use the G4 in our other car (another Civic but this time a '10) which I don't have bluetooth set up for - but rather use the headphone jack and AUX on the car. This also has some weird noise issues on the left channel too. Not like the sound on the other car - but this is amore obvious distortion/static/crap. It's not a continual noise like an out of tune TV (like you'd get in the old days), but it's a frequent intermittent noise.
Do you think this is due to the G4 - or what?
It seems weird to me that in the two cars there are similar audio issues, via different input sources.
Coincidence?
I haven't tested either car with other devices yet - but before I do, I just wondered if someone on here had experienced similar.
subharmonic said:
Has anyone noticed something similar with their LG G4?
When playing music, or podcasts, using different apps (eg CloudPlayer, GMusic, Pocketcasts) via bluetooth in our newest car (Honda Civic '14) I get a noticeable scratchy electric noise now and again - sounds a bit like an old jack cable that needs some cleaning.
Weirdly though, when I use the G4 in our other car (another Civic but this time a '10) which I don't have bluetooth set up for - but rather use the headphone jack and AUX on the car. This also has some weird noise issues on the left channel too. Not like the sound on the other car - but this is amore obvious distortion/static/crap. It's not a continual noise like an out of tune TV (like you'd get in the old days), but it's a frequent intermittent noise.
Do you think this is due to the G4 - or what?
It seems weird to me that in the two cars there are similar audio issues, via different input sources.
Coincidence?
I haven't tested either car with other devices yet - but before I do, I just wondered if someone on here had experienced similar.
Click to expand...
Click to collapse
Had the issue on g3 my fix was when i use music i had to turn off all other sounds even screen toich sounds
"i had to turn off all other sounds even screen toich sounds "
I don't understand. I don't have any other audio on as far as I know when the bluetooth is on.
Are you saying that the phone needs to be set to silent, in order for bluetooth streamed audio not to be affected?
The thing I find weird is that it's only the left channel which has issues - right channel seems perfect.
And this is both for when using bluetooth, or minijack cable.
Why should only one channel be affected?
I've got same issue with sound via bt in my car with a parrot receiver. Scratches for a few secs after connection, then it stops. But continuous scratchy sound when using gmaps or waze
Hi everyone. I ask you for help because I am a GOLF 5 owner with an Eonon GA5153F installed (which should be an MCTB) originally with Android 4.4.4 which I then brought to version 5.1 with a rom
The problem he has always had is related to the audio quality in calls. Until I used it, I used the hands-free phone and that's it, but now that my wife uses it, I prefer to be careful while driving and therefore call and do everything via the car radio. The problem is that the audio I get is really HORRIBLE. Practically whoever is on the other side of the phone hears nothing, hears 1 word every 5 and at a very low volume (I've already gone to the factory settings and turned up the bluetooth but nothing changes).
I've read that many of these Chinese have made hardware changes, removing the capacitor and resistor on the bluetooth module or similar, but I can't find anything about my car radio. Have any of you done this? Does anyone of you have photos, videos or something that tells me on mine which component I have to desolder, which track to open, or what to do?
Please because the quality that this car radio has on call is really a shameful thing!
Thanks a lot to everyone
P.S. Currently I have connected (in the back of the car stereo) an external microphone (the one that was inside the car stereo package)