bug in DMM driver ? And several weeks ago this bug was not there ???
Edited by ims, 2 March 2014 - 10:37.
Posted 2 March 2014 - 11:56
When I go to teletext, then picon is partialy replaced by dark (f.eg. there is 1/3 of PICON only). After return from Teletext is OLED white or dark or "running" nonsences, or first row is lighting, or is there big text of EPG...
May be, when is displayed message, that transponder do not has teletext, then after return is OLED ok. Strange...
What is "[SKIN] Parsing embedded skin <embedded-in-'ShellStarter'>" after running TXT ?
Posted 2 March 2014 - 14:04
skin = """ <screen position="1,1" size="1,1" title="TuxTXT" > </screen>"""
Posted 2 March 2014 - 21:46
I tried it after reboot on dad's box ( because my OLED is little wrong after 3 years using) and I can saw:
1) call teletext - picon is replaced cca 1/3-2/3 with black.
2) return => for short time is visible some text - it seems as number of channel and name. After it is placed whole picon. But why is there for moment displayed text ? Ii do not know, because i have in skin for LED picon, progress and record flag only
after several steps (1, 2) is OLED fully corrupted - it "rotates" or whole is black or clear white line on top or bottom etc...
When on channel is displayed message, that transponder do not broadcasting teletext, then OLED is not corrupted so soon.
Posted 2 March 2014 - 21:54
And it works with an old image without problems?
I have no idea what could cause it. At best you try to debug it with some debug eDebug statements.
E.g. it would be useful to know whether this procedure
void eTuxtxtApp::recvEvent(const int &evt) { uiRunning = false; eDBoxLCD::getInstance()->unlock(); eDBoxLCD::getInstance()->update(); fbClass::getInstance()->unlock(); /* emit */appClosed(); }
(http://sourceforge.n...s/tuxtxtapp.cpp)
is called after closing teletext. And what "eDBoxLCD::getInstance()->update();" exactly do.
Posted 2 March 2014 - 23:06
I still do not know, why is before picon always displayed for 0,3s realtime clock. When I tried it on vu ultimo, there before displaying teletext on TV screen, at first is there left bottom displayed yellow date and time from infobar, then left bottom is moved teletext screen and after it is teletext screen displayed standardly over whole TV screen. When is teletect closed, then is for moment displayed reduced teletext screen left bottom again. But it is on CRT screen.
It seems, there are some wrong. May be, that clock displayed before picon are in wrong size and it corrupts OLED.
As I saw, on vu ultimo time of time I must turn on teletext again, because txt "flashs" and close imediately. Strange.
Edit: tried again and on DM800SE: before teletext is hide picon and is displayed:
uxTXT
23:13
for time, when is waiting for TXT. When is TXT displayed on TV, then whole OLED is black.
return from TXT: after black is for moment displayed TuxTXT and clock, then picon (or corrupted oled)
Edited by ims, 3 March 2014 - 00:10.
Posted 3 March 2014 - 06:45
As far as i know this began on the 8th of december, images with oled like my DM 8000, had no issues with TT before that date.I must know, when it was corrupted. May be, that was some changed in E2, what it corrupted. I think, it began cca on february.
-Triax 88cm schotel
-TD 20 flexi-block met 2 Inverto Black Premium Quattro LNB's
- Polytron PSG 908 Q II Multiswitch 8 in / 8 out
- VU+Duo 4K, 2x VU+ Duo2, Zgemma H8.2H en een DM8000 HD PVR
Posted 3 March 2014 - 07:13
Posted 3 March 2014 - 11:40
Maybe this??
http://sourceforge.n...2a27d7a4a18847/
But it was a bug and not correct...
Yes. I reverted it and all works well. Now it is without "TuxTXT and clock" screen between picon and dark screen and all works well. OLED do not crashing more.
But I think, there was wanted: picon (or infobar screen) to "TuxTXT and clock" and not dark screen ?
Edited by ims, 3 March 2014 - 11:45.
0 members, 8 guests, 0 anonymous users