OMG... Thank you! I had no idea this was going on. I had hardly any
space left on my phone and this double-reboot trick recovered about 30
MB.
On Jan 12, 3:46 pm, "Justin (Google Employee)"
wrote:
> Here is some more information on what's happening. There is a problem
> in yaffs2 where unlinke
On Tue, Jan 13, 2009 at 10:57 PM, Disconnect wrote:
> 1.5 million was a number a blogger pulled from somewhere warm and dark.
Ahahahahahahaha :) ROFLMAO!!!
>
> Realistically I think the numbers that came out were on the order of
> 250,000.
>
This would kill many people's dreams of riches but I
1.5 million was a number a blogger pulled from somewhere warm and dark.
Realistically I think the numbers that came out were on the order of
250,000.
On Tue, Jan 13, 2009 at 3:54 PM, Stoyan Damov wrote:
>
> On Tue, Jan 13, 2009 at 9:47 PM, Justin (Google Employee)
> wrote:
> >
> > The Market ca
On Tue, Jan 13, 2009 at 9:47 PM, Justin (Google Employee)
wrote:
>
> The Market cache growing is not related to this issue. When I first
> heard about it I thought it might be, I investigated, its not.
>
> I wasn't trying to label this as not a bug to say "oh look at our
> beautiful, bug free sys
The Market cache growing is not related to this issue. When I first
heard about it I thought it might be, I investigated, its not.
I wasn't trying to label this as not a bug to say "oh look at our
beautiful, bug free system", but as a semantic argument. I completely
agree that most people would l
Hi all - new to this, but have a (possibly related, possibly not)
issue - I tried the above, and it didn't change... I've seen a number
of folks comment on the size of the Market as reported in the Settings-
>Applications->Manage Applications panel, and I still don't get why
my Market is 21MB.
On Tue, Jan 13, 2009 at 10:08 AM, Stoyan Damov wrote:
>
> On Tue, Jan 13, 2009 at 11:09 AM, Al Sutton wrote:
> >
> > C'mon Justin, it's a bug.
> >
> > It has no positive effect for users, it's not the desired behaviour, and
> > it's on JBQs to-fix list.
> >
> > Lets not get into the realms of mar
On Tue, Jan 13, 2009 at 11:09 AM, Al Sutton wrote:
>
> C'mon Justin, it's a bug.
>
> It has no positive effect for users, it's not the desired behaviour, and
> it's on JBQs to-fix list.
>
> Lets not get into the realms of marketing by trying to relabel things so
> they don't sound so bad.
>
+1
T
I think it's assigned to someone internally. I have no visibility over
the level of support that we can get from upstream on this issue.
JBQ
On Tue, Jan 13, 2009 at 1:28 AM, Al Sutton wrote:
>
> Thanks for the clarification. Is anyone assigned to look at the
> filesystem problem or is that bein
Thanks for the clarification. Is anyone assigned to look at the
filesystem problem or is that being reported upstream?
Al.
Jean-Baptiste Queru wrote:
> Just to make some things clear:
>
> -the core bug appears to be on the filesystem side. I'm not going to
> touch that part.
>
> -a secondary is
Just to make some things clear:
-the core bug appears to be on the filesystem side. I'm not going to
touch that part.
-a secondary issue exists in the system process where some unlinked
files are kept open longer than necessary (which apparently triggers
the "core bug"). This is where I'm hoping
C'mon Justin, it's a bug.
It has no positive effect for users, it's not the desired behaviour, and
it's on JBQs to-fix list.
Lets not get into the realms of marketing by trying to relabel things so
they don't sound so bad.
Al.
Justin (Google Employee) wrote:
> Well, I don't think this is rea
Well, I don't think this is really a "bug" in the traditional sense,
but an adverse interaction between two pieces of code. The phone
should checkpoint the filesystem when it goes to sleep, just in case.
The filesystem should probably also not worry about cleanup on
checkpointed filesystem, becaus
On Tue, Jan 13, 2009 at 2:25 AM, Justin (Google Employee)
wrote:
>
> Yes, your understanding is correct. Yes, you will need to unlock the
> screen and wait for the home scree to appear before shutting the phone
> down the second time. Shutting the phone down is better than pulling
> the battery.
Yes, your understanding is correct. Yes, you will need to unlock the
screen and wait for the home scree to appear before shutting the phone
down the second time. Shutting the phone down is better than pulling
the battery.
Cheers,
Justin
Android Team @ Google
On Jan 12, 4:22 pm, "Stoyan Damov" w
On Tue, Jan 13, 2009 at 1:46 AM, Justin (Google Employee)
wrote:
>
> Here is some more information on what's happening. There is a problem
> in yaffs2 where unlinked files are not removed from a check-pointed
> filesystem. Whenever Android sleeps, it check-points the filesystem.
> When you uninst
Here is some more information on what's happening. There is a problem
in yaffs2 where unlinked files are not removed from a check-pointed
filesystem. Whenever Android sleeps, it check-points the filesystem.
When you uninstall an app the files are unlinked. If the device then
goes to sleep before t
On Mon, Jan 12, 2009 at 4:54 PM, Joel Knighton wrote:
> Okay, someone who can replicate this problem, can you perform a "cat
> /proc/yaffs" and then post the output here. Curious to see the YAFFS
> debugging info.
>
>
I don't have the output handy, but I went from ~12K unlinked files to ~2K.
This
Beautiful. It does appear to be nUnlinkedFiles in userdata causing the
problem after continual uninstall/reinstall (my phone is at 30k after
infrequent installations, I notice yours is at 5k after a fresh
install/battery trick). Working on a shell script that could potentially
remedy this problem
On Tue, Jan 13, 2009 at 12:05 AM, Disconnect wrote:
> Why not? Its available to anyone with a g1 these days (if you are willing to
> wipe out your data, which it sounds like you have to do occasionally anyway)
>
> http://tinyurl.com/g1rc30
>
> On Mon, Jan 12, 2009 at 5:00 PM, Stoyan Damov
> wrot
Find it below, I'll do it again when the memory drops so you can compare:
YAFFS built:Oct 6 2008 14:13:20
$Id$
$Id$
Device 0 "system"
startBlock. 0
endBlock... 539
totalBytesPerChunk. 2048
nDataBytesPerChunk. 2048
chunkGroupBits. 0
chunkGroupSize. 1
nErasedBlocks.. 9
Why not? Its available to anyone with a g1 these days (if you are willing to
wipe out your data, which it sounds like you have to do occasionally anyway)
*http://tinyurl.com/g1rc30*
On Mon, Jan 12, 2009 at 5:00 PM, Stoyan Damov wrote:
>
> I guess by "you" you don't mean me - I don't have root ac
Just anybody. If you'd like, you could still do the first one for me and
help out a bit.
On Mon, Jan 12, 2009 at 4:00 PM, Stoyan Damov wrote:
>
> I guess by "you" you don't mean me - I don't have root access. BTW, I
> just found another bug, which is very weird but I'll send it in a new
> post.
I guess by "you" you don't mean me - I don't have root access. BTW, I
just found another bug, which is very weird but I'll send it in a new
post.
On Mon, Jan 12, 2009 at 11:58 PM, Joel Knighton wrote:
> In fact, if you have root access, a "$su #echo all > /proc/yaffs #cat
> /proc/yaffs" would be
In fact, if you have root access, a "$su #echo all > /proc/yaffs #cat
/proc/yaffs" would be optimal. This should give a fair amount of debugging
info for system, userdata, and cache. If you post that up here, I should be
able to give it a shot.
On Mon, Jan 12, 2009 at 3:54 PM, Joel Knighton wrot
Okay, someone who can replicate this problem, can you perform a "cat
/proc/yaffs" and then post the output here. Curious to see the YAFFS
debugging info.
On Mon, Jan 12, 2009 at 3:45 PM, Jean-Baptiste Queru wrote:
>
> When I tried to reproduce it a few months ago I think that I was able
> to re
When I tried to reproduce it a few months ago I think that I was able
to reproduce it without such a shortcut, but I might be wrong.
JBQ
On Mon, Jan 12, 2009 at 1:42 PM, Stoyan Damov wrote:
>
> You might want to check whether this is related to having a shortcut
> of the app on the home screen.
You might want to check whether this is related to having a shortcut
of the app on the home screen. I have a hunch it is.
Cheers
On Mon, Jan 12, 2009 at 11:39 PM, Jean-Baptiste Queru wrote:
>
> There is a bug somewhere (it's assigned to me for investigation) where
> the system process keeps apk
There is a bug somewhere (it's assigned to me for investigation) where
the system process keeps apk files open after they get unlinked in
some scenario close to what you mention (install, launch, uninstall),
which can then trigger the yaffs2 leak bug.
JBQ
On Mon, Jan 12, 2009 at 1:35 PM, Stoyan
Thanks.
A little bit more info about that bug - I *am* experiencing it again.
It *is* related to re-installs of one and the same application over
and over again.
I reinstalled my app maybe ~20 times today and slowly my ~70 went to 63 MB.
My app is 2MB so I have to have ~68MB but I don't. I notice
Second hand information about the battery trick: yaffs2 has some
sanity-checking code that can detect and recover from unlinked files,
but that code is only run when the filesystem wasn't cleanly
unmounted.
JBQ
On Mon, Jan 12, 2009 at 1:02 PM, Stoyan Damov wrote:
>
> On Mon, Jan 12, 2009 at 10:
On Mon, Jan 12, 2009 at 10:55 PM, Dianne Hackborn wrote:
>
> Another place to look -- there is a filesystem bug that can sometimes happen
> where unlinked files are not recovered. Here is the comment from an
> engineer who knows more about it:
>
> "They can easily tell by looking at the number o
On Mon, Jan 12, 2009 at 1:00 AM, Stoyan Damov wrote:
> Actually Dianne I am *stunned* how few bugs I've found during my 1
> month usage of Android.
> Hail to Google engineers (I'm *not* joking)!
Wow, that's nice to hear. :)
> This one, however, is a showstopper for me in the verbatim sense.
>
> The Market has nothing to do with what apps you have installed or
> uninstalled, AFAIK, so uninstalling an app will not affect the Market size.
>
The Market may not have anything to do with what apps are installed,
but the Market application on the device does. I agree with Stoyan
about th
On Mon, Jan 12, 2009 at 8:43 PM, Mark Murphy wrote:
>
> The Android Market apparently caches market-related information (e.g.,
> icons and descriptions). This cache is not proactively released.
> However, when free storage space drops far enough, the Market will free
> up the cache.
>
> The core
What is your reference for the market actually freeing cache?
The devs I talked to about this indicated it did not do that. (Ditto for the
occasional lost webpage screenshot, but at least 'delete all data' can clear
that at the expense of bookmarks, etc)
On Mon, Jan 12, 2009 at 1:43 PM, Mark Murp
HaleRazor wrote:
> I am also seeing similar behavior. Market now shows using 21MB. I
> thought it might be related to the apps that I had installed, so I
> uninstalled three applications of varying sizes...the biggest being
> 3MB. Market still showed using 21MB. I have formed the suspicion
> t
I am also seeing similar behavior. Market now shows using 21MB. I
thought it might be related to the apps that I had installed, so I
uninstalled three applications of varying sizes...the biggest being
3MB. Market still showed using 21MB. I have formed the suspicion
that there is a bug in the M
I'm having the same problem too now, of sorts.. Market claims to be
using 19MB of storage (and grows with every app I download), and there
doesn't appear to be any way to clear it.
On Jan 12, 1:00 am, "Stoyan Damov" wrote:
> On Mon, Jan 12, 2009 at 4:33 AM, Dianne Hackborn wrote:
> > On Sun,
On Mon, Jan 12, 2009 at 4:33 AM, Dianne Hackborn wrote:
> On Sun, Jan 11, 2009 at 5:04 PM, Stoyan Damov
> wrote:
>>
>> Is there *anyone* who'll dare to tell me there's no bug in Android?
>
> Why would anyone claim there are no bugs in -any- piece of complicated
> software? (Except I guess TeX).
Joel, thanks for your help, but I unfortunately I can't help you help
me because I don't have root, so I can't install busybox and I can't
give you a meaningful file listing with so many directories being
denied access. I didn't see anything interesting in the log, and btw
ls hung while (or after)
Okay, Stoyan, if you want to do a ls -l -R and then email it to me (
joel.knigh...@gmail.com) I'll read through it and see if I notice a problem.
(You can email straight from the terminal app)
On Sun, Jan 11, 2009 at 8:41 PM, Joel Knighton wrote:
> Do you have busybox on the device? If so, I ca
Do you have busybox on the device? If so, I can help you find where the
space is gone. With only the included android shell binaries, however, I
don't know if I can.
On Sun, Jan 11, 2009 at 8:33 PM, Dianne Hackborn wrote:
> On Sun, Jan 11, 2009 at 5:04 PM, Stoyan Damov wrote:
>
>> Is there *any
On Sun, Jan 11, 2009 at 5:04 PM, Stoyan Damov wrote:
> Is there *anyone* who'll dare to tell me there's no bug in Android?
Why would anyone claim there are no bugs in -any- piece of complicated
software? (Except I guess TeX).
> How the fuck I don't have *anything* installed (besides the
> pre
44 matches
Mail list logo
