I installed the Android N beta and quasseldroid is not compatible with the new version due to a certificate store error when attempting to connect. It can't seem to retrieve the cached certificate or store the new certificate from the server on connect attempt so it never successfully connects to a server. The error is below:

The core SSL-Certificate has changed, do you trust the new one? java.lang.RuntimeException: Failed to load certificates from KeyStore

I would really like to see an option which enables an automatic reconnect after the connection is lost. After every network change (wifi to mobile or vice versa) or after a period of poor/no mobile connection quasseldroid's connection to the core is lost and you have to manually open the application and hit "connect" to reconnect.

Issue:

Based on the version currently available on Google Play (https://play.google.com/store/apps/details?id=com.iskrembilen.quasseldroid), upon disconnect, Quassel remains in the notification bar as disconnected.

This is useful if the user wants to continue using and has experienced an unintended disconnect, but not useful if somebody has invoked the disconnect themselves. When navigating away from the Quassel intent(s), the notification of being disconnected remains in the notification bar; it's a little irritating and also makes me concerned about whether a wake-lock is still locked.

To get round the problem, I currently have to force stop the Quassel app.

Desired result:

No disconnection notification altogether, OR

A disconnection notification when a disconnection has been experienced outside of user invocation. Such a notification should be able to be cleared and not remain resident along with the process.

A menu option to exit the Quassel app would also be nice.

This is probably the largest Pull Request here yet, I should have split it up into multiple seperate ones, but it was easier to do this way.

Screenhots APKs

Here’s a summary of the changes this Pull Request does:

UI:

• Replaced ActionBarSherlock with the new AppCompat implementation
• Added DetailFragment as a right navigation drawer for QueryBuffers
• Changed the whole UI to use Material Design.
• Updated Notifications
• Replaced most icons with new ones from @oppoyu and Android Lollipop default icons
• Rewrote sender color system
• Added Tablet UI

Misc:

• Made a lot of stuff more modular, allowing for easier modification
• Moved ALL strings out of the code into the strings.xml, also sorted that file properly to make translations easier
• Added support for automated Travis building and testing

Bugfixes:

• Fixed Notifications: #180 and #26, ~~hopefully~~ confirmed #195
• Fixed Multiline-input: #181
• Fixed NickCompletion: #57
• Fixed #42 (partially) by saving the last state in the app, this stores the state beyond reconnect, but the state is lost at reboot of the phone
• Fixed UI bugs #76, #40, #99
• Fixed a lot of reconnect bugs, including #105, #114 and #146, but also multiple ones that weren’t even tracked yet
• Fixed a bug where, upon joining a new channel, the client would show a random other channel instead.

I love this app. IRC was never easier to use, thanks!

I only wish, it would make better use of all the space on my 10" tablet. Especially in landscape mode, the channel and nickname lists could be integrated with the chat on one screen, making it even more usable! ;)

Are there any plans to make a HD version for tablets, or to use a different layout for large screens?

I have a core running craploads of IRC buffers. Looks like QuasselDroid (emulator) fails to get all the init data from the core, even after hard trying:

03-14 23:38:38.910: INFO/CoreConnection(411): Package reviced, reseting countdown
03-14 23:38:38.910: ERROR/CoreConnService(411): Getting message buffer already have
03-14 23:38:38.920: WARN/System.err(411): Slow parsing (2ms)!: Request type: Sync Class name:BacklogManager
03-14 23:38:38.950: INFO/System.out(411): Slow core is slow: 31ms
03-14 23:38:38.950: INFO/CoreConnection(411): Package reviced, reseting countdown
03-14 23:38:38.960: ERROR/CoreConnService(411): Getting message buffer already have
03-14 23:38:38.970: WARN/System.err(411): Slow parsing (10ms)!: Request type: Sync Class name:BacklogManager
03-14 23:38:39.010: INFO/System.out(411): Slow core is slow: 28ms
03-14 23:38:39.010: INFO/CoreConnection(411): Package reviced, reseting countdown
03-14 23:38:39.020: ERROR/CoreConnService(411): Getting message buffer already have
03-14 23:38:39.020: WARN/System.err(411): Slow parsing (6ms)!: Request type: Sync Class name:BacklogManager
03-14 23:38:39.060: INFO/System.out(411): Slow core is slow: 36ms
03-14 23:38:39.060: INFO/CoreConnection(411): Package reviced, reseting countdown
03-14 23:38:39.060: ERROR/CoreConnService(411): Getting message buffer already have
03-14 23:38:39.070: WARN/System.err(411): Slow parsing (5ms)!: Request type: Sync Class name:BacklogManager
03-14 23:38:39.100: INFO/System.out(411): Slow core is slow: 32ms
03-14 23:38:39.110: INFO/CoreConnection(411): Package reviced, reseting countdown
03-14 23:38:39.120: ERROR/CoreConnService(411): Getting message buffer already have
03-14 23:38:39.120: WARN/System.err(411): Slow parsing (5ms)!: Request type: Sync Class name:BacklogManager
03-14 23:38:39.160: INFO/System.out(411): Slow core is slow: 35ms
03-14 23:38:39.160: INFO/CoreConnection(411): Package reviced, reseting countdown
03-14 23:38:39.170: ERROR/CoreConnService(411): Getting message buffer already have
03-14 23:38:39.170: WARN/System.err(411): Slow parsing (5ms)!: Request type: Sync Class name:BacklogManager
03-14 23:38:40.140: DEBUG/dalvikvm(411): GC freed 9135 objects / 477720 bytes in 74ms
03-14 23:38:41.880: DEBUG/dalvikvm(411): GC freed 7266 objects / 398368 bytes in 113ms
03-14 23:38:43.880: DEBUG/dalvikvm(411): GC freed 7238 objects / 397864 bytes in 137ms
03-14 23:38:45.640: DEBUG/dalvikvm(411): GC freed 7226 objects / 397704 bytes in 84ms
03-14 23:38:47.170: DEBUG/dalvikvm(411): GC freed 7243 objects / 397904 bytes in 82ms
03-14 23:38:48.790: DEBUG/dalvikvm(411): GC freed 7257 objects / 398144 bytes in 84ms
03-14 23:38:50.450: DEBUG/dalvikvm(411): GC freed 7253 objects / 398368 bytes in 87ms
03-14 23:38:52.101: DEBUG/dalvikvm(411): GC freed 7729 objects / 424576 bytes in 93ms
03-14 23:38:54.610: DEBUG/dalvikvm(411): GC freed 8371 objects / 458512 bytes in 138ms
03-14 23:38:56.750: DEBUG/dalvikvm(411): GC freed 9028 objects / 494912 bytes in 104ms
03-14 23:38:59.160: DEBUG/dalvikvm(411): GC freed 9825 objects / 537120 bytes in 116ms
03-14 23:39:01.440: DEBUG/dalvikvm(411): GC freed 10463 objects / 576432 bytes in 151ms
03-14 23:39:03.760: DEBUG/dalvikvm(411): GC freed 11389 objects / 624912 bytes in 126ms
03-14 23:39:06.630: DEBUG/dalvikvm(411): GC freed 12270 objects / 675016 bytes in 123ms
03-14 23:39:09.170: INFO/CoreConnection(411): Timer finished, disconnection from core
03-14 23:39:09.190: WARN/System.err(411): IO error!
03-14 23:39:09.190: WARN/System.err(411): java.net.SocketException: Bad socket
03-14 23:39:09.200: WARN/System.err(411):     at org.apache.harmony.luni.platform.OSNetworkSystem.receiveStreamImpl(Native Method)
03-14 23:39:09.250: WARN/System.err(411):     at org.apache.harmony.luni.platform.OSNetworkSystem.receiveStream(OSNetworkSystem.java:478)
03-14 23:39:09.250: WARN/System.err(411):     at org.apache.harmony.luni.net.PlainSocketImpl.read(PlainSocketImpl.java:565)
03-14 23:39:09.250: WARN/System.err(411):     at org.apache.harmony.luni.net.SocketInputStream.read(SocketInputStream.java:87)
03-14 23:39:09.250: WARN/System.err(411):     at java.io.DataInputStream.readToBuff(DataInputStream.java:157)
03-14 23:39:09.250: WARN/System.err(411):     at java.io.DataInputStream.readInt(DataInputStream.java:285)
03-14 23:39:09.250: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QInteger.unserialize(QInteger.java:24)
03-14 23:39:09.260: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QInteger.unserialize(QInteger.java:1)
03-14 23:39:09.270: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:180)
03-14 23:39:09.270: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:1)
03-14 23:39:09.282: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QMap.unserialize(QMap.java:48)
03-14 23:39:09.320: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QMap.unserialize(QMap.java:1)
03-14 23:39:09.330: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:180)
03-14 23:39:09.330: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:1)
03-14 23:39:09.330: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QMap.unserialize(QMap.java:48)
03-14 23:39:09.330: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QMap.unserialize(QMap.java:1)
03-14 23:39:09.330: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:180)
03-14 23:39:09.340: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:1)
03-14 23:39:09.351: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QMap.unserialize(QMap.java:48)
03-14 23:39:09.351: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QMap.unserialize(QMap.java:1)
03-14 23:39:09.360: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:180)
03-14 23:39:09.390: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:1)
03-14 23:39:09.410: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QMap.unserialize(QMap.java:48)
03-14 23:39:09.410: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QMap.unserialize(QMap.java:1)
03-14 23:39:09.420: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:180)
03-14 23:39:09.430: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:1)
03-14 23:39:09.440: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QList.unserialize(QList.java:36)
03-14 23:39:09.440: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.serializers.QList.unserialize(QList.java:1)
03-14 23:39:09.440: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:180)
03-14 23:39:09.460: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QVariant$QVariantSerializer.unserialize(QVariant.java:1)
03-14 23:39:09.470: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QMetaTypeRegistry.unserialize(QMetaTypeRegistry.java:172)
03-14 23:39:09.470: WARN/System.err(411):     at com.lekebilen.quasseldroid.qtcomm.QMetaTypeRegistry.unserialize(QMetaTypeRegistry.java:175)
03-14 23:39:09.480: WARN/System.err(411):     at com.lekebilen.quasseldroid.CoreConnection.readQVariantList(CoreConnection.java:805)
03-14 23:39:09.500: WARN/System.err(411):     at com.lekebilen.quasseldroid.CoreConnection.access$2(CoreConnection.java:803)
03-14 23:39:09.500: WARN/System.err(411):     at com.lekebilen.quasseldroid.CoreConnection$ReadThread.run(CoreConnection.java:463)

I assume it tries to load backbuffers and finally gives up after timeoutting?

Software versions: Quasselcore Version: v0.12.4, Protocol 10, Debian stretch. Quasseldroid 0.11.7 Build #174 Android 7.0, HTC One M9

Description: I get an invalid username/password combination on android, and the following were on the sever's core.log

2017-10-16 16:43:16 Info: Client connected from 2017-10-16 16:43:16 Warning: Reached end of zlib stream!
2017-10-16 16:43:16 Warning: "Socket error 1: The TLS/SSL connection has been closed"
2017-10-16 16:43:16 Warning: "Socket error 1: The remote host closed the connection"
2017-10-16 16:43:16 Info: Non-authed client disconnected:

It would be great to have support for Pebble. I made an quick hack: https://github.com/kipe/QuasselDroid/commit/7046344154b831bed8a34700f9a3ffdc768031a6, which proves that the support shouldn't be that hard to implement. I'm very unexperienced with Android coding at the moment, so I have no means to take this much further, at least not at the moment.

At the moment the features and/or issues include:

• Send highlights as notifications to Pebble (not sure if done correctly / in the correct location)
• ~~The Pebble support should have an item in settings, however I didn't figure out how to do it correctly.~~
• Notification is sent on each message (even if the buffer is open and visible, configurable in settings?)

So, any help and suggestions are more than appreciated, I'm more than willing to work on this to get Quassel to my wrist :smile:

//E: Well, adding the settings -item wasn't that hard: https://github.com/kipe/QuasselDroid/commit/b6400756d0758eb8fc3a6e348cd56d78c91498e4

A google search turns up 8494417fc806e0db70ce4d0e49366319aceee2e1 , which implies that QuasselDroid supports history in the input widget with "up" and "down" keys. On a computer, that would be they arrow keys of the keyboard. However my mobile device (Nexus 5 with the default/built-in software keyboard) has nothing equivalent to arrow keys, as far as I can tell. Can the history feature still be accessed somehow?

I'm running a Galaxy Nexus (stock GooPlay version) and, after upgrading to 4.3 from the OTA install, Quasseldroid crashes on connecting to my home QuasselCore. I've tried wiping settings from my phone and reinstalling Quasseldroid - no effect. I've submitted this via Android's crash report feature, but I wasn't sure if those got to you.

After further testing, it looks like the upgrade to 4.3 was a red herring; I still can't connect even after wiping my phone and installing the latest stable Cyanogenmod, so I'm assuming it is choking on something in my SQLlite database for Quassel.

What additional info do you need from me?

I had some issues with my quassel core so i recreated the certificate using the wiki suggested method: openssl req -x509 -nodes -days 365 -newkey rsa:1024 -keyout ~/.config/quassel-irc.org/quasselCert.pem -out ~/.config/quassel-irc.org/quasselCert.pem

After doing this i got an "Connection failed" every time i tried to connect to my core. Removing the "core-configuration" from quassel droid and adding it again didnt help. Neither did upgrading the application to the latest version.

Completely uninstalling the application and installing it again from android maket fixed the issue.

Should i supply any more information?

Parallel test execution maxParallelForks, running multiple test cases in parallel is useful and helpful when there are several CPU cores.

According to Process forking options, Gradle will run all tests in a single forked VM by default. This can be problematic if there are a lot of tests or some very memory-hungry ones. one option is to fork a new test VM after a certain number of tests have run. So our recommendation is to configure "forkEvery" and we give a specific value of 100

Disable report generation, Gradle will automatically create test reports by default which will slowing down the overall build. So it's better to disable the test reports while we don't need it

Incremental compilation, We note that the gradle version for this project is smaller than 4.10, so we recommend enabling this configuration to shorten build times

===================== If there are any inappropriate modifications in this PR, please give me a reply and I will change them.

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

2. When I change the orientation of the device screen, the Dialog inside NetworkServerActivity disappears

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

-- second case -- The Dialog disappears

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

-- second case -- "Disconnect after" EditText loses its value

-- third case -- Two ToggleButtons lose their values

5. When I change the orientation of the device screen, the "Type" options disappear in IgnoreItemActivity

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

-- second case -- The TextView disappears

-- third case -- It doesn't keep the scroll position

7. When I change the orientation of the device screen, the Dialog inside HighlightRuleActivity disappears

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

-- second case -- The options disappear

-- third case -- The "Highlight rules" disappear

9. When I change the orientation of the device screen, CoreSettingsActivity doesn't keep the scroll position

10. When I change the orientation of the device screen, ClientSettingsActivity loses the options opened

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

-- second case -- The Dialog disappears

-- third case -- It loses the text written inside the "name" EditText

12. When I change the orientation of the device screen, the "Paste and Select all" options disappear in ChatActivity

13. When I change the orientation of the device screen, the Menu in AccountSelectionActivity disappears

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

-- second case -- The menu disappears

-- third case -- "Port" EditText loses the focus

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

-- second case -- The Dialog disappears

16. When I change the orientation of the device screen, AboutActivity doesn't keep the scroll position

I have a very large quassel core with many buffers and many users in those buffers, and quasseldroid is very slow to connect (4 minutes) for me. These changes attempt to fix some of the most obvious issues, cutting down connect time by 50% or 2 minutes for me.

Some of these solutions are more patching up than real fixes (especially that Executor...) but it works.

Feel free to cherry-pick individual changes from this PR, or split it into multiple commits, I don't really care since it runs fine on my phone now :)

Thanks for porting Quassel for Android. I'm a happy user. Here you are the Spanish translation, for the case you want to offer in next releases. Thanks!

Hello. I added some strings.xml files to translate QuasselDroid to Spanish. This is an initial translation, if you find something odd let me know. Please review and merge if/when possible.

Thanks.