Use hifiberry-dacplus.dtbo and i2c-rtc.dtbo. According to this both modules have no GPIO conflict.
Posts by Da Flex
-
-
Sorry, this is utter nonsense. The serial_ir driver will load whenever there's an UART present. And as the OP already wrote in his first post that he's not getting any output chances are very high there's nothing attached there.
What kind of output do you expect from a serial port device at boot time?
-
Sigh. If you had paid more attention then you'd noticed that this was the serial_ir module the OP had loaded and as the SOC has a built-in UART the module load succeeded. This doesn't mean that there's an IR receiver attached to the serial port.
We know the IR receiver is attached, and the serial_ir driver has been loaded. That's enough for me to trust the /dev/lirc0 output.
The Android-x86 Linux (yes, I'm sure it's Linux) can handle it, which makes it very likely to work with LE, too.
-
Sorry, but this is nonsense. LIRC needs an IR device/driver where it gets it's signals from and this is missing with the box. Running LIRC won't help.
If you have a look at the start posting (ir-keytable output), you can see that the LIRC device is ready to go.
-
No, i don't use usb IR dongle, my box has a built-in IR receiver. This IR receiver works fine under android, but it refuses to work under Linux.
Android-x86 OS'es are usually based on Linux kernels. At this point, my conclusion is that your built-in IR receiver is made for LIRC, and does not support most of the IR protocols LE is offering. Your Android-x86 OS probably has LIRC enabled, and that's why it's working. Under LE you have to enable / configure it as mentioned.
Many LE users prefer CEC, because it uses the TV remote control without the need of dealing with IR signals.
-
Which IR protocol do you use at your Android mobile? If it's LIRC, then go the LIRC way, and enable / configure it.
-
Some more words would be helpful. I assume your answer to my first question is "yes", and to my second question is "no, LIRC is disabled, because
/storage/.config/lircd.conf doesn't exists in my configuration".Do you see the gap of supported / enabled protocols? The reason for that gap could be your IR dongle. If you bought a LIRC dongle, then it probably can't deal with the most other supported protocols.
If the dongle worked with other Linux OS'es then it's probably a driver problem (different kernel).
-
I installed the Mi remote application on an Android phone with an infrared port...
That means you are using an IR receiver dongle at serial port, right?
CodeSupported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm Enabled protocols: lirc sonyDo you use a LIRC RC? If not, disable it at Settings -> Services and reboot, as mentioned at your first link (part Troubleshooting).
-
At the drieschel.de download you can see a "1G" after MXIII. That could mean "first generation" -> more than one MXIII version.
-
PS: I just found your other forum activity here. It's no good conversation, if you double dip without telling us.
-
It's no official image, it's no supported hardware, so this forum is actually not the right place to ask.
The error message can mean that hardware and software don't fit, maybe because there are different hardware revisions.
If you want to invest a lot of time, you can try to compile a current LE version.
My suggestion is to buy a Raspberry Pi 4B, and stay away from the Chinese fortune cookie.
-
btw, where did you read that an older version of inputstream.adaptive is the reason of your buffering issues.
Never heard of buffering issues because of inputstream.adaptive
Thanks for the list of issues. The ISA settings have two max. resolution options. When setting them higher than 640p, then it breaks the DAZN stream by showing the buffering / loading sign in batches.
-
Indeed but the needed change is only in that master version so there was no other choice
What does "needed change" mean? Are buffering issues fixed at your version?
As mentioned, I'm using ISA 2.4.2 now, but I have no benefit.
-
Some SD cards, I think the most, have their own error correction system. So bad blocks will be sorted out, and the card still works with now less total memory.
-
Does the sd card naturally slow over time since they do not support trim.
Normally not. It's hard to say what really happens inside an SD card, because they at least have their own error correction code as part of the firmware. If you notice slowdowns again, scan for bad blocks or buy a new microSD.
-
Do you think I should leave a message regarding the TVDB scraper on the Kodi forums?
Yes. It increases the chance that the developer of the add-on will notice the bug. Post at the right place (add-on or bug report sub-forum).
-
For the amount of times that I have installed LE I am 100% certain that it's not a DB problem. I can't get every LE installation wrong and all the Windows installations right.
I don't think it's an installation problem. The DB file will be created and edited after the installation. The point is, it will be created/edited in different ways, because the implementation of the TVDB scraper add-on is different on Windows and Linux. That's why my suggestion is to use a DB tool to have a look inside the DB files. Maybe a DB column is missing, and the add-on can't write into it.
A possible cause is that the DB format (columns etc.) can change from one add-on version to the next. If the developer forgot to do the DB update, then the add-on update is incomplete, and can produce errors like yours.
-
excluding the database file
Then maybe a database entry is missing on the LE installation, and the add-on can't write into it.
I don't know the database type (MySQL etc.), but there are tools to read those files (MySQL workbench etc.).
If you really want to invest the time, compare the database files by using appropriate tools, and eventually add missing entries.
