Howdy all!
I'm running CM10.1-nightly and I've been trying to connect my inPulse SmartWatch to my N4, without success. It appears to pair successfully, but the client app never connects and I can't send any commands to it. Has anyone successfully paired their device with an inPulse watch? I wonder if it has anything to do with the changes in the bluetooth stack in 4.2.2?
jsylvia007 said:
Howdy all!
I'm running CM10.1-nightly and I've been trying to connect my inPulse SmartWatch to my N4, without success. It appears to pair successfully, but the client app never connects and I can't send any commands to it. Has anyone successfully paired their device with an inPulse watch? I wonder if it has anything to do with the changes in the bluetooth stack in 4.2.2?
Click to expand...
Click to collapse
I have the same problem too. I upgraded my Motorola Atrix 2 to 4.2.2 and also cannot connect. My Ubuntu netbook however has no problems. I'll reply back here here if I find anything, but I'm not too optimistic.
Hi guys. I emailed Alerta a while back about the compatibility issues with newer versions of Android. I emailed in February of this year...
"Good afternoon. I wonder if you plan to update the inpulse Android app to
run correctly on 4.2 Jellybean? I have tried several times after updating
my Nexus S to 4.2 but the app simply will not connect to my watch. I would
really like to be able to use the watch. I used it all the time before the
Android system update and I truly miss it.
As an added note, if it helps, I am running Cyanogenmod ROM's and have been
for years. Never had an issue with my watch connecting until 4.2.1. I would
try the forums but those have been taken over by bots and have become
pointless.
I will appreciate your reply, should I receive one.
Your paying customer,"
On March 01, 2013 I received this reply...
"Thank you for reaching out to us. We are not supporting further development on the inPulse Android app.
Best regards,
Asad"
Guess we can chalk it up to another wasted $100. Jerks.
Related
Hey all,
Recently got my n4 and am currently running cm10 nightlies on it, but today I picked up our new car (Hyundai i30 premium) which has bluetooth built into the audio system and I can't get my n4 to sync with it properly. My partners Desire HD syncs no problems and all her contacts phone book everything shows up fine. My n4 wouldn't even sync originally then I just kept retrying and eventually it synced but nothing really works, music won't play through the speakers (the audio system just sits there waiting for music and nothing happens) my phonebook etc don't show up (after me allowing them permission) I can't even make calls.
I have heard that the n4 has some bluetooth problems but nothing this bad, anyone have any suggestions that I can try? Happy to go to another ROM if that will help??
Thanks,
Hosh
this build has serious BT issues. i can't even find a mouse that works. wait and see what the 4.2.2 update brings.
I own a Hyundai Elantra GT which is the US version of the i30 - I didn't seem to experience any issues when I paired it this morning, but I"ll double check when I get out of work this afternoon that the contact sync is working. I am, however, on the stock rom.
I own a 4 day old Dodge Journey and it pairs with no issue to Uconnect.
Try a different rom?
If thats not it, then its your hardware.
The new bluetooth stack in Android 4.2 is causing a lot of issues. Personally, I don't have any problems connecting to UConnect (Jeep Grand Cherokee) or my SmartMini (bluetooth music streaming).
I am waiting on delivery for my MetaWatch, there have been complaints that 4.2 isn't connecting well with it but I guess we'll see. CM10.1 users don't seem to have as many problems. I'm running Xylon w/ Franco r53.
I had the same problem with Chevrolet captiva until I have installed custom ROM and is working perfect now.I have tried every custom ROM and is OK with all.
I have this problem but there is a way around it (for me anyway).
Download Bluetooth file transfer from the market.
Delete the connections with your car. Both on the phone and your car.
Open Bluetooth file transfer. Select the Bluetooth screen.
Make a connection. The default android Bluetooth will ask for a password. Don't enter it. Instead go to your recent apps and select Bluetooth file transfer. Put the password in the request screen the app supplies.
Bluetooth file transfer should pair the devices and make a connection.
Once done. Kill Bluetooth file transfer as you won't be able to exit.
You can then uninstall Bluetooth file transfer if you want (although I tend to keep it for when I change ROMs or have to do a factory reset etc).
Hope this works for you
Sent from my Nexus 4 using xda premium
Hey all,
Sorry for the late reply, been away for the weekend. Thanks for all the advice, tried them all and no luck. Will try out a mates n4 tomorrow and see if he has any luck syncing with the car, if he does might just flash roms again.
after flashing a new rom, I had problems pairing w/bluetooth and connecting w/wi-fi. I fixed the problem by restoring my system settings w/titanium backup thanks to someone's suggestion.
Seems the only thing that worked for me is when it asks to sync my phonebook I have to say no, if I say yes it seems to freeze the whole thing. Makes me think if I click yes I might just need to give it 10-15 mins to sync, might try that tomorrow. But for the moment at least it's half working!
I'm working with a Nexus 7 (2013) and a Nexus 4. I've had both devices for quite awhile, the 4 for well over a year and the 7 for a year. Both are rooted and using stock ROMs, 4.4.4.
I have the two devices Bluetooth paired and sometimes connect them. For the most part, over the last year, there have been no problems doing that. Once in awhile, they won't connect, but if I reboot, they will. Now, all of a sudden, I can't get them to connect under any circumstances. They're paired. But they won't connect. They both connect to an external Bluetooth speaker and the phone connects to my car bluetooth. That happens with 100% reliability. But these devices just won't connect with each other. And I need them to for certain work related purposes.
What could have happened?
I've unpaired and repaired them a few times. I've rebooted both devices. Potentially competing Bluetooth devices (like my car and the speaker I mentioned) are turned off. The devices aren't connected to any other Bluetooth devices.
Strangely, someone I work with who's doing the same sort of thing (and whose urgency to make them work together is greater than mine) with the same exact devices as I am is having the exact same problems.
What could be going on? Please let me know if you have any ideas.
Thanks.
Same exact problem here with my Nexus 4; rooted, stock ROM, no problem paring with Bluetooth, but unable to connect. I just noticed this today when I was trying to connect to my OBD2 device. This has worked since I bought the phone a year ago. I only use one app, and not very often, so I can't pinpoint the exact time the problem started, but I am pretty sure it would be in the time-frame of the 4.4.3 or 4.4.4 update. I also tried rebooting, re-pairing the hardware with the phone, enabling and disabling Bluetooth, etc..
pjc123 said:
Same exact problem here with my Nexus 4; rooted, stock ROM, no problem paring with Bluetooth, but unable to connect. I just noticed this today when I was trying to connect to my OBD2 device. This has worked since I bought the phone a year ago. I only use one app, and not very often, so I can't pinpoint the exact time the problem started, but I am pretty sure it would be in the time-frame of the 4.4.3 or 4.4.4 update. I also tried rebooting, re-pairing the hardware with the phone, enabling and disabling Bluetooth, etc..
Click to expand...
Click to collapse
Thanks for the commentary, pjc123. At least someone said something.
I restored one of my Nexus devices to stock 4.4.3, then 4.4.4. Didn't change anything. Maybe I need to take a couple of them back to 4.4.2 or earlier and see what happens. But AFAIK, my friend who has the same problem hasn't ever even updated to those versions of the OS. And it worked fine for him, doing these Bluetooth connections on no less than a weekly basis for a year.
Google's tech support, fwiw, told me that the first thing I needed to do was to update to 4.4.4. Not that I took that as anything other than their reading off a script.
Please let me know if you ever figure anything out with this. I'll report here if I do, too.
Well, as it turns out it was my fault for not checking the Xprivacy security settings; I am brand new to that app. After wasting a good part of the day, I discovered that the Torque app for my OBD2 reader needs both "Identification (device)" and "Network(addresses)" permissions for the Bluetooth device to show up within the app so it can be connected to. Once I gave those permissions it was back to working OK again.
pjc123 said:
Well, as it turns out it was my fault for not checking the Xprivacy security settings; I am brand new to that app. After wasting a good part of the day, I discovered that the Torque app for my OBD2 reader needs both "Identification (device)" and "Network(addresses)" permissions for the Bluetooth device to show up within the app so it can be connected to. Once I gave those permissions it was back to working OK again.
Click to expand...
Click to collapse
Interesting. I temporarily turned XPrivacy off just for that purpose. The app that's failing for me wasn't being protected, anyway, but it doesn't matter. I can't even get to that point, because the devices don't connect, even though they're paired. Furthermore, only one of my devices even has XPrivacy installed. I can't get any two of my, or my friend's, Nexus devices to connect, even though they're all paired. And they all used to.
I'm waking up this thread again to see if anyone has any ideas. I just can't connect two Bluetooth devices anymore by using the list of Bluetooth devices in settings on a Nexus device. This prevents an app that's dependent on that from working.
I CAN connect two devices via Bluetooth using ES File Explorer and see the contents of the other device and make file transfers. But the Bluetooth icon remains unlit and the connection isn't made in the settings. Maybe it's a different aspect of Bluetooth. When I close the connection with ES File Explorer, the toast says that the OBEX connection has been discontinued.
Why would I be able to connect two Nexus devices regularly for a year, then not be able to anymore?
I've tried to get Google support on this. Unlike some companies who provide inept support, even laughably so, Google just blows off the notion altogether.
Some months later...
This problem remains unresolved. I've now tested this on multiple devices (about ten of them) running various different versions of Android. I just tried it today with another, a stock, factory state N4 trying to connect to a stock, factory state N7 (2012). I wiped the devices, reinstalled the OS and then tried to pair and connect as the very first act on the clean systems once I got past the initiation routine.. I even loaded a few different versions of Android from distant past (4.2) to present. I CAN NOT connect two paired Android devices using Bluetooth, even if they're successfully paired and Bluetooth is turned on for both devices. All these devices connect fine with things like external speakers and cars. I've shown this to Google employees, some of whom have tried it on their own devices. Nobody succeeds.
As mentioned earlier in the thread, this used to work every time on every set of paired devices, regardless of the Android version.
What could possibly be going on here?
I struggled with this for awhile today. Same symptom: the devices can pair, but will quickly go from "Conecting..." to "not connected". I eventually stumbled on the solution: one device must have internet tethering enabled. This setting is in the "Tethering & portable hotspot" section, not in the bluetooth settings. This will enable the two devices to connect, and it will also enable the second device to use the "Internet access" feature in the bluetooth configuration for its connection with the first device. Hope that helps!
For those anxious to get 4.4.4 you might try liquidsmooth which now incorporates it and runs on most if not all moto-x's. It's been upgraded to 4.4.4. Unfortunately, bluetooth is still not working correctly for me and if I try to pair the phone with my car, the car's system goes into a slow endless loop where the phone is connected and then disconnected. I am going to try to see if there is some way to get the phone working with my car....it's very frustrating because the moto-x has never connected correctly (galaxy nexus was flawless in this regard).
I am guessing that it isn't built on the 444 kernel, so, don't get too discouraged yet
Sent from my Nexus 7 using Tapatalk
ghstudio said:
For those anxious to get 4.4.4 you might try liquidsmooth which now incorporates it and runs on most if not all moto-x's. It's been upgraded to 4.4.4. Unfortunately, bluetooth is still not working correctly for me and if I try to pair the phone with my car, the car's system goes into a slow endless loop where the phone is connected and then disconnected. I am going to try to see if there is some way to get the phone working with my car....it's very frustrating because the moto-x has never connected correctly (galaxy nexus was flawless in this regard).
Click to expand...
Click to collapse
What year make and model do you have? I have a 2011 Ford Edge and 2011 Ford Fusion, both of which use Ford Sync (Suck), and I have no issues with either.
Also, are you stock, or running a custom ROM? You seem to be running a custom ROM, and in that case, all bets are off.
jaykresge said:
What year make and model do you have? I have a 2011 Ford Edge and 2011 Ford Fusion, both of which use Ford Sync (Suck), and I have no issues with either.
Also, are you stock, or running a custom ROM? You seem to be running a custom ROM, and in that case, all bets are off.
Click to expand...
Click to collapse
It is 4.4.4 kernel. I think I've found the issue and it's unique to "techies". I have a pebble smart watch which uses google...the connection to the car system (2014 MB) uses bluetooth. If I don't wear my watch, the connection to the car works...no loops/etc. When I wear the watch in the car, the car/phone link goes all screwy. I suspect that one of the bluetooth stacks doesn't like to share....and I'd bet it's the moto-x stack which can either use the bluetooth or the car link, but not manage both together, even though everything is paired correctly. I haven't checked to see if pebble and the MB use the same protocols...it may be that they both share txt even though I only need phone on the car link.
I'll post more when I get further into this....I just stumbled on the cause today when I didn't wear the watch and repaired the phone with the 4.4.4 kernel.
Next time, get a Cadillac.
FORD -Fix Or Repair Daily
abuttino said:
Next time, get a Cadillac.
FORD -Fix Or Repair Daily
Click to expand...
Click to collapse
I've heard them all, but we've had precisely zero issues with the Fusion, and one with the Edge that was fixed free of charge due to silent recall.
My only issue with Sync is that my Fusion has the Gen 1 version, and the most recent software update removed the key reason I chose this car over the then comparable Sonata. Without that feature, I would have gone with the Sonata.
Hi All
Just got upgraded to an S4 i9505 for my work phone and I'm happy to have an Android device over the Blackberry I had before.
My phone is already rooted and setup to the way I like it.
The FEAR I had came true when pairing the phone with my car. I have a F30 BMW with extended Bluetooth option, which enables you to have like a mobile office on the iDrive.
With the Blackberry I was able to :
1. See all my Contacts
2. See my SMS/Text messages
3. Able to play music via Bluetooth
4. Able to read e-mails, both my exchange and gmail
With the Samsung S4 I can do all of the the above but can't read my e-mails anymore. This feature are very handy since I drive allot for work and having the iDrive option to read the e-mail back to you helps allot to keep up with whats going on at work.
Have searched via google, XDA and some BMW forums, but have not yet seen an option that works. It appears that it's an android issue with regards to MAP (Message Access Profile) not working the same way in Android as it does with Blackberry.
My phone is running KK 4.4.2 Stock ROM, my car has been updated to the latest Bluetooth software. Do anyone know of any third party App or xposed type framework solution to get the working?
Many thanks for any suggestions in advance.
Any help or suggestions?
Nope but nice car btw
189cutter said:
Nope but nice car btw
Click to expand...
Click to collapse
Thanks [emoji4]
My Bluetooth keeps saying wrong pin with all my devices and even the car. Any ideas on how to troubleshoot this! Ps. I'm on 4.5.8 cleaned installed.
Thanks
Hello,
I'm getting the same issue with my OnePlus5.
I'm not able to connect any device with bluetooth and each time I try to pair a device (car, smartwatch, other smartphone galaxy S6), the other device shows a pin code and asks if the same on the OnePlus5 but nothing happens on my OnePlus5.
after few seconds (about 30), I get pairing failed message saying "Couldn't pair with DeviceName because of an incorrect PIN or passkey."
Could you please help how to solve the issue. Thanks in advance.
My Device is:
OnePlus 5
OS / Version : OxygenOS 4.5.14
Recovery (stock/twrp/autre) : stock
Root (oui/non) : no
not getting passkey/pin accept prompt on the phone. Smartwatch & phone see one another and the phone attempts pairing, while the smartwatch displays code, but then the phone does nothing, timing out and giving wrong code message. Running 5.02
How can I get the phone to take the next step, to display a passkey confirm prompt? Have I defeated the popup with some other sw e.g. Malware bytes?
p1gnone said:
not getting passkey/pin accept prompt on the phone. Smartwatch & phone see one another and the phone attempts pairing, while the smartwatch displays code, but then the phone does nothing, timing out and giving wrong code message. Running 5.02
How can I get the phone to take the next step, to display a passkey confirm prompt? Have I defeated the popup with some other sw e.g. Malware bytes?
Click to expand...
Click to collapse
It didn't work for me with my smartwatch if I choose Bluetooth LE.
What's your setup?
strongst said:
It didn't work for me with my smartwatch if I choose Bluetooth LE.
What's your setup?
Click to expand...
Click to collapse
OP5 with 5.02 Oos, rooted, twrp recovery.. what do mean by setup?
p1gnone said:
OP5 with 5.02 Oos, rooted, twrp recovery.. what do mean by setup?
Click to expand...
Click to collapse
Exactly that plus which Smartwatch and Bluetooth or Bluetooth LE
strongst said:
Exactly that plus which Smartwatch and Bluetooth or Bluetooth LE
Click to expand...
Click to collapse
LG Urbane3520 and the system Bluetooth. What do you mean by Bluetooth LE?
p1gnone said:
LG Urbane3520 and the system Bluetooth. What do you mean by Bluetooth LE?
Click to expand...
Click to collapse
How do you connect to the watch? With Bluetooth or Bluetooth LE. My Pebble Time Steel provides both, but with LE im also getting no pass key. That's why I'm asking about connection
strongst said:
How do you connect to the watch? With Bluetooth or Bluetooth LE. My Pebble Time Steel provides both, but with LE im also getting no pass key. That's why I'm asking about connection
Click to expand...
Click to collapse
My system/stock Bluetooth pairs just fine with headsets, GoogleHome, my cars A3 & A4, even with my Dell Laptop
Asking for if anyone with similar OP5/5.02 has had similar experience so to see if it is intrinsic or due to other sw interactions.
p1gnone said:
My system/stock Bluetooth pairs just fine with headsets, GoogleHome, my cars A3 & A4, even with my Dell Laptop
Asking for if anyone with similar OP5/5.02 has had similar experience so to see if it is intrinsic or due to other sw interactions.
Click to expand...
Click to collapse
Seems like a watch problem, cause I have also an audi A4(2016) and Bluetooth headsets and several connections to other cars and Bluetooth hands free
Maybe someone with the same Smartwatch and op5 can test?
strongst said:
Seems like a watch problem, cause I have also an audi A4(2016) and Bluetooth headsets and several connections to other cars and Bluetooth hands free
Maybe someone with the same Smartwatch and op5 can test?
Click to expand...
Click to collapse
New watch. Wife got it as a tester. Not sure its even in the market yet. Who among your associates has an OP5? Me? none.
Watch generates&displays passkey, sees phone
Phone sees watch
User starts pairing
Phone never prompts passkey acceptance
So this seems like the phone is the problem? not to me.
[other background] Paired just fine with an iphone7
SO your ultimate contribution was to suggest that find someone with the same hardware combo? LOL. The point of a forum is for far flung users to share related experience and insights.. SO your ultimate contribution was to suggest find someone with the same hardware combo? LOL.
p1gnone said:
New watch. Wife got it as a tester. Not sure its even in the market yet. Who among your associates has an OP5? Me? none.
Watch generates&displays passkey, sees phone
Phone sees watch
User starts pairing
Phone never prompts passkey acceptance
So this seems like the phone is the problem? not to me.
[other background] Paired just fine with an iphone7
SO your ultimate contribution was to suggest that find someone with the same hardware combo? LOL. The point of a forum is for far flung users to share related experience and insights.. SO your ultimate contribution was to suggest find someone with the same hardware combo? LOL.
Click to expand...
Click to collapse
It was not my ultimate contribution to find one with the same watch, just a suggestion, but... It's a new watch, new to the market and it didn't pair with your op5 but with an iPhone 7. Maybe it's a problem of the watch if it's new several phones wouldn't supported maybe.
And since other devices pair successfully with your op5, where to look further? Maybe you have another android phone and can check?
strongst said:
It was not my ultimate contribution to find one with the same watch, just a suggestion, but... It's a new watch, new to the market and it didn't pair with your op5 but with an iPhone 7. Maybe it's a problem of the watch if it's new several phones wouldn't supported maybe.
And since other devices pair successfully with your op5, where to look further? Maybe you have another android phone and can check?
Click to expand...
Click to collapse
Not due to the iphone7 pairing. It's unpaired now and it returns to stock when unpairing.
So yeah, will pair/attempt with the wife's S9+ this evening.
Thanks