Hello everyone,
A big thanks in advance (and after, no worries) if you can help.
I have a nexus 6, CM13 and all it's fine but few weeks ago my bluetooth started to act a little strange by itself : it's turn off, disconnect the headset and turn on and reconnect the headset.
I have made test this weekend and I don't see any pattern.
I desactivate all the authorization for all the apps and no succes. I deinstall lot of apps but nothing.
I have the habit of listenning audio book when running or fitness so to have to relaunch the play during activity is quite boring.
If you have any idea or if you need some log, please ask!
You're not alone. I and many others are having the same problem with no resolution yet. I even bought a new headset a couple months ago, thinking my headset was going bad, but that didn't help.
I saw that. I find a lot of thread on the net about this problem. Various rom, various phone and no solution.
Sometimes they tried to do factory reset but with no success.
And I have two headset (one for the sport and one for the rest) so I already exclude the headset.
BT issues are really nothing new with CM roms. They have had them for years and never fixed them. This is why more and more are no longer using their code. Many are completely dropping all their code with the 7.0 update.
Your best bet is to troubleshoot it yourself. The first thing you should have done is pull a logcat.
JimSmith94 said:
You're not alone. I and many others are having the same problem with no resolution yet. I even bought a new headset a couple months ago, thinking my headset was going bad, but that didn't help.
Click to expand...
Click to collapse
I should have mentioned that I'm not on CM, but am having the same problems on stock rooted 6.0.1 with the August security update.
JimSmith94 said:
I should have mentioned that I'm not on CM, but am having the same problems on stock rooted 6.0.1 with the August security update.
Click to expand...
Click to collapse
This normally turns out to be a kernel issue somewhere. As you are on stock then I would get a logcat. At worst case it maybe a hardware issue. A log will help you determine where the issue is.
Same problem here. For months having this annoying issue.
I'm also on stock rom, and this is getting worse everyday. I am now on Nougat beta participating in the preview with the stock rom and the problem is still there.
I tried several fixes and resets, wipes, etc. with no success. I am very close to throw it against the wall, believe me. It is specially annoying with my VW bluetooth and with a Jabra 510 speaker. With my other bluetooth headphones (Genius) it works very well and no cuts... I don't understand the pattern...
So, I read to do a logcat... how do I do it? And how do I deduct from the log what is happening and when?
Thanks in advance.
agustinsj said:
Same problem here. For months having this annoying issue.
I'm also on stock rom, and this is getting worse everyday. I am now on Nougat beta participating in the preview with the stock rom and the problem is still there.
I tried several fixes and resets, wipes, etc. with no success. I am very close to throw it against the wall, believe me. It is specially annoying with my VW bluetooth and with a Jabra 510 speaker. With my other bluetooth headphones (Genius) it works very well and no cuts... I don't understand the pattern...
So, I read to do a logcat... how do I do it? And how do I deduct from the log what is happening and when?
Thanks in advance.
Click to expand...
Click to collapse
XDA Developers, being a forum for developers, has many tutorials and help threads about logcat, since a logcat is the single best, and often the ONLY way to find OS level issues.
http://forum.xda-developers.com/showthread.php?t=2141817
http://forum.xda-developers.com/showthread.php?t=1726238
http://forum.xda-developers.com/showthread.php?t=1378491
Pkt_Lnt said:
XDA Developers, being a forum for developers, has many tutorials and help threads about logcat, since a logcat is the single best, and often the ONLY way to find OS level issues.
http://forum.xda-developers.com/showthread.php?t=2141817
http://forum.xda-developers.com/showthread.php?t=1726238
http://forum.xda-developers.com/showthread.php?t=1378491
Click to expand...
Click to collapse
I have a BT headset and an Android Wear watch connected.Here are (I think) the relevant parts of one of my logcats where it dies and restarts four minutes apart:
Code:
08-10 12:53:17.182 975 1681 I ActivityManager: Process com.android.bluetooth (pid 21994) has died
08-10 12:53:17.183 975 1681 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:17.401 975 1073 I ActivityManager: Start proc 31623:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:53:20.312 975 3086 I ActivityManager: Process com.android.bluetooth (pid 31623) has died
08-10 12:53:20.313 975 3086 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:21.362 975 2813 I ActivityManager: Start proc 31765:com.android.bluetooth/1002 for broadcast com.android.bluetooth/.pbap.BluetoothPbapReceiver
...
08-10 12:57:43.497 975 3092 I ActivityManager: Process com.android.bluetooth (pid 31765) has died
08-10 12:57:43.499 975 3092 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:43.695 975 1073 I ActivityManager: Start proc 932:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:57:46.510 975 3098 I ActivityManager: Process com.android.bluetooth (pid 932) has died
08-10 12:57:46.511 975 3098 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:49.453 975 1073 I ActivityManager: Start proc 1403:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
I see nothing before it dies, and it seems really weird that BT dies with only an informational message, but the restarts are warnings.
JimSmith94 said:
I have a BT headset and an Android Wear watch connected.Here are (I think) the relevant parts of one of my logcats where it dies and restarts four minutes apart:
Code:
08-10 12:53:17.182 975 1681 I ActivityManager: Process com.android.bluetooth (pid 21994) has died
08-10 12:53:17.183 975 1681 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:17.401 975 1073 I ActivityManager: Start proc 31623:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:53:20.312 975 3086 I ActivityManager: Process com.android.bluetooth (pid 31623) has died
08-10 12:53:20.313 975 3086 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:21.362 975 2813 I ActivityManager: Start proc 31765:com.android.bluetooth/1002 for broadcast com.android.bluetooth/.pbap.BluetoothPbapReceiver
...
08-10 12:57:43.497 975 3092 I ActivityManager: Process com.android.bluetooth (pid 31765) has died
08-10 12:57:43.499 975 3092 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:43.695 975 1073 I ActivityManager: Start proc 932:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:57:46.510 975 3098 I ActivityManager: Process com.android.bluetooth (pid 932) has died
08-10 12:57:46.511 975 3098 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:49.453 975 1073 I ActivityManager: Start proc 1403:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
I see nothing before it dies, and it seems really weird that BT dies with only an informational message, but the restarts are warnings.
Click to expand...
Click to collapse
Is this logcat from the watch or phone and is the headset connected to the watch or phone and is this BT crash from the watch or headset?
I'm trying to understand if this is a phone issue or watch issue and who to get this information to for some help?
As we've exchanged posts before, both my headset and watch drop connections from the phone, though I've minimized this with some hacks. This only happens when I am out and about, and can not duplicate it when I am near a computer to get a logcat. When I'm walking or on my bike I get it from the headset, even when the phone is on my belt only two feet away. When I look at the watch, it has dropped too.
Pkt_Lnt said:
Is this logcat from the watch or phone and is the headset connected to the watch or phone and is this BT crash from the watch or headset?
I'm trying to understand if this is a phone issue or watch issue and who to get this information to for some help?
As we've exchanged posts before, both my headset and watch drop connections from the phone, though I've minimized this with some hacks. This only happens when I am out and about, and can not duplicate it when I am near a computer to get a logcat. When I'm walking or on my bike I get it from the headset, even when the phone is on my belt only two feet away. When I look at the watch, it has dropped too.
Click to expand...
Click to collapse
Hi Pkt_Lnt! This is from my phone and I have saved the rest of the logcat if it will help you. My BT headset is only connected to my phone. This was at home while I was on a phone call and the BT connections to both the headset and watch were lost twice. The phone icon went from connected to just on both times. I don't recall this happening before I got an Android Wear watch, but I've had several over the past few years.
BTW, I'm only on the phone two or three times a day, but this happens almost every time I receive a call, but very rarely when I initiate a call.
I'd be interested in what hacks you have done to see if they might help me.
Thanks Pkt_Lnt! for your useful information.
As Jim I also have a watch connected (Huawei) and I see also continuous but random disc&connections.
Will try to get that catlog for the thread as soon as I can.
One thing that maybe a chance or not is that always always when I'm ridding and go through a bridge the BT disconnects from my car headset. Always. That is the only pattern I can verify. Can a LTE cell update break a BT connection? Maybe the radio chip is fooled by this change?
I remember in previous versions to marshmallow that this happened once in a blue moon... now dozens an hour.
Thanks.
JimSmith94 said:
Hi Pkt_Lnt! This is from my phone and I have saved the rest of the logcat if it will help you. My BT headset is only connected to my phone. This was at home while I was on a phone call and the BT connections to both the headset and watch were lost twice. The phone icon went from connected to just on both times. I don't recall this happening before I got an Android Wear watch, but I've had several over the past few years.
BTW, I'm only on the phone two or three times a day, but this happens almost every time I receive a call, but very rarely when I initiate a call.
I'd be interested in what hacks you have done to see if they might help me.
Click to expand...
Click to collapse
I've frozen Google Connectivity Services, switched to Legacy DHCP in developer settings, turned off wifi on the watch, and disabled cloud sync in the Android Wear app on the phone.
agustinsj said:
Thanks Pkt_Lnt! for your useful information.
As Jim I also have a watch connected (Huawei) and I see also continuous but random disc&connections.
Will try to get that catlog for the thread as soon as I can.
One thing that maybe a chance or not is that always always when I'm ridding and go through a bridge the BT disconnects from my car headset. Always. That is the only pattern I can verify. Can a LTE cell update break a BT connection? Maybe the radio chip is fooled by this change?
I remember in previous versions to marshmallow that this happened once in a blue moon... now dozens an hour.
Thanks.
Click to expand...
Click to collapse
Well, the bridge would block the cell signal, but I don't think it should drop the BT since they are handled by different software, but I'm not sure what hardware (antenna) handle cellular / wifi / bluetooth. This is hard to sort out. What I know is that cellular, voice and data, is controlled by the phone radio. Both wifi and bluetooth are controlled by the kernel. On bluetooth and wifi drops, they will occur simultaneously for me. When I see a bluetooth drop on mobile, there is not effect on my cellular data.
So, what would help is noting phone type, ROM used, kernel used, and I know we all have Huawei watches. I have a Nexus 6, Pure nexus ROM, ElementalX kernel. I've tested three kernels besides stock to see what is happening. It just occurred to me that I have not disconnected my watch when out using my headset to see if those headset dropouts happen.
edit - Even though I've tried differnet kernels to solve the BT / WiFi drops, I suspect they have the same stock kernel modules that control those functions since I've seen no difference in them. No kernel control apps have anything related to those two functions either. (le sigh)
There is no solution, but hope for the future.
Check posts 8 and 11 here. I have the HBS-730 and it works except for the "out of range" dropouts.
http://forum.xda-developers.com/nexus-6/help/nexus-6-marshmallow-bluetooth-operating-t3253708
Ideas from Reddit, none have worked for me.
https://www.reddit.com/r/nexus6/comments/4pk876/nexus_6_keeps_disconnecting_bluetooth_audio_at/
Google Product forums have many posts, but no solutions and it is a user to user forum like XDA.
I've found so many entries in Google Code, but none that seem to be this issue. I have not been able to search all that come up to narrow it down and report with a good logcat.
https://code.google.com/p/android/i...D+Type+Status+Owner+Summary+Stars&cells=tiles
Now my head hurts from all the searching, I need a time out.
Pkt_Lnt said:
I've frozen Google Connectivity Services, switched to Legacy DHCP in developer settings, turned off wifi on the watch, and disabled cloud sync in the Android Wear app on the phone.
Well, the bridge would block the cell signal, but I don't think it should drop the BT since they are handled by different software, but I'm not sure what hardware (antenna) handle cellular / wifi / bluetooth. This is hard to sort out. What I know is that cellular, voice and data, is controlled by the phone radio. Both wifi and bluetooth are controlled by the kernel. On bluetooth and wifi drops, they will occur simultaneously for me. When I see a bluetooth drop on mobile, there is not effect on my cellular data.
So, what would help is noting phone type, ROM used, kernel used, and I know we all have Huawei watches. I have a Nexus 6, Pure nexus ROM, ElementalX kernel. I've tested three kernels besides stock to see what is happening. It just occurred to me that I have not disconnected my watch when out using my headset to see if those headset dropouts happen.
edit - Even though I've tried differnet kernels to solve the BT / WiFi drops, I suspect they have the same stock kernel modules that control those functions since I've seen no difference in them. No kernel control apps have anything related to those two functions either. (le sigh)
Click to expand...
Click to collapse
I am on a stock rooted Nexus 6 running the latest MOB30W, my watch is the Huawei Watch running the latest M6E69B, and I'm on the latest Android Wear 1.5.0.3124679.gms.
I have tried your hacks as well, but they made no difference. However, I just tried your suggestion and disconnected my watch in the Android Wear app. I just made it through a 25 minute incoming call with no disconnect at all, so I think you're on to something! Maybe for now, somebody can come up with something in Tasker to disconnect the watch when the phone is answered and reconnect on hangup.
JimSmith94 said:
I am on a stock rooted Nexus 6 running the latest MOB30W, my watch is the Huawei Watch running the latest M6E69B, and I'm on the latest Android Wear 1.5.0.3124679.gms.
I have tried your hacks as well, but they made no difference. However, I just tried your suggestion and disconnected my watch in the Android Wear app. I just made it through a 25 minute incoming call with no disconnect at all, so I think you're on to something! Maybe for now, somebody can come up with something in Tasker to disconnect the watch when the phone is answered and reconnect on hangup.
Click to expand...
Click to collapse
Ah, I love Tasker ideas!
http://www.pocketables.com/2015/01/disconnecting-one-bluetooth-device-using-tasker.html
Try the attached, customize them for your device and contacts and let me know. I don't have a second phone here to test them at the moment.
You will need Secure Settings if you don't already have it. It has its own idiosyncrasies with systemless root if you have it.
Attachments removed because of errors in my logic.
Pkt_Lnt said:
Ah, I love Tasker ideas!
http://www.pocketables.com/2015/01/disconnecting-one-bluetooth-device-using-tasker.html
Try the attached, customize them for your device and contacts and let me know. I don't have a second phone here to test them at the moment.
You will need Secure Settings if you don't already have it. It has its own idiosyncrasies with systemless root if you have it.
Click to expand...
Click to collapse
Haha, I had created my own before I saw that you had attached yours! The watch ID is different of course, but yours disconnects when the phone is ringing and reconnects when it's off hook.
As I understand it, off hook means that the phone state is either dialing, active, or on hold, so I set mine to disconnect the watch when the phone is off hook and reconnect when it's idle. I'm a Tasker rookie, and I don't have a second phone to test with either, so I could be wrong.
JimSmith94 said:
Haha, I had created my own before I saw that you had attached yours! The watch ID is different of course, but yours disconnects when the phone is ringing and reconnects when it's off hook.
As I understand it, off hook means that the phone state is either dialing, active, or on hold, so I set mine to disconnect the watch when the phone is off hook and reconnect when it's idle. I'm a Tasker rookie, and I don't have a second phone to test with either, so I could be wrong.
Click to expand...
Click to collapse
Oh good. Yes I can see now I had phone off hook wrong. I have plenty of Tasker profiles, but none on phone calls. Let me know if this works when you test it.
Pkt_Lnt said:
Oh good. Yes I can see now I had phone off hook wrong. I have plenty of Tasker profiles, but none on phone calls. Let me know if this works when you test it.
Click to expand...
Click to collapse
I added flash messages to my connect and disconnect tasks, dialed my Google Voice number, and the messages popped up on the screen properly. I'll have to wait for an actual call to be sure it really works.
Dear all,
I just install catlog, launch it, bluetooth, the music app and after a few moment : disconneting like always.
Related
When I switch off my XDA IIs by button or SW button in most of the cases the device switches on it self for one more time.
Is there anyone who can help?
Thanks guys!
:?:
I have the same problem, I had a bluetooth headset paired to it, maybe that is it, I only got the XDAIIs today so I have not had much time to watch it but it happened tonight and the XDA mini never does it.
Each time the BT headset is switched on or off and pairs up or releases, when a text message arrives, when you come out of a signal blackspot and reconnect and find you have missed calls etc.
Basically anything that results in a visual change caused the device to switch on.
Very annoying. Don't know the solution.
I share your pain.
Joe
I'm using http://www.trancreative.com/nicestart.aspx to keep the device locked, but it will turn on/off, but now it's locked so i dont delete data when it turns on in my pocket.
No matter what you do, the device will turn on at least once every hour.
I read somewhere that it does this to check the battery status.
I had the same problem once. Please open ActiveSync, switch the device off and see if ActiveSync is trying to connect..
Of course there can be lots of other reasons...
Yes I didn't mention on my post that activesync also seems to be a player in this problem.
If activesync is running, somehow the device syncs at varying intervals from 5 mins-1hr and switches it on to do so.
I used the attached to kill activesync to stop it happening.
Hope it helps.
Joe
I just unchecked the "Use mobile schedule to sync with this PC" setting and the problem was solved.
Though this seems to be a bug in ActiveSync..
Thanks
Works fine, great!
i had this problem on my old rom, and since i upgraded to 1.40, it aint done it since. maybe u need to upgrade.
I have the Captivate, running Phoenix 4.1 ROM, almost all is working well but Bluetooth. Does anyone know what I can do, what I can look for, any files to review, etc. to help troubleshoot the issue I am having.
The problem is that the phone will initially connect to my car radio, stay connected for a few minutes and then drop the phone connection. The music/audio connection remains, which I could care less about. If I reconnect it, it will last a few minutes and then drop again. It's unlikely to stay connected for anything longer than 4 minutes. Frustrating.
I have removed the profiles from both the phone and radio and recreated multiple times, pairing from the radio first, then again from the phone first. All efforts so far have left me with a non-functional Bluetooth connection.
Thanks to anyone who can provide me guidance for troubleshooting.
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?
mstrpeter said:
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?
Click to expand...
Click to collapse
All righty then, I guess its me
mstrpeter said:
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?
Click to expand...
Click to collapse
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Komodo Rogue said:
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Click to expand...
Click to collapse
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
mstrpeter said:
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
Click to expand...
Click to collapse
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
freekyfrogy said:
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
Click to expand...
Click to collapse
Well I swapped to omnirom as well and sure enough, operation has been perfect. I also noticed while looking at obd2 apps that one had mentioned bluetooth connectivity issues on CM...
so i'd say, SOLVED.
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
jeffcrilly said:
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
Click to expand...
Click to collapse
The same exact thing is happening to me, just one day started to get in a "Pairing Loop" continually asking me to pair the watch to my phone. Upon pairing successfully and syncing some notifications the connection gets broken and immediately a new parigin code appears.
UPDATE:
I'm back on cm11 and everything is working properly. The problem is not the ROM, its the Kernel that comes baked in. Currently using elementalX Kernel and no issues.
Hello all!
I must say, this watch is a very nice toy to play with and very handy in meetings! I have used the watch for a few days now, but I (only) have 2 issues to be solved which I cannot seem to find the answer yet:
1. The watch is connected to my phone OK (all notifications come through all the time). However, when I say "OK google" and then for instance "show me my steps" or "show me the weather", it will go to a screen saying me the connection is offline (white logo on blue background on the top of the screen). When I dismiss that message, I see that my connection is still OK! Weird .... this happens to me practically 80-90% of the times .... on a very rare occasion it succeeds to show me the info I want. By the way, my internet connection is OK at that time.
2. I have my phone also connected with BT to my Volvo V40 (2013). However, with the watch also on BT, the carkit of my Volvo is now almost useless as the voice is completely messed up (from the caller to me, and from me to the caller), sounds very intermittend or something. It seems like the BT connection is not happy with having 2 devices to be connected at the same time. My phone is an iNew V3 ... could it be something with BT profiles or versions?
I have already tried to reset the watch, re-install wear on my phone, deleted the dalvik cache (phone), un-installed apps, but no luck. Anybody have a clue on the above?
Maybe your Wifi/3G connexion is in sleeping mode and is too long to unsleep ? the watch can not connect so quickly ?
You sound like having BT reception issues on the phone. This behaviour might be triggered by the bluetooth interface itself (on the phone - bad design) or by bad drivers (also on the phone) or by interferences from the wifi module. Is your wifi on all the time?
Regular wifi is on 2.4GHz, the same frequency as BT. Wifi, however, uses more Rx/Tx power compared to BT so, under certain bad antenna designs, WiFi can just mess-up BT.
On my phone (Z1C) is the other way around: having BT ON will cause bad performance on 2.4GHz WiFi .... so I just stopped using the 2.4 band for WiFi.
Give it a try, Worst case scenario: use another phone.
Hi guys,
Thanks for the reply. About the first idea ... well if I have my phone on the charger and already switched on, it still happens. So there I assume the 3G / wifi connection is already on and this issue will not be due to the delay of switching the data connection on. Am I right?
Second option: my wifi is switched on all the time, you are right. I will try to experiment a little bit with it, let's see if that will make a difference. And, changing the phone ... hmmm well that would be a very high impact of course. My iNew V3 actually works very well ...
I am still a bit struggling with accepting it is my phone causing this issue ... only with the voice regocognition I have this issue ... with all other commands and apps the connection is OK! Only with the "OK google" option it says "offline" ... and immediately (I do not see the colored circle). To me it looks more like a but in the software or something, but after 3 resets of the device I also cannot believe that ...
Any more options? Thanks!
Troxelke said:
Hi guys,
Thanks for the reply. About the first idea ... well if I have my phone on the charger and already switched on, it still happens. So there I assume the 3G / wifi connection is already on and this issue will not be due to the delay of switching the data connection on. Am I right?
Second option: my wifi is switched on all the time, you are right. I will try to experiment a little bit with it, let's see if that will make a difference. And, changing the phone ... hmmm well that would be a very high impact of course. My iNew V3 actually works very well ...
I am still a bit struggling with accepting it is my phone causing this issue ... only with the voice regocognition I have this issue ... with all other commands and apps the connection is OK! Only with the "OK google" option it says "offline" ... and immediately (I do not see the colored circle). To me it looks more like a but in the software or something, but after 3 resets of the device I also cannot believe that ...
Any more options? Thanks!
Click to expand...
Click to collapse
Update: i tried several things with the WIFI / BT settings and on/off, but no luck. I have forwarded the above issues to Google, maybe they can help me out. I will keep you informed ... in the meantime anybody else some useful tips? Thanks!!!
Troxelke said:
Hello all!
I must say, this watch is a very nice toy to play with and very handy in meetings! I have used the watch for a few days now, but I (only) have 2 issues to be solved which I cannot seem to find the answer yet:
1. The watch is connected to my phone OK (all notifications come through all the time). However, when I say "OK google" and then for instance "show me my steps" or "show me the weather", it will go to a screen saying me the connection is offline (white logo on blue background on the top of the screen). When I dismiss that message, I see that my connection is still OK! Weird .... this happens to me practically 80-90% of the times .... on a very rare occasion it succeeds to show me the info I want. By the way, my internet connection is OK at that time.
2. I have my phone also connected with BT to my Volvo V40 (2013). However, with the watch also on BT, the carkit of my Volvo is now almost useless as the voice is completely messed up (from the caller to me, and from me to the caller), sounds very intermittend or something. It seems like the BT connection is not happy with having 2 devices to be connected at the same time. My phone is an iNew V3 ... could it be something with BT profiles or versions?
I have already tried to reset the watch, re-install wear on my phone, deleted the dalvik cache (phone), un-installed apps, but no luck. Anybody have a clue on the above?
Click to expand...
Click to collapse
which phone are you using? are you on custom rom or kernel?
doki81 said:
which phone are you using? are you on custom rom or kernel?
Click to expand...
Click to collapse
I am using a iNew V3 on KitKat with the 1.13 official version (however from needrom). Would that be the issue?
Troxelke said:
I am using a iNew V3 on KitKat with the 1.13 official version (however from needrom). Would that be the issue?
Click to expand...
Click to collapse
try to pair your watch with your friend phone and to check this is not a problem coming from your phone. sometimes certain kernel do have issue with some of the bluetooth device.
Hello everyone. Sorry for my English, because I am using a translator. I decided to write this post, because it happened to me the same trouble and I found her cause. In anticipation of its Nexus 6, I decided to temporarily buy fairly cheap option LG G60 (X135). When watch came to me, I noticed the same problem. I then tried to connect them to the Moto G (1st generation), and there is the same. but by chance, in the evening, in my hands was LG G90 and I connected watch to this phone. Everything works without any problem. it turns out that despite the declared characteristics (Bluetooth 4.0) in all devices, it works quite differently everywhere. I hope with Nexus no problems.
Hi all, after opening this thread I tried several things and have some new insights:
- new update (5.0.1) solved my issue with going "offline" after a voice command. Now it works perfectly! But only if I am not connected to my carkit.
- if my watch is connected and try to use the carkit the sound is still bad. So I would like to have my watch disconnected if my carkit connects:
-- this could be done by only allowing 1 device to pair with my phone and prioritize carkit to be first and watch to be second.
-- this could be done by actively unpairing the watch if I receive a call (and connect when call is over).
The first option would be the most reliable and most simple. I tried to find an app that restricts only having 1 pairing and having a prioritize option ... but I cannot find such app. People any options?
Thanks!
Hi guys, in response of the above, the app TRIGGER might do the job, but it seems closing the Android Wear app or disconnect via Bluetooth does NOT disconnect your watch! Has anybody succeeded in using TRIGGER to disconnect / connect the watch with a automatic job?
My WiFi has issues opening new connections, like checking my email can take anything from a normal 1 second to just sit there and spin for 30 seconds.
This gets worse if I ask the email client to check all three accounts at the same time.
Opening say facebook through a bookmark on the start screen, can either load instantly, or just show a white screen until I force close Chrome and retry.
I never get an actual timeout error, but it'll keep loading some items between 10 seconds, to just never connecting.
When I do a speed check, there's no issue, I get the same 12 Mbps as the wired computer, assuming it'll actually start downloading.
On the play store there's broken downloads though, it'll download at max speed instantly, but then hang in the middle until I force stop the play store (or reboot).
If I let it sit long enough, it might resume but often with corrupt downloads as a result.
I've had this problem for a while now, and I've tried connecting to various other networks with completely different configurations and it's pretty much consistent.
Disabling WiFi and using the LTE network instead, it doesn't display this behaviour at all, so it has to be something with the WiFi.
Has anyone else had this? I can't find anything useful through the search or google, they all suggest I do this and that on my router, but the other devices work fine.
Tested with the HTC M7, an old Motorola Razr, even the now ancient Moto XT720 has no issues.
If you are in the stock Lollipop 5.0, then you should check your logcat (or use CatLog app in PlayStore if you are rooted).
There are many many WifiStateMachine errors that are logged each second.... I made a thread about it:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-pure-edition-stock-5-0-major-t3002124
I reverted back to 4.4.4 and had no more of those errors.
eyeoncomputers said:
If you are in the stock Lollipop 5.0, then you should check your logcat (or use CatLog app in PlayStore if you are rooted).
There are many many WifiStateMachine errors that are logged each second.... I made a thread about it:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-pure-edition-stock-5-0-major-t3002124
I reverted back to 4.4.4 and had no more of those errors.
Click to expand...
Click to collapse
I checked your thread, and I had a bug like that on 4.4.4 actually.
Where it would work fine, go to sleep then not wake up again.
For me, it was a game from humble bundle that triggered this, "The Deer God"
There was another game on play that did the same, but I can't remember the name of that one.
After I emailed the devs of Deer God, they oddly found the bug immediately and their new version didn't have this problem.
I didn't even send them a log file or anything.. Which was weird.
So far this never happened after upgrading to Lollipop though.
My WiFi problems disappeared at work, but remained at home.
Thinking it was the router, I borrowed a WiFi repeater but the problem still occurred.
Even when I used the repeater as a hotspot with cable.
I was about to give up, and just use my 4G all the time..
But I installed DD-WRT, and lo and behold, WiFi works flawlessly?!
It's not like I'm using a cheap rubbish router, it's the Netgear Nighthawk for crying out loud..
You'd think the software for it would be well coded considering how long they've been doing these devices...