Aframe: Aframe Camera issues in latest Android chrome version

[artemistint]

The camera cannot be tilted, also camera movement very slow.
Dowgrade to ver. 56 of Chrome resolved the issue.

• A-Frame Version: 0.7.1 / 0.8.0
• Platform / Device: Android 7, Chrome 65.0.3325.109
• Reproducible Code Snippet or URL: Aframe.io

[jeanmatthieud]

Same issue with

• A-Frame Version: 0.7.1
• Platform / Device: Android 8, Chrome 65.0.3325.109
• Reproducible Code Snippet or URL: Aframe.io (examples)

AFrame doesn't use the gyros anymore, and behaves as the non-gyro-equipped phones.
It impacts every Android app using Cordova (the webview is based on Chrome)

[jeanmatthieud]

I checked the master, and the #3453 fixes in part the issue.
Now, the camera have a low refresh rate.
It's linked to an issue of Chromium : https://bugs.chromium.org/p/chromium/issues/detail?id=819413&desc=3

Moreover, the VR view is and moves in the wrong way when using aframe master and Chrome 65.0.3325.109.
It's OK with the old version of Chrome and aframe master.

[jsantell]

More information on the workarounds and Chrome regressions can be found in the polyfill's v0.10.3 release notes

[jsantell]

@jeanmatthieud the camera moving the wrong way, is this only when you start in landscape? I believe https://github.com/aframevr/aframe/pull/3466 will fix this if that's the issue you're running into

[dmarcos]

@jeanmatthieud this should be fixed on master now. Can you confirm?

[dirkk0]

No, it's not fixed.

[jsantell]

What's the result? If it's stuttering on rotation updates, that's a platform regression on Chrome m65 and not much we can do to fix in JS land.

[dirkk0]

It's stuck on some random axis, and mobile device movement doesn't do anything anymore on Android Chrome.

[jsantell]

@dirkk0 what version of the polyfill (or commit of A-Frame build) is being used on that site?

[dirkk0]

@jsantell thanks for looking into this!
it was:
//cdnjs.cloudflare.com/ajax/libs/aframe/0.7.1/aframe.min.js
and is now:
//rawgit.com/aframevr/aframe/4d90df5/dist/aframe-master.min.js
(because we hoped the latest version would somehow mitigate the problem)

[jsantell]

Do you have a link to the site anywhere where you can reproduce?

[dirkk0]

my apologies:
it is indeed stuttering on rotation updates, as you said. I was probably looking at a cached version.
So we need to wait for m66, hoping there is a fix, right?

[jsantell]

There's a fix in m66 for the stuttering, correct -- there may be a m65 update with a fix, but at this point seems unlikely

[Adilmar]

Hi, can anyone tell me if the problem with the VR camera has been solved?

In earlier versions of Chrome it works perfectly.

[jsantell]

This webvr-polyfill release details what issues are on latest Chrome, and the workarounds employed

[Kezzsim]

Having no luck with our site The Union Project A-Frame 0.8 fixes issues we've been having on mobile with one click causing two click events, but the Gyroscope is totally disabled on chrome Android 65 & beta 66. We are using the dist above with the latest Polyfill version, also clicking is kinda weird and insensitive at times on mobile and in the mobile emulator; but I think the lack of Gyro is more severe.

[dmarcos]

@Kezzsim On the A-Frame side we won't be able to work around all of the problems introduced on m65. We will have to wait till the fixes are deployed in m66 to have everything working as before.

[chngngclrs]

Hello, I'm new to this and found this thread because I've got no gyroscope in chrome...but i have sound...while in Firefox I have gyroscope but no sound....any suggestions for the best browser to test my projects on that will allow both sound and head movement? Using Galaxy note 4, for now.
Thanks

[jsantell]

@chngngclrs gyroscope issue fixed (mostly) in latest aframe; audio issue sounds like a codec that Firefox does not support

[sabbir420]

I got the same issue on Samsung S6. When I move right to left or up and down, it moves slowly. I tested on every browser on Samsung S6. But same thing I have found. It's really slow.

[chngngclrs]

Updated the Samsung browser late last night and I get full gyroscope and my
sound is working. So I’ll use this browser for a bit.

On Thu, Mar 29, 2018 at 12:34 AM MD Sabbir Hossain [e-mail]
wrote:

I got the same issue on Samsung S6. When I move right to left or up and
down, it moves slowly. I tested on every browser on Samsung S6. But same
thing I have found. It's really slow.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aframevr/aframe/issues/3458#issuecomment-377136628,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjuFdzDzX-0ON7JcGQCEvsZQS7Dc5jwyks5tjIBzgaJpZM4Sr03S
.

[sabbir420]

I checked some aframe example on Samsung S6 even on Samsung S6 edge some times. But I have found same problem. It's moving very slow.
I checked with these examples:
https://aframe.io/aframe/examples/performance/cubes/
https://aframe.io/aframe/examples/performance/entity-count/
https://aframe.io/aframe/examples/performance/animation/
https://aframe.io/aframe/examples/test/geometry-gallery/
And some other. What can I do for this lagging issue?

[dirkk0]

I wonder why the Threejs examples still work on m65?
https://threejs.org/examples/webvr_cubes.html

[jsantell]

@sabbir420 w/r/t lagging issue: https://github.com/aframevr/aframe/issues/3458#issuecomment-375915490
@dirkk0 three.js examples use an origin trial, so using native WebVR most likely rather than the polyfill, which uses devicemotion/orientation which is the source of issues in Chrome m65

[EdgarPironti]

Any news about this?

[jsantell]

nothing to update on until m66

[Adilmar]

Can someone tell me if the problem has been solved? Thanks

[dirkk0]

Nope, but hope is m66 is to be released very soon:
https://www.chromestatus.com/features/schedule
I can also confirm that it is fixed in Chrome Canary already.

[FeralRizvi]

Looks like it's gotten worse with m66 - camera is now moving on it's own: https://drive.google.com/file/d/1CeFykDjUC9GkZxLFqRnhQiROQ_lO1qDl/view?usp=drivesdk

[dirkk0]

are you sure you are on m66?

[FeralRizvi]

I think so! https://drive.google.com/file/d/1bd_TmtKUqXrTnM79Ls1d4cF8jHC7SGRx/view?usp=drivesdk

[dirkk0]

ok, I have m66 too, now.
Switching through the example section of aframe.io, I can confirm that some examples work, while others look weird.
I think this is because some of the examples are not on the latest version.
@FeralRizvi what aframe version did you import?

[FeralRizvi]

I'm on 0.8.0 @dirkk0

[dmarcos]

@FeralRizvi Update to 0.8.2

[FeralRizvi]

Works now!!! Thank you so much @dmarcos !

[Adilmar]

People my Chrome updated to 66 but the gyroscope bug continues, any solution? Thanks

[dmarcos]

@Adilmar are you using 0.8.2

[Adilmar]

@dmarcos Yes in the browser only it works, in the phonegap app no longer works.

[dmarcos]

As far as I know phonegap goes behind in the chromium version they use. If they are behind m66 then the bugs introduced in m65 will remain until phonegap catches up.

[Adilmar]

@dmarcos I understand, but when I come back to the version of my Chrome it works.

[dmarcos]

@Adilmar You're probably on Chrome m66 or on a version older than m65 that's why it works, right? Phonegap might be shipping a Chrome version affected by the bugs described in this issue.

[Adilmar]

@dmarcos I understood, thanks, I'll wait for an update.

[dax72]

Gyroscope doesn't work before to enter on VR Mode!
I have this issue on Samsung S8 ( Chrome 66.0.3359.158) with Aframe 0.8.2.

It works with Aframe 0.7.1

[manoweb]

Gyroscope doesn't work in fullscreen and VR
Android 6 / Chrome 67 /aframe 0.8.2

[timokorkalainen]

Indeed, same here. Samsung S8, Android 8, Aframe 0.8.2, Chrome 67. No gyros in the non-vr mode, just the one axis touch movement.

[Xrispy7]

I am also experiencing a gyro problem on 2 phones except they are accessing the gyro but with either random input, or very very sensitive input. If i keep my hand still and don't move it is almost still but i can see the micromovements on screen with my hand's micro shaking.

The Gyro works 100% fine with this link:

https://aframe.io/examples/showcase/sky/

but not the image gallery:
https://aframe.io/examples/showcase/360-image-gallery/

Honor 6x | Android 7.0 EMUI 5.0.2 / Google Chrome 67.0.3396.87 / aframe 0.8.2
&
Samsung S8 |Google Chrome 67.0.3396.87 / aframe 0.8.2

Thanks!

[jsantell]

https://aframe.io/examples/showcase/sky/ is using 0.8.2
https://aframe.io/360-image-gallery-boilerplate/ is using Aframe 0.3.2

Older versions of aframe will not work on the latest versions of Chrome

[EdgarPironti]

Gyro was finally working good with 0.8.2 and Chrome m66.
Now on Chrome m67 it is not working again (not shaking this time, but completely still I can just rotate on one axis swiping with my finger) is it expected?

[tomsride]

Same problem here: 0.8.2 and Chrome m67: camera not shaking, but no gyro active until entering VR-mode.

[eggybot]

same issue with Chrome m68 using 0.8.2
fixed (update): I got issue with aframe-layout and no error with version 0.8.2 and m68 just the other library causing the issue.

update (issue): there is a slight movement to the left when I intend to focus or stand still (no movement). This slow movement keeping me as a user to notice that my view has been automatically rotating. Is there are quick fix to this issue?

thanks,

[dmarcos]

@eggybot what phone?

[srdmathur]

With Chrome Version 70.0.3538.80 and Aframe version 0.8.2, The Movement is very slow in android mobile

[dmarcos]

@srdmathur What phone / chrome version?

[dmarcos]

I can't reproduce on Pixel 3 / Chrome m71

[dmarcos]

Gyro should work on Chrome m66+ / A-Frame 0.8.2+

If it doesn’t please open a new issue with Phone / Chrome version / A-Frame version and link with demo that reproduces the issue.

[walidabazo]

A-Frame Version: 0.7.x / 0.8.x/ 0.9.x
Working Done show this solution
tested on android 7 / 8
https://github.com/walidabazo/a-frame-android-

[dmarcos]

@walidabazo Sorry I don't understand. Is there still a problem?

FYI, Chrome and Safari now ship with devicemotion events disabled by default. The user has to enable manually on settings:

• chrome://flags/#enable-generic-sensor in Chrome

• Settings -> Safari -> Motion & Orientation Access in Safari iOS

Content also must be served over https.

More info on: https://github.com/aframevr/aframe/issues/3976

[Kif11]

I noticed that gyro doesn't work on Android when you serves from localhost over HTTP.
Changing my Webpack devServer config to https: true makes gyro work.

[dmarcos]

Correct. Browsers enforce https to access the sensors

[joelmarquez]

A-Frame Version: 0.7.x / 0.8.x/ 0.9.x
Working Done show this solution
tested on android 7 / 8
https://github.com/walidabazo/a-frame-android-

I Use this:

work on the latest versions of Chrome

Thanks for your support.

[dmarcos]

You are in a very old A-Frame version. Use 1.0.4