LiveCode Forums.

I have hooked the Android Studio up with LiveCode successfully, but whenever I connect my Android device to my computer and try to test a stack on it, it does not work.

Yes I configured the Standalone Stack Settings for deployment.
I'm running on Windows 8.1
LiveCode Indie 7.0.4

I successfully installed the Android SDK and it works fine. Idk why this isn't working.

Is the device connected with USB debugging enabled?
Is the device connected before you start LiveCode? I find if I am developing and want to attach the phone, I need to close LiveCode, connect the device and set USB debugging (every time) and then I can restart LiveCode.

I just tried that and it did not work.

Hi 7leven,
You haven't mentioned if your device shows up as a Test Target?
And that you have selected it.

Simon

Simon wrote:Hi 7leven,
You haven't mentioned if your device shows up as a Test Target?
And that you have selected it.

Simon

My device does not show up as a test target.

The device is plugged in, recognized by my PC, and debugging is on.
Android Studio is linked with my LiveCode application as well.
Likewise, I have saved the standalone application stack settings, and the Test or Test Target option is still gray and I am unable to press either.

Try killing any adb.exe running in the process list. Restart LiveCode and try the test target again. I had a problem with a Sony Mira phone, that needed extra driver installation to work, even though windows could find it as an external storage device and read the SDcard.
As well as the USB debugging option, you have set permission on the phone to run apps from sources other than the Play Store, haven't you?

SparkOut wrote:Try killing any adb.exe running in the process list. Restart LiveCode and try the test target again. I had a problem with a Sony Mira phone, that needed extra driver installation to work, even though windows could find it as an external storage device and read the SDcard.
As well as the USB debugging option, you have set permission on the phone to run apps from sources other than the Play Store, haven't you?

How do I enable my phone to run apps other than those from the Play Store?

Ok I figured out how to allow apps to download that aren't from Google play. But when I tried it, along with everything else I should of done . (i.E closing LiveCode, plugging in my phone with debugging enabled, and then opening LiveCode again) and it still didn't work. I also closed any processes with the name abd.exe and still no luck.

You need Google USB drivers: http://developer.android.com/sdk/win-usb.html

MaxV wrote:You need Google USB drivers: http://developer.android.com/sdk/win-usb.html

I just checked Android Studio and I've already installed that too..

Does anyone have an idea what my problem is?

Not really, all the usual things have been mentioned in this thread.
It must be something specific to your setup. If there is only greyed out options in the Development menu for Test and Test Target then the thing I suspect most is the connection with your specific device to the PC. Using Windows, can you browse to the devices storage folder? If you can, then look for other connection settings options - some devices will offer "connnect as installer, or connect to transfer media, or connect for charging only" type options. Try to ensure that the installer option is used. Chances are that if you can get to the files on the device it's in the wrong "connection type". In the "Devices" section of Windows can you see the device listed by name and type? or just generic "Android". It might be that you need to install the manufacturer's specific connection software in order to get the full drivers installed (not the same as the google usb drivers). If Samsung you might have to install Kies, for instance.
Other than that, I don't know what else to try, without seeing the specifics you have. Can you set up a device in the simulator and does that work as a selection in the Development menu? If you can, it's a phone specific problem. If you can't, I think it will be the SDK installation that's the problem.

Hi 7leven - it may be that the lazy way I get my apps to run on Android devices will be of use to you...

I also sometimes get devices (such my current nexus4) which just doesn't like connecting to my mac - and a while ago I gave up trying to keep it as a 'test target' started deploying to it directly using a little 0.88 pence app called "Wifi Transfer Pro" (https://play.google.com/store/apps/deta ... o&hl=en_GB)

With this I can build a standalone in LiveCode, switch to Chrome (where I have a page already set up that connects to my device) and from there download the .apk file to the device and install it. It's not quite as fast as downloading via cable, but not by much - and it is so handy that now I don't bother even trying to set up Android devices as 'test targets'

If your problem is only to do with getting your Android device and your development machine to recognise each other then it may be that using a wifi connection could bypass the need for a direction connection and allow you do carry on...

I have no idea if this will work in your situation and am just letting you know in case it helps...

NOTE: I don't have an connection with 'Wifi Transfer Pro" and I should think other similar apps would also work for you

Good luck!

Dave

dave.kilroy wrote:Hi 7leven - it may be that the lazy way I get my apps to run on Android devices will be of use to you...

I also sometimes get devices (such my current nexus4) which just doesn't like connecting to my mac - and a while ago I gave up trying to keep it as a 'test target' started deploying to it directly using a little 0.88 pence app called "Wifi Transfer Pro" (https://play.google.com/store/apps/deta ... o&hl=en_GB)

With this I can build a standalone in LiveCode, switch to Chrome (where I have a page already set up that connects to my device) and from there download the .apk file to the device and install it. It's not quite as fast as downloading via cable, but not by much - and it is so handy that now I don't bother even trying to set up Android devices as 'test targets'

If your problem is only to do with getting your Android device and your development machine to recognise each other then it may be that using a wifi connection could bypass the need for a direction connection and allow you do carry on...

I have no idea if this will work in your situation and am just letting you know in case it helps...

NOTE: I don't have an connection with 'Wifi Transfer Pro" and I should think other similar apps would also work for you

Good luck!

Dave

Actually, Dave, this is another problem I need help with as well.
Because like you, I thought maybe if I just compiled my project as a standalone application for Android, and sent the files to my phone, I could run them. BUt whenever I try that, my phone tells me "There was a problem parsing the package". It does this for all applications I try to test on it.

MaxV wrote:http://developer.android.com/tools/extr ... lingDriver

Max, I'll try this, thank you. As I have a OnePlus One, there aren't actual drivers for it but when I Google it all my sources tell me to use Samsung drivers. So I'll do that.

And as someone mentioned before, the emulators also do not work on my PC, although I'm sure I've installed everything correctly. I just got my new laptop so maybe I'll try everything on there and if it works then I'll start using that as my development hub.