Develop Bugs

wifi smartwatch 3

Hi everybody,
i just bought a smartwatch 3 and i just don't get how to activate the wifi, i searched everywhere but no information.. even to activate or desactivate nfc to save battery but i cant find th options..
if anybody can help...
thank you

WiFi is not enabled until Google releases a version of Android Wear that supports it.
The same for NFC, it's active but only limited functionality available right now.

nCoder said:
WiFi is not enabled until Google releases a version of Android Wear that supports it.
The same for NFC, it's active but only limited functionality available right now.
Click to expand...
Click to collapse
This is great news to hear! Can I ask for the source?

SOURCES
You see here WiFi Ready:
Play Store https://play.google.com/store/devices/details?id=sony_smartwatch_3_black
Sony Developers Product White Paper: http://dl-developer.sonymobile.com/documentation/whitepapers/SmartWatch3_SWR50_WP_1.pdf
Verizon, Technical Specs http://www.verizonwireless.com/accessories/sony-smartwatch-3/ also in "FEATURES" it states "Wi-Fi ready (these features to be activated after launch, timing to be announced per Google)"
...And I posted official test documents in this forum proving it has WiFi

and the wait is almost over!!!
Been a long time in the making but finally:
Wi-Fi support
With GPS and offline music support, you can already leave your phone at home, then go jogging and jamming like normal. Now Android Wear supports watches with built-in Wi-Fi. As long as your watch is connected to a Wi-Fi network, and your phone has a data connection (wherever it is), you’ll be able to get notifications, send messages, and use all your favorite apps. And if you really do forget your phone, you can always ask your watch where it is.
Source: http://officialandroid.blogspot.co.uk/2015/04/android-wear-wear-what-you-want-get.html

Is the wifi feature properly working? How will I know if the wifi feature is working? does this mean i can turn off bluetooth on my phone and have the smart watch still work?

The latest update to the Wear app now includes the Wi-fi functionality however, I could not get it to work. Has anybody else had any better luck

You still need to receive the Smartwatch upgrade (watch itself)

It should be out in the next couple of days or weeks. Just keep checking the Sony companion app.

Is there a Sony companion app for the SW3? I normally just check under settings on the watch itself.

dingbatt said:
Is there a Sony companion app for the SW3? I normally just check under settings on the watch itself.
Click to expand...
Click to collapse
yeah for windows though

when I first bought my SW3, I received a firmware upgrade notification. I was able to update it thru the watch itself connected to my phone,

nCoder said:
WiFi is not enabled until Google releases a version of Android Wear that supports it.
The same for NFC, it's active but only limited functionality available right now.
Click to expand...
Click to collapse
I didn't know there was any NFC functionality yet. What is currently usable for NFC?

I think the only thing NFC on the watch can do is open the app on your phone. Apart from that it's useless.

You can use NFC to pair headphones with your watch, I pair my sbh-80 headphones this way

Has anyone received the wifi update yet?

lambstone said:
Has anyone received the wifi update yet?
Click to expand...
Click to collapse
nope... it's theoretically due post Urbane release, but thats been and gone now... so we're waiting

rob_h said:
I think the only thing NFC on the watch can do is open the app on your phone. Apart from that it's useless.
Click to expand...
Click to collapse
Thanks. I just found on another thread that it also starts up the watch when it's off. I tested it and that works and is pretty cool that NFC works when the watch is off, though I have doubts there will be many possibilities of using NFC with the watch off.

NFC can be somewhat powered by the reading device, so I thought I'd give this a try to see if it was enough to wake the watch up and power on. I turned my watch off, and tapped it to the NFC location on my phone. The phone launched the Android Wear companion app. The watch and phone both vibrated, and the "Sony" logo appeared on the watch then disappeared without ever finishing booting. I tried leaving it on the phone, and it buzzed a few times trying to start.

rob_h said:
I think the only thing NFC on the watch can do is open the app on your phone. Apart from that it's useless.
Click to expand...
Click to collapse
ROB .. thats not true .. its not useless .. when implimented , it will be usable for bus fair, as credit card and lots of other features in the future.

Google Play Services kills call volume.

So I noticed about 2 months ago that I have absolutely no sound (voice in/out or ringing while call is being placed) when I make or receive calls using the Phone app. I have various VOIP apps that all work fine. All media plays fine. Headsets all work fine for watching movies and whatnot. No sound during calls.
I had a factory unlocked N7100 that I was told came from Spain originally (I'm in Toronto). I had flashed some other country (I think South Africa) because they got a newer version and my phone wasn't updating automatically. Never had any issues until I noticed this with the calls. I have no idea how long it's been like that as I have a second phone I use primarily for voice calls and this one I usually just use basically as a tablet or I use VOIP apps for calling.
Yesterday I tried to flash to DN4 2.1 but after numerous times it would never get past the Samsung logo so I went with a France 4.4.2 stock ROM. That one has since autoupdated. Everything is working great including data. I can place calls and the other line will ring but there is no audio in/out of my phone (other end can't hear me, I can't hear them). Although it's not a huge issue for me I'd like to fix it. I have previously messed around with hidden menus and possibly even tried to play modifying with the phone app (as various hidden menus stopped working after the last update and I was trying to get them back). But when I was trying to get DN4 to work I wiped EVERYTHING repeatedly so I don't think anything could be hanging around to mess stuff up.
I don't think it's a hardware issue otherwise why would it work fine for VOIP using the same mic and speaker? Also, it doesn't work through a headset either. No voice, no ringing, etc.
Currently my phone is showing the following:
Baseband:
N7100XXUFNG1
Kernel:
3.0.31-4587314
[email protected] #1
Tue Mar 31 14:58:35 KST 2015
Build:
KOT49H.N7100XXUFOC2
Suggestions?!?

No suggestions?

Found the answer here: http://forum.xda-developers.com/showpost.php?p=57436919&postcount=39
Settings
Apps
Scroll right to All
Scroll down to Google Play Services
Tap Disable
Repeat for Google Services Framework.
Click to expand...
Click to collapse
Instant call volume after I do this. But now my Google apps don't work. I need a better solution!
Edit: Nevermind, turned them back on and calls are still working. Hopefully it doesn't stop working the moment I need to make an emergency call or something.

Google app/Google search question about crashes

Hi all,
I know there are quite a few people with issues on the google app crashing and I thought it might be helpful to see if we could collate different people's experience here - what hardware (RK?), rom, version etc, in case there is a particular version that works.
I have a RK3066/stock rom configuration. In terms of the version I have tried:
So 3.3.12 didn't crash at all in my brief test . But can't voice dial, guess they changed how it works some point after that .
5.4.x can crash repeatedly, best case feels like every other time. It also does not pick up my navigate requests correctly.
4.9.22 crashes infrequently so far. Never repeatedly which is importantly , worst every other time,usual say every five attempts.
4.7.x similar to 4.9.22
4.5.x - crashed alot
4.1.x crashes every 2-3 attempts, but can voice dial with this version (and above).
There is a 5.12 beta I haven' tried.
APKs at http://www.apkmirror.com/apk/google-inc/google-search/
Finally, is there a way of logging the detail of a google app crash - to see if there is something specific causing it?
Cheers

Another option.. I played w/ it on my phone and it was pretty nice. It does rely on google voice search so who knows if it'll crash also.
http://www.xda-developers.com/how-to-get-voice-access-beta/

TT_Vert said:
Another option.. I played w/ it on my phone and it was pretty nice. It does rely on google voice search so who knows if it'll crash also.
http://www.xda-developers.com/how-to-get-voice-access-beta/
Click to expand...
Click to collapse
Minimum android version is lollipop

Well that sucks a big one. To be honest it started to annoy me today. Couldn't fund out how to quickly turn it off

I would prefer to dig into why it crashes rather them retry to replace it. We know Goggle Voice works well when it works we just need to keep it working.
Unfortunately I really don't know where to start with it. I wish I had a bench top unit so I didn't always need to be in my car.
Is anyone running a HU emulator?

hans109h said:
I would prefer to dig into why it crashes rather them retry to replace it. We know Goggle Voice works well when it works we just need to keep it working.
Unfortunately I really don't know where to start with it. I wish I had a bench top unit so I didn't always need to be in my car.
Is anyone running a HU emulator?
Click to expand...
Click to collapse
Yes I think this will get us furthest, if we can understand why it crashes, then maybe there is a work around. Is it to do with microphone readiness, data connection or some other launch/ROM issue????
Having a crash free google app voice search would turn this HU from good to virtually perfect for me!

Mr Bigglesworth said:
Yes I think this will get us furthest, if we can understand why it crashes, then maybe there is a work around. Is it to do with microphone readiness, data connection or some other launch/ROM issue????
Having a crash free google app voice search would turn this HU from good to virtually perfect for me!
Click to expand...
Click to collapse
On my device it crashed offer if radio was playing during while I initiated the search. But it crashed also when the radio was not playing.

p_mike83 said:
On my device it crashed offer if radio was playing during while I initiated the search. But it crashed also when the radio was not playing.
Click to expand...
Click to collapse
On my HU is crashing all the time. I'm using the latest ROM from Malay Master. I have tried different version(some are crashes often, some rarely), but until now I didn't find a solution/workaround to this problem.
Still investigating...

dj.martzian said:
On my HU is crashing all the time. I'm using the latest ROM from Malay Master. I have tried different version(some are crashes often, some rarely), but until now I didn't find a solution/workaround to this problem.
Still investigating...
Click to expand...
Click to collapse
So are you able to say which are more stable? And what hardware do you have?

Mr Bigglesworth said:
So are you able to say which are more stable? And what hardware do you have?
Click to expand...
Click to collapse
The most stable is version 4.9.22.19 from apkmirror.com
HU Technical Specs: RK3188, 1024x600
Here is the link with the product:
http://www.aliexpress.com/item/Quad...r-DVD-Player-For-FORD-MONDEO/32563024121.html
Best Regards,
D.

dj.martzian said:
The most stable is version 4.9.22.19 from apkmirror.com
HU Technical Specs: RK3188, 1024x600
Here is the link with the product:
http://www.aliexpress.com/item/Quad...r-DVD-Player-For-FORD-MONDEO/32563024121.html
Best Regards,
D.
Click to expand...
Click to collapse
Yes, I also thought that 4.9.22 is one of the most stable of those that I have tried and have proper functionality. I'm on RK3066 and stock ROM. Interesting that your RK3188 doesn't improve things markedly, I don't think it is a processing power issue.
I was thinking about this a little bit more, I remember trying 3.3.12 (or whatever is the stock one installed) and it was very stable, but can't voice dial on it; 4.1.x etc start to crash so I wonder if there is information out there about the main changes that happened between these versions and so what might be causing it. is it something that has greater dependency on a good wifi connection or something else or some kind of software module that's not meshing right with the HU?

I found this in an old thread http://forum.xda-developers.com/showpost.php?p=48854301&postcount=714
gpmg762 said:
Got Google Now working, sort of anyway. Here's how I did it.
install an old PrebulitGMSCore apk https://drive.google.com/file/d/0B2FRr4c4c1g8WVI2YWg3TFZ4MTg/edit?usp=sharing (Google Play Services).
install Velvet apk https://drive.google.com/file/d/0B2FRr4c4c1g8X2t2MzQ4MkMyd1U/edit?usp=sharing (Google Now).
this step probably not be needed as I was trying to install Google Home Launcher, install Google Home apk https://drive.google.com/file/d/0B2FRr4c4c1g8OU9odi1ZRzJ5cHM/edit?usp=sharing (Google Home Launcher).
launch Google Now, it will detect a new version, update it.
I can use Google Now to launch default Radio and Music app by "play music" and "play radio".
"play disc" not working for me, neither are "navigate home" and "navigate office", they just get normal search results.
Click to expand...
Click to collapse
Has anyone gone done the route of changing the PrebulitGMSCore apk but with a more functional Google Now etc?

I'm hesitant to dig into this until Malaysk's next update that will be out soon.

Hello all,
I made some good progress, although with one drawback.
Today I tried v3.6 (I think it was 3.6.16) from apkmirror. And tried it just under ten times with NO crashes. A record for my head unit!!
v3.6 does have calling functionality, and navigate works fine too.
The only drawback seems to be the play music function (I really only need these three functions as everything else I do is quite straightforward from steering wheel controls). It doesn't seem to bring up poweramp and play the music as later versions do....But maybe this is something can be resolved by settings, I need to investigate more when I am back in the car.
Please can others try this and contribute to the thread - I feel I am so close to having this up and running well!

I'm going to continue posting on this thread, although it does somewhat feel like I am talking to myself.
So in the car a couple more times today. Absolutely no crashes on this version of 3.6.16 (what did they change after that which made it no work so well on MTCB HU?). When online, call and navigation work brill, don't know why it refused to play ball on play music.
Messing around with some voice command apps, and still testing this, but this sorts out the play music, and play music and navigate commands work well when offline - but just cant seem to get call to recognise properly when offline - it would be the last missing link for me - think it might be something that can be customised to be fixed though - will update when I figure this last bit out!

I'll play with this soon also.
Dave

I'm swamped right now but I will try to test it later in the week.

Ok, that would be great - was in the car again this morning and seemed to work fine. If someone knows how to make this version work well with the play music command (i.e. find local music and load it in poweramp), that would be great!
The other reason why i went to 3.6 is that it offline voices is meant to work but it isn't. I am wondering if the gapps version needs to also be rolled back to an earlier version for offline voices to work.

Mr Bigglesworth said:
I'm going to continue posting on this thread, although it does somewhat feel like I am talking to myself.
Click to expand...
Click to collapse
Please continue to talk to yourself, i'm listening
I hope to give version 3.6.16 a try later today and I'll post my results here.
There are some things I need to figure out to make this HU (almost) perfect and a stable voice command/search certainly is one of them.

I loaded 3.6.16 today and so far no issues. Do you happen to have a chameleon or version history so we can try to bisect this?

Call recording apps?

On ye olde phone (Samsung) I used ACR to record calls. That worked great.
For the Pixel, not so much. I notice on the ACR support forum that they say that it won't work: https://bitbucket.org/copluk/acr/issues/870/google-pixel-xl
Anyone else found a different app or method that does work?

Hi, there's no way to record both sides without root on Pixel XL. But if you get root, call recording is possible: http://forum.xda-developers.com/showthread.php?p=69380102#post69380102

Automatic Calll Recorder Pro
ohmegosh said:
On ye olde phone (Samsung) I used ACR to record calls. That worked great.
For the Pixel, not so much. I notice on the ACR support forum that they say that it won't work: https://bitbucket.org/copluk/acr/issues/870/google-pixel-xl
Anyone else found a different app or method that does work?
Click to expand...
Click to collapse
I'm using Automatic Call Recorder Pro with my Nexus 6p and it works great, you can setup up default actions on how you want the recordings handled including automated backups to your cloud account. I have mine automatically saved to my Google Drive account when on wi-fi. Or alternatively you can choose to handle everything manually in which case you willl be prompted at the end of each calll.
I'm still waiting for my pre-ordered Pixel XL so I haven't yet tried it with that handset at this time.

gheymann said:
I'm using Automatic Call Recorder Pro with my Nexus 6p and it works great
Click to expand...
Click to collapse
I'm also using Pro licence, with version 18.6 and use the DropBox integration. But, as I mentioned, it doesn't seem to record on the Pixel and according to the developer shouldn't be working on your Nexus either.
Would you mind answering a few q's?
* What version of OS do you have on your Nexus?
* In ACR, what is the Audio source?
* Are you attempting to record using bluetooth?
* Did you select a profile in the 'Recording issue' setting, and if so, do you know which one?
Thanks.

ohmegosh said:
I'm also using Pro licence, with version 18.6 and use the DropBox integration. But, as I mentioned, it doesn't seem to record on the Pixel and according to the developer shouldn't be working on your Nexus either.
Would you mind answering a few q's?
* What version of OS do you have on your Nexus?
* In ACR, what is the Audio source?
* Are you attempting to record using bluetooth?
* Did you select a profile in the 'Recording issue' setting, and if so, do you know which one?
Thanks.
Click to expand...
Click to collapse
No Problem glad to help
Android version 7.0 with the August 5th, 2016 security patch, build NRD90M
Audio Source: Voice Communications
Audio Format AMR
App version: Pro 5.20 (103)
Delay calll in: 500
Delay call out: 1000
I haven't tried recording using a bluetooth headset, I do have bluetooth built in to my car and can send or receive calls over bluetooth without issue, haven't specifically checked calll recordings while driving using the built in car bluetooth system.
App works like a champ, hope that helps troubleshoot your settings!

gheymann said:
No Problem glad to help
Android version 7.0 with the August 5th, 2016 security patch, build NRD90M
Audio Source: Voice Communications
Audio Format AMR
App version: Pro 5.20 (103)
Delay calll in: 500
Delay call out: 1000
I haven't tried recording using a bluetooth headset, I do have bluetooth built in to my car and can send or receive calls over bluetooth without issue, haven't specifically checked calll recordings while driving using the built in car bluetooth system.
App works like a champ, hope that helps troubleshoot your settings!
Click to expand...
Click to collapse
Interesting, thank you.
Just to check, it's the same app. ACR by NLL ('Another Call Recorder). I only ask because that version number is very different to the one for the app I've got.
I'll change from auto to voice communication when I'm back in the country (Monday) to see if that fixes it.

ohmegosh said:
Interesting, thank you.
Just to check, it's the same app. ACR by NLL ('Another Call Recorder). I only ask because that version number is very different to the one for the app I've got.
I'll change from auto to voice communication when I'm back in the country (Monday) to see if that fixes it.
Click to expand...
Click to collapse
The Program I'm using is Automatic Call Recorder Pro by Appliqato "NOT" Another call recorder the version number 5.20 (103) is the latest available in the Play store.
All the best
geO-

I've checked Automatic Call Recorder with settings provided by @gheymann and it works... thanks

matchev said:
I've checked Automatic Call Recorder with settings provided by @gheymann and it works... thanks
Click to expand...
Click to collapse
I'm glad that worked for you, I hope it will work for others as well!

gheymann said:
I'm glad that worked for you, I hope it will work for others as well!
Click to expand...
Click to collapse
IT works way better in Root, picking up the stream of both Mic and Speaker.
Without root Mic audio is fine but speaker Audio is way low.
I can easily hear both ends of the conversation but it is simply not as effective as when you have Root.
But it works fine enough for the law, Yes i am in a one party state.

gheymann said:
The Program I'm using is Automatic Call Recorder Pro by Appliqato "NOT" Another call recorder the version number 5.20 (103) is the latest available in the Play store.
All the best
geO-
Click to expand...
Click to collapse
Just to follow up on this. I'm now at 7.1.1 and, after uninstalling AnotherCR, installed AutomaticCR, but it only records my voice not the caller, regardless of settings. I suspect it's the lack of root. Ho hum.

I just discovered this issue too. Wish I would have checked previously to see if it was actually working. Time to add another thing to check when moving to a new phone. Oh I miss my Note 7 but outside this recording issue, the Pixel XL is Awesome!

Use boldbeast app from Google store, then use these settings : use these settings to record calls:
- Record Mode: Alsa
- Alsa Channels: 2 Channels
- Tune Audio Effect: No
- Tune Audio Route: Group3
- Change Audio Controls: Yes
- Change Audio Driver: No
- Start Input Stream: test Yes and No
Sent from my Pixel XL using XDA-Developers Legacy app
---------- Post added at 01:42 AM ---------- Previous post was at 01:40 AM ----------
Tested on android 7.1.1 latest build, rooted. You have to activate root option in the program. Tested on Bluetooth and regular voice, working perfect. Enjoy!!
Sent from my Pixel XL using XDA-Developers Legacy app

I always found that Call Recorder by skvalex worked on all the phones I used. Paid app but one of the best out there.

This app works for my Pixel XL, very clear recording both ways without rooting the phone play.google.com/store/apps/details?id=com.enlightment.voicecallrecorder

ach1234 said:
This app works for my Pixel XL, very clear recording both ways without rooting the phone play.google.com/store/apps/details?id=com.enlightment.voicecallrecorder
Click to expand...
Click to collapse
Link please

dpalmer76 said:
Link please
Click to expand...
Click to collapse
http://play.google.com/store/apps/details?id=com.enlightment.voicecallrecorder

What? seriously? Are you people paid to promote this app? DUDE. It doesn't work unless the SPEAKER is on and do you know how annoying that is? Not to mention no Bluetooth. The reason for this is simple. Like the guy said you need to ROOT the Pixel to get the other end of the call. Otherwise you are just recording it from the speaker. Not even the last app posted here (which seems to be ADWARE) can do it properly without ROOT.

The call recording feature of Pixel / Pixel Plus is disabled by Google, as a result it can only record your own voice, the caller's voice will be very weak in recordings, no matter what recorder you are using in the market. However during recording if you switch on the speaker it can record calls well in both directions.
It's inconvenient to switch on the speaker, especially when you are in the office with your colleagues. If you don't root the phone you have no solution in the world to fix the problem. If you root the phone there are several recorders that can fix the problem.
After root the phone, Boldbeast Recorder can record calls crystal clear in two sides, both Android 7.0 and 8.0 Oreo work well.
Android 7.0 and 8.0 need different settings, detailed information: https://www.boldbeast.com/forum/topic1343-google-pixel-call-recorder.html

ithehappy said:
I always found that Call Recorder by skvalex worked on all the phones I used. Paid app but one of the best out there.
Click to expand...
Click to collapse
I 2nd this.
call recorder works very well since Note2 days

'Call not sent' error on Android 10 beta

Anyone having this problem where call doesn't connect with error of 'Call not sent'? This is doesn't happen when connected to Wi-Fi but happens most of the time otherwise and I have to re-try 2 times (sometimes 10 times) to get the call connected. I have tried clearing data for phone app but it didn't help. I am not seeing any reports on it in any beta discussion so I am guessing its not a beta problem? It never happened before the beta update and I installed the beta update from total reset instead of just updating.

Yes. Only happens when I am on Bluetooth connected to my car. I gave to call from the phone app instead of my driver control.

"Call not sent" error on Samsung Note10
I'm having a similar issue with my Note10, just shows "Call not sent.", whether connected or not to Android Auto or any other dock/bluetooth, it doesn't seem to fix the problem.
I have tried several active sim cards from different carriers which work fine in other phones, but in the Note10 I can only access the web and text. When trying to make a call with full signal bars and LTE next to it, it just shows "Call not sent". I've done all the usual restart, full factory reset from the recovery menu, even reflashed it via Odin with the latest firmware (N970U1_UES2BTA1) three times, then factory reset again, but it's doing the same. It seems to be a hardware problem, not a software glitch.
By the way, my phone is unlocked and I have checked the IMEI to make sure it's not blacklisted. I have also examined the charging port for any liquid damage, but it's completely clean and shiny. When I dial the test code *#0011# to compare the network status screen against a Samsung S9's, I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
Also, out of curiosity I have installed a couple of different phone dialers (Google Phone and Simpler Dialer), but the outcome is the same "Call not sent.".
Evidently there's a hardware problem with the Note10 series (some or all), because Samsung's own forum full of similar complaints.:=(

Same problem. Getting call not sent
Was not issue in Android 9. Only Android 10.
Galaxy note 10+ unlocked version on tmobile.
I've also had other random Bluetooth issues.
this issue got so bad, i am not able to make calls, unless i make multiple attempts.
so i just upgraded to the S20 Ultra. Same issue!!
Here are other factors and connected devices.
Connected to a Ford vehicle (Sync; 2017 Explorer)
Connected to Samsung Active2 smartwatch (but issues remained even when watch disconnected).
I've also tried to unpair / re-pair. To no avail...
Help!
Also here:
https://us.community.samsung.com/t5...-Android-Auto-after-upgrading-to/td-p/1077007

I am really glad I blocked updates, I am still running on Pie

billa said:
I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
(
Click to expand...
Click to collapse
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?

ultramag69 said:
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
Click to expand...
Click to collapse
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.

billa said:
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
Click to expand...
Click to collapse
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...

ultramag69 said:
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
Click to expand...
Click to collapse
Right, but usually same bootloader version updates are just maintenance or critical security updates only.
Looks like some major changes have happened in the latest update, which could be causing the no call issue.
Just checked, and it's still the same version available.
Version: N970U1UES2BTA1/N970U1OYM2BTA1/N970U1UES2BTA1/N970U1UES2BTA1
OS: Q(Android 10)

I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.

kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.

Chiming in late to the game with a Samsung Galaxy S20. I never had this issue with the new OS on my S10 but it started happening with the S20. It's also intermittent. Sometimes it works. I have tried unpairing and repairing. I have tried deleting the bluetooth device and reconnecting it. All to no avail. At least other folks recognize this issue and hopefully Samsung issue an update soon.

i have regerts (spelled wrong to be funny)
winol said:
I am really glad I blocked updates, I am still running on Pie
Click to expand...
Click to collapse
As nice as this phone is--I am annoyed with myself that I upgraded to Android 10--everything worked so great with 9!!! I wish there was a way to go backwards. I might investigate that, actually. I have a little downtime as of late.

I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…

i have Android 10 ui 2.1 with infinity rom 6.0 rom N975FD and everything works perfect including goodlock 2020

winol said:
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
Click to expand...
Click to collapse
For me, Android 10, whether UI 2.0 or 2.1
battery.... standby, is exceptional good .!
I am a power user, eg theming etc
so i don't worry or have time to worry,
about SOT ETC....
For me what matters is when , my device is sleeping.....!
/ if anything
is draining my device battery etc.
( Ihave about 200./300 apps.)
Suggestion... factory reset or did you already done that.?
See examples of device overnight
standby etc.

kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
THIS WAS THE FIX FOR ME! I'll have to research why Android 10 isn't playing nicely with Google Voice, but I'm glad I can hit call and it goes though, instead of hitting "send" over and over and over again!!!

S10+ Exynos, running Android 10 stock - same problem. Annoying as hell!
I can't uninstall GV because I use it for international calls.
Edit: BTW - it definitely seems to be affected by connected BT headset. As soon as I turn the BT headset off I am able to make the call (using MPOW headset, don't remember the exact model).

billa said:
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Click to expand...
Click to collapse
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.

dhebi111 said:
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
Click to expand...
Click to collapse
Are you (were you at the time) connected to a BT headseat? It happens to me only when my headset is connected, and not just one - two different types of headseats and also happened once or twice when the phone was BT connected to my car. As soon as I disconnect the BT, all calls can be completed without a problem.