›

Screen flashes when trying to login to launcher

InhumanInhuman Posts: 1Member
in ODK (OUYA Developer Kit)

When I run the OUYA Launcher and try to login with my existing account the screen flashes back and forth between a white screen that says "Contacting ouya servers..." and the purple screen with the new user and existing user buttons on it. This happens on both the emulator and my tablet. Has anyone else seen this behavior and know how to fix it?  Thanks!!

Comments

  • TheMaskedFoxTheMaskedFox Posts: 10Member
    Yeah.  A couple of us over on the ODK 0.0.5 announcement made the same observation.  I'm dead in the water on development right now because I can't get the launcher past the login screen.  Same issue.  If you don't provide login credentials, you can't pass.  If you DO provide login credentials, the launcher just gets stuck in a loop.  Frustrating.
  • atsats Posts: 2Member
    You can launch a package from the command line once an emulator is started (not sure if it also works this way for the real device) and the game will start regardless of whether you're on the login screen or not. Assuming you have the android tools on your path, you can run:

    adb shell am start -a ouya.intent.category.GAME -n com.foo.bar/com.foo.bar.SomeActivity

    and it will start the activity. There are other commands to install .apk files so you can do all of your development without having to interface much with the OUYA menu.
  • jbanesjbanes Posts: 45Member
    edited January 2013
    User ats is on the right track. The only need for the launcher is to test the launcher. (e.g. Info pages, icons, etc.) Otherwise the software can be tested by launching it directly from IDE/command line, or by using the Android default launcher. (Not as pretty, but it works.)

    I hope Ouya fixes this problem soon. It even happens on my MK808 stick. It makes testing very difficult.

    Pro tip: To test the launcher with your app, launch the emulator and login. After the screen flashes a few times, disable the network by hitting F8. This will cause an error that will allow you to skip the screen flashing process. Note that the tools may also lose track of the emulator at this point, so it's really only useful for testing the launcher info to make sure your app looks good.
    Post edited by jbanes on
  • TheMaskedFoxTheMaskedFox Posts: 10Member
    Both of these replies are immensely helpful.  Thank you!
  • mjoynermjoyner Posts: 168Member
    ick, works fine on my Pipo S1, but yeah, fails miserable on the MK808

    02-02 18:41:14.746: D/IAP Client Service(1553): Getting from URL: https://devs.ouya.tv/api/v1/consoles/-106598380
    02-02 18:41:14.956: D/IAP Client Service(1553): Got response with code: 400
    02-02 18:41:14.966: D/IAP Client Service(1553): Response body was: {"error":{"code":2007,"message":"Invalid console Uuid was provided"}}
    02-02 18:41:14.966: D/IAP Client Service(1553): Response body was: {"error":{"code":2007,"message":"Invalid console Uuid was provided"}}
    02-02 18:41:14.966: E/IapGateway(1553): Got failure response with message: {"error":{"code":2007,"message":"Invalid console Uuid was provided"}}
    02-02 18:41:15.026: D/inAppPurchase(1539): Binding to StoreService
    02-02 18:41:15.066: D/inAppPurchase(1539): Successfully bound to IapService
    02-02 18:41:15.076: D/IAP Client Service(1553): Posting to URL: https://devs.ouya.tv/api/v1/gamers/me/consoles
    02-02 18:41:15.386: D/IAP Client Service(1553): Got response with code: 200
    02-02 18:41:15.436: D/IAP Client Service(1553): Response body was: {}
    02-02 18:41:15.436: D/IapGateway(1553): received success response
    02-02 18:41:15.436: D/IAP Client Service(1553): Response body was: {}
    02-02 18:41:15.436: D/IapGateway(1553): response body: {}
    02-02 18:41:15.436: D/IAP Client Service(1553): Response body was: {}
    02-02 18:41:15.446: D/dalvikvm(1553): GC_CONCURRENT freed 389K, 65% free 6600K/18567K, paused 11ms+4ms, total 59ms

  • chrissfootchrissfoot Posts: 14Member
    This looks like a security feature to me. A way to stop non-ouya devices from pretending to be ouyas. Sure is annoying for developing though!
  • JeromyNixJeromyNix Posts: 3Member
    This looks like a security feature to me. A way to stop non-ouya devices from pretending to be ouyas. Sure is annoying for developing though!
    It is absolutely no doubt an annoying problem for those of us that want to get started on development but haven't got a dev-console, and here's the biggest problem i'm finding with it, I can't get my controller up and running (non-ouya controller) without getting into the Ouya launcher, so while i can navigate via keyboard, it's the actual controller functions i need to test. 
    Note this is my first attempt at developing anything for a non-Windows system... (unless you count for linux via Mono)
Sign In or Register to comment.