WM 6.5 Kitchen QVGA and VGA Developer Edition

[mettercomputers]

Originally Posted by joojoobee666

Ok, finished with manual xip port an cooked a ROM, Tested. It is still 21905. So even the MSIXIPKernel files that are in Da_G's kitchen are wrong

Yo Da_G, can you confirm?

I guess it stays like this for the evening...I gotta run for a bit.

i know i ask for a lot but can someone make nuekernal xip.bin for us titan folks
thanks

[indagroove]

I've got the xip.bin but can't post till I get home in a couple hours.

[Tplane37]

Originally Posted by krazy_about_technology

@Da_G:

This is a little put down kind of thing for users like me with retro devices having 64 MB RAM If the base os code is done that means they are not going to work on memory leaks that GWES.exe, Shell32.exe, device.exe and filesys.exe are having. GWES is the top memory eater. In 21815, it increased a bit, people with phones having less ram should have notices it. Memory usage wise, 217xx series was better. Maybe we, old device users, should go back to 6.1 now. But the increased battery life always stops me. I get double the speed and responsiveness in 6.1 but in 6.5, battery life is more than 1.5 times.

Back to 6.1 due to only having 64 MB RAM????? Never! I may never run a 6.1 ROM on my Titan again, unless I am testing for something to bring over to 6.5. And even then, I can test most (if not all) 6.1 apps by simply turning off "Windows Default" in the Today settings......I am rather impressed with how well the Titan is handling 6.5, and they said it would never run it...some one just had to try it, and guess what...64 MB may not be a lot, but it's enough!


Speaking of the Titan....anyone have that 21820/21905 XIP thrown together yet for the Titan? I have an angry mob knocking at my virtual door screaming: "We want more!" So I guess I should throw something together to see how it works and try to answer the calling.

[mettercomputers]

Originally Posted by Tplane37

Back to 6.1 due to only having 64 MB RAM????? Never! I may never run a 6.1 ROM on my Titan again, unless I am testing for something to bring over to 6.5. And even then, I can test most (if not all) 6.1 apps by simply turning off "Windows Default" in the Today settings......I am rather impressed with how well the Titan is handling 6.5, and they said it would never run it...some one just had to try it, and guess what...64 MB may not be a lot, but it's enough!

I agree 6.1 is so boring and slow no matter which build I use I wish I could learn to port nuekernal xip.bins

[joojoobee666]

Originally Posted by mettercomputers

i know i ask for a lot but can someone make nuekernal xip.bin for us titan folks
thanks

PPCKitchen files. WinCENLS_WWE is in tha 0409. IPSECVPN and Enterprise are options under system. Browsingie and AdobeFlash are reccmodded. The 96 DPI are put together from the 21815 DPI. So hopefully all is well there. Let me know and I will update this post. Again, no promises on anything here. This is the development thread after all

SYS_21820_Common
http://www.4shared.com/file/11395369...20_Common.html

SYS_21820_192DPI_0409
http://www.4shared.com/file/11395313...2DPI_0409.html

SYS_21820_96DPI_0409
http://www.4shared.com/file/11398320...6DPI_0409.html


CDMA Herman, CDMA Titan XIPs, Kaiser, Vogue (fixed, the first one that was up for the first 30mins had overlaps and I had to manually fix) and CDMA Diamond (Victor) XIPs. All but the Herman are confirmed working.

Thanks for the goods, Da_G (your MISXIPKernel was all good, I just flubbed it)

[da_reeseboy]

So what was the previous xip you posted joojoobee?

[joojoobee666]

Originally Posted by da_reeseboy

So what was the previous xip you posted joojoobee?

start\settings\system\About showed 21905. I also changed the name to 21819 to reflect the ACTUAL version as to not confuse people any more

[Tplane37]

Originally Posted by joojoobee666

start\settings\system\About showed 21905. I also changed the name to 21819 to reflect the ACTUAL version as to not confuse people any more

But the question is....is this a 21905 XIP hexed to 21819, or was it a 21819 hexed to 21905 and you just changed it back?

If the XIP is supposed to be 21905, can you please post up the XIP.bin as the 21905 (un-hexed).....but if it is actually supposed to be a 21819 XIP, can you fill us in a bit....

I get a little confused, and sometimes concerned, when Buld and XIP numbers start getting editted to reflect different numbers.

[joojoobee666]

Originally Posted by Tplane37

But the question is....is this a 21905 XIP hexed to 21819, or was it a 21819 hexed to 21905 and you just changed it back?

If the XIP is supposed to be 21905, can you please post up the XIP.bin as the 21905 (un-hexed).....but if it is actually supposed to be a 21819 XIP, can you fill us in a bit....

I get a little confused, and sometimes concerned, when Buld and XIP numbers start getting editted to reflect different numbers.

The 21905 was what I pulled out of the os.nb.payload after a build in Da_G's kitchen. It was NOT the right XIP. When I ported manually, I missed whatever file holds the version number so the version still showed up as 21905. Finally, I fixed the manual port by making sure ALL the files from the MSIXIPKernel in Da_g's kitchen were in my port properly. So, the 21819 is NOT a hex, but that is what Da_G said is SUPPOSED to go with this build.

[charleskincade]

Help, I just upgraded to the TP and i'm eager to flash but updater isn't allow me to finish updating the oem's. Can someone help me with this, I've tried installing and uninstalling BuildOS many times and I still have no success! I've sent messages to GGURUUSA and Conflipper and I haven't heard a peep from either one; beats the devil outta me why they wouldn't respond so can someone please help me with running the updated oem's so that I can flash my rom. Thanks in advance to whoever can help