doesn't refresh newly installed apps. #113
Comments
|
This is a known issue. FAST has quite some problems with automatic refreshing of apps that i once attempted to fix in my own fork but i couldn't yet make it compatible with android oreo and the changes also haven't been merged. In the meantime as a workaround you can use the fact that FAST refreshes on a new start and ends the main activity when entering the settings. So going to settings and back right away will trigger a refresh without the need to clear any data. Or, if you are familiar with compiling android apps and don't run Android Oreo or newer you could go ahead and compile for yourself with my changes. |
|
Oh, didn't know that. Thanks for replying so fast. |
|
If your suggestion concerns something to be implemented into the pull request then i think you should post it there. |
|
Actually I am new here and I don't understand what exactly pull request means. So let me tell ny suggestion here and if it is inappropriate then I will delete it and add it to pull request. |
|
I am literally sorry that I didn't notice it is already in the settings. Extremely sorry sir. (._.) |
|
No Problem, settings of new apps can be quite confusing sometimes. :D |
|
Certainly it is. Thank you again. ❤️ |
|
I think you should leave it open until it is fixed for good. |
|
done. |
|
I've just completed my rework of FASTs app list update mechanisms. The only thing necessary now is to test it and polish it up before release. If you would want to test this it would greatly be appreciated as I can't properly test it under real life conditions since I don't use Android 8.0 or newer on my main device. |
|
Hey, I would really love to help you in testing the app out, although
unfortunately I don't know how to build apps, so I will go for the testing
build. :D
…On Sun, 12 May 2019, 10:05 Sebastian, ***@***.***> wrote:
I've just completed my rework of FASTs app list update mechanisms. The
only thing necessary now is to test it and polish it up before release. If
you would want to test this it would greatly be appreciated as I can't
properly test it under real life conditions since I don't use Android 8.0
or newer on my main device.
If you are familiar with building android apps go ahead and compile my
feature branch.
If not, I have uploaded a testing build
<https://github.com/SebiderSushi/FAST/releases/tag/redesign_receiever> on
my forked repository that can be installed alongside the official FAST
application.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#113 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALJAPTI77DJ77URFLAM7KBLPU6NBLANCNFSM4GZJJHMA>
.
|
|
Fast-debug_redesign_test_v00.apk
The test build is with this name right, just to confirm?
…On Sun, 12 May 2019, 11:33 Na Cl2, ***@***.***> wrote:
Hey, I would really love to help you in testing the app out, although
unfortunately I don't know how to build apps, so I will go for the testing
build. :D
On Sun, 12 May 2019, 10:05 Sebastian, ***@***.***> wrote:
> I've just completed my rework of FASTs app list update mechanisms. The
> only thing necessary now is to test it and polish it up before release. If
> you would want to test this it would greatly be appreciated as I can't
> properly test it under real life conditions since I don't use Android 8.0
> or newer on my main device.
> If you are familiar with building android apps go ahead and compile my
> feature branch.
> If not, I have uploaded a testing build
> <https://github.com/SebiderSushi/FAST/releases/tag/redesign_receiever>
> on my forked repository that can be installed alongside the official FAST
> application.
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#113 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/ALJAPTI77DJ77URFLAM7KBLPU6NBLANCNFSM4GZJJHMA>
> .
>
|
|
Yes :) |
|
It isn't being installed, i am running on a custom rom based on 8.1
…On Sun, 12 May 2019, 11:37 Sebastian, ***@***.***> wrote:
Yes :)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#113 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALJAPTITMJTCP6ZFE7U5S2TPU6X3TANCNFSM4GZJJHMA>
.
|
|
It finally got installed when i did that from mixplorer's inbuilt
installer, strangely android package installer was unable to do this. I
disabled one app just now and it got updated quickly, will report further
if any issues found. Thanks
…On Sun, 12 May 2019, 11:38 Na Cl2, ***@***.***> wrote:
It isn't being installed, i am running on a custom rom based on 8.1
On Sun, 12 May 2019, 11:37 Sebastian, ***@***.***> wrote:
> Yes :)
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#113 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/ALJAPTITMJTCP6ZFE7U5S2TPU6X3TANCNFSM4GZJJHMA>
> .
>
|
|
Very strange. But good that it worked anyway. Thank you very much for putting your trust and time into this and testing! |
|
That's just your generosity sir, oh and I don't trust you at all btw :p
I tried disabling and uninstalling apps and then quickly checking them in
the FAST, it was working fine each and every time so i guess this mechanism
is absolutely working well. :D
…On Sun, 12 May 2019, 11:44 Sebastian, ***@***.***> wrote:
Very strange. But good that it worked anyway. Thank you very much for
putting your trust and time into this and testing!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#113 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALJAPTLHE6D5SKSMFT6KO3DPU6YUZANCNFSM4GZJJHMA>
.
|
|
But installing an app someone else built sure needs to happen out of at least a little bit of trust. |
|
Okay then, I love you too.
…On Sun, 12 May 2019, 22:51 Sebastian, ***@***.***> wrote:
But installing an app someone else built sure needs to happen out of at
least a little bit of trust.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#113 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALJAPTI3VYJAHCCKQOWA4SDPVBGYJANCNFSM4GZJJHMA>
.
|
|
Hello, It's been quite a time and I didn't find any issue in FAST except that most of the times if an app is uninstalled from another launcher or from settings directly, FAST doesn't recognise the uninstallation. Thanks. :D
|
|
Okay this should not happen. |
|
Yep sure
1. 116 apps
2. Icon resolution is 48
3. I can't really tell about the workload as I didn't even notice it. :(
4. Fast isn't set as default.
To reproduce the issue you can set some other launcher as default and uninstall any app either from that launcher or from android settings. FAST won't notice the uninstallation most probably. Even force stopping FAST doesn't work. It isn't the case if it is set as default launcher.
…-------- Original Message --------
From: Sebastian <[email protected]>
Sent: June 7, 2019 5:04:54 PM UTC
To: ligi/FAST <[email protected]>
Cc: Nihal Anand <[email protected]>, State change <[email protected]>
Subject: Re: [ligi/FAST] doesn't refresh newly installed apps. (#113)
Okay this should not happen.
Could you give the details specified in the last paragraph of the [release notes](https://github.com/SebiderSushi/FAST/releases/tag/redesign_receiever) of the testing build to give a clearer image?
Also if you might know anything that could be important when reproducing this bug that would be helpful too.
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
#113 (comment)
|
|
Thank You very much for the information. I will look into it when i find the time. |
|
You're welcome and thank you too.
…On June 10, 2019 7:34:43 AM UTC, Sebastian ***@***.***> wrote:
Thank You very much for the information. I will look into it when i
find the time.
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
#113 (comment)
--
Sent from my Android device with Librem Mail. Please excuse my brevity.
|
|
Okay i have been using the testing build for about a week now since i finally have a daily driver phone running Oreo (more precisely LineageOS 15.1). The only issue i found to be reproducible on my system seems to be that on Oreo FAST doesn't recognize it automatically if a "component" is enabled or disabled. For example there are Apps that offer to manually specify in their settings to hide or show one of their activities. I also found the error in the code that probably causes this and will fix it right now. |
|
Correction: While investigating the issue of FAST not detecting components correctly i managed to reproduce your error: The issue i was investigating turned out to consist of two parts, one of them being the error in the code i already found and the other one being the issue you were observing. The fixed version can now be downloaded from my release page (just pick the latest one). Explanation It happended to be that if the list of changed packages was too short, then the refresh mechanism that should refresh only said changed packages on a fresh FAST launch (i.e. FAST has been terminated some time before) would be very quick. Due to a mistake i made this would lead to a situation where (i guess) somehow the mechanism would save the refreshed app list to disk while the user interface would have already loaded the previous version from disk and therefore keeps displaying that and then saves that outdated list later when you leave FAST, overwriting the refreshed list. |
|
That's really great to hear, although I didn't understand the technicalities much. Thanks a lot sir, once again! :D
…On June 30, 2019 4:19:41 PM UTC, Sebastian ***@***.***> wrote:
**Correction:** While investigating the issue of FAST not detecting
components correctly i managed to reproduce your error: The issue i was
investigating turned out to consist of two parts, one of them being the
error in the code i already found and the other one being the issue you
were observing.
The fixed version can now be downloaded from my [release
page](https://github.com/SebiderSushi/FAST/releases).
#### Explanation
It happended to be that if the list of changed packages was too
short, then the refresh mechanism that should refresh only said changed
packages on a fresh FAST launch (i.e. FAST has been terminated some
time before) would be very quick. Due to a mistake i made this would
lead to a situation where (i guess) somehow the mechanism would save
the refreshed app list to disk while the user interface would have
already loaded the previous version from disk and therefore keeps
displaying that and then saves that outdated list later when you leave
FAST, overwriting the refreshed list.
I probably always (un)installed multiple apps while trying to
reproduce your issue. In these cases the refreshing mechanism would
take long enough for the user interface to completely initalize. At
that point instead of writing the new list to disk, it will be sent
directly to the running user interface and so the changes are applied.
My fix simply consists in making sure that the callback
resposible for sending the updated list directly to the user interface
gets initialized before the updating mechanism is executed.
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
#113 (comment)
|
|
Hello
I know it's been a long time, so how are you?
i was just confused about if you ever pushed the test builds of Fast app to
fdroid/playstore?
thanks.
…On Tue, Jul 2, 2019, 10:49 AM Nihal ***@***.***> wrote:
That's really great to hear, although I didn't understand the
technicalities much. Thanks a lot sir, once again! :D
On June 30, 2019 4:19:41 PM UTC, Sebastian ***@***.***>
wrote:
>
> *Correction:* While investigating the issue of FAST not detecting
> components correctly i managed to reproduce your error: The issue i was
> investigating turned out to consist of two parts, one of them being the
> error in the code i already found and the other one being the issue you
> were observing.
>
> The fixed version can now be downloaded from my release page
> <https://github.com/SebiderSushi/FAST/releases>.
> Explanation
>
> It happended to be that if the list of changed packages was too short,
> then the refresh mechanism that should refresh only said changed packages
> on a fresh FAST launch (i.e. FAST has been terminated some time before)
> would be very quick. Due to a mistake i made this would lead to a situation
> where (i guess) somehow the mechanism would save the refreshed app list to
> disk while the user interface would have already loaded the previous
> version from disk and therefore keeps displaying that and then saves that
> outdated list later when you leave FAST, overwriting the refreshed list.
> I probably always (un)installed multiple apps while trying to reproduce
> your issue. In these cases the refreshing mechanism would take long enough
> for the user interface to completely initalize. At that point instead of
> writing the new list to disk, it will be sent directly to the running user
> interface and so the changes are applied.
> My fix simply consists in making sure that the callback resposible for
> sending the updated list directly to the user interface gets initialized
> before the updating mechanism is executed.
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#113?email_source=notifications&email_token=ALJAPTPCJDA325WKPQLWAGTP5DMJ3A5CNFSM4GZJJHMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY4PHXA#issuecomment-507048924>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ALJAPTJ4REUBY5C67ETJ26LP5DMJ3ANCNFSM4GZJJHMA>
> .
>
|
|
I pushed a new build on my release page. At some point i stopped using FAST and stopped working on the patch. It was left lingering for about 3 years now and is 5 years old in total. I wouldn't get my hopes up that it will ever get merged at this stage. Right now it is what it is but it should work pretty ok. |
|
yeah, that's totally understandable. Much thanks and appreciation for
pushing another build for just a guy :)
I dont understand the difference between extras and no extras version. Can
you tell me?
Also, which launcher do you use nowadays ?
Thanks again
…On Sun, Aug 21, 2022, 4:17 PM Sebastian ***@***.***> wrote:
I pushed a new build on my release page.
<https://github.com/SebiderSushi/FAST/releases>
It's still not up to code but should work. I put together the existing
code and fixed some bits here and there.
At some point i stopped using FAST and stopped working on the patch. It
was left lingering for about 3 years now and is 5 years old in total. I
wouldn't get my hopes up that it will ever get merged at this stage. Right
now it is what it is but it should work pretty ok.
—
Reply to this email directly, view it on GitHub
<#113 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJAPTPKMHDD56VH3I7GYIDV2ICNVANCNFSM4GZJJHMA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
|
I'm using Lawnchair. The inability to use app shortcuts or widgets on FAST was always a bummer... The TL;DR is: You likely only care about The noExtras version is set up to get the app as small as possible. It is what you get when you download the app "FASTER" (org.ligi.faster on F-Droid). Nowadays this build variant isn't really useful as almost no contemporary phone would notice a difference between a 60KB apk and a 90KB apk. But it can still be compiled so here we are. The Amazon, F-Droid, Play variants are basically different in which link they use when you tap "Share" or where you get sent to when you tap "open in market" (only shown on apps that were installed by google play / amazon app store). |
|
got it. So there is no difference in terms of features or fastness of the
opening. Thanks.
I am also using lawnchair, just wanted to make fast app as default
assistant so that i can open apps from any screen.
Thanks a lot man, you're great.
…On Sun, Aug 21, 2022, 5:35 PM Sebastian ***@***.***> wrote:
I'm using Lawnchair. The inability to use app shortcuts or widgets on FAST
was always a bummer...
------------------------------
The TL;DR is: You likely only care about forFDroid-withExtras
If you're curious, build variants are different in these aspects:
The noExtras version is set up to get the app as small as possible. It's
what you can get through F-Droid as "FASTER" (org.ligi.faster)
<https://f-droid.org/en/packages/org.ligi.faster>. The are no
translations and no "About" page (opened by tapping the question mark in
the top bar in the full release).
Nowadays this build variant isn't really useful as almost no contemporary
phone would notice a difference between a 60KB apk and a 90KB apk. But it
can still be compiled so there we are.
The Amazon, F-Droid, Play variants are basically different in which link
they use when you tap "Share" or where you get sent to when you tap "open
in market" (only shown on apps that were installed by google play).
—
Reply to this email directly, view it on GitHub
<#113 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJAPTLWM2VYD5QUESI6GM3V2ILSLANCNFSM4GZJJHMA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
|
Hi, hope you are doing well.
I saw that you are developing FAST app again.
I wanted to ask if there is some reason you made it show in recents, bcoz
its kinda pain now.
And a request if you find it worth it, please make FAST bottom oriented.
Regards
…On Sun, Aug 21, 2022, 7:26 PM Na Cl ***@***.***> wrote:
got it. So there is no difference in terms of features or fastness of the
opening. Thanks.
I am also using lawnchair, just wanted to make fast app as default
assistant so that i can open apps from any screen.
Thanks a lot man, you're great.
On Sun, Aug 21, 2022, 5:35 PM Sebastian ***@***.***> wrote:
> I'm using Lawnchair. The inability to use app shortcuts or widgets on
> FAST was always a bummer...
> ------------------------------
>
> The TL;DR is: You likely only care about forFDroid-withExtras
> If you're curious, build variants are different in these aspects:
>
> The noExtras version is set up to get the app as small as possible. It's
> what you can get through F-Droid as "FASTER" (org.ligi.faster)
> <https://f-droid.org/en/packages/org.ligi.faster>. The are no
> translations and no "About" page (opened by tapping the question mark in
> the top bar in the full release).
>
> Nowadays this build variant isn't really useful as almost no contemporary
> phone would notice a difference between a 60KB apk and a 90KB apk. But it
> can still be compiled so there we are.
>
> The Amazon, F-Droid, Play variants are basically different in which link
> they use when you tap "Share" or where you get sent to when you tap "open
> in market" (only shown on apps that were installed by google play).
>
> —
> Reply to this email directly, view it on GitHub
> <#113 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ALJAPTLWM2VYD5QUESI6GM3V2ILSLANCNFSM4GZJJHMA>
> .
> You are receiving this because you modified the open/close state.Message
> ID: ***@***.***>
>
|
|
I thought it could be useful to have fast in recents when not using it as a launcher but i can revert this change, sure. Can you go into more detail as to why it is a pain? I'd like to grasp this a little better. As for a bottom-oriented layout, there's issue #66 which has been around since 2015. Again, there's not much going on with this project anymore. My intention is to finally finish my work that i started and make FAST at least usable even if it's still far from polished. The core of my changes still is "make FAST refresh the app list properly for once", the rest is what's required to even compile it and some low hanging fruit that i thought i just might fix along the way as well. |
|
Oh okay , understood.
The thing with recents is that
1) if it is used as default launcher, it shows up in recents. Nobody goes
to the launcher by swiping through the apps in recents menu, but by
pressing the home button. So it takes unnecessary space there.
2) if it is used as an assitant app, I personally find it quicker to open
FAST by long pressing the home, instead of scrolling through recents.
Basically same reason as above.
Thanks a lot for replying and working on the project. :D
…On Tue, Nov 8, 2022, 11:35 PM Sebastian ***@***.***> wrote:
I thought it could be useful to have fast in recents when not using it as
a launcher but i can revert this change, sure. Can you go into more detail
as to why it is a pain? I'd like to grasp this a little better.
As for a bottom-oriented layout, there's issue #66
<#66> which has been around since
2015. Again, there's not much going on with this project anymore. My
intention is to finally finish my work that i started and make FAST at
least usable even if it's still far from polished. The core of my changes
still is "make FAST refresh the app list properly for once", the rest is
what's required to even compile it and some low hanging fruit that i
thought i just might fix along the way as well.
—
Reply to this email directly, view it on GitHub
<#113 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJAPTOQF7YIM6MX3RHC4FLWHKI7TANCNFSM4GZJJHMA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
After some tests i came to the conclusion that android does not offer any way to make FAST appear on the recents screen with just the regular launcher entry but not the Assist entry. I reverted the change and posted a new release. |
|
1. im on android 13, limeage os.
I had not tested it thoroughly but i did now and it seems that it happens
if you go to FAST settings menu. Then the app is stuck on recents menu
unless it is swiped away manually.
…On Wed, Nov 9, 2022, 12:53 AM Sebastian ***@***.***> wrote:
1. I realize that your default launcher should never appear on the
recents screen, but from my testing i came to the conclusion that android
already takes care of this situation. I tested my build on CyanogenMod 7
(android 2.3.7), LineageOS 15.1 (android 8.1) and LineageOS 18.1 (android
11) and all of these do not add FAST to the recents list if it is set as
the default launcher. What android version by which vendor are you using?
2. Using FAST as an assistant app is indeed a use case i did not test
so far so i just tried it out.
After some tests i came to the conclusion that android does not offer any
way to make FAST appear on the recents screen with just the regular
launcher entry but not the Assist entry. I reverted the change and posted a new
release <https://github.com/SebiderSushi/FAST/releases>.
—
Reply to this email directly, view it on GitHub
<#113 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJAPTKPFBSXRHMKAKE6YKTWHKSCPANCNFSM4GZJJHMA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
|
I can't reproduce this issue, but i don't have android 13. |
|
i was talking about the second last update.
the latest one with the changes reverted is absolutely working.
…On Wed, Nov 9, 2022, 1:18 AM Sebastian ***@***.***> wrote:
I can't reproduce this issue, but i don't have android 13.
You might have to remove FAST from recents and reboot after the update
until it all woks as expected again - but that's a shot in the dark i have
no clue what android 13 is doing here.
—
Reply to this email directly, view it on GitHub
<#113 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJAPTLQGANEWSNXJVBUF3DWHKVBJANCNFSM4GZJJHMA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
|
v6.8-redesign-7 will show up on the recents screen just like any other app would, regardless of whether you navigated to the settings screen or not - that's expected behavior. The only exception is if android removes it because it is set as the default launcher app. glad to hear that v6.8-redesign-8 works properly again. |
|
yeah, thank you again for doing this much!
…On Wed, Nov 9, 2022, 1:25 AM Sebastian ***@***.***> wrote:
v6.8-redesign-7 will show up on the recents screen just like any other app
would, regardless of whether you navigated to the settings screen or not -
that's expected behavior. The only exception is if android removes it
because it is set as the default launcher app.
glad to hear that v6.8-redesign-8 works properly again.
—
Reply to this email directly, view it on GitHub
<#113 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJAPTLSJGHTTGCD5IMR5DLWHKV25ANCNFSM4GZJJHMA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
|
Hi Sebastian, hope you doing great.
I was wondering if you still interested in maiantaining fast app tool, if
yes id like to request for some small features.
yeah right im still using your app on android 13 cuz theres no better
replacement, there is one app search app that came out recently and has
pretty many features, looks mice but isnt "fast" and "light".
so please do let me know if you are interested.
Thanks again and hoping you're good healthwise and financially.
Love you too
…On Wed, Nov 9, 2022, 5:04 AM Na Cl ***@***.***> wrote:
yeah, thank you again for doing this much!
On Wed, Nov 9, 2022, 1:25 AM Sebastian ***@***.***> wrote:
> v6.8-redesign-7 will show up on the recents screen just like any other
> app would, regardless of whether you navigated to the settings screen or
> not - that's expected behavior. The only exception is if android removes it
> because it is set as the default launcher app.
>
> glad to hear that v6.8-redesign-8 works properly again.
>
> —
> Reply to this email directly, view it on GitHub
> <#113 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ALJAPTLSJGHTTGCD5IMR5DLWHKV25ANCNFSM4GZJJHMA>
> .
> You are receiving this because you modified the open/close state.Message
> ID: ***@***.***>
>
|
Fast doesn't recognize newly installed apps. so to do that I have to clear cache in settings of the app but that also resets sorting of apps and the apps I pinned to the top. Please look into this issue.
The text was updated successfully, but these errors were encountered: