Posts by chewitt

If we turn our anti-spam defenses off to appease you (one user) we get overwhelmed fairly quickly by a ton of spam which pisses off all the moderators and staff of the project (many users) who support our userbase (several hundred thousand users). If we have to lose one user to keep everyone else happy .. sorry but we're not changing. This project is non-profit. This forum doesn't track anything. There are no advertising tools.

"Support" in that context means you can boot the board. There's a ton more code required to get a functional media device!

Overall I am very happy to see a mix of the Pi Foundation staff, several core subcontractors they hired, and numerous names from the Pi ecosystem (including some of our own contributors) writing and upstreaming code to the kernel right now. The previous Pi architecture ended up being largely "out of tree" because when the first Pi launched in 2012 the folks who wrote the code were (in their own words) pretty ignorant about kernel things and the business priority was on shipping a working product. Over time their upstream awareness grew but the success of the Pi meant the task had become exponentially larger and still being a charity with a small staff the priority remained on shipping a working product. RPi0/1/2/3 are now super stable because the codebase has been iterated continuously and attentively over a period of seven years. RPi4 is being treated very differently. The benefits of being and business need to be "upstream" are very clearly understood now, and to continue the stratoshpheric success of Pi hardware the new shiny needs to mature a tad quicker than seven years. Lessons have been learned. Fortunately the success of the Pi means they're somewhat better funded this time around, so they aren't being shy about spending on good resources to get things done.

So .. to end my ramble. In the last few days some of the GBM/V4L2 work reached the point where we can package a "working" system on Linux 5.4 and we'll bump to Linux 5.5 soon. Proper public testing is still some way off as the transition from MMAL to GBM/V4L2 decoding means "one step forwards and two steps backwards" in the user experience due to the amount of new code involved. We'd like things to be closer to parity before we invite the masses to bug hunt. The greatest compliment will be a bunch of users whining about updating and not noticing any difference

Once Linux 5.6 lands in LE in a few months time we can switch devices to the in-kernel module and drop the wireguard-linux-compat package. Until then it's trivial to build as an out-of-tree package.

WireGuard support is now merged in LE master branch. I will wait on the connman bump before PR'ing to the 9.2 branch as well. It's in a functional state (it works for me) but I'm sure there are some lurking issues to find. Enjoy

There are HAT boards that exploit the ability to power an RPi via the GPIO pins. Basically you power the HAT board not the main board, and this means the IR sensor remains powered and able to recieve a power-on command when the main board is powered off. Have a look in some of the larger Pi reseller catalogues online and you'll find them.

The only time I've ever seen people trigger this sort of behaviour - they have been routing their traffic through Tor - which causes GeoIP to change with abnormal groundspeed and this (and other abnormal behaviours) triggers the captcha. It's part of our anti-spam defence and it will not be turned off.

/storage/.config/autostart.sh is run at userspace boot, so (sleep 10 && background the commands)& that you want to run and put them there, or create a systemd .service file in /storage/.config/system.d/routes.service with the commands you want, with dependencies on connman so the network is up before the commands are applied. LE has non-standard packaging - you cannot apply persistent network config, but there are ways to persistently (re)apply config.

First thing to do is create an image (dump) of the SD card .. if this is possible. Then you put the SD card somewhere safe and concentrate on trying to recover data from the image. Linux has numerous data recovery utilities that can look for raw data on the card/image. If you cannot get anything from the card .. the data is gone. SD cards a pretty reliable these days, but everything has a lifespan, and there are only two kinds of computer user: a) people who back up their stuff all the time, and b) people who haven't lost all their data yet.

CPUs and boxes got more powerful in recent times so the price points have remained higher .. $70-$90. The cheap devices are still S905X/D based and there's lots of stock being cleared.

I missed the Indigo reference in the original post. If piracy add-ons break .. that's brilliant.

Two choices:

a) Wait patiently for add-on creators to udpate their add-ons to be Py3 compatible for K19.

b) Run LE 9.2 instead of Milhouse pre-Alpha K19 code - the bleeding edge is bloody.

I'd guess that ConnMan wants to have a deafult route and will add one back if it detects it's missing. If you put connman in debug mode stop the service and restart manually with -d in the command and tail the journal you'll probably observe that behaviour.

I'm no expert on routing things, but can you change the route instead of delete it? .. and what's the purpose of deleting it?

The best option in the $50 range is an RPi4 (2GB or 4GB) with a Kodi flirc case. Software is still evolving (no HDR or high bitrate audio yet) but those will come and it's more reliable then the Amlogic and equivalent Rockchip hardware that's kicking around. Most of the 'good' new box devices are some way above your price point.

I've no idea what the issue is, but it's best to run the GUI at 1080p with 4K modes (23.976/24/50/59.94/60) in the whitelist for playback. RPi4 may be a leap forwards in terms of Pi hardware and processing but it's still a low-power ARM board.

Which Xaomi device was it shipped with?

I've pinged the maintainer. The workaround will be to create another $PROJECT entry in packages/linux/package.mk so that NXP project is compiled using an eariler kernel that the patches were generated agaisnt. Until a proper kernel bump is done.

S905 does not support HDR, the -H means the chip is widevine/playready licensed.

Scraping issues are frequently caused by people not following "the Kodi way" of structuring files/folders. Put each movie in it's own "moveiname (YYYY)" folder under the (source) root and things should be fine. Stuff everything into a single folder and .. expect some scraper issues.