Pandora Wiki - User contributions [en]

Compo4All

2016-06-03T23:24:59Z

Levi: Hack to make permissible values show properly.

Compo4All is an gaming competition system designed by Skeezix.

The initial system was based on a MAME build where highscores were uploaded to a website, but has since expanded to include native Pandora games ([[PND]]) as well.

== Platforms ==
Currently, the only supported platform is the Pandora, but there are thoughts about expanding it to the Raspberry Pi, and desktop environments.

There is an unofficial port of C4A for the GCW and Caanoo. However at the moment only a few games (no MAME) are supported yet.

== Launchers ==
* Skeezix's [http://repo.openpandora.org/?page=detail&app=compo4all-skeezix-0001 Compo4All MAME] ([http://boards.openpandora.org/index.php/topic/12127-release-compo4all-mame-ladderscoreboard-competition-for-classic-arcade-games/ Forum Thread])
* Skeezix's [http://repo.openpandora.org/?page=detail&app=compo4all-mgr-skeezix-0001 Compo4All Manager] ([http://boards.openpandora.org/index.php/topic/13742-c4a-manager-now-on-repo-beta-please-test-it-create-your-c4a-profile-without-using-c4a-mame-now/#entry260224 Forum Thread])
* [http://pandorawiki.org/User:Pmprog pmprog's] [http://repo.openpandora.org/?page=detail&app=thetournamenthub.marqwatkin Tournament Hub] ([http://boards.openpandora.org/index.php/topic/12745-pandora-compo4all-ui/ Forum Thread])
* Ziz's [http://repo.openpandora.org/?page=detail&app=Sparrow-C4A-Manager-1337 Sparrow C4A Manager] ([http://boards.openpandora.org/topic/14104-sparrow-compo4all-manager-and-puzzletube-c4a-edition-betas Forum Thread])

== Scoreboard ==
Scores are shown within the three launchers, but are also accessible via a web browser at [http://c4a.openpandora.org/ http://c4a.openpandora.org]

== Developers SDK ==

There are two ways of developing C4A stuff at the moment. First of all the official way from skeezix. Details of the official API for integrating with the Compo4All system can be found [[Compo4AllSDK|here]].

The second way is to use libSparrowNet, an independent library from Ziz, which encapsulate the network stuff with background thread and multi platform support. Details can be found [[Using_C4A_with_libSparrowNet|here]].

== Publishing a game to the servers ==

Given that a game supports compo4all (pushes scores to it, say), a few steps remain.

- the compo4all server must be told about the game, via a config file submitted to skeezix (at the openpandora boards)
- ideally, the http://c4a.openpandora.org/ website needs to have some marquee artwork (send an image to milkshake at the openpandora boards)

A config file example (pulled from current indie game) is below; the values shoudl be more or less self explanatory, but I realize at this time this isn't a great deal of information; please ask if you're confused about the syntax or acceptible values and I'll update this page!

Sample config file:

{
"active": true,
"plugin": "scoreonly",
"module": null,
"alltime": true,
"platforms": [ "pandora" ],
"league": "all",
"shortname": "mygame",
"longname": "My Game!",
"ordering": "highest-first",
"dispunit": "points",
"type": "int",
"field": "indie",
"genre": "logic",
"execinfo": {
"pandora": {
"type": "standalone",
"pnd_unique_id": "mygame.skeezix.001",
"last_known_filename_hint": "mygame.pnd",
"command_line_add": "",
"last_known_appdata_hint": "mygame",
"file_dependancies_hint": ""
}
}
}

Permissible values..

ordering: lowest-first highest-first
type: standalone
league: all
field: indie arcade
genre: logic strategy racing action shmup runngun

Keyboard

2016-04-03T22:39:23Z

Levi: Fixing gp32x links

[[Image:Pandkey.png|thumb]]

In the months before the first preorders were taken, there was much discussion and community voting about the best layout. [http://www.gp32x.de/board/index.php?/topic/43762-pandora-keyboard-layout/ This] was one of the final votes. The final layout was different from either one of the two most popular community proposals, but incorporated some of the suggestions such as having a "Pandora" button.

Many desirable applications require a keyboard,general consensus was that an on-screen keyboard wasn't good enough. For computing mode, the game controls are used for mouse, cursor and control keys.

Some classic systems such as the Atari and C64, which had keyboards, are far more comfortably emulated on a device with a keyboard.

==Hotkeys==
'''alt+ctrl+ up / down''' | switches between virtual desktops. (if you put them in a single row in the widget you can use ← →) 
'''powerbutton slidelock left''' | locks keyboard nubs L and R shoulderbuttons 
'''pandorabutton + start''' | brings up a dialogue to kill processes 
'''Fn-L''' | Toggles TV-out on/off

==Keycodes==
This table might be useful if you're trying to map keys in some program, or writing a program:
{| class="wikitable"
!Pandora button!!Keycode!!Hex Equivalent
|-
|Space || key 32 || 0020
|-
|Pandora || key 147 || 0093
|-
|D-pad up || key 273 || 0111
|-
|D-pad down || key 274 || 0112
|-
|D-pad right || key 275 || 0113
|-
|D-pad left || key 276 || 0114
|-
|Game A || key 278 || 0116
|-
|Game B || key 279 || 0117
|-
|Game Y || key 280 || 0118
|-
|Game X || key 281 || 0119
|-
|Shoulder L || key 303 || 012f
|-
|Shoulder R || key 305 || 0131
|-
|Select || key 306 || 0132
|-
|Start || key 308 || 0134
|}
Sources: [[DOSBox#Assigning_action_keys_to_A.2FB.2FX.2FY|1]], [http://www.gp32x.de/board/index.php?app=forums&module=forums&section=findpost&pid=949070 2], [http://www.gp32x.de/board/index.php?/topic/54073-the-one-nub-club/page__view__findpost__p__905644 3] [http://www.gp32x.de/board/index.php?/topic/55124-remapping-the-mouse-buttons-etc/page__view__findpost__p__896576 4] (note: the last two links give different keycodes for the gaming buttons. Possibly both numbers will work?){{FIXME|Check the keycode issue}}

== Matrix ==

The matrix layout is detailed on p.20 of the Hardware hacker's guide ([http://www.openpandora.org/downloads/PANDORA_Hackers_manual_v100.pdf here]). A more readable version appears below. A .svg version of the Pandora's keyboard layout (made by cosurgi) can be downloaded [http://www.mediafire.com/?8s157q5qj8dibjq here]. (broken link) {{FIXME|This should be embedded within this wiki. Also, that link is broken.}}

<gallery widths=250px>
Image:Final Keymat.jpg|the mat
image:Keypadmatrix.png
</gallery>

==Remapping keys on the keyboard==
First, an apology - I'm writing this without knowing how to remap the keys on the [[keyboard]], so this is not really a tutorial. It is currently just a collection point for information on the subject.

===Reference===
Forum Threads
* [[http://www.gp32x.de/board/index.php?/topic/55124-remapping-the-mouse-buttons-etc/ Remapping The Mouse Buttons, Etc?]]
* [[http://www.gp32x.de/board/index.php?/topic/54077-changing-the-function-of-buttoms/ Changing The Function Of Buttoms]]
* [[http://www.gp32x.de/board/index.php?/topic/54324-remap-gaming-buttons-within-xfce Remap Gaming Buttons Within Xfce]]

The os should allow the standard keypad and modifier keys to be defined to generate any key. So if you want shift '1' to be anything other than 'section', it is possible. somehow :(

===Linking events to Keys===
There is a Pandora event map daemon, which reacts to the lid close, Pandora button and power button.
It can be configured using the <pre>/etc/pandora/conf/eventmap</pre> file. How to reference additional special keys is TBD. A thread showing an example is [[http://www.gp32x.de/board/index.php?/topic/54944-xfce-style-changing-with-brightness-buttons-hack/ here]]
It is also possible to configure xfce to capture events (forum thread is not locatable today)

===Using shoulder buttons for mouse===
{{hint|Seems only to be reported working permanently on HF4 but see NOTE below}}
As described in this [http://www.gp32x.de/board/index.php?/topic/55124-remapping-the-mouse-buttons-etc/page__view__findpost__p__896576 post]
# Find the keycodes which you want to modify. Run '''xev''' (this needs to be installed from angstrom repo) from the terminal, and record the numbers.
# Edit the '''.pndXmodmap''' file in your home directory, modify or add (in the correct numerical order for ease) lines like this (for the shoulder buttons)
<source lang="bash">
keycode 62 = Pointer_Button1 NoSymbol Pointer_Button1
keycode 105 = Pointer_Button3 NoSymbol Pointer_Button3
</source>
# If you want to use the 'a' and 'b' buttons, the codes are 110 and 115 respectively.
# As a test, open the XFCE Accessibility settings and enable mouse keys.
# To make this permanent, download a compiled version of [http://urjaman.dy.fi/xkbset xkbset], copy to /usr/bin and chmod a+x /usr/bin/xkbset
# Create a script (file) with this as content
<source lang="bash">#!/bin/sh
xkbset m
xkbset exp =m</source>
# Now open a terminal where the file is saved, and give it executable permissions:
#:<source lang="bash">chmod +x nameofyourfile.sh</source>
#Now install it:
#:<source lang="bash">sudo cp nameofyourfile.sh /usr/bin/nameofyourfile</source>
# Add this script to XFCE autostarted stuff (Session and Startup->Application Autostart)
NOTE
# For HF5 you only need add these two commands to .xinitrc (located in your home directory)
<pre>xkbset m
xkbset exp m</pre>
note the missing =(equals) sign

===Swapping Caps Lock and Tab===
As a command line junkie, I was pretty frustrated with where Tab is. I decided to remap it to where Caps Lock is (Fn + Shift). I added the following to .pndXmodmap (in your home directory):
<pre>keysym Tab = Caps_Lock
remove Lock = Caps_Lock
keycode 66 = Tab NoSymbol Tab
add Lock = Caps_Lock</pre>
After you add this, just run "xmodmap ~/.pndXmodmap" to reload the keymappings

== Keyboard layout changer tool ==

The '''keyboard layout changer''' provides a means to easily change keyboard layout. Possible uses are for typing in a different language on your Pandora, for using an external keyboard, or simply for making small key modifications.

=Usage guide=
#Download the PND to your Pandora from either [http://stuffs.slaeshjag.org/pnd/kblayout.pnd Slaeshjag's site] or from the [http://repo.openpandora.org/?page=detail&app=change-keymap-0.1-slaeshjag Repo] (see [[User_manual#Installing_a_PND_file_.28an_application.29|here]] for instructions on where to place PNDs)
#Run the PND; it's called "Keyboard Layout" and is in the "Settings" category
#You will now see a choice of keyboard layouts. Choose one, and your layout will change! (if the program doesn't run, find the <code>/tmp/pndrun_kblayout.out</code> file and post its contents in the [http://boards.openpandora.org/index.php?/topic/2428-keyboard-layout-changer/ official forum thread], so that the author can see what went wrong)

==Keyboard layouts==

[http://repo.openpandora.org/?page=detail&app=change-keymap-0.1-slaeshjag Keyboard layout] is an app by slashjag which helps you change layout in a graphical interface.

=== Make your own ===

*Go to the <code>/media/yourSDcard/pandora/appdata/kblayout/keymaps</code> directory. Inside, you will see a bunch of files. Open any one with a text editor, and you'll see something like this:

./setxkbmap -layout us
xmodmap ~/.pndXmodmap

What this means is that it's using the "us" layout with the modifications specified in the ".pndXmodmap" file (the Pandora needs these modifications because its keyboard isn't the same as a standard one).

So there are two basic things you could change: you could replace "us" with a different base layout, or you could replace "~/.pndXmodmap" with a different file.

===Base layouts===
The default layout is "us". The full list of base layouts included with the Pandora is listed in the file <code>/usr/share/X11/xkb/keymap/xfree86</code>. Here's the full list:
{{HideableNotes|<pre>
us
ar
be
bg
br
cz
de
ch_de
ch_fr
dk
dvorak
en_US
es
fr
fr-latin9
fr_CA
gb
hr
it
jp106
lt
lt_std
lv
mk
mt
no
pl
pt
ro
ro_microsoft
ru
se_FI
se_SE
sl
sl_SI
sk
syr
th
th_tis
th_pat
tr
uk
us_flexpro
us_intl
us_microsoft
uz
cz_qwerty
de_CH
fr_CH
mt_us
sk_qwerty
</pre>}}

If you just want to use one of these base layouts with no modifications, make a new file in the <code>/media/yourSDcard/pandora/appdata/kblayout/keymaps</code> directory, name it anything, open it in a text editor and place the following text inside, replacing "xx" with any of the codes in the above list:
./setxkbmap -layout xx
Save the file. Then just start Keyboard Layout Changer, and you'll be able to select it.

===xmodmap===
This type of file modifies whatever base layout is selected. One of these comes by default with your Pandora OS. You can find the <code>.pndXmodmap</code> file in the <code>/home/username</code> directory. It might be hidden, so press Ctrl+H to make it visible. If you open it with a text editor, you'll see this:

{{HideableNotes|<pre>keycode 9 = Escape NoSymbol Escape
keycode 10 = 1 section 1 section
keycode 11 = 2 braceleft 2 braceleft
keycode 12 = 3 braceright 3 braceright
keycode 13 = 4 asciitilde 4 asciitilde
keycode 14 = 5 percent 5 percent
keycode 15 = 6 asciicircum 6 asciicircum
keycode 16 = 7 ampersand 7 ampersand
keycode 17 = 8 asterisk 8 asterisk
keycode 18 = 9 bracketleft 9 bracketleft
keycode 19 = 0 bracketright 0 bracketright
keycode 22 = BackSpace Delete BackSpace Delete
keycode 24 = q Q q Q
keycode 25 = w W w W
keycode 26 = e E e E
keycode 27 = r R r R
keycode 28 = t T t T
keycode 29 = y Y y Y
keycode 30 = u U u U
keycode 31 = i I i I
keycode 32 = o O o O
keycode 33 = p P p P
keycode 34 = parenleft NoSymbol parenleft
keycode 35 = parenright NoSymbol parenright
keycode 36 = Return Multi_key Return
keycode 37 = Control_L NoSymbol Control_L
keycode 38 = a A a A
keycode 39 = s S s S
keycode 40 = d D d D
keycode 41 = f F f F
keycode 42 = g G g G
keycode 43 = h H h H
keycode 44 = j J j J
keycode 45 = k K k K
keycode 46 = l L l L
keycode 47 = semicolon NoSymbol semicolon
keycode 48 = apostrophe NoSymbol apostrophe
keycode 49 = grave NoSymbol grave
keycode 50 = Shift_L NoSymbol Shift_L
keycode 52 = z Z z Z
keycode 53 = x X x X
keycode 54 = c C c C
keycode 55 = v V v V
keycode 56 = b B b B
keycode 57 = n N n N
keycode 58 = m M m M
keycode 59 = comma less comma less
keycode 60 = period greater period greater
keycode 61 = slash NoSymbol slash
keycode 62 = Shift_R NoSymbol Shift_R
keycode 64 = Alt_L NoSymbol Alt_L
keycode 65 = space NoSymbol space
keycode 66 = Caps_Lock NoSymbol Caps_Lock
keycode 67 = F1 NoSymbol F1
keycode 68 = F2 NoSymbol F2
keycode 69 = F3 NoSymbol F3
keycode 70 = F4 NoSymbol F4
keycode 71 = F5 NoSymbol F5
keycode 72 = F6 NoSymbol F6
keycode 73 = F7 NoSymbol F7
keycode 74 = F8 NoSymbol F8
keycode 75 = F9 NoSymbol F9
keycode 76 = F10 NoSymbol F10
keycode 82 = minus NoSymbol minus NoSymbol
keycode 83 = Home quotedbl Home quotedbl
keycode 86 = plus NoSymbol plus NoSymbol
keycode 87 = Prior Multi_key Prior Multi_key
keycode 88 = End XF86_Switch_VT_2 End XF86_Switch_VT_2
keycode 89 = Next XF86_Switch_VT_1 Next XF86_Switch_VT_1
keycode 95 = F11 NoSymbol F11
keycode 96 = F12 NoSymbol F12
keycode 118 = Insert NoSymbol Insert
keycode 132 = yen NoSymbol yen
keycode 187 = parenleft NoSymbol parenleft
keycode 188 = parenright NoSymbol parenright
keycode 191 = acute NoSymbol acute
keycode 192 = bar NoSymbol bar
keycode 193 = underscore NoSymbol underscore
keycode 194 = numbersign NoSymbol numbersign
keycode 195 = exclam NoSymbol exclam
keycode 196 = sterling NoSymbol sterling
keycode 197 = quotedbl NoSymbol quotedbl
keycode 198 = at NoSymbol at
keycode 199 = colon NoSymbol colon
keycode 200 = dollar NoSymbol dollar
keycode 201 = EuroSign NoSymbol EuroSign
keycode 222 = question NoSymbol question
keycode 235 = Tab NoSymbol Tab</pre>}}

Ok, now let's break this down a little. <code>keycode 38 = a A a A</code> - the first two letters after the = sign are what you'll get if you press the button marked A with and without holding "shift". The next two are with and without shift modifier together with a second modifier, but since there's no second modifier on the Pandora, this is redundant really. What about Fn, you may ask, isn't that a second modifier? The Fn-key acts on a lower level, and is not seen as a separate key. Instead, there are separate keycode entries for all Fn keys (the ones marked in blue on your Pandora). "NoSymbol" means that the combination doesn't produce a character. You can find a full list of symbols (or "keysyms") that you can use [http://wiki.linuxquestions.org/wiki/List_of_Keysyms_Recognised_by_Xmodmap over here].

You can edit the .pndXmodmap file itself if you want to. That'll change the default keyboard layout you have at startup.

But you can also make secondary custom keyboard layouts.

For example, here's how to make a selectable custom Russian keyboard layout:

====Making a custom Russian keyboard layout====
Make two new files inside <code>/media/yourSDcard/pandora/appdata/kblayout/keymaps</code>. One called "RU-translit" (the name doesn't matter), one called ".rumodmap" (the dot at the start of the name is to make it not show up in the Keyboard Layout Changer menu as a keymap; that's the function of the ''first'' file you made). Put this text in the RU-translit file:
./setxkbmap -layout us
xmodmap keymaps/.rumodmap

Put this text in the .rumodmap file:

{{HideableNotes|<pre>keycode 9 = Escape NoSymbol Escape
keycode 10 = 1 section 1 section
keycode 11 = 2 braceleft 2 braceleft
keycode 12 = 3 braceright 3 braceright
keycode 13 = 4 asciitilde 4 asciitilde
keycode 14 = 5 percent 5 percent
keycode 15 = 6 asciicircum 6 asciicircum
keycode 16 = 7 ampersand 7 ampersand
keycode 17 = 8 asterisk 8 asterisk
keycode 18 = 9 bracketleft 9 bracketleft
keycode 19 = 0 bracketright 0 bracketright
keycode 22 = BackSpace Delete BackSpace Delete
keycode 24 = Cyrillic_ya Cyrillic_YA Cyrillic_ya Cyrillic_YA
keycode 25 = Cyrillic_zhe Cyrillic_ZHE Cyrillic_zhe Cyrillic_ZHE
keycode 26 = Cyrillic_ie Cyrillic_IE Cyrillic_ie Cyrillic_IE
keycode 27 = Cyrillic_er Cyrillic_ER Cyrillic_er Cyrillic_ER
keycode 28 = Cyrillic_te Cyrillic_TE Cyrillic_te Cyrillic_TE
keycode 29 = Cyrillic_yeru Cyrillic_YERU Cyrillic_yeru Cyrillic_YERU
keycode 30 = Cyrillic_u Cyrillic_U Cyrillic_u Cyrillic_U
keycode 31 = Cyrillic_i Cyrillic_I Cyrillic_i Cyrillic_I
keycode 32 = Cyrillic_o Cyrillic_O Cyrillic_o Cyrillic_O
keycode 33 = Cyrillic_pe Cyrillic_PE Cyrillic_pe Cyrillic_PE
keycode 34 = parenleft NoSymbol parenleft
keycode 35 = parenright NoSymbol parenright
keycode 36 = Return Multi_key Return
keycode 37 = Control_L NoSymbol Control_L
keycode 38 = Cyrillic_a Cyrillic_A Cyrillic_a Cyrillic_A
keycode 39 = Cyrillic_es Cyrillic_ES Cyrillic_es Cyrillic_ES
keycode 40 = Cyrillic_de Cyrillic_DE Cyrillic_de Cyrillic_DE
keycode 41 = Cyrillic_ef Cyrillic_EF Cyrillic_ef Cyrillic_EF
keycode 42 = Cyrillic_ghe Cyrillic_GHE Cyrillic_ghe Cyrillic_GHE
keycode 43 = Cyrillic_che Cyrillic_CHE Cyrillic_che Cyrillic_CHE
keycode 44 = Cyrillic_shorti Cyrillic_SHORTI Cyrillic_shorti Cyrillic_SHORTI
keycode 45 = Cyrillic_ka Cyrillic_KA Cyrillic_ka Cyrillic_KA
keycode 46 = Cyrillic_el Cyrillic_EL Cyrillic_el Cyrillic_EL
keycode 47 = semicolon NoSymbol semicolon
keycode 48 = apostrophe NoSymbol apostrophe
keycode 49 = grave NoSymbol grave
keycode 50 = Shift_L NoSymbol Shift_L
keycode 52 = Cyrillic_ze Cyrillic_ZE Cyrillic_ze Cyrillic_ZE
keycode 53 = Cyrillic_ha Cyrillic_HA Cyrillic_ha Cyrillic_HA
keycode 54 = Cyrillic_tse Cyrillic_TSE Cyrillic_tse Cyrillic_TSE
keycode 55 = Cyrillic_ve Cyrillic_VE Cyrillic_ve Cyrillic_VE
keycode 56 = Cyrillic_be Cyrillic_BE Cyrillic_be Cyrillic_BE
keycode 57 = Cyrillic_en Cyrillic_EN Cyrillic_en Cyrillic_EN
keycode 58 = Cyrillic_em Cyrillic_EM Cyrillic_em Cyrillic_EM
keycode 59 = comma less comma less
keycode 60 = period greater period greater
keycode 61 = slash NoSymbol slash
keycode 62 = Shift_R NoSymbol Shift_R
keycode 64 = Alt_L NoSymbol Alt_L
keycode 65 = space NoSymbol space
keycode 66 = Caps_Lock NoSymbol Caps_Lock
keycode 67 = Cyrillic_yu Cyrillic_YU Cyrillic_yu Cyrillic_YU
keycode 68 = Cyrillic_e Cyrillic_E Cyrillic_e Cyrillic_E
keycode 69 = Cyrillic_softsign Cyrillic_SOFTSIGN Cyrillic_softsign Cyrillic_SOFTSIGN
keycode 70 = Cyrillic_sha Cyrillic_SHA Cyrillic_sha Cyrillic_SHA
keycode 71 = Cyrillic_shcha Cyrillic_SHCHA Cyrillic_shcha Cyrillic_SHCHA
keycode 72 = Cyrillic_io Cyrillic_IO Cyrillic_io Cyrillic_IO
keycode 73 = Cyrillic_hardsign Cyrillic_HARDSIGN Cyrillic_hardsign Cyrillic_HARDSIGN
keycode 74 = F8 NoSymbol F8
keycode 75 = F9 NoSymbol F9
keycode 76 = F10 NoSymbol F10
keycode 82 = minus Prior minus Prior
keycode 83 = Home quotedbl Home quotedbl
keycode 86 = plus NoSymbol plus NoSymbol
keycode 87 = Prior Multi_key Prior Multi_key
keycode 88 = End XF86_Switch_VT_2 End XF86_Switch_VT_2
keycode 89 = Next XF86_Switch_VT_1 Next XF86_Switch_VT_1
keycode 95 = F11 NoSymbol F11
keycode 96 = F12 NoSymbol F12
keycode 118 = Delete Insert Delete
keycode 132 = yen NoSymbol yen
keycode 187 = parenleft NoSymbol parenleft
keycode 188 = parenright NoSymbol parenright
keycode 191 = acute NoSymbol acute
keycode 192 = bar NoSymbol bar
keycode 193 = underscore NoSymbol underscore
keycode 194 = numbersign NoSymbol numbersign
keycode 195 = exclam NoSymbol exclam
keycode 196 = sterling NoSymbol sterling
keycode 197 = quotedbl NoSymbol quotedbl
keycode 198 = at NoSymbol at
keycode 199 = colon NoSymbol colon
keycode 200 = dollar NoSymbol dollar
keycode 201 = EuroSign NoSymbol EuroSign
keycode 222 = question NoSymbol question
keycode 235 = Tab NoSymbol Tab</pre>}}

Once that's done, you can open the Keyboard Layout Changer, choose "RU-translit", and your keyboard layout will change to a layout similar to [http://i.imgur.com/O96Pu.gif this one], with extra letters replacing F1-F7 (note: for those 7 letters, you can only use the Shift on the Pandora's front face, not the left shoulder button). To change back, open Keyboard Layout Changer again and select "default".

In the same way, you can create any other sorts of custom layouts. The easiest way to create a new modmap file is to copy+paste the contents of <code>/home/username/.pndXmodmap</code> into a new file in the <code>/media/yourSDcard/pandora/appdata/kblayout/keymaps</code> directory and make adjustments to whatever you want to change.

==How many keypresses can it detect at once?==
It can detect two "regular" keys being pressed at once[http://www.gp32x.de/board/index.php?s=&showtopic=44326&view=findpost&p=651104]. However, this restriction does not apply to the game controls, or the central "Menu" keys.

* The keyboard is listed on p.20 of the hackers manual

== Dpad ==
8way D-pad designed by DaveC.
[[File:dpad.jpg|thumbnail|right|D-pad]]
 

== ABXY ==
The abxy-cluster provides quick and easy access to ingame options. It is also used for hotkeys in [http://repo.openpandora.org/?page=detail&app=pndmanager-bzar PND-manager]]
[[File:abxy.jpg|thumbnail|right|ABXY]]
 

== Default mapping of game controls ==
For desktop use, game controls are mapped to useful functions, replacing dedicated cursor keys and extra buttons on larger keyboards.

[[File:Pandora_keyboard_mapping.png|400px|thumb|left|overview of game control mappings]]

[[Category:Keyboard]]
[[Category:Software]]
[[Category:Tutorials]]
[[Category:Optimization]]

New PND format

2014-02-05T22:25:36Z

Levi: /* The 2014/Pyra effort */ updates and clarifications based on chat

The current PND format has some shortcomings as listed below. This page should serve as a discussion page/white board for how the format could be improved.

''' Proposal for discussion, this is just some opening shots '''

== Current situation ==
The current (ISO-based) PND format has the following shortcomings:

* It currently uses ISO, SquashFS, and other filesystems... This means that there's no standard to follow, and libpnd needs to carry around support for a multitude of file systems.
* It (often, but not always) uses the [http://en.wikipedia.org/wiki/ISO_9660 ISO file system] which is inefficient at storing data, because:
** It contains duplicate headers for each file entry[http://users.telenet.be/it3.consultants.bvba/handouts/ISO9960.html] (one version with big-endian integers, one version with little-endian integers[http://en.wikipedia.org/wiki/Endianness]) which leads to many kilobytes of wasted space.
** Its file tables are fixed-size, and there are therefore limitations on how many folders you can have, what names you can give your files, how big your files can be etc. For instance, files can only have names that are max 31 characters long, all upper-case, and limited to the ASCII character encoding, and an ISO does only support a folder depth of 8[http://www.on-time.com/rtos-32-docs/rtfiles-32/programming-manual/iso-9660/]. To support more, the Joliet file system extension is needed (or isofs won't recognize all file paths), and the Joliet header can be placed practically anywhere in the file, which means additional seek times.
** It needs various file system extensions to behave correctly, like for example [http://en.wikipedia.org/wiki/Rock_Ridge Rock Ridge Interchange Protocol] and [http://en.wikipedia.org/wiki/Joliet_(file_system) Joliet]. Without them, it becomes pretty useless as demonstrated above, and with them, it becomes difficult to read by a tool (You can only use isofs! There are no other tools out there for programmers to use!).
** It's very difficult to use since you need special ISO making tools to create the image. ISO is a relatively rare format if you're not technically inclined.
** If you want to add or remove files from it, it's near impossible if you use a compact ISO file, since there's no way that you can "expand" an existing ISO file.
* The PND header data is at the end (or in the middle of the file if a screenshot is included) which makes it impossible for e.g. libmagic to recognize the PND file. It will instead recognize it as an ISO file. Having the header data at the end also makes it take a very long time to find the data, making tools and the libpnd library very inefficient.
* The PND file uses a custom XML format for its metadata. There's no reason to do this, especially since the established ".desktop" file format fills exactly the same function.
(note: ".desktop" does not contain all metadata we have wanted over time, but it's of course possible to add extensions à la "X-Pandora-Whatever=xyz")
* There's no "index" for the PND file. The whole file has to be scanned (albeit backwards) to find a PXML file, and there's a big chance for false positives etc.
* Data is just appended linearly to the file so there's no order. If the format is to be extended (to e.g. include an icon file after the screenshot file), should the data just be appended as well?
* UTF-8 is strictly the only encoding that is supported. If you make your PXML on a Windows machine, it won't work.

== Proposed revisions ==
=== Step 1: File system ===
The file system for PNDs should be replaced by the ''uncompressed'' ZIP archive format. ZIP has the advantage that it's incredibly compact, and uncompressed ZIP makes it possible to read data from the file without having to do any decompression.

ZIP files are mountable using various implementations of zipfs, and most of these implementations won't store files in memory when they are being read if the ZIP file is uncompressed.

=== Step 2: Metadata ===
PND files should no longer require special tools for them to be created. Therefore, since ZIP files support random access on files, it shouldn't be necessary to append/prepend metadata to the file. The user simply includes the "PXML.xml" and "preview.png" files inside of the ZIP, and any tools that need information about the PND can simply go to the central directory of the ZIP file (or use a simple ZIP library to do it for them) and get the location of the file inside of the ZIP. This should also dramatically decrease loading times for PNDs.

Note; performance testing is needed; at the time we started, zip was enormously slower than plain ISO; with driver changes, it may or may not be so, hence our adopted multiple-filesystem-type system. zipfs is one possible option.

=== Step 3: Metadata format ===
Current PND files include so-called "PXML.xml" files. These files have a custom XML format that has a strange structure.

These files should be replaced by ".desktop" files. A PND can contain one or more ".desktop" files in its root directory that specify how an application should be launched. PND tools simply use all ".desktop" files they can find in the PND when creating launchers for the contents of the PND.

== Advantages ==
* There don't have to be ''any'' special tools for reading PND files. The package can be run on any platform using any programming language that can read ZIP files.
* We can use existing facilities to manage the launching of applications. The ".desktop" files can basically be copied without modification into standard locations of the system, and all launchers will become aware of them.
* Reading PND files becomes easier (because of better tool support... sorry, but you can't link to libpnd in all programming languages) and quicker (becuase of the central directory for random file access).

=== Benchmarks ===
A benchmark was carried through to measure the performance of various package implementations.
The compared systems were:
* ZIP-based uncompressed packages using fuse-zip (a zipfs implementation) to read the files
* ZIP-based compressed packages also using fuse-zip.
* ISO8859-based packages using isofs
* CramFS-based packages.

A total of 9 files were generated for the test. They have sizes 1, 2, 3, 4, 16, 32, 64, 128 and 256 MB, and were generated via "dd if=/dev/urandom of=$file bs=1M count=$size".

Because the files contain random data, they did not compress very well. The resulting files were:
* "zipcompressed.zip" 511.1 MB
* "zipuncompressed.zip" 511.0 MB
* "iso.iso" 511.3 MB
* "cramfs.image" 95.4 MB (WOW!)

Some notes:
* No write tests were done for obvious reasons
* No random access tests were done since the Pandora will use SD cards and thus not get penalized from random access, and that's not what we're interested in anyways.
* Before each test, the commands "sync; echo 3 > /proc/sys/vm/drop_caches" were run.

==== First test: linear read time ====
Command: "time cat mountpoint/* > /dev/null"

* ISO: 8.119 seconds
* CramFS: 1.488 seconds (WOW!)
* Zip (compressed): 8.535 seconds
* Zip (uncompressed): 8.290 seconds

==== Second test: RAM usage ====
-- TODO, have to find a good method of measuring this --

== Remaining issues ==
* How should libpnd tell the difference between old and new PND files? Should it depend on the "file" tool, should it run its own recognition algorithm, or what? Should the extension be changed to e.g. ".box" (Which was proposed in a thread)?
* How to make sure that the ZIP files are uncompressed? Should we provide a script that "uncompresses" an ordinary ZIP file?
* Is cramfs better than ZIP?
** cramfs cannot be uncompressed like ZIP can
** If you compare compressed ZIP and cramfs, cramfs is more efficient.
** cramfs is harder to use than ZIP (for the developer).
** cramfs ''needs'' to have all of its opened files in memory.

== Upgrade path from the old PND format ==
A simple script can be written that extracts the old PND file, including the screenshot and the PXML.xml file. The PXML.xml file is then converted to one or many .desktop files, and the desktop files, the preview.png file, and the package contents are compacted into a ZIP that then is renamed to "*.pnd"

== Usage scenario ==
=== Repackaging of an application from another package format ===
* The user grabs the package for the application
* He dumps the executable and all required libraries into a folder
* He dumps a "screenshot.png" file into the folder that he's made
* He copies the ".desktop" file(s) for the application from the old package, opens them, replaces "Exec=/usr/bin/bla" with "Exec=./bla" and saves them in the directory
* He uses a ZIP archiver to make a ZIP out of the folder, making sure that he sets the "uncompressed" option.

=== Creating PNDs as part of a build process ===
* The build tool creates a directory with all of the necessary information like above and invokes the "zip" utility to compress the folder.

=== Accessing a PND's contents for the... ===

==== ...lazy programmer ====
* The programmer extracts the PND into a folder via libzip and accesses its contents.

==== ...pragmatic programmer ====
* The programmer uses zipfs to mount the ZIP and accesses the file's contents.

==== ...smart performance-aware programmer ====
* The programmer fseek()'s the ZIP file until he finds 0x04034b50.
* He jumps 18 bytes forward and reads the int at that location, storing it in "length".
* He jumps 4 bytes and checks if this int matches "length". If it doesn't, it means that the file is compressed, and an error is reported.
* He then jumps forward 4 bytes and stores the short at that location in a variable "nameLength".
* Another 2-byte jump gets the short "extensionsLength".
* He then jumps 2 bytes and reads "nameLength" amount of bytes from the file.
* He then uses strcmp() to see if this string matches the sought-after file. If not, he continues the fseek().
* The programmer now skips "entensionsLength" amount of bytes.
* The programmer reads "length" amount of bytes from the file, and uses this as the sought-after file data.

==== ...performance fascist/programmer who wants low seek times ====
* The programmer fseek()'s the file from the end until he finds 0x02014b50.
* He then uses the following table to get the information he needs:
{|class="wikitable"
|+ ZIP central directory file header
|-
! Offset !! Bytes !! Description
|-
| 0 || 4 || Central directory file header signature = 0x02014b50
|-
| 4 || 2 || Version made by
|-
| 6 || 2 || Version needed to extract (minimum)
|-
| 8 || 2 || General purpose bit flag
|-
| 10 || 2 || Compression method
|-
| 12 || 2 || File last modification time
|-
| 14 || 2 || File last modification date
|-
| 16 || 4 || CRC-32
|-
| 20 || 4 || Compressed size
|-
| 24 || 4 || Uncompressed size
|-
| 28 || 2 || File name length (''n'')
|-
| 30 || 2 || Extra field length (''m'')
|-
| 32 || 2 || File comment length (''k'')
|-
| 34 || 2 || Disk number where file starts
|-
| 36 || 2 || Internal file attributes
|-
| 38 || 4 || External file attributes
|-
| 42 || 4 || Relative offset of local file header
|-
| 46 || ''n'' || File name
|-
| 46+''n'' || ''m'' || Extra field
|-
| 46+''n''+''m'' || ''k'' || File comment
|}

* The relative file offset can then be used to jump to the file in question. The file is then scanned as described in the previous section.

== The 2014/Pyra effort ==

A new format is being developed for the DragonBox Pyra handheld. Here are the requirements/notes:

The compatibility layer should have its own table?

{| class="wikitable"
|-
! Requirement !! Solutions !! Importance !! Status (decided, undecided, post-proned, won't fix, ...) !! Notes
|-
| Should the new format be supported by Pandora AND Pyra? ||
* Yes
** Makes releasing compatible applications easier.
* no
** Pandora is softfp and Pyra is hardfp - it's unlikely one package could work on both systems anyway.
|| Very high || ||
* http://boards.openpandora.org/topic/15530-the-software-side/page-7#entry310691
* This decision affects several of the requirements and possible solutions on this table and should be decided sooner
|-
| API/Daemon to switch between joystick/keyboard mode || || || ||
* Not exactly a PND-error
* aTc gathered a nice list of notes: http://boards.openpandora.org/topic/15587-userspace-input-daemon/#entry311623
|-
| Guideline for consistent use of gaming buttons:
* It should reduce the need of patches on top of the ported software
||
* A keyboard/joystick remapping function
* A guideline for software developers
|| || || No single-solution, but a set of them
|-
| Easier to parse than current PNDs and less fragile ||
* header + metadata (UBJSON) + icon + screenshots + squashfs
* tar archive
** more future proof
** easier for shell scripts
*** with dd you can extract the tar part and so
** filenames and file permissions are overhead
*** But the overhead is too small to be significant?
** easier to modify after-compiled
*** not really a problem, because the user should be contributing to the recipe anyway
*** a specialized to can be create if another solution is chosen
* zipfs uncompressed filesystem
** See above sections
* ar archive
** Like .deb format
|| || ||
|-
| Should the metadata include packages dependencies? ||
* Yes
** apt-get install package --print-uris will print download uris for dep packages. Using this uris download packages and extract all (dpkg -x 1.deb ./extracted)
*** Not enough. It'll need two passes between an online and an offline system. It's impossible to be sure that an offline installation will work in one pass without including the whole repo: http://boards.openpandora.org/topic/15530-the-software-side/page-9#entry311602
** EvilDragon voted for yes-and-no? http://boards.openpandora.org/topic/15530-the-software-side/page-5#entry310590
*** Or does it mean a minimum "os-version required" metadata on the package and let the user update the system to have the latest libraries available?
*** Possibly he doesn't care and just want something that just works: http://boards.openpandora.org/topic/15574-confliting-requirements/page-2#entry311580
** http://boards.openpandora.org/topic/15530-the-software-side/page-5#entry310627
* No.
** EvilDragon commented that he wanna a plug-and-play-and-works system ( http://boards.openpandora.org/topic/15530-the-software-side/page-3#entry310412 )
** If the user is lacking of internet access, "plug-and-play" package won't work
** .deb for general-purpose software
* set of dependencies that system is required to have (SDL, ...)
* Complete user-space like containment features (see http://www.docker.io/ for an example)
|| || Undecided ||
|-
| It should be click-and-run ||
* binfmt
* Sheebang
* File (extension) association
|| || ||
|-
| Less duplication of metadata (c.f. PXML files) || || || ||
|-
| AUR-like system:
* Building recipes is easier to replicate and contribute
* If maintainer is jerk, moderator can move his maintanership
|| Fork makepkg || || [http://boards.openpandora.org/topic/15530-the-software-side/page-7#entry310691 Cloudef is working on this task] ||
|-
| A compatibility layer for the current *.PND system:
* The more transparent, the better
||
* Dual-boot
* Virtual Machine
* Tune Debian system to include all libraries used in current SuperZaxxon
** OpenEmbedded it's based on the Debian, afterall
** Probably won't happen because of hard/soft float point library issues
* chroot
** chroot doesn't start services like the real system, then the services of the chroot must be replaced/configured
|| High || ||
* Pyra will have larger internal space, then duplicate system isn't a large problem
* For current OpenPandora, we can already run Debian on SD-card.
** Maybe we can provide Pyra apps for OpenPandora using the Debian-on-sd-card opposed to Debian-on-internal-space
|-
| Cross-building? || || || Undecided ||
|-
| Home-dir of applications ||
* Maybe on per SD-card
* Union-fs? Aufs?
* overridable by env var?
|| || ||
|-
| Overridable scripts ||
* By creating files with the right name, you can override files in the package (e.g. scripts)
* Yes:
** Cool for hackers
* No:
** Necessitates a union filesystem
** Not absolutely necessary - hackers can just rebuild the package.
|| || ||
|-
| File-extension? ||
* .pyra
** We're not using fucking DOS for lord-sake, what's the point of use 3-letters extension?
* .pyd for pyra-data
* .pyr
* .pp for pyra program
* .pa for pyra app
* .drp for dragonbox pyra
** Why limit this to just the Pyra? Could be useful in future systems/elsewhere too.
* ...
|| || undecided. || Maybe a series of polls on the boards? ;)
|-
| Keep what is good || Document all of the good features and port the content to this table || High || Not started ||
|-
| Extra bonus points for a design that can easily be used on other distros and devices as well || || Optional || Optional || Optional
|-
| Multiple binaries/icons per app || || || || Somebody (lost on the sea of comments) didn't like this design, but it should be possible for special software
|-
| Delta packages || || || || http://boards.openpandora.org/topic/15530-the-software-side/page-9#entry311600
|-
| PATH handling || || || || http://boards.openpandora.org/topic/15530-the-software-side/page-9#entry311618
|}

[[Category:PND]]
[[Category:Ideas and proposals]]

New PND format

2014-02-03T21:27:55Z

Levi: /* The 2014/Pyra effort */ Union mount stuff.

The current PND format has some shortcomings as listed below. This page should serve as a discussion page/white board for how the format could be improved.

''' Proposal for discussion, this is just some opening shots '''

== Current situation ==
The current (ISO-based) PND format has the following shortcomings:

* It currently uses ISO, SquashFS, and other filesystems... This means that there's no standard to follow, and libpnd needs to carry around support for a multitude of file systems.
* It (often, but not always) uses the [http://en.wikipedia.org/wiki/ISO_9660 ISO file system] which is inefficient at storing data, because:
** It contains duplicate headers for each file entry[http://users.telenet.be/it3.consultants.bvba/handouts/ISO9960.html] (one version with big-endian integers, one version with little-endian integers[http://en.wikipedia.org/wiki/Endianness]) which leads to many kilobytes of wasted space.
** Its file tables are fixed-size, and there are therefore limitations on how many folders you can have, what names you can give your files, how big your files can be etc. For instance, files can only have names that are max 31 characters long, all upper-case, and limited to the ASCII character encoding, and an ISO does only support a folder depth of 8[http://www.on-time.com/rtos-32-docs/rtfiles-32/programming-manual/iso-9660/]. To support more, the Joliet file system extension is needed (or isofs won't recognize all file paths), and the Joliet header can be placed practically anywhere in the file, which means additional seek times.
** It needs various file system extensions to behave correctly, like for example [http://en.wikipedia.org/wiki/Rock_Ridge Rock Ridge Interchange Protocol] and [http://en.wikipedia.org/wiki/Joliet_(file_system) Joliet]. Without them, it becomes pretty useless as demonstrated above, and with them, it becomes difficult to read by a tool (You can only use isofs! There are no other tools out there for programmers to use!).
** It's very difficult to use since you need special ISO making tools to create the image. ISO is a relatively rare format if you're not technically inclined.
** If you want to add or remove files from it, it's near impossible if you use a compact ISO file, since there's no way that you can "expand" an existing ISO file.
* The PND header data is at the end (or in the middle of the file if a screenshot is included) which makes it impossible for e.g. libmagic to recognize the PND file. It will instead recognize it as an ISO file. Having the header data at the end also makes it take a very long time to find the data, making tools and the libpnd library very inefficient.
* The PND file uses a custom XML format for its metadata. There's no reason to do this, especially since the established ".desktop" file format fills exactly the same function.
(note: ".desktop" does not contain all metadata we have wanted over time, but it's of course possible to add extensions à la "X-Pandora-Whatever=xyz")
* There's no "index" for the PND file. The whole file has to be scanned (albeit backwards) to find a PXML file, and there's a big chance for false positives etc.
* Data is just appended linearly to the file so there's no order. If the format is to be extended (to e.g. include an icon file after the screenshot file), should the data just be appended as well?
* UTF-8 is strictly the only encoding that is supported. If you make your PXML on a Windows machine, it won't work.

== Proposed revisions ==
=== Step 1: File system ===
The file system for PNDs should be replaced by the ''uncompressed'' ZIP archive format. ZIP has the advantage that it's incredibly compact, and uncompressed ZIP makes it possible to read data from the file without having to do any decompression.

ZIP files are mountable using various implementations of zipfs, and most of these implementations won't store files in memory when they are being read if the ZIP file is uncompressed.

=== Step 2: Metadata ===
PND files should no longer require special tools for them to be created. Therefore, since ZIP files support random access on files, it shouldn't be necessary to append/prepend metadata to the file. The user simply includes the "PXML.xml" and "preview.png" files inside of the ZIP, and any tools that need information about the PND can simply go to the central directory of the ZIP file (or use a simple ZIP library to do it for them) and get the location of the file inside of the ZIP. This should also dramatically decrease loading times for PNDs.

Note; performance testing is needed; at the time we started, zip was enormously slower than plain ISO; with driver changes, it may or may not be so, hence our adopted multiple-filesystem-type system. zipfs is one possible option.

=== Step 3: Metadata format ===
Current PND files include so-called "PXML.xml" files. These files have a custom XML format that has a strange structure.

These files should be replaced by ".desktop" files. A PND can contain one or more ".desktop" files in its root directory that specify how an application should be launched. PND tools simply use all ".desktop" files they can find in the PND when creating launchers for the contents of the PND.

== Advantages ==
* There don't have to be ''any'' special tools for reading PND files. The package can be run on any platform using any programming language that can read ZIP files.
* We can use existing facilities to manage the launching of applications. The ".desktop" files can basically be copied without modification into standard locations of the system, and all launchers will become aware of them.
* Reading PND files becomes easier (because of better tool support... sorry, but you can't link to libpnd in all programming languages) and quicker (becuase of the central directory for random file access).

=== Benchmarks ===
A benchmark was carried through to measure the performance of various package implementations.
The compared systems were:
* ZIP-based uncompressed packages using fuse-zip (a zipfs implementation) to read the files
* ZIP-based compressed packages also using fuse-zip.
* ISO8859-based packages using isofs
* CramFS-based packages.

A total of 9 files were generated for the test. They have sizes 1, 2, 3, 4, 16, 32, 64, 128 and 256 MB, and were generated via "dd if=/dev/urandom of=$file bs=1M count=$size".

Because the files contain random data, they did not compress very well. The resulting files were:
* "zipcompressed.zip" 511.1 MB
* "zipuncompressed.zip" 511.0 MB
* "iso.iso" 511.3 MB
* "cramfs.image" 95.4 MB (WOW!)

Some notes:
* No write tests were done for obvious reasons
* No random access tests were done since the Pandora will use SD cards and thus not get penalized from random access, and that's not what we're interested in anyways.
* Before each test, the commands "sync; echo 3 > /proc/sys/vm/drop_caches" were run.

==== First test: linear read time ====
Command: "time cat mountpoint/* > /dev/null"

* ISO: 8.119 seconds
* CramFS: 1.488 seconds (WOW!)
* Zip (compressed): 8.535 seconds
* Zip (uncompressed): 8.290 seconds

==== Second test: RAM usage ====
-- TODO, have to find a good method of measuring this --

== Remaining issues ==
* How should libpnd tell the difference between old and new PND files? Should it depend on the "file" tool, should it run its own recognition algorithm, or what? Should the extension be changed to e.g. ".box" (Which was proposed in a thread)?
* How to make sure that the ZIP files are uncompressed? Should we provide a script that "uncompresses" an ordinary ZIP file?
* Is cramfs better than ZIP?
** cramfs cannot be uncompressed like ZIP can
** If you compare compressed ZIP and cramfs, cramfs is more efficient.
** cramfs is harder to use than ZIP (for the developer).
** cramfs ''needs'' to have all of its opened files in memory.

== Upgrade path from the old PND format ==
A simple script can be written that extracts the old PND file, including the screenshot and the PXML.xml file. The PXML.xml file is then converted to one or many .desktop files, and the desktop files, the preview.png file, and the package contents are compacted into a ZIP that then is renamed to "*.pnd"

== Usage scenario ==
=== Repackaging of an application from another package format ===
* The user grabs the package for the application
* He dumps the executable and all required libraries into a folder
* He dumps a "screenshot.png" file into the folder that he's made
* He copies the ".desktop" file(s) for the application from the old package, opens them, replaces "Exec=/usr/bin/bla" with "Exec=./bla" and saves them in the directory
* He uses a ZIP archiver to make a ZIP out of the folder, making sure that he sets the "uncompressed" option.

=== Creating PNDs as part of a build process ===
* The build tool creates a directory with all of the necessary information like above and invokes the "zip" utility to compress the folder.

=== Accessing a PND's contents for the... ===

==== ...lazy programmer ====
* The programmer extracts the PND into a folder via libzip and accesses its contents.

==== ...pragmatic programmer ====
* The programmer uses zipfs to mount the ZIP and accesses the file's contents.

==== ...smart performance-aware programmer ====
* The programmer fseek()'s the ZIP file until he finds 0x04034b50.
* He jumps 18 bytes forward and reads the int at that location, storing it in "length".
* He jumps 4 bytes and checks if this int matches "length". If it doesn't, it means that the file is compressed, and an error is reported.
* He then jumps forward 4 bytes and stores the short at that location in a variable "nameLength".
* Another 2-byte jump gets the short "extensionsLength".
* He then jumps 2 bytes and reads "nameLength" amount of bytes from the file.
* He then uses strcmp() to see if this string matches the sought-after file. If not, he continues the fseek().
* The programmer now skips "entensionsLength" amount of bytes.
* The programmer reads "length" amount of bytes from the file, and uses this as the sought-after file data.

==== ...performance fascist/programmer who wants low seek times ====
* The programmer fseek()'s the file from the end until he finds 0x02014b50.
* He then uses the following table to get the information he needs:
{|class="wikitable"
|+ ZIP central directory file header
|-
! Offset !! Bytes !! Description
|-
| 0 || 4 || Central directory file header signature = 0x02014b50
|-
| 4 || 2 || Version made by
|-
| 6 || 2 || Version needed to extract (minimum)
|-
| 8 || 2 || General purpose bit flag
|-
| 10 || 2 || Compression method
|-
| 12 || 2 || File last modification time
|-
| 14 || 2 || File last modification date
|-
| 16 || 4 || CRC-32
|-
| 20 || 4 || Compressed size
|-
| 24 || 4 || Uncompressed size
|-
| 28 || 2 || File name length (''n'')
|-
| 30 || 2 || Extra field length (''m'')
|-
| 32 || 2 || File comment length (''k'')
|-
| 34 || 2 || Disk number where file starts
|-
| 36 || 2 || Internal file attributes
|-
| 38 || 4 || External file attributes
|-
| 42 || 4 || Relative offset of local file header
|-
| 46 || ''n'' || File name
|-
| 46+''n'' || ''m'' || Extra field
|-
| 46+''n''+''m'' || ''k'' || File comment
|}

* The relative file offset can then be used to jump to the file in question. The file is then scanned as described in the previous section.

== The 2014/Pyra effort ==

A new format is being developed for the DragonBox Pyra handheld. Here are the requirements/notes (this table should have an importance cell and a status (decided, undecided, post-proned, ...) cell):

The compatibility layer should have its own table?

{| class="wikitable"
|-
! Requirement !! Solutions !! Notes
|-
| API/Daemon to switch between joystick/keyboard mode || || Not exactly a PND-error
|-
| Easier to parse than current PNDs and less fragile ||
* UBSON header and metadata + icon + screenshots + cramfs
* tar filesystem
** more future proof
** easier for shell scripts
*** with dd you can extract the tar part and so
** filenames and file permissions are overhead
*** But the overhead is too small to be significant?
** easier to modify after-compiled
*** not really a problem, because the user should be contributing to the recipe anyway
*** a specialized to can be create if another solution is chosen
* zipfs uncompressed filesystem
** See above sections
||
|-
| Should the metadata include packages dependencies? ||
* Yes
** apt-get install package --print-uris will print download uris for dep packages. Using this uris download packages and extract all (dpkg -x 1.deb ./extracted)
** EvilDragon voted for yes-and-no? http://boards.openpandora.org/topic/15530-the-software-side/page-5#entry310590
*** Or does it mean a minimum "os-version required" metadata on the package and let the user update the system to have the latest libraries available?
** http://boards.openpandora.org/topic/15530-the-software-side/page-5#entry310627
* No.
** EvilDragon commented that he wanna a plug-and-play-and-works system ( http://boards.openpandora.org/topic/15530-the-software-side/page-3#entry310412 )
** If the user is lacking of internet access, "plug-and-play" package won't work
** .deb for general-purpose software
* set of dependencies that system is required to have (SDL, ...)
* Complete user-space like containment features (see http://www.docker.io/ for an example)
|| Undecided
|-
| It should be click-and-run ||
* binfmt
* Sheebang
* File (extension) association
||
|-
| Less duplication of .desktop and PXML files || ||
|-
| AUR-like system:
* Building recipes is easier to replicate and contribute
* If maintainer is jerk, moderator can move his maintanership
|| Fork makepkg ||
|-
| Guideline for consistent use of gaming buttons:
* It should reduce the need of patches on top of the ported software
||
* A keyboard/joystick remapping function
* A guideline for software developers
|| No single-solution, but a set of them
|-
| A compatibility layer for the current *.PND system:
* The more transparent, the better
||
* Dual-boot
* Virtual Machine
* Tune Debian system to include all libraries used in current SuperZaxxon
** OpenEmbedded it's based on the Debian, afterall
** Probably won't happen because of hard/soft float point library issues
* chroot
** chroot doesn't start services like the real system, then the services of the chroot must be replaced/configured
||
* Pyra will have larger internal space, then duplicate system isn't a large problem
* For current OpenPandora, we can already run Debian on SD-card.
** Maybe we can provide Pyra apps for OpenPandora using the Debian-on-sd-card opposed to Debian-on-internal-space
|-
| Cross-building? || || Undecided
|-
| Filesystem type ||
* Cramfs
* Squashfilesystem
||
|-
| Home-dir of applications ||
* Maybe on per SD-card
* Union-fs?
* overridable by env var?
||
|-
| Overridable scripts ||
* By creating files with the right name, you can override files in the package (e.g. scripts)
* Yes:
** Cool for hackers
* No:
** Necessitates unionFS.
** Not absolutely necessary - hackers can just rebuild the package.
|-
| File-extension? ||
* .pyra
** We're not using fucking DOS for lord-sake, what's the point of use 3-letters extension?
* .pyd for pyra-data
* .pyr
* .pp for pyra program
* .pa for pyra app
* .drp for dragonbox pyra
** Why limit this to just the Pyra? Could be useful in future systems/elsewhere too.
* ...
|| undecided. Maybe a series of polls on the boards?
|-
| Keep what is good || Document all of the good features and port the content to this table || Not started
|-
| Extra bonus points for a design that can easily be used on other distros and devices as well || || Optional
|-
| Multiple binaries/icons per app || || Somebody (lost on the sea of comments) didn't like this design, but it should be possible for special software
|}

[[Category:PND]]
[[Category:Ideas and proposals]]

Keyboard/Requirement Analysis Pyra

2014-01-21T02:42:25Z

Levi:

Discuss [http://boards.openpandora.org/topic/15403-pyra-keyboard-layout-requirement-analysis/ there].

#hardware
##keyboard:
###MUST: allows for both handheld thumb typing and desktop finger typing
###MUST: is possible to find the keys by touch (for thumb typing)
####surface form: flat? rounded? concave? (T4b: I would like them to be more or less flat and concave a little bit so you feel the different keys better)
####surface height: (T4b: no higher than on current Pandora, preferably almost (only almost!) flush with the rest of the surface)
####MUST: surface coating: non sticky, fingers must glide over it as easily as possible
####MUST: minimum force needed to trigger key: is possible to slide finger over key without triggering it
####SHOULD: possible to easily find central keys (e.g. f and j) by touch (e.g. raised markers)
###MUST: individual keys easy to press
####maximum force needed to trigger key: must not be so big as to make it difficult to press the key (clarified?) (too obvious to include? But I guess we should also include trivial things)
####maximum way/travel needed to trigger key: (T4b: must be low, say 0.3mm, max 0.5mm)
####room between keys: (T4b: I would like to get rid of it completely, but only technically possible if the plastic ribs between the keys aren't necessary anymore)
####size of individual keys:
#####SHOULD: width is as wide if not wider than the Pandora (ED)
#####MUST: height: is no taller than the Pandora (ED)
###MUST NOT: forces Pyra's dimensions to exceed 1-2mm beyond the Pandora's
###MUST: has easy to read labels:
####colors:
####MUST: high enough contrast -> easy to read
###SHOULD (?): backlighting
####MUST: variable intensity (PWM? - Levi)
####COULD: variable color
###is possible to map to (generally as many as possible):
####MUST: qwerty/qwertz/azerty (those are basically the same, so we can group them together)
####MUST: dvorak
####COULD: colemak
####COULD: non latin (Russian, Japanese, etc.) (clarify! what's needed for this?)
###MUST NOT: keyboard gets into the way when gaming
####<practical considerations>
##keyboard '''and''' gaming controls:
###MUST: is resistant to foreign matter (pocket lint) from getting into/between the keys: not possible with the Pandora, could be a problem with mechanical keyboards
##gaming controls:
###NOTE: I think the individual action buttons are fine on the Pandora (T4b)
###MUST: 4 action buttons, dpad, 2 shoulder buttons, 2 nubs
###SHOULD: 2 additional shoulder buttons, buttons between nubs
###COULD: x additional action buttons
##cost: well, this should maybe be a poll. (T4b: the keyboard could cost a lot more than CHF9.27 ($10) if it's also considerably better if you ask me)
#software (default key bindings)
##SHOULD: is similar to Pandora's
##SHOULD: is similar to US international qwerty
###SHOULD NOT: break the correlation between a key and its shifted value (e.g. ; and : ) on the US international layout.
##Which keys need to be there?
###MUST: all keys and special characters found on a normal US keyboard layout (0-9,a-z, A-Z, ~!@#$%*()-_=+[{]}\|;:'"`,<.>/?, F1-F12, ESC, Tab, Capslock, shift, ctrl, alt, backspace, enter, insert, delete, home, end, pageup and pagedown.
###COULD: Omits Num Lock, Pause/Break, Print Scr, Sys Req
###MUST: support valid regular keyboard combinations from being input (e.g. shift-delete is a common shortcut in file managers that cannot be input on a Pandora keyboard)
###SHOULD: Characters commonly needed for shell usage ( Tab,;,",`,{},(),$,| ) are accessible using only one thumb (not counting sticky Fn) in combination with a modifier from the shoulder buttons. (Levi)
###SHOULD: German characters: äöüß (ED)
###SHOULD: two shift keys on main keyboard (ED)
###COULD: different keycodes for different versions of the same keys (T4b: "support" should be a given, it's more about the default layout, isn't it? Did I express it better?)
##what to map to the gaming controls?
##MUST: is usable using non-sticky modifiers in both of the handheld/desktop modes of typing. (clarify!) (T4b: I guess this is similar to 2.3.4, the most important characters shouldn't need sticky modifiers to input)
##Mouse emulation:
###MUST: allows mouse motion
###MUST: allows left/right mouse button clicks
###SHOULD: allows middle mouse button clicks (emulation through left mouse + right mouse is acceptable)
###COULD: allow mouse scrolling
##COULD: W-LAN, Bluetooth, etc.

Keyboard/Requirement Analysis Pyra

2014-01-21T00:47:14Z

Levi: Moved 'valid key combinations' to inside 'what keys', clarifying what keys we don't require

Discuss [http://boards.openpandora.org/topic/15403-pyra-keyboard-layout-requirement-analysis/ there].

#hardware
##keyboard:
###MUST: allows for both handheld thumb typing and desktop finger typing
###MUST: is possible to find the keys by touch (for thumb typing)
####surface form: flat? rounded? concave? (T4b: I would like them to be more or less flat and concave a little bit so you feel the different keys better)
####surface height: (T4b: no higher than on current Pandora, preferably almost (only almost!) flush with the rest of the surface)
####MUST: surface coating: non sticky, fingers must glide over it as easily as possible
####MUST: minimum force needed to trigger key: is possible to slide finger over key without triggering it
####SHOULD: possible to easily find central keys (e.g. f and j) by touch (e.g. raised markers)
###MUST: individual keys easy to press
####maximum force needed to trigger key: must not be so big as to make it difficult to press the key (clarified?) (too obvious to include? But I guess we should also include trivial things)
####maximum way/travel needed to trigger key: (T4b: must be low, say 0.3mm, max 0.5mm)
####room between keys: (T4b: I would like to get rid of it completely, but only technically possible if the plastic ribs between the keys aren't necessary anymore)
####size of individual keys:
#####SHOULD: width is as wide if not wider than the Pandora (ED)
#####MUST: height: is no taller than the Pandora (ED)
###MUST NOT: forces Pyra's dimensions to exceed 1-2mm beyond the Pandora's
###MUST: has easy to read labels:
####colors:
####MUST: high enough contrast -> easy to read
###SHOULD (?): backlighting
####MUST: variable intensity (PWM? - Levi)
####COULD: variable color
###is possible to map to (generally as many as possible):
####MUST: qwerty/qwertz/azerty (those are basically the same, so we can group them together)
####MUST: dvorak
####COULD: colemak
####COULD: non latin (Russian, Japanese, etc.) (clarify! what's needed for this?)
###MUST NOT: keyboard gets into the way when gaming
####<practical considerations>
##keyboard '''and''' gaming controls:
###MUST: is resistant to foreign matter (pocket lint) from getting into/between the keys: not possible with the Pandora, could be a problem with mechanical keyboards
##gaming controls:
###NOTE: I think the individual action buttons are fine on the Pandora (T4b)
###MUST: 4 action buttons, dpad, 2 shoulder buttons, 2 nubs
###SHOULD: 2 additional shoulder buttons, buttons between nubs
###COULD: x additional action buttons
##cost: well, this should maybe be a poll. (T4b: the keyboard could cost a lot more than CHF9.27 ($10) if it's also considerably better if you ask me)
#software (default key bindings)
##SHOULD: is similar to Pandora's
##SHOULD: is similar to US international qwerty
###SHOULD NOT: break the correlation between a key and its shifted value (e.g. ; and : ) on the US international layout.
##Which keys need to be there?
###MUST: all keys and special characters found on a normal US keyboard layout (0-9,a-z, A-Z, ~!@#$%*()-_=+[{]}\|;:'"`,<.>/?, F1-F12, ESC, Tab, Capslock, shift, ctrl, alt, backspace, enter, insert, delete, home, end, pageup and pagedown.
###COULD: Omits Num Lock, Pause/Break, Print Scr, Sys Req
###MUST: support valid regular keyboard combinations from being input (e.g. shift-delete is a common shortcut in file managers that cannot be input on a Pandora keyboard)
###SHOULD: Characters commonly needed for shell usage ( Tab,;,",`,{},(),$,| ) are accessible using only one thumb (not counting sticky Fn) in combination with a modifier from the shoulder buttons. (Levi)
###SHOULD: German characters: äöüß (ED)
###SHOULD: two shift keys on main keyboard (ED)
###COULD: different keycodes for different versions of the same keys (T4b: "support" should be a given, it's more about the default layout, isn't it? Did I express it better?)
##what to map to the gaming controls?
##MUST: is usable using non-sticky modifiers in both of the handheld/desktop modes of typing. (clarify!) (T4b: I guess this is similar to 2.3.2, the most important characters shouldn't need sticky modifiers to input)
##Mouse emulation:
###MUST: allows mouse motion
###MUST: allows left/right mouse button clicks
###SHOULD: allows middle mouse button clicks (emulation through left mouse + right mouse is acceptable)
###COULD: allow mouse scrolling
##COULD: W-LAN, Bluetooth, etc.

Keyboard/Requirement Analysis Pyra

2014-01-19T17:35:57Z

Levi: Oops, wrong shell brackets

Discuss [http://boards.openpandora.org/topic/15403-pyra-keyboard-layout-requirement-analysis/ there].

#hardware
##keyboard:
###MUST: allows for both handheld thumb typing and desktop finger typing
###MUST: is possible to find the keys by touch (for thumb typing)
####surface form: flat? rounded? concave? (T4b: I would like them to be more or less flat and concave a little bit so you feel the different keys better)
####surface height: (T4b: no higher than on current Pandora, preferably almost (only almost!) flush with the rest of the surface)
####MUST: surface coating: non sticky, fingers must glide over it as easily as possible
####MUST: minimum force needed to trigger key: is possible to slide finger over key without triggering it
####SHOULD: possible to easily find central keys (e.g. f and j) by touch (e.g. raised markers)
###MUST: individual keys easy to press
####maximum force needed to trigger key: must not be so big as to make it difficult to press the key (clarified?) (too obvious to include? But I guess we should also include trivial things)
####maximum way/travel needed to trigger key: (T4b: must be low, say 0.3mm, max 0.5mm)
####room between keys: (T4b: I would like to get rid of it completely, but only technically possible if the plastic ribs between the keys aren't necessary anymore)
####size of individual keys:
#####SHOULD: width is as wide if not wider than the Pandora (ED)
#####MUST: height: is no taller than the Pandora (ED)
###MUST NOT: forces Pyra's dimensions to exceed 1-2mm beyond the Pandora's
###MUST: has easy to read labels:
####colors:
####MUST: high enough contrast -> easy to read
###SHOULD (?): backlighting
####MUST: variable intensity (PWM? - Levi)
####COULD: variable color
###is possible to map to (generally as many as possible):
####MUST: qwerty/qwertz/azerty (those are basically the same, so we can group them together)
####MUST: dvorak
####COULD: colemak
####COULD: non latin (Russian, Japanese, etc.) (clarify! what's needed for this?)
###MUST NOT: keyboard gets into the way when gaming
####<practical considerations>
##keyboard '''and''' gaming controls:
###MUST: is resistant to foreign matter (pocket lint) from getting into/between the keys: not possible with the Pandora, could be a problem with mechanical keyboards
##gaming controls:
###NOTE: I think the individual action buttons are fine on the Pandora (T4b)
###MUST: 4 action buttons, dpad, 2 shoulder buttons, 2 nubs
###SHOULD: 2 additional shoulder buttons, buttons between nubs
###COULD: x additional action buttons
##cost: well, this should maybe be a poll. (T4b: the keyboard could cost a lot more than CHF9.27 ($10) if it's also considerably better if you ask me)
#software (default key bindings)
##SHOULD: is similar to Pandora's
##SHOULD: is similar to US international qwerty
###SHOULD NOT: break the correlation between a key and its shifted value (e.g. ; and : ) on the US international layout.
##Which keys need to be there?
###MUST: all keys and special characters found on a normal US keyboard layout (0-9,a-z, A-Z, ~!@#$%*()-_=+[{]}\|;:'",<.>/?, F1-F12, ESC, Tab, Capslock, shift, ctrl, alt, backspace, enter, insert, delete, home, end, pageup and pagedown.
###SHOULD: Characters commonly needed for shell usage ( Tab,;,",`,{},(),$,| ) are accessible using only one thumb (not counting sticky Fn) in combination with a modifier from the shoulder buttons. (Levi)
###SHOULD: German characters: äöüß (ED)
###SHOULD: two shift keys on main keyboard (ED)
###COULD: different keycodes for different versions of the same keys (T4b: "support" should be a given, it's more about the default layout, isn't it? Did I express it better?)
##what to map to the gaming controls?
##MUST: is usable using non-sticky modifiers in both of the handheld/desktop modes of typing. (clarify!) (T4b: I guess this is similar to 2.3.2, the most important characters shouldn't need sticky modifiers to input)
##MUST NOT: prevents valid regular keyboard combinations from being input (e.g. shift-backspace on the Pandora) (T4b: What's that about again?)
##Mouse emulation:
###MUST: allows mouse motion
###MUST: allows left/right mouse button clicks
###SHOULD: allows middle mouse button clicks (emulation through left mouse + right mouse is acceptable)
###COULD: allow mouse scrolling
##COULD: W-LAN, Bluetooth, etc.

Mupen2.0 Compatibility List

2013-11-14T09:19:53Z

Levi: Update version

Mupen64Plus 2.0 is a Nintendo 64 emulator ported on Pandora by PtitSeb. Other versions exist (Android, Windows, Mac, Linux...).

Current version is 2.0.0.10 from Nov 5th 2013.

==Adding to the Compatibility List==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. You may also add specific conditions you specified in the settings if they differ from the defaults. As for the SGX driver, please write "default" if you did not change your driver vs what was in the firmware.

Don't post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new Mupen2.0 version, update the entry and add that to notes.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by PtitSeb about further debugging your problems.

==The Compatibility List==


You can sort the columns by clicking the table header (javascript required).

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game Name and Region
! Mupen Version
! Used Plugin
! Pandora Model[1]
! SGX driver
! SZ version

! Frequency
! Notes on Settings
! Status

|- style="background: #F7BE81"
|[http://www.mobygames.com/game/n64/donkey-kong-64 Donkey Kong 64 (unknown)]
|2.0.0.10
! GLES2N64
|1GHz
|4.03.02
|1.55
|1000 MHz
|Minor geometry glitches, a stuttering camera and significant motion clipping failures make it hard to do anything in this game. Runs close to 100% speed with the GLES2N64 plugin - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Orange

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/dr-mario-64 Dr Mario (US?)]
|2.0.0.07
! Glide GLES2
|Rebirth
|Default
|1.54
|995 MHz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable.
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/f1-pole-position-64 F-1 Pole Position 64]
|2.0.0.07
! Rice GLES2
|Rebirth
|Default
|1.54
|995 MHz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable. Barely. A Higher Clockspeed might help.
|Yellow

|- style="background: #90FF90"
|[http://www.mobygames.com/game/f-zero-x F-Zero X (EU)]
|2.0.0.09
! Rice GLES2
|1 GHz
|4.03.02
|1.55
|1000 MHz
|GLES2N64 video plugin also works well, with slightly more texture wobbles. Needs updated SGX driver to display times correctly. The game is almost full speed all the time (while the slow-downs are mainly in-menu). Very playable - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Green

|- style="background: #90FF90"
|[http://www.mobygames.com/game/n64/quest-64 Holy Magic Century (EU)] (aka Quest64)
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 MHz
|Speed and visual are fine
|Green

|- style="background: #90FF90"
|[http://www.mobygames.com/game/mario-kart-64 Mario Kart 64]
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 MHz
|Runs very well, with default settings
|Green

|- style="background: #F7BE81"
|[http://www.mobygames.com/game/mario-tennis Mario Tennis (EU)]
|2.0.0.10
! Arachnoid
|1GHz
|4.03.02
|1.55
|1.0GHz
|'''Glide''': Slows to a stall then crashes; '''GLES2N64''': Transparency issues, missing characters; '''Rice GLES 1.1/2''': Freezes prior to match; '''Arachnoid''': Slow with many glitches. Almost playable tho. - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Orange

|- style="background: #90FF90"
|[http://www.mobygames.com/game/super-mario-64 Super Mario 64 (EU)]
|2.0.0.10
! Rice GLES1.1
|1GHz
|4.03.02
|1.55
|1000 MHz
|Runs well.
|Green

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/starcraft-64- StarCraft 64 (EU)]
|2.0.0.9
! Rice GLES2
|1GHz
|4.03.02
|1.55
|1000 MHz
|Runs well in-game. Many screen-clear glitches and slowdown in 2d menus - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Yellow

|}
===Notes===

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM@166MHz
* Rebirth - OMAP3530 SoC@600MHz stock, '''512MiB RAM'''@166MHz
* 1GHz - '''DM3730 SoC@1GHz stock''', 512MiB RAM@'''200Mhz'''

Mupen2.0 Compatibility List

2013-11-14T09:18:41Z

Levi: /* The Compatibility List */ Add Mario Tennis

Mupen64Plus 2.0 is a Nintendo 64 emulator ported on Pandora by PtitSeb. Other versions exist (Android, Windows, Mac, Linux...).

Current version is 2.0.0.5 from Oct 15th 2013.

==Adding to the Compatibility List==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. You may also add specific conditions you specified in the settings if they differ from the defaults. As for the SGX driver, please write "default" if you did not change your driver vs what was in the firmware.

Don't post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new Mupen2.0 version, update the entry and add that to notes.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by PtitSeb about further debugging your problems.

==The Compatibility List==


You can sort the columns by clicking the table header (javascript required).

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game Name and Region
! Mupen Version
! Used Plugin
! Pandora Model[1]
! SGX driver
! SZ version

! Frequency
! Notes on Settings
! Status

|- style="background: #F7BE81"
|[http://www.mobygames.com/game/n64/donkey-kong-64 Donkey Kong 64 (unknown)]
|2.0.0.10
! GLES2N64
|1GHz
|4.03.02
|1.55
|1000 MHz
|Minor geometry glitches, a stuttering camera and significant motion clipping failures make it hard to do anything in this game. Runs close to 100% speed with the GLES2N64 plugin - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Orange

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/dr-mario-64 Dr Mario (US?)]
|2.0.0.07
! Glide GLES2
|Rebirth
|Default
|1.54
|995 MHz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable.
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/f1-pole-position-64 F-1 Pole Position 64]
|2.0.0.07
! Rice GLES2
|Rebirth
|Default
|1.54
|995 MHz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable. Barely. A Higher Clockspeed might help.
|Yellow

|- style="background: #90FF90"
|[http://www.mobygames.com/game/f-zero-x F-Zero X (EU)]
|2.0.0.09
! Rice GLES2
|1 GHz
|4.03.02
|1.55
|1000 MHz
|GLES2N64 video plugin also works well, with slightly more texture wobbles. Needs updated SGX driver to display times correctly. The game is almost full speed all the time (while the slow-downs are mainly in-menu). Very playable - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Green

|- style="background: #90FF90"
|[http://www.mobygames.com/game/n64/quest-64 Holy Magic Century (EU)] (aka Quest64)
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 MHz
|Speed and visual are fine
|Green

|- style="background: #90FF90"
|[http://www.mobygames.com/game/mario-kart-64 Mario Kart 64]
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 MHz
|Runs very well, with default settings
|Green

|- style="background: #F7BE81"
|[http://www.mobygames.com/game/mario-tennis Mario Tennis (EU)]
|2.0.0.10
! Arachnoid
|1GHz
|4.03.02
|1.55
|1.0GHz
|'''Glide''': Slows to a stall then crashes; '''GLES2N64''': Transparency issues, missing characters; '''Rice GLES 1.1/2''': Freezes prior to match; '''Arachnoid''': Slow with many glitches. Almost playable tho. - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Orange

|- style="background: #90FF90"
|[http://www.mobygames.com/game/super-mario-64 Super Mario 64 (EU)]
|2.0.0.10
! Rice GLES1.1
|1GHz
|4.03.02
|1.55
|1000 MHz
|Runs well.
|Green

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/starcraft-64- StarCraft 64 (EU)]
|2.0.0.9
! Rice GLES2
|1GHz
|4.03.02
|1.55
|1000 MHz
|Runs well in-game. Many screen-clear glitches and slowdown in 2d menus - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Yellow

|}
===Notes===

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM@166MHz
* Rebirth - OMAP3530 SoC@600MHz stock, '''512MiB RAM'''@166MHz
* 1GHz - '''DM3730 SoC@1GHz stock''', 512MiB RAM@'''200Mhz'''

Mupen2.0 Compatibility List

2013-11-06T03:52:49Z

Levi: /* The Compatibility List */ SM64

Mupen64Plus 2.0 is a Nintendo 64 emulator ported on Pandora by PtitSeb. Other versions exist (Android, Windows, Mac, Linux...).

Current version is 2.0.0.5 from Oct 15th 2013.

==Adding to the Compatibility List==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. You may also add specific conditions you specified in the settings if they differ from the defaults. As for the SGX driver, please write "default" if you did not change your driver vs what was in the firmware.

Don't post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new Mupen2.0 version, update the entry and add that to notes.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by PtitSeb about further debugging your problems.

==The Compatibility List==


You can sort the columns by clicking the table header (javascript required).

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game Name and Region
! Mupen Version
! Used Plugin
! Pandora Model[1]
! SGX driver
! SZ version

! Frequency
! Notes on Settings
! Status

|- style="background: #F7BE81"
|[http://www.mobygames.com/game/n64/donkey-kong-64 Donkey Kong 64 (unknown)]
|2.0.0.10
! GLES2N64
|1GHz
|4.03.02
|1.55
|1000 Mhz
|Minor geometry glitches, a stuttering camera and significant motion clipping failures make it hard to do anything in this game. Runs close to 100% speed with the GLES2N64 plugin - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Orange

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/dr-mario-64 Dr Mario (US?)]
|2.0.0.07
! Glide GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable.
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/f1-pole-position-64 F-1 Pole Position 64]
|2.0.0.07
! Rice GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable. Barely. A Higher Clockspeed might help.
|Yellow

|- style="background: #90FF90"
|[http://www.mobygames.com/game/f-zero-x F-Zero X (EU)]
|2.0.0.09
! Rice GLES2
|1 Ghz
|4.03.02
|1.55
|1000 Mhz
|GLES2N64 video plugin also works well, with slightly more texture wobbles. Needs updated SGX driver to display times correctly. The game is almost full speed all the time (while the slow-downs are mainly in-menu). Very playable - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Green

|- style="background: #90FF90"
|[http://www.mobygames.com/game/n64/quest-64 Holy Magic Century (EU)] (aka Quest64)
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 Mhz
|Speed and visual are fine
|Green

|- style="background: #90FF90"
|[http://www.mobygames.com/game/super-mario-64 Super Mario 64 (EU)]
|2.0.0.10
! Rice GLES1.1
|1GHz
|4.03.02
|1.55
|1000 Mhz
|Runs well.
|Green

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/starcraft-64- StarCraft 64 (unknown)]
|2.0.0.9
! Rice GLES2
|1Ghz
|4.03.02
|1.55
|1000 Mhz
|Runs well in-game. Many screen-clear glitches and slowdown in 2d menus - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Yellow

|- style="background: #90FF90"
|[http://www.mobygames.com/game/mario-kart-64 Mario Kart 64]
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 Mhz
|Runs very well, with default settings
|Green

|}
===Notes===

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM@166MHz
* Rebirth - OMAP3530 SoC@600MHz stock, '''512MiB RAM'''@166MHz
* 1GHz - '''DM3730 SoC@1GHz stock''', 512MiB RAM@'''200Mhz'''

Mupen2.0 Compatibility List

2013-11-06T03:37:23Z

Levi: /* The Compatibility List */ Tidy up - sorting, adding links

Mupen64Plus 2.0 is a Nintendo 64 emulator ported on Pandora by PtitSeb. Other versions exist (Android, Windows, Mac, Linux...).

Current version is 2.0.0.5 from Oct 15th 2013.

==Adding to the Compatibility List==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. You may also add specific conditions you specified in the settings if they differ from the defaults. As for the SGX driver, please write "default" if you did not change your driver vs what was in the firmware.

Don't post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new Mupen2.0 version, update the entry and add that to notes.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by PtitSeb about further debugging your problems.

==The Compatibility List==


You can sort the columns by clicking the table header (javascript required).

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game Name and Region
! Mupen Version
! Used Plugin
! Pandora Model[1]
! SGX driver
! SZ version

! Frequency
! Notes on Settings
! Status

|- style="background: #F7BE81"
|[http://www.mobygames.com/game/n64/donkey-kong-64 Donkey Kong 64 (unknown)]
|2.0.0.10
! GLES2N64
|1GHz
|4.03.02
|1.55
|1000 Mhz
|Minor geometry glitches, a stuttering camera and significant motion clipping failures make it hard to do anything in this game. Runs close to 100% speed with the GLES2N64 plugin - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Orange

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/dr-mario-64 Dr Mario (US?)]
|2.0.0.07
! Glide GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable.
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/f1-pole-position-64 F-1 Pole Position 64]
|2.0.0.07
! Rice GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable. Barely. A Higher Clockspeed might help.
|Yellow

|- style="background: #90FF90"
|[http://www.mobygames.com/game/f-zero-x F-Zero X (EU)]
|2.0.0.09
! Rice GLES2
|1 Ghz
|4.03.02
|1.55
|1000 Mhz
|GLES2N64 video plugin also works well, with slightly more texture wobbles. Needs updated SGX driver to display times correctly. The game is almost full speed all the time (while the slow-downs are mainly in-menu). Very playable - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Green

|- style="background: #90FF90"
|[http://www.mobygames.com/game/n64/quest-64 Holy Magic Century (EU)] (aka Quest64)
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 Mhz
|Speed and visual are fine
|Green

|- style="background: #90FF90"
|[http://www.mobygames.com/game/super-mario-64 Super Mario 64 (EU)]
|2.0.0.05
! Rice Plugin
|1GHz
|4.03.02
|1.54
|1000 Mhz
|Runs very well. Some cases of sound stuttering and slowdown but otherwise almost perfect.
|Green

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/starcraft-64- StarCraft 64 (unknown)]
|2.0.0.9
! Rice GLES2
|1Ghz
|4.03.02
|1.55
|1000 Mhz
|Runs well in-game. Many screen-clear glitches and slowdown in 2d menus - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Yellow

|- style="background: #90FF90"
|[http://www.mobygames.com/game/mario-kart-64 Mario Kart 64]
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 Mhz
|Runs very well, with default settings
|Green

|}
===Notes===

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM@166MHz
* Rebirth - OMAP3530 SoC@600MHz stock, '''512MiB RAM'''@166MHz
* 1GHz - '''DM3730 SoC@1GHz stock''', 512MiB RAM@'''200Mhz'''

Mupen2.0 Compatibility List

2013-11-06T03:28:09Z

Levi: /* The Compatibility List */ DK64

Mupen64Plus 2.0 is a Nintendo 64 emulator ported on Pandora by PtitSeb. Other versions exist (Android, Windows, Mac, Linux...).

Current version is 2.0.0.5 from Oct 15th 2013.

==Adding to the Compatibility List==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. You may also add specific conditions you specified in the settings if they differ from the defaults. As for the SGX driver, please write "default" if you did not change your driver vs what was in the firmware.

Don't post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new Mupen2.0 version, update the entry and add that to notes.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by PtitSeb about further debugging your problems.

==The Compatibility List==


You can sort the columns by clicking the table header (javascript required).

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game Name and Region
! Mupen Version
! Used Plugin
! Pandora Model[1]
! SGX driver
! SZ version

! Frequency
! Notes on Settings
! Status

|- style="background: #F7BE81"
|[http://www.mobygames.com/game/n64/donkey-kong-64 Donkey Kong 64 (unknown)]
|2.0.0.10
! GLES2N64
|1GHz
|4.03.02
|1.55
|1000 Mhz
|Minor geometry glitches, a stuttering camera and significant motion clipping failures make it hard to do anything in this game. Runs close to 100% speed with the GLES2N64 plugin.
|Orange

|- style="background: #90FF90"
|[http://www.mobygames.com/game/super-mario-64 Super Mario 64 (EU)]
|2.0.0.05
! Rice Plugin
|1GHz
|4.03.02
|1.54
|1000 Mhz
|Runs very well. Some cases of sound stuttering and slowdown but otherwise almost perfect.
|Green

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/starcraft-64- StarCraft 64 (unknown)]
|2.0.0.9
! Rice GLES2
|1Ghz
|4.03.02
|1.55
|1000 Mhz
|Runs well in-game. Many screen-clear glitches in 2d menus, and slowdown - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/dr-mario-64 Dr Mario (US?)]
|2.0.0.07
! Glide GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable.
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/f1-pole-position-64 F-1 Pole Position 64]
|2.0.0.07
! Rice GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable. Barely. A Higher Clockspeed might help.
|Yellow

|- style="background: #90FF90"
|[http://www.mobygames.com/game/f-zero-x F-Zero X (EU)]
|2.0.0.09
! Rice GLES2
|1 Ghz
|4.03.02
|1.55
|1000 Mhz
|GLES2N64 video plugin also works well, with slightly more texture wobbles. Needs updated SGX driver to display times correctly. The game is almost full speed all the time (while the slow-downs are mainly in-menu). Very playable - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Green

|- style="background: #90FF90"
|Mario Kart 64
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 Mhz
|Runs very well, with default settings
|Green

|- style="background: #90FF90"
|Holy Magic Century
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 Mhz
|Speed and visual are fine
|Green

|}
===Notes===

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM@166MHz
* Rebirth - OMAP3530 SoC@600MHz stock, '''512MiB RAM'''@166MHz
* 1GHz - '''DM3730 SoC@1GHz stock''', 512MiB RAM@'''200Mhz'''

DraStic Compatibility List

2013-11-04T19:16:58Z

Levi: /* Notes */

DraStic is a Nintendo DS Emulator created by Exophase for ARM devices such as the OpenPandora.

* [http://repo.openpandora.org/?page=detail&app=DraStic Download]
* [http://exophase.devzero.co.uk/drastic_readme.txt Readme and Changelog]
* [http://boards.openpandora.org/index.php/topic/12038-emulator-drastic-nintendo-ds/page-1 Forum Thread]

The current version on the Repo is 2.1.6.1, released on Sept. 17th, 2013. It identifies itself as "Version r2.1.6.1p" on the menu screen.

* [http://pandorawiki.org/DraStic_Compatibility_List_1.x Outdated Previous 1.x Version Compatibility List]

==Compatibility==
''128MB+ zipped games have issues on CC Pandoras because of limited RAM. 256MB zipped games may work on 512MB systems such as the Rebirth or 1GHz Pandora. 512MB zipped games are not expected to run on any system. Unzipped games of any size are not dependent on RAM, so should work the same on all systems.　Note that wifi is not emulated or faked so far, so it may lead to compatibility issues/crashes.''

==Adding to the list==
Note: you can use the [http://repo.openpandora.org/?page=detail&app=drasticwikihelper-PowerGod Drastic Wiki Helper] application from the repo to automatically generate appropriate text to paste in the compatibility list below.

Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. Include the unzipped ROM size in base-2 mebibytes (16MB, 64MB, 128MB, etc.). If available please indicate the game ID figure, too. The Game ID figure should be 8 characters long and can usually be found by pressing Y on the rom selection menu.

'''Don't''' post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new DraStic version, update the entry and add that to notes. Please don't copy entries from the old list into this one unless you first re-test the game using a recent version of DraStic and update the color and notes as required.

Default frameskip for version 2.0.1p is automatic and 4. Please record a comment if you use a different setting.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by Exophase about further debugging your problems.

==The Compatibility List==


You can sort the colums by clicking the table header (javascript required).

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game ID
! Game Name
! DraStic Version
! ROM Size
! Pandora Model[1]

! Frequency
! Notes
! Status

|- style="background: #90FF90"
|454d5341
|Super Mario 64 DS
|r2.1.0p
|16MiB
|1GHz
|900MHz
|Minimal graphical tears; almost none; other than that seems to plays perfectly. :(knightron)
|Green

|- style="background: #90FF90"
|454c4759
|Geometry Wars - Galaxies
|r2.1.3p
|64MiB
|1Ghz
|1000Mhz
|Works very well. (ekianjo)
| Green

|- style="background: #F3F781"
|55595241
|Rayman DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Very choppy sound often, and frameskip choppyness too. :(knightron)
|Yellow

|- style="background: #90FF90"
|50445441
|42 All Time Classics/Clubhouse Games (E)
|r2.1.0p
|16MiB
|1GHz
|900MHz
|Plays fine with frameskip 2
|Green

|- style="background: #90FF90"
|45575941
|Yoshis Island DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45474443
|Disgaea DS (U)
|r2.1.3p
|64MiB
|1Ghz
|1000Mhz
|runs very well overall. No issue detected. (ekianjo)
| Green

|- style="background: #F3F781"
|50425341
|Snowboard Kids
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Runs at full speed but has constant choppy sound during races. :(Knightron)
|Yellow

|- style="background: #90FF90"
|45455341
|Children of Mana
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45555159
|Chrono Trigger
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Seems to run perfect. I did not play long enough to test cut scenes. :(Knightron)
|Green

|- style="background: #90FF90"
|45445741
|Diddy Kong Racing DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|A couple of graphical bugs in a few places, but seems close to perfect. :(Knightron)
|Green

|- style="background: #90FF90"
|4a554a41
|Jump Ultimate Stars (English patched)
|r2.1.0p
|62.9MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F3F781"
|45475049
|Pokemon SoulSilver
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Slight graphical tearing. Lags a little when entering buildings ect. Other than that, it seems very playable. :(Knightron)
|Yellow

|- style="background: #90FF90"
|45484d41
|Metroid Prime Hunters
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems close to perfect. Full speed most of the time, but when lots of enemies are fireing at you, it slows down a little. May encounter bigger issues further into the game. :(Knightron)
|Green

|- style="background: #90FF90"
|45524341
|Sprung The Dating Game
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F7BE81"
|454a4c43
|Mario and Luigi Bowsers Inside Story
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays pretty close to perfect, but freezes during the first fight, while playing as Bowser. :(knightron)
|Orange

|- style="background: #90FF90"
|45355659
|Dragon Quest V Hand of the Heavenly Bride
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Seems to play close to perfectly, very slight choppy inconsistancy between two screens, but not as bad as DQIV. :(Knightron)
|Green

|- style="background: #90FF90"
|45425742
|Plants vs Zombies
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|454b5441
|Kirby Canvas Curse
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|4a534259
|Soma Bringer (English patched)
|r2.1.0p
|122MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45564959
|Dragon Quest IV Chapters of the Chosen
|r2.1.0p
|128MiB
|1GHz
|900MHz
|It can apear a little choppy when playing with vertical screens, but still plays very well: I switch it to one screen mode. :(Knightron)
|Green

|- style="background: #90FF90"
|45464641
|Final Fantasy III
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays pretty damn close to perfect. :(Knightron)
|Green

|- style="background: #F3F781"
|45344659
|Final Fantasy IV
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays at full speed, but has choppy sound quite often. :(Knightron)
|Yellow

|- style="background: #F7BE81"
|4a545941
|Tales Of Innocence (English Patched)
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays at full speed, but there are major graphical issues that make the game very hard to follow. :(Knightron)
|Orange

|- style="background: #90FF90"
|454b5341
|Lost in Blue
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Plays almost perfectly, just a few very minor graphical and sound bugs in a few spots. Microphone fails sometimes but works again once Drastic is restarted. Game crashes occasionally when atempting to light the fire or build something. At the moment, I recommend regular saving through savestates just in case. :(Knightron)
|Green

|- style="background: #F78181"
|45514459
|Dragon Quest IX Sentinels of the Starry Skies
|r2.1.0p
|22.3MiB
|1GHz
|900MHz
|Game crashes on boot. :(Knightron)
|Red

|- style="background: #90FF90"
|454d5241
|Mario and Luigi Partners in Time
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45495941
|Yoshi Touch & Go
|r2.1.0p
|16MiB
|1GHz
|900MHz
|This Game Apears to play perfectly, but it has major problems when the Pandora is put to sleep. :(Knightron)
|Green

|- style="background: #90FF90"
|454b5342
|9 Hours, 9 Persons, 9 Doors
|r2.0.1p
|128MiB
|Rebirth
|850
|Plays at full speed.
|Green

|- style="background: #90FF90"
|45574b59
|Kirby - Super Star Ultra
|r2.0.1p
|128MiB
|CC
|800
|Plays at full speed.
|Green

|- style="background: #90FF90"
|45365359
|Civilization Revolution DS
|r2.0.1p
|64MiB
|Rebirth
|825MHz
|Fully playable. (Long firststart ~62sec.)
|Green

|- style="background: #90FF90"
|45365359
|Barnyard Blast: Swine of the Night
|r2.0.1p
|8MiB
|1GHz
|1.1GHz
|Works Completely fine. No Lag or Graphical Issues even on cut scenes
|Green

|- style="background: #90FF90"
|45454650
|Fire Emblem: Shadow Dragon (E)
|r2.1.3p
|64MiB
|1GHz
|900MHz
|Runs fine since r2.1.3p
|Green

|- style="background: #90FF90"
|4a564942
|Ivy the Kiwi (J)
|r2.1.3p
|8MiB
|1GHz
|900MHz
|Runs fine since r2.1.0p. Doesn't even need frameskip at 900Mhz.
|Green

|- style="background: #90FF90"
|50505841
|Picross DS (E)
|r2.1.3p
|32MiB
|1GHz
|600MHz
|Very minor graphical glitch where at end of level the top screen image transitions from monochrome to (animated) colour - one pixel line of monochrome image is left above the animated image.
|Green

|- style="background: #90FF90"
|50503643
|Picross 3D (E)
|r2.1.3p
|32MiB
|1GHz
|600MHz
|Absolutely perfect since version r2.1.0p
|Green

|- style="background: #F3F781"
|50344759
|Suikoden Tierkreis
|r2.0.1p
|256MiB
|Rebirth
|900MHz
|Sound sometimes a bit laggy during battle. (tested for 40min only)
|Yellow

|- style="background: #90FF90"
|45375341
|Summon Night, Twin Age
|r2.0.1p
|128MiB
|Rebirth
|900MHz
|nice. (tested for 10h)
|Green

|- style="background: #F3F781"
|404c5741
|The World Ends With You (E)
|r2.0.1p
|128MiB
|Rebirth
|900MHz
|Ran fine as far as the end of the first day. (not further tested.)
|Yellow

|- style="background: #90FF90"
|45434d41
|MarioKart DS (US)
|r2.1.3p
|32MiB
|1GHz
|1050MHz
|Runs fine with frameskip
|Green

|- style="background: #90FF90"
|45444e41
|Brain Age - Train Your Brain in Minutes a Day! (v01)
|r2.1.0p
|16MiB
|1Ghz
|800 Mhz
|Works great. (PowerGod)
|Green

|- style="background: #90FF90"
|50444e41
|Dr Kawashima's Brain Training - How Old Is Your Brain
|r2.1.0p
|16MiB
|1Ghz
|800 Mhz
|Works great. (PowerGod)
|Green

|- style="background: #F3F781"
|455a4443
|Dragon Ball - Origins
|r2.1.6.1p
|64MiB
|1Ghz
|800 Mhz
|Playable with some lag. (PowerGod)
|Yellow

|- style="background: #90FF90"
|45503743
|Peggle Dual Shot
|r2.1.3p
|64MiB
|1Ghz
|750MHz
|Perfect play, fluid motion, just like the real thing. :(kumaki+levi)
|Green

|- style="background: #F3F781"
|45533241
|Dragon Ball Z - Supersonic Warriors 2
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|Playable with some lag. (PowerGod)
|Yellow

|- style="background: #F3F781"
|45414441
|Pokemon Diamond Version (v13)
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|No text in the introduction tutorial. Only played it a bit. (PowerGod)
(Edit by knightron: text is now played in DraStic 2.1.0p)
|Yellow

|- style="background: #90FF90"
|45433643
|Infinite Space
|r2.1.3p
|256MiB
|1Ghz
|1050Mhz
|Plays well. Graphical glitches in the attract mode. Played only as far as the first spaceport. (levi)
|Green
|- style="background: #90FF90"
|50385243
|Crash - Mind Over Mutant (U)
|r2.1.3p
|64MiB
|CC
|800Mhz
|works perfect at default (dsleaf67)
| Green

|- style="background: #90FF90"
|50595943
|Giana Sisters DS (U)
|r2.1.3p
|8MiB
|CC
|800Mhz
|works perfect (dsleaf67)
| Green

|- style="background: #F3F781"
|50595943
|Giana Sisters DS (E)
|r2.1.6.1p
|8MiB
|1Ghz
|800Mhz
|Playable, but there are issues with the microphone in later levels and it should be disabled (to use the jump button instead) in order to use the bubble. UPDATE: actually seems something related more to the DraStic session than to the game itself, because when the issue happened I made a savestate, and even reloading it had the same issue, but after restarting DraStic that savestate is working right (PowerGod)
| Yellow

|- style="background: #90FF90"
|45563241
|M&M's - Break'em (U)
|r2.1.3p
|8MiB
|CC
|800Mhz
|works great only has minor sound issue at start (dsleaf67)
| Green

|- style="background: #90FF90"
|45575041
|Pac-Man World 3 (U)
|r2.1.3p
|32MiB
|CC
|800Mhz
|works good some slowdowns but very playable (dsleaf67)
| Green
|- style="background: #F3F781"
|454a5141
|Crash of the Titans (U)
|r2.1.3p
|128MiB
|CC
|800Mhz
|playable with choppy sound and some slow downs (dsleaf67)
| Yellow

|- style="background: #F3F781"
|50394643
|FIFA 09 (U)
|r2.1.3p
|32MiB
|CC
|800Mhz
|playable with sound issues (dsleaf67)
| Yellow

|- style="background: #90FF90"
|45413541
|Golden Compass, The (U)
|r2.1.3p
|64MiB
|CC
|800Mhz
|works good minor sound issues (dsleaf67)
| Green

|- style="background: #90FF90"
|45424a59
|LEGO Batman - The Videogame (U)
|r2.1.3p
|64MiB
|CC
|800Mhz
|works great (dsleaf67)
| Green

|- style="background: #F7BE81"
|50494b42
|Legend of Zelda - Spirit Tracks, The (E)
|r2.1.6.1p
|128MiB
|1Ghz
|1100Mhz
|when you're supposed to use the microphone to blow in the flute it doesn't work. (frostfall)
| Orange

|- style="background: #F3F781"
|45343243
|Phantasy Star 0
|r2.1.6.1p
|128MiB
|Rebirth
|600Mhz
|Nice gameplay, but the sound with some problem, 80~90% in battle. The game crash if you are using saves state and try to feed the MAG, if you use normal save and reset the game work fine. (MarTinazzI)
| Yellow

|- style="background: #90FF90"
|454d3341
|Dynasty Warriors DS - Fighter's Battle (E)
|r2.1.6.1p
|128MiB
|Rebirth
|600Mhz
| (MarTinazzI)
| Green

|- style="background: #90FF90"
|454d4241
|Bomberman (E)
|r2.1.6.1p
|8MiB
|Rebirth
|600Mhz
| (MarTinazzI)
| Green

|- style="background: #90FF90"
|504e4241
|Bomberman Story DS (U)
|r2.1.6.1p
|128MiB
|Rebirth
|600Mhz
| (MarTinazzI)
| Green

|- style="background: #90FF90"
|45584241
|Bomberman Land Touch!
|r2.1.6.1p
|32MiB
|Rebirth
|600Mhz
| (MarTinazzI)
| Green

|- style="background: #90FF90"
|45324259
|Bomberman Land Touch! 2
|r2.1.6.1p
|32MiB
|Rebirth
|600Mhz
| (MarTinazzI)
| Green

|- style="background: #F3F781"
|45435741
|Drone Tactics (U)
|r2.1.6.1p
|64MiB
|Rebirth
|600Mhz
|Only in battle scene run about 70~90% (MarTinazzI)
| Yellow

|- style="background: #90FF90"
|454a5841
|Dungeon Explorer - Warriors of Ancient Arts (U)
|r2.1.6.1p
|64MiB
|Rebirth
|600Mhz
| (MarTinazzI)
| Green

|- style="background: #F3F781"
|45474b59
|Kingdom Hearts - 358-2 Days
|r2.1.6.1p
|256MiB
|Rebirth
|600Mhz
|Run 75~90% and bad sound, but playable (MarTinazzI)
| Yellow

|- style="background: #90FF90"
|45574b59
|Kirby - Super Star Ultra (U)
|r2.1.6.1p
|128MiB
|Rebirth
|600Mhz
| (MarTinazzI)
| Green

|- style="background: #F3F781"
|454e4c41
|Lunar - Dragon Song (U)
|r2.1.6.1p
|32MiB
|Rebirth
|600Mhz
|Some lag on action select in battle, 70~90% but in far of the game seem all 100%, need test early game again. (MarTinazzI)
| Yellow

|- style="background: #F78181"
|45555043
|Pokemon - Platinum Version (v10) (U)
|r2.1.6.1p
|128MiB
|Rebirth
|600Mhz
|bug on introduction. blinking screen and game stop (MarTinazzI)
| Red

|- style="background: #F78181"
|4f415249
|Pokemon - White Version (DSi Enhanced)(USA) (U)
|r2.1.6.1p
|256MiB
|Rebirth
|600Mhz
|just close the game on introduction (MarTinazzI)
| Red

|- style="background: #F78181"
|454c4859
|Time Hollow (U)
|r2.1.6.1p
|128MiB
|1Ghz
|975Mhz
|Game crashes at the beginning of Chapter 2, also ingame saves doesn't work at all (PowerGod)
| Red

|}


===Notes===

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM@166MHz
* Rebirth - OMAP3530 SoC@600MHz stock, '''512MiB RAM'''@166MHz
* 1GHz - '''DM3730 SoC@1GHz stock''', 512MiB RAM@'''200Mhz'''

[[Category:Emulators]]
[[Category: Compatibility]]
[[Category:List]]

Mupen2.0 Compatibility List

2013-11-04T19:16:26Z

Levi: /* Notes */

Mupen64Plus 2.0 is a Nintendo 64 emulator ported on Pandora by PtitSeb. Other versions exist (Android, Windows, Mac, Linux...).

Current version is 2.0.0.5 from Oct 15th 2013.

==Adding to the Compatibility List==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. You may also add specific conditions you specified in the settings if they differ from the defaults. As for the SGX driver, please write "default" if you did not change your driver vs what was in the firmware.

Don't post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new Mupen2.0 version, update the entry and add that to notes.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by PtitSeb about further debugging your problems.

==The Compatibility List==


You can sort the columns by clicking the table header (javascript required).

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game Name and Region
! Mupen Version
! Used Plugin
! Pandora Model[1]
! SGX driver
! SZ version

! Frequency
! Notes on Settings
! Status

|- style="background: #90FF90"
|[http://www.mobygames.com/game/super-mario-64 Super Mario 64 (EU)]
|2.0.0.05
! Rice Plugin
|1GHz
|4.03.02
|1.54
|1000 Mhz
|Runs very well. Some cases of sound stuttering and slowdown but otherwise almost perfect.
|Green

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/starcraft-64- StarCraft 64 (unknown)]
|2.0.0.9
! Rice GLES2
|1Ghz
|4.03.02
|1.55
|1000 Mhz
|Runs well in-game. Many screen-clear glitches in 2d menus, and slowdown - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/dr-mario-64 Dr Mario (US?)]
|2.0.0.07
! Glide GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable.
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/f1-pole-position-64 F-1 Pole Position 64]
|2.0.0.07
! Rice GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable. Barely. A Higher Clockspeed might help.
|Yellow

|- style="background: #90FF90"
|[http://www.mobygames.com/game/f-zero-x F-Zero X (EU)]
|2.0.0.09
! Rice GLES2
|1 Ghz
|4.03.02
|1.55
|1000 Mhz
|GLES2N64 video plugin also works well, with slightly more texture wobbles. Needs updated SGX driver to display times correctly. The game is almost full speed all the time (while the slow-downs are mainly in-menu). Very playable - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Green

|- style="background: #90FF90"
|Mario Kart 64
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 Mhz
|Runs very well, with default settings
|Green

|- style="background: #90FF90"
|Holy Magic Century
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 Mhz
|Speed and visual are fine
|Green

|}
===Notes===

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM@166MHz
* Rebirth - OMAP3530 SoC@600MHz stock, '''512MiB RAM'''@166MHz
* 1GHz - '''DM3730 SoC@1GHz stock''', 512MiB RAM@'''200Mhz'''

Mupen2.0 Compatibility List

2013-11-04T19:11:46Z

Levi: /* The Compatibility List */ Starcraft 64 (plus some tidyup)

Mupen64Plus 2.0 is a Nintendo 64 emulator ported on Pandora by PtitSeb. Other versions exist (Android, Windows, Mac, Linux...).

Current version is 2.0.0.5 from Oct 15th 2013.

==Adding to the Compatibility List==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. You may also add specific conditions you specified in the settings if they differ from the defaults. As for the SGX driver, please write "default" if you did not change your driver vs what was in the firmware.

Don't post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new Mupen2.0 version, update the entry and add that to notes.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by PtitSeb about further debugging your problems.

==The Compatibility List==


You can sort the columns by clicking the table header (javascript required).

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game Name and Region
! Mupen Version
! Used Plugin
! Pandora Model[1]
! SGX driver
! SZ version

! Frequency
! Notes on Settings
! Status

|- style="background: #90FF90"
|[http://www.mobygames.com/game/super-mario-64 Super Mario 64 (EU)]
|2.0.0.05
! Rice Plugin
|1GHz
|4.03.02
|1.54
|1000 Mhz
|Runs very well. Some cases of sound stuttering and slowdown but otherwise almost perfect.
|Green

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/starcraft-64- StarCraft 64 (unknown)]
|2.0.0.9
! Rice GLES2
|1Ghz
|4.03.02
|1.55
|1000 Mhz
|Runs well in-game. Many screen-clear glitches in 2d menus, and slowdown - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/dr-mario-64 Dr Mario (US?)]
|2.0.0.07
! Glide GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable.
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/f1-pole-position-64 F-1 Pole Position 64]
|2.0.0.07
! Rice GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable. Barely. A Higher Clockspeed might help.
|Yellow

|- style="background: #90FF90"
|[http://www.mobygames.com/game/f-zero-x F-Zero X (EU)]
|2.0.0.09
! Rice GLES2
|1 Ghz
|4.03.02
|1.55
|1000 Mhz
|GLES2N64 video plugin also works well, with slightly more texture wobbles. Needs updated SGX driver to display times correctly. The game is almost full speed all the time (while the slow-downs are mainly in-menu). Very playable - [[User:Levi|Levi]] ([[User talk:Levi|talk]])
|Green

|- style="background: #90FF90"
|Mario Kart 64
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 Mhz
|Runs very well, with default settings
|Green

|- style="background: #90FF90"
|Holy Magic Century
|2.0.0.09
! Rice GLES2
|CC
|default
|1.55
|800 Mhz
|Speed and visual are fine
|Green

|}
===Notes===

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM
* Rebirth - OMAP3530 SoC @ 600MHz stock, **512MiB RAM**
* 1GHz - **DM3730 SoC @ 1GHz stock**, 512MiB RAM}}

Mupen2.0 Compatibility List

2013-11-04T18:42:16Z

Levi: /* The Compatibility List */

Mupen64Plus 2.0 is a Nintendo 64 emulator ported on Pandora by PtitSeb. Other versions exist (Android, Windows, Mac, Linux...).

Current version is 2.0.0.5 from Oct 15th 2013.

==Adding to the Compatibility List==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. You may also add specific conditions you specified in the settings if they differ from the defaults. As for the SGX driver, please write "default" if you did not change your driver vs what was in the firmware.

Don't post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new Mupen2.0 version, update the entry and add that to notes.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by PtitSeb about further debugging your problems.

==The Compatibility List==


You can sort the columns by clicking the table header (javascript required).

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game Name and Region
! Mupen Version
! Used Plugin
! Pandora Model[1]
! SGX driver
! SZ version

! Frequency
! Notes on Settings
! Status

|- style="background: #90FF90"
|[http://www.mobygames.com/game/super-mario-64 Super Mario 64 (EU)]
|2.0.0.05
! Rice Plugin
|1GHz
|4.03.02
|1.54
|1000 Mhz
|Runs very well. Some cases of sound stuttering and slowdown but otherwise almost perfect.
|Green

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/dr-mario-64 Dr Mario (US?)]
|2.0.0.07
! Glide GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable.
|Yellow

|- style="background: #F3F781"
|[http://www.mobygames.com/game/n64/f1-pole-position-64 F-1 Pole Position 64]
|2.0.0.07
! Rice GLES2
|Rebirth
|Default
|1.54
|995 Mhz
|Used Z64 LLE RSP for RSP Plugin. Sound and speed both slower than fullspeed. Playable. Barely. A Higher Clockspeed might help.
|Yellow

|- style="background: #90FF90"
|F-Zero64 (EU)
|2.0.0.09
! Rice GLES2 Plugin
|1 Ghz
|4.03.02
|1.55
|1000 Mhz
|GLES2N64 video plugin also works well, with slightly more texture wobbles. Needs updated SGX driver to display times correctly. The game is almost full speed all the time (while the slow-downs are mainly in-menu). Very playable.
|Green

|- style="background: #90FF90"
|Mario Kart 64
|2.0.0.09
! Rice GLES2 Plugin
|CC
|default
|1.55
|800 Mhz
|Runs very well, with default settings
|Green

|- style="background: #90FF90"
|Holy Magic Century
|2.0.0.09
! Rice GLES2 Plugin
|CC
|default
|1.55
|800 Mhz
|Speed and visual are fine
|Green

PXML specification

2013-10-28T03:01:53Z

Levi: Removing redundant outdated information

This article covers the specification for PXML files. To see the specification for PND repository files, please see the [[PND repository specification]]. To see examples you can base your own on to get quickly up-to-speed, see [[#Example_files|below]]

{{Warning | At the present time, the PXML file format isn't set in stone, and is therefore subject to change. There is no guarantee that the format or the schema are bug-free or will be changed at any time. In general it is likely that a working PXML file will stay valid, if the schema definition mentioned here is followed.}}This is the human-readable specification for the PXML file format. The PXML file format is used in your applications for the OpenPandora® that you package in <code>.pnd</code>-files or distribute otherwise, to make it possible for menus and launchers to use your applications and their properties.

A PXML file should be appended to your <code>.pnd</code>-file, using the tools provided for that purpose, or put in a directory that you want to serve as a redistributable package, to make it possible for launchers and menus to find it. It should have the name <code>PXML.xml</code> (not case sensitive) and there should only be one such file. The contents of the PXML file should also comply to this specification without exception, to guarantee that everyone will be able to read it.

The following specification is based on what the latest version of the <code>PXML_schema.xsd</code> definition accepts as valid data. Files that do not pass the validation might still work as expected, but if the validation is passed you can be (almost) 100% sure that it is supposed to be correct.

== XML compatibility ==
The PXML format is XML-based and fully XML-compliant, which means that it can be read and written by any XML reader or writer. Included with this specification should also be a <code>.xsd</code>-file, which is used by XML tools to validate PXML files. A <code>.xsd</code>-file is also known as a XML schema, and can be called the "computer-readable" version of this document. It is very good practice to validate your PXML-files with that schema before publishing them.

To write a PXML file, you also need to know the basics of writing a XML file. It boils down to the following:

# If an element contains text or other elements, it needs a start-tag and an end-tag. This looks like (1)
# If an element does not contain other elements or text, but only attributes, it looks like (2)
<source lang="xml">
<exampleelement someattribute="something">something inside it</exampleelement> 
<exampleelement2 someattribute="something"/> 
</source>

== General format ==

The PXML-file is split up into multiple so-called elements, each of which specify one property of the <code>.pnd</code>-package. All of these elements are surrounded with a <code><PXML></code> tag, which tells the readers of the file that the data within that tag belongs to a PXML file. The tag and elements should be defined as follows:
=== The <PXML> tag ===
==== Description ====
The <code><PXML></code> tag serves as the container for all PXML elements. It is the first thing that should occur in your PXML file.

==== Attributes ====
; xmlns : The "xmlns" attribute is required by the XML standard, and guarantees that this file will be identified as a PXML file. You must include the xmlns attribute, exactly as shown, in your PXML file, with the URL as specified. Only then can it be guaranteed that the file will be read at all by launchers and menu apps.

==== Required Children ====
; <code><package></code> : ''(exactly one)'' See [[#The <package> area|The <package> area]]
; <code><application></code> : ''(one or more)'' See [[#The <application> area|The <application> area]]

==== Example ====
<source lang="xml">
<PXML xmlns="http://openpandora.org/namespaces/PXML">

</PXML>
</source>

== The <package> area ==
Since PND files can contain various applications the new <code><package></code> element was introduced. It is meant to allow you to describe what the package is about. This will, at least at the moment (firmware 1 pre hotfix6), not be used by the pandora itself for detection, but is meant as tool for package repositories as well as package managers that might eventually be created.

Each PND should have one of those at the top (and only one). For single application packages this can basically be a copy of the respective areas from the <code><application></code> element.

==== Attributes ====

; id
: ''(required)'' The "id" attribute specifies an identifier common to all versions of a particular PND package. This can be achieved by appending some random number to your package name or by simply generating a completely random, very long identifier. A good ID may consist of the application name, developer name and some key, for example <code>battlejewels.skeezix.001</code> or <code>quake-1.pickle.001</code>.
: The package ID allows repositories to identify different versions of the same package and therefore determine whether that package should be updated. The package ID should therefore '''not''' be changed if a package is merely updated.
: '''The package ID '''must not''' include characters which would be invalid in directory or file names, such as ?, >, /, etc. Use of such characters will prevent the PND from functioning.'''

==== Required Children ====
; <code><author></code> : See [[#The <author> element|The <author> element]]
; <code><version></code> : See [[#The <version> element|The <version> element]]
; <code><titles></code> : See [[#The <titles> element|The <titles> element]]

==== Example ====
<source lang="xml">
<package id="uniqueID">

</package>
</source>

=== The <author> element ===
==== Description ====
The author element is an element that is used by the author to introduce him/herself.
An author element is mandatory. It accepts the following attributes:

==== Attributes ====
; name : ''(required)'' The name attribute specifies the name of the author.
; website : ''(optional)'' The website attribute specifies the website of the author.
; email : ''(optional)'' The email attribute specifies the e-mail of the author.

==== Example ====
<source lang="xml">
<author name="Bjornhild Andersson" website="http://some.website.with.author.info"/>
</source>

=== The <version> element ===
==== Description ====
The version element specifies the application version.
A version element is required. It is recommended to keep the entries as simple as possible, where possible just numbers. It accepts the following attributes:

==== Attributes ====
; major : ''(required)'' The major attribute specifies the major version number. Valid entries: strings consisting of letters (a-z and A-Z) as well as the chars '+' and '-'.
; minor : ''(required)'' The minor attribute specifies the minor version number. Valid entries: strings consisting of letters (a-z and A-Z) as well as the chars '+' and '-'.
; release : ''(required)'' The release attribute specifies the release number. Valid entries: strings consisting of letters (a-z and A-Z) as well as the chars '+' and '-'.
; build : ''(required)'' The build attribute specifies what build the application is at. Valid entries: strings consisting of letters (a-z and A-Z) as well as the chars '+' and '-'.
; type : ''(optional'' You can specify a type attribute that is either set to "release", "beta" or "alpha". This will (at the moment) not be read by libpnd but package repositories might use it in some way (to eg mark "beta" versions explicitly or something like this). If this is not specified, "release" will be assumed.

==== Example ====
<source lang="xml">
<version major="1" minor="1" release="1" build="2" type="release"/>
</source>

=== The <titles> element ===
==== Description ====
The titles element is an element that contains multiple other elements.

The titles element specifies the text that is shown to the users of your PND file as the package title. Inside the <code><titles></code> block should be one entry for each language you want to support. The first language listed should always be <code>en_US</code>. The language is indicated by the lang attribute.

==== Required Children ====
; <code><title></code> : ''(At least one with <code>lang="en_US"</code> for American English)''

==== Example ====
<source lang="xml">
<titles>
<title lang="en_US">Your application name</title>
<title lang="de_DE">Dein Programmname</title>
</titles>
</source>

=== The <descriptions> element ===
==== Description ====
The descriptions element is an element that contains multiple other elements.

The descriptions element specifies the text that is shown to the users of your PND file as the package description. Inside the <descriptions> block should be one entry for each language you want to support. The first language listed should always be <code>en_US</code>. The language is indicated by the lang attribute. Additional tags are optional.

The "descriptions"-element is optional, though it is highly recommended to specify it. If specified, at least one entry for "en_US" ( American English language) is required. Several of those elements are allowed, one for each lang that you want to display.

==== Required Children ====
; <code><description></code> : ''(At least one with <code>lang="en_US"</code> for American English)''

==== Example ====
<source lang="xml">
<descriptions>
<description lang="en_US">Your long description of this application, describing its purpose and highlighting its features.</description>
<description lang="de_DE">Deine etwas längere Programmbeschreibung, die den Sinn des Programmes und seine wichtigsten Features beschreiben sollte.</description>
</descriptions>
</source>

=== The <icon> element ===
==== Description ====
The icon element should specify a nice icon for your application. An icon element is optional, but if one is specified you have to include the src attribute. Only up to one icon element is allowed. It accepts the following attributes:

'''Note:''' Current implementation will use the PND file's appended icon; for a PXML-app-directory, it will try to use the icon mentioned in the PXML. So, for a PND file, all subapps will show the appended-icon regardless of the <icon> tag within the <code>PXML.xml</code>.

==== Attributes ====
; src : ''(required)'' The src attribute specifies the path to the image file used as the icon.

==== Example ====
<source lang="xml">
<icon src="images/icon.png"/>
</source>

== The <application> area ==
The Application-tag permits the <code>PXML.xml</code> container to have multiple applications within it; you should have at least one application tag-pair (for one app), though you may have many.

<source lang="xml">
<application id="uniqueID" appdata="dirname">

</application>
</source>

The sections which follow describe the allowed elements inside <code><application></code> blocks. You can have as many applications listed in a single PXML file as you want to (though there is/was a limit in libpnd that was set to about 50 once upon the time, which might eventually be completely be removed).

==== Attributes ====
; id
: ''(required)'' The "id" attribute specifies an identifier for your current application, and should be something globally unique so that no two PND packages have the same id. This can be achieved by appending some random number to your application name, and to use that as your id; or to simply generate a completely random, very long id. If this id already is used in another PND file, those two PND files will conflict with each other, and unforseeable errors will occur. Please put effort into generating a unique id for your PXML-file.
; appdata
: ''(optional)'' The "appdata" permits a directory name (NOT PATH) to be specified as preferred; if not present, the unique id provided in the ID attribute will be used. For example, we may want a unique id of <code>Battlejewels.skeezix.3216836217382163.v001</code>, but an appdata path of <code>battlejewels</code> to make it easier on the user, or to have multiple different battlejewels sharing one appdata.

===== Suggestions for Generating A Unique ID =====
A unique ID '''must not''' include directory or filename invalid characters, such as <code>?</code>, <code>></code>, <code>/</code>, etc. Any of those will cause the PND file to not function.

The unique-id should be unique against other PND files, but may be re-used by other 'application' tags within the PND; for example, you may have multiple subapps that want to share the same appdata path (which is formed based on unique-id!), so use the same unique-id. You might then have a utility application in that same PND, which needs its own appdata, and so gets its own unique-id.

A good unique id is the application name, developer name, and some key you may wish to update on occasion (should state-data become incompatible between updates, say.)
Consider:
* <code>battlejewels.skeezix.001</code>
* <code>quake-1.pickle.001</code>

==== Required Children ====
; <code><exec></code> : See [[#The <exec> element|The <exec> element]]
; <code><author></code> : See "The <author> element" (below)
; <code><version></code> : See "The <version> element" (below)
; <code><titles></code> : See "The <titles> element" (below)
; <code><licenses></code> : See [[#The <licenses> element|The <licenses> element]]
; <code><categories></code> : See [[#The <categories> element|The <categories> element]]



=== The <exec> element ===
==== Description ====
The exec element should specify all the information needed to execute your application. An exec element must be included in every PXML file. Only exactly one exec element is allowed. It accepts the following attributes:

==== Attributes ====
; command : ''(required)'' The command attribute specifies the path to the executable file. This should be a relative path to a file within the PND package. Must contain no arguments! One strategy you may need is to point to a shell script in your PND file, which in turn sets up <code>LD_LIBRARY_PATH</code>, determines arguments to pass, uses zenity to pop up a pre-run menu, or other trickery.
; arguments : ''(optional)'' The arguments attribute may be not present, or present with 1 or more arguments to the executable.
; startdir : ''(optional)'' The startdir attribute specifies the starting directory (Also known as the working directory) that the application should start in. This should be a relative path to a directory within the PND package, or to a well-known directory in the Pandora file system.
; standalone : ''(optional)'' The standalone attribute specifies whether or not this application can run on its own, or if it needs parameters to run. A value of "true" or "1" means that the application can be run without parameters. A value of "false" or "0" means that the application must be run with parameters (Meaning that no icon will appear for it in a launcher; it will only be run via file associations or via the terminal).
; background : ''(optional)'' The background attribute specifies whether or not this application should run in the background, and it should be possible to switch to other apps while it is running, or if it is the only application that should be running. A value of "true" or "1" means that the application can run in the background. A value of "false" or "0" means that the application must be run as the only application.
; x11 : ''(optional)'' The x11 attribute may be missing; values are one of "req", "stop", and "ignore". If "req" is set, it means the application requires X11 (and possibly could be filtered out of users display in a menu if X is not running, or perhaps such a menu would have to start X.) If "stop" is set, it means X must be not running, or temporarily shut down, for the app. If "ignore" is set, the app doesn't care if X is running or not (such as an SDL app, or a sh-script, etc.)
; extraarguments
: ''(optional)'' The extraarguments attribute may be missing; values here are appended to the <code>Exec=</code> <code>.desktop</code> line after everything else, and after adding a <code>--</code>
: <code>pnd_run.sh</code>, when executing this, will let the dashdash arguments be handled first by the shell then fed into the PND application. Regular arguments above are quoted and shielded by <code>pnd_run.sh</code> so not handled/expanded by the shell or desktop environment. Example: For file associations, <code>%f</code> (or others) may be a desirable argument.. however, placing <code>%f</code> into the <code>arguments</code> element above will result in a literal <code>%f</code> being passed into the PND application; adding <code>%f</code> into <code>extraarguments</code> will result in a file associated invocation with <code>%f</code> expanded to the desired string, instead.
: Specifically, <code>arguments</code> above will insert <code>-a "foo"</code> into the <code>Exec=</code> line, while <code>extraarguments</code> will append <code>-- foo</code>.

==== Example ====

A minimal (and typical) exec:

<source lang="xml">
<exec command="myprogram.sh"/>
</source>

A fully loaded one:

<source lang="xml">
<exec background="true" startdir="/usr/share/icons/" standalone="true" command="myprogram" arguments="arg1 arg2" x11="option" extraarguments="%f"/>
</source>

=== The <author> element ===
==== Description ====
The author element is an element that is used by the author to introduce him/herself.
An author element is mandatory. It accepts the following attributes:

==== Attributes ====
; name : ''(required)'' The name attribute specifies the name of the author.
; website : ''(optional)'' The website attribute specifies the website of the author.
; email : ''(optional)'' The email attribute specifies the e-mail of the author.

==== Example ====
<source lang="xml">
<author name="Bjornhild Andersson" website="http://some.website.with.author.info"/>
</source>

=== The <version> element ===
==== Description ====
The version element specifies the application version.
A version element is required. It is recommended to keep the entries as simple as possible, where possible just numbers. It accepts the following attributes:

==== Attributes ====
; major : ''(required)'' The major attribute specifies the major version number. Valid entries: strings consisting of letters (a-z and A-Z) as well as the chars '+' and '-'.
; minor : ''(required)'' The minor attribute specifies the minor version number. Valid entries: strings consisting of letters (a-z and A-Z) as well as the chars '+' and '-'.
; release : ''(required)'' The release attribute specifies the release number. Valid entries: strings consisting of letters (a-z and A-Z) as well as the chars '+' and '-'.
; build : ''(required)'' The build attribute specifies what build the application is at. Valid entries: strings consisting of letters (a-z and A-Z) as well as the chars '+' and '-'.
; type : ''(optional)'' You can specify a type attribute that is either set to "release", "beta" or "alpha". This will (at the moment) not be read by libpnd but package repositories might use it in some way (to eg mark "beta" versions explicitly or something like this). If this is not specified, "release" will be assumed.

==== Example ====
<source lang="xml">
<version major="1" minor="1" release="1" build="2" type="release"/>
</source>

=== The <osversion> element ===
==== Description ====
The osversion element specifies the minimal OS version that supports the PND file. The PND file will not be loaded by an OS that has an older version than the one specified here. If unsure, just use a '0' in the respective field.

==== Attributes ====
; major : ''(required)'' The major attribute specifies the major version number. Valid entries: non negative integers.
; minor : ''(required)'' The minor attribute specifies the minor version number. Valid entries: non negative integers.
; release : ''(required)'' The release attribute specifies the release number. Valid entries: non negative integers.
; build : ''(required)'' The build attribute specifies what build the application is at. Valid entries: non negative integers.

==== Example ====
<source lang="xml">
<osversion major="1" minor="1" release="1" build="2"/>
</source>

=== The <titles> element ===
==== Description ====
The titles element is an element that contains multiple other elements.

The titles element specifies the text that is shown to the users of your PND file as the package title. Inside the <code><titles></code> block should be one entry for each language you want to support. The first language listed should always be <code>en_US</code>. The language is indicated by the lang attribute.

'''Note:''' This is new in HF6. For backwards compatibilty please include the <code><title lang="en_US"></code> once outside the <code><titles></code> block, too!


==== Required Children ====
; <code><title></code> : ''(At least one with <code>lang="en_US"</code> for American English)''

At least one "title"-element is required, in the "en_US" American English language. Additional tags are optional.

==== Example ====
<source lang="xml">
<titles>
<title lang="en_US">Your application name</title>
<title lang="de_DE">Dein Programmname</title>
</titles>
<title lang="en_US">Your application name</title>
</source>

=== The <descriptions> element ===
==== Description ====
The descriptions element is an element that contains multiple other elements.

The descriptions element specifies the text that is shown to the users of your PND file as the package description. Inside the <descriptions> block should be one entry for each language you want to support. The first language listed should always be <code>en_US</code>. The language is indicated by the lang attribute. Additional tags are optional.

The "descriptions"-element is optional, though it is highly recommended to specify it. If specified, at least one entry for "en_US" ( American English language) is required. Several of those elements are allowed, one for each lang that you want to display.

'''Note:''' This is new in HF6. For backwards compatibilty please include the <code><description lang="en_US"></code> once outside the <code><titles></code> block, too!


==== Required Children ====
; <code><description></code> : ''(At least one with <code>lang="en_US"</code> for American English)''

==== Example ====
<source lang="xml">
<descriptions>
<description lang="en_US">Your long description of this application, describing its purpose and highlighting its features.</description>
<description lang="de_DE">Deine etwas längere Programmbeschreibung, die den Sinn des Programmes und seine wichtigsten Features beschreiben sollte.</description>
</descriptions>
<description lang="en_US">Your long description of this application, describing its purpose and highlighting its features.</description>
</source>

=== The <icon> element ===
==== Description ====
The icon element should specify a nice icon for your application. An icon element is optional, but if one is specified you have to include the src attribute. Only up to one icon element is allowed. It accepts the following attributes:

==== Attributes ====
; src : ''(required)'' The src attribute specifies the path to the image file used as the icon.

'''Note:''' Current implementation will use the PND file's appended icon; for a PXML-app-directory, it will try to use the icon mentioned in the PXML. So, for a PND file, all subapps will show the appended-icon regardless of the <code><icon></code> tag within the <code>PXML.xml</code>.

==== Example ====
<source lang="xml">
<icon src="images/icon.png"/>
</source>

=== The <licenses> element ===
==== Description ====
The licenses element is an element that contains multiple other elements.

It contains multiple license elements. Every element represents one license (so you *can* also multilicense something). You have to provide at least one license for your application. You can basically enter anything you want, though if you are using an existing license, it is best to just enter the name and provide a link to the full version. This tag also allows you to provide links to websites with the sourcecode.

==== Required Children ====
; <code><license></code> : ''(At least one)''

==== Attributes for <code><license></code> ====
; name : ''(required)'' The name attribute specifies what the license is called. If you don't have a real license you can also enter some short text here (please keep it short!) or just enter "other" and doN't care no more.
; url : ''(optional)'' The url attribute can be used to specify a url to the full license text.
; sourcecodeurl : ''(optional)'' The sourcecodeurl attribute can be used to specify a url to the sources.

==== Example ====
<source lang="xml">
<licenses>
<license name="GPLv2+" url="http://www.gnu.org/licenses/gpl-2.0.html" sourcecodeurl="http://pandora.org/sources/package.tar.bz2"/>
<license name="other"/>
</licenses>
</source>

=== The <previewpics> element ===
==== Description ====
The previewpics element is an element that contains multiple other elements.
A previewpics element is optional.

It contains multiple pic-elements. Every pic-element represents one preview picture. If the previewpics element is specified, it must contain at least one pic element. Use the native 800x480 LCD screen resolution, minimenu and others will scale it down as needed.

==== Required Children ====
; <code><pic></code> : ''(At least one)''

==== Attributes for <code><pic></code> ====
; src : ''(required)'' The src attribute on a pic element specifies the path to the image file used as the preview picture.

==== Recommendation ====

If you define multiple <previewpic> elements, then set the most illustrative picture as the primary <previewpic>! 
''Why?'' Because many context use only that picture at all or at that picture at first sight and more only on demand. ''Examples:''
* [[Minimenu]]'s preview function (toggled via "A") shows only the first picture,
* [http://repo.openpandora.org/includes/rss.php Repo RSS feed] shows only the first picture,
* [http://repo.openpandora.org/?page=detail&app=pndmanager-bzar PNDManager]'s app info shows 1 picture at first sight, more on demand.

Currently there is no technical definition of the ''"primary"'' <code><previewpic></code>, therefore ensure that your intended primary <code><previewpic></code>
* occurs first in the source code order,
* has a filename that lists it first in a typical lexicographical sorting order.

''What is an illustrative picture?'' 
It should quickly give an impression of the look & feel of an application. 
I.e. for video games this would mean and in-game screenshot rather than a main menu screenshot, except if the menu is just a small overlay, and the important parts of the game can still be seen.

[http://boards.openpandora.org/index.php?/topic/8137-pnd-packagers-1-please-provide-previewpics-2-define-primary-pic-if-you-give-multiple/ Discussion in the developer forum]

==== Example ====
<source lang="xml">
<previewpics>
<pic src="preview/pic1.jpg"/>
<pic src="preview/pic2.jpg"/>
</previewpics>
</source>

=== The <info> element ===
====Description====
The "info" element allows the <code>PXML.xml</code> to suggest to the desktop environment or menu a file that may be shown to the user when they want to know more - be it an About, a Install Guide, a User Guide, or all of the above. Per application only up to one of those entries is allowed. If you need more, the best approach is to create an html file and link the other files.

The file can be a txt-file or an html-file, and as the PXML-app-dir or <code>.pnd</code>-application will be mounted, the file may in turn branch to other files should it wish to.

Developers do not need to have this element, if their app is nice and simple and just runs. If the application requires additional set up (such as Quake requiring separate pak files that cannot be included in the PND), or if you wish to include sample config files or config guidelines for something complex like DosBox, or include Pandora-specific notes.. those are all good things. But the developer is encouraged to be tasteful and not go hog-wild!

==== Attributes ====
; name : ''(required)'' the name to be shown in the menu; should be obvious that it belongs to the PND .. Quake's game PND could have "Quake 1 Setup". '''Don’t call it „Readme“ or similar as it will show up just like that in the big list which is the Documentations menu of XFCE, unclear to which application it belongs!'''
; type : ''(required)'' the mime type for the file; in the event the consuming application can map mimetypes to an appropriate executable, this would be a good way of letting the user's preferred reader come up. Should be one of <code>text/html</code> (for an html file) or <code>text/plain</code> (for a .txt file). Those two are the only types allowed if the validation against the scheme is meant to be successful.
; src : ''(required)'' A file (including path relative to the PND; ie: <code>./index.html</code> would be the root of the PND) in the PND to open up; by default, the web browser will likely be used to open it.

==== Example ====
<source lang="xml">
<info name="AwesomeGame Setup" type="text/html" src="index.html"/>
</source>

=== The <categories> element ===
==== Description ====
The categories element is an element that contains multiple other elements.
A categories element is required, and must contain at least one category.

Menus that use your PXML in any shape or form will use the category information to sort your application entry into the tree or sub menus. Depending on the menu system, this will be done differently every time. It is therefore advisable to specify as many categories and subcategories as possible (and as suitable; don't specify that your application belongs in a category if it doesn't).

The "categories" element contains multiple category-elements. Every category-element represents one category that this app can be sorted into. Valid top-level categories are (among others):

# AudioVideo
# Audio
# Video
# Development
# Education
# Game
# Graphics
# Network
# Office
# Settings
# System
# Utility

Please see [http://standards.freedesktop.org/menu-spec/latest/apa.html the FreeDesktop specification] for more information. In it, you will also find valid subcategories for your top-level categories.

The category-element takes one attribute: The name-attribute. This attribute represents the category name, which preferrably should be one of the above.

A category-element can contain further child-elements: subcategory-elements. These represent the subcategories of a category that the app will be sorted into.

The subcategory-element also takes a name-attribute; this attibute can contain a name for your subcategory.

For passing validation any category/subcategory entries have to confirm to the FDO specs linked above.

==== Required Children ====
; <code><category></code> : ''(At least one)''

==== Example ====
<source lang="xml">
<categories>

<category name="Game">
<subcategory name="StrategyGame"/>
</category>

<category name="Graphics">
<subcategory name="ImageProcessing"/>
</category>
</categories>
</source>

=== The <associations> element ===
==== Description ====

The associations element is an element that contains multiple other elements.
An associations element is optional, except if <code>exec.standalone</code> is false (this is not checked via the schema!).

It contains one or multiple association-elements. Every association-element represents one file action association (though it is possible to put multiple mimetypes into a single association it muddies the waters so is best avoided.) The association is a request that this application may open a specified mimetype(s). Many applications may associate the same mimetype, and the desktop may offer a menu to allow one to be selected.

'''Note: This element is a 'recent' addition to the firmware (Super Zaxxon) - users will have to ensure they are in a late edition firmware'''

==== Required Children ====
; <code><association></code> : ''(At least one)''

==== Attributes for <code><association></code> ====
; name : ''(required)'' The name attribute on an association element specifies the user-friendly action name for the association. ex: "Open PNG". It will be shown in menus, so include your app name ideally.
; filetype : ''(required)'' The filetype attribute on an association element specifies what file types (in MIME format) that this association should apply to. ex: <code>image/png</code>
; command : ''(no longer used)'' The command attribute is not used; most linux distributions do not allow for alternative execution methods for file associations versus standalone execution, so we have dropped this idea
; arguments : ''(no longer used)'' The arguments attribution is no longer used; see 'command' for why.

You will likely want to add an <code>extraarguments</code> element into the <code><exec></code> line, to contain <code>%f</code> or other hint; in this way the desktop environment will know to insert the filename(s), url(s), etc:
* <code>%f</code> → a single file
* <code>%F</code> → multiple files
* <code>%u</code> → a single url
* <code>%U</code> → multiple urls
* and so on (see the [http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#exec-variables freedesktop specification for the Exec tag])

The result in the <code>.desktop</code> file is a <code>Exec=</code> line looking approximately like:
<source lang="ini">
Exec=/usr/pandora/scripts/pnd_run.sh -p "/media/mysdcard/pandora/menu//ristrun.pnd" -e "run.sh" -b "ristrun" -- %f
</source>

==== Example ====
<source lang="xml">
...
<exec command="myprogram.sh" extraarguments="%f"/>
...
<associations>
<association name="Open a BMP Image" filetype="image/bmp" />
<association name="Open a stylesheet" filetype="text/css" />
</associations>
...
</source>

=== The <clockspeed> element ===
==== Description ====
The clockspeed element specifies what clockspeed this app should run at. Please do only specify this element if your application *needs* to run at the specified clock speed.
A clockspeed element is optional. It accepts the following attributes:

==== Attributes ====
; frequency : ''(required)'' The frequency attribute specifies the wanted frequency, in megahertz (MHz).

==== Example ====
<source lang="xml">
<clockspeed frequency="600"/>
</source>

== Example files ==
There are several example files available in the [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=tree;f=docs/examples git repository]. They do match the current specification and (unless mentioned differently) validate. Below the direct links and a short description what they are meant to show:

* [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/examples/PXML.xml PXML.xml]: This is a sample <code>PXML.xml</code> file making use of many different things.
* [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/examples/average-case_PXML.xml average-case_PXML.xml]: This is an example how a "common" pnd with just one application could look. Most of the information for the <package> block can in this case directly be copied over from the respective parts in the <application> block.
* [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/examples/full-sample_PXML.xml full-sample_PXML.xml]: This is a complex example defining a "real" package collection. It offers several applications, all using different features of PXML.
* [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/examples/minimum-schema_PXML.xml minimum-schema_PXML.xml]: This is a minimum example that will validate with the schema but basically offer nothing beside what really is required. This application should work nicely with any pnd repositories based upon the PXML specs. '''Note:''' This application will not work with pre HF6, for support for OS versions up to HF6 an additional <title> block outside of <titles> is required!
* [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/examples/minimum-libpnd_PXML.xml minimum-libpnd_PXML.xml]: This is a minimum example that will work on the pandora, but is '''not''' following the schema and lots of information that will be required for repositories based on the PXML specs is not available.



== Validation ==
To validate a PXML file, you need a XSD (XML schema) validator, and you have to know how to use it. The schema is also available in a plaintext file described in words that are by far more compact than this page but still understandable for coders: [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/PXML_schema_plaintext.txt plaintext description of the schema]

The current-most XSD is in 'libpnd' (in the git repository). Here is the file history: [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=history;f=docs/PXML_schema.xsd PXML_schema.xsd file history]
Once on the history page, just click on the filename (right click -> save as) to download the latest version.

The easiest way to run validation is using this command:
<source lang="bash">
xmllint --noout --schema PATH/TO/PXML_schema.xsd PATH/TO/PXML.xml
</source>
To run it you have to have xmllint installed and the (latest) <code>PXML_schema.xsd</code> definition downloaded. Using this command you can now simply evaluate if the <code>PXML.xml</code> file is valid. xmllint can be installed via the angstrom repository (it is part of <code>libxml2-utils</code>).

'''Attention''': It is possible to validate PXML files that won't work with pre HotFix6. If you want to have the pnd work with basically all versions of the OS (you most likely want this!) please have a look above searching for '''' and include those blocks in your pxml file.

== Examples ==

Please have a look at the '''example files provided in git''':
* [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/examples/PXML.xml PXML.xml]: This is a sample PXML.xml file making use of many different things.
* [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/examples/average-case_PXML.xml average-case_PXML.xml]: This is an example how a "common" pnd with just one application could look. Most of the information for the <package> block can in this case directly be copied over from the respective parts in the <application> block.
* [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/examples/full-sample_PXML.xml full-sample_PXML.xml]: This is a complex example defining a "real" package collection. It offers several applications, all using different features of PXML.
* [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/examples/minimum-schema_PXML.xml minimum-schema_PXML.xml]: This is a minimum example that will validate with the schema but basically offer nothing beside what really is required. This application should work nicely with any pnd repositories based upon the PXML specs. '''NOTE:''' This application will not work with pre HF6, for support for OS versions up to HF6 an additional <title> block outside of <titles> is required!
* [http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=docs/examples/minimum-libpnd_PXML.xml minimum-libpnd_PXML.xml]: This is a minimum example that will work on the pandora, but is '''not''' following the schema and lots of information that will be required for repositories based on the PXML specs is not available.

[[Category:Documentation]]
[[Category:Development]]
[[Category:Official OpenPandora Development]]
[[Category:PND]]

LEDs and backlight

2013-10-26T18:42:33Z

Levi: /* Configuration */

==Status LEDs==

Meaning of the LEDs from left to right according to [http://boards.openpandora.org/index.php?/topic/325-led-function-documented/page__view__findpost__p__5726 gfrancisdev].

Left LED group
* SD card 1
* SD card 2
* Wifi
* Bluetooth

Right LED group
* Empty (with solder pad for hardware hackers who want to use an additional LED)
* Empty (-"-)
* Charging
* Power

These LEDs can be enabled or disabled using the LED settings script which can be launched from Menu->Settings.

==Backlight==

===Brightness===

The screen backlight power is controllable via a number of mechanisms:
* The 'sun' icon next to volume on the task bar - click it and drag the slider that appears to modify backlight power interactively
* The LCD-Settings app under Pandora menu->Settings - choose Change LCD brightness from the menu. This allows you to see the power value to be set, but doesn't change until you accept the setting and close the app
* Using the FN+u and FN+i keyboard shortcuts. This gives you quick access to screen brightness, but doesn't give you fine-grained control.

Note: For the top two methods, you can use the d-pad to change the power step by step. Up and right increase the power by 1 unit, and down or left decrease it similarly.

=== Power Saving ===

The backlight can be configured to dim to display after a period of inactivity. To set this option go to Pandora menu->Settings->LCD-Settings and choose 'Enable/disable screen blanking'.

By default this settings is disabled, since the Pandora disables the screen when the lid is closed, so unless you're in the habit of leaving your Pandora with the lid open for extended periods, this saves power and extends the lifetime of your LCD backlight by itself. Note that the lid closed settings are also configurable under Menu->Settings->Lid-Close-Settings.

== Controlling LEDs and backlight programmatically ==

Available through LED and brightness classes:
<source lang="bash">
/sys/class/leds/*
/sys/class/backlight/pandora-backlight/*
</source>
LED brightness and backlight brightness can be controlled through those files. Power and charger LEDs have variable brightness control, others are on/off only.

For example:
<source lang="bash">
sudo -s 'cat /sys/class/leds/pandora::bluetooth/max_brightness > /sys/class/leds/pandora::bluetooth/brightness'
</source>
This turns the bluetooth LED on.
<source lang="bash">
sudo -s 'echo 0 > /sys/class/leds/pandora::bluetooth/brightness'
</source>
This turns it off again (note the associated bluetooth hardware has not been touched here - only the LED lamp).

Note: SD card LEDs use SD cart power supplies, so those must be enabled for those LEDs to work (they are enabled when cards are inserted).

==== Configuration ====

/etc/default/leds contains the mappings between the folders (above) and the name triggers. The trigger files in each of the LED and backlight folders also map the trigger to the folder. The bluetooth LED as of SuperZaxxon 1.55 does not use the trigger system - instead it is controlled by the bluetooth script writing the appropriate values into .../pandora::bluetooth/brightness directly.

/etc/pandora/conf/brightness.state defines the default backlight brightness.

Note: the driver allows lower brightness than you can set using keyboard controls, because some units start to flicker on lowest brightness. This can be changed in /usr/pandora/scripts/op_bright.sh

=== backlight power saving ===

Controlled by X server through omapfb_drv.so, can be disabled by running
<source lang="bash">
xset s off
</source>

=== Keyboard controls ===

Backlight controls, power switch and pandora button are handled by pndevmapperd which calls appropriate scripts as needed.

pndevmapperd is configured using /etc/pandora/conf/eventmap - the [keys] section maps between key names and scripts to operator those controls. The scripts generally live in /usr/pandora/scripts and operate the LEDs/backlight as well as performing any hardware startup/shutdown as required (e.g. for bluetooth and wi-fi).

/usr/bin/op_test_inputs is included designed to test inputs.

LEDs and backlight

2013-10-26T18:25:53Z

Levi: /* Status LEDs */ Mention LED settings app

==Status LEDs==

Meaning of the LEDs from left to right according to [http://boards.openpandora.org/index.php?/topic/325-led-function-documented/page__view__findpost__p__5726 gfrancisdev].

Left LED group
* SD card 1
* SD card 2
* Wifi
* Bluetooth

Right LED group
* Empty (with solder pad for hardware hackers who want to use an additional LED)
* Empty (-"-)
* Charging
* Power

These LEDs can be enabled or disabled using the LED settings script which can be launched from Menu->Settings.

==Backlight==

===Brightness===

The screen backlight power is controllable via a number of mechanisms:
* The 'sun' icon next to volume on the task bar - click it and drag the slider that appears to modify backlight power interactively
* The LCD-Settings app under Pandora menu->Settings - choose Change LCD brightness from the menu. This allows you to see the power value to be set, but doesn't change until you accept the setting and close the app
* Using the FN+u and FN+i keyboard shortcuts. This gives you quick access to screen brightness, but doesn't give you fine-grained control.

Note: For the top two methods, you can use the d-pad to change the power step by step. Up and right increase the power by 1 unit, and down or left decrease it similarly.

=== Power Saving ===

The backlight can be configured to dim to display after a period of inactivity. To set this option go to Pandora menu->Settings->LCD-Settings and choose 'Enable/disable screen blanking'.

By default this settings is disabled, since the Pandora disables the screen when the lid is closed, so unless you're in the habit of leaving your Pandora with the lid open for extended periods, this saves power and extends the lifetime of your LCD backlight by itself. Note that the lid closed settings are also configurable under Menu->Settings->Lid-Close-Settings.

== Controlling LEDs and backlight programmatically ==

Available through LED and brightness classes:
<source lang="bash">
/sys/class/leds/*
/sys/class/backlight/pandora-backlight/*
</source>
LED brightness and backlight brightness can be controlled through those files. Power and charger LEDs have variable brightness control, others are on/off only.

For example:
<source lang="bash">
sudo -s 'cat /sys/class/leds/pandora::bluetooth/max_brightness > /sys/class/leds/pandora::bluetooth/brightness'
</source>
This turns the bluetooth LED on.
<source lang="bash">
sudo -s 'echo 0 > /sys/class/leds/pandora::bluetooth/brightness'
</source>
This turns it off again (note the associated bluetooth hardware has not been touched here - only the LED lamp).

Note: SD card LEDs use SD cart power supplies, so those must be enabled for those LEDs to work (they are enabled when cards are inserted).

==== Configuration ====

/etc/default/leds contains the mappings between the files (above) and the name triggers. As of SuperZaxxon 1.55, only the op_led_settings script seems to use this file. All the other scripts manipulate the files defined above directly.

/etc/pandora/conf/brightness.state defines the default backlight brightness.

Note: the driver allows lower brightness than you can set using keyboard controls, because some units start to flicker on lowest brightness. This can be changed in /usr/pandora/scripts/op_bright.sh

=== backlight power saving ===

Controlled by X server through omapfb_drv.so, can be disabled by running
<source lang="bash">
xset s off
</source>

=== Keyboard controls ===

Backlight controls, power switch and pandora button are handled by pndevmapperd which calls appropriate scripts as needed.

pndevmapperd is configured using /etc/pandora/conf/eventmap - the [keys] section maps between key names and scripts to operator those controls. The scripts generally live in /usr/pandora/scripts and operate the LEDs/backlight as well as performing any hardware startup/shutdown as required (e.g. for bluetooth and wi-fi).

/usr/bin/op_test_inputs is included designed to test inputs.

LEDs and backlight

2013-10-26T18:02:14Z

Levi: /* Controlling LEDs and backlight programmatically */ rewrite

==Status LEDs==

Meaning of the LEDs from left to right according to [http://boards.openpandora.org/index.php?/topic/325-led-function-documented/page__view__findpost__p__5726 gfrancisdev].

Left LED group
* SD card 1
* SD card 2
* Wifi
* Bluetooth

Right LED group
* Empty (with solder pad for hardware hackers who want to use an additional LED)
* Empty (-"-)
* Charging
* Power

==Backlight==

===Brightness===

The screen backlight power is controllable via a number of mechanisms:
* The 'sun' icon next to volume on the task bar - click it and drag the slider that appears to modify backlight power interactively
* The LCD-Settings app under Pandora menu->Settings - choose Change LCD brightness from the menu. This allows you to see the power value to be set, but doesn't change until you accept the setting and close the app
* Using the FN+u and FN+i keyboard shortcuts. This gives you quick access to screen brightness, but doesn't give you fine-grained control.

Note: For the top two methods, you can use the d-pad to change the power step by step. Up and right increase the power by 1 unit, and down or left decrease it similarly.

=== Power Saving ===

The backlight can be configured to dim to display after a period of inactivity. To set this option go to Pandora menu->Settings->LCD-Settings and choose 'Enable/disable screen blanking'.

By default this settings is disabled, since the Pandora disables the screen when the lid is closed, so unless you're in the habit of leaving your Pandora with the lid open for extended periods, this saves power and extends the lifetime of your LCD backlight by itself. Note that the lid closed settings are also configurable under Menu->Settings->Lid-Close-Settings.

== Controlling LEDs and backlight programmatically ==

Available through LED and brightness classes:
<source lang="bash">
/sys/class/leds/*
/sys/class/backlight/pandora-backlight/*
</source>
LED brightness and backlight brightness can be controlled through those files. Power and charger LEDs have variable brightness control, others are on/off only.

For example:
<source lang="bash">
sudo -s 'cat /sys/class/leds/pandora::bluetooth/max_brightness > /sys/class/leds/pandora::bluetooth/brightness'
</source>
This turns the bluetooth LED on.
<source lang="bash">
sudo -s 'echo 0 > /sys/class/leds/pandora::bluetooth/brightness'
</source>
This turns it off again (note the associated bluetooth hardware has not been touched here - only the LED lamp).

Note: SD card LEDs use SD cart power supplies, so those must be enabled for those LEDs to work (they are enabled when cards are inserted).

==== Configuration ====

/etc/default/leds contains the mappings between the files (above) and the name triggers. As of SuperZaxxon 1.55, only the op_led_settings script seems to use this file. All the other scripts manipulate the files defined above directly.

/etc/pandora/conf/brightness.state defines the default backlight brightness.

Note: the driver allows lower brightness than you can set using keyboard controls, because some units start to flicker on lowest brightness. This can be changed in /usr/pandora/scripts/op_bright.sh

=== backlight power saving ===

Controlled by X server through omapfb_drv.so, can be disabled by running
<source lang="bash">
xset s off
</source>

=== Keyboard controls ===

Backlight controls, power switch and pandora button are handled by pndevmapperd which calls appropriate scripts as needed.

pndevmapperd is configured using /etc/pandora/conf/eventmap - the [keys] section maps between key names and scripts to operator those controls. The scripts generally live in /usr/pandora/scripts and operate the LEDs/backlight as well as performing any hardware startup/shutdown as required (e.g. for bluetooth and wi-fi).

/usr/bin/op_test_inputs is included designed to test inputs.

Port Requests

2013-10-16T17:06:42Z

Levi: /* Games */

'''Some requests have and may not appear on this list'''

* [http://www.gp32x.com/board/index.php?showtopic=47518 Emulator Plausibility List] - A semi-speculative list of which systems the Pandora is likely to emulate, along with status of active emulation projects.
* [http://www.gp32x.com/board/index.php?showtopic=43659 Closed Source Projects] - A list of closed source / commercial projects that have shown interest / disinterest in the Pandora platform.
* [http://www.gp32x.com/board/index.php?showtopic=43532 Port Requests] - A catch-all thread for all of the "Wouldn't it be cool if Pandora ran XXXX?" posts.

If you have a port request, you may add it to this page. If a developer likes the look of it, it might get picked up. Before adding your request, please follow these steps:

*Check that your request is not already ported or under development on the Repo or in the forums
*Determine if the request is viable using [http://www.gliffy.com/publish/1448256/ this flowchart]; if not, move to "improbable"
*Requests need a link to source code
*Observe alphabetical and categorical order
==Possible==
===Games===
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
!Name
!Game Type
!Link to Source
!Remarks
|-
|Adonthell
|RPG
|[http://adonthell.nongnu.org/index.shtml]
|
|-
|Alien Arena
|FPS
|[http://icculus.org/alienarena/rpa/]
|old alien movie aesthetic
|-
|Angstron 2
|FPS
|[http://angstron2.garage.maemo.org/]
|runs on Nokia N770, N800, and N810
|-
|AnUntitledStory
|Metroidvania
|[http://www.mattmakesgames.com/]
|Really nice Metroidvania style adventure game.
|-
|Apprentice 2
|Card
|[http://sourceforge.net/projects/apprentice2/]
|
|-
|Area 2048
|Shmup
|[http://homepage2.nifty.com/isshiki/prog_win_d.html]
|Fast-paced arena shooter
|-
|AssaultCube
|FPS
|[http://assault.cubers.net/]
|team oriented multiplayer
|- style="background: #90FF90"
|Bitfighter
|Puzzle
|[http://www.bitfighter.org/]
|Now available on the [http://repo.openpandora.org/?page=detail&app=bitfighter repo] 2-D space combat with retro graphics, Robotron-like controls and customizable ships
|-
|Blobwars2
|TPS
|[http://sourceforge.net/projects/blobandconquer/]
|aka Blob Wars:Blob And Conquer
|-
|Block Attack - Rise of the Blocks
|BlocksGame
|[http://blockattack.sourceforge.net]
|Switch with neighbour left/right (also via gravity into gap). Control via keys.
|-
|BlueFury
|?
|[http://sourceforge.net/projects/bluefury/]
|
|-
|bsdgames
|Terminal-based
|[http://packages.debian.org/lenny/bsdgames]
|
|-
|BZFlag
|FPS
|[http://bzflag.org/]
|designed for mouse+keyboard
|-
|Cube 1
|FPS
|[http://cubeengine.com/cube.php4]
|(works with lunixbochs' GL shim)
|-
|Cube 2: Sauerbraten
|FPS
|[http://sourceforge.net/projects/sauerbraten/]
|Works (and has good framerates) with lunixbochs' GL shim.
|-
|Coldest
|mech
|[http://sourceforge.net/projects/coldestgame/]
|
|-
|Crack Attack
|Puzzle
|[http://www.nongnu.org/crack-attack/]
|inspired by Tetris Attack
|-
|ctp2
|Strategy
|[http://ctp2.darkdust.net/]
|Civilization:Call To Power 2
|-
|-
|Cubosphere
|Puzzle
|[http://sourceforge.net/projects/cubosphere/]
|Freeware game similar to the PSX game "Kula World" / "Roll Away".Platform independent, written in C++ and using OpenGL, SDL, libjpeg, LUA, GLSL-Shader.
|-
|Cytadela
|FPS
|[http://cytadela.sourceforge.net]
|Conversion of Amiga FPS created by Virtual Design in mid 1990's
|-
|Danger from the Deep
|?
|[http://sourceforge.net/projects/dangerdeep/]
|WW2 German submarine 3d simulation
|-
|Dawn
|RPG
|[http://dawn-rpg.sourceforge.net/wiki/index.php/Main_Page]
|
|-
|Dash Border
|Shmup
|[http://homepage2.nifty.com/isshiki/prog_linux_game.html]
|Arena shmup with focus on lots of speed
|-
|DTXmania
|Rhythm
|[http://en.sourceforge.jp/projects/dtxmania/]
|Japanese
|-
|Egoboo
|dungeon crawl
|[http://egoboo.sourceforge.net/]
|<10 fps with libGL
|-
|Emilia Pinball
|Pinball
|[http://pinball.sourceforge.net/]
|Uses the Allegro renderer, and should thus be easily portable, according to [http://boards.openpandora.org/index.php?/topic/1717-visual-pinball-went-opensource/page__view__findpost__p__105625 lunixbochs]
|-
|Empty Clip
|Action-RPG
|[http://emptyclip.sourceforge.net/]
|
|-
|Fabled Lands App
|Gamebook
|[http://flapp.sourceforge.net/]
|Java
|-
|Fall of Imiryn
|RPG
|[http://annchienta.sourceforge.net/?page=fall_of_imiryn]
|
|-
|FlightGear
|Flight sim
|[http://www.flightgear.org/]
|
|-
|Fofix
|Music
|[http://code.google.com/p/fofix/]
|Fret on fire fork
|-
|FooBillard
|Sports
|[http://foobillard.sourceforge.net/]
|
|-
|FreeOrion
|TBS
|[http://freeorion.org/]
|inspired by Master of Orion
|-
|Free Tennis
|Sports
|[http://freetennis.sourceforge.net/]
|
|-
|Funguloids
|Arcade,Puzzle
|[http://funguloids.sourceforge.net/]
|
|-
|Game Of Bases
|RTS
|[http://www.modeemi.cs.tut.fi/~flux/goba/]
|Flash Attack remake
|-
|Glest
|RTS
|[http://sourceforge.net/projects/glest/]
|
|-
|GNU shogi
|board
|[http://www.cs.caltech.edu/~mvanier/hacking/gnushogi/gnushogi.html]
|computer shogi
|-
|Hedgewars
|Artillery
|[http://www.hedgewars.org/]
|Worms clone
|-
|Heroes
|arcade
|[http://sourceforge.net/projects/heroes/]
|like tron
|-
|Heroes of Allacrost
|RPG
|[http://www.allacrost.org/]
|Requires GL, glu, openal, lua, sdl_ttf
|-
|Helena The 3rd
|action-platforming
|[https://code.google.com/p/helenathe3rd/]
|inspired by Blaster Master
|-
|iiChantra P.E.A.R. DSO
|Action, Platform
|[http://iichantra.ru/files/pear-dso-src1.2.zip]
|Contra-inspired game with original gameplay and retro-style graphics and music, sequel of iiChantra P.E.A.R.
Previous iiChantra games exist, [http://iichantra.ru/downloads/ first part of P.E.A.R. and Halloween version].
|-
|Jack-Claw
|Action
|[https://code.google.com/p/jack-claw/]
|
|-
|Kiki the Nano Bot
|Puzzle
|[http://kiki.sourceforge.net/]
|mixture of Sokoban and Kula World
|-
|Kollision (from the KDE game pack)
|Arcade
|[http://games.kde.org/game.php?game=kollision]
|Dodge more and more balls. Desktop control via mouse, desirable if Panda conversion could use nub, dpad or touchscreen.
|-
|Kurok
|FPS
|[http://www.bladebattles.com/kurok/files.html]
|
|-
|Knyttds
|Platformer
|[http://code.google.com/p/knyttds/]
|
|-
|L-Echo
|Puzzle
|[http://code.google.com/p/l-echo/]
|Echochrome clone
|-
|LinWarrior
|mech
|[http://www.hackcraft.de/games/linwarrior_3d/downloads.htm]
|
|-
|Lips of Suna
|dungeon crawl
|[http://lipsofsuna.org/]
|
|-
|LOCKJAW
|puzzle
|[http://www.pineight.com/lj/]
|tetris
|-
|LordsAWar
|TBS
|[http://www.nongnu.org/lordsawar/]
|Warlords II clone
|-
|Lunar Lander
|?
|[http://www.doof.me.uk/lunar-lander/]
|Lunar Lander Clone
|-
|Marfitude
|Music
|[http://www.erestar.net/games/marfitude/]
|loads a music file and turns it into a level. Graphics coded in SDL
|-
|M.A.R.S.
|shmup
|[http://mars-game.sourceforge.net/]
|
|-
|Masashikun Hi
|Arcade
|[http://www.asahi-net.or.jp/~cs8k-cyu/free/mas_e.html]
|stick figure olympics from Kenta Cho (ABA Games)
|-
|Megamek
|TBS
|[http://sourceforge.net/projects/megamek/]
|
|-
|MegaZeux
|Arcade
|[http://sourceforge.net/projects/megazeux/]
|game creation system
|-
|Micropolis
|City sim
|[http://www.donhopkins.com/home/micropolis/]
|sim city
|-
|Microwar
|Arcade
|[http://microwar.sourceforge.net/]
|Space Invaders clone in the cruel world of micro-compter industry
|-
|MotoGT
|Racing
|[http://motogt.sourceforge.net/]
|motorcycles
|-
|Mu-cade
|shmup
|[http://www.asahi-net.or.jp/~cs8k-cyu/windows/mcd_e.html]
|from Kenta Cho (ABA Games)
|-
|Netrek
|Star Trek themed battle sim
|[http://netrek.org]
|-
|Neverball
|Puzzle
|[http://neverball.org/]
|similar to Super Monkey Ball
|-
|Nikki and the Robots
|platformer
|[http://joyridelabs.de/game/code/]
|
|-
|Nimuh
|Puzzle
|[http://sourceforge.net/projects/nimuh/]
|based in the "Theseus and the Minotaur Mazes"
|-
|NPRQuake
|FPS
|[http://research.cs.wisc.edu/graphics/Gallery/NPRQuake/]
|Non-PhotoRealistic rendering of GLQuake
|-
|Oolite
|space sim
|[http://www.oolite.org/]
|
|-
|Open Invaders
|Arcade
|[http://www.jamyskis.net/invaders.php]
|Another Space Invaders clone, as Classic Invaders (from the repo) is not enough arcade/action like. Would prefer even something better than Open Invaders.
|-
|open-ig
|RTS
|[http://code.google.com/p/open-ig/]
|Java clone of "Imperium Galactica" by Digital Reality
|-
|openBVE
|Train sim
|[http://openbve.trainsimcentral.co.uk/]
|
|-
|OpenDungeons
|RTS
|[http://opendungeons.sourceforge.net/index.php/Main_Page]
|Dungeon Keeper clone
|-
|Paraball
|Sports
|[http://dl.openhandhelds.org/cgi-bin/gp32.cgi?0,0,0,0,48,629]
|Simple volleyball game.uses Fenix
|-
|Pax Britannica
|RTS
|[http://paxbritannica.henk.ca/]
|
|-
|Performous
|Music
|[http://sourceforge.net/projects/performous/]
|Karaokee,Guitar,drum,DDR
|-
|Pioneer Space Sim
|space sim
|[http://pioneerspacesim.net/]
|A game of lonely space adventure.
|-
|Privateer Gemini Gold
|space sim
|[http://sourceforge.net/projects/privateer/]
|patterned after original Wing Commander Privateer and uses Vegastrike engine
|-
|Pseudoform
|FPS
|[http://www.pseudoform.org/]
|portal clone
|-
|Race For The Galaxy AI
|Board
|[http://www.keldon.net/rftg/]
|Probably needs minor UI tweaks for everything to fit
|-
|Red Eclipse
|FPS
|[http://www.redeclipse.net/]
|uses cube2 engine
|-
|S.C.O.U.R.G.E. Heroes of Lesser Renown
|RPG
|[http://www.scourgeweb.org/]
|3D rogue-like
|-
|Scorched3D
|Artillery
|[http://www.scorched3d.co.uk/]
|based on Scorched Earth
|-
|Secret Maryo Chronicles
|Platformer
|[http://www.secretmaryo.org/index.php?page=about]
|
|-
|Shadowgrounds
|action
|[http://code.google.com/p/shadogrounds-and-shadowgrounds-survivor/]
|Shadowgrounds" and "Shadowgrounds: Survivor
|-
|Simulate (a Simon clone)
|Memory, Puzzle
|[http://inventwithpython.com/simulate.py]
|Python PyGame library
|-
|Skulltag
|fps
|[http://vega.skulltag.com/2010/03/skulltag-source-code-released/]
|doom with multiplayer focus
|-
|Sleep Is Death
|RPG
|[http://www.sleepisdeath.net/]
|2 player only
|-
|Smash Battle
|Platformer
|[http://sourceforge.net/projects/smashbattle/]
|
|-
|Smokin'Guns
|FPS
|[http://sourceforge.net/projects/smokinguns/]
|
|-
|Soulfu
|RPG
|[http://soulfu.motherhamster.org/]
|[http://www.gp32x.com/board/index.php?/topic/55339-testing-blobwars-soulfu port attempt] was unsuccessful
|-
|SpaceTrader
|FPS,Strategy
|[http://sourceforge.net/projects/palmtrader/]
|
|-
|Speed Dreams
|Racing
|[http://speed-dreams.sourceforge.net/]
|TORCS fork
|-
|Summoning Wars
|RPG
|[http://sumwars.org/]
|port should be possible, main issue is some excessive memory use
|-
|Sunbeam
|RPG
|[http://dl.openhandhelds.org/cgi-bin/gp32.cgi?0,0,0,0,46,1048]
|Abandoned project for the gp32
|
|-
|Tester Phase One
|Shmup
|[http://homepage2.nifty.com/isshiki/prog_win_game.html]
|Vertical shmup
|-
|Thunder&Lightning
|Flight sim
|[http://tnlgame.net/]
|
|-
|T.o.M.E.
|RPG
|[http://sourceforge.net/projects/pernband/]
|
|-
|Torus Trooper
|shmup
|[http://www.asahi-net.or.jp/~cs8k-cyu/windows/tt_e.html]
|Gyruss like tube shooter with focus on speed from Kenta Cho (ABA Games)
|-
|Trackballs
|Puzzle
|[http://trackballs.sourceforge.net/download.shtml]
|
|-
|Tremulous
|FPS+RTS
|[http://tremulous.net/]
|
|- style="background: #90FF90"
|UFO:AI
|TBS
|[http://sourceforge.net/projects/ufoai/]
|Available on the repo here: [http://repo.openpandora.org/?page=detail&app=ufoai_ptitseb], sourcecode of GLES port here: [https://github.com/ptitSeb/UFO--AI-OpenPandora]
|-
|Ultimate Stunts
|Racing
|[http://sourceforge.net/projects/ultimatestunts/]
|3D Racing with focus on settings times and making tracks
|-
|Vertigo
|arcade
|[http://www.vertigo-game.com/]
|
|-
|violetland
|shooter
|[http://code.google.com/p/violetland/]
|top down
|-
|Warlock's Gauntlet
|shooter
|[http://www.musztardasarepska.pl/wgdown/index.php?lang=en]
|
|-
|Warsow
|FPS
|[http://www.warsow.net/]
|requirements similar to Quake 3
|-
|WFTO
|Strategy
|[http://warfortheoverworld.org/downloads/]
|NBKE fork
|-
|Wok
|Arcade
|[http://www.asahi-net.or.jp/~cs8k-cyu/linux/wok_e.html]
|ball tossing game from Kenta Cho (ABA Games)
|- style="background: #90FF90"
|World of Padman
|FPS
|[http://padworld.myexp.de/index.php?files=mapping]
|creative death-match weapons and models. On the repo here: [http://repo.openpandora.org/?page=detail&app=wop_ptitseb], sources of the GLES port here: [https://github.com/ptitSeb/WoP-Pandora]
|-
|Xonotic
|FPS
|[http://www.xonotic.org/]
|Nexuiz fork [http://forums.xonotic.org/showthread.php?tid=1427 lightweight version]
|-
|Yoda Soccer
|Sports
|[http://yodasoccer.sourceforge.net/]
|gameplay and style of Sensible World of Soccer (a.k.a. SWOS)
|-
|ZEQ2 Lite
|Fighting
|[http://zeq2.com/lite/?page_id=33]
|
|-
|Z-LOCK
|Shmup
|[http://homepage2.nifty.com/isshiki/prog_win_d.html]
|Vertical shmup with focus on lock-on mechanic
|-
|}

===Emulators===
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
!Name
!System
!Link to Source
!Remarks
|-
|B-EM
|BBC Micro
|[http://b-em.bbcmicro.com/]
|[http://stardot.org.uk/forums/viewtopic.php?f=4&t=3830 Compiling B-em 2.1+ for Linux], [http://stardot.org.uk/forums/viewtopic.php?f=4&t=1986 GP2X port]
|-
|Mini vMac
|Macintosh Plus
|[http://sourceforge.net/projects/minivmac/]
|There is an ARM Linux binary available, and I did get it to run on the Pandora quite smoothly, but I have no means to put it into a PND.
|-
|Reality Boy
|Virtual Boy
|[http://www.goliathindustries.com/vb/VBDown.html]
|Runs, but slow and without sound in linux :( - Needs Allegro
|-
|TwoMbit
|Sega Master System
|[http://sourceforge.net/projects/twombit/]
|-
|Uzem
|Uzebox
|[http://uzebox.org/wiki/index.php?title=Emulator]
|
|-
|}

===Game Engines===
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
!Name
!Engine Type
!Link to Source
!Remarks
|-
|Colditz Escape
|Escape From Colditz
|[http://sites.google.com/site/colditzescape/]
|
|-
|Doomsday
|Doom,Heretic and Hexen
|[http://dengine.net/]
|
|-
|DreamZZT
|ZZT interpreter
|[http://dev.c99.org/DreamZZT/]
|
|-
|ezQuake
|Quakeworld
|[http://sourceforge.net/projects/ezquake/]
|QuakeWorld client
|- style="background: #90FF90"
|FIFE
|Isometric
|[http://fifengine.de]
|Ported and can be found in the Unknown Horizon PND [http://repo.openpandora.org/?page=detail&app=unknown_horizons_ptitseb], but only with SDL backend
|-
|Freeprince
|Prince of Persia
|[http://www.princed.org]
|
|-
|FreeRA
|Command&Conquer/Red Alert
|[http://freera.sourceforge.net/]
|
|-
|FSOpen
|FreeSpace 2
|[http://scp.indiegames.us/]
|FreeSpace and FreeSpace 2 were ported using different code base
|-
|lwjgl
|Input,Sound,Graphics
|[http://java-game-lib.svn.sourceforge.net/viewvc/java-game-lib/]
|Requires compilation of native library->OGL2.0 wrappers needed
|-
|Newton Game Dynamics
|Physics
|[http://newtondynamics.com]
|Demos are being ported from MFC to Qt
|-
|Novashell
|Lua-based 2D Game/Creation
|[http://www.rtsoft.com/novashell/]
|Author interested in Pandora
|-
|OHRRPGCE
|2D RPG
|[http://en.wikipedia.org/wiki/OHRRPGCE]
|
|-
|OpenDarkEngine
|Dark Engine
|[http://sourceforge.net/projects/opde/]
|
|-
|OpenMOHAA
|FPS
|[http://sourceforge.net/projects/openmohaa/]
|Medal of Honor: Allied Assault
|-
|openmw
|The Elder Scrolls III: Morrowind
|[http://openmw.com/wiki/index.php?title=Main_Page]
|
|-
|PONScripter
|visual novel
|[http://unclemion.com/onscripter/]
|Proportional-OnScripter a heavy modified fork of ONScripter-EN that is deliberately backwards-incompatible with ONScripter-EN.
Narcissu: Side 2nd was ported to this engine.
|-
|SLUDGE
|2D Adventure creation
|[http://sourceforge.net/projects/opensludge/develop]
|Already has OpenGL ES 2 support. Development kit and engine available in Debian/Ubuntu and for Mac/Windows.
|-
|Sphere
|Game Creation
|[http://en.wikipedia.org/wiki/Sphere_%28program%29]
|
|-
|Syntensity
|multiplayer 3D
|[http://www.syntensity.com/]
|
|-
|TA3D
|Total Annihilation remake
|[http://www.ta3d.org/cquoi-en.php]
|
|-
|Zod
|Zod Recreation with multiplayer focus
|[http://zod.sourceforge.net/]
|
|-
|}

===Other programs===
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
!Name
!App Type
!Link to Source
!Remarks
|-
|Aldrin
|MIDI Sequencer
|[http://code.google.com/p/aldrin-sequencer/]
|
|-
|Ardour
|DAW
|[http://www.ardour.org/]
|
|-
|Art of Illusion
|3D modeling
|[http://sourceforge.net/projects/aoi/]
|Java
|-
|BlueGriffon
|WYSIWYG web editor
|[http://bluegriffon.org/]
|
|-
|Calligra Suite
|office
|[http://www.calligra-suite.org/]
|koffice fork
|-
|Celestia
|space simulation
|[http://www.shatters.net/celestia/]
|
|-
|Clementine
|Music Manager
|[http://www.clementine-player.org/]
|Amarok 1.4 forked+ported to Qt4 and GStreamer
|-
|Dropbox
|File Management
|[http://www.dropbox.com/downloading?os=lnx]
|There is a [https://github.com/andreafabrizi/Dropbox-Uploader shell script] to upload, download, delete and list files from Dropbox.
|-
|Ease
|presentation
|[http://www.ease-project.org/download.html]
|
|-
|Freecad
|3D CAD modeler
|[http://sourceforge.net/projects/free-cad/]
|
|-
|FreeSpeak
|translator
|[http://freespeak.berlios.de/]
|
|-
|Gajim
|Instant messaging
|[http://gajim.org/downloads.php?lang=en#tarball]
|
|-
|Gcstar
|library management
|[http://wiki.gcstar.org/en/]
|
|-
|Gnash
|flash
|[http://www.gnashdev.org/]
|
|-
|-
|Gnome Disk Utility
|Manage storage devices - format, partition, file system check, benchmark test, etc
|[http://git.gnome.org/browse/gnome-disk-utility]
|If Pandora users want to compare SD card speeds, benchmark tests only make sense on the target device (the Pandora itself). I propose to port this one, as it has all necessary functions in an easy interface. --[[User:Porg|Porg]] 00:14, 19 July 2011 (CEST)
|-
|Gnomeradio
|Radio
|[http://projects.gnome.org/gnomeradio/]
|Gnomeradio is a FM-radio tuner for the GNOME desktop (version 1 and 2). It should work with every FM tuner card that is supported by video4linux.
|-
|Gnote
|notetaking
|[http://live.gnome.org/Gnote]
|c++ tomboy clone
|-
|GnoTime
|TODO list/diary/journal
|[http://gttr.sourceforge.net/]
|
|-
|GNU Radio
|Radio
|[http://gnuradio.org/]
|GNU Radio is a free software toolkit for learning about, building, and deploying software-defined radio systems. Version needed: 3.5.1 or higher.
|
|-
|Gnucap
|Circuit Simulation
|[http://http://gnucap.org/]
|General purpose circuit simulator. It performs nonlinear dc and transient analyses, fourier analysis, and ac analysis.
|
|-
|Gobby
|Collaborative editor
|[http://gobby.0x539.de/trac/]
|
|-
|GoogSysTray
|System tray
|[http://sourceforge.net/projects/googsystray/]
|
|-
|Gramps
|Genealogical research
|[http://gramps-project.org/download/]
|
|-
|Gtrainer
|Health
|[http://kutxa.homeunix.org/gtrainer/index-en.html]
|
|-
|Gummi
|WYSIWYG ''LATEX'' editor
|[http://gummi.midnightcoding.org/]
|Live preview pane for document
|-
|gwibber
|microblogging client
|[http://gwibber.com/]
|
|-
|Handbrake
|video transcoder
|[http://handbrake.fr/]
|
|-
|HTTrack
|Offline reader/Web crawler
|[http://www.httrack.com/]
|
|-
|Hydrogen
|drum machine
|[http://www.hydrogen-music.org/]
|
|-
|Jokosher
|multi-track studio
|[http://www.jokosher.org/]
|
|-
|Kazam
|screen capture
|[https://launchpad.net/kazam]
|
|-
|Kismet
|network detector,packet sniffer,intrusion detection
|[http://www.kismetwireless.net/]
|
|-
|Kolourpaint
|Pixel graphics editor
|[http://www.kolourpaint.org/]
|
|-
|KStars
|Desktop Planetarium Software
|[http://edu.kde.org/applications/all/kstars]
|
|-
|KToon
|2D Animation
|[http://www.ktoon.net/]
|Port requires gui changes
|-
|LilyPond
|Musical Score Editor & Engraver
|[http://lilypond.org]
|
|-
|Maemo Mapper
|geographical mapping
|[https://garage.maemo.org/projects/maemo-mapper/]
|designed for 800 × 480
|-
|Marble
|digital globe
|[http://edu.kde.org/marble/]
|
|-
|Maxima
|Math
|[http://maxima.sourceforge.net/]
|
|-
|Miro
|Internet television
|[http://www.getmiro.com/]
|
|-
|Mixxx
|DJ mixing software
|[http://www.mixxx.org/download.php]
|[http://www.mixxx.org/wiki/doku.php/dependencies Dependencies]. There is an 800x480 skin called [http://www.mixxx.org/forums/viewtopic.php?f=8&t=2430 Outline].
|-
|Mosaic-CK
|browser
|[http://www.floodgap.com/retrotech/machten/mosaic/]
|NCSA Mosaic
|-
|MySQL Workbench
|MySql Database Tools (remote DB administration)
|[http://wb.mysql.com/?page_id=152]
|
|-
|Nathive
|image editor
|[http://www.nathive.org/]
|
|-
|OpenAstro.org
|natal chart generator
|[http://openastro.org/?Download]
|
|-
|Open-rp
|Remote Play
|[http://code.google.com/p/open-rp/]
|Remotely play PS3
|-
|OpenShot
|movie editor
|[http://www.openshot.org/]
|
|-
|PCB
|printed circuit board editor
|[http://pcb.gpleda.org/]
|
|-
|puddletag
|audio tag editor
|[http://puddletag.sourceforge.net/index.html]
|
|-
|Qucs
|Circuit Simulation
|[http://qucs.sourceforge.net/index.html]
|Qucs is an integrated circuit simulator which means you are able to setup a circuit with a graphical user interface (GUI) and simulate the large-signal, small-signal and noise behaviour of the circuit. After that simulation has finished you can view the simulation results on a presentation page or window. Uses QT.
|-
|RedNotebook
|Diary/Journal
|[http://digitaldump.wordpress.com/projects/rednotebook/]
|
|-
|Recipe Manager
|Recipe Manager
|[https://launchpad.net/recipe-manager]
|
|-
|Rosegarden
|sequencer, score editor, composition and editing
|[http://www.rosegardenmusic.com/]
|
|-
|Rubrica
|address book
|[http://freshmeat.net/projects/rubrica/]
|
|-
|scribus
|page layout
|[http://www.scribus.net/]
|
|-
|Shotwell
|photo manager
|[http://yorba.org/shotwell/]
|
|-
|Stellarium
|Virtual Planetarium
|[http://www.stellarium.org/]
|
|-
|TangoGPS
|GPS
|[http://www.tangogps.org/]
|[http://www.angstrom-distribution.org/repo/?pkgname=tangogps Anstrom Repo] [http://www.gp32x.com/board/index.php?/topic/54520-bluetooth-gps-and-tangogps/ pandora]
|-
|Tilda
|Quake style terminal
|[http://tilda.sourceforge.net/wiki/index.php/Main_Page]
|
|-
|Tor
|Anonymity network
|[https://www.torproject.org/download/download.html.en#source]
|
|-
|Traverso DAW
|Multitrack audio recording & editing
|[http://traverso-daw.org/]
|
|-
|TuxGuitar
|multitrack guitar tablature editor & player
|[http://sourceforge.net/projects/tuxguitar/]
|
|-
|Zynaddsubfx
|Software Synthesizer
|[http://sourceforge.net/projects/zynaddsubfx/]
|
|-
|}

==Improbable==
programs with available source code that are unlikely to be ported
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
!Name
!App Type
!Link to Source
!Reason
|-
|0AD
|RTS
|[http://wildfiregames.com/0ad/page.php?c=46]
|high System requirements
|-
|Ardentryst
|Action-RPG
|[http://sourceforge.net/projects/ardentryst/]
|high System requirements
|-
|Arx Fatalis
|Action-RPG
|[http://arx.parpg.net/]
|There is a openGL port (https://github.com/arx/ArxLibertatis). It's far too resource-intensive with glshim.
|-
|Capitán Sevilla
|Platformer
||[http://computeremuzone.com/ficha.php?id=754&l=en]
|runs very slow at 1000Mhz, works only with swap, needs too much ram
|-
|Dolphin
|Gamecube Emulator
|[http://www.dolphin-emulator.com/]
|high System requirements
|-
|Pcsx 2
|PS2 Emulator
|[http://pcsx2.net/]
|high system requirements
|-
|Penumbra
|Survival Horror
|[http://frictionalgames.blogspot.com/2010/05/penumbra-overture-goes-open-source.html]
|high System requirements
|-
|PlaneShift
|MMORPG
|[http://www.planeshift.it/]
|requires to much ram
|-
|Revenge of the Titans
|RTS
|[http://www.puppygames.net/blog/?p=914]
|[http://www.puppygames.net/blog/?p=914 see License]
|-
|VDrift
|Racing
|[http://vdrift.net/]
|high System requirements
|-
|Xdriller
|Arcade
|[http://sourceforge.net/projects/xdriller/]
|Requires Ogre3D
|-
|Zero Ballistics
|FPS/tank
|[http://sourceforge.net/projects/zeroballistics/]
|high System requirements
|-
|}
[[Category:Development]]
[[Category:Community]]
[[Category:Ports]]
[[Category:List]]

Port Requests

2013-10-16T13:00:22Z

Levi: /* Games */ Marking BitFighter as ported

'''Some requests have and may not appear on this list'''

* [http://www.gp32x.com/board/index.php?showtopic=47518 Emulator Plausibility List] - A semi-speculative list of which systems the Pandora is likely to emulate, along with status of active emulation projects.
* [http://www.gp32x.com/board/index.php?showtopic=43659 Closed Source Projects] - A list of closed source / commercial projects that have shown interest / disinterest in the Pandora platform.
* [http://www.gp32x.com/board/index.php?showtopic=43532 Port Requests] - A catch-all thread for all of the "Wouldn't it be cool if Pandora ran XXXX?" posts.

If you have a port request, you may add it to this page. If a developer likes the look of it, it might get picked up. Before adding your request, please follow these steps:

*Check that your request is not already ported or under development on the Repo or in the forums
*Determine if the request is viable using [http://www.gliffy.com/publish/1448256/ this flowchart]; if not, move to "improbable"
*Requests need a link to source code
*Observe alphabetical and categorical order
==Possible==
===Games===
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
!Name
!Game Type
!Link to Source
!Remarks
|-
|Adonthell
|RPG
|[http://adonthell.nongnu.org/index.shtml]
|
|-
|Alien Arena
|FPS
|[http://icculus.org/alienarena/rpa/]
|old alien movie aesthetic
|-
|Angstron 2
|FPS
|[http://angstron2.garage.maemo.org/]
|runs on Nokia N770, N800, and N810
|-
|AnUntitledStory
|Metroidvania
|[http://www.mattmakesgames.com/]
|Really nice Metroidvania style adventure game.
|-
|Apprentice 2
|Card
|[http://sourceforge.net/projects/apprentice2/]
|
|-
|Area 2048
|Shmup
|[http://homepage2.nifty.com/isshiki/prog_win_d.html]
|Fast-paced arena shooter
|-
|AssaultCube
|FPS
|[http://assault.cubers.net/]
|team oriented multiplayer
|- style="background: #90FF90"
|Bitfighter
|Puzzle
|[http://repo.openpandora.org/?page=detail&app=bitfighter]
|2-D space combat with retro graphics, Robotron-like controls and customizable ships
|-
|Blobwars2
|TPS
|[http://sourceforge.net/projects/blobandconquer/]
|aka Blob Wars:Blob And Conquer
|-
|Block Attack - Rise of the Blocks
|BlocksGame
|[http://blockattack.sourceforge.net]
|Switch with neighbour left/right (also via gravity into gap). Control via keys.
|-
|BlueFury
|?
|[http://sourceforge.net/projects/bluefury/]
|
|-
|bsdgames
|Terminal-based
|[http://packages.debian.org/lenny/bsdgames]
|
|-
|BZFlag
|FPS
|[http://bzflag.org/]
|designed for mouse+keyboard
|-
|Cube 1
|FPS
|[http://cubeengine.com/cube.php4]
|(works with lunixbochs' GL shim)
|-
|Cube 2: Sauerbraten
|FPS
|[http://sourceforge.net/projects/sauerbraten/]
|Works (and has good framerates) with lunixbochs' GL shim.
|-
|Coldest
|mech
|[http://sourceforge.net/projects/coldestgame/]
|
|-
|Crack Attack
|Puzzle
|[http://www.nongnu.org/crack-attack/]
|inspired by Tetris Attack
|-
|ctp2
|Strategy
|[http://ctp2.darkdust.net/]
|Civilization:Call To Power 2
|-
|-
|Cubosphere
|Puzzle
|[http://sourceforge.net/projects/cubosphere/]
|Freeware game similar to the PSX game "Kula World" / "Roll Away".Platform independent, written in C++ and using OpenGL, SDL, libjpeg, LUA, GLSL-Shader.
|-
|Cytadela
|FPS
|[http://cytadela.sourceforge.net]
|Conversion of Amiga FPS created by Virtual Design in mid 1990's
|-
|Danger from the Deep
|?
|[http://sourceforge.net/projects/dangerdeep/]
|WW2 German submarine 3d simulation
|-
|Dawn
|RPG
|[http://dawn-rpg.sourceforge.net/wiki/index.php/Main_Page]
|
|-
|Dash Border
|Shmup
|[http://homepage2.nifty.com/isshiki/prog_linux_game.html]
|Arena shmup with focus on lots of speed
|-
|DTXmania
|Rhythm
|[http://en.sourceforge.jp/projects/dtxmania/]
|Japanese
|-
|Egoboo
|dungeon crawl
|[http://egoboo.sourceforge.net/]
|<10 fps with libGL
|-
|Emilia Pinball
|Pinball
|[http://pinball.sourceforge.net/]
|Uses the Allegro renderer, and should thus be easily portable, according to [http://boards.openpandora.org/index.php?/topic/1717-visual-pinball-went-opensource/page__view__findpost__p__105625 lunixbochs]
|-
|Empty Clip
|Action-RPG
|[http://emptyclip.sourceforge.net/]
|
|-
|Fabled Lands App
|Gamebook
|[http://flapp.sourceforge.net/]
|Java
|-
|Fall of Imiryn
|RPG
|[http://annchienta.sourceforge.net/?page=fall_of_imiryn]
|
|-
|FlightGear
|Flight sim
|[http://www.flightgear.org/]
|
|-
|Fofix
|Music
|[http://code.google.com/p/fofix/]
|Fret on fire fork
|-
|FooBillard
|Sports
|[http://foobillard.sourceforge.net/]
|
|-
|FreeOrion
|TBS
|[http://freeorion.org/]
|inspired by Master of Orion
|-
|Free Tennis
|Sports
|[http://freetennis.sourceforge.net/]
|
|-
|Funguloids
|Arcade,Puzzle
|[http://funguloids.sourceforge.net/]
|
|-
|Game Of Bases
|RTS
|[http://www.modeemi.cs.tut.fi/~flux/goba/]
|Flash Attack remake
|-
|Glest
|RTS
|[http://sourceforge.net/projects/glest/]
|
|-
|GNU shogi
|board
|[http://www.cs.caltech.edu/~mvanier/hacking/gnushogi/gnushogi.html]
|computer shogi
|-
|Hedgewars
|Artillery
|[http://www.hedgewars.org/]
|Worms clone
|-
|Heroes
|arcade
|[http://sourceforge.net/projects/heroes/]
|like tron
|-
|Heroes of Allacrost
|RPG
|[http://www.allacrost.org/]
|Requires GL, glu, openal, lua, sdl_ttf
|-
|Helena The 3rd
|action-platforming
|[https://code.google.com/p/helenathe3rd/]
|inspired by Blaster Master
|-
|iiChantra P.E.A.R. DSO
|Action, Platform
|[http://iichantra.ru/files/pear-dso-src1.2.zip]
|Contra-inspired game with original gameplay and retro-style graphics and music, sequel of iiChantra P.E.A.R.
Previous iiChantra games exist, [http://iichantra.ru/downloads/ first part of P.E.A.R. and Halloween version].
|-
|Jack-Claw
|Action
|[https://code.google.com/p/jack-claw/]
|
|-
|Kiki the Nano Bot
|Puzzle
|[http://kiki.sourceforge.net/]
|mixture of Sokoban and Kula World
|-
|Kollision (from the KDE game pack)
|Arcade
|[http://games.kde.org/game.php?game=kollision]
|Dodge more and more balls. Desktop control via mouse, desirable if Panda conversion could use nub, dpad or touchscreen.
|-
|Kurok
|FPS
|[http://www.bladebattles.com/kurok/files.html]
|
|-
|Knyttds
|Platformer
|[http://code.google.com/p/knyttds/]
|
|-
|L-Echo
|Puzzle
|[http://code.google.com/p/l-echo/]
|Echochrome clone
|-
|LinWarrior
|mech
|[http://www.hackcraft.de/games/linwarrior_3d/downloads.htm]
|
|-
|Lips of Suna
|dungeon crawl
|[http://lipsofsuna.org/]
|
|-
|LOCKJAW
|puzzle
|[http://www.pineight.com/lj/]
|tetris
|-
|LordsAWar
|TBS
|[http://www.nongnu.org/lordsawar/]
|Warlords II clone
|-
|Lunar Lander
|?
|[http://www.doof.me.uk/lunar-lander/]
|Lunar Lander Clone
|-
|Marfitude
|Music
|[http://www.erestar.net/games/marfitude/]
|loads a music file and turns it into a level. Graphics coded in SDL
|-
|M.A.R.S.
|shmup
|[http://mars-game.sourceforge.net/]
|
|-
|Masashikun Hi
|Arcade
|[http://www.asahi-net.or.jp/~cs8k-cyu/free/mas_e.html]
|stick figure olympics from Kenta Cho (ABA Games)
|-
|Megamek
|TBS
|[http://sourceforge.net/projects/megamek/]
|
|-
|MegaZeux
|Arcade
|[http://sourceforge.net/projects/megazeux/]
|game creation system
|-
|Micropolis
|City sim
|[http://www.donhopkins.com/home/micropolis/]
|sim city
|-
|Microwar
|Arcade
|[http://microwar.sourceforge.net/]
|Space Invaders clone in the cruel world of micro-compter industry
|-
|MotoGT
|Racing
|[http://motogt.sourceforge.net/]
|motorcycles
|-
|Mu-cade
|shmup
|[http://www.asahi-net.or.jp/~cs8k-cyu/windows/mcd_e.html]
|from Kenta Cho (ABA Games)
|-
|Netrek
|Star Trek themed battle sim
|[http://netrek.org]
|-
|Neverball
|Puzzle
|[http://neverball.org/]
|similar to Super Monkey Ball
|-
|Nikki and the Robots
|platformer
|[http://joyridelabs.de/game/code/]
|
|-
|Nimuh
|Puzzle
|[http://sourceforge.net/projects/nimuh/]
|based in the "Theseus and the Minotaur Mazes"
|-
|NPRQuake
|FPS
|[http://research.cs.wisc.edu/graphics/Gallery/NPRQuake/]
|Non-PhotoRealistic rendering of GLQuake
|-
|Oolite
|space sim
|[http://www.oolite.org/]
|
|-
|Open Invaders
|Arcade
|[http://www.jamyskis.net/invaders.php]
|Another Space Invaders clone, as Classic Invaders (from the repo) is not enough arcade/action like. Would prefer even something better than Open Invaders.
|-
|open-ig
|RTS
|[http://code.google.com/p/open-ig/]
|Java clone of "Imperium Galactica" by Digital Reality
|-
|openBVE
|Train sim
|[http://openbve.trainsimcentral.co.uk/]
|
|-
|OpenDungeons
|RTS
|[http://opendungeons.sourceforge.net/index.php/Main_Page]
|Dungeon Keeper clone
|-
|Paraball
|Sports
|[http://dl.openhandhelds.org/cgi-bin/gp32.cgi?0,0,0,0,48,629]
|Simple volleyball game.uses Fenix
|-
|Pax Britannica
|RTS
|[http://paxbritannica.henk.ca/]
|
|-
|Performous
|Music
|[http://sourceforge.net/projects/performous/]
|Karaokee,Guitar,drum,DDR
|-
|Pioneer Space Sim
|space sim
|[http://pioneerspacesim.net/]
|A game of lonely space adventure.
|-
|Privateer Gemini Gold
|space sim
|[http://sourceforge.net/projects/privateer/]
|patterned after original Wing Commander Privateer and uses Vegastrike engine
|-
|Pseudoform
|FPS
|[http://www.pseudoform.org/]
|portal clone
|-
|Race For The Galaxy AI
|Board
|[http://www.keldon.net/rftg/]
|Probably needs minor UI tweaks for everything to fit
|-
|Red Eclipse
|FPS
|[http://www.redeclipse.net/]
|uses cube2 engine
|-
|S.C.O.U.R.G.E. Heroes of Lesser Renown
|RPG
|[http://www.scourgeweb.org/]
|3D rogue-like
|-
|Scorched3D
|Artillery
|[http://www.scorched3d.co.uk/]
|based on Scorched Earth
|-
|Secret Maryo Chronicles
|Platformer
|[http://www.secretmaryo.org/index.php?page=about]
|
|-
|Shadowgrounds
|action
|[http://code.google.com/p/shadogrounds-and-shadowgrounds-survivor/]
|Shadowgrounds" and "Shadowgrounds: Survivor
|-
|Simulate (a Simon clone)
|Memory, Puzzle
|[http://inventwithpython.com/simulate.py]
|Python PyGame library
|-
|Skulltag
|fps
|[http://vega.skulltag.com/2010/03/skulltag-source-code-released/]
|doom with multiplayer focus
|-
|Sleep Is Death
|RPG
|[http://www.sleepisdeath.net/]
|2 player only
|-
|Smash Battle
|Platformer
|[http://sourceforge.net/projects/smashbattle/]
|
|-
|Smokin'Guns
|FPS
|[http://sourceforge.net/projects/smokinguns/]
|
|-
|Soulfu
|RPG
|[http://soulfu.motherhamster.org/]
|[http://www.gp32x.com/board/index.php?/topic/55339-testing-blobwars-soulfu port attempt] was unsuccessful
|-
|SpaceTrader
|FPS,Strategy
|[http://sourceforge.net/projects/palmtrader/]
|
|-
|Speed Dreams
|Racing
|[http://speed-dreams.sourceforge.net/]
|TORCS fork
|-
|Summoning Wars
|RPG
|[http://sumwars.org/]
|port should be possible, main issue is some excessive memory use
|-
|Sunbeam
|RPG
|[http://dl.openhandhelds.org/cgi-bin/gp32.cgi?0,0,0,0,46,1048]
|Abandoned project for the gp32
|
|-
|Tester Phase One
|Shmup
|[http://homepage2.nifty.com/isshiki/prog_win_game.html]
|Vertical shmup
|-
|Thunder&Lightning
|Flight sim
|[http://tnlgame.net/]
|
|-
|T.o.M.E.
|RPG
|[http://sourceforge.net/projects/pernband/]
|
|-
|Torus Trooper
|shmup
|[http://www.asahi-net.or.jp/~cs8k-cyu/windows/tt_e.html]
|Gyruss like tube shooter with focus on speed from Kenta Cho (ABA Games)
|-
|Trackballs
|Puzzle
|[http://trackballs.sourceforge.net/download.shtml]
|
|-
|Tremulous
|FPS+RTS
|[http://tremulous.net/]
|
|-
|UFO:AI
|TBS
|[http://sourceforge.net/projects/ufoai/]
|
|-
|Ultimate Stunts
|Racing
|[http://sourceforge.net/projects/ultimatestunts/]
|3D Racing with focus on settings times and making tracks
|-
|Vertigo
|arcade
|[http://www.vertigo-game.com/]
|
|-
|violetland
|shooter
|[http://code.google.com/p/violetland/]
|top down
|-
|Warlock's Gauntlet
|shooter
|[http://www.musztardasarepska.pl/wgdown/index.php?lang=en]
|
|-
|Warsow
|FPS
|[http://www.warsow.net/]
|requirements similar to Quake 3
|-
|WFTO
|Strategy
|[http://warfortheoverworld.org/downloads/]
|NBKE fork
|-
|Wok
|Arcade
|[http://www.asahi-net.or.jp/~cs8k-cyu/linux/wok_e.html]
|ball tossing game from Kenta Cho (ABA Games)
|-
|World of Padman
|FPS
|[http://padworld.myexp.de/index.php?files=mapping]
|creative death-match weapons and models
|-
|Xonotic
|FPS
|[http://www.xonotic.org/]
|Nexuiz fork [http://forums.xonotic.org/showthread.php?tid=1427 lightweight version]
|-
|Yoda Soccer
|Sports
|[http://yodasoccer.sourceforge.net/]
|gameplay and style of Sensible World of Soccer (a.k.a. SWOS)
|-
|ZEQ2 Lite
|Fighting
|[http://zeq2.com/lite/?page_id=33]
|
|-
|Z-LOCK
|Shmup
|[http://homepage2.nifty.com/isshiki/prog_win_d.html]
|Vertical shmup with focus on lock-on mechanic
|-
|}

===Emulators===
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
!Name
!System
!Link to Source
!Remarks
|-
|B-EM
|BBC Micro
|[http://b-em.bbcmicro.com/]
|[http://stardot.org.uk/forums/viewtopic.php?f=4&t=3830 Compiling B-em 2.1+ for Linux], [http://stardot.org.uk/forums/viewtopic.php?f=4&t=1986 GP2X port]
|-
|Mini vMac
|Macintosh Plus
|[http://sourceforge.net/projects/minivmac/]
|There is an ARM Linux binary available, and I did get it to run on the Pandora quite smoothly, but I have no means to put it into a PND.
|-
|Reality Boy
|Virtual Boy
|[http://www.goliathindustries.com/vb/VBDown.html]
|Runs, but slow and without sound in linux :( - Needs Allegro
|-
|TwoMbit
|Sega Master System
|[http://sourceforge.net/projects/twombit/]
|-
|Uzem
|Uzebox
|[http://uzebox.org/wiki/index.php?title=Emulator]
|
|-
|}

===Game Engines===
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
!Name
!Engine Type
!Link to Source
!Remarks
|-
|Colditz Escape
|Escape From Colditz
|[http://sites.google.com/site/colditzescape/]
|
|-
|Doomsday
|Doom,Heretic and Hexen
|[http://dengine.net/]
|
|-
|DreamZZT
|ZZT interpreter
|[http://dev.c99.org/DreamZZT/]
|
|-
|ezQuake
|Quakeworld
|[http://sourceforge.net/projects/ezquake/]
|QuakeWorld client
|-
|FIFE
|Isometric
|[http://fifengine.de]
|
|-
|Freeprince
|Prince of Persia
|[http://www.princed.org]
|
|-
|FreeRA
|Command&Conquer/Red Alert
|[http://freera.sourceforge.net/]
|
|-
|FSOpen
|FreeSpace 2
|[http://scp.indiegames.us/]
|FreeSpace and FreeSpace 2 were ported using different code base
|-
|lwjgl
|Input,Sound,Graphics
|[http://java-game-lib.svn.sourceforge.net/viewvc/java-game-lib/]
|Requires compilation of native library->OGL2.0 wrappers needed
|-
|Newton Game Dynamics
|Physics
|[http://newtondynamics.com]
|Demos are being ported from MFC to Qt
|-
|Novashell
|Lua-based 2D Game/Creation
|[http://www.rtsoft.com/novashell/]
|Author interested in Pandora
|-
|OHRRPGCE
|2D RPG
|[http://en.wikipedia.org/wiki/OHRRPGCE]
|
|-
|OpenDarkEngine
|Dark Engine
|[http://sourceforge.net/projects/opde/]
|
|-
|OpenMOHAA
|FPS
|[http://sourceforge.net/projects/openmohaa/]
|Medal of Honor: Allied Assault
|-
|openmw
|The Elder Scrolls III: Morrowind
|[http://openmw.com/wiki/index.php?title=Main_Page]
|
|-
|PONScripter
|visual novel
|[http://unclemion.com/onscripter/]
|Proportional-OnScripter a heavy modified fork of ONScripter-EN that is deliberately backwards-incompatible with ONScripter-EN.
Narcissu: Side 2nd was ported to this engine.
|-
|SLUDGE
|2D Adventure creation
|[http://sourceforge.net/projects/opensludge/develop]
|Already has OpenGL ES 2 support. Development kit and engine available in Debian/Ubuntu and for Mac/Windows.
|-
|Sphere
|Game Creation
|[http://en.wikipedia.org/wiki/Sphere_%28program%29]
|
|-
|Syntensity
|multiplayer 3D
|[http://www.syntensity.com/]
|
|-
|TA3D
|Total Annihilation remake
|[http://www.ta3d.org/cquoi-en.php]
|
|-
|Zod
|Zod Recreation with multiplayer focus
|[http://zod.sourceforge.net/]
|
|-
|}

===Other programs===
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
!Name
!App Type
!Link to Source
!Remarks
|-
|Aldrin
|MIDI Sequencer
|[http://code.google.com/p/aldrin-sequencer/]
|
|-
|Ardour
|DAW
|[http://www.ardour.org/]
|
|-
|Art of Illusion
|3D modeling
|[http://sourceforge.net/projects/aoi/]
|Java
|-
|BlueGriffon
|WYSIWYG web editor
|[http://bluegriffon.org/]
|
|-
|Calligra Suite
|office
|[http://www.calligra-suite.org/]
|koffice fork
|-
|Celestia
|space simulation
|[http://www.shatters.net/celestia/]
|
|-
|Clementine
|Music Manager
|[http://www.clementine-player.org/]
|Amarok 1.4 forked+ported to Qt4 and GStreamer
|-
|Dropbox
|File Management
|[http://www.dropbox.com/downloading?os=lnx]
|There is a [https://github.com/andreafabrizi/Dropbox-Uploader shell script] to upload, download, delete and list files from Dropbox.
|-
|Ease
|presentation
|[http://www.ease-project.org/download.html]
|
|-
|Freecad
|3D CAD modeler
|[http://sourceforge.net/projects/free-cad/]
|
|-
|FreeSpeak
|translator
|[http://freespeak.berlios.de/]
|
|-
|Gajim
|Instant messaging
|[http://gajim.org/downloads.php?lang=en#tarball]
|
|-
|Gcstar
|library management
|[http://wiki.gcstar.org/en/]
|
|-
|Gnash
|flash
|[http://www.gnashdev.org/]
|
|-
|-
|Gnome Disk Utility
|Manage storage devices - format, partition, file system check, benchmark test, etc
|[http://git.gnome.org/browse/gnome-disk-utility]
|If Pandora users want to compare SD card speeds, benchmark tests only make sense on the target device (the Pandora itself). I propose to port this one, as it has all necessary functions in an easy interface. --[[User:Porg|Porg]] 00:14, 19 July 2011 (CEST)
|-
|Gnomeradio
|Radio
|[http://projects.gnome.org/gnomeradio/]
|Gnomeradio is a FM-radio tuner for the GNOME desktop (version 1 and 2). It should work with every FM tuner card that is supported by video4linux.
|-
|Gnote
|notetaking
|[http://live.gnome.org/Gnote]
|c++ tomboy clone
|-
|GnoTime
|TODO list/diary/journal
|[http://gttr.sourceforge.net/]
|
|-
|GNU Radio
|Radio
|[http://gnuradio.org/]
|GNU Radio is a free software toolkit for learning about, building, and deploying software-defined radio systems. Version needed: 3.5.1 or higher.
|
|-
|Gnucap
|Circuit Simulation
|[http://http://gnucap.org/]
|General purpose circuit simulator. It performs nonlinear dc and transient analyses, fourier analysis, and ac analysis.
|
|-
|Gobby
|Collaborative editor
|[http://gobby.0x539.de/trac/]
|
|-
|GoogSysTray
|System tray
|[http://sourceforge.net/projects/googsystray/]
|
|-
|Gramps
|Genealogical research
|[http://gramps-project.org/download/]
|
|-
|Gtrainer
|Health
|[http://kutxa.homeunix.org/gtrainer/index-en.html]
|
|-
|Gummi
|WYSIWYG ''LATEX'' editor
|[http://gummi.midnightcoding.org/]
|Live preview pane for document
|-
|gwibber
|microblogging client
|[http://gwibber.com/]
|
|-
|Handbrake
|video transcoder
|[http://handbrake.fr/]
|
|-
|HTTrack
|Offline reader/Web crawler
|[http://www.httrack.com/]
|
|-
|Hydrogen
|drum machine
|[http://www.hydrogen-music.org/]
|
|-
|Jokosher
|multi-track studio
|[http://www.jokosher.org/]
|
|-
|Kazam
|screen capture
|[https://launchpad.net/kazam]
|
|-
|Kismet
|network detector,packet sniffer,intrusion detection
|[http://www.kismetwireless.net/]
|
|-
|Kolourpaint
|Pixel graphics editor
|[http://www.kolourpaint.org/]
|
|-
|KStars
|Desktop Planetarium Software
|[http://edu.kde.org/applications/all/kstars]
|
|-
|KToon
|2D Animation
|[http://www.ktoon.net/]
|Port requires gui changes
|-
|LilyPond
|Musical Score Editor & Engraver
|[http://lilypond.org]
|
|-
|Maemo Mapper
|geographical mapping
|[https://garage.maemo.org/projects/maemo-mapper/]
|designed for 800 × 480
|-
|Marble
|digital globe
|[http://edu.kde.org/marble/]
|
|-
|Maxima
|Math
|[http://maxima.sourceforge.net/]
|
|-
|Miro
|Internet television
|[http://www.getmiro.com/]
|
|-
|Mixxx
|DJ mixing software
|[http://www.mixxx.org/download.php]
|[http://www.mixxx.org/wiki/doku.php/dependencies Dependencies]. There is an 800x480 skin called [http://www.mixxx.org/forums/viewtopic.php?f=8&t=2430 Outline].
|-
|Mosaic-CK
|browser
|[http://www.floodgap.com/retrotech/machten/mosaic/]
|NCSA Mosaic
|-
|MySQL Workbench
|MySql Database Tools (remote DB administration)
|[http://wb.mysql.com/?page_id=152]
|
|-
|Nathive
|image editor
|[http://www.nathive.org/]
|
|-
|OpenAstro.org
|natal chart generator
|[http://openastro.org/?Download]
|
|-
|Open-rp
|Remote Play
|[http://code.google.com/p/open-rp/]
|Remotely play PS3
|-
|OpenShot
|movie editor
|[http://www.openshot.org/]
|
|-
|PCB
|printed circuit board editor
|[http://pcb.gpleda.org/]
|
|-
|puddletag
|audio tag editor
|[http://puddletag.sourceforge.net/index.html]
|
|-
|Qucs
|Circuit Simulation
|[http://qucs.sourceforge.net/index.html]
|Qucs is an integrated circuit simulator which means you are able to setup a circuit with a graphical user interface (GUI) and simulate the large-signal, small-signal and noise behaviour of the circuit. After that simulation has finished you can view the simulation results on a presentation page or window. Uses QT.
|-
|RedNotebook
|Diary/Journal
|[http://digitaldump.wordpress.com/projects/rednotebook/]
|
|-
|Recipe Manager
|Recipe Manager
|[https://launchpad.net/recipe-manager]
|
|-
|Rosegarden
|sequencer, score editor, composition and editing
|[http://www.rosegardenmusic.com/]
|
|-
|Rubrica
|address book
|[http://freshmeat.net/projects/rubrica/]
|
|-
|scribus
|page layout
|[http://www.scribus.net/]
|
|-
|Shotwell
|photo manager
|[http://yorba.org/shotwell/]
|
|-
|Stellarium
|Virtual Planetarium
|[http://www.stellarium.org/]
|
|-
|TangoGPS
|GPS
|[http://www.tangogps.org/]
|[http://www.angstrom-distribution.org/repo/?pkgname=tangogps Anstrom Repo] [http://www.gp32x.com/board/index.php?/topic/54520-bluetooth-gps-and-tangogps/ pandora]
|-
|Tilda
|Quake style terminal
|[http://tilda.sourceforge.net/wiki/index.php/Main_Page]
|
|-
|Tor
|Anonymity network
|[https://www.torproject.org/download/download.html.en#source]
|
|-
|Traverso DAW
|Multitrack audio recording & editing
|[http://traverso-daw.org/]
|
|-
|TuxGuitar
|multitrack guitar tablature editor & player
|[http://sourceforge.net/projects/tuxguitar/]
|
|-
|Zynaddsubfx
|Software Synthesizer
|[http://sourceforge.net/projects/zynaddsubfx/]
|
|-
|}

==Improbable==
programs with available source code that are unlikely to be ported
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
!Name
!App Type
!Link to Source
!Reason
|-
|0AD
|RTS
|[http://wildfiregames.com/0ad/page.php?c=46]
|high System requirements
|-
|Ardentryst
|Action-RPG
|[http://sourceforge.net/projects/ardentryst/]
|high System requirements
|-
|Arx Fatalis
|Action-RPG
|[http://arx.parpg.net/]
|There is a openGL port (https://github.com/arx/ArxLibertatis). It's far too resource-intensive with glshim.
|-
|Capitán Sevilla
|Platformer
||[http://computeremuzone.com/ficha.php?id=754&l=en]
|runs very slow at 1000Mhz, works only with swap, needs too much ram
|-
|Dolphin
|Gamecube Emulator
|[http://www.dolphin-emulator.com/]
|high System requirements
|-
|Pcsx 2
|PS2 Emulator
|[http://pcsx2.net/]
|high system requirements
|-
|Penumbra
|Survival Horror
|[http://frictionalgames.blogspot.com/2010/05/penumbra-overture-goes-open-source.html]
|high System requirements
|-
|PlaneShift
|MMORPG
|[http://www.planeshift.it/]
|requires to much ram
|-
|Revenge of the Titans
|RTS
|[http://www.puppygames.net/blog/?p=914]
|[http://www.puppygames.net/blog/?p=914 see License]
|-
|VDrift
|Racing
|[http://vdrift.net/]
|high System requirements
|-
|Xdriller
|Arcade
|[http://sourceforge.net/projects/xdriller/]
|Requires Ogre3D
|-
|Zero Ballistics
|FPS/tank
|[http://sourceforge.net/projects/zeroballistics/]
|high System requirements
|-
|}
[[Category:Development]]
[[Category:Community]]
[[Category:Ports]]
[[Category:List]]

Boot setup

2013-10-14T02:24:47Z

Levi:

This guide assumes you have got the operating system of choice at the ready.

==Partition your SD card==

This is an optional step for cards<=32GB formatted to FAT32. It may be a good idea to set up multiple partitions/slices on your SD card - reasons include wanting to include a separate first partition for use on Windows, having a swap partition, or separating your kernel image from your root filesystem in case of filesystem corruption.

If you do want to slice your SD card into several partitions (see [[#Setting_up_mutliple-partition_SD_cards_for_booting|Setting up mutliple-partition SD cards]]), you can use the ''cfdisk'' command-line tool on the Pandora to create a partition table, or you can also download and use the [http://repo.openpandora.org/?page=detail&app=gparted-gparted graphical tool ''gparted''].

Note that - as of Zaxxon HF5 - the Pandora firmware doesn't have a command to format FAT partitions, so if you want to use the FAT/ext2/swap - scheme, you'll have to format the first partition on another system later on (under Windows, use the Disk Management tool).

===Using ''cfdisk''===

Assuming your card is in the left slot:

<source lang="bash">sudo cfdisk -z /dev/mmcblk0</source>

'''WARNING: mmcblk0 will [http://bugs.openpandora.org/index.php?do=details&task_id=237 not necessarily be the left slot]. It's the first card that the system recognizes, which is ''usually'' the left slot (but not if you inserted an SD into the left slot after you had one in the right slot, for example). Please make sure before you do anything dangerous e.g. use 'mount' to see what filesystems you recognise are mounted from where.'''

cfdisk -z starts off with a clean partition table - if you want to see what's set up currently, use ''cfdisk /dev/mmcblk0''.

Use only primary partitions (so you're limited to four slices).

===Using ''gparted''===

Download the gparted PND and install it. Note: this generally requires having a second SD card to install it to, though it should be possible to install it to the /pandora folder in your filesystem root, which will install it to NAND.

Find the program under 'System' in the menu and launch it. '''WARNING: It will start off pointing at /dev/mmcblk0 which is ''usually'' your left slot, but may not be.''' You can switch between the two card slots (if you have a card in each) and deduce which is which from the graphical display and the partition labels, but '''please be sure before applying any changes'''. Selecting 'information' from the right-click menu will also show you where each partition is mounted on the root filesystem, if it is currently mounted.

If the system has automounted the existing partition it'll show as locked and you'll need to unmount it using the right-click menu before you'll be able to change it. In this case, you'll probably want to delete it and create new partitions. Note that whatever partition your end up installing your boot/autoboot.txt to must be either ext2 or FAT, but you have a freer choice of filesystems to use on other partitions.

Once you've decided on your partitions and marked up the changes you'll need to apply them. Use the '''Apply All Operations''' menu item from the '''Edit''' menu. Then sit back and wait as it repartitions and reformats your card.

==Format SD card==

If you didn't use '''gparted''' to partition and format your card, you need to format your SD card to have at least an ext2 partition; ext3 also works[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/] and is more reliable[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/page-5#entry901072]. You can have additional paritions, such as swap partition, as well if you like.

===Using the command line===
Take care with using these command line tools, to be certain you are accessing the correct device. They will not ask you and will DESTROY any data on the device. This command will replace an existing partition with an empty EXT2 formatted filesystem (this includes the single FAT partition most SD cards come shipped with). Assuming ''/dev/mmcblk0p1'' for your SD device (left slot, first partition), ''LABELNAME'' for the partition:
<source lang="bash">
mkfs.ext2 -L LABELNAME /dev/mmcblk0p1
</source>
or
<source lang="bash">
mkfs.ext3 -L LABELNAME /dev/mmcblk0p1
</source>
If you run into problems with formatting the SD card, try unmounting it first:
<source lang="bash">
sudo umount /media/[LABELNAME of SD card]
</source>

==Copy the files to your SD card==
Navigate (cd) to the directory with the .tar.bz2 file you just downloaded (or made) and do:

<source lang="bash">
sudo tar -xvjf <tarfile>.tar.bz2 -C <SD card>
</source>

If you're doing this on your Pandora, <SD card> is something like /media/mmcblk0p1 (first SD card slot on Pandora). On Ubuntu it would be something like /media/disk if it has no label. You can also try using GUI tools for this, but I didn't have very good luck with them.

===OR copy your firmware from the NAND to the SD card===

The following will ask for your password. All the operations need root permissions so I thought it would be wasteful to sprinkle sudo to everything.
We will bind mount the root fs to an alternative location ("/mp"), under which other filesystems mounted under root (like the kernel virtual filesystems /proc and /sys, and your SD card.) wont be visible. This allows us to take a live copy of the NAND contents to the SD filesystem.

<source lang="bash">
sudo su
mkdir /mp
mount --bind / /mp
cp -va /mp/* /media/<SD card>
umount /mp
rmdir /mp
exit
</source>

==Set up your boot.txt==

Create a new file called boot.txt (or autoboot.txt if you want to boot automatically) and copy and paste the text below. Copy that file to the root of the root of the SD card.

{{warning
|If you edit the file on Windows, use an advanced text editor like [http://notepad-plus-plus.org/ Notepad++] and be sure to convert to UNIX format (in NP++: Edit -> EOL Conversion -> UNIX format). If you have DOS linebreaks, ext2load will fail with an error like "file not found" as it appends an hidden character to the uImage file name.
}}boot.txt (from the [http://openpandora.org/firmware/README.txt official firmware site])
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0 0x80300000 /boot/uImage
bootm 0x80300000
</source>
Note: If you chose ext3 instead of ext2 for the partition containing the kernel, the second line still starts with ext2load. There is no ext3load.

Note: depending on firmware version kernels might be at several, sometimes multiple locations, so you have to choose one:
* /boot/uImage-3 - the default 3.2 kernel (recommended)
* /lib/boot/uImage - alternative location of 3.2 kernel on certain older firmwares
* /boot/uImage - mostly a symlink to the latest kernel on recent firmwares

Be aware though that this boot.txt assumes you have formatted your card with ext2 and loads the kernel off the SD card. It is technically possible to boot the kernel from NAND but still run the rest of the file system from your SD card with following boot.txt
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr} && boot
</source>
However this is not recommended because kernel modules on SD card will likely be not compatible with kernel on NAND.

Both boot.txt's assume you are booting from the left SD card slot, first partition. You can change "mmcblk0p1" to "mmcblk1p1" if you want to boot from the right slot (but boot.txt must still be on a card on the left slot).

===Setting up mutliple-partition SD cards for booting===

It is possible to have several partitions on the SD card and boot from one of them.
E.g. if you have three partitions on the card like this:
*Partition 1: FAT
*Partition 2: ext2 (where the rootfs should be placed)
*Partition 3: swap

How it's done:

1. Put uBoot's boot control files "boot.txt" and/or "autoboot.txt" into the root of the '''first partition''' of the card (FAT partition in this example)

2. Make "boot.txt" and "autoboot.txt" point U-Boot to the '''partition, which holds the root file system''' of your Linux system. This would be parition 2 in this example (ext2 FS).
This is done '''using the "root" parameter of setenv'''.

3. Make "boot.txt" and "autoboot.txt" point U-Boot to the correct '''location to boot your kernel from'''.
This kernel location can be any FAT or ext2/3/4 partition on the SD card.
The uBoot commands '''"fatload" and "ext2load" with their parameter "mmc x:y"''' are repsonsible for loading the kernel. Choose the command, which addresses the file system the kernel is located on and make sure to correctly adapt the values x and y.

This common example boots the kernel from the FAT partition (then this is a "boot partition"), and uses the ext2 file system as root FS:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
fatload mmc 0:1 0x80300000 uimage
bootm 0x80300000
</source>

If you put the kernel into the root file system's /boot directory, the second line would be different:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0:2 0x80300000 /boot/uImage
bootm 0x80300000
</source>

'''Note: '''

For both the "root=" kernel argument and the "mmc x:y" argument of the fatload/ext2load commands, slot numbering begins at 0 (0 is left SD slot, 1 is right SD slot) and partition numbering begins at 1!

'''Recommendation:'''

Put the kernel into another partition than the root FS is located.
Reason: In case the root FS partition is flagged "inconsistent" after a system crash or sudden SD card removal, uBoot won't be able to boot from that partition anymore. But the file system cleanup routines can only be run, once the kernel has been booted. Hence it's safer to put the kernel on a different partition.

==Boot the system==

As you power up the Pandora, hold the shoulder button R. A menu should appear, allowing you to boot from the SD card. (this step isn't necessary if you chose to create an autoboot.txt instead of boot.txt). Remember that this will be an un-configured image, taking a little while longer to boot, and giving the first-run dialogue.

==Access the NAND==
Once you're booted into the system from SD, you may want access to the NAND rootfs. The following will let you do that.
<source lang="bash">
sudo mkdir /mnt/nand
sudo ubiattach /dev/ubi_ctrl -m 4
sudo mount -t ubifs ubi0:rootfs /mnt/nand
</source>

==Other information==
An alternative approach to using an SD card to increase the space accessible to the system is [[Extend_Utils#OS_Extends | OS Extend]]. This allows the root filesystem to exist on more than one physical device.

==References==
*[http://www.rjmitchell.ca/~jeff/blog2009/2010/06/07/pandora-running-firmware-from-sd-card-instead-of-nand-flash/ Skeezix's blog]
*[http://openpandora.org/firmware/ Official firmware page]
*[http://repo.openpandora.org/?page=detail&app=sd-install-2011-03-10 The GUI-driven SD installer by David Boucher]

[[Category:Tutorials]]
[[Category:Booting]]
[[Category:Storage card]]
[[Category:Operating system]]

Boot setup

2013-10-14T02:21:32Z

Levi: /* References */

This guide assumes you have got the operating system of choice at the ready.

===Partition your SD card===

This is an optional step. It may be a good idea to set up multiple partitions/slices on your SD card - reasons include wanting to include a separate first partition for use on Windows, having a swap partition, or separating your kernel image from your root filesystem in case of filesystem corruption.

If you do want to slice your SD card into several partitions (see [[#Setting_up_mutliple-partition_SD_cards_for_booting|Setting up mutliple-partition SD cards]]), you can use the ''cfdisk'' command-line tool on the Pandora to create a partition table, or you can also download and use the [http://repo.openpandora.org/?page=detail&app=gparted-gparted graphical tool ''gparted''].

Note that - as of Zaxxon HF5 - the Pandora firmware doesn't have a command to format FAT partitions, so if you want to use the FAT/ext2/swap - scheme, you'll have to format the first partition on another system later on (under Windows, use the Disk Management tool).

====Using ''cfdisk''====

Assuming your card is in the left slot:

<source lang="bash">sudo cfdisk -z /dev/mmcblk0</source>

'''WARNING: mmcblk0 will [http://bugs.openpandora.org/index.php?do=details&task_id=237 not necessarily be the left slot]. It's the first card that the system recognizes, which is ''usually'' the left slot (but not if you inserted an SD into the left slot after you had one in the right slot, for example). Please make sure before you do anything dangerous e.g. use 'mount' to see what filesystems you recognise are mounted from where.'''

cfdisk -z starts off with a clean partition table - if you want to see what's set up currently, use ''cfdisk /dev/mmcblk0''.

Use only primary partitions (so you're limited to four slices).

====Using ''gparted''====

Download the gparted PND and install it. Note: this generally requires having a second SD card to install it to, though it should be possible to install it to the /pandora folder in your filesystem root, which will install it to NAND.

Find the program under 'System' in the menu and launch it. '''WARNING: It will start off pointing at /dev/mmcblk0 which is ''usually'' your left slot, but may not be.''' You can switch between the two card slots (if you have a card in each) and deduce which is which from the graphical display and the partition labels, but '''please be sure before applying any changes'''. Selecting 'information' from the right-click menu will also show you where each partition is mounted on the root filesystem, if it is currently mounted.

If the system has automounted the existing partition it'll show as locked and you'll need to unmount it using the right-click menu before you'll be able to change it. In this case, you'll probably want to delete it and create new partitions. Note that whatever partition your end up installing your boot/autoboot.txt to must be either ext2 or FAT, but you have a freer choice of filesystems to use on other partitions.

Once you've decided on your partitions and marked up the changes you'll need to apply them. Use the '''Apply All Operations''' menu item from the '''Edit''' menu. Then sit back and wait as it repartitions and reformats your card.

===Format SD card===

If you didn't use '''gparted''' to partition and format your card, you need to format your SD card to have at least an ext2 partition; ext3 also works[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/] and is more reliable[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/page-5#entry901072]. You can have additional paritions, such as swap partition, as well if you like.

====Using the command line====
Take care with using these command line tools, to be certain you are accessing the correct device. They will not ask you and will DESTROY any data on the device. This command will replace an existing partition with an empty EXT2 formatted filesystem (this includes the single FAT partition most SD cards come shipped with). Assuming ''/dev/mmcblk0p1'' for your SD device (left slot, first partition), ''LABELNAME'' for the partition:
<source lang="bash">
mkfs.ext2 -L LABELNAME /dev/mmcblk0p1
</source>
or
<source lang="bash">
mkfs.ext3 -L LABELNAME /dev/mmcblk0p1
</source>
If you run into problems with formatting the SD card, try unmounting it first:
<source lang="bash">
sudo umount /media/[LABELNAME of SD card]
</source>

===Copy and boot===

====Copy the files to your SD card====
Navigate (cd) to the directory with the .tar.bz2 file you just downloaded (or made) and do:

<source lang="bash">
sudo tar -xvjf <tarfile>.tar.bz2 -C <SD card>
</source>

If you're doing this on your Pandora, <SD card> is something like /media/mmcblk0p1 (first SD card slot on Pandora). On Ubuntu it would be something like /media/disk if it has no label. You can also try using GUI tools for this, but I didn't have very good luck with them.

====OR copy your firmware from the NAND to the SD card====

The following will ask for your password. All the operations need root permissions so I thought it would be wasteful to sprinkle sudo to everything.
We will bind mount the root fs to an alternative location ("/mp"), under which other filesystems mounted under root (like the kernel virtual filesystems /proc and /sys, and your SD card.) wont be visible. This allows us to take a live copy of the NAND contents to the SD filesystem.

<source lang="bash">
sudo su
mkdir /mp
mount --bind / /mp
cp -va /mp/* /media/<SD card>
umount /mp
rmdir /mp
exit
</source>

===Set up your boot.txt===

Create a new file called boot.txt (or autoboot.txt if you want to boot automatically) and copy and paste the text below. Copy that file to the root of the root of the SD card.

{{warning
|If you edit the file on Windows, use an advanced text editor like [http://notepad-plus-plus.org/ Notepad++] and be sure to convert to UNIX format (in NP++: Edit -> EOL Conversion -> UNIX format). If you have DOS linebreaks, ext2load will fail with an error like "file not found" as it appends an hidden character to the uImage file name.
}}boot.txt (from the [http://openpandora.org/firmware/README.txt official firmware site])
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0 0x80300000 /boot/uImage
bootm 0x80300000
</source>
Note: If you chose ext3 instead of ext2 for the partition containing the kernel, the second line still starts with ext2load. There is no ext3load.

Note: depending on firmware version kernels might be at several, sometimes multiple locations, so you have to choose one:
* /boot/uImage-3 - the default 3.2 kernel (recommended)
* /lib/boot/uImage - alternative location of 3.2 kernel on certain older firmwares
* /boot/uImage - mostly a symlink to the latest kernel on recent firmwares

Be aware though that this boot.txt assumes you have formatted your card with ext2 and loads the kernel off the SD card. It is technically possible to boot the kernel from NAND but still run the rest of the file system from your SD card with following boot.txt
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr} && boot
</source>
However this is not recommended because kernel modules on SD card will likely be not compatible with kernel on NAND.

Both boot.txt's assume you are booting from the left SD card slot, first partition. You can change "mmcblk0p1" to "mmcblk1p1" if you want to boot from the right slot (but boot.txt must still be on a card on the left slot).

====Setting up mutliple-partition SD cards for booting====

It is possible to have several partitions on the SD card and boot from one of them.
E.g. if you have three partitions on the card like this:
*Partition 1: FAT
*Partition 2: ext2 (where the rootfs should be placed)
*Partition 3: swap

How it's done:

1. Put uBoot's boot control files "boot.txt" and/or "autoboot.txt" into the root of the '''first partition''' of the card (FAT partition in this example)

2. Make "boot.txt" and "autoboot.txt" point U-Boot to the '''partition, which holds the root file system''' of your Linux system. This would be parition 2 in this example (ext2 FS).
This is done '''using the "root" parameter of setenv'''.

3. Make "boot.txt" and "autoboot.txt" point U-Boot to the correct '''location to boot your kernel from'''.
This kernel location can be any FAT or ext2/3/4 partition on the SD card.
The uBoot commands '''"fatload" and "ext2load" with their parameter "mmc x:y"''' are repsonsible for loading the kernel. Choose the command, which addresses the file system the kernel is located on and make sure to correctly adapt the values x and y.

This common example boots the kernel from the FAT partition (then this is a "boot partition"), and uses the ext2 file system as root FS:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
fatload mmc 0:1 0x80300000 uimage
bootm 0x80300000
</source>

If you put the kernel into the root file system's /boot directory, the second line would be different:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0:2 0x80300000 /boot/uImage
bootm 0x80300000
</source>

'''Note: '''

For both the "root=" kernel argument and the "mmc x:y" argument of the fatload/ext2load commands, slot numbering begins at 0 (0 is left SD slot, 1 is right SD slot) and partition numbering begins at 1!

'''Recommendation:'''

Put the kernel into another partition than the root FS is located.
Reason: In case the root FS partition is flagged "inconsistent" after a system crash or sudden SD card removal, uBoot won't be able to boot from that partition anymore. But the file system cleanup routines can only be run, once the kernel has been booted. Hence it's safer to put the kernel on a different partition.

==Boot the system==

As you power up the Pandora, hold the shoulder button R. A menu should appear, allowing you to boot from the SD card. (this step isn't necessary if you chose to create an autoboot.txt instead of boot.txt). Remember that this will be an un-configured image, taking a little while longer to boot, and giving the first-run dialogue.

==Access the NAND==
Once you're booted into the system from SD, you may want access to the NAND rootfs. The following will let you do that.
<source lang="bash">
sudo mkdir /mnt/nand
sudo ubiattach /dev/ubi_ctrl -m 4
sudo mount -t ubifs ubi0:rootfs /mnt/nand
</source>

==Other information==
An alternative approach to using an SD card to increase the space accessible to the system is [[Extend_Utils#OS_Extends | OS Extend]]. This allows the root filesystem to exist on more than one physical device.

==References==
*[http://www.rjmitchell.ca/~jeff/blog2009/2010/06/07/pandora-running-firmware-from-sd-card-instead-of-nand-flash/ Skeezix's blog]
*[http://openpandora.org/firmware/ Official firmware page]
*[http://repo.openpandora.org/?page=detail&app=sd-install-2011-03-10 The GUI-driven SD installer by David Boucher]

[[Category:Tutorials]]
[[Category:Booting]]
[[Category:Storage card]]
[[Category:Operating system]]

Boot setup

2013-10-14T02:20:08Z

Levi: /* Set up your boot.txt */

This guide assumes you have got the operating system of choice at the ready.

===Partition your SD card===

This is an optional step. It may be a good idea to set up multiple partitions/slices on your SD card - reasons include wanting to include a separate first partition for use on Windows, having a swap partition, or separating your kernel image from your root filesystem in case of filesystem corruption.

If you do want to slice your SD card into several partitions (see [[#Setting_up_mutliple-partition_SD_cards_for_booting|Setting up mutliple-partition SD cards]]), you can use the ''cfdisk'' command-line tool on the Pandora to create a partition table, or you can also download and use the [http://repo.openpandora.org/?page=detail&app=gparted-gparted graphical tool ''gparted''].

Note that - as of Zaxxon HF5 - the Pandora firmware doesn't have a command to format FAT partitions, so if you want to use the FAT/ext2/swap - scheme, you'll have to format the first partition on another system later on (under Windows, use the Disk Management tool).

====Using ''cfdisk''====

Assuming your card is in the left slot:

<source lang="bash">sudo cfdisk -z /dev/mmcblk0</source>

'''WARNING: mmcblk0 will [http://bugs.openpandora.org/index.php?do=details&task_id=237 not necessarily be the left slot]. It's the first card that the system recognizes, which is ''usually'' the left slot (but not if you inserted an SD into the left slot after you had one in the right slot, for example). Please make sure before you do anything dangerous e.g. use 'mount' to see what filesystems you recognise are mounted from where.'''

cfdisk -z starts off with a clean partition table - if you want to see what's set up currently, use ''cfdisk /dev/mmcblk0''.

Use only primary partitions (so you're limited to four slices).

====Using ''gparted''====

Download the gparted PND and install it. Note: this generally requires having a second SD card to install it to, though it should be possible to install it to the /pandora folder in your filesystem root, which will install it to NAND.

Find the program under 'System' in the menu and launch it. '''WARNING: It will start off pointing at /dev/mmcblk0 which is ''usually'' your left slot, but may not be.''' You can switch between the two card slots (if you have a card in each) and deduce which is which from the graphical display and the partition labels, but '''please be sure before applying any changes'''. Selecting 'information' from the right-click menu will also show you where each partition is mounted on the root filesystem, if it is currently mounted.

If the system has automounted the existing partition it'll show as locked and you'll need to unmount it using the right-click menu before you'll be able to change it. In this case, you'll probably want to delete it and create new partitions. Note that whatever partition your end up installing your boot/autoboot.txt to must be either ext2 or FAT, but you have a freer choice of filesystems to use on other partitions.

Once you've decided on your partitions and marked up the changes you'll need to apply them. Use the '''Apply All Operations''' menu item from the '''Edit''' menu. Then sit back and wait as it repartitions and reformats your card.

===Format SD card===

If you didn't use '''gparted''' to partition and format your card, you need to format your SD card to have at least an ext2 partition; ext3 also works[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/] and is more reliable[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/page-5#entry901072]. You can have additional paritions, such as swap partition, as well if you like.

====Using the command line====
Take care with using these command line tools, to be certain you are accessing the correct device. They will not ask you and will DESTROY any data on the device. This command will replace an existing partition with an empty EXT2 formatted filesystem (this includes the single FAT partition most SD cards come shipped with). Assuming ''/dev/mmcblk0p1'' for your SD device (left slot, first partition), ''LABELNAME'' for the partition:
<source lang="bash">
mkfs.ext2 -L LABELNAME /dev/mmcblk0p1
</source>
or
<source lang="bash">
mkfs.ext3 -L LABELNAME /dev/mmcblk0p1
</source>
If you run into problems with formatting the SD card, try unmounting it first:
<source lang="bash">
sudo umount /media/[LABELNAME of SD card]
</source>

===Copy and boot===

====Copy the files to your SD card====
Navigate (cd) to the directory with the .tar.bz2 file you just downloaded (or made) and do:

<source lang="bash">
sudo tar -xvjf <tarfile>.tar.bz2 -C <SD card>
</source>

If you're doing this on your Pandora, <SD card> is something like /media/mmcblk0p1 (first SD card slot on Pandora). On Ubuntu it would be something like /media/disk if it has no label. You can also try using GUI tools for this, but I didn't have very good luck with them.

====OR copy your firmware from the NAND to the SD card====

The following will ask for your password. All the operations need root permissions so I thought it would be wasteful to sprinkle sudo to everything.
We will bind mount the root fs to an alternative location ("/mp"), under which other filesystems mounted under root (like the kernel virtual filesystems /proc and /sys, and your SD card.) wont be visible. This allows us to take a live copy of the NAND contents to the SD filesystem.

<source lang="bash">
sudo su
mkdir /mp
mount --bind / /mp
cp -va /mp/* /media/<SD card>
umount /mp
rmdir /mp
exit
</source>

===Set up your boot.txt===

Create a new file called boot.txt (or autoboot.txt if you want to boot automatically) and copy and paste the text below. Copy that file to the root of the root of the SD card.

{{warning
|If you edit the file on Windows, use an advanced text editor like [http://notepad-plus-plus.org/ Notepad++] and be sure to convert to UNIX format (in NP++: Edit -> EOL Conversion -> UNIX format). If you have DOS linebreaks, ext2load will fail with an error like "file not found" as it appends an hidden character to the uImage file name.
}}boot.txt (from the [http://openpandora.org/firmware/README.txt official firmware site])
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0 0x80300000 /boot/uImage
bootm 0x80300000
</source>
Note: If you chose ext3 instead of ext2 for the partition containing the kernel, the second line still starts with ext2load. There is no ext3load.

Note: depending on firmware version kernels might be at several, sometimes multiple locations, so you have to choose one:
* /boot/uImage-3 - the default 3.2 kernel (recommended)
* /lib/boot/uImage - alternative location of 3.2 kernel on certain older firmwares
* /boot/uImage - mostly a symlink to the latest kernel on recent firmwares

Be aware though that this boot.txt assumes you have formatted your card with ext2 and loads the kernel off the SD card. It is technically possible to boot the kernel from NAND but still run the rest of the file system from your SD card with following boot.txt
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr} && boot
</source>
However this is not recommended because kernel modules on SD card will likely be not compatible with kernel on NAND.

Both boot.txt's assume you are booting from the left SD card slot, first partition. You can change "mmcblk0p1" to "mmcblk1p1" if you want to boot from the right slot (but boot.txt must still be on a card on the left slot).

====Setting up mutliple-partition SD cards for booting====

It is possible to have several partitions on the SD card and boot from one of them.
E.g. if you have three partitions on the card like this:
*Partition 1: FAT
*Partition 2: ext2 (where the rootfs should be placed)
*Partition 3: swap

How it's done:

1. Put uBoot's boot control files "boot.txt" and/or "autoboot.txt" into the root of the '''first partition''' of the card (FAT partition in this example)

2. Make "boot.txt" and "autoboot.txt" point U-Boot to the '''partition, which holds the root file system''' of your Linux system. This would be parition 2 in this example (ext2 FS).
This is done '''using the "root" parameter of setenv'''.

3. Make "boot.txt" and "autoboot.txt" point U-Boot to the correct '''location to boot your kernel from'''.
This kernel location can be any FAT or ext2/3/4 partition on the SD card.
The uBoot commands '''"fatload" and "ext2load" with their parameter "mmc x:y"''' are repsonsible for loading the kernel. Choose the command, which addresses the file system the kernel is located on and make sure to correctly adapt the values x and y.

This common example boots the kernel from the FAT partition (then this is a "boot partition"), and uses the ext2 file system as root FS:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
fatload mmc 0:1 0x80300000 uimage
bootm 0x80300000
</source>

If you put the kernel into the root file system's /boot directory, the second line would be different:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0:2 0x80300000 /boot/uImage
bootm 0x80300000
</source>

'''Note: '''

For both the "root=" kernel argument and the "mmc x:y" argument of the fatload/ext2load commands, slot numbering begins at 0 (0 is left SD slot, 1 is right SD slot) and partition numbering begins at 1!

'''Recommendation:'''

Put the kernel into another partition than the root FS is located.
Reason: In case the root FS partition is flagged "inconsistent" after a system crash or sudden SD card removal, uBoot won't be able to boot from that partition anymore. But the file system cleanup routines can only be run, once the kernel has been booted. Hence it's safer to put the kernel on a different partition.

==Boot the system==

As you power up the Pandora, hold the shoulder button R. A menu should appear, allowing you to boot from the SD card. (this step isn't necessary if you chose to create an autoboot.txt instead of boot.txt). Remember that this will be an un-configured image, taking a little while longer to boot, and giving the first-run dialogue.

==Access the NAND==
Once you're booted into the system from SD, you may want access to the NAND rootfs. The following will let you do that.
<source lang="bash">
sudo mkdir /mnt/nand
sudo ubiattach /dev/ubi_ctrl -m 4
sudo mount -t ubifs ubi0:rootfs /mnt/nand
</source>

==Other information==
An alternative approach to using an SD card to increase the space accessible to the system is [[Extend_Utils#OS_Extends | OS Extend]]. This allows the root filesystem to exist on more than one physical device.

==References==
*[http://www.rjmitchell.ca/~jeff/blog2009/2010/06/07/pandora-running-firmware-from-sd-card-instead-of-nand-flash/ Skeezix's blog]
*[http://www.gp32x.com/board/index.php?/topic/54290-up-to-date-firmware-tarball GP32x Forum Topic, "Up to date firmware tarball"]
*[http://openpandora.org/firmware/ Official firmware page]
*[http://repo.openpandora.org/?page=detail&app=sd-install-2011-03-10 The GUI-driven SD installer by David Boucher]

[[Category:Tutorials]]
[[Category:Booting]]
[[Category:Storage card]]
[[Category:Operating system]]

Boot setup

2013-10-14T02:12:05Z

Levi: /* Set up your boot.txt */

This guide assumes you have got the operating system of choice at the ready.

===Partition your SD card===

This is an optional step. It may be a good idea to set up multiple partitions/slices on your SD card - reasons include wanting to include a separate first partition for use on Windows, having a swap partition, or separating your kernel image from your root filesystem in case of filesystem corruption.

If you do want to slice your SD card into several partitions (see [[#Setting_up_mutliple-partition_SD_cards_for_booting|Setting up mutliple-partition SD cards]]), you can use the ''cfdisk'' command-line tool on the Pandora to create a partition table, or you can also download and use the [http://repo.openpandora.org/?page=detail&app=gparted-gparted graphical tool ''gparted''].

Note that - as of Zaxxon HF5 - the Pandora firmware doesn't have a command to format FAT partitions, so if you want to use the FAT/ext2/swap - scheme, you'll have to format the first partition on another system later on (under Windows, use the Disk Management tool).

====Using ''cfdisk''====

Assuming your card is in the left slot:

<source lang="bash">sudo cfdisk -z /dev/mmcblk0</source>

'''WARNING: mmcblk0 will [http://bugs.openpandora.org/index.php?do=details&task_id=237 not necessarily be the left slot]. It's the first card that the system recognizes, which is ''usually'' the left slot (but not if you inserted an SD into the left slot after you had one in the right slot, for example). Please make sure before you do anything dangerous e.g. use 'mount' to see what filesystems you recognise are mounted from where.'''

cfdisk -z starts off with a clean partition table - if you want to see what's set up currently, use ''cfdisk /dev/mmcblk0''.

Use only primary partitions (so you're limited to four slices).

====Using ''gparted''====

Download the gparted PND and install it. Note: this generally requires having a second SD card to install it to, though it should be possible to install it to the /pandora folder in your filesystem root, which will install it to NAND.

Find the program under 'System' in the menu and launch it. '''WARNING: It will start off pointing at /dev/mmcblk0 which is ''usually'' your left slot, but may not be.''' You can switch between the two card slots (if you have a card in each) and deduce which is which from the graphical display and the partition labels, but '''please be sure before applying any changes'''. Selecting 'information' from the right-click menu will also show you where each partition is mounted on the root filesystem, if it is currently mounted.

If the system has automounted the existing partition it'll show as locked and you'll need to unmount it using the right-click menu before you'll be able to change it. In this case, you'll probably want to delete it and create new partitions. Note that whatever partition your end up installing your boot/autoboot.txt to must be either ext2 or FAT, but you have a freer choice of filesystems to use on other partitions.

Once you've decided on your partitions and marked up the changes you'll need to apply them. Use the '''Apply All Operations''' menu item from the '''Edit''' menu. Then sit back and wait as it repartitions and reformats your card.

===Format SD card===

If you didn't use '''gparted''' to partition and format your card, you need to format your SD card to have at least an ext2 partition; ext3 also works[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/] and is more reliable[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/page-5#entry901072]. You can have additional paritions, such as swap partition, as well if you like.

====Using the command line====
Take care with using these command line tools, to be certain you are accessing the correct device. They will not ask you and will DESTROY any data on the device. This command will replace an existing partition with an empty EXT2 formatted filesystem (this includes the single FAT partition most SD cards come shipped with). Assuming ''/dev/mmcblk0p1'' for your SD device (left slot, first partition), ''LABELNAME'' for the partition:
<source lang="bash">
mkfs.ext2 -L LABELNAME /dev/mmcblk0p1
</source>
or
<source lang="bash">
mkfs.ext3 -L LABELNAME /dev/mmcblk0p1
</source>
If you run into problems with formatting the SD card, try unmounting it first:
<source lang="bash">
sudo umount /media/[LABELNAME of SD card]
</source>

===Copy and boot===

====Copy the files to your SD card====
Navigate (cd) to the directory with the .tar.bz2 file you just downloaded (or made) and do:

<source lang="bash">
sudo tar -xvjf <tarfile>.tar.bz2 -C <SD card>
</source>

If you're doing this on your Pandora, <SD card> is something like /media/mmcblk0p1 (first SD card slot on Pandora). On Ubuntu it would be something like /media/disk if it has no label. You can also try using GUI tools for this, but I didn't have very good luck with them.

====OR copy your firmware from the NAND to the SD card====

The following will ask for your password. All the operations need root permissions so I thought it would be wasteful to sprinkle sudo to everything.
We will bind mount the root fs to an alternative location ("/mp"), under which other filesystems mounted under root (like the kernel virtual filesystems /proc and /sys, and your SD card.) wont be visible. This allows us to take a live copy of the NAND contents to the SD filesystem.

<source lang="bash">
sudo su
mkdir /mp
mount --bind / /mp
cp -va /mp/* /media/<SD card>
umount /mp
rmdir /mp
exit
</source>

===Set up your boot.txt===

Create a new file called boot.txt (or autoboot.txt if you want to boot automatically) and copy and paste the text below. Copy that file to the root of the root of the SD card.

{{warning
|If you edit the file on Windows, use an advanced text editor like [http://notepad-plus-plus.org/ Notepad++] and be sure to convert to UNIX format (in NP++: Edit -> EOL Conversion -> UNIX format). If you have DOS linebreaks, ext2load will fail with an error like "file not found" as it appends an hidden character to the uImage file name.
}}

boot.txt (from the [http://openpandora.org/firmware/README.txt official firmware site])
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0 0x80300000 /boot/uImage
bootm 0x80300000
</source>
Note: If you chose ext3 instead of ext2 for the partition containing the kernel, the second line still starts with ext2load. There is no ext3load.

Note: depending on firmware version kernels might be at several, sometimes multiple locations, so you have to choose one:
* /boot/uImage-3 - the default 3.2 kernel (recommended)
* /lib/boot/uImage - alternative location of 3.2 kernel on certain older firmwares
* /boot/uImage - mostly a symlink to the latest kernel on recent firmwares

Be aware though that this boot.txt assumes you have formatted your card with ext2 and loads the kernel off the SD card. It is technically possible to boot the kernel from NAND but still run the rest of the file system from your SD card with following boot.txt
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr} && boot
</source>
However this is not recommended because kernel modules on SD card will likely be not compatible with kernel on NAND.

Both boot.txt's assume you are booting from the left SD card slot, first partition. You can change "mmcblk0p1" to "mmcblk1p1" if you want to boot from the right slot (but boot.txt must still be on a card on the left slot).

====Setting up mutliple-partition SD cards for booting====

It is possible to have several partitions on the SD card and boot from one of them.
E.g. if you have three partitions on the card like this:
*Partition 1: FAT
*Partition 2: ext2 (where the rootfs should be placed)
*Partition 3: swap

How it's done:

1. Put uBoot's boot control files "boot.txt" and/or "autoboot.txt" into the root of the '''first partition''' of the card (FAT partition in this example)

2. Make "boot.txt" and "autoboot.txt" point U-Boot to the '''partition, which holds the root file system''' of your Linux system. This would be parition 2 in this example (ext2 FS).
This is done '''using the "root" parameter of setenv'''.

3. Make "boot.txt" and "autoboot.txt" point U-Boot to the correct '''location to boot your kernel from'''.
This kernel location can be any FAT or ext2/3/4 partition on the SD card.
The uBoot commands '''"fatload" and "ext2load" with their parameter "mmc x:y"''' are repsonsible for loading the kernel. Choose the command, which addresses the file system the kernel is located on and make sure to correctly adapt the values x and y.

This common example boots the kernel from the FAT partition (then this is a "boot partition"), and uses the ext2 file system as root FS:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
fatload mmc 0:1 0x80300000 uimage
bootm 0x80300000
</source>

If you put the kernel into the root file system's /boot directory, the second line would be different:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0:2 0x80300000 /boot/uImage
bootm 0x80300000
</source>

'''Note: '''

For "root=" kernel argument, slot numbering begins at 0 (0 is left SD slot, 1 is right SD slot) and partition numbering begins at 1!

For "mmc x:y" agrument of the fatload/ext2load commands, x is the card number (0 is left slot, 1 is right slot), y is the partition number, beginning at 1(!).

'''Recommendation:'''

Put the kernel into another partition than the root FS is located.
Reason: In case the root FS partition is flagged "inconsistent" after a system crash or sudden SD card removal, uBoot won't be able to boot from that partition anymore. But the file system cleanup routines can only be run, once the kernel has been booted. Hence it's safer to put the kernel on a different partition.

==Boot the system==

As you power up the Pandora, hold the shoulder button R. A menu should appear, allowing you to boot from the SD card. (this step isn't necessary if you chose to create an autoboot.txt instead of boot.txt). Remember that this will be an un-configured image, taking a little while longer to boot, and giving the first-run dialogue.

==Access the NAND==
Once you're booted into the system from SD, you may want access to the NAND rootfs. The following will let you do that.
<source lang="bash">
sudo mkdir /mnt/nand
sudo ubiattach /dev/ubi_ctrl -m 4
sudo mount -t ubifs ubi0:rootfs /mnt/nand
</source>

==Other information==
An alternative approach to using an SD card to increase the space accessible to the system is [[Extend_Utils#OS_Extends | OS Extend]]. This allows the root filesystem to exist on more than one physical device.

==References==
*[http://www.rjmitchell.ca/~jeff/blog2009/2010/06/07/pandora-running-firmware-from-sd-card-instead-of-nand-flash/ Skeezix's blog]
*[http://www.gp32x.com/board/index.php?/topic/54290-up-to-date-firmware-tarball GP32x Forum Topic, "Up to date firmware tarball"]
*[http://openpandora.org/firmware/ Official firmware page]
*[http://repo.openpandora.org/?page=detail&app=sd-install-2011-03-10 The GUI-driven SD installer by David Boucher]

[[Category:Tutorials]]
[[Category:Booting]]
[[Category:Storage card]]
[[Category:Operating system]]

Boot setup

2013-10-14T02:02:08Z

Levi: /* Format SD card to ext2 */

This guide assumes you have got the operating system of choice at the ready.

===Partition your SD card===

This is an optional step. It may be a good idea to set up multiple partitions/slices on your SD card - reasons include wanting to include a separate first partition for use on Windows, having a swap partition, or separating your kernel image from your root filesystem in case of filesystem corruption.

If you do want to slice your SD card into several partitions (see [[#Setting_up_mutliple-partition_SD_cards_for_booting|Setting up mutliple-partition SD cards]]), you can use the ''cfdisk'' command-line tool on the Pandora to create a partition table, or you can also download and use the [http://repo.openpandora.org/?page=detail&app=gparted-gparted graphical tool ''gparted''].

Note that - as of Zaxxon HF5 - the Pandora firmware doesn't have a command to format FAT partitions, so if you want to use the FAT/ext2/swap - scheme, you'll have to format the first partition on another system later on (under Windows, use the Disk Management tool).

====Using ''cfdisk''====

Assuming your card is in the left slot:

<source lang="bash">sudo cfdisk -z /dev/mmcblk0</source>

'''WARNING: mmcblk0 will [http://bugs.openpandora.org/index.php?do=details&task_id=237 not necessarily be the left slot]. It's the first card that the system recognizes, which is ''usually'' the left slot (but not if you inserted an SD into the left slot after you had one in the right slot, for example). Please make sure before you do anything dangerous e.g. use 'mount' to see what filesystems you recognise are mounted from where.'''

cfdisk -z starts off with a clean partition table - if you want to see what's set up currently, use ''cfdisk /dev/mmcblk0''.

Use only primary partitions (so you're limited to four slices).

====Using ''gparted''====

Download the gparted PND and install it. Note: this generally requires having a second SD card to install it to, though it should be possible to install it to the /pandora folder in your filesystem root, which will install it to NAND.

Find the program under 'System' in the menu and launch it. '''WARNING: It will start off pointing at /dev/mmcblk0 which is ''usually'' your left slot, but may not be.''' You can switch between the two card slots (if you have a card in each) and deduce which is which from the graphical display and the partition labels, but '''please be sure before applying any changes'''. Selecting 'information' from the right-click menu will also show you where each partition is mounted on the root filesystem, if it is currently mounted.

If the system has automounted the existing partition it'll show as locked and you'll need to unmount it using the right-click menu before you'll be able to change it. In this case, you'll probably want to delete it and create new partitions. Note that whatever partition your end up installing your boot/autoboot.txt to must be either ext2 or FAT, but you have a freer choice of filesystems to use on other partitions.

Once you've decided on your partitions and marked up the changes you'll need to apply them. Use the '''Apply All Operations''' menu item from the '''Edit''' menu. Then sit back and wait as it repartitions and reformats your card.

===Format SD card===

If you didn't use '''gparted''' to partition and format your card, you need to format your SD card to have at least an ext2 partition; ext3 also works[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/] and is more reliable[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/page-5#entry901072]. You can have additional paritions, such as swap partition, as well if you like.

====Using the command line====
Take care with using these command line tools, to be certain you are accessing the correct device. They will not ask you and will DESTROY any data on the device. This command will replace an existing partition with an empty EXT2 formatted filesystem (this includes the single FAT partition most SD cards come shipped with). Assuming ''/dev/mmcblk0p1'' for your SD device (left slot, first partition), ''LABELNAME'' for the partition:
<source lang="bash">
mkfs.ext2 -L LABELNAME /dev/mmcblk0p1
</source>
or
<source lang="bash">
mkfs.ext3 -L LABELNAME /dev/mmcblk0p1
</source>
If you run into problems with formatting the SD card, try unmounting it first:
<source lang="bash">
sudo umount /media/[LABELNAME of SD card]
</source>

===Copy and boot===

====Copy the files to your SD card====
Navigate (cd) to the directory with the .tar.bz2 file you just downloaded (or made) and do:

<source lang="bash">
sudo tar -xvjf <tarfile>.tar.bz2 -C <SD card>
</source>

If you're doing this on your Pandora, <SD card> is something like /media/mmcblk0p1 (first SD card slot on Pandora). On Ubuntu it would be something like /media/disk if it has no label. You can also try using GUI tools for this, but I didn't have very good luck with them.

====OR copy your firmware from the NAND to the SD card====

The following will ask for your password. All the operations need root permissions so I thought it would be wasteful to sprinkle sudo to everything.
We will bind mount the root fs to an alternative location ("/mp"), under which other filesystems mounted under root (like the kernel virtual filesystems /proc and /sys, and your SD card.) wont be visible. This allows us to take a live copy of the NAND contents to the SD filesystem.

<source lang="bash">
sudo su
mkdir /mp
mount --bind / /mp
cp -va /mp/* /media/<SD card>
umount /mp
rmdir /mp
exit
</source>

====Set up your boot.txt====

Create a new file called boot.txt (or autoboot.txt if you want to boot automatically) and copy and paste the text below. Copy that file to the root of the root of the SD card.

{{warning
|If you edit the file on Windows, use an advanced text editor like [http://notepad-plus-plus.org/ Notepad++] and be sure to convert to UNIX format (in NP++: Edit -> EOL Conversion -> UNIX format). If you have DOS linebreaks, ext2load will fail with an error like "file not found" as it appends an hidden character to the uImage file name.
}}

boot.txt (from the [http://openpandora.org/firmware/README.txt official firmware site])
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0 0x80300000 /boot/uImage-3
bootm 0x80300000
</source>
Note: depending on firmware version kernels might be at several, sometimes multiple locations, so you have to choose one:
* /boot/uImage-3 - the default 3.2 kernel (recommended)
* /lib/boot/uImage - alternative location of 3.2 kernel on certain older firmwares
* /boot/uImage - the old 2.6 kernel

Be aware though that this boot.txt assumes you have formatted your card with ext2 and loads the kernel off the SD card. It is possible to boot the kernel from NAND with following boot.txt
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr} && boot
</source>
However this is not recommended because kernel modules on SD card will likely be not compatible with kernel on NAND.

Both boot.txt's assume you are booting from the left SD card slot, first partition. You can change "mmcblk0p1" to "mmcblk1p1" if you want to boot from the right slot (but boot.txt must still be on a card on the left slot).
Note: If you chose ext3 instead of ext2, the second line still starts with ext2load. There is no ext3load.

====Setting up mutliple-partition SD cards for booting====

It is possible to have several partitions on the SD card and boot from one of them.
E.g. if you have three partitions on the card like this:
*Partition 1: FAT
*Partition 2: ext2 (where the rootfs should be placed)
*Partition 3: swap

How it's done:

1. Put uBoot's boot control files "boot.txt" and/or "autoboot.txt" into the root of the '''first partition''' of the card (FAT partition in this example)

2. Make "boot.txt" and "autoboot.txt" point U-Boot to the '''partition, which holds the root file system''' of your Linux system. This would be parition 2 in this example (ext2 FS).
This is done '''using the "root" parameter of setenv'''.

3. Make "boot.txt" and "autoboot.txt" point U-Boot to the correct '''location to boot your kernel from'''.
This kernel location can be any FAT or ext2/3/4 partition on the SD card.
The uBoot commands '''"fatload" and "ext2load" with their parameter "mmc x:y"''' are repsonsible for loading the kernel. Choose the command, which addresses the file system the kernel is located on and make sure to correctly adapt the values x and y.

This common example boots the kernel from the FAT partition (then this is a "boot partition"), and uses the ext2 file system as root FS:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
fatload mmc 0:1 0x80300000 uimage
bootm 0x80300000
</source>

If you put the kernel into the root file system's /boot directory, the second line would be different:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0:2 0x80300000 /boot/uImage
bootm 0x80300000
</source>

'''Note: '''

For "root=" kernel argument, slot numbering begins at 0 (0 is left SD slot, 1 is right SD slot) and partition numbering begins at 1!

For "mmc x:y" agrument of the fatload/ext2load commands, x is the card number (0 is left slot, 1 is right slot), y is the partition number, beginning at 1(!).

'''Recommendation:'''

Put the kernel into another partition than the root FS is located.
Reason: In case the root FS partition is flagged "inconsistent" after a system crash or sudden SD card removal, uBoot won't be able to boot from that partition anymore. But the file system cleanup routines can only be run, once the kernel has been booted. Hence it's safer to put the kernel on a different partition.

==Boot the system==

As you power up the Pandora, hold the shoulder button R. A menu should appear, allowing you to boot from the SD card. (this step isn't necessary if you chose to create an autoboot.txt instead of boot.txt). Remember that this will be an un-configured image, taking a little while longer to boot, and giving the first-run dialogue.

==Access the NAND==
Once you're booted into the system from SD, you may want access to the NAND rootfs. The following will let you do that.
<source lang="bash">
sudo mkdir /mnt/nand
sudo ubiattach /dev/ubi_ctrl -m 4
sudo mount -t ubifs ubi0:rootfs /mnt/nand
</source>

==Other information==
An alternative approach to using an SD card to increase the space accessible to the system is [[Extend_Utils#OS_Extends | OS Extend]]. This allows the root filesystem to exist on more than one physical device.

==References==
*[http://www.rjmitchell.ca/~jeff/blog2009/2010/06/07/pandora-running-firmware-from-sd-card-instead-of-nand-flash/ Skeezix's blog]
*[http://www.gp32x.com/board/index.php?/topic/54290-up-to-date-firmware-tarball GP32x Forum Topic, "Up to date firmware tarball"]
*[http://openpandora.org/firmware/ Official firmware page]
*[http://repo.openpandora.org/?page=detail&app=sd-install-2011-03-10 The GUI-driven SD installer by David Boucher]

[[Category:Tutorials]]
[[Category:Booting]]
[[Category:Storage card]]
[[Category:Operating system]]

Boot setup

2013-10-14T01:48:44Z

Levi: /* Partition your SD card */ Note rationale for parititioning, document gparted and other tweaks

This guide assumes you have got the operating system of choice at the ready.

===Partition your SD card===

This is an optional step. It may be a good idea to set up multiple partitions/slices on your SD card - reasons include wanting to include a separate first partition for use on Windows, having a swap partition, or separating your kernel image from your root filesystem in case of filesystem corruption.

If you do want to slice your SD card into several partitions (see [[#Setting_up_mutliple-partition_SD_cards_for_booting|Setting up mutliple-partition SD cards]]), you can use the ''cfdisk'' command-line tool on the Pandora to create a partition table, or you can also download and use the [http://repo.openpandora.org/?page=detail&app=gparted-gparted graphical tool ''gparted''].

Note that - as of Zaxxon HF5 - the Pandora firmware doesn't have a command to format FAT partitions, so if you want to use the FAT/ext2/swap - scheme, you'll have to format the first partition on another system later on (under Windows, use the Disk Management tool).

====Using ''cfdisk''====

Assuming your card is in the left slot:

<source lang="bash">sudo cfdisk -z /dev/mmcblk0</source>

'''WARNING: mmcblk0 will [http://bugs.openpandora.org/index.php?do=details&task_id=237 not necessarily be the left slot]. It's the first card that the system recognizes, which is ''usually'' the left slot (but not if you inserted an SD into the left slot after you had one in the right slot, for example). Please make sure before you do anything dangerous e.g. use 'mount' to see what filesystems you recognise are mounted from where.'''

cfdisk -z starts off with a clean partition table - if you want to see what's set up currently, use ''cfdisk /dev/mmcblk0''.

Use only primary partitions (so you're limited to four slices).

====Using ''gparted''====

Download the gparted PND and install it. Note: this generally requires having a second SD card to install it to, though it should be possible to install it to the /pandora folder in your filesystem root, which will install it to NAND.

Find the program under 'System' in the menu and launch it. '''WARNING: It will start off pointing at /dev/mmcblk0 which is ''usually'' your left slot, but may not be.''' You can switch between the two card slots (if you have a card in each) and deduce which is which from the graphical display and the partition labels, but '''please be sure before applying any changes'''. Selecting 'information' from the right-click menu will also show you where each partition is mounted on the root filesystem, if it is currently mounted.

If the system has automounted the existing partition it'll show as locked and you'll need to unmount it using the right-click menu before you'll be able to change it. In this case, you'll probably want to delete it and create new partitions. Note that whatever partition your end up installing your boot/autoboot.txt to must be either ext2 or FAT, but you have a freer choice of filesystems to use on other partitions.

Once you've decided on your partitions and marked up the changes you'll need to apply them. Use the '''Apply All Operations''' menu item from the '''Edit''' menu. Then sit back and wait as it repartitions and reformats your card.

===Format SD card to ext2===

You need to format your SD card to have a single ext2 partition; ext3 also works[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/] and is more reliable[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/page__view__findpost__p__901072]. You can have a second, swap partition, as well if you like. There are command line tools you can use as well as GUI tools.

====Using the command line====
Take care with using these command line tools, to be certain you are accessing the correct device. They will not ask you and will DESTROY any data on the device. This command will replace an existing partition with an empty EXT2 formatted filesystem (this includes the single FAT partition most SD cards come shipped with). Assuming ''/dev/mmcblk0p1'' for your SD device (left slot, first partition), ''LABELNAME'' for the partition:
<source lang="bash">
mkfs.ext2 -L LABELNAME /dev/mmcblk0p1
</source>
If you run into problems with formatting the SD card, try unmounting it first:
<source lang="bash">
sudo umount /media/[LABELNAME of SD card]
</source>

====Using a GUI tool====
The GUI tools are simple enough that you shouldn't need someone to tell you how to use them. For now this is left as an exercise left for the reader (until someone wants to write up how to do it).

===Copy and boot===

====Copy the files to your SD card====
Navigate (cd) to the directory with the .tar.bz2 file you just downloaded (or made) and do:

<source lang="bash">
sudo tar -xvjf <tarfile>.tar.bz2 -C <SD card>
</source>

If you're doing this on your Pandora, <SD card> is something like /media/mmcblk0p1 (first SD card slot on Pandora). On Ubuntu it would be something like /media/disk if it has no label. You can also try using GUI tools for this, but I didn't have very good luck with them.

====OR copy your firmware from the NAND to the SD card====

The following will ask for your password. All the operations need root permissions so I thought it would be wasteful to sprinkle sudo to everything.
We will bind mount the root fs to an alternative location ("/mp"), under which other filesystems mounted under root (like the kernel virtual filesystems /proc and /sys, and your SD card.) wont be visible. This allows us to take a live copy of the NAND contents to the SD filesystem.

<source lang="bash">
sudo su
mkdir /mp
mount --bind / /mp
cp -va /mp/* /media/<SD card>
umount /mp
rmdir /mp
exit
</source>

====Set up your boot.txt====

Create a new file called boot.txt (or autoboot.txt if you want to boot automatically) and copy and paste the text below. Copy that file to the root of the root of the SD card.

{{warning
|If you edit the file on Windows, use an advanced text editor like [http://notepad-plus-plus.org/ Notepad++] and be sure to convert to UNIX format (in NP++: Edit -> EOL Conversion -> UNIX format). If you have DOS linebreaks, ext2load will fail with an error like "file not found" as it appends an hidden character to the uImage file name.
}}

boot.txt (from the [http://openpandora.org/firmware/README.txt official firmware site])
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0 0x80300000 /boot/uImage-3
bootm 0x80300000
</source>
Note: depending on firmware version kernels might be at several, sometimes multiple locations, so you have to choose one:
* /boot/uImage-3 - the default 3.2 kernel (recommended)
* /lib/boot/uImage - alternative location of 3.2 kernel on certain older firmwares
* /boot/uImage - the old 2.6 kernel

Be aware though that this boot.txt assumes you have formatted your card with ext2 and loads the kernel off the SD card. It is possible to boot the kernel from NAND with following boot.txt
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr} && boot
</source>
However this is not recommended because kernel modules on SD card will likely be not compatible with kernel on NAND.

Both boot.txt's assume you are booting from the left SD card slot, first partition. You can change "mmcblk0p1" to "mmcblk1p1" if you want to boot from the right slot (but boot.txt must still be on a card on the left slot).
Note: If you chose ext3 instead of ext2, the second line still starts with ext2load. There is no ext3load.

====Setting up mutliple-partition SD cards for booting====

It is possible to have several partitions on the SD card and boot from one of them.
E.g. if you have three partitions on the card like this:
*Partition 1: FAT
*Partition 2: ext2 (where the rootfs should be placed)
*Partition 3: swap

How it's done:

1. Put uBoot's boot control files "boot.txt" and/or "autoboot.txt" into the root of the '''first partition''' of the card (FAT partition in this example)

2. Make "boot.txt" and "autoboot.txt" point U-Boot to the '''partition, which holds the root file system''' of your Linux system. This would be parition 2 in this example (ext2 FS).
This is done '''using the "root" parameter of setenv'''.

3. Make "boot.txt" and "autoboot.txt" point U-Boot to the correct '''location to boot your kernel from'''.
This kernel location can be any FAT or ext2/3/4 partition on the SD card.
The uBoot commands '''"fatload" and "ext2load" with their parameter "mmc x:y"''' are repsonsible for loading the kernel. Choose the command, which addresses the file system the kernel is located on and make sure to correctly adapt the values x and y.

This common example boots the kernel from the FAT partition (then this is a "boot partition"), and uses the ext2 file system as root FS:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
fatload mmc 0:1 0x80300000 uimage
bootm 0x80300000
</source>

If you put the kernel into the root file system's /boot directory, the second line would be different:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0:2 0x80300000 /boot/uImage
bootm 0x80300000
</source>

'''Note: '''

For "root=" kernel argument, slot numbering begins at 0 (0 is left SD slot, 1 is right SD slot) and partition numbering begins at 1!

For "mmc x:y" agrument of the fatload/ext2load commands, x is the card number (0 is left slot, 1 is right slot), y is the partition number, beginning at 1(!).

'''Recommendation:'''

Put the kernel into another partition than the root FS is located.
Reason: In case the root FS partition is flagged "inconsistent" after a system crash or sudden SD card removal, uBoot won't be able to boot from that partition anymore. But the file system cleanup routines can only be run, once the kernel has been booted. Hence it's safer to put the kernel on a different partition.

==Boot the system==

As you power up the Pandora, hold the shoulder button R. A menu should appear, allowing you to boot from the SD card. (this step isn't necessary if you chose to create an autoboot.txt instead of boot.txt). Remember that this will be an un-configured image, taking a little while longer to boot, and giving the first-run dialogue.

==Access the NAND==
Once you're booted into the system from SD, you may want access to the NAND rootfs. The following will let you do that.
<source lang="bash">
sudo mkdir /mnt/nand
sudo ubiattach /dev/ubi_ctrl -m 4
sudo mount -t ubifs ubi0:rootfs /mnt/nand
</source>

==Other information==
An alternative approach to using an SD card to increase the space accessible to the system is [[Extend_Utils#OS_Extends | OS Extend]]. This allows the root filesystem to exist on more than one physical device.

==References==
*[http://www.rjmitchell.ca/~jeff/blog2009/2010/06/07/pandora-running-firmware-from-sd-card-instead-of-nand-flash/ Skeezix's blog]
*[http://www.gp32x.com/board/index.php?/topic/54290-up-to-date-firmware-tarball GP32x Forum Topic, "Up to date firmware tarball"]
*[http://openpandora.org/firmware/ Official firmware page]
*[http://repo.openpandora.org/?page=detail&app=sd-install-2011-03-10 The GUI-driven SD installer by David Boucher]

[[Category:Tutorials]]
[[Category:Booting]]
[[Category:Storage card]]
[[Category:Operating system]]

Template:Help

2013-10-04T23:12:29Z

Levi: Get involved -> Boards

{|width="100%"
|- valign="top" cellpadding="0px" cellspacing="0px"
|style="width:50%; padding: .5em; border: 1px solid #c9c9ff; color: #000; background-color: #f3f3ff;"|
Have some expertise, or just some spare time? [http://boards.openpandora.org/index.php/index Get involved!]
|}

Pandora

2013-10-04T23:08:52Z

Levi: /* Overview */

{{disclaimer}}
{{help}}

[[Image:PandoraFrontNew.jpg|right|thumb|320px|The Pandora.]]
__TOC__

= Overview =

The Pandora is a unique combination of gaming console and pocket computer.

It is the [[Wikipedia:spiritual successor|spiritual successor]] to other handheld consoles such as the [[Wikipedia:GP32|GP32]] and [[Wikipedia:GP2X|GP2X]]. There is currently no other device that has dedicated gaming controls, two [[nubs|analog nubs]] and a [[keyboard|QWERTY keyboard]].

It was developed as a gaming device not just to run [[games]] made just for it but also to [[Emulator List|emulate older systems]]. From home consoles like the [[Wikipedia:Atari 2600|Atari 2600]], [[Wikipedia:Nintendo Entertainment System|NES]], [[Wikipedia:Super Nintendo Entertainment System|SNES]], [[Wikipedia:Sega Master System|Sega Master System]], [[Wikipedia:Sega Genesis|Sega Genesis]] and [[Wikipedia:Neo Geo (system)|Neo Geo]] to handheld consoles like the [[Wikipedia:Sega Game Gear|Game Gear]], [[Wikipedia:Game Boy|Game Boy]]/[[Wikipedia:Game Boy Color|Color]]/[[Wikipedia:Game Boy Advance|Advance]] to traditional arcade cabinet games. It can also emulate entire computer systems, from the [[Wikipedia:Commodore 64|Commodore 64]] and [[Wikipedia:Amiga|Amiga]] to old Apple Macintosh computers or a PC with DOS.

The Pandora can do all of this because it is a tiny computer running a custom distribution of Linux based on [http://www.angstrom-distribution.org/ The Ångström Distribution]. Because it runs Linux, the Pandora isn't just a console but a complete desktop computer with access to tens of thousands of Linux programs.

From classic gaming, listening to music, watching movies, viewing pictures, program development or surfing the web to just reading or writing texts, the Pandora has a lot to offer.

{{hr}}

[http://www.open-pandora.org/ Visit the Pandora website] for ordering information.

= Specifications =

[[Hardware documentation]] has detailed hardware specifications.

* [[Size Comparisons|140 x 83 x 27 mm]]

* 320g (0.739 lbs) {{FIXME|Does this include the battery?}}

== Core Hardware ==

* [[Hardware_documentation#OMAP3530|Texas Instruments OMAP3530 SoC]]

* [[Hardware_documentation#PowerVR|PowerVR SGX GPU]]

* 512MB DDR SDRAM.

* 512MB internal storage ([[NAND]])

== Display ==

* Touchscreen TFT-LCD
** 4.3-inch (93.6 x 56.2 mm)
** 800x480 widescreen (5:3)
** Brightness: 300 cd/m2
** Contrast ratio: 450:1
*** Viewable in direct sunlight, but it ''will'' wash out.
** Response time: tr+tf=30ms
*** No ghosting.

* {{FIXME|This is a mess.}} TV-out included in hardware, A/V-OUT Port (similar in appearance to a large USB OTG port) has Composite and S-Video outputs and 3.5mm headphone output and microphone input.
** Separate TV-out signals, picture-in-picture capabilities. [http://www.gp32x.com/board/index.php?showtopic=38044]

== Audio ==

* Stereo speakers

* Volume control wheel

* Microphone

* A [[Wikipedia:Digital-to-analog converter|DAC]] and an [[Wikipedia:Analog-to-digital converter|ADC]]

== Input ==

* QWERTY [[keyboard]]

* Gaming controls:
** 8-way D-pad
** Four gaming buttons
** Two shoulder buttons
** Two analog [[nubs]]

* Touchscreen

* Microphone

== Connectivity ==

* [[Wi-Fi|802.11b/g Wi-Fi]]

* [[Bluetooth|Bluetooth 2.0 + EDR]] (3Mbps)

* [[USB_reference|USB]]
*# Standard-A USB host port
*#* Fully powered (500 mA)
*# [[Wikipedia:USB On-The-Go|USB On-The-Go]] mini-AB port.
** You can use anything that has the appropriate drivers. [http://www.gp32x.com/board/index.php?s=&showtopic=38155&view=findpost&p=568882]
** Some devices need to first go through a powered USB hub.

* Two [[Wikipedia:Secure_Digital#SDIO|SDIO]]-capable [[Wikipedia:SDHC#SDHC|SDHC]]/[[Wikipedia:SDHC#SDXC|SDXC]] slots.

* [[Wikipedia:RS-232|RS-232]] included, but a level converter is needed for the [[Wikipedia:Universal asynchronous receiver/transmitter|UART]]. [http://www.gp32x.com/board/index.php?s=&showtopic=38155&view=findpost&p=568882]

== Power ==

* [[Wikipedia:Lithium-ion polymer battery|Lithium-ion polymer]] [[battery]], 4200mAh design capacity.
** 10-20 hours battery life under reasonable load
** 8-12 hours under max CPU load
** 6-8 hours under max CPU load with overclocking
** 5-6 days standby time
** 21 hours playing music with the display off

* Can charge through an AC adapter or USB. [http://www.gp32x.com/board/index.php?s=&showtopic=40659&view=findpost&p=587802]
** Charging with the AC adapter takes about 4 hours from near-empty. In 2 hours you get to about 80%.

* Advanced power management capabilities: only need to set a max clock speed; when the CPU is not doing anything it automatically HALTs and does nothing to save power. [http://www.gp32x.com/board/index.php?s=&showtopic=38155&view=findpost&p=574380]

* Suspend to RAM or suspend to disk functionality is being developed. This will give longer battery life and faster start up.
** See [[Power modes]].

= More Information =

* [[Hardware documentation]]
* [[Pandora history]]

[[Category:Hardware]]
[[Category:List]]

Pandora

2013-10-04T23:02:06Z

Levi: /* More Information */ Less Information ;)

{{disclaimer}}
{{help}}

[[Image:PandoraFrontNew.jpg|right|thumb|320px|The Pandora.]]
__TOC__

= Overview =

The Pandora is a unique combination of gaming console and pocket computer.

It is the [[Wikipedia:spiritual successor|spiritual successor]] to other handheld consoles such as the [[Wikipedia:GP32|GP32]] and [[Wikipedia:GP2X|GP2X]]. There is currently no other device that has dedicated gaming controls, two [[nubs|analog nubs]] and a [[keyboard|QWERTY keyboard]].

It was developed as a gaming device not just to run [[games]] made just for it but also to [[Emulator list|emulate older systems]]. From home consoles like the [[Wikipedia:Atari 2600|Atari 2600]], [[Wikipedia:Nintendo Entertainment System|NES]], [[Wikipedia:Super Nintendo Entertainment System|SNES]], [[Wikipedia:Sega Master System|Sega Master System]], [[Wikipedia:Sega Genesis|Sega Genesis]] and [[Wikipedia:Neo Geo (system)|Neo Geo]] to handheld consoles like the [[Wikipedia:Sega Game Gear|Game Gear]], [[Wikipedia:Game Boy|Game Boy]]/[[Wikipedia:Game Boy Color|Color]]/[[Wikipedia:Game Boy Advance|Advance]] to traditional arcade cabinet games. It can also emulate entire computer systems, from the [[Wikipedia:Commodore 64|Commodore 64]] and [[Wikipedia:Amiga|Amiga]] to old Apple Macintosh computers or a PC with DOS.

The Pandora can do all of this because it is a tiny computer running a custom distribution of Linux based on [http://www.angstrom-distribution.org/ The Ångström Distribution]. Because it runs Linux, the Pandora isn't just a console but a complete desktop computer with access to tens of thousands of Linux programs.

From classic gaming, listening to music, watching movies, viewing pictures, program development or surfing the web to just reading or writing texts, the Pandora has a lot to offer.

{{hr}}

[[FAQ|Our FAQ]] has more detailed information.

[http://www.open-pandora.org/index.php?option=com_content&view=article&id=97&Itemid=34&lang=en Visit the Pandora website] for ordering information.

= Specifications =

[[Hardware documentation]] has detailed hardware specifications.

* [[Size Comparisons|140 x 83 x 27 mm]]

* 320g (0.739 lbs) {{FIXME|Does this include the battery?}}

== Core Hardware ==

* [[Hardware_documentation#OMAP3530|Texas Instruments OMAP3530 SoC]]

* [[Hardware_documentation#PowerVR|PowerVR SGX GPU]]

* 512MB DDR SDRAM.

* 512MB internal storage ([[NAND]])

== Display ==

* Touchscreen TFT-LCD
** 4.3-inch (93.6 x 56.2 mm)
** 800x480 widescreen (5:3)
** Brightness: 300 cd/m2
** Contrast ratio: 450:1
*** Viewable in direct sunlight, but it ''will'' wash out.
** Response time: tr+tf=30ms
*** No ghosting.

* {{FIXME|This is a mess.}} TV-out included in hardware, A/V-OUT Port (similar in appearance to a large USB OTG port) has Composite and S-Video outputs and 3.5mm headphone output and microphone input.
** Separate TV-out signals, picture-in-picture capabilities. [http://www.gp32x.com/board/index.php?showtopic=38044]

== Audio ==

* Stereo speakers

* Volume control wheel

* Microphone

* A [[Wikipedia:Digital-to-analog converter|DAC]] and an [[Wikipedia:Analog-to-digital converter|ADC]]

== Input ==

* QWERTY [[keyboard]]

* Gaming controls:
** 8-way D-pad
** Four gaming buttons
** Two shoulder buttons
** Two analog [[nubs]]

* Touchscreen

* Microphone

== Connectivity ==

* [[Wi-Fi|802.11b/g Wi-Fi]]

* [[Bluetooth|Bluetooth 2.0 + EDR]] (3Mbps)

* [[USB_reference|USB]]
*# Standard-A USB host port
*#* Fully powered (500 mA)
*# [[Wikipedia:USB On-The-Go|USB On-The-Go]] mini-AB port.
** You can use anything that has the appropriate drivers. [http://www.gp32x.com/board/index.php?s=&showtopic=38155&view=findpost&p=568882]
** Some devices need to first go through a powered USB hub.

* Two [[Wikipedia:Secure_Digital#SDIO|SDIO]]-capable [[Wikipedia:SDHC#SDHC|SDHC]]/[[Wikipedia:SDHC#SDXC|SDXC]] slots.

* [[Wikipedia:RS-232|RS-232]] included, but a level converter is needed for the [[Wikipedia:Universal asynchronous receiver/transmitter|UART]]. [http://www.gp32x.com/board/index.php?s=&showtopic=38155&view=findpost&p=568882]

== Power ==

* [[Wikipedia:Lithium-ion polymer battery|Lithium-ion polymer]] [[battery]], 4200mAh design capacity.
** 10-20 hours battery life under reasonable load
** 8-12 hours under max CPU load
** 6-8 hours under max CPU load with overclocking
** 5-6 days standby time
** 21 hours playing music with the display off

* Can charge through an AC adapter or USB. [http://www.gp32x.com/board/index.php?s=&showtopic=40659&view=findpost&p=587802]
** Charging with the AC adapter takes about 4 hours from near-empty. In 2 hours you get to about 80%.

* Advanced power management capabilities: only need to set a max clock speed; when the CPU is not doing anything it automatically HALTs and does nothing to save power. [http://www.gp32x.com/board/index.php?s=&showtopic=38155&view=findpost&p=574380]

* Suspend to RAM or suspend to disk functionality is being developed. This will give longer battery life and faster start up.
** See [[Power modes]].

= More Information =

* [[Hardware documentation]]
* [[Pandora history]]

[[Category:Hardware]]
[[Category:List]]

Template:MainPageUsersLinks

2013-10-04T17:29:58Z

Levi: Hardware docs already linked in the devloper's section

* [[Pandora|About the Pandora]]
** [[User manual | Unofficial user manual]]
** [[Emulators]] • [[Emulator List]]
** [[Games]]
** [[Software projects]]
** [[Port Requests]]
** [[Production Timeline]]
* [[Hardware Hacking]]

Template:MainPageUsersLinks

2013-10-04T17:25:39Z

Levi: Fixing up broken links

* [[Pandora|About the Pandora]]
** [[User manual | Unofficial user manual]]
** [[Hardware_documentation | Hardware FAQs]]
** [[Emulators]] • [[Emulator List]]
** [[Games]]
** [[Software projects]]
** [[Port Requests]]
** [[Production Timeline]]
* [[Hardware Hacking]]

Firmware

2013-09-25T02:17:43Z

Levi: Grr, syntax

#REDIRECT [[Ångström]]

Firmware

2013-09-25T02:16:55Z

Levi: Restoring broken links

#REDIRECT Ångström

LEDs and backlight

2013-09-15T21:32:14Z

Levi: Adding user text to control the backlight

==Status LEDs==

Meaning of the LEDs from left to right according to [http://boards.openpandora.org/index.php?/topic/325-led-function-documented/page__view__findpost__p__5726 gfrancisdev].

Left LED group
* SD card 1
* SD card 2
* Wifi
* Bluetooth

Right LED group
* Empty (with solder pad for hardware hackers who want to use an additional LED)
* Empty (-"-)
* Charging
* Power

==Backlight==

===Brightness===

The screen backlight power is controllable via a number of mechanisms:
* The 'sun' icon next to volume on the task bar - click it and drag the slider that appears to modify backlight power interactively
* The LCD-Settings app under Pandora menu->Settings - choose Change LCD brightness from the menu. This allows you to see the power value to be set, but doesn't change until you accept the setting and close the app
* Using the FN+u and FN+i keyboard shortcuts. This gives you quick access to screen brightness, but doesn't give you fine-grained control.

Note: For the top two methods, you can use the d-pad to change the power step by step. Up and right increase the power by 1 unit, and down or left decrease it similarly.

=== Power Saving ===

The backlight can be configured to dim to display after a period of inactivity. To set this option go to Pandora menu->Settings->LCD-Settings and choose 'Enable/disable screen blanking'.

By default this settings is disabled, since the Pandora disables the screen when the lid is closed, so unless you're in the habit of leaving your Pandora with the lid open for extended periods, this saves power and extends the lifetime of your LCD backlight by itself. Note that the lid closed settings are also configurable under Menu->Settings->Lid-Close-Settings.

== Controlling LEDs and backlight programmatically ==

Available through LED and brightness classes:
<source lang="bash">
/sys/class/leds/*
/sys/class/backlight/*
</source>
LED brightness and trigger and backlight brightness can be controlled through those files. Power and charger LEDs have variable brightness control, others are on/off only.

Note: SD card LEDs use SD cart power supplies, so those must be enabled for those LEDs to work (they are enabled when cards are inserted).

=== backlight power saving ===

Controlled by X server through omapfb_drv.so, ca be disabled by running
<source lang="bash">
xset s off
</source>

==== config ====
Kept in /etc/default/leds (LEDs) and /etc/pandora/conf/brightness.state (backlight).

Note: driver allows lower brightness than you can set using keyboard controls, because some units start to flicker on lowest brightness. This can be changed in /usr/pandora/scripts/op_bright.sh .

=== Keyboard controls ===
Backlight controls, power switch and pandora button are handled by pndevmapperd which calls appropriate scripts as needed. The scripts reside in /usr/pandora/scripts/ . There is a op_test_inputs program included designed to test inputs.

==== config ====
/etc/pandora/conf/eventmap

User manual

2013-09-15T12:17:31Z

Levi: /* Mini Menu */ reword

[[Image:PandoraFront.jpg|Right|thumb|360px|The Pandora.]]

== Introduction ==

The OpenPandora is a pocket sized computer which is a combination of a PC and a Gaming Console. OpenPandora has a D-Pad, Two analogue [[nubs]], ABXY + Shoulder Buttons and a 43-button QWERTY [[keyboard]]. The OpenPandora is fast enough to run a full ARM based Operating System, access the internet, play games and do stuff productively if desired.

==Quick Start Guide ==
If you just want a quick walkthrough on how things work (tl;dr) have a look [[Quickstart | here]]

== Technical Specifications ==

; Outside:

* 140 x 83.4 x 27.5mm, 335g (including battery)
* "Clamshell" design
* 43 button QWERTY and numeric keypad

* Gaming controls:
** Two analog controllers (nubs)
** 8-way D-pad
** A/B/X/Y and shoulder buttons for gaming.
* 800x480 resolution LTPS lcd with resistive touch screen, 4.3" widescreen, 16.7 million colors, 300 cd/m2 brightness, 450:1 contrast ratio
* Two SDHC slots
* Headphone output up to 150mW/channel into 16 ohms, 99dB SNR (up to 24 bit/48KHz)
* Internal microphone plus ability to connect external microphone through headset
* TV Output (composite and S-Video)
* USB 2.0 OTG port (1.5/12/480Mbps) with capability to charge device
* USB 2.0 HOST port (480Mbps) capable of providing the full 500mA to attached devices (examples include USB memory, keyboard, mouse, 3G modem, GPS)
* Two externally accessible UARTs and four PMW signals (for hardware hacking, robot control, debugging, etc.)

; Inside:

* 4200mAh battery.
** 10+ hours of battery life, depending on usage. For example, turning Wi-Fi or the screen off would give better battery life.
* 600MHz Texas Instruments OMAP3530 processor /1GHZ DM3730 Texas Instruments SoC
** Can be clocked higher or lower by software designed for the device.
* 256MB DDR-333 SDRAM (Pre-2012-units), 512MB DDR-333 SDRAM (units made in Germany, 2012)
* 512MB NAND FLASH memory
* IVA2+ audio and video processor using TI's DaVinci™ technology (430MHz C64x DSP)
* ARM ® Cortex™-A8 superscalar microprocessor core
* PowerVR SGX530 110MHz OpenGL ES 2.0 compliant 3D hardware
* Wifi 802.11b/g (up to 18dBm output)
* Bluetooth 2.0 + EDR (3Mbps) (Class 2, + 4dBm)

; More:

* Stereo line level inputs and outputs

* Unbrickable design with integrated boot loader for safe code experimentation.
* Power and hold switch useful for "instant on" and key lockout to aid in media player applications on the go.
* Runs on the Linux Operating System (currently 3.2.x and 2.6.x)

== Box Contents ==

When you first open Pandora's box, a slew of demons and raging emotions may forcibly leave the box. This is normal. After that, you should find the following items:

* The Pandora console
* Stylus (located in stylus slot on the side of the Pandora)
* Battery
* Mains power adapter
* Battery Case

Available separately:

* TV-Out Cable - SDTV over composite or s-video
* Carrying Case
* Extra Battery

== Safety Information ==

*The OpenPandora should not be used by Children under the age of 3 due to potential choking hazards.
*The OpenPandora's Battery should only be charged with supplied charger / Via USB or a suitable third party charger.
*The OpenPandora should only be used in temperatures above -10°C (14°F) and below 40°C (104°F).

== Warranty Information ==

Standard one year warranty applies to the OpenPandora.

* User Neglect / Modifications are generally not covered by warranty.

== First Time Use ==

Place the battery inside the battery compartment underneath the OpenPandora taking care to ensure the battery contacts and battery touch. Please the battery cover on and your OpenPandora will power up.

==== Charging ====

As this is your first time using the Battery it is recommended you fully charge your OpenPandora to 100% using the AC Adapter as this will calibrate and improve the lifetime of your battery. This process may take up to 4 hours. If you're not planning on using the OpenPandora whilst it is charging you should flip the power switch to the left (Low Power Mode) as it should decrease the charging time dramatically.

Once the OpenPandora has completed charging it will stop charging and begin discharging to protect the battery from damage.

You can find more useful information about charging on the [[power modes | Power Modes]] page.

==== First Boot ====

While you are charging your OpenPandora completing the first boot wizard is essential.

===== Steps Involved=====
*Calibrate Touchscreen - This will ensure that the TouchScreen works perfectly.
*Enter Full Name - This personalises your OpenPandora
*Enter Short name - can be a fancy nickname or just your fullname in all lowercase
*Enter Password - anything you like and you'll need to verify it
*Choose a name for your OpenPandora - Give it a fancy name as this will be the network visible name.
*Automatic Login - Entirely up to you. Preferably off if you don't want others to use your OpenPandora without your permission
*GUI choice - Slimmed down basic GUI - Minimenu or full Linux OS - Xfce
*TimeZone / Date and Time - Recommended you do set this correctly as it may cause problems down the track with certain applications.
*CPU Clock Speed - Recommended that you set to Default unless a game / application is running slowly.
*Advanced settings - Do not change until you are comfortable with the device.

====Analog Nubs [http://pandorawiki.org/Nubs]====

The OpenPandora nubs are designed to automatically calibrate when you turn your Pandora & Calibration is lost once the OpenPandora is switched off.

==== Calibrating the Touchscreen ====

The touchscreen in the OpenPandora may / may not be calibrated when you first get it. It is recommended you do run the Calibration Wizard in the first boot wizard alternatively if you clicked too fast you can run the calibration wizard by going to the Settings / Calibrate Touch Screen section in either GUIs

== Basic Use ==
See the [[GUI]] page for more details on the user interfaces which can be used with the Pandora.

===Mini Menu===

[[minimenu | Mini Menu]] is a quick and easy to use launcher created by OpenPandora's great friend Skeezix. Mini Menu is designed to be fully reskinnable.

===== Basic Navigation =====

The main grid of Mini Menu displays the available applications, category tabs, Date / Time, Battery life and a detail pane on the right.

When you copy a PND to SDCARDNAME/pandora/apps it will appear in its preset category.

Controls for Mini Menu:
* D-Pad or touch screen can be used to select PNDs
* Launch a PND by pressing 'Start', 'B' or touching the icon with the stylus or finger.
* Press 'Y' for documentation if there is any available.
* Left and Right shoulder triggers switch categories

=====Skinning=====

Skinning guide in gp32x forum: http://www.gp32x.com/board/index.php?/topic/53990-skinning-minimenu/

A mmskin.conf from February 2011: http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=minimenu/skin/default/mmskin.conf;h=695888b3ae310d7ea04b4e682baed0c0c6fc4349;hb=98c1d081629ac9cbb3056b39097a3db968ce4055 (Skinning will not work without it)

===Desktop style environment (Xfce)===

=====On the Desktop=====

The desktop contains icons which have been found on SD Cards / in Firmware.

=====Pandora Menu & Task Bar=====
On the bottom left the Pandora menu contains all your applications sorted into the appropriate categories.

The task bar by default contains settings for Brightness and Sound, various enablers such as Wifi, Bluetooth and USB host, Network Connectivity, Battery life, Date / Time and various workspaces you can select.

=====Navigation=====
*If a window for an application is too big for the screen you can drag the window around by holding the left trigger and dragging with the stylus.
*Changing your workspace is as easy as holding 'Start' & "Select' then using the D-Pad to switch
*Killing an application is as simple as holding the Pandora button down for 5 seconds, selecting the application and clicking okay

===Power modes===

Pushing the power button to the left will turn the OpenPandora to low power mode for conserving battery which is similar to sleep mode on a computer but the Pandora can still run.

The [[Power modes]] page provides more information.

=== USB Peripherals ===

Connecting USB2 High Speed devices is possible using the standard USB connector or USB On The Go adapter. USB 1.1 devices will only work through a USB hub.
See the [[USB_compatibility_list| USB compatibility list]] for more information

=== Forcing a Restart ===
Occasionally something will happen causing your Pandora to become unresponsive (to the point that even killing a program isn't possible). When this happens it is necessary to force your Pandora to restart. The easiest way to do this is by holding the Pandora button and moving the power switch to the right.

== Firmware ==

==== Updating The Firmware ====

Updating the Firmware can be done via either full Reflash or the Upgrade Pandora OS Application which is found in the System Menu.

==== Reinstalling the Firmware ====

Sometimes things don't work out or you've broken something in the OS. You can reflash the firmware to default by getting the latest package from the [http://boards.openpandora.org/index.php/forum/41-pandora-os-superzaxxon-gnulinux/ forum] and placing in the root of the SD Card then while booting the Pandora hold down the R Button. Reinstalling the OS can take up to 15 minutes

== Applications ==

There's quite a large amount of Applications available for the OpenPandora and there's several distribution points as mentioned below

*[http://repo.openpandora.org OpenPandora Repo] - Has over 1000 applications which are either free or at a very low cost. Applications do not contain DRM.
*[http://dl.openhandshelds.org/cgi-bin/pandora.cgi Open HandHelds] - An older site which may not have the latest applications but you'll find a heap of applications that are archive worthy.
*Angstrom Repository - Contains several applications for your Pandora. It is not really recommended that you use this unless you are an advanced user.
*[http://repo.openpandora.org/?page=detail&app=pndmanager-bzar PND Manager] - A very useful application which syncs with the Repo and allows you to download / install Applications easily.

Installing Applications is as simple as dragging them to the appropriate folders on your SD Card.
These folders are:
* <SD>/pandora/apps - Will appear both on Xfce Desktop & Pandora Menu (this is the 'both' option in PNDManager)
*<SD>/pandora/desktop/ - If you want it to appear on Xfce Desktop
*<SD>/pandora/menu/ - If you want it to appear in Pandora Menu

Some applications will require additional data to work, this data will need to go into:
*<SD>/pandora/appdata/applicationname

The application should generate the required appdata folder when launched.

==Futher reading==
* [[Basic Linux Guide]] - For those who don't know very much about Linux and want to learn more.
* [[Minimenu Configuration Documentation]] - If you want to customize or configure Minimenu.
* [[Games]] - Take a look at the games that are available.
* [[Software projects]] - A list of all non-emulator, non-game software for Pandora.

[[Category:Documentation]]

User manual

2013-09-15T12:13:41Z

Levi: /* Applications */ Capitalisation

[[Image:PandoraFront.jpg|Right|thumb|360px|The Pandora.]]

== Introduction ==

The OpenPandora is a pocket sized computer which is a combination of a PC and a Gaming Console. OpenPandora has a D-Pad, Two analogue [[nubs]], ABXY + Shoulder Buttons and a 43-button QWERTY [[keyboard]]. The OpenPandora is fast enough to run a full ARM based Operating System, access the internet, play games and do stuff productively if desired.

==Quick Start Guide ==
If you just want a quick walkthrough on how things work (tl;dr) have a look [[Quickstart | here]]

== Technical Specifications ==

; Outside:

* 140 x 83.4 x 27.5mm, 335g (including battery)
* "Clamshell" design
* 43 button QWERTY and numeric keypad

* Gaming controls:
** Two analog controllers (nubs)
** 8-way D-pad
** A/B/X/Y and shoulder buttons for gaming.
* 800x480 resolution LTPS lcd with resistive touch screen, 4.3" widescreen, 16.7 million colors, 300 cd/m2 brightness, 450:1 contrast ratio
* Two SDHC slots
* Headphone output up to 150mW/channel into 16 ohms, 99dB SNR (up to 24 bit/48KHz)
* Internal microphone plus ability to connect external microphone through headset
* TV Output (composite and S-Video)
* USB 2.0 OTG port (1.5/12/480Mbps) with capability to charge device
* USB 2.0 HOST port (480Mbps) capable of providing the full 500mA to attached devices (examples include USB memory, keyboard, mouse, 3G modem, GPS)
* Two externally accessible UARTs and four PMW signals (for hardware hacking, robot control, debugging, etc.)

; Inside:

* 4200mAh battery.
** 10+ hours of battery life, depending on usage. For example, turning Wi-Fi or the screen off would give better battery life.
* 600MHz Texas Instruments OMAP3530 processor /1GHZ DM3730 Texas Instruments SoC
** Can be clocked higher or lower by software designed for the device.
* 256MB DDR-333 SDRAM (Pre-2012-units), 512MB DDR-333 SDRAM (units made in Germany, 2012)
* 512MB NAND FLASH memory
* IVA2+ audio and video processor using TI's DaVinci™ technology (430MHz C64x DSP)
* ARM ® Cortex™-A8 superscalar microprocessor core
* PowerVR SGX530 110MHz OpenGL ES 2.0 compliant 3D hardware
* Wifi 802.11b/g (up to 18dBm output)
* Bluetooth 2.0 + EDR (3Mbps) (Class 2, + 4dBm)

; More:

* Stereo line level inputs and outputs

* Unbrickable design with integrated boot loader for safe code experimentation.
* Power and hold switch useful for "instant on" and key lockout to aid in media player applications on the go.
* Runs on the Linux Operating System (currently 3.2.x and 2.6.x)

== Box Contents ==

When you first open Pandora's box, a slew of demons and raging emotions may forcibly leave the box. This is normal. After that, you should find the following items:

* The Pandora console
* Stylus (located in stylus slot on the side of the Pandora)
* Battery
* Mains power adapter
* Battery Case

Available separately:

* TV-Out Cable - SDTV over composite or s-video
* Carrying Case
* Extra Battery

== Safety Information ==

*The OpenPandora should not be used by Children under the age of 3 due to potential choking hazards.
*The OpenPandora's Battery should only be charged with supplied charger / Via USB or a suitable third party charger.
*The OpenPandora should only be used in temperatures above -10°C (14°F) and below 40°C (104°F).

== Warranty Information ==

Standard one year warranty applies to the OpenPandora.

* User Neglect / Modifications are generally not covered by warranty.

== First Time Use ==

Place the battery inside the battery compartment underneath the OpenPandora taking care to ensure the battery contacts and battery touch. Please the battery cover on and your OpenPandora will power up.

==== Charging ====

As this is your first time using the Battery it is recommended you fully charge your OpenPandora to 100% using the AC Adapter as this will calibrate and improve the lifetime of your battery. This process may take up to 4 hours. If you're not planning on using the OpenPandora whilst it is charging you should flip the power switch to the left (Low Power Mode) as it should decrease the charging time dramatically.

Once the OpenPandora has completed charging it will stop charging and begin discharging to protect the battery from damage.

You can find more useful information about charging on the [[power modes | Power Modes]] page.

==== First Boot ====

While you are charging your OpenPandora completing the first boot wizard is essential.

===== Steps Involved=====
*Calibrate Touchscreen - This will ensure that the TouchScreen works perfectly.
*Enter Full Name - This personalises your OpenPandora
*Enter Short name - can be a fancy nickname or just your fullname in all lowercase
*Enter Password - anything you like and you'll need to verify it
*Choose a name for your OpenPandora - Give it a fancy name as this will be the network visible name.
*Automatic Login - Entirely up to you. Preferably off if you don't want others to use your OpenPandora without your permission
*GUI choice - Slimmed down basic GUI - Minimenu or full Linux OS - Xfce
*TimeZone / Date and Time - Recommended you do set this correctly as it may cause problems down the track with certain applications.
*CPU Clock Speed - Recommended that you set to Default unless a game / application is running slowly.
*Advanced settings - Do not change until you are comfortable with the device.

====Analog Nubs [http://pandorawiki.org/Nubs]====

The OpenPandora nubs are designed to automatically calibrate when you turn your Pandora & Calibration is lost once the OpenPandora is switched off.

==== Calibrating the Touchscreen ====

The touchscreen in the OpenPandora may / may not be calibrated when you first get it. It is recommended you do run the Calibration Wizard in the first boot wizard alternatively if you clicked too fast you can run the calibration wizard by going to the Settings / Calibrate Touch Screen section in either GUIs

== Basic Use ==
See the [[GUI]] page for more details on the user interfaces which can be used with the Pandora.

===Mini Menu===

[[minimenu | Mini Menu]] is a quick and easy to use launcher created by OpenPandora's great friend Skeezix. Mini Menu is designed to be capable of fully customised skins.

===== Basic Navigation =====

The main grid of Mini Menu displays the available applications, category tabs, Date / Time, Battery life and a detail pane on the right.

When you copy a PND to SDCARDNAME/pandora/apps it will appear in its preset category.

Controls for Mini Menu:
* D-Pad or touch screen can be used to select PNDs
* Launch a PND by pressing 'Start', 'B' or touching the icon with the stylus or finger.
* Press 'Y' for documentation if there is any available.
* Left and Right shoulder triggers switch categories

=====Skinning=====

Skinning guide in gp32x forum: http://www.gp32x.com/board/index.php?/topic/53990-skinning-minimenu/

A mmskin.conf from February 2011: http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=minimenu/skin/default/mmskin.conf;h=695888b3ae310d7ea04b4e682baed0c0c6fc4349;hb=98c1d081629ac9cbb3056b39097a3db968ce4055 (Skinning will not work without it)

===Desktop style environment (Xfce)===

=====On the Desktop=====

The desktop contains icons which have been found on SD Cards / in Firmware.

=====Pandora Menu & Task Bar=====
On the bottom left the Pandora menu contains all your applications sorted into the appropriate categories.

The task bar by default contains settings for Brightness and Sound, various enablers such as Wifi, Bluetooth and USB host, Network Connectivity, Battery life, Date / Time and various workspaces you can select.

=====Navigation=====
*If a window for an application is too big for the screen you can drag the window around by holding the left trigger and dragging with the stylus.
*Changing your workspace is as easy as holding 'Start' & "Select' then using the D-Pad to switch
*Killing an application is as simple as holding the Pandora button down for 5 seconds, selecting the application and clicking okay

===Power modes===

Pushing the power button to the left will turn the OpenPandora to low power mode for conserving battery which is similar to sleep mode on a computer but the Pandora can still run.

The [[Power modes]] page provides more information.

=== USB Peripherals ===

Connecting USB2 High Speed devices is possible using the standard USB connector or USB On The Go adapter. USB 1.1 devices will only work through a USB hub.
See the [[USB_compatibility_list| USB compatibility list]] for more information

=== Forcing a Restart ===
Occasionally something will happen causing your Pandora to become unresponsive (to the point that even killing a program isn't possible). When this happens it is necessary to force your Pandora to restart. The easiest way to do this is by holding the Pandora button and moving the power switch to the right.

== Firmware ==

==== Updating The Firmware ====

Updating the Firmware can be done via either full Reflash or the Upgrade Pandora OS Application which is found in the System Menu.

==== Reinstalling the Firmware ====

Sometimes things don't work out or you've broken something in the OS. You can reflash the firmware to default by getting the latest package from the [http://boards.openpandora.org/index.php/forum/41-pandora-os-superzaxxon-gnulinux/ forum] and placing in the root of the SD Card then while booting the Pandora hold down the R Button. Reinstalling the OS can take up to 15 minutes

== Applications ==

There's quite a large amount of Applications available for the OpenPandora and there's several distribution points as mentioned below

*[http://repo.openpandora.org OpenPandora Repo] - Has over 1000 applications which are either free or at a very low cost. Applications do not contain DRM.
*[http://dl.openhandshelds.org/cgi-bin/pandora.cgi Open HandHelds] - An older site which may not have the latest applications but you'll find a heap of applications that are archive worthy.
*Angstrom Repository - Contains several applications for your Pandora. It is not really recommended that you use this unless you are an advanced user.
*[http://repo.openpandora.org/?page=detail&app=pndmanager-bzar PND Manager] - A very useful application which syncs with the Repo and allows you to download / install Applications easily.

Installing Applications is as simple as dragging them to the appropriate folders on your SD Card.
These folders are:
* <SD>/pandora/apps - Will appear both on Xfce Desktop & Pandora Menu (this is the 'both' option in PNDManager)
*<SD>/pandora/desktop/ - If you want it to appear on Xfce Desktop
*<SD>/pandora/menu/ - If you want it to appear in Pandora Menu

Some applications will require additional data to work, this data will need to go into:
*<SD>/pandora/appdata/applicationname

The application should generate the required appdata folder when launched.

==Futher reading==
* [[Basic Linux Guide]] - For those who don't know very much about Linux and want to learn more.
* [[Minimenu Configuration Documentation]] - If you want to customize or configure Minimenu.
* [[Games]] - Take a look at the games that are available.
* [[Software projects]] - A list of all non-emulator, non-game software for Pandora.

[[Category:Documentation]]

User manual

2013-09-15T12:12:57Z

Levi: /* Steps Involved */ typos

[[Image:PandoraFront.jpg|Right|thumb|360px|The Pandora.]]

== Introduction ==

The OpenPandora is a pocket sized computer which is a combination of a PC and a Gaming Console. OpenPandora has a D-Pad, Two analogue [[nubs]], ABXY + Shoulder Buttons and a 43-button QWERTY [[keyboard]]. The OpenPandora is fast enough to run a full ARM based Operating System, access the internet, play games and do stuff productively if desired.

==Quick Start Guide ==
If you just want a quick walkthrough on how things work (tl;dr) have a look [[Quickstart | here]]

== Technical Specifications ==

; Outside:

* 140 x 83.4 x 27.5mm, 335g (including battery)
* "Clamshell" design
* 43 button QWERTY and numeric keypad

* Gaming controls:
** Two analog controllers (nubs)
** 8-way D-pad
** A/B/X/Y and shoulder buttons for gaming.
* 800x480 resolution LTPS lcd with resistive touch screen, 4.3" widescreen, 16.7 million colors, 300 cd/m2 brightness, 450:1 contrast ratio
* Two SDHC slots
* Headphone output up to 150mW/channel into 16 ohms, 99dB SNR (up to 24 bit/48KHz)
* Internal microphone plus ability to connect external microphone through headset
* TV Output (composite and S-Video)
* USB 2.0 OTG port (1.5/12/480Mbps) with capability to charge device
* USB 2.0 HOST port (480Mbps) capable of providing the full 500mA to attached devices (examples include USB memory, keyboard, mouse, 3G modem, GPS)
* Two externally accessible UARTs and four PMW signals (for hardware hacking, robot control, debugging, etc.)

; Inside:

* 4200mAh battery.
** 10+ hours of battery life, depending on usage. For example, turning Wi-Fi or the screen off would give better battery life.
* 600MHz Texas Instruments OMAP3530 processor /1GHZ DM3730 Texas Instruments SoC
** Can be clocked higher or lower by software designed for the device.
* 256MB DDR-333 SDRAM (Pre-2012-units), 512MB DDR-333 SDRAM (units made in Germany, 2012)
* 512MB NAND FLASH memory
* IVA2+ audio and video processor using TI's DaVinci™ technology (430MHz C64x DSP)
* ARM ® Cortex™-A8 superscalar microprocessor core
* PowerVR SGX530 110MHz OpenGL ES 2.0 compliant 3D hardware
* Wifi 802.11b/g (up to 18dBm output)
* Bluetooth 2.0 + EDR (3Mbps) (Class 2, + 4dBm)

; More:

* Stereo line level inputs and outputs

* Unbrickable design with integrated boot loader for safe code experimentation.
* Power and hold switch useful for "instant on" and key lockout to aid in media player applications on the go.
* Runs on the Linux Operating System (currently 3.2.x and 2.6.x)

== Box Contents ==

When you first open Pandora's box, a slew of demons and raging emotions may forcibly leave the box. This is normal. After that, you should find the following items:

* The Pandora console
* Stylus (located in stylus slot on the side of the Pandora)
* Battery
* Mains power adapter
* Battery Case

Available separately:

* TV-Out Cable - SDTV over composite or s-video
* Carrying Case
* Extra Battery

== Safety Information ==

*The OpenPandora should not be used by Children under the age of 3 due to potential choking hazards.
*The OpenPandora's Battery should only be charged with supplied charger / Via USB or a suitable third party charger.
*The OpenPandora should only be used in temperatures above -10°C (14°F) and below 40°C (104°F).

== Warranty Information ==

Standard one year warranty applies to the OpenPandora.

* User Neglect / Modifications are generally not covered by warranty.

== First Time Use ==

Place the battery inside the battery compartment underneath the OpenPandora taking care to ensure the battery contacts and battery touch. Please the battery cover on and your OpenPandora will power up.

==== Charging ====

As this is your first time using the Battery it is recommended you fully charge your OpenPandora to 100% using the AC Adapter as this will calibrate and improve the lifetime of your battery. This process may take up to 4 hours. If you're not planning on using the OpenPandora whilst it is charging you should flip the power switch to the left (Low Power Mode) as it should decrease the charging time dramatically.

Once the OpenPandora has completed charging it will stop charging and begin discharging to protect the battery from damage.

You can find more useful information about charging on the [[power modes | Power Modes]] page.

==== First Boot ====

While you are charging your OpenPandora completing the first boot wizard is essential.

===== Steps Involved=====
*Calibrate Touchscreen - This will ensure that the TouchScreen works perfectly.
*Enter Full Name - This personalises your OpenPandora
*Enter Short name - can be a fancy nickname or just your fullname in all lowercase
*Enter Password - anything you like and you'll need to verify it
*Choose a name for your OpenPandora - Give it a fancy name as this will be the network visible name.
*Automatic Login - Entirely up to you. Preferably off if you don't want others to use your OpenPandora without your permission
*GUI choice - Slimmed down basic GUI - Minimenu or full Linux OS - Xfce
*TimeZone / Date and Time - Recommended you do set this correctly as it may cause problems down the track with certain applications.
*CPU Clock Speed - Recommended that you set to Default unless a game / application is running slowly.
*Advanced settings - Do not change until you are comfortable with the device.

====Analog Nubs [http://pandorawiki.org/Nubs]====

The OpenPandora nubs are designed to automatically calibrate when you turn your Pandora & Calibration is lost once the OpenPandora is switched off.

==== Calibrating the Touchscreen ====

The touchscreen in the OpenPandora may / may not be calibrated when you first get it. It is recommended you do run the Calibration Wizard in the first boot wizard alternatively if you clicked too fast you can run the calibration wizard by going to the Settings / Calibrate Touch Screen section in either GUIs

== Basic Use ==
See the [[GUI]] page for more details on the user interfaces which can be used with the Pandora.

===Mini Menu===

[[minimenu | Mini Menu]] is a quick and easy to use launcher created by OpenPandora's great friend Skeezix. Mini Menu is designed to be capable of fully customised skins.

===== Basic Navigation =====

The main grid of Mini Menu displays the available applications, category tabs, Date / Time, Battery life and a detail pane on the right.

When you copy a PND to SDCARDNAME/pandora/apps it will appear in its preset category.

Controls for Mini Menu:
* D-Pad or touch screen can be used to select PNDs
* Launch a PND by pressing 'Start', 'B' or touching the icon with the stylus or finger.
* Press 'Y' for documentation if there is any available.
* Left and Right shoulder triggers switch categories

=====Skinning=====

Skinning guide in gp32x forum: http://www.gp32x.com/board/index.php?/topic/53990-skinning-minimenu/

A mmskin.conf from February 2011: http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=minimenu/skin/default/mmskin.conf;h=695888b3ae310d7ea04b4e682baed0c0c6fc4349;hb=98c1d081629ac9cbb3056b39097a3db968ce4055 (Skinning will not work without it)

===Desktop style environment (Xfce)===

=====On the Desktop=====

The desktop contains icons which have been found on SD Cards / in Firmware.

=====Pandora Menu & Task Bar=====
On the bottom left the Pandora menu contains all your applications sorted into the appropriate categories.

The task bar by default contains settings for Brightness and Sound, various enablers such as Wifi, Bluetooth and USB host, Network Connectivity, Battery life, Date / Time and various workspaces you can select.

=====Navigation=====
*If a window for an application is too big for the screen you can drag the window around by holding the left trigger and dragging with the stylus.
*Changing your workspace is as easy as holding 'Start' & "Select' then using the D-Pad to switch
*Killing an application is as simple as holding the Pandora button down for 5 seconds, selecting the application and clicking okay

===Power modes===

Pushing the power button to the left will turn the OpenPandora to low power mode for conserving battery which is similar to sleep mode on a computer but the Pandora can still run.

The [[Power modes]] page provides more information.

=== USB Peripherals ===

Connecting USB2 High Speed devices is possible using the standard USB connector or USB On The Go adapter. USB 1.1 devices will only work through a USB hub.
See the [[USB_compatibility_list| USB compatibility list]] for more information

=== Forcing a Restart ===
Occasionally something will happen causing your Pandora to become unresponsive (to the point that even killing a program isn't possible). When this happens it is necessary to force your Pandora to restart. The easiest way to do this is by holding the Pandora button and moving the power switch to the right.

== Firmware ==

==== Updating The Firmware ====

Updating the Firmware can be done via either full Reflash or the Upgrade Pandora OS Application which is found in the System Menu.

==== Reinstalling the Firmware ====

Sometimes things don't work out or you've broken something in the OS. You can reflash the firmware to default by getting the latest package from the [http://boards.openpandora.org/index.php/forum/41-pandora-os-superzaxxon-gnulinux/ forum] and placing in the root of the SD Card then while booting the Pandora hold down the R Button. Reinstalling the OS can take up to 15 minutes

== Applications ==

There's quite a large amount of Applications available for the OpenPandora and there's several distribution points as mentioned below

*[http://repo.openpandora.org OpenPandora Repo] - Has over 1000 applications which are either free or at a very low cost. Applications do not contain DRM.
*[http://dl.openhandshelds.org/cgi-bin/pandora.cgi Open HandHelds] - An older site which may not have the latest applications but you'll find a heap of applications that are archive worthy.
*Angstrom Repository - Contains several applications for your Pandora. It is not really recommended that you use this unless you are an advanced user.
*[http://repo.openpandora.org/?page=detail&app=pndmanager-bzar PND Manager] - A very useful application which syncs with the Repo and allows you to download / install Applications easily.

Installing Applications is as simple as dragging them to the appropriate folders on your SD Card.
These folders are:
* <SD>/pandora/apps - Will appear both on xFCE Desktop & Pandora Menu (this is the 'both' option in PNDManager)
*<SD>/pandora/desktop/ - If you want it to appear on xFCE Desktop
*<SD>/pandora/menu/ - If you want it to appear in Pandora Menu

Some applications will require additional data to work, this data will need to go into:
*<SD>/pandora/appdata/applicationname

The application should generate the required appdata folder when launched.

==Futher reading==
* [[Basic Linux Guide]] - For those who don't know very much about Linux and want to learn more.
* [[Minimenu Configuration Documentation]] - If you want to customize or configure Minimenu.
* [[Games]] - Take a look at the games that are available.
* [[Software projects]] - A list of all non-emulator, non-game software for Pandora.

[[Category:Documentation]]

User manual

2013-09-15T12:10:20Z

Levi: /* Box Contents */ TV cable

[[Image:PandoraFront.jpg|Right|thumb|360px|The Pandora.]]

== Introduction ==

The OpenPandora is a pocket sized computer which is a combination of a PC and a Gaming Console. OpenPandora has a D-Pad, Two analogue [[nubs]], ABXY + Shoulder Buttons and a 43-button QWERTY [[keyboard]]. The OpenPandora is fast enough to run a full ARM based Operating System, access the internet, play games and do stuff productively if desired.

==Quick Start Guide ==
If you just want a quick walkthrough on how things work (tl;dr) have a look [[Quickstart | here]]

== Technical Specifications ==

; Outside:

* 140 x 83.4 x 27.5mm, 335g (including battery)
* "Clamshell" design
* 43 button QWERTY and numeric keypad

* Gaming controls:
** Two analog controllers (nubs)
** 8-way D-pad
** A/B/X/Y and shoulder buttons for gaming.
* 800x480 resolution LTPS lcd with resistive touch screen, 4.3" widescreen, 16.7 million colors, 300 cd/m2 brightness, 450:1 contrast ratio
* Two SDHC slots
* Headphone output up to 150mW/channel into 16 ohms, 99dB SNR (up to 24 bit/48KHz)
* Internal microphone plus ability to connect external microphone through headset
* TV Output (composite and S-Video)
* USB 2.0 OTG port (1.5/12/480Mbps) with capability to charge device
* USB 2.0 HOST port (480Mbps) capable of providing the full 500mA to attached devices (examples include USB memory, keyboard, mouse, 3G modem, GPS)
* Two externally accessible UARTs and four PMW signals (for hardware hacking, robot control, debugging, etc.)

; Inside:

* 4200mAh battery.
** 10+ hours of battery life, depending on usage. For example, turning Wi-Fi or the screen off would give better battery life.
* 600MHz Texas Instruments OMAP3530 processor /1GHZ DM3730 Texas Instruments SoC
** Can be clocked higher or lower by software designed for the device.
* 256MB DDR-333 SDRAM (Pre-2012-units), 512MB DDR-333 SDRAM (units made in Germany, 2012)
* 512MB NAND FLASH memory
* IVA2+ audio and video processor using TI's DaVinci™ technology (430MHz C64x DSP)
* ARM ® Cortex™-A8 superscalar microprocessor core
* PowerVR SGX530 110MHz OpenGL ES 2.0 compliant 3D hardware
* Wifi 802.11b/g (up to 18dBm output)
* Bluetooth 2.0 + EDR (3Mbps) (Class 2, + 4dBm)

; More:

* Stereo line level inputs and outputs

* Unbrickable design with integrated boot loader for safe code experimentation.
* Power and hold switch useful for "instant on" and key lockout to aid in media player applications on the go.
* Runs on the Linux Operating System (currently 3.2.x and 2.6.x)

== Box Contents ==

When you first open Pandora's box, a slew of demons and raging emotions may forcibly leave the box. This is normal. After that, you should find the following items:

* The Pandora console
* Stylus (located in stylus slot on the side of the Pandora)
* Battery
* Mains power adapter
* Battery Case

Available separately:

* TV-Out Cable - SDTV over composite or s-video
* Carrying Case
* Extra Battery

== Safety Information ==

*The OpenPandora should not be used by Children under the age of 3 due to potential choking hazards.
*The OpenPandora's Battery should only be charged with supplied charger / Via USB or a suitable third party charger.
*The OpenPandora should only be used in temperatures above -10°C (14°F) and below 40°C (104°F).

== Warranty Information ==

Standard one year warranty applies to the OpenPandora.

* User Neglect / Modifications are generally not covered by warranty.

== First Time Use ==

Place the battery inside the battery compartment underneath the OpenPandora taking care to ensure the battery contacts and battery touch. Please the battery cover on and your OpenPandora will power up.

==== Charging ====

As this is your first time using the Battery it is recommended you fully charge your OpenPandora to 100% using the AC Adapter as this will calibrate and improve the lifetime of your battery. This process may take up to 4 hours. If you're not planning on using the OpenPandora whilst it is charging you should flip the power switch to the left (Low Power Mode) as it should decrease the charging time dramatically.

Once the OpenPandora has completed charging it will stop charging and begin discharging to protect the battery from damage.

You can find more useful information about charging on the [[power modes | Power Modes]] page.

==== First Boot ====

While you are charging your OpenPandora completing the first boot wizard is essential.

===== Steps Involved=====
*Calibrate Touchscreen - This will ensure that the TouchScreen works perfectly.
*Enter Full Name - This personalises your OpenPandora
*Enter Short name - can be a fancy nickname or just your fullname in all lowercase
*Enter Password - anything you like and you'll need to verify it
*Choose a name for your OpenPandora - Give it a fancy name as this will be the network visible name.
*Automatic Login - Entirely up to you. Preferable off if you don't want others to use your OpenPandora without your permission
*GUI choice - Slimmed down basic GUI - Minimenu or full Linux OS - xFCE
*TimeZone / Date and Time - Recommended you do set this correctly as it may cause problems down the track with certain applications.
*CPU Clock Speed - Recommended that you set to Default unless a game / application is running slowly.
*Advanced settings - Do not change until you are comfortable with the device.

====Analog Nubs [http://pandorawiki.org/Nubs]====

The OpenPandora nubs are designed to automatically calibrate when you turn your Pandora & Calibration is lost once the OpenPandora is switched off.

==== Calibrating the Touchscreen ====

The touchscreen in the OpenPandora may / may not be calibrated when you first get it. It is recommended you do run the Calibration Wizard in the first boot wizard alternatively if you clicked too fast you can run the calibration wizard by going to the Settings / Calibrate Touch Screen section in either GUIs

== Basic Use ==
See the [[GUI]] page for more details on the user interfaces which can be used with the Pandora.

===Mini Menu===

[[minimenu | Mini Menu]] is a quick and easy to use launcher created by OpenPandora's great friend Skeezix. Mini Menu is designed to be capable of fully customised skins.

===== Basic Navigation =====

The main grid of Mini Menu displays the available applications, category tabs, Date / Time, Battery life and a detail pane on the right.

When you copy a PND to SDCARDNAME/pandora/apps it will appear in its preset category.

Controls for Mini Menu:
* D-Pad or touch screen can be used to select PNDs
* Launch a PND by pressing 'Start', 'B' or touching the icon with the stylus or finger.
* Press 'Y' for documentation if there is any available.
* Left and Right shoulder triggers switch categories

=====Skinning=====

Skinning guide in gp32x forum: http://www.gp32x.com/board/index.php?/topic/53990-skinning-minimenu/

A mmskin.conf from February 2011: http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=minimenu/skin/default/mmskin.conf;h=695888b3ae310d7ea04b4e682baed0c0c6fc4349;hb=98c1d081629ac9cbb3056b39097a3db968ce4055 (Skinning will not work without it)

===Desktop style environment (Xfce)===

=====On the Desktop=====

The desktop contains icons which have been found on SD Cards / in Firmware.

=====Pandora Menu & Task Bar=====
On the bottom left the Pandora menu contains all your applications sorted into the appropriate categories.

The task bar by default contains settings for Brightness and Sound, various enablers such as Wifi, Bluetooth and USB host, Network Connectivity, Battery life, Date / Time and various workspaces you can select.

=====Navigation=====
*If a window for an application is too big for the screen you can drag the window around by holding the left trigger and dragging with the stylus.
*Changing your workspace is as easy as holding 'Start' & "Select' then using the D-Pad to switch
*Killing an application is as simple as holding the Pandora button down for 5 seconds, selecting the application and clicking okay

===Power modes===

Pushing the power button to the left will turn the OpenPandora to low power mode for conserving battery which is similar to sleep mode on a computer but the Pandora can still run.

The [[Power modes]] page provides more information.

=== USB Peripherals ===

Connecting USB2 High Speed devices is possible using the standard USB connector or USB On The Go adapter. USB 1.1 devices will only work through a USB hub.
See the [[USB_compatibility_list| USB compatibility list]] for more information

=== Forcing a Restart ===
Occasionally something will happen causing your Pandora to become unresponsive (to the point that even killing a program isn't possible). When this happens it is necessary to force your Pandora to restart. The easiest way to do this is by holding the Pandora button and moving the power switch to the right.

== Firmware ==

==== Updating The Firmware ====

Updating the Firmware can be done via either full Reflash or the Upgrade Pandora OS Application which is found in the System Menu.

==== Reinstalling the Firmware ====

Sometimes things don't work out or you've broken something in the OS. You can reflash the firmware to default by getting the latest package from the [http://boards.openpandora.org/index.php/forum/41-pandora-os-superzaxxon-gnulinux/ forum] and placing in the root of the SD Card then while booting the Pandora hold down the R Button. Reinstalling the OS can take up to 15 minutes

== Applications ==

There's quite a large amount of Applications available for the OpenPandora and there's several distribution points as mentioned below

*[http://repo.openpandora.org OpenPandora Repo] - Has over 1000 applications which are either free or at a very low cost. Applications do not contain DRM.
*[http://dl.openhandshelds.org/cgi-bin/pandora.cgi Open HandHelds] - An older site which may not have the latest applications but you'll find a heap of applications that are archive worthy.
*Angstrom Repository - Contains several applications for your Pandora. It is not really recommended that you use this unless you are an advanced user.
*[http://repo.openpandora.org/?page=detail&app=pndmanager-bzar PND Manager] - A very useful application which syncs with the Repo and allows you to download / install Applications easily.

Installing Applications is as simple as dragging them to the appropriate folders on your SD Card.
These folders are:
* <SD>/pandora/apps - Will appear both on xFCE Desktop & Pandora Menu (this is the 'both' option in PNDManager)
*<SD>/pandora/desktop/ - If you want it to appear on xFCE Desktop
*<SD>/pandora/menu/ - If you want it to appear in Pandora Menu

Some applications will require additional data to work, this data will need to go into:
*<SD>/pandora/appdata/applicationname

The application should generate the required appdata folder when launched.

==Futher reading==
* [[Basic Linux Guide]] - For those who don't know very much about Linux and want to learn more.
* [[Minimenu Configuration Documentation]] - If you want to customize or configure Minimenu.
* [[Games]] - Take a look at the games that are available.
* [[Software projects]] - A list of all non-emulator, non-game software for Pandora.

[[Category:Documentation]]

User manual

2013-09-15T11:07:49Z

Levi: /* Pandora Menu & Task Bar */

[[Image:PandoraFront.jpg|Right|thumb|360px|The Pandora.]]

== Introduction ==

The OpenPandora is a pocket sized computer which is a combination of a PC and a Gaming Console. OpenPandora has a D-Pad, Two analogue [[nubs]], ABXY + Shoulder Buttons and a 43-button QWERTY [[keyboard]]. The OpenPandora is fast enough to run a full ARM based Operating System, access the internet, play games and do stuff productively if desired.

==Quick Start Guide ==
If you just want a quick walkthrough on how things work (tl;dr) have a look [[Quickstart | here]]

== Technical Specifications ==

; Outside:

* 140 x 83.4 x 27.5mm, 335g (including battery)
* "Clamshell" design
* 43 button QWERTY and numeric keypad

* Gaming controls:
** Two analog controllers (nubs)
** 8-way D-pad
** A/B/X/Y and shoulder buttons for gaming.
* 800x480 resolution LTPS lcd with resistive touch screen, 4.3" widescreen, 16.7 million colors, 300 cd/m2 brightness, 450:1 contrast ratio
* Two SDHC slots
* Headphone output up to 150mW/channel into 16 ohms, 99dB SNR (up to 24 bit/48KHz)
* Internal microphone plus ability to connect external microphone through headset
* TV Output (composite and S-Video)
* USB 2.0 OTG port (1.5/12/480Mbps) with capability to charge device
* USB 2.0 HOST port (480Mbps) capable of providing the full 500mA to attached devices (examples include USB memory, keyboard, mouse, 3G modem, GPS)
* Two externally accessible UARTs and four PMW signals (for hardware hacking, robot control, debugging, etc.)

; Inside:

* 4200mAh battery.
** 10+ hours of battery life, depending on usage. For example, turning Wi-Fi or the screen off would give better battery life.
* 600MHz Texas Instruments OMAP3530 processor /1GHZ DM3730 Texas Instruments SoC
** Can be clocked higher or lower by software designed for the device.
* 256MB DDR-333 SDRAM (Pre-2012-units), 512MB DDR-333 SDRAM (units made in Germany, 2012)
* 512MB NAND FLASH memory
* IVA2+ audio and video processor using TI's DaVinci™ technology (430MHz C64x DSP)
* ARM ® Cortex™-A8 superscalar microprocessor core
* PowerVR SGX530 110MHz OpenGL ES 2.0 compliant 3D hardware
* Wifi 802.11b/g (up to 18dBm output)
* Bluetooth 2.0 + EDR (3Mbps) (Class 2, + 4dBm)

; More:

* Stereo line level inputs and outputs

* Unbrickable design with integrated boot loader for safe code experimentation.
* Power and hold switch useful for "instant on" and key lockout to aid in media player applications on the go.
* Runs on the Linux Operating System (currently 3.2.x and 2.6.x)

== Box Contents ==

When you first open Pandora's box, a slew of demons and raging emotions may forcibly leave the box. This is normal. After that, you should find the following items:

* The Pandora console
* Stylus (located in stylus slot on the side of the Pandora)
* Battery
* Mains power adapter
* Battery Case

Available separately:

* TV-Out Cable
** As of 3rd November 2010 these are not yet included in the box and will ship separately as available.
* Carrying Case
* Extra Battery

== Safety Information ==

*The OpenPandora should not be used by Children under the age of 3 due to potential choking hazards.
*The OpenPandora's Battery should only be charged with supplied charger / Via USB or a suitable third party charger.
*The OpenPandora should only be used in temperatures above -10°C (14°F) and below 40°C (104°F).

== Warranty Information ==

Standard one year warranty applies to the OpenPandora.

* User Neglect / Modifications are generally not covered by warranty.

== First Time Use ==

Place the battery inside the battery compartment underneath the OpenPandora taking care to ensure the battery contacts and battery touch. Please the battery cover on and your OpenPandora will power up.

==== Charging ====

As this is your first time using the Battery it is recommended you fully charge your OpenPandora to 100% using the AC Adapter as this will calibrate and improve the lifetime of your battery. This process may take up to 4 hours. If you're not planning on using the OpenPandora whilst it is charging you should flip the power switch to the left (Low Power Mode) as it should decrease the charging time dramatically.

Once the OpenPandora has completed charging it will stop charging and begin discharging to protect the battery from damage.

You can find more useful information about charging on the [[power modes | Power Modes]] page.

==== First Boot ====

While you are charging your OpenPandora completing the first boot wizard is essential.

===== Steps Involved=====
*Calibrate Touchscreen - This will ensure that the TouchScreen works perfectly.
*Enter Full Name - This personalises your OpenPandora
*Enter Short name - can be a fancy nickname or just your fullname in all lowercase
*Enter Password - anything you like and you'll need to verify it
*Choose a name for your OpenPandora - Give it a fancy name as this will be the network visible name.
*Automatic Login - Entirely up to you. Preferable off if you don't want others to use your OpenPandora without your permission
*GUI choice - Slimmed down basic GUI - Minimenu or full Linux OS - xFCE
*TimeZone / Date and Time - Recommended you do set this correctly as it may cause problems down the track with certain applications.
*CPU Clock Speed - Recommended that you set to Default unless a game / application is running slowly.
*Advanced settings - Do not change until you are comfortable with the device.

====Analog Nubs [http://pandorawiki.org/Nubs]====

The OpenPandora nubs are designed to automatically calibrate when you turn your Pandora & Calibration is lost once the OpenPandora is switched off.

==== Calibrating the Touchscreen ====

The touchscreen in the OpenPandora may / may not be calibrated when you first get it. It is recommended you do run the Calibration Wizard in the first boot wizard alternatively if you clicked too fast you can run the calibration wizard by going to the Settings / Calibrate Touch Screen section in either GUIs

== Basic Use ==
See the [[GUI]] page for more details on the user interfaces which can be used with the Pandora.

===Mini Menu===

[[minimenu | Mini Menu]] is a quick and easy to use launcher created by OpenPandora's great friend Skeezix. Mini Menu is designed to be capable of fully customised skins.

===== Basic Navigation =====

The main grid of Mini Menu displays the available applications, category tabs, Date / Time, Battery life and a detail pane on the right.

When you copy a PND to SDCARDNAME/pandora/apps it will appear in its preset category.

Controls for Mini Menu:
* D-Pad or touch screen can be used to select PNDs
* Launch a PND by pressing 'Start', 'B' or touching the icon with the stylus or finger.
* Press 'Y' for documentation if there is any available.
* Left and Right shoulder triggers switch categories

=====Skinning=====

Skinning guide in gp32x forum: http://www.gp32x.com/board/index.php?/topic/53990-skinning-minimenu/

A mmskin.conf from February 2011: http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=minimenu/skin/default/mmskin.conf;h=695888b3ae310d7ea04b4e682baed0c0c6fc4349;hb=98c1d081629ac9cbb3056b39097a3db968ce4055 (Skinning will not work without it)

===Desktop style environment (Xfce)===

=====On the Desktop=====

The desktop contains icons which have been found on SD Cards / in Firmware.

=====Pandora Menu & Task Bar=====
On the bottom left the Pandora menu contains all your applications sorted into the appropriate categories.

The task bar by default contains settings for Brightness and Sound, various enablers such as Wifi, Bluetooth and USB host, Network Connectivity, Battery life, Date / Time and various workspaces you can select.

=====Navigation=====
*If a window for an application is too big for the screen you can drag the window around by holding the left trigger and dragging with the stylus.
*Changing your workspace is as easy as holding 'Start' & "Select' then using the D-Pad to switch
*Killing an application is as simple as holding the Pandora button down for 5 seconds, selecting the application and clicking okay

===Power modes===

Pushing the power button to the left will turn the OpenPandora to low power mode for conserving battery which is similar to sleep mode on a computer but the Pandora can still run.

The [[Power modes]] page provides more information.

=== USB Peripherals ===

Connecting USB2 High Speed devices is possible using the standard USB connector or USB On The Go adapter. USB 1.1 devices will only work through a USB hub.
See the [[USB_compatibility_list| USB compatibility list]] for more information

=== Forcing a Restart ===
Occasionally something will happen causing your Pandora to become unresponsive (to the point that even killing a program isn't possible). When this happens it is necessary to force your Pandora to restart. The easiest way to do this is by holding the Pandora button and moving the power switch to the right.

== Firmware ==

==== Updating The Firmware ====

Updating the Firmware can be done via either full Reflash or the Upgrade Pandora OS Application which is found in the System Menu.

==== Reinstalling the Firmware ====

Sometimes things don't work out or you've broken something in the OS. You can reflash the firmware to default by getting the latest package from the [http://boards.openpandora.org/index.php/forum/41-pandora-os-superzaxxon-gnulinux/ forum] and placing in the root of the SD Card then while booting the Pandora hold down the R Button. Reinstalling the OS can take up to 15 minutes

== Applications ==

There's quite a large amount of Applications available for the OpenPandora and there's several distribution points as mentioned below

*[http://repo.openpandora.org OpenPandora Repo] - Has over 1000 applications which are either free or at a very low cost. Applications do not contain DRM.
*[http://dl.openhandshelds.org/cgi-bin/pandora.cgi Open HandHelds] - An older site which may not have the latest applications but you'll find a heap of applications that are archive worthy.
*Angstrom Repository - Contains several applications for your Pandora. It is not really recommended that you use this unless you are an advanced user.
*[http://repo.openpandora.org/?page=detail&app=pndmanager-bzar PND Manager] - A very useful application which syncs with the Repo and allows you to download / install Applications easily.

Installing Applications is as simple as dragging them to the appropriate folders on your SD Card.
These folders are:
* <SD>/pandora/apps - Will appear both on xFCE Desktop & Pandora Menu (this is the 'both' option in PNDManager)
*<SD>/pandora/desktop/ - If you want it to appear on xFCE Desktop
*<SD>/pandora/menu/ - If you want it to appear in Pandora Menu

Some applications will require additional data to work, this data will need to go into:
*<SD>/pandora/appdata/applicationname

The application should generate the required appdata folder when launched.

==Futher reading==
* [[Basic Linux Guide]] - For those who don't know very much about Linux and want to learn more.
* [[Minimenu Configuration Documentation]] - If you want to customize or configure Minimenu.
* [[Games]] - Take a look at the games that are available.
* [[Software projects]] - A list of all non-emulator, non-game software for Pandora.

[[Category:Documentation]]

User manual

2013-09-15T11:05:44Z

Levi: /* Applications */

[[Image:PandoraFront.jpg|Right|thumb|360px|The Pandora.]]

== Introduction ==

The OpenPandora is a pocket sized computer which is a combination of a PC and a Gaming Console. OpenPandora has a D-Pad, Two analogue [[nubs]], ABXY + Shoulder Buttons and a 43-button QWERTY [[keyboard]]. The OpenPandora is fast enough to run a full ARM based Operating System, access the internet, play games and do stuff productively if desired.

==Quick Start Guide ==
If you just want a quick walkthrough on how things work (tl;dr) have a look [[Quickstart | here]]

== Technical Specifications ==

; Outside:

* 140 x 83.4 x 27.5mm, 335g (including battery)
* "Clamshell" design
* 43 button QWERTY and numeric keypad

* Gaming controls:
** Two analog controllers (nubs)
** 8-way D-pad
** A/B/X/Y and shoulder buttons for gaming.
* 800x480 resolution LTPS lcd with resistive touch screen, 4.3" widescreen, 16.7 million colors, 300 cd/m2 brightness, 450:1 contrast ratio
* Two SDHC slots
* Headphone output up to 150mW/channel into 16 ohms, 99dB SNR (up to 24 bit/48KHz)
* Internal microphone plus ability to connect external microphone through headset
* TV Output (composite and S-Video)
* USB 2.0 OTG port (1.5/12/480Mbps) with capability to charge device
* USB 2.0 HOST port (480Mbps) capable of providing the full 500mA to attached devices (examples include USB memory, keyboard, mouse, 3G modem, GPS)
* Two externally accessible UARTs and four PMW signals (for hardware hacking, robot control, debugging, etc.)

; Inside:

* 4200mAh battery.
** 10+ hours of battery life, depending on usage. For example, turning Wi-Fi or the screen off would give better battery life.
* 600MHz Texas Instruments OMAP3530 processor /1GHZ DM3730 Texas Instruments SoC
** Can be clocked higher or lower by software designed for the device.
* 256MB DDR-333 SDRAM (Pre-2012-units), 512MB DDR-333 SDRAM (units made in Germany, 2012)
* 512MB NAND FLASH memory
* IVA2+ audio and video processor using TI's DaVinci™ technology (430MHz C64x DSP)
* ARM ® Cortex™-A8 superscalar microprocessor core
* PowerVR SGX530 110MHz OpenGL ES 2.0 compliant 3D hardware
* Wifi 802.11b/g (up to 18dBm output)
* Bluetooth 2.0 + EDR (3Mbps) (Class 2, + 4dBm)

; More:

* Stereo line level inputs and outputs

* Unbrickable design with integrated boot loader for safe code experimentation.
* Power and hold switch useful for "instant on" and key lockout to aid in media player applications on the go.
* Runs on the Linux Operating System (currently 3.2.x and 2.6.x)

== Box Contents ==

When you first open Pandora's box, a slew of demons and raging emotions may forcibly leave the box. This is normal. After that, you should find the following items:

* The Pandora console
* Stylus (located in stylus slot on the side of the Pandora)
* Battery
* Mains power adapter
* Battery Case

Available separately:

* TV-Out Cable
** As of 3rd November 2010 these are not yet included in the box and will ship separately as available.
* Carrying Case
* Extra Battery

== Safety Information ==

*The OpenPandora should not be used by Children under the age of 3 due to potential choking hazards.
*The OpenPandora's Battery should only be charged with supplied charger / Via USB or a suitable third party charger.
*The OpenPandora should only be used in temperatures above -10°C (14°F) and below 40°C (104°F).

== Warranty Information ==

Standard one year warranty applies to the OpenPandora.

* User Neglect / Modifications are generally not covered by warranty.

== First Time Use ==

Place the battery inside the battery compartment underneath the OpenPandora taking care to ensure the battery contacts and battery touch. Please the battery cover on and your OpenPandora will power up.

==== Charging ====

As this is your first time using the Battery it is recommended you fully charge your OpenPandora to 100% using the AC Adapter as this will calibrate and improve the lifetime of your battery. This process may take up to 4 hours. If you're not planning on using the OpenPandora whilst it is charging you should flip the power switch to the left (Low Power Mode) as it should decrease the charging time dramatically.

Once the OpenPandora has completed charging it will stop charging and begin discharging to protect the battery from damage.

You can find more useful information about charging on the [[power modes | Power Modes]] page.

==== First Boot ====

While you are charging your OpenPandora completing the first boot wizard is essential.

===== Steps Involved=====
*Calibrate Touchscreen - This will ensure that the TouchScreen works perfectly.
*Enter Full Name - This personalises your OpenPandora
*Enter Short name - can be a fancy nickname or just your fullname in all lowercase
*Enter Password - anything you like and you'll need to verify it
*Choose a name for your OpenPandora - Give it a fancy name as this will be the network visible name.
*Automatic Login - Entirely up to you. Preferable off if you don't want others to use your OpenPandora without your permission
*GUI choice - Slimmed down basic GUI - Minimenu or full Linux OS - xFCE
*TimeZone / Date and Time - Recommended you do set this correctly as it may cause problems down the track with certain applications.
*CPU Clock Speed - Recommended that you set to Default unless a game / application is running slowly.
*Advanced settings - Do not change until you are comfortable with the device.

====Analog Nubs [http://pandorawiki.org/Nubs]====

The OpenPandora nubs are designed to automatically calibrate when you turn your Pandora & Calibration is lost once the OpenPandora is switched off.

==== Calibrating the Touchscreen ====

The touchscreen in the OpenPandora may / may not be calibrated when you first get it. It is recommended you do run the Calibration Wizard in the first boot wizard alternatively if you clicked too fast you can run the calibration wizard by going to the Settings / Calibrate Touch Screen section in either GUIs

== Basic Use ==
See the [[GUI]] page for more details on the user interfaces which can be used with the Pandora.

===Mini Menu===

[[minimenu | Mini Menu]] is a quick and easy to use launcher created by OpenPandora's great friend Skeezix. Mini Menu is designed to be capable of fully customised skins.

===== Basic Navigation =====

The main grid of Mini Menu displays the available applications, category tabs, Date / Time, Battery life and a detail pane on the right.

When you copy a PND to SDCARDNAME/pandora/apps it will appear in its preset category.

Controls for Mini Menu:
* D-Pad or touch screen can be used to select PNDs
* Launch a PND by pressing 'Start', 'B' or touching the icon with the stylus or finger.
* Press 'Y' for documentation if there is any available.
* Left and Right shoulder triggers switch categories

=====Skinning=====

Skinning guide in gp32x forum: http://www.gp32x.com/board/index.php?/topic/53990-skinning-minimenu/

A mmskin.conf from February 2011: http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=minimenu/skin/default/mmskin.conf;h=695888b3ae310d7ea04b4e682baed0c0c6fc4349;hb=98c1d081629ac9cbb3056b39097a3db968ce4055 (Skinning will not work without it)

===Desktop style environment (Xfce)===

=====On the Desktop=====

The desktop contains icons which have been found on SD Cards / in Firmware.

=====Pandora Menu & Task Bar=====
On the bottom left the Pandora menu contains all your applications sorted into the appropriate categories.

The task bar by default contains settings for Brightness, Sound, various enablers such as Wifi / Bluetooth, Network Connectivity, Battery life, Date / Time and various workspaces you can select.

=====Navigation=====
*If a window for an application is too big for the screen you can drag the window around by holding the left trigger and dragging with the stylus.
*Changing your workspace is as easy as holding 'Start' & "Select' then using the D-Pad to switch
*Killing an application is as simple as holding the Pandora button down for 5 seconds, selecting the application and clicking okay

===Power modes===

Pushing the power button to the left will turn the OpenPandora to low power mode for conserving battery which is similar to sleep mode on a computer but the Pandora can still run.

The [[Power modes]] page provides more information.

=== USB Peripherals ===

Connecting USB2 High Speed devices is possible using the standard USB connector or USB On The Go adapter. USB 1.1 devices will only work through a USB hub.
See the [[USB_compatibility_list| USB compatibility list]] for more information

=== Forcing a Restart ===
Occasionally something will happen causing your Pandora to become unresponsive (to the point that even killing a program isn't possible). When this happens it is necessary to force your Pandora to restart. The easiest way to do this is by holding the Pandora button and moving the power switch to the right.

== Firmware ==

==== Updating The Firmware ====

Updating the Firmware can be done via either full Reflash or the Upgrade Pandora OS Application which is found in the System Menu.

==== Reinstalling the Firmware ====

Sometimes things don't work out or you've broken something in the OS. You can reflash the firmware to default by getting the latest package from the [http://boards.openpandora.org/index.php/forum/41-pandora-os-superzaxxon-gnulinux/ forum] and placing in the root of the SD Card then while booting the Pandora hold down the R Button. Reinstalling the OS can take up to 15 minutes

== Applications ==

There's quite a large amount of Applications available for the OpenPandora and there's several distribution points as mentioned below

*[http://repo.openpandora.org OpenPandora Repo] - Has over 1000 applications which are either free or at a very low cost. Applications do not contain DRM.
*[http://dl.openhandshelds.org/cgi-bin/pandora.cgi Open HandHelds] - An older site which may not have the latest applications but you'll find a heap of applications that are archive worthy.
*Angstrom Repository - Contains several applications for your Pandora. It is not really recommended that you use this unless you are an advanced user.
*[http://repo.openpandora.org/?page=detail&app=pndmanager-bzar PND Manager] - A very useful application which syncs with the Repo and allows you to download / install Applications easily.

Installing Applications is as simple as dragging them to the appropriate folders on your SD Card.
These folders are:
* <SD>/pandora/apps - Will appear both on xFCE Desktop & Pandora Menu (this is the 'both' option in PNDManager)
*<SD>/pandora/desktop/ - If you want it to appear on xFCE Desktop
*<SD>/pandora/menu/ - If you want it to appear in Pandora Menu

Some applications will require additional data to work, this data will need to go into:
*<SD>/pandora/appdata/applicationname

The application should generate the required appdata folder when launched.

==Futher reading==
* [[Basic Linux Guide]] - For those who don't know very much about Linux and want to learn more.
* [[Minimenu Configuration Documentation]] - If you want to customize or configure Minimenu.
* [[Games]] - Take a look at the games that are available.
* [[Software projects]] - A list of all non-emulator, non-game software for Pandora.

[[Category:Documentation]]

Nubs

2013-09-14T02:53:28Z

Levi: /* Nub Disassembly */ Still fixing gp32x links

The Pandora has 2 analogue controllers 'nubs', which were custom designed.

== Nub Calibration ==
[[Image:Nub_back.jpg|thumb|Backside]]
The nubs need time to calibrate at startup. Often this can be achieved by moving the nubs around once the Pandora has fully loaded (moving them while the OS is still loading may cause a calibration error). Re-calibration of the nubs can be achieved via 'Pandora Menu -> Settings -> Nubs', and selecting either configure <nub> or 'Restore default settings for both nubs'

===Nub Dance===
The 'Nub Dance' or 'Magic Nub Dance' is a technique used to calibrate the Pandora's nubs by exercising the nubs to their hardware limits.

Some of the older nubs required this calibration technique periodically, however newer nubs (since 2011) do not need as much calibration as the older ones.
Push them up, down, left, right to the edge, then let go of them so they spring back by themselves.
i.e. push up, as far as it will go, then let go (it must spring back). Do that for each direction. Then do some circles.
That should set them up. If you don't do this they can go wrong during that session until reset.[http://www.gp32x.com/board/index.php?/topic/54445-please-fix-the-right-anolog-nub-functions/page__view__findpost__p__876651]

===Nub firmware===
The proprietary algorithm for calibrating the nubs is contained within 8KB of flash ROM. More information [http://www.gp32x.com/board/index.php?/topic/53939-the-real-pandora-niche/page-3#entry865928 here].

===Using compressed air to remove dirt===
If you feel that you might be getting some nub problems caused by dirt having gotten inside, you can try blasting compressed air into the niche where the nubs meet the case. [http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/#entry868440] [http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page-9#entry871405][http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page-10#entry872373][http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page-12#entry872896]

==Nub Configuration==
(As of Zaxxon HF5) 
Nubs can be configured in software under Settings -> Nubs in the Xfce 4 menu system and can also be managed through the filesystem in the /proc/pandora/(nub0/nub1 for left and right nubs respectively).
Most files in that folder (mbutton_threshold, mouse_sensitivity, scroll_rate, scrollx_sensitivity, and scrolly_sensitivity) are fairly straightforward, containing a number determining the value of the attribute.

The only different field is in mode, which contains a string to determine how each nub behaves-

<pre>
mouse - The nub is treated as a mouse, the default configuration of the left nub.
mbuttons - The nub is used as the buttons of the mouse, the default configuration of the right nub.
scroll - The nub scrolls the screen vertically/horizontally as a pair of scroll wheels would.
absolute - The nub is treated as a joystick for the purposes of gaming.
mbscroll* - A combination of mbuttons and scroll. Up/down for scrolling up/down, left/right for according mouse buttons.
</pre>

<nowiki>*</nowiki>'''Note''': As of 2013-01-01 '''mbscroll''' is only available in an experimental kernel image. [http://boards.openpandora.org/index.php/topic/11295-idea-combined-nub-mode-2-mouse-buttons-scrolling-on-1-axis/ Concept] by porg, realization by urjaman ([http://boards.openpandora.org/index.php/topic/11295-idea-combined-nub-mode-2-mouse-buttons-scrolling-on-1-axis/?p=210868 download & instructions], [http://boards.openpandora.org/index.php/topic/11295-idea-combined-nub-mode-2-mouse-buttons-scrolling-on-1-axis/?p=210844 source code]).

The easiest way to alter a nub's mode in the console is to use the following code-
<source lang=bash>
echo "(mode)" > /proc/pandora/nubx/mode
</source>
Where (mode) is one of the above modes and the x in nubx is 0 or 1.

For example, if we wanted to set the left nub to scroll, we'd use
<source lang=bash>
echo "scroll" > /proc/pandora/nub0/mode
</source>
All information pulled from [http://www.pandorawiki.org/PND_nub_modes] and may be subject to change due to updates.

== Nub Disassembly ==
{{warning|This is a fairly tricky process, and will almost certainly '''void your warranty.'''}}

You need[http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page__view__findpost__p__874378]:
* High quality soldering iron
* Solder Wick
* Shim Blade (Edsyn RB641)
* Isopropyl Alcohol cleaner
* Size 0.00 cross-head screwdriver

Removing the nubs from the PCB is difficult. They are mounted using cut-off plated through holes butted onto pads (fairly standard SMT technology). Just using solder wick will not be sufficient, and if you are not extremely careful, you will rip the pads off the nub or the board.

[[Image:Nub_inside.jpg|thumb|shows the under side of the nub, which has a small PCB screwed on, and 2 locating pins]]

Full sized versions of these photos can be found [http://www.flickr.com/photos/tsh2/4707661640/ here]. Original pics from [http://picasaweb.google.com/claude.schwarz/DropBox?authkey=Gv1sRgCN7KsICXu-KTzwE&feat=directlink Claude], discussion [http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page-13#entry874378 here].

Top left is the micro-joystick which serves as both a spring and the sensing element. when re-assembling this must fit perfectly into the plastic, and be perfectly clean.

==More info on how the nubs work==
Some words from MWeston [http://boards.openpandora.org/index.php?/topic/2270-nubs-feel-weird/page__view__findpost__p__40328 here]: "The nubs were designed to work when thumb pressure is applied. They will not work right if you try to slide them with your finger tip or finger nail or anything like that."

== Early Nub Problems ==
[[Image:Faultynub.jpg | thumb | One example of a faulty nub.]]
The nubs on some of the first units suffered from a myriad of issues. The issues include bad traces, bad resistance in the joystick, looseness, grittiness, nubs not centering, and nubs sticking in one direction.[http://www.openpandora.org/index.php?option=com_content&view=category&layout=blog&id=2&Itemid=2&lang=en] Much of this was caused by the nub manufacturer not having strict enough tolerances[http://www.gp32x.com/board/index.php?/topic/54824-production-status/page__p__883494&#entry883494] and not 'bare board' testing the PCBs used in the manufacture. Probably the most serious problem is that the nubs can break mechanically, resulting in a nub which cannot centre itself. This causes drifting while in-game, rendering the nub completely unusable.

Because of these problems, a few "one nub" units were made available to people who wished to accept one and skip the queue. The faulty nub is not covered under warranty for these units. Reports[http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/] suggest that many of these were reasonably functional, and problems relate to either the calibration process or dirt inside the nub. There is a risk that these nubs might fail with extended use. Soon after the first units were shipped, 100% testing was arranged for the nubs by the supplier and OpenPandora Ltd. (This applies to units shipped after July 27,2010 which are expected to all start with known good nubs)

== Configuring nubs ==
Controls available through /proc/pandora/nub{0,1}/ , see [[Nubs|dedicated page]].
=== reset ===
The nubs can be reset to restart their calibration process by writing 1, then 0 to:
<source lang="bash">
/sys/bus/i2c/devices/3-0066/reset
</source>
It is not recommended to keep them in reset state (write 1 and no 0), this will use more power.
=== config ===
Kept in /etc/pandora/conf/nubs.state, GUI tool available in firmware.

[[Category:Hardware defects]]
[[Category:Keyboard]]
[[Category:Tutorials]]

Nubs

2013-09-14T02:31:34Z

Levi: /* Using compressed air to remove dirt */ ...and again

The Pandora has 2 analogue controllers 'nubs', which were custom designed.

== Nub Calibration ==
[[Image:Nub_back.jpg|thumb|Backside]]
The nubs need time to calibrate at startup. Often this can be achieved by moving the nubs around once the Pandora has fully loaded (moving them while the OS is still loading may cause a calibration error). Re-calibration of the nubs can be achieved via 'Pandora Menu -> Settings -> Nubs', and selecting either configure <nub> or 'Restore default settings for both nubs'

===Nub Dance===
The 'Nub Dance' or 'Magic Nub Dance' is a technique used to calibrate the Pandora's nubs by exercising the nubs to their hardware limits.

Some of the older nubs required this calibration technique periodically, however newer nubs (since 2011) do not need as much calibration as the older ones.
Push them up, down, left, right to the edge, then let go of them so they spring back by themselves.
i.e. push up, as far as it will go, then let go (it must spring back). Do that for each direction. Then do some circles.
That should set them up. If you don't do this they can go wrong during that session until reset.[http://www.gp32x.com/board/index.php?/topic/54445-please-fix-the-right-anolog-nub-functions/page__view__findpost__p__876651]

===Nub firmware===
The proprietary algorithm for calibrating the nubs is contained within 8KB of flash ROM. More information [http://www.gp32x.com/board/index.php?/topic/53939-the-real-pandora-niche/page-3#entry865928 here].

===Using compressed air to remove dirt===
If you feel that you might be getting some nub problems caused by dirt having gotten inside, you can try blasting compressed air into the niche where the nubs meet the case. [http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/#entry868440] [http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page-9#entry871405][http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page-10#entry872373][http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page-12#entry872896]

==Nub Configuration==
(As of Zaxxon HF5) 
Nubs can be configured in software under Settings -> Nubs in the Xfce 4 menu system and can also be managed through the filesystem in the /proc/pandora/(nub0/nub1 for left and right nubs respectively).
Most files in that folder (mbutton_threshold, mouse_sensitivity, scroll_rate, scrollx_sensitivity, and scrolly_sensitivity) are fairly straightforward, containing a number determining the value of the attribute.

The only different field is in mode, which contains a string to determine how each nub behaves-

<pre>
mouse - The nub is treated as a mouse, the default configuration of the left nub.
mbuttons - The nub is used as the buttons of the mouse, the default configuration of the right nub.
scroll - The nub scrolls the screen vertically/horizontally as a pair of scroll wheels would.
absolute - The nub is treated as a joystick for the purposes of gaming.
mbscroll* - A combination of mbuttons and scroll. Up/down for scrolling up/down, left/right for according mouse buttons.
</pre>

<nowiki>*</nowiki>'''Note''': As of 2013-01-01 '''mbscroll''' is only available in an experimental kernel image. [http://boards.openpandora.org/index.php/topic/11295-idea-combined-nub-mode-2-mouse-buttons-scrolling-on-1-axis/ Concept] by porg, realization by urjaman ([http://boards.openpandora.org/index.php/topic/11295-idea-combined-nub-mode-2-mouse-buttons-scrolling-on-1-axis/?p=210868 download & instructions], [http://boards.openpandora.org/index.php/topic/11295-idea-combined-nub-mode-2-mouse-buttons-scrolling-on-1-axis/?p=210844 source code]).

The easiest way to alter a nub's mode in the console is to use the following code-
<source lang=bash>
echo "(mode)" > /proc/pandora/nubx/mode
</source>
Where (mode) is one of the above modes and the x in nubx is 0 or 1.

For example, if we wanted to set the left nub to scroll, we'd use
<source lang=bash>
echo "scroll" > /proc/pandora/nub0/mode
</source>
All information pulled from [http://www.pandorawiki.org/PND_nub_modes] and may be subject to change due to updates.

== Nub Disassembly ==
{{warning|This is a fairly tricky process, and will almost certainly '''void your warranty.'''}}

You need[http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page__view__findpost__p__874378]:
* High quality soldering iron
* Solder Wick
* Shim Blade (Edsyn RB641)
* Isopropyl Alcohol cleaner
* Size 0.00 cross-head screwdriver

Removing the nubs from the PCB is difficult. They are mounted using cut-off plated through holes butted onto pads (fairly standard SMT technology). Just using solder wick will not be sufficient, and if you are not extremely careful, you will rip the pads off the nub or the board.

[[Image:Nub_inside.jpg|thumb|shows the under side of the nub, which has a small PCB screwed on, and 2 locating pins]]

Full sized versions of these photos can be found [http://www.flickr.com/photos/tsh2/4707661640/ here]. Original pics from [http://picasaweb.google.com/claude.schwarz/DropBox?authkey=Gv1sRgCN7KsICXu-KTzwE&feat=directlink Claude], discussion http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page__view__findpost__p__874378 here].

Top left is the micro-joystick which serves as both a spring and the sensing element. when re-assembling this must fit perfectly into the plastic, and be perfectly clean.

==More info on how the nubs work==
Some words from MWeston [http://boards.openpandora.org/index.php?/topic/2270-nubs-feel-weird/page__view__findpost__p__40328 here]: "The nubs were designed to work when thumb pressure is applied. They will not work right if you try to slide them with your finger tip or finger nail or anything like that."

== Early Nub Problems ==
[[Image:Faultynub.jpg | thumb | One example of a faulty nub.]]
The nubs on some of the first units suffered from a myriad of issues. The issues include bad traces, bad resistance in the joystick, looseness, grittiness, nubs not centering, and nubs sticking in one direction.[http://www.openpandora.org/index.php?option=com_content&view=category&layout=blog&id=2&Itemid=2&lang=en] Much of this was caused by the nub manufacturer not having strict enough tolerances[http://www.gp32x.com/board/index.php?/topic/54824-production-status/page__p__883494&#entry883494] and not 'bare board' testing the PCBs used in the manufacture. Probably the most serious problem is that the nubs can break mechanically, resulting in a nub which cannot centre itself. This causes drifting while in-game, rendering the nub completely unusable.

Because of these problems, a few "one nub" units were made available to people who wished to accept one and skip the queue. The faulty nub is not covered under warranty for these units. Reports[http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/] suggest that many of these were reasonably functional, and problems relate to either the calibration process or dirt inside the nub. There is a risk that these nubs might fail with extended use. Soon after the first units were shipped, 100% testing was arranged for the nubs by the supplier and OpenPandora Ltd. (This applies to units shipped after July 27,2010 which are expected to all start with known good nubs)

== Configuring nubs ==
Controls available through /proc/pandora/nub{0,1}/ , see [[Nubs|dedicated page]].
=== reset ===
The nubs can be reset to restart their calibration process by writing 1, then 0 to:
<source lang="bash">
/sys/bus/i2c/devices/3-0066/reset
</source>
It is not recommended to keep them in reset state (write 1 and no 0), this will use more power.
=== config ===
Kept in /etc/pandora/conf/nubs.state, GUI tool available in firmware.

[[Category:Hardware defects]]
[[Category:Keyboard]]
[[Category:Tutorials]]

Nubs

2013-09-14T02:19:37Z

Levi: /* Nub firmware */ Seems gp32x deep linking URI spec has changed

The Pandora has 2 analogue controllers 'nubs', which were custom designed.

== Nub Calibration ==
[[Image:Nub_back.jpg|thumb|Backside]]
The nubs need time to calibrate at startup. Often this can be achieved by moving the nubs around once the Pandora has fully loaded (moving them while the OS is still loading may cause a calibration error). Re-calibration of the nubs can be achieved via 'Pandora Menu -> Settings -> Nubs', and selecting either configure <nub> or 'Restore default settings for both nubs'

===Nub Dance===
The 'Nub Dance' or 'Magic Nub Dance' is a technique used to calibrate the Pandora's nubs by exercising the nubs to their hardware limits.

Some of the older nubs required this calibration technique periodically, however newer nubs (since 2011) do not need as much calibration as the older ones.
Push them up, down, left, right to the edge, then let go of them so they spring back by themselves.
i.e. push up, as far as it will go, then let go (it must spring back). Do that for each direction. Then do some circles.
That should set them up. If you don't do this they can go wrong during that session until reset.[http://www.gp32x.com/board/index.php?/topic/54445-please-fix-the-right-anolog-nub-functions/page__view__findpost__p__876651]

===Nub firmware===
The proprietary algorithm for calibrating the nubs is contained within 8KB of flash ROM. More information [http://www.gp32x.com/board/index.php?/topic/53939-the-real-pandora-niche/page-3#entry865928 here].

===Using compressed air to remove dirt===
If you feel that you might be getting some nub problems caused by dirt having gotten inside, you can try blasting compressed air into the niche where the nubs meet the case. [http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page__view__findpost__p__868440] [http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page__view__findpost__p__871405][http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page__view__findpost__p__872373][http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page__view__findpost__p__872896]

==Nub Configuration==
(As of Zaxxon HF5) 
Nubs can be configured in software under Settings -> Nubs in the Xfce 4 menu system and can also be managed through the filesystem in the /proc/pandora/(nub0/nub1 for left and right nubs respectively).
Most files in that folder (mbutton_threshold, mouse_sensitivity, scroll_rate, scrollx_sensitivity, and scrolly_sensitivity) are fairly straightforward, containing a number determining the value of the attribute.

The only different field is in mode, which contains a string to determine how each nub behaves-

<pre>
mouse - The nub is treated as a mouse, the default configuration of the left nub.
mbuttons - The nub is used as the buttons of the mouse, the default configuration of the right nub.
scroll - The nub scrolls the screen vertically/horizontally as a pair of scroll wheels would.
absolute - The nub is treated as a joystick for the purposes of gaming.
mbscroll* - A combination of mbuttons and scroll. Up/down for scrolling up/down, left/right for according mouse buttons.
</pre>

<nowiki>*</nowiki>'''Note''': As of 2013-01-01 '''mbscroll''' is only available in an experimental kernel image. [http://boards.openpandora.org/index.php/topic/11295-idea-combined-nub-mode-2-mouse-buttons-scrolling-on-1-axis/ Concept] by porg, realization by urjaman ([http://boards.openpandora.org/index.php/topic/11295-idea-combined-nub-mode-2-mouse-buttons-scrolling-on-1-axis/?p=210868 download & instructions], [http://boards.openpandora.org/index.php/topic/11295-idea-combined-nub-mode-2-mouse-buttons-scrolling-on-1-axis/?p=210844 source code]).

The easiest way to alter a nub's mode in the console is to use the following code-
<source lang=bash>
echo "(mode)" > /proc/pandora/nubx/mode
</source>
Where (mode) is one of the above modes and the x in nubx is 0 or 1.

For example, if we wanted to set the left nub to scroll, we'd use
<source lang=bash>
echo "scroll" > /proc/pandora/nub0/mode
</source>
All information pulled from [http://www.pandorawiki.org/PND_nub_modes] and may be subject to change due to updates.

== Nub Disassembly ==
{{warning|This is a fairly tricky process, and will almost certainly '''void your warranty.'''}}

You need[http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page__view__findpost__p__874378]:
* High quality soldering iron
* Solder Wick
* Shim Blade (Edsyn RB641)
* Isopropyl Alcohol cleaner
* Size 0.00 cross-head screwdriver

Removing the nubs from the PCB is difficult. They are mounted using cut-off plated through holes butted onto pads (fairly standard SMT technology). Just using solder wick will not be sufficient, and if you are not extremely careful, you will rip the pads off the nub or the board.

[[Image:Nub_inside.jpg|thumb|shows the under side of the nub, which has a small PCB screwed on, and 2 locating pins]]

Full sized versions of these photos can be found [http://www.flickr.com/photos/tsh2/4707661640/ here]. Original pics from [http://picasaweb.google.com/claude.schwarz/DropBox?authkey=Gv1sRgCN7KsICXu-KTzwE&feat=directlink Claude], discussion http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/page__view__findpost__p__874378 here].

Top left is the micro-joystick which serves as both a spring and the sensing element. when re-assembling this must fit perfectly into the plastic, and be perfectly clean.

==More info on how the nubs work==
Some words from MWeston [http://boards.openpandora.org/index.php?/topic/2270-nubs-feel-weird/page__view__findpost__p__40328 here]: "The nubs were designed to work when thumb pressure is applied. They will not work right if you try to slide them with your finger tip or finger nail or anything like that."

== Early Nub Problems ==
[[Image:Faultynub.jpg | thumb | One example of a faulty nub.]]
The nubs on some of the first units suffered from a myriad of issues. The issues include bad traces, bad resistance in the joystick, looseness, grittiness, nubs not centering, and nubs sticking in one direction.[http://www.openpandora.org/index.php?option=com_content&view=category&layout=blog&id=2&Itemid=2&lang=en] Much of this was caused by the nub manufacturer not having strict enough tolerances[http://www.gp32x.com/board/index.php?/topic/54824-production-status/page__p__883494&#entry883494] and not 'bare board' testing the PCBs used in the manufacture. Probably the most serious problem is that the nubs can break mechanically, resulting in a nub which cannot centre itself. This causes drifting while in-game, rendering the nub completely unusable.

Because of these problems, a few "one nub" units were made available to people who wished to accept one and skip the queue. The faulty nub is not covered under warranty for these units. Reports[http://www.gp32x.com/board/index.php?/topic/54073-the-one-nub-club/] suggest that many of these were reasonably functional, and problems relate to either the calibration process or dirt inside the nub. There is a risk that these nubs might fail with extended use. Soon after the first units were shipped, 100% testing was arranged for the nubs by the supplier and OpenPandora Ltd. (This applies to units shipped after July 27,2010 which are expected to all start with known good nubs)

== Configuring nubs ==
Controls available through /proc/pandora/nub{0,1}/ , see [[Nubs|dedicated page]].
=== reset ===
The nubs can be reset to restart their calibration process by writing 1, then 0 to:
<source lang="bash">
/sys/bus/i2c/devices/3-0066/reset
</source>
It is not recommended to keep them in reset state (write 1 and no 0), this will use more power.
=== config ===
Kept in /etc/pandora/conf/nubs.state, GUI tool available in firmware.

[[Category:Hardware defects]]
[[Category:Keyboard]]
[[Category:Tutorials]]

DraStic Compatibility List

2013-09-10T00:41:10Z

Levi: /* Adding to the list */ Adding link

DraStic is a Nintendo DS Emulator created by Exophase for ARM devices such as the OpenPandora.

* [http://repo.openpandora.org/?page=detail&app=DraStic Download]
* [http://exophase.devzero.co.uk/drastic_readme.txt Readme and Changelog]
* [http://boards.openpandora.org/index.php/topic/12038-emulator-drastic-nintendo-ds/page-1 Forum Thread]

The current version on the Repo is 2.1.0.0 beta, released on August 5th, 2013. It identifies itself as "Version r2.1.0p" on the menu screen.

* [http://pandorawiki.org/DraStic_Compatibility_List_1.x Outdated Previous 1.x Version Compatibility List]

==Compatibility==
''128MB+ zipped games have issues on CC Pandoras because of limited RAM. 256MB zipped games may work on 512MB systems such as the Rebirth or 1GHz Pandora. 512MB zipped games are not expected to run on any system. Unzipped games of any size are not dependent on RAM, so should work the same on all systems.　Note that wifi is not emulated or faked so far, so it may lead to compatibility issues/crashes.''

==Adding to the list==
Note: you can use the [http://repo.openpandora.org/?page=detail&app=drasticwikihelper-PowerGod Drastic Wiki Helper] application from the repo to automatically generate appropriate text to paste in the compatibility list below.

Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. Include the unzipped ROM size in base-2 mebibytes (16MB, 64MB, 128MB, etc.). If available please indicate the game ID figure, too. The Game ID figure should be 8 characters long and can usually be found by pressing Y on the rom selection menu.

'''Don't''' post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new DraStic version, update the entry and add that to notes. Please don't copy entries from the old list into this one unless you first re-test the game using a recent version of DraStic and update the color and notes as required.

Default frameskip for version 2.0.1p is automatic and 4. Please record a comment if you use a different setting.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by Exophase about further debugging your problems.

==The Compatibility List==


You can sort the colums by clicking the table header.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game ID
! Game Name
! DraStic Version
! ROM Size
! Pandora Model[1]

! Frequency
! Notes
! Status

|- style="background: #90FF90"
|454d5341
|Super Mario 64 DS
|r2.1.0p
|16MiB
|1GHz
|900MHz
|Minimal graphical tears; almost none; other than that seems to plays perfectly. :(knightron)
|Green

|- style="background: #90FF90"
|454c4759
|Geometry Wars - Galaxies
|r2.1.3p
|Geometry Wars - GalaxiesMiB
|1Ghz
|1000Mhz
|Works very well. (ekianjo)
| Green

|- style="background: #F3F781"
|55595241
|Rayman DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Very choppy sound often, and frameskip choppyness too. :(knightron)
|Yellow

|- style="background: #90FF90"
|50445441
|42 All Time Classics/Clubhouse Games (E)
|r2.1.0p
|16MiB
|1GHz
|900MHz
|Plays fine with frameskip 2
|Green

|- style="background: #90FF90"
|45575941
|Yoshis Island DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45474443
|Disgaea DS (U)
|r2.1.3p
|Disgaea DSMiB
|1Ghz
|1000Mhz
|runs very well overall. No issue detected. (ekianjo)
| Green

|- style="background: #F3F781"
|50425341
|Snowboard Kids
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Runs at full speed but has constant choppy sound during races. :(Knightron)
|Yellow

|- style="background: #90FF90"
|45455341
|Children of Mana
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45555159
|Chrono Trigger
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Seems to run perfect. I did not play long enough to test cut scenes. :(Knightron)
|Green

|- style="background: #90FF90"
|45445741
|Diddy Kong Racing DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|A couple of graphical bugs in a few places, but seems close to perfect. :(Knightron)
|Green

|- style="background: #90FF90"
|4a554a41
|Jump Ultimate Stars (English patched)
|r2.1.0p
|62.9MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F3F781"
|45475049
|Pokemon SoulSilver
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Slight graphical tearing. Lags a little when entering buildings ect. Other than that, it seems very playable. :(Knightron)
|Yellow

|- style="background: #90FF90"
|45484d41
|Metroid Prime Hunters
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems close to perfect. Full speed most of the time, but when lots of enemies are fireing at you, it slows down a little. May encounter bigger issues further into the game. :(Knightron)
|Green

|- style="background: #90FF90"
|45524341
|Sprung The Dating Game
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F7BE81"
|454a4c43
|Mario and Luigi Bowsers Inside Story
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays pretty close to perfect, but freezes during the first fight, while playing as Bowser. :(knightron)
|Orange

|- style="background: #90FF90"
|45355659
|Dragon Quest V Hand of the Heavenly Bride
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Seems to play close to perfectly, very slight choppy inconsistancy between two screens, but not as bad as DQIV. :(Knightron)
|Green

|- style="background: #90FF90"
|45425742
|Plants vs Zombies
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|454b5441
|Kirby Canvas Curse
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|4a534259
|Soma Bringer (English patched)
|r2.1.0p
|122MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45564959
|Dragon Quest IV Chapters of the Chosen
|r2.1.0p
|128MiB
|1GHz
|900MHz
|It can apear a little choppy when playing with vertical screens, but still plays very well: I switch it to one screen mode. :(Knightron)
|Green

|- style="background: #90FF90"
|45464641
|Final Fantasy III
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays pretty damn close to perfect. :(Knightron)
|Green

|- style="background: #F3F781"
|45344659
|Final Fantasy IV
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays at full speed, but has choppy sound quite often. :(Knightron)
|Yellow

|- style="background: #F7BE81"
|4a545941
|Tales Of Innocence (English Patched)
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays at full speed, but there are major graphical issues that make the game very hard to follow. :(Knightron)
|Orange

|- style="background: #90FF90"
|454b5341
|Lost in Blue
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Plays almost perfectly, just a few very minor graphical and sound bugs in a few spots. Microphone fails sometimes but works again once Drastic is restarted. Game crashes occasionally when atempting to light the fire or build something. At the moment, I recommend regular saving through savestates just in case. :(Knightron)
|Green

|- style="background: #F78181"
|45514459
|Dragon Quest IX Sentinels of the Starry Skies
|r2.1.0p
|22.3MiB
|1GHz
|900MHz
|Game crashes on boot. :(Knightron)
|Red

|- style="background: #90FF90"
|454d5241
|Mario and Luigi Partners in Time
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45495941
|Yoshi Touch & Go
|r2.1.0p
|16MiB
|1GHz
|900MHz
|This Game Apears to play perfectly, but it has major problems when the Pandora is put to sleep. :(Knightron)
|Green

|- style="background: #90FF90"
|454b5342
|9 Hours, 9 Persons, 9 Doors
|r2.0.1p
|128MiB
|Rebirth
|850
|Plays at full speed.
|Green

|- style="background: #90FF90"
|45574b59
|Kirby - Super Star Ultra
|r2.0.1p
|128MiB
|CC
|800
|Plays at full speed.
|Green

|- style="background: #F3F781"
|45563241
|M&M's - Break 'Em
|r2.0.1p
|8MiB
|CC
|800
|Plays at too slow to be enjoyed.
|Yellow

|- style="background: #90FF90"
|45365359
|Civilization Revolution DS
|r2.0.1p
|64MiB
|Rebirth
|825MHz
|Fully playable. (Long firststart ~62sec.)
|Green

|- style="background: #90FF90"
|45365359
|Barnyard Blast: Swine of the Night
|r2.0.1p
|8MiB
|1GHz
|1.1GHz
|Works Completely fine. No Lag or Graphical Issues even on cut scenes
|Green

|- style="background: #90FF90"
|45454650
|Fire Emblem: Shadow Dragon (E)
|r2.1.3p
|64MiB
|1GHz
|900MHz
|Runs fine since r2.1.3p
|Green

|- style="background: #90FF90"
|4a564942
|Ivy the Kiwi (J)
|r2.1.3p
|8MiB
|1GHz
|900MHz
|Runs fine since r2.1.0p. Doesn't even need frameskip at 900Mhz.
|Green

|- style="background: #90FF90"
|50505841
|Picross DS (E)
|r2.1.3p
|32MiB
|1GHz
|600MHz
|Very minor graphical glitch where at end of level the top screen image transitions from monochrome to (animated) colour - one pixel line of monochrome image is left above the animated image.
|Green

|- style="background: #90FF90"
|50503643
|Picross 3D (E)
|r2.1.3p
|32MiB
|1GHz
|600MHz
|Absolutely perfect since version r2.1.0p
|Green

|- style="background: #F3F781"
|50344759
|Suikoden Tierkreis
|r2.0.1p
|256MiB
|Rebirth
|900MHz
|Sound sometimes a bit laggy during battle. (tested for 40min only)
|Yellow

|- style="background: #90FF90"
|45375341
|Summon Night, Twin Age
|r2.0.1p
|128MiB
|Rebirth
|900MHz
|nice. (tested for 10h)
|Green

|- style="background: #F3F781"
|404c5741
|The World Ends With You (E)
|r2.0.1p
|128MiB
|Rebirth
|900MHz
|Ran fine as far as the end of the first day. (not further tested.)
|Yellow

|- style="background: #90FF90"
|45434d41
|MarioKart DS (US)
|r2.1.3p
|32MiB
|1GHz
|1050MHz
|Runs fine with frameskip
|Green

|- style="background: #90FF90"
|45444e41
|Brain Age - Train Your Brain in Minutes a Day! (v01)
|r2.1.0p
|16MiB
|1Ghz
|800 Mhz
|Works great. (PowerGod)
|Green

|- style="background: #90FF90"
|50444e41
|Dr Kawashima's Brain Training - How Old Is Your Brain
|r2.1.0p
|16MiB
|1Ghz
|800 Mhz
|Works great. (PowerGod)
|Green

|- style="background: #F3F781"
|455a4443
|Dragon Ball - Origins
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|Playable with some lag. (PowerGod)
|Yellow

|- style="background: #90FF90"
|45503743
|Peggle Dual Shot
|r2.1.3p
|64MiB
|1Ghz
|750MHz
|Perfect play, fluid motion, just like the real thing. :(kumaki+levi)
|Green

|- style="background: #F3F781"
|45533241
|Dragon Ball Z - Supersonic Warriors 2
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|Playable with some lag. (PowerGod)
|Yellow

|- style="background: #F3F781"
|45414441
|Pokemon Diamond Version (v13)
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|No text in the introduction tutorial. Only played it a bit. (PowerGod)
(Edit by knightron: text is now played in DraStic 2.1.0p)
|Yellow

|- style="background: #90FF90"
|45433643
|Infinite Space
|r2.1.3p
|256MiB
|1Ghz
|1050Mhz
|Plays well. Graphical glitches in the attract mode. Played only as far as the first spaceport. (levi)
|Green
|}



==Notes==

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM
* Rebirth - OMAP3530 SoC @ 600MHz stock, **512MiB RAM**
* 1GHz - **DM3730 SoC @ 1GHz stock**, 512MiB RAM}}

[[Category:Emulators]]
[[Category: Compatibility]]
[[Category:List]]

Introduction to PNDs

2013-09-09T16:48:26Z

Levi: First attempt at merging this mess

{{IntroNote|For developers: [[Libpnd hub]]}}

{{merge|PND:FAQ}}

A [[.pnd]] ("pandora") file is an application (game, word processor, emulator, whatever.) More accurately, it is a full application bundled up into a single file; think of it like a zip, with a relatively well defined internal structure.

The pnd-file system was designed so you could use an application without the hassle of installation or uninstallation, or even having to organize it yourself if you don't want to. You just download or obtain the pnd-file, and use it.

If you remember classic computers such as the Amiga - where you inserted a disk and then launched the applications read by Workbench (the Amiga's operating system) - then this is similar: 
When you insert an SD card into one of the two slots, the (Linux-based) Pandora OS will scan it for your PND program files. Any program it finds will either turn up on the desktop or the application menu (just like in Windows).

== How do I run a PND-application? ==

Put your pnd-files on your SD card and insert the SD card into either slot of your Pandora.

Using the file browser, you can double-click on the pnd-file to run it. However, more normally pnd files are put in special folders so they get picked up by the Pandora's OS and are made easier to find and run.

== Where do .PNDs Go? ==
[[Image:PandoraSD.png|thumb|alt=SD card folder structure|This is what the folder structure on your SD card should look like. The drive letter and card name will vary; they're not important.]]
Put .pnd-files into specific directories if you want them to show up in the Start menu or on your Pandora desktop, or in Minimenu.

You can put them anywhere you like in internal NAND or SD, if you wish to organize them yourself and launch them with taps.

{|class="wikitable"
!Folder!!Note
|-
|/pandora/desktop||pnd files show up on the desktop background
|-
|/pandora/menu||show up in the Applications menu or in minimenu(under the categories suggested by the developer)
|-
|/pandora/apps||show up in all places; the desktop, the apps menu and in Minimenu
|-
|/pandora/mmenu||show up only in minimenu, ignored by other GUIs
|}

These locations are not written in stone. The [[libpnd]] config files are in /etc/pandora/conf in the [[NAND]]. Generally you will never need to alter these files, but you certainly can if you wish. In theory, obliterating the files will still leave the system working, and they are easily restored. One file, /etc/pandora/conf/desktop defines the "search paths" to look for .pnd files, and where to put ".desktop" files when they are found. The searchpaths says where to find them (such as /pandora/desktop), and where to put the application link - /usr/share/applications is where the menu items are pulled from. IF you wish to put pnd files somewhere not in the searchpath, just add the directory to the search-path and you're good to go.

NOTE: You can actually put subdirectories into those locations above, should you wish to organize your pnd-files somehow within those larger categories.

== Where DON'T .PND files go? ==

* .pnd files are looked for in the directories mentioned above; that list can be tailored if you wish to edit config files.
* .pnd files are not looked for in the / (root) of the SD cards.. this is _on purpose_; consider, if your SD card is 32GB, or if you're using a 2TB USB drive even -- it could have tens of thousands of files on it; having the Pandora scan the entire device for pnd files would take forever. Instead, we made a well defined set of directories the system will use - /pandora for everything, with 'appdata' and 'menu' and 'desktop' and other special purpose directories.

== Where does my data go? How do I make files visible to the applications? ==

An application normally will see what is contained within the pnd-file, or your personal data created with the tool; it can of course look anywhere on the SD or device internal memory. For example a Quake port might expect to see extra level files in /quake, or give you a way of selecting a path to put files in.. or it might just expect it to be in your personal data folders, or in the pnd-file itself. Its up to the application, with suggestions in the pnd-guidelines for developers.

The first time a pnd-application is run, an "app data" directory is created for it; anything that app data folder contains will be visible to the application as if it was in the pnd-file (and in fact, this lets you override files in the pnd-file without modifying the .pnd itself, which could be handy.) If your app creates a file "foo", it'll show up in '''/pandora/appdata/appname-id''' as "foo". The actual appdata folder name depends on the name used by the developer, but should generally look like application-name and some funny number afterwards. It should be easy to spot.

example: Quake 1 will probably put score or save data in /pandora/appdata/quake1-123/ or somesuch.

It will always be helpful to read the description or readme file included.

==== Example: Hatari ====

Hatari (Atari ST emulator) by default is set to look in "./disks" for the disk images (ROMs) to use. What this means is within the pnd-file (where no disks are supplied), and in the appdata directory. With Hatari, you can browse anywhere from the UI and pick a disk anywhere on your SD cards, but by default it'll look into the ./disks directory.

So you might put Hatari into the menu (/pandora/menu/Hatari131.pnd), or into the desktop (/pandora/desktop/Hatari131.pnd), or somewhere else. Regardless, the appdata will be (with the version I'm building now), /pandora/appdata/hatari.skeezix and thus you would put your .ST or .MSA disk images into /pandora/appdata/hatari.skeezix/disks to make them visible to the emulator. However, given it features its own UI, you can put them into /roms/atarist or /disks or whatever, and use them from there.

= Advanced topics =

== I want to override the .PND icon, name, or other settings, how is this done? ==

The easiest way right now is via the "override" (or "overlay") system -- [[.ovr]] files.

An [[.ovr]] is just a text file you create, with the same name as the pnd-file and in the same location, but with a different file extension. Piece of cake.

If your pnd-file is Hatari.pnd, and you're putting it into /pandora/desktop, then you might create an ovr file for it as: /pandora/desktop/Hatari.ovr
If you wish to provide your own icon, create it with the same location and filename, but as a .png file: /pandora/desktop/Hatari.png

.ovr files are automatically supported by the system so should work across all pnd-application aware applications and desktops. .png icon overrides have to be handled by the menus, but are already handled by minimenu and anything using the .desktop system (such as [[xfce]] full desktop or other standard desktop environments.)

An ovr-file simply looks like this:
* The ovr file may (at this time) override the icon title, the CPU clock speed to set on launch, the main category, and the first subcategory for the main category. Additional fields will become overridable.
* The category list uses the existing desktop standard. See [http://standards.freedesktop.org/menu-spec/latest/apa.html here] for a list of categories and subcategories supported.
* Minimenu honors up to 3 lines of 'notes', pulled from the .ovr file. (Make sure they are in the right subapp group). note-1, note-2, note-3, see example below. The notes in minimenu are shown at the bottom of the detail text panel.

<source lang="c">
[Application-0]
title HatariHack0
maincategory Audio
maincategorysub1 Emulator
[Application-1]
title HatariHack1
clockspeed 200
note-1 My text for note line 1
</source>

Notice the Application-0 and Application-1 -- any given .pnd file may include multiple applications, so you need to assign your overrides to the correct "sub application". It can be tricky to figure out which subapp you wish to override, but there are some tricks. minimenu, for example, shows the subapp-number in the detail panel. When looking at a .desktop filename, you'll notice #0.desktop .. some number after the # is the subapp-number.

== How Do I Make .PNDs? ==

{{IntroNote | The following is a work in progress, the instructions in here may or may not work for you. It was taken from PND quickstart.}}

The steps to produce a pnd file are as follows:

* create a directory to represent the application on SD card; i.e.: ./mame-app

* create a PXML.xml file and drop it into the dir (./mame-app/PXML.xml); genpxml script can be used, or do it by hand

* drop the executable and data files into this dir (say, ./mame-app/mame.bin, and ./mame-app/artwork/foo, etc.) <- note, with a PXML.xml and executable, your Pandora can now find and run your app without even bundling it into a .pnd!

* invoke /usr/pandora/scripts/pnd-make.sh (or on Windows, various commands in the command-line) to produce mame4all-pandora-1.0-arm.pnd or whatever you want to call it (foobearspanky.pnd, we don't care.)

* you're done, distribute it as you see fit

=== (alternate instructions) ===

For these instructions, you will first need to grab the example file, [http://www.shiranui.in/pndexample.tar.gz here].

* Edit ./pnds.sh. I use that script to handle multiple apps at once. Each line represents a command line for an app / game to turn the directory into a PND. If I change the app / game, I simply uncomment the line in pnds.sh so that I can easily create or update multiple PNDs by simply running one single script.
* Run ./pnds.sh
* Upload

Don't forget to check the license conditions for anything you re-distribute.

== PXML.xml file? ==

The PXML.xml file is the pnd file's metadata file and specifies things like:
* A description of the software
* A link to the icon filename
* What version it is
* The author, and their website
* Whether it's a beta or release version
* The menu categories the pnd file should appear in
* The license the code is distributed under
* Preview pictures, for display in minimenu or on the [[http://repo.openpandora.org/ repo]]

You can use genpxml.sh to generate a template PXML.xml file for you (in /usr/pandora/scripts/), but
perhaps simplest way to make your first PXML.xml file is to look at an example one from a real pnd file, from the repo (where PXML.xml file are guaranteed to be valid). The PXML.xml file will be inside the pnd file's root folder, and you can look at it using a text editor.

== How Do I Look Inside a .PND? ==

To open a PND, the easiest way is probably to use the [http://boards.openpandora.org/index.php?/topic/3756-pndtools/ PNDTools] or [http://boards.openpandora.org/index.php?/topic/3805-pnd-manager/ PNDManager] programs, which can browse and create PNDs. They're Windows-only, currently.

You could also install 7zip on your home PC, change the .pnd's file extension to .sfs, and 7zip should be able to open it. (This is a simple way to look into a .pnd on Ubuntu: <code>unsquashfs FILE.pnd</code> needs squashfs-tools installed) [http://boards.openpandora.org/index.php?/topic/3594-pnd-criticism/page__view__findpost__p__62546] On the Pandora, you can run a PND and look at what's inside [[Basic Linux Guide|/mnt/tmp]]. To do this in a terminal (on PC or Pandora), see [http://www.gp32x.com/board/index.php?/topic/58937-how-to-mount-a-pnd-and-see-the-gooey-bits-inside/ this tutorial].

The [[PND Cookbook]] contains recipes for common PND tasks, like setting up your application's environment and configuration, locating and copying files, etc.

== All these commands are hard. Give me a GUI tool to do it ==

Okay:

*'''PNDbuilder''' by freedomdown. [http://www.gp32x.com/board/index.php?/topic/58587-pndbuilder/ Discussion]. [http://www.freedomdown.ca/storage/pndb.pnd Download v1.1 for Pandora].

== How do I make .PNDs on Windows? ==

=== Command-line ===

For this command-line tutorial, I will assume you have already created a PXML.xml file.

==== Preparations ====
Get yourself mkisofs tools; for example, grab from here: http://www.student.tugraz.at/thomas.plank/ -- get cdrtools-2.01-win32-bin.zip and DLL version 1.5.25, and extract to somewhere. That lets you run 'mkisofs' to spit out .iso files

''If you want to make a compressed image, use squashfs tools here: ftp://ftp.slax.org/useful-binaries/win32/squashfs-tools/''

==== Generate the actual PND-file ====

Make yourself the iso; this step produces the iso, but to turn the iso into a pnd you need a couple last steps. You could also use some fancy iso-building tool.
<pre>mkisofs -o foo.iso -R /path/to/folder/myapp</pre>

Append PXML.xml to the .iso (yes, the PXML.xml is included in the iso, but we also want to append it for performance reasons.)
<pre>copy foo.iso+PXML.xml foo.step2</pre>

Append the icon PNG file to the .iso (if you have an icon; if not, you can leave this step out.)
<pre>copy foo.step2+myicon.png foo.pnd</pre>

Clean up:
<pre>del foo.step2 foo.iso</pre>

Profit!

=== GUI ===

You have a few choices here:
*'''PNDTools''' by foxblock. Discussion: [http://boards.openpandora.org/index.php?/topic/3756-pndtools/ OP], [http://www.gp32x.com/board/index.php?/topic/60060-pndtools/ GP32X]. Can browse and create PNDs. Two (simple and advanced) editors for PXML creation.
*'''PNDBuilder''' by StreaK. [http://www.gp32x.com/board/index.php?/topic/59862-openpandora-pnd-builder-for-windows-linux/ Discussion] [http://www.gp32x.com/board/index.php?/topic/47088-pnd-builder-for-windows/ (old)]. Can create PNDs and edit PXML files.
*'''PNDManager''' by Speaker Ender. [http://boards.openpandora.org/index.php?/topic/3805-pnd-manager/ Discussion].
*'''PNDbuilder''' by freedomdown. [http://www.gp32x.com/board/index.php?/topic/58587-pndbuilder/ Discussion].

== Mac OSX ==

TBD

[[Category:PND]]
[[Category:FAQ]]

DraStic Compatibility List

2013-09-08T23:17:26Z

Levi: /* The Compatibility List */ Infinite Space

DraStic is a Nintendo DS Emulator created by Exophase for ARM devices such as the OpenPandora.

* [http://repo.openpandora.org/?page=detail&app=DraStic Download]
* [http://exophase.devzero.co.uk/drastic_readme.txt Readme and Changelog]
* [http://boards.openpandora.org/index.php/topic/12038-emulator-drastic-nintendo-ds/page-1 Forum Thread]

The current version on the Repo is 2.1.0.0 beta, released on August 5th, 2013. It identifies itself as "Version r2.1.0p" on the menu screen.

* [http://pandorawiki.org/DraStic_Compatibility_List_1.x Outdated Previous 1.x Version Compatibility List]

==Compatibility==
''128MB+ zipped games have issues on CC Pandoras because of limited RAM. 256MB zipped games may work on 512MB systems such as the Rebirth or 1GHz Pandora. 512MB zipped games are not expected to run on any system. Unzipped games of any size are not dependent on RAM, so should work the same on all systems.　Note that wifi is not emulated or faked so far, so it may lead to compatibility issues/crashes.''

==Adding to the list==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. Include the unzipped ROM size in base-2 mebibytes (16MB, 64MB, 128MB, etc.). If available please indicate the game ID figure, too. The Game ID figure should be 8 characters long and can usually be found by pressing Y on the rom selection menu.

'''Don't''' post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new DraStic version, update the entry and add that to notes. Please don't copy entries from the old list into this one unless you first re-test the game using a recent version of DraStic and update the color and notes as required.

Default frameskip for version 2.0.1p is automatic and 4. Please record a comment if you use a different setting.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by Exophase about further debugging your problems.

==The Compatibility List==


You can sort the colums by clicking the table header.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game ID
! Game Name
! DraStic Version
! ROM Size
! Pandora Model[1]

! Frequency
! Notes
! Status

|- style="background: #90FF90"
|454d5341
|Super Mario 64 DS
|r2.1.0p
|16MiB
|1GHz
|900MHz
|Minimal graphical tears; almost none; other than that seems to plays perfectly. :(knightron)
|Green

|- style="background: #F3F781"
|55595241
|Rayman DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Very choppy sound often, and frameskip choppyness too. :(knightron)
|Yellow

|- style="background: #90FF90"
|50445441
|42 All Time Classics/Clubhouse Games (E)
|r2.1.0p
|16MiB
|1GHz
|900MHz
|Plays fine with frameskip 2
|Green

|- style="background: #90FF90"
|45575941
|Yoshis Island DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F3F781"
|50425341
|Snowboard Kids
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Runs at full speed but has constant choppy sound during races. :(Knightron)
|Yellow

|- style="background: #90FF90"
|45455341
|Children of Mana
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45555159
|Chrono Trigger
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Seems to run perfect. I did not play long enough to test cut scenes. :(Knightron)
|Green

|- style="background: #90FF90"
|45445741
|Diddy Kong Racing DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|A couple of graphical bugs in a few places, but seems close to perfect. :(Knightron)
|Green

|- style="background: #90FF90"
|4a554a41
|Jump Ultimate Stars (English patched)
|r2.1.0p
|62.9MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F3F781"
|45475049
|Pokemon SoulSilver
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Slight graphical tearing. Lags a little when entering buildings ect. Other than that, it seems very playable. :(Knightron)
|Yellow

|- style="background: #90FF90"
|45484d41
|Metroid Prime Hunters
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems close to perfect. Full speed most of the time, but when lots of enemies are fireing at you, it slows down a little. May encounter bigger issues further into the game. :(Knightron)
|Green

|- style="background: #90FF90"
|45524341
|Sprung The Dating Game
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F7BE81"
|454a4c43
|Mario and Luigi Bowsers Inside Story
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays pretty close to perfect, but freezes during the first fight, while playing as Bowser. :(knightron)
|Orange

|- style="background: #90FF90"
|45355659
|Dragon Quest V Hand of the Heavenly Bride
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Seems to play close to perfectly, very slight choppy inconsistancy between two screens, but not as bad as DQIV. :(Knightron)
|Green

|- style="background: #90FF90"
|45425742
|Plants vs Zombies
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|454b5441
|Kirby Canvas Curse
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|4a534259
|Soma Bringer (English patched)
|r2.1.0p
|122MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45564959
|Dragon Quest IV Chapters of the Chosen
|r2.1.0p
|128MiB
|1GHz
|900MHz
|It can apear a little choppy when playing with vertical screens, but still plays very well: I switch it to one screen mode. :(Knightron)
|Green

|- style="background: #90FF90"
|45464641
|Final Fantasy III
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays pretty damn close to perfect. :(Knightron)
|Green

|- style="background: #F3F781"
|45344659
|Final Fantasy IV
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays at full speed, but has choppy sound quite often. :(Knightron)
|Yellow

|- style="background: #F7BE81"
|4a545941
|Tales Of Innocense (English Patched)
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays at full speed, but there are major graphical issues that make the game very hard to follow. :(Knightron)
|Orange

|- style="background: #90FF90"
|454b5341
|Lost in Blue
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Plays almost perfectly, just a few very minor graphical and sound bugs in a few spots. Microphone fails sometimes but works again once Drastic is restarted. Game crashes occasionally when atempting to light the fire or build something. At the moment, I recommend regular saving through savestates just in case. :(Knightron)
|Green

|- style="background: #F78181"
|45514459
|Dragon Quest IX Sentinels of the Starry Skies
|r2.1.0p
|22.3MiB
|1GHz
|900MHz
|Game crashes on boot. :(Knightron)
|Red

|- style="background: #90FF90"
|454d5241
|Mario and Luigi Partners in Time
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45495941
|Yoshi Touch & Go
|r2.1.0p
|16MiB
|1GHz
|900MHz
|This Game Apears to play perfectly, but it has major problems when the Pandora is put to sleep. :(Knightron)
|Green

|- style="background: #90FF90"
|454b5342
|9 Hours, 9 Persons, 9 Doors
|r2.0.1p
|128MiB
|Rebirth
|850
|Plays at full speed.
|Green

|- style="background: #90FF90"
|45574b59
|Kirby - Super Star Ultra
|r2.0.1p
|128MiB
|CC
|800
|Plays at full speed.
|Green

|- style="background: #F3F781"
|45563241
|M&M's - Break 'Em
|r2.0.1p
|8MiB
|CC
|800
|Plays at too slow to be enjoyed.
|Yellow

|- style="background: #90FF90"
|45365359
|Civilization Revolution DS
|r2.0.1p
|64MiB
|Rebirth
|825MHz
|Fully playable. (Long firststart ~62sec.)
|Green

|- style="background: #90FF90"
|45365359
|Barnyard Blast: Swine of the Night
|r2.0.1p
|8MiB
|1GHz
|1.1GHz
|Works Completely fine. No Lag or Graphical Issues even on cut scenes
|Green

|- style="background: #90FF90"
|45454650
|Fire Emblem: Shadow Dragon (E)
|r2.1.3p
|64MiB
|1GHz
|900MHz
|Runs fine since r2.1.3p
|Green

|- style="background: #90FF90"
|4a564942
|Ivy the Kiwi (J)
|r2.1.3p
|8MiB
|1GHz
|900MHz
|Runs fine since r2.1.0p. Doesn't even need frameskip at 900Mhz.
|Green

|- style="background: #90FF90"
|50505841
|Picross DS (E)
|r2.1.3p
|32MiB
|1GHz
|600MHz
|Very minor graphical glitch where at end of level the top screen image transitions from monochrome to (animated) colour - one pixel line of monochrome image is left above the animated image.
|Green

|- style="background: #90FF90"
|50503643
|Picross 3D (E)
|r2.1.3p
|32MiB
|1GHz
|600MHz
|Absolutely perfect since version r2.1.0p
|Green

|- style="background: #F3F781"
|50344759
|Suikoden Tierkreis
|r2.0.1p
|256MiB
|Rebirth
|900MHz
|Sound sometimes a bit laggy during battle. (tested for 40min only)
|Yellow

|- style="background: #90FF90"
|45375341
|Summon Night, Twin Age
|r2.0.1p
|128MiB
|Rebirth
|900MHz
|nice. (tested for 10h)
|Green

|- style="background: #F3F781"
|404c5741
|The World Ends With You (E)
|r2.0.1p
|128MiB
|Rebirth
|900MHz
|Ran fine as far as the end of the first day. (not further tested.)
|Yellow

|- style="background: #90FF90"
|45434d41
|MarioKart DS (US)
|r2.1.3p
|32MiB
|1GHz
|1050MHz
|Runs fine with frameskip
|Green

|- style="background: #90FF90"
|45444e41
|Brain Age - Train Your Brain in Minutes a Day! (v01)
|r2.1.0p
|16MiB
|1Ghz
|800 Mhz
|Works great. (PowerGod)
|Green

|- style="background: #90FF90"
|50444e41
|Dr Kawashima's Brain Training - How Old Is Your Brain
|r2.1.0p
|16MiB
|1Ghz
|800 Mhz
|Works great. (PowerGod)
|Green

|- style="background: #F3F781"
|455a4443
|Dragon Ball - Origins
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|Playable with some lag. (PowerGod)
|Yellow

|- style="background: #90FF90"
|45503743
|Peggle Dual Shot
|r2.1.3p
|64MiB
|1Ghz
|750MHz
|Perfect play, fluid motion, just like the real thing. :(kumaki+levi)
|Green

|- style="background: #F3F781"
|45533241
|Dragon Ball Z - Supersonic Warriors 2
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|Playable with some lag. (PowerGod)
|Yellow

|- style="background: #F3F781"
|45414441
|Pokemon Diamond Version (v13)
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|No text in the introduction tutorial. Only played it a bit. (PowerGod)
(Edit by knightron: text is now played in DraStic 2.1.0p)
|Yellow

|- style="background: #90FF90"
|45433643
|Infinite Space
|r2.1.3p
|256MiB
|1Ghz
|1050Mhz
|Plays well. Graphical glitches in the attract mode. Played only as far as the first spaceport. (levi)
|Green
|}



==Notes==

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM
* Rebirth - OMAP3530 SoC @ 600MHz stock, **512MiB RAM**
* 1GHz - **DM3730 SoC @ 1GHz stock**, 512MiB RAM}}

[[Category:Emulators]]
[[Category: Compatibility]]
[[Category:List]]

DraStic Compatibility List

2013-09-08T02:11:37Z

Levi: /* The Compatibility List */ Peggle

DraStic is a Nintendo DS Emulator created by Exophase for ARM devices such as the OpenPandora.

* [http://repo.openpandora.org/?page=detail&app=DraStic Download]
* [http://exophase.devzero.co.uk/drastic_readme.txt Readme and Changelog]
* [http://boards.openpandora.org/index.php/topic/12038-emulator-drastic-nintendo-ds/page-1 Forum Thread]

The current version on the Repo is 2.1.0.0 beta, released on August 5th, 2013. It identifies itself as "Version r2.1.0p" on the menu screen.

* [http://pandorawiki.org/DraStic_Compatibility_List_1.x Outdated Previous 1.x Version Compatibility List]

==Compatibility==
''128MB+ zipped games have issues on CC Pandoras because of limited RAM. 256MB zipped games may work on 512MB systems such as the Rebirth or 1GHz Pandora. 512MB zipped games are not expected to run on any system. Unzipped games of any size are not dependent on RAM, so should work the same on all systems.　Note that wifi is not emulated or faked so far, so it may lead to compatibility issues/crashes.''

==Adding to the list==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. Include the unzipped ROM size in base-2 mebibytes (16MB, 64MB, 128MB, etc.). If available please indicate the game ID figure, too. The Game ID figure should be 8 characters long and can usually be found by pressing Y on the rom selection menu.

'''Don't''' post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new DraStic version, update the entry and add that to notes. Please don't copy entries from the old list into this one unless you first re-test the game using a recent version of DraStic and update the color and notes as required.

Default frameskip for version 2.0.1p is automatic and 4. Please record a comment if you use a different setting.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by Exophase about further debugging your problems.

==The Compatibility List==


You can sort the colums by clicking the table header.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game ID
! Game Name
! DraStic Version
! ROM Size
! Pandora Model[1]

! Frequency
! Notes
! Status

|- style="background: #90FF90"
|454d5341
|Super Mario 64 DS
|r2.1.0p
|16MiB
|1GHz
|900MHz
|Minimal graphical tears; almost none; other than that seems to plays perfectly. :(knightron)
|Green

|- style="background: #F3F781"
|55595241
|Rayman DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Very choppy sound often, and frameskip choppyness too. :(knightron)
|Yellow

|- style="background: #90FF90"
|50445441
|42 All Time Classics/Clubhouse Games (E)
|r2.1.0p
|16MiB
|1GHz
|900MHz
|Plays fine with frameskip 2
|Green

|- style="background: #90FF90"
|45575941
|Yoshis Island DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F3F781"
|50425341
|Snowboard Kids
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Runs at full speed but has constant choppy sound during races. :(Knightron)
|Yellow

|- style="background: #90FF90"
|45455341
|Children of Mana
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45555159
|Chrono Trigger
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Seems to run perfect. I did not play long enough to test cut scenes. :(Knightron)
|Green

|- style="background: #90FF90"
|45445741
|Diddy Kong Racing DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|A couple of graphical bugs in a few places, but seems close to perfect. :(Knightron)
|Green

|- style="background: #90FF90"
|4a554a41
|Jump Ultimate Stars (English patched)
|r2.1.0p
|62.9MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F3F781"
|45475049
|Pokemon SoulSilver
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Slight graphical tearing. Lags a little when entering buildings ect. Other than that, it seems very playable. :(Knightron)
|Yellow

|- style="background: #90FF90"
|45484d41
|Metroid Prime Hunters
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems close to perfect. Full speed most of the time, but when lots of enemies are fireing at you, it slows down a little. May encounter bigger issues further into the game. :(Knightron)
|Green

|- style="background: #90FF90"
|45524341
|Sprung The Dating Game
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F7BE81"
|454a4c43
|Mario and Luigi Bowsers Inside Story
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays pretty close to perfect, but freezes during the first fight, while playing as Bowser. :(knightron)
|Orange

|- style="background: #90FF90"
|45355659
|Dragon Quest V Hand of the Heavenly Bride
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Seems to play close to perfectly, very slight choppy inconsistancy between two screens, but not as bad as DQIV. :(Knightron)
|Green

|- style="background: #90FF90"
|45425742
|Plants vs Zombies
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|454b5441
|Kirby Canvas Curse
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|4a534259
|Soma Bringer (English patched)
|r2.1.0p
|122MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45564959
|Dragon Quest IV Chapters of the Chosen
|r2.1.0p
|128MiB
|1GHz
|900MHz
|It can apear a little choppy when playing with vertical screens, but still plays very well: I switch it to one screen mode. :(Knightron)
|Green

|- style="background: #90FF90"
|45464641
|Final Fantasy III
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays pretty damn close to perfect. :(Knightron)
|Green

|- style="background: #F3F781"
|45344659
|Final Fantasy IV
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays at full speed, but has choppy sound quite often. :(Knightron)
|Yellow

|- style="background: #F7BE81"
|4a545941
|Tales Of Innocense (English Patched)
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays at full speed, but there are major graphical issues that make the game very hard to follow. :(Knightron)
|Orange

|- style="background: #90FF90"
|454b5341
|Lost in Blue
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Plays almost perfectly, just a few very minor graphical and sound bugs in a few spots. Microphone fails sometimes but works again once Drastic is restarted. Game crashes occasionally when atempting to light the fire or build something. At the moment, I recommend regular saving through savestates just in case. :(Knightron)
|Green

|- style="background: #F78181"
|45514459
|Dragon Quest IX Sentinels of the Starry Skies
|r2.1.0p
|22.3MiB
|1GHz
|900MHz
|Game crashes on boot. :(Knightron)
|Red

|- style="background: #90FF90"
|454d5241
|Mario and Luigi Partners in Time
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45495941
|Yoshi Touch & Go
|r2.1.0p
|16MiB
|1GHz
|900MHz
|This Game Apears to play perfectly, but it has major problems when the Pandora is put to sleep. :(Knightron)
|Green

|- style="background: #90FF90"
|454b5342
|9 Hours, 9 Persons, 9 Doors
|r2.0.1p
|128MiB
|Rebirth
|850
|Plays at full speed.
|Green

|- style="background: #90FF90"
|45574b59
|Kirby - Super Star Ultra
|r2.0.1p
|128MiB
|CC
|800
|Plays at full speed.
|Green

|- style="background: #F3F781"
|45563241
|M&M's - Break 'Em
|r2.0.1p
|8MiB
|CC
|800
|Plays at too slow to be enjoyed.
|Yellow

|- style="background: #90FF90"
|45365359
|Civilization Revolution DS
|r2.0.1p
|64MiB
|Rebirth
|825MHz
|Fully playable. (Long firststart ~62sec.)
|Green

|- style="background: #90FF90"
|45365359
|Barnyard Blast: Swine of the Night
|r2.0.1p
|8MiB
|1GHz
|1.1GHz
|Works Completely fine. No Lag or Graphical Issues even on cut scenes
|Green

|- style="background: #90FF90"
|45454650
|Fire Emblem: Shadow Dragon (E)
|r2.1.3p
|64MiB
|1GHz
|900MHz
|Runs fine since r2.1.3p
|Green

|- style="background: #90FF90"
|4a564942
|Ivy the Kiwi (J)
|r2.1.3p
|8MiB
|1GHz
|900MHz
|Runs fine since r2.1.0p. Doesn't even need frameskip at 900Mhz.
|Green

|- style="background: #90FF90"
|50505841
|Picross DS (E)
|r2.1.3p
|32MiB
|1GHz
|600MHz
|Very minor graphical glitch where at end of level the top screen image transitions from monochrome to (animated) colour - one pixel line of monochrome image is left above the animated image.
|Green

|- style="background: #90FF90"
|50503643
|Picross 3D (E)
|r2.1.3p
|32MiB
|1GHz
|600MHz
|Absolutely perfect since version r2.1.0p
|Green

|- style="background: #F3F781"
|50344759
|Suikoden Tierkreis
|r2.0.1p
|256MiB
|Rebirth
|900MHz
|Sound sometimes a bit laggy during battle. (tested for 40min only)
|Yellow

|- style="background: #90FF90"
|45375341
|Summon Night, Twin Age
|r2.0.1p
|128MiB
|Rebirth
|900MHz
|nice. (tested for 10h)
|Green

|- style="background: #F3F781"
|404c5741
|The World Ends With You (E)
|r2.0.1p
|128MiB
|Rebirth
|900MHz
|Ran fine as far as the end of the first day. (not further tested.)
|Yellow

|- style="background: #90FF90"
|45434d41
|MarioKart DS (US)
|r2.1.3p
|32MiB
|1GHz
|1050MHz
|Runs fine with frameskip
|Green

|- style="background: #90FF90"
|45444e41
|Brain Age - Train Your Brain in Minutes a Day! (v01)
|r2.1.0p
|16MiB
|1Ghz
|800 Mhz
|Works great. (PowerGod)
|Green

|- style="background: #90FF90"
|50444e41
|Dr Kawashima's Brain Training - How Old Is Your Brain
|r2.1.0p
|16MiB
|1Ghz
|800 Mhz
|Works great. (PowerGod)
|Green

|- style="background: #F3F781"
|455a4443
|Dragon Ball - Origins
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|Playable with some lag. (PowerGod)
|Yellow

|- style="background: #90FF90"
|45503743
|Peggle Dual Shot
|r2.1.3p
|64MiB
|1Ghz
|750MHz
|Perfect play, fluid motion, just like the real thing. :(kumaki+levi)
|Green

|- style="background: #F3F781"
|45533241
|Dragon Ball Z - Supersonic Warriors 2
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|Playable with some lag. (PowerGod)
|Yellow

|- style="background: #F3F781"
|45414441
|Pokemon Diamond Version (v13)
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|No text in the introduction tutorial. Only played it a bit. (PowerGod)
(Edit by knightron: text is now played in DraStic 2.1.0p)
|Yellow
|}



==Notes==

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM
* Rebirth - OMAP3530 SoC @ 600MHz stock, **512MiB RAM**
* 1GHz - **DM3730 SoC @ 1GHz stock**, 512MiB RAM}}

[[Category:Emulators]]
[[Category: Compatibility]]
[[Category:List]]

DraStic Compatibility List

2013-09-06T01:10:43Z

Levi: /* The Compatibility List */

DraStic is a Nintendo DS Emulator created by Exophase for ARM devices such as the OpenPandora.

* [http://repo.openpandora.org/?page=detail&app=DraStic Download]
* [http://exophase.devzero.co.uk/drastic_readme.txt Readme and Changelog]
* [http://boards.openpandora.org/index.php/topic/12038-emulator-drastic-nintendo-ds/page-1 Forum Thread]

The current version on the Repo is 2.1.0.0 beta, released on August 5th, 2013. It identifies itself as "Version r2.1.0p" on the menu screen.

* [http://pandorawiki.org/DraStic_Compatibility_List_1.x Outdated Previous 1.x Version Compatibility List]

==Compatibility==
''128MB+ zipped games have issues on CC Pandoras because of limited RAM. 256MB zipped games may work on 512MB systems such as the Rebirth or 1GHz Pandora. 512MB zipped games are not expected to run on any system. Unzipped games of any size are not dependent on RAM, so should work the same on all systems.　Note that wifi is not emulated or faked so far, so it may lead to compatibility issues/crashes.''

==Adding to the list==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. Include the unzipped ROM size in base-2 mebibytes (16MB, 64MB, 128MB, etc.). If available please indicate the game ID figure, too. The Game ID figure should be 8 characters long and can usually be found by pressing Y on the rom selection menu.

'''Don't''' post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new DraStic version, update the entry and add that to notes. Please don't copy entries from the old list into this one unless you first re-test the game using a recent version of DraStic and update the color and notes as required.

Default frameskip for version 2.0.1p is automatic and 4. Please record a comment if you use a different setting.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by Exophase about further debugging your problems.

==The Compatibility List==


You can sort the colums by clicking the table header.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game ID
! Game Name
! DraStic Version
! ROM Size
! Pandora Model[1]

! Frequency
! Notes
! Status

|- style="background: #90FF90"
|454d5341
|Super Mario 64 DS
|r2.1.0p
|16MiB
|1GHz
|900MHz
|Minimal graphical tears; almost none; other than that seems to plays perfectly. :(knightron)
|Green

|- style="background: #F3F781"
|55595241
|Rayman DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Very choppy sound often, and frameskip choppyness too. :(knightron)
|Yellow

|- style="background: #90FF90"
|50445441
|42 All Time Classics/Clubhouse Games (E)
|r2.1.0p
|16MiB
|1GHz
|900MHz
|Plays fine with frameskip 2
|Green

|- style="background: #90FF90"
|45575941
|Yoshis Island DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F3F781"
|50425341
|Snowboard Kids
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Runs at full speed but has constant choppy sound during races. :(Knightron)
|Yellow

|- style="background: #90FF90"
|45455341
|Children of Mana
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45555159
|Chrono Trigger
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Seems to run perfect. I did not play long enough to test cut scenes. :(Knightron)
|Green

|- style="background: #90FF90"
|45445741
|Diddy Kong Racing DS
|r2.1.0p
|32MiB
|1GHz
|900MHz
|A couple of graphical bugs in a few places, but seems close to perfect. :(Knightron)
|Green

|- style="background: #90FF90"
|4a554a41
|Jump Ultimate Stars (English patched)
|r2.1.0p
|62.9MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F3F781"
|45475049
|Pokemon SoulSilver
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Slight graphical tearing. Lags a little when entering buildings ect. Other than that, it seems very playable. :(Knightron)
|Yellow

|- style="background: #90FF90"
|45484d41
|Metroid Prime Hunters
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems close to perfect. Full speed most of the time, but when lots of enemies are fireing at you, it slows down a little. May encounter bigger issues further into the game. :(Knightron)
|Green

|- style="background: #90FF90"
|45524341
|Sprung The Dating Game
|r2.1.0p
|32MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #F7BE81"
|454a4c43
|Mario and Luigi Bowsers Inside Story
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays pretty close to perfect, but freezes during the first fight, while playing as Bowser. :(knightron)
|Orange

|- style="background: #90FF90"
|45355659
|Dragon Quest V Hand of the Heavenly Bride
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Seems to play close to perfectly, very slight choppy inconsistancy between two screens, but not as bad as DQIV. :(Knightron)
|Green

|- style="background: #90FF90"
|45425742
|Plants vs Zombies
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|454b5441
|Kirby Canvas Curse
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|4a534259
|Soma Bringer (English patched)
|r2.1.0p
|122MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45564959
|Dragon Quest IV Chapters of the Chosen
|r2.1.0p
|128MiB
|1GHz
|900MHz
|It can apear a little choppy when playing with vertical screens, but still plays very well: I switch it to one screen mode. :(Knightron)
|Green

|- style="background: #90FF90"
|45464641
|Final Fantasy III
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays pretty damn close to perfect. :(Knightron)
|Green

|- style="background: #F3F781"
|45344659
|Final Fantasy IV
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays at full speed, but has choppy sound quite often. :(Knightron)
|Yellow

|- style="background: #F7BE81"
|4a545941
|Tales Of Innocense (English Patched)
|r2.1.0p
|128MiB
|1GHz
|900MHz
|Plays at full speed, but there are major graphical issues that make the game very hard to follow. :(Knightron)
|Orange

|- style="background: #90FF90"
|454b5341
|Lost in Blue
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Plays almost perfectly, just a few very minor graphical and sound bugs in a few spots. Microphone fails sometimes but works again once Drastic is restarted. Game crashes occasionally when atempting to light the fire or build something. At the moment, I recommend regular saving through savestates just in case. :(Knightron)
|Green

|- style="background: #F78181"
|45514459
|Dragon Quest IX Sentinels of the Starry Skies
|r2.1.0p
|22.3MiB
|1GHz
|900MHz
|Game crashes on boot. :(Knightron)
|Red

|- style="background: #90FF90"
|454d5241
|Mario and Luigi Partners in Time
|r2.1.0p
|64MiB
|1GHz
|900MHz
|Seems to play perfectly. :(Knightron)
|Green

|- style="background: #90FF90"
|45495941
|Yoshi Touch & Go
|r2.1.0p
|16MiB
|1GHz
|900MHz
|This Game Apears to play perfectly, but it has major problems when the Pandora is put to sleep. :(Knightron)
|Green

|- style="background: #90FF90"
|454b5342
|9 Hours, 9 Persons, 9 Doors
|r2.0.1p
|128MiB
|Rebirth
|850
|Plays at full speed.
|Green

|- style="background: #90FF90"
|45574b59
|Kirby - Super Star Ultra
|r2.0.1p
|128MiB
|CC
|800
|Plays at full speed.
|Green

|- style="background: #F3F781"
|45563241
|M&M's - Break 'Em
|r2.0.1p
|8MiB
|CC
|800
|Plays at too slow to be enjoyed.
|Yellow

|- style="background: #90FF90"
|45365359
|Civilization Revolution DS
|r2.0.1p
|64MiB
|Rebirth
|825MHz
|Fully playable. (Long firststart ~62sec.)
|Green

|- style="background: #90FF90"
|45365359
|Barnyard Blast: Swine of the Night
|r2.0.1p
|8MiB
|1GHz
|1.1GHz
|Works Completely fine. No Lag or Graphical Issues even on cut scenes
|Green

|- style="background: #90FF90"
|45454650
|Fire Emblem: Shadow Dragon (E)
|r2.1.3p
|64MiB
|1GHz
|900MHz
|Runs fine since r2.1.3p
|Green

|- style="background: #90FF90"
|4a564942
|Ivy the Kiwi (J)
|r2.1.3p
|8MiB
|1GHz
|900MHz
|Runs fine since r2.1.0p. Doesn't even need frameskip at 900Mhz.
|Green

|- style="background: #90FF90"
|50505841
|Picross DS (E)
|r2.1.3p
|32MiB
|1GHz
|600MHz
|Very minor graphical glitch where at end of level the top screen image transitions from monochrome to (animated) colour - one pixel line of monochrome image is left above the animated image.
|Green

|- style="background: #90FF90"
|50503643
|Picross 3D (E)
|r2.1.3p
|32MiB
|1GHz
|600MHz
|Absolutely perfect since version r2.1.0p
|Green

|- style="background: #F3F781"
|50344759
|Suikoden Tierkreis
|r2.0.1p
|256MiB
|Rebirth
|900MHz
|Sound sometimes a bit laggy during battle. (tested for 40min only)
|Yellow

|- style="background: #90FF90"
|45375341
|Summon Night, Twin Age
|r2.0.1p
|128MiB
|Rebirth
|900MHz
|nice. (tested for 10h)
|Green

|- style="background: #F3F781"
|404c5741
|The World Ends With You (E)
|r2.0.1p
|128MiB
|Rebirth
|900MHz
|Ran fine as far as the end of the first day. (not further tested.)
|Yellow

|- style="background: #90FF90"
|45434d41
|MarioKart DS (US)
|r2.1.3p
|32MiB
|1GHz
|1050MHz
|Runs fine with frameskip
|Green

|- style="background: #90FF90"
|45444e41
|Brain Age - Train Your Brain in Minutes a Day! (v01)
|r2.1.0p
|16MiB
|1Ghz
|800 Mhz
|Works great. (PowerGod)
|Green

|- style="background: #90FF90"
|50444e41
|Dr Kawashima's Brain Training - How Old Is Your Brain
|r2.1.0p
|16MiB
|1Ghz
|800 Mhz
|Works great. (PowerGod)
|Green

|- style="background: #F3F781"
|455a4443
|Dragon Ball - Origins
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|Playable with some lag. (PowerGod)
|Yellow

|- style="background: #F3F781"
|45533241
|Dragon Ball Z - Supersonic Warriors 2
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|Playable with some lag. (PowerGod)
|Yellow

|- style="background: #F3F781"
|45414441
|Pokemon Diamond Version (v13)
|r2.0.1p
|64MiB
|1Ghz
|800 Mhz
|No text in the introduction tutorial. Only played it a bit. (PowerGod)
(Edit by knightron: text is now played in DraStic 2.1.0p)
|Yellow
|}



==Notes==

1. Pandora model:
* CC - OMAP3550 SoC@600Mhz stock, 256MiB RAM
* Rebirth - OMAP3530 SoC @ 600MHz stock, **512MiB RAM**
* 1GHz - **DM3730 SoC @ 1GHz stock**, 512MiB RAM}}

[[Category:Emulators]]
[[Category: Compatibility]]
[[Category:List]]