[Help] Wear Os disconnect problem. - Wear OS Q&A, Help & Troubleshooting

Hey, guys.
I've trouble with my smartwatch "Ticwatch E2" and think it's occur because wear os problem.
My watch is disconnect from bluetooth or even wifi randomly.
I've tried restart ,reset watch or reinstall latest wear os on my phone (Galasy S9) but problem still occur.
I've noticed this problem occur when I've enter game or open many apps on my phone. (I suggest it's battery saving feature on android oreo) Could it be the reason? If so, How could I shut it down even its drain my battery? (I've checked my app list and it has already shown "exemp")
Anyway, I've searched for any solution but have not found permanent solution yet.
Could anyone can help me for this problem?
Thank you for every comments

You're not alone, I have tried everything, I even flashed Lineage OS 16 on my Mi 5s Plus, this is supposed to fix that issue but no change I have a Moto 360 Gen. 2.

Help!
Hy, I have redmi note 7, it is not pairing with my smart watch (ticwatch e2), my watch is pairing with other cellphones like ( iPhone and Motorola) but not with xiaomi redmi phones I tried to pair it with redmi note 4 as well, kindly look into this

markus_mark said:
Hey, guys.
I've trouble with my smartwatch "Ticwatch E2" and think it's occur because wear os problem.
My watch is disconnect from bluetooth or even wifi randomly.
I've tried restart ,reset watch or reinstall latest wear os on my phone (Galasy S9) but problem still occur.
I've noticed this problem occur when I've enter game or open many apps on my phone. (I suggest it's battery saving feature on android oreo) Could it be the reason? If so, How could I shut it down even its drain my battery? (I've checked my app list and it has already shown "exemp")
Anyway, I've searched for any solution but have not found permanent solution yet.
Could anyone can help me for this problem?
Thank you for every comments
Click to expand...
Click to collapse
Samsung is getting worse after pie update. The aggresive battery saver kill almost everything. Follow the instruction on dontkillmyapp for S9. Hopes thi helps
Cloos said:
You're not alone, I have tried everything, I even flashed Lineage OS 16 on my Mi 5s Plus, this is supposed to fix that issue but no change I have a Moto 360 Gen. 2.
Click to expand...
Click to collapse
Does your disconnection also happen when opening some app? If yes, can you try to repeat if that is reproduceable consistently?
waliwasti said:
Hy, I have redmi note 7, it is not pairing with my smart watch (ticwatch e2), my watch is pairing with other cellphones like ( iPhone and Motorola) but not with xiaomi redmi phones I tried to pair it with redmi note 4 as well, kindly look into this
Click to expand...
Click to collapse
What is the ROM at Redmi Note 7 or 4? If you are using custom ROM, there might some extra restriction preventing it from pairing. Example is LineageOS privacy guard, if this is enabled for the wear os app, you can't pair it properly. You have to exclude it. I use RR pie, which has LOS privacy guard too, have no problem with pairing, since I exclude it.

Related

[Q] CyanogenMod + Android Wear

Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
sebastiaann said:
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
Click to expand...
Click to collapse
So far i know it works
Sent from my LG-D855 using XDA Free mobile app
I have an S4, and I haven't gotten mine to work on CM 11. I mean it does, but not very well. Gonna switch to a TW rom tonight.
S4 running CM11 and no issues with my LG g watch. Everything comes through with no disconnects.
Sent from my GT-I9505 using XDA Free mobile app
sebastiaann said:
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
Click to expand...
Click to collapse
I'm using CM 11 (4.4.4) on a S4 with Android Wear. No issues that I can see so far.
On Nexus 5, anything other than stock doesn't work well. Watch disconnects too often to be usable (bluetooth stack is dodgy on aosp or CM).
The fix is to flash Elemental kernel. Problem solved. This kernel is available for both aosp and CM.
Even in stock rom, if you flash another kernel, like franco kernel, the watch becomes unusable.
Again, the fix is to flash Elemental, with gives you the added bonus of enabling screen calibration for nice poping colors.
It took me time to discover all this. And frustration.
lost network connection
Hello I installed cm 10.2 through flash recovery. Onti my galaxy ace 2GT I8160 was gingerbread 2.3.6
Now its team conja jls361 if ive looked in the rite plce i still have iemi number and can recieve messages
But when i try and send or call it say no network ive been on to 3 my provider and they say its the phone
Please could you help with thi ive read it happens alot with this release of cm.. Would installing cm 11 sort it out im a newbie to being root ive already soft bricked it once so can see it being a bumpy ride so all the help i can get the better thank you
Also I looked at the build list and the radio and boitloader are unknown the biitloader has been like that when i got the phine that's bootloader not biitloader or bout loader dam key pad lol
My kernal is a i8160xxlk8 or it was I dunno if it still is
Connecting, running sync loop
Latoc said:
On Nexus 5, anything other than stock doesn't work well. Watch disconnects too often to be usable (bluetooth stack is dodgy on aosp or CM).
The fix is to flash Elemental kernel. Problem solved. This kernel is available for both aosp and CM.
Even in stock rom, if you flash another kernel, like franco kernel, the watch becomes unusable.
Again, the fix is to flash Elemental, with gives you the added bonus of enabling screen calibration for nice poping colors.
It took me time to discover all this. And frustration.
Click to expand...
Click to collapse
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Garrett 77 said:
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Click to expand...
Click to collapse
I don't know about s3, but you should try a few kernels and see what works...
FIXED
Latoc said:
I don't know about s3, but you should try a few kernels and see what works...
Click to expand...
Click to collapse
Well,
I tried a different kernel and still same issue. I flashed a TouchWiz based rom and it WORKED. Shows "connected". Battery life on moto 360 also vastly improved. Went from dead at 3:30 PM to 45% at same time!
I'm on DarkCM(11) for the xperia z1 and can't get it to work either.
Tested on my brothers stock xperia and that worked just fine. Il try downgrading to stock as well. :'(
If anyone gets CM on the z1 running with android wear please let me know.
I have a Oneplus One CM 11S works great on my old Gear Live and my new Sony Smartwatch 3
I read that MOTO 360 has (had) issues ?? Maybe the watch not the phones OS
Hi. My first post here and very New to all this. I have Samsung S4 with cm11 just got an Samsung galaxy gear2 neo and now i have to figure out how to get it to work with cm11 ? Can some body help
TechieInAK said:
I'm using CM 11 (4.4.4) on a S4 with Android Wear. No issues that I can see so far.
Click to expand...
Click to collapse
Sorry for bringing up an old post. I wanted to check in on your Android Wear connection to CM ROMs. I have a Sprint S4 (jfltespr) running CM12. I will be getting a LG G Watch R in a few days but someone else on our ROM thread was having issues with his Moto 360 and the CM12 ROM. Have you experienced any issues not connection or remaining in a sync loop?
Has anyone else experienced Android Wear issues with CM 11 or CM 12 on S4 phones? Particularly jfltespr?
Cant speak for the S4 but my LG G3 has had nothing but issues with my G Watch R since I flashed CM12. I reverted back to CM11 (recent build) and its working great, never disconnects. With CM12 it would disconnect at least 10-20 times a day its unusable.
I just installed the Google Play Edition Lollipop on my GS4 and it paired perfectly with my ASUS ZenWatch. Lollipop AOSP is AMAZING and i am so stoked it works so great!
Garrett 77 said:
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Click to expand...
Click to collapse
"Connecting, running sync loop" is just a different message for the same thing - it is activated on some ROMs(?) apparently when you have Developer mode enabled. But it works the same, and this message in itself doesn't indicate there should be any battery drain.
Of course something in the ROM might be causing this problem - a logcat from the watch would help in that case, but my guess is you just need to let everything install, settle down and then reboot both devices, and the drain will be gone...
My Zenwatch works perfectly with my Oneplus One running the latest CM11S. Having bluetooth on all the time does drain a bit more battery, but that's it.
I am having an issue with google wear (zenwatch) completing some tasks:
It fails to launch a phone call from google wear (my watch simply says "try again using your phone")
It fails to launch google play for music (it gives the same error as above)
Setting reminders using google keep (same error)
Text messages sent from android wear are NOT working.
Starting navigation on my watch using voice commands works.
Other basic apps appear to be working as well.
So far I've only noticed the above listed (maybe a few others) google apps and dialer that fail to launch when initiated from the watch, I have tried another dialer to see if that was the issue.
Anyone have any suggestions or insight on what I might be able to do in order to get google wear working 100% with this ROM?
Any help is greatly appreciated.
Mine works well
I have OnePlus One with CM11 and everything works quite well so far with my G Watch R

Lollipop issues with Android Wear

I gather many people are having connection issues with their Android Wear devices.
Is this just a Note 3 issue?
Has anyone managed to get a stable connection using Lollipop?
Yes, my Note 3 with Lollipop (tested many ROMs, even the Note 4 ports) has this issue, and it's not only with Android Wear, but with several other Bluetooth LE devices. I've heard mixed explanations: some say it's something with Lollipop itself, affecting many phones (unless the manufacturer added patches to solve the issue), and Google solved it with Lollipop 5.1; others say it's something only with Samsung's Lollipop ROMs. The latter may be true, as @civato apparently solved the issue tweaking the kernel.
Some people say their phones don't have this issue, but I suspect it's because they haven't put their BTLE devices under the failing scenarios. I have a very easy test case:
1) Pair your Android Wear watch with your phone, using the Android Wear app. Make sure the watch is communicating with the phone.
2) Create a situation where your watch loses connection with your phone (e.g. walk away with the watch, put it in a Faraday cage etc.). But make sure it stays that way for some time, say 10-30 minutes (sometimes it happens as soon as it's out of range).
3) Notice that even though the watch is disconnected (the "no cloud" icon is shown), the Android Wear app on the phone will show it as "connected". Now even if you bring the watch close to the phone again, it will not reconnect automatically.
The same thing happens with other BTLE devices. Other symptoms include frequently disconnects / reconnects, even when the device is in range.
Mine has paired but refuses to connect now. I'll try Civ kernel.
Is there a Lollipop Civ kernel lol
Some problem here with my Sony Smartwatch. The new XEO Update don't fix the Bluetooth problems complete. Is any fix released to fix the Bluetooth Connection problems?
I had all sorts of problems on both the leaked Lollipop and the official Lollipop. It was driving me insane with its constant disconnections/reconnections and then just disconnecting until Bluetooth was cycled. It made the watch useless!!!
I then tried Dark Lords N4 port (v1.5). Boom! All working perfectly. No more issues at all and reconnects if i move out of range seamlessly.
Same problem, Note 3 XEO with Sony SW3. So maybe for now there is only way - root with knox 0x1 and N4 port ROM...
Had a few issues after getting Lollipop but nothing compared to the issues I got when Android Wear updated (on Friday I think it was).
My Moto 360 just wasn't wanting to connect, tried rebooting phone, then the watch, but didn't help. In the end I factory rest my watch and its been fine since.
Vince
Yep, bluetooth all over the shop...Headset and Moto 360.
I also have a lot of problems with Sony SW3 and Note 3. Not only I have inconstant BT connection, but also weird management of incoming phone calls: watch notifies phone calls that appear on the teleohone only 3 or 4 seconds later (that's a huge time).
Anaother issue: I have also tried to decline a phone call with the Smartwatch but the telephone went on ringing.
Inviato dal mio SM-N9005 utilizzando Tapatalk

Android Wear issue with Android 6.0

I updated my OnePlus One to Android 6.0 and I've encoutered an issue with the two ROMs I tried (Ressurection Remix and AICP).
When I want to pair my watch, the app on the phone freezes, and the only thing I can do is forcing the reboot by pushing the on/off button during 10 seconds.
So my watch is unusable as long as Wear app won't work properly.
Has anyone encoutered this issue ?
Thanks.
Seosamh said:
I updated my OnePlus One to Android 6.0 and I've encoutered an issue with the two ROMs I tried (Ressurection Remix and AICP).
When I want to pair my watch, the app on the phone freezes, and the only thing I can do is forcing the reboot by pushing the on/off button during 10 seconds.
So my watch is unusable as long as Wear app won't work properly.
Has anyone encoutered this issue ?
Thanks.
Click to expand...
Click to collapse
It's a ROM problem, android wear works great with marshmallow on stock android.

Android Auto full of bugs. Any solutions?

Hi,
first of all, I love my Mi 9t. But I'm using android auto everyday and it is still full of bugs. First to paint a picture of my setup:
-Mi 9t Global 11.0.6.0
-Car: Skoda Fabia 2019, tried different USB Cables, everything works perfect with a Samsung Galaxy S9
List of Bugs:
1. Crashing of Media apps after disconnecting Android Auto
After disconnecting Android Auto the active media app crashes. I have to completly restart the app. Doesn't matter if using a podcast app like "antenna pod" or "podcast addicted" or "sportify". All of them are crashing.
2. Can not start media apps inside Android Auto
If the phone is connected to a car I'm not able to start any media app by using the cars display. There is just a message saying that the app isn't avaible at the moment. I have to pickup the phone and start the app directly on the phone.
3. Spontaneous crashes of Android Auto
Sometimes Android Auto just crashes out of nowhere. It automatically restarts after a few seconds, but after that I have to restart the media app by picking up the phone. (see bug number 2 and 1). It happens more frequently during calls.
4. Android Auto is lagy
It's not a bug, but in comparision to the Samsung Galaxy S9 Android Auto is a bit more lagy. It's not unusable but every command needs a few more moments then on the galaxy S9.
I tried different things to solve these problems. Using different usb cables, trying different media apps, changing the energy saving settings. Nothing helps so far.
These bugs are very annoying, therefore I thinking about using a custom rom or switchting to another brand. I got my Mi9t for a year now and these bugs are still not fixed. Some of them can lead to dangerous situations, because I have to pickup the phone during driving.
Does anybody having any ideas what else I can try. I don't want to do a factory reset now, because all the work I have to do setup the phone again. Does anybody else have similar problems?
Thank you all
Sorry, I am using Android Auto with Havoc 3.6 in an Audi Q3 and I don't have any of the issues. Works nice, no lag or crashes.
I even use AA Mirrow to get the TomTom app on my car's screen. Works most of the time as well.
I know this is not helpful, but just saying it's not the phone`s fault.
Thank you for your help. Now I have at least a recommendation for another rom I can try.
viper2035 said:
Thank you for your help. Now I have at least a recommendation for another rom I can try.
Click to expand...
Click to collapse
If you are going to try another ROM then you need to backup your data.
I would suggest you try the xiaomi.eu MIUI 12.1 weekly ROM. I have been using it for well over a month now and it is relatively stable, almost completely ad-free, and it also includes the latest security updates for Android 10.
update firmware of your car's multimedia. I use AA everyday with lineage, but I have had miltiple ROMs without an issue

Quick Charge & Discharge

Hello,I am currently using redmi note 7. 3/32 gb variant and using pixel experience latest update & magisk installed.from past 2 days i am facing very quick charging and quick discharging issue. Also when i am opening some apps like facebook or youtube for example i am facing automatic restarts.i am not able to use my mobile.
Everytime when there is an incoming call it restarts and i am not able to figure out who is calling me.I tried restarting many times,Tried resetting my mobile and also clean install old version of pixel experience and also clean flashing latest pixel experience rom but no use. Should i go back to stock rom ? Or can it be a battery issue? I bought this phone on may 2019 so just 1 year had been completed.
UP. same issue here . Did you find a solution already ts?

Categories

Resources