Related
Quoting from another thread, apparently I'm not the only one with this issue so I'd like to dedicate this thread to finding a possible fix (PS, if someone can suggest a better title let me know).
open1your1eyes0 said:
Hmm maybe it's just me but I think I discovered the oddest bug ever. For some reason, the first sound I hear after like 30 seconds of idle is quieter than what I'm set to in the volume settings and then if I keep using the device without idle all the sounds are loud like normal after that first sound.
For example, I have the device locked with screen off for a while, I unlock the device and the unlock sound is really quiet, then I immediately lock it and unlock it again and now the sound is loud like normal. I keep doing that and it sounds fine each time after that, but as soon as I lock it and leave it idle for like 30 seconds or more and unlock it again, the unlock sound is quiet again.
Also this doesn't only affect the unlock sound, it affects everything, notifications, alarm, ringer, etc....and all my volume is set to maximum I even checked with a 3rd party app. The same thing happened on the previous 2.07 and 2.10 leaks, it's almost like Gingerbread introduced this weird "automatically lower master volume after idle mode". I can't seem to find any option that would affect it.
Click to expand...
Click to collapse
So basically the first sound you hear after a short or long idle time will always be quieter than your actual setting and then keep using the device and everything sounds normal. I almost overslept and missed calls several times cause my alarm and ringtones are so quiet now.
Anyone have any ideas what could be done or taken a look at here?
EDIT: FYI, someone else claimed they had it since MR1 update but I had no issues on Froyo whatsoever. This only became introduced to me with the first 2.07 leak.
I've noticed this as well. I didn't find it to be a big deal, but thought I'd share.
Sent from my HTC CyanogenBolt powered by CyanogenMod 7 RC1.6.1
all i know is even with volume+ the volume sucks on this phone. my wife's lg vortex is 5x louder. we need a dev to look into this.
I honestly thought I was alone on this one. I miss texts and calls all the time because the volume is so quiet after idle.
It is easy to see this with gingeritis all you have to do is turn the volume up to max for your ringer, and then turn the screen off and let it sit for a minute or two. Then turn the screen back on and push the volume up key, you will notice the first sound it makes is really soft, and if you push it again, it makes the normal loud sound.
I hope someone sheds light on this...I for one would like to stop missing calls
I am about to try the official RUU and see if it still does it, but it's only done it since I started using gingerbread roms.
arunningpir8 said:
I honestly thought I was alone on this one. I miss texts and calls all the time because the volume is so quiet after idle.
It is easy to see this with gingeritis all you have to do is turn the volume up to max for your ringer, and then turn the screen off and let it sit for a minute or two. Then turn the screen back on and push the volume up key, you will notice the first sound it makes is really soft, and if you push it again, it makes the normal loud sound.
I hope someone sheds light on this...I for one would like to stop missing calls
I am about to try the official RUU and see if it still does it, but it's only done it since I started using gingerbread roms.
Click to expand...
Click to collapse
aosp roms are louder but not loud enough. we for sure need a volume boost. i cannot imagine it would be that hard to do.
I was just getting ready to start a thread about a possible volume booster.. I can't remember if it was the tb or fascinate i had it on but, adrynalyne had a program called drm i think in his roms that enhanced the volume.. the problem I'm having is the media volume.. I'm trying to listen to MLB at bat here at work but can barely hear the broadcast.
Sent from my ADR6400L using XDA App
Hmm volume booster does seem to be a good workaround idea but I think the main issue is the fact that the volume level automatically changes regardless of the volume loudness. If only someone might be able to figure out what this can be caused by.....
Also I noticed something interesting today. On some sounds it actually seems like it starts off quiet and then makes it louder while the sound is playing. It's hard to tell cause it's so fast but it's definitely noticeable in some cases.
On cm7 there is an option to play notifications and ringtone through the speaker (even though I thought they did anyway) but I haven't noticed the problem with that selected.
Sent from my HTC CyanogenBolt powered by CyanogenMod 7 RC1.6.1
someone should look into the lg vortex volume and try to port the mod over. my wifes phone is 10x louder than my tbolt. hers is aosp too.
FYI, I have only tested this on the official leaks. No custom ROMs or AOSP yet. Though I'm quite tempted to find out if this occurs on other ROMs as well (especially AOSP).
open1your1eyes0 said:
Quoting from another thread, apparently I'm not the only one with this issue so I'd like to dedicate this thread to finding a possible fix (PS, if someone can suggest a better title let me know).
So basically the first sound you hear after a short or long idle time will always be quieter than your actual setting and then keep using the device and everything sounds normal. I almost overslept and missed calls several times cause my alarm and ringtones are so quiet now.
Anyone have any ideas what could be done or taken a look at here?
EDIT: FYI, someone else claimed they had it since MR1 update but I had no issues on Froyo whatsoever. This only became introduced to me with the first 2.07 leak.
Click to expand...
Click to collapse
It takes a split second for the audio amplifier to fire up. The kernel is probably not accounting for this. The audio amplifier suspends after usage just like the screen does to prevent battery drain.
Sent from my A501 using Tapatalk
nelboy said:
It takes a split second for the audio amplifier to fire up. The kernel is probably not accounting for this. The audio amplifier suspends after usage just like the screen does to prevent battery drain.
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Hmm that's an interesting theory but just FYI, the screen times out later than the volume begins to idle to quiet (if it matters). You think flashing another kernel might fix the issue?
open1your1eyes0 said:
Hmm that's an interesting theory but just FYI, the screen times out later than the volume begins to idle to quiet (if it matters). You think flashing another kernel might fix the issue?
Click to expand...
Click to collapse
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk
nelboy said:
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Hmm I see. FYI, I also noticed this issue is extremely obvious when opening the phone dialer for the first time and just press like the number 1. You can hear for a split second as if it "boots up" the audio amplifier the dialing sound for the button grows from silent to normal volume. Then as you dial the rest it sounds fine. But cancel out of the phone dialer and back into literally after like as short as 5 seconds press a number on the dialpad again, you hear it making dialing sound quiet to louder and then normal for the rest of the dialing.
Such a bizarre issue, I really don't understand why this problem just occurred in Gingerbread builds if it's been absolutely fine on older Froyo builds. You would think something as obvious as this would be one of the first bugs they try to resolve. And it seems like it wouldn't be that hard also (assuming it's just a setting in the kernel coding or something).
FYI, if it helps anyone willing to look into it I found out the audio amplifier for the Thunderbolt is a TI TPA2051.
I am really hoping some of our higher up guys can take a look at this. I am really curious to know what (if anything) can fix this issue.
i do know the overall volume on sense roms are much quieter than aosp. what a waste of a good speaker. we for sure need a fix here.
It might not be as easy as it sounds. Audio can be handled quite differently from OEM to OEM. I'm not sure if the thunderbolt is using the native Android audio or if HTC is using their own implementation. You also have to throw the audio Codec into the mix. Here is a link that although it doesn't explain our specific problem, you can see the complexity and the inherent issues with Android audio http://groups.google.com/group/android-ndk/browse_thread/thread/1744088af0924ed9/7170773c13aabe2f i'm not sure about now but the general consensus with audio developers used to be that google needed to stop trying to implement fancy bells and whistles in the audio and get a good solid foundation to start with. Gingerbread was supposed to address some of these issues but I don't believe it did.
Anyway, i'm not positive but you may notice the problem more in gingerbread because there were quite a few changes in the native audio implementation.
Sent from my A501 using Tapatalk
nelboy said:
Sorry. I didn't mean they time out at the same time. Just meant that it also suspends to save battery. I have a feeling this won't be solved until the gingerbread sense kernel source is released. A really good kernel dev might be able to look into this with their current source. You might also notice a pop or crackle sound due to this same issue. Again it is coming from the amplifier powering up WHILE the audio is playing instead of BEFORE. There could be an underlying latency in the hardware but I doubt that's true since it wasn't really noticeable on Froyo. Android has always had a problem with audio latency although it has been pretty much "worked around".
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
Gingerbread Kernel Source for Thunderbolt just released: Link
I know this thread is old, but something i've noticed in regards to this. Im running a semi-stock ROM (xda-bolt), with a stock kernel. I noticed the volume changes don't happen on this ROM, however with a modified kernel such as IMOs 6, the problem arises. Any other non-stock kernel i've used has this problem, but stock kernels do not.
For your information.
-Unrooted, it only has the Aviate launcher but this thing has been going on weeks before it.
-No cellular service(I am using it only at WiFi. It is like as if it were an iPod touch.)
-Happens in videos, YouTube daily motion etc.
-Only when using earphones.
Hey forum! I once again bring up another problem with my Nexus 5. I had it for 60ish days, and this thing has only been occurring for a few weeks. It is this annoying sound which occurs when I plug my headphones and watch some YouTube videos. Initially I thought it was my headphones, but I used two and found that the problem was the same. I believe it is definitely my Nexus 5, but I do not know why and how. It is a pest to me which I want to exterminate, and I gladly could use some help. Is this worthy enough to send back and get a new device? If so, what do I need to be aware of (additional charges, if I can ask for a new color etc).
I found this video which has strong resemblance to my problem only his occurs on speaker. https://www.youtube.com/watch?v=6XZSef6fuKU&feature=youtube_gdata_player
Thank you for your help,
EL
Sent from my Nexus 5 using Tapatalk
I'm having the same issue on my N5 (stock, rooted). I've been searching online, but have yet to find an explanation or solution. I'll report back here if that changes.
Hopefully somebody else on this forum can chime in with some useful information.
I'm getting an annoying buzzing through my headphone jack as well. Noticed it more when playing through my car stereo. I'm inclined to say it's software related, not hardware. Hopefully in 4.4.3 there will be something that will take care of it. I can't see the hardware degrading that quickly, i've only had my phone for less than 4 months and this issue is just starting.
So I think I solved this problem on my phone. Before, I was having glitchy hiccups at least once per song. This hasn't happened once in the past two days since I went into the xposed module gravitybox and disabled "More music volume steps." Hopefully this helps someone else or perhaps inspires them to their own solution.
ancient light said:
So I think I solved this problem on my phone. Before, I was having glitchy hiccups at least once per song. This hasn't happened once in the past two days since I went into the xposed module gravitybox and disabled "More music volume steps." Hopefully this helps someone else or perhaps inspires them to their own solution.
Click to expand...
Click to collapse
I do have more music steps in the ROM settings I changed, but not on Gravity Box. I'll have to see if those are possibly a cause.
I have the same issue but also when playing music using the internal speakers of the phone. It happens when playing music with Spotify and YouTube but I do not think it ever happened to ingame music of any game.
I will also try the XPosed module and report back if it worked..
Edit: Using this tweak of GravityBox did not work for me. The buzzing continues
everyone with this problem
does it only happen when you have the phone plugged into a car or home charger?
i have always gotten this on all my android phones when charging and listening to music in my car or with headphones.. its just one of those things that happens because all the components inside our phones arent shielded as well as they should be
It does not has anything to do with the charger because it happens without it plugged in
Does anyone have updates on the issue? It still occurs on my phone, even on Android L. So I guess it cannot be a software issue
Mine does this all the time when I'm watching videos on YouTube on speaker or headphone... On every ROM from stock to slimkat (using now) and sometimes through the music player. I'm guessing it's some sort of WiFi interference?
My newly acquired Nexus 5 also suffers from this issue
It's exactly the same as in the video. And I don't know why, it's more apparent when watching youtube videos, and much less common when listening to music (both locally with Poweramp and while streaming with Spotify).
I also can confirm this has nothing to do with the device being in charge or not.
Help??
I'm going to buy Nexus 5 soon and that issue sounds really bad to me. Any more information about it? I listen to music on my phone every day and I'd be really disappointed if the noise happened to me.
For me that issue stills persists after over half a year of owning the Nexus 5. I tried several ROMs, some Audio Mods. Nothing helped. I guess it must be a hardware issue.
I wrote a ticket about it to LG, but never got an answer. Since there is not much discussion about it in the internet it appears like it is only an issue with a small amount of devices. So if you are going to buy one the chances are low to get this bug.
You are probably right but when I consider my luck, I still get worried. Keeping my fingers crossed though Thanks for an update.
i think all nexus 5 devices have it, but not everybody notices it.
from my experience with various brands, as much as i dislike them as a company, but samsung has the best headphone jack sound output.
rayiskon said:
i think all nexus 5 devices have it, but not everybody notices it.
from my experience with various brands, as much as i dislike them as a company, but samsung has the best headphone jack sound output.
Click to expand...
Click to collapse
I see. I'm not a big fan of Samsung either, I had some phones from them and I didn't really like those Also for comparision, HTC Desire Z's sound that was coming from the minijack output was perfect for me on my Soundmagic PL11 buds (I'm not an audiophile).
I need to get a new phone anyway and Nexus 5 seems to be something I was looking for - cheap, powerful and comes with Full HD screen. Even if headphone jack isn't going to work well...
TheReduxPL said:
I see. I'm not a big fan of Samsung either, I had some phones from them and I didn't really like those Also for comparision, HTC Desire Z's sound that was coming from the minijack output was perfect for me on my Soundmagic PL11 buds (I'm not an audiophile).
I need to get a new phone anyway and Nexus 5 seems to be something I was looking for - cheap, powerful and comes with Full HD screen. Even if headphone jack isn't going to work well...
Click to expand...
Click to collapse
The headphone jack on the N5 works well, i listen to music through my phone almost on a daily basis, so you don't have to worry about that, but i've come across the glitch linked in OP several times, and it can be reproduced. it doesn't just appear out of nowhere.
i had have this issue from when i bought my device
Annoying buzz and static noise but ya live with it ,regard's joe.
since upgrading to lollipop i can notice this sound glitch (while listening to music over headphones) more often, it occurs once in every 10min for sure... it's really annoying
I hope it's not placebo, but for me, since the lollipop upgrade, I haven't noticed this noise. I've even been listening to more music than before, as this quite got on my nerves, but now it seems to be gone.
My Skyrocket has always had low earpiece volume. It sounds normal until I get in a noisy environment, then I have to press my ear totally against the phone which barely helps. My wife's Galaxy s2 i777 has louder volume and doesn't have this problem. I have tried all the available roms for my device to no avail. Is this normal for this phone, and if so, is there anything I can do to fix this problem? Any app that will work? I love this phone as it meets all my needs except for the volume. Thanks for your help!
edit: i bought this phones 2 months ago from Ebay. I researched it before i bought it, but the main issues others had with the skyrocket was the battery life with LTE. Well, the battery life has been great after custom rom, But the volume is terrible. I first thought i was sold a defective phone but then i found out that others had the same problem, but no solutions. Even all the volume boosts apps that work on other phones (for reasons WAY above my pay grade) do not work on our skyrocket.
...Anybody?... I know this problem of low earpiece volume is common with the skyrocket and has been brought up on many different forums, but I have not found anyone who has found a way to resolve the problem. Any help or direction would be appreciated. This trouble exist with both stock and custom roms.
still no answers?...sigh...
Well, I have replaced the earspeaker and the problem still persists. To clarify, the speaker is not as low as it was when Beanstalk 4.4 was going thru its growing pains and the volume level dropped after one of the builds a month or so ago. It is just that standing outside with normal outdoor sounds (occasional traffic, birds tweeting, outdoor noises) ihave to hold my ear directly against the speaker. I dont have that problem with my wife's s2 i777
Well, a month has passed with no replies. I have found that the volume level is good when using a headset to answer calls, so I have resorted to trying to be sure to carry earbuds with me. On the rare occasion that I dont have earbuds are the days I dread having this phone. As I us my phone for work, I need it to work as a phone first, and a smartphone secondary. As I stated before, I love the features of this phone, but there has to be a workaround for the volume levels. Maybe I'm just getting old and you young folks dont use the phone to actually speak to each other. Woah! Who let my dad in the room?!!? Anyway, Still looking for help. I am not asking which rom is better than another, but are there any roms that have louder volume levels? I have tried many here including Beanstalk, Dirty Unicorns, Liquid Smooth, Sultans CM 11...
crad614 said:
Well, a month has passed with no replies. I have found that the volume level is good when using a headset to answer calls, so I have resorted to trying to be sure to carry earbuds with me. On the rare occasion that I dont have earbuds are the days I dread having this phone. As I us my phone for work, I need it to work as a phone first, and a smartphone secondary. As I stated before, I love the features of this phone, but there has to be a workaround for the volume levels. Maybe I'm just getting old and you young folks dont use the phone to actually speak to each other. Woah! Who let my dad in the room?!!? Anyway, Still looking for help. I am not asking which rom is better than another, but are there any roms that have louder volume levels? I have tried many here including Beanstalk, Dirty Unicorns, Liquid Smooth, Sultans CM 11...
Click to expand...
Click to collapse
Bean Stalk comes with am app called DSP manager which helps control volumes for bluetooth headsets. Give that a shot. It may just be your headset
harrisd23 said:
Bean Stalk comes with am app called DSP manager which helps control volumes for bluetooth headsets. Give that a shot. It may just be your headset
Click to expand...
Click to collapse
The headset isn't the problem. The phone sounds great thru all the headsets that I have tried and thru the loudspeaker. The low volume level is when I am not using the headset and actually have to place my ear up to the phone(earpiece speaker). Its usable in normal areas, such as inside a room, but standing outside with normal background sounds like nature and light road traffic, I can barely hear the caller. I have to press my ear against the phone pretty hard, which usually ends up with accidental button presses and hangups.
crad614 said:
The headset isn't the problem. The phone sounds great thru all the headsets that I have tried and thru the loudspeaker. The low volume level is when I am not using the headset and actually have to place my ear up to the phone(earpiece speaker). Its usable in normal areas, such as inside a room, but standing outside with normal background sounds like nature and light road traffic, I can barely hear the caller. I have to press my ear against the phone pretty hard, which usually ends up with accidental button presses and hangups.
Click to expand...
Click to collapse
Oh i understand, yes I have had that same issue which is why i bought a blue tooth headset.... Not sure if programming can do anything about the internal speaker.
harrisd23 said:
Oh i understand, yes I have had that same issue which is why i bought a blue tooth headset.... Not sure if programming can do anything about the internal speaker.
Click to expand...
Click to collapse
Yeah, I was kinda hoping that maybe somebody discovered something that solve this. I don't know anything about programming, but I was thinking that back when beanstalk had those troubles with extra low volume, it was eventually fixed. And since he was able to boost the volume back to correct levels maybe it could be boosted just a little bit more. Or Since DSP works with bluetooth speakers and headphones and external speakers it seems like it would be easy to make it boost the earpiece volume. But I know that it is NOT easy...it may be impossible. If it was easy then there would have been a fix long ago. But a man can hope, can't he?
****Update 10/27/17: I have received two phones white and black both RMA replacements and I am extremely happy to report they do NOT have either issue. I have an observation to make though regarding the high pitch sound and also why Google may not be approaching this the way we expect. The replacements do have a very very very very faint sound if you put your ear up to the phone. It is so quiet that you would need a dead silent room to hear it. I suspect this is what Google engineers think is going on with our devices and also why the response is lackluster. I will extend an olive branch to Google and admit, I would not replace the phones either if they are just like my new RMA phone. BUT! The issues these users are describing regarding the electronic noise is enough to hear in any area during every call. This is not something you can tune out. I wish you all the best and please let me know if I can help in some way. I don't want to walk away from this knowing how it feels to have that static/issue.****
*******Temporary fix - Turn off NFC******* Please still report this to google using the feedback option inside settings and about phone. *********
I received my Pixel 2 white version and have experienced clicking during phone calls. I have rebooted into safe mode, turned off wifi, bluetooth, always on listening and still experience it.
My wife got a pixel 2 as well and it does not exhibit the clicking sound.
Both phones have a high pitch frequency noise while in phone calls regardless if it is wifi or carrier signal.
I have contacted google support and they have not had any reported issues. Please post here if you have experienced high frequency noise and/or clicking. Here is a reviewer that experienced the clicking as well.
https://www.phonearena.com/reviews/Google-Pixel-2-and-Pixel-2-XL-Review_id4431/page/4
Anyone have advice on diagnosing it?
I ordered both phones from google and use them on T-Mobile.
***Clicking occurs outside of phone calls only when screen is on and unlocked. I have also tried safe mode in addition to airplane mode.***
These are the instructions Google Support gave me.
--------------
We only have the 2 options to get you another device. We can do what we call Advanced Replacement. With this, I send you labels for the original phone and a link to order the replacement. We don't charge you, but there is an authorization hold placed on your payment method until we receive the original phone. This lets you keep using the phone you have while you wait and is usually the faster option.
We also have the option for a Standard Exchange. With this, you send the bad phone back first and when it reaches our warehouse, a replacement is shipped out. This way typically takes 5-10 business days and requires no authorization hold, but you are without the phone during that time.
--------------
Mods, can you change the title to "High-frequency noise & clicking when screen is on and unlocked RMA"
No issues here. Unlocked version using Verizon.
I'm using the unlocked pixel 2 on Verizon and I have experienced both of those issues. The high pitched sound does not happen all the time but the clicking does. So far the clicking is low volume and only noticable during conversation pauses. I hope it's something cured by a software update.
---------- Post added at 05:12 AM ---------- Previous post was at 04:49 AM ----------
One thing to try that might lessen the problem, I noticed that the voice privacy settings was off by default and since I turned it on I haven't noticed the high pitched sound and the clicking was there but less noticable. Could be just a coincidence but let me know if that does anything for you.
weinga16 said:
I'm using the unlocked pixel 2 on Verizon and I have experienced both of those issues. The high pitched sound does not happen all the time but the clicking does. So far the clicking is low volume and only noticable during conversation pauses. I hope it's something cured by a software update.
---------- Post added at 05:12 AM ---------- Previous post was at 04:49 AM ----------
One thing to try that might lessen the problem, I noticed that the voice privacy settings was off by default and since I turned it on I haven't noticed the high pitched sound and the clicking was there but less noticable. Could be just a coincidence but let me know if that does anything for you.
Click to expand...
Click to collapse
I noticed the clicking goes away when WiFi calling. High pitch noise is present at all times except when screen is locked.
I have recorded the sound here. You can also hear the electrical sound as well.
https://soundcloud.com/pwned2owned/click-sound-pixel-2-recorded
soundwave123 said:
I have recorded the sound here. You can also hear the electrical sound as well.
https://soundcloud.com/pwned2owned/click-sound-pixel-2-recorded
Click to expand...
Click to collapse
That sounds a bit like interference on the speaker, not something easy to fix in software. I'm getting my P2 tomorrow. I'll report back.
I started a thread about this at Google's product forums so that if this is a widespread issue, they can be alerted to it.
https://productforums.google.com/forum/m/#!category-topic/phone-by-google/google-pixel-2/TTCkF_SrlpQ
---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------
bartolo5 said:
That sounds a bit like interference on the speaker, not something easy to fix in software. I'm getting my P2 tomorrow. I'll report back.
Click to expand...
Click to collapse
Hopefully this is similar to what plagued the iPhone 8 and can be fixed in an update. It sounds like a very similar issue.
I am experiencing the clicking noise too. It occurs all the time while the screen is on, not just in calls, but its only audible with the phone against your ear. It gave me a headache after a 20min call. It is very noticeable to me. I also hear the high frequency noise during calls if the screen is off.
Android Central also mentioned the clicking noise in their review video.
I have opened a topic on the Pixel support forums. I highly recommend anyone with this issue post there so we can get some attention to this issue.
https://productforums.google.com/fo...!msg/phone-by-google/XuQgtm5dK8I/7SZD7EfxAAAJ
bartolo5 said:
That sounds a bit like interference on the speaker, not something easy to fix in software. I'm getting my P2 tomorrow. I'll report back.
Click to expand...
Click to collapse
Yeah, it never occured to me before to hold the earpiece on my phone to my ear, when not making a call. But I just tried it with my Nexus 4 (that I'm replacing with a Pixel 2). When the screen is on, with my Nexus 4, but not in a call, I hear a static-like noise and an electronicy noise; it is very faint and only audible in a very quiet setting. When the screen is off I hear only the static noise and it seems even more faint. I don't notice anything during calls, because I assume the sound of my caller is far louder and drowns out any background static.
Thinking about it, it seems like any speaker, connected to an amplifier, with the volume all the way up (my usual setting on my Nexus 4) makes static and electronic noises. In my car, if I turn the stereo all the way up, without playing anything, there's quite a bit of noise coming through the speakers. And one is certainly use to hearing the hum of speakers, when a powerful sound system is turned on.
I'm assuming that when the system is on, there is a completed circuit to the speaker, and it is difficult to have a pefectly clean signal. Any surrounding electro-magnetic activity (of which there is a lot in a phone, the power source; the cellular, wifi, and bluetooth radios; probably elements of how the screen functions) would potentially create interference in the voltage on the circuit to the speaker (i.e. earpiece), in essence creating micro-voltages that would cause noise in the speaker. After all, that's all a speaker does, it turns amplitude in voltage into sound (I think, I'm not an expert on this). So tiny random voltages from interfence would create noise of some sort or another.
I wonder if it's almost impossible not to have this effect with a speaker (you'd have to have a perfectly clean power source with no interference and everything connected to the speaker would have to be perfectly shielded).
Anyway, obviously this sort of phenomenon can be more or less noticeable. So I wonder if all phones do this, but it's more noticeable on the Pixel 2 for some reason.
The clicking noise is more interesting, because it's regularity reflects some sort of interference that is not just random interference from other electronic components. It's also curious that a couple people report not having this issue on the Pixel 2--maybe it's there, but much less noticeable?
Anyway, I'll be interested if people replace the device and get another one without the issue.
Goes away when camera is open. Make a call then open camera. Sound is gone.
Can confirm my Pixel 2 also has this clicking + hissing noise. It happens ALL the time when the screen is on, and obviously is a lot more obvious when you are using the phone for a phone call. Has nothing to do with RF cell output because it also happens when using the speaker in airplane mode + wifi. hopefully there's a software fix for this, but it just sound like interference from the circuits into the speaker... Although it's not super annoying it should not be happening.
I am experiencing the same problem as well
---------- Post added at 04:44 AM ---------- Previous post was at 04:39 AM ----------
davwman said:
Goes away when camera is open. Make a call then open camera. Sound is gone.
Click to expand...
Click to collapse
Mine goes away too when the camera is open
I've contacted support and have a replacement on the way. Hopefully it's gone. I don't have much confidence
Can anyone confirm that this does not happen to some degree on all phones?
As I note above, though I never thought before to put the earpiece to my ear when I'm not making a call on my old Nexus 4, after reading this I discovered it also makes static and electronic interference noises when the screen is on. In fact, it's even there, but only very faintly, when it's off. It does not make a ticking sound, though, which I can imagine is more annoying, especially if it is audible during calls.
Anyway, I'm just wondering it it's reasonable to expect there to be no sound like this at all. Maybe it's just more pronounced and obvious on the Pixel 2, but not necessarily unexpected on a smartphone.
Also, are there any more people other than the OP who has a Pixel 2 that does not make the clicking sound (he said his wife's does not, but his does)?
*
[Edit: Okay, I just started setting up my Pixel 2 and I definitely have the clicking sound. I'm officially annoyed. It's only there when the phone is unlocked, not when the screen is on but the phone is locked. Definitely audible during calls.
I do also hear a static noise and some high pitched electronic sounds, when the screen is locked, but it's pretty faint and not significantly different from what I've described on my Nexus 4. So to me the clicking sound is the real issue.]
*
[Edit 2: The clicking sound went away.
I have no idea what caused this, if anything. I factory reset the phone, just so I'd be able to tell customer support I'd already tried that, and it did not help. The clicking was still there. Then I was going through and changing settings--most of which I had done before the factory reset and the clicking sound was still there. The only thing I can think of is that I was disabling a lot of the app permissions. I think I disabled more this time than before the factory reset. I prefer not to allow access to the microphone, location, anything that seems privacy related, if not necessary. So I was even disabling stuff for the Google app and Google play services, which in several instances gave me a warning that the phone might no work properly, but I did it anyway. It was soon after this that I notice the clicking sound was gone.
I tried re-enabling a few things having to do with the micophone (thinking that could create feedback or something), but that did not bring the clicking sound back.
Something else I did that I hadn't done before the factory reset was calibrate the compass. I noticed it was way off in the maps, so I just did the figure eight flipping around motion that maps sometimes prompts one to do to calibrate the compass. That did fix the compass.
Anyway, perhaps the disappearance of the clicking had nothing to do with any of these settings. I'm a bit mystified and baffled. I'd also been charging the phone at the same time.
The high pitched electronic sound I was hearing is also less noticeable. I don't hear it with my ear to the earpiece; but I just discovered it's much more noticeable with my ear to the top back of the phone. I do still hear the faint static noise that I described in the earpiece.
Lastly, this could be totally unrelated, but wondering if the clicking is just from something not being put together correctly, I tapped the phone on the top edge and notice that something sounds faintly loose or like it's ratting in the top of the phone. I don't hear this anywhere else on the phone and it only works by tapping the phone on the side at the top or on the edge of the top. Actually, I can hear something similar, but lower pitched tapping the phone on the bottom. It's more like something vibrating inside the phone, than like something is loose. Perhaps components in the speakers? I assume there are small moving components in the speakers for them to function (or maybe not?). I notice I can provoke a similar sound from the earpiece in my Nexus 4. Anyone else notice this?
Anyway, I hope this is somehow helpful. I suppose I won't be surprised if the clicking sound comes back.]
I just noticed this same hissing sound is heard on recorded videos!
cb474 said:
Can anyone confirm that this does not happen to some degree on all phones?
As I note above, though I never thought before to put the earpiece to my ear when I'm not making a call on my old Nexus 4, after reading this I discovered it also makes static and electronic interference noises when the screen is on. In fact, it's even there, but only very faintly, when it's off. It does not make a ticking sound, though, which I can imagine is more annoying, especially if it is audible during calls.
Anyway, I'm just wondering it it's reasonable to expect there to be no sound like this at all. Maybe it's just more pronounced and obvious on the Pixel 2, but not necessarily unexpected on a smartphone.
Also, are there any more people other than the OP who has a Pixel 2 that does not make the clicking sound (he said his wife's does not, but his does)?
*
[Edit: Okay, I just started setting up my Pixel 2 and I definitely have the clicking sound. I'm officially annoyed. It's only there when the phone is unlocked, not when the screen is on but the phone is locked. Definitely audible during calls.
I do also hear a static noise and some high pitched electronic sounds, when the screen is locked, but it's pretty faint and not significantly different from what I've described on my Nexus 4. So to me the clicking sound is the real issue.]
*
[Edit 2: The clicking sound went away.
I have no idea what caused this, if anything. I factory reset the phone, just so I'd be able to tell customer support I'd already tried that, and it did not help. The clicking was still there. Then I was going through and changing settings--most of which I had done before the factory reset and the clicking sound was still there. The only thing I can think of is that I was disabling a lot of the app permissions. I think I disabled more this time than before the factory reset. I prefer not to allow access to the microphone, location, anything that seems privacy related, if not necessary. So I was even disabling stuff for the Google app and Google play services, which in several instances gave me a warning that the phone might no work properly, but I did it anyway. It was soon after this that I notice the clicking sound was gone.
I tried re-enabling a few things having to do with the micophone (thinking that could create feedback or something), but that did not bring the clicking sound back.
Something else I did that I hadn't done before the factory reset was calibrate the compass. I noticed it was way off in the maps, so I just did the figure eight flipping around motion that maps sometimes prompts one to do to calibrate the compass. That did fix the compass.
Anyway, perhaps the disappearance of the clicking had nothing to do with any of these settings. I'm a bit mystified and baffled. I'd also been charging the phone at the same time.
The high pitched electronic sound I was hearing is also less noticeable. I don't hear it with my ear to the earpiece; but I just discovered it's much more noticeable with my ear to the top back of the phone. I do still hear the faint static noise that I described in the earpiece.
Lastly, this could be totally unrelated, but wondering if the clicking is just from something not being put together correctly, I tapped the phone on the top edge and notice that something sounds faintly loose or like it's ratting in the top of the phone. I don't hear this anywhere else on the phone and it only works by tapping the phone on the side at the top or on the edge of the top. Actually, I can hear something similar, but lower pitched tapping the phone on the bottom. It's more like something vibrating inside the phone, than like something is loose. Perhaps components in the speakers? I assume there are small moving components in the speakers for them to function (or maybe not?). I notice I can provoke a similar sound from the earpiece in my Nexus 4. Anyone else notice this?
Anyway, I hope this is somehow helpful. I suppose I won't be surprised if the clicking sound comes back.]
Click to expand...
Click to collapse
Rattling is likely the ois of the camera
Reported... waiting for feedback... Hold on everyone...anyone with pixel 2 xl can confirm if its also happening on the bigger one?
turn off nfc... temporary work around for the meantime...
For info I don't believe i'm getting this, i've used the unit pretty extensively since i received on Wednesday. I'm in the UK and have the White 64Gb edition.
Wow, this is unacceptable. I am waiting for my Pixel 2 XL to arrive next week, if I have this issue it is going back to Google. For the money they ask you would think they test things like this.
This is a simple problem that has no solution that I'm aware of. On my OP6, notifications coming through any bluetooth headset that I've tried (3 of my own, and a couple others) have been so quiet even at max volume as to be nearly useless. Since the vibration motor on this phone is also so weak as to be nearly useless, this creates a problem when doing something like listening to music--any message will probably get missed.
Anyone have any experience solving this problem? Or maybe even a workaround of some kind? I'm on open beta 5 and rooted, but that makes no difference as all builds show this behavior identically.
Absolutely no one has noticed this problem? This isn't even a OP6 thing: it happened on my 3t and 5t as well.
deedaleet said:
Absolutely no one has noticed this problem? This isn't even a OP6 thing: it happened on my 3t and 5t as well.
Click to expand...
Click to collapse
It's fine here. Maybe it's your device thats connected to all your phones.
Happens to me too.
yldlj said:
It's fine here. Maybe it's your device thats connected to all your phones.
Click to expand...
Click to collapse
I suppose it's possible, but over the years I've tried upwards of 5 or 6 devices, ranging from wireless earbuds, over hear headphones, and a couple of bluetooth speakers. All exhibit exactly the same problem 100% of the time.
deedaleet said:
This is a simple problem that has no solution that I'm aware of. On my OP6, notifications coming through any bluetooth headset that I've tried (3 of my own, and a couple others) have been so quiet even at max volume as to be nearly useless. Since the vibration motor on this phone is also so weak as to be nearly useless, this creates a problem when doing something like listening to music--any message will probably get missed.
Anyone have any experience solving this problem? Or maybe even a workaround of some kind? I'm on open beta 5 and rooted, but that makes no difference as all builds show this behavior identically.
Click to expand...
Click to collapse
Doesn't your phone attenuate when a notification comes in? I barely hear the notification tone as well (which may confirm what you're saying) but the music lowers when one comes in so I know immediately when someone has texted me.