[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[sonofdibnah]

Thanks for the latest 6.0.0.2 version. It's working well for me though I nearly reported a problem to you in error. I reinstalled android firmware to reset the bootloader and then your SD version on my mxq red. I discovered you have to create a backup to see the folder via file manager. I copied my backup to that folder and then chose the wrong one to restore 3 times, each time restoring to where I already was!

What a plonker.

There is an older 109k android firmware with the correct permissions for HD video and refresh rate switching available thro mbox.co.za forum if anyone is interested. The 110k and, I think 111k, versions still don't have these and it's a real pain to correct for this using init-d.

Sorry for slipping off topic but I thought it to be connected, unlike some of the "I've bought this, will this work?" posts I've read here.

[Pravsovet]

Pravsovet In 6.0.0.2 default CPU governor is interactive and not ondemand. You can tell if it's working in Kodi System Info page or by displaying debugging information during playback ('o' on a keyboard). I may have to look into the update issue. Were you trying to update NAND or SD version?

I've trying update Openelec with Amlogic.HD18Q .tar file. I put the file in the folder Update. In this case Kodi is not working, only Openelec loading.
NAND version work. I see CPU load. 15% 3% 14% 0%. I don't know - Is it interactive?

[wilro_6276]

Friends, I have some good news, mainly for HD18Q owners: thanks to an idea from gcsuri I was able to successfully boot OpenELEC from and SD card without modifying bootloader. This means no more bricked boxes! This also means less issues with remote control: if powering on works with factory firmware, it'll also work after installing my OpenELEC builds. I will compile 6.0.0.1 (= old kernel, working Ethernet) very soon and post it so that everybody can flash OpenELEC without fearing of bricking their boxes. Of course I'll also push the script to my repo so that everyone can use it.

Well done!! I've been able to use this bootenv tweak to get dual boot for my MX3G box (Should be compatible with all S805/S812's, I suspect

[PatrickJB]

Just for the record my board is: AM_MXQ_A 20150825 with probably the Realtek RTL8189 wifi chip, can't read chip ID even with glasses!

I'm running the MXQ version 6.0.0.2 (nand install via toothpick method) of K's build everything OK except wifi connects but doesn't work, using Ethernet dongle as workaround.


Here's a link to the MXQ clones thread with a factory download of the standard AM_MXQ_A 20150825 ROM although I don't think it can be installed via toothpick method and we've all gone OpenElec anyway. The ROM may contain a fix for wifi although I'm not that techie!

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s805/others-ab/540512-mxq-all-black-s805-versions-hd18q-and-clones-directory?p=550784#post550784

[mylle]

How about red stripe MXQ? Is there a fix for that one yet?

Edit: I tried the updated build and it worked!

[jed]

jed The 8189es.ko module is already built in - that's why you can connect over WiFi. I don't know why there is no traffic. I ordered a HD18Q a few days ago and if it comes with Relatek WiFi, I might be able to fix that issue.

kszaq That would be brilliant - note that the more recent "HD18Q"s work better on MXQ build than on HD18Q build due to using the newer/better remote as has been documented before. I wonder though, whether the WiFi issue has anything to do with the GPIO like you said the LED did. I have extracted the GPIO info from the stock Android for this box as is as follows, which, as you can see, differs from the extraction using your OpenElec. Thank you.

ANDROID
root@mxq:/ # cat /sys/kernel/debug/gpio
GPIOs 0-138:
gpio-49 (amlsd ) in hi
gpio-86 (gpio_key ) in hi
gpio-107 (sdio_wifi ) out hi
gpio-117 (bt_rfkill ) out lo
gpio-137 (mute_spk ) out lo
gpio-138 (wifi_power ) out hi

root@mxq:/ # uname -r
3.10.33

OpenELEC:~ # cat /sys/kernel/debug/gpio
GPIOs 0-138:
gpio-1 (power_led ) out hi
gpio-3 (gpio_key ) in hi
gpio-6 (sdio_wifi ) out hi
gpio-49 (amlsd ) in hi
gpio-75 (bluetooth ) in lo
gpio-107 (sdio_wifi ) out hi
gpio-108 (sdio_wifi ) out hi
gpio-117 (bt_rfkill ) out hi
gpio-118 (sdio_wifi ) in hi
gpio-137 (mute_spk ) out lo

[jed]

Just for the record my board is: AM_MXQ_A 20150825 with probably the Realtek RTL8189 wifi chip, can't read chip ID even with glasses!

Yes same board as me, yes it has RTL8189ETV chip which uses 8189es.ko module. As far as I know this is what is shipping now for the all black MXQ boxes unless you get "old stock" or there's something even newer, its constantly changing.

[PatrickJB]

Yes same board as me, yes it has RTL8189ETV chip which uses 8189es.ko module. As far as I know this is what is shipping now for the all black MXQ boxes unless you get "old stock" or there's something even newer, its constantly changing.

So does your wifi work? Just be tidy to have it working instead of having to use a dongle. Mine worked OK when I was running the Android factory build then I decided I couldn't live with the 23p frame rate judder! And of course OpenE is simply better except no browser but we've all got laptops / tablets so it no problem there.

[jed]

So does your wifi work? Just be tidy to have it working instead of having to use a dongle. Mine worked OK when I was running the Android factory build then I decided I couldn't live with the 23p frame rate judder! And of course OpenE is simply better except no browser but we've all got laptops / tablets so it no problem there.

No, as I've been dialoging with kszaq in this thread, it pretends its going to work, it connects but then nothing happens/no traffic. LED not working either, it just stays blue even when off. Remote working on MXQ build but not on HD18Q build.

[PatrickJB]

No, as I've been dialoging with kszaq in this thread, it pretends its going to work, it connects but then nothing happens/no traffic. LED not working either, it just stays blue even when off. Remote working on MXQ build but not on HD18Q build.

Yes same as me, the LED is so bright that when I took the box apart to check the board today I placed a piece of black tape inside the box to hide it!

While I'm at it I wonder if K could do something to power off the usb ports when the box is powered off / in standby? I only ask as I have three 128GB SanDisk Ultra Fit USB memory sticks in my box and they get really hot, which I was aware of when I purchased them, so it would be good for them to get a chill out period (LOL) when the box is off. My box often stays on even when I switch the TV off, seems to have a mind of it's own!

[jed]

Yes same as me, the LED is so bright that when I took the box apart to check the board today I placed a piece of black tape inside the box to hide it!

While I'm at it I wonder if K could do something to power off the usb ports when the box is powered off / in standby? I only ask as I have three 128GB SanDisk Ultra Fit USB memory sticks in my box and they get really hot, which I was aware of when I purchased them, so it would be good for them to get a chill out period (LOL) when the box is off. My box often stays on even when I switch the TV off, seems to have a mind of it's own!

I think the kszaq build does not power off this particular board. It just puts it to displayoff/standby. The only build that I had luck with it actually powering off the box was one by "therealjohngalt" further back in this thread - the MXQ version I think dated 27/11/2015. And just noticed that the kszaq build when the box goes to standby the light stays blue but when it comes back from standby the light is dim red so it looks as if its working the LED but the wrong way round. Also the kszaq build seems to increment the IP address with each powerup, which didn't happen with "therealjohngalt" build.

[PatrickJB]

I think the kszaq build does not power off this particular board. It just puts it to displayoff/standby. The only build that I had luck with it actually powering off the box was one by "therealjohngalt" further back in this thread - the MXQ version I think dated 27/11/2015. And just noticed that the kszaq build when the box goes to standby the light stays blue but when it comes back from standby the light is dim red so it looks as if its working the LED but the wrong way round. Also the kszaq build seems to increment the IP address with each powerup, which didn't happen with "therealjohngalt" build.

Hmm not techie, as I often mention, but it does seem more than standby as the old Android ROM did have proper standby functionality i.e. It would come out of standby in a second or two and be ready to use whereas K's build does reboot as if just plugged in.

Unfortunately most people won't be bothered about it not powering down but obviously there are a few of us that will have USB sticks plugged in and in my case they run hot which probably isn't doing them any good in the long term. Hopefully it's on K's' to-do-list' but I'm not expecting it to be as there are more important issues to resolve as well as him doing his regular job and having some R&R.

[goofball]

Stutter appears to be gone with the 6.0.0.2 update on mk808b+ running from NAND. Thanks!

[jed]

Hmm not techie, as I often mention, but it does seem more than standby as the old Android ROM did have proper standby functionality i.e. It would come out of standby in a second or two and be ready to use whereas K's build does reboot as if just plugged in.

All I can state is my experience. Perhaps yours is different. I am starting to think that how the box was flashed and what was there before has some bearing on how the final result ends up. Perhaps ours have ended up differently, depending how we got 6.0.0.2 into the box (NAND Flash or Upgrade or SD flash or upgrade).

[PatrickJB]

All I can state is my experience. Perhaps yours is different. I am starting to think that how the box was flashed and what was there before has some bearing on how the final result ends up. Perhaps ours have ended up differently, depending how we got 6.0.0.2 into the box (NAND Flash or Upgrade or SD flash or upgrade).

Yes I agree with that. The only info I can give is that I did update the bootloader recently(think it was the MXQ 6.0.01 version) via SD/toothpick and I'm on OpenE MXQ 6.0.0.2 again SD/toothpick.Oh and I used the Nand versions, I think!! LOL The power, LED etc has all been the same since I first moved to OpenE.

I don't know if there are certain code remnants left from my other endeavours. Obviously something is still active, and has to be, to allow the remote to boot the box but I'm hoping that the USB power can be suspended when the box automatically turns off when the TV is switched off! Hopefully that makes sense? Would be great to have a true suspend option, with the usb ports powered down.