Related
For some reason my xda 11 says i have 91.68 mb allocated for storage
yet the last time i looked at it there was only 28mb in use.
I have no pictures or sound files no extra programmes and have only 2.2 mb of data above 64K. I've closed down all my active programs and performed a soft reset yet nothing seems to help.
Any ideas??
I'm a bit confused about your terminology here - I read it as you have 98MB allocated, 28MB in use, and therefore 70MB free - does this correspond with what you're getting in the Settings-Memory applet?
I'm confused because I can't see a problem with the above - although it only leaves you with 29ishMB allocated for program execution it's a perfectly reasonable config. You can change allocation between storage and program by sliding the slider. You probably know all this, I've probably got the wrong end of the stick.
Looks like a bit has gone somewhere, I have 126.03 to begin with, you are out by a bit as yours only adds up to 119.68.
memory loss
ok sorry if i'm not explaining myself properly
i am currently looking my memory settings
which tells me i have 91.69 MB in use for storage leaving 10.19 free
and 18.06 MB in use for program and only 6.09 free
now what concerns me is that having been through file explorer i don't know what is taking up so much storage memory especially as i have no voice or picture files or have got any additional programs
firstly there is insufficent memory to run transcriber properly and secondly what happened to increase my storage use from 28mb to 91 when i hadn't even used it.
(i haven't even connected my xda to the net yet)
Any comments would be appreciated
cheers john
Hmm 90odd MB in use is indeed strange. Are you sure there are no large files anywhere? Have you installed anything recently? Have you made a recording and forgotten to stop it manually so that it filled the available memory (although you'd still find this as a large file). It's not normal for PPC apps to take up such amounts of storage, and without a directory listing or access to your device it's unfortunately going to be pretty much impossible to work out whats wrong.
Incidentally. storage vs program memory allocation can be automatically adjusted by the device itself if it needs to.
Check for camera files, or do a backup and do a hard reset back to factory settings, then look at it from there and check it as you install programs/files.
memory loss
Thanks for that guys I can't explain it either
i've got 02 data support looking in to it and they're stuck as well so they are escalating it ie sending it to someone else. I should hear back today or tomorrow.
i guess in the end i'll probably have to do a hard reset. I'm just worried that it might come back or i have a virus even though they don't exist on ppcs at the moment.
i want to get a 1gb storage card any tips ?
ps thanks again if you ever get arrested (not that you will) send me a private message and i'll look after you. (I'm in the old bailey tomorrow on a murder case)
When I use Word Mobile on my Jasjar, it often happens that I am suddenly unable to save the file. This message appears:
Not enough memory to save the document. Please delete files or insert a storage card.
Tap Discard to close without saving or Cancel to return to the document.
Sometimes it helps to stop other running programs, sometimes not. The error message may also appear when I have recently taken a soft reset and only use Word Mobile. It may also happen with very small documents.
I use the wonderful PQz, which occupies a good deal of memory, but not that much...
Any advice??
no idea sorry, never had this problem. i have word set to save to SD card automatically so local memory shouldnt be relevant.
what is PQz?
This error happens often to me - I am surprised that not several other Universal users immediately respond that they have the same problem! And it happens while Settings -> System -> Memory tells me that 19 Mb is available for Storage and 27 Mb for programs.
I always save documents on the SD card.
PQz is the most wonderful program, which really increases the usability of the Universal enormously. And it is free. I use it to achieve fast multitasking and to get a Ctrl key. It may also be used for several other purposes. You may read about it by following this thread:
http://forum.xda-developers.com/viewtopic.php?t=33343
and look at the website
http://www.nicque.com/PQz/
This problem happens to me about 1/4 of the time. It doesn't matter if the file is large or has no text whatsoever. The only solution I have found is to copy the contents of my word file into a text file and save it using another application, thus losing all the formatting.
I've never used pqz.
I have realized that my use of malloc that has been working fine with sizes up to ~1.5mb always fails when going over that size. It has been rare that I ever actually need more than that but it creates a problem.
I am no expert on how windows sets up memory for programs and only have a rough idea about it. I have tried creating a heap and allocating memory from that, but that fails too.
eg
unsigned long sizeOfDataBlock;
HANDLE he=HeapCreate(NULL,sizeOfDataBlock+1024,NULL);
dose not return NULL
but
char*returnBlock=(char*)HeapAlloc(he,NULL,sizeOfDataBlock);
dose return NULL.
Can someone give some pointers on how to get hold of more memory to work with please.
You could consider using VirtualAlloc and VirtualFree instead I think. That's advisable for large allocations of contiguous memory.
V
I substituted them but it did not help. I also realized that the problem was not a size of 1.5mb but more like between 7-9mb. I was holding the same data in multiple seperate places so I re-aranged my code to use only 1 copy but the cost was more entangled code. The thing I still do not get is why the memory manager can show more than 20mb of free storage and 20mb free program memory but can't give me th 9 I want. On the first calls to malloc I can see the in use value rize by what I expected but before the last rize my error code tells me it failed.
Its probably bad practice to hog that much memory on a device any way.
I have found something else very interesting.
I made a small program to just allocate blocks and then give time to see the memory manager to confirm the effect. I can allocate as much memory in one call to malloc as the device can provide. Even if the program memory is less than what I request it adjusts with storage to allow huge allocations. I can still make it fail but only after about 24mb.
Why then can the same not be done from within my other program. Could it be that having more than one thread limits the amount of memory each thread can get. I would really like to understand this because memory allocations are at the hart of just about everything.
<<edit>>
I added 4 threads to my test app and tried again. The result was that I could allocate even more from the main thread, 4mb more. Why????
What is up with the memory drain on this device. I'll start the day with 24mb of memory (soft reset) and only have 10mb or less at the end of the day with no apps but activesync running. Has anyone less notice this?
hansolos said:
What is up with the memory drain on this device. I'll start the day with 24mb of memory (soft reset) and only have 10mb or less at the end of the day with no apps but activesync running. Has anyone less notice this?
Click to expand...
Click to collapse
Yea I get the same problem. Except I start off with about 20 and end up with as low as 9 before i'm forced to soft reset.
Its the magic of the Mogul's memory leak. The old rom and new rom feature it so untill a new update comes out, were stuck with it.
Does the Hermes and Kaiser have the same issue? They seem to be similar. They other thing is that the WM6 is suppose to have made those apps that leak in previous versions run at the kernel level.
my titan doesnt have the issue. its an app you've got installed. hard reset and dont install anything, you wont have the problem. troubleshooting 101. dont blame the titan.
I posted this on another forum discussing this problem, so I'll just quote myself here:
The memory "leak" thing is nothing more than a cache "optimization" in place to make the device respond snappier.
Whether it succeeds or not is another story altogether...
Basically, like any cache, it stores recent calculations for faster response later. For example, if you open and close IE alot, you might notice that the first time you open it on a fresh restart takes a little bit longer than the next times- that's because the second time you start it up, parts of it are still in memory from the first time!
You might be wondering why this happens even after forcing it closed with Xbutton or the memory settings. That's because the info stored in the performance cache aren't directly related to any one program! Many apps can use the same routines and calculations, and therefore this process exists on a processor/file system layer as opposed to a software layer, and therefore also exists even when all programs are closed!
Meaning, if I have mapopolis that uses a certain routine to access my BT GPS receiver, even after I close it, some of that routine stays in memory because perhaps Google Maps will use the same routine, and therefore respond faster!
Now, ideally, this should speed up performance, and it SHOULD disappear on its own if the memory is needed and the information goes "stale" (hasn't been processed in a while = not really needed for optimized perfomance). However, one look at the way Microsoft handles "automatically closing apps" (native X button, anyone?) is enough to know that WM can't manage its own memory very well.
I can, however, vouch for the fact that the longer you leave all programs closed, the more of your memory starts to creep back into available. I've sat and watched this happen. So, it sort of works, but perhaps not well enough if people are having low memory system crash problems.
Now, before you all start blaming MS for this... Its not Microsoft's problem. They developed CE-5 (which WM6 is based on) on machines limited to 32MB to make sure the programmers didn't get lazy with OS bloat.
Its the manufacturers who add all this file system optimization and stuff to their final device. In this case, its the way HTC thinks the system should run, which is why this anomaly is NOT as apparent on, say, a WM Treo device.
The good news is that if we complain enough, HTC might realize this optimization does more bad than good, and leave it out on the next ROM update for us.
However, truth be told, I think it works. The Mogul is one of the snappiest PPC's I've used of late, although I can't say for sure if its because of the cache or not.
This is just my personal opinion, so don't flog me! I just don't look at the memory useage anymore unless I'm having a problem, which mind you, I hardly do.
My most recent observations were this:
Soft reset gives me ~21MB (got some htc plugins), and after a day of use, making sure to close everything after I'm done, I get 18-19MB. At lowest, I hit 10MB after closing alot of apps. This memory usually comes back to 18-19mb in a matter of time for me. If for some strange reason it doesn't (can't say how often this happens), I soft reset.
All in all, I'm happy with the Mogul.
Click to expand...
Click to collapse
I wasn't blaming the Titan directly, although I wish they would allow you to adjust the memory like they have in the past. But as I've read that may having something to do with chipset of battery consumption.
I was just wondering if others had the same issue and might know of the reason.
Is there a list of known apps that cause memory 'drain' or don't clear their cache. I can understand apps caching data into memory to run faster, but they are not cleaning themselves out upon exit. The strange thing is how they continue to grow over the course of the day with no interaction.
I'm doing a hard reset to see if it get better. Add apps one at a time until I find an issue.
Ok did a hard reset. Setup Outlook to get my mail from Exchange and Gmail. Let it get synced and then did a soft reset. Started with 24mb after reset, down to 21mb without doing anything after an hour and it's still falling. The only thing running is ActiveSync. I've also removed htc_cm_guardain and ssdaemon from the startup. The only thing in startup is poutlook.
The thing I noticed when I had handyswitcher installed (before hard reset) was that filesys, device, gwes, services, shell and cprog all continously increased there memory consumption over the course of a few hours and never stopped or released it.
hansolos said:
I wasn't blaming the Titan directly, although I wish they would allow you to adjust the memory like they have in the past. But as I've read that may having something to do with chipset of battery consumption.
Click to expand...
Click to collapse
No no no... the reason you used to be able to select storage vs RAM was because it was SHARED memory! It was actually all RAM. If you had a 64MB device, that 64mb was split between ram and storage, and just like the rest of your RAM, it would wipe out when the battery died!
Ever since WM5 came along, they stopped sharing the memory, and now have dedicated RAM and Storage (using the leftover space on the EPROM chips used for the ROM image), much like a computer. This is a much better solution since you don't sacrifice your RAM for storing some large files, and you don't have to worry about battery failure cleaning you out!
Also, its not the apps that have cache, its the file system. The file system WILL actually free up some of that memory as the device is left with all apps closed for a while (maybe not all of it, but I've watched my device go from 11mb free after closing stuff to 18-19mb).
You guys need to hit the easy button on this one! It may not be a permanent fix, but there's a small freeware called Oxios Hibernate that releases RAM. I just put it on my start menu and 2 clicks....I have free RAM. Try it out, you won't be disappointed.
bam, thanks for the info... that little app rocks.
use a file explorer and go to \Windows\Startup. There is a shortcut there for a program along the lines of HTC_Guardian_cmsomething. This app is a htc app used to enforce sprint settings and runs in the background. So long as you don't destroy your phone internet settings you can just remove the shortcut. I found all my memory leak issues have gone away. I don't have any leaks when using the kaiser tab plugin.
Yes I've removed the links for HTC_Guardian and SSDaemon from startup and added them to my settings folder (if I ever need them). I soft reset to around 25mb and the Oxios Hibernate app keeps me around 24.5mb.
what does SDdaemon do?
sddaemon is suppose to be the speed dial or voice command app you get when you hit the button on the left side with the talk bubble. It loads the app if you hit the button, so I'm not sure why they have it in startup.
On my old Treo 700W, which REALLY had a memory problem, I used Oxios hibernate all the time. It works quite well.
yes, it works.
bam099 said:
You guys need to hit the easy button on this one! It may not be a permanent fix, but there's a small freeware called Oxios Hibernate that releases RAM. I just put it on my start menu and 2 clicks....I have free RAM. Try it out, you won't be disappointed.
Click to expand...
Click to collapse
you know what might help...if windows mobile had some sorta sorta disk caching feature...
that's what is causing the memory leak.
great tips. thanks.
hansolos said:
Yes I've removed the links for HTC_Guardian and SSDaemon from startup and added them to my settings folder (if I ever need them). I soft reset to around 25mb and the Oxios Hibernate app keeps me around 24.5mb.
Click to expand...
Click to collapse
It seems as if there's some code in the SMS-receiving app that says 'if the phone is reporting low memory, fire a 'warning' notification and completely forget the message I just got sent'. We do not get to see who sent the message, and the sender is not sent a 'message failed' response.
As we know the phone reports 'low memory' a bit cautiously, you could actually have 10mb spare - plenty for an SMS. It's possible for the phone to reach a 'low memory' status whilst in your pocket, so the user doesn't know he's going to miss txts until one comes in.
Could really do with a mod to do something about this - still show the warning but accept the text as normal rather than dropping it?
This would go wrong if there actually isn't enough space to store the message (<1k?), but if the warning fires on every text then at least the user has had a chance to do something about it.
mamoulian666 said:
It seems as if there's some code in the SMS-receiving app that says 'if the phone is reporting low memory, fire a 'warning' notification and completely forget the message I just got sent'. We do not get to see who sent the message, and the sender is not sent a 'message failed' response.
As we know the phone reports 'low memory' a bit cautiously, you could actually have 10mb spare - plenty for an SMS. It's possible for the phone to reach a 'low memory' status whilst in your pocket, so the user doesn't know he's going to miss txts until one comes in.
Could really do with a mod to do something about this - still show the warning but accept the text as normal rather than dropping it?
This would go wrong if there actually isn't enough space to store the message (<1k?), but if the warning fires on every text then at least the user has had a chance to do something about it.
Click to expand...
Click to collapse
Can the Nexus One actually run out of memory to receive a mere SMS? :/ Has this ever happened to you before or is this just a hypothetical question/request?
I don't think he would talk so specifically about it in detail if he was just making it up. I've lost an sms before too.
I was under the warning limit, but between 10mb and 20mb free, and my phone decided to tell me there wasn't enough room on the phone when an sms came in and that's that. No indication as to whom it was from, and definitely no way to get it again.
Yeap, it definitely does this. I've had it happen a few times and very annoying it is too. The message never gets received but shows as delivered at the other end.
Yes it has happened to me several times since having the N1, and just a few days ago on 2.2. Sometimes it's been 'my fault' because I've ignored the 'low on memory' notification, sometimes it's been the first I've heard of it - by then it's too late.
Either way, just dropping the message like that is not good :-/
Oh, and no, I don't think I've ever *actually* run out of memory, I've seen that 'low memory' warning appear but still have just under 10mb free.
So I think the SMS-receiving-code is being overly cautious/strict.
+1 for some workaround for this situation, when I went from cyan ext3 to froyo stock and trying fit everything on I did lose a few texts, which I had no idea where they were from.
what is the low memory warning? Can this phone actually run out of memory?
legion21 said:
what is the low memory warning? Can this phone actually run out of memory?
Click to expand...
Click to collapse
Low internal storage space. The SMS's are not saved in ram you know? Install too many applications and you run out of internal storage space.
So can we clarify if this is low MEMORY or low STORAGE being as the two are completely different?
I've had missing messages so this may explain it?
It is when you have low STORAGE. Internal storage to be precise. Would be nice if you could have SMS going to mem-card. But yes, I have had the same issue in the past. And there is no way to retrieve the 'delivered' message that I know of. Very annoying.
Yes, low storage.
Install a load of stuff... Google Earth and Fennec beta should do it, and you'll get the warning. But it's a bit over-sensitive, you could still have 10mb or so left.
There's an issue for this on the official tracker:
http://code.google.com/p/android/issues/detail?id=4991
doesn't look like it'll be looked at in a hurry though as there's not very many stars... so I hope a mod might be possible until G gets around to it?
(if you want to register your interest in the issue just star it, no need to comment with a 'me too' unless you're adding some info)
Edit: please keep 'store messages on SD card' to another thread... that is a big job, and it's not like we would actually have problems storing one 250-character message when we've got 10mb of space. The fix is for it to ignore that warning.
IDEA, install a program that when internal mem is detected as below the threshold where the system will rej, and overwride the default messaging and take hold of the message itself (and presumably SD it)
a very irratating bug indeed.. i have missed countless sms cause i have tonz of apps installed on an unrooted fone; leading to low internal storage RAM and thus getting this error... FROYO isnt much of a help with the option to put apps to SD since the apps have to integrate that feature and 95% of apps currently in the marked dont have that feature YET.. even GOOGLE Earth (25mb <- WAAA so big!!!) ..
I've added a comment to the bug. I would suggest everyone else does if you want this bug fixed officially, otherwise talk nicely to a dev on this forum
thelucster said:
I've added a comment to the bug. I would suggest everyone else does if you want this bug fixed officially, otherwise talk nicely to a dev on this forum
Click to expand...
Click to collapse
No, don't add a COMMENT, just add a STAR. 'Me too' comments get emailed to everyone and are annoying. STARs register interest. Thanks!
So is it possible to fix this with a mod? Is it even in the SMS app or is it some other code that handles receiving the message?
try this post for altering your low space threshold:
http://forum.xda-developers.com/showthread.php?t=877793
I have had this happen to me too.
The most infuriating part of the matter is that the phone rejects the message, but the message is GONE forever. You have no idea who sent it, and they have no idea you never got the message. On top of that, there is still nearly 20mb of space left. WTF the phone needs to reject a 1kb sms when there is 20mb of space left completely blows my mind.
It is a terrible glitch and one of the few things I severely dislike about android.
One option could be an app for when the phone hits low storage, to put the phone in air plane mode?
This would prevent ANY sms from being rejected until you delete space, and take the phone out of air plane mode.
Once you get up to the limit on apps no matter where the low storage limit is set you always run the risk of running into it. It would be better to simply put all the data on sd, there would be no performance hit and the problem is permafixed. As an added advantage all your texts are backed up locally and with just a little more coding could be set up to be restored as needed when the app was reinstalled on the same or new device.
GldRush98 said:
I have had this happen to me too.
The most infuriating part of the matter is that the phone rejects the message, but the message is GONE forever. You have no idea who sent it, and they have no idea you never got the message. On top of that, there is still nearly 20mb of space left. WTF the phone needs to reject a 1kb sms when there is 20mb of space left completely blows my mind.
It is a terrible glitch and one of the few things I severely dislike about android.
Click to expand...
Click to collapse
It is not that simple. AFAIK sms/mms are stored in the sqlite database. Which needs some maneuver space to operate normally. In fact, android SQLiteOpenHelper under certain threshold will open the database only in the readonly mode. Which seems to be happening here.
The pragmatic solution would be to "tweak" the free space display and show the real size minus some 30mb "reserve". So, the user would see "0 bytes left" and would not complain. Better still - stop receiving messages and signal "memory full" to the Short Message Service Center. Adding nagging notifications to the user. Seems like unfinished work by google.
krabman said:
Once you get up to the limit on apps no matter where the low storage limit is set you always run the risk of running into it. It would be better to simply put all the data on sd, there would be no performance hit and the problem is permafixed. As an added advantage all your texts are backed up locally and with just a little more coding could be set up to be restored as needed when the app was reinstalled on the same or new device.
Click to expand...
Click to collapse
The SD way would be a straight road to hell, since all the data can "disappear" from under your arse at any random moment.
It's enough just to plug-in the USB cable or simply pop-out the card (easily doable on many models).
Even worse: someone can easily delete anything on the card since it is a stupid FAT32 with no permissions whatsoever. O just insert different SD card from the different phone. It is far from trivial to define what should the apps do in this case.