X
Tap here to go to the mobile version of the site.

Support Forum

Why do I have to restart the firefox to detect my earphone?

Posted

First thing! Firefox is the best and my favorite.

I have one concern that, I have to restart it all the time to get the audio in my earphone. It plays the audios nicely. But if it is playing something and then I plugged in a earphone 3.5 mm jack, then it won't switch to that. Only workaround is to restart the Firefox.

First thing! Firefox is the best and my favorite. I have one concern that, I have to restart it all the time to get the audio in my earphone. It plays the audios nicely. But if it is playing something and then I plugged in a earphone 3.5 mm jack, then it won't switch to that. Only workaround is to restart the Firefox.

Additional System Details

Application

  • Firefox 61.0.2
  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
  • Support URL: https://support.mozilla.org/1/firefox/61.0.2/WINNT/en-US/

Extensions

  • Forget Me Not - Forget cookies & other data 1.0.5 (forget-me-not@lusito.info)
  • Privacy Badger 2018.8.22 (jid1-MnnxcxisBPnSXQ@jetpack)
  • IDM Integration Module 6.31.2 (mozilla_cc3@internetdownloadmanager.com) (Inactive)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription:
  • adapterDescription2:
  • adapterDeviceID:
  • adapterDeviceID2:
  • adapterDrivers: Unknown
  • adapterDrivers2:
  • adapterRAM: Unknown
  • adapterRAM2:
  • adapterSubsysID:
  • adapterSubsysID2:
  • adapterVendorID:
  • adapterVendorID2:
  • contentUsesTiling: False
  • crashGuards: []
  • direct2DEnabled: False
  • direct2DEnabledMessage: [u'blockedGfxCard']
  • directWriteEnabled: True
  • directWriteVersion: 10.0.18219.1000
  • driverDate:
  • driverDate2:
  • driverVersion:
  • driverVersion2:
  • featureLog: {u'fallbacks': [], u'features': [{u'status': u'available', u'description': u'Compositing', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'HW_COMPOSITING'}, {u'status': u'blacklisted', u'description': u'Direct3D11 Compositing', u'log': [{u'status': u'available', u'type': u'default'}, {u'status': u'blacklisted', u'message': u'#BLOCKLIST_FEATURE_FAILURE_UNKNOWN_DEVICE_VENDOR', u'type': u'env'}], u'name': u'D3D11_COMPOSITING'}, {u'status': u'unavailable', u'description': u'Direct2D', u'log': [{u'status': u'unavailable', u'message': u'Direct2D requires Direct3D 11 compositing', u'type': u'default'}], u'name': u'DIRECT2D'}, {u'status': u'disabled', u'description': u'Direct3D11 hardware ANGLE', u'log': [{u'status': u'unavailable', u'message': u'D3D11 compositing is disabled', u'type': u'default'}, {u'status': u'disabled', u'message': u'D3D11 compositing is disabled', u'type': u'env'}], u'name': u'D3D11_HW_ANGLE'}, {u'status': u'blacklisted', u'description': u'GPU Process', u'log': [{u'status': u'available', u'type': u'default'}, {u'status': u'blacklisted', u'message': u'#BLOCKLIST_FEATURE_FAILURE_UNKNOWN_DEVICE_VENDOR', u'type': u'env'}], u'name': u'GPU_PROCESS'}, {u'status': u'unavailable', u'description': u'WebRender', u'log': [{u'status': u'opt-in', u'message': u'WebRender is an opt-in feature', u'type': u'default'}, {u'status': u'unavailable', u'message': u'ANGLE is disabled', u'type': u'runtime'}], u'name': u'WEBRENDER'}, {u'status': u'available', u'description': u'Off Main Thread Painting', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'OMTP'}]}
  • info: {u'ApzWheelInput': 1, u'ApzDragInput': 1, u'ApzKeyboardInput': 1, u'ApzTouchInput': 1, u'ApzAutoscrollInput': 1, u'AzureFallbackCanvasBackend': u'cairo', u'AzureCanvasAccelerated': 0, u'AzureCanvasBackend': u'skia', u'AzureContentBackend': u'skia'}
  • isGPU2Active: False
  • numAcceleratedWindows: 0
  • numAcceleratedWindowsMessage: [u'blockedGfxCard']
  • numTotalWindows: 3
  • offMainThreadPaintEnabled: True
  • offMainThreadPaintWorkerCount: 3
  • usesTiling: False
  • webgl1DriverExtensions: GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object
  • webgl1Extensions: ANGLE_instanced_arrays EXT_blend_minmax EXT_color_buffer_half_float EXT_frag_depth EXT_sRGB EXT_shader_texture_lod EXT_texture_filter_anisotropic EXT_disjoint_timer_query OES_element_index_uint OES_standard_derivatives OES_texture_float OES_texture_float_linear OES_texture_half_float OES_texture_half_float_linear OES_vertex_array_object WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_depth_texture WEBGL_draw_buffers WEBGL_lose_context
  • webgl1Renderer: Google Inc. -- ANGLE (Microsoft Basic Render Driver Direct3D11 vs_5_0 ps_5_0)
  • webgl1Version: OpenGL ES 2.0 (ANGLE 2.1.0.fcbca0e873c3)
  • webgl1WSIInfo: EGL_VENDOR: Google Inc. (adapter LUID: 0000000000005830) EGL_VERSION: 1.4 (ANGLE 2.1.0.fcbca0e873c3) EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_CHROMIUM_sync_control EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses
  • webgl2DriverExtensions: -
  • webgl2Extensions: -
  • webgl2Renderer: WebGL creation failed: * Refused to create WebGL2 context because of blacklist entry: FEATURE_FAILURE_UNKNOWN_DEVICE_VENDOR
  • webgl2Version: -
  • webgl2WSIInfo: -
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Basic
  • windowUsingAdvancedLayers: False

Modified Preferences

Misc

  • User JS: No
  • Accessibility: Yes
WestEnd
  • Top 25 Contributor
60 solutions 5376 answers

That would be your sound driver issue not a FF Browser issue. I don't have trouble with mine when I do that it takes a micro second to switch over and if your takes longer then you got either software driver or hardware issues causing it.

That would be your sound driver issue not a FF Browser issue. I don't have trouble with mine when I do that it takes a micro second to switch over and if your takes longer then you got either software driver or hardware issues causing it.
cor-el
  • Top 10 Contributor
  • Moderator
17421 solutions 157412 answers

That is how it always has worked in Firefox. Firefox only detects the currently used output device when Firefox starts and doesn't detect changes made during the session.

That is how it always has worked in Firefox. Firefox only detects the currently used output device when Firefox starts and doesn't detect changes made during the session.

Question owner

WestEnd said

That would be your sound driver issue not a FF Browser issue. I don't have trouble with mine when I do that it takes a micro second to switch over and if your takes longer then you got either software driver or hardware issues causing it.

Well, it sometime detects my USB headset, but not the 3.5 jack. And My driver is healthy.

''WestEnd [[#answer-1149813|said]]'' <blockquote> That would be your sound driver issue not a FF Browser issue. I don't have trouble with mine when I do that it takes a micro second to switch over and if your takes longer then you got either software driver or hardware issues causing it. </blockquote> Well, it sometime detects my USB headset, but not the 3.5 jack. And My driver is healthy.

Question owner

cor-el said

That is how it always has worked in Firefox. Firefox only detects the currently used output device when Firefox starts and doesn't detect changes made during the session.

Thank you! I noticed the same. But other browsers say chrome and Edge, they are picking me up in between the sessions. Moreover, fyi I am using a VM.

''cor-el [[#answer-1150027|said]]'' <blockquote> That is how it always has worked in Firefox. Firefox only detects the currently used output device when Firefox starts and doesn't detect changes made during the session. </blockquote> Thank you! I noticed the same. But other browsers say chrome and Edge, they are picking me up in between the sessions. Moreover, fyi I am using a VM.
the-edmeister
  • Top 25 Contributor
  • Moderator
5395 solutions 40084 answers

Helpful Reply

Harty said

Well, it sometime detects my USB headset, but not the 3.5 jack. And My driver is healthy.

USB "devices" connect into the operating system thru the USB controller chip, which handles connecting an additional device more smoothly than the motherboard plugs, such as the keyboard, mouse, and parallel printers. The USB controller is programmed in the operating system to select a "known device" (the API used & code knowledge for each device) and automatically use the correct driver. Although the first time a new device is used on that operating system Windows will ask confirmation about the new device before selecting (and saving) that device so that it will connect seamlessly after the first use.

In my experiences, I can't remember the last time Firefox didn't recognize a USB device that was plugged in while Firefox was running, and be able to use automatically the USB device without "jumping thru hoops". But I have always needed to restart Firefox after plugging in a headphone or mic into a 3.5 jack; electronically I don't understand the "why" Firefox works this way.

My guess it is due to Firefox being written for cross-browser compatibility where most parts of Firefox are the same whether the OS is Windows, Mac, or Linux. Extra code is added for each different type of OS and for each major version of those different types of OS's.

''Harty [[#answer-1150732|said]]'' <blockquote> Well, it sometime detects my USB headset, but not the 3.5 jack. And My driver is healthy. </blockquote> USB "devices" connect into the operating system thru the USB controller chip, which handles connecting an additional device more smoothly than the motherboard plugs, such as the keyboard, mouse, and parallel printers. The USB controller is programmed in the operating system to select a "known device" (the API used & code knowledge for each device) and automatically use the correct driver. Although the first time a new device is used on that operating system Windows will ask confirmation about the new device before selecting (and saving) that device so that it will connect seamlessly after the first use. In my experiences, I can't remember the last time Firefox didn't recognize a USB device that was plugged in while Firefox was running, and be able to use automatically the USB device without "jumping thru hoops". But I have always needed to restart Firefox after plugging in a headphone or mic into a 3.5 jack; electronically I don't understand the "why" Firefox works this way. My guess it is due to Firefox being written for cross-browser compatibility where most parts of Firefox are the same whether the OS is Windows, Mac, or Linux. Extra code is added for each different type of OS and for each major version of those different types of OS's.

Question owner

the-edmeister said

Harty said
Well, it sometime detects my USB headset, but not the 3.5 jack. And My driver is healthy.

USB "devices" connect into the operating system thru the USB controller chip, which handles connecting an additional device more smoothly than the motherboard plugs, such as the keyboard, mouse, and parallel printers. The USB controller is programmed in the operating system to select a "known device" (the API used & code knowledge for each device) and automatically use the correct driver. Although the first time a new device is used on that operating system Windows will ask confirmation about the new device before selecting (and saving) that device so that it will connect seamlessly after the first use.

In my experiences, I can't remember the last time Firefox didn't recognize a USB device that was plugged in while Firefox was running, and be able to use automatically the USB device without "jumping thru hoops". But I have always needed to restart Firefox after plugging in a headphone or mic into a 3.5 jack; electronically I don't understand the "why" Firefox works this way.

My guess it is due to Firefox being written for cross-browser compatibility where most parts of Firefox are the same whether the OS is Windows, Mac, or Linux. Extra code is added for each different type of OS and for each major version of those different types of OS's.

Cool. I totally agree about the cross-platform thing as you described. On my point of view, chrome is also cross-platformed, right? and it works. But I don't use chrome as much as I use Firefox and sadly I am restarting my Firefox for USB head-set too.

''the-edmeister [[#answer-1150740|said]]'' <blockquote> ''Harty [[#answer-1150732|said]]'' <blockquote> Well, it sometime detects my USB headset, but not the 3.5 jack. And My driver is healthy. </blockquote> USB "devices" connect into the operating system thru the USB controller chip, which handles connecting an additional device more smoothly than the motherboard plugs, such as the keyboard, mouse, and parallel printers. The USB controller is programmed in the operating system to select a "known device" (the API used & code knowledge for each device) and automatically use the correct driver. Although the first time a new device is used on that operating system Windows will ask confirmation about the new device before selecting (and saving) that device so that it will connect seamlessly after the first use. In my experiences, I can't remember the last time Firefox didn't recognize a USB device that was plugged in while Firefox was running, and be able to use automatically the USB device without "jumping thru hoops". But I have always needed to restart Firefox after plugging in a headphone or mic into a 3.5 jack; electronically I don't understand the "why" Firefox works this way. My guess it is due to Firefox being written for cross-browser compatibility where most parts of Firefox are the same whether the OS is Windows, Mac, or Linux. Extra code is added for each different type of OS and for each major version of those different types of OS's. </blockquote> Cool. I totally agree about the cross-platform thing as you described. On my point of view, chrome is also cross-platformed, right? and it works. But I don't use chrome as much as I use Firefox and sadly I am restarting my Firefox for USB head-set too.
the-edmeister
  • Top 25 Contributor
  • Moderator
5395 solutions 40084 answers

Harty said

Cool. I totally agree about the cross-platform thing as you described. On my point of view, chrome is also cross-platformed, right? and it works. But I don't use chrome as much as I use Firefox and sadly I am restarting my Firefox for USB head-set too.

I am not an expert by any stretch of the imagination, but Chrome / WebKit was created in a different era (2007) than Netscape / Gecko (1995?) and Internet Explorer (1996 or '97?). IMO part of the limitations that affected the older era of web browsers had to do with the DOS underpinnings of Windows 95, 98, and ME, which Google didn't face with WinXP and later being on NT. Plus there's a 16-bit vs 32-bit "thing" that could have affected the older era difference or limitations in cross-browser programming. Plus MS IE supported MacOSX until it didn't after Safari WebKit came about; iirc, that was about the time that Mac began with 64-bit versions of MacOSX. One of the things that led me to think of the 16 vs 32-bit situation.

Google Chrome never had to support the DOS based versions of Windows, it was WinXP (NT-based) and later. Or possibly it could be due to the web browser market being much larger in 2007 and Google was huge by then and had the money to hire away programmers from all over to achieve their goals; work out the "kinks" or just author code for each of the major 3 OS types involved.

By 2005 Mozilla with Firefox was able to chip away an IE dominance of the web browser market in the early 00's, Google then stepped in hiring away the best Mozilla "minds" to help "put the nail in IE's coffin"; subsequently Google managed to just about kill Firefox by 2011. IMO, Mozilla was too slow to move away from its roots in Netscape/Gecko; IOW, too slow moving towards what is now called Quantum; which is going over like a lead balloon in many long term Firefox users's minds.

Then there's the probability that Chrome has access with Alphabet "cash" to almost write platform specific code to meet their goals for what amounts to an "advertising delivery vehicle" for the internet. Overall there's could be a lot of anti-trust issues coming down the pike for Google / Alphabet. The USA didn't touch (or couldn't) touch Microsoft in the mid-00's, but the EU did at least least get a 5 year ( ? ) consent order to equalize the web browser playing field in the "teens"; and EU has something going on with Google as far as potential litigation over their practices.

Hey, just ramblings from a 68 yo man who is far from an expert in anything, and just a spectator / observer. I love Firefox and I am clinging to the Firefox of the past. Quantum "excites" me as much as going to the dentist does.

''Harty [[#answer-1153582|said]]'' <blockquote> Cool. I totally agree about the cross-platform thing as you described. On my point of view, chrome is also cross-platformed, right? and it works. But I don't use chrome as much as I use Firefox and sadly I am restarting my Firefox for USB head-set too. </blockquote> I am not an expert by any stretch of the imagination, but Chrome / WebKit was created in a different era (2007) than Netscape / Gecko (1995?) and Internet Explorer (1996 or '97?). IMO part of the limitations that affected the older era of web browsers had to do with the DOS underpinnings of Windows 95, 98, and ME, which Google didn't face with WinXP and later being on NT. Plus there's a 16-bit vs 32-bit "thing" that could have affected the older era difference or limitations in cross-browser programming. ''Plus MS IE supported MacOSX until it didn't after Safari WebKit came about; iirc, that was about the time that Mac began with 64-bit versions of MacOSX. One of the things that led me to think of the 16 vs 32-bit situation.'' Google Chrome never had to support the DOS based versions of Windows, it was WinXP (NT-based) and later. Or possibly it could be due to the web browser market being much larger in 2007 and Google was huge by then and had the money to hire away programmers from all over to achieve their goals; work out the "kinks" or just author code for each of the major 3 OS types involved. By 2005 Mozilla with Firefox was able to chip away an IE dominance of the web browser market in the early 00's, Google then stepped in hiring away the best Mozilla "minds" to help "put the nail in IE's coffin"; subsequently Google managed to just about kill Firefox by 2011. IMO, Mozilla was too slow to move away from its roots in Netscape/Gecko; IOW, too slow moving towards what is now called Quantum; which is going over like a lead balloon in many long term Firefox users's minds. Then there's the probability that Chrome has access with Alphabet "cash" to almost write platform specific code to meet their goals for what amounts to an "advertising delivery vehicle" for the internet. Overall there's could be a lot of anti-trust issues coming down the pike for Google / Alphabet. The USA didn't touch (or couldn't) touch Microsoft in the mid-00's, but the EU did at least least get a 5 year ( ? ) consent order to equalize the web browser playing field in the "teens"; and EU has something going on with Google as far as potential litigation over their practices. ''Hey, just ramblings from a 68 yo man who is far from an expert in anything, and just a spectator / observer. I love Firefox and I am clinging to the Firefox of the past. Quantum "excites" me as much as going to the dentist does.''