On Thu, Feb 12, 2009 at 5:21 PM, clark <clarkd...@gmail.com> wrote:
>
> I am finding it very hard to believe and empathise or believe you.
Fair enough. Never asked for any of these.
> First, you mention that T-Mobile "could care less," but failed to
> mention the fact that you are not a T-Mobile customer.
True. Even if I was a T-Mobile customer I very much doubt they could
care less because the 1.1 update is the same received by all users. If
there isn't a critical mass of them saying "the update screwed my
phone" I'm pretty sure I'd get anything from T-Mobile but "sorry to
hear that".
> In another
> post you mention that you are not only a user, but a developer,
> however, in a later post you mention "If I WAS an Android developer."
Make the difference, I'm a developer FOR Android, I'm not an Android
developer, meaning I don't develop the Android stack itself.
> The way I read your first post was as if you WERE an Android
> developer. Reading into that was probably my own fault, but it does
> seem like you are being a bit misleading.
I'm Bulgarian, English is not my native language, sorry if I have been
misleading.
>
> Is it possible that there are other details you have not revealed?
>
> You also seem to be describing all sorts of issues, some that sound
> like the phone causing you problems
If by "the phone causing you problems" you mean the dial and hang up
buttons not working - it's not the case. They worked *perfectly* well
before the minute I did the update.
> and another that sounds like you
> are using Eclipse to do some development and that when running an app
> from there, the Device Picker lists the phone several times.
True, these are 2 separate issues, which I put on 1 rant post.
> If you
> are experiencing issues on a particular computer, try out another (if
> that is possible) and report those findings.
I'm experiencing the issues with the device (buttons locking and the
unreasonable GCs), the only computer problem I have (had) was that
Eclipse did connect to the device *once* *after* the update, and then
it wouldn't, listing instead a dozen of bogus devices (all off-line) +
1 online to which it couldn't connect.
> Even though you "really don't want to know what's going on with [your]
> phone," I will suggest trying to connect to the phone with ADB and
> perform a Logcat and see if there are any hints as to what could be
> the issue.
I did (after I upgraded to 1.1) and I can't see anything that's
useful. Here's a logcat dump from 1 minute ago:
02-12 17:35:31.500: INFO/ActivityManager(60): Starting activity:
Intent { action=android.intent.action.MAIN flags=0x10800000
comp={com.android.phone/com.android.phone.InCallScreen} }
02-12 17:35:31.540: DEBUG/dalvikvm(95): threadid=25 wakeup: interrupted
02-12 17:35:31.630: INFO/AudioHardwareMSM72XX(32): Routing audio to Speakerphone
02-12 17:35:31.630: DEBUG/HTC_Acoustic(32): msm72xx_enable_audpp: 0x0001
02-12 17:35:32.320: DEBUG/dalvikvm(92): GC freed 5354 objects / 327600
bytes in 150ms
02-12 17:35:32.400: INFO/BluetoothHeadset(92): Proxy object is now
connected to Bluetooth Headset Service
02-12 17:35:32.560: INFO/ActivityManager(60): Displayed activity
com.android.phone/.InCallScreen: 1056 ms
02-12 17:35:35.340: INFO/phone(92): acceptCall: incoming...
^^^^
02-12 17:35:35.361: INFO/AudioHardwareMSM72XX(32): Routing audio to Handset
02-12 17:35:35.361: DEBUG/HTC_Acoustic(32): msm72xx_enable_audpp: 0x0000
02-12 17:35:37.650: DEBUG/dalvikvm(119): GC freed 110 objects / 5096
bytes in 87ms
02-12 17:35:39.110: INFO/phone(92): acceptCall: incoming...
^^^^
02-12 17:35:41.490: INFO/phone(92): acceptCall: incoming...
^^^^
02-12 17:35:42.640: DEBUG/dalvikvm(133): GC freed 105 objects / 5024
bytes in 76ms
02-12 17:35:46.860: WARN/PHONE/CallCard(92): CallCard updateState:
overall Phone state is IDLE
02-12 17:35:47.730: WARN/ActivityManager(60): Duplicate finish request
for HistoryRecord{431fe778
{com.android.phone/com.android.phone.InCallScreen}}
02-12 17:35:48.910: INFO/AudioHardwareMSM72XX(32): Routing audio to Speakerphone
02-12 17:35:48.920: DEBUG/HTC_Acoustic(32): msm72xx_enable_audpp: 0x0001
02-12 17:35:52.022: DEBUG/AudioHardwareMSM72XX(32): Going to standby
02-12 17:35:53.920: DEBUG/dalvikvm(131): GC freed 24 objects / 856 bytes in 82ms
You can see the rings pointed with ^^^. 1st ring is at 17:35:35, I
press the dial button - nothing.
Then after the 3rd ring at 17:35:41.490 (6 seconds after!) the call started.
I don't understand the warnings in the log either.
>
> Perhaps after you are done venting and have had a chance to calm down
> a bit you will be willing to work with the developers and others to
> perhaps isolate the problem. Although this is the first time I've
> heard of this issue with RC33, it may be possible that there is
> another user or two experiencing the same symptoms. Help the
> community out and the community will help you. It's give and take.
>
I did, and am calm. I'd help anyone diagnose this problem, and I'm
willing to put whatever extra time is needed to help anyone fix the GC
from hell bug (illustrated below):
02-12 17:37:05.370: DEBUG/dalvikvm(119): GC freed 110 objects / 5096
bytes in 74ms
02-12 17:37:19.220: DEBUG/dalvikvm(119): GC freed 110 objects / 5112
bytes in 74ms
02-12 17:37:36.270: DEBUG/dalvikvm(119): GC freed 110 objects / 5096
bytes in 73ms
02-12 17:37:53.330: DEBUG/dalvikvm(119): GC freed 110 objects / 5112
bytes in 72ms
02-12 17:38:10.420: DEBUG/dalvikvm(119): GC freed 110 objects / 5096
bytes in 73ms
02-12 17:38:34.310: DEBUG/dalvikvm(119): GC freed 110 objects / 5112
bytes in 73ms
02-12 17:38:44.520: DEBUG/dalvikvm(119): GC freed 110 objects / 5096
bytes in 74ms
02-12 17:39:05.160: DEBUG/dalvikvm(119): GC freed 110 objects / 5112
bytes in 74ms
02-12 17:39:18.650: DEBUG/dalvikvm(119): GC freed 110 objects / 5096
bytes in 74ms
02-12 17:39:35.720: DEBUG/dalvikvm(119): GC freed 110 objects / 5112
bytes in 73ms
02-12 17:39:52.760: DEBUG/dalvikvm(119): GC freed 110 objects / 5096
bytes in 74ms
02-12 17:40:09.800: DEBUG/dalvikvm(119): GC freed 110 objects / 5112
bytes in 72ms
02-12 17:40:26.870: DEBUG/dalvikvm(119): GC freed 110 objects / 5096
bytes in 73ms
02-12 17:40:43.920: DEBUG/dalvikvm(119): GC freed 110 objects / 5112
bytes in 73ms
^^^ these are while the phone is completely idle.
Cheers,
Stoyan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
