Closed GoogleCodeExporter closed 9 years ago
--------------------
02-15 12:38:08.260 E/AndroidRuntime( 6200): FATAL EXCEPTION: Thread-300
02-15 12:38:08.260 E/AndroidRuntime( 6200): java.lang.NullPointerException
02-15 12:38:08.260 E/AndroidRuntime( 6200): at
com.android.contacts.dialpad.T9Search.initT9Map(T9Search.java:223)
02-15 12:38:08.260 E/AndroidRuntime( 6200): at
com.android.contacts.dialpad.T9Search.getAll(T9Search.java:79)
02-15 12:38:08.260 E/AndroidRuntime( 6200): at
com.android.contacts.dialpad.T9Search.<init>(T9Search.java:74)
02-15 12:38:08.260 E/AndroidRuntime( 6200): at
com.android.contacts.dialpad.DialpadFragment$2.run(DialpadFragment.java:512)
02-15 12:38:08.260 E/AndroidRuntime( 6200): at
java.lang.Thread.run(Thread.java:856)
02-15 12:38:08.265 W/ActivityManager( 1977): Force finishing activity
com.android.contacts/.activities.DialtactsActivity
---------------------------
This is the main part I am focusing on but thought I would show some of the
logcat before and after just in case I missed something.
Original comment by shaynemc...@gmail.com
on 15 Feb 2012 at 2:58
Sorry, I did search. (But obviously not hard enough)
Issue 290, has the same problem.
Original comment by shaynemc...@gmail.com
on 15 Feb 2012 at 3:21
Hello? anyone home?
Original comment by shaynemc...@gmail.com
on 24 Feb 2012 at 2:50
i have sme problem.
Original comment by Jorgef...@gmail.com
on 24 Feb 2012 at 8:34
Same issues. Unable to find resolution.
Original comment by gunther...@gmail.com
on 29 Feb 2012 at 2:09
I´ve tried compile AOSP contacts.apk 4.0.3 stock and work fine. I think the
problem is to build contacts.apk with t9 implemented. Contacts.apk whit T9
implemented not compiles fine, resources.arsc resizes.
Original comment by Jorgef...@gmail.com
on 29 Feb 2012 at 2:31
i have the same error when running a compiled phone apk and from contacts.apk
in a CM7 rom .
as jorgef suggested id like to implement t9 ..howto do it with apktool?
Original comment by drbejoya...@gmail.com
on 1 Sep 2012 at 1:58
This was a problem with <string-array> and <array> which I believe has been
fixed.
Original comment by connor.tumbleson
on 16 Nov 2012 at 11:59
Original issue reported on code.google.com by
shaynemc...@gmail.com
on 15 Feb 2012 at 2:57