Logcat

[mirajp1]

Can any body here possibly read a logcat of android?
I hope many of you

I have some problem.Here's my problem:

I absolutely love swiftkey X keyboard and cant live without it.
It increases my writing speed by 3-4 times(yes its true)

Well after an upgrade to my custom rom swiftkey X just FC on selecting as default input.I tried customer support of Swidfkey but they refused to help becoz of custom rom( ).
well my rom developer has stopped working so he's of no help too.

So I want to try to fix problem myself.I already saved a logcat of error but I dont have enough skills of understanding it.

So can anybody here help me?
Is it worth a try ?

[caga]

If you upload your logcat we can have a look.
Which phone are you using? A link to the roms thread might be useful.

cheers caga

[lady black]

I can be of absolutely no help, but wish you good luck.

[mirajp1]

My device:
Xperia X10
running 2.3.7

heres the link to the thread of rom

http://forum.xda-developers.com/showthr ... ?t=1458001


I cant attach logcat cause it says that cant upload .txt file

so heres a copy of that file :

=================================================================================================--------- beginning of /dev/log/main
--------- beginning of /dev/log/system
E/su (15014): sudb - Opening database
E/su (15014): sudb - Database opened
E/su (15014): sudb - Database closed
E/ (15001): statfs /dbdata failed, errno: 2
E/ (15001): statfs /dbdata failed, errno: 2
E/MobileDataSettingButton( 4067): activate()
E/fb_music_like(15074): downloadMusicLikes: false -> Value false of type java.lang.Boolean cannot be converted to JSONObject
E/SemcSettingsParser(15193): key not found. key=[group-visible]
E/MP3Extractor( 920): Unable to resync. Signalling end of stream.
E/AndroidRuntime(15268): FATAL EXCEPTION: main
E/AndroidRuntime(15268): java.lang.AssertionError
E/AndroidRuntime(15268): at com.touchtype.preferences.TouchTypePreferences.getString(TouchTypePreferences.java:474)
E/AndroidRuntime(15268): at com.touchtype.preferences.TouchTypePreferences.getKeyboardTheme(TouchTypePreferences.java:137)
E/AndroidRuntime(15268): at com.touchtype.keyboard.view.ThemeManager.<init>(ThemeManager.java:29)
E/AndroidRuntime(15268): at com.touchtype.keyboard.service.TouchTypeSoftKeyboard.onCreate(TouchTypeSoftKeyboard.java:215)
E/AndroidRuntime(15268): at android.app.ActivityThread.handleCreateService(ActivityThread.java:1966)
E/AndroidRuntime(15268): at android.app.ActivityThread.access$2500(ActivityThread.java:121)
E/AndroidRuntime(15268): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:997)
E/AndroidRuntime(15268): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(15268): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(15268): at android.app.ActivityThread.main(ActivityThread.java:3701)
E/AndroidRuntime(15268): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(15268): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime(15268): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:862)
E/AndroidRuntime(15268): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:620)
E/AndroidRuntime(15268): at dalvik.system.NativeStart.main(Native Method)

=================================================================================================

[caga]

As far as I can see, swiftkey has a problem with loading a theme and/or with creating the service to set itself as default keyboard.
Actually I don't have a clue what is going on there
Over at the xda thread I saw some messages about swiftkey not working on this ROM, but you have seen this this yourself I guess.

I try to investigate a little on this problem, but can't promiss anything

cheers, caga

[mirajp1]

As far as I can see, swiftkey has a problem with loading a theme and/or with creating the service to set itself as default keyboard.
Actually I don't have a clue what is going on there
Over at the xda thread I saw some messages about swiftkey not working on this ROM, but you have seen this this yourself I guess.

I try to investigate a little on this problem, but can't promiss anything

cheers, caga

yeah I constantly see the thread so i would know about the fix if it existed

thanx for the reply