![]() Please thank Google and their brilliant UX team for that. Sorry, but there is absolutely nothing I can do on my side to fix this. Android usually also 'forgets' to remove this message again when To give you a way to tell Android that you know that you don't care.ĭepending in the device, such message may only appear if you start the app in a way where the app won't be shown in the foreground.Įxamples are starting the app with a homescreen widget or by using a headset button. Android shows that to make you aware that there is a backround app and they forgot Google thought it is an awesome idea that Android shows such messages automatically for apps which can run in the background. Why are you torturing me with something like this? Question: After updating to version 3.1.x, I see a stupid message telling me that the app is running. Please don't skip any of the steps, even if you think it doesn't make sense.ġ) Clear cache and data of the app in the Android app settings If not, please try a clean re-install of the app with the following steps. This can take up to 15 minutes or even longer if you have a an extremely large number of files and folders. In all cases you have to restart the phone and wait a while for Android to rebuild the database. Not all file managers show such files by default. Please be aware that these files are "hidden" because of the dot at the beginning. You need to remove all ".nomedia" in all of the folders (including parent folders). All files in such folders won't be visible to the app. This tells Android not to index the folder and all sub-folders. Usually this happens because there are files with the name '.nomedia' in a folder. I can't do anything on my end to fix this. Apparently this is not the case on your device. Google thought it was a great idea that apps targeting Android 12 (which Google is forcing us app developers to target as of today) should only be able to "see" the files which are indexed in the Android media data database (unless the app is a file manager app). Question: After updating to version 3.1.x, I don't see files in some folders. I'm just a hobby developer, working on that in my spare time, but I assure you, I'll do whatever I can. I ask for your indulgence during this time, as it was not my idea to introduce all these restrictions, but Google's. It will surely take a while until the new version has reached this level as well. Please keep in mind that the old version of the app was developed continuouslyįor 11 years and therefore all kinds of issues were addressed there. Not everything works out of the box immediately. I worked really hard within the last two years trying to mitigate all of that, but there will surely be cases where Scanning and reading files and folders is now 70 times (not 70%!!!) slower than before. The only exception to this are file manager apps which can still access all files and folders without restrictions. File and folder access is now extremely restricted. Newer which has some dramatic consequences. ![]() Google is forcing app developers to target Android 11 or This is basically a newly developed version of the app. It took two years to implement all the changes Google requires for apps targeting Android 11 and newer. Let me share some general words about the new version of the app. Question: What the hell changed in Version 3.1.x? If you use the payed version, please send me the Google Order Number via email. The following page provides hints for different manufacturers: Īs a last resort, you can download the old version of the app from here: Very often this is called "Power Saving". These can be found in the battery options of the phone. There are also other options in the general Android settings that can cause an app to be forced to quit. ![]() Then follow the steps shown in this video: Alternatively, un-install and re-install the app. You can go to the Android app settings and disable the battery optimization for the app manually. What you experience sounds like one of the problems the dialog was warning about. The dialog also contains a warning that not following the recommended changes, it will likely lead to problems. When you started the new app version 3.1.x for the first time, you have seen a dialog regarding battery optimization settings. Android terminates an app after a certain time (depending on the settings) if it is not running in the foreground with the display turned on. For apps that are targeting Android 11 or 12, a very strict "battery optimization" is automatically active, which causes that an app cannot run in the background for a longer time. In the new version of the app, this happens because Google forces us app developers to target Android 12 or newer for app updates. Question: Version 3.1.x does not longer run in background for a longer time.
0 Comments
Leave a Reply. |