IssueTracker

Here's a code snippet that readily demonstrates the problem.  Note that on some
devices, while plugged in they continue to work in standby, so untethering the device
may be necessary.


package test.com;

import android.app.Activity;
import android.app.Service;
import android.content.Context;
import android.content.Intent;
import android.hardware.Sensor;
import android.hardware.SensorEvent;
import android.hardware.SensorEventListener;
import android.hardware.SensorManager;
import android.media.MediaPlayer;
import android.os.Bundle;
import android.os.IBinder;

public class acceltest extends Activity
{
        static Context ctxt = null;
        Intent svcIntent = null;
       
    /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState)
    {
        ctxt = this;
       
        super.onCreate(savedInstanceState);
        setContentView(R.layout.main);
       
        svcIntent = new Intent (this, MovementListener.class);
        startService (svcIntent);
    }
   
    static public class MovementListener extends Service implements
SensorEventListener
    {
        MediaPlayer a = null;
       
                @Override
                public void onCreate()
                {
                        SensorManager sm = (SensorManager)getSystemService
(SENSOR_SERVICE);
                       
                        sm.registerListener (this, sm.getDefaultSensor
(Sensor.TYPE_ACCELEROMETER), SensorManager.SENSOR_DELAY_NORMAL);
                        super.onCreate();
                }

                @Override
                public void onAccuracyChanged(Sensor arg0, int arg1) {
                        // TODO Auto-generated method stub
                       
                }

                @Override
                public void onDestroy()
                {
                        SensorManager sm = (SensorManager)getSystemService
(SENSOR_SERVICE);
                        sm.unregisterListener(this);
                       
                        if (a != null)  a.release();
                       
                        super.onDestroy();
                }

                @Override
                public void onSensorChanged(SensorEvent event)
                {
                        if (a != null)  a.release();
                       
                        a = MediaPlayer.create (ctxt, R.raw.triangle);
                        a.seekTo(a.getDuration()/3);
                        a.start();
                }

                @Override
                public IBinder onBind(Intent arg0)
                {
                        // TODO Auto-generated method stub
                        return null;
                }
    }
}

Android Developers group thread started to discuss this issue...

http://groups.google.com/group/android-developers/browse_frm/thread/9787faee6f36a4fe

After discussion in the above mentioned thread, I think there are two potential
issues here:

1. If we're to assume the correct way forward is to use a wakelock, on the HTC Hero a
partial wakelock does not seem to wake the device enough to get the
OnSensorChanged()'s through.  On G1 and Magic, it does.  This is a big problem to
apps like mine (and others in the thread).

2. It seems (in contrast) GPS location changes do get through without a wakelock. Is
this because we have to set parameters for how often/far and therefore it is a less
frequent event to wake the device for?  If so, could the Sensor API do similar, ie
have a register parameter for how much movement before a series of OnSensorChanged()
are called and the device woken to accept them?  It seems to me that this would be
the optimal solution to give the best potential battery performance under the
circumstances where sensor messages are required at all times (ie. where the device
is expected to be motionless most of the time, only waking if moved).  As the Sensor
messages HAVE got through in standby previously for all current devices, could we
have this functionality as a compromise?

I notice this has not been assigned an owner -  I wonder if someone can comment on when
this will be fixed?  Thank you.

This issue does really annoy users of Smart Alarm Clock or similar applications.
It also reported to be seen on Droid.

Well, I'm starting to advertise this issue in this applcation (currently 5000
installations from market). So, if 10% percents will vote a star, it will gain
significant momentum to be fixed soon.

I hope so =)

Just for search results:
- accelerometer stops the data if screen goes off
- g-sensor not working while display is off
- cpu wake lock doesn't enable accelerometer on Hero or Droid
- partial wakelock (wake lock) not helps

This is a urgent issue for always-sensing based applications.

I could not understand why they removed this function.
If it was for energy consumption problem, they could provide other option, for
example, SENSOR_LOCK, but they just remove it !

Google wants to have always-sensing applications all to themselves ?
How do you think ? Why Google eliminates this function ?

Oh, I don't think that it was intentional.
This is just a bug, not a feature. Who does really need a navigation software while
screen is off?

Ask your users to vote for this bug!

My website collects hardware tests from the application:
- From 9 Hero200 devices 2 are working great, and 3 works a little ('Game' frequency
is 3 Hz instead of 20 while screen is on)
- None of 20 HTC Hero works at all - accelerometer doesn't work while screen is off.
- Only 4 of 29 HTC Eris works.
- Samsung SPH-M900 records are unstable, 50/50.

Other devices work great.
Please let me know if you need access to these anonymous statistics (including
complete hardware information).

Motorola Droid is working, at least I got one tester with positive feedback (no
reports about broken Droid support, so no comments about this).

My devices are HTC Hero, so I thought that this was not a bug, it's my mistake.
(Google, I sincerely apologize.)

I borrowed android phones from other teams, and tested follow devices.

2 HTC G1(SDK 1.6) work great.
2 Motorola Cliq(SDK 1.5) work great.
3 HTC Hero does not work.

I really like HTC Hero because of its UI and design.
But..... I think I will dislike Hero.
Please fix it !

This issue also affects the application ShakeIt (http://www.androlib.com/android.application.com-androood-
shakeitdonate-xAmj.aspx), which enables speakerphone when you flip the phone upside down. As soon as the
screen turns off (10 seconds or so), the speakerphone is disabled (even if the call is still in progress).

[Comment deleted]

I think maybe we should try HTC's customer support,
maybe they done this by purpose,

here is the report url
http://www.htc.com/www/CS_Mail.aspx

Worked on my Droid fine for about a week until the new OS download now it doesn't
work. This was my favorite Alarm clock cause it really worked. Google please fix the
problem.

I'm working on an app that crucially relies on accelerometer readings during standby,
so this issue is a big problem for me too. Hope to have it resolved soon!

Looks like I have the same problem with my Motorola Milestone. It can only track
movements while the screen is on. But as soon as the screen turns off: nothing.

[Comment deleted]

stefan.van.essen,

Are you sure this issue has been fixed in Eclair? How do you know it is going to be
fixed when Eclair is released?

I would also be very keen to know whether this issue is officially a bug. If not, I
will have to terminate my current development project.

The milestone ships with eclair, and for me it is not working - so I assume it is not
fixed in Eclair.

Not working here either, I need it as well for some logging tool.

Please fix, or at least give some info if this is being worked on.

There's something I still don't understand. If this is an Android issue, why do some Android phones do not show
this problem? According to the Smart Alarm Clock website, T-Mobile G1, Motorola Milestone and Samsung
Galaxy work fine (although paul.dubs reports the opposite for the Milestone). Shouldn't all Android phones be
affected?

Just confirmed it too!
Please fix asap.

Please fix it...

anybody know if it works on a htc tatoo?

Would be great if this can be fixed so that applications like smart alarm clock will work on HTC hero

yea someone please try to fix this! man awesome apps depends on this function!

Please fix this for the htc hero!!

Please fix this for the htc hero!!
I can not use some apps.....

Same problem on verizons motorolia droid.

This bug really needs a fix!

This app worked perfectly on my droid for about a week. Google please fix this problem.

fix it plz.

Htc hero user

Please fix this. Looks like a lot of users need this me included thank you

AAAA!!!

Automatic data collection from Smart Alam Clock shows that Nexus One is also have a
bug!

GOOGLE!! Your OWN phone violates your own specifications!

device: passion
model: Nexus One
firmware: Android 2.1
board: mahimahi
build: ERD79
product: passion
version: ERD79
incremental: 22607
reported 5 times as not working

build: passion-userdebug 36903751.1 ERD72 22132 test-keys, incemental 22132, 21364
reported 5 times as not working

build: ERD78, incremental 22525 - WORKS OKAY!!!! Accelerometer works at 9 Hz while
the screen is off.

Guys, you have a working bugfix! Please find the difference and fix other build.
I hope you could.

*

Needs fix.

I just published an application that uses the orientation sensor and this also does
not work in standby mode (no sensor updates) on my Motorola Milestone. It would be
great if this could be solved.

Will turning screening app help this

Will turning screening app help this

Will screening app help

G1 version 1.6 (donut).  Same issue using CardioTrainer market application from WorkSmart Labs.  
Thanks

 

After some investigation to get my app to work, I found out a workaround that seems
to work and that would not require any changes even if this issue is fixed. In the
spirit of helping other fellow developers, I am posting it here (you may thank me in
your release notes ;) ). I do not have the code here with me right now so I will
simply describe the process. The code itself is trivial anyway:

1 - Create a BroadcastReceiver for the ACTION_SCREEN_OFF intent. You will want to
create it programatically in your service as you only want to intercept it if your
service is running. *DO NOT CREATE IT USING XML*.

2 - Implement the onReceive() method for this broadcast receiver as something like
this:

public void onReceive(Context context, Intent intent) {
  // mSensorManager is a reference to the system's SensorManager.
  mSensorManager.unregisterListener(YourServiceClass.this);
  // mSensor is the sensor you want to monitor.
  mSensorManager.registerListener(YourServiceClass.this, mSensor,
SensorManager.SENSOR_DELAY_NORMAL);
}

3 - Don't forget to use registerReceiver() to register your receiver (you can do that
on your service's onCreate method()) and to use unregisterReceiver() to unregister it
when your service is being turned off (do it in onDestroy()).

That is it. You do not have to change anything else in your code (probably). The only
side effect of this is that when you go from normal to standby mode, there can be a
small delay (up to 500 milliseconds in my measures) where onSensorChanged() will not
be called.

Please, always make it clear to the user that running in standby mode will drain more
battery. In my specific app (Silencer, available in the Android Market) I require the
user to explicitly enable standby support and I mention on the relevant settings that
this will drain more battery.

Hope this helps.

I know this might've been stated elsewhere, but in case of Smart Alarm Clock app
can't you just set screen time out to 'never'? Seemed to work for me. You will be
having your phone in charger when you are using the said app anyway.

Just a thought.

my code is already registering the listener in the SCREEN_OFF event (my program uses
sensors only with screen off), but still fails on some devices.
Only real difference from your sample is that I don't call unregister because sensors
are not in use.

[Comment deleted]

Bruno, thanks a lot!
I really hope re-registering listener after screen off will help at least for some phones.

I will use this hack in next version of Smart Alarm Clock and will write the resulting stats here.
Bruno, you made my day :-)  

So far, I was able to test the code I described above in the following devices:

Google Nexus One
Motorola Milestone
HTC Dream
HTC Magic
HTC Hero

In all of those, the code worked. Note that, in my case, my program already
registered a listener for the orientation sensor and I simply added the code I
described (that's why I unregistered the listener in onReceive().

As this is kinda of a hack (either this issue we are discussing here is a bug or it
is an intended feature and the fact that my example code worked is a bug), I can not
make guarantees about it generally working, but it *IS* working for me.

This issue is seriously impacting one of my apps as well. The app works perfectly on
the G1 (and I haven't received any issue reports from anyone else), but on my new
Nexus, the onSensorChanged listener stops being called when the screen turns off,
despite my holding a PARTIAL_WAKE_LOCK.

Unfortunately, I tried Bruno's workaround but thus far have not been able to get it to
work. :-(  Please, PLEASE fix this ASAP.  

I really any this bug fix

Pls do help

would it be possible if you post a blogpost about this bruno? Or an elaborate
explanation?

Your wish is my command. ;)

https://sites.google.com/a/bug-br.org.br/android/technical-documents/sensors-and-
standby-mode

Hope this helps.

Another Samsung Moment not working with the screen off. Hopefully this will help.

Owner of HTC hero would lov3 to have a fix. Thanks

Owner of HTC hero would lov3 to have a fix. Thanks

thx a lot bruno, will try it soon

FYI: After working with Bruno a bit and discovering that the fix does not seem to work
on HTC Hero or Tattoo, I have now posted a call for help in the Android Developers
forum -- http://groups.google.com/group/android-
developers/browse_thread/thread/67d1345090dd8b41?hl=en#

Please feel free to also join the discussion, or continue it here.

Can someone confirm that Bruno's fix works for Droid 2.01?

ohhh, pleeeease fix this problem.

Definitely need this fix for the droid eris.

Please fix this for the htc hero!!

I would also very much like a fix for the HTC Hero, please google/htc :(

I tried the App on my G1.
I did not recognize my movements, but alarm started at the fixed time.

Three times I had "force coloses".

I think things have to be done.
Thanks!

[Comment deleted]

I can't use Smart Alarm Clock aplication on Hero because of this bug:( Please fix
asop.

I'm having trouble getting the Smart Alarm Clock application to work as intended on
my Nexus One because of this problem.  A fix would be greatly appreciated :)  Thank you!

Can we all please stop crying "please fix this!" because it is really getting
annoying to get all these mails. I got some people to star this problem but they
already unstarred because of the mail flood they got. I am on the verge of unstarring
too, thus further sinking this problem towards the bottom of the problem pool. Thanks
in advance.

Please fix this "asap" for the HTC Hero!

This bug really needs a fix!

I belive that if you install a app like KeepScreen (block screen timeout), you can
choose to keep Smart alarm clock to not shut down screensaver and can then use this
app.

"block screen timeout" is "screen dim lock" which means screen never turn out.
This way is alternative thing, but it will consume battery a lot.
Using accelerometer with "screen off" is essential for efficient usage.

Temporary solution for Nexus One (and maybe others) is to use Screen Mode or Screen On
from Market and then dim the screen in Clock app running.

Please fix this "asaFp" for the HTC Hero!

Please fix this. I would love to have a sleep cycle detecting app for my phone so I
can make the most out of the time I have to sleep. It just isn't possible unless this
bug is fixed!! (Moto Droid)

This bug also encountered on HTC Eris.

Good news, everybody!

I'm attending Android Labs event in Zurich and developers say they have a bugfix and
are going to push it in the next OTA update, at least for Nexus One. That's really
great!

Why didn't anyone take assignment of the issue and provide a status update if it indeed
was being worked on.  Maybe it would help limit the flood of "OMG PlZ FIx!!!! IT no
WERKS!!!"

I talked to one of the Google Android Developers at the Android Developer Labs, and
it turns out there is still internal debate about this issue as it relates to battery
power. The argument seems to largely revolve around "protecting users". On the other
hand, I strongly believe the argument is strongly in favor of allowing the
accelerometer to be on and then letting the users decide with feedback/download
counts. This is the same idea is Google followed with background apps, etc. -- this
severely limits our ability to develop such useful apps as pedometers, various other
motion based games and apps. If someone has the time, please put together a more
organized list of reasons, and I can try to get it into the right hands.

@80

Protecting users against what a flat battery?
I dont understand why they cant just put it in settings "Enabled Accelerometer while
screen is off".

I need this feature because I want a sleep cycle alarm clock to wake me up because I
have serious sleeping pattern issues.

#80

oh, well,
maybe they should just say

"because we don't use this feature when my screen off,
so we decide to disable this feature when screen off, in core."

what a open develop environment,
just another step toward apple store, and google do their way in system core lol

@andcycle, @p.artem,

I just want to repeat: Reto Meier, Android developer advocate from Google
(google.com/profiles/reto.meier) kindly answered my quetion about this bug during
Android Developers lab in Zurich.

I was really surprised that he knows a lot about this bug (said it really affects
pedometers because that even can't keep phones on charger as a workaround) and he
knows that there's a software workaround for Motorola phoned.

So, he confirmed that after internal discussions they agreed that this is a software
bug: "If you hold CPU lock, that's over - you definetely should have access to all
the senors. So, it's a question of build process and time - where it will be pushed
to updates."
That's what I was said.


PS. Many thanks to Google - they presented free Nexus One to every visitor of that
meeting! That was really kind and great idea =)

@a.kosenkov, @all_google_android_developer,

I apologize for my rude reply,
and I can accept that if fix this problem now would stall the entire build process,

but if here, a issue tracking system,
issue just hanging there without any response on it,
we just think you guys ignore all the users,
at least there should be a official response like
"we will investigate this problem soon."
"we have located the issue, but it would take a long time for fixing it, please be
patient."
any progress report will let people know you guys are working on it, not ignoring us.

and by the way, there is no free Nexus One for every visitor in my little island,
that's a treat lol

@a.kosenkov
Thanks for the information. I had spoken to Roman at the New York ADL event, and he
checked the internal db then. I am guessing the internal issue-tracking system is also
out of date on this issue. It's very good to hear that the debate went this way, and
not the other way around. It is really surprising nobody has chimed in officially here.

Another HTC Hero user here, please fix this guys i would love to use the smart alarm
clock, you guys are really losing out on the iphone because of this.

My Eris no longer records steps with screen locked in cardiorainer app. Worked fine before last.update.
Please fix this bug asap.

Please fix this bug. I do need this function.
thanks

Yeah, now we know that people like to see this bug fixed. Quit replying if you don't
have anything to say. :(

My apologies bothering everyone in this thread with another meaningless reply.

How long & how many votes before you guys finally fix this stuff? l would think that by now it would
have been done so that this wouldn't still be happening. Do you guys even care?

Chocokitt: I agree with you, it's dissapointing, we can only wait, it's also
unprofessional to not say when this update will come, I have a IT-development firm and
it's standard procedure to have a launch date on updates + roadmap with time.

Pls fix this bug, there are a lot of apps can't response normally without it...

[Comment deleted]

Please, stop spaming to this thread!!!

I've subscribed to this issue in order to obtain relevant information and not to
listening your cries like: "Please, fix this bug. I want this bug to be fixed
very-very much.". It really annoys.

The problem lies in the use of the word "thread". Bug trackers are not forums, please don't treat them like so.

Please fix this for the HTC Hero! Thank you!

PLEASE FIX, i have HTC Hero and love CardioTrainer and now does not allow pedometer
to work when screen is not on. I contacted Worksmart Labs and they said it was an
Android system update that stopped this, please fix would love to have it work.

PLEASE FIX,I have moto cliq and love CardioTrainer and now does not allow pedometer
to work when screen is not on. FIX THIS PLEASE

DO NOT REPLY to this thread unless you have something to add to the discussion. That
does not include solution requests.

Please fix this. Many applications on my Motorola
Droid are plagued by this

Droid isn't doing. Please fix!

PLEASE FIX, i have HTC Hero and love CardioTrainer and now does not allow pedometer
to work when screen is not on. I want to be able to work out and it count my steps!!!
Please fix!!!

PLEASE FIX!

I have rooted my phone and installed BeHero V1.3.2 (Android 2.1) will this fix the
problem?

I cannot actually get bruno's fix to work for some reason. His page says it works on
droid 2.0.1 but it is not working for me.

It doesn't works in Hero, Nexus and Tattoo.

It works perfectly in Magic.

Fix this bug please or make some wakelock for sensors and cpu! thanks in advance

The pedometer does not work correctly for the cardio program. Please do what you can to
repair this bug.

Thanks,

Would like a fix for this as well!

Please fix

Fix it Palmer!

Please fix so sleep monitoring apps work properly

[Comment deleted]

Having this problem with cardio trainer using motorla backflip

Please fix this issue... @HTC Please upgrade Hero firmware to Version 2.x! It's really embarassing...

Please fix ,not working in 2.0.1.

Hey Google, please help my Nexus wake me up with a smile!

Please fix that!

This really needs to be fixed

Please fix! I have to leave cardio trainer on while
I'm treadmilling, and this means leaving the screen
on for the pedometer count. Leaving the screen on
means random apps turned on or off and cardio
trainer going into pause accidentally.

Please fix this issue!
It's need for many useful applications.

Seems not to work on a HTC legend either.

This issue happens on the HTC Desire as well.

Good to see that my advice has been heeded.

[Comment deleted]

[Comment deleted]

Dito

Really annoying i was getting dangerously close to
thinking the legend was an iPhone beater.

Just in case anybody wants to use it. This bit of code will periodically get the
accelerometer readings when the phone is asleep. I warn you tho!! It's a very nasty
hack, as it has to wake the phone so the screen will be on briefly to take the
measurements, then turns it off again. I don't think I can even use it in my app, as
I would have to explain that to the users.  Maybe if someone knows how to switch the
screen off at a lower level before the wake lock takes place we may have something
usable. In any case Google really need to fix this issue! Even if it allowed readings
in partial lock mode it would be acceptable, but having to have the screen on is
ridiculous! For what it's worth:



        class PhoneMovementManager {

                private SensorManager sensorManager;
                private PowerManager powerManager;
                private SensorEventListener sensorEventListener;
                private Timer timer;

                public PhoneMovementManager(SensorManager sensorManager, PowerManager powerManager) {
                        super();
                        this.sensorManager = sensorManager;
                        this.powerManager = powerManager;
                        sensorEventListener = new SensorEventListener() {

                                public void onSensorChanged(SensorEvent event) {
                                        PhoneMovementManager.this.onAccelerometerChanged(event.values);

                                }

                                public void onAccuracyChanged(Sensor sensor, int accuracy) {
                                        // TODO Auto-generated method stub

                                }
                        };
                }

                protected void onAccelerometerChanged(float[] values) {
                        StringBuffer buf = new StringBuffer();
                        for (float f : values) {
                                buf.append(f);
                                buf.append(", ");
                        }
                        log.debug(buf.toString());
                        synchronized (sensorEventListener) {
                                sensorEventListener.notify();
                        }

                }

                public void init() {
                        timer = new Timer();
                        timer.scheduleAtFixedRate(new TimerTask() {

                                @Override
                                public void run() {
                                        try {
                                                log.debug("START listening on the SENSOR_ACCELEROMETER");
                                                log.debug("register accelerometer listener");
                                                sensorManager.registerListener(sensorEventListener, sensorManager
                                                                .getDefaultSensor(SensorManager.SENSOR_ACCELEROMETER),
                                                                SensorManager.SENSOR_DELAY_NORMAL);
                                                log.debug("acquiring lock");
                                                PowerManager.WakeLock wl =
powerManager.newWakeLock(PowerManager.ACQUIRE_CAUSES_WAKEUP
                                                                | PowerManager.SCREEN_DIM_WAKE_LOCK, PhoneMovementManager.class.getSimpleName());
                                                wl.acquire();
                                                log.debug("waiting");
                                                synchronized (sensorEventListener) {
                                                        sensorEventListener.wait(1000);
                                                }
                                                log.debug("releasing lock");
                                                wl.release();
                                                log.debug("unregister accelerometer listener");
                                                sensorManager.unregisterListener(sensorEventListener);
                                                log.debug("STOP listening on the SENSOR_ACCELEROMETER");
                                        } catch (Exception e) {
                                                log.error("Unable to use SENSOR_ACCELEROMETER", e);
                                        }
                                }
                        }, 10000, 10000);

                }

                public void release() {
                        timer.cancel();

                }

        }

[Comment deleted]

Just tried the unregister and re-register "hack" and it doesn't work on a HTC Legend
(2.1).

This should be solved by a permission: "application can read sensors when in sleep mode"

Please fix this bug!

HTC Hero Smart Alarm users: You can set it so that the screen is always on when the
phone is plugged in by going to Settings > Applications > Development and ticking
""Stay Awake". That way you can use this app at night.

Sadly there are some apps that are impractical to run while charging, like Cardiac
trainer. I hope this bug is fixed soon.

HTC Hero - Sprint: when using Cardio Trainer app the steps are no longer counted when the phone
goes into sleep mode.

HTC Hero - Sprint: when using Cardio Trainer app the steps are no longer counted when the phone
goes into sleep mode.

HTC Hero - Sprint: when using Cardio Trainer app the steps are no longer counted when the phone
goes into sleep mode.

Droid Incredible here, Cardiotrainer unable to count steps when screen is off/asleep

HTC Desire: I'm developing always-sensing based application. This issue is really
critical, in this way I cannot use android platform for my application.
I hope this issue will be fixed ASAP.
Thanks

Fix it please

Am I getting it right that someone is actually working to solve the issue now?
In that case: Thanks to everyone that has commented and made clear thjat the issue is
important. And of course thanks to the one actually working on it.

This bug also happens if you just turn the screen off manually:

WindowManager.LayoutParams params = getWindow().getAttributes();
params.screenBrightness = 0.0f;
getWindow().setAttributes(params);

So it seems that disabling SensorEvents is directly connected to turning off the
screen, regardless of whether the phone is in standby mode.

Cool! So, I assume it is fixed now?

If so then I assume it's in 2.2.

Yes, it is 2.2, in case there are still any doubts about this.

As an addendum, the way it works now is that you have to acquire a partial wake lock.
This guarantees that the CPU will not enter sleep mode and that will guarantee that
the sensors continue sending data as expected. The underlying problem was that,
basically, a partial wake lock would not guarantee that the sensors would continue
running.

Please can this bug get fixed.

Plz fix this!

I experience this on my Motorola Droid. I wish I could record my treadmill workouts
on with Cardio Trainer. But until this is fixed, my recorded workouts look completely
wimpy : )

Could you fix that for HTC Hero. It doesn't work now due this bug.

I would love to c this fixed on htc desire

Yes, this is critical to implement so that some apps can truly compete with Apple

It's really annoying not to recieve updates while phone screen is off even you set a proper PARTIAL WAKE LOCK !

Guys, pay attention! It has been fixed and the fix has been released in Android 2.2. No point on asking for it to be fixed now, right? :)

PLEASE fix this.

Can anyone provide commit number or git link to released fix? any useful info besides "Status: Released"?

I hope a fix can be found soon. I'm very uncomfortable leaving my screen on the whole night. Using an HTC EVO.

I have updated my Nexus One to 2.2, but the accelerometer issue is still not completely solved. OnSensorChanged() is called at sleep mode, but the accuracy can be extremely low. The gap between OnSensorChanged() is random and it can be 15 mins or higher. Has anybody experienced the same issue?

Please fix this issue

My Cardio Trainer Pedometer doesn’t work on my HTC Desire
How to fix it??

My Alarmclock doesn’t work on my HTC Desire

PLEASE fix this.

Please fix this!

Hi *tojaymail*,
   have you updated Nexus One with official release?
About the OnSensorChanged() gap: have you notice this high gap not moving the smartphone? Because OnSensorChanged() receive more updates (=more accelerometer values) while smartphone is moved .
Can you send us a two recording file of the accelerometer values to see any possible difference while the device is moved and not moved (in sleeping mode)?

Bests

Same thing with CardiTrainer using motorola cliq xt anf samsung vibrant with stock roms

Today I've received my 2.2 update for the HTC Desire and unfortunately it did *not* fix this issue.

I repeat: the issue is *not* fixed in Froyo / 2.2 (official non-rooted Desire version).

Whenever my Desire goes into standby (with partial wakelock already acquired and sensor registered as DELAY_NORMAL), logcat tells me "Compass CLOSE" and that's about it. There's *no* sensor information at all. Screen goes off, sensor dies.

All of the sensors die, actually. Orientation, magnetic field, temperature, proximity.. they all don't seem to exist in standby mode with a partial wakelock. With and without moving the device around.

Could someone from Google itself actually provide us with some insight into this situation?

G sensor doesn't work if screen is turned off (standby modus, is needed voor android app 'smart alarm clock', mobile is HTC hero. Bug need to be fixed.

Same on HTC desire. Gsensor doesn't work with screen turned off.

Same on my Desire with 2.2. This bug is a pain in the but. It would seriously make me change the phone if I could afford to.

Plz fix this issue. Desire with 2.2

Please fix it!

I can confirm for Nexus 1 on Android 2.2, if cable is unplugged sensor values come at random times if movement is low (gaps up to about 10 minutes). if there is some movement it seems to be better and most of the time you get the sampling rate you expect, but there are some longer delays (at least in the seconds). All in all, it seems very unreliable...

Same issue with Android 2.2 - steps do not register in cardio trainer with the screen off.