Difference between revisions of "Android"
(Category, fluidity.) |
|||
(3 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | |||
[[File:Lead_Photo_For_Android0-31797052380859137.png|thumbnail|Android logo]] | [[File:Lead_Photo_For_Android0-31797052380859137.png|thumbnail|Android logo]] | ||
− | + | Android is Google's Linux-based operating system for ARM mobile devices. <br> | |
− | < | + | This page covers the [http://boards.openpandora.org/topic/8626-android-gingerbread-in-a-pnd/ Android in a PND for Gingerbread]. |
− | |||
− | Android | ||
= Installing Android = <!--T:2--> | = Installing Android = <!--T:2--> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<!--T:5--> | <!--T:5--> | ||
− | # You | + | # You need at least [[Ångström]] Beta 5a. |
− | # | + | # Download the Android PND from [http://notaz.gp2x.de/releases/pandora/gingerbread_r6.pnd here]. |
− | # For safety reasons, if you want to use a second SD Card with Android, use an empty one. | + | # Move the Android PND onto the card that is in your left SD card slot. |
+ | # For safety reasons, if you want to use a second SD Card with Android, use an empty one. Android may corrupt it. Android seems to only delete files in the root directory of the second card. Anything in subdirectories shouldn't be affected. | ||
# If your date is not set properly: Do so before starting Android. If the date is in the past, there will be issues with the Google certification. | # If your date is not set properly: Do so before starting Android. If the date is in the past, there will be issues with the Google certification. | ||
# Start Android from System/Android Gingerbread. It takes a while to boot. Once it has booted up, setup your WiFi connection. | # Start Android from System/Android Gingerbread. It takes a while to boot. Once it has booted up, setup your WiFi connection. | ||
− | # To install APKs, put them onto a second SD Card and | + | # To install APKs, put them onto a second SD Card and execute them using the built-in FileManager. |
# To stop Android, select "Kill Android" from the menu. | # To stop Android, select "Kill Android" from the menu. | ||
− | + | ==Key Mapping== | |
− | |||
− | |||
− | ==Key | ||
− | |||
Home : Pandora Button or F1[/background] <br> | Home : Pandora Button or F1[/background] <br> | ||
Back : Esc, Right nub to the right. <br> | Back : Esc, Right nub to the right. <br> | ||
Line 34: | Line 22: | ||
Volume Up / Down : F12 / F11 <br> | Volume Up / Down : F12 / F11 <br> | ||
− | =Android | + | =Android APK Repositories= |
− | + | [https://f-droid.org/ F-Droid] is a high quality repository with only free and open-source software. | |
− | + | To use F-Droid, install the APK from it's [https://f-droid.org/ website]. To install the APK, just execute it from the file manager. | |
− | |||
− | |||
− | [https://f-droid.org/ | ||
− | + | [https://play.google.com/store Google Play] is Google's official repository with software, music, movies, and other media. | |
− | + | To use Google Play: | |
+ | # Set up WiFi on your Android installation, and the system time from [[Ångström]]. | ||
+ | # Download this [http://www.androidfilehost.com/?fid=22979706399755027/ ZIP file]. | ||
+ | # Extract the ZIP into the /pandora/appdata/android_gingerbread folder on your SD Card. Remove the meta-inf-Folder. | ||
+ | # On your next Android boot, the Play Store setup should appear automatically.<br> | ||
− | + | =Map Touchscreen Controls to Physical Controls= | |
− | + | Not all games support physical controls-- some only use the touchscreen.<br> | |
− | + | However, there's an app called "GameKeyboard 2.0" that maps touchscreen controls to physical controls.<br> | |
− | + | [http://boards.openpandora.org/index.php?/topic/8871-how-to-install-android-on-your-pandora/page__pid__159757#entry159757 This guide] is intended to help you use GameKeyboard. | |
− | + | # Go to CyanogenMod Settings and enable "Soft Keyboard" on long menu button press. This way you can bring up the keyboard in most games by holding the Menu Button. | |
− | + | # Run GameKeyboard and set it up. | |
− | |||
− | |||
− | =Map Touchscreen Controls to | ||
− | |||
− | |||
− | Not all games support physical controls - some only use the touchscreen. | ||
− | However, there's an app called "GameKeyboard 2.0" that | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | # Go to CyanogenMod Settings and enable "Soft Keyboard" on long menu button press. This way you can bring up the keyboard in most games holding the Menu Button | ||
− | # Run GameKeyboard and set it up | ||
# Follow the on-screen instructions to enable it as SoftKeyboard and choose it as current SoftKeyboard. | # Follow the on-screen instructions to enable it as SoftKeyboard and choose it as current SoftKeyboard. | ||
# Then in the settings, do the following: | # Then in the settings, do the following: | ||
Line 73: | Line 48: | ||
Go into "Layout Edit" and allow "Layout Edit Mode" | Go into "Layout Edit" and allow "Layout Edit Mode" | ||
− | + | This is the first-time setup, GameKeyboard is now ready to be used. Grant it root access when it asks for it. | |
− | This is the first-time setup, GameKeyboard is now ready to be used. Grant it root access when it asks for | ||
− | |||
− | |||
# Run your game. If the touchscreen buttons and DPad are located in the default GameKeyboard locations, the Pandora controls should now just work. | # Run your game. If the touchscreen buttons and DPad are located in the default GameKeyboard locations, the Pandora controls should now just work. | ||
# If buttons / DPad are somewhere else on the screen, hold the menu button which should show the GameKeyboard controls (doesn't work with all games). | # If buttons / DPad are somewhere else on the screen, hold the menu button which should show the GameKeyboard controls (doesn't work with all games). | ||
# Move the controls around using the touchscreen to match the touchscreen controls. Some games hide them though when you press the menu button, some don't even show the GameKeyboard as they disable the softkeyboard. In this case, remember where DPad / buttons need to be, go to the GameKeyboard app and slide the controls at the desired location and then go back to the game. | # Move the controls around using the touchscreen to match the touchscreen controls. Some games hide them though when you press the menu button, some don't even show the GameKeyboard as they disable the softkeyboard. In this case, remember where DPad / buttons need to be, go to the GameKeyboard app and slide the controls at the desired location and then go back to the game. | ||
− | |||
Once that's done, the game will work with your physical gaming controls. | Once that's done, the game will work with your physical gaming controls. | ||
As you can save different profiles in GameKeyboard, you only need to match the locations per game once and then safe the config. | As you can save different profiles in GameKeyboard, you only need to match the locations per game once and then safe the config. | ||
− | + | = How to Remap Android Hardware Keys = | |
− | + | # Install a text editor from F-Droid or Google Play, such as 920 Editor and Jota+. | |
− | + | # Install a file manager from F-Droid or Google Play, such as Root Browser. | |
− | + | # Open up the file manager and navigate to /system/usr/keylayout | |
− | = How to | + | # Copy all the contents of that folder to /mnt/sdcard2/Backups |
− | + | # Now, open the text editor. | |
− | + | # Open gpio-keys.kl in the Backups folder. | |
− | + | # Edit the file as you wish. | |
− | + | ## I reccomend you change key 29 from "BUTTON_SELECT" to "BACK" | |
− | + | ## It is also reccomended to change key 56 from "BUTTON_START" to "MENU" | |
− | + | ## You should reference [http://code.google.com/p/androhid/wiki/Keycodes this page] on Android keycodes for easy editing. | |
− | + | # After editing the file, save and exit the text editor. | |
− | + | # Open your file manager and delete /system/usr/keylayout/gpio-keys.kl | |
− | + | # Copy /mnt/sdcard2/Backups/gpio-keys.kl to /system/usr/keylayout | |
− | + | # Finally, relaunch Android with the "Kill Android" app. | |
− | + | # Finally, confirm the key remapping. | |
− | Copy all the contents of that folder to /mnt/sdcard2/ | ||
− | |||
− | |||
− | Now, | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | change key 29 from "BUTTON_SELECT" to "BACK" | ||
− | |||
− | |||
− | change key 56 from "BUTTON_START" to "MENU" | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | save and exit. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | Unfortunately, the coding for the nubs is incomplete. Right_Nub_Down is mapped to Keycode 82 and Right_Nub_Left is mapped to keycode 4 but other than that, the nubs have no key functionality and so as far as I can tell, you can't change what they do. If anyone wants to look around and see if they can find a way, please post in [http://boards.openpandora.org/index.php/topic/11355-tutorial-how-to-remap-android-hardware-keys/ the thread]. | |
− | |||
− | + | [https://github.com/chrisboyle/keytest/KeyTest.apk/qr_code KeyTest] is a useful program that tells you the keycode for the key you're currently pressing. | |
− | |||
− | + | [[Category:Operating system]] | |
− | [ | ||
− | |||
− |
Latest revision as of 20:13, 20 July 2015
Android is Google's Linux-based operating system for ARM mobile devices.
This page covers the Android in a PND for Gingerbread.
Contents
Installing Android
- You need at least Ångström Beta 5a.
- Download the Android PND from here.
- Move the Android PND onto the card that is in your left SD card slot.
- For safety reasons, if you want to use a second SD Card with Android, use an empty one. Android may corrupt it. Android seems to only delete files in the root directory of the second card. Anything in subdirectories shouldn't be affected.
- If your date is not set properly: Do so before starting Android. If the date is in the past, there will be issues with the Google certification.
- Start Android from System/Android Gingerbread. It takes a while to boot. Once it has booted up, setup your WiFi connection.
- To install APKs, put them onto a second SD Card and execute them using the built-in FileManager.
- To stop Android, select "Kill Android" from the menu.
Key Mapping
Home : Pandora Button or F1[/background]
Back : Esc, Right nub to the right.
Menu : F2
Search : Unknown
Volume Up / Down : F12 / F11
Android APK Repositories
F-Droid is a high quality repository with only free and open-source software. To use F-Droid, install the APK from it's website. To install the APK, just execute it from the file manager.
Google Play is Google's official repository with software, music, movies, and other media. To use Google Play:
- Set up WiFi on your Android installation, and the system time from Ångström.
- Download this ZIP file.
- Extract the ZIP into the /pandora/appdata/android_gingerbread folder on your SD Card. Remove the meta-inf-Folder.
- On your next Android boot, the Play Store setup should appear automatically.
Map Touchscreen Controls to Physical Controls
Not all games support physical controls-- some only use the touchscreen.
However, there's an app called "GameKeyboard 2.0" that maps touchscreen controls to physical controls.
This guide is intended to help you use GameKeyboard.
- Go to CyanogenMod Settings and enable "Soft Keyboard" on long menu button press. This way you can bring up the keyboard in most games by holding the Menu Button.
- Run GameKeyboard and set it up.
- Follow the on-screen instructions to enable it as SoftKeyboard and choose it as current SoftKeyboard.
- Then in the settings, do the following:
Enable "Touchscreen Mode" Enable "Remap Hard-Key" Map your buttons with "Hardkey Mappings": Select a free slot, press the desired D-Pad direction or button and select in the list what it should be (i.e. D-Pad up to D-Pad up, etc.) Go into "Layout Edit" and allow "Layout Edit Mode"
This is the first-time setup, GameKeyboard is now ready to be used. Grant it root access when it asks for it.
- Run your game. If the touchscreen buttons and DPad are located in the default GameKeyboard locations, the Pandora controls should now just work.
- If buttons / DPad are somewhere else on the screen, hold the menu button which should show the GameKeyboard controls (doesn't work with all games).
- Move the controls around using the touchscreen to match the touchscreen controls. Some games hide them though when you press the menu button, some don't even show the GameKeyboard as they disable the softkeyboard. In this case, remember where DPad / buttons need to be, go to the GameKeyboard app and slide the controls at the desired location and then go back to the game.
Once that's done, the game will work with your physical gaming controls. As you can save different profiles in GameKeyboard, you only need to match the locations per game once and then safe the config.
How to Remap Android Hardware Keys
- Install a text editor from F-Droid or Google Play, such as 920 Editor and Jota+.
- Install a file manager from F-Droid or Google Play, such as Root Browser.
- Open up the file manager and navigate to /system/usr/keylayout
- Copy all the contents of that folder to /mnt/sdcard2/Backups
- Now, open the text editor.
- Open gpio-keys.kl in the Backups folder.
- Edit the file as you wish.
- I reccomend you change key 29 from "BUTTON_SELECT" to "BACK"
- It is also reccomended to change key 56 from "BUTTON_START" to "MENU"
- You should reference this page on Android keycodes for easy editing.
- After editing the file, save and exit the text editor.
- Open your file manager and delete /system/usr/keylayout/gpio-keys.kl
- Copy /mnt/sdcard2/Backups/gpio-keys.kl to /system/usr/keylayout
- Finally, relaunch Android with the "Kill Android" app.
- Finally, confirm the key remapping.
Unfortunately, the coding for the nubs is incomplete. Right_Nub_Down is mapped to Keycode 82 and Right_Nub_Left is mapped to keycode 4 but other than that, the nubs have no key functionality and so as far as I can tell, you can't change what they do. If anyone wants to look around and see if they can find a way, please post in the thread.
KeyTest is a useful program that tells you the keycode for the key you're currently pressing.