Tested the issue on chrome reported version 65.0.3325.146 using Ubuntu 14.04 with steps mentioned below:
1) Launched chrome reported version and opened Devtools > Console
2) Tried executing DeviceOrientationEvent.alpha, DeviceOrientationEvent.beta, DeviceOrientationEvent.gamma in console, it is showing as undefined.
Observation: Tested the issue on Ubuntu 17.10, observed same behaviour as mentioned in above steps.

@Reporter: Please find the attached screen cast for your reference and provide your inputs on it which helps us in further triaging in better way.

Thanks!

Deleted: 820943.ogv 2.0 MB

	820943.ogv 2.0 MB View Download

I was listen to device absolute rotation (https://developers.google.com/web/updates/2016/03/device-orientation-changes). Event is fired only when tab is focused. Also the test is performed on android device with latest software and all needed sensors to calculate this orientation. 

*** Mobile device
*** window.addEventListener('deviceorientationabsolute', function(event) { 
      event.gamma = null, event.beta = null, event.alpha = null
  });
*** deviceorientationabsolute are firing only once on start and when tab is again on focus.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sorry for choosing wrong OS. I cannot find functionality to change it to Android.

As per comment#5 from the reporter, as the issue seems related to Android, hence adding appropriate OS label to it.

Thanks!

aleksandar@ -- Thanks for reporting the issue. Could you please provide the screen cast of the actual issue with required test data to reproduce at our end. Along with the device details including OS version.

This issue could be same as the  issue 820926 . @juncai, could you please take a look into it.

Thanks!

Must be related:  I just had to demo aframe WebVR and it worked fine on Firefox on my Pixel 2, Chrome M64 on my Pixel XL - but not on M65+ (stable, beta, dev, canary) on Pixel 2  ... the http://aframe.io  start page when browsing from mobile exposes it (and I *don't* think it's a hardware issue because Firefox works on the same device.  the behavior: extremely slow movement - except for canary, where it's way too fast

aleksandar@gsix.me: What chrome version did you use on Android to test? Can you try it on Canary?
The deviceorientationabsolute event is firing only when tab is on focus, and this is working as intended, because it doesn't need continuous pulling of sensor data, and can help reduce power consumption.

larsgk@gmail.com: "the behavior: extremely slow movement" is caused by the following issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=819413&desc=3
And this is fixed on Canary and merged to M66.
"except for canary, where it's way too fast" is because the change in units explained here:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/ple1o7bFqEs/jJuhTSEYCwAJ
https://bugs.chromium.org/p/chromium/issues/detail?id=541607

Chrome version 65.0.3325.109 
Sorry i cannot try on Canary at the moment.
Yup the problem is that is firing only once when tab is on focus. 

Is not related with https://bugs.chromium.org/p/chromium/issues/detail?id=819413&desc=3 or any other issue. 

Once again:

    If i go with deviceorientation i always get absolute value false.

    If i go with deviceorientationabsolute is only firing once and tab is on focus.

aleksandar@gsix.me: What device did you use to test? Can you try the following website to see if the sensor data is updated continuously?
http://code.viget.com/device-motion-demo

aleksandar@gsix.me: if the deviceorientation works fine, and the absolute flag is set false, then the deviceorientationabsolute should only be firing once, this is working as intended, because it can not provide the deviceorientationabsolute values, as explained in the spec:
"If an implementation can never provide absolute orientation information, the event should be fired with the alpha, beta and gamma attributes set to null."
https://w3c.github.io/deviceorientation/spec-source-orientation.html#deviceorientationabsolute

Attached video with http://code.viget.com/device-motion-demo demo.
Device HTC M9 Android 7.0

Deleted: deviceorientattionchrome65.mp4 908 KB

	deviceorientattionchrome65.mp4 908 KB View Download

You are wrong because deviceorientationabsolute was working fine before update to 65 version.

I see. Sorry for the confusion. From the screen video, I think it is related to the issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=805146
The fix was merged to M65, but the current M65 stable version doesn't have the fix yet. The M66 dev and M67 Canary both have the fix.

Hello Juncai.

I wanna know when the bug will be fixed. I have a startup that make contents in virtual reality and I show them by using samsung s7 and cardboard. The new version 65 of chrome doesn´t have the possibility to move the cell phone and follow the photo in 360. All my clients are claiming about that!!

Please.. I need a answear about the atualization of the Chrome.

Here my website with a example
www.mucavr.com.br/exemplos/BQ.html

Best Regard
Jonatas Garcia
CEO Muca vr 

Hi jonatasogarcia@gmail.com, sorry about the situation. We are working on trying to solve this issue.

BTW, the latest Chrome Beta M66 (66.0.3359.30) has the fix, and Chrome Dev, and Canary also have the fix.