engaging-computing / isense-hardware Goto Github PK

They are exactly the same as the SOR River Walk app's icons. (Not really a bug/issue, but Jeremy will be pushing these new icons on the app soon.)

Don wants all phones to be synced to a similar time-frame.

Update: we will learn DatagramSockets and use UDP connections between phones.

Also, make experiment searching limited to only compatible experiments.

Finally, customize toast messages and make the background look nicer.

The data could captured by the PINPoint after the weather balloon experiment could not be retrieved using the PINPoint software.

When you first open the app you should get a prompt for the name. Then you should connect to the pinpoint

enable a way to either display all the data on the left hand column or to split it up by pages (and allow users to jump through pages)

the sync time button on the RAAC app should notify the user if the time was successfully or unsuccessfully synced

It tries calling a Toast in a loop other than the main UI thread and thus force closes the app. The toasting should occur once that method returns instead.

In the data set from the weather balloon trip, the latitudes were all correct, but the longitudes were incorrect. I adjusted each longitude by 0.69197 to fix this problem, but the data still seem a little strange. See: http://isense.cs.uml.edu/newvis.php?sessions=4927. Zoom out a bit. The GPS points are arranged in sets of odd looking diagonal rows.

I suspect the problem may have something to do with variable types. In these parts, longitude values are always negative. The first digit is 0 around here, but the values have three digits (unlike latitude values). I'm not sure whether this error is being introduced in the PINPoint firmware, or during the data capture. (Michael pulled this data set from the PINPoint without using DUCK.)

All android apps should have they own repository.

@jdalphon @mmcguinn

Missing pictures package on github!!

maybe to "Upload to iSENSEProject.org"

• Media Manager (done)
• Lint Fixes (done)
• Data Saving (done)
• Sample Rate (done)
• Sensor Checking (done)
• Data Field Manager (done)

The loading screen is pretty and all, but doesn't actually load anything.

Additionally, our code is not well commented, logs failure upon success, unorganized, and hard to read. That should be fixed.

Experiment fields are currently hard-coded to a particular order.
We must fetch experiment fields from an experiment, look at the fields, and upload the data in the order it wants.

Characters cannot include things like &, *, etc. It "messes up" the URL for the request sent to the site.
Accepted characters in any text field should only include:
A-Z, a-z, 0-9, [space], _, -, ., ,, ;, : ... add more as appropriate.

Michael/Jeremy,

Would you please add a 5th pulldown location option for the boat app: Claypit Brook.

Also create the matching session on iSENSE, in experiment http://isense.cs.uml.edu/experiment.php?id=350 .

The name of the session should be "Claypit Brook" and it should be hard-coded to
42.642420, -71.352910 .

This should be ready and installed on the "boat phone" for Friday's class.

@jaypoulz @stowellm

the RAAC app should sync time after successfully connecting to the pinpoint every time.

The RAAC app should round numbers on the right hand column to three sig figs.

old:
pH: 6.12345

new:
pH: 6.12

Sensors are currently limited to Temperature and/or pH just for the SoR workshop. This should be addressed as soon as it is over.

RestAPI on our side (and all the objects associated with it) are lagging behind all the new/removed stuff from the API. We need to go through each API function, see what it does/returns, and re-configure RestAPI/object files to match appropriately.

Sample intervals must also be implemented into app.

No matter how you describe your saved viz, when it shows up in your Profile page, the place where the description should be just says "blah."

Weird things are going on with that XML layout for layout-land. @nickavv, could you hold onto a clean, working version of the main, blue, layout orientation XML code for the RAAC app and replace isenseDev/iSENSE-Hardware's version of that XML layout? This one is force closing... probably another merge bug.

Add buttons and TextView widgets for portrait layouts.

Removed Description and change xml layout to say "name" instead of group name.

The app just starts you off with terms and conditions... kind of an ugly view to the start of the app.

Ideas for splash:

• Welcome text
• Link to an "About App" dialog.
• Link to a "How To Use App" dialog.
• Checkbox/link for the EULA
• Green "Continue to App!" button
  - Continue only if they said they read and accept the EULA!
• Red "Exit" button

Loading Screen:

• Awesome rotating logo thing

Jar files are magically defining AndroidManifests, Dalvikm 1 errors are occurring, Jeremy's Eclipse stopped working, project doesn't import right half the times... We've copied over all the significant code and jar over to a new, stable project that (hopefully) doesn't do this.

This was my fault from a SharedPreferences fix we made to the RAAC app a while ago. It seems the RAAC app implemented our new changes, but kept some old code as well when it merged, giving it an error (probably just me forgetting to switch an arrow in the mergetool). This has already been resolved and will be pull requested.

This app is more "general" than the Canobie Lake Physics application. In this case, we should have landscape functionality and tablet-sized layouts for our tablet users. No longer is this just a "hey-I-am-not-crazy-enough-to-bring-a-tablet-on-a-roller-coaster" app.

Things to accomplish:

• Landscape Layout for Phones
• Portrait-Large for Tablets
• Landscape-Large for Tablets
• Make a whole new set of drawables for the tablet layouts
• Make every dialog an activity

This will eliminate the need for default experiment values.

• Implement QR code functionality to select an experiment
• Allow the parsing of failed-to-upload experiments from the .csv files in the SD Card
• Potentially save said failed upload for upload later?
• Bring some changes from Data Collector app (ie the above changes) into Canobie App as well

• Clear all traces of "Amusement Park" in this app.
• Handle temperature for celsius/kelvin/fahrenheit (add more strings and fix the boolean arrays)
• Implement user's choice of what data to record when selected/deselected items
• Add "Steps" to dialogs
• Add session description to the end
• Debug SD Card error
• Re-vamp the main layout and make it pretty!

List of things Don wants to see:
https://www.sugarsync.com/pf/D6966681_8781121_642579

(Also as an aside, add Jeremy's changes to RestAPI to make createSession work again in the Canobie app).

Make a single RestAPI.java that all Android apps use/link against. This will help avoid multiple RestAPI files, especially ones that may slightly differ from others.

allow special characters such as & for group names aka sanitize your inputs

I will be releasing version 2.0 of iSENSE Imports sometime early next week. These will be fully documented, and I will be releasing Java-Docs coincidentally. These WILL effect the behavior of current applications, so I recommend that you all read the API carefully and make any modifications as are necessary.

Will include:
-- Default behavior changes RestAPI changing -- it will now default to iSENSE NOT dev.
-- Updated parameters for functions (I was going to deprecate but support the old ones, but I happen to want to reuse names and the arguments have changed but are of the same type.)
-- new generic waffles (toasts that don't overlap and are build to easily but customized (@stowellm)
-- the removal (or deprecation) of any API functions not currently in use
-- self policing logs and error messages that are labeled appropriately (e.g. errors will throw exceptions or log in red)
-- possible reimplementation of self-caching responses for improved speed (no promises here)
-- other stuff I'll deal with on Monday

@stowellm @jdalphon @fgmart @AlanRosenthal @nickavv

sometimes you cannot press the push to iSENSE button even with data.

if there is data and you are logged in you should be able to push to iSENSE.

Toast messages are ugly.

This is a feature.

Waffle messages (trademark by Mike) are the way to go.

Does the org. issue tracker merge all repos?

Start being able to push the data on the LabQuest to push to iSENSEDev via RestAPI

If a user has a profile picture it is not displayed on the profile page.

If an experiment is "closed" on iSENSE and we try pushing data to it, we get back a 400 status error, yet the apps will still say that we succeeded. Error checking needs to be added for all of these apps, perhaps a toast that says "Could not push data to this experiment; it may be closed."

Create an option in the settings to auto upload data/manually push

Now that we can find out what fields are being recorded, we can determine what sensors are needed and whether or not the user's Android Device will be compatible with the experiment. Also, here is the best place to determine what sensors we are enabling/disabling for the experiment, as well as implementing our sorting algorithm to upload data in the correct order.

Such as set up sensors, etc

Should also be able to configure username and password. Default username should go away.

the experiment ID in the science of rivers app should be saved in preferences

Sometimes when pushing data, no dialog appears for visualizing stuff on iSENSE. Error checking/toasting should occur.