Draghmar Insert SD card with the latest aml_autoscript on it (take it from 7.0.2.005), boot LE and then execute reboot recovery over SSH. With some luck the autoscript will apply and you'll have 1080p as default resolution.
Posts by kszaq
-
-
Szymon_Zy From my experience Nexbox does some weird stuff with their u-boots and I won't be surprised if they locked access to dtb partition after booting. Or they may simply not use that parition and go with "old scheme" (kernel image with attached dtb) instead. Who knows.
-
michaelchen and others with RTL2832 tuner: can you please try this build: 7.0.2.4-media-test
It has media-backports included but also drivers from stock kernel.
If it doesn't work, you can downgrade to 7.0.2.2 using tar file (no need to wipe data).
Also included in this build is a revert for a Kodi patch that may have been causing 10-sec delay when playing some videos.
-
Whoops, I forgot to include the firmware... I hope you can wait until the next release for the Bluetooth to work. [emoji56]
-
JonSnow WileCoyote Can you try executing this command over SSH: /usr/bin/rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5 &?
-
Yes, thank you. I can now see that there's a Realtek 8723BS chip inside. It's been some time before I made it work for S805, I will have a look what should be done to make it work for S905.
-
this kernel supports both types with detailed amlogic patches
I am (slowly) working on making the latest kernel work.This kernel works out-of-the-box for the WeTek Hub. To make it work and "all" S905(X) devices there are some changes I need to make. This is not a trivial process and it takes time.
-
Kyniol_73 Default resolution is determined by device tree. The value is overridden from 7.0.2.003 on.
Try doing this:
- download zip file with 7.0.2.002 build
- extract aml_autoscript from that ZIP to your SD card - don't replace other files
- use toothpick method to boot
-
Kodi log doesn't tell a single thing about this issue, that's why I always ask to collect full system logs. Please collect and post them here so I can see what is missing.
-
You should run make amlpkg to get both SD card image and update ZIP.
-
I will add Wrxtasy's patch to next builds.
-
Edit here skysar usb via build s805 Alex ...I repeat: I was not able to find driver source for your device. Sources are available for other tuners named "Technisat Skystar" but not yours.
"AlexELEC" is a closed source build. If it works with your tuner, why don't you use it?
-
It seems kszaq is actively avoiding this thread.
It would be nice if someone told us is this possible or not so we don't have our hopes up...I guarantee that I read every single post in Amlogic forum section, I sometimes may not have time to respond to them all, especially when I have no news to report.
It seems like Minix is using some custom sound chip/driver. It might be resolved with kernel update that I am actively (but slowly) working on. I ask for lots of patience.
In case the issue is not resolved with kernel update, I will try to get necessary sources from Minix.
-
Yes, one kernel should support both types. I am (slowly) working on making the latest kernel work.
-
can you Compile model ( stv0299.ko or mt312.ko + b2c2-flexcop.ko + b2c2-flexcop-usb.ko ) for kernel 3.10.99
it not included in your build ...Yes they are:
Code/lib/modules/3.10.99/updates/media-backports/drivers/media/dvb-frontends/stv0299.ko /lib/modules/3.10.99/updates/media-backports/drivers/media/dvb-frontends/mt312.ko /lib/modules/3.10.99/updates/media-backports/drivers/media/common/b2c2/b2c2-flexcop.ko /lib/modules/3.10.99/updates/media-backports/drivers/media/usb/b2c2/b2c2-flexcop-usb.koEdit: I have googled a bit and it seems like there is no Linux driver for this tuner for ARM devices. There is only a closed-source blob for i386 and x86_64 - Intel and AMD CPUs.
-
I fixed the link for you.
Search is your friend: LibreELEC
It seems that it should work. And as said in builds post, trying to run from SD won't break your box and will confirm if you can run my builds.
-
darren1963 I think you should look one page back, this looks like the box you are asking about: LibreELEC
-
@asmar2 I have no knowledge how DVB drivers work, I just include them. Your log is not collected correctly - you should have rebooted before collecting it - but from what I can see you should try connecting the tuner over a powered USB hub first. Here's the error you are having:
Codedvb_usb_v2: usb_bulk_msg() failed=-110
and a solution from someone with similar issue on other platform: OpenELEC Mediacenter - OpenELEC Forum - Error dvb_usb_v2: 2nd usb_bulk_msg() failed=-110 (1/1)