Bug causing some handsets to party like it's 2016?

Bug causing some handsets to party like it's 2016?
We recently reported that some Windows Mobile phones were showing text messages coming in after the ball dropped in Times Square as having been written in the year 2016 instead of the obviously correct 2010. While some might have thought that they were getting messages from the future, there actually is a mundane explanation according to WMExperts. A bug is affecting mostly LG and HTC devices running Windows Mobile 6.1 and 6.5, that is causing some text messages to show the incorrect year. Other handsets, including non-Windows Mobile models, are also involved to a lesser degree. The site says that it is ROM independent so switching is not an option. All carriers in all areas are affected and LG and HTC are aware of the situation. Clicking on the source link will present you with a link  that offers a fix for the 2016 date problem via the installation of a CAB file. One interesting fact. The binary code for 16 is 010110 (01/01/10-January 1, 2010).

source: WMExperts



1. *HOVA*

Posts: 564; Member since: Dec 11, 2008

Primarily a WINMO problem, whata surprise.

2. Dood

Posts: 269; Member since: Mar 23, 2009

Actually, this was all my doing. I take full time-traveling responsibility. In the future all phones will be razrs with actual razors, too.

3. Illyich

Posts: 167; Member since: Oct 13, 2009

SWEET! Will they still not function as a phone?

4. bryantkd

Posts: 1; Member since: Jan 03, 2010

010110 is binary for 22 not 16. Binary for 16 is 010000

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at https://www.parsintl.com/phonearena or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit https://www.parsintl.com/ for samples and additional information.