mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #499] I/O ERROR (timeout after 5 minutes) #423
Labels
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 $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#423
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @LSmith6938 on GitHub (Nov 23, 2014).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/499
getting I/O Error when trying to back up about 22k text messages. error occurs after several hundred messages have been "backed up"... it stops backing up between 500 and 1000 messages, randomly. i have disabled wifi backup, enabled wifi backup, restarted the app, reset the app, uninstalled the app, checked gmail settings, etc.
what's interesting is that the app says it's backing up, but does not create gmail messages. the folder is empty, even though SMS backup tells me it's backed up a number of messages. i only have 1 gmail account linked on my phone.
please help. i desperately need to data reset my nexus 5, and i dont want to lose my texts, so i've been waiting to data reset the phone until after i have backed up all my texts.
here is the link to the sync log:
https://gist.github.com/LSmith6938/dc9b14681caf6d2592dc
@jberkel commented on GitHub (Nov 23, 2014):
weird, looks like this is a timeout issue. how many messages are already stored on the gmail side, in the SMS folder ? you could try moving some of them to a different label (temporarily) before doing the backup.
@LSmith6938 commented on GitHub (Nov 23, 2014):
so, i moved all my backed up text messages to a new folder i just created ' SMS 2 '
SMS back up is being told to back everything up to the SMS folder in gmail. i tried it again, still getting the same I/O error.
@jberkel commented on GitHub (Nov 23, 2014):
i'm running out of ideas. the default timeout is 5 minutes, and looking at your logs it always happens 5 minutes after the backup got initiated. i think the backup never started properly and you get the timeout whilst connecting to the server. do you use the standard gmail config?
@jberkel commented on GitHub (Nov 23, 2014):
also if possible, can you paste the full adb log while doing a backup ? it might help to debug
@LSmith6938 commented on GitHub (Nov 23, 2014):
how would i do this?
@jberkel commented on GitHub (Nov 23, 2014):
if you have a rooted phone you can use this app: https://play.google.com/store/apps/details?id=org.jtb.alogcat
if not, you'll need to install the android sdk and then use the
adb logcatcommand https://developer.android.com/tools/help/logcat.html@LSmith6938 commented on GitHub (Nov 29, 2014):
i'm more of a intermediate smart phone user... not an advanced user. i've clicked the link you provided, but i'm not sure where to go to download and install this program. could you give me more specific instructions? sorry to be a pain. :/
@flomin commented on GitHub (Dec 11, 2014):
Hi,
I just got the same problem: backup wouldn't finish with IO Error during calculating phase.
So I disconnected and reconnected to my gmail account and it started to backup the sms from the start. It seems I still have the SMS messages on my account in only one copy without changing anything on gmail. But it stucked at some point with the same error. There are already 20k+ messages saved on my account and still 2080 messages to backup.
I tried to move all messages to another label on gmail, but I still get the same error.
The error comes after a timeout of five minutes during the calculating phase.
Here is the logcat filtered for appname 'com.zegoggles.smssync':
I can do some more tests if you'd like. I really want to backup my messages before trying to update my cyanogenmod rom...
Btw aLogcat doesn't seem to be able to read logs past his, you need to grant him permission by console with root access...
@jberkel commented on GitHub (Dec 11, 2014):
@flomin does this happen consistently? i will send you a build which has more logging enabled, maybe it will help
@jberkel commented on GitHub (Dec 11, 2014):
@flomin please reproduce with https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.6-BETA6 and post logs again
@LSmith6938 commented on GitHub (Dec 11, 2014):
please let me know if there is anything i can do to help with this. i'm no expert, but i can certainly follow directions.
i've been putting off a much needed data reset for about a month now. :)
@flomin commented on GitHub (Dec 11, 2014):
@jberkel I tried several times because the backup of all the messages took something like 12 hours and I had several IO Errors due to wifi deconnections when I used my phone or moved too far away. And at the end I got a few IO Errors before it worked for the last time. Now it's consistent, the IO Error happens every time, and I tried something like 10 times in a row.
I'll install the beta version and give you the logcat result ! I just hope it won't start backing up everything again or it'll take a very long time...
@flomin commented on GitHub (Dec 11, 2014):
Ok I got the same error with the new version (which updated the old one, so no need to backup everything again).
Just for the information, I currently have a SMS label on gmail which is empty and a SMS-Old label nested in it which contains 1141 conversations (more than 22k messages, I don't know how to have the exact number on gmail).
Here is the logcat (I removed personal information):
@jberkel commented on GitHub (Dec 11, 2014):
@flomin this is very useful, thanks. i have some ideas what might cause this. in the meantime, does it always happen with the same message ? you can tell by looking at the
APPENDline just before it stops:If it always stops during this message it might be an indication that the timeout is caused by one specific SMS on the device, rather than a random failure.
@flomin commented on GitHub (Dec 11, 2014):
Here are a few other logs:
Both APPEND lines:
So it seems its a message which is in fault. How can I find this particular message easily ?
@flomin commented on GitHub (Dec 11, 2014):
I found the faulty message, which is quite personal (too much for public forum :-P).
I can say it's a really long message (2567chars), which was sent using SMS (several SMS used to transmit the whole one). I can't see any problematic char in it, perhaps it's its length which causes problem ?
I have a lot of very big SMS afterwards (big epistolary correspondence), so removing this one won't solve the issue (and I'd like to keep it if possible).
@jberkel commented on GitHub (Dec 11, 2014):
@flomin ok that's a good pointer, it might be the length. i'll send you a new version to try soon
@jberkel commented on GitHub (Dec 11, 2014):
@flomin ok, please try again with https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.6-BETA7
it's a stab in the dark since i can't reprodruce locally, but it might fix the problem
@flomin commented on GitHub (Dec 12, 2014):
@jberkel Same error after five minutes, but no APPEND message this time:
Can't you send yourself a big message to test ?
@jberkel commented on GitHub (Dec 12, 2014):
i tried it, didn't hang.... at least on the emulator. have some more ideas how to fix it, i'll keep you posted
@jberkel commented on GitHub (Dec 16, 2014):
@flomin ok, there's another beta for you to try, it has lots more debug enabled so should help. there's a lot of new code in there as well so other things might get broken
https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.6-BETA9
@flomin commented on GitHub (Dec 16, 2014):
@jberkel With the new version the backup began just fine !
But after a while it stopped with another IO Error which is reproductible.
Here are the intial working log, the first error after some successful backups, and the reproduced error.
I couldn't find the APPEND log with the faulty SMS details this time.
@jberkel commented on GitHub (Dec 16, 2014):
cool, that's helpful. i think basically what happens is the following:
APPEND "SMS" (\Seen) {1143}conn1107852472<<<#+# [go ahead]now need to figure out why this happens. what i don't understand is that if there's some elementary flaw with the logic a lot more users should be affected by this problem
@flomin commented on GitHub (Dec 16, 2014):
Can't you add a log for the size of data sent ? Even if very verbose, for debug usage, it would be very useful. And perhaps put back the date of the backing up message to be able to find it and see why it could pose problem?
@jberkel commented on GitHub (Dec 17, 2014):
@flomin this is one of the most annoying bugs i've encountered so far.
i've created a new version which will dump the size and content of the whole message to the log once it gets stuck, this should hopefully help:
https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.6-BETA10
@flomin commented on GitHub (Dec 17, 2014):
@jberkel If it can reassure you, I had worse, with nobody to help debug, just random bugs coming from specific devices which completely crashed the system and not reproducible... I only had the ACRA reports. I spent weeks on this one...
On the bright side, this version works ! At least for now, 300 messages saved on 2367. And the backup seems to be much quicker than before. I'll tell you the result when it stops. Here is the log so far:
@jberkel commented on GitHub (Dec 17, 2014):
cool, fingers crossed
@flomin commented on GitHub (Dec 17, 2014):
There was this one error during the save, but not blocking.
Now it's backing up the MMS !
Can I be sure all the SMS got backed up ?
@flomin commented on GitHub (Dec 17, 2014):
I worked !
The MMS got backed up too and everything seems fine !
@jberkel commented on GitHub (Dec 17, 2014):
phew.. glad this one's fixed. still not 100% sure what caused it, but will find out i hope
@flomin commented on GitHub (Dec 17, 2014):
Yes thanks a lot for this !
There is one problem though: I tend to send a lot of MMS, and as the MMS are backed up after the SMS, they are completely out of timeline on my mail account, even if the date is OK. Isn't it possible to save them at the same time as the SMS ?
I also got some whatsapp messages which were not backed up: 'D/Whassup(17421): could not find db' in the log.
But these are other bugs I can fill different bug reports if you like.
@jberkel commented on GitHub (Dec 17, 2014):
you mean the date on the mail itself is ok, but is displayed out of order? the time when the mail saved should not have an effect on the way it is displayed, but gmail is always a bit particular. i would first check if the ordering is ok if you look at the folder with a normal mail client, not gmail. it might be gmail's internal threading which gets easily confused. and yes, please report as new bug....
did you enable whatsapp backups? if not it should not show the debug message...
@jberkel commented on GitHub (Dec 17, 2014):
@LSmith6938 could you try with https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.6-BETA10 as well and report back? thanks!
@flomin commented on GitHub (Dec 17, 2014):
Thanks a lot for the time you spent solving this issue !
SMS and MMS timeline issue here: https://github.com/jberkel/sms-backup-plus/issues/509
Whatsapp issue here: https://github.com/jberkel/sms-backup-plus/issues/510
@flomin commented on GitHub (Dec 17, 2014):
BTW, you should add ACRA to log debug informations on errors, it's great ! I developed a PHP website to manage (a lot) of ACRA issues. Not perfect, but worth it, if you'd like to try...
@LSmith6938 commented on GitHub (Dec 18, 2014):
hi everyone -- thanks for your help with this! i have initiated the back up process. it seems to be working, as the text messages are now showing in the SMS gmail label. i have about 26k pending texts, so this is going to take all day. i'll sign back in tomorrow when this is complete to let you know it finished. :)
@jberkel commented on GitHub (Dec 18, 2014):
great to hear, hope it works out. and also wondering how you managed to accumulate 26k worth of text messages :)
@jberkel commented on GitHub (Dec 19, 2014):
i'm closing this for now. reopen if problem occurs again
@LSmith6938 commented on GitHub (Dec 19, 2014):
thanks! it took all day, but i got everything backed up! i am an avid texter -- i usually hit about 5k/month. :D
i've been using your app for years, btw. it's awesome!
@robotcmastr5000 commented on GitHub (Nov 28, 2016):
Was running a Sprint Note 4 With Marshmallow update. SMS Backup + has worked on there. I can see all the messages in my gmail. However, my note 4 stopped working. And I now have a galaxy s7 running marshmallow as well. But i cannot get SMS Backup + to restore with out the I/O Error - Please help?
@Fisherpon commented on GitHub (Dec 19, 2017):
I'm on a Samsung S8 running Android 7.0, and I'm having the same issue as this thread (I/O error between 500 and 1000 messages). I tried installing the beta APK that seemed to fix it for others (https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.6-BETA10), but it wouldn't let me install it as 'the packet seems to be corrupt' (Can't remember if it said packet or package). Was that beta APK rolled out into the main app at any point?