Starting with episode 5 we have reasonably decent iOS (8.0+) and Android (4.1+) support.

To install the app on your iOS device you could use an Apple Developer Program certificate or Cydia Impactor application. To copy game files the latest iTunes version is recommended.

To install on your Android device you may follow the FAQ below.

[−] Spoiler
    Game path:
    The game should be stored on any sdcard (emulated or external) in ONScripter-RU folder in the root of the sdcard.
    * All the saves will be stored on the internal (emulated) sdcard due to external card being unwritable on some deivices/firmwares. For this reason you are not allowed to have ons.cfg (do not confuse with default.cfg) in the game folder if it is stored on the external sdcard.
    * On some devices it is not possible to easily determine external sdcard path, and the game will fail to launch. If this happens create default.cfg file in ONScripter-RU folder on your internal (emulated) sdcard with 'root=/full/game/path' line without quotes.

    Compatibility:
    The game targets any armv7s, arm64, or x86 droid device on firmware 4.1 and newer, with at least 2 gigabytes of RAM and OpenGL ES 2.0 support with at least 4096 pixel texture dimension limit. However, newer os versions are generally preferred.
    * Starting with droid 4.3 it is possible to use OpenGL ES 3.0 renderer on supported device models.
    * Starting with droid 4.4 it is possible to use the whole screen space.
    * Starting with droid 5.0 it is possible to gain from using 64-bit CPUs natively on supported device models.

    Fixing visual glitches:
    Some devices need render-self=no ons.cfg option to fix visual artifacts.

    Fixing cropped image on wide-screen devices:
    You need to update to r3569 or newer and specify manual screen offset used to shift left the game image in ons.cfg. For example, on Redmi Note 9 Pro with 2400x1080 screen it is system-offset-x=180.

    Performance:
    There are multiple performance issues at the moment and thus you should take good care of the configuration options described below.

    Choosing renderer:
    By default ONScripter-RU uses OpenGL ES 2.0 renderer and falls back to OpenGL ES 3.0 if OpenGL ES 2.0 renderer failed to initialise or if 'renderer-blacklist=GLES2' line is present in ons.cfg (!). OpenGL ES 3.0 may not be available on some devices, however, it may deliver slightly better performance.

    Enabling hardware video decoding:
    By default ONScripter-RU has hardware video decoding disabled on droid due to poor performance. However, you may be able to reduce power consumption by enabling it via 'hwdecoder=on' line in ons.cfg. Note that 1080p video playback is not guaranteed on any mobile devices regardless of this option.

    Fallback texture loading:
    When using OpenGL ES 2.0 renderer on certain devices you might be able to improve certain texture loading performance (e.g. Config menu) by using additional RAM caching. To enable this add 'texture-upload=ramcopy' to ons.cfg. Note that it may cause crashes on lower end devices having not enough memory. This setting is ignored when using OpenGL ES 3.0 renderer.

    FPS limit:
    You may be able to improve game performance and seriously reduce power consumption by limiting game fps to a lower value than 60 frames per second. To do so add 'force-fps=30' line to ons.cfg, where 30 is your preferred value. Note that you could additionally add 'force-vsync' line to ons.cfg to enable old-style vertical synchronisation, however it will unlikely benefit you in any way. Not setting a fps limit may result in getting rendering glitches like black stripes appearing in some scenes on some hardware.

    Texture size limit:
    You might get slightly better performance in some scenes by limiting the supported texture dimentsion limit to a lower value than your device supports. To do so add 'texlimit=4096' line to ons.cfg, where 4096 is a power-of-two value in pixels.

    Getting log dumps:
    You should install some adb drivers for your device, and then use command-line utility to obtain the necessary output. For example, on UNIX-like systems you could use:
    adb logcat | grep --line-buffered -Ei 'sdl|onscripter' > /path/to/my/log.txt


Touch controls are the same for iOS and Android:
— single finger tap for left click
— double finger tap for right click
— triple finger tap for middle click
— two finger swipe for scroll
— three finger swipe right is skip
— three finger swipe left is automode
— three finger swipe up is mute
— three finger swipe down is tab (skip to next chapter)

extract: 035646750436634546568555050