-
Notifications
You must be signed in to change notification settings - Fork 767
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
Unwanted "shaking your phone in frustration" followed by crash #2564
Comments
Thanks for reporting. Any chance to get some log from logcat when the crash occurs? We can make the code robust against sensors failure, but logs may help. Or send a rageshake if it is possible. |
Thanks for the quick response. I have no experience with logcat (or Android logging / programming) at all. But I will see what I can learn in the coming days. As mentioned above, I have sent a rageshake some time ago (quite sure that it was October, 25th) but do not know how to refer to it here. However, I just sent a new one refering to this issue. |
Here is some log. Sorry for the bloat, I simply do not know what is important to be filtered. Also, the app was started and crashed twice (each time by choosing the "settings" option in the rageshake dialog). So, there might be some redundant information.
|
I just reproduced this crash by simply clean-installing the app, shaking my device and then selecting settings in the dialog. As the logcat indicates, the settings fragment cannot be accessed without authentication. Some possible approaches to solve this issue:
|
Thanks for pointing this out! From my naive point of view it would also make sense to simply disable rageshake by default, at least until the user is authenticated. Overall, I would absolutely not call rageshake an anti-feature (as might others #2576). But it probably should not complicate things like this. |
Still happening for me. I'm using my Cosmo Communicator on a fresh install of the app. I can't disable the rageshake feature, nor go to settings without it crashing. I've disabled haptic feedback in the hopes that would fix it; no joy. I've also rebooted my phone several times. Anything I can do? Logs might not be possible at the moment. |
For my sensor-failing phone I have indeed found an (actually obvious) "workaround" by accident: Rotating the phone in a different position, the rageshake is not triggered. This allowed me to enter my credentials while holding the phone upside down and then disabling the feature. Another "possibility" is of course to simply use another app. SchildiChat (as a fork of Element) appears to me to have all features of Element but with a more traditional interface (which I actually find more intuitive than the original). But most importantly for the topic discussed here, it has rageshake disabled. Hope this helps until the problem is finally solved. |
Since I'm affected by #3897 I had to reinstall the app from the CI and caught this bug, so can confirm. Shaking furiously and rotating the device until the dialog stopped popping up helped. May be disabling rageshake straight from the dialogue could be considered as an alternative to disabling it by default for non-authenticated users? |
Not sure since when (because I do not use the app very often anymore) but with the possibility to deactivate rageshakes in the welcome screen directly, this issue can be closed (though it would of course be ideal if Element was able to also detect and handle the sensor failure of my phone automatically). |
Describe the bug
Directly when opening the app, I get the message "shaking your phone in frustration" (which I am not doing at all) allowing to send a bug report. Sending the report works (and I have done it some time ago). Choosing the "no"-option, closes the message but immediately reopens it. Choosing the "Settings"-Option crashes the app.
Expected behavior
Normally starting the app without any messages.
Smartphone
Additional context
App version and store: [1.0.11 / F-Droid] (problem has been the same for all previous versions of Element)
There have been some hints in the past that at least one of the sensors of the phone does not work properly. However, other apps seem to be able to detect and compensate for that. It would be nice if Element could do so, too, because currently I am simply not able to use the app.
The text was updated successfully, but these errors were encountered: