Related
Hello All,
I have a strange issue with my phone which started during the night. My phone (I-9195) restarted by himself and then stuck on the GT-I9195 screen. After I restarted it the phone start normally but then it shows that earphones are connected which is not the case and after some time the phone restart again. I`m with a stock Rom JDQ39.I9195XXUBMJ7 please someone to give me an idea why this is happening.
bnight said:
Hello All,
I have a strange issue with my phone which started during the night. My phone (I-9195) restarted by himself and then stuck on the GT-I9195 screen. After I restarted it the phone start normally but then it shows that earphones are connected which is not the case and after some time the phone restart again. I`m with a stock Rom JDQ39.I9195XXUBMJ7 please someone to give me an idea why this is happening.
Click to expand...
Click to collapse
And the phone self restart on every 10-20 minutes !
So two issues earphones are not present but the icon for earphones connected is there and the phone self restart on every 20 minutes and don`t start after restart.
Have you tried
bnight said:
And the phone self restart on every 10-20 minutes !
So two issues earphones are not present but the icon for earphones connected is there and the phone self restart on every 20 minutes and don`t start after restart.
Click to expand...
Click to collapse
Have you tried to take the battery out and wait for at least 10 sec before putting it back in?
Another option is to "tease" the RAM and take out the battery while the phone is on. This should of coarse be a last resort.
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.
So over the past few days, have noticed that if I walk away from my phone (LG G3 Verizon rooted) my watch does not auto reconnect. Any ideas? It does reconnect after 2-3 mins, or if I disconnect/reconnect from Wear app. Never did this before. Always reconnected almost instantly when I got back within range of the phone.
Have you unpaired the watch and phone. Reboot and pair up? If you have what about unpaired then uninstall android wear, then reboot and start again?
Last resort would be a reset of the watch.
Sent from my Nexus 5 using Tapatalk
droidkevlar said:
So over the past few days, have noticed that if I walk away from my phone (LG G3 Verizon rooted) my watch does not auto reconnect. Any ideas? It does reconnect after 2-3 mins, or if I disconnect/reconnect from Wear app. Never did this before. Always reconnected almost instantly when I got back within range of the phone.
Click to expand...
Click to collapse
Try restarting the watch and turning off and on the bluetooth your phone. I noticed that it takes about a min to reconnect sometimes and restarting the watch and turning off/on the bluetooth on the phone helps.
I noticed the same thing, and it's indeed not very convenient...
I wonder if this may have something to do with the latest update that achieve a better battery management.
Maybe they increased the time between bluetooth connection attempts in case of connection loss, to avoid wasting precious battery life?
kpjimmy said:
Have you unpaired the watch and phone. Reboot and pair up? If you have what about unpaired then uninstall android wear, then reboot and start again?
Last resort would be a reset of the watch.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of this, minus doing a reset on the watch. If I cant figure out, this is what Ill be trying next.
JayRyu said:
Try restarting the watch and turning off and on the bluetooth your phone. I noticed that it takes about a min to reconnect sometimes and restarting the watch and turning off/on the bluetooth on the phone helps.
Click to expand...
Click to collapse
I have tried all of this, minus doing a reset on the watch. If I cant figure out, this is what Ill be trying next.
euroclie said:
I noticed the same thing, and it's indeed not very convenient...
I wonder if this may have something to do with the latest update that achieve a better battery management.
Maybe they increased the time between bluetooth connection attempts in case of connection loss, to avoid wasting precious battery life?
Click to expand...
Click to collapse
Thought this too, but it just happened out of the blue. It wasnt right after the update.
I just rem'd last night that there was an update to an xposed module I use, called Unbounce, Im wondering if this is the culprit. You wouldnt happen to have it installed too, would you? I am going to test disabling it and see if it resolves my issues. Will report back.
So just tested and it still takes a long time to reconnect. Next step will be wiping watch completely and seeing if it resolves the issue. Will try this over the next few days when I get some free time to really mess with it.
My device also does not seem to auto reconnect. A manual cycle of the connection status from the android wear app on the phone immediately reconnects it for me. I don't have the patience to wait and see if it has a timeout on reconnect but I can test if need be.
fwayfarer said:
My device also does not seem to auto reconnect. A manual cycle of the connection status from the android wear app on the phone immediately reconnects it for me. I don't have the patience to wait and see if it has a timeout on reconnect but I can test if need be.
Click to expand...
Click to collapse
Good to hear I am not the only one. Which phone do you have? Mine does reconnect, but takes 1-3mins. Im not using a stop watch, just looking at clock and watching the time before it reconnects.
Nexus 5 32gb. Ill do an intentional test and see if it reconnects eventually with a time out. I imagine as others have said it was set to a timeout to save battery.
fwayfarer said:
Nexus 5 32gb. Ill do an intentional test and see if it reconnects eventually with a time out. I imagine as others have said it was set to a timeout to save battery.
Click to expand...
Click to collapse
OK, Im on LG G3 Verizon rooted. Its just weird that either I didnt notice it after the update, or it happened shortly after the update. Either way, batt life has been a lot better, I just wanted to make sure something I did didnt screw it up.
And let us know about your test for the disconnect.
droidkevlar said:
I just rem'd last night that there was an update to an xposed module I use, called Unbounce, Im wondering if this is the culprit. You wouldnt happen to have it installed too, would you? I am going to test disabling it and see if it resolves my issues. Will report back.
Click to expand...
Click to collapse
FWIW I don't have Xposed installed (but a custom ROM on a i9502 Dual-SIM Samsung Galaxy S4, which might contain some Xposed stuff even though it's unlikeley).
I didn't notice the same reconnect delay today, so maybe this isn't a permanent phenomenon...
I have same issue with reconnecting after walking away. I have a Galaxy S5.
Walked upstairs and watch disconnected, got alert. Came back down and put phone in my pocket. Took three minutes to reconnect.
Bluetooth reconnect takes ages
Same issue with my 360. I have a xperia z2 and its taking a good 2-3 mins to recconect. Such a pain as this is really important to me and work.
Any ideas on if its a downloaded app or not?
Everyone's timeout is looking about equal. It was probably put in for battery savings.
Isn't this what we want? An immediate reconnect (admittedly what my gear live and neo do) would mean constant ping attempts while disconnected. This means battery. My 360 re-connects within 2-3 minutes which is fine by me.
LG g3, sprint, rooted, xposed
fwayfarer said:
Everyone's timeout is looking about equal. It was probably put in for battery savings.
Click to expand...
Click to collapse
robber said:
Isn't this what we want? An immediate reconnect (admittedly what my gear live and neo do) would mean constant ping attempts while disconnected. This means battery. My 360 re-connects within 2-3 minutes which is fine by me.
LG g3, sprint, rooted, xposed
Click to expand...
Click to collapse
Yep. Just wanted to make sure as it seemed to happen not right after the update. Thanks everyone.
Hi,
I've had this watch over a year now. Everything was working fine until probably last update or two. Now the watch just turns off randomly even when battery level is high. And sometimes it won't turn on unless its connected to the charging dock. I've tried deleted android wear, clearing cache, unpairing, factory resets, restarts. Nothing has worked, i've tried it close to 10 times now and just another factory reset this morning. Haven't been able to use the watch for like 2 months now. Its just a desk clock now. Please help.
Android Wear version - 1.3.0.2166028
Play Services = 7.8.99
Android OS = 5.1.1
is the watch actually shutting down like when you go into the screen and tell it to shut off or does it just go blank right away?
If the later then I hate to say it but it sounds like something inside the watch is broken. Perhaps a contact or solder point near or on the battery. Hard to say without sending it for service.
SirDigitalKnight said:
is the watch actually shutting down like when you go into the screen and tell it to shut off or does it just go blank right away?
If the later then I hate to say it but it sounds like something inside the watch is broken. Perhaps a contact or solder point near or on the battery. Hard to say without sending it for service.
Click to expand...
Click to collapse
It just goes blank. No notification at all. It's been on for 20 percent now. But I am sure it will turn off again. Maybe it's because it gets hot. I dunno.
bustanut666 said:
Hi,
I've had this watch over a year now. Everything was working fine until probably last update or two. Now the watch just turns off randomly even when battery level is high. And sometimes it won't turn on unless its connected to the charging dock. I've tried deleted android wear, clearing cache, unpairing, factory resets, restarts. Nothing has worked, i've tried it close to 10 times now and just another factory reset this morning. Haven't been able to use the watch for like 2 months now. Its just a desk clock now. Please help.
Android Wear version - 1.3.0.2166028
Play Services = 7.8.99
Android OS = 5.1.1
Click to expand...
Click to collapse
Did the watch suffer any kind of mechanical shock ?
Cst79 said:
Did the watch suffer any kind of mechanical shock ?
Click to expand...
Click to collapse
Not that I know of or anything very severe. I have pumped it on a wall before but that's it. Never dropped or anything. Just seemed like after the updates it when crazy. And I've tried almost every solution I've read on these forums.
So only turned off once yesterday which was good. This morning took it off dock and it didn't pair. Tried turning on/off bluetooth on phone no luck so I restarted watch. Then it says "android is starting". "App 1 of 12". Why does it do this sometimes? Does it alot. And it will not finish the process and boot up the watch unless it is docked. If wearing watch. It just shuts off.
bustanut666 said:
So only turned off once yesterday which was good. This morning took it off dock and it didn't pair. Tried turning on/off bluetooth on phone no luck so I restarted watch. Then it says "android is starting". "App 1 of 12". Why does it do this sometimes? Does it alot. And it will not finish the process and boot up the watch unless it is docked. If wearing watch. It just shuts off.
Click to expand...
Click to collapse
That sounds like it is trying to update or download the apps to the watch... which it sounds like you have 12 installed on your phone.
Have you tried deleting ALL the apps from you phone (only the 12 apps for the moto 360) and then uninstall Android wear and factory reset the moto 360 and then download Android wear to your phone and pair the 360 as a new watch and test it for a while and see how it works?
I have the same issue, watch shuts down while I am jogging and listening to Android Wear music from the watch throught Bluetooth. Watch shuts down around 75-80%. When I start it says: Loading Apps 1 out of 12... then shuts down (I assume its a safeguard mechanism for watch not to start without full battery to ensure all apps load completely).
When I wear the watch normally, it never goes off during the day, issue presents itself only when using Bluetooth headphones (perhaps the heating of BT transmitter forces the watch to malfunction and shut down)
ykazimir said:
I have the same issue, watch shuts down while I am jogging and listening to Android Wear music from the watch throught Bluetooth. Watch shuts down around 75-80%. When I start it says: Loading Apps 1 out of 12... then shuts down (I assume its a safeguard mechanism for watch not to start without full battery to ensure all apps load completely).
When I wear the watch normally, it never goes off during the day, issue presents itself only when using Bluetooth headphones (perhaps the heating of BT transmitter forces the watch to malfunction and shut down)
Click to expand...
Click to collapse
I never connect the bluetooth to listen to music. It just shuts down.
Maybe you are doing something that causes it to overheat. Do you leave it on for prolonged periods of time?
Been having this same issue. The Moto 360 powers off and when I press the power button to turn it back on I see the splash "M" image then it turns off. The only way to get it to stay on is to put it back on the dock and when it turns on it says shows the updating apps screen. Any fixes?
I haven't figured out fix. Because of this I barely use my watch anymore. Sucks.
Sent from my SM-G900V using Tapatalk
yep, haven't used my 360 in 6 months because of this problem. it's a shame really. my warranty went out like a week ago too :/
Same thing has been happening to me as well. Not doing anything on the watch, it just goes into sleep of death and I have to put it back on the charger. Battery level is usually above 60 or 70 %.
Same issue!!!
Guys even I had same issue, my watch will heat up suddenly and turns off. I've to put it in dock to turn it on again. This issue never occurred after stopped using some of the new watch faces which allows dim option. I'm currently using some of the old watch faces which are working fine. May be these new watch faces are not working fine with latest update. Now I don't face any problem and battery life is also great.
Try this solution and let me know.
Watch faces has nothing to do with it. My watch will not fully boot into android wear unless it's on the dock no matter which watch face I am using. Even the minimal face.
Sent from my SM-G900V using Tapatalk
Anybody able to find a fix? This is so annoying
I'm having the same problem. I purchased a used Moto 360 off eBay for $120 and it turns off randomly even when the battery is pretty high for example it just turned off randomly at 80%. Then when I try to turn it on it boots up till the M logo or sometimes to the colorful part but then turns off again. It also only turns back on by putting it on the charging dock. Also it shows the Installing App 1 of 1 at startup and then suddenly shuts down again. I am extremely annoyed and frustrated because of this as I spend $120 on this watch and now I get this which makes it unusable and a waste of money. Please tell me guys if any of you find a solution!
Unfortuanately, mine is doing the exact same thing. I thought I had it working again, but as soon as I tried to give GPS permission to Google Fit (wouldn't run without it), it spun there and just went black. I literally just took the watch off the charger, so it isn't that. Now, if I hold the power button or press it multiple times, it tries to boot up, and will stop before it even gets past the normal Android boot animation. Sometimes, it won't even get past the Motorola boot animation. Now, when I put it on the charger, it seems to load perfectly fine, and even gets past the 'Starting apps' phase. Again, once it loads back up, my watch shows +90% battery. I've tried a factory reset, unpair/repair, and still no go.
Found a pattern
My app does the same but i have at least a pattern when it happens. It seems like it is as soon as there has been an update either in Android ware app or in soem app that has an wear application.
Having issues with factory reset on my watch. When I go to the unpair option and say yes to factory reset, it acts like it's going to do the reset but then just kind of shuts off or goes unresponsive. Throw it back on the charger and it boots up like it was just powered off. What am I missing?
agentfazexx said:
Having issues with factory reset on my watch. When I go to the unpair option and say yes to factory reset, it acts like it's going to do the reset but then just kind of shuts off or goes unresponsive. Throw it back on the charger and it boots up like it was just powered off. What am I missing?
Click to expand...
Click to collapse
I have the same problem too!
I've tried the reset multiple times, battery is always at 100% when trying. Getting very frustrating. Any ideas? Google has not been helpful.
Just says "Resetting, please wait" then "Restarting" then goes black until I dock it again, at which point it boots back up like all I did was reboot it.
Any help at all here?
I was having this problem... so I fully charged it and while it was turning off, I threw it on the charge also and it worked..
gd6noob said:
I was having this problem... so I fully charged it and while it was turning off, I threw it on the charge also and it worked..
Click to expand...
Click to collapse
None of that is working for me. It just turns off when trying to reset while at 100% battery.
I think this watch is just broken. I had it off the charger and when I re-docked it and it turned on with 54% battery. 5 mins later, it was at 100%.
I have the exact same issue :/
Still unable to factory reset this..
So, finally got this reset to happen...now ~30 minutes after the initial setup has finished, the watch battery is dying while on the charger. Thoughts?
It's (kinda) charging now. I just have no watch faces to pick from. Not really syncing.
I had the same problem - after multiple tries it worked.
After several days of waiting, I still have no ability to pick watch faces from the Android Wear app. Thoughts?
Moto 360 first gen. reset
The trick is to un-pair and reset it while is charging. good luck!
RD