For argument sake...

[1jaxstate1]

It was a half baked attempt. A stop gap from WM6.5 to WP7. I'm pretty sure it's part of the reason Verizon hasn't been too quick to adopt WP7. The got crap from MS last time, they got smart and played the waiting game.

 

[1jaxstate1]

Well, they haven't built up any type of good track record on phone front. But hopefully they'll do better in the future.

MS said that the next update will be available across all phones , WP7.5 to WP8 update is an exception.

 

[power5]

It was a half baked attempt. A stop gap from WM6.5 to WP7. I'm pretty sure it's part of the reason Verizon hasn't been too quick to adopt WP7. The got crap from MS last time, they got smart and played the waiting game.

Wouldn't call a billion dollar development half baked, but it was a failure for sure.

 

[1jaxstate1]

Geez, whoever was leading that team should be an ex-employee. That's a lot of dough.

Wouldn't call a billion dollar development half baked, but it was a failure for sure.

 

[fatclue_98]

**cough** KIN **cough**KIN **cough**

That was really uncalled for. Mods, take this person out back and flog him!!

 

[1jaxstate1]

I'm actually trying to win a ebay bid on a KIN now. I actually like the confused interface. A MP3 player, with wifi, twitter, FB, camera, video recorder. Not bad. But I'm not paying over 25 bucks for it LOL.

That was really uncalled for. Mods, take this person out back and flog him!!

 

[X0LARIUM]

So, as predicted, its a 50-50 chance for these new devices to see light of day when it comes to WP9.

I just hope they don't abandon it...My only worry is that they might use the quad core argument to get away the next time as this time it was the kernel. People have been generous and given MS benefit of doubt. I just hope MS isn't pushing their luck this time...

 

[twincamfxd]

I have had android phones that have received OS updates that really shouldn't have. As bad as I wanted that update, as soon as it was in the phone, it was blatantly obvious the device could not support it. I had to deal with lag and force closing, as well as poor battery life. That is why I get a chuckle when on the android forums and g+ I read posts about people wanting 4.1 on their DROID x when it barely supported 3.5.

I guess my point is that maybe the new OS requires a dual core, or maybe a certain amount of ram, who knows? The only thing I can say is wait and see what is in store for your phones, maybe it will be better than it seems. Personally, I think if they are holding it back there has to be a reason.

Sent from my Galaxy Nexus using Tapatalk 2

 

[Winterfang]

I don't get mad at things I expect .

 

[X0LARIUM]

I have had android phones that have received OS updates that really shouldn't have. As bad as I wanted that update, as soon as it was in the phone, it was blatantly obvious the device could not support it. I had to deal with lag and force closing, as well as poor battery life. That is why I get a chuckle when on the android forums and g+ I read posts about people wanting 4.1 on their DROID x when it barely supported 3.5.

I guess my point is that maybe the new OS requires a dual core, or maybe a certain amount of ram, who knows? The only thing I can say is wait and see what is in store for your phones, maybe it will be better than it seems. Personally, I think if they are holding it back there has to be a reason.

Sent from my Galaxy Nexus using Tapatalk 2

By that logic...none of the OS versions deserve any updates.. I'm on RaZr.. GB lagged, and so does ICS...and I'm pretty damn sure so will JB..

Sent from my RaZr HD.

 

[1jaxstate1]

Strange. I had a GS2 and GB didn't lag, the ICS update didn't lag. It my reboot from time to time, but lag it did not. It was quite fast.

 

[X0LARIUM]

Strange. I had a GS2 and GB didn't lag, the ICS update didn't lag. It my reboot from time to time, but lag it did not. It was quite fast.

Weird. This being a dual core, give it 3 tasks and coughs like an old man on death bed...

Sent from my RaZr HD.

 

[twincamfxd]

I'm not saying no updates for older phones, just that when they don't, there's usually a reason. Not all phones are going to react the same. When my razr got the update from gb to ics, it was like somebody underclocked it. It just got laggy and didn't want to run smoothly. I flashed a rom to fix it, but most wouldn't do that. There's a pretty good chance the new os needs something hardware wise that these phones cannot offer.

Sent from my Nexus 7 using Tapatalk 2

 

[power5]

Geez, whoever was leading that team should be an ex-employee. That's a lot of dough.

very true, but I am sure MS learned something from the project. I doubt it was a billion dollars worth of learning, but something.



As for laggyness:

I thought android was laggy and everyone who used it accepted that fact. Maybe I am not understanding people's definition of laggy. I see laggy as me typing and KB freezes and after a few moments all the letters quickly catch up. Not click an app, and it takes a little longer to open than it did before the "laggy" update.

 

[fatclue_98]

very true, but I am sure MS learned something from the project. I doubt it was a billion dollars worth of learning, but something.



As for laggyness:

I thought android was laggy and everyone who used it accepted that fact. Maybe I am not understanding people's definition of laggy. I see laggy as me typing and KB freezes and after a few moments all the letters quickly catch up. Not click an app, and it takes a little longer to open than it did before the "laggy" update.

MS learned not to push an unfinished product to market. A lesson that should have been learned by simply watching Palm rush webOS to market and having to deal with all kinds of problems. Companies, in all industries, need to understand that consumers are no longer their developmental engineers. "Try it out for a 30 days and let me know how she rides" is no longer an acceptable policy. Alas, until these old geezers at the helm retire or are put to pasture, I don't see a shift coming.

 

[WasteSomeTime]

Why can't they just give a model or OS that is being worked on to the engineers and programmers that are working on it? They could be their own test subjects. Make them use it as if it was their every day phone. Then when they run into a problem, they could fix it the next day they come to work.

Sent from my SGH-i677 using Board Express

 

[fatclue_98]

Why can't they just give a model or OS that is being worked on to the engineers and programmers that are working on it? They could be their own test subjects. Make them use it as if it was their every day phone. Then when they run into a problem, they could fix it the next day they come to work.

Sent from my SGH-i677 using Board Express

That's fine with one or two representative models, but when production lines crank out thousands or even millions, you're sure to get more issues. Works the same with cars. They have a couple of test mules out there racking up miles but when the consumers get the actual production models.... you know how that works out.

 

[cckgz4]

No that's not what I'm asking. I'm asking, IF...the next big update, Win9, doesn't come in 18 months but a mere placeholder, 8.5, would we really have a reason to get pissed? I know what MS did here was, in a way, future-proof themselves..but, they shouldn't leave a bad taste in my mouth with something like this..

The way (excuse) I see it:
"The next BIG update is Windows 9. All the existing devices WONT see it though. Why? Cause its quad-core optimized whereas older services are dual-core, hence won't run it..."

Cha-ching!



Sent from my RaZr HD.

But they said that the kernels in the current software will be multi core supported, so I assume that means that even with dual core devices coming, they'll still get the support

 

[cckgz4]

Oh and my Asus tablet received JB not too long ago and I HATE it

 

[HeyCori]

If Windows 8 is so fundamentally flawed that Microsoft has to replace the kernel in two years then it's probably for the better.