Posts by chewitt

AFAIK the business was mothballed and eventually the assets (the intellectual property) of FiveNinja's were sold so nobody really has interest in running a defunct forum these days. If you have questions post them in the subsection here and someone will probably answer.

S905D and S905X are the same chip except for S905D supporting an external PHY (so boxes can have GB ethernet, not that all do) and the interface for internal tuner devices. The difference between SDIO and USB tuners will be negligible. More significant, especially for how weak signals are handled, will be the drivers. I cannot provide a validated answer (and i'm not sure there is one) but as a rule the not-in-kernel drivers for SDIO chipsets used in Android boxes are worse than the more widely used mostly-in-kernel USB drivers.

I wouldn't spend money on a cross-grade at this point. If you want to do an upgrade, it's time for a NUC and/or a network SAT>IP device with multiple tuners (so pre-selection is possible) and no impact on the local system.

Raspberry Pi is our largest user group (consistently around 75% of our active installed base) which means more people to report (and often fix) issues, and the Pi Foundation has long been attentive to the needs of Kodi - because great support helps to sell more boards to support their education mission. That said, the experience for 1080p/H.264 should be pretty consistent everywhere assuming the same media being played back on the same TV screen over the same USB drive or NAS/network. It's only once you stray towards exotic encodings, 4k, HDR, wonky TV's and bad network connections that you'll start to discover differences between platforms.

I've been told that udev is setting a property that marks it as removable and Kodi displays icons based on that propery, but I'll need to dig further to figure out what/where and whether it can be changed. This is really a cosmetic level issue; the drive is correctly mounted and 100% usable, there is nothing 'broken' in that sense.

No idea about the dual-audio patch. Last time I saw that code (a couple of years ago) it was a fcuking horrible hack. If it works, it works. If it doesn't work .. not our problem to solve. Also hard to mind-read what you've done, so best to just build and see what happens.

In that specific case "git cherry-pick 2af9c405521db9d57fac6e9aba07f1525d7b3b27" and you'll apply that commit to your current working branch.

In that case it's a Kodi issue, and you're still in the wrong forum for reporting core Kodi issues

If you have 100 files in a scraped source and then add a new source with 100 more files, and use the Videos (non-library file browser) view to move around and play things; only the 100 files that have previously been scraped will support resume. Unless you scrape a media file to the library there is no corresponding DB entry for file state to be saved against. If you browse media via the Movies/TVShows library views you will always get resume points because (by definition) everything's in the DB.

^ not an authoritative statement, but an educated hunch on what's happening.

You can't, because LE has no 'desktop' environment. Enable SSH and use an SFTP client (e.g. WinSFTP).

No idea then. It's probably better to ask the question in Kodi forums where developers more familiar with the innards of Kodi are.

Skin issues need to be taken up with the skin author via their support thread in Kodi forums. Anything in that department isn't going to be an LE issue that we'll understand or be able to fix (not our forté).

ATV1200 uses an Amlogic 8726MX chipset and I'm not aware of anyone offering images for those chips now. It's possible to find S905X devices on sale for $16-30 so community developers don't take much interest in older devices (and older hardware is a pain to support).

Maybe Kodi assumes any device in /var/media is removable and shows the USB icon against it? .. I've asked in team chat but nobody answered the question yet. It's not important. Just configure a source for /var/media/Films and use it

Some Kodi skins support additional customisation options (or just hack extra menu items in, which is also what some users do) but the default (Estuary) skin is deliberately designed to be simple and it doesn't support that level of tweaking.

<blue>System.Exec("(/storage/LampsToggle.sh)&")</blue>

No idea if this ^ works, but in shell scripting (/path/to/command)& spawns a new shell process and backgrounds the task.

/dev/sdb1 on /var/media/Films type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=1024)

the only issue I can see is PEBKAC .. because /dev/sdb1 is mounted

[    3.003630] ata3.00: ATA-8: ST2000LM003 HN-M201RAD, 2BE10001, max UDMA/133
...
[    3.096836] scsi 2:0:0:0: Direct-Access     ATA      ST2000LM003 HN-M 0001 PQ: 0 ANSI: 5
[    3.097242] sd 2:0:0:0: Attached scsi generic sg2 type 0
[    3.097550] sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[    3.097556] sd 2:0:0:0: [sdb] 4096-byte physical blocks
[    3.097602] sd 2:0:0:0: [sdb] Write Protect is off
[    3.097607] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    3.097720] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.159969] sd 2:0:0:0: [sdb] Attached SCSI disk

^ definitely *not* a USB device

run "parted -s /dev/sdb unit s print | paste" then "blkid | paste" and "mount | paste" ..

You look for the very limited number of S8XX install thread in this section of the forums and hope that someone cobbled together a working image with a device tree that at least supports Ethernet (wifi is always a bonus). No need to type in codetext.