Posts by chewitt

Are you installing the YouTube add-on from the Kodi repo or from somewhere else?

We believe there is a memory leak in Amlogic builds as we see OOM issues on several devices (and sooner on ones with 1GB RAM) but we haven't been able to pin down the cause yet. No guarantees that's the issue though. I'm also conscious the 3.10 kernel used on older WeTek devices like the Core hasn't had quite the same level of developer love as the 3.14 kernel.

Each time someone comes up with an unpack/hack/repack/share modification the staff sigh deeply and another unicorn dies. Doing it for you own consumption if fine, but if you want to publicly share things you should be making an effort to learn the build-system and compile things properly from sources. This would also ensure you can easily publish your work on GitHub so that others can collaborate on the effort or benefit from it, with the added bonus of honouring your GPLv2 license obligations.

Thread locked. If you want to discuss hacking "ROMS" for other OS/platforms please do it in a more appropriate forum. Thanks.

Please post the FULL log not the bits you think are important, there is other information we want/need to see. Also use the OS log paste function so we don't have to scroll stuff in forum posts.

I have a ~5 year old Netgear WNDA3200 stick; they were given away (bundled with an ADSL router) by an ISP in the UK called "Virgin" (same brand as the airline; their logo is on the device) and lots of them found their way onto eBay for $10-15. It has Atheros AR7010+AR9280 inside. The Netgear WNDA3100 v1 is the Netgear brand version of the same devce, but there are now 2-3 newer versions and I have no idea what chips are inside those.

Core uses the add-ons we build for WeTek Play (same kernel etc. so they're compatible) but the folder alias was missing on the webserver. It should be working now if you try again.

feedvalidator.org is barfing on the cipher configuration used in our certs. We have certs from letsencrypt installed on the servers, although we front-end things with cloudflare who substitute their own versions ~ both orgs know what they're doing and issue valid certs. Most likely cause for the error they show is an outdated version of OpenSSL on their server. I'd guess the issue you're seeing on your RSS reader has a similar cause as "it works for me" in Vienna on macOS. There have been lots of fixes and changes to the default cipher configurations in SSL suites in the last 24 months so your OS or the app (if libs are embedded) need to be recent else things break.

No idea. I'll share opinion on drivers but I don't recommend specific products unless I've used them personally.

Install a current alpha build and test again.

There is a significant difference between rooting a TV to add another application or fiddle with configuration, and rooting it to run a replacement OS on the internal TV hardware. Unless someone would like to donate a bunch of 65"+ 4k OLED TV's to the team for testing and experimentation (we're open to offers!) it's not likely to happen.

The ability to disable lirc from LE settings will probably appear in the next alpha build.

I've no objection to a sample systemd .service file being included as we do for some other things (and some wiki documentation) but VLAN's are a niche requirement so there's no need to complicate the GUI for the other 99.99% of users.

It's originally intended to show an X.X.X format number so once we pad it with "blah blah (community) X.X.XXX blah" it overflows. It's not an issue once we arrive at 8.0.0 (official) so it's known but not very high on the priority list

Find something that uses the Atheros ath9k driver, it's probably the best written one.

That's the one that only works for 50% of users due to the hard-coded config file. Mediatek need to get their sh1t together and write a driver against the proper (modern) kernel interfaces. Drivers like that one went out of coding fashion c.2004.

It's not really needed with LE as most (all but one) of our images boot directly into Kodi where the first-run wizard guides you through connecting to a network. All you'd do is replace one typing opportunity (password) with something earlier in the boot process where you'd need to input two things (password and SSID) and from experience it's better to reduce the opportunities for user input; too many fat fingers on keyboards

It's not the panacea you are seeking. Amazon changed the widevine security level on their streams and now require decryption of video in addition to audio, and this effectively kills the capability as it's not possible to software decode the streams on all the low-power ARM devices which make up the majority of our (and Kodi's) userbase.

It's not a dead topic, but right now we're back to the start and have to figure out another approach.