Fixed
Status Update
No update yet.
Comments
dc...@gmail.com
dc...@gmail.com
Didn't see this in the last month. Please close it.
st...@google.com
st...@google.com
Thanks - please respond to this bug thread if you see it again.
dc...@gmail.com
I've also seen this problem when displaying a map on a SamSung SII. I had no GPS fix at the time, not sure if that is important. It happened both when initially displaying a map and then on onResume.
W/dalvikvm( 5284): threadid=34: thread exiting with uncaught exception (group=0x4001e578)
I/WindowOrientationListener( 2715): orientation = 352.51413 Tilt = 50.829815 -- 0 , 6 , 7
E/ ( 2715): Dumpstate > /data/log/dumpstate_app_error
E/AndroidRuntime( 5284): FATAL EXCEPTION: GLThread 42
E/AndroidRuntime( 5284): java.lang.NullPointerException
E/AndroidRuntime( 5284): at java.nio.ReadWriteDirectByteBuffer.put(ReadWriteDirectByteBuffer.java:201)
E/AndroidRuntime( 5284): at java.nio.IntToByteBufferAdapter.put(IntToByteBufferAdapter.java:206)
E/AndroidRuntime( 5284): at maps.aa.i.e(Unknown Source)
E/AndroidRuntime( 5284): at maps.aa.i.d(Unknown Source)
E/AndroidRuntime( 5284): at maps.ab.ao.a(Unknown Source)
E/AndroidRuntime( 5284): at maps.ab.ax.a(Unknown Source)
E/AndroidRuntime( 5284): at maps.as.aw.a(Unknown Source)
E/AndroidRuntime( 5284): at maps.w.g.a(Unknown Source)
E/AndroidRuntime( 5284): at maps.w.g.b(Unknown Source)
E/AndroidRuntime( 5284): at maps.q.p.l(Unknown Source)
E/AndroidRuntime( 5284): at maps.q.p.run(Unknown Source)
W/dalvikvm( 5284): threadid=34: thread exiting with uncaught exception (group=0x4001e578)
I/WindowOrientationListener( 2715): orientation = 352.51413 Tilt = 50.829815 -- 0 , 6 , 7
E/ ( 2715): Dumpstate > /data/log/dumpstate_app_error
E/AndroidRuntime( 5284): FATAL EXCEPTION: GLThread 42
E/AndroidRuntime( 5284): java.lang.NullPointerException
E/AndroidRuntime( 5284): at java.nio.ReadWriteDirectByteBuffer.put(ReadWriteDirectByteBuffer.java:201)
E/AndroidRuntime( 5284): at java.nio.IntToByteBufferAdapter.put(IntToByteBufferAdapter.java:206)
E/AndroidRuntime( 5284): at maps.aa.i.e(Unknown Source)
E/AndroidRuntime( 5284): at maps.aa.i.d(Unknown Source)
E/AndroidRuntime( 5284): at maps.ab.ao.a(Unknown Source)
E/AndroidRuntime( 5284): at maps.ab.ax.a(Unknown Source)
E/AndroidRuntime( 5284): at maps.as.aw.a(Unknown Source)
E/AndroidRuntime( 5284): at maps.w.g.a(Unknown Source)
E/AndroidRuntime( 5284): at maps.w.g.b(Unknown Source)
E/AndroidRuntime( 5284): at maps.q.p.l(Unknown Source)
E/AndroidRuntime( 5284): at maps.q.p.run(Unknown Source)
vv...@google.com
Still seeing this issue (very frequently). I have a very similar stack trace too.
Description
What
User experience
What type of Android issue is this?
Bluetooth
What steps would let us observe this issue?
What did you expect to happen?
It was fixed in last OTA QPR1 BETA 2 but now it's broken again.
What actually happened?
I upgraded to the latest Android 15 QPR2 Beta 1 for my Pixel 9 Pro XL today and after installing my Libre 3 Plus glucose sensor is not reading.
What was the effect of this issue on your device usage, such as lost time or work?
None - device worked normally
Additional comments
All my other Bluetooth devices work such as Pixel buds, OnePlus watch etc but not my glucose monitor I wear on my arm.
When
Time and frequency
When did this happen?
Nov 12, 2024 3:45 PM GMT-06:00
How often has this happened?
Frequently
Where
Component
Suggested component: <not visible> (1630575)
Build and device data
- Build Number: google/komodo_beta/komodo:15/BP11.241025.006/12620009:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 244433036 (24.44.33 (260408-694629214))
System App (Updated)
Android System WebView
com.google.android.webview
Version 677803942 (131.0.6778.39)
System App (Updated)
Network operator: Verizon
SIM operator: Verizon
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)https://developer.android.com/preview/feedback#feedback-app .
To learn more about our feedback process, please visit