Status Update
Comments
ra...@gmail.com <ra...@gmail.com> #2
Branch: androidx-main
commit 2db6d01af84b5752190c6dd28cdea12500b701cb
Author: Charcoal Chen <charcoalchen@google.com>
Date: Fri Dec 23 10:15:10 2022
Fix JPEG image corruption issue if writing Exif location data on some Samsung Android 12 devices
This issue can be avoided in CameraX side by skipping the unnecessary Exif data copy. But there should still be some unknown reason in ExifInterface or these problematic devices to cause the issue.
Relnote: "Fixed JPEG image corruption issue if writing Exif location data on some Samsung Android 12 devices."
Bug: 263289024
Test: ImageCaptureTest
Change-Id: Ib70862aa6e654f06b9358e3f92bbb98c86cb9caf
M camera/camera-core/src/main/java/androidx/camera/core/impl/utils/Exif.java
M camera/integration-tests/coretestapp/src/androidTest/java/androidx/camera/integration/core/ImageCaptureTest.kt
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #3
Thanks for reporting, i can use the example app to reproduce the problem. I saved the corrupted file and pulled it off the device and ran it through exiftool
, which complained (it doesn't complain as loudly about the source file, just some technically out-of-order tags):
$ exiftool -v2 editedFile.jpg
ExifToolVersion = 12.52
FileName = editedFile.jpg
Directory = .
FileSize = 433785
FileModifyDate = 1678109782
FileAccessDate = 1678109782
FileInodeChangeDate = 1678109782
FilePermissions = 33184
FileType = JPEG
FileTypeExtension = JPG
MIMEType = image/jpeg
Warning = [minor] Skipped unknown 617 bytes after JPEG APP1 segment
JPEG APP1 (46 bytes):
ExifByteOrder = II
Warning = Short directory size for IFD0 (missing 150 bytes)
| Warning = Bad IFD0 directory
Warning = [minor] Skipped unknown 917 bytes after JPEG NULL segment
JPEG SOI
JPEG APP0 (14 bytes):
+ [BinaryData directory, 9 bytes]
| JFIFVersion = 1 1
| - Tag 0x0000 (2 bytes, int8u[2])
| ResolutionUnit = 0
| - Tag 0x0002 (1 bytes, int8u[1])
| XResolution = 1
| - Tag 0x0003 (2 bytes, int16u[1])
| YResolution = 1
| - Tag 0x0005 (2 bytes, int16u[1])
| ThumbnailWidth = 0
| - Tag 0x0007 (1 bytes, int8u[1])
| ThumbnailHeight = 0
| - Tag 0x0008 (1 bytes, int8u[1])
JPEG DQT (65 bytes):
JPEG DQT (65 bytes):
JPEG SOF0 (15 bytes):
ImageWidth = 512
ImageHeight = 384
EncodingProcess = 0
BitsPerSample = 8
ColorComponents = 3
YCbCrSubSampling = 2 1
JPEG DHT (29 bytes):
JPEG DHT (179 bytes):
JPEG DHT (29 bytes):
JPEG DHT (179 bytes):
JPEG SOS
ga...@gmail.com <ga...@gmail.com> #4
The size of the JPEG APP1
segment looks wrong in the edited file (from exiftool
):
JPEG APP1 (46 bytes):
Compared to the original file:
JPEG APP1 (65279 bytes):
In binary this difference is visible in the 5th/6th byte of each file (from hexdump -C
). The first 4 bytes are a JPEG marker (0xFF
), a JPEG SOI (start of image, 0xd8
), another marker and an APP1 (0xe1
), followed by 2 bytes indicating the size of the APP1 segment.
Edited image:
ff d8 ff e1 00 30
Original image:
ff d8 ff e1 ff 01
Looking into why ExifInterface
is writing out the wrong APP1 size, I turned on
$ adb shell setprop log.tag.ExifInterface VERBOSE
And now it becomes a bit more obvious (this logging is from
saveJpegAttributes starting with (inputStream: java.io.BufferedInputStream@4fba9e8, outputStream: java.io.BufferedOutputStream@e5c3801)
index: 0, offsets: 8, tag count: 15, data sizes: 81, total size: 65584
65584
(0x10030
) is greater than the max 16-bit unsigned value (2^16 = 65536
), so when we ByteOrderedDataOutputStream.writeUnsignedShort
writeShort((short) val)
) truncates to the lower two bytes (0x0030
) - and this gets written out to the file and then breaks everything.
I think this likely only affects files that are very close to the 2^16
threshold, and the act of 'copying' all the EXIF attributes over probably reformats some of them just enough to take up slightly more bytes.
I'm not sure what is supposed to happen when a JPEG APP1 segment gets larger than 2^16
bytes, I need to dig a bit further into that part.
bl...@gmail.com <bl...@gmail.com> #5
Actually thinking about it more, it's not obvious to me why the APP1
segment of the original image is so large either - looking in exiftool
it doesn't seem to contain any particularly enormous fields, so I can't really see where 65kB comes from.
ma...@gmail.com <ma...@gmail.com> #6
re APP1
segment is so large, I missed the thumbnail the first time, which takes up a significant chunk (64kB):
+ [IFD1 directory with 15 entries]
| 0) ImageHeight = 384
| - Tag 0x0101 (4 bytes, int32u[1]):
| 0323: 80 01 00 00 [....]
| 1) Orientation = 6
| - Tag 0x0112 (2 bytes, int16u[1]):
| 032f: 06 00 [..]
| Warning = Tag ID 0x0103 Compression out of sequence in IFD1
| 2) Compression = 6
| - Tag 0x0103 (2 bytes, int16u[1]):
| 033b: 06 00 [..]
| 3) ThumbnailOffset = 1273
| - Tag 0x0201 (4 bytes, int32u[1]):
| 0347: f9 04 00 00 [....]
| 4) ThumbnailLength = 64000
| - Tag 0x0202 (4 bytes, int32u[1]):
| 0353: 00 fa 00 00 [....]
| Warning = Tag ID 0x010f Make out of sequence in IFD1
sr...@gmail.com <sr...@gmail.com> #7
APP1
:
Exif metadata are restricted in size to 64 kB in JPEG images because according to the specification this information must be contained within a single JPEG APP1 segment.
Charcoal: Do you know if CameraX is deciding how large to make the thumbnail in this case, or is this happening lower down in the device? Taking up 64,000 bytes doesn't leave much space for the rest of the Exif data.
Related thread I found (also complaining about a Samsung device, but from 2013...):
I experimented to see what exiftool
does now when the APP1
segment gets too large, and it looks like they just add a second APP1
segment and call it 'multi-segment EXIF` (I have no idea how well supported this is):
$ exiftool -UserComment="abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz" b-263747161_original.jpg
Warning: [minor] File contains multi-segment EXIF - b-263747161_original.jpg
1 image files updated
$ exiftool -v3 b-263747161_original.jpg
ExifToolVersion = 12.52
FileName = b-263747161_original.jpg
Directory = .
FileSize = 434075
FileModifyDate = 1678121141
FileAccessDate = 1678121141
FileInodeChangeDate = 1678121141
FilePermissions = 33184
FileType = JPEG
FileTypeExtension = JPG
MIMEType = image/jpeg
JPEG APP1 (65533 bytes):
0006: 45 78 69 66 00 00 49 49 2a 00 08 00 00 00 0d 00 [Exif..II*.......]
0016: 00 01 04 00 01 00 00 00 a0 05 00 00 01 01 04 00 [................]
0026: 01 00 00 00 38 04 00 00 0e 01 02 00 01 00 00 00 [....8...........]
0036: 00 00 00 00 0f 01 02 00 08 00 00 00 aa 00 00 00 [................]
0046: 10 01 02 00 09 00 00 00 b2 00 00 00 12 01 03 00 [................]
0056: 01 00 00 00 06 00 00 00 1a 01 05 00 01 00 00 00 [................]
0066: bc 00 00 00 1b 01 05 00 01 00 00 00 c4 00 00 00 [................]
[snip 65421 bytes]
Warning = [minor] File contains multi-segment EXIF
JPEG APP1 (71 bytes):
10007: 45 78 69 66 00 00 00 00 00 00 00 00 00 00 00 00 [Exif............]
10017: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [................]
10027: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [................]
10037: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [................]
10047: 00 00 00 00 00 00 00 [.......]
ExifByteOrder = II
Obviously the current ExifInterface
behaviour is very problematic (corrupting the image completely), but I'm not actually sure the best way to improve it. Some options I came up with:
- If the size of the
APP1
segment is larger than2^16
then just write the first2^16
bytes and hope. - Implement the same 'split segment' support that
exiftool
has. - Add logic to
ExifInterface
to resize a thumbnail to free up space in theAPP1
segment if it runs out (this seems too magical and could be very confusing for users). - Refuse to save a file in
ExifInterface.saveAttributes
if it results inAPP1
being larger than2^16
, either by silently not writing out (confusing) or throwing an exception (disruptive). - Add prioritisation of Exif tags, so when we run out of space we drop tags lowest-priority-first (very unlikely we can predict the 'correct' prioritisation such that users aren't annoyed/confused by the tags we decide to drop).
cw...@gmail.com <cw...@gmail.com> #8
Hi Ian,
Thanks for looking into the issue and provide the detailed analysis result.
About the question: Charcoal: Do you know if CameraX is deciding how large to make the thumbnail in this case, or is this happening lower down in the device? Taking up 64,000 bytes doesn't leave much space for the rest of the Exif data.
CameraX doesn't specify any thumbnail related capture request settings (
I'm curious about why this issue only happens when setting a FUSED location data but does not happen when setting a GPS location data? Does the FUSED location data in Exif actually occupy a little bit more size than GPS location data? So it causes the different result?
cw...@gmail.com <cw...@gmail.com> #9
I'm curious about why this issue only happens when setting a FUSED location data but does not happen when setting a GPS location data? Does the FUSED location data in Exif actually occupy a little bit more size than GPS location data? So it causes the different result?
Good question - I actually only got as far as playing with the image provided inside MyApplication-ExifLocationIssue.zip
, I didn't look at CameraXBasic-WriteFusedLocation.zip
, and as you noted in
ri...@gmail.com <ri...@gmail.com> #10
ph...@gmail.com <ph...@gmail.com> #11
Branch: androidx-main
commit c6bbc03f39f811ac546882880be46380cb31f5d5
Author: Ian Baker <ibaker@google.com>
Date: Tue Mar 07 11:09:08 2023
Throw an exception if trying to write a JPEG APP1 segment that's too large
jpeg_with_full_app_segment.jpg is an image taken with a Samsung A32
with a nearly-full APP1 segment due to a 64,000 byte thumbnail:
$ exiftool -v3 jpeg_with_exif_full_app1_segment.jpg
<snip>
JPEG APP1 (65072 bytes):
<snip>
| 5) ThumbnailLength = 64000
Bug: 263747161
Test: ./gradlew :exifinterface:exifinterface:connectedAndroidTest
Change-Id: Id421cd36d974ad4f29a2c6d6c730d99d8986d917
M exifinterface/exifinterface/build.gradle
M exifinterface/exifinterface/src/androidTest/java/androidx/exifinterface/media/ExifInterfaceTest.java
A exifinterface/exifinterface/src/androidTest/res/raw/jpeg_with_exif_full_app1_segment.jpg
M exifinterface/exifinterface/src/main/java/androidx/exifinterface/media/ExifInterface.java
wr...@gmail.com <wr...@gmail.com> #12
Are you sure it's an issue with the APP1 segment being too large with the FUSED location? I was thinking perhaps there's some issue with the length calculation that's happening as we were able to fix these images by just detecting the start of the jpeg image data and re-writing the length field based on that detection.
lb...@gmail.com <lb...@gmail.com> #13
Are you sure it's an issue with the APP1 segment being too large with the FUSED location? I was thinking perhaps there's some issue with the length calculation that's happening as we were able to fix these images by just detecting the start of the jpeg image data and re-writing the length field based on that detection.
This fix is consistent with the current failure mode of ExifInterface
when the APP1
segment gets 'too large' (before my change linked above in 0x10030
bytes to write to the APP1 segment, and ExifInterface
does two things:
- When writing the length of the APP1 segment it truncates this to
0x0030
- It writes all those
0x10030
bytes out, and then it writes the rest of the image.
A JPEG parser (I assume) comes along and reads the length of the APP1
segment (0x30
) and skips that many bytes, then expects to find JPEG data - but it's actually in the middle of the Exif and so it fails.
If you manually find the start of the JPEG data then you obviate both of the problems - and the image is 'fixed'.
lb...@gmail.com <lb...@gmail.com> #14
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.exifinterface:exifinterface:1.3.7
ma...@gmail.com <ma...@gmail.com> #15
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.exifinterface:exifinterface:1.4.0-alpha01
ka...@gmail.com <ka...@gmail.com> #16
ga...@gmail.com <ga...@gmail.com> #17
yo...@googlemail.com <yo...@googlemail.com> #18
What
Feature request
Uninstalled and re-installed home, working fine now
When
Time and frequency
Time when bug report was triggered: Jan 25, 2025 5:44 PM GMT+00:00
Where
Build and device data
- Build Number: google/husky_beta/husky:Baklava/BP22.250103.008/12932282:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Google Play services
com.google.android.gms
Version 250231035 (25.02.31 (260400-713337402))
System App (Bundled)
Android System WebView
com.google.android.webview
Version 694302342 (133.0.6943.23)
System App (Updated)
Network operator: vodafone UK
SIM operator: Vodafone
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
yo...@googlemail.com <yo...@googlemail.com> #19
Information redacted by Android Beta Feedback.
jp...@gmail.com <jp...@gmail.com> #20
ph...@gmail.com <ph...@gmail.com> #21
ap...@gmail.com <ap...@gmail.com> #22
Information redacted by Android Beta Feedback.
Have checked Google play services are up to date, tried asking Gemini to list all devices, Home app. Still broken on my P9P.
tx...@gmail.com <tx...@gmail.com> #23
What
Feature request
Google home app Crashes upon each launch attempt
Where
Build and device data
- Build Number: google/caiman_beta/caiman:Baklava/BP22.250103.008/12932282: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 250231035 (25.02.31 (260400-713337402))
System App (Bundled)
Android System WebView
com.google.android.webview
Version 683412233 (132.0.6834.122)
System App (Updated)
Network operator: Google Fi
SIM operator: Google Fi
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
tx...@gmail.com <tx...@gmail.com> #24
Information redacted by Android Beta Feedback.
yo...@googlemail.com <yo...@googlemail.com> #25
What
Feature request
No longer opening again
When
Time and frequency
Time when bug report was triggered: Jan 26, 2025 12:40 PM GMT+00:00
Where
Build and device data
- Build Number: google/husky_beta/husky:Baklava/BP22.250103.008/12932282:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Google Play services
com.google.android.gms
Version 250231035 (25.02.31 (260400-713337402))
System App (Bundled)
Android System WebView
com.google.android.webview
Version 694302342 (133.0.6943.23)
System App (Updated)
Network operator: vodafone UK
SIM operator: Vodafone
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
yo...@googlemail.com <yo...@googlemail.com> #26
Information redacted by Android Beta Feedback.
ka...@gmail.com <ka...@gmail.com> #27
ga...@gmail.com <ga...@gmail.com> #28
ma...@gmail.com <ma...@gmail.com> #29
ni...@gmail.com <ni...@gmail.com> #30
What
More information
Google Home doesn't open after the last update to android 16 beta 1
When
Time and frequency
Time when bug report was triggered: Jan 27, 2025 9:15 PM GMT+01:00
Where
Build and device data
- Build Number: google/bluejay_beta/bluejay:Baklava/BP22.250103.008/12932282:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Servicios de Google Play
com.google.android.gms
Version 250231035 (25.02.31 (260400-713337402))
System App (Bundled)
Android System WebView
com.google.android.webview
Version 677826233 (131.0.6778.262)
System App (Updated)
Network operator: Orange
SIM operator: Yoigo
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
ni...@gmail.com <ni...@gmail.com> #31
Information redacted by Android Beta Feedback.
oj...@gmail.com <oj...@gmail.com> #32
What
More information
Today I use Google assistant to turn light on and after that Google home no crashing. But this info is for today
When
Time and frequency
Time when bug report was triggered: Jan 28, 2025 8:25 PM GMT+01:00
Where
Build and device data
- Build Number: google/lynx_beta/lynx:Baklava/BP22.250103.008/12932282:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Usługi Google Play
com.google.android.gms
Version 250234035 (25.02.34 (260400-716794385))
System App (Updated)
Android System WebView
com.google.android.webview
Version 677826033 (131.0.6778.260)
System App (Updated)
Network operator: T-Mobile.pl
SIM operator: T-Mobile.pl
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
oj...@gmail.com <oj...@gmail.com> #33
Information redacted by Android Beta Feedback.
ap...@gmail.com <ap...@gmail.com> #34
gm...@gmail.com <gm...@gmail.com> #35
ha...@gmail.com <ha...@gmail.com> #36
sl...@gmail.com <sl...@gmail.com> #37
What
More information
Still crashing
When
Time and frequency
Time when bug report was triggered: Jan 28, 2025 10:44 PM GMT-05:00
Where
Build and device data
- Build Number: google/husky_beta/husky:Baklava/BP22.250103.008/12932282:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Debugging information
Google Play services
com.google.android.gms
Version 250234035 (25.02.34 (260400-716794385))
System App (Updated)
Android System WebView
com.google.android.webview
Version 677826033 (131.0.6778.260)
System App (Updated)
Network operator: XFINITY Mobile
SIM operator: Xfinity Mobile
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
sl...@gmail.com <sl...@gmail.com> #38
Information redacted by Android Beta Feedback.
cl...@hotmail.com <cl...@hotmail.com> #39
What
More information
It's working again since this morning, not sure why...
When
Time and frequency
Time when bug report was triggered: Jan 29, 2025 8:20 AM GMT+01:00
Where
Build and device data
- Build Number: google/panther_beta/panther:Baklava/BP22.250103.008/12932282: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 250234035 (25.02.34 (260400-716794385))
System App (Updated)
Android System WebView
com.google.android.webview
Version 694302342 (133.0.6943.23)
System App (Updated)
Network operator: 1GLOBAL
SIM operator: 1GLOBAL
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
cl...@hotmail.com <cl...@hotmail.com> #40
Information redacted by Android Beta Feedback.
ne...@gmail.com <ne...@gmail.com> #41
lb...@gmail.com <lb...@gmail.com> #42
fr...@gmail.com <fr...@gmail.com> #43
jo...@gmail.com <jo...@gmail.com> #44
What
More information
As of 6:10 pm, it seems to be working now. I didn't see any Google home app updates and didn't have any system updates.
Where
Build and device data
- Build Number: google/caiman_beta/caiman:Baklava/BP22.250103.008/12932282: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 250234035 (25.02.34 (260400-716794385))
System App (Updated)
Android System WebView
com.google.android.webview
Version 683412233 (132.0.6834.122)
System App (Updated)
Network operator: AT&T
SIM operator: AT&T
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
ga...@gmail.com <ga...@gmail.com> #45
an...@google.com <an...@google.com> #46
Information redacted by Android Beta Feedback.
to...@gmail.com <to...@gmail.com> #47
What
More information
The issue seems to have been fixed.
Where
Build and device data
- Build Number: google/oriole_beta/oriole:Baklava/BP22.250103.008/12932282: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 250363035 (25.03.63 (260400-721896117))
System App (Updated)
Android System WebView
com.google.android.webview
Version 683412233 (132.0.6834.122)
System App (Updated)
Network operator: Sky
SIM operator: Sky
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
to...@gmail.com <to...@gmail.com> #48
Information redacted by Android Beta Feedback.
to...@gmail.com <to...@gmail.com> #49
What
More information
The issue has been fixed.
Where
Build and device data
- Build Number: google/oriole_beta/oriole:Baklava/BP22.250103.008/12932282: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 250363035 (25.03.63 (260400-721896117))
System App (Updated)
Android System WebView
com.google.android.webview
Version 683412233 (132.0.6834.122)
System App (Updated)
Network operator: Sky
SIM operator: Sky
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
an...@google.com <an...@google.com> #50
Information redacted by Android Beta Feedback.
wd...@gmail.com <wd...@gmail.com> #51
What
More information
Bug report pop up out of the blue
Where
Build and device data
- Build Number: google/cheetah_beta/cheetah:Baklava/BP22.250103.008/12932282: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 250433035 (25.04.33 (260400-721828623))
System App (Updated)
Android System WebView
com.google.android.webview
Version 694303942 (133.0.6943.39)
System App (Updated)
Network operator: Spectrum
SIM operator: Spectrum
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
wd...@gmail.com <wd...@gmail.com> #52
Information redacted by Android Beta Feedback.
ks...@gmail.com <ks...@gmail.com> #53
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
The google files app stops accidentally when trying to open the pdf files. Other files open regularly.
Debugging information
Google Play services
com.google.android.gms
Version 250234035 (25.02.34 (260400-716794385))
System App (Updated)
Android System WebView
com.google.android.webview
Version 683416333 (132.0.6834.163)
System App (Updated)
Network operator: 019
SIM operator: 019
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
an...@google.com <an...@google.com> #54
Information redacted by Android Beta Feedback.
jb...@gmail.com <jb...@gmail.com> #55
What
More information
I also have noticed the Google home application crashing upon startup. The first time this happened, I installed the application, went through the setup, and it crashed upon finishing the setup.
When
Time and frequency
Time when bug report was triggered: Feb 7, 2025 11:51 AM GMT-07:00
Where
Build and device data
- Build Number: google/caiman_beta/caiman:Baklava/BP22.250103.008/12932282: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 250335035 (25.03.35 (260400-720971461))
System App (Updated)
Android System WebView
com.google.android.webview
Version 683416333 (132.0.6834.163)
System App (Updated)
Network operator: Verizon
SIM operator: Verizon
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
jb...@gmail.com <jb...@gmail.com> #56
Information redacted by Android Beta Feedback.
ti...@gmail.com <ti...@gmail.com> #57
What
More information
After latest beta app install. Figure print sensor doesn't work
Where
Build and device data
- Build Number: google/felix_beta/felix:Baklava/BP22.250103.008/12932282: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 250335035 (25.03.35 (260400-720971461))
System App (Updated)
Android System WebView
com.google.android.webview
Version 683416333 (132.0.6834.163)
System App (Updated)
Network operator: Spectrum
SIM operator: Spectrum
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
vv...@google.com <vv...@google.com> #58
Thank you for reporting this issue. We have a fix rolling out in an upcoming release.
kh...@gmail.com <kh...@gmail.com> #59
On Tue, Feb 11, 2025, 12:25 AM <buganizer-system@google.com> wrote:
Description
What
User experience
What type of issue is this?
Crash
What steps would let us observe this issue?
What did you expect to happen?
App to opem
What actually happened?
App crashed
What was the effect of this issue on your device usage, such as lost time or work?
Slight
When
Time and frequency
Time when bug report was triggered: Jan 23, 2025 9:11 PM GMT+00:00
How often has this happened?
Every time
Where
Component
Suggested component: <not visible> (1684638)
Build and device data
- Build Number: google/husky_beta/husky:Baklava/BP22.250103.008/12932282:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Related apps
Home
com.google.android.apps.chromecast.app
Version 30474443 (3.28.1.7)
Not system app
Debugging information
Google Play services
com.google.android.gms
Version 250231035 (25.02.31 (260400-713337402))
System App (Bundled)
Android System WebView
com.google.android.webview
Version 677826033 (131.0.6778.260)
System App (Updated)
Network operator: 3
SIM operator: 3
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