Fusion2.5 locking up when trying 'Build And Run'

Im having this problem:
http://community.clickteam.com/threads/83325-MMF-locks-up-when-building-Android-apk

Fusion locks up at 100% when using 'Build And Run' ( happens regardless of Android Device being connected or not ).
After this i have to force quit Fusion and reboot my PC, as Steam thinks Fusion is still running ( cant reopen Fusion and cant close STEAM ).

I have installed the driver posted by Simon, rebooted but the issue is still there.
I have not uninstalled the original drivers however, as i dont know how to do so.

Anyone know how to uninstall curent/ previous drivers?
Anyone else having this issue?
Other suggestions?

EDIT: As the issue ocurrs regardless of Device being connected, is it safe to assume the problem is not with the driver?

If you use build and run with no device connected it will always hang. If you can succesfully build an .apk but not use build and run, it's likely a driver / connectivity issue.

I'd try reinstalling the google usb drivers in the Android SDK manager. Also make sure you device is set to developer mode and usb debugging / unsigned apps etc. is all set up correctly.

Navigate to your android SDK folder, then to Platform Tools folder, then hold shift+right click in the folder and open a command window. Type "adb devices" and any detected devices will be loaded up.. if nothing is detected, it's definitely a driver issue.

- I can build .apk file without Fusion hanging

- Deleted 'Google USB Drivers' from Android SDK
- Installed 'Google USB Drivers' from Android SDK

- Checked 'Allow Applications from unknown sources' ( was on )
- Checked 'USB debugging' ( was not on, set it to on )

^ Issue still persists

...
Did the "adb" thing 1st time and got a strange message ( see image ).
Did it a second time and nothing was listed ( see image ).
https://dl.dropboxusercontent.com/u/...%20devices.PNG

...
So this is definitivly a Driver issue then?

This driver stuff confuses me.
When deleted/ installing the 'Google USB Drivers' from the Android SDK, havent i reinstalled the USB drivers ( i have allso installed the driver thigie in the Sticky by Simon )?
or it is some other driver thats not working?
( my device does pop up with autorun when connected, and i can access it )

you could try this guide - http://www.makeuseof.com/tag/android...t-three-steps/

or wait for someone else who might be able to help.

My Device is a Samsung Galaxy ( software up to date ).
So this is what has ben done:

#1
- Device: Unknown Sources = CHECKED
- Device: USB Debugging = CHECKED

- Deleted 'Google USB Drivers' from Android SDK
- Installed 'Google USB Drivers' from Android SDK

^ Issue persisted

- Doing the 'adb devices' thing yielded this:
https://dl.dropboxusercontent.com/u/...%20devices.PNG

...

#2
Followed this 3 Step guide ( http://www.makeuseof.com/tag/android...t-three-steps/ )
- Connected Device + uninstalled driver from 'Device manager' + Disconnected Device
- Removed bad drivers using this Nirsoft tool ( http://www.nirsoft.net/utils/usb_devices_view.html )
- Installed Universal USB Driver ( provided in the 3 step guide )
- Rebooted + Connected Device ( 'Samsung Android ADB Interface' present in Device Manager ) + Tested 'Build and Run' button
^ Issue persists

#3
Followed 2 steps of this 3 Step guide ( http://www.makeuseof.com/tag/android...t-three-steps/ )
- Connected Device + uninstalled driver from 'Device manager' + Disconnected Device
- Removed bad drivers using this Nirsoft tool ( http://www.nirsoft.net/utils/usb_devices_view.html )
- Installed Samsungs USB Drivers ( http://developer.samsung.com/technic...o?v=T000000117 )
- Rebooted + Connected Device ( 'Samsung Android ADB Interface' present in Device Manager ) + Tested 'Build and Run' button
^ Issue persists

...

When i now do the 'adb thing' i get this:
https://dl.dropboxusercontent.com/u/...evices%202.PNG

Looks like there is something wrong, or is this the way its supposed to look?

...
Another thing i notice is, after installing different USB Drivers in #1 and #2 above its still the same Driver listed in the Device manager ( 'Samsung Android ADB Interface' ).
Does this mean that the 'Samsung Driver' takes controll regardless of what USB driver i try t oinstall, or is it supposed to be like this?

Ive made sure to run everything applicable with Admin Priveleges ( by right clicking -> Run as Admin, or whatever its called )

Also, after #1 above i didnt uninstall the 'Google USB Drivers' from the Android SDK.
Does this mean i have 2 sets, potentially conflicting, USB Drivers? Or is the 'Google USB Drivers' something entirely seperate?
How can i make sure, so i know im starting of with a clean slate, that all USB drivers are uninstalled?

Yet another thing, even after uninstalling/ removing everything ( step 1 and 2 in the 3step guid ) when i try to run the 'Samsung Driver Installation' it says that its allrready installad and asks me if i want to insall it anyway.
Is this normal, or is there a conflict here?

...
I would very much want this to work, any input would be appreciated.

...
EDIT:
As i finished writing this, i noticed something new on my Device.
It asked me if i wanted to trust this computer for debugging or something, and i choose OK and Fusion stoppe hanging! :D
I tested again and same thing happened! :D

...But... Isnt the app supposed to automatically pop up and run on my device at this point? Or am i missing something?

does the build finish at least? often times for me, the build and run will successfully build the app but hang on a black screen at start, if I force quit the app and run the apk that was put on the device then it'll work.. sounds like you're getting close though!

Yes its like small incremental steps, with problems queuing up infront of me as i go
But im getting there

Im now stuck after creating the keystore file, with an error log stating:

Signing key TESTAPPLICATION not found

And no the build does not finish, the apk file does not get created

...
Is the keystore file required to test the application on the connected Device though?

no, you don't need to do anything with the keystore until you're ready to release the game. I've never used the keystore stuff - even having gotten to the stage of cloud testing on google play.

K, so unchecking the 'release mode' makes the 'Build and Run' button work without error messages.
The .apk also gets built, but noting popps up on my connected Device ( conected, is accesable, and software up to date ).
Is this normal, or should the App appear on my Device and run after i hit this button?

question did you enable developer mode in that device and after that did you accept the checksum from your Pc? if not they will always be blank for adb

Yes i have 2 Samsung Devices, have enabled DevMode on both..
Have enabled USB Debugging ( Developer settings ) on both, and also Accept Unknown Sources ( Security settings ).
And yes i have accepted the message asking if i want to trust the computer ( on the Device ) after i click 'Build and Run'.

Nothing happens on either Device.

EDIT: Just to be clear the issue about the .apk not getting built with an error message is resolved. The problem now is that the App doesnt run on the connected Device when pressing 'Build and Run'.

If you run monitor.bat from the Android/Tools folder do you see your phone connected?

I get a window saying:

"An error has ocurred see log file
...eclipse/org.eclipse.platform_4.2.0_2061726483..."

I follow the path and open the log looking like...well its pretty long but ill post just the bottom most paragraph:

"!ENTRY org.eclipse.osgi 4 0 2016-02-01 21:56:47.585
!MESSAGE Application error
!STACK 1
java.io.IOException: The folder "C:\Users\Rami\.android\monitor-workspace\.metadata" is read-only.
at org.eclipse.core.runtime.internal.adaptor.BasicLoc ation.lock(BasicLocation.java:206)
at org.eclipse.core.runtime.internal.adaptor.BasicLoc ation.set(BasicLocation.java:164)
at org.eclipse.core.runtime.internal.adaptor.BasicLoc ation.set(BasicLocation.java:137)
at com.android.ide.eclipse.monitor.MonitorApplication .start(MonitorApplication.java:53)
at org.eclipse.equinox.internal.app.EclipseAppHandle. run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseA ppLauncher.runApplication(EclipseAppLauncher.java: 110)
at org.eclipse.core.runtime.internal.adaptor.EclipseA ppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.ru n(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.ru n(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknow n Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Un known Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework( Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.ja va:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:14 38)"

And the tool of cource opens up:
https://dl.dropboxusercontent.com/u/3537859/MONBAT.PNG

The phone is there, but not sure it looks healthy and there is a ? mark there and of cource the error log.

did you try to run as administrator and check.