[OnePlus 3 & 3T Cross Device Development] :
Location is needed to compute sunrise/sunset. It has been the same for LD. If no "last known location" is set (i.e. wiped or too old) a location service is needed to compute sunrise/sunset for the location you are at.

Like my niche stated in the age of 7: "If you have no üroblem, you have no problem." ;)

Just to get this straight: With waiting till screen goes off +10s works without PIS 25 times?

BTW: I don't think waiting works because of mobile data or wifi is up, nor do I belive that keeping the display on solves PIS - it's just waiting since the os is up t handle the login.

I've spended the last night with this log: https://xdaforums.com/showpost.php?p=79219741&postcount=1375

Be aware that this is from op5t and may lead to something not relevant for op3/t!

[MENTION=1763460]Dirk[/MENTION] is suspecting

03-28 23:34:13.106 1293 1419 W ServiceManagement: Waited one second for vendor.lineage.livedisplay@2.0::IPictureAdjustment/default. Waiting another...

to be the culprit. This is a follow-up error of

03-28 23:34:12.099 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IAdaptiveBacklight/default in either framework or device manifest.
03-28 23:34:12.100 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IColorEnhancement/default in either framework or device manifest.
03-28 23:34:12.100 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IAutoContrast/default in either framework or device manifest.
03-28 23:34:12.100 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IDisplayColorCalibration/default in either framework or device manifest.
03-28 23:34:12.101 1293 1419 I android_os_HwBinder: HwBinder: Starting thread pool for default::vendor.lineage.livedisplay@2.0::IDisplayModes
03-28 23:34:12.102 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IReadingEnhancement/default in either framework or device manifest.
03-28 23:34:12.104 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IColorBalance/default in either framework or device manifest.
03-28 23:34:12.105 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::ISunlightEnhancement/default in either framework or device manifest.
03-28 23:34:12.106 1293 1419 I ServiceManagement: getService: Trying again for vendor.lineage.livedisplay@2.0::IPictureAdjustment/default...

I've no idea, why this happens. And it happens for more hwservices:

grep "in either framework or device manifest." /mnt/export/data/Downloads/incoming/logcat.txt
03-28 23:34:01.206 594 594 W hwservicemanager: getTransport: Cannot find entry android.hardware.soundtrigger@2.0::ISoundTriggerHw/default in either framework or device manifest.
03-28 23:34:01.337 594 594 W hwservicemanager: getTransport: Cannot find entry android.hardware.ir@1.0::IConsumerIr/default in either framework or device manifest.
03-28 23:34:01.649 594 594 W hwservicemanager: getTransport: Cannot find entry android.hardware.camera.provider@2.4::ICameraProvider/external/0 in either framework or device manifest.
03-28 23:34:01.654 594 594 W hwservicemanager: getTransport: Cannot find entry android.hardware.oemlock@1.0::IOemLock/default in either framework or device manifest.
03-28 23:34:01.890 594 594 W hwservicemanager: getTransport: Cannot find entry android.hardware.usb.gadget@1.0::IUsbGadget/default in either framework or device manifest.
03-28 23:34:01.940 594 594 W hwservicemanager: getTransport: Cannot find entry android.hardware.contexthub@1.0::IContexthub/default in either framework or device manifest.
03-28 23:34:02.180 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.trust@1.0::IUsbRestrict/default in either framework or device manifest.
03-28 23:34:02.192 594 594 W hwservicemanager: getTransport: Cannot find entry android.hardware.weaver@1.0::IWeaver/default in either framework or device manifest.
03-28 23:34:02.192 594 594 W hwservicemanager: getTransport: Cannot find entry android.hardware.authsecret@1.0::IAuthSecret/default in either framework or device manifest.
03-28 23:34:04.272 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.touch@1.0::IKeyDisabler/default in either framework or device manifest.
03-28 23:34:04.330 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.touch@1.0::IStylusMode/default in either framework or device manifest.
03-28 23:34:04.330 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.touch@1.0::IGloveMode/default in either framework or device manifest.
03-28 23:34:05.444 594 594 W hwservicemanager: getTransport: Cannot find entry android.hardware.wifi.offload@1.0::IOffload/default in either framework or device manifest.
03-28 23:34:05.562 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.trust@1.0::IUsbRestrict/default in either framework or device manifest.
03-28 23:34:12.099 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IAdaptiveBacklight/default in either framework or device manifest.
03-28 23:34:12.100 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IColorEnhancement/default in either framework or device manifest.
03-28 23:34:12.100 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IAutoContrast/default in either framework or device manifest.
03-28 23:34:12.100 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IDisplayColorCalibration/default in either framework or device manifest.
03-28 23:34:12.102 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IReadingEnhancement/default in either framework or device manifest.
03-28 23:34:12.104 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::IColorBalance/default in either framework or device manifest.
03-28 23:34:12.105 594 594 W hwservicemanager: getTransport: Cannot find entry vendor.lineage.livedisplay@2.0::ISunlightEnhancement/default in either framework or device manifest.

I've no idea why this happens. Even more confusing is that commenting out(!) livedisplay from the device manifest (yes, it's there!) is said to help. If the livedisplay wouldn't be there, and adding it solves PIS would make much more sense according to the log entries...

What can be seen is that not only LD, but a bunch of hwservices is broken, when PIS shows up.

The longer I look at this, it seems more amd more probable to me, we have a timing problem hitting once in a while (on op3/t - on op5t [MENTION=5092836]Dirk H[/MENTION]as reported several PIS in a row).

The bootup process is slightly differnt (timing and order) if caches are wiped, or the device is powered off and on instead of rebooting. If it's an timing problem in the boot process, that would explain, why different things (wiping, waiting, updating) show different results sending us to belive that one of this actions trigger/solve PIS.

Booting after an update is different from booting after wipe, which is different from just rebooting. All three behave slightly different, with power off/on instead of warm reset...

After spending many hours on the log, I still have no idea what's the cause and how to solve this.

I love people with mathematical, statistical and logical knowledge! Most of the time I reboot from twrp after flashing a rom. Second most is rebooting from twrp after flashing a fw package. I barely just reboot the rom from the rom. If I would expirience PIS, it's obvious that I mostly expirience it after updating... There are three important points on statistics: sample size, sample size and sample size... ;)

I can't find any traces for this in the log. But: everything that chanhes the timing/order of the boot process, may trigger or avoid PIS... I understand every dev keeping quiet after working throgh the log...

Maybe. On the other hand it should be reproducable with fast unlocking... It's a pain in the arse to track this down. ATM I'm out of ideas why the hardware service isn't finding the device manifest entries, though they are present. Sorry folks, but I think I'm no help on this.

Also keep in mind, that the log I've examined is from op5t. It may be caused by something completely different - though not very probable. Imagine two car accidents looking absolutely identically: both hit a tree in a turn without any breaking traces. The first one had a broken break, the second driver was just unconscious. With only the op5t log making conclusions for our op3/t, would be like concluding from the first car, that the second has broken breaks, too...