https://kodi.wiki/view/Add-on:Transmission
Let’s see what Team Kodi has to say about it:
This add-on has been marked as broken in the repository: Violation of our piracy policy
@Portisch @Vascobraga thanks, was able to remove pvr.hts. but still same behaviour, kodi starts to home screen but stays in bootloop. i still believe pvr.hts was initiating the behaviour, cause i can see it connecting and immediately disconnecting from tvh, than this described bootloop. i do not see anythng special now in the log, but i am just poor user 
hope it helps development…
This was a proof of concept before Christmas. As already mentioned it will only work with Dolby Vision Licensed SoC’s. I tried the N2 and it doesn’t work and I doubt it could ever work or be tricked to work.
3 Likes
Can you copy this advancedsettings.xml to the userdata folder?
advancedsettings.xml (710 Bytes)
It will enable debug logging and debug for libCEC.
The crash log shows libCEC crash on setting the OSD device name.
Just place the file in the userdata folder where the other xml are located and restart the box.
When the error happen again please upload the new crash log, thx.
Forbidden (#403)
tnx what device exactly?
thank you, let me make a test image for you…
1 Like
interesting that it has been working fine for awhile, than suddenly after reboot this problem started.
no hurry, wife is occupating the tv on stable CE
I have no idea why it is crashing without debugging it with GDB.
But I have no idea how to reproduce this crash here locally.
It crashes when libCEC set the OSD device name.
In the test image I dropped the package arm-mem as it’s written for armv6l and armv7l.
But the Amlogic SoC are already a long time armv8l. So maybe there is a difference what may cause this issue.
Please test with this image:
https://mega.nz/file/6S4SRZpR#4On73kx3txoM2GWDi6kBfnNN5HFCDlwKCBx3Yjf6oew
On CE-19 you just can enter /storage/.update and use the megadl https://mega.nz… tool to download directly on the device.
1 Like
same behaviour.
additional info that came to my mind, do not know if useful - if i restore matrix backup that has been working and restore it, it also goes into this bootloop. https://controlc.com/c51c4cbf
if i do clean install, it will work for awhile, than this problem will start w/o changing anything, at least not intentionally.
interesting that nobody else reports this.
1 Like
Now the strlen used in kernel fails, no idea how to solve it without local debugging.
don’t bother, just wanted to help development. but it’s challenging me as well, though i have no knowledge
after it booted to safe mode, i just installed pvr.hts, did the config, started connection to tvh, get refused and bum, imeediate bootloop. i might be wrong and there is nothing in log actually, but i do not believe it is coincidence.
Is there an aproximately space of time for an official stable release?
@nrpetonr does it also happen with 20200104 nightly? There was a change about libCEC handling, not that this cause this issue. Please test it with this version.
One more look into your logs shows me after libCEC is opened it immediately sends out the OSD name (what lead to the crash), I am not sure this is correct.
I’ve read that if you upgrade the firmware to at least 004FW, you can boot from SD (the current latest is 005FW).
https://theminixforum.com/index.php?forums/neo-u22-xj-official-firmware-releases.132/
i think i did, but no problem to test. would you like me to do clean install or just reflash over existing build?
how does the backup work for u?
Had no time yet. Please try with the nightly from the archive again please, clean install. It’s just to be sure it’s another issue then the last libCEC changes.