The issue is that the accelerometer sensor is turning off. So the listener
will not detect any changes while it is off. Your CPU isnt sleeping while
the screen is off, maybe slowing down to save power, but it will
not completely shut off. So a service running should still be running. The
best work
I found the same thing. The accelerometer still fires when the screen is
off but connected to USB and logcat. There might be a work around here
somewhere. I'm just not savy enough to figure it out. Andyone else care to
hack this?
--
You received this message because you are subscribed to the
I didn't see the original thread you're responding to, so what's your question?
As in you want your service to stop using resources when the screen is
off, or the opposite. In one of those situations you can hold a wake
lock to keep the cpu on, but not the screen, I believe.
kris
On Thu, Jan
According these, I think some cases will you come across :
open sensor
1: and then screen off, phone will close sensor. if screen on, sensor will
be lunched, you can log the sensor go on. It's not affect logging result.
2: if not close sensor, I think it should be used AlarmManager to log
because
The common ways to sleep in java, only counts cpu time on the Android
platform.
So a Thread.sleep(60 * 1000); may become 5 or 10 minutes if the phone
is in standby, since it only counts when the cpu is awake.
afaik you need to use AlarmManager to get called when the phone is in
standby.
Even a
Acquire a partial wake lock, that should help.
2011/7/20 Jan Nielsen j...@air-port.dk
The common ways to sleep in java, only counts cpu time on the Android
platform.
So a Thread.sleep(60 * 1000); may become 5 or 10 minutes if the phone
is in standby, since it only counts when the cpu is
Thanks for the replys,
Looking into it the partial wake lock should be my solution, but it isnt
implementing well. I keep getting a runtime error on acquire(). my code
looks like:
PM = (PowerManager) getSystemService(Context.POWER_SERVICE);
WL=
Use adb logcat, DDMS, or the DDMS perspective in Eclipse to examine
LogCat and look at the stack trace associated with your runtime error.
My guess is that you do not hold the WAKE_LOCK permission.
On Wed, Jul 20, 2011 at 11:21 AM, Chris Conry cjco...@gmail.com wrote:
Thanks for the replys,
And your guess was completely correct. Thank you. The problem is
still happening, as soon as I hit the power button the data stops logging.
Is there something else im missing about wakelock?
On Wed, Jul 20, 2011 at 11:26 AM, Mark Murphy mmur...@commonsware.comwrote:
Use adb logcat, DDMS, or the
On Wed, Jul 20, 2011 at 11:53 AM, Chris Conry cjco...@gmail.com wrote:
And your guess was completely correct. Thank you. The problem is
still happening, as soon as I hit the power button the data stops logging.
Is there something else im missing about wakelock?
Try a stronger WakeLock than
Prior to 2.3 the sensors were turned off when the screen went off in order
to reduce battery use. This was changed on 2.3, though it's possible we are
actually going to end up regretting that change. :p
Also even as of 2.3, I wouldn't be surprised if some device's drivers are
still turning off
Partial wake lock works just fine with accelerometer sensor on Nexus One 2.2
(tested this for over than 6 months as a part of my research), although this
might not be the case for different combination of device and OS version.
2011/7/20 Dianne Hackborn hack...@android.com
Prior to 2.3 the
Thanks for the answers,
Makes sense now, I am using the myTouch 4g and LG ally, sadly both of them I
guess turn off their sensors. Its good to hear that the Nexus and some 2.3
device keep it on and hopefully other manufacturers adopt this.
I guess i'm going to try and find a work around. Any
If you are trying to develop a market application, I think there is no
workaround. If you just want to experiment with the accelerometer data, you
can try different types of wakelock as Mark suggested, some of them might
work. Or just keep the device awake while you do the experiments (although
The only two types of wakelocks are partial and full. A full wakelock will
keep the screen from automatically turning off, and the screen being on will
definitely mean the sensors are running. Once the user presses the power
button and turns the screen off, though, you are in no better a state
15 matches
Mail list logo
