v17 LibreELEC Testbuilds for x86_64 (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: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52) +---- Thread: v17 LibreELEC Testbuilds for x86_64 (Kodi 17.0) (/showthread.php?tid=269815) 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
|
RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - Thomas233 - 2016-06-07 (2016-06-06, 23:57)Milhouse Wrote: Build Highlights: Wahhh great...finally....thank you very much guys for your efforts +1 !! RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - fritsch - 2016-06-07 (2016-06-07, 18:46)Tequilla9 Wrote: Here you are: Thanks, please turn on debuglogging and play the file for longer (10 minutes), please., don't open the codec info screen, but press a remote button every time you see the stutter. Also disable ffmpeg's component logging that is spamming us like hell. Then please only post the kodi.log - the rest is not relevant for now. RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - fritsch - 2016-06-07 (2016-06-05, 14:45)_Spook_ Wrote:(2016-06-05, 14:10)fritsch Wrote:(2016-06-05, 12:41)_Spook_ Wrote: Ok. I did not know that obviosly. Donate time - that's what is needed. RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - fritsch - 2016-06-07 @Robby77: Do: Code: touch /storage/.config/forcedisplay And reboot. Display comes up? RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - Roby77 - 2016-06-07 Watson question: Will try but if i reboot how i understand (and report) if the problem disappear cause no handshake problem or thanks to your trick ? Just to resume Forced edid but on boot i can have A)Black screen after syslinux text and need almost 2/3 reboot to have kodi gui (maybe this is the best scenario to test that trick) B) black screen after lbreelec logo...wait 15 sec ~ 2 minuts for kodi gui And also Random black screen when movie stop wait 15 sec ~ 2 minuts for kodi gui Tried also with dr hdmi solution...same problem For WAF i mapped reboot command to remote RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - fritsch - 2016-06-07 your B) issue is your personal issue and we won't and can't fix that. The random movie stopped issue is filed upstream - nothing we can do - we wait for upstream. If you care for WAF -> sell all your hardware and get an Android TV and use the netflix app only :-) As your wife won't see the difference between 23.976 hz and 60 hz, just disable Adjust Refreshrate to match video. RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - Roby77 - 2016-06-07 Between 24p and wife i prefer the first seriously (Also prefer pc architecture* for picture quality and audio hd and love oe/libreelec kodi standalone) Maybe not relevant but i have this error in log several reported Got external EDID base block and 1 extension from "edid/edid.bin" for connector "HDMI-A-1" And this in last 2/3 builds had: snd_intelhad_open: HDMI cable plugged-out Thank you RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - Milhouse - 2016-06-07 New LibreELEC.tv Krypton build #0607: Generic (Supercedes previous build) Code: # uname -a Based on tip of LibreELEC.tv master (f59ff67c, changelog) and tip of XBMC master (d1a52d1e, changelog) with the following modifications:
RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - Tequilla9 - 2016-06-08 (2016-06-07, 21:13)fritsch Wrote:(2016-06-07, 18:46)Tequilla9 Wrote: Here you are: OK, I will upload new logs in the evening. RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - fritsch - 2016-06-08 Please with the new build Milhouse just posted. RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - john.cord - 2016-06-08 Is there is reason caused by Kodi that after i boot a client all drives of the NAS gets busy? Is kodi by default set to scan some sort of file metadate or something? RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - Milhouse - 2016-06-08 (2016-06-08, 12:54)john.cord Wrote: Is there is reason caused by Kodi that after i boot a client all drives of the NAS gets busy? Is kodi by default set to scan some sort of file metadate or something?Try with a "clean" .kodi ("mv .kodi .kodi.bak" and restart Kodi). This well ensure you have no additional add-ons, and using default settings. If problem guess away it's either a third-party add-on (watchdog?) or a setting (scan/clean library on startup?) RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - _Spook_ - 2016-06-08 @fritsch regarding my NUC6i7KYK sound issue, this might be the fix: https://downloadcenter.intel.com/download/26061/HDMI-2-0-Firmware-Update Will try it and report back RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - fritsch - 2016-06-08 Windows only ... the updater - not sure what they are thinking ... RE: LibreELEC Testbuilds for x86 (Kodi 17.0) - _Spook_ - 2016-06-08 (2016-06-08, 13:47)fritsch Wrote: Windows only ... the updater - not sure what they are thinking ... I know. Will have to make a windows drive for these kind of updates... EDIT: Oh yeah! That firmware did it! Works like a charm now. Except passthrough, but that's not a big deal for me EDIT2: Spoke to soon. Works fine in Kodi. But linux speakertest no go. But oh well. Seems like a firmware and kernel issue. Not a Kodi issue. Passthrough works on AC3 and DTS. Not DTS-HD, TrueHD and so on. EDIT3: This is the same issue as I had with the Club3D miniDP->HDMI2.0 adapter with the Paradetech PS176 chip. So it's a firmware issue. The NUC6i7KYK has the PS175 chip, basically the same chip with same firmware. https://communities.intel.com/thread/102165 explains the same thing. |