Accelerometer and light sensor only working after pm-suspend

[chives]

My notebook has a built-in accelerometer and light sensor. Both are not working after normal startup, which I can confirm by the output of
sudo gdbus introspect --system --dest net.hadess.SensorProxy --object-path /net/hadess/SensorProxy
Also the automatic screen rotation does not work at this point.

As soon as I go into suspend and return, I receive a valid output for both. The screen rotation then works fine as well.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-generic 4.4.0.28.30
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: timeshifter 1768 F.... pulseaudio
 /dev/snd/controlC1: timeshifter 1768 F.... pulseaudio
CurrentDesktop: GNOME
Date: Sat Jul 2 14:27:03 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
InstallationDate: Installed on 2016-03-19 (104 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20C0003SFR
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/usr/bin/zsh
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-28-generic N/A
 linux-backports-modules-4.4.0-28-generic N/A
 linux-firmware 1.157.1
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-07-02 (0 days ago)
dmi.bios.date: 11/07/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: B0ET24WW (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C0003SFR
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrB0ET24WW(1.11):bd11/07/2014:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C0003SFR
dmi.product.version: ThinkPad S1 Yoga
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

chives, thank you for reporting this and helping make Ubuntu better.

Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)?

[chives (mra+ubuntu)]

penalvch, thanks for addressing this issue so quickly.

I'm afraid there is no further information. The stickers only provide the machine code and the serial number. The machine code allows for precise identification of the hardware for Lenovo computers. Also in the BIOS there's no information visible that is not printed here.

This is a Lenovo ThinkPad Yoga (S1, first generation), machine code 20C0003SFR.

[chives (mra+ubuntu)]

I'm sorry for having missed the "have-the-bios-updated" part of the FAQ. I did this now.

1)
# dmidecode -s bios-version && sudo dmidecode -s bios-release-date
B0ET33WW (1.20 )
04/29/2016

2) The problem persists without any kind of improvement.

Thanks for the support.

[penalvch (penalvch)]

chives, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

[chives (mra+ubuntu)]

I have tested this against 4.7-RC6. The problem is still present here.

$ uname -r
4.7.0-040700rc6-generic

[penalvch (penalvch)]

chives, to clarify, did this issue not occur in a Ubuntu release prior to 16.04?

[chives (mra+ubuntu)]

I only became aware of this issue after I recently upgraded to 16.04. All I can say is that automatic screen rotation did NOT work in 15.10. I'm not sure if this was already implemented in Ubuntu Gnome 15.10. I cannot give any comments on the output of `gdbus introspect [...]` for any version before 16.04.