29.12.2018, 09:42
(Dieser Beitrag wurde zuletzt bearbeitet: 29.12.2018, 12:00 von gerard1989.)
Yes, of course, I tried to install each version from 1.3.6k to 1.3.6o, but pibus did not start with each of them.
Hi all, small question
|
29.12.2018, 09:42
(Dieser Beitrag wurde zuletzt bearbeitet: 29.12.2018, 12:00 von gerard1989.)
Yes, of course, I tried to install each version from 1.3.6k to 1.3.6o, but pibus did not start with each of them.
29.12.2018, 12:41
try to set back the system name to osmc.
29.12.2018, 19:00
(Dieser Beitrag wurde zuletzt bearbeitet: 29.12.2018, 19:01 von gerard1989.)
(29.12.2018, 12:41)harryberlin schrieb: try to set back the system name to osmc. It worked, but why? I changed the name to osmc, and the pibus LED began to flash. A am installed plugin.script.ibuscommunicator-1.3.6o.zip with sustem name osmc, it worked. log files of kodi with ibuscommunicator-1.3.6k and ibuscommunicator-1.3.6o attached. Thanks in advance! Sorry, what about with differens system name?
29.12.2018, 19:54
i should try to check the system with other method.
29.12.2018, 23:39
(Dieser Beitrag wurde zuletzt bearbeitet: 29.12.2018, 23:53 von gerard1989.)
(29.12.2018, 19:54)harryberlin schrieb: i should try to check the system with other method. Maybe implement the system identification like Peter Zelezny did when installing pibus software? Code: uname -a | grep -i osmc > /dev/null As far as I understand, this is a mistake in system identification, since you entered the system definition by host name, and if the host name is not osmc, then the installation principle for another system, for example LibreElec, is launched. Did I understand this situation correctly?
30.12.2018, 23:19
try version 1.3.6p.
this is my method: Code: def is_osmc(): i will change to this: Code: def is_osmc():
hey Harry, got 2 small questions:
1) Is it possible that the new skin will be as it was before? I just updated to the latest OSMC, then added your plugin and skip from github repo, everything is really really small, barely can read. Before elements were much larger. 2) Is it possible that when I press next\prev keys on my steering wheel it will invoke next and prev buttons of Player window (round player with round buttons), cause right now it tries to switch to the next track of current playlist, which is actually empty, cause I'm streaming music from my iPhone to RPI via AirPlay. When I press "Next" via the Player of Kodi - works like a charm, it changes track on my phone. I guess I can set my custom action for button 1, 2 for example with such command: PlayerControl(command), where command = Next or Prev? edit: ok I just tried this - PlayerControl(Next) binded on hold of button 6. Works great now the question is: can you guide me what I need to change in the code to make this happen when I press steering wheel next\prev buttons. Danke! edit2: guess this - btn_stw_up_rel()
03.06.2019, 18:35
1. kodi 18 skin is in progress. download on github from subfolder.
2. prev / next should work already, when pi is active. the command is the simple kodi action.
03.06.2019, 21:28
1. I already downloaded new skin. everything is really small.
2. they work only if I play music from flash drive, cause it is using playlist. If I use AirPlay or Bluetooth it is not working. Custom command on buttons work well (e.g PlayerControl(Next)), but I want to make this for steering whell as well. need to change some code of your plugin.
03.06.2019, 22:26
(Dieser Beitrag wurde zuletzt bearbeitet: 03.06.2019, 22:37 von harryberlin.)
1. don't have time for editing the skin.
2. Works PlayerControl in every case? So i will check for an other command. try 1.3.6v |
|