[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[sonofdibnah]

Bug report for 6.0.0.2 I'm afraid.

After the update spdif audio passthrough isn't working for anything as far as I could tell although I didn't check what it did with 5.1 audio before I reverted to 6.0.0.1. This is on Beelink MXQ running from SD.

As soon as I reverted, spdif worked again.

Happy to test scenarios if you want me to kszak.

[kszaq]

jed Thanks for posting. I looked at it and it's very similar to m201_1G so no changes in build needed, I suppose.

sonofdibnah Thanks for reporting. I did not check S/PDIF output as I don't use it, I use HDMI passthrough. Here's a quick fix: http://s805.eu/releases/6.0.1.2/MXQ_...Fix/kernel.zip Unpack this file to root folder of your SD card. This fix will be included in next release. I have to stop messing with device trees...

[niros]

From time to time I'm facing an issue with audio not synced with video.
This can be resolved with a reboot.

Is that a known issue? will it help if I'll provide dmesg output or something else?

[sonofdibnah]

jed Thanks for posting. I looked at it and it's very similar to m201_1G so no changes in build needed, I suppose.

sonofdibnah Thanks for reporting. I did not check S/PDIF output as I don't use it, I use HDMI passthrough. Here's a quick fix: http://s805.eu/releases/6.0.1.2/MXQ_...Fix/kernel.zip Unpack this file to root folder of your SD card. This fix will be included in next release. I have to stop messing with device trees...

Couldn't get the quick fix to work Kszaq. I unzipped the kernel image and used it to replace the existing kernel.img on the sd card. When I tried to boot with this new kernel, l could see various "bits" starting. By 'bits' I mean things like samba, remote and dummy wifi (adapter?). This showed on the Openelec boot screen but would not complete and run kodi. I tried a few times and each time it seemed to stop at a different point.

I then replaced my original kernel. Saw "bits" starting on the openelec screen and voila, I was back in kodi.

I'm more than happy to wait for your next release for the fix but if you want me to try something else, I read the forum at least once a day. I prefer to use spdif so I can turn the telly off when just listening to audio through my cinema amp.

[Craigthered]

I have a problem, I used the image provided by Pigbait back in october and it worked fine, was the first to work with the wifichip
realtext8189es.

All was well but I had a box stick on the open elec logo and another I accidentally put this image on too.
Both of the boxs have no way into the recovery menu via the toothpick method as the reset button does nothing.
Now I have started to try using the hard brick method and usb burning tool connecting to my laptop via usb.
I shorted out the correct pins and my laptop detects the 'world cup device' however it has a yellow exclamation mark in control panel and I cannot proceed any further. I was hoping you may have some experience with this and could assist.

Thanks

[pigbait]

what you can try is hook the box up via ethernet, check your router for the IP address of the box and SSH to the box with PUTTY, log in with Username: root password: openelec . once logged in type reboot recovery

its a shot in the dark. but has worked for me

[Compos]

Both of the boxs have no way into the recovery menu via the toothpick method as the reset button does nothing.

I have found that when this happened to me I was using an incorrect recovery image for my box. Try different recovery images on your SD card.

[Craigthered]

I have managed to get into recovery using a uboot sd card and shorting the pin. Is latest azaa release now compatible with realtek es?

[jed]

I have managed to get into recovery using a uboot sd card and shorting the pin. Is latest azaa release now compatible with realtek es?

Both 6.0.1.1 and 6.0.1.2 now work fine with WiFi in general, including Realtek8189.

[kszaq]

For all of you getting issues with booting 6.0.1.2, here's a build to test: http://s805.eu/test/6.0.1.3-devel-20160219/

Changelog:

• reverted device trees to those used in 6.0.1.1 and prior
• m201C_1G and m201C_512M device trees in HD18Q build replaced with what I found on Baidu

sonofdibnah This should also fix your S/PDIF issue.

[topher67]

I'm using linux to write the 5 sdcard boot files to the sdcard, and have flashed the uenv file but can't for the life of me get this to boot.

Have an OTT MXQ box with RT8189ES wifi chip, and am using the toothpick method ie holding in the reset button, sdcard inserted, push in power plug, but the thing just boots to (twrp) recovery.

I'm using the HD18Q rom, as the Android version of HD18Q works on my box. Would I have more joy trying a different version?

Peace.

[jed]

How do you change remote control in OpenElec ? Simply adding the correct remote.conf to /Configfiles/rc_keymaps does not and has never worked for me....

[sammaz]

How do you change remote control in OpenElec ? Simply adding the correct remote.conf to /Configfiles/rc_keymaps does not and has never worked for me....

Why not just use the Keymap editor addon? http://kodi.wiki/view/Add-on:Keymap_Editor You can program any remote buttons through the UI.

[kostaman]

How do you change remote control in OpenElec ? Simply adding the correct remote.conf to /Configfiles/rc_keymaps does not and has never worked for me....

I believe you are not putting the remote.conf file in the root of the Configfiles. Do not put it in the rc_keymaps. Re-Boot after you put the file in. Then it should work.

[pigbait]

For all of you getting issues with booting 6.0.1.2, here's a build to test: http://s805.eu/test/6.0.1.3-devel-20160219/

Changelog:

• reverted device trees to those used in 6.0.1.1 and prior
• m201C_1G and m201C_512M device trees in HD18Q build replaced with what I found on Baidu

Guest This should also fix your S/PDIF issue.

no dice on my device went from 6.0.1.1 to 6.0.1.3 and just stuck at MXQ logo. i will try and send you a twrp copy of the original firmware. thanks for all your tine and help