Robot voice on adb after 2.2.4 release and dead tcp connections

[AlehAbakshonak]

Devices: Windows 10 pc / Android v16 phone

Since 2.2.4 there are few inconveniences appeared:

1. The quality of the audio is lowered significantly, there is a lot of static noise and some echo. Both when im listening to the audio input or exporting it to some audio export.
2. While using adb connection, the only port that is used is 55555, although the feature to change the port is appeared in the settings. But changing it to anything else does not change the port.
3. Any method of closing the program does not close the adb.exe process and related ports, they are keep listening. Futhermore, attempt to re-connect the app to adb fails since the tcp ports listening is started. OS returns an error of single port bind.

I suppose nr.1 could be caused by interference of the signals from several ports, since in CurrPorts i can see that there are 5 adb connections and 4 of them are sending data both directions. But im not sure how it was pre 2.2.4, since from today i can't use abd on 2.2.3 due to "frame size too big" error.

Im not sure if this amount of info is enough, please feel free to request any additional info.

[AlehAbakshonak]

Update - the reason for the robotic voice, nr.1, was the f32 audio format setting; any of the i16-32 formats are suitable, and the u8 format is also bad. If only f32 wasn't used by default...

Nrs 2 and 3 seem to be closed by teamclouday, but I will wait for the release version before closing the issue by myself.

[wiiznokes]

i16 should be the default:

AndroidMic/Android/app/src/main/java/io/github/teamclouday/androidMic/Preferences.kt

Line 33 in d8952dd

val sampleRate = enumPreference("sampleRate", SampleRates.S44100)

.

Maybe you changed it without noticing or the config propagated from an old version of the app

[teamclouday]

Cool I'll make a new release soon!