Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.comp.os.windows-10    |    Steaming pile of horseshit Windows 10    |    197,590 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 196,796 of 197,590    |
|    Graham J to Paul    |
|    Re: OT: Alexa can't answer incoming call    |
|    15 Jan 26 08:39:11    |
      From: nobody@nowhere.co.uk              Paul wrote:       > On Wed, 1/14/2026 10:39 AM, Graham J wrote:       >> Graham J wrote:       >>> Graham J wrote:       >>>> This on behalf of a disabled neighbour.       >>>>       >>>> So: "Alexa, call Graham" - this works, so Alexa is correctly set up.       >>>>       >>>> But when there is an incoming call: "Alexa, answer the phone" gives a       message of the form "Can't answer incoming calls".       >>>       >>> OP here.       >>>       >>> The actual message is "There is no incoming call."       >>>       >>> Alexa is clearly lying, since the phone is ringing.              [snip]              > It's a hodge podge of bodgery for sure.              Thanks Paul for your investigation. I will print out the CoPilot       suggestions and take them with me next time I visit.              I note       " The Samsung A16 is a newer budget model, and some carriers disable        **Bluetooth HFP call control** for third‑party devices. In that case:"              The carrier is Tesco. Here in the UK Tesco is a large budget       supermarket and it would not surprise me that **Bluetooth HFP call       control** is disabled.              --       Graham J              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca