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) - popcornmix - 2015-07-17 (2015-07-17, 16:55)zaphod24 Wrote: 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. You can remove the force_turbo=1 and then over_voltage is allowed without setting warranty bit. Now as long as the arm is busy enough (it may be for 1080i video, especially if PVR is enabled) you should be in turbo mode all the time when playing. If not, you can force the governor to be in turbo mode: Code: echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor (untested, but I think that may work). This doesn't set the warranty bit. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - M32134c╘ - 2015-07-17 (2015-07-17, 16:55)zaphod24 Wrote: 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. Already had at 3 upped to 4 im at 1100Mhz im not worried about overvolting not going to do any damage and by some off chance it did its only $30-35. Re: RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-17 (2015-07-17, 15:20)M32134c╘ Wrote: I noticed but forgot to mention is there is no keyboard cursor when typing not big deal just giving heads up I'll include a potential fix for that (PR7532) in the next build if it isn't already merged. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-17 New OpenELEC Isengard build #0717: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (39949671, changelog) and tip of XBMC master (2f0e73fd, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-17 Could Hifiberry Digi and Hifiberry Digi+ owners confirm if they are still having problems (as originally reported here) when using the latest build, thanks. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - M32134c╘ - 2015-07-17 Keyboards cursor is working just one thing if you delete everything you type the first letter remains visible once you start typing it goes away. (2015-07-17, 16:55)zaphod24 Wrote: 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. It didn't help I even removed my GPU OC still happened. I was watching tv and switched TV input to my pi2 and screen was black it did this twice and other times i was browsing around and the UI went all weird. Ive never had these issues with any other build but maybe something changed IDK testing #0717 ATM RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-18 (2015-07-17, 23:55)M32134c╘ Wrote: Keyboards cursor is working just one thing if you delete everything you type the first letter remains visible once you start typing it goes away. Confirmed - it appears that PR7532 requires a little more work. Cursor also doesn't appear until you start typing, when it should be visible as soon as the dialog is opened. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-07-18 (2015-07-17, 23:55)M32134c╘ Wrote: It didn't help I even removed my GPU OC still happened. I was watching tv and switched TV input to my pi2 and screen was black it did this twice and other times i was browsing around and the UI went all weird. Can you switch deinterlace method to "Bob" and remove overclock. If you still see issues then can you confirm the latest build you believe is stable? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - M32134c╘ - 2015-07-18 I switched to Bob and removed all overclocks and it still eventually freezes but i can hear my inputs being made i left it alone and eventually it goes to black screen Last build i didn't have this problem was #0714 I did run debug log with last build and it happens not sure if this will help. http://sprunge.us/OaRN RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Milhouse - 2015-07-18 (2015-07-18, 02:07)M32134c╘ Wrote: I did run debug log with last build and it happens not sure if this will help. Your crashlog is from #0715 and the crash is being caused by ApplicationMessenger - try #0715b, as that fixes the ApplicationMessenger crash. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - M32134c╘ - 2015-07-18 i did that one also still had problems i tried every release edit crap that was kodi.old log ignore it RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - M32134c╘ - 2015-07-18 Replicated it again here is the logs IDK what one is needed. Kodi.log http://sprunge.us/CMFF Kodi.old.log http://sprunge.us/UaXJ edit it happened again when i plugged in my USB thumb drive message about it mounting then screen went all crazy again maybe the ApplicationMessenger still causing problems? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-07-18 (2015-07-18, 02:07)M32134c╘ Wrote: Last build i didn't have this problem was #0714 If #07014 is definitely good and #715b is bad, and it still fails with advanced deinterlace disabled, then I think we still have issues with the ApplicationMessenger PR. There still seem to be other problems reported on that PR. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - M32134c╘ - 2015-07-18 Good to know thought i was going crazy and maybe my device had issue. Ill test new build when released. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - zaphod24 - 2015-07-18 Running 0717. Had an overclock (core_freq=500,v3d_freq=500,h264_freq=500,over_voltage=2) as well as performance for the scaling governor and advanced deinterlacing running this morning. After watching live TV for a while and then exiting, the weird menu navigation problem happened again. The temp was around 64c and this is what was in the log: 09:54:21 42978.957031 T:1967968256 NOTICE: DecodeJpegToTexture: unable to decode to texture special://skin/backgrounds/tv.jpg 1280x720 I've disabled the overclock and gone back to bob deinterlacing to see if the problem occurs. |