I've had an LG G Watch R for a few months and used it without problems. However, I just flashed Blisspop on my Nexus 6 last night. Initially, it would connect and then after a few minutes disconnect. After a few factory resets, the Android Wear app no longer sees the watch. This is incredibly annoying; other Bluetooth devices can connect, but the watch can't.
I know the ROM can be compatible with Wear, since it's CM based and worked initially. Any suggestions would be immensely appreciated.
Did you install gapps with your ROM?
Wear apps use Google Play Services. So what is your google apps service version in phone?
Related
So I bought my Google Play S4 from the Play store maybe 6 months ago. I unlocked it at one point to be able to write to my memory card. But I didn't run any custom roms, and I'm currently running the stock 4.4.2 rom on the phone.
After the update, I got an error nearly every startup. Realizing I hadn't cleared the cache or data since I'd updated, I did this over the weekend and that error went away. First day of use had no problem, but yesterday the phone's battery drained 85% in just 3-4 hours. I put it on a charger at work, got through my dinner plans, and went to pair the phone to the car as usual last night.
Normally when I paired my Note II or S 4, there would be the usual deal, but when it wanted to access the address book, etc... there would be a check box for "don't ask me again". Left unchecked, the phone would disconnect and reconnect to the car fairly regularly. Obviously, I'm used to leaving that box checked and accepting. But after the wipe and reload of 4.4.2, I have no checkbox. And whether I accept syncing the phone book, etc... the phone isn't staying connected to the car!
Anyone else having this problem with 4.4.2? I'm starting to wish I hadn't upgraded past 4.4, since it seemed to work fine for my purposes. And I'm already tired of the problems upgrading seems to have caused.
Same problem to me on S4 I 9505.
The phone disconnect and reconnect to the car bluetooth module regularly (5 - 10 seconds) and when is connected from car's bluetooth can't acces the adress book at all.
I wish I hadn't update yesterday to 4.4.2 and have remained at 4.3 where everything was ok.
LE:
Tested now with my second phone (HTC Desire 600 dual sim) running 4.1.2 and everything it's ok.
Seems that the big problem is in the 4.4.2 not in the car, neither in the car's bluetooth preparation module.
Hope somebody will repair this bluetooth bug soon.
HATE GOOGLE FOR THIS!!! :crying:
After many hours of searching for an workaround about this bug/issue, seems that it's a Google bug, not a Samsung.
Same (plus many others) problems with bluetooth are present in last google 4.4.2 firmwares in Nexus 4 phones.
It's an older issue, has been reported to google since the date of 30.11.2013 and seems that google didn't find a solution for this since now.
Google forum 1
Google forum 2
After Android 5.0 upgrade my Note 3 has many bluetooth problems that stops me from using my smartwatches (Moto 360 and Pebble Time). Frequent dropped connection on bluetooth, both moto 360 and pebble can`t connect, i have problems with my car stereo, and sometimes when i push the back or home button on an app, nothing happens. Tried everything, wipe cache, phone reset, deleted cache from the Bluetooth and Bluetooth test app, factory reset the pebble and moto 360, no luck.
Android 5.0 is a big mess and i can`t use my bluetooth devices, that worked perfect on Android 4.4.4.
My phone is still in warranty, i have never done root on it, only installed stock updates, OTA, from Samsung.
I want now to downgrade back to Android 4.4.4 stock with ODIN. I want to download stock Android 4.4.4 for my Samsung Note 3 and flash it with ODIN. Can i do that?
Please help, Android 5.0 messed up my phone.
It's better to do a reset after every OTA update...
I personally feel the performance never goes down if I do a reset after update...
And I'm using my Moto 360 with my Aryamod Lollipop Note 3 (had no issues with stock Lollipop as well for 6 months)
Sent from my Nexus 7 using Tapatalk
I tried delete cache from Bluetooth and Bluetooth Test apps, factory reset from phone settings, reseted my watches Moto 360 and Pebble Time, deleted all paired bluetooth devices and paired again. Still connections are dropped, android wear says moto 360 is connected but watch is not, the same with Pebble drops connections, unable to connect, it ask for some bluetooth key, sometimes the pairing is gone by it self and i have to repair, etc., just a nightmare. Moto 360 and my car stereo worked perfect on Android 4.4. The Pebble Time is 3 days old, never worked fine on Android 5.0.
Now i did a full reset (wipe data) by restarting the phone into Recovery Mode. Contacted Samsung and i`m waiting for a reply.
I downloaded stock Android 4.4.2 from sammobile for my Note 3 LTE. If i can`t find a fix for bluetooth issues i will use ODIN and flash back the stock Android 4.4.2 ROM...
I can not believe that Samsung and Android will push out this update terrible. On the Pebble forums i see lots of users complaining about Android 5 ruined their bluetooth connections.
Just downgraded my Note 3 to Android 4.4.2 this morning. So far my Pebble Time works like a dream, no more dropped connection, no more unable cu connect, all bluetooth issues are gone.
Because i never rooted my Note 3 and downgraded to stock firmware, the downgrade process was pretty simple using ODIN, just uncheck F.reset.
great then!
Anturaju93 said:
Just downgraded my Note 3 to Android 4.4.2 this morning. So far my Pebble Time works like a dream, no more dropped connection, no more unable cu connect, all bluetooth issues are gone.
Because i never rooted my Note 3 and downgraded to stock firmware, the downgrade process was pretty simple using ODIN, just uncheck F.reset.
Click to expand...
Click to collapse
great then.. I believe there were no great features to miss Lollipop... other than the fact that Touchwiz looked better...
the biggest feature I would miss is Trusted device, so the Pebble can keep my phone unlocked and I don't need to type the PIN every time. Also S View cover issues are resolved with Android 5. So I am really not happy to downgrade. Did anybody receive any official statement from Pebble or Samsung where is the problem and when we can expect it to be resolved? There are several threads around like
sammobile.com/forum/showthread.php?t=27542
or
forums.getpebble.com/discussion/26926/bluetooth-connectivity-issue-after-android-5-0-update
but no statement
I own two smartwatches, Motorola Moto 360 and Pebble Time, and both not working on Android 5.0, but are working fine on Android 4.4.2. This is not Pebble fault. I had problems even with my car stereo with Android 5.0 , and now, after downgrade, all are working fine. My Pebble is connected for 2 days now, with no disconnect
I do like Android 5.0 and i like to keep my devices up to date, but i need bluetooth connection to work with all my devices.
Anturaju93 said:
I own two smartwatches, Motorola Moto 360 and Pebble Time, and both not working on Android 5.0, but are working fine on Android 4.4.2. This is not Pebble fault. I had problems even with my car stereo with Android 5.0 , and now, after downgrade, all are working fine. My Pebble is connected for 2 days now, with no disconnect
I do like Android 5.0 and i like to keep my devices up to date, but i need bluetooth connection to work with all my devices.
Click to expand...
Click to collapse
hey i just want to knw which firmware 4.4.2 u flashed ? and did u use LTE on 4.4.2 rom .... ?
my note 3 model is SM-N9005 and is the LTE version. I did use the last firmware available here http://www.sammobile.com/firmwares/database/SM-N9005/ROM/
L POF3 sol ce BT problems for most users......
There was OTA update last days that has resolved the bluetooth problems! Connection to Pebble is now stable!
yeah, switched to iphone 6 now. Samsung said they don't care if my watch is not working, they guarantee connections only with gear devices.
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Sent from my Nexus 6P using Tapatalk
glenb83 said:
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Click to expand...
Click to collapse
Hello,
Backup your data's and try to factory reset.
You can install a custom ROM, but I guess it doesn't fix drivers issues which are closed sources.
Otherwise you can downgrade to a 6.x stock firmware.
Option 1 and 3 needs you to unlock your bootloader. Backup important datas, unlocking bootloader wipe all datas!
Good luck...
glenb83 said:
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I suggest you fully wipe your phone and install the May Google image (N2G47O). There was a major BT rework introduced with 7.1.2 that fixed an issue just as you describe. I went 5-6 months without being able to connect with one of my cars (2014 Cadillac). When the 7.1.2 beta came out I did a fresh install and it immediately fixed the problem. BT has worked flawlessly since.
glenb83 said:
Hi all,
Since upgrading to Android 7.x, I've had problems connecting my phone to other Bluetooth devices, particularly my car heading it for hands-free. The headunit in one car works fine, the other car keeps connecting and disconnecting after about 1-2seconds in a continual loop. Before 7.x it was connecting fine. Even now my phone makes the notification sound of connecting when I'm in that car even when I choose 'forget this device' on both hu and phone, only way to stop the notifications is to turn bt off.
I've googled and found it's quite a common issue, but yet to find a solution. I joined the beta program and update everytime but yet to fix it.
My question is, will this problem be fixed if I install a custom rom like PureNexus or is it a flaw in 7.x affecting every rom? If that is the case, is it possible to downgrade to 6.x? I really want to be able to connect to my hu with hands free again, it's been months now with no luck!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You need a completely clean 7.1.2 install.
There is a setting somewhere (I don't know where) left over from previous OS version or app.
My phone was doing the exact same thing with my BMW, and only my BMW.
Clean install of 7.1.2 fixed the issue for me.
I wiped my 6P today hoping it would resolve my BT issues with my 2015 Toyota Highlander. No such luck, it still boots my Toyota in an endless loop until I disable the BT on the phone. The car works fine on my Samsung S3.
What is the process to do a Clean install of 7.1.2?
Hi there, I'm not sure if my issue can be resolved but I thought I would check. I have a Android 4.1.1 headunit which I used a lot when I first got 4-6 years. I stopped driving that car but have decided to take it out again and I notice that a lot of the apps don't seem to connect to the internet including Play Store, they all seem to say no internet connection. The only app that seems to work is Spotify. The once that don't work which I would like to use are: Google Play, Waze, & Firefox.
Is it possible to upgrade the OS if this could be what's causing the issues as apps get updated ? Or is there a way I can get working apps for this device if upgrading is not an option?
hi guys ,I have the p40pro plus with gems working fine. I have just got the new ticwatch pro 3 GPS and its a great watch. the problem is I can't log into the playstore on my watch as it won't allow me to enter my email. So I can't use the playstore or google assistant. Does any one have any ideas or workaround??
Any updates on a fix for this??
How to Pair Android Wear Watches to New Phones without Factory Resetting
A tutorial on how to pair Android Wear smartwatches to a new phone without factory resetting. Also useful if you flash a custom ROM and don't want to reset!
www.xda-developers.com
Good pairing information! Cheers
I doubt you will have much luck with this since the P40 does not have Google Services installed, it will therefor not be able to get the account information from your P40.