[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[kszaq]

Awesome! May I ask if Elonics e4000 tuner driver will be included?

kkm I'll include drivers from kernel and not media_build for this tuner to hopefully get rid of unknown symbol errors.

[kszaq]

Update uploaded. I'm not happy with the way power down works, I'm waiting to get some information on how to do it properly from Nexteon.

Changelog:

• re-added Kodi audio patches to hopefully fix audio drops experienced by some users
• added Kodi patches from Koying to improve SD video playback and fix occasional decoder deadlocks
• added "Reboot from NAND" option to Confluence skin
• added a possibility to either power off or suspend the box
• fixed u-boot logo not showing after bootloader update
• fixed HD18Q SD build to include all necessary files
• excluded media_build drivers from build (temporarily?) to fix DVB module errors

Remember to update bootloader for SD card installations.

More information and download links at https://github.com/kszaq/OpenELEC.tv...s/tag/5.0.8.17

[kkm]

Thank you for the update. I have mixed results to report:

- the new bootloader now displays the original "Google TV" logo
- toothpick recovery method works again
- e4000 tuner is properly detected, but DVB-T reception is defective

Here is the RTL2832/e4000 TV stick on MK where only one mux barely works (pixelated and freezing):


Tvheadend log: http://pastebin.com/p6qf9GiN


And the same TV stick on a PC with OpenELEC-Generic.i386-5.0.8 with all muxes OK and perfect TV reception:



Tvheadend log: http://pastebin.com/5YGZ7yFt

Please help.

[djdean1]

I just flashed the latest build for hd18q 5.0.8.17. everything works except the wifi/bluetooth, not too fussed about the bluetooth but would love to get the wifi working. i went through my original boxes firmware to see what drivers it used and found these 8188eu.ko 8192cu.ko . not sure why it wont boot the wifi

[kszaq]

Thank you for the update. I have mixed results to report:

- the new bootloader now displays the original "Google TV" logo
- toothpick recovery method works again
- e4000 tuner is properly detected, but DVB-T reception is defective

Here is the RTL2832/e4000 TV stick on MK where only one mux barely works (pixelated and freezing):

[ATTACH]n510409[/ATTACH]
Tvheadend log: http://pastebin.com/p6qf9GiN


And the same TV stick on a PC with OpenELEC-Generic.i386-5.0.8 with all muxes OK and perfect TV reception:

[ATTACH]n510410[/ATTACH]

Tvheadend log: http://pastebin.com/5YGZ7yFt

Please help.

kkm First of all, we can't compare i386 OpenELEC with this ROM as we use an older kernel and there is no way to update it unless Amlogic posts a newer one/someone ports it (the latter is very unlikely). Secondly, I have some bad news: the USB driver for our devices has issues with some devices, DVB tuners among others. Some work well, some don't. It seems like your tuner won't work at the moment, just as my IT9135 tuner doesn't.

The solution? Wait for updated kernel driver or try to port RPi fixes - I failed to do that, maybe I'll try again at some point. You can read about it more on Odroid forum, Odroid-C1 uses the same SoC and kernel: http://forum.odroid.com/viewtopic.php?f=112&t=8106

I just flashed the latest build for hd18q 5.0.8.17. everything works except the wifi/bluetooth, not too fussed about the bluetooth but would love to get the wifi working. i went through my original boxes firmware to see what drivers it used and found these 8188eu.ko 8192cu.ko . not sure why it wont boot the wifi

djdean1 These drivers are included but I now noticed that despite being selected the 8192cu module is not there... I'll try to solve it.

[djdean1]

No problem man need me to test anything let me know

[kkm]

It seems like your tuner won't work at the moment, just as my IT9135 tuner doesn't.

I was going to get IT9135 -

IT9135 DVB-T tuner works very well with a fresh install of OpenELEC 5.0.8 (p15) 5.0.8-20150610... the tuner is great with zero problems. It's detected as a AF9033.

but if it does not work for you then I see no alternatives.

The Odroid C1 link is invalid. Did you check the May Amlogic release? Maybe it's a newer kernel?

[kszaq]

No problem man need me to test anything let me know

djdean1 I found the reason why the modules were not compiled in. Please try flashing this update: http://s805.eu/test/OpenELEC-Amlogic...17.wififix.tar

I was going to get IT9135 - but if it does not work for you then I see no alternatives.

kkm There are a few versions of IT9135 on the market and some may work, some may not.

The Odroid C1 link is invalid.

I have corrected the link.

Did you check the May Amlogic release? Maybe it's a newer kernel?

Unfortunately I don't have access to Amlogic's GIT server, I rely solely on open source code they release from time to time.

[djdean1]

djdean1 I found the reason why the modules were not compiled in. Please try flashing this update: http://s805.eu/test/OpenELEC-Amlogic...17.wififix.tar

Hi tried this update but wifi section is still missing from openelec configuration. I can upload the 8192cu.ko from my working android firmware if that helps.

[kszaq]

Hi tried this update but wifi section is still missing from openelec configuration. I can upload the 8192cu.ko from my working android firmware if that helps.

djdean1 Can you post a result of dmesg and lsmod? Does issuing a modprobe 8192cu command help?

[anemeth]

Kszaq,

Thanks for the update. Just one question. I have p8 installed, now if I update to p17, can I just use the tar file copying to Update directory, or I have to go the toothpick method and set up Openelec/Kodi again?

Thanks,

[djdean1]

Unfortunately modprobe command doesn't work. I have attached both logs. I have also attached the 8192cu file from my android image

[kszaq]

Unfortunately modprobe command doesn't work. I have attached both logs. I have also attached the 8192cu file from my android image

djdean1 1. What is the result of modprobe? Can you post dmesg after you issued modprobe 81922cu command?
2. Can you try modprobe wifi_dummy (+ dmesg) to check whether you have a SDIO WiFi chip?
3. There is no sign of Realtek WiFi in your dmesg. It is a USB-based device so it should be visible in dmesg. Are you sure that your device uses Realtek chip?

[djdean1]

According to the chip on the board after inspection it says RTL8188ETV, Seems it is the same as the 8188eu except it uses less power. I have attached the 8188eu.ko from my andorid aswell not sure whats different about it

[kkm]

I tried another TV stick from my collection, Abilis AS102, which I thought had no Linux support. It is not detected during booting but lsmod recognizes it after plugging in as dvb_as102. However tvheadend does not list it as a TV adapter. Would you be able to move it from media_build to the kernel drivers in the next release? Maybe this one will work.