Hi all, anyone has encounter the s-pen kept disconnecting or can't even connect via the S-Pen Remote constantly?
airfong said:
Hi all, anyone has encounter the s-pen kept disconnecting or can't even connect via the S-Pen Remote constantly?
Click to expand...
Click to collapse
I noticed mine was connected yesterday, then I pulled it out this morning to snap an awkward photo and it was somehow disconnected. I had to "reset" it to get it to connect. I also noticed a notification letting me know it was not connected prior to this.
Mine is disconnecting too. I have to go in and reconnect it in the S Pen settings. As of now I turned it off. Hoping an update fixes this.
My S-Pen does nothing except for shake the air command icon when I press it. It's set to take pics.
Sent from my SM-N960U1 using Tapatalk
This issue is annoying as hell. Samsung needs to pick up the pace with a fix!
---------- Post added at 07:34 PM ---------- Previous post was at 07:33 PM ----------
Hella annoying! Samsung needs to pick up the pace with a fix for this problem.
I fixed it by using a different case.
Hi, after update to latest pie firmware (CSC:KSA) s pen remote is not working. I have tried resetting spend from setting. clearing cashe. but it says unable to connect to spen. any solution. or anyone here to confirm that it cause by this latest firmware. Please.
Related
Noticed today my screen would randomly come on with the phone sitting across the room. Has anybody else noticed this? I only had one homebrew app installed that had background activity so I uninstalled it to see if that would stop it. It has happened once since then.
Sent from my SGH-i937 using XDA Windows Phone 7 App
Only time I've seen this happen is when receiving text message or phone call; otherwise, I just hear vibrate/audio for background tasks and screen remains off.
I have the same issue
It doesn't switch off then
---------- Post added at 02:22 PM ---------- Previous post was at 01:38 PM ----------
It appears after I change Lock Settings first time
I didn't have a similar issue
Charging port problem?
Could be an App or the case
I've had this happen to me on two occasion. First was because of one of the flashlight apps. Once I uninstalled it, the problem stopped. Next time the case I had for it was so tight it always pressed the power button. Hope you find this helpful.
The problem has not repeated itself in many months. Maybe it was an app that is no longer installed?
Sent from my GT-P3113 using xda premium
I had the same problem plus the screen would become unresponsive to the touch. When it's charging, the problem goes away. At one point, the phone thought it was charging with no cables attached to it and it worked okay. It comes and goes. For no reason, the screen will turn on and just keeps beeping.
william8004 said:
I had the same problem plus the screen would become unresponsive to the touch. When it's charging, the problem goes away. At one point, the phone thought it was charging with no cables attached to it and it worked okay. It comes and goes. For no reason, the screen will turn on and just keeps beeping.
Click to expand...
Click to collapse
This also happened to me.
You have the solution in this link:
http://forum.xda-developers.com/showpost.php?p=37217587&postcount=4
Good luck :good:
OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?
I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.
I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification
disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...
Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.
I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.
On a friends p10 lite the screen is timing out after like 10 seconds even though its set to 5 minutes in display settings, any idea why?
Battery saving mode is probably turned on, check that!
Nothing enabled in that section, it's still timing out very quickly.
It happens to me too, no matter how much I set the timeout to. Usually happens when watching an Instagram video or while on Snapchat camera. Any fixes?
Happens to me too, on my p10 lite. Anyone found a fix? It is so annoying
---------- Post added at 10:10 PM ---------- Previous post was at 09:20 PM ----------
I did a " reset all settings", and it works now. It is probably a software issue, but I dont know if the problem will reappear or not.
Found a fix. I did a "reset all settings" in settings and it now works.
This helped me as well. Thank you. Mind you, this action bumps off your wifi password, your contact names connected to your email and your push notifications. So you'll have to reinstate all those after performing a reset.
Anyone else having issues with the note 9 and android auto? I no longer receive texts to Android auto when connected. I can send but not notifications come through.
Yes, all permissions and access to notifications are set. I've uninstalled and reinstalled. Deleted the phone from my car. Reset the Google app as well.
Nothing seems to be working. I'm thinking it's just an issue with the android auto app and being a new phone. Likely just needs an update to the app to fix the issue. At least I hope.
If you have android auto and a note 9, please test this out and report back.
I haven't had any issues with Android Auto on my Note9. Are you using any apps to disable services. I had a similar issue with my Note8 and it ended being a service disabled.
No, nothing that would disable it.
So get this now. I have hard reset my note 9 to see if this would fix it. It did not. I decided to try installing Google Messages. It works. Android auto and incoming texts works with this app. Just not the stock Samsung messages app. Has to be something with that app. I'll use Google messages until there is an update and then give it a try again.
Quite annoying though. I really don't mind the Samsung messages app.
Hi, I have a similar problem, Note 9 with Alpine iLX-702d Head unit, as soon as you plug the cable into the phone to start the setup utility for AA, the app closes. not cool
I do have a note 9 since last saturday. I already could work with android auto with no problem. Today i connected the phone and i was unable to use android auto. No update have been done.
My android Auto disconnects on its own randomly. OEM head unit in a VW Jetta 2019. Note 9 is a Tmobile unit that I just setup. Not sure it is related but I also have Android Wear problems where the bluetooth disconnects all the time, and I have to put my phone and watch in airplane mode and back again just to get it to connect.
Using Android Auto with my Note 9 lags for about 4 seconds on every touch input so is pretty much unusable. Have tried rebooting the device and head unit (Honda Civic 2017).
Have a Peugeot 2008 2017
Just can't seem to get android auto to work
When I open android auto app on my note 9 it just says "something went wrong
Google play services doesn't seem to be working at the moment. "
If I connect the USB to car it keeps connecting then disconnecting over and over, gutted as apple carplay connects flawlessly ?
Any help would be appreciated
Mine works better than my note 8 device. No misses yet.
And I use it on my commute everyday to work and back.
Sent from my SM-N960U using Tapatalk
Have a 2018 focus st with AA. TMO note 9. I have zero problems with it so far. All messages come through on stock. Ok google works with no button push. And Facebook messenger works good as well as Waze.
I've got a Hyundai i30, and AA was working perfectly until I updated my Note 9 to the September patch. Now it disconnects after a random amount of time, usually 2-4 seconds, sometimes up to 15 seconds.
Very frustrating!
When I plug my Note9 into my 2016 F150 the bottom on-screen buttons on Android Auto freeze and do nothing when you tap them then the whole bottom line turns into a black bar. The only way to Navigate between screens in Android Auto is to pull the cord from the phone and make your new selection.
BigMosely said:
When I plug my Note9 into my 2016 F150 the bottom on-screen buttons on Android Auto freeze and do nothing when you tap them then the whole bottom line turns into a black bar. The only way to Navigate between screens in Android Auto is to pull the cord from the phone and make your new selection.
Click to expand...
Click to collapse
Have the same problem. If I uninstall Android Auto and reinstall it works briefly then right back to the navigation buttons doing nothing and turning to a black bar.
Sent from my SM-N960U1 using Tapatalk
ldkud50 said:
Have the same problem. If I uninstall Android Auto and reinstall it works briefly then right back to the navigation buttons doing nothing and turning to a black bar.
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
Yep, same here.
I opened a thread on the Android Auto Forum about it...
https://productforums.google.com/forum/#!msg/android-auto/O3S-JU5BCdA/j2YcAxdFAgAJ
ldkud50 said:
Have the same problem. If I uninstall Android Auto and reinstall it works briefly then right back to the navigation buttons doing nothing and turning to a black bar.
Click to expand...
Click to collapse
Yes I also uninstalled AA and it worked for a ride and when I got back in my Truck it didn't work again, WTF man.
---------- Post added at 11:47 PM ---------- Previous post was at 11:45 PM ----------
tripleoptic said:
Yep, same here.
I opened a thread on the Android Auto Forum about it...
https://productforums.google.com/forum/#!msg/android-auto/O3S-JU5BCdA/j2YcAxdFAgAJ
Click to expand...
Click to collapse
I'm glad to see it's not an issue with just my Note9. I'm sure it'll be fixed in no time since it looks like a widespread issue.
BigMosely said:
Yes I also uninstalled AA and it worked for a ride and when I got back in my Truck it didn't work again, WTF man.
---------- Post added at 11:47 PM ---------- Previous post was at 11:45 PM ----------
I'm glad to see it's not an issue with just my Note9. I'm sure it'll be fixed in no time since it looks like a widespread issue.
Click to expand...
Click to collapse
I sure hope so. we are submitting bug reports now.
Works great in my 2016 Silverado.
Sent from my SM-N960U using Tapatalk
Same exact black bar issue started happening to my Note 9 with a 2016 Ford Escape, since last week. I thought I was going crazy. Uninstall, reinstall, works for a ride, and then breaks again.
Sent from my SM-N960U using Tapatalk
I am having issues as well with my Note 9 and android auto. When I use google maps, it will work for a few minutes and then it goes out. Google maps will never stay up for more than a few minutes. Is it just an issue with the app? I just bought a new car and want to be able to use android auto!
Hi Everyone,
I have a weird problem with my Note 9, I connect it to the PC and a notification showed up to allow transfering data and I allow it.
then I activate the Development mode to change it back to charge only as default USB and this is what happened:
The first time I chose charge only the screen go all white then it do back to development menu
then I click on the Default USB configuration again and click on the charging phone only the settings app crash.
I tried to do it while the USB cable connected and with out it didn't help
restarting the note, disable and re-enable the development mode.
Android version: Pie
Anyone having the same problem?
I started to have also an issue with this. A "settings keep stopping" message continuously appears and it started shortly after the Pie update.
I can go into settings and everything there works fine but the message is annoying. I cleared the cache from the recovery menu but nothing changed, the message persists.
Sometimes the phone freezes when trying to open an app or when accessing the secret folder. It is necessary to reboot it.
Ugh!!
Sent from my SM-N9600 using Tapatalk
Never have that issue. I did a factory reset. But u can try to clear data and cache in apps setting. Not in the recovery.
I have this issue too.
The only annoying workaround I found is to select it through the notification when I plug the USB cable every time...
---------- Post added at 02:01 PM ---------- Previous post was at 01:58 PM ----------
Did you disable some system apps?
If so we can compare since I did with some, to see if it correlates.
if you both updated to pie without doing a factory reset, weird stuff has been reported.
like anything in the IT world, major revisions should be used from scratch and not updated to.
I made a factory reset and it seems my issue is related to the knox modification made by adhell
Sent from my SM-N9600 using Tapatalk
teddy beer said:
I made a factory reset and it seems my issue is related to the knox modification made by adhell
Click to expand...
Click to collapse
if stock works and a modded os dosent, then there is your answer
We are not using a modded OS.
Nastrahl said:
We are not using a modded OS.
Click to expand...
Click to collapse
well the guy above said he used adhell.
a anyways my comment regarding wiping clean when doing a major update still rings true.
AdHell is a GUI to set up a Samsung app already installed on the phone, it mods nothing.
And I wonder how AdHell could ever interfere with the USB charging mode since it's provide no option related to it. ?
---------- Post added at 10:33 PM ---------- Previous post was at 10:31 PM ----------
Your shouldn't have to factory reset your phone nowadays. And by reading the forum i it actually does nothing 99% of the time.
Nastrahl said:
AdHell is a GUI to set up a Samsung app already installed on the phone, it mods nothing.
And I wonder how AdHell could ever interfere with the USB charging mode since it's provide no option related to it. ?
---------- Post added at 10:33 PM ---------- Previous post was at 10:31 PM ----------
Your shouldn't have to factory reset your phone nowadays. And by reading the forum i it actually does nothing 99% of the time.
Click to expand...
Click to collapse
sure beats doing nothing about it though.
and yeah factory resets does really help when you've upgraded from a previous OS.
also maybe you should read on what can be done with adhell:
https://bit.ly/2Uz24nP
after the read maybe you will understand better by point.
( by modding ( change what is initially not possible) like disabling packages or changing certain permissions can cause FC's)
Reset everything and just let the phone handle it.
Since my s5 on android 5.0 it automatically handles the connection. Just close the window after you enable it In the popup!
Photo's[emoji2398] by Sully using SM-N960U or SM-870A
bober10113 said:
sure beats doing nothing about it though.
and yeah factory resets does really help when you've upgraded from a previous OS.
also maybe you should read on what can be done with adhell:
https://bit.ly/2Uz24nP
after the read maybe you will understand better by point.
( by modding ( change what is initially not possible) like disabling packages or changing certain permissions can cause FC's)
Click to expand...
Click to collapse
Except the firewall part you can already do all of that with ADB. Technically, what you can do in general still falls under that range.
They why I asked him firstly if he did disable some components because it's not technically possible that the two behaviours correlate, especially when it's working through the notification.
---------- Post added at 03:28 PM ---------- Previous post was at 03:27 PM ----------
sullytrny said:
Reset everything and just let the phone handle it.
Since my s5 on android 5.0 it automatically handles the connection. Just close the window after you enable it In the popup!
Photo's[emoji2398] by Sully using SM-N960U or SM-870A
Click to expand...
Click to collapse
What we are trying to do is that to be the default behaviour without having to enable it every time.