[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[phinc]

hi ,i have been able to install the latest stable build for mxq red in mxv s805 device.
http://www.everbuying.net/product904...FvaRoC9oDw_wcB

but the remote dont work.I have put mxv remote file too,arrows key works but ok button doesnt work.
how can i get the original remote of mxv working with openelec build .
thanks

If you want to make the factory remote work, simply extract remote.conf from the Android ROM for your device and put it into Config folder.

[billo]

Awesome work Kszaq on bringing OE to AML. I new to this forum and have been looking for AML OE build for a while. I just discovered your build

I have 2 MX boxes:

1. MKv : http://www.aliexpress.com/store/prod...342186647.html
2. Beelink with Red strip on the top

Questions:
1. Which ROMs should I be using , please provide me the links
2. I once tried another OE Rom on my MKv but I wasn't able to turn on the WIFI and was also not able to set the Display to 1080p
3. Is there a OE firmware available for M8s S812 ?

Can someone assist me THANKS !

billo

[billo]

I forgot to ask, How to extract the " extract remote.conf from the Android ROM for your device and put it into Config folder "

billo

[jackmate]

i have extracted remote.conf from original android rom and put in openelec configfiles folder.
problem is all key in remote works except the OK button,
without ok button not working ,useless.
what should i do?i been using wireless airmouse right now.
another issue is wifi not stable.
i see 2 ssid in wifi same repeated,i connect to one but disconnects after few minutes and connects again.
when i reboot device ,wifi doesnt connect automatically.

[borikua]

i have extracted remote.conf from original android rom and put in openelec configfiles folder.
problem is all key in remote works except the OK button,
without ok button not working ,useless.
what should i do?i been using wireless airmouse right now.
another issue is wifi not stable.
i see 2 ssid in wifi same repeated,i connect to one but disconnects after few minutes and connects again.
when i reboot device ,wifi doesnt connect automatically.

Think the problem is you are trying to use a rom for the mxq red in a mxv s805 device. These are two different devices.

[kszaq]

Awesome work Kszaq on bringing OE to AML. I new to this forum and have been looking for AML OE build for a while. I just discovered your build

I have 2 MX boxes:

1. MKv : http://www.aliexpress.com/store/prod...342186647.html
2. Beelink with Red strip on the top

Questions:
1. Which ROMs should I be using , please provide me the links
2. I once tried another OE Rom on my MKv but I wasn't able to turn on the WIFI and was also not able to set the Display to 1080p
3. Is there a OE firmware available for M8s S812 ?

Can someone assist me THANKS !

billo

@billo
1. 2. "MKV" box is not supported. For the second one you should use MXQ version, links are provided in OP.
3. Not from me, you should search the forum and maybe someone builds for M8s.

I forgot to ask, How to extract the " extract remote.conf from the Android ROM for your device and put it into Config folder "

billo

You may either copy it using a file explorer in Android or extract it from zipped Android firmware update. You'll find the file in /system/etc folder.

i have extracted remote.conf from original android rom and put in openelec configfiles folder.
problem is all key in remote works except the OK button,
without ok button not working ,useless.
what should i do?i been using wireless airmouse right now.
another issue is wifi not stable.
i see 2 ssid in wifi same repeated,i connect to one but disconnects after few minutes and connects again.
when i reboot device ,wifi doesnt connect automatically.

jackmate About OK button, you can do the following:

1. Login over SSH.
2. cat /proc/kmsg
3. Press OK button and note the message that appeared in the log.
4. Look for the keycode in remote.conf and change it to 28.

You haven't provided any logs so I'm unable to give you any hints on WiFi issue. Please also not that I don't support this device.

[jackmate]

@billo
1. 2. "MKV" box is not supported. For the second one you should use MXQ version, links are provided in OP.
3. Not from me, you should search the forum and maybe someone builds for M8s.

You may either copy it using a file explorer in Android or extract it from zipped Android firmware update. You'll find the file in /system/etc folder.


Guest About OK button, you can do the following:

1. Login over SSH.
2. cat /proc/kmsg
3. Press OK button and note the message that appeared in the log.
4. Look for the keycode in remote.conf and change it to 28.

You haven't provided any logs so I'm unable to give you any hints on WiFi issue. Please also not that I don't support this device.

Hi ,
Ok button in remote works now after changing code for ok button in remote.conf file .
Thanks
Only other issue now is wifi,
2 wifi name appears for same ssid,
Once I connect ,it drops out and when reboot wifi doesn't connect ,get error in wifi connection .
What logs do u want ,I can provide
.
Thanks

[kszaq]

Hi ,
Ok button in remote works now after changing code for ok button in remote.conf file .
Thanks
Only other issue now is wifi,
2 wifi name appears for same ssid,
Once I connect ,it drops out and when reboot wifi doesn't connect ,get error in wifi connection .
What logs do u want ,I can provide
.
Thanks

jackmate I would need dmesg collected after booting the box and trying to connect to a network. Have you tried using HD18Q build? It doesn't load dummy SDIO WiFi driver that may cause some WiFi chips to fail.

[rev6]

MXQ. 5.0.8.18 just crash now. Video froze and audio looped. SSH won't seem to connect for dmesg.

[billo]

Thanks kszaq !

I installed the 5.0.8.18 on my MXv S805 and it seems working so far :-) I have MXQ black and Red ordered so as soon as I get those boxes I will try same. now i need to find M8s rom..

I have another question , 5.0.8.18 has the Google TV boot screen , i need to change it to my own boot logo. I am able to change the OE spalsh screen which is the oemsplash.png,

[jackmate]

jackmate I would need dmesg collected after booting the box and trying to connect to a network. Have you tried using HD18Q build? It doesn't load dummy SDIO WiFi driver that may cause some WiFi chips to fail.

I did flash HD18q build ,with that no wifi is shown in openelec. I flashed mxq red openelec build back ,wifi is there but 2 wifi name eth0 and eth1 for same wifi.connected to 1 and if box reboot,wifi is lost and doesnt connect automatically,get failed message.and here is dmesg

http://sprunge.us/gOGV

after reboot :

http://sprunge.us/WTMB

[kszaq]

MXQ. 5.0.8.18 just crash now. Video froze and audio looped. SSH won't seem to connect for dmesg.

rev6 I have experienced several crashes with my MXQ recently and what helped is changing CPU governor to hotplug on boot. This will be a in a next release. If I remember correctly, you reported a "chipmunk sound" issue some time ago. I was able to reproduce it but I'm still working on a fix.

Thanks kszaq !

I installed the 5.0.8.18 on my MXv S805 and it seems working so far :-) I have MXQ black and Red ordered so as soon as I get those boxes I will try same. now i need to find M8s rom..

I have another question , 5.0.8.18 has the Google TV boot screen , i need to change it to my own boot logo. I am able to change the OE spalsh screen which is the oemsplash.png,

billo This will help you: http://mbox.co.za/forum/viewtopic.php?f=23&t=334

http://freaktab.com/forum/main-category/screens-wallpaper-and-other-artwork/15367

I did flash HD18q build ,with that no wifi is shown in openelec. I flashed mxq red openelec build back ,wifi is there but 2 wifi name eth0 and eth1 for same wifi.connected to 1 and if box reboot,wifi is lost and doesnt connect automatically,get failed message.and here is dmesg

http://sprunge.us/gOGV

after reboot :
http://sprunge.us/WTMB

jackmate OK, now I see that your device uses Realtek 8723BS chip. For the next release I will include drivers for it in HD18Q and you should be able to make it work by adding a modprobe 8723bs command to autostart.sh script.

[pajopasa]

Hi kszaq
Thanks for your great work.
I've installed your 5.95.3.1 test version and i found this.
It works but...
Only in english, no hotplug governator for the cpu and when we boot the device (mxq) several lines like in old ms-dos.
It is possible to remove the google tv splash screen and put the openelec logo at boot?
In the final release will fix this?
Cumps

[rev6]

rev6 I have experienced several crashes with my MXQ recently and what helped is changing CPU governor to hotplug on boot. This will be a in a next release. If I remember correctly, you reported a "chipmunk sound" issue some time ago. I was able to reproduce it but I'm still working on a fix.

Oh good I thought I might have been the only one with the crashing. Thanks. I haven't had issues with "chipmunk sound" just a lot of the time audio is slightly ahead of video. -0.250 audio offset fixes it. p8 is still the best here for audio/video sync.

[kszaq]

Hi kszaq
Thanks for your great work.
I've installed your 5.95.3.1 test version and i found this.
It works but...
Only in english, no hotplug governator for the cpu and when we boot the device (mxq) several lines like in old ms-dos.
It is possible to remove the google tv splash screen and put the openelec logo at boot?
In the final release will fix this?
Cumps

pajopasa 5.95.3.1 uses hotplug as default governor for all devices: https://github.com/kszaq/OpenELEC.tv....arm.conf#L467
These "MS-DOS lines" are actually a kernel log and I like to have it there but you're right, I may want to get rid of it in the future...
The "Google TV" splash is from original firmware. If you change it to something else, my latest releases won't change it. Look at my previous post to read how to change it. If you want to use an OpenELEC logo, you can download logo.img from my previous releases: https://github.com/kszaq/OpenELEC.tv...files/logo.img

Oh good I thought I might have been the only one with the crashing. Thanks. I haven't had issues with "chipmunk sound" just a lot of the time audio is slightly ahead of video. -0.250 audio offset fixes it. p8 is still the best here for audio/video sync.

rev6 I'm sorry, someone else must have reported it... anyway, it's going to be fixed in today's release.
Here's a changelog between 5.0.8p8 and 5.0.8.18: https://github.com/kszaq/OpenELEC.tv...8p8...5.0.8.18
As you can see, there are no changes that may have affected audio sync and honestly I'm out of ideas what may be causing them for you.