[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[jed]

Can you try if 6.0.0.1 works? Don't flash bootloader - after changing uenv you don't have to do this and it might brick the box. Simply copy KERNEL and SYSTEM from 6.0.0.1 tar file to your SD card and rename KERNEL to kernel.img. That way you'll be able to tell if OpenELEC works if you change CPU governor back to hotplug - 6.0.0.1 uses it.

Yes ! Well I havent loaded anything yet but I am happily clicking around in OpenElec 6.0.0.1 :-)

[hockeycraze]

it looks like i spoke too soon, i am still having the same issues with wifi... wifi still not working when a hard reboot occurs, driver completely fails to load... wifi options in openelec settings dont show up at all... kszaq is there a way to retrieve logs without an internet connection???

[jed]

Can you try if 6.0.0.1 works? Don't flash bootloader - after changing uenv you don't have to do this and it might brick the box. Simply copy KERNEL and SYSTEM from 6.0.0.1 tar file to your SD card and rename KERNEL to kernel.img. That way you'll be able to tell if OpenELEC works if you change CPU governor back to hotplug - 6.0.0.1 uses it.

kszaq Yes ! Genius ! Works ! :-) Noticed though when I restored an OpenElec backup (had TVAddons build on) from my other MXQ it started freezing again. Perhaps restoring that backup changed the CPU governor back ? Then it froze again.

[kszaq]

it looks like i spoke too soon, i am still having the same issues with wifi... wifi still not working when a hard reboot occurs, driver completely fails to load... wifi options in openelec settings dont show up at all... kszaq is there a way to retrieve logs without an internet connection???

To be honest I don't know but I don't think there is. You can only retrieve them using Ethernet connection when there's no WiFi available.

Yes ! Genius ! Works ! :-) Noticed though when I restored an OpenElec backup (had TVAddons build on) from my other MXQ it started freezing again. Perhaps restoring that backup changed the CPU governor back ? Than it froze again.

CPU governor is determined by kernel config unless you change it by yourself in an autostart.sh script. If you didn't have that kind of script in your backup, I'd say that CPU in your box can't handle bigger loads and apart from using hotplug governor you may want to downclock it a little.

[jed]

CPU governor is determined by kernel config unless you change it by yourself in an autostart.sh script. If you didn't have that kind of script in your backup, I'd say that CPU in your box can't handle bigger loads and apart from using hotplug governor you may want to downclock it a little.

kszaq OK, no worries, and thanks for trying I've moved the box on now but I am sure the issue will come up again somewhere when someone ends up with one of this type of board (whatever that was) on a newer MXQ. Can you tell me please kszaq where you got your all black MXQ v4 from and/or Red Stripe MXQ please ?

[hockeycraze]

kszaq i managed to retrieve logs through an ethernet connection, this is from a bootup sequence where wifi failed to load. hopefully this shines some light on why the wifi driver isn't loading...

[hockeycraze]

kszaq and the following are logs from when wifi successfully loaded during a random reboot, wifi fails to load during the majority of reboots on my machine

[pigbait]

kszaq I know your busy with all these other boxes and family life. but just woundering it you have A jarvis beta build?

[kszaq]

kszaq OK, no worries, and thanks for trying I've moved the box on now but I am sure the issue will come up again somewhere when someone ends up with one of this type of board (whatever that was) on a newer MXQ. Can you tell me please kszaq where you got your all black MXQ v4 from and/or Red Stripe MXQ please ?

jed I sent you a PM.

kszaq i managed to retrieve logs through an ethernet connection, this is from a bootup sequence where wifi failed to load. hopefully this shines some light on why the wifi driver isn't loading...

kszaq and the following are logs from when wifi successfully loaded during a random reboot, wifi fails to load during the majority of reboots on my machine

hockeycraze These logs are from 6.0.1.1. Have you tried the test build I posted and the second one from http://s805.eu/test/6.0.1.2-test1/ ?

kszaq I know your busy with all these other boxes and family life. but just woundering it you have A jarvis beta build?

pigbait Not yet. When I'm happy with 6.0.1.2 (in a few days, I suppose), I'll port my commits to Jarvis branch. It's not been a priority for me since there's no official OpenELEC beta release yet.

[hockeycraze]

jed I sent you a PM.



hockeycraze These logs are from 6.0.1.1. Have you tried the test build I posted and the second one from http://s805.eu/test/6.0.1.2-test1/ ?


pigbait Not yet. When I'm happy with 6.0.1.2 (in a few days, I suppose), I'll port my commits to Jarvis branch. It's not been a priority for me since there's no official OpenELEC beta release yet.

kszaq yes i tried the first test build you posted and the same problem was occuring, so i reverted back. havent tried the second one yet. is the problem discernible from the logs?

[hockeycraze]

kszaq i will try the second test build and report back

[jed]

kszaq Thank you. Read and replied :-)

[burimek]

burimek I noticed the colour keys bug after some testing and I figured out that OpenELEC introduced mappings for that keys that override our previous mappings. I fixed this for the next release, aiming for this week.

In the meantime I will be able to test only for MK808B+ as my second MXQ has broken down and I am waiting for a replacement. No luck with these boxes.

thanks work great now with the color buton, but with this new version have black screen whenn i play a video, audio works, need restart to become video, i have 3 time this bug, i thing is a bug.
waiting for new release, thanks for your good job,
i spend you a beer...

[jed]

Anyone running OpenElec on Chiptrip MXV (S805) box ? How is it and are these boxes variable like all-black-MXQ or are they all the same ?

[jed]

Help ! Bricked my MXQ_A. I updated the bootloader using kszaq instructions a few pages back and then went to reboot and noticed something I don't normally see and that was no flickering whatsoever on TV. No matter what I do there is no image on TV. Now I've tried USB update method using Amlogic USB Burning Tool but no matter what I do the box does not register. The LED is still on though (blue). Is there anything I can do ? EDIT: Scarily, with nothing to lose I had it connected to PC and Burning Tool running and shorted some pins on what I thought might be the Nand chip and then, by complete suprise I heard Windows10 detect a device and I looked up and it had started programming it! Strange why it would suddenly mess up like that, all I did was flash a bootloader !