Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quasseldroid crashes on connection; regular Quassel connects just fine. #105

Closed
aetherspoon opened this issue Aug 7, 2013 · 6 comments
Closed

Comments

@aetherspoon
Copy link

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?

@aetherspoon
Copy link
Author

After wiping my phone and installing the latest stable Cyanogenmod (running 4.2), I'm still having the same problems, so I'm assuming the upgrade to 4.3 isn't my culprit after all.

@YtvwlD
Copy link

YtvwlD commented Dec 29, 2014

I'm having the same problems - Quasseldroid crashes after it has established a connection during "Receiving backlog...". It loads the networks just fine.

@YtvwlD
Copy link

YtvwlD commented Dec 29, 2014

I've tested it: It doesn't crash if I set the initial backlog amount to 0 lines.

@kenjiqq
Copy link
Collaborator

kenjiqq commented Jan 1, 2015

What version are you using? If you're not in the beta, try this version https://www.dropbox.com/s/fqwpqw498fv19i9/QuasselDroid-release-0.11.5.apk?dl=0 and see if the problem is still there. A lot has changed in the beta compared to the production version now.

@YtvwlD
Copy link

YtvwlD commented Jan 3, 2015

@kenborge The problem is solved in v0.11.4 which I downloaded from F-Droid today.

@kenjiqq
Copy link
Collaborator

kenjiqq commented Jan 3, 2015

Counting this as fixed then

@kenjiqq kenjiqq closed this as completed Jan 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants