[GH-ISSUE #574] App crash (f-droid) #487

New issue

Closed

opened 2026-02-26 01:30:43 +03:00 by kerem · 8 comments

kerem commented 2026-02-26 01:30:43 +03:00

Owner

Copy link

Originally created by @Mageti on GitHub (Jul 25, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/574

Hello,
SMS-backup+ crashes when I ask him to backup my SMS. It used to work correctly, but not now anymore.
Here are some informations :

• Android version 4.1.2 on Wiko Cink Peax 2
• SMS Backup+ v1.5.8 from f-droid
• I have ~11000 messages on stock SMS app
• I backup on my own IMAP server
  Log :

E/Trace   (18351): error opening trace file: No such file or directory (2)
W/dalvikvm(18351): VFY: unable to resolve static method 234: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/Context;)Ljava/lang/String;
W/dalvikvm(18351): VFY: unable to resolve static method 234: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/Context;)Ljava/lang/String;
I/System  (18191): libcore.io.ErrnoException: kill failed: EPERM (Operation not permitted)
I/System  (18191):  at libcore.io.Posix.kill(Native Method)
I/System  (18191):  at libcore.io.ForwardingOs.kill(ForwardingOs.java:77)
I/System  (18191):  at java.lang.ProcessManager$ProcessImpl.destroy(ProcessManager.java:260)
I/System  (18191):  at eu.chainfire.libsuperuser.Shell$Interactive.kill(Shell.java:1611)
I/System  (18191):  at rs.pedjaapps.alogcatroot.app.LogCat.stop(LogCat.java:162)
I/System  (18191):  at rs.pedjaapps.alogcatroot.app.LogActivity.onStop(LogActivity.java:211)
I/System  (18191):  at android.app.Instrumentation.callActivityOnStop(Instrumentation.java:1210)
I/System  (18191):  at android.app.Activity.performStop(Activity.java:5158)
I/System  (18191):  at android.app.ActivityThread.performStopActivityInner(ActivityThread.java:3128)
I/System  (18191):  at android.app.ActivityThread.handleStopActivity(ActivityThread.java:3177)
I/System  (18191):  at android.app.ActivityThread.access$900(ActivityThread.java:149)
I/System  (18191):  at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1332)
I/System  (18191):  at android.os.Handler.dispatchMessage(Handler.java:99)
I/System  (18191):  at android.os.Looper.loop(Looper.java:153)
I/System  (18191):  at android.app.ActivityThread.main(ActivityThread.java:5000)
I/System  (18191):  at java.lang.reflect.Method.invokeNative(Native Method)
I/System  (18191):  at java.lang.reflect.Method.invoke(Method.java:511)
I/System  (18191):  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:821)
I/System  (18191):  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:584)
I/System  (18191):  at dalvik.system.NativeStart.main(Native Method)
W/dalvikvm(18351): VFY: unable to resolve static method 234: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/Context;)Ljava/lang/String;
W/dalvikvm(18351): VFY: unable to resolve static field 2284 (DEFAULT) in Lorg/apache/james/mime4j/field/address/AddressBuilder;
E/dalvikvm(18351): Could not find class 'com.beetstra.jutf7.CharsetProvider', referenced from method com.fsck.k9.mail.store.imap.ImapStore.<init>
W/dalvikvm(18351): VFY: unable to resolve new-instance 133 (Lcom/beetstra/jutf7/CharsetProvider;) in Lcom/fsck/k9/mail/store/imap/ImapStore;
E/AndroidRuntime(18351): FATAL EXCEPTION: main
E/AndroidRuntime(18351): java.lang.NoClassDefFoundError: com.beetstra.jutf7.CharsetProvider
E/AndroidRuntime(18351):    at com.fsck.k9.mail.store.imap.ImapStore.<init>(ImapStore.java:356)
E/AndroidRuntime(18351):    at com.zegoggles.smssync.mail.BackupImapStore.<init>(BackupImapStore.java:60)
E/AndroidRuntime(18351):    at com.zegoggles.smssync.service.ServiceBase.getBackupImapStore(ServiceBase.java:102)
E/AndroidRuntime(18351):    at com.zegoggles.smssync.service.SmsBackupService.backup(SmsBackupService.java:105)
E/AndroidRuntime(18351):    at com.zegoggles.smssync.service.SmsBackupService.handleIntent(SmsBackupService.java:87)
E/AndroidRuntime(18351):    at com.zegoggles.smssync.service.ServiceBase.onStartCommand(ServiceBase.java:87)
E/AndroidRuntime(18351):    at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2643)
E/AndroidRuntime(18351):    at android.app.ActivityThread.access$1900(ActivityThread.java:149)
E/AndroidRuntime(18351):    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1402)
E/AndroidRuntime(18351):    at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(18351):    at android.os.Looper.loop(Looper.java:153)
E/AndroidRuntime(18351):    at android.app.ActivityThread.main(ActivityThread.java:5000)
E/AndroidRuntime(18351):    at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18351):    at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(18351):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:821)
E/AndroidRuntime(18351):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:584)
E/AndroidRuntime(18351):    at dalvik.system.NativeStart.main(Native Method)
E/AppErrorDialog(  393): Failed to get ILowStorageHandle instance
E/JavaBinder(  393): !!! FAILED BINDER TRANSACTION !!!
E/JavaBinder(  393): !!! FAILED BINDER TRANSACTION !!!

Originally created by @Mageti on GitHub (Jul 25, 2015). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/574 Hello, SMS-backup+ crashes when I ask him to backup my SMS. It used to work correctly, but not now anymore. Here are some informations : - Android version 4.1.2 on Wiko Cink Peax 2 - SMS Backup+ v1.5.8 from f-droid - I have ~11000 messages on stock SMS app - I backup on my own IMAP server Log : ``` E/Trace (18351): error opening trace file: No such file or directory (2) W/dalvikvm(18351): VFY: unable to resolve static method 234: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/Context;)Ljava/lang/String; W/dalvikvm(18351): VFY: unable to resolve static method 234: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/Context;)Ljava/lang/String; I/System (18191): libcore.io.ErrnoException: kill failed: EPERM (Operation not permitted) I/System (18191): at libcore.io.Posix.kill(Native Method) I/System (18191): at libcore.io.ForwardingOs.kill(ForwardingOs.java:77) I/System (18191): at java.lang.ProcessManager$ProcessImpl.destroy(ProcessManager.java:260) I/System (18191): at eu.chainfire.libsuperuser.Shell$Interactive.kill(Shell.java:1611) I/System (18191): at rs.pedjaapps.alogcatroot.app.LogCat.stop(LogCat.java:162) I/System (18191): at rs.pedjaapps.alogcatroot.app.LogActivity.onStop(LogActivity.java:211) I/System (18191): at android.app.Instrumentation.callActivityOnStop(Instrumentation.java:1210) I/System (18191): at android.app.Activity.performStop(Activity.java:5158) I/System (18191): at android.app.ActivityThread.performStopActivityInner(ActivityThread.java:3128) I/System (18191): at android.app.ActivityThread.handleStopActivity(ActivityThread.java:3177) I/System (18191): at android.app.ActivityThread.access$900(ActivityThread.java:149) I/System (18191): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1332) I/System (18191): at android.os.Handler.dispatchMessage(Handler.java:99) I/System (18191): at android.os.Looper.loop(Looper.java:153) I/System (18191): at android.app.ActivityThread.main(ActivityThread.java:5000) I/System (18191): at java.lang.reflect.Method.invokeNative(Native Method) I/System (18191): at java.lang.reflect.Method.invoke(Method.java:511) I/System (18191): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:821) I/System (18191): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:584) I/System (18191): at dalvik.system.NativeStart.main(Native Method) W/dalvikvm(18351): VFY: unable to resolve static method 234: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/Context;)Ljava/lang/String; W/dalvikvm(18351): VFY: unable to resolve static field 2284 (DEFAULT) in Lorg/apache/james/mime4j/field/address/AddressBuilder; E/dalvikvm(18351): Could not find class 'com.beetstra.jutf7.CharsetProvider', referenced from method com.fsck.k9.mail.store.imap.ImapStore.<init> W/dalvikvm(18351): VFY: unable to resolve new-instance 133 (Lcom/beetstra/jutf7/CharsetProvider;) in Lcom/fsck/k9/mail/store/imap/ImapStore; E/AndroidRuntime(18351): FATAL EXCEPTION: main E/AndroidRuntime(18351): java.lang.NoClassDefFoundError: com.beetstra.jutf7.CharsetProvider E/AndroidRuntime(18351): at com.fsck.k9.mail.store.imap.ImapStore.<init>(ImapStore.java:356) E/AndroidRuntime(18351): at com.zegoggles.smssync.mail.BackupImapStore.<init>(BackupImapStore.java:60) E/AndroidRuntime(18351): at com.zegoggles.smssync.service.ServiceBase.getBackupImapStore(ServiceBase.java:102) E/AndroidRuntime(18351): at com.zegoggles.smssync.service.SmsBackupService.backup(SmsBackupService.java:105) E/AndroidRuntime(18351): at com.zegoggles.smssync.service.SmsBackupService.handleIntent(SmsBackupService.java:87) E/AndroidRuntime(18351): at com.zegoggles.smssync.service.ServiceBase.onStartCommand(ServiceBase.java:87) E/AndroidRuntime(18351): at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2643) E/AndroidRuntime(18351): at android.app.ActivityThread.access$1900(ActivityThread.java:149) E/AndroidRuntime(18351): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1402) E/AndroidRuntime(18351): at android.os.Handler.dispatchMessage(Handler.java:99) E/AndroidRuntime(18351): at android.os.Looper.loop(Looper.java:153) E/AndroidRuntime(18351): at android.app.ActivityThread.main(ActivityThread.java:5000) E/AndroidRuntime(18351): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(18351): at java.lang.reflect.Method.invoke(Method.java:511) E/AndroidRuntime(18351): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:821) E/AndroidRuntime(18351): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:584) E/AndroidRuntime(18351): at dalvik.system.NativeStart.main(Native Method) E/AppErrorDialog( 393): Failed to get ILowStorageHandle instance E/JavaBinder( 393): !!! FAILED BINDER TRANSACTION !!! E/JavaBinder( 393): !!! FAILED BINDER TRANSACTION !!! ```

kerem 2026-02-26 01:30:43 +03:00

• closed this issue
• added the
  v1.5.9
  label

kerem commented 2026-02-26 01:30:44 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (Jul 26, 2015):

some of f-droid's version are broken, and 1.5.9 is not published there yet.
@RealRancor anything i can do to help to get a new version out?

for reference: #525

<!-- gh-comment-id:125040239 --> @jberkel commented on GitHub (Jul 26, 2015): some of f-droid's version are broken, and 1.5.9 is not published there yet. @RealRancor anything i can do to help to get a new version out? for reference: #525

kerem commented 2026-02-26 01:30:44 +03:00

Author

Owner

Copy link

@ghost commented on GitHub (Jul 28, 2015):

@jberkel Thanks for the notification. Seems some one already opened an merge request for the new update: https://gitlab.com/fdroid/fdroiddata/merge_requests/893

<!-- gh-comment-id:125726671 --> @ghost commented on GitHub (Jul 28, 2015): @jberkel Thanks for the notification. Seems some one already opened an merge request for the new update: https://gitlab.com/fdroid/fdroiddata/merge_requests/893

kerem commented 2026-02-26 01:30:44 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (Jul 28, 2015):

@RealRancor ah ok. i somehow assumed the process was automated, at least partially. so whenever i publish a new version i need to open a merge request on gitlab?

<!-- gh-comment-id:125729591 --> @jberkel commented on GitHub (Jul 28, 2015): @RealRancor ah ok. i somehow assumed the process was automated, at least partially. so whenever i publish a new version i need to open a merge request on gitlab?

kerem commented 2026-02-26 01:30:44 +03:00

Author

Owner

Copy link

@ghost commented on GitHub (Jul 28, 2015):

@jberkel Depends on the build receipt. Currently the k9lib dependency needs to be updated manually so thats probably the reason why its not set to auto-update. But maybe @krt16s can give you some more background info.

<!-- gh-comment-id:125733207 --> @ghost commented on GitHub (Jul 28, 2015): @jberkel Depends on the build receipt. Currently the k9lib dependency needs to be updated manually so thats probably the reason why its not set to auto-update. But maybe @krt16s can give you some more background info.

kerem commented 2026-02-26 01:30:44 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (Jul 28, 2015):

@RealRancor OK. but i'm unclear where f-droids "build everything from source" philopsophy ends? if an artifact is hosted on maven central it surely won't have to be build from source each time?

<!-- gh-comment-id:125734145 --> @jberkel commented on GitHub (Jul 28, 2015): @RealRancor OK. but i'm unclear where f-droids "build everything from source" philopsophy ends? if an artifact is hosted on maven central it surely won't have to be build from source each time?

kerem commented 2026-02-26 01:30:44 +03:00

Author

Owner

Copy link

@ghost commented on GitHub (Jul 28, 2015):

I don't know the reason of the dependency but will have a look in a few days if the build receipt can be changed to only use your pom.xml

<!-- gh-comment-id:125735060 --> @ghost commented on GitHub (Jul 28, 2015): I don't know the reason of the dependency but will have a look in a few days if the build receipt can be changed to only use your pom.xml

kerem commented 2026-02-26 01:30:44 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (Aug 2, 2015):

@Mageti there's a new version on f-droid now, please upgrade and test again with 1.5.9

<!-- gh-comment-id:127031012 --> @jberkel commented on GitHub (Aug 2, 2015): @Mageti there's a new version on f-droid now, please upgrade and test again with 1.5.9

kerem commented 2026-02-26 01:30:44 +03:00

Author

Owner

Copy link

@Mageti commented on GitHub (Aug 3, 2015):

Just tested that, and it works.
Thank you very much !

<!-- gh-comment-id:127197331 --> @Mageti commented on GitHub (Aug 3, 2015): Just tested that, and it works. Thank you very much !

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

cyber1000-docker

multisim

update-build-process

gh-pages

jcrben-patch-1

workmanager

jcrben-patch-2

old-sms-backup

1.6.0-BETA2

1.6.0-BETA1

1.5.11

1.5.11-BETA22

1.5.11-BETA21

1.5.11-BETA20

1.5.11-BETA19

1.5.11-BETA18

1.5.11-BETA17

1.5.11-BETA16

1.5.11-BETA15

1.5.11-BETA14

1.5.11-BETA13

1.5.11-BETA12

1.5.11-BETA11

1.5.11-BETA10

1.5.11-BETA9

1.5.11-BETA8

1.5.11-BETA7

1.5.11-BETA6

1.5.11-BETA5

1.5.11-BETA4

1.5.11-BETA3

1.5.11-BETA2

1.5.11-BETA1

1.5.10

1.5.10-BETA1

1.5.9

1.5.9-BETA6

1.5.9-BETA5

1.5.9-BETA4

1.5.9-BETA3

1.5.9-BETA2

1.5.9-BETA1

1.5.8

1.5.8-BETA2

1.5.8-BETA1

1.5.7

1.5.7-BETA2

1.5.7-BETA1

1.5.6-DEBUG

1.5.6

1.5.6-RC1

1.5.6-BETA11

1.5.6-BETA10

1.5.6-BETA9

1.5.6-BETA8

1.5.6-BETA7

1.5.6-BETA6

1.5.6-BETA5

1.5.6-BETA4

1.5.6-BETA3

1.5.6-BETA2

1.5.6-BETA1

1.5.5

1.5.5-BETA2

1.5.5-BETA1

1.5.4

1.5.4-BETA2

1.5.4-BETA1

1.5.3

1.5.2

1.5.1

1.5.0

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.1

1.3.2

1.3

1.2

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1

1.0.11

1.0.10

1.0.9

1.0.8

1.0.7

1.0.6

1.0.5

1.0.4

1.0.3

1.0.2

1.0.1

1.0

Labels

Clear labels   

AM+RCS

  

FAQ

  

awaiting response

  

backup

  

bespoke

  

bug

  

calendar

  

call log

  

cannot reproduce

  

cloudless

  

device-specific

  

documentation

  

dual- & multi-SIM

  

duplicate

  

feature-request

  

fixed in beta

  

good first issue

  

half-missing

  

help wanted

  

helpful

  

meta

  

misattribution

  

mms

  

other message sources

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

rejuvenation

  

restore

  

schedule

  

security

  

stale

  

task

  

thanks

  

v1.5.1

  

v1.5.10

  

v1.5.11

  

v1.5.2

  

v1.5.3

  

v1.5.3

  

v1.5.4

  

v1.5.4

  

v1.5.5

  

v1.5.5

  

v1.5.6

  

v1.5.7

  

v1.5.8

  

v1.5.9

  

v1.6β

  

xoauth

  

~$ bounty $~

No labels

AM+RCS

FAQ

awaiting response

backup

bespoke

bug

calendar

call log

cannot reproduce

cloudless

device-specific

documentation

dual- & multi-SIM

duplicate

feature-request

fixed in beta

good first issue

half-missing

help wanted

helpful

meta

misattribution

mms

other message sources

pull-request

question

rejuvenation

restore

schedule

security

stale

task

thanks

v1.5.1

v1.5.10

v1.5.11

v1.5.2

v1.5.3

v1.5.3

v1.5.4

v1.5.4

v1.5.5

v1.5.5

v1.5.6

v1.5.7

v1.5.8

v1.5.9

v1.6β

xoauth

~$ bounty $~

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/sms-backup-plus-jberkel#487

No description provided.