[P3600 ROM Development] the.decoy:
Hey guys! Sorry for going off the radar like that ... I was initially just too busy on weekend to get on forum, and then on Sunday night I came down with a real nasty flu. :( Been off work and too sick to even concentrate on a screen at home since then.

I did finally get back onto xda for a few hours yesterday (thanks mostly to Dayquil, lol) and I am back at work today. However taking an unplanned 4-day weekend has got me rather backlogged with work, so I apologise if my progress is a little slow for the next week :o

I did get one good thing done yesterday however ... (see end of post) :D

Thanks for answering Q's while I was gone Super, much appreciated.

While the GWES.exe in 6.5 does seem to keep evolving from build to build, I do think that infamous "6.5 memory leak" is far less dramatic than in the past. There are still the odd bad build versions where it is noticeably bad but now it mostly comes down to properly closing apps (HTC Task Mgr) and effective Slot 0 optimisation.

And YES, as SuperSport mentioned, I have been working on the Slot 0 situation for a while now and I am no longer aiming at the "free as possible" benchmark any more. All my (recent and future) Kitchens will now come setup to build ROMs with ZERO Modules in VM Slot 0.

In short this means I am recmod'ing a very large number of the modules in the SYS packages. All of which then need to be loaded into memory/vm at load/runtime. However I am trying my best to optimise exactly which modules get to stay (and fill up as much of Slot 1 as possible in the process).

Frankly with the tiny 64MB (effectively 55MB) of RAM our devices have available, I don't see any other choice than to make sure the full 32MB (effectively 30MB) of VM in Slot 0 is left free to support the "Active Process" and its memory requirements.

A few apps may seem laggy the first time your run them but at least they will (hopefully) run smoothly :)

Whoa! That thing is stripped naked! hehehehe :p

I suspect you might have gone a little too far and that explains some of the broken things like Camera (remember that even the devices that these SYS builds are ported from did have a bunch of OEM packages too, that are necessary for device specific functionality, eg: camera, gps, bluetooth)

Anyway, it was still a very cool little experiment and it saved me having to do all that downloading/unzipping to get a QVGA 23064 SYS setup :D

One reason it ran so heavy on memory was probably the ~8MB of VM in Slot0 that was being used for modules:

You seem to have done at least some of recmod'ing I usually do, so I have gone through your 23064 SYS and recmod'ed the remaining modules required to squeeze it back into Slot1 only:

However, that isn't all I did to your "skeleton" kitchen ;) ... since it seems we are now quite actively building ROMs for both TRIN models, I have taken your bare kitchen and used it as the basis for a unified P3600I+TRINITY Kitchen.

This was already in my roadmap for the kitchen anyway, but seeing just how many "hex hack" ROMs you were having to do convinced me that I should get it done before any more efforts get duplicated.

No offence to your "superlite", but I do actually plan to put most of the existing EXT packages back into the kitchen before doing a proper release. However for your own purposes, here is a base to build your own kitchens from - that has all the build scripting, HTCRT configs, XIP and OEMs required to build for either model of the TRINxxx family (no more hex edits required). :D

Kitchen_WWE+FRA_23064_P3600I+TRINITY (SuperSport beta version)

I am running on a ROM built from it right now (that memory map I posted above) ... but I must stress

this is just a test kitchen/rom

:eek: ... it has many many missing features, apps, plugins, etc etc. I am posting it for SuperSport (and any other chef who just needs the Kitchen structure to build on).

LOL, but the Camera works :p (actually that is probably because I put most of OEM back in there, hehehe) ... it just doesn't have an app to start it. The only way I can get the camera up is by going via "Pictures & Videos".

I have dumped your 2 EXT packages and just a handful of example EXT packages of my own into \EXT\SHARED\External_Packages\

My plan for future build is to put

everything

(in EXT) under \EXT\SHARED\ (unless it is a fix/mod that is either device-specific or version-specific). Then we will choose the "6IETIT" or "8IEMANTIT" ROM flavours by loading pre-built ERV files from the "Load ROM" button (which then enable/disable packages to suit that ROM).

Check it out and let me know what you think :)

Cheers,

-Decoy