Hello,
Did Samsung ever fix the low level volume fluctuation problem through the headphone connection on the 7.0+? Listening to lower level music files at lower volumes resulted in the volume jumping up and down slightly. The problem occurs regardless of whatever music player app is used. The files play fine on the Samsung Galaxy 5.0 player and other devices.
Thanks!
Update: It's not fixed.
This thread is the only reference I could find to this issue anywhere. Is it documented more fully somewhere else? Is Samsung aware of it and planning to fix it? Any references or other help would be greatly appreciated.
I've had my 7.0 Plus for about a week, and yesterday was the first time I tried listening to some classical music favorites featuring very soft choral passages. I couldn't. The volume surges every couple of seconds during soft passages. It sounds as if some demented engineer thought it would be a good idea to add an automatic volume equalizer to make sure the music never gets too soft. No. Very bad idea.
Until I found this thread, I thought I had a defective device or was losing my hearing. I'm glad that neither is the case. Again, please post links to further info about the issue. TIA.
Sun_Cat said:
Until I found this thread, I thought I had a defective device or was losing my hearing. I'm glad that neither is the case. Again, please post links to further info about the issue. TIA.
Click to expand...
Click to collapse
I've had the same problem with 6210 from day one. Other than album art being screwed up, it's the only real annoying problem I've had with the box.
The problem may be in the default player. I use poweramp and don't experience that
Sent from my DROID BIONIC using XDA
It's not just the default player. I've experienced it in the Rhapsody app too. Also see the OP, which says regardless of app and also strongly imples that the issue has been discussed before.
Sun_Cat said:
It's not just the default player. I've experienced it in the Rhapsody app too. Also see the OP, which says regardless of app and also strongly imples that the issue has been discussed before.
Click to expand...
Click to collapse
I hear it using TuneIn Radio. Hoping for a fix with ICS.
UPDATE
I've found two earlier references to the issue:
A review on Amazon from last November (reviewer says he's notified Samsung)
A post by this thread's OP, also from November (like me, he thought it sounded like Automatic Gain Control; unlike me, he remembered the right name for that feature )
Again, any more references, especially from Samsung, would be appreciated.
ETA: I found one on the Samsung support page (search for the string "How can I stop the volume" and click on the text to open the answer). It was answered, not by Samsung but by an anonymous user, who said "Sorry charlie, but you've got a headphone jack with a malfunctioning sensor. Sorry!"
I suppose that's a plausible explanation, but against it is the Amazon reviewer, who said he had the same problem with two different units. And then there's me and the OP here.
redsmear said:
The problem may be in the default player. I use poweramp and don't experience that
Click to expand...
Click to collapse
I installed Poweramp. Nice app, but it doesn't help with this problem at all.
To hear the problem you have to be playing music with sustained passages that are very soft. With most pop, rock, and jazz it won't be noticeable. That's probably why the issue isn't more widely reported.
Try this video in your YouTube app. If your Tab Plus is behaving like mine, you'll hear several volume surges during the first 20 seconds or so. ETA: Crap! I can't post outside links. Here's the last part of the YouTube URL, after the slash: watch?v=6-i1ESIRKdA.
One more clue
And I found one more indirect clue in the Samsung Troubleshooting Guide under the heading GT-P6210 Volume Drops When Headphones Are Plugged In:
The volume on your Tablet will drop 75% when you plug in your headphones. This is a preventive measure for acoustic shock to your ears. The volume can be increased after the headphones are connected.
Click to expand...
Click to collapse
Obviously this proves nothing about the issue we're discussing, but it is suggestive because it tells us that something in the firmware is deliberately designed to mess with the headphone volume.
Aha, so it's not just me who noticed this "feature" then
For anyone who is experiencing this issue and wants to let Samsung know about it in one place, I've started a public thread on their Facebook support wall. You'll have to imagine the first part of the usual Facebook URL since I can't post links. Here's the last part, after the slash: samsungsupport/posts/10150588609036213
Nothing from Samsung Support on Facebook since yesterday morning. One other person has posted there (thanks, Mark, if you're reading this). It would be nice if a few others would chime in.
I'll chime back in. I'm glad somebody else has finally noticed! The problem also exists with the Verizon SCH-i810 (Tab 7.7) but, perhaps, to a lesser degree.
I strongly suspect the (Yamaha?) driver and/or its configuration -- see the original post from November that shows the (configuration?) files. I suspect that file may hold the key to the problem. Problem is, I have no idea what the numbers actually mean and didn't find any documentation for those numbers (data sheets, etc.). I did attempt at the time to tweak a few numbers using my "best guess" by comparing the entries for rx-speaker vs. rx-headphone vs. rx-headset. but no discernible effect was heard.
No prizes for guessing who was raising such a fuss in November.
The "Sorry Charlie" answer is incorrect and I flagged it as such.
UPDATE: I found the 7.0+ /etc/audio files and I have the 7.7 /etc/audio files. There are some differences in the numbers and the 7.7 audio files (LVVEFS) have some comments (!!!) in them so maybe I can track down pertinent parameters.
Anyone else have an opinion or another idea? Is this a waste of time?
Thanks again to everyone who posted here. If you've been watching the Samsung wall on Facebook where I posted last week you've noticed that they haven't responded at all except to ask one simple question, which I answered immediately. Since then, crickets.
If you're experiencing this issue and you feel comfortable saying so in public, please add your comment to the post on Facebook. Maybe we can guilt them into responding.
Thanks.
Sun_Cat said:
Thanks again to everyone who posted here. If you've been watching the Samsung wall on Facebook where I posted last week you've noticed that they haven't responded at all except to ask one simple question, which I answered immediately. Since then, crickets.
If you're experiencing this issue and you feel comfortable saying so in public, please add your comment to the post on Facebook. Maybe we can guilt them into responding.
Thanks.
Click to expand...
Click to collapse
They just answered about 1/2 an hour ago. They provide a link and ask us to go to the Samsung Service Facebook page and fill out a support form. Might as well. Keep the pressure up on someone over there.
Agreed. I just submitted their form with full details. We'll see whether they follow through.
A hint to anyone posting there: Samsung appears to be great at stalling by asking follow-up questions. Include as many pertinent details as possible in the initial post, such as model, wi-fi or data-enabled, serial number, firmware, streaming or stored music sources, which apps, etc., etc., and so forth.
Well, at least they're responding, but I'm not sure it's helping. This morning they replied to my original Facebook post:
We can suggest checking to see if the same problem occurs in a different set of headphones or speakers. If the problem persists we will suggest servicing your Tab.
Click to expand...
Click to collapse
I've already checked with different headphones (not speakers; I've already told them several times that it's a headphones-only issue!), so I already know that the problem isn't due to one set of headphones.
This gives me zero confidence that they actually understand the issue. (Except that it's possible -- though in my view unlikely -- that it is a defective headphone jack.) I'm reluctant to send it in for service. The problem is subtle enough that someone lacking a trained musician's ear is likely to just say it's fixed and send it back. We already know that the fellow who mentioned this issue in his Amazon review got a second unit exhibiting the same defect.
Also, I have not heard from Samsung directly in response to submitting the official support form the other day, so I can't now tell whether or not this latest comment on the wall is coordinated with that other support request.
Does anyone have any advice? Has anyone here dealt successfully with Samsung support in the past, on any issue at all? How did you do it?
Sun_Cat said:
...This gives me zero confidence that they actually understand the issue. (Except that it's possible -- though in my view unlikely -- that it is a defective headphone jack.)
Click to expand...
Click to collapse
I agree. I don't believe it's a headphone jack issue either. I'm going to wait until ICS comes out and then decide what to do if it's still an issue.
I've tried adjusting some numbers in the .txt files -- no change yet. Maybe I'm adjusting the wrong file. Who knows?
I'm surprised there aren't more complaints. It's easy to identify. Headphones, earphones -- doesn't matter. The problem exists with Samsung's earphones. They can't run away from that one. Doesn't the 7.0+ come with four audio files? I can't recall if the problem could be reproduced with those files, because the problem needs periods of relative silence to get into the "AGC" mode. I think the Samsung support is in typical "denial mode". Problem? What problem? Let's go through all the permutations of user error or workaround before considering that there is a problem. It's a matter of problem ownership -- and Samsung isn't owning it.
The questions I would ask are: "Have you tried reproducing the problem?" "Do you know how to reproduce the problem?" "Who has the capability to reproduce the problem, if you can't".
Yes! Just found the Samsung music files, going to try to reproduce with all Samsung supplied software and equipment.
UPDATE: Reproduced the problem on Galaxy Tab 7.7 with all Samsung supplied files/software/equipment:
MATERIAL:
1. Samsung supplied "Music Player", no EQ
2. Samsung supplied music file "Silky whisper.mp3"
3. Samsung supplied earphones, white with button and mic (I think it's pretty generic to Samsung)
Steps:
1. Start Music Player.
2. Make certain volume is all the way down and the sound is muted (slash through speaker)
3. Press the volume up button once, twice (once to unmute and one step higher)
4. Play music file. Note how the piano cuts in and out throughout the song, especially during the opening of the instrumental.
I suspect that Samsung is going to hand this issue off to Yamaha. The constant in this matter is the Yamaha-sourced audio chip/driver/library/configuration/firmware.
Here are some files to compare from /etc/audio (I added the model to the name):
TonyBigs said:
It's a matter of problem ownership -- and Samsung isn't owning it.
Click to expand...
Click to collapse
Agreed. That's why my first question to them on Facebook was "Are you aware of the problem?" No way will I send my GT7+ to them for service until they take that step.
I'll try your steps later today and see if I get the same result. Maybe we can gang up on them.
I have one additional datum since last week. I've tried to reproduce it on Bluetooth headphones, and the problem does not show up. It's only there with plugged-in headphones.
I suppose this could be interpreted as evidence slightly inclining toward the "defective headphone jack" theory. But I still don't think so. If anything, I think it could be related to the Self Aware Volume Ghost on the Galaxy Nexus, which Samsung apparently did acknowledge. Except the Nexus bug was much more obvious since the volume control indicator actually appeared on the screen and changed.
Related
Greetings all, first time post / long time watcher. Love the forums, been on Android since the very first G1 and these forums have been fantastic over the years.
I have Cyanogenmod 3.4.0 June 7th nightly and have been having this same issue since the first. Headphones work great for music, movies, etc... Even can hear emulated DTMF tones just fine, however when I get into a call there is no far end audio coming through, pretty weird. If i unplug the headset, i can hear just fine from the phone speaker. It is only when the headset is plugged in... What gives? Just wanted to make sure that someone was aware and that there is a bug worth fixing. I noticed in the nightly thread (which i am not authorized to post to yet) that others have complained about this as well. Wish I could collaborate there, but alas I cannot so here I sit on Q&A.
Outside of that, GPS issue is a bother. Must disable "Wi-Fi & mobile network location" in order to sync up with a GPS. Doing this kills the location features which is a super downer, so I find myself toggling this on and off all the time just depending on what I need to do.
I am able and willing to provide technical feedback in the form of logs, images and whatever is needed to help resolve. Just let me know what I can do. Thanks a bunch!
Robert
Sent from my SCH-I545 using xda app-developers app
At least you have that. Nothing fixes mine. Won't even see one bird. ..
Having the same problem with GPS
ogonzoo,
I'm having the same problem with GPS. So far, I haven't been able to get it to work except by toggling off the Wifi/Mobile Network location. I did run across a post mentioning a possible fix involving a Touchwiz ROM, but I'm not sure I understood.
I found this other thread seeming to explain the procedure for actually implementing that fix, but I don't know how to apply it to the Cyanogenmod Nightly ROM (assuming that's even possible). Hopefully someone else here will.
EDIT:
Apparently, there's a pretty extensive discussion of this problem in the thread where I read invisiblek's post (first link above), starting at about page 31. It seems to be an acknowledged bug and the Cyanogenmod devs are supposed to address it in a forthcoming build.
Hey guys! New to XDA. To keep this post short and simple, i bought the new Nexus 5 and so far its been great. However, i do have a slight problem that irks me in a bad way. At times google now will pick up my voice no problem. Google search, send a text, open a app you, call someone you name it, it works fine. Recently, however, google now tends to not pick up my voice, and the only way to remedy this is by restarting the phone. I remember reading about people have microphone issues and that phone calls sound muddy and video recording at times with bad units barely picks up ones voice. I, on the other hand, do not experience these problems. Only google now seems to show this problem. If anyone could help that'd be great . Im thinking since my video recording and phone calls are fine, its not a hardware issue. Do you think it might be software? I unfortunately cant post a video link in here so...ill try to rack 10 posts somewhere quick.
so it turns out XDA makes it pretty hard to post 10 posts. Just to get the quickest results, if you guys are up for it you can find the video on youtube. Just search "Nexus 5 Google Now glitch". the videos under the name john doe...lmao:good:
I have the same issue myself. 'OK Google' will work fine, then for some reason a while later it'll stop working. Sorry to say I don't know how to remedy it without a restart, but don't worry too much because it is a bug that is affecting other people too.
i see. im just wondering because if its a hardware issue i would wanna return it before im out of time.
So I've recently updated to the current oreo Beta on my MHA-L29 and I'm facing issues with the Bluetooth audio codec selection. Regardless of what device I connect, Android always switches to the lowest possible settings aka 44. 1kHz streaming and 16bit sample after stopping/starting audio (its enough for a song to end and a new one to start to reset those) now visually the settings don't actually change at all as long as a Bluetooth device is connected, so even if I change to 96kHz the option displays 44.1kHz, however the change in sound quality is definitely noticeable since 44.1kHz has atrocious artifacts on any higher note.
Now my question would be if this is beta related, a general oreo bug or If anyone actually has an idea on how to fix this issue.
Build number: 8.0.0.361(C432)
Bumping this since I still haven't found a fix and maybe someone else has the same issue.
Having the same issue on a Mate 10 Pro, seems to be an Android 8 related problem.
Same issue here.. but bluetooth does work well
Having the same issue, do you think they will fix it?
Updated to .363 today and unfortunately the issue still persists, i am actually starting to get worried now that it will take quite a while for this to be fixxed, if it is adressed at all.
I'm having this issue as well and this is absolutely atrocious.
Ever since I upgraded to android 8 my bluetooth audio sounds like crap. There is very noticable overall hissing and lots of cracking (most noticeably on drums in music).
I also tried digging in the developer options but nothing will stick, this is the first and last time I ever bought a Huawei product.
Arthurvben said:
I'm having this issue as well and this is absolutely atrocious.
Ever since I upgraded to android 8 my bluetooth audio sounds like crap. There is very noticable overall hissing and lots of cracking (most noticeably on drums in music).
I also tried digging in the developer options but nothing will stick, this is the first and last time I ever bought a Huawei product.
Click to expand...
Click to collapse
Im pretty sure Huawei is not to blame for this, since i've seen reports from other phones aswell having the same problem, i believe its an Oreo problem in general that adds ontop of the other bluetooth connectivity issues.
Ran into the same issue myself. Unacceptable audio quality reduction since Oreo update a few days ago. Rolling back to Nougat for now. Based on what I could find, seems to be just as much Google's fault. I really don't like what they did with the notifications either. The app running in the back round is just plain annoying since you can't turn it off.
Syndirail said:
So I've recently updated to the current oreo Beta on my MHA-L29 and I'm facing issues with the Bluetooth audio codec selection. Regardless of what device I connect, Android always switches to the lowest possible settings aka 44. 1kHz streaming and 16bit sample after stopping/starting audio (its enough for a song to end and a new one to start to reset those) now visually the settings don't actually change at all as long as a Bluetooth device is connected, so even if I change to 96kHz the option displays 44.1kHz, however the change in sound quality is definitely noticeable since 44.1kHz has atrocious artifacts on any higher note.
Now my question would be if this is beta related, a general oreo bug or If anyone actually has an idea on how to fix this issue.
Build number: 8.0.0.361(C432)
Click to expand...
Click to collapse
Is your Bluetooth turned off while you changing the setting. I think bluetooth need to be turned off if you want setting to stick. I tried my phone and it is keeping the setting
zhouqishi110ok said:
Is your Bluetooth turned off while you changing the setting. I think bluetooth need to be turned off if you want setting to stick. I tried my phone and it is keeping the setting
Click to expand...
Click to collapse
Yeah it does...until you turn bluetooth on again.. Ive tried absolutely everything unfortunately.
Syndirail said:
Im pretty sure Huawei is not to blame for this, since i've seen reports from other phones aswell having the same problem, i believe its an Oreo problem in general that adds ontop of the other bluetooth connectivity issues.
Click to expand...
Click to collapse
I couldnt care less about who's to blame, its unacceptable Huawei pushed this update through with such a major bug in it. If they couldnt fix developer settings not sticking, the least they could've done is make people aware of this issue when they offered the update. I use my phone for music A LOT and if I had known this in advance I would have never updated in the first place. Now im stuck with this crappy audio quality on a phone I paid 655 euros for.
Welp, that's what you get for not waiting around for bug reports I guess....
Does anyone here know if there is a safe way to downgrade back to Nougat without voiding your warranty? I know how to root etc. but I dont feel like totally breaking open my phone again, I got out of that world a while back because I wanted to avoid this crucial stuff not working the way it should stuff. If there is no other way Ill void my warranty but I'm seeing lots of different guides on here and none of them seem that professionally made so I'm kinda on the fence
Arthurvben said:
I couldnt care less about who's to blame, its unacceptable Huawei pushed this update through with such a major bug in it. If they couldnt fix developer settings not sticking, the least they could've done is make people aware of this issue when they offered the update. I use my phone for music A LOT and if I had known this in advance I would have never updated in the first place. Now im stuck with this crappy audio quality on a phone I paid 655 euros for.
Welp, that's what you get for not waiting around for bug reports I guess....
Does anyone here know if there is a safe way to downgrade back to Nougat without voiding your warranty? I know how to root etc. but I dont feel like totally breaking open my phone again, I got out of that world a while back because I wanted to avoid this crucial stuff not working the way it should stuff. If there is no other way Ill void my warranty but I'm seeing lots of different guides on here and none of them seem that professionally made so I'm kinda on the fence
Click to expand...
Click to collapse
Fair enough point. You can downgrade safely via the Huawei pc application, just choose update and it should give you the option to downgrade. It will however most likely factory reset your phone so I'd advise you create a backup first.
Syndirail said:
Fair enough point. You can downgrade safely via the Huawei pc application, just choose update and it should give you the option to downgrade. It will however most likely factory reset your phone so I'd advise you create a backup first.
Click to expand...
Click to collapse
I downloaded the HiSuite app and there is no downgrade option anywhere.
Edit: Windows 10 antivirus says the downloaded .exe from the official Huawei website is a virus, anyone else have this?
Hello. I've been playing around with the Bluetooth settings and I've found out that while playing Spotify through BT, if I change the kHz to 48 or higher the sound is actually getting better! Although the setting isn't sticking or showing, I'm getting way better sound choosing 48 kHz or better after I press play. Maybe just my phone, but try it out if you're experiencing bad quality BT sound!
Thanks. Will try the 48k sound mode out
I was having this problem with my P20 Pro and Sony WH1000XM2s. Turns out you can get the aptx HD codec and 24bits setting to stick if you select 'Priority on Sound Quality' within Sony's Headphones app. Sample rate is still stuck on 44.1khz however.
Edit: Just turned off bluetooth and set sample rate to 96khz, turned bt back on and it's sticking!
Hello everyone! I've bought this device recently (1 day ago) and found a (I suppose it belongs to it) hardware bug with sound from side loudspeaker. And I am very surprised that nobody wrote similar thread in this forum. UPD: found thread here, sorry, forgot that word "speaker" suits... I "represent" Russian-speaking community from 4pda, and this issue is met pretty often.
The point is when you play video or play some games or simply type some text (with typesound), the loudspeaker can "eat" some part of playable sound. It is absolutely random when you play it without any charger and not random when the charger is plugged. We named it "sound hiccup" and this problem was discussed in some threads on Samsung forum, but there was no any normal solution of this problem.
I've recorded some video to show it to service center and I'm showing it to you:
Timecode when it starts is 1:10. Then I showed that it works below volume threshold and is OK above it.
So, did you meet same problem? If yes, how did you fix that? Phone is new, as it appeared, it is from UAE (the phone has its ROM, I'm from Ukraine), I can't reflash my phone until I send it to SC and receive it back but some users with different ROM region have the same problems but not at the same moments as I have.
Hope for your help, thanks!
I have that bug too
Can you join here https://t.me/joinchat/CS3WpUl4nQVgtOrA2zt4KA
It's a telegram group for a8
Hi all,
I pre-ordered my S22U and got it last Wednesday.2/23/22. (USA)
Had a couple issues when using android auto:
1. When replying to a message after its been read to me, I dictate the message it says its sent, but it never gets sent. Once I've stopped somewhere and talk to the person the message was supposedly sent to they say they never got it. Its not my vehicle because its happening to my boyfriend who also got the S22U, and he has a totally different brand of vehicle than I do. Super frustrating when I think I have sent a message, and an hour or so later find out it didn't go through like it said it did. This happens for text messages and also with Facebook messenger messages.
2. When android auto is reading me the messages, or reading me waze directions, the first portion of the reading has an annoying echo then it stops echoing. Same for my boyfriends vehicle and his S22U. We are both using our phones connected via an OEM USB cable (the only way to use android auto in both vehicles it has to be connected with the cable). I've had android phones for years and never had either of these issues before.
Any help is appreciated. Thanks!
uncertain as to what may be causing this, but as you may have already guessed it's probably a software issue.
I suggest you report error after reproducing the issue (in a safe manner of course).
Samsung Members app > get help > error report.
it's best if you provide step by step on how you reproduce the test, so that samsung engineers can better identify where the issue occurred.
TheNewGuy92 said:
uncertain as to what may be causing this, but as you may have already guessed it's probably a software issue.
I suggest you report error after reproducing the issue (in a safe manner of course).
Samsung Members app > get help > error report.
it's best if you provide step by step on how you reproduce the test, so that samsung engineers can better identify where the issue occurred.
Click to expand...
Click to collapse
There is no error code........
google auto app issues since 2021. try older version of app. jan 2021 version works fine for me.
malikin said:
google auto app issues since 2021. try older version of app. jan 2021 version works fine for me.
Click to expand...
Click to collapse
I never had any issues at all with Android Auto until I got the S22 Ultra. So that isn't it. Its something to do with this phone.
LadyGamer955 said:
I never had any issues at all with Android Auto until I got the S22 Ultra. So that isn't it. Its something to do with this phone.
Click to expand...
Click to collapse
just try an older version from APKPURE
Sadly I have got the same problem with the Galaxy S22 Ultra and Android Auto (echo at the beginning). This gets quite annoying especially with navigation instructions. Didn't have this issue with the Galaxy Note 20 Ultra.
Denyo2 said:
Sadly I have got the same problem with the Galaxy S22 Ultra and Android Auto (echo at the beginning). This gets quite annoying especially with navigation instructions. Didn't have this issue with the Galaxy Note 20 Ultra.
Click to expand...
Click to collapse
Glad to know its not just me. Another friend also has an S22 Ultra and a different type of vehicle than I do and same problems. And so many times I dictate a response to a message it reads it back says it was sent and it never sends it. Also never had this issue with Note 20 Ultra
LadyGamer955 said:
There is no error code........
Click to expand...
Click to collapse
you don't need an error code. Error submission using the samsung members app is manual submission that users do when the phone shows an issue but does not recognize that there is an issue.
If you see something and think it's an issue regardless of error code or messages, you can submit/report issue.
Any fix to this stupid issue yet? Im experiencing it with my s23+
kevindd992002 said:
Any fix to this stupid issue yet? Im experiencing it with my s23+
Click to expand...
Click to collapse
I have just got a Samsung S22 and have the exact same issue....Google haven't replied and Samsung just say its probably the phone.... My old S20 FE never had the issue
So, I found the answer in another thread. Turn equaliser settings to normal in sound and turn off adapt sound mode... this cured the echo. The minute I turn it back on, the echo comes back.
For Waze, also leave the sound settings with adapt sound off and normal equaliser, but change the waze voice to a different one. Both issues fixed.
Be interesting to know if other people with the same phone have been able to change their sound settings and the car sounds OK.
SLS1972 said:
So, I found the answer in another thread. Turn equaliser settings to normal in sound and turn off adapt sound mode... this cured the echo. The minute I turn it back on, the echo comes back.
For Waze, also leave the sound settings with adapt sound off and normal equaliser, but change the waze voice to a different one. Both issues fixed.
Be interesting to know if other people with the same phone have been able to change their sound settings and the car sounds OK.
Click to expand...
Click to collapse
Could you please upload some screenshots ?
Change the equaliser to normal.. and turn adapt sound to none. This cured the echo in my car for Android auto. I have custom setting on my S20 and it doesn't affect it.. but the S22 does.... its weird how two phones can behave differently with AA.