[android-developers] Re: Accelerometer not working when screen turns off
How Google Fit app works when phone is locked and how he get sensor values. And Our apps don't get sensor values when phone is locked. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To post to this group, send email to android-developers@googlegroups.com. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/f1525ee1-0bd6-42b5-a432-916c770fd98b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[android-developers] Re: Accelerometer not working when screen turns off
Partial wake lock doesn't work for me either. SCREEN_DIM_WAKE_LOCK works. I'm using a Cliq XT running CM7. On Wednesday, August 25, 2010 3:38:25 AM UTC-7, Furiaceca wrote: Hello, I tried few days ago with my HTC Desire and the official Froyo release ... but when the screen is off the sensor never provide any data: I use Partial Wake lock but this doesn't work. Have you success by using Partial Wake lock? Which smartphone are you using? Thanks a lot Carlo On 16 Lug, 17:06, Bret Foreman bret.fore...@gmail.com wrote: My application will run extensively in partial wakelock mode and I'm very curious to see what standby power consumption consequences that has for various popular phones. Maybe we should start a thread just for that purpose where people can post their observations of battery life in this mode for various phones. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Accelerometer not working when screen turns off
I would prefer a way to do it that wouldn't drain the battery. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Accelerometer not working when screen turns off
On Fri, Jan 20, 2012 at 10:52 AM, crennie cmren...@gmail.com wrote: I would prefer a way to do it that wouldn't drain the battery. You act as though you have a choice. You do not. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 4.0 Programming Books: http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Accelerometer not working when screen turns off
I found that if I'm connected with USB and watching Logcat my accelerometer sensor is still firing even when the screen is off. When I run the same program with out the USB connected the sensor stop a few seconds after the screen goes dark. I wonder if there is a work around here waiting to be found. Can you fool the phone into thinking it is connected to USB? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Accelerometer not working when screen turns off
can this not be fixed using a partial wake lock? kris On Thu, Jan 19, 2012 at 11:23 AM, crennie cmren...@gmail.com wrote: I found that if I'm connected with USB and watching Logcat my accelerometer sensor is still firing even when the screen is off. When I run the same program with out the USB connected the sensor stop a few seconds after the screen goes dark. I wonder if there is a work around here waiting to be found. Can you fool the phone into thinking it is connected to USB? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Accelerometer not working when screen turns off
I have not been able to test yet with an HTC device running Froyo. Adding to the list, I am getting reports that Samsung is having some trouble with this too. On Wed, Aug 25, 2010 at 6:38 AM, Furiaceca ctacc...@gmail.com wrote: Hello, I tried few days ago with my HTC Desire and the official Froyo release ... but when the screen is off the sensor never provide any data: I use Partial Wake lock but this doesn't work. Have you success by using Partial Wake lock? Which smartphone are you using? Thanks a lot Carlo On 16 Lug, 17:06, Bret Foreman bret.fore...@gmail.com wrote: My application will run extensively in partial wakelock mode and I'm very curious to see what standby power consumption consequences that has for various popular phones. Maybe we should start a thread just for that purpose where people can post their observations of battery life in this mode for various phones. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Accelerometer not working when screen turns off
Hello, I tried few days ago with my HTC Desire and the official Froyo release ... but when the screen is off the sensor never provide any data: I use Partial Wake lock but this doesn't work. Have you success by using Partial Wake lock? Which smartphone are you using? Thanks a lot Carlo On 16 Lug, 17:06, Bret Foreman bret.fore...@gmail.com wrote: My application will run extensively in partial wakelock mode and I'm very curious to see what standby power consumption consequences that has for various popular phones. Maybe we should start a thread just for that purpose where people can post their observations of battery life in this mode for various phones. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Accelerometer not working when screen turns off
My application will run extensively in partial wakelock mode and I'm very curious to see what standby power consumption consequences that has for various popular phones. Maybe we should start a thread just for that purpose where people can post their observations of battery life in this mode for various phones. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Accelerometer not working when screen turns off
I heard back from the developer at Google. This should be fixed starting in 2.2. :-) A partial wake lock will be required in order to keep the sensors running when the CPU goes in standby, but the screen turning off will no longer stop the sensors from running. Although I would prefer not to have to hold the wake lock to keep the sensors running in standby, this is still great news! On May 26, 10:44 pm, Jonathan jharrisweinb...@gmail.com wrote: FYI - it looks like Issue 3708 referenced above has now been addressed! I am reaching out to the developer to see if we can get further clarification as to how exactly this has been addressed and in which release. Encouraging news! On May 11, 7:11 pm, Jonathan jharrisweinb...@gmail.com wrote: I'm hoping we don't start debating the usefulness of this issue here. It has been debated quite enough in other threads and on other forums. All I would like at this point is some official response from someone who knows why the behavior is what it is. If it is firmware and it is controlled by the phone manufacturers, then that is an acceptable answer. I'm inclined to think that it is not a firmware issue since this was supposedly fixed in an earlier version of Android, only to have varying results after that. But enough speculating... On May 11, 7:02 pm, mike enervat...@gmail.com wrote: On 05/11/2010 03:56 PM, Kelly wrote: I hear the word 'firmware' being used, which is closely monitored and work on by the manufacturer (HTC, Motorola, Sony Ericsson). I can unserstand why google would have nothing to say, since this is likely 100% controlled by the phone manufacturer who wants to extend battery life by turning off peripheral components in sleep state. My advice is to work around it. I'm sorry, this is silly. The only way to work around it is to lock the display on! Which completely and utterly defeats any battery savings they might have got. I'm perfectly happy with the accelerometer by default being off when the display is being slept, but there needs to be a SDK programmatic way to turn it on for apps that need that functionality. Please don't fall for Apple nanny-state silliness. Mike Cheers On May 11, 2:03 pm, Jordan Frankjordan.w.fr...@gmail.com wrote: Holy crap, this again?!? I just discovered this because we ordered four Nexus Ones to do some demos of our research on the Discovery Channel. All of a sudden what was working perfectly on the G1 stopped working altogether on the Nexus One. If you read the archives of this list, you'll see that I've harped about this a lot in the past, and was delighted when it was changed in Cupcake. Now they've gone and broke it again. And I just spent hundreds shipping these things to Canada. Argggh. So Google, are you going to remain silent on this issue again, or will you let us know at the very least why this decision was made. You've pissed off a lot of developers. Not to mention that your Nexus One phone won't be featured on the Discovery Channel bit that is being filmed tomorrow. Tough luck. Cheers, Jordan On Apr 26, 8:25 pm, mikeenervat...@gmail.com wrote: I'll third that on wanting to know what's up. Some insight as to whether this is a hardware issue on some platforms would be pretty nice too... the same thing happens on the iPhone but getting any insight from them is impossible. Mike On 04/24/2010 09:14 AM, Jonathan wrote: Thanks Lance. I saw that... it is one of the highest ranked issues out there and the comments are being abused quite a bit, but there does not seem to be any response from Google about whether or not they plan to correct this going forward, or if they feel it is something that even needs to be corrected. I've been trying everything I can think of to find some kind of workaround, but so far have failed to do so. It would be great to get a response from one of the Google engineers on this and I think it would hopefully at least put the issue to rest, even if the response is that they do not plan to change this going forward. I hope that is not the answer, but at least we would know. The odd thing is that thesensorsappear to behave somewhat differently depending on the actual device. For example, there are different behaviors between the Droid and the Nexus One, despite the fact that they are both using Android 2.1. So possibly some of the issues are related to the variations in the hardwaresensors themselves, but that is just more speculation. Dianne, if you are out there, I think there are a lot of people that would like to get a response on this one. Thank you!! On Apr 24, 10:14 am, Lance Naneklna...@gmail.com wrote: http://code.google.com/p/android/issues/detail?id=3708 On Apr 13, 6:32 am,
[android-developers] Re: Accelerometer not working when screen turns off
Its the backlight that sucks coulombs. If you can dim that way down, you're golden. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Accelerometer not working when screen turns off
FYI - it looks like Issue 3708 referenced above has now been addressed! I am reaching out to the developer to see if we can get further clarification as to how exactly this has been addressed and in which release. Encouraging news! On May 11, 7:11 pm, Jonathan jharrisweinb...@gmail.com wrote: I'm hoping we don't start debating the usefulness of this issue here. It has been debated quite enough in other threads and on other forums. All I would like at this point is some official response from someone who knows why the behavior is what it is. If it is firmware and it is controlled by the phone manufacturers, then that is an acceptable answer. I'm inclined to think that it is not a firmware issue since this was supposedly fixed in an earlier version of Android, only to have varying results after that. But enough speculating... On May 11, 7:02 pm, mike enervat...@gmail.com wrote: On 05/11/2010 03:56 PM, Kelly wrote: I hear the word 'firmware' being used, which is closely monitored and work on by the manufacturer (HTC, Motorola, Sony Ericsson). I can unserstand why google would have nothing to say, since this is likely 100% controlled by the phone manufacturer who wants to extend battery life by turning off peripheral components in sleep state. My advice is to work around it. I'm sorry, this is silly. The only way to work around it is to lock the display on! Which completely and utterly defeats any battery savings they might have got. I'm perfectly happy with the accelerometer by default being off when the display is being slept, but there needs to be a SDK programmatic way to turn it on for apps that need that functionality. Please don't fall for Apple nanny-state silliness. Mike Cheers On May 11, 2:03 pm, Jordan Frankjordan.w.fr...@gmail.com wrote: Holy crap, this again?!? I just discovered this because we ordered four Nexus Ones to do some demos of our research on the Discovery Channel. All of a sudden what was working perfectly on the G1 stopped working altogether on the Nexus One. If you read the archives of this list, you'll see that I've harped about this a lot in the past, and was delighted when it was changed in Cupcake. Now they've gone and broke it again. And I just spent hundreds shipping these things to Canada. Argggh. So Google, are you going to remain silent on this issue again, or will you let us know at the very least why this decision was made. You've pissed off a lot of developers. Not to mention that your Nexus One phone won't be featured on the Discovery Channel bit that is being filmed tomorrow. Tough luck. Cheers, Jordan On Apr 26, 8:25 pm, mikeenervat...@gmail.com wrote: I'll third that on wanting to know what's up. Some insight as to whether this is a hardware issue on some platforms would be pretty nice too... the same thing happens on the iPhone but getting any insight from them is impossible. Mike On 04/24/2010 09:14 AM, Jonathan wrote: Thanks Lance. I saw that... it is one of the highest ranked issues out there and the comments are being abused quite a bit, but there does not seem to be any response from Google about whether or not they plan to correct this going forward, or if they feel it is something that even needs to be corrected. I've been trying everything I can think of to find some kind of workaround, but so far have failed to do so. It would be great to get a response from one of the Google engineers on this and I think it would hopefully at least put the issue to rest, even if the response is that they do not plan to change this going forward. I hope that is not the answer, but at least we would know. The odd thing is that thesensorsappear to behave somewhat differently depending on the actual device. For example, there are different behaviors between the Droid and the Nexus One, despite the fact that they are both using Android 2.1. So possibly some of the issues are related to the variations in the hardwaresensors themselves, but that is just more speculation. Dianne, if you are out there, I think there are a lot of people that would like to get a response on this one. Thank you!! On Apr 24, 10:14 am, Lance Naneklna...@gmail.com wrote: http://code.google.com/p/android/issues/detail?id=3708 On Apr 13, 6:32 am, Jonathanjharrisweinb...@gmail.com wrote: As I understand it, there seems to have been a change in the OS that prevents the accelerometer from running when the screen turns off and the phone CPU goes into its power saving state. Can this be confirmed? I have gotten around this by using a wake lock, but this is a much less than ideal solution as it drains a lot of battery. If the accelerometer was disabled in low power mode to save the battery, it may very well have the opposite effect in many cases, such as
[android-developers] Re: Accelerometer not working when screen turns off
Holy crap, this again?!? I just discovered this because we ordered four Nexus Ones to do some demos of our research on the Discovery Channel. All of a sudden what was working perfectly on the G1 stopped working altogether on the Nexus One. If you read the archives of this list, you'll see that I've harped about this a lot in the past, and was delighted when it was changed in Cupcake. Now they've gone and broke it again. And I just spent hundreds shipping these things to Canada. Argggh. So Google, are you going to remain silent on this issue again, or will you let us know at the very least why this decision was made. You've pissed off a lot of developers. Not to mention that your Nexus One phone won't be featured on the Discovery Channel bit that is being filmed tomorrow. Tough luck. Cheers, Jordan On Apr 26, 8:25 pm, mike enervat...@gmail.com wrote: I'll third that on wanting to know what's up. Some insight as to whether this is a hardware issue on some platforms would be pretty nice too... the same thing happens on the iPhone but getting any insight from them is impossible. Mike On 04/24/2010 09:14 AM, Jonathan wrote: Thanks Lance. I saw that... it is one of the highest ranked issues out there and the comments are being abused quite a bit, but there does not seem to be any response from Google about whether or not they plan to correct this going forward, or if they feel it is something that even needs to be corrected. I've been trying everything I can think of to find some kind of workaround, but so far have failed to do so. It would be great to get a response from one of the Google engineers on this and I think it would hopefully at least put the issue to rest, even if the response is that they do not plan to change this going forward. I hope that is not the answer, but at least we would know. The odd thing is that thesensorsappear to behave somewhat differently depending on the actual device. For example, there are different behaviors between the Droid and the Nexus One, despite the fact that they are both using Android 2.1. So possibly some of the issues are related to the variations in the hardwaresensors themselves, but that is just more speculation. Dianne, if you are out there, I think there are a lot of people that would like to get a response on this one. Thank you!! On Apr 24, 10:14 am, Lance Naneklna...@gmail.com wrote: http://code.google.com/p/android/issues/detail?id=3708 On Apr 13, 6:32 am, Jonathanjharrisweinb...@gmail.com wrote: As I understand it, there seems to have been a change in the OS that prevents the accelerometer from running when the screen turns off and the phone CPU goes into its power saving state. Can this be confirmed? I have gotten around this by using a wake lock, but this is a much less than ideal solution as it drains a lot of battery. If the accelerometer was disabled in low power mode to save the battery, it may very well have the opposite effect in many cases, such as mine. A partial wake lock seems to be required to keep it running, which is obviously much worse than if just the accelerometer were running without the need for the wake lock. Are there any other workarounds anyone knows of to getting accelerometer values while the phone is in low power mode? Also, are there any plans to change this in future versions of the OS? If there are no plans to change this, I would definitely like to petition for this to be changed. Thoughts? Ideas? Workarounds? Thank you!! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Accelerometer not working when screen turns off
I'm hoping we don't start debating the usefulness of this issue here. It has been debated quite enough in other threads and on other forums. All I would like at this point is some official response from someone who knows why the behavior is what it is. If it is firmware and it is controlled by the phone manufacturers, then that is an acceptable answer. I'm inclined to think that it is not a firmware issue since this was supposedly fixed in an earlier version of Android, only to have varying results after that. But enough speculating... On May 11, 7:02 pm, mike enervat...@gmail.com wrote: On 05/11/2010 03:56 PM, Kelly wrote: I hear the word 'firmware' being used, which is closely monitored and work on by the manufacturer (HTC, Motorola, Sony Ericsson). I can unserstand why google would have nothing to say, since this is likely 100% controlled by the phone manufacturer who wants to extend battery life by turning off peripheral components in sleep state. My advice is to work around it. I'm sorry, this is silly. The only way to work around it is to lock the display on! Which completely and utterly defeats any battery savings they might have got. I'm perfectly happy with the accelerometer by default being off when the display is being slept, but there needs to be a SDK programmatic way to turn it on for apps that need that functionality. Please don't fall for Apple nanny-state silliness. Mike Cheers On May 11, 2:03 pm, Jordan Frankjordan.w.fr...@gmail.com wrote: Holy crap, this again?!? I just discovered this because we ordered four Nexus Ones to do some demos of our research on the Discovery Channel. All of a sudden what was working perfectly on the G1 stopped working altogether on the Nexus One. If you read the archives of this list, you'll see that I've harped about this a lot in the past, and was delighted when it was changed in Cupcake. Now they've gone and broke it again. And I just spent hundreds shipping these things to Canada. Argggh. So Google, are you going to remain silent on this issue again, or will you let us know at the very least why this decision was made. You've pissed off a lot of developers. Not to mention that your Nexus One phone won't be featured on the Discovery Channel bit that is being filmed tomorrow. Tough luck. Cheers, Jordan On Apr 26, 8:25 pm, mikeenervat...@gmail.com wrote: I'll third that on wanting to know what's up. Some insight as to whether this is a hardware issue on some platforms would be pretty nice too... the same thing happens on the iPhone but getting any insight from them is impossible. Mike On 04/24/2010 09:14 AM, Jonathan wrote: Thanks Lance. I saw that... it is one of the highest ranked issues out there and the comments are being abused quite a bit, but there does not seem to be any response from Google about whether or not they plan to correct this going forward, or if they feel it is something that even needs to be corrected. I've been trying everything I can think of to find some kind of workaround, but so far have failed to do so. It would be great to get a response from one of the Google engineers on this and I think it would hopefully at least put the issue to rest, even if the response is that they do not plan to change this going forward. I hope that is not the answer, but at least we would know. The odd thing is that thesensorsappear to behave somewhat differently depending on the actual device. For example, there are different behaviors between the Droid and the Nexus One, despite the fact that they are both using Android 2.1. So possibly some of the issues are related to the variations in the hardwaresensors themselves, but that is just more speculation. Dianne, if you are out there, I think there are a lot of people that would like to get a response on this one. Thank you!! On Apr 24, 10:14 am, Lance Naneklna...@gmail.com wrote: http://code.google.com/p/android/issues/detail?id=3708 On Apr 13, 6:32 am, Jonathanjharrisweinb...@gmail.com wrote: As I understand it, there seems to have been a change in the OS that prevents the accelerometer from running when the screen turns off and the phone CPU goes into its power saving state. Can this be confirmed? I have gotten around this by using a wake lock, but this is a much less than ideal solution as it drains a lot of battery. If the accelerometer was disabled in low power mode to save the battery, it may very well have the opposite effect in many cases, such as mine. A partial wake lock seems to be required to keep it running, which is obviously much worse than if just the accelerometer were running without the need for the wake lock. Are there any other workarounds anyone knows of to getting accelerometer values while the phone is in low power mode? Also, are there any plans to change this in future versions of the OS? If
Re: [android-developers] Re: Accelerometer not working when screen turns off
I'll third that on wanting to know what's up. Some insight as to whether this is a hardware issue on some platforms would be pretty nice too... the same thing happens on the iPhone but getting any insight from them is impossible. Mike On 04/24/2010 09:14 AM, Jonathan wrote: Thanks Lance. I saw that... it is one of the highest ranked issues out there and the comments are being abused quite a bit, but there does not seem to be any response from Google about whether or not they plan to correct this going forward, or if they feel it is something that even needs to be corrected. I've been trying everything I can think of to find some kind of workaround, but so far have failed to do so. It would be great to get a response from one of the Google engineers on this and I think it would hopefully at least put the issue to rest, even if the response is that they do not plan to change this going forward. I hope that is not the answer, but at least we would know. The odd thing is that the sensors appear to behave somewhat differently depending on the actual device. For example, there are different behaviors between the Droid and the Nexus One, despite the fact that they are both using Android 2.1. So possibly some of the issues are related to the variations in the hardware sensors themselves, but that is just more speculation. Dianne, if you are out there, I think there are a lot of people that would like to get a response on this one. Thank you!! On Apr 24, 10:14 am, Lance Naneklna...@gmail.com wrote: http://code.google.com/p/android/issues/detail?id=3708 On Apr 13, 6:32 am, Jonathanjharrisweinb...@gmail.com wrote: As I understand it, there seems to have been a change in the OS that prevents the accelerometer from running when the screen turns off and the phone CPU goes into its power saving state. Can this be confirmed? I have gotten around this by using a wake lock, but this is a much less than ideal solution as it drains a lot of battery. If the accelerometer was disabled in low power mode to save the battery, it may very well have the opposite effect in many cases, such as mine. A partial wake lock seems to be required to keep it running, which is obviously much worse than if just the accelerometer were running without the need for the wake lock. Are there any other workarounds anyone knows of to getting accelerometer values while the phone is in low power mode? Also, are there any plans to change this in future versions of the OS? If there are no plans to change this, I would definitely like to petition for this to be changed. Thoughts? Ideas? Workarounds? Thank you!! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Accelerometer not working when screen turns off
http://code.google.com/p/android/issues/detail?id=3708 On Apr 13, 6:32 am, Jonathan jharrisweinb...@gmail.com wrote: As I understand it, there seems to have been a change in the OS that prevents the accelerometer from running when the screen turns off and the phone CPU goes into its power saving state. Can this be confirmed? I have gotten around this by using a wake lock, but this is a much less than ideal solution as it drains a lot of battery. If the accelerometer was disabled in low power mode to save the battery, it may very well have the opposite effect in many cases, such as mine. A partial wake lock seems to be required to keep it running, which is obviously much worse than if just the accelerometer were running without the need for the wake lock. Are there any other workarounds anyone knows of to getting accelerometer values while the phone is in low power mode? Also, are there any plans to change this in future versions of the OS? If there are no plans to change this, I would definitely like to petition for this to be changed. Thoughts? Ideas? Workarounds? Thank you!! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Accelerometer not working when screen turns off
Thanks Lance. I saw that... it is one of the highest ranked issues out there and the comments are being abused quite a bit, but there does not seem to be any response from Google about whether or not they plan to correct this going forward, or if they feel it is something that even needs to be corrected. I've been trying everything I can think of to find some kind of workaround, but so far have failed to do so. It would be great to get a response from one of the Google engineers on this and I think it would hopefully at least put the issue to rest, even if the response is that they do not plan to change this going forward. I hope that is not the answer, but at least we would know. The odd thing is that the sensors appear to behave somewhat differently depending on the actual device. For example, there are different behaviors between the Droid and the Nexus One, despite the fact that they are both using Android 2.1. So possibly some of the issues are related to the variations in the hardware sensors themselves, but that is just more speculation. Dianne, if you are out there, I think there are a lot of people that would like to get a response on this one. Thank you!! On Apr 24, 10:14 am, Lance Nanek lna...@gmail.com wrote: http://code.google.com/p/android/issues/detail?id=3708 On Apr 13, 6:32 am, Jonathan jharrisweinb...@gmail.com wrote: As I understand it, there seems to have been a change in the OS that prevents the accelerometer from running when the screen turns off and the phone CPU goes into its power saving state. Can this be confirmed? I have gotten around this by using a wake lock, but this is a much less than ideal solution as it drains a lot of battery. If the accelerometer was disabled in low power mode to save the battery, it may very well have the opposite effect in many cases, such as mine. A partial wake lock seems to be required to keep it running, which is obviously much worse than if just the accelerometer were running without the need for the wake lock. Are there any other workarounds anyone knows of to getting accelerometer values while the phone is in low power mode? Also, are there any plans to change this in future versions of the OS? If there are no plans to change this, I would definitely like to petition for this to be changed. Thoughts? Ideas? Workarounds? Thank you!! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group athttp://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
