Digitalic - Test Reports

Installed Android Exporter (Beta 4) following Yves' instructions. I already had the relevant SDK & JDK installed as I had been testing the Android SDK with Eclipse, so it was simply a matter of installing the Android Exporter, creating a simple test application and pointing at the correct SDK/JDK folders on the first build.

Actually, that is where I first came unstuck! I failed to read the second dialog box correctly and pointed at the JDK folder againn, so I had to supply the correct folder in the MMF preferences dialog!

I am testing on the Asus EEE Pad Transformer running Android 3.0 (Honeycomb).

My first, simple application (just bouncing an active around the screen) works perfectly. Initially, I used the emulator, but it is so slow that it is impractical to use. I connected my EEE Pad via USB (I already had the USB debugger enabled) and tested my app on the device. Again, it worked perfectly.

I have also installed an apk by emailing it to my EEE Pad, downloading it, and using "appInstaller" to install it. Again, no problems there.

During the week ending 13/05/11, I plan to familiarise myself with the basics of tablet-centric features such as Accelerometer, Location, Multi-Touch, etc, so I can test them and report back during the weekend.

Test Device: Asus EEE Pad, Android 3.0

Initial testing is going well. Noted issues below:

Possible Bugs
-------------
Date & Time Clock doesn't render correctly.
List object renders strangely.
Frame transition causes application to "stop unexpectedly".

Notes
-----
In application properties, Minimum Android version - no 3.0 option

I have created an active object which moves around the screen using the the accelerometer to detect the tilt. The active object is moving smoothly and apparently accurately, but when I create another active object that is always 'following' the main object, there is significant lag which varies depending on the speed of the original active object. The 'following' is achieved by always setting the X&Y coordinates of the follower to the coordinates of the main active object.

No facility to angle or scale objects, but I think that this is already known.

Questions
---------
Can MMF apps be configured to allow me to use the Android 3.0 settings button on the Android System bar?

How do I specify to hide the Android "System bar"?

Is it possible to add "Notifications" in the system bar?

Is it possible to add "Action Items" to the system bar?

Help file corrections
----------------------
"Emulators" help available, but feature does not exist.
Typo in Android help. Under "Release mode", "certificat".
iPhone Joystick Device should refer to Android.

Hope that helps. If you require more detailed information about the above issues, please let me know; I didn't want to repeat previously noted bugs.

Test Device: Asus EEE Pad, Android 3.0

I can only get a single sample to play, then no further samples are heard. I have tried playing the same sample multiple times and playing different samples, but only the first instance of the request to play a sample is heard; all others seem to be ignored.

Test Device: Asus EEE Pad, Android 3.0

I've done a simple test with the multi-touch object where an active follows a single touch around the screen. It's surprisingly fast and the lag is no different to dragging an item around on the Android home screen (i.e. it's virtually imperceptible).

The next task is to test several simultaneous touches.

I haven't had a single crash on the Android platform and the testing process is quite fast; about 20 seconds from selecting "Build and Run" to getting the application running on the device.

I am having trouble getting more than a single touch working properly.

I'm using multitouch as shown in the code block below. [active 1] is the active object, [MT] is the multitouch object.

Code:

---

Touch  0 is active
  [active 1]:Set X position  to XTouch("[MT]",0)
  [active 1]:Set Y position  to YTouch("[MT]",0)

---

The above code works just fine, but if I add a second multitouch condition, e.g...

Code:

---

Touch  1 is active
  [active 2]:Set X position  to XTouch("[MT]",1)
  [active 2]:Set Y position  to YTouch("[MT]",1)

---

... the second active object [active 2] does not follow the touch; it just 'jumps' to it whilst the first touch continues to work as expected.

Am I using the multitouch object correctly?

Are you building for 1.6 or 2.1? (application properties)

I have set the "Minimum Android" property to 2.1.

Test Device: Asus EEE Pad, Android 3.0

Basic testing of virtual joystick successful; functions as expected. Not tested fire buttons yet.

Also, tried rebuilding multitouch testing from scratch in a new project. Same problem occurs; first touch registers perfectly, allowing dragging of an active, but second and subsequent touches do not allow an active to be dragged; the active just jumps to the point at which the touch was initiated.

I'm still here! I had to put Android testing (and just about everything else in my life) to one side due to personal commitments, but I hope to spend some more time on Android Exporter testing over the next few weeks.

The main change for me is that the 3.1 update for the Asus Transformer EEE Pad has been released, so I am now on 3.1. I'll be testing my existing MMF2-created apks to make sure that nothing has gone awry!

I have installed StephenL's Dialogs extension which works well and looks great (thanks for that).

I am currently working on the location object and am about to take my tablet out for a drive to test the code. I will report back later!

A quick update...

I've installed Beta 5 and have tested the rotation feature. It works, but sometimes when an active object rotates it flashes! I'll provide more detail in another post.

I'm moving home next week, and my PC is being packed away at the weekend. I may not see it again until the end of September so, clearly, I won't be able to provide any test reports until then!

If the Android Exporter is still in testing at that time, I'll be pleased to rejoin the beta programme, and will be able to dedicate some more time to it.

If you are going to the Click Convention, you'll recognise me; I'll be the one shaking as a result of withdrawal symptoms.

Good luck with the development & testing of the exporter; I'll be following the forums, and I'll definitely be buying the Android Exporter when it is released!