Feed aggregator

Finding Tivo model number

TiVoCommunity Forum Recent Threads - Fri, 01/03/2014 - 08:31
Is there a screen in Tivo Central that shows the model number of a Tivo. I am in the process of buying a replacement drive from Weeknees and want to make sure I get the correct drive. I have a Tivo 2 tuner Premiere (the original one not one of the newer ones with the smaller hard drive).

As a side note, it appears that Weaknees is the cheapest place to buy a formatted drive. Unless someone knows of a cheaper place.

Thanks for the help.

channel listings with 3 same channels

TiVoCommunity Forum Recent Threads - Fri, 01/03/2014 - 08:16
Why do some channels have 3 channels listed in the guide?
I understand there is usually a lower channel number for SD and an equivalent high channel number for HD, but sometimes there is an intermediate channel number as well. In the examples below, all of them have the same programming. There are more examples, but I just listed 3.

AMC channels 63, 550 & 1652
Animal planet channels 36, 254 & 1622
CNN channels 46, 311 & 1630

I'm trying to (painfully) go through my channel list and remove duplicate channels and only leave HD channels when SD channels exist. Looks like when I'm finished I won't be getting the 200+ channels that Time Warner Austin says I get for my monthly sub. :confused:

Also, I've very concerned that after I go through all of this trouble that any glitch or software reset might erase all of my efforts. It would be so nice if one could backup this type of stuff with the ability to restore it in such a situation.

What To Expect From TiVo At CES

Zatz Not Funny! - Fri, 01/03/2014 - 07:34

With CES mere days away, it’s time to flex our predictive musculature. Mari’s gone broad with the TV trends, but I’m dialing it down to a single set-top manufacturer we know so well. Unlike years past where TiVo hid themselves at the end of an obscure, dusty hallway for invite-only meetings, TiVo’s invested in a [...]

The post What To Expect From TiVo At CES appeared first on Zatz Not Funny!.

The Big Bang Theory [01/02/2014] - "The Hesitation Ramification"

TiVoCommunity Forum Recent Threads - Fri, 01/03/2014 - 07:11
Oh dear.
Penny: Let's get married?
Leonard: What?
Penny: Leonard Hofstadter, will you marry me?
Leonard: Um....
Penny: Did you seriously just say "Umm..."? Also, I'm going to have to re-watch the ending where Sheldon was so supportive. I kept expecting it to be some kind of dream.:confused:

Treme Season 4 (Final Season and Final Episode) *spoilers*

TiVoCommunity Forum Recent Threads - Fri, 01/03/2014 - 05:52
This was one of those low key shows that I really liked. I'm glad HBO stuck with it even though it wasn't that popular.

There was a big cast, some of whom connected with me more than others. Antoine and his family and the kids in the band, Chief Lambreax and his son, LaDonna and her family, Janet Desautel, Toni Collette. Those were the characters I cared for the most.

It took me a while to warm to Davis. I hated him the first season but as the seasons went by, I grew to like his character more.

I never really grew to like Annie Tee. She just never seemed to fit into the rest of the show to me. Maybe it's because she started the show with Sonny whom I loathed for every second of his screen time. Then she was attached to Davis as one of the world's most mind bendingly bizarre couples and I've been ambivalent about his character. She was so miserable this final season that I couldn't wait until her scenes were over.

Terry the cop never really grabbed me but I liked him with Toni. But then he just bailed on her when he resigned and I thought "You jerk!"

I kinda liked Nelson Hildago but to paraphrase something his character said in the last episode, he came to town and made a lot of money but didn't really accomplish anything. That's pretty much how I feel about his character.

There are some actors that I just plain like and am happy to see them turn up on shows: Wendell Pierce, Khandi Alexander, Kim Dickens, Clarke Peters. I hope to see them again.

1080 p 60 fps - new S5 feature

TiVoCommunity Forum Recent Threads - Fri, 01/03/2014 - 03:41
I mirror my roamio to two displas. A 1080P projector, and a 1366 X 768 plasma. my avr's don't offer scaling features so my displays are fed pure signals from TiVo. My findings are that 1080i content looks better outpit at 1080p when viewed on my 1080 projector. because of this result I was also hoping 720P content would look just as good on my 720p plasma when the TiVo was set to output 1080P fixed. this would be good because then I wouldn't worry about time out for resolution changes when changing channels. unfortunately after more testing, 720 P material still looks better output of TiVo at 720 P when out put to my 720p plasma. 1080p playback doesn't seem quite as soon as smooth. Like less frame rate. so I'm glad series 5 tivo has1080 P 60 fps, its just too bad 1080 P output doesn't look as good as 720 P output on my 720 display. end result is I have the following 3 rez outputs in settings checked :
-1080P 24 Fps pass through.
Ill do some more critical testing of 1080p 24 FPS later, but I presume if you have a display that correctly handles pull-down such 24fps films such as on Netflix, then its better to enable this.

Comcast VOD with Netflix on TiVo Roamio

TiVoCommunity Forum Recent Threads - Fri, 01/03/2014 - 02:09
When was this announced? Not sure which is bigger, Comcast supporting TiVo Roamio or Netflix. 2014 is going to be an interesting year!


Comcast customers rejoice!

Only TiVo offers you all your entertainment from TV, the web and XFINITY® On Demand in one box.

XFINITY On Demand comes together with the best stuff on the web—like Netflix, Hulu Plus, YouTube and more—all on a TiVo DVR.

XFINITY On Demand works on TiVo Roamio and Premiere DVRs

Why switch to a TiVo DVR?

Replaces your cable box (CableCARD required)
Up to 75, 150 or 450 hours of recording capacity
Records up to 4 or 6 shows at once
Searches TV and the web simultaneously
Access XFINITY On Demand and Streampix
Comcast can assist with set up of your TiVo DVR

Tivo Series 3 HD w/ Lifetime for sale

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 23:49
Original Owner series 3 for sale, with Lifetime service.
Model is TCD648250B, that is THX-certified and has a digital readout on the front, software 11.0m-01-2-648

35 hrs HD / 303 SD hours capacity.

Includes manuals, cables, 2 remotes ( one great, one iffy)

$275 plus shipping from LA, CA

Please PM for pics.



S3 Consolidation while preserving recordings

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 23:39
I wanted to share some of my experiences with the group, in case it helps other people. With the help of jmbach, and dougdingle, I was trying to consolidate my S3 OLED which has the original internal drive (250GB) and a 1 TB external drive onto a single 2TB drive. The process was reasonably straightforward once I got the source for the mfstools from the MFSLive CD and fixed the code to properly handle drives larger than 1TB. I used the procedure laid out in
which worked successfully.

But dougdingle mentioned that he had a S3 that he had not been able to upgrade because it had already had its internal drive expanded. So I wanted to see if I could understand the process better.

Here is my understanding of how things work. Someone please correct me if I am wrong on any of this stuff... Some of it is obvious and well-trod knowledge, but I'm trying to piece things together here...

The TiVo has multiple media regions on disk (these are typically the "Media Partitions" in the partition map). However, the way the TiVo keeps track of the various partitions and available space is via the zone map data structures. This is a linked list of structures that has the head in the first application zone. (It may be pointed to in the MFS super block; I'm not sure about that, but the TiVo knows how to find the first zone map, and once it finds the first one, the rest chain off from there.) The zone maps come in three different flavors that describe different things (inodes, application regions, media regions). The way that the tivo points to things on the disk(s) is via sectors. However, the sectors are not the same as the sectors on the disk. (They are the same size, but sector X on disk does not necessarily correspond to sector X in the TiVo's idea of sectors.)

The MFS superblock contains a list of partitions (the devlist). The tivo loads each partition in the order given. The way the TiVo addresses things by sector is by making a contiguous "address space" of sectors by just appending each partition's sectors as the are loaded. So if the devlist contains "/dev/hda10 /dev/hda11 /dev/hda12 /dev/hda13", and those partitions have 10, 20, 30, and 40 sectors respectively, then the contents of hda10 are sectors 0-9, hda11 is 10-29, hda12 is 30-59, and hda13 is 60-99. These partitions may be anywhere on the disk, and they may be on other disks, but they just get loaded contiguously for the purpose of calculating sector addresses.

The zonemaps work in sector addresses, so when the TiVo goes looking for something at sector X, it figures out which partition that sector lies in, then takes the offset into that partition. So as long as you make sure that the partitions are loaded in order, and they are the right size, they can be anywhere. And also, the partition numbers indexed by their order in the partition map, not their order on disk. For example, on the internal drive for my S3 TiVo, the partition map looks like

Code: Partition map (with 512 byte blocks) on '/deskstar/s3-internal-disk.dd'
 #:                type name                        length  base      ( size )
 1: Apple_partition_map Apple                          63 @ 1       
 2:              Image Bootstrap 1                      1 @ 268618469
 3:              Image Kernel 1                      8192 @ 268618470 (  4.0M)
 4:                Ext2 Root 1                      524288 @ 268626662 (256.0M)
 5:              Image Bootstrap 2                      1 @ 269150950
 6:              Image Kernel 2                      8192 @ 269150951 (  4.0M)
 7:                Ext2 Root 2                      524288 @ 269159143 (256.0M)
 8:                Swap Linux swap                  262144 @ 269683431 (128.0M)
 9:                Ext2 /var                        524288 @ 269945575 (256.0M)
10:                MFS MFS application region      589824 @ 270469863 (288.0M)
11:                MFS MFS media region        216747657 @ 271649511 (103.4G)
12:                MFS MFS application region 2    589824 @ 271059687 (288.0M)
13:                MFS MFS media region 2      268618405 @ 64        (128.1G)

Device block size=512, Number of Blocks=488397168 (232.9G)
DeviceType=0x0, DeviceId=0x0 Note that the last partition in the map is actually describing a partition thats first on the disk (media region 2, /dev/hda13). TiVo does this so that the OS is physically in the middle of the disk, with big media partitions on either side to keep the average seek distance down.

When TiVo looks at a partition, it actually rounds the sectors in the partition down to the nearest multiple of 1024. So if you look at /dev/hda11 in the above, its a wierd size (216747657), and is not a multiple of 1024 sectors. I'm not sure why TiVo did this; this is the unmodified disk that came with the unit. So even though the partition is a weird size, TiVo will only consider the partition to have 216747008 sectors. There are 649 sectors at the end of the partition that aren't used. This is important, because when TiVo is counting sectors, it uses the rounded-down number, not the actual size of the partition on disk.

You can see the size of the partitions (as used by TiVo) with mfsinfo.
Code: ---------------------------------------------------------------------
Super Header
        state=0 magic=abbafeed
        devlist=/dev/hda10 /dev/hda11 /dev/hda12 /dev/hda13 /dev/hdc2 /dev/hdc3
        zonemap_ptr=1121 total_secs=2440069120
MFS volume set for /deskstar/s3-internal-disk.dd and /deskstar/s3-external-disk.dd
The MFS volume set contains 6 partitions
  Partition    sectors        size
  /deskstar/s3-internal-disk.dd10        589824          288 MiB
  /deskstar/s3-internal-disk.dd11    216747008      105833 MiB
  /deskstar/s3-internal-disk.dd12        589824          288 MiB
  /deskstar/s3-internal-disk.dd13    268617728      131161 MiB
  /dev/hdc2          4096            2 MiB
  /dev/hdc3    1953520640      953867 MiB
Total MFS sectors: 2440069120
Total MFS volume size: 1191440 MiB
Estimated hours in a standalone TiVo: 1480
--------------------------------------------------------------------- (Note that I'm actually using images of the disks, not the disks themselves. The name of the partitions look a little weird, but everything else is exactly the same.)

So /dev/hda11 is the 11th partition on the internal disk, which from the partition map is 216747657 sectors, but in the MFS volume set is 216747008 sectors. So when TiVo is counting sectors, sectors 0-589823 are on /dev/hda10, then 589824 - 217336831 are on /dev/hda11, then 217336832 - 217926655 are on /dev/hda12, and so on. The partitions on the external disk (/dev/hdc2 and /dev/hdc3) just get loaded sequentially as well; the fact that they happen to be on another disk is just kept track of in the devlist. The list of sectors that TiVo uses is contiguous across all volumes.

So when the TiVo looks at the disks, it loads the partitions in the order listed in the devlist, and builds the mapping of "TiVo sectors" to hard disk sectors. Once that is done, the distinction of where partition boundaries are seems to be lost. This is why the trick of collapsing or coalescing multiple partitions into one (as referenced in the thread mentioned above) works. If you take partitions that are contiguous in load order (meaning their partitions are sequential in the devlist) and you concatenate them, and you increase the size of the entry in the partition map to include the added data, then the whole big block will be loaded and the data in the concatenated partitions will be found just fine. A few things to remember, though. If you are going to concatenate one partition onto the end of another, you need to add the data starting at the end of the active part of the partition, if the partition isn't a multiple of 1024 sectors. Otherwise, the "unused" sectors at the end of the first partition will get included when the partition is loaded which will screw up the sector counts, and will make all of the sector offsets be wrong. (Meaning that the zonemaps will not be where they are supposed to be, and nothing will work.) The other thing is that you can only concatenate partitions if they are sequential in load order. Partitions that are physically adjacent on disk might not be adjacent in load order, so you can't assume that partitions that are adjacent on disk can be combined. Load order is dictated by the devlist.

So as long as you keep these rules in mind, you can move partitions around, change the order in the devlist, reorder the partition map, etc, as long as the result is that the data will all be loaded in the same order.

One other side note: it appears that if the TiVo starts up and finds that some of the partitions in the devlist don't exist, and your TiVo has an external drive, then it will bring up the "I can't find the external drive. Do you want to divorce it?" screen. Then, when you tell it to go ahead, it loads all the partitions in the devlist, then starts looking at all of the shows in the filesystem. It will delete any shows that it doesn't have all of the data for, but keep all of the ones that it does have all of the data for. So in the earlier thread, the idea is that we take the data from the partitions that used to be on the external drive, concatenate them into an existing partition on the internal drive, and change the partition map so that there is one entry that includes the sectors from all three partitions. That way, when the TiVo boots, it will load all of the data (because all of the sectors are now contained in the remaining partitions), but it will see some partitions are missing, and bring up the divorce screen, and do the divorce process. During the divorce process, it won't find any sectors missing, so it will complete successfully, and keep all of the recordings.

So given this knowledge of a set of behaviors, I wanted to see if I could combine a setup like Doug's, with an expanded internal drive and an external drive. I took a couple of 1 TB drive and copied (just using dd) my real internal and external drives onto them. I then ran mfsadd to expand the internal drive, and offered it to the TiVo, and it was perfectly happy with this pair. It found and used the additional partition pair.

So the partition map for the internal disk is
Code: Partition map (with 512 byte blocks) on '/dev/sdc'
 #:                type name                        length  base      ( size )
 1: Apple_partition_map Apple                            63 @ 1       
 2:              Image Bootstrap 1                      1 @ 268618469
 3:              Image Kernel 1                      8192 @ 268618470  (  4.0M)
 4:                Ext2 Root 1                      524288 @ 268626662  (256.0M)
 5:              Image Bootstrap 2                      1 @ 269150950
 6:              Image Kernel 2                      8192 @ 269150951  (  4.0M)
 7:                Ext2 Root 2                      524288 @ 269159143  (256.0M)
 8:                Swap Linux swap                  262144 @ 269683431  (128.0M)
 9:                Ext2 /var                        524288 @ 269945575  (256.0M)
10:                MFS MFS application region      589824 @ 270469863  (288.0M)
11:                MFS MFS media region          216747657 @ 271649511  (103.4G)
12:                MFS MFS application region 2    589824 @ 271059687  (288.0M)
13:                MFS MFS media region 2        268618405 @ 64        (128.1G)
14:                MFS New MFS Application            2048 @ 488397168  (  1.0M)
15:                MFS New MFS Media            865107968 @ 488399216  (412.5G)
16:          Apple_Free Extra                    600017984 @ 1353507184 (286.1G)

Device block size=512, Number of Blocks=1953525168 (931.5G)
DeviceType=0x0, DeviceId=0x0 and the partition map for the external disk is
Code: Partition map (with 512 byte blocks) on '/dev/sdd'
 #:                type name                      length  base      ( size )
 1: Apple_partition_map Apple                          63 @ 1       
 2:                MFS MFS application region      4096 @ 64        (  2.0M)
 3:                MFS MFS media region      1953521008 @ 4160      (931.5G)

Device block size=512, Number of Blocks=1953525168 (931.5G)
DeviceType=0x0, DeviceId=0x0 and MFSInfo for the combined pair gives
Code: ---------------------------------------------------------------------
Super Header
      state=0 magic=abbafeed
      devlist=/dev/hda10 /dev/hda11 /dev/hda12 /dev/hda13 /dev/hdc2 /dev/hdc3 /dev/hda14 /dev/hda15
      zonemap_ptr=1121 total_secs=3305179136
MFS volume set for /dev/sdc and /dev/sdd
The MFS volume set contains 8 partitions
  Partition    sectors        size
  /dev/sdc10        589824          288 MiB
  /dev/sdc11    216747008      105833 MiB
  /dev/sdc12        589824          288 MiB
  /dev/sdc13    268617728      131161 MiB
  /dev/hdc2          4096            2 MiB
  /dev/hdc3    1953520640      953867 MiB
  /dev/sdc14          2048            1 MiB
  /dev/sdc15    865107968      422416 MiB
Total MFS sectors: 3305179136
Total MFS volume size: 1613857 MiB
Estimated hours in a standalone TiVo: 2011
--------------------------------------------------------------------- So you can see how the partition I added with mfsadd got stuck on the end of the load order. If the internal disk had been expanded before the external disk was added, those partitions would have showed up before the /dev/hdc partitions in the devlist.

Note that since I copied everything with dd, the original partition (with odd partition sizes) was retained. If you copy things with MFS backup/restore, that makes partitions without extra sectors on the end.

Also note that I used a slightly tweaked version of mfsadd that allows me to hold back some sectors when adding the new partition. The 2TB drive I was using to test combining on is just a little smaller than the combined size of the two 1 TB drives I was using. So I made the added partition a little smaller so that everything would fit. That's why there is a free partition at the end of the disk. It might or might not be there on other systems.

So for this arrangement on disk, TiVo maps sectors to partitions as follows:
Code: hda10:          0 - 589823
hda11:    589824 - 217336831
hda12:  217336832 - 217926655
hda13:  217926656 - 486544383
hdc2:  486544384 - 486548479
hdc3:  486548480 - 2440069119
hda14: 2440069120 - 2440071167
hda15: 2440071168 - 3305179135 We can re-arrange things as we see fit, as long as the data ends being loaded in the correct order.

I started by copying the contents of the internal drive onto a 2TB drive just using dd. Then the problem was how to copy the contents of the external drive (hdc2 and hdc3) and stuff them into an existing partition. The data needs to get loaded right after hda13. But hda13 is at the start of the disk, so there is no room after that. So I decided to put the data at the front of hda14, and change the devlist to move the references to the external partitions to the end. (Those partition reference will be to the no-longer-existing disk that triggers the divorce. I don't know what TiVo would do if the missing partitions are in the middle of the devlist; I probably wouldn't be happy at all, because if the partitions are missing, partitions that are after it in the devlist can't load properly, since the sector numbers would be all wrong.)

I copied all of the data from the external disk and put it at where hda14 starts, then I copied the data from the real hda14 after the external disk's data. I changed the entry in the partition map to make the size of hda14 big enough to encompass all of this data. I also had to re-copy the data from the real hda15, since that partition got moved on disk to accommodate the data from the external drive. I also had to fix the partition map to create the corrected hda15.

To accomplish these moves/copies, I just used dd:
dd if=/dev/sdd of=/dev/sdh bs=512 seek=488397168 skip=64
dd if=/dev/sdc of=/dev/sdh bs=512 seek=2441921904 skip=488397168 count=2048
dd if=/dev/sdc of=/dev/sdh bs=512 seek=2441923952 skip=488399216 count=865107968 For me, /dev/sdc was the 1TB internal disk, /dev/sdd was the 1TB external disk, and /dev/sdh was the 2TB target disk.

(As an aside, the commands I actually used were slightly different, because doing the dd with 512B blocks was really slow. Using 8KB blocks was about 10 times faster. So in the above, I just changed the bs=512 to bs=8k, then divided all of the numbers by 16. I could do that since they were all multiples of 8KB.)

The adjusted partition map looks like
Code: Partition map (with 512 byte blocks) on '/dev/sdh'
 #:                type name                        length  base      ( size )
 1: Apple_partition_map Apple                          63 @ 1       
 2:              Image Bootstrap 1                      1 @ 268618469
 3:              Image Kernel 1                      8192 @ 268618470  (  4.0M)
 4:                Ext2 Root 1                      524288 @ 268626662  (256.0M)
 5:              Image Bootstrap 2                      1 @ 269150950
 6:              Image Kernel 2                      8192 @ 269150951  (  4.0M)
 7:                Ext2 Root 2                      524288 @ 269159143  (256.0M)
 8:                Swap Linux swap                  262144 @ 269683431  (128.0M)
 9:                Ext2 /var                        524288 @ 269945575  (256.0M)
10:                MFS MFS application region      589824 @ 270469863  (288.0M)
11:                MFS MFS media region        216747657 @ 271649511  (103.4G)
12:                MFS MFS application region 2    589824 @ 271059687  (288.0M)
13:                MFS MFS media region 2      268618405 @ 64        (128.1G)
14:                MFS New MFS Application    1953526784 @ 488397168  (931.5G)
15:                MFS New MFS Media            865107968 @ 2441923952 (412.5G)
16:          Apple_Free Extra                    599997248 @ 3307031920 (286.1G)

Device block size=512, Number of Blocks=3907029168 (1.8T)
DeviceType=0x0, DeviceId=0x0 So you can see that the "New MFS Application" partition is now huge, since it contains the data from the external disk.

When I run mfsinfo on it, I get
Code: ---------------------------------------------------------------------
Super Header
      state=0 magic=abbafeed
      devlist=/dev/hda10 /dev/hda11 /dev/hda12 /dev/hda13 /dev/hda14 /dev/hda15 /dev/hdc2 /dev/hdc3
      zonemap_ptr=1121 total_secs=3305179136
MFS volume set for /dev/sdh
The MFS volume set contains 8 partitions
  Partition    sectors        size
  /dev/sdh10        589824          288 MiB
  /dev/sdh11    216747008      105833 MiB
  /dev/sdh12        589824          288 MiB
  /dev/sdh13    268617728      131161 MiB
  /dev/sdh14    1953526784      953870 MiB
  /dev/sdh15    865107968      422416 MiB
  /dev/hdc2            0            0 MiB
  /dev/hdc3            0            0 MiB
Total MFS sectors: 3305179136
Total MFS volume size: 1613857 MiB
Estimated hours in a standalone TiVo: 0
--------------------------------------------------------------------- You can see that I've reordered the devlist to move the reference to hdc2 and hdc3 to the end of the list. (You might have to scroll the text box above to the right to see it.) That way the TiVo will see them as missing, but won't give up on other partitions that would otherwise have followed them.

mfsinfo shows /dev/hdc2 and /dev/hdc3 as 0 size because they are missing. If I take the reference to /dev/hdc2 and /dev/hdc3 out of the devlist, mfsinfo is completely happy with the consolidated disk, and reads and validates the zonemaps without a problem. But if I put it into the TiVo like that (with hdc2 and hdc3 not in the devlist), it would complain about an incorrect storage device. But with the references to hdc2 and hdc3 back in the devlist, it figures out that it needs to divorce the disk.

So to test it out, I offered the disk to the TiVo and it did what was expected. It did the divorce (which took 5-10 minutes or so), then rebooted and all of the recordings were still there, and the TiVo reported the correct size.

Looking at the drive post-divorce with mfsinfo shows:
Code: ---------------------------------------------------------------------
Super Header
      state=0 magic=abbafeed
      devlist=/dev/hda10 /dev/hda11 /dev/hda12 /dev/hda13 /dev/hda14 /dev/hda15
      zonemap_ptr=1121 total_secs=3305179136
MFS volume set for /dev/sdh
The MFS volume set contains 6 partitions
  Partition    sectors        size
  /dev/sdh10        589824          288 MiB
  /dev/sdh11    216747008      105833 MiB
  /dev/sdh12        589824          288 MiB
  /dev/sdh13    268617728      131161 MiB
  /dev/sdh14    1953526784      953870 MiB
  /dev/sdh15    865107968      422416 MiB
Total MFS sectors: 3305179136
Total MFS volume size: 1613857 MiB
Estimated hours in a standalone TiVo: 2011
--------------------------------------------------------------------- and we can see that the TiVo got rid of the reference to /dev/hdc2 and /dev/hdc3.

So the point of this exercise was to show what you can do if you stay within the rules. I tried to do some of this with MFS backup/restore, but that doesn't seem to deal properly with partitions that have been consolidated (and that required me to modify the source volume). It also doesn't deal well at all with creating a destination volume with more than 16 partitions. (The TiVo can't deal with that disk, but I might have wanted it to just do the copy, and then I would consolidate the partitions post-restore.) MFS restore has the 16 partition limit hard coded in a number of places, so it looked like it was going to be a pain to modify. Its not clear what the backup/restore approach does for you if you're copying all of the video streams. If you're copying all of the data, you can accomplish the same thing with dd. But for normal operations, backup/restore are much easier to use, and a lot more failsafe. And they make nice even partitions.

But you could accomplish all of that (partition aligning, moving, reordering, etc) with dd and pdisk. The only thing magic I used was a quick tool to allow manipulation of the devlist. I did all of the above using Debian 12.04 LTS.

Mini power connection

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 22:10
This has to be the worst designed power connection of all time. I swear just touching either of my units or trying to move them causes a loss of power and a reboot. This is my biggest beef with the mini units. The power connections just are not positive IMO.

Community - 'Re-Pilot'/'Introduction to Teaching' 1/2/2014 S05 Ep 1 and 2

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 21:34
Community returned tonight with Dan Harmon back at the helm.

I enjoyed both episodes. Thankfully I hadn't deleted my season pass last year and this was recorded for me. thanks tivo!

Love the addition of Jonathan Banks, but then I loved him on Breaking Bad and way back with Wiseguy.

Magnitude's 'pop pop' during the riot was great.

And I loved Abed's Nick Cage.

And I love Kevin Corrigan so it was good to see him again.

what's you think

Freezes since fall update, plus numerous other issues

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 21:26
My Premier 4 is driving my wife and I nuts to the point I may can the thing.

Since we moved in July, we went from Cox communications to Verizon FiOS for an ISP.

I have a Premier 4, and a TiVO mini running over Ethernet off of it.

The mini has ZERO problems. The Premier 4... not so much.

Immediately we saw:

-v301 on apps
-Suggested show images are now just text of the show name, images don't work.
-DNS network tests fail, but everything else in my house works great. Updates and network checkins are all fine.

Then I got the fall update that enabled dynamic tuner support and now:

-Severe freezing on multiple screens.
1. Info screen when changing channels freezes for between 30-60 seconds
2. Post DVR watching, the delete screen freezes without an ad being displayed. Once the freeze stops, the ad shows up immediately. Seems to be related to the advertisements.
3. Turning on the TV, TiVO on 24/7 prior, the screen freezes for 5-10 seconds it seems.

I got the last update expecting the freezes to go away, but no dice.

I've tried everything with network settings, static, new IP ranges, reformatting network devices, etc. With no luck.

Anyone have any suggestions? I'm about to wipe the whole device, but really would like to avoid that.


Channels intermittently unavailable

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 20:52
We just moved into a new place and I got a new Roamio. I'm in Southern NJ on Comcast. About once a day, we lose channels like TNT or TBS - get the "channel is not authorized" message.

I've gone through all the troubleshooting steps listed on TiVo's site (http://support.tivo.com/app/answers/detail/a_id/2571) and everything appears to be in order. Rebooting the TiVo box corrects the problem, for a little while at least,

I have a SA 802 cable card running PKEY1.5.2_F.p.3001.

We are also having the on demand problem I've seen mentioned on other threads and are fighting with Comcast to get that fixed, not sure if it is related.

Thanks for any suggestions on how we can fix this.


Can only keep recordings xx hours?

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 20:18
I was trying to figure out why my recordings of the World Junior Hockey Tourney from the NHL network were not appearing in Tivo. Tonight I started watching a game nearly live and received the message that the recording can only be kept for another ~90 minutes.

I'm familiar with the copy flags but this is much worse. Guessing there is nothing I can do about this but wanted to check with the Tivo crew.

TiVo Help please!

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 20:14
Hello all,
I am new to TiVo and all other 3rd party set top boxes. I currently am a Verizon FiOS customer, and I am paying 15$ a month per HD box (I have two of them). I would like to know, if it is possible to purchase two cable cards from verizon, and run them on a HDMI equiped tivo box with no subscription, just to function as a dumb box capable of decrypting verizon's channels and output in HD. I do not want any DVR functions whatsoever, and I could not care less about on demand. I just want to be able to decrypt verizon's signal (legally) without having to fork over 180$ per year per box. Is that possible, or is it just wishful thinking?

Did not have HD before but I have it now

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 20:13
So I received a Tivo and just got the cable card for it today and got it all working. So before I did not have HD channels but with the Tivo I can receive them. Is this normal for it to be able to get HD channels without an HD channel package?

Problem setting up MOCA on Roamio Plus with FIOS

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 19:00
I have FIOS with the Actiontec Router. I recently purchased a Roamio Plus for the living room that is co-located with the Actiontec router to which is it currently connected via Ethernet. I also have a Premier XL4 upstairs in the media room that is currently connected via wireless. This all works fine, however I wanted to take advantage of multiroom streaming as well as faster transfers. The wireless connection is too slow to keep up.
So I have been experimenting with implementing MOCA since both of my Tivos are MOCA enabled, but been running into problems. The coax wiring infrastructure is as follows. From FIOS ONT box in garage coax goes to attic where I have a 4-way splitter with the 4 coax runs terminating in my living room, media room, master bedroom, son's bedroom. The Actiontec router is installed on the living room run.
Being a noobie with MOCA my first attempt was to change the network settings on the Roamio. I left the ethernet connected and chose the option to use this TIVO to set up a MOCA network., That was a misktake as it essentially took out my wireless network. I went back to ethernet connected only and disabled MOCA and the wireless network returned to normal operation ( I have 50/25 service on FIOS). I then went to my XL4 and tried to connect via MOCA in the network settings. I used the default MOCA settings. I got a C19 network error. I went back and re-enabled the wireless connection
I also then tried to connect the Roamio via MOCA in the network
settings using the defailt MOCA settings and got the same C19 network error.
So I called Tivo support. They recommend I reboot the Actiontec and both Tivos...and then try to connect the Roamio with MOCA using the defauilt settings. I did this and it appeared to be successful. The network status was
"Ethernet+MOCA", but it showed the MOCA link down in the diagnostics. Thnking I had some level of success, I went to the XL4 and attempted to MOCA connect. I got the same C19 error. I ran network diagnostics. The DNS test passed, but the TCP/IP Port test failed saying port 37 , 80 and 7288 needed to be enabled on my router. I then went to check on my wireless network from my laptop to see if the MOCA connection on the Roamio was impacting other devices. I did have a network connection, but the performance was so low it took over two minutes to just get to Google. So I reset everything back to where I initially started so the rest of my network clients (family) would return to smiling.
I do not think I have a POE filter...not sure if that is an issue. Other than that I am at a loss to figure this out. I would appreciate any advice by those with MOCA experience. Thanks in advance for your help..and Happy 2014...

XL4 all 4 tuners BLACK!

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 18:47
Never had this happen before. I turned on the TV and the screen was Black with no audio! Cable was OK as I checked a Tivo in another room.

Looked at all 4 tuners and still same thing no matter what station. HD Menus are all OK. Looked at sig level and Tivo said they were OK as well. I did a soft reboot and all is OK. I am connected via HDMI, but the menu showed, so cable was not the issue.

Any idea what could be wrong or is this just a fluke? Still looking good today.

Caller ID on television with TiVo Roamio & Premiere / caller ID on TV without cable

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 16:55

60% of American households have landline telephone service. Cable TV STB/DVR provide caller ID on-screen for incoming calls, when subscribed to a cable double-play and triple-play bundle with digital telephone service.

Many consumers find caller ID on TV convenient. People who switch from cable STB / DVR to TiVo -- or who cut the cord entirely -- may still want caller ID on screen. Roamio and Premiere are not hackable like previous TiVo models to add this feature. I found one solution, a DIY device that keeps television content at HD quality, called the NeTV. It is paired with a USB modem or ATA box (like a Vonage, Obi, or Linksys SPA device) and open-source NCID software to transmit the caller ID information.

Full version:


Longtime lurker here. After becoming a cable 'cord cutter' and buying TiVo, I spent hours of research here and elsewhere trying to figure out how to get caller ID on screen.

(Before anyone jumps in with the usual sarcastic quips about caller ID on television, please see my preemptive answers in the section below.)

Most of the threads on TCF addressing this topic -- some of which I've compiled in a list at the bottom -- are more than 2 years old, and have thoroughly hashed out the pros and cons of on-screen caller ID.

As many of you probably know, Caller ID on the TV screen was possible with TiVo in the past with DirecTiVo and with series 1 or by modding / hacking the EEPROM on series 2 and series 3 models.

But that ability was lost with TiVo Premiere and Roamio.

Desire for on-screen Caller ID

A majority of American households (60.6%) have landline telephone service (source: CDC-NCHS, Dec. 2013), with many households using Vonage, MagicJack, Ooma, CMRS Wireless Home Phone by AT&T / Verizon / Straight Talk / T-Mobile / Sprint, or another VoIP provider.

Many people with cable TV with set-top box service have become accustomed to caller ID on screen. It's likely that some people cutting the cord from cable triple-play or double-play bundle service or who are switching from their MSO cable provider STB/DVR to TiVo would like to keep their old 'default' option for caller ID information on-screen.

As other posters have eloquently stated in past threads:

Quote: "The TV is the display you're most likely looking at, while in the family/living room. Makes more sense to have caller ID info there, than on a tiny screen on a phone base"... "That way you can decide if you need to get up off the couch, or pick up the phone." ah30k:
Quote: "In my opinion, pausing the current show so that I can find the handset and look to see who is calling is annoying." miller890:
Quote: "While watching Tivo, my biggest interruption is the phone ringing. CallerID on screen would mean no more pausing and looking for the cordless phone. " JWThiers:
Quote: "The Onscreen CallerID is what I miss the most about my hacked DirecTivo.... It beats reaching for the phone to see who is calling, its displayed right on the TV. " Quote: "Have you ever had on screen caller id for any length of time? It can grow on you really quickly. A perfect example of when it is really convenient, sometimes I actually do watch live tv (I know scary) [...] and the phone is on the other side of the room [...]. Wouldn't it be nice to have that information just a glance away? " BlackBetty:
Quote: "The convience would be that when the phone rings, you just glance at your TV to see who's calling you. Instead of having to hunt down your cordless phone and then realize that you got up to find your cordless and you didn't even want to talk to the person calling in the first place. "
Other, old solutions

I looked at some of the workaround solutions people have discussed previously, but they're ugly.

1. The CallerTV box, by NetMedia, inserts itself between the TiVo and the television, but uses composite video for it's signal in and signal out (no HDMI model available), which creates an ugly result, obviously. Also, the Roamio doesn't have analog out, so you couldn't use this device (without a digital-to-analog converter or DAC) even if you wanted to.

2. The TelNote, by Southlake, is just a gawky device (connected only to the telephone line, not the television devices) -- especially to have it sit on or adjacent to your TV in an otherwise sleek entertainment center. (And it's $50-$90+, which is expensive for what it does).

New solution

I spent hours looking for a solution that would:

1) place caller ID information on screen, while
2) keeping the video signal in high-definition (HDMI)

I already submitted a feature request through TiVo's website for caller ID on-screen with the Premiere through a TiVo approved add-on device, but obviously that's not actually going to be realized.

The only solution I could find that's for sale at this time is a DIY (do-it-yourself) device called the NeTV by Adafruit. It's a cousin to the Raspberry Pi, which was covered in the tech news a lot in 2012 and 2013.

The NeTV is placed between the TiVo and the television -- it has HDMI passthrough, with an HDMI input that comes from your TiVo or other tuner and and an HDMI output that goes to the television.

You add an analog telephone adapter (ATA) with an RJ-11 jack (to insert the telephone line), so you can capture the caller ID information from incoming calls.

As your ATA, you can use either a USB modem or a full-scale telephony device (I believe that Vonage and Obi boxes and the Linksys SPA-1302 would work). After researching it, I believe that the ATA can be located in an entirely different room (e.g., where the telephone line comes in), and can transmit the caller ID information from the ATA by ethernet or WiFi (depending on the ATA specs) to the NeTV.

There is an open-source software effort (called NCID on Sourceforge) to help with capturing caller ID information from the ATA, transmitting it to the NeTV, and displaying it on-screen. TCF user JLC has written about this effort previously.

For more info, also look at the posts by user TAA on the Kosagi website. Also, TCF user LRHorer has discussed in previous posts how he set up his Vonage ATA to send caller ID information over Ethernet/WiFi to his NCID clients and had the information display on-screen.

Preemptive answers to the usual sarcastic responses

TCF user Tiassa usually jumps into these caller ID threads to say:

Quote: "There is this really cool invention called the "Wireless telephone handset". Not only does it give you the caller ID, it allows you to answer the phone as well!" Quote: "Just get a cordless handset...then you can answer the call." Quote: "buy a cordless phone with caller ID display. That way you can not only see who is calling, you can answer the phone as well! " My response: See other TCF users' response above. In summary, the whole reason I want caller ID on screen is that I'm already looking at the TV screen, so I want the information on that screen.

TCF user AbMagFab has responded that he doesn't have a telephone jack near his TiVo and doesn't want to run a telephone line to the television area.

My response: As I note above, you can keep the ATA device in a separate area near the telephone jack, and it can still transmit caller ID information by WiFi or ethernet to the NeTV.

TCF user Sugarbowl suggested just using the Telnote to avoid the difficulties of caller ID on screen.

My response: I'm not interested in a separate gawky device in the field of vision like the Telnote marring on an otherwise 'clean' looking entertainment center.

Main old threads from TCF about caller ID on-screen with TiVo

"Caller ID and Screensaver?"
TCF showthread.php?t=447275

"Caller ID on-screen"
TCF showthread.php?t=351434

"Caller ID?"
TCF showthread.php?t=495937

"Wife asks where is Caller ID?"
TCF showthread.php?t=430359

"On screen caller id? "
TCF showthread.php?t=351417

Changing from OTA to Cable

TiVoCommunity Forum Recent Threads - Thu, 01/02/2014 - 15:46
I currently have a 4 Tuner Tivo Roamio hooked up to an OTA antenna. I am getting Charter Cable installed tomorrow and will of course be getting a Cable Card and Tuning Adapter. My question is this.

Is there anything I should do to the Tivo prior to the installer coming out to get it ready to switch from OTA to Cable?



Subscribe to TiVoCommunity aggregator