Develop Bugs

[Q] Stuck at "just a minute"

I installed a new ROM on my Note 3 and in order to re-pair it with the phone I reset Moto 360 and now I cannot get it paired again. In the Android Wear app it just shows as "Connecting" but I was able to pair it via Bluetooth settings. Now it is just stuck at a " Just a minute" with a circle going around. Before I started the pairing process Moto 360 was at 84% battery, so not sure if it's a battery issue.
With that said, is there any other way to pair the watch other then resetting to stock?

ajamils said:
I installed a new ROM on my Note 3 and in order to re-pair it with the phone I reset Moto 360 and now I cannot get it paired again. In the Android Wear app it just shows as "Connecting" but I was able to pair it via Bluetooth settings. Now it is just stuck at a " Just a minute" with a circle going around. Before I started the pairing process Moto 360 was at 84% battery, so not sure if it's a battery issue.
With that said, is there any other way to pair the watch other then resetting to stock?
Click to expand...
Click to collapse
You may have to reset the watch a few times, I saw someone else having an issue with getting it to connect before resetting it three times.

TheJesus said:
You may have to reset the watch a few times, I saw someone else having an issue with getting it to connect before resetting it three times.
Click to expand...
Click to collapse
Thanks, I got it working after resetting it few times.
Scribbled on Note 3.

Good christ mine has been a PitA to get up and running. The original update kept failing on me despite the fact it was charged to 100%.
Now, Ive reset it multiple times after the update, but i keep getting stuck on "connecting" on the phone and "just a minute" on the watch. This is after the pair code in the app and everything.

[Q] Watch continues to disconnect?

Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?

Noticed the same with my 360 and Nexus 5. Both on stock latest versions.

Issue with mine is that the Moto360 constantly says Disconnected when trying to connect to my Note4. I click connect, it says connected and then quickly changes to Disconnected.
Been trying to figure it out for 3 days now.

I think I realized that the issue is in reconnecting.
I still don't know why sometimes it disconnects, but disconnecting itself wouldn't be an issue if then it proceeds to reconnect on its own.
But I realized that when I'm at home, I leave my phone by the computer and walk around. If I walk outside of the bluetooth range, then it disconnects. That's fine. But then it should reconnect when I come back into range, and it never does. It says "Connecting" and never reconnects unless I do it manually as I said in the OP.
So I guess the question becomes: why does it get stuck on "connecting" when it's in range and should be connected? Is this a Samsung issue or a Moto360 issue?

I have seen the same issue with my Moto 360 and an original Moto X. It normally reconnects but then once in a while it just won't. The easiest solution I have found is to turn bluetooth off and then on again on my Moto X. That always brings it back, a reboot of the 360 does not.

Well as I said in the OP, if I go into Android Wear, click Disconnect and then click Connect, it works. But there is absolutely no reason why it shouldn't auto-connect. If it disconnects, and I don't notice, the rest of the day I go without notifications until I realize the watch has disconnected. That's not how this should work.

Max_Pain said:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Click to expand...
Click to collapse
Hi, i have the same problem, my watch always disconect to my phone (moto x), and then the bluetooth system never start again. When I enter in setup ---- bluetooth---- the bluetooth switch doesn t turn on again until phone reboot.

this is so annoying. and it seems like there's a few people experiencing the same thing but nobody seems to have hit a solution. I have yet to come up with one. if I do, i'll post on here.

Same happens with mine. It just prompts me with a "connect" screen on my phone once in a while. After connecting 2-3 times, it won't appear until next time I turn off Bluetooth.

I get this problem about 2 times per day...running with a Note 2 running 4.4.2 stock but rooted....

Bluetooth Repeated Disconnects with Car

I just got my new civic 2016 EX-T (in sexy blue) 2 days ago, but I've yet to get my phone to work properly with it.
I'm using Jedi rom, and have no issues connecting with either of my other 2 bluetooth devices. (a speaker and a radio transmitter)
The issue is that the phone will connect for a couple seconds, then disconnect and repeat ad-nausium every thirty seconds.
I re-paired them and they connected for the whole ride, but then when I turned it on today they refused to stay connected again.
Any ideas?
P.S.
Are any good note 2 roms out based on 5.0 so I can get android auto?

AT&T Note 4 Edge Slow/Freezing/Randomly Re-booting After Marshmallow Upgrade

Hi there, I have a locked AT&T Samsung Galaxy Note 4 Edge (SM-N915A) that is experiencing issues after the Marshmallow upgrade (6.0.1). I have had the following issues:
--> phone freezes (will not wake after wallet is closed and then opened);
--> the phone will randomly re-boot;
--> if phone is awake, the response times have been very slow;
--> Issue seems to occur more often when charging
The only method to remedy the issue is to remove the battery and then power back on. I have wiped cache and factory reset the unit but still experience the same issues. I went to Samsung desk at Best Buy and they re-flashed the operating system but this did not fix the issue. I finally narrowed down the issue to the Samsung Gear application (I have the new Frontier Gear S3). When this application is not running the issue seems to disappear (although still testing). I am attempting to pinpoint whether NumberSync is causing the issue or the application itself. Has anyone else experienced this issue?
Update: while writing this email, my unit just re-booted when I woke it up
Any suggestions would be greatly appreciated....
Update to issue...
I attempted another factory reset. Again, once I installed the Samsung Gear application and proceeded to setup my Gear S3 wearable, the phone started to "act up". Details on setting up Frontier Gear S3...
--> Downloaded/Installed Samsung Gear application
--> Used "Connect to New Phone" to setup Gear S3
--> Setup and Activated NumberSync
After this process, phone response time was sluggish and then froze. I pulled the battery, and then uninstalled the Samsung Gear application, and the phone seemed to recover. After some careful thought, I performed a complete factory reset on my Gear S3 wearable (in lieu of using "Connect New Phone"), then, I re-installed the Samsung Gear application. The phone seemed to be functioning as normal. I proceeded to setup NumberSync and again, the phone was still functioning as normal for most of the day. In the evening, I setup the wearable (added back watch faces, setup S Health, added localized weather and setup notifications). The phone still seemed to be fine. I plugged the phone in to charge (fast charge) and left the phone alone. Came back several hours later and the phone had froze. I concluded that my issue is directly related to the Samsung Gear application although I am continuing to test.
UPDATE 4/5/2017 - After experiencing 2 weeks of freezing, slow response times, removing the battery, numerous re-boots and factory resets my phone finally died (would not power on). I finally succumbed to calling Samsung Customer Care. I sent my Note 4 in for servicing on March 29th. Here is the response: Problem found: NO POWER UP - IF/CHARGING PORT - FWT - LOW BATTERY (STBY) Solution: REPLACED PBA - REPLACED COMPONENT. I think this means they changed out the motherboard and also replaced my battery. My Note 4 is performing flawlessly thus far. The only issue I have is the timing of all of this....I started having problems directly after the Marshmallow (AT&T 6.0.1) upgrade. My wife and son have the same phone, bought at the same time, and are also having issues but not as profound as mine.

Maybe it has something to do with the notifications on the Gear? My phone was aggressively rebooting after a notification from Hangouts would arrive. I have the Gear Fit 2.
I was just about to give up on this phone today, but I'm hoping that removing the Gear app may stop the freezes.

Followup from earlier. Nope, removing the Gear app for me didn't fix my phone. I'm not getting reboots, but it is still freezing up. Sorry dude/ dudette. I think I'm going to have to bow out of the Note 4. It was a great phone for me.

Same happen today to my SM-N910A. It happened after half of a year successful run with 6.0.1.
Erasing cache and factory reset bring no results.
Unfortunately the phone looks slow even in recovery. Is it a hardware failure?

filon said:
Same happen today to my SM-N910A. It happened after half of a year successful run with 6.0.1.
Erasing cache and factory reset bring no results.
Unfortunately the phone looks slow even in recovery. Is it a hardware failure?
Click to expand...
Click to collapse
My issue turned out to be a HW and battery issue (as noted in my original post above (updated))

cswackha said:
My issue turned out to be a HW and battery issue (as noted in my original post above (updated))
Click to expand...
Click to collapse
I've been having the same issue for the past year after the update to 5 and i've researched and purchased 5 new batteries as that somewhat made the issue better but it freezes sometimes up to 10 times a day. currently i can't get it to actually boot. usually i can get it working but i'm so upset with theis phone. for the 1st year it was great. purchased dec of 2014 on the ATT Next plan. I think i have 1 more payment but there are no phones ATT offers that I like. I'm calling Samsung.

Samsung Gear S3 frontier connection problem

My previous phone Mate RS connects with the Samsung S3 perfectly and stays connected all the time. Every since I have switched to my Mate 20x (China Version 256gb), it wouldn't stay connected. I have to manually connect it from time to time. Anyone have the same problem?

jf1972 said:
My previous phone Mate RS connects with the Samsung S3 perfectly and stays connected all the time. Every since I have switched to my Mate 20x (China Version 256gb), it wouldn't stay connected. I have to manually connect it from time to time. Anyone have the same problem?
Click to expand...
Click to collapse
Can't use the trash can on the button in the bottom right it will auto disconnect. You also need to go and turn off battery optimization for all the gear stuff and it will stay connected but my gear's battery life is terrible these days.

I'm having the same issue

I don't know if you're seeing the same but for me the last update has fixed most things, my gear set now syncs and stays connected

Don't kill the gear app from memory and the watch will stay connected. Also disable power management for gear app.