OpenPli 2.1 20.10.2011 freezes after press...
macnuts 20 Oct 2011
The box freezes after pressing the TEXT button while watching the service with no teletext.
I pressed the TEXT button on remote. At first, I got the tuxtxt(?) window with some message about teletext being searched, then after the message was gone the box was stuck. The teletext layout was displayed (I had configured it to display current service in the bottom right corner), the service was being played, the teletext page area was blank (there was no teletext for that service). And the problem was that I couldn't close the teletext view. I tried to press every possible key on the remote, but no luck. The only option was to switch off the power.
The same problem occurred just after I flashed the image as well. The tuxtxt was not configured at that time (or it had the "factory default settings"). The only difference was that after the "teletext being searched"-like message had disappeared, the tuxtxt configuration window appeared (the one which is displayed when one presses the Menu button while viewing teletext). The window did not response to the remote. The only option was to switch the power off.
I had no such problem with my previous image, OpenPli 2.0 built on 03.05.2011.
BTW, this is the first OE-1.6 image I use that supports DM Spectrum Keyboard (or maybe some blocking plugin is no longer used)!
Regards.
Edited by Orzes72, 20 October 2011 - 17:41.
able 20 Oct 2011
blzr 20 Oct 2011
for me it looks as follows:
1. after enigma restart, if you first run txt on a channel with no txt available BUT with txt on this transponder, you've got freeze during/after txt search
2. but if you first run txt on a channel with txt available - after that you can press txt button on every channel you want, with no freeze and everything works as it should (until next enigma restart...)
//and if you first run txt on channel with no txt available on a whole transponder, you got no freeze, but it doesn't 'fix' txt as in 2.
so, it seems that has something to do with txt search...
littlesat 20 Oct 2011
blzr 20 Oct 2011
maybe I should but I am notYou should always able to quit this via exit.
it's 100% reproducible here (as I described above) - try restart enigma go to service with no txt, press txt and after the search you'll stuck with teletxt configuration menu on the screen...
//it's not a freeze in strict sense, tv is running under the osd normally, but you can do nothing but 'hard' reboot your box...
littlesat 20 Oct 2011
pieterg 20 Oct 2011
All this after a clean reboot.
Tried with txt caching enabled as well as disabled, same result.
littlesat 20 Oct 2011
When it finds more then one teletext service on a transponder you get in the teletext menu. From there it may take two exits to get back into the normal "zap" zone as with the first exit you will get into the first found teletext version >which< could be an empty page of the service e.g. only contains subtitles.
You should be able to use the cursor keys from there and also exit (sometimes twice)...you'll stuck with teletxt configuration menu on the screen...
blzr 20 Oct 2011
same hereJust tested here. Here I get a nice searching for teletext service message and then it is fine... On a transper without TT services is says no teletext service found and I can use exit.
and here if I go directly to such service after restart I got:On a transponder with just one teletekst service it starts directly the only teletekst service.
'HBO HD
waiting for reception of page 100'
and cant' get out of this
it turned out you're right BUT unfortunately if you use any other key (like exit or ok) instead of 'arrow down' first you're stuckOn a transponder with teletekst service I indeed get the menu, can go down and select a teletekst channel. So when you get hte configuration screen it should not get stuck... Use down first...
littlesat 21 Oct 2011
blzr 21 Oct 2011
moreover, as I wrote in my first post, after I run txt on service with txt on it first, then such freeze does not appear at all, on any service, I can press any key, and escape from menu after that...
this 'bug' happens for me only on first txt run after the restart...
//and yes, I think this has nothing to do with latest updates, it's with us for a while I suppose
Edited by blzr, 21 October 2011 - 07:21.
littlesat 21 Oct 2011
blzr 21 Oct 2011
//in fact I haven't encountered it until yesterday (and I had to try hard to get it )
regarding a log - yesterday I ran enigma in console but nothing intersting appeared (iirc something like 'tuxtxt init > ok', and then nothing more), I can try to do some more tests tonight...
macnuts 21 Oct 2011
Thank you for the detailed info & workaround. I was concerned about my wife pressing the text button accidentally and then try to exit immediately. But with your workaround (open teletext on service with teletext provided after enigma2 restart) it is no problem anymore.
@littlesat:
Here is the init4; enigma2 log. Nothing fancy, as blzr said.
You should be able to reproduce the behavior on any of the following FTA services (without teletext):
Anixe HD: 19.2E, 10773kHz H 22000 3/4 DVB-S2, 1:0:19:526C:41D:1:C00000:0:0:0
Eska TV: 13.0E, 11508kHz V 27500 5/6 DVB-S, 1:0:1:3DC3:640:13E:820000:0:0:0
1. Switch to the Eska TV or Anixe HD.
2. Restart your box.
3. You should be on the Eska TV or Anixe HD automatically after the box is restared (hopefully).
4. Press Text button, wait for the configuration menu.
5. Press the Exit button as the only button on the config menu.
6. Observe the bug: no way to exit empty teletext view.
It is important to restart the box on the channel you are going to test.
I restarted the box on Anixe HD, then switched to Eska TV from my bouquet, then switched to other services on the same transponder till I found the one with teletext (did not used the text button, just looked for the txt icon on infobar). Then I switched back to Eska TV to test the tuxtxt behavior. And everything was Ok, even though I had not used teletext since power up.
BR.
blzr 21 Oct 2011
1. this 'bug' /?/ appears when enigma restarts on service with no txt available (and it appears then on other such services too),
unless...
2. just zapping first to a channel with txt available is actually this waht 'fixes' this bug (no need to run txt on it)
littlesat 21 Oct 2011
littlesat 21 Oct 2011
Now it also freezes with 13th street NL - but only when I did not toggle a selected tuxtxt service...
Attached Files
Edited by littlesat, 21 October 2011 - 17:43.
littlesat 21 Oct 2011
if (Init)
tuxtxt_cache.vtxtpid = 0; // force clear cache
#endif
/* reset data */
//page_atrb[32] = transp<<4 | transp;
renderinfo.inputcounter = 2;
tuxtxt_cache.page = 0x100;
lastpage = 0x100;
renderinfo.prev_100 = 0x100;
renderinfo.prev_10 = 0x100;
renderinfo.next_100 = 0x100;
renderinfo.next_10 = 0x100;
tuxtxt_cache.subpage = 0;
tuxtxt_cache.pageupdate = 0;
tuxtxt_cache.zap_subpage_manual = 0;
renderinfo.hintmode = 0;
memset(renderinfo.page_char,' ',40 * 25);
for (i = 0; i < 40*25; i++)
{
renderinfo.page_atrb[i].fg = tuxtxt_color_transp;
renderinfo.page_atrb[i].bg = tuxtxt_color_transp;
}
tuxtxt_ClearFB(&renderinfo,tuxtxt_color_transp);
/* start demuxer with new vtxtpid */
if (renderinfo.auto_national)
tuxtxt_cache.national_subset = pid_table[current_pid].national_subset;
#if TUXTXT_CFG_STANDALONE
tuxtxt_cache.vtxtpid = pid_table[current_pid].vtxt_pid;
tuxtxt_start_thread();
#else
tuxtxt_start(pid_table[current_pid].vtxt_pid, -1);
#endif
Edited by littlesat, 21 October 2011 - 17:50.