Forums

Welcome! On Miraclebox Premium Micro keys media and fav don't work. Previously I had OpenMB and Egami-Image and in those softwares - these keys work (key media open recording list). Can you fix it?

I have always been told that the code should be present in the drivers. In case those buttons don't work, this should be changed in the drivers, I guess.

Try the hotfix configuration, if that doesn't work, it must be fixed in the drivers.

I have always been told that the code should be present in the drivers.

That is the first prerequisite.
The second is that the button (keycode) is also present in the active keymap. And that is image dependant.
Edited by Rob van der Does, 24 December 2016 - 17:17.

With keymap from OpenMB, key media works, but key fav don't work.

Edited by hawkeye116477, 24 December 2016 - 21:13.

Where exactly does this file come from? Because I don't see any OpenMB specific changes here: https://github.com/o...data/keymap.xml

This is the OpenMB that illegally call their images "OpenPLI 5". I have reported this before long time ago but nothing seems to be done about it, which is strange because the site is linked by the manufacturer that has an agreement with OpenPLI for original support, so why then link to illegal OpenPLI 5 ?

 

 

Edited by Dimmie, 25 December 2016 - 02:24.

On the top-left of the page you linked to it says "OpenMB based on OpenPLi".

Except that now OpenPLi officially support 2 models of MiracleBox.

https://www.openpli....oad/miraclebox/

So indeed Miracle Box provide "abusive OpenPli brand" images under www.openpli.com and at the same time OpenPLi officially support two of their boxes...
I would have hope that since OpenPLi now get in touch officially with MiracleBox will clarify once for all this situation, but now it is even worse.

The suggestion that I perform doesn't receive any remarks, nor feedback but this is typically a nice case to have the feature I ask for:

https://forums.openp...-key-discovery/

Pr2

Where exactly does this file come from? Because I don't see any OpenMB specific changes here: https://github.com/o...data/keymap.xml

Here is -> https://github.com/o...87199b1b0f39c72 .

I just flashed such an image and indeed: once on the box it's all PLi, never any 'based on PLi'.

Bah....

 

BTW: A similar behaviour as GB does: they manipulated VU's HbbTV so it runs on their MIPS image.

Conclusion: No ethics when it comes to money making....

I just flashed such an image and indeed: once on the box it's all PLi, never any 'based on PLi'.

Bah....

 

BTW: A similar behaviour as GB does: they manipulated VU's HbbTV so it runs on their MIPS image.

Conclusion: No ethics when it comes to money making....

On bootlogo is written „OpenMB based on OpenPli", but on other places is as you write.

I just ran into the same issue. I created a startup script that modifies the keymap.xml, so I can update my miraclebox premium again without issues It just replaced the "InfobarActions" section of the keymap.xml with the additional entries needed for the miraclebox remote control...

 

For creating the startup script, place the attached file 'user.txt' in /etc/init.d, remove the .txt extention, make it executable (chmod 777 user) and link it from /etc/rcS.d (ln -s ../init.d/user S80user).

Edited by Yo!, 27 December 2016 - 12:07.

I found other bug, when playing recording with default media player after press audio key and change audio, movie rewinds forward.

I just flashed such an image and indeed: once on the box it's all PLi, never any 'based on PLi'.

Bah....

 

BTW: A similar behaviour as GB does: they manipulated VU's HbbTV so it runs on their MIPS image.

Conclusion: No ethics when it comes to money making....

 

 

Exactly, I already reported this long time ago. I was surprised that nothing is done about it. The picture on the website and also the 'based on' is false/fake just to mislead the OpenPLI crew.

Edited by Dimmie, 27 December 2016 - 19:31.

We can't do anything about it, we don't know who to address.

 

There is no way to contact anybody, and there is no direct (visible) link between Miraclebox and OpenMB. If there was, there wouldn't be a need for them to ask us to make an image for their boxes.

 

If you have more information, please share so we can try to contact them again.

Come on!
 
You support already 2 STBs branded Miraclebox so you have the contacts.
 
https://openpli.org/...oad/miraclebox/
 
And of course openpli.com is only linked with Miraclebox!  They called the image OpenMB  which means Open Miracle Box ! In the bottom of the page:  "The open image for Miraclebox Premium"

They also registered:  openmb.net  (they cannot get openmb.com since it was already registered by someone else).

 

If OpenPLi is a registered trademark you can always try to contact:

Registrar Abuse Contact Email: @godaddy.com

 

Pr2

The fact that it is an MB image doesn't imply it is owned and made by MB.

 

Off course we have contacted them, but it not that easy, the same issues exist with Zgemma for example, where the website that provides "fake" OpenPLi images isn't from the manufacturer, but run by some distributor (which doesn't respond at all).

 

For GoDaddy the same is true as for OVH: you can report all you want, it goes directly to /dev/null, and you never get a response.

Let's get back to the topic better. So is there any chance that soon the problem with the Miraclebox remote control buttons will be repaired? On OpenMB so it is done: https://github.com/o...87199b1b0f39c72 . I hope this helps a little.

the favourites key is OK now, still not OK is the Plugin key, according to evtest it is the KEY_BOOKMARKS key code 156, putting this in keymap.xml does not resolve the problem, still unhandled key
<map context="InfobarActions">
..............................................................
<key id="KEY_BOOKMARKS" mapto="showPluginBrowser" flags="b" />
..............................................................´
</map>
can you put it please in HotKey.py