User:JodyBruchonFan/Google software sucks: Difference between revisions
Archive, just in case. |
m wording |
||
| Line 12: | Line 12: | ||
Most importantly, after tapping on "copy" or "move", it doesn't stay in the current directory, but opens the Download folder instead. This means, if you wish to move items to a subdirectory of the currently viewed directory, you first have to manually navigate all the way back to the directory you were in before tapping on "copy" or "move". This is something even Windows 95 did better. | Most importantly, after tapping on "copy" or "move", it doesn't stay in the current directory, but opens the Download folder instead. This means, if you wish to move items to a subdirectory of the currently viewed directory, you first have to manually navigate all the way back to the directory you were in before tapping on "copy" or "move". This is something even Windows 95 did better. | ||
Earlier versions even had a bug where cancelling a file move operation would cause source files to be irrecoverably deleted without having been moved to the destination.<ref>{{cite web |url=https://support.google.com/photos/thread/106201?hl=en |title=Photos disappeared after moving to another device folder - Google Photos Community |author=Gökhun Güneyhan |date=2018-04-24 |access-date=2026-06-08 }} ([https://megalodon.jp/2023-0228-0023-32/https://support.google.com:443/photos/thread/106201?hl=en archive])</ref> | |||
But hey, at least they implemented Google Drive integration. To their credit, they implemented the ability to browse ZIP and even TAR and 7z files, create ZIP files, a built-in EXIF viewer, the ability to open multiple instances, selection by tapping the file icon (faster than holding), a large grid view suitable for image seeking, and the file transfer progress indicator is displayed as a notification, which is better than a pop-up that blocks interacting with the file manager, like in Samsung's file manager. | But hey, at least they implemented Google Drive integration. To their credit, they implemented the ability to browse ZIP and even TAR and 7z files, create ZIP files, a built-in EXIF viewer, the ability to open multiple instances, selection by tapping the file icon (faster than holding), a large grid view suitable for image seeking, and the file transfer progress indicator is displayed as a notification, which is better than a pop-up that blocks interacting with the file manager, like in Samsung's file manager. | ||
| Line 19: | Line 19: | ||
The thing that supposedly sets Android apart from iOS is user choice and freedom, yet Google decided that device owners are at the mercy of app developers to let them take screenshots and screen recordings. This is known as [[screenshot blocking]] or screen capture blocking, and can only be overridden with an unlocked bootloader and root access, which has complications of its own. | The thing that supposedly sets Android apart from iOS is user choice and freedom, yet Google decided that device owners are at the mercy of app developers to let them take screenshots and screen recordings. This is known as [[screenshot blocking]] or screen capture blocking, and can only be overridden with an unlocked bootloader and root access, which has complications of its own. | ||
While this was originally intended to prevent banking app content from being captured or broadcasted to external screens (miracast, MHL), there is nothing preventing it from being used outside of its intended scope. Consequently, it was only a matter of time before app developers | While this was originally intended to prevent banking app content from being captured or broadcasted to external screens (miracast, MHL), there is nothing preventing it from being used outside of its intended scope. Consequently, it was only a matter of time before app developers realized they could use it arbitrarily.<ref>{{cite web |url=https://www.howtogeek.com/why-screenshots-dont-always-work-especially-in-secure-apps/ |website=How To Geek |author=Faisal Rasool |title=Why Your Phone Blocks Screenshots in Secure Apps |date=2025-08-23 |access-date=2026-05-26 }}</ref><ref>{{cite web |author=konradkar |url=https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |website=[[Reddit]] |title=Booking.com app disallow to take screenshot, can I bypass this? |date=2020-02-14 |access-date=2026-05-26 |archive-url=https://web.archive.org/web/20230615071612/https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |archive-date=2023-06-15}}</ref> | ||
For this reason, Google should have provided a built-in option that lets the device owner override screen capture blocks at their own responsibility. An app deciding whether you should be allowed to take screenshots on your device is comparable to a guest in your home telling you how to behave. | For this reason, Google should have provided a built-in option that lets the device owner override screen capture blocks at their own responsibility. An app deciding whether you should be allowed to take screenshots on your device is comparable to a guest in your home telling you how to behave. | ||