The ABXY are basically a clone of the original SNES controller buttons. Although everyone seems to be getting two purple and two lilac coloured buttons, there's a disparity to the type of buttons folks are getting - some get two convex and two concave buttons, others have gotten three concave and one convex, etc.. You can swap out the buttons and d-pad (and their membranes) for ones from original SNES controllers (not SNES Classic), which gives a more retro "mushy" feel (if your replacement buttons have 3 "pins", you may need to file or clip one of the pins off) Game saves don't seem to be working for me? Save states are fine, but the built-in save function in games doesn't seem to work? If you only care about how your theme looks via AV out, and don't care about it looking aliased/jagged on the internal display, design for the regular 640 x 480 base Added a note to the Game Boy Advance section about the newly discovered gba_bios.bin loading bug, and how to work around it (thanks bnister!)

You can swap the battery for a higher-capacity 3500 mAh 18650, which will give you longer playtime (at the cost of longer charging time). If you do decide to replace the battery, make sure you use one with a built-in protection circuit, as the SF2000 has no under-charge protection. The community built tool Tadpole can be used to change the theme on the SF2000, amongst many other features. The next sequence of bytes is the name of a .zip file in the bin folder, without any path (SF2000's firmware automatically looks for the .zip in a bin subfolder relative to where the .zfb file is stored - thanks .ericgoldstein for the testing!), e.g. gamename.zip Added a link to "ZFBTool" by dteyn in the "Tools and Links" section. Updated the custom firmware FAQ answer with the latest progress notes.Updated the main menu BGM sample rate details with the latest findings from bnister. Clarified which menu text colour resets after exiting a game. Added a note about charging safety (thanks for your sacrifices, Zerter#4954! 🫡) And that’s why a lot of emulation enthusiasts are excited about the Data Frog… this is something you can give as a pretty cool gift to somebody. The rest of the file is composed of pairs of 2 byte little-endian Uint16s - the first byte pair is a number indicating which ROM list the entry belongs to (more on that below); the second number is the 0-based game number within that list All of the above emulators support stave sates natively through an interface that is accessed by pressing SELECT + START simultaneously in-game. Four save state slots are provided per-game; the files have the extensions .sa0, .sa1, .sa2 and .sa3 depending on which slot they're for, and are stored in a save subfolder along-side wherever the game's ROM file is stored. The extension is appended to the name of the ROM file the save state is for; for example, if the ROM is called SD:/ROMS/Apotris.gba, and the save state is for slot 2, then the save state file name will be SD:/ROMS/save/Apotris.GBA.sa1. One weird note is that save states created for ROMs stored in the user ROMS folder on the device get their ROM file extension capitalised when a save state is created (as per the previous example with Apotris, where .gba became .GBA); this does not happen with save states created in the other ROM folders. The capitalisation doesn't appear to matter - the SF2000 successfully loads save states with any extension capitalisation in any folder.

The SF2000 suffers from the same graphic glitches of many budget devices. A phenomena called “screen tearing”, where the device has trouble processing the graphics fast enough for the screen to display them properly. These are other files that have been identified, which don't fit into the other categories. Non-Latin characters in the files are encoded in UTF-8. Filename The Resources folder on the microSD card contains all of the resources used by the device's firmware to construct the user interface at runtime. The following tables list the files from various firmware versions (the numbered columns, in approximate mm.dd format for firmwares we don't have official version numbers for, and regular version numbers for the rest) and what they are used for, grouped by broad categories. Resolution and format given are for the latest firmware version only; details may be different for older firmwares. The icons in the firmware columns have the following meanings:

Complete OS Files

The first four bytes are a little-endian Uint32 storing the length of the zlib-compressed raw save state data I still think the SF2000 has surprises and I've found one of them. I've decided to throw some of my own roms into the the SF2000 ROM directory and here's what I found out: Added a built-in UI for global button mapping (which is broken in several ways, mainly SNES and Genesis controls are swapped, and no support for setting Player 2 controls), added a History feature, added a Favourites feature

Used to store the history of played ROMs; only appears after the first game is played after installing the 05.15 or later firmware. User ROMs are not added to history, only built-in games. If a built-in game that is referenced in history is removed from the device, the device will crash when trying to view the History screen. You can delete the History.bin file to clear the device's history; there is no built-in functionality to do so Emulator is gpSP v0.91 (Git commit 261b2db). Performance is fairly poor. On the original firmware, A and B buttons are mapped correctly, but the GBA shoulder buttons are mapped to X and Y for some reason. See " Button Mappings/Key Bindings" section below. The xfgle.hgp file is a plain-text file containing the ROM "shortcuts" on the main menu for each game system. The xfgle.hgp.bak file appears to be a test version of this file that was not removed from the firmware before being sent to production This file controls some of the UI settings for the main menu. It's a plain-text file, but not an actual INI file. It's contents from the 1.5 firmware (just as an example) are as follows: SF2000 The operating system does allow for save states, as well. So you do have the ability to save and load your game play on the fly. This is a nice touch for a budget handheld. Gaming PerformanceUpdated FAQ about custom firmware with latest details (Retroarch input driver in basic functional state) Emulator is TGB Dual v0.8.3 (Git commit 9be31d3). On the original firmware, the A and B buttons were swapped. See " Button Mappings/Key Bindings" section below. Game Boy Advance Updated FAQ about custom firmware with latest details. Moved "what can I do" bullet point about custom themes to its own separate FAQ to make it easier to find, and added more details about how to actually install a theme. The screen is a 3 inch LCD that is covered by a plastic lens. There’s no lamination like we typically see in current handhelds.