SMS Backup Constantly Force Closing

[JaceMan]

SMS Backup has long been one of my favorite apps. After upgrading to Cyanogen today, I have noticed that every time SMS Backup attempts to sync with Gmail I receive a force close error. Anyone else on Cyanogen and using SMS Backup? I wasn't encountering any problems under JF.

Thanks in advance.

[Fare]

What version did you upgrade to/what version did you upgrade from?

fine and dandy on a 4.2.2 (this is of a concern to me as I wanted to upgrade to 4.2.5 today)

[JaceMan]

I upgraded from JF 1.51 to Cy4.2.5

[JaceMan]

Apparently nobody else is on Cyanogen 4.2.5 who happens to be a fan of SMS Backup... with that in mind, can anyone else recommend another app that auto backs-up your SMS messages to Gmail?

[dazw]

Hi,

i have the same problems with SMS Backup since i upgraded from 4.2.4 to 4.2.5.

f.e.:

If there are 4 SMS to backup, SMS Backup backups the first one and then it dies.
If i restart the app, there are 3 SMS left....
That's kinda ***** but i can backup my SMS one by one

SMS Backups writes the stacktrace to /data/anr/traces.txt.

Maybe someone can handle this trace

----- pid 3646 at 2009-11-18 14:20:36 -----
Cmd line: tv.studer.smssync

DALVIK THREADS:
"main" prio=5 tid=3 WAIT
| group="main" sCount=1 dsCount=0 s=N obj=0x4001e250 self=0xbc20
| sysTid=3646 nice=0 sched=0/0 cgrp=default handle=-1344001384
at java.lang.Object.wait(Native Method)
- waiting on <0x1cfd38> (a android.os.MessageQueue)
at java.lang.Object.wait(Object.java:288)
at android.os.MessageQueue.next(MessageQueue.java:148 )
at android.os.Looper.loop(Looper.java:110)
at android.app.ActivityThread.main(ActivityThread.jav a:4203)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:791)
at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:549)
at dalvik.system.NativeStart.main(Native Method)

"Thread-8" prio=5 tid=15 NATIVE
| group="main" sCount=1 dsCount=0 s=N obj=0x4369eef0 self=0x1ec7b8
| sysTid=3654 nice=10 sched=0/0 cgrp=bg_non_interactive handle=2017488
at android.os.BinderProxy.transact(Native Method)
at android.app.ActivityManagerProxy.handleApplication Error(ActivityManagerNative.java:2243)
at com.android.internal.os.RuntimeInit.crash(RuntimeI nit.java:302)
at com.android.internal.os.RuntimeInit$UncaughtHandle r.uncaughtException(RuntimeInit.java:75)
at java.lang.ThreadGroup.uncaughtException(ThreadGrou p.java:887)
at java.lang.ThreadGroup.uncaughtException(ThreadGrou p.java:884)

"Binder Thread #2" prio=5 tid=13 NATIVE
| group="main" sCount=1 dsCount=0 s=N obj=0x43659908 self=0x152ff0
| sysTid=3651 nice=0 sched=0/0 cgrp=default handle=1396176
at dalvik.system.NativeStart.run(Native Method)

"Binder Thread #1" prio=5 tid=11 NATIVE
| group="main" sCount=1 dsCount=0 s=N obj=0x43659848 self=0x15cec0
| sysTid=3650 nice=0 sched=0/0 cgrp=default handle=1541552
at dalvik.system.NativeStart.run(Native Method)

"JDWP" daemon prio=5 tid=9 VMWAIT
| group="system" sCount=1 dsCount=0 s=N obj=0x436582a0 self=0x15cda8
| sysTid=3649 nice=0 sched=0/0 cgrp=default handle=1539072
at dalvik.system.NativeStart.run(Native Method)

"Signal Catcher" daemon prio=5 tid=7 RUNNABLE
| group="system" sCount=0 dsCount=0 s=N obj=0x436581e8 self=0x15d268
| sysTid=3648 nice=0 sched=0/0 cgrp=default handle=1538600
at dalvik.system.NativeStart.run(Native Method)

"HeapWorker" daemon prio=5 tid=5 VMWAIT
| group="system" sCount=1 dsCount=0 s=N obj=0x4289da00 self=0x154cb8
| sysTid=3647 nice=0 sched=0/0 cgrp=default handle=1538304
at dalvik.system.NativeStart.run(Native Method)

----- end 3646 -----

Sorry, for my bad englisch

Greetings from Germany

[cerebro84]

I've got the very same problem, doesn't anybody know how to solve it? Cyanogen 4.2.5