Navigation sounds through earpiece only

Discussion in 'Android Devices' started by ImBatman, Nov 7, 2009.

  1. ImBatman

    ImBatman Member
    5

    Nov 7, 2009
    5
    0
    5
    When using Car Home mode - whether in the dash mount cradle or not - all navigation directions are coming through the earpiece speaker (above the word "Motorola" on the front) instead of the louder speaker-phone speaker (on the back). Totally useless.

    I have Bluetooth turned off, so that shouldn't be the problem. Turning up the volume only increases the earpiece volume, it doesn't activate the other speaker. Anyone know how to fix this? Thanks.
     

    Advertisement

  2. Chadster

    Chadster New Member
    5

    Nov 7, 2009
    3
    0
    5
    BUMP - I have the same problem!!! Very frustrating... I've tried every setting I can think of but I'm missing something
     
  3. ImBatman

    ImBatman Member
    5

    Nov 7, 2009
    5
    0
    5
    Me too. I'm thinking it's a bug. Strange that it would only affect a limited number of units though.
     
  4. kmfdmk

    kmfdmk Well-Known Member
    38

    Nov 7, 2009
    82
    16
    38
    Bomb Technician / Computer Nerd
    Vancouver, WA / Louisville, KY
    Soft resetting (Turning off phone and turning phone back on) seemed to fix the problem for me. Can't believe I didn't think to do the old "Reboot" trick. Worked for me for now. I was also having the same problem on audio playback as well.
     
  5. darrinaltman

    darrinaltman Well-Known Member
    36

    Oct 11, 2009
    139
    3
    36
    Lot of people are reporting this. I'm sure it will be fixed in an update.
     
  6. derrickonline

    derrickonline Member
    16

    Nov 3, 2009
    19
    2
    16
    Same problem, but mine wasn't navigation it was notification tones. I suspect that when you were having only navigation sounds coming through your notification sounds were only coming out of the headset or earpiece only as well.

    I was wondering why I wasn't hearing my alerts for text or emails. A reboot fixed it. Hope this doesn't happen often.
     

Share This Page

Loading...