Posts by LE23

    try NFS...another option is install zeroconf/bonjour server on your windows pc...it's kind of the smb version of Apple devices

    NFS is not well supported in Windows; for example, I cant find a GUI interface, so you have to use terminal just to mount shares. Windows native protocol (SMB) is only slightly less problematic: there are many different versions, and they often dont work right together 100%, particularly across different OS platforms. Sometimes multiple machines will contest for the status of master browser, and changes in network topology may require a reboot of one or all participants to get things working again. Bonjour / Zeroconf has none of these issues. Once its been set up correctly, Bonjour is the most reliable way for applications on different machines to find shared resources on the LAN automatically. It's worth a try if you cant get anything else to work. I wrote a short guide for this on Windows a while back,* and even if you dont end up using Bonjour, there might be something which helps you to see what is wrong. The advantage of Zeroconf tools like "Bonjour browser" is the ability to see whether shared services have been configured properly, which helps to narrow down the source of the problem... and you can get those tools for any major platform, including Android. Also, dont forget to (temporarily) disable the Windows Firewall and run the network troubleshooter if nothing works at all. I never had much problem getting Mac & Linux machines to communicate as I have with Windows, regardless... and sharing folders on Windows is a lot more buggy than browsing shared resources from Windows. That's why I say, if you are using an old, spare Windows box as a file server, just put Linux on it instead and your life will be easier.

    * RE: SAMBA problem

    Thanks for all the suggestions, but I'm not going to put another second of effort into getting my LE box to work properly.

    I feel your pain, Windows networking is crazy :S

    Quote

    This thread was intended to solve all the networking problems for everyone by suggesting adding a small util to Windows,thus bypassing anything that Windows would normally require.

    It's my opinion that Bonjour for Windows is the closest thing to what you have in mind, but you will still have to contend with all of the other bugs in Windows file sharing, Homegroup, the crappy firewall, et cetera. This is why people often give up.

    Thanks for the tip -- it's nice to see that you can assign actions to those colored Teletext keys. But I dont see the Listbox / Menu key in the Keymap Editor, so I cannot assign a function to it. Incidentally, I discovered the problem is even worse on a Mac: the back button on the remote does not function either, in addition to that menu key. So the default key map for USB keyboards in Windows somehow needs to be duplicated on Mac and Linux. In the interest of being more user friendly, I think it would make sense if the key mapping for remote controls was standardized across Kodi on all platforms, to every extent possible, so you dont need separate documentation for each platform, and everything "just works".

    If anyone associated with the project feels overworked, they absolutely should step away for a while. But I dont see people complaining that someone else has gone on holiday. I dont know where this accusation is coming from, and I dont believe for a minute that the forum was shut down to give anyone a break from their busy schedules. That's simply not credible: If you want time off, you dont need to wait for April fools. This just sounds like an excuse for exercising bad judgment. If you have an international user base, they are not all going to understand your strange traditions.

    Just like you, I can only speak for myself when I say that I never expect a response, and I never complain if I dont receive a reply. And I dont see other people complaining about being ignored either. So I honestly dont know what you are talking about when you claim that people are demanding commercial-grade support. I always take time out to help others when I see that it's needed, and I see many people doing the same. Now some may be obsessed with Kodi, that's true -- but I dont think it has anything to do with selfishness:

    As clunky as BBS systems were, it was still nowhere near as frustrating as Kodi can be. In my opinion, serious Kodi users are masochists who torture themselves with software that's not user friendly in order to break free from the tyranny of proprietary platforms that wont let you do what you want. Many are already at their wit's end, and breaking the forum was a bad move. If you're trying to gather support, that is not a solution.

    I think this is reasonable advice which the staff should be willing to consider. When you claim that it's just a few "familiar faces" who feel this way, it sounds like you're trying to deny reality: From what I observed, I think at least 50% would have voted against shutting down the forums (particularly the parts where add-on documentation is stored that is not available anywhere else.) I just think it's really bad public relations to blame the user base for your mistakes. But hey, if Zuckerberg can get away with it, what do I know.

    A lot of the users were just annoyed that the forum was shut down for no reason — on a weekend — when people normally file bug reports, perform maintenance on their Kodi box, and fix things for friends or family. It turned into a big fiasco with a few leading members of Team Kodi growing increasingly nasty towards visitors who expressed frustration and disappointment, with contributors being called selfish parasites, moaning old farts, and other such nonsense. It looks like the thread was removed.

    I’ve decided to discontinue support for it.😁

    Now that was the only funny thing I've seen and heard all day. 😁

    have nearly no troubles using WiFi. Maybe once in a while it has a short hickup

    Just thought it might be worth mentioning that bufferbloat could be an issue and it sometimes can be addressed at the router, for example:

    "Working software is available in LEDE firmware that runs on off-the-shelf routers, x86 boxes, and embedded systems."

    Make-Wifi-Fast Project - Bufferbloat.net

    (LEDE is to OpenWRT what LibreELEC is to OpenELEC)

    The 'other OS' needed to finish the installation is libreelec. That free space is filled on first boot.

    Oh. Maybe there should be a "read.me" file which explains that (and a notation in the creator app) so people dont go looking for a partitioner to resize it manually. It seems I have another problem then: this buggy old Wetek box refuses to boot from the SD card. Strange thing is I can *read* the card under Android but I cannot boot it even when the ROM says that its trying.


    Update: For some inexplicable reason the boot loader just decided to stop recognizing the SD card. (The index of complaints about this on the Wetek forum is 10 pages long.) The issue seems related to the "new" v1.7 bootloader which provides internal/external boot selection through the remote. Reflashing the defective Uboot 1.7 only resulted in a boot loop. Had to revert to Uboot 1.6 to solve the problem.

    WeTek OS 1.1.7 for WeTek Play [14/03/2016] - Page 4 - WeTek Community Forum

    I used the USB-SD Creator on my PC to install LibreELEC on a USB drive.

    That is a nice tool but I wonder of the developers what is the rationale for supporting Windows if you still need to boot another OS to finish the installation because most of the free space on the memory card is wasted (i.e. the the "resize me" message in the ext4 volume)

    made the changes to the USB using ES File Explorer

    After installing AFwall and disabling internet access for ES File Explorer, I see a lot of warnings that it wants to connect to the internet at many times when that should not be necessary. Wonder what they are up to?

    It's a Windows vs Linux thing. But there are solutions for using EXT4 via Windows. Example: Paragon...

    Paragon works but it is a very buggy solution ; for example special characters or mass deletions can crash it. Be careful using this tool in R/W mode or you could end up with a corrupted file system. They should not be charging a fee for that super-buggy beta quality software. If you can manage your Kodi installation in remote terminal mode that might be preferable.

    Posting Kodi crash log regarding original update failure


    Like it should? I'm guessing Addons27.db will have changes compared to its previous version.

    yeah, I meant to say "migrate" like it should rather than copy, cause YES, it's not necessarily gonna be an exact copy -- I got that, okay?

    Quote


    just delete Addons27.db so Kodi can upgrade via the normal upgrade procedure.

    That is exactly what happened. I do believe I said that clearly enough:

    "deleted it via SCP and Kodi recreated it"

    If Kodi recreated it, and that can only occur through auto-migration, it should be obvious the upgrade took place as designed. My question is why did it fail in the first place. If you don't know, consider it a rhetorical question - just something for devs to be aware of. I really did not need to post my solution at all, just trying to help the other guys with the same problem.


    Do a clean install?

    oh I see, its an in-Kodi issue then, not a shell script error

    kodi.log says

    Code
    21:51:08.843 T:3036082176  NOTICE: Loading player core factory settings from special://xbmc/system/playercorefactory.xml.
    21:51:08.844 T:3036082176  NOTICE: Loaded playercorefactory configuration
    21:51:08.844 T:3036082176  NOTICE: Loading player core factory settings from special://masterprofile/playercorefactory.xml.
    21:51:08.844 T:3036082176  NOTICE: special://masterprofile/playercorefactory.xml does not exist. Skipping.
    21:51:08.878 T:3036082176   ERROR: SQL: [Addons27.db] SQL error or missing database
                                                Query: SELECT idVersion FROM version

    so here is the problem:
    /storage/.kodi/userdata/Database/Addons27.db was zero length

    deleted it via SCP and Kodi recreated it immediately by copying Addons26.db to Addons27.db like it should

    then Kodi finished loading right away
    so... database migration error then. whys it only fail on some systems and not others though?

    in any case you can trap this, right?

    If Addons27.db = 0 bytes at launch -and- Addons26.db = nonzero, delete/recreate Addons27.db

    Kodi splash screen never appears
    gdb terminates & restarts every few seconds in endless loop
    issue was seen on Pi v3 and Play v1

    some possibly relevant dmesg excerpts...

    note: last 3 lines in code box above repeat continuously