search

MM2-0 / Kvaesitso

A search-focused Android launcher
https://kvaesitso.mm20.de/
GNU General Public License v3.0
2.51k stars 86 forks source link

Bug: When returning to home screen from app home screen image is locked yet still usable in invisible layer beneath #961

Open paulvolk opened 4 months ago

paulvolk commented 4 months ago

background This is not a new issue and has been occurring since I started using this launcher. Its hard to explain and not clear on how to consistently repro but it happens 80% of the time I navigate to the launcher. I've even reset the launcher to default setting (by resetting in settings) with no solution.

Device: pixel 7 pro

Repro steps

  1. Boot phone
  2. Launcher works without issue
  3. Scroll slightly down to reveal widgets (or don't)
  4. Search for something and launch it (or execute search by hitting enter on the search bar)
  5. Lock phone while in app or let screen time out into locked state
  6. Unclock phone by entering code to find yourself in the lars open app
  7. Swipe up on bottom of screen to initiate home action
  8. Arrive at launcher
  9. ACTUAL RESULT: launcher visual state is fixed/frozen where last left off (in default or partially scrolled down to widgets). Swiping on screen does not change launcher scroll state. Launcher visual is static. However, the launcher is actually active despite no visual feedback. For example scrolling down to reveal app drawer causes haptic feedback bump when app drawer is revealed (however the app drawer is not visually present on the screen). Additionally tapping on the screen occasionally will launch an app despite the app not being visible to the user.
  10. EXPECTED RESULT: launcher scrolls normally and is visible to the user.

Solution to ACTUAL RESULT: user locks screen waits 1 to 2 seconds and then unlocks screen. Launcher now has returned to normal working condition.

zeaglee commented 3 months ago

I've been having this issue on a relatively recently factory reset (~2 weeks) stock pixel 7. If I return to the home screen using the home swipe I can see but can't interact with the launcher. The solution is to turn the phone on and off once or twice with the power button.

Edit: 1.32.1

raelefae commented 2 months ago

I'm experiencing the exact same problem on my Google Pixel 8 Pro with GrapheneOS, Kvaesitso v1.33.1-fdroid. The only way to solve it is the lock/unlock method above, or to force stop Kvaesitso and relaunch it.

MasterEuphemius commented 1 month ago

I'm also having this same issue on a Pixel 6a with GrapheneOS, Kvaesitso v1.33.1-fdroid but in earlier versions too.

cayhorstmann commented 2 weeks ago

I am having the same issue on a stock Pixel 8. Nothing special about it--no different OS, not rooted, only the launcher is not the default. Maybe 10% of the time, when I turn the screen on, the launcher is not showing. But tapping on where the buttons should be has an effect.

The only remedy is to turn the screen off and on again.

amadaluzia commented 1 week ago

Hey, I seem to be having this issue too on my Pixel 6 Pro on GrapheneOS. I am looking at logcat and there seems to fail during setting up the view and also cancels something related to animations (not 100%)

log:

--------- switch to events
11-14 13:01:04.483 26665 26665 I view_enqueue_input_event: [eventType=Motion - Cancel,action=de.mm20.launcher2.nightly/de.mm20.launcher2.ui.launcher.LauncherActivity]
11-14 13:01:04.494 26665 26665 I wm_on_top_resumed_lost_called: [Token=202992985,Component Name=de.mm20.launcher2.ui.launcher.LauncherActivity,Reason=topStateChangedWhenResumed]
11-14 13:01:05.063 26665 26665 I wm_on_paused_called: [Token=202992985,Component Name=de.mm20.launcher2.ui.launcher.LauncherActivity,Reason=performPause,time=0ms]
--------- switch to main
11-14 13:01:05.100 26665 26665 D VRI[LauncherActivity]: visibilityChanged oldVisibility=true newVisibility=false
--------- switch to events
11-14 13:01:05.111 26665 26665 I viewroot_draw_event: [window=VRI[LauncherActivity],event=Not drawing due to not visible. Reason=!mAppVisible && !mForceDecorViewVisibility]
11-14 13:01:05.115 26665 26665 I wm_on_stop_called: [Token=202992985,Component Name=de.mm20.launcher2.ui.launcher.LauncherActivity,Reason=STOP_ACTIVITY_ITEM,time=0ms]
--------- switch to main
11-14 13:01:05.232 26665 26665 D InsetsController: hide(ime(), fromIme=true)
--------- switch to events
11-14 13:01:05.238 26665 26748 I jank_cuj_events_begin_request: [CUJ Type=81,Unix Time Ns=1731589265238364s,Elapsed Time Ns=495012768057.915s,Uptime Ns=206186530335.944s,Tag=1@1@de.mm20.launcher2.nightly]
--------- switch to main
11-14 13:01:05.241 26665 26665 I ImeTracker: ch.protonmail.android:41334220: onCancelled at PHASE_CLIENT_ANIMATION_CANCEL
--------- switch to events
11-14 13:01:05.241 26665 26748 I jank_cuj_events_cancel_request: [CUJ Type=81,Unix Time Ns=1731589265241620s,Elapsed Time Ns=495012771314.182s,Uptime Time Ns=206186533592.292s]
11-14 13:01:05.241 26665 26748 I jank_cuj_events_end_request: [CUJ Type=81,Unix Time Ns=1731589265241684s,Elapsed Time Ns=495012771375.38s,Uptime Time Ns=206186533653.205s]
--------- switch to main
11-14 13:01:05.242 26665 26665 I ImeTracker: de.mm20.launcher2.nightly:f2d2c4e9: onRequestHide at ORIGIN_CLIENT reason HIDE_SOFT_INPUT_ON_ANIMATION_STATE_CHANGED fromUser false
11-14 13:01:05.242 26665 26665 I ImeTracker: de.mm20.launcher2.nightly:f2d2c4e9: onFailed at PHASE_CLIENT_VIEW_SERVED
11-14 13:01:11.484 26665 28294 D MM20    : Icon pack app.lawnchair.lawnicons is up to date
11-14 13:01:11.485 26665 28294 D MM20    : Icon pack com.donnnno.arcticons.you is up to date
11-14 13:01:11.486 26665 28294 D MM20    : Icon pack app.lawnchair.lawnicons is up to date
amadaluzia commented 1 week ago

Found another oddity regarding this, if you use the move to last app gesture then it opens the 2nd most recent app, using the next most recent app gesture will go back to the last used app before that.

cayhorstmann commented 1 week ago

Another symptom that happened to me repetedly: Sometimes, the launcher buttons display, but they don't work. The clock shows but doesn't display the current time. For example, the digital clock on the top border may display 10:26, and the analog clock from Kvaesito shows 10:12.