Forums

Good Day,

 

 

 

Everytime i set or change a timer on Openpli the Waiting balls (Top left ) come and the action is finisch after 12 Sec.

I think it was faster in past releases.

 

Could it be so slow because enigma uses only one core for this?

 

with regards

 

HArdware: et9200 (97-2)

OPenpli: 4

Kernel: 3.8.7

Enigma: 2014-04-16

 

 

 

CPU0:   4% usr   9% sys   4% nic  73% idle   0% io   0% irq   8% sirq
CPU1:  93% usr   1% sys   0% nic   4% idle   0% io   0% irq   0% sirq
Load average: 0.50 0.42 0.27 2/75 4664
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
  402   397 root     R     107m  38%  55% /usr/bin/enigma2
  100     2 root     SW       0   0%   2% [sched_high]
 4198  4193 root     R     3204   1%   0% top
 4176   354 root     S     2972   1%

I virtually never see the spinner, so it is absolutely not normal.

 

Does you box have a local disk that is in sleep mode when you open the timer, so you have to wait for a spin-up of the disk?

Hello,

 

I use a CIFS Mount as hdd replacement.

i Don'T have a hdd in my et9200.

the timers.xml in /etc/enigma2/

 

 

Further i try a debug mode and set a timer:

 

init 4

enigma2

..

..

..

 

action ->  SetupActions ok
finished add
main thread is non-idle! display spinner!
[Timer] Record RecordTimerEntry(name=Tarzan, begin=Fri Apr 18 13:37:00 2014, serviceref=1:0:19:EF10:421:1:C00000:0:0:0:, justplay=False)
ERROR reading PES (fd=53) - Value too large for defined data type
poll: unhandled POLLERR/HUP/NVAL for fd 53(8)
..

..

action ->  EPGSelectActions timerAdd
[TIMER] record time changed, start prepare is now: Fri Apr 18 15:06:40 2014
warning, skin is missing element ok in <class 'Screens.TimerEntry.TimerEntry'>
warning, skin is missing element cancel in <class 'Screens.TimerEntry.TimerEntry'>
TuxTxt <Biterror in Packet>
action ->  SetupActions save
finished add
main thread is non-idle! display spinner!
[Timer] Record RecordTimerEntry(name=Mulan, begin=Fri Apr 18 15:07:00 2014, serviceref=1:0:19:EF10:421:1:C00000:0:0:0:, justplay=False)
ERROR reading PES (fd=53) - Value too large for defined data type
poll: unhandled POLLERR/HUP/NVAL for fd 53(8)
 

Edited by Chibby, 18 April 2014 - 09:46.

Which skin are you using? Perhaps that starts some kind of plugin or code that has this side-effect?

 

You are talking about a normal standard timer, not about an autotimer?

Hello,

 

1) i Go to Programm Guide (Single sender)

2) i Go down to the entry, which i want to record

3) i push the green button (Timer)

     -> I Think its the normal Timer.

4) I commit the Timer with the green button.

 

Skin: Pli-HD

 

Great thanks for help.

I Installed the Following Plugins:

-> oscam

-> EPGimport

 

--> All default Plugins which are installed in the IMAGE

I attached the file /etc/installed file:

I used the German Skin;)

Writing of the timers can be done in about 1/100'th of a second. If it takes longer, something is wrong, but it's hard to trace.

It is a timer which will record in the future right?
If the new timer starts a recording immediately, it usually takes some time to spin up the harddisc and really start the recording.

Hello,

 

Yes it's a Timer which starts 3 Hours later