Display More
Thanks for latest builds.
install to EMMC doesn't work for me, if I select install to EMMC in le settings nothing happens.
Display More
Thanks for latest builds.
install to EMMC doesn't work for me, if I select install to EMMC in le settings nothing happens.
Could you make a new testbuild with latest changes for mvr9?
it's an officially by libreelec supported TV box with rockchip 3328.
Bqeel MVR9 (NT-N9) TV Box Review - Part 2: Android Nougat Firmware, RKMC, YouTube 4K, and More
Could you please publish nightlies for trn9/mvr9 box on Index of / ?
I'm getting data errors in recordings with your 4.3 but also with official 4.2 builds.
my dvb box technotrend s2-4600 is connected to my mvr9 box.
I also had similar issues with rpi and newer kernel, which were solved with a kernel patch DVB issue since LE switched to kernel 4.9.x
Could this patch also be applied to rockchip kernel?
uploaded a new version with that fix ^^^^^
no idea if this works, no time to test it yet
latest build works for me on mvr9.
Thanks!
you have latest LE9 images ?
I need top check if this is a build problem or an Tvh problem.
And pls fix your smaba.conf
browsable to browseable this messes up the log ;D
samba.conf is fixed, thanks
I'm using build 8.90.006 (RK38282.arm) downloaded from Index of /test/006/ on 4th october.
updated for LE9 after the buildserver disappeared several times
currently just manual update, no time yet to setup full auto mode
tvh doesn't start on my 3328 box
journalctl http://ix.io/1oxf
dmesg http://ix.io/1oxg
Looks like the device is not recognized.
Code20:41:32.545 T:3946808176 ERROR: AddOnLog: Joystick Support: ScanEvents: failed to read joystick "GEN GAME" on /dev/input/js0 - 19 (No such device)
It also looks like you may be having power issues. Try using a powered hub and see if this improves things.
Otherwise it may just be a issue with the rk3328 build which is always a possibility with such a new build.
It's a bluetooth controller, so no hub possible.
Do you have a hint how to dig deeper? As already mentioned, controller worked fine on rpi3.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link
This is the debug log
New MVR9 image with new bluetooth firmware
works good for me but some strange kernel messages:
[ 71.439784] Bluetooth: Failed to start inquiry: status 12
[ 74.266464] Bluetooth: Invalid header checksum
[ 74.270103] Bluetooth: Out-of-order packet arrived (2 != 1)
[ 74.272548] Bluetooth: Out-of-order packet arrived (3 != 1)
kernel log http://ix.io/1nre
I'm using rk3328 community build for my mvr9 box and I'm able to connect my bluetooth gen game s3 game pad, but it's not recognized in kodi.
I'm thankful for every hint.
kernel log
udev rule
thanks, I also had interrupts with my bt headphones and rpi but no issues when using the headphones with smartphone.
Do you know if 150balbes will push the emmc install/backup scripts to libreelec?
When you will push the rc driver?
One more missing point for mvr9 is the non functional on/off switch, maybe something could be done about that.
Dev progress is very well for the box!
Display MoreNew MVR9 image with bluetooth support
After writing the image
Check the following file on your micro-sd card
microsd_card/extlinux/extlinux.conf
Just add 'bluetooth' to the end of the following string so it looks like
APPEND boot=UUID=<uuid> disk=UUID=<uuid> quiet console=tty0 bluetooth
Also need to turn bluetooth on in the LibreELEC Settings.
The first time it also froze and I just reconnected the power.
Please check if bluetooth is turned on, if it also makes videos freeze or if everything works and provide logs.
Hope it's something small that is easily fixable.
Do you also get audio interrupts with bluetooth speaker?
I connected my bt controller to mvr9, but can't map buttons.
All I get is
21:51:05.942 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_IS_UP → DEBOUNCE_EVENT_OTHERBUTTON → DEBOUNCE_STATE_IS_UP
21:51:05.942 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_IS_UP → DEBOUNCE_EVENT_PRESS → DEBOUNCE_STATE_DOWN_WAITING
21:51:05.942 T:4084200304 DEBUG: CLibInputPointer::ProcessButton - event.type: 4, event.button.button: 0, event.button.x: 0, event.button.y: 0
21:51:05.967 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_DOWN_WAITING → DEBOUNCE_EVENT_TIMEOUT → DEBOUNCE_STATE_IS_DOWN
21:51:06.073 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_IS_DOWN → DEBOUNCE_EVENT_RELEASE → DEBOUNCE_STATE_RELEASE_WAITING
21:51:06.073 T:4084200304 DEBUG: CLibInputPointer::ProcessButton - event.type: 5, event.button.button: 0, event.button.x: 0, event.button.y: 0
21:51:06.085 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_RELEASE_WAITING → DEBOUNCE_EVENT_TIMEOUT_SHORT → DEBOUNCE_STATE_RELEASED
21:51:06.098 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_RELEASED → DEBOUNCE_EVENT_TIMEOUT → DEBOUNCE_STATE_IS_UP
21:51:06.168 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_IS_UP → DEBOUNCE_EVENT_PRESS → DEBOUNCE_STATE_DOWN_WAITING
21:51:06.168 T:4084200304 DEBUG: CLibInputPointer::ProcessButton - event.type: 4, event.button.button: 0, event.button.x: 0, event.button.y: 0
21:51:06.193 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_DOWN_WAITING → DEBOUNCE_EVENT_TIMEOUT → DEBOUNCE_STATE_IS_DOWN
21:51:06.254 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_IS_DOWN → DEBOUNCE_EVENT_RELEASE → DEBOUNCE_STATE_RELEASE_WAITING
21:51:06.255 T:4084200304 DEBUG: CLibInputPointer::ProcessButton - event.type: 5, event.button.button: 0, event.button.x: 0, event.button.y: 0
21:51:06.266 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_RELEASE_WAITING → DEBOUNCE_EVENT_TIMEOUT_SHORT → DEBOUNCE_STATE_RELEASED
21:51:06.279 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_RELEASED → DEBOUNCE_EVENT_TIMEOUT → DEBOUNCE_STATE_IS_UP
21:51:06.814 T:4084200304 DEBUG: libinput: event3 - debounce state: DEBOUNCE_STATE_IS_UP → DEBOUNCE_EVENT_PRESS → DEBOUNCE_STATE_DOWN_WAITING
Display More
in the log.
Is something still missing? Controller already worked with rpi.
I think so, maybe that is causing the crashes, but I haven't changed anything when I tested, only flashed and then changed extlinux.conf file.
I will test some more later today.
You can also test.
my bt headphones connected and work. no crash in livetv even when zapping. :->
further testing needed.
reboot doesn't work any more, power cycle is needed.
EDIT: after an hour of using bt headphones I'm experiencing some audio dropouts during livetv and video streams. connection to headphones has never been lost. thanks Kwiboo