LiveCode Forums.

I have been a runrev supporter and subscriber for a number of years. I was in need of a good project in order for me get really serious about using RunRev. I have a windows 64 machine and I am testing RunRev 5.5. I am having problems with the Android development pkg. I have given up on the simulator - it's way to slow and very unreliable. I am using by Asus T101 but I can't get the programs to compile and run on my android device. I am almost certain that it is not the tablet, it shows up in the developer list. I am getting the following error message:Installation of app failed: adb server is out of date. killing....ADB server didn't ACK *failed to startdaemon * error:
this is all contained in a message box. HELP!!!

Clarence

If you have updated all android components so that you're current you might try this..

1st on the command line manually try to kill the adb process. (adb kill-server).. Depending on the version of android the adb binary could either be in platform-tools folder or.. um. Well I forget so you may have to look for the other location.

2nd, if on windows try to kill the process using tasklist. Look in processes for adb.exe If its there kill it. If on a mac, you can do a ... I think its ps -ef to see all processes (bad memory but I THINK that will do it) see if adb is a running process (could do ps -ef |grep adb) if its running do a kill -9 processid

3rd start adb again from the command line. (adb start-server)

Not sure what else it could be but if I run across anything i'll post it here.

Thanks.
I actually had this stuff running once, but I can't figure what happened.
I have actually uninstalled the Android SDK and will re-install it.
If the problem pops up again, I will try your suggestions.

I had a similar problem when I was testing apps on my Android phone. Here's what I did.

I put the compiled app in my Dropbox folder. Then from my phone, I opened up Dropbox,
clicked on the compiled app, it installed fine.

OK.
My solution:
After many tries- Un-installing Java, Android SDK, etc......
I found my problem. The ADB.exe in my Asus folder was the program that was out of date. I removed the ADB.exe in the Asus folder and replaced it with the ADB.exe that was in the Android SDK folder.
All solved - what a PITA (Pain in the Ass) this was.
NOW I'M HAPPY! and get on with my life.

Clarence

Probably a bit late but I found this:
http://visualgdb.com/adbfix/
Took care of my adb server error with 2 clicks.

HTH
Simon

I have had to solve this problem a couple times.

Thanks for the information.