Related
Once my Bluetooth Headset is connected to my Prophet, all my notification sounds come through my Bluetooth Headset instead of the phone speaker.
The sound for normal incoming call works as it should though (through the speaker).
The only way i've found how to solve this problem, is to uncheck the "Wireless Stereo" option under:
Settings > Connections > Bluetooth > i.Tech Clip R35 > Partnership Settings
And then when I want to listen to music through the Windows Media Player, I have to do the opposit.
So, my two questions...
1. Is there a way to map notification sounds to always use the phone's speaker? (or)
2. Is there a small shortcut / Today-plugin that can switch "Wireless Stereo" on/off in one click?
Cheers!
Eric
Mortscript could be used for to create a script that would toggle Wireless Stereo" & then a shortcut to this script could be put on the today screen or mapped to a button.
Do a search on scripts for wifi as many people have done this type of thing already.
Also have a look at this link, might be of some use.
http://www.vijay555.com/?Releases:VJVolubilis
Mister B said:
Mortscript could be used for to create a script that would toggle Wireless Stereo" & then a shortcut to this script could be put on the today screen or mapped to a button.
Do a search on scripts for wifi as many people have done this type of thing already.
Also have a look at this link, might be of some use.
http://www.vijay555.com/?Releases:VJVolubilis
Click to expand...
Click to collapse
Thanks Mr. B.
Interesting idea.
But it seems like the VJVolubilis only supports BlueTooth on/off at this stage, and not switching a BlueTooth service on/off.
And from what I understand the "agon" command passes the audio through the "Headset" service of a BlueTooth device.
Well, I solved it by creating a Mortscript...
It's not beautiful, but it works!
overone said:
Well, I solved it by creating a Mortscript...
It's not beautiful, but it works!
Click to expand...
Click to collapse
It may look ugly in notepad but the beauty is watching it work.
Have fun with your scripts, its a useful tool.
@overone, can u share the script???
shantzg001 said:
@overone, can u share the script???
Click to expand...
Click to collapse
Yes, sure! If you promise not to laugh?
I'm sure there's tons of ways to make this better, but I never used this script language before, and I didn't want to waste an eternity fixing my problem.
Removing the sleeps would be the first things on my mind for an improvement.
As for the shortcut "BluetoothSettings.lnk"; it just a simple shortcut that opens the bluetooth setting panel.
And YES, it's hardcoded to be located in Program Files...
Code:
# Open Bluetooth Settings
Run("\Program Files\BluetoothSettings.lnk")
WaitForActive("Settings",5)
# Go to i.Tech Clip R35
SendDown
SendCR
Sleep(1000)
# Mark/Un-Mark Wireless Stereo
SendDown
SendDown
SendCR
Sleep(1000)
# Exit and Save
SendRightSoft
Sleep(2500)
SendOK
That worked wonderfully for me, and is the only solution I have found so far to automatically turn on my BT Stereo Audio headset.
Download Mortscript from http://www.sto-helit.de
Create a new file ToggleBTStereoAudio.mscr in any folder on your PPC with the following text in it
Code:
# Open Bluetooth Settings
Run("\Program Files\BluetoothSettings.lnk")
WaitForActive("Settings",5)
# Go to i.Tech Clip R35
SendDown
SendCR
Sleep(1000)
# Mark/Un-Mark Wireless Stereo
SendDown
SendDown
SendCR
Sleep(1000)
# Exit and Save
SendRightSoft
Sleep(2500)
SendOK
Create a new file "\Program Files\BluetoothSettings.lnk" with the following in it
Code:
23#ctlpnl cplmain.cpl,23,1
To toggle your BT Stereo simply click on the ToggleBTStereoAudio.mscr file. You will be able to see the mortscript run and toggle the stereo audio for the device.
There's a program called A2DPToggle - freeware
Just came across it myself and it does the job very well - has a Today plugin that can even start A2DP then launch your media player as well as other BT management and speakerphone toggle, or an app that just toggles Wireless Stereo when run
The homepage for it is at http://www.teksoftco.com/index.php?section=freeware
I thought it would be nice if we cfoudl get some Q&A going about this topic.
I'd like to hear which Tornado ROMs seem to have good working A2DP, which BT stack they use (if you know), what headset/remote you're using.
I'd also like to know if anyone can give use directions for checking what stack our phone is using.
I'd also like to know your opinions on volume, hiss, etc.
If you are satisfied or unsatisfied with your volume, please include your audiogain settings for comparision:
HKLM\SOFTWARE\HTC\AUDIOGAIN
(note: audiogain settings are in hexidecimal)
Here is some info on A2DP reg tweaking, that is supposed to be relevant to the WM6 bt stack.
i.e. from the "final" or "official" released, not a beta.
[ Default Settings are as follows: ]
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\
BitPool DWORD 30
MaxSupportedBitPool DWORD 30
SampleRate
UseJointStereo DWORD 1
HKLM\Software\Microsoft\Bluetooth\AudioGateway\
Capability DWORD 37
[ Aternate Settings: ]
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\
BitPool DWORD 51
MaxSupportedBitPool DWORD 60
SampleRate DWORD 48000
UseJointStereo DWORD 0
Cant remember if i changed the one below or it was already at that value.
HKLM\Software\Microsoft\Bluetooth\AudioGateway\
Capability DWORD 60
-----------------
[ Sleuth255's WM6 optimum settings for bluetooth A2DP: ]
These are applicable to the newer releases of WM6.
Finding #1:
ADD/CHANGE the following values from the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings :
Name: UseJointStereo
Value (DWORD): 1
What this does is enable Joint-Stereo for the SBC codec, which is important and makes the biggest significant change to improve sound quality. (Note: In earlier versions of WM5 and WM6, Joint-Stereo was broken and resulted in a mono-output. This is not the case anymore with the newer WM6 ROMS.)
Further note: Sleuth255 found that some of his A2DP headsets could not work with JS turned on. In that case, you have to set the value to 0 to disable JS (resulting in poorer quality sound with more "hissing").
Finding #2:
REMOVE the following values from the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings if they are present:
- BitPool
- MaxSupportedBitPool
These values are used to manually set limits for the BT stack for the A2DP SBC codec. Previously, it was thought that these values should be set between 38 to 86. But if the values are removed, I think that the BT stack automatically chooses the best BitPool values for maximum quality. I've tried removing these values and the sound quality either improved or at least stayed the same.
[ SUMMARY ]
At this point, you should have only one value in the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings:
UseJointStereo = 1
Your A2DP audio should be very good at this point - almost indistinguishable from a wired headset. However, if you are still unsatisfied with the sound (you may notice some very slight "hissing" or "swishing" sounds on high frequencies of certain songs), you may want to try the optional setting below.
[ OPTIONAL ]
Finding #3:
This is optional, and a matter of preference.
ADD the following value to the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings:
Name: SampleRate
Value (DWORD): 48000 (decimal)
This forces the A2DP stack to send the audio to the headset at 48000Hz instead of the default 44100Hz. For some reason, I find that the 48Khz value makes the "hissing" sounds less obvious. Your findings may vary, as some people may prefer the slightly more forward sound of the original setting. But if you are game, give this a try - one thing for sure is that it definitely changes the sound quality.
To reverse the change, just remove the SampleRate value.
If you make this 3rd optional change, you should have the following values in the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings:
UseJointStereo = 1
SampleRate = 48000
[ Note - Quick tip on registry editing ]
Of course, every registry change needs a soft-reset to take effect. And please take the usual proper care when editing the registry or risk damaging your device.
Find that your settings dont "stick" after a reset?
Make sure you reset the phone like this: After making changes to the registry, exit your registry editor. Then push the power button of your phone (putting it into standby, with the screen off). Wait for about 10 seconds (the phone will be saving the data to disk during this time), and only after that push the reset button.
Click to expand...
Click to collapse
I like to quote my sources, but I don't have the links at this moment. I will update them later.
Varied...
My experience across four or five builds has always been mixed. My older Motorolas work fine but my newer S9s dropout periodically. Interestingly, not all builds have the same result when I use them for handsfree. Some builds give me the voice I am speaking to in mono and some in stereo. Currently I am using Nitro's build from a month ago.
I have already exchanged the S9s once, so it wasn't specific to that one headset.
Exitao - Do you have dropouts periodically? What headset do you have?
kkrull said:
My experience across four or five builds has always been mixed. My older Motorolas work fine but my newer S9s dropout periodically. Interestingly, not all builds have the same result when I use them for handsfree. Some builds give me the voice I am speaking to in mono and some in stereo. Currently I am using Nitro's build from a month ago.
I have already exchanged the S9s once, so it wasn't specific to that one headset.
Exitao - Do you have dropouts periodically? What headset do you have?
Click to expand...
Click to collapse
Sorry, I was intending to post my personal details soon.
I am using a Sonorix C3
Standards Bluetooth Specification V2.0
RF Frequency Range 2402 ~ 2480 MHz
Profiles Supported A2DP, AVRCP, Headset, Handsfree V1.5
Transmission Power 0.25 ~ 2.5mW (Bluetooth Power Class 2)
Receiver Sensitivity < -80dBm (PER 1 %)
Distance 10m (in open space)
Click to expand...
Click to collapse
I am using EA's Chinese "WM6 5.2.318.18120" ROM:
http://bbs.koxo.cn/thread-14687-1-1.html
Currently my headset (well, the remote dongle, really) supports stereo playback, call display and bt handsfree usage.
Reception seems very clear. Mic pickup is sensitive and noise cancellation seems to be just as sensitive (I was holding the mic in my hand and gesturing madly one day, and realised what I was doing).
My only complain is the volume. I need to muck about in the audiogain settings to increase it.
As for what bt stack I'm using, I have no clue.
If I dump the zip file from this link, http://forum.xda-developers.com/showthread.php?t=263735&highlight=a2dp the bta2dp.dll was last modified on april, 2006. When I look in the windows directory of my phone, it only tells me I flashed it. I guess I have to dump the ROM to find out.
There is also the problem that the WiMP in my ROM can't handle VBR files. I'll be updating to vjgrace's 3.5 ROM shortly.
edit:
No dropouts. Mostly it is a fight to manage system resources on the phone.
any ppl know how yo make when the phone ringtone can ring in bluetooth.
mean we can listen the ring tone from bluetooth.
When I heard about USB audio in Android 5.x.x, I was really excited, I could finally use my G930 headset with my phone! ...then I tried it and I found out that the volume is ridiculously low. So I thought it was the headset and naturally I decided to try a different one, but as it turns out, the other one was just as quiet. Am I missing something here?
Even trying other players doesn't seem to work, with the exception being USB Audio Player, which I was able to play with the pre-amp and boost the volume to the proper levels, but the equalizer on it is horrible.
Any thoughts on this? Is USB audio even a thing in Android or it's just "there"?
CrisR82 said:
When I heard about USB audio in Android 5.x.x, I was really excited, I could finally use my G930 headset with my phone! ...then I tried it and I found out that the volume is ridiculously low. So I thought it was the headset and naturally I decided to try a different one, but as it turns out, the other one was just as quiet. Am I missing something here?
Even trying other players doesn't seem to work, with the exception being USB Audio Player, which I was able to play with the pre-amp and boost the volume to the proper levels, but the equalizer on it is horrible.
Any thoughts on this? Is USB audio even a thing in Android or it's just "there"?
Click to expand...
Click to collapse
The issue could be a million things since it's new. and since headsets aren't guaranteed support outside of a PC trial and error is your best friend.
Try different ROMs, stock ROM's, stock based, etc. you get the point.
CrisR82 said:
When I heard about USB audio in Android 5.x.x, I was really excited, I could finally use my G930 headset with my phone! ...then I tried it and I found out that the volume is ridiculously low. So I thought it was the headset and naturally I decided to try a different one, but as it turns out, the other one was just as quiet. Am I missing something here?
Even trying other players doesn't seem to work, with the exception being USB Audio Player, which I was able to play with the pre-amp and boost the volume to the proper levels, but the equalizer on it is horrible.
Any thoughts on this? Is USB audio even a thing in Android or it's just "there"?
Click to expand...
Click to collapse
Sounds like the USB mixer is set to a low volume by default.
Are you rooted? If so, you can download a binary called "tinymix" from here to view and modify the mixer.
(tinymix is part of AOSP, but does not ship with Google's Android. It may with custom ROMs.)
Copy the binary to, e.g. /system/xbin, make it executable (744), and run the following command as root in an adb shell, after you connected your USB audio device:
Code:
tinymix -D 1
For example, I have an external DAC (FiiO E18, which works fine on my N5 running stock Android 5.1) and the output is
Code:
Mixer name: 'FiiO USB DAC-E18'
Number of controls: 2
ctl type num name value
0 BOOL 1 PCM Playback Switch On
1 INT 2 PCM Playback Volume 110 110
Knowing this output you can run
Code:
tinymix -D 1 "PCM Playback Volume"
which in my case returns
Code:
PCM Playback Volume: 110 110 (range 0->110)
This means that the playback volume on my device, which can range from 0 to 110, is set to max.
What does tinymix return on your device?
chdloc said:
Sounds like the USB mixer is set to a low volume by default.
Are you rooted? If so, you can download a binary called "tinymix" from here to view and modify the mixer.
(tinymix is part of AOSP, but does not ship with Google's Android. It may with custom ROMs.)
Copy the binary to, e.g. /system/xbin, make it executable (744), and run the following command as root in an adb shell, after you connected your USB audio device:
Code:
tinymix -D 1
For example, I have an external DAC (FiiO E18, which works fine on my N5 running stock Android 5.1) and the output is
Code:
Mixer name: 'FiiO USB DAC-E18'
Number of controls: 2
ctl type num name value
0 BOOL 1 PCM Playback Switch On
1 INT 2 PCM Playback Volume 110 110
Knowing this output you can run
Code:
tinymix -D 1 "PCM Playback Volume"
which in my case returns
Code:
PCM Playback Volume: 110 110 (range 0->110)
This means that the playback volume on my device, which can range from 0 to 110, is set to max.
What does tinymix return on your device?
Click to expand...
Click to collapse
Does that affect USB volume only, or it will affect global audio output?
CrisR82 said:
Does that affect USB volume only, or it will affect global audio output?
Click to expand...
Click to collapse
USB volume only.
Note that modifying the USB audio playback gain via the mixer may not be permanent. You may have to re-adjust the playback gain every time after you have plugged in your USB audio device. If this is the case, an automation app like Tasker can be very useful.
The USB Audio Player seems to have this built-in and works pretty well...wish it's equalizer wasn't lacking even basic presets...
Will give it a go I guess
So I finally got fed up enough to purchase a USB-C DAC dongle to overcome the unbearable hissing noise of the inbuilt 3.5mm audio jack. The first obvious choice would be a Pixel dongle, but for some reason Apple is selling a better performing dongle. Being cheaper and available in a mortar store, it was a no brainer purchase. I can definitely say that hissing is gone and sound is crystal clear. However for yet another reason, Apple dongle is by default quite limited in power, being usable mainly by sensitive IEMs. After several attempts of various methods, I found a reliable way of removing this limit.
Ingredients needed:
1. Apple DAC dongle
2. Tasker
3. Magisk
4. AlsaMixer app (https://apkpure.com/alsamixer-root/com.skvalex.alsamixer)
Recipe:
1. Extract AlsaMixer app and locate "assets\alsa\system" folder
2. Create a Magisk module from this folder with 755/755 rights
3. Install Magisk module
4. Create a Tasker event "headphones connected", task "shell script", run as root, command "alsa_amixer -c 1 sset Headphone 120"
5. Connect Apple dongle
Voila, you suddenly moved from -40dB limit to 0db for max volume. Limit is automatically reset on each DAC re-connection, so Tasker intent is mandatory.
Verification:
1. In terminal write as root "alsa_amixer -c 1" to see the current playback limit. It obviously works only with DAC connected.
Note: this method works only for USB-C DACs, not for analog audio jack of Mi A1 phone.
Default:
Code:
# [B]alsa_amixer -c 1[/B]
Simple mixer control 'Headphone',0
Capabilities: pvolume pswitch pswitch-joined penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 120
Mono:
Front Left:[B] Playback 80 [67%] [-40.00dB][/B] [on]
Front Right:[B] Playback 80 [67%] [-40.00dB][/B] [on]
Headphones with no mic:
Code:
# [B]alsa_amixer -c 1 sset Headphone 120[/B]
Simple mixer control 'Headphone',0
Capabilities: pvolume pswitch pswitch-joined penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 120
Mono:
Front Left: [B]Playback 120 [100%] [0.00dB][/B] [on]
Front Right: [B]Playback 120 [100%] [0.00dB][/B] [on]
Headset with a mic:
Code:
# [B]alsa_amixer -c 1 sset Headset,1 120[/B]
Simple mixer control 'Headset',1
Capabilities: pvolume pswitch pswitch-joined penum
Playback channels: Front Left - Front Right
Limits: Playback 0 - 120
Mono:
Front Left: [B]Playback 120 [100%] [0.00dB][/B] [on]
Front Right: [B]Playback 120 [100%] [0.00dB][/B] [on]
--first post updated--
Why don't you use tinymix, that is included on any Android release, instead of alsa_mixer so that you don't need to install other stuff?
drizzt said:
Why don't you use tinymix, that is included on any Android release, instead of alsa_mixer so that you don't need to install other stuff?
Click to expand...
Click to collapse
Wasn't aware of this fact, thanks. Will check tinymix, but alsa seems to be much easier to use for this purpose (at least for me ).
Edit:tinymix is just too complex to use and control commands probably aren't 100% universal with all DACs, so I'll stay with ALSA and Tasker. If I wanted to utilize tinymix, I'd just use this app (Apple dongle requires special version) https://forum.xda-developers.com/pixel-2-xl/themes/pixel-2-usb-audio-control-t3704024
Hissing sound? Bro have you checked the internals of your phone? I did and I had a snake inside, after getting him out everything was fine
Yes, I have a very inteligent snake in there, which hisses only when I connect headphones and only during music playback + about 3 seconds once it stops. Also the snake is able to distinguish between sensitive low impedance IEMs and less sensitive bigger headphones, so it adjusts volume of its hissing accordingly. What's even more interesting, he keeps quiet when I connect an external DAC. I want to keep the snake, so I won't remove it from the phone.
Well, it's that or there's ****ty audio output circuit in the phone.
Fixes the PH-1 !
I came across your thread while looking for a fix for the Apple dongle when used with the Essential PH-1. The problem is when using a TRS headset with this specific dongle+phone combo the left and right channels are at significantly different volumes. A TRRS headset does not exhibit this issue.
TRRS reports Headset,1
TRS reports PCM,0
I renamed xbin to bin. Not sure if that is the right solution, but the tools were not showing up before. A quick Tasker task and it's all set!
Thank you so much!!
numanair said:
I came across your thread while looking for a fix for the Apple dongle when used with the Essential PH-1. The problem is when using a TRS headset with this specific dongle+phone combo the left and right channels are at significantly different volumes. A TRRS headset does not exhibit this issue.
TRRS reports Headset,1
TRS reports PCM,0
I renamed xbin to bin. Not sure if that is the right solution, but the tools were not showing up before. A quick Tasker task and it's all set!
Thank you so much!!
Click to expand...
Click to collapse
Thanks for letting us know and I'm glad this guide helped you. Different phones can have different bin folder and also parameters for alsa-mixer, so you did the right thing.
Works on Oneplus 7 pro (Android 10). Just had to change "Headphone" to "Headset" in the alsa_amixer command.
Been trying to get a magisk module made for this on my Razer Phone 2 and it took me quite a while since I kept getting errors. I got fed up and decided to try Samsung's dongle since that surely would've been optimized for Androids, but it seems that it also had the same exact issue (go figure, Samsung practically copied Apple 100%). The Samsung dongle is the same quality as Apple's dongle for sound quality (albeit a tiny bit worse, practically unnoticeable) and also, the same volume output from the same set of earbuds at max. So back to figuring out the whole magisk module thing.
Anyways I got the issue resolved. I remade the module I had on my pc rather than doing it on the phone itself and the error magically went away, and the whole thing is working wonderfully now. Even works for the Samsung USB-C 3.5mm dongle, with a different value. 108 for the Samsung dongle rather than Apple's 120.
Thank you for posting the guide, super helpful to fix this issue for the Apple and Samsung dongles on Android in general.
Thanks for this thread. Could I use this stuff to fix my AirPods Pro with my OnePlus 7 Pro? I have to set the volume to max to hear something in the bus ;-;
cedricberger27 said:
Thanks for this thread. Could I use this stuff to fix my AirPods Pro with my OnePlus 7 Pro? I have to set the volume to max to hear something in the bus ;-;
Click to expand...
Click to collapse
I'm afraid that it's not possible to control external amplifier connected over bluetooth (or at least I don't know about any way how to do it). USB-C dongle can be configured because Android sees it connected "internally" as a sound card. AirPods and similar have DAC ("sound card") in the earphones and phone can use only standard Bluetooth commands to send music and perform basic control. AFAIK, changing the gain parameters isn't among them.
kenvenin said:
Works on Oneplus 7 pro (Android 10). Just had to change "Headphone" to "Headset" in the alsa_amixer command.
Click to expand...
Click to collapse
brother, i tried to make the module for my OnePlus 6 but can't get it to work. it will be great help if you please share your magisk module. thanks in advanced
Can someone upload this module here? Or maybe give some tutorial how to make a magisk module? I was searching for this, but I didn't find it.
Adamz274 said:
Can someone upload this module here? Or maybe give some tutorial how to make a magisk module? I was searching for this, but I didn't find it.
Click to expand...
Click to collapse
Not sure if it's still working (I created and installed this module while on Magisk v19 and modules format changed since then), you might need to update "META-INF\com\google\android\update-binary" script with the latest version from here https://topjohnwu.github.io/Magisk/guides.html (and maybe remove "install.sh")
EU/USA Model
_mysiak_ said:
Not sure if it's still working (I created and installed this module while on Magisk v19 and modules format changed since then), you might need to update "META-INF\com\google\android\update-binary" script with the latest version from here https://topjohnwu.github.io/Magisk/guides.html (and maybe remove "install.sh")
Click to expand...
Click to collapse
Maybe I misunderstood but from everything I have read, the EU version of the Apple Adapter is worse, much quieter. I thought that was in the hardware, the US version is full power.
'There are 2 versions of it, US version A2049 which could output 1v, and EU version A2155 which limited to 0.5v' from another source
https://www.reddit.com/r/headphones/comments/ecf1ud/apple_usbc_to_35mm_adapter_impressions/
Is this 'fix' able to achieve the full 1v power output on the EU Model ?
poster74 said:
Maybe I misunderstood but from everything I have read, the EU version of the Apple Adapter is worse, much quieter. I thought that was in the hardware, the US version is full power.
'There are 2 versions of it, US version A2049 which could output 1v, and EU version A2155 which limited to 0.5v' from another source
https://www.reddit.com/r/headphones/comments/ecf1ud/apple_usbc_to_35mm_adapter_impressions/
Is this 'fix' able to achieve the full 1v power output on the EU Model ?
Click to expand...
Click to collapse
As far as I know it's SW limitation, affecting mostly Android phones (not sure about Apple devices, I don't own any). My phone and dongle come from the official EU distribution, so I assume that it's the EU version. The fix definitely removes the power limit. I do not have an US dongle (or measurement device), so can't compare them though. All I can say for sure it's that with sensitive IEMs the dongle is dead silent, there is no hissing noise. At the same time, and after removing the power limit, the dongle can drive AKG K240MK2 (55ohms) cans without problems. It struggles a bit with Beyerdynamic DT990pro (250ohm) - depending on the sound source, volume can (Google music) or won't be enough (most Youtube videos).
Hi,
I appreciate you dont have meter to measure output but are you saying that this fix seems to increase the volume limit significantly ? The US version is supposed 1v against EU 0.5V.
Does this fix, 'feel' that much louder ?
_mysiak_ said:
As far as I know it's SW limitation, affecting mostly Android phones (not sure about Apple devices, I don't own any). My phone and dongle come from the official EU distribution, so I assume that it's the EU version. The fix definitely removes the power limit. I do not have an US dongle (or measurement device), so can't compare them though. All I can say for sure it's that with sensitive IEMs the dongle is dead silent, there is no hissing noise. At the same time, and after removing the power limit, the dongle can drive AKG K240MK2 (55ohms) cans without problems. It struggles a bit with Beyerdynamic DT990pro (250ohm) - depending on the sound source, volume can (Google music) or won't be enough (most Youtube videos).
Click to expand...
Click to collapse
techcolab said:
Hi,
I appreciate you dont have meter to measure output but are you saying that this fix seems to increase the volume limit significantly ? The US version is supposed 1v against EU 0.5V.
Does this fix, 'feel' that much louder ?
Click to expand...
Click to collapse
Yes, it sounds significantly louder. Dongle is pretty cheap, they might even let you try it in the mortar store, so just get ready your phone and try it with your headphones. In the "worst" case you can use it with a PC (Windows 10), there it works at full power with no "hacking" needed.
I am a novice. But I need a module and good explanation on how to DIY. Can u help me PLEASE?
I am on android 10 samsung tab s7 plus rooted. Alsa installation showing error too. Will be very helpful if u make a video of it.
I have a new ANDROID TV 10 philips oled, and i would like to change the audio output with ADB (without use a graphical menu)
with this command:
adb shell settings put global hdmi_system_audio_control_enabled 1
i can powe on my surround home theater via HDMI CEC but the audio is not redirected, i think that there is some other command for this.
can you help me?