I don't have a solution for you unfortunately, just meant to mention I'm seeing kind of similar problems fairly often - my installs also fail when they really shouldn't.
My test device is HTC Desire whose internal storage, unlike your case, is used up to some extent by other installed apps. However, there should be enough room left to install my .apk. Another difference from your case is that it always helps if I reboot the phone (annoying enough to have to do that 15 times a day though). My theory is that the install process fails to clean up something in /tmp (or an Android equivalent thereof) that gets cleaned up only during the next boot. This obviously doesn't explain your situation though if device reboot doesn't help you ... On Tue, Sep 6, 2011 at 10:31 AM, Palsson <palsson...@gmail.com> wrote: > Hello Ed, > > Thanks for your response. > But restart and reboot of both adb server and even target and host, is > not solving the issue. > > The problem: > I'm using Eclipse, with adb-plugin, to develop applications for my > target (AM3517 evm, running Android). > I'm connecting adb over ethernet. > This has been working just fine until recently. > Now the debug session is not being established and terminates with: > Installation error: INSTALL_FAILED_INSUFFICIENT_STORAGE > Please check logcat output for more details. > Launch canceled! > > I can't even run the HelloWorld example anymore. > The issue can't be related to memory storage, as there are no other > applications loaded onto the module, beside default apps from the > release. > I have a different host (computer) with the Eclipse ADT configured, > and the same error appears. > > Instead of debugging (installing and debugging) my application via > Eclipse, I can use the adb push tool. > If I just use # adb push myapplication.apk /data/app - I can find the > app icon on my target and run it. > I'm not using the adb install command from the shell. > > So: > It worked for some time after my first installation. > Now I'm trying to figure it out, which part of the configuration has > changed resulting in the Eclipse debugging not being functional? > > Regards > Palsson > > > > On Sep 6, 2:08 am, Ed <edscha...@gmail.com> wrote: > > If it's not a device storage issue then the first place I would start is > > running "adb kill-server" and "adb start-server" to restart adb. > > > > Not 100% sure what your problem is - you can use the adb push command but > > cannot use the adb install command? > > > > Don't forget that internal memory and SD memory are different so one may > > have room while the other doesn't. > > > > Cheers, > > > > Ed > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
