Related
Help my phone memory has 2mb left were has it gone? I have no programs installed on it and have deleted all the temp internet files but there is no space help please!!!!!!!!!!!!!!!!!
Try and check your Windows\Opera9\download and Windows\Opera9\tmpdownload folders. If you've had Opera to "open" files directly from the Internet rather then "downloading" them first, you probably have plenty of those stored in there.
Mobile Monger
Mobile Monger can scan your main memory and your storage memory if thats what you need but it can not scan RAM. It gives a graphical display of a block for each file - the bigger the block the bigger the file. It takes a while to scan but makes it very easy to see what is taking up your memory.
http://forum.xda-developers.com/showthread.php?t=420763&highlight=monger
I have found that if I don't clear my cache in opera it really eats memory
open opera
open settings
open privacy
delete cache
helps alot for me
I would also recommend mobile monger
wow that memory monger app is brill!
thanks
Ever since I updated my nexus to Froyo, when I'm using the browser itll start to take up all of my available memory causing me to get the low storage warning and sometimes stop me from getting text messages. The only way to free back up the memory is to go force close the browser, which is sometimes using up to 80 mb of data. Ive already tried a factory data reset and also went into the recovery and wiped and clear the cache. I never had this problem in 2.1 and its really annoying. anyone got any ideas? thanks.
forceclosing the browser wont clear up cache.... scroll down instead of forceclosing, and hit clear cache. dont do it through recovery
I am having this problem too D:
Yeah, the browser doesn't seem to limit cache, although I've never seen it use 80M. Most I've seen is 7M. I just clear cache through the Applications list, although in Froyo you can do it directly in the browser now.
if you visit the google forums, the android team has changed the browser in 2.2 to cache the pages you have open in your browser much more aggressively, so that when you go back to the browser the phone doesnt need to refresh the network and reload the page. i posted a link to the google topic before. but what this means is that the browser now takes up huge amounts of space as time goes on. killing it does bring back the space. personally i like this change, but i can see why it might suck for some people.
here's the link
http://code.google.com/p/android/issues/detail?id=2171
Anyone who is having this issue, go here and click the star to vote for this issue: http://code.google.com/p/android/issues/detail?id=1068
i posted against this issue, because i happen to like what they did to the new browser. god forbid they go back to the old way, it was not good.
I agree, the browser is better this way in some regards, but it needs to LIMIT what it does... If you don't manually clear cache it'll easily take 8+ megs of storage!
khaytsus said:
I agree, the browser is better this way in some regards, but it needs to LIMIT what it does... If you don't manually clear cache it'll easily take 8+ megs of storage!
Click to expand...
Click to collapse
but its not the cache, its just a temporary storage usage. if you force close the browser, it regains back that storage. at least for me it does. my actual cache in the browser never changes, and hovers around 7mb.
Aaaand we're not using A2SD why???
RogerPodacter said:
but its not the cache, its just a temporary storage usage. if you force close the browser, it regains back that storage. at least for me it does. my actual cache in the browser never changes, and hovers around 7mb.
Click to expand...
Click to collapse
Ah, sorry, I got off topic then.. I was talking specifically about the browser cache, which for me varies between 4-8.5M it seems.. and I clear it because otherwise I'm <20M
Christopher3712 said:
Aaaand we're not using A2SD why???
Click to expand...
Click to collapse
Because not everyone is rooted running non-stock roms?
Simple solution
Friend was having the same issue but this was pre-froyo.
Found out that after viewing articles on the news and weather app and also viewing webpages she was just hitting the home softkey to return to the main page. This was causing new window after new window of fully loaded websites to be cached out of memory and into storage.
Although i agree there should be a caching limit on the browser there should also be an effort from the end user to close the unused windows when done (easily done through the windows menu). Also after using the news and weather app and any other app that uses the browser to display pages, it should be good practice to use the back button and not the home key.
I've always done that and now my girlfriend does it and guess what... its not an issue anymore.
Cabarnacus said:
Friend was having the same issue but this was pre-froyo.
Found out that after viewing articles on the news and weather app and also viewing webpages she was just hitting the home softkey to return to the main page. This was causing new window after new window of fully loaded websites to be cached out of memory and into storage.
Although i agree there should be a caching limit on the browser there should also be an effort from the end user to close the unused windows when done (easily done through the windows menu). Also after using the news and weather app and any other app that uses the browser to display pages, it should be good practice to use the back button and not the home key.
I've always done that and now my girlfriend does it and guess what... its not an issue anymore.
Click to expand...
Click to collapse
Except that you can't use the back button in the browser if you've been browsing a lot, you'll be going backwards through a bunch of pages. And if you've logged in, you can't go past that at all as it'll want to repost data etc...
One could close the window I suppose, which would load a default homepage, then go back, but that's tedious.
khaytsus said:
Except that you can't use the back button in the browser if you've been browsing a lot, you'll be going backwards through a bunch of pages. And if you've logged in, you can't go past that at all as it'll want to repost data etc...
One could close the window I suppose, which would load a default homepage, then go back, but that's tedious.
Click to expand...
Click to collapse
Tedious? Thats almost as bad as that YouTube review of the Nexus where one guy said he had to move his hand "All the way up to the top of the phone" just to switch it on. (Surely we've all seen it?)
I wouldn't say tedious, just something to get used to. Sadly Google aren't quite there with their Google MindReader beta for Android but until then menus and manually closing windows work just fine ;-)
Cabarnacus said:
Tedious? Thats almost as bad as that YouTube review of the Nexus where one guy said he had to move his hand "All the way up to the top of the phone" just to switch it on. (Surely we've all seen it?)
I wouldn't say tedious, just something to get used to. Sadly Google aren't quite there with their Google MindReader beta for Android but until then menus and manually closing windows work just fine ;-)
Click to expand...
Click to collapse
Steps to properly exit browser
Menu button
Select Windows option
X on all open Windows
Back Button
Not exactly "move hand to top of phone".
And again, my major complaint is about the lack of a limited browser cache, ie: html, css, images, cached for later reload. It grows over 8M, that's really too much IMO. Should be able to limit it, in which case I'd likely limit it to 2-3M myself and see how it worked out.
khaytsus said:
Except that you can't use the back button in the browser if you've been browsing a lot, you'll be going backwards through a bunch of pages. And if you've logged in, you can't go past that at all as it'll want to repost data etc...
One could close the window I suppose, which would load a default homepage, then go back, but that's tedious.
Click to expand...
Click to collapse
Actually I do that quite a bit. But you don't even have to. After you close all windows, it defaults to open a last page (Google home in my case), then just hit home cause there's nothing left to cache anyway, so back button or home button does the same thing, makes no difference.
hmm in my case it's also not the cache which makes the problems, but the "Data" of the browser app.
It easily exceeds 28MB!
And cache is only at 600kb, so clearing cache doesn't help.
Clearing the data helps. but it will delete all your bookmarks and other settings which is bull****.
Force closing the browser didn't help too (it helped in the past but interestingly not today).
Browser can not be installed on sd card. System updates can not be installed on external memory.
Sent from my Nexus One using XDA App
Shahpur.Azizpour said:
hmm in my case it's also not the cache which makes the problems, but the "Data" of the browser app.
It easily exceeds 28MB!
And cache is only at 600kb, so clearing cache doesn't help.
Clearing the data helps. but it will delete all your bookmarks and other settings which is bull****.
Force closing the browser didn't help too (it helped in the past but interestingly not today).
Click to expand...
Click to collapse
What? From apps, manage, all, find browser. Clear cache there. That does not clear up your 28M in ram?
Is someone else having this kind of behaviour?
When i browse my SD-Card with a file manager and want to open a picture with the stock gallery app, it loads about 10 sec.
If I open the same picture direct from the gallery-app, it opens directly without delay.
I don't have a huge picture collection - about 90 pics and some videos about 300mb, so that shouldn't be the problem. I also tried to clear the cache of the gallery (com.cooliris.media). No solution.
Someone got an idea how to fix it?
nice grettings.
I have noticed the same issue that stock gallery app is slow when opening a specified image from any file manager.
There are some free picture viewers which are able to load pictures much faster, I have used "Picture Viewer", "ViewPic", they both perform well.
However ViewPic requires permission to access your location and full internet access, thus I have to use DroidWall to block its internet access.
I have this problem too. It's especially annoying because the gallery is used to view pictures from the camera. It's really annoying wanting to show someone a picture I just took, and having to sit around waiting for gallery.
houzuoguo said:
I have noticed the same issue that stock gallery app is slow when opening a specified image from any file manager.
There are some free picture viewers which are able to load pictures much faster, I have used "Picture Viewer", "ViewPic", they both perform well.
However ViewPic requires permission to access your location and full internet access, thus I have to use DroidWall to block its internet access.
Click to expand...
Click to collapse
I have been having the same issue I have a 16 Gb class 2 card though. Do the apps you mentioned perform better on larger cards as well? Shall give them a try Thanks for the suggestion
My card is also a class 2 I think. I suppose that could be part of the problem, does anyone know if faster cards make a noticeable difference here?
I usually keep my N1 at around 30-50 MB free of internal storage, which is enough to have everything I want loaded on, but it's tough to free up much more space than that without uninstalling apps or moving to SD the apps that shouldn't be moved.
So anyway, today my phone suddenly dropped down to 13 MB left and the culprit appeared to be Browser data - suddenly over 46 MB! The cache was already cleared. I went through with Root Explorer and found that the largest file was located in:
/data/data/com.android.browser/app_thumbnails
For some reason a 31.5 MB file had made it into this directory, and Android clearly is not smart enough to clean it up. Anyway I deleted the offending file via Root Explorer and now it's happy.
Any thoughts on how to keep the browser from ballooning like this? I didn't want to delete all browser data because of bookmarks, cookies etc.
because in 2.2 froyo google updated the browser to temporarily store the entire contents of the page you are browsing into memory such that if you lost data connection, the page could be reloaded without the data connection. so when you have a few tabs open in the browser, or a very large site open, all contents are temporarily being stored for just in case.
if you were to close out all the tabs, kill the browser, all would return to normal. often times my browser hits up over 80MB because i have tons of pages open. i just kill all my tabs and the low space warnings go right away.
its a trade off, i dont mind it cause its better than the old way, but the trade off is we suffer with low storage.
I'll try closing tabs next time, but I swear I'd already closed all the tabs and still the bloat persisted across reboots...
Sent from my Nexus One using XDA App
also delete the browser cache if you want to clear the pron vid, that stuff can take up quite a bit of space
cmstlist said:
I'll try closing tabs next time, but I swear I'd already closed all the tabs and still the bloat persisted across reboots...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
when this happens to me, occasionally i kill all the tabs and it takes a small bit of time for it to appear back to normal, but never more than a minute or so. but if i close the tabs, then force close the browser, it for sure instantly clears the used space back.
if its happening to you across reboots, then might be something completely different.
FYI i havent cleared my browser cache since July last year hehh, and i use the browser like a madman. i wonder how much space i'd get back if i did?
I find that when space is low, it automatically empties the browser cache to zero. In the scenario I described above, the cache was already empty.
Sent from my Nexus One using XDA App
Photo Uploads Don't WorkWhenever I try to upload photos through the built in photo uploading app (it doesn't matter what service I try to upload to) the photo fails to upload, giving an "Upload error" notification. When the notification is clicked I get the following error: "Can't send response now. Data services are unavailable."
I've seen some people mention doing a full factory reset (on other Motorola DROID phones) and this possibly fixing the issue, but I would definitely like to avoid this at all costs.
Additionally, and this may or may not be related, my phone has trouble syncing with verious social networks at various times.
Stuff I've Tried Already
I have tried on both WiFi and 3g (both connections work fine for everything else)
I have updated my roaming with *228
I have tried a factory reset
Data Manager is not set to Wait for WiFi to upload
I have tried removing and re-adding the accounts
Nevermind. Removed all that stuff anyway.
--
matt katzenberger
http://katzmatt.com
[sent from my droid]
OMg i hated that!!! mine does that from time to time!
I have noticed that happening from time to time with dropbox, and also a problem where it uploads t the main dropbox directory rather than my selected directory. I noticed that it appears to happen when the phone is running low on RAM.
Based on the behavior of the gallery app and dropbox app, I believe what is happening lies in how Android manages memory. There is a good article about this over at Android Central but essentially Android allows for different classifications of apps. As Android system runs out of RAM, it will start shutting down apps and running processes based on this priority system.
So, what I believe happens is that when you select a picture in the Gallery app, then switch over to your uploaded (or vice versa), the phone runs out of RAM and closes the original app. Once you select the upload location (or the desired pic in the vice versa scenario), that app will look for a handoff from the first app, however that first app was closed by the system due to low memory. I am basing this on conjecture, but I have observed dropbox or the gallery app appear to "reload" after I switch between the two.
The low RAM is my major gripe about the Droid 3. Moto's custom skin, along with all the VZ bloat, appears to somehow eat up a ton of RAM (perhaps there is bloatware that runs in the background" which would be OK if the Droid came with 768mb or 1gb of ram. I wish there was a way to add ram after the fact.
I've never experienced this but I never use the native uploading app in Motorla gallery either. I tend to steer clear of the account setup in android and download apps from the market instead so i can control the data transfer and how all my interactions with my albums go a little more specifically. All that to say i use photobucket and have never had this error using the photobucket app on the market.
This problem was not a memory management problem, and had something to do with motorolas servers. It seemed to be fixed last time I checked
––
matt katzenberger
http://katzmatt.com
[sent from my droid]