QuasselDroid-ng issueshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues2023-09-18T14:41:24Zhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/248QD closes immediately after connecting when using Gesture Navigation2023-09-18T14:41:24ZJanne Mareike KoschinskiQD closes immediately after connecting when using Gesture Navigationhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/245ipv6 in connection list gets formatted as f00::ba2:4242 instead of [f00::ba2]...2022-05-17T17:21:18ZJanne Mareike Koschinskiipv6 in connection list gets formatted as f00::ba2:4242 instead of [f00::ba2]:4242https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/240Query with services cause unneeded notifications2022-01-10T05:17:08ZJim RamsayQuery with services cause unneeded notificationsIf I'm in a query chat with an IRC service, such as `/query nickserv` and say `help`, I get a flurry of notifications even though I'm in the chat buffer where those messages are coming in.
I don't need or want a notification for message...If I'm in a query chat with an IRC service, such as `/query nickserv` and say `help`, I get a flurry of notifications even though I'm in the chat buffer where those messages are coming in.
I don't need or want a notification for messages I'm actively reading.1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/239Reduce chat drawer grab range when expanding message compose box2022-01-10T05:17:13ZShane SynanReduce chat drawer grab range when expanding message compose box1. Connect to core, open buffer to send message
2. Expand the message box for composing messages
3. Start typing or paste a long message
4. Try to hold-select text near the left side of the screen
5. Experience fight with the chat d...1. Connect to core, open buffer to send message
2. Expand the message box for composing messages
3. Start typing or paste a long message
4. Try to hold-select text near the left side of the screen
5. Experience fight with the chat drawer
*To be filled out more if needed when not on mobile*2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/238Pressing Up arrow key clears current/unsent message without saving it to mess...2022-01-10T05:17:20ZShane SynanPressing Up arrow key clears current/unsent message without saving it to message history### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message ...### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message in the input history)
4. Type another, different message, but don't send it
5. Press the Up arrow key
6. Observe the results
7. Press the Down arrow key
8. Observe the results
### Expected
* After pressing the Up arrow, the current message is replaced with the most recently sent message
* After pressing the Down arrow, the most recently sent message is replaced with the unsent, still-being-composed message
This matches the behavior of Quassel desktop.
### Actual
* :heavy_check_mark: After pressing the Up arrow, the current message is replaced with the most recently sent message
* :x: After pressing the Down arrow, the most recently sent message is replaced with.. **nothing - the unsent, still-being-composed message is now lost**
### Details
Quasseldroid [v1.3.3](https://git.kuschku.de/justJanne/QuasselDroid-ng/commit/b622ad63056b6054b06e09f8e1f1ef2b0c3aaf9a )
Using a USB keyboard with the USB OTG adapter that comes in the Pixel box, on Android 11, Pixel 4 XL.
*Priority is set to high due to the potential to lose chat messages in the middle of writing them on ChromeOS or with a USB/Bluetooth keyboard. This may be a smaller impact, though.*1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/237Up/down arrow keys don't move cursor in multi-line message edit mode2022-01-10T05:17:24ZShane SynanUp/down arrow keys don't move cursor in multi-line message edit mode### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message ...### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message in the input history)
4. Expand the message input box to switch to multi-line edit mode
5. Type a long enough message that it wraps across several lines (e.g. copy-paste a few words)
6. With the input caret/cursor on the bottom, press the Up arrow key
7. Observe the results
### Expected
The input caret/cursor navigates upwards through the text, as happens with e.g. QKSMS on Android or Quassel desktop and Kate on KDE.
Only when the input caret/cursor is at the very top of the message (or anytime in single-line edit mode) should the message history be accessed.
### Actual
Quasseldroid interprets the up arrow as a request to switch to the message history, despite being in multi-line edit mode.
### Details
Quasseldroid [v1.3.3](https://git.kuschku.de/justJanne/QuasselDroid-ng/commit/b622ad63056b6054b06e09f8e1f1ef2b0c3aaf9a )
Using a USB keyboard with the USB OTG adapter that comes in the Pixel box, on Android 11, Pixel 4 XL.
*Feel free to edit the priority as desired - I'm not sure how many folks use Quasseldroid with a keyboard - ChromeOS + USB/Bluetooth keyboards on Android, possibly?*1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/236Black cursor on AMOLED theme2022-01-10T05:17:54ZPeGaSuSBlack cursor on AMOLED themeWhen editing settings on AMOLED theme, we have a black cursor on black background.
The input box while chatting works fine though, with the cursor being orange-ish.
Screenshot below:
![Screenshot_20210104_083233_com.iskrembilen.quasseld...When editing settings on AMOLED theme, we have a black cursor on black background.
The input box while chatting works fine though, with the cursor being orange-ish.
Screenshot below:
![Screenshot_20210104_083233_com.iskrembilen.quasseldroid](/uploads/c15aa3604fbec035675f72bdbae9a6eb/Screenshot_20210104_083233_com.iskrembilen.quasseldroid.jpg)2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/228Double-tap message to insert nickname re-appends nickname after every app switch2022-01-10T05:19:39ZShane SynanDouble-tap message to insert nickname re-appends nickname after every app switch## Steps
1. Connect to core
2. In `…` → `Client Settings`, under `Autocomplete`, ensure `Double tap to autocomplete` is enabled (the default)
3. Open an IRC channel and load backlog until normal chat messages are visible
* E.g. `#...## Steps
1. Connect to core
2. In `…` → `Client Settings`, under `Autocomplete`, ensure `Double tap to autocomplete` is enabled (the default)
3. Open an IRC channel and load backlog until normal chat messages are visible
* E.g. `#quasseldroid`
4. Focus the chat input box
5. Double tap a message from any user
* E.g. `Not-####` the notification bot, or `justJanne`
6. Observe the chat input box
7. Go to the home screen via the Home button/gesture
* Do not use the Back button/gesture as that will destroy the activity
8. Open Quasseldroid
9. Observe the chat input box
10. Optional: keep going to the home screen and returning to Quasseldroid, or switch apps, or lock the screen/unlock
11. Optional: to workaround the issue, switch to another buffer and back, or use the Back button/gesture to finish the activity
## Expected
Only one instance of `nickname: ` is visible, e.g. `justJanne: `.
## Actual
Every time Quasseldroid regains focus, another instance of `nickname` is appended, e.g. `justJanne: justJanne justJanne`.
## Details
Tested using Android 10 with Gboard on a Pixel 4 XL.1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/227Server Redirect Notices and User Redirect Notices should be independent2022-01-10T05:15:34ZPeGaSuSServer Redirect Notices and User Redirect Notices should be independentAs explained on IRC:
```
[12:15:49] <PeGaSuS> justJanne: I found a weird behaviour in Quasseldroid in my phone (Huawei P20 Lite). Menu > Client Settings > Message Redirection > Enable "Redirect User Notices"
[12:15:49] <PeGaSuS> Tap the ...As explained on IRC:
```
[12:15:49] <PeGaSuS> justJanne: I found a weird behaviour in Quasseldroid in my phone (Huawei P20 Lite). Menu > Client Settings > Message Redirection > Enable "Redirect User Notices"
[12:15:49] <PeGaSuS> Tap the back arrow. Menu > Client Settings > Message Redirection > "Redirect User Notices" and "Redirect Server Notices" will be enabled.
[12:15:49] <PeGaSuS> Disable "Redirect Server Notices", tap back arrow, Menu > Client Settings > Message Redirection > All redirects will be disabled
[12:17:10] <PeGaSuS> shouldn't "User Notices" and "Server Notices" be independent?
```1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/225Crash on rotation from landscape to portrait after connection [v1.2.26]2020-03-27T12:10:52ZShane SynanCrash on rotation from landscape to portrait after connection [v1.2.26]## Steps
1. Ensure device is in portrait orientation
2. Connect to core
3. Rotate to landscape
4. Rotate back to portrait
## Expected
Quasseldroid handles the rotation.
## Actual
Quasseldroid crashes.
## Details
Android 10, Pixel ...## Steps
1. Ensure device is in portrait orientation
2. Connect to core
3. Rotate to landscape
4. Rotate back to portrait
## Expected
Quasseldroid handles the rotation.
## Actual
Quasseldroid crashes.
## Details
Android 10, Pixel 4 XL.
I've sent the crash logs to `support` at `kuschku.de` as of 12:41 AM EST, subject `Crashes on rotation with v1.2.26`. If it's safe to post the logs here, I can attach them to this issue, too.
Snippet:
```
{
"application": {
"buildConfig": {
"APPLICATION_ID": "com.iskrembilen.quasseldroid",
"BUILD_TYPE": "release",
"DEBUG": false,
"FANCY_VERSION_NAME": "<a href=\"https://git.kuschku.de/justJanne/QuasselDroid-ng/commit/4a9409a67f3b87a935d87524558fbf2621696a76\">v1.2.25-1-g4a9409a6</a>",
"FLAVOR": "",
"GIT_COMMIT_DATE": 1585270969,
"GIT_HEAD": "4a9409a67f3b87a935d87524558fbf2621696a76",
"VERSION_CODE": 1265,
"VERSION_NAME": "v1.2.25-1-g4a9409a6"
},
"installationSource": "com.android.vending",
"versionCode": 1265,
"versionName": "v1.2.25-1-g4a9409a6"
},
"crash": {
"cause": {
"localizedMessage": "Wrong state class, expecting View State but received class androidx.coordinatorlayout.widget.CoordinatorLayout$SavedState instead. This usually happens when two views of different type have the same id in the same hierarchy. This view's id is id/layout_main. Make sure other views do not use the same id.",
"message": "Wrong state class, expecting View State but received class androidx.coordinatorlayout.widget.CoordinatorLayout$SavedState instead. This usually happens when two views of different type have the same id in the same hierarchy. This view's id is id/layout_main. Make sure other views do not use the same id.",
[…]
```https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/224Forced immersive mode results in shifting entire app UI when opening keyboard2020-10-07T08:39:33ZShane SynanForced immersive mode results in shifting entire app UI when opening keyboard## Steps
1. Connect to the device via ADB, or otherwise access an app that allows changing global preferences
2. Force system into navigation immersive mode
* `adb shell settings put global policy_control immersive.navigation=apps`...## Steps
1. Connect to the device via ADB, or otherwise access an app that allows changing global preferences
2. Force system into navigation immersive mode
* `adb shell settings put global policy_control immersive.navigation=apps`
3. Open Quasseldroid, connect to core
4. Tap the message input box to reveal the IME/keyboard
5. Tap the down arrow to hide the IME/keyboard
6. Optional: revert back to normal immersive mode
* `adb shell settings put global policy_control null`
## Expected
Revealing the keyboard reduces the amount of space available to Quasseldroid's UI, shrinking it down.
## Actual
Revealing the keyboard shifts the entire Quasseldroid UI upwards, making the ActionBar and upper UI elements inaccessible until the keyboard is hidden.
## Details
Tested using Android 10 with Gboard on a Pixel 4 XL.
I suspect this may be a bug with Android itself and not the fault of Quasseldroid. However, other apps (Firefox for Android, non-preview, the Contacts app, YouTube) appear to handle this correctly.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/223Expanded (multi-line) message input box won't collapse with swipe down except...2022-01-10T05:20:14ZShane SynanExpanded (multi-line) message input box won't collapse with swipe down except under Send button## Steps
1. Connect to core
2. Swipe up message input box
3. Swipe down message input box by dragging `Write a message…` down
4. Observe message input box state, expanded or collapsed
5. If message input box is collapsed, swipe up m...## Steps
1. Connect to core
2. Swipe up message input box
3. Swipe down message input box by dragging `Write a message…` down
4. Observe message input box state, expanded or collapsed
5. If message input box is collapsed, swipe up message input box again
6. Swipe down message input by dragging underneath the `>` Send button
## Expected
For both steps 3 and 6, the expanded message input box collapses.
## Actual
The expanded message input box does not react to drags in step 3, but step 6 will collapse the input box.2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/222@mention, "Mention" in user profile, or double-tapping message won't insert n...2020-03-27T12:10:55ZShane Synan@mention, "Mention" in user profile, or double-tapping message won't insert nickname [v1.2.26]## Steps
1. Connect to core
2. Select a channel with multiple users inside it
* E.g. `#quasseldroid` on freenode
3. Verify `Client Settings` are set to enable auto-completion as per defaults
* `Sender Autocomplete` checked
...## Steps
1. Connect to core
2. Select a channel with multiple users inside it
* E.g. `#quasseldroid` on freenode
3. Verify `Client Settings` are set to enable auto-completion as per defaults
* `Sender Autocomplete` checked
* `Double tap to autocomplete` checked
* `Show after prefix` checked
* `Autocomplete Nicknames` checked
4. Open the nickname list
5. Tap on a nickname to open the user profile
* E.g. `justJanne`
6. Tap `Mention`
7. Observe input widget, clearing any text if successful
8. Scroll to a message from a user
9. Double tap the message
10. Observe input widget, clearing any text if successful
11. Give focus to the input widget, and start typing `@` and the first letters of a nickname in the channel
* E.g. `@justJ`
12. Observe auto-complete results
13. Start typing the first letters of a nickname without an `@` prefix
* E.g. `justJ`
14. Double-tap the nickname text
15. Observe auto-complete action
## Expected
In all cases (step 7, 10, 12, 15), the chosen nickname is filled in or suggested via auto-complete.
## Actual
When double-tapping the nickname text (step 15), the chosen nickname is filled in. In all other cases (step 7, 10, 12), the nickname is not filled in or suggested.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/221Multi-line message edit mode won't change Enter key on keyboard [v1.2.26]2020-03-27T12:10:57ZShane SynanMulti-line message edit mode won't change Enter key on keyboard [v1.2.26]## Steps
1. Connect to core
2. Swipe up on the input chat box to enter multi-line message edit mode
## Expected
* Keyboard switches the "tab to next input" Enter key into the selected setting, e.g. a return/newline key.
## Actual
* K...## Steps
1. Connect to core
2. Swipe up on the input chat box to enter multi-line message edit mode
## Expected
* Keyboard switches the "tab to next input" Enter key into the selected setting, e.g. a return/newline key.
## Actual
* Keyboard continues to show the "tab to next input" Enter key which appears to do nothing.
## Details
Using Gboard on Android 10, Pixel 4 XL. Worked before the most recent stable update (2019 builds).
This may be [related to issue #220](https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/220 ).
### Screenshot of the issue
![Screenshot of Quasseldroid's expanded message compose view, showing the keyboard with a "tab to next input" key instead of an "Enter" key](https://zorro.casa/sync/Hosting/Utilities/Quassel/QuasselDroid/Development/issues/multi-line-message-edit-wrap-fails/Multi-line%20message%20editing%20line%20doesn%27t%20wrap.png#v1 )https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/220Multi-line message edit mode won't wrap text [v1.2.26]2020-03-27T12:10:59ZShane SynanMulti-line message edit mode won't wrap text [v1.2.26]## Steps
1. Connect to core
2. Type or paste a message in the chat box that's long enough to scroll
* Predictive text suggestions helpfully generated this: `I will be there at least with the tip of the iceberg lettuce and tomato an...## Steps
1. Connect to core
2. Type or paste a message in the chat box that's long enough to scroll
* Predictive text suggestions helpfully generated this: `I will be there at least with the tip of the iceberg lettuce and tomato and onion chips`
3. Swipe up on the chat box to enter multi-line mode
## Expected
* Text wraps at the edge of the screen into multiple lines.
## Actual
* Text remains in a single line, scrolling horizontally.
## Details
This may be [related to issue #221](https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/221 ).
### Screenshot of the issue
![Screenshot of Quasseldroid's expanded message compose view, showing a fragment of the sentence from above on a single line instead of wrapping it: "e iceberg lettuce and tomato and onion chips"](https://zorro.casa/sync/Hosting/Utilities/Quassel/QuasselDroid/Development/issues/multi-line-message-edit-wrap-fails/Multi-line%20message%20editing%20line%20doesn%27t%20wrap.png#v1 )https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/217reconnect jumps to latest messages2022-01-10T05:21:34Zhyperfektreconnect jumps to latest messagesIf the connection to the core is reacquired while reading in a channel, the view reloads and jumps to the latest messages.
This is undesirable especially on mobile connections, where it might happen very frequently.
Version: 1.2.24If the connection to the core is reacquired while reading in a channel, the view reloads and jumps to the latest messages.
This is undesirable especially on mobile connections, where it might happen very frequently.
Version: 1.2.242.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/207Graphic glitch in Chatlist - Topicline Sliding2019-06-17T08:50:21ZFireAntyGraphic glitch in Chatlist - Topicline SlidingThe Topicline under the Channel name slides if Topic is longer then the Space given.
This results in a glitch, idk if QT-Error or QD or maybe specific Problem of my Device.
It slides up to a white bar, see Screenshot ![49jml](/uploads/...The Topicline under the Channel name slides if Topic is longer then the Space given.
This results in a glitch, idk if QT-Error or QD or maybe specific Problem of my Device.
It slides up to a white bar, see Screenshot ![49jml](/uploads/4f29b4acef5c3cc917df494ed2557c8a/49jml.jpg)
I Use latest Beta on LOS 16 (Android 9) on a Lenovo Yoga Tab 3 Plus and the AMOLED-Theme
I personal would even like to be able to disable the Topicline, so Chatlist is getting shorter and needs less scrolling…couldn't find an option for this.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/205Background execution notification/icon visibility can't be configured on pre-6.02019-06-07T20:19:54ZJanne Mareike KoschinskiBackground execution notification/icon visibility can't be configured on pre-6.0Janne Mareike KoschinskiJanne Mareike Koschinskihttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/204Auto-reconnects when remotely disconnected/etc2019-06-17T09:02:46ZShane SynanAuto-reconnects when remotely disconnected/etc## Test case
### Steps
1. Connect two clients to Quassel core, at least one of them Quasseldroid
* E.g. desktop and Quasseldroid
2. Put Quasseldroid in the background
3. In the `Core Info` menu of the secondary client, disconnect ...## Test case
### Steps
1. Connect two clients to Quassel core, at least one of them Quasseldroid
* E.g. desktop and Quasseldroid
2. Put Quasseldroid in the background
3. In the `Core Info` menu of the secondary client, disconnect the Quasseldroid that is in the background
*Update: This seems to happen even when disconnecting locally, too!*
### Expected
Quasseldroid stays disconnected.
### Actual
Quasseldroid eventually reconnects.
## Additional
Running [latest Quasseldroid, v1.2.2](https://git.kuschku.de/justJanne/QuasselDroid-ng/tags/v1.2.2 ), and Quassel core 0.13.1, and only started happening with the recent connection logic rewrite.
I'm not sure exactly how long this takes, or if connection state changes trigger this. I'll continue to investigate this.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/202Ignore rules have inconsistent case-sensitivity2019-05-18T13:40:05ZkythyriaIgnore rules have inconsistent case-sensitivityIn Quassel Desktop (0.13.0), dynamic ignores (of messages and senders) are case-insensitive. In QuasselDroid (1.0.5), they are case-sensitive. For instance, if you have an ignore rule for `/justjanne.*/` and receive a message from `JustJ...In Quassel Desktop (0.13.0), dynamic ignores (of messages and senders) are case-insensitive. In QuasselDroid (1.0.5), they are case-sensitive. For instance, if you have an ignore rule for `/justjanne.*/` and receive a message from `JustJanne`, Desktop will ignore the message, while QuasselDroid will happily display it and generate notifications/sounds as normal. This also applies to wildcard and message rules.
The expected behaviour is case-insensitivity, as Desktop does (and which is consistent with how casing is treated for decidng what buffer a message goes into).