- New: Tweak: display Wi-Fi instead of Mobile data.
- Improve: widget updating logic (may fix widget-not-updating bug)
- Several internal updates
Minor update, just to get things going.
It's good to be back.
Minor update, just to get things going.
It's good to be back.
I almost forgot.
So yeah, this is an app that I made a long time ago, and that I had to stop developing because it required a permission that (I though) was no longer possible to obtain.
In order to get the data usage, originally you had to use a method that required the phone id. Getting that id required a phone permission, and that permission was not granted anymore for apps targeting Android 10 and up. The deprecation notice said to use an alternative, but I was never able to make it work. So I just kept the app at that working version, and never updated it.
Fast-forward a couple years, and I discovered that you could use the alternative, but only if you allowed ONLY android 10 and up, which meant that, by updating the app, existing phones could no longer use it (original: 7-9, new 10+). So I just kept avoiding updates.
Fast-forward a couple more years, I have now a new Android 12 phone, and Android 8 is now considered 'old'. So I implemented the change (which allowed me to remove the phone permission), and a couple others I always wanted to make (this is an app mainly for myself after all). Play Store is no longer displaying apps targeting versions older than 10, so this was perfectly the best moment to do so.
Hope it's help useful for someone, it was for me.
Several of my apps are now available on F-droid! Links below:
V 3.0
- Configurable period length (any number of days or months).
- New tweak: advanced secondary bars
- Improved settings screen
IMPORTANT! This new update has a newer period management, which needs the starting day and the period length. After updating, the previous configuration will be automatically migrated to the new version, but you may want to check it just in case.
Edit: a new beta was released that fixes the 'invalid first update after period changes' bug.
At last! It wasn't easy, but not as hard as I expected at first. This new version allow you to choose any arbitrary period length! Now you can choose a daily period, a 21 days period, 28 days, or even 12 months period if you want (any positive days or months). In fact internally it can have any time, even hours or years, however for simplicity the user interface only allows days or month.
This new version uses a different approach: previously you only needed to specify the day of the change (for 1 month periods) and calculating the current percentage of the current period was almost instant, with just a saved parameter (the last month) to know when the period was changed.
Now that you can specify an arbitrary length the app uses a different approach: it has a configurable 'start of the period' date that uses to know the percentage of the current period. But it also allows to know when the period changes, and does the update.
I've tried myself this new version for a few days and it seem to work fine, however I need real users to test under real conditions, so I hope at least someone in the beta is able to try it.
As the notice in the changelog implies, this new method uses new configuration, and although there is special code to migrate it, it may fail in some cases so better check that it worked. This is also the reason why the version was increased to 3.0.
There are other minor modifications, like some internal cleanup, but also a new tweak (that may be the default in future versions) to show a better secondary progress bar indicator when you have accumulated data. Specifically (sp is the saved periods parameter):
V 2.4
- Fixed incorrect accumulated after a period change
- New tweak: Hide bars
- New tweak: Hide labels
- Always show secondary progress while negative (-50% = -150%...)
A very minor update, but with a fix for how the accumulated data was computed, which lead to incorrect values.
It also adds two new tweaks to hide either the bars or the texts in the normal widget (specially useful in the compressed version) and now the secondary progress is always shown rounded to the percentage (previously it was only shown when between -100 and 0). This is useful to check how many data you will lose on the next period, for example.