Not sure if I'm just getting old, but dang the volume seems way too loud when I try and use headphones on my GT 10.1 Wifi. Even on the lowest level. Any way to lower the default volume level for headphones?
Yes, this is a volume level software defect stupid Samsung engineers screwed up. Its mind boggling how they tested this and thought to themselves "Yes, this is good".
Going from mute to the lowest volume level is ridiculously loud in a quiet room when using either the speakers or head phones. The funny thing is going to the next 2 or 3 steps up barely increases the volume. Its all screwed up.
It really does suck and Im not sure Samsung has any plans on fixing this.
5thElement said:
Yes, this is a volume level software defect stupid Samsung engineers screwed up. Its mind boggling how they tested this and thought to themselves "Yes, this is good".
Going from mute to the lowest volume level is ridiculously loud in a quiet room when using either the speakers or head phones. The funny thing is going to the next 2 or 3 steps up barely increases the volume. Its all screwed up.
It really does suck and Im not sure Samsung has any plans on fixing this.
Click to expand...
Click to collapse
If you rooted flash a kernel that supports voodoo sound, then download voodoo control or voodoo control plus and lower the headphone amplifier.
That does not work. Voodoo control does not work to lower the volume. Yes there is an option to lower the gain on the amplifier but it does not work and its very buggy when you map the hardware volume buttons to the voodoo gain control. I tried it.
5thElement said:
That does not work. Voodoo control does not work to lower the volume. Yes there is an option to lower the gain on the amplifier but it does not work and its very buggy when you map the hardware volume buttons to the voodoo gain control. I tried it.
Click to expand...
Click to collapse
Voodoo control works for me. Rooted with Starbust UEKME and pershoot's kernel. I have custom IEMs with an input sensitivity of 119dB at 1mW. I have to set it to -55 dB on Voodoo.
ya but thats just for headphones. Does not change the speakers volume.
But it would work for the op as he was talking about headphones
Sent from my GT-P7510 using xda premium
For some reason I don't have this problem. I have never used lower volume then about 25%, usually it's at about 50%. BTW my hearing is just fine. I use a-JAYS Three headphones.
I think the impedance of the headphones plays a role in this. Headphones with lower impedance are louder.
Yes impedance definitely plays a role but the problem is with standard headphone impedance the volume is WAY too loud.
This is a big problem with the tab 10. Speakers play way too loud at the lowest volume setting....you hear me Samsung!! You hear me!!!!!
I just tried the built in speakers, one step up from muted and i can hear that it's playing very quietly if i hold the tablet normally. I need to put my ear next to the speaker to really hear enough to understand what song is playing.
So clearly my tablet doesn't have this problem.
On a standard UK rom here and my speakers appear to be fine, not too loud. Odd.
UKseagull said:
On a standard UK rom here and my speakers appear to be fine, not too loud. Odd.
Click to expand...
Click to collapse
There is nothing odd about it. Your unit is exactly the same as ours. Different people have different hearing sensitivity. My hearing is excellent and above average so I can hear the music play too loud even on the lowest setting. Others will figure it is fine as hearing sensitivity varies.
The volume levels are simply all screwed up. You can see for yourself as turning the volume from 1 to the next 2 levels and the volume barely increases. Going from 1 to 2 almost does not even increase the volume at all. Going to 3 only increases it slightly then 4 and up increase at too high of levels to make up for the lack of volume increase going from 1 - 2 and 2 - 3. The levels are all screwed up. Horrible job by samsung.
I also have this issue!! The volume can' t be changed when using headphones and the volume is too loud for normal use
You can buy headphones with a volume control or a in-line volume control adapter for headphones but that still does not resolve the issue for the output to the speakers.
Does anyone know which headphones (earbuds) are compatible with N6? I've tried a few different ones including apple, shure, htc and ifrog and none can control volume, answer/hang up call, or change tracks. All I've been able to do is start/stop music. Any suggestions for headphones that can perform those functions (confirmed, not speculation)?
Xiaomi pistons work fine. Be sure not to get the fake ones, you find reviews of the product on xda as well as head fi. Relatively cheap too, around $25
Sent from my Nexus 6 using Tapatalk
cygnusx8 said:
Does anyone know which headphones (earbuds) are compatible with N6? I've tried a few different ones including apple, shure, htc and ifrog and none can control volume, answer/hang up call, or change tracks. All I've been able to do is start/stop music. Any suggestions for headphones that can perform those functions (confirmed, not speculation)?
Click to expand...
Click to collapse
Link?
I can answer/end calls just fine with my PowerBeats and an old pair of Vmoda that are a few years old. Neither has volume keys so cant help you there.
Xiaomi pistons 2 are awesome for the price. The output has amazing sounds that are well worth more than they are priced at.
LG tone pro work great. voice dialing, answer/end calls, and volume work. Skip tracks and pause do not work
Majority of headphones with volume controls are MFI certified, meaning they will only work with apple devices. They're some, which by chance, happen to work with android devices; however, they are rare. I believe Bose makes some headphones for android with incorporate volume controls. unfortunately, most of the time you will find that android certified headphones only have single button option. Also, the higher quality ear/headphones almost never have mics or button controls.
stas333 said:
LG tone pro work great. voice dialing, answer/end calls, and volume work. Skip tracks and pause do not work
Click to expand...
Click to collapse
Skip and pause work fine with my LG Tone Pro's. All features work as they are supposed to with mine.
Just get the Samsung ear buds that come with any Samsung phone it works.
Beats UrBeats volume control doesn't work (Chroma ROM)
zephiK said:
Xiaomi pistons work fine. Be sure not to get the fake ones, you find reviews of the product on xda as well as head fi. Relatively cheap too, around $25
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Seconding this, they sound pretty good and volume buttons work just fine. A pair can be had for under $20 from banggood.
Sent from my Nexus 6 using Tapatalk
Hello everyone,
I recently purchased a Xiaomi Piston 3 headset to use with my Nexus 6P, and I was disappointed to discover that I was unable to lower the volume of sound through the decrease volume button on the headset. I initially believed this was the result of a defective audio jack on my Nexus 6P, since the headset worked fine on a friend's Nexus 5X. However, after discovering reports of other people having the same issue with the Xiaomi Piston 3 headset, I did some tests to see if I could figure out what could be causing this issue.
I used three wired headsets with in-line remote controls (including volume) for my tests: the Xiaomi Piston 3, Samsung HS330, and Sennheiser Momentum In-Ear headset. All three headsets fully support in-line remote controls for Android devices, and they all worked properly on a Nexus 5X. Both the Xiaomi Piston 3 and Samsung HS330 had the same results, but the Sennheiser Momentum In-Ear headset had different results. Here are my results:
Xiaomi Piston 3 and Samsung HS330 headsets
Listening to music on the Google Play Music app: increasing volume and pause/play worked, but decreasing volume did not work.
Listening to music on the home screen with the Google Play Music app running in the background: increasing volume and pause/play worked, but decreasing volume did not work.
Listening to music with the screen turned off and With screen locked and Google Play Music running in the background: increasing volume and pause/play worked, but decreasing volume did not work.
Sennheiser Momentum In-Ear headset
Listening to music on the Google Play Music app: increasing volume, decreasing volume, and pause/play worked.
Listening to music on the home screen with the Google Play Music app running in the background: increasing volume and pause/play worked, but decreasing volume did not work.
Listening to music with the screen turned off and With screen locked and Google Play Music running in the background: increasing volume, decreasing volume, and pause/play worked.
I am not an audio expert, but I was surprised by these results. I have no idea why both the Xiaomi Piston 3 and Samsung HS330 headsets were unable to decrease sound volume, but the Sennheiser Momentum In-Ear headset was able to do so in most situations. I am also very puzzled as to why the Sennheiser Momentum In-Ear headset was able to decrease volume while in the Google Play Music app and while running the app in the background with the screen turned off, but running the app in the background while on the home screen caused the volume problem to occur.
Hopefully someone more knowledgeable on audio can make sense of these results. It would also be great if others who have a Nexus 6P and a wired headset with Android compatible in-line remote controls (including volume) can test them and post their results here. At best we might be able to find a pattern to this issue, and at the very least we can create a list of headsets with in-line remote controls that have been verified to work.
TheHeeyyy said:
Hello everyone,
I recently purchased a Xiaomi Piston 3 headset to use with my Nexus 6P, and I was disappointed to discover that I was unable to lower the volume of sound through the decrease volume button on the headset. I initially believed this was the result of a defective audio jack on my Nexus 6P, since the headset worked fine on a friend's Nexus 5X. However, after discovering reports of other people having the same issue with the Xiaomi Piston 3 headset, I did some tests to see if I could figure out what could be causing this issue.
I used three wired headsets with in-line remote controls (including volume) for my tests: the Xiaomi Piston 3, Samsung HS330, and Sennheiser Momentum In-Ear headset. All three headsets fully support in-line remote controls for Android devices, and they all worked properly on a Nexus 5X. Both the Xiaomi Piston 3 and Samsung HS330 had the same results, but the Sennheiser Momentum In-Ear headset had different results. Here are my results:
Xiaomi Piston 3 and Samsung HS330 headsets
Listening to music on the Google Play Music app: increasing volume and pausing worked, but decreasing volume did not work.
Listening to music on the home screen with the Google Play Music app running in the background: increasing volume and pausing worked, but decreasing volume did not work.
Listening to music with the screen turned off and With screen locked and Google Play Music running in the background: increasing volume and pausing worked, but decreasing volume did not work.
Sennheiser Momentum In-Ear headset
Listening to music on the Google Play Music app: increasing volume, decreasing volume, and pausing worked.
Listening to music on the home screen with the Google Play Music app running in the background: increasing volume and pausing worked, but decreasing volume did not work.
Listening to music with the screen turned off and With screen locked and Google Play Music running in the background: increasing volume, decreasing volume, and pausing worked.
I am not an audio expert, but I was surprised by these results. I have no idea why both the Xiaomi Piston 3 and Samsung HS330 headsets were unable to decrease sound volume, but the Sennheiser Momentum In-Ear headset was able to do so in most situations. I am also very puzzled as to why the Sennheiser Momentum In-Ear headset was able to decrease volume while in the Google Play Music app and while running the app in the background with the screen turned off, but running the app in the background while on the home screen caused the volume problem to occur.
Hopefully someone more knowledgeable on audio can make sense of these results. It would also be great if others who have a Nexus 6P and a wired headset with Android compatible in-line remote controls (including volume) can test them and post their results here. At best we might be able to find a pattern to this issue, and at the very least we can create a list of headsets with in-line remote controls that have been verified to work.
Click to expand...
Click to collapse
I have a couple of sets of the piston 2. My first 6P didn't even recognise anything was plugged into the headset. Would simply not play audio through the jack. I tried 3 more brands a Klipsch and Jaybirds and an Apple pair. The Klipsch recognised only 50% of the time and remote would not work other than Pause/Play. The Jaybirds played but remote did not work at all and Apple earbuds worked but only play/pause
I got a new 6P to replace that model and headphone situation is much the same however it recognises the Piston 2's but may have to plug in and out a couple of times and again remote does not work at all.
All these headphones work with the myriad of Android devices I've had this year and last including
Moto X Pure 2014, M9, S6 Edge, Edge +, Note 5, Moto X Style, Nexus 6, OnePlus 2, Xperia Z3 and even Apple 6 plus & 6S Plus ...
So clearly nothing physically with the headphones. I'm not sure WTF is going on with the headphone support and the 6P but suffice to say I'm extremely disappointed by it so far.
Sent from my iPhone using Tapatalk
nookcoloruser said:
I have a couple of sets of the piston 2. My first 6P didn't even recognise anything was plugged into the headset. Would simply not play audio through the jack. I tried 3 more brands a Klipsch and Jaybirds and an Apple pair. The Klipsch recognised only 50% of the time and remote would not work other than Pause/Play. The Jaybirds played but remote did not work at all and Apple earbuds worked but only play/pause
I got a new 6P to replace that model and headphone situation is much the same however it recognises the Piston 2's but may have to plug in and out a couple of times and again remote does not work at all.
All these headphones work with the myriad of Android devices I've had this year and last including
Moto X Pure 2014, M9, S6 Edge, Edge +, Note 5, Moto X Style, Nexus 6, OnePlus 2, Xperia Z3 and even Apple 6 plus & 6S Plus ...
So clearly nothing physically with the headphones. I'm not sure WTF is going on with the headphone support and the 6P but suffice to say I'm extremely disappointed by it so far.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thank you for posting your findings. I have seen posts on Reddit with Nexus 6P owners having issues with the Xiaomi Piston 2 headset. It looks like no one has had any luck with getting the in-line remote controls working, and some people are not able to play audio through it at all. The seemingly random results people are having is making me wonder if it is an issue with the quality of the audio jack on the Nexus 6P, the audio connector on the Xiaomi Piston 2 headset, or both.
Your results for the Apple earbuds are to be expected, as headsets designed for Apple devices can only pause and play audio on Android devices. I believe the Jaybird headset uses wireless Bluetooth, so that problem could be the result of a compatibility issue with the Nexus 6P's Bluetooth 4.2 connectivity (despite supposedly being backwards compatible). It would be greatly appreciate if you could post which model Klipsch headset you used, as that can help us create a list of headsets that have been tested out by Nexus 6P owners and the results people had.
Just for some background, that this has been an ongoing issue with android phones for a very long time.
The issue is how each manufacturer wires their headphone jack. Some headsets use the tip or the ring to transmit the remote signals over, and if the headphone jack in the phone is not able to "receive" this signal, or was not setup to get anything but the negative signal on the tip, then you are out of luck.
With there not being a true standard in how phone headsets are wired (the iphone has a way they do it, and then in android they have several ways that the manufacturers wire the phones and then the headsets have the same issues with this).
So... you need to figure out how the headphone jack on the 6P is wired, then we can figure out which headphones will easily work and which ones will for sure have trouble. I am betting that there is something that either has been leaked or was released by Huawei that you can find this out. I will do some poking around as well and see what I can figure out.
I use these, they work fine both pause/play and volume up and down.
https://www.amazon.com/gp/aw/d/B00HSJRT7I
Sent from a 128th Legion Stormtrooper 6P.
jimbridgman said:
Just for some background, that this has been an ongoing issue with android phones for a very long time.
The issue is how each manufacturer wires their headphone jack. Some headsets use the tip or the ring to transmit the remote signals over, and if the headphone jack in the phone is not able to "receive" this signal, or was not setup to get anything but the negative signal on the tip, then you are out of luck.
With there not being a true standard in how phone headsets are wired (the iphone has a way they do it, and then in android they have several ways that the manufacturers wire the phones and then the headsets have the same issues with this).
So... you need to figure out how the headphone jack on the 6P is wired, then we can figure out which headphones will easily work and which ones will for sure have trouble. I am betting that there is something that either has been leaked or was released by Huawei that you can find this out. I will do some poking around as well and see what I can figure out.
Click to expand...
Click to collapse
True, although both the Nexus 5 and Nexus 6 supported inline remote volume controls, and I do not recall either headset having this particular issue. You would think any headset with an OMTP connector would work fine on an Android device (as appears to be the case with my own tests on the Nexus 5X), but the results I have been seeing with the Xiaomi Piston 2 headset alone have been incredibly inconsistent. Hopefully you or someone else can make sense of these results, but for now I am sticking to the theory that the issue is related to both the headphone jack of the Nexus 6P and the audio connector of whichever headset is used on it.
[hfm] said:
I use these, they work fine both pause/play and volume up and down.
https://www.amazon.com/gp/aw/d/B00HSJRT7I
Sent from a 128th Legion Stormtrooper 6P.
Click to expand...
Click to collapse
Thanks for pointing that out. At some point I will make a list of everyone's results and post it in the OP.
I had a chat with Google support this afternoon about why he volume down button on my headphone remote doesn't work with the 6P, but it works fine with the 6. They said they're aware that some people are having issues and are supposed to elevate it and get back with me.
In the meantime, I found the "Android Wired Audio Headset Specification v1.1" which is the first link in Google if you search for that. It has reference values for resistances and tolerances and a test circuit.
Turns out the volume down button on my headset does not conform to the spec. It has a resistance of 616 ohms rather than the 470 ohm +/- 1% in the spec.
My volume up is 216 ohms, which also doesn't match the spec of 240 ohm +/- 1%, but evidently they made the tolerance wider than the spec, which suggests that the volume down tolerance could be increased as well like in the Nexus 6, but no guarantees there.
matthewbudraitis said:
I had a chat with Google support this afternoon about why he volume down button on my headphone remote doesn't work with the 6P, but it works fine with the 6. They said they're aware that some people are having issues and are supposed to elevate it and get back with me.
In the meantime, I found the "Android Wired Audio Headset Specification v1.1" which is the first link in Google if you search for that. It has reference values for resistances and tolerances and a test circuit.
Turns out the volume down button on my headset does not conform to the spec. It has a resistance of 616 ohms rather than the 470 ohm +/- 1% in the spec.
My volume up is 216 ohms, which also doesn't match the spec of 240 ohm +/- 1%, but evidently they made the tolerance wider than the spec, which suggests that the volume down tolerance could be increased as well like in the Nexus 6, but no guarantees there.
Click to expand...
Click to collapse
@matthewbudraitis thank you for the update. I subscribed to this thread, please keep us posted if you hear anything back from them.
I did hear back from Google, but they just asked a few questions about which headset I have and if it happens with all apps.
In the meantime, I did a little more research.
I tested both the Nexus 6P and Nexus 6 with some resistors to see how they work in relation to the spec. The Nexus 6P will recognize a volume down command from 330 ohms to 560 ohms, which explains why the 612 ohms in my headset isn't working. The Nexus 6 will recognize a volume down command from 390 ohms to 680 ohms, which explains why it WILL work with my headset and still work with the spec.
So then I started questioning why my headset would have 612 ohms anyway. From what I could find, 620 ohms is what Samsung and HTC have been using for a number of years and most Android-compatible headsets on the market have been sold to work with Samsung, not all android in general.
Personally, I think it would be best for customers if Google just made the official spec range work like the Nexus 6. It allows for both the current spec and the Samsung/HTC devices to work, which makes the Nexus phones more compatible with what customers already own. I hope the range can be expanded on the 6P with a software update. For my headset, I'm going to solder the correct resistors into it to make it work, but I know that's not a solution for most people.
matthewbudraitis said:
I did hear back from Google, but they just asked a few questions about which headset I have and if it happens with all apps.
In the meantime, I did a little more research.
I tested both the Nexus 6P and Nexus 6 with some resistors to see how they work in relation to the spec. The Nexus 6P will recognize a volume down command from 330 ohms to 560 ohms, which explains why the 612 ohms in my headset isn't working. The Nexus 6 will recognize a volume down command from 390 ohms to 680 ohms, which explains why it WILL work with my headset and still work with the spec.
So then I started questioning why my headset would have 612 ohms anyway. From what I could find, 620 ohms is what Samsung and HTC have been using for a number of years and most Android-compatible headsets on the market have been sold to work with Samsung, not all android in general.
Personally, I think it would be best for customers if Google just made the official spec range work like the Nexus 6. It allows for both the current spec and the Samsung/HTC devices to work, which makes the Nexus phones more compatible with what customers already own. I hope the range can be expanded on the 6P with a software update. For my headset, I'm going to solder the correct resistors into it to make it work, but I know that's not a solution for most people.
Click to expand...
Click to collapse
I'm guessing this is 100% hardware driven and can't be changed in software. Which means we're stuck where we are at, aye?
Elnrik said:
I'm guessing this is 100% hardware driven and can't be changed in software. Which means we're stuck where we are at, aye?
Click to expand...
Click to collapse
I can't say for sure, but based on the test circuit in the spec, I'm assuming they're using a known voltage and resistor value in the device in series with these remote resistors to make a voltage divider. As the headset button resistances decrease, it puts a lower voltage on the mic terminal which can be read by an analog to digital converter in the device. The voltage set points would then be done in software, possibly at a device driver level.
Assuming it works like I think, the set points could be adjusted.
Anyone having issues similar to the Piston 3's (volume down button not working), check out ElementX kernel. Flar2 has included a patch to fix this. Piston 2's still are not working, but it looks like this is fixable in software. Fingers crossed.
chowhoundb said:
Anyone having issues similar to the Piston 3's (volume down button not working), check out ElementX kernel. Flar2 has included a patch to fix this. Piston 2's still are not working, but it looks like this is fixable in software. Fingers crossed.
Click to expand...
Click to collapse
I just found a partial fix for Piston 2 by trial & error, Remember all the buttons are still not functional yet, but atleast you can hear music using your headphones on Piston 2.
To make it work on your Nexus 6P, Press and hold any button on your headphones while plugging your headphones to your Nexus 6P. Again, none of the controls work but at least you can listen to music. Also, the inline mic does not work during calls
chichu_9 said:
I just found a partial fix for Piston 2 by trial & error, Remember all the buttons are still not functional yet, but atleast you can hear music using your headphones on Piston 2.
To make it work on your Nexus 6P, Press and hold any button on your headphones while plugging your headphones to your Nexus 6P. Again, none of the controls work but at least you can listen to music. Also, the inline mic does not work during calls
Click to expand...
Click to collapse
The gentleman who figured out how to fix the piston 3's is currently looking into a solution for the 2's. The issue has also been passed onto google engineers to look into.
chichu_9 said:
I just found a partial fix for Piston 2 by trial & error, Remember all the buttons are still not functional yet, but atleast you can hear music using your headphones on Piston 2.
To make it work on your Nexus 6P, Press and hold any button on your headphones while plugging your headphones to your Nexus 6P. Again, none of the controls work but at least you can listen to music. Also, the inline mic does not work during calls
Click to expand...
Click to collapse
Thanks!!!!! Great tip, I was worried about this, I can't believe I can't use my Pistons on my new Nexus 6P.
My two cents, you can plug in your headphones and then press any buton and they start to work, it is not necesary to press a button while you are connecting them.
I have a set of cheap in-ear earphones with a volume slider which works brilliantly. Is this problem affecting only a few 6P owners or is it applicable to button operated volume controls?
I realize you guys might not want to hear this, but my piston 2s have always worked perfect on my 6p. Controls and all, and they sound great with viper.
Sent from my Nexus 6P using Tapatalk
bikeryder007 said:
I realize you guys might not want to hear this, but my piston 2s have always worked perfect on my 6p. Controls and all, and they sound great with viper.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
That is interesting. I thought this affected everyone. Just curious, do you know if yours are piston 2.0 or piston 2.1's. I have a white pair of 2.1's and a brown pair of 2.1's and both do not work.
UPDATE: nevermind, it looks like the 2.1's are the same as 2.0 with just a slightly longer cable, and different earpieces. They have the same internals so there shouldnt be a difference.
bikeryder007 said:
I realize you guys might not want to hear this, but my piston 2s have always worked perfect on my 6p. Controls and all, and they sound great with viper.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
That's nice to know. I love how my Pistons sound. I cant believe that I am not able to use these puppies with my new phone. I am bummed.
chichu_9 said:
That's nice to know. I love how my Pistons sound. I cant believe that I am not able to use these puppies with my new phone. I am bummed.
Click to expand...
Click to collapse
I just tested them again when I got home from work, and everything is working as it should. I just checked up and down volume and everything. I have the piston 2's with the white cord, silver buds etc... It is weird that so many others are having problems.
Sent from my Nexus 6P using Tapatalk
Is there a way to increase the maximum headphones volume ?
Yes buy another headphone i am already on samsung one and soud is awesome
i use Denon AH-C50MA and sound is great
What's you headphones impedance? Mine piston 2's are loud even 3 volume bars @ 16ohm
Well i don't care about my earphones impedance as my previous smartphone (S3) could easily drive these with louder sound.
I think i will probably give a try with Viper4Android.
I also find the Honor 7 volume levels too low. The phone speaker as well as the headset.
Call volume is low as well but you can fix that by setting it into speaker mode.
The low headset volume annoys me the most. (I use HQ headset)
I found the service mode menu and had hoped i could increase headset volume levels there.
https://youtu.be/r0gSdYQ5egw
Sadly, there is no option. I tried some apps from the playstore but they didnt do anything.
I'm currently (officially) participating in the Android 6 Beta so am not rooted or anything.
Is there a way i can increase the level already?
Or maybe once I have the final Android 6, can i root/unlock the phone and increase the volume in another manner? I want to stay on the original roms, dont want to flash something else on my phone.
Anyone else finding this annoying as well and has a fix?
I am running 80ohm sennheiser dt880 and the volume is high enough for me so every mobile headphone with 32ohm should be easily powered to painful volume . Not sure which media you play, but if you need higher volume i suggest a mobile dac as headphone amplifier