Status Update
Comments
vs...@google.com <vs...@google.com>
rk...@google.com <rk...@google.com>
wd...@google.com <wd...@google.com>
ru...@gmail.com <ru...@gmail.com> #2
If that's not the case and I change the microphone source, it would affect the sound quality as well.
Edit: Probably on the Mac program `Audio MIDI Setup` the sound source format is changed to a lower bitrate
ru...@gmail.com <ru...@gmail.com> #3
I've tried the Audio MIDI Setup program, but it doesn't show any changes for my headphones that are bluetooth connected with a USB dongle.
ru...@gmail.com <ru...@gmail.com> #4
Hi, as the emulator continuously uses the microphone, Bluetooth headset quality will be degraded due to there being not enough bluetooth bandwidth to have both hi quality output and input. We can consider having a dynamic switch for this, but adding this will take some time.
ru...@gmail.com <ru...@gmail.com> #5
I don't think that is what is happening. For me, when the emulator launches, it changes the macOS input device from the internal speaker to my headphones which switches the bt profile to a2dp.
As a temporary workaround, I set hw.audioInput=no
in my avd config.ini and it seemed to help.
ru...@gmail.com <ru...@gmail.com> #6
+1 with "not enough bluetooth bandwidth" not being the issue. Connecting the headphones after the emulator has started up has no issues.
al...@gmail.com <al...@gmail.com> #7
kc...@gmail.com <kc...@gmail.com> #8
wd...@google.com <wd...@google.com> #9
ru...@gmail.com <ru...@gmail.com> #10
wd...@google.com <wd...@google.com> #11
Which is almost a year old, guys!
bo...@google.com <bo...@google.com> #12
As a temporary workaround,
bo...@google.com <bo...@google.com> #13
config.ini do the fix, thanks!
source: #5 comment
- Device manager -> virtual device dropdown menu -> Show on Disk
- open config.ini and add this line: hw.audioInput=no
de...@google.com <de...@google.com> #14
config.ini changes don't seem to work for me - tried on various emulators with API level 31+. Both freshly installed emulators and existing ones.
Description
DESCRIBE THE ISSUE IN DETAIL: The
-http-proxy
command line parameter is not parsed correctly no matter what format I use - it uses an empty string as a hostname/ip and fails to connect. The port is parsed correctly. Formats I tried:STEPS TO REPRODUCE:
emulator.exe -avd Pixel_3a_API_34_extension_level_7_x86_64 -http-proxy 127.0.0.1:8888 -verbose -debug-proxy
Note: I tried to create the issue in "Android Studio > Emulator" component but got "You do not have permission to create issues in this component."