Range Roulette always generates same sequence after app restart about randomix HOT 9 CLOSED

I recreated it successfully on a Galaxy A32 running android 13, while I can't recreate it on my Oneplus 7 pro, even after reinstalling your exact same version from f-droid. The only possible explanation is that I have some fix in my rom that other devices haven't. Anyway, as I said, I'm going to use the "standard" Random and nextInt() function, just to make sure this is fixed :)

from randomix.

Sorry for the late reply! I didn't know about this issue and i agree, I should try to fix it. I'll update the issue as soon as i work on it 😄

from randomix.

Hi again. After a (big) pause, I'm working on this bug and more features. At the moment, I can't recreate it on my side (Android 13). Is that normal? What are the step to recreate it?

from randomix.

Hi, so I am still able to reproduce on my Samsung S20 FE with Android 13 (edit: originally we discovered this on a Fairphone 4 with Android 12). Here is a screen recording:

Note that after restarting the app, the sequence generated for the roulette is identical, i.e. "9, 3, 18, 17, 9". This is different from other random functions in the app (e.g. dice rolls) which always generate new (i.e. unpredictable) sequences after an app restart.

from randomix.

Done in aa642a1 it should work properly now. I still have a translation to wait and a couple fixes left, but I should release the update quite soon (finally 😆)

from randomix.

That's a real mistery! I did the same procedure on my Oneplus 7 Pro running an Android 13 rom, and for 4 times, I had different sequences. This means that the bug only affects certain devices? This makes no sense since we're running the same android version. I'll try to recreate it on other test devices (Android 9, 11 and 12), let's see what happens 😕
Of course, this is a bug and I have to fix it nevertheless.

from randomix.

That is odd indeed! I don't know much about modern Android development, might it be an issue that is fixed by recompilation using a newer SDK? I'm running the v2.5 build from FDroid - perhaps recompiling it with a newer SDK might include a version of java.util.concurrent.ThreadLocalRandom which has the bugfix already applied?

Edit: At least the Kotlin commit seems to imply that: JetBrains/kotlin@a2e8ed0

from randomix.

Yep, it makes sense. Anyway, just to make sure this problem is fixed, I'm looking for an alternative approach 😄

from randomix.

Awesome, thank you!

from randomix.