PPCGeeks Forums HTC Arrive HTC HD2 HTC Thunderbolt HTC Touch Pro 2 HTC Evo 4G HTC Evo 3D Samsung Galaxy S II Motorola Droid X Apple iPhone Blackberry
Go Back   PPCGeeks > Windows Mobile > WM HTC Devices > HTC Touch Pro 2

Notices



Reply
 
LinkBack Thread Tools Display Modes
  #291 (permalink)  
Old 01-02-2010, 08:36 PM
cptok's Avatar
PPCGeeks Regular
Offline
Pocket PC: TP2
Carrier: Verizon
Location: HI
 
Join Date: Dec 2009
Posts: 100
Reputation: 180
cptok is keeping up the good workcptok is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: text messages from the future Y2KX issue

Quote:
Originally Posted by ajac View Post
they make devices that use windows mobile but they dont make windows mobile and no longer actively support windows mobile.. but they dont tinker around with it like HTC and obviously Microsoft..
In fairness - HTC, LG and any other only "make devices that use windows mobile". And the Treo Pro is current using WinMo 6.1 and is one of 3 phones on their home page -- so I'd say they still support it.

Don't get me wrong - I'm not a big Palm supporter by any means! But just being clear that really only Microsoft "makes" windows mobile
Reply With Quote
  #292 (permalink)  
Old 01-02-2010, 08:45 PM
BlackDynamite's Avatar
VIP Member
Offline
Pocket PC: HTC Evo
Carrier: Sprint
 
Join Date: Sep 2006
Posts: 1,839
Reputation: 1190
BlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: text messages from the future Y2KX issue

It's not a problem with the Windows Mobiel operating system. If it was, then it would be happening on T-Mobile and AT&T too.

It's clearly something on the network, as Sprint has been telling customers.

Think about it- using the phone's time for when the message was received works just fine, but using the network's timestamp for when the message was sent doesn't work... It's clearly a network issue.
Reply With Quote
  #293 (permalink)  
Old 01-02-2010, 08:46 PM
neilson's Avatar
Halfway to VIP Status
Offline
Pocket PC: TP
Carrier: Sprint
 
Join Date: Oct 2007
Posts: 549
Reputation: 185
neilson is keeping up the good workneilson is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: text messages from the future Y2KX issue

Quote:
Originally Posted by cptok View Post
In fairness - HTC, LG and any other only "make devices that use windows mobile". And the Treo Pro is current using WinMo 6.1 and is one of 3 phones on their home page -- so I'd say they still support it.

Don't get me wrong - I'm not a big Palm supporter by any means! But just being clear that really only Microsoft "makes" windows mobile
It's past tense. They "made" Windows Mobile phones. Now, Palm is exclusively WebOS.
Reply With Quote
  #294 (permalink)  
Old 01-02-2010, 08:51 PM
[sammich]'s Avatar
Retired Moderator
Offline
Pocket PC: NULL
Carrier: NULL
 
Join Date: Jul 2007
Posts: 6,039
Reputation: 10109
[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: text messages from the future Y2KX issue

If its network related, why are only PocketPC's getting this issue?

I believe it has to do with Windows Mobile interpreting the timestamp the network uses.
Reply With Quote
  #295 (permalink)  
Old 01-02-2010, 08:53 PM
psycho_maniac's Avatar
Super Senior VIP Member
Offline
Pocket PC: Nexus 6p
Carrier: Att StraightTalk
Location: Wi,USA
 
Join Date: May 2009
Posts: 4,027
Reputation: 3882
psycho_maniac is still contributing even after becoming a VIPpsycho_maniac is still contributing even after becoming a VIPpsycho_maniac is still contributing even after becoming a VIPpsycho_maniac is still contributing even after becoming a VIPpsycho_maniac is still contributing even after becoming a VIPpsycho_maniac is still contributing even after becoming a VIPpsycho_maniac is still contributing even after becoming a VIPpsycho_maniac is still contributing even after becoming a VIPpsycho_maniac is still contributing even after becoming a VIPpsycho_maniac is still contributing even after becoming a VIPpsycho_maniac is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via MSN to psycho_maniac Send a message via Skype™ to psycho_maniac
Re: text messages from the future Y2KX issue

Quote:
Originally Posted by strra View Post
he said there are people working on the towers and the computers and it should be fixed within 3 days
i hope so!

Quote:
Originally Posted by mutation9 View Post
I never checked yesterday, but today (1/2/10) all of my 01/01 texts all read 01/01/10.
whats your location?
I am on Verizon using the stock 6.1 ROM... It is tweaked with cabs and Reg hacks, but the ROM itself is unchanged.
just to let you know i think your rom already has this tweak built in

so i called a vzw tech suport rep today and she didnt know what the h i was talking about. she pretty much told me what i expected to say which was reprogram my phone with *228. anybody try this and see if it fixed it? also is it *2289 to reactivate my phone and update my towers? i asked the lady and she said i was talking nonsense. man i had tech support. sometimes i know more about phones then they do!
__________________
Phone: Nexus 6p | Carrier: StraightTalk Att
Kernel: Stock | ROM: Stock Oreo
Reply With Quote
  #296 (permalink)  
Old 01-02-2010, 09:02 PM
raziel's Avatar
PPCGeeks Regular
Offline
Pocket PC: HTC Touch Pro 2
Carrier: Sprint
 
Join Date: Dec 2007
Posts: 85
Reputation: 35
raziel is just getting started
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: text messages from the future Y2KX issue

Quote:
Originally Posted by titaniumgiant View Post
Thanks for posting the fix!
__________________
Macbook Pro 13" Unibody | Core 2 Duo 2.66GHz | 4GB RAM | 500GB HDD | Mac OS X (Snow Leopard)
iPhone 4 32GB | iPad 32GB

visit louie tran spot! a blog for geeks by a geek
Reply With Quote
  #297 (permalink)  
Old 01-02-2010, 09:35 PM
BlackDynamite's Avatar
VIP Member
Offline
Pocket PC: HTC Evo
Carrier: Sprint
 
Join Date: Sep 2006
Posts: 1,839
Reputation: 1190
BlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: text messages from the future Y2KX issue

Quote:
Originally Posted by ⌥ saumaun ☢ View Post
If its network related, why are only PocketPC's getting this issue?

I believe it has to do with Windows Mobile interpreting the timestamp the network uses.
Well we don't really know if anyone else is getting it or not. We're mostly Winmo users on this forum so that is pretty much all we know. We don;t know if RAZR users or whatever have this issue.

Also, it's not affecting WinMo users on T-mobile or AT&T. Even Sprint customners that have their Touch Pro 2 SIM unlocked don't have the issue on a T-Mobile prepaid SIM, on the same phone they have the issue on Sprint if they switch to CDMA.

Maybe none of the other phones we have reports on are even getting the time stamp from the towers. Maybe all of the phones it is confirmed to work on are already set to use the phone's received time stamp instead of the network's sent time stamp...
Reply With Quote
  #298 (permalink)  
Old 01-02-2010, 09:52 PM
[sammich]'s Avatar
Retired Moderator
Offline
Pocket PC: NULL
Carrier: NULL
 
Join Date: Jul 2007
Posts: 6,039
Reputation: 10109
[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level[sammich] can't get a higher reputation level
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: text messages from the future Y2KX issue

Lol. Dad has a Blackberry on AT&T without an issue. Sister has a Samsung Glyde on Verizon without an issue. So from what I've seen, it is only Windows Mobile.
Reply With Quote
  #299 (permalink)  
Old 01-02-2010, 10:17 PM
cptok's Avatar
PPCGeeks Regular
Offline
Pocket PC: TP2
Carrier: Verizon
Location: HI
 
Join Date: Dec 2009
Posts: 100
Reputation: 180
cptok is keeping up the good workcptok is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: text messages from the future Y2KX issue

Here's my take on this. The "issue" seems to be with the SMS gateways putting an incorrect sent time stamp on the SMS (relatively well confirmed at this point). Just like email - where you can decide if you want the "received" column to be when it was sent by sender or received on your server - SMS clients do the same thing.

It's my bet that in fact, with the possible exception of T-Mo, ALL SMS messages actually have the bad time stamp from the gateways for the "sent time", but that it is the SMS clients use of received time rather than sent time making the difference as to whether it is an "affected device".

So it comes down to what the client does. Verizon stock ROM's appear to have default of using received timestamp - so no problem. Same for other devices and OS's. Cooked ROM's like Mighty do not have that reg entry and so were using sent time, and nobody paid much attention to this little difference - until all hell broke loose on 1/1/16!

It is a valid and healthy debate as to whether it is more valuable to use received time or sent time. In the email world, this has been debated a lot - and yet few people actually know which one they are using. In Outlook Express - the default is "Received" - i.e. the time it hit your server inbound. But "Sent" is a non-default option you can put in there and display if you wish by customizing the columns.

Personally - I don't care much which one is displayed. Although, at the moment, I wildly prefer to display "Received" time!! Once the carriers fix whatever gateway bug was malforming the sent date, we will then have that choice to keep the reg entry, or delete it and go back to sent time. In the meantime - I don't see this as a Windows issue as such - but rather a nice feature that windows actually allows configuring the display of either the sent time or the received time.

I might be wrong on this one - but I'll test tonight with a non-windows phone. Turn off the device so that it delays the SMS message a few minutes. Then turn on and see what time displays. I'm betting on Symbian it's the received time..... Possibly so on Android as well. In which case, those devices would not display the problem - although the sent time field may still be just as wrong on those "unaffected" devices.

So I very much agree that the current "reg fix" is not a fix for the real problem. That will be the gateway providers fixing the sent timestamp. But then... once the carriers really do fix this - look at what we've figured out! We now know that we can configure our incoming timestamps on SMS just the way we choose via a simple reg setting.

Last edited by cptok; 01-02-2010 at 10:32 PM.
Reply With Quote
This post has been thanked 1 times.
  #300 (permalink)  
Old 01-02-2010, 10:37 PM
BlackDynamite's Avatar
VIP Member
Offline
Pocket PC: HTC Evo
Carrier: Sprint
 
Join Date: Sep 2006
Posts: 1,839
Reputation: 1190
BlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: text messages from the future Y2KX issue

Quote:
Originally Posted by ⌥ saumaun ☢ View Post
Lol. Dad has a Blackberry on AT&T without an issue. Sister has a Samsung Glyde on Verizon without an issue. So from what I've seen, it is only Windows Mobile.
Windows Mobile phones aren't having the issue on AT&T either. Take your dad's AT&T SIM and pop it into your Touch Pro 2. Set your Touch Pro 2 to GSM mode so it uses the AT&T SIM instead of Sprint service. Bet you don't have the issue anymore...
Reply With Quote
Reply

  PPCGeeks > Windows Mobile > WM HTC Devices > HTC Touch Pro 2

Tags
2016 y2k

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


All times are GMT -4. The time now is 03:04 PM.


Powered by vBulletin® ©2000 - 2019, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.6.0
©2012 - PPCGeeks.com