Hi guys, I hope you can help.
I recently brought and installed A Pumpkin 10.1 unit (rk3188).
Ive managed to get Malaysk's custom rom installed but my issue is that i dont have steering wheel controls so i brought a satechi media button. (Because im a new user i cant post a link)
The thing is i can get the unit to find it but it will not connect to it. Could it be a bluetooth name limitation on the unit? is there a work around?
Thank you for your time guys.
Kris
I'm having the same issue... I think its temporal issue, I will update to 23 april rom...
Cool. Let me know how you get on.
The only BT devices that are supported are OBDII readers and Phones (for phonebook sharing, calls and media streaming). No other devices will work (media controllers, gamepads, etc).
That's a shame. I need to look at another work around. Thank you for the info
Is there any way around to connect to non OBDII devices via rooting and using xposed framework
I'm looking for a way for this to happen as well. Just purchased an iSimple remote for my Joying head unit. Lo-and-behold it doesn't work because... reasons? How hard is it for the programmers to allow a remote device use media controls while any other android unit will allow this?
Related
I'm thinking of upgrading to this phone, one of the main reasons is that my current device, which has galaxy S guts, is not compatible with most bluetooth devices. I like to use an app called blueputdroid that turns my phone into a universal keyboard as well as an ELM bluetooth device that turns my phone into a dyno along with the torque app for my car.
For some reason the way samsung built the bluetooth makes it not work with a lot of these things, I know it's not the apps or 3rd party devices as I use my old G1 now for it, but would much rather just have my main phone be my one device.
Have any of you tested blueputdroid or any bluetooth devices? If not could someone try out blueputdroid with this phone (it's free in the market) any help would be much appreciated thanx!!
Says it has detected unsupported Bluetooth stack.. Install cyanogen Rom, etc.
Thanks, at least this phone is likely to get cyanogenmod support which will fix the problem my SK sure as hell won't
My GS2 works perfect with my ELM adapter. It worked perfect with my Vibrant too. I've never had a single problem with any bluetooth device on either of them.
I've had a lot of bluetooth problems with both my vibrant and now my GS2. Both work reliably with my wife's mini cooper bluetooth but they both have had problems connecting to the garmin nuvi I use for handsfree in my car (and forget about the A2DP on it).
I tried a lot of roms on my vibrant (incl stock) and they did lots of cool stuff but never made the BT connect reliably. Then I came across this thread: http://forum.xda-developers.com/showthread.php?t=795691
I made the suggested change to /system/etc/bluetooth/audio.conf and voila! I finally have good BT with my vibrant.
So I got my SG2 last week, rooted it and found that it also had the bad settings in /system/etc/bluetooth/audio.conf. However it also lacked BLN (backlight notification) and few other tweaks I've come to love on my vibrant so I flashed juggernaut 2.6. That fixed all the major foibles with the SG2 but it still won't reliably connect to my garmin.
I opened up the filesystem to find that /system/etc/bluetooth/audio.conf is no longer there! Does anyone know where it went?
Apparently I don't have enough posts to ask in the dev forum where juggernaut was posted http://forum.xda-developers.com/showthread.php?t=1322642 so I'm hoping someone will see this plee for help.
thanks
the phone has BT 3.0, but it is backward compatible with BT 2.0 and 1.0 devices
i haven't had any trouble using it with my car deck (streaming audio & phone), my large collection of stereo BT devices, and other BT enabled phones & PCs/Laptops
the remote control feature from the stereo headsets works properly, for fast forward, backward, play, pause, talk, mute, etc
the only thing i have yet need to test BT on is with a BT smart wrist watch
Hello All!
I recently bought a new car that has a stock head unit from Toyota in the middle console, but no USB or even an AUX input for sound. But as the electronics enthusiast I am I started searching around for solutions that would fit my needs in regards to compatibility and usefulness, I haven’t been able to find the solution making me pleased.
I bought a 7” Tontec screen with resistive touch overlay and the first idea was to run this Kodi build on a Raspberry Pi B rev.2 (Kudos to Andrei for the fantastic project!) engineering-diy.blogspot.fi
Altough I would be able to use android as OS, mostly because I want to use the electrical and networking tools bought in Play Store. And since adding an android unit to my existing “Internet of Things” setup would be fairly simple.
To my knowledge there isn’t any stable good working build for android on the raspi and it struck me that I have two old but still functional android phones in the drawer. So I would only need to connect the phone to the screen, and basically get the same solution as with the MimicsX2 and Smartphone Uplink (smartphone-uplink.com)
Units at my disposal
Samsung GS2, GT-9300 (Will be used as Head Unit)
Samsung GS4 LTE+, GT-i9506 (Will not be used, my backup phone if my S5 breaks)
Tontec 7" Display (itontec.com/product-detail/product-name-7)
Display controller board (HDMI/Component-In)
Resistive 4-wire Touch Overlay
Touch controller board supplied with overlay (USB-out)
Pioneer 1-Din Car Stereo (Aux & USB for sound input)
Sure Electronics Audio Amp
ELM327 OBD2 Bluetooth Adapter for ECU Readings
Units to be bought
Bluetooth slave controller [USB-BT] (For connecting touch controller to android phone)
Touch controller (USB) (Optional, adafruit.com/products/1580 To emulate mouse HID, would this eliminate the need of external android driver?)
Reverse Camera
Main Issues
What Bluetooth slave should I use? Other issues to be taken into considerations regarding Bluetooth?
How many Bluetooth devices may be connected to the phone at once?
External BT GPS for added accuracy.
“Hands free” connection to regular Smartphone with SIM-card. (How should this be implemented? Pause music etc.)
And finally attached a visual box diagram of what i meant to accomplish.
postimg.org/image/mbnjcve5t/
And since I'm completely new to using bluetooth communication, is this even a possible setup? Anything i should know? I would be very grateful for some help before ordering the bluetooth modules, or other needed components.
Hi All,
I now own a Joying RK3188 1024x600, which I am really loving.
One issue I am having though, is using my Moga Controller with the unit.
The bluetooth will see the device, but will not pair/connect to it.
It is as if the Head Unit will only connect to mobile devices with audio output.
Is there anything I can change, or a patch to alter how the bluetooth operates?
I would really love you suggestions.
I am currently running the rooted rom suggested on the Joying website (http://forum.xda-developers.com/showpost.php?p=60591423&postcount=12068).
Thanks.
Read HERE.
Bumping an old thread. I have a moga controller and when scanned both A and B mode show up but I cannot pair with it on either mode. I tried the info in the link above but I still cannot get it to pair. It shows up as a phone icon instead of a controller on my Bluetooth settings.
Any help?
Edit: it's a 3188 model Android 4.4.4 on latest Malay ROM and 1024x600
OK I added the moga Bluetooth strings in the xposedMTC Bluetooth settings and it now shows up as an obd device. Followed the link posted 2 replies up and I don't think the exposedMTC will fix the issue. I'll try decompiling the Bluetooth files and manually adding them if that's possible.
Following this ^^^ I have tried a bluetooth keyboard and mini bluetooth SNES controller and while I can see it I can't pair with it. Is that a hardware shortcoming or bluetooth.apk shortcoming? I would love to be able to use this SNES controller, I have a SNES emulator installed with a few ROM's but no way to play them. I have a USB wired 360 controller that I am going to take out to my VW and try shortly but bluetooth is how I would like to do it. Thanks.
Id liek to know this as well. I have some devices that I can see but not pair with also.
Dave
Also interested in getting any of my bluetooth controllers to work with my unit. They show up, but won't connect.
What is the pin on those controllers, if there is one?
Is there an update on this thread? I am really interested in connecting 8bitdo controllers to my Pumpkin head-unit. Like everyone else i can see the devices but wont connect.
In a reddit post, someone made it with usb but is there any way to connect via bluetooth?
i also own a joying unit with malaysk rom (RK3188 / 1024x600 / 06.2016) since a few days and also i am not able to connect my 8bitido SNES controller.
- installed XposedMTC / Override BT OBD device string with SNES controller BT name (didn't enter full name because of space character
and pairing worked!
- did pair as OBD device
- didn't recognize as input device
so the controller doesn't work yet
would be interesting if the controller would work in original joying / pumpkin ROM?
=====================================================================
EDIT: after reading some time in malaysk rom thread it seems that BT functionality is trimmed from the manufacturerers... and so no support for numerous BT devices.
Hi everyone, looking to pick up an octacore headunit from aliexpress, "KANOR" branded.
[can't post link because new member]
But one of the main reasons I want it is to connect with my ECU through a google play app called MDash. It connects via bluetooth. Through my reading over these android head units, I've seen a lot of mentions of the bluetooth functionality only working for music, phone calls, and the obd2 adapters. Does anyone have experience on whether or not the bluetooth is still this limited for the newer Android 8.0 octacore units? And if so, is there a way I can get the functionality I need out of the headunit by rooting it?
Thanks for your time and help!
bump
bump. Any help is greatly appreciated before I spend my money on a headunit.
Yes mate still crap. In fact Id say worse.
I have a new erising octa px5, mtcE, android 8 and bluetooth is minimal. Phone app is rubbish, sounds / looks terrible and it just about works .
Dont no for sure what profiles it has stock but seems everywhere I read now ppl are going the android auto route (which uses 'OK' google everything (surprise surprise)) and always on data. etc.
Lemmings!
(@Admins I think this is the correct forum to post this in, but please feel free to move it if I've chosen the wrong forum. I'm still figuring out exactly what category my device is in)
TL;DR - Trying to figure out if it's possible to get an external USB Bluetooth dongle working on my radio instead of the built-in one, so I can connect to all types of bluetooth devices, not just streaming audio
Hi all,
I'm searching for a possible solution that would allow me to connect my Android radio (AUTOPUMPKIN AA0495B, using a PX5, MCU CSN2_06252019_163051) to a Dual XGPS160 device. I installed this stereo in my track car for the purpose of running Harry's Lap Timer; currently the app is running perfectly, with a wired OBDLink EX in use for OBDII data and also connecting to a GoPro via WiFi to control the camera. The last piece of the puzzle is I want to get an XGPS160 connected for better GPS data capture (10Hz vs 1Hz of the radio's GPS). After hours spent trying to get it to pair and connect to the device, I emailed AUTOPUMPKIN support and they confirmed that this radio cannot connect to such devices, as the Bluetooth module in the radio is essentially a glorified bluetooth headset and can only connect for streaming audio (I haven't been able to determine the model number of the bluetooth module it uses). My hope is there is a USB Bluetooth dongle that I could plug into the radio and then have the radio use that instead, which would then allow it to connect to the XGPS160 (and any other type of bluetooth device).
When I go into the Car Settings on the radio, it has the following options available for bluetooth:
IVT i140
IVT i145
FC6000TN
GOC_BC5
KD6
KD6 is what is selected from the factory. Please correct me if I'm wrong, but my understanding is this list is basically the different bluetooth hardware models the radio has driver support for? If I'm correct on that, then I'm also guessing if I were to plug in a bluetooth dongle using one of the other models and change this setting, the radio would use that instead of the built-in bluetooth? I don't use the bluetooth audio streaming or phone tethering feature, so I don't care if I lose those features if it allows me to connect the radio to the XGPS160. As long as the WiFi keeps working I'm ok with it.
Sorry if I'm asking any stupid questions; I'm a programmer by background, but even after hours of reading this forum my knowledge about the hardware in these Android radio units is still very limited. That being said, I'm not opposed to modifying config files to get this working. I have Android Developer mode enabled and I can connect to the radio via ADB; I spent some time looking at the file structure and various config files so modifying those if needed shouldn't be a problem for me.
thanks!
There was another (lengthy) thread on the subject of bluetooth dongles around here somewhere. You will have to do a search for it. If I remember correctly you had to open your head unit and physically disconnect your original bt module... and even with that there was limited success in getting the thing to actually work....and of those who claimed they did get it to work also said they couldn't get anything more to connect to the dongle than what the original BT could handle
It's too bad too. I have a sound processor on my system which uses an app through BT on my phone to make adjustments and I was HOPING it would connect to the head unit. It won't
BTW... your obdlink ex usb will also work with Torque (Pro). I use it with torque and it's blazing fast and reliable.... a lot more than a BT connection!
deja100 said:
(@Admins I think this is the correct forum to post this in, but please feel free to move it if I've chosen the wrong forum. I'm still figuring out exactly what category my device is in)
TL;DR - Trying to figure out if it's possible to get an external USB Bluetooth dongle working on my radio instead of the built-in one, so I can connect to all types of bluetooth devices, not just streaming audio
Hi all,
I'm searching for a possible solution that would allow me to connect my Android radio (AUTOPUMPKIN AA0495B, using a PX5, MCU CSN2_06252019_163051) to a Dual XGPS160 device. I installed this stereo in my track car for the purpose of running Harry's Lap Timer; currently the app is running perfectly, with a wired OBDLink EX in use for OBDII data and also connecting to a GoPro via WiFi to control the camera. The last piece of the puzzle is I want to get an XGPS160 connected for better GPS data capture (10Hz vs 1Hz of the radio's GPS). After hours spent trying to get it to pair and connect to the device, I emailed AUTOPUMPKIN support and they confirmed that this radio cannot connect to such devices, as the Bluetooth module in the radio is essentially a glorified bluetooth headset and can only connect for streaming audio (I haven't been able to determine the model number of the bluetooth module it uses). My hope is there is a USB Bluetooth dongle that I could plug into the radio and then have the radio use that instead, which would then allow it to connect to the XGPS160 (and any other type of bluetooth device).
When I go into the Car Settings on the radio, it has the following options available for bluetooth:
IVT i140
IVT i145
FC6000TN
GOC_BC5
KD6
KD6 is what is selected from the factory. Please correct me if I'm wrong, but my understanding is this list is basically the different bluetooth hardware models the radio has driver support for? If I'm correct on that, then I'm also guessing if I were to plug in a bluetooth dongle using one of the other models and change this setting, the radio would use that instead of the built-in bluetooth? I don't use the bluetooth audio streaming or phone tethering feature, so I don't care if I lose those features if it allows me to connect the radio to the XGPS160. As long as the WiFi keeps working I'm ok with it.
Sorry if I'm asking any stupid questions; I'm a programmer by background, but even after hours of reading this forum my knowledge about the hardware in these Android radio units is still very limited. That being said, I'm not opposed to modifying config files to get this working. I have Android Developer mode enabled and I can connect to the radio via ADB; I spent some time looking at the file structure and various config files so modifying those if needed shouldn't be a problem for me.
thanks!
Click to expand...
Click to collapse
No; it must be a specific BT type MD725 realtek device. No, you cant connect all manner of devices due to the hacked BT implementation.
Bob_Sanders said:
There was another (lengthy) thread on the subject of bluetooth dongles around here somewhere. You will have to do a search for it. If I remember correctly you had to open your head unit and physically disconnect your original bt module... and even with that there was limited success in getting the thing to actually work....and of those who claimed they did get it to work also said they couldn't get anything more to connect to the dongle than what the original BT could handle
It's too bad too. I have a sound processor on my system which uses an app through BT on my phone to make adjustments and I was HOPING it would connect to the head unit. It won't
BTW... your obdlink ex usb will also work with Torque (Pro). I use it with torque and it's blazing fast and reliable.... a lot more than a BT connection!
Click to expand...
Click to collapse
Yeh I found that threat in my searches, but no one in there quite mentioned this specific scenario (Selecting one of the other options in the Bluetooth settings) so I wasn't sure. And I'm definitely not opening up the unit and cutting on the hardware; hacking config files I can do all day long, but I have no skills when it comes to soldering so I'd probably just destroy the radio in the process of trying to cut that module :laugh:
Yeh I've run the OBDLink EX with Torque as well for data logging temps on track and it worked flawlessly for that as well. BT is definitely more convenient, especially since most are running apps from their phones, but if you have a dedicated radio like these then it's a no-brainer to permanently wire up a USB device.
marchnz said:
No; it must be a specific BT type MD725 realtek device. No, you cant connect all manner of devices due to the hacked BT implementation.
Click to expand...
Click to collapse
When you say "hacked BT implementation" I'm assuming you mean they don't use the standard Bluetooth stack built into the Android OS? That would make sense, as when I try to do anything with bluetooth from the standard Bluetooth settings menu, it doesn't do anything, doesn't see any devices available for pairing, or anything else. You can only see other devices and pair to them from the PUMPKIN Bluetooth app; the funny thing is it will go through the first steps and show the XGPS160 as being paired, but none of the apps that use the GPS actually see it as a paired device (my OBD dongle shows up, but not the GPS).
I don't understand why they didn't just use standard bluetooth that's already part of the OS, rather than use some hacky custom solution
Quick update since the last post. Spent some time tonight on google looking up the information I could find on those other bluetooth modules in the list of options on my stereo. Based on technical manuals and FCC documents, it appears the FC6000TN and BC5 are audio-only bluetooth chips that only support A2DP profile (basically the same as what I have now with the KD6); Now the IVT i140 and IVT i145 on the other hand appear to be full fledged bluetooth chips, and do support the SPP (Serial Port Protocol) that is needed by the XGPS160 (and many other bluetooth profiles) so in theory that would work. Unfortunately after searching for both of those, all I can find are ones in bare module form (i145 and i140) that would have to be soldered onto the board (assuming the pins are even compatible) and there are no USB versions of them that I could just plug in to my radio's free USB-A slot. The only thing even remotely close that comes up in Google in USB form is this adapter and I'm pretty sure it's not based on the i140 or i145.
Given that my soldering skills are non-existent, it seems I'm pretty much out of luck on getting this to work. Disappointing for sure, as I would gladly have paid more $ for the unit to come with a fully functional bluetooth module instead of this hacked audio only junk they put in it :/
deja100 said:
Quick update since the last post. Spent some time tonight on google looking up the information I could find on those other bluetooth modules in the list of options on my stereo. Based on technical manuals and FCC documents, it appears the FC6000TN and BC5 are audio-only bluetooth chips that only support A2DP profile (basically the same as what I have now with the KD6); Now the IVT i140 and IVT i145 on the other hand appear to be full fledged bluetooth chips, and do support the SPP (Serial Port Protocol) that is needed by the XGPS160 (and many other bluetooth profiles) so in theory that would work. Unfortunately after searching for both of those, all I can find are ones in bare module form (i145 and i140) that would have to be soldered onto the board (assuming the pins are even compatible) and there are no USB versions of them that I could just plug in to my radio's free USB-A slot. The only thing even remotely close that comes up in Google in USB form is this adapter and I'm pretty sure it's not based on the i140 or i145.
Given that my soldering skills are non-existent, it seems I'm pretty much out of luck on getting this to work. Disappointing for sure, as I would gladly have paid more $ for the unit to come with a fully functional bluetooth module instead of this hacked audio only junk they put in it :/
Click to expand...
Click to collapse
Unfortunately, It wouldn't matter which BT you use from the supported BT types, BT implementation is non-standard to do stuff like act as a BT hands-free.
marchnz said:
Unfortunately, It wouldn't matter which BT you use from the supported BT types, BT implementation is non-standard to do stuff like act as a BT hands-free.
Click to expand...
Click to collapse
Yeh, that's extremely disappointing Does anyone know of any Android based radio units that have full working bluetooth? I don't mind buying a new unit for the car if I know it will work with everything.
The old intel sofia units (mtcd as well) had the bluetooth & wifi ibtegrated into the soc...and they had a standard (or at least more profiles) implemented
Enviado desde mi SM-G975F mediante Tapatalk
ikerg said:
The old intel sofia units (mtcd as well) had the bluetooth & wifi ibtegrated into the soc...and they had a standard (or at least more profiles) implemented
Enviado desde mi SM-G975F mediante Tapatalk
Click to expand...
Click to collapse
Bummer they don't make those units anymore :/ Then again, they may not have been powerful enough to run my track timer apps anyway.