All the threads I've found on this seem a little dated. Anyone try Drivelink with an S4 now that KitKat has been released. Doesn't work at all for me. Was able to trick it into working with my JVC previously. I reinstalled hoping that would fix it. Shame...I was really hoping KitKat would miraculously fix this problem.
jmfrost said:
All the threads I've found on this seem a little dated. Anyone try Drivelink with an S4 now that KitKat has been released. Doesn't work at all for me. Was able to trick it into working with my JVC previously. I reinstalled hoping that would fix it. Shame...I was really hoping KitKat would miraculously fix this problem.
Click to expand...
Click to collapse
Even stranger...Somehow Drivelink is associated with the phone app. Every time I made a call, Drivelink would force close. You hit ok and it re-appeared over and over. Had to finally restart the phone and uninstall it.
Sadly Samsung didn't include the TMServerApp.apk File that is needed for drivelink to run properly in the Kit Kat build for the Galaxy S4.
There is no way to make this work at the moment and currently there is no one working on it.
thedoginthewok said:
Sadly Samsung didn't include the TMServerApp.apk File that is needed for drivelink to run properly in the Kit Kat build for the Galaxy S4.
There is no way to make this work at the moment and currently there is no one working on it.
Click to expand...
Click to collapse
That's really a shame. The whole reason behind me choosing this head unit was because of their "close relationship" with each other during development. But if I have to replace the HU every time I want to replace my phone, then forget it. Guess I'll be returning my S4. I hate Apple, but it's things like this that force me to stick with them.
Some Sony Xperia Devices also support the Mirrorlink technology.
I am currently staying on Android 4.3, because Mirrorlink works there, but I will probably buy a Xperia Z2 because it should also work with Mirrorlink.
thedoginthewok said:
Some Sony Xperia Devices also support the Mirrorlink technology.
I am currently staying on Android 4.3, because Mirrorlink works there, but I will probably buy a Xperia Z2 because it should also work with Mirrorlink.
Click to expand...
Click to collapse
I tried my S4 before the KitKat upgrade with marginal success. It kept wanting to crash. I was able to get some things to work on the screen, but making the maps shortcut work for directions was a fail for me. I know the HU was rated for use with the S3, but I had hopes I could make the 4 work. Wonder if KitKat breaks any of the S3's that were previously working with it? JVC hasn't put out any new firmware in over a year either.
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?
Hi team,
I am using Samsung Galaxy Note 3 Neo(SM-N750) INU(Indian version) running Android 4.4.2 Kitkat Stock ROM.
Currently my moto360 is not able to discover from Bluetooth but the watch is working fine with other phone.
This issue is occurred after I paired my pebble with the phone and installed pebble software.
I uninstalled and pebble software and rebooted the phone / watch many time and tried , no luck .
Tried reinstalling the moto connect and Android wear on phone.
I noticed both pebble and moto360 wont work together , there was an issue connecting pebble(watch not discovered from Bluetooth) when I first install the moto360. There moto360 work but not pebble now pebble is working but not moto360.
Can you guys help me how to resolve this ? I believe the phone factory reset will resolve but any alternate solution to this?
Currently I would like to connect my moto360 only and I really appreciate if you help on this & is any option to work both pebble and Android wear together?.
Regards,
Tintu Kuruvilla
Tintu Kuruvilla said:
Hi team,
I am using Samsung Galaxy Note 3 Neo(SM-N750) INU(Indian version) running Android 4.4.2 Kitkat Stock ROM.
Currently my moto360 is not able to discover from Bluetooth but the watch is working fine with other phone.
This issue is occurred after I paired my pebble with the phone and installed pebble software.
I uninstalled and pebble software and rebooted the phone / watch many time and tried , no luck .
Tried reinstalling the moto connect and Android wear on phone.
I noticed both pebble and moto360 wont work together , there was an issue connecting pebble(watch not discovered from Bluetooth) when I first install the moto360. There moto360 work but not pebble now pebble is working but not moto360.
Can you guys help me how to resolve this ? I believe the phone factory reset will resolve but any alternate solution to this?
Currently I would like to connect my moto360 only and I really appreciate if you help on this & is any option to work both pebble and Android wear together?.
Regards,
Tintu Kuruvilla
Click to expand...
Click to collapse
You should try to factory reset your watch, not your phone. Connect your watch like is brand new. Do the same with your pebble after everything is ok with moto.
Also you should delete cache and data from your pebble watch apk.
Hi Calinormy,
Thank you very much for your prompt support.
Now My Moto360 connected and working fine after the watch reset.
I tried a factory reset with my pebble and installed pebble app on my phone.
Now moto works fine but pebble is not able to discover.
I think both watches wont work together and I believe If i uninstall Android wear and moto connect from phone(clear the cache too) then probably pebble will work but not moto.
Anyhow this helps and many thanks to Calinormy.
Regards,
Tintu Kuruvilla
calinormy said:
You should try to factory reset your watch, not your phone. Connect your watch like is brand new. Do the same with your pebble after everything is ok with moto.
Also you should delete cache and data from your pebble watch apk.
Click to expand...
Click to collapse
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, I have a problem
I have a pair of gear iconx, but cannot pair with them, the phone sees the bluetooth device, connects for half a second then disconnets immediately
Also I cannot install the software samsung gear (or better, installed but the app is not compatible because finds the OS is modified). Same as the samsung gear iconx app... is there any way to solve the problem?
there is something with bluetooth that doesn't go?
zazolo said:
hi, I have a problem
Also I cannot install the software samsung gear (or better, installed but the app is not compatible because finds the OS is modified). Same as the samsung gear iconx app... is there any way to solve the problem?
there is something with bluetooth that doesn't go?
Click to expand...
Click to collapse
Refer to my thread here if you are using a custom ROM on the S5. A slight text change in a file and then the Gear app will run.
https://forum.xda-developers.com/gear-s3/help/gear-s3-samsung-phones-custom-rom-t3585024