Diacritics break alphabetical order

[Travisyard]

Tested in Musikcube x86_64 on Fedora 3.0.2 and Musikdroid 3.0.2.

Expected behavior: Characters with accent marks and other diacritics should be alphabetized as if they did not have diacritics.

Observed behavior: In the album artists listing in Musikcube and Musikdroid, characters with diacritics are not alphabetized correctly.

Example: "Télépopmusik" should be between "Tautumeitas" and "The Irrepressibles", but it shows up after "True Faith".

Here is how Fedora's file manager handles it, which is well-accepted to be the correct way to alphabetize such characters:

I observed this in the album artists listing, but it is possible that it affects other lists within the app as well.

[rohitashPrajapati]

Hi, have you figured out any workaround for this?

[imoxto]

Hi, have you figured out any workaround for this?

For now im just keeping the screen awake while recording

[vijaystroup]

+1

Submitted this a few days ago as well.

[TheScalion]

Does this NPM supports android API level 33

[Fabian15-03]

Al parecer no es un tema de la librería como tal, creería que es debido a como el SO lo cataloga. Al usarlo en React Native y tenerlo en segundo plano puede ser que sea menos prioritario que una llamada telefónica que también usa el micrófono pero en una app nativa. De todas formas también tengo el mismo problema (+1). Veo como solución usar un modulo nativo de Kotlin y hacer un bridge a mi app de React Native.

[samadRopstam]

have you enabled "Audio, AirPlay, and Picture in Picture" option in xcode> Signing&Capabilities > Background Modes?

[jondrews]

+1 Experiencing basically the same issue here. Audio keeps recording when the device is locked, but a short time after locking (usually 30secs to 2mins) the audio levels become zero - it just records silence. The audio file then continues to be created, recording silence while the device is locked. When the device is later unlocked, the audio file continues to be created, and instead of recording silence the audio signal is restored to normal expected behaviour.

Any suggestions for improving this behaviour (other than keeping the screen unlocked)?

react-native version: 0.72.4 react-native-audio-recorder-player version: 3.6.0 release build tested on Oppo A52 (CPH2069) w/ Android 11, ColorOS v11.1