Frequently Asked Questions: Difference between revisions

From Pyra Wiki
Jump to navigation Jump to search
Line 15: Line 15:
The default Pyra OS is based on [https://packages.debian.org/testing/ 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):  <code>apt-cache search synthesizer</code>.  Then run <code>sudo apt-get install zynaddsubfx</code> to install the program.  Then type in <code>zynaddsubfx</code> to run it.  Easy!
The default Pyra OS is based on [https://packages.debian.org/testing/ 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):  <code>apt-cache search synthesizer</code>.  Then run <code>sudo apt-get install zynaddsubfx</code> to install the program.  Then type in <code>zynaddsubfx</code> 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 [http://repo.openpandora.org/ Pandora community repository], there will be a Pyra specific repository which utilizes the DBP (DragonBox Package) format.  (For the interested, see the [https://pyra-handheld.com/boards/threads/a-possible-pnd-system-replacement.74709/ development thread].)
For CPU-intensive programs such as games, however, the standard Debian packages won't be optimized well for the Pyra hardware.  Like the [http://repo.openpandora.org/ Pandora community repository], there will be a Pyra specific repository which utilizes the DBP (DragonBox Package) format.  (For the interested, see the [https://pyra-handheld.com/boards/threads/a-possible-pnd-system-replacement.74709/ development thread].) TODO:  simple install instructions for DBP.
 
TODO:  simple install instructions for DBP.


=== How can I control volume via software? ===
=== How can I control volume via software? ===
=== What's this about screen tearing issues? ===
=== What's this about screen tearing issues? ===
=== When will the GPU be fully utilizable? ===
=== When will the GPU be fully utilizable? ===


== How can I customize my Pyra? ==
== How can I customize my Pyra? ==

Revision as of 04:26, 24 March 2016

What to expect when booting Pyra for the first time

First Run Wizard

After booting, the screen will look something like this. Code is developed by community members bzar and Christoph.Krn. The first run wizard will walk you through creating a user, setting a password, and the usual keyboard setup.

Help, I'm a Linux n00b!

What are the standards for navigating menus with the game buttons?

How do I connect to WiFi?

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. (For the interested, see the development thread.) TODO: simple install instructions for DBP.

How can I control volume via software?

What's this about screen tearing issues?

When will the GPU be fully utilizable?

How can I customize my Pyra?

How can I change the theme?

How can I tweak the options for Pyra-specific hardware? (e.g. Keyboard, Nubs, Touchscreen, etc.)

Hardware questions

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 is there not a camera???

What's this about eSATA?