Open TheUnknownHack3r opened 8 months ago
Same issue in Windows 10 while connecting Poco F1. As soon as the device is connected, the UI breaks. There is flickering with intermittent purple and white patches across the top of the UI. These intensify or go way depending on mouse pointer movement and position (disabled wireless mouse and checked with track-pad too). The Reboot button and the one next to it also become blank leaving just the outline. The flickering and some UI-breakages go away as press any key on the keyboard in an attempt to take a screenshot. Best shown through a screen recording.
Same issue in Windows 10 while connecting Poco F1. As soon as the device is connected, the UI breaks. There is flickering with intermittent purple and white patches across the top of the UI. These intensify or go way depending on mouse pointer movement and position (disabled wireless mouse and checked with track-pad too). The Reboot button and the one next to it also become blank leaving just the outline. The flickering and some UI-breakages go away as press any key on the keyboard in an attempt to take a screenshot. Best shown through a screen recording.
Please open a separate issue for this, and post logs if possible
Please open a separate issue for this, and post logs if possible
Where do I find the logs. How do I capture them for this session?
Same happening with a Galaxy S10e on Windows 10.
Guys, there are 2 version, one with opengl and another one with no opengl. For my case, I was using the no opengl version which had ths problem. But the opengl version had no ui glitch.
Guys, there are 2 version, one with opengl and another one with no opengl. For my case, I was using the no opengl version which had ths problem. But the opengl version had no ui glitch.
Nice find! That works brilliantly. Thank you!
Please use the up to date version of this program: https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation
Describe the bug When you open the application on a Raspberry Pi 4 (after compiling, because ARM builds don't exist), the GUI is fine. But as soon as a device is detected, the GUI breaks. Technically usable, but I don't want to accidentally press the wrong buttons. Here is a image below:
Expected behavior For the software to work as expected.
You have a solution? Perhaps it is because the wrong driver is being used. But I don't see documentation on how to switch the driver.
UAD log When opened via a terminal, this is what I see: