It's more like we are waiting for those Wayland features.
No need to wait, but rather actively contribute for it.
It would miss some crucial features like refresh rate switching. Also Kodi does not support HDR passthrough on Wayland.
Any places (GH issues?) to track the progress to make it happen?
LE can be built with Wayland.
Nice. Is it documented?
Was dropped in favor of GBM, but no Wayland still I believe (even optional)?
LE has no need or plan to use Wayland though.
Is it still true?
X11 is more and more like abandonware now, it won't have support upstream anymore.
It's better we think how (and when) we can drop it too.
I didn't put it clear:
I want to use HAT on RPi4, but on Android TV. So I wonder if I could somehow build custom Android TV for RPi to support DVB there? I'm not sure if TV HAT-supporting DVB drivers for Android exist..
Thanks, my interest is mainly in their Android TV sources.
I recall their Android TV firmware supported embedded DVB tuner the boxes had.
So I wonder if I could repeat the procedure and somehow add RPi's DVB TV HAT support to Android TV custom build?
Hi,
sorry I couldn't find the info - what happened with WeTek Hub/Play2, they discontinued their business of STB boxes?
I don't see any mention of these nor any new models on their site, neither about the firmware they used (Kodi/Android TV-based).
Should work, I was experimenting with it on Amlogic box several years ago.
I get the opposite, the BD Remote disconnects really quickly I and most of the time I have to hit a button twice; I don't mind, it saves battery.
IIRC, there is an option in LE for BT devices to disable auto-disconnect. Try submenu on connected PS3 remote, or similar.
Hi,
I would like to start PVR Live TV every time screen turns on (after being off on idle).
Do I have some signal to hook up?
I'm completely newbie in Kodi scripting.
Thanks for any help.
This is bluetooth remote.
I used this remote but the main issue on LE for me was really quick battery drain.
Please tell if you get different experience..
The pull-up setting seems also to be ignored, since the high-voltage is still only 1.9 V. I therefore added a 10 k resistor, which puts it to 3.1 V.
I wonder why the pull-up setting was ignored, is it correct syntax?
In the end, I was able to make it work providing 64 hexadecimal digits converted with wpa_passphrase as a password for connman.
edited the systemctl script for wpa_supplicant to, again, match what Raspian was running:
Hey utdrmac, could you share your script to provide complete solution?
63-character passwords are pointless.
It's a matter of well-established password I already use for all my devices (adding new devices via WPS mostly) , and changing it is not feasible.
Regardless, it's a known issue and the workaround is to use connmanctl over SSH to join the network.
That doesn't work either - the same "invalid-key" error..
I'm not quite sure how further debug the problem.
To have a connection, I'm going to supply a config to wpa_supplicant. If someone has ready solution, please share.
Hi,
I have generated 63-characters WiFi password for all devices in my house, so I can't really change it just for RPi.
For some reason, I can't set it in connman config either - get "invalid-key" error.
I also tried to convert the password to 64 digit with wpa_passphrase, no luck.
Both methods work in connman on Ubuntu (version 1.36 vs 1.39 on LE).
If I temporary change the password to a fake 12345678, then it works on RPi.
Could someone confirm the problem, at least? I'm on LE 10.0.1 for RPi4.
Hi, just wanted to ask is this remote still drains batteries on idle as earlier?
it will still run poorly on RPi0/1 devices because they don't have enough RAM for the new video pipeline
In this video from 2017 we can see LE ate only 18% RAM on Pi Zero:
** VIDEO DELETED DUE TO SHOWING PIRACY ADDONS **
Do we regressed so much since then?
Would adding some swap help?
PS: asking in spite Pi Zero 2 W just launched, it's much more powerful but still has only 512MB of RAM..
