Reicast-emulator: Reicast error on start up and inability to toggle options.
Using the latest dev on android 7 you get this error when opening the app:
Also you are unable to turn on or off some of the options in settings:
blackman91
All 21 comments
This also makes games like marvel vs capcom 2 unplayable with a controller on android 7 because of the R1 and L1 bug that needs the option compatibility mode on to make the shoulder buttons work but you can't use this option on Android 7 because of the above bug :(
blackman91
on 24 Aug 2017
This is a known issue. This is being closed as part of https://github.com/reicast/reicast-emulator/issues/1041
AbandonedCart
on 27 Aug 2017
Thanks, any news on if this will ever be fixed for Android 7?
blackman91
on 28 Aug 2017
blackman91
on 9 Sep 2017
It seems silly to have decompiled, edited, and recompiled a single version so you could come to the open source project and post a link to it on reddit.
Hopefully this is not going to break the emulator for others, but I can have compat enabled by default for Android 7+. If it causes issues, it may have to be placed behind a prompt.
AbandonedCart
on 30 Sep 2017
I am not a dev, I did it using an app called save to game, what you said it's what the app does. But yeah having those options enabled by default for Android 7 would be great (fps counter, compat), in older Android versions you can disable those option easily.
blackman91
on 2 Oct 2017
The problem with enabling optional settings by default is that you cause the inverse problem. What about everyone else that doesn't want the FPS counter? What about all of the controllers that get invalid mappings with compatibility mode?
The real issue is getting access to settings. That is what needs to get solved, preferably with as little overhead that will need to be removed as possible. Compatibility mode has been submitted as a temporary workaround, but there is no real need to enable "dev mode" features while the core is fixed. I am sure seeing the FPS counter can wait until after settings are accessible.
AbandonedCart
on 9 Oct 2017
Also enabling compatibility mode makes the shoulder buttons work but it makes reicast unable to differentiate between dpad and the left analog, with compat mode disabled the analog and dpad input is correct but the shoulder buttons do not work, any fix for this?
blackman91
on 14 May 2018
Currently, no. It has only been reported using an OUYA controller. Is the issue with an OUYA controller?
AbandonedCart
on 14 May 2018
Nope, it is a saitake I use on Android 7, I am on latest dev build, happens with the 8bitdo SF30 pro controller too. Also what does the native gamepad mode option does? It seems it makes reicast crash on Android 7.
blackman91
on 15 May 2018
It's for the Xperia Play, which would only allow using the touchpads with specialized native code. It is not intended for Android 7, since the Xperia Play stopped at an ICS beta.
Latest dev build? Which branch?
AbandonedCart
on 15 May 2018
The latest apk from here:
http://builds.reicast.com/
I have tested several gamepads and it appear the R1 and L1 won't work if I don't enable compat mode, even remapping the reicast lt and rt to face buttons doesn't work. Also it seems that in the reicast root folder inside the shared_prefs folder you can change the options that are not togglable on Android 7 by editing a xml file, any way you could make that file save to somewhere writable?
blackman91
on 15 May 2018
Sounds like the master branch. You want builds from the lk/android-studio branch to fix not being able to toggle the options. It won't fix the triggers, but includes all of the other Android fixes since last year.
AbandonedCart
on 15 May 2018
Speaking of the android studio branch, can you re-open the MR for it?
On Tue, 15 May 2018 at 11:02, TwistedUmbrella notifications@github.com
wrote:
Sounds like the master branch. You want builds from the lk/android-studio
branch to fix not being able to toggle the options. It won't fix the
triggers, but includes all of the other Android fixes since last year.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/reicast/reicast-emulator/issues/1046#issuecomment-389079456,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYAMisNIz3smKf8xTHIHZTtXjmWsCQGks5tyot8gaJpZM4PAvXO
.>
~skmp
skmp
on 15 May 2018
Still fails for posix_memalign
/home/travis/build/reicast/reicast-emulator/shell/android-studio/app/src/main/jni/../../../../../../core/hw/pvr/ta_ctx.cpp:27:20: error: use of undeclared identifier 'posix_memalign'
if(posix_memalign(&result, align, size)) result = 0;
^
1 error generated.
make: *** [/home/travis/build/reicast/reicast-emulator/shell/android-studio/app/build/intermediates/ndkBuild/debug/obj/local/x86/objs-debug/dc//home/travis/build/reicast/reicast-emulator/shell/android-studio/app/src/main/jni/__/__/__/__/__/__/core/hw/pvr/ta_ctx.o] Error 1
After the fix (https://github.com/reicast/reicast-emulator/commit/50a96cd9b9ca577ae84afed408cd34d9dbdc890c) according to https://stackoverflow.com/questions/44852378/android-ndk-r15b-posix-memalign-undeclared-identifier
AbandonedCart
on 15 May 2018
Nice, where can I download these lk/android-studio branch reicast builds?
blackman91
on 15 May 2018
http://builds.reicast.com/
All the other headings except master are alphabetical.
AbandonedCart
on 15 May 2018
Thanks a bunch, the options work now! also enabling the option enable custom key layout in input settings fixed my issue of the shoulder buttons and the analog not working, really nice job devs.
blackman91
on 15 May 2018
Just curious what are the differences between all those lk Android studio branches? These guys seem to want to know too:
https://www.reddit.com/r/EmulationOnAndroid/comments/8jod8t/psa_reicast_settings_bug_on_android_7_and_up_has/
blackman91
on 16 May 2018
The builds page corresponds to the actual branches in the source, but deleted branches may not always be deleted from the builds page (since it needs to be done manually).
I left a link to this issue "forum" in the thread and explained that it would help us help them to post issues here, since it can get a bit crazy trying to stay on top of everything across sites. I also noticed you were trying to support people reporting issues there, so thanks for that.
AbandonedCart
on 16 May 2018
@skmp Not sure what needs to be done to remove branches from the build page, but here are all the ones that reference deleted branches that are either merged or failed tests:
lk/a-s-w
lk/a-w-s-2
lk/android-studio-compat
lk/android-studio-core
lk/android-studio-update
lk/cleanup
lk/windows
lk/xcode
AbandonedCart
on 16 May 2018
Related issues
skmp
·
20Comments
skmp
·
49Comments
skmp
·
29Comments
blackman91
·
31Comments
AbandonedCart
·
55Comments
Most helpful comment
The builds page corresponds to the actual branches in the source, but deleted branches may not always be deleted from the builds page (since it needs to be done manually).
I left a link to this issue "forum" in the thread and explained that it would help us help them to post issues here, since it can get a bit crazy trying to stay on top of everything across sites. I also noticed you were trying to support people reporting issues there, so thanks for that.