dial interface + incoming ui: accept call button is working, woadilaer opens the call-active interface but the call is not active (the dialing device continues ringing)

woa 18362 driver pack 1909 updated on 08-26-2019 950 xl SS

• Setting user-friendly name
• Selecting color for line

Notification is missing and UI not ready for accepting calls.

Only one minimized view must exist.

to replicate:

• open the app (note that call button is not enabled, greyed)
• call a number, do the call as usual, terminate the call
• you'll be back to the calling view, but now the calling button is active
• now if you for mistake press the call button (active) you will have the exception

hope to be useful and compliments for the great job

on lumia 950xl ss 1907 driver pack woa ver.18362.239

It prints two characters 0+ instead of one +

I cannot launch the WOA Dialer on x86 and x64 system. I can install through Powershell but when i click on the app, it just launch for a second and end abruptly

LumiaWOA.Dialer

Windows 10
18995 19041 18362
ARM64
WoADialer.exe hangs on Windows 10.  

PROCESS_NAME:  WoADialer.exe WATSON_BKT_EVENT:  AppHang   ERROR_CODE: (NTSTATUS) 0xcfffffff - EXCEPTION_CODE_STR:  cfffffff   STACK_TEXT:  0000009fb1bfea30 00007fff09c8a2e0 : 0000009fb1bfea40 00007fff09c8a234 0000009fb1bfeaa0 00007fff0ac1ecb0 : win32u!ZwUserMsgWaitForMultipleObjectsEx+0x4 0000009fb1bfea30 00007fff09c8a234 : 0000009fb1bfea40 00007fff09c8a234 0000009fb1bfeaa0 00007fff0ac1ecb0 : user32!RealMsgWaitForMultipleObjectsEx+0x20 0000009fb1bfea40 00007fff0ac1ecb0 : 0000009fb1bfeaa0 00007fff0ac1ecb0 0000021600e807f0 0000000000000004 : user32!MsgWaitForMultipleObjectsEx+0x64 0000009fb1bfea80 00007fff0ac1e418 : fffffffffffffffe 00007fff05a1d4b8 0000000000000000 0000000000000000 : combase!ModernSTAWaitContext::KernelWait+0x80 0000009fb1bfeb00 00007fff0ac1fd9c : 0000009fb1bfecd0 00007fff09c7f5d0 0000000000000001 0000000000000000 : combase!ModernSTAWaitContext::Wait+0x330 0000009fb1bfeea0 00007ffefe4f131c : 0000009fb1bfef80 00007ffefe4f131c 0000000000000000 0000000600001cff : combase!CoMsgWaitInProcessEvents+0xac 0000009fb1bfeef0 00007ffefe4f25e4 : 0000000000000001 00007ffefe5b74d8 0000000000000398 00000000000005e8 : Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessagesInternal+0xfc 0000009fb1bfefe0 00007fff05d87764 : 0000009fb1bff000 00007fff05d87764 0000021600e84478 00007ffefe4f25a0 : Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessages+0x44 0000009fb1bff000 00007fff05d95b28 : 0000009fb1bff060 00007fff05d95b28 0000021600e84478 fffffffffffffffe : twinapi_appcore!Event::WaitAndProcessEvents+0xcc 0000009fb1bff060 00007fff05da96e4 : 0000009fb1bff260 00007fff05da96e4 0000021600e9c530 0000000000000000 : twinapi_appcore!Windows::ApplicationModel::SuspendingOperation::WaitForAnyOutstandingDeferrals+0x58 0000009fb1bff0c0 00007fff05d882ac : 0000000000000000 00007fff09d233b8 0000000000000250 00007fff05a1d514 : twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::SuspendResume+0x244 0000009fb1bff2c0 00007ffefe4f02e8 : fffffffffffffffe 000002161c9274c0 00007fff09d23001 00007fff05f05c18 : twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::SuspendResumeHandler::Invoke+0x13c 0000009fb1bff470 00007ffefe4f1688 : 0000009fb1bff530 00007ffefe4f1688 00007fff05a1d470 00007fff0b1612b0 : Windows_UI!Windows::UI::Core::CDispatcher::ProcessInvokeItem+0x260 0000009fb1bff520 00007ffefe4f12dc : 00000000000002d4 0000021600e84440 0000009fb1bff660 00007ffefe4f12dc : Windows_UI!Windows::UI::Core::CDispatcher::ProcessMessage+0x238 0000009fb1bff5d0 00007ffefe4f25e4 : 0000009fb1bf0000 00007ffefe5b74d8 0000000000000398 00000000000002d4 : Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessagesInternal+0xbc 0000009fb1bff6c0 00007fff05d87764 : 0000009fb1bff6e0 00007fff05d87764 0000021600e84478 00007ffefe4f25a0 : Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessages+0x44 0000009fb1bff6e0 00007fff05d8e988 : 0000009fb1bff740 00007fff05d8e988 0000021600e84478 fffffffffffffffe : twinapi_appcore!Event::WaitAndProcessEvents+0xcc 0000009fb1bff740 00007fff05d8dcd4 : 0000009fb1bff7d0 00007fff05d8dcd4 0000021600e7a480 0000021600e723f0 : twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationViewAgileContainer::WaitForViewReady+0x60 0000009fb1bff790 00007fff09e82cd0 : 0000021600e7a480 0000021600e723f0 fffffffffffffffe 00007fff05f28e30 : twinapi_appcore!<lambda_643db08282a766b00cec20194396f531>::<lambda_invoker_cdecl>+0xb4 0000009fb1bff810 00007fff09bb4974 : 0000009fb1bff900 00007fff09bb4974 0000000000000000 0000000000000000 : SHCore!_WrapperThreadProc+0x1f0 0000009fb1bff900 00007fff0b1a96f4 : 0000009fb1bff940 00007fff0b1a96f4 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x34 0000009fb1bff940 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x44  
IMAGE_NAME:  twinapi.appcore.dll
OS_VERSION:  10.0.18363.1
OSPLATFORM_TYPE:  arm64
OSNAME:  Windows 10

When prefix from contact store doesn't match with prefix that obtained from operator.

Hello,
I have tried it in the release of 1909v2,1910 and 1910-release,but woadialer can't open,It stays on the first page(the blue) and can't go on.

My windows system is 18875pro and 18908home-China,I tried a lot,but defeat.

When woadialer stays on the first page,There was no answer to the system call,unless I don't touch woadialer at the begining and never open to use it.

My English isn't very well,I hope you can understand what I say.

Please pay attention and solve it,thanks a lot!
yours
Chinese fans

When attempting a call with locked SIM then WoA dialer silently ignores the call action. It is a good idea to either display an error message ("PIN required") or prompt the user with an input dialog to unlock their SIM.

Windows 10 ARM64 build 18908 using gus33000's NTARM64 1909 driver pack WoA deployer install.

Hello! Tried using the dialer. Works good to dial out. When I close the call, it doesn't end it. I let is sit for over a minute with no change in the status. I made sure WoaDialerHelper.exe is running and phonesvc is as well. Let me know what I can provide to help work it out. Thanks!

Hello everyone.
Is a binary release available for this?
I'd like to avoid building myself, because I'd have to install Visual Studio, which is huge, especially compared to this little app.

Thanks in advance for either.

I think, should be able to customize this behavior.
But, it is not excepted behavior, so it's bug.

on xl 18362, driver pack 1909 240819 (and previous), commit fccb7ee (and previous), during remote debug (VS 2019), on push call button, the call is placed but the debug stucks on this exception

on release it crashes on call button push
thanks for attention

i found this app can support making call by phones linked by "your phone" app. but the support is not perfect. if the app will make it perfect oneday?

dial interface: dialing a number (via dialpad) the call is placed but the close call button (get activated) doesn't close the call.

woa 18362 driver pack 1909 updated on 08-26-2019 950 xl SS

App seems to work fine, except hanging up a call hangs for about 30 to 45 seconds...

Also, one time on a call WoA kept notifying me that I had an incoming call.
But it was the same call I was already on.
That one was a little odd... But it only did that one time.
Not since.

When the message notification is not cleared, Incoming call can not display prompt.
If all message notifications are cleared, the call notification will be displayed.

In current Commit, as of 01/01/2020, On Lumia 950, Windows Build 1909, while on a call the On-Hold Icon overlays the speaker phone icon and you cannot click on the Speaker Phone.
I was able to fix this by editing the CallUIPage.xaml and changing the HorizontalAlignment attributes, since they were both set to "centered" and Grid.Column="2", I changed the SpeakerPhone to Left aligned and the OnHold to Right aligned and redistributed to my device and it works.
The changed lines are as follows:

<AppBarToggleButton x:Name="speakerOutputButton" Grid.Column="2" Label="Speaker" Width="100" HorizontalAlignment="Left" Style="{ThemeResource AppBarToggleButtonRevealStyle}" Height="56" Checked="SpeakerOutputButton_Checked" Unchecked="SpeakerOutputButton_Unchecked">


<AppBarToggleButton x:Name="abtb_Hold" Grid.Column="2" Label="Hold" Width="100" HorizontalAlignment="Right" Style="{ThemeResource AppBarToggleButtonRevealStyle}" Height="56" Unchecked="Abtb_Hold_Unchecked" Checked="Abtb_Hold_Checked">