Magic TV 3600 random rebooting after upgrading to 3.18

Forums › Freeview (DVB-T/DVB-S) › Magic TV 3600 random rebooting after upgrading to 3.18

1 | ... | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | ... | 19

339 posts

Ultimate Geek
+1 received by user: 44

#1282337 13-Apr-2015 17:07

wklie:
JefWright: how about adding an undocumented, timed reboot feature that we can use to automatically refresh our 3600s? I really don't want to have to operate my 3600 from a plug-in timer if I can avoid it and I don't know enough to hack into it and schedule a daily shutdown.

Why not just use firmware 3.20?

Looks like we're going in circles here ...

3.20 Has the auto reboot problem, which means the 4-5 day stability issues are a secondary concern

3.21 "Fixes" the auto reboot problem, but introduces stability issues (sluggish responses after a 4-5 days) which means we need to restart the box anyway

Wklie - I think your loyal customers would appreciate a bit of progress in some real fixes to these issues. Would you be able to explain the changes made and difficulties encountered, give us an idea of what support you/Magic tv provide?

RingoTB

118 posts

Master Geek
+1 received by user: 3

#1282359 13-Apr-2015 17:29

wklie:
JefWright: how about adding an undocumented, timed reboot feature that we can use to automatically refresh our 3600s? I really don't want to have to operate my 3600 from a plug-in timer if I can avoid it and I don't know enough to hack into it and schedule a daily shutdown.

Why not just use firmware 3.20?

After both myself and my neighbour loaded firmware ver 3.20, we both had many random lock-ups. This seemed to occur when the unit would be either coming out of standby, or going back into standby. Upgrading to firmware 3.21 got rid of that major problem. In comparison, the response slow down and having to restart issue with ver 3.21 is very minor. After what both myself and my neighbour went through with firmware 3.20 I would recommend that no one use that version.

Also, any firmware version that has the auto reboot issue (firmware 3.18 - 3.20 I think???) is very unlikely to actually see the response slow down issue. The auto reboot will be resetting and effectively masking that fault if indeed it was in any of those earlier firmwares. Potentially, the response slow down issue could have been introduced from firmware 3.18 or onwards.

wklie

191 posts

Master Geek
+1 received by user: 5

Trusted

MagicTV

#1282513 13-Apr-2015 21:00

cb1: Would you be able to explain the changes made and difficulties encountered

As explained before, the primary difficulty is that with the various recorded broadcast ts streams I got from NZ I cannot reproduce the auto-reboot or memory leak issues using a ts signal generator.

Changes are as listed before -

Major differences among recently released MTV36000TD firmwares are:

6.08beta2 = 6.08 beta + fix for FF/RW
6.08beta = Some MTV3700TD features back ported to MTV3600TD + fix for wake-up reboot

3.21 = 3.20 + fix for wake-up reboot
3.20 = 3.19 beta7 + EIT Huffman Coding decompression (fix for recorded programme names garbage)
3.19 beta7 = 3.18 + booking fix for Nelson area

LUMIN Network Music Player, Magic TV New Zealand and Australia firmware lead

JefWright

85 posts

Master Geek
+1 received by user: 2

#1282586 14-Apr-2015 01:07

wklie:
JefWright: how about adding an undocumented, timed reboot feature that we can use to automatically refresh our 3600s? I really don't want to have to operate my 3600 from a plug-in timer if I can avoid it and I don't know enough to hack into it and schedule a daily shutdown.

Why not just use firmware 3.20?

3.20 didn't do much for me because 3.20 does a cold restart almost every time I turn the PVR on. I appreciate that this probably overcomes the memory leak (because the PVR is being rebooted once or twice a day) but it's awful to use.

cb1

339 posts

Ultimate Geek
+1 received by user: 44

#1282587 14-Apr-2015 01:15

wklie:
cb1: Would you be able to explain the changes made and difficulties encountered

As explained before, the primary difficulty is that with the various recorded broadcast ts streams I got from NZ I cannot reproduce the auto-reboot or memory leak issues using a ts signal generator.

Changes are as listed before -

Major differences among recently released MTV36000TD firmwares are:

6.08beta2 = 6.08 beta + fix for FF/RW
6.08beta = Some MTV3700TD features back ported to MTV3600TD + fix for wake-up reboot

3.21 = 3.20 + fix for wake-up reboot
3.20 = 3.19 beta7 + EIT Huffman Coding decompression (fix for recorded programme names garbage)
3.19 beta7 = 3.18 + booking fix for Nelson area

What I meant was a fuller explanation e.g. fix for wake-up reboot by doing x, y, z (in layman's terms, not exact program code). I'm guessing, but from the new HDD spinning issue, it seems that the it's been achieved by no longer going into full standby and hence avoiding the problem being encountered at start up.

I'm certainly not an expert in this field, but I have programming experience. If you can't reproduce the problem from the recordings, then maybe the crucial info isn't being recorded - I wouldn't think that all the data transmitted is stored in the ts file.

Would it be possible to create a diagnostic version of the firmware which gives some additional information about what caused the problem
e.g.
1) Show the 'Magic Tv is restarting' error message with some error code/useful information as to where the error message was called from/what caused the error routine to be invoked and waits until OK is pressed on the remote (so that someone can write it down or take a photo)
2) Optionally create a trace log of routines being called - not sure how the file would be copied/viewed

Gemini

429 posts

Ultimate Geek
+1 received by user: 23

#1284590 15-Apr-2015 11:06

wklie:
cb1: Would you be able to explain the changes made and difficulties encountered

As explained before, the primary difficulty is that with the various recorded broadcast ts streams I got from NZ I cannot reproduce the auto-reboot or memory leak issues using a ts signal generator.

Changes are as listed before -

Major differences among recently released MTV36000TD firmwares are:

6.08beta2 = 6.08 beta + fix for FF/RW
6.08beta = Some MTV3700TD features back ported to MTV3600TD + fix for wake-up reboot

3.21 = 3.20 + fix for wake-up reboot
3.20 = 3.19 beta7 + EIT Huffman Coding decompression (fix for recorded programme names garbage)
3.19 beta7 = 3.18 + booking fix for Nelson area

Hi Wklie
Seems like you wanted to fix the auto reboot but it hasn't worked
Does that give you some information that gets you closer to finding a fix for the auto-reboot?
Also why is 3.20 unstable I'd really like programme names?

Geekzone support

Support Geekzone with one-off or recurring donations Donate via PressPatron.

Gemini

429 posts

Ultimate Geek
+1 received by user: 23

#1284592 15-Apr-2015 11:16

RingoTB:
wklie:
JefWright: how about adding an undocumented, timed reboot feature that we can use to automatically refresh our 3600s? I really don't want to have to operate my 3600 from a plug-in timer if I can avoid it and I don't know enough to hack into it and schedule a daily shutdown.

Why not just use firmware 3.20?

After both myself and my neighbour loaded firmware ver 3.20, we both had many random lock-ups. This seemed to occur when the unit would be either coming out of standby, or going back into standby. Upgrading to firmware 3.21 got rid of that major problem. In comparison, the response slow down and having to restart issue with ver 3.21 is very minor. After what both myself and my neighbour went through with firmware 3.20 I would recommend that no one use that version.

Also, any firmware version that has the auto reboot issue (firmware 3.18 - 3.20 I think???) is very unlikely to actually see the response slow down issue. The auto reboot will be resetting and effectively masking that fault if indeed it was in any of those earlier firmwares. Potentially, the response slow down issue could have been introduced from firmware 3.18 or onwards.

FYI I have had the auto reboot issue since 3.13 which I reported here 2.5 years ago.
wklie said to upgrade to 3.18 but it seemed like a stock standard response so I did not
I'm waiting for a stable version that has EIT Huffman Coding decompression (fix for recorded programme names garbage) as 3.20 and 3.21 are not stable judging by the comments here

butlerboy

457 posts

Ultimate Geek
+1 received by user: 53

#1284608 15-Apr-2015 11:32

Gemini:
I'm waiting for a stable version that has EIT Huffman Coding decompression (fix for recorded programme names garbage) as 3.20 and 3.21 are not stable judging by the comments here

3.21 is pretty stable aside from it getting a bit slow after a week and a reboot once a week fixes that. I'd much rather have to reboot once a week than have it restart every time I turn it on. 3.21 is a step in the right direction.

Gemini

429 posts

Ultimate Geek
+1 received by user: 23

#1284630 15-Apr-2015 12:03

butlerboy:
Gemini:
I'm waiting for a stable version that has EIT Huffman Coding decompression (fix for recorded programme names garbage) as 3.20 and 3.21 are not stable judging by the comments here

3.21 is pretty stable aside from it getting a bit slow after a week and a reboot once a week fixes that. I'd much rather have to reboot once a week than have it restart every time I turn it on. 3.21 is a step in the right direction.

Thanks for the info
Imagine this scenario
You're out shopping for a Freeview PVR
A salesman says "You have two choices. One that auto-reboots just when you want to use it, or another that slows down and becomes unusable and requires a manual reset"
Every single person I know would walk away from that product. They would also feel its unfair if that started happening a year or two after purchase.
The CGA was put in place to protect us from this kind of thing yeah?

butlerboy

457 posts

Ultimate Geek
+1 received by user: 53

#1284683 15-Apr-2015 12:57

Gemini:
Thanks for the info
Imagine this scenario
You're out shopping for a Freeview PVR
A salesman says "You have two choices. One that auto-reboots just when you want to use it, or another that slows down and becomes unusable and requires a manual reset"
Every single person I know would walk away from that product. They would also feel its unfair if that started happening a year or two after purchase.
The CGA was put in place to protect us from this kind of thing yeah?

Don't get me wrong, I totally agree with everything you've said in this post. Just saying, that for me at least, the WAF is a lot higher running 3.21 assuming I remember to reboot it once a week. :)

Gemini

429 posts

Ultimate Geek
+1 received by user: 23

#1284819 15-Apr-2015 15:16

butlerboy:
Gemini:
Thanks for the info
Imagine this scenario
You're out shopping for a Freeview PVR
A salesman says "You have two choices. One that auto-reboots just when you want to use it, or another that slows down and becomes unusable and requires a manual reset"
Every single person I know would walk away from that product. They would also feel its unfair if that started happening a year or two after purchase.
The CGA was put in place to protect us from this kind of thing yeah?

Don't get me wrong, I totally agree with everything you've said in this post. Just saying, that for me at least, the WAF is a lot higher running 3.21 assuming I remember to reboot it once a week. :)

My wife thinks it's a POS and went out and bought a Panasonic for her recording ;)

Dell

Shop now for Dell laptops and other devices (affiliate link).

butlerboy

457 posts

Ultimate Geek
+1 received by user: 53

#1284872 15-Apr-2015 16:18

Gemini:
butlerboy:
Gemini:
Thanks for the info
Imagine this scenario
You're out shopping for a Freeview PVR
A salesman says "You have two choices. One that auto-reboots just when you want to use it, or another that slows down and becomes unusable and requires a manual reset"
Every single person I know would walk away from that product. They would also feel its unfair if that started happening a year or two after purchase.
The CGA was put in place to protect us from this kind of thing yeah?

Don't get me wrong, I totally agree with everything you've said in this post. Just saying, that for me at least, the WAF is a lot higher running 3.21 assuming I remember to reboot it once a week. :)

My wife thinks it's a POS and went out and bought a Panasonic for her recording ;)

Maybe I should get your wife to give my wife a call!!!! :D

theoldfarter

235 posts

Master Geek
+1 received by user: 21

ID Verified

#1285064 15-Apr-2015 19:57

butlerboy:
Gemini:
I'm waiting for a stable version that has EIT Huffman Coding decompression (fix for recorded programme names garbage) as 3.20 and 3.21 are not stable judging by the comments here

3.21 is pretty stable aside from it getting a bit slow after a week and a reboot once a week fixes that. I'd much rather have to reboot once a week than have it restart every time I turn it on. 3.21 is a step in the right direction.

Using v3.21, do you have any instances where the HDD is still spinning even though the unit appears to be off on the front panel? You need to put your ear to the unit to know if that is happening. The unit would shut down & the HDD spun down but then spun up again & stayed spinning. Other times, after turning off after a scheduled recording, I would notice the HDD spinning hours later, even with the display showing the unit off.

butlerboy

457 posts

Ultimate Geek
+1 received by user: 53

#1285102 15-Apr-2015 20:22

theoldfarter:
butlerboy:
Gemini:
I'm waiting for a stable version that has EIT Huffman Coding decompression (fix for recorded programme names garbage) as 3.20 and 3.21 are not stable judging by the comments here

3.21 is pretty stable aside from it getting a bit slow after a week and a reboot once a week fixes that. I'd much rather have to reboot once a week than have it restart every time I turn it on. 3.21 is a step in the right direction.

Using v3.21, do you have any instances where the HDD is still spinning even though the unit appears to be off on the front panel? You need to put your ear to the unit to know if that is happening. The unit would shut down & the HDD spun down but then spun up again & stayed spinning. Other times, after turning off after a scheduled recording, I would notice the HDD spinning hours later, even with the display showing the unit off.

Yip. I read somewhere on here that the hdd remaining spinning is a side effect of the fix for the restart from standby problem.

JefWright

85 posts

Master Geek
+1 received by user: 2

#1285239 15-Apr-2015 23:55

Running 3.21 here and after it auto-stands-by it is silent (no HDD running at all). When I press start and it comes to life quite quickly (depending on how long since its last reboot) and you can here the HDD spin up a second or two after it powers up.

1 | ... | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | ... | 19