Hi there,
I cannot get my Universal Bluetooth Mobile Keyoard to work with my Sony Xperia Tablet Z. Sometimes it will ask for a code, and before I can enter it an error message pops up saying "cannot communicate with device". Other times I am able to enter the code with no errors, however, key presses are not registered at all on the tablet.
The most confusing part about this problem is that my Microsoft Wedge Mobile Keyboard works perfectly well with my tablet. And what's more, when the Wedge keyboard is connected, the bluetooth module in quick settings displays the Wedge kayboard name. While, when the Universal keyboard is connected, the bluetooth module in the quick settings doesn't seem to pick it up. I have also tried using both keyboards with my Nexus 5 running Android 5.0, and both keyboard work fine. Even more confusion!
It's important to note that while trying to connect either device, I've unpaired the other from the tablet. Basically, only one keyboard is paired with my tablet at any given instance. Therefore, this is not the issue.
I've heard that there was a bug in 4.3 Jellybean which caused some connectivity issues with bluetooth devices. My tablet is running a Cyanogenmod 4.4.4 Kit-Kat ROM, so that issue shouldn't be present here (at least, I think...)
Has anyone encountered this problem before, or have a solution?
Cheers!
ttarpey said:
Hi there,
I cannot get my Universal Bluetooth Mobile Keyoard to work with my Sony Xperia Tablet Z. Sometimes it will ask for a code, and before I can enter it an error message pops up saying "cannot communicate with device". Other times I am able to enter the code with no errors, however, key presses are not registered at all on the tablet.
The most confusing part about this problem is that my Microsoft Wedge Mobile Keyboard works perfectly well with my tablet. And what's more, when the Wedge keyboard is connected, the bluetooth module in quick settings displays the Wedge kayboard name. While, when the Universal keyboard is connected, the bluetooth module in the quick settings doesn't seem to pick it up. I have also tried using both keyboards with my Nexus 5 running Android 5.0, and both keyboard work fine. Even more confusion!
It's important to note that while trying to connect either device, I've unpaired the other from the tablet. Basically, only one keyboard is paired with my tablet at any given instance. Therefore, this is not the issue.
I've heard that there was a bug in 4.3 Jellybean which caused some connectivity issues with bluetooth devices. My tablet is running a Cyanogenmod 4.4.4 Kit-Kat ROM, so that issue shouldn't be present here (at least, I think...)
Has anyone encountered this problem before, or have a solution?
Cheers!
Click to expand...
Click to collapse
I think it is an issue of CM. Try stock ROM or CM12.
Rootk1t said:
I think it is an issue of CM. Try stock ROM or CM12.
Click to expand...
Click to collapse
Turns out CM was the issue. Running stock 4.4.4 and it works perfectly now! Thank you so much!
Related
Purchased a Targus Bluetooth Keyboard for iPad (yea I know it said iPad) Model AKB32US from OfficeDepot today. Probably taking it back tomorrow but it is such a nice looking and sized Bluetooth keyboard.
Attempted to sync it with Viewsonic Gtab (TNT ROM) and Archos 101 (Stock Rom) with no luck. I know I need a APK to go along with the keyboard but I needed to try anyway.
Did some searching but the Google-Foo was weak today. Left a message at Targus.com but don't really expect an answer. Tried the Android Bluetooth Driver from the My Gear area on all settings as well.
Anyone had any success stories on Bluetooth keyboards and Gtab?
There are several threads that discuss bluetooth keyboards and different ROMs on the gTab.
Do a search in the Market for an app called Bluetooth Keyboard Easyconnect. It seems to have the most success of making connections for keyboards to the gTab.
Anyone else find it a bit ridiculous that you need an apk helper program to get almost any bluetooth device working with the gtab?
I've had some success with this keyboard/gTab combination. I was running into problems with entering the passphrase. My gTab kept asking me to enter the passphrase. It suggested 000 or 1234 and neither appeared to work. I was able to connect the keyboard to my Galaxy S and it seemed to work fine. When connecting that one though it prompted me on my phone to type a passphrase on the keyboard rather than the phone. Since it (the passphrase) was different everytime I assume it was randomly generated on my phone and sent to the keyboard for authentication. On my gTab it wasn't like that. It prompted me for the passphrase on my tablet and didn't connect. I read on another forum that someone was able to connect by typing the 0000 on their gTab then typing 0000 on the keyboard. It connected for me. Good, now I don't have to return it.
Since I'm not sure which, if any, did it for me. Here's the things I loaded to try and get it to work:
1. First tried to to a straight connect. No luck.
2. Loaded Bluetooth Keyboard Easy connect. (In market). No luck.
3. Loaded Blueinput. (In market also). No luck.
4. Tried the 0000 input on gTab then again directly afterwards on the keyboard. Voila! Success!
5. Uninstalled Blueinput. Rebooted, still working.
6. Uninstalled Bluetooth Keyboard Easy connect. Rebooted, still working.
I am running the VEGAn-7.0.0-RC1-Harmony ROM. (which is absolutley fantastic by the way...)
Much luck to you all.
JS
jfs999 said:
I've had some success with this keyboard/gTab combination. I was running into problems with entering the passphrase. My gTab kept asking me to enter the passphrase. It suggested 000 or 1234 and neither appeared to work. I was able to connect the keyboard to my Galaxy S and it seemed to work fine. When connecting that one though it prompted me on my phone to type a passphrase on the keyboard rather than the phone. Since it (the passphrase) was different everytime I assume it was randomly generated on my phone and sent to the keyboard for authentication. On my gTab it wasn't like that. It prompted me for the passphrase on my tablet and didn't connect. I read on another forum that someone was able to connect by typing the 0000 on their gTab then typing 0000 on the keyboard. It connected for me. Good, now I don't have to return it.
Since I'm not sure which, if any, did it for me. Here's the things I loaded to try and get it to work:
1. First tried to to a straight connect. No luck.
2. Loaded Bluetooth Keyboard Easy connect. (In market). No luck.
3. Loaded Blueinput. (In market also). No luck.
4. Tried the 0000 input on gTab then again directly afterwards on the keyboard. Voila! Success!
5. Uninstalled Blueinput. Rebooted, still working.
6. Uninstalled Bluetooth Keyboard Easy connect. Rebooted, still working.
I am running the VEGAn-7.0.0-RC1-Harmony ROM. (which is absolutley fantastic by the way...)
Much luck to you all.
JS
Click to expand...
Click to collapse
Thank you sir... bought the same keyboard, love the feel and dimensions but could not get past the passkey part... now it's up and running and working great... thanks again
Running on Vegan-Tab 7.0.0 GingerEdition
JacRyan said:
Thank you sir... bought the same keyboard, love the feel and dimensions but could not get past the passkey part... now it's up and running and working great... thanks again
Running on Vegan-Tab 7.0.0 GingerEdition
Click to expand...
Click to collapse
I am interested in this keyboard, how does the ipad hotkeys work under andriod ?
Bump ..
Any feedback ?!
Got mine to work with HTC Evo
Got my keyboard to work yesterday using instructions below, on an Evo running 2.3.3
1.) Put batteries in Keyboard
2.) Put Android Device in bluetooth search
3.) Turn Keybaord on and Press "Connect"
4.) Once the keyboard shows up on Android Device, enter the paskey "0000"
5.) Press connect on your android device, then immediately type "0000" on the keyboard and press the enter key.
That's what worked for me.....
jfs999 said:
I've had some success with this keyboard/gTab combination. I was running into problems with entering the passphrase. My gTab kept asking me to enter the passphrase. It suggested 000 or 1234 and neither appeared to work. I was able to connect the keyboard to my Galaxy S and it seemed to work fine. When connecting that one though it prompted me on my phone to type a passphrase on the keyboard rather than the phone. Since it (the passphrase) was different everytime I assume it was randomly generated on my phone and sent to the keyboard for authentication. On my gTab it wasn't like that. It prompted me for the passphrase on my tablet and didn't connect. I read on another forum that someone was able to connect by typing the 0000 on their gTab then typing 0000 on the keyboard. It connected for me. Good, now I don't have to return it.
Since I'm not sure which, if any, did it for me. Here's the things I loaded to try and get it to work:
1. First tried to to a straight connect. No luck.
2. Loaded Bluetooth Keyboard Easy connect. (In market). No luck.
3. Loaded Blueinput. (In market also). No luck.
4. Tried the 0000 input on gTab then again directly afterwards on the keyboard. Voila! Success!
5. Uninstalled Blueinput. Rebooted, still working.
6. Uninstalled Bluetooth Keyboard Easy connect. Rebooted, still working.
I am running the VEGAn-7.0.0-RC1-Harmony ROM. (which is absolutley fantastic by the way...)
Much luck to you all.
JS
Click to expand...
Click to collapse
Does this need to be done every time? Or does it remember after the initial pair?
I just got the Targus keyboard working with Honeycomb on the G-Tablet. This is the fastrack version and sems to be working pretty well. No driver needed
poneal410 said:
Got my keyboard to work yesterday using instructions below, on an Evo running 2.3.3
1.) Put batteries in Keyboard
2.) Put Android Device in bluetooth search
3.) Turn Keybaord on and Press "Connect"
4.) Once the keyboard shows up on Android Device, enter the paskey "0000"
5.) Press connect on your android device, then immediately type "0000" on the keyboard and press the enter key.
That's what worked for me.....
Click to expand...
Click to collapse
Did some similar steps and it worked perfectly on my Xoom! Thanks bro...
JacRyan said:
Thank you sir... bought the same keyboard, love the feel and dimensions but could not get past the passkey part... now it's up and running and working great... thanks again
Running on Vegan-Tab 7.0.0 GingerEdition
Click to expand...
Click to collapse
Just loaded this Keyboard on my Galaxy Note 10 inch. Works nicely. Nothing required to install.
I'm trying to pair my bluetooth keyboard, which worked perfectly under Gingerbread, but will not pair under ICS. Basically, the keyboard will not go into pairing mode until I give it a pin, and ICS won't give me the pin until the keyboard is pairing. Is there any way to tell ICS what pin to expect before trying to pair? This is the sequence I am doing:
1. Put keyboard in discoverable mode.
2. Select the keyboard in the bluetooth menu.
3. Type in a pin on the keyboard and hit enter.
4. A dialog comes up on the tablet telling me what pin to use to pair. (I have to type in the pin in the keyboard for this to come up)
5. Pairing fails after about 1/4 of a second.
Anyone I have the same thing. Get a pop up for a quarter of a second that has a pin but I can't enter it or even read it and then fail.
Please been looking for a solution for a while.
HP Touchpad CM9 4.03
I've downgraded to cyanogenmod 7, and am purchasing a case with a built in keyboard that hopefully does not share the issue. I think these are the only two options.
Bluetooth keyboard in ics
Hi all, I hope I'm in the right area, I have android ics, when I go to pair a Bluetooth keyboard, I put the keyboard into pairing mode and then search on the phone. The phone finds the keyboard and sais please enter the pin code on the keyboard, and press enter, wichita I do and the message on the phone disappears and the keyboard seems to be pairs, but when you look at the keyboard the pairing light is still flashing. The keyboard works great on my partners...dare I say it iPad, but I can not get it to work in ics. I've tried blueinput, blue keyboard jp ,but neither of these program's seem to help. The can see the keyboard but don't seem to connect to them. Any help would be appreciated. To me it seems as tho the keyboard is not receiving an acceptance message from the phone to say connected.
Kryptoniteics said:
Hi all, I hope I'm in the right area, I have android ics, when I go to pair a Bluetooth keyboard, I put the keyboard into pairing mode and then search on the phone. The phone finds the keyboard and sais please enter the pin code on the keyboard, and press enter, wichita I do and the message on the phone disappears and the keyboard seems to be pairs, but when you look at the keyboard the pairing light is still flashing. The keyboard works great on my partners...dare I say it iPad, but I can not get it to work in ics. I've tried blueinput, blue keyboard jp ,but neither of these program's seem to help. The can see the keyboard but don't seem to connect to them. Any help would be appreciated. To me it seems as tho the keyboard is not receiving an acceptance message from the phone to say connected.
Click to expand...
Click to collapse
I would venture to say this is a device specific issue. I'd recommend going to the forum for your particular device and replying to a six month old post there that is vaguely related to your issue.
I have looked through the forums, and havnt found anything that helps. I have tried different programs and possible fixes. To no avail. I have a generic phone with ics so rooting may not b an option. One thing i have noticed is ics automatically generates a bluetooth access key. Is there a way to change this to manually choose or enter a pass key. I think this may be part of my problem. Or possibly fix the issue i have. Any thoughts.
Sent from my S5_75_5647 using xda app-developers app
Hey all, my name is Dan, long time lurker, first time poster.
I have done alot of research on the topic, but didn't find much in the way of this particular problem.
I currently have a SGS2 running Ressurection 1.8 and a Galaxy Tab 10.1 running the latest build of AOKP.
So basically the problem I'm having is that both of these devices are stuck in Bluetooth Legacy mode, and what I need is to somehow enable Simple Secure Pairing (SSP).
I have a bluetooth mouse that has no PIN. It was designed strictly for SSP use.
When my SGS2 was running stock 3.2.6 I had no problems pairing my mouse.
My tablet was running 3.2, and it would not pair, it insisted I input the correct PIN. There was no way to leave the field blank and continue, and inputting anything got you a failed pair.
Fast forward to now, I updated both devices thinking that SSP was the standard and now I'm sad to learn that Legacy mode seems to be the only way to pair any of my bluetooth devices.
So basically does anyone have any idea of SSP can be enabled?
Easy solution is to buy a new mouse.
But what would that solve? lol.
Thanks for readin.
Hi,
in our warehouse I use the Galaxy Wifi 4.0 with a Motorola RS507 bluetoothscanner for orderpicking.
I have 10 of them all working without any problem. Now I needed 10 more, but the 4.0 is replaced by the 4.2. So I bought them instead.
But I cannot get the scanners working with this device.
If I want to connect the scanner I get the message:
Confirm passkey is xxxxxx to pair with RS507 1234
I can press "Accept" or "Decline"
When I press "Accept", it says "paired" but I cannot use the device.Also the device give no confirmation sound that it is connected.
On all the other devices (Wifi 4.0, Galaxy S, Lenovo A1 Tablet) I get the message:
Confirm password to pair with "RS507 1234"
Then I only have to press Accept and the device is paired and working.
Does anyone have a similar problem with another bluetooth device and knows a solution how I can connect the scanner?
If it will not work I have to look around for the old Galaxy Wifi 4.0.
Thanks for your help.
kiteman76 said:
Hi,
in our warehouse I use the Galaxy Wifi 4.0 with a Motorola RS507 bluetoothscanner for orderpicking.
I have 10 of them all working without any problem. Now I needed 10 more, but the 4.0 is replaced by the 4.2. So I bought them instead.
But I cannot get the scanners working with this device.
If I want to connect the scanner I get the message:
Confirm passkey is xxxxxx to pair with RS507 1234
I can press "Accept" or "Decline"
When I press "Accept", it says "paired" but I cannot use the device.Also the device give no confirmation sound that it is connected.
On all the other devices (Wifi 4.0, Galaxy S, Lenovo A1 Tablet) I get the message:
Confirm password to pair with "RS507 1234"
Then I only have to press Accept and the device is paired and working.
Does anyone have a similar problem with another bluetooth device and knows a solution how I can connect the scanner?
If it will not work I have to look around for the old Galaxy Wifi 4.0.
Thanks for your help.
Click to expand...
Click to collapse
Try enabling CONFIG_BT_HID in your kernel. I say this since the scanner's datasheet has blutooth HID listed, the 4.2 kernel doesn't have it enabled, and my 4.0 *does* have it enabled. In the 4.0 it's configured as a module, but you could try getting away with linking it directly in your kernel just in case the 4.2's init scripts/ueventd doesn't load it.
If you need help doing this let me know in a PM.
jlyo said:
Try enabling CONFIG_BT_HID in your kernel. I say this since the scanner's datasheet has blutooth HID listed, the 4.2 kernel doesn't have it enabled, and my 4.0 *does* have it enabled. In the 4.0 it's configured as a module, but you could try getting away with linking it directly in your kernel just in case the 4.2's init scripts/ueventd doesn't load it.
If you need help doing this let me know in a PM.
Click to expand...
Click to collapse
Thanks for your help. But I configured the scanner to use SPP an not the HID profile. Is SPP also disabled ?
It is not that important for me anymore.I bought 15 new 4.0 devices. But as a sport I want to get it working on de the 4.2
Can I ask?
kiteman76 said:
Thanks for your help. But I configured the scanner to use SPP an not the HID profile. Is SPP also disabled ?
It is not that important for me anymore.I bought 15 new 4.0 devices. But as a sport I want to get it working on de the 4.2
Click to expand...
Click to collapse
Hi, We are trying to do pretty much the same thing pairing RS507 to Galaxy Player. Can I ask where you found or can you describe the procedure for pairing.
Thanks!
eikaun said:
Hi, We are trying to do pretty much the same thing pairing RS507 to Galaxy Player. Can I ask where you found or can you describe the procedure for pairing.
Thanks!
Click to expand...
Click to collapse
What version of the Galaxy Player do you have? I only succeeded in connecting it to the 4.0 and the 5.0. If you need more help, let me know.
Yes I need help
kiteman76 said:
What version of the Galaxy Player do you have? I only succeeded in connecting it to the 4.0 and the 5.0. If you need more help, let me know.
Click to expand...
Click to collapse
To answer your question 4.0. Yes I need help I am flying by the seat of my pants on this. If you can help with a start to finish explanation including any software you downloaded I would very much appreciate it. Like I say I really need some help - so thanks
RS507 and Android Phone
eikaun said:
To answer your question 4.0. Yes I need help I am flying by the seat of my pants on this. If you can help with a start to finish explanation including any software you downloaded I would very much appreciate it. Like I say I really need some help - so thanks
Click to expand...
Click to collapse
Hi,
I've tried connecting Android to various other BT scanners before (using the SPP) and have not had problems. But I'm struggling on the RS unit.
What I normally do is on other scanners is turn pairing on for the scanner, connect and pair to the unit from the phone. Then start my application on the phone, which initiates the connection to the scanner and connects. Then I can read from the scanner and all works well.
On the RS this seems different, as you don't seem to put the RS in pair mode and connect to it. instead the process seems to be to scan a barcode on/for the device (with MAC id?) and the RS connects?
Either way, I have not managed to get this to work.
Can someone provide me with the correct process to connect the RS to an android device in SPP mode?
Any help or working code example would be much appreciated!
I have a Galaxy S3 I9300 for a couple of weeks now and I love it, other than the fact that I keep having a strange issue with the Bluetooth connection with my carkit. I've been searching forums for similar issues and I found a variety of carkit related problems, but none of the ones I found describe the same problem as what I'm having:
- Initially the Bluetooth connection works fine and I can play music or make a call through the carkit just fine
- When I switch off the car's systems and don't use any apps on the phone in the meanwhile, and then start the car's systems again, it establishes the Bluetooth connection just fine again
- When I switch off the car's systems and I use other apps for a while and then start the car again, it won't work. Bluetooth does appear to connect, but after that it just doesn't play ball. When I try to play a song at this point, the phone shows the song is playing, but neither the phone nor the car audio produces any sound
So anyway, every morning before leaving to work and every evening before going home, I reboot my phone first. Then I step into the car and it establishes the Bluetooth connection just fine. But if I don't reboot the phone first, it just won't work. Now I guess I could setup a tasker profile to automatically reboot the phone, but I'd rather just get the problem fixed.
I run a Galaxy S3 I9300 with stock Android 4.1.1, rooted. I have already tried to run the "Bluetooth Fix Repair" app and afterwards had to pair the phone with the carkit again, but that made no difference.
Any help would be greatly appreciated!
*bump*
Some additional info:
This issue has now also happened a few times while driving. While music (through Spotify) was playing over the bluetooth carkit, it would sometimes just stop working when I opened a different app (like for example opening an SMS). Spotify was still running (and the song was still ongoing) and also the bluetooth connection still showed as being connected, but it just wouldn't produce any sound anymore.
Anyway, it seems clear to me that this is a bluetooth issue, but I have no idea how I can troubleshoot this beyond what I've already done.
I would be happy to pay whoever can fix this problem..
With an issue like you are describing it may be helpful to list the headunit model too. I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.
Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
ItzCrooK2UxD said:
With an issue like you are describing it may be helpful to list the headunit model too.
Click to expand...
Click to collapse
My car is a Renault Megane RS, the carkit was built in. I believe it's called Renault Carminat TomTom.
ItzCrooK2UxD said:
I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.
Click to expand...
Click to collapse
I've covered everything like that in about 100 different ways, none of which made any difference.
ItzCrooK2UxD said:
Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
Click to expand...
Click to collapse
Good point. It does have an SD card slot, but as far as I know that's only to update the maps of the navigation system. I'll see if I can figure that out.
Thanks for the tips!
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
Apoc_ said:
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
Click to expand...
Click to collapse
It is in fact very possible that it is your phone, but wanted to throw it out there that bluetooth headunits can be troublesome on their own. Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me. Also do you have other bluetooth devices in the car, such as the 3GS you mentioned?
Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
ItzCrooK2UxD said:
Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me.
Click to expand...
Click to collapse
Yeah I had read that too in some other thread (I went through just about every bluetooth related thread I could find, before I posted this topic). Mine saves up to 5. It didn't have anything in there except for my previous phone, which I had cleared. I also tried re-pairing the S3 several times, that didn't make any difference either.
Now, I just read somewhere that some people are having disconnection issues on the same carkit. In their case, in the end the problem turned out to be that their carkit will import all of their contacts from their phone (so you can call people even while your phone is in your pocket), and this would cause trouble when there are contacts without a phone number associated with it (just like my thousands of Exchange contacts). The people in question are talking about random disconnects though, whereas in my case it happens after doing some stuff on my phone. So it's probably unrelated, but I'll give that a try anyway just to rule it out. I just need to figure out a way to stop the carkit from importing contacts, because removing thousands of email contacts is obviously not an option.
I'll keep this topic updated with any progress. If anyone has any other ideas, please keep em coming. Thanks for the help so far!
ItzCrooK2UxD said:
Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
Click to expand...
Click to collapse
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.
I've installed alogcat just now. Does it just keep running automatically in the background?
Apoc_ said:
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.
I've installed alogcat just now. Does it just keep running automatically in the background?
Click to expand...
Click to collapse
It reads a file that is being constantly updated (which happens to be the logcat file). Typically I will clear it right before doing what it took to cause the failure, like in your case in your car with the bluetooth on.
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
YoghurtPL said:
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
Click to expand...
Click to collapse
Yep - I have that too. The weird thing is that in that situation the phone does seem to think it is connected, while it really isn't. Just to be clear: this is not the only way to cause this issue (because it also happens when trying to reconnect the Bluetooth while on the phone it hasn't been disabled in the meanwhile).
So far I haven't been able to pull anything related from the logcat.
Also, while reading up on common bluetooth issues, I came across some posts of people who were saying that some phone/carkit combinations are having trouble with 2-way communication (because I can stream music from the phone to the carkit, but I can also change a song using the carkit or initiate a phonecall from the carkit). I'm going to try to only use communication initiated from the phone, and see whether that makes any difference. In the meanwhile: does anyone happen to know anything about 2-way communication issues with bluetooth, and how to overcome such issues?
Update:
- Updated carkit to latest firmware. No change, still same problem
- Have not been able to capture anything unusual in the logs
- I have a Bose Soundlink now, which is a wireless speaker. Whenever my S3 is connected to the Soundlink (with bluetooth), wifi doesn't work. Upon turning off bluetooth, wifi instantly works fine again. So this definitely confirms this is a problem with bluetooth on the phone, not on the carkit.
- Wanted to upgrade to Android 4.1.2 but Samsung won't let me, as it says the device is modified (rooted). Triangle away isn't helping. Damn you, Samsung. This is *the* reason I moved away from Apple, as I don't like companies who don't let you use your stuff any way you like. And now Samsung is moving down the same route. Idiots. Anyway, I guess the only option left, is to start using a custom ROM.
Does anyone happen to have experience in terms of solving bluetooth problems by using a custom ROM? I'm thinking of using Cyanogenmod 10.1
In the meanwhile I have upgraded to Android 4.1.2: still the same problem.
I have also discussed this matter with quite a few other Samsung smartphone owners, and all of them appear to be having the same issue. Most of them just don't seem to be bothered to spend time on looking for a fix.
Also, I have figured out that this problem is specific to media streaming. I'm able to use my phone on the carkit for calls at any time, without having to reboot first. Only when I try to listen to music, the problem occurs.
Anyway, I have ruled out that this problem is specific to me or my devices - this appears to be a global issue. So I'm completely puzzled as to why there's not a lot more fuss going on about this.
If anyone has any more suggestions for a resolution of this problem, please share.
S3 bluetooth connection problem
Had the same problem with my S3 and renault megane III handsfree bluetooth system.(Arkamsys software version 2.2.0.19 auditorium)
I downgraded to 4.0.4 baseband I9300CELH1 (stock) and problem seems fixed
hope this helps.
Hi Bennes,
Thank you for your response.
I'm still dealing with this problem myself. All upgrades so far haven't made a difference. So far, I've been able to figure out that if I first initiate a phonecall, after hanging up, the audio streaming works (while before the phonecall it usually wouldn't). This works about 8 out of 10 times (the other 2 times it doesn't make a bluetooth connection at all). So what I've done, is to use Tasker and to automatically make it call my own phone number whenever bluetooth gets connected to the carkit, and hanging up after 3 seconds. But this is obviously far from ideal.
Do you know whether it is possible to change the baseband version without changing the firmware version? I wouldn't like to downgrade to an older firmware version, as I like the new features in the newer versions. I do also prefer to stick with the stock firmware, but that's not a requirement.
Carkit bluetooth issue
Apoc_ said:
Hi Bennes,
Thank you for your response.
I'm still dealing with this problem myself. All upgrades so far haven't made a difference. So far, I've been able to figure out that if I first initiate a phonecall, after hanging up, the audio streaming works (while before the phonecall it usually wouldn't). This works about 8 out of 10 times (the other 2 times it doesn't make a bluetooth connection at all). So what I've done, is to use Tasker and to automatically make it call my own phone number whenever bluetooth gets connected to the carkit, and hanging up after 3 seconds. But this is obviously far from ideal.
Do you know whether it is possible to change the baseband version without changing the firmware version? I wouldn't like to downgrade to an older firmware version, as I like the new features in the newer versions. I do also prefer to stick with the stock firmware, but that's not a requirement.
Click to expand...
Click to collapse
mmm, don`t know about baseband only. Try google.
I have read that after downgrade to 4.0.4 and then upgrade again to latest stock version, bluetooth connection keeps working.
I cannot confirm this as i am still on 4.0.4, but will get an update of the arkamsys radio to the latest renault firmware version next week and then start experimenting again. i will report back once i have new results
Bennes18 said:
mmm, don`t know about baseband only. Try google.
I have read that after downgrade to 4.0.4 and then upgrade again to latest stock version, bluetooth connection keeps working.
I cannot confirm this as i am still on 4.0.4, but will get an update of the arkamsys radio to the latest renault firmware version next week and then start experimenting again. i will report back once i have new results
Click to expand...
Click to collapse
BB only, try this :
http://forum.xda-developers.com/showthread.php?t=2106424
Confirmed the update thing, i have updated the S3 to version 4.1.2 BB I9300CEELL1 and have no bluetooth issue whatsoever, car audio still on 2.2.0.19 byt the way
Pretty strange ... , but glad its working !
I have the same issue with a Ford Focus =/
also, while using CM or Omega, the music title never changes.