[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[kszaq]

With the hotplug governator my device almost the time uses only one cpu core and gets 40 or more degres ( i have coler in the device just for it ) and if i use de ondemand governator it uses all cores and the device is at 20 or 25 degrees.
And the percentage of use of the all cores with the ondemand is almost 20% and the hotplug governator is almost 60% or more
That's i said it work more efficiently and it doesn't spend mutch more energy by that.

Pajopasa, I measured power consumption again yesterday and it turned out that there is no difference between hotplug and ondemand (or my cheap Chinese meter is wrong ). Considering your observations I decided to make ondemand the default governor for my next releases. Thanks for your input!

[envagyok]

Hi kszaq,

Unfortunately at 5.0.8 i cannot reach the tvheadend server port at 9981 for web configuring.
Before at 5.0.7. it worked, Aftern.0.8. i try reinstall, delete, disable, enable the tvheadend server addon without succes.
Then i revert to 5.0.7., and worked again the web interface.

[kszaq]

Hi kszaq,

Unfortunately at 5.0.8 i cannot reach the tvheadend server port at 9981 for web configuring.
Before at 5.0.7. it worked, Aftern.0.8. i try reinstall, delete, disable, enable the tvheadend server addon without succes.
Then i revert to 5.0.7., and worked again the web interface.

I am afraid I won't be able to help you - there were no changes that could prevent tvheadend from running: https://github.com/kszaq/OpenELEC.tv....7p1...5.0.8p1

Can you provide a log?

[envagyok]

Its strange..
I try again (now with desktop pc and wired ethernet, before wifi and laptop) and working again..
Sorry for post

[jackmate]

You can probably fix this by flashing a bootloader meant for your device. Here's how to do it:

1. Download a zip release from GitHub page.
2. Unpack it to a SD card.
3. Delete factory_update_param.aml and recovery.img files.
4. Grab a bootloader.img from your Android firmware and put it into the OpenELEC-Amlogic.MXQ.arm-5.0.x-update.zip file (overwrite existing bootloader.img).
5. Download TWRP recovery and copy it to your SD card. Rename it to recovery.img.
6. Boot using a toothpick and flash your modified zip. Do not "root" the firmware.

After this you may update using tar files and the bootloader will persist until next toothpick-flash.


It should boot much faster unless there are file system check operations being performed for some reason. Did previous builds work for you?

This is new device 1st time using it ,I have flashed 5.0.8 latest one ,is there a particular old build I should try for faster startup?
It's more than 2 minutes now to start into KODI . Another issue is openelec setting has left text missing like in pics ,using confluence custom skin.

[Compos]

@jackmate
Is yours the all black model with the MXQ logo on the top? I have the long boot up time with this model but once you swap the bootloader you can just put the unit into standby and it will wake up in seconds. I don't have the missing text problem. Does this just happen on your custom skin? I use Aeon Nox without any problems.

[jackmate]

@jackmate
Is yours the all black model with the MXQ logo on the top? I have the long boot up time with this model but once you swap the bootloader you can just put the unit into standby and it will wake up in seconds. I don't have the missing text problem. Does this just happen on your custom skin? I use Aeon Nox without any problems.

No ,I got Mxq with buttom on top

Which bootloader do I swap in the firmware ,I would like to try that Pls.
Missing text is on confluence custom skin ,in default confluence skin it's fine .

[kszaq]

No ,I got Mxq with buttom on top

Which bootloader do I swap in the firmware ,I would like to try that Pls.
Missing text is on confluence custom skin ,in default confluence skin it's fine .

Your box looks like Beelink MXQ but it might be yet another clone... can you post a dmesg here so that we may see if something wrong is going on?

[jackmate]

Your box looks like Beelink MXQ but it might be yet another clone... can you post a dmesg here so that we may see if something wrong is going on?

here is dmesg:
the kodi shows in screen almost after 4-5 minutes.openelec splash screen appears during this time.
The seller tells me its orignial beelink mxq.

http://sprunge.us/AVXg

[kszaq]

here is dmesg:
the kodi shows in screen almost after 4-5 minutes.openelec splash screen appears during this time.
The seller tells me its orignial beelink mxq.
http://sprunge.us/AVXg

There are a lot of messages like this one:

[COLOR=#000000][0m[aml_sdio_timeout] emmc: cmd0, ISR have been run, xfer_step=2, time_start_cnt=499mS, timeout_cnt=2[/COLOR]

in your dmesg. This may tell that the driver doesn't work well with your emmc, that it is faulty or that you have a next generation device with no emmc (= I have no idea ).

Can you try flashing factory image via USB Burning Tool (use 107k4, as previously requested) and see if the problem persists with Android?

[MeleTest]

Hi kszaq,

Unfortunately at 5.0.8 i cannot reach the tvheadend server port at 9981 for web configuring.
Before at 5.0.7. it worked, Aftern.0.8. i try reinstall, delete, disable, enable the tvheadend server addon without succes.
Then i revert to 5.0.7., and worked again the web interface.

Hi envagyok,
I have the same problem as you : kodi HTS client can't rich thveadend server. In my case, sure this have relation with my USB TNT dongle, because when I take it off and reboot, evereything goes right as with the 5.0.7.
Here follows the dmesg log file relative to this part:

[jackmate]

There are a lot of messages like this one:

[COLOR=#000000][0m[aml_sdio_timeout] emmc: cmd0, ISR have been run, xfer_step=2, time_start_cnt=499mS, timeout_cnt=2[/COLOR]

in your dmesg. This may tell that the driver doesn't work well with your emmc, that it is faulty or that you have a next generation device with no emmc (= I have no idea ).

Can you try flashing factory image via USB Burning Tool (use 107k4, as previously requested) and see if the problem persists with Android?

From OpenELEC I flashed android fw using SD card this image
And works fine as expected .boots android in 20 seconds .
It's only when I flash openelec ,takes 4 min to bring KODI on screen .

http://www.mediafire.com/download/wb...0_20141231.rar (password: geekbuying.com)

[jackmate]

There are a lot of messages like this one:

[COLOR=#000000][0m[aml_sdio_timeout] emmc: cmd0, ISR have been run, xfer_step=2, time_start_cnt=499mS, timeout_cnt=2[/COLOR]

in your dmesg. This may tell that the driver doesn't work well with your emmc, that it is faulty or that you have a next generation device with no emmc (= I have no idea ).

Can you try flashing factory image via USB Burning Tool (use 107k4, as previously requested) and see if the problem persists with Android?

The seller tells me it's beelink box ,beelink recently started changed flash to Emmc instead of nand flash .
I bought this device for purely using ur openelec build ,not interested in slow android .
What option do I have to boot kodi faster in this ,it's takes 4-5 min to bring kodi on screen right now .

[kszaq]

Hi envagyok,
I have the same problem as you : kodi HTS client can't rich thveadend server. In my case, sure this have relation with my USB TNT dongle, because when I take it off and reboot, evereything goes right as with the 5.0.7.
Here follows the dmesg log file relative to this part:

It seems like this patch: https://github.com/kszaq/OpenELEC.tv...d1b3827d1e7831 broke media_build drivers. I would need to find a way to make it work for both you using DVB tuners and people needing a working LIRC. I will revert this patch in the next release

The seller tells me it's beelink box ,beelink recently started changed flash to Emmc instead of nand flash .
I bought this device for purely using ur openelec build ,not interested in slow android .
What option do I have to boot kodi faster in this ,it's takes 4-5 min to bring kodi on screen right now .

Have you tried flashing back OpenELEC after flashing Android?

[jackmate]

It seems like this patch: https://github.com/kszaq/OpenELEC.tv...d1b3827d1e7831 broke media_build drivers. I would need to find a way to make it work for both you using DVB tuners and people needing a working LIRC. I will revert this patch in the next release


Have you tried flashing back OpenELEC after flashing Android?

Yes did that ,I flashed the android build u suggested ,android works and boots normal .then I flash openelec ,same issues ,get openelc splash screen and after 4-5 min ,get kodi screen .