Assigned
Status Update
Comments
ma...@google.com <ma...@google.com>
ma...@google.com <ma...@google.com> #2
Thanks for the feedback on the emulator. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps and as much as possible of the following information:
1. Emulator version
2. Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -show-kernel” and send the resulting logs
3. Any relevant Logcat logs
4. The results of running “adb shell top” in the command line.
For more information on what’s needed and how to obtain this information please read the guide athttps://developer.android.com/studio/report-bugs#emulator-bugs .
1. Emulator version
2. Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -show-kernel” and send the resulting logs
3. Any relevant Logcat logs
4. The results of running “adb shell top” in the command line.
For more information on what’s needed and how to obtain this information please read the guide at
mi...@gmail.com <mi...@gmail.com> #3
Android Studio Ladybug Feature Drop 2024.22
Am Fr., 7. März 2025 um 16:08 Uhr schrieb <buganizer-system@google.com>:
Am Fr., 7. März 2025 um 16:08 Uhr schrieb <buganizer-system@google.com>:
ma...@google.com <ma...@google.com>
pa...@etnetera.cz <pa...@etnetera.cz> #4
Hi Stean, the file you attached shows
INFO | Boot completed in 62411 ms
Did the Emulator work for you when you started from the command line? Could you also attach idea.log (in Android Studio, Help > Show Log) please.
Description
I/chatty: uid=10379(com.com.project) androidmapsapi- identical 61 lines
I/Counters: exceeded sample count in FrameTime
Just a "FrameTime" when this will get fixed. We're 100% positive you're aware of this tremendous, annoying bug that's been around for a month+. Thanks.
What steps will reproduce the problem?
1. Using Google Maps SDK for Android
2. Checking the RUN (Alt+4, NOT Alt+f4)
Also add the following details:
- Device (and version of Android) you have verified this issue on: Google Pixel 3 XL
- Google Play Services client library version: the newest
- Google Play Services version on the device: the newest
- Android SDK Version: the newest
- Was this working correctly on a previous version of Google Play Services?
(If yes, which client library and SDK version?)
Yes. I don't know. It's probably on the API side of things...
Also attach screenshots, sample code and optionally an APK if possible.
If the problem exhibits itself in a released version of your app on the
Play Store, optionally provide a link to the app, and explain how to
reproduce the issue in the app.