Related
anyone out there can fix the issue when headset is plugged into 3.5 jack and a call comes in and you can just take the call instead of unplugging the headset?
Thanks,
I guess nobody is bothered by this.... strange
hackercity said:
anyone out there can fix the issue when headset is plugged into 3.5 jack and a call comes in and you can just take the call instead of unplugging the headset?
Thanks,
Click to expand...
Click to collapse
Every phone I've had since the iPhone has done this.
craighwk said:
Every phone I've had since the iPhone has done this.
Click to expand...
Click to collapse
my og droid and droid 2 and incredible did not do this. I was able to take the call with an aux cable plugged in. The mic would work and I was able to use my phone over my car speakers. The thunderbolt disables the mic if the aux cable is not 4 pole, as in has a mic. The only solution I have found is to buy http://cgi.ebay.com/ws/eBayISAPI.dl...49206&ssPageName=STRK:MEWNX:IT#ht_2617wt_1141
I used this in both my cars with the thunderbolt and it works perfectly.
Is this something that can be fixed by the ROM/Kernel developers?
Here's a fix!
Okay guys so here's a work around that I've been using for a while and I don't really remember where I saw it so I'm sorry for not giving proper credit. So you go to Home>Settings>Call>TTY mode> and pick "TTY VCO". The only negative thing is that you're gonna have a few extra icons up there in the notification bar but you get used to them right away.
Does that disable the ability to change in-call volume?
No issue here on Das Bamf Remix 1.7
I've been running Das Bamf Remix and since a few versions ago (1.6 I believe) I have not noticed this issue -- calls work fine with headphones.
I'm pretty damn sure this was fixed, or supposed to be fixed with MR1. Ever since I upgraded to an MR1 based ROM, the issue went away for me. It also fixed video chat. The issue is related to something software based with having 2 noise cancelling mics. Basically, they were cancelling each other out.
Can anyone PM me on how to get needed software to root plz? If asked a few with no responses. Tried one click option but cannot get galaxysense Rom because link 404's
Sent from my ADR6400L using XDA App
ZuneNinja! said:
I'm pretty damn sure this was fixed, or supposed to be fixed with MR1. Ever since I upgraded to an MR1 based ROM, the issue went away for me. It also fixed video chat. The issue is related to something software based with having 2 noise cancelling mics. Basically, they were cancelling each other out.
Click to expand...
Click to collapse
I just tried this on bamf 2.0-5 and I still have the problem. The mic turns off when headphones are plugged in.
This has been addressed, but not thoroughly. It works sometimes, but not all the time and its very irritating when it doesn't work. Maybe when the June 30th update comes in. That's wishful thinking though. My dinc, iphone, droid, all the way back to my touch pro had this functionality.
This has been strange for me to and I posted about it in the bamf kernel thread. Some headphone mics work and some don't. The same mic that doesn't work on my phone works on other non htc phones.
Sent from my Xoom using XDA Premium App
I've run stock, rooted, Das BAMF 1.4 - 2.0.5, and preview4. Every single one cuts off the mic if I have headphones in. Very frustrating. I took to buying headsets with built-in mic. Unfortunately, they all seem to last about 3-4 weeks before going bad and randomly hitting play/next/back on my audio book app. I've gone back to standard headphones and would LOVE to be able to leave them in and use the built-in mic.
I have a set of Rockfish stereo headphones. they have been clear in calls and listening to music. Connected them to the sensation and now everybody that I talks to says that they hear an echo on their end when we are talking. This did not happen with my 2.0 version on the hd2. Is anybody else having a problem with migrating their previous 2.0 headphones to the sensations 3.0 bluetooth format?
If not, does anyone know how I can remedy this (if there is one)? Thanks in advance.
My Sony DRBT100CX's are 2.1 and work great.
steve austin said:
I have a set of Rockfish stereo headphones. they have been clear in calls and listening to music. Connected them to the sensation and now everybody that I talks to says that they hear an echo on their end when we are talking. This did not happen with my 2.0 version on the hd2. Is anybody else having a problem with migrating their previous 2.0 headphones to the sensations 3.0 bluetooth format?
If not, does anyone know how I can remedy this (if there is one)? Thanks in advance.
Click to expand...
Click to collapse
Bluetooth version has nothing to do with Sense version.... different animals altogether.
at a loss...
NRGZ28 said:
Bluetooth version has nothing to do with Sense version.... different animals altogether.
Click to expand...
Click to collapse
well i can't figure out why everybody on the other end is now getting an echo when i speak. this never happened with the hd2.
NRGZ28 said:
Bluetooth version has nothing to do with Sense version.... different animals altogether.
Click to expand...
Click to collapse
I think he's saying Bluetooth 3.0 not Sense 3.0........
He is asking if anyone coming from Bluetooth 2.0 is having problems with their headsets on bluetooth 3.0
Ye. I have the same issue. The Phone will sync to bluetooth in my car but everyone states they get echo feedback. I have posted email to HTC, see what they come up with.
nice catch.
KillaHurtz said:
I think he's saying Bluetooth 3.0 not Sense 3.0........
He is asking if anyone coming from Bluetooth 2.0 is having problems with their headsets on bluetooth 3.0
Click to expand...
Click to collapse
Thank you for pointing that out to me. I should have caught that he was unclear about my point.
yes, BLUETOOTH 3.0 & 2.0 compatibility. Not Sense 3.0
rickscheibe said:
Ye. I have the same issue. The Phone will sync to bluetooth in my car but everyone states they get echo feedback. I have posted email to HTC, see what they come up with.
Click to expand...
Click to collapse
i thought it was just me. i will call tomorrow and see how much of the run around they give me.
steve austin said:
i thought it was just me. i will call tomorrow and see how much of the run around they give me.
Click to expand...
Click to collapse
Hi,
I have a similar problem.i have a Sennheiser bluetooth earpiece. It works well on my Hd2, but on some Sense 3.0 ROMS , it would sound bubbly almost underwater.I have found the same thing with the Sensation.
So maybe it does have something to do with Sense 3.0.
I have the same problem. When using my bluetooth speakerphone in the car, the other caller complains of echos and bad background noise. I have no problems when I use it with my Vibrant. This sucks.
I have the same issue with my carkit. Lots of complaints from receivers:
Bluetooth carkit quality
I've been having issues with BT as well. Echos as you describe on calls but also i can only connect to media upon initial pair. I have jambox, jawbone and a stereo headset that all are A2DP but only connect to phone audio when i connect to them. They will do media the when first paired. I have to keep unpairing and pairing to get media. Was like that on all 3 sensations i've had. TMO US needs an update in a bad bad way.... This is the buggiest phone i've ever had
nugzo said:
I've been having issues with BT as well. Echos as you describe on calls but also i can only connect to media upon initial pair. I have jambox, jawbone and a stereo headset that all are A2DP but only connect to phone audio when i connect to them. They will do media the when first paired. I have to keep unpairing and pairing to get media. Was like that on all 3 sensations i've had. TMO US needs an update in a bad bad way.... This is the buggiest phone i've ever had
Click to expand...
Click to collapse
Totally agree. May take mine back.
Sony mw600 headphones, Kenwood DDX-812 and my pc all pair fine for me.
Sent from my HTC Sensation 4G using XDA Premium App
Same issue. Jabra BT2015 (Bluetooth version 2.0) was working fine with my HD2, but with the Sensation, callers complain of excessive background noises.
Thaught it was my phone, but tried yesterday with an another Sensation in the shop & was the same. Too high noise. So I thaught it must be the headset.
I have used my IOGEAR Solar Bluetooth Car Kit with my MyTouch 3G and with my Vibrant and never had complaints from callers. My fiance won't even talk to me when I use it with my Sensation. She complains about an echoing noise and horribly loud background noises.
Bluetooth issue - no audio on carkit
My bluetooth pairs with my car kit, can answer and hangup with car kit, but no audio goes through car kit.
It did work when i first got my sensation.
I got root (temp) and deleted some "bloatware" (maybe something i shouldn't have), then I upgraded to latest software. Now i have above problem.
anyone know is upgrade may have caused problem - or do i need to replace driver???? if so anyone got the file?
Bluetooth issue - no audio on carkit
My bluetooth pairs with my car kit, can answer and hangup with car kit, but no audio goes through car kit.
It did work when i first got my sensation.
I got root (temp) and deleted some "bloatware" (maybe something i shouldn't have), then I upgraded to latest software. Now i have above problem.
anyone know is upgrade may have caused problem - or do i need to replace driver???? if so anyone got the file?
bumping this for the people who might have missed this thread
I have the Jawbone Icon and while I don't have an echo incoming sounds are hallow and tinny with a bit of crackle. Sounds like crap. Although the people I speak to say I sound great. On my SGS2 people say I sound great however they say I don't sound as good.
Hello,
Pardon if this has been answered already, I simply did not find my exact question answered.
I am using my unmodified Nexus 5 (not even rooted), with the latest KitKat (v.4.4.2 build KOT49H) with quite a few wired and wireless headsets and people always complain they cannot hear me. Eventually I got my hands on an old Samsung Galaxy S2 and tried my best bluetooth headset with it: Imagine my surprise, I could hear myself quite clearly even when I was talking really really softly, barely above a whisper. My headset is excellent. My phone is not.
My questions revolve around what to do about it.
Nothing in KitKat allows me to adjust the bluetooth microphone gain, nor does it let me use an equalizer on my microphone. I can adjust the volume of the headset, but this does not do anything to the microphone gain.
So...
Question 1: am I the only person with this problem?
Question 2: what do you people do about it?
Question 3: are there any mods / custom ROMs out there that attempt to fix this problem? Google does not appear to be interested in doing so.
Thanks in advance!
*bump*
Any ideas? I have tried re-pairing my bluetooth headset - no go. I have tried flashing custom ROMs and kernels - no go again. It seems to be a problem with the phone, but I have no idea how to fix it. And Google searches always return other people having this problem. Noone with solutions, though.
Using a wired headset results in even worse results, if that were at all possible.
Has anyone tried to replace the bluetooth stack or driver with something that works?
Thanks!
*bump*
Yesterday I spent quite a few hours tinkering with my phone. I tried every last radio out there for the Nexus 5 and none had any effect on bluetooth microphone levels. Then I tried a few AOSP ROMs: CM11 and Omni. They turned out to be so closely related I might as well have just tried one. None had any effect on bluetooth microphone. Heck if CM11 doesn't do it, there really are no alternatives out there! I tried the FauxAudio tweak, even paid $2 to Faux, which successfully managed to do nothing: app didn't was written badly. Finally, I tried a bunch of volume boost tweaks. That worked, actually. That is, it boosted the wrong volume. Finally, in a moment of true and utter desperation, I opened an ADB shell and edited that mixer file by hand. I then discovered that microphone gain on bluetooth is not controlled there.
I tried all my wired headsets again: Etymotic HF3's microphone produces such an atrocious sound, if I am to rely on it I need to seriously consider becoming a mime. Then there were my Bose QC15 headphones with a remote cable for Android by some off-brand company: that was terrible, the cable is useless. Heck, not even mime lessons can help me there.
Eventually I chanced upon an old microphone cable for my QC15 headphones. Just microphone, no remote. Surprisingly, this one is loud and clear! That after being anything but loud or clear on my old cell phone. Interesting. Unfortunately, it's been out of production for a few years. My working theory is that Bose realized putting a decent microphone on expensive headphones gives people real value, makes them spend money, and that way lies madness. We can't have that, can we. So when that cable starts cutting, so does my use of this cell phone.
I am screwed.
In any case, I will stop bumping my own thread, you guys obviously don't know a solution or there would have been a lively conversation right now. And I am pretty sure there is a moderator or two frowning right now, possibly getting ready to throw an encyclopedia at me. My only hope is that Google is going to do something about that pesky Broadcom driver that doesn't work sometime before the mass exodus to the iPhone. And before my precious microphone cable stops working, or I will be leading the way for that exodus. It's a phone, damnit, if it doesn't work like one it's no good.
Hmmm.... it should be possible to wire a good lavalier mike on a cell phone cable... maybe I can get an op-amp from an old tape recorder to get decent amplification... When attaching a 9V battery on my headphone cable begins to look appealing, we really have a problem.
Yes, if nobody reply you is because no one can help u.
But for what it's worth, i had an Xperia Play for 2 years. Using an Motorola Bluetooth Headset H350 while driving and a MW600 Sony Ericsson Stereo Bluetooth Headset, both never had a problem.
Now from 2013 Christmas both headsets with my new N5: still never a problem and not noticing any low volume or mic. Sorry
same issue
Dany XP said:
Yes, if nobody reply you is because no one can help u.
But for what it's worth, i had an Xperia Play for 2 years. Using an Motorola Bluetooth Headset H350 while driving and a MW600 Sony Ericsson Stereo Bluetooth Headset, both never had a problem.
Now from 2013 Christmas both headsets with my new N5: still never a problem and not noticing any low volume or mic. Sorry
Click to expand...
Click to collapse
hi,
i am having the same issue with my Nexus 5 in combination with my Logitech H800 Wireless headset (people can`t hear me).
Anybody who did find a solution for this?
Thx
pitchdown said:
hi,
i am having the same issue with my Nexus 5 in combination with my Logitech H800 Wireless headset (people can`t hear me).
Anybody who did find a solution for this?
Thx
Click to expand...
Click to collapse
No solution. I tried everything, everything I could think of. I got FauxAudio to work eventually and that did nothing for Bluetooth performance (and it said it wouldn't, but I was desperate).
I returned a lot of high end bluetooth headsets over this issue. Eventually I came upon the Plantronics Voyager Legend. I would like to tell you this really expensive headset works fine, but no - microphone gain is still low, though this time around people can hear me okay. Not great, just okay. I am using that now. It's not perfect, it's far from perfect, but finally usable. Sort of. If I speak loudly.
For what it is worth, the ElementalX kernel improves Bluetooth stability on the N5 quite a bit. Microphone gain is still low, though. Another thing that sometimes helps a little is turning off the multimedia profile on the headset, though why THAT would make a difference is beyond me.
All we can do is wait, watch the Samsung Galaxy S5 get released and wonder if we should switch.
kangelov said:
No solution. I tried everything, everything I could think of. I got FauxAudio to work eventually and that did nothing for Bluetooth performance (and it said it wouldn't, but I was desperate).
I returned a lot of high end bluetooth headsets over this issue. Eventually I came upon the Plantronics Voyager Legend. I would like to tell you this really expensive headset works fine, but no - microphone gain is still low, though this time around people can hear me okay. Not great, just okay. I am using that now. It's not perfect, it's far from perfect, but finally usable. Sort of. If I speak loudly.
For what it is worth, the ElementalX kernel improves Bluetooth stability on the N5 quite a bit. Microphone gain is still low, though. Another thing that sometimes helps a little is turning off the multimedia profile on the headset, though why THAT would make a difference is beyond me.
All we can do is wait, watch the Samsung Galaxy S5 get released and wonder if we should switch.
Click to expand...
Click to collapse
Somebody advised me to download the app "persist"
This is free from the playstore.
Can you try this and let me know this is working for you?
Thx
pitchdown said:
Somebody advised me to download the app "persist"
This is free from the playstore.
Can you try this and let me know this is working for you?
Thx
Click to expand...
Click to collapse
This app controls the bluetooth volume, not the bluetooth gain. The bluetooth volume was never a problem.
kangelov said:
This app controls the bluetooth volume, not the bluetooth gain. The bluetooth volume was never a problem.
Click to expand...
Click to collapse
Ok,
i am having the problem with my Logitech H800 headset with the nexus 5.
So this is a android kitkiat 4.4 issue?
Or is this problem only on several Nexus 5-devices?
pitchdown said:
Ok,
i am having the problem with my Logitech H800 headset with the nexus 5.
So this is a android kitkiat 4.4 issue?
Or is this problem only on several Nexus 5-devices?
Click to expand...
Click to collapse
My guess is either the bluetooth baseband or the bluetooth kernel driver used in the N5 is flaky. This is why I think so:
Problem does not exist on my old Samsung Galaxy S2, including when it runs the same nightly of CM11, nor does it exist on my computer or my desk phone. All the headsets I've owned performed admirably there, so the headsets are not directly the cause. From what I've seen no ROM and no kernel out there seem to be making a difference as far as Bluetooth gain is concerned, the problem is persistently there and the same. Best I could tell it's just the N5 with a problem and it's just for the phone profile. I've tried the Bose headset (the worst performer headset with the N5 of the lot) on a colleague's N5 and his phone was just as bad with it as mine. I am not sure if it's a small batch of N5s having a problem, I don't own lots and lots of N5 phones to try on, but I doubt it: with anything digital things are usually all-or-nothing and the N5 has an off-the-shelf Bluetooth chip, which is not unique to the N5. My guess is it's the entire model, but having only tried on 2 N5 phones, this is no more than a guess.
From what I saw online, the entire Nexus line has poor Bluetooth performance, not just the 5, and Google changed the Bluetooth stack with KitKat besides possibly introducing more problems. If you have a non-Nexus phone, the manufacturer most certainly replaced the Bluetooth driver and radio with one of their own, so problem goes away, but the Nexus line does not enjoy such attention.
An interesting thing to try would be for someone to put the LG G2 Bluetooth driver on a N5 kernel and try it out. I don't have the time or the expertise to do that, but there are plenty of people who do. Assuming the G2 does not have problems with bluetooth gain, if the problem still persists it will tell us if it's the N5 baseband or hardware doing it, and noone can help us there if that's the case.
I have this problem too, using my Nexus5 with iphone headsets. Peoples told me in skype and hangouts, that they hear me bad...
Shiver2005 said:
I have this problem too, using my Nexus5 with iphone headsets. Peoples told me in skype and hangouts, that they hear me bad...
Click to expand...
Click to collapse
That's a different problem. The wired headset problem is easily solvable with FauxAudio and a supported kernel.
This maybe realted to the changes Google made to the core Bluetooth stack as of Android 4.3+ I know they made adjustments for the BLE [low poer Bluetooth devices like pedometers and other senor type crap]. It is BEYOND me as to why Google keeps adding functionality ot the core Bluetooth stack when it is GLARINGLY OBVIOUS they have real problems with Bluetooth as a whole. WHY NOT fix the core issues so Bluetooth is much better at the basics before trying to add functionality or more complex?
I know they complained it would cost a bit for a different newer Bluetooth license but I mean in my personal experience with many different phones Bluetooth is SUPER flaky even at it's best in Android, and does not even work the same way across devices [I have used 3 different Jabra speakerphones on my bosses Galaxy 3 recently and they all worked to varying degrees even though they all use the same version of Bluetooth protocol], but my T989 [Galaxy 2 T-mobile], my parents G2s My bosses older Bionic, My fathers new Droid X, etc. all have random problems. You can usually find one device that works well with a certain phone/ROM, but that can change between ROM versions and devices so it is like you need to go and buy 1 of everything every time there is an update and go crazy finding the ONE that works [and as noted on page 1 with the gentleman using the same Platronics Voyager Platinum as I have it is a super expensive very nice device that worked BEAUTIFULLY in ICS, but now in 4.1 + you can not get more than 1 or 2 words across the mic unless you are YELLING at it like a crazy person on the SAME device].
So all that to say I think it is prolly related to changes Android made in 4.3+ flipped the Bluetooth operability on it's head.
Mic Volume OK with KitKat 4.4.4 and cheap "HB-800" headset
there've been no posts for a while so maybe the problem has gone away with the KitKat updates.
But anyway:-
I have a Nexus 5 and recently bought a cheap generic stereo earbud headset with mic from eBay .... $14.82 Ozzie including delivery to Western Australia.
I've actually asked the other party whether they can hear me (specifically "am I loud enough?") because I read this thread and have been assured that it's all good.
In fact it's a pity the sound quality at MY end isn't better, but that's probably the low quality ear buds rather than electronics / firmware reasons.
Of course, ymmv.
Here's the ebay item title in case anyone wants to look it up or I can pm the item number if it helps.
"Headphones Earphones with MIC 1st Stereo Bluetooth Hands-Free Wireless HV/HB-800"
No, the problem is still there. Reason there are no posts is that no one has a solution. Nothing has changed since March. I am somewhat controlling it with CM11 running on the ElementalX kernel. Without this kernel Bluetooth performance is unbearable. With it it is barely adequate.
It's funny that a cheap headset would work okay while multiple top-of-the-line everything-but-the-kitchen-sink models like the Plantronics Voyager Pro would still be having problems.
I was seriously considering getting the OnePlus One, the Nexus 6 and even the iPhone 6 hoping the issue would finally be fixed. It's ridiculous that a phone commonly accepted as the measuring stick of the Android world would be having problems with simple tasks like driving a bluetooth headset. *very disappointed*
Me too. Two days with my new N5 and when I use my Sony SBH20 people hear me bad... With my N4 no problem. Its annoying! Ive to speak with headset because Ive problems with my left arm and legs, I only have the right to hold the phone, I cant do anyhing more and when I walk I need that arm to hold my cane.
I dont see a real solution, I will have to return the N5
I'm having an issue with my Idol 3 5.5". It functions normally when in handset or speaker mode I can hear the other party and they can hear me, but when I connect to my car's Bluetooth people tell me they can't hear me or it sounds like the mic is far away and under water. I did not have this problem with my last phone so I do not believe the issue is with my car (it's a Grom unit) I have only had this phone for a couple weeks and have had the issue from the beginning.
I'm running 6.0.1 stock ROM build 7VAB-UEB0
So far I have tried:
turning off and on Bluetooth on my phone during or right before calls
unpairing and repairing my car
I am charging an old Bluetooth earpiece to try that today and make sure it isn't an issue with my car.
Anyone else have this issue and were you able to solve it?
Me too, dont know what to do
Same problem here, http://forum.xda-developers.com/showthread.php?p=69084028
ciclolars said:
Same problem here, http://forum.xda-developers.com/showthread.php?p=69084028
Click to expand...
Click to collapse
Not the same issue. That thread is talking about poor/low microphone when recording video. This thread is about poor microphone quality through bluetooth, which does not use the phone's microphone.
I'm still trying to determine what the issue is. I tried using an old bluetooth headset and the test call was fine so I will try it tomorrow while driving to confirm. It might be that the Idol doesn't like certain bt devices.
I plugged in my headphones to the phone and heard horrible static/hissing in the background, particularly when the volume is over halfway. I've tried 4 different connections (to my car stereo, to my headphones, to an external speaker, etc) and they all sound equally awful. I really hope I don't have a defective unit... This isn't normal though, right? Anything I can try to do to avoid an RMA? I'm rooted, bootloader unlocked, on PureNexus with EX kernel. No audio mods.
Also, just two notes:
1) I am 100% sure the cable is plugged in all the way.
2) I have no issues with the speaker (which tends to be what people have issues with on this phone, ironically). Audio had no distortion through speaker, but through the headphone jack its horrendous. I can't even listen to it it's so bad.
PsiPhiDan said:
I plugged in my headphones to the phone and heard horrible static/hissing in the background, particularly when the volume is over halfway. I've tried 4 different connections (to my car stereo, to my headphones, to an external speaker, etc) and they all sound equally awful. I really hope I don't have a defective unit... This isn't normal though, right? Anything I can try to do to avoid an RMA? I'm rooted, bootloader unlocked, on PureNexus with EX kernel. No audio mods.
Click to expand...
Click to collapse
Seems like you're not alone. May be worth adding your experience here :
https://productforums.google.com/forum/m/#!category-topic/phone-by-google/SJZzrfohirY
Hope this helps.
buzzboy said:
Seems like you're not alone. May be worth adding your experience here :
https://productforums.google.com/forum/m/#!category-topic/phone-by-google/SJZzrfohirY
Hope this helps.
Click to expand...
Click to collapse
Unfortunately (fortunately?) that's not my issue. I can hear music, it's just terrible sounding due to the hissing I'm the background. It's as if the cable is only half plugged in (but it's not). Thank you for searching though!
PsiPhiDan said:
I plugged in my headphones to the phone and heard horrible static/hissing in the background, particularly when the volume is over halfway. I've tried 4 different connections (to my car stereo, to my headphones, to an external speaker, etc) and they all sound equally awful. I really hope I don't have a defective unit... This isn't normal though, right? Anything I can try to do to avoid an RMA? I'm rooted, bootloader unlocked, on PureNexus with EX kernel. No audio mods.
Click to expand...
Click to collapse
Google has admitted the audio distortion issue being reported in its Pixel smartphones is an hardware problem, and it looks like the company is issuing replacements for customers. The audio distortion issue was first reported in December when a user named Mark Buckman had posted about the same.
shakirajane said:
Google has admitted the audio distortion issue being reported in its Pixel smartphones is an hardware problem, and it looks like the company is issuing replacements for customers. The audio distortion issue was first reported in December when a user named Mark Buckman had posted about the same.
Click to expand...
Click to collapse
Wasn't Mark having issues with his internal speaker when headphones were NOT plugged in though? I think those are different issues. My audio is fine at full blast, as far as I can tell, with no headphones plugged in. It's just when I plug something into the headphone jack that I hear the problem. I'll try his piano and see if I can reproduce his issue though. Maybe I just haven't tested the internal speaker hard enough.
EDIT: Grr... I do have the other problem too! Shown clearly by the Perfect Piano app... Well thank you for leading me to finding that out!
PsiPhiDan said:
Wasn't Mark having issues with his internal speaker when headphones were NOT plugged in though? I think those are different issues. My audio is fine at full blast, as far as I can tell, with no headphones plugged in. It's just when I plug something into the headphone jack that I hear the problem. I'll try his piano and see if I can reproduce his issue though. Maybe I just haven't tested the internal speaker hard enough.
EDIT: Grr... I do have the other problem too! Shown clearly by the Perfect Piano app... Well thank you for leading me to finding that out!
Click to expand...
Click to collapse
Lots of people have a problem with the speaker. I've had 3 replacements with various faults and all have had the speaker issue. It's been reported that its a software issue, and will be resolved in an update..... Hopefully.
https://productforums.google.com/forum/m/#!topic/phone-by-google/XDl52F-Np6o
buzzboy said:
Lots of people have a problem with the speaker. I've had 3 replacements with various issues and all had the speaker issue. It's been reported that its a software issue, and will be resolved in an update..... Hopefully.
https://productforums.google.com/forum/m/#!topic/phone-by-google/XDl52F-Np6o
Click to expand...
Click to collapse
Weird. I spoke to Google today and 5 minutes after describing the problem, they told me to get a replacement through Verizon (that'll be fun).
PsiPhiDan said:
Weird. I spoke to Google today and 5 minutes after describing the problem, they told me to get a replacement through Verizon (that'll be fun).
Click to expand...
Click to collapse
Google can do the replacement too. I opted for that route because I'm hopefully more likely to receive one that I can unlock the bootloader on.
jumaaneface said:
Google can do the replacement too. I opted for that route because I'm hopefully more likely to receive one that I can unlock the bootloader on.
Click to expand...
Click to collapse
They will, but it will leave me without a phone for 2 weeks. They won't ship until they receive mine since it's through Verizon.
PsiPhiDan said:
They will, but it will leave me without a phone for 2 weeks. They won't ship until they receive mine since it's through Verizon.
Click to expand...
Click to collapse
They quoted me 7-10 days max. I still had my old HTC 10 so wasn't really am issue
Did you try cleaning out the headphone jack with an electronic cleaner/compressed air? Dust could be a factor.
(Please correct me if these aren't the ways to clean a headphone jack)
CyberLykan said:
Did you try cleaning out the headphone jack with an electronic cleaner/compressed air? Dust could be a factor.
(Please correct me if these aren't the ways to clean a headphone jack)
Click to expand...
Click to collapse
It's not only the headphones jack I found out though. It's also the speaker when the headphones aren't plugged in. So apparently I have a jacked up phone, sadly. I may try the compressed air for fun though.
PsiPhiDan said:
It's not only the headphones jack I found out though. It's also the speaker when the headphones aren't plugged in. So apparently I have a jacked up phone, sadly. I may try the compressed air for fun though.
Click to expand...
Click to collapse
Tough luck. Mine seems fine.