Author Topic: ODK project set up: initial issues  (Read 29059 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: ODK project set up: initial issues
« Reply #75 on: January 27, 2013, 08:31:30 PM »
NICE WORK!!!  Just finished a 3-player game of Diddy Kong Racing with Melinda and Robbie (2 OUYA controllers, one modified N64 controller).  Absolutely no problems mapping or playing the game.

Uploaded the latest build (same link above) for OUYA devs who are following.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: ODK project set up: initial issues
« Reply #76 on: January 27, 2013, 08:55:53 PM »
Awesome.  Think I've finally got the monkey off the back on this one.  Now I can focus on persistent controller IDs and fun stuff like a skin customization activity.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: ODK project set up: initial issues
« Reply #77 on: January 28, 2013, 06:45:15 PM »
If you haven't already started, I think I'll take a stab at that joystick-navigable alternate layout for the input mapping screen.

Any thoughts on how users could activate the "cancel" and "unmap" buttons in the popup listener?  Would it be reasonable to make them use the touchpad for that?  Does tapping the touchpad simulate a mouse click?  Another option might be to the have the user simply tap the touchpad to cancel (doesn't matter where) and long-touch the touchpad to unmap.  Of course there would be some instructions in the popup for that.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: ODK project set up: initial issues
« Reply #78 on: January 28, 2013, 08:13:06 PM »
Using the touchpad as a mouse is pretty awkward, IMO.  I'd prefer to have tapping cancel and long-press unmap like you mentioned.  Yes, tapping simulates a click.  It is very similar to the touchpad on a laptop (which I've never liked, haha).
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: ODK project set up: initial issues
« Reply #79 on: January 28, 2013, 08:29:53 PM »
Ok, sounds good.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: ODK project set up: initial issues
« Reply #80 on: January 29, 2013, 08:03:40 AM »
I was thinking about this some more, and it might be better to just leave Cancel/ Unmap as buttons rather than tap/ long-press.  My dislike for touchpads is just my personal preference, and doesn't really represent the majority of people (if it did, touchpads would not be a standard for every laptop sold in stores, haha!)  Having the functions on normal buttons would free up the long-press action to be used elsewhere (for example mapping virtual buttons to the touchpad, which I'll be looking into at some point).
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: ODK project set up: initial issues
« Reply #81 on: January 29, 2013, 08:06:25 AM »
Ok, well that's the easiest anyhow in the short term since it requires no changes to the listener.  I put together something last night, need to tweak a few things but it's mostly implemented now.  Should have something to push in the next day or two.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: ODK project set up: initial issues
« Reply #82 on: January 29, 2013, 11:57:35 PM »
I made a few OUYA-specific changes to the settings and resources.  There is now a controller profile for OUYA, which puts start on the "Y" button and menu on the "A" button.  I also disabled the actionbar (not usable on the OUYA), so the in-game menu is now accessible.

The OUYA customization is coming along quite nicely!

Latest Build.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: ODK project set up: initial issues
« Reply #83 on: February 08, 2013, 07:34:38 AM »
Paul - I'm sure you're swamped right now with real work, so no pressure.  Just wondering what your timeframe is for the next release update, so I can prioritize things on my list.  If it will be a while, I'll take my time on some things, but if you might get to it this weekend then I'll work on some quick & dirty bugfixes.

Since your workstation has been in storage for a while, I'm guessing you might need to update some SDK/eclipse stuff first.  In case it helps, here's my current config:

Code: [Select]
Eclipse 4.2.1 (Juno)
ADT Plugin - https://dl-ssl.google.com/android/eclipse/
  Developer Tools
    Android DDMS                 21.0.1.v201212060256-543035
    Android Development Tools    21.0.1.v201212060256-543035
    Android Hierarchy Viewer     21.0.1.v201212060256-543035
    Android Traceview            21.0.1.v201212060256-543035
    Tracer for OpenGL ES         21.0.1.v201212060256-543035
  NDK Plugins
    Android Native Development Tools 21.0.1.v201212060256-543035

Android SDK Manager
  Android SDK Tools 21.0.1
  Android SDK Platform-tools 16.01
  Android 4.2 (API 17) rev. 1

And here's the commit with multi-core compile instructions:
https://github.com/paulscode/mupen64plus-ae/commit/473690483ab2b9589562b88b197c6ebc74778db
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: ODK project set up: initial issues
« Reply #84 on: February 08, 2013, 10:18:29 AM »
It will probably be a couple more weeks until I'll have time to do an update.  This weekend I really need to finish unpacking, as much as I hate it!
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: ODK project set up: initial issues
« Reply #85 on: February 08, 2013, 11:00:14 AM »
I don't envy you a bit. :P  I detest unpacking...

No problem, I'll take my time on some things then ;)
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: ODK project set up: initial issues
« Reply #86 on: March 08, 2013, 10:49:12 PM »
Any OUYA devs who might be following the project, here is the latest and greatest build:

BOU-YA!

The app is pretty much good to go at this point.  I'll probably tweak a few more default settings (such as making the OUYA input profile load by default the first time, so folks can start playing immediately without visiting the mapping section).  And I still need to write the donation section (waiting for the review by OUYA to see if they'll approve the app for their store or not).

Be sure to report any speed or compatibility differences with this build compared to earlier ones if you notice anything like that
« Last Edit: March 08, 2013, 10:51:55 PM by Paul »
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted