Ezra Pound
Well-Known Member
Polite, as ever, so what is your theory, or are you too busy re-writing Raydon's code
[CFW 2.19/1.03.06] Custom firmware for version 1.03.06
- Thread starter af123
- Start date
Ezra Pound
Well-Known Member
I think you may have hit on something there, I had 20 current and 48 non current (dead) entries in my schedules list, so I tried a test with and without the 48 non current entries, with a surprising result. With 20+48 entries in the schedule it took 56 seconds to scroll through all 42 entries in my Favourites list and with 20 + 0 entries in my schedule it took just 37 seconds to scroll through the same 42 entries in my Favourites list - good result
EDIT
Tried 20+0 again and got an even lower figure of 29 seconds
I have been using this version since the day it was released, and have never noticed the EPG to be lagging. This could be because I only have the HD channels tuned into my boxes.
Black Hole
May contain traces of nut
How are we to interpret that? Does it mean "I have loaded 1.03.06 and observe no lag whatsoever" (which would be a useful contribution), or does it mean "I have not tried out 1.03.06 but I don't believe there is a lag effect"? I suspect the latter.
If you have nothing useful to say, just keep schtum - this will do your reputation no end of good. As things stand you are making yourself appear utterly ridiculous and dismissible.
Wallace
Traveler 34122
Back on topic.
I have loaded 1.03.06 on all my machines now and I don't have any dead schedule entries (my OCD forbids it!). I can say that there is a very small lag compared to using 1.02.32. So small I would say that if I hadn't used 1.02.32, I would just think it was normal. This is true of all of my three HDR's.
HTH
I have loaded 1.03.06 on all my machines now and I don't have any dead schedule entries (my OCD forbids it!). I can say that there is a very small lag compared to using 1.02.32. So small I would say that if I hadn't used 1.02.32, I would just think it was normal. This is true of all of my three HDR's.
HTH
I think it is just you.
I am certainly not aware of any posts being deleted from the 11 minutes between post #140 and #141.
Black Hole
May contain traces of nut
? Post 141 quotes a previous post, and if you follow the link you will see the context.
Black Hole
May contain traces of nut
Oh, it makes quotes invisible too? That's confusing!
Luke
Well-Knwοn Мember
I've loaded 1.03.06 on an old HDR-FOX (loader 7.30) that was on 1.02.29 and had just had a reset while on 1.02.29. A reset while it's been on 1.03.06 has not been actioned. After the epg populated I then used the right button within the epg. It took twice as long as my 1.02.20 HDR-FOX (loader 7.31) currently is. The 7.31 with 1.03.06 has currently got an empty schedule (well it would do wouldn't it after the reset on 1.02.29). When I temporarily put 1.03.06 on the one with loader 7.31 a few weeks ago it took six times as long compared to 1.02.20, but it did have more timers back then than now.
I.e. I have a 3 fold increase in speed than I was expecting, but what I did was not a totally fair comparison.
I'll have a play at the weekend and set them up identically on 1.02.20 then change the 7.31 to use 1.03.06, and see how they compare.
I hope that makes since. I’m a bit rushed this week.
BTW I do know that the loader makes no difference. It is just a handy way for me to tell them apart.
Edited 26/11 to correct typos and clarify. Thanks Mr Daniels.
I.e. I have a 3 fold increase in speed than I was expecting, but what I did was not a totally fair comparison.
I'll have a play at the weekend and set them up identically on 1.02.20 then change the 7.31 to use 1.03.06, and see how they compare.
I hope that makes since. I’m a bit rushed this week.
BTW I do know that the loader makes no difference. It is just a handy way for me to tell them apart.
Edited 26/11 to correct typos and clarify. Thanks Mr Daniels.
ChrisDaniels
Well-Known Member
When you say rest, do you mean reset?
free30
Member
I've installed the new firmware again
This time I removed 'auto scheduled restore' before doing a factory reset.
I've now started repopulating the schedule myself.
If the EPG went at speed level '10' with the old firmware, and '4' with the new firmware without a reset, it is now going about '8'.
Its not perfect and if it gets worse over time I know I'll return to the old one, else I will just keep thinking something is wrong with the remote.
Anyhow thats my little report. Better have a play with the new portal to see if it worth it.
This time I removed 'auto scheduled restore' before doing a factory reset.
I've now started repopulating the schedule myself.
If the EPG went at speed level '10' with the old firmware, and '4' with the new firmware without a reset, it is now going about '8'.
Its not perfect and if it gets worse over time I know I'll return to the old one, else I will just keep thinking something is wrong with the remote.
Anyhow thats my little report. Better have a play with the new portal to see if it worth it.
kevindickinson
Active Member
This might add to the evidence
I'm on 1.03.06 and after a retune yesterday the auto restore failed (it restored some of the programme names but the channel was always MovieMix
Got into problems after that which I think was partially human error, partially a package bug but not relevant here.
Anyway end result was I could not restore my scheduled recordings so had to manually re enter them
My EPG has no noticeable lag - I remember a lag when I first installed 1.03.06 but could not be certain it was still there immediatly before above issue.
I'm on 1.03.06 and after a retune yesterday the auto restore failed (it restored some of the programme names but the channel was always MovieMix
Got into problems after that which I think was partially human error, partially a package bug but not relevant here.
Anyway end result was I could not restore my scheduled recordings so had to manually re enter them
My EPG has no noticeable lag - I remember a lag when I first installed 1.03.06 but could not be certain it was still there immediatly before above issue.
Luke
Well-Knwοn Мember
I've been timing the length of time it takes to right scroll BBC 1 from midnight Sun/Mon to midnight Tue/Wed on a non-RE HDR-FOX T2. A bit awkward as a RM-F04 times out after 30 seconds!
(1) No timers, and no reset ever having been actioned when using 1.03.06:
24 seconds for 1.01.09, 1.02.20 (HDR1 & HDR2), 1.02.29, 1.02.32
50 seconds 1.03.06
(2) 50 series link timers, and and no reset ever having been actioned when using 1.03.06:
25 seconds for 1.2.20 (timers were loaded from a backup from a different 1.02.20 HDR)
140 seconds for 1.03.06 (timers were loaded from a backup from a different 1.02.20 HDR)
(3) 10 series link timers, and and no reset ever having been actioned when using 1.03.06:
25 seconds for 1.2.20 (timers were loaded from a backup from a different 1.02.20 HDR)
67 seconds for 1.03.06 (timers were loaded from a backup from a different 1.02.20 HDR)
(4) No timers, and reset actioned when using 1.03.06:
48 seconds (near enough the 50 seconds from before the reset - perhaps I'm getting slicker with the stop watch)
(5) No timers, and reset actioned when using 1.03.06:
48 seconds for 1.03.06
(6) No timers, a reset actioned when using 1.03.06, and no aerial:
48 seconds for 1.03.06
(7) No timers, a reset actioned when using 1.03.06, reconnected aerial and started to playback a recording:
48 seconds for 1.03.06
(8) 50 new series link timers selected after a reset while on 1.03.06:
127 seconds for 1.03.06
(9) The same 50 timers but padding added to preferences:
127 seconds for 1.03.06
(10) The same 50 timers but each one edited and saved to remove the series linking, (also padding was still switched on):
107 seconds for 1.03.06
A couple of things surprised me. I was expecting (10) to be nearer the 50 seconds of (1) rather than the 127 seconds of (8).
Also the difference between the 1.03.06 for (2) and (8) was not what I was expecting. Although both are noticeably slower than 25 seconds I was expecting something a bit closer to each other than the 13 second difference.
(1) No timers, and no reset ever having been actioned when using 1.03.06:
24 seconds for 1.01.09, 1.02.20 (HDR1 & HDR2), 1.02.29, 1.02.32
50 seconds 1.03.06
(2) 50 series link timers, and and no reset ever having been actioned when using 1.03.06:
25 seconds for 1.2.20 (timers were loaded from a backup from a different 1.02.20 HDR)
140 seconds for 1.03.06 (timers were loaded from a backup from a different 1.02.20 HDR)
(3) 10 series link timers, and and no reset ever having been actioned when using 1.03.06:
25 seconds for 1.2.20 (timers were loaded from a backup from a different 1.02.20 HDR)
67 seconds for 1.03.06 (timers were loaded from a backup from a different 1.02.20 HDR)
(4) No timers, and reset actioned when using 1.03.06:
48 seconds (near enough the 50 seconds from before the reset - perhaps I'm getting slicker with the stop watch)
(5) No timers, and reset actioned when using 1.03.06:
48 seconds for 1.03.06
(6) No timers, a reset actioned when using 1.03.06, and no aerial:
48 seconds for 1.03.06
(7) No timers, a reset actioned when using 1.03.06, reconnected aerial and started to playback a recording:
48 seconds for 1.03.06
(8) 50 new series link timers selected after a reset while on 1.03.06:
127 seconds for 1.03.06
(9) The same 50 timers but padding added to preferences:
127 seconds for 1.03.06
(10) The same 50 timers but each one edited and saved to remove the series linking, (also padding was still switched on):
107 seconds for 1.03.06
A couple of things surprised me. I was expecting (10) to be nearer the 50 seconds of (1) rather than the 127 seconds of (8).
Also the difference between the 1.03.06 for (2) and (8) was not what I was expecting. Although both are noticeably slower than 25 seconds I was expecting something a bit closer to each other than the 13 second difference.
Can anyone help this guy with only partial webif working, not something I've had to fix myself:
http://forums.digitalspy.co.uk/showthread.php?p=70142234#post70142234
http://forums.digitalspy.co.uk/showthread.php?p=70142234#post70142234
michael.h
Member
The web-if fails to provide any programme information for HDR Fox-T2 v1.03.06 Loader a7.34 with CF v2.19 so that is not an usable option.
Since the arrival of the TVDiarythe GB/RE model reports "Not in EPG No information available" until the programme has been transmitted.
Thanks to all who have made the custom firmware available and particularly to Michael Eaton for keeping things going. I have today donated £10.
#1 HDR Fox-T2 v1.02.32 with CF v2.19 HDD upgrade problem 500GB HDD
#2 HDR Fox-T2 v1.02.32 with CF v2.19 - upgraded to 1TB Seagate Pipeline HDD
#3 HDR Fox-T2 v1.03.06 Loader a7.34 with CF v2.19 - 1TB as supplied.
#4 HDR Fox-T2 v1.02.32 Loader a7.33 with CF v2.19 - upgraded to 1TB Seagate Pipeline HDD
Would you care to explain exactly what you mean?
michael.h
Member
The EPG fails to populate with any programme info only the page headers!
The TV Diary reports "Not in EPG No information available" until the programme has been transmitted.
Since my previous post I have found the info on removing Portal Xtra1 and installing New Portal this has fixed the above EPG and TV Diary problems after a hard reboot rather than a Diags reboot.
My post No. 157 was a reply to The Asgard who implied that using the Humax guide was stupid when the web-if provided a much better option (see post 100).
#1 HDR Fox-T2 v1.02.32 with CF v2.19 HDD upgrade problem 500GB HDD
#2 HDR Fox-T2 v1.02.32 with CF v2.19 - upgraded to 1TB Seagate Pipeline HDD
#3 HDR Fox-T2 v1.03.06 Loader a7.34 with CF v2.19 - 1TB as supplied.
#4 HDR Fox-T2 v1.02.32 Loader a7.33 with CF v2.19 - upgraded to 1TB Seagate Pipeline HDD
Black Hole
May contain traces of nut
That fault has been experienced with other firmware selections, it is unlikely to be firmware specific. I'm sure there is a fix.