QuasselDroid-ng issueshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues2022-01-10T05:15:03Zhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/7Visual Channel Mode Editor2022-01-10T05:15:03ZJanne Mareike KoschinskiVisual Channel Mode Editorhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/8Visual Ban List2022-01-10T05:15:03ZJanne Mareike KoschinskiVisual Ban Listhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/43Collapse multiple join/quit messages into one, collapse netsplits2022-01-10T05:15:01ZJanne Mareike KoschinskiCollapse multiple join/quit messages into one, collapse netsplitshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/10Network Channel List Dialog2022-01-10T05:15:00ZJanne Mareike KoschinskiNetwork Channel List Dialoghttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/20Support for uploading of files to sharing services2022-01-10T05:15:03ZJanne Mareike KoschinskiSupport for uploading of files to sharing serviceshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/22Automatically suggest submitting long content to a paste service2022-01-10T05:15:03ZJanne Mareike KoschinskiAutomatically suggest submitting long content to a paste serviceDepends on #20Depends on #20https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/29Support for Android Wear, Pebble, etc2022-01-10T05:15:03ZJanne Mareike KoschinskiSupport for Android Wear, Pebble, etchttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/33Fulltext search2022-01-10T05:15:04ZJanne Mareike KoschinskiFulltext searchhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/36Theme Preview UI2022-01-10T05:15:03ZJanne Mareike KoschinskiTheme Preview UIAllow previewing themes in a gallery before applying themeAllow previewing themes in a gallery before applying themehttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/40Allow custom sender colors2022-01-10T05:15:00ZJanne Mareike KoschinskiAllow custom sender colorshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/47Battery-Saving FCM Push Notifications2022-01-10T05:15:03ZJanne Mareike KoschinskiBattery-Saving FCM Push Notificationshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/54Add in client settings import/export feature.2022-01-10T05:15:00ZdeathspawnAdd in client settings import/export feature.Could possibly use a text file and then we can back it up somewhere if needed and restore easily. Would also have to add in warnings if a settings file won't work for a new version for whatever reason.Could possibly use a text file and then we can back it up somewhere if needed and restore easily. Would also have to add in warnings if a settings file won't work for a new version for whatever reason.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/75Add "jump to markerline" option to resume from last read2022-01-10T05:15:03ZShane SynanAdd "jump to markerline" option to resume from last readThere's an easy method for jumping to the present, the double down-arrow on the bottom right when scrolling down. However, there's no easy way to jump to where the marker line is, akin to <kbd>Ctrl</kbd>+<kbd>k</kbd> on desktop.
This m...There's an easy method for jumping to the present, the double down-arrow on the bottom right when scrolling down. However, there's no easy way to jump to where the marker line is, akin to <kbd>Ctrl</kbd>+<kbd>k</kbd> on desktop.
This might take the form of a menu item, a contextual button that shows when scrolling up, etc.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/93Add contextual reminders of missing needed core features2022-01-10T05:15:03ZShane SynanAdd contextual reminders of missing needed core features### Steps
1. Connect to a core missing needed features, e.g. `CoreSideHighlights`
2. Accept the missing core features dialog
* This includes tapping outside of the dialog, which can happen accidentally
3. Access client notificatio...### Steps
1. Connect to a core missing needed features, e.g. `CoreSideHighlights`
2. Accept the missing core features dialog
* This includes tapping outside of the dialog, which can happen accidentally
3. Access client notification settings, configure core highlights, etc
### Expected
Some gentle reminder of missing core features that can be tapped to reveal the dialog again.
This hopefully reduces confusion for anyone who taps `Accept`/skips dialog, uses QuasselDroid for a while, then notices things don't work and wonders why. It also would solve the (*admittedly contrived*) case of connecting to a core missing one feature, restoring that core to an older backup missing more features, and having no way to see this in QuasselDroid.
### Actual
The dialog only shows once.
### Additional
Perhaps this could be integrated into [the `Core Info` activity](https://git.kuschku.de/justJanne/QuasselDroid-ng/issues/24 ), with Settings providing some sort of tappable item to launch the core info window? A button/bar/activatable item there could then re-launch the missing features dialog.
The current approach seems fine for QuasselDroid in beta where people are more likely to pause to read dialogs as they expect new things, but this may want to be addressed before a full release.
*Disclosure: I am biased given I've written a few contextual info/warning bars in the Quassel desktop client. I have no idea how well those work in practice.*https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/97Add per-chat input and sent message history2022-01-10T05:15:00ZShane SynanAdd per-chat input and sent message history### Steps
1. Connect to core
2. Open a buffer, send a message
3. Type another message, do not send it
4. Switch to buffer that hasn't been used
5. Open chat history
6. Switch back to first buffer
7. Open chat history
### Expected...### Steps
1. Connect to core
2. Open a buffer, send a message
3. Type another message, do not send it
4. Switch to buffer that hasn't been used
5. Open chat history
6. Switch back to first buffer
7. Open chat history
### Expected
When switching to an unused buffer, the input box text and message history should clear.
When switching back to first used buffer, the input box text and message history from earlier steps should come back.
### Actual
Input box text and message history don't change when switching buffers, staying global.
### Additional
Given the buffer list slides on top of the input box, it implies it is higher in the hierarchy, as if it is linked. Also, per-chat input and sent message history matches some other messaging apps and Quassel desktop.
Without this, it's easier to send a message to the wrong channel if you briefly switch channels to check on a notification, then want to reply. Global history also makes it harder to interrupt a reply in one place to respond elsewhere.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/98Queue/save messages sent when offline/connection dropped2022-01-10T05:15:04ZShane SynanQueue/save messages sent when offline/connection dropped### Steps
1. Connect to core
2. Start writing an awesome, long message
3. Enable airplane mode (*e.g. as if out of signal range*)
4. Try to send
**Or...**
1. Connect to core over high-latency link
2. Write a message, send it
3. E...### Steps
1. Connect to core
2. Start writing an awesome, long message
3. Enable airplane mode (*e.g. as if out of signal range*)
4. Try to send
**Or...**
1. Connect to core over high-latency link
2. Write a message, send it
3. Enable airplane mode before message successfully reaches core
### Expected
* Messages are queued if sent when offline/connection lost
* Automatically sent when back online
* Prompted to send when back online
* Sending messages is disallowed when offline, visibly disabling the send button
* Something else..?
### Actual
In either case messages don't send and may disappear. In the latter it can be found in message history.
### Additional
Queuing messages in the case of connection failing may require core-side changes if it's not possible to know what message ID will be used. It should still be possible to queue messages for reconnect, or otherwise warn of connection loss.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/104Hint at buffer list on left when no buffer chosen2022-01-10T05:15:00ZShane SynanHint at buffer list on left when no buffer chosen### Steps
1. Disconnect QuasselDroid, clear from Recents (*remove any saved activity state*)
2. Connect to core
3. Hide buffer list *without choosing a buffer*
### Expected
The area where chat history would normally show contains a g...### Steps
1. Disconnect QuasselDroid, clear from Recents (*remove any saved activity state*)
2. Connect to core
3. Hide buffer list *without choosing a buffer*
### Expected
The area where chat history would normally show contains a graphic and brief text hinting at the buffer list.
For example...
**`Let's get talking`**
`Pick a conversation on the left`
...below an icon of an arrow above a list pointing to the left, perhaps a cross between [the `list` icon](https://material.io/tools/icons/?icon=list&style=baseline ) and [the `arrow_left` icon](https://material.io/tools/icons/?icon=arrow_left&style=baseline).
But with more suitable phrasing and icon.
### Actual
The area where chat history shows is blank, no clues given for the next step.
### Additional
Even if the buffer list always opened, it may be more friendly to nudge towards the left sidebar.
**Example screenshot of the [Transistor radio app](https://github.com/y20k/transistor) with no stations added**
![Transistor radio app showing the first-run screen, with 'Get Started' pointing pointing up to the 'Add new station' button](/uploads/1e3e612855422614757441099a4ab4a3/transistor-radio-first-run.png)https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/106Simplify scrolling past/collapsing avatars in User Details2022-01-10T05:15:04ZShane SynanSimplify scrolling past/collapsing avatars in User Details### Steps
1. Connect to core
2. Open channel, then open Nick list
3. Rotate to landscape orientation if not already
4. Tap a nickname with an avatar
5. Try to view nick details below the image
### Expected
Tapping on the user avata...### Steps
1. Connect to core
2. Open channel, then open Nick list
3. Rotate to landscape orientation if not already
4. Tap a nickname with an avatar
5. Try to view nick details below the image
### Expected
Tapping on the user avatar collapses it to a fraction of the visible screen area, or if collapsed, expands it to take up the full size.
Scrolling with swiping works as before.
### Actual
Collapsing avatars requires scrolling, possibly a lot of scrolling for a tall portrait avatar with QuasselDroid in landscape orientation.
### Additional
The Contacts app in AOSP/LineageOS 14.1 offers one half of this functionality with contact avatars - tapping the avatar expands it to fill the screen. It doesn't seem to offer the tap-to-collapse functionality.
**Example video, scrolling past portrait Matrix avatar in User Details**
![Picking a nick from the nick list with a portrait Matrix avatar, scrolling up and down to reveal information, taking several swipes to do so](/uploads/d94e344e732e920c9c9cf3ed24f561fc/ScreenRecord-2018-05-20-13-16-31-trimmed.webm)
**Example video, Contacts expanding avatar by tapping it**
![Scrolling a contact in Contacts, partially collapsing avatar, then tapping it to expand avatar to full size](/uploads/7f7ab6d5c06105f58e81e3269e955cda/ScreenRecord-2018-05-20-13-28-41-trimmed.webm)https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/113Few ideas that could be handy to have in QuasselDroid2022-01-10T05:15:03ZPeGaSuSFew ideas that could be handy to have in QuasselDroid* [ ] In networks like Freenode, that have user mode **+g** (https://freenode.net/kb/answer/usermodes), would be handy to have something like tapping in the notice to add the nick that's trying to message us to the accept list, like thi...* [ ] In networks like Freenode, that have user mode **+g** (https://freenode.net/kb/answer/usermodes), would be handy to have something like tapping in the notice to add the nick that's trying to message us to the accept list, like this: https://imgur.com/a/38JqJ0n
* [x] We currently have no way to know how many users are present in a channel. As we have a user list button I was wondering if it would be possible to add a small `badge` with the number of users bellow it or even in the top of the user list (like the current implementation in QuasselClient).
* [ ] When opening the channel topic dialogue, just to see the current topic or to edit it, would be nice to have information about the setter and the set date.
According to justJanne: `won’t be possible without core changes because quassel does not store or transmit that info. another thing for 0.14/0.15`
* [x] Now that we have the possibility to chose between round or square avatars, I think that would be nicer to have the square ones with rounded corners.
For the time being these are the things that I think that could make QuasselDroid look nicer in long term.
~"Type: Feature"https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/114Reorganize client settings to avoid 'wall of toggles'2022-01-10T05:15:03ZShane SynanReorganize client settings to avoid 'wall of toggles'### Idea
Structure the `Client Settings` to further group settings according to type or functionality.
One *possible* example...
* `Appearance`
* `General` (*implicit subcategory, maybe no header*): show lag, keep screen active, etc
...### Idea
Structure the `Client Settings` to further group settings according to type or functionality.
One *possible* example...
* `Appearance`
* `General` (*implicit subcategory, maybe no header*): show lag, keep screen active, etc
* `Language and input`: language, enter key on keyboard, current `Autocomplete` category
* `Messages`: current messages category, with subcategory for `Avatars` (*disabled when separate nicknames is disabled*)
* `Theming`: theme (*eventually will have theme preview gallery and custom colors*)
* `Notifications`: current `Notifications` category
* `Connection`
* `General` (*implicit subcategory, maybe no header*): show notification
* `Backlog`: current `Backlog` category
* `Certificates`: access to current certificate manager
* *Any additional client-side connection parameters, e.g. session timeout if needed*
Or something else?
This will include [simplifying/clarifying the `Show Avatars` settings](https://git.kuschku.de/justJanne/QuasselDroid-ng/issues/163 ).
### Additional
I'm not entirely sure how this would go, with activity fragments, with different header levels, or whatever... It just seems.. not ideal to put a wall of options in front of someone trying to find a specific setting, or to someone new to the client.
`Messages`, if possible and only when there's room, could also show a possibly-scrollable preview of the new message layout, like Discord does. To better suit space-constrained phones, it could be a `Preview` option to show a test conversation, allowing testing realnames, avatars, etc without backing out and hunting for a conversation that has everything you need.
**Example screenshot of Discord's Appearance settings page**
![Discord's Appearance settings page, viewable at https://discordapp.com/ after making a guest account and accessing settings. It shows a preview of the message layout above.](https://zorro.casa/sync/Hosting/Utilities/Quassel/QuasselDroid/Development/issues/organize-client-settings/Discord%20appearance%20settings.png )https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/119Dismissing notification marks entire buffer as read, not just highlights2022-01-10T05:15:03ZShane SynanDismissing notification marks entire buffer as read, not just highlights### Steps
1. Connect to core
2. Receive highlight in channel
3. Receive non-highlights in that same channel
4. Swipe away notification for highlight from that channel
### Expected
The highlight status is removed from the channel, bu...### Steps
1. Connect to core
2. Receive highlight in channel
3. Receive non-highlights in that same channel
4. Swipe away notification for highlight from that channel
### Expected
The highlight status is removed from the channel, but the other messages are not marked as read.
### Actual
The entire channel is marked as read, making it harder to see what messages may be missed.
### Additional
This depends on protocol changes to the core, and may need the core-side notification system (not just core-side highlights) in order to mark notifications as dismissed without clearing a channel's activity.
Alternatively, Quasseldroid can mark everything up to the swiped-away notification as read, but this may risk confusion among users instead of the "swipe notification == marks all as read" behavior.
This could possibly involve messing with the last read markerline to re-set that to right after the highlight.. but that still risks confusion.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/124Option for last message instead of channel topic2022-01-10T05:15:03ZVolkorOption for last message instead of channel topicWhere the green part is on the image below, have an option to show the latest message sent from that channel, would be better for keeping track of activity.
Also, having the icons on the left change colour depending on activity would be...Where the green part is on the image below, have an option to show the latest message sent from that channel, would be better for keeping track of activity.
Also, having the icons on the left change colour depending on activity would be a nice thing to have too.
![image](https://thecum.zone/e7d90c4b67.png)https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/125Batch deletion for PM and parted channels buffers2022-01-10T05:15:01ZPeGaSuSBatch deletion for PM and parted channels buffers* [ ] On PM and parted channels buffers we have the option to delete them, but we must do it one by one.
Having an option to batch delete would be nice.
* [ ] On channels that we're still in, probably also add the option to delete i...* [ ] On PM and parted channels buffers we have the option to delete them, but we must do it one by one.
Having an option to batch delete would be nice.
* [ ] On channels that we're still in, probably also add the option to delete it, which would make the user part the channel and then delete it (would spare the work of parting first and delete after).https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/127Option to mark all channels as read, per network basis2022-01-10T05:15:01ZPeGaSuSOption to mark all channels as read, per network basis* [ ] Normally every user is in several channels on a network, and some are more important than others. Would be nice to have an option to mark as channels as read, per network basis, after we take a look into the most important ones.* [ ] Normally every user is in several channels on a network, and some are more important than others. Would be nice to have an option to mark as channels as read, per network basis, after we take a look into the most important ones.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/136Optionally use visibility-optimized mIRC colors2022-01-10T05:15:03ZShane SynanOptionally use visibility-optimized mIRC colorsOffer a setting to choose between accurate mIRC colors, and colors optimized for visibility.
E.g. color blue (2 or 4) with `Material Dark` theme.
*Thanks to `rubenwardy` from Freenode/`#quasseldroid` for the idea!*Offer a setting to choose between accurate mIRC colors, and colors optimized for visibility.
E.g. color blue (2 or 4) with `Material Dark` theme.
*Thanks to `rubenwardy` from Freenode/`#quasseldroid` for the idea!*https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/139Request: Increase "Real Name" display length2022-01-10T05:15:04ZChris KrauseRequest: Increase "Real Name" display lengthI was just wondering if it was possible to increase the length of the displayed user "Real Name" that is shown next to their nickname. Its usually more then enough, but I sometimes see issues with bot users like relay programs that tie t...I was just wondering if it was possible to increase the length of the displayed user "Real Name" that is shown next to their nickname. Its usually more then enough, but I sometimes see issues with bot users like relay programs that tie the IRC channel to other chat services that have the full program name and revision number as their "Real Name". Those users often see it cut by 1-2 characters. And in the case of a relay program, you will see it all the time.
Super low priority, but it would really be nice if it could be extended by maybe 5 characters.
Thank you!https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/141Support automatic Light/Dark mode, e.g. via Theme.AppCompat.DayNight2022-01-10T05:15:04ZShane SynanSupport automatic Light/Dark mode, e.g. via Theme.AppCompat.DayNight### Idea
* Automatically switch between Light and Dark theme variants
* Time of day
* Using `Theme.AppCompat.DayNight` to follow system-wide theme, e.g. as per [the Android 10 developer documentation](https://developer.android.com/gu...### Idea
* Automatically switch between Light and Dark theme variants
* Time of day
* Using `Theme.AppCompat.DayNight` to follow system-wide theme, e.g. as per [the Android 10 developer documentation](https://developer.android.com/guide/topics/ui/look-and-feel/darktheme ) and [LineageOS' Styles API](https://wiki.lineageos.org/sdk/api/styles.html )
### Rationale
Dark theme can easier on the eyes at night, but the light theme is better for reading in daylight/sunlight. Manually switching works, but can be a slight hassle.
Time-based is sufficient, though integrating with the system-wide choice on devices that support it makes for a smoother experience by having everything follow a single setting.
### Additional
This is [now available in Android 10](https://developer.android.com/guide/topics/ui/look-and-feel/darktheme ), hurrah!
The LineageOS' Styles API also has the option for setting an accent color without needing the Lineage SDK. Might be neat to integrate this somehow.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/142Delete selected messages from log2022-01-10T05:15:04ZHannah von RethDelete selected messages from logWith the recent spam wave it would be interesting to be able to delete selected messages from the log.With the recent spam wave it would be interesting to be able to delete selected messages from the log.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/146Separate notification channels for "Highlights" and "Private Messages"2022-01-10T05:15:04ZShane SynanSeparate notification channels for "Highlights" and "Private Messages"Similar to the desktop Quassel client (at least with KNotification support), it'd be nice to configure `Highlights` and `Private Messages` separately. One use case is setting different sounds for each.
Given the matter of `Old Highligh...Similar to the desktop Quassel client (at least with KNotification support), it'd be nice to configure `Highlights` and `Private Messages` separately. One use case is setting different sounds for each.
Given the matter of `Old Highlights`, this might double the notification-related notification channels from 2 to 4, having `Old Highlights` and `Old Private Messages`. I'm not sure of a good way to handle this (other than push notifications so it's not needed in the first place).
**Example screenshot of desktop Quassel's `Configure Notifications…`**
![Quassel desktop showing "Configure Notifications..." for KNotification's dialog, revealing separate Highlight and Private Message settings](https://zorro.casa/sync/Hosting/Utilities/Quassel/QuasselDroid/Development/issues/pm-notification-channels/Quassel%20desktop%20KNotifications%20settings.png )
*Aside, `NotifyMerged` is a simple C# app that monitors a directory for changes and emits notifications compatible with Canonical's `x-canonical-append` flag to enable [message merging with their NotifyOSD framework](https://wiki.ubuntu.com/NotifyOSD#merging ).*https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/155Unsaved changes dialogs should use "Discard"/"Cancel" buttons2022-01-10T05:15:00ZShane SynanUnsaved changes dialogs should use "Discard"/"Cancel" buttons## Idea
The `You have unsaved changes` dialog should use `Discard` and `Cancel` for the confirmation buttons. This [follows the Material design guidelines](https://material.io/design/communication/confirmation-acknowledgement.html#conf...## Idea
The `You have unsaved changes` dialog should use `Discard` and `Cancel` for the confirmation buttons. This [follows the Material design guidelines](https://material.io/design/communication/confirmation-acknowledgement.html#confirmation ) and makes it more clear at a glance what will happen.
It could also be simplified to `Discard changes?` or such.
> **`Discard changes?`**
>
> `You have unsaved changes that will be lost.`
>
> **`Cancel`** **|** **`Discard`**
## Additional
### Example dialogs ["Communication → Confirmation & Acknowledgement" design guidelines](https://material.io/design/communication/confirmation-acknowledgement.html#confirmation )
![Screenshot of an Android confirmation dialog, showing "Reset filters?" with the subtext of "Your filters will reset your search history and remove all saved filters from your device.", and two buttons, "Cancel" and "Reset".](https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F15xpoCSgcskWZg69oK6PVIOPwXpoRAV9I%2Fcommunication-confirmation2.png )
### Example dialogs [from the Alert Dialog design guidelines](https://material.io/design/components/dialogs.html#alert-dialog )
**Do**
![Screenshot of an alert dialog showing "Discard draft?" with "Cancel" and "Discard" buttons.](https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1g8052ZKUjp4a9STlAHL9FJ7MtLTOHJnK%2Fdialogs-alertdialog-do-1.png )
**Don't**
![Screenshot of an alert dialog showing "Discard draft?" with "No" and "Yes" buttons.](https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F1Q6QdoQcU7IJK9jjH0TSqWf8PZNtE8Lbu%2Fdialogs-alertdialog-dont-1.png )https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/159Empty/invalid values should be rejected in several fields2022-01-10T05:15:00ZShane SynanEmpty/invalid values should be rejected in several fields# Test case
## Steps
1. Connect to core
2. Go to overflow menu → `Core Settings`
### `Network` (servers)
1. Add a new network
2. Set `Network Name`
3. Don't add any servers
4. Press `Save`
*This one may be more difficult to imp...# Test case
## Steps
1. Connect to core
2. Go to overflow menu → `Core Settings`
### `Network` (servers)
1. Add a new network
2. Set `Network Name`
3. Don't add any servers
4. Press `Save`
*This one may be more difficult to implement and can be set aside to a new issue if desired.*
Quassel desktop actually even catches this if you delete all servers from a network after adding it:
> ### Invalid Network Settings
> **The following problems need to be corrected before your changes can be applied:**
>
> * All networks need at least one server defined
### `Network` (name)
1. Add a new network
2. Don't set `Network Name`
3. Add a dummy server
4. Press `Save`
### Network → `Server`
1. Add a new server to an existing network
2. Don't fill in `Host`
3. Press `Save`
### `Identity`
1. Add a new identity
2. Don't fill in `Identity name`
3. Press `Save`
### `Chatlists`
1. Add a new chat list
2. Don't fill in `Name`
3. Press `Save`
*Technically, this one is accepted by the Quassel core, but the desktop GUI requires specifying a name.*
### Ignore List → `Ignore Rule` (ignore rule)
1. Add a new ignore rule
2. Don't fill in `Ignore Rule`
3. Press `Save`
*Technically, this one is accepted by the Quassel core, but the desktop GUI requires specifying an ignore rule.*
### Ignore List → `Ignore Rule` (scope)
**This one needs fixed in upstream Quassel, too. It can be ignored for now, or fixed.**
1. Add a new ignore rule
2. Fill in `Ignore Rule`
2. Set Scope to `Network Scope`
2. Don't fill in `Scope Rule`
3. Press `Save`
*Technically, this one is accepted by the Quassel core, and the desktop GUI does not require specifying an ignore rule scope, but it probably should.*
### `Aliases` → `Alias` (name)
1. Add a new alias
2. Don't fill in `Name`
3. Press `Save`
Bonus: this logs a crash report in Quasseldroid due to a non-null value set to null. See [the crash issue for the specifics](https://git.kuschku.de/justJanne/QuasselDroid-ng/issues/161 ).
### `Aliases` → `Alias` (expansion)
1. Add a new alias
2. Don't fill in `Expansion`
3. Press `Save`
Bonus: this logs a crash report in Quasseldroid due to a non-null value set to null. See [the crash issue for the specifics](https://git.kuschku.de/justJanne/QuasselDroid-ng/issues/161 ).
## Expected
Quasseldroid rejects the empty fields in the above cases.
## Actual
Quasseldroid accepts the empty fields in the above cases, highlighting with red/whatever method Android uses to indicate a field is required.
# Additional
The Android approaches appears to be using `setHint` and [`setError`](https://developer.android.com/reference/android/widget/TextView#setError(java.lang.CharSequence) ).https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/163Simplify/clarify avatar settings2022-01-10T05:15:04ZShane SynanSimplify/clarify avatar settings## Idea
The `Show Avatars` handling isn't very clear on what actually happens and can leave someone confused about what affects what.
Avatar handling should probably be moved into it's own section, perhaps under an `Appearance` pane [a...## Idea
The `Show Avatars` handling isn't very clear on what actually happens and can leave someone confused about what affects what.
Avatar handling should probably be moved into it's own section, perhaps under an `Appearance` pane [as part of reorganizing the client settings](https://git.kuschku.de/justJanne/QuasselDroid-ng/issues/114 ).
`Show Avatars` controls `Show Avatars in Messages` *and* IRCv3 avatar fetching functionality. Avatars elsewhere are always shown, but could use settings to manage that.
Perhaps a `Avatar fetching` section and a `Display` section for where they're actually shown, with the notion that if all display options are disabled (if possible), nothing's fetched, either.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/168Chat View switching is not working2022-01-10T05:15:00ZZauberfischChat View switching is not workingThis seems like a new bug in the recent beta
Right after reconnecting it works fine.
After some time/minimizing the app it just stops working.This seems like a new bug in the recent beta
Right after reconnecting it works fine.
After some time/minimizing the app it just stops working.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/169Warn on multi line paste2018-12-26T01:18:31ZmavhcWarn on multi line pasteIf a user accidentally copies text that contains multiple lines, and pastes them into QuasselDroid, it should warn the user, to avoid spamming others. Maybe offer to remove the newline characters.
More than 3 lines is probably enough to...If a user accidentally copies text that contains multiple lines, and pastes them into QuasselDroid, it should warn the user, to avoid spamming others. Maybe offer to remove the newline characters.
More than 3 lines is probably enough to trigger the warning.
Warning text could be something like: Warning, you are about to send (x) lines of text, continue? OK/Cancelhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/175Warn in Core Settings and (phone-only) sidebar when connection lost/reconnecting2022-01-10T05:15:04ZShane SynanWarn in Core Settings and (phone-only) sidebar when connection lost/reconnecting## Test case
### Steps
1. Connect to a Quassel core
2. Open the buffer list
3. Disable Internet connection (e.g. `WiFi`/`Airplane mode` toggle)
4. Observe the buffer list
5. Re-enable Internet connection
6. Open `…` menu, `Core Se...## Test case
### Steps
1. Connect to a Quassel core
2. Open the buffer list
3. Disable Internet connection (e.g. `WiFi`/`Airplane mode` toggle)
4. Observe the buffer list
5. Re-enable Internet connection
6. Open `…` menu, `Core Settings`
7. Disable Internet connection
### Expected
On phone layouts (sidebar hides chat view), there's a notice of being disconnected/reconnection status, hinting as to why the list is empty.
On tablet layouts (sidebar doesn't obscure chat view), as the chat view's always visible, no redundant information is put into the buffer list sidebar.
For both, when in `Core Settings`, a warning is shown about being disconnected/reconnection status, hinting as to why nothing's loaded.
### Actual
Nothing is shown.
## Additional
If displaying reconnection status incurs performance drops, it could be limited to just a disconnected warning.
*Edited from original issue now that feature warning is addressed.*https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/176Past notifications persist on disconnect then connect to different core2022-01-10T05:15:03ZShane SynanPast notifications persist on disconnect then connect to different core## Test case
### Steps
1. Connect to a Quassel core
2. Receive a notification
3. Disconnect from Quassel core
4. Connect to a different Quassel core that doesn't have the same buffers
### Expected
Notifications that don't exist on ...## Test case
### Steps
1. Connect to a Quassel core
2. Receive a notification
3. Disconnect from Quassel core
4. Connect to a different Quassel core that doesn't have the same buffers
### Expected
Notifications that don't exist on the second Quassel core disappear.
### Actual
Notifications remain while connected to the second Quassel core.
## Additional
Alternatively, this could be fixed by removing notifications when manually disconnecting (not timeout/etc) from a Quassel core. Currently, notifications must be swiped away to clear up the system tray.
This will likely change once the goal of push notifications that arrive regardless of being actually "connected" exists in Quassel.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/187Add UI hint to improve discovery of draggable editor input2022-01-10T05:15:03ZJanne Mareike KoschinskiAdd UI hint to improve discovery of draggable editor inputhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/193Allow opening multiple windows/sessions at the same time (for multiwindow)2019-04-16T07:38:06ZJanne Mareike KoschinskiAllow opening multiple windows/sessions at the same time (for multiwindow)https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/194Add special UI for networks of type bouncer2019-04-16T07:38:47ZJanne Mareike KoschinskiAdd special UI for networks of type bouncerhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/195Add workaround for IPv6 enabled cores that only listen on IPv42019-04-16T07:39:28ZJanne Mareike KoschinskiAdd workaround for IPv6 enabled cores that only listen on IPv4https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/196Add workaround to avoid keyboard showing every time2019-04-16T07:39:51ZJanne Mareike KoschinskiAdd workaround to avoid keyboard showing every timehttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/197Add search in nicklist2019-04-16T07:40:29ZJanne Mareike KoschinskiAdd search in nicklisthttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/198Add per-channel notification options2019-04-16T07:41:54ZJanne Mareike KoschinskiAdd per-channel notification options- mute channel
- always notify on message in this channel- mute channel
- always notify on message in this channelhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/199Implement message attachments and link unfurling2019-04-16T07:42:31ZJanne Mareike KoschinskiImplement message attachments and link unfurlinghttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/203Resizing the width of Chatlist/Userlist2022-01-10T05:15:03ZFireAntyResizing the width of Chatlist/UserlistWould be very nice to make the lists resizable, according to functionality in desktop client.
Also the option to make it always visible as an users choice...if i could resize it to the half i would like to see it all the time for instanc...Would be very nice to make the lists resizable, according to functionality in desktop client.
Also the option to make it always visible as an users choice...if i could resize it to the half i would like to see it all the time for instance, not only in horizontal view.
I'm on LOS 16 (Android 9) on a Lenovo Yoga Tab 3 Plushttps://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/206Allow disabling background execution2019-06-07T20:25:57ZJanne Mareike KoschinskiAllow disabling background executionJanne Mareike KoschinskiJanne Mareike Koschinskihttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/211Allow disabling/enabling multiple reconnection triggers2019-06-17T18:42:51ZJanne Mareike KoschinskiAllow disabling/enabling multiple reconnection triggersJanne Mareike KoschinskiJanne Mareike Koschinskihttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/212Expand Matrix long messages2019-07-30T21:19:58ZvinzvExpand Matrix long messagesWould it be possible to implement a switch that, if activated, let's Quassel pull in shortened and linked messages from Matrix?\
\
Example on IRC:
```
-*- MauG[m] sent a long message: < https://matrix.org/_matrix/media/v1/download/matri...Would it be possible to implement a switch that, if activated, let's Quassel pull in shortened and linked messages from Matrix?\
\
Example on IRC:
```
-*- MauG[m] sent a long message: < https://matrix.org/_matrix/media/v1/download/matrix.org/jquAHPPVNNNVwCErkIuFQGVo >
```
The same on Matrix:
```
actually no...
check the configure.ac file. Looks like some flags in %configure are needed:
--enable-gtk3
--enable-dbus```https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/213Breadcrumbs feature for quick navigation between chats2020-03-27T04:13:19Zη (eta)Breadcrumbs feature for quick navigation between chatsFrom IRC conversation:
```
[17:13:26] <eeeeeta> justJanne: oh yeah, (e) as a low-priority feature request, add a 'breadcrumbs' feature similar to what riot has, so I can easily switch between recently used chats
[17:13:34] <eeeeeta> ins...From IRC conversation:
```
[17:13:26] <eeeeeta> justJanne: oh yeah, (e) as a low-priority feature request, add a 'breadcrumbs' feature similar to what riot has, so I can easily switch between recently used chats
[17:13:34] <eeeeeta> instead of scrolling through my massive list to tab between people >_<
[17:14:00] <eeeeeta> (I mean the thing at the bottom of https://medium.com/@RiotChat/riot-web-1-1-ux-3ad8d0b792e4)
...
<justJanne> eeeeeta: one idea was having a swipe on the header bar
<justJanne> left/right to swipe between people
<eeeeeta> justJanne: ooh yeah, that would be pretty nifty :)
<justJanne> but other people wanted that to do hot chats
<eeeeeta> justJanne: make it configurable?
<justJanne> not so great UX then
<eeeeeta> left/right swipes between {items in current chat list, hot chats, recently used chats}
```
Basically, it'd be nice to have a way to quickly jump between chats, without having to use the sidebar at all. In particular, one easy way to accomplish this would be to add a dropdown menu to the header bar, showing recently switched to chats, where selecting an item would switch back, but there would be multiple ways of doing it.
## Possible UI ways of doing this
- Dropdown menu, as mentioned above
- This could simply add like 3 items to the top of the hamburger menu with "switch to *chat X*", as a quick & dirty first cut.
- Alternatively, it could be an additional item on the header bar.
- Swiping on the header bar left/right to jump between chats
- Swiping on the main view left/right
There wouldn't be any need to support more than one of these methods, IMHO.
Ideally, the list of chats that this feature would navigate between should be configurable to one of the following:
## Possible chat lists the user may want to use
- Recently used chats
- 'Hot chats' (i.e. chats with highlights / unread messages)
- Frequently used chats (may require more work)
- Items in the current chat list, or a user-specified chat list (?)https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/214Unexpected behaviours after a screen orientation change (reported by activity)2019-08-08T12:04:20Zdlicse1Unexpected behaviours after a screen orientation change (reported by activity)I developed an automatic test case generation tool and it detected these problems in your app.
I would like to know if you consider them as failures and, if not, why. Thanks for your collaboration.
1) When I change the orientation of th...I developed an automatic test case generation tool and it detected these problems in your app.
I would like to know if you consider them as failures and, if not, why. Thanks for your collaboration.
1) When I change the orientation of the device screen, the Dialog inside WhitelistActivity disappears
![2019-07-16 20-40-03_before](https://user-images.githubusercontent.com/53469180/62207879-8be43a80-b395-11e9-8cba-f3b2f3d5cdd4.png)
![2019-07-16 20-40-03_after](https://user-images.githubusercontent.com/53469180/62207880-8c7cd100-b395-11e9-8dbc-0b5f2f17dcf5.png)
2) When I change the orientation of the device screen, the Dialog inside NetworkServerActivity disappears
![2019-07-17 05-38-31_before](https://user-images.githubusercontent.com/53469180/62207807-5b9c9c00-b395-11e9-81e2-a33fdb519084.png)
![2019-07-17 05-38-31_after](https://user-images.githubusercontent.com/53469180/62207808-5b9c9c00-b395-11e9-9604-85a49effd29f.png)
3) When I change the orientation of the device screen, NetworkCreateActivity changes its state. Below there are different examples: the screenshots were taken before and after the screen orientation change and they are paired (before, after), (before, after) ...
-- first case --
"SASL" ToggleButton loses its value
![2019-07-17 00-55-45_before](https://user-images.githubusercontent.com/53469180/62207620-e03aea80-b394-11e9-83cd-e8b4f9d1334b.png)
![2019-07-17 00-55-45_after](https://user-images.githubusercontent.com/53469180/62207621-e03aea80-b394-11e9-9129-894b4c08db14.png)
-- second case --
The Dialog disappears
![2019-07-16 21-31-52_before](https://user-images.githubusercontent.com/53469180/62207622-e0d38100-b394-11e9-85a2-52751e7e8cbc.png)
![2019-07-16 21-31-52_after](https://user-images.githubusercontent.com/53469180/62207623-e0d38100-b394-11e9-9f3c-36c1017389bc.png)
4) When I change the orientation of the device screen, NetworkConfigActivity changes its state. Below there are different examples: the screenshots were taken before and after the screen orientation change and they are paired (before, after), (before, after) ...
-- first case --
The Dialog disappears
![2019-07-17 03-54-51_before](https://user-images.githubusercontent.com/53469180/62207353-36f3f480-b394-11e9-98d6-7006f6979c11.png)
![2019-07-17 03-54-51_after](https://user-images.githubusercontent.com/53469180/62207354-36f3f480-b394-11e9-8eab-b8e57b537864.png)
-- second case --
"Disconnect after" EditText loses its value
![2019-07-17 03-35-26_before](https://user-images.githubusercontent.com/53469180/62207355-378c8b00-b394-11e9-8da4-6ced4795c5fa.png)
![2019-07-17 03-35-26_after](https://user-images.githubusercontent.com/53469180/62207357-378c8b00-b394-11e9-9f36-2347878ba467.png)
-- third case --
Two ToggleButtons lose their values
![2019-07-16 22-57-00_before](https://user-images.githubusercontent.com/53469180/62207358-378c8b00-b394-11e9-9e36-15d5afbb32ff.png)
![2019-07-16 22-57-00_after](https://user-images.githubusercontent.com/53469180/62207360-38252180-b394-11e9-805e-34a54db66d03.png)
5) When I change the orientation of the device screen, the "Type" options disappear in IgnoreItemActivity
![2019-07-17 03-29-58_before](https://user-images.githubusercontent.com/53469180/62207023-5d656000-b393-11e9-92cb-764523086863.png)
![2019-07-17 03-29-58_after](https://user-images.githubusercontent.com/53469180/62207024-5d656000-b393-11e9-918d-9d2787090132.png)
6) When I change the orientation of the device screen, IdentityCreateActivity changes its state. Below there are different examples: the screenshots were taken before and after the screen orientation change and they are paired (before, after), (before, after) ...
-- first case --
"Add to dictionary" option disappears
![2019-07-17 00-50-24_before](https://user-images.githubusercontent.com/53469180/62206810-e92abc80-b392-11e9-8029-ddc31bf41032.png)
![2019-07-17 00-50-24_after](https://user-images.githubusercontent.com/53469180/62206814-e9c35300-b392-11e9-9b60-5d7b2748d7aa.png)
-- second case --
The TextView disappears
![2019-07-17 00-48-01_before](https://user-images.githubusercontent.com/53469180/62206817-e9c35300-b392-11e9-9ad1-be1a46fdf150.png)
![2019-07-17 00-48-01_after](https://user-images.githubusercontent.com/53469180/62206819-e9c35300-b392-11e9-89a9-6cc449ba0ce5.png)
-- third case --
It doesn't keep the scroll position
![2019-07-16 22-54-29_before](https://user-images.githubusercontent.com/53469180/62206820-ea5be980-b392-11e9-9391-45a1989c6a73.png)
![2019-07-16 22-54-29_after](https://user-images.githubusercontent.com/53469180/62206821-ea5be980-b392-11e9-8dd8-4ff074b42f10.png)
7) When I change the orientation of the device screen, the Dialog inside HighlightRuleActivity disappears
![2019-07-17 05-25-06_before](https://user-images.githubusercontent.com/53469180/62206734-c1d3ef80-b392-11e9-9be8-6c53dfa694b0.png)
![2019-07-17 05-25-06_after](https://user-images.githubusercontent.com/53469180/62206735-c26c8600-b392-11e9-95e3-472321e04bb7.png)
8) When I change the orientation of the device screen, HighlightListActivity changes its state. Below there are different examples: the screenshots were taken before and after the screen orientation change and they are paired (before, after), (before, after) ...
-- first case --
It loses the value of the "Case Sensitive" ToggleButton
![2019-07-17 09-25-10_before](https://user-images.githubusercontent.com/53469180/62206513-45d9a780-b392-11e9-95c7-5dcac03fe347.png)
![2019-07-17 09-25-10_after](https://user-images.githubusercontent.com/53469180/62206515-45d9a780-b392-11e9-8375-2c5a6076bc8b.png)
-- second case --
The options disappear
![2019-07-17 03-58-37_before](https://user-images.githubusercontent.com/53469180/62206516-45d9a780-b392-11e9-9f46-7de4a8b317d0.png)
![2019-07-17 03-58-37_after](https://user-images.githubusercontent.com/53469180/62206517-45d9a780-b392-11e9-80b0-ed8f2308d4ae.png)
-- third case --
The "Highlight rules" disappear
![2019-07-16 23-02-56_before](https://user-images.githubusercontent.com/53469180/62206518-46723e00-b392-11e9-97b3-f34580433797.png)
![2019-07-16 23-02-56_after](https://user-images.githubusercontent.com/53469180/62206519-46723e00-b392-11e9-93ef-3df3b7fe5c19.png)
9) When I change the orientation of the device screen, CoreSettingsActivity doesn't keep the scroll position
![2019-07-17 02-11-15_before](https://user-images.githubusercontent.com/53469180/62206443-1f1b7100-b392-11e9-9401-73661aafe505.png)
![2019-07-17 02-11-15_after](https://user-images.githubusercontent.com/53469180/62206444-1f1b7100-b392-11e9-8e29-e5167c4e1c6d.png)
10) When I change the orientation of the device screen, ClientSettingsActivity loses the options opened
![2019-07-17 08-34-56_before](https://user-images.githubusercontent.com/53469180/62206387-fbf0c180-b391-11e9-9ade-3c8b73a874ac.png)
![2019-07-17 08-34-56_after](https://user-images.githubusercontent.com/53469180/62206388-fbf0c180-b391-11e9-8b01-c283db4045c9.png)
11) When I change the orientation of the device screen, ChatlistCreateActivity changes its state. Below there are different examples: the screenshots were taken before and after the screen orientation change and they are paired (before, after), (before, after) ...
-- first case --
"All Networks" option disappears
![2019-07-17 11-08-51_before](https://user-images.githubusercontent.com/53469180/62206079-4a519080-b391-11e9-924a-b9fdad249c38.png)
![2019-07-17 11-08-51_after](https://user-images.githubusercontent.com/53469180/62206080-4aea2700-b391-11e9-87f3-eada1ff2a18e.png)
-- second case --
The Dialog disappears
![2019-07-17 03-26-23_before](https://user-images.githubusercontent.com/53469180/62206082-4b82bd80-b391-11e9-9181-65c28c0ea293.png)
![2019-07-17 03-26-23_after](https://user-images.githubusercontent.com/53469180/62206083-4b82bd80-b391-11e9-9d65-7fb1f7d6a14a.png)
-- third case --
It loses the text written inside the "name" EditText
![2019-07-17 03-25-43_before](https://user-images.githubusercontent.com/53469180/62206084-4b82bd80-b391-11e9-9a6a-1623eff1855f.png)
![2019-07-17 03-25-43_after](https://user-images.githubusercontent.com/53469180/62206085-4c1b5400-b391-11e9-8924-89e8df0165cc.png)
12) When I change the orientation of the device screen, the "Paste and Select all" options disappear in ChatActivity
![2019-07-17 00-18-44_before](https://user-images.githubusercontent.com/53469180/62205953-f34bbb80-b390-11e9-8019-fcf5d4c6a51a.png)
![2019-07-17 00-18-44_after](https://user-images.githubusercontent.com/53469180/62205954-f34bbb80-b390-11e9-897f-88b90bf9f426.png)
13) When I change the orientation of the device screen, the Menu in AccountSelectionActivity disappears
![2019-07-16 20-50-05_before](https://user-images.githubusercontent.com/53469180/62205818-92bc7e80-b390-11e9-9044-6cda3f0ab415.png)
![2019-07-16 20-50-05_after](https://user-images.githubusercontent.com/53469180/62205820-92bc7e80-b390-11e9-81e0-24227f5e8675.png)
14) When I change the orientation of the device screen, AccountSetupActivity changes its state. Below there are different examples: the screenshots were taken before and after the screen orientation change and they are paired (before, after), (before, after) ...
-- first case --
"Paste, Select All" options disappear
![2019-07-16 23-54-27_before](https://user-images.githubusercontent.com/53469180/62205619-22adf880-b390-11e9-9a6e-6e51ec75b7ad.png)
![2019-07-16 23-54-27_after](https://user-images.githubusercontent.com/53469180/62205621-23468f00-b390-11e9-9baa-d69c4645c145.png)
-- second case --
The menu disappears
![2019-07-16 21-49-37_before](https://user-images.githubusercontent.com/53469180/62205622-23468f00-b390-11e9-9bc8-84db2ceb59b7.png)
![2019-07-16 21-49-37_after](https://user-images.githubusercontent.com/53469180/62205623-23468f00-b390-11e9-864a-debfda6ba3ae.png)
-- third case --
"Port" EditText loses the focus
![2019-07-16 21-46-41_before](https://user-images.githubusercontent.com/53469180/62205624-23df2580-b390-11e9-8575-59431022b236.png)
![2019-07-16 21-46-41_after](https://user-images.githubusercontent.com/53469180/62205625-23df2580-b390-11e9-8330-2ae48024495f.png)
15) When I change the orientation of the device screen, AccountEditActivity changes its state. Below there are different examples: the screenshots were taken before and after the screen orientation change and they are paired (before, after), (before, after) ...
-- first case --
It loses some of the text written in the "Password" EditText
![2019-07-17 01-46-33_before](https://user-images.githubusercontent.com/53469180/62205380-9d2a4880-b38f-11e9-8e73-30aafbf6d242.png)
![2019-07-17 01-46-33_after](https://user-images.githubusercontent.com/53469180/62205381-9d2a4880-b38f-11e9-89e7-f2bb5227130f.png)
-- second case --
The Dialog disappears
![2019-07-16 20-55-58_before](https://user-images.githubusercontent.com/53469180/62205382-9d2a4880-b38f-11e9-80b0-e71a65b516d1.png)
![2019-07-16 20-55-58_after](https://user-images.githubusercontent.com/53469180/62205383-9d2a4880-b38f-11e9-99b7-180c6483d362.png)
16) When I change the orientation of the device screen, AboutActivity doesn't keep the scroll position
![2019-07-16 20-28-01_before](https://user-images.githubusercontent.com/53469180/62205279-694f2300-b38f-11e9-8291-61390eb1e9c5.png)
![2019-07-16 20-28-01_after](https://user-images.githubusercontent.com/53469180/62205280-694f2300-b38f-11e9-8650-fb8cc9620677.png)https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/216Notifications persist even after swiping them away2020-08-14T05:07:51ZToni SpetsNotifications persist even after swiping them awayI have a setup where I'm using irssi that exposes the networks I'm on as a proxy where I have Quassel connected to and Quasseldroid is my only client that I use to connect to that. I know this is an unusual setup. However, this may uncov...I have a setup where I'm using irssi that exposes the networks I'm on as a proxy where I have Quassel connected to and Quasseldroid is my only client that I use to connect to that. I know this is an unusual setup. However, this may uncover some bugs in Quasseldroid that other people don't see because they may use other Quassel clients as well.
What I'm encountering a lot is that when I connect I get a notification flood which is understandable as those hilights or PMs have not been addressed in any other Quassel client - it's fine.
The issue is those notifications can sometimes persist even if I try to swipe them off or reconnect. I do want them because they may also contain some unanswered things but they are really annoying when they keep coming back on reconnect and don't seem to go away.
Ideally I'd get those notifications only once and they wouldn't persist between reconnects but they also would not mark a buffer read when swiped off - they are just notifications. Is this combination currently possible and is it technically possible with Quassel and Quasseldroid?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/218Set Navigation Bar color based on theme?2022-01-10T05:21:41ZChris KrauseSet Navigation Bar color based on theme?Would it be possible to change the color of the Navigation Bar based on the current theme? I noticed that a few other apps I have do that, including QuickEdit+ which was just updated with this functionality (which is what made me think o...Would it be possible to change the color of the Navigation Bar based on the current theme? I noticed that a few other apps I have do that, including QuickEdit+ which was just updated with this functionality (which is what made me think of requesting this right now). Its most apparent on Samsung devices which by default have the Navigation bar color a light gray regardless of your dark system theme. The only way to change it is to have in app support for setting its color.Future Feature Releasehttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/219Listen to intents to restart service on app upgrade/phone reboot2022-01-10T05:20:27ZShane SynanListen to intents to restart service on app upgrade/phone reboot## In brief
* **If previously connected to core**, Quasseldroid should restart the service on app upgrades and device reboot
* * [Android 8.0+ send a broadcast `MY_PACKAGE_REPLACED`, while earlier versions send `PACKAGE_REPLACED`](htt...## In brief
* **If previously connected to core**, Quasseldroid should restart the service on app upgrades and device reboot
* * [Android 8.0+ send a broadcast `MY_PACKAGE_REPLACED`, while earlier versions send `PACKAGE_REPLACED`](https://developer.android.com/about/versions/oreo/background.html#broadcasts); both versions send `ON_BOOT_COMPLETED`
* This would be similar [to KDE Connect's handling](https://github.com/KDE/kdeconnect-android/commit/386c3cec21d64129c6dcb71fe05cb4cd0cbc2bca)Future Feature Releasehttps://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/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/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/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/230Stop marking buffer as read when full-screen message compose interface is open2022-01-10T05:19:32ZShane SynanStop marking buffer as read when full-screen message compose interface is open## In brief
* Don't mark buffers as read while the message compose interface is expanded
* Makes it possible to notice new messages, including those which would change one's reply
* Might be desirable enough to not need to become ano...## In brief
* Don't mark buffers as read while the message compose interface is expanded
* Makes it possible to notice new messages, including those which would change one's reply
* Might be desirable enough to not need to become another setting
* Tablet UI may be different (not tested)
## Example
1. Open a private message with a user you can send messages from, or visit a channel you have another account in
* Applies to both use-cases
2. Swipe up the message compose box to cover the list of chat messages
3. Imagine you're spending a long time composing a message
4. From the other user send a private message or channel highlight to this user
5. Observe how Quasseldroid handles the new message/highlight
6. Swipe down the message compose box to reveal the list of chat messages
7. Imagine you've received a message that would have changed your reply significantly
### Before
Quasseldroid marks the incoming messages as read, despite not showing the message or any notification. Time might be wasted.
### After
Quasseldroid won't mark messages as read, and won't move the marker line while the compose box is expanded. Once the compose box is no longer expanded, Quasseldroid resumes marking the active buffer as read.
### Hypothetical conversation
```
[1:23 pm] <someNick> digitalcircuit: What was your reasoning behind this change?
```
*starts writing a lengthy reply in the expanded message compose interface*
```
[1:25 pm] <someNick> digitalcircuit: Nevermind, I found your past message
```Future Feature Releasehttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/231Make swipe left and right work from any point of the view2022-01-10T05:14:20ZToni SpetsMake swipe left and right work from any point of the viewI've noticed that it's *really* hard to get the user list or the server/channel list open with swipes because it requires you to start the swipe from the very edge of the screen.
Slack and Discord both allow you to start swiping from an...I've noticed that it's *really* hard to get the user list or the server/channel list open with swipes because it requires you to start the swipe from the very edge of the screen.
Slack and Discord both allow you to start swiping from any part of the screen (to left or right) and it will slide open either the channel or user list.
This is a small UX improvement that would make Quasseldroid immensely easier to use one handed.
Thanks!2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/232Add means to distinguish italic formatting in CTCP ACTION (/me) messages2022-01-10T05:19:11ZShane SynanAdd means to distinguish italic formatting in CTCP ACTION (/me) messages## In brief
* Add some way of distinguishing whether italic mIRC formatting is used in a CTCP ACTION (`/me`) message
* Perhaps italicized formatting should invert to return the default-italicized text to normal?
* Or, disable use of ...## In brief
* Add some way of distinguishing whether italic mIRC formatting is used in a CTCP ACTION (`/me`) message
* Perhaps italicized formatting should invert to return the default-italicized text to normal?
* Or, disable use of italics with a setting?
## Rationale
Some folks make use of *italics* when writing their CTCP ACTION (`/me`) messages. Quasseldroid's notifications correctly show the italic formatting, but when viewing the buffer in Quasseldroid, the italics are no longer distinguishable from the default styling of CTCP ACTION messages.
This can result in losing emphasis in tone of voice or lessening creative uses of formatting in conversational messages.
## Test cases
### Steps
1. Open Quasseldroid, connect to a network
2. As another user, send this Quasseldroid client a CTCP ACTION message with italics mixed in
* E.g. `/me shakes his head with a frown. "It's almost like Google *wants* to keep Android developers on their toes."`
3. Observe the Android notification Quasseldroid generates
4. Observe how Quasseldroid shows the message in the buffer view
5. Optionally, observe the message in the Quassel desktop client
### Before
In steps 3 and 5, the emphasis can be seen on the word `wants`. In step 4, however, Quasseldroid does not distinguish between the italic mIRC formatted word `wants` and the rest of the auto-italicized CTCP ACTION message.
### After
In steps 3-5, it's always possible to tell some form of emphasis was placed on the word `wants`.
## Examples
### Quasseldroid notification
![Screenshot of Quasseldroid notification on Android properly showing italics in a CTCP ACTION message](https://zorro.casa/sync/Hosting/Utilities/Quassel/QuasselDroid/Development/issues/ctcp-action-italics/Example%20-%20Quasseldroid%20notification%20view.png#v1 )
> **qdroid_examp…** \* Quasseldroid \* now
>
> shakes his head with a frown. "It's almost like Google *wants* to keep Android developers on their toes."
>
> `Hahaha` [auto-generated reply suggestion]
>
> `Mark Read` [button] | `Reply` [button]
### Quasseldroid buffer view
![Screenshot of Quasseldroid buffer view showing the entire CTCP ACTION message as italics](https://zorro.casa/sync/Hosting/Utilities/Quassel/QuasselDroid/Development/issues/ctcp-action-italics/Example%20-%20Quasseldroid%20buffer%20view.png#v1 )
> **Dec 19, 2020**
>
> — *qdroid_example shakes his head with a frown. "It's almost like Google *wants* to keep Android developers on their toes." 04:50 PM*
### Quassel desktop
![Screenshot of Quassel desktop buffer view properly showing the italics within the CTCP ACTION message](https://zorro.casa/sync/Hosting/Utilities/Quassel/QuasselDroid/Development/issues/ctcp-action-italics/Example%20-%20Quassel%20desktop.png#v1 )
> [4:50:14 pm] -\*- qdroid_example shakes his head with a frown. "It's almost like Google *wants* to keep Android developers on their toes."Future Feature Releasehttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/233Use Tabular Numbers instead of Monospace for the time2022-01-10T05:18:15ZJanne Mareike KoschinskiUse Tabular Numbers instead of Monospace for the time```xml
<item name="android:fontFeatureSettings">tnum</item>
``````xml
<item name="android:fontFeatureSettings">tnum</item>
```1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/234Adapt font size and spacing in channel list2022-01-10T05:18:09ZJanne Mareike KoschinskiAdapt font size and spacing in channel listWe should use the new, larger presets provided by Android (16sp main, 14sp description), and additionally allow a condensed mode disabling the second line, shrinking the icons to 24dp, and reducing overall item height to 48dp (the smalle...We should use the new, larger presets provided by Android (16sp main, 14sp description), and additionally allow a condensed mode disabling the second line, shrinking the icons to 24dp, and reducing overall item height to 48dp (the smallest we can use without getting flagged by Android’s "touch target too small" warning)2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/235Provide a way to show server messages without using italics2021-01-08T17:44:54ZJanne Mareike KoschinskiProvide a way to show server messages without using italicsAlternative options include reducing the contrast, as used in old quasseldroidAlternative options include reducing the contrast, as used in old quasseldroidhttps://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/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/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/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/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/241Confirmation Dialog for joining channels2021-08-09T16:45:11ZJanne Mareike KoschinskiConfirmation Dialog for joining channelshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/242Indicate Here/Away presence when viewing query/PM2022-01-10T05:16:58ZShane SynanIndicate Here/Away presence when viewing query/PM### Discussion
Quasseldroid should show some sort of "Here/Away" presence indication when viewing a query/private message. This would make it easier to tell if the person you're talking to has gone away in the middle of writing a long ...### Discussion
Quasseldroid should show some sort of "Here/Away" presence indication when viewing a query/private message. This would make it easier to tell if the person you're talking to has gone away in the middle of writing a long message, etc.
### Ideas
* A green circle/yellow triangle/gray X/whatever somewhere near the buffer name
* Mimics Quassel desktop
* Should follow Material design/icons
* Italicize the buffer name for users that are away
* Might be easier and more obvious, but might not look nice - not sure
* Something else..?1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/243Display inline image preview2022-01-10T05:16:51ZTrigextrigex@protonmail.comDisplay inline image previewAn inline image preview, not unlike that of another irc client like The Lounge, or like Discord's inline image previews, would be fantastic! In the IRC channel I frequent, it is very image heavy and it really is a big pain to have to man...An inline image preview, not unlike that of another irc client like The Lounge, or like Discord's inline image previews, would be fantastic! In the IRC channel I frequent, it is very image heavy and it really is a big pain to have to manually click each link, especially with multiple images in a row.
This feature would pull images from posted links in chat.
Is there any technical reason for why this hasn't been implemented yet, or has there just been no demand to?2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/244Can't resolve '.local' domains (mDNS)2022-01-10T05:13:22ZeNV25Can't resolve '.local' domains (mDNS)Can't connect to quassel core using '.local' mDNS domain.
I have quassel core running in a raspberry pi and I used 'hostname.local' to connect to it.
Everything works using quassel client on Linux, so this is probably because android d...Can't connect to quassel core using '.local' mDNS domain.
I have quassel core running in a raspberry pi and I used 'hostname.local' to connect to it.
Everything works using quassel client on Linux, so this is probably because android doesn't resolve using mDNS.https://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/246Monospace font not working2022-07-27T01:57:00ZKaziMonospace font not workingMonospace font doesn't seem to work. Makes no difference in the font enabled vs disabled. Running OnePlus 7T Pro android 11Monospace font doesn't seem to work. Makes no difference in the font enabled vs disabled. Running OnePlus 7T Pro android 11https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/247Sever connection does not initialize over Wi-Fi2022-10-29T12:21:54ZEloySever connection does not initialize over Wi-FiThis has been tested using QuasselDroid 1.6.2 on a Samsung Galaxy Fold 3 5G with Android 12 and using QuasselDroid 1.6.2 on a OnePlus 5 with Android 7.
When using a Wi-Fi connection on startup, it hangs in the init phase. When switching...This has been tested using QuasselDroid 1.6.2 on a Samsung Galaxy Fold 3 5G with Android 12 and using QuasselDroid 1.6.2 on a OnePlus 5 with Android 7.
When using a Wi-Fi connection on startup, it hangs in the init phase. When switching to cellular, it does work. After switching back to Wi-Fi after it has been initialized, it works fine as well.https://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/249Avatar not being displayed if "<email@domain.tld> ..-. ..- -.-. -.- / -.-- --...2023-11-18T23:56:02ZPeGaSuSAvatar not being displayed if "<email@domain.tld> ..-. ..- -.-. -.- / -.-- --- ..-" is used as realnameI'm using Quassel to connect to weechat.
When setting my realname on the format `"<email@domain.tld> ..-. ..- -.-. -.- / -.-- --- ..-"` my avatar, even if set, isn't shown to myself on Quasseldroid but other clients, such as IRCCloud, a...I'm using Quassel to connect to weechat.
When setting my realname on the format `"<email@domain.tld> ..-. ..- -.-. -.- / -.-- --- ..-"` my avatar, even if set, isn't shown to myself on Quasseldroid but other clients, such as IRCCloud, are able to see it.
If I set the ralname to be `"..-. ..- -.-. -.- / -.-- --- ..- <email@domain.tld>"` then I can see my on avatar on Quasseldroid and other clients, such as IRCCloud, are able to see it too.
I don't know if the issue is the dots and dashes present in the realname that causes Quasseldroid to parse it incorrectly.