I can't post this in development because I an still a nobody ...
Would it be possible to add in rfcomm for Bluetooth SPP serial port? The Nook would make a great tablet for telescope mount control over BT. You can't do it with the iPad due to the security around the BT stacks. It would also allow NEMA GPS modules to be read for different applications.
I'm running CM7 7.0.2 and this isn't yet available.
Just a dream?
Not sure if this is what you're talking about, but you can send the GPS data to the Nook form a GPS device like a Cell phone or GPS receiver. I use a stand alone GPS receiver and sometimes my Droid cell phone to send my location to the Nook to use CoPilot and Google Maps on the Nook. That's at least half of what you're talking about right?
Calla969 said:
Not sure if this is what you're talking about, but you can send the GPS data to the Nook form a GPS device like a Cell phone or GPS receiver. I use a stand alone GPS receiver and sometimes my Droid cell phone to send my location to the Nook to use CoPilot and Google Maps on the Nook. That's at least half of what you're talking about right?
Click to expand...
Click to collapse
Hmm, you got me pondering...
I got out my trusty Garmin GPS 10 and I can pair but it's not connected. That could be for a couple of reasons (the Nook only connects on demand maybe.) But if what you are saying is correct, maybe it does support SPP since it uses a comm port for the GPS.
But, when I connected from my notebook and checked the services, SPP wasn't one of them (just OPEX and AD2P.) I will keep playing but I half expect that part of the SPP stack requirements are missing.
On the plus side, if the GPS will work too, that is a second plus since it's nice to be able to ask the GPS for the specific time and location during the telescope setup (it matters.)
I'll look for an app in the Market that might read an external GPS devices and show the location. I notice most apps are for reading the phone GPS (which we don't have.)
Thanks!
Android does not support SPP, but there are multiple apps in the market which do, Bluetooth GPS Provider is the one which I prefer as it works very well and just works no matter what.
Thanks folks,
I fired up the Garmin GPS 10 and it works using Bluetooth GPS. That means an application can add in the SPP. That is perfect and gives us hope!
I really appreciate the responses!
Awats said:
Thanks folks,
I fired up the Garmin GPS 10 and it works using Bluetooth GPS. That means an application can add in the SPP. That is perfect and gives us hope!
I really appreciate the responses!
Click to expand...
Click to collapse
Yes, apps can directly talk with a Blutooth GPS. There are a handful which do this, or again, Bluetooth GPS Provider will provide the BT GPS to every app that asks for GPS.
This isn't only about GPS. GPS is just one aspect. I want to communicate with any serial device over BT. My understanding from reading it that rfcomm and the applications can supply that function.
What I did notice last night is that even without an application that supplies rfcomm, the Nook would still discover the devices unlike the iPad. I could pair to pretty much anything I wanted but it wouldn't connect. That's normal from my perspective.
At least I know it can be made to work.
khaytsus said:
Android does not support SPP...
Click to expand...
Click to collapse
Well, the XOOM does at least. Not sure whether it was Motorola's or Google's doing though. I use a Bluetooth to Serial adapter from Roving Networks quite successfully with it. I'm unaware of any other devices that do it.
I agree that native Android doesn't support SPP but the rfcomm library does and if it's linked into the application, SPP works.
Now if I can only find a way to use VNC to control my PPC from the Nook without going through a remote server (maybe via adhoc or BT ...)
Any device at API level 5 (2.0) or above may support BluetoothSocket, RFCOMM and therefore SPP unless the OEM did something to screw it up.
Hopefully I'm not asking about something that's already been answered. But after spending hours on google, forums, etc I'm finding myself at a dead end.
On my note 3 I've got to liking the hands free mode but forgetting to turn it on when I get in the car or even worse, not turning it off when I get out is getting really annoying.
Now unlike most, I don't have bluetooth audio in the car at all. I've never needed it & never will. A simple headset is good enough. Problem is, the headset is always on, driving or not.
So I'm left with the OBD adapter on the car as a potential for letting the phone know I'm driving. But I just can't the damm thing to work.
Now the OBD adapter connects to the phone perfectly fine & I can load up the info in pretty much any app I try. But trying to set the phones "location settings" for the car (using the OBD adapter) just isn't doing anything. No matter how many times I tap the OBD adapter in the menu, it just does nothing. Yet bluetooth audio devices connect right up.
So my question now, is.... can you use the OBD adapter as an option for car location? or is there a way to hack the phone to allow it as an option? or am I just not looking at it right?
Thank's in advance.
O2 Samsung Galaxy Note 3 (SM-N9005) - Android 4.4.2 (Stock)
Hi, I have an issue related to odb2 that need your help guys,.
Currently, I have a HUD to show the speed and battery of car. I also have an ELM327 running by Torque app which help me keep track with many technical data realtime. All 2 devices are connected to the odb split wires.
The problem is when i use both device, only the elm327 show data via Torque app. The HUD only works if only I close the app Torque. It means each time I could only use 1 device. I even changed many type of device either many type of odb split wires but no use.
I would be grateful and appreciate your support to solve my issue.
Rgds,
I don't know if this feasible and as i am thinking it whatever connects uses a connection with specific baud rate and a standard like in the old days we had dialup modems.... that times you wasn't able to put 2 modems in the sane line, but maybe im wrong.
Joying JY-VOS01N4GS w/ an SC-9853i 1.8GHz Octa-core, installed in a 1991 Toyota MR2 with a Honda K24A2 turbo engine swapped into it, controlled by an ECU called a Hondata KPro V4.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/143309152617
I can install and run Hondata or RealDash apps on the stereo without issue, but I can't get it to connect to the ECU itself so I'm looking for suggestions. I've got a $20 no name tablet or a 7+ yrs old Samsung Note 3....all connect to the KPro without issue. Hondata, RealDash and Torque apps all connect without issue on the tablet or phone. New $350+ stereo...keeps giving me failed to connect error.
I'm open to rooting if needed, installing a different Bluetooth app, I have the pin to access developer options, etc....I just need it to connect and work.
m5james said:
Joying JY-VOS01N4GS w/ an SC-9853i 1.8GHz Octa-core, installed in a 1991 Toyota MR2 with a Honda K24A2 turbo engine swapped into it, controlled by an ECU called a Hondata KPro V4.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/143309152617
I can install and run Hondata or RealDash apps on the stereo without issue, but I can't get it to connect to the ECU itself so I'm looking for suggestions. I've got a $20 no name tablet or a 7+ yrs old Samsung Note 3....all connect to the KPro without issue. Hondata, RealDash and Torque apps all connect without issue on the tablet or phone. New $350+ stereo...keeps giving me failed to connect error.
I'm open to rooting if needed, installing a different Bluetooth app, I have the pin to access developer options, etc....I just need it to connect and work.
Click to expand...
Click to collapse
It will not pair. Joying (actually FYT/SYU) crippled the bluetooth on their units. You can only pair with phones and a few OBD and TPMS BT devices.
For the rest: nothing.
And that is done onto the lowest compiled level including the MCU. Other drivers/apps/kernels/whatever will not work.
I've been writing Joying and they offered to sell me their OBDII dongle at a discount. I explained to them shortly before writing this post that the car doesn't have an OBDII port since it's a 91, lightly explained the engine sway, but I haven't heard anything yet. Why would they go through all that effort...just to force us to buy their $15 OBDII dongle?
What about universal Bluetooth dongle plugged into one of the USB cords? Or maybe even USB to USB? The ECU has a USB port that I use when I connect to my laptop to run KPro Manager (a Windows PC based program) and the RealDash app on Android does give me the option of Bluetooth, USB or serial input. I'm currently monitoring from this tablet which is completely illegible while driving, needs to be manually powered on/off and then reconnected to Bluetooth...not being able to see the gauges on a much larger screen and automatically reconnect when I start the car crushes EVERY reason why I bought this stereo. There's gotta be a way.
Wrote a long reply, stupid token expired...I'm gonna try this.
https://www.hondata.com/forum/viewtopic.php?t=18829
Bluetooth dongle didn't work, but I can't confirm if it's a dongle issue since I can connect to it but then the Hondata app says "Ignition not on" when it is. Nevertheless today I played around with the GF's cwr who has a Joying JY-HOS02P4 screen in hers, it's only 3 months old, and it'll connect to my Hondata just fine! Would it be as simple as taking the Bluetooth APK from her car and installing it on mine?
Bump for help...there's gotta be a way :/
Bumping again, hoping maybe someone can help.
Following - need this for ECUTEK bluetooth adapter in my GTR, otherwise the screen is worthless...
m5james said:
Bumping again, hoping maybe someone can help.
Click to expand...
Click to collapse
Like mentioned a couple of posts above. Joying crippled Bluetooth and there is simply no "normal" bluetooth stack.
You cannot alter the current BT app as it won't be signed correctly anymore and it will not even be visible anymore.
You cannot add another BT app as that will not have the correct signing either.
Your question is not new. This BT "not being able to pair" is already an issue since 2016. You would be the first to find a solution.
The only thing you can try is what I described in this post, based on info from ojuniour.
Having said that: you should also search the rest of the forum and not only stick to your own question. Otherwise you might already have tried what I described. It might work, it might not.
Surfer, thank you so much for the reply. I've read in depth and was fearful of that, but will try what is in the thread you linked. If you'd be so kind, couple questions that you may have answers to:
- I have a sofia 9853 with android 8.1 (upgrading to 9.0), does that make things better worse or same for the bluetooth situation?
- I've seen some talk on much older threads of using Comfast® CF-WU725B as an external/usb bluetooth solution? Did this (or an alternative dongle) ever or does it still work?
- I've also seen talk of used xposed modules to add bluetooth devices to the whitelist - is there any truth to this?
Surfer, thanks in advance, this is for a tesla screen in a GTR. By removing the stock screen we lose a ton of critical info that can only be gotten back through ecutek, which currently only has a bluetooth solution for android.
M5James - sorry for hijacking your thread, but hopefully this helps you as well
xadamadax said:
Surfer, thank you so much for the reply. I've read in depth and was fearful of that, but will try what is in the thread you linked. If you'd be so kind, couple questions that you may have answers to:
- I have a sofia 9853 with android 8.1 (upgrading to 9.0), does that make things better worse or same for the bluetooth situation?
- I've seen some talk on much older threads of using Comfast® CF-WU725B as an external/usb bluetooth solution? Did this (or an alternative dongle) ever or does it still work?
- I've also seen talk of used xposed modules to add bluetooth devices to the whitelist - is there any truth to this?
Click to expand...
Click to collapse
1. There is no Sofia 9853. There is a Intel Sofia AND an Intel SC9853i. Those are 2 different CPUs needing different ROMs.
2. No idea. Like mentioned: an external BT dongle has not worked till now, but I have never heard of that Confast one.
3. Xposed is not supported on the 9853i. Not on Android 8.1 and neither on 9.0
@surfer63, thank you again, your thread here (https://forum.xda-developers.com/an...qa-tips-info-roll-joying-fyt-sc9853i-t3979377) helped me tremendously
@m5james, on a whim i plugged in ecutek to usb via the usb mini port, and shockingly there is support for it. Maybe try the same with Hondata if there is an sort of interface on it.
surfer63 said:
Like mentioned a couple of posts above. Joying crippled Bluetooth and there is simply no "normal" bluetooth stack.
You cannot alter the current BT app as it won't be signed correctly anymore and it will not even be visible anymore.
You cannot add another BT app as that will not have the correct signing either.
Your question is not new. This BT "not being able to pair" is already an issue since 2016. You would be the first to find a solution.
The only thing you can try is what I described in this post, based on info from ojuniour.
Having said that: you should also search the rest of the forum and not only stick to your own question. Otherwise you might already have tried what I described. It might work, it might not.
Click to expand...
Click to collapse
Fair enough...honestly like 10 +/-yrs ago I was WAY more into custom ROMs, baking, etc etc but nowadays I feel like it's over my head again. The only reason why I asked about using other BT versions from other Joying devices is because the GF's similarily aged stereo was able to connect, but I understand the signing thing since our two stereos don't share the same OS and CPU.
xadamadax said:
M5James - sorry for hijacking your thread, but hopefully this helps you as well
Click to expand...
Click to collapse
You're fine, the more exposure the merrier...I'm not as good at this stuff as I used to be so I'm just hoping someone smarter than me can help
xadamadax said:
@surfer63, thank you again, your thread here (https://forum.xda-developers.com/an...qa-tips-info-roll-joying-fyt-sc9853i-t3979377) helped me tremendously
@m5james, on a whim i plugged in ecutek to usb via the usb mini port, and shockingly there is support for it. Maybe try the same with Hondata if there is an sort of interface on it.
Click to expand...
Click to collapse
Do you have a pic of how you physically hooked it up? I haven't touched much on this subject since my original post and honestly don't recall the connections at the moment but I do recall mine having a square port (I don't know it's official name) that allows me to connect via USB to a laptop. I think I even tried connecting directly to the stereo that way but no luck.
Hondata runs on the screen easily in both portrait and landscape mode but I prefer RealDash, which at doesn't like portrait mode...I'm hoping it's something I can adjust to fit myself since RealDash allows for customisable gauges.
@m5james that is a micro usb port you have, try connecting it to a usb port on the head unit (same way you would a laptop) and open your hondata app - with any luck you'll be in business. If one port doesn't work, try the other - good luck
If you guys want to use the bluetooth pairing with basically about anything then buy the "Stop" brand. Unit actually confess with 2 BT models. One for music and phone call, the other one is located in the android bluetooth setting that would enable you to pair with anything.
ojuniour said:
If you guys want to use the bluetooth pairing with basically about anything then buy the "Stop" brand. Unit actually confess with 2 BT models. One for music and phone call, the other one is located in the android bluetooth setting that would enable you to pair with anything.
Click to expand...
Click to collapse
I looked on eBay for "stop android DIN" and nothing comes up.
m5james said:
I looked on eBay for "stop android DIN" and nothing comes up.
Click to expand...
Click to collapse
lol my bad I mean Atoto.. Damn auto correction.
here is an example of one connecting to ecuTek obd bluetooth:
https://www.ft86club.com/forums/showthread.php?t=141515
xadamadax said:
@m5james that is a micro usb port you have, try connecting it to a usb port on the head unit (same way you would a laptop) and open your hondata app - with any luck you'll be in business. If one port doesn't work, try the other - good luck
Click to expand...
Click to collapse
Wait wait wait. Wait a minute.... Are you saying you are able to get the ecuTek OBD bluetooth to work in wired mode[ to the head unit] without connecting to it wirelessly through bluetooth?
And you are using the ecuTek App?
I cant find much info on this device so I figured I would ask here. I picked up one of those Carplay AI Box dongles for the car and am having an issue keeping a bluetooth connection. Im trying to connect to and ODB MX+ which is attached to my car, via bluetooth and an app like DashCommand. Only issue is everytime I restart the car I have to go into the pairing menu of DashCommand for it to reactiveate bluetooth on the Ai Box. For whatever reason it seems bluetooth just isnt staying on. Even when the app is running and its connected the bluetooth indicator on the MI Box is off.
psychoholica said:
I cant find much info on this device so I figured I would ask here. I picked up one of those Carplay AI Box dongles for the car and am having an issue keeping a bluetooth connection. Im trying to connect to and ODB MX+ which is attached to my car, via bluetooth and an app like DashCommand. Only issue is everytime I restart the car I have to go into the pairing menu of DashCommand for it to reactiveate bluetooth on the Ai Box. For whatever reason it seems bluetooth just isnt staying on. Even when the app is running and its connected the bluetooth indicator on the MI Box is off.
Click to expand...
Click to collapse
What device. You haven't listed what the device is details, what you've done to resolve it or what the reseller suggests.
You brought a cheap Chinese origin device and then expect support - do you realise xda isn't the seller or the support forum. What I mean by that is you have to put the effort in to get help
Wake up on the wrong side of bed today or whats your deal?
I came here asking for help which I've done multiple times over the years, never once getting such a crap response. Yes, I bought a cheap Chinese android device, have you never purchased anything from China? I bought it because from the limited info on the internet it seemed to be the fastest one out there with the Snapdragon 665 cpu. If there was a better one made my Samsung or whoever I would have bought that but they dont exist so excuse me for buying somethign from China.
Any why on earth would I assume XDA is the reseller? There are literally hundreds of thousands of threads on this site of people asking for help with something they didnt buy from XDA so no idea why the hostility.
Thanks for your worthless reply, why did you even bother?
You could try one of the 'Bluetooth auto connect' apps on the Play Store.
But what I would do is use Tasker. Setup a profile with tasks that: turns on Bluetooth, then connects to your ODB device. And set the profile to activate when the display is 'on'.
You lucked out with yours as my CarPlay AI box doesn't even allow more than one device to be paired...so I've been unable to even pair my ODB reader.