PSPKVM: Difference between revisions
From GameBrew
More actions
No edit summary |
|||
| Line 46: | Line 46: | ||
==User guide== | ==User guide== | ||
'''To install and run a MIDlet from the memory stick:''' | '''To install and run a MIDlet from the memory stick:''' | ||
* Select Find Application item in AMS (the item on the top). Then select Install from Memory Stick (ms0:/). | |||
* Browse the file system of your Memory Stick, and select JAD or JAR to run. | |||
* After selected, the JAD/JAR will be automatically installed and run. You can choose the installed application from AMS next time you want to run. | |||
'''Text input and virtual keyboard:''' | |||
* It uses phone keypad mapping as default settings for text input. You can pop up a menu by pressing Right Soft-button to change to other input methods. | |||
* In addition, most MIDlets will invoke your selected virtual keyboard for involved text entry tasks, as these provide for much easier text input. You can enable them in the VM Config midlet in the System Midlets folder. | |||
** AWF virtual keyboard (Default). | |||
** Danzeff virtual keyboard. | |||
** Semichordal virtual keyboard. | |||
'''Text input:''' | |||
It uses phone keypad mapping as default settings for text input. You can pop up a menu by pressing Right Soft-button to change to other input methods. | |||
* AWF virtual keyboard (Default). | |||
* Danzeff virtual keyboard. | |||
* Semichordal virtual keyboard. | |||
'''Multitasking:''' | '''Multitasking:''' | ||
* In any application, you can use the combination keys to send the currently running MIDlet to the background, and the AMS screen will be shown. | |||
In any application, you can use the combination keys to send the currently running MIDlet to the background, and the AMS screen will be shown. | * The backgrounded MIDlet is shown highlighted, and you can choose another MIDlet to run without stopping the previous MIDlet. | ||
* To bring a midlet running in the background to the foreground, just click the MIDlet item from AMS. | |||
The backgrounded MIDlet is shown highlighted, and you can choose another MIDlet to run without stopping the previous MIDlet. | |||
To bring a midlet running in the background to the foreground, just click the MIDlet item from AMS. | |||
'''Connecting to the network:''' | '''Connecting to the network:''' | ||
* Before a Java MIDlet can use the network, you need to connect your PSP to a WiFi hub. To do this, select Network Setup in the AMS (the second item in the AMS MIDlets list). | |||
Before a Java MIDlet can use the network, you need to connect your PSP to a WiFi hub. To do this, select Network Setup in the AMS (the second item in the AMS MIDlets list). | * All the WiFi connections you've set up on your PSP will be listed. Select one and wait for an alert popup telling you the connection attempt has been successful. | ||
* Once the message "Successfully connected by profile xxx" appears, your network is ready, and you can go back to the AMS and run MIDlets that use the network. | |||
All the WiFi connections you've set up on your PSP will be listed. Select one and wait for an alert popup telling you the connection attempt has been successful. | ** For 3.xx OE users, you don't have to set up network in the Network Setup menu. | ||
** When the first MIDlet want to access the network, a PSP network setup dialog will popup and prompt you to start a connection. | |||
Once the message "Successfully connected by profile xxx" appears, your network is ready, and you can go back to the AMS and run MIDlets that use the network. | ** And also, you can call up the network setup dialog at any time with the combination keys. | ||
For 3.xx OE users, you don't have to set up network in the Network Setup menu. When the first MIDlet want to access the network, a PSP network setup dialog will popup and prompt you to start a connection. | |||
And also, you can call up the network setup dialog at any time with the combination keys. | |||
'''Selecting a device to emulate:''' | '''Selecting a device to emulate:''' | ||
* When the user installs a Midlet, a Device Select menu will appear. Choose your preferred device size and model here, and press the Circle key to select it. | |||
When the user installs a Midlet, a Device Select menu will appear. Choose your preferred device size and model here, and press the Circle key to select it. | * If you want to change the preferred device setting, go back to the AMS and move the highlight onto the MIDlet whose setting you want to change, then select Select Device from the menu. | ||
If you want to change the preferred device setting, go back to the AMS and move the highlight onto the MIDlet whose setting you want to change, then select Select Device from the menu. | |||
'''Compatibility List:''' | '''Compatibility List:''' | ||
* [https://netlogin.home.xs4all.nl/pspkvm/pspkvm.htm PSPKVM 0.5.3 OE Compatibility List] (~200 Java games and applications were tested). | |||
[https://netlogin.home.xs4all.nl/pspkvm/pspkvm.htm PSPKVM 0.5.3 OE Compatibility List] (~200 Java games and applications were tested). | |||
==Controls== | ==Controls== | ||
| Line 155: | Line 137: | ||
==Known issues== | ==Known issues== | ||
* Not running on 5.02 Gen-A firmware. | * Not running on 5.02 Gen-A firmware. | ||
* javacall_file_truncate isn't ported, so some file truncating operations, including some RMS operations, may not work as expected. | * javacall_file_truncate isn't ported, so some file truncating operations, including some RMS operations, may not work as expected. | ||
* Multimedia temporary files may be left on your memory stick occasionally, especially after a VM crash. They're usually not big, but if you want to delete them manually, go to your PSP's /PSP/GAME/pspkvm/ directory, find the files whose names look like xxxxxxxx_tmp_mus.mid, and delete them. | * Multimedia temporary files may be left on your memory stick occasionally, especially after a VM crash. They're usually not big, but if you want to delete them manually, go to your PSP's /PSP/GAME/pspkvm/ directory, find the files whose names look like xxxxxxxx_tmp_mus.mid, and delete them. | ||
* Fileconnection rmdir operation may fail for unknown reasons. | * Fileconnection rmdir operation may fail for unknown reasons. | ||
* LocationProvider.getState() will always return AVAILABLE once the GPS is initialized, so LocationListener.providerStateChanged() doesn't work as expected. | * LocationProvider.getState() will always return AVAILABLE once the GPS is initialized, so LocationListener.providerStateChanged() doesn't work as expected. | ||
