cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zeph Davies (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-10375) Android 6.0 (Marshmallow) getCurrentAcceleration does not callback
Date Wed, 27 Jan 2016 17:26:39 GMT

    [ https://issues.apache.org/jira/browse/CB-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119836#comment-15119836
] 

Zeph Davies commented on CB-10375:
----------------------------------

Apparently it's due to poor nexus 4 accelerometer drivers, in which the "update sensor quality"
is never called.
So, after the first watch is closed, the plugin (?) sets the quality to "UNRELIABLE".
With a new watch created, since the drivers never update the quality, the quality stays as
unreliable.
Therefore, no accelerometer values are returned.

To basically, the first watch (since device boot?) works fine, but a second watch (and all
after) do not work.

This is an issue with the plugin, but is an edge case for a particular phone's poor drivers.

> Android 6.0 (Marshmallow) getCurrentAcceleration does not callback
> ------------------------------------------------------------------
>
>                 Key: CB-10375
>                 URL: https://issues.apache.org/jira/browse/CB-10375
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin Device Motion
>            Reporter: Zeph Davies
>              Labels: Android, triaged
>
> Tested using an application running on Android Lollipop and Marshmallow.
> The Lollipop returns an accelerometer reading.
> The Marshmallow never returns anything (nether success or error callback is called).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message