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
Resources occupied after closing this app properly and openning another app #19
Comments
i have done the testing with moto g3 (Android 6)its working fine. |
Everything around cameras works so much differently per Android version and manufacturer, that I just cannot fix some of the bugs without having a device with the particular issue :/ |
Not only the around cameras will trigger this error, but also other flashlight apps(like Camera your team developed, Open Flashlight, Search Light, etc. in F-Droid) will cause similar problem. You can use these apps in the Step3 for further testing. |
Try downloading one of the popular flashlight apps on the market and then install and try to use this app. Then you should get this problem. I couldn't reproduce it on my friend's device as well. |
Yes, I get this, but Simple Flashlight seems to be closing resources fine. EasyLight breaks Simple Flashlight in my case but if I try to start EasyLight after Simple Flashlight on-off, everything works. |
Steps to trigger the problem
What happens when you follow the steps
The app open in Step 3 will report errors or be hanging. Below is a screenshot:
Bugs behind the problem
It does not release the flashlight or relevant services in a proper way.
The version of the software being used
Version 1.20 - Added on 2016-09-27
Environments
The text was updated successfully, but these errors were encountered: