Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Making an Android Frontend (Android 2600:Part 1)  (Read 58101 times)

0 Members and 1 Guest are viewing this topic.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Making an Android Frontend (Android 2600:Part 1)
« on: June 19, 2013, 03:40:36 pm »
Part 1 of the Android 2600 project

I set out to make a simple frontend for Android by customising an existing launcher (Nova Launcher) in combination with other utilities.  Aim was to completely strip away all of the Android components (Dock, Status Bar, Navigation Bar, Search Bar, Home Screen, Lock screen, icons,  widgets etc) and simply have one page per system with a themed background.  Games for each systems will be run via shortcuts which are given images (screenshots or boxarts). Rather than litter the screens with game shortcuts I opted to use a hidden folder on each page.  Having only this one item on each page allows the user to cycle through systems with one press of the controller (left or right).

It was possible to strip down most of the Android screen elements by configuring Nova Launcher.  Config details are posted below.
I used the full!screen app to hide the status bar and the icons that appear in the touch areas.

The OS I am using is Android v4.1 (Jelly Bean) on a rooted device.  Refer to part 2 for the hardware and firmwire I'm using.
Screen is set at 1980x1080 at 60hz with HDMI output.  The device supports other screen resolutions.

I made a custom boot animation and applied it using the Boot Animations app.  For now,  I simply use a static gif image but it is also possible to generate an intro from an animated gif.  There are some examples of ready made intros at http://androidbootanimation.com/
It is also possible to change the boot logo which appears briefly before the boot animation.  For this I will need to modify the boot image (firmware) and reflash the hardware.  I'll take a look at that later.

To allow multiple wallpaper backgrounds (one per system) I installed Multipicture Live Wallpaper and made some of my own HD backgrounds.
I've attached my Photoshop template (EDIT: oh no i haven't - it's too big) and the JPEG backgrounds can be viewed at http://imgur.com/a/hmxbz#0



I include the system name as part of the background image in bottom-right corner.  Originally I had used the system name artwork on the games folder but it wasn't quite big enough.  The hidden games folder is in the same location, bottom-right.
The games folder is hidden by simply setting its image to be a 1x1 pixel transparent gif.

Nova Launcher allows shortcut creation for some applications including most of the console emulators that I have installed.  After creating a shortcut,  I apply artwork and move the shortcut to the hidden games folder.

I used Font Installer to change the default Android font - which is used for the game names.

I've installed these emulators so-far.
 * ATARoid
 * NESoid
 * SNESoid
 * GENSoid
 * N64oid / Mupen64
 * PCE (PC Engine/Turbografx)
 * GAMEBoid
 * GEARoid (Gamegear and MasterSystem)
 * FPse (PS1)

I'm mainly focussed on consoles for this project.  There are many other emulators on Android for me to test including MAME, NEOGEO, CPS, NDS, Saturn, Amiga, C64, GBC, PSP, Scumm

I made some notes on setting up:

<SETTING UP>

Install these apps:
 * Nova Launcher
 * Nova Launcher Prime - optional
 * full!screen
 * Multipicture Live Wallpaper
 * Font Installer Root
 * Boot Animations Root

Run full!screen app and apply these settings:
 * full!screen mode > On
 * Autostart > On
 * Show notification > Off
 * Set opacity (of touch areas) > 0% (to hide the home button/corner buttons)

Run Font Installer app:
 * Install Dekar font (or the Droid font maybe to match the android|2600 logo)

In Android Settings:
 * Display > Auto hide systembar
 * Display > Font Size > Large (or Huge)
 * Screen > Screen Scale > Extend to Max (if you have a black border to remove)
 * Screen > Output Interface > HDMI (it was the only option)
 * Screen > Display Mode > 1920x1080p-60

In Nova settings:
 * Nova > Select Default Home as Nova Launcher (if not set already)
 * Desktop > Desktop Grid > 5x5
 * Desktop > Width Margin > None
 * Desktop > Height Margin > None
 * Desktop > Persistent Search Bar > Never
 * Desktop > Home Screens - Create a screen for each system
 * Desktop > Lock Desktop > On
 * Drawer > Inifinite Scroll > Off
 * Drawer > Advanced > Remember Position > On
 * Dock > Enable Dock > Off
 * Dock > Show Divider > Off
 * Dock > Show Scroll Indicator > Off
 * Folders > Label Icons > On
 * Look and feel > Show notification bar > Off
 * Look and feel > Scroll Speed > Relaxed
 * New Apps > Auto Add Shortcuts > Off

On Desktop:
 * Remove all widgets
 * Remove all app icons (can still access all apps with long left click on desktop)
 * Set the active wallpaper as "Multipicture Live Wallpaper"

Change settings of the live wallpaper,  we want to have individual settings for each screen.
 * In screen settings > Add inidividual settings (this creates screen 1 settings)
 * In the screen 1 settings,  set picture source to JPEG image of first system e.g. NES
 * Set crop/resize ratio > show entire picture
 * In Drawing Settings > Transition Type > None (Fade and outside-cube work well too)
 * Repeat these steps for all other system screens

</SETTING UP>

Would be cool for others to replicate this setup and suggest ways that it can be improved.

One thing I'd like to improve is to have bigger boxarts/screenshots for the game images.  AFAIK it is not possible to increase size more than 130% unless I start hacking at the launcher .APK file and force some changes that way.

Can anybody help me to create an intro animation using the Android 2600 logo?

I made a short video of the frontend on my main project thread.  I'll try to post some pics of this running on my TV soon.

« Last Edit: June 19, 2013, 04:12:41 pm by degenatrons »

chopperthedog

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1049
  • Last login:Yesterday at 09:27:26 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #1 on: June 19, 2013, 05:10:30 pm »
Increasing the icon size within a folder from source shouldn't be too hard if you have a build box set up. Never dealt with building from source myself only madhacking of apk's with apktool and some java sdk tools. But from a decompiled apk would prove to be a greater challenge. For an edit like that since it has a variable (e.g. being able to edit size from settings) it ends up in java and is no longer just an xml line that would be part of dimens.xml. I've done some smali edits in the past, it just really helps to be able to find the line of source code you want to edit and and convert the entry to hex and then you hope to find that line within the smali mess. The bookmark widget from the browser would be something interesting to use as a scrollable layout for game titles.


good day. 

Mungo9000

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 82
  • Last login:August 25, 2016, 09:18:21 am
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #2 on: June 20, 2013, 02:00:02 pm »
Amazing work.
I've just built a couple of machines out of Android tablets (using your hexload minimus) and I realised that MAME systems no longer needed to use bulky Windows PC's; cheap Android can do it all now that the software is coming together. (Plus a way to make sensational mini machines)
This is going offer huge cost savings as a TV stick and minimus gives all of the guts for around £50.
Excellent work again Degenatrons.  :applaud: Amazeballs!

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #3 on: June 20, 2013, 02:50:22 pm »
Thanks for the info chopperthedog. 
I decompiled the .apk using APK tool and had a look around.  There are some preference files but the contents are pretty much meaningless so I am in the dark as to what I should change.  Anyway,  I managed to make some dummy changes and recompile the .apk file.  That didn't help with my issue but it's good to know I can do this for future stuff.

So I had a look around the system folders on the android device and found an interesting file: build.prop .  I've seen this file discussed on various forums for managing system settings.
It's a read only file so I had to set write permissions before I could change the values.

Here's the file:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRO03H
ro.build.display.id=rk30sdk-eng 4.1.1 JRO03H lewy20041@ eng.root.20130116.110927 test-keys
ro.build.version.incremental=eng.root.20130116.110927
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=2012 08 30 09:29:35 EST
ro.build.date.utc=1346030975
ro.build.type=eng
ro.build.user=root
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=MinixHFW 2.2.4
ro.product.brand=asus
ro.product.name=EeePad
ro.product.device=tf700t
ro.product.board=rk30sdk
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=rk30xx
# ro.build.product is obsolete; use ro.product.device
ro.build.product=rk30sdk
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=rk30sdk-eng 4.1.1 JRO03H eng.root.20130125.165203 test-keys
ro.build.fingerprint=rk30sdk/rk30sdk/rk30sdk:4.1.1/JRO03H/eng.root.20130125.165203:eng/test-keys
ro.build.characteristics=tablet
# end build properties
#
# system.prop
#

#rild.libpath=/system/lib/libreference-ril.so
#rild.libargs=-d /dev/ttyUSB2

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Default.ogg
ro.config.notification_sound=Default.ogg
ro.carrier=unknown
ro.config.alarm_alert=Default.ogg
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=80m
dalvik.vm.heapsize=256m
ro.config.facelock=enable_facelock
persist.facelock.detect_cutoff=5000
persist.facelock.recog_cutoff=5000
persist.sys.usb.config=adb,mass_storage
persist.sys.strictmode.visual=false
dalvik.vm.jniopts=warnonly
ro.rksdk.version=RK30_ANDROID4.1.1-SDK-v1.00.00
sys.hwc.compose_policy=6
ro.sf.fakerotation=true
ro.sf.hwrotation=270
ro.rk.MassStorage=true
wifi.interface=wlan0
ro.rk.screenoff_time=-1
ro.rk.def_brightness=200
ro.rk.homepage_base=http://www.google.com/webhp?client={CID}&amp;source=android-home
ro.rk.install_non_market_apps=true
wifi.supplicant_scan_interval=15
ro.default.size=100
persist.sys.timezone=Asia/Shanghai
ro.product.usbfactory=MHFW USB
ro.opengles.version=131072
testing.mediascanner.skiplist=/mnt/sdcard/Android/
ro.factory.tool=0
rild.libargs=-d_/dev/ttyUSB1
ril.pppchannel=/dev/ttyUSB2
rild.libpath=/system/lib/libril-rk29-dataonly.so
ril.function.dataonly=1
ro.com.google.apphider=on
ro.com.google.gmsversion=4.1_r2
ro.com.archos.appsversion=1.16
ro.product.version=1.0.0
ro.product.ota.host=www.rockchip.com:2300
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.hardware.version=1.0.0.0

#
#lewy20041
#

# Helps Scrolling Response
windowsmgr.max_events_per_sec=300

# Increases overall touch response
Debug.performance.tuning=1
video.accelerate.hw=1

# Forces your home screen launcher to remain in memory
ro.HOME_APP_ADJ=1

# Disable error checking, fix some application issues
ro.kernel.android.checkjni=0

# Google has something called a "checkin" service that sends them anonymous
# usage data, bug reports, crash logs, etc, but it fails a lot. When you download
# something from the Market, it sends a message to Google about it, and if it fails
# it just freezes.
ro.config.nocheckin=true
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1

#Improve 3g data speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5

#Increased Media & Streaming Performance
ro.platform.has.sleeppolicy=false
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-scan=true
media.stagefright.enable-meta=true
media.stagefright.enable-fma2dp=true
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.evdo_b=4096,87380,256960,4096,1 6384,256960

#General Performance
debug.sf.hw=1
persist.sys.ui.hw=1
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
ro.media.enc.jpeg.quality=100
persist.service.adb.enable=1
persist.sys.screen.state=on
ro.sf.lcd_density=160



That last entry: ro.sf.lcd_density is the holy grail.  I found that the value relates directly to the icon and text size :D
I tested with various values and finally set at 270.

I made a couple of other tweaks
I reset the icon scale in Nova to 100% - so that we are not losing any image quality.
I installed a smaller font (FaunScript) and reduced font size to: Small because it had greatly increased with the density change.

I'm super happy with the way I have the box arts now.



« Last Edit: June 20, 2013, 02:55:40 pm by degenatrons »

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #4 on: June 20, 2013, 03:07:18 pm »
Looking good, is this something that you are thinking about doing for Mame? Some of us are experimenting with Android based PC's for potential small form-factor Mame solutions but of course Mame front ends on Android are pretty awful

bsellers100

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 53
  • Last login:June 19, 2018, 05:46:46 pm
  • I want my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #5 on: June 20, 2013, 05:36:02 pm »
That looks really cool.  I would love to see something like this as a seperate .apk that you could set up with gameplay images so that my kids could easily start emulator games on their tablets.  As it is now the youngest can't read all that well yet and game pics would make it easy for him to play the game he wants without always coming to me to start the emulator and game for him.  Keep up the good work, I can't wait to see how far you get with this.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #6 on: June 21, 2013, 04:57:14 am »
Amazing work.
I've just built a couple of machines out of Android tablets (using your hexload minimus) and I realised that MAME systems no longer needed to use bulky Windows PC's; cheap Android can do it all now that the software is coming together. (Plus a way to make sensational mini machines)
This is going offer huge cost savings as a TV stick and minimus gives all of the guts for around £50.
Excellent work again Degenatrons.  :applaud: Amazeballs!
Cheers Mungo.  Loving your tiny arcade builds,  I'm keen to make one of them myself one day.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #7 on: June 21, 2013, 07:46:44 am »
Looking good, is this something that you are thinking about doing for Mame? Some of us are experimenting with Android based PC's for potential small form-factor Mame solutions but of course Mame front ends on Android are pretty awful

There's a new Retroarch release (17th June) for Android including MAME build 2003 (0.78).  I'll try it out.  Seems like there are significant improvements.
http://forum.xda-developers.com/showthread.php?t=2116468&page=37

To use it I need to figure out how to launch into MAME game directly from my FE , bypassing Retroarch's game launcher - i'm only interested in its MAME core.

sharpfork

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 618
  • Last login:April 07, 2023, 12:43:42 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #8 on: June 21, 2013, 11:13:26 pm »
Does retroarch have an API for game launch?  It seems like it should...

mike boss

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2645
  • Last login:October 22, 2021, 01:19:45 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #9 on: June 21, 2013, 11:42:13 pm »
This is really cool and I'll be keeping an eye on this thread for sure.
I have a very simply Android tablet, picked up a KADE, and was inspired by the Android tablet mini arcade units.
This is really awesome stuff.

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #10 on: June 26, 2013, 02:24:01 pm »
Hiya Fellas.

OK my Kade is in the mail (Thanks Kevin) and I've been testing RetroArch which is giving much better performance in the emulation arena so things are looking promising enough for me to continue pursuing the Android approach.

Degenatrons - did you ever work out if you could launch ROMs through RetroArch via scripts? I'd like to try that approach simulating what you have done here by giving each script a custom Icon and using a customized version of NOVA Launcher as my front end.

chopperthedog

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1049
  • Last login:Yesterday at 09:27:26 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #11 on: June 26, 2013, 04:53:39 pm »
This might help in the quest to launch game from shortcut. https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm&hl=en


good day.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #12 on: June 26, 2013, 06:27:32 pm »
This might help in the quest to launch game from shortcut. https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm&hl=en

Thanks,  will take a look at that app you posted chopperthedog.

Degenatrons - did you ever work out if you could launch ROMs through RetroArch via scripts? I'd like to try that approach simulating what you have done here by giving each script a custom Icon and using a customized version of NOVA Launcher as my front end.

The wrapper for Retroarch looks interesting at: https://github.com/Themaister/RetroArch/blob/master/android/phoenix/src/org/retroarch/browser/RetroArch.java#L403
The methods onItemClick starts an activity and loads the roms,  also onActivityResult gives useful informtiion and references the config files.  Maybe we can adapt this to launch specific rom direct from the Android frontend. 
There's not much documentation out there so will have to play around and see what happens.  Aim would be to build an .APK that runs a single MAME rom and then we can look at automating the .APK creation for a bunch of other roms.
I won't have much time this week to look at it but will let you know if i make progress. 

Cheers

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #13 on: June 26, 2013, 06:58:17 pm »
Aim would be to build an .APK that runs a single MAME rom and then we can look at automating the .APK creation for a bunch of other roms.

Sounds interesting. Depending on your android programming skills the ideal approach would be to scan the roms folders, and maybe a graphics folder for png/jpg of the same name and show them in a list you could scroll through as buttons, clicking the image launches the rom.

Sp3c7r3

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 43
  • Last login:March 09, 2016, 02:09:52 am
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #14 on: June 27, 2013, 05:24:49 am »
Very interesting!! I have a Android MK809 lying around and if I could make that into a dedicated console emulator that would be pretty sweet. I know nothing about flashing/modding these things, so I'm following this project to hopefully pick something up  ;)

The ideal thing, for me, would be for the thing to boot directly to a front-end on power-on and everything being controllable with a generic usb joypad.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #15 on: June 28, 2013, 06:21:11 pm »
I decided to take the bull by the horns and get my head into RetroArch to figure out how we can launch MAME games directly from the frontend.  Seems like there would be other uses for this outside of my project and potentially would be provide a viable alternative to a 60-in-1 board.  It's kind of a detour of the main goals of my console project but I admit it would be a pretty cool add.

My initial efforts have been successful :D  I've modified RetroArch code to launch Donkey Kong directly from my Android FrontEnd.  There is still some work to do to make this configurable so we can launch into any rom but the hard part is done.

I'll try to post a video soon to show it working.  In the meantime,  here's some pics to explain what was done.

I downloaded RetroArch source from https://github.com/Themaister/RetroArch/ and copied to the SD card on my Android stick.
For Java development,  I found a really neat IDE on Android called AIDE.  This App will allow be to modify and compile code directly on the Android stick and required no setup whatsoever :D  I highly recommend it.

I located the code which handles the game launching and moved it to the RetroArch start up routine,  so the first thing RetroArch does is launch a game.  This bypasses the UI selection by the user.  The user would normally have to pick an emulator core (from a long list) and then a rom (by browsing folders).  For now,  I have the rom hard-coded as dkong.zip but I can make this variable later. 
I added some text to appear as the game launches.



I compile the code and installed the modded RetroArch .APK.  I didn't build all of the emulator cores (no reason) so I copied these over to the RetroArch library manually.  You need root access for this and recommend the Root Browser App for the copying.  The 2 files pictures were copied from a default installation of RetroArch which I have since uninstalled from the device.



A Donkey Kong shortcut was added to the frontend.  I'm thinking that I could use the label name of the shortcut to identify the rom which should be launched.  Then would simply need to create other shortcuts for other games.  I'll take a look at this later.



I added a MAME screen to the Android 2600 launcher.



and made some more shortcuts for other classic games.



That's all for MAME.

In other news,  I made some tweaks to the icon size and resolution. and dropped the Android|2600 logo from the top-right which was a little distracting.  I also added some nice transitions when switching between the systems.
Here's some updated console pics.










Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #16 on: June 28, 2013, 06:30:53 pm »
WELL DANG!!!!!!!!!!!!!!!!!!!!!!!!!

Nice, this is looking very promising indeed. My goal it to find an Android replacement for the 60 boards and this is certainly getting very very close to that, especially with the inclusion of the KADE too it is looking like a potentially very simple, powerful and reasonably economical way forward.

I'll have to take some time to wrap my head around what you have done here as I'm really not very good with code, but I love the look of what's happening.

Are you using Nova Launcher as your front end? What is the maximum Icon size that you can use, they look nice n big!!

Great work.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #17 on: June 28, 2013, 06:53:04 pm »
Yup,  this is built on Nova Launcher with various tweaks.  When done,  I'll try to package everything up so it is easy to install/distribute and I can include the modded RetroArch .APK.  Kudos to themaister for making RetroArch source available and having a completetly open license  :cheers:

I manipulate the icon size using a combination of the lcd_density (parameter in the build.prop file) and the Nova icon size (max 130%).  Icons can be as big or small as you like using this combination.  My size gives we 2 rows within a folder window.  Bigger icons can be cropped when displayed in the folder so some trial and error is necessary.  I went for a clean screen for each of the systems and a button press opens up the rom selection.  Roms could be on the main screen too and then icons can be any size.


degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #18 on: June 28, 2013, 06:53:59 pm »
(accidental empty post)
« Last Edit: June 28, 2013, 06:56:20 pm by degenatrons »

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #19 on: June 28, 2013, 06:56:09 pm »
Cool. Nice, I'm familiar with build.prop tweaks and LCD density so I can work that out, I use Nova on my phone too so this is all good.

Can't wait to play with it, I'll be out for a few weeks on vacation but when I get back I'll dive head on into this.

Bender

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1919
  • Last login:November 28, 2016, 08:12:21 pm
    • Happ to Tron Conversion tutorial
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #20 on: June 30, 2013, 06:42:44 am »
Degrentrons,

This is great work!
Haven't looked into android before but I got a ouya and its been fun playing with that
Have you looked into MAME4droid reloaded which runs .139 a pretty recent version
I was just mentioning in another thread that a emu front end for the ouya would be killer
Think yours would work on it?

Plus aside from the technical challenges your overcoming I love the art and design of the Frontend too! :cheers:
« Last Edit: June 30, 2013, 06:45:43 am by Bender »

404

  • Trade Count: (+3)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1019
  • Last login:August 04, 2015, 10:19:10 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #21 on: June 30, 2013, 11:47:21 am »
I'm really quite fed up with the fragmentation in the android ecosystem as of late. I haven't tinkered with android stuff in over a year because of that.

This project however, makes me want to go buy one of these android tv sticks and start tinkering myself.

great job!  ;D

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #22 on: June 30, 2013, 03:33:24 pm »
Degrentrons,

This is great work!
Haven't looked into android before but I got a ouya and its been fun playing with that
Have you looked into MAME4droid reloaded which runs .139 a pretty recent version
I was just mentioning in another thread that a emu front end for the ouya would be killer
Think yours would work on it?

Plus aside from the technical challenges your overcoming I love the art and design of the Frontend too! :cheers:

I've tried MAME4droid.  It works but doesnt' perform as well (at least not on my device) as the latest RetroArch MAME build of 17th June.
This setup should work on OUYA too.  I just ordered one and will check it out.

Thanks for your comments about the art and design.  I tried to keep it all basic and functional for now.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #23 on: June 30, 2013, 03:48:45 pm »
I'm really quite fed up with the fragmentation in the android ecosystem as of late. I haven't tinkered with android stuff in over a year because of that.

This project however, makes me want to go buy one of these android tv sticks and start tinkering myself.

great job!  ;D
I'm sure you'll love tinkering with your stick  :P
It took me a while to get used to Android but I'm really starting to warm to it and can see potential for projects big and small.

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #24 on: June 30, 2013, 09:45:26 pm »
Jellybean turned the corner its an extremely good OS just stick with vanilla builds

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #25 on: July 02, 2013, 08:08:27 pm »
The frontend now launches directly into MAME games using custom shortcuts  ;D.  These shortcuts need data to identify the rom and this data is passed to my modified build of RetroArch.

Custom shortcuts are easily created with the Tasker App



I created a bunch of shortcuts for classic roms and gave them each an image.



All tested and working.



The vertical games can be stretched to fit full screen but that looks pants on my TV!  I took another look at the Tasker App and found that is also has some UI capabilities.  It was possible for me to create a basic bezel using artwork for the left and right sides of the screen.  The images are displayed as a scene that is defined in Tasker to appear as an overlay.

I defined a scene in Tasker.



and updated the task of my custom shortcut. 



I did some other neat stuff in this task too.
i) There is speech to announce the name of the rom that is being launched. 
ii) After the rom loads I send left/right key input so the start screen in MAME is skipped.





I'm really loving the combination of Nova and Tasker.  Thanks to chopperthedog for suggesting the Tasker app :cheers:

That's all for now.  I haven't had time to make an updated video :(

kayser2008

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15
  • Last login:December 07, 2014, 09:50:09 am
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #26 on: July 03, 2013, 05:22:06 am »
 :o  really
 great job Degenatrons will you realease that frontend ?
keep  up the AMAZING job.

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #27 on: July 03, 2013, 06:19:16 am »
Oh yes this is really coming together, I love where this is going

404

  • Trade Count: (+3)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1019
  • Last login:August 04, 2015, 10:19:10 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #28 on: July 03, 2013, 08:11:20 am »
I'm sure you'll love tinkering with your stick  :P
It took me a while to get used to Android but I'm really starting to warm to it and can see potential for projects big and small.

Jellybean turned the corner its an extremely good OS just stick with vanilla builds

I'm quite used to android as it stands. I've published 2 or 4 simple apps on the market. my gripe is the complete fragmentation of the android environment.


kahlid74

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1366
  • Last login:January 01, 2021, 12:42:56 pm
  • Gaming for a better future!
    • GamersAnon
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #29 on: July 03, 2013, 09:22:26 am »
Degrentrons,

This is great work!
Haven't looked into android before but I got a ouya and its been fun playing with that
Have you looked into MAME4droid reloaded which runs .139 a pretty recent version
I was just mentioning in another thread that a emu front end for the ouya would be killer
Think yours would work on it?

Plus aside from the technical challenges your overcoming I love the art and design of the Frontend too! :cheers:

I've tried MAME4droid.  It works but doesnt' perform as well (at least not on my device) as the latest RetroArch MAME build of 17th June.
This setup should work on OUYA too.  I just ordered one and will check it out.

Thanks for your comments about the art and design.  I tried to keep it all basic and functional for now.

Reading this thread I was just thinking the Ouya too!  I've got mine ready to roll so if you want to shoot me some directions to try I'd love to give it a whirl.

Great job btw!

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #30 on: July 03, 2013, 10:23:09 am »
Reading this thread I was just thinking the Ouya too!  I've got mine ready to roll so if you want to shoot me some directions to try I'd love to give it a whirl.
Great job btw!

My OUYA should be with me in a few days so I will try to replicate the setup on that and make some notes.
Cheers.

Bender

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1919
  • Last login:November 28, 2016, 08:12:21 pm
    • Happ to Tron Conversion tutorial
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #31 on: July 03, 2013, 07:39:35 pm »
Reading this thread I was just thinking the Ouya too!  I've got mine ready to roll so if you want to shoot me some directions to try I'd love to give it a whirl.
Great job btw!

My OUYA should be with me in a few days so I will try to replicate the setup on that and make some notes.
Cheers.

Hells Yeah! :applaud: :applaud:

emphatic

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2008
  • Last login:Yesterday at 05:08:23 pm
  • -"Suck it, Donny!" -"No, YOU suck it.... more".
    • Emphatic's Video Game Collection
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #32 on: July 05, 2013, 05:46:53 am »
Nice work!  :cheers: What's up with those "X" icons on the bottom right of the "bezel" pictures?

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #33 on: July 05, 2013, 06:20:56 am »
Nice work!  :cheers: What's up with those "X" icons on the bottom right of the "bezel" pictures?
Thanks.  I got rid of the "X" (close icon) by changing the overlay settings.  The bezel appears automatically on game start and disappears on exit so no reason to have those icons appear.
 
« Last Edit: July 05, 2013, 06:22:57 am by degenatrons »

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #34 on: July 05, 2013, 11:10:12 am »
I made a short video to show progress with the frontend.  Quality is not great - there's lots of flickering because i'm recording the TV.  Anyway,  it shows what I have created so-far.



I have ideas to change the layout of the popup folder containing the roms.  Options are to use a web view which can display animated content (animated gif and flash) and be populated dynamically based on a scan of a roms or replace the app drawer with a custom version which will display specified items in a grid.

I am able to package my game customisations into .apk files.  The .apk can then be installed onto another machine.  This seems like a neat way of managing/distributing the game specific content I am adding to each of the roms (bezels, sounds, startup instructions, exit instructions). 

In other news,  my OUYA arrived today  ;D

   

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #35 on: July 05, 2013, 11:28:46 am »
Looks fantastic. I can't wait to play around with these pieces. I assume with your apk you could easily build complete game packs that are a simple install.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #36 on: July 05, 2013, 03:21:47 pm »
Looks fantastic. I can't wait to play around with these pieces. I assume with your apk you could easily build complete game packs that are a simple install.
Interesting idea  :cheers:.  I should be able to bundle all the pieces into a project and generate a single .apk from that, excluding roms of course - roms would have to be placed in a given folder.

kayser2008

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15
  • Last login:December 07, 2014, 09:50:09 am
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #37 on: July 06, 2013, 06:45:13 am »
degenatrons

I saw this app, i know already very advanced in your project, but decided to post it might help.
 good work. :applaud:

https://play.google.com/store/apps/details?id=com.ccpcreations.android.VLW&hl=en

http://www.youtube.com/watch?feature=player_embedded&v=oBpqZH8NEBI#at=76



degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #38 on: July 09, 2013, 08:16:43 am »
degenatrons

I saw this app, i know already very advanced in your project, but decided to post it might help.
 good work. :applaud:

https://play.google.com/store/apps/details?id=com.ccpcreations.android.VLW&hl=en

Thanks for the suggestion.

I've actually been working on my own video overlay for display of the game previews as a videowall, so when clicking on the MAME option,  the videowall is presented for you to select a game from.  I now have it working on Android and will be doing some testing later with the frontend.
The production of the video wall is automated using a routine I wrote a while ago and is documented at:

https://sites.google.com/site/degenatrons/other-stuff/video-wall-generator

I had originally used this to generate a custom intro but found that it was easily adapted to work as a video menu.

Each video in the wall is an animated gif and these are bundled into a local webview on Android.  I added a JavaScript "onClick" event to each image and that is used to launch a task on Android which starts the game.  It is also possible for me to overlay transparent gif and flash animation over the webview by creating a Scene with Tasker.  I can set depth for each of the components that I use to make up the screen.  This provides a very powerful way to make themes.

I hope to post pics and more information later.

Here's that custom intro I made a while ago which shows how the videos appear together in a wall.  All the video was converted from AVI and merged together using my routine described in the above link.



Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #39 on: July 09, 2013, 11:26:30 am »
A BILLION INTERNETZ POINTS!!!! for using Megablast by Bomb the Bass!!!

GIZMOGAMES

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 103
  • Last login:February 28, 2019, 10:33:46 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #40 on: July 17, 2013, 05:24:17 am »
hee hee if i remember right it was the theme music from was it Xenon on the amiga :D great little shootemup :) loving the way this is going :D

Drnick

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1641
  • Last login:May 06, 2023, 01:19:48 pm
  • Plodding Through Life
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #41 on: July 17, 2013, 12:31:45 pm »
Nah it was xenon2 -  Megablast,   Its going back a while and your memory is starting to fail you.   :laugh2:

Mind you this app may actually mean that I find something to do with my Nexus 7  :cheers:

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #42 on: July 17, 2013, 02:11:26 pm »
Biotches please.....



 :afro: :afro: :afro: :afro: :afro: :afro:

emphatic

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2008
  • Last login:Yesterday at 05:08:23 pm
  • -"Suck it, Donny!" -"No, YOU suck it.... more".
    • Emphatic's Video Game Collection
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #43 on: July 17, 2013, 05:18:21 pm »
^^This. It's actually John Carpenter's Escape From New York from the beginning though before Bomb The Bass sampled it.  :cheers:

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #44 on: July 17, 2013, 05:43:27 pm »
^^This. It's actually John Carpenter's Escape From New York from the beginning though before Bomb The Bass sampled it.  :cheers:

Cool, thanks I was trying to find that

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #45 on: July 18, 2013, 12:49:23 pm »
^^This. It's actually John Carpenter's Escape From New York from the beginning though before Bomb The Bass sampled it.  :cheers:

Awesome!  Played through that soundtrack today, hearing parts that could've been sampled/sped up by BTB.  Wasn't obvious though.  Loved that film, was oft-played on Betamax.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #46 on: July 18, 2013, 02:04:43 pm »
So I got sidetracked on MAME and have been building a frontend specifically for MAME as an Android App.
Currently calling it andMAME.
Have it working and will try to make a demo video soon.

The Android App allows you to select from a list of roms that are defined in a list.  The list could also be populated from contents of your roms folder.
I'm using wheel art (taken from Hyperspin) to list games and they're selected by scrolling through them in a list.
Marquees, game videos and background music are changed dynamically based on the currently selected game.



This content is simply placed into folders.



When launched, the App will check if bezel art is available to display on left/right of display.



App will need root permission.

I'm using a local Webview to drive the frontend and it interfaces with Tasker (using Javascript) to execute Android events (e.g. highlight game, launch game).

Webview code currently looks like this: - if you're interested in this stuff?

Code: [Select]
<!-- andMAME Frontend by Degenatrons, July 2013-->
<!-- Webview component to list roms and trigger "highlight" and "launch" events in Tasker -->

<style>
  body {
    background:url(file:///mnt/external_sd/andMAME/theme/window.jpg) no-repeat fixed top left;
    background-size: 100%;
    text-align: center;
    font-size: 57px;
    margin: 0px 0px 0px 0px;
  }
  img {
    padding-top: 11px;
    padding-left: 4px;
    padding-right: 4px;
  {
</style>

<script type="text/javascript">
  function list(rom, show_bezel) {
    var img_dir = "file:///mnt/external_sd/andMAME/wheel/"; 
    document.write('<a href="#"');
    document.write(' onfocus="performTask('   "'highlight',10,'"   rom   "'"   ')" ');
    document.write(' onclick="performTask('   "'launch',10,'"   rom   "',"   show_bezel   ')">');
    document.write('<img height="42px" src="'   img_dir   rom   '.png'   '">');
    document.write('</a>');
  }

  //======================================================
  //  List of roms to display in frontend view
  //  1st parameter = rom name
  //  2nd parameter = show bezel (0=False, 1=True)
  //======================================================
  list("arkanoid",0);
  list("btime",1);
  list("dkong",0);
  list("dkongjr",1);
  list("elevator",0);
  list("frogger",0);
  list("galaxian",1);
  list("kungfum",1);
  list("mspacman",1);
  list("popeye",0);
  list("rallyx",0);
  list("scramble",0);

</script>

For test purposes I have 12 games which are specified directly in the webview.  I plan to populate the list dynamically based on folder contents.  No limit on number of games that can be listed.
Wheel art for games can be displayed 1 row per game or sized to fit into a grid (like above pics) based on image dimensions.

The theme needs some design tweaks. 
I found the background image showing the arcade cab on the interwebs.  It would be possible to swap this out with templates from other FE's like MALA.

I'm using Tasker to package the App and to generate an .apk installer.  It relies on my modded version of RetroArch mentioned above.
I'll add the App to my MAME screen on the Android 2600 launcher.
« Last Edit: July 18, 2013, 02:21:15 pm by degenatrons »

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #47 on: July 19, 2013, 03:51:55 am »
Other ways to list the game roms:

As an image list:


As a text list:

Superfrog

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 393
  • Last login:June 28, 2022, 10:39:08 am
    • My YouTube Channel
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #48 on: July 19, 2013, 07:22:15 am »
Great work degenatrons  :applaud:

Not working on a android project, but this is one to keep in mind just like your YouTube series about the weecade  ;)

Like to follow your progress.

Greetings

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #49 on: July 19, 2013, 08:04:39 am »
Great work degenatrons  :applaud:

Not working on a android project, but this is one to keep in mind just like your YouTube series about the weecade  ;)

Like to follow your progress.

Greetings
Cheers Superfrog :cheers:

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #50 on: July 19, 2013, 10:20:22 am »
A quick video to show progress with the andMAME App.
EDIT: This is a recording of my telly so there will be some flickering.

« Last Edit: July 19, 2013, 10:28:23 am by degenatrons »

kayser2008

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15
  • Last login:December 07, 2014, 09:50:09 am
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #51 on: July 19, 2013, 11:01:03 am »
Congrats degenatrons
 this is better and better every update
 have followed the topic and have you have done an excellent job.
keep up   :applaud:

sharpfork

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 618
  • Last login:April 07, 2023, 12:43:42 pm
    • KADE
Re: CNC Cut Bartop Kits - Orders Open! New Models Available!
« Reply #52 on: July 19, 2013, 11:12:15 am »
Really nice work Degenatrons.  The theme looks alot like the one I ran in mala not too long ago.

galaxy SIII-cyanogen-tapatalk 4 beta


degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #53 on: July 19, 2013, 12:59:13 pm »
Congrats degenatrons
 this is better and better every update
 have followed the topic and have you have done an excellent job.
keep up   :applaud:

Really nice work Degenatrons.  The theme looks alot like the one I ran in mala not too long ago.

Thanks guys.  It's a fun project and a learning curve too.   :cheers:

I'm interested in setting up with other MALA style layouts if anybody has good ones.

kayser2008

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15
  • Last login:December 07, 2014, 09:50:09 am
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #54 on: July 19, 2013, 04:06:14 pm »
Quote
I'm interested in setting up with other MALA style layouts if anybody has good ones.

I have here a few Mala layouts that i get hover the web if you are interested i can upload them for you.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #55 on: July 19, 2013, 04:52:29 pm »
Quote
I'm interested in setting up with other MALA style layouts if anybody has good ones.

I have here a few Mala layouts that i get hover the web if you are interested i can upload them for you.

That's be great.  :cheers:

kayser2008

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15
  • Last login:December 07, 2014, 09:50:09 am
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #56 on: July 19, 2013, 05:47:23 pm »
Quote
    Quote

        I'm interested in setting up with other MALA style layouts if anybody has good ones.


    I have here a few Mala layouts that i get hover the web if you are interested i can upload them for you.


That's be great.  :cheers:


https://www.dropbox.com/sh/zex17pvsq9j5nbh/dFOoWYq5Al

here you have the link to my dropbox. :cheers:

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #57 on: July 19, 2013, 06:47:49 pm »
This is looking absolutely amazing.

I think what your doing here is very very important and could be the tipping point for bringing Android into the fold of viable options for builders here, the FE is starting to look excellent and the way you're building it out is perfect.


equlizer

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 363
  • Last login:November 17, 2019, 02:56:48 am
  • All your base are belong to us
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #58 on: July 20, 2013, 01:52:44 am »
Can't wait for a release!!  I would even pay for it  :applaud:

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #59 on: July 20, 2013, 03:27:08 pm »
Quote
    Quote

        I'm interested in setting up with other MALA style layouts if anybody has good ones.


    I have here a few Mala layouts that i get hover the web if you are interested i can upload them for you.


That's be great.  :cheers:


https://www.dropbox.com/sh/zex17pvsq9j5nbh/dFOoWYq5Al

here you have the link to my dropbox. :cheers:

Much appreciated  :)
« Last Edit: July 20, 2013, 03:50:55 pm by degenatrons »

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #60 on: July 20, 2013, 03:46:16 pm »
This is looking absolutely amazing.

I think what your doing here is very very important and could be the tipping point for bringing Android into the fold of viable options for builders here, the FE is starting to look excellent and the way you're building it out is perfect.
Hey,  thanks and that's good to know.  I see potential in Android and hope that some consider it as an option for their project.

a1pharm

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 374
  • Last login:February 25, 2024, 09:22:48 pm
  • Planning and preparation prevents problems
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #61 on: July 20, 2013, 04:49:30 pm »
Let us know when you need beta testers...

Great job so far!

 :applaud:

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #62 on: July 22, 2013, 08:44:53 am »
I made improvements to the andMAME game selection by implementing a carousel to provide a smooth scrolling effect when cycling through roms.

You can see a working mock-up of the carousel by clicking the link below.  Use cursor up/down to scroll through the list.
http://kadevice.com/temp/andMAME-carousel-with-bg/index.html

This is a MALA background provided by kayser2008  :cheers:


I'm using a jquery plugin for the carousel and am super happy to have got this working on Android  ;D

The carousel can be easily tweaked to make a circular wheel - Hyperspin style.  Click link below to see a working example.
http://kadevice.com/temp/andMAME-carousel-curve/index.html







 
« Last Edit: July 22, 2013, 11:15:23 am by degenatrons »

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #63 on: July 22, 2013, 12:49:23 pm »
Added foreground overlays to mimic what was done in the original MALA theme.  I'm making use of the Tasker scene designer to bring all the components together.



Components are:
  Background image
  Webview (for the carousel with css, javascript and jquery)
  Images (Luigi, Mario, Fly) are transparent gif
  Video (which I still need to add to this theme)

« Last Edit: July 22, 2013, 12:53:36 pm by degenatrons »

emphatic

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2008
  • Last login:Yesterday at 05:08:23 pm
  • -"Suck it, Donny!" -"No, YOU suck it.... more".
    • Emphatic's Video Game Collection
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #64 on: July 22, 2013, 05:22:37 pm »
Sweet!  :cheers:

Superfrog

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 393
  • Last login:June 28, 2022, 10:39:08 am
    • My YouTube Channel
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #65 on: July 22, 2013, 05:27:00 pm »
Nice to see Popeye in the list   :laugh2:
Good to see that's coming along the whole project  :cheers:

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #66 on: July 22, 2013, 05:32:51 pm »
This is disgustingly awesome!!

Carry on.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #67 on: July 23, 2013, 03:24:29 pm »
Added video overlay to this theme and resized/optimised video to fit the window.



The carousel is working and can launch MAME games directly based on user selection.
I still need to wire the event for changing the video when scrolling through the carousel - there are some issues with jquery/Tasker that I need to work around  :banghead:

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #68 on: July 23, 2013, 07:04:09 pm »
I think it's time you cracked out a Paypal donate button for all the time you've put into this

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #69 on: July 24, 2013, 12:55:45 pm »
I think it's time you cracked out a Paypal donate button for all the time you've put into this
I'm actually enjoying the journey so no thoughts about that just yet  :cheers:

jesjhoward

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 5
  • Last login:June 30, 2016, 07:47:45 am
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #70 on: July 25, 2013, 07:30:14 pm »
Just read this whole post... what a great job! I love this so far, keep it up!! Is there any way (that you know of) to connect  4 player rig to android? I have an ipac4, and a couple of those MK808s lying around, but I haven't tried it yet. I'd really love to replace the whole PC in my cab and replace it with something like a simple android stick. Again, great work!! =]

Edit:
Nevermind, just found your KADE product. Looking good as well =]
« Last Edit: July 25, 2013, 08:11:21 pm by jesjhoward »

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #71 on: July 26, 2013, 02:23:53 pm »
Nevermind, just found your KADE product. Looking good as well =]
:cheers:

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #72 on: July 26, 2013, 02:58:54 pm »
I sorted the video switching issue when cycling through games and is working smoothly now  :)

I made another theme using artwork from the Maximus Arcadius theme - http://www.maximus-arcade.com/pages/maximus-arcade-themes
and added a circular carousel for games.
Theme setup for andMAME did not take long at all.  I'm reusing elements (video, marquee, sounds) from my earlier theme.





I was thinking to package each of the themes into an .apk so they can be installed independently of the core application.  Will give this some more thought.
Otherwise,  I have most component for andMAME prototyped and working.

Next up,  I need to make all of the various settings configurable and readable from XML or other human readable file.


 
« Last Edit: July 26, 2013, 05:07:32 pm by degenatrons »

kayser2008

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15
  • Last login:December 07, 2014, 09:50:09 am
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #73 on: July 26, 2013, 06:53:50 pm »
I like the Mala theme more , but this is ok too
keep up.
 :applaud:

jesjhoward

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 5
  • Last login:June 30, 2016, 07:47:45 am
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #74 on: August 02, 2013, 06:25:27 pm »
Is there any way that we could get some more info on how you modified retroarch? I'd love to get this functional =] please and thank you

PL1

  • Global Moderator
  • Trade Count: (+1)
  • Full Member
  • *****
  • Online Online
  • Posts: 9392
  • Last login:Today at 02:11:51 am
  • Designated spam hunter
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #75 on: August 02, 2013, 06:52:21 pm »
Jon,

Is it theoretically possible to do a vertically oriented version to work with a setup like Mungo9000's bartops here?




Scott

UFO

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 323
  • Last login:July 22, 2022, 06:37:12 pm
  • Im nearly out of unproductive things to do at work
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #76 on: August 02, 2013, 08:08:57 pm »
Jon,

Is it theoretically possible to do a vertically oriented version to work with a setup like Mungo9000's bartops here?




Scott

This is exactly what I'm looking to use this for ... My daughter does not have enough space for even a bartop.

This FE looks totally amazing!

sharpfork

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 618
  • Last login:April 07, 2023, 12:43:42 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #77 on: August 03, 2013, 12:45:17 pm »
Is it theoretically possible to do a vertically oriented version to work with a setup like Mungo9000's bartops

I'm a big fan of dedicated Tate cabs (and this project) so I borrowed Degenatrons HTML and put up a dirty proof of concept of a tate oriented UI by tweaking the CSS a tiny bit.  I made a version where the controls are rotated with the screen and one where they don't rotate.
http://kadevice.com/temp/andMAME-carousel-vert-tate/index2.html
http://kadevice.com/temp/andMAME-carousel-vert-tate/index.html

It would be sure easy to rotate the screen the other direction too.

Degenatrons is a spectacular coder so I assume he could roll in a tate option or unique tate APK if he feels like it.  I'll help where I can if he wants it.  I ordered more Android hardware like his so I can help him at least with testing.
 :cheers:

As a side note, I have BootSectors's RetroVGA 2.0 hardware SLG working on android with a powered HDMI -> VGA converter too.
https://lh5.googleusercontent.com/-PSt4Q24m3Aw/Ufx9-dG2oOI/AAAAAAAAYho/8yDdaJtn0zw/w578-h770-no/IMG_20130802_214942.jpg

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #78 on: August 03, 2013, 03:48:09 pm »
Is it theoretically possible to do a vertically oriented version to work with a setup like Mungo9000's bartops here?

Yep,  rotation is well supported on the Android platform.  For Mungo9000 and those using a phone or tablet then the vertical orientation will just work. 
TV sticks are designed for landscape only and a slight tweak is required for them to output to vertical orientation.  The value ro.sf.hwrotation in the build.prop file can be adjusted to suit your preference. 
ro.sf.hwrotation = 0 (vertical orientation)
ro.sf.hwrotation = 270  (landscape orientation - was the default on my TV stick)

Tested and working on my TV stick  ;D

The other consideration is theme.  The theme really needs to be designed to work with vertical orientation otherwise it will just look bad.
I'll knock up a vertical theme and post some pics when I get back from my hols.



PL1

  • Global Moderator
  • Trade Count: (+1)
  • Full Member
  • *****
  • Online Online
  • Posts: 9392
  • Last login:Today at 02:11:51 am
  • Designated spam hunter
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #79 on: August 03, 2013, 03:53:39 pm »
 :woot :notworthy:   :notworthy:   :notworthy:


Scott

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #80 on: August 03, 2013, 03:58:58 pm »
I'm a big fan of dedicated Tate cabs (and this project) so I borrowed Degenatrons HTML and put up a dirty proof of concept of a tate oriented UI by tweaking the CSS a tiny bit.  I made a version where the controls are rotated with the screen and one where they don't rotate.
http://kadevice.com/temp/andMAME-carousel-vert-tate/index2.html
http://kadevice.com/temp/andMAME-carousel-vert-tate/index.html

It would be sure easy to rotate the screen the other direction too.
Thanks for looking at the carousel files sharpfork.  If we adjust the rotation in the build.prop config then the setting will apply globally to all apps so it should not be necessary to control in the css directly.  Still,  you came up with a neat way to do it and maybe there will be other uses for this method  :cheers:

As a side note, I have BootSectors's RetroVGA 2.0 hardware SLG working on android with a powered HDMI -> VGA converter too.
https://lh5.googleusercontent.com/-PSt4Q24m3Aw/Ufx9-dG2oOI/AAAAAAAAYho/8yDdaJtn0zw/w578-h770-no/IMG_20130802_214942.jpg
I gotta build me one of these  ;D

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #81 on: August 03, 2013, 04:08:55 pm »
Is there any way that we could get some more info on how you modified retroarch? I'd love to get this functional =] please and thank you
I'll post my adapted RetroArch source and some instruction for building the modified .apk  soon. 
Good to see others developing for Android.  Do you have a link to your project?

kayser2008

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15
  • Last login:December 07, 2014, 09:50:09 am
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #82 on: August 03, 2013, 05:44:03 pm »
Quote
The other consideration is theme.  The theme really needs to be designed to work with vertical orientation otherwise it will just look bad.
I'll knock up a vertical theme and post some pics when I get back from my hols.

I think  in the package that i have uploaded , as there a really nice vertical theme.

jesjhoward

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 5
  • Last login:June 30, 2016, 07:47:45 am
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #83 on: August 03, 2013, 05:48:01 pm »
Unfortunately no... This is really for a refit of my current PC based cabinet, but I do have some working knowledge of android app development (just enough to be dangerous). The PC hardware constantly fails due to its age, and an Android stick would be an awesome replacement, and I just happen to have two of them laying around. However Mame is the meat and potatoes of my cab, and it's the only system that isn't easily launched from shortcuts. I'll add some pics of my cab in its building progress soon... thanks for all of your work! =]

NOTICE:
I don't want to hijack this thread from the awesome work that degenatrons is doing, but I've found another (though not as great) Mame emulator that will work with Tasker to make homescreen shortcuts if anyone is interested. Retroarch is still going to be the better way to go, but until everything is squared away, this will work. PM for interest, and if there's enough, I'll create a new thread for it. Thanks!
« Last Edit: August 03, 2013, 09:07:47 pm by jesjhoward »

mike boss

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2645
  • Last login:October 22, 2021, 01:19:45 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #84 on: August 05, 2013, 01:05:45 pm »
That MaLa background is the custom MaLa layout I did for my Mario Bros MAME.
I think I've also posted somewhere the version with rectangle/square boxes (this way the snap can fill the entire box).
This is an amazing project you are working on.
I actually ordered two KADE units to work on something custom for a lower end tablet I have (which I plan on pairing with an iCade  to give it the desired look).
I'll no doubt keep my eyes posted on this thread.

This is AMAZING !


« Last Edit: August 05, 2013, 01:23:36 pm by mike boss »

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #85 on: August 13, 2013, 01:52:47 pm »
Quick questions about resolutions, are we stuck with widescreen resolutions or can we output the more traditional 800x600 4:3 resolutions? Also how do we handle vertical?

Thinking about pulling the Jamma board out of my Tiny Pilot cab build and making it my first ever android based cabinet but I have a Dell 17" 4:3 in there.

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #86 on: August 13, 2013, 01:59:05 pm »
Yep,  rotation is well supported on the Android platform. 

TV sticks are designed for landscape only and a slight tweak is required for them to output to vertical orientation.  The value ro.sf.hwrotation in the build.prop file can be adjusted to suit your preference. 
ro.sf.hwrotation = 0 (vertical orientation)
ro.sf.hwrotation = 270  (landscape orientation - was the default on my TV stick)

Tested and working on my TV stick  ;D

Noted.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #87 on: August 13, 2013, 04:52:46 pm »
That MaLa background is the custom MaLa layout I did for my Mario Bros MAME.
I think I've also posted somewhere the version with rectangle/square boxes (this way the snap can fill the entire box).

I see you contributed some really nice mala layouts at http://malafe.net/index.php?page=layouts  :applaud:

e.g.



Also just had a look at your FIF layout thread at http://forum.arcadecontrols.com/index.php?topic=131257.0

I'd like to use one of these as a vertical theme.  Are you ok with me making tweaks to the artwork e.g. removing the title at top?  Do you have PSD files?  If you're up for creating a generic layout for andMAME then that would be cool too  ;)

Thanks for following

I actually ordered two KADE units to work on something custom for a lower end tablet I have (which I plan on pairing with an iCade  to give it the desired look).
I'll no doubt keep my eyes posted on this thread.
:cheers:
« Last Edit: August 13, 2013, 04:54:44 pm by degenatrons »

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #88 on: August 13, 2013, 05:13:44 pm »
Quick questions about resolutions, are we stuck with widescreen resolutions or can we output the more traditional 800x600 4:3 resolutions? Also how do we handle vertical?

Thinking about pulling the Jamma board out of my Tiny Pilot cab build and making it my first ever android based cabinet but I have a Dell 17" 4:3 in there.
Can do widescreen and vertical.  The stock roms are typically 1080p and 720p but the finless roms should provide more selection.  I'm using a basic mini HDMI to VGA converter - similar to those  mentioned in one of your projects.  Was shocked to see how much these converters have dropped in price.
http://www.geekbuying.com/item/Mini-HDMI-to-VGA-with-Aduio-HD-Convertor-Cable-Adapter-for-Tablet-PC-314183.html

I have 17" Dell 4:3 and 5:4 LCD's to test with.

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #89 on: August 13, 2013, 05:21:44 pm »
I think I'd really like to kick the 60-in-1 to the curb and go Android on this new mini cab build, so I need to get serious about getting into this and setting it up properly. This could be the beginning of a beautiful new hardware setup.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #90 on: August 13, 2013, 05:48:18 pm »
Back from hols and getting my head back into this.  Actually made some good progress today.

I made an .apk installer for andMAME and installed it to a clean android stick - an MK908.  This baby is quad core with has 2GB ram  >:D
The theme and all resource files are placed on an external SD card under an andMAME folder.

Basic install process as follows:

1. Install my modified retroArch .apk
2. copy libretro_mame078.so and libretroarch-activity.so files from my SD card to /data/data/org/retroarch/lib/ folder.  This could be automated.
3. Install my andMAME .apk (each theme will be packaged into its own .apk)
4. Install full!screen .apk (to force fullscreen mode on device startup)
5. Prepare all resources needed for the theme on SD card.  Resources are mostly generic,  intended for use with all themes.  Folder structure as per screenshot.



Install was tested and working on a clean android  MK908 stick, fresh out of the box. I didn't even need to root it or flash a new bios  ;D.  My OUYA is going on ebay.

I've got lots of tweaks and configuration to work on.
For the list of roms,  I was thinking to scan the roms folder and match files to those with available wheel art.  If both items exist then the rom will appear in the carousel. 
I'm currently working with a static list of roms which can be edited but would be much better to generate list on the fly based on available files.

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #91 on: August 13, 2013, 06:25:21 pm »
And where would one find all of these modified APK files should one want to by chance install them on ones MK908 thatone also happens to have laying round?  ;D

mike boss

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2645
  • Last login:October 22, 2021, 01:19:45 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #92 on: August 13, 2013, 06:48:52 pm »
That MaLa background is the custom MaLa layout I did for my Mario Bros MAME.
I think I've also posted somewhere the version with rectangle/square boxes (this way the snap can fill the entire box).

I see you contributed some really nice mala layouts at http://malafe.net/index.php?page=layouts  :applaud:

e.g.



Also just had a look at your FIF layout thread at http://forum.arcadecontrols.com/index.php?topic=131257.0

I'd like to use one of these as a vertical theme.  Are you ok with me making tweaks to the artwork e.g. removing the title at top?  Do you have PSD files?  If you're up for creating a generic layout for andMAME then that would be cool too  ;)

Thanks for following

I actually ordered two KADE units to work on something custom for a lower end tablet I have (which I plan on pairing with an iCade  to give it the desired look).
I'll no doubt keep my eyes posted on this thread.
:cheers:


This project is fantastic and if I can I'd certainly like to do this to my tablet (as I don't use it as is).
I can check my PC and send any PSD files you might need.
I may even be able to make something custom for you, just let me know what you need (resolution, etc).
Got my two KADE units here still in the box! I need a reason to break them out, and this would be so awesome.
« Last Edit: August 13, 2013, 06:50:27 pm by mike boss »

UFO

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 323
  • Last login:July 22, 2022, 06:37:12 pm
  • Im nearly out of unproductive things to do at work
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #93 on: August 13, 2013, 07:11:51 pm »
And where would one find all of these modified APK files should one want to by chance install them on ones MK908 thatone also happens to have laying round?  ;D

I too would like to establish a location to these files to test on my Note 2...  ;) ;)

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #94 on: August 14, 2013, 08:30:18 am »
And where would one find all of these modified APK files should one want to by chance install them on ones MK908 thatone also happens to have laying round?  ;D

I too would like to establish a location to these files to test on my Note 2...  ;) ;)

I'm tidying a few things with the way themes work and adding some basic configuration.   Image proportions seem to be out on the mk808 when compared to mk908 but maybe this is down to the changes I made to the build.prop file on the mk808 stick.  Anyway,  I need to do some testing,  make things reasonably stable,  and then will make files available for others to help test an early alpha release with a few bundled themes. 

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #95 on: August 14, 2013, 08:47:45 am »
And where would one find all of these modified APK files should one want to by chance install them on ones MK908 thatone also happens to have laying round?  ;D
Gnfy p pp **dreee$exkooo quiz s

I too would like to establish a location to these files to test on my Note 2...  ;) ;)
10 aqqq0qpwa
Sea) aik(15 I wm/ql@(#(won 9l

yotsuya

  • Trade Count: (+21)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19955
  • Last login:Yesterday at 10:19:17 pm
  • 2014 UCA Winner, 2014, 2015, 2016 ZapCon Winner
    • forum.arcadecontrols.com/index.php/topic,137636.msg1420628.html
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #96 on: August 14, 2013, 10:03:37 am »
Looks like you picked the wrong day to stop sniffing glue.
***Build what you dig, bro. Build what you dig.***

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #97 on: August 14, 2013, 10:13:20 am »
Lol just saw this.  My daughter was playing with my phone, she does make some good points though.

yotsuya

  • Trade Count: (+21)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19955
  • Last login:Yesterday at 10:19:17 pm
  • 2014 UCA Winner, 2014, 2015, 2016 ZapCon Winner
    • forum.arcadecontrols.com/index.php/topic,137636.msg1420628.html
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #98 on: August 14, 2013, 10:31:44 am »
Lol just saw this.  My daughter was playing with my phone, she does make some good points though.

I DO agree with her about 10 aqqq0qpwa.
***Build what you dig, bro. Build what you dig.***

jesjhoward

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 5
  • Last login:June 30, 2016, 07:47:45 am
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #99 on: August 14, 2013, 12:16:01 pm »
Are there future plans for supporting other systems as well? If no, could you make the modified retroarch available that uses the home screen shortcut method? Again, this is great work degen.

Sent from my SPH-D710 using Tapatalk 2


degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #100 on: August 14, 2013, 12:18:05 pm »
And where would one find all of these modified APK files should one want to by chance install them on ones MK908 thatone also happens to have laying round?  ;D
Gnfy p pp **dreee$exkooo quiz s

I too would like to establish a location to these files to test on my Note 2...  ;) ;)
10 aqqq0qpwa
Sea) aik(15 I wm/ql@(#(won 9l

Gnfy  :laugh2:

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #101 on: August 14, 2013, 12:25:13 pm »
Are there future plans for supporting other systems as well? If no, could you make the modified retroarch available that uses the home screen shortcut method? Again, this is great work degen.

Sent from my SPH-D710 using Tapatalk 2

Yep,  I've been thinking about adding in support for other systems.  Those systems that support shortcuts (the vast majority of them) could be made to work already. 

Maximus

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1391
  • Last login:May 26, 2017, 05:32:05 pm
  • Plans are for fools!!!!
    • Arcade Icons
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #102 on: August 14, 2013, 12:36:51 pm »
Couple of quick questions.

- How many admin buttons do we need, or is it shifted keys to quit game etc?
- I'm assuming the Mame build supports coin switches/keys?
- Are we following the Mame standard for generating the playlist where we just name all the related files the same? ROM/ART/LOGO/SNAP etc?
- Are you thinking of a search option, say just by first letter/number of the game name? If so how would  you launch it?
- Is it trivial to support video snaps alongside regular static snaps for games in the menu?
- Will Bezels/art not show on traditional 4:3 screens?

Great work, can't wait to start testing, I'm going to build a dedicated Android testing board for this.

rablack97

  • Trade Count: (+3)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2215
  • Last login:May 11, 2022, 06:50:10 pm
  • If you don't try, you have no chance at innovation
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #103 on: August 14, 2013, 11:19:52 pm »
smart people suck.... :cheers:

Brian74

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1089
  • Last login:March 10, 2024, 01:55:58 pm
  • Yep... I built that!!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #104 on: August 15, 2013, 01:32:51 pm »
         

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #105 on: August 16, 2013, 07:52:12 am »
Couple of quick questions.

- How many admin buttons do we need, or is it shifted keys to quit game etc?
- I'm assuming the Mame build supports coin switches/keys?
- Are we following the Mame standard for generating the playlist where we just name all the related files the same? ROM/ART/LOGO/SNAP etc?
- Are you thinking of a search option, say just by first letter/number of the game name? If so how would  you launch it?
- Is it trivial to support video snaps alongside regular static snaps for games in the menu?
- Will Bezels/art not show on traditional 4:3 screens?

Great work, can't wait to start testing, I'm going to build a dedicated Android testing board for this.

- How many admin buttons do we need, or is it shifted keys to quit game etc?
For the frontend I'm using Android default controls and have tested with usb keyboard, usb joystick, mouse and touchscreen.  Also tested with 3 KADE encoder firmwares (USB/HID Joystick Encoder, PS3 Gamepad Encoder and USB Keyboard Encoder).  I have yet to test KADE rotary joystick support with Android.

So games can be selected using up/down keys (which can be defined), up/down on the joystick,  or by tapping/clicking the games in the carousel.  When selecting with mouse or touch the carousel can move multiple positions at a time to focus on the clicked item.
Games are launched by pressing Enter on keyboard (can be defined), pressing button on joystick or clicking on the central/selected image.
MAME keys can be defined in RetroArch config and input can be from keyboard, joystick, mouse.  It should also be possible to configure MAME keys via the frontend in the future. 
Sharpfork is talking to RetroArch dev's about adding plug/play support for KADE encoder aligned with our default input mappings.

I've also been testing with a KADE+ prototype (to be announced soon) which supports most of the original console controllers so have been using nes, snes, n64, gamecube, saturn, mastersystem, megadrive, tg16, atari 2600, psx controllers with Android.  We have wii remote support too so that opens some interesting wireless/bluetooth possibilities :D  Big thanks to bootsector on the KADE team for his outstanding work on KADE+ prototype  :notworthy:

- I'm assuming the Mame build supports coin switches/keys?
Yup

- Are we following the Mame standard for generating the playlist where we just name all the related files the same? ROM/ART/LOGO/SNAP etc?
Yup,  All resources are given the same filename (prefix) as the rom
 
- Are you thinking of a search option, say just by first letter/number of the game name? If so how would  you launch it?
Haven't really given this any thought.  Scrolling pages is easily done.  Filtering would be easily done too.  For searching,  I could call up an on-screen keyboard - kind of android default way of working :D - and allow user to enter search string using joystick, keyboard, mouse or screen.

- Is it trivial to support video snaps alongside regular static snaps for games in the menu?
I already have support for static snaps and video snaps.  For video I'm currently working with animated .gif but also have .flv tested and working too.  .flv is good for me because I have thousands of Hyperspin video snaps in this format.
Should also be possible to animate items displayed in the carousel.  This may impact on performance so will need to be tested.

- Will Bezels/art not show on traditional 4:3 screens?
Bezels can be made to appear at any resolution and can overlay any part or all of the screen for the duration of the game.

Great work, can't wait to start testing, I'm going to build a dedicated Android testing board for this.
:cheers:

I had a little set back yesterday when Tasker screwed up my backup files  :hissy:  I lost a couple of days work  :banghead:  Probably should set up a proper dev environment and start committing code so this doesn't happen again.
« Last Edit: August 16, 2013, 08:02:06 am by degenatrons »

rablack97

  • Trade Count: (+3)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2215
  • Last login:May 11, 2022, 06:50:10 pm
  • If you don't try, you have no chance at innovation
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #106 on: August 16, 2013, 09:17:17 am »
Who is this Tasker guy, where is he..... :angry: :bat

kayser2008

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15
  • Last login:December 07, 2014, 09:50:09 am
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #107 on: August 21, 2013, 03:39:29 pm »
Does any of you know a way to make those portable games for windows  (mame with a .batch file) but for Android ?
Is there a way to do that ?

thanks.

mike boss

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2645
  • Last login:October 22, 2021, 01:19:45 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #108 on: October 01, 2013, 08:23:01 am »
This project is super awesome and I appreciate you posting the list of emulators used.
Are these all free complete versions or are some LITE versions ? (or does it even matter?)

I have a tablet I bought and never touch, I'm hoping emulation brings some life (and use) to the tablet.

Any info would be great, thank you.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #109 on: October 02, 2013, 11:50:26 am »
This project is super awesome and I appreciate you posting the list of emulators used.
Are these all free complete versions or are some LITE versions ? (or does it even matter?)

I have a tablet I bought and never touch, I'm hoping emulation brings some life (and use) to the tablet.

Any info would be great, thank you.

:cheers:

All the emu's were free with the exception of PCE.EMU (for PC Engine/TurboGrafx) and FPse (Playstation).  Only talking £2 or £3 each.  You can go for the free alternatives if you're on a budget.  I have full versions of everything installed.

I had a long break from the Android project and hoping to get back into it soon.  Just seems like there is so much other stuff going on!

mike boss

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2645
  • Last login:October 22, 2021, 01:19:45 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #110 on: October 02, 2013, 12:01:22 pm »
I think I'll need to take a closer look when I get home tonight.
When I searched on my tablet all the app's said LITE.
For some I don't even recall noticing an other option, but it was late, I was tired, I could be wrong.

Thank you for the info.

EDIT - I think I'm perhaps better to DL the emulators online (not thru app store) then install them.
It shows some are RAR, so I take it I unzip then install.
« Last Edit: October 02, 2013, 12:26:19 pm by mike boss »

jesjhoward

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 5
  • Last login:June 30, 2016, 07:47:45 am
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #111 on: October 02, 2013, 12:59:41 pm »
Any info on the modified retroarch? I'm in the prices of rebuilding an arcade cabinet and would love to get shortcuts to mame =]

Sent from my SPH-D710 using Tapatalk 2


Mr. Dude

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 477
  • Last login:March 03, 2019, 05:12:50 am
  • Hi...
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #112 on: October 16, 2013, 09:13:17 am »
I've gotta say this is amazing degenatrons!  I picked up an Android stick about a week ago and plan to do something like you are planning with the atari box.  Do you plan on releasing andMAME on the appstore?  I would buy it for sure!  :cheers:

mancity

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 5
  • Last login:September 01, 2014, 08:58:53 am
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #113 on: November 26, 2013, 03:12:43 am »
Iv'e read through this entire thread after a search looking for this in Google and have joined the site on the back of it.

This looks awesome - Do you think this is something you will release at all? Im sure plenty would pay for this.

I have a broken tablet which I have removed the mobo from and am looking to create a MAME machine from it. I already have a MAME machine built around a Windows XP laptop, but am looking to create something smaller with this.

crawlingpeter

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 18
  • Last login:April 27, 2015, 01:41:19 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #114 on: December 02, 2013, 06:10:23 pm »
Whoa. This project looks amazing! I just registered on this site simply to post in this thread.

Are there any current updates on this front end from anyone in the know? It seems to have been a bit forgotten as of the past couple months.  :-[

I know myself as well as many others would love to donate to show our appreciation if that's ever an option as well!

crawlingpeter

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 18
  • Last login:April 27, 2015, 01:41:19 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #115 on: January 28, 2014, 10:35:07 pm »
Since this project has unfortunately not seen much life lately, I was looking for an alternative and came across this:  http://libretro.com/forums/viewtopic.php?f=29&t=1357

It's an early but very nice front end built straight into Retroarch for Android. Perhaps some of the ideas in this thread could be applied to that?

kz1911

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 63
  • Last login:May 26, 2015, 02:47:59 pm
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #116 on: February 02, 2014, 12:09:20 am »
definitely an app I'd buy, there needs to be a nice frontend for android already, especially since there are so many new android based mini pc units out

Generic Eric

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4520
  • Last login:March 05, 2024, 09:02:23 am
  • Restore! Don't maim for MAME, build from scratch!
    • forum.arcadecontrols.com/index.php/topic,143226.0.html
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #117 on: February 28, 2014, 10:43:27 am »
This looks neat.

How is it coming along? When I read the post about playing flappy bird, I was reminded of this.  Thanks.

Santoro

  • Purveyor of Shiny Arcade Goodness
  • Santoro
  • Trade Count: (+32)
  • Full Member
  • *
  • Offline Offline
  • Posts: 3051
  • Last login:December 23, 2023, 07:05:04 pm
  • Boycott Quarters!!!
    • ArcadeReplay!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #118 on: February 28, 2014, 08:29:36 pm »
Subscribe.  Hope this picks up again!

talkgeek

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 199
  • Last login:February 03, 2024, 02:30:46 am
  • Every day you wake up breathing is a GOOD day!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #119 on: March 01, 2014, 12:04:38 am »
I've been watching too - feeling concerned this thread / project has died  :dunno

Like Maximus I too would like to shelve my 60-n-1 in favour of something that gives me more FE UI flexibility - and would pay for the privilege
Currently building http://forum.arcadecontrols.com/index.php/topic,137777.0.html Mass-Replicate
Built "n0tsq3" cocktail cab http://forum.arcadecontrols.com/index.php/topic,133913.0/all.html
..and restoring a Sega MegaLo 410 Candy Cab & Moon Patrol Cab

crawlingpeter

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 18
  • Last login:April 27, 2015, 01:41:19 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #120 on: March 01, 2014, 12:32:37 am »
I believe I have lost hope for this project and that truly makes me sad because it had the most potential for any Android front-end I'd seen...

However, there is a new Android FE in town! The Gamesome Frontend.

https://play.google.com/store/apps/details?id=com.vektor.gamesome

I haven't used it yet because I just found out about it today. The one in this thread looks like it would've been much flashier so I do hope it eventually gets resurrected and they can both coexist.


fish_

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 4
  • Last login:April 19, 2014, 02:09:03 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #121 on: March 15, 2014, 12:38:05 pm »
Hello.

I have a suggestion to make. For those who own the same type of Android stick as the one used in this project, one additional option to consider is installing Linux via a Micro-SD card and compiling the required emulators. As you can see from
of my MK808 stick's desktop, I have managed to compile several Retroarch cores on an optimised Linux distribution and implement custom launchers for each game. For those wanting something more striking than custom launchers, installing an emulator front-end or configuring an animated desktop dock would be viable options.

The performance of the various Libretro cores on my system seemingly matches that of their Android equivalents, though I should note that I have not yet managed to successfully compile the N64 core. (It doesn't officially support ARMv7 architecture, leading to a variety of installation issues.) This point notwithstanding, I am most impressed at my little stick's ability to operate as both an emulation station and a lightweight desktop replacement.

Being a Linux beginner, the installation process was not without its difficulties. I started by browsing this thread in order to install a pre-configured Ubuntu distribution. The rest involved following instructions from various sources, along with conjuring a few improvisations of my own. I shall not describe these processes yet for brevity's sake, though I would be happy to give a full account of the steps I took if others are interested.

Thank you.

thehammer12

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 294
  • Last login:October 24, 2021, 01:46:34 pm
  • Arcade Breaking Specialist
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #122 on: March 20, 2014, 02:00:56 pm »
Hello.

I have a suggestion to make. For those who own the same type of Android stick as the one used in this project, one additional option to consider is installing Linux via a Micro-SD card and compiling the required emulators. As you can see from
of my MK808 stick's desktop, I have managed to compile several Retroarch cores on an optimised Linux distribution and implement custom launchers for each game. For those wanting something more striking than custom launchers, installing an emulator front-end or configuring an animated desktop dock would be viable options.

The performance of the various Libretro cores on my system seemingly matches that of their Android equivalents, though I should note that I have not yet managed to successfully compile the N64 core. (It doesn't officially support ARMv7 architecture, leading to a variety of installation issues.) This point notwithstanding, I am most impressed at my little stick's ability to operate as both an emulation station and a lightweight desktop replacement.

Being a Linux beginner, the installation process was not without its difficulties. I started by browsing this thread in order to install a pre-configured Ubuntu distribution. The rest involved following instructions from various sources, along with conjuring a few improvisations of my own. I shall not describe these processes yet for brevity's sake, though I would be happy to give a full account of the steps I took if others are interested.

Thank you.

I just ordered the MK808 and the MK908ii the other day, I thought about trying that and glad to hear someone else thought about putting linux on it. My only concern is that will I still be able to hook up joysticks and buttons? I would rather not use gaming controllers with it as I have seen some others online do.

fish_

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 4
  • Last login:April 19, 2014, 02:09:03 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #123 on: March 22, 2014, 01:53:51 pm »
My only concern is that will I still be able to hook up joysticks and buttons? I would rather not use gaming controllers with it as I have seen some others online do.
Hello.
I attached two controllers to my device via a cheap passive USB hub. Linux detected their axes and buttons without any problems.
Unlike most emulators in Android, I can program my desktop launchers to load bespoke configuration files via simple shell scripts. This way I can customise controls for each rom; my Wii Classic Controller is used in most cases, whereas my arcade stick is used for certain fighting games. When emulating DOS games, I can even use my controllers on games with no pre-programmed joystick support.

thehammer12

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 294
  • Last login:October 24, 2021, 01:46:34 pm
  • Arcade Breaking Specialist
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #124 on: March 25, 2014, 12:10:14 am »
My only concern is that will I still be able to hook up joysticks and buttons? I would rather not use gaming controllers with it as I have seen some others online do.
Hello.
I attached two controllers to my device via a cheap passive USB hub. Linux detected their axes and buttons without any problems.
Unlike most emulators in Android, I can program my desktop launchers to load bespoke configuration files via simple shell scripts. This way I can customise controls for each rom; my Wii Classic Controller is used in most cases, whereas my arcade stick is used for certain fighting games. When emulating DOS games, I can even use my controllers on games with no pre-programmed joystick support.

I was thinking about using a USB hub as well and or going with an i-pac, do you think it would be compatible?
so your swamping out controllers depending on the game? Can you post a pic of your setup....if you dont mind.

fish_

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 4
  • Last login:April 19, 2014, 02:09:03 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #125 on: March 27, 2014, 06:01:03 pm »
I was thinking about using a USB hub as well and or going with an i-pac, do you think it would be compatible?
so your swamping out controllers depending on the game? Can you post a pic of your setup....if you dont mind.
Hello again.
If the I-PAC is compatible with Ubuntu—as appears to be case—then I would expect it to be recognised by a Linux-enabled MK808. That said, I am far from knowledgeable about such a peripheral.
As for your request,
is an annotated photograph of my system. You will notice that my two game controllers pass through the same adapter, which are thus detected by Linux as a single device with a large number of axes and buttons. Thanks to my shell scripts however, each game is pre-configured to the physical controller and button layout that best suits it.

thehammer12

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 294
  • Last login:October 24, 2021, 01:46:34 pm
  • Arcade Breaking Specialist
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #126 on: March 31, 2014, 11:57:21 am »
I was thinking about using a USB hub as well and or going with an i-pac, do you think it would be compatible?
so your swamping out controllers depending on the game? Can you post a pic of your setup....if you dont mind.
Hello again.
If the I-PAC is compatible with Ubuntu—as appears to be case—then I would expect it to be recognised by a Linux-enabled MK808. That said, I am far from knowledgeable about such a peripheral.
As for your request,
is an annotated photograph of my system. You will notice that my two game controllers pass through the same adapter, which are thus detected by Linux as a single device with a large number of axes and buttons. Thanks to my shell scripts however, each game is pre-configured to the physical controller and button layout that best suits it.

Good set up right there, you should at least throw it in a bartop kit or something. I think it would be pretty cool if you did that.

 Im definitely gonna go that route with the i-pac w/ linux but I gotta do more research before I mess this up haha.

spongebobgorilla

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 2
  • Last login:April 15, 2014, 12:02:17 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #127 on: April 01, 2014, 04:20:31 am »
The frontend now launches directly into MAME games using custom shortcuts  ;D.  These shortcuts need data to identify the rom and this data is passed to my modified build of RetroArch.

Custom shortcuts are easily created with the Tasker App



How exactly does the rom name get passed to Retroarch. I'm trying to replicatethis but having trouble with the code. Any help would be greatly appreciated.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #128 on: April 01, 2014, 05:19:53 am »
The frontend now launches directly into MAME games using custom shortcuts  ;D.  These shortcuts need data to identify the rom and this data is passed to my modified build of RetroArch.

Custom shortcuts are easily created with the Tasker App



How exactly does the rom name get passed to Retroarch. I'm trying to replicatethis but having trouble with the code. Any help would be greatly appreciated.

My modified build of retroarch reads data from the shortcut to determine which rom to launch.
For the fontend,  I'm using Javascript within the HTML/webview to launch a task with romname as a parameter.  The task launches the rom and does various other rom specific stuff if resources exist e.g. display bezels.

Code: [Select]
performTask('launch',10,romname,0);
I've been away for a while but will be picking up work on this again as there seems to be a lot of interest in it.
« Last Edit: April 01, 2014, 05:21:42 am by degenatrons »

spongebobgorilla

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 2
  • Last login:April 15, 2014, 12:02:17 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #129 on: April 01, 2014, 05:41:44 am »
There certainly is. is there any chance you can release an APK or your modded retroarch, as this is the only emulator i'm having trouble creating shortcuts for. Or perhaps provide a more detailed instruction on how to modify it ourselves?

Keep up the good work though...

fish_

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 4
  • Last login:April 19, 2014, 02:09:03 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #130 on: April 01, 2014, 03:39:22 pm »
Im definitely gonna go that route with the i-pac w/ linux but I gotta do more research before I mess this up haha.
As a preliminary piece of advice, it is important to ensure you have suitable accessories. Few have faith in the unbranded power supply bundled with the MK808, so a replacement PSU is strongly recommended. I use a 2.1 amp model that I found for a reasonable price on Amazon. A Class 10 Micro SD card is also an advisable purchase, though it may be possible to boot to Linux directly from a USB device.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #131 on: April 01, 2014, 04:56:05 pm »
Im definitely gonna go that route with the i-pac w/ linux but I gotta do more research before I mess this up haha.
As a preliminary piece of advice, it is important to ensure you have suitable accessories. Few have faith in the unbranded power supply bundled with the MK808, so a replacement PSU is strongly recommended. I use a 2.1 amp model that I found for a reasonable price on Amazon. A Class 10 Micro SD card is also an advisable purchase, though it may be possible to boot to Linux directly from a USB device.
I had considered Linux on MK808 before setting out with the Android stuff.  I've previously installed Picuntu as per this step by step guide on the miniand forum.  Basic install was straight-forward but I had driver issues (video and network) and found myself spending lots of time troubleshooting and not making progess.  That's why I dropped the idea.  If i'm honest,  I was only looking to Linux at the time because it was more familiar to me.  I had planned to use Puppy Linux.
I found power supply issues on MK808 were resolved after update to latest Minix HFW firmware.  I've never had a problem with the bundled supply.

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #132 on: April 01, 2014, 05:07:54 pm »
There certainly is. is there any chance you can release an APK or your modded retroarch, as this is the only emulator i'm having trouble creating shortcuts for. Or perhaps provide a more detailed instruction on how to modify it ourselves?

Keep up the good work though...
Thanks.  My plan is to make the modded retroarch available with install instructions.  It will likely be a prerequisite for andMAME.

crawlingpeter

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 18
  • Last login:April 27, 2015, 01:41:19 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #133 on: April 01, 2014, 11:22:58 pm »
I've been away for a while but will be picking up work on this again as there seems to be a lot of interest in it.

This is seriously the best news I've heard all week! I know I would personally be not be opposed to paying quite a bit for a finished version of this.

Also, would it be possible for your project to use the Android intents RetroArch already has in place?

degenatrons

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 364
  • Last login:March 29, 2016, 05:53:23 pm
    • KADE
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #134 on: April 02, 2014, 07:50:18 am »
I'm taking a look at the latest retroarch v1.0.0.2.
Noticed that the latest build v1.0.0.2-r36 available on playstore doesn't include MAME cores. I could've installed manually but to keep things simple have picked up an earlier release from their download page.

http://www.libretro.com/index.php/downloads/
RetroArch-armv7-v1.0.0.2-r34.apk

The build includes these MAME cores.
MAME 2003 (0.78)  - Older MAME which is less demanding on resources and good for mobile devices
MAME 2010 (0.139) - Intended for more powerful devices.  Same as MAME4Droid.  CPS3 support is included.

Here's the changelog.  Not much in there about Android.
http://www.libretro.com/index.php/retroarch-1-0-0-2-changelog/

I was hoping to see intents added to simplify integration with andMAME frontend.  I'll take a look at the code to see if anything is changed in that respect.

crawlingpeter

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 18
  • Last login:April 27, 2015, 01:41:19 pm
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #135 on: November 27, 2014, 09:15:03 am »
Even though I had forgotten about this thread for a while, RetroArch has been improving in every category since the last time you posted so maybe they have fixed all the issues that were getting in the way?!

Galahad

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 6
  • Last login:June 12, 2021, 03:46:17 pm
  • İn god we trust one
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #136 on: September 18, 2016, 09:55:21 am »
Hi.  I decided to use my android tv box as a processor of my bartop
arcade machine.  Therefore i set a frontend to android tv box so it launches bu holding
android background.

I used the follwing apks
nova launcher (set as default home manager)
and a startup apk (set mame to start automatically)

Here is the link in youtube


RetroDevil#2

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 1
  • Last login:March 15, 2022, 08:28:25 am
  • I want to build my own arcade controls!
Re: Making an Android Frontend (Android 2600:Part 1)
« Reply #137 on: December 29, 2021, 09:01:49 am »
Ahoy !!
So I love this project .
Me and the boys are jumping into making a open sourced android frontend now .

We have been reverse engineering DIG frontend and stuff like that .
This project is very cool and also deserves a look. 


I have been trying to recreate your project as well.
I don't understand a few things .
Retrying and review this thread today .

A few things that really stand out
built in bezels
System on page then folder with roms .
Ability to add virtually anything.


« Last Edit: December 29, 2021, 09:06:01 am by RetroDevil#2 »