Tuxbox-Forum

Diesen Fehler kann ich mit einem Test-Snap von heute 19.12.2008, 17:16 Uhr auch nicht feststellen. Das war schon gefixt.

Greetz von DrStoned

Danke. Getestet, läuft

Oh ja. Der war peinlich:

Geht jetzt wieder.

Uch habe mal ein Testprogramm gemacht für alle, die Probleme mit der FB haben.
rc_test.tar.gz
Da ist ein Source-File drin (das braucht ihr nicht) und ein binary "rc_test". Das auf die box nach /tmp, "chmod 0755 /tmp/rc_test", dann "/tmp/rc_test" im telnet aufrufen.
Dann eine Taste der Fernbedienung ein paar Sekunden drücken.
Dabei kommt dann sowas raus (Beispiel DBOX-Taste):
Das bitte hier posten.

Modell 2 Original


Modell 2 Nachbau aus der Bucht

Keine Probs bis dato.

Hier von mir:



Nokia D-BOX2 - Kernel 2.4.36.6-dbox2 (17:44:26).
dbox login: root


BusyBox v1.7.2 (2008-12-17 20:25:43 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # /tmp/rc_test
dbox-II remote control timing test tool
Testing ... (interrupt to exit)
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 199, diff 199, type 1, code 5, value 02
Event: time (ms) 396, diff 197, type 1, code 5, value 02
Event: time (ms) 594, diff 198, type 1, code 5, value 02
Event: time (ms) 792, diff 198, type 1, code 5, value 02
Event: time (ms) 990, diff 198, type 1, code 5, value 02
Event: time (ms) 1188, diff 198, type 1, code 5, value 02
Event: time (ms) 1385, diff 197, type 1, code 5, value 02
Event: time (ms) 1628, diff 243, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 247, diff 247, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 240, diff 240, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 198, diff 198, type 1, code 5, value 02
Event: time (ms) 396, diff 198, type 1, code 5, value 02
Event: time (ms) 594, diff 198, type 1, code 5, value 02
Event: time (ms) 791, diff 197, type 1, code 5, value 02
Event: time (ms) 1033, diff 242, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 198, diff 198, type 1, code 5, value 02
Event: time (ms) 396, diff 198, type 1, code 5, value 02
Event: time (ms) 645, diff 249, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 242, diff 242, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 245, diff 245, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 197, diff 197, type 1, code 5, value 02
Event: time (ms) 438, diff 241, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 240, diff 240, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 198, diff 198, type 1, code 5, value 02
Event: time (ms) 430, diff 232, type 1, code 5, value 02
Event: time (ms) 677, diff 247, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 244, diff 244, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 198, diff 198, type 1, code 5, value 02
Event: time (ms) 447, diff 249, type 1, code 5, value 00
---
Event: time (ms) 0, diff 0, type 1, code 5, value 01
Event: time (ms) 243, diff 243, type 1, code 5, value 00
---

Anfangsverzögerung 300, Wiederholungsverzögerung 180

Mal geht's, mal nicht...

Das sind die Defaultwerte von Neutrino, wenn neutrino.conf nicht existiert.
Diese Werte sollten geändert werden, weil die Dbox damit kaum bedienbar ist.

Ich habe mit diesen Werte erste, gute Erfahrungen gemacht:

auf einer Sagem 2x-Dbox2 mit dieser Fernbedienung. Andere Vorschläge?

Hier die Ergebnisse (Kernel 2.4 + Neutrino-Patches) von rc_test mit gedrückter Dbox-Taste mit repeat 25/5:

2. Test mit diesen beiden Patchen
und

Dauerdrücken erzeugt diese Ausgabe: Vielleicht hilft es Dir für den 2.4er

Zuerst mal: lasst bitte die kernel-autorepeat-Patches für diesen Test erst mal aussen vor. Solange wir nicht wissen, woran's hängt, sollte man da immer nur an einem Ding drehen.

Bis hier sieht's gut aus...
hier nicht mehr. Die Fernbedienung schickt einzelne Kommandos mit Unterbrechung, keine zusammenhängende Taste "4". Ist evtl. deine Batterie in der Fernbedienung schwach?
Das ist meinem Testprogramm egal, zumindest solange du nicht den kernel-repeat-patch benutzt (mach das erstmal nicht).



Da ist mit kernel 2.4 definitiv was faul, der erste "diff" nach dem drücken müsste ca. 300, die folgenden dann ca. 150ms sein. => Diese Patches für 2.4 bitte nicht verwenden.


Ja, das ist klar. Im Original machen die Fernbedienungen anscheinend nie schneller als 200/200, deswegen fällt es nicht auf. Mit dem originaltreiber kannst du einstellen was du willst, die Fernbedienung schickt nicht mehr als 5 Impulse pro Sekunde. Meine Fernbedienung scheint da anders zu sein, die schickt alle 120ms einen Impuls (oder der FP der Philips ist anders).
Tatsächlich sieht das eher nach 250/50 aus (schau dir mal die "diff"-Werte an...) Anscheinend verwendet der 2.4er Kernel eine Andere Zeitbasis für die Werte wie 2.6. Oder hast du neutrino gar nie gestartet? 250/50 ist nämlich glaube ich auch der default im Kernel input-core.

Lasst den Kernel-Patch, zumindest auf 2.4 mal aussen vor, ich teste momentan auch auf 2.6 ohne diesen Patch, damit nicht zu viele verschiedene Kombinationen zu testen sind. Der ist später eine Mikrooptimierung (und erleichtert das Portieren auf andere Maschinen u.U.), er macht erst mal das Bild nicht bunter

50ms repeat würdest du ohne kernel-repeat übrigens nie bekommen, weil pro FB-impuls nur ein input-Event kommt - probier's mal ohne den Patch dann wirst du das sehen.

Das Ganze hat ein paar Implikationen für die Einstellungen:

- Wenn kernel-autorepeat verwendet werden soll, muss die initiale Verzögerung länger sein, als die Zeit zwischen 2 FB-Impulsen, also länger als ~210 ms (mal schauen, was sonst noch an Fernbedienungen auftaucht. Eine alte Nokia wäre noch interessant). Wenn die initiale Verzögerung kürzer ist als der Abstand der Impulse, dann wiederholt die Taste immer mindestens 1x, schliesslich kann erst dann, wenn der nächste Impuls kommt festgestellt werden, ob die Taste wieder losgelassen wurde. Zumindest habe ich den Treiber-Code so verstanden.
- Die Wiederholverzögerung muss dann auch auf realistische Werte eingestellt werden, "0" bedeutet dann wirklich "Saumässig unbenutzbar schnell", in der Praxis sollte das vermutlich auch in der Grössenordnung der Impulswiederholrate sein. Nun wird mir auch klar, warum mir meine "333/150" so praxisgerecht vorkamen: meine FB wiederhlt mit 120ms.

Alle Klarheiten beseitigt?

Kernel-Patch verwende ich nicht und die Batterien sind i.o., hab gerade nochmal gewechselt.

Test folgt gleich......

Batterien neu:

Event: time (ms) 0, diff 0, type 1, code 398, value 01
Event: time (ms) 241, diff 241, type 1, code 398, value 00
---
Event: time (ms) 0, diff 0, type 1, code 398, value 01
Event: time (ms) 199, diff 199, type 1, code 398, value 02
Event: time (ms) 398, diff 199, type 1, code 398, value 02
Event: time (ms) 597, diff 199, type 1, code 398, value 02
Event: time (ms) 796, diff 199, type 1, code 398, value 02
Event: time (ms) 995, diff 199, type 1, code 398, value 02
Event: time (ms) 1193, diff 198, type 1, code 398, value 02
Event: time (ms) 1392, diff 199, type 1, code 398, value 02
Event: time (ms) 1591, diff 199, type 1, code 398, value 02
Event: time (ms) 1790, diff 199, type 1, code 398, value 02
Event: time (ms) 1989, diff 199, type 1, code 398, value 02
Event: time (ms) 2188, diff 199, type 1, code 398, value 02
Event: time (ms) 2387, diff 199, type 1, code 398, value 02
Event: time (ms) 2586, diff 199, type 1, code 398, value 02
Event: time (ms) 2785, diff 199, type 1, code 398, value 02
Event: time (ms) 2984, diff 199, type 1, code 398, value 02
Event: time (ms) 3182, diff 198, type 1, code 398, value 02
Event: time (ms) 3423, diff 241, type 1, code 398, value 00
---
Event: time (ms) 0, diff 0, type 1, code 398, value 01
Event: time (ms) 242, diff 242, type 1, code 398, value 00
---
Event: time (ms) 0, diff 0, type 1, code 398, value 01
Event: time (ms) 199, diff 199, type 1, code 398, value 02
Event: time (ms) 398, diff 199, type 1, code 398, value 02
Event: time (ms) 597, diff 199, type 1, code 398, value 02
Event: time (ms) 844, diff 247, type 1, code 398, value 00
---
Event: time (ms) 0, diff 0, type 1, code 398, value 01
Event: time (ms) 249, diff 249, type 1, code 398, value 00
---
Event: time (ms) 0, diff 0, type 1, code 102, value 01
Event: time (ms) 246, diff 246, type 1, code 102, value 00
---

Ältere Fernbedienungen haben oft Kontaktprobleme zwischen Platine und Gummimatte.
Meist tritt aus dem Gummi(Silikon) so eine leicht zähe Flüssigkeit aus. Diese wird sozusagen
von dem Material mit der Zeit ausgeschwitzt. Eine Reinigung mit Spritus oder ähnlichem wirkt oft
Wunder. Für die Gummimatte habe ich sogar schon mal warmes Wasser und Seife (aus dem
Seifespender) benutzt. Danach Trockenföhnen und sauber zusammensetzen.

Ich habe es in einem yadd-neutrino getestet, Neutrino war gestartet.

Die Fernbedienung ist schon mehrfach gereinigt, mit einer zweiten geht's auch nicht anders.

Vor dem Patch funktionierte ja auch noch alles wie es sollte.

Abgesehen davon blinkt die LED an der Box auch ständig, wenn ich eine Taste der FB dauerhaft drücke.
Ob das nun ein Indiz für eine korrekte Funktion ist-keine Ahnung.

Ich geb's erst mal auf, vielleicht kann ich ja im Verlauf dieses Threads noch was nützliches beitragen.


gruß boardgeist

Nicht aufgeben! Du musst mir beim debuggen helfen, schliesslich tritt das Problem bei mir nicht auf.
Evtl. waren ja solche Boxen der Grund, warum das so "seltsam" implementiert war.

Ich habe das rc_test auf tuxbox-upload leicht erweitert, probiere es bitte mit der neueren Version nochmals aus, eine Taste für ein paar Sekunden sollte reichen. (Ich gebe nun noch die absolute Zeit aus, also nicht nur relativ zum tasten-"down"-Event, damit ich sehe, in Welchem Zeitrahmen die Events bei dir kommen).

@Boardgeist

Wenn es Deine Zeit erlaubt, so benutze das Testtool auch mal mit einem Image
bei dem Du keine Probs hast. Mal zum Vergleichen.

Ja. Ein altes Image vor meinen RCinput patches. Da _sollte_ sich zwar gar nichts ändern, aber... man weiss ja nie.

Geht los, aber erst mal Mittag essen!

Edit: Sorry, aber auf dem Tuxbox-Upload finde ich kein rc_test, wenn ich den Link der vorigen Seite nehme?!

Nochmal edit: hab's, blind gewesen und F5 gedrückt....


So bitte, neuer Test, aktuelles CVS:




Nokia D-BOX2 - Kernel 2.4.36.6-dbox2 (12:43:18).
dbox login: root


BusyBox v1.7.2 (2008-12-17 20:25:43 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # /tmp/rc_test
dbox-II remote control timing test tool
Testing ... (interrupt to exit)
Event: time: 17.578, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 17.820, rel: 242, diff: 242, type 1 code 398 val 0
---
Event: time: 17.876, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 18.084, rel: 209, diff: 209, type 1 code 398 val 2
Event: time: 18.330, rel: 454, diff: 245, type 1 code 398 val 0
---
Event: time: 18.373, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 18.620, rel: 247, diff: 247, type 1 code 398 val 0
---
Event: time: 18.671, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 18.920, rel: 248, diff: 248, type 1 code 398 val 0
---
Event: time: 19.069, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 19.310, rel: 241, diff: 241, type 1 code 398 val 0
---
Event: time: 19.367, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 19.566, rel: 199, diff: 199, type 1 code 398 val 2
Event: time: 19.810, rel: 442, diff: 243, type 1 code 398 val 0
---
Event: time: 19.864, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 20.110, rel: 245, diff: 245, type 1 code 398 val 0
---
Event: time: 20.163, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 20.410, rel: 247, diff: 247, type 1 code 398 val 0
---
Event: time: 20.461, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 20.660, rel: 199, diff: 199, type 1 code 398 val 2
Event: time: 20.859, rel: 398, diff: 199, type 1 code 398 val 2
Event: time: 21.100, rel: 639, diff: 241, type 1 code 398 val 0
---
Event: time: 21.157, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 21.356, rel: 199, diff: 199, type 1 code 398 val 2
Event: time: 21.554, rel: 398, diff: 199, type 1 code 398 val 2
Event: time: 21.753, rel: 597, diff: 199, type 1 code 398 val 2
Event: time: 21.952, rel: 796, diff: 199, type 1 code 398 val 2
Event: time: 22.151, rel: 995, diff: 199, type 1 code 398 val 2
Event: time: 22.350, rel: 1194, diff: 199, type 1 code 398 val 2
Event: time: 22.600, rel: 1443, diff: 249, type 1 code 398 val 0
---
Event: time: 22.648, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 22.890, rel: 241, diff: 241, type 1 code 398 val 0
---
Event: time: 22.946, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 23.145, rel: 199, diff: 199, type 1 code 398 val 2
Event: time: 23.390, rel: 443, diff: 244, type 1 code 398 val 0
---
Event: time: 23.444, rel: 0, diff: 0, type 1 code 398 val 1
Event: time: 23.690, rel: 246, diff: 246, type 1 code 398 val 0
---

~ #

Ich hatte es aus versehen im falschen verzeichnis hochgeladen, sollte jetzt gehen.

So, Test mit Image vom 1.12.08:


Nokia D-BOX2 - Kernel 2.4.36.6-dbox2 (13:22:11).
dbox login: root


BusyBox v1.7.2 (2008-12-01 10:28:15 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # /tmp/rc_test
dbox-II remote control timing test tool
Testing ... (interrupt to exit)
Event: time: 52.004, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 52.250, rel: 245, diff: 245, type 1 code 113 val 0
---
Event: time: 52.303, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 52.503, rel: 200, diff: 200, type 1 code 113 val 2
Event: time: 52.702, rel: 400, diff: 200, type 1 code 113 val 2
Event: time: 52.901, rel: 599, diff: 199, type 1 code 113 val 2
Event: time: 53.101, rel: 798, diff: 199, type 1 code 113 val 2
Event: time: 53.301, rel: 998, diff: 200, type 1 code 113 val 2
Event: time: 53.500, rel: 1198, diff: 200, type 1 code 113 val 2
Event: time: 53.702, rel: 1399, diff: 201, type 1 code 113 val 2
Event: time: 53.899, rel: 1597, diff: 198, type 1 code 113 val 2
Event: time: 54.098, rel: 1796, diff: 199, type 1 code 113 val 2
Event: time: 54.298, rel: 1996, diff: 200, type 1 code 113 val 2
Event: time: 54.540, rel: 2237, diff: 241, type 1 code 113 val 0
---
Event: time: 54.697, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 54.900, rel: 203, diff: 203, type 1 code 113 val 2
Event: time: 55.096, rel: 399, diff: 196, type 1 code 113 val 2
Event: time: 55.296, rel: 599, diff: 200, type 1 code 113 val 2
Event: time: 55.540, rel: 842, diff: 243, type 1 code 113 val 0
---
Event: time: 55.596, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 55.840, rel: 244, diff: 244, type 1 code 113 val 0
---
Event: time: 55.895, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 56.096, rel: 201, diff: 201, type 1 code 113 val 2
Event: time: 56.340, rel: 445, diff: 244, type 1 code 113 val 0
---
Event: time: 56.493, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 56.740, rel: 247, diff: 247, type 1 code 113 val 0
---
Event: time: 56.795, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 56.992, rel: 197, diff: 197, type 1 code 113 val 2
Event: time: 57.195, rel: 401, diff: 204, type 1 code 113 val 2
Event: time: 57.440, rel: 645, diff: 244, type 1 code 113 val 0
---
Event: time: 58.089, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 58.290, rel: 201, diff: 201, type 1 code 113 val 2
Event: time: 58.489, rel: 400, diff: 199, type 1 code 113 val 2
Event: time: 58.688, rel: 600, diff: 200, type 1 code 113 val 2
Event: time: 58.888, rel: 799, diff: 199, type 1 code 113 val 2
Event: time: 59.130, rel: 1041, diff: 242, type 1 code 113 val 0
---
Event: time: 59.186, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 59.430, rel: 243, diff: 243, type 1 code 113 val 0
---
Event: time: 59.486, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 59.730, rel: 244, diff: 244, type 1 code 113 val 0
---
Event: time: 59.786, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 60.030, rel: 244, diff: 244, type 1 code 113 val 0
---
Event: time: 60.084, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 60.330, rel: 245, diff: 245, type 1 code 113 val 0
---
Event: time: 60.383, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 60.584, rel: 201, diff: 201, type 1 code 113 val 2
Event: time: 60.830, rel: 446, diff: 245, type 1 code 113 val 0
---
Event: time: 60.982, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 61.230, rel: 247, diff: 247, type 1 code 113 val 0
---
Event: time: 61.284, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 61.486, rel: 203, diff: 203, type 1 code 113 val 2
Event: time: 61.682, rel: 399, diff: 196, type 1 code 113 val 2
Event: time: 61.880, rel: 597, diff: 198, type 1 code 113 val 2
Event: time: 62.080, rel: 796, diff: 199, type 1 code 113 val 2
Event: time: 62.330, rel: 1046, diff: 250, type 1 code 113 val 0
---
Event: time: 62.479, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 62.720, rel: 241, diff: 241, type 1 code 113 val 0
---
Event: time: 62.778, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 62.977, rel: 200, diff: 200, type 1 code 113 val 2
Event: time: 63.179, rel: 402, diff: 202, type 1 code 113 val 2
Event: time: 63.377, rel: 599, diff: 197, type 1 code 113 val 2
Event: time: 63.620, rel: 842, diff: 243, type 1 code 113 val 0
---
Event: time: 63.676, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 63.875, rel: 200, diff: 200, type 1 code 113 val 2
Event: time: 64.120, rel: 444, diff: 244, type 1 code 113 val 0
---
Event: time: 64.176, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 64.375, rel: 198, diff: 198, type 1 code 113 val 2
Event: time: 64.574, rel: 397, diff: 199, type 1 code 113 val 2
Event: time: 64.775, rel: 599, diff: 202, type 1 code 113 val 2
Event: time: 65.020, rel: 843, diff: 244, type 1 code 113 val 0
---
Event: time: 65.172, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 65.420, rel: 247, diff: 247, type 1 code 113 val 0
---
Event: time: 82.884, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 83.130, rel: 246, diff: 246, type 1 code 113 val 0
---
Event: time: 83.595, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 83.840, rel: 245, diff: 245, type 1 code 113 val 0
---
Event: time: 83.933, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 84.180, rel: 246, diff: 246, type 1 code 113 val 0
---
Event: time: 84.370, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 84.575, rel: 205, diff: 205, type 1 code 113 val 0
---
Event: time: 84.575, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 84.799, rel: 223, diff: 223, type 1 code 113 val 0
---
Event: time: 84.799, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 85.040, rel: 240, diff: 240, type 1 code 113 val 0
---
Event: time: 85.099, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 85.308, rel: 209, diff: 209, type 1 code 113 val 0
---
Event: time: 85.308, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 85.424, rel: 115, diff: 115, type 1 code 113 val 0
---
Event: time: 85.424, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 85.670, rel: 246, diff: 246, type 1 code 113 val 0
---
Event: time: 86.335, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 86.580, rel: 244, diff: 244, type 1 code 113 val 0
---
Event: time: 92.802, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 93.050, rel: 248, diff: 248, type 1 code 113 val 0
---
Event: time: 93.104, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 93.304, rel: 199, diff: 199, type 1 code 113 val 2
Event: time: 93.550, rel: 445, diff: 246, type 1 code 113 val 0
---
Event: time: 93.701, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 93.900, rel: 199, diff: 199, type 1 code 113 val 2
Event: time: 94.150, rel: 449, diff: 250, type 1 code 113 val 0
---
Event: time: 94.198, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 94.398, rel: 199, diff: 199, type 1 code 113 val 2
Event: time: 94.598, rel: 400, diff: 201, type 1 code 113 val 2
Event: time: 94.797, rel: 598, diff: 198, type 1 code 113 val 2
Event: time: 95.040, rel: 841, diff: 243, type 1 code 113 val 0
---
Event: time: 95.201, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 95.450, rel: 249, diff: 249, type 1 code 113 val 0
---
Event: time: 95.497, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 95.695, rel: 198, diff: 198, type 1 code 113 val 2
Event: time: 95.940, rel: 442, diff: 244, type 1 code 113 val 0
---
Event: time: 95.994, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 96.196, rel: 202, diff: 202, type 1 code 113 val 2
Event: time: 96.395, rel: 401, diff: 199, type 1 code 113 val 2
Event: time: 96.596, rel: 601, diff: 200, type 1 code 113 val 2
Event: time: 96.840, rel: 845, diff: 244, type 1 code 113 val 0
---
Event: time: 96.992, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 97.240, rel: 247, diff: 247, type 1 code 113 val 0
---
Event: time: 97.292, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 97.540, rel: 248, diff: 248, type 1 code 113 val 0
---
Event: time: 97.591, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 97.793, rel: 203, diff: 203, type 1 code 113 val 2
Event: time: 98.040, rel: 449, diff: 246, type 1 code 113 val 0
---
Event: time: 98.189, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 98.389, rel: 199, diff: 199, type 1 code 113 val 2
Event: time: 98.588, rel: 399, diff: 200, type 1 code 113 val 2
Event: time: 98.788, rel: 598, diff: 199, type 1 code 113 val 2
Event: time: 98.987, rel: 798, diff: 200, type 1 code 113 val 2
Event: time: 99.187, rel: 997, diff: 199, type 1 code 113 val 2
Event: time: 99.387, rel: 1198, diff: 201, type 1 code 113 val 2
Event: time: 99.630, rel: 1440, diff: 242, type 1 code 113 val 0
---
Event: time: 99.685, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 99.930, rel: 244, diff: 244, type 1 code 113 val 0
---
Event: time: 99.985, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 0.184, rel: 200, diff: 200, type 1 code 113 val 2
Event: time: 0.430, rel: 445, diff: 245, type 1 code 113 val 0
---
Event: time: 0.484, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 0.683, rel: 199, diff: 199, type 1 code 113 val 2
Event: time: 0.883, rel: 398, diff: 199, type 1 code 113 val 2
Event: time: 1.082, rel: 598, diff: 200, type 1 code 113 val 2
Event: time: 1.282, rel: 797, diff: 199, type 1 code 113 val 2
Event: time: 1.482, rel: 997, diff: 200, type 1 code 113 val 2
Event: time: 1.682, rel: 1198, diff: 201, type 1 code 113 val 2
Event: time: 1.930, rel: 1445, diff: 247, type 1 code 113 val 0
---
Event: time: 1.980, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 2.230, rel: 249, diff: 249, type 1 code 113 val 0
---
Event: time: 2.280, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 2.479, rel: 199, diff: 199, type 1 code 113 val 2
Event: time: 2.679, rel: 398, diff: 199, type 1 code 113 val 2
Event: time: 2.878, rel: 598, diff: 200, type 1 code 113 val 2
Event: time: 3.078, rel: 797, diff: 199, type 1 code 113 val 2
Event: time: 3.287, rel: 1006, diff: 209, type 1 code 113 val 2
Event: time: 3.530, rel: 1249, diff: 243, type 1 code 113 val 0
---
Event: time: 3.579, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 3.820, rel: 240, diff: 240, type 1 code 113 val 0
---
Event: time: 3.879, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 4.075, rel: 197, diff: 197, type 1 code 113 val 2
Event: time: 4.275, rel: 397, diff: 200, type 1 code 113 val 2
Event: time: 4.476, rel: 598, diff: 201, type 1 code 113 val 2
Event: time: 4.674, rel: 795, diff: 197, type 1 code 113 val 2
Event: time: 4.876, rel: 997, diff: 202, type 1 code 113 val 2
Event: time: 5.076, rel: 1197, diff: 200, type 1 code 113 val 2
Event: time: 5.273, rel: 1395, diff: 198, type 1 code 113 val 2
Event: time: 5.479, rel: 1601, diff: 206, type 1 code 113 val 2
Event: time: 5.674, rel: 1795, diff: 194, type 1 code 113 val 2
Event: time: 5.871, rel: 1993, diff: 198, type 1 code 113 val 2
Event: time: 6.120, rel: 2241, diff: 248, type 1 code 113 val 0
---
Event: time: 6.171, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 6.370, rel: 200, diff: 200, type 1 code 113 val 2
Event: time: 6.576, rel: 405, diff: 205, type 1 code 113 val 2
Event: time: 6.820, rel: 649, diff: 244, type 1 code 113 val 0
---
Event: time: 6.869, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 7.069, rel: 200, diff: 200, type 1 code 113 val 2
Event: time: 7.268, rel: 400, diff: 200, type 1 code 113 val 2
Event: time: 7.468, rel: 599, diff: 199, type 1 code 113 val 2
Event: time: 7.710, rel: 841, diff: 242, type 1 code 113 val 0
---
Event: time: 7.767, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 7.966, rel: 200, diff: 200, type 1 code 113 val 2
Event: time: 8.210, rel: 443, diff: 243, type 1 code 113 val 0
---
Event: time: 8.266, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 8.510, rel: 244, diff: 244, type 1 code 113 val 0
---
Event: time: 8.566, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 8.810, rel: 244, diff: 244, type 1 code 113 val 0
---
Event: time: 9.183, rel: 0, diff: 0, type 1 code 113 val 1
Event: time: 9.430, rel: 246, diff: 246, type 1 code 113 val 0
---

@seife

Kannst du dir nochmal den Audioplayer bzw. das Internetradio anschauen.
Die Autorepeat-Funktion beim Scrollen durch die Listen funktioniert noch nicht.

Jetzt schon, zumindest im Audioplayer. Internetradio wird ja auch dort gemacht, oder?
Das "numericzap" im Audioplayer habe ich auch gleich gefixt.
http://cvs.tuxbox.org/cgi-bin/viewcvs.c ... 56&r2=1.57

Thanks a lot. Guten Rutsch ins Neue Jahr!

@seife

Innerhalb der Audiosettings bleibt bei einem Wechsel der Volumesteuerung von avs/lirc/ost der Lautstärkebalken zum Justieren der Lautstärke nicht mehr länger als einen Bruchteil einer Sekunde sichtbar und verschwindet sofort.
Nur durch das Weiterschalten der Volumesteuerungsauswahl blitzt der Lautstärkebalken kurz auf.
Wählt man dann allerdings die +/- Tasten der FB zum einstellen, wird der Lautstärkebalken wieder sichtbar und verschwindet nicht mehr.

also ich hab die beiden patche mit kernel repeat drinnen.
ausser, daß man anfangsverzögerung nicht < 30 und wiederholungsverzögerung nicht < 10 stellen darf, geht das klasse.
anbei ein log, wenn man mit werten:
-anfangsverzögerung=55
-wiederholung=20
kanalliste aufgerufen hat, und mit hoch oder runter durch die liste scrollt. hänger hab ich keine feststellen können

auffällig ist am anfang die 546 und zum schluss die 170. also höher oder niedriger als die konstanten 200(einstellung 20! im menü) also is irgendwo ne "0" verschütt gegangen seife

Kernel-repeat bringt nicht den erhofften Vorteil (nämlich dass der Code portabler wird), weil die dreambox-Treiber das anscheinend nicht können , insofern habe ich das nicht weiter verfolgt.

Ansonsten sieht es bei dir nach Anfangsverzögerung 550, wiederholverzögerung 200 aus.