[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[smilez]

A few tips then:

1. Try using different HDMI cable.
2. Check if the same happens on Android - this might be a hardware fault as noone reported that kind if issue before.
3. My builds are currently safe to flash and won't brick your device: there is no bootloader nor recovery to flash, replacing which may result in a brick. But in your case I think there is no point in trying another build if everything else works.
4. If you don't have that issue with Android and another cable, please do the following: turn on your box (when there's no sound), replug HDMI to make sound work and immediately after collect logs. You can read how to do this in first post.

I can't promise your issue will be resolved fast as I'm away from tomorrow.

when it was running straight android I've never had a sound issue. I've tried different hdmi and i was still having this problem. I've had this problem with an m8 to a while back after putting openelec. i will look into how to check change log and hope i don't lose my mind.

[michaelchen]

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

[PatrickJB]

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

K is away for a week so you may want to ask over at the Kodi forum.

[michaelchen]

K is away for a week so you may want to ask over at the Kodi forum.

Thx
And k......have fun where ever u R

[PatrickJB]

You could also ask for advice on this thread: http://freaktab.com/forum/tv-player-...-tv110-mx2-g18

[vn800art]

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

[jekkos]

Hello all,

I'm facing some weird problems with my AM_MXQ_A board (rlt 8189ETV chip). All was running wel with 6.0.1.2 and all of a sudden the board stopped booting. I attached a serial console and found that the bootup stalled after the bootloader started the kernel. As I didn't change anything I thought this was pretty weird and tried to reflash. Device boots up from sd after toothpick and flashes new version to nand. But after reboot it stalls at this line



I was able to reflash original stock android rom which does work!! But once I want to go back to OpenElec the board stalls on on this line. Anybody got any idea what could be wrong here? Maybe a hardware issues or bad flash block or something? So no problem to boot into recovery or into original Android ROM, it's just that none of kszzaq's (nand, sd) builds work any longer, I've tried all recent version to no avail (even 6.0.3.1)

I could try to boot into uboot and load kernel on different address (not from nand) but no idea how to boot further. One thing I did notice is that the address of timer changes from boot to boot. Not sure whether this is normal or not.

Just wanted to report back that my issue has been solved! After entering uboot and resetting environment variables using defenv command all went back to normal and I was able to flash latest nand version from sd card! Pretty weird that the kernel refused to boot all of a sudden. I guess something in uboot-env must have gone awry that prevented the image to startup.

Could be a nice tip for other people facing weird and unseen issues!!

Also good to know is that once you have serial connection then usb burning becomes a breeze as there is a standard command in uboot to enable OTG mode for flashing using amloigc tools in windows. In this case you don't need to short nand pins and possibly damage your circuit board!!

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.

[chrissales]

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

[anemeth]

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

[gds]

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

[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

You have not told us which version you installed MXQ ARM or HD18Q ?
Try the the other of whatever you used.

[gds]

You have not told us which version you installed MXQ ARM or HD18Q ?
Try the the other of whatever you used.

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

[topher67]

How are people finding the Jarvis version compared to Isengard?
Worth updating or shall I stick with the 15.2 version for now?

[sonofdibnah]

How are people finding the Jarvis version compared to Isengard?
Worth updating or shall I stick with the 15.2 version for now?

Strange question when, if you read the forum and release notes, you will see that you can run one version from Nand and another from SD card. I've yet to find fault with either version I run but kodi 16 wins because of the better stretching of 4:3 to 16:9. So I tend to use the Jarvis version I have on SD rather than the 15.2 I have nand. My advice would be to read the release notes and give Jarvis a try for yourself by running it from SD.

[Dez]

I prefer to use Jarvis.
For some odd reason with Isengard, the program guide for Live TV is always 1 hour advanced. If I reset it, it eventually goes back this way.
Strangely, the system time and time zone is correct, and TVHeadend shows the correct program guide for the time.

Jarvis also appears to start the Live TV stream much faster than Isengard.

As Sonofdinah mentioned, scaling does seem a bit better and appears to stretch 4:3 to 16:9 well.