Sorting by usage does not work
When sorting by usage is selected in the menu, it stops working after a few searches and apps are sorted by name again. If the last used apps were displayed instead, then one wouldn't need to type anything most of the time, so to me sorting by usage is the most important feature of the app.
Thanks for reporting - I cannot yet reproduce this yet - is the mode also changed in the setting when you experience this problem?
Hi,
These are the only non-default settings I have:
- Icon size: small
- Finish FAST on app launch: yes
- Sort: usage
- Ignore space: yes.
I have Android 6 on my phone, but I had the same problem with my previous phone that ran Android 5.
Please, let me know if there is anything else that is not clear.
Best regards Tamas
On 25 Oct 2016 2:45 a.m., "ligi" [email protected] wrote:
Thanks for reporting - I cannot yet reproduce this yet - is the mode also changed in the setting when you experience this problem?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ligi/FAST/issues/88#issuecomment-255913635, or mute the thread https://github.com/notifications/unsubscribe-auth/AV8eD1K4_v4HDNE1p6Xwe2itR7ByRZ4vks5q3V8ugaJpZM4KeGHq .
thanks - but I mean you see the setting is set to sort by usage but you get a different behavior?
Hi,
Exactly! The setting is set to sort by usage, but the actual sorting algorithm used sorts by application name.
Though sometimes it does work for a few searches, and then it goes back to sorting by application name again. When I check the setting, it still shows sort by usage even then.
Best regards Tamas
On Tue, Oct 25, 2016 at 10:18 PM ligi [email protected] wrote:
thanks - but I mean you see the setting is set to sort by usage but you get a different behavior?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ligi/FAST/issues/88#issuecomment-256179017, or mute the thread https://github.com/notifications/unsubscribe-auth/AV8eD2KeIZcrJipF04K2czHXizSJnyoyks5q3nIygaJpZM4KeGHq .
My experience has been that FAST somehow forgets the usage stats from time to time. (ATM i'm using Titanium Backup to restore the latest automatically refreshed backup if that happens.)
This might happen more often because of the "finish on app launch" setting. I'm using FAST as my main launcher and keep this disabled and as for me this 'forgetting' happens very seldomly.
Tamas, can you remember if (un)installing apps was somehow related to your issue? (see issue #74)
Hi Sebastian,
I am not aware of any connection between the issue and installing or uninstalling apps. That does not mean there isn't any though, but if I remember correctly, the problem was simply that sorting by usage did not work, as the apps were sorted by their name.
I am not sure if others can/could reproduce this issue, but one thing that I can think of is that some cleaner app removed the usage data from your app's folder, and then your app reverted to using the default sorting. But this is just speculation, as I cannot remember using such an application when I reported this problem.
Best regards, Tamas
On 28 August 2017 at 13:54, Sebastian [email protected] wrote:
Tamas, can you remember if (un)installing apps was somehow related to your issue?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ligi/FAST/issues/88#issuecomment-325345396, or mute the thread https://github.com/notifications/unsubscribe-auth/AV8eD_sLO0Ssnhw_G2uuLQSHHOhD7MHnks5scriKgaJpZM4KeGHq .
As you can see FAST is sorting by usage and by name at the same time. If it "switches from usage sorting to name sorting" that's probably because there's no usage data anymore. The point is that there is a bug that causes FAST to drop usage data whenever an app gets (un)installed in background.
OK, I get it now, and this scenario is very likely to happen on my phones, as I keep installing and uninstalling apps (sometimes many times a day). So if this triggers the bug, then I can see why it kept happening to me, and not for other people.
Best regards, Tamas
On 29 August 2017 at 12:20, Sebastian [email protected] wrote:
As you can see FAST is sorting by usage and by name at the same time. If it "switches from usage sorting to name sorting" that's probably because there's no usage data anymore. The point is that there is a bug that causes FAST to drop usage data whenever an app gets (un)installed in background.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ligi/FAST/issues/88#issuecomment-325633774, or mute the thread https://github.com/notifications/unsubscribe-auth/AV8eDyFszGGwygJz6VqLaf9KeExUkx-Pks5sc_QYgaJpZM4KeGHq .
My fix for issue #74 has been merged and will be included in the upcoming release 6.7. You can check if the error still persists. Otherwise this can be closed :yum:
Hi, Thanks for the update!
Best regards, Tamas
On 6 Sep 2017 14:06, "Sebastian" [email protected] wrote:
My fix for issue #74 https://github.com/ligi/FAST/issues/74 has been merged and will be included in the upcoming release 6.7
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ligi/FAST/issues/88#issuecomment-327477056, or mute the thread https://github.com/notifications/unsubscribe-auth/AV8eD4aBP39i_KMKYwDMKFhoCtow7fzYks5sfpjHgaJpZM4KeGHq .
is your issue resolved in the new release?
Hi Sebastian,
I cannot see a new release yet; the last version I can see in Play Store is almost 2 years old. Should I download it from another source (e.g.: F-Droid)?
Best regards, Tamas
On Mon, 1 Jul 2019 at 07:32, Sebastian [email protected] wrote:
is your issue resolved in the new release?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ligi/FAST/issues/88?email_source=notifications&email_token=AFPR4D5XZSJXJV2XKYQJXGLP5GQJPA5CNFSM4CTYMHVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY5EBIQ#issuecomment-507134114, or mute the thread https://github.com/notifications/unsubscribe-auth/AFPR4D6DPESM2CKN335VOBLP5GQJPANCNFSM4CTYMHVA .
Two years ago is correct. The play store page for FAST reports 6.7 as the latest version and that one should include the patch.
Hi Sebastian,
You are right; I have not realised that I reported the bug 3 years ago. I believe not long after I removed the application, as I already had a built-in search in Nova Pro. I only needed FAST because of the sorting by usage feature and Nova did not have that.
I have just reinstalled FAST and will let you know if there is anything wrong with it. By the way, are you still maintaining it if something does come up?
Best regards, Tamas
On Mon, 1 Jul 2019 at 07:47, Sebastian [email protected] wrote:
Two years ago is correct. The play store page for FAST reports 6.7 as the latest version and that one should include the patch.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ligi/FAST/issues/88?email_source=notifications&email_token=AFPR4DY37IT6WVSAQA3LQC3P5GSA5A5CNFSM4CTYMHVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY5E6QA#issuecomment-507137856, or mute the thread https://github.com/notifications/unsubscribe-auth/AFPR4D6GTNDJZWFLMSC7XE3P5GSA5ANCNFSM4CTYMHVA .
Great!
About maintaining
Right now i still have substantial interest in this Application as i'm also using it. This might change in the next years as i might tend to move away from Android entirely. But until then i will be around to take care of this app whenever i find the time for it. This will probably exclude cosmetic or fancy features and most features that don't call my personal interest, but i'm positive that a bug will catch my attention and that in these cases i would likely get around to bring up a fix as long as i have time for it. So just keep in mind that things might take very long and that i am not an official maintainer nor do i have write access to this repository, so it also depends on the project owner, ligi, to respond to pull requests and such. Some changes might linger a while before they are included in releases. In the end i will always try to respond to messages and if asked at least respond with explanations, even if it just means explaining why something will take long or possibly never happen.
Thanks for your reply and your work!
Best regards, Tamas
On Mon, 1 Jul 2019 at 19:48, Sebastian [email protected] wrote:
Great! About maintaining
Right now i still have substantial interest in this Application as i'm also using it. This might change in the next years as i might tend to move away from Android entirely. But until then i will be around to take care of this app whenever i find the time for it. This will probably exclude cosmetic or fancy features and most features that don't call my personal interest, but i'm positive that a bug will catch my attention and that in these cases i would likely get around to bring up a fix as long as i have time for it. So just keep in mind that things might take very long and that i am not an official maintainer nor do i have write access to this repository, so it also depends on the project owner, ligi, to respond to pull requests and such. Some changes might linger a while before they are included in releases. In the end i will always try to respond to messages and if asked at least respond with explanations, even if it just means explaining why something will take long or possibly never happen.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ligi/FAST/issues/88?email_source=notifications&email_token=AFPR4D4AOIFKZA3RZX7EPATP5JGO3A5CNFSM4CTYMHVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY7AKXY#issuecomment-507381087, or mute the thread https://github.com/notifications/unsubscribe-auth/AFPR4DZ3NGHOQLG2BC6EQODP5JGO3ANCNFSM4CTYMHVA .
I have also noted the sort-by-usage problem.
@thioshp Which version of FAST are you using and do you still encounter the problem?