Fix/Workaround for 2016 Issue

[a3rdeye]

As of 0750 central time I had a Sprint tech with some common sense and give me a flat out "WE HAVE NO SOLUTION" response. He told me that it's a WinMO issue and Microsoft is developing a patch for it. I asked him about ziggy's cab and regedit and he informed me that it HAS NOT affected the servers in anyway.

My question for the forum is can someone walk me through this so it acts with the Touch Flow messaging feature. I have installed/uninstalled/ reset/ and done a straight regedit through Rescoe explorer and have been unable to have the fix work with the scolling message feature. Suggestions?

as always thanx for ur hard work guys.

[BOO B)]

I have Sprint and the cab worked fine. But it doesn't fix your old texts. I just deleted all the ones I got Jan. 1st upto when I installed the cab. I think a lot of people thinks it will fix old texts also. Just from installing cab and forward.

BOO B)

[psycho_maniac]

i hope microsoft actually has a fix. i mean its not a big issue "really", but how could they miss a mistake like this?

[fusion]

Originally Posted by psycho_maniac

i hope microsoft actually has a fix. i mean its not a big issue "really", but how could they miss a mistake like this?

i 100% agree... and i was just starting to get some respect back for them with win7...

[scarydok]

Hey all, after reading all of the posts, as most of you have pointed out, this does seem to be a WinMo issue, but I'm still confused as to why Android phones are experiencing the issue as well.

I have a Sprint TP2 with stock rom running WinMo 6.1. I'm also confused as to why this seems to be happening on some carriers, but not others. Why are some CDMA customers experiencing it, but others are not? There are several reports of WinMo on VZW that are not experiencing this issue, but several are.

I've got the workaround in place just so my messages are threaded properly, but am anxiously awaiting Uncle Bill's fix...

[scarydok]

P.S.

Ziggy, sorry for not thanking you before, but I finally stomped that button...lol

Seriously, thank you.

[fceeviper]

Sorry but I don't think its a big deal (to me(, I think its kinda funny to have a date of 2016 on my texts, all my friends and family thought it was funny/cool.

Microsoft/Sprint will have an official fix for it eventually...

So what's the hurry in getting a temp fix?

[scarydok]

Originally Posted by fceeviper

Sorry but I don't think its a big deal (to me(, I think its kinda funny to have a date of 2016 on my texts, all my friends and family thought it was funny/cool.

Microsoft/Sprint will have an official fix for it eventually...

So what's the hurry in getting a temp fix?

To me, it's frustrating that I not only spent how many hundreds of dollars on the smartphone, but I also give Sprint over $1300/yr to pay for service. And when something is flawed with the product that I'm continuously paying money for, that infuriates me.

Would you not be upset if you had a car that you were paying on, and because of a manufacturer's defect, the radio station would randomly change on you? It's not anything that's causing the car to not work, but it's something that is a major annoyance, isn't it? What would you do? Would you not be taking the car up to the dealership and telling them to fix it?

Please don't take these comments as me being rude or disrespectful, they are not meant as such. They are strictly to express my point of view on why I'm upset at Sprint/HTC/Microsoft for dragging their feet on this.

[ziggy471]

Originally Posted by scarydok

Hey all, after reading all of the posts, as most of you have pointed out, this does seem to be a WinMo issue, but I'm still confused as to why Android phones are experiencing the issue as well.

I have a Sprint TP2 with stock rom running WinMo 6.1. I'm also confused as to why this seems to be happening on some carriers, but not others. Why are some CDMA customers experiencing it, but others are not? There are several reports of WinMo on VZW that are not experiencing this issue, but several are.

I've got the workaround in place just so my messages are threaded properly, but am anxiously awaiting Uncle Bill's fix...

My only guess as to why Android is also effected is that they use a similar conversion for the same field.

The reason for VZW not experiencing the problem, as I've stated before, is that VZW sets the same key I post in my original post by default. Some users running cooked ROMs from the great chefs here and other places, may or may not set that key also. I looked into a few of the kitchens I had downloaded, and all set the key in one way or another, some by default, some just for specific operators.

Originally Posted by scarydok

P.S.

Ziggy, sorry for not thanking you before, but I finally stomped that button...lol

Seriously, thank you.

No worries, I forget to hit thanks too, as do many of us around here. We find what we need, and go off to try it, but forget to come back and hit thanks when it worked or helped us get over that stumbling block.



Z

[burn_31]

Originally Posted by dcdave63

You might want to consider creating a cab to reverse this, since uninstalling might not be enough to undo this, so that when someone eventually pushes out a fix, this can be undone.

Is this true???