Accelerometers are not working

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Download the demo game from the following URL:
http://code.google.com/p/apps-for-android/source/browse/trunk/Amazed/bin/Amazed.
apk
2. Install it onto the FR
3. Run it

What is the expected output? What do you see instead?
Tilting FR should affect rolling of the ball, but nothing happens.

What version of the product are you using? On what operating system?
android-on-freerunner-cupcake-0.1.1.tar.gz

Please provide any additional information below.
adb logcat shows a lot of messages like following:
D/sensors ( 1286): Wake up by the control system

Original issue reported on code.google.com by skliarie@gmail.com on 14 Oct 2009 at 6:09

GoogleCodeExporter commented 9 years ago

Maybe try a daily built there is a lot of work around accelerometer.

Original comment by michaelt...@gmail.com on 15 Oct 2009 at 9:41

GoogleCodeExporter commented 9 years ago

Original comment by michaelt...@gmail.com on 19 Oct 2009 at 9:07

Changed state: FeedbackPending

GoogleCodeExporter commented 9 years ago

I'm still seeing this issue in the Week-43 build (accelerometers don't work in 
Amazed).

Screen orientation auto-adjust does work though.

Original comment by montg...@gmail.com on 20 Oct 2009 at 3:54

GoogleCodeExporter commented 9 years ago

Well, can be a problem of Amazed? Can you send a logcat?

Original comment by michaelt...@gmail.com on 22 Oct 2009 at 10:18

GoogleCodeExporter commented 9 years ago

It doesn't work with daily 20091023. Here is the adb logcat :

I/ActivityManager(  850): Starting activity: Intent {
action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER}
flags=0x10200000 comp={com.example.amazed/com.example.amazed.AmazedActivity} }
D/sensors (  850): Control set delay 20 ms is not supported and fix to 400
D/sensors (  850): Control set delay 20 ms is not supported and fix to 400
W/IInputConnectionWrapper(  912): showStatusIcon on inactive InputConnection
W/ActivityManager(  850): Launch timeout has expired, giving up wake lock!
W/ActivityManager(  850): Activity idle timeout for HistoryRecord{437064d0
{com.example.amazed/com.example.amazed.AmazedActivity}}
D/dalvikvm(  912): GC freed 118 objects / 5512 bytes in 686ms
I/ActivityManager(  850): Displayed activity 
com.example.amazed/.AmazedActivity: 25175 ms

Original comment by kewlcat...@gmail.com on 22 Oct 2009 at 11:02

GoogleCodeExporter commented 9 years ago

Same goes for Labyrinth Lite :

I/ActivityManager(  850): Start proc se.illusionlabs.labyrinth.lite for activity
se.illusionlabs.labyrinth.lite/.StartUpActivity: pid=1093 uid=10016 gids={3003}
D/SensorManager( 1093): found sensor: Openmoko GTA02 3-axis Accelerometer TOP, 
handle=0
D/dalvikvm( 1093): GC freed 1155 objects / 79600 bytes in 211ms
D/        ( 1093): unable to unlink
'/data/data/se.illusionlabs.labyrinth.lite/shared_prefs/LabyrinthSettings.xml.ba
k':
No such file or directory (errno=2)
I/ActivityManager(  850): Displayed activity
se.illusionlabs.labyrinth.lite/.StartUpActivity: 3286 ms
I/InetAddress( 1093): Unknown host labyrinth.codify.se, throwing 
UnknownHostException
D/dalvikvm(  998): GC freed 165 objects / 26152 bytes in 92ms
I/ActivityManager(  850): Starting activity: Intent {
comp={se.illusionlabs.labyrinth.lite/labyrinth.screen.level.LevelScreenActivity}
 }
I/ActivityManager(  850): Displayed activity
se.illusionlabs.labyrinth.lite/labyrinth.screen.level.LevelScreenActivity: 570 
ms
D/        ( 1093): unable to unlink
'/data/data/se.illusionlabs.labyrinth.lite/shared_prefs/LabyrinthLevelpacks.xml.
bak':
No such file or directory (errno=2)
D/dalvikvm( 1048): GC freed 1595 objects / 99208 bytes in 107ms
I/System.out( 1093): /data/data/se.illusionlabs.labyrinth.lite/files/Demo.zip
I/ActivityManager(  850): Starting activity: Intent {
comp={se.illusionlabs.labyrinth.lite/labyrinth.game.GameActivity} }
D/dalvikvm( 1093): GC freed 2359 objects / 199928 bytes in 107ms
D/sensors (  850): Control set delay 20 ms is not supported and fix to 400
D/sensors (  850): Open sensor 86
D/sensors ( 1093): Open sensor
E/sensors ( 1093): write_int failed to open
/sys/bus/spi/drivers/lis302dl/spi3.1/threshold
I/global  ( 1093): Default buffer size used in BufferedReader constructor. It 
would
be better to be explicit if an 8k-char buffer is required.
D/dalvikvm( 1093): GC freed 1515 objects / 183528 bytes in 106ms

Original comment by kewlcat...@gmail.com on 22 Oct 2009 at 11:05

GoogleCodeExporter commented 9 years ago

Ok, it can't write on the threshold file. It this file have the correct rights?
Michael

Original comment by michaelt...@gmail.com on 26 Oct 2009 at 8:07

GoogleCodeExporter commented 9 years ago

This file was 644 (rw-r--r--). I've just changed to rw-rw-rw- the permissions 
on it
but the result is an endless stream of messages :
D/sensors ( 1677): Wake up by the control system
D/sensors ( 1677): Wake up by the control system
D/sensors ( 1677): Wake up by the control system
D/sensors ( 1677): Wake up by the control system
D/sensors ( 1677): Wake up by the control system
D/sensors ( 1677): Wake up by the control system
D/sensors ( 1677): Wake up by the control system
D/sensors ( 1677): Wake up by the control system
D/sensors ( 1677): Wake up by the control system
...

Original comment by kewlcat...@gmail.com on 26 Oct 2009 at 8:55

GoogleCodeExporter commented 9 years ago

same D/Sensors  Wake up by control system here, but I didn't mod any folder 
rights, I
using the 0.1.1 release in Sept, should I switch to daily or weekly build?

Original comment by nengyu...@gmail.com on 29 Oct 2009 at 3:16

GoogleCodeExporter commented 9 years ago

Change to a new one and apply this change

Original comment by michaelt...@gmail.com on 3 Nov 2009 at 8:28

GoogleCodeExporter commented 9 years ago

Using daily 20091105 :

 -- Before
I/ActivityManager(  862): Starting activity: Intent {
action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER}
flags=0x10200000 comp={com.example.amazed/com.example.amazed.AmazedActivity} }
I/ActivityManager(  862): Start proc com.example.amazed for activity
com.example.amazed/.AmazedActivity: pid=1370 uid=10019 gids={}
D/SensorManager( 1370): found sensor: Openmoko GTA02 3-axis Accelerometer TOP, 
handle=0
D/sensors (  862): Activate sensor
D/sensors (  862): Control set delay 20 ms is not supported and fix to 400
D/sensors (  862): Open sensor 81
D/sensors ( 1370): Open sensor
E/sensors ( 1370): write_int failed to open
/sys/bus/spi/drivers/lis302dl/spi3.1/threshold
D/sensors (  862): Control set delay 20 ms is not supported and fix to 400
W/IInputConnectionWrapper(  958): showStatusIcon on inactive InputConnection
I/ActivityManager(  862): Displayed activity 
com.example.amazed/.AmazedActivity: 1309 ms
W/ActivityManager(  862): Launch timeout has expired, giving up wake lock!
W/ActivityManager(  862): Activity idle timeout for HistoryRecord{4361fde0
{com.example.amazed/com.example.amazed.AmazedActivity}}

 -- After
I/ActivityManager(  862): Starting activity: Intent {
action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER}
flags=0x10200000 comp={com.example.amazed/com.example.amazed.AmazedActivity} }
D/sensors (  862): Control set delay 20 ms is not supported and fix to 400
D/sensors (  862): Control set delay 20 ms is not supported and fix to 400
I/ActivityManager(  862): Displayed activity 
com.example.amazed/.AmazedActivity: 552 ms
W/IInputConnectionWrapper(  958): showStatusIcon on inactive InputConnection
W/ActivityManager(  862): Launch timeout has expired, giving up wake lock!
W/ActivityManager(  862): Activity idle timeout for HistoryRecord{4360bac0
{com.example.amazed/com.example.amazed.AmazedActivity}}

That is, before and after I change the rights to the "threshold" file to 666 
instead
of 644.

Original comment by kewlcat...@gmail.com on 4 Nov 2009 at 11:21

GoogleCodeExporter commented 9 years ago

I confirm on build 45 when "Orientation" on configure screen menus is checked 
screen
goes portrait and landscape upon position change. So accelerometers should be 
working.

Original comment by gism...@gmail.com on 10 Nov 2009 at 12:36

GoogleCodeExporter commented 9 years ago

Applications using the accelerometers to change the orientation are doing fine. 
The
problem is when applications try to use the accelerometers for something else 
(here,
a game, for instance...)
Amazed does NOT work the way it is supposed to with weekly build 45.

Original comment by kewlcat...@gmail.com on 10 Nov 2009 at 12:57

GoogleCodeExporter commented 9 years ago

Issue 111 has been merged into this issue.

Original comment by hmu...@gmail.com on 7 Feb 2010 at 8:50

GoogleCodeExporter commented 9 years ago

application compass doesn't work :( the logcat said "D/sensors ( 4077): Wake up 
by 
the control system" ...

I/Compass ( 4077): Registering Sensor Event Listener for ShakeSensor
D/sensors (  875): Activate sensor
D/sensors (  875): Control set delay 60 ms is not supported and fix to 400
D/sensors (  875): Open sensor 127
D/sensors ( 4077): Open sensor
D/sensors ( 4077): Wake up by the control system
D/sensors ( 4077): Wake up by the control system
D/sensors ( 4077): Wake up by the control system
D/sensors ( 4077): Wake up by the control system
D/sensors ( 4077): Wake up by the control system
....

Original comment by rooszpe...@gmail.com on 31 Mar 2010 at 9:14

GoogleCodeExporter commented 9 years ago

The problem still exists on 0.2.0-RC1. Here is the relevant logcat when running 
Amazed:

D/SensorManager( 1821): found sensor: Openmoko GTA02 3-axis Accelerometer TOP, 
handle=0
D/sensors (  867): Activate sensor
D/sensors (  867): Control set delay 20 ms is not supported and fix to 400
D/sensors (  867): Open sensor 123
D/sensors ( 1821): Open sensor
E/sensors ( 1821): write_int failed to open
/sys/bus/spi/drivers/lis302dl/spi3.1/threshold
D/sensors (  867): Control set delay 20 ms is not supported and fix to 400

Original comment by skliarie@gmail.com on 8 Apr 2010 at 2:23

GoogleCodeExporter commented 9 years ago

Does this problem still exist for master?

Original comment by seder...@googlemail.com on 19 Apr 2010 at 9:42

GoogleCodeExporter commented 9 years ago

Tried the latest daily build available 
(android-on-freerunner-cupcake-daily-20100528.tar.bz2) but the problem still 
persists.

Any news about that?
Are there any alternative to gather the sensor data?

Original comment by josean1...@gmail.com on 23 Jul 2010 at 7:02

GoogleCodeExporter commented 9 years ago

Tested again latest currently available daily build (20100805):

Still the same problem with accelerometers.

Original comment by josean1...@gmail.com on 11 Aug 2010 at 11:14

jancona / android-on-freerunner

Accelerometers are not working #43