Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility with Alternative A2DP Driver #1578

Open
CloudyEagle opened this issue Jul 12, 2024 · 4 comments
Open

Compatibility with Alternative A2DP Driver #1578

CloudyEagle opened this issue Jul 12, 2024 · 4 comments

Comments

@CloudyEagle
Copy link

Summary

When I use Alternative A2DP Driver to connect wireless headphone by Bluetooth, some APPs volume cannot display, the item of System Sounds is often doing on. Some other items also not display. When I restart this EarTrumpet, all items back and EarTrumpet working correctly.

Steps to reproduce

  1. Use Alternative A2DP Driver to connect wireless headphone by Bluetooth
  2. Click icon of EarTrumpet in taskbar

EarTrumpet version

2.3.0.0

Windows version

10.0.19045.4170

Additional information

image
error image, Normally It will have the item of System Sounds, like blow image.
image

@CloudyEagle CloudyEagle changed the title some items of APPs disappear some items of APPs disappearing Jul 12, 2024
@CloudyEagle
Copy link
Author

CloudyEagle commented Sep 27, 2024

When I use another wireless Bluetooth earphone, then used Alternative A2DP Driver to change connection driver. This bug still appears.
image

But when APP exited and restarted, this bug disappeared.
image
image

I think this is the compatibility with that driver. I want to connect the Bluetooth earphone by Alternative A2DP Driver, but do not need restart EarTrumpet manually for fixing that question.

@CloudyEagle CloudyEagle changed the title some items of APPs disappearing List of APPs disappearing Sep 27, 2024
@CloudyEagle CloudyEagle changed the title List of APPs disappearing Compatibility with Alternative A2DP Driver Nov 5, 2024
@riverar
Copy link
Contributor

riverar commented Nov 12, 2024

This is likely our fault #1305. Restarting EarTrumpet likely resolves the issue until you switch again, right?

@CloudyEagle
Copy link
Author

Yes. after connecting wireless earphones by Bluetooth, I find out sometime this problem happened. It's not all the third-part driver causing this.

@riverar
Copy link
Contributor

riverar commented Nov 13, 2024

Thanks for the quick reply, will work on this via #1305.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants