WM 6.5 Kitchen QVGA and VGA Developer Edition

[joojoobee666]

Originally Posted by lennie

I'm searching for this but can't find it...

It's part of his kitchen now and is not a separate utility.

http://forum.xda-developers.com/showthread.php?t=469420

[gtrab]

Originally Posted by Da_G

@Wizzard: 6.5 is already final (21234) and we've gone through.. 6.5.0.1, 6.5.0.20, 6.5.0.40 we're working on 6.5.0.50 right now, which is now final with 21280 At the very least we'll make it to 6.5.1 before WM7, but I expect it to go beyond that too

Let's see if I can recall the build naming convention...

212xx = AKU1, all builds leading up to and including WM 6.5
213xx = MOT motorola
214xx = forget
215xx = SAM samsung
216xx = HTC htc
217xx = COM1, continuing dev of 6.5.0.1 - 6.5.0.40
218xx = COM2, continuing dev of 6.5.0.50
219xx = MD, feature branch (unstable features are added here, backported to 218xx (this tree is based on COM1, so older base os code, but the UX code is newer [user experience])
22xxx = SEMC sony ericsson

almost all of the oem branches are based off 21234 (iirc SAM was based off an older build than that) - the oem's requested their modifications, and msft did them, incremented build number - some of these trees have stopped receiving modifications already.

For most of you, for the moment, 218xx is the branch to follow (but they might change the number now that COM2 is done as of 21820)

Most of the current focus is on UX as the backend code is mostly at the goal, so we should be seeing some nice changes to the theming api's etc. that will allow us much more modification of the UI (iirc the end goal is complete skinnability and finger friendliness - nothing left over from the old 6.1 interface that used a stylus, essentially)

They might be bandying about the idea of licensing resco keyboard to replace the stock non-finger-friendly keyboard.

Also, an interesting tidbit, any device that has a dpad and IE6 is *required* to have support in the display driver for a mouse pointer, and support in the dpad driver for a mouse pointer, to allow for things like javascript mouseovers that pull drop-down menus

Thanks for clarifying

First, great to learn SEMC will be OEM updated then
Second, great to know Sony will natively drop out a WM6.5 version !!!

Kovsky fans rejoice

[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.

[joojoobee666]

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.

I remember asking this before in this thread a month or so ago, but no one ever replied. I was wondering if any GSM owners with the 6.5 native kernel were seeing these massive memory leaks. Anyone?

[dsi76]

Originally Posted by joojoobee666

I remember asking this before in this thread a month or so ago, but no one ever replied. I was wondering if any GSM owners with the 6.5 native kernel were seeing these massive memory leaks. Anyone?

I'll reply to your question tomorrow after I flash 21815 w/ 6.5 kernel onto my Fuze tonight.

Been using a Diamond the last few days with 6.1 kernel .. and my battery life actually has been decent, most likely because I don't use the memory-hogging Phone Canvas in my 6.5 builds, as I did in 6.1.

[joojoobee666]

Originally Posted by dsi76

I'll reply to your question tomorrow after I flash 21815 w/ 6.5 kernel onto my Fuze tonight.

Been using a Diamond the last few days with 6.1 kernel .. and my battery life actually has been decent, most likely because I don't use the memory-hogging Phone Canvas in my 6.5 builds, as I did in 6.1.

The phone canvas thing has irked me as well so I haven't used a phone canvas since my first couple 6.5 when I discovered it was the canvas killing the RAM. 10MB as opposed to 1MB, are you kidding me?

Anyhow, I look forward to hearing what the results are for you with the native kernel. I just can't believe this is how WinMO 6.5 is going to be for everyone...

[swampy395]

Build 21900.5.0.2

For any body that want's to try It Here's 21900 I'v built a rom with this and it's fast and stable I used 21202 DPI and 0409's, It built first time. and every thing works the XIP.BIN is with SYS
http://www.4shared.com/file/11392381..._QVGA_DPI.html
http://www.4shared.com/file/11392430...ocal_0804.html
http://www.4shared.com/file/11392877...IP_Common.html
best
regards
swampy395

[ai6908]

Originally Posted by joojoobee666

I remember asking this before in this thread a month or so ago, but no one ever replied. I was wondering if any GSM owners with the 6.5 native kernel were seeing these massive memory leaks. Anyone?

I dont think I have any massive memory leaks! Although, I flash and SR about 10 times a day, so not really sure if I can be used as a baseline.

[Da_G]

I posted 21820 over at xda from my cell lol

btw, gwes and shell32 are both core components of the ui, so they will need to be optimized as more extensibility is added, i think we'll see improvements here

[joojoobee666]

Originally Posted by Da_G

I posted 21820 over at xda from my cell lol

btw, gwes and shell32 are both core components of the ui, so they will need to be optimized as more extensibility is added, i think we'll see improvements here

Thanks for the goods, downloading now. I surely do hope to see improvements soon with the memory leaks. Are you saying the memory leaks are happeneing to you, too? If so, I fail to understand how they could have rtm'd with these conditions. (unless of course it's because of the crappy 6.1 kernel I am forced to use...)