You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated ssiv lib with few visual bug fixes, quality enhancement and optimization then implemented it in my fork.
You can try new enhancements by installing and testing it here. If you like these enhancements and want to implement them in your app, I can open PRs! Let me know after you test it thoroughly.
Details:
Fixed a visual bug that affect Android/Google TV 11+ that result in part of image cut and obscure 10% of top reading screen and 10% of buttom screen at the same time, usually it dissapear only after clicking on back then continue but appear again after few reading minutes. This visual bug only affect webtoon reading mode in ATV11+. (On ssiv lib)
Speed up of "processing" when loading images on all reading modes. (On ssiv lib + app)
Made ARGB_8888 mode the default rendering reading mode (same exactly as 32bit reading mode setting) (on ssiv lib + app)
Tried to fix Skia engine visual bug that result in visual transparent tint colors on large long strip images (1400x10000 resolution or higher) but could only improve it partially and not fix the issue completely (will try to fix it in near future, refer to uploaded comparison for details) (on ssiv lib)
Increased default max zoom by 100% (2x) on both manga and webtoon mode (on app)
These are the current changes I made and tested, you can decide to implement it or not based on your preference and judgment.
PS: I will make it clear beforehand, I vibecoded these changes using Claude code, it works as intended so there should be no problem but just wanted to let you know, either way it's up to you to decide.
Acknowledgements
This is not a duplicate of an existing issue. Please look through the list of open issues or our project backlog before creating a new one.
I have updated ssiv lib with few visual bug fixes, quality enhancement and optimization then implemented it in my fork.
You can try new enhancements by installing and testing it here. If you like these enhancements and want to implement them in your app, I can open PRs! Let me know after you test it thoroughly.
Details:
Fixed a visual bug that affect Android/Google TV 11+ that result in part of image cut and obscure 10% of top reading screen and 10% of buttom screen at the same time, usually it dissapear only after clicking on back then continue but appear again after few reading minutes. This visual bug only affect webtoon reading mode in ATV11+. (On ssiv lib)
Speed up of "processing" when loading images on all reading modes. (On ssiv lib + app)
Made ARGB_8888 mode the default rendering reading mode (same exactly as 32bit reading mode setting) (on ssiv lib + app)
Tried to fix Skia engine visual bug that result in visual transparent tint colors on large long strip images (1400x10000 resolution or higher) but could only improve it partially and not fix the issue completely (will try to fix it in near future, refer to uploaded comparison for details) (on ssiv lib)
Increased default max zoom by 100% (2x) on both manga and webtoon mode (on app)
These are the current changed I made and tested, you can decide to implement it or not based on your preference and judgment.
PS: I will make it clear beforehand, I vibecoded these changes using Claude code, it works as intended so there should be no problem but just wanted to let you know, either way it's up to you to decide.
### Acknowledgements
* [x] This is not a duplicate of an existing issue. Please look through the list of [open issues](https://github.com/UsagiApp/UsagiApp/issues) or our [project backlog](https://github.com/orgs/UsagiApp/projects/3/views/2) before creating a new one.
I have updated ssiv lib with few visual bug fixes, quality enhancement and optimization then implemented it in my fork.
You can try new enhancements by installing and testing it here. If you like these enhancements and want to implement them in your app, I can open PRs! Let me know after you test it thoroughly.
Details:
Fixed a visual bug that affect Android/Google TV 11+ that result in part of image cut and obscure 10% of top reading screen and 10% of buttom screen at the same time, usually it dissapear only after clicking on back then continue but appear again after few reading minutes. This visual bug only affect webtoon reading mode in ATV11+. (On ssiv lib)
Speed up of "processing" when loading images on all reading modes. (On ssiv lib + app)
Made ARGB_8888 mode the default rendering reading mode (same exactly as 32bit reading mode setting) (on ssiv lib + app)
Tried to fix Skia engine visual bug that result in visual transparent tint colors on large long strip images (1400x10000 resolution or higher) but could only improve it partially and not fix the issue completely (will try to fix it in near future, refer to uploaded comparison for details) (on ssiv lib)
Increased default max zoom by 100% (2x) on both manga and webtoon mode (on app)
These are the current changed I made and tested, you can decide to implement it or not based on your preference and judgment.
PS: I will make it clear beforehand, I vibecoded these changes using Claude code, it works as intended so there should be no problem but just wanted to let you know, either way it's up to you to decide.
### Acknowledgements
* [x] This is not a duplicate of an existing issue. Please look through the list of [open issues](https://github.com/UsagiApp/UsagiApp/issues) or our [project backlog](https://github.com/orgs/UsagiApp/projects/3/views/2) before creating a new one.
Isn't it better to switch to my ssiv lib fork in your libs.versions.toml code rather than implementing it in your ssiv lib code? This way, you can easily revert and switch back to your ssiv lib in case you change your mind later or some bugs appear while keeping your ssiv code clean.
If you are certain and still want me to implement these changes anyway, then I will gladly do.
I have updated ssiv lib with few visual bug fixes, quality enhancement and optimization then implemented it in my fork.
You can try new enhancements by installing and testing it here. If you like these enhancements and want to implement them in your app, I can open PRs! Let me know after you test it thoroughly.
Details:
Fixed a visual bug that affect Android/Google TV 11+ that result in part of image cut and obscure 10% of top reading screen and 10% of buttom screen at the same time, usually it dissapear only after clicking on back then continue but appear again after few reading minutes. This visual bug only affect webtoon reading mode in ATV11+. (On ssiv lib)
Speed up of "processing" when loading images on all reading modes. (On ssiv lib + app)
Made ARGB_8888 mode the default rendering reading mode (same exactly as 32bit reading mode setting) (on ssiv lib + app)
Tried to fix Skia engine visual bug that result in visual transparent tint colors on large long strip images (1400x10000 resolution or higher) but could only improve it partially and not fix the issue completely (will try to fix it in near future, refer to uploaded comparison for details) (on ssiv lib)
Increased default max zoom by 100% (2x) on both manga and webtoon mode (on app)
These are the current changed I made and tested, you can decide to implement it or not based on your preference and judgment.
PS: I will make it clear beforehand, I vibecoded these changes using Claude code, it works as intended so there should be no problem but just wanted to let you know, either way it's up to you to decide.
### Acknowledgements
* [x] This is not a duplicate of an existing issue. Please look through the list of [open issues](https://github.com/UsagiApp/UsagiApp/issues) or our [project backlog](https://github.com/orgs/UsagiApp/projects/3/views/2) before creating a new one.
Isn't it better to switch to my ssiv lib fork in your libs.versions.toml code rather than implementing it in your ssiv lib code? This way, you can easily revert and switch back to your ssiv lib in case you change your mind later or some bugs appear while keeping your ssiv code clean. If you are certain and still want me to implement these changes anyway, then I will gladly do.
still want to use my own library, just make sure that i can control my library for future patches / fixes
I have updated ssiv lib with few visual bug fixes, quality enhancement and optimization then implemented it in my fork.
You can try new enhancements by installing and testing it here. If you like these enhancements and want to implement them in your app, I can open PRs! Let me know after you test it thoroughly.
Details:
Fixed a visual bug that affect Android/Google TV 11+ that result in part of image cut and obscure 10% of top reading screen and 10% of buttom screen at the same time, usually it dissapear only after clicking on back then continue but appear again after few reading minutes. This visual bug only affect webtoon reading mode in ATV11+. (On ssiv lib)
Speed up of "processing" when loading images on all reading modes. (On ssiv lib + app)
Made ARGB_8888 mode the default rendering reading mode (same exactly as 32bit reading mode setting) (on ssiv lib + app)
Tried to fix Skia engine visual bug that result in visual transparent tint colors on large long strip images (1400x10000 resolution or higher) but could only improve it partially and not fix the issue completely (will try to fix it in near future, refer to uploaded comparison for details) (on ssiv lib)
Increased default max zoom by 100% (2x) on both manga and webtoon mode (on app)
These are the current changed I made and tested, you can decide to implement it or not based on your preference and judgment.
PS: I will make it clear beforehand, I vibecoded these changes using Claude code, it works as intended so there should be no problem but just wanted to let you know, either way it's up to you to decide.
### Acknowledgements
* [x] This is not a duplicate of an existing issue. Please look through the list of [open issues](https://github.com/UsagiApp/UsagiApp/issues) or our [project backlog](https://github.com/orgs/UsagiApp/projects/3/views/2) before creating a new one.
Isn't it better to switch to my ssiv lib fork in your libs.versions.toml code rather than implementing it in your ssiv lib code? This way, you can easily revert and switch back to your ssiv lib in case you change your mind later or some bugs appear while keeping your ssiv code clean. If you are certain and still want me to implement these changes anyway, then I will gladly do.
still want to use my own library, just make sure that i can control my library for future patches / fixes
I have updated ssiv lib with few visual bug fixes, quality enhancement and optimization then implemented it in my fork.
You can try new enhancements by installing and testing it here. If you like these enhancements and want to implement them in your app, I can open PRs! Let me know after you test it thoroughly.
Details:
Fixed a visual bug that affect Android/Google TV 11+ that result in part of image cut and obscure 10% of top reading screen and 10% of buttom screen at the same time, usually it dissapear only after clicking on back then continue but appear again after few reading minutes. This visual bug only affect webtoon reading mode in ATV11+. (On ssiv lib)
Speed up of "processing" when loading images on all reading modes. (On ssiv lib + app)
Made ARGB_8888 mode the default rendering reading mode (same exactly as 32bit reading mode setting) (on ssiv lib + app)
Tried to fix Skia engine visual bug that result in visual transparent tint colors on large long strip images (1400x10000 resolution or higher) but could only improve it partially and not fix the issue completely (will try to fix it in near future, refer to uploaded comparison for details) (on ssiv lib)
Increased default max zoom by 100% (2x) on both manga and webtoon mode (on app)
These are the current changed I made and tested, you can decide to implement it or not based on your preference and judgment.
PS: I will make it clear beforehand, I vibecoded these changes using Claude code, it works as intended so there should be no problem but just wanted to let you know, either way it's up to you to decide.
### Acknowledgements
* [x] This is not a duplicate of an existing issue. Please look through the list of [open issues](https://github.com/UsagiApp/UsagiApp/issues) or our [project backlog](https://github.com/orgs/UsagiApp/projects/3/views/2) before creating a new one.
Isn't it better to switch to my ssiv lib fork in your libs.versions.toml code rather than implementing it in your ssiv lib code? This way, you can easily revert and switch back to your ssiv lib in case you change your mind later or some bugs appear while keeping your ssiv code clean. If you are certain and still want me to implement these changes anyway, then I will gladly do.
still want to use my own library, just make sure that i can control my library for future patches / fixes
@dragonx943 finally after over than 2 weeks of testing, debugging and quality Vibe coding, I have successfully fixed visual tints bug on large long strip jpeg images by implementing jpeg turbo lib and made it the default decoder for all jpeg/jpg images type for the following reasons:
Decode every jpeg/jpg image correctly.
Faster than any other jpeg decoder, from 2x up to 6x times faster.
No extra overhead, use same overhead as any other jpeg decoder lib or android native lib/hardware decoder and sometimes use less resources since its fully optimized.
Actively developed and maintained.
The only possible downside: add extra ~500KB per abi since its an external library (.so file) so total added size is around ~2MB.
Since this visual tint bug only affect large long strip jpeg/jpeg images, other images types: webp, jxl and avif remain unchanged.
I have tested new lib and its working perfectly and its certainly faster than default jpeg decoder, I will keep updating it regulary as soon as there is new stable updates from upstream + fix any possible bugs.
Shall I open PR to your ssiv lib main branch?
@dragonx943 finally after over than 2 weeks of testing, debugging and quality Vibe coding, I have successfully fixed visual tints bug on large long strip jpeg images by implementing jpeg turbo lib and made it the default decoder for all jpeg/jpg images type for the following reasons:
Decode every jpeg/jpg image correctly.
Faster than any other jpeg decoder, from 2x up to 6x times faster.
No extra overhead, use same overhead as any other jpeg decoder lib or android native lib/hardware decoder and sometimes use less resources since its fully optimized.
Actively developed and maintained.
The only possible downside: add extra ~500KB per abi since its an external library (.so file) so total added size is around ~2MB.
Since this visual tint bug only affect large long strip jpeg/jpeg images, other images types: webp, jxl and avif remain unchanged.
I have tested new lib and its working perfectly and its certainly faster than default jpeg decoder, I will keep updating it regulary as soon as there is new stable updates from upstream + fix any possible bugs. Shall I open PR to your ssiv lib main branch?
I created PR in your ssiv lib, you just need to make a new release tag and publish it on github as a new release, wait for jitpack to build lib then refactor .toml file with your ssiv package git URL + new release tag + implement necessary lib changes into app your self (uploaded full changes zip file with full folders path) + 2x max zoom (optional).
Activity
dragonx943 commentedon Apr 23, 2026
You can create a PR for Usagi's SSIV: https://github.com/UsagiApp/subsampling-scale-image-view and make a PR in this repo if necessary
Ero-gamer commentedon Apr 23, 2026
Isn't it better to switch to my ssiv lib fork in your libs.versions.toml code rather than implementing it in your ssiv lib code? This way, you can easily revert and switch back to your ssiv lib in case you change your mind later or some bugs appear while keeping your ssiv code clean.
If you are certain and still want me to implement these changes anyway, then I will gladly do.
dragonx943 commentedon Apr 25, 2026
still want to use my own library, just make sure that i can control my library for future patches / fixes
Torro101 commentedon Apr 30, 2026
what about turning it into a branch?
dragonx943 commentedon Apr 30, 2026
yes, you can
Ero-gamer commentedon May 1, 2026
@dragonx943 finally after over than 2 weeks of testing, debugging and quality Vibe coding, I have successfully fixed visual tints bug on large long strip jpeg images by implementing jpeg turbo lib and made it the default decoder for all jpeg/jpg images type for the following reasons:
The only possible downside: add extra ~500KB per abi since its an external library (.so file) so total added size is around ~2MB.
Since this visual tint bug only affect large long strip jpeg/jpeg images, other images types: webp, jxl and avif remain unchanged.
I have tested new lib and its working perfectly and its certainly faster than default jpeg decoder, I will keep updating it regulary as soon as there is new stable updates from upstream + fix any possible bugs.
Shall I open PR to your ssiv lib main branch?
dragonx943 commentedon May 1, 2026
yes
Ero-gamer commentedon May 2, 2026
I created PR in your ssiv lib, you just need to make a new release tag and publish it on github as a new release, wait for jitpack to build lib then refactor .toml file with your ssiv package git URL + new release tag + implement necessary lib changes into app your self (uploaded full changes zip file with full folders path) + 2x max zoom (optional).
2x max zoom + ssiv refactor.zip