[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[kszaq]

I have a question for anyone that has transfered a remote config, when I transfer my remote config to my box the remote starts working, but a few buttons need mapping, I use the addon keymapper, but for some reason I can't map the menu button with the three lines. Does anyone know why?

pigbait There may be 2 reasons:
1. The menu key is not mapped in remote.conf file.
2. The key is mapped but it is not recognized by Kodi.

You can diagnose that by connecting over SSH and typing cat /proc/kmsg - that way you'll see live kernel log. For every key pressed a message is displayed - it says if the key is not recognized or what keycode it has. For Menu key, the keycode numer should be 46.

Ok well I'm guessing its a Kernel thing, as I have updated with .tar to your OE 5.0.8.18 build and I lose wifi, here are dmesg logs from build with working wifi and build without wifi

pigbait Using version with no working WiFi, can you please try connecting over SSH and typing modprobe 8189es?

Ok, it has been a while since I received my UStick Mk809 Plus from Geekbuying. It works very smooth under Android compared to my Minix Neo X7 running with Rockchips.

I am looking forward to flashing this with Openelec.

Kszaq, I know you said the MK808B and MK809 Plus share the same flash but the units outwardly are a little different. Are there instructions stating exactly how to go about flashing the MK809 Plus available in order to refer to?

Thank you very much in advance.

mpp MK809 Plus is reported to work but is not guaranteed. As you may already know, your device doesn't have a "recovery button". From what I looked into bootloader source code, you may be able to enter recovery by repeatedly pressing Menu button right after powering on the box - and you should be aware that even if it works, you'll lose that ability after flashing OpenELEC as the included bootloader is intended for devices with recovery button and not without. If the Menu button method doesn't work for you, you can either use Terminal Emulator or connect over ADB and issue a reboot recovery command.

[ofear]

No idea, you have to try by yourself. Looking at the remote, MXQ version should be usable but you flash it on your own risk.

I'm a software developer and I guess I will be able to port this source to run on the Chiptrip MXV S805.

Can you please show me what should I do to try and test it?

I guess I need to replace or to edit the Kernel file...

Thanks kszaq !

[ofear]

OK. I'm going to try to install the MXQ version on the MXV player. (It the same manufacturer and I so here that GearBest gave someone to install a newer ROM of the MXQ on the MXV.)

Just one thing before I start..

How do I set a returning point if something goes wrong?
I mean, How to I backup my TV player before testing a new ROM / OS on it?

[rev6]

OK. I'm going to try to install the MXQ version on the MXV player. (It the same manufacturer and I so here that GearBest gave someone to install a newer ROM of the MXQ on the MXV.)

Just one thing before I start..

How do I set a returning point if something goes wrong?
I mean, How to I backup my TV player before testing a new ROM / OS on it?

Use the TWRP recovery and make a backup to a micro-SD card. Or run it from micro-SD card without touching NAND.

[ofear]

Use the TWRP recovery and make a backup to a micro-SD card. Or run it from micro-SD card without touching NAND.

So I understand that I can run it from the micro-SD without even override the OS?
How can I boot it up from SD only?

Or maybe I'm mixing things up?

[phinc]

SSH into your stick and type "Reboot recovery" ...The stick will reboot and look for recovery + update files on your SD Card...then it will proceed to flash NAND.

I don't want to flash. What i want to do is to reboot to android from my SD installation of openELEC. Is there a way to do this via SSH?

EDIT: Nevermind, i found it out. It works by executing /usr/bin/rebootfromnand.sh

So I understand that I can run it from the micro-SD without even override the OS?
How can I boot it up from SD only?

Or maybe I'm mixing things up?

Yes. Just put the recovery.img in the root of your SD card, insert it and boot via the toothpick (reset button) method. This way, the recovery.img on the SD card should be executed.

[...]

I bought this keyboard: http://www.gearbest.com/mice-keyboards/pp_70916.html
It works in Android and Windows, but not in OpenELEC (at least not in this version). Is there any way i can make it work?

kszaq could you please comment on this? Thank you in advance.

[rev6]

A small problem with power off on my MXQ. If TV source isn't the MXQ, if you turn off the MXQ (power button, down, enter) the box will switch off then switch on and the TV will switch over to the box source I can change source to power off, no problem.

[phinc]

Anybody managed to mount the ext4 storage partition of OpenELEC in android?

[kszaq]

So I understand that I can run it from the micro-SD without even override the OS?
How can I boot it up from SD only?

Or maybe I'm mixing things up?

ofear I'd recommend making a TWRP backup anyway. Using SD card version needs overwriting a bootloader (but doesn't touch other partitions) so you'd better keep a backup handy.

I don't want to flash. What i want to do is to reboot to android from my SD installation of openELEC. Is there a way to do this via SSH?

EDIT: Nevermind, i found it out. It works by executing /usr/bin/rebootfromnand.sh

phinc Yes, you can use /usr/bin/rebootfromnand.sh if you want to add a shortcut to your skin or simply reboot switch_system if you need to issue a command over SSH. Keep in mind that reboot switch_system forces a boot from NAND and not a system switch so if you want to reboot from Android to Android, you should also use that command.

kszaq could you please comment on this? Thank you in advance.

Please do the following:
1. Boot OpenELEC.
2. Connect device's receiver a few seconds after booting.
3. Collect dmesg and post a result here.

That way I'll be able to see if there's something missing in kernel config to support your wireless keyboard.

Anybody managed to mount the ext4 storage partition of OpenELEC in android?

Try mounting /dev/mmcblk0p2 partition. I haven't tried that but it should work.

[miguelf]

kszaqNo sound this time using the p18 when watching standart sports streams. Can you apply the audio patch again?
I wish i could go back to p17 but i know it was deleted since it was not stable.

[pigbait]

kszaq Ok so modprobe 8189es kinda worked my WiFi booted up right away after hitting enter, once connected it won't do anything i.e download addons or connect via SSH the wifi will get an IP address... also once I reboot these settings are lost... now I did try the remote command you've suggested and it sees the menu key as mappable in SSH but i cant get keymap editor addon to map it,
this is the remote config from my box not sure if you can see anything strange about it.

Your work is greatly appreciated and thanks again.

[borikua]

With the latest build 5.0.8.18 , audio on Live streams is now high pitched and everybody sounds like the chipmunks. Never had this happen on the other builds.

I am using all Black MXQ HD18Q.

[Pryxus]

Good morning.

I was SO excited to see this version of OpenELEC for my MXQ box a couple of days ago. Especially, because I already have two RPi with OpenELEC and one Amazon Fire TV which I planned to replace by my MXQ.

Unfortunately, after four days of testing, I must admit that the MXQ is no alternative to any of the other devices. At least for me and my equippment.

- it scrambles my HDMI settings, which means that the audio connection to my Pioneer receiver is disconnected and either there is no sound at all or just through my TV
- HDMI-CEC only works randomly (while all the other devices communicate perfectly with my Sony Bravia TV)
- MXQ seems to go to sleep after some time of switching to another channel. When returning to MXQ's HDMI-port, the screen is black and the box cannot be reactivated. I have to swith it off and on.

While point 1 and 2 are OS independend (it happes with Android and OpenELEC), the third point only happes with OpenELEC. Android returns to it's screensaver-screen.

That's a big bummer which makes this device unusable for me. I guess, the main problem is the lousy hardware. After all I got what I paid for ;-).

Still, I admire your enthusiasm and will follow your project :-).

[kszaq]

kszaqNo sound this time using the p18 when watching standart sports streams. Can you apply the audio patch again?
I wish i could go back to p17 but i know it was deleted since it was not stable.

miguelf Audio patches are present in 5.0.8.18. Basically the only change that could affect audio is reverting to kernel, which was used in 5.0.8p8 anyway.

As for 5.0.8.17, it is still available to download, should you wish to downgrade: http://s805.eu/releases/5.0.8.17/

kszaq Ok so modprobe 8189es kinda worked my WiFi booted up right away after hitting enter, once connected it won't do anything i.e download addons or connect via SSH the wifi will get an IP address... also once I reboot these settings are lost... now I did try the remote command you've suggested and it sees the menu key as mappable in SSH but i cant get keymap editor addon to map it,
this is the remote config from my box not sure if you can see anything strange about it.

Your work is greatly appreciated and thanks again.

pigbait Try changing lines with

0x27 106

to

0x27 46

I'm guessing this is the menu button.

As for WiFi, I will include the 8192es driver in my next HD18Q builds. It seems like the wifi_dummy module (the one I use to power on SDIO WiFi) prevents your WiFi from working properly.

With the latest build 5.0.8.18 , audio on Live streams is now high pitched and everybody sounds like the chipmunks. Never had this happen on the other builds.

I am using all Black MXQ HD18Q.

borikua I need logs. Also, did that happen on 5.0.8p8?

Good morning.

I was SO excited to see this version of OpenELEC for my MXQ box a couple of days ago. Especially, because I already have two RPi with OpenELEC and one Amazon Fire TV which I planned to replace by my MXQ.

Unfortunately, after four days of testing, I must admit that the MXQ is no alternative to any of the other devices. At least for me and my equippment.

- it scrambles my HDMI settings, which means that the audio connection to my Pioneer receiver is disconnected and either there is no sound at all or just through my TV
- HDMI-CEC only works randomly (while all the other devices communicate perfectly with my Sony Bravia TV)
- MXQ seems to go to sleep after some time of switching to another channel. When returning to MXQ's HDMI-port, the screen is black and the box cannot be reactivated. I have to swith it off and on.

While point 1 and 2 are OS independend (it happes with Android and OpenELEC), the third point only happes with OpenELEC. Android returns to it's screensaver-screen.

That's a big bummer which makes this device unusable for me. I guess, the main problem is the lousy hardware. After all I got what I paid for ;-).

Still, I admire your enthusiasm and will follow your project :-).

Pryxus I admit that these are showstoppers. Unfortunately they all exist due to lousy CEC implementation by Amlogic. Let's hope their next kernel release fixes at least some of them.

[phinc]

phinc

Please do the following:
1. Boot OpenELEC.
2. Connect device's receiver a few seconds after booting.
3. Collect dmesg and post a result here.

That way I'll be able to see if there's something missing in kernel config to support your wireless keyboard.


Try mounting /dev/mmcblk0p2 partition. I haven't tried that but it should work.

Thanks. When i collected the dmesg, the keyboard suddenly started working, i have no idea why. I hope it stays that way .
And about the mounting: You mean dev/block/mmcblk0p2?

I tried

su
mount -rw -t ext4 /dev/block/mmcblk0p2 /storage/external

in terminal emulator. There was no error message but nothinng was mounted in storage/external either.