RetroPlayer Test Builds (updated for Nexus) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: Game support (https://forum.kodi.tv/forumdisplay.php?fid=292) +--- Thread: RetroPlayer Test Builds (updated for Nexus) (/showthread.php?tid=173361) 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: RetroPlayer Test Builds (updated for Leia) - xodi - 2018-08-18 Crashed on startup with Beta1 release, but today's nightly build works well. V/CrashDescriptorUtil( 518): extractNativeCrashFromBody inputTrace=*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** V/CrashDescriptorUtil( 518): Build fingerprint: 'Amazon/full_sloane/sloane:5.1.1/LVY48F/36.6.0.6_user_606753920:user/release-keys' V/CrashDescriptorUtil( 518): Revision: '0' V/CrashDescriptorUtil( 518): ABI: 'arm64' V/CrashDescriptorUtil( 518): pid: 30149, tid: 30169, oom: 0, name: Thread-37943 >>> org.xbmc.kodi <<< V/CrashDescriptorUtil( 518): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x19998c4 V/CrashDescriptorUtil( 518): Abort message: 'art/runtime/check_jni.cc:72] JNI DETECTED ERROR IN APPLICATION: JNI CallBooleanMethodV called with pending exception 'java.lang.NoSuchMethodError' thrown in unknown throw location' V/CrashDescriptorUtil( 518): x0 0000000000000000 x1 00000000019998c4 x2 0000007fad949000 x3 0000007fad94cdc0 V/CrashDescriptorUtil( 518): x4 4de410701f6e060c x5 0000000000000007 x6 000000000019d5ff x7 0000000000000004 V/CrashDescriptorUtil( 518): x8 0000000000000001 x9 0000000000000002 x10 4de410701f6e060c x11 0000000000000001 V/CrashDescriptorUtil( 518): x12 0000000000000001 x13 0000000000000000 x14 0000000000000000 x15 0000000000000004 V/CrashDescriptorUtil( 518): x16 0000007fb0867ad0 x17 0000000000000001 x18 0000007fad941eb0 x19 00000000019998b0 V/CrashDescriptorUtil( 518): x20 000000006f8ac518 x21 0000007f93bef760 x22 0000007fad949000 x23 0000000000000000 V/CrashDescriptorUtil( 518): x24 00000055716d8b20 x25 000000556dfc95d0 x26 0000007fad89ce80 x27 0000007f93bef640 V/CrashDescriptorUtil( 518): x28 0000000000000000 x29 0000007f93bef510 x30 0000007fad7caafc V/CrashDescriptorUtil( 518): sp 0000007f93bef510 pc 0000007fad867e08 pstate 0000000060000000 V/CrashDescriptorUtil( 518): V/CrashDescriptorUtil( 518): backtrace: V/CrashDescriptorUtil( 518): #00 pc 000000000039ae08 /system/lib64/libart.so (_ZN3art5arm6412Arm64Context15FillCalleeSavesERKNS_12StackVisitorE+60) V/CrashDescriptorUtil( 518): #01 pc 00000000002fdaf8 /system/lib64/libart.so (_ZN3art12StackVisitor9WalkStackEb+340) V/CrashDescriptorUtil( 518): #02 pc 0000000000305e6c /system/lib64/libart.so (_ZNK3art6Thread13DumpJavaStackERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEE+268) V/CrashDescriptorUtil( 518): #03 pc 0000000000306080 /system/lib64/libart.so (_ZNK3art6Thread9DumpStackERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEE+272) V/CrashDescriptorUtil( 518): #04 pc 0000000000310f60 /system/lib64/libart.so (_ZN3art10ThreadList10DumpLockedERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEE+100) V/CrashDescriptorUtil( 518): #05 pc 00000000002f228c /system/lib64/libart.so (_ZN3art7Runtime5AbortEv+444) V/CrashDescriptorUtil( 518): #06 pc 00000000000ce678 /system/lib64/libart.so (_ZN3art10LogMessageD1Ev+2684) V/CrashDescriptorUtil( 518): #07 pc 00000000000dda10 /system/lib64/libart.so (_ZN3artL8JniAbortEPKcS1_+2164) V/CrashDescriptorUtil( 518): #08 pc 00000000000de290 /system/lib64/libart.so (_ZN3art9JniAbortFEPKcS1_z+216) V/CrashDescriptorUtil( 518): #09 pc 00000000000dfe54 /system/lib64/libart.so (_ZN3art11ScopedCheckC2EP7_JNIEnviPKc+1328) V/CrashDescriptorUtil( 518): #10 pc 00000000000ee3e8 /system/lib64/libart.so (_ZN3art8CheckJNI18CallBooleanMethodVEP7_JNIEnvP8_jobjectP10_jmethodIDSt9__va_list+64) V/CrashDescriptorUtil( 518): #11 pc 00000000019ae5f0 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN7_JNIEnv18CallBooleanMethodVEP8_jobjectP10_jmethodIDSt9__va_list+48) V/CrashDescriptorUtil( 518): #12 pc 00000000019ab2cc /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN3jni7details20call_jboolean_methodEP7_JNIEnvP8_jobjectP10_jmethodIDz+120) V/CrashDescriptorUtil( 518): #13 pc 00000000019e0da8 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZNK19CJNIViewInputDevice13hasMicrophoneEv+28) V/CrashDescriptorUtil( 518): #14 pc 000000000197b87c /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN11PERIPHERALS21CPeripheralBusAndroid14LogInputDeviceERK19CJNIViewInputDevice+460) V/CrashDescriptorUtil( 518): #15 pc 000000000197a92c /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN11PERIPHERALS21CPeripheralBusAndroid15GetInputDevicesEv+168) V/CrashDescriptorUtil( 518): #16 pc 000000000197a7cc /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN11PERIPHERALS21CPeripheralBusAndroidC2ERNS_12CPeripheralsE+256) V/CrashDescriptorUtil( 518): #17 pc 00000000016f43f8 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZNSt6__ndk110shared_ptrIN11PERIPHERALS21CPeripheralBusAndroidEE11make_sharedIJRNS1_12CPeripheralsEEEES3_DpOT_+140) V/CrashDescriptorUtil( 518): #18 pc 00000000016eda98 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN11PERIPHERALS12CPeripherals10InitialiseEv+272) V/CrashDescriptorUtil( 518): #19 pc 000000000154eb54 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN15CServiceManager14InitStageThreeEv+48) V/CrashDescriptorUtil( 518): #20 pc 00000000014d8524 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN12CApplication10InitializeEv+2036) V/CrashDescriptorUtil( 518): #21 pc 0000000001266270 /da I/ActivityManager( 518): addErrorToDropBox inserted hashcode=28afee5ba86e461d320cdc1609daf6b75cfb6d24 for eventType crash. RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-08-18 The problem was introduced in https://github.com/xbmc/xbmc/pull/14308 . Thanks for reporting, I'll look into it. RE: RetroPlayer Test Builds (updated for Leia) - ghizzu - 2018-08-18 Made a quick test of the latest build. The problems with the resolution changes seem to be gone. Fingers crossed... RE: RetroPlayer Test Builds (updated for Leia) - Abbaskip - 2018-08-20 I tried the latest beta, and for the first time had some success running a Genesis game - but now can't play any videos. I get: "This game isn’t compatible with any available emulators" Whenever I select anything from my library. RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-08-20 (2018-08-20, 12:39)Abbaskip Wrote: I tried the latest beta, and for the first time had some success running a Genesis game - but now can't play any videos. Please post a debug log showing the problem happening. RE: RetroPlayer Test Builds (updated for Leia) - Abbaskip - 2018-08-21 (2018-08-20, 21:02)garbear Wrote:Yep - will try this afternoon. I had to go straight back to 18.alpha3 last night, as my wife wanted to watch TV(2018-08-20, 12:39)Abbaskip Wrote: I tried the latest beta, and for the first time had some success running a Genesis game - but now can't play any videos. RE: RetroPlayer Test Builds (updated for Leia) - quig - 2018-08-21 @garbear just in case you missed it... (2018-08-17, 04:27)quig Wrote: 1. I have a RPi3 running #816 and have noticed a strange behavior with exiting games. I use a harmony one remote and lirc. If I am playing a game (NES or SNES) and I hit the exit button on my remote, I go back to the list of my ROMS (which are hosted on my NAS). I can used the arrows on the remote to move up and down to select another ROM. When I hit the OK button on my remote, the screen flashes (it looks like it is killing the old game I was playing). I then have to hit the OK button again to bring up the list of emulators. When doing these same steps for movies, I do not have to hit OK twice. RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-08-21 (2018-08-17, 04:27)quig Wrote: 1. I have a RPi3 running #816 and have noticed a strange behavior with exiting games. I use a harmony one remote and lirc. If I am playing a game (NES or SNES) and I hit the exit button on my remote, I go back to the list of my ROMS (which are hosted on my NAS). I can used the arrows on the remote to move up and down to select another ROM. When I hit the OK button on my remote, the screen flashes (it looks like it is killing the old game I was playing). I then have to hit the OK button again to bring up the list of emulators. When doing these same steps for movies, I do not have to hit OK twice.Can you post a debug log? (2018-08-17, 04:27)quig Wrote: 1. I have a RPi3 running #816 and have noticed a strange behavior with exiting games. I use a harmony one remote and lirc. If I am playing a game (NES or SNES) and I hit the exit button on my remote, I I've added this to my list of input issues: https://github.com/garbear/xbmc/issues/79. It is something I plan to address when I do the Player Manager. (2018-08-17, 04:27)quig Wrote: 1. I have a RPi3 running #816 and have noticed a strange behavior with exiting games. I use a harmony one remote and lirc. If I am playing a game (NES or SNES) and I hit the exit button on my remote, I Can you post a debug log? RE: RetroPlayer Test Builds (updated for Leia) - zachmorris - 2018-08-21 (2018-08-17, 04:27)quig Wrote: 1. I have a RPi3 running #816 and have noticed a strange behavior with exiting games. I use a harmony one remote and lirc. If I am playing a game (NES or SNES) and I hit the exit button on my remote, I go back to the list of my ROMS (which are hosted on my NAS). I can used the arrows on the remote to move up and down to select another ROM. When I hit the OK button on my remote, the screen flashes (it looks like it is killing the old game I was playing). I then have to hit the OK button again to bring up the list of emulators. When doing these same steps for movies, I do not have to hit OK twice. This issue sounds vaguely similar to this one. I still haven't been able to figure out a rhyme or reason to the lack of control after stopping playback of a game, sometimes it happens, sometimes it doesn't. RE: RetroPlayer Test Builds (updated for Leia) - quig - 2018-08-22 (2018-08-21, 21:36)garbear Wrote:debug log for #1 and #3: debug log this failed to upload from within kodi. I had to manually get the log and upload it.(2018-08-17, 04:27)quig Wrote: 1. I have a RPi3 running #816 and have noticed a strange behavior with exiting games. I use a harmony one remote and lirc. If I am playing a game (NES or SNES) and I hit the exit button on my remote, I go back to the list of my ROMS (which are hosted on my NAS). I can used the arrows on the remote to move up and down to select another ROM. When I hit the OK button on my remote, the screen flashes (it looks like it is killing the old game I was playing). I then have to hit the OK button again to bring up the list of emulators. When doing these same steps for movies, I do not have to hit OK twice.Can you post a debug log? debug log for #2: debug log this also failed and was manually uploaded. I tested uploading a debug log after a reboot and can successfully upload, so something with games is causing uploading to fail RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-08-23 (2018-08-18, 06:25)xodi Wrote: Crashed on startup with Beta1 release, but today's nightly build works well. @xodi I think I found the problem, I'll upload some builds tonight, can you give it a try tmrw? RE: RetroPlayer Test Builds (updated for Leia) - xodi - 2018-08-23 (2018-08-23, 00:22)garbear Wrote:Definitely.(2018-08-18, 06:25)xodi Wrote: Crashed on startup with Beta1 release, but today's nightly build works well. RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-08-23 @xodi new Android build is up: https://github.com/garbear/xbmc/releases RE: RetroPlayer Test Builds (updated for Leia) - xodi - 2018-08-24 (2018-08-23, 20:43)garbear Wrote: @xodi new Android build is up: https://github.com/garbear/xbmc/releasesKodi can start now. But got error "Failed to install add-on: Shader Preset Support. An unknown error has occurred" after each time Kodi started: 19:28:00.893 T:367166597008 DEBUG: ADDON: Dll Initializing - Shader Preset Support 19:28:00.894 T:367166597008 DEBUG: SECTION:LoadDLL(/data/app/org.xbmc.kodi-1/lib/arm64/libgame.shader.presets.so) 19:28:00.894 T:367166597008 DEBUG: Loading: /data/app/org.xbmc.kodi-1/lib/arm64/libgame.shader.presets.so 19:28:00.897 T:367166597008 ERROR: Unable to load /data/app/org.xbmc.kodi-1/lib/arm64/libgame.shader.presets.so, reason: dlopen failed: cannot locate symbol "RARCH_ERR" referenced by "/data/app/org.xbmc.kodi-1/lib/arm64/libgame.shader.presets.so"... RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-08-24 (2018-08-24, 04:34)xodi Wrote:(2018-08-23, 20:43)garbear Wrote: @xodi new Android build is up: https://github.com/garbear/xbmc/releasesKodi can start now. But got error "Failed to install add-on: Shader Preset Support. An unknown error has occurred" after each time Kodi started: I can reproduce. For now, just disable it in the add-on manager. |