v17 LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166) +---- Thread: v17 LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) (/showthread.php?tid=269814) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
|
RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-05-28 (2016-05-28, 13:13)Shanyel Wrote: Tried that. I do get replies from all pool.ntp.org clusters, though the date is incorrect... "ntpd -w" won't set your date but you should see an "offset" calculated which is the difference in seconds between the correct date/time and your current system date/time - if the offset isn't being calculated correctly for pool.ntp.org then I don't know why that isn't working. If you have the same issue with OpenELEC/LibreELEC release builds then it's not a test build issue. If it's only an issue with these test builds, what build does it start etc. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - User 99401 - 2016-05-28 (2016-05-28, 13:39)Milhouse Wrote:(2016-05-28, 13:13)Shanyel Wrote: Tried that. I do get replies from all pool.ntp.org clusters, though the date is incorrect... I meant, i got no timeout, hence interent is fine... It was OK with previous builds on LibreELEC as far as I recall, let me go back and see whether I can come back where it started... RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Little_Kitty - 2016-05-28 (2016-05-28, 03:58)Milhouse Wrote: @Little_Kitty: Given the above, if you have set the correct timezone but still have incorrect time (your date is "correct" purely by chance, something that will stop being the case in future once systemd is not built on a daily basis, and probably will be incorrect if you reboot after midnight) then I can only imagine that you do not have a functioning internet connection and will need to look at the rest of your network to determine where the fault lies. it showed wrong time and date. But i got it fixed now. i had the timeservers setup on my router. but no idea why it didnt send the info to the PI. So i setup NTP specially for the PI IP on my router as the PI has a static IP. i cant use pool.ntp on there i have to put in IP address so i did. When i now start it it show the correct time/date. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Little_Kitty - 2016-05-28 (2016-05-28, 00:13)Milhouse Wrote: connmand handles ntp. 1)TIMEZONE=Europe/Amsterdam ( which is correct) 2) http://sprunge.us/BMUH 3) http://sprunge.us/YidW 4) http://sprunge.us/ViFQ 5) http://sprunge.us/fOUg RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Bor_NL - 2016-05-29 I have a issue while switching channels in dvblink PVR with #0527 build. First channel works ok but switching to the 2nd or 3th channel it gives a blank screen. No problem whatsoever with #0526 build. Some logs : #0527 http://sprunge.us/eUij #0526 http://sprunge.us/WMMA Any other logs that could help ? Thx for the hard work ! RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-05-29 (2016-05-29, 10:21)Bor_NL Wrote: Some logs : You don't have debug enabled. Can you enable debug and "video" component specific debug and capture a log from #527. I suspect it is the preroll commit but can't immediately think of the failure mode. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - MONSTA - 2016-05-29 Hi Here a video from phone https://drive.google.com/file/d/0B9_XmyOyllHVOENvR0Rzd2JDQ1U/view?usp=sharing Massive artifacts with hardware acceleration. Thanks RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popel - 2016-05-29 Hi, new to this forum. I use the libreelec builds for my rPi2, but the last build I can use is #505. Newer builds update, but I don´t get a picture in Kodi. I can connect via smb/ssh and downgrade to #507 and it works again. Also for newer builds there is no connection for Yatse (remote). If you tell me which, I can upload the logfile, but there are 10 of them. (And where to upload it) Another problem is the keyboard layout: Changed it to German QWERTZ, but when I use my keyboard it is still Englisch QWERTY. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Bor_NL - 2016-05-29 (2016-05-29, 12:42)popcornmix Wrote:(2016-05-29, 10:21)Bor_NL Wrote: Some logs : I hope i've done it the right way this time. http://sprunge.us/WGPZ RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-05-29 (2016-05-29, 14:55)popel Wrote: I use the libreelec builds for my rPi2, but the last build I can use is #505. Newer builds update, but I don´t get a picture in Kodi. I can connect via smb/ssh and downgrade to #507 and it works again. This isn't clear to me. You seem to be saying #505 is the newest build you can use, but #507 also works? Is that just a typo, and #505 is good, and #506 is bad for you? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popel - 2016-05-29 Oh sorry. #507 is the last that works for me! From #508 it begins not to work RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-05-29 (2016-05-29, 16:56)popel Wrote: Oh sorry. #507 is the last that works for me! From #508 it begins not to work Okay, main change there was splash video related. Do you normally have a working splash video when booting? Is it the default LibreELEC one, or have you customised it? Does disabling the splash video fix the newer builds? Code: touch /storage/.config/splash.disable" RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popel - 2016-05-29 No, I use the default builds. Looks like there is no splash video, wo I will try to disable (learning by doing for me) €: Worked!! Thanks a lot! But how will I be able to use the splash video? or was it just missing? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-05-29 (2016-05-29, 18:32)popel Wrote: €: Worked!! Thanks a lot! But how will I be able to use the splash video? or was it just missing? Milhouse can probably help here, but it sounds like perhaps the splash video file is missing or corrupted. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-05-29 (2016-05-29, 18:32)popel Wrote: No, I use the default builds. Hmmm, a missing splash video should not block Kodi startup. A non-standard splash video could delay Kodi startup if the video is ridiculously long. Not sure if a corrupt video file might cause problems - if this is possible, then obtaining a copy of /storage/.cache/splash.h264 might be useful so that it can be debugged further. What is the output from the following commands: Code: ls -la /storage/.cache Also, try the following which should reproduce "blocked Kodi", then paste the results: Code: rm -f /storage/.config/splash.disable To "unblock" Kodi: Code: touch /storage/.config/splash.disable |