-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application stuck at splash screen on a Xiaomi Mi Max 3 #475
Comments
LogCat: logcat.txt.bz2.zip |
Pastebin (truncated UTF-8 encoded, dos2unix treated (CRLF -> LF)): https://pastebin.com/F3v0Cha7 |
The SQLite flooding issue in an Android StackExchange issue https://android.stackexchange.com/questions/255630/which-process-floods-my-logs-with-sqlite-migration-error-and-how-can-i-cure-it |
Questions:
From the logs it seems that the Bluetooth scan got kicked off from the app, and the scanning is ongoing. There could be some permissions missing though. But the scanning should happen only after the initialization is over and the app is on the Find Devices starting screen and not on the splash screen. |
Possibly I'll release a custom APK build to Ati. The main modification would be to add many log statements which made it to the LogCat and help to determine what is really going on during the initialization. There's a package https://pub.dev/packages/logging_to_logcat, however I don't think it's even needed. According to https://stackoverflow.com/questions/58906977/flutter-app-print-statements-will-not-show-up-in-adb-logcat I'd need to just use regular
|
Hmmm, apparently 3 years ago we had the same problem: #120 I wonder if this is a regression, we really need to check those permissions. I don't see the same exception in the logcat tho. |
I opened a feature branch:
Release build: https://drive.google.com/file/d/1-e63W5Lvtg2fg8sLvaiRrn3UquAOXs9M/view?usp=drive_link |
With custom APKs I built Ati was not able to reproduce the issue. So it's a mystery so far. |
Ati also tried the stock beta install and that works now again. I wonder what was the cause. It couldn't be the Floor -> Isar migration (#269 #422), maybe the |
More details: Xiaomi Mi Max 3 (MIUI 11, Android 10).
Not sure if custom ROM or not.
Since the app doesn't start at all, there's no application specific log.
Ati extracted a Logcat, which shows an insane flood of some system component: looks like most probably the
hwservicemanager
tries to perform a schema and database migration, and it fails at the 24th step of 27, and it gets into an endless loop logging every single millisecond!And so on and on. However this is possibly not relevant to our problem, it just makes the read of the LogCat hard.
The text was updated successfully, but these errors were encountered: