Next WM release any time soon?

[chevyforlife]

Originally Posted by electronicrice

While I understand that they do this for free, what I don't understand is the fact that we have so much time in between builds, given the fact that for a long while we were getting steady updates and bug-fixed builds for our phones. I have used both no2chem's ROMs, PPCKitchen and DCD. I have gravitated between all of them and found something I liked in each iteration.

What my problem is is that while DCD continues to focus on the community and produce builds of WM to help make our phone better, faster and bug-free, while giving us the bleeding edge, no2chem, for months, has been focusing more on his own applications both for perceived functionality and as replacements of core windows applications, which are being implemented in future PPCKitchen versions, without the options of removal. This focus is a huge shift from what the kitchen idea was and has taken a considerable amount of time away from producing/porting newer versions of the WM builds.

I'm not bitter; as I said I'm disappointed. One guy at xda has been giving regular updates with newer builds of a program that a team of developers here have taken months to produce, and are still behind. And mind you, they have received A LOT of donations for their work, so while they're not being a paid a salary for it, they're being compensated quite well. If you don't believe that, take a look at PPCKitchen.org and tally the names of users who have donated money, more or less around the $5 range. And that's not even counting the donations just to no2chem himself. If that's not enough to keep interest in providing the community with new rom development at regular intervals then that's disappointing in itself.

With that being said, I find your rebuttal unfounded.

my standing exactly.

[electronicrice]

Originally Posted by jakdillard

Ok I have questions for all of you who wants a new build ...... Honestly what is the benefit .... what is it that you notice from the last build of WM6.1 ...... Why are you concerned with a build number ...... When are you gonna put the hours in to port a QVGA SYS to a VGA device ... and make it bug free ... if you are ready to flash for a build number why have you not searched the forums .. found a build .. and gave it to the people that be ....

Are you serious with that? Okay....

As a "Senior Member" I'm surprised. It's not the mere fact that each release has a new build number, it's the fact that with each incrementation of that build number usually comes better functionality/features, as well as possible bugs, being that most of our ports are from other devices.

What is it that I notice in the latest 20273 build? Speedier applications, more RAM, better core windows mobile functionality. You know what else? That same build came from one developer, whereas the build 20270 came from a whole team and it was riddled with bugs that were barely fixed even after release.

So I'm not concerned with just a build number. That and the improved functionality go hand in hand, in most cases. I've already delved into how I feel for each development.

And I'm not going into the childish "why don't you do it and see how hard it is" game. I'm not going to port over a ROM because 1)I don't know how and 2) there were people here dedicated to that task and were being rewarded for it.

And stop with the over-use of ellipses. It discredits your argument.

[chevyforlife]

cant we all just get along?

[electronicrice]

Originally Posted by chevyforlife

cant we all just get along?

Yes. =)

[MrObvious]

We can eat chicken.

[YaTwice]

I have to agree with electronicrice....

If you'd never flashed a PPC before, could you do it with the current kitchen?

I think the issue everyone is overlooking with the PPCKitchen team can be summed up in this quote from the website:

"PPCKitchen.org is dedicated to putting out free easy-to-use solutions for end users who wish to update or customize the software on their Windows Mobile phones."

As I have witnessed the evolution of the PPCKitchen project, I've noticed that the only significant leap in the direction of the stated purpose of the team was the development of first kitchen. Since then, they have fallen into the same quagmire that we all ***** about M$ being in and each "update" to buildOS just continues along that path. For me, the current BuildOS is completely unusable. The entire application is counter-intuitive, and the "automatic" update is anything but automatic. Since the new buildOS came out(after Helmi's original kitchen for the Apache), I've went back to the old-style of ROM cooking with the individual tools, I pull what I want out of the different ROMs and the kitchen RARs and cook it myself.

Too much time is being spent on bells and whistles and not enough time on core functionality.

[jakdillard]

Originally Posted by electronicrice

Are you serious with that? Okay....

As a "Senior Member" I'm surprised. It's not the mere fact that each release has a new build number, it's the fact that with each incrementation of that build number usually comes better functionality/features, as well as possible bugs, being that most of our ports are from other devices.

What is it that I notice in the latest 20273 build? Speedier applications, more RAM, better core windows mobile functionality. You know what else? That same build came from one developer, whereas the build 20270 came from a whole team and it was riddled with bugs that were barely fixed even after release.

So I'm not concerned with just a build number. That and the improved functionality go hand in hand, in most cases. I've already delved into how I feel for each development.

And I'm not going into the childish "why don't you do it and see how hard it is" game. I'm not going to port over a ROM because 1)I don't know how and 2) there were people here dedicated to that task and were being rewarded for it.

And stop with the over-use of ellipses. It discredits your argument.

the point that I'm making is there were a lot of builds coming out because most of them were beta , now with the release of the diamond there was builds coming out in different languages , honestly as far as better memory management \ core speeds , I have not noticed anything different between the official 19208 build verses the 20273 build ...... I at one point was in the rat race to port builds to my roms but after actually using the ported build for more than a week or two I noticed I was having issues that I did not get with the 19208 build ... what I'm getting at is certain builds may be for certain phones as an example 19208 has been the build for all of the titan and vogue carriers such as bell telus and sprint on the treo800 the build number is 19216 the last known kaiser build is 19214 I have used all of these builds so the question still stands do you port a new build or work on the build that was design for your phone , I was doing this .. I would port only the modules I needed to update but then there were problems with certain apps not working right LIKE WMDC AND ACTIVESYNC so I went back to using all of 19208 so my builds will be based off of that unless something ground breaking comes out for the titan

[conflipper]

Originally Posted by electronicrice

Are you serious with that? Okay....

As a "Senior Member" I'm surprised. It's not the mere fact that each release has a new build number, it's the fact that with each incrementation of that build number usually comes better functionality/features, as well as possible bugs, being that most of our ports are from other devices.

What is it that I notice in the latest 20273 build? Speedier applications, more RAM, better core windows mobile functionality. You know what else? That same build came from one developer, whereas the build 20270 came from a whole team and it was riddled with bugs that were barely fixed even after release.

So I'm not concerned with just a build number. That and the improved functionality go hand in hand, in most cases. I've already delved into how I feel for each development.

And I'm not going into the childish "why don't you do it and see how hard it is" game. I'm not going to port over a ROM because 1)I don't know how and 2) there were people here dedicated to that task and were being rewarded for it.

And stop with the over-use of ellipses. It discredits your argument.

Here is a question for you. What is so new in the 20273 build? What is different? sure it might seem faster, but it could also just be a plecbo affect. I mean unless you have an actual changelog from microsoft detailing everything that they change in every single build number. It might seem faster, and better power managment, but how do you know that is not just a plebo? you really dont, so aside from 20273 being bigger number then 19208, what is going to be different?

Get a changelog and then I will believe until then 19208 is just perfect.

[kashabrown]

Originally Posted by YaTwice

I have to agree with electronicrice....

If you'd never flashed a PPC before, could you do it with the current kitchen?

I think the issue everyone is overlooking with the PPCKitchen team can be summed up in this quote from the website:

"PPCKitchen.org is dedicated to putting out free easy-to-use solutions for end users who wish to update or customize the software on their Windows Mobile phones."

As I have witnessed the evolution of the PPCKitchen project, I've noticed that the only significant leap in the direction of the stated purpose of the team was the development of first kitchen. Since then, they have fallen into the same quagmire that we all ***** about M$ being in and each "update" to buildOS just continues along that path. For me, the current BuildOS is completely unusable. The entire application is counter-intuitive, and the "automatic" update is anything but automatic. Since the new buildOS came out(after Helmi's original kitchen for the Apache), I've went back to the old-style of ROM cooking with the individual tools, I pull what I want out of the different ROMs and the kitchen RARs and cook it myself.

Too much time is being spent on bells and whistles and not enough time on core functionality.

I started out a bit later in the game but agree with the above. I have tried several times to "build a rom" from the new Kitchen/Build OS and have found it incredibly confusing and when I finally was able to put something together, it just didn't function right on my phone while before all of these changes, I had quite a few excellent "Rom Builds" from the BuildOS.

I love to experiment and try new things on my phone - but with all of these options and attempting to wade through it all, it has become more work and effort than it's worth. I am currently utilizing DCD's latest effort with a few of my favorite OEM's thrown in with fantastic results. The software is stable, fast and allows for more free RAM than I have seen so far. The kitchen offered by DCD is simple, intuitive and takes much less time to deal with than the latest version of Build OS.

That being said, I really appreciate the work that goes into Build OS, but it's way beyond my understanding, and quite honestly, I do not have the time to "learn" over and over again how to use it properly.

[ajm144k]

Originally Posted by conflipper

Here is a question for you. What is so new in the 20273 build? What is different? sure it might seem faster, but it could also just be a plecbo affect. I mean unless you have an actual changelog from microsoft detailing everything that they change in every single build number. It might seem faster, and better power managment, but how do you know that is not just a plebo? you really dont, so aside from 20273 being bigger number then 19208, what is going to be different?

Get a changelog and then I will believe until then 19208 is just perfect.

that is exactly where i stand too.

my opinion:
if you dont believe that an official build can be better (f@ck the smaller numbers the build comes with) , try out JDs rom which is based on 19208 with modules from other builds that he knows wont botch anything up.

once you try that rom, youll know the difference between real speed gains and placebo speed gains you think youre getting from going from 20270 to 20273 or whatever other moves youre making.

...not even getting into battery management, ram management, or stability. find out for yourself