kevinfodor / my-sensors Goto Github PK

Issue submitted via email by user: anialator

"Wondering if you would would be able adjust the UI? I have attached a screen shot to show how the rows are not wide enough.

"

Issue was reported by: [email protected]

Hello good afternoon ....
I have a problem with pequrño very good application ...

In the part of the sensor grip sensors ... you tell me .... that will not date?

A failure of the talves application?
Or has my phone said sensor does not work?

My response:

Sorry you are having some trouble with the app. From time to time, the Android OS adds additional sensors to the types available. When the application was written these new types are not know. This is why you see some of the "?" markings.

I am not familiar with the "grip" sensor, but what the screen is telling you is that no events have been received for this sensor yet. You probably need to do something to generate one of the events (perhaps grip it tight?). Once the events are generated the application will show the values.

For instance this happens on my device when using the "ChopChop Gesture" sensor. There is no data reported until I very strongly shake the phone. At that time data from the sensor is reported.

What steps will reproduce the problem?
If you go away from or background the app and then come back to it, the sensor 
list grows in size by the number of available sensors. This happens each time 
you leave the app and come back.

What is the expected output? What do you see instead?
Expected behavior is that the sensor list is always constant.
The problem is that the sensor list is static and is added to, rather than 
built each time the app starts. Should be a simple fix.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by [email protected] on 22 May 2014 at 11:32

It may be helpful to persist the rate change setting (i.e. Fastest, Game, UI, 
Normal) between activities as one browses the various settings.

Currently you need to change it from the default (Normal) each time.
No need to persist into the file system however. Just between screens as 
browsing. Once the session is over it can go back to default when they start 
the application again.

Original issue reported on code.google.com by [email protected] on 18 May 2014 at 11:27

What steps will reproduce the problem?
1. When you start a sensor view it immediately begins logging output
about the sensor data to the logcat. For some sensors this can be quite a bit 
of data. If the data is not needed this could be eliminated. Perhaps with a 
button option.

Original issue reported on code.google.com by [email protected] on 26 Jul 2014 at 11:52

The SIGNIFICANT_MOTION sensor does not work.
I downloaded the source from code.google.com & took a look. The problem appears to be caused by incorrect registering for TriggerEvents. (Google "android Trigger events" for more info).
I patched the source and AFAICT, everything is now working - at least for the sensors on my ancient GS4.

Kevin's input: there is a new API requestTriggerSensor added at API level 18. Interesting, and the documentation now says "Note: Don't use this mechanism with a Trigger Sensor, have a look at TriggerEventListener. TYPE_SIGNIFICANT_MOTION is an example of a trigger sensor." which I should update the code to handle.
mysensor_diff.zip

Since screen rotation is locked so that sensor values can be observed more 
easily while using them, it would be helpful to be able to toggle the screen 
orientation and also remember the selected orientation when returning to that 
sensor.

Original issue reported on code.google.com by [email protected] on 3 Jul 2014 at 2:21

Looks like Android has new sensor types available. Should add in support for 
those and also a better way of handling the sensor types (defining them) in the 
code.

Original issue reported on code.google.com by [email protected] on 23 May 2014 at 9:50

Problem in Sensor

Posted by an app user:

"minor observation:
the App screen pops under the main Adroid buttons. It took me a while to figure out that the app actually scrolls up and down.
It does not do this for all the sensors only the ones that have a lot of values to show, again a hint in the "About" may be helpful for some users."

What steps will reproduce the problem?
1. Launch MySensors
2. Select any sensor and monitor
3. Go to home and load a few other applications (Maps, Contacts, etc.)
It may take some time for the main application to get 'destroyed' by Android
4. Later, return to MySensors, the application will crash

What is the expected output? What do you see instead?
The application should resume sensor monitoring, it crashes instead

Please use labels and text to provide additional information.

Original issue reported on code.google.com by [email protected] on 20 Jul 2014 at 5:31

---------- Forwarded message ----------
From: Kevin Fodor <[email protected]>
Date: Fri, Jun 1, 2012 at 8:24 AM
Subject: Re: My Sensors
To: Michael Madsen <[email protected]>

Hi Michael,

I think that could be possible. I'll definitely look into it. Not sure when I 
am going to post another update, but if I can figure it out I will be glad to 
add it.

As a temporary work around you do have the option to go into 
Settings->Display->Screen timeout and select "never".
Kind of a trouble I know, and you'll need to remember to set it back as well, 
but might help you in the mean time.

-Kevin

On Thu, May 31, 2012 at 1:34 PM, Michael Madsen <[email protected]> wrote:
Hi, could you add an option to prevent the screen from timing out?

Regards,
Michael


-- 
Kevin Fodor

Original issue reported on code.google.com by [email protected] on 1 Jun 2012 at 1:37

Hi Kevin,

Thank you for the great app! I have a feature request: would it be possible to make it log sensor output data to the SD card, such as in a csv format?

Shawn

What steps will reproduce the problem?
Viewing a sensor's real-time data. It appears the time stamps do not update as 
expected.

What is the expected output? What do you see instead?
Time stamps should be shown in seconds and increase.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by [email protected] on 22 May 2014 at 11:33

This is from an app user who had a suggestion:

"Another recommendation, if you are still interested in improving on what you have already, would be to allow selecting multiple sensors for recording and possibly adding the GPS to the list of record-able items.
To do this add a checkbox next to each sensor on the homepage.
The user could go into each sensor and change its settings as one can now and underneath the bottom of the homepage is a button [Log all checked Sensors]
While logging you just create an additional outer loop that goes through all sensors and adds the value from the checked ones to the file.
I see that this becomes tricky when some sensors update very fast and others only rarely.

Then one could strap the phone to something that moves and get two independent acceleration measurements, multiple rotation and heading readings and if needed the changing illumination.

Think model train or race car movements. Roller-coaster ride and road-trips not only with geo-location but multiple, parallel, time-stamped exact sensor data. one could integrate accelerations to get velocities and integrate those to get relative location.

There are already multiple GPS track recorders that one could let run in parallel and hopefully it will be possible to align the time stamps, so recording GPS would be for me the lower priority."