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
Terminal spam with F/android.hardware.atrace@1.0-service(25128): Check failed: stat(tracefs_event_root_.c_str(), &st) == 0 tracefs
#94652
Comments
HI @nikhilbadyal, please share your output of flutter doctor -v
logs
|
Here is the relevant data you asked for flutter doctor -v
flutter run -v
|
@nikhilbadyal I ran a newly created flutter project on the master channel in Android studio and vscode but did not see those logs. Are you seeing those logs with a specific project or a newly created project too? flutter doctor -v
|
It happens with new created projects too. Running Gradle task 'assembleDebug'... |
@nikhilbadyal I can't really reproduce the issue.
Is this using adb via the command line? Are you seeing these logs when running via android studio or from the command prompt? flutter doctor -v
logs
|
It shouldn't matter ig. But as you asked it happens everytime. Whether i run from AS by pressing the debug icon or using simple windows cmd The command i use to connect my device is
Log with plain old windows CMD
By pressing the debug button in Android Studio/summary>
|
Thanks for the info |
In my case, this problem arises even when debugging via USB.
log while debugging over wi-fi
log while debugging via USB
|
I am using Redmi Note 5 and I get the same message in my logs. So far, it doesn't break anything that I'm aware of sha. |
i have the same problem on my Redmi Note 5 (whyred) running an Android 12 custom rom flutter doctor -v
I have tested my other devices running Android 7.1.1 and 10. they both work fine.
|
It runs fine with the oem software MIUI 12.0.2.0 running Android 9
|
Whenever i try to run flutter application. It spams the whole terminal with these lines.
and it only happens when i use
WIRELESS DEBUGGING
.Any fix or solution ?
The text was updated successfully, but these errors were encountered: