You could submit a bug, but I don't know when this would be worked on.
On Tue, Oct 13, 2009 at 10:33 PM, Dan Sherman impact...@gmail.com wrote:
Dianne,
Sorry to revive the thread (its been a while), but noticed this got posted
in a different thread:
Dianne,
Sorry to revive the thread (its been a while), but noticed this got posted
in a different thread:
http://groups.google.com/group/android-developers/browse_thread/thread/d92a41988f9d3428
packageinstaller/PackageInstallerActiviity.java (line 293):
//compute the size of the
I _think_ the market has the same issue, I'll try to confirm it tonight, but
from what I've heard from users they're experiencing download errors if
they don't have a large amount of space free. Again, I'll try to get some
more concrete info later tonight :)
Thanks for taking a look at this
Hey Dianne (or anyone else reading),
I've got a more concrete case nailed down here. Might help us to figure
this issue out :)
There's still a tiny bit of ambiguity which looks to be stemming from
Windows vs Linux sdk's (as far as I can tell), but this process should
illustrate the problem.
Okay it just sounds like the browser's (or download manager's) checking on
free space may be a little overly aggressive (though perhaps not too much,
once you start getting to 15% free or so performance goes down fast).
On the one hand, I don't see what can be done for ADC. On the other hand,
Oh sorry.
I must not have specified, this is with just an APK, completely outside of
the market. We've heard complaints of users having issues through the
market, but with a full uninstall of the application, and an install from a
downloaded APK (which I imagine should be a fresh install), it
We're also a bit worried about how this would/will be handled in the ADC
installer, as I'm sure 22mb is easily above what many community judges will
have available...
- Dan
On Tue, Sep 8, 2009 at 2:33 AM, Dan Sherman impact...@gmail.com wrote:
Oh sorry.
I must not have specified, this is
To be honest, I am surprised it requires that much. For something that
isn't forward locked, we should need at most double the space (for the
original copy of the apk, and the copy placed into /data/apps by the system
as it is being installed before the original is deleted). Using more than
3x
I'll see what I can do here to reproduce the issue with more concrete
documentation, everything we've got so far is based on user input and what
they've told us they've needed to free to get it to install properly. :)
Thanks for the response :)
- Dan
On Tue, Sep 8, 2009 at 6:07 PM, Dianne
You might start with an app that installs just the framework, then use
an internal function to install the graphics and anything that takes
up a lot of space. That way the package installer won't hog all the
space.
-John Coryat
What Zip Code?
Radar Now!
If your app is forward locked, it can take significantly more space, even
after the install is done (unfortunately all of the resources currently have
to be installed twice).
On Mon, Sep 7, 2009 at 8:13 AM, Dan Sherman impact...@gmail.com wrote:
Hey guys,
The package installer looks to take
Thanks for the responses,
Dianne, what do you mean by forward-locked?
- Dan
On Mon, Sep 7, 2009 at 2:51 PM, Dianne Hackborn hack...@android.com wrote:
If your app is forward locked, it can take significantly more space, even
after the install is done (unfortunately all of the resources
If you select the option when putting your app on market it to copy protect
it (which uses forward locking on the device).
On Mon, Sep 7, 2009 at 7:21 PM, Dan Sherman impact...@gmail.com wrote:
Thanks for the responses,
Dianne, what do you mean by forward-locked?
- Dan
On Mon, Sep 7, 2009
13 matches
Mail list logo
