Posts by r4w

Quote from kszaq

This is an issue with u-boot, you have to ask the box manufacturer to fix this.

Thanks, what should I ask for exactly? Power off and suspend are working from the Android side.
My workaround is to restart to internal and power off from Android.

Verified the same issue with 7.0.3.012h.

I'm sorry but I'm too new to Kodi to help

Quote from kszaq

A build with bumped NFS chunk size to test: 7.95.beta5b

I have just tested beta5b but unfortunately increasing the NFS chunk size didn't help

Device type: S905X
Build: 7.95.beta5b
Device: NPET S905X 2G/16G

Issue happens each time I shutdown from the menu or from SSH (poweroff or shutdown -h), the box just restarts instead.

I have attached debug logs.

Quote from sharpey

Can you not use Keymap Editor to map the back button, if the rest of your remote is working already?

Kodi (7.95.2) doesn't even recognise my buttons are being pressed.

The back button works as long as the air mouse is disabled, unsure if this is by design then.
Any other button seems to work (I didn't try the numbers or the Internet explorer button nor the buttons at top Play/Pause/skip track etc).
I'm doing this at night and to watch a movie I didn't need them but tbh I didn't notice the play/pause one, it's on my list to try it

Kshi: Interesting, it seems it's another manufacturer indeed.

usb-devices: LFPA
ls-usb -v: SOQX

I got it from ebay (cheapest I could find), I guess they all look the same: 2.4GHz Wireless Fly Air Mouse Keyboard Remote For Android PC Smart TV Box MX3 M8

PS: I have tested all the important buttons and everything seems to work for me.
I'm wondering if it's normal that the "back" button doesn't work when the air mouse is enabled, but I can live with that.

Quote from minimoe

Nope, it is not expected. Mine shuts down when told to do so
I don't remember anyone else mention this problem.

That's odd, but I have just recalled that I may have forgotten to copy the right dtb last time I have upgraded. Could that cause this? Anything else works.
I'm waiting for my new microsd to upgrade to beta5b.
Thank you!

sharpey: as the airmouse is working, I didn't test many, but up and down buttons certainly works. The home key too. I didn't have much time to test yesterday but I can do today. If any of you have a configuration where all the buttons should do something (again, my back button doesn't do anything), I can give it a try.
Kshi, that's odd. What logs would you like to check? Happy to help to solve the mystery.

All, does the keyboard work for you? It works for me.

Quote from sharpey

Fancy spilling the beans as to how you did? [emoji12]

Sent from my ONE A2003 using Tapatalk

TBH, I didn't do anything special. I have bought it and looking for the configuration I have seen this thread... and told my self: what I have done?
Then, I have just set up the power button and attached the USB dongle and it worked out of the box for me.
I didn't test every button, but the back doesn't do anything for me. Home button is working fine, for example.
If you need any logs, happy to help in exchange of a good conf ahah

I have just got this remote and it's almost fully working for me in kszaq build 7.95.beta5. So far only the back button doesn't work for me.
Can somebody share a remote config so that I can give it a try?

Is there anybody else having the issue that shutdown actually restarts the box with Beta5 running from SD?
Is this expected (know bug as suspended) or should I open a bug for it?
Thank you!

Is anyone else experiencing issue with shutdown/suspend in Beta5 (from SD)?
I have a s905x and whenever I use the power off option, the box just restarts (I'm not using the remote control to do this yet).
If I use the suspend option (which is the default for me in Kodi for the remote too), I cannot wake up the device with remote or mouse/keyboard but I have to power cycle it (I'm aware that suspend may not work), but I think this was working in Beta3/Beta4a, but I need Beta5 due to bluetooth not working in Beta4a.
Am I missing something? Happy to provide any logs.

Tim_Taylor: If the interfaces your box don't support more than 100 Mbit, the only option is what mmpp suggested. Or a USB Wireless AC adapter.
I'm fortunate to have Wireless AC in my box, however the box can handle only up to 120 Mbit bitrate streams, so even only 100 Mbit should be adequate.

You should be able to run birds 90 mbit file.

Quote from kszaq

There is a Kodi patch that aims to improve libnfs performance a bit, I will include in a next build. Let's hope it will get performance a little bit closer to native mounts.

I'm really looking forward to test it, however I'm having a bad performance with SMB too (I didn't try SMB from shell yet).
On the other hand, DLNA (UPNP) seems to work well (I use minidlna as server on the same Linux box).

From USB, I can confirm that Jelly fish 140 Mbit is hitting the hard limit of my box, it can't play it.
My box is fine with Jelly fish 120 Mbit (both HD 264 or UHD 265) and I can run the file from network via NFS (mount from OS only) or UPNP.

I have also tried NFS over UDP, but no major changes in performance.

Just for reference, I'm using this string for the mount (UDP):

mount -o rw,relatime,vers=3,namlen=255,hard,proto=udp,port=2049,timeo=70,retrans=3 192.168.xx.xx:/home/download /storage/mnt

TCP:

mount -o rw,relatime,vers=3,namlen=255,hard,proto=tcp,port=2049,timeo=70,retrans=3 192.168.xx.xx:/home/download /storage/mnt

But in my case, "mount 192.168.xx.xx:/home/download /storage/mnt" defaults to the TCP options above, so I don't need to pass them on.

Tim_Taylor, have you tried to run iperf first between the two hosts (it works on Windows too) to see how much theoretical bandwidth you may get between the devices?
Also, it really depends on how your network is designed (I have all Gigabit equipment and my "NAS" is a virtual machine running Linux).
Regarding mounting NFS from the NAS, maybe you can check with the vendor or Google it for the appropriate string to mount it over linux.
I didn't test from USB today yet, but I don't expect to see major differences.

ssarava9  jd17: If you can try to mount NFS as I did and report to me your results, it would be interesting to understand what's your max video bitrate that your box can sustain.

I can play without problems these files (I'm testing more my wireless at this point as I have more bandwidth):

bird90.m2ts
bird90.
jellyfish-120-mbps-4k-uhd-h264.mkv
jellyfish-120-mbps-4k-uhd-hevc-10bit.mkv
Camp (Nature) 4K HDR Demo (Sony)h.265 (HEVC)3.840 x 2.160 75.8 Mbit/s 59.9410 bit HDR 2:07
http://jell.yfish.us/media/jellyfis…4k-uhd-h264.mkv

Maybe my wireless was better yesterday or I was too tired but I believe I have run this too:

jellyfish-140-mbps-4k-uhd-hevc-10bit.mkv

I can't see heavily buffering today but it seems that the GPU can't cope with it instead. Yesterday I was running Beta4a and today I'm on Beta5, maybe is there a difference?
I will try tomorrow from a USB key to see how much it can handle, but so far I'm more than happy as 120 Mbit will cover videos for a while (at least for me).

PS: sorry for the no-beautiful links

kszaq: thank you for the latest release! Bluetooth is working now for bcm4335:)