Samsung Galaxy S crashes - vibrates once, pauses, then vibrates three times.

[extorian]

My phone has started crashing more and more frequently. This started since upgrading to FroYo (UK). The first time it was when I was doing an "Update all" in the Market, and maybe one in 5 apps I update even if I do it manually. It happens frequently in the stock browser (not Dolphin HD though), and randomly when the phone is in standby (I've had acore do it, twlauncher do it, the sound system do it, gmail do it, you name it).

The crash is different from your normal force closes. What happens is the phone pulse vibrates once, pauses, then vibrates three times. During the pause the screen goes black (but the notification bar remains). The pause can last anything from half a second to maybe 30 seconds. Then when it does the three pulse vibrate the home screen returns. There is a brief flash of some dialog box, but it instantly disappears and I don't have time to read it.

The system logs show:

12-12 10:14:30.411: DEBUG/GmailNotifier(5912): New email for [email address removed] unreadCount:1
12-12 10:14:30.411: INFO/global(2472): Default buffer size used in BufferedInputStream constructor. It would be better to be explicit if an 8k buffer is required.
12-12 10:14:30.426: DEBUG/Gmail(5406): MailProvider.query: content://gmail-ls/conversations/[email address removed](label:^^unseen-^i, null)
12-12 10:14:30.461: DEBUG/Gmail(5406): MailProvider.query: content://gmail-ls/conversations/[email address removed](label:^i, [SELECTION_ARGUMENT_DO_NOT_BECOME_ACTIVE_NETWORK_CURSOR])
12-12 10:14:30.508: DEBUG/GmailNotifier(5912): Notifying account:[email address removed] schedule:0 interval:300000 repeats:100 visible:true nicon:nicon_20 ledmode:off ledcolor:none vibrationmode:off ringtoneUri:content://media/internal/audio/media/38 gmstylefirst:true
12-12 10:14:30.520: INFO/NotificationService(2472): Normal Sound PLAY ... content://media/internal/audio/media/38
12-12 10:14:30.520: INFO/NotificationService(2472): Sound <1>
12-12 10:14:30.809: INFO/MediaPlayer(2472): uri is:content://media/internal/audio/media/38
12-12 10:14:30.809: INFO/MediaPlayer(2472): inside  getAudioFilePath: content://media/internal/audio/media/38
12-12 10:14:30.829: INFO/MediaPlayer(2472): The actual path is:/system/media/audio/notifications/01_Sherbet.ogg
12-12 10:14:30.832: INFO/MediaPlayer(2472): path is: /system/media/audio/notifications/01_Sherbet.ogg
12-12 10:14:30.832: INFO/MediaPlayer(2472): file path found for DRM file:path is: /system/media/audio/notifications/01_Sherbet.ogg
12-12 10:14:30.868: INFO/AudioService(2472):  AudioFocus  requestAudioFocus() from android.media.AudioManager@482f5c88
12-12 10:14:30.872: DEBUG/AudioHardwareALSA(2367): AudioStreamOutALSA::setParameters() routing=2
12-12 10:14:30.872: DEBUG/AudioHardwareALSA(2367):  ALSA OPEN mode 0,device 2 
12-12 10:14:30.872: INFO/AudioHardwareALSA(2367): Try to open ALSA PLAYBACK device AndroidPlayback_Speaker_normal
12-12 10:14:30.907: INFO/AudioHardwareALSA(2367): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_normal
12-12 10:14:30.907: DEBUG/AudioHardwareALSA(2367): Set PLAYBACK PCM format to S16_LE (Signed 16 bit Little Endian)
12-12 10:14:30.907: DEBUG/AudioHardwareALSA(2367): Using 2 channels for PLAYBACK.
12-12 10:14:30.907: DEBUG/AudioHardwareALSA(2367): Set PLAYBACK sample rate to 44100 HZ
12-12 10:14:30.907: DEBUG/AudioHardwareALSA(2367): Buffer size: 2048
12-12 10:14:30.907: DEBUG/AudioHardwareALSA(2367): Latency: 46439
12-12 10:14:31.657: INFO/DEBUG(2361): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-12 10:14:31.657: INFO/DEBUG(2361): Build fingerprint: 'samsung/GT-I9000/GT-I9000/GT-I9000:2.2/FROYO/XXJPO:user/release-keys'
12-12 10:14:31.657: INFO/DEBUG(2361): pid: 2367, tid: 2470  >>> /system/bin/mediaserver <<<
12-12 10:14:31.657: INFO/DEBUG(2361): signal 4 (SIGILL), fault addr 80b00944
12-12 10:14:31.657: INFO/DEBUG(2361):  r0 00029588  r1 00029588  r2 80c029cc  r3 80c020a8
12-12 10:14:31.657: INFO/DEBUG(2361):  r4 80b010d0  r5 00027070  r6 00029588  r7 00002000
12-12 10:14:31.668: INFO/DEBUG(2361):  r8 00029588  r9 00026d50  10 a979bfe8  fp 00000001
12-12 10:14:31.668: INFO/DEBUG(2361):  ip 00001000  sp 40307d30  lr 80b00b49  pc 80b00944  cpsr a0000010
12-12 10:14:31.668: INFO/DEBUG(2361):  d0  643a64696f72646e  d1  6472656767756265
12-12 10:14:31.668: INFO/DEBUG(2361):  d2  000000010000ac75  d3  0000000000000074
12-12 10:14:31.668: INFO/DEBUG(2361):  d4  0000000000000000  d5  0000000000000000
12-12 10:14:31.668: INFO/DEBUG(2361):  d6  0000000000000000  d7  000007253ee4b3b6
12-12 10:14:31.680: INFO/DEBUG(2361):  d8  0000000000000000  d9  0000000000000000
12-12 10:14:31.680: INFO/DEBUG(2361):  d10 0000000000000000  d11 0000000000000000
12-12 10:14:31.680: INFO/DEBUG(2361):  d12 0000000000000000  d13 0000000000000000
12-12 10:14:31.680: INFO/DEBUG(2361):  d14 0000000000000000  d15 0000000000000000
12-12 10:14:31.680: INFO/DEBUG(2361):  d16 3fd999999999999a  d17 4010000000000000
12-12 10:14:31.680: INFO/DEBUG(2361):  d18 3fe0000000000000  d19 3fe0000001312d00
12-12 10:14:31.696: INFO/DEBUG(2361):  d20 3f1153cbde08ad39  d21 bebbb90e9e9bc9e2
12-12 10:14:31.696: INFO/DEBUG(2361):  d22 3ff0000000000000  d23 3feb70bba144e0a7
12-12 10:14:31.696: INFO/DEBUG(2361):  d24 3e66376972bea4d0  d25 0000000000000000
12-12 10:14:31.696: INFO/DEBUG(2361):  d26 0000000000000000  d27 0000000000000000
12-12 10:14:31.696: INFO/DEBUG(2361):  d28 0000000000000000  d29 0000000000000000
12-12 10:14:31.696: INFO/DEBUG(2361):  d30 0000000000000000  d31 0000000000000000
12-12 10:14:31.700: INFO/DEBUG(2361):  scr 80000010
12-12 10:14:31.938: WARN/AudioTrack(2367): obtainBuffer timed out (is the CPU pegged?) 0x77df8 user=00002800, server=00000800 cblk->bufferTimeoutMs(1000) cblk->waitTimeMs(1000)
12-12 10:14:32.114: INFO/DEBUG(2361):          #00  pc 00000944  /system/lib/libsamsungAcousticeq.so
12-12 10:14:32.114: INFO/DEBUG(2361):          #01  lr 80b00b49  /system/lib/libsamsungAcousticeq.so
12-12 10:14:32.114: INFO/DEBUG(2361): code around pc:
12-12 10:14:32.114: INFO/DEBUG(2361): 80b00924 6d84f5ad 49644607 200cf854 4863b083 
12-12 10:14:32.114: INFO/DEBUG(2361): 80b00934 68131861 f8cd1820 f7ff3424 9006efc8 
12-12 10:14:32.114: INFO/DEBUG(2361): 80b00944 f0402800 4b5e808f 495e3006 186118e2 
12-12 10:14:32.114: INFO/DEBUG(2361): 80b00954 efaaf7ff 30fff04f f10de09b 46280e20 
12-12 10:14:32.114: INFO/DEBUG(2361): 80b00964 99054672 e00cf8cd ef86f7ff 78029b03 
12-12 10:14:32.114: INFO/DEBUG(2361): code around lr:
12-12 10:14:32.114: INFO/DEBUG(2361): 80b00b28 bf0068c3 1964a500 4605460e eb02b1f3 
12-12 10:14:32.114: INFO/DEBUG(2361): 80b00b38 105072d2 eecef7ff 46304631 eedcf7ff 
12-12 10:14:32.114: INFO/DEBUG(2361): 80b00b48 c030f8df 0000f9b5 1004f9b5 c00cf854 
12-12 10:14:32.114: INFO/DEBUG(2361): 80b00b58 2008f9b5 f8cd4b08 f8dfc000 58e3c020 
12-12 10:14:32.114: INFO/DEBUG(2361): 80b00b68 c00cf854 c004f8cd ee7ef7ff bd7c2000 
12-12 10:14:32.114: INFO/DEBUG(2361): stack:
12-12 10:14:32.114: INFO/DEBUG(2361):     40307cf0  a979bfe8  /system/lib/libaudio.so
12-12 10:14:32.114: INFO/DEBUG(2361):     40307cf4  00000001  
12-12 10:14:32.114: INFO/DEBUG(2361):     40307cf8  00007fff  
12-12 10:14:32.114: INFO/DEBUG(2361):     40307cfc  80a019e4  /system/lib/lib_Samsung_Sound_Booster.so
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d00  0000004a  
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d04  80a07ba8  
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d08  00007fff  
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d0c  00000001  
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d10  80a030c8  /system/lib/lib_Samsung_Sound_Booster.so
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d14  80a010d8  /system/lib/lib_Samsung_Sound_Booster.so
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d18  00001000  
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d1c  0002b690  [heap]
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d20  00027058  [heap]
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d24  00029588  [heap]
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d28  df002777  
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d2c  e3a070ad  
12-12 10:14:32.114: INFO/DEBUG(2361): #00 40307d30  00027070  [heap]
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d34  00029588  [heap]
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d38  00026d48  [heap]
12-12 10:14:32.114: INFO/DEBUG(2361):     40307d3c  00029588  [heap]
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d40  00002000  
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d44  a9723178  /system/lib/libaudio.so
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d48  00026d48  [heap]
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d4c  00000000  
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d50  40307e0c  
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d54  a9724898  /system/lib/libaudio.so
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d58  00000000  
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d5c  00027b70  [heap]
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d60  00000000  
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d64  40307e0c  
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d68  00027b94  [heap]
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d6c  a8d365d8  /system/lib/libaudioflinger.so
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d70  0000b3b0  [heap]
12-12 10:14:32.118: INFO/DEBUG(2361):     40307d74  a979ae50  /system/lib/libaudio.so
12-12 10:14:32.940: WARN/AudioTrack(2367): obtainBuffer timed out (is the CPU pegged?) 0x77df8 user=00002800, server=00000800 cblk->bufferTimeoutMs(1000) cblk->waitTimeMs(1000)
12-12 10:14:33.107: INFO/Process(5912): Sending signal. PID: 5912 SIG: 9
12-12 10:14:33.114: INFO/ActivityManager(2472): Process com.jonasl.gmailnotifier2 (pid 5912) has died.
12-12 10:14:33.940: WARN/AudioTrack(2367): obtainBuffer timed out (is the CPU pegged?) 0x77df8 user=00002800, server=00000800 cblk->bufferTimeoutMs(1000) cblk->waitTimeMs(1000)
12-12 10:14:34.157: INFO/DEBUG(2361): dumpmesg > /data/log/dumpstate_app_native.log
12-12 10:14:35.868: INFO/BootReceiver(2472): Copying /data/tombstones/tombstone_09 to DropBox (SYSTEM_TOMBSTONE)
12-12 10:14:35.914: INFO/dumpstate(5923): begin
12-12 10:14:35.950: INFO/dalvikvm(2472): threadid=3: reacting to signal 3
12-12 10:14:36.079: DEBUG/dalvikvm(2472): JIT code cache reset in 4 ms (1048544 bytes 5/0)
12-12 10:14:36.079: DEBUG/dalvikvm(2472): GC_FOR_MALLOC freed 6471 objects / 344992 bytes in 197ms
12-12 10:14:36.079: INFO/dalvikvm-heap(2472): Grow heap (frag case) to 9.012MB for 32806-byte allocation
12-12 10:14:36.150: INFO/dalvikvm(2564): threadid=3: reacting to signal 3
12-12 10:14:36.351: INFO/dalvikvm(2566): threadid=3: reacting to signal 3
12-12 10:14:36.552: INFO/dalvikvm(2571): threadid=3: reacting to signal 3
12-12 10:14:36.753: INFO/dalvikvm(2574): threadid=3: reacting to signal 3
12-12 10:14:36.942: INFO/dalvikvm(2574): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:36.969: INFO/dalvikvm(2578): threadid=3: reacting to signal 3
12-12 10:14:36.981: INFO/dalvikvm(2564): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:36.996: INFO/dalvikvm(2566): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:37.067: INFO/dalvikvm(2571): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:37.086: INFO/dalvikvm(2472): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:37.086: INFO/dalvikvm(2578): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:37.172: INFO/dalvikvm(2697): threadid=3: reacting to signal 3
12-12 10:14:37.188: DEBUG/dalvikvm(2472): GC_FOR_MALLOC freed 252 objects / 75528 bytes in 103ms
12-12 10:14:37.254: DEBUG/dalvikvm(2472): GC_FOR_MALLOC freed 188 objects / 8944 bytes in 65ms
12-12 10:14:37.254: INFO/dalvikvm-heap(2472): Grow heap (frag case) to 9.057MB for 131176-byte allocation
12-12 10:14:37.325: DEBUG/dalvikvm(2472): GC_FOR_MALLOC freed 2 objects / 80 bytes in 71ms
12-12 10:14:37.376: INFO/dalvikvm(2775): threadid=3: reacting to signal 3
12-12 10:14:37.551: DEBUG/dalvikvm(2472): GC_FOR_MALLOC freed 2485 objects / 294672 bytes in 109ms
12-12 10:14:37.575: INFO/dalvikvm(2846): threadid=3: reacting to signal 3
12-12 10:14:37.625: DEBUG/dalvikvm(2472): GC_FOR_MALLOC freed 17 objects / 1072 bytes in 73ms
12-12 10:14:37.625: INFO/dalvikvm-heap(2472): Grow heap (frag case) to 8.715MB for 49461-byte allocation
12-12 10:14:37.696: DEBUG/dalvikvm(2472): GC_FOR_MALLOC freed 5 objects / 296 bytes in 69ms
12-12 10:14:37.750: INFO/dalvikvm(3091): threadid=3: reacting to signal 3
12-12 10:14:37.754: INFO/dalvikvm(2846): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:37.952: INFO/dalvikvm(3098): threadid=3: reacting to signal 3
12-12 10:14:38.152: INFO/dalvikvm(3292): threadid=3: reacting to signal 3
12-12 10:14:38.254: INFO/dalvikvm(2775): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:38.258: ERROR/dalvikvm(3091): Failed to write stack traces to /data/anr/traces.txt (2153 of 3413): Interrupted system call
12-12 10:14:38.274: ERROR/dalvikvm(3098): Failed to write stack traces to /data/anr/traces.txt (-1 of 6129): Math result not representable
12-12 10:14:38.286: INFO/dalvikvm(3292): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:38.353: INFO/dalvikvm(3514): threadid=3: reacting to signal 3
12-12 10:14:38.356: INFO/dalvikvm(3514): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:38.555: INFO/dalvikvm(3523): threadid=3: reacting to signal 3
12-12 10:14:38.571: INFO/dalvikvm(3523): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:38.758: INFO/dalvikvm(3667): threadid=3: reacting to signal 3
12-12 10:14:38.770: INFO/dalvikvm(3667): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:38.959: INFO/dalvikvm(4442): threadid=3: reacting to signal 3
12-12 10:14:39.161: INFO/dalvikvm(4926): threadid=3: reacting to signal 3
12-12 10:14:39.362: INFO/dalvikvm(5210): threadid=3: reacting to signal 3
12-12 10:14:39.563: INFO/dalvikvm(5255): threadid=3: reacting to signal 3
12-12 10:14:39.766: INFO/dalvikvm(5261): threadid=3: reacting to signal 3
12-12 10:14:39.946: INFO/dalvikvm(5290): threadid=3: reacting to signal 3
12-12 10:14:40.145: INFO/dalvikvm(5322): threadid=3: reacting to signal 3
12-12 10:14:40.164: INFO/dalvikvm(5210): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:40.348: INFO/dalvikvm(5406): threadid=3: reacting to signal 3
12-12 10:14:40.403: INFO/dalvikvm(4442): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:40.418: INFO/dalvikvm(5792): threadid=3: reacting to signal 3
12-12 10:14:40.735: ERROR/dalvikvm(5255): Failed to write stack traces to /data/anr/traces.txt (2610 of 3112): Unknown error: 0
12-12 10:14:40.770: INFO/dalvikvm(5261): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:40.813: ERROR/dalvikvm(5290): Failed to write stack traces to /data/anr/traces.txt (1805 of 2797): Unknown error: 0
12-12 10:14:40.832: ERROR/dalvikvm(5322): Failed to write stack traces to /data/anr/traces.txt (-1 of 3407): Math result not representable
12-12 10:14:40.895: ERROR/dalvikvm(5792): Failed to write stack traces to /data/anr/traces.txt (-1 of 2305): Math result not representable
12-12 10:14:40.911: INFO/dalvikvm(4926): Wrote stack traces to '/data/anr/traces.txt'
12-12 10:14:40.915: ERROR/dalvikvm(5406): Failed to write stack traces to /data/anr/traces.txt (11679 of 12076): Unknown error: 0
12-12 10:14:41.188: INFO/dalvikvm(2697): Wrote stack traces to '/data/anr/traces.txt'

In this example I received a new email and playing the notification sound caused the crash. You'll notice that this was a SIGILL (not sigKill). Playing a sound immediately afterwards worked fine, and it worked 5 minutes before this crash when I received a previous email.

A SIGILL usually happens due to stack corruption or file system corruption. I've checked the filesystem (being rooted with fsck) and it's fine. Other times it's crashed it's been a SIGBUS, which means that there was a bus error.

So, this looks horribly like it's a hardware problem... but... here's the kicker. My partner's phone (not rooted) is doing exactly the same thing, although less frequently, an a neighbour asked me about this exact same issue as he knew I have the same phone as him. All Samsung Galaxy S, all running the UK stock FroYo, all crashing at a kernel level (SIGBUS, SIGILL) rather than an Android level (i.e. force closes).

My guess is it's a bug in this version of the ROM.

I don't want to install any custom ROM to fix this, or factory reset (which I doubt would fix it), I was more putting it out there in case anyone else has the same issues.

[Bade]

I get this many, many times a day and I know what causes it (at least for me).
It's a mix of Google and Samsung. The Android term for it is ANR, application not responding and Android will force close, or a device reset if an app becomes unresponsive for 5 seconds, or a BroadcaseReciever within 10. Single threaded apps are particularly vulnerable to this.
The culprit is the Email app as I live in Taiwan but my email servers are in the UK and USA. The latency is frequently over 10 seconds and often over 5. If I disable Email completely the device behaves normally, except when I have an intermittent internet connection.
My bedroom is at the fringe of my WiFi coverage, and I live in a poor cellular area. Frequently IP packets are dropped, and I expect the TCP receive buffers overflow. Android does not handle intermittent connections gracefully and will cause any connected app to experience ANR.
So to "fix" this issue Google needs to write a decent IP stack, and Samsung needs to write a better Email client. (also Samsung needs to urgently improve their 802.11g and 802.11n support. I can flatten a fully battery trying to connect to WiFi in Hong Kong airport, and if it magically connects then the latency is so poor that everything ANR's and the phone constantly reboots)

[extorian]

Thanks for the reply. Usually when I get an ANR the phone pops up a message asking if I want to Wait or Force Close. I don't get this with this type of crash. I just get a long pause on the phone where it's unresponsive for several seconds, then a vibrate pulse, then the screen goes black (apart from the notification bar), then another long pause while the phone is unresponsive, and then the 3 pulses. There is something that I can sometimes see very briefly popping up when it returns to the Home screen, but it flashes off so quickly I don't have time to see it.

I don't use the email client on my phone, but I do use GMail, which is generally very fast. However, I know one time it crashed in the middle of the night while I was asleep (the vibrate pulses woke me up) happened to be at exactly the same time I received a GMail.

Another interesting thing is that this hasn't happened to me for several days now, but I have had updates to several apps (Gmail, Youtube, Layar, Tasker, Google Maps, Google Earth), which may be related.

Isn't the TCP stack part of the underlying Linux OS on the phone? I wouldn't have thought they'd have re-wrote that - the Linux TCP stack has been solid, reliable, and compact, for years - there's no need to change it. I genuinely don't know if it is or isn't... but I'd be surprised if it was changed for Android. Having said that, it could just as easily by the way it's accessed/used by Android at an API level.

I have very good WiFi in my house. I've checked the access point logs and there have been zero dropped packets since it last restarted (weeks ago).

However, I think we're on the right lines. Everything that has crashed on my phone has been related to network access in some way (but then isn't nearly everything on a Android phone?)... Sound subsystem crashing after a GMail was received, Browser crashing...

[Bade]

I get both, but with the JPE Froyo build I now get more windows with the option to close or wait.

The TP stack is part of the OS, but there are things that you can do to improve performance for what is called long-thin networks. There is actually a RFC for it RFC 2757. Suffice it to say that the standard Linux IP stack can do with a lot of optimisation for mobile clients. Increasing the buffers is something Samsung could do if they wanted, and configuring window size and scaling. Windows Mobile was good in that you could (as a end user) set these. I haven't dug into user level settings on Android.

There are (I think) two calls you can make to the IP stack too. The Java calls or the native. Java sucks completely and is unusable. I cannot do simple ping using Java calls across my home wireless network. The Android implementation of Java's stack. Pinger form the Market is a good example of this where you can choose which method you can use to ping. For some apps I actually need to start Pinger and ping my home server before the 3rd party app would actually conect! Google telling developers to use the Java IP calls for ping, dnslookup and other "standard" calls also points to the issue being in Google's court rather than Samsungs.

I hope someone at Google monitors these forums still.

[extorian]

I'm on the JPO build of FroYo (UK official one). I used to get ANR popups a lot more frequently on Éclair. Maybe the speed increases with FroYo now pushes those below the 5 second rule Android has.

[eric0023]

Hello there! I'm having the almost exact same issue. I updated to FROYO about a week ago and just today I experienced the VIBRATE pause...VIBE VIBE. Mine only happens when opening ebay via my browser. I could get on the website just a few days ago but, not any longer. I dont get a black screen however, just a straight jump to my home screen. Also I live in California USA so I have the US update, naturally. This is my first Android phone and I love it but, I'm starting to get a lot more FC's on apps that never FC'd on the ECLAIR OS. I hope they can fix this issue. Oh wow I just noticed the date on these posts....lol

[extorian]

When 2.2 was updated to 2.2.1 in December here in the UK, this fixed 99% of this vibrate crashing issue. I use my phone all the time and I experience this maybe once per month now.

[kodel]

I just registered on this forum to let you guys and google know that the just released (May 2011) Samsung Galaxy Gio is facing a similar issue.

I've written an extensive analysis of the problem (as far as my limited knowledge allows) on my blog: http://bit.ly/lU2fUX

Let's hope for a quick firmware update, since the device is really unusable like this.

[techtrip]

I second this issue on a Samsung Gio.

The recent firmware 2.2.1. seems to have the hang issue while in standby / sleep mode as well.

It's not getting extremely irritating!

[capellipro]

This happens to me at least once a day. Happened 5 times on saturday! I am sick of it. I am missing client calls and texts, i am losong business and I can't get t-mobile to do anything about it. I need a new phone. Only had the samsung for 4 months. Somebody please please fix this!!!!