- This topic has 101 replies, 25 voices, and was last updated 9 years, 2 months ago by
.
-
Posts
-
Unfortunately I will have to agree that this update is causing problems.
After manually downloading the update from Humax, I was completely unable to get the machine to recognise the update from the usb stick until I did the power off/▼channel/power on. (Usually just a power on/off and/or update search will find an update on the usb).
After the update I attempted a manual retune of the correct mux`s for my area and this was troublesome to say the least. Each separate channel required several runs before it tuned anything and each time I needed to swap between dvb-t and dvb-t2 a few times until it settled. Once tuned it appeared that the machine was ok but I have since had several reboots and I have noticed the previous channel (via return button) works very intermittently.
More work required please Humax.
I turned the remote record on to have a play with how it worked, which is when I started to have numerous random reboots of the FVP-4000T. Turned remote record off and I’ve not had a reboot or any other problems for 4 days now.
Remote record has been enabled on one of my FVP’s since we started testing this application and no reboots to date.
Has anybody at Humax Towers got any suggestions as to what is causing these random reboots. As they are random only they can help or fix them. As it will take a debugger to find the problem. This firmware seems to lack the functionality of previous Humax PVR boxes and is now completely unreliable. This is really becoming embarrassing to what was a good reputation. What have they done internally to mess things up this badly.
OK managed to get a few hours to check out this update
Current software is v1.01.31 loader is 1.05, updated on 5th August over WiFi, the update was so painless I didn’t even realise it had happened.
So I worked through a few checks
Did a quick 15 minute recording in SD for test purposes
Transfer to USB
Seems to work as before, transfer takes about the same time as playback, files are decrypted on transfer, transferred files are in a “.recordings” folder & has HJM,HJTSM & NTS in addition to the TS file
Tried a different format for the USB, exFAT formatted drives aren’t recognised, FAT32 still is though
Samba server
The new recording appears as a directory or folder with a TS extension, the HJM,HJTSM & NTS files are also present
Attempting to copy the TS folder over the network is denied, the error says
Quote:You need permission to perform this actionYou need permission from Unix User\0 to make changes to this folder
So Samba is borked for any new recordings, old pre update recordings still appear as files and transfer OK but these are still encrypted and of limited use
FTP server
Looks like a similar problem to Samba the TS file appears to be a directory, attempting to access it gets an error
Quote:550 /Recordings/”program name”.ts/: No such file or directorydrag & drop to a file explorer and you get a link to the original, open the link and you get the 550 error
So FTP is also borked
Media server transfer
Windows 7 still can’t handle the media server, so as I still had the win10 tablet (I really must give it back one day) I fired that up
Started the file explorer went to “This PC” & “FVP-4000T Media Server DMS” was present in “Network Locations”
Opened the “4000” & found 2 folders called “Channel” & “My Contents”
“Channel” has a list of all available channels, double clicking one opened media player but I couldn’t get any to play
“My Contents” has an “Internal HDD” folder & a “Recordings” folder
“Internal HDD” seems to provide access to files you’ve uploaded to the 4000 but as I didn’t have any I couldn’t say for certain.
“Recordings” is all your recordings and they can be dragged/dropped, copy/pasted to another drive, no apparent distinction between pre & post update recordings so the test recording transferred ok & was unencrypted as did recordings made prior to the upgrade.
As other users have reported I also cannot get the media server on/off timer to work while the 4000 is in standby mode
Not noticed any crashes or hangs since the update
I’ll be reporting this to Humax, hope it’s of use to someone
Esme
I am not trying to run down Humax for some bizarre reason.
Firstly I have been a Firmware Engineer for over twenty seven years. I worked with Humax engineers some years ago in Paris when the chip set was based on conexent ARM SOC processors. They were/are amazing engineers.
However, something bad has happened here. I HAVE HAD REBOOTS THAT ARE RANDOM.
I don’t care why they are happening in this latest build they just are, full stop. However, being a engineer I have either reduced or stopped them happening by going into System Settings and giving everything in sight an initial value. This might suggest that the default values in the code are not as should be.
Again as this is a random problem only some sort of help from Humax could confirm or deny this as a partial solution.
Again the lack of a creat folder and move and copy just leaves my HDD organisation a total mess. I recover a program after a rest and I can do nothing to tidy things up. I have said this until I am blue in the face and now again it is causing problems. What more can I say, add the ability to manage stuff on the HDD and I make things like this less painful. Who or what is Humax stopping the obvious.
4th random reboot last night since the recent update. No problems what so ever prior to that in 8 months!
Davygogs – 2 hours ago »
4th random reboot last night since the recent update. No problems what so ever prior to that in 8 months!
I’ve had three reboots since the update,the last one being Saturday. Like you the box was trouble free for months. I just hope Humax are aware of this problem,and will correct it asap.
Sorry to say this but I,m glad now I took mine back last week and got a refund from John Lewis.
Clearly this upgrade has done no good whatsoever, in fact it seems to have made things worse.
Elmojo – 8 hours ago »
Esme
I am not trying to run down Humax for some bizarre reason.
Firstly I have been a Firmware Engineer for over twenty seven years. I worked with Humax engineers some years ago in Paris when the chip set was based on conexent ARM SOC processors. They were/are amazing engineers.
However, something bad has happened here. I HAVE HAD REBOOTS THAT ARE RANDOM.
I don’t care why they are happening in this latest build they just are, full stop. However, being a engineer I have either reduced or stopped them happening by going into System Settings and giving everything in sight an initial value. This might suggest that the default values in the code are not as should be.
Again as this is a random problem only some sort of help from Humax could confirm or deny this as a partial solution.
Again the lack of a creat folder and move and copy just leaves my HDD organisation a total mess. I recover a program after a rest and I can do nothing to tidy things up. I have said this until I am blue in the face and now again it is causing problems. What more can I say, add the ability to manage stuff on the HDD and I make things like this less painful. Who or what is Humax stopping the obvious.
Oh I agree, this software wasn’t tested adequately & shouldn’t have been rolled out in this state.
Just for clarification I have no connection with Humax, I just mail them with any problems as they don’t always read these threads unless they’re pointed out
What’s going on with this rebooting issue?
I have my FVP4000 for almost a year now and it has never once spontaneously rebooted itself. During the last few days since the update it has done it three times for no apparent reason whilst we’re watching a recorded programme.
I hope Humax fix this before too long.
Richard
I’ve had the same thing yesterday morning around 8. I was watching a recorded program (channel 4HD), nothing else was being recorded, the internet was not connected. The picture froze and the sound carried on for a while, then it rebooted. On restart it had not remembered where I was in the recording.
It might be helpful (for Humax technicians) to know if these reboots are happening in a particular way. Does it only happen if one is watching hd and not sd? For example.
First reboot for ten days just happened whilst on YouTube. Getting really sick of this happening. When are Humax going to wake up to the problems caused by the last software update?
Just want to add my voice to the spontaneous random reboot discussion. This has also recently started happening on my FVP-4000T and it is really annoying, especially if watching a recorded programme while another is recording as the recording is then abandoned. Even if manually restarted, there’s probably 3 or 4 minutes lost while the box gets it self together and is working again. Not sure if it happens in unattended timer recordings but there have been a couple of instances recently when a timer recording has stopped before the end of the programme.
I’m not aware of it happening on any particular channel.
It has only started happening since the update but probably happens once or twice a week now. Had considered returning machine under warranty but there are about 100hrs of programmes on it we have yet to watch.
As a programmer, these kind of random events are often traced to an uninitialised variable somewhere in the code that had been missed during checking – could this be the case here?
I too had my first re-boot yesterday whilst watching a youtube video around lunch time, maybe it’s youtube app related.
- You must be logged in to reply to this topic.