[GH-ISSUE #557] StrictMode policy violation; ~duration=60 ms: android.os.StrictMode$StrictModeDiskWriteViolation: policy=2069 violation=1 #474

Closed
opened 2026-02-26 01:30:41 +03:00 by kerem · 1 comment
Owner

Originally created by @haridsv on GitHub (May 22, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/557

Just happened to notice this exception coming in logcat, and I suspect it sometimes makes the save fail. I am however not sure what causes it or how to fix it.

D/StrictMode( 2875): StrictMode policy violation; ~duration=60 ms: android.os.StrictMode$StrictModeDiskWriteViolation: policy=2069 violation=1
D/StrictMode( 2875):    at android.os.StrictMode$AndroidBlockGuardPolicy.onWriteToDisk(StrictMode.java:1111)
D/StrictMode( 2875):    at libcore.io.BlockGuardOs.remove(BlockGuardOs.java:254)
D/StrictMode( 2875):    at java.io.File.delete(File.java:313)
D/StrictMode( 2875):    at android.app.SharedPreferencesImpl.writeToFile(SharedPreferencesImpl.java:611)
D/StrictMode( 2875):    at android.app.SharedPreferencesImpl.access$800(SharedPreferencesImpl.java:51)
D/StrictMode( 2875):    at android.app.SharedPreferencesImpl$2.run(SharedPreferencesImpl.java:512)
D/StrictMode( 2875):    at android.app.SharedPreferencesImpl.enqueueDiskWrite(SharedPreferencesImpl.java:533)
D/StrictMode( 2875):    at android.app.SharedPreferencesImpl.access$100(SharedPreferencesImpl.java:51)
D/StrictMode( 2875):    at android.app.SharedPreferencesImpl$EditorImpl.commit(SharedPreferencesImpl.java:455)
D/StrictMode( 2875):    at com.zegoggles.smssync.preferences.Preferences.setReferenceUid(Preferences.java:122)
D/StrictMode( 2875):    at com.zegoggles.smssync.mail.MessageConverter.<init>(MessageConverter.java:78)
D/StrictMode( 2875):    at com.zegoggles.smssync.service.BackupTask.<init>(BackupTask.java:69)
D/StrictMode( 2875):    at com.zegoggles.smssync.service.SmsBackupService.getBackupTask(SmsBackupService.java:168)
D/StrictMode( 2875):    at com.zegoggles.smssync.service.SmsBackupService.backup(SmsBackupService.java:105)
D/StrictMode( 2875):    at com.zegoggles.smssync.service.SmsBackupService.handleIntent(SmsBackupService.java:87)
D/StrictMode( 2875):    at com.zegoggles.smssync.service.ServiceBase.onStartCommand(ServiceBase.java:87)
D/StrictMode( 2875):    at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2897)
D/StrictMode( 2875):    at android.app.ActivityThread.access$2100(ActivityThread.java:151)
D/StrictMode( 2875):    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1401)
D/StrictMode( 2875):    at android.os.Handler.dispatchMessage(Handler.java:102)
D/StrictMode( 2875):    at android.os.Looper.loop(Looper.java:135)
D/StrictMode( 2875):    at android.app.ActivityThread.main(ActivityThread.java:5257)
D/StrictMode( 2875):    at java.lang.reflect.Method.invoke(Native Method)
D/StrictMode( 2875):    at java.lang.reflect.Method.invoke(Method.java:372)
D/StrictMode( 2875):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
D/StrictMode( 2875):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Originally created by @haridsv on GitHub (May 22, 2015). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/557 Just happened to notice this exception coming in logcat, and I suspect it sometimes makes the save fail. I am however not sure what causes it or how to fix it. ``` D/StrictMode( 2875): StrictMode policy violation; ~duration=60 ms: android.os.StrictMode$StrictModeDiskWriteViolation: policy=2069 violation=1 D/StrictMode( 2875): at android.os.StrictMode$AndroidBlockGuardPolicy.onWriteToDisk(StrictMode.java:1111) D/StrictMode( 2875): at libcore.io.BlockGuardOs.remove(BlockGuardOs.java:254) D/StrictMode( 2875): at java.io.File.delete(File.java:313) D/StrictMode( 2875): at android.app.SharedPreferencesImpl.writeToFile(SharedPreferencesImpl.java:611) D/StrictMode( 2875): at android.app.SharedPreferencesImpl.access$800(SharedPreferencesImpl.java:51) D/StrictMode( 2875): at android.app.SharedPreferencesImpl$2.run(SharedPreferencesImpl.java:512) D/StrictMode( 2875): at android.app.SharedPreferencesImpl.enqueueDiskWrite(SharedPreferencesImpl.java:533) D/StrictMode( 2875): at android.app.SharedPreferencesImpl.access$100(SharedPreferencesImpl.java:51) D/StrictMode( 2875): at android.app.SharedPreferencesImpl$EditorImpl.commit(SharedPreferencesImpl.java:455) D/StrictMode( 2875): at com.zegoggles.smssync.preferences.Preferences.setReferenceUid(Preferences.java:122) D/StrictMode( 2875): at com.zegoggles.smssync.mail.MessageConverter.<init>(MessageConverter.java:78) D/StrictMode( 2875): at com.zegoggles.smssync.service.BackupTask.<init>(BackupTask.java:69) D/StrictMode( 2875): at com.zegoggles.smssync.service.SmsBackupService.getBackupTask(SmsBackupService.java:168) D/StrictMode( 2875): at com.zegoggles.smssync.service.SmsBackupService.backup(SmsBackupService.java:105) D/StrictMode( 2875): at com.zegoggles.smssync.service.SmsBackupService.handleIntent(SmsBackupService.java:87) D/StrictMode( 2875): at com.zegoggles.smssync.service.ServiceBase.onStartCommand(ServiceBase.java:87) D/StrictMode( 2875): at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2897) D/StrictMode( 2875): at android.app.ActivityThread.access$2100(ActivityThread.java:151) D/StrictMode( 2875): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1401) D/StrictMode( 2875): at android.os.Handler.dispatchMessage(Handler.java:102) D/StrictMode( 2875): at android.os.Looper.loop(Looper.java:135) D/StrictMode( 2875): at android.app.ActivityThread.main(ActivityThread.java:5257) D/StrictMode( 2875): at java.lang.reflect.Method.invoke(Native Method) D/StrictMode( 2875): at java.lang.reflect.Method.invoke(Method.java:372) D/StrictMode( 2875): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903) D/StrictMode( 2875): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698) ```
kerem closed this issue 2026-02-26 01:30:41 +03:00
Author
Owner

@jberkel commented on GitHub (Jun 3, 2015):

this is just a warning and can be ignored. should not show up in the logs though.

<!-- gh-comment-id:108596514 --> @jberkel commented on GitHub (Jun 3, 2015): this is just a warning and can be ignored. should not show up in the logs though.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
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#474
No description provided.