Yes, even if the upgrade only took care of that annoying msg every time you start the app it would be worth it.....though it would be nice if it also fixed the issue with the usage not resetting properly too.
Once the bugs get fixed this app will do almost everything I need it to....Except have the ability to look at past usage. If you could include a usage log in a future release it would be perfect
How do you know this? Have you spoken to the developer lately? I understand that he is busy with an internship now. App seems to work fine now. It didn't reset properly last month, but this month it did. So hoping the problem is fixed somehow. Only thing now is the message to upgrade everytime the app is opened. Hopefully this is fixed soon too
That's ok. School has to be a priority. No worries, at least for me anyway, how are you going to implement full background capabilities? You already registered for the headless APIs?
What are you planning for version 2? Any chance you can implement data tracking for sms sent and outgoing calls? Thanks.
Jonathan, Now that you have put a warning when the App is closed does that imply that it will no longer run in the background in the way the previous versions could? (I appreciate that I need to start the App if I ever reboot my device).
I was curious about the data reset does it reset at 12:01am on that day the number is set or would it be the following. So if I put 13 would it be 12:01am on the 13 or 12:01am of the 14. Thanks a bunch love the app
Hopefully you still check this thread once in a while, and still work on the updates.
Just today I noticed this, as described below. Running OS 10.2.0.1791 on Z10 STL100-2
I noticed that my free memory was down to 200MB from the usual 800-900MB. When checked the details in the apps management, found that DataCheck Pro was using over 600MB. I did not take the screenshot unfortunately.
I closed the app, and re-opened it. It started with the usage of 8MB memory. Now, after 2 hours, it uses 32MB of memory, so it is constantly increasing.
I have not noticed it before, running 10.1
Can you check it you can optimize the memory management in you application?