Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

Compability for Samsung devices forcing 3-4 array vector length #9746

Merged
merged 1 commit into from Aug 10, 2017

Conversation

tobrun
Copy link
Member

@tobrun tobrun commented Aug 10, 2017

Closes #9745, as noted in issue and shown in chromium tracker. A couple of 4.3 Samsung devices throw an exception when the rotation vector size is larger as 4. This PR provides compatibility those devices.

Haven't been able to verify this issue myself, default implementation still works.

@tobrun tobrun added this to the android-v5.1.3 milestone Aug 10, 2017
@tobrun tobrun self-assigned this Aug 10, 2017
// For the purposes of this class the first 4 values of the
// rotation vector are sufficient (see crbug.com/335298 for details).
// Only affects Android 4.3
if (truncatedRotationVectorValue == null) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correct, fixed in 3c4810e

Copy link
Contributor

@Guardiola31337 Guardiola31337 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@tobrun tobrun merged commit 9238dd4 into master Aug 10, 2017
@tobrun tobrun deleted the 9745-samsung-sensor-bug branch August 10, 2017 13:08
@kkaefer kkaefer added the Android Mapbox Maps SDK for Android label Aug 16, 2017
@tobrun tobrun mentioned this pull request Aug 18, 2017
19 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Android Mapbox Maps SDK for Android
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants