mar753
commented
5 years ago @skmp Just fixed some typos etc. in the description of Reicast from Google Play store (you can copy the below text and update the description in Play store):
Play your Dreamcast games on the go & in HD.
Reicast the only Dreamcast emulator for Android. It is not perfect yet, but can already run many games.
No games or bios are included with this download, as this would be illegal. You have to dump the bios and games from your own dreamcast.
**Permissions**
- "Photos/Media/Files" -> to read game images and bios
- "Camera/Microphone" -> for dreamcast microphone emulation
- "Device & app history" -> to read emulator crash logs. You can submit the logs via the included menu to help us solve issues.
**Setup**
1. Create a folder named "reicast" on internal or external memory, and then a folder named "data" inside it. Put the bios (dc_boot.bin & dc_flash.bin) inside the data folder. When using USB cable connection Android->Windows to transfer files: Windows sometimes hides the file extension, so the filename might look like "dc_boot" on the windows explorer.
2. Create a folder anywhere you want, and put the Dreamcast games in there. Reicast currently supports .gdi, .chd (v4), and .cdi disc formats, but .cdi is discouraged due to problematic compatibility.
3. Open reicast settings and select the "reicast" folder you created as system path.
4. In order to save your game-play progress you will first need to format the memory cards. In order to do this you need to start the program, select the "boot bios" option, go to the "file" option, select the memory cards and then select the "delete all" option.
5. Finally use the game navigator to locate your games. You can also setup a game path if you want to default to a specific folder.
For further support you can visit: http://reicast.com and https://github.com/reicast/reicast-emulator
**Recommended specs**
- Cpu: Cortex-A9, Dualcore, 1.2ghz
- Gpu: Adreno, Tegra K1 or Mali400 gpus
- At least 512mb ram
I'm still not 100% certain on how to use jekyll, PRs vs commit-to-master vs blog post reviews from the team, etc. Anyone in the team has experience on it?
Meanwhile, I've (test) pushed a progress report for march, 6b44fa7924077806a2f5f86693368bd9b67500a0. Would be great to get some feedback on it.
For the April one I'll have it ready a couple of days before the end of the month, so we can review before it lands to master. Sounds fair enough?