Force crashes 5-10 seconds after launch

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Launch app
2.
3.

What is the expected output? What do you see instead?
No input accepted, app crashes to home screen

What version of the product are you using? On what operating system?
Quill version 10.7, Android version 4.1.1
Samsung Galaxy Note 10.1

Please provide any additional information below.
java.lang.illegalArgumentException

Source File: ComparableTimSort.java

line 831

This is the Play Store version. Nothing else on the tablet changed.

Original issue reported on code.google.com by Kyn...@gmail.com on 23 Apr 2014 at 6:49

[GoogleCodeExporter]

After a factory wipe, the app worked for a couple of days and the same behavior 
has returned.

Original comment by Kyn...@gmail.com on 6 May 2014 at 5:09

[GoogleCodeExporter]

I am seeing the same behavior, including it working after a wipe for a few 
days, then failing.  Note 10.1, Quill v10.7, Android 4.3.1 (Cyanogenmod20140323 
nightly, which is the latest available)

Original comment by k...@laberteaux.org on 2 Jul 2014 at 6:21

[GoogleCodeExporter]

I may have found the fix, at least for me.  Try a "Fix Permissions", either in 
your recovery, or there are some apps that do this.  

Original comment by k...@laberteaux.org on 7 Jul 2014 at 7:49

[GoogleCodeExporter]

I had the same thought, no luck. I also see this behavior on my Note II. 
Thankfully the 10.1 is working after a custom ROM installation. Must be an 
Exynos thing. 

Original comment by Kyn...@gmail.com on 7 Jul 2014 at 7:58

[GoogleCodeExporter]

Yea, must have been a coincidence.  It is not working now for me either.  I 
will try falling back to an earlier version, although previous attempts have 
not worked.  I think it may have something to do with the new file structure 
introduced at the beginning of V9.0 (or was it 10.0)?

10.1 works for you?

Original comment by k...@laberteaux.org on 7 Jul 2014 at 8:38

[GoogleCodeExporter]

Can you confirm which custom ROM you are using that works with Quill v10.1?  I 
am happy to change ROMs, if I can get back to a stable Quill experience.

Original comment by k...@laberteaux.org on 8 Jul 2014 at 5:29

[GoogleCodeExporter]

Hyperdrive, I think.

Original comment by Kyn...@gmail.com on 9 Jul 2014 at 5:47

[GoogleCodeExporter]

I'm having the same issue on Samsung Galaxy Note 10.1 2014. Rebooting the 
tablet fixes it for a while, and then it happens again.

Original comment by MHag...@gmail.com on 16 Mar 2015 at 8:02

[GoogleCodeExporter]

I grabbed the source and investigated the issue.

Technical synopsis:
The problem is actually caused by a runtime change in Java 7 that modified how 
java.util.Arrays.sort works internally ( see 
http://www.oracle.com/technetwork/java/javase/compatibility-417013.html#source 
and search for Arrays.sort). What triggers this particular issue on Android is 
when you have an accessibility service running, and android tries to retrieve 
the child views for HandwriterView (see: 
https://code.google.com/p/android/issues/detail?id=55933 for reports of similar 
issues).

TLDR:
If you have an accessibility service running (LastPass, LazySwipe, Greenify, 
etc.), you are likely to run into this issue. It's an interaction between a 
java runtime change (from version 6 to 7) and Quill which causes a crash in 
accessibility.

Workarounds:
Disable accessibility services. Unfortunately this is not a great workaround.

Fix:
Luckily, a simple fix can be applied to the code. If we disable accessibility 
specifically for HandwriterView, Quill no longer crashes. The fix is attached 
as a patch, but you'll need to grab the sources and build it yourself. You 
won't be able to install the custom build until you uninstall Quill itself 
(because of the difference in signing).

Original comment by MHag...@gmail.com on 12 Apr 2015 at 12:18

Attachments:

• patch.diff