I'm trying to set up a tasker profile that would work around when my laptop is on with bluetooth, my phone would connect and run the appropriate Tasker profile. I can pair the phone but it just sits at "Paired but not connected". Is this even possible or do I need an app like Bluetooth File Transfer to generate the constant connection.
Inc2 w/ CM9 AOKP build 22 (happened with MIUI 11.25 & 12.9 as well)
Macbook Pro most recent model
I have had the same problem with CM builds. I have found that sense roms for this phone has much better BT connectivity. I use Locale alot, and it just seems to work better with sense roms. I have not tried any apps to help though.
420fan said:
I have had the same problem with CM builds. I have found that sense roms for this phone has much better BT connectivity. I use Locale alot, and it just seems to work better with sense roms. I have not tried any apps to help though.
Click to expand...
Click to collapse
Thanks, i had a feeling Sense base would work better.
I have a Galaxy Note 2 running Jedi Master 13. Every single thing is awesome about this phone...
EXCEPT:
I have a Lincoln with the new MyLincoln Touch radio. It supports text messaging ONLY with ICS or more specifically, Bluetooth 3.x. The Bluetooth MAP (messaging access profile) is different in 4.0 and thus not supported. Is there any way to downgrade said Bluetooth version?
I only use BT stereo and phone headsets normally, never use file transfers so the 4.0 advantages wouldn't affect me (I hope).
Thanks in advance for the input! :good:
Did u try and call the dealership, maybe ur car has update they can do
BACARDILIMON said:
Did u try and call the dealership, maybe ur car has update they can do
Click to expand...
Click to collapse
Yes, yes I did. I was in touch with the people that make the MyLincoln Touch device that works with Microsoft Sync. I have the newest version, which supports up to Android 4.1.1 and the Bluetooth 3.0 software, which has advanced compatibility with MAP. The Bluetooth 4.0 doesn't work the same and makes it lose the ability to do SMS from the car itself. Ugh.
I was hoping I could somehow put the old Bluetooth stack onto my phone to make it work properly. As of right now, Ford/Lincoln say that only Android ICS' Bluetooth stack is compatible. I feel better than the Apple community, they don't even get pictures to transfer. At least It's cool having the address book picture on my phone.
So can it be downgraded or not?
I am also interested in this (for another device though). Is it possible in principle?
No this stuff is way too complex due to the new advancement of spamsung Knox controling everything, we have very little control of our devices any more
Hi. I'm loving Android 4.2.2. I've noticed one parity difference though when it comes to auto connecting to my car's bluetooth dongle (It's a belkin aftermarket one). I've tried LiquidSmooth, rootbox nightlies, DeviantXone, etc. I've probably tried 7-8 different brands of ROMs. I've noticed though that on 4.2.2, bluetooth auto connect isn't alike on all of them. For some of them, bluetooth always auto connects with my Belkin receiver in the car. On the other ones, maybe sometimes.
I'm wondering if this perhaps has to do with deep sleep because I've noticed that (perhaps not coincidentally) on the ROMs where it always auto connects just fine, battery life tends to be a lot weaker. For a given ROM, I've tried changing the kernel from Ktoonsez, Lean, etc...no difference. For me, it's the ROM that makes the difference, not the kernel.
I've looked in /system/etc/bluetooth and perused through the .conf files. I could have sworn there used to be an auto sync related parameter but can't seem to find it. I don't know if maybe it's some parameter in a conf file somewhere. It would make sense that attempting to always auto connect with nearby devices would result in more of a battery drain.
Any ideas? Is it a setting or something ROM specific? Can it be changed by the end user of a ROM? I am trying to avoid bluetooth auto connect apps on the market since I also don't want a kernel wakelock being used for a service that never sleeps. That may really hinder battery. Thanks!
davidisflash said:
Hi. I'm loving Android 4.2.2. I've noticed one parity difference though when it comes to auto connecting to my car's bluetooth dongle (It's a belkin aftermarket one). I've tried LiquidSmooth, rootbox nightlies, DeviantXone, etc. I've probably tried 7-8 different brands of ROMs. I've noticed though that on 4.2.2, bluetooth auto connect isn't alike on all of them. For some of them, bluetooth always auto connects with my Belkin receiver in the car. On the other ones, maybe sometimes.
I'm wondering if this perhaps has to do with deep sleep because I've noticed that (perhaps not coincidentally) on the ROMs where it always auto connects just fine, battery life tends to be a lot weaker. For a given ROM, I've tried changing the kernel from Ktoonsez, Lean, etc...no difference. For me, it's the ROM that makes the difference, not the kernel.
I've looked in /system/etc/bluetooth and perused through the .conf files. I could have sworn there used to be an auto sync related parameter but can't seem to find it. I don't know if maybe it's some parameter in a conf file somewhere. It would make sense that attempting to always auto connect with nearby devices would result in more of a battery drain.
Any ideas? Is it a setting or something ROM specific? Can it be changed by the end user of a ROM? I am trying to avoid bluetooth auto connect apps on the market since I also don't want a kernel wakelock being used for a service that never sleeps. That may really hinder battery. Thanks!
Click to expand...
Click to collapse
The audio.conf is no longer there in 4.2.2. I've read something about the BT stack being re-engineered. Someone on xda has released some replacement libraries for BT and I suspect compiling a new library might be the only way to make changes similar to the previoud audio.conf file changes. This really sucks and there are not too many people who know enough about this sort of thing. Also, the android documentation for bluetooth is not helpful.
As for me, I am trying to get by BT audio working well again. Right now audio is skipping pretty bad streaming to my Kenwood (Parot) Bluetooth headunit. I know what settings I need for audio.conf to make this work, but have no idea what to tweak in Android 4.2.2.
HELP PLEASE
gg48gg said:
The audio.conf is no longer there in 4.2.2. I've read something about the BT stack being re-engineered. Someone on xda has released some replacement libraries for BT and I suspect compiling a new library might be the only way to make changes similar to the previoud audio.conf file changes. This really sucks and there are not too many people who know enough about this sort of thing. Also, the android documentation for bluetooth is not helpful.
As for me, I am trying to get by BT audio working well again. Right now audio is skipping pretty bad streaming to my Kenwood (Parot) Bluetooth headunit. I know what settings I need for audio.conf to make this work, but have no idea what to tweak in Android 4.2.2.
HELP PLEASE
Click to expand...
Click to collapse
+1 I have the same problems with my head unit. I'm hoping someone can fix this
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
I haven't seen many threads on this and I am curious as to why it is not a concern for many Android users. Maybe it is because many Android users did not move from Apple like I did. The fact is, Apple is still superior to Android in terms of vehicle bluetooth connectivity. The more you need to look at and operate your phone while driving, the more dangerous driving becomes.
The difference between AVRCP 1.3 and AVRCP 1.5 primarily is the playlist selections. Since my car supports this, with 1.5 (iPhone 5) I would be able to see the contents of my library and browse/select music. Then I switched to a Nexus 6 and didn't have this feature anymore. Just a couple days ago I got the Nexus 5X and I am surprised they didn't change this with Marshmallow.
Is Apple always going to hover over Android with their updated bluetooth stacks?
Seems ridiculous that this is still a problem. Its as if no one want to shed any light on this. Talking about this and no apps that expose the Bluetooth stack and avrcp versions to the users who don't know any better. I would be nice if this was a separate module that could be upgraded independently so users could get the functionality they needed. Companies like Samsung rolling there own stack and adding feature is not a proper fix. This should be Android standard.
I have always been thinking the same thing, why is the
bluetooth stack from Google missing so many features.. I have tried both Samsung and HTC and their stack is just so much better.. But I always end up with a Nexus phone again and longing for a better BT stack...
Sent from my Nexus 7 using Tapatalk
BT overall sucks with the 5X. Hissing, popping, laggy stream kills it for me. It can't keep the connection with my car either while iPhones were trouble free. It's almost 2016. Are we asking for too much?
Thought I would add a way to get some info. This is from android.stackexchange.com/questions/43667/discover-version-of-bluetooth
Turn on bluetooth by going to the home screen, clicking menu->settings bluetooth. Pull that to enabled. Make sure it is on.
On the home screen, click menu -> settings -> applications -> 'running' tab.
An item appears called: "bluetooth share".
A screen pops up with information about the program, but it is sparse.
Also you can go to All tab and "Bluetooth Share" to see its actual version number. Though that might not be very helpful.
Also and old article discussing some of the bluetooth stack changes in Android for what its worth.
lwn.net/Articles/597293/
Sorry for the broken url but I've not posted enough on XDA to be allowed proper urls.
I'm going to try keep posting things I find that might be useful just consolidate more info in one spot. Trying to make this problem clearer for myself.
Is there anything new about AVRCP 1.5 features? May it possible to build and install a custom kernel with bluez support (which afaik has avrcp 1.5 support)?
More info on the bluez stack
http://forum.xda-developers.com/showthread.php?t=2640723&page=1