Sean Hodges wrote:
> On Thu, May 14, 2009 at 6:32 PM, PeeDee <[email protected]> wrote:
>
>> I've had a number of calls over the last few days where the caller
>> couldn't hear me. Different callers on different days. Some calls are
>> ok. This has only happened since the update to 1.5.
>>
>
> Hmm, the only suggestion I have right now is that you may have
> bluetooth enabled and another device is in close proximity, taking
> over the microphone...
>
>
I've never enabled bluetooth on the phone because I haven't needed it.
Saying that I've just checked the bluetooth settings on the phone to
make sure.
>> Another problem is
>> the battery life is even worse than before. My phone has very few
>> applications running and I haven't installed anything since the 1.5
>> update. I hardly use the phone so its in standby mode most of the time
>> so wifi is disabled.
>>
>
> Try power-cycling the phones battery a few times. There are some known
> issues surrounding the battery power indicators, although they are not
> specific to 1.5. I have been told that 1.5 should provide better power
> saving than 1.1, but my personal experience has found the difference
> marginal.
>
>
I'm in the process and am a week in. Maybe these batteries do sufferer
from the avalanche effect.
>> Also, since the 1.5 update the led doesn't flash
>> when I get a text message, voice mail etc. I've looked at the settings
>> but can't see where this would be enabled just in case this was made a
>> configurable option.
>>
>
> It's possible that you've installed an alternative Messaging app that
> has taken over the message received notification... Not too sure.
>
>
I've done a wipe, rebooted etc. Since then I get the notifications.
Did notice now though that I get two audible notifications if I send a
message to myself. Not really bothered about that though as long as its
working :-)
>> Anybody else having these problems?
>>
>
> I'm not experiencing any of the above, have you reported these issues
> in the bug tracker? http://code.google.com/p/android/issues
>
>
Rather not overload the bug database until I have ruled out all
possibilities of human error :-) ( ie me )
I'm going to see how frequent the problem is because who knows maybe it
was a t-mobile problem in my area. I tend to think if its not happening
to most people then it must be local to me hence the reason why I asked
the question. If it happens too often I'll grab a log and see if
anything jumps out. Like all things new its easy to jump to the wrong
conclusion and blame it on an update which I'm trying not to do. There
are other factors so I'll see what gives over the next few weeks.
> >
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Android Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
