-
Notifications
You must be signed in to change notification settings - Fork 41
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
Niagara becomes unresponsive intermittently #2595
Comments
I'm having this same issue on my Samsung Fold 5, randomly Niagra will freeze visually on the home screen. When I tap and scroll my phone vibrates as if I'm actively scrolling things, but the screen stays frozen. I took have to force stop the app for it to restart and work correctly. I'm on Android 14 as well. I can submit logs, too, if possible. Screen_Recording_20240212_101435_Messenger.mp4 |
Thanks for reporting the issue and also thanks for providing a screen recording @sesu-tech
StatementWe have reproduced the issue on some devices. This is just one cause and it seems there are others. Our current theory is that the issue appears on devices running Android 14. When the screen is locked and another application takes charge of its awake state, Niagara Launcher and other third-party launchers have issues realizing they are in the foreground after unlocking the device and thus will not update their UI while staying responsive to actions. We need your helpThis issue is an Android incompatibility with third-party launchers in general, please check the information below to see how you can help!
Possible workaroundIf this sounds like what you are affected by, please read the section below describing a possible workaround. Massive thanks to @burny90 for finding the following information: Steps to reproduce the issue on devices it appears on:
Workaround instructionsPlease react to this post with 🎉, if this workaround worked for you and with 👎 if it did not work.
Workarounds worked for:
|
I will edit this post when we receive more devices on which this issue occurs and react with Confirmed
Suspected
Last updated: 28.06.2024 |
@TFackler I'm on One UI 6.0 |
Same issue here. One UI 6.0, Galaxy S21 FE, Android 14. Need to force stop Niagara to fix it. Don't know how to manually trigger the issue, but it happens frequently |
FYI I'm also having this issue quite regularly now, but I'm on a Pixel 8 Pro |
Interesting... what version of Android are you on? |
1.11.5 is Niagara's version, just to confirm. Still can't figure out how to trigger the issue manually 😅 |
This has happened to me a few times now over the past week or so. Pixel 5 Before finding this repo I went to the Google Play reviews to see if the problem was widespread, and noticed a couple of reports in the recent reviews there (names omitted).
|
As a paying Pro user, I am hoping I don't have to ask for a refund. I really like Niagara+. |
They'll fix it, no worries. Patience is virtuous. :) |
And frustration thru non-access is tantamount to paralysis, or mutiny, or
something much, much worse.
…On Tue, Mar 12, 2024 at 7:35 PM Seth ***@***.***> wrote:
As a paying Pro user, I am hoping I don't have to ask for a refund. I
really like Niagara+.
I tried switching back to the Samsung OneUI 6.0...it sucks.
Please fix this.
They'll fix it, no worries. Patience is virtuous. :)
—
Reply to this email directly, view it on GitHub
<#2595 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG5GZXDTNHSH2OHCLQTWWRLYX6NNBAVCNFSM6AAAAABDCJU7LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJSHA2DENJSG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
True, frustrating, but think of it this way: expressing your frustration here takes more work than just reloading the app. ;) |
@weirdchylde your home screen is awesome bro |
It is more than just reloading the app. Must I restart the app and/or my
phone EVERY time I exit an app back to my home screen?
No. That is not a viable solution. Especially when it is several times a
day. No.
And just being in the queue of bugs with promises of a fix somewhere down
the road is NOT an option.
Isn't this how apps go from sterling 5-star products to the depths of
MySpace???
Someone needs to at least provide a detailed problem/fix flow to paid
subscribers.
I just want my Niagara Pro+ to work.... :(
…On Tue, Mar 12, 2024 at 8:48 PM Seth ***@***.***> wrote:
And frustration thru non-access is tantamount to paralysis, or mutiny, or
something much, much worse.
True, frustrating, but think of it this way: expressing your frustration
here takes more work than just reloading the app. ;)
—
Reply to this email directly, view it on GitHub
<#2595 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG5GZXD37E72R6LJHJYN54DYX6V7HAVCNFSM6AAAAABDCJU7LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJTGA3TAMJYGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
It's absolutely just reloading the app. Settings > Apps > Niagra Launcher > Press "Force stop". Yes, it's tedious and annoying. But do you have any idea the amount of work and skill it takes to develop software? Complaining in the comments that you're a "paying customer" and deserve first class immediate support helps nothing and nobody. If anything, it discourages the dev team behind the project. Patience. If you don't have it, maybe you should contribute to the source code and fix it yourself! 😛 Trust me: life is more enjoyable when you're patient and slow to anger. |
P.S. how much do you pay for Niagra Pro? Be honest: I bet we're talking $1-10 a YEAR. 😅 |
Seth,
Sorry for coming off as an ass. Not at all my intent. Sometimes I can't
even get to the settings at the bottom of my phone screen.
And, no. I do not know all the work that goes on behind the scenes of app
development and maintenance. But when an app one has come to rely on 100%
of the time starts getting wonky and then goes "tits-up" 70% of the time,
that takes a toll.
Also sorry for pulling the "paying customer Karen card"....also, not my
intention. I, by NO MEANS, am proferring that I am an elite-class citizen
because I paid. Shit, I can't even create my own smart watch face, so....
I paid the lifetime rate (Sept 12, 2022) before things went full-on annual
subscription. Can't find exactly how much.
R,
Zed
…On Tue, Mar 12, 2024 at 9:28 PM Seth ***@***.***> wrote:
P.S. how much do you pay for Niagra Pro? And no lying or inflating; be
honest. I bet we're talking $1-10 a YEAR.
—
Reply to this email directly, view it on GitHub
<#2595 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG5GZXCHFCQDPF3MBV4CSMDYX62U5AVCNFSM6AAAAABDCJU7LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJTGE3TEMJWGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Seth,
I found my receipt for Niagara Pro+ Dunno if that helps or means
anything.
[image: Screenshot 2024-03-12 215157.png]
On Tue, Mar 12, 2024 at 9:49 PM Mike Kaldenberg ***@***.***>
wrote:
… Seth,
Sorry for coming off as an ass. Not at all my intent. Sometimes I can't
even get to the settings at the bottom of my phone screen.
And, no. I do not know all the work that goes on behind the scenes of app
development and maintenance. But when an app one has come to rely on 100%
of the time starts getting wonky and then goes "tits-up" 70% of the time,
that takes a toll.
Also sorry for pulling the "paying customer Karen card"....also, not my
intention. I, by NO MEANS, am proferring that I am an elite-class citizen
because I paid. Shit, I can't even create my own smart watch face, so....
I paid the lifetime rate (Sept 12, 2022) before things went full-on annual
subscription. Can't find exactly how much.
R,
Zed
On Tue, Mar 12, 2024 at 9:28 PM Seth ***@***.***> wrote:
> P.S. how much do you pay for Niagra Pro? And no lying or inflating; be
> honest. I bet we're talking $1-10 a YEAR.
>
> —
> Reply to this email directly, view it on GitHub
> <#2595 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BG5GZXCHFCQDPF3MBV4CSMDYX62U5AVCNFSM6AAAAABDCJU7LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJTGE3TEMJWGU>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
No worries!-------- Original Message --------On 3/12/24 10:50 PM, ZedFaldor wrote:
Seth,
Sorry for coming off as an ass. Not at all my intent. Sometimes I can't
even get to the settings at the bottom of my phone screen.
And, no. I do not know all the work that goes on behind the scenes of app
development and maintenance. But when an app one has come to rely on 100%
of the time starts getting wonky and then goes "tits-up" 70% of the time,
that takes a toll.
Also sorry for pulling the "paying customer Karen card"....also, not my
intention. I, by NO MEANS, am proferring that I am an elite-class citizen
because I paid. Shit, I can't even create my own smart watch face, so....
I paid the lifetime rate (Sept 12, 2022) before things went full-on annual
subscription. Can't find exactly how much.
R,
Zed
On Tue, Mar 12, 2024 at 9:28 PM Seth ***@***.***> wrote:
P.S. how much do you pay for Niagra Pro? And no lying or inflating; be
honest. I bet we're talking $1-10 a YEAR.
—
Reply to this email directly, view it on GitHub
<#2595 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG5GZXCHFCQDPF3MBV4CSMDYX62U5AVCNFSM6AAAAABDCJU7LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJTGE3TEMJWGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#2595 (comment)",
"url": "#2595 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
Thank you for the continuous reports with device specs. Before, we thought this was an incompatibility with OneUI and thrid-party launchers / Niagara Launcher, but now we see that it is also common on Pixel devices. |
@ZedFaldor, I 100% understand where you are coming from, having your phone's homescreen not work reliably must be incredibly frustrating, and I would try to fix the issue in a heartbeat if we knew where it stems from. Sadly, none of our test devices has had this issue, so tracking down the error is really difficult. |
Just to throw another data point in there, I also experience this issue somewhat frequently on my Pixel 8. Not sure if it helps track down where it's freezing, but I have a widget that I have adjusted so that it pushes the Niagara UI down a bit lower than default. When the freezes occur, the stuck UI reflects the "original" position of the Niagara UI before that widget pushes things down. The app I was previously using, if it was one of the favorites, will return to its proper, lower position. The frozen UI stays in the "up" position. |
TFackler,
If I wouldn't be totally crippled by not having my phone on me, I'd mail it
to Niagara devs to root out the problem. But alas, how the hell would I
function without my phone?! Probably like I did as a kid in the 80s. LOL
It would just suck more.
Zed
…On Fri, Mar 15, 2024 at 2:11 AM TFackler ***@***.***> wrote:
@ZedFaldor <https://github.com/ZedFaldor>, I 100% understand where you
are coming from, having your phone's homescreen not work reliably must be
incredibly frustrating, and I would try to fix the issue in a heartbeat if
we knew where it stems from. Sadly, none of our test devices has had this
issue, so tracking down the error is really difficult.
—
Reply to this email directly, view it on GitHub
<#2595 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG5GZXGWDYKWWL5RN2KYBJDYYKNIRAVCNFSM6AAAAABDCJU7LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZGA3DEMZWGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I have the same issue, on a newly purchased pixel 8 (not pro) |
I have this same issue on the pixel fold. Android 14, Niagara 1.11.5, it seems that it is happening more frequently lately. |
Yes, this solution is great! I have run the launcher without any issue for one week. Congratulations 🎉 |
Mine is hanging on pixel 7 pro. Niagara 1.12.3 Android build number: AP1A.240505.005 |
@burny90 The thread is not dead yet, but it was a bit slow. Thanks so much for all the effort you put into trying to find the cause 💙 I have looked at it, and since others also said the workaround worked for them, let's hope that grating Niagara Launcher the accessibility permission is indeed the fix. I added your workaround and reproduction steps to my collection comment above so others are aware of this. Sadly, I could not replicate the issue on my Pixel 5 running Android 14, so it's still difficult to determine exactly what's going on. |
Accessibility has been turned on for my phone, that didn't fix it for me. |
@ageisen2000 can you reproduce the issue using these steps:
If so, please also try to reproduce the issue with another third party launcher like Nova Launcher if you have the time, that would be valuable information. |
Google.Assistant.hates.Nova.Launcher.mp4](url) I've pasted this on the discord discussion too. Nova Launcher displayed the same issues more or less. I'll attach a video in a short second, but the freezing can vary from temporary to a full unresponsiveness. Sometimes swiping to the left for the Google Feed will trigger normally, but the rest of the launcher is still stuck and frozen. Turning on accessibility mode for Nova Launcher will fix the issue. The video I will attach in a second has Niagra Launchers accessibility mode off for the purposes of the test. I have also turned it on in other tests when using Nova Launcher and it still freezes. This is also the case vice-versa, so using Nova Launchers accessibility settings but using Niagara Launcher .So the finding is that the accessibility mode for whatever launcher you use must be turned on. |
Thank you for trying with Nova launcher and also for sharing the video. Nova can at least catch itself somewhat soon / opening the app list fixes the issue, so that might give us some points we can look into. 👍 While I hope this is the solution for everyone, it seems that there is also a version of this issue that cannot be fixed by granting the accessibility permission. We will keep looking. |
All,
I wish I could co-celebrate the "locked Assistant to Niagara freeze"
solution. Tried 3 times to freeze things. It didn't do it. That said, I
haven't had a lock up in a while. I will keep tryong, tho.
ZED
…On Wed, Jun 19, 2024, 05:26 Berny ***@***.***> wrote:
Hello.
I really hope this thread is not dead..
I can consistently replicate the bug now. It is caused by using the Google
Assistant when the screen is turned off.
Steps to replicate:
1. Be on the home screen (this seems to be important as being in an
app doesn't always cause an issue)
2. Turn off screen
3. Ask the google assistant a question
4. Unlock phone normally and the screen becomes unresponsive
I have attached a short video for reference.
—
Reply to this email directly, view it on GitHub
<#2595 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG5GZXGMSWWFBFLSQ2PNSE3ZIFMEJAVCNFSM6AAAAABDCJU7LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZYGMZDOMRZHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I've discovered that phone calls cal lock it up too. Try that as well with your testing. The situation might be niche to certain phones. |
That sounds to mee like it is caused by apps that draw on top of the lockscreen. |
What phone and android version do you use? |
I also have a hunch that this might be the case. For me, it tends to freeze up after the Alarmy app rings an alarm, which draws over the screen. |
I'm seeing this on:
I just tried applying the accessibility fix and will keep an eye on whether the issue happens again. |
btw it actually worked for me, I'm not having this bug anymore (for 2 months now) |
For me it was also fixed by the proposed solution of enabling the accessibility permission although it was 100% never caused by the Google assistant on my end as I don't have it installed at all. There may have been a certain trigger but to me it just seemed to happen randomly. |
It stopped crashing for me for a while (couple of weeks????). Happened
again just yesterday. No Google Assistant (installed but not in use @ the
time).
I wonder if I am just too fast for my phone and Niagara
Niagara Pro Since 9/12/2022
ver. 1.12.6 Updated 8/3/24
Android 14
One UI v. 6.1
Samsung S22+
Thx,
Zed
…On Thu, Aug 15, 2024 at 8:45 AM YouRik ***@***.***> wrote:
For me it was also fixed by the proposed solution of enabling the
accessibility permission although it was 100% never caused by the Google
assistant on my end as I don't have it installed at all. There may have
been a certain trigger but to me it just seemed to happen randomly.
—
Reply to this email directly, view it on GitHub
<#2595 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG5GZXEOHVWBYJLXNKYQNH3ZRSWI3AVCNFSM6AAAAABDCJU7LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJRGI4TKOBQGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Same, enabled accessibility (I also dont have google assistant turned on, or even activated) and things have been smooth since then. (pixel 8 ) |
I granted the Accessibility permission but still had the issue. Each time it happened, I went back and the Accessibility toggle had been turned off, though. So it might be working fine while Accessibility permission is granted, but for some reason something is turning the Accessibility toggle off. |
My partner has run into the same issue on his Pixel 9 Pro XL w/ Android 14 (AD1A.240530.047) this morning. I, on the other hand, have used my P9 Pro XL a lot more heavily and have not seen it. After checking the differences, I have the accessibility service enabled for the quick lock while he does not. I will enable it on his device too and see how it goes. Two more dara points:
Is there any way to restart Niagara easily when this happens? Accessing the settings app blindly is nothing a non-tech savy person can do. On a Pixel you could setup the double tap on the back to open the settings app... but that comes with its own problems. |
Those are good observations and it's a shame to hear it's affecting the new Pixel as well. Remember, it can also trigger from phone calls too. Anything that technically can open something whilst in the lock screen can potentially set it off. I used to quickly reset it by accessing the settings through the quick settings drop down and force closing Niagara Launcher within there. You could probably create a shortcut to do the same thing with something like tasker if you want a faster way than that. |
Berny, a shortcut would be awesome, except the only way I can interact with
it during the "lockout" is to hold the center "button" and then tell Google
Assistant to open an app. That, or restart the phone (S22+, Android 14,
Nigara Pro+). I will say tho, the anomaly has been less of late.
MKaldenberg
…On Sat, Aug 31, 2024 at 8:22 AM Berny ***@***.***> wrote:
My partner has run into the same issue on his Pixel 9 Pro XL w/ Android 14
(AD1A.240530.047) this morning. I, on the other hand, have used my P9 Pro
XL a lot more heavily and have not seen it. After checking the differences,
I have the accessibility service enabled for the quick lock while he does
not. I will enable it on his device too and see how it goes.
Two more dara points:
1. He hasn't enabled / used the Google assistant nor does he do anything special with his device. As non-tech savvy person, his usage is very tame. It happened randomly after the device had been in stand-by for several hours.
2. I also use Niagara on a Tab S9 Ultra w/o the accessibility service enabled and have yet to run into this issue there. It too runs Android 14 (One UI 6.1, UP1A.231005.007.X910XXS4BXG7).
Is there any way to restart Niagara easily when this happens? Accessing
the settings app blindly is nothing a non-tech savy person can do. On a
Pixel you could setup the double tap on the back to open the settings
app... but that comes with its own problems.
Those are good observations and it's a shame to hear it's affecting the
new Pixel as well.
Remember, it can also trigger from phone calls too. Anything that
technically can open something whilst in the lock screen can potentially
set it off.
I used to quickly reset it by accessing the settings through the quick
settings drop down and force closing Niagara Launcher within there. You
could probably create a shortcut to do the same thing with something like
tasker if you want a faster way than that.
—
Reply to this email directly, view it on GitHub
<#2595 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG5GZXDU7W6ID4IBIVKPKXDZUG7RBAVCNFSM6AAAAABDCJU7LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRSHA4TMMBTGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
That's very unusual. You should be able to swipe down to access quick settings even during the freeze up. How I fix it quickly can be seen in my demonstration video here at 0:27 If that is also frozen, it points to a wider system issue on your device IMO. Google.Assistant.hates.Third.Party.Launchers.unless.you.do.this.one.trick.mp4 |
@ZedFaldor From your control panel, you should be able to access settings. |
@burny90 I would like to report the issue to Google properly and also add it to our official list of issues that we want users to be aware of. Sadly, we have not been able to reproduce the issue on one of our devices, so I cannot create a screen recording myself. |
Yeah of course. Go ahead :) |
Responding to this survey might help (amongst other things related to custom launchers) with solving this issue from the platform side 🤞 See the announcement of the survey and this news article for context |
Hello I have the exact same issue on my Galaxy Fold 4, I really can't justify buying the pro version with such an annoying bug ... |
Hey everyone! Could you please add some easy shortcut to restart launcher? It's highly annoying to search for Niagara in apps to restart it. For example you could treat chaotic movement of finger around the screen as a restart gesture. And make it configurable in settings. |
Describe the bug
Normally using the launcher, it will become unresponsive and/or laggy.
I will tap my home button and Niagara comes into the foreground, and is responsive to input but is not visually updating.
For example, I will scroll down to the letter K apps, it suddenly becomes frozen. I scroll down to the letter Y (still frozen, no screen update has occurred after my scroll input), and I tap where an app would be. It will launch an app from the Y section but still display the letter K apps. It's like the app is still running and working but the view is frozen.
This behavior continues until I force quit the app, it starts working normally again but eventually starts freezing again.
Steps to reproduce
Occurs randomly, I cannot consistently reproduce it, app will work fine for hours and it then happens, or happen within a few minutes after I force quit it.
Device: Samsung S24, Android 14
Niagara version 1.11.3
I use Niagara on 3 other phones, a Pixel a OnePlus, and a Unihertz and they do not have this issue
Does the issue also occur with other 3rd-party launchers?
Not applicable
Other 3rd-party launcher(s) tested
No response
Device name
Samsung S24
Android version
Android 14
Screenshots / Screen recordings
No response
The text was updated successfully, but these errors were encountered: