Simple answer is no. Drivers need to be already there in the image you install - and it sounds like they are.
Posts by trogggy
-
-
There's no clean way to do that AFAIK. You can physically move addon folders in and out of /storage / .kodi/addons, then use the built-in kodi 'updatelocaladdons' function (or restart kodi to update) and if necessary enable via json. It's certainly possibly via a script, but it would be a lot more effort for a one-off than installing a vnc.
Before krypton it was just a case of dropping folders into place, but there were deliberate changes to make that more difficult.
-
Any reason not to use a vnc?
-
As long as the scraper isn't down it's usually about naming.
For instance - stick 'Professor Green tvdb' into google and you'll find the tvdb has these docs under 'BBC documentaries.'
The name on the main tv show folder needs to match the name the scraper uses.
-
Have a look in settings > system > Input > peripherals
Is your cec adapter enabled?
If it is either disable it or take a look in settings for the setting when the tv is switched off.
-
You don't run a web-interface within kodi - you just set the addon you want to use (in estuary that's found in settings / services / control / web-interface) and connect from your browser. The right one should appear.
It's not very intuitive.
-
Probably you mean "open" and if that's greyed out, you probably need to enable that add-on. Depending on which kind of add-on we are talking about. Hence the question which add-on it is.
Just to add to that... if you've 'installed' an addon but 'open' is greyed out because it's not enabled...
how did you install it / them?
If you install from a repo or install from a zip file (via the gui) anything you install should be enabled by default.
Any other (ie officially unsupported) way leaves addons disabled, so you need to enable them separately.
-
The obvious answer is 'Don't switch it off.' Given the pi's tiny power consumption why would you need to?
-
The GUI dependency incompatibility says you've used a different version of skin.estuary - most likely you've used the latest (leia) version from Github and tried to install in krypton?
If you copy estuary from your own install (as in post 1 step 1) you're guaranteed to have the right version - and any customizations specific to libreelec (if there are any). You can no doubt find the same version on github, I've just found it easier to dig into my install with WinSCP.
-
For people saying SMB is working could you possibly mention what OS your server is running? Thanks.
There's a glitch in Millhouse builds at the moment - smb doesn't play nicely with windows shares if passwords aren't used. Might be the same issue...?
-
Editing addon.xml doesn't change the menu - you're just changing the skin name / id / version etc. For editing the skin you'll need to find the right files in the skin.estuary/xml folder.
Maybe start here:
-
I'm assuming you're using krypton / Estuary (and want to stay with Estuary)...
Your issue is that the skin is part of the initial install, so it's somewhere in the image in your flash partition. It can't be edited directly, you need to copy it to somewhere else, muck about with it and then stick it in the storage/.kodi/addons folder.
Option 1: edit Estuary
1. Copy the skin.estuary folder from usr/share/kodi/addons/ to somewhere you can edit it. WinSCP can do that.
2. Open skin.estuary/addon.xml - bump the version number (so it won't be overwritten). Notepad++ will do that.
3. Make your changes.
4. Zip up the folder
5. Install from zip
Your estuary skin has the changes, but won't update.
Option 2: make a new skin
Step 1 as above, then:
2. Rename the skin.estuary folder to eg skin.estuarymod
3. Open skin.estuarymod/addon.xml in notepad++, change the addon name to 'Estuary Mod'.
4. In notepad++ use the 'search in files' / 'replace in files' function to change every occurence of 'skin.estuary' in your new skin folder to 'skin.estuarymod'.
5. Make your changes
6. Zip up the folder, install from zip, switch to new skin.
This way you have a cloned modified estuary, but can still switch back to estuary. Estuary will update, the clone won't.
Option 3: use a custom version of estuary
Look in the kodi forum - there are several versions of estuary with lots of customization available. Install / try one of those. As long as you install from a repo the new skin will be updated automatically.
-
I responded 2 hours after he first posted.
No point asking members about any MiniM8sPro s905 or any MiniM8s on page #1 as these boxes are all different depending on the date purchased as to what the hell is inside the Generic plastic case or who on Flebay or scAmazon gets the box from. #79
No response = nobody advised him to buy it.
So how has he been BUM STEERED by this thread?
-
Another member BUM STEERED by this Thread.
If I'm Hijacking this thread, it's done to help members who stumbled here.
As I read it:
1. He asks if anyone's tried the box (post #73).
No response.
2. He buys the box anyway (#76).
The wifi chip turns out not to be compatible (#78).
3. You post that he's been misled here.
What have I missed? Who told him the wifi would work?
If anything - because he's documented it - the next person to read the thread will be better informed about that particular box. No?
-
If I use minipartitionwizard to look at a freshly imaged 16gb SD, I see a 512mb LIBREELEC partition, a 32mb Other, and 14.2GB unallocated
Is that normal? I flashed it win32diskimager.
Normal. On first boot the 32Mb expands to fill the card with an ext4 partition.
-
switch to a highly unstable build where "all" addons are broken isn't really an option
(also the same thread is at kodinerds with "different" infos)
We must use different addons.
-
yes it is in that builds, afaik nowhere else
Am I missing something here?
What's wrong with trying a Millhouse build then?
I've re-read the op several times, and I can't see why that's not the obvious thing to try,,..?
-
yes but still not merged and this would also only affect Kodi18
It's in the latest Millhouse builds. And the OP is about using v18.
