View Single Post
  #2364 (permalink)  
Old 03-30-2009, 07:13 PM
fiyah's Avatar
fiyah
Regular 'Geeker
Offline
Location: San Antonio TX
 
Join Date: Jan 2008
Posts: 261
Reputation: 806
fiyah knows their stufffiyah knows their stufffiyah knows their stufffiyah knows their stufffiyah knows their stufffiyah knows their stufffiyah knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: (March 29, 2009) MERDIN'S WMPro 4.1*Manila 2* CE OS 5.2.21042(Build 21042 MerdinH

Quote:
Originally Posted by Merdinh View Post
Yea the clock problem is a know issue with a fix, that works for some phones and others it wont, and about the alarm clock, i use it every morning to wake me up, not sure i might have fixed it on accident editing my manila, but DHarvery stated that they found a fix that can be included in the next manila they release hopefully soon, becuase it will not work with a cab install.


Also for the text messaging if you dont have sprint, then try installing one of the other carrier cabs and see if that fixes your messaging issue.

Yup. According to DHarvey the clock problem is inherent within TF3D2 itself. The recommended fix is to go to "clocks and alarms" in the settings menu (not through the TF3D home screen!) and change your time to the correct settings. Once the time is set there if your TF3D time is still set to the wrong time then go ahead and fix TF3Ds time from the home screen. Once that is done go back in and set the clock settings back to the right timezone and time. Basically what you are trying to do is get the OS time to match with the TF3D time and then once you have it right NEVER got into the homescreen clock again because it will revert back to the wrong time because of the reset bug. The work around is not really a work around ... just a means of getting your time back to normal. The clock and alarms functionality from TF3D just does not work.

As for the users who have not had this issue... I think that might be because they haven't set any alarms as yet. Once they actually fool around with their alarms the issue will rear its ugly head would be my theory.

The good news is there should be a fix in the next release so just hang on till then.
Reply With Quote
This post has been thanked 2 times.