Jump to content
MrZorbatron

Galaxy Note 2 + MC3 + SO 73 = Uncontrollable earpiece volume + Blown Speaker

Recommended Posts

I have recently come across a new problem with my new phone. This only happens in areas that are on the new network for 3G, and only on calls displaying so 73.

 

I find that I am completely unable to control the volume level of the earpiece speaker on my device. Whether it's all the way up or all the way down, the sound level is exactly the same. Speakerphone volume control functions normally. As soon as I'm outside of the new network, I'm back on the legacy 3G, my earpiece volume control functions normally.

 

At first it was just a mild annoyance, and I'd solvde it by putting a piece of cloth isolator tape over a my speaker. Now that my software has been updated, I am able to control the volume in these areas, but my earpiece sound is very very bad because the speaker seems to be blown.

 

Has anyone else encountered this issue? I am seriously about to replace my speaker myself, as I do not want a rebuilt phone. I have much greater confidence in my ability to repair this device than in their refurbishment shop.

Share this post


Link to post
Share on other sites

I am starting to wonder now, actually. I just read a few complaints about the sound quality. I also just downloaded an app that allows playing audio files through the earpiece. It has no issue with music or talk files even at pretty high levels. I don't particularly want to take this thing apart either. Will reflash MC2 and find out.

Share this post


Link to post
Share on other sites

This sounds like a software issue, since you stated that you can play other files perfectly fine. Maybe the phone app is just being really buggy.

 

 

-Luis

Share this post


Link to post
Share on other sites

This sounds like a software issue, since you stated that you can play other files perfectly fine. Maybe the phone app is just being really buggy.

 

 

-Luis

 

yes i have figured out that the speaker itself it not damaged.  As for the phone misbehavior, it only happens on the new CDMA and not the old.  i am more inclined to think it is a radio issue.  Further, when this is happening, the device says it is unable to adjust sound while on a "wideband" call if i change anything but volume.  It seems to have this same screwy sound no matter what output device it is connected to.

 

The sound is like a hiss mixed with the audio signal that rapidly transitions between on and off.  At lower volumes, it sounds like a blown speaker would, but at high volumes it does not.

 

With the restoration of MC2 firmware, the hiss like problem no longer occurs.  I instead have my ear blasted once again with no ability to turn the sound down.

 

the only problem is that it was a trip to install the new firmware without getting that stupid new Samsung security thing with it.  I do not want to go through that again until I know it will work right, plus I am getting OTA update notices again.

Share this post


Link to post
Share on other sites

yes i have figured out that the speaker itself it not damaged.  As for the phone misbehavior, it only happens on the new CDMA and not the old.  i am more inclined to think it is a radio issue.  Further, when this is happening, the device says it is unable to adjust sound while on a "wideband" call if i change anything but volume.  It seems to have this same screwy sound no matter what output device it is connected to.

 

The sound is like a hiss mixed with the audio signal that rapidly transitions between on and off.  At lower volumes, it sounds like a blown speaker would, but at high volumes it does not.

 

With the restoration of MC2 firmware, the hiss like problem no longer occurs.  I instead have my ear blasted once again with no ability to turn the sound down.

 

the only problem is that it was a trip to install the new firmware without getting that stupid new Samsung security thing with it.  I do not want to go through that again until I know it will work right, plus I am getting OTA update notices again.

 

Same problem here after update. At my place of employment phone sounds really poor. Same msg about wideband calls. Other places calls sound fine.

Share this post


Link to post
Share on other sites

If you got the update over the air, do not use Odin to go back to the old version. It will trip a flag in the KNOX bootloader and cause problems for later software updates or possibly a no boot or reboot loop condition.

Share this post


Link to post
Share on other sites

Same problem here after update. At my place of employment phone sounds really poor. Same msg about wideband calls. Other places calls sound fine.

Let me guess... in a Samsung market with Network Vision 3G?

 

Edit: never mind. ohio is Samsung.

Share this post


Link to post
Share on other sites

If you got the update over the air, do not use Odin to go back to the old version. It will trip a flag in the KNOX bootloader and cause problems for later software updates or possibly a no boot or reboot loop condition.

Heh, I did that last night since my root got all messed up for some reason, so I figured I'd go back to MC2 from MK4. I thought I could go back, but nope... I realize that now after doing a bit of research.

 

Anyway, ended up soft bricking my Note 2 after receiving a fail message within Odin. Tried rebooting afterwards and it wouldn't even light up. Only download mode worked and had to use Kies to get back up and running. If Knox is going to be the norm of Samsung, then this is my last device from them.

 

Sent from my Samsung Galaxy Note 2 using Tapatalk 4 HD.

 

 

Share this post


Link to post
Share on other sites

Too late for the Odin Advice.  I flashed an incomplete copy of MK4 from XDA.  The phone took the update and even booted up and functioned for the most part however it would fail sending texts frequently and dropped calls like crazy.  Ended up being able to go back to MC2 until i could get a proper MK4 update.  There are 2 ways around Knox that will let you install custom recovery. 1. you can root the phone and delete the knox related files or you can just not let the phone reboot back into android after you install your custom recovery (all of this info can be found on XDA)  the MC2 i installed came with an app to reset the rom status and tamper counter HOWEVER after i went back to MK4 the knox warranty void status was 1.  At this current point in time it cannot be reset as far as i know. However it does not hurt anything as my phone is out of warranty anyhow.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • as of today band 25 being reduced on Sprint side, EARFCN 8321 is 5 MHz vs 8290 10 MHz here in LES. But when I forced roam to T-mobile it still 10 MHz band 2 EARFCN 750.
    • I sent mine back a few weeks ago. My power went out for 2 seconds and it went back to search mode. If the pebble gets disconnected from power for any amount of time, it needs to be completely re-configured. Decided it wasn't worth the hassle. I have wifi calling so I get phone calls and if I don't get texts,....depending on who it is from that's actually a bonus.
    • Just did some quick adding and 70% of the US population is in the largest 114 US MSAs. If Dish covered every MSA above 475k population (so, everything from Lafayette, LA on up), and service stopped completely outside MSA borders, they'd hit their 70%. That's while covering none of places as large as Reno, NV. Oh, and if you cover the San Juan, PR MSA, you can just hit the top 110 other MSAs, down to Pensacola, FL (so, everything with >= 500k population). Now, I fully expect Dish to omit some MSAs in the top 114 in favor of others that are closer to their footprint, or have more Boost Mobile user concentration, but this isn't a ridiculously huge lift...and is why Dish is saying they'll be building out only 15k cell sites by 2023...and they'll have help from T-Mobile as TMo casts off a bunch of redundant sites, many of which would love to immediately get a new tenant.
    • Thing is, building a coverage focused network to cover 70% of the US population using 600 isn't *that* expensive. It's the capacity play that's expensive. You need capacity if you have a ton of customers, which 10MM isn't. Alltel had 12 million customers when Verizon bought them, and covered a larger area than Dish will need to. If you spend $5 billion building a network for, say, 15 million customers, and don't have to subsidize those customers, that's not a huge outlay in the scheme of things.
  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...