Develop Bugs

Bluetooth A2DP on my Tilt2: WORTHLESS AS $H!T

Ok, so I finally got into the smartphone game to get a better music streaming experience. MFRadio and MFScorn just weren't cutting it for me anymore. I hated the skips and the ridiculously long (and repeated) buffering time. So I first looked at Android phones but went with WinMo because they say you can run both OS's with WinMo (and the only Android offering from AT&T has a 12-hour standby time before the battery dies, according to reviews).
I have a Bluetooth head unit and have had over a dozen phones paired with it. This phone however is a completely different story. I have installed the latest "release" from AT&T (from a thread on this site). At first I tried streaming with the bundled Windows Media Player which apparently doesn't stream anything at all (with both the bundled and downloaded releases of the OS), then downloaded TCPMP. TCPMP is everything I have ever dreamed of in a streaming media player, but the only problem I have with it is that it won't connect to a stream unless I have already opened up a browser window and went to a website. Not the end of the world.
So, I get in my truck and initiate pairing to the phone. It sees the head unit as a Hands-free and as Stereo Audio. I can get it to connect for a split second and then it dies. I get a popup notification that tells me that the phone cannot control volume when paired to the bluetooth device and audio must be adjusted from the device itself. Fine. But then it doesn't work at all. At first, I wanted to blame TCPMP until I realized that nothing at all was working with the head unit. I think I got it to work once but it never worked again.
So is there any way to fix this problem? This is the one thing I wanted working on my new phone. Yes, the notifications that my texts were successfully sent are very annoying (as well as the other notifications), and yes, Windows Media Player for Mobile is useless, but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
What can I do? I have not yet unlocked anything (although I have a SIM unlock code waiting) and have not yet flashed Hard-SPL. My phone has Bluetooth for Windows Mobile Version 1.9.2 Build 600 HCI Version 4.84. I'd do anything at this point to get this working. Windows Mobile is not that precious to me either. PLEASE HELP!

e-thug said:
Ok, so I finally got into the smartphone game to get a better music streaming experience. MFRadio and MFScorn just weren't cutting it for me anymore. I hated the skips and the ridiculously long (and repeated) buffering time. So I first looked at Android phones but went with WinMo because they say you can run both OS's with WinMo (and the only Android offering from AT&T has a 12-hour standby time before the battery dies, according to reviews).
I have a Bluetooth head unit and have had over a dozen phones paired with it. This phone however is a completely different story. I have installed the latest "release" from AT&T (from a thread on this site). At first I tried streaming with the bundled Windows Media Player which apparently doesn't stream anything at all (with both the bundled and downloaded releases of the OS), then downloaded TCPMP. TCPMP is everything I have ever dreamed of in a streaming media player, but the only problem I have with it is that it won't connect to a stream unless I have already opened up a browser window and went to a website. Not the end of the world.
So, I get in my truck and initiate pairing to the phone. It sees the head unit as a Hands-free and as Stereo Audio. I can get it to connect for a split second and then it dies. I get a popup notification that tells me that the phone cannot control volume when paired to the bluetooth device and audio must be adjusted from the device itself. Fine. But then it doesn't work at all. At first, I wanted to blame TCPMP until I realized that nothing at all was working with the head unit. I think I got it to work once but it never worked again.
So is there any way to fix this problem? This is the one thing I wanted working on my new phone. Yes, the notifications that my texts were successfully sent are very annoying (as well as the other notifications), and yes, Windows Media Player for Mobile is useless, but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
What can I do? I have not yet unlocked anything (although I have a SIM unlock code waiting) and have not yet flashed Hard-SPL. My phone has Bluetooth for Windows Mobile Version 1.9.2 Build 600 HCI Version 4.84. I'd do anything at this point to get this working. Windows Mobile is not that precious to me either. PLEASE HELP!
Click to expand...
Click to collapse
Hmmmm .... I don't believe you ever stated what type of headset you are trying to get working here? I find your problem to be very strange, even though WinMo does seem to be lacking in a lot of different areas, audio streaming via bluetooth stereo headset is definitely not a problem I have encountered. It even streams flawlessly through my 5.1 hooked to my pc via a crappy 8 buck bt dongle and still sounds excellent. Have you considered that the problem may lie with your bt headset itself?
Also, when you say that you installed latest "release" from AT&T (from a thread on this site), what exactly do you mean? I am running the "unofficial" leaked rom from AT&T on mine and I just paired my Motorola S9 stereo headset and it is playing great for me. You also may want to try using some different software, give S2P (Slide 2 Play) a try and see if you have different results. That's what I am using right now, but I have used TCPMP to play a few xVids through my headset and have had no problems.

The problem is not in the head unit. 25 other phones can't all be wrong. I have no problem using my bluetooth headset. That is probably why you don't see the problem. Anything more complex than a headset will not work with this release. The problem lies within the phone as soon as it displays a notification (which, of course I cannot disable) which reads, "The connected Bluetooth headset does not support volume adjustment from the device. Adjust volume on the headset itself."
That message is the kiss of death. So basically any Bluetooth head unit will not work with this phone? Sounds like shoddy programming to me. Yes, I am using the "leaked" release. I really don't think this release will ever see the light of day. Its horrible! You cannot disable notifications (I don't need to know when my text messages were sent successfully), and it looks like whenever I get a system notification, any program I am using crashes immediately. Like I said before, as soon as I get a notification, I lose the Bluetooth connection (which is like a split second before the notification comes up). I highly doubt this "leaked" copy will ever see the light of day, officially (unless AT&T and HTC do absolutely zero testing on it).

A little clarification for those who don't know... when I say "head unit" I'm talking about a Bluetooth-enabled car stereo and when I say "headset" I mean a Bluetooth headset

My Tilt 2 works absolutely fine with all my BT devices, including 2 Motorola headphone sets and my Sony Xplod head unit in my truck.

e-thug said:
A little clarification for those who don't know... when I say "head unit" I'm talking about a Bluetooth-enabled car stereo and when I say "headset" I mean a Bluetooth headset
Click to expand...
Click to collapse
I was mis-understanding you about the head unit, I did think you were talking about a headset. Sorry bout that, my Mustang doesn't have built-in BT so I have to use a Motorokr t505 for those chores. It works well but it does give me the same message that you are getting about "volume can't be cotrolled etc" but I can dismiss it and carry on without any problems.

but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
Click to expand...
Click to collapse
Since you don't need your phone for calls, just get Sirius or XM. Ya know, considering you only stream music through the phone..

Did you try the BT headset or head unit with the original stock ROM before you flashed the "leaked official" ROM?
Seems like you might have a couple random issues, with the BT issues and the system notifications crashing programs. I haven't flashed the leaked ROM, but I do know that many random issues with cooked ROMs can often be cleared up by running Task29, which completely wipes the phone memory before you flash a new ROM. I think you will need to HardSPL before you run Task29. Might be worth a try, sometimes fragments of the old ROM interfere with the new one, and cause some bugs.

Bluetooth protocols can be implemented differently by different manufacturers.
I know of many people including myself who have NO PROBLEM with the tilt 2 and different Bluetooth products INCLUDING car radios.
I am using the "new" AT&T ROM and have no difficulties.
Clearly your pissed but your subject is wrong. I would suggest changing to "Worthless as $HIT to ME"

I think my problem is that I am getting notifications which seem to be killing my connection. Is there a way to turn all notifications OFF? The only ones I care about are missed calls, incoming SMS and maybe a birthday. I would like to try to kill the notifications first because I think this may solve my problem

You can get yourself a free reg editor (like Total Commander) and apply the following tweaks to modify the notifications:
SMS sent notification: http://www.mydigitallife.info/2008/06/24/enable-or-disable-the-sms-text-message-sent-notification-bubble/
Other notifications: http://www.mydigitallife.info/2008/06/24/tweak-and-configure-how-notifications-work-in-windows-mobile-notifications/
Although, this sounds like a band-aid just hiding a deeper problem. What you are describing is not typical behavior, and this is something else going on.

redpoint73 said:
You can get yourself a free reg editor (like Total Commander) and apply the following tweaks to modify the notifications:
SMS sent notification: http://www.mydigitallife.info/2008/...he-sms-text-message-sent-notification-bubble/
Other notifications: http://www.mydigitallife.info/2008/...cations-work-in-windows-mobile-notifications/
Although, this sounds like a band-aid just hiding a deeper problem. What you are describing is not typical behavior, and this is something else going on.
Click to expand...
Click to collapse
Thanks I will try these out and report back
For the record my head unit is a JVC KD-BT11 and I have never had any kind of problem pairing any other phone

Somebody else just posted a very similar issue, and found the app hAndyUtils to be helpful:
http://forum.xda-developers.com/showthread.php?t=741311
I think hAndyUtils might just be a app-based way to make the reg edits I posted earlier. But give it a try.

I scanned through the topic and did not see anyone mention this so I thought I would add my .02. The Tilt 2 is different than many other WM phones when it comes to bluetooth as it contains the Widcomm BT stack instead of the MS stack. (Just as an aside, on all my past phones, there were people bemoaning the the fact that it had MS, and trying to replace it with the Widcomm, so I am getting a real chuckle out of folks complaining about the Widcomm and wishing for MS )
In any case, the utilities (Blue music toggle etc...) that used to work for me to toggle between streaming in stereo and plain phone qulity no longer work. However, all my stereo headsets (I own three different brands/pairs) all work perfectly with the Tilt 2. And stay connected and streaming all day.
By the way, coming on a forum that is full of people helping each other and using profanity, anger and threats, is not the most conducive way to get your questions answered. The odds are that the problem you are having is already solved somewhere among the 6+ million posts in this forum. I do not know where or I would post it for you, but it is probably out there. Good luck. And if you find it, please post the link to the answer back here so that other serchers will find it too.

maybe it can come from the phone itself
i had a rhodium for almost a year and never got my motorola headset ht820 to work well enough for me to use it... (more skips than music...cant move my head without a skip)
i flashed to a NRG rom before trying my headset...i tried eveything as far as ref setting, different radios...even flashed my ht820...
no improvement...
then my phone fell in water not so long ago...got another rhodium same model (european)...and it worked perfect out the box on stock rom i can go in a different room than my device and still hear music with no skips...and it still does with nrg rom and latest radio...
so my guess is maybe some actual devices have bad bluetooth hardware ???

I have the Motorola S9 and the HT820 and both work absolutely fine on my Tilt 2.

yatrg said:
I scanned through the topic and did not see anyone mention this so I thought I would add my .02. The Tilt 2 is different than many other WM phones when it comes to bluetooth as it contains the Widcomm BT stack instead of the MS stack.
Click to expand...
Click to collapse
Can I change my Bluetooth stack to MS? I have installed Hard-SPL and have experimented with cooked ROMs to no avail.
I sent the phone back to AT&T, went to Trinidad & Tobago for a few weeks and came home to a new Tilt 2 waiting at my doorstep (which could have been stolen by anyone!) and I am still having the same problem. So I guess I sent back a perfectly good phone!
I would love to try some different Bluetooth stacks if possible. Where do I go from here?

e-thug said:
Can I change my Bluetooth stack to MS? I have installed Hard-SPL and have experimented with cooked ROMs to no avail.
I sent the phone back to AT&T, went to Trinidad & Tobago for a few weeks and came home to a new Tilt 2 waiting at my doorstep (which could have been stolen by anyone!) and I am still having the same problem. So I guess I sent back a perfectly good phone!
I would love to try some different Bluetooth stacks if possible. Where do I go from here?
Click to expand...
Click to collapse
Did you ever try the solution in this thread? It fixed a lot of issues people were having with bluetooth car kits. Maybe it will work for you: http://forum.xda-developers.com/showthread.php?t=591322
The solution source is here: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
And here is the solution. You need a registry editor to do this:
1. Modify the HandsFree plug-in:
HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2
2. Modify the WIDCOMM bluetooth general settings:
HKLM\Software\WIDCOMM\BtConfig\General
i. Change bdaddr to (no value)
ii. Change (or add if not there) DisableReopenAudio to 0 (default is 1)
3. Reboot device
You may also want to do the A2DP quality registry edit: Add a DWORD value of LineSpeed to HKLM\Software\WIDCOMM\Plugin\AV\ with a value of 320.
Give it a try, it may work for you.

I will give this a try and report back. Thank you very much for the response!

No luck. And my bdaddr keeps resetting to a binary value when I reset the phone

Desire bluetooth not working with BMW

My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.

tifosi256 said:
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
Click to expand...
Click to collapse
Hi,
I know there are some issues when it comes to Bluetooth and Android, and especially car kits.
Ref (sound quality): http://code.google.com/p/android/issues/detail?id=9888
Ref (disconnections): http://code.google.com/p/android/issues/detail?id=5452
This is supposed to be a fix (I did not get it to work properly): http://forum.xda-developers.com/showthread.php?t=731626
I know that Cyanogenmod has made some changes to their kernel in 6.1 that adresses audio quality (bitpool increased), and I also think that the disconnection is adressed. I'm actually testing it for the moment (6.1RC2).

Thanks very much for your reply - very useful. The link to disconnections that you gave shows someone else with the same car as us (slightly different model) with the same issue.
It's very strange as there are people reporting no problems at all with that car/phone combination.
Unfortunately, I can't try the suggested fix as I don't want to start mucking around with my ROM.

I have a problem with my Volvo and the Desire. No disconnections, but I can't get into the phonebook, using PBAP.
Flashing a MIUI Rom works charming for the bluetooth connectivity, however I'm missing my SenseUI.
Just hoping, praying, some def will include the AOSP bluetoothstack in a SenseUI-Rom

BMW Software update
Hi
I´d try contacting your local BMW workshop, to let them do a reading on your car to establish which software version your car have.
If it´s a rather old software version your car have, I´d suggest that you have it updated.
The software update might be the answer to your problems, and can also explain why other users with the same car don´t have this issue (they might have a newer software version than you).
Remember, this phone is way newer than the car, and also the software in it.
I´d give it a try
PS: Be advised. Updating from very old software to new software might cause "in car-hardware" compatibility issues, and demand new hardware in the car (computer modules ect.), so make sure you talk over which consequences the update could have for your specific car before the update is carried out
Cheers
-Buggi- (BMW workshop foreman in Denmark)

Thanks for that advice. I'll talk to the dealership and see about software upgrades. Fingers crossed!

I have a 2008 530i and my Desire (and my other halfs) work fine, so hopefully there is some newer firmware for yours. They facelifted the cars and slightly changed the iDrive in 2007 though so fingers crossed there is an update that fixes the pre-LCI models with a Desire.

Just for reference, this is sorted out now.
My I-Drive actually broke and I had a whole new unit put in (under warranty thankfully!). Since they were doing that, I begged them for the latest software, not just for the Bluetooth module, but for the system as a whole.
Since the software upgrade, the phone stays connected and everything works great.
The only fly in the ointment is that it seems that for some reason, not all numbers of contacts (or all contacts) make it into the car's phone book (most of them do).
Anyway, for anyone else having this issue, get BMW to upgrade your BT software (or the whole system if you're brave).

I have similar problem when i try to pair the phone with volkswagen tiguan 2010, it says "your phone in not supported"

[Q] Problems Pairing new SGS2E4GT Phonebook with Car Bluetooth??

Okay so, I have read a couple of threads that somewhat touch base on my issue, however are not specific to my phone so I thought I would drill down to the subject matter in a new thread.
I just got a new SGS2E4GT yesterday as a replacement for my EVO4G. So far I love it, however when I paired it into my vehicle's (2011 Hyundai Elantra) bluetooth system, It connected to phone & media with no problem, but did not download the contact book.
Is there a fix, setting, or something I am missing within the SGS24E4GT?
I guess the thing that is a bit perturbing to me is that my good ol EVO had no issues whatsoever with pairing up.....

One option you might try is to remove pairing from both devices.
Then try to re-pair them.
I have a parrot CK-3100 BT setup in my truck and the first pairing didnt go well.
Removed it and re-did it. It asked me to allow access to my phone book. It was an option i had to check and after that its worked every time.
Also, check with the vehicle manufacturer and see if any software updates are available for your BT device in your vehicle.
It might not be an issue with the Epic Tocuch but with the other device playing nicely with the Touch.

Thanks very much. Will do as soon as I get out of work tonight

does the bluetooth pairing request problem exist on the note 2?

currently have the gs3 thinking of getting the note 2. on the gs3 with the stock jellybean roms there is a problem that there is bluetooth pairing request every time you pair with a device, even if you have paired with that device before. it does not just connect automatically each time you must fill the request to connect.
does this happen with note 2?

No problem here pairing with a samsung headset and also a nokia one. No repeated request filling.
But of course there are lots of other problems with bluetooth (at least for me), especially with S voice control. Let's say the bluetooth experience on this phone is not stellar... Hoping these things will get better with time :angel:

Hi,
Paired my bluetooth once and going fine since then. Never asked to pair again.
Cheers!!

manjeev said:
Hi,
Paired my bluetooth once and going fine since then. Never asked to pair again.
Cheers!!
Click to expand...
Click to collapse
i picked up the note 2 here in the US today...unfortunately it seems we have to pair bluetooth every single time. really sucks. every time i connect to my appradio2 i get i have to confirm the passkey to connect. there is no way around it that i can see and my previous phone the gs3 running cm10 never had this problem. could there possibly be someting i'm missing as to why it asks to confirm the passkey every time?

knives of ice said:
i picked up the note 2 here in the US today...unfortunately it seems we have to pair bluetooth every single time. really sucks. every time i connect to my appradio2 i get i have to confirm the passkey to connect. there is no way around it that i can see and my previous phone the gs3 running cm10 never had this problem. could there possibly be someting i'm missing as to why it asks to confirm the passkey every time?
Click to expand...
Click to collapse
Hello sir,
I'm also having this same situation when connecting my N7100 to the car audio.
I think this is because the Bluetooth function on N7100 Jelly Bean is in invisible mode (Only visible for 2 Minutes with Default Setting).
Try to change the Visible Time Out on Bluetooth settings to "Never Time Out".
Hope this help.:silly:

Maybe a work around
Hello,
You might have the problem with "old" and "new" pairing method and these don't get on quite well. The problem is that you can't make the pairing code permanent.
You might want to try this work around and see if it works (I'm not sure but I managed to pair the ICS BT in my wifes car this way):
- Turn BT on on your phone and prepare it to send a picture or a contact by BT
- Put the device you want to pair with your Note in pairing mode (so it can be discovered by the Note)
- Now send the contact/image from the Note to the device you want to pair.
- The note will start searching for devices and you chose the device you need once the phone found your device
- Now the notification bar on the phone should prompt for the BT connection and you have the option to put in the code and check the "Do not ask anymore" option. After hitting OK your code should be permanent.
This method was found by a Master Brain called Rayer and he published it on a XPeria forum; you can hit the "Thank You" button anyway if it helps you

Bluetooth Keyboard Connection Issue

Hi all, I just bought a COD (TM) Bluetooth Keyboard Stand from Amazon. The stand is great, but the bluetooth keyboard keep losing its connection, even when I'm typing.
What could be the cause? Does anyone know how to fix this? Your help is much appreciated.
EDIT :
Try this to fix your BT problems .
Go to settings > Connections > Bluetooth > Hit menu button > Visibility Timeout > and change it to Never
Thanks to Geordie Affy.
Thanks in advance.

eddlum25 said:
Hi all, I just bought a COD (TM) Bluetooth Keyboard Stand from Amazon. The stand is great, but the bluetooth keyboard keep losing its connection, even when I'm typing.
What could be the cause? Does anyone know how to fix this? Your help is much appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Try disabling the onscreen keyboard when connected to bluetooth. Some have reported this to help. I do not know for sure as I dont have BT Keyboard yet. There is some talk in one of the threads here about it. I dont remember where ATM but will look again for it and post a link to it if I can find it. Otherwise you can search in the threads for it here yourself
Here is the link I mentioned:
http://forum.xda-developers.com/showthread.php?t=2526070

ArticFox918 said:
Try disabling the onscreen keyboard when connected to bluetooth. Some have reported this to help. I do not know for sure as I dont have BT Keyboard yet. There is some talk in one of the threads here about it. I dont remember where ATM but will look again for it and post a link to it if I can find it. Otherwise you can search in the threads for it here yourself
Here is the link I mentioned:
http://forum.xda-developers.com/showthread.php?t=2526070
Click to expand...
Click to collapse
BarryH_GEG said:
Click to expand...
Click to collapse
Thanks for your reply. I tried this trick with no luck. It automatically switch back to Samsung keyboard after 2 second. Grrrrr...very annoying

Google "android 4.3 bluetooth keyboard". Android 4.3 breaks most bluetooth keyboards and it appears Google has no desire to fix it with 4.4 out now. There are fixes out there but they involve rooting and voiding your warranty on this tablet. I think those of us who use bt keyboards and want a warranty will just have to wait for Samsung to roll out 4.4.
I almost returned the tablet over this but I get enough out of it that I'll wait. Hopefully they'll roll out 4.4 soon.
Sent from my SM-P600 using xda app-developers app

LaRoach said:
Google "android 4.3 bluetooth keyboard". Android 4.3 breaks most bluetooth keyboards and it appears Google has no desire to fix it with 4.4 out now. There are fixes out there but they involve rooting and voiding your warranty on this tablet. I think those of us who use bt keyboards and want a warranty will just have to wait for Samsung to roll out 4.4.
I almost returned the tablet over this but I get enough out of it that I'll wait. Hopefully they'll roll out 4.4 soon.
Click to expand...
Click to collapse
I use my Samsung BT keyboard for hours on end and have never had a single issue with it. If BT is on, my N10.1-14 auto-connects when I turn on my BT keyboard and disables the onscreen keyboard. Samsung doesn't use Android's stock BT stack so any problems in generic Android wouldn't affect their devices. There are quite a few people here that aren't having issues with BT keyboards which would lead me to believe that it's the keyboards that some people are using that are causing issues. Interestingly, I had issues with the same keyboard I'm using now on my N10.1-12 where it would fight with the onscreen keyboard and randomly pop-up accented characters if I typed something like an "a" and left my finger on the key too long. It drove me crazy and I don't have any of those issues with the N10.1-14.

It's not clear exactly what the problem is, but here are a couple of observations, from what I've noticed:
- In some cases, the problem may be related to conflicts with other apps installed. The problem became much less noticeable after i uninstalled MightyText. May be coincidence, but I definitely see a big improvement. I still get an occasional disconnect with the Logitech K810, at most once every half hour of so. When MightyText was installed, I got disconnected every couple minutes.
- I also have a Samsung BT keyboard. I very rarely get disconnects with the Samsung KB.

@BarryH_GEG
I'd like to know where it was published that Samsung isn't using the stock Android BT stack? I've tried numerous keyboards that work with my desktop, iphone, and original GN 10.1 without any issue whatsoever, but are useless with this tablet. All of the symptoms are consistent with what others have reported on android 4.3. Hard to imagine that being a coincidence. Glad you found one keyboard that works. We can add it to the (short) list of ones that do.

dpersuhn said:
@BarryH_GEG
I'd like to know where it was published that Samsung isn't using the stock Android BT stack? I've tried numerous keyboards that work with my desktop, iphone, and original GN 10.1 without any issue whatsoever, but are useless with this tablet. All of the symptoms are consistent with what others have reported on android 4.3. Hard to imagine that being a coincidence. Glad you found one keyboard that works. We can add it to the (short) list of ones that do.
Click to expand...
Click to collapse
Kind of simple really. BT's been broken in AOSP since 4.2.
Bluetooth Is Basically Broken
Known affected devices: Nexus 10, Nexus 7, Galaxy Nexus.
Documented? Android bugs [1] [2], XDA [1] [2], Google+.
We've already received numerous emails about this issue, and I've confirmed it myself: Bluetooth on everything but the Nexus 4 (apparently) is in an absolutely sorry state right now. Audio streams extremely choppily, sounds mediocre, and often loses connectivity entirely. 3rd party Bluetooth apps that create compatibility with devices like the Sixaxis or Wii controllers no longer function at all, and throw an error instead.
This is bad. This is the kind of thing that makes someone return a phone or tablet, because A.) people have no patience for stuff like this, and B.) there's zero reason something as simple as Bluetooth should be broken so badly out of the box. Google needs to mark this one "critical" and fix it ASAP.
http://www.androidpolice.com/2012/1...major-issues-plaguing-googles-newest-release/​
Samsung's 4.2 devices weren't affected which means they had to be using either their own BT s/w or made major modifications to BT in AOSP. As for a "short list," how do we know it's of "working" peripheral's vs. "broken" peripheral's? I've only seen about a half-dozen BT connectivity complaints and really wasn't aware of the problem until it was pointed out to me in another thread. In my case I have about six BT devices I use regularly including speakers, headphones, mice, and keyboards and if asked I'd say they work better on the N10.1-14 then they did on the N10.1-12. I'd define "better" as connecting faster automatically, staying connected, and playing well with others when multiple BT devices are connected. To your point, I could be the anomaly but as posted in this and other threads disabling the onscreen keyboard and checking for conflicting s/w seems to have helped some people so it wouldn't appear BT issues are that widespread (yet).

I agree that the onscreen keyboard adds much to the frustration, as it's default behavior mimics the problems folks have been reporting on other 4.3 devices. Most of what I've come across cites keyboard issues that many have experienced immediately after upgrading to 4.3, but that doesn't really meet the requirements of being evidence either. I suppose the only real way to know would be to grab the base android build that Sammy used and compare files.
As for compatibility issues beyond keyboard input, I can't really speak to that, as I only have a few audio devices and one gamepad. It isn't really a large enough sampling to suggest that the entire stack is hosed up. My issues have been entirely related to BT keyboards, so I'm more focused on that.
You mention conflicting software, which brings up a question. Since the BT stack would be considered part of the protected core OS, apps would require root to mess with it, wouldn't they? The six axis app being a good example, as it requires root. To hook the BT stack at a low enough level to add profiles or override existing ones for compatibility isn't something that should be possible with a user level app. I could be off base here and the reports of user apps affecting BT are an interesting coincidence, but I'm not sure I can quite see where the two cross paths. The alternative is surely more concerning, as it would imply that core OS functions in this tablet are somehow exposed to being overridden by user space apps.

dpersuhn said:
I agree that the onscreen keyboard adds much to the frustration, as it's default behavior mimics the problems folks have been reporting on other 4.3 devices. Most of what I've come across cites keyboard issues that many have experienced immediately after upgrading to 4.3, but that doesn't really meet the requirements of being evidence either. I suppose the only real way to know would be to grab the base android build that Sammy used and compare files.
As for compatibility issues beyond keyboard input, I can't really speak to that, as I only have a few audio devices and one gamepad. It isn't really a large enough sampling to suggest that the entire stack is hosed up. My issues have been entirely related to BT keyboards, so I'm more focused on that.
You mention conflicting software, which brings up a question. Since the BT stack would be considered part of the protected core OS, apps would require root to mess with it, wouldn't they? The six axis app being a good example, as it requires root. To hook the BT stack at a low enough level to add profiles or override existing ones for compatibility isn't something that should be possible with a user level app. I could be off base here and the reports of user apps affecting BT are an interesting coincidence, but I'm not sure I can quite see where the two cross paths. The alternative is surely more concerning, as it would imply that core OS functions in this tablet are somehow exposed to being overridden by user space apps.
Click to expand...
Click to collapse
Great post and it touches on one of Android's key weaknesses. "Core" like everything else is nothing but a guideline. OEMs like Samsung and app developers color outside the lines all the time for their own benefit. In Samsung's case it was beneficial because BT in 4.2 was a mess and based on your findings still is so Samsung's meddling helped their audience. Android's kind of like the wild wild West in that regard. Add to that something like BT which itself is kind of like the wild wild West with frequent complaints about incompatibility between devices and you end up with the situation we're discussing. In every phone forum I've seen there's always multiple threads on "can't connect to my [insert brand of car]'s BT system." If the phone and car's BT implementation followed prescribed standards that wouldn't be the case. But who knows who's fault it is - the device OEM or the car manufacturer.
Here's another thing to consider about Samsung devices. ROMs from different regions with the same build and change list number released within days or weeks of each other can have different versions of included apps and s/w. As an example, some users on the N10.1-12 forum couldn't import PDFs in to S Note while the majority could. Those that could successfully imported the same PDFs that those that couldn't were having issues with. With some sleuthing we discovered there were almost a dozen different versions of S Note and that two had the PDF issue. And that was with the N10.1-12 being out for about three months. I'm on a Latin American SM-601 so there's the possibility that my BT might be different from U.S. (and possibly other region) SM-600's.
You might want to try a Samsung BT keyboard that you can return if you want to see if the BT issue is pervasive. If Samsung's KB works then you'll know that BT isn't totally borked and that perhaps updates might correct incompatibility issues with other keyboards.

The OEM customizations necessary to fit android to a particular platform is a necessary part of enabling the OS on vendor specific hardware platforms. I get that part, but replacing the entire stack instead of just creating the kernel driver component would definitely be an aggressive move. If this is the case, I would really be surprised that apps outside of the ones Samsung has written or bundled would be able to interfere with it. Maybe I'm giving samsung too much credit by assuming that they would leave the baseline android security model intact, but to deviate from it that badly is asking for a major vulnerability trainwreck. The inclusion of Knox (I won't get started on that in this thread) would imply that they are trying to prevent such a thing.
I obviously don't have the details necessary to speak decisively about what Samsng May or may not have done, but if what you say is correct and they have inserted some other BT stack, KitKat may not help us either. The stock BT stack in it adds support for HID over GATT (HOGP), enabling A number of BT 4.0 LE devices that currently won't work (MS Arc Touch for Surface Pro, for example). I'm hoping we might see an update to 4.4 in Q1 '14, so it'll be interesting to see how an updated release affects BT functionality.

Anyone try the app external keyboard helper?
Sent from my SM-P605 using XDA Premium HD app

matsuru said:
Anyone try the app external keyboard helper?
Click to expand...
Click to collapse
I gave the free version a shot but it didn't work. I tried some of the steps listed for Samsumg devices as well but no go...

matsuru said:
Anyone try the app external keyboard helper?
Sent from my SM-P605 using XDA Premium HD app
Click to expand...
Click to collapse
I tried it as well with no luck. Bluetooth keyboard connection is very intermittent. Connection still broken while typing.
Sent from my SM-P600 using XDA Premium HD app

I have a logitech k810 bluetooth keyboard and have no issues with disconnects, whatsoever. Maybe its a problem with the keyboards trying to conserve energy?

ChrisNee1988 said:
I have a logiteck k810 bluetooth keyboard and have no issues with disconnects, whatsoever. Maybe its a problem with the keyboards trying to conserve energy?
Click to expand...
Click to collapse
Could you describe your device details?
I'm having this problem with logitech k810 keyboard and android mouse. I have the pro version of the keyboard helper and it has no effect.
Here is a video of the issue = http://youtu.be/WlCgFQ0cAO0
It is much worse with the keyboard than the mouse. My Note 3 running android 4.3 has no issue with galaxy gear, keyboard, mouse and allshare cast all connected at once. I expected the same out of this tablet. I may be returning this tablet, I do not find this acceptable.
My device is a 32GB white SM-p600 USA version.
BT problem exists at initial boot, and was tested after each incremental firmware update to still be present.

Action B said:
Could you describe your device details?
I'm having this problem with logitech k810 keyboard and android mouse. I have the pro version of the keyboard helper and it has no effect.
Here is a video of the issue = http://youtu.be/WlCgFQ0cAO0
It is much worse with the keyboard than the mouse. My Note 3 running android 4.3 has no issue with galaxy gear, keyboard, mouse and allshare cast all connected at once. I expected the same out of this tablet. I may be returning this tablet, I do not find this acceptable.
My device is a 32GB white SM-p600 USA version.
BT problem exists at initial boot, and was tested after each incremental firmware update to still be present.
Click to expand...
Click to collapse
I saw your video (nice nicknames for mouse and note btw). I have the USA p600 16GB wifi only - white. I don't have a bluetooth mouse so I can't try that but it seems to work flawlessly with my K810 keyboard with my limited trials. I haven't done any extensive like write a paper but i've done some messaging and emails. Also i've only tried it with the latest firmware. I'd recommend doing a factory reset, and if that doesn't fix it, maybe exchange it for another unit.

Action B said:
BT problem exists at initial boot, and was tested after each incremental firmware update to still be present.
Click to expand...
Click to collapse
Since there's no possible s/w conflicts and I'm assuming you disabled the onscreen keyboard during your testing it might be the keyboard itself. If your keyboard is older/newer than @ChrisNee1988's it might have a different chip or f/w in it. Peripherals aren't built to exacting standards whereas it's unlikely for there to be h/w differences between two SM-600's built so close together.

BarryH_GEG said:
Since there's no possible s/w conflicts and I'm assuming you disabled the onscreen keyboard during your testing it might be the keyboard itself. If your keyboard is older/newer than @ChrisNee1988's it might have a different chip or f/w in it. Peripherals aren't built to exacting standards whereas it's unlikely for there to be h/w differences between two SM-600's built so close together.
Click to expand...
Click to collapse
The keyboard works great on my note 3 so it's fine.
Sent from my SM-N900P using Tapatalk