Different remote button actions

[Lothar2]

No that crash is again base 16.

i attach a log from this evening. I think crash came this time in Movielist or channellist after end of play a video.mp4.

[Trial]

Hi Lothar2,
you have a very funny box. Are you sure that it is an original Duo2? The routines that make problems on your machine are >1 year old and beside me there are some other Duo2 user which use OpenViX. Same reason different file. Try attached converter.

ciao

[Lothar2]

Even my old Duo was a funny box. But with VIX 3.0.7xx it then ran perfectly. I use determined only slightly different settings than other users. see "gradient" in LCD4Linux.
I think it is a original Box, because problems in other Image-plugin combinations generate the same problems as other users have. Only VIX is different than in others.
I always seem to good boxes for find error.

THX for fixed ServiceInfo.py. However, it may take some time with feedback, since the error occurs rarely and can not be reproduced.

[Trial]

Hi,
in this area ViX is a bit different. Because gstreamer sometimes delivered wrong or missing video information especially with downloaded or streamed videos ViX uses the information the hardware delivers in /proc/stb/vmpeg which is reliable and important for instance when using auto resolution.

You can take a look for yourself in VideoMode.py.
OpenViX uses:

if path.exists("/proc/stb/vmpeg/0/xres"):
	f = open("/proc/stb/vmpeg/0/xres", "r")
	try:
		video_width = int(f.read(),16)
	except:
	        pass
	f.close()

The try/except is because of you:-)

Most other images are using

video_width = int(info.getInfo(iServiceInformation.sVideoWidth))

and rely completely on gstreamer.

ciao

[Lothar2]

thx for information about the issue. if the information from hardware in /proc/stb/vmpeg is reliable, why it crash only from time to time and can not be reproduced with same file? Is there a too short timeout set somewhere and my Box or fingers too fast?

[Trial]

Hi,
it should be a driver/hardware problem. With reliable I mean the information you get. As I said with only gstreamer sometimes frequency or other information was wrong and this means that AutoResolution or Multi for frequency could not work reliable.

ciao

[Lothar2]

it should be a driver/hardware problem.

Can Ubi-Error have something to do with that my box behaves differently?

[Trial]

Hi,
what ubi-error? ubi is the file system of the flash and can be cause of funny behavior.

ciao

[Lothar2]

But, if "UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16" mean "define EBUSY 16 /* Device or resource busy */" then i must have no flash, or?

is this ok so?:

root@vuduo2:~# df -h                                                  
Filesystem                Size      Used Available Use% Mounted on    
ubi0:rootfs             862.3M    143.6M    718.7M  17% /             
devtmpfs                687.4M      8.0K    687.4M   0% /dev          
tmpfs                    64.0K         0     64.0K   0% /media        
/dev/sda1               931.1G    605.5G    325.6G  65% /media/hdd    
/dev/sdb1                 7.2G    292.5M      6.9G   4% /media/usb    
tmpfs                   687.5M    320.0K    687.2M   0% /var/volatile

root@vuduo2:~# free -m                                                     
             total       used       free     shared    buffers     cached  
Mem:          1375        229       1145          0          8         76  
-/+ buffers/cache:        143       1231                                   
Swap:            0          0          0

Next i have time i will see in dmesg in VTI if there is the same massage.

[Trial]

Hi,
I think this means that it is mounted and no thing to worry about.

ciao

[Lothar2]

Hi Lothar2,
you have a very funny box. Are you sure that it is an original Duo2? The routines that make problems on your machine are >1 year old and beside me there are some other Duo2 user which use OpenViX. Same reason different file. Try attached converter.

ciao

Hello Trial,

after Update to 095 the invalid literal for int() with base 16: '' is back. Have the Update change ServiceInfo.pyo back to unfixed dafault? Is fixed in 097?
At this Time the crash occurs my wife only would select a other Channel from Channellist.

[Lothar2]

and after update to build 097 the same failure come back. this time i have play a file from RTLnow.