Develop Bugs

[Q] SideSync with Galaxy S Tab + S5 -- can't operate touchscreen

I am using:
Galaxy Tab S 10.1 (SM-T800)
TMobile S5: Stock rooted late May build, Xposed is installed, Knox apps are disabled (about all the possible relevant things I can think of)
So I fire up Sidesync 3.0 on both devices to try out this much touted feature. I get connected just fine, but I cannot operate the phone's touchscreen at all from the tablet. There's just no response. However, the menu/home/back virtual buttons do work.
A search has turned up empty, which included trying one of the level one script readers from Samsung support. They literally had no information about tablet to s5 connections.
Disabled my exchange administrator thinking it's some security lockdown on my phone, but nope... removed my account, rebooted, didn't fix it. I'm out of ideas.
I figure this is the place to ask. I'm figuring I'm right.

Phreaker47 said:
I am using:
Galaxy Tab S 10.1 (SM-T800)
TMobile S5: Stock rooted late May build, Xposed is installed, Knox apps are disabled (about all the possible relevant things I can think of)
So I fire up Sidesync 3.0 on both devices to try out this much touted feature. I get connected just fine, but I cannot operate the phone's touchscreen at all from the tablet. There's just no response. However, the menu/home/back virtual buttons do work.
A search has turned up empty, which included trying one of the level one script readers from Samsung support. They literally had no information about tablet to s5 connections.
Disabled my exchange administrator thinking it's some security lockdown on my phone, but nope... removed my account, rebooted, didn't fix it. I'm out of ideas.
I figure this is the place to ask. I'm figuring I'm right.
Click to expand...
Click to collapse
All I can offer is to say that I had no trouble with my Verizon GS5 and my Tab S 10.5 (not 10.1). I controlled it a little yesterday evening. Even made a call through it from my tablet. I tend to keep my phone up on the bar and my tablet with me on the couch so I have sidesync on the phone all evening.

HughesNet said:
All I can offer is to say that I had no trouble with my Verizon GS5 and my Tab S 10.5 (not 10.1). I controlled it a little yesterday evening. Even made a call through it from my tablet. I tend to keep my phone up on the bar and my tablet with me on the couch so I have sidesync on the phone all evening.
Click to expand...
Click to collapse
After some searching around I have found I am not the only one. I was very hopeful a minute ago when I found I didn't have the latest version installed on the S5, but it didn't resolve the issue.

I got this resolved. The issue was with the S5, not the tablet. I needed to install the June S5 update. Ran into a snag where I couldn't install the OTA, so, it was time to bite the bullet and flash a recovery and ROM. Did TWRP + BeansTown's stock rooted (http://forum.xda-developers.com/showthread.php?t=2789850)
...and now it all works. A full restore from titanium and I'm right back in business, now with working SideSync!

[Q] Is there a way to pair Galaxy Gear S to a Galaxy Tab S 8.4 LTE (SM-T705)?

Hi,
I dont know if anyone has an answer to my question but I am just curios if there a method in doing this
"Is there a way to pair Galaxy Gear S to a Galaxy Tab S 8.4 LTE (SM-T705)?"
Coz to my surprise that here in Singapore I tried to pair demo Galaxy Gear S from retail store or even Samsung Store and it would not detect the Gear S on my Tab S 8.4 using the Gear App that I got from the Samsung Store.
They also said that the Gear S is not compatible with any newer tablets (Tab S) that Samsung has even the tablet has LTE and can make outbound and received inbound calls.
Anyone out their either ROOT method or NOT please do let me know coz it would be a waste that Gear S wont be able to pair to a Tab S 8.4 LTE (SM-T705) with phone capability.

Edit:
The only way that I was able to pair my Tab S with my Gear S was to first setup the Gear S on a Note 2, then
I did a titanium backup of Gear Manager and restored that on my Tab S.
I was then able to connect them after wiping the Gear S first. It took a little trial and error and a few restores but it worked.
All of the default Gear Apps work.
The Gear Store is empty but I am hoping a build prop edit will fix that.
Otherwise the Tab S said it was not a supported device.
Sent from my SM-T705 using Tapatalk

kable said:
Edit:
The only way that I was able to pair my Tab S with my Gear S was to first setup the Gear S on a Note 2, then
I did a titanium backup of Gear Manager and restored that on my Tab S.
I was then able to connect them after wiping the Gear S first. It took a little trial and error and a few restores but it worked.
All of the default Gear Apps work.
The Gear Store is empty but I am hoping a build prop edit will fix that.
Otherwise the Tab S said it was not a supported device.
Sent from my SM-T705 using Tapatalk
Click to expand...
Click to collapse
Damn, I have the same issue. And I just sold my Note 4. waiting on delivery for the note 4 duos.

I realize this is an older thread but I picked up the International Tab S this week and wanted to post the process it took for me to get this working with my Gear S.
So, to start off, I have all functions working except the built-in SMS feature. I can use any other message app and get notifications but I am still trying to figure out what it will take to have the built-in SMS on the Gear S synchronize with the Tab S. I think it may require the SMS app from a supported device so that is where I am going next with this.
To get the Gear Manager itself to find the Gear S required Root access and editing the build.prop file. In this file there are two things you must change:
1) [ro.product.model=] should be changed from SM-T705 to SM-N910A (or any Gear S supported model)
2) [ro.build.characteristics] should be changed from tablet to phone. This has to be changed back after completely pairing for the first time, otherwise Settings will force close every time you try to open it.
At this point I have all the apps I need and all functionality except the SMS issue mentioned above and the forwarding feature was not working. After much troubleshooting I discovered that I could not even forward from the settings menu directly. After a lengthy chat with AT&T, and having them reapply my IMEI from my Note 4 to the account, it is now working as expected.
I am very happy with this tablet, even though I do not currently have LTE capability. Being able to combine my tablet and phone is incredible and thanks to the Gear S it is feasible. I guess to each their own but it works great for me. I am hoping that at some point we can figure out a way to add the US LTE bands to this device but it is not that big of a deal for me. Everything I have tried to stream and access has been flawless so far. I hope this post is helpful to others trying to get the Gear S working with the Tab S.
**** Update ***** I just realized that I can send SMS from the Gear S and it goes out like it game from my Tab S phone number as it should. So it appears that it is only coming back from the Tab S that is not working properly at the moment.

[Q] Android Auto on S6 Edge [/Q]

I'm having issue getting Android Auto to play nicely with the S6. Using the Nexus 5 had no problem at all, but the S6 edge loads AA on the Pioneer 4100nex, then defaults to a black screen with white text stating for me to check my phone when in a safe moment. This is after the initial setup having me to accept all the terms of maps, bluetooth, play music and the like. So I know the phone and the headunit are recognizing each other. I'm curious is the preinstalled "CarMode" app has something to do with it??? Its icon appears on the status bar nearly every time I connect via USB.
Any possible insight would be greatly appreciated.

I'm picking up my 64GB edge this Friday(verizon), and first thing I do when I leave the store is plug it into my 4100. Fingers crossed that it works, but I'll be reporting here with what I find.

mindtrip1016 said:
I'm having issue getting Android Auto to play nicely with the S6. Using the Nexus 5 had no problem at all, but the S6 edge loads AA on the Pioneer 4100nex, then defaults to a black screen with white text stating for me to check my phone when in a safe moment. This is after the initial setup having me to accept all the terms of maps, bluetooth, play music and the like. So I know the phone and the headunit are recognizing each other. I'm curious is the preinstalled "CarMode" app has something to do with it??? Its icon appears on the status bar nearly every time I connect via USB.
Any possible insight would be greatly appreciated.
Click to expand...
Click to collapse
I received my GS6 Edge yesterday and I'm having the same issue. It works great with the Note 4. Pioneer had a firmware update to allow for more models of phones. My guess is that they need another firmware update to include the S6.

Reporting back to confirm, having same issue on my Verizon edge. Like mcryans said, probably need an update for the 4100 for better compatibility.

Same here guys
I, too, am experiencing the same issues. I have a Pioneer AVIC-8100NEX and it worked great with my OnePlus One (Oxygen OS). But when hooking up my new S6 Edge (AT&T), it does not work. I spoke to a rep at Samsung and they were not aware of this issue nor even understood what Android Auto even was. The tech was hopeless and a waste of my hour explaining the problem. Hopefully Samsung and Google resolves this soon as many 2015 cars should come with Android Auto support.

I have the AT&T edge and just reporting that the latest Google Play Service update fixed anything wonky between my avh-4100 and my S6 Edge. I'll try voice commands on my way to work but otherwise works like a charm.

Unable to stay connected after s7 Nougat update?

Since i upgraded my s7 to Nougat, my Smartwatch 3 has failed to stay connected to the phone. Most of the time it refuses to connect at all.
Ive googled for days now, trying all of the usual stuff including clearing the bluetooth cache and wiping the system cache, unpairing the watch, safe mode, forgetting the watch and repairing, removing android wear.
The setup starts working and then during the sync stage, i start getting the bluetooth share has failed message several times although most apps seem to sync eg watchmaker pro and strava.
My question is should the Smartwatch 3 still work correctly with my phone even though the phone is on Android 7.0 and the phone is on 6.0?
Thanks
Andy

My SW3 works great with my HTC 10 running Nougat.
Have you tried doing a factory reset on the watch?

That was going to be my last resort!
Think I may be there though
Thanks,
Andy

Just completed a full reset. Paired first time but crashed several times with bluetooth share has failed.
Failed to complete and no longer connects

I'm also on 7.0 and no problem at all. Maybe is something wrong with your BT from S7, unfortunately I have to tell you to try try factory on the phone, if you can't find out. Samsung for me have strange way of using there BT connections maybe this is why.
Hope I'm not starting any flame but.... that's why I'm on HTC (and not only), Samsung (S4 and S5) phone several times have blocked my car BT system...
Sent from my HTC 10 using Tapatalk

Thanks for the feedback. I have done a factory reset and it made no difference, but maybe it is a Samsung issue as nobody with an S7 has indicated they are using an SW3 with nougat.
burleanu said:
I'm also on 7.0 and no problem at all. Maybe is something wrong with your BT from S7, unfortunately I have to tell you to try try factory on the phone, if you can't find out. Samsung for me have strange way of using there BT connections maybe this is why.
Hope I'm not starting any flame but.... that's why I'm on HTC (and not only), Samsung (S4 and S5) phone several times have blocked my car BT system...
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse

I'm having same issues. Updated S7 edge to Nougat last week and everything running fine until SW3 ceased connecting today. Tried everything other than factory reset on phone and cannot get connection to SW3.

Mine has started working after a month of failing.
It's been connected for a couple of days without any disconnections.
The latest attempt was no different to any others.....
I switched off the watch, wiped the system cache, restarted the phone and watch and lt connected.
I left it alone as apps started to sync and there were some bluetooth share has stopped messages but everything works!

try this:
https://forum.xda-developers.com/pixel-xl/help/bluetooth-off-t3572982

andyshandyman said:
Since i upgraded my s7 to Nougat, my Smartwatch 3 has failed to stay connected to the phone. Most of the time it refuses to connect at all.
Ive googled for days now, trying all of the usual stuff including clearing the bluetooth cache and wiping the system cache, unpairing the watch, safe mode, forgetting the watch and repairing, removing android wear.
The setup starts working and then during the sync stage, i start getting the bluetooth share has failed message several times although most apps seem to sync eg watchmaker pro and strava.
My question is should the Smartwatch 3 still work correctly with my phone even though the phone is on Android 7.0 and the phone is on 6.0?
Thanks
Andy
Click to expand...
Click to collapse
If you use in the phone the option "deep kill all apps" in recen menus... you will have sync problem... It happend me with my op3...

I have similar problem with my S7. It works fine with bt connection as long as i connect the watch over wifi. Then no more bt connection is established, only wifi. Turning off wifi makes the watch permanently offline.
Very annoying as my watch can't sync when outside my wifi range.
Any solution so far?

'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.