Hello , I updated my Xperia Z3 to version 6.0.1 , and from that moment my SW2 restarts every moment. Until now , half a year it happened maybe 2 times. Is it Z3 fault or SW2 is broken ?
matejank said:
Hello , I updated my Xperia Z3 to version 6.0.1 , and from that moment my SW2 restarts every moment. Until now , half a year it happened maybe 2 times. Is it Z3 fault or SW2 is broken ?
Click to expand...
Click to collapse
Right now, I have Galaxy S7 with Android 6.0.1. My SW2 works very well and I'm really surprised. Because few month ago I had Galaxy S6 with Android 5.0.x and SW2 wasn't working with S6. I had the same problems like you. From that moment Sony made 1-2 updates for their app (Sony Connect), so I suppose they fixed the issue.
But I have no idea how to help you. I'm know it's really annoying. Maybe you can try older version of Sony Connect and SW2 app (customized version from XDA).
With my xperia Z5C android 6.0 my SW2 restart and need to be apaired again few time at day so unusable.
So I installed the SW2 with my Galaxy S4 android 5.01 and since, no issue. So I think is yet an issue with Sony Android 6. Many issue on bluetooth with Sony phones
I have also some paired issue with the Z5C and my Zenwatch2. The watch do not restart but ask for acknowledge a new pairing code regularly.
Its fine on my z3c 6.0.1 , try clean reflash your z3c with flastool
Sent from my D5833 using XDA-Developers mobile app
Related
sudden blackout onmy new xperia z when there is phone calls its a rare issue happens sometime...i the 4.3 version buggy its a 5 day old zl and it happened twice after 4.3 update
hey
bhavstech said:
sudden blackout onmy new xperia z when there is phone calls its a rare issue happens sometime...i the 4.3 version buggy its a 5 day old zl and it happened twice after 4.3 update
Click to expand...
Click to collapse
same issue ! no reply 5 days old zl updated 4.3 !!! you got the fix?
zeeman11 said:
same issue ! no reply 5 days old zl updated 4.3 !!! you got the fix?
Click to expand...
Click to collapse
no it suddenly stopped after i accidently did factory reset
I tried to post in QandA section but for some reason it would not let me post.
Since the lollipop Roms don't support Bluetooth LE do they still pair with android wear devices? Also, is there any decreased functionality?
Thanks
hal3146 said:
I tried to post in QandA section but for some reason it would not let me post.
Since the lollipop Roms don't support Bluetooth LE do they still pair with android wear devices? Also, is there any decreased functionality?
Thanks
Click to expand...
Click to collapse
I tried out for a brief moment, the AICP 12/18 build, and my G Watch connected just fine too it. Can't say for the other Roms though..
I've been running CM 12 since I got my Moto 360 2 weeks ago with no issues. It connects and pairs fine. Everything works as it should.
qbanlinxx said:
I tried out for a brief moment, the AICP 12/18 build, and my G Watch connected just fine too it. Can't say for the other Roms though..
Click to expand...
Click to collapse
also on CM12 and pairs with LG G watch no issues
It works with my moto360 and CM12
I just got an Asus Zenwatch. I didn't have any issues with lollipop initially but after flashing a different ROM I had issues pairing. I had to factory reset the watch to get it to pair again.
I also read that BLE wasn't working on lollipop ROMs, which makes me question if it really is connecting on low energy. Does anyone know if this has been fixed with newer lollipop builds?
Sent from my LG-D851 using XDA Free mobile app
I can tell you I had paired the moto 360 and HTC one running lollipop with no issues for about 2 weeks.
I've had my G Watch R randomly disconnect all the time on every lollipop rom I've tried. Haven't had a single issue on stock LG or CM11. It connects and pairs fine and randomly shows the disconnected icon on the watch face even though the Android Wear app says its connected. Can't even reconnect without rebooting the phone or turning bluetooth off and on again. Only happens on lolipop roms though... dont know why.
jesusfranco said:
I've had my G Watch R randomly disconnect all the time on every lollipop rom I've tried. Haven't had a single issue on stock LG or CM11. It connects and pairs fine and randomly shows the disconnected icon on the watch face even though the Android Wear app says its connected. Can't even reconnect without rebooting the phone or turning bluetooth off and on again. Only happens on lolipop roms though... dont know why.
Click to expand...
Click to collapse
I've have a Moto360 connected to my LG G3 d851 that has the same issue.
I have only used LP ROMs (Euphoria as my DD), but have yet to find one that doesn't have this issue. Disconnects up to 15-30 times a day with "Bluetooth Sharing" fometimes showing a FC. I even managed to reset my BT right after a FC and got a 'Green Screen'.. (Like a BSOD).. my guess is the unofficial BT drivers pulled from KK don't play well with LP/ART.
(FC: force close, KK: Kit Kat, LP: lollipop, BT: Bluetooth)
Wish there was a way to port the bluetooth driver from the leaked LG lolipop build for the d855
This is still an issue.
I switched back to KK thinking the issue would be solved in a few months. To my surprise, it has not been addressed. I specifically tired the Illusion Lollipop build, but no bueno.
Are there any Lollipop ROMs free of the connectivity issue?
No. Until we get official 5.0 (or more specific, the source) we won't have the specific BT stack for our device. Everything right now is working hard to get it working, but it's kinda like working blind with a deaf partner.
Sent from my LG-D851 using Tapatalk
BL LE
I've got the Sony Smartband (SWR10) and I've had trouble trying to pair it with my phone. It just won't.
I've tried multiple roms and still got the problem. The roms i tried pairing the band with: RR, DU, LiquidSmooth and Bliss Pop
I factory reset my Moto360 after clean wiping my phone (CM12.1 Nexus 6)... Now it won't stay connected via Bluetooth to my watch. Any idea how to fix this?
Anyone?
You need to reset the watch and re-pair it to the phone.
Sent from my SAMSUNG-SM-N910A using Tapatalk
frellingfrakker said:
You need to reset the watch and re-pair it to the phone.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Did that 3-4 times. Today though it seems more stable.
Looks like Android Wear keeps crashing. That's the cause of all this, even after several resets.
Maybe CM 12.1 causes the problems?
Verstuurd vanaf mijn Nexus 9 met Tapatalk
giancarlo_f said:
Maybe CM 12.1 causes the problems?
Verstuurd vanaf mijn Nexus 9 met Tapatalk
Click to expand...
Click to collapse
Others on 12.1 have not had these issues.
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
karcher01 said:
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
Click to expand...
Click to collapse
I haven't gotten Wear 5.1.1 yet unfortunately. Hopefully soon. 5.0.2 is BUGGY! Especially with battery drain during app sync.
i'm having the same issue here running android wear 5 . and cm12.
6 reset so far today . it keep disconnecting and then after on the phone it says connecting... which does not goes away until you reset the watch .
It seems to be a software issue . Android wear is still buggy
karcher01 said:
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
Click to expand...
Click to collapse
I give up. I tested this morning with a new phone (ASus Padfone Inifinity). Same problem. I send my watch back for a refund and wait for anoter one. Back to my G Watch.
Edit : My G watch is just receving the 5.1.1 update. Good news of the day after this 4 days in Hell with Moto 360
karcher01 said:
I give up. I tested this morning with a new phone (ASus Padfone Inifinity). Same problem. I send my watch back for a refund and wait for anoter one. Back to my G Watch.
Edit : My G watch is just receving the 5.1.1 update. Good news of the day after this 4 days in Hell with Moto 360
Click to expand...
Click to collapse
The Moto360 should get 5.1.1 soon... Returning it was a bit excessive IMHO.
Moto 360 5.0.2
agentfazexx said:
The Moto360 should get 5.1.1 soon... Returning it was a bit excessive IMHO.
Click to expand...
Click to collapse
I am receiving the same disconnect issues with my Moto 360 running 5.0.2. It happens every ~5 minutes.
dvrose said:
I am receiving the same disconnect issues with my Moto 360 running 5.0.2. It happens every ~5 minutes.
Click to expand...
Click to collapse
It should eventually stop. It did it for me after posting this for hours after resetting.
agentfazexx said:
I factory reset my Moto360 after clean wiping my phone (CM12.1 Nexus 6)... Now it won't stay connected via Bluetooth to my watch. Any idea how to fix this?
Click to expand...
Click to collapse
It's a CM issue. When I had my S4, I had the same problem that you're describing on both CM12 and CM12.1, both official and unofficial builds. Installing a google play edition or stock-based rom solved the problem. I just got a Droid Turbo, and it also has no problems with the watch. After doing some reading, it seems like there is a problem with the way that CM12 and CM12.1 handles low energy bluetooth devices. Try another rom.
TheSt33v said:
It's a CM issue. When I had my S4, I had the same problem that you're describing on both CM12 and CM12.1, both official and unofficial builds. Installing a google play edition or stock-based rom solved the problem. I just got a Droid Turbo, and it also has no problems with the watch. After doing some reading, it seems like there is a problem with the way the CM12 and CM12.1 handle low energy bluetooth devices. Try another rom.
Click to expand...
Click to collapse
I got flamed in the thread for blaming the ROM.
agentfazexx said:
I got flamed in the thread for blaming the ROM.
Click to expand...
Click to collapse
Well whoever flamed you is stupid. It's a well known problem, at least with the S4. Go to any CM12 or 12.1 thread on the Verizon GS4 forum and search for Bluetooth. I guarantee at least 10 posts asking whether or not it is fixed in the latest build.
TheSt33v said:
Well whoever flamed you is stupid. It's a well known problem, at least with the S4. Go to any CM12 or 12.1 thread on the Verizon GS4 forum and search for Bluetooth. I guarantee at least 10 posts asking whether or not it is fixed in the latest build.
Click to expand...
Click to collapse
Whenever I blame anything on CM that worked fine on stock, they all flame me.
Those that had this issue.. Were you on CM or not?
Yep...... It's a CM-bug on my S4 too. I installed echo-rom (tw based based rom) and it worked perfect .
Verstuurd vanaf mijn Nexus 9 met Tapatalk
giancarlo_f said:
Yep...... It's a CM-bug on my S4 too. I installed echo-rom (tw based based rom) and it worked perfect .
Verstuurd vanaf mijn Nexus 9 met Tapatalk
Click to expand...
Click to collapse
This happens to me on my stock Nexus 5, so I doubt it's a ROM issue. Most likely it's an issue with the firmware on the 360, or maybe the hardware. Hopefully 5.1.1 comes before my 30 days is up so I can decide whether or not to keep the 360, kind of sick of resetting the watch.
Hi all!
So I've just swapped my Sony smartwatch 3 for a moto 360 and have just set it up as new and downloaded a few new watch Faces (still have the old ones on my watch too from when I had them on the SW3) but for some reason even after a system reset none of them are appearing on the watch. All my notifications are appearing however.
Anyone know what is causing this? I haven't updated to the latest wear version on the watch due to the battery issues which forced me to sell my SW3 with 5.1.1 could this be the issue?
Thanks
Sent from my OnePlusOne
Okay so fixed the above issue with a software update to 5.0.2. Wondering if it's better to stay on this version or go to 5.1.1...What's the best for this watch?
Sent from my OnePlusOne
i feel 5.1.1 is better
sheppy101 said:
Okay so fixed the above issue with a software update to 5.0.2. Wondering if it's better to stay on this version or go to 5.1.1...What's the best for this watch?
Sent from my OnePlusOne
Click to expand...
Click to collapse
I get better battery backup in 5.1.1 (with tilt to wake ON, ambient display off), so I would suggest you to update and give a reset after it. (few people have battery issues with 5.1.1)
Cheers! Updated last night and doesn't seem to be toooo bad atm! No worse than 5.0.2 anyway. Still probably need time to settle though aswell I guess.
Was worried as the 5.1.1 update on the Sony watch made the battery so unpredictable!
Sent from my OnePlusOne
Hello experts,
Since some weeks when I receive a phone call my SW3 keeps vibrating for 8 or 9 seconds even after I answerd (the phone is a Sony Z3c).
That's really very annoying...
I tried to full reset and resynch, and even reinstalled all apps, but the problem remains.
Suggesions?
Thanks
freewing70 said:
Hello experts,
Since some weeks when I receive a phone call my SW3 keeps vibrating for 8 or 9 seconds even after I answerd (the phone is a Sony Z3c).
That's really very annoying...
I tried to full reset and resynch, and even reinstalled all apps, but the problem remains.
Suggesions?
Thanks
Click to expand...
Click to collapse
I'd suggest you to send it to Sony Service. This is not a normal behavior for our watch. I'm also using Xperia Z3C (stock 5.1.1) and this watch (now stock 6.0.1, AW 1.4) and no such thing happened ever.
romcio47 said:
I'd suggest you to send it to Sony Service. This is not a normal behavior for our watch. I'm also using Xperia Z3C (stock 5.1.1) and this watch (now stock 6.0.1, AW 1.4) and no such thing happened ever.
Click to expand...
Click to collapse
Thanks for answering.
The problem is that my SW3 is a gift I received: it was bought in UK and I live in Italy.
Very difficulto to get an economical sustainable assistence.
I can't understand the logic, but... since I changed in the phone in settings/notifications/apps with access to notifications/ DISABLE Android Wear
then now everything looks to worl fine.
(I know it looks wired, but... now it seems to work)
does this make sense?
...any more suggestion from experts and/or Sony Tech Sup?
freewing70 said:
...any more suggestion from experts and/or Sony Tech Sup?
Click to expand...
Click to collapse
@freewing70
Repair/ upgrade the firmware version in the Smartwatch using PC companion and try pairing with your phone again. Other option would be to goto recovery and do a factory reset in the watch. You can search to find the steps to get to recovery in the watch.
gauthamsv said:
@freewing70
Repair/ upgrade the firmware version in the Smartwatch using PC companion and try pairing with your phone again. Other option would be to goto recovery and do a factory reset in the watch. You can search to find the steps to get to recovery in the watch.
Click to expand...
Click to collapse
Alredy done: nothig changed.
I do believ my SW3 has some probs.
Thanks for answering