Frequently Asked Questions

What to expect when booting Pyra for the first time

First Run Wizard

After booting, the screen will look something like this. Further refinements to be developed by various members of the community. The first run wizard will walk you through creating a user, setting a password, and the usual keyboard setup.

What software is available for the Pyra?

How do I install software?

The default Pyra OS is based on Debian testing, specifically for the "armhf" architecture, which has many programs. To locate a package to install, try searching for a keyword like this (on the command line): apt-cache search synthesizer. Then run sudo apt-get install zynaddsubfx to install the program. Then type in zynaddsubfx to run it. Easy!

For CPU-intensive programs such as games, however, the standard Debian packages won't be optimized well for the Pyra hardware. Like the Pandora community repository, there will be a Pyra specific repository which utilizes the DBP (DragonBox Package) format. TODO: simple run instructions for DBP, and locations where to have the .dbp files.

When will the phone software be ready?

When someone gets around to porting this stuff. It may be a couple months (or longer) after the first preorder Pyras arrive in people's pockets.

Hardware questions

What carrier compatibility is there with the Pyra cell module?

The Pyra has a GSM module, so CDMA network carriers in the USA are definitely out. (Verizon and Sprint use CDMA.) That leaves T-mobile and Sprint in the USA.

In addition, the compatible carriers would likely have to approve the use of the Pyra on their networks.

How can I get the Pyra working on one of the compatible networks?

You may have to call or talk to someone about it, give them the device information, etc.

Can I turn off data and use the Pyra as a dumb phone?

For the above carriers, probably, if/when they allow the device on the network, and if/when the software will be ready.

Why is there not a camera?

At the time of development, all available camera modules are too thick (front to back) to fit inside the lid without enlarging the (already quite thick) case. Putting a camera in the base would result in an awkward and unusable camera angle.

Concerns were also raised about:

• The utility of a small, low-performance camera
• Privacy implications
• Cost

Why only 2GB? Why not 4GB RAM?

Simple GNU/Linux distributions (such as the default Pyra OS) do not require the 1 to 2 GB of memory that other proprietary OSes require, so most of the 2 GB will be available to the user, and this will be sufficient for the vast majority of Pyra software and use-cases. For a demonstration trying to push a Pyra devboard to its limits, check out this video.

There are always compromises to make when working on a device, especially one not expected to sell millions of units. The Pyra is based around a small but active community, which can really push the potential of the device. If you are more excited about specs than community, then perhaps the Pyra is currently not for you. There is the possibility of an upgrade to 4 GB or 8 GB if the Pyra does well, which would only require an update of the CPU board (with the extra RAM). A few years in the future, CPU upgrades would also likely increase the RAM.

Why not include hardware X on the Pyra?

The reason(s) may include but not be limited to:

• Limited funding
• Limited resources
• Potential future upgrades/versions to add it
• Current expected specs are adequate for MOST of the existing community
• Feature creep would mean the Pyra would never get released
• EvilDragon made his decision to not include it

The Pyra will be a modular, hackable device. Just as the Pandora has been lovingly modded, there will be creative solutions to get the most out of the Pyra. The hardware designs for the Pyra are also expected to be open-sourced, so anything is possible in terms of homebrew hardware development.

What's this about eSATA?

See: Storage