Android Driver Station

[tanogirl]

This might be a stupid question... but is there a trick to installing it? I have an Asus MemoPad and could get it to install but the app wouldn't open.

[dmaciel10123]

Originally Posted by tanogirl

This might be a stupid question... but is there a trick to installing it? I have an Asus MemoPad and could get it to install but the app wouldn't open.

Is it crashing or just not opening at all?

[MatthewC529]

Originally Posted by tanogirl

This might be a stupid question... but is there a trick to installing it? I have an Asus MemoPad and could get it to install but the app wouldn't open.

Hmm thats interesting. There is really no way to get Log information in this case which is a problem... maybe I will try to create a Pull Request to get a logging system in place for issues like this.

If you can try running it and get LogCat information that would be awesome. It will report the exception if there is one and five us the exact processes leading up to and after the exception as well as the Stack Trace.

[guniv]

It may have something to do with his Android version. That sounds like an old device that prooooobably isn't supported very well.

Now that Android Wear watches are out, someone should make this app for it

[dmaciel10123]

Originally Posted by guniv

It may have something to do with his Android version. That sounds like an old device that prooooobably isn't supported very well.

Now that Android Wear watches are out, someone should make this app for it

It could be the version or the IP. When I was trying to get the camera working the app wouldn't open if the IP had more than 2 numbers in a segment (ie 192.168.1.70) because of the way the all sets the team number from the IP. All depends on the way it's acting when they try to open it.

If they were able to install it though I don't think it's the android version.

[tanogirl]

Its not the device, its less than 6 months old and running Jelly Bean- could that be the problem? And this is what I get when I try to open it .

[dmaciel10123]

Originally Posted by tanogirl

Its not the device, its less than 6 months old and running Jelly Bean- could that be the problem? And this is what I get when I try to open it Attachment 17136.

Did you change the IP on your device before opening it? Go into the WiFi settings and long tap the network you're on. Tap on modify network and then check the "show advanced settings" option. Then change the IP Settings from "DHCP" to "Manual" or "Static", and change the IP to 10.12.34.6 and the subnet mask or gateway to 255.255.255.0

This may solve the crash but you'll lose Internet connectivity until you put the network back into DHCP mode.

To use it on a robot you'd change the 1234 in the IP to your team number, ie 10.35.25.6 for my team.

[tanogirl]

Ohhh that was it! Got it open and it looks great! Can't wait to try it with one of our bots!

[MatthewC529]

Originally Posted by guniv

It may have something to do with his Android version. That sounds like an old device that prooooobably isn't supported very well.

Now that Android Wear watches are out, someone should make this app for it

Just to make this clear, the program as it is now is listed as supporting a Minimum API Level of 14. This means it will support Ice Cream Sandwich and Above. As it stands now, until it is changed because it can be even further lowered, devices that still run Honeycomb and Lower can NOT run the program. The Target SDK is 18 (Jelly Bean 4.3) but it should support anything between Ice Cream Sandwich and Android L.

Just making this clear since this means the App will (and there is nothing in the code to prevent it from doing so, Eclipse would let you know that) run on any Jelly Bean device.

[raystubbs]

Just so that everybody knows, there is code in the app so support joysticks, it should work with any joystick that you manage to connect to your device including OTG and bluetooth. This feature is untested, so I would appreciate feedback if you try any kind of joystick.

[raystubbs]

Originally Posted by MatthewC529

Hmm thats interesting. There is really no way to get Log information in this case which is a problem... maybe I will try to create a Pull Request to get a logging system in place for issues like this.

If you can try running it and get LogCat information that would be awesome. It will report the exception if there is one and five us the exact processes leading up to and after the exception as well as the Stack Trace.

I now this is an older post, but just so people know there is an app on the android market called ´aLogcat´ that does allow you to get log info.

[raystubbs]

Originally Posted by MatthewC529

Hmm thats interesting. There is really no way to get Log information in this case which is a problem... maybe I will try to create a Pull Request to get a logging system in place for issues like this.

If you can try running it and get LogCat information that would be awesome. It will report the exception if there is one and five us the exact processes leading up to and after the exception as well as the Stack Trace.

I know this is an older post, but just so people know there is an app on the android market called ´aLogcat´ that does allow you to get log info.

[raystubbs]

Originally Posted by MatthewC529

Hmm thats interesting. There is really no way to get Log information in this case which is a problem... maybe I will try to create a Pull Request to get a logging system in place for issues like this.

If you can try running it and get LogCat information that would be awesome. It will report the exception if there is one and five us the exact processes leading up to and after the exception as well as the Stack Trace.

I know this is an older post, but just so people know there is an app on the android market called ´aLogcat´ that does allow you to get log info.

[MatthewC529]

Originally Posted by raystubbs

I know this is an older post, but just so people know there is an app on the android market called ´aLogcat´ that does allow you to get log info.

Alternatives include CatLog, Logcat Extreme, Log Viewer and so on. Plenty of apps to this. Thanks for adding that on!

It wouldn't hurt to have a logging utility built in to the app though no? As an easily retrievable log file? A simple endeavor using Log4j. I have also been looking into the best way to retrieve a video feed, automatically changing and reverting the IP and keeping track of the Team Number between application instances. Just to make it more convenient without having to have people dig through the Network Settings to run it on their phone, it would simply be more convenient to have the app do it for you with sufficient permissions.

[raystubbs]

Originally Posted by MatthewC529

Alternatives include CatLog, Logcat Extreme, Log Viewer and so on. Plenty of apps to this. Thanks for adding that on!

It wouldn't hurt to have a logging utility built in to the app though no? As an easily retrievable log file? A simple endeavor using Log4j. I have also been looking into the best way to retrieve a video feed, automatically changing and reverting the IP and keeping track of the Team Number between application instances. Just to make it more convenient without having to have people dig through the Network Settings to run it on their phone, it would simply be more convenient to have the app do it for you with sufficient permissions.

Yes, I've figured out all of this except efficient video. I just haven't taken the time to implement the features. This app was designed to be functional and light, but not super convinient. It was more a test run than anything. Right now I'm working on whan I want to be the final implementation of the app. One of the main complaints with the current one seems to be that it is not compatible with all drive systems. So on this other implementation I am going to add the other requested features, but also I'm adding a 'drag and drop' interface to customize the layout of the controls.