I finally figured out (aka hacked) how to deploy JAD and JAR files to N-Gage via USB cable (Yes, that's right. You don't need to purchase one of those USB Bluetooth adapters. And yes, you can use your file manager).
The trick is to find which file system (or directory in Windows sense) the files should be downloaded to. There is a small modification to do as well as some configuration settings.
Here is the steps:
1. Plug in your N-Gage gamedeck to PC using USB cable; If you are using Windows XP, it should bring Explorer up (or a menu to ask you if you would like to do so).
2. Enable Hidden Files View on Explorer (Tools > Folder Options > View > Advanced settings > Files and Folders > Hidden files and folders > Show hidden files and folders); Refresh your Explorer and you should see a directory called System.
3. Create a directory under System\midp named $MIDlet-Vendor (where $MIDlet-Vendor should be the same as defined in the JAD file);
NOTE: Now, this is the trick. Due to N-Gage strict file naming convention, it will replace "." with "_09" character instead (fair enough as the OS relies heavily on the file extension and from the look of it, the OS uses simple parser to extract this). So, if your MIDlet-Vendor is Create.AU then the directory name should be Create_09AU and so forth.
4. Create a directory under System\midp\$MIDlet-Vendor named untrusted; This is the case if you don't sign your package, but that's trivial.
5. Create a directory under System\midp\$MIDlet-Version\untrusted named $MIDlet-Name (where again $MIDlet-Name should be substituted with your MIDlet-Name as defined in the JAD file);
NOTE: Again, file naming rule is still applicable. Spaces are okay AFAIK.
6. Create a directory under System\midp\$MIDlet-Version\untrusted\$MIDlet-Name named $MIDlet-Version (where again it should correspond to the JAD file);
7. Copy your JAD and JAR files to directory System\midp\$MIDlet-Version\untrusted\$MIDlet-Name\$MIDlet-Version.
NOTE: The JAR file name must be the same as $MIDlet-Name.
8. Create a file using Notepad (under Windows) named $MIDlet-Name.ini (the extension must be ini) and then copy it to the same directory. The content of the file should be as follows:
9. Create two files using Notepad (under Windows) named StartInstallFile.midp and CompleteInstallFile.midp and copy them to the same directory. The content can be left blank. These files stored pre- and post-installation scripts respectively.
10. Unplug your gamedeck and go to Menu > Extras > Applications and WHOLAA you should see your J2ME application (CLDC 1.0 and MIDP 1.0 conformance) installed.
That's all folks! Hope this help. Please add more information should you possess some.
"I am under no responsible and whatsoever for any damages and will not claim responsibilities should anything go wrong with your gamedeck. Please consult your manual or else try to be risk-seeking human being for once "