11-13-2019 07:19 AM
11-13-2019 08:40 PM
LP_ASUSI just tried a factory reset as you suggested and it works exactly the same (meaning incorrectly as above). Needs a fix.I'm thinking that a factory reset is your best option. If you have a spare phone around, try using Swift. https://play.google.com/store/apps/details?id=org.swiftapps.swiftbackup&hl=en_US
It does a wireless transfer between two devices on the same network, and is a quick way to save your call logs and all the painful stuff to reload after a reset.
Android 10 must have borked something with your devices, but we know it isn't software if all three of you were operating correctly before 10.
View post
11-14-2019 04:55 AM
11-14-2019 04:55 AM
11-14-2019 05:51 AM
YuntianThat's a much easier work around. So simply make a call then after the person answers toggle the speakerphone on then off again and it works? (Edit - yes it works and is much easier than the Bluetooth method)I have reported this bug in XDA and it affects .63 as well. The workaround is to turn on the speaker and turn off. You can do this with voicemail. Have to apply this workaround after rebooting.
View post
11-14-2019 06:13 AM
skylerwolfeThat's correct.https://zentalk.asus.com/en/discussion/comment/27731#Comment_27731
That's a much easier work around. So simply make a call then after the person answers toggle the speakerphone on then off again and it works? (Edit - yes it works and is much easier than the Bluetooth method)
View post