Build and Run only Builds then hangs

The same thing did happen to me all the time on a previous install, and on another computer. The apk built fine, but MMF freezed. Yves investigated it during the beta period, but I am not sure if he found out what caused it. It started happening when I debugged using a second device, but that may have been coincidence.

Are you able to use the file - build and then upload the APK to your phone?

This happened to me when I was using 'Build and Run' on my tablet which didn't have any device driver support so the Android SDK was unable to send it to my device. Try just building the application as an APK and then manually transferring it to your phone. If the busy cursor is showing and the loading bar at the bottom remains full then MMF2 has done it's job of building the APK it's just waiting on ABT sending it to the device.

The Android Dialog object is still in beta stage and so various devices may not work etc.

Kung -- One interesting thing to try

Inside your Android SDK folder then inside the tools folder
Run Monitor.exe

This should show the Android devices you have connected to your computer.

What I am interested in knowing is --- Does your device show up in there?
If not -- That would explain why MMF can not do build and run
If yes -- then I wonder whats going on

I had this problem after I installed Bluestacks. Make sure Bluestacks is not running when you connect your device.

Are you sure you downloaded and installed the driver for tablet?
Its something you have to get from the makers of the tablet and then also turn on USB debugging on the tablet to make everything communicate with each other.

Is your device rooted? I couldn't get USB debugging to work on my Galaxy Tab so I downloaded an app called Wifi ADB which let me do it over wifi, which works rather well. To make sure what devices are connected, go to your Android SDK folder (for me it is C:\Program Files (x86)\Android\android-sdk ) then hold shift and right click on the folder called platform-tools. There will be an option that says "Open command window here". Once the command prompt loads, type adb devices to see which devices are loading. If there is one device, it should work. Zero means your device is not connected, and more than one means MMF doesn't know which one to build the file to. If there are too many, you can type adb disconnect [name] where [name] is the optional name of the device you want to disconnect and leaving it out will disconnect all devices. Then just reconnect the device you want to use and it should work. You can check again by running adb devices at any time to see what's connected.

If it still doesn't work after checking USB Debugging, try to get a driver from your manufacterer : Please login to see this link.

Just a little Addition for Kungsangun's Question: "So the "Build and Run" command is only for attached devices and not for the MMF development environment?"

Well, the "Build and Run"-Command can also be used with the Android-Emulator (can be accessed in the Android-Settings of the Programm/App). Run the Emulator (can take a while to load) and after the Emulator has loaded completely, click on "Build and Run". It should export the APK directly to the Emulator. (At least that' s what worked for me). It' s a little bit Annoying that You have to close the small Window from MMF2 that' s needed to start the Emulator before you can use the "Build and Run"-Command.

But as already mentioned, it' s better to Test on a Real Device than on the Emulator because the Emulator is relatively slow.

I hope this also helps a little Bit.

With kind regards,

jahkri

I had the same problem and installing the drivers worked well (as stated by Yves before).
I have now to figure out what needs most resource with the DDMS. Any tips about this tool?
Please login to see this attachment.
Please login to see this attachment.
I am pretty sure that it is graphics but I want to be sure before beginning with a huge optimisation.

I am also having problems getting my tablet to connect using the USB cable, MMF2 just locks up after creation of the APK file.

I have a NATPC M009S 7" Tablet with Android 4.0.3, I am using an Windows 8 Ultrabook, the device manager says, "No drivers are installed or required for this device"

WiFi ADB is working for me too.

Build & run randomly stopped working for me the other day- found out it was because there wasn't enough space left on the internal memory on my device.

My Samsung Galaxy Tab 2.7 is does not appear on Monitor.exe (Android/Tools) but my MMF2 builds the apk file ok. I have tried updating my tablet drivers from Samsung site. Has anyone any suggestion which driver to download? My Sony Xperia U phone does not appear either. I have turned on USB debugging on the Tablet. The tablet appears in MyComputer as GT-P5100.
I have installed Android 4.2.2 (API 17) and Android 4.0 (API 14)

How do I manually port my apk file to my Tablet. I can access my tablet in Windows Explorer. Where should I put the apk file?

Keli

Inside your Android SDK folder then inside the tools folder
Run Monitor.exe

This should show the Android devices you have connected to your computer.

What I am interested in knowing is --- Does your device show up in there?
If not -- That would explain why MMF can not do build and run
If yes -- then I wonder whats going on

Dropbox is a great little app -- for going around this issue
You can build your APK to dropbox then open dropbox on your device and click it - It will then install to your device.

Hi

I uninstalled Android SDK tools. Then reinstalled only Android 4.0 (API 14) not also Android 4.2.2 (API 17) . Then everything works perfectly. I now see my tablet in Monitor.exe (by running the batch file) and it builds to my tablet! Now it would be very nice if Clickteam could set up some examples for one to look at.

best wishes,

What would you like some examples of?