If you are using sensors then check this.
There is a feature specific for Motorola phones: Sensor subsystem
doesn't report SensorEvent unless the values have been changed since
the previous call.
Let's say you are using the following code:
mSensorManager.registerListener(this, mLightSensor,
SensorManager.SENSOR_DELAY_NORMAL)
If you expect to get roughly 5 updates per second then you are wrong:
you will get update only when driver decides so - it could be in 10
seconds or 30 minutes. Different sensors have different noise level
therefore it is hard to notice on every Sensor on all Motorola phone.
I found it on Milestone (aka Droid) then reproduced it on Motorola
Backflip. Filed a bug but didn't get any feedback.
Someone at Motorola should be very proud of this "improvement" ;)
On Jan 24, 2:26 pm, darrinps <[email protected]> wrote:
> I have an app on the market. Everyone I have had try it (half dozen
> folks or so) likes the thing and it works well, but one type of
> Android based phone seems to have major issues with it.
>
> In specific, Droids! The app plays Ogg Vorbis (ogg) sound files and
> displays a white screen at varying intensities (it's a night light
> app).
>
> Does anyone have a clue as to why Droids act differently than all
> others (I've hit a wide variety of other phones and they all work
> fine)?
>
> Also as a side note, wouldn't it be GREAT if Google would have a bank
> of phones one could install their application on for testing? We could
> pay a nominal fee, sign up, do our testing, and then let the next one
> hit the phone farm.
>
> I really hate having bugs that customers have to discover that I don't
> have a good way to solve like this.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
