Related
I just recently bought a Samsung Galaxy Note 8 and was hoping to hook up a WiiMote to play some classic emulators, however the "WiiMote controller" app itself does not pair the two. I read somewhere that because of the bluetooth stack Samsung loads on, not all devices are supported. I do have the tablet rooted, but it is still running stock rom as I have not found other compatible roms to run on it yet. Is there any workaround to remove the bluetooth stack and load a standard Android on, or do I have to wait for more updates from dev?
Foresman1 said:
I just recently bought a Samsung Galaxy Note 8 and was hoping to hook up a WiiMote to play some classic emulators, however the "WiiMote controller" app itself does not pair the two. I read somewhere that because of the bluetooth stack Samsung loads on, not all devices are supported. I do have the tablet rooted, but it is still running stock rom as I have not found other compatible roms to run on it yet. Is there any workaround to remove the bluetooth stack and load a standard Android on, or do I have to wait for more updates from dev?
Click to expand...
Click to collapse
I have not looked into it, so I do not know if Samsung is using anything other than the stock BT stack.
I don't know of any way to easily changing the stack. It requires several things, kernel support, modules & the new stack code integrated into hardware specific drivers. BlueZ, has a plugin & source available written to specifically avoid proprietary BT code, but again, you'd need to at the very least compile a new kernel, then find & modify stock modules. I am not so sure that BlueZ has an HID profile, so it may not work anyway. A custom rom is not going to affect this & most likely, your best bet is getting the app developer to add device support.
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 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
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
wakers said:
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
Click to expand...
Click to collapse
It worked fine for me with KitKat.
Friday evening I upgraded to LolliPop. (Did a clean install, no data restore from backup)
Since then I have the same problem. Once you lose your Bluetooth connection it won't reconnect anymore.
You have to unpair and the repair in order to be connected again. A real pain in the ass, as I use it only for the notifications on the bracelet.
I have had a Vivosmart since the week they came out. I had a lot of the BT issues the first few months (mainly due to their software being released before it was really production ready) but has been fine since. I'm rooted and have ran a few different roms without an issue. Currently I'm using SkyDragon's Sense 7 rom. I haven't had to pair to my phone due to disconnects for at least a couple months. Are you pairing from with-in the Connect app? At one time the pairing was done via the regular android BT devices but they got rid of that and now pair from the app only. So technically your Vivosmart shouldn't ever show up on the list of installed/connected BT devices because it's only paired from the Connect app. I'm sure you've been on the garmin forum but if you haven't or someone else reading this hasn't it's here https://forums.garmin.com/forumdisplay.php?478-vivosmart. I've seen posts over there about m8 users having problems but don't remember reading if anyone was able to get the problem fixed and what they did. It doesn't make sense that it works for some (like me).
Hello,
I have same problem with Garmin Fenix 3. Apparently there is some bug in HTC ONE M8 Android 5.0.1
I am able to connect and connection is quite stable but watch wont reconnect automatically.
Usually it will reconnect once you reset BT on phone and than on watch. But its quite annoying so I am also looking for solutions. Any idea? Ive tried to add watch to trusted device under smart lock but its not working either. I know most Garmin devices worked on previous version of android on HTC ONE M8 but with Lollipop its bugged..
wakers said:
Not sure anyone will be able to help with this appreciate its a long shot, i've bought a Garmin Vivosmart fitness tracker and it connects to the phone via Bluetooth, now it all works mint except if i go out of range with the bluetooth the phone and garmin are supposed to reconnect automatically but it doesn't i have to unpair and then repair which isn't the end of the world but is a pain in the backside, looking on the garmin forums lots of people with M8's saying the same so there seems to be an issue with the way HTC - Garmin bluetooth works, some phones seem to work perfect (as in other android phones) so it doesn't seem a generic android-garmin issue, just wondering if anyone has had the same issue with any other bluetooth equipment and managed to find a cure ?
also if anyone know if custom roms mess about with bluetooth and the way it works, tempted to try an AOSP rom or CM to see if the bluetooth works properly but i do like sense so would prefer to stick with what i got, using Insertcoins Sense 7 rom, might go back to official sense 6 and see if that works also...
thanks for any suggestions...
Click to expand...
Click to collapse
G'day wakers,
I have had exactly the same problem with my m8. I also have only used insertcoin rom which may be part of the problem as I have an identical m8 with stock lollipop (never unlocked or rooted) and it has no problems with the vivosmart or Garmin Fenix BLE connection.
I have since sold my m8 and traded up to an m9, which is still stock, but I'm reluctant to flash custom Rom as the Bluetooth works perfectly... On the other hand, stock roms drive me mental with bloatware and ads.
If you try another Rom I'd be very interested to hear how you go...as it may give me some confidence to unlock my brand new m9.
Cheers.
great_lumbuey said:
G'day wakers,
I have had exactly the same problem with my m8. I also have only used insertcoin rom which may be part of the problem as I have an identical m8 with stock lollipop (never unlocked or rooted) and it has no problems with the vivosmart or Garmin Fenix BLE connection.
I have since sold my m8 and traded up to an m9, which is still stock, but I'm reluctant to flash custom Rom as the Bluetooth works perfectly... On the other hand, stock roms drive me mental with bloatware and ads.
If you try another Rom I'd be very interested to hear how you go...as it may give me some confidence to unlock my brand new m9.
Cheers.
Click to expand...
Click to collapse
Cheers for the reply i might try a few different rom's i presumed that lollipop was the issue from what your saying maybe not then i'll let you know...
I have any M8 stock lollipop and vivosmart. When vivosmart go out of range lose connection. When vivosmart come Back near smartphone, if I want to connect it, i must switch off Bluetooth and switch on manually.
It is not auto.
Can you help me?
Thank you
Inviato dal mio HTC One_M8 utilizzando Tapatalk
I'm experiencing an even worst problem with no pairing at all with my fenix 3 and Garmin Connect with Cyanogenmod 12.1 .
I've done the test with a Samsung SII, Oneplus X and Oneplus One. All pairing fail and all with Cyanogenmod 12.1
It's working well with a Samsung Galaxy S5 ! So if one Cyanogenmod developper is reading this, can you please let us know if this bug is known, or if you can log it, and i can help some troubleshooting as well.
Samyterje said:
I'm experiencing an even worst problem with no pairing at all with my fenix 3 and Garmin Connect with Cyanogenmod 12.1 .
I've done the test with a Samsung SII, Oneplus X and Oneplus One. All pairing fail and all with Cyanogenmod 12.1
It's working well with a Samsung Galaxy S5 ! So if one Cyanogenmod developper is reading this, can you please let us know if this bug is known, or if you can log it, and i can help some troubleshooting as well.
Click to expand...
Click to collapse
Solution found on my side by realizing that one dialog box is not scaled in Garmin Connect and so the "yes" button is not visible in material design. I've understood this by rolling back to Cyanogenmod 11 and see the process.
Workaround is to use a language with shorter words like english. My initial set was in French. So if it can help somebody else with Garmin Connect, use it
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