I installed the accelerometer sample app from the android SDK 2.3 om the device (Nexus s). I get several balls falling towards one side of the screen and nothing changes their position.
Is there any place in which the expected behavior of this application is described?
Does anyone here knows the expected behavior?
I suspects it exposed a problem with the hardware operation.
Thanks,
Yoav
Just ran it on a Nexus One... you hold the phone flat w.r.t. the ground. Tilting it slightly will cause the balls to fall towards the downmost edge of the screen, i.e. as if they were under the influence of real gravity.
Related
Hello and thanks in advance for the help.
I am working on an app which provides range bearing to a particular spot based on GPS and compass.
From time to time (every week or so) I have noticed that the compass orientation freezes. I have installed a different compass app and, it doesn't freeze, but it is clearly giving a very wrong reading (for example, north indicated directly to the sun).
Similarly, Google Maps is showing the wrong reading. I am sure the bearing are wrong because if the sun was in the north we'd be really screwed :). Plus I have another compass on my watch, and it is OK, so I know where north really is.
I suspect the reason my app is frozen, and the other app is not frozen, is just because of the different animation approaches. The root cause appears to be that the sensor is "jammed" even though it is in a solid state.
I have tried recalibrating (maybe 40 times), shutting off the phone, resetting the phone, clear the app's memory, stopping the app, etc..
What I noticed today is that if I place my phone on its magnetic mount, all of a sudden the compass started working again once I remove it from the mount. So, to be clear, I am out in the woods many kilometers away from my magnetic mount when it is jammed but when I return to my car and put it on/remove it from the mount everything works fine again for a few days.
I have never had an electronic compass behave like this. Unfortunately google searches invariably point me to suggestions to recalibrate.
If it matters, the phone is a OnePlus 6T with Android 11, Oxygen OS 11.1.1.1
Thanks
We are having issues with one of our two tango devices.
With one device it's really easy to create adf files and re localize. With the other it's very hard (same room, and scanning area).
Furthermore we are developing a multiplayer game by sharing the adf file. And the device who connects to the first one always has a offset in the y-axis.
Another experiment showed a quite strange behavior:
We placed the two devices in the docking stations right next to each other, closed all apps and rebooted both devices. Then we opened the explorer app on both devices and displayed the point cloud. Oddly enough the horizon line one device is much higher than on the other. Is this normal or is on of our devices miss-calibrated/broken.
Here are the two screenshots:
Even if these two tablets are physically at the same height level. They haven't the same Z because their initialization at 0 happens at the start of the service. You can check this with full diagnostic menu entry.
I've an android TV box (jellybean) to which I have connected a 17'' eGalaxy touchscreen. It moves the pointer but only with in a small are. I've created the necessary idc file but don't know the right configuration to put in it.
You probably just need to run a touch screen calibration app.
Regards
Rasmus
I have no actual Galaxy Note on-hand and no access to such device so
I would like to ask if the S-Pen behaves the same way as a Finger on a SurfaceView?
Basing from the behavior of S-Pen SDK samples when run on an emulator, it seems that the S-Pen's input is the same with finger inputs only that it is very precise. (noticing that when run on the emulator, its impossible to detect if input came from a finger or S-Pen since touch input is emulated via the mouse cursor)
I'd like to confirm if the gestures I can do with my finger is also doable using the S-Pen?
If this is the case, is it safe to say that the S-Pen is comparable to a very thin finger?
The only difference it can make, is that when an app is coded with specific functionality using the SDK that samsung provides?
Thanks
As it will be easier for everyone to spot an answer and not a comment, here's an explanation from samsung developers themselves:
S Pen behavior on SurfaceView - http://developer.samsung.com/
Yes, using the international Samsung Note (still waiting on ICS). But your question would be better served by one of the xda developers forums.
Using the S Memo app to add a memo, selecting the pen input option, I can write a note using my finger. The stroke is thin, as it would be for a pen...
I can use the pen to interact with anything on the screen, as if it were my finger. But the pen can not interact with the capacitative buttons, nevermind the physical ones.
The s pen works with the Wacom digitizer in the Note devices. This allows for precision, pressure sensitivity (256 levels on my Note II), and hover events. These are pointer events, not touch or mouse/click events at the OS level.
Hello :) I am working on an application that uses the compass and location to draw an arrow at the direction of a location. My problem is when I run my code on the emulator, all the arrows point the correct directions, and when I change the orientation of the emulator to landscape, all the arrows are still correct. But when I run the same application on my Nexus One, the arrows are all correct when the phone is vertical, but when it turns to landscape all of the arrow are off by 90 degrees. It keeps the "top" of the phone as the reference to North. Thus you must correct the compass for the orientation of the phone. Does this happen on all real phones and the emulator is the different one? Or is this just the Nexus One? Thanks :)
From my understanding the current way the compass works it is supposed to always use the "top" of the phone or "default orientation" for the correct reading. This could have been different on earlier versions of android. It is said it is then up to developers to compensate for the screen orientation to represent the true north with orientation changes. Same goes for the accelerometer the axis stay based off of default screen orientation (so for most phones portrait, but tablets most would be landscape).
I hate to refer you to the sdk but this link first paragraph explains:
http://developer.android.com/reference/android/hardware/SensorEvent.html