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
Related
Still having the same Bluetooth issues I had in 4.2.1 in 4.2.2...
Occasionally when turning off bluetooth, it gets stuck in a shutting down state. You can't then turn bluetooth back on and the only way to recover is to reboot.
I don't have that issue. Are you using custom ROM..?
No completely stock, not rooted or anything.
Looks like the issue has been around in some way or another since Ice Cream Sandwich! Can't believe they haven't fixed it yet!...
http://code.google.com/p/android/issues/detail?id=24522
I haven't seen it yet either. Although I did in 4.2.1 I wish they would fix the ****ty quality already
Sent from my Galaxy Nexus using xda premium
Do you need to really turn it off?
Sent from my Galaxy Nexus using Tapatalk 2
same form me! android 4.2.2 I can't use BT with my car!
R: Bluetooth issues still in 4.2.2
That's the reason I'm so excited to update my gnex... but now... ****!
Sent from my Galaxy Nexus using xda app-developers app
The same, not working with my InCar HFsystem. need to wait 4.2.3?
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I also just updated my nexus 10 to 4.2.2. same issues. my keyboard and mouse won't stay connected and it gets stuck on turning off! I really want this to replace my laptop but it can't with these problems. it also still seems to studder on video a bit with ad2p. I sold my note 10.1 in hopes that this update would fix my only issue with an awesome tablet and it didnt .what a disappointment.
Same here. Was working good for the first 2 hrs being connected to my headphones, connected to my in car, skips just like before.
I feel stupid saying this, but it seems to get worse over time. Can't understand how length of time connected would matter
Yeah this is pissing me off it will not connect to my cars head unit (Sony), im running stock 4.2.2 rooted
Can't believe theres no fix or workaround
Im also still have issues with 4.2.2 and stuttering. Also quality is still lacking big time from 4.1.2 stack
xoxoJI said:
The same, not working with my InCar HFsystem. need to wait 4.2.3?
Click to expand...
Click to collapse
Carbon Rom 1.1 (4.2.2) with AK 691, flashed Tiny's GPU libraries update to enable true 4.2.2 kernel usage.
Turned off "High Performance Sound" option in Trickster Mod settings and all BT issues are resolved for first time since I had 4.1 running. That includes skipping/distortion with Google Play Music, overall performance and linkup issues, and most important all the bluetooth controls on my RocketFish headphones finally work again!
May not work for everyone, but I've been trying to resolve this for quite some time and had the Eureka moment today!
So I'm wondering. Does the bluetooth stuttering problem only occur when connected to a wifi network? That type of problem has existed for quite some time. The iPhone 3G had an issue where bluetooth phone and media audio would severely skip and stutter when connected to a wifi network. From what I understand since bluetooth and wifi b/g both use the 2.4GHz band the two interfered with each other. Turning wifi off always fixed the problem. The HTC Nexus One also suffered from this type of issue on all Google stock ROM's. I'm assuming it was also because of bluetooth and 2.4GHz wifi interfering with each other. Is this the type of issue that Nexus devices have been experiencing on Android 4.2 and 4.2.1?
havn`t got any problem before flashing 4.2,and now all right,seens like hardware problem in same series of gnexus
Same issue. Bluetooth seems to reset when the phone is rebooted, however it isn't long before it's on the fritz again. Very annoying for car connection and renders my Bluetooth speaker practically useless. Please acknowledge and fix Google, this affects your flagship range!
clearyt1 said:
Carbon Rom 1.1 (4.2.2) with AK 691, flashed Tiny's GPU libraries update to enable true 4.2.2 kernel usage.
Turned off "High Performance Sound" option in Trickster Mod settings and all BT issues are resolved for first time since I had 4.1 running. That includes skipping/distortion with Google Play Music, overall performance and linkup issues, and most important all the bluetooth controls on my RocketFish headphones finally work again!
May not work for everyone, but I've been trying to resolve this for quite some time and had the Eureka moment today!
Click to expand...
Click to collapse
This still working for you? I had actually gone back to 4.2.1 stock as it was worse for me after 4.2.2 upgrade
kendoori said:
This still working for you? I had actually gone back to 4.2.1 stock as it was worse for me after 4.2.2 upgrade
Click to expand...
Click to collapse
Do you have a copy of the 4.2.1 ?i cant find it,google only has 4.2.2 ontheir page,4.2.1 seemed better,as it did not have the audio bug where you can't use the equalizer in google music when moving the sliders,if you have a working 4.2.1 for galaxy nexus can you upload it somewhere?
So on 4.3, I tried several Bluetooth keyboard but had the well known problem of the keyboard disconnecting after 3-4 seconds of inactivity.. Has anyone experienced an improvement of this on 4.4.2?
Sent from my HTC One_M8 using xda app-developers app
sameer1807 said:
So on 4.3, I tried several Bluetooth keyboard but had the well known problem of the keyboard disconnecting after 3-4 seconds of inactivity.. Has anyone experienced an improvement of this on 4.4.2?
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
I use a bluetooth keyboard frequently during the day. I've tried several bluetooth keyboards. I've never had one disconnect yet. I have had them go into sleep mode after a few minutes and need to press a key to wake them up. But they've never disconnected on me. This was true in 4.3 and is the same for me in 4.4.2.
The well-discussed BT problem is h/w. Some folks who exchanged their N10.1-14's had the problem go away using the same peripherals. I'm a heavy BT user and haven't had an issue since October.
Yea I spoke to several Samsung reps and they kept saying its because of incompatible hardware but I know that's bs. I guess I'm SOL for now
Sent from my SM-P600 using XDA Free mobile app
I'm holding out for 4.4.2 helping. I bought a Nexus 7 (latest one) and a Perixx 806 keyboard. It worked great with 4.2.2. When the Nexus was upgraded to 4.3, it didn't work properly at all. Keyboard was unusable. When the 4.4 update came, it all worked perfectly again.
With the Note 10.1 2014, 4.3 keeps disconnecting every few seconds for me. After a few seconds it will reconnect and catch up, but sometimes it misses a few characters. Based on what I saw on the Nexus 7, I'm hoping 4.4.2 will fix it - but maybe I'm just an optimistic fool!
thenag said:
I'm holding out for 4.4.2 helping. I bought a Nexus 7 (latest one) and a Perixx 806 keyboard. It worked great with 4.2.2. When the Nexus was upgraded to 4.3, it didn't work properly at all. Keyboard was unusable. When the 4.4 update came, it all worked perfectly again.
With the Note 10.1 2014, 4.3 keeps disconnecting every few seconds for me. After a few seconds it will reconnect and catch up, but sometimes it misses a few characters. Based on what I saw on the Nexus 7, I'm hoping 4.4.2 will fix it - but maybe I'm just an optimistic fool!
Click to expand...
Click to collapse
It has nothing to do with hardware. I have used my Rapoo e6100 succesfully on my Note 10.1 (2013 edition) on Official and semi-official firmware 4.1.2 for several months (used another noname keyboard before that).I just updated to 4.4.2 official firmware and the keyboard pairs and that is it.
So, the fix from Google still needs to come.
Still on jb ..had my tab since Dec ..never had a Bluetooth issue..
Sent from my SM-P600 using XDA Premium HD app
I'm on 4.4.2 and I have massive bluetooth keyboard issues. I'm using an Apple Wireless Keyboard which works fine on my PC at home, and I could have sworn worked fine when I first got the tablet... so I can't guarantee I haven't futzed with something, but all I've done so far is rooted and removed a few bloat apps, nothing too major.
Now, for whatever reason, I have lots of keystroke lag which produces a lot of missed characters if I type too fast. It's basically useless. I have no idea how to begin troubleshooting it either, so it's a frustrating issue.
For those having BT keybaord issues, install Bluetooth Keybaord EasyConnect app from the Play Store. It solved my BT keyboard problems. Nothing else has worked except this
sam2c said:
For those having BT keybaord issues, install Bluetooth Keybaord EasyConnect app from the Play Store. It solved my BT keyboard problems. Nothing else has worked except this
Click to expand...
Click to collapse
This is helpful....
Just bout the LTE model so new as new can get and the BT keyboard disconnects and then reconnects frustrating when typing... I used the same keyboard with NO issues on my Samsung Nexus 10 tablet... It's a Logitech keyboard
parcou said:
This is helpful....
Just bout the LTE model so new as new can get and the BT keyboard disconnects and then reconnects frustrating when typing... I used the same keyboard with NO issues on my Samsung Nexus 10 tablet... It's a Logitech keyboard
Click to expand...
Click to collapse
Hello,
On my SM-P600, 4.4.2, the problem does'nt fix with Keyboard Esyconnect (the app is not compatible with 4.4.2). I use a Logitech K810 BT kb, but disconnect every 3 ou 5 seconds...
Did someone try the Bluetooth Keyboard Kug Fix on playstore ?
Hello Community,
Has anyone have had any success with AOSP based rom and syncing their phones via bluetooth with their car audio?
I've tried numerous roms, including CM11, Carbon, and SlimKat with no success.
Although, my phone successfully paired and everything. However, upon returning to my car (2013 Prius), my phone doesn't reconnect successfully. Oftentimes, I get these "bluetooth has crashed not responding" popup.
TouchWiz rome work flawlessly, of course.
Anyhow, if there is a trick to get this to work, I would really appreciate it. I love AOSP.
Thanks!
Anyone?
knite75 said:
Anyone?
Click to expand...
Click to collapse
I get the exact same thing. I don't think the drivers for Cm are working right
knite75 said:
Hello Community,
Has anyone have had any success with AOSP based rom and syncing their phones via bluetooth with their car audio?
I've tried numerous roms, including CM11, Carbon, and SlimKat with no success.
Although, my phone successfully paired and everything. However, upon returning to my car (2013 Prius), my phone doesn't reconnect successfully. Oftentimes, I get these "bluetooth has crashed not responding" popup.
TouchWiz rome work flawlessly, of course.
Anyhow, if there is a trick to get this to work, I would really appreciate it. I love AOSP.
Thanks!
Click to expand...
Click to collapse
Androidnewuser1 said:
I get the exact same thing. I don't think the drivers for Cm are working right
Click to expand...
Click to collapse
Me three. And I happen to have a 2014 plug in model :highfive:
I flashed Gummy rom few days back and I did not notice any issues with car bluetooth but did notice the my Moto 360 keeps disconnecting randomly and I have to turn off and turn on bluetooth and restart watch for it to connect again.
Scribbled on Galaxy Note 3.
Mine has always worked with my Sony deck, been on CM nightlies for months. In fact last week it was synced to my deck and my OBD2 scan tool at the same time with no hiccups.
I've never had any issues with BT in my car(2013 Forte) with any of the various AOSP/CM builds & kernels I've been running for the past year, it connects fine & doesn't drop. I get the occasional stutter but I get that with TW too.
ajamils said:
I flashed Gummy rom few days back and I did not notice any issues with car bluetooth but did notice the my Moto 360 keeps disconnecting randomly and I have to turn off and turn on bluetooth and restart watch for it to connect again.
Scribbled on Galaxy Note 3.
Click to expand...
Click to collapse
Same here with the 360.
moSess said:
Me three. And I happen to have a 2014 plug in model :highfive:
Click to expand...
Click to collapse
Maybe it's specific to the Prius. Sounds like only the Prius had the issue.
---------- Post added at 09:42 AM ---------- Previous post was at 09:41 AM ----------
Maybe it's specific to the Prius. Sounds like only the Prius had the issue.
Hey guys!
I am fairly satisfied with my Moto 360 and I enjoy using it. But after 5-6 days (around a week maybe) it shows that it's not connected to my One M8. When I try to scan for it with bluetooth, the phone can't discover it. I also tried using brother's OnePlus One, but the result is the same.
The only thing that fixes this is factory reset the watch. Then I have to do everything all over again and it's getting really annoying. Did someone have similar experience and is there some solution to this?
Thanks in advance!
inspire4gfreak said:
Hey guys!
I am fairly satisfied with my Moto 360 and I enjoy using it. But after 5-6 days (around a week maybe) it shows that it's not connected to my One M8. When I try to scan for it with bluetooth, the phone can't discover it. I also tried using brother's OnePlus One, but the result is the same.
The only thing that fixes this is factory reset the watch. Then I have to do everything all over again and it's getting really annoying. Did someone have similar experience and is there some solution to this?
Thanks in advance!
Click to expand...
Click to collapse
Got a similar problem where after several hours the watch doesnt reconnect to the phone because my moto x thinks that its still connected.
the only solution i found so far is to disconnect through the wear app on my phone, disable bluetooth and re-enable bluetooth.
you could give it a try.
eric
edit: newest android wear update seems to solve this issue
I surely hope so! I tried your method before already, but the only trick for getting it to work is factory reseting the watch. We'll see if the update squashed this bug
well that sucks mate. good luck!
I too am having this issue... my watch shows Disconnected and nothing I do fixes this except for resetting my wtach and reconnecting from scratch.
I also just updated to Lollipop on my nexus 5 through a clean factory install, and had the same issue.
I'm having the same problem once a week.
What solves my problem ist:
Turn off BT on phone
Reboot watch
Reboot Phone
Turn BT on phone back on
Connect through Wear App
mc-paulo said:
I'm having the same problem once a week.
What solves my problem ist:
Turn off BT on phone
Reboot watch
Reboot Phone
Turn BT on phone back on
Connect through Wear App
Click to expand...
Click to collapse
This also helps, but only sometimes I hope Google will fix this in the near future. It is a single thing that drives me crazy about this watch.
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.