tanujnotes / Olauncher

Minimal AF Launcher for Android. Reduce your screen time. Daily wallpapers.
https://play.google.com/store/apps/details?id=app.olauncher
GNU General Public License v3.0
1.95k stars 206 forks source link

[Bug] Random crash after hitting home button from another application #480

Open rottenwheel opened 2 months ago

rottenwheel commented 2 months ago

Got a crash log too. As a side note, from time to time, I notice the recents/apps in background button breaks: tapping on it doesn't trigger any action. The only solution I've found is to reboot my device, though I haven't tried force closing OLauncher to see if the causing agent is Olauncher or something else.

Regardless, that doesn't seem related to hitting home button and getting a black screen, then a force close message with the log...

type: ANR
osVersion: google/panther/panther:14/AP2A.240605.024/2024062000:user/release-keys
package: app.olauncher:78
process: app.olauncher
installer: org.fdroid.fdroid

activity: app.olauncher/.MainActivity
cause: ANR Input dispatching timed out (Application does not have a focused window).
info: ANR in app.olauncher (app.olauncher/.MainActivity)
PID: 16503
Reason: Input dispatching timed out (Application does not have a focused window).
Parent: app.olauncher/.MainActivity
ErrorId: 7bf23f40-cd26-45b4-9ed1-dc315168704b
Frozen: false
Timestamp: 2024-06-24 18:10:31.542-0500
Load: 3.29 / 3.06 / 3.34
----- Output from /proc/pressure/memory -----
some avg10=2.08 avg60=1.60 avg300=1.45 total=1173053831
full avg10=1.16 avg60=1.11 avg300=0.97 total=777141728
----- End output from /proc/pressure/memory -----
----- Output from /proc/pressure/cpu -----
some avg10=8.69 avg60=7.35 avg300=7.79 total=5122364913
----- End output from /proc/pressure/cpu -----
----- Output from /proc/pressure/io -----
some avg10=1.15 avg60=0.87 avg300=1.01 total=963673672
full avg10=0.81 avg60=0.59 avg300=0.67 total=667339087
----- End output from /proc/pressure/io -----

CPU usage from 70198ms to -16ms ago (2024-06-24 18:09:21.309 to 2024-06-24 18:10:31.523):
  28% 21993/chat.simplex.app: 24% user + 4.4% kernel / faults: 42270 minor 518 major
  19% 1523/system_server: 12% user + 6.8% kernel / faults: 42364 minor 1144 major
  18% 541/surfaceflinger: 11% user + 6.3% kernel / faults: 452 minor 9 major
  13% 3678/com.touchtype.swiftkey: 10% user + 2.6% kernel / faults: 28112 minor 1289 major
  11% 9554/de.spiritcroc.riotx.testing.foss: 8.5% user + 2.7% kernel / faults: 38983 minor 1738 major
  6.5% 544/android.hardware.composer.hwc3-service.pixel: 4.1% user + 2.3% kernel / faults: 35 minor 29 major
  6.4% 2075/com.android.systemui: 4.4% user + 2% kernel / faults: 2544 minor 128 major
  4.7% 16070/org.telegram.messenger.web: 3.4% user + 1.2% kernel / faults: 8027 minor 662 major
  4.1% 1099/irq/502-fts_ts: 0% user + 4.1% kernel
  3.7% 1326/twoshay: 2.7% user + 0.9% kernel / faults: 2 minor 2 major
24% TOTAL: 15% user + 7% kernel + 0.5% iowait + 1.2% irq + 0.5% softirq
CPU usage from 85ms to 605ms later (2024-06-24 18:10:31.592 to 2024-06-24 18:10:32.112):
  124% 1523/system_server: 62% user + 62% kernel / faults: 5737 minor 469 major
    40% 1682/Signal Catcher: 21% user + 19% kernel
    40% 22330/AnrAuxiliaryTas: 19% user + 21% kernel
    7.1% 1754/android.bg: 0% user + 7.1% kernel
    4.7% 16202/binder:1523_1D: 4.7% user + 0% kernel
    2.3% 1694/binder:1523_2: 0% user + 2.3% kernel
    2.3% 1724/android.io: 0% user + 2.3% kernel
    2.3% 1725/android.display: 2.3% user + 0% kernel
    2.3% 1726/android.anim: 2.3% user + 0% kernel
    2.3% 1961/StorageManagerS: 0% user + 2.3% kernel
    2.3% 2041/BackgroundInsta: 2.3% user + 0% kernel
    2.3% 2044/StatsCompanionS: 0% user + 2.3% kernel
    2.3% 3837/binder:1523_B: 2.3% user + 0% kernel
    2.3% 16338/binder:1523_1F: 2.3% user + 0% kernel
    2.3% 16339/binder:1523_20: 2.3% user + 0% kernel
    2.3% 22329/AnrConsumer: 0% user + 2.3% kernel
  72% 93/kswapd0: 0% user + 72% kernel
  96% 22178/com.skemailmobileapp: 92% user + 3.8% kernel / faults: 677 minor 4 major
    88% 22227/mqt_js: 88% user + 0% kernel
    3.8% 22229/BMScavenger: 0% user + 3.8% kernel
  20% 541/surfaceflinger: 14% user + 6.2% kernel / faults: 32 minor
    6.2% 541/surfaceflinger: 6.2% user + 0% kernel
    4.1% 582/binder:541_2: 2% user + 2% kernel
    2% 584/RenderEngine: 2% user + 0% kernel
    2% 652/TimerDispatch: 2% user + 0% kernel
    2% 723/surfaceflinger: 2% user + 0% kernel
    2% 1938/binder:541_5: 0% user + 2% kernel
  21% 2507/com.android.launcher3: 18% user + 2.6% kernel / faults: 1337 minor 52 major
    13% 2507/droid.launcher3: 13% user + 0% kernel
    5.3% 15721/InsetsAnimation: 2.6% user + 2.6% kernel
    2.6% 3933/RenderThread: 2.6% user + 0% kernel
    2.6% 15718/TaskThumbnailIc: 2.6% user + 0% kernel
  11% 182/eh_comp_thread: 0% user + 11% kernel
  19% 16503/app.olauncher: 12% user + 6.4% kernel / faults: 809 minor 982 major
    16% 16522/Signal Catcher: 9.6% user + 6.4% kernel
  6.2% 544/android.hardware.composer.hwc3-service.pixel: 4.1% user + 2% kernel
    6.2% 649/binder:544_4: 4.1% user + 2% kernel
  4% 248/decon0_kthread: 0% user + 4% kernel
  4.9% 2075/com.android.systemui: 0% user + 4.9% kernel / faults: 2 minor
    2.4% 2193/wmshell.main: 0% user + 2.4% kernel
    2.4% 2289/RenderThread: 2.4% user + 0% kernel
  1.9% 13/rcuog/0: 0% user + 1.9% kernel
  1.9% 64/rcuop/6: 0% user + 1.9% kernel
  2% 475/logd: 2% user + 0% kernel
    2% 485/logd.writer: 2% user + 0% kernel
  2% 476/lmkd: 0% user + 2% kernel
    2% 476/lmkd: 0% user + 2% kernel
  2% 619/android.hardware.power-service.pixel-libperfmgr: 0% user + 2% kernel
    2% 619/android.hardwar: 2% user + 0% kernel
    2% 2957/NodeLooperThrea: 0% user + 2% kernel
  2.4% 1843/android.hardware.thermal-service.pixel: 0% user + 2.4% kernel / faults: 1 major
    2.4% 1849/FileWatcherThre: 0% user + 2.4% kernel
  3.3% 20624/kworker/6:1-memlat_wq: 0% user + 3.3% kernel
62% TOTAL: 30% user + 26% kernel + 3.2% iowait + 1.4% irq + 0.4% softirq
tanujnotes commented 2 months ago

If you haven't already, set the battery to Unrestricted for Olauncher and restart the device once. Let me know if it makes any difference.

rottenwheel commented 2 months ago

@tanujnotes When I go to Olauncher settings>App battery usage it says it is allowed for background usage and save battery is disabled. Is that what you mean?

tanujnotes commented 2 months ago

@rottenwheel could you post a screenshot? You need to figure out how to set the battery to Unrestricted (or No restriction, depending on the phone model).

rottenwheel commented 2 months ago

@rottenwheel could you post a screenshot? You need to figure out how to set the battery to Unrestricted (or No restriction, depending on the phone model).

IMG_20240626_154659.jpg

tanujnotes commented 2 months ago

@rottenwheel Tap on the 'Allow background usage' text and set it to Unrestricted on the next page. Then restart the phone once.

rottenwheel commented 2 months ago

@tanujnotes sneaky, that setting. Olauncher has been working much more reliably since, no sudden force closes, nor have I lost functionality of the recents button again. However, every now and then I'll get a full black screen after hitting home button, just navigation buttons and status bar working. It looks like it hangs there. I can only get out of there via recents or pulling status bar down, going into settings, then hitting home button works again. It's odd because it doesn't crash, nor shows me an Olauncher has stopped working message, force close it. Maybe if I let it sit for longer in the black screen?

Thanks for your fast responses.

rottenwheel commented 2 months ago

Yeah, unfortunately can confirm the random black screen problem with home button is still occurring, sometimes accompanied by the Olauncher isn't responding, force close or wait popup and I also noticed default launcher gets reset, as I'm asked which launcher I want to use after force closing the application.

tanujnotes commented 1 month ago

@rottenwheel Would you try these 2 things separately and report if it makes any difference -

  1. Turning off the auto keyboard Off from the settings
  2. Using a different keyboard app with auto keyboard On
rottenwheel commented 1 month ago

@rottenwheel Would you try these 2 things separately and report if it makes any difference -

  1. Turning off the auto keyboard Off from the settings
  2. Using a different keyboard app with auto keyboard On

Noted, on it. I am turning auto keyboard off first. For what it is worth what I've been getting the most of is, hit home screen from an application, screen turns fully black, nothing comes through. Either pull down notification bar, go to system settings by tapping on gear icon and then do home button again, this time it'd work ok, or press recents button, then home button would work. Not sure what's up.

I am very used to my daily driver keyboard application, but I'll see what I can do for 2 if 1 doesn't improve the situation the next few days. Will report back. Thanks.

Edit: black screen just happened again about 5-10 minutes after I turned auto keyboard setting off. Err...

rottenwheel commented 1 month ago

OK, turnin off auto keyboard did not help at all, if anything, I think it made it worse.

I am currently testing with a different keyboard application, will give it a day or two, if I can... It's tedious, too many mistakes. Used to daily driver.

rottenwheel commented 1 month ago

Can confirm it happens in both tested scenarios, much less often with a different keyboard application though.

Main is Swiftkey, alternative is FUTO.

rottenwheel commented 5 days ago

Any hints on this yet? Upgraded to v4.3.3 hoping for some improvement. 😅 Love the launcher!