|
||||
Your program memory goes down because OEMs sometimes need to make copies of the files in different paths or with different names than those found in /windows - the copies consume program memory (done via initflashfiles.txt or provxml).
You provxml looks like it's missing the enclosing <wap-provisioningdoc></wap-provisioningdoc> You can't move ROM files, you can only copy them. Not sure why you're having intermitent success/failure with initflashfiles.txt. I suspect it's something your doing. The syntax looks correct. |
|
||||
Thanks for the quick reply!
That was a excerpt from a provXML, I have the <wap-provisioningdoc></wap-provisioningdoc> enclosing the whole file. So, Just to clarify: EVERYTHING in my ROM is installed\locked to \Windows, Then shortcuts, templates, etc are COPIED to the appropriate directory? |
|
||||
That's exactly right. Here's how to think of it.
You are creating a read-only image when you run createrom.bat. Think of it like creating a CD or DVD image. Once it's created--that's it. Therefore initflashfiles and provxml are just copying files from that image to the storage partition on your device. This is why you want to try to avoid too much of that--otherwise the advantages of "baking" that app into your ROM are negated. |
|
||||
OK, I was under the assumption that the initflashfiles was executed during the ROM build, not at boot time on the device.
Any info on the structure of the imgfs image? Does it support subdirectories, etc. that could be integrated at build time? |
|
||||
I'm sure there is documentation somewhere (maybe in the PPC SDK? Not sure). But no it is a flat file structure, and is all located in \Windows. Literally every other directory and containing files you see on your device is created on first boot and is using up space in your storage memory.
|
![]() |
|
|
|