Ren'py and Android often don't play together well... the issue is that Android 12 changed a bunch of stuff that Ren'py interacts with and it seems to have broken some things.
I suspect that the devs of PEERLESS LUST started on version 7.6+ of Ren'py and upgraded to 8.1+, as that contains a number of Android 12 fixes, but unfortunately I can't do that - CK was started on 7.3 and can't be upgraded past 7.5.2 without having to scrap 80% of the coding and start again.
The only solution I can think of, if you want to run CK on your phone, is to use JoiPlay ( https://play.google.com/store/apps/details?id=cyou.joiplay.joiplay&hl=en&gl=US ) and download the Windows version of CK. It works in exactly the same way, but runs through the JoiPlay emulator rather than the Android OS, and so doesn't break when Android updates.
Sorry I can't be more help!
Viewing post in WEEKLY RELEASE - v0.19.3! comments
Thank you. But how about this? I do the coding, and by that I mean I pay or ask someone (Estrada777) to do it, and then I'll send it back to you, so when you make an update you can just work on that one, that is creating 2 download ports for Androids one for lower than 12 and one for android 12 and above?
I'm asking so I can have your permission to access your file.
Not Arc, but I have some input on the matter.
Arc is hesitant to update the engine because last time he did, turned out that PyTom (the developer of RenPy, the engine) did some changes that he didn’t consider major enough to be written in the changelogs but either way ended up broking quite a few things in CK.
Weeks of updates with a major gamebreaking bug that couldn’t be fixed, because now Arc wasn’t able to rollback to the old version of the engine.
Plus a thing with the autosaves that Arc had to manually tweak the engine to revert.
Point is, Arc doesn’t have the time to “audit” that the code changes between his current version of RenPy and the latest one won’t break things in unexpected ways.
Weekly updates, just one guy working on everything. The schedule is really damn tight.
Which is also the reason why I presume that, even if you contributed the code, it’s not likely that he would compile and upload two android versions.
- It would only make things even more confusing for the general public.
I can’t promise anything, but I’ll try to look into the engine update to see if it’s safe for Arc to update it.
But then there’s the issue that I don’t have a device where I could test the error you’re getting.
- I don’t really believe it’s an Android 12 issue. But rather an issue of your device by itself.
- I have a phone that shipped with a custom rom of Android 11 on launch, the manufacturer updated it to Android 12 later on and the current one is based on Android 13 (which is basically the same as 12 but with a few extra features)
Game has worked fine on my end, and same for other people. And it’s not really easy to get someone that has the issue to volunteer as a lab rat.