Hello All,
I searched first by the way :-/
Recently my Nexus has had its earpiece too loud for both Incoming and Outgoing Calls.
At first I thought it had something to do with the radio, so I downgraded. It actually worked on the first call but after that it was loud as heck even on the lowest volume.
I tried to retrace my steps with my applications next, but nothing that would point to the earpiece. The last apps installed updated where mostly games like Fruit Ninja and Aliens vs. Humans, so I think we can rule out that.
The specs in my sig should be up to date.
The only variable that has changed other than the ones listed above is the fact that I recently bought a Jawbone Icon Bluetooth Headset. But to my memory, this issue began before that.
Can't find a solution anywhere cause it seems most people have an issue with the phone being too soft lol.
I'm really looking for some help guys. I'm just short of wiping the phone clean and reinstalling CM6 and my apps. If that dosen't work I'll have to use the warranty I guess. Had the phone from about Sept 10 I believe.
Let me know if I missed anything guys. All ideas are welcomed to fix this issue.
It's probably because of CM. CM uses a audio boost kernel by default, so I'm guessing that's the problem. Try installing no audio boost kernel to see if it solves the issue.
yeah if you are using cyanogen ROM, they added an audio boost hack long ago. on cyan 5.0.8 the audio boost was so loud that over 50% volume started to distort the speaker and kill your ears. so in later releases they split the difference and lowered it somewhat.
but the boost has always been there. the only likely possibility is that you recently started enabling DSP settings like compression or the EQ, which would suddenly now make things way louder.
Wow thanks guys. Had no clue that CM had an audio boosted kernel. Guess I'll be flashing something else for the while. Something as close to vanilla I guess.
Oh, I also checked the DSP settings, everything was off but was worth a shot.
Thanks again for the replies!
Just to let anyone with the same issue know, I found away around it. I installed one of Wildmonks kernels without the audio fix.
Kernel 2.6.35.10 to be exact. I get to keep my cyan features and have a decent volume ear piece too. Yay!
Good work. It's funny cause most people complain this phone is too quiet. If only they see this post!
Hi everyone,
I'm experiencing problems with the volume of my microphone when I'm in a call.
The persons at the other end of the call can only hear me very silent.
The problems are only exists with the standart phone app, when I'm using a third party app (like sipdroid) my volume is fine...
I'm using Cyanogen 7.0.3 on my Nexus One
Is there a fix for this Problem?
With the stock ROM I don't have this problems but I need a ROM with trackball wake because my power button fails.
I can't RMA my Phone to HTC right now, because I'll be not at home in the next three weeks. Therefore I need my mobile phone with me.
I'd use an other ROM which has TB wake support and no microphone issues but at a quick glance through the forums I couldn't find a suiting one.
Thanks for your efforts to help me
hey, i have a similar problem but i noticed that using different kernel affect the microphone. I'm a noob to this so im not entirely sure if kernel is related to microphone.
Well basically im running miui rom 1.5.6 right now and i was using redstar kernel 38.4 and then i upgraded it to redstar kernel 38.5. Then i called my girlfriend and she could barely hear me. Then i reverted back to 38.4 and she hears me now much louder but not the clarity isn't as good.
You using DT a2sd by any chance?
Damn, my phone froze today at work and I had to pull the battery.
Now I can't power it on again due to the not working power button...
Battery trick doesn't work either.
So I guess I have to take the bitter pill and RMA it right now.
Holy sucks! What's the battery trick...just incase.
Can anyone suggest any 'good' solution? kernel or otherwise to fix this $#@$# 'bug' of low in-call volume in Nexus One??
Would really appreciate all the help!
If people hear you very quiet - look up the mod to disable noise cancellation. If the problem will disappear with noise cancellation disabled - it means your 2nd mic is faulty and needs replacement.
Jack_R1 said:
If people hear you very quiet - look up the mod to disable noise cancellation. If the problem will disappear with noise cancellation disabled - it means your 2nd mic is faulty and needs replacement.
Click to expand...
Click to collapse
Nope, people hear me well. Its that I cannot hear well. Specially in traffic, I usually tell them that I shall call them back
Any help?
Look up Gingerbread volume control app in Development forum. It can override the system settings and make the volume much louder than the maximum stock, AFAIK.
Thanks, but this app is not working for everyone AFAIK.
So apparently, I am just finding out now that this is a major issue with all Bionics and seems to be something related to the Gingerbread kernels. This is actually an issue I first noticed with my Thunderbolt back when testing out Gingerbread builds. I won't go into too many details as most of it is in the following thread: Click Here
The idea seems to be that the kernel was not properly written to account for the device's amplifier and it takes about a second for it to boot up after the first sound is made. Then if you keep producing sounds it will be at the proper volume. But don't touch it for about 5-10 seconds and it goes "idle" and then the first sound again is quieter and then accompanying sounds will be louder again.
A good way for you guys to test this is try the following:
1. Make sure your volume is all the way up
2. Go to the dialer app and press a number like 2 on the dialpad and listen to the sound (you can hear it sounds as if it starts quiet and then grows louder)
3. Keep pressing the same number and any other number you will hear they all sound the normal loud volume now
4. Don't touch the dialpad for 5 seconds
5. Press any of the numbers again and you will hear the same issue (sound of the key pressed grows from quiet to loud)
6. Keep pressing any number and you will hear it sounds normal again
This issue is not only in the dial but pretty much any system sound. It has been determined that it is related to the kernel and perhaps now with the kernel source released maybe a developer can look into this issue?
Wow I never noticed that before. Guess its not a huge issue in my use. Oh well....maybe we'll get some custom kernel apps now that the source is released.
Bump for more exposure
I never noticed this before but it happens on my phone as well. I don't really see what the big deal is. It's probably a battery saving trade off of some sort. It's not like this happens in the middle of a song.
My Bionic with D3Blurr3d rom on it does not do this. Either through the speaker or headphones. BTW, you made me call someone in Mauritania by punching a bunch of 2's in my dialer!!! (not really, but wouldn't that be funny?)
I don't have this issue on liberty 48
Not a kernel issue it's a hardware issue.
https://supportforums.motorola.com/message/469889#469889
If you test 10 different Bionics you will get 10 different results, but what we know is that it's due to piss-poor EMI shielding or grounding. Not trying to **** on your thread or anything, I (almost) hope it is a kernel issue, as an OTA could possibly resolve the issue.
quentin0 said:
Not a kernel issue it's a hardware issue.
https://supportforums.motorola.com/message/469889#469889
If you test 10 different Bionics you will get 10 different results, but what we know is that it's due to piss-poor EMI shielding or grounding. Not trying to **** on your thread or anything, I (almost) hope it is a kernel issue, as an OTA could possibly resolve the issue.
Click to expand...
Click to collapse
The OP was referring to a different issue, not headphone whine. But on that topic, it's not a Bionic issue, it's a Motorola issue. I took a trip on Sprint with the Photon before getting the Bionic and it has the high pitched whine also, even though it uses a different processor (and i'm assuming sound codec). It wasn't as loud as the Bionic's, but it was there.
I am a long-time user of CyanogenMod, but I have never flashed a non-"stock" kernel into CM until recently. I tried the Devil and Semaphore Kernels, and while performance was excellent, my Captivate's speaker is problematic with both of them.
First, the speaker is extremely loud regardless of how low I set the volume. This volume issue does not appear when the speaker is disabled.
Second, when I activate the speaker, the person with whom I am speaking complains that I sound "distant and tinny," possibly with a lot of reverberations. This is not the other person's hearing him- or herself. If I disable the speaker, regardless of whether I actually move the phone toward my head, the problem seems to disappear. They can hear me clearly.
Re-flashing CM10 fixes both problems. I have not modified the default settings introduced by either non-stock kernel. Could these issues be due to audio tweaks introduced in those kernels? Does anyone have any suggestions for me if I would like to continue using one of them?
Thank you!
Hey everyone, Has anyone experienced a light snap sound coming from the speakers while no media is playing? Trying to figure out if this is only on my phone or a bug. Thanks!
Yep this is a known issue ATM
I'm sure they're looking into it as we have a lot of mentions about it on the subreddit.
here is what i did to get rid of the popping sound until they fix it. turn off screen locking sounds, charging sounds, touch sounds, and vibrate on tap the popping went away completely. I dont know which setting it is but after those are off the popping stopped for me and others.
It was the screen touch sounds for me, switching that off got rid of most click/pop/snap noises but not all of them. It's particularly noticeable after a short notification sound has played, it's like the speaker is still active even though the sound has finished playing, then the speaker deactivates making a click noise. Very annoying. Is it Android or hardware causing the issue? If it's Android it can be fixed if it's hardware it may be fixable.
RetroFlux said:
It was the screen touch sounds for me, switching that off got rid of most click/pop/snap noises but not all of them. It's particularly noticeable after a short notification sound has played, it's like the speaker is still active even though the sound has finished playing, then the speaker deactivates making a click noise. Very annoying. Is it Android or hardware causing the issue? If it's Android it can be fixed if it's hardware it may be fixable.
Click to expand...
Click to collapse
Usually clicks happens when there is a sharp change in sound. Every speaker does clicks if not handled correctly. For instance, my studio speakers will click every time I shut them down before lowering the volume to zero. Most likely, adding a software DSP that applies an exponential volume lowering before actually shutting down the speaker would solve the problem.
Let's just wait for them.
To answer your question. Since that is a software issue were having. The resolution we can offer regarding this if its not fixed with any of our basic troubleshooting would be to wait for an update. But for an ETA on to when the update will happen, we apologize for we do not have the exact dates. Since before an update gets released the developer team needs to gather all the reports from us on all the issues we have encountered on the new phone so they can release a one and done update.
Click to expand...
Click to collapse
That's from support just now.
Cellendril said:
That's from support just now.
Click to expand...
Click to collapse
Sounds like they will wait around for more issues to develop and then finally push a fix? Maybe it comes with Pie
Could everyone with the RazerPhone 2 please post if the newly released update corrected the speaker cracking/popping sounds issue.
I had the following Live Chat with Razer support:
Peripheral Support (12/5/2018, 4:38:10 PM): May I know what is the issue that you have with
your Razer Phone 2?
Me (12/5/2018, 4:38:29 PM):
A new software update is available for Razer Phone 2. This update includes:
Camera
• Improved color for richer more vibrant shots
• Improved brightness for warmer tones and details.
• Improved HDR for more consistent shot detection and processing
Audio
• Audio fixes and improvements.
Me (12/5/2018, 4:38:56 PM): Am holding off on purchasing the phone until I see that the "snap..pop" sound in speakers is corrected. May I please have a definitive answer regarding the "Audio fixes and improvements" mentioned in the update description to see if it does address the pop crackling speaker issue
Peripheral Support (12/5/2018, 5:08:28 PM): Upon checking my resources here it should be fixed as well as per checking the update.
Me (12/5/2018, 5:10:04 PM): Specifically asking about the "pop crack:" sound?
Peripheral Support (12/5/2018, 5:10:27 PM): Yes.
Me (12/5/2018, 5:12:03 PM): Great, will await to see if owners of the phone post their claim that it was fixed. Until then your resource info was encouraging
Peripheral Support (12/5/2018, 5:14:15 PM): Thank you.
[Session ended and I was given a Case Number]
No cracking or popping here after the Update ?
Did you have the cracking/popping sound bug before the update?
Any other owners reading this, did you have the snapping sound problem before the update and did the update correct the problem?
Update
I returned from the Microsoft Store after having a lengthy hands on with the phone. I brought along a Moto G6 to compare speaker volume and sound quality. The volume on the RP2 was louder in volume but only by a margin. I admittedly didn't turn on Dolby Atmos to tweak any settings nor did I check to see if the store had it turned on. As for the sound quality, to my ears the trebles became unpleasantly harsh at higher volumes. The bass had a nice, full quality regardless of volume and was very good even at maximum volume.
As for the "pop/snap" sound issue, I didn't encounter any of it while scrolling through the various Settings windows and while scrolling in the Apps folder, and that was with all the various advanced sounds turned on. Had the interior of the store not been exposed to all the ambient loud mall music, perhaps I may then have heard the reported popping sounds, or perhaps I would not if the store had installed the aforementioned described update. The About Phone settings appeared to not have it installed.
I realize that the subject of this thread is "Snap sound coming from speakers" but I feel obligated to say I wasn't sufficiently impressed with the phone to consider purchasing it, despite it being on sale for $650 through December. I found the display coloration appeared dull. If the demo phone would have allowed me to tweak the color settings perhaps I may have been able to make the colors appear more vibrant. Also, for some reason the screen images did not appear sharp, despite it being set for 1440 X 2560. Perhaps the demo unit may have been at fault.
*Supersnake* said:
Could everyone with the RazerPhone 2 please post if the newly released update corrected the speaker cracking/popping sounds issue.
I had the following Live Chat with Razer support:
Peripheral Support (12/5/2018, 4:38:10 PM): May I know what is the issue that you have with
your Razer Phone 2?
Me (12/5/2018, 4:38:29 PM):
A new software update is available for Razer Phone 2. This update includes:
Camera
• Improved color for richer more vibrant shots
• Improved brightness for warmer tones and details.
• Improved HDR for more consistent shot detection and processing
Audio
• Audio fixes and improvements.
Me (12/5/2018, 4:38:56 PM): Am holding off on purchasing the phone until I see that the "snap..pop" sound in speakers is corrected. May I please have a definitive answer regarding the "Audio fixes and improvements" mentioned in the update description to see if it does address the pop crackling speaker issue
Peripheral Support (12/5/2018, 5:08:28 PM): Upon checking my resources here it should be fixed as well as per checking the update.
Me (12/5/2018, 5:10:04 PM): Specifically asking about the "pop crack:" sound?
Peripheral Support (12/5/2018, 5:10:27 PM): Yes.
Me (12/5/2018, 5:12:03 PM): Great, will await to see if owners of the phone post their claim that it was fixed. Until then your resource info was encouraging
Peripheral Support (12/5/2018, 5:14:15 PM): Thank you.
[Session ended and I was given a Case Number]
Click to expand...
Click to collapse
I can't confirm the bug is solved. Probably right after this post, it pops. Nevertheless, I can confirm that after the update I no longer got the snap sound, so most likely it is solved.
Renovatio33 said:
Usually clicks happens when there is a sharp change in sound. Every speaker does clicks if not handled correctly. For instance, my studio speakers will click every time I shut them down before lowering the volume to zero. Most likely, adding a software DSP that applies an exponential volume lowering before actually shutting down the speaker would solve the problem. Let's just wait for them.
Click to expand...
Click to collapse
:good:
Knowledgeable explanation of what may likely be the cause and how it can be fixed.
I did experience the strange snapping sound for first few weeks having the phone, and I have not noticed it since the update, so far.
Haven't heard the clicks after using using MR2 for a bit. Unfortunately the speakers sound a little softer, but they had issues at max volume before anyway so maybe that's for the best.
CurtisMJ said:
Haven't heard the clicks after using MR2 for a bit. Unfortunately the speakers sound a little softer, but they had issues at max volume before anyway so maybe that's for the best.
Click to expand...
Click to collapse
Screenshot of a poster on Reddit evaluating the effects of the update.
*Supersnake* said:
Did you have the cracking/popping sound bug before the update?
Any other owners reading this, did you have the snapping sound problem before the update and did the update correct the problem?
Click to expand...
Click to collapse
I had the problem before the update. So far, the update seems to have completely solved the audio/speaker popping. Will report back again once I've used it a while.
EDIT: I've run the Dolby Atmos demo many time pre-update, so I had a good benchmark. Ran the Dolby Demo a couple of times after the update. Volume seems very similar & there is definitely less distortion, because I remember how bad it was before. However, there is more noticeable crackling of the speakers while playing the demo at higher volume.
*Supersnake* said:
Screenshot of a poster on Reddit evaluating the effects of the update.
Click to expand...
Click to collapse
Ah, so I'm not crazy. I feel like he's exaggerating a bit though. He evidently doesn't know the factory images exist either. Maybe someone should tell him
CurtisMJ said:
Ah, so I'm not crazy. I feel like he's exaggerating a bit though. He evidently doesn't know the factory images exist either. Maybe someone should tell him
Click to expand...
Click to collapse
I agree that there's some exaggerating. I actually think there hasn't been much-if any-volume change. I've got a Phone 2 with the update & another without the update, so I'll setup the SPL meter & do some comparisons & report back.
Semi-related, the speakers now "click" each time the YouTube app rotates from landscape to portrait... any one else have this happen?
Per this reddit thread, watching https://youtu.be/ZK5bOZx2xXs at max volume on the speakers reboots my phone. Very odd - do any of you experience this?
I do sometimes get the snap sound on rotation, but the formerly persistent pop is not there.