search

andreynovikov / trekarta

Simple, responsive map for your trek. You decide how to journey today, not the application!
https://trekarta.info
GNU General Public License v3.0
176 stars 25 forks source link

Stuck at splashscreen #176

Closed licaon-kter closed 2 years ago

licaon-kter commented 3 years ago

2021.04 (80) F-Droid, Android 11 AOSP

Logcat:

11:22:48.962  1540 30658 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=mobi.maptrek/.MainActivity bnds=[50,1839][171,1960]} from uid 10266
11:22:49.005  1540  1669 I ActivityManager: Start proc 23477:mobi.maptrek/u0a670 for pre-top-activity {mobi.maptrek/mobi.maptrek.MainActivity}
11:22:49.018 23477 23477 E mobi.maptrek: Not starting debugger since process cannot load the jdwp agent.
11:22:49.080 23477 23477 E MapTrek : mobi.maptrek.MapTrek Has SD card: null
11:22:49.103 23477 23477 E MapTrek : mobi.maptrek.MainActivity ES: null
11:22:49.103 23477 23477 E MapTrek : mobi.maptrek.MainActivity New ES: null
11:22:49.208 23477 23477 I chatty  : uid=10670(mobi.maptrek) identical 1 line
11:26:01.406  1540  2218 W InputDispatcher: Waiting because no window has focus but ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} may eventually add a window when it finishes starting up. Will wait for 5000ms
...me touching the screen...
11:26:03.972  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:26:04.244  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:26:04.460  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:26:04.717  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:26:04.941  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:26:05.189  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:26:05.447  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:26:05.687  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:26:06.408  1540  2218 I WindowManager: Input event dispatching timed out sending to application ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity.  Reason: ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} does not have a focused window
11:26:07.015 23477 23489 I mobi.maptrek: Thread[6,tid=23489,WaitingInMainSignalCatcherLoop,Thread*=0x72468bf2c0,peer=0x12dc01b0,"Signal Catcher"]: reacting to signal 3
11:26:07.015 23477 23489 I mobi.maptrek: 
11:26:07.121 23477 23489 I mobi.maptrek: Wrote stack traces to tombstoned
11:26:13.373  1540 23680 E ActivityManager: ANR in mobi.maptrek (mobi.maptrek/.MainActivity)
11:26:13.373  1540 23680 E ActivityManager: Reason: Input dispatching timed out (ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} does not have a focused window)
11:26:13.373  1540 23680 E ActivityManager: Parent: mobi.maptrek/.MainActivity
11:26:13.373  1540 23680 E ActivityManager:   1.4% 23477/mobi.maptrek: 1.1% user + 0.2% kernel / faults: 3138 minor 32 major
11:26:13.375  1540 23680 D ActivityManager: Completed ANR of mobi.maptrek in 6886ms, latency 0ms
11:59:27.032  1540  2218 W InputDispatcher: Waiting because no window has focus but ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} may eventually add a window when it finishes starting up. Will wait for 5000ms
...me touching the screen...
11:59:28.203  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:59:28.401  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:59:28.574  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:59:28.755  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:59:28.944  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:59:29.134  1540  2219 W InputDispatcher: Pruning the input queue because ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550} is unresponsive, but we have a responsive gesture monitor that may handle the event
11:59:29.434  1540  2219 I InputDispatcher: Pruning input queue because user touched a different application while waiting for ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550}
11:59:30.467  1540  2219 I InputDispatcher: Pruning input queue because user touched a different application while waiting for ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550}
11:59:31.069  1540  2219 I InputDispatcher: Pruning input queue because user touched a different application while waiting for ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550}
11:59:31.707  1540  2219 I InputDispatcher: Pruning input queue because user touched a different application while waiting for ActivityRecord{16e8854 u0 mobi.maptrek/.MainActivity t550}
11:59:37.229 23477 23492 W mobi.maptrek: Reducing the number of considered missed Gc histogram windows from 196 to 100

At one point Android asked me if I want to Force Close it or Wait

I eventually swiped it off in taskmanager.

Later I open it again... but now starts fine

albrechtd commented 2 years ago

Same effect for me, on a Google Pixel 4a running GrapheneOS w/ the latest version from F-Droid… Up to yesterday, on GrapheneOS based on Android 11, this happend ~ once in ten times starting trekarta. Just close it, start again, and it typically works. Annoying, but usable. Today, GrapheneOS updated to Android 12, and now its almost impossible to start trekarta: the startup screen appears, the device indicates that the GPS is activated, and its stuck. Closing and starting again usually again leads to the hanging splash screen; I sometimes have to re-try for ten times before it comes up, which renders trekarta more or less unusable. Any help or fix will be highly appreciated!