Closed GoogleCodeExporter closed 9 years ago
Is that possible for you to produce some logs both with -23 and -25? (see wiki
HowToCollectLogs to do so)
I'm not able to reproduce with my accounts so your logs can help me a lot.
Original comment by r3gis...@gmail.com
on 30 Aug 2010 at 8:58
More detail: this issue occurs when the Legend is asleep but not when awake.
Does not occur with -23, but tested with -26 and still occurs. Behavior is, put
phone to sleep, dial the Legend's extension, SIP client does not wake up the
phone. Hang up the call, phone rings but does not wake up. Continues to ring
until I power of the phone. I sent you logs for -23 and -26 just now.
Original comment by phil.med...@gmail.com
on 31 Aug 2010 at 3:29
Resent logs for -26 per your request. Also, yes, killing the app does terminate
the ring tone. Don't know why I didn't think of that.
Original comment by phil.med...@gmail.com
on 31 Aug 2010 at 4:37
Similar thing happened to me with -25 on Desire. The phone started ringing but
did not wake up the screen; when I pressed power button there was home screen
and no interesting notifications in the notification bar. When I "Force stop"
the app from app management menu the sound stopped.
On other instances, the phone started to vibrate but did not produce sound on
incoming call, and the screen was black. When I pressed power button ringtone
began to play and there was an "incoming call" screen and I was able to answer
the call. Happened a few times.
Most of the time it works right. And it did not yet happen since I installed
-26.
Original comment by egcros...@gmail.com
on 2 Sep 2010 at 2:09
Forgot to close the issue, this issue was fixed in 12-27.
However, I keep in mind the issue with the fact it doesn't wake up the phone
everytime. Still trying to debug it. Some improvements have been done in -12-30
that ~could~ impact wake up. (However, it is not fixes for the issue but as
things are more clean worth to retry).
After installing -12-30, it is a good idea to reboot the phone (previously
there where a leak in wifi lock - and to be sure to release it a reboot is a
good idea)
Original comment by r3gis...@gmail.com
on 10 Sep 2010 at 9:27
Original issue reported on code.google.com by
phil.med...@gmail.com
on 30 Aug 2010 at 8:29