Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781
[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4362: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4364: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4365: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4366: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
anddev.org • View topic - CPU spikes when implementing accelerometer

CPU spikes when implementing accelerometer

Put problem concerning MapActivities, MapViews, Overlays and GPS in this forum.

CPU spikes when implementing accelerometer

Postby sebrock » Wed Dec 02, 2009 5:43 pm

I have a MapActivity which implements a SensorEventListener. However if I register a listener for a Sensor.TYPE_ACCELEROMER the CPU spikes and makes it unusable. If I instead register a listener for Sensor.TYPE_ORIENTATION all is well.

So it seems it's just the accelerometer that makes the CPU spike (maybe in combination with the mapactivity).

Any ideas?
sebrock
Freshman
Freshman
 
Posts: 2
Joined: Fri Nov 13, 2009 11:51 am

Top

Return to Map Problems

Who is online

Users browsing this forum: No registered users and 2 guests