Note that there are some explanatory texts on larger screens.

plurals
  1. POplayn android problems - Netbeans cannot find device
    primarykey
    data
    text
    <p>As the title states, I'm having troubles running the android version of my playn projects. I found the setup incredibly difficult, but the html and java versions are now running. </p> <p>I have have eclipse working now, but much prefer netbeans. Please note that I am able to succesfully deploy <em>regular</em> android projects with netbeans.</p> <p>I have no experience with maven whatsoever, so I'm trying to avoid the command line.</p> <hr> <p><strong>Netbeans</strong></p> <p>I followed this tutorial: <a href="http://www.gamefromscratch.com/post/2012/05/24/Using-Netbeans-712-with-PlayN-13.aspx" rel="nofollow">http://www.gamefromscratch.com/post/2012/05/24/Using-Netbeans-712-with-PlayN-13.aspx</a></p> <p>There are some problems at this point:</p> <blockquote> <p>In the Actions list, select Run Project. Under Execute Goals: enter android:deploy android:run, and under Set Properties: enter skipTests=True and android.device=usb. Finally click OK. </p> </blockquote> <p>When I enter all the information, "run" is still greyed out on the android project. When I go back to the actions list, everything is blank again. Seems like the settings are not saved. However, I can run the project by rightmouse selecting the project -> custom and enter the details there. It's quite annoying to fill everything in each time I want to run the project, but that's a problem to worry about later I guess.</p> <p>When running the project, it always throws one of these errors:</p> <pre><code>Device not found Device is offline ADB not connected </code></pre> <p>When I use adb devices, it lists my device just fine.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload