G1 gets really slow when backing up >50 messages

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Have tons of SMS messages on your G1 device.
2. Start a backup with "Maximum items per sync" set to 200.

Expected:
Backup should finish successfully, each message taking about the same time
to upload.

Actual:
After about 60 messages, messages take longer and longer to upload. After
some more messages, the G1 gets really upset and sometimes even crashes.
This does not happen in the emulator, it only happens on the G1.
I ran `top` while this was happening and system_server had about 15% CPU time.

Original issue reported on code.google.com by chstu...@gmail.com on 26 Jan 2009 at 1:05

[GoogleCodeExporter]

Issue 14 has been merged into this issue.

Original comment by chstu...@gmail.com on 27 Jan 2009 at 3:09

[GoogleCodeExporter]

The current workaround is to set "Maximum number of messages per backup" to 50 
and backup incrementally. 
That's exactly why I added this setting. Maybe I should change the default to 
be 50, so it works for all users by 
default.

Eventually I hope to be able to shed some light on what's going on. But it's 
rather hard to reproduce for me and 
it looks like I'm triggering some strange behavior (bug?) in the platform.

Original comment by chstu...@gmail.com on 27 Jan 2009 at 3:38

[GoogleCodeExporter]

This issue does not occur in Android RC33 JF1.41

Original comment by michaelt...@gmail.com on 11 Feb 2009 at 7:42

[GoogleCodeExporter]

michaeltanyk, did this happen to you in a previous version of Android?

Original comment by chstu...@gmail.com on 11 Feb 2009 at 2:43

[GoogleCodeExporter]

Somebody was able to reproduce this problem. He was able to blame it on 
networking over 3G/EDGE as opposed 
to Wifi.

Original comment by chstu...@gmail.com on 30 Mar 2009 at 2:51

[GoogleCodeExporter]

I've been experiencing the crash using the latest version of Android (CRB43)
Using a setting of 200 occasionally crashes and restarts my android.
Will try using 50.

Original comment by chengt on 1 Jun 2009 at 1:29

[GoogleCodeExporter]

Crashed again using 50.
Trying again w/ 25.

Is there a way to get a crash log?

Original comment by chengt on 1 Jun 2009 at 2:36

[GoogleCodeExporter]

I too am getting this error.  During initial backup, using the default 100, the 
G1
became unresponsive after the first few, getting progressively slower, and 
ended up
crashing twice.  

Re-attempted with setting to 25...at approx 20-22, G1 becomes unresponsive and
eventually crashes.

Should be noted that i have threads exceeding 2k messages.

Original comment by Sabre...@gmail.com on 7 Jun 2009 at 9:55

[GoogleCodeExporter]

i have the same issue on the g2 too.

Original comment by marcel.b...@gmail.com on 17 Jun 2009 at 11:08

[GoogleCodeExporter]

also with a 2k+ thread and >50 sms backup at once.

Original comment by marcel.b...@gmail.com on 17 Jun 2009 at 11:10

[GoogleCodeExporter]

also running into this problem. g1, cupcake.

Original comment by nak...@gmail.com on 10 Jul 2009 at 8:14

[GoogleCodeExporter]

I didn't find this issue when I searched, but I am having the same problem with 
back-
ups of more than 50 messages.  I just set up issue #35 since I didn't see this 
one.

Original comment by green...@gmail.com on 20 Jul 2009 at 9:21

[GoogleCodeExporter]

Issue 35 has been merged into this issue.

Original comment by chstu...@gmail.com on 27 Jul 2009 at 4:14

[GoogleCodeExporter]

I have checked in a change in revision r54 that might fix this issue.

Original comment by chstu...@gmail.com on 2 Aug 2009 at 12:36

[GoogleCodeExporter]

I'm not crashing or stalling, but on a 3G connection with full bars, at 200 
per, it's
taking about 3 seconds per sms...

Hard for me to understand why a 160 byte file should take more than .001 
seconds...
may just be my expectations =/= technology reality

Original comment by Czarr....@gmail.com on 6 Feb 2010 at 4:54