[ Discontinued ][ v4.2 ][ 6.5.x / 6.5 / 6.1 ] Calkulin's Visual VGA Kitchen & ROMs

[lunacie]

Originally Posted by jdm627

Where?

I'll create a new thread in CDMA upgrades, but I'm not quite there yet. Still need to get the HTC Twitter client, MMS, and this pesky calendar 'new appointment' issue worked out.

Also, I'm pretty new at this, so don't expect my ROM to be quite as flashy & superclean as some of the real luminaries here can produce. I won't really be supporting it other than just working out the kinks as I'm able - I have a pretty hectic work life, and only so much time to devote to the ROM. And though mine's coming along nicely, it's probably total amateur/noob stuff next to Calk, NRG, Indagroove, etc... as I'm really just learning my way through this as I go.

[vernox701]

Originally Posted by omahajs

?? I was just going to ask this question. I'm on a vzw tp and I have no where near the free memory you are talking about. I disabled almost everything in the kitchen except manila and menu enhancements, a few apps, etc. but I only have about 18-20MB free. This is when running manila after I scroll through all the tabs, update weather, etc. I can't even browse with opera for more than a few pages before my device resets because of no memory. The cooked rom I'm running right now is only 113MB so I'm not sure how else I can make this thing any lighter.

Now, I do have quite a few apps installed - are these taking up my available memory?

If I post my erv file can someone who knows what they are doing help me out?

Here is a screen shot so you can see I am not just making up stuff. I am running about 43.25 megs in TF3Dand free before active sync and my mobler connect to my device Screen04.jpg

[lunacie]

Ok, so it looks like I had some bad package conversions (old style to new style kitchen mis-conversions), but I managed to muddle my way through and get things working.

So now I've got a 23506 build with Manila 2.5 (latest Leo). I'm going to chew on it for a few days, but so far so good.

[somken]

So, I fixed my other issue, ..., but I have yet another one.

When i open the dialer, i get this.



any ideas?

[sc00b4s7eve]

Originally Posted by somken

So, I fixed my other issue, ..., but I have yet another one.

When i open the dialer, i get this.



any ideas?

Did you just disable TFlo3D? and had you slid the keyboard open & closed yet?
Is it the stock dialer? did you pick the correct phone canvas there are only two for rhodium phone canvas. Really, idk. I can't spot it off the top of my head.

[welrope]

any news on mms with the new htc client. I have it sending, but to where i don't know. Have my build of 506/2.5 done and I have to say, this is the only bug i have left. bg4a, twitter, my location, calander, opera 9.7, and it is set up for all the "location" features to be active off the flash...and on top of this im getting a full day out of a charge! Ill try to post some screenies shortly.

[omahajs]

Originally Posted by vernox701

Here is a screen shot so you can see I am not just making up stuff. I am running about 43.25 megs in TF3Dand free before active sync and my mobler connect to my device Attachment 48757

I wasn't doubting you, I was asking how? I'm just trying to figure out how I can run tf3d reliably without memory going down to 15-20 free.

Again, my rom is only 113MB (6MB PP). I just soft reset into titanium and after everything is loaded I'm sitting at 35MB free.

[Asphyx]

Has anyone gotten a 21055 rom cooked with this kitchen to boot?

[welrope]

Quote from 2nd post

"Make sure to check Real WM 6.5 AKU for ALL SYS
when building or IT WILL NOT BOOT"

that should fix it

[sc00b4s7eve]

Originally Posted by nomad_delta

what are modules all about anyway? never quite understood what the whole "files to modules" converter thing was for, or whether I ought to be using it...?

--nomad_delta

Originally Posted by mwalt2

If you use the 6.5 kernal for your CDMA TouchPro, then you don't need to be concerned about modules. I think you just need to click the 'real wm 6.5 aku' box in the kitchen (though I'm not 100% since my lowly diamond is still stuck with the 6.1 kernal).

Are you sure about that mwalt? 'Cause Da_G wrote this: http://forum.xda-developers.com/show...37&postcount=2
"When you create a module, you are telling Windows Mobile that you want that module to be memory-mapped, so that each time it loads, it's loading to the same, known area of ram - saving space in slot 0 - this is done on the computer-side, during 'cooking' and is the job of wmreloc, g'reloc, bepe's Platform Rebuilder, etc. Virtual allocations are aligned to a 64KB border, so if you memory map a .dll that's only 3Kb large, it's still going to eat up 64KB of memory space.

There are also pages that can be allocated to these slots, that are aligned to a 4KB boundry, and process/general allocations that take place during normal operation. The way the system handles this is that modules allocated on rom build-time (modules we allocate with g'reloc et. al.) are allocated from top-down (for slot 1 for example, starting at 0x03FFFFFF for the first module, taking up space to the nearest 64kb boundry, then the next module, in a line down to the 0x02000000 address, which is the beginning of the slot) - General allocations that take place during normal system operations are allocated in the remaining space, from the bottom-up (so again with slot 1 as an example, starting at 0x02000000 and ending at 0x03FFFFFF) - As you fill up these slots more and more with modules, that leaves less space for windows to dynamically allocate other, general allocations, which can, and does result in out of memory errors (even when the device has plenty of physical memory left, it cannot address this memory when virtual memory is full)...

...WinMo 6.5 improves on this by opening up Slots 60 and 61 to Modules - yielding an extra 64mb of potential Virtual Memory space. (the allocation order is now 1, 61, 60, 0 for modules, 60, 61, 0 for files) - In order for the Kernel to recognize these new Slots as being mappable for Modules, it must be updated to the 6.5 codebase. This is where the 6.5 nk.exe comes in, and why it's so important."

I think I've actually made too many modules, and I'm getting some weird memory leaks (only when I run programs though, LOL, the OS, itself, is solid)