The online Samsung community acts as a platform where the users can address their grievances or maybe get a quick fix solution to their devices that are not providing the service they had offered or have stopped working. A plethora of users came out and wrote about their faulty devices, hoping they would hear back from the Samsung developers.
A user has complained about the forum that his Galaxy S10e, which runs on Android 10 and the Boya BY-DM2 USB Type-C microphone, is facing some issues. The external microphone of the smartphone worked without any issues after the smartphone was updated to Android Pie. However, as soon as the Android 10 update was downloaded and the user decided to switch to the Android 10 version, his device started having technical issues.
Connecting the Boya BY-DM2 microphone to the updated Samsung Galaxy S10e smartphone forces the smartphone to turn off on its own, but not permanently.
He addresses another issue with the quality of the sound of the microphone. There had been a static background noise playing in the background of the speaker. The user thinks that this is likely a software issue.
Elegant Themes - The most popular WordPress theme in the world and the ultimate WordPress Page Builder. Get a 30-day money-back guarantee. Get it for Free
However, this is not an isolated incident as several other users have complained of facing the same issues with their devices. Another user commented that he has been having the same problem with the Galaxy S10+ device. The voice recorded using this smartphone is distorted and the sound is coming out with static noise sometimes. A few of the Galaxy S10 users are also facing the same problems with the microphones.
A Samsung GoMic works well with Galaxy S8+, and the same microphone should work just fine with the S10, but that is not the case here. Another user of the Samsung S20 Ultra has complained of the same thing.
It should be duly noted that the first complaint sprung up in January, and it has been five months since; but the developers at Samsung have failed to address this issue, let alone solve it.