I have a 2011 Jeep Grand Chreokee. When I first got the phone, it paired fine and I was able to make and receive calls through the BT. I had this setup for about 1-2 days. I then rooted the phone with the stock ROM only removing bloat ware...now I cannot connect via bluetooth back to the car. It seems to connect then disconnect me right away. Ideas?
I know this seems obvious but have you tried unpairing and repairing the phone to the car? Sometimes bluetooth can get fidgety and most of the time it requires you to repair the device. In my experience that generally solves the issues I have had with bluetooth.
Any time I have factory restored my phone I have had to repair it to any Bluetooth devices it was once connected to. Not sure if the Bluetooth address changes for the phone or not on a reset or ROM change, but it seems to be the case. My Infiniti G37s has Bluetooth and I experienced the same issue as you, pair it again and see if that helps.
Thanks for replies...I tried to repair about 6 different times...same result. It seem that the phone and audio connections both connect for about 2 seconds, then the phone disconnects.
Funny, I wanted to try this but kept forgetting. So I just went down to my garage and tried it, and it paired successfully on the first try. Tried making a call via number/phonebook and it all worked.
I'm rooted running Das BAMF 1.3, and paired it with a '11 Sonata Limited.
So I got it working...but without the phone book downloaded. The issue is in fact when it tries to download the phone book. Need to get another phone loaded up with my contacts and do a sync to get phone book loaded to car.
DieselvRR said:
So I got it working...but without the phone book downloaded. The issue is in fact when it tries to download the phone book. Need to get another phone loaded up with my contacts and do a sync to get phone book loaded to car.
Click to expand...
Click to collapse
Did you do anything to get it working?
When the device asked me to allow connection to download the phone book, I declined, only then would it pair properly.
I think I figured it out, I have the Infiniti G37, when I rooted & re-paired the Bluetooth, somehow I ignored the question when it popped up asking to "allow" or "deny" the connection.
Yesterday during the whole 4G fiasco, I reflashed & had to re do everything this morning, when I paired my BT, it asked me whether to allow & this time I clicked allow & my BT connects & stays connected fine now.
My question is, is there a way to delete the BT pairing on the phone without having to completely wipe the phone with a reflash?
ruddogg said:
I think I figured it out, I have the Infiniti G37, when I rooted & re-paired the Bluetooth, somehow I ignored the question when it popped up asking to "allow" or "deny" the connection.
Yesterday during the whole 4G fiasco, I reflashed & had to re do everything this morning, when I paired my BT, it asked me whether to allow & this time I clicked allow & my BT connects & stays connected fine now.
My question is, is there a way to delete the BT pairing on the phone without having to completely wipe the phone with a reflash?
Click to expand...
Click to collapse
nevermind, I just found the answer
http://support.vzw.com/clc/devices/knowledge_base.html?id=39262
just hold down "paired"
I believe the issue is just with the MyGig radio on the Chrysler products. I have a SRT8 Magnum with the MyGig and allowing it to download the address book "Breaks" the B.T. connection. I don't know what the issue is? Perhaps too much information being sent to the MyGig and it "locks up"?
I also have a Ford Focus for a daily driver and allowing it to download the Address Book over the phone has no such issue.
DieselvRR said:
When the device asked me to allow connection to download the phone book, I declined, only then would it pair properly.
Click to expand...
Click to collapse
It does it on my aftermarket Kenwood double-din unit, too. I've seen it happen on several Ford units too.
usafle said:
I believe the issue is just with the MyGig radio on the Chrysler products. I have a SRT8 Magnum with the MyGig and allowing it to download the address book "Breaks" the B.T. connection. I don't know what the issue is? Perhaps too much information being sent to the MyGig and it "locks up"?
I also have a Ford Focus for a daily driver and allowing it to download the Address Book over the phone has no such issue.
Click to expand...
Click to collapse
I updated my 430N radio with the latest firmware update and phone book downloaded and BT is working without getting disconnected.
Thanks
Thanks for that info. Although I can't do it as I have the "MyGig" retro-fitted into my 07 SRT. So, if I apply the "official update" I will lose GPS time and a bunch of other things.
But, nice to know it works.
DieselvRR said:
I updated my 430N radio with the latest firmware update and phone book downloaded and BT is working without getting disconnected.
Thanks
Click to expand...
Click to collapse
Hi!
So I've managed to connect a USB reciever (made for PCS) to the tablet USB port and got my controller working on the tablet. Literally, working. Buttons are responding and it controls everything.
However, trying to play GTA Vice City has proven futile. It appears the controller is constantly transmitting a "right camera movement" to the tablet making it "turn around the character". No matter what I tried, it appears to simply be "jammed" with this.
Since no software was installed, and the controller is basically working with builtin drivers, I was wondering whether someone tried to do the same, had the same issues and found a work around?
I had the same issue. This is a known problem, described in several topics. If your Transformer is rooted, the solution is provided here: http://forum.xda-developers.com/showthread.php?t=1792531. It's for Nexus, but works for Transformers.
For non-rooted devices, I'm afraid there is no solution.
hello guys,
i have a recent problem that i could not find a way to fix. the thing is, when i use the stick during the it's connected to tv(seeing the android on tv) it's ok. but when i switch the hdmi interface to some other device like ps3, the stick is stuck/frozen after a few minutes, so when i switch back to android i see nothing. it was identified here as mk802iii clone, and i tried the 1.7 finless rom, as well as 2dark4u's rom. none helped.
do you have any workarounds for this particular problem ?
thanks in advance.
Hi!
I have a S2 (I9100G) since 2 years.
Before switching on CyanogenMod (2013 september), I don't had any problem to connect aWiimote to play some games (via Bluetooth).
Since 2013 september, I use a I9100g with CM (10.1.3 during january. Before I was in 10.1.3RC-1 and RC2 and before in 10.1.2).
Since, impossible to use Wiimote and WiimoteController, I have a error message.
So, I bought a Wamo Pro gamepad. It work on friends S2, S4 or android tablet. But impossible to connect the Gamepad (bluetooth paring) to my phone.
The phone see the bluetooth device, I select the device, it appears that connect, but no.
It seems there is bluetooth problem on cyanogenmod without solution (driver problem).
I try almost each nightlies, without succes.
Do you have any idea?
I don't want uninstall CyanogenMod...
Unfortunately, I can't post in the CM11 dev's topic, I don't have 10 posts at this time on this forum.
thanks for your help.
Any idea?
Hello all,
My shield controller worked great when using KitKat.
I had no need for it for a while - but wanted to use it today. Since I used it last time, I have updated my wifi Shield Tablet to 5.0.1 (rooted). Th Lolipop update included a factory reset - so my original controller pairing was lost.
So I tried to pair it again - but the pairing did not work (the unit and the controller both just blink - but they do not connect). The I tried to select "forget all controllers" in the controller setup - when I click "Forget" at the prompt, the controller app seems to be crashing, as I get a message saying that Shield Controller Stopped Working...
I tried everything (factory reset the controller, multiple restarts, wipe controller data via titanium backup etc.) but no luck.
The controller does not connect. The fact that the app crashes when I want to forget paired controllers suggests that this is a software issue. But what is the issue? And how do I fix it?
Any ideas would be very welcome...
Thank you all
Gadgetguy2005 said:
Hello all,
The controller does not connect. The fact that the app crashes when I want to forget paired controllers suggests that this is a software issue. But what is the issue? And how do I fix it?
Click to expand...
Click to collapse
I had a similar issue happen to me when I first got my controller. The key difference is that my blink-of-death came after a firmware update for the controller. I tried for a while to find answers on Nvidia's page, but the only solution was to get a new controller. Have you reached out to Nvidia support to see what they say? If it's too late to return the unit to wherever you purchased it, Nvidia might offer to replace it directly. My 2nd controller came and updated perfectly. On a side note, how did you perform a factory reset on the controller? I wasn't able to find any information on that.
adampdx said:
I had a similar issue happen to me when I first got my controller. The key difference is that my blink-of-death came after a firmware update for the controller. I tried for a while to find answers on Nvidia's page, but the only solution was to get a new controller. Have you reached out to Nvidia support to see what they say? If it's too late to return the unit to wherever you purchased it, Nvidia might offer to replace it directly. My 2nd controller came and updated perfectly. On a side note, how did you perform a factory reset on the controller? I wasn't able to find any information on that.
Click to expand...
Click to collapse
I got the controller a while ago (not even sure from where) - and it is too late to return. I did not update the controller firmware. The controller worked fine with Kitkat
And the fact that the controller app (on the Shield) crashes when I want to forget all controllers suggests to me that this is a software issue on the tablet
But I may be wrong. Lets see if others have other suggestions - I will also contact Nvidia about this.
Thank you!
Ps factory reset is by holding the nvidia button on the controller for a long time - I think 30 seconds
Update - cleared the controller app cache again, restarted and now it works. Really weird. Not sure why. But it works - that's all that counts