-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quality of Wallpapers and Autostart #81
Comments
The reboot-thing seems to be an Android issue, see https://issuetracker.google.com/issues/251231297. Unfortunately, I've no idea why the quality of the wallpapers differs. |
Ok, thanks for your answer. Sadly I am not an app developer so my help/insight is limited as well. |
Unfortunately I don't have any idea what could cause the wallpaper resolution issue (and I don't aim to do anything about it currently, sorry). |
Hi @Bnyro, I am encountering the same problem with the low quality wallpaper resolution. I think that the problem is due to the method According to this page of Stackoverflow seems to be a common issue with this function. Most likely, setting this flag to |
No, feel free to create a pull request if you tested it to make sure it actually has an impact. |
I tried on my fork, but unforutnately seem not solving the issue, the quality of the image is significantly bad to me :( |
Steps to reproduce
First issue
Second issue
Expected behavior
First issue
Second issue
Actual behavior
First issue
WallYou
Aves Libre
WallYou
Aves Libre
The first two pictures is the problem which I am referring to. The WallYou pictures looks blurrier and pixilated.
The second two pictures show an other wallpaper, and show that the result is more pixilated.
See also the (new) pictures I added in #64.
Second issue
Wall You version
3.3 (17)
Android version
Android 13
Other details
As I am using quite a lot of minimalistic wallpapers these problems are often visible. Other wallpapers work fine. I really like your app(s), thanks a lot for your work.
Acknowledgements
The text was updated successfully, but these errors were encountered: