Assigned
Status Update
Comments
vi...@google.com <vi...@google.com> #2
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
lb...@gmail.com <lb...@gmail.com> #3
How fast would it be compared to JPG/PNG, for encoding/decoding?
jo...@gmail.com <jo...@gmail.com> #4
Encoding: depends on encode effort, but generally speaking faster than PNG, a bit slower than JPEG.
Decoding: a bit slower than PNG and JPEG (unless you use multithreading, then it can be faster).
Both encode and decode should be fast enough for most use cases on current phone cpus.
Decoding: a bit slower than PNG and JPEG (unless you use multithreading, then it can be faster).
Both encode and decode should be fast enough for most use cases on current phone cpus.
lb...@gmail.com <lb...@gmail.com> #5
@4 Interesting.
Thanks.
Thanks.
hm...@gmail.com <hm...@gmail.com> #6
For both opening in Webview and as a saved filetype with third party editors
ay...@gmail.com <ay...@gmail.com> #7
Would love to see this backported to older versions of Android/PXL phones too!
za...@gmail.com <za...@gmail.com> #8
Can't wait to have JXL supported on Android and being the new default. So much potential to push photography forward with features such as HDR, depth maps and better quality in a smaller size. Such exciting times to come.
lb...@gmail.com <lb...@gmail.com> #9
I hope it will be possible to easily support it for old Android versions.
Otherwise, it would take years to become popular...
Sadly I don't think you can add logic of decoding to the framework (BitmapFactory.decode... forms, and maybe others too), so this would be a challenging thing to have...
Otherwise, it would take years to become popular...
Sadly I don't think you can add logic of decoding to the framework (BitmapFactory.decode... forms, and maybe others too), so this would be a challenging thing to have...
ad...@gmail.com <ad...@gmail.com> #10
Any updates on this? 🍿👀
hm...@gmail.com <hm...@gmail.com> #11
100 Votes so far, yet Google blocked it on Chrome despite that request recieving almost 1000 Votes & hundreds of responses
Including by Facebook's Meta, Intel, Adobe, Image Hosting Services, Medical Imaging Developers etc etc even some of Google's own Team showed support for the format against their very company!
It would be a shame if it was blocked for Android too :/
Including by Facebook's Meta, Intel, Adobe, Image Hosting Services, Medical Imaging Developers etc etc even some of Google's own Team showed support for the format against their very company!
It would be a shame if it was blocked for Android too :/
ry...@gmail.com <ry...@gmail.com> #12
Was there no response or follow-up action then? And are all the issues about adding compatibility with JPEG-XL Metadata just DOA?
mo...@gmail.com <mo...@gmail.com> #13
This would be huge for devices with less flash memory. Even my 128GB Pixel fills up fast when taking photos. Just converting them losslessly to JPEG-XL would reduce their size by about 20%.
Google could save 20% cloud storage on Photos too. Going forward the savings would be even larger when converting lossless originals directly to JPEG-XL.
Google could save 20% cloud storage on Photos too. Going forward the savings would be even larger when converting lossless originals directly to JPEG-XL.
ay...@gmail.com <ay...@gmail.com> #14
Any news?
ad...@gmail.com <ad...@gmail.com> #15
Comment has been deleted.
ad...@gmail.com <ad...@gmail.com> #16
Seriously, this is a highly requested feature that has already had a lot of the work done for it
https://bugs.chromium.org/p/chromium/issues/detail?id=1178058
lb...@gmail.com <lb...@gmail.com> #18
Is there perhaps an easy-to-use Android library to decode such files ?
go...@gmail.com <go...@gmail.com> #19
Hi, is support for JPEG XL added to a roadmap? Is there any timeline for delivering this feature or any update. It would be great to reveal more details about it. Best regards /R.
al...@hotmail.com <al...@hotmail.com> #20
Wondering if this in in the works. The option to save photos directly to JXL from the camera app should be priority. Also, reducing cloud storage and internet bandwidth footprint is granted.
fo...@yahoo.com <fo...@yahoo.com> #21
+1
no...@gmail.com <no...@gmail.com> #22 Restricted+
Restricted+
Comment has been deleted.
de...@gmail.com <de...@gmail.com> #23
I have the same request. Please add support for JPEG XL (jxl) on Android devices. For photographers it is a highly usable feature/image codec.
Kind regards
Dennis Gruhn
Kind regards
Dennis Gruhn
ql...@gmail.com <ql...@gmail.com> #24
lb...@gmail.com <lb...@gmail.com> #25
I hope that if Google adds it, it should also decode&encode faster than all other formats that Android already supports.
va...@gmail.com <va...@gmail.com> #26
+1
Description
Android does not currently have out of the box encode/decode support for JPEG XL (image/jxl). It would be useful to add at least decode support, so e.g. image gallery applications can show these images. Encode support would be useful too for several common use cases: