[P3600 ROM Development] the.decoy:
Wow, thanks a lot Super! :)

Well firstly ... Yay! it boots! :D

Everything else we can fix but if the base kitchen I put together didn't make a bootable Trinity then I was stuck.

As for the first boot & customisation, that lengthy wait on first boot is "normal" for these ROMs (as you say, probably due to all the bloat) ... however that customisation problem sounds weird :confused: It shouldn't take that long at all to process the included config.txt as it barely does anything. I did just discover that in the Trinity config.txt there was a call to the HTCBlack.TSK (which I had removed for COM3 compatibility) so may be that was it?

Actually that is exactly what I have been slowly trying to work towards ... however because I am still technically maintaining the "Chanvi+oggi" kitchen I felt obliged to not immediately remove anything unless it was incompatible, deprecated or broken. Other than adding Titanium Weather and AT Fave People to CHome, I am not adding anything that Chanvi didn't put there.

That said I have every intention of giving the EXT and OEM setup a complete overhaul ... I just hadn't got around to it yet because I was concentrating on coming up with the best process for optimising the port of new SYS builds.

As I'm sure you know, all the 6.5 builds are very much built for better resources devices than ours and so there is much recmod'ing (and even some package removal) required just to make them run on a TRINxxx.

I want to eventually have a kitchen I have assembled from top to bottom ... so I started the bottom :p

Anyway, I am very nearly finished that bottom layer as I have nice empty Slot0 VM, with almost all SYS components still included, I have changed over to the newer initflashfiles.dat to get back to the "what MSFT intended" setup, and I have built my own Ervius VK to run it all on.

The only thing left now at the SYS level is to identify a few more components that are not viable for our hardware and can be removed (eg: MSTag which requires a higher res camera than we have, VoiceCommand which uses substantial memory with little or no functional benefit, etc).

Additionally I am starting to use Task Manager to examine the memory addresses of all the active modules in use by GWES and shell32, to see if there are any modules I have recmod'ed which then just end up back in SlotO (or worse still RAM) because of "Current process" allocation. Effectively seeing if there are any modules would better recmod'ed than those - to make sure that everything that is always running is in Slot1.

Funnily enough I don't think this kitchen has gotten any more bloated, it is just the newer builds that get a bit slower.

Oh cool! I have been meaning to quiz you about what tweaks you are running in those ROMs of yours.

Question: What Trinity kitchen did you download?? I had removed the one that was linked ... did you find the newer one by just looking in the mediafire folder?

I am very keen to see this modified version you have done ... but as I said, the hex-edit alone ends up very badly on our "i" devices (it may take a few days but then corrupts savagely :eek:).

Any chance you could zip up copy of the modified kitchen for me? Or just an ERV project file (if all you did was disable components)? Or even just detail the changes you made?

Thanks heaps for your help with this Super! My biggest problem lately is not having free time to work on this stuff (I barely slept last night to get the P3600i updating done), so any assistance with the optimising is most welcome.