Custom ROM Developers- just my 2cents - Page 3

sfaure03 · #21 (**permalink**) 11-13-2007, 06:55 PM

vk, thats exactly what the kitchen is that we keep refering to. A place for you to click on the options you want, and have you're own rom.

Again the issue is on stabilizing in on the base operating system to choose from, before we start piling on the other "options."

The kitchens are eminently configurable, but getting the "starting" configuration for a device where the drivers and implementation are less than satisfactory is taking longer than we would hope.

**shaun0207** · #22 (**permalink**) 11-13-2007, 06:58 PM

Quote:

Originally Posted by sfaure03

vk, thats exactly what the kitchen is that we keep refering to. A place for you to click on the options you want, and have you're own rom.

Again the issue is on stabilizing in on the base operating system to choose from, before we start piling on the other "options."

The kitchens are eminently configurable, but getting the "starting" configuration for a device where the drivers and implementation are less than satisfactory is taking longer than we would hope.

Is it possible to rewrite the current drivers somehow? Or is that almost like recreating WM6?

TC1 · #23 (**permalink**) 11-13-2007, 07:13 PM

Quote:

Originally Posted by shaun0207

My question is... how come this wasnt done before releasing WM6? There are so many problems with WM6 from resource hogging, to memory leak, issues the alarm. Wasnt this fully tested before being released? I had WM5 on my Moto Q and I was upset that they werent giving a WM6 upgrade to my 4moth old Q. So I switched to the Mogul for the full keyboard and WM6. Not to mention the touchscreen. It seems like MS really dropped the ball.

I'm not picking on you Shaun, but your statement could be made about EVERY OS ever released by Microsoft (or others)... "How come they didn't find this bug... or this one?" XP had problems. Vista has problems. Win95 had problems when first released. Etc, etc.

Like I previously said, regression testing is a mind blowing task. Unless you have a totally locked down platform, ie, you control BOTH the hardware and the software (like Apple), it's next to impossible to catch all the bugs. Look at Apple, even though they do control everything they still have some bugs (but a lot less than the other OS platforms).

I'll give you a little insight to modern software development methodology: Even when we know there are bugs, we will still ship/release software based on market demands and the severity of the bugs. It's always a trade-off between cooking the software longer to get it near perfect, and actually releasing a product so you can make money and capture market share. Like I said, you can regression test until you are blue in the face, but then the law of diminishing returns kicks in and you start to lose $$$.

As a consumer, yes, you should be upset that something you paid for is buggy. But unfortunately it's just the nature of the beast.

**shaun0207** · #24 (**permalink**) 11-13-2007, 07:16 PM

Quote:

Originally Posted by TC1

I'm not picking on you Shaun, but your statement could be made about EVERY OS ever released by Microsoft (or others)... "How come they didn't find this bug... or this one?" XP had problems. Vista has problems. Win95 had problems when first released. Etc, etc.

Like I previously said, regression testing is a mind blowing task. Unless you have a totally locked down platform, ie, you control BOTH the hardware and the software (like Apple), it's next to impossible to catch all the bugs. Look at Apple, even though they do control everything they still have some bugs (but a lot less than the other OS platforms).

I'll give you a little insight to modern software development methodology: Even when we know there are bugs, we will still ship/release software based on market demands and the severity of the bugs. It's always a trade-off between cooking the software longer to get it near perfect, and actually releasing a product so you can make money and capture market share. Like I said, you can regression test until you are blue in the face, but then the law of diminishing returns kicks in and you start to lose $$$.

As a consumer, yes, you should be upset that something you paid for is buggy. But unfortunately it's just the nature of the beast.

I dont feel picked on at all. You make a good point.

sfaure03 · #25 (**permalink**) 11-13-2007, 07:20 PM

Quote:

Originally Posted by shaun0207

Is it possible to rewrite the current drivers somehow? Or is that almost like recreating WM6?

Which current drivers? Yes and we are currently waiting for the vendor to provide us that very thing. In the meantime we are attempting to build a set of "compromises" between different drivers and settings that work better.

I assure you we will NEVER get a perfect fit for this, but i'm also confident that over the next weeks or months it will get to where we have a very fine compromise that will please most of the users.

**shaun0207** · #26 (**permalink**) 11-13-2007, 07:23 PM

Quote:

Originally Posted by sfaure03

Which current drivers? Yes and we are currently waiting for the vendor to provide us that very thing. In the meantime we are attempting to build a set of "compromises" between different drivers and settings that work better.

I assure you we will NEVER get a perfect fit for this, but i'm also confident that over the next weeks or months it will get to where we have a very find compromise that will please most of the users.

I think the guys/gals of thise site will figure out most oif the fixes long before Sprint does. I have a little faith in HTC on getting it done. But not much.

DogGuy · #27 (**permalink**) 11-13-2007, 07:39 PM

Quote:

Originally Posted by TC1

I hear exactly what you are saying, and on the surface seems logical and a great idea

But let me play devil's advocate here for a moment: If it was as simple as picking the most stable driver, out of a selection of already available drivers, then why hasn't HTC done that already?......

Again, this is just my opinion and I'll be very happy if I proven wrong, because then we all win.

I still think what you guys are attempting is cool and it will be a great feeling and win for all if you can solve it.

No offense, but you're playing devil's advocate with a statement that was never made TC1. That is not at all what I was implying, because quite honestly its been done. We know the drivers are not solely at fault. The issue is *not* with simply swapping drivers. What I said a lot of us are working on is a hybrid rom, meaning numerous swapped out pieces from a variety of variations on the wm6 OS. Very clearly there is a substantial difference between say, 2.16 and 2.14 and the Vogue. Dropping BT drivers from the Vogue into 2.16 works, to a point, but try the same with 2.14 and you have utter failure. What we're attempting is a compromise of hacks and "fixes" from various working parts, with the intent of figuring out who doesn't feel like being a nice team player with the rest of the OS, and calling in the second string'ers.

I have little doubt that the combined hours of sfaure03, jtrag, myself, and the other major contributors in the last week alone, most likely triples the beta testing that went into the 2.16 release. Simple is the last thing I'd call what we're doing.

If HTC or Sprint are actually legitimately working on a fix, they are either taking approach a) rewrite everything that might be a problem b) figure out where the failures are and the poor interactions, and rewrite or replace only what is necessary or c) a little of both. Personally, I'm trying to do b.

It simply comes down to, can we work with what is available to create something useable until the commercial developers of the device decide to give us a real solution. Lets all keep hoping for a big ol' yes there.

- DogGuy

**pzztgotbagz** · #28 (**permalink**) 11-13-2007, 11:11 PM

im going to leave this thread here but im going to close it i dont want a pissing match to be started