Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Ok, I have a workaround for your issue, Zecanalis. You can replace the default battery icon with a battery icon which has a percentage inside it, so that you don't need to worry about going to the Power settings to see the value.

Here's one I used:
http://forum.xda-developers.com/show...79&postcount=1

There's probably a nicer QVGA one, but this does the job.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

So basically there is no difference as far as the SYS and OEM files since they are not in the XIP. They can either be a module or a file without any performance gain/impact?

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

i cant change the notification settings in 21501
it opens but when i click ok it reverts to default and doesnt close the app

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

I had this problem as well with one I cooked in the kitchen. Don't know what was causing the problem cause I left some things out and did a recook. Now the problem is not there. I did change comm manager on recook. That was the only thing I changed other than add more oems. Don't know if that was it or not. Had 10 button and on recook did not select any.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

right now i dont have any comm cooked in
i like simplisty and more ram :)

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

wrong, your confusing xip with xip-section, xip is not limited to the xip section

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

I'm sure I am. The XIP does contains modules that run in XIP, but any other file that is in the imgfs as a module would run in XIP as well?

So do recmod and reversmode play into this at all? I was assuming that these convert files to modules/modules to files. If this is the case, would I be correct in assuming that by converting some of my files to modules with reversmode that the program/dll would then run in XIP, not freeing up more RAM, but opening quicker?

Sorry for all the questions, but I am STILL unable to find a good read somewhere with the whole breakdown.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

from what I can tell, the reason for having a xip section, is to make it possible to handle the xip in a different way.

excerpt from MSDN:
Windows CE allows you to create multiple execute in place (XIP) regions in one single operating system (OS) image. XIP regions are areas where an application can execute code directly from read-only memory (ROM) rather than having to load it from random access memory (RAM).
With a multi-region image, you have finer control over the image layout, you can control region updates, and you can decide on a per-region basis how the OS will access that region when it pages its components at run time.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

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)

And just going one step further, the XIP layout is what WMreloc is actually doing. It is creating the imgfs and XIP maps?

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

I had same problem with build 2500.
And when i resolved i didn't achieved any conclusion.
I changed somethings in my OEM folder, but at the end i replaced everything or almos everything back to the begining and all worked well... ](*,)