1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Series 1 owners to get no March 11 DST support

Discussion in 'TiVo Coffee House - TiVo Discussion' started by fluke, Feb 12, 2007.

  1. n548gxg

    n548gxg New Member

    912
    0
    Mar 7, 2003
    East Coast
    +1
     
  2. VictorWI

    VictorWI New Member

    11
    0
    Feb 4, 2000
    Greendale,...
    My S1 SA is working fine. Recording my shows, letting me time shift, pause live tv, fast forward through commercial. There is some cosmetic issue with the clock but I can add one.
     
  3. IHDB

    IHDB New Member

    40
    0
    Mar 9, 2007
    I'm inclined to believe Jerry that there wasn't a was to make the switch. Despite the fact that they are both S1's, since the DirecTivo boxes are different, it's not at all unrealistic to expect the software to be different. I would even speculate that the DirecTivo boxes get their time from the sattelite feed (like GPS does), so that the time handling parts would be one of the parts where the code was a little bit different, since you can't get time information from cable TV or an antenna...

    I know that it's silly in this day and age to have trust in some people, but Stephen and Jerry are pretty honest folks, and I'm inclined to beleive that the problem isn't as easy as some of the self-proclaimed "experts" in this thread think that it is.
     
  4. sbourgeo

    sbourgeo Hepcat Daddio

    7,662
    26
    Nov 10, 2000
    New England
    I suppose anything is possible, but I'm not convinced it was impossible from a technical point of view to fix the DST issue on the S1 standalones.

    I found the new DST entries in the MFS database after my DSR6000 was upgraded from from 3.5 to 3.5b and 3.5b introduced offsets for DST start and end dates as well as start and end times. Prior to that, the 3.5 software on my DSR6000 had the same location configuration entries in MFS as my HDR312. As long as the TiVo binaries and scripts were updated to grab the DST info from MFS, one would think that it wouldn't be a big deal to implement this on the S1 standalones too.

    In the end, it doesn't matter much anyway...
     
  5. jberman

    jberman Mostly Harmless

    102
    0
    Oct 1, 2002
    PLEASE NOTE: Since the time I posted these scripts, TiVo has incorporated them into an official update that became available to S1 owners (regardless of current TiVo subscription status) on 3/14/2007. Please visit http://research.tivo.com/prioritydst to sign up for the official patch. Thanks! -jberman

    --

    I'm certainly no expert at this, but I think I might have figured out a workaround for my Series 1 SA (Philips) Tivo....

    I spent most of the afternoon piecing together information on this problem, and eventually discovered that there's an MFS setting called TimeZoneOld that has the following possible values (which I grabbed from /tvlib/tcl/tv/DbEnum.tcl):

    Code:
    namespace eval TimeZone {
    variable Eastern 1   [a.k.a. GMT-5]
    variable Central 2   [a.k.a. GMT-6]
    variable Mountain 3  [a.k.a. GMT-7]
    variable Pacific 4   [a.k.a. GMT-8]
    variable Alaska 5    [a.k.a. GMT-9]
    variable Hawaii 6    [a.k.a. GMT-10]
    variable GMT 7
    variable GMTPlus1 8
    variable GMTPlus2 9
    variable GMTPlus3 10
    variable GMTPlus4 11
    variable GMTPlus5 12
    variable GMTPlus6 13
    variable GMTPlus7 14
    variable GMTPlus8 15
    variable GMTPlus9 16
    variable GMTPlus10 17
    variable GMTPlus11 18
    variable GMTPlus12 19
    variable GMTMinus1 20
    variable GMTMinus2 21
    variable GMTMinus3 22
    variable GMTMinus4 23
    variable GMTMinus11 24
    variable GMTMinus12 25
    }
    I live on the U.S. east coast. Assuming that TivoApp manipulates this setting to control DST changes, I ran a little tcl script (included below) to set TimeZoneOld to 23 (a.k.a. GMT-4), then restarted my Tivo. Now the clock looks correct in the program guide, all my season passes still work, and everything (so far) looks good. My last step was to set up a crontab entry to make sure this script gets run on the second Sunday in March (and also the first Sunday in April and last Sunday in October for good measure, just in case TivoApp does something funky with the timezone then), and another one to set it back to GMT-5 on the first Sunday in November.

    If you want to give it a try, good luck.... I'm posting the scripts and crontab entries here. This requires access to the bash prompt, or for you to pull your drives. In other words, it's intended for hacked Series 1 SA Tivos only. In addition, I can't support or guarantee anything... if you break your Tivo, you're SOL, yadda yadda yadda. But if do try it, please post your results here. I'd love to know if this helps anyone else. :) (FYI cron doesn't come with the S1 Tivo, but you can download a precompiled version here.)

    The scripts below are for the Eastern time zone. If you live elsewhere, make sure you alter the tcl scripts to set the TimeZoneOld variable for your own timezone as follows:

    Central time:
    In DST_on.tcl, set TimeZoneOld to 1
    In DST_off.tcl, set TimeZoneOld to 2

    Mountain time:
    In DST_on.tcl, set TimeZoneOld to 2
    In DST_off.tcl, set TimeZoneOld to 3

    Pacific time:
    In DST_on.tcl, set TimeZoneOld to 3
    In DST_off.tcl, set TimeZoneOld to 4

    General case:
    In DST_on.tcl, set TimeZoneOld to the code representing your offset from GMT during Daylight Savings Time
    In DST_off.tcl, set TimeZoneOld to the code representing your offset from GMT during Standard Time.


    DST_on.tcl: (run this on the 2nd Sunday in March, 1st Sunday in April, and last Sunday in October)
    Code:
    #!/tvbin/tivosh
    source /tvlib/tcl/tv/Inc.itcl
    source /tvlib/tcl/tv/mfslib.tcl
    set db [dbopen]
    try { transaction {
    set setup [db $db open /State/LocationConfig]
    puts "Springing ahead one hour ..."
    dbobj $setup set TimeZoneOld 23 
    } } catch errCode {
        puts "Sorry, an error occurred: $errCode"
        puts "NOTE: This script is only known to work on TiVo Series 1 Standalone"
        puts "models with s/w version 3.0-01-1-000"
        dbclose $db
        unset db
        exit 1
    }
    dbclose $db
    unset db
    event send $TmkEvent::EVT_DATA_CHANGED $TmkDataChanged::SCHEDULE 0
    puts "Done"
    DST_off.tcl (run this on the 1st Sunday in November):
    Code:
    #!/tvbin/tivosh
    source /tvlib/tcl/tv/Inc.itcl
    source /tvlib/tcl/tv/mfslib.tcl
    set db [dbopen]
    try { transaction {
    set setup [db $db open /State/LocationConfig]
    puts "Falling back one hour ..."
    dbobj $setup set TimeZoneOld 1
    } } catch errCode {
        puts "Sorry, an error occurred: $errCode"
        puts "NOTE: This script is only known to work on TiVo Series 1 Standalone"
        puts "models with s/w version 3.0-01-1-000"
        dbclose $db
        unset db
        exit 1
    }
    dbclose $db
    unset db
    event send $TmkEvent::EVT_DATA_CHANGED $TmkDataChanged::SCHEDULE 0
    puts "Done"
    crontab entries:
    Code:
    1 7 8-14 3 0 /var/hack/bin/DST_on.tcl; echo "`date` - Reboot for DST fix (spring ahead)" >> /var/log/cronlog_dst; sync; /sbin/restart
    1 6 1-7 4 0 /var/hack/bin/DST_on.tcl; echo "`date` - Reboot for DST fix (undo TiVo spring ahead)" >> /var/log/cronlog_dst; sync; /sbin/restart
    1 6 25-31 10 0 /var/hack/bin/DST_on.tcl; echo "`date` - Reboot for DST fix (undo TiVo fall back)" >> /var/log/cronlog_dst; sync; /sbin/restart
    1 7 1-7 11 0 /var/hack/bin/DST_off.tcl; echo "`date` - Reboot for DST fix (fall back)" >> /var/log/cronlog_dst; sync; /sbin/restart
    WARNING: It turns out that this crontab is broken. It runs every day of the week of the time change, AND every Sunday morning at 2:01 am during that month. For an updated version, please see Post #446 below. The scripts in this post will work fine when used without cron, however.
     
  6. LoadStar

    LoadStar LOAD"*",8,1

    35,696
    391
    Jul 24, 2001
    Milwaukee, WI
    You know, this is the part that irritates me more than anything else.

    No matter what the reason that TiVo decided not to update the series 1 units - whether it be financial, technical, or even if they just didn't feel like it - had they said something more than 3-4 days ahead of time, someone like jberman would've been able to come up with something as a work-around with enough time before the DST changeover.
     
  7. BTUx9

    BTUx9 back?

    1,596
    0
    Nov 13, 2003
    Rockport, MA
    did you check your todo list?
    I may be wrong, but I believe tivo schedules repeating manual recordings ahead of time, so if you change your timezone when DST actually changes, any manual recordings that are already scheduled will be off by one hour.
     
  8. jberman

    jberman Mostly Harmless

    102
    0
    Oct 1, 2002
    Update: Just confirmed that newly-scheduled manual recordings are working perfectly... and even the ones that I scheduled before creating this workaround are still scheduled to record at the correct time. Woo hoo!
     
  9. timckelley

    timckelley Top most important TCFer

    28,202
    168
    Oct 15, 2002
    Austin, TX
    If jberman, who I assume doesn't work for TiVo and is not one of the authors of the TiVo software, could figure this out, why couldn't TiVo's programmers and authors figure it out?
     
  10. BTUx9

    BTUx9 back?

    1,596
    0
    Nov 13, 2003
    Rockport, MA
    just to verify... let's say you set a manual recording before changing TZ, and in todo, it was scheduled for this monday from 2-3 (according to the tivo, which would have been an hour off and the actual recording would be 3-4)
    Now, you've changed the TZ, and the recording is still scheduled for 2-3 on Monday, right?

    If so, then congratulations... I think you've found a very workable solution to the problem.
     
  11. jberman

    jberman Mostly Harmless

    102
    0
    Oct 1, 2002
    Uh, thanks! No, I don't work for Tivo, and I really have only a limited experience in hacking it. But I can't really take too much credit for this (in fact I can't even say with 100% certainty that it works yet - won't really know until after April 1, though indications are good). Most of the information I needed came from this thread, especially post #9 (thanks sbourgeo!). I just put the pieces together, is all.
     
  12. jberman

    jberman Mostly Harmless

    102
    0
    Oct 1, 2002
    BTUx9 -

    That's right. For years now I've had a manual recording set to record every Friday night from 11:30 pm - 12:00 am. Now that I've changed the time zone, the ToDo list still shows the manual recording scheduled from 11:30 pm - 12:00 am. Since my Tivo's GMT setting is also correct, there's every reason to expect that it will record on-time, as scheduled. :D
     
  13. BTUx9

    BTUx9 back?

    1,596
    0
    Nov 13, 2003
    Rockport, MA
    Umm... while this will help many people, it isn't a method that could be released in production, because times on either side of the DST change will be off, and that would freak some people out.

    people are reading tivo's declaration of "Our engineers have been working on alternate solutions for the Series1, but unfortunately none exist.", and are inferring that to mean the engineers can't fix the software, but that's patently untrue.

    The "alternate solutions" are probably given the constraints of "no downloads of new s/w for series 1 machines", and under those constraints, that statement is true.

    They've just spun the wording to look like a technical problem.
     
  14. timckelley

    timckelley Top most important TCFer

    28,202
    168
    Oct 15, 2002
    Austin, TX
    Not very many days ago, one of the TiVo employees posted here, and said that many TiVo employees have series 1 machines, and they want to fix the DST problem, and that they won't "leave us high and dry". (This was before the recent announcement that they're going to stiff us on the patch.) This announced intention that they had made at that time, seems to imply that they were willing to send download patches to us, that there wasn't some rule against letting us download a patch to the S1's.
     
  15. BTUx9

    BTUx9 back?

    1,596
    0
    Nov 13, 2003
    Rockport, MA
    Don't you think that could have been a corporate over-rule?

    As a programmer, I just can't IMAGINE not being able to fix this given the full source code.
     
  16. sbourgeo

    sbourgeo Hepcat Daddio

    7,662
    26
    Nov 10, 2000
    New England
    Nice jberman! I have to admit that I gave up on TimeZoneOld since I am in the Eastern zone and was too dense to notice that it could be set to "GMT-X" values. :p

    That seems like workable solution since the bash prompt would continue to display GMT, which what the guide data works off of...
     
  17. jimnoblett

    jimnoblett Member

    238
    0
    Nov 18, 2001
    Somewhere...
    I suspect that the post TiVoJerry made here was given to him by the TiVo legal department, and was meant to deflect liability. Since jberman's patch seems to work, I would like to see TiVoJerry step up to the plate and explain WHY TiVo can't seem to fix this.
     
  18. sbourgeo

    sbourgeo Hepcat Daddio

    7,662
    26
    Nov 10, 2000
    New England
    Must be. All of us corporate drones have to stick with the company line ya know... :)

    My disappointment is with the decision made by TiVo the company, and not with Pony, Jerry, and Stephen, who have helped out a lot of us here on many occasions.
     
  19. jberman

    jberman Mostly Harmless

    102
    0
    Oct 1, 2002
    I can confirm that. It's 8:35 am here on the east coast, and the bash prompt returns GMT as follows:

    bash-2.02# date
    Mon Mar 12 12:35:30 localtime 2007


    Perfect. :)
     
  20. bicker

    bicker bUU

    10,442
    47
    Nov 9, 2003
    Georgia
    To be fair, my cable company DVR is much much better than my TiVo S1. No problems whatsoever with the DST change on my cable company DVR.
     

Share This Page