Porting Me and My Shadow to Android

[acme_pjz]

Hi everyone,

After two days of work I managed to build Android version of all dependencies of MnMS, and the game itself. It runs on my phone, but unfortunately SDL Android doesn't support 32bpp video surface, so the graphics doesn't display at all Now I need to check if changing it to 16bpp works Maybe a lot of code in the game should be changed, too

[acme_pjz]

Finally, it works The document of SDL 1.2 Android port is frustrating and confusing It said that we should use SDL_SWSURFACE and 16bpp in the code and use software mode in the config file, but maybe it's wrong because I can only get black screen And there http://www.anddev.org/code-snippets-for ... 8-270.html also said that

The corrent one is use SDL_HWSURFACE and 32bpp (?) in the code, but use software mode in the config file. Then it works

There are some photos:

The next thing to do is improve UI and performance (currently it runs smoothly on my Samsung Galaxy SIII except for the fading screen), after V0.5 release

[Edward_Lii]

Hello acme_pjz,

Finally, it works

Great work, it looks awesome.

The next thing to do is improve UI and performance (currently it runs smoothly on my Samsung Galaxy SIII except for the fading screen), after V0.5 release

There are quite a few things UI wise that could be improved.
Although I think the level editor will never be practical on a hand-held device.

[acme_pjz]

In order to compile it, the name of findlocale.c must be changed to findlocale.cpp and change some code in it I don't know if it's OK to change SVN version to that?

[Edward_Lii]

Hello acme_pjz,

In order to compile it, the name of findlocale.c must be changed to findlocale.cpp and change some code in it I don't know if it's OK to change SVN version to that?

Depends on the changes that need to be made.
Renaming the file is completely fine, so feel free to make the needed changes.

What I would like is to keep track of the changes we make/made to the bundled libraries.
Preferably a text file stating the source and license of each library and patch files.

There is however a small problem with the included md5 code.
The license of the code segment seems quite permissive and might be DFSG compliant, but I'm not sure...
As far as I can see the code is in Debian's curl package and no patch file is changing/removing it.

Anyway, maybe I'll try to compile it and run it on an android devices myself if I find the time for it.

[acme_pjz]

Hi Edward_Lii,

About the changes to the bundled libraries, I'll upload it soon to SourceForge "Files" tab first, but I'm sure if I should upload it to SVN

EDIT: I have uploaded it here: http://sourceforge.net/projects/meandmy ... y/download Somehow the file name is incorrect, at first I want to create a "android_dependency" folder The actual file name is "mnms_android_dep_src.7z"

There is however a small problem with the included md5 code.
The license of the code segment seems quite permissive and might be DFSG compliant, but I'm not sure...
As far as I can see the code is in Debian's curl package and no patch file is changing/removing it.

Maybe we should write some comments says that this code is taken from libcurl md5.c, it is in turn taken from MD5 reference implementation (not sure)

Anyway, maybe I'll try to compile it and run it on an android devices myself if I find the time for it.

You can check the uncompleted instructions here http://meandmyshadow.sourceforge.net/wi ... on_Android

[acme_pjz]

SDL_HWSURFACE and 16bpp makes the game runs a lot faster with slightly inferior graphics

[Edward_Lii]

Hello acme_pjz,

Maybe we should write some comments says that this code is taken from libcurl md5.c, it is in turn taken from MD5 reference implementation (not sure)

After some searching I came across this: http://sourceforge.net/projects/md5deep/
The project is licensed under public domain so we can do with it what we want.

I will try and extract the md5 code and implement it into meandmyshadow.
Should this become the default method, or should we still depend on openssl?

EDIT: I have uploaded it here: http://sourceforge.net/projects/meandmy ... y/download Somehow the file name is incorrect, at first I want to create a "android_dependency" folder The actual file name is "mnms_android_dep_src.7z"

I see, there are quite a few changes and to libraries that aren't really bundled with meandmyshadow at the moment.
We need a way to separate desktop and android development in a clean way.

What could work is creating a new separate svn repository for the android libraries and configuration files.
That way the main repository will not contain android specific files like the appsettings and icon.

[acme_pjz]

Hi Edward_Lii,

I will try and extract the md5 code and implement it into meandmyshadow.
Should this become the default method, or should we still depend on openssl?

I think your code has some obvious mistake. Did you test your code? I fixed it in latest SVN.

I see, there are quite a few changes and to libraries that aren't really bundled with meandmyshadow at the moment.
We need a way to separate desktop and android development in a clean way.

What could work is creating a new separate svn repository for the android libraries and configuration files.
That way the main repository will not contain android specific files like the appsettings and icon.

If we separate a new SVN then it's hard to make the code up to date IMHO there are only some #ifdefs and two additional files which are only a few KBs. For the dependency libraries, because it changes not so often, so IMHO we don't need to put them into SVN, and let the developers download them on SourceForge.

[Edward_Lii]

Hello acme_pjz,

I think your code has some obvious mistake. Did you test your code? I fixed it in latest SVN.

Oops , not sure how that method slipped in.
I have it corrected in a test case but must have copied over the wrong one...
Anyway, it seems the MD5 method is never called/used.

If we separate a new SVN then it's hard to make the code up to date IMHO there are only some #ifdefs and two additional files which are only a few KBs. For the dependency libraries, because it changes not so often, so IMHO we don't need to put them into SVN, and let the developers download them on SourceForge.

I didn't mean making two different svn repositories for the code, but only for the Android specific files.
But you're right that the libraries shouldn't change that often.

[acme_pjz]

Unfortunately, addons doesn't work on Android even if wifi is connedted, it just freezes

[Edward_Lii]

Hello acme_pjz,

Unfortunately, addons doesn't work on Android even if wifi is connedted, it just freezes

What svn revision did you try?
I have an older version and addons seem to work quite fine.
The only problem I've encountered so far is that although themes install and are detected, they don't seem to work.

I'm going to test the latest svn soon.

[MCMic]

You should consider adding M&MS to Fdroid : http://f-droid.org/

[johnamaro]

Finally, it works The document of SDL 1.2 Android port is frustrating and confusing It said that we should use SDL_SWSURFACE and 16bpp in the code and use software mode in the fmwhatsapp config file, but maybe it's wrong because I can only get black screen And there http://www.anddev.org/code-snippets-for ... 8-270.html also said that

The corrent one is use SDL_HWSURFACE and 32bpp (?) in the code, but use software mode in the config file. Then it works

There are some photos:

1.JPG

2.JPG

The next thing to do is improve UI and performance (currently it runs smoothly on my Samsung Galaxy SIII except for the fading screen), after V0.5 release

I hope you have found the solution to this problem but if you doesn't so If you doesn't any Java then Kotlin is also supported by Android Studio. Kotlin's Syntax is definitely easier to learn and if it is a straight forward app. Then with enough time put in a month is feasible. Its worth looking at, at the very least.

To clarify the two options at least for native support are Java and Kotlin. I'm not sure if there is a 3rd party solution for porting it over.