Here's a thread to somewhat centralize issues that have been uncovered with the current image, as well as observations for people looking to get an Odroid Go Advance for the first time.
This post will continually be edited by me as I go, in order to help me keep track of what I've uncovered and may help others find answers for things they can't find in other threads.
****First Time Buyers**** - If you do not have a USB Wifi Adapter for this unit, you may have a hard time getting roms onto it unless you have a Linux machine. If you have a working Wifi Adapter, then you will be able to access your Odroid Go Advance as a Samba Share. The dongle I've tested that works acceptably is a TP-Link TL-WN725N. It works out of the box, easy to configure, only does 2.4ghz Wifi however.
Firstly, there are a couple of different images (Ubuntu, Batocera, etc) and this thread is focused on the current stock offered Ubunutu image.
If you have missing roms, or no roms at all with this image, see the thread here: viewtopic.php?f=195&p=280188#p280188
You will need the install image for the OS, and an SD card writing software. For Windows, I recommend BalenaEtcher. After the card has finished, do NOT reformat the card as Windows suggests. The filesystem is unreadable by Windows. Just close Etcher and remove the card.
The guide located here: https://wiki.odroid.com/odroid_go_advance/start is a great place to start. You can get the install image from here.
After first boot (which will take a little longer due to SD card expansion) your boot time may be anywhere from 13 to 22 seconds. This is normal. Shutdown is approximately two seconds. Simply press and hold the power button on the top until the lights on the top/back next to the USB port light up and let go. To turn it off, press and hold the power button for about 2 seconds until the lights turn off. If your device has frozen for any reason, just keep pressing and holding the power button until the power completely turns off.
The screen is the best I've seen on any handheld emulator. It's roughly about the same size as the screen on the PSP and appears to be 320x480, but it looks a lot nicer on this device and extremely sufficient for any game played on it so far.
Functional for a single speaker. My first unit is not exactly loud, but it's loud enough for personal use. Headphone jack is a major plus if you want more amazing sound for your games. Don't expect it to be ear blasting across the room for parties.
The Polycarbonate shell is amazingly sturdy. However, putting it together was a slight bit of a challenge with the snaps along the edges of the screen. The Youtube video does a good job helping explain how to put it together and apply the snaps (You should have a smooth seam across all edges, and you should not feel a 'lip' at any point) however, this makes disassembly somewhat difficult if you intend to do more to this unit such as fiddle with GPIO pins and such. You won't be taking it apart as readily as you can an Odroid Go. If you're a tinkerer, you may want to plan ahead of time to make your headers accessable through the shell before you put it together.
You'll want to use the included charger cable, as it charges via the barrel jack. You can use any 5v USB phone charger or a PC USB port. Do not plug it into any other power supply even if it fits unless it has the same polarity on the plug and supplies 5v. The amperage isn't that important, but it's recommended at least a 1amp charger to be used. If you break your cable, more should be orderable on hardkernel's site. If you're enterprising, you could make one from parts you can get easily from electronics stores, just make sure you connect the wires to the correct pins on the USB port. Be very careful! If you swap pins, you could easily damage your unit! Unless you know what you're doing, it's probably a better idea to order multiple spare power cables, as they're relatively inexpensive and there is a good chance they are likely to break. Good length on the power cable, though.
None. You will need a separate Wifi adapter to access it. Once you have, you can use SSH to connect to it. Default Username/Password: odroid/odroid. After connection to Wifi, find out your IP in the show Ip configuration, and then you can access the roms folder with Windows by \\192.168.x.x (where x.x is the IP) and you will have access to three folders. At this time, you can only write to the /roms folder. If you need to make configuration file changes such as es_systems.cfg, you'll need to stick it here, and then move it via SSH to the appropriate folder. I use Putty to do this. I'm using a TP-Link TL-WN725N (Which you can get easily, try Amazon) for mine. It's low profile, and works pretty well. Transfer speeds are not amazing, but they're better than no transfer speed at all!
It is highly recommended to add a Wifi Dongle offered on Hardkernel's site as well, as it can make using this device a lot simpler when you have network connectivity.
Button One does nothing in Emulation Station. When used in an emulator, it will return you back to the Emulationstation Menu.
Button Two takes a screenshot regardless of what you are running. Be aware, this sticks a screenshot in your /home/odroid folder. Does this whether in Emulationstation or in any Emulator.
Button Three is Select and is select for most emulators.
Button Four is Start. and is start for most emulators. (I think there is one I came across where it is not, but I cannot remember offhand and will find it later)
Five and Six do nothing. in Emulationstation, In Atari Lynx it also functions as Option 1 and Option 2.
I have two Odroid go kits. My first kit had some slight issues with buttons, but my second kit works perfectly fine. There is a little more travel on the game buttons than some people may be used to, and they are nicely spaced.
Shoulder Buttons: Make sure you orient them correctly. My first install had them backwards. They're comfortable and functional. Not perfect, but decent. Would have benefitted better from two more shoulder buttons for L2 and R2, however this could be installed with an expansion header via a daughterboard.
* Emulators: (None of the Emulators have any adjustable settings at this time except PSP)
- You may need some additional BIOS files eg SCPH1001.bin for Playstation, and Atari800.bin for Atari. The emulator will tell you what you need. These will need to go in the appropriate core folder for now.
- Atari 2600/5200/7800/Lynx all seem to work perfectly fine with roms I've tested them on. (River Raid on 2600, Montezuma's Revenge on 5200, Space Invaders on 7800, Chips Challenge, Gates of Zendocon and California Games on Lynx. CG has some stuttering/framerate issues on the title and event selection screen, but seem to work fine in the actual event.)
- Gameboy/Gameboy Color/Gameboy Advance All seem to work perfectly fine with roms I've tested them on. (Super Mario Land on GB, Shantae on GBC, Super Mario Advance: Super Mario World on GBA) - Screen is not resizable and there is a definite border around the screen in GB and GBC, this is due to MGBA. Could use a configuration menu/file
- Nes/Snes All seem to work fine with some exceptions. Nes worked fine (Super Mario Bros 3) and most Snes worked fine (Super Mario World) but some did not (Star Fox, Super Mario World 2: Yoshi's Island) - Seems the current Snes core available has trouble running SuperFX games. There are Snes cores that do run this fine, though. This needs further testing.
- Sega Master System/GameGear/Genesis All seemed to work fine.
- Playstation all seemed to work fine with what I've tested, but further testing needed (Tested Gran Turismo 2, Silent Hill) However, sound emulation needs tweaking. Sound Interpolator seems set default to None, would work better if set to Gaussian, still hunting for a configuration file that may resolve this.
- PSP Is hit or miss. Lego Star Wars II runs acceptably with some minimal stutter from time to time. Dante's Inferno is extremely sluggish and choppy, as expected.
- Mame and NeoGeo do not seem to work at this time by default, and I don't have them included in my es_systems.cfg at the moment, and it doesn't seem that there is a libretro core currently installed for then currently.
- Retroarch can be installed via the Ubuntu Repo, but I can't seem to get it to run, and certainly not through Emulationstation directly. This warrants further experimentation and testing.
- Exiting an emulator is simple as pressing Function One. It will save a snapshot in your /home/odroid folder that instantly loads when you return to that specific game. Instant Save State! This also accumulates much as the screenshots.
- Keep in mind that in-game saving doesn't seem to work properly at this time. Saving states with Function one works, but if you end up back at the main menu, DO NOT EXIT until you are sure where you were or you will lose all of your progress.
Performance has been amazing. There's been no screen tearing with any emulator I've used so far, though I've noticed a slight bit of ghosting which actually helps improve the appearance of some games and is by no means unpleasant. It does not affect the gameplay in any way and I didn't even notice it at first until I was looking specifically for it. A heat sink on the main CPU isn't necessary but a copper spreader might be considerable if heat becomes an issue. Haven't noticed any heat issues at this time.
* Battery Life
I had this thing on almost all day, on and off with Wifi attached and it ran for several hours as I was fiddling with it, installing roms and such. Expect reasonably long battery life. Will try to get more exact measurements at another time.
Stock Emulationstation. You can download themes and move them via ssh to /etc/emulationstation/themes - with a bit of Samba configuration file wrangling detailed below, you can actually access the folder directly and just stick them in there.
- Stock es_systems.cfg file is missing many proper extensions for file. As mentioned above, see the thread here: viewtopic.php?f=195&p=280188#p280188 for an updated es_systems.cfg. This can be placed in your /home/odroid/.emulationstation folder (you'll need to stick it in /roms and then move it via SSH, unless you perform the Samba modifications detailed below) and a restart of Emulationstation will pick it up.
- Themes I've tested that work well: Pixel and Pixel-TFT and they look *AMAZING*. If you include boxart in /media/images in your rom folders, and an appropriate gamelist.xml in your rom folder, it will pick up box art immediately. Videos do not work yet, so save yourself the SD card space and only include box art images.
- Remapping buttons with Emulationstation didn't seem to stick. I tried remapping start and select to function Five and Six, and it didn't have any effect.
- Setting Brightness or Volume is achieved by pressing Start and selecting the Display or Sound options. These do work, so you have to make sure you have them set before you start a game.
* Needed in Future Builds
- Dedicated Controls across emulators (Batocera demonstrates this could be done, Function Two and Three work as Volume up and down regardless of what emulator you are in, something similar can be implemented for this Ubuntu image somehow) For Screen Brightness/Volume (Setting Function 2 + DPad Up/Down or Left/Right would be better for this purpose, like the Odroid Go does)
- Inclusion of nano by default for configuration, as vi could be used but is probably more convoluted to use for the average user for editing configuration files.
- Inclusion of usbView for auto-mounting of thumb drives.
- In-Game saving use of memory cards (Perhaps standard MCR format)
* Additions by me in my current install (I have not created an image to share with, but most of these changes are somewhat minor and simple and could be done by anybody with SSH access but I will be making a flashable image later)
- Installed nano
- Added exfat utilities (Confirmed works on mounting a drive manually, but USBView currently is only automounting Fat32 drives)
- installed usbview (and verified works)
- Corrected Samba configuration file to correctly create files and scripts in /opt, /odroid and /roms to assign files to the correct user and groups so they can be manipulated correctly on both Samba and through Scripts for easy rom copying or rom folder cleaning.
- Created /roms/ports for a unified location to add Quality of Life scripts (USBCopy. and RomClean.sh) and confirmed creation of new scripts and copied to /roms/ports creates functional scripts that work.
- Added the workaround for the audio controls on F5 and F6. However, this seems to break randomly, and seems to happen more with Atari emulators (Atari 2600, Atari 5200, Atari 7800 and Atari Lynx) which is probably due to these emulators making use of F5 and F6 for other functions.
* You may need to change ownership of some directories. Also may need to add a Samba password for the Odroid User.
Code: Select all
sudo chown -R odroid:odroid /roms sudo smbpasswd -a odroid
* To Do
Generate a new OS image.