I received the New Gear VR and Controller and attempted set up on my S8+. Everything went smooth until pairing the Controller. Inside the Oculus app The pairing instructions are displayed, and it flashed a toast message that it connected to the controller. However, from there nothing else will work. Checks for firmware updates for 5+ mins, and randomly will say there's an update available. I attempt the update, and it just sits at downloading 0%, then a toast will pop up that the controller disconnected. So I skipped the firmware update and moved straight to the calibration. Step 1 with the figure 8's generally work fine. Step 2, set it flat displays a green check, and then again the toast that the controller has disconnected. Then another toast message of Unable to connect to the controller. I've swapped the batteries, still the same issues. I was wondering if there was a way to default/reset the controller, and start the pairing process again. I've tried, removing it from paired Bluetooth settings, clearing the cache of the Oculus app, etc. However it seems to instantly re-pair as soon as I put the batteries in the remote, and I'm in the same cycle of connections and disconnections. I've been able to use the Gear VR and everything ELSE is working, but as it the remote is not staying connected long enough to update, calibrate, or use. Any ideas? Thanks!
i have the same. tried uninstalling several times already to no avail.
I was having the same problem. What worked for me was to unpair the controller and pair it again over BT. But don't do it from within Oculus app, because it will not solve your problem. Do it from your phone Bluetooth settings instead.
If you restart your phone the issue may return. If it happens, just unpair and pair it again (always from your phone BT settings...) and you will be good again.
Regards
Enviado de meu SM-G935F usando Tapatalk
Had the same problem. What solved it for me was to go back to the default theme. I've ran into occasional problems where it turns out to be my theme. You can go back to whatever theme you use after getting the controller to work. Of course, disregard if you're not using a theme.
Thank you Ramer! That solution was the answer to my problem!! Awesome!!
Had a similar problem. Ended up being the batteries after 2 weeks of first use. Just posting in case someone hasnt tried that
Related
Just wanted to throw this out here in case anybody else runs into this problem. I just purchased a bt keyboard, worked fine for a few days, then suddenly my tab started to freeze, even after rebooting. System panel would show full cpu usage, and it took minutes to simply scroll, but the time and charging indicator worked in real time. After some searching I found some troubles the tab had with bluetooth devices. To the point, I found that after opening pandora for the first time since I had the keyboard that the bt media setting was enabled, turned that off, rebooted, and its been at least 5 hours and haven't had a problem since, usually only took a few minutes to freeze after powering up. As a side note, I'm sure other apps/settings may cause the same problem.
Sent from the Tab
I use(d) bluetooth headset and my freezing problem was with any and all music players. I have Pandora installed, but is it only the setting in pandora that's the problem or all music players?
It could be any apps really. For me it was pandora, I'm using poweramp for my music and I know that has bt disabled. I would just check any media apps for bt settings.
From the Captivate
Thanks
I noticed that the 'Bluetooth' was the cause of my GT-P1000 freezing issues.
But I didn't know that some apss could also cause this!
I will try to uninstall Pandora and see if the BT issues has been resolved.
It's annoying coz I often turn the BT ON coz I used it as my primary phone number
So since you changed the BT setting in Pandora, have you had any freezing issue at all? My device started freezing like mad and I couldn't for the life of me figure out what it was. I first deleted unnecessary apps, no effect. Then I formatted the memory, followed by a factory reset when the format didn't work. The problem persisted! Two constants in the equation are the presence of Pandora (which I did not realize uad a BT setting) and my Apple Bluetooth keyboard. I finally put two and two together that it had to do with my keyboard, so now I'm a bit wary of even pairing it again lest I smash my Tab against the desk in a fit of freeze induced anger.
So I am interested to know if yoir correction of the Pandora setting seems to be a permanemt resolution.
Notice the typos above? That's because I'm not using my Bluetooth keyboard. Haha
Sent from my GT-P1000 using XDA App
Helps alot, thanks.
Yep. Pandora. As soon as got my new Jawbone ICON Hero bt earpiece I decided to try it with my media players. with XiaaLive it was fine. Audio was nice and clear. Starting and stopping the app was smooth. However, when I tried Pandora, audio was fine and starting the app was fine. But every time I tried quieting the app my US T-Mo Galaxy Tab would get super slow. Everything was going in slow motion. Folders would take 20 to 30 seconds to open. Even pressing the Power button took about 15 seconds to show the "Shut Down" screen.
After a reboot, everything was fine again. And I left it alone until the next day when I tried it again. And sure enough. Upon quitting the Pandora app everything got really really slow again.
So, using Pandora and a BT device seems to be the issue.
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.
after the last update my neo2 no longer gives option on notifications to show on device. It is grayed out. I loved that feature any ideas to get back?
I had this happen when I changed ROMs and also when I replaced my Note 3 with the Note 4. If you are having problems after an update (as opposed to setting it up on a new product), you might be able to reboot your Gear and be done. Conversely, you might need to go to the watch settings and "Bluetooth", then uncheck the Bluetooth box to turn off the Bluetooth, then re-check the box to enable Bluetooth and have it locate your phone again. At the very worst, and I had to do this on mine, you would go to settings (on the watch) and "Reset Gear", and basically start from scratch.
The last update yesterday to gear manager now shows the send to device link but it still does not work though. What is going on w/gear manager?
Also I noticed my weather watch face is gone. Why would they take that away, I wonder?
Sent from my SM-G900P
Hate resurrecting old threads but I just noticed my gear 2 neo show on device button is also grayed out and I didn't change phones or roms or anything like that. Just quit working one day and rebooting didn't solve it, nor did "forgetting" it from my phone and reconnecting.
I have a weird problem with my Moto X 2014 (Pure Edition). It's randomly losing bluetooth connection in a background (basically any BT connection – to auto, smartwatch, etc.) but the phone itself says everything is fine (Bluetooth is on and devices are connected). But actual connection is not working: unable to play music via BT, unable to discover a new BT device, notifications not coming through to a smartwatch, etc. Bluetooth devices continue to show as connected even if I power them off, and when I turn them back on, they won't reconnect.
I meet this problem every 1-2 hours, sometimes even 10-20 minutes. The only way to fix this problem - to turn off BT and then turn it on again. Or keep Wi-Fi always off.
I tried to use another Moto X (2014, same software build version), to pair and unpair devices, to clean cache and even do a factory reset (with and without backup restoring) – the problem is still here. That's weird but this problem start appears 2-3 weeks ago, before everything was just fine.
Phone: Moto X 2014 Pure Edition @ T-Mobile, Lollipop 5.1 (TMO_Pure_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US)
Devices: Pebble Time, Pebble Time Steel, Ford SYNC2, Moto Stream.
Things I tried that didn't help: deleting and re-pairing devices, deleting all old device profiles, clearing cache, reflash, factory reset, safe mode, flash CM12.
BT HCI Logs:
A disconnect at 1:28pm
dropbox.com/s/q3pka5egagq3e5g/01_btsnoop_hci.log?dl=0
A disconnect at at 3:09pm (or so)
dropbox.com/s/f2kl4rowr12lypt/02_btsnoop_hci.log?dl=0
Same issue here with a VZW XT1096, since OTA to 5.1. Factory reset does not help.
Up
Same issue here, same device & carrier & software build version & Pebble Time Steel. As long as I'm constantly making use of a BT connection, it seems to stay alive just fine, but as soon as it sits idle for more than a couple minutes, the connection drops (according to the BT device, but not according to the phone). I've tried all the same things with the same total lack of success. I have nothing new/helpful to offer, but at least you're not suffering alone.
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Just to say I have the same problem with a Pebble Time Steel and my 2014 Moto X. Have e to disable BT and dependable BT to get phone to connect to Pebble to only be dropped a few minutes later from Pebble side.
Lyre
AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
I'm having the same problems and have also had it "go away" for extended periods of time only to reappear after a day or two. Mine will drop the BT connection even if I'm actively listening to audio over my headset.
Registered because I'm having the same issue. I'm running stock 5.1, no root. The connection to my Pebble Time Steel is very unreliable. The Bluetooth settings thinks it's still connected, the Pebble Time app on my phone thinks it's still connected, but my watch shows no connection and there's no communication to or from my watch. Sometimes it'll work for hours just fine and then drop, sometimes it'll only be a few minutes. It seems to be when the phone screen is off. Turning BT off and on always fixes it, it'll immediately automatically reconnect and show it on the watch.
I've tried the Pebble troubleshooting online (factory reset & recovery mode on watch, uninstall Pebble Time app, forget pairing on all devices, remove all other BT apps, reboot phone, reinstall Pebble Time app, re-pair) but the problem remains.
In the past, I've had it where my Fitbit One seems to have dropped the connection. Since the sync is so infrequent, I don't notice it much but I did catch it where it hadn't synced in a few days. (That app was uninstalled while I try to figure the Pebble thing out)
Next step is factory reset on the phone, but it sounds like that's not a fix for some people. That, or design a watchface that sends a keep alive signal to the phone, which runs an app to reset the BT when the connection drops. Since it's still listed as connected, I don't think Tasker will fix it.
Same issue. My phone is a Verizon Moto X and I've tried factory reset. Hoping that whenever they update to 6 that it will fix the issue, but I'm ready to smash my Moto x over this
AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
While I hope your problem is "fixed" I would not be too hopeful. I have had this problem as long as I've had the phone. Sometimes it goes away for a while but it always returns. Right after I unlocked my bootloader and it did a complete factory reset the problem went away for a week but it eventually returned. I've seen similar problems reported with all the MX14 variations and nobody seems to have a solution. There was a thread on the Moto forums with folks reporting these issues to Moto but nothing ever came of it. Seems to be connected to wifi somehow because I don't seem to drop the BT connection if wifi is turned off. Not really a useful solution but it does seem to work. I just gave up and put a BT toggle button on my homescreen.
I had the same problem using marshmallow, I downgraded to 5.1 and it went to normal
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
jimbo0914 said:
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
Click to expand...
Click to collapse
Update: I changed over to Android M on CM13 and no longer have this issue. Nice not to have to power toggle the BT function a couple times a day anymore.
YMMV
Met the same problem after updating to Android M.
I often connect to BT during driving and after a few days working normally, my headset will be disconnect without any "notification".
My solution is to wipe cache, after that BT connection will work well for another few days.
Never met this issue in Android L, but I just love M so much.
Looking for better solution / fix.
I found this thread while searching for some solution for my BT+Android Wear problems. I have them since circa february / march 2017.
But today, I got a problem with non-Wear watch (Fossil Q Grant). I noticed my phone was locked even if I have smart lock set up. I checked fossil q app, the watch was connected, it received notifications so far. But in the phone settings, in smart lock, all my devices vanished. I checked the BT setting and saw the same. All my paired devices disappeared! It happened after nothing more than a restart, after my fossil lost connection earlier today and did not want to reconnect. So I restarted the phone.
This happened to me the second time already, but first time I somehow did not pay attention because I was frustrated by the Wear app problems and weekly factory resets to get my Wear watches working.
Could our issues be related? Some bluetooth software bug in phone? THIS IS PURE HELL!
Moto X4 cant come soon enough.
So here's a wierd one. Have a SM-N960U1 on Android 9. Everything's been fine but as of last Friday every time it pairs with a Bluetooth device (headphones, car, etc.) it starts calling itself? I re-paired all devices, turned BT off and back on, restarted phone, etc., but this behavior persists. Music is also terrible during this time, but realized by accident when I press Device Care widget to optimize phone the BT device announces 'Call Ending', and music again sounds great. However there's no record of any outgoing call in Phone App. I didn't realize what # was being called until I got in my car and saw it was dialing itself, but again, this phantom call does not show up in Recent Calls history? Any ideas?
Ugh... Same
Same man. Just letting you know you're not alone and following for a resolution.
smart lock on?
Removed all trusted devices from smart lock and it still happened.
Did a support Chat with Samsung, they recommended a soft reset (Vol dn + Power, similar to a Battery pull) which solved it temporarily when I turned on Bluetooth but since then the bug continues. No new updates or setup changes I'm aware of before this started happening. They also suggested running in safe mode and disabling Apps one at a time to see if the issue can be isolated (aren't these supposed to 'be' smartphones? Evidently there's no log of what it's doing) Will try that or another Chat session when I get some time again.
Ive been having this issue for a week or so as well. Every time I get in my car, I have to end the call. Its got to be a software update that caused the issue.
I'm thinking now it could be related to Bixby. I don't use it (remapped to google assistant & flashlight on long press using bxActions) but I recall I allowed it to update recently in case it gets better in the future.
Same issue here ... Sprint Note 9 on Pie ... Bluetooth headphones even has issues. I have to make a phone call and end it to be able to control volume from the headset (changing it from in-call audio to media audio).
Yup, those are the symptoms. Bluetooth headphones sound terrible and has no device control until the 'phantom' call that starts on it's own is manually ended.
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
ogretech said:
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
Click to expand...
Click to collapse
Awesome tip!
I use Ring Central App for keeping up with work phone messages. A few days ago started the phone in safe mode and had no BT issue, then back in 'un-safe' mode at first it didn't happen but cycling the headphones on and off it did occur again so I was faced with narrowing it down to which App. After reading your post I went into RC Phone settings, Mobile App Settings, Default Launching, and turned off 'Call From Android Dialer' since I don't use that feature and so far no issue!
Thanks for the tip, hopefully this setting change continues to solve this.
Still good after a couple days and weekly auto phone restart (Sat @ 3:00 AM). So nice not to have to end a phantom call that interrupts the stereo after 10 seconds every time I start the car.
Thanks again for the RC Phone tip.
You guys are definitely not alone. I unfortunately do not use the ring central app so I am not sure what is causing it for me...
I'm on the note 10 and have only had this problem pop up recently out of nowhere... I have no idea what could be my problem as I do not have RC Phone installed on my phone
Possible Solution
Hey, I posted a few days ago about having this same problem and not being a user of ring central. I got to thinking and tested this out. The Voxer app was the issue for me. I uninstalled this app and I haven't had any problems since. I am not sure about why the most recent Voxer update caused my phone to start doing this but I hope this helps someone else.
Possible Solution
Some may have tried this. Let me know.
My wife has Honda Hands Free 2016. In the past 30 days it started this same freaky behavior as all of you list.
She has a Samsung s9+.
She also has had Voxer installed on her phone and has had for many years. I will have to check to see if a recent update hit.
But, this is what seems to work for me at this point........
Told Honda Hands Free to completely forget her s9+. Then disabled blue tooth on the s9+.
Turn Entire Honda car off.
Turn Honda back on, told it to connect to my Samsung phone SM-J320A. Verified Honda was connecting properly to my SM-320A with no issues. All good with no freaky behavior. As info Voxer is not installed on my SM-320A.
Turned bluetooth back on s9+ then added the Samsung s9+ back to Honda Hands Free and told it to completely forget my SM-320A.
So far this has stopped the freaky behavior. If it comes back I will update here and then I will try uninstalling Voxer.