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 Frank<jordan.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, 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 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 > >>> 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 > 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
