yashsingh1/xdaforums huggingface dataset:
[P3600 ROM Development] SuperSport:
I will try them now. Great to hear new version coming.

"WWE_23060_TRINITY_8IEMANTIT": Flash was Successful - Boot Successful. Took a LONG time to finish booting 1st time (2+mins). Probably due to size - Customization LONG Winded and NOT Successful - Hard Reset Successful ;) - ReBoot Successful. Took a LONG time to finish booting 1st time (2+mins). Probably due to size - This time, I left USB Cable on so phone would not sleep. Customization LOOONNNNGGG Winded and Successful (5mins+ Be Patient, it will finish.) - My guess is the Customization adds a LOT of stuff. :confused: - Reboot Successful - Mortscript Window pops up as mentioned. - Runs Quite Smoothly! Although, only about 13-14MB free. :eek: I'm sure on your slimmed down version, this will be fine. Titanium Weather Settings errors out. (Unauth Access Exception)

I think for a Light Version, I would try to leave it as "Microsoft" as Possible. No added software, and No removed software. So people can see what Microsoft intended with this build. If you are working on another version, I may try to create this. ;)

I'm impressed. A True Gentleman. :)
[P3600 ROM Development] the.decoy:
Uploads are finished.

New and improved 23060 Kitchen & ROMs available on First Post

As soon as I can work out what is happening with the Trinity Kitchen I will get some new links up for that too (thanks to SuperSport for assistance).
[P3600 ROM Development] SuperSport:
I'm still running it and trying things out. I've got Wi-Fi running, and it all seems smooth, although I've only got 10.98MB Free now, but no lag yet. Edit: Downloading new Kitchen Now.
[P3600 ROM Development] SuperSport:
the.decoy; Using your Kitchen, I just cooked a Lite Version of your ROM. It's much more usable on the Trinity, and still keeps your COOL looks. :cool:

Edit: on the Trinity, 23-24MB Free Ram

Download either Trinity or P3600i versions below (P3600i is the .bak one):

Download

I only HEX edited the Trinity Version, but so far, I have yet to have any trouble with this method. Please use at your own risk.
[P3600 ROM Development] SuperSport:
the.decoy; I just got home, and my wife will be right behind me, so this will be short for tonight. ;)

Most of what you said went right over my head. :o I really am new to all this, and am struggling getting my mind around it all.

The two RUU files I listed were cooked using YOUR P3600i kitchen (Linked), and then I Hex Modded the one for our Trinity. So, you can use the .bak version on your phone without issue.

You are so far beyond me on this stuff, but I would be honored to help in any way I can. Tomorrow, I will try to answer more clearly.

Thanks again for all your hard work, this latest one is REALLY running well on my Trinity. Memory stays constant at 23-24MB with no effort. I've now installed MotoSurf on it, and it functions like it should. (Pretty neat Home Screen if you don't need a lot of free memory.) I think I'll be trying to cook a MotoSurf version that is tweaked to get the most RAM and usability as possible and still maintain all the MotoSurf features.

PS: I like that you are preserving Changi & Oggi's Kitchen. They did such a great job of creating it for us.
[P3600 ROM Development] the.decoy:
hehehe yeah that's why I started so late last night too :o

Oh cool, I will do that now. Still is there any chance you can tell me what you did to it?

If it was just a matter of disabling packages in Visual Kitchen, you can save that setup as an ERV file with the "Save ROM" button. It asks you what filename (using \Tools\RomSaved\ folder by default).

The ERV file is just a text file with the list of all enabled/disabled packages and what version IDs were used for XIP/SYS. You could easily attach it to a post here.

Also, did you change the page pool size? I am pretty sure you and Tomme are using them as low as 4M but I have been sticking with 6M so far because it seems to make more efficient use of that extra 2M that just leaving it as available ram.

Our devices are so drastically short on memory that I figure we will never have enough of it "free" ... so I concentrate on making the OS run stable with ~10M ram free (since it always seems to end up around that mark anyway :rolleyes:) by optimising VM and PP.

EDIT: OK, I have flashed that uber-lite ROM now ... OMG! That is seriously cut down to bare bones :eek:

Still curious as to what the full list of things disabled was ... but I suspect that you are gaining a tonne of ram as soon as you ditched CHome and all those BT packages.

LOL, can't say I am a fan of going that lean ... sure it runs really quick but I am basically back to the wm6 I had originally (albeit with a new Start Menu, task bar and window UI elements).

Even still it nice to see the fruit of all my optimising so clear when you strip away all the memory hogging packages that are going on top. Nice work :D

I think I might put together an ERV/EXT config that builds this ROM but give the option to cook the old "HTC Home plugin" into it so that you at least some kind of home screen with msg, launcher and weather widget
[P3600 ROM Development] SuperSport:
I just snuck into the office for a sec. ;)

Yes, I'm using 4MB PP. I've heard that it works better for the Trinity due to our lower initial RAM. I will try one with 6MB though and see what it feels like.

Here is the erv file (change ext from txt to erv). Yes, it is lean, but I was making it so that someone could run SPBMS 3.5 or MotoSurf on it and still get performance. Using your Kitchen as the base, it worked well. It still needs a lot of optimizing (on my part), but I just did a quick and dirty version. I THINK I only turned off items in the kitchen, if I remember correctly.

I notice a couple duplicate icons and such that I will be able to help you track down and remove. And possibly cut down on the folders in the start menu, combine a couple? I also saw somewhere when somebody used Folder icons with smaller images on them so you knew when you were going to a folder as opposed to a program (See attached Icon, this sample is for Communications). Might be a nice touch. I can make those if you know how to enable them?

More tomorrow. :D

PS:

Great Idea! Super Fast, AND Functional.
[P3600 ROM Development] the.decoy:
Yeah I have tried both but I must admit that I went to 6MB back on older builds when we had lots more memory leakage ... might be worth trialling 4MB again.

I can definitely see the advantage to 4MB PP on these superlite builds where you aren't in as much danger of running low on real RAM and need to turn to PP mem.

Cool, got it. I will load that up and have a look (it helps even just knowing what packages the ROM can live without and still function).

Yes, again I am already in the middle of unravelling all the various app.dat & provxml files (and entries in initflashfiles.dat) that Chanvi had used to do that to the Start Menu.

When I changed over to the new initflashfiles.dat I have inadvertently created a few dupes because of the multiple ways in which they were being relocated in the old kitchen.

You may have noticed that I modified the redundant "Utilities" folder (created by the CHome plugin packagess) into a new "CHome Utilities" and assigned it an icon.

I also want to get rid of "ShortCut" and examine the need for keeping both "Tools" and "Utility". I think GPS, M2D and Internet are useful enough to stay.

Anyway it is a juggling acting trying to reign them all in (especially in a multi-lang kitchen like this where you have to do it for both WWE and FRA language start menu folder structures :rolleyes:

You read my mind about the Folder Icons :D

I have been looking for some but not too fond of the ones I have found so far ... primarily because I want to find icons that will look like they belong with the MSFT icons already provided (I don't want to replace everything in some kind of "theme skin" manner, just want to embrace the native wm6.5 icon look).

The way to do it is pretty simple, you actually disabled one of my provxml files that does some of it in your uber-lite:

EXT\COMMON\StartMenu_Icon\files\mxipinit_startmenu_002.provxml

^^^ Disabling that is why your Home, Clock and Sounds icons under Settings-Personal looked a bit oldschool in your uber-lite rom. My fault really ... I should have put that provxml under OEM but I only just worked out what icons needed fixing at the last minute before I uploaded the kitchen yesterday, so it went in EXT where the old broken one was.

EDIT: OK, that's weird - I just checked and you didn't disable that provxml :confused: ... anyway that file is a good example of how to set them

Basically there need to be reg keys/vals (mapping to PNG images) for each shortcut or folder in HKLM\Security\Shell\StartInfo\Start\

Take a look with CE Reg Editor and it is pretty obvious ... it only gets a bit messy with the icons under "Settings" (which are identified by obscure CPL numbers) and some of the important OS icons have their name spelled out in ASCII char numbers (but the icon image filename usually makes it obvious what the icon is anyway).
[P3600 ROM Development] RedBux:
Hi

Thanking you so much for your time and hard work.

I did downloded 23060 earlier released but still didn't flash yet.

Seemed that U upgraded this release I am dl now and will flash soon.

Regards
[P3600 ROM Development] SuperSport:
I will look the provxml file over. Yes, I think that's another example of where settings have been made all over the place to do the same thing. It's too bad Microsoft did not set ALL icons in a single file and just change that file when things change. Same for Layouts, Settings, etc... Should all be in a central place so you don't have to search all over the ROM to make changes.

Maybe it was not MS, but the result of many different cooks getting ahold of these ROMs? Either way, it would be nice to clean one up and make it the starting point for future versions. You are doing great work, and hopefully I can help. As a matter of fact, it might be helpful if others could pitch in? Maybe you could delegate jobs for a number of people to accomplish so each person had less to do? Together, we could come up with a nice clean base?

Then again, sometimes it's easier to do it alone, keep on track, and keep everything as your mind sees it. Too many hands in the Pot and all.

Let me know where I'll be the most help. I may be ADHD, because I tend to bounce all over the place, but I can focus on a task when told what to do. :D
[P3600 ROM Development] SuperSport:
The icons still need work, but this is the general idea I was thinking for Subfolders, so you knew they were not programs. Any ideas? I thought maybe 5-6 total folder categories?

PS: Windows Media is supposed to say Multimedia. I picked the wrong icon to change.

I just noticed I'm still using your older Kitchen. Downloading newer one now.

Please find Sample Icons Attached. I will create any you feel you would like.
[P3600 ROM Development] the.decoy:
Dude, that looks great! :D

I was actually going to say (in response to your other post about how to help) that it would be good if you could sort out the start menu folder icons and maybe think up some ideas for what apps should go where.

Everytime I have tried to get around to this aspect of the start menu I get soooo sidetracked with some new build bug or other kitchen issue .... then never get back around to it :o

It's friday afternoon here so I am about to go "mostly offline" ;) for the weekend but if I get a spare moment on sunday I will start putting together a dedicated EXT package (maybe even put it under OEM) for all of our Start Menu layout/icon enhancements ... a single place where we can round up all the existing miscellaneous reg's dat's & provxml's and keep track of them properly.

One of my biggest concerns with all this was trying to make sure that it would all work properly in a modular nature so we don't keep having the "jenga syndrome" with our packages (i.e. taking out one app inadvertently messes up the setup of others). But I am pretty sure now that if we come up with a unifying Start Menu layout (with folder icons) and implement that at the OEM package level, we then just need to edit all our EXT app.dat's to create their icons in the relevant folders.

So yeah, if you get finished with making folder icons, I would appreciate your input on deciding what apps should where in the new folder structure (lol, especially all the obscure apps that we may not use or even cook into our "lite" roms).

No hurry though. We probably have until the next releasable build is ready before we need it to go public :)

Thanks again Super!

Cheers,

-Decoy
[P3600 ROM Development] sprint:
P3600

the.decoy can you make the ROM for P3600?
[P3600 ROM Development] SuperSport:
Hey Sprint. the.decoy mentioned maybe being gone for the weekend. I will say that there will definately be a P3600/Trinity version soon. I am using the Trinity, and it sounds like the.decoy and I will be working on making an organized version using what he's already done. I'm VERY impressed with his organizational skills, so it should be a nice ROM. FYI, this is HIS ROM, and HIS hard work, I'm just going to help weed out some bugs, etc...

Like I said, I use the Trinity, so I will guarantee a Trinity version. Even if I convert the Kitchen after the P3600i version is complete. For the time being, I've been using his Kitchen to cook the ROM, and then I Hex Edit it back to Trinity and it is working fine so far. I would say to use this as a TEMPORARY solution if you really want to use his ROMs.

Is there a particular one you'd like to use? I'd be willing to do the HEX Edit for anyone not familiar with that process. (BUT, beware, it's possibly not as stable as what the.decoy has created. I have not had a problem, but maybe I've just been lucky.)
[P3600 ROM Development] D@vide:
hi SuperSport, what about memory leak on 6.5? It would be nice to have the possibility to have chome (titanium) included... are you working on slot 0 to be as free as possible?

Tia

D@vide

ps.

can you hex edit a chome ie6 version as lite as possible? Thank you
[P3600 ROM Development] SuperSport:
the.decoy did mention keeping slot 0 as free as possible See Link Here. Memory has been stable on the ones I've tried. I'll look at the newest Kitchen and see what I can cook up from it. Again, remember this is the.decoy's work and I'm just playing with it. I don't want to take away from what he's been doing. ;)

Edit: Ok, two versions avail. One is using the Kitchen as is. The other is a Very Lite Chome Version. And just to clarify, they are both cooked using the P3600i Kitchen, then I Hex Edited the RUU files. So they may not be as stable as they should be, but they might be. When the Kitchen is closer to a complete version, either the.decoy or myself, or both, will convert the kitchen to Trinity version. Seeing his work, I know you will be happy with the final cleaned up version.

Lite Chome Version:

22.06MB Free Ram

54.01MB Free Storage

Very Responsive. Some Icons don't work, due to the menu layout that will be fixed in future. Keep an eye out for cool future changes to menu. Access Task Manager in Top Right Corner as normal. The.Decoy has made the icon invisible so it works with this version of the OS.

Download
[P3600 ROM Development] D@vide:
ok, thank you very much SuperSport.

last night I already managed cooking a chome lite version using the last kitchen the decoy have released for trinity, using as guide to clean the rom the .txt file you have published for him. Very responsive and with a 25M free ram at first boot. Now I'm going to try your. ;)

Thanks

D@vide
[P3600 ROM Development] SuperSport:
23064 sys & xip

Hey the.decoy, just wanted to let you know that when you return, I've got a treat for you. I took your Kitchen, Stripped it WAY down, and upgraded it to 23064. (NO Ext Packages and only Camera and Lang in OEM! :eek:) Everything running on it now comes straight from the SYS, which is pretty all inclusive.

The New Lockscreen works, as does the New Contacts App. Also, the latest IE8 works MUCH faster than the previous one. Still slower than Opra, but gaining headway. No Camera, YET.

I've got it running on my Trinity now, and so far, it's running well. I'm going to play with it tomorrow. I'm babysitting my grandson, so between "stuff", I'll be playing with my phone.

Please see attachments.
[P3600 ROM Development] GWADADA:
hi what is the HARD SPL or software that must be added to P3600 trinity to flash the ROM 23,060 of P3600i, thank you
[P3600 ROM Development] D@vide:
nice!! Can you share the new kitchen?

D@vide
[P3600 ROM Development] der_timo:
Yes, please share your Rom or the kitchen! Is it for the trin without "i" too?
[P3600 ROM Development] SuperSport:
23064

This is the.decoy's P3600i Kitchen modified to 23064. It's SuperLite and not fully functional. If he decides to use it, I'm sure he will make it a really nice ROM. It does seem on the Heavy Side as it uses a LOT of RAM, but runs well. Still NO camera yet.

I've also included Two cooked ROMs from the Kitchen. One for Trinity, and one for P3600i.

Download
[P3600 ROM Development] SuperSport:
WHOA! :eek:

I'll report back after flashing, hopefully with something more intelligent than Whoa.

Edit: Ok, the Kitchen is awesome. I don't know how you think these things through. Organizing it into two seperate and yet Singular Kitchens is pretty smart.

When I flashed, it does the Mortscript pause again (1-4 Mins). Not sure yet what that is about. When I use the P3600i kitchen and Hex Edit, I don't get that. Strange??? There is some fixing to be done, as you mentioned, but it's a GREAT start. The Phonepad does not have any skin, just numbers hanging in air, but I've used a phone long enough to remember how it works. ;) The things I see that need work appear to be easy fixes, and mostly asthetic. Thank you for your work on this. I know you don't want to hear this, but I'm already testing 23420 just to see what all the hype is about. :o
[P3600 ROM Development] the.decoy:
Ahh, cool. That mortscript thing is something I will have to check out (these are the things it is hard for me to test when only have p3600i). The way I have done it you do definitely need to tap the OK on the mortscript popup to make it continue ... but it sounds more like you are getting the original bug where it just stays locked on the customisation screen with mort stuck in the background.

Phonepad is like that because I didn't include any kind of canvas package and I think there must be a leftover reg key or two in the OEM that is there to enable the old canvas (canvas enabled + no canvas = white dialler). Anyway I would never release a proper kitchen with no canvas package ... this was just a quick mash-up to get the structure together.

Clearly I need to tidy up some more of the differences between the 2 OEM folders (I actually started building it with an \OEM\SHARED\ folder to avoid any duplication but the kitchen would not support it under OEM - it just thought I had added a 3rd device called "SHARED" lol :rolleyes: )

23420 port? Excellent! I am busy porting 23071 to hopefully do our first release version of this kitchen. Good way to split the workload between the COM3 and COM4 branches :cool:

Will post back later today ...

EDIT: Got the SYS ported with a really good recmod setup (slot0 empty, slot1 completely full) ... running a skeleton test rom right now (23071 looks really nice) ... sorry but still kinda wiped out with flu, so not going to get the EXT and OEM finished tonight. :( Will hopefully have something ready and uploaded for the start of the weekend.
[P3600 ROM Development] chanvi93:
PhonePad COM3 problem solved

Hi to all and specialy The.decoy + Supersport

I have solved the phoepad too large problem in COM3 build like the latest 23071 from DaG

DL attach folder , replace cprog.exe in SYS-SHARED-COMMON-PhoeRedist, then replace 2 mui files in SYS-SHARED-040...

It work for me with Topaz so i think it will work also with Trinity or P3600i .

Try with my 3 Phonepad completed ( with smartdialing) .

Also i suggest you try to use Resource_Proxy package from Mega if it exist to reduce RAM use.
[P3600 ROM Development] SuperSport:
Great news! Thanks. 23420 is So large that I have a hard time adding any software. Not sure what the differences are between 23063 and 23420, but something. :confused: It looks like the Trinity might be stuck going the route of 23063, 71, etc...

I just cooked a ROM with these files added, and also the Mega Package mentioned. The phone pad is still without a skin, but it is sized correct. The way I get around the phone issues with most of my cooking is to include the Pandora Dialpad Ext Package. It just makes everything ok when complete, and I like the way it looks. I believe it's the one in your Signature Chanvi. If anybody wants it, let me know.

Thank you for your input, as it is always valuable. :D
[P3600 ROM Development] chanvi93:
If phone skin is desabled it mind somewhere in your kitchen the registry has changed this key

HKLM-Security-Phone and check phone skin is enabled or not , the value must be at 1
[P3600 ROM Development] the.decoy:
Oh cool, thanks Chanvi. Will definitely be keen to check out that Resource_Proxy (actually want to go through and try out lots of those Mega packages but just keeping up with the COM3 builds and kitchen modifications :rolleyes:).

I take it this is the cprog.exe from a older build then? No compatibility side-effects from replacing the 23071 cprog?

BTW, sorry I haven't yet sent you that detailed list of module recmod's for the Slot0/1 setup I am using ... didn't want to send it until I was more sure about some of the modules I was choosing. Anyway, the recipe I have used for the 23071 recmod's is looking pretty good so I will just clean it up into a spreadsheet and PM it to you when it is ready.

Yeah I tread carefully regarding COM4 as it is the "bleeding edge" dev branch and clearly they are developing with much younger (better resourced) devices in mind ... and lately most of the time the good changes end up in COM3 within a few weeks anyway.

Yeah, I actually found where those leftover canvas reg keys were ... there are a bunch of HKLM-Security-Phone-Skin keys in the RGU file in OEMAPPS. I will remove them from the RGU (probably transplant them into the app.reg for OEM dialer package) in the release kitchen.

To have working (native wm6.5 2G) dialer you can either edit that RGU, or install AdvancedConfig and disable Phone Skin/Canvas (as Chanvi suggested).

Installing Pandora package effectively replaces a broken canvas with a working one.

Anyway, hang in there and I will hopefully have the new kitchen ready in next 24hrs and you can build off it instead.
[P3600 ROM Development] mac_es:
In your package there are also some muis, quite critical to replace... they are needed? Or replacing cprog will be sufficient?

Also from what version is this cprog?

About, resource proxy how it will reduce the ram? AFAIK it installs a service which preload images to a shared memory so it goes "faster", so whith so limited memory amount in trinitys I don't see any beneficits using the service, though you will need to install it as it is a depencency for other packages
[P3600 ROM Development] SuperSport:
I don't know if you were going to try to incorporate the new Icons into this build or not, but here are some updated ones. A little larger images, and some different ones too.