![]() |
OpenELEC Testbuilds for RaspberryPi (Kodi 16.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: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) (/showthread.php?tid=231092) 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
|
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-16 @M32134c: The PPTP change in the last build has no effect on OpenVPN so you'll need to provide more information (debug log (wiki), dmesg etc.) or debug this one yourself - there's no obvious reason why it should stop working in #0715b so please double check your network. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - wezley98 - 2015-07-16 Is anybody else getting issues with third party themes since #710, I think the theme settings changes have broken something with old themes, testing with Arctic Zephyr and Titan, Confluence works fine. http://sprunge.us/gYYd This line concerns me: 09:59:06 103.315598 T:1966940160 WARNING: CSkinInfo: failed to load skin settings When loading the skin kodi locks up the interface but doesn't crash (no crashlog), #709 is the last build third party skins work for me. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - M32134c╘ - 2015-07-16 (2015-07-16, 09:49)Milhouse Wrote: @M32134c: The PPTP change in the last build has no effect on OpenVPN so you'll need to provide more information (debug log (wiki), dmesg etc.) or debug this one yourself - there's no obvious reason why it should stop working in #0715b so please double check your network. Yea network is fine once i revert to 0714 they are working. I tried reinstalling plugins after upgrade and still no go. Openvpn does nothing when i open and the openelec dev update opens but when i select a build to download it just closes. Bear with me im new to this i think this is what you want i enabled debug log and tried to run them here is results ![]() http://sprunge.us/daNP edit Another thing i noticed is the progression bar on the top right when copying files in file manager is missing. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - MrNice - 2015-07-16 (2015-07-14, 14:36)Milhouse Wrote:(2015-07-11, 19:12)MrNice Wrote: Here is the screenshot of the window with "Add music". Version #0714 When I am on the menu bar window without activity (waited 20 s) ssh/top %CPU kodi.bin is 9.5-15.7 %. When I am on the "Music, Music add-ons, Add music" list without activity (waited 20 s) ssh/top %CPU kodi.bin is 8.3-13.6 %. When I am on the "Media info" window not playing no activity (waited 20 s) ssh/top %CPU kodi.bin is 8.6-15.1 %. When I am on the "Media info" window playing 2ch/16/44 (waited 20 s) ssh/top %CPU kodi.bin is 24.6-27.3 % When I am on full screen playing 2ch/16/44 (waited 20 s) ssh/top %CPU kodi.bin is 10.0-18.9 % So everything looks OK now, well done! Many thanks for your commitment RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - startv - 2015-07-16 TO Developers Can you add the “Prefer PTS timestamps” option into playback video settings window? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-16 (2015-07-16, 11:30)wezley98 Wrote: This line concerns me: I believe this is harmless, and simply indicates that the settings from guisettings.xml have already been migrated into the addon folder settings. (2015-07-16, 11:30)wezley98 Wrote: When loading the skin kodi locks up the interface but doesn't crash (no crashlog), #709 is the last build third party skins work for me. You're getting a SQL error in your log - a debug log might have revealed more. I suspect your addons db may need to be deleted. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-16 (2015-07-16, 15:06)M32134c╘ Wrote: Another thing i noticed is the progression bar on the top right when copying files in file manager is missing. Yes, something else broken by the ApplicationMessenger change - should be fixed in build #0716 (when I upload it). RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-17 New OpenELEC Isengard build #0716: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (b726891e, changelog) and tip of XBMC master (106d5517, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - M32134c╘ - 2015-07-17 Everything i mentioned all set now, thanks RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - M32134c╘ - 2015-07-17 I noticed but forgot to mention is there is no keyboard cursor when typing not big deal just giving heads up RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - zaphod24 - 2015-07-17 So I've been experimenting with the new advanced deinterlacing for 1080i content. Last night I had gpu_freq=400 and force_turbo=1 and watched TV for ~2 hours. Everything worked great, but a few minutes after watching some recorded TV I decided to navigate around and watch something on live TV. At that point, the interface did some weird stuff where it would flash during navigation like it was going to move around but then it didn't. I tried ssh to reboot but got some weird messages that it couldn't stop kodi. I finally just cut the power. Now I'm using core_freq=400, v3d_freq=400 and force_turbo=1 so we'll see how far that gets me. Just didn't know if anyone else had the weird navigation freeze. That is the first time I've seen that, but I've not overclocked anything until now. I've got a good power supply (http://www.newegg.com/Product/Product.aspx?Item=9SIA5YB21W9092) so I don't think that is the issue and I've never see the red or rainbow square in the upper right corner. All of my 1080i60 MPEG2 content from live TV works great with the advanced deinterlacing. I did notice that a high bitrate h264 sample I have (Georges Bizet - Carmen-007.mkv, I can't recall where I got it but it was for testing imx6 deinterlacing) was too much for advanced deinterlacing. The file is 270meg and would take a long time to upload anywhere but the mediainfo for that sample is at http://sprunge.us/gXBT RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-07-17 (2015-07-17, 16:13)zaphod24 Wrote: So I've been experimenting with the new advanced deinterlacing for 1080i content. Last night I had gpu_freq=400 and force_turbo=1 and watched TV for ~2 hours. Everything worked great, but a few minutes after watching some recorded TV I decided to navigate around and watch something on live TV. At that point, the interface did some weird stuff where it would flash during navigation like it was going to move around but then it didn't. I tried ssh to reboot but got some weird messages that it couldn't stop kodi. I finally just cut the power. Possibly too high an overclock. Increasing over_voltage may help. Reducing gpu_freq may help. We've got some ideas to improve performance (trying to improve sdram utilisation), so hopefully it will run with lower overclock in future builds. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - zaphod24 - 2015-07-17 That would be great! I try not to overclock mine since it can lead to instability and makes you wonder if you really found a software bug or if the PI just got too hot. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - M32134c╘ - 2015-07-17 Same thing just happened to me ill up voltage one more notch RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - zaphod24 - 2015-07-17 So far I've avoiding setting the over voltage so as not to set the warranty bit. Be interesting to see how your PI gets along after running for a bit. |