FM-1-Swap

Download FM-1-Swap.apk from this GitHub release and install it on the phone. It replaces an earlier release of FM-1 Swap already there.

Install that file from this release and nowhere else. If Android refuses the install because a different copy of the app is already on the phone, uninstall that first, then install this file.

Not affiliated with M-VAVE. Flashing custom firmware is at your own risk.

New in 0.6.2

PATCHES has TRY ON V15. It loads that bank's 32 patches into Official V15 and starts it. They fill the first 32 slots. Patches you already saved in those slots on the virtual FM-1 are replaced, and the bank stays for the next time you TRY that same virtual FM-1.

A phone already on 0.6.1 shows this release under the top bar. UPDATE downloads it.

New in 0.6.1

TRY was stopping 386DX while its own screen said it was building voices. CTL and MC-1 stopped on the same instruction, and Kawa on a bit-test branch. The virtual FM-1 now runs both, so those firmwares keep going.

A phone already on 0.6.0 shows this release under the top bar. UPDATE downloads it.

New in 0.6.0

FoMni, the Omnichord firmware, reports FM-1_8000400. That number sits near Official Open's, and the app was waiting for Official Open to say it was ready to update. FoMni never says that, so nothing was written, whichever firmware you chose. It now switches with the ordinary update. The same goes for FiMba, Niagara Drift, and Dub Techno, and for a firmware that reports an Official Open number but doesn't answer like Official Open.

A phone already on 0.5.0 shows this release under the top bar. UPDATE downloads it.

New in 0.5.0

A firmware you have flashed says when, on its row: last installed, then the day-month-year. Forks that report the same device name are kept apart.

SETUP names every source the firmware list and the patch banks come from, with a link to each. The same credits are on the guide.

SETUP, next to the version, has a link to tip on Ko-fi.

A USB MIDI keyboard plays in TRY. Notes are played on channel 2, so a controller left on channel 1 is heard, and every port the keyboard sends on is listened to. A keyboard such as an MPK mini is no longer opened to ask whether it is an FM-1.

When a newer release of FM-1 Swap is published, a line under the top bar says so. UPDATE downloads it. Android asks you to confirm before it installs. LATER hides that line. SETUP still shows UPDATE.

The first screen can be scrolled. That is the notice that appears the first time the app opens. On a short phone the text was taller than the display, so OK sat off the bottom and you could not reach it. The notice now scrolls, and OK stays on the screen.

FIRMWARE now has the same groups as the firmware hub. You can show All, Synths, Grooveboxes, Drums, Chords, Trackers, For devs, Other, Vintage, In browser, or From source.

How it works is on the guide.

What has been tried on a real FM-1

FM-1 Swap has been used to swap firmwares on a real FM-1, including SLOOP, Felucca Rainbow, and Clipper. Those swaps completed. The pictures here are from a write that started on Clipper, which reported FM-1_900. FM-1 Swap wrote Rainbow Mode 1.1.5-rb, and the FM-1 came back reporting FM-1_911.

If a flash goes wrong

Keep the screen open and the cable in until the app says it finished. An install takes about a minute. If the write is interrupted after the update loader has taken over, leave the FM-1 plugged in and press RESUME with the same package. The FM-1 waits in that loader until a write finishes.

Some firmwares can be started in USB recovery by holding OCT− while switching on, then flashing a saved package. SLOOP and Clipper do this. Melodee does from 1.3.5, ChoralRoot from 0.16. HYP-1, FuMi-1, FiMba-1, LOF-1, ECO-1 and GRAV-1 use OCT− and OCT+ held for 5 seconds while the firmware is already running.

Official V15 and Felucca 1.6.1 do not. Holding OCT− while switching those on starts them normally. There is no recovery gesture.

If the FM-1 will not start at all, not even in USB recovery, FM-1 Swap cannot repair it. A computer that sees a USB device with UBOOT in the name, such as WL80UBOOT, is seeing the chip's own download mode. Tools built on jl-uboot-tool can put the official firmware back. Some firmwares, Melodee, FuMi-1 and Hortator among them, publish one with instructions. If the chip never gets that far, recovery needs an FM-1 Transporter. This app has not tried either.

Pictures

These shots are from a write that started on Clipper. The status line on the firmware list is the FM-1 reporting FM-1_900 before Rainbow Mode was written.

Download FM-1-Swap.apk from this GitHub release and install it on the phone. It replaces an earlier release of FM-1 Swap already there.

Install that file from this release and nowhere else. If Android refuses the install because a different copy of the app is already on the phone, uninstall that first, then install this file.

Not affiliated with M-VAVE. Flashing custom firmware is at your own risk.

New in 0.6.1

TRY was stopping 386DX while its own screen said it was building voices. CTL and MC-1 stopped on the same instruction, and Kawa on a bit-test branch. The virtual FM-1 now runs both, so those firmwares keep going.

A phone already on 0.6.0 shows this release under the top bar. UPDATE downloads it.

New in 0.6.0

FoMni, the Omnichord firmware, reports FM-1_8000400. That number sits near Official Open's, and the app was waiting for Official Open to say it was ready to update. FoMni never says that, so nothing was written, whichever firmware you chose. It now switches with the ordinary update. The same goes for FiMba, Niagara Drift, and Dub Techno, and for a firmware that reports an Official Open number but doesn't answer like Official Open.

A phone already on 0.5.0 shows this release under the top bar. UPDATE downloads it.

New in 0.5.0

A firmware you have flashed says when, on its row: last installed, then the day-month-year. Forks that report the same device name are kept apart.

SETUP names every source the firmware list and the patch banks come from, with a link to each. The same credits are on the guide.

SETUP, next to the version, has a link to tip on Ko-fi.

A USB MIDI keyboard plays in TRY. Notes are played on channel 2, so a controller left on channel 1 is heard, and every port the keyboard sends on is listened to. A keyboard such as an MPK mini is no longer opened to ask whether it is an FM-1.

When a newer release of FM-1 Swap is published, a line under the top bar says so. UPDATE downloads it. Android asks you to confirm before it installs. LATER hides that line. SETUP still shows UPDATE.

The first screen can be scrolled. That is the notice that appears the first time the app opens. On a short phone the text was taller than the display, so OK sat off the bottom and you could not reach it. The notice now scrolls, and OK stays on the screen.

FIRMWARE now has the same groups as the firmware hub. You can show All, Synths, Grooveboxes, Drums, Chords, Trackers, For devs, Other, Vintage, In browser, or From source.

How it works is on the guide.

What has been tried on a real FM-1

FM-1 Swap has been used to swap firmwares on a real FM-1, including SLOOP, Felucca Rainbow, and Clipper. Those swaps completed. The pictures here are from a write that started on Clipper, which reported FM-1_900. FM-1 Swap wrote Rainbow Mode 1.1.5-rb, and the FM-1 came back reporting FM-1_911.

If a flash goes wrong

Keep the screen open and the cable in until the app says it finished. An install takes about a minute. If the write is interrupted after the update loader has taken over, leave the FM-1 plugged in and press RESUME with the same package. The FM-1 waits in that loader until a write finishes.

Some firmwares can be started in USB recovery by holding OCT− while switching on, then flashing a saved package. SLOOP and Clipper do this. Melodee does from 1.3.5, ChoralRoot from 0.16. HYP-1, FuMi-1, FiMba-1, LOF-1, ECO-1 and GRAV-1 use OCT− and OCT+ held for 5 seconds while the firmware is already running.

Official V15 and Felucca 1.6.1 do not. Holding OCT− while switching those on starts them normally. There is no recovery gesture.

If the FM-1 will not start at all, not even in USB recovery, FM-1 Swap cannot repair it. A computer that sees a USB device with UBOOT in the name, such as WL80UBOOT, is seeing the chip's own download mode. Tools built on jl-uboot-tool can put the official firmware back. Some firmwares, Melodee, FuMi-1 and Hortator among them, publish one with instructions. If the chip never gets that far, recovery needs an FM-1 Transporter. This app has not tried either.

Pictures

These shots are from a write that started on Clipper. The status line on the firmware list is the FM-1 reporting FM-1_900 before Rainbow Mode was written.

Download FM-1-Swap.apk from this GitHub release and install it on the phone. It replaces an earlier release of FM-1 Swap already there.

Install that file from this release and nowhere else. If Android refuses the install because a different copy of the app is already on the phone, uninstall that first, then install this file.

Not affiliated with M-VAVE. Flashing custom firmware is at your own risk.

New in 0.6.0

FoMni, the Omnichord firmware, reports FM-1_8000400. That number sits near Official Open's, and the app was waiting for Official Open to say it was ready to update. FoMni never says that, so nothing was written, whichever firmware you chose. It now switches with the ordinary update. The same goes for FiMba, Niagara Drift, and Dub Techno, and for a firmware that reports an Official Open number but doesn't answer like Official Open.

A phone already on 0.5.0 shows this release under the top bar. UPDATE downloads it.

New in 0.5.0

A firmware you have flashed says when, on its row: last installed, then the day-month-year. Forks that report the same device name are kept apart.

SETUP names every source the firmware list and the patch banks come from, with a link to each. The same credits are on the guide.

SETUP, next to the version, has a link to tip on Ko-fi.

A USB MIDI keyboard plays in TRY. Notes are played on channel 2, so a controller left on channel 1 is heard, and every port the keyboard sends on is listened to. A keyboard such as an MPK mini is no longer opened to ask whether it is an FM-1.

When a newer release of FM-1 Swap is published, a line under the top bar says so. UPDATE downloads it. Android asks you to confirm before it installs. LATER hides that line. SETUP still shows UPDATE.

The first screen can be scrolled. That is the notice that appears the first time the app opens. On a short phone the text was taller than the display, so OK sat off the bottom and you could not reach it. The notice now scrolls, and OK stays on the screen.

FIRMWARE now has the same groups as the firmware hub. You can show All, Synths, Grooveboxes, Drums, Chords, Trackers, For devs, Other, Vintage, In browser, or From source.

How it works is on the guide.

What has been tried on a real FM-1

FM-1 Swap has been used to swap firmwares on a real FM-1, including SLOOP, Felucca Rainbow, and Clipper. Those swaps completed. The pictures here are from a write that started on Clipper, which reported FM-1_900. FM-1 Swap wrote Rainbow Mode 1.1.5-rb, and the FM-1 came back reporting FM-1_911.

If a flash goes wrong

Keep the screen open and the cable in until the app says it finished. An install takes about a minute. If the write is interrupted after the update loader has taken over, leave the FM-1 plugged in and press RESUME with the same package. The FM-1 waits in that loader until a write finishes.

Some firmwares can be started in USB recovery by holding OCT− while switching on, then flashing a saved package. SLOOP and Clipper do this. Melodee does from 1.3.5, ChoralRoot from 0.16. HYP-1, FuMi-1, FiMba-1, LOF-1, ECO-1 and GRAV-1 use OCT− and OCT+ held for 5 seconds while the firmware is already running.

Official V15 and Felucca 1.6.1 do not. Holding OCT− while switching those on starts them normally. There is no recovery gesture.

If the FM-1 will not start at all, not even in USB recovery, FM-1 Swap cannot repair it. A computer that sees a USB device with UBOOT in the name, such as WL80UBOOT, is seeing the chip's own download mode. Tools built on jl-uboot-tool can put the official firmware back. Some firmwares, Melodee, FuMi-1 and Hortator among them, publish one with instructions. If the chip never gets that far, recovery needs an FM-1 Transporter. This app has not tried either.

Pictures

These shots are from a write that started on Clipper. The status line on the firmware list is the FM-1 reporting FM-1_900 before Rainbow Mode was written.

Download FM-1-Swap.apk from this GitHub release and install it on the phone. It replaces an earlier release of FM-1 Swap already there.

Install that file from this release and nowhere else. If Android refuses the install because a different copy of the app is already on the phone, uninstall that first, then install this file.

Not affiliated with M-VAVE. Flashing custom firmware is at your own risk.

New in 0.5.0

FoMni, the Omnichord firmware, reports FM-1_8000400. That number sits near Official Open's, and the app was waiting for Official Open to say it was ready to update. FoMni never says that, so nothing was written, whichever firmware you chose. It now switches with the ordinary update. The same goes for FiMba, Niagara Drift, and Dub Techno, and for a firmware that reports an Official Open number but doesn't answer like Official Open.

A firmware you have flashed says when, on its row: last installed, then the day-month-year. Forks that report the same device name are kept apart.

SETUP names every source the firmware list and the patch banks come from, with a link to each. The same credits are on the guide.

SETUP, next to the version, has a link to tip on Ko-fi.

A USB MIDI keyboard plays in TRY. Notes are played on channel 2, so a controller left on channel 1 is heard, and every port the keyboard sends on is listened to. A keyboard such as an MPK mini is no longer opened to ask whether it is an FM-1.

When a newer release of FM-1 Swap is published, a line under the top bar says so. UPDATE downloads it. Android asks you to confirm before it installs. LATER hides that line. SETUP still shows UPDATE.

The first screen can be scrolled. That is the notice that appears the first time the app opens. On a short phone the text was taller than the display, so OK sat off the bottom and you could not reach it. The notice now scrolls, and OK stays on the screen.

FIRMWARE now has the same groups as the firmware hub. You can show All, Synths, Grooveboxes, Drums, Chords, Trackers, For devs, Other, Vintage, In browser, or From source.

How it works is on the guide.

What has been tried on a real FM-1

FM-1 Swap has been used to swap firmwares on a real FM-1, including SLOOP, Felucca Rainbow, and Clipper. Those swaps completed. The pictures here are from a write that started on Clipper, which reported FM-1_900. FM-1 Swap wrote Rainbow Mode 1.1.5-rb, and the FM-1 came back reporting FM-1_911.

If a flash goes wrong

Keep the screen open and the cable in until the app says it finished. An install takes about a minute. If the write is interrupted after the update loader has taken over, leave the FM-1 plugged in and press RESUME with the same package. The FM-1 waits in that loader until a write finishes.

Some firmwares can be started in USB recovery by holding OCT− while switching on, then flashing a saved package. SLOOP and Clipper do this. Melodee does from 1.3.5, ChoralRoot from 0.16. HYP-1, FuMi-1, FiMba-1, LOF-1, ECO-1 and GRAV-1 use OCT− and OCT+ held for 5 seconds while the firmware is already running.

Official V15 and Felucca 1.6.1 do not. Holding OCT− while switching those on starts them normally. There is no recovery gesture.

If the FM-1 will not start at all, not even in USB recovery, FM-1 Swap cannot repair it. A computer that sees a USB device with UBOOT in the name, such as WL80UBOOT, is seeing the chip's own download mode. Tools built on jl-uboot-tool can put the official firmware back. Some firmwares, Melodee, FuMi-1 and Hortator among them, publish one with instructions. If the chip never gets that far, recovery needs an FM-1 Transporter. This app has not tried either.

Pictures

These shots are from a write that started on Clipper. The status line on the firmware list is the FM-1 reporting FM-1_900 before Rainbow Mode was written.

Download FM-1-Swap.apk from this GitHub release and install it on the phone. It replaces an earlier release of FM-1 Swap already there.

Install that file from this release and nowhere else. If Android refuses the install because a different copy of the app is already on the phone, uninstall that first, then install this file.

Not affiliated with M-VAVE. Flashing custom firmware is at your own risk.

New in 0.4.0

The first screen can be scrolled. That is the notice that appears the first time the app opens. On a short phone the text was taller than the display, so OK sat off the bottom and you could not reach it. The notice now scrolls, and OK stays on the screen.

How it works is on the guide.

What has been tried on a real FM-1

FM-1 Swap has been used to swap firmwares on a real FM-1, including SLOOP, Felucca Rainbow, and Clipper. Those swaps completed. The pictures here are from a write that started on Clipper, which reported FM-1_900. FM-1 Swap wrote Rainbow Mode 1.1.5-rb, and the FM-1 came back reporting FM-1_911.

If a flash goes wrong

Keep the screen open and the cable in until the app says it finished. An install takes about a minute. If the write is interrupted after the update loader has taken over, leave the FM-1 plugged in and press RESUME with the same package. The FM-1 waits in that loader until a write finishes.

Some firmwares can be started in USB recovery by holding OCT− while switching on, then flashing a saved package. SLOOP and Clipper do this. Melodee does from 1.3.5, ChoralRoot from 0.16. HYP-1, FuMi-1, FiMba-1, LOF-1, ECO-1 and GRAV-1 use OCT− and OCT+ held for 5 seconds while the firmware is already running.

Official V15 and Felucca 1.6.1 do not. Holding OCT− while switching those on starts them normally. There is no recovery gesture.

If the FM-1 will not start at all, not even in USB recovery, FM-1 Swap cannot repair it. A computer that sees a USB device with UBOOT in the name, such as WL80UBOOT, is seeing the chip's own download mode. Tools built on jl-uboot-tool can put the official firmware back. Some firmwares, Melodee, FuMi-1 and Hortator among them, publish one with instructions. If the chip never gets that far, recovery needs an FM-1 Transporter. This app has not tried either.

Pictures

These shots are from a write that started on Clipper. The status line on the firmware list is the FM-1 reporting FM-1_900 before Rainbow Mode was written.

Download FM-1-Swap.apk from this GitHub release and install it on the phone. It replaces an earlier release of FM-1 Swap already there.

Install that file from this release and nowhere else. If Android refuses the install because a different copy of the app is already on the phone, uninstall that first, then install this file.

Not affiliated with M-VAVE. Flashing custom firmware is at your own risk.

New in 0.3.0

The PATCHES screen sends a hosted DX7 patch, or a bank of 32, to a connected FM-1. Official V15, FM-1+VA, and Official Open take a single patch. A bank replaces 32 patches, and you choose that bank on the FM-1. The same banks are on the patches page.

TRY takes notes from a USB MIDI keyboard plugged into the phone. SAVE sits beside TRY on a firmware page; SAVE and FLASH no longer open TRY. Firmwares you mark as FAVORITE stay on your list; the app no longer starts with rows already marked kept. The phone can offer to open FM-1 Swap when an FM-1 is plugged in. Sliding a finger onto a TRY key plays it. Clock and notification icons hide while TRY is sideways.

How it works is on the guide.

What has been tried on a real FM-1

FM-1 Swap has been used to swap firmwares on a real FM-1, including SLOOP, Felucca Rainbow, and Clipper. Those swaps completed. The pictures here are from a write that started on Clipper, which reported FM-1_900. FM-1 Swap wrote Rainbow Mode 1.1.5-rb, and the FM-1 came back reporting FM-1_911.

If a flash goes wrong

Keep the screen open and the cable in until the app says it finished. An install takes about a minute. If the write is interrupted after the update loader has taken over, leave the FM-1 plugged in and press RESUME with the same package. The FM-1 waits in that loader until a write finishes.

Some firmwares can be started in USB recovery by holding OCT− while switching on, then flashing a saved package. SLOOP and Clipper do this. Melodee does from 1.3.5, ChoralRoot from 0.16. HYP-1, FuMi-1, FiMba-1, LOF-1, ECO-1 and GRAV-1 use OCT− and OCT+ held for 5 seconds while the firmware is already running.

Official V15 and Felucca 1.6.1 do not. Holding OCT− while switching those on starts them normally. There is no recovery gesture.

If the FM-1 will not start at all, not even in USB recovery, FM-1 Swap cannot repair it. A computer that sees a USB device with UBOOT in the name, such as WL80UBOOT, is seeing the chip's own download mode. Tools built on jl-uboot-tool can put the official firmware back. Some firmwares, Melodee, FuMi-1 and Hortator among them, publish one with instructions. If the chip never gets that far, recovery needs an FM-1 Transporter. This app has not tried either.

Pictures

These shots are from a write that started on Clipper. The status line on the firmware list is the FM-1 reporting FM-1_900 before Rainbow Mode was written.

Install FM-1-Swap.apk from this release. It is the release build, package com.fmswitch, and it is not debuggable. It installs over the copy already on the phone. Do not install the debug APK on the android-debug tag, and do not install an APK from anywhere else. The signing key lives in this repository so that a later file from this same release can install over this one. Anyone else with that key could sign an update Android would accept.

If you already installed a debug build, uninstall it first. Its package is com.fmswitch.debug, and it will not update into this one.

Not affiliated with M-VAVE. Flashing custom firmware is at your own risk.

The PATCHES screen sends a hosted DX7 patch, or a bank of 32, to a connected FM-1. Official V15, FM-1+VA, and Official Open take a single patch. A bank replaces 32 patches, and you choose that bank on the FM-1. The same banks are on the patches page.

What has been tried on a real FM-1

FM-1 Swap has been used to swap firmwares on a real FM-1, including SLOOP, Felucca Rainbow, and Clipper. Those swaps completed. The pictures here are from a write that started on Clipper, which reported FM-1_900. FM-1 Swap wrote Rainbow Mode 1.1.5-rb, and the FM-1 came back reporting FM-1_911.

If a flash goes wrong

Keep the screen open and the cable in until the app says it finished. An install takes about a minute. If the write is interrupted after the update loader has taken over, leave the FM-1 plugged in and press RESUME with the same package. The FM-1 waits in that loader until a write finishes.

Some firmwares can be started in USB recovery by holding OCT− while switching on, then flashing a saved package. SLOOP and Clipper do this. Melodee does from 1.3.5, ChoralRoot from 0.16. HYP-1, FuMi-1, FiMba-1, LOF-1, ECO-1 and GRAV-1 use OCT− and OCT+ held for 5 seconds while the firmware is already running.

Official V15 and Felucca 1.6.1 do not. Holding OCT− while switching those on starts them normally. There is no recovery gesture.

If the FM-1 will not start at all, not even in USB recovery, FM-1 Swap cannot repair it. A computer that sees a USB device with UBOOT in the name, such as WL80UBOOT, is seeing the chip's own download mode. Tools built on jl-uboot-tool can put the official firmware back. Some firmwares, Melodee, FuMi-1 and Hortator among them, publish one with instructions. If the chip never gets that far, recovery needs an FM-1 Transporter. This app has not tried either.

Pictures

These shots are from a write that started on Clipper. The status line on the firmware list is the FM-1 reporting FM-1_900 before Rainbow Mode was written.

Debug build only (package com.fmswitch.debug, debuggable). The install to share is the release APK on the v0.6.2 tag.

Built from 7528661c1de39d8f8e3e30232714bea07a7f41f9 on main (versionCode 388).