Win64 and Android Test Builds

General Development
#901

Has anything changed in the retroarch executable file from the last build? As with yesterdays build when i was using Advanced Launcher to load my roms when i quit a rom it would put me back to the rom select screen as it should do but with todays build when i quit a game now it kicks me back to OE main menu screen.

I think its because once RA has loaded the service is being stopped so when i quit a game it going back to OE main menu, i think the RA service needs to keep running in order for it to put me back to the rom select screen in advanced launcher???

#902

This is actually the normal behavior I get when either launching a game in RA via the commandline or when using a frontend like RCB in Kodi (esc exits out of RA not end game but got back into RA). As for changes, I had made a few in default.py & retroarch.sh but as for RA itself the code change was for the XMB fronted of RA.

#903

I changed out both retroarch files in the bin folder, I have build 26.11.14 installed and overwrite the 2 retroarch files in the bin folder with the same 2 files from build 25.11.14, I then ran advanced launcher and quit out of a game it would send me back to the rom select screen. I then overwrite the 2 retroarch files again with the 2 files from build 26.11.14 and ran advanced launcher again but this time when I quit a game it put me back to the OE main menu.

So it would appear something has defiantly changed from build 25.11.14 to 26.11.14 in either of the 2 retroarch files found in the bin folder

#904

RetroArch-2014-11-28 Android: Updated: Updated: RetroArch[07e2f24], UME[1c41ae9]

OpenElec-x86_64: Fixed: Changed -libretro.so to _libretro.so in retroarch.sh Added: CATSFC[66002fa], UAE[c25469b] Updated: RetroArch[07e2f24], Beetle PSX[7004da4], Desmume[f4ab405], Hatari[5c98270], ppsspp[37e7bcc], UME[1c41ae9]

NOTE: For best results with Android port, be sure to uninstall previous version before installing newer versions. UME 2014 based on MAME-SVN r33567 from 0.156 release.

#905

Only major change that I did was in retorarch.sh from

touch /var/lock/xbmc.disabled
killall xbmc.bin
sleep 2

$ADDON_DIR/bin/retroarch -c $ADDON_FILES/config/retroarch.cfg $EXTRAFLAG -L $ADDON_CORES/$1-libretro.so "$2" &

while [ $(pidof retroarch) ];do
    usleep 200000
done;
rm /var/lock/xbmc.disabled

to

touch /var/lock/kodi.disabled
killall kodi.bin
sleep 2

$ADDON_DIR/bin/retroarch -c $ADDON_FILES/configs/retroarch.cfg $EXTRAFLAG -L $ADDON_CORES/$1-libretro.so "$2" &

while [ $(pidof retroarch) ];do
    usleep 200000
done;
rm /var/lock/kodi.disabled

Also hopefully this new release should silence the warnings about xaudio. Let me know how it goes.

#906

Latest version for OE doesnt appear to be working get this error in terminal…

/storage/.kodi/addons/emulator.retroarch/bin/retroarch: error while loading shared libraries: libavcodec.so.54: cannot open shared object file: No such file or directory

#907

I don’t know if this is a general issue, but for some reason Netplay isn’t working for me anymore with latest builds (this includes the Nightlys and the beta as well). :confused:

#908

@BlockABoots, I am really unhappy with the way my current toolchain is working so I am in the process of completely redoing my toolchain.

@lwares87, when I get a chance I’ll try to do a netplay session on my local network and see what happens for me.

#909

That’s good to here.

Do you have the ability to add unsupported cores?, I would really like to see GroovyMAME build of Mame be included in RA. It’s probably the best version of Mame and fixes numerous historical problems that vanilla Mame has always had. For instance, screen tearing, audio stutter, smooth scrolling, correct refresh rates, reduced input lag etc.

#910

@Lordashram thx for your great work!!

Have you tested your PS3 DualShock3 on your Retroarch android build?

It seems android RA’s custom binds not working since 2014-05-15 apk build ,and the autodetection aslo borken since 2014-09-18.apk.

In lately android builds, the android frontend does deceted these keys ,and the Phoenix frontend(RGUI?) aslo read these key value,but these keys can’t work in rgui/games.

I also found some issue with the default path setting:

In build 0918,Joypad autoconfig dir point to /data/data/com.retroarch/autoconfig/;it is an empty dir.

But in builds after 0918,joypad autoconfig dir default to /data/data/com.retroarch/autoconfig/android/,and all the cfg files still be put in /data/data/com.retroarch/autoconfig/.

I try to chang the dir point to autoconfig/ instead of autoconfig/android/ in retroarch.cfg manually,but no effect.

Maybe there is some path setting missing in your lately build’s compile setting?

Many many thanks if you could fix the bug when you have some freetime!! :lol:

#911

The PS3 pad works (over blue tooth) in the last working build for OpenElec i can confirm

#912

Sorry…my bad, I means @lordashram’s android test build. :stuck_out_tongue:

#913

hi lordashram

First i want to thank you for your work i’m using your builds on an android dongle and it’s almost perfect my 360 controllers are perfectly detected and with that autoconfig i can create presets for all my controller (arcade pad ect …)

the only important issue i have is ramdom freeze ! it happens with all cores and is really frequent

also i never suceed launch mupen64 with retroarch

any solution for this freeze issue ? (i tried to take a look to logcat but i didn’t find anything that could help but my lack of knowledge may be why i didn’t find something

if you can find the solution with that issue that would be awesome ^^

anyway thanks for your work !

edit : if you need some informations please feel free to ask !

#914

@Eguibs - Try turning off threaded video driver that usually fixes random freezing problems

#915

hi foleyjo thanks for your answer

i tried your solution but it didn’t work but then i decided to test retroarch on another hardware (my phone ) and on this one absolutely no issues so i suppose my android dongle has hardware incompatibility sadly !!

#916

hi again this is what i’ve captured with logcat

there is an ANR with retroarch but i can’t say more about this waybe you can find the solution with


W/AppOps  (  447): Bad call: specified package media under uid 1000 but it is really 1013
D/StatusBar.NetworkController(  506): refreshViews connected={ wifi } level=0 combinedSignalIconId=0x7f0200aa/com.android.systemui:drawable/stat_sys_wifi_signal_4_fully mobileLabel= wifiLabel="Fwiiiiiiiiii"xxxxXXXXxxxxXXXX emergencyOnly=false combinedLabel="Fwiiiiiiiiii"xxxxXXXXxxxxXXXX mAirplaneMode=false mDataActivity=0 mPhoneSignalIconId=0x0 mQSPhoneSignalIconId=0x0 mDataDirectionIconId=0x0 mDataSignalIconId=0x0 mDataTypeIconId=0x0 mQSDataTypeIconId=0x0 mWifiIconId=0x7f0200aa mQSWifiIconId=0x7f020062 mBluetoothTetherIconId=0x10805d2
D/StatusBar.NetworkController(  506): refreshViews connected={ wifi } level=0 combinedSignalIconId=0x7f0200aa/com.android.systemui:drawable/stat_sys_wifi_signal_4_fully mobileLabel= wifiLabel="Fwiiiiiiiiii"xxxxXXXXxxxxXXXX emergencyOnly=false combinedLabel="Fwiiiiiiiiii"xxxxXXXXxxxxXXXX mAirplaneMode=false mDataActivity=0 mPhoneSignalIconId=0x0 mQSPhoneSignalIconId=0x0 mDataDirectionIconId=0x0 mDataSignalIconId=0x0 mDataTypeIconId=0x0 mQSDataTypeIconId=0x0 mWifiIconId=0x7f0200aa mQSWifiIconId=0x7f020062 mBluetoothTetherIconId=0x10805d2
D/AudioHardwareALSA(   96): AudioStreamOutALSA::standby().....
W/AppOps  (  447): Bad call: specified package media under uid 1000 but it is really 1013
D/StatusBar.NetworkController(  506): refreshViews connected={ wifi } level=0 combinedSignalIconId=0x7f0200aa/com.android.systemui:drawable/stat_sys_wifi_signal_4_fully mobileLabel= wifiLabel="Fwiiiiiiiiii"xxxxXXXXxxxxXXXX emergencyOnly=false combinedLabel="Fwiiiiiiiiii"xxxxXXXXxxxxXXXX mAirplaneMode=false mDataActivity=0 mPhoneSignalIconId=0x0 mQSPhoneSignalIconId=0x0 mDataDirectionIconId=0x0 mDataSignalIconId=0x0 mDataTypeIconId=0x0 mQSDataTypeIconId=0x0 mWifiIconId=0x7f0200aa mQSWifiIconId=0x7f020062 mBluetoothTetherIconId=0x10805d2
I/InputDispatcher(  447): Application is not responding: AppWindowToken{42481a60 token=Token{42325af8 ActivityRecord{422005f8 u0 com.retroarch/.browser.retroactivity.RetroActivityFuture t66}}} - Window{4239acb0 u0 com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture}.  It has been 5013.5ms since event, 5005.3ms since wait started.  Reason: Waiting because the focused window has not finished processing the input events that were previously delivered to it.
I/WindowManager(  447): Input event dispatching timed out sending to com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture.  Reason: Waiting because the focused window has not finished processing the input events that were previously delivered to it.
I/Process (  447): Sending signal. PID: 10949 SIG: 3
I/dalvikvm(10949): threadid=3: reacting to signal 3
I/dalvikvm(10949): Wrote stack traces to '/data/anr/traces.txt'
I/Process (  447): Sending signal. PID: 447 SIG: 3
I/dalvikvm(  447): threadid=3: reacting to signal 3
E/SensorsHal(  447): poll() failed (Interrupted system call)
I/Process (  447): Sending signal. PID: 613 SIG: 3
I/dalvikvm(  613): threadid=3: reacting to signal 3
D/StatusBar.NetworkController(  506): refreshViews connected={ wifi } level=0 combinedSignalIconId=0x7f0200aa/com.android.systemui:drawable/stat_sys_wifi_signal_4_fully mobileLabel= wifiLabel="Fwiiiiiiiiii"xxxxXXXXxxxxXXXX emergencyOnly=false combinedLabel="Fwiiiiiiiiii"xxxxXXXXxxxxXXXX mAirplaneMode=false mDataActivity=0 mPhoneSignalIconId=0x0 mQSPhoneSignalIconId=0x0 mDataDirectionIconId=0x0 mDataSignalIconId=0x0 mDataTypeIconId=0x0 mQSDataTypeIconId=0x0 mWifiIconId=0x7f0200aa mQSWifiIconId=0x7f020062 mBluetoothTetherIconId=0x10805d2
I/dalvikvm(  447): Wrote stack traces to '/data/anr/traces.txt'
I/Process (  447): Sending signal. PID: 506 SIG: 3
I/dalvikvm(  506): threadid=3: reacting to signal 3
I/dalvikvm(  506): Wrote stack traces to '/data/anr/traces.txt'
I/dalvikvm(  613): Wrote stack traces to '/data/anr/traces.txt'
D/dalvikvm(  447): GC_EXPLICIT freed 1056K, 18% free 11797K/14220K, paused 3ms+5ms, total 71ms
I/Process (  447): Sending signal. PID: 10845 SIG: 3
I/dalvikvm(10845): threadid=3: reacting to signal 3
I/dalvikvm(10845): Wrote stack traces to '/data/anr/traces.txt'
E/ActivityManager(  447): ANR in com.retroarch (com.retroarch/.browser.retroactivity.RetroActivityFuture)
E/ActivityManager(  447): PID: 10949
E/ActivityManager(  447): Reason: Input dispatching timed out (Waiting because the focused window has not finished processing the input events that were previously delivered to it.)
E/ActivityManager(  447): Load: 1.73 / 1.89 / 1.33
E/ActivityManager(  447): CPU usage from 4424ms to -2007ms ago:
E/ActivityManager(  447):   10% 447/system_server: 8.3% user + 1.8% kernel / faults: 933 minor
E/ActivityManager(  447):   3.1% 10845/org.xbmc.xbmc: 0.7% user + 2.3% kernel / faults: 110 minor 1 major
E/ActivityManager(  447):   0.1% 91/debuggerd: 0% user + 0.1% kernel / faults: 2970 minor 58 major
E/ActivityManager(  447):   2.1% 29/ksmd: 0% user + 2.1% kernel
E/ActivityManager(  447):   0.9% 506/com.android.systemui: 0.7% user + 0.1% kernel / faults: 214 minor
E/ActivityManager(  447):   0% 73/mtdblock9: 0% user + 0% kernel
E/ActivityManager(  447):   0.2% 613/com.android.phone: 0.1% user + 0.1% kernel / faults: 310 minor
E/ActivityManager(  447):   0.3% 10949/com.retroarch: 0.1% user + 0.1% kernel / faults: 126 minor 4 major
E/ActivityManager(  447):   0.1% 22/fb-vsync: 0% user + 0.1% kernel
E/ActivityManager(  447):   0% 28/kswapd0: 0% user + 0% kernel
E/ActivityManager(  447):   0.1% 93/surfaceflinger: 0% user + 0.1% kernel / faults: 1 minor
E/ActivityManager(  447):   0.1% 96/mediaserver: 0% user + 0.1% kernel / faults: 1 minor
E/ActivityManager(  447):   0.1% 116/adbd: 0% user + 0.1% kernel
E/ActivityManager(  447):   0.1% 524/tx_thread: 0% user + 0.1% kernel
E/ActivityManager(  447):   0% 1961/com.google.android.googlequicksearchbox:search: 0% user + 0% kernel
E/ActivityManager(  447): 13% TOTAL: 5.3% user + 5.3% kernel + 2.4% iowait
E/ActivityManager(  447): CPU usage from 1443ms to 1957ms later:
E/ActivityManager(  447):   1.9% 29/ksmd: 0% user + 1.9% kernel
E/ActivityManager(  447):   1.4% 116/adbd: 0% user + 1.4% kernel
E/ActivityManager(  447):   1.9% 447/system_server: 0% user + 1.9% kernel
E/ActivityManager(  447):     1.9% 461/ActivityManager: 0% user + 1.9% kernel
E/ActivityManager(  447):   1.9% 10845/org.xbmc.xbmc: 0% user + 1.9% kernel
E/ActivityManager(  447):     1.9% 10894/org.xbmc.xbmc: 0% user + 1.9% kernel
E/ActivityManager(  447): 4.9% TOTAL: 0% user + 4.9% kernel
D/dalvikvm(  447): GC_FOR_ALLOC freed 34K, 17% free 11803K/14220K, paused 52ms, total 52ms
W/ActivityManager(  447):   Force finishing activity com.retroarch/.browser.retroactivity.RetroActivityFuture
D/dalvikvm(  447): GC_FOR_ALLOC freed 353K, 20% free 11624K/14396K, paused 56ms, total 56ms
I/dalvikvm-heap(  447): Grow heap (frag case) to 12.405MB for 352944-byte allocation
D/dalvikvm(  447): GC_FOR_ALLOC freed 0K, 19% free 11968K/14744K, paused 51ms, total 51ms
I/ActivityManager(  447): Killing 10949:com.retroarch/u0a156 (adj 0): user request after error
W/InputDispatcher(  447): channel '4239acb0 com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture (server)' ~ Consumer closed input channel or an error occurred.  events=0x9
E/InputDispatcher(  447): channel '4239acb0 com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture (server)' ~ Channel is unrecoverably broken and will be disposed!
D/dalvikvm(  447): GC_FOR_ALLOC freed 243K, 20% free 11849K/14744K, paused 62ms, total 62ms
I/dalvikvm-heap(  447): Grow heap (frag case) to 12.627MB for 355706-byte allocation
D/dalvikvm(  447): GC_FOR_ALLOC freed 3K, 20% free 12193K/15092K, paused 64ms, total 64ms
D/dalvikvm(  447): GC_FOR_ALLOC freed 345K, 22% free 11848K/15092K, paused 54ms, total 54ms
W/InputDispatcher(  447): Attempted to unregister already unregistered input channel '4239acb0 com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture (server)'
I/WindowState(  447): WIN DEATH: Window{4239acb0 u0 com.retroarch/com.retroarch.browser.retroactivity.RetroActivityFuture}
#917

RetroArch-2014-12-10 OpenElec-x86_64: Added: Mednafen PSX[3803844], FFmpeg[]d00d3ff Updated: RetroArch[78850cb], common-shaders[fdf2358], 4do[46cc2a9], Beetle/Mednafen GBA[f0b518f], Beetle/Mednafen NGP[7cc7965], Beetle PSX[ff3e87f], blueMSX[d2356f1], bSNES[4a98250], bSNES-CPlusplus98[8fe0555], bSNES-Mercury[6e08947], CATSFC[26d62ef], Desmume[362fee2], FBA[aaf3e5a], FCEUmm[48b22ac], Gambatte[459c2ff], Genplus GX[8b4b807], Handy[8ac0d43], Meteor[dc1331f], Mupen64plus[c65fd9b], Nestopia[40405a5], o2em[5bb7477], PCSX_Rearmed[13bb560], PPSSPP[f69ee76], Prosystem[8220f68], QuickNES[d077028], ScummVM[30f21e7], ES9x[ac3ac4c], SNES9x-Next[fc8cf72], Stella[6c7f553], TyrQuake[502f5e0], UME[f492e0f], VBA-M[d6eea2a], VBA Next[9f3063b], Yabause[11cc55a]

NOTE: For best results with Android port, be sure to uninstall previous version before installing newer versions. UME 2014 based on MAME-SVN r33796.

#918

#BlockABoots, I will add that to my to do list but I am not getting my hopes up as RA handles a lot of that on the back end. Also let me know how this new build works as I have spent a lot of my free time these last couple of weeks working on the toolchain. Sadly I wasn’t able to achieve my primary goal of having OE be able to build a portable toolchain and the binary that this new toolchain builds seg faults when I try to run it in kUbuntu. I have some new ideas to try at a later time on trying to make a portable toolchain but for now I need to know if the current version actually produces a working binary or not.

@newisle, I’ve got to find my OTG cable to pair up the PS3 controller, then I will let you know. I’ve spent a lot of time working on trying to fix the toolchain issue for OpenElec that I have put the Android build on hold. I will start back working on updating the Android port and try to get what info I can to the devs to help with the input issues.

@eguibs, It sounds like RA is overheating your Android dongle. If you can try to underclock the CPU of your Android dongle and see what that does.

#919

I can confirm that Ps3 pads don’t work well in Android, not even using custom binds. Also, when I disable the touch overlay, it is still showing up, so it seems there is no way to disable the touch overlay, which is very annoying.

#920

Now I found the only way to use real gamepad in lordashram’s newest android testbuild!

There are two setting gui in retroarch-android:first one is android frontend ,the other is RA’s OSD GUI.You must bind your keypad in the OSD setting>input options>user xx bind all,all the cores would work with your setting until you return to the android frontend or exit retroarch.

If you exit, these key setting you made in OSD GUI will lost.And you need to binds the gamepad key everytime in this way! :rolleyes:

Hope @lordashram fix this bug soon~~~~ =D