Pandora (computer)
handheld console and mobile computer series
The Pandora was a handheld gaming computer developed and produced by OpenPandora, which is made up of former distributors and community members of the GP32 and GP2X handhelds. Originally released in 2010, it was designed to take advantage of existing free and open-source software and to be a target for homebrew development. The Pandora runs Linux and uses an ARM processor. Until 2013, multiple batches of slightly updated Pandora variants were produced. In 2014, development of a redesigned and upgraded successor, named DragonBox Pyra, began.
History
Development of the Pandora began when Craig Rothwell, Fatih Kilic, Michael Mrozek and (later) Michael Weston teamed up and planned a portable system that would excel in the areas where they thought the GP32 and GP2X systems (from Game Park and GamePark Holdings respectively) were flawed. The Pandora was designed based on ideas and suggestions contributed by GP32X forum members, with the goal of creating the ultimate open source handheld device. When announcing the system, the designers of Pandora stated that it would be more powerful than any handheld video game console that had yet existed.
The final case and keymat design was made by Dave Cancilier (DaveC), who was known on the forums for custom hardware modifications.
In February 2008 the Pandora wiki had already been created; as of 2014, it contains a thousand pages and is translated with the MediaWiki Translate extension.
This brief starts where responsible research should: with the source description of “Pandora (computer)” as handheld console and mobile computer series. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as handheld console and mobile computer series. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Aug 30, 2026. The linked authority identifier is Q225009. 1 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2010, 2013, 2014 and 2008.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Pandora (computer)”, its source revision and the description used here.
- Expand the search: follow Pandora (computer) primary sources, Pandora (computer) archive and Pandora research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Pandora (computer)”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Pandora (computer)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.