[Venton Unibox HDx] No typing with remote possible

[BoxFreak]

Hello,

Upgraded to Apollo version 24 and faced an issue when trying to type letters with remote controller. It only gives out numbers, no letters at all. Checked with trying to edit an autotimer definitions and also same thing when trying to edit just ordinary timer entry.
Anyone else seen this?

 

[Tkr001]

Do you have text support enabled in System, Setup, Remote Control Code?

 

[BoxFreak]

Sorry, but where is the "Remote Control Code" setup.
I go to "Menu" -> "Setup" -> "System", in there I can't find anything that would show me that info
(using finnish language in menu's) What else is set up in there?

Besides that this was working with build 19, and settings were restored from it...

 

[Tkr001]

Menu -> Setup -> System -> Remote Control Code -> Text Support set to yes

Remote control cole is the second to bottom in the "System" list. Note the list is more than one page long. Alonso set there is the remote control code to use. This must be set on the remote and in the image but won't have anything to do with your problem. Sorry can't help in Finnish

Note I am using a Vu box not a Venton so may be different on your box.

 

[BoxFreak]

Thans for the reply's, but with Venton there is NO such menu item at all (I even changed language to English in the box to check)...

 

[Joe_90]

Ok - the method of entry has been changed. Only noticed it myself today when I fresh flashed 024 image clean (no settings restore) and had to input my wi-fi password. If you press the "Text" key on your remote in one of the menus where you have to input alpha characters (you will see the "Text" icon on the bottom of the screen as a prompt) you will get an on-screen keyboard. It's a bit more flexible than the old method although you possibly are pressing the remote keys as many times as you would using the old method.

- note I do not know if you will get a proper keyboard with the correct accented character glyphs

 

[BoxFreak]

Well the "text" key is not an allowed key in timers or autotimers, so thats not possible...

 

[Joe_90]

Well the "text" key is not an allowed key in timers or autotimers, so thats not possible...

I just checked autotimers and timers and was able to use the remote keys in alphabetic fields to edit the contents directly as per usual. This is on a GB Quad+. The "text key" facility seems to be only in certain menus, such as network adapter setup. Autotimers/timers are unchanged, so it should work for you, but there may be a specific setting needed for your box. Sorry not able to help, but maybe a Venton user can answer.

 

[kk1234]

Hi, I've got the same problem on Venton HD3 after updating to 025 (and now to 026). Haven't found any setting yet which would change this behaviour back to what it was on 023. I noticed before that also the onscreen keyboard used to support typing with the number keys but not anymore.

 

[Joe_90]

Well the "text" key is not an allowed key in timers or autotimers, so thats not possible...

Confirmed on Miraclebox Premium Twin also, thanks for reporting. Bug report opened and may be driver related. We are investigating...

 

[Joe_90]

Here's a preview version of the fix (courtesy of Rob) for alpha entry which will be contained in the next image release.

If you are comfortable with using FTP to copy files to your receiver,
1. please unzip the attached file (UsageConfig.py) and copy to the following directory - /usr/lib/enigma2/python/Components
2. Rename the existing UsageConfig.pyo to something else.
3. Restart Enigma and it will generate a new UsageConfig.pyo
4. Test the fix in timers/autotimers menu
5. If ok please delete the .py file left in the directory.

 

[BoxFreak]

Sorry, but I was not at home so that I could have checked this. Is this now included with build 28? I could try to check the fix with it tonight...

 

[Joe_90]

Sorry, but I was not at home so that I could have checked this. Is this now included with build 28? I could try to check the fix with it tonight...

Yes - it's in build 028

 

[BoxFreak]

Thank you for getting this fixed. Tested now with build Apollo 28 to be working.:thumbsup:

 

[Joe_90]

Good stuff - nothing to do with me though. Devs have sorted it, I'm only the messenger in this case