Skip to content

Releases

0.1.6-kgsl1 (test build for #148)

Pre-release

Choose a tag to compare

@alpersamur3 alpersamur3 released this 19 Nov 20:24

test build for #148, not a release. it installs over 0.1.6 or the mali test builds (same signature) and keeps your disk and saves.

what it fixes: on snapdragons with an older kernel (888, 870, 865, 855, 778g and the like, kernel 5.4 or older) ios 26 died at the first gpu buffer of the setup's second boot. their gpu driver refuses to import memory that belongs to a file the app still has open, and thats how the app keeps ios's memory. the app's own turnip driver now retries such an import from a thread that has only the gpu's file open, which those kernels take. newer kernels take the import the first time and nothing changes there.

the gpu check now tests the same kind of memory the engine uses, and it logs which ways of importing your kernel takes (the "kgsl import" lines at the end). after the update it runs again by itself when you tap set up or resume on the ios 26 setup screen.

first run of this on a 5.4 kernel, i dont have such a phone. on my s25 (newer kernel) the check passes and ios 26 boots to the lock screen, also with every import forced through the new thread. it also has the changes of 0.1.6-mali2 and the fixes of the next version so far (the ios 16 memory setting among them).

sources: app branch kgsl-import, the turnip patch is attached (on mesa 26.2.6 with the patches of 0.1.6), the engine is the one of 0.1.6-mali2.

0.1.6-mali2 (second test build for #96)

Pre-release

Choose a tag to compare

@alpersamur3 alpersamur3 released this 16 Nov 15:36

second test build for #96, not a release. it installs over 0.1.6 or 0.1.6-mali1 (same signature) and keeps your disk and saves.

what changed since mali1: the engine's gpu memory import was refused on phones whose driver only imports host memory into its cached, non-coherent memory type (the engine only took the coherent one). it now takes the cached type and does the cache flushes and invalidates for it. first run of that code on a real driver, so if ios looks broken or freezes tell me what and when. on a snapdragon phone nothing changes: the import lands in a coherent type and the new code stays idle.

sources: app branch mali-import-app, engine branches mali-import in reims-vgpu and metal2vulkan; the qemu part is the same source as 0.1.6 (qemu-sptm asoft-android).

0.1.6-mali1 (test build for #96)

Pre-release

Choose a tag to compare

@alpersamur3 alpersamur3 released this 16 Nov 13:17

test build for #96, not a release. it installs over 0.1.6 (same signature) and keeps your disk and saves.

what it does: on a phone that runs iOS 26 on its own vulkan driver (no snapdragon), the engine now says which check refused the gpu memory import and what the driver accepts, and if it still stops on that import the next start tries a second memory mode (lazy surface views off). on a snapdragon phone nothing changes.

sources: app branch mali-import-app, engine branches mali-import in reims-vgpu and metal2vulkan; the qemu part is the same source as 0.1.6 (qemu-sptm asoft-android).

0.1.6

Choose a tag to compare

@alpersamur3 alpersamur3 released this 15 Nov 17:10

New engines for the first time since 0.1.2, with fixes for crashes and stalls on phones we do not own. Most of them could only be tested on our one phone: please tell us what changed on yours.

Engines

  • First boot on CPUs without SSBS. iOS 26 and watchOS panicked or aborted at their first boot on phones with Cortex-A55 class cores (#18, #42, #57). Fixed in the engine; on our phone both the normal path and a forced "no SSBS" boot reach the lock screen. Never run on a real A55 phone.
  • iOS 16 on Android 10. The start was killed with signal 31, because Android 10 forbids a system call the engine made (#23). The engines no longer make it on kernels older than 6.1. Never run on Android 10.
  • QEMU ending during DataMigration or after a long run. The engine could use up Android's limit of memory mappings (#6, #10). It now maps the guest's surfaces only when they are used.
  • A screen that ended QEMU. A drawing path with an extended-range colour target was refused and took QEMU down (#11).
  • Very slow picture on some Mali phones. Reading a frame back took about 250 ms where the GPU's memory is not cached for the CPU (#66). Frames are now read through a cached buffer there. Our phone does not take this path, so it has never run on a Mali or PowerVR.
  • Adreno 825 (Snapdragon 8s Gen 4) is in the driver's table (#4). Nobody has run it yet.

Setup

  • The right clock on every chip. iOS was told the timer runs at 19.2 MHz. That is true for Snapdragons; a Dimensity 9500 runs it at 1 GHz, so the guest's clock ran 52 times too fast (#66). The app now reads the frequency from the CPU, and measures it where the CPU does not say (an Exynos 9810 answers 0; measured on a Galaxy S9+: 26 MHz). A quick save made with another frequency is not loaded.
  • iOS 26: a shorter first boot. One of iOS's migration plug-ins did nothing useful here and took about a third of the DataMigration boot; it stays out of the disk now (helps #16, #48, #55, #65).
  • iOS 26: "the guest did not answer sync" at 98 % (#19, #37, #50): a setup boot now also ends cleanly when the guest's shell has gone quiet.
  • Waits follow signs of life instead of a fixed limit. The iOS 16 first start gave up after a flat 2 hours and the iOS 26 DataMigration after a flat 3 (#59, #23, #16, #55, #65). They now go on while the guest shows progress, stop after an hour in which nothing at all moves, and keep the console's last lines for a report. When the setup does give up, iOS is saved and closed first, so Resume carries on from there; 0.1.5 left iOS 16 running in the background, where Android later closed the app (#84). An iOS 26 boot whose programs keep restarting is given two hours: on our own phone such a stretch ended by itself after 26 minutes and the setup finished.
  • Why a setup is on hold. The screen and the notification say whether it waits for the phone to cool down or for the charger (battery under 15 %); #63 was the battery rule under a "hot" text. Holds start later (thermal "severe") and end at "moderate".
  • Low memory. When Android closes the app for memory during a build, the next run gives the helper VM one size less (#54, #67), and a start or a setup with little free memory asks first (#8, #17). Why the copy is so slow on those phones is not known yet.
  • A notification that Android refuses no longer takes the setup or iOS down with it (#43).
  • The app opens on home; Set up is one section per system.

Running

  • Install an .ipa into iOS 26 from the phone ("Install an .ipa…" under iOS 26 on home). The app signs it ad hoc and puts it onto iOS 26's disk while iOS is off, so the next start is a boot, not a quick-save load. Not every app runs.
  • GPU check: it no longer asks for 16-bit storage buffers (more Adreno 600-series pass, in compatibility mode); a GPU that is not supported yet gets a plain text and the link to its family's issue (#22, #31, #51, #62, #64). On drivers whose shared memory needs cache syncs (newer Malis) its host-memory test now does them, so it no longer reports that memory as broken there (#81; the fix is @fasilfaezi's, #82).
  • Experimental: iOS 26 and watchOS on the phone's own graphics driver. Until now only Adreno phones could pass, because the engine always used the app's own Turnip driver. A phone without an Adreno now passes when its own Vulkan driver gets every test of the check right and lacks only sparse memory binding: iOS 26 and watchOS then start on that driver, in the compatibility mode. This is how @fasilfaezi booted iOS 26 on a Mali-G1-Ultra with this engine (#66, #81). We have no such phone, so it has never run in our hands: expect a slow picture, wrong pictures in places (the engine does not do the cache syncs such a driver needs) or a stop, and send the report from Logs either way. The check's screen says "experimental" when this is the route. Nothing changes on Adreno phones.
  • Reports name the decisive line, memory-mapping exhaustion, a phone maker's battery manager, and Android 12's limit on child processes (#53, #58, #66). The same report is not opened twice a day. A run that ended for another reason in its first minutes is no longer reported as the memory-mapping limit (the engine names that limit at every start, and the app took that for the cause).
  • "Works" report. When iOS has run for ten minutes and your chip is not on the list of tested phones, home shows one line that opens a filled-in GitHub issue with the phone's chip, the start time and the frame rate. You read it and send it, or not; the app sends nothing by itself.
  • The live view is rebuilt for the system that runs (the watch was drawn full width after iOS 26).

Not fixed

  • Mali and PowerVR GPUs without VK_EXT_external_memory_host and Samsung Xclipse still cannot run iOS 26 and watchOS (#22, #51, #62, #64, asoft-ios #4). Newer Malis that do have it can try the experimental route above; making it fast and correct there (cache syncs in the engine, a quicker way to show the picture) is the next work. iOS 16 runs without a GPU.
  • iOS 26's DataMigration still stalls on some phones (#16, #55, #65): the cause is not known. This version shortens that boot, waits longer for one that may still come back, ends one that shows nothing sooner, and records more about it.
  • The slow "copying iOS" on phones with little memory (#54, #67).

Tested

On our Galaxy S25 Ultra (Snapdragon 8 Elite, Android 17): updating over 0.1.5 keeps iOS and loads its quick save; iOS 26 cold boot to the lock screen in about two minutes, Save and close, resume; iOS 16 start, save, resume; an iOS 16 setup from an IPSW that was already on the phone, to the end in 51 minutes (disk 20, first start 29); a full iOS 26 setup from Apple's files that were already on the phone, to the end in 99 minutes (disk 31, DataMigration 45 with a long silent stretch that it came out of by itself), then its first boot to the home screen, Save and close, and a resume in 6 seconds. On a Galaxy S9+ (Exynos 9810, Mali-G72, Android 10): the app opens, the GPU check says in plain words why iOS 26 will not run there, the timer is measured as 26 MHz; no iOS was booted on it. Also on the S25: the "works" report with a test list (line, dialog, both buttons); the low-memory question before a start. The experimental own-driver route was forced on the S25 in a debug build: the engine opened Android's Vulkan loader and Qualcomm's driver, refused that driver by name (it lacks the shared-memory extension, so it would never pass the check) and the app said so; iOS 26 on a driver that passes has never run in our hands. Not run by us: the download steps, and everything above that says so.

0.1.6 installs over 0.1.5 and earlier and keeps your iOS, its settings and its saves (same signing key). If the APK will not install, download it again and compare SHA256SUMS.txt.

Signing certificate SHA-256: d412a33bde757a6b36524e09c215b1e2a2a21285b0fd38e8e30a8c5f23672ef2. Sources and licenses as in 0.1.2 (the app's README).

Not affiliated with Apple.

0.1.5

Choose a tag to compare

@alpersamur3 alpersamur3 released this 12 Nov 01:11

Setup fixes for the "stuck at 2 %" and "crashes while building the iOS disk" reports, and logs you can share.

  • No more silent 2 %. The iOS 16 build unpacks 7 GB of iOS images and the iOS 26 and watchOS builds copy iOS onto their disks; both said nothing for many minutes, so the setup looked frozen at 2 %. They now report how far they are every 20 s. A helper VM that really stops responding (no output and no CPU time for 5 minutes) is ended, and the setup says so instead of waiting forever.
  • The helper VM fits the phone. Every phone gave the build's helper VM 4 GB, and on phones with 8 GB of RAM or less Android could end it half way (often seen as a crash while building the iOS disk). Its RAM now follows the phone's: 4 GB on 12 GB phones, 3 GB on 8 GB, 2 GB on 6 GB, 1.5 GB on 4 GB. If Android still ends it, the step runs again one size smaller. When memory is short and "Free memory for iOS" is on, the app frees memory before the build.
  • Logs. A failed setup, the app closing unexpectedly, or iOS ending by itself is kept as a log, and the app asks you to share it: Share log, or Report on GitHub, which opens a filled-in issue you read before sending. Nothing is sent by itself. The new Logs screen is in Settings and on the setup screen, even before anything is installed. Paths inside the app are shortened and nothing personal is in the logs.
  • Remove from this phone. Each system's ⋯ menu can now remove it (iOS 16, iOS 26 or watchOS) with its saves, and says how much space that frees.
  • More Adreno GPUs pass the GPU check. The compatibility mode from 0.1.4 now also covers drivers with no sparse memory at all, and the check no longer requires 8-bit storage buffers (the engine works without them). The Adreno 660 (Snapdragon 888) failed on exactly these two and passes now; other Adreno 600-series GPUs that miss only these should pass too. None of them has been tested on a real phone yet: run Check the GPU again, and reports are welcome on #1.

Not changed: the engines (iOS 16: libqemu.so, iOS 26 and watchOS: libqemu26.so) are the same as in 0.1.4. Mali and PowerVR GPUs still cannot run iOS 26 and watchOS (asoft-ios #4); iOS 16 runs without a GPU.

0.1.5 installs over 0.1.4 and earlier and keeps your iOS, its settings and its saves (same signing key). A setup that failed before can be started again from Set up. If the APK will not install, download it again: a broken download has the right size but the wrong checksum (SHA256SUMS.txt).

Signing certificate SHA-256: d412a33bde757a6b36524e09c215b1e2a2a21285b0fd38e8e30a8c5f23672ef2. Sources and licenses as in 0.1.2 (the app's README).

Not affiliated with Apple.

0.1.4

Choose a tag to compare

@alpersamur3 alpersamur3 released this 11 Nov 18:19

Adreno 740 and 750 can run iOS 26 and watchOS now (Galaxy S23 and S24 series, Z Fold6, nubia, Motorola edge 40 pro and others with a Snapdragon 8 Gen 2 or 8 Gen 3). If 0.1.2 or 0.1.3 said your GPU is not supported, install this and check again.

  • A compatibility mode for Adreno 740 and 750. On these GPUs the app's Turnip driver accepts sparse binds from host memory but reads back zeros, so the GPU check failed. Now, when that is the only thing missing, the check passes in a compatibility mode: iOS 26 and watchOS start on the engine's older GPU path, which binds nothing sparse. This is a temporary fix, not the full one: that path keeps one memory mapping per view, so a long session can reach Android's limit and stop. The app saves before that when it can. If iOS 26 stops in this mode, the app says so and links to #1: logs from these phones are what the full fix needs.
  • Android 10 to 12: the app no longer closes at its first screen. 0.1.2 and 0.1.3 used a call that exists from Android 13 on. The build now refuses any call newer than Android 10. Whether iOS 16 runs well on these Androids is not tested yet: reports welcome.
  • The update notice says what changed, colored by how important the update is.

Not changed: the engines (iOS 16: libqemu.so, iOS 26 and watchOS: libqemu26.so) are the same files as in 0.1.2 and 0.1.3. Mali GPUs still cannot run iOS 26 and watchOS (asoft-ios #4); iOS 16 runs without a GPU.

0.1.4 installs over 0.1.3, 0.1.2 and 0.1.1 and keeps your iOS, its settings and its saves (same signing key). If the APK will not install, download it again: a broken download has the right size but the wrong checksum (SHA256SUMS.txt).

Signing certificate SHA-256: d412a33bde757a6b36524e09c215b1e2a2a21285b0fd38e8e30a8c5f23672ef2. Sources and licenses as in 0.1.2 (the app's README).

Not affiliated with Apple.

ASoftware iOS for Android 0.1.3

Choose a tag to compare

@alpersamur3 alpersamur3 released this 11 Nov 17:10

A fix for 0.1.2's GPU check. If 0.1.2 told you your GPU is not supported, install this and check again.

  • The GPU check no longer fails at random. In 0.1.2 the check often said "the probe's process ended without a result (the driver crashed it)" and "not supported yet" even on a supported Adreno, while Check again usually passed. The app took the still-running check for a crashed one: Android hides a release app's other processes from it, which our development builds never showed. Tested on our S25 Ultra: the check passes on the first try.
  • After an update, the setup screen has its Check the GPU button again. A check that passed under the previous version has to run once more, and 0.1.2 hid the button that starts it.

Nothing else changed: the same engines as 0.1.2 (iOS 16: libqemu.so 916071b1, iOS 26 and watchOS: libqemu26.so c5398dcd). 0.1.3 installs over 0.1.2 and 0.1.1 and keeps your iOS, its settings and its saves (same signing key).

What 0.1.2 brought (iOS 26 and watchOS set up on the phone, the faster engine, Save and close that frees memory) and what is not working: see 0.1.2.

If the APK will not install, download it again: a broken download has the right size but the wrong checksum (SHA256SUMS.txt).

Signing certificate SHA-256: d412a33bde757a6b36524e09c215b1e2a2a21285b0fd38e8e30a8c5f23672ef2. Sources and licenses as in 0.1.2 (the app's README).

Not affiliated with Apple.

ASoftware iOS for Android 0.1.2

Choose a tag to compare

@alpersamur3 alpersamur3 released this 11 Nov 15:43

iOS 16, iOS 26 and watchOS 27.2 in an Android app, on a stock phone: no root, locked bootloader, no PC needed. iOS 26 and watchOS are drawn by the phone's GPU, and iOS's apps run natively on the phone's CPU.

Research preview, tested on one phone: Galaxy S25 Ultra (Snapdragon 8 Elite, 12 GB RAM, Android 17). iOS 26 and watchOS need an Adreno GPU and have run only on a Snapdragon 8 Elite; iOS 16 should run on most 64-bit phones, drawn on the CPU. If something fails on your phone, please open an issue with the app's log.

New since 0.1.1

  • Set up on the phone from Apple's servers, no PC: iOS 16, and after a GPU check iOS 26 and watchOS.
  • iOS 26.6.2, with its own keyboard, at 2x by default (3x is under More).
  • watchOS 27.2 in a drawn watch.
  • iOS 26 runs faster: with the app open, a cold start reaches the lock screen in about 130 s, Settings opens in 2.1 s and going back Home takes 4.9 s (S25 Ultra; scrolling stays at about 14 fps). A save comes back in about 10 s.
  • A new home screen: each system drawn as its device with its last screen in it.
  • Free memory for iOS on Android 14 and later through Wireless debugging (pair once, in Settings).
  • iOS 26 can have 6 GB of RAM (3 and 4 GB as before). It leaves Android little: on a 12 GB S25 Ultra 0.8 to 1.0 GB, and the app warns before using it.
  • Save and close frees iOS's memory while it saves, so Android no longer closes the app halfway through a save.
  • Saves stay as a way back: Go back, on the home screen or under Saves.
  • Turn off on iOS 26 and watchOS takes about 2 s and keeps what was just written.

0.1.2 installs over 0.1.1 and keeps your iOS, its settings and its saves (same signing key).

Not working or not verified

  • App Store and Apple ID, calls and SMS (there is no baseband), audio, GPU acceleration on iOS 16.
  • Android can still close the app when memory runs out, most likely right after iOS 26 resumes with 6 GB. Use Free memory first, or give iOS 26 4 GB.
  • Any phone other than the S25 Ultra, and any GPU other than the Adreno 830.
  • Our tests ran in the development build with the same engines; the release-signed APK was installed over 0.1.1 on our phone but not run through the same tests.

Set up

Install ASoftware-iOS-Android-0.1.2.apk, open it and choose what to install. iOS 16 downloads about 6 GB and takes about 75 minutes on our phone; iOS 26 and watchOS are larger and slower, and the app shows the size before it starts. Keep the phone on its charger and on Wi-Fi. Or bring a system from a PC with ASoftware iOS for Windows 0.3.0 (Send to phone in its launcher).

Neither the app nor this release holds any Apple file: everything comes from Apple during the setup.

Sources and licenses

Signing certificate SHA-256: d412a33bde757a6b36524e09c215b1e2a2a21285b0fd38e8e30a8c5f23672ef2. File checksums: SHA256SUMS.txt.

Not affiliated with Apple.

ASoftware iOS for Android 0.1.1

Choose a tag to compare

@alpersamur3 alpersamur3 released this 04 Nov 19:39

New: Turn off. iOS can now be shut down without a save: in the side bar's 💾 (Turn off iOS without saving), from the notification (Turn off), or on the home screen under More while iOS runs. iOS shuts down as an iPhone does (settings and apps stay, open apps close), and the next start boots instead of going on from the last close. Before, the only ways out were Save and close or swiping the app away, which both save.

Fixed: saves lost when the phone was short of memory. A save writes about 3 GB of iOS's memory into its disk; through Android's page cache that could fill the phone's memory, and Android's low-memory killer then closed the app, iOS with it, halfway through the save: the next start booted instead of going on. The disk now bypasses the page cache, and QEMU writes the save in bigger pieces: a save takes about 20 s and going on from it about 12 s on our phone, with no kills in our tests.

Also: the app keeps a log of what it did (starts, saves, loads) in Android/data/com.asoft.ios/files/log, which you can attach to a bug report; the start times shown are closer to what we measure (a boot is 2 to 4 minutes on our phone).

0.1.1 installs over 0.1.0 and keeps your iOS, its settings and its saves (same signing key).


iOS 16 in an Android app, on a stock phone: no root, locked bootloader, no Termux. It runs the iOS 16 that ASoftware iOS for Windows installed on your PC.

Research preview, tested on one phone: Galaxy S25 Ultra (Snapdragon 8 Elite, 12 GB RAM, Android 17). Reports from other phones (Exynos, Tensor, MediaTek) help most.

What works

  • iOS 16.7.16 full screen with touch, iOS's own keyboard, and Safari with HTTPS pages.
  • Side bar: Home, side button, 💾 saves. The phone's volume keys are iOS's, Android's back gesture is iOS's edge swipe, and turning the phone's screen off locks iOS too.
  • Quick boot: swipe the app away, or use Save and close, and iOS comes back where it was in about 12 s. Named saves are about 3 GB each.
  • Turn off: shuts iOS down without a save.
  • Settings and apps stay on the phone's own copy of the disk.

Not working: App Store and Apple ID, audio, GPU acceleration (iOS 16 draws on the CPU).

Set up

You need a Windows PC with ASoftware iOS (iOS 16) installed, and a 64-bit Android 10+ phone with about 12 GB free.

  1. Install ASoftware-iOS-Android-0.1.1.apk on the phone.
  2. On the PC, open the ASoftware iOS folder. With Windows release 0.2.0, first extract Send-ToPhone-0.1.1.zip into it; later Windows releases have the tool already.
  3. Run Send-ToPhone.cmd. It packs that iOS into ASoftware-iOS16.asoft (about 6.5 GB, a few minutes on our PC). With the phone on USB and USB debugging on, it sends the file to the app; otherwise copy the file to the phone yourself.
  4. In the app: Set up, Import (or Choose file), then Start iOS 16. The first start takes a few minutes.

The .asoft file is made on your PC from what the Windows installer downloaded from Apple. Neither the app nor this release holds any Apple file. Do not share the file.

Sources and licenses

Signing certificate SHA-256: d412a33bde757a6b36524e09c215b1e2a2a21285b0fd38e8e30a8c5f23672ef2. File checksums: SHA256SUMS.txt.

Not affiliated with Apple.