Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Install on Device - Android - never works

I've spent quite a bit of time running through the posts here and I've seen a few hints of people having problems, but no real conversation on the topic.

Running Titanium 1.2.1 and attempting to get KitchenSink (or anything) to install on an Android device fails every single time.

There is no error returned. According to Titanium it works. However, nothing ever shows up on the phone.

Tried this from a Mac and from an XP machine. Same result.

Device is set to accept 'insecure' apps, etc, etc.

Can someone please point me in the right direction to solve this?

Thanks.

— asked April 22nd 2010 by Jason Burfield
  • android
  • device
  • install
1 Comment
  • I am struggling with this as well… Works fine in the simulator etc… go to package it and send it to someone to test - just hangs on the splash screen!

    — commented December 21st 2010 by Jay Vark

20 Answers

  • I was having this problem too - trying to deploy from Titanium on a Mac to a Galaxy Samsung S II. Turns out all I had to do was go to Settings>Applications>Development and turn on USB debugging. Titanium found the device like a charm after that.

    As previously mentioned on this thread, it won't launch automatically so you'll have to do that yourself.

    Note that this may interfere with other features on the phone - if you use Kies for example. For full details check this thread:
    http://androidforums.com/samsung-galaxy-s2-international/393624-help-samsung-galaxy-s2-wont-connect-kies.html

    — answered February 24th 2012 by James Wise
    permalink
    4 Comments
    • this worked for me too. thx!

      — commented April 6th 2012 by Bryant Tyson
    • Worked for me also (HTC Hero)

      — commented May 31st 2012 by Matt Hiscock
    • Just to be clear, you go to "Settings > Applications > Development" ON THE PHONE. I spent a few minutes trying to find this in Appcelerator until I figured it out :)

      — commented January 17th 2013 by Tim Holt
    • Worked for me as well. Android testing is SO much easier, faster, and more accurate on the device.(Went out and bought a new android phone cause the android emulator is so..sh-…bad.)

      — commented March 25th 2013 by Jonathan Craddock
  • Hi I had the same problem.

    Make sure that you set the USB connection to "Charge only" or else the application will not install.

    This happens because when the USB connection is set to "Disk Drive" the sd card cannot be mounted to install applications.

    Hope this helps :)

    — answered April 22nd 2010 by Simon Facciol
    permalink
    0 Comments
  • Ya, me too. Till date, I can't get any app to run in the android emulator. My most recent experience is that it will ignore all my splash screen and custom app icon and auto replace with the default Ti ones….

    — answered April 23rd 2010 by Peter Lum
    permalink
    0 Comments
  • My suggestions:

    Locate the APK from the dist folder and direclty copy to the Android phone SD and instlal it using Astro File manager or something else. Can this work?

    — answered February 9th 2011 by Taylor Ren
    permalink
    2 Comments
    • I use this method and it seems to work thanks

      — commented February 28th 2011 by Sid Bachtiar
    • I got a Samsung Galaxy Note N7000 and I enabled USB debugging and allowed apps from unknown sources and even though Titanium Studio says the app was installed, it doesn't show up anywhere in the menus or even under the Applications menu in the device settings. In the end, this is the only method that worked for me. Thanks :)

      — commented October 16th 2012 by Robin Stoker
  • This thread is 2 years old but I'm having the same problem. I installed Titanium a few weeks ago.
    I'm running on Windows 7 Pro 64-bit. My phone is the HTC Google Nexus One running 2.2.
    The phone is set for USB Debugging, Stay awake, Allow mock locations. USB storage is off. Status shows USB connected and USB debugging connected.
    >>> FAIL.<<<
    JAVA_HOME var is defined properly and still fails on Java.
    All my Eclipse based IDEs see my device and can deploy but Titanium.
    Like most people, I have no time to deal with this. What's the solution Appcelerator Team? Titanium to recognize the Android SDK similarly problematic.

    — answered May 30th 2012 by David Kramer
    permalink
    0 Comments
  • Hi I had the same problem.

    Make sure that you set the USB connection to "Charge only" or else the application will not install.

    This happens because when the USB connection is set to "Disk Drive" the sd card cannot be mounted to install applications.

    Hope this helps :)

    — answered April 22nd 2010 by Simon Facciol
    permalink
    0 Comments
  • As Simon mentioned, you can't mount your phone's SD card when you plug in your USB cable. I had trouble when I first started trying to run on the device for this vary reason.

    — answered April 22nd 2010 by Ryan Huff
    permalink
    0 Comments
  • Thanks all. Unfortunately, still doesn't work.

    I have tried it with the device mounted and not mounted. Nada.

    I've tried the update mentioned here, on both Mac and Windows. Still no go.

    Any additional ideas?

    Thanks for the help, do appreciate it.

    — answered April 22nd 2010 by Jason Burfield
    permalink
    0 Comments
  • Do you have USB debugging turned on for your device?

    — answered April 22nd 2010 by Marshall Culpepper
    permalink
    0 Comments
  • Yeah, USB debugging is turned on.

    I have managed to at least get Titanium to spit back an error from the Mac now though. Just says there was an error, nothing really descriptive though.

    It appears 1.2.1 is also having issues with java on my machine for some reason. Actually, on 3 different macs I'm having the same java issues. I believe others are experiencing it as well.

    The windows machine here does not have those java problems, but still does not install.

    — answered April 23rd 2010 by Jason Burfield
    permalink
    0 Comments
  • Anyone want to throw any thoughts out there? Is it time to give up on Appcelerator? I really hope not.

    The unfortunate thing is that we have already practically finished an app using Titanium, however, now we can get anything to work so all that work may be lost.

    We had an app working with 0.8. Then had to re-write for 1.0.

    Now that one is failing due to this situation.

    – Jason

    — answered April 26th 2010 by Jason Burfield
    permalink
    0 Comments
  • I got this. I was having the same issue. I downloaded and reinstalled everything. Come to find out that my device was not in the Android's USB driver install. I have an HTC Eris. I went o HTC's website and downloaded and installed the HTC Sync software on my computer (PC running Vista). See if you actually have your device's USB drivers installed. Android's site does not provide all the devices that run Android. Too many are coming out.
    Also, go to your Build folder in your project, copy the AndroidManifest.xml and create an AndroidManifest.custom.xml and add that in the same place your AndroidManifest.xml is at and changed 'debuggable' from "false" to "true" in your AndroidManifest.custom.xml.
    Finally, make sure you device's settings are USB debuggable "On", Charge Only, and Third Party applications are turned on and allowed.

    — answered June 18th 2010 by Carlos Mosqueda
    permalink
    0 Comments
  • Ti is great for iphone but I have never ever get it to work smoothly with Android. The most I got is to compile and run the app on the android emulator, only to crash on first launch..

    — answered June 18th 2010 by Peter Lum
    permalink
    0 Comments
  • This thread is 7 months old but I'm having the same problem. I installed Titanium a few weeks ago.

    I'm running 1.2.1 on Windows 7 64-bit. The HelloWorld app runs correctly on the emulator. My phone is the HTC Google Nexus One running 2.2. In Titanium Developer, in the tab Test & Package, in the tab Run on Device, I click Install Now. It says "Installing app on device…" for a long time, but nothing happens.

    The phone is set for USB Debugging, Stay awake, Allow mock locations. USB storage is off. Status shows USB connected and USB debugging connected.

    What have I forgotten to do?

    — answered November 10th 2010 by John Dimm
    permalink
    1 Comment
    • Have you added the windows usb drivers. You can also use the ddms tool or adb -d to watch the log during install. You can do adb devices to make sure the phone is visibile to adb before trying to install with Developer.

      — commented November 11th 2010 by Don Thorp
  • Installing the usb drivers worked for me (in my case htc sync)

    — answered December 26th 2010 by Nicolas Mommaerts
    permalink
    1 Comment
    • "usb drivers" - I think I have them installed. CAn you anyway let me know the url you got these drivers from? Thanks,

      — commented January 24th 2011 by Sameer Prabhu
  • Hi there,

    10 months later, I still have the exact same problem of the application not starting on the phone and Titanium doing as everything went fine.

    My phone is in USB debugging mode, allowing mock installations.
    I tried to install the app on the phone both with the USB Storage and without, it did not work…

    My main concern is that it works perfectly with Rhomobile Rhodes, in USB Debugging + USB Storage mode but just doesn't work on Titanium…
    It writes "Installing app on device…" on the top right corner then shows the logo and that's it. Nothing happen on the phone.
    I tried all possible settings on the phone and none of them worked (neither the recommended Mock+Debug+not-usb-storage).

    Windows 7 x64
    Titanium Dev 1.2.2, SDK 1.5.1

    Any help?

    — answered February 9th 2011 by Thomas Dall'Agnese
    permalink
    3 Comments
    • (Oh and I have the usb drivers of course)

      — commented February 9th 2011 by Thomas Dall'Agnese
    • Oh, actually it installs the application successfully, but does not automatically starts the application.
      And indeed it does not start the application because… it doesn't work on the device! It works in the emulator though…

      — commented February 9th 2011 by Thomas Dall'Agnese
    • We don't automatically launch the application when it's installed on device. Use the adb -d logcat command or DDMS utility to look at the log statements to see what the problem is.

      — commented February 9th 2011 by Don Thorp
  • I think your solution works, but actually now it works also through Titanium Developer.
    The only problem is that the application does not automatically start. But it seems to work now!
    I needed (and still need sometimes otherwise it just fails at application startup) to delete the android build folder, make a small change to the project settings (Edit tab), save it, and rebuild everything.

    Also I installed the 64 bits driver of my cellphone.
    I think this is not what solved my problems but still may be useful to tell it…
    So far I had installed only the official driver that came with the phone, but it is only 32 bits. Android SDK and Titanium are also 32 bits anyway (I believe…) so I thought it's fine but I found 64 dlls on the web. I just copy/pasted it into the System32 directory (the dlls in the SysWOW64 were already there and more recent).

    — answered February 9th 2011 by Thomas Dall'Agnese
    permalink
    0 Comments
  • Hi,

    10 months later.. I too had similar problem. But when I installed it via adb it worked in my HCT Wildfire S.

    \build\android\bin>adb install app.apk
    1790 KB/s (1661287 bytes in 0.906s)
            pkg: /data/local/tmp/app.apk
    Success
    

    ref: adb

    — answered November 30th 2011 by bhupal sapktoa
    permalink
    0 Comments
  • Hey,

    I was having the same problem on Mac and the below was what I did to get it working.

    I had the following on my Nexus 7:

    Unknown Sources on. [https://wiki.appcelerator.org/display/guides/Deploying+to+Android+devices]
    Developer Mode on.
    USB Debugging Mode on.
    Mock Installations on.
    It by default was connected as a Media Device.
    Not locked.

    Using terminal in the location of the adb file I ran .&#x2F;adb kill-server wait a few seconds, then ran .&#x2F;adb start-server. You can then do .&#x2F;adb devices to see if your device is being found.

    I got info on how to do the above here [http://forum.xda-developers.com/showthread.php?t=1917237]

    After that I just attempted to rebuild the android device on my tablet and it worked fine, it didn't launch itself and the app I built was the Kitchen Sink, this didn't work correctly, it freezes and doesn't load anything. I am not sure if this the that Kitchen isn't supported well on the Nexus 7.

    — answered March 1st 2013 by Paul Flood
    permalink
    0 Comments
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.