Modern Alchemists ShiVa Libs is a bundle of custom written ShiVa addons. All projects rely on ShiVa 1.9 and UAT 1.2 beta 7. This doesn’t mean it won’t work with older versions, but the docs might refer to code hockups which weren’t present back then.

All code is under LGPL License. If you like our work, tell us! If not, tell us even more! Got a code fix? Tell us… you get the idea

It features:

• MASS: In-App-Purchase for iOS and Android
• MAOF: OpenFeint for iOS and Android
• Mortar (TBA): automating the world!

You can get all the files/code either from the download section or via SVN at  google code: http://code.google.com/p/ma-sh/

The answer why your VM crashes is, that the heap space trying to be allocated is not free in physical memory.

That means: try to decrease the setting for max heap space in the file android-sdk-windows/platform-toolsdx.bat to smaller value. I had to change it to 512M instead of 1024M, meaning:
set defaultMx=-Xmx512M

And tada, off you go!

Update Feb 10th: I’m doing some tests with the new domain. Currently it’s running, but not as intended to (still got some frame-issues which I don’t want). So in case you see some missing GFX or so, it’s me testing

If you want to be able to just drag and drop your APK file onto a CMD file, and let it be installed on the connected device automatically, use something like this (simply copy this to your *.cmd file):

New:

:: Just some debug output:
echo Attempting to install file: %1
 
:: Enter drive letter:
d:
 
:: Enter path to adb here:
cd D:\android_sdk on 10.17.1.205\platform-tools
 
:: Install file:
adb install -r %1
PAUSE

Old:

:: Just some debug output:
echo Attempting to install file: %1
 
:: Enter drive letter:
d:
 
:: Enter path to adb here:
cd D:\androidsdk\tools
 
:: Install file:
adb install -r %1
PAUSE

PS: Of course one could use set varNAme=__PATH__ instead of the cd-ing, but my path has some spaces and that leads to troubles.

Like shown above, type in ‘telnet‘ and press enter. The result will look like:

Here type in ‘o localhost 5554‘ as shown here:

This will establish a connection to the emulator.
You can see the port number to be entered in the title bar of the emulator window.
If this succeeds, it will open the Android Console:

Here you can use all kinds of commands.
To simulate a call, type ‘gsm call 066712345‘:

The result is an incoming call at the emulator:

To cancel the call, type ‘gsm cancel 066712345‘.
See http://developer.android.com/guide/developing/tools/emulator.html#telephony for more information about gsm operations.

Use ‘exit‘ to exit the Android Console and ‘quit‘ to quit telnet.
Hope that helps!

[2010-08-16 19:56:41 - xxx] ------------------------------
[2010-08-16 19:56:41 - xxx] Android Launch!
[2010-08-16 19:56:41 - xxx] adb is running normally.
[2010-08-16 19:56:41 - xxx] Could not find xxx.apk!
[2010-08-16 19:58:04 - xxx] ------------------------------

after importing a project (maybe doing some reconfiguring), just remove the project (only the project from Eclipse, not from disk!).
Then simply re-import it and it should work again!

Update March 14th: according to Sean, you can get this error also by having the emulator already running and changing the project SDK. The solution then is to close the emulator and run it again from eclipse. Thanks for the info!

I also stumbled over this interview.
Wow! If only part of this is true, I can’t wait for it to be released! Unfortunately, the PC release seems to be delayed and a new date has not yet been announced.