Here's just a thread that bundles some best practices and common issues with the Dingoo and Dingux
. Hopefully it'll be a good starting/reference point for people new to the Dingoo.
I know the Wiki is supposed to cover this, but for now the forum seems more active than the Wiki. HARDWARE FACTS AND MODIFICATIONS
- The Dingoo has a MiniSD slot, NOT a MicroSD one! Get a MiniSD adapter if you want to use a MicroSD.
- You can use a screw to mod the pin hole reset button to a more accessible button. (Youtube Video)
- The AV-Out doubles as a stereo output. This way you can use two 3.5mm headphones at the same time.
- There is NO hardware volume control: Setting the volume in an application is up to every single application.
- If you notice some stuck pixel(s) on your Dingoo, you can try to run the GBA Stuck Pixel Fixer, or the flash movie at Z0r.de. (thread)
The Dingoo can be themed to your liking. This can be done for Dingux-based menu systems (DMenu), as well as the native OS (which requires
a custom firmware with the system folder exposed).FIRMWARES:
Several firmwares are available for the Dingoo, both official and unofficial.
Check this thread by omgomg
for info on firmwares, and the flashing procedure. Or check the Wiki
. Note that if you flash a foreign firmware, you'll want to put the Dingoo's Language to English after flashing.
In the Dingoo Menu, select the rightmost option (with the A button), then Language setting is the 6th option. English should be the last option there. NATIVE OS QUIRKS
- The Y and B buttons can't be pressed together. --> This is a native OS only issue, present in pre-1.2 firmwares. Update your firmware or run Dingux instead.
- The Dingoo might not be detected on some edition(s) of Windows 7 and Windows Vista. If the device isn't recognised, try the Windows-XP based USBSTOR.sys driver from Dingoo-Digital. For installing unsigned drivers in Windows 7/Vista, check this workaround.
- File Indexing/Library scan: When disconnecting the (native) Dingoo from the PC, it will scan the device for compatible music files. This is an annoyance which can't be circumvented at this time. To speed it up slightly, make sure your MP3s have ID3 tags. Also, the Music player lists MP3s along with Wavs/content from the Sd card (Dingux /local folder). --> Update the jukebox with the SD card out. Library will be rebuilt without the SD-card content. Alternatively, use the Folder Once instead of the Playing option to select & play your music.
- For native Dingoo-OS applications, check the Wiki: Emulators, Games, Applications, Utilities.
Dingux is Linux ported to the Dingoo. The installer is composed of 2 components: the dualboot bootloader (which allows for either booting Dingux, or the native OS) and the Linux system files (rootfs and zImage). The rootfs file is the minimal root filesystem, zImage is the actual Linux kernel.
To install Dingux, download the dual_boot_installer zip
, and follow the instructions in the README file. For a running start afterwards, install the latest Dingux Local Pack
with many homebrew applications included and configured.BOOTING DINGUX
If you're having trouble getting Dingux up and running, here's a log of the boot proceedings and some known problems:
0) THE DINGOO POWERS ON --> You get a white screen.
- Observation: The Dingoo's screen stays white.
- Symptom: The White Screen Of Death would indicate that the Dingoo may be bricked: the Dingoo's firmware does not start the device.
- Cause: You probably installed an improper firmware, or a firmware improperly.
- Solution: If you have an update a320.hxf put in your internal memory, try booting the Dingoo while holding DOWN on the dpad. It should flash that firmware. If that doesn't work, try the A320 Recovery Tool. More detailed information can be found at this thread by omgomg.
1) THE DINGOO POWERS ON --> You press the SELECT-button DURING BOOT
- Observation: The Dingoo freezes on boot, while displaying the Dinux-logo.
- Symptom: The bootloader can't find the bootfiles on the SD card.
- Cause: You have either an incorrect rootfs/zImage installed OR it's the Fat32 corruption bug. Alternatively, your MiniSD card/adapter might not be properly inserted or its pins are not connecting properly.
- Solution: Install correct bootfx/zImage, OR defragment the bootfx/zImage on the SDcard, OR reformat the SD-Card (using 32K block size is reported to counter the corruption bug!) and FIRST copy the zImage and SECOND copy rootfs to it, before copying the local folder and the rest of the data. Also resist writing to the SD card under Dingux for now. (My Windows7 x64 format didn't work, where my Windows XP x32 format worked fine. You can also try Panasonic SD Formatter.)
2) BOOTING CONTINUES --> Showing the Dingux boot screen, boot procedure is run.
- Observation: Black screen displayed after bootscreen.
- Symptom: dMenu 0.4 bug
- Cause: Brightness setting set to minimum.
- Solution: Press X to turn brightness up.
- Observation: Dingux error message: cannot run '/usr/local/sbin/main': No such file or directory
- Symptom: Main menu (shell) missing.
- Cause: Dingux loads the local/sbin/main executable on start. If there is no file, nothing will execute.
- Solution: Put a shell-script or application there, ideally a menu like Dmenu or DinguXMB. Or, if you want them both, check here.
- Observation: Dingux error message: Kernel panic - not syncing VFS: unable to mount root fs
- Symptom: Dingux can't deal with rootfs
- Cause: If you're sure the bootfs/zImage you're using are correct, there might be a (filesystem) problem with your MiniSD card/adapter.
- Solution: Try another SDCard, or format the SDCard to FAT32 in a way different from how you did it before.
- Observation: Dingux error message: Segmentation Fault
- Symptom: Application Memory/Storage error (?)
- Cause: If you're booting into DMenu 0.4, you might see this message on boot. DMenu 0.4 seems less forgiving in handling errors than DMenu0.3.
- Solution: Try Updating DMenu, or throw DMenu out and use G-Menu. In the case this occurs when running other applications, it might indicate a MiniSD filesystem problem (possibly caused by DMenu). Try CHKDSK, or reformatting.
- Observation: Dingux error message: FATAL: cannot mount /dev/mmcb1k0/dev/mmcb1k0p1 on /boot (17)
- Symptom: MiniSD unmountable.
- Cause: Bad card partition/format. In my case it occured only with Panasonic SD Format on WinXP x64. Assumed to have something to do with incompatible cluster size.
- Solution: Try an alternative way of formatting your SDcard. This might help
- There is a filesystem corruption problem with Dingux, when writing to the miniSD card. Be sure to promptly backup your files from your sd card to your computer as you might need to re-install your data and possibly reformat the SD Card! When doing so, you might want to try a 32K block size as it's reported to help counter the corruption. (More Info)
- If your arcade ROM doesn't load in Mame4All, keep in mind that Mame4All only supports a subset of the ROMs available today. Rebuild your ROMset with ClrMamePro, using the datfile supplied with Mame4All.
- If you're using the Dingux Local Pack and wonder why some games don't start: they are lacking the copyrighted files from their original release. You need to own and copy those games' files to the respected folders yourself if you want them to work.
- For Dingux applications, check the Wiki: Emulators, Games, Applications.