Hi
Just upgraded to /e T 1.21. On /e S 1.17 one could sign in from the black startup screen by swiping rather than using the start button. This seems unavailable on T.
Am I missing something here?
Thanks
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
Just to be clear when I say ‘black startup screen’ I mean the screen that appears when one hovers ones hand over the device.
Device is 1.21-t-20240325389105-dev-river
I’d guess it’s somehow up to motoactions. Do you find them in the settings? something turned off that was enabled before? https://github.com/LineageOS/android_hardware_motorola/
Yep. Thanks that’s what I thought. Couldn’t find anything that refers to startup.
Is that software an addition to Android?
its term for "display activation on motion detection"is ‘peek display’ or ‘doze glimpse’ and is on Stock Rom inside Settings → Display → Peek Display - (docs)
It’s introduced via proprietary blobs at https://github.com/TheMuppets/proprietary_vendor_motorola/blob/lineage-19.1/sdm632-common/proprietary/product/etc/permissions/com.motorola.motodisplay.xml
The devices acknowledges its use at https://github.com/LineageOS/android_device_motorola_sdm632-common/blob/4ff3999/proprietary-files.txt#L473
But I don’t see where the package “com.motorola.motodisplay” itself was supplied in /e/-S / lineage-19.0 muppet … you can always read through the dependencies bugtrackers if there was some general overhaul / standardization kicking out that package.
Here’s the question to Nolen - https://old.reddit.com/r/LineageOS/comments/1711p93/motorola_peek_display_on_lineageos/
I have a stock sdm632 moto around to fetch the package if you want to add it by hand via adb root (could work, never tried). The permissions should still be in place for it to run
Thanks again for all the input
I’m not sure that package is going to help me. As mentioned I have the display options on the startup screen apart from the option to swipe to signin. I have to use the power button to open.
I kinda got the same thing in the end by swiping finger print.
cool. Just for completeness sake, in case anyone else is after this, that was the stockrom output when playing with it, indicating what packages are involved
10-05 19:44:25.816 10975 10975 I MotoDisplay: Acquiring partial wakelock MotoDisplayWakeLock for 500ms.
10-05 19:44:25.821 10975 10975 I MotoDisplay: Start logging time for trigger Type: GLANCE_GESTURE GlanceType: GLANCE_GESTURE_MOVEMENT
10-05 19:44:25.821 10975 10975 I MotoDisplay: Glance Sensor Event Gesture Type: 16
10-05 19:44:25.821 10975 10975 I MotoDisplay: pulse - trigger: Type: GLANCE_GESTURE GlanceType: GLANCE_GESTURE_MOVEMENT is pulsing: false is paused: false
10-05 19:44:25.821 10975 10975 I MotoDisplay: Acquiring partial wakelock MotoDisplayWakeLock for 500ms.
10-05 19:44:25.843 10975 10975 I MotoDisplay: isPulseAllowed: true
10-05 19:44:25.854 2362 8777 I MotoDisplayManager: MotoDisplayCallback triggerVirtualSensor
10-05 19:44:25.866 834 1552 W qti_sensors_hal: reportSingleEvent: NearBy 0, pData 54, highThd 550
10-05 19:44:25.873 837 2207 V MotSpeakerHelperProximity: updated mCurProximityState: FAR (5.000000)
10-05 19:44:25.873 837 2207 V MotSpeakerHelperProximity: ThreadLoop event mProximityState = FAR, previous FAR
10-05 19:44:25.873 834 1552 W qti_sensors_hal: reportSingleEvent: NearBy 0, pData 54, highThd 550
10-05 19:44:25.876 837 2207 V MotSpeakerHelperProximity: updated mCurProximityState: FAR (5.000000)
10-05 19:44:25.876 837 2207 V MotSpeakerHelperProximity: ThreadLoop event mProximityState = FAR, previous FAR
10-05 19:44:25.887 1744 1900 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
10-05 19:44:25.887 1744 1900 I WindowManager: Screen turning on...
10-05 19:44:25.892 2362 8777 V KeyguardViewMediator: notifyDrawn
10-05 19:44:25.892 1744 3479 D WindowManager: mKeyguardDelegate.ShowListener.onDrawn.
10-05 19:44:25.893 1744 1800 W WindowManager: Setting mKeyguardDrawComplete
10-05 19:44:25.910 1744 1900 V DisplayPowerController: Brightness [23] reason changing to: 'doze', previous reason: 'screen_off'.
10-05 19:44:25.912 904 904 D SurfaceFlinger: Setting power mode 2 on display 0
10-05 19:44:25.912 1744 1802 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
10-05 19:44:25.913 847 919 I SDM : DisplayBase::SetDisplayState: Set state = 1, display 0
10-05 19:44:25.926 834 1552 W qti_sensors_hal: reportSingleEvent: NearBy 0, pData 54, highThd 550
10-05 19:44:25.926 837 2207 V MotSpeakerHelperProximity: updated mCurProximityState: FAR (5.000000)
10-05 19:44:25.926 837 2207 V MotSpeakerHelperProximity: ThreadLoop event mProximityState = FAR, previous FAR
10-05 19:44:25.930 2362 2379 I MotoDisplayManager: MotoDisplayCallback setScreenBrightness<brightness>30
10-05 19:44:25.944 10975 10975 I MotoDisplay: Time elapsed since sensor trigger Type: GLANCE_GESTURE GlanceType: GLANCE_GESTURE_MOVEMENT is 123 ms
10-05 19:44:25.944 2362 2379 I MotoDisplayManager: MotoDisplayCallback setScreenBrightness<brightness>23
10-05 19:44:25.965 1744 1802 I WindowManager: All windows ready for display!
10-05 19:44:25.966 1744 1800 W WindowManager: Setting mWindowManagerDrawComplete
10-05 19:44:25.966 1744 1900 I DisplayPowerController: Unblocked screen on after 79 ms
This topic was automatically closed after 30 days. New replies are no longer allowed.