cvzi/ScreenshotTile

Home Button Shot Not Working

rjm831 opened this issue · 9 comments

Using a Samsung Tab A7. Samsung just updated to Android 12 and the app no longer functions with Native/Assist. When I long press the home button the screen turns blank and in the color of the app, and completely freezes. I don't know if this bug is due to recent app updates or due to Samsung's Android 12 upgrade. Don't have root privileges but will provide any logs or data if needed.

cvzi commented
cvzi commented

Thanks. I don't see anything relating to the app at all, which is strange.

I checked the aLogcat app, and it seems that app doesn't work on newer Android versions. It only shows logs from the Android system and from aLogcat itself, not from other apps.

You would have to use a computer with the Android SDK Platform Tools installed and run adb logcat to get the full log via USB.

I will try the app myself on an Android 12 device later, I currently don't have access to one. But I am pretty sure I checked it on Android 12 the last time I made major changes, so I doubt I'll find anything. It's probably related to your specific device or Samsung.

cvzi commented

I see, that's a bit unexpected that the debug version works. Since you never had the debug version installed, the debug app started with a fresh settings copy. Maybe the settings or something else got corrupted during the update of Android or during the update of the app and that's causing the crash.

Find the app in the Android settings in the "Apps" section. There you can "Force stop" the app and then tap on "Storage and cache" and then "Clear storage". Then open the app and set it as assistant again and make sure the app settings are as you want them.
Or you could try uninstalling the app, restarting the phone and the re-install the app.

Also you could definitely keep using the debug version, there's no harm in using it, you just won't get app updates.

I checked the aLogcat app, and it seems that app doesn't work on newer Android versions. It only shows logs from the Android system and from aLogcat itself, not from other apps.

Try AppManager.
It's very easy to view logs of other apps from their PID: https://muntashirakon.github.io/AppManager/en/#subsubsec:main:running-apps

cvzi commented

I don't know what could be the problem. My knowledge of the difference between debug and release version in Android is limited.

When I publish the next version of the app, I can create another debug version for you to see if that will work as well.