So i deiced to get the 10" Joying rx3188 unit with android 5.1.1 that recently came on the market. So far I rooted it and got it set mostly how i want, but I discovered an issue with bluetooth. Basic phone pairing and functionality works properly and ive also paired my OBD2link MX unit with it as well for the torque app, which works fine as well. the issue i'm having is that other apps that would use bluetooth, think that bluetooth is disabled on the unit. when i try to have them use bluetooth, they ask if they can turn bluetooth on. Selecting yes hangs the app and i have to force end the app to stop it. Even if i go in to torque, it reads bluetooth as disabled even tough the app itself works fine otherwise.
It seems as if the OS is not properly flagging to apps that bluetooth is turned on as far as i can tell. Is there a workaround for this, or something i can do to signal to apps installed that bluetooth is indeed enabled on the HU?
whitetigerlgt said:
ive also paired my OBD2link MX unit with it as well for the torque app, which works fine as well.
Click to expand...
Click to collapse
whitetigerlgt said:
Even if i go in to torque, it reads bluetooth as disabled even tough the app itself works fine otherwise.
Click to expand...
Click to collapse
Sorry i don't understand, Torque is working for you or not?
But, what's the "bluetooth name" of your device? Because to work properly i think it must be "OBD" or "OBD2", otherwise you have to search an Xposed module that can help you.
I'm having the exact same problem with the same unit also on Lollipop. I've notified the developer in the Forum post below and he is looking into it. This now makes a total of 3 people with the same problem.
http://forum.carjoying.com/thread-52.html
whitetigerlgt said:
the issue i'm having is that other apps that would use bluetooth
Click to expand...
Click to collapse
what apps are you having problems with?
also, what car did you put it in? How does it look? 10 inch screen sounds awesome
I'm having two problems right now. The first is that I am unable to pair my Logitech k810 keyboard, and I am unable to connect to a Bluetooth dongle that is used by my radar detector / laser Jammer with an application called Alp connect. I've found quite a few bugs with this head unit and I'm reporting them all to the developer. It works okay my main concern is that it is quite sluggish and I think that is due to the one gigabyte of RAM and lollipop. I installed it in a 2011 Subaru Impreza
sterod said:
The first is that I am unable to pair my Logitech k810 keyboarda
Click to expand...
Click to collapse
I'm fully on board with the concept "your money your car, do what you want" but what do you use a keyboard for in the car?
Quite often I'm too lazy to unpack my laptop when I have to compose a lengthy email on the go so I prefer to do it with a keyboard rather than try to use the touch screen to bash out a couple paragraphs.
popeye70 said:
Sorry i don't understand, Torque is working for you or not?
But, what's the "bluetooth name" of your device? Because to work properly i think it must be "OBD" or "OBD2", otherwise you have to search an Xposed module that can help you.
Click to expand...
Click to collapse
Torque is working, but if you go to adapter status in torque i shows BT not enabled. And thats the issue, the BT status is off when apps check it. For torque, it does not try to turn on BT to function. other apps do, and when they do, they hang.
I need to somehow flag BT as on for other apps so they dont say they need to turn on BT to work.
CadillacMike said:
what apps are you having problems with?
also, what car did you put it in? How does it look? 10 inch screen sounds awesome
Click to expand...
Click to collapse
apps like tablet talk, or obdlink or solostorm. all think BT is off, and try to turn it on when you want to use the BT obd2 adapter.
its in a Mazda MX-5.
sterod said:
Quite often I'm too lazy to unpack my laptop when I have to compose a lengthy email on the go so I prefer to do it with a keyboard rather than try to use the touch screen to bash out a couple paragraphs.
Click to expand...
Click to collapse
If your objective is to solve the problem get a usb keyboard. They work. If your objective is to get bluetooth keyboards working you might have to wait a long time.
Well, I hope you are wrong as my previous NewsMy NU3001 head unit worked perfectly with it. I'm aware I can use a USB keyboard. In any case I'm happy the developer is willing to try and fix it. What is your source for claiming it will be a long time for it to be fixed?
Also to add to this, im also unable to pair my qstarx 10hz BT gps unit.
It may be helpful to post your Bluetooth concerns in the same thread as mine on the Joying Forum I linked to above so that the developer is aware it's not just me and may encourage him to work on this more quickly.
Just popped my head in over there. I was hoping that peeps here would know of a trick or flag for the OS to make all apps think BT is on. then they could get past the check and just access BT, kinda like what the torque app does.
Yeah if someone finds a way to do that I'd be interested to know how as well. Slightly off-topic did you try installing a custom recovery or the Xposed framework on this unit? I have tried and failed many different types of attempts to do it on this unit.
sterod said:
Well, I hope you are wrong as my previous NewsMy NU3001 head unit worked perfectly with it. I'm aware I can use a USB keyboard. In any case I'm happy the developer is willing to try and fix it. What is your source for claiming it will be a long time for it to be fixed?
Click to expand...
Click to collapse
My source? Joying didn't write the software.
And what relevance does that have to the speed at which the issue can be resolved? It seems that you are just being defeating for no purpose. The developer is willing to help and he has expressed that desire in many Communications I've had with him so far. I prefer to be optimistic and that he has the right people to contact to resolve the issue
sterod said:
Yeah if someone finds a way to do that I'd be interested to know how as well. Slightly off-topic did you try installing a custom recovery or the Xposed framework on this unit? I have tried and failed many different types of attempts to do it on this unit.
Click to expand...
Click to collapse
no. i just have it rooted so far with supersu installed. what feature in xposed could be used to help here?
None that I can think of I was just curious if you had been able to install Xposed. I am curious as to how you were able to install SuperSU, as I was only able to install King root.
sterod said:
And what relevance does that have to the speed at which the issue can be resolved? It seems that you are just being defeating for no purpose. The developer is willing to help and he has expressed that desire in many Communications I've had with him so far. I prefer to be optimistic and that he has the right people to contact to resolve the issue
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Generic_Android_Head_Unit/MCU_Explained
Related
The device is Holux GPSlim 236. The phone is Hermes. The phone will pair without question on a 6.0 rom, does not matter who cooked it.
It will specifically not pair with 6.1 roms.
I can see the device when scanning for bluetooth devices, i can choose it, it asks me for passcode, but will not accept the "0000" as the passcode. (tried hardware and software keyboards). IF i type in a passcode OTHER than "0000", it appears to pair, i can see the spp slave service and select it, but once the gps software tries to talk with it, it asks to pair again.
Something is definitely different in the pairing process between 6.0 and 6.1.
Any suggestions are greatly appreciated.
Also see thread about it here from the Himelaya:
http://forum.xda-developers.com/showthread.php?t=378103
Thanks,
Rock
Did you select it as a serial port? You have to do this after you pair the device with the phone!
I am not familar with gps units, does it have a pairing mode like a headset? I know with my Plantronics headset, if I let my phone discover it without the headset being in pairing mode, the phone says it pairs with it, but it really doesn't, so I put it in pair mode then turn on bluetooth on my phone and pair up as normal(0000 passkey) and all works fine.
I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.
Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)
Bluetooth Pairing with 6.1
In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:
"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."
It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.
I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.
I had issues with the same device on some roms. I eventually changed BT drivers from WM6 and all went back to normal.
On some WM6.1 roms things went OK though.
Try not using any password when you try and pair it manually.
If it asks would you like to pair your device automatically select no and do it manually.
I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.
mines gps is a holux 240 and i have the same probs
ive mentioned it on a couple of threads, im glad to know im not the only one
im stickin with K's 6 final until this problem gets sorted out
this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there
crusti said:
this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there
Click to expand...
Click to collapse
ummm no, dont move my thread thanks. you can start one over there if you would like.
crusti said:
mines gps is a holux 240 and i have the same probs
ive mentioned it on a couple of threads, im glad to know im not the only one
im stickin with K's 6 final until this problem gets sorted out
Click to expand...
Click to collapse
You are not the only one
I reverted back to the 6.0 and it pairs without issue. I am thinking that alot of these cookers do not pay much attention to the development of bluetooth in some of their roms. Its not like I changed something on the GPS, so something must have happened with the software.... Still investigating. I hope it works on schaps new rom.
miffymiffy said:
Try not using any password when you try and pair it manually.
If it asks would you like to pair your device automatically select no and do it manually.
I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.
Click to expand...
Click to collapse
this method paired my jabra automatically, it didnt even ask if i wanted to do it auto, i juck clicked "pair" and there it was.
When pairing the holux 236 on the other hand, it would ask for a passcode, then reject it if you put in the correct code of "0000". If you canceled it, it would appear in the connected devices list!!, but still ask to pair once the gps application tries to connect. VERY jacked up.
Hissing Syd said:
In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:
"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."
It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.
I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.
Click to expand...
Click to collapse
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...
rock99rock said:
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...
Click to expand...
Click to collapse
No, there was no mention of if it could be disabled.
Wam7 said:
I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.
Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)
Click to expand...
Click to collapse
Wam, which rom are you using now that it works with? id like to download and try it. The 5 or so ive tried did not work.
I power cycle the device without any change in pairing succession.
Thanks!
BTW: Other users experiencing differences between 6.0 and 6.1
http://forum.xda-developers.com/showthread.php?t=391488
http://forum.xda-developers.com/showthread.php?p=2240665
can anyone tell me if I can update the Bluetooth in my HTC Desire or have more profiles. the phone is branded o2 but can be rooted. I dont want to change anything else in the ROM just make the bluetooth connect automaticaly & reliably to the car.
There are newer software builds available but have no mention of updating bluetooth.
Ther are no OTA updates available.
Software Number is 2.14.207.1
Andriod 2.2
Thanks for any advice in advance.
Trampsdad
Can't you just pair the 2 devices together? I personally don't use Bluetooth so no idea on that aspect. Also, the software is so out of date because o2 cba to release and update. There are major updates since yours. It might be worth considering to root so then you can flash a newer ROM, or infact, you don't need to root and just use an RUU. With the newest software. No need to root it then and less chance of it mess up.
Hope this helps
I still have some strangeness with Bluetooth. From what I read there are some updates in Honeycomb and maybe gingerbread. But I don't have a feeling what you are looking for is in FroYo
Sent from my HTC Desire using XDA App
Well I have a Kenwood Headunit with Bluetooth and the connection to that using stock Froyo and LeeDroid showed some interesting results. Gaps in the phonebook for instance. However, putting a 2.3 ROM (Ginger Villain) sorted that out, its fine now.
Bluetooth depends on the other device too.
What exactly is the problem you are having?
What Car do you have?
What Bluetooth system is installed (is it standard)?
I have used my desire in a number of cars (Vauxhall, Ford, BMW) without any isses with pairing, using the Phonebook,etc. is a different matter.
Personally, I have just received a new BMW 528i, and it doesn't get on well with my Desire at all.
It pairs OK and can use both the phone and music, but when I leave and return to the car, it just refuses to auto-connect again, and I have to go through the pairing procedure again.
Oh, except one - the time I went back to the garage to 'complain' about it and ask for advice, when it worked perfectly. Until I got home again!
Have experimented with my old Nokia N85, and that works fine, too. So it's either the Desire or an incompatibility between it and the car.
Oh, my Desire is running MCR r9 (FroYo) at the moment. Are there known issues with this? Info on any Bluetooth updates I could apply would be gratefully received!
i have to enter my pairing code every time i connect my bt headset - i took this to be a quirk for the moment - hoping its fixed in 2.2.2/2.3.x etc.
Lothaen said:
i have to enter my pairing code every time i connect my bt headset - i took this to be a quirk for the moment - hoping its fixed in 2.2.2/2.3.x etc.
Click to expand...
Click to collapse
Im having this same problem also with a Pioneer Head Unit in my car.
Bluetooth has always been troublesome as it doesn't auto connect. It will connect if I either manually click on "Pioneer Head Unit" or turn Bluetooth off and on (which I automate with tasker).
The pin thing is new and happens with all roms I have tried except LeeDroid, (which I prefer not to use as I don't like sense much). Leedroid still has the auto connect problem.
daveaus said:
Bluetooth has always been troublesome as it doesn't auto connect. It will connect if I either manually click on "Pioneer Head Unit" or turn Bluetooth off and on (which I automate with tasker).
Click to expand...
Click to collapse
Some good hints there - thanks!
I can connect far more reliably if I initiate the connection from the phone than from the car.
Likewise, if BT is switched off on the phone and then turned on after the car is on, then it sometimes works, too. Certainly don't need to re-pair anywhere near as often.
Can I ask how you use Tasker to automate the BT switching? I've not used that (I use Setting Profiles instead which I understand does roughly the same thing), so am curious what kind of rule you have that's useful for this.
Cheers.
TheMegaMan_ said:
Can I ask how you use Tasker to automate the BT switching? I've not used that (I use Setting Profiles instead which I understand does roughly the same thing), so am curious what kind of rule you have that's useful for this.
Click to expand...
Click to collapse
I use the following rules:
On wifi connection turn off bluetooth
On wifi disconnection wait 30 seconds and turn bluetooth on.
If not wifi connected & not bluetooth connected turn bluetooth off and on every 5 minutes.
If not wifi connected & not bluetooth connected and incoming call turn bluetooth off and on.
If not wifi connected & not bluetooth connected when display switched on turn bluetooth off and on.
The battery drain hasn't been a problem, if I go away or won't be using my car for a while I disable tasker. Of course this doesn't help when it keeps asking for the pin.
daveaus said:
I use the following rules:
Click to expand...
Click to collapse
Ah, cunning! Of course...toggle it when it's not already connected. Prifile Settings doesn't seem to let me toggle things like BT directly, although I could probably do so by setting some appropriate profiles.
I'll have to experiment...or just buy Tasker, instead!
daveaus said:
Of course this doesn't help when it keeps asking for the pin.
Click to expand...
Click to collapse
True, but so far in my case, I've only had that when I've tried to initiate connection from the car. Hopefully your trick will mean I don't need to do that so often.
Anyone found a gingerbread rom (or any rom!) with improved Bluetooth?
I have found the bluetooth to be terrible on the desire. I have got about 3 devices that my phone just refuses to pair with.
Currently I am trying to get it to connect with an Elm 327 Obd scanner. No luck, it asks for a pin, then I enter the pin, but it immediately rejects it.
I have tried oxygen rom, leedroid, stock froyo, everything...
I also have a parrot hands free kit that does the same thing, asks for pin, then does nothing...
Something makes me think it might be the radio or something. Except that my phone DOES connect with my scala motorbike helmet... So frustrating
Sent from my HTC Desire using XDA App
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
So, Bluetooth works well with all alter devices but does not recognise my car Bluetooth. I have not had any issues so far testing from all possible android phones to Nokia and iPhone. I have a 2010 C class. Any suggestions? The car says that no devices has been found when trying to pair. Thanks
Same exact problem here with an Audi A1. I contacted support, but they only suggested things I had already tried (like factory reset etc). I'm going to try and get a log to them at some point this week.
Are you on the latest OTA? That's when the problems started happening for me - it was working fine before that.
bladerara1 said:
So, Bluetooth works well with all alter devices but does not recognise my car Bluetooth. I have not had any issues so far testing from all possible android phones to Nokia and iPhone. I have a 2010 C class. Any suggestions? The car says that no devices has been found when trying to pair. Thanks
Click to expand...
Click to collapse
Know issue supposed to be fixed next update.
HomerSp said:
Same exact problem here with an Audi A1. I contacted support, but they only suggested things I had already tried (like factory reset etc). I'm going to try and get a log to them at some point this week.
Are you on the latest OTA? That's when the problems started happening for me - it was working fine before that.
Click to expand...
Click to collapse
Yes, latest update. Unfortunately support gave me "support" I have already tried and if you have a bit of knowledge of android you do not need some to tell you those things. We just have to wait until next update. Thanks
Have you tried turning off HD audio in the device settings?
When the device is connected, go to Bluetooth and select the cog next to the device. Uncheck HD audio.
This worked for me with my JVC Bluetooth car stereo.
kdogguk said:
Have you tried turning off HD audio in the device settings?
When the device is connected, go to Bluetooth and select the cog next to the device. Uncheck HD audio.
This worked for me with my JVC Bluetooth car stereo.
Click to expand...
Click to collapse
For me to be ableto do that, I will need to be connected first. That a my problem.
I am trying to find a solution for switching launchers. I have a Galaxy S21+ running the One UI and Nova. I would like to be able to auto switch to Nova when my phone is connected to my radio in the car. The trigger for the switch, if I am able to find a way, would be either bluetooth connection to the radio or when the app AppRadio Unchained is activated. I am not rooted as I know that will make a difference. Can anyone help with suggestions or ideas? I have googled for hours and have found many looking to do something similar but have not found any real solutions.
Haven't heard anything about it, but good idea! Maybe check or ask over connected car section:
Connected Car
For discussion of connected car infotainment systems
forum.xda-developers.com
galaxys said:
Haven't heard anything about it, but good idea! Maybe check or ask over connected car section:
Connected Car
For discussion of connected car infotainment systems
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks! I will head that way now.
Also check here:
Android Head-Units
Discussion about Android Head Units
forum.xda-developers.com