[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[kostaman]

Update or clean install ?
Using: 6.0.3.5 / OpenELEC-Amlogic.MXQ.arm-6.0.3.5
Did this fix a remote issue for you ? or just a suggestion ?

Thanks

Clean install. These boxes have 2 different remotes. You have flashed the version i use even though my box is the all black version as well.
Just flash clean install of HD18Q. See link post.

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/23766-rom-unofficial-openelec-for-mk808b-and-mxq?p=557788#post557788

[michaelchen]

God day all
Just felt like sharing
Kszaq u made it possible for me to move ahead with something I had in mind for a long time.
I think it's all most 13 years that I was subscribed to a cable company, and 2 months ago I told them good by.
Was paying them 58$ per month , comming to think about it it sums up to a lot of $.
Now I spent
32$ black mxq box
18$ dvb-t2 usb stick
2$ pc remote control
And now I can watch tv channels for free with no buffering issues thanks to the dvb-t2 I baut, hated iptv, was working purrly.
Tv sieries and movies for free
And it's all possible because of your great work on this openelec build.
Wanted to say all works great and thx allot.
Where ever u R may God bless U.

[PatrickJB]

Codesnakes rewrite of the amcodec is what I'm waiting for. Most people won't notice the odd judder and more often micro judder but apparently this is a know issue. Kodi's refresh-rate switching was a great leap forward and together with the 23p problem being sorted these boxes are pretty good.

I got a crappy 'WD TV Media Player' from a charity shop the other day for £4 (£79 on Amazon!!!) and playback of H264 files is really good, in fact much better than the MXQ, but I think this is because it has a dedicated decoder chip! And for the record, no the WD box can't play H265 and it is a slow crappy box, but for £4!

[sonofdibnah]

God day all
Just felt like sharing
Kszaq u made it possible for me to move ahead with something I had in mind for a long time.
I think it's all most 13 years that I was subscribed to a cable company, and 2 months ago I told them good by.
Was paying them 58$ per month , comming to think about it it sums up to a lot of $.
Now I spent
32$ black mxq box
18$ dvb-t2 usb stick
2$ pc remote control
And now I can watch tv channels for free with no buffering issues thanks to the dvb-t2 I baut, hated iptv, was working purrly.
Tv sieries and movies for free
And it's all possible because of your great work on this openelec build.
Wanted to say all works great and thx allot.
Where ever u R may God bless U.

Why not buy him a beer to say thank you in a tangible way?. Page 1 of this forum tells you how.

[michaelchen]

Why not buy him a beer to say thank you in a tangible way?. Page 1 of this forum tells you how.

Will do so as he comes back

[michaelchen]

Hello friends
short question
Are any of you having or using a dvb-t/t2/c usb stick (astrometa) ???
its recognized by the openelec as RTL2832 (dvb-t) only, but the stick works fine on my pc as a dvb-c as well.
so its a driver issue only, as i understand it, has any 1 tried it ?
it works very well with TVH, but i want to use the dvb-c capabilities as well.
serched the web for that but found little info.
any help b more than wellcome.

[kostaman]

I am running OpenELEC 6.95.1.1 MXQ ARM (Nand) on all black MXQ. My Board am_mxq_a 20150825.
Best OpenElec version for this box so far.
It has never hung or froze during normal operating.

I can report a BUG when performing restore from previous backup. I have had 3 instances of the Box Freezing
during the restore whilst the copying of the files is in progress. It happens at no particular % of files copied or any particular file.
It is stuck at a file and that is it. Wont move any further and remote control is in operative. Cannot even hit cancel.
Have to un plug device and re power. Perform the restore again and it works.

Just putting it out there.

[smilez]

God day all
Just felt like sharing
Kszaq u made it possible for me to move ahead with something I had in mind for a long time.
I think it's all most 13 years that I was subscribed to a cable company, and 2 months ago I told them good by.
Was paying them 58$ per month , comming to think about it it sums up to a lot of $.
Now I spent
32$ black mxq box
18$ dvb-t2 usb stick
2$ pc remote control
And now I can watch tv channels for free with no buffering issues thanks to the dvb-t2 I baut, hated iptv, was working purrly.
Tv sieries and movies for free
And it's all possible because of your great work on this openelec build.
Wanted to say all works great and thx allot.
Where ever u R may God bless U.

I just read your post never herd of dvb-t2 until now. Does that pick up satellite signal from other country? And which do u have? Is there a add on for it??

[smilez]

Hi,

My remote stops working on the MXQ s805 ott box (all black)
Running 6.0.3.5 on NAND MXQ s805 ott box (all black)
Copy remote.conf to \Configfiles\ and reboot, now the remote works perfect
When I unplug the powercable for lets say 1 minute and plug power back in
When back In openelec the remote doesn't work anymore
Why ?
To fix this I have to remove remote.conf and reboot, copy remote.conf back to \Configfiles\ and reboot
Now the remote works again
But when I unplug the power cable again, the remote stops working

Hope someone can help me out here to fix this issue
Thanks

Are u doing this with a computer? I just understood how to update with tar. But never done it. There a set of remote that doesn't work on these boxes. I mention this problem couple of post back.

[michaelchen]

I just read your post never herd of dvb-t2 until now. Does that pick up satellite signal from other country? And which do u have? Is there a add on for it??

dvb-t/t2 are for local broadcasting not satellite , i have astrometa dvb-t/t2/c+dab+fm usb stick.
it works as dvb-t and dvb-c(cable)(on pc), as mentiond before the mxq reconized it as dvb-t and not dvb-c!!!!
im using tvheadend.
followed this

[kostaman]

Hi,

My remote stops working on the MXQ s805 ott box (all black)
Running 6.0.3.5 on NAND MXQ s805 ott box (all black)
Copy remote.conf to \Configfiles\ and reboot, now the remote works perfect
When I unplug the powercable for lets say 1 minute and plug power back in
When back In openelec the remote doesn't work anymore
Why ?
To fix this I have to remove remote.conf and reboot, copy remote.conf back to \Configfiles\ and reboot
Now the remote works again
But when I unplug the power cable again, the remote stops working

Hope someone can help me out here to fix this issue
Thanks

Hi again
I do remember you posted this problem and i replied with advice on the version you have flashed.
You have flashed OpenELEC-Amlogic.MXQ.arm-6.0.3.5 and you have the All Black MXQ.
You have flashed the wrong version. You should have flashed the HD18Q version.
I have an all black MXQ and use the MXQ arm version but i have a different remote to you.

You have to do a clean install.

I hope you understand what i am saying.

[kszaq]

I'm back! Thank you for all good words and for helping each other in this thread!

I'll answer some questions, then 8 hours of work (the one that I get paid for ) and back to developing!

Hi just a quick one
K dose it support astrometa dvb-t2 usb stick?
Just got it right now.

DVB-T support is a tricky one. You should look up your stick on LinuxTV Wiki before purchasing. If it's supported in <=3.10, it should work. If in <=3.16, it might work. In other cases expect it not to work.

Considering how K. has made things more and more "simple", starting from .uenv and aml.autoscript, which were also known techniques ( but implemented widely by nobody until K. started), I want to point out that in Amlinux for S905 we now have a .dtb image file which can be switched to adapt different ram/rom and chipset configuration within certain limits, to a fixed OE Release! I do not know at all if this could also be done in the ( vast really ) builds that K. maintains , but I see all this as a real turn towards a certain multiSoc scalability and an easier approach to compile a Sw, which in the end can be adapted to different devices. Modularity? Or I am getting it wrong and this is possible only with Amlogic processors architecture? Btw, I am thinking philosophy, because I can't think in the programming way!
Regards
Wonderful work, kudos kszaq !
Alessandro

One kind of headache gone but we'll have others! I tried to achieve loading device tree from somewhere else in my ROM but for S805 devices that would cause more trouble than it's worth. I'm happy to see S905 devices having separate flash space for device tree but I think that we won't achieve multi-SoC builds, rather a single build for many S905 devices out there.

I also flashed another bootloader and now even my led is turning colors. This wasn't even working with the original stock rom!! Not sure how they develop this software in the factory but looks like some binaries were reused or something. Only funny thing is that the led doesn't go off, it changes to red once I suspend and stays red next time I resume.

kszaq any idea if this led issue is something linux or uboot related? I guess it's a combination as the rom is the same but now it turns red due to different uboot. Also really nice that wifi works when resuming the system now!! It's fully functional and I'm a happy camper now.

There is a kernel driver that can switch LED colours but only if GPIO pins for LED are defined in device tree. At the moment I define them in MK808B+ and MXQ builds since these devices are always the same. In HD18Q builds power LED management is not in place because of many boards on the market. If you look into u-boot source code (example), you'll see that for "costdown" m201 boards - which most of available S805 devices today are - power LED should be managed by u-boot.

Kszaq, it would be awesome if you could add the RTL8188 wifi driver again to the HD18Q build.

It's there all the time: https://github.com/kszaq/OpenELEC.tv...arm.conf#L1074
Is it not working for you?

Kszaq,

Thanks for your hard work

Just an observation/question to the latest MXQ 6.0.3.5. version NAND. I have a Beelink "red" MXQ which had 6.0.3.2. on it. I updated my box with tar files from the original zip version of 5.0.8.20. Everytime the Kodi "Power off system" worked and the LED on the box changed from blue to red.

Now I updated the box to 6.0.3.5. version using tar file, and now when I "power off system" the LED is not changing, but looks like the box powers off. If I use "Suspend" instead of "Power off system" the LED changes from blue to red.

Can you pleae look into it. Otherwise the version looks good to me.

Thanks, Arpad

I agree that power LED is not working properly for power off. I'll try to fix that for the next build.

Hi,

My remote stops working on the MXQ s805 ott box (all black)
Running 6.0.3.5 on NAND MXQ s805 ott box (all black)
Copy remote.conf to \Configfiles\ and reboot, now the remote works perfect
When I unplug the powercable for lets say 1 minute and plug power back in
When back In openelec the remote doesn't work anymore
Why ?
To fix this I have to remove remote.conf and reboot, copy remote.conf back to \Configfiles\ and reboot
Now the remote works again
But when I unplug the power cable again, the remote stops working

Hope someone can help me out here to fix this issue
Thanks

That's odd, I'll look into it.

Codesnakes rewrite of the amcodec is what I'm waiting for. Most people won't notice the odd judder and more often micro judder but apparently this is a know issue. Kodi's refresh-rate switching was a great leap forward and together with the 23p problem being sorted these boxes are pretty good.

I got a crappy 'WD TV Media Player' from a charity shop the other day for £4 (£79 on Amazon!!!) and playback of H264 files is really good, in fact much better than the MXQ, but I think this is because it has a dedicated decoder chip! And for the record, no the WD box can't play H265 and it is a slow crappy box, but for £4!

Codesnake's new decoder is still a WIP and not ready to use: https://github.com/xbmc/xbmc/pull/9432
For stutter/judder, I recently got some tips from Sam Nazarko @ OSMC that may help in resolving that a little. I'll post a test build with Sam's suggestions later today for you to test.

I am running OpenELEC 6.95.1.1 MXQ ARM (Nand) on all black MXQ. My Board am_mxq_a 20150825.
Best OpenElec version for this box so far.
It has never hung or froze during normal operating.

I can report a BUG when performing restore from previous backup. I have had 3 instances of the Box Freezing
during the restore whilst the copying of the files is in progress. It happens at no particular % of files copied or any particular file.
It is stuck at a file and that is it. Wont move any further and remote control is in operative. Cannot even hit cancel.
Have to un plug device and re power. Perform the restore again and it works.

Just putting it out there.

Can you connect over SSH when it freezes? If yes, that may be a Kodi/OpenELEC upstream bug.

[kostaman]

I'm back! Thank you for all good words and for helping each other in this thread!

I'll answer some questions, then 8 hours of work (the one that I get paid for ) and back to developing!


DVB-T support is a tricky one. You should look up your stick on LinuxTV Wiki before purchasing. If it's supported in <=3.10, it should work. If in <=3.16, it might work. In other cases expect it not to work.


One kind of headache gone but we'll have others! I tried to achieve loading device tree from somewhere else in my ROM but for S805 devices that would cause more trouble than it's worth. I'm happy to see S905 devices having separate flash space for device tree but I think that we won't achieve multi-SoC builds, rather a single build for many S905 devices out there.


There is a kernel driver that can switch LED colours but only if GPIO pins for LED are defined in device tree. At the moment I define them in MK808B+ and MXQ builds since these devices are always the same. In HD18Q builds power LED management is not in place because of many boards on the market. If you look into u-boot source code (example), you'll see that for "costdown" m201 boards - which most of available S805 devices today are - power LED should be managed by u-boot.


It's there all the time: https://github.com/kszaq/OpenELEC.tv...arm.conf#L1074
Is it not working for you?


I agree that power LED is not working properly for power off. I'll try to fix that for the next build.


That's odd, I'll look into it.


Codesnake's new decoder is still a WIP and not ready to use: https://github.com/xbmc/xbmc/pull/9432
For stutter/judder, I recently got some tips from Sam Nazarko @ OSMC that may help in resolving that a little. I'll post a test build with Sam's suggestions later today for you to test.


Can you connect over SSH when it freezes? If yes, that may be a Kodi/OpenELEC upstream bug.

No i could not connect over SSH (connect to host 192.168.1.4 port 22: Operation timed out) or SMB .

After i un plug and re plug in the box It is as if the restore successfully happened. Checking file ok etc. It then re boots but the backup is not complete it is an incomplete backup.
the build is partially built working it is all over the place.

I took logs before and after attached .

[michaelchen]

I'm back! Thank you for all good words and for helping each other in this thread!

I'll answer some questions, then 8 hours of work (the one that I get paid for ) and back to developing!


DVB-T support is a tricky one. You should look up your stick on LinuxTV Wiki before purchasing. If it's supported in <=3.10, it should work. If in <=3.16, it might work. In other cases expect it not to work.


One kind of headache gone but we'll have others! I tried to achieve loading device tree from somewhere else in my ROM but for S805 devices that would cause more trouble than it's worth. I'm happy to see S905 devices having separate flash space for device tree but I think that we won't achieve multi-SoC builds, rather a single build for many S905 devices out there.


There is a kernel driver that can switch LED colours but only if GPIO pins for LED are defined in device tree. At the moment I define them in MK808B+ and MXQ builds since these devices are always the same. In HD18Q builds power LED management is not in place because of many boards on the market. If you look into u-boot source code (example), you'll see that for "costdown" m201 boards - which most of available S805 devices today are - power LED should be managed by u-boot.


It's there all the time: https://github.com/kszaq/OpenELEC.tv...arm.conf#L1074
Is it not working for you?


I agree that power LED is not working properly for power off. I'll try to fix that for the next build.


That's odd, I'll look into it.


Codesnake's new decoder is still a WIP and not ready to use: https://github.com/xbmc/xbmc/pull/9432
For stutter/judder, I recently got some tips from Sam Nazarko @ OSMC that may help in resolving that a little. I'll post a test build with Sam's suggestions later today for you to test.


Can you connect over SSH when it freezes? If yes, that may be a Kodi/OpenELEC upstream bug.

Wellcome back
i followed the link and yes it is supported since 3.13.
im using hts tvheadend + openelec tvh addon and i mannaged to setup the channeles ok, the only problem is that i dont have the possibility to define a dvb-c network since the stick is recognized only as a dvb-t device.
a stupid question, does it matter which addon i use? the driver is inside the OE right?

[kszaq]

No i could not connect over SSH (connect to host 192.168.1.4 port 22: Operation timed out) or SMB .

After i un plug and re plug in the box It is as if the restore successfully happened. Checking file ok etc. It then re boots but the backup is not complete it is an incomplete backup.
the build is partially built working it is all over the place.

I took logs before and after attached .

Have you tried leaving the device on for a few minutes after it freezes? I remember having a device freeze once, after a few minutes my device unfroze and restored fully.

Wellcome back
i followed the link and yes it is supported since 3.13.
im using hts tvheadend + openelec tvh addon and i mannaged to setup the channeles ok, the only problem is that i dont have the possibility to define a dvb-c network since the stick is recognized only as a dvb-t device.
a stupid question, does it matter which addon i use? the driver is inside the OE right?

LinuxTV Wiki says that only DVB-T is supported for this tuner: http://linuxtv.org/wiki/index.php/DVB-C_USB_Devices
It does not matter which addon you use, driver is in kernel.