mine XDA I having total 32MB memory allows for moving memory tab in
start/settings/system/memory
between STORAGE and PROGRAM options so that it divides in-bulit memory but .... I am curious about one thing, I have just noticed that today - if I assign too small amount of memory for STORAGE (i.e. it automatically put the division tab sback in a way that memory is split in halfs (50:50) considering current utilization od PROGRAM part
the question is .... is it a limitations imposed from OS manufactirer ??
regards, monika
seems like similar issues have been covered here ... sorry for double posting
http://forum.xda-developers.com/viewtopic.php?t=5660
regards, monika
Related
===============================================
I used to use this program to gain space in Nokia :
"Stacker" is the best, fully automatized and reliable compression system for your device. Stacker software doubles the size of your entire drives and works invisible behind the scene. When you start any compressed application it becomes decompressed in background automatically and it becomes compressed again when you close it.
"Stacker" is the best way to increase disks space on your device, it guarantees to give you as much disk space as possible without you even thinking about it!
===============================================
Is there a software that could do the same job of stacker in the XDA?
All files in RAM are automatically compressed by OS itself. You may check that yourself for example by placing a big text document to the root directory on the device and checking the free space change.
There are several programs that compress data on storage cards. For example http://www.pocketgear.com/ppcw/software_detail.asp?id=14226 (I don't know would it work on XDA or not)
Mamaich,
I wanted to thank you for the reply..StackDriver works with any ARM-based Pocket PC device thus it compresses every files in our Storage Card it's a good program but I'm no interested since my Sd is locked while its in the XDA bcz of Sd erasure caused by the WM2003.
pflatlyne said:
Looking back at it,im not so sure anymore. I looked up some information on how the virtual memory in windows mobile works. It seems that whether a program is kept in memory depends on what kind of memory it is stored on. Programs that can be reloaded from flash will be unloaded if needed. Data structures that programs keep,will not be becuase there is no way to restore them.
It might well be possible to swap some of these things out to the transflash card. In fact,vista does something similar with readyboost. Ive actually used my phones card as the readyboost device without problems. What might be a problem is the speed of the card reader in the phone. Some people say the reader is very slow. I dont know if this is true or not,but as a general rule,the card itself is faster than a hard disk,so its not at all unreasonable. One problem of course would be wearing out the flash. Readyboost uses a special algorithm to spread the writes across the drive and reduce the amount of writes. If you just put the swap on flash,it would wear out rather fast.
Click to expand...
Click to collapse
Ive decided that this might not be so crazy as it sounds. This was originally discussed here. http://forum.xda-developers.com/showthread.php?t=350002&page=15
Consider this: http://blogs.msdn.com/ce_base/archive/2006/10/30/What-is-Virtual-Memory.aspx
Now direct your attention to this part from the above link
<QUOTE>
Windows CE will “demand commit” pages, meaning that it will usually delay committing them until the last possible moment. There are also some cases in which Windows CE will take committed pages out of memory again, returning them to “reserved” status:
* Since DLL and EXE code can easily be re-loaded from the file system, it is often decommitted.
* Memory-mapped file pages also have well defined files to read from, so those are decommitted as well.
* Thread stack can shrink; if the system is very low on memory we’ll scavenge the top pages from a stack if the thread is not currently using them.
* Heaps can shrink; if the system is very low on memory we’ll check whether there are heap pages without data in them that can be decommitted.
However that is where Windows CE stops. Other operating systems have a “page file” in which they will write other pages that don’t have corresponding files, notably:
* Stack
* Heap
* Allocations from VirtualAlloc()
* Memory-mapped files that don’t actually have files underneath them (CreateFileMapping with INVALID_HANDLE_VALUE)
* The writable data of executables (global variables)
Those operating systems have algorithms to decide that these pages have not been used in a while, and will write them to the page file and decommit the RAM. Windows CE does not have a page file. We’ll demand-commit to delay committing these pages as long as possible, but once they are committed, the operating system won’t page them out again.
So, as you see, virtual memory in its most minimal definition is just having a mapping between virtual addresses and physical addresses. To lay out allocations in the address space in an efficient manner and avoid wasting physical memory on unallocated address space. In more practical terms, we also use the virtual address space to implement paging, avoid wasting physical memory on allocated addresses that are not actively being used.
</QUOTE>
Here is another interesting article.
http://blogs.msdn.com/ce_base/archive/2008/01/19/Paging-and-the-Windows-CE-Paging-Pool.aspx
Consider:
<Quote>
I’d like to explain a little more about memory management in Windows CE. I already explained a bit about paging in Windows CE when I discussed virtual memory. In short, the OS will delay committing memory as long as possible by only allocating pages on first access (known as demand paging). And when memory is running low, the OS will page data out of memory if it corresponds to a file – a DLL or EXE, or a file-backed memory-mapped file – because the OS can always page the data from the file back into memory later. (Win32 allows you to create “memory-mapped files” which do or do not correspond to files on disk – I call these file-backed and RAM-backed memory-mapped files, respectively.) Windows CE does not use a page file, which means that non file-backed data such as heap and thread stacks is never paged out to disk. So for the discussion of paging in this blog post I’m really talking only about memory that is used by executables and by file-backed memory-mapped files.
</QUOTE>
In short,people are comparing transflash speed to ram speed,realizing there is a vast difference and deciding it wont work. The fact is,the OS is already using virtual memory. It is just not using the transflash and it is not paging certain structures. It still may not be possible,but I think its going to be more of a matter of getting the OS to handle it rather than a speed thing. The quick easy and vastly oversimplified requirements would be to some software on the phone that would create a paging file,manage that file so as not to wear out the flash to fast,and do all the back end work necessary to swap them in and out. What is not clear is how much we can use machinery the OS already has.
Im now going to go into the realm of unsupported speculation. Could we perhaps have a program that manages the paging file(we will call this the page file manager). Its job would be to create a virtual file system inside the page file. Then we could set the pages that are ordinarily not pageable (through some magic algorithm that knows what we REALLY want to not page,and what we can get away with paging to the file) as pageable. I imagine we set them as "file backed" and allocate a virtual file inside the paging file.(our page file manager would manage this for us). The machinery of the OS might then handle all the paging for us. Of course the fact that these structures are writeable would be an issue. Writes to a page would cause an exception and the modified page would be recorded in the virtual file system. Like I said however,this is very early speculation,not even to the level of a plan. In short the idea is to take data structures,make a file for them somewhere,and then make the OS treat them like any other file backed memory page. It sounds almost plausible,doesn't it.
Still more speculatory rambling. I imagine the paging file manager would manage the list of free pages in the page file that are allocated to files and the free ones that can be allocated. It would also manage the order in which they are used,to spread the usage around as much as possible to extend the life of the flash card.
It would go something like this. A data structure is to be paged. A virtual file is created in the paging file,allocated to the size of the data structure to be paged. The structure would be copied to the file and the pages uncommitted. A read to the virtual memory pages would generate a exception and ultimatley cause structure to be reloaded. A write would generate an exception and cause the file to be updated. Page_file_manager would handle this. It would allocate the next available block to the page. It would then update the file allocation table to reflect the replacement of that block in the file and release the original. Of course this all really depends on the internal structure of windows mobile.
It’s possible to move all Mails (Outlook folders…) and Attachments’ to storage card, because don’t any memory place in my phone.
Any Help is welcome…
Thank’s
Just look at this site:
"Low Memory Warnings on with Windows Mobile 5 Smartphone?"
http://mike.temporale.com/archive/2006/09/23/176.aspx
Not every tip on this site is working, but I think your question is answered.
As i'm a new member,i can not ask geowolf1000 question for malata_t8_smba_9701_cm9_3g.So i hope i could get reply from here.
First i would like thanks geowolf1000 very much for his great work.
After i flashed my T8 into malata_t8_smba_9701_cm9_3g,the performance is amazing!Very fast than before!
But i have some question as below,
1.Max CPU speed is 750,it should be 1G.How could we set it into 1G?
2.when i connected it into PC,how could i set it as a large size storage model ?Because when i copy a large size file into it,it takes so long time if it can not be set into a large size storage model.
Hello,
I am working on an Acer Iconia B1-A71 at the moment.
I managed to unlock the BootLoader, thanks to @FireDiamond ) & I also managed to root it, thanks to @entonjackson ).:highfive:
Now I'ld like to increase the memory dedicated to applications.
I know that I'm able to swap internal & external storage, but what I'm willing to do is increase what in the settings is called "applications memory".
Talking with a friend we thought that repartitioning internal & application memory, & then swapping modified internal with external memory, would grant lots of application memory & lots of internal memory.
Is this possible ? what should I use or do to achieve this ??
Thanks to all the comunity!!!
P.S.: More specifically:
App 1GB, Int 5GB, Ext 30GB =Partition=> App 5GB, Int 1GB, Ext 30GB =Swap=> App 5GB, Int 30GB, Ext 1GB.
My useless opinion:
So, what will you do with that increased memory? I thought only about games with large cache like Dead Trigger (about 0.7 Gb) or apps that require a heavy amount of memory like cSploit+MetaSploit Framework+Ruby (about 3 Gb).
Did you know we need another resources to get apps working, like RAM and CPU? That's why I bolded RAM - we need to increase it first!
I did a little research earlier:
(tablet status) — (free RAM in standby mode, total is 480 Mb)
1. Full stock RV04RC04 — ~90 Mb
2. Stock, DVM heap 30 Mb, Smart Launcher v2 — 130 Mb
3. Same as 2, but with removed bloatware and stock launcher — 150 Mb.
Now let's check minimal and optimal requirements for some apps:
Minecraft PE — 64/128 Mb (passes)
NfS: MW — 100/250 Mb (passes on minimal graphics)
GTA: SA — 300/1024 Mb (passes veeery laggy on minimal graphics then crashes)
DJ Studio 5 — 500/1024 Mb (btw it passes, so strange!)
Firefox (even Beta) — ?/? (crashes on second opened tab)
Also, when playing some heavy games you can see that ugly LOW MEMORY sign in edge of screen.
What we need to make:
1. Custom kernel with another compression and enabled 2nd CPU kernel (it's disabled forever with stock one).
2. ROM with a high RAM economy, so we can use free RAM in heavy apps.
Unfortunately, I don't think we are able to do it, because there are no many developers who ready to work with Iconias; anyway we have devs, but in the most cases we can't co-work because of "language barrier". I know some guys from 4PDA, they can look on the B1-A71 if I ask them, but we need more than only 2 russian devs to make all that stuff...
Now about your problem with memory swapping
Use google: android create vold fstab
@FireDiamond
I know that RAM is needed & I noticed it had quite a low amount.
The owner ( a friend of mine ) wants to have a bit more app memory because by installing the few apps she uses, it fills up pretty fast.
She uses it to read some pdf, browsing & play low level games as Fruit Ninja or any Saga game.
I'm searching now on the keywords, thanks for them.
Probably it would be enough to set 3GB for App & 3GB for Int storage, though if possible, it could be more usefull if I also did the memory swap, in which case the "Ext" storage ( = Int memory left out of App storage ) would be useless since there would be an "Int" 30GB.
That is why I thought of giving everything to App memory.
EDIT: I searched a bit about thevold.fstab & I recognized that it is usefull for swapping, which I will do following an other topic. What about resizing interanl memory partitions ? Does anyone know what I could use ?