Bug #390
jelly bean 4.2 =broken=
| Status: | Closed | Start date: | 11/26/2012 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | devrandom | % Done: | 0% | |
| Category: | - | |||
| Target version: | v11 - January Judo | |||
| Component: |
Description
After the official jelly bean 4.2 update on my Galaxy Nexus, Gibberbot stopped working properly.
The screen flickers randomly. I tried a uninstall/reinstall, and yet the problem is still there.
It is triggered after moving back to the account list (or other menus) after opening a chat window and/or minimizing it to background.
Once the flickering starts, it is impossible to stop. I have to force kill the app.
Associated revisions
Workaround for activity infinite relaunch
fixes #390
Merge pull request #390 from n8fr8/bugs_v13_still_coming
Bugs v13 still coming
Removed XMPPURI scheme replaced with share link
Fixes #390
History
#1 Updated by devrandom about 5 years ago
- Status changed from New to In Progress
I have a temporary workaround here:
https://github.com/devrandom/Gibberbot/commit/a66766f7e6488e78659a50611cfd2136803f1c00
We can't be setting the locale at that point.
#2 Updated by devrandom about 5 years ago
- Assignee set to devrandom
- Target version set to v11 - January Judo
#3 Updated by devrandom about 5 years ago
To replicate this on a Jelly Bean MR1 (4.2) emulator:
- Start the app
- Go to an unconfigured account and click on the username text field
- pull down the notification bar, and click on the keyboard config
- Toggle the enable state of the hardware keyboard
#4 Updated by devrandom about 5 years ago
I've redone the fix, pull request is here: https://github.com/guardianproject/Gibberbot/pull/185
#5 Updated by devrandom about 5 years ago
Another way to replicate:
Configure an account. Kill the app. Start it from the launcher in landscape mode.
#6 Updated by devrandom about 5 years ago
- Status changed from In Progress to Resolved
#7 Updated by n8fr8 almost 5 years ago
- Status changed from Resolved to Closed