WM 6.5 Kitchen QVGA and VGA Developer Edition

[dan-htc-touch]

Originally Posted by joojoobee666

Well, that was easy. taskmgrCustRes.dll only has icons, so that was probably my problem

HTC Task Manager is now running as modules/XIP after recmodding that dll.

yeah, graphic resourse only .dll's don't like to be modules

[joojoobee666]

Originally Posted by vickylife007

Wow, wow, wow!!! Learnt so much reading your dialogues, Dan and Joojoobee. But aint you guys forgetting something, today is THURSDAY. Aint we supposed to be expecting two drops today as in two major leaks? We've been anticipating.
And trust me no amount of xip, modules, files, rom and ram talk is "distractive" enough (permit my english".
Whet our appetites a bit, what's happening to those leaks?
Hey Joojoobee what about that cure we talked about?
Just another leak, that's all we ask for.

True, but all of this work will not be lost on a new kitchen since this is for my User OEMs.

[joojoobee666]

Originally Posted by dan-htc-touch

yeah, graphic resourse only .dll's don't like to be modules

Yup, and that was proof

[aaronpoweruser]

ok i have 13-17 on boot after running oxis mb free in high memory mode on my titan in 2102 i had about 24 but i didnt have as many oems
also after letting the phone sit for 10 minutes opening no apps but start to get to oxis i am down to 16-13 is there any oem known to cause a memory leak?

i atached my oem selections

[gguruusa]

Originally Posted by joojoobee666

I did just manage to come across this little tidbit:
"The advantage of XIP modules comes into play when one considers the limited amount of RAM available on a typical Windows Mobile device. XIP modules are pre-relocated to a guaranteed available base address, and do not require any runtime alterations to their backing memory when mapped. As a result, XIP modules can be backed entirely by ROM and not RAM, decreasing the (scarce) RAM that must be devoted to holding executable code"

So, if I am reading this correctly, it would be advantageous to convert ANY program/dll that needs to stay loaded/in use for the entire boot into a module. This should in essence free more RAM? (HTC Task Manager is one example, Arcsoft being another, and possibly even some phone/canvas related resources)

You are reading incorrectly.

First, unlike regular loading, xip modules have larger boundaries. Loading a code section that barely fills a region is very wasteful.

2nd, "Freeing more ram" is a misleading synopsis. What you are doing is consuming less RAM than you would if multiple programs needed the code section. You are consuming more memory than if no program needed the module.

3rd, scarce resources can be an issue when consumed by never-unloaded xip modules.

The moral: don't convert everything to xip. Candidates for conversion are things which are a) used frequently b) used by multiple programs and c) have code sections just under the boundary size.

[gguruusa]

Originally Posted by aaronpoweruser

ok i have 13-17 on boot after running oxis mb free in high memory mode on my titan in 2102 i had about 24 but i didnt have as many oems
also after letting the phone sit for 10 minutes opening no apps but start to get to oxis i am down to 16-13 is there any oem known to cause a memory leak?

What makes you say leak? A leak is something that continues to consume until you have none left. There are many reasons for memory to be "consumed" at any given time, regardless of whether you are doing anything.

There's a reason why punctuation is taught in grade school. Make punctuation your friend.

[aaronpoweruser]

Originally Posted by gguruusa

What makes you say leak? A leak is something that continues to consume until you have none left. There are many reasons for memory to be "consumed" at any given time, regardless of whether you are doing anything.

There's a reason why punctuation is taught in grade school. Make punctuation your friend.

i say leak because it continues to go down till i have 3-4 left and have to restart

[aaronpoweruser]

Originally Posted by joojoobee666

Ahh ok, that makes sense. I already converted Arcsoft and Etphone.dll to modules in hopes of gaining some performance from it. So far, my text messaging does seem to be a bit more responsive (I guess it could be placebo). I am going to pull HTC Task Manager from the Geeks OEM, change the GUIDS and convert it as well. I guess I will see how it goes.

Do you know of why this would be a bad idea? Am I at risk of running out of slots for the modules?

u wouldnt happen to know a link to a tutorial to do this

[joojoobee666]

Just for the sake of curiosity I converted my igo8.exe into a module and cooked it in. When I run it from the windows folder, igo8.exe opens up in half the time 10 secs as opposed to 20 secs), and leaves almost 4.5MB of free RAM STILL! When I run it from the storage card, it takes 20secs to open up and I have .5MB free. Holy sh*t!! eXecute In Place can really make a difference

Thanks again, for clearing all of that up for me Dan and Conflipper!

[joojoobee666]

Originally Posted by gguruusa

You are reading incorrectly.

First, unlike regular loading, xip modules have larger boundaries. Loading a code section that barely fills a region is very wasteful.

2nd, "Freeing more ram" is a misleading synopsis. What you are doing is consuming less RAM than you would if multiple programs needed the code section. You are consuming more memory than if no program needed the module.

3rd, scarce resources can be an issue when consumed by never-unloaded xip modules.

The moral: don't convert everything to xip. Candidates for conversion are things which are a) used frequently b) used by multiple programs and c) have code sections just under the boundary size.

Yes, I understand I run the risk of killing my VM after some further reading. Is that what you are referring to?

Also, point 2 is WELL received. I noticed LESS ram after a clean boot. But loading programs that I XIP'd consume less now when running (see my iGO victory which is my main concern here. I use it alot and have to FREQUENTLY reboot to free up enough RAM. The executable is 5MB which is 25% of my free RAM alone. I know, it's probably an awfully large exe to be converting to a module, but what's the worst that can happen? A recook? Just another reason to do so....)